- WLUG - wlug.mailman3.com

Server crash - is recovery possible?

by Richard Goodman

I'm running a RH 7.0 box at home that does (a) NAT for the local network (b) mail server for multiple domains (c) web server for multiple domains and (d) DNS for multiple domains Yesterday I attempted to ssh login from a workstation and got a message "..exited with Signal 11". I attempted to log on from the console and could not - got screen full of messages and numbers. At this point at least the web server was still running. I hit reset to reboot, got all the standard messages until "Checking root filesystem...." About 5-10% in, then: "Warning ..fsck.ext2 for device /dev/hda2 exited with signal 11 [FAILED] " Looked in my configuration book this morning ... hda2 is "/" . The only fortunate thing is that /home and /var are separate partitions on a second hard drive. Is there any way to recover from this? Barring that - is there any way to recover any config files from various places in /etc on this partition. If not I guess its a complete reload - mainly a problem with mail and DNS config files. I am only mildly competent on this stuff. If you need more info, I'll get it, although I don't know how to capture that screen full of info at the abort point. Dick Richard Goodman (508) 757-3452 r.goodman(a)11harvard.com 11 Harvard St, Worcester MA 01609

Aug. 26, 2002

Re: [Wlug] /dev/sequencer problems

by Michael Frysinger

when helping people solve their alsa problems, the answer almost always was 'use kernel drivers' as soon as they did, their problems went away -mike ----- Original Message ----- From: "Keith Wright" <kwright(a)gis.net> To: <wlug(a)mail.wlug.org> Sent: Sunday, August 25, 2002 16:54 Subject: Re: [Wlug] /dev/sequencer problems > > From: "Michael Frysinger" <vapier(a)WPI.EDU> > > > > If you're alsa or something, g'luck, cause i'm not touching alsa ;) > > Why is this? Is it personal (e.g. you have no time for it), or > is there something I should know before I start touching ALSA? > > -- Keith > > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

Aug. 25, 2002

Re: [Wlug] /dev/sequencer problems

by Charles R. Anderson

On Sun, Aug 25, 2002 at 04:54:15PM -0400, Keith Wright wrote: kwright> > From: "Michael Frysinger" <vapier(a)WPI.EDU> kwright> > kwright> > If you're alsa or something, g'luck, cause i'm not touching alsa ;) kwright> kwright> Why is this? Is it personal (e.g. you have no time for it), or kwright> is there something I should know before I start touching ALSA? As to the last question: It certainly is a bit trickier to set up, but that is mainly because it isn't integrated into most distributions or mainline stable kernels. However, now that Linus has accepted it in kernel 2.5, we will hopefully see more support built-in to the distributions. Once you set it up, however, it has more advanced features. Your applications would need to be coded to the native ALSA API to take advantage of most features, but there are some other neat things you can do without specific application support, like intercept the output stream for visual effects and/or recording. Major apps like XMMS (via external plugin), xine and mplayer have ALSA support. My main impetus for using it is that the i810 AC'97 codec support in OSS/Free sucks. Both the Dell machines I've used come with this braindead sound hardware. The older Dell wouldn't do bitrates other than 44kHz/16-bit under OSS (or it tried to do them, with abyssmal results). ALSA fixed these issues for me. -- 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

Aug. 25, 2002

Re: [Wlug] /dev/sequencer problems

by Keith Wright

> From: "Michael Frysinger" <vapier(a)WPI.EDU> > > If you're alsa or something, g'luck, cause i'm not touching alsa ;) Why is this? Is it personal (e.g. you have no time for it), or is there something I should know before I start touching ALSA? -- Keith

Aug. 25, 2002

Re: [Wlug] /dev/sequencer problems

by Charles R. Anderson

On Sun, Aug 25, 2002 at 02:08:25PM -0400, Wesley Allen wrote: wallen> what modules are these? How do I load them? Just found the files are wallen> provided in a kernel package, so I must have modules installed, but not wallen> loaded! First, make sure you have the proper stuff in /etc/modules.conf: # ALSA native device support alias char-major-116 snd options snd snd_major=116 snd_cards_limit=1 alias snd-card-0 snd-intel8x0 # this depends on your sound card # ALSA OSS/Free emulation support alias char-major-14 soundcore alias sound-slot-0 snd-card-0 alias sound-service-0-0 snd-mixer-oss alias sound-service-0-1 snd-seq-oss alias sound-service-0-3 snd-pcm-oss alias sound-service-0-8 snd-seq-oss alias sound-service-0-12 snd-pcm-oss Then, the correct modules are usually loaded by /etc/init.d/alsasound. So: /sbin/service alsasound start At least that's what does it on my RH system. -- 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

