This is a discussion on fedora 6 wont install or rescue, cant find driver within the Linux Operating System forums, part of the Unix Operating Systems category; --> Hello- I got a new motherboard/cpu (Intel DG965WH w/Intel CPU Pentium D 820 2.8Ghz dual core. I took a ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hello- I got a new motherboard/cpu (Intel DG965WH w/Intel CPU Pentium D 820 2.8Ghz dual core. I took a working fed 6 HD and stuck it in and it wont boot, it complains during bootup saying: .... Red Hat nash version 5.1.19.0.2 starting mount: could not find filesystem '/dev/root' setuproot: moving /dev failed: no such file or directory setuproot: error mounting /proc: no such file or directory setuproot: error mounting /sys: no such file or directory switchroot: mount failed: no such file or directory kernel panic - not syncing: attempted to kill init! then it freezes. I took same working disk and put it in my windows box (switching out the HD temporarily) and it boots and works just fine (its an older motherboard/cpu). next: I thought Id try to use the fedora 6 rescue disk and see if it might somehow correct itself (even though nothing seems to legitimately be wrong with it). Now it boots up the fedora rescue and I go through the menus. Just after the language -> keyboard type -> I get to the menu that says: Rescue Method What type of media contains the rescue image? Local CDROM Hard Disk Floppy Drive FTP HTTP When I select CDROM (duh, I just boot from there), it says: unable to find any devices of the type needed for this install type. Would you like to manually select your driver or use a driver disk? OPTIONS: Select Driver Use Driver Disk At this point Im lost. Is it saying that it no longer has a driver for the CD rom its reading the disk from? If so why not?? How did I get this far? I tried putting in another HD and installing fed 6 from scratch, but it complains about the same issue. With a new motherboard and CPU I didnt think this would be an issue. Anyone know what this is and how I should resolve it? Thanks, Jeff |
| |||
| On 2007-02-24, Jeff <jeep@rahul.net> wrote: > mount: could not find filesystem '/dev/root' That translated means: the mobo has a strange disk controller that your kernel doesn't recognize > At this point Im lost. Is it saying that it no longer has a driver > for the CD rom its reading the disk from? See previous point. Davide -- BOFH prayer: God, give me strength, because I'll need it later when I'm carting 150Kg of dead body to dump in the nearby river... |
| |||
| Jeff wrote: > I got a new motherboard/cpu (Intel DG965WH w/Intel CPU Pentium D 820 > 2.8Ghz dual core. > I took a working fed 6 HD and stuck it in and it wont boot, What kind of hard disk, SATA or PATA? You must use the "all-generic-ide" kernel option to access any PATA drives. If it's a SATA disk make sure the SATA controller is set in AHCI mode in the BIOS. > When I select CDROM (duh, I just boot from there), it says: > > unable to find any devices of the type > needed for this install type. > Would you like to manually select your > driver or use a driver disk? > > OPTIONS: Select Driver Use Driver Disk > > At this point Im lost. Is it saying that it no longer has a driver > for the CD rom its > reading the disk from? If so why not?? How did I get this far? Again, you need to use the "all-generic-ide" option to use PATA drives. The kernel and the initial RAM disk image are read using BIOS code, but you need a Linux driver to proceed past this point. > I tried putting in another HD and installing fed 6 from scratch, but > it > complains about the same issue. With a new motherboard and CPU I > didnt > think this would be an issue. The motherboard is _too_ new. You would need kernel 2.6.20 or later to use the Marvell PATA controller without any extra options. The FC6 installer uses kernel 2.6.18. -- Markku Kolkka markku.kolkka@iki.fi |
| |||
| I have the exact same configuration, and had similar problems. You have to: 1) Set AHCI mode in the BIOS 2) At the installer's first screen (Before starting the installer) linux all-generic-ide pci=nommconf This will boot and install successfully. |
| |||
| On Feb 25, 5:56 pm, Jim Garrison <j...@athensgroup.com> wrote: > I have the exact same configuration, and had similar problems. > You have to: > > 1) Set AHCI mode in the BIOS > > 2) At the installer's first screen (Before starting the installer) > > linux all-generic-ide pci=nommconf > > This will boot and install successfully. Thank you very much Jim for this info, however, I didnt see AHCI mode anywhere in my bios? Can you point me to it? And I assume you mean that the linux all-generic-ide pci=nommconf is an argument to the kernel during boot up? Ive never done that before is why I asked. Thanks again! Jeff |
| |||
| Jeff wrote: > On Feb 25, 5:56 pm, Jim Garrison <j...@athensgroup.com> wrote: >> I have the exact same configuration, and had similar problems. >> You have to: >> >> 1) Set AHCI mode in the BIOS >> >> 2) At the installer's first screen (Before starting the installer) >> >> linux all-generic-ide pci=nommconf >> >> This will boot and install successfully. > > Thank you very much Jim for this info, however, I didnt see > AHCI mode anywhere in my bios? Can you point me to it? AHCI is set in the IDE disk configuration page. The options are IDE or AHCI. > And I assume you mean that the linux all-generic-ide pci=nommconf > is an argument to the kernel during boot up? Ive never done that > before is why I asked. Yes. At the very first screen, where you'd normally press ENTER to boot and launch the installer, enter the linux... command and press ENTER. |
| |||
| On Feb 26, 11:37 am, "Jeff" <j...@rahul.net> wrote: > On Feb 25, 5:56 pm, Jim Garrison <j...@athensgroup.com> wrote: > > > I have the exact same configuration, and had similar problems. > > You have to: > > > 1) Set AHCI mode in the BIOS > > > 2) At the installer's first screen (Before starting the installer) > > > linux all-generic-ide pci=nommconf > > > This will boot and install successfully. > > Thank you very much Jim for this info, however, I didnt see > AHCI mode anywhere in my bios? Can you point me to it? > > And I assume you mean that the linux all-generic-ide pci=nommconf > is an argument to the kernel during boot up? Ive never done that > before is why I asked. > > Thanks again! > Jeff Bah, nevermind, I found both. Thankyou! |
| ||||
| Markku Kolkka wrote: > Jeff wrote: > >>I got a new motherboard/cpu (Intel DG965WH w/Intel CPU Pentium D 820 >>2.8Ghz dual core. >>I took a working fed 6 HD and stuck it in and it wont boot, > > > What kind of hard disk, SATA or PATA? You must use the "all-generic-ide" > kernel option to access any PATA drives. If it's a SATA disk make sure > the SATA controller is set in AHCI mode in the BIOS. > > >>When I select CDROM (duh, I just boot from there), it says: >> >>unable to find any devices of the type >>needed for this install type. >>Would you like to manually select your >>driver or use a driver disk? >> >>OPTIONS: Select Driver Use Driver Disk >> >>At this point Im lost. Is it saying that it no longer has a driver >>for the CD rom its >>reading the disk from? If so why not?? How did I get this far? > > > Again, you need to use the "all-generic-ide" option to use PATA drives. > The kernel and the initial RAM disk image are read using BIOS code, but > you need a Linux driver to proceed past this point. > > >>I tried putting in another HD and installing fed 6 from scratch, but >>it >>complains about the same issue. With a new motherboard and CPU I >>didnt >>think this would be an issue. > > > The motherboard is _too_ new. You would need kernel 2.6.20 or later to > use the Marvell PATA controller without any extra options. The FC6 > installer uses kernel 2.6.18. > You could try out Fedora core 7 test 2: http://torrent.fedoraproject.org/ the FC7 Test 2 just got posted today on there, I bet it has 2.6.20 in it. I have FC7 Test 1 on my laptop and it's at 2.6.20 something for the kernel. You could just try the f7-test2-livecd-i386 and use it to confirm that it works on your hardware before having to commit anything to disk. It depends on what you want to use this machine for and if you can accept some occasional odd occurances (something will work, you do an update and it quits working, then a day or two later another yum update will fix it..) Mark |