http://www.linuxquestions.org/questi...icle&artid=408

...has the same instructions almost, just skip down to where it tells you how to config LILO since that's the part you need to do to get the new kernel to boot up

Hi,

Thanks for that, I was getting a bit confused!

I now have the 2.6.11.6 kernel installed, all went well... I think. Well I lost my little penguin at startup but the main thing is it detected my Ethernet card!!!!! I included the sis900 in the kernel instead of as a module.

The thing is I can't connect to any websites through any browser, in Konqueror it just says Unknown host www.google.com
I'm not sure what I need to configure or set for my domain name, I have localhost there at the moment. My router is acting as the DHCP server but I have no clue as to what the DHCP Hostname should be? or how I should proceed to configure internet access for this machine?

Doing /sbin/ifconfig says inet addr:192.168.0.3 for eth0 so shouldn't this be working and allowing internet access?

I am very gratefull for all your help in this, and it's good to see that light on my router at last! I rebooted again just to make sure and it still works!

Thank you for all your help, I have learned alot through this and I'm now addicted to Slackware forever.

Many thanks again

I belive the little penguine comes from framebuffer, which probably isnt on in yourt new kernel.

If the netgear router is doing dhcp, it should give you DNS servers when it does that too. It will either give you it's IP address, or forward the ones it got from logging into your ISP.
cat /etc/resolv.conf

compare that to what windows is using for nameservers (c:\> ipconfig /all entry for DNS Servers) and adjust accordingly.

if nothing is there (probably even if there are numbers there) use your router's web interface at http://192.168.0.1 and see if it has authenticated to your ISP.

try to ping an IP address on The Internet, like 64.179.4.149 or the nameserver IPs in resolv.conf

as usual, post all of it you tried if it's still not working.

Hi,

cat /etc/resolv.conf: gives

search 192.168.0.1

Here is what is happening,

from a cold boot the light is lit on the router solid green, then starts flashing as if receiving data. Then I startx and ping a website, such as google, I get a reply. I cannot access any site from any browser, it just says Host not found. Then after a while the light on the router will go out and stay out untill another cold boot is performed.

It once asked if I would like to recevie cookies from google, I replied yes but then it got no further. It has never got this far again.

If I just reboot the machine, no light comes on, it only lights up from a cold boot, but then not long after being on, say about 2 minutes the light will go out and then I can't ping anything or even connect to my routers web interface.

I am going to try upgrading the routers firmware, I have the lastest but I have just found that there's a new beta version available.

What I can't understand is, why the NIC gets detected but then after a while it becomes inactive again.

Many thanks, is there anything else I can do or try?

janap-146

[quote]...Then after a while the light on the router will go out and stay out untill another cold boot...[quote]
I know we went over this before, but if that was happening to me the first thing I'd do was replace the cable. Cables are just one of those things that can make weird things happen but it also helps that I have a bulk spool of cable handy.

It also sounds like it could be some quirky driver issue, or possibly something with the router port though.

If ping google.com works from a shell while at the same time the site won't load, that's a browser config issue. It may be something else broken though and it happens to drop connection between doing one test and the other. I'd say test at various stages of whatever is happening (lights on, lights off, etc) and see if you can still ping 192.168.0.1 or ping google.com. Also check your logfiles, usually in /var/log for messages stamped during the time when it cuts off.

Lastly, rather than playing musical kernels I'd look for a vendor supplied sis900 and see what that does. Generally I don't use the vendor's drivers if the kernel modules work but if they are buggy I'd say try it.

Hi,

I have just looked in /var/log at syslog and there is alot of errors relating to shpchp.o.gz: insmod shpchp failed
and also pciehp.0.gz: init_module: no such device

Not sure if this is relating to the NIC problem? Should these be added to the blacklist? or are they needed?

