Re: [coreboot] FILO and SATA on 690/600

[Dan Lykowski]

This is the section I am concerned about.
It is having trouble detecting my SATA Flash on the master port.

Waiting for ide0 to become ready for reset... ok

Resetting ide0... ok

Testing for hda

ProbIDE: status=0x58, err=0x0

Testing for hda

ProbIDE: status=0x51, err=0x4

MASTER CHECK: master no  /* slave */ -- drive is 0

NO MASTER -- check slave!

The SATA flash has been really picky.
My first guess is that I think the IDE device register setup might be the problem.
I am trying to understand why IDE_DH_CHS/IDE_DH_LBA are named the way they are? The
bits being set by these macros are legacy for setting a sector size and
should always be set to 1-0 according to everything I have read. Using IDE_DH_LBA instead of IDE_DH_CHS would set the right bits.

Current FILO:
   cmd.device = IDE_DH_DEFAULT | IDE_DH_HEAD(0) | IDE_DH_CHS | info->slave;

Psedo code based on what Grub2 does: 
   device_reg = 0xE0 | (slave)?slave_bits:master_bits

I believe this would be correct for FILO:
   cmd.device = IDE_DH_DEFAULT | IDE_DH_HEAD(0) | IDE_DH_LBA | info->slave

This of course is just a hunch at the moment. I won't be able to try it until Monday.

Thanks,
Dan Lykowski

--- On Sat, 1/17/09, Wang, Qingpei  wrote:

From: Wang, Qingpei 
Subject: Re: [coreboot] FILO and SATA on 690/600
To: "Dan Lykowski" , [e-mail], "Peter Stuge" 
Date: Saturday, January 17, 2009, 3:20 AM

Hi,

Please
see below.

Jason Wang

BeiJing Technology 
 Development Center

Advanced Micro Devices (AMD)

From:
[e-mail] [mailto:[e-mail]] On Behalf Of Dan Lykowski

Sent: Saturday, January 17, 2009
2:59 PM

To: [e-mail]; Peter
Stuge

Subject: Re: [coreboot] FILO and
SATA on 690/600

Peter,

I will test it when I get in to work on Monday.

I was able to get a HDD to be detected. My SATA flash is still being
  stubborn.

Here is my log: (Without Peters Patch)

boot eax = 0x2badb002

boot ebx = 0xf3400

boot arg = 0xf3400

Current location: 0x100000-0x49e117

Relocating to 0x37c61000-0x37fff117... ok

00:13.0 4387:1002.0 OHCI controller

00:13.1 4388:1002.1 OHCI controller

00:13.2 4389:1002.2 OHCI controller

00:13.3 438a:1002.3 OHCI controller

00:13.4 438b:1002.4 OHCI controller

00:13.5 4386:1002.5 EHCI controller

Not supported.

ERROR: No such CMOS option (boot_devices)

Press <Enter> for default menu.lst (hda1:/boot/filo/menu.lst), or
  <Esc> for prompt...

menu: hda1:/boot/filo/menu.lst

dev=hda1, path=/boot/filo/default

Scanning for: SATA

...

found PCI IDE controller 1002:4380

prog_if=0x8f

primary channel: native PCI mode

cmd_base=0x3020 ctrl_base=0x3060

init_controller: drive 0

Waiting for ide0 to become ready for reset... ok

Resetting ide0... ok

Testing for hda

ProbIDE: status=0x58, err=0x0

Testing for hda

ProbIDE: status=0x51, err=0x4

MASTER CHECK: master no  /* slave */ -- drive is 0

NO MASTER -- check slave!

Testing for hda

ProbLBA mode, sectors=156301488

Init device params... ok

hda: LBA 80GB: WDC WD800JD-22JNA0

SLAVE ONLY CHECK: slave yes

Partition 1 start 64260 length 16787925

Unknown filesystem type. 
  [Jason, Wang] if seems that filo can not detect the the filesystem
  type. 
  Did hda1 is an ext2 or ext3 filesystem 
  Change the filo config.h MENULST_FILE to the correct path of your
  linux boot path. And try again

dev=hda1, path=/boot/filo/menu.lst

already open

Could not open menu.lst file 'hda1:/boot/filo/menu.lst'.

Entering command line.

[Jason, Wang] please make sure that the /boot/filo/menu.lst exist

Thanks,

Dan Lykowski

--- On Sat, 1/17/09, Peter Stuge  wrote:

From: Peter Stuge

Subject: Re: [coreboot] FILO and SATA on 690/600

To: [e-mail]

Date: Saturday, January 17, 2009, 1:09 AM

-----Inline Attachment Follows-----

Dan Lykowski wrote:
> Has anyone been able to boot a SATA drive using FILO on a 690/600
> platform?
> I keep getting IDE timeouts on detection.

I would be interested in debug output from filo-0.5, e.g. r52, with

http://stuge.se/filo.r52.ide_ext2_pio4_debug6.patch
  applied and both

DEBUG_PCI = 1 and DEBUG_IDE = 1 in Config. Please also set

USE_GRUB = 0 to make the interface easier to work with.

//Peter

coreboot mailing list: [e-mail]

http://www.coreboot.org/mailman/listinfo/coreboot

-----Inline Attachment Follows-----