Bug 5896
| Summary: | [sk98lin] vpd errors on dfi lanparty ut expert | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | drago01 |
| Component: | Network | Assignee: | Stephen Hemminger (stephen) |
| Status: | REJECTED WILL_NOT_FIX | ||
| Severity: | high | CC: | bunk, stephen |
| Priority: | P2 | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.15 | Subsystem: | |
| Regression: | --- | Bisected commit-id: | |
| Attachments: | lsvpd output | ||
Does the skge driver work for you? yes thx sk98lin 230404 0 skge 76369 0 how can I check which driver is used? ok slge driver is used and works fine The VPD is data in NVRAM on the board. It can either be non-existent because the vendor didn't put the hardware in (that is what the D-Link 530T did), or it could just have an incorrect checksum (see ASUS board). You might want to check the vendor site for a tool to patch the NVRAM. As already mentioned, the skge driver ignores VPD. but you can find out the info with the lsvpd tool (part of linux-diags). Please keep using the skge driver but find out the contents of the VPD. If VPD is totally missing from this motherboard, it will come back as all 0xFF. In which case, the best long term solution would be to blacklist it from the sk98lin driver. Created attachment 7042 [details]
lsvpd output
hier is the output.
note I also have a forcedeth network card
If it is still an issue, bug the vendor. There was another vendor (Gigabyte) that just patched the VPD but forgot to update the checksum. They shipped a tool to fix it (windows/DOS), but there were license issues. The sk98lin driver depends on good VPD data. Since a better alternative the skge driver is already available, there is no point in modifying the sk98lin driver to handle bad vendor VPD. |
Most recent kernel where this bug did not occur: N/A Distribution: FC4 x86_64 Hardware Environment: 00:00.0 Memory controller: nVidia Corporation CK804 Memory Controller (rev a3) 00:01.0 ISA bridge: nVidia Corporation CK804 ISA Bridge (rev a3) 00:01.1 SMBus: nVidia Corporation CK804 SMBus (rev a2) 00:02.0 USB Controller: nVidia Corporation CK804 USB Controller (rev a2) 00:02.1 USB Controller: nVidia Corporation CK804 USB Controller (rev a3) 00:06.0 IDE interface: nVidia Corporation CK804 IDE (rev a2) 00:07.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev a3) 00:08.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev a3) 00:09.0 PCI bridge: nVidia Corporation CK804 PCI Bridge (rev a2) 00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a3) 00:0b.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) 00:0c.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) 00:0d.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) 00:0e.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) 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:07.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 0a) 01:07.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 0a) 01:09.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80) 01:0a.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13) 05:00.0 VGA compatible controller: nVidia Corporation GeForce 7800 GTX (rev a1) Software Environment: Problem Description: when I load the sk98lin driver I get this errors in dmesg: eth1: -- ERROR -- Class: internal Software error Nr: 0x19e Msg: Vpd: Cannot read VPD keys (they keep comming because ifplud is running) Steps to reproduce: load the sk98lin driver on the dfi lanparty nf4 expert mobo I looked at the sources and found that there is a fix for this problem for asus mobos. Is it possible to add a similar fix for this mobo? If what kind of info should I provide to help? For now I have commented out the checksum check in the driver source.