WARNING: Deprecated config file /etc/modprobe.conf

Hi ,

the thought was good "I even tried to move the /etc/modprobe.conf file into the /etc/modprobe.d/ folder"

you can do that from Recovery Mode.

So follow these steps

1. Boot in to Recovery Mode (if you have not grub menu , just hold "Shift" button during Pc boot)

2. Click on Root

3. Give this command first : mount -o remount,rw /

4. Then move the file with this command : mv /etc/modprobe.conf /etc/modprobe.d/

5. Reboot your system with this command : reboot

Now , be careful with above commands. Everything matters. Spaces , Backslashes , Dots ... etc.

Thanks

Can you give the output of:

cat /etc/modprobe.conf

Thanks

options parport_pc io=0x378 irq=7 dma=3

After the command: mount -o remount,rw /
I was able to move the modprobe.conf to the modprobe.d folder, after that when I rebooted my system it stopped at:

checking battery state...... [OK],

Please some one help me to resolve my issue.

On 09/13/2012 03:56 AM, Tashi Daw wrote:
> After the command: mount -o remount,rw /
> I was able to move the modprobe.conf to the modprobe.d folder, after that when I rebooted my system it stopped at:
>
> checking battery state...... [OK],
>
>
> Please some one help me to resolve my issue.
>

Hi ,

just do the same process again (boot from Recovery Mode + click Root) .
Do not forget to give first the command

mount -o remount,rw /

then rename the file with bellow command

mv /etc/modprobe.d/modprobe.conf /etc/modprobe.d/modprobe.conf.old

then give this command to reboot

reboot

Thanks

BUT

maybe is better to rename the file to this

mv /etc/modprobe.d/modprobe.conf /etc/modprobe.d/parport.conf

Try this command instead of : mv /etc/modprobe.d/modprobe.conf /etc/modprobe.d/modprobe.conf.old

Prefixed with sudo, as the source and destination are only readable by the user, a move command needs write access to both folders.

On 09/13/2012 10:35 AM, actionparsnip wrote:
> Prefixed with sudo, as the source and destination are only readable by
> the user, a move command needs write access to both folders.
>

No need for sudo when you are in Recovery Mode and already clicked ROOT.

First command : mount -o remount,rw / achieves the write access.

Then as Root(user) you don't need sudo to mv(move) the file.