Per Jessen schrieb:
Florian Gleixner wrote:
Today i swapped my mainboard. The hardest thing was to get access to the harddisks at boot time. I used rescue system to rebuild the initrd several times, adding more and more modules, but the disk was not visible in /dev. The solution was to run mkinitrd -A and after that i can see the disks. This is not a solution!
Any help? Thanks!
We need some more info - your hardware (lspci -v) config, your mkinitrd config to start with. It would also be good to know what didn't work and which error messages you got.
/Per
Thanks for your answer and for your help offer. I'll send you a lspci later when i have access to the machine. You alternatively could tell me how to find out what modules to load. I started a rescue system from PXE boot and checked what modules this rescue system did load. But the kernel modules don't have man pages so i can only guess what the module does. Solaris provides man pages for kernel modules. Wouldn't that be a great benefit (would have to send this to lkml)? So i added some ...scsi... ...ata... and via82cxxx in /etc/sysconfig/kernel and rebuild the initrd. After reboot i could see that the driver loads and it can see the disks, but the /dev tree was missing the discs. I could see them somewhere in /proc, but i'm unsure why the initrd cannot create the dev? With initrd -A i see the disks as /dev/hdX - in rescue as /dev/sdX. What happens here? Wouldn't it be nice to offer another kernel to be installed on /boot and added to grub that has the same modules and logic as the rescue or install kernel: Has all modules, probes all hardware and - the great benefit - you don't have to do the mounts and chroot to rebuild the initrd. Yast misses a "hardware detection and add drivers to initrd" function. With this function and a rescue kernel this mailing list could have 30% less postings i guess. Flo