Aug. 25, 2002

Re: [Wlug] /dev/sequencer problems

by Wesley Allen

what modules are these? How do I load them? Just found the files are provided in a kernel package, so I must have modules installed, but not loaded! Wes On Sun, 2002-08-25 at 14:04, Charles R. Anderson wrote: > On Sun, Aug 25, 2002 at 01:53:47PM -0400, Wesley Allen wrote: > wallen> And Mandrake uses.....ALSA...oh well, I'll find another outlet! > wallen> Thanks anyway gang! > > Not yet... > > Check if you have the OSS compatibility modules loaded: > > /sbin/lsmod | grep oss > > You should see something like this: > > snd-seq-oss 27552 0 (autoclean) > snd-seq-midi-event 5440 0 (autoclean) [snd-seq-oss] > snd-seq 43596 2 (autoclean) [snd-seq-oss > snd-seq-midi-event] > snd-pcm-oss 41540 0 (autoclean) > snd-mixer-oss 10944 0 (autoclean) [snd-pcm-oss] > snd-pcm 68192 0 [snd-pcm-oss snd-intel8x0] > snd-seq-device 5480 0 [snd-seq-oss snd-seq snd-rawmidi] > snd 36200 4 [snd-seq-oss snd-seq-midi-event snd-seq > snd-pcm-oss snd-mixer-oss snd-intel8x0 snd-pcm snd-timer snd-ac97-codec > snd-mpu401-uart snd-rawmidi snd-seq-device] > > > The 'seq' devices are the ones that run the sequencer. > > Never used devfs, but I've always had to make the sound devices for ALSA > manually: > > cd /usr/share/doc/alsa-driver-0.9.0rc2 > ./snddevices > > That will create /dev/sequencer for you, too. > > Also, make sure your sequencer is unmuted in alsamixer. > > -- > 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 > -- This message may be digitally signed. For my public key, e-mail me a request.

Aug. 25, 2002

Re: [Wlug] /dev/sequencer problems

by Wesley Allen

No, they're not installed. perhaps I'll go look for them...hmm... Thanks, Wes On Sun, 2002-08-25 at 14:04, Charles R. Anderson wrote: > On Sun, Aug 25, 2002 at 01:53:47PM -0400, Wesley Allen wrote: > wallen> And Mandrake uses.....ALSA...oh well, I'll find another outlet! > wallen> Thanks anyway gang! > > Not yet... > > Check if you have the OSS compatibility modules loaded: > > /sbin/lsmod | grep oss > > You should see something like this: > > snd-seq-oss 27552 0 (autoclean) > snd-seq-midi-event 5440 0 (autoclean) [snd-seq-oss] > snd-seq 43596 2 (autoclean) [snd-seq-oss > snd-seq-midi-event] > snd-pcm-oss 41540 0 (autoclean) > snd-mixer-oss 10944 0 (autoclean) [snd-pcm-oss] > snd-pcm 68192 0 [snd-pcm-oss snd-intel8x0] > snd-seq-device 5480 0 [snd-seq-oss snd-seq snd-rawmidi] > snd 36200 4 [snd-seq-oss snd-seq-midi-event snd-seq > snd-pcm-oss snd-mixer-oss snd-intel8x0 snd-pcm snd-timer snd-ac97-codec > snd-mpu401-uart snd-rawmidi snd-seq-device] > > > The 'seq' devices are the ones that run the sequencer. > > Never used devfs, but I've always had to make the sound devices for ALSA > manually: > > cd /usr/share/doc/alsa-driver-0.9.0rc2 > ./snddevices > > That will create /dev/sequencer for you, too. > > Also, make sure your sequencer is unmuted in alsamixer. > > -- > 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 > -- This message may be digitally signed. For my public key, e-mail me a request.

Aug. 25, 2002

