Linux-Hardware Digest #564, Volume #13 Tue, 12 Sep 00 11:13:09 EDT
Contents:
Re: modems (winmodems?) (sideband)
Setting up an HP Deskjet 520. (Mark Andal)
Re: SB 16 ISA PnP: Alsa ok, Kernel not??? (Frank Steiner)
Re: Suse 6.4, disk: modules, driver: imm.o (Dieter Buricke)
Re: SB 16 ISA PnP: Alsa ok, Kernel not??? (sideband)
Linux and k7v irq ("Danilo")
Re: HP CDWriter SCSI support (Chris Rankin)
Re: SB 16 ISA PnP: Alsa ok, Kernel not??? (Dean Plude)
Info isdn. ("Gemini")
Re: Sounsblaster Pro doesn't work ("f.g.a.m.wouters")
Re: Zip 100 Parallel Port Drive (Kasper Dupont)
Re: which kernel for 486+16MB? ("Chan Chung Hang Christopher")
Re: SB 16 ISA PnP: Alsa ok, Kernel not??? (Frank Steiner)
Re: SB 16 ISA PnP: Alsa ok, Kernel not??? (Frank Steiner)
Re: SB 16 ISA PnP: Alsa ok, Kernel not??? (Frank Steiner)
Stumped. Any ideas? ("Fountainhead")
Re: which kernel for 486+16MB? ("Peter T. Breuer")
3Com 3c980C on Linux (Peter S F Luk)
Re: Stumped. Any ideas? (TekMate)
----------------------------------------------------------------------------
From: sideband <[EMAIL PROTECTED]>
Subject: Re: modems (winmodems?)
Date: Tue, 12 Sep 2000 06:19:12 -0400
Most, if not all, external serial modems are compatible with Linux.
-SSB
On or about Tue, 12 Sep 2000 08:53:53 GMT, Mike <[EMAIL PROTECTED]>,
using the forum comp.os.linux.hardware did say:
:Hi all, I'm looking for a new external modem, but I'm having trouble
:finding one that I can use with Linux, largely because all the modem
:manufacturers seem to put "Windows" under system requirements, leaving
:me uncertain as to whether or not they are winmodems. Are external
:modems generally not windmodems?
:
:I was looking at the USR Faxmodem (external), until I saw the line
:"Operating Systems Modem is compatible with Windows NT 4.0 (Windows
:2000 support expected)"
:
:Bah. Can anyone recommend a good external modem?
------------------------------
From: Mark Andal <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.help,comp.os.liunux.misc,comp.os.linux.setup
Subject: Setting up an HP Deskjet 520.
Date: Tue, 12 Sep 2000 10:20:49 GMT
Greetings,
So far I've used printtool and drakconf's printer setup. (Also made
sure I have the latest versions)
Both were pretty straightforward. But each time I try to print or test
print.
All that comes out is garbled. I few lines of junk and then nothing,.
This is not a stair-steeping problem I've seen what that looks like when
installing a different printer.
Any help on how to diagnose this would be appreciated.
This machine is a pure linux machine. There is no Win on this to see if
it works under Windows.
It does self test properly though.
Thanks.
Mark Andal
------------------------------
From: Frank Steiner <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: SB 16 ISA PnP: Alsa ok, Kernel not???
Date: Tue, 12 Sep 2000 13:22:14 +0200
sideband wrote:
> =
> Did you compile SB as a module, and include PnP support in the kernel?
=
Yes and yes :-)
-- =
Dipl.-Inform. Frank Steiner mailto:[EMAIL PROTECTED]
Lehrstuhl f. Programmiersprachen mailto:[EMAIL PROTECTED]
CAU Kiel, Olshausenstra=DFe 40 Phone: +49 431 880-7265, Fax: -7613
D-24098 Kiel, Germany http://www.informatik.uni-kiel.de/~fst=
/
------------------------------
From: Dieter Buricke <[EMAIL PROTECTED]>
Subject: Re: Suse 6.4, disk: modules, driver: imm.o
Date: Tue, 12 Sep 2000 13:20:19 +0200
Answer from myself:
It works, when you first load CD-ROM modules from modules-disk and choose
a parallel-port CD-ROM-drive (e.g. Freecom IQ). Before you can load that
module for the CD-ROM, the parport-modules will be load (look at console
3 with keys alt+F3) and that is it, what you need for the ZIP+ drive,
which you can than load from the SCSI-modules. You don't need to load the
CD-ROM module completely before.
Bye!
Dieter Buricke schrieb:
> Hi all,
>
> want to boot Suse Linux 6.4 from 'bootdisk' (floppy) and then load
> driver imm.o from disk 'modules' for parallel-port zip plus drive. It
> doesn't work.
>
> Which parameters I have to put?
>
> Thanks
>
> D.B.
--
Dieter Buricke (EDV)
DZA - Deutsches Zentrum fuer Altersfragen
(German Centre of Gerontology)
Manfred-von-Richthofen-Strasse 2
D - 12101 Berlin
Tel: (49) 30 - 78 60 42 67
Fax: (49) 30 - 7 85 43 50
http://www.dza.de
------------------------------
From: sideband <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: SB 16 ISA PnP: Alsa ok, Kernel not???
Date: Tue, 12 Sep 2000 07:31:00 -0400
Hrm... Well, you know.. gotta ask the stupid questions first. ::grin::
does SuSE have sndconfig, or something similar? Worked for me on
RedHat.
-SSB
On or about Tue, 12 Sep 2000 13:22:14 +0200, Frank Steiner
<[EMAIL PROTECTED]>, using the forum comp.os.linux.hardware
did say:
:sideband wrote:
:>
:> Did you compile SB as a module, and include PnP support in the kernel?
:
:Yes and yes :-)
------------------------------
From: "Danilo" <[EMAIL PROTECTED]>
Crossposted-To:
alt.comp.linux,alt.os.linux,comp.os.linux.help,linux.act.configs,linux.net
Subject: Linux and k7v irq
Date: Tue, 12 Sep 2000 09:47:28 +0200
Hi to all,
my problem is this, I have a motherboard k7v and a processor athlon 800, 256
mb of ram.
The problem is that linux recognizes me the peripheral pci (modem isdn, sb
Live !) but he doesn't succeed to take the irq for the pci cards, under
windows there is the driver of Irq Routing Script..... but for [linux]??
The error is "cannot rents irq for the resource" and "resource is busy"
for each hardware pci
Please help me,
I'm desperate
SyRiO On IrCnET
------------------------------
From: Chris Rankin <au.zipworld.com@{no.spam}rankinc>
Subject: Re: HP CDWriter SCSI support
Date: Tue, 12 Sep 2000 23:09:02 +1100
Duane wrote:
> I would suggest two changes. You don't need the ide-cd driver at all, so
> you can just say no to that in the kernel configuration. Leaving it as a
> module does not hurt anything, but you are never using it.
Yes I am; it's an IDE drive so I don't bother using SCSI emulation for
CD-ROMs. It's the SCSI CD-ROM support I don't use much.
> Also, if you
> compile ide-scsi and sr into the kernel, rather than as modules, you do
> not need any commands in modules.conf either.
No, see above. And I always compile as many systems as modules as I can
so that I can remove then from memory and then insert modified versions
with debugging code if I spot something I don't understand etc. This way
I don't have to reboot.
> I am pretty sure you do need the sr driver.
Nope; never use it. Yes, I know that I *CAN* use SCSI emulation for
everything but I prefer not to. The interesting thing is I don't need
the lilo parameter. Isn't it wonderful what you discover when you
experiment?
Chris
------------------------------
From: Dean Plude <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: SB 16 ISA PnP: Alsa ok, Kernel not???
Date: Tue, 12 Sep 2000 12:26:23 GMT
modprobe sb io=0x220 irq=5 dma=1 dma16=3 mpu_io=0x330
note you must pass parm to this module to work
Frank Steiner wrote:
> Hi,
>
> I've a strange problem with a Sounblaster 16 ISA PnP on SuSE 6.4.
> The card is detected by alsaconf, and everything works fine with
> the alsa drivers. But the kernel drivers (sb.o) refuses to detect
> the card (unfortunately, I need the kernel drivers for Quake I).
>
> In /proc/isapnp there are the following information:
>
> Card 1 'CTL00f0:Creative ViBRA16X PnP' PnP version 1.0 Product version 1.0
> Logical device 0 'CTL0043:Audio'
> Device is not active
> Active port 0x220,0x330,0x388
> Active IRQ 5 [0x2]
> Active DMA 1,3
> Resources 0
> Priority preferred
> Port 0x220-0x220, align 0x0, size 0x10, 16-bit address decoding
> Port 0x330-0x330, align 0x0, size 0x2, 16-bit address decoding
> Port 0x388-0x3f8, align 0x0, size 0x4, 16-bit address decoding
> IRQ 5 High-Edge
> DMA 1 8-bit byte-count compatible
> DMA 3 8-bit byte-count compatible
> Alternate resources 0:1
> ...
> etc.
>
> Ok, so I tried the following lines on the modules.conf file:
>
> alias char-major-14 sb
> post-install sb /sbin/modprobe "-k" "adlib_card"
> options sb io=0x220 irq=5 dma=1 dma16=3 mpu_io=0x330
> options adlib_card io=0x388
>
> After doing a depmod, I tried "modprobe sb" (after unloading
> the alsa driver of course), but got the following:
>
> /lib/modules/2.2.16/misc/sb.o: init_module: Device or resource busy
> /lib/modules/2.2.16/misc/sb.o: insmod /lib/modules/2.2.16/misc/sb.o failed
> /lib/modules/2.2.16/misc/sb.o: insmod sb failed
>
> The same when I try to specify irq etc. directly as parameter to modprobe.
> With "fuser" I've checked that no one is using the sound devices...
>
> When alsa is loaded, it shows the following information in /proc/asound:
>
>
> Sound Driver:3.8.1a-980706 (ALSA v0.5.5 emulation code)
> Kernel: Linux linux 2.2.14 #1 Sat Mar 25 00:45:35 GMT 2000 i686
> Config options: 0
>
> Installed drivers:
> Type 10: ALSA emulation
>
> Card config:
> Sound Blaster 16 at 0x220, irq 5, dma 1
>
> Audio devices:
> 0: DSP v4.16 (DUPLEX)
>
> Synth devices: NOT ENABLED IN CONFIG
>
> Midi devices:
> 0: MPU-401 (UART)
>
> Timers:
> 7: system timer
>
> Mixers:
> 0: CTL1745
>
> That all looks very fine to me, but why is the kernel driver
> refusing to detect the card???
>
> Has anyone an idea? I would really appreciate any help!!!
>
> Best regards,
> Frank
>
> --
> Dipl.-Inform. Frank Steiner mailto:[EMAIL PROTECTED]
> Lehrstuhl f. Programmiersprachen mailto:[EMAIL PROTECTED]
> CAU Kiel, Olshausenstra�e 40 Phone: +49 431 880-7265, Fax: -7613
> D-24098 Kiel, Germany http://www.informatik.uni-kiel.de/~fst/
------------------------------
From: "Gemini" <[EMAIL PROTECTED]>
Subject: Info isdn.
Date: Tue, 12 Sep 2000 14:30:07 +0200
Ho la linea isdn e volevo prendere un modem interno per andare a 64k. Come
faccio a sapere se funziona anche sotto linux?
Che caratteristche deve avere?
Esiste una lista di modem isdn che posso consultare prima dell'acquisto?
Grazie.
--
============================================================
Gemini
[EMAIL PROTECTED]
[EMAIL PROTECTED]
ICQ:35060193
Gemini Web
http://gabry80.supereva.it/index.htm
============================================================
------------------------------
From: "f.g.a.m.wouters" <[EMAIL PROTECTED]>
Subject: Re: Sounsblaster Pro doesn't work
Date: 12 Sep 2000 11:40:31 GMT
Rejean Beaudet <[EMAIL PROTECTED]> schreef in artikel
<[EMAIL PROTECTED]>...
> My .au (audio files) are working properly but not the .wav with the
> dsp.
>
> With Suse 6.4, i have tried the pnpdump and isapnp commands
> but this is not a pnp card, and in the manual, they only give an
> example for the soundblaster 16 configuration in /etc/conf.modules
> file (Chapter 12.3 of SUSE manual).
>
> here is the example given:
>
> alias char-major-14 sb
> post-install sb /sbin/modprobe "-k" "adlib_card"
> options sb io=0x220 irq=5 dma=1 dma16=5 mpu_io=0x330
> options adlib_card io=0x388 # FM synthetiser
>
> Here is what i've tried with my card with parameters : io=0x220 and
> 0x388 irq=5 dma=1
>
> alias char-major-14 sb
> post-install sb /sbin/modprobe "-k" "adlib_card"
> options sb io=0x220 irq=5 dma=1
> options adlib_card io=0x388 # FM synthetiser
>
> Maybe the adlib configuration is not good for the synthetiser. It was
> working in previous kernels when i had the Soundblaster Pro option in
> the menuconfig. Now it's a pain for me with this module configuration.
> Should i buy a PCI pnp card instead?? It's not worthing the time
> spent...
>
> Thanks for helping me
>
I don't know if the soundblaster pro has the same chip then the
soundblaster live?
The soundblaster live has the emu10k1 chip on it .
With the cd's of SUSE there is a package called emu10k1 if you install it
with YAST your soundcard will work.
Frans Wouters
------------------------------
From: Kasper Dupont <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc,comp.os.linux.development.system
Subject: Re: Zip 100 Parallel Port Drive
Date: Tue, 12 Sep 2000 14:57:24 +0200
[EMAIL PROTECTED] wrote:
>
> In comp.os.linux.hardware Michel Talon <[EMAIL PROTECTED]> wrote:
>
> > Sorry, had not seen this one, but i think SPP will be slow. EPP would be
> > better.
>
> Well, ZIP drives are known not to work well or at all with ECP.
The problem was not that the ZIP drive does not work with ECP.
The problem was that the ParIde system for Linux does not work
with ECP, which is also written in the documentation. However
EPP is faster than ECP, at least with my SparQ drive it is.
The speed for reading is as far as i remember:
SPP: less than 200 kb/sec
ECP under DOS: 300 kb/sec
EPP under DOS: 400 kb/sec
EPP under Linux: 500 kb/sec
For some reasons many new computers come with the BIOS default
set to SPP, does anyone have a very good explanation for that?
--
Kasper Dupont
------------------------------
From: "Chan Chung Hang Christopher" <[EMAIL PROTECTED]>
Subject: Re: which kernel for 486+16MB?
Date: Tue, 12 Sep 2000 20:57:17 +0800
Peter T. Breuer wrote in message <8ph6ke$uu9$[EMAIL PROTECTED]>...
>gLiTcH <[EMAIL PROTECTED]> wrote:
>: ram has nothing to do with the kernel size
>
>: the kernel has to fit within the 640k limit i believe, which has nothing
>
>You believe wrong, but some aspects of what you say are not entirely
>incorrect. A running kernel will occupy about 1.5 to 2MB nowadays.
Actually, gLiTcH is right. Due to the design of the 80386 processor (which
design is just extended for our Pentium II/III and compatibles) it has a
limit on the size of the first file it loads which is about 640k. That is
why it became necessary to use the modular loading of drivers after the
kernel has been loaded. That allows the driver code to be taken out of the
kernel (thus reducing size) and 'put' back in after the kernel has been
exploded into memory above the 1MB constraint of the 80386 real mode....blah
blah blah
>: of using 'make zImage' use 'make bzImage'
>
>No no no. This does not change the size of the kernel. It changes the
>method used to load it, so that it can support a larger image.
Actually the 'z' stands for gzip compression and 'bz' for bzip compression.
Bzip is a more powerful compression algorithm and therefore allows a larger
sized kernel image to be compressed till it is smaller than 640k than a gzip
compression would. You will notice that kernel images of zImage files
larger than 640k will invoke the message to use 'make bzImage'.
uwuh, I load linux on my 486 box and it only has 8 mb. I do remove a lot
of useless drivers and my kernel image is around 420k. Keep your image size
below 640k and it will boot and any Intel-compatible including 386 boxes.
Chris
------------------------------
From: Frank Steiner <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: SB 16 ISA PnP: Alsa ok, Kernel not???
Date: Tue, 12 Sep 2000 15:12:29 +0200
Dean Plude wrote:
> =
> modprobe sb io=3D0x220 irq=3D5 dma=3D1 dma16=3D3 mpu_io=3D0x330
> note you must pass parm to this module to work
=
Well, that should be done automatically by the entries
in modules.conf, but even with the parameters directly
passed to modprobe, it does not work... :-(
Best regards,
Frank
-- =
Dipl.-Inform. Frank Steiner mailto:[EMAIL PROTECTED]
Lehrstuhl f. Programmiersprachen mailto:[EMAIL PROTECTED]
CAU Kiel, Olshausenstra=DFe 40 Phone: +49 431 880-7265, Fax: -7613
D-24098 Kiel, Germany http://www.informatik.uni-kiel.de/~fst=
/
------------------------------
From: Frank Steiner <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: SB 16 ISA PnP: Alsa ok, Kernel not???
Date: Tue, 12 Sep 2000 15:14:42 +0200
sideband wrote:
> =
> Hrm... Well, you know.. gotta ask the stupid questions first. ::grin::
> =
> does SuSE have sndconfig, or something similar? Worked for me on
> RedHat.
=
No sndconfig, but there is a possibility in their new install tool
(yast2) which I've not used because I prefer the old, textmode-based-
everything-can-be-done-manually yast1 ;-)
But good idea anyway, I will see what yast2 does for me :-)
Best regards,
Frank
-- =
Dipl.-Inform. Frank Steiner mailto:[EMAIL PROTECTED]
Lehrstuhl f. Programmiersprachen mailto:[EMAIL PROTECTED]
CAU Kiel, Olshausenstra=DFe 40 Phone: +49 431 880-7265, Fax: -7613
D-24098 Kiel, Germany http://www.informatik.uni-kiel.de/~fst=
/
------------------------------
From: Frank Steiner <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: SB 16 ISA PnP: Alsa ok, Kernel not???
Date: Tue, 12 Sep 2000 15:17:49 +0200
yast2 automatically installs the alsa drivers only :-((
-- =
Dipl.-Inform. Frank Steiner mailto:[EMAIL PROTECTED]
Lehrstuhl f. Programmiersprachen mailto:[EMAIL PROTECTED]
CAU Kiel, Olshausenstra=DFe 40 Phone: +49 431 880-7265, Fax: -7613
D-24098 Kiel, Germany http://www.informatik.uni-kiel.de/~fst=
/
------------------------------
From: "Fountainhead" <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux.caldera,comp.os.linux.help,comp.os.linux.setup
Subject: Stumped. Any ideas?
Date: Tue, 12 Sep 2000 08:41:01 -0500
System:
HP Pavilion 8240 P266 32MB RAM 3GB HD
NetworkEverywhere NC100 card
Internet access (DSL) configured through Linksys router
O/S
COL 2.3 kernel 2.2.17 (just upgraded from 2.2.10) installed on /dev/hda1
Swap file on dev/hda2
No other O/S
Background:
Installed NIC but old kernel version did not like tulip and pci-scan modules
Upgraded kernel to 2.2.17 and then installed the netdriver package, courtesy
of Donald Becker/Scyld
Everything worked fine for a few minutes and then system crashed while
browsing
Only way to reboot system was to power off and on
Worked fine for a few minutes and crashed again while browsing
Even power cycle did not help
Booted using emergency diskette and commented out the above driver entries
in /etc/modules/default
System booted properly
Swap file was not being recognized so made the recommended changes
Uninstalled netdriver package and re-installed
Re-configured eth0
System worked fine for a few minutes and crashed again even though I was
using terminal-based ftp
Given that the system crashes a few minutes after boot, are there any
overheating issues, memory overruns, or something else perhaps that is being
exceeded that shouldn't be?
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: which kernel for 486+16MB?
Date: 12 Sep 2000 14:10:15 GMT
Chan Chung Hang Christopher <[EMAIL PROTECTED]> wrote:
: Peter T. Breuer wrote in message <8ph6ke$uu9$[EMAIL PROTECTED]>...
:>gLiTcH <[EMAIL PROTECTED]> wrote:
:>: ram has nothing to do with the kernel size
:>
:>: the kernel has to fit within the 640k limit i believe, which has nothing
:>
:>You believe wrong, but some aspects of what you say are not entirely
:>incorrect. A running kernel will occupy about 1.5 to 2MB nowadays.
: Actually, gLiTcH is right. Due to the design of the 80386 processor (which
No, he's wrong. Not only actually, but previously.
: design is just extended for our Pentium II/III and compatibles) it has a
: limit on the size of the first file it loads which is about 640k. That is
This is true, but does not imply that the kernel has to fit within
640K. Did you read what I wrote or are you on halucogens?
: why it became necessary to use the modular loading of drivers after the
No, this is false.
: kernel has been loaded. That allows the driver code to be taken out of the
: kernel (thus reducing size) and 'put' back in after the kernel has been
This is nonsense.
: exploded into memory above the 1MB constraint of the 80386 real mode....blah
: blah blah
This is total nonsense.
:>: of using 'make zImage' use 'make bzImage'
:>
:>No no no. This does not change the size of the kernel. It changes the
:>method used to load it, so that it can support a larger image.
: Actually the 'z' stands for gzip compression and 'bz' for bzip compression.
And so is that total nonsense, as well as being false.
: Bzip is a more powerful compression algorithm and therefore allows a larger
This is true.
: sized kernel image to be compressed till it is smaller than 640k than a gzip
This is false. The bzImage files are compressed with gzip, not bzip.
Where did you get such an idea from!
: compression would. You will notice that kernel images of zImage files
: larger than 640k will invoke the message to use 'make bzImage'.
This is false. The limit is about 510K.
: uwuh, I load linux on my 486 box and it only has 8 mb. I do remove a lot
So do I.
: of useless drivers and my kernel image is around 420k. Keep your image size
Mine is well below that.
: below 640k and it will boot and any Intel-compatible including 386 boxes.
This is total irrelevant nonsense.
I suggest you go read a book on something. Anything. To learn about the
DEcompression technique used in the kernel both in its zImage and
bzImage formats, I suggest Documentation/kbuild/commands.txt. I quote:
Note: the difference between 'zImage' files and 'bzImage' files is that
'bzImage' uses a different layout and a different loading algorithm,
and thus has a larger capacity. Both files use gzip compression.
The 'bz' in 'bzImage' stands for 'big zImage', not for 'bzip'!
Peter
------------------------------
From: Peter S F Luk <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.networking
Subject: 3Com 3c980C on Linux
Date: 12 Sep 2000 14:19:09 GMT
Dear All,
Have any tried the above NIC in Linux?? I want to use the VLAN feature
of this network but I don't know whether 3Com's Linux driver can
support this feature or not. Thanks for any sharing
Rgds.
--
Pls remove NOSPAM. from my email address to email me!!
------------------------------
From: TekMate <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux.caldera,comp.os.linux.help,comp.os.linux.setup
Subject: Re: Stumped. Any ideas?
Date: Tue, 12 Sep 2000 14:26:05 GMT
Fountainhead wrote:
> System:
> HP Pavilion 8240 P266 32MB RAM 3GB HD
> NetworkEverywhere NC100 card
> Internet access (DSL) configured through Linksys router
>
> O/S
> COL 2.3 kernel 2.2.17 (just upgraded from 2.2.10) installed on /dev/hda1
> Swap file on dev/hda2
> No other O/S
>
> Background:
> Installed NIC but old kernel version did not like tulip and pci-scan modules
> Upgraded kernel to 2.2.17 and then installed the netdriver package, courtesy
> of Donald Becker/Scyld
> Everything worked fine for a few minutes and then system crashed while
> browsing
> Only way to reboot system was to power off and on
> Worked fine for a few minutes and crashed again while browsing
> Even power cycle did not help
> Booted using emergency diskette and commented out the above driver entries
> in /etc/modules/default
> System booted properly
> Swap file was not being recognized so made the recommended changes
> Uninstalled netdriver package and re-installed
> Re-configured eth0
> System worked fine for a few minutes and crashed again even though I was
> using terminal-based ftp
>
> Given that the system crashes a few minutes after boot, are there any
> overheating issues, memory overruns, or something else perhaps that is being
> exceeded that shouldn't be?
With the driver commented out will it still crash in a few minutes if yes then
it could be a hardware issue if no then it is the driver.
------------------------------
** 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
******************************
