skyspeedr

I'm trying to install ndiswrapper version 1.14 on Red Hat 9 kernel 2.4.20-8 but I'm getting "unresolved symbol" errors when I issue modprobe ndiswrapper. I've read several posts about this error and it seems to be related to having a difference in kernel versions. I've tried a couple of suggestions but have not been able to resolve it. Does anyone have a simple solution for this?

OK. So I either have to update my kernel to 2.4.26 or find a verson of ndiswrapper that's compatible with 2.4.20. Which would be easier to do?

I have SuSE Linux 10.0 installed but the sound card is not working. When I try to set up my sound card in YaST2 I get the message "It seems that you have a Thinkpad 600E laptop. On this laptop, the CS4236 driver should be used although the CS46xx chip is detected. Attempt to probe the configuration of CS4236 driver?". When I answer "Yes" and the probe finishes I get a panel that says "An error occurred during the installation of CD4610 SoundFurion Audio Accelerator. This can be caused by incorrect module parameters, including invalid IO or IRQ parameters. How do I find out what the problem is with the paramaters, and how do I change them?

OK, I've been looking at lots of sites where they talk about how to get sound working on a TP600E, but nothing has worked for me, so... I installed Red Hat Linux in a new partition on my 600E and entered the commands: insmod sound insmod ad1848 insmod uart401 insmod cs4232 0x530 irq=5 dma=1 dma2=0 And presto! I have sound!! Now, why won't this work with SuSE 10.0???

I also tried running alsaconf and here's the result: Linux:~ # alsaconf Following card(s) are found or your system. Choose a soundcard to configure: cs46xx -- Cirrus Logic CS 4610/11 [CrystalClear SoundFusion Audio Accelerator legacy -- Probe legacy ISA (non-PnP) chips If I try the legacy probe it doesn't find any cards. If I try cs46xx it reports the (esd) output below and then says: Now ALSA is ready to use. For adjustment of volumes, use your favorite mixer. But none of the sound mixer programs work. They all report that no device is found, or "Cannot connect to sound daemon. Please run ‘esd’ at command prompt." When I run esd this is the output. Linux:~ # esd ALSA lib confmisc.c:672:(snd_func_card_driver) cannot find card '0' ALSA lib conf.c:3493:(_snd_config_evaluate) function snd_func_card_driver returned error: No such device ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:3493:(_snd_config_evaluate) function snd_func_concat returned error: No such device ALSA lib confmisc.c:955:(snd_func_refer) error evaluating name ALSA lib conf.c:3493:(_snd_config_evaluate) function snd_func_refer returned error: No such device ALSA lib conf.c:3962:(snd_config_expand) Evaluate error: No such device ALSA lib pcm.c:2094:(snd_pcm_open_noupdate) Unknown PCM default Linux:~ #

It was owned by root but did not have Execute priviledges. I changed it and now I get: Linux:~ # modprobe snd-cs4236 /usr/local/sbin/soundcard-on: line 53: /lib/alsa/modprobe-post-install: No such file or directory FATAL: Error running install command for snd_cs4236 Line 53 is at the end of the file. Here's snd-cs4236... #!/bin/bash # Sound-via-pnp-script for Thinkpad 600E and possibly other computers with onboard # CS4239/CS4610 that do not work with the PCI driver and are not recognized by the # PnP code of snd-cs4236 # search sound card pnp device for dev in /sys/bus/pnp/devices/* do grep CSC0100 $dev/id > /dev/null && WSSDEV=$dev grep CSC0110 $dev/id > /dev/null && CTLDEV=$dev done # activate devices (Thinkpad boots with devices disabled unless "fast boot" is turned off) echo activate > $WSSDEV/resources echo activate > $CTLDEV/resources # parse resource settings { read read bla port1 read bla port2 read bla port3 read bla irq read bla dma1 read bla dma2 # Hack: with PnPBIOS: ports are: port1: WSS, port2: OPL, port3: sb (unneeded) # with ACPI-PnP:ports are: port1: OPL, port2: sb, port3: WSS # (ACPI bios seems to be wrong here, the PnP-card-code in snd-cs4236.c uses the # PnPBIOS port order) # Detect port order using the fixed OPL port as reference if [ ${port2%%-*} = 0x388 ] then # PnPBIOS: usual order port=${port1%%-*} oplport=${port2%%-*} else # ACPI: mixed-up order port=${port3%%-*} oplport=${port1%%-*} fi } < $WSSDEV/resources { read read bla port1 cport=${port1%%-*} } < $CTLDEV/resources # load the module modprobe --ignore-install snd-cs4236 port=$port cport=$cport fm_port=$oplport irq=$irq dma1=$dma1 dma2=$dma2 isapnp=0 index=0 && /lib/alsa/modprobe-post-install snd-cs4236

My laptop is an IBM Thinkpad 600E type 2645-8AU I'm using the SuSE Linux 10.0 Eval version. I tried the following option from your first link (afer doing a BIOS reset and disabling quickboot). Added to /etc/modprobe.conf.local: options snd-cs4236 isapnp=0 cport=0x538 port=0x530 sb_port=0x220 fm_port=0x388 irq=5 dma1=1 dma2=0 alias snd-card-0 snd-cs4236 But this is the message I get from modprobe (as root): Linux:~ # modprobe snd-cs4236 sh: /usr/local/sbin/soundcard-on: Permission denied FATAL: Error running install command for snd_cs4236 Linux:~ # Then I tried the suggestion from the second link (set up using YaST): * used the CS4231 driver I/O = 0x530 * Irq = 5 * DMA1 = 1 * DMA2 = 0 * MPUIO = 0x330 * MPUIRQ =9 But no luck. I get the following error in YaST: "An error occurred during the installation of CS4231. The kernel module snd-cs4231 for sound support could not be loaded. This can be caused by incorrect module parameters, including invalid IO or IRQ parameters." -Same message I get when trying to set up the cs46xx device that shows up in YaST by default. I had already found your third link. But thanks for looking these up! You're right, though, the card does not seem to be detected as PnP.

Yes, I added the soundcard-on script to /usr/local/sbin/, and I modified the modprobe Configuration lines in /etc/modprobe.conf.local (comments in /etc/modprobe.conf tell you to add local modifications to /etc/modprobe.conf.local rather than modifying modprobe.conf directly, and the last line of /etc/modprobe.conf is include /etc/modprobe.conf.local). I even created the file /etc/modprobe.d/cs4236pnp file (which did not previously exist), using the lines added to /etc/modprobe.conf.local, and also copied soundcard-on to /usr/local/bin/ to see if that would help. I've tried booting with fastboot disabled and fastboot enabled. I only tried the terminal Window when nothing changed and I wanted to see what messages the commands were producing.

I've tried the suggestion on the link below but is has not made any difference. http://www.thinkwiki.org/wiki/Script_for_configuring_the_CS4239_sound_chip_in_PnP_mode When I enter install snd-cs46xx /bin/true as root in terminal, I get: Linux:~ # install snd-cs46xx /bin/true install: cannot stat `snd-cs46xx': No such file or directory Linux:~ # Same goes for: Linux:~ # install snd-cs4236 /usr/local/bin/soundcard-on install: cannot stat `snd-cs4236': No such file or directory Linux:~ # Anyone else have this problem???

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

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]

BTW, I tried using the command iwconfig wlan0 txpower 20 (and several other values) and tried including dBm at the end, but it's still 0.

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]

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?

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?

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.

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]

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".

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.

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

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

But it's still not working! No power on the card at all! It works fine when I boot windoze, but nothing I've tried works with Linux.

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...