"siefke_lis...@web.de" <siefke_lis...@web.de> wrote: > On Mon, 8 Feb 2016 22:01:11 +0100 <waben...@gmail.com> wrote: > > > Very sparse information. It would be helpful if you would tell us at > Yes sorry but with this kernel become crazy... > > > VFS: unable to mount root fs on unknown block...) and also what > > kind > > This was last message. Now i run genkernel kernel config and delete > what not need. But now come: > > siefke@sisibox ~/.kernel/source/linux-4.4.0-pf3 $ du -sh > arch/x86_64/boot/bzImage 0 arch/x86_64/boot/bzImage
This is ok because this file is just a symlink. I never used genkernel so I don't know if your home directory is the right place for kernel sources. On my system the kernel sources are located here: /usr/src/linux/ where "linux" is a symlink to the directory that contains the kernel sources. So arch/x86_64/boot/bzImage is on my system located here: $ ls -hl /usr/src/linux/arch/x86_64/boot/bzImage lrwxrwxrwx 1 root root 22 18. Jan 04:46 /usr/src/linux/arch/x86_64/boot/bzImage -> ../../x86/boot/bzImage When I use "du" on this file I get back the same result, because it's a symlink and not a "real" file. $ du -hs /usr/src/linux/arch/x86_64/boot/bzImage 0 /usr/src/linux/arch/x86_64/boot/bzImage But when I use "du" not on the symlink but on the "real" file, I get: $ du -hs /usr/src/linux/arch/x86/boot/bzImage 6,2M /usr/src/linux/arch/x86/boot/bzImage > sisibox siefke # lspci [...] > SATA controller: Intel Corporation 5 Series/3400 Series Chipset 6 > port SATA AHCI Controller (rev 05) 00:1f.6 v [...] For a SATA AHCI Controller these kernel options should be sufficient: CONFIG_ATA CONFIG_ATA_ACPI CONFIG_SATA_AHCI I don't think that you also need this one, but if it doens't work you can give it a try: CONFIG_SATA_AHCI_PLATFORM What filesystem(s) do you use on your laptop? Are you sure they are included in the kernel configuration? For ext4 filesystem you should enable these options: CONFIG_EXT4_FS CONFIG_EXT4_USE_FOR_EXT2 CONFIG_EXT4_FS_POSIX_ACL You should also enable these (regardless what filesystem you use): CONFIG_DNOTIFY CONFIG_INOTIFY_USER CONFIG_FANOTIFY And now for something completely different... ;-) The error message you've seen could also be caused by a misconfigured bootloader. Unfortunately you didn't tell us what bootloader you use. I'm still using the old grub. I don't have any knowledge about grub2, gummiboot or efibootmgr. If you use one of these I can't help you with it's configuration. In this case the gentoo handbook should give you the information that you need (or some other member of this list). You should carefully check your bootloader configuration. If for example the path to your root-partition is wrong then your system cannot boot. -- Regards wabe
