May 2002 - WLUG - wlug.mailman3.com

Re: [Wlug] strange filenames

by Michael Frysinger

or just do what i do, rm ./--file_name -mike ----- Original Message ----- From: "Michelle Vadeboncoeur" <mrv(a)kluge.net> To: <wlug(a)mail.wlug.org> Sent: Saturday, May 25, 2002 11:55 Subject: Re: [Wlug] strange filenames > On Sat, 25 May 2002, Joe Riopel wrote: > > JR> If you want you can also open up midnight commander, just delete it > JR> that way. I had the same problem with a file named '-s' > > for files that start with a "-" character, to remove them you include a > "--" before the file name. > > for your example: rm -- -s > > I had to move and delete a bunch of files that were named with a "-" at > the beginning... Lots of graphics for a report for one of my math > classes... > > -- > --==*==-- --==*==-- Michelle R. Vadeboncoeur --==*==-- --==*==-- > mrv(a)kluge.net: http://www.kluge.net/~mrv/ > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

May 31, 2002

RE: [Wlug] weird ethernet problem...

by Keller, Tim

Well I'm running rh7.3 and I've got another box with this same card running 7.3 as well on the same network without a problem?? Weirdness. Tim. -----Original Message----- From: Charles R. Anderson [mailto:cra@WPI.EDU] Sent: Thursday, May 30, 2002 11:55 AM To: 'wlug(a)mail.wlug.org' Subject: Re: [Wlug] weird ethernet problem... On Thu, May 30, 2002 at 11:48:21AM -0400, Keller, Tim wrote: Tim.Keller> http://lists.us.dell.com/pipermail/linux-poweredge/2002-February/001688.html Tim.Keller> I also looked at the next message and I'm already running the eepro100 Tim.Keller> driver. Ahh. So it looks like it was a crappy card/driver problem after all. I did see somewhere else that you might want to download the driver from Intel and try that instead...of course I think that was the e100 they were referring to in that message :-/ -- 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 _______________________________________________ Wlug mailing list Wlug(a)mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug

May 30, 2002

Re: [Wlug] weird ethernet problem...

by Charles R. Anderson

On Thu, May 30, 2002 at 11:48:21AM -0400, Keller, Tim wrote: Tim.Keller> http://lists.us.dell.com/pipermail/linux-poweredge/2002-February/001688.html Tim.Keller> I also looked at the next message and I'm already running the eepro100 Tim.Keller> driver. Ahh. So it looks like it was a crappy card/driver problem after all. I did see somewhere else that you might want to download the driver from Intel and try that instead...of course I think that was the e100 they were referring to in that message :-/ -- 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

May 30, 2002

RE: [Wlug] weird ethernet problem...

by Keller, Tim

I just changed the format of the netstat so it would be more readable. also, I found a message that accurately describes the problem... http://lists.us.dell.com/pipermail/linux-poweredge/2002-February/001688.html I also looked at the next message and I'm already running the eepro100 driver. Tim. -----Original Message----- From: Charles R. Anderson [mailto:cra@WPI.EDU] Sent: Thursday, May 30, 2002 11:36 AM To: 'wlug(a)mail.wlug.org' Subject: Re: [Wlug] weird ethernet problem... On Thu, May 30, 2002 at 11:16:48AM -0400, Keller, Tim wrote: Tim.Keller> here's what netstat -i gives me... Tim.Keller> Thanks, Tim.Keller> Tim. Tim.Keller> Tim.Keller> Iface: eth0 Tim.Keller> mtu: 1500 Tim.Keller> met: 0 Tim.Keller> rx-ok: 0 Tim.Keller> rx-err: 0 Tim.Keller> rx-drp: 0 Tim.Keller> rx-ovr: 0 Tim.Keller> tx-ok: 0 Tim.Keller> tx-err: 0 Tim.Keller> tx-ovr: 3 Tim.Keller> flg: BMRU That's a strange netstat. I've never seen output formatted like that before. tx-ovr (overruns) is the statistic to watch out for. What does lspci -v -v say about your ethernet card? Any other relavent dmesg output? -- 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 _______________________________________________ Wlug mailing list Wlug(a)mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug

May 30, 2002

Re: [Wlug] weird ethernet problem...

by Charles R. Anderson

On Thu, May 30, 2002 at 11:16:48AM -0400, Keller, Tim wrote: Tim.Keller> here's what netstat -i gives me... Tim.Keller> Thanks, Tim.Keller> Tim. Tim.Keller> Tim.Keller> Iface: eth0 Tim.Keller> mtu: 1500 Tim.Keller> met: 0 Tim.Keller> rx-ok: 0 Tim.Keller> rx-err: 0 Tim.Keller> rx-drp: 0 Tim.Keller> rx-ovr: 0 Tim.Keller> tx-ok: 0 Tim.Keller> tx-err: 0 Tim.Keller> tx-ovr: 3 Tim.Keller> flg: BMRU That's a strange netstat. I've never seen output formatted like that before. tx-ovr (overruns) is the statistic to watch out for. What does lspci -v -v say about your ethernet card? Any other relavent dmesg output? -- 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

May 30, 2002

RE: [Wlug] weird ethernet problem...

by Keller, Tim

