- WLUG - wlug.mailman3.com

domain settings on dsl with dynamic IP and NAT (and postfix issue)

by Jim & Toni

One thing I've never been sure of is what to set the domain to on my Linux box. I'm on verizon dsl with a dynamic IP and PPPOE. I just got a dyndns.org domain with a different hostname than what I have for the machine. I set up the machine to run spamassassin (and to experiment). Machine name = grizzy Dyndns.org address = dibb.homelinux.net Email = jntdibb(a)bellatlantic.net What should I be using for the domain name? Specifically I'm having trouble with some part of postfix or spamc/d. I believe an hourly cron job is trying to send mail to 'root' which causes the following in maillog. I can send my postfix/main.cf file if anyone is interested. Oct 14 13:01:01 grizzy spamd[1921]: connection from grizzy [127.0.0.1] at port 3 3171 Oct 14 13:01:01 grizzy spamd[4504]: info: setuid to postfix succeeded Oct 14 13:01:02 grizzy spamd[4504]: Creating default_prefs [/var/spool/postfix/. spamassassin/user_prefs] Oct 14 13:01:01 grizzy postfix/local[4499]: 49D3FD0B45: to=<postfix(a)localhost.lo calhost>, relay=local, delay=1, status=bounced (can't create user output file. C ommand output: procmail: Couldn't create "/var/spool/mail/postfix" procmail: Loc k failure on "spamassassin.lock" procmail: Program failure (74) of "/usr/bin/spa mc" procmail: Rescue of unfiltered data succeeded ) Oct 14 13:01:01 grizzy postfix/cleanup[4497]: C4A35D0B43: message-id=<2003101417 0101.C4A35D0B43(a)grizzy.bellatlantic.net> Oct 14 13:01:01 grizzy postfix/nqmgr[1920]: C4A35D0B43: from=<>, size=2676, nrcp t=1 (queue active) Here's another example of something wrong. Oct 13 04:02:04 grizzy postfix/pickup[1462]: EFFAFD0B47: uid=0 from=<root> Oct 13 04:02:04 grizzy postfix/cleanup[1781]: EFFAFD0B47: message-id=<2003101308 0203.EFFAFD0B47@grizzy> Oct 13 04:02:04 grizzy postfix/nqmgr[1906]: EFFAFD0B47: from=<root(a)grizzy.grizzy >, size=1093, nrcpt=1 (queue active) Oct 13 04:02:06 grizzy postfix/smtp[1797]: EFFAFD0B47: to=<root(a)grizzy.grizzy>, relay=none, delay=3, status=bounced (Name service error for grizzy.grizzy: Host not found) Oct 13 04:02:06 grizzy postfix/cleanup[1781]: E295BD0B46: message-id=<2003101308 0206.E295BD0B46@grizzy> Oct 13 04:02:07 grizzy postfix/nqmgr[1906]: E295BD0B46: from=<>, size=2614, nrcp t=1 (queue active) Oct 13 04:02:07 grizzy postfix/smtp[1797]: E295BD0B46: to=<root(a)grizzy.grizzy>, relay=none, delay=1, status=bounced (Name service error for grizzy.grizzy: Host not found) Overall, mail handling seems to work. Stuff gets out, stuff comes in, spam gets tagged. But I need to clean some of this up.

Oct. 15, 2003

Re: [Wlug] Fw: RE: show

by Andy Stewart

On Tuesday 14 October 2003 12:55 pm, Yury I Vashugin wrote: > hi, everyone. > since we talked about producing an educational show about linux and > putting it 'in-the-air' at the last wlug meeting and i saw a very > enthusiastic response so i've reserved the studio for oct.21(see below). > there's a problem with a converter but i'm sure we can find a laptop with > a video output. HI everybody, I'm still quite enthusiastic about this opportunity, but unfortunately I cannot make it on October 21st (Tuesday is generally a bad night for me). I will be looking forward to reading the e-mails from people who do make it on that date. Please keep us posted! Andy -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org

Oct. 15, 2003

Re: [Wlug] NIC settings -- how?

by Matt Higgins

These links should get you started. I would be surprised if the distro you are running even supports ipchains. One NIC NAT: http://www.linuxjournal.com/article.php?sid=7175 Netfilter documentation section: http://www.netfilter.org/documentation/index.html iptables HOWTO: http://www.linuxguruz.com/iptables/howto/iptables-HOWTO.html GUI for iptables: http://www.fwbuilder.org/ rc script from linuhttp://www.linuxgazette.com/issue76/misc/whitmarsh/rc.firewall.sh.txtxg… artile:

Oct. 15, 2003

Re: [Wlug] NIC settings -- how?

by Keith Wright

> From: David Goss <vze2bd6u(a)verizon.net> > > have the pppoe all set up... but can't for the life of me remember > how to set up the ipchains to handle the windows boxes for the wife > and kids... and man they are getting hostile about not being able to > get on the internet from home... i know it was not that hard to set > up but for the life of me i can not find the docs i used in the > first place... Well, if you are starting from scratch you might as well use iptables instead of ipchains, which are nearing obsolete. Here is my "gateway" script. It is a firewall with a big hole in it. It protects the windows machines just by trusting the ISP not to route local addresses to you from outside. (I assume your Windows machines are 192.168.0.???, or similar.) Once you have a gateway working you can play with it to turn it into a real firewall. I have two ethernet cards in the firewall machine, one connected to the DSL modem one to the LAN. You don't say if you have the same. I think the below should work with one card, forwarding both from and to the LAN, but have not tried it. Also, I have a static IP address build into the script. I think to use PPPoE you need to change the last line, but again have not tried it. ------------------- #!/bin/bash /etc/sysconfig/network-scripts/ifup eth1 /sbin/rmmod ipchains /sbin/modprobe ip_conntrack_ftp echo "1" >/proc/sys/net/ipv4/ip_forward IPT="/sbin/iptables" INTERNET_ETHER="eth0" FCS_ETHER="eth1" GATEWAY_IP="66.92.74.1" FCS_IP="66.92.74.188" $IPT -t filter --flush $IPT -t nat --flush $IPT -t mangle --flush $IPT -A INPUT -i lo -j ACCEPT $IPT -A OUTPUT -o lo -j ACCEPT $IPT -t filter --policy INPUT ACCEPT $IPT -t filter --policy OUTPUT ACCEPT $IPT -t filter --policy FORWARD ACCEPT $IPT -t nat --policy PREROUTING ACCEPT $IPT -t nat --policy OUTPUT ACCEPT $IPT -t nat --policy POSTROUTING ACCEPT $IPT -t mangle --policy PREROUTING ACCEPT $IPT -t mangle --policy OUTPUT ACCEPT $IPT -t nat -A POSTROUTING -o $INTERNET_ETHER -j SNAT --to-source $FCS_IP ------------------ For PPPoE, change that last line to $IPT -t nat -A POSTROUTING -o $INTERNET_ETHER -j MASQURADE -- Keith