Re: [Wlug] /dev/sequencer problems

by Charles R. Anderson

On Sun, Aug 25, 2002 at 01:53:47PM -0400, Wesley Allen wrote: wallen> And Mandrake uses.....ALSA...oh well, I'll find another outlet! wallen> Thanks anyway gang! Not yet... Check if you have the OSS compatibility modules loaded: /sbin/lsmod | grep oss You should see something like this: snd-seq-oss 27552 0 (autoclean) snd-seq-midi-event 5440 0 (autoclean) [snd-seq-oss] snd-seq 43596 2 (autoclean) [snd-seq-oss snd-seq-midi-event] snd-pcm-oss 41540 0 (autoclean) snd-mixer-oss 10944 0 (autoclean) [snd-pcm-oss] snd-pcm 68192 0 [snd-pcm-oss snd-intel8x0] snd-seq-device 5480 0 [snd-seq-oss snd-seq snd-rawmidi] snd 36200 4 [snd-seq-oss snd-seq-midi-event snd-seq snd-pcm-oss snd-mixer-oss snd-intel8x0 snd-pcm snd-timer snd-ac97-codec snd-mpu401-uart snd-rawmidi snd-seq-device] The 'seq' devices are the ones that run the sequencer. Never used devfs, but I've always had to make the sound devices for ALSA manually: cd /usr/share/doc/alsa-driver-0.9.0rc2 ./snddevices That will create /dev/sequencer for you, too. Also, make sure your sequencer is unmuted in alsamixer. -- 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

Aug. 25, 2002

Re: [Wlug] /dev/sequencer problems

by Wesley Allen

And Mandrake uses.....ALSA...oh well, I'll find another outlet! Thanks anyway gang! Wes On Sun, 2002-08-25 at 13:21, Michael Frysinger wrote: > umm, well, if you use kernel sound drivers, make sure > you have midi support enabled. if you're alsa or something, > g'luck, cause i'm not touching alsa ;) > -mike > > ----- Original Message ----- > From: "Wesley Allen" <wallen(a)charter.net> > To: <wlug(a)mail.wlug.org> > Sent: Sunday, August 25, 2002 06:11 > Subject: Re: [Wlug] /dev/sequencer problems > > > > Yes, I'm using devf, and devfsd.conf exists, although it's mandrake's > > default. > > > > No, /dev/sequencer doesn't exist; should've checked that first. How > > would I see that it's created and bound to my sound-card? > > > > Wes > > > > On Sat, 2002-08-24 at 21:48, Michael Frysinger wrote: > > > does the device file exist ? > > > if it does, are the permissions set properly on it ? > > > are you using devfs ? if you are, did you set up > > > /etc/devfsd.conf ? > > > -mike > > > > > > ----- Original Message ----- > > > From: "Wesley T Allen" <wallen(a)charter.net> > > > To: "wlug" <wlug(a)mail.wlug.org> > > > Sent: Friday, August 23, 2002 21:28 > > > Subject: [Wlug] /dev/sequencer problems > > > > > > > > > > Hi all, > > > > I'm full of problems this week. Hopefully this'll have a successful > > > ending as well! > > > > > > > > Any time I try to open a midi file, I get an error "can't open > > > /dev/sequencer" it doesn't matter what desktop I'm in (sometimes I hate > > > arts); and I can't figure this out. Anyone got an idea? > > > > > > > > Wes > > > > > > > > _______________________________________________ > > > > 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 > > > > > -- > > This message may be digitally signed. > > For my public key, e-mail me a request. > > > > > > _______________________________________________ > > 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 > -- This message may be digitally signed. For my public key, e-mail me a request.

Aug. 25, 2002

Re: [Wlug] /dev/sequencer problems

by Michael Frysinger