here's what netstat -i gives me... Thanks, Tim. Iface: eth0 mtu: 1500 met: 0 rx-ok: 0 rx-err: 0 rx-drp: 0 rx-ovr: 0 tx-ok: 0 tx-err: 0 tx-ovr: 3 flg: BMRU -----Original Message----- From: Charles R. Anderson [mailto:cra@WPI.EDU] Sent: Thursday, May 30, 2002 10:51 AM To: 'wlug(a)wlug.org' Subject: Re: [Wlug] weird ethernet problem... On Thu, May 30, 2002 at 10:08:52AM -0400, Keller, Tim wrote: Tim.Keller> NETDEV WATCHDOG: eth0: transmit timed out status 7088 0c00 at 241/301 Tim.Keller> command 001c000 Tim.Keller> Tim.Keller> the box has a Intel 10/100 Pro card running at 100 full duplex. Is the port the card is plugged into also running at full duplex? If autonegotiation is disabled on only one end of the link, you will have a duplex mismatch since the other end will fall back to half duplex. Always use autonegotiation on both ends, or on neither end. Any other errors? What does netstat -i show? Tim.Keller> I hooked up a win2k laptop configured it to the proper ip in the DMZ and it Tim.Keller> worked fine, so I know it's not the link. Try running tcpdump or ethereal on the link. I usually use tcpdump to write to a file, then copy it to my workstation and load it into ethereal there: server# tcpdump -i eth0 -s 1500 -w capture.pcap (the -s 1500 makes sure it captures the whole ethernet frames) I usually see these errors due to one of three reasons: 1. the netcard and/or driver is misconfigured (duplex, interrupt, etc.) 2. the netcard and/or driver is buggy or bad (usually seen on 3c503's :) 3. there is a TON of traffic on the network which is causing the card to not be able to keep up with the reception and transmission of all the packets. -- 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 _______________________________________________ Wlug mailing list Wlug(a)mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug

May 30, 2002

Re: [Wlug] weird ethernet problem...

by Charles R. Anderson

On Thu, May 30, 2002 at 10:08:52AM -0400, Keller, Tim wrote: Tim.Keller> NETDEV WATCHDOG: eth0: transmit timed out status 7088 0c00 at 241/301 Tim.Keller> command 001c000 Tim.Keller> Tim.Keller> the box has a Intel 10/100 Pro card running at 100 full duplex. Is the port the card is plugged into also running at full duplex? If autonegotiation is disabled on only one end of the link, you will have a duplex mismatch since the other end will fall back to half duplex. Always use autonegotiation on both ends, or on neither end. Any other errors? What does netstat -i show? Tim.Keller> I hooked up a win2k laptop configured it to the proper ip in the DMZ and it Tim.Keller> worked fine, so I know it's not the link. Try running tcpdump or ethereal on the link. I usually use tcpdump to write to a file, then copy it to my workstation and load it into ethereal there: server# tcpdump -i eth0 -s 1500 -w capture.pcap (the -s 1500 makes sure it captures the whole ethernet frames) I usually see these errors due to one of three reasons: 1. the netcard and/or driver is misconfigured (duplex, interrupt, etc.) 2. the netcard and/or driver is buggy or bad (usually seen on 3c503's :) 3. there is a TON of traffic on the network which is causing the card to not be able to keep up with the reception and transmission of all the packets. -- 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

May 30, 2002

weird ethernet problem...

by Keller, Tim

I just moved a box from a testing network to a DMZ network and I'm getting all this weird ethernet crap... here's the error's I keep getting NETDEV WATCHDOG: eth0: transmit timed out status 7088 0c00 at 241/301 command 001c000 the commands are different along with the status codes. the box has a Intel 10/100 Pro card running at 100 full duplex. I hooked up a win2k laptop configured it to the proper ip in the DMZ and it worked fine, so I know it's not the link. Thanks, Tim.

May 30, 2002

Re: [Wlug] USB Driver: Where to start?

by doug waud

Hi, back again with some second thoughts/ideas :-) Bill Smith wrote: > > Folks, > > I've got this idiot little USB camera that I got as part of a promotion. > (Specifically, it's a QuickVideo weeCam USB from Alaris that I got a > couple years back from Earthlink.) > > Near as I can figure, there are no drivers for this fool thing for > Linux. > > IF I were to attack the problem, where should I start? After sending off that first reply, I recalled that I had got a cheap webcam going some time ago. I went back to find it (took a while!) but it was not that weeCam (it was a Creative Model CT6840). However, I did find some notes I made at the time. The SuSE 7.2 Configuration manual has a chapter on "Watching TV on your PC" (yes, it does pay to buy the distro to get the manuals) which I followed. Basically, I ended up using xawtv (aw as in Athena widgets) which, in turn, uses V4L (video for linux). It looks like I just used Yast (the SuSE sysadmin tool) to install these two, plugged the camera into the USB port, and then went into a terminal (Alt/F2) and typed xawtv and a window came up with the picture from the camera. I just tried the last steps (Alt/F2 and xawtv) and got a view of the bookcase behind me. If you want to borrow that manual and don't mind driving out to Shrewsbury, you are welcome to take a peek. If you do come out, bring your camera and we can plug it in instead of mine and see if it works. doug

May 30, 2002

Re: [Wlug] USB Driver: Where to start?

by doug waud

Hi Bill Smith wrote: > > Folks, > > I've got this idiot little USB camera that I got as part of a promotion. > (Specifically, it's a QuickVideo weeCam USB from Alaris that I got a > couple years back from Earthlink.) > > Near as I can figure, there are no drivers for this fool thing for > Linux. > > IF I were to attack the problem, where should I start? You might find the WLUG slides for the Oct 11 2002 meeting helpful as background. While I was dealing with a compact flash reader and USB, you may still find the basic ritual informative. It certainly will not take long to skim. :-) (Just go to the WLUG website, click the "here" under "Past meeting Information" on the main page, and then the "view" under the third meeting from the top.) doug

May 30, 2002