Oct. 15, 2003

Re: [Wlug] problem hardware?

by Baris Hasdemir

On Tue, 2003-10-14 at 16:05, Charles R. Anderson wrote: > On Tue, Oct 14, 2003 at 03:55:02PM -0400, Baris Hasdemir wrote: > > no. The region should be "1" I got this dvd from the shrewsbury public > > library. and actually it is playing the dvd without any problems. I am > > using xine to play it. the only problem is those error messages. > > Well, if it works I wouldn't worry about it. It is likely that xine > is trying "region 0" for playing DVDs from any region, although this > is just a guess. Do I need to set a region code? Here is what I think, I used my first dvd-rom first with a windows system. Probably the player there, changed the region setting to the first DVD that I put in it. But for a long time I do not have windows on my computer, so this new drive has born directly into linux. In linux do we still have region codes? If yes, may be that error is because I am expected to decide on a region? I found a utility regionset http://sourceforge.net/projects/dvd/ here is its output: ~~~~~~~~~~~~~~~~~~~ root@penguen:~# ./regionset /dev/dvd Current Region Code settings: RPC Phase: II type: NONE vendor resets available: 4 user controlled changes resets available: 5 drive plays discs from region(s):, mask=0xFF Would you like to change the region setting of your drive? [y/n]:n ~~~~~~~~~~~~~~~~~~ I could not decide whether a region is set already(by xine, or libdvdread or something...) or not. Other than region setting error it looks like I have a "driveready seekcomplete error" problem. What does this error mean? I get this error when I play a dvd: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Oct 14 17:00:56 penguen kernel: hdd: packet command error: status=0x51 { DriveReady SeekComplete Error } Oct 14 17:00:56 penguen kernel: hdd: packet command error: error=0x54 Oct 14 17:00:56 penguen kernel: ATAPI device hdd: Oct 14 17:00:56 penguen kernel: Error: Illegal request -- (Sense key=0x05) Oct 14 17:00:56 penguen kernel: Media region code is mismatched to logical unit -- (asc=0x6f, ascq=0x04) Oct 14 17:00:56 penguen kernel: The failed "Report Key" packet command was: Oct 14 17:00:56 penguen kernel: "a4 00 00 2b 0f 60 00 00 00 0c c4 00 " and I get this when I mount and look in a cd/dvd: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Oct 14 17:14:26 penguen kernel: hdd: command error: status=0x51 { DriveReady SeekComplete Error } Oct 14 17:14:26 penguen kernel: hdd: command error: error=0x54 Oct 14 17:14:26 penguen kernel: end_request: I/O error, dev 16:40 (hdd), sector 1792 thanks, baris

Oct. 14, 2003

Re: [Wlug] Fw: RE: show

by Gregory Avedissian

Makes sense to me, Tim. Easy replacement is the selling point, and in some ways it's been the stumbling block to my converting entirely to linux. I still use Windows for a couple of tasks that either can't be done in linux (yet) or I haven't figured them out in linux yet (unsupported scanner). Show people that they can do the things they need to do with a minimal amount of effort and without having to pay microsoft, and there will be plenty of converts. Most of the things that most people do with their computers can now be done in linux without having to read a manual, and people need to know that. Greg Keller, Tim wrote: > Yury, > > You can count me in. I also know my way around a TV production studio. > > We had talked about doing an introduction to linux. As an aside to that I > was thinking that possibly we could do a show on equivalent pieces of > software on the linux side of things that could replace (perceived) missing > functionality. This would include stuff like Evolution, Mozilla, GnuCash, > OpenOffice, mplayer, xmms, etc. > > What do people think? > > Thanks, > Tim. > > -----Original Message----- > From: Yury I Vashugin [mailto:vashugins@juno.com] > Sent: Tuesday, October 14, 2003 12:56 PM > To: wlug(a)mail.wlug.org > Cc: wlug(a)wlug.org > Subject: [Wlug] Fw: RE: show > > > hi, everyone. > since we talked about producing an educational show about linux and > putting it 'in-the-air' at the last wlug meeting and i saw a very > enthusiastic response so i've reserved the studio for oct.21(see below). > there's a problem with a converter but i'm sure we can find a laptop with > a video output. > for the show we need two cameramen(anyone can do that; very simple duties > and can be learned within 3-5 min), a show host and guests. > please, bring any suggestions or/and recommendations. thanks. > yury > > --------- Forwarded message ---------- > From: Marc Serra <mserra(a)ci.shrewsbury.ma.us> > To: 'Yury I Vashugin' <vashugins(a)juno.com> > Date: Fri, 10 Oct 2003 13:42:56 -0400 > Subject: RE: show > Message-ID: <A7F72312FF5DB348BE2D037A6FE5F1C1407EC2@selpnt2> > > Yes. > > Does anybody in the group have access to a scan converter or can you use > a > computer with a video card output? Since we spoke about it, our last scan > converter was put into service to be used on one of our channel's for our > bulletin board. For you to use it, we would have to take a channel off > the > air. I know that a lot of laptops have video out. > > -----Original Message----- > From: Yury I Vashugin [mailto:vashugins@juno.com] > Sent: Friday, October 10, 2003 11:48 AM > To: mserra(a)ci.shrewsbury.ma.us > Subject: show > > > marc, > can i reserve the studio for half-an-hour show on tuesday, october 21 at > 6:30 (actually it will not be a show; just a preliminary stuff- what > light, what background, what settings we want for 'linux show', to try a > scanner converter etc)? > yury > > ________________________________________________________________ > The best thing to hit the internet in years - Juno SpeedBand! > Surf the web up to FIVE TIMES FASTER! > Only $14.95/ month - visit www.juno.com to sign up today! > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > >

