Thanks again (Myles & everyone) for discussing coreboot for s4882 until I could compile & install. After doing so, my s4882 just has a blank screen and continually does 2 alternating beeps (like a siren.)
I saw no POST codes on coreboot.org. I saved coreboot.rom and now have a Slackware pII system up (no coreboot) as well as a Windows 2.4GHz Athlon. What next?
I only installed grub2 as payload; grub2 may not be the problem: IIRC, I included chainloader in grub2.elf: my '/' has LILO. Coreboot.org has 'official grub' (grub2) and 'grub2' pages, which say different things, though they likely mean the same thing.
I neither want to re-flash old BIOS nor yet try coreboot on my alternate Slackware system, though I plan to after any possible functional s4882 build.
Coreboot compiles within about 1 min. on 8-core a880 w/8Gb and would be relatively quick even on dual pIII. I am unsure about pII (I skipped from pI.) Does DJGPP work well on XP, or are Cygwin or MinGW like it? I have never done GUI programming--incl. 'programming on an OS requiring GUI (except in class)' and would rather not boot Windows until I learn to add it to BOINC ( http://boinc.berkeley.edu ) on a LAN.
--David
On Thu, Feb 5, 2009 at 7:42 PM, David Melik dchmelik@gmail.com wrote:
Thanks again (Myles & everyone) for discussing coreboot for s4882 until I could compile & install. After doing so, my s4882 just has a blank screen
Do you have a null-modem cable? Did you see anything on the serial console?
and continually does 2 alternating beeps (like a siren.)
The siren is the chipset complaining that its timer wasn't touched for too long. That sounds like an early problem.
I saw no POST codes on coreboot.org.
I don't know where there's a list of them, but if you grep the source for post_code you'll find some.
I saved coreboot.rom and now have a Slackware pII system up (no coreboot) as well as a Windows 2.4GHz Athlon. What next?
What size is your coreboot.rom (ls -l)? What size is your chip? That's a frequent problem. If you had to add another ROM, did you prepend it?
Have you tried it with a warm reset? It's a bit of a long shot, but it can affect things sometimes.
I only installed grub2 as payload; grub2 may not be the problem: IIRC, I included chainloader in grub2.elf: my '/' has LILO. Coreboot.org has 'official grub' (grub2) and 'grub2' pages, which say different things, though they likely mean the same thing.
It is very unlikely that it is reaching the payload. If you're worried about that, use buildrom to build a payload. Grub2 from buildrom works well as long as you substitute ata for hd in the grub.cfg.
I neither want to re-flash old BIOS nor yet try coreboot on my alternate Slackware system, though I plan to after any possible functional s4882 build.
Coreboot compiles within about 1 min. on 8-core a880 w/8Gb and would be relatively quick even on dual pIII. I am unsure about pII (I skipped from pI.) Does DJGPP work well on XP, or are Cygwin or MinGW like it? I have never done GUI programming--incl. 'programming on an OS requiring GUI (except in class)' and would rather not boot Windows until I learn to add it to BOINC ( http://boinc.berkeley.edu ) on a LAN.
--David
-- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
On 2/6/09, Myles Watson mylesgw@gmail.com wrote:
Do you have a null-modem cable? Did you see anything on the serial console?
I have such cables; maybe not a serial console, but away from university I have some old analog monitors....
[...] if you grep the source for post_code you'll find some.
Good. I will try this weekend.
What size is your coreboot.rom (ls -l)? What size is your chip?
That's a frequent problem. If you had to add another ROM, did you prepend it?
The .rom (saved on a WD 24000 that Slackware 10.2 cannot mount) size had '5:' over 512 Kb I guess. The manual says 4 MB. Apparently my ROM is too small... I doubt I need certain grub2 modules, but I know not what others do.
Would it help Coreboot more if I make a smaller grub2 to test newer coreboot2 on s4882 asap or if wait a while and 'prepend' (if it involves soldering that is alright.) I know It can be specially configured; maybe that needs more ROM.
Have you tried it with a warm reset? It's a bit of a long shot, but
it can affect things sometimes.
I think I at least tried or also turned it on later 1 - 3 times.
It is very unlikely that it is reaching the payload. [...] Grub2 from
buildrom works well as long as you substitute ata for hd in the grub.cfg.
I may try but would like to try serial consoles:
I neither want to re-flash [old] BIOS nor yet try coreboot on my alternate
Slackware system[....]
--David
On Fri, Feb 6, 2009 at 4:21 AM, David Melik dchmelik@gmail.com wrote:
On 2/6/09, Myles Watson mylesgw@gmail.com wrote:
Do you have a null-modem cable? Did you see anything on the serial console?
I have such cables; maybe not a serial console, but away from university I have some old analog monitors....
Serial console in this context refers to connecting the serial port of the s4882 to another machine's via null modem cable and using a terminal emulator program like minicom, gtkterm, etc. on the other machine to see what the s4882 is writing to the serial port.
[...] if you grep the source for post_code you'll find some.
Good. I will try this weekend.
What size is your coreboot.rom (ls -l)? What size is your chip? That's a frequent problem. If you had to add another ROM, did you prepend it?
The .rom (saved on a WD 24000 that Slackware 10.2 cannot mount) size had '5:' over 512 Kb I guess. The manual says 4 MB. Apparently my ROM is too small... I doubt I need certain grub2 modules, but I know not what others do.
It's important that the size is exact. Flash is sized in megabits, so 4 Mbits = 512KB. This probably isn't the problem, I just wanted to make sure.
There is a lot of valuable information on coreboot.org. I recommend reading through the developer pages.
Thanks, Myles
Would it help Coreboot more if I make a smaller grub2 to test newer coreboot2 on s4882 asap or if wait a while and 'prepend' (if it involves soldering that is alright.) I know It can be specially configured; maybe that needs more ROM.
Have you tried it with a warm reset? It's a bit of a long shot, but it can affect things sometimes.
I think I at least tried or also turned it on later 1 - 3 times.
It is very unlikely that it is reaching the payload. [...] Grub2 from buildrom works well as long as you substitute ata for hd in the grub.cfg.
I may try but would like to try serial consoles:
I neither want to re-flash [old] BIOS nor yet try coreboot on my alternate Slackware system[....]
--David
-- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
-
David Melik -
Myles Watson