help with hardware detection at boot
 

I'm a Linux n00blet and have been very impressed with the info I've been able to get off of this and the linmodem website but I've seem to run into a problem I havn't been able find the answer for as yet:

I'm running Mandrake 9.2 and have finally been able to get my Lucent WinModem to work but it seems like it is still not being detected at boot. I compiled the driver for it and used the ./autostart command but after rebooting I am only able to dial out with kppp after running the ./checkout utility in the console.

How would I go about configuring the boot process to ensure that it is detected now that I have the correct driver for it (and also now that I know that the modem works with linux)?

Add whatever it is you do to make it work (run the checkout command? I'm not familiar with this) to /etc/rc.local and it will be executed every boot.

Håkan

thanks...i'm on a different machine right now i'll give that a try in a couple of minutes

I can't seem to be able to edit the /etc/rc.local file. It says I don't have the correct permissions to do so.....what do i have to do to be able to edit this? also, is there a certain symbol i have to use so the system knows that this is a command?
this is what i have to use in the console after rebooting to enable usage of the modem:
[bryan@localhost bryan]$ su
[root@localhost bryan]# cd /home/bryan/LT/ltmodem-8.26a9
[root@localhost ltmodem-8.26a9]# ./checkout

This checkout utility currently
checks for expected components of a Lucent DSP winmodem installation
provides a minor tutorial
if modem driver insertion is successfull
runs a wvdialconf test
unloads excess drivers if module loading fails
Does not as yet have signficant problem solving action
except for referrals to Documentation.
Can readily be adapted to work with other winmodem installations.

The current Working folder is: /home/bryan/LT/ltmodem-8.26a9.

To continue: Enter

To edit /etc/rc.local you will need to be the root user

su

(then type in the root password when asked)

As for rc.local, you just type in the lines as you would on the command line, one per line. Where you could run into a problem is if what you're running asks for input (Like 'press enter to continue'). If there's a man page for the app, or documentation of some kind, see if there's a way to suppress prompts, if you can call it with a flag or something. Otherwise if you put it in rc.local it's likely that your boot will pause at that point and you'll have to provide the required response. I suppose that would still be better than what you're doing now.

thanks fyoder...i'll give it a try and c what happens