Oct. 14, 2003

Re: [Wlug] problem hardware?

by Charles R. Anderson

On Tue, Oct 14, 2003 at 03:55:02PM -0400, Baris Hasdemir wrote: > no. The region should be "1" I got this dvd from the shrewsbury public > library. and actually it is playing the dvd without any problems. I am > using xine to play it. the only problem is those error messages. Well, if it works I wouldn't worry about it. It is likely that xine is trying "region 0" for playing DVDs from any region, although this is just a guess. -- Charles R. Anderson <cra(a)wpi.edu> / http://angus.ind.wpi.edu/~cra/ PGP Key ID: 49BB5886 Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886

Oct. 14, 2003

Re: [Wlug] problem hardware?

by Baris Hasdemir

no. The region should be "1" I got this dvd from the shrewsbury public library. and actually it is playing the dvd without any problems. I am using xine to play it. the only problem is those error messages. On Tue, 2003-10-14 at 15:33, gboyce(a)badbelly.com wrote: > The error given here "Media region code is mismatched to logical unit" > sounds like the drive believes that it's not allowed to read content of > that type. Are you trying to view a non-US/Canada movie in the drive? > > On Tue, 14 Oct 2003, Baris Hasdemir wrote: > > > Hello all, > > > > Today I received my slot loading pioneer dvd rom drive from newegg.com. > > But linux tells me there are problems with it. The problem is my new > > hardware right? Or should I upgrade my kernel? I wanted to be sure > > before sending it back. > > > > kernel 2.4.22(slackware 9.1) > > > > thanks, > > baris > > > > # tail -f /var/log/syslog > > Oct 14 14:39:45 penguen kernel: hdd: packet command error: status=0x51 { > > DriveReady SeekComplete Error } > > Oct 14 14:39:45 penguen kernel: hdd: packet command error: error=0x54 > > Oct 14 14:39:45 penguen kernel: ATAPI device hdd: > > Oct 14 14:39:45 penguen kernel: Error: Illegal request -- (Sense > > key=0x05) > > Oct 14 14:39:45 penguen kernel: Media region code is mismatched to > > logical unit -- (asc=0x6f, ascq=0x04) > > Oct 14 14:39:45 penguen kernel: The failed "Report Key" packet command > > was: > > Oct 14 14:39:45 penguen kernel: "a4 00 00 00 01 26 00 00 00 0c c4 00 " > > Oct 14 14:39:45 penguen kernel: hdd: packet command error: status=0x51 { > > DriveReady SeekComplete Error } > > Oct 14 14:39:45 penguen kernel: hdd: packet command error: error=0x54 > > Oct 14 14:39:45 penguen kernel: ATAPI device hdd: > > Oct 14 14:39:45 penguen kernel: Error: Illegal request -- (Sense > > key=0x05) > > Oct 14 14:39:45 penguen kernel: Media region code is mismatched to > > logical unit -- (asc=0x6f, ascq=0x04) > > Oct 14 14:39:45 penguen kernel: The failed "Report Key" packet command > > was: > > Oct 14 14:39:45 penguen kernel: "a4 00 00 00 02 3d 00 00 00 0c c4 00 " > > Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { > > DriveReady SeekComplete Error } > > Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 > > Oct 14 14:39:46 penguen kernel: ATAPI device hdd: > > Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense > > key=0x05) > > Oct 14 14:39:46 penguen kernel: Media region code is mismatched to > > logical unit -- (asc=0x6f, ascq=0x04) > > Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command > > was: > > Oct 14 14:39:46 penguen kernel: "a4 00 00 00 02 ad 00 00 00 0c c4 00 " > > Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { > > DriveReady SeekComplete Error } > > Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 > > Oct 14 14:39:46 penguen kernel: ATAPI device hdd: > > Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense > > key=0x05) > > Oct 14 14:39:46 penguen kernel: Media region code is mismatched to > > logical unit -- (asc=0x6f, ascq=0x04) > > Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command > > was: > > Oct 14 14:39:46 penguen kernel: "a4 00 00 00 02 dc 00 00 00 0c c4 00 " > > Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { > > DriveReady SeekComplete Error } > > Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 > > Oct 14 14:39:46 penguen kernel: ATAPI device hdd: > > Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense > > key=0x05) > > Oct 14 14:39:46 penguen kernel: Media region code is mismatched to > > logical unit -- (asc=0x6f, ascq=0x04) > > Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command > > was: > > Oct 14 14:39:46 penguen kernel: "a4 00 00 00 0a 2b 00 00 00 0c c4 00 " > > Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { > > DriveReady SeekComplete Error } > > Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 > > Oct 14 14:39:46 penguen kernel: ATAPI device hdd: > > Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense > > key=0x05) > > Oct 14 14:39:46 penguen kernel: Media region code is mismatched to > > logical unit -- (asc=0x6f, ascq=0x04) > > Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command > > was: > > Oct 14 14:39:46 penguen kernel: "a4 00 00 20 f9 76 00 00 00 0c c4 00 " > > Oct 14 14:39:47 penguen kernel: hdd: packet command error: status=0x51 { > > DriveReady SeekComplete Error } > > Oct 14 14:39:47 penguen kernel: hdd: packet command error: error=0x54 > > Oct 14 14:39:47 penguen kernel: ATAPI device hdd: > > Oct 14 14:39:47 penguen kernel: Error: Illegal request -- (Sense > > key=0x05) > > Oct 14 14:39:47 penguen kernel: Media region code is mismatched to > > logical unit -- (asc=0x6f, ascq=0x04) > > Oct 14 14:39:47 penguen kernel: The failed "Report Key" packet command > > was: > > Oct 14 14:39:47 penguen kernel: "a4 00 00 20 f9 e6 00 00 00 0c c4 00 " > > > > > > > > _______________________________________________ > > Wlug mailing list > > Wlug(a)mail.wlug.org > > http://mail.wlug.org/mailman/listinfo/wlug > > > > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > > >

