Bug ethernet SIS 64bit version

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.

Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!

Boas António

I have the same headache...because I have the bloody laptop as well... ;-)

intrepid-amd64 2.6.27-11-generic #1 SMP Thu Jan 29 19:28:32 UTC 2009

lspci returns:

00:00.0 Host bridge: Silicon Integrated Systems [SiS] 671MX
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] SiS AGP Port (virtual PCI-to-PCI bridge)
00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS968 [MuTIOL Media IO] (rev 01)
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev 01)
00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f)
00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.1 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] 191 Gigabit Ethernet Adapter (rev 02)
00:05.0 IDE interface: Silicon Integrated Systems [SiS] SATA Controller / IDE mode (rev 03)
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:09.0 FLASH memory: ENE Technology Inc ENE PCI Memory Stick Card Reader Controller
00:09.1 SD Host controller: ENE Technology Inc ENE PCI SmartMedia / xD Card Reader Controller
00:09.3 FLASH memory: ENE Technology Inc ENE PCI Secure Digital / MMC Card Reader Controller
00:0f.0 Audio device: Silicon Integrated Systems [SiS] Azalia Audio Controller
01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 771/671 PCIE VGA Display Adapter (rev 10)

I was able to make it work by filling in /etc/network/interfaces, but alone it cannot even ping regularly. It works at high speed when a companion smc dongle is there.

auto eth0
iface eth0 inet static
address 192.168.0.24
netmask 255.255.255.0
gateway 192.168.0.100

The same machine has problems with:
(lsusb output)
Bus 003 Device 009: ID 0bda:8189 Realtek Semiconductor Corp. RTL8187B Wireless 802.11g 54Mbps Network Adapter
(it only works at high signal levels)
and
01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 771/671 PCIE VGA Display Adapter (rev 10)
(only works with xorg.conf setup in vesa driver mode)

I am not aware of any installation problems apart of the usual intrepid problems with static interfaces...

Em resumo, uma seca para masoquistas...para que me meti nisto...

Cheers

Antonio

Confirming the bug since you have the same problem with the network card.

Good luck with the laptop, hope SiS is better supported in jaunty :).

António, can you attach these log files?

      uname -a > uname-a.log

      cat /proc/version_signature > version.log

      dmesg > dmesg.log

      sudo lspci -vvnn > lspci-vvnn.log

These four files should be attached to the bug report (not pasted into comments, as it makes things harder to read, and formatting is completely broken).

dmesg.log is already attached so only the other 2 are missing. Thanks!

Ok, here goes

The quoted vendor laptop reference machine is really a Clevo M/61S in disguise...

there is still another problem on this laptop, keyboard inserts control chars when you change case fast enough...

Cheers

Sorry, the keyboard did its deeds again... Clevo M761S, I mean...

On Jaunty now, I had the adapter flawlessly working on 32-bit Jaunty, changed back to 64-bit now that an open display driver is available (why is this not incorporated in the kernel...), and the bug is still there

Linux 2.6.28-13-generic #44-Ubuntu SMP Tue Jun 2 07:55:09 UTC 2009 x86_64 GNU/Linux

Is there at least a known workaround?

Good morning

I have the interface working on:

Linux luna 2.6.31-15-generic #49-Ubuntu SMP Fri Nov 6 09:55:13 UTC 2009 x86_64 GNU/Linux

I will conduct more experiments on this interface (namely plug/unplug and revert to/from wireless testing), and if all goes well I will suggest that this bug is closed.

I have filed an ugly wireless bug, so it is good to have this interface around ;-)

Cheers

Antonio

Good morning

Confirmed, this bug vanished. There is a minor nag that should be corrected, each time we disconnect the cable, turn on the radio and go wireless, then turn off the radio and reconnect the cable, network manager turns up the interface, but it does not work anymore.
eth0 is absent from /etc/network/interfaces for this experiment.
To make the cable connection useful again, one must use sudo service network-manager restart (note that cas has been dropped in Karmik). Then it will resume normal operation.

Cheers

Antonio

amsn_lnx, thank you for reporting this and helping make Ubuntu better. Intrepid reached EOL on April 30, 2010.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue on a supported release? If so, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in a supported release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]