Re: Booting PilOS
Hi Geo, Yes! i was able build the image and immediately tried it using my USB stick, it's working!!! but I'm stuck at Checking long mode.. maybe because I'm trying it under an Intel i3? Thanks! That's interesting! i3 is a 64-bit CPU, right? So the check for long mode doesn't work? I would at least expect an error message. The checks are done in pilos/x86-64/beg.l starting from line 32. If the checks were successful, it should next print Initializing memory. Otherwise, we should see ERROR: CPU does not support long mode or ERROR: CPU has no local APIC. Normally, all those messages are not visible, because the boot is so fast that they are overwritten quickly. ♪♫ Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Booting PilOS
Hi Alex, That's interesting! i3 is a 64-bit CPU, right? So the check for long mode doesn't work? I would at least expect an error message. Yes it is also a 64-bit, just now i also got the same result here at my room's PC which is an AMD64, how is the checking done btw? The checks are done in pilos/x86-64/beg.l starting from line 32. If the checks were successful, it should next print Initializing memory. Otherwise, we should see ERROR: CPU does not support long mode or ERROR: CPU has no local APIC. OK did a quick peek and most of them are in x86 assembly hmmm Normally, all those messages are not visible, because the boot is so fast that they are overwritten quickly. ... No, it all goes in a tiny fraction of a second. Normally, you don't see any of the messages. I see, so it means it got stuck somewhere on the checking, would it be possible to be inside an infinite loop? hmm if only there is a WDT... is it possible to have a debug mode for PilOS that it will not overwrite the messages? Like it will just do a newline per message like we did with pilMCU emulator version? Might be useful during polishing pilOS to able to boot in all different x86-64 hardware.. I think other people also tried VirtualBox, and said it doesn't work. It doesn't even load the remaining sectors from the drive. This is done via BIOS interrupt 0x13: https://en.wikipedia.org/wiki/INT_13#INT_13h_AH.3D42h:_Extended_Read_Sectors_From_Drive I think VirtualBox doesn't support this interrupt call. I see, ok noted. But still this can be reworked right? Coz it would be nice to have it boot in all cases as long as its x86-64 machine, correct? Alex, you already got the following results, I'm just reposting them to the list as well. I have tried PilOS on the following machines: Hi Mattias, thanks for sharing your list! It looks like the current pilOS is tailored for Acer hardware's hmmm might make sense coz Alex developed it on his Acer laptop as well... BR,Geo On Wednesday, July 8, 2015 6:57 PM, Mattias Sundblad mattias@gmail.com wrote: Hi George and Alex, Yes! i was able build the image and immediately tried it using my USB stick, it's working!!! but I'm stuck at Checking long mode.. maybe because I'm trying it under an Intel i3? Let me try it with my AMD machine back in my room and feedback to you how it goes... this is great!! I ran into the same message when trying to boot PilOS on an Asus UL30A, this machine has a core2duo cpu. Alex, you already got the following results, I'm just reposting them to the list as well. I have tried PilOS on the following machines: *Acer Aspire One 722, AMD C-60 cpu Everything works fine on this machine. *Lenovo Thinkpad x201i, i3 cpu Fails with the message READ ERROR 08 *Lenovo Thinkpad x230, i5 cpu Fails with the message READ ERROR 01 *and finally the Asus UL30A, Core2Duo cpu Does not get past the message Checking long mode Best regards, Mattias -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Booting PilOS
Hi Geo, OK did a quick peek and most of them are in x86 assembly hmmm Yeah. Basically calls to the 'cpuid' instruction to question the CPU for its parameters. I see, so it means it got stuck somewhere on the checking, would it be possible to be inside an infinite loop? I believe that the 'cpuid' instruction cannot loop or crash. Rather, I suspect that for some reason the following messages are not printed because the CPU got into an unknown state. it possible to have a debug mode for PilOS that it will not overwrite the messages? Yes. What I did usually during development is inserting more 'print' messages, similar to mov $LongMsg, %si call print and and/or stopped the CPU with jmp stop so that the blue VGA screen of PilOS doesn't overwrite the boot screen. Even easier is, if you re-use some existing message, e.g. Loading PilOS (which is in 'LoadMsg') and then jump directly to 'bootError' which will output the message and stop the CPU. So if you insert mov $LoadMsg, %si jmp bootError after e.g. the first 'cpuid' call, and you see Loading PilOS appearing a second time, you are sure that the boot got this far. The problem is that this is a bit tedious (unless using e.g. qemu) because you have to put the test onto the USB-stick each time and reboot the test machine with it. This is done via BIOS interrupt 0x13: https://en.wikipedia.org/wiki/INT_13#INT_13h_AH.3D42h:_Extended_Read_Sectors_From_Drive I think VirtualBox doesn't support this interrupt call. I see, ok noted. But still this can be reworked right? Hmm, perhaps, but I don't know how. Because we *need* to read the sectors from the stick, don't we? Perhaps there is another way to format the boot partitions and/or use another BIOS call. I just don't know about it. Also, it would be good to know if VirtualBox *really* doesn't support this BIOS call, or if there is some other reason why it fails. ♪♫ Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Unsubscribe
Unsubscribe
Re: Booting PilOS
Hi Mattias + Geo, Alex, you already got the following results, I'm just reposting them to the list as well. Yes, thanks! I have tried PilOS on the following machines: ... *Lenovo Thinkpad x201i, i3 cpu Fails with the message READ ERROR 08 *Lenovo Thinkpad x230, i5 cpu Fails with the message READ ERROR 01 Also, for public info: The READ ERROR nn error codes are supposed to mean: http://www.bioscentral.com/misc/biosint13.htm So 08 should be DMA overrun (floppy), and 01 Invalid command. The latter is what I would expect if the BIOS doesn't support the Extended Read Sectors call. ♪♫ Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Booting PilOS
Hi George and Alex, Yes! i was able build the image and immediately tried it using my USB stick, it's working!!! but I'm stuck at Checking long mode.. maybe because I'm trying it under an Intel i3? Let me try it with my AMD machine back in my room and feedback to you how it goes... this is great!! I ran into the same message when trying to boot PilOS on an Asus UL30A, this machine has a core2duo cpu. Alex, you already got the following results, I'm just reposting them to the list as well. I have tried PilOS on the following machines: *Acer Aspire One 722, AMD C-60 cpu Everything works fine on this machine. *Lenovo Thinkpad x201i, i3 cpu Fails with the message READ ERROR 08 *Lenovo Thinkpad x230, i5 cpu Fails with the message READ ERROR 01 *and finally the Asus UL30A, Core2Duo cpu Does not get past the message Checking long mode Best regards, Mattias -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Booting PilOS
Hi Alex, Oops, sorry. My fault! init/.pil/history was added recently, and I forgot to include it into the release script. Please download once more pilos.tgz. Yes! i was able build the image and immediately tried it using my USB stick, it's working!!! but I'm stuck at Checking long mode.. maybe because I'm trying it under an Intel i3? Let me try it with my AMD machine back in my room and feedback to you how it goes... this is great!! I think that currently there is no special dependency on AMD, though I used only the AMD CPU manuals. OK noted, and yes i agree with that.. but lets keep an eye on this.. BR,Geo On Wednesday, July 8, 2015 1:56 PM, Alexander Burger abu@software-labde wrote: Hi Geo, thanks for the feedback! :) I tried building them and here is what i get: * First release: make will generate x86-64.bin* Latest release: make: *** No rule to make target `init/.pil/history', needed by `db.bin'. Oops, sorry. My fault! init/.pil/history was added recently, and I forgot to include it into the release script. Please download once more pilos.tgz. I used pil 3.1.11.1 That's perfect. ♪♫ Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Booting PilOS
Hi Alex, Another feedback is i try to boot it on my VirtualBox and I'm seeing Loading PilOS but its already a while, is this expected? BR,Geo On Wednesday, July 8, 2015 4:41 PM, George Orais gpor...@yahoo.com wrote: Hi Alex, Oops, sorry. My fault! init/.pil/history was added recently, and I forgot to include it into the release script. Please download once more pilos.tgz. Yes! i was able build the image and immediately tried it using my USB stick, it's working!!! but I'm stuck at Checking long mode.. maybe because I'm trying it under an Intel i3? Let me try it with my AMD machine back in my room and feedback to you how it goes... this is great!! I think that currently there is no special dependency on AMD, though I used only the AMD CPU manuals. OK noted, and yes i agree with that.. but lets keep an eye on this.. BR,Geo On Wednesday, July 8, 2015 1:56 PM, Alexander Burger abu@software-labde wrote: Hi Geo, thanks for the feedback! :) I tried building them and here is what i get: * First release: make will generate x86-64.bin* Latest release: make: *** No rule to make target `init/.pil/history', needed by `db.bin'. Oops, sorry. My fault! init/.pil/history was added recently, and I forgot to include it into the release script. Please download once more pilos.tgz. I used pil 3.1.11.1 That's perfect. ♪♫ Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Booting PilOS
Hi Geo, Another feedback is i try to boot it on my VirtualBox and I'm seeing Loading PilOS but its already a while, is this expected? No, it all goes in a tiny fraction of a second. Normally, you don't see any of the messages. I think other people also tried VirtualBox, and said it doesn't work. It doesn't even load the remaining sectors from the drive. This is done via BIOS interrupt 0x13: https://en.wikipedia.org/wiki/INT_13#INT_13h_AH.3D42h:_Extended_Read_Sectors_From_Drive I think VirtualBox doesn't support this interrupt call. ♪♫ Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
