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.
PIIX4: IDE controller on PCI bus 00 dev f9
PCI: Device 00:1f.1 not available because of resource collisions
PIIX4: (ide_setup_pci_device Could not enable device.
00:1f.1 Class 0101: 8086:248a (rev 02) - from some command
00:1f.1 IDE interface: Intel Corp.: Unknown device 248a (rev 02) - from lspci
unknown : Intel Corporation|82801 UltraATA IDE Controller - from drakelspci, i think this is the same thing, not 100% though.
hello,
it looks like there are two IDE controllers both sharing the same resources, i am guessing this is a laptop and i would think that is strange, perhaps it is for hotswaping...?
Try booting into the BIOS to see if you can find evidence of an IRQ conflict. Laptops are notorious for those, and this might help you confirm if it is the IDE controllers causing the problem.
Is your BIOS up to date?
Okay, I booted into what I think is the bios (newbee), F2, and I get the Phoenix blah blah screen. So, I ran through it and the only thing I can think of that could cause a conflict (I'm a newbee now) is maybe my parallel port config, this is the only thing in bios that I can tell that could cause a conflict and is configurable. Everything else is common and far removed. The funny thing is that everything is running okay.
I havn't used eth0 yet nor an outside monitor, maybe these could be? There is a funky quirk I get sometimes now that I think about it, more than I like, sometimes my sound modules won't load. I switched from oss to alsa, still, no change. Could this be it? I haven't noticed any parallels to the sound and the conflict message though, conflict is always, sound just sometimes. Hmmm, I'm clueless to as if my bios are up to date, A03? I think that was the number, lets say I upgrade my bios, is this a hard process? What intails? Any how, I'm still working on it, thanks for help, bests -cg
If you go to Dell's website support at http://support.dell.com/us/en/register.asp?redirect=yes
then choose your system type and search for BIOS, it'll show you version A04 available, with instructions. If BIOS version is the source of the problem, that might fix. I worked in hardware tech support for a little while; laptop BIOS upgrades were pretty common (and easy). The first time you do an update it's always interesting, but after that it's like filling your car up with gas.
I updated to 2.4.14-8.1, no probs now. Sound is working too, so far with no glitch. With the other kernel, dma wasn't enabled because of the conflict, now dma is working. No error. Must of been a bug in the kernel, who knows. Thanks, i'll be updating the bios too, it's time for the suspend to disk sufferfest.
Ya know, I love ticking these long lists. Bests- cg
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.