SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Im not a n00b really. But sometimes I feel like one when trying to get wireless working under Linux. MY BCM4301 internal PCI card is listed, but is getting no power. I bought an Orinoco Classic Gold PCMCIA card, because its supposed to work.
Rubbish! Im getting no power to my PCMCIA card, and on boot, the kernel (at init 3 when loading PCMCIA, no such error on /etc/init.d/pcmcia restart) complains that it cant find a module (sorry, its a bit hard to copy-paste at init 3). So, i've scoured YaST, and attempted to add this card (it lists an unknown device in Network Devices, but i've had no luck).
So, I beg you, whoever may help, could you please help me out getting this working?
Computer Specification
---------------------------
Laptop Manu.:Compaq Presario R3000
Processor: AMD64
RAM: 512MB
PCI: Ethernet (Broadcom 8139)
WiFi (BCM 4301, Broadcom)
PCMCIA: 1 Slot, with an Orinoco Classic Gold PC Card
Various Output (dmesg, lspci, lsmod et al)
-------------------------------------------------
Quote:
===========================
PCMCIA restart (dmesg output)
(/etc/init.d/pcmcia restart)
===========================
Linux Kernel Card Services
options: [pci] [cardbus] [pm]
ACPI: PCI interrupt 0000:02:04.0[A] -> GSI 11 (level, low) -> IRQ 11
Yenta: CardBus bridge found at 0000:02:04.0 [103c:006d]
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:02:04.0, mfunc 0x01111d22, devctl 0x64
Yenta: ISA IRQ mask 0x00f8, PCI irq 11
Socket status: 30000084
ACPI: PCI interrupt 0000:02:04.1[B] -> GSI 10 (level, low) -> IRQ 10
Yenta: CardBus bridge found at 0000:02:04.1 [103c:006d]
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:02:04.1, mfunc 0x01111d22, devctl 0x64
Yenta: ISA IRQ mask 0x00f8, PCI irq 10
Socket status: 30000006
==============
cardctl status
==============
Socket 0:
no card
Socket 1:
no card
eth0: No wireless extensions!
lo: No wireless extensions!
sit0: No wireless extensions!
I've found that the problem is that SuSE 9.2 is incorrectly identifying my card (Orinoco Classic Gold PCMCIA) as an "Anonymous Memory" card. So, i changed the modules it should load (from memory_cs [it doesnt exist], to orinoco, orinoco_cs, hermes, yenta_socket). I've also set my eth0 to 'Manual' in /etc/network/ifcofg-eth0... but it still seems to attempt to map to eth0 and not to the wireless card.
I also cannot get power to the PC card because of this...Any ideas?
Also, here's some updated dmesg output after messing with the modules (setting the "Anonymous Memory" sections bind line to load "orinoco" [or any of the aforementioned modules])
Quote:
=======
dmesg after /etc/init.d/pcmcia restart and editing /etc/pcmcia/config
=======
unloading Kernel Card Services
Linux Kernel Card Services
options: [pci] [cardbus] [pm]
ACPI: PCI interrupt 0000:02:04.0[A] -> GSI 11 (level, low) -> IRQ 11
Yenta: CardBus bridge found at 0000:02:04.0 [103c:006d]
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:02:04.0, mfunc 0x01111d22, devctl 0x64
Yenta: ISA IRQ mask 0x00f8, PCI irq 11
Socket status: 30000010
ACPI: PCI interrupt 0000:02:04.1[B] -> GSI 10 (level, low) -> IRQ 10
Yenta: CardBus bridge found at 0000:02:04.1 [103c:006d]
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:02:04.1, mfunc 0x01111d22, devctl 0x64
Yenta: ISA IRQ mask 0x00f8, PCI irq 10
Socket status: 30000006
cs: memory probe 0x0c0000-0x0fffff: excluding 0xc0000-0xfffff
cs: memory probe 0x60000000-0x60ffffff: excluding 0x60000000-0x60ffffff
cs: memory probe 0xa0000000-0xa0ffffff: excluding 0xa0000000-0xa0ffffff
cs: unable to map card memory!
cs: unable to map card memory!
[
I hope, that someone can help me with this, i've been trying so hard recently to get this working (as you can see), but I really cant jump this hurdle.
Any help or suggestions would be greatly appreciated.
Hi,
I had a similar problem with my network card (no power) the problem for me was that the card was being allocated the wrong area of RAM. Try this site: http://lists.infradead.org/mailman/l...o/linux-pcmcia and send a email with your dmegs, /proc/ioports & /proc/iomem outputs and maybe they will be able to help.
Thanks a lot for the reply. I've reinstalled SuSE, but in 23-bit mode (cant be arsed with 64-bit if I cant get on the net.) If i manage to get it installed, i'll probably reinstall with 64bit.
I got ndiswrapper installed and installed the .inf/.sys files (win drivers), I can modprobe it, but still no power
There is still no power with the 32 bit version? If so then have a look in your dmesg and see if there are many messages like this:
Yenta TI: socket 0000:00:09.0 probing PCI interrupt failed, trying to fix
Yenta TI: socket 0000:00:09.0 no PCI interrupts. Fish. Please report.
or:
'*** DANGER *** unable to remove socket power
cs: pcmcia_socket0: unsupported voltage key.'
If so, then follow the instructions from the first post as your card is not getting any interrupts due to a memory problem (and no power too). This is what happened to me
Originally posted by weanerbassgod There is still no power with the 32 bit version? If so then have a look in your dmesg and see if there are many messages like this:
Yenta TI: socket 0000:00:09.0 probing PCI interrupt failed, trying to fix
Yenta TI: socket 0000:00:09.0 no PCI interrupts. Fish. Please report.
or:
'*** DANGER *** unable to remove socket power
cs: pcmcia_socket0: unsupported voltage key.'
If so, then follow the instructions from the first post as your card is not getting any interrupts due to a memory problem (and no power too). This is what happened to me
Thanks. Any idea how you fixed it? Its still allocating the PC card as a Memory device, and i've changed the 'bind "memory_cs"' to 'bind "ndiswrapper"' (along with other modules.
Just seems a little long winded, and i've never used a mailing list before
It's really easy to fix, you just have to add a line to the kernel command line that allocates an area of ram for the card. However, because I have 1 gig of ram the solution I was given wouldn't be same for you, thats why I would ask the people at the pcmcia website for help, they know what they are doing where as.... I don't
Sorry it's not a real solution to your problem but it's the best I can do.
FYI I posted on the mailing list. And they fixed it. Those guys are really helpful and quick too!
You were right, I need to change the memory allocation lines in /etc/pcmcia/config.opts to that of my card details (found through lspci -vvv), once that was found, I edited /etc/pcmcia/config.opts and did /etc/init.d/pcmcia restart and I heard the lovely little beep that gave me an erection.
So, alls working. Thanks a lot for your help guys!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.