Oct. 14, 2003

Re: [Wlug] problem hardware?

by gboyce＠badbelly.com

The error given here "Media region code is mismatched to logical unit" sounds like the drive believes that it's not allowed to read content of that type. Are you trying to view a non-US/Canada movie in the drive? On Tue, 14 Oct 2003, Baris Hasdemir wrote: > Hello all, > > Today I received my slot loading pioneer dvd rom drive from newegg.com. > But linux tells me there are problems with it. The problem is my new > hardware right? Or should I upgrade my kernel? I wanted to be sure > before sending it back. > > kernel 2.4.22(slackware 9.1) > > thanks, > baris > > # tail -f /var/log/syslog > Oct 14 14:39:45 penguen kernel: hdd: packet command error: status=0x51 { > DriveReady SeekComplete Error } > Oct 14 14:39:45 penguen kernel: hdd: packet command error: error=0x54 > Oct 14 14:39:45 penguen kernel: ATAPI device hdd: > Oct 14 14:39:45 penguen kernel: Error: Illegal request -- (Sense > key=0x05) > Oct 14 14:39:45 penguen kernel: Media region code is mismatched to > logical unit -- (asc=0x6f, ascq=0x04) > Oct 14 14:39:45 penguen kernel: The failed "Report Key" packet command > was: > Oct 14 14:39:45 penguen kernel: "a4 00 00 00 01 26 00 00 00 0c c4 00 " > Oct 14 14:39:45 penguen kernel: hdd: packet command error: status=0x51 { > DriveReady SeekComplete Error } > Oct 14 14:39:45 penguen kernel: hdd: packet command error: error=0x54 > Oct 14 14:39:45 penguen kernel: ATAPI device hdd: > Oct 14 14:39:45 penguen kernel: Error: Illegal request -- (Sense > key=0x05) > Oct 14 14:39:45 penguen kernel: Media region code is mismatched to > logical unit -- (asc=0x6f, ascq=0x04) > Oct 14 14:39:45 penguen kernel: The failed "Report Key" packet command > was: > Oct 14 14:39:45 penguen kernel: "a4 00 00 00 02 3d 00 00 00 0c c4 00 " > Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { > DriveReady SeekComplete Error } > Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 > Oct 14 14:39:46 penguen kernel: ATAPI device hdd: > Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense > key=0x05) > Oct 14 14:39:46 penguen kernel: Media region code is mismatched to > logical unit -- (asc=0x6f, ascq=0x04) > Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command > was: > Oct 14 14:39:46 penguen kernel: "a4 00 00 00 02 ad 00 00 00 0c c4 00 " > Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { > DriveReady SeekComplete Error } > Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 > Oct 14 14:39:46 penguen kernel: ATAPI device hdd: > Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense > key=0x05) > Oct 14 14:39:46 penguen kernel: Media region code is mismatched to > logical unit -- (asc=0x6f, ascq=0x04) > Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command > was: > Oct 14 14:39:46 penguen kernel: "a4 00 00 00 02 dc 00 00 00 0c c4 00 " > Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { > DriveReady SeekComplete Error } > Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 > Oct 14 14:39:46 penguen kernel: ATAPI device hdd: > Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense > key=0x05) > Oct 14 14:39:46 penguen kernel: Media region code is mismatched to > logical unit -- (asc=0x6f, ascq=0x04) > Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command > was: > Oct 14 14:39:46 penguen kernel: "a4 00 00 00 0a 2b 00 00 00 0c c4 00 " > Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { > DriveReady SeekComplete Error } > Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 > Oct 14 14:39:46 penguen kernel: ATAPI device hdd: > Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense > key=0x05) > Oct 14 14:39:46 penguen kernel: Media region code is mismatched to > logical unit -- (asc=0x6f, ascq=0x04) > Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command > was: > Oct 14 14:39:46 penguen kernel: "a4 00 00 20 f9 76 00 00 00 0c c4 00 " > Oct 14 14:39:47 penguen kernel: hdd: packet command error: status=0x51 { > DriveReady SeekComplete Error } > Oct 14 14:39:47 penguen kernel: hdd: packet command error: error=0x54 > Oct 14 14:39:47 penguen kernel: ATAPI device hdd: > Oct 14 14:39:47 penguen kernel: Error: Illegal request -- (Sense > key=0x05) > Oct 14 14:39:47 penguen kernel: Media region code is mismatched to > logical unit -- (asc=0x6f, ascq=0x04) > Oct 14 14:39:47 penguen kernel: The failed "Report Key" packet command > was: > Oct 14 14:39:47 penguen kernel: "a4 00 00 20 f9 e6 00 00 00 0c c4 00 " > > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

Oct. 14, 2003

problem hardware?

by Baris Hasdemir

