|
Bugzilla – Full Text Bug Listing |
| Summary: | uli526x ethernet module doesn't load (for ASRock 939Dual-SATA2 mb) | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Jake Hamby <jake.hamby> |
| Component: | Kernel | Assignee: | Karsten Keil <karsten.keil> |
| Status: | RESOLVED WORKSFORME | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | ||
| Version: | Alpha 4 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | hwinfo.txt | ||
(In reply to comment #0) > On SUSE Linux 10.0 and 10.0 alpha 2, I'm able to use the onboard Ethernet on my This should read "SUSE Linux 10.0 and 10.1 alpha 2". Jake, can you please provide the output of hwinfo and attach it to this bug report? Thanks! Created attachment 61663 [details]
hwinfo.txt
Here is the output of hwinfo on SUSE 10.0.
Karsten, can you track this please? Jake, please try loading the uli module with "modprobe uli526x debug=1" Adding "debug=1" doesn't make any difference. I get the same two lines in syslog. Does it work with the final version ? No answer for half a year, if you still see problems please reopen the bug. |
On SUSE Linux 10.0 and 10.0 alpha 2, I'm able to use the onboard Ethernet on my ASRock 939Dual-SATA2 motherboard using the Tulip driver, which is automatically detected. On SUSE Linux 10.1 alpha 3 and alpha 4, however, the Tulip driver has now been split and there's a separate uli526x.ko driver. This driver doesn't load on my system. Dmesg shows that it's trying to load that module, but failing: uli526x: module not supported by Novell, setting U taint flag. uli526x: falsely claims to have parameter mode If I manually run "modprobe uli526x", I get (on 10.1 Alpha 4): FATAL: Error inserting uli526x (/lib/modules/2.6.15-rc5-git3-2-default/kernel/dr ivers/net/tulip/uli526x.ko): Invalid argument plus another copy of the dmesg entry. It looks like there is some sort of configuration problem with the module, rather than a hardware detection problem? On my SUSE 10.0 system, I get these kernel messages for the Ethernet: Linux Tulip driver version 1.1.13-NAPI (May 11, 2002) ACPI-0212: *** Warning: Device is not power manageable ACPI: PCI Interrupt 0000:00:11.0[A] -> GSI 17 (level, low) -> IRQ 217 tulip0: EEPROM default media type Autosense. tulip0: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block. tulip0: Index #1 - Media 10baseT (#0) described by a <unknown> (128) block. tulip0: Index #2 - Media 10baseT (#0) described by a 21140 non-MII (0) block. tulip0: Index #3 - Media 10base2 (#1) described by a 21140 non-MII (0) block. tulip0: Index #4 - Media 10baseT-FDX (#4) described by a 21140 non-MII (0) bloc k. tulip0: Index #5 - Media 100baseTx-FDX (#5) described by a 21140 non-MII (0) bl ock. tulip0: MII transceiver #1 config 3100 status 786d advertising 01e1. ali1563: SMBus control = 0403 ali1563_probe: Returning 0 eth0: ULi M5261/M5263 rev 64 at 000000000001e800, 00:13:8F:4A:2A:E4, IRQ 217. And there is a boot message (from /var/log/boot.msg): eth0 device: ALi Corporation M5263 Ethernet Controller (rev 40) eth0 configuration: eth-id-00:13:8f:4a:2a:e4 eth0 (DHCP) . IP/Netmask: 192.168.2.4 / 255.255.255.0 ('puma.')