Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Make sure you have PnP Disabled/No in the BIOS. If that's not possible, then boot with pci=biosirq; this has the same effect as turning off PnP in the BIOS and forcing the BIOS to perform hardware detection for the OS.
If you still have trouble booting, it could be the power management routines getting in the way. If that's the case turn off ACPI with acpi=off.
Another thing that can cause hangups in booting is APIC (Advanced Programmable Interrupt Controller - not to be confused with ACPI). If that can't be turned off in the BIOS, pass 'noapic' as a kernel boot parameter. With my desktop, it used to hang after 'checking module dependencies'; noapic fixed that.
Other BIOS settings: make sure you are not using Shadow Video BIOS (set to No) and turn off Boot Virus Protection if applicable. HTH.
Using 'pci=biosirq' seems to be working (knock on wood). My question is this. Do I need to pass that every time I boot or can I pass it once and it will turn off pnp inderinitely?
No, it needs to be done for every boot. You do this by editing /etc/lilo.conf and adding 'pci=biosirq' to the 'append=' line under the 'label = "linux"' entry. (you need to be root to do this) For example, if the line in /etc/lilo.conf is:
Well successful booting has once again come to an end.
Using pic=biosirq worked fine for about a day. Now that option no longer works. I then used acpi=off which worked once. I used noapic after that, which also worked once.
I'm so confused by this. I just don't understand why it's so sparatic.
Describe the steps you have taken to alter your computer's setup. Post the output of /etc/lilo.conf. I need this info to get to the bottom of why this is happening to you.
I don't use lilo as my boot manager, I'm using grub. I haven't changed any of the config files as of yet. I've been testing the parameters at boot time by appending them to the kernel line.
When the system boots up I press 'e' to edit the kernel line, I then append the parameters you listed to the end of it. (only one at a time) Like so:
Using pic=biosirq worked fine for about a day. Now that option no longer works. I then used acpi=off which worked once. I used noapic after that, which also worked once.
Try using all the kernel boot parameters that I suggested all at once. So you would make you kernel bootup line:
Also, remember that editing your grub startup at boot is a once-only deal. To permanently enter your boot options and have them take effect automagically every time you boot you need to open your Grub config file (usually /boot/grub/menu.lst) and add those parameters to the end of your "kernel" line.
Also, remember that editing your grub startup at boot is a once-only deal. To permanently enter your boot options and have them take effect automagically every time you boot you need to open your Grub config file (usually /boot/grub/menu.lst) and add those parameters to the end of your "kernel" line.
Yea, I know. I've been editing it every time I boot. Pain in the ass, but its easier than having to boot and edit the file everytime.
Quote:
Try using all the kernel boot parameters that I suggested all at once. So you would make you kernel bootup line:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.