System: -MSI K8NGM2 with GeForce 6150 graphic on Board -dual core RAM 2x 256 MB -AMD ATHLON 64 Venice 3200+ What I had make: Install with amd64 CD. Booting from IDE-CRDOM. What I get: While initializing the setup the system want mount the CDROM allways as /dev/hda. After a long time a kernel problem is shown and the system hangs. The Problem: HDD => Primary Master => /dev/hda CDROM => Primary Slave OR Secundary Slave => should be /dev/hdb Workarround: Make BOOT-CDROM Primary Master and the other devices Secondary or Slave.
OK. I'm not sure I understand. Your hard drive is PATA (not SATA), correct? In Gentoo, SATA drives show up as /dev/sd* instead as we use the (better) SCSI driver. Also, if you have multiple controllers for PATA, it could be that your HDD is on another controller and is detected as /dev/hde instead. Perhaps some more information would be in order. Can you post the actual output from the kernel panic? Otherwise, there won't be much of anything that we can do.
(In reply to comment #1) > Your hard drive is PATA (not SATA), correct? Yes. > In Gentoo, SATA drives show up as /dev/sd* instead as we use the (better) SCSI > driver. Yes I know, but SATA is deactivated in the BIOS. > Also, if you have multiple controllers for PATA, it could be that your > HDD is on another controller and is detected as /dev/hde instead. I have only the onboard controller (Primary, Secundary) and had pluged the HD at Primary with switch to Master and the CDROM also at primary with switch to slave. Therefore the HD is /dev/hda and CDROM /dev/hdb. At boot time want the gentoo mount the /dev/hda as CDROM, but there is the HD! There is no way to solve this unless substitution CDROM (now master) with HD (now slave). This works great. > Perhaps some > more information would be in order. Can you post the actual output from the > kernel panic? Otherwise, there won't be much of anything that we can do. Unfortunately I have now installed the gentoo. But I think the kernel panic is a follow up of false mount. Btw: How can I make a screenshot after a kernel-panic? Ok, I have to use a digital camera. But is there any other way (log-file at /dev/fd0 which can held some informations)?
Can you see if this is still a problem with the 2006.1 media? We are using a much newer kernel, and I hope that this has resolved the issue for you. Thanks
Well, there was no response and there's been two releases since this was reported. I'm assuming that this is FIXED, but since I got no response, marking this as NEEDINFO.