Hello all, Today I received my slot loading pioneer dvd rom drive from newegg.com. But linux tells me there are problems with it. The problem is my new hardware right? Or should I upgrade my kernel? I wanted to be sure before sending it back. kernel 2.4.22(slackware 9.1) thanks, baris # tail -f /var/log/syslog Oct 14 14:39:45 penguen kernel: hdd: packet command error: status=0x51 { DriveReady SeekComplete Error } Oct 14 14:39:45 penguen kernel: hdd: packet command error: error=0x54 Oct 14 14:39:45 penguen kernel: ATAPI device hdd: Oct 14 14:39:45 penguen kernel: Error: Illegal request -- (Sense key=0x05) Oct 14 14:39:45 penguen kernel: Media region code is mismatched to logical unit -- (asc=0x6f, ascq=0x04) Oct 14 14:39:45 penguen kernel: The failed "Report Key" packet command was: Oct 14 14:39:45 penguen kernel: "a4 00 00 00 01 26 00 00 00 0c c4 00 " Oct 14 14:39:45 penguen kernel: hdd: packet command error: status=0x51 { DriveReady SeekComplete Error } Oct 14 14:39:45 penguen kernel: hdd: packet command error: error=0x54 Oct 14 14:39:45 penguen kernel: ATAPI device hdd: Oct 14 14:39:45 penguen kernel: Error: Illegal request -- (Sense key=0x05) Oct 14 14:39:45 penguen kernel: Media region code is mismatched to logical unit -- (asc=0x6f, ascq=0x04) Oct 14 14:39:45 penguen kernel: The failed "Report Key" packet command was: Oct 14 14:39:45 penguen kernel: "a4 00 00 00 02 3d 00 00 00 0c c4 00 " Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { DriveReady SeekComplete Error } Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 Oct 14 14:39:46 penguen kernel: ATAPI device hdd: Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense key=0x05) Oct 14 14:39:46 penguen kernel: Media region code is mismatched to logical unit -- (asc=0x6f, ascq=0x04) Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command was: Oct 14 14:39:46 penguen kernel: "a4 00 00 00 02 ad 00 00 00 0c c4 00 " Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { DriveReady SeekComplete Error } Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 Oct 14 14:39:46 penguen kernel: ATAPI device hdd: Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense key=0x05) Oct 14 14:39:46 penguen kernel: Media region code is mismatched to logical unit -- (asc=0x6f, ascq=0x04) Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command was: Oct 14 14:39:46 penguen kernel: "a4 00 00 00 02 dc 00 00 00 0c c4 00 " Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { DriveReady SeekComplete Error } Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 Oct 14 14:39:46 penguen kernel: ATAPI device hdd: Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense key=0x05) Oct 14 14:39:46 penguen kernel: Media region code is mismatched to logical unit -- (asc=0x6f, ascq=0x04) Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command was: Oct 14 14:39:46 penguen kernel: "a4 00 00 00 0a 2b 00 00 00 0c c4 00 " Oct 14 14:39:46 penguen kernel: hdd: packet command error: status=0x51 { DriveReady SeekComplete Error } Oct 14 14:39:46 penguen kernel: hdd: packet command error: error=0x54 Oct 14 14:39:46 penguen kernel: ATAPI device hdd: Oct 14 14:39:46 penguen kernel: Error: Illegal request -- (Sense key=0x05) Oct 14 14:39:46 penguen kernel: Media region code is mismatched to logical unit -- (asc=0x6f, ascq=0x04) Oct 14 14:39:46 penguen kernel: The failed "Report Key" packet command was: Oct 14 14:39:46 penguen kernel: "a4 00 00 20 f9 76 00 00 00 0c c4 00 " Oct 14 14:39:47 penguen kernel: hdd: packet command error: status=0x51 { DriveReady SeekComplete Error } Oct 14 14:39:47 penguen kernel: hdd: packet command error: error=0x54 Oct 14 14:39:47 penguen kernel: ATAPI device hdd: Oct 14 14:39:47 penguen kernel: Error: Illegal request -- (Sense key=0x05) Oct 14 14:39:47 penguen kernel: Media region code is mismatched to logical unit -- (asc=0x6f, ascq=0x04) Oct 14 14:39:47 penguen kernel: The failed "Report Key" packet command was: Oct 14 14:39:47 penguen kernel: "a4 00 00 20 f9 e6 00 00 00 0c c4 00 "

Oct. 14, 2003

RE: [Wlug] Fw: RE: show

by mlong＠datalong.com

That sounds like a great topic. This could be expanded to include mini tutorials scattered about in subsequent shows explaining how to achieve the same functionality in the various apps. Cheers, Mike > Yury, > > You can count me in. I also know my way around a TV production studio. > > We had talked about doing an introduction to linux. As an aside to that I > was thinking that possibly we could do a show on equivalent pieces of > software on the linux side of things that could replace (perceived) > missing > functionality. This would include stuff like Evolution, Mozilla, GnuCash, > OpenOffice, mplayer, xmms, etc. > > What do people think?

Oct. 14, 2003

RE: [Wlug] Fw: RE: show

by Keller, Tim

Yury, You can count me in. I also know my way around a TV production studio. We had talked about doing an introduction to linux. As an aside to that I was thinking that possibly we could do a show on equivalent pieces of software on the linux side of things that could replace (perceived) missing functionality. This would include stuff like Evolution, Mozilla, GnuCash, OpenOffice, mplayer, xmms, etc. What do people think? Thanks, Tim. -----Original Message----- From: Yury I Vashugin [mailto:vashugins@juno.com] Sent: Tuesday, October 14, 2003 12:56 PM To: wlug(a)mail.wlug.org Cc: wlug(a)wlug.org Subject: [Wlug] Fw: RE: show hi, everyone. since we talked about producing an educational show about linux and putting it 'in-the-air' at the last wlug meeting and i saw a very enthusiastic response so i've reserved the studio for oct.21(see below). there's a problem with a converter but i'm sure we can find a laptop with a video output. for the show we need two cameramen(anyone can do that; very simple duties and can be learned within 3-5 min), a show host and guests. please, bring any suggestions or/and recommendations. thanks. yury --------- Forwarded message ---------- From: Marc Serra <mserra(a)ci.shrewsbury.ma.us> To: 'Yury I Vashugin' <vashugins(a)juno.com> Date: Fri, 10 Oct 2003 13:42:56 -0400 Subject: RE: show Message-ID: <A7F72312FF5DB348BE2D037A6FE5F1C1407EC2@selpnt2> Yes. Does anybody in the group have access to a scan converter or can you use a computer with a video card output? Since we spoke about it, our last scan converter was put into service to be used on one of our channel's for our bulletin board. For you to use it, we would have to take a channel off the air. I know that a lot of laptops have video out. -----Original Message----- From: Yury I Vashugin [mailto:vashugins@juno.com] Sent: Friday, October 10, 2003 11:48 AM To: mserra(a)ci.shrewsbury.ma.us Subject: show marc, can i reserve the studio for half-an-hour show on tuesday, october 21 at 6:30 (actually it will not be a show; just a preliminary stuff- what light, what background, what settings we want for 'linux show', to try a scanner converter etc)? yury ________________________________________________________________ The best thing to hit the internet in years - Juno SpeedBand! Surf the web up to FIVE TIMES FASTER! Only $14.95/ month - visit www.juno.com to sign up today! _______________________________________________ Wlug mailing list Wlug(a)mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug

Oct. 14, 2003