umm, well, if you use kernel sound drivers, make sure you have midi support enabled. if you're alsa or something, g'luck, cause i'm not touching alsa ;) -mike ----- Original Message ----- From: "Wesley Allen" <wallen(a)charter.net> To: <wlug(a)mail.wlug.org> Sent: Sunday, August 25, 2002 06:11 Subject: Re: [Wlug] /dev/sequencer problems > Yes, I'm using devf, and devfsd.conf exists, although it's mandrake's > default. > > No, /dev/sequencer doesn't exist; should've checked that first. How > would I see that it's created and bound to my sound-card? > > Wes > > On Sat, 2002-08-24 at 21:48, Michael Frysinger wrote: > > does the device file exist ? > > if it does, are the permissions set properly on it ? > > are you using devfs ? if you are, did you set up > > /etc/devfsd.conf ? > > -mike > > > > ----- Original Message ----- > > From: "Wesley T Allen" <wallen(a)charter.net> > > To: "wlug" <wlug(a)mail.wlug.org> > > Sent: Friday, August 23, 2002 21:28 > > Subject: [Wlug] /dev/sequencer problems > > > > > > > Hi all, > > > I'm full of problems this week. Hopefully this'll have a successful > > ending as well! > > > > > > Any time I try to open a midi file, I get an error "can't open > > /dev/sequencer" it doesn't matter what desktop I'm in (sometimes I hate > > arts); and I can't figure this out. Anyone got an idea? > > > > > > Wes > > > > > > _______________________________________________ > > > 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 > > > -- > This message may be digitally signed. > For my public key, e-mail me a request. > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

Aug. 25, 2002

Re: [Wlug] /dev/sequencer problems

by Wesley Allen

Yes, I'm using devf, and devfsd.conf exists, although it's mandrake's default. No, /dev/sequencer doesn't exist; should've checked that first. How would I see that it's created and bound to my sound-card? Wes On Sat, 2002-08-24 at 21:48, Michael Frysinger wrote: > does the device file exist ? > if it does, are the permissions set properly on it ? > are you using devfs ? if you are, did you set up > /etc/devfsd.conf ? > -mike > > ----- Original Message ----- > From: "Wesley T Allen" <wallen(a)charter.net> > To: "wlug" <wlug(a)mail.wlug.org> > Sent: Friday, August 23, 2002 21:28 > Subject: [Wlug] /dev/sequencer problems > > > > Hi all, > > I'm full of problems this week. Hopefully this'll have a successful > ending as well! > > > > Any time I try to open a midi file, I get an error "can't open > /dev/sequencer" it doesn't matter what desktop I'm in (sometimes I hate > arts); and I can't figure this out. Anyone got an idea? > > > > Wes > > > > _______________________________________________ > > 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 > -- This message may be digitally signed. For my public key, e-mail me a request.

Aug. 25, 2002

Re: [Wlug] /dev/sequencer problems

by Michael Frysinger

does the device file exist ? if it does, are the permissions set properly on it ? are you using devfs ? if you are, did you set up /etc/devfsd.conf ? -mike ----- Original Message ----- From: "Wesley T Allen" <wallen(a)charter.net> To: "wlug" <wlug(a)mail.wlug.org> Sent: Friday, August 23, 2002 21:28 Subject: [Wlug] /dev/sequencer problems > Hi all, > I'm full of problems this week. Hopefully this'll have a successful ending as well! > > Any time I try to open a midi file, I get an error "can't open /dev/sequencer" it doesn't matter what desktop I'm in (sometimes I hate arts); and I can't figure this out. Anyone got an idea? > > Wes > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

Aug. 25, 2002

python regular expressions

by Brad Noyes

Hi All, I'm starting to learn python. I was looking for a python equivalent to a perl regular expression such as $_ = "FreeBSD"; /(.*)BSD/; where $1 would get what ever is between '(...)', 'Free' in this case. Is there a way i can make use of the () regex operator in python? I can't seem to find an equivalent in python's regex module (re). Thanks, --brad

Aug. 24, 2002

/dev/sequencer problems

by Wesley T Allen

Hi all, I'm full of problems this week. Hopefully this'll have a successful ending as well! Any time I try to open a midi file, I get an error "can't open /dev/sequencer" it doesn't matter what desktop I'm in (sometimes I hate arts); and I can't figure this out. Anyone got an idea? Wes

Aug. 23, 2002

RE: [Wlug] orinoco driver

by Wesley Allen

