On Wed, 2002-10-02 at 13:14, Cochran Robert L (NO) wrote:
To me this means your ethernet controller is working fine. An lsmod
should show that sis900 is running.
In fact, lsmod shows that it is not running at all. Trying to load the
card manually produces the following from dmesg (many entries over and
over again):
sis900.c: v1.08.04 4/25/2002
divert: allocating divert_blk for eth1
/var/log/messages has the following:
Oct 2 23:34:30 spike kernel: sis900.c: v1.08.04 4/25/2002
Oct 2 23:34:30 spike kernel: eth1: Error EERPOM read 0
Oct 2 23:34:30 spike /etc/hotplug/net.agent: NET unregister event not
supportedOct 2 23:34:30 spike /etc/hotplug/net.agent: NET unregister
event not supportedOct 2 23:34:30 spike insmod:
/lib/modules/2.4.18-14/kernel/drivers/net/sis900.o: init_module: No such
device
Oct 2 23:34:30 spike insmod: Hint: insmod errors can be caused by
incorrect module parameters, including invalid IO or IRQ
parameters. You may find more
information in syslog or the output from dmesg
Oct 2 23:34:30 spike insmod:
/lib/modules/2.4.18-14/kernel/drivers/net/sis900.o: insmod eth1 failed
Oct 2 23:34:30 spike /etc/hotplug/net.agent: invoke ifup eth1
This confirms the driver is not loading.
Let's go back a bit. When you installed 8.0 did you have an ethernet
cable plugged into your machine (using the onboard ethernet plug and
not the PCI card) and did you have a running network available? For
example -- was there a gateway device that could be pinged at
install time?
The answer to the existing network question is yes. I have a Linksys
firewall/vpn router/gateway, which also serves as my DHCP server. All of
this was live when I installed RH 8.0. In fact, I only installed the PCI
card *after* several unsuccessful tries with the on-board controller.
If so, the anaconda installer should have detected your networking,
loaded the right driver for the ethernet controller, and brought you
to a screen asking for the IP address of the machine and IP
addresses representing the gateway IP, and the DNS server IP. Did
this happen? My guess is you didn't have the machine connected to
your network. So the installer skipped the network setup.
But the reality is Anaconda did not. I re-installed twice just to be
sure. That means to me that the Ethernet controller's driver did NOT
load properly, because there was, indeed, a working network. In
addition, there actually does not need to be a network running - only a
network card. You can configure a static address on an Ethernet
controller with no cable plugged in. I've done this many, many times. A
Link-down state on an Ethernet controller will not stop the driver from
loading. Even so, the state on the controller should have been Link-up.
Also, were you asked to select a firewall security level? It is very
possible that you turned on the default firewall and it is blocking
ethernet packets, making you think the hardware is not working.
Because I already have a hardware firewall, I set my security level to
no firewall.
What does running 'ifconfig' show you? Do you see output for eth0
and/or eth1?
My ifconfig for eth0 shows a working connection and also shows that the
device eth1 does not exist.
PS -- when you post to this list, can you do that in plain text.
Sure I can. Note, your last post was also in HTML - I reformatted your
message. So many people post here in HTML it seems odd that I would be
singled out though. My XE settings just default to it.
Thanks
Robert L. Cochran
-----Original Message-----
From: Christopher A. Williams [mailto:chrisw@;privatei.com]
Sent: Wednesday, October 02, 2002 2:44 PM
To: [EMAIL PROTECTED]
Subject: RE: 8.0 Problems - SIS900 series controller will not load.
OK - here's the output of the lspci -v -v command regarding the
SIS-900 series (963) Ethernet controller:
00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900
10/100 Ethernet (rev 91)
Subsystem: Asustek Computer, Inc.: Unknown device 80a7
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (13000ns min, 2750ns max)
Interrupt: pin A routed to IRQ 9
Region 0: I/O ports at 9800 [size=256]
Region 1: Memory at e4000000 (32-bit, non-prefetchable)
[size=4K]
Expansion ROM at ef6c0000 [disabled] [size=128K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
I'm not sure what the Unknown Device 80a7 means, but this seems to
be consistent with the errors I get at startup when trying to load
this device. Manually setting the IRQ did not help. Insmod reports
back roughly the same error as I recall. Could this be where the
problem is?
Cheers,
Chris
--
====================================
"If you get to thinkin' you're a
person of some influence, try
orderin' someone else's dog around."
--Cowboy Wisdom