Fw: RE: show

by Yury I Vashugin

hi, everyone. since we talked about producing an educational show about linux and putting it 'in-the-air' at the last wlug meeting and i saw a very enthusiastic response so i've reserved the studio for oct.21(see below). there's a problem with a converter but i'm sure we can find a laptop with a video output. for the show we need two cameramen(anyone can do that; very simple duties and can be learned within 3-5 min), a show host and guests. please, bring any suggestions or/and recommendations. thanks. yury --------- Forwarded message ---------- From: Marc Serra <mserra(a)ci.shrewsbury.ma.us> To: 'Yury I Vashugin' <vashugins(a)juno.com> Date: Fri, 10 Oct 2003 13:42:56 -0400 Subject: RE: show Message-ID: <A7F72312FF5DB348BE2D037A6FE5F1C1407EC2@selpnt2> Yes. Does anybody in the group have access to a scan converter or can you use a computer with a video card output? Since we spoke about it, our last scan converter was put into service to be used on one of our channel's for our bulletin board. For you to use it, we would have to take a channel off the air. I know that a lot of laptops have video out. -----Original Message----- From: Yury I Vashugin [mailto:vashugins@juno.com] Sent: Friday, October 10, 2003 11:48 AM To: mserra(a)ci.shrewsbury.ma.us Subject: show marc, can i reserve the studio for half-an-hour show on tuesday, october 21 at 6:30 (actually it will not be a show; just a preliminary stuff- what light, what background, what settings we want for 'linux show', to try a scanner converter etc)? yury ________________________________________________________________ The best thing to hit the internet in years - Juno SpeedBand! Surf the web up to FIVE TIMES FASTER! Only $14.95/ month - visit www.juno.com to sign up today!

Oct. 14, 2003

Re: [Wlug] You can't get there from here...

by Gregory Avedissian

Andy Stewart wrote: > On Monday 13 October 2003 2:28 pm, Gregory Avedissian wrote: > >>Lowres won't work. The problem is it sees the S3Virge chip on the vid >>card and wants to use the s3virge driver, when it should really be using >>the 3DLabs driver. In the old sax, it tries to run in lowres first, and >>it comes up very large and hanging way over the edge of my screen. What >>I've found to work is this - >>sax -h 30-70 -v 50-150 -a 1024x768 -s XF86_3DLabs > > > The "very large and hanging way over the edge of my screen" problem is most > likely a funky "modelines" line in your XF86Config file. This can often be > remedied by manually adjusting your monitor, or by running (carefully!) > xvidtune and noting the new mode line once the screen is properly adjusted. > This new mode line would then be hand edited into your XF86Config file. If > the XFree86 v3.x driver (XF86_3DLabs) works for you, there may be no need to > fuss with the v4.x XFree86 driver. > > >>I've read the help screen for sax2 a bunch of times, and I don't >>understand how to give it the same information. >> >>sax2 -m 0=vga sort of works. I get a 320x200 image that fills the bottom >>half of my screen and bleeds way off the right edge. >> >>sax2 -m 0=glint quits and gives me error messages (no device found - the >>card has a glint 500tx accelerator) >> >>sax2 -m 0=s3virge goes black and locks up, only reset button gets me out >> > > > Which version of XFree86 4.x are you trying to use? If you are having > problems like this, you most likely need the latest and greatest. However, I > have seen cases where XFree86 v3.x works better than v4.x, especially on > "weird" video cards that are getting on in years. > > Later, > > Andy I'm trying to use 4.1.0. The 3Dlabs driver didn't come with 3.3.6. I had to find it online and unpack it. I also ran the Xinstall script that came with the 4.1.0 tarballs. I thought it had replaced all my files, so I can't tell you for sure which version is really running. I just tried again to run sax2 -m 0=vga, and it ran fine at 640x480. I'm not sure what's different now, but I did install some other packages this afternoon, like openmotif devel and some font packages. Anyway, sax2 does not list my vid card, but sax does. Maybe I should just leave this alone for now, since it works. If it's the source of the kde problem, I can live with it as long as my function keys work. BTW, I had asked you about my other machine, which wouldn't let me switch virtual screens. Turns out my nifty new keyboard has about 10 special buttons for web surfing, and one of them turns off the function keys. Thanks, Greg

Oct. 13, 2003

Re: [Wlug] You can't get there from here...

by Andy Stewart

On Monday 13 October 2003 2:28 pm, Gregory Avedissian wrote: > > Lowres won't work. The problem is it sees the S3Virge chip on the vid > card and wants to use the s3virge driver, when it should really be using > the 3DLabs driver. In the old sax, it tries to run in lowres first, and > it comes up very large and hanging way over the edge of my screen. What > I've found to work is this - > sax -h 30-70 -v 50-150 -a 1024x768 -s XF86_3DLabs The "very large and hanging way over the edge of my screen" problem is most likely a funky "modelines" line in your XF86Config file. This can often be remedied by manually adjusting your monitor, or by running (carefully!) xvidtune and noting the new mode line once the screen is properly adjusted. This new mode line would then be hand edited into your XF86Config file. If the XFree86 v3.x driver (XF86_3DLabs) works for you, there may be no need to fuss with the v4.x XFree86 driver. > > I've read the help screen for sax2 a bunch of times, and I don't > understand how to give it the same information. > > sax2 -m 0=vga sort of works. I get a 320x200 image that fills the bottom > half of my screen and bleeds way off the right edge. > > sax2 -m 0=glint quits and gives me error messages (no device found - the > card has a glint 500tx accelerator) > > sax2 -m 0=s3virge goes black and locks up, only reset button gets me out > Which version of XFree86 4.x are you trying to use? If you are having problems like this, you most likely need the latest and greatest. However, I have seen cases where XFree86 v3.x works better than v4.x, especially on "weird" video cards that are getting on in years. Later, Andy -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org

Oct. 13, 2003

Re: [Wlug] You can't get there from here...

by Andy Stewart

