Re: [LinuxBIOS] Etherboot (FILO) with SATA on tyan s2895

[Myles Watson]

I didn't have another sata disk, but I looked again and noticed that the
network didn't work either.  Here is the first suspicious snippet of
/var/log/messages:

May 26 13:36:20 orangutan kernel: ACPI: Unable to locate RSDP
May 26 13:36:20 orangutan kernel: Scanning NUMA topology in Northbridge 24
May 26 13:36:20 orangutan kernel: Number of nodes 2
May 26 13:36:20 orangutan kernel: Node 0 MemBase 0000000000000000 Limit
0000000080000000
May 26 13:36:20 orangutan kernel: Node 1 MemBase 0000000080000000 Limit
0000000140000000
May 26 13:36:20 orangutan kernel: Using node hash shift of 31
May 26 13:36:20 orangutan kernel: Bootmem setup node 0
0000000000000000-0000000080000000
May 26 13:36:20 orangutan kernel: Bootmem setup node 1
0000000080000000-0000000140000000

Then part that talks about SATA:

May 26 13:36:27 orangutan kernel: SCSI subsystem initialized
May 26 13:36:27 orangutan kernel: ata1: SATA max UDMA/133 cmd 0x2850 ctl
0x28A2 bmdma 0x2830 irq 23
May 26 13:36:27 orangutan kernel: ata2: SATA max UDMA/133 cmd 0x2860 ctl
0x28B2 bmdma 0x2838 irq 23
May 26 13:36:27 orangutan kernel: input: ImPS/2 Generic Wheel Mouse as
/class/input/input1
May 26 13:36:27 orangutan kernel: ata1: SATA link down (SStatus 0)
May 26 13:36:27 orangutan kernel: scsi0 : sata_nv
May 26 13:36:27 orangutan kernel: ata2: SATA link down (SStatus 0)
May 26 13:36:27 orangutan kernel: scsi1 : sata_nv
May 26 13:36:27 orangutan kernel: ata3: SATA max UDMA/133 cmd 0x2870 ctl
0x28C2 bmdma 0x2840 irq 22
May 26 13:36:27 orangutan kernel: ata4: SATA max UDMA/133 cmd 0x2880 ctl
0x28D2 bmdma 0x2848 irq 22
May 26 13:36:27 orangutan kernel: ata3: SATA link down (SStatus 0)
May 26 13:36:27 orangutan kernel: scsi2 : sata_nv
May 26 13:36:27 orangutan kernel: ata4: SATA link down (SStatus 0)
May 26 13:36:27 orangutan kernel: scsi3 : sata_nv

And another with the network:

May 26 13:36:28 orangutan kernel: forcedeth.c: Reverse Engineered nForce
ethernet driver. Version 0.49.
May 26 13:36:28 orangutan kernel: PCI: Error while updating region
0000:00:0a.0/0 (f5205000 != 00000000)
May 26 13:36:28 orangutan kernel: PCI: Enabling device 0000:00:0a.0 (0000 ->
0003)
May 26 13:36:28 orangutan kernel: 0000:00:0a.0: Invalid Mac address
detected: ff:ff:ff:ff:ff:ff
May 26 13:36:28 orangutan kernel: Please complain to your hardware vendor.
Switching to a random MAC.
May 26 13:36:28 orangutan kernel: 0000:00:0a.0: open: Could not find a valid
PHY.
May 26 13:36:28 orangutan kernel: forcedeth: probe of 0000:00:0a.0 failed
with error -12
May 26 13:36:28 orangutan kernel: eth0: forcedeth.c: subsystem: 010f1:2895
bound to 0000:80:0a.0
May 26 13:36:28 orangutan kernel: nvnet: module license 'NVIDIA' taints
kernel.
May 26 13:36:28 orangutan kernel: ERROR: nvenet_probe, unable to create
adapter object
May 26 13:36:28 orangutan kernel: nvnet: probe of 0000:00:0a.0 failed with
error -12