can you edit the file directly with emacs or vi? Wes On Fri, 2002-08-23 at 15:21, Haines, Charles Allen wrote: > I've got a question relating to this. I've got a netgear wireless card also. The card is detected and i can plug and play with it but I can't seem to get it set and essid. First off, I'm not sure which config it reading from /etc/pcmcia/wireless.opts. I've tried manually configuring it with iwconfig, it accepts the WEIP key, however it will not accept my essid. I've tried typing iwconfig essid "WPI-Wireless-Network", but it doesn't seem to keep it. Once I put it in and type iwconfig again, it says ESSID="". Anyone have any ideas. I'm using gentoo linux with kernel 2.4.19. > > > -----Original Message----- > From: Andy Stewart [mailto:andystewart@attbi.com] > Sent: Thu 8/22/2002 11:20 PM > To: wlug(a)mail.wlug.org > Cc: > Subject: Re: [Wlug] orinoco driver > > > > > Hi Wes, > > I discovered on my laptop that I had to insure that my wireless card was > listed in /etc/pcmcia/config or things didn't work. (Although I use SuSE > 8.0, I believe the description below is distribution agnostic). > > Try this as root: > > # cardctl ident > > Note the "manfid" line. Next, check /etc/pcmcia/config and see if a card with > an entry matching the manfid is present. In my case, there was no entry so I > added one thus: > > card "Andy's Linksys Wireless" > manfid 0x0274, 0x1613 > bind "orinoco_cs" > > The card string seems to be arbitrary text. The manfid comes from "cardctl > ident", and the bind is to a kernel module. I have hotplugging services > running, so when I plug in my wireless adapter, it automagically loads the > kernel module(s), starts the net, sets up routing, etc. > > Give it a try and let us know how it goes! > > Later, > > Andy > > -- > Andy Stewart, Founder > Worcester Linux Users' Group > Worcester, MA USA > http://www.wlug.org > > > _______________________________________________ > 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 > -- This message may be digitally signed. For my public key, e-mail me a request.

Aug. 23, 2002

RE: [Wlug] orinoco driver

by Haines, Charles Allen

I've got a question relating to this. I've got a netgear wireless card also. The card is detected and i can plug and play with it but I can't seem to get it set and essid. First off, I'm not sure which config it reading from /etc/pcmcia/wireless.opts. I've tried manually configuring it with iwconfig, it accepts the WEIP key, however it will not accept my essid. I've tried typing iwconfig essid "WPI-Wireless-Network", but it doesn't seem to keep it. Once I put it in and type iwconfig again, it says ESSID="". Anyone have any ideas. I'm using gentoo linux with kernel 2.4.19. -----Original Message----- From: Andy Stewart [mailto:andystewart@attbi.com] Sent: Thu 8/22/2002 11:20 PM To: wlug(a)mail.wlug.org Cc: Subject: Re: [Wlug] orinoco driver Hi Wes, I discovered on my laptop that I had to insure that my wireless card was listed in /etc/pcmcia/config or things didn't work. (Although I use SuSE 8.0, I believe the description below is distribution agnostic). Try this as root: # cardctl ident Note the "manfid" line. Next, check /etc/pcmcia/config and see if a card with an entry matching the manfid is present. In my case, there was no entry so I added one thus: card "Andy's Linksys Wireless" manfid 0x0274, 0x1613 bind "orinoco_cs" The card string seems to be arbitrary text. The manfid comes from "cardctl ident", and the bind is to a kernel module. I have hotplugging services running, so when I plug in my wireless adapter, it automagically loads the kernel module(s), starts the net, sets up routing, etc. Give it a try and let us know how it goes! Later, Andy -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org _______________________________________________ Wlug mailing list Wlug(a)mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug

Aug. 23, 2002

Re: [Wlug] Stupid Hardware Clock Tricks, aka: WTF?

by Theo Van Dinter

