Hopefully someone can help me out here...

uname -r
2.6.28-11-generic

lspci -nn
...
00:04.0 Ethernet controller [0200]: Silicon Integrated Systems [SiS] 191 Gigabit Ethernet Adapter [1039:0191] (rev 02)
...

ethtool -i eth0
driver: sis190
version: 1.2
firmware-version:
bus-info: 0000:00:04.0

ethtool eth0
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Current message level: 0x00000037 (55)
Link detected: no

ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:24:8c:95:50:8c
inet addr:192.168.1.167 Bcast:192.168.1.255 Mask:255.255.255.0
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:23 dropped:0 overruns:0 frame:23
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:19 Base address:0xdead

dmesg
...
[ 1309.862345] sis190 Gigabit Ethernet driver 1.2 loaded.
[ 1309.862361] sis190 0000:00:04.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[ 1309.862373] sis190 0000:00:04.0: setting latency timer to 64
[ 1309.862397] 0000:00:04.0: Read MAC address from EEPROM
[ 1309.862399] 0000:00:04.0: Error EEPROM read 0.
[ 1309.862402] 0000:00:04.0: Read MAC address from APC.
[ 1309.893016] 0000:00:04.0: Unknown PHY transceiver at address 0.
[ 1310.421017] 0000:00:04.0: Using transceiver at address 1 as default.
[ 1310.453680] 0000:00:04.0: SiS 191 PCI Gigabit Ethernet adapter at ffffc20010140c00 (IRQ: 19), 00:24:8c:95:50:8c
[ 1310.453682] eth0: RGMII mode.
[ 1310.453685] eth0: Enabling Auto-negotiation.
[ 1344.180814] ADDRCONF(NETDEV_UP): eth0: link is not ready

So it looks like you have an IRQ problem.
Try the board in another slot (if possible)
Try booting with some kernel options: noapic and / or nolapic
Check your BIOS settings: Disable "PnP OS" in your BIOS if it was enabled, or vice versa
Search on these terms linux kernel IRQ problem

-Interrupt:19 Base address:0xdead
+Interrupt:7 Base address:0xdead

noapci / nolapci didn't do anything besides change the interrupt,

I can't move the ethernet controller or touch it, as it is inside a storebought laptop.
and PnP OS is not enabled in my bios

I will investigate the search more but, I'm still hoping someone who corrected this issue will post in this thread.

The part that really bothers me is:
Link detected: no
Which absolutely should not be happening given the fact that the driver _should_ be working well enough.

I looked around and the only thing relevant was that the ubuntu driver doesn't seem to probe the link status, so I manually patched the sis190.c file as detailed here:
http://bugzilla.kernel.org/attachment.cgi?id=16963

However even after insmod-ing the new .ko file it seems to still not detect the link status:
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Current message level: 0x00000037 (55)
Link detected: no
-----------
00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] 191 Gigabit Ethernet Adapter (rev 02)
Subsystem: ASUSTeK Computer Inc. Device 1815
Flags: bus master, medium devsel, latency 0, IRQ 19
Memory at f9ffcc00 (32-bit, non-prefetchable) [size=128]
I/O ports at cc00 [size=128]
Capabilities: [40] Power Management version 2
Kernel driver in use: sis190
Kernel modules: sis190
-----------
This is odd given that my driver was properly inserted with the patch ( I set it's version to 1.3 as opposed to the current version (1.2))

ethtool -i eth0
driver: sis190
version: 1.3
firmware-version:
bus-info: 0000:00:04.0

Anyone who has any ideas please reply.

Hello there,

I have the same problem trying to install a slackware linux 12.1 // 12.2 // 13.0 RC1 on a Asus X58C laptop. The network card is SiS190/191, and on all distributions I've tried -> Slackware, Fedora Core 9, ZenWalk, etc I keep bumping into the same problem.

The problem more exactly, is that www.google.com or yahoo.com or gmail.com load perfectly and fast, but any other sites i try to browse end up generating rx errors.

It's not a problem from the browser. If i ssh to another machine, I can do remotely anything as long as it doesn't generate many lines. If i do a 'ps -auxf' it crashes after the first 3 lines. Same with ftp-s, if i open a ftp from konsole it connects flawlessly but when I do a dir or ls, it crashes generating rx errors.

I'll post some more detailed information once I get another distribution up on that machine.

Hi together,

I had the same problem with my laptop (Asus) and an SiS191 card. I was running slackware64-current on that machine. Because I use that computer in business I decided to installed slackware12.2 instead and now everything works fine.

Before the reinstall I booted with slax and also everything worked fine.

My problem was that I could not find out what went wrong since dhcp configuration went properly and the machine had an ip-adress as well as the correct standard-gateway and dns-server. I started tcpdump and saw that my machine was sending a lot of arp-requests to the ip of the standard-gateway.

I'm interessted in an expanation what there was going wrong with this module.

Markus

I am writing to say I have just experienced this issue, and the remedy was to set the MTU to 1496, rather than the default 1500. Apparently this is the maximum supported by this driver before it becomes unstable. Preliminary testing shows it all working fine, I can get webpages at least!

http://http://bugzilla.kernel.org/show_bug.cgi?id=13862 shows the bug on the kernel bugzilla site.

To change in gnome (at least in FC 11) right click on the TVs (The network logo) at the top right, select "Edit Connections", edit the ethernet connection, and change the MTU.

Hello scarydeath,

thanks for your post, this helped me to understand the problem and its solution.

Markus

i was solved this problem with this way. this is not my think but it's work !

#sudo ifconfig eth0 down
#sudo ifconfig eth0 mtu 1024
#sudo ifconfig eth0 up

---> implementation <---
the driver of vendor sis can use maximum mtu 1024.

in basic word
----------------------------
if ( mtu > 1024 ) network=crashed
----------------------------
chears