Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with 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.
I've searched for yenta threads with little luck, so I decided to post. I guess this is how you learn.....
I recently installed Red Hat 9 just after giving up on Mandrake 9.1 to find out both of them have the same problem (with my notebook).
This has been an ongoing battle for me, which started out with a pcmcia cardbus nic (linksys). I had long since given up and have since bought a linksys wireless card (WPC11, v. 2.0.x) when I set up a home wireless network. The card worked with RedHat 8, but will not work with 9.
After a little more learning, and some trial & error, I have narrowed the problem to the yenta kernel module (yenta_socket). It isn't loading....it fails miserably.
When I try to 'insmod yenta_socket' it gives me an error indicating that no devices are found. dmesg reports no irq found on device 0:0:a (something like that), and says to try 'pci=biosirq'.
The notebook is using a texas instruments cardbus socket, and for whatever reason it isn't starting. None of my pcmcia cards get power. They all work fine in windows (multiboot).
So I've narrowed the problem, but what do I do now? As far as the wireless nic driver is concerned, there are no pcmcia devices attached.
What's in "dmesg" from the yenta_socket load fail?
Also, what's the exact pcmcia bridge type off of:
/sbin/lspci
If its just an IRQ issue, which is really a compaq problem instead of a yenta issue, you might want to look at:
/etc/pcmcia/config.opts
This way you can exclude irq ports from its search order... although that might just be outdated since the switch to yenta.
Also, you can send arguments directly at modprobe in the init file, they're about 30 lines down, but I can't remember offhand the syntax they require, but you can definately still find that info at pcmcia-cs's sourceforge page.
The thing that is really driving me nuts is that my pcmcia worked in an earlier version of linux....I assume it was using yenta....but I'm not sure. Would have been Mandrake 8.1.
Here's the output of several of the commands:
#lspci
00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 03)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP]
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 22)
00:07.1 IDE interface: VIA Technologies, Inc. VT82C586/B/686A/B PIPC Bus Master IDE (rev 10)
00:07.2 USB Controller: VIA Technologies, Inc. USB (rev 10)
00:07.4 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 30)
00:07.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio Controller (rev 20)
00:09.0 Ethernet controller: Conexant HCF 56k Modem (rev 08)
00:09.1 Communication controller: Conexant HCF 56k Modem (rev 05)
00:0a.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus Controller (rev 01)
01:00.0 VGA compatible controller: ATI Technologies Inc Rage Mobility P/M AGP 2x (rev 64)
#insmod yenta_socket
Using /lib/modules/2.4.20-8/kernel/drivers/pcmcia/yenta_socket.o
/lib/modules/2.4.20-8/kernel/drivers/pcmcia/yenta_socket.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
#dmesg
PCI: No IRQ known for interrupt pin A of device 00:0a.0. Please try using pci=biosirq.
See what happens... Oh, btw, you were using yenta with RH 8.0 before. Also probably with Mandy 8.1, oddly enough I never used that release and by 8.2 they had switched to yenta.
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You do not have a /boot partition. This means that
# all kernel and initrd paths are relative to /, eg.
# root (hd0,1)
# kernel /boot/vmlinuz-version ro root=/dev/hda2
# initrd /boot/initrd-version.img
#boot=/dev/hda
default=0
timeout=0
splashimage=(hd0,1)/boot/grub/splash.xpm.gz
title Red Hat Linux (2.4.20-8)
root (hd0,1)
kernel /boot/vmlinuz-2.4.20-8 ro root=LABEL=/ pci=biosirq
initrd /boot/initrd-1.4.20-8.img
I restarted the computer, and it freezes solid when it tries to load pcmcia services....
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.