Is there somewhere that the ACPI information should be getting passed
through, and it's getting clobbered? I'm booting LinuxBIOS -> FILO/Etherboot
-> Kernel on an IDE disk.

Thanks,
Myles

-----Original Message-----
From: [e-mail]
[mailto:[e-mail]] On Behalf Of yhlu
Sent: Thursday, May 25, 2006 9:11 PM
To: [e-mail]
Cc: [e-mail]
Subject: Re: [LinuxBIOS] Etherboot (FILO) with SATA on tyan s2895

It seems some old version sata disk has problem. Can you try some new sata
disk?

YH

On 5/25/06, Myles Watson  wrote:
> I decided to just add an IDE drive to boot the first kernel.  Until I had
> LinuxBIOS booting, I felt like the 512KB that the BIOS Savior gave me was
> too little to play with for adding tiny Linux. After I can reliably boot
> from the 512KB "backup" I'll think about writing over my original 1 MB :)
>
> When I boot from LinuxBIOS to the IDE drive it doesn't recognize my SATA
> drives, even though sata_nv gets loaded. They get mounted normally when I
> boot from the same drive with the factory BIOS.  Any ideas or hints?
>
> Thanks,
> Myles
>
> -----Original Message-----
> From: [e-mail]
> [mailto:[e-mail]] On Behalf Of Myles Watson
> Sent: Thursday, May 18, 2006 7:49 AM
> To: 'Lu, Yinghai'; [e-mail]
> Subject: Re: [LinuxBIOS] Etherboot (FILO) with SATA on tyan s2895
>
> It's starting to seem like a long chain of events from LinuxBIOS to
> Etherboot to FILO to kernel on CF to myKernel.  I'd also like to be able

to
> get to grub eventually.  Is there a way to go from LinuxBIOS to grub more
> directly on the s2895?
>
> Thanks again for your help.
>
> Myles
>
> -----Original Message-----
> From: Lu, Yinghai [mailto:[e-mail]]
> Sent: Wednesday, May 17, 2006 5:09 PM
> To: [e-mail]; [e-mail]
> Subject: RE: [LinuxBIOS] Etherboot (FILO) with SATA on tyan s2895
>
> You can not boot from CK804 sata directly with FILO in Etherboot.
>
> The code only support Sata that can work on compatible IDE mode.
>
> You need to use other media ( network, CF IDE flash) to load kernel with
> ck804 sata and kexec support, and use kexec to load final kernel in your
> sata disk.
>
> YH
>
> -----Original Message-----
> From: [e-mail]
> [mailto:[e-mail]] On Behalf Of Myles Watson
> Sent: Wednesday, May 17, 2006 3:57 PM
> To: [e-mail]
> Subject: [LinuxBIOS] Etherboot (FILO) with SATA on tyan s2895
>
> I am booting linuxbios with etherboot and filo as the payload. I tried
> to
> follow the s2881 tutorial on the wiki.
>
> Etherboot only finds my cd-rom. When I try to use hde:/ it tells me that
> "Drive 4 does not exist". All drives up to j except hda (my cd-rom) give
> the
> same error message. Sometimes if I try hdg it hangs.
>
> I saw README.filo_in_etherboot where it says it only works on SATA port
> 1 or
> 2. I've tried on SATA 0 port 0 and 1, SATA 1 port 2 and 3.
>
> I also seem to need to boot the factory BIOS in between each attempt, or
> I
> won't get very far.
>
> Is there something simple I've missed?
>
> Thanks,
> Myles
>
> Output:
>
> Etherboot 5.4.2
> Drivers: TG3 FILO Images: NBI ELF
> Protocols: DHCP TFTP
> Relocating text ...
> Scanning PCI: found 30 devices
> Probing pci disk...
> [FILO]FILO version 0.4.1
> boot: hde3:/boot/vmlinuz... initrd=/boot/initrd...
> IDE time out
> No drive detected on IDE channel 2
> boot: hdc:/
> No drive detected on IDE channel 1