Hello All,
I am running Coreboot v2 on AMD's db800 with FILO as the payload. It gets to a point where it intialzes the kernel but the kernel doesnt boot. Any idea whats going on.. I have captured the messages using the serial console. The last few messages are...
linux-34w5:~ # tail minicom.cap parse_command_line: initrd=/initrd-2.6.16.46-0.12-default parse_command_line: kernel command line (64 bytes): "root=/dev/hda3 vga=0x317 resume=/dev/hda2 splash=silent showopts" load_linux_kernel: offset=0x2000 addr=0x100000 size=0x13158c Loading kernel... ok file_open: dev=<NULL>, path=/initrd-2.6.16.46-0.12-default load_initrd: start=0x1f502000 end=0x1f7aeb32 Loading initrd... ok malloc_diag: alloc: 312 bytes (4 blocks), free: 16064 bytes (1 blocks) start_linux: eip=0x100000 Jumping to entry point...
Is this the last message that one is suppose to see with coreboot ?
Regards, Phani
On Wed, Mar 05, 2008 at 04:06:46PM -0800, Phani Babu Giddi wrote:
Hello All,
I am running Coreboot v2 on AMD's db800 with FILO as the payload. It gets to a point where it intialzes the kernel but the kernel doesnt boot. Any idea whats going on.. I have captured the messages using the serial console. The last few messages are...
linux-34w5:~ # tail minicom.cap parse_command_line: initrd=/initrd-2.6.16.46-0.12-default parse_command_line: kernel command line (64 bytes): "root=/dev/hda3 vga=0x317 resume=/dev/hda2 splash=silent showopts" load_linux_kernel: offset=0x2000 addr=0x100000 size=0x13158c Loading kernel... ok file_open: dev=<NULL>, path=/initrd-2.6.16.46-0.12-default load_initrd: start=0x1f502000 end=0x1f7aeb32 Loading initrd... ok malloc_diag: alloc: 312 bytes (4 blocks), free: 16064 bytes (1 blocks) start_linux: eip=0x100000 Jumping to entry point...
Is this the last message that one is suppose to see with coreboot ?
Your kernel command line seems to be
root=/dev/hda3 vga=0x317 resume=/dev/hda2 splash=silent showopts initrd=/initrd-2.6.16.46-0.12-default
which does not tell the kernel to output messages on the serial console, thus the output stops there.
Try adding 'console=tty0 console=ttyS0,115200' or similar to the kernel commandline, and see if it helps.
Uwe.
Hi Uwe,
Thanks for the tip.
Actually Linux was starting and everthing was working fine. Its just that I cannot see anything on the display. The messages that I get on the serial console are just similar to what I would get when booting from the commerial BIOS and GRUB.
What do you think is missing, I was under the impression that VGA ROM is only required only for the BIOS and the kernel has its own driver.
Let me remove the vga=0x317 and make it normal and see how it goes.
Any other inputs are welcome.
Regards, Phani
On Wed, Mar 5, 2008 at 4:34 PM, Uwe Hermann uwe@hermann-uwe.de wrote:
On Wed, Mar 05, 2008 at 04:06:46PM -0800, Phani Babu Giddi wrote:
Hello All,
I am running Coreboot v2 on AMD's db800 with FILO as the payload. It
gets to
a point where it intialzes the kernel but the kernel doesnt boot. Any
idea
whats going on.. I have captured the messages using the serial console.
The
last few messages are...
linux-34w5:~ # tail minicom.cap parse_command_line: initrd=/initrd-2.6.16.46-0.12-default parse_command_line: kernel command line (64 bytes): "root=/dev/hda3 vga=0x317 resume=/dev/hda2 splash=silent showopts" load_linux_kernel: offset=0x2000 addr=0x100000 size=0x13158c Loading kernel... ok file_open: dev=<NULL>, path=/initrd-2.6.16.46-0.12-default load_initrd: start=0x1f502000 end=0x1f7aeb32 Loading initrd... ok malloc_diag: alloc: 312 bytes (4 blocks), free: 16064 bytes (1 blocks) start_linux: eip=0x100000 Jumping to entry point...
Is this the last message that one is suppose to see with coreboot ?
Your kernel command line seems to be
root=/dev/hda3 vga=0x317 resume=/dev/hda2 splash=silent showopts initrd=/initrd-2.6.16.46-0.12-default
which does not tell the kernel to output messages on the serial console, thus the output stops there.
Try adding 'console=tty0 console=ttyS0,115200' or similar to the kernel commandline, and see if it helps.
Uwe.
http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org
On Wed, Mar 05, 2008 at 05:19:11PM -0800, Phani Babu Giddi wrote:
Let me remove the vga=0x317 and make it normal and see how it goes.
vga= may not be appropriate when using the geodelx framebuffer driver.
Also note that you currently have to patch the geodelx framebuffer into your kernel manually.
Look into /usr/src/linux/Documentation/fb/
//Peter
Let me recheck if the geodelx frame buffer is already patched or not. I think it was patched because X was working for with the commerial BIOS.
-Phani
On Wed, Mar 5, 2008 at 5:42 PM, Peter Stuge peter@stuge.se wrote:
On Wed, Mar 05, 2008 at 05:19:11PM -0800, Phani Babu Giddi wrote:
Let me remove the vga=0x317 and make it normal and see how it goes.
vga= may not be appropriate when using the geodelx framebuffer driver.
Also note that you currently have to patch the geodelx framebuffer into your kernel manually.
Look into /usr/src/linux/Documentation/fb/
//Peter
-- coreboot mailing list coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
On Wed, Mar 05, 2008 at 05:47:27PM -0800, Phani Babu Giddi wrote:
Let me recheck if the geodelx frame buffer is already patched or not. I think it was patched because X was working for with the commerial BIOS.
X could be using the VESA driver. There is also an Xorg driver for the geodelx. Neither depend on kernel framebuffer.
//Peter
On Wed, Mar 5, 2008 at 5:50 PM, Peter Stuge peter@stuge.se wrote:
On Wed, Mar 05, 2008 at 05:47:27PM -0800, Phani Babu Giddi wrote:
Let me recheck if the geodelx frame buffer is already patched or not. I think it was patched because X was working for with the commerial BIOS.
X could be using the VESA driver. There is also an Xorg driver for the geodelx. Neither depend on kernel framebuffer.
can someone remind me:do we need a special VSA to make the Linux geode lx framebuffer driver work?
Phani, do you want my .config that works with linux and brings up the frame buffer? it is for 2.6.24.2
ron
Hi Ron,
Yeah please provide me the .config that will defnitely help me.
Regards, Phani
On Wed, Mar 5, 2008 at 6:03 PM, ron minnich rminnich@gmail.com wrote:
On Wed, Mar 5, 2008 at 5:50 PM, Peter Stuge peter@stuge.se wrote:
On Wed, Mar 05, 2008 at 05:47:27PM -0800, Phani Babu Giddi wrote:
Let me recheck if the geodelx frame buffer is already patched or not. I think it was patched because X was working for with the commerial BIOS.
X could be using the VESA driver. There is also an Xorg driver for the geodelx. Neither depend on kernel framebuffer.
can someone remind me:do we need a special VSA to make the Linux geode lx framebuffer driver work?
Phani, do you want my .config that works with linux and brings up the frame buffer? it is for 2.6.24.2
ron
-- coreboot mailing list coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
ron minnich wrote:
On Wed, Mar 5, 2008 at 5:50 PM, Peter Stuge peter@stuge.se wrote:
On Wed, Mar 05, 2008 at 05:47:27PM -0800, Phani Babu Giddi wrote:
Let me recheck if the geodelx frame buffer is already patched or not. I think it was patched because X was working for with the commerial BIOS.
X could be using the VESA driver. There is also an Xorg driver for the geodelx. Neither depend on kernel framebuffer.
can someone remind me:do we need a special VSA to make the Linux geode lx framebuffer driver work?
Phani, do you want my .config that works with linux and brings up the frame buffer? it is for 2.6.24.2
ron
Ron, You need VSA with LX. Not a special VSA. Just the same old one that buildrom will pull in for Geode platforms. Marc
Hi Ron,
The Geode frame buffer driver is turned on the .config file SLES 10 SP1 kernel that I have and I am not sure why I cannot see anything on the screen.
One more thing in the Config.lb file for db800, the pci device id corresponding to this device has been turned off does that make a difference. I thought this should be set only when VGA ROM is present and CONFIG_CONSOLE_VGA and CONFIG_PCI_ROM_RUN is set ? Regards, Phani On Wed, Mar 5, 2008 at 6:03 PM, ron minnich rminnich@gmail.com wrote:
On Wed, Mar 5, 2008 at 5:50 PM, Peter Stuge peter@stuge.se wrote:
On Wed, Mar 05, 2008 at 05:47:27PM -0800, Phani Babu Giddi wrote:
Let me recheck if the geodelx frame buffer is already patched or not. I think it was patched because X was working for with the commerial BIOS.
X could be using the VESA driver. There is also an Xorg driver for the geodelx. Neither depend on kernel framebuffer.
can someone remind me:do we need a special VSA to make the Linux geode lx framebuffer driver work?
Phani, do you want my .config that works with linux and brings up the frame buffer? it is for 2.6.24.2
ron
-- coreboot mailing list coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
-
Marc Jones -
Peter Stuge -
Phani Babu Giddi -
ron minnich -
Uwe Hermann