Re: PilOS Boot Issues
On Mon, Jun 29, 2015 at 08:02:06PM +0200, Alexander Burger wrote: > It seems that virtualbox doesn't support BIOS 0x13 interrupts for > "Extended Read Sectors" calls. > > > > It still freezes on the black screen Loading PilOS > > We guessed that from the fact that this message appears, but not the > following "Checking long mode". And, for Virtual PC, we get a "READ ERROR 01" which means "Invalid command" (https://en.wikipedia.org/wiki/INT_13). Same. ♪♫ Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: PilOS Boot Issues
Hi Joe, > The new version boots fine on qemu under windows 7 x64. Under > virtualbox on the same platform, get stuck with a black screen that > says Loading PilOS with nothing else displayed For the mailing list: We discussed this in IRC just now. It seems that virtualbox doesn't support BIOS 0x13 interrupts for "Extended Read Sectors" calls. > It still freezes on the black screen Loading PilOS We guessed that from the fact that this message appears, but not the following "Checking long mode". ♪♫ Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: PilOS Boot Issues
Hi Alex,
The new version boots fine on qemu under windows 7 x64. Under
virtualbox on the same platform, get stuck with a black screen that
says Loading PilOS with nothing else displayed
This is how I converted the image
"c:\Program Files\qemu\qemu-img.exe" convert -O vmdk x86-64.img x86-64.vmdk
The symptoms are the same when I use vboxmanage to convert:
c:\Program Files\Oracle\VirtualBox\VBoxManage.exe convertfromraw
x86-64.img x86-64_vbox.vmdk --format VMDK
Converting from raw image file="x86-64.img" to file="x86-64_vbox.vmdk"..
Creating dynamic image with size 684032 bytes (1MB)...
It still freezes on the black screen Loading PilOS
On Mon, Jun 29, 2015 at 9:55 AM, Alexander Burger wrote:
> Hi all,
>
> it seems that there are still problems with booting PilOS.
>
> While it works for me (on Qemu and on my Acer notebook), it hear that on
> other emulators or hardware people just see a black screen. So I would
> be glad to find out the reason(s).
>
>
> One reason might be that the image is not recognized as a hard disk:
>
>
> http://reboot.pro/topic/7512-fool-the-bios-booting-any-usb-stick-as-a-hard-disk
>
> So I followed the suggestions there, and changed the partition table to
> two dummy-partitions instead of one. Also, I set one System ID to
> "Linux" ("83", instead of the arbitrary "22" before), and the other to
> "Linux swap" (ID "82"). I don't know if this helps though.
>
>
> Also, I added a few diagnostic messages, to see how far it gets.
>
> So anybody daring to try it is welcome! As before, PilOS can be
> downloaded from
>
>http://software-lab.de/pilos.tgz
>
> and put on an USB-Stick, e.g. on /dev/sdb
>
>$ sudo dd if=x86-64.img of=/dev/sdb
>
> Then try to boot (only on x86-64 (Amd64) hardware, of course).
>
> ♪♫ Alex
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
PilOS Boot Issues
Hi all,
it seems that there are still problems with booting PilOS.
While it works for me (on Qemu and on my Acer notebook), it hear that on
other emulators or hardware people just see a black screen. So I would
be glad to find out the reason(s).
One reason might be that the image is not recognized as a hard disk:
http://reboot.pro/topic/7512-fool-the-bios-booting-any-usb-stick-as-a-hard-disk
So I followed the suggestions there, and changed the partition table to
two dummy-partitions instead of one. Also, I set one System ID to
"Linux" ("83", instead of the arbitrary "22" before), and the other to
"Linux swap" (ID "82"). I don't know if this helps though.
Also, I added a few diagnostic messages, to see how far it gets.
So anybody daring to try it is welcome! As before, PilOS can be
downloaded from
http://software-lab.de/pilos.tgz
and put on an USB-Stick, e.g. on /dev/sdb
$ sudo dd if=x86-64.img of=/dev/sdb
Then try to boot (only on x86-64 (Amd64) hardware, of course).
♪♫ Alex
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
