|
Bugzilla – Full Text Bug Listing |
| Summary: | D-Link DFE-660 card not detected | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Thorsten Kukuk <kukuk> |
| Component: | Hotplug | Assignee: | Christian Zoz <zoz> |
| Status: | RESOLVED INVALID | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Beta 4 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
If you configure it once with YaST2, it works. But there will never be a popup that new hardware was found or so. User has to find out itself that he has to start YaST2 and configure the card. Plug it in the other slot. Ok, once I did that it always works. Do I need to understand that? My DFE 660 also works. At least plugging in the running system. I will test booting with plugged card later. It works also when plug before booting. Please reopen if the problem arises again. |
The D-Link DFE-660 card will be detected by lspci and hwinfo: 02:00.0 Ethernet controller: Digital Equipment Corporation DECchip 21142/43 (rev 41) 22: PCI 200.0: 0200 Ethernet controller [Created at pci.277] UDI: /org/freedesktop/Hal/devices/pci_1011_19 Unique ID: gvUW.Ri9FBKBdN42 Parent ID: _Znp.qcMpx0aRxCB SysFS ID: /devices/pci0000:00/0000:00:02.0/0000:02:00.0 SysFS BusID: 0000:02:00.0 Hardware Class: network Model: "D-Link DECchip 21142/43" Vendor: pci 0x1011 "Digital Equipment Corporation" Device: pci 0x0019 "DECchip 21142/43" SubVendor: pci 0x1186 "D-Link System Inc" SubDevice: pci 0x1142 Revision: 0x41 Driver: "tulip" Device File: eth4 I/O Ports: 0x1400-0x14ff (rw) Memory Range: 0x12000000-0x120003ff (rw,non-prefetchable) Memory Range: 0x10000000-0x1003ffff (ro,prefetchable,disabled) IRQ: 11 (288 events) HW Address: 00:e0:98:77:01:ff Module Alias: "pci:v00001011d00000019sv00001186sd00001142bc02sc00i00" Driver Info #0: Driver Status: tulip is active Driver Activation Cmd: "modprobe tulip" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #12 (CardBus bridge) But the driver is not loaded and the network not active. I have the card here for testing.