DWL650+ not recognized/no power - SuSE 10.0
Anyone else had this problem? I've tried installing native drivers, NDISWrapper with the windoze drivers but no luck! I messed up my installation with some of the stuff I tried so I just reinstalled but can't get SuSE to recognized my D-Link DWL650+ WLAN card.
Anyone else had this problem? I've tried installing native drivers, NDISWrapper with the windoze drivers but no luck! I messed up my installation with some of the stuff I tried so I just reinstalled but can't get SuSE to recognized my D-Link DWL650+ WLAN card. There's just no power to it and lspci doesn't seem to show it (works fine in windoze).
Any help you can give me would be greatly appreciated!
Here's my (abbr.) DMESG log. BTW I have "pci=routeirq" in the boot script.
linux:~ # dmesg
Linux version 2.6.13-15-default (geeko@buildhost) (gcc version 4.0.2 20050901 (p
rerelease) (SUSE Linux)) #1 Tue Sep 13 14:56:15 UTC 2005
.
.
Allocating PCI resources starting at 12000000 (gap: 12000000:edfe0000)
..
ACPI: Looking for DSDT in initrd... not found!
not found!
ACPI: setting ELCR to 0200 (from 0800)
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfd880, last bus=7
PCI: Using configuration type 1
ACPI: Subsystem revision 20050408
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
ACPI: Assume root bridge [\_SB_.PCI0] segment is 0
ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
Boot video device is 0000:01:00.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP0._PRT]
ACPI: Power Resource [PSIO] (on)
ACPI: Embedded Controller [EC0] (gpe 9)
ACPI: Power Resource [PFN0] (off)
ACPI: Power Resource [PVID] (on)
ACPI: Power Resource [PRSD] (off)
ACPI: Power Resource [PDCK] (on)
Linux Plug and Play Support v0.97
Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 17 devices
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
TC classifier action (bugs to netdev@vger.kernel.org cc hadi@cyberus.ca)
pnp: 00:0c: ioport range 0x15e0-0x15ef has been reserved
pnp: 00:0c: ioport range 0xef00-0xef3f could not be reserved
pnp: 00:0c: ioport range 0xefa0-0xefaf has been reserved
PCI: Ignore bogus resource 6 [0:0] of 0000:01:00.0
PCI: Bridge: 0000:00:01.0
IO window: d000-dfff
MEM window: 70000000-dfffffff
PREFETCH window: e0000000-f7ffffff
PCI: Bus 2, cardbus bridge: 0000:00:02.0
IO window: 00002000-00002fff
IO window: 00003000-00003fff
PREFETCH window: 12000000-13ffffff
MEM window: 14000000-15ffffff
PCI: Bus 6, cardbus bridge: 0000:00:02.1
IO window: 00004000-00004fff
IO window: 00005000-00005fff
PREFETCH window: 16000000-17ffffff
MEM window: 18000000-19ffffff
ACPI-0212: *** Warning: Device is not power manageable
ACPI: PCI Interrupt Link [LNKA] disabled and referenced, BIOS bug.
ACPI: PCI Interrupt Link [LNKA] BIOS reported IRQ 0, using IRQ 9
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 9
PCI: setting IRQ 9 as level-triggered
ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [LNKA] -> GSI 9 (level, low) -> IRQ
9
ACPI-0212: *** Warning: Device is not power manageable
ACPI: PCI Interrupt Link [LNKB] disabled and referenced, BIOS bug.
ACPI: PCI Interrupt Link [LNKB] BIOS reported IRQ 0, using IRQ 9
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 9
ACPI: PCI Interrupt 0000:00:02.1 -> Link [LNKB] -> GSI 9 (level, low) -> IRQ
9
.
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
.
PNP: PS/2 Controller [PNP0303:KBD0,PNP0f13:MOU0] at 0x60,0x64 irq 1,12
.
pnp: Device 00:02 activated.
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
.
ACPI wakeup devices:
LID0 SLPB PCI0 UAR1 MWV0 BAT0 USB0
ACPI: (supports S0 S1 S3 S4 S5)
.
ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
ACPI: Processor [CPU0] (supports 8 throttling states)
.
ACPI: Thermal Zone [THM0] (51 C)
ACPI: Thermal Zone [THM2] (28 C)
ACPI: Thermal Zone [THM6] (30 C)
ACPI: Thermal Zone [THM7] (27 C)
ACPI: Fan [FN00] (off)
ACPI: Fan [FN20] (off)
ACPI: Fan [FN60] (off)
ACPI: Fan [FN70] (off)
.
pnp: Device 00:03 activated.
parport: PnPBIOS parport detected.
parport0: PC-style at 0x3bc, irq 7 [PCSPP,TRISTATE]
lp0: using parport0 (interrupt-driven).
.
ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [LNKA] -> GSI 9 (level, low) -> IRQ
9
Yenta: CardBus bridge found at 0000:00:02.0 [1014:00eb]
Yenta: Enabling burst memory read transactions
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:02.0, mfunc 0xfba97543, devctl 0x62
Yenta TI: socket 0000:00:02.0 probing PCI interrupt failed, trying to fix
Yenta TI: socket 0000:00:02.0 no PCI interrupts. Fish. Please report.
Yenta: no PCI IRQ, CardBus support disabled for this socket.
Yenta: check your BIOS CardBus, BIOS IRQ or ACPI settings.
Yenta: ISA IRQ mask 0x0438, PCI irq 0
Socket status: 30000006
ACPI: PCI Interrupt 0000:00:02.1 -> Link [LNKB] -> GSI 9 (level, low) -> IRQ
9
Yenta: CardBus bridge found at 0000:00:02.1 [1014:00eb]
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:02.1, mfunc 0xfba97543, devctl 0x62
Yenta TI: socket 0000:00:02.1 probing PCI interrupt failed, trying to fix
Yenta TI: socket 0000:00:02.1 no PCI interrupts. Fish. Please report.
Yenta: no PCI IRQ, CardBus support disabled for this socket.
Yenta: check your BIOS CardBus, BIOS IRQ or ACPI settings.
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: acpi_shpchprm:\_SB_.PCI0 evaluate _BBN fail=0x5
shpchp: acpi_shpchprm:get_device PCI ROOT HID fail=0x5
Yenta: ISA IRQ mask 0x0438, PCI irq 0
Socket status: 30000020
cs: pcmcia_socket1: cardbus cards are not supported.
usbcore: registered new driver usbfs
usbcore: registered new driver hub
USB Universal Host Controller Interface driver v2.3
ACPI: PCI Interrupt Link [LNKD] disabled and referenced, BIOS bug.
ACPI: PCI Interrupt Link [LNKD] BIOS reported IRQ 0, using IRQ 10
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 10
PCI: setting IRQ 10 as level-triggered
ACPI: PCI Interrupt 0000:00:07.2[D] -> Link [LNKD] -> GSI 10 (level, low) -> IRQ
10
uhci_hcd 0000:00:07.2: UHCI Host Controller
uhci_hcd 0000:00:07.2: new USB bus registered, assigned bus number 1
irq 10: nobody cared (try booting with the "irqpoll" option)
[<c013c18c>] __report_bad_irq+0x1c/0x70
[<c013c27b>] note_interrupt+0x6b/0xd0
[<c013bd1c>] __do_IRQ+0xbc/0xd0
[<c01055e8>] do_IRQ+0x38/0x60
[<c0103dea>] common_interrupt+0x1a/0x20
[<c013007b>] posix_cpu_timer_schedule+0xbb/0x480
[<c0120ba1>] __do_softirq+0x31/0xa0
[<c0120c36>] do_softirq+0x26/0x30
[<c01055ed>] do_IRQ+0x3d/0x60
[<c0103dea>] common_interrupt+0x1a/0x20
[<d2dd007b>] usbdev_read+0xdb/0x2c0 [usbcore]
[<c013becd>] setup_irq+0x5d/0xc0
[<d2dcc0d0>] usb_hcd_irq+0x0/0x60 [usbcore]
[<c013c043>] request_irq+0x83/0xa0
[<d2dcc322>] usb_add_hcd+0xd2/0x340 [usbcore]
[<c0281bb9>] pcibios_set_master+0x19/0x90
[<d2dd2907>] usb_hcd_pci_probe+0x187/0x290 [usbcore]
[<c0255d00>] __driver_attach+0x0/0x40
[<c01f9c50>] __pci_device_probe+0x30/0x40
[<c01f9c7e>] pci_device_probe+0x1e/0x40
[<c0255c3f>] driver_probe_device+0x2f/0x90
[<c0255d39>] __driver_attach+0x39/0x40
[<c02554a8>] bus_for_each_dev+0x38/0x60
[<c0255d51>] driver_attach+0x11/0x20
[<c0255d00>] __driver_attach+0x0/0x40
[<c02558aa>] bus_add_driver+0x5a/0xa0
[<c01f9e38>] pci_register_driver+0x58/0x80
[<d2c1606f>] uhci_hcd_init+0x6f/0xd0 [uhci_hcd]
[<c0134171>] sys_init_module+0xa1/0x180
[<c0102d1b>] sysenter_past_esp+0x54/0x79
handlers:
[<d2dcc0d0>] (usb_hcd_irq+0x0/0x60 [usbcore])
Disabling IRQ #10
uhci_hcd 0000:00:07.2: irq 10, io base 0x00008400
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
piix4_smbus 0000:00:07.3: Found 0000:00:07.3 device
piix4_smbus 0000:00:07.3: IBM Laptop detected; this module may corrupt your seri
al eeprom! Refusing to load module!
piix4_smbus: probe of 0000:00:07.3 failed with error -1
.
ibm_acpi: IBM ThinkPad ACPI Extras v0.11
ibm_acpi: http://ibm-acpi.sf.net/
ACPI-0077: *** Warning: No context for object [d1e0ca00]
ibm_acpi: hotkey device not present
ACPI-0077: *** Warning: No context for object [d1fb2a80]
ibm_acpi: dock device not present
IA-32 Microcode Update Driver: v1.14 <tigran@veritas.com>
IA-32 Microcode Update Driver v1.14 unregistered
.
cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7
cs: IO port probe 0x100-0x3af: clean.
cs: IO port probe 0xc00-0xcff: clean.
cs: IO port probe 0x820-0x8ff: clean.
cs: IO port probe 0xa00-0xaff: clean.
cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7
cs: IO port probe 0x100-0x3af: clean.
cs: IO port probe 0xc00-0xcff: clean.
cs: IO port probe 0x820-0x8ff: clean.
cs: IO port probe 0xa00-0xaff: clean.
.
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|100], AE_TIME
mtrr: 0xe0000000,0x400000 overlaps existing 0xe0000000,0x200000
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|100], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|100], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|100], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|100], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|100], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|100], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|100], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|100], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|100], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|100], AE_TIME
Any help you can give me would be greatly appreciated!
Here's my (abbr.) DMESG log. BTW I have "pci=routeirq" in the boot script.
linux:~ # dmesg
Linux version 2.6.13-15-default (geeko@buildhost) (gcc version 4.0.2 20050901 (p
rerelease) (SUSE Linux)) #1 Tue Sep 13 14:56:15 UTC 2005
.
.
Allocating PCI resources starting at 12000000 (gap: 12000000:edfe0000)
..
ACPI: Looking for DSDT in initrd... not found!
not found!
ACPI: setting ELCR to 0200 (from 0800)
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfd880, last bus=7
PCI: Using configuration type 1
ACPI: Subsystem revision 20050408
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
ACPI: Assume root bridge [\_SB_.PCI0] segment is 0
ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
Boot video device is 0000:01:00.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP0._PRT]
ACPI: Power Resource [PSIO] (on)
ACPI: Embedded Controller [EC0] (gpe 9)
ACPI: Power Resource [PFN0] (off)
ACPI: Power Resource [PVID] (on)
ACPI: Power Resource [PRSD] (off)
ACPI: Power Resource [PDCK] (on)
Linux Plug and Play Support v0.97
Adam Belaypnp: PnP ACPI init
pnp: PnP ACPI: found 17 devices
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
TC classifier action (bugs to netdev@vger.kernel.org cc hadi@cyberus.ca)
pnp: 00:0c: ioport range 0x15e0-0x15ef has been reserved
pnp: 00:0c: ioport range 0xef00-0xef3f could not be reserved
pnp: 00:0c: ioport range 0xefa0-0xefaf has been reserved
PCI: Ignore bogus resource 6 [0:0] of 0000:01:00.0
PCI: Bridge: 0000:00:01.0
IO window: d000-dfff
MEM window: 70000000-dfffffff
PREFETCH window: e0000000-f7ffffff
PCI: Bus 2, cardbus bridge: 0000:00:02.0
IO window: 00002000-00002fff
IO window: 00003000-00003fff
PREFETCH window: 12000000-13ffffff
MEM window: 14000000-15ffffff
PCI: Bus 6, cardbus bridge: 0000:00:02.1
IO window: 00004000-00004fff
IO window: 00005000-00005fff
PREFETCH window: 16000000-17ffffff
MEM window: 18000000-19ffffff
ACPI-0212: *** Warning: Device is not power manageable
ACPI: PCI Interrupt Link [LNKA] disabled and referenced, BIOS bug.
ACPI: PCI Interrupt Link [LNKA] BIOS reported IRQ 0, using IRQ 9
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 9
PCI: setting IRQ 9 as level-triggered
ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [LNKA] -> GSI 9 (level, low) -> IRQ
9
ACPI-0212: *** Warning: Device is not power manageable
ACPI: PCI Interrupt Link [LNKB] disabled and referenced, BIOS bug.
ACPI: PCI Interrupt Link [LNKB] BIOS reported IRQ 0, using IRQ 9
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 9
ACPI: PCI Interrupt 0000:00:02.1 -> Link [LNKB] -> GSI 9 (level, low) -> IRQ
9
.
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
.
PNP: PS/2 Controller [PNP0303:KBD0,PNP0f13:MOU0] at 0x60,0x64 irq 1,12
.
pnp: Device 00:02 activated.
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
.
ACPI wakeup devices:
LID0 SLPB PCI0 UAR1 MWV0 BAT0 USB0
ACPI: (supports S0 S1 S3 S4 S5)
.
ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
ACPI: Processor [CPU0] (supports 8 throttling states)
.
ACPI: Thermal Zone [THM0] (51 C)
ACPI: Thermal Zone [THM2] (28 C)
ACPI: Thermal Zone [THM6] (30 C)
ACPI: Thermal Zone [THM7] (27 C)
ACPI: Fan [FN00] (off)
ACPI: Fan [FN20] (off)
ACPI: Fan [FN60] (off)
ACPI: Fan [FN70] (off)
.
pnp: Device 00:03 activated.
parport: PnPBIOS parport detected.
parport0: PC-style at 0x3bc, irq 7 [PCSPP,TRISTATE]
lp0: using parport0 (interrupt-driven).
.
ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [LNKA] -> GSI 9 (level, low) -> IRQ
9
Yenta: CardBus bridge found at 0000:00:02.0 [1014:00eb]
Yenta: Enabling burst memory read transactions
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:02.0, mfunc 0xfba97543, devctl 0x62
Yenta TI: socket 0000:00:02.0 probing PCI interrupt failed, trying to fix
Yenta TI: socket 0000:00:02.0 no PCI interrupts. Fish. Please report.
Yenta: no PCI IRQ, CardBus support disabled for this socket.
Yenta: check your BIOS CardBus, BIOS IRQ or ACPI settings.
Yenta: ISA IRQ mask 0x0438, PCI irq 0
Socket status: 30000006
ACPI: PCI Interrupt 0000:00:02.1 -> Link [LNKB] -> GSI 9 (level, low) -> IRQ
9
Yenta: CardBus bridge found at 0000:00:02.1 [1014:00eb]
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:02.1, mfunc 0xfba97543, devctl 0x62
Yenta TI: socket 0000:00:02.1 probing PCI interrupt failed, trying to fix
Yenta TI: socket 0000:00:02.1 no PCI interrupts. Fish. Please report.
Yenta: no PCI IRQ, CardBus support disabled for this socket.
Yenta: check your BIOS CardBus, BIOS IRQ or ACPI settings.
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: acpi_shpchprm:\_SB_.PCI0 evaluate _BBN fail=0x5
shpchp: acpi_shpchprm:get_device PCI ROOT HID fail=0x5
Yenta: ISA IRQ mask 0x0438, PCI irq 0
Socket status: 30000020
cs: pcmcia_socket1: cardbus cards are not supported.
usbcore: registered new driver usbfs
usbcore: registered new driver hub
USB Universal Host Controller Interface driver v2.3
ACPI: PCI Interrupt Link [LNKD] disabled and referenced, BIOS bug.
ACPI: PCI Interrupt Link [LNKD] BIOS reported IRQ 0, using IRQ 10
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 10
PCI: setting IRQ 10 as level-triggered
ACPI: PCI Interrupt 0000:00:07.2[D] -> Link [LNKD] -> GSI 10 (level, low) -> IRQ
10
uhci_hcd 0000:00:07.2: UHCI Host Controller
uhci_hcd 0000:00:07.2: new USB bus registered, assigned bus number 1
irq 10: nobody cared (try booting with the "irqpoll" option)
[<c013c18c>] __report_bad_irq+0x1c/0x70
[<c013c27b>] note_interrupt+0x6b/0xd0
[<c013bd1c>] __do_IRQ+0xbc/0xd0
[<c01055e8>] do_IRQ+0x38/0x60
[<c0103dea>] common_interrupt+0x1a/0x20
[<c013007b>] posix_cpu_timer_schedule+0xbb/0x480
[<c0120ba1>] __do_softirq+0x31/0xa0
[<c0120c36>] do_softirq+0x26/0x30
[<c01055ed>] do_IRQ+0x3d/0x60
[<c0103dea>] common_interrupt+0x1a/0x20
[<d2dd007b>] usbdev_read+0xdb/0x2c0 [usbcore]
[<c013becd>] setup_irq+0x5d/0xc0
[<d2dcc0d0>] usb_hcd_irq+0x0/0x60 [usbcore]
[<c013c043>] request_irq+0x83/0xa0
[<d2dcc322>] usb_add_hcd+0xd2/0x340 [usbcore]
[<c0281bb9>] pcibios_set_master+0x19/0x90
[<d2dd2907>] usb_hcd_pci_probe+0x187/0x290 [usbcore]
[<c0255d00>] __driver_attach+0x0/0x40
[<c01f9c50>] __pci_device_probe+0x30/0x40
[<c01f9c7e>] pci_device_probe+0x1e/0x40
[<c0255c3f>] driver_probe_device+0x2f/0x90
[<c0255d39>] __driver_attach+0x39/0x40
[<c02554a8>] bus_for_each_dev+0x38/0x60
[<c0255d51>] driver_attach+0x11/0x20
[<c0255d00>] __driver_attach+0x0/0x40
[<c02558aa>] bus_add_driver+0x5a/0xa0
[<c01f9e38>] pci_register_driver+0x58/0x80
[<d2c1606f>] uhci_hcd_init+0x6f/0xd0 [uhci_hcd]
[<c0134171>] sys_init_module+0xa1/0x180
[<c0102d1b>] sysenter_past_esp+0x54/0x79
handlers:
[<d2dcc0d0>] (usb_hcd_irq+0x0/0x60 [usbcore])
Disabling IRQ #10
uhci_hcd 0000:00:07.2: irq 10, io base 0x00008400
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
piix4_smbus 0000:00:07.3: Found 0000:00:07.3 device
piix4_smbus 0000:00:07.3: IBM Laptop detected; this module may corrupt your seri
al eeprom! Refusing to load module!
piix4_smbus: probe of 0000:00:07.3 failed with error -1
.
ibm_acpi: IBM ThinkPad ACPI Extras v0.11
ibm_acpi: http://ibm-acpi.sf.net/
ACPI-0077: *** Warning: No context for object [d1e0ca00]
ibm_acpi: hotkey device not present
ACPI-0077: *** Warning: No context for object [d1fb2a80]
ibm_acpi: dock device not present
IA-32 Microcode Update Driver: v1.14 <tigran@veritas.com>
IA-32 Microcode Update Driver v1.14 unregistered
.
cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7
cs: IO port probe 0x100-0x3af: clean.
cs: IO port probe 0xc00-0xcff: clean.
cs: IO port probe 0x820-0x8ff: clean.
cs: IO port probe 0xa00-0xaff: clean.
cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7
cs: IO port probe 0x100-0x3af: clean.
cs: IO port probe 0xc00-0xcff: clean.
cs: IO port probe 0x820-0x8ff: clean.
cs: IO port probe 0xa00-0xaff: clean.
.
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|100], AE_TIME
mtrr: 0xe0000000,0x400000 overlaps existing 0xe0000000,0x200000
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|100], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|100], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|100], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|100], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|100], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|100], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|100], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|100], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|100], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|0], AE_TIME
ACPI-1048: *** Warning: Failed to acquire semaphore[d1fadd80|1|100], AE_TIME
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
Can you post the exact make and model of your laptop?
What led you to use the pci=routeirq settings on boot?
What happens if you ammend the boot kernel command from pci=routeirq to acpi=off?
What version of ndiswrapper are you using, the one that came with SuSE, or via an updated source package?
Is this SuSE 10 final release, or a beta version that you are using?
What led you to use the pci=routeirq settings on boot?
What happens if you ammend the boot kernel command from pci=routeirq to acpi=off?
What version of ndiswrapper are you using, the one that came with SuSE, or via an updated source package?
Is this SuSE 10 final release, or a beta version that you are using?
Sorry it's taken a while to respond... when I tried acpi=off I got all kinds of bad messages like DMA timeout , cant' load thermal module, can load fan module, and IDE failure. Most of the time I could not even boot. My only option was to reload Linux. It's working fine again now.
To answer your questions...
My laptop is an IBM Thinkpad 600E type 2645-8AU
I downloaded SUSE Linux 10.0 Eval version from http://www.novell.com/products/suselinux/downloads/suse_linux/index.html
I used pci=routeirq because dmesg reported:
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
I used the ndis wrapper that came with SuSE 10.0.
This is what it reported:
linux:/ # /usr/sbin/ndiswrapper -i /home/malcolm/windriver/airplup.inf
Installing airplus
linux:/ # /usr/sbin/ndiswrapper -l
Installed ndis drivers:
airplus driver present
linux:/ # /sbin/modprobe ndiswrapper
linux:/ # dmesg
.
.
.
ndiswrapper: module not supported by Novell, setting U taint flag.
ndiswrapper version 1.2 loaded (preempt=no,smp=no)
Before trying acpi=off I was getting...
Yenta TI: socket 0000:00:02.0, mfunc 0xfba97543, devctl 0x62
Yenta TI: socket 0000:00:02.0 probing PCI interrupt failed, trying to fix
Yenta TI: socket 0000:00:02.0 no PCI interrupts. Fish. Please report.
Yenta: no PCI IRQ, CardBus support disabled for this socket.
But when I was able to boot I got...
PCI: Found IRQ 11 for device 0000:00:02.0
PCI: Sharing IRQ with 0000:00:06.0
PCI: Sharing IRQ with 0000:01:00.0
PCI: Found IRQ 11 for device 0000:00:02.1
.
.
Yenta: CardBus bridge found at 0000:00:02.0 [1014:00eb]
Yenta: Enabling burst memory read transactions
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:02.0, mfunc 0xfba97543, devctl 0x62
Yenta: ISA IRQ mask 0x06b8, PCI irq 11
Socket status: 30000006
PCI: Found IRQ 11 for device 0000:00:02.1
PCI: Sharing IRQ with 0000:00:06.0
PCI: Sharing IRQ with 0000:01:00.0
Yenta: CardBus bridge found at 0000:00:02.1 [1014:00eb]
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:02.1, mfunc 0xfba97543, devctl 0x62
Yenta: ISA IRQ mask 0x06b8, PCI irq 11
Socket status: 30000020
.
.
But still no power on the card.
With all the other failures that got reported I had to re-install...
To answer your questions...
My laptop is an IBM Thinkpad 600E type 2645-8AU
I downloaded SUSE Linux 10.0 Eval version from http://www.novell.com/products/suselinux/downloads/suse_linux/index.html
I used pci=routeirq because dmesg reported:
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
I used the ndis wrapper that came with SuSE 10.0.
This is what it reported:
linux:/ # /usr/sbin/ndiswrapper -i /home/malcolm/windriver/airplup.inf
Installing airplus
linux:/ # /usr/sbin/ndiswrapper -l
Installed ndis drivers:
airplus driver present
linux:/ # /sbin/modprobe ndiswrapper
linux:/ # dmesg
.
.
.
ndiswrapper: module not supported by Novell, setting U taint flag.
ndiswrapper version 1.2 loaded (preempt=no,smp=no)
Before trying acpi=off I was getting...
Yenta TI: socket 0000:00:02.0, mfunc 0xfba97543, devctl 0x62
Yenta TI: socket 0000:00:02.0 probing PCI interrupt failed, trying to fix
Yenta TI: socket 0000:00:02.0 no PCI interrupts. Fish. Please report.
Yenta: no PCI IRQ, CardBus support disabled for this socket.
But when I was able to boot I got...
PCI: Found IRQ 11 for device 0000:00:02.0
PCI: Sharing IRQ with 0000:00:06.0
PCI: Sharing IRQ with 0000:01:00.0
PCI: Found IRQ 11 for device 0000:00:02.1
.
.
Yenta: CardBus bridge found at 0000:00:02.0 [1014:00eb]
Yenta: Enabling burst memory read transactions
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:02.0, mfunc 0xfba97543, devctl 0x62
Yenta: ISA IRQ mask 0x06b8, PCI irq 11
Socket status: 30000006
PCI: Found IRQ 11 for device 0000:00:02.1
PCI: Sharing IRQ with 0000:00:06.0
PCI: Sharing IRQ with 0000:01:00.0
Yenta: CardBus bridge found at 0000:00:02.1 [1014:00eb]
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:02.1, mfunc 0xfba97543, devctl 0x62
Yenta: ISA IRQ mask 0x06b8, PCI irq 11
Socket status: 30000020
.
.
But still no power on the card.
With all the other failures that got reported I had to re-install...
Ooops! I took your beginning line on your last post as it was working. Let's try an experiment from my experience on another distro.
Try running as root user;
cardctl info. See if it produces any output at all. In my Thinkpad, it showed;
MANFID = 0271,0012
Then make ndiswrapper use the pcmcia device with the -d command manufacturer's id;
ndiswrapper -d 0271:0012 net5211
Where 0271:0012 is the code that was returend in your cardctl command, and net5211 is the name of your ndiswrapper module that you get when doing ndiswrapper -l (the list command).
Of course, what quetion I did not ask, is what exact Windows driver did you use to install with ndiswrapper -i? Was it the Windows XP driver from your driver cd, or something else?
I also assume you did modprobe ndiswrapper after installing the drivers, to load the module? Did you follow the generic ndiswrapper instructions, or the SuSE specific ones?
Were the .inf and .sys files both in the source directory when you ran the install command for ndsiwrapper?
Try running as root user;
cardctl info. See if it produces any output at all. In my Thinkpad, it showed;
MANFID = 0271,0012
Then make ndiswrapper use the pcmcia device with the -d command manufacturer's id;
ndiswrapper -d 0271:0012 net5211
Where 0271:0012 is the code that was returend in your cardctl command, and net5211 is the name of your ndiswrapper module that you get when doing ndiswrapper -l (the list command).
Of course, what quetion I did not ask, is what exact Windows driver did you use to install with ndiswrapper -i? Was it the Windows XP driver from your driver cd, or something else?
I also assume you did modprobe ndiswrapper after installing the drivers, to load the module? Did you follow the generic ndiswrapper instructions, or the SuSE specific ones?
Were the .inf and .sys files both in the source directory when you ran the install command for ndsiwrapper?
Thanks for the response, danleff!! Here are the answers to your questions....
When I issue "cardctl info" I get:
cardctl: command not found
I used the Windows XP driver from the install CD (actually I downloaded them from D-Link as a zip, then unzipped them to CD).
Yes, I did "modprobe ndiswrapper" after installing the drivers.
To install the drivers I used:
/usr/sbin/ndiswrapper -i /home/malcolm/DWL650/Drivers/WinXP/AIRPLUS.INF
I previously coppied the CD to DWL650 in my home directory. The WinXP directory contains the following files:
AIRPLUS.CAT
AIRPLUS.INF
AIRPLUS.SYS
RADIO0d.BIN
RADIO11.BIN
RADIO15.BIN
WLANGEN.bin
When I issue "cardctl info" I get:
cardctl: command not found
I used the Windows XP driver from the install CD (actually I downloaded them from D-Link as a zip, then unzipped them to CD).
Yes, I did "modprobe ndiswrapper" after installing the drivers.
To install the drivers I used:
/usr/sbin/ndiswrapper -i /home/malcolm/DWL650/Drivers/WinXP/AIRPLUS.INF
I previously coppied the CD to DWL650 in my home directory. The WinXP directory contains the following files:
AIRPLUS.CAT
AIRPLUS.INF
AIRPLUS.SYS
RADIO0d.BIN
RADIO11.BIN
RADIO15.BIN
WLANGEN.bin
OK, what is the output when you type ndiswrapper -l?
You should get a message like;
Installed ndis drivers:
xxxxxx driver present, hardware present
Where xxxxxx is the name of the driver.
Consult the SuSE 10 specific ndiswrapper instructions, located here.
If the message of ndiswrapper -l is OK, then follow the rest of the directions. If not, post what you found.
Finally, do you have the wireless tools package installed in your SuSE installation? Consult the begining of the instructions from the link above and let us know what point you are at.
You should get a message like;
Installed ndis drivers:
xxxxxx driver present, hardware present
Where xxxxxx is the name of the driver.
Consult the SuSE 10 specific ndiswrapper instructions, located here.
If the message of ndiswrapper -l is OK, then follow the rest of the directions. If not, post what you found.
Finally, do you have the wireless tools package installed in your SuSE installation? Consult the begining of the instructions from the link above and let us know what point you are at.
Yes, I have the wireless tools package installed.
Yes, I'm following SuSE 10 specific ndiswrapper instructions.
Here's the responses to the various commands you were asking about and/or part of the SuSE specific instructions.
Linux:~ # ndiswrapper -l
Installed ndis drivers:
airplus driver present
Linux:~ # depmod -a
(long pause then...)
Linux:~ #
Linux:~ # modprobe ndiswrapper
(short pause then...)
Linux:~ #
Linux:~ # dmesg | grep ndiswrapper
ndiswrapper: module not supported by Novell, setting U taint flag.
ndiswrapper version 1.2 loaded (preempt=no,smp=no)
Linux:~ #
Linux:~ # dmesg | grep Yenta
Yenta: CardBus bridge found at 0000:00:02.0 [1014:00eb]
Yenta: Enabling burst memory read transactions
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:02.0, mfunc 0xfba97543, devctl 0x62
Yenta TI: socket 0000:00:02.0 probing PCI interrupt failed, trying to fix
Yenta TI: socket 0000:00:02.0 no PCI interrupts. Fish. Please report.
Yenta: no PCI IRQ, CardBus support disabled for the socket.
Yenta: check your BIOS CardBus, BIOS IRQ or ACPI settings.
Yenta: ISA IRQ mask 0x0438, PCI irq 0
Yenta: CardBus bridge found at 0000:00:02.1 [1014:00eb]
Yenta: Enabling burst memory read transactions
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:02.1, mfunc 0xfba97543, devctl 0x62
Yenta TI: socket 0000:00:02.1 probing PCI interrupt failed, trying to fix
Yenta TI: socket 0000:00:02.1 no PCI interrupts. Fish. Please report.
Yenta: no PCI IRQ, CardBus support disabled for the socket.
Yenta: check your BIOS CardBus, BIOS IRQ or ACPI settings.
Yenta: ISA IRQ mask 0x0438, PCI irq 0
Linux:~ #
What it looks like to me is that my card is not even recognized as being present. If you remember, when I set acpi=off I did get a response to IRQ 11 (as shown below)...but I'm not about to set acpi=off again as it trashed my system and I had to reinstall SuSU to even get it to boot.
Yenta: CardBus bridge found at 0000:00:02.0 [1014:00eb]
Yenta: Enabling burst memory read transactions
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:02.0, mfunc 0xfba97543, devctl 0x62
Yenta: ISA IRQ mask 0x06b8, PCI irq 11
Socket status: 30000006
PCI: Found IRQ 11 for device 0000:00:02.1
PCI: Sharing IRQ with 0000:00:06.0
PCI: Sharing IRQ with 0000:01:00.0
Yenta: CardBus bridge found at 0000:00:02.1 [1014:00eb]
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:02.1, mfunc 0xfba97543, devctl 0x62
Yenta: ISA IRQ mask 0x06b8, PCI irq 11
Socket status: 30000020
Yes, I'm following SuSE 10 specific ndiswrapper instructions.
Here's the responses to the various commands you were asking about and/or part of the SuSE specific instructions.
Linux:~ # ndiswrapper -l
Installed ndis drivers:
airplus driver present
Linux:~ # depmod -a
(long pause then...)
Linux:~ #
Linux:~ # modprobe ndiswrapper
(short pause then...)
Linux:~ #
Linux:~ # dmesg | grep ndiswrapper
ndiswrapper: module not supported by Novell, setting U taint flag.
ndiswrapper version 1.2 loaded (preempt=no,smp=no)
Linux:~ #
Linux:~ # dmesg | grep Yenta
Yenta: CardBus bridge found at 0000:00:02.0 [1014:00eb]
Yenta: Enabling burst memory read transactions
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:02.0, mfunc 0xfba97543, devctl 0x62
Yenta TI: socket 0000:00:02.0 probing PCI interrupt failed, trying to fix
Yenta TI: socket 0000:00:02.0 no PCI interrupts. Fish. Please report.
Yenta: no PCI IRQ, CardBus support disabled for the socket.
Yenta: check your BIOS CardBus, BIOS IRQ or ACPI settings.
Yenta: ISA IRQ mask 0x0438, PCI irq 0
Yenta: CardBus bridge found at 0000:00:02.1 [1014:00eb]
Yenta: Enabling burst memory read transactions
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:02.1, mfunc 0xfba97543, devctl 0x62
Yenta TI: socket 0000:00:02.1 probing PCI interrupt failed, trying to fix
Yenta TI: socket 0000:00:02.1 no PCI interrupts. Fish. Please report.
Yenta: no PCI IRQ, CardBus support disabled for the socket.
Yenta: check your BIOS CardBus, BIOS IRQ or ACPI settings.
Yenta: ISA IRQ mask 0x0438, PCI irq 0
Linux:~ #
What it looks like to me is that my card is not even recognized as being present. If you remember, when I set acpi=off I did get a response to IRQ 11 (as shown below)...but I'm not about to set acpi=off again as it trashed my system and I had to reinstall SuSU to even get it to boot.
Yenta: CardBus bridge found at 0000:00:02.0 [1014:00eb]
Yenta: Enabling burst memory read transactions
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:02.0, mfunc 0xfba97543, devctl 0x62
Yenta: ISA IRQ mask 0x06b8, PCI irq 11
Socket status: 30000006
PCI: Found IRQ 11 for device 0000:00:02.1
PCI: Sharing IRQ with 0000:00:06.0
PCI: Sharing IRQ with 0000:01:00.0
Yenta: CardBus bridge found at 0000:00:02.1 [1014:00eb]
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:02.1, mfunc 0xfba97543, devctl 0x62
Yenta: ISA IRQ mask 0x06b8, PCI irq 11
Socket status: 30000020
You are correct.
You apparently got the following;
Linux:~ # ndiswrapper -l
Installed ndis drivers:
airplus driver present
You should have gotten;
Linux:~ # ndiswrapper -l
Installed ndis drivers:
airplus driver present, hardware present
You also got;
Linux:~ # dmesg | grep ndiswrapper
ndiswrapper: module not supported by Novell, setting U taint flag.
ndiswrapper version 1.2 loaded (preempt=no,smp=no)
There is no use going on, if the ndiswrapper -l command does not show that the hardware is detected.
From the directions;
Quote:Where 'present' means that you have a card that can be used with the driver installed. In this case, marvell driver mrv8335 is used. If you see 'cannot locate lspci. Unable to see if hardware is present', you need to install the pciutils package.
Did you install, or have installed, the pciutils package?
If yes, or you now installed the pciutils package, try unloading the driver with;
ndsiwrapper -e AIRPLUS
Then install the driver again with;
ndiswrapper -i AIRPLUS.INF
Do ndiswrapper -l and see if the hardware is present now.
You apparently got the following;
Linux:~ # ndiswrapper -l
Installed ndis drivers:
airplus driver present
You should have gotten;
Linux:~ # ndiswrapper -l
Installed ndis drivers:
airplus driver present, hardware present
You also got;
Linux:~ # dmesg | grep ndiswrapper
ndiswrapper: module not supported by Novell, setting U taint flag.
ndiswrapper version 1.2 loaded (preempt=no,smp=no)
There is no use going on, if the ndiswrapper -l command does not show that the hardware is detected.
From the directions;
Quote:Where 'present' means that you have a card that can be used with the driver installed. In this case, marvell driver mrv8335 is used. If you see 'cannot locate lspci. Unable to see if hardware is present', you need to install the pciutils package.
Did you install, or have installed, the pciutils package?
If yes, or you now installed the pciutils package, try unloading the driver with;
ndsiwrapper -e AIRPLUS
Then install the driver again with;
ndiswrapper -i AIRPLUS.INF
Do ndiswrapper -l and see if the hardware is present now.
Yes, I already have the pciutils package installed.
I uninstalled and reinstalled AIRPLUS as you suggested but ndiswrapper -l still shows:
Linux:~ # ndiswrapper -l
Installed ndis drivers:
airplus driver present
Linux:~ #
i.e doesn't report "hardware present". Both uninstall and install processes worked fine and ndiswrapper reported no driver installed and then driver installed as expected.
I uninstalled and reinstalled AIRPLUS as you suggested but ndiswrapper -l still shows:
Linux:~ # ndiswrapper -l
Installed ndis drivers:
airplus driver present
Linux:~ #
i.e doesn't report "hardware present". Both uninstall and install processes worked fine and ndiswrapper reported no driver installed and then driver installed as expected.
Ok, let's try my above suggestions using the pccardctl command, rather than the cardctl one. Apparently, the manager has been changed in SuSE 10.
If this works, load the module (modprobe ndiswrapper). Then check the dmesg output. Look at the ndiswrapper troubleshooting page to see if you get output, such as in the example.
The correct command options can be found by typing in man pccardctl, or by looking at this readme.
However, i have the feeling that I am missing something, or that you need to uninstall SuSE's ndiswrapper and install the sorce package.
One final question. Do you have either the kernel headers or source package(s) installed in this system?
If this works, load the module (modprobe ndiswrapper). Then check the dmesg output. Look at the ndiswrapper troubleshooting page to see if you get output, such as in the example.
The correct command options can be found by typing in man pccardctl, or by looking at this readme.
However, i have the feeling that I am missing something, or that you need to uninstall SuSE's ndiswrapper and install the sorce package.
One final question. Do you have either the kernel headers or source package(s) installed in this system?
Yes, I have the kernel source package installed.
I tried pccardctl info and it reports:
PRODID_1=""
PRODID_2=""
PRODID_3=""
PRODID_4=""
MANFID-0000,0000
FUNCID=255
PRODID_1=""
PRODID_2=""
PRODID_3=""
PRODID_4=""
MANFID-0000,0000
FUNCID=255
dmesg still reports: module not supported my Novell, setting U taint flag.
I'm still thinking that it's not the driver; it's way before that when the machine detects insertion or the presence of a card and assigns/detects an IRQ. For some reason the card is not being detected at all. When Windoze boots it does power on the card and recognize that a card is present before it starts looking for a driver, but when I boot SuSE it doesn't even power on the card or acknowledge its presence at all!
I'm still suspicious about the Yenta messages in dmesg:
Yenta TI: socket 0000:00:02.0, mfunc 0xfba97543, devctl 0x62
Yenta TI: socket 0000:00:02.0 probing PCI interrupt failed, trying to fix
Yenta TI: socket 0000:00:02.0 no PCI interrupts. Fish. Please report.
Yenta: no PCI IRQ, CardBus support disabled for the socket.
Do you think that getting the right driver installed going to fix this?
BTW, for most of the pccardctl options I get "not yet handled by pccardctl".
I tried pccardctl info and it reports:
PRODID_1=""
PRODID_2=""
PRODID_3=""
PRODID_4=""
MANFID-0000,0000
FUNCID=255
PRODID_1=""
PRODID_2=""
PRODID_3=""
PRODID_4=""
MANFID-0000,0000
FUNCID=255
dmesg still reports: module not supported my Novell, setting U taint flag.
I'm still thinking that it's not the driver; it's way before that when the machine detects insertion or the presence of a card and assigns/detects an IRQ. For some reason the card is not being detected at all. When Windoze boots it does power on the card and recognize that a card is present before it starts looking for a driver, but when I boot SuSE it doesn't even power on the card or acknowledge its presence at all!
I'm still suspicious about the Yenta messages in dmesg:
Yenta TI: socket 0000:00:02.0, mfunc 0xfba97543, devctl 0x62
Yenta TI: socket 0000:00:02.0 probing PCI interrupt failed, trying to fix
Yenta TI: socket 0000:00:02.0 no PCI interrupts. Fish. Please report.
Yenta: no PCI IRQ, CardBus support disabled for the socket.
Do you think that getting the right driver installed going to fix this?
BTW, for most of the pccardctl options I get "not yet handled by pccardctl".
Yep, you are again correct. The issue, I think, is that the PCMCIA port on your laptop is not being sensed correctly. Try doing a search on google, or your favorite search engine on "Linux Thinkpad 600E."
Your last command results post confirm this.
I'll look around, as well. It most likely has to do with the PCMCIA chipset in the system and the ability of SuSE to detect it. There must be a kernel command setting to fix this, such as one like I asked you to try. Also realize, that these old Thinkpads were made to work with Windows, so that Linux support was not thought of at the time.
Your last command results post confirm this.
I'll look around, as well. It most likely has to do with the PCMCIA chipset in the system and the ability of SuSE to detect it. There must be a kernel command setting to fix this, such as one like I asked you to try. Also realize, that these old Thinkpads were made to work with Windows, so that Linux support was not thought of at the time.
On mine, pccarddtl config shows:
Socket 0:
command 'config' not yet handled by pccardctl
It's almost like the command fails once it gets to Socket 1, which is where I believe my card is located.
also, pccardctl ident shows:
Socket 0:
no product info available
Socket 1:
no product info available
lspci -H1 doesn't list my card eithr. All it shows is the bridge for each slot:
00:00.0 Host bridge: Intel Corporation 440BX/2X/DX - 82443BX/2X/DX Host bridge (rev 03)
00:01.0 PCI bridge: Intel Corporation 440BX/2X/DX - 82443BX/2X/DX AGP bridge (rev 03)
00:02.0 CardBus bridge: Texas Instruments PCI1251A
00:02.1 CardBus bridge: Texas Instruments PCI1251A
BTW, when I insert my non-CardBus PCMCIA 3COM modem card, it is detected and pccardctl ident reports it in socket 1.
I've done quite a bit of searching on Google for thinkpad 600E Linux and haven't found this particular problem, but I'll keep looking.
[Edited by skyspeedr on 2006-04-06 06:02:38]
Socket 0:
command 'config' not yet handled by pccardctl
It's almost like the command fails once it gets to Socket 1, which is where I believe my card is located.
also, pccardctl ident shows:
Socket 0:
no product info available
Socket 1:
no product info available
lspci -H1 doesn't list my card eithr. All it shows is the bridge for each slot:
00:00.0 Host bridge: Intel Corporation 440BX/2X/DX - 82443BX/2X/DX Host bridge (rev 03)
00:01.0 PCI bridge: Intel Corporation 440BX/2X/DX - 82443BX/2X/DX AGP bridge (rev 03)
00:02.0 CardBus bridge: Texas Instruments PCI1251A
00:02.1 CardBus bridge: Texas Instruments PCI1251A
BTW, when I insert my non-CardBus PCMCIA 3COM modem card, it is detected and pccardctl ident reports it in socket 1.
I've done quite a bit of searching on Google for thinkpad 600E Linux and haven't found this particular problem, but I'll keep looking.
[Edited by skyspeedr on 2006-04-06 06:02:38]
I've tried both sockets and neither one recognizes CardBus cards. I've tried other CardBus cards too and they're not recognized either.
I'm thinking that the reason it says CardBus cards not supported has to do with this error:
Yenta: CardBus bridge found at 0000:00:02.1 [1014:00eb]
Yenta: Enabling burst memory read transactions
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:02.1, mfunc 0xfba97543, devctl 0x62
Yenta TI: socket 0000:00:02.1 probing PCI interrupt failed, trying to fix
Yenta TI: socket 0000:00:02.1 no PCI interrupts. Fish. Please report.
Yenta: no PCI IRQ, CardBus support disabled for the socket.
Yenta: check your BIOS CardBus, BIOS IRQ or ACPI settings.
Unless you think that SuSE 10.0 just doesn't support CardBus cards at all. I'd be very surprised if that was true.
To me it seems like the PCI bridge is having trouble getting an IRQ. I'll keep looking, but thanks for your help so far! I've learned a lot, and I'm sure the solution (when I find it) is going to help a lot of other people.
I'm thinking that the reason it says CardBus cards not supported has to do with this error:
Yenta: CardBus bridge found at 0000:00:02.1 [1014:00eb]
Yenta: Enabling burst memory read transactions
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:02.1, mfunc 0xfba97543, devctl 0x62
Yenta TI: socket 0000:00:02.1 probing PCI interrupt failed, trying to fix
Yenta TI: socket 0000:00:02.1 no PCI interrupts. Fish. Please report.
Yenta: no PCI IRQ, CardBus support disabled for the socket.
Yenta: check your BIOS CardBus, BIOS IRQ or ACPI settings.
Unless you think that SuSE 10.0 just doesn't support CardBus cards at all. I'd be very surprised if that was true.
To me it seems like the PCI bridge is having trouble getting an IRQ. I'll keep looking, but thanks for your help so far! I've learned a lot, and I'm sure the solution (when I find it) is going to help a lot of other people.
Let's go back a little. Do you have the acpi=noirq command in Grub at the end of the kernel command line?
kernel (hdx,x)..... root=/dev/hdax... acpi=noirq
The line is just an example, but make sure that there is a space between the last entry and the acpi=noirq line.
See if the yenta line errors go away.
If not, try going into the bios and disabling the quickboot option.
kernel (hdx,x)..... root=/dev/hdax... acpi=noirq
The line is just an example, but make sure that there is a space between the last entry and the acpi=noirq line.
See if the yenta line errors go away.
If not, try going into the bios and disabling the quickboot option.
SUCCESS!! I tried your acpi=noirq suggestion and ZAM! the card powered up! I checked dmesg and the Yenta errors have gone and I now have IRQ 11 assigned to the sockets. ndiswrapper -l now shows "hardware present" although pccardctl info still shows nothing. However, I issued modprobe ndiswrapper and the card came alive! I went into YaST>Network Devices>Network Card and amazingly it shows an entry for my D-Link DWL-650+ card! So I set up the paramaters for my network and checked iwconfig and it looks like its found my wireless router, but being a Linux newbie I don't know how to tell if it's actually communicating. So I fired up Firefox to see if I could get anything, but no luck. I'm so close, but where do I go from here?
Ok, so now the question is, do you know the settings for your router?
When you set up your card in Windows, most likely you used an installation cd disk which helped set up these values. You need to know what the router (or modem) ESSID is and if you are using WEP or WPA encription, what the password is.
Also, does your ISP use a static or dynamic assignment of the IP addresss? Yes, you need to set these values to actually allow the card to access the modem/router. If you edit the settings for the wireless card in Yast, there is a tab where you can set these values. If you ISP uses dynamic assignment, then you chose auto DHCP when you do the settings in Yast, such as with broadband.
The final catch is what your ISP is. Is it DSL or broadband?
If DSL, you need to set up your username and password, if you have to use these for DSL, such as mine (Verizon). You can do this in Yast, as well.
You are about 1/2 way there! thought it was going to be easy?
When you set up your card in Windows, most likely you used an installation cd disk which helped set up these values. You need to know what the router (or modem) ESSID is and if you are using WEP or WPA encription, what the password is.
Also, does your ISP use a static or dynamic assignment of the IP addresss? Yes, you need to set these values to actually allow the card to access the modem/router. If you edit the settings for the wireless card in Yast, there is a tab where you can set these values. If you ISP uses dynamic assignment, then you chose auto DHCP when you do the settings in Yast, such as with broadband.
The final catch is what your ISP is. Is it DSL or broadband?
If DSL, you need to set up your username and password, if you have to use these for DSL, such as mine (Verizon). You can do this in Yast, as well.
You are about 1/2 way there! thought it was going to be easy?
