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
Yes, I know the settings for my router. I'm using WEP and I set up the YaST panel to match my network; i.e. I set the Operating Mode (Ad-hoc), entered my ESSID, and set Authentication Mode to "Shared Key" and entered my encryption key (5 digits in ASCII). I have 3 other (Windows) computers connected to this router with the above settings. The router is connected to a cable modem and my ISP uses dynamic IP addressing so the router is set up as a DHCP client on the WAN side to get the router address from the ISP. Then on the LAN side I have the the DHCP server set up on the router to assign IP addresses to the computers that connect to it. So what I'm looking for is a Linux command (like Window's IPCONFIG) or program that will list the IP address assigned to the WLAN card to confirm that it's connected. I did find the ifconfig command that looks like what I need: the lo entry shows inet addr:127.0.0.1 for the local loopback, however, the wlan0 entry doesn't show an IP address. It shows:
wlan0 Link encap:Ethernet HWaddr 00:40...(my correct MAC address)
inet6 addr: fe80::240:5ff..... Scope:Link
and then the TX and RX packet stats (which change so it looks like it's communicating).
So I'm thinking that the card has not got an IP address from the router because I would expect to see an address for my local network (like 192.168.0.xxx) here.
Also, is there an app I can run in Linux that will give me the ability to visiually monitory my connection status from the GNOME desktop?
wlan0 Link encap:Ethernet HWaddr 00:40...(my correct MAC address)
inet6 addr: fe80::240:5ff..... Scope:Link
and then the TX and RX packet stats (which change so it looks like it's communicating).
So I'm thinking that the card has not got an IP address from the router because I would expect to see an address for my local network (like 192.168.0.xxx) here.
Also, is there an app I can run in Linux that will give me the ability to visiually monitory my connection status from the GNOME desktop?
It looks like the card is not configured correctly. I think that I know the problem. Is the WEP key on the router set in ASCII or Hex code?
The command to look at the wireless side and what it is currently set at is iwconfig. If possible, post what that says, or if it shows wlan0. It should look something like;
wlan0 IEEE 802.11b ESSID:""
Mode:Master Channel: 0 Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power:50 dBm Sensitivity=0/3
Retry: off RTS thr: off Fragment thr: off
Encryption key: off
Power Management: off
Link Quality=0/94 Signal level=-95 dBm Noise level=-95 dBm
Rx invalid nwid:0 Rx invalid crypt: 0 Rx invalid frag: 0
Tx excessive retries:0 Invalid misc: 0 Missed beacon: 0
If the Encription line has extra numbers in it (more than the actual ones that you put in, say extra zeros at the start), then you probably have a hex WEP password.
The ESSID line shoulkd not be like the example, but have the actual ESSID value in it between the quotes. But, if possible, post what you have and we can go from there.
The command to look at the wireless side and what it is currently set at is iwconfig. If possible, post what that says, or if it shows wlan0. It should look something like;
wlan0 IEEE 802.11b ESSID:""
Mode:Master Channel: 0 Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power:50 dBm Sensitivity=0/3
Retry: off RTS thr: off Fragment thr: off
Encryption key: off
Power Management: off
Link Quality=0/94 Signal level=-95 dBm Noise level=-95 dBm
Rx invalid nwid:0 Rx invalid crypt: 0 Rx invalid frag: 0
Tx excessive retries:0 Invalid misc: 0 Missed beacon: 0
If the Encription line has extra numbers in it (more than the actual ones that you put in, say extra zeros at the start), then you probably have a hex WEP password.
The ESSID line shoulkd not be like the example, but have the actual ESSID value in it between the quotes. But, if possible, post what you have and we can go from there.
OK, here's the actual iwconfig output:
wlan0 IEEE 802.11b ESSID:"malcbren" Nickname:"Linux"
Mode:Ad-Hoc Frequency:2.437 GHz Cell: C2:A8:2E:6C:A9:23
Bit Rate:22 Mb/s Tx-Power:0 dBm Sensitivity=0/3
RTS thr:4096 B Fragment thr:4096 B
Encryption key: 3732-3235-36
Power Management: off
Link Quality=93/100 Signal level=-100 dBm Noise level=-256 dBm
Rx invalid nwid:0 Rx invalid crypt: 0 Rx invalid frag: 0
Tx excessive retries:3 Invalid misc:8 Missed beacon: 0
The encrypion key is correct. Even though I entered it as 5 ASCII numbers (and clicked the ASCII radio button on the panel), the HEX representaton of it above is correct.
On my router there is no trace of my MAC address anywhere. It doesn't show up in the DHCP client list, neither does it show up in the wireless status of PC's connected to the AP.
Looking at the iwconfig output it looks to me like the transmission power is set to 0. How do you change that?
[Edited by skyspeedr on 2006-04-08 16:09:37]
wlan0 IEEE 802.11b ESSID:"malcbren" Nickname:"Linux"
Mode:Ad-Hoc Frequency:2.437 GHz Cell: C2:A8:2E:6C:A9:23
Bit Rate:22 Mb/s Tx-Power:0 dBm Sensitivity=0/3
RTS thr:4096 B Fragment thr:4096 B
Encryption key: 3732-3235-36
Power Management: off
Link Quality=93/100 Signal level=-100 dBm Noise level=-256 dBm
Rx invalid nwid:0 Rx invalid crypt: 0 Rx invalid frag: 0
Tx excessive retries:3 Invalid misc:8 Missed beacon: 0
The encrypion key is correct. Even though I entered it as 5 ASCII numbers (and clicked the ASCII radio button on the panel), the HEX representaton of it above is correct.
On my router there is no trace of my MAC address anywhere. It doesn't show up in the DHCP client list, neither does it show up in the wireless status of PC's connected to the AP.
Looking at the iwconfig output it looks to me like the transmission power is set to 0. How do you change that?
[Edited by skyspeedr on 2006-04-08 16:09:37]
OK, I'm at a disadvantage right now. I don't have SuSE available to me, as my system will not be totally set up until those taxes are in. It looks like you have an AP, WEP key (which is correct) and ESSID.
You have no IP address when doing ifconfig
I may have missed this, but you have a broadband connection? Not DSL, correct? Which ISP provider?
I can't remember the correct command to bring the network up in SuSE (too many distros...)
You set up the wireless card to activate at boot (auto DHCP at boot) in Yast?
If not, try the following at the command line, as root user;
dhclient wlan0
If this returns ok, then see if ifconfig shows an IP address.
You have no IP address when doing ifconfig
I may have missed this, but you have a broadband connection? Not DSL, correct? Which ISP provider?
I can't remember the correct command to bring the network up in SuSE (too many distros...)
You set up the wireless card to activate at boot (auto DHCP at boot) in Yast?
If not, try the following at the command line, as root user;
dhclient wlan0
If this returns ok, then see if ifconfig shows an IP address.
SUCCESS!! This post is via a working DWL 650+ on SuSE Linux 10.0!!!
OK, here's what I did...
First off, I found the KWiFiMan application and discovered that my network was being seen (along with several other networks) except that there was no connection, and obviously no IP address reported. So I set up a static IP address on the router for the MAC address of the card, and then set that address in the YaST setup dialog. Still no success. So I tried experimenting with the card setup in YaST and observing the behavior of the card using KWiFiMan. I changed the Operating Mode to "Managed" instead of "Ad-Hoc" (my Windows PC's are set up as Ad-Hoc) and WHAM!! I was connected!!! I could access the router but not the Internet, so I went back into YaST and set up "Name Server 1" with the LAN address of my router (192.168.0.1) and BINGO!! I was up and running!!
Thanks very much for all your help!! I could not have done it without you!!
[Edited by skyspeedr on 2006-04-10 00:29:37]
OK, here's what I did...
First off, I found the KWiFiMan application and discovered that my network was being seen (along with several other networks) except that there was no connection, and obviously no IP address reported. So I set up a static IP address on the router for the MAC address of the card, and then set that address in the YaST setup dialog. Still no success. So I tried experimenting with the card setup in YaST and observing the behavior of the card using KWiFiMan. I changed the Operating Mode to "Managed" instead of "Ad-Hoc" (my Windows PC's are set up as Ad-Hoc) and WHAM!! I was connected!!! I could access the router but not the Internet, so I went back into YaST and set up "Name Server 1" with the LAN address of my router (192.168.0.1) and BINGO!! I was up and running!!
Thanks very much for all your help!! I could not have done it without you!!
[Edited by skyspeedr on 2006-04-10 00:29:37]
