How to move PCMCIA to initialize sooner in BOOT sequence
Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
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.
How to move PCMCIA to initialize sooner in BOOT sequence
Using Debian Etch... the PCMCIA card is the LAST thing that gets loaded before the login prompt. I would like to have it initialized sooner in boot process. I'm trying to have USB mount a directory during boot. When it's plugged into USB 1.1 (original on motherboard) IT WORKS fine. When I plug it into pcmcia USB 2.0 (upgrade), the directory is NOT mounted.
- My research came up with "modify init.d/PCMCIA script" - but my script doesn't have the "chkconfig: 2345 9 96" line those help files call for.
or...
- "Change the "S20pcmcia" or "S40pcmcia" to a lower number - but none of my "rcX.d" have the "S20pcmcia" or "S40pcmcia" line.
Maybe I just need more simplified instructions. I'd really appreciate the help. Thank you.
I don't know about Debian Etch, but I checked this out on Ubuntu Feisty. You can manually specify what modules you want to run in the file '/etc/modules'. I think specifying them here will enable them sooner. If not, then just list them with the pcmcia modules first, then the usb modules second. Look, using the command lsmod, for what pcmcia modules you'll need (for example yenta, etc.) and add them to the file (the contents of the file should be a vertical list, not space-separated horizontally).
Further, the contents of the directory '/etc/rc5.d' are all symbolic links to the scripts in '/etc/init.d'. So if there's a script you want to run at boot time, just create a link from the rc5.d directory to the script you want in the init.d directory, giving the link the name 'S##****' (## = number, **** = name).
I've re-named pcmcia link to load earlier (from S40 to S20) but that didn't solve it.
What happens is that when I plug the USB into to old USB 1.1 port (orig on motherboard) it works fine. Prompt for LUKS password shows up and continues booting flawlessly. When I plug it into the PCMCIA USB 2.0 card, the card is recognized but the USB dir is not mounted and there is no prompt for password. I get told to "press ctrl+D to continue" or "enter root password for maintenance". And I have no clue where to look next.
I've run into a bunch of articles with similar problems... but no solutions. Anyone? Thank you.
You might see if your usb drive is mounted as a different device name depending on whether you use the pcmcia slots or the regular 1.1 slots. I don't have any hardware to see if this will work, myself, but you might try booting each time with the usb first in a computer slot, then in a pcmcia slot. Run 'lsusb', or some such device scanner after each boot, and see if it uses a different /dev entry each time. Then check your /etc/fstab file, and change the /dev entry for the usb partition to the one you want to use.
See, the system may only be looking for the usb device on a particular usb hub. If you install the usb on a pcmcia usb 2.0, you're using a different usb hub, and it won't be mounted properly.
You didn't mention if you tried adding your pcmcia modules to the /etc/modules file. It might load those modules first, before any others.
When plugged into usb 1.1 "lsusb" shows it in:
"bus 001 device 002: ID 0814:0204"
When plugged into usb 2.0 (pcmcia) it shows it in:
"bus 005 device 002: ID 0814:0204"
/etc/fstab has entries:
/dev/mapper/myhomeonusb-lv--home /home ext3 defaults
...
/dev/sda5 /media/usb0 auto rw,user,noauto
When it boot fine with usb plugged into the usb 1.1 port. On boot, I get entries...
. enter LUKS password for /dev/hda5 (encrypted harddrive): xxxxxxxx
...
. enter LUKS password for /dev/sda5 (encrypted /home dir on usb): xxxxxxxx
...
and it mounts everything just fine into GUI. In /dev/mapper I get entries for hda5_crypt and sda5_crypt and myhomeonusb-lv--home.
When plugged into usb 2.0 (pcmcia)... during boot, I get...
. enter LUKS password for /dev/hda5 (encrypted harddrive): xxxxxxxx
. ...
. (press ctrl+d for maintenance)... then loads without asking for sda5 password and kick me out to command prompt login.
...
In /dev/mapper there is an entry for hda5_crypt but sda5_crypt is MISSING. Sorry, I'm still learning and don't know if this info will help you.. help me. Thanks for trying, anyway.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.