Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Kernel panic when using v86d initramfs
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
wdsci
Tux's lil' helper
Tux's lil' helper


Joined: 02 Oct 2007
Posts: 148
Location: US

PostPosted: Thu Jan 02, 2014 12:57 am    Post subject: Kernel panic when using v86d initramfs Reply with quote

I'm trying to get fbsplash working on my Gentoo desktop, after many years of running successfully with boring old text-mode startup messages. But I had some issues following the instructions, which I will get to later. For now, as a first step, I just want to get uvesafb working to let myself know I'm on the right track.

Here is my problem: I've followed the instructions on the [uvesafb](http://wiki.gentoo.org/wiki/Uvesafb) wiki page. I ensured that all four of these relevant kernel options were set:

Code:
Device Drivers  --->
    <*> Connector - unified userspace <-> kernelspace linker  --->
    Graphics support  --->
        [*] Support for frame buffer devices  --->
            [*]   Enable firmware EDID
            <*>   Userspace VESA VGA graphics support


Then I emerged klibc and v86d.

Then I went back into the kernel configuration and made sure these options were set:

Code:
General setup  --->
    [*] Initial RAM filesystem and RAM disk (initramfs/initrd) support
    (/usr/share/v86d/initramfs) Initramfs source file(s)


Then I build and install the kernel and its modules, and reboot into this new kernel. The framebuffer starts up, and then I get

Quote:
Kernel panic - not syncing: VFS: unable to mount root-fs on unknown-block(0,0)


or something like that. That's as well as I can remember. It is accompanied by a stack trace, of course.

Then I fired up make menuconfig again, and removed the path to the initramfs source file:

Code:
General setup  --->
    [*] Initial RAM filesystem and RAM disk (initramfs/initrd) support
    () Initramfs source file(s)


With this one change, the kernel boots up fine. Of course the framebuffer doesn't work, I still only see the startup messages in regular text mode, but there is no kernel panic.

Any ideas as to what is going on and how I can get uvesafb working?

If it helps, this comes from /var/log/kernel/current:

Code:
Kernel command line: BOOT_IMAGE=/vmlinuz-3.12.5-gentoo.noiramfs root=/dev/sda1 ro video=uvesafb:1400x1050-24,mtrr:3,ywrap


and output of uname -a:

Code:
Linux acetylene09 3.12.5-gentoo #4 SMP Wed Jan 1 17:44:22 EST 2014 x86_64 AMD Phenom(tm) II X4 955 Processor AuthenticAMD GNU/Linux


and I'm not sure what other information will be useful, but I'll be happy to provide whatever I can.
Back to top
View user's profile Send private message
nshibalov
n00b
n00b


Joined: 14 Aug 2015
Posts: 16

PostPosted: Sat Aug 15, 2015 7:55 am    Post subject: Reply with quote

Hi! I have exactly the same problem. UUID is identical in grub and system. If I write root=/dev/sda4 (my root partition) in grub.cfg instead of root=UUID=... system loads without an error.
Please help.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum