Hi, mucking with the source cde and with configuration samples I've solved the compile problem I wrote about yesterday night (udelay)
Now I can get a romimage file. I plan to burn this file inside the normal flash of my pcchips 810 board to boot from IDE (hard disk).
However, the file romimage is too big! I would have expected a 256KB file, but I obtain a 1.4MB one:
$ ll -h payload.block linuxbios.rom romimage -rw-rw-r-- 1 alesan alesan 64k Mar 14 13:31 linuxbios.rom -rw-rw-r-- 1 alesan alesan 1.3M Mar 14 13:31 payload.block -rw-rw-r-- 1 alesan alesan 1.4M Mar 14 13:31 romimage
What am I doing wrong? This is the config file:
target rom mainboard pcchips/m810lmr cpu k7 option CONFIG_UDELAY_TSC=1 option VIDEO_CONSOLE=1 option SERIAL_CONSOLE=1 option DEFAULT_CONSOLE_LOGLEVEL=6 option SERIAL_POST=1 option ENABLE_MII=1 option MUST_ENABLE_FLOPPY=1 option HAVE_FRAMEBUFFER=1 option SMA_SIZE=0x80 option BOOT_IDE=1 option IDE_BOOT_DRIVE=0 option ONE_TRACK=32 biosbase 0xffff0000 linux /usr/src/linux commandline root=/dev/hda1 console=ttyS0,115200 console=tty0
bye bye thank you as
On Fri, 14 Mar 2003, Alessio Sangalli wrote:
linux /usr/src/linux commandline root=/dev/hda1 console=ttyS0,115200 console=tty0
how could you expect a 256KB romimage with a kernel in there? It's just not possible. I wish it were.
ron
Ronald G. Minnich wrote:
On Fri, 14 Mar 2003, Alessio Sangalli wrote:
linux /usr/src/linux commandline root=/dev/hda1 console=ttyS0,115200 console=tty0
how could you expect a 256KB romimage with a kernel in there? It's just not possible. I wish it were.
:) yes I know. However I couldn't find any config file or example to let the kernel image being loaded from the hard disk or IDE in general. On cwlinux it's possible to find images that load a kernel named "kernel" on the root file system. How can I reproduce this in my config file?
I will try to "grep -r" it out of the sources, but if anybody could help... I promise I will write a beautiful howto :)
bye bye!!! as
Greetings,
These days, LinuxBIOS expects to find a bootloader in ELF format at the beginning of the ROM. Etherboot has an extension to load an image from a raw IDE partition. I'm working on one that can handle an ext2 filesystem, but it's VERY alpha at the moment.
On Fri, 14 Mar 2003, Alessio Sangalli wrote:
Ronald G. Minnich wrote:
On Fri, 14 Mar 2003, Alessio Sangalli wrote:
linux /usr/src/linux commandline root=/dev/hda1 console=ttyS0,115200 console=tty0
how could you expect a 256KB romimage with a kernel in there? It's just not possible. I wish it were.
:) yes I know. However I couldn't find any config file or example to let the kernel image being loaded from the hard disk or IDE in general. On cwlinux it's possible to find images that load a kernel named "kernel" on the root file system. How can I reproduce this in my config file?
I will try to "grep -r" it out of the sources, but if anybody could help... I promise I will write a beautiful howto :)
bye bye!!! as
These days, LinuxBIOS expects to find a bootloader in ELF format at the beginning of the ROM. Etherboot has an extension to load an image from a raw IDE partition. I'm working on one that can handle an ext2 filesystem, but it's VERY alpha at the moment.
Actually Adam has that patch already. His patch supports ext2, ext3 and vfat at the moment. Shouldn't be too hard to support other filesystems also since most of the code can be extracted from grub.
-Andrew
steven james wrote:
Greetings,
These days, LinuxBIOS expects to find a bootloader in ELF format at the beginning of the ROM. Etherboot has an extension to load an image from a raw IDE partition. I'm working on one that can handle an ext2 filesystem, but it's VERY alpha at the moment.
Ok. I know how to make an ELF image of the kernel (mkElfImage). Should I assume cwlinux's rom has etherboot inside? I was able to boot from a ext2(3) partition with it; but now I would like to build my own image etc etc. Which options should I include in the config file? Is there any example for this?
Bye bye, thank you as
Right. But check out the latest development release of etherboot, that is etherboot-5.1.7 . It has pretty much the same code rolled into it and they have really done some other good work on that release as well (like cleaning up the directory structure). I suspect Eric brought those polled ide changes in.
If anyone has trouble with that, they can still use the patch against 5.0.6 which is at http://www.missl.cs.umd.edu/~agnew/etherboot-5.0.6.polled1.diff
On Sat, 15 Mar 2003, Andrew Ip wrote:
These days, LinuxBIOS expects to find a bootloader in ELF format at the beginning of the ROM. Etherboot has an extension to load an image from a raw IDE partition. I'm working on one that can handle an ext2 filesystem, but it's VERY alpha at the moment.
Actually Adam has that patch already. His patch supports ext2, ext3 and vfat at the moment. Shouldn't be too hard to support other filesystems also since most of the code can be extracted from grub.
-Andrew
-- Andrew Ip Email: aip@cwlinux.com Tel: (852) 2542 2046 Fax: (852) 2542 2036 Mobile: (852) 9201 9866
Cwlinux Limited Unit 202B 2/F Lai Cheong Factory Building, 479-479A Castle Peak Road, Lai Chi Kok, Kowloon, Hong Kong.
Tel: (852)2542 2046 Fax: (852)2542 2036
For public pgp key, please obtain it from http://www.keyserver.net/en. _______________________________________________ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Steven James wrote:
These days, LinuxBIOS expects to find a bootloader in ELF format at the beginning of the ROM. Etherboot has an extension to load an image from a raw IDE partition. I'm working on one that can handle an ext2 filesystem, but it's VERY alpha at the moment.
Oh, wait, i see what you mean. On closer inspection of etherboot-5.1.7 they didn't include the file system code? I wonder why.. but alright.
Adam Agnew agnew@cs.umd.edu writes:
Steven James wrote:
These days, LinuxBIOS expects to find a bootloader in ELF format at the beginning of the ROM. Etherboot has an extension to load an image from a raw IDE partition. I'm working on one that can handle an ext2 filesystem, but it's VERY alpha at the moment.
Oh, wait, i see what you mean. On closer inspection of etherboot-5.1.7 they didn't include the file system code? I wonder why.. but alright.
Because I rolled the code in. And I have always seen the fs code as overkill for the problem.
However the code should be layered well enough that you should be able to incorporate the fs code if you like.
Eric
steven james pyro@linuxlabs.com writes:
Greetings,
These days, LinuxBIOS expects to find a bootloader in ELF format at the beginning of the ROM. Etherboot has an extension to load an image from a raw IDE partition. I'm working on one that can handle an ext2 filesystem, but it's VERY alpha at the moment.
And I am working on a tool that can do a lilo like thing, and generate an ELF header for a kernel stored anywhere on the disk. And put that header at the start of the disk.
It works but it needs some variables.
Eric