On Wed, Aug 21, 2002 at 07:53:33PM -0400, Theo Van Dinter wrote: > it got funky, but I know what you're saying. I'll test externally after > dinner. Ok, so I got caught up after dinner ... ;) I did go and change the BIOS settings again, around 11pm on Wednesday. The problem then stayed away until ~4:12am on the 23rd. > I suggest writing down the value, counting five minutes with an EXTERNAL > clock, such as a stopwatch, and then writing down the value again. > (value2 - value1) / (60*5) should equal about 100. Ok, here we go: (date as reported from different system) Fri Aug 23 09:50:26 EDT 2002 CPU0 0: 13720765 XT-PIC timer 1: 3475 XT-PIC keyboard 2: 0 XT-PIC cascade 4: 753652 XT-PIC serial 8: 1 XT-PIC rtc 10: 320822 XT-PIC eth0, eth1 11: 996123 XT-PIC 3ware Storage Controller 15: 190389 XT-PIC ncr53c8xx NMI: 0 LOC: 13720778 ERR: 4588 MIS: 0 Fri Aug 23 10:28:45 EDT 2002 CPU0 0: 13950661 XT-PIC timer 1: 3475 XT-PIC keyboard 2: 0 XT-PIC cascade 4: 761173 XT-PIC serial 8: 1 XT-PIC rtc 10: 326570 XT-PIC eth0, eth1 11: 1008701 XT-PIC 3ware Storage Controller 15: 190389 XT-PIC ncr53c8xx NMI: 0 LOC: 13950673 ERR: 4622 MIS: 0 The first thing I notice is that int 4 is getting hit quite a bit, and I have no idea why. The device hooked up to that serial port is a UPS, and shouldn't be generating so many interrupts. Hmmm. Anyway, between the two times is 38:19, or 2299 seconds. So: (13950661-13720765) / 2299 = 99.9982601130927 So that part seems ok. :| -- Randomly Generated Tagline: That is a known bug in 5.00550. Either an upgrade or a downgrade will fix it. -- Larry Wall in <6vu1vo%2489c(a)kiev.wall.org>

Aug. 23, 2002

Re: [Wlug] orinoco driver

by Wesley Allen

Andy, I just typed the pass-phrase into my router's config utility; since it only does up to 128-bit, I don't have to worry about 256! So I got the key and put that in /etc/network-scripts/eth1-config (after testing it by putting it in iwconfig) and it works. I didn't want to send a plain-text passphrase! But it WORKS! Wes On Fri, 2002-08-23 at 07:58, Andy Stewart wrote: > > Hi Wes, > > I discovered that I could only get 64 and 128 bit WEP working. Although my > hardware allegedly supports up to 256 bit WEP, I was unsuccessful in making > it work. > > I also discovered that typing a pass phrase on a Windows based appliance would > yield a different hex string than typing the same pass phrase on Linux. So, > what I did was to pick my pass phrase, type it into one machine, and then > copy the resulting hex code directly to the other machine ("machine" meaning > access point, Linux wireless software, etc). > > On my system, the hex string is coded in /etc/sysconfig/network/wireless. I'm > not sure whether that is a SuSE specific file. The syntax of the important > line is: > > WIRELESS_KEY="s:xxxxx" > > where the "s:" indicates a string (the pass phrase) and the xxxx are the > characters. For 64 bit encryption, you need 5 characters, while with 128 bit > encryption, you need 13 characters. > > Have fun! > > Andy > > -- > Andy Stewart, Founder > Worcester Linux Users' Group > Worcester, MA USA > http://www.wlug.org > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > -- This message may be digitally signed. For my public key, e-mail me a request.

Aug. 23, 2002

Re: [Wlug] LUG's rule

by Andy Stewart

On Friday 23 August 2002 6:52 am, Wesley Allen wrote: > Gang, can I just tell you how much I love the Linux community. You > figure stuff out part way, and the community fills in the gaps! > > orinoco_cs is loaded, and wep is FINALLY enabled on my wlan! > > Thank you! > > Wes Way to go, Wes. Congratulations! Later, Andy -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org

Aug. 23, 2002

Re: [Wlug] orinoco driver

by Andy Stewart

Hi Wes, I discovered that I could only get 64 and 128 bit WEP working. Although my hardware allegedly supports up to 256 bit WEP, I was unsuccessful in making it work. I also discovered that typing a pass phrase on a Windows based appliance would yield a different hex string than typing the same pass phrase on Linux. So, what I did was to pick my pass phrase, type it into one machine, and then copy the resulting hex code directly to the other machine ("machine" meaning access point, Linux wireless software, etc). On my system, the hex string is coded in /etc/sysconfig/network/wireless. I'm not sure whether that is a SuSE specific file. The syntax of the important line is: WIRELESS_KEY="s:xxxxx" where the "s:" indicates a string (the pass phrase) and the xxxx are the characters. For 64 bit encryption, you need 5 characters, while with 128 bit encryption, you need 13 characters. Have fun! Andy -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org

