Linux-Hardware Digest #228, Volume #9 Wed, 20 Jan 99 11:13:44 EST
Contents:
Re: K6-400 "kernel paging request" errors ("David R. Bergstein")
Re: SMC 1211TX PCI ethernet in linux (John Thompson)
Re: Linux and IDE (ATA) Hard Drives > 8.4 GB (Wolfgang Viechtbauer)
Re: AMD K6-2 66MHz, freeze on install of 5.2 ("Richard J Graner")
SCSI Problem (AIC-78xx) (Jean-Baptiste Jacquemard)
Re: Linux keyboard? (For emacs use) (Ilya)
Problems setting up SoundBlaster AWE64 Gold on RH 5.2 (John Welch)
Re: lexmark printer 7000 unterstuetzt ??? (Henryk Paluch)
Re: Ram Detection (Jim Adams)
Re: K6-400 "kernel paging request" errors (Stephen Jenuth)
Linux compatible modems (Ryan Lamb)
----------------------------------------------------------------------------
From: "David R. Bergstein" <[EMAIL PROTECTED]>
Crossposted-To: linux.dev.kernel,comp.os.linux.development.system,comp.os.linux.misc
Subject: Re: K6-400 "kernel paging request" errors
Date: Wed, 20 Jan 1999 08:13:13 -0500
If it helps at all, I am also seeing similar paging request errors under
linux 2.0.36 with an AMD K6-200 and 128MB RAM. I will need to change
my syslog.conf to obtain a dump next time it happens (will post).
[EMAIL PROTECTED] wrote:
>
> Suffering from an unstable system.
> K6-400 (stepping 12), Motherboard FIC PA-2013 (VIA MP3),
> 256 MB Ram (PC-100), (the board allows to downclock the RAM to 66 Mhz, what I
> did),
> AGP Matrox G200, 2 SCSI-Controller, EATA-DPT (only Disks)
> and ncr53c825 (DDS-3, CDROM ).
> RedHat 5.2 Kernel 2.0.36 and I tried as well all 2.2.0-preXX. the last
> 2.2.0-pre7ac2.
> The system keeps chrashing.
>
> I am trying to fix the system now since christmas. Getting frustrated....
>
> Any ideas, suggestions??
>
> Thanks in advance
>
> Mario Dix
>
> This is from 2.0.36:
>
> Unable to handle kernel paging request at virtual address e8f7ce98
> current->tss.cr3 = 083ac000, %cr3 = 083ac000
> *pde = 00000000
> Oops: 0000
> CPU: 0
> EIP: 0010:[<00125af0>]
> EFLAGS: 00010202
> eax: 28f7ce98 ebx: 08c30814 ecx: 00000400 edx: 00000025
> esi: 00000814 edi: 00067831 ebp: 00000400 esp: 0313de68
> ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
> Process tar (pid: 3707, process nr: 53, stackpage=0313d000)
> Stack: 08c3f398 00067831 00000814 00000002 00000000 00000025 0012702d 00000814
> 00067831 00000400 0313df18 00002484 00000000 0dfddf00 00067831 00000814
> 00000100 08c3f498 036c0814 00000000 08c3f498 08c3f418 036cf918 0313df14
> Call Trace: [<0012702d>] [<001274af>] [<0011d25c>] [<0011d341>] [<0011d6b4>]
> [<00123c70>] [<0010a941
> >]
> Code: 39 38 75 24 66 39 58 04 75 1e 39 68 20 74 22 56 e8 17 f9 ff
> Unable to handle kernel paging request at virtual address e8f7ce98
> current->tss.cr3 = 041b8000, %cr3 = 041b8000
> *pde = 00000000
> Oops: 0000
> CPU: 0
> EIP: 0010:[<00125af0>]
> EFLAGS: 00010202
> eax: 28f7ce98 ebx: 00080814 ecx: 00000814 edx: 00000025
> esi: 00000814 edi: 00086831 ebp: 00000400 esp: 0313dddc
> ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
> Process tar (pid: 3708, process nr: 53, stackpage=0313d000)
> Stack: 00086831 03130814 00000400 00086831 08975818 00000025 00126352 00000814
> 00086831 00000400 00086831 0313def4 001d25a0 00086831 00000001 00154cec
> 00000814 00086831 00000400 00000000 00086831 00000001 0df16b00 00000400
> Call Trace: [<00126352>] [<00154cec>] [<0015534c>] [<001555d5>] [<00153905>]
> [<00156845>] [<0012c414
> >]
> [<0011d7f2>] [<00123deb>] [<0010a941>]
> Code: 39 38 75 24 66 39 58 04 75 1e 39 68 20 74 22 56 e8 17 f9 ff
> general protection: 0000
> CPU: 0
> EIP: 0010:[<00125af0>]
> EFLAGS: 00013286
> eax: 88f0e018 ebx: 0dbf0811 ecx: 00000400 edx: 0000008c
> esi: 00000811 edi: 002f889d ebp: 00000400 esp: 0ee6be8c
> ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
> Process X (pid: 384, process nr: 4, stackpage=0ee6b000)
> Stack: 0dbff898 002f889d 00000811 00000001 00000000 0000008c 0012702d 00000811
> 002f889d 00000400 0ee6bf3c 00000004 00000000 0dfdc800 002f889d 00000811
> 00000100 0dbff918 00000811 00000000 0dbff918 0015638b 0df10400 0ee6bf38
> Call Trace: [<0012702d>] [<0015638b>] [<001274af>] [<0011d83e>] [<0011d91d>]
> [<00123c70>] [<0010a941
> >]
> Code: 39 38 75 24 66 39 58 04 75 1e 39 68 20 74 22 56 e8 17 f9 ff
> general protection: 0000
> CPU: 0
> EIP: 0010:[<00125af0>]
> EFLAGS: 00010286
> eax: 88f0e018 ebx: 06850811 ecx: 00000400 edx: 0000008c
> esi: 00000811 edi: 0000689d ebp: 00000400 esp: 04c02e60
> ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
> Process m4 (pid: 3762, process nr: 47, stackpage=04c02000)
> Stack: 06851b18 0000689d 00000811 00000001 00000000 0000008c 0012702d 00000811
> 0000689d 00000400 04c02f10 00000044 00000000 0e321c00 0000689d 00000811
> 00000100 06851898 06850811 00000000 06851898 00154ee1 06851518 04c02f0c
> Call Trace: [<0012702d>] [<00154ee1>] [<001274af>] [<0011db3f>] [<0011dc39>]
> [<0011b1f7>] [<0011b0f4
> >]
> [<00111b48>] [<00111a2c>] [<0011414e>] [<0010aaa4>]
> Code: 39 38 75 24 66 39 58 04 75 1e 39 68 20 74 22 56 e8 17 f9 ff
>
> -----------== Posted via Deja News, The Discussion Network ==----------
> http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
--
David R. Bergstein
Systems Engineer and Blues Musician
Rockville, MD
===========================================================================
[EMAIL PROTECTED] [EMAIL PROTECTED]
SE & Blues Musician Home Page Heart of Blue - Playin' the Blues for
You!
http://www.erols.com/dbergst http://heartofblue.com
===========================================================================
------------------------------
From: [EMAIL PROTECTED] (John Thompson)
Subject: Re: SMC 1211TX PCI ethernet in linux
Date: Wed, 20 Jan 1999 04:09:27 GMT
Reply-To: [EMAIL PROTECTED]
In <781tvl$pfu$[EMAIL PROTECTED]>, [EMAIL PROTECTED] writes:
>In article <c1.2c.2PLxcW$[EMAIL PROTECTED]>,
> [EMAIL PROTECTED] wrote:
>> I need help making the SMC 1211TX "EzCard" PCI ethernet adaptor
>> in my new machine work. Linux (RH v5.1, kernel 2.0.34) flatly
>> refuses to recognize it. Searching dejanews revealed only one
>> marginally pertinent article with vague references to making some
>> unspecified changes to Space.c and replacing ne.c with rtl8139.c
>> I can do the later but have no idea what changes to make in
>> Space.c. Anybody here able to make this card work for them?
>I saw the same article, and had the same problem with RH v5.2 claiming the
>device was busy...
>
>However, I tried updating the rtl8139.c driver to version 1.4, and now the
>card works great (RH v5.2 ships with version 0.99B).
>
>The latest version is available at
>http://cesdis.gsfc.nasa.gov/linux/drivers/rtl8139.c
I got the source, compiled it as a module but it still doesn't
want to work. Did you need to make any changes to Space.c as the
original author apparently did? Do you need some parameters to
pass to the module when it loads? I see in my /var/log/messages
that the card is now apparently being recognized, but I still get
these modprobe errors "can't locate module net-pf-5" and netstat
-r doesn't show the eth0 interface. I have this machine as
192.168.0.2 and my other machine as 192.168.0.1 and it seems to
work with OS/2 and Win98 but not linux (yet). I'm still pretty
new at this so forgive me if the answer seems obvious...
-John ([EMAIL PROTECTED])
------------------------------
From: Wolfgang Viechtbauer <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.questions
Subject: Re: Linux and IDE (ATA) Hard Drives > 8.4 GB
Date: Wed, 20 Jan 1999 04:11:40 +0000
Hey there ...
I just bought an IBM 10GB hd. I can make Linux see the whole 10GB (or
something like 9.6GB to be accurate, since IBM also practices the false
advertisement method). Also, Windows recognizes the total 10GB. BUT, I
cannot make Linux and Windows coexist. If I install Win first, then
Linux won't see the total 10GB, and if I install Linux first, Windows
does not see the total 10GB. I messed around with it for hours. It seems
that if you make the Windows partition with Linux fdisk, things might
actually work, but there was still a problem with an overlapping
partition. It's quite messy ... I ended up just using 8.4GB. It's okay
for right now, but I am a little disappointed that there seems to be
such an incompatibility (I am not blaming either OS here). Hopefully,
this will be resolved in the future. On /., a guy wrote about how you
have to use a different geometry when partitioning for Linux and Windows
... i.e. you use a different geometry for the two OS's. But then you
gotta make sure that things align evenly and that just got too
complicated for me. Anyway, read that post on /. ... it's quite
interesting.
--
Wolfgang Viechtbauer
[EMAIL PROTECTED]
------------------------------
From: "Richard J Graner" <[EMAIL PROTECTED]>
Subject: Re: AMD K6-2 66MHz, freeze on install of 5.2
Date: Wed, 20 Jan 1999 07:30:31 -0600
Thanks Ray for the info, I will re-up the info later tonight when I pull my
machine back out of the closet...
Ray wrote in message ...
>On Tue, 19 Jan 1999 23:38:17 -0600, Richard J Graner
<[EMAIL PROTECTED]>
> wrote:
>>Anyone have an idea why my PC locks up on install of the newest version of
>>Linux 5.2?
>
>What processor is that again? There is no K6-2 66 but maybe you mean a
K6-2
>266 or maybe a K6 266?
>
>Also, we really need to know more to even take a good guess. What is the
>rest of your hardware like? What distribution of Linux are you using (I'm
>guessing Red Hat since there is no "Linux 5.2")? Does your system work
with
>any other OS or maybe a different version of Linux? How far does the
>install process get? Are there any error messages?
>
>--
>Ray
>ray AT sonictech DOT net
------------------------------
From: Jean-Baptiste Jacquemard <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.questions,comp.os.linux
Subject: SCSI Problem (AIC-78xx)
Date: Wed, 20 Jan 1999 15:10:31 +0100
Reply-To: [EMAIL PROTECTED]
Hello,
I have installed RedHat 5.2 on a HP KAYAK XU computer.
The SCSI auto-probe module detects an AIC-7880 controler but at boot,
I have this message:
sqlsrv kernel: (scsi0) <Adaptec AIC-7880 Ultra SCSI host adapter> found
at PCI 8/0
sqlsrv kernel: (scsi0) Wide Channel, SCSI ID=7, 16/255 SCBs
sqlsrv kernel: (scsi0) Warning - detected auto-termination
sqlsrv kernel: (scsi0) Please verify driver detected settings are
correct.
sqlsrv kernel: (scsi0) If not, then please properly set the device
termination
sqlsrv kernel: (scsi0) in the Adaptec SCSI BIOS by hitting CTRL-A when
prompted
sqlsrv kernel: (scsi0) during machine bootup.
sqlsrv kernel: (scsi0) Cables present (Int-50 YES, Int-68 YES, Ext-68
YES)
sqlsrv kernel: (scsi0) Illegal cable configuration!! Only two
sqlsrv kernel: (scsi0) connectors on the SCSI controller may be in use
at a time!
sqlsrv kernel: (scsi0) Downloading sequencer code... 419 instructions
downloaded
sqlsrv kernel: (scsi1) <Adaptec AIC-7860 Ultra SCSI host adapter> found
at PCI 9/0
sqlsrv kernel: (scsi1) Narrow Channel, SCSI ID=7, 3/255 SCBs
sqlsrv kernel: (scsi1) Downloading sequencer code... 419 instructions
downloaded
sqlsrv kernel: <Adaptec AIC-7880 Ultra SCSI host adapter>
sqlsrv kernel: scsi1 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast
SCSI) 5.1.2/3.2.4
sqlsrv kernel: <Adaptec AIC-7860 Ultra SCSI host adapter>
sqlsrv kernel: scsi : 2 hosts.
sqlsrv kernel: Vendor: SEAGATE Model: ST34501W Rev: 8301
sqlsrv kernel: Type: Direct-Access ANSI SCSI
revision: 02
sqlsrv kernel: Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
sqlsrv kernel: (scsi0:0:0:0) Synchronous at 40.0 Mbyte/sec, offset 8.
sqlsrv kernel: SCSI device sda: hdwr sector= 512 bytes. Sectors= 8887200
[4339 MB] [4.3 GB]
sqlsrv kernel: sda: sda1 sda2 sda3
And the system boots correctly.
But when I work on large files, I often get
sqlsrv kernel: scsi : aborting command due to timeout : pid 3965, scsi0,
channel 0, id 0,
lun 0 Write (6) 16 29 81 02 00
sqlsrv kernel: SCSI host 0 abort (pid 3965) timed out - resetting
sqlsrv kernel: SCSI bus is being reset for host 0 channel 0.
sqlsrv kernel: (scsi0:0:0:0) Synchronous at 40.0 Mbyte/sec, offset 8.
And the system blocks about 1 minute.
What should I do???
--
Jean-Baptiste Jacquemard
========================
J. POLLAK & Cie SNC
4, rue de la Bourse
75002 PARIS
------------------------------
From: Ilya <[EMAIL PROTECTED]>
Subject: Re: Linux keyboard? (For emacs use)
Crossposted-To:
comp.os.linux.misc,comp.unix.questions,comp.unix.misc,comp.emacs,comp.editors
Date: 19 Jan 1999 20:43:22 +0800
In comp.editors David A. Rogers <[EMAIL PROTECTED]> wrote:
> On Tue, 19 Jan 1999 06:27:00 GMT, Joseph H Allen <[EMAIL PROTECTED]>
> speaketh saying:
> >In article <36a42292.0@calwebnnrp>, Ilya <[EMAIL PROTECTED]> wrote:
> >>I am interested in a "soft-touch" keyboard for a Linux workstation that has
> >>one Control key on the home row - by the "A" key or "Caps lock" key, instead
> >>of 2 Control keys on the bottom like on Windows keyboards. I would like to
> >>hear someone recommend a keyboard with these specifications.
> >
> >Remap the caps-lock key into the Ctrl key. Take a look at 'loadmap' and
> >/usr/lib/kbd/keytables/emacs.map
> As well as modmap for X11.
I truly appreciate your suggestions, but I'd rather get a real workstation
keyboard like the ones that Sun, HP, DEC and the rest of them sell, and not
mess with re-mapping.
------------------------------
From: John Welch <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Problems setting up SoundBlaster AWE64 Gold on RH 5.2
Date: Tue, 19 Jan 1999 22:59:25 -0500
Hello,
I have recently installed RedHat 5.2 on my PC (P166, 48MB). While
the install went smoothly, I have been struggling to set up some
things. I worked through getting an X-server running. It also took
some time for me to get my modem up and running. In each case by doing
research on newsgroups and HOWTO docs I was able to find my problems and
successfully configure these things. However, I am now stuck in trying
to get my Sound Blaster AWE64 Gold sound card working.
These are the steps that I have followed:
1. Read Sound Blaster AWE32/64 HOWTO. I basically ignored the section
on rebuilding the kernel because it is my understanding that these
modules are already built into this kernel (2.0.36).
2. Ran sndconfig program. This program found my card and correctly
identified it. It then said it was going to run a sound card test.
However an "isapnp error" window comes up saying:
LD setting verify failed.....
Try adding (VERIFYLD N) to top of your script
Error occurred executing request 'LD2' on or around
Line 324 --- Further action aborted
I click OK to this message and another window comes up saying:
Autoconfig failed now proceeding with manual config. (I click OK)
I step through the manual config but it comes right back to the isapnp
error screen. All I can do at this point is cancel out.
3. After exiting the sndconfig program I looked around and found a file
called 'soundcard' in the /etc/sysconfig directory. This file says that
it was created by the sndconfig program. The only active line
(non-commented) says "CARDTYPE = SB32"
4. I then edited the /etc/isapnp.conf file which also was created by
the sndconfig program. I added the (VERIFYLD N) to the top of the
script. I also looked at the IRQ, DMA, and I/O settings in each
section. These settings match exactly the settings from Windows 95
(where the card is working by the way).
5. I re-executed the command 'isapnp /etc/isapnp.conf'. When I do this
it sees Board 1 (my modem) and then says "Board CTl009/2547404 not
found" three times.
6. I then rebooted the PC to watch it go through the boot process.
When the system gets to the ISAPNP
Conf program it finds two boards, my modem and my soundcard.
7. Executing the command 'modprobe -a sound' returns nothing and when I
execute 'cat /proc/sndstat'
no devices show up.
I have searched the linux newsgroups and have found other problems
with the SB32/64 sound cards but nothing really similar to my problem.
Sorry for being so long winded but I wanted to include as much detail
as possible. Any comments or suggestions would be appreciated.
Thank You in Advance,
John
------------------------------
From: [EMAIL PROTECTED] (Henryk Paluch)
Subject: Re: lexmark printer 7000 unterstuetzt ???
Date: 20 Jan 1999 14:14:18 +0100
On Tue, 19 Jan 1999 21:32:57 +0100, marco heeg <[EMAIL PROTECTED]> wrote:
>hi all
>kann ich einen lexmark 7000 fotodrucker unter linux nutzen.
>es ist so ein GDI drucker ???
>Bis dann Marco
>
Yes Lexmark 7000 is "GDI" printer.
The key problem is that Lexmark won't publish protocol specification.
They consider it "copryrighted" :-(
There is currently only one chance: to guess & disassemble the protocol
and write the driver.
Good Luck
Henryk Paluch, [EMAIL PROTECTED]
------------------------------
From: Jim Adams <[EMAIL PROTECTED]>
Crossposted-To: linux.redhat.install,comp.os.linux.help
Subject: Re: Ram Detection
Date: Wed, 20 Jan 1999 08:52:57 -0600
The RH 5.2 install guide gives the following remedy.
In lilo.conf add this line at the end of the Linux boot section:
append="mem=xx" xx being the amount of RAM you have installed on your system.
digitalklown wrote:
> I have had 64M of RAM for quiet sometime, and with the old install of RedHat
> 5.1 it was detected when I upgraded, however when I did a clean install of
> 5.2, only 16M was detected.
>
> Through my minimal research I have found that by entering at LILO:
>
> linux mem=64M
>
> however only 16M is only still loaded....
>
> any suggestions......
------------------------------
From: Stephen Jenuth <[EMAIL PROTECTED]>
Subject: Re: K6-400 "kernel paging request" errors
Crossposted-To: linux.dev.kernel,comp.os.linux.development.system,comp.os.linux.misc
Date: Wed, 20 Jan 1999 15:10:47 GMT
In comp.os.linux.hardware David R. Bergstein <[EMAIL PROTECTED]> wrote:
I have run into these problems on a k6 266, and a k6 300. In both cases
I got rid of the systems because they seemed to be too much work to fix.
When they crashed they tended to leave the mounted file systems in a bit
of disarray.
On the k6 266, disabling the internal cache did the trick. Nothing else
seemed to work. (Disabling the internal cache was done in the include/asm/bugs.h).
In this case, I had a intel pentium 233mmx installed and things have worked
famously thereafter (it cost me $ 35 CDN or so extra). Curiously the system
worked well with windoze.
On the k6 300, I just returned the system to the vendor. I suppose I should
have tried various different timings for the ram, but I lost patience. This
system had some problems with windoze.
It may be something related to cooling. Things seemed to work OK for a time
and then all hell broke loose.
On the other hand, I have a k6-2/300 which works flawlessly with linux.
: If it helps at all, I am also seeing similar paging request errors under
: linux 2.0.36 with an AMD K6-200 and 128MB RAM. I will need to change
: my syslog.conf to obtain a dump next time it happens (will post).
: [EMAIL PROTECTED] wrote:
:>
:> Suffering from an unstable system.
:> K6-400 (stepping 12), Motherboard FIC PA-2013 (VIA MP3),
:> 256 MB Ram (PC-100), (the board allows to downclock the RAM to 66 Mhz, what I
:> did),
:> AGP Matrox G200, 2 SCSI-Controller, EATA-DPT (only Disks)
:> and ncr53c825 (DDS-3, CDROM ).
:> RedHat 5.2 Kernel 2.0.36 and I tried as well all 2.2.0-preXX. the last
:> 2.2.0-pre7ac2.
:> The system keeps chrashing.
:>
:> I am trying to fix the system now since christmas. Getting frustrated....
:>
:> Any ideas, suggestions??
:>
:> Thanks in advance
:>
:> Mario Dix
:>
:> This is from 2.0.36:
:>
:> Unable to handle kernel paging request at virtual address e8f7ce98
:> current->tss.cr3 = 083ac000, %cr3 = 083ac000
:> *pde = 00000000
:> Oops: 0000
:> CPU: 0
:> EIP: 0010:[<00125af0>]
:> EFLAGS: 00010202
:> eax: 28f7ce98 ebx: 08c30814 ecx: 00000400 edx: 00000025
:> esi: 00000814 edi: 00067831 ebp: 00000400 esp: 0313de68
:> ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
:> Process tar (pid: 3707, process nr: 53, stackpage=0313d000)
:> Stack: 08c3f398 00067831 00000814 00000002 00000000 00000025 0012702d 00000814
:> 00067831 00000400 0313df18 00002484 00000000 0dfddf00 00067831 00000814
:> 00000100 08c3f498 036c0814 00000000 08c3f498 08c3f418 036cf918 0313df14
:> Call Trace: [<0012702d>] [<001274af>] [<0011d25c>] [<0011d341>] [<0011d6b4>]
:> [<00123c70>] [<0010a941
:> >]
:> Code: 39 38 75 24 66 39 58 04 75 1e 39 68 20 74 22 56 e8 17 f9 ff
:> Unable to handle kernel paging request at virtual address e8f7ce98
:> current->tss.cr3 = 041b8000, %cr3 = 041b8000
:> *pde = 00000000
:> Oops: 0000
:> CPU: 0
:> EIP: 0010:[<00125af0>]
:> EFLAGS: 00010202
:> eax: 28f7ce98 ebx: 00080814 ecx: 00000814 edx: 00000025
:> esi: 00000814 edi: 00086831 ebp: 00000400 esp: 0313dddc
:> ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
:> Process tar (pid: 3708, process nr: 53, stackpage=0313d000)
:> Stack: 00086831 03130814 00000400 00086831 08975818 00000025 00126352 00000814
:> 00086831 00000400 00086831 0313def4 001d25a0 00086831 00000001 00154cec
:> 00000814 00086831 00000400 00000000 00086831 00000001 0df16b00 00000400
:> Call Trace: [<00126352>] [<00154cec>] [<0015534c>] [<001555d5>] [<00153905>]
:> [<00156845>] [<0012c414
:> >]
:> [<0011d7f2>] [<00123deb>] [<0010a941>]
:> Code: 39 38 75 24 66 39 58 04 75 1e 39 68 20 74 22 56 e8 17 f9 ff
:> general protection: 0000
:> CPU: 0
:> EIP: 0010:[<00125af0>]
:> EFLAGS: 00013286
:> eax: 88f0e018 ebx: 0dbf0811 ecx: 00000400 edx: 0000008c
:> esi: 00000811 edi: 002f889d ebp: 00000400 esp: 0ee6be8c
:> ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
:> Process X (pid: 384, process nr: 4, stackpage=0ee6b000)
:> Stack: 0dbff898 002f889d 00000811 00000001 00000000 0000008c 0012702d 00000811
:> 002f889d 00000400 0ee6bf3c 00000004 00000000 0dfdc800 002f889d 00000811
:> 00000100 0dbff918 00000811 00000000 0dbff918 0015638b 0df10400 0ee6bf38
:> Call Trace: [<0012702d>] [<0015638b>] [<001274af>] [<0011d83e>] [<0011d91d>]
:> [<00123c70>] [<0010a941
:> >]
:> Code: 39 38 75 24 66 39 58 04 75 1e 39 68 20 74 22 56 e8 17 f9 ff
:> general protection: 0000
:> CPU: 0
:> EIP: 0010:[<00125af0>]
:> EFLAGS: 00010286
:> eax: 88f0e018 ebx: 06850811 ecx: 00000400 edx: 0000008c
:> esi: 00000811 edi: 0000689d ebp: 00000400 esp: 04c02e60
:> ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
:> Process m4 (pid: 3762, process nr: 47, stackpage=04c02000)
:> Stack: 06851b18 0000689d 00000811 00000001 00000000 0000008c 0012702d 00000811
:> 0000689d 00000400 04c02f10 00000044 00000000 0e321c00 0000689d 00000811
:> 00000100 06851898 06850811 00000000 06851898 00154ee1 06851518 04c02f0c
:> Call Trace: [<0012702d>] [<00154ee1>] [<001274af>] [<0011db3f>] [<0011dc39>]
:> [<0011b1f7>] [<0011b0f4
:> >]
:> [<00111b48>] [<00111a2c>] [<0011414e>] [<0010aaa4>]
:> Code: 39 38 75 24 66 39 58 04 75 1e 39 68 20 74 22 56 e8 17 f9 ff
Best regards,
Stephen Jenuth
([EMAIL PROTECTED])
Quidquid latine dictum sit, altum viditur.
------------------------------
From: Ryan Lamb <[EMAIL PROTECTED]>
Subject: Linux compatible modems
Date: Tue, 19 Jan 1999 21:06:54 -0800
Could someone email me a list of modems that are known to be compatible
with RedHat5.2 My current 33.6 is not campatible with linux and I am
forced to use an older 14.4
Thank You,
Ryan Lamb [EMAIL PROTECTED]
--
If it doesn't work, use a bigger hammer. If it breaks, it needed fixing
anyway.
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list (and comp.os.linux.hardware) via:
Internet: [EMAIL PROTECTED]
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Hardware Digest
******************************