I also looked in /var/log messages, here is part of it as it's quite long:
----------------------------------------------------------------------------------------
Apr 11 17:59:43 paradox kernel: eth0: Media Link Off
Apr 11 18:00:52 paradox kernel: NETDEV WATCHDOG: eth0: transmit timed out
Apr 11 18:00:52 paradox kernel: eth0: Transmit timeout, status 00000004 00000000
Apr 11 18:00:53 paradox kernel: eth0: Media Link On 100mbps full-duplex
Apr 11 18:00:59 paradox kernel: eth0: Media Link Off
Apr 11 18:01:09 paradox kernel: eth0: Media Link On 100mbps full-duplex
Apr 11 18:01:25 paradox kernel: eth0: Media Link Off
Apr 11 18:02:05 paradox kernel: eth0: Media Link On 100mbps full-duplex
Apr 11 18:02:06 paradox kernel: eth0: Media Link Off
Apr 11 18:02:51 paradox kernel: eth0: Media Link On 100mbps full-duplex
Apr 11 18:02:52 paradox kernel: eth0: Media Link Off
Apr 11 18:03:42 paradox kernel: eth0: Media Link On 100mbps full-duplex
Apr 11 18:03:43 paradox kernel: eth0: Media Link Off
Apr 11 18:04:28 paradox kernel: eth0: Media Link On 100mbps full-duplex
Apr 11 18:04:29 paradox kernel: eth0: Media Link Off
Apr 11 18:05:29 paradox kernel: eth0: Media Link On 100mbps full-duplex
Apr 11 18:05:30 paradox kernel: eth0: Media Link Off
Apr 11 18:06:30 paradox kernel: eth0: Media Link On 100mbps full-duplex
Apr 11 18:06:31 paradox kernel: eth0: Media Link Off
Apr 11 18:06:48 paradox kernel: eth0: Media Link On 100mbps full-duplex
Apr 11 18:07:24 paradox kernel: eth0: Media Link Off
Apr 11 18:08:14 paradox kernel: eth0: Media Link On 100mbps full-duplex
Apr 11 18:08:15 paradox kernel: eth0: Media Link Off
Apr 11 18:08:27 paradox kernel: eth0: Media Link On 100mbps full-duplex
Apr 11 18:09:23 paradox kernel: eth0: Media Link Off
Apr 11 18:10:08 paradox kernel: eth0: Media Link On 100mbps full-duplex
Apr 11 18:10:09 paradox kernel: eth0: Media Link Off
Apr 11 18:10:34 paradox kernel: eth0: Media Link On 100mbps full-duplex
Apr 11 18:10:35 paradox kernel: eth0: Media Link Off
Apr 11 18:10:52 paradox kernel: eth0: Media Link On 100mbps full-duplex
Apr 11 18:11:08 paradox kernel: eth0: Media Link Off
Apr 11 18:11:31 paradox kernel: eth0: Media Link On 100mbps full-duplex
Apr 11 18:11:42 paradox kernel: eth0: Media Link Off
Apr 11 18:12:02 paradox kernel: eth0: Media Link On 100mbps full-duplex
Apr 11 18:12:18 paradox kernel: eth0: Media Link Off
Apr 11 18:37:00 paradox -- MARK --
Apr 11 18:57:00 paradox -- MARK --
-----------------------------------------------------------------------------------------------

It seems to be turning on and off for some reason, I am going to get a new cable tomorrow, failing that a new NIC!!

I did also notice a message in syslog yesterday, about dhcp: timed out waiting for a valid DHCP server response.

The trouble is, I have already swapped cables around and the cable works on WinXP that is being used in Slack, I have just been to the sis website and downloaded the sis900 module, is it just: make, to compile the driver? or maybe: make module??

Many thanks for your help,

janap-146

~ UPDATE ~

I have just taken the NIC out of my WinXP machine and put it in Slackware again, and I'm now typing this message in Slackware!
It connected to the Internet with no problems at all!

My WinXP box has just crashed at the Welcome screen with the NIC from my Slackware box, so tomorrow time to buy a new NIC
as this one has to be faulty. It worked the last time I tried it in WinXP but this time the link light is out on the router and has locked up XP!
at least Slackware doesn't crash when something like this happens, it just shows the diference.

I will let you know how it goes, I will post back tomorrow once I have a new NIC installed.

Many thanks for all your time and help through this, the Linux community is a great place.

janap-146

Hi,

I realise this is an old thread, and that my problem is quite different to the OP, but I too have a problem with an SiS900 network card.
Background to the problem: Running ubuntu dapper on an IBM PC 300. Can't get the onboard NIC (which linux reports as an SiS900) to work. Details as follows:

# uname -a
Linux fileserver 2.6.15-19-386 #1 PREEMPT Mon Mar 20 16:46:02 UTC 2006 i686 GNU/Linux

# lspci -vvv
<snip>
0000:00:01.1 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 80)
Subsystem: Silicon Integrated Systems [SiS] SiS900 10/100 Ethernet Adapter
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 C routed to IRQ 4
Region 0: I/O ports at d000 [size=256]
Region 1: Memory at e1101000 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at 20000000 [disabled] [size=128K]
Capabilities: [40] Power Management version 1
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

# tail /var/log/messages
Mar 28 13:28:18 localhost kernel: [4340251.246000] sis900.c: v1.08.09 Sep. 19 2005
Mar 28 13:28:18 localhost kernel: [4340251.247000] ACPI: PCI Interrupt 0000:00:01.1[C] -> Link [LNKC] -> GSI 4 (level, low) -> IRQ 4
Mar 28 13:28:18 localhost kernel: [4340251.247000] 0000:00:01.1: Error EERPOM read 0
Mar 28 13:28:18 localhost kernel: [4340251.247000] 0000:00:01.1: Cannot read MAC address.

# lsmod | grep sis
sis900 22912 0
mii 5888 3 sis900,8139cp,8139too
i2c_sis630 7948 0
i2c_core 21904 2 i2c_acpi_ec,i2c_sis630
sis_agp 8708 1
agpgart 34888 1 sis_agp
sis5513 17032 1


Does anyone have any ideas as to what I should be trying to get this to work?