if i try to boot the minimal live cd 2005.0 i get the error "skge ignoring bogus sensor interrupts" if I try to boot the cd whit the nodetect option everything is allright just at the moment that I try to modprobe skge the old module sk98lin, worked fine. I have an Asus p4c800 motherboard and the network card is onboard.
egolf: have you tried a 2.6.12 kernel with skge? I'm just curious if this was fixed or not and have no way of testing it...
it seems to work well whit the 2.6.12 kernel. I just tried. Thx for the tip.
(In reply to comment #2) > it seems to work well whit the 2.6.12 kernel. I just tried. > Thx for the tip. oops no it dosn't wok have the same errer like before only in the kern.log :o( In 1 houer I have 3.1Gb of kern.log But the connection works well. tial kern.log Jul 23 13:48:25 AC skge ignoring bogus sensor interrups Jul 23 13:48:25 AC skge ignoring bogus sensor interrups Jul 23 13:48:25 AC skge ignoring bogus sensor interrups Jul 23 13:48:25 AC skge ignoring bogus sensor interrups Jul 23 13:48:25 AC skge ignoring bogus sensor interrups Jul 23 13:48:25 AC skge ignoring bogus sensor interrups Jul 23 13:48:25 AC skge ignoring bogus sensor interrups Jul 23 13:48:25 AC skge ignoring bogus sensor interrups Jul 23 13:48:25 AC skge ignoring bogus sensor interrups
Please attach "lspci -v" output and I will report this upstream.
0000:02:05.0 Ethernet controller: 3Com Corporation 3c940 10/100/1000Base-T [Marvell] (rev 12) Subsystem: ASUSTeK Computer Inc. P4P800/K8V Deluxe motherboard Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 22 Memory at feaf8000 (32-bit, non-prefetchable) I/O ports at d800 [size=256] Capabilities: [48] Power Management version 2 Capabilities: [50] Vital Product Data
Sent a mail upstream, awaiting response
Created attachment 65185 [details, diff] Possible fix This is the patch which the skge author would like you to test.
I just tested. The fix works for me! I have not one error message! :o) Thx
Fixed in gentoo-sources-2.6.12-r8 Fixed in genpatches-2.6.12-12 Release team, feel free to close this bug.
This is fixed with the 2005.1-r1 release media.