Latest LQ Deal: Latest LQ Deals
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


  Search this Thread
Old 10-05-2004, 01:12 PM   #1
Registered: Oct 2004
Location: still outside the Matrix
Distribution: Arch, formerly Gentoo and Slackware
Posts: 438

Rep: Reputation: 31
Conflict between network driver and PCMCIA driver

I use an external hard drive connected via a USB port on a PCMCIA card (I have a Thinkpad T21). Problem:

(1) If the PCMCIA card is plugged in at boot time, my LAN doesn't work, but my external hard drive does work.

(2) If I plug the PCMCIA card in after booting, both my LAN and my external hard drive work.

"lsmod" shows that when the PCMCIA card is plugged in at boot, the e100 module doesn't load.

The modules apparently associated with the PCMCIA card are yenta_socket, eth1394 and och1394 (the PCMCIA card has two USB ports and one firewire port).

Does anyone know how I can resolve this conflict.

I'm running Vector Linux 4.3 and am posting here 'cause my posts in the VL forum didn't get any bites (well, I got one, but the tip didn't do the trick).

Old 10-06-2004, 04:39 AM   #2
Registered: Oct 2003
Location: United Kingdom
Distribution: SuSE 10.0 - 11.4
Posts: 347

Rep: Reputation: 30
Sounds like the default loading order for your system is PCMCIA before ethernet which normally makes sense if you want to get a PCMCIA ethernet card working! Unfortunately I'm not familiar with your distro so I don't know how you change the order - on SuSE in /etc/init.d there are links to the scripts used in each runlevel which are numbered in the order they are loaded. The scripts themselves have dependency info in the headers so in my case I can edit the headers and use the insserv tool to recalculate dependencies and rewrite the order.

If there isn't anything similar on your distro then you could try booting with the PCMCIA card in and then use combinations of rmmod and insmod to remove the PCMCIA and e100 modules and start them again in the correct order. If this works you can then put these manual commands into a script file that gets executed after start up - probably something like rc.local (it's boot.local in SuSE). This is not elegant but if it works it's better than pulling the card out all the time.

Good luck.
Old 10-06-2004, 05:30 AM   #3
Registered: Oct 2004
Location: still outside the Matrix
Distribution: Arch, formerly Gentoo and Slackware
Posts: 438

Original Poster
Rep: Reputation: 31
Thank you, Andrew. I'll give it a try and post my results.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Problem with pcmcia network card driver francio Linux - Hardware 5 10-12-2006 10:09 PM
Network driver and Video card driver sniperbooger Linux - Software 2 11-10-2005 09:39 PM
XFree86 Version/Driver conflict Trust Linux - Hardware 2 09-19-2004 03:48 PM
sound driver conflict scarabs Linux - Newbie 11 03-29-2004 03:50 PM
EtherExpress100 driver conflict on toshiba 1800 renegade69 Linux - Networking 13 02-07-2004 08:32 PM > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 01:36 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration