I'm using FILO with nVidia reference board with a CK804. I've got LinuxBIOS to load FILO and FILO sees the IDE controller but not the drive. I thought FILO was device independent, but could the IDE controllers on the CK804 require FILO changes? Thanks.
Steve
----------------------- serial output ----------------------------------- Press <Enter> for default boot, or <Esc> for boot prompt... boot: hdc1:/boot/vmlinuz-2.6.9-1.667smp initrd=hdc1:/boot/initrd-2.6.9-1.667smp.img root=LABEL=/1 console=tty0 console=ttyS0,115200 desktop splash=silent showopts malloc_diag: alloc: 624 bytes (5 blocks), free: 15752 bytes (1 blocks) malloc_diag: alloc: 640 bytes (6 blocks), free: 15736 bytes (1 blocks) file_open: dev=hdc1, path=/boot/vmlinuz-2.6.9-1.667smp find_ide_controller: found PCI IDE controller 10de:0053 prog_if=0x8a find_ide_controller: secodary channel: compatibility mode find_ide_controller: cmd_base=0x170 ctrl_base=0x374 Detected floating bus No drive detected on IDE channel 1 devopen: failed to open ide malloc_diag: alloc: 624 bytes (5 blocks), free: 15752 bytes (1 blocks) malloc_diag: alloc: 456 bytes (4 blocks), free: 15920 bytes (1 blocks) boot: hdc1:/boot/vmlinuz-2.6.9-1.667smp initrd=hdc1:/boot/initrd-2.6.9-1.667smp.img root=LABEL=/1 console=tty0 console=ttyS0,115200 desktop splash=silent showopts malloc_diag: alloc: 624 bytes (5 blocks), free: 15752 bytes (1 blocks) malloc_diag: alloc: 640 bytes (6 blocks), free: 15736 bytes (1 blocks) file_open: dev=hdc1, path=/boot/vmlinuz-2.6.9-1.667smp Drive 2 does not exist devopen: failed to open ide malloc_diag: alloc: 624 bytes (5 blocks), free: 15752 bytes (1 blocks) malloc_diag: alloc: 456 bytes (4 blocks), free: 15920 bytes (1 blocks) boot: hdc1:/boot/vmlinuz-2.6.9-1.667smp initrd=hdc1:/boot/initrd-2.6.9-1.667smp.img root=LABEL=/1 console=tty0 console=ttyS0,115200 desktop splash=silent showopts
On Wed, 2 Mar 2005 Stephen.Kimball@bench.com wrote:
I'm using FILO with nVidia reference board with a CK804. I've got LinuxBIOS to load FILO and FILO sees the IDE controller but not the drive. I thought FILO was device independent, but could the IDE controllers on the CK804 require FILO changes?
Wow, you've taken this far.
Not sure yet. I need a board, so guess we'll order some. ron
* Stephen.Kimball@bench.com Stephen.Kimball@bench.com [050302 19:40]:
I'm using FILO with nVidia reference board with a CK804. I've got LinuxBIOS to load FILO and FILO sees the IDE controller but not the drive. I thought FILO was device independent, but could the IDE controllers on the CK804 require FILO changes? Thanks.
You should be using 0.4.2 and be sure to set PCI_BRUTE_SCAN = 1
You probably end up with filo not looking at anything but bus 0. Common problem on amd64 boards.
Stefan
Why not try Etherboot at first? That would be easier.
On Wed, 2 Mar 2005 20:06:40 +0100, Stefan Reinauer stepan@openbios.org wrote:
- Stephen.Kimball@bench.com Stephen.Kimball@bench.com [050302 19:40]:
I'm using FILO with nVidia reference board with a CK804. I've got LinuxBIOS to load FILO and FILO sees the IDE controller but not the drive. I thought FILO was device independent, but could the IDE controllers on the CK804 require FILO changes? Thanks.
You should be using 0.4.2 and be sure to set PCI_BRUTE_SCAN = 1
You probably end up with filo not looking at anything but bus 0. Common problem on amd64 boards.
Stefan
Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
On Wed, 2 Mar 2005, yhlu wrote:
Why not try Etherboot at first? That would be easier.
we've never found it to be easier, but that is a point of disagreement between several places :-)
ron