I'm wondering if anyone else has seen anything like this:
During the installation of redhat-based systems, certain hardware will work in the end only depending on if I provoked it or not during the install.
For instance, my laptop has an onboard audio card (I'm not sure of the brand right offhand), but it usually works fine using ALSA. During the firstboot setup, if I tell it to test the sound card, it will work and play the test sound. But then it won't work ever again after that. However, if I don't test it, then it will continue to work after firstboot is completed. This is with CentOS 5.
Similarly, on Fedora 8 on my PC at work, sometimes the network would stall to a halt for no reason, and then any attempt to ifdown/ifup would result in a kernel panic. This behavior seemed random, but if it was giving this behavior during the time of the install from the LiveCD, the network was doomed to that fate forever until it's reinstalled. So I'd have to boot the LiveCD, surf the web for 15 or 20 minutes and make sure the network doesn't stall out and stop working after a few minutes, and then install to the hard drive.
It seems like if you provoke certain hardware (or not provoke it) during the installation/setup of a redhat box, that it dictates whether the hardware is going to actually work when you need it to. Anybody seen anything like this?
-------------
Cuvou.com | My personal homepage
Project Fearless | My web blog
During the installation of redhat-based systems, certain hardware will work in the end only depending on if I provoked it or not during the install.
For instance, my laptop has an onboard audio card (I'm not sure of the brand right offhand), but it usually works fine using ALSA. During the firstboot setup, if I tell it to test the sound card, it will work and play the test sound. But then it won't work ever again after that. However, if I don't test it, then it will continue to work after firstboot is completed. This is with CentOS 5.
Similarly, on Fedora 8 on my PC at work, sometimes the network would stall to a halt for no reason, and then any attempt to ifdown/ifup would result in a kernel panic. This behavior seemed random, but if it was giving this behavior during the time of the install from the LiveCD, the network was doomed to that fate forever until it's reinstalled. So I'd have to boot the LiveCD, surf the web for 15 or 20 minutes and make sure the network doesn't stall out and stop working after a few minutes, and then install to the hard drive.
It seems like if you provoke certain hardware (or not provoke it) during the installation/setup of a redhat box, that it dictates whether the hardware is going to actually work when you need it to. Anybody seen anything like this?
-------------
Cuvou.com | My personal homepage
Project Fearless | My web blog