On Monday 13 October 2003 2:28 pm, Gregory Avedissian wrote: > >> > >>I'm thinking it might have to do with my funky vid card (ELSA GLoria-L). > >>Sax2 won't run on this machine - it goes to a black screen that won't > >>respond to any keystrokes except the reset button. I had to setup XFree > >>4.1 with the old sax, passing monitor and server parameters to it on the > >>command line for it to run correctly (hsync, vsync, screen resolution > >>and server). Sax2 doesn't seem to have the same switches. Is it bad to > >>setup newer versions of X with sax instead of sax2? > >> > >>BTW, I had a lot of trouble setting up the older version of XFree from > >>the CD's, too. > >> > >>Greg > > > > HI Greg, > > > > I think sax2 has a command line switch to force it to run in a low res > > mode, and I believe it is "-l" (minus ell). I've succeeded in using this > > with all sorts of strange hardware. This switch is not the default. > > > > sax is designed for XFree86 3.x, while sax2 is designed for XFree86 4.x. > > SuSE seems to be geared to more easily handle XFree86 4.x. > > > > See if you can get this graphics card to run in 640x480 8-bit color mode > > first, and if you succeed, then get brave and attempt higher resolutions > > afterwards. > > > > Later, > > > > Andy > > Andy, > > Lowres won't work. The problem is it sees the S3Virge chip on the vid > card and wants to use the s3virge driver, when it should really be using > the 3DLabs driver. In the old sax, it tries to run in lowres first, and > it comes up very large and hanging way over the edge of my screen. What > I've found to work is this - > sax -h 30-70 -v 50-150 -a 1024x768 -s XF86_3DLabs > > I've read the help screen for sax2 a bunch of times, and I don't > understand how to give it the same information. > > sax2 -m 0=vga sort of works. I get a 320x200 image that fills the bottom > half of my screen and bleeds way off the right edge. > > sax2 -m 0=glint quits and gives me error messages (no device found - the > card has a glint 500tx accelerator) > > sax2 -m 0=s3virge goes black and locks up, only reset button gets me out > > Can't figure out the proper syntax for the --xmode option to set the > screen resolution or hsync, and setting vsync doesn't seem to be an > option. If you know this secret, I'll buy you a beer. > > > Greg > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org

Oct. 13, 2003

RE: [Wlug] FW: Authentication on outgoing SMTP, how to set with postfix?

by Jim & Toni

Well, found the answer here. http://sdb.suselinux.hu/en/sdb/html/rsimai_imap_smtp_auth.html -----Original Message----- From: Jim & Toni [mailto:jntdibb@bellatlantic.net] Sent: Monday, October 13, 2003 2:28 PM To: 'wlug(a)wlug.org' Subject: Authentication on outgoing SMTP, how to set with postfix? I've almost got postfix setup as a mail relay from my local linux box to 'outgoing.verizon.net'. But, the postfix howto doesn't specify how to provide login/password authentication for smtp servers that require it. The error was '554: Authentication required' Going to search more, but appreciate any help. Thanks.

Oct. 13, 2003

FW: Authentication on outgoing SMTP, how to set with postfix?

by Jim & Toni

Sorry if you get multiples, like it says, having trouble with outgoing. Thanks. -----Original Message----- From: Jim & Toni [mailto:jntdibb@bellatlantic.net] Sent: Monday, October 13, 2003 2:28 PM To: 'wlug(a)wlug.org' Subject: Authentication on outgoing SMTP, how to set with postfix? I've almost got postfix setup as a mail relay from my local linux box to 'outgoing.verizon.net'. But, the postfix howto doesn't specify how to provide login/password authentication for smtp servers that require it. The error was '554: Authentication required' Going to search more, but appreciate any help. Thanks.

Oct. 13, 2003

Re: [Wlug] You can't get there from here...

by Gregory Avedissian

Andy Stewart wrote: > On Monday 13 October 2003 9:13 am, Gregory Avedissian wrote: > >>Same thing happens with any user, and the problem spans two consecutive >>installations on the same machine. The problem doesn't exist on my other >>machine, even though I intalled the same stuff. >> >>I'm thinking it might have to do with my funky vid card (ELSA GLoria-L). >>Sax2 won't run on this machine - it goes to a black screen that won't >>respond to any keystrokes except the reset button. I had to setup XFree >>4.1 with the old sax, passing monitor and server parameters to it on the >>command line for it to run correctly (hsync, vsync, screen resolution >>and server). Sax2 doesn't seem to have the same switches. Is it bad to >>setup newer versions of X with sax instead of sax2? >> >>BTW, I had a lot of trouble setting up the older version of XFree from >>the CD's, too. >> >>Greg > > > HI Greg, > > I think sax2 has a command line switch to force it to run in a low res mode, > and I believe it is "-l" (minus ell). I've succeeded in using this with all > sorts of strange hardware. This switch is not the default. > > sax is designed for XFree86 3.x, while sax2 is designed for XFree86 4.x. SuSE > seems to be geared to more easily handle XFree86 4.x. > > See if you can get this graphics card to run in 640x480 8-bit color mode > first, and if you succeed, then get brave and attempt higher resolutions > afterwards. > > Later, > > Andy > > Andy, Lowres won't work. The problem is it sees the S3Virge chip on the vid card and wants to use the s3virge driver, when it should really be using the 3DLabs driver. In the old sax, it tries to run in lowres first, and it comes up very large and hanging way over the edge of my screen. What I've found to work is this - sax -h 30-70 -v 50-150 -a 1024x768 -s XF86_3DLabs I've read the help screen for sax2 a bunch of times, and I don't understand how to give it the same information. sax2 -m 0=vga sort of works. I get a 320x200 image that fills the bottom half of my screen and bleeds way off the right edge. sax2 -m 0=glint quits and gives me error messages (no device found - the card has a glint 500tx accelerator) sax2 -m 0=s3virge goes black and locks up, only reset button gets me out Can't figure out the proper syntax for the --xmode option to set the screen resolution or hsync, and setting vsync doesn't seem to be an option. If you know this secret, I'll buy you a beer. Greg

Oct. 13, 2003

Re: [Wlug] You can't get there from here...

by Andy Stewart

