LinuxQuestions.org Member Success Stories Just spent four hours configuring your favorite program? Just figured out a Linux problem that has been stumping you for months?
Post your Linux Success Stories here. |
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
05-11-2004, 03:46 PM
|
#1
|
Senior Member
Registered: Aug 2003
Location: Birkenhead/Britain
Distribution: Linux From Scratch
Posts: 2,073
Rep:
|
linux-2.6.6 hdc: lost interrupt
I've just been patching our computers to the 2.6.6 kernel. One of them was no problem but the other...when I rebooted into the new kernel it would always hang probing the cdrom with the message
ide-cd: cmd 0x5a timed out
hdc: lost interrupt
I recompiled the kernel dozens of times with many different combinations of options and none of them made any difference. The solution came to me when I rebooted into the 2.6.5 kernel and typed dmesg into the terminal and there on the screen was a message I'd seen so many times that I'd stopped seeing it...
PCI: Using ACPI for IRQ routing
PCI: if you experience problems, try using option 'pci=noacpi' or even 'acpi=off'
So I tried booting with the option pci=noacpi in /boot/grub/menu.lst and it worked first time. I've recompiled with my current best config for this machine and it's all working again. The only thing I'm left wondering about is what changed between the 2.6.5 and 2.6.6 kernels that doesn't agree with the DVD/CDRW in this machine? It's working though, so I won't be losing sleep over it.
|
|
|
05-13-2004, 03:20 AM
|
#2
|
LQ Newbie
Registered: May 2004
Location: Ireland
Distribution: Slackware 9.1
Posts: 2
Rep:
|
RE:
I experienced the same problem yesterday after compiling 2.6.6. It wasn't just by cd drive but two of my hard drives that were flagging this error message. I recompiled several times even doing a line by line comparison to my 2.6.5 and 2.6.1 configurations. I think there is a new ide option (generic ide ??) can't remember off the top of my head. I also did some searching on Google this morning and the problem has been seen by a few other people. I'll give your workaround a try later and see how it goes.
Last edited by wayne040576; 05-13-2004 at 03:23 AM.
|
|
|
05-13-2004, 07:26 PM
|
#3
|
LQ Newbie
Registered: May 2004
Location: Kemper, Lannuon [BZH]
Distribution: Gentoo GNU/Linux
Posts: 1
Rep:
|
I've the same problem
Have anobody have resolv this ?
|
|
|
05-13-2004, 08:22 PM
|
#4
|
Member
Registered: Jul 2003
Location: Dallas, TX
Distribution: Ubuntu 10.04 LTS
Posts: 987
Rep:
|
did you try the pci=noacpi boot parameter?
after booting with that param, check dmesg for new messages and try some of the recommended options from there; if nothing works, use an older kernel
|
|
|
05-14-2004, 02:20 AM
|
#5
|
LQ Newbie
Registered: May 2004
Location: Ireland
Distribution: Slackware 9.1
Posts: 2
Rep:
|
Quote:
Originally posted by TheOneAndOnlySM
did you try the pci=noacpi boot parameter?
|
I gave it a go yesterday and it worked fine. After some more googling, I found that this seems to be the common workaround for the problem.
|
|
|
05-31-2004, 01:30 PM
|
#6
|
Member
Registered: May 2004
Location: Lyon, France
Posts: 53
Rep:
|
Hi, newbie here, had the same probs myself on my new computer, simple solution I found... Updating my BIOS! I al using an Asrock K7S8X motherboard and I think that the old BIOS (2.20) was conflicting with something, with the new BIOS installed (2.30) all worked fine.
Hope this is of use to someone
|
|
|
06-08-2004, 01:09 PM
|
#7
|
LQ Newbie
Registered: May 2004
Location: Finland
Distribution: Mandrake
Posts: 19
Rep:
|
Hello!
I have Asrock K7S8X motherboard, too, and the only way to install or start Mandrake 9.2 or 10 was option "linux noapic". But after updating bios to 2.30, there is no need for extra options in LILO. Thanks for you, mikejac69.
|
|
|
11-15-2004, 10:29 AM
|
#8
|
LQ Newbie
Registered: Nov 2004
Posts: 22
Rep:
|
In the kernel options, I think there was an option on PCI access modes... and one of them was ACPI... so if you recompile the kernel with something that isn't ACPI, it might work.
Sorry if this seems disjointed, trying to remember something from a kernel coniguration program I don't have infront of me...
|
|
|
All times are GMT -5. The time now is 04:56 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|