Hi,
I am having two problems with LinuxBIOS.
1. I have an ATI 3D Rage Pro onboard video rom. I have got the vgabios rom for it. I cat it with linuxbios.rom and produce the final linuxbios image. During execution, after entering the x86 emulator, there is a message saying -
halt_sys:/home/rohit/LinuxBIOSv2/src/devices/emulator/x86emu/ops.c line 2136
but the execution of LinuxBIOS continues and nothing is seen on the monitor. Whats the problem?
2. I am using FILO in Etherboot to boot linux already stored in a SATA disk. But I am getting the following message -
No Drive detected on IDE Channel 2
What could be the problem?
Please reply ASAP.
Regards,
Rohit.
* ROHIT VENKATACHALAM rohitvenkat@sify.com [060912 16:14]:
- I have an ATI
3D Rage Pro onboard video rom. I have got the vgabios rom for it. I cat it with linuxbios.rom and produce the final linuxbios image. During execution, after entering the x86 emulator, there is a message saying
halt_sys:/home/rohit/LinuxBIOSv2/src/devices/emulator/x86emu/ops.c line 2136
This message just means the rom has been executed and the emulator execution ended normally.
but the execution of LinuxBIOS continues and nothing is seen on the monitor. Whats the problem?
- what board are you using?
- Is there any other output? Can you send the complete log, please?
- Can you please enable debug output for the emulator?
- I am using FILO in
Etherboot to boot linux already stored in a SATA disk. But I am getting the following message -
No Drive detected on IDE Channel 2
- SATA drives are recognized first in the chain. Try hda instead of hde.
- Are you using an nvidia chipset? SATA does not work on those.
Stefan
On Thu, Sep 14, 2006 at 01:32:20PM +0200, Stefan Reinauer wrote:
- I am using FILO in
Etherboot to boot linux already stored in a SATA disk. But I am getting the following message -
No Drive detected on IDE Channel 2
- SATA drives are recognized first in the chain. Try hda instead of hde.
For what it's worth; I had the exact same problem yesterday, and it turned out that the sata drives were plugged in to ports 3 and 4 instead of 1 and 2; FILO (0.5) did not seem to like that very much, it simply didn't see the drives.
Thanks, Ward.