I'm not sure if it's buildrom's fault or SeaBIOS's, but the build fails for me with this error:
make[1]: P: Command not found
It's actually a symptom that $(CPP) isn't being set. When I add these lines in SeaBIOS's Makefile, it goes away.
ifeq ($(CPP),) CPP=$(CC) -E endif
Where should it get fixed?
Thanks, Myles
On Thu, Jul 03, 2008 at 04:27:51PM -0600, Myles Watson wrote:
Kevin,
I didn't have my windows CD handy, so I tried several Linux install CDs, but I can't get them to boot on my s2892. They boot fine in qemu with SeaBIOS.
Okay - thanks for trying.
Here's the log:
I don't see anything unusual in the log. Did all the OSes die in the same way? Did anything come up on the vga screen? What OSes did you try?
On Thu, Jul 03, 2008 at 03:54:11PM -0600, Myles Watson wrote:
I'm not sure if it's buildrom's fault or SeaBIOS's, but the build fails for me with this error:
make[1]: P: Command not found
It's actually a symptom that $(CPP) isn't being set. When I add these lines in SeaBIOS's Makefile, it goes away.
ifeq ($(CPP),) CPP=$(CC) -E endif
That's very odd. What distro did you try to build on?
-Kevin
On 04.07.2008 08:40, Kevin O'Connor wrote:
On Thu, Jul 03, 2008 at 04:27:51PM -0600, Myles Watson wrote:
Kevin,
I didn't have my windows CD handy, so I tried several Linux install CDs, but I can't get them to boot on my s2892. They boot fine in qemu with SeaBIOS.
Okay - thanks for trying.
Here's the log:
I don't see anything unusual in the log. Did all the OSes die in the same way? Did anything come up on the vga screen? What OSes did you try?
I found the various "await_ide: ERROR" and "fail floppy_13XX" messages interesting. In another mail you said you're not sure the floppy support works with real hardware. Could that be one of the reasons for the problems Myles is seeing?
Regards, Carl-Daniel
Hi Carl-Daniel,
On Fri, Jul 04, 2008 at 02:27:08PM +0200, Carl-Daniel Hailfinger wrote:
On 04.07.2008 08:40, Kevin O'Connor wrote:
I don't see anything unusual in the log. Did all the OSes die in the same way? Did anything come up on the vga screen? What OSes did you try?
I found the various "await_ide: ERROR" and "fail floppy_13XX" messages interesting. In another mail you said you're not sure the floppy support works with real hardware. Could that be one of the reasons for the problems Myles is seeing?
I did notice the "await_ide: ERROR", but the cdrom code was written to handle errors during ata_detect_medium (I guess real drives do that?). The cdrom did eventually return a valid looking sector count and size, so it doesn't look wrong to me.
Myles stated that he had CONFIG_FLOPPY_SUPPORT disabled. If so, I don't see it causing a problem as the code wouldn't even be included. The "fail floppy_13XX" messages would be normal if the code isn't compiled in - every floppy bios call would return a failure status.
-Kevin
Hi Kevin,
On 04.07.2008 20:59, Kevin O'Connor wrote:
Hi Carl-Daniel,
On Fri, Jul 04, 2008 at 02:27:08PM +0200, Carl-Daniel Hailfinger wrote:
On 04.07.2008 08:40, Kevin O'Connor wrote:
I don't see anything unusual in the log. Did all the OSes die in the same way? Did anything come up on the vga screen? What OSes did you try?
I found the various "await_ide: ERROR" and "fail floppy_13XX" messages interesting. In another mail you said you're not sure the floppy support works with real hardware. Could that be one of the reasons for the problems Myles is seeing?
I did notice the "await_ide: ERROR", but the cdrom code was written to handle errors during ata_detect_medium (I guess real drives do that?). The cdrom did eventually return a valid looking sector count and size, so it doesn't look wrong to me.
Myles stated that he had CONFIG_FLOPPY_SUPPORT disabled. If so, I don't see it causing a problem as the code wouldn't even be included. The "fail floppy_13XX" messages would be normal if the code isn't compiled in - every floppy bios call would return a failure status.
Hmmm. I do believe you. I'd be interested in what a proprietary BIOS does when no floppy is present and when floppy support is disabled. IIRC there is a BIOS call listing the number of floppies which never fails.
Regards, Carl-Daniel
-----Original Message----- From: Kevin O'Connor [mailto:kevin@koconnor.net] Sent: Friday, July 04, 2008 12:41 AM To: Myles Watson Cc: Coreboot Subject: Re: [coreboot] SeaBIOS booting
On Thu, Jul 03, 2008 at 04:27:51PM -0600, Myles Watson wrote:
Kevin,
I didn't have my windows CD handy, so I tried several Linux install CDs, but I can't get them to boot on my s2892. They boot fine in qemu with SeaBIOS.
Okay - thanks for trying.
Here's the log:
I don't see anything unusual in the log. Did all the OSes die in the same way? Did anything come up on the vga screen? What OSes did you try?
I tried the Ultimate Boot CD, a Fedora CD, and a CD I'd made that just runs grub.
On Thu, Jul 03, 2008 at 03:54:11PM -0600, Myles Watson wrote:
I'm not sure if it's buildrom's fault or SeaBIOS's, but the build fails for me with this error:
make[1]: P: Command not found
It's actually a symptom that $(CPP) isn't being set. When I add these lines in SeaBIOS's Makefile, it goes away.
ifeq ($(CPP),) CPP=$(CC) -E endif
That's very odd. What distro did you try to build on?
Fedora 7. It might be buildrom's problem, since CPP is defined when I checked in the main Makefile. I'll have to look around for why it's getting undefined.
Thanks, Myles
-Kevin
On Fri, Jul 4, 2008 at 1:46 PM, Myles Watson mylesgw@gmail.com wrote:
-----Original Message----- From: Kevin O'Connor [mailto:kevin@koconnor.net] Sent: Friday, July 04, 2008 12:41 AM To: Myles Watson Cc: Coreboot Subject: Re: [coreboot] SeaBIOS booting
On Thu, Jul 03, 2008 at 04:27:51PM -0600, Myles Watson wrote:
Kevin,
I didn't have my windows CD handy, so I tried several Linux install CDs, but I can't get them to boot on my s2892. They boot fine in qemu with SeaBIOS.
Okay - thanks for trying.
Here's the log:
Kevin,
I don't see anything unusual in the log. Did all the OSes die in the same way?
Yes.
Did anything come up on the vga screen?
I missed this question the first time. Nothing comes up on the VGA screen. That was especially interesting to me because when I tried to boot the Windows CD in qemu, if I press F12 for the boot menu, then select 3. CD-ROM, it says Press Any Key to Boot from CD..... If you wait until all 5 dots are there, you can't press any key any more. It hangs.
Maybe that's what's happening, maybe it's something else, I'm still looking.
Does the lack of VGA output give any hints? I have VGA output until it jumps to the SeaBIOS, but nothing after that.
Thanks, Myles
On Mon, Jul 07, 2008 at 11:52:21AM -0600, Myles Watson wrote:
I don't see anything unusual in the log. Did all the OSes die in the same way?
Yes.
Did anything come up on the vga screen?
I missed this question the first time. Nothing comes up on the VGA screen. That was especially interesting to me because when I tried to boot the Windows CD in qemu, if I press F12 for the boot menu, then select 3. CD-ROM, it says Press Any Key to Boot from CD..... If you wait until all 5 dots are there, you can't press any key any more. It hangs.
Hrmm - I don't see this on my machine. Did you compile seabios yourself? Maybe it's being miscompiled on your machine. Can you try the elf at:
http://linuxtogo.org/~kevin/SeaBIOS/bios.bin.elf-0.2.3
Maybe that's what's happening, maybe it's something else, I'm still looking.
Does the lack of VGA output give any hints? I have VGA output until it jumps to the SeaBIOS, but nothing after that.
It's very odd. From your log:
Scan for VGA option rom Running option rom at 000c0003
That indicates that seabios found your vga rom and ran it. I don't know why you wouldn't see seabios' output on the screen.
It can be pretty challenging to debug these problems. The only thing I can think of that will help is to try and increase the debug levels in src/config.h.
I'm currently tracking down a boot failure with os/2 under qemu. Maybe the fix will improve booting on other OSes as well.
-Kevin
-----Original Message----- From: Kevin O'Connor [mailto:kevin@koconnor.net] Sent: Monday, July 07, 2008 5:47 PM To: Myles Watson Cc: Coreboot Subject: Re: [coreboot] SeaBIOS booting
On Mon, Jul 07, 2008 at 11:52:21AM -0600, Myles Watson wrote:
I don't see anything unusual in the log. Did all the OSes die in the same way?
Yes.
Did anything come up on the vga screen?
I missed this question the first time. Nothing comes up on the VGA screen. That was especially interesting to me because when I tried to boot the Windows CD in qemu, if I press F12 for the boot menu, then select 3. CD-ROM, it says Press Any Key to Boot from CD..... If you wait until all 5 dots are there, you can't press any key any more. It hangs.
Hrmm - I don't see this on my machine. Did you compile seabios yourself? Maybe it's being miscompiled on your machine. Can you try the elf at:
Same behavior. What version of qemu are you using? I'm using the patched version of 0.9.0.
http://linuxtogo.org/~kevin/SeaBIOS/bios.bin.elf-0.2.3
Maybe that's what's happening, maybe it's something else, I'm still
looking.
Does the lack of VGA output give any hints? I have VGA output until it jumps to the SeaBIOS, but nothing after that.
It's very odd. From your log:
Scan for VGA option rom Running option rom at 000c0003
That indicates that seabios found your vga rom and ran it. I don't know why you wouldn't see seabios' output on the screen.
I tried a different boot CD (Knoppix), and it doesn't give me any output until later in the boot process. Once it gets to a certain point, the text output appears, but it is only displayed in the top 5 lines of the screen, and continues to display the coreboot boot messages everywhere else. Once Knoppix boots into the graphical mode, it works fine.
I'm thinking that the text output from the other CDs is getting lost. I tried turning on the debugging output from handler_10, but it is a lot to go through. I tried adding in a different video card, but it isn't getting past the emulator.
It can be pretty challenging to debug these problems. The only thing I can think of that will help is to try and increase the debug levels in src/config.h.
It looks like the characters are getting passed to the video BIOS. I don't know why they get lost from there.
If you have any ideas for where to look next...
Thanks, Myles
I'm currently tracking down a boot failure with os/2 under qemu. Maybe the fix will improve booting on other OSes as well.
-Kevin
On Mon, Jul 07, 2008 at 07:46:55PM -0400, Kevin O'Connor wrote:
I'm currently tracking down a boot failure with os/2 under qemu. Maybe the fix will improve booting on other OSes as well.
Well, I fixed OS/2 booting under qemu. It was a floppy code error. Unfortunately, I'm still not having any luck with XP on my epia.
-Kevin
-
Carl-Daniel Hailfinger -
Kevin O'Connor -
Myles Watson