I see a lot of people here have gotten LinuxBIOS working with the Via EPIA using an IDE device, but has anyone managed to get it working using etherboot to boot a kernel over a network? I'm a hopeless newbie and have been struggling with this for some time. I have links to logs, my payload, and my config below (Trying to keep the list archives tidy).
I had gotten etherboot working with the PCM-5823s earlier and compared the minicom log with that of my Epia. The only real obvious discrepency I see is the entry point. The Geode entered at 0x00094000 (606,208), while the Epia is trying to enter at 0x00020000 (131,072).
I'm using CVS versions of Etherboot and LinuxBios. However, I haven't been able to update in the past one or two weeks due to Sourceforge's problems so I might have missed an important patch.
Links EPIA minicom log (High verbosity): http://www.flagen.com/~sc/linux/funstuff/epia-dave My Rhine payload: http://www.flagen.com/~sc/linux/funstuff/via-rhine-ebcvs.elf My config file: http://www.flagen.com/~sc/linux/funstuff/epia.config Geode (Elfboot part only): http://www.flagen.com/~sc/linux/funstuff/geode-elfboot-dave
TIA --David
Hi David, If you mean has anyone managed to boot a Via EPIA using etherboot as the payload, and loading the kernel via (no pun) tftp, then yes.... but then I wrote it all down in the EPIA howto :-)
Regards Mark.
On Thursday 10 Jul 2003 23:22, David Hendricks wrote:
I see a lot of people here have gotten LinuxBIOS working with the Via EPIA using an IDE device, but has anyone managed to get it working using etherboot to boot a kernel over a network? I'm a hopeless newbie and have been struggling with this for some time. I have links to logs, my payload, and my config below (Trying to keep the list archives tidy).
I had gotten etherboot working with the PCM-5823s earlier and compared the minicom log with that of my Epia. The only real obvious discrepency I see is the entry point. The Geode entered at 0x00094000 (606,208), while the Epia is trying to enter at 0x00020000 (131,072).
I'm using CVS versions of Etherboot and LinuxBios. However, I haven't been able to update in the past one or two weeks due to Sourceforge's problems so I might have missed an important patch.
Links EPIA minicom log (High verbosity): http://www.flagen.com/~sc/linux/funstuff/epia-dave My Rhine payload: http://www.flagen.com/~sc/linux/funstuff/via-rhine-ebcvs.elf My config file: http://www.flagen.com/~sc/linux/funstuff/epia.config Geode (Elfboot part only): http://www.flagen.com/~sc/linux/funstuff/geode-elfboot-dave
TIA --David _______________________________________________ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
On Thursday 10 Jul 2003 23:20, Mark Wilkinson wrote:
Hi David, If you mean has anyone managed to boot a Via EPIA using etherboot as the payload, and loading the kernel via (no pun) tftp, then yes.... but then I wrote it all down in the EPIA howto :-)
oops, hit the wrong key there...
what seems to be the problem that you're having ? your epia.config, the zkernel_start address looks odd. My configs have this option commented out or set to 0xfffc000
what version of etherboot are you using ?
Regards Mark.
Regards Mark.
On Thursday 10 Jul 2003 23:22, David Hendricks wrote:
I see a lot of people here have gotten LinuxBIOS working with the Via EPIA using an IDE device, but has anyone managed to get it working using etherboot to boot a kernel over a network? I'm a hopeless newbie and have been struggling with this for some time. I have links to logs, my payload, and my config below (Trying to keep the list archives tidy).
I had gotten etherboot working with the PCM-5823s earlier and compared the minicom log with that of my Epia. The only real obvious discrepency I see is the entry point. The Geode entered at 0x00094000 (606,208), while the Epia is trying to enter at 0x00020000 (131,072).
I'm using CVS versions of Etherboot and LinuxBios. However, I haven't been able to update in the past one or two weeks due to Sourceforge's problems so I might have missed an important patch.
Links EPIA minicom log (High verbosity): http://www.flagen.com/~sc/linux/funstuff/epia-dave My Rhine payload: http://www.flagen.com/~sc/linux/funstuff/via-rhine-ebcvs.elf My config file: http://www.flagen.com/~sc/linux/funstuff/epia.config Geode (Elfboot part only): http://www.flagen.com/~sc/linux/funstuff/geode-elfboot-dave
TIA --David _______________________________________________ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
EPIA howto? I must've overlooked it in my extensive Googling.
I tried fff80000 because when I run flash_rom, it finds my SST28SF040A at that address. I did notice, however, that you and Sone used fffc0000 for the zkernel_start address. fff80000 does not seem to work at all, so I guess the Epia specifically looks for that address.
My fault for not keeping the epia.config file exactly the same as it was used in the minicom log. That's what I get for being a packrat and keeping so many of them sitting around. The config I'm currently using is exactly the same, but using fffc0000.
As for my etherboot version, it was originally downloaded using CVS on June 25. I'm using version etherboot-5.1.
On Thursday 10 Jul 2003 23:20, Mark Wilkinson wrote:
Hi David, If you mean has anyone managed to boot a Via EPIA using etherboot as the payload, and loading the kernel via (no pun) tftp, then yes.... but then I wrote it all down in the EPIA howto :-)
oops, hit the wrong key there...
what seems to be the problem that you're having ? your epia.config, the zkernel_start address looks odd. My configs have this option commented out or set to 0xfffc000
what version of etherboot are you using ?
Regards Mark.
Regards Mark.
On Thursday 10 Jul 2003 23:22, David Hendricks wrote:
I see a lot of people here have gotten LinuxBIOS working with the Via EPIA using an IDE device, but has anyone managed to get it working
using
etherboot to boot a kernel over a network? I'm a hopeless newbie and
have
been struggling with this for some time. I have links to logs, my payload, and my config below (Trying to keep the list archives tidy).
I had gotten etherboot working with the PCM-5823s earlier and compared the minicom log with that of my Epia. The only real obvious
discrepency I
see is the entry point. The Geode entered at 0x00094000 (606,208),
while
the Epia is trying to enter at 0x00020000 (131,072).
I'm using CVS versions of Etherboot and LinuxBios. However, I haven't been able to update in the past one or two weeks due to Sourceforge's problems so I might have missed an important patch.
Links EPIA minicom log (High verbosity): http://www.flagen.com/~sc/linux/funstuff/epia-dave My Rhine payload: http://www.flagen.com/~sc/linux/funstuff/via-rhine-ebcvs.elf My config file: http://www.flagen.com/~sc/linux/funstuff/epia.config Geode (Elfboot part only): http://www.flagen.com/~sc/linux/funstuff/geode-elfboot-dave
TIA --David _______________________________________________ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
On Thu, Jul 10, 2003 at 05:12:25PM -0700, David Hendricks wrote:
EPIA howto? I must've overlooked it in my extensive Googling.
Look at freebios/HOWTO directory of your freebios tree. I thought you've been aware of it.
I tried fff80000 because when I run flash_rom, it finds my SST28SF040A at that address. I did notice, however, that you and Sone used fffc0000 for the zkernel_start address. fff80000 does not seem to work at all, so I guess the Epia specifically looks for that address.
SST28SF040A is 512KByte (4Mbit). I'm using 256KB part and as far as I know EPIA comes with 256KB part installed so it's standard for EPIA. If you use the 512KB part, you must change other values in the config.
-- Takeshi
On Friday 11 Jul 2003 01:12, David Hendricks wrote:
EPIA howto? I must've overlooked it in my extensive Googling.
It's in the HOWTO directory from CVS.
I tried fff80000 because when I run flash_rom, it finds my SST28SF040A at that address. I did notice, however, that you and Sone used fffc0000 for the zkernel_start address. fff80000 does not seem to work at all, so I guess the Epia specifically looks for that address.
Oh, you've got a 28SF040.... the chip my EPIA came with is a 39SF020A, which is half the size (hence using 0xfffc0000)
What you might need to do, is set the zkernel_start to 0xfff80000, AND set the ROM_SIZE to 524288.
why ? well, memory address is 0 to 0xffffffff which is a total of 0x100000000 bytes. the bios rom sits at the top of this and extends from 0xffffffff down. if your rom chip is 256K this will extend down my 0x40000 bytes ( to start at 0xfffc0000) as you rom is 512K, this will extend down by 0x80000 bytes (and start at the correctly used and found 0xfff80000)
There may be some magic in the Makefiles that works out the correct ZKERNEL_START from the rom size, but you will need to set the ROM_SIZE option to the size of your rom chip !
You may also have to increase the PAYLOAD_SIZE option by 256K
As to the version of etherboot, i've not used 5.1 to boot from the network, only used it to boot from a CF disk
regards Mark.
My fault for not keeping the epia.config file exactly the same as it was used in the minicom log. That's what I get for being a packrat and keeping so many of them sitting around. The config I'm currently using is exactly the same, but using fffc0000.
As for my etherboot version, it was originally downloaded using CVS on June 25. I'm using version etherboot-5.1.
On Thursday 10 Jul 2003 23:20, Mark Wilkinson wrote:
Hi David, If you mean has anyone managed to boot a Via EPIA using etherboot as the payload, and loading the kernel via (no pun) tftp, then yes.... but then I wrote it all down in the EPIA howto :-)
oops, hit the wrong key there...
what seems to be the problem that you're having ? your epia.config, the zkernel_start address looks odd. My configs have this option commented out or set to 0xfffc000
what version of etherboot are you using ?
Regards Mark.
Regards Mark.
On Thursday 10 Jul 2003 23:22, David Hendricks wrote:
I see a lot of people here have gotten LinuxBIOS working with the Via EPIA using an IDE device, but has anyone managed to get it working
using
etherboot to boot a kernel over a network? I'm a hopeless newbie and
have
been struggling with this for some time. I have links to logs, my payload, and my config below (Trying to keep the list archives tidy).
I had gotten etherboot working with the PCM-5823s earlier and compared the minicom log with that of my Epia. The only real obvious
discrepency I
see is the entry point. The Geode entered at 0x00094000 (606,208),
while
the Epia is trying to enter at 0x00020000 (131,072).
I'm using CVS versions of Etherboot and LinuxBios. However, I haven't been able to update in the past one or two weeks due to Sourceforge's problems so I might have missed an important patch.
Links EPIA minicom log (High verbosity): http://www.flagen.com/~sc/linux/funstuff/epia-dave My Rhine payload: http://www.flagen.com/~sc/linux/funstuff/via-rhine-ebcvs.elf My config file: http://www.flagen.com/~sc/linux/funstuff/epia.config Geode (Elfboot part only): http://www.flagen.com/~sc/linux/funstuff/geode-elfboot-dave
TIA --David _______________________________________________ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
On Thu, 10 Jul 2003, Mark Wilkinson wrote:
what seems to be the problem that you're having ? your epia.config, the zkernel_start address looks odd. My configs have this option commented out or set to 0xfffc000
it's a 512KB part. Is this not addressable on this board?
ron
-
David Hendricks -
Mark Wilkinson -
ron minnich -
SONE Takeshi