[GUTSY] SiS 190 onboard NIC problems

Bug #137630 reported by SqUe
10
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Ubuntu 7.10 Tribe 5.
M/B: Asrock 939S56-M
OnBoard chipset: SiS 756

The first time I tried to install it on the system, the installation process freezed at the point "Scanning for mirror...", after many retries, i came of killing by hand all "wget" process so that installation finishes.
Booting at the fresh installed system, had no difference, as the firefox couldn't visit all sites and update manager didn't work. Although network was connected, i had ip and I could ping the world!

Searching on google I came up a solution of lowering MTU to 1492, and did the trick!.

uname -a
Linux papillon 2.6.22-10-generic #1 SMP Wed Aug 22 08:11:52 GMT 2007 i686 GNU/Linux

lspci
00:00.0 Host bridge: Silicon Integrated Systems [SiS] Unknown device 0756 (rev 02)
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] PCI-to-PCI bridge
00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS965 [MuTIOL Media IO] (rev 48)
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev 01)
00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] AC'97 Sound Controller (rev a0)
00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f)
00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f)
00:03.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f)
00:03.3 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller
00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] 190 Gigabit Ethernet Adapter
00:05.0 IDE interface: Silicon Integrated Systems [SiS] 182 SATA/RAID Controller (rev 01)
00:06.0 PCI bridge: Silicon Integrated Systems [SiS] PCI-to-PCI bridge
00:07.0 PCI bridge: Silicon Integrated Systems [SiS] PCI-to-PCI bridge
00:0a.0 Modem: PCTel Inc HSP56 MicroModem (rev 04)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6600] (rev a2)

lspci -v only the part of ethernet
00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] 190 Gigabit Ethernet Adapter
        Subsystem: ASRock Incorporation Unknown device 0190
        Flags: bus master, medium devsel, latency 0, IRQ 22
        Memory at febfbc00 (32-bit, non-prefetchable) [size=128]
        I/O ports at e480 [size=128]
        Capabilities: [40] Power Management version 2

Revision history for this message
Nicolas Deschildre (ndeschildre) wrote :

Hi!
Thanks for the bugreport!
I think we can confirm this bug and the workaround working ([1] [2]).
Now as a quick fix, i don't know if there is per-driver scripts in network scripts so that we can change the MTU...
The bug itself would be interesting to investigate... The only probable reference to your problem i have found in the kernel ML [3] didn't seem to get a solution.
Regards,

[1] http://kerneltrap.org/node/4838?page=1
[2] http://ubuntuforums.org/showthread.php?t=395712
[3] http://marc.info/?l=linux-netdev&m=113662386231760&w=2

Changed in linux-source-2.6.22:
status: New → Confirmed
Revision history for this message
CharitakisYannis (charitakis-yannis) wrote :

Hi!

In our computer lab, I have installed edubuntu 7.10 on 13 machines
with Foxconn motherboard 622MX.
This motherboard uses the same network controller and I had the same
problem which I fixed by changing the mtu to 1492.

However, I would like to report that three out of 13 machines were still
facing network connectivity problems.

More precisely, despite the modified mtu, these machines after a cold boot,
were not able to browse web-pages despite that ping-ing a site was working.

For example ping www.google.com was working, while ssh or web browsing
was not working.

Now rebooting to Windows and then rebooting back to Linux was fixing the problem.
Ssh and web-browsing was ok.
However if turned off and then booting to linux, the problem persisted.

It seems that the MTU-work around is not working all the times.

Thank you very much for your support.

Revision history for this message
SqUe (sque) wrote :

I think you should try different values of MTU around and below 1500, also open an Ethereal (wireshark? can't remember its new name) and try to check what is going on with your packets. As this is a computer lab and you probably must fix it, (I don't know if this NIC is so badly designed or is so badly supported by linux drivers), in case you don't manage to fix it you could always buy some cheap network cards around 8-12 euros each, which have a common chip and well supported.

(An meneis athina, stin stournari tha vreis tetoies fthines kartoules, akoma k to plaisio fairnei kati netgear me 12 euros pou proswpika mou exoun doulepsei apsoga)

Revision history for this message
Brian Murray (brian-murray) wrote :

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

Changed in linux-source-2.6.22:
assignee: nobody → ubuntu-kernel-team
Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Revision history for this message
Amit Kucheria (amitk) wrote :

This bug report is being closed because we received no response to the previous inquiry for information. Please reopen if this is still an issue in the current Ubuntu release, Jaunty Jackalope 9.04 - http://www.ubuntu.com/getubuntu/download. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.