On Monday 13 October 2003 9:13 am, Gregory Avedissian wrote: > > Same thing happens with any user, and the problem spans two consecutive > installations on the same machine. The problem doesn't exist on my other > machine, even though I intalled the same stuff. > > I'm thinking it might have to do with my funky vid card (ELSA GLoria-L). > Sax2 won't run on this machine - it goes to a black screen that won't > respond to any keystrokes except the reset button. I had to setup XFree > 4.1 with the old sax, passing monitor and server parameters to it on the > command line for it to run correctly (hsync, vsync, screen resolution > and server). Sax2 doesn't seem to have the same switches. Is it bad to > setup newer versions of X with sax instead of sax2? > > BTW, I had a lot of trouble setting up the older version of XFree from > the CD's, too. > > Greg HI Greg, I think sax2 has a command line switch to force it to run in a low res mode, and I believe it is "-l" (minus ell). I've succeeded in using this with all sorts of strange hardware. This switch is not the default. sax is designed for XFree86 3.x, while sax2 is designed for XFree86 4.x. SuSE seems to be geared to more easily handle XFree86 4.x. See if you can get this graphics card to run in 640x480 8-bit color mode first, and if you succeed, then get brave and attempt higher resolutions afterwards. Later, Andy -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org

Oct. 13, 2003

Re: [Wlug] You can't get there from here...

by Gregory Avedissian

Andy Stewart wrote: > On Sunday 12 October 2003 2:25 pm, Gregory Avedissian wrote: > >>At the meeting last Thursday, I asked about a problem I'm having with >>KDE desktop, and Tim mentioned I should run 'tail -f /var/log/messages' >>in another terminal while loading KDE. > > > Hi Greg, > > What happens if you create a brand new user, and then log in as that user and > fire up KDE? I'm wondering if there is a system problem or if something is > fubar in one of your user specific KDE files. > > Later, > > Andy Hi Andy, Same thing happens with any user, and the problem spans two consecutive installations on the same machine. The problem doesn't exist on my other machine, even though I intalled the same stuff. I'm thinking it might have to do with my funky vid card (ELSA GLoria-L). Sax2 won't run on this machine - it goes to a black screen that won't respond to any keystrokes except the reset button. I had to setup XFree 4.1 with the old sax, passing monitor and server parameters to it on the command line for it to run correctly (hsync, vsync, screen resolution and server). Sax2 doesn't seem to have the same switches. Is it bad to setup newer versions of X with sax instead of sax2? BTW, I had a lot of trouble setting up the older version of XFree from the CD's, too. Greg

Oct. 13, 2003

Re: [Wlug] You can't get there from here...

by Andy Stewart

On Sunday 12 October 2003 2:25 pm, Gregory Avedissian wrote: > At the meeting last Thursday, I asked about a problem I'm having with > KDE desktop, and Tim mentioned I should run 'tail -f /var/log/messages' > in another terminal while loading KDE. Hi Greg, What happens if you create a brand new user, and then log in as that user and fire up KDE? I'm wondering if there is a system problem or if something is fubar in one of your user specific KDE files. Later, Andy -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org

Oct. 13, 2003

You can't get there from here...

by Gregory Avedissian

At the meeting last Thursday, I asked about a problem I'm having with KDE desktop, and Tim mentioned I should run 'tail -f /var/log/messages' in another terminal while loading KDE. Description of problem: KDE starts to load, tells me it's checking peripherals, and then the screen goes black. Ctrl-alt-back kills the xserver and gets me out. In running the tail, I discovered that KDE really is runnning OK, but I have to switch to another virtual console (alt-F2) and then ctrl-alt-F7 will get me to the kde desktop. I get error messages from modprobe while kde is loading. It's looking for sound-slot-1, which I think is odd, because modules.conf doesn't say anything about a sound-slot-1. I only have one sound card, and it's at sound-slot-0. I tried turning off the sound server in the kde control center, and that didn't help. I also get gpm error messages when I go in an out of an x-session. Changing GPM_PARAMS in /etc/rc.config to the correct type of mouse helped get rid of flaky mouse behavior in console, but the error messages continue. Below are the messages. Any ideas or suggestions are appreciated. Thanks, Greg Oct 12 13:54:29 linux gpm[1601]: Error in protocol Oct 12 13:55:04 linux last message repeated 38 times Oct 12 13:55:05 linux modprobe: modprobe: Can't locate module sound-slot-1 Oct 12 13:55:05 linux modprobe: modprobe: Can't locate module sound-service-1-0 Oct 12 13:55:05 linux modprobe: modprobe: Can't locate module sound-slot-1 Oct 12 13:55:05 linux modprobe: modprobe: Can't locate module sound-service-1-0 Oct 12 13:55:05 linux modprobe: modprobe: Can't locate module sound-slot-1 Oct 12 13:55:05 linux modprobe: modprobe: Can't locate module sound-service-1-0 Oct 12 13:55:05 linux modprobe: modprobe: Can't locate module sound-slot-1 Oct 12 13:55:05 linux modprobe: modprobe: Can't locate module sound-service-1-0

Oct. 12, 2003

Re: [Wlug] NIC settings -- how?

by David Goss

Hi all... hope someone can help... been away from the meetings for a while... ( like a year ) due to health reasons... then to boot my linux machine had a massive failure and i had to replace it... had it all set up the forward and masquerade a couple of windows boxes through my dsl connection... ( verizon ) have the pppoe all set up... but can't for the life of me remember how to set up the ipchains to handle the windows boxes for the wife and kids... and man they are getting hostile about not being able to get on the internet from home... i know it was not that hard to set up but for the life of me i can not find the docs i used in the first place... hoping to make some meetings soon... now that the health is getting back to "normal"... and buying beer for the helpful guy that can get my network back to normal as well... best regards to all dave goss

Oct. 11, 2003

Re: [Wlug] NIC settings -- how?

by Charles R. Anderson

On Thu, Oct 09, 2003 at 01:18:34PM -0400, Bill Mills-Curran wrote: > How can I view and alter NIC settings, like auto-negotiate, speed, > duplex on my Red Hat 8/9 boxes? mii-tool or ethtool, depending on the driver. -- Charles R. Anderson <cra(a)wpi.edu> / http://angus.ind.wpi.edu/~cra/ PGP Key ID: 49BB5886 Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886

Oct. 9, 2003