On Friday 10 October 2008 15:51:13 Ward Vandewege wrote:
On Fri, Oct 10, 2008 at 12:02:17PM +0300, Roman Yeryomin wrote:
On Fri, Oct 10, 2008 at 10:04 AM, Roman Yeryomin leroi.lists@gmail.com
wrote:
I don't understand - serial works fine for me on the 2c3. Getting serial to work was in fact the 'hardest' part of doing the 2c3 port based on the .1c code, because of the absense of the winbond superio chip. It required all of changing a few lines of code :)
that image you gave me.. serial works with it for you, right? (I didn't check) also what kind of linux distribution you have? does it work with busybox also?
Well, serial doesn't work for me with your image also... :(
Something is wrong then - unless you're not looking at the right speed? 115200 baud.
Note that that image I gave you will not send out much on serial, I reduced the coreboot log level because the alix.2c3 does not have a cmos battery and thus will always default to the hardcoded log level when powered on - and that's set to SPEW right now in the buildrom version. But you should see some output, and then a very quick jump to filo.
Now - if your grub.list file on disk does not specify serial, you might not see filo on serial either. Does it?
I can boot my kernel with your image, that's fine (I can see bios, filo and kernel messages), but as soon as init starts there is no serial console anymore. Very strange. But at the same time no problem with native bios...
Roman
On Fri, Oct 10, 2008 at 07:35:09PM +0300, Roman Yeryomin wrote:
Note that that image I gave you will not send out much on serial, I reduced the coreboot log level because the alix.2c3 does not have a cmos battery and thus will always default to the hardcoded log level when powered on - and that's set to SPEW right now in the buildrom version. But you should see some output, and then a very quick jump to filo.
Now - if your grub.list file on disk does not specify serial, you might not see filo on serial either. Does it?
I can boot my kernel with your image, that's fine (I can see bios, filo and kernel messages), but as soon as init starts there is no serial console anymore. Very strange. But at the same time no problem with native bios...
Ah! Now we are talking. So your serial works until you hit init.
That is a bit odd. It's entirely possible that coreboot is not doing something that busybox requires, but that is not required by init/(m)getty on debian. I'm not sure what that would be though :/
Thanks, Ward.
On Fri, Oct 10, 2008 at 9:52 AM, Ward Vandewege ward@gnu.org wrote:
That is a bit odd. It's entirely possible that coreboot is not doing something that busybox requires, but that is not required by init/(m)getty on debian. I'm not sure what that would be though :/
interrupt setup?
ron
-
Roman Yeryomin -
ron minnich -
Ward Vandewege