Aug. 23, 2002

LUG's rule

by Wesley Allen

Gang, can I just tell you how much I love the Linux community. You figure stuff out part way, and the community fills in the gaps! orinoco_cs is loaded, and wep is FINALLY enabled on my wlan! Thank you! Wes -- This message may be digitally signed. For my public key, e-mail me a request.

Aug. 23, 2002

Re: [Wlug] orinoco driver

by Wesley Allen

Andy, Worked like a charm. There was an entry with my manfid in /etc/pcmcia/config and the bound driver was wvlan_cs; I switched it to orinoco_cs and, taking the cheesy way of rebooting, the network came up with the orinoco driver! Now I need to see if I can get wep working! Thanks, I love learning new tricks. Wes On Thu, 2002-08-22 at 23:20, Andy Stewart wrote: > > Hi Wes, > > I discovered on my laptop that I had to insure that my wireless card was > listed in /etc/pcmcia/config or things didn't work. (Although I use SuSE > 8.0, I believe the description below is distribution agnostic). > > Try this as root: > > # cardctl ident > > Note the "manfid" line. Next, check /etc/pcmcia/config and see if a card with > an entry matching the manfid is present. In my case, there was no entry so I > added one thus: > > card "Andy's Linksys Wireless" > manfid 0x0274, 0x1613 > bind "orinoco_cs" > > The card string seems to be arbitrary text. The manfid comes from "cardctl > ident", and the bind is to a kernel module. I have hotplugging services > running, so when I plug in my wireless adapter, it automagically loads the > kernel module(s), starts the net, sets up routing, etc. > > Give it a try and let us know how it goes! > > Later, > > Andy > > -- > Andy Stewart, Founder > Worcester Linux Users' Group > Worcester, MA USA > http://www.wlug.org > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > -- This message may be digitally signed. For my public key, e-mail me a request.

Aug. 23, 2002

Re: [Wlug] orinoco driver

by Andy Stewart

Hi Wes, I discovered on my laptop that I had to insure that my wireless card was listed in /etc/pcmcia/config or things didn't work. (Although I use SuSE 8.0, I believe the description below is distribution agnostic). Try this as root: # cardctl ident Note the "manfid" line. Next, check /etc/pcmcia/config and see if a card with an entry matching the manfid is present. In my case, there was no entry so I added one thus: card "Andy's Linksys Wireless" manfid 0x0274, 0x1613 bind "orinoco_cs" The card string seems to be arbitrary text. The manfid comes from "cardctl ident", and the bind is to a kernel module. I have hotplugging services running, so when I plug in my wireless adapter, it automagically loads the kernel module(s), starts the net, sets up routing, etc. Give it a try and let us know how it goes! Later, Andy -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org

Aug. 23, 2002

orinoco driver

by Wesley Allen

Hi all, hope the BBQ went well, sorry I couldn't come (I was picking up my Brother-In-Law at Logan...sigh, one day I'll get to a meeting). I've got a netgear wifi card that works great in Mandrake Linux, with the exception of wep (I know, it's cracked). In doing some research on the card and the kernel module that loads wvlan_cs, I have found out that this module has been replaced (by and large) by orinoco_cs, which I understand to be more functional (i.e. maybe I can get wep working?). I tried modprobe -r wvlan_cs and modprobe orinoco_cs but it won't bind to my pcmcia card. So I figured, "Well, maybe my card is just one that can't use the newer driver..." WRONG! Just to see what it was like, I download Knoppix, burned it onto a cd, and booted it up. Guess what driver loaded? orinoco_cs!! And it worked well too. Well, since Knoppix is a cd-boot, run in memory distro; I'm not changing to it anytime soon. So I'm going to use this opportunity to learn something new. How can I bind the orinoco driver to my card? Wes -- This message may be digitally signed. For my public key, e-mail me a request.

Aug. 23, 2002

WLUG BBQ

by Andy Stewart

HI gang, I'm running late. I'm leaving my house now for the BBQ. I'll see ya there around 6:30 - 6:45 PM. Later, Andy -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org

Aug. 22, 2002