Re: [coreboot] Seabios problems

Hello Kevin,

I can't give you the full log for the keyboard problem. I think this is a timeout issue:
when I run Seabios in debuglevel=8, no problem, but if debuglevel=1 or even 4, my keyboard don't want to initialize most of the time. So, I suppose that sending debug data to the port gives time to the keyboard to initialize correctly.

The attachment files are the logs you asked me reporting the Vista booting error.
Do you use DMA since version 0.5.1 to boot ?

Regards.
> Message du 16/01/10 à 06h52
> De : "Kevin O'Connor" 
> A : [e-mail]
> Copie à : [e-mail], "coreboot" 
> Objet : Re: [coreboot] Seabios problems
>
> On Fri, Jan 15, 2010 at 02:27:39PM +0100, [e-mail] wrote:
> > Hello,
> >
> > I wanted to upgrade my seabios version, but some troubles arrived.
> >
> > 0.5.0  : keyboard timeout problem (I think)
> > error: ps2_recvbyte timeout
> >                                             keyboard self test failed (got e0 not 0xaa)
> >
> > 0.5.1 : same problem as 0.5.0 and Vista don't want to boot
> >
> > I don't have any problems with my previous version pre-0.4.3.
> > I run coreboot rev5007 on my asus m2v-mx_se.
> >
> > Does anyone report those troubles before ?
>
> I haven't seen this reported before.  Can you set the debug level to 8
> on both the working and non-working versions of SeaBIOS and post the
> full logs?
>
> Thanks,
> -Kevin

____________________________________________________

Vous n’avez pas encore adressé vos voeux ? Retrouvez nos cartes sur http://carte-de-voeux.voila.fr

Seabios problems

[Kevin O'Connor]

On Sat, Jan 16, 2010 at 12:06:01PM +0100, [e-mail] wrote:
> Hello Kevin,
>
> I can't give you the full log for the keyboard problem. I think this
> is a timeout issue: when I run Seabios in debuglevel=8, no problem,
> but if debuglevel=1 or even 4, my keyboard don't want to initialize
> most of the time. So, I suppose that sending debug data to the port
> gives time to the keyboard to initialize correctly.

Okay - can you send a log with a failure when at debug level 4 then?
> The attachment files are the logs you asked me reporting the Vista
> booting error.  Do you use DMA since version 0.5.1 to boot ?

Okay - I'll take a look.  It seems there is an issue with DMA on your
board.  What's 'lspci' report for your machine?

-Kevin

Seabios problems

[Kevin O'Connor]

On Sat, Jan 16, 2010 at 12:06:01PM +0100, [e-mail] wrote:
> Hello Kevin,
>
> I can't give you the full log for the keyboard problem. I think this
> is a timeout issue: when I run Seabios in debuglevel=8, no problem,
> but if debuglevel=1 or even 4, my keyboard don't want to initialize
> most of the time. So, I suppose that sending debug data to the port
> gives time to the keyboard to initialize correctly.
>
> The attachment files are the logs you asked me reporting the Vista
> booting error.  Do you use DMA since version 0.5.1 to boot ?

Lets try a couple of things.  For the keyboard, can you see if this
change improves things?  In either case, can you send the output it
produces?

--- a/src/ps2port.c
+++ b/src/ps2port.c
@@ -62,7 +62,7 @@ i8042_flush(void)
             return 0;
         udelay(50);
         u8 data = inb(PORT_PS2_DATA);
-        dprintf(7, "i8042 flushed %x (status=%x)\n", data, status);
+        dprintf(1, "i8042 flushed %x (status=%x)\n", data, status);
     }

dprintf(1, "i8042 timeout on flush\n");

Your ps2 port has stale data in it, and I think that is causing the
init process to get confused.

For the DMA issue, it looks like your drive isn't ready for it.  Can
you see if this change improves things?

--- a/src/ata.c
+++ b/src/ata.c
@@ -856,6 +856,15 @@ init_drive_ata(struct drive_s *dummy, u16 *buffer)
     // Register with bcv system.
     add_bcv_internal(drive_g);

+    // XXX - set dma mode
+    struct ata_pio_command cmd;
+    memset(&cmd, 0, sizeof(cmd));
+    cmd.command = ATA_CMD_SET_FEATURES;
+    cmd.feature = 0x03;
+    cmd.sector_count = 0x22; // mwDMA mode 2
+    ret = ata_cmd_nondata(drive_g, &cmd);
+    dprintf(1, "set drive=%p dma=%d\n", drive_g, ret);
+
     return drive_g;
 }

Thanks,
-Kevin