From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510
Description of problem:
machine boots, NIC is recognized and configured but in 9 out of 10
attempts I cannot saccess the network.
Error message (mesages):
sandwich kernel: NETDEV WATCHDOG: eth0: transmit times out
sandwich kernel: eth0: Transmit timeout, status 00000000 00000240
NIC sis900 onboard
booting with pci=acpioff, pci=usepirqmask, or noacpi doesn't cure the
Can provide error and ok of: dmesg, dmidecode, dsdt, interrupts,
lspci, pci on request
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Created attachment 101001 [details]
dmesg, dmidecode, dsdt, interrupts,
dmesg, dmidecode, dsdt, interrupts, lspci, pc
I just disassembled the dsdt. Both versions are identical...
Problem remains with new kernel (2.6.6-1.427)
Kernel update to 2.6.6-1.435 didn't fix the problem. BTW: is anyone
reading this stuff??
> booting with pci=acpioff, pci=usepirqmask, or noacpi doesn't cure the
You got those backwards, should be pci=noacpi or acpi=off
Give those a try ?
Been there, done that (as mentioned above) to no avail...
ah, this was mentioned this afternoon on Linux-kernel.
There's a fix for this in Andrew Morton's -mm tree, but the upstream
maintainer doesn't think its the right fix.
I'll look into this some more tomorrow.
I upgraded the BIOS two days ago and guess what: it didn't help
either... Unfortunately, there's nothing implemented in this BIOS
which would allow for tinkering with ACPI settings (MSI MS 6701 board
in a Medion PC).
My best workaround so far: whenever Linux fails to setup the NIC
properly I can restart the computer with another operating system
(developed somewhere in Redmond, WA, USA...). Rebooting again with
Linux gives usually full access to the NIC. Strange...
do you have any (good) news?
Is there any way of "freezing" the configuration once everything is
running? Right now, I do have LAN access, but there's no way to get
THE USB bluetooth dongle up and running...
Upgraded yesterday to 2.6.6-1.435.2.1. Rebooted today: NIC does not
Upgrade to 2.6.6-1.435.2.1 didn't help either. Anything I could try, test?
Hey guys, is there really nothing that could be done in this case???
Hello... Anybody working on this request?????
Fedora Core 2 has now reached end of life, and no further updates will be
provided by Red Hat. The Fedora legacy project will be producing further kernel
updates for security problems only.
If this bug has not been fixed in the latest Fedora Core 2 update kernel, please
try to reproduce it under Fedora Core 3, and reopen if necessary, changing the
product version accordingly.