Link to home
Start Free TrialLog in
Avatar of bisonfur37
bisonfur37

asked on

all of your loopback devices are in use, and other recompile questions

I have RedHat9 running on an old laptop(5years old) and I am upgrading the kernel to 2.6.  My major problems are the following:

1. When I 'make install', sometimes I am getting the error message "all of you loopback devices are in use"
I understand what a loopback device is and I am sure that my laptop does not require the SCSI modules to boot up using an initrd image.  I want to know what options need to be disabled or made modular so that an initrd image is not created.
For instance, there is the 'device' section in the kernel config where you will find the SCSI options.  Likewise, there is the "block device" section within this device section where there are the loopback and RAMdisk options.  What are the exact options that need to be turned off so that an initrd image is not required?  I have recompiled over 10 times in the last three days and things are not getting any clearer.

2. Second, the reason for recompiling the kernel is so that I can include support for Bluetooth.  When I restart the machine using the newly compiled kernel, I keep getting warnings about the 'usb_ohci' module as well as keydev, mousedev and iptables even though I am sure those have been compiled.  When I read /var/log/dmesg, I do not see these warning messages so does anyone have a good way to reproduce these so I can begin troubleshooting?

3. I have used lspci to see what pci devices the laptop is using although I think that I would be better off getting a more inclusive list.  I have the specifications for the machine but I was wondering if there were any other commands that at least in conjunction with lspci show all of the devices?
ASKER CERTIFIED SOLUTION
Avatar of Karl Heinz Kremer
Karl Heinz Kremer
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of bisonfur37
bisonfur37

ASKER

There are only a few times when an initrd is needed.  The way I solved the initial problem what to NOT run 'make install' and make sure to:
1. cp arch/i386/boot/bzImage /boot/<your kernel name>
2. cp System.map /boot/System.map<your kernel name or whatever your little heart desires>
3. make sure to edit either /etc/lilo.conf or /boot/grub/grub.conf