PCMCIA don't work
Forum: Laptops
Topic: PCMCIA don't work
started by: snowyrain
Posted by snowyrain on June 27 2006,10:10
Hello,I have a Medion Laptop 266MMX,96MBRam,CD,Floppy...
I Have installed DSL3.01 on hda2. But DSL only works when I set NOPCMCIA, but I need to use the Networkcard.
How can I get my Networkcard work?
Greetings
Snowyrain.
P.S: Excuse me for my bad english, I hoppe you can understand me.
Posted by Someone on June 27 2006,10:55
Try these next commands:sudo modprobe yenta_socket
sudo modprobe (your netcards module, if you don't know it by yourself then tell us what card you have)
I'am not sure if it works but you can allways try.
Posted by snowyrain on June 27 2006,17:11
Hello,the Networkcard is a EP-427 / EP-427-T. I found on < PCMCIA_CS Sourceforge > , that I have to use axnet_cs. Is this correct?
Mod Probe says the pcmcia_core, yenta_socket, ds and axnet_cs is started. But when I try lspci it takes a long time to diplay the results.
Even the cardmgr is very slow. And say no pcmcia driver in /proc/devices.
Lspci says about the Pcmcia-Slot:
0000:00:0a.0 CardBus bridge: Texas Instruments PCI1131 (rev 01) ICR 13 and IRQ 14
"cat /proc/interrupts" shows
| Code Sample |
| 13: 0 XT-PIC Texas Instruments PCI1131 14: 5893 XT-PIC ide0, Texas Instruments PCI1131 (#2) |
I think I need help
THX
Snowyrain
EDIT
PS1: And when I shut the X server down the console says "lost interrupt", "lost interrupt", "lost interrupt" ...
But only when I start yenta_socket. When I start only "pcmcia_core" I don't get tihs message.
PS2: dsl-n-0.1RC1.iso also hängs when starting cardmgr on booting.
PS3: Boot with dsl acpi=off noapm pci=biosirq don't help
Posted by cbagger01 on June 27 2006,18:29
Try DSL version 2.1bIt has a newer version of the pcmcia card manager.
Posted by snowyrain on June 27 2006,19:22
Hello,thanks for the reply, I have tried 2.1b and I have the same Problem.
Thanks
Snowyrain
EDIT: I have tried Deli Linux. In Delilinux the pcmcia slot works, when I use i82365.
But when I tried modprobe i82365 in DSL i get an error.
Posted by jonam on June 28 2006,13:25
To check your problem, I installed a 16bit ethernet card in my Compaq 1530D laptop running DSL 2.1b and had no problems. Cardmgr correctly loaded the smc91c92_cs module to manage it. Based on what my card is doing, I don't think your problem is with the TI PCI1131 controllers. You are installing a 16 bit PCMCIA card and it will be the axnet_cs module that will handle the interrupts. You should check to see if axnet_cs is listed in /proc/interrupts. The PCI1131 interrupts will remain at zero with this card.
If you can't see axnet_cs in the interrupt list, then you might try free up some interrupts by going into the laptop BIOS and disabling the IR port and maybe the parallel port.
You might also try allocating axnet_cs a specific interrupt as per the man page for axnet_cs found at:
< http://www.die.net/doc/linux/man/man4/axnet_cs.4.html >
Lastly, look at the output of dmesg to see if there is any obvious problem with allocating interrupts. You should see eth0 being allocated an IRQ if all is OK.
I had a quick look at DeLi Linux's home page and it is using an older kernel (2.2.26) and I think that in that kernel, the pcmcia_cs package was used to manage PCMCIA cards using the i82365 module. In DSL, the kernel is 2.4.26 or 2.4.31 and the yenta_socket module manages PCMCIA Cardbus while the *_cs modules handle 16bit PCMCIA.
Hope this helps.
Regards,
Jonam
Posted by snowyrain on July 12 2006,22:10
Hallo,thank you for your answer and sorry for my late reply, I have had to write a hard student research project.
Now to the problem:
I have disabled all what the bios allow, but it don't work. I don't think that the problem is the axnet_cs driver. But you are right DSL don't show a IRQ for this Networkcard, even when lsmod shows the module.
When I start only pcmcia_core I don't have any problems (OK the Networkcard don't work
). But when I start pcmcia_core and yenta_socket and I stop the X-Server the console shows "lost interrupt", "lost interrupt", "lost interrupt" ...I think here (yenta_socket) is the problem.
I have installed Windows 98 SE and there both PCMCIA Ports are found on IRQ15. I have tried to run "insmod yenta_socket irg=15", but the module don't know the option irq=15.
Maybe the Problem ist here
< PCMCIA Card Services >.
Now I'm sitting here so many hours, and I don't get a positiv result
greetings
Snowyrain
Posted by Pete on July 14 2006,18:23
Hi,I seem to have a slightly different problem. My DSL
hardrive install runs fine, except that the PCMCIA
card does not work, although DSL says that it
is up and running.
The DSL distro is the most recent one (downloaded
today), the laptop is a Toshiba Sattelite, and the card is
a SMC 8036TX.
All the help will be most welcome, but note that I'm
a newbie in Linux and would appreciate more if
the suggestions are more explicit and simple to follow.
Thanks!!!
P
Posted by roberts on July 14 2006,22:36
Does the boot option pci=assign-busses help?
Posted by Pete on July 15 2006,15:01
| Quote (roberts @ July 14 2006,18:36) |
| Does the boot option pci=assign-busses help? |
Hi,
I tried to put that line "pci=assign-busses" in
/etc/lilo.conf, ran lilo but it doesn't work. Could
you be more specific as to how to try this out?
cheers,
P
Posted by Pete on July 17 2006,18:37
| Quote (Pete @ July 15 2006,11:01) | ||
Hi, I tried to put that line "pci=assign-busses" in /etc/lilo.conf, ran lilo but it doesn't work. Could you be more specific as to how to try this out? cheers, P |
Ok,
I managed to find out how to get LILO to accept the
prompt and tried booting with the optionb pci=assing-busses.
No error is generated, but no internet access either.
I also note that I cant turn the ethernet service down...
"device or resource busy"...
Posted by brianw on July 17 2006,19:37
Try booting with the nopcmcia boot option then when the system is up try sudo modprobe pcmcia_core
sudo modprobe tcic
sudo modprobe ds
cardmgr
if everything goes well shut down X and see if you get the lost interupt. If not start X and try the
sudo modprobe axnet_cs
Also what errors do you get with the i82365 modprobe attempt?
Posted by Pete on July 21 2006,10:01
| Quote (brianw @ July 17 2006,15:37) |
| Try booting with the nopcmcia boot option then when the system is up try sudo modprobe pcmcia_core sudo modprobe tcic sudo modprobe ds cardmgr |
Unfortunately, all the commands below return errors:
sudo modprobe tcic
sudo modprobe ds
sudo modprobe axnet_cs
----------------------------
init_module: no such device
insmod ... failed
Posted by roberts on July 21 2006,19:56
Check that you do not have IRQ conflicts.At a system prompt
dmesg | grep irq
Many times a conflict at irq 11 will show up.
Then either the card won't work or will be very very slow.
If so, then see if you can disable or assign via bios.
Posted by Pete on July 22 2006,15:40
| Quote (roberts @ July 21 2006,15:56) |
| Check that you do not have IRQ conflicts. At a system prompt dmesg | grep irq Many times a conflict at irq 11 will show up. |
Again, thaks for your suggestion, but I don't think there is
such a conflict. The result of "dmesg | grep irq" is:
Piccolo: not 100% native mode: will probe irqs later
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
PCI: No IRQ known for interrupt pin A of device 00:13.0. Please try using pci=biosirq.
PCI: No IRQ known for interrupt pin B of device 00:13.1. Please try using pci=biosirq.
Yenta ISA IRQ mask 0x0eb8, PCI irq 0
Yenta ISA IRQ mask 0x0eb8, PCI irq 0
PCI: No IRQ known for interrupt pin A of device 14:00.0. Please try using pci=biosirq.
PCI: No IRQ known for interrupt pin A of device 14:00.0. Please try using pci=biosirq.
ttyS00 at 0x03f8 (irq = 4) is a 16550A
parport0: irq 7 detected
ttyS14 at 0x1c00 (irq = 3) is a Lucent Modem
Posted by brianw on July 23 2006,18:47
Here is a link that talks about this error. Device 00:13.0 is the pcmcia so that is why it is not working. The first recomendation in the link says to try the pci=biosirq (I think the main post is for a 2.6 kernel but there are mentions of the 2.4 as well).< http://www.gossamer-threads.com/lists/linux/kernel/400179 >