Re: Is this the right place for bugs / questions about PilOS?

[Alexander Burger]

On Sat, Apr 23, 2016 at 02:55:47AM +0200, Danilo Kordic wrote:
> 0.0 It is alive!  Acer AOD270 (Intel Atom N2600).
>   `` PilOS 15.11.0

So Acer again! I wonder if any other BIOS (in addition to qemu's) will
work.

♪♫ Alex
-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: Is this the right place for bugs / questions about PilOS?

[Danilo Kordic]

0.0 It is alive!  Acer AOD270 (Intel Atom N2600).
  `` PilOS 15.11.0
 Heap: 1010MiB
 :
   ''

I downloaded pios.tgz a few minutes ago, or so it feels ;) .  Just `dd'ed
x86-64.img.

Re: Is this the right place for bugs / questions about PilOS?

[cat stevens]

Robert,

The link  you
gave is, interestingly, quite helpful. (That's the non-404 version, because
things got moved around, it seems.)
I was ambivalent about using an emulator inside Wine (since I use Linux,
and don't have much access to Windows), but trying to compile the sources
for that version, and all surrounding versions, was met with linker errors
only *after* 99% of the object files were generated.

Compilation issues aside, the Windows exe does in fact run inside Wine and
PilOS does in fact run inside that, so thank you for that. :D

I'll still have to see if I can pick up an old-ish cheap-ish Acer
somewhere, if that's what I gotta do to run a modern Lisp on bare-metal.

~cat

On Fri, Apr 15, 2016 at 8:12 PM, Robert Herman  wrote:

> Cat,
>
> Try an older version of qemu. If it works, you can try newer ones if they
> have features or bugs corrected that may affect you.
>
> I had the same problem, but thanks to Joe Bogner and Alex, I have it
> running. Here's the link to the older qemu that worked:
>
> http://qemu.weilnetz.de/w64/qemu-w64-setup-20140715.exe
>
> I was running it on Win 8 64-bit at the time.
>
>
> Regards,
>
> Rob
>
>
>
> On 16 April 2016 at 02:46, cat stevens  wrote:
>
>> > This is an error from the BIOS (Was this also Qemu?).
>>
>> Yes, that was Qemu. Here's a screenshot .
>>
>> It comes after the "Loading PilOS" text, and I found the string constant
>> "READ ERROR 00" in the image binary (at 0xBF), so I thought that was
>> PilOS.
>>
>> I also recompiled using the provided source / instructions on the Wiki,
>> and
>> tried booting the resulting "x86_64.bin" in Qemu and bare metal with the
>> same results.
>>
>> > Most of today's BIOSes seem to implement only the absolute minimum,
>> > which is understandable as modern OSes don't call the BIOS so much any
>> > more.
>>
>> My PC's BIOS is the same (un-updated) one it shipped with, but the trouble
>> with BIOSes is that it's unlikely to find two identical confiugurations on
>> any two systems. :)
>>
>> > This is a pity, and I don't know what to recommend. But at least
>> > Qemu I would have expected to work ...
>>
>> I was kinda looking forward to having a Lisp OS on bare metal, but maybe
>> this is why there aren't that many. :P
>> I'm all ears if you've any suggestions, and I'll definitely keep an eye on
>> development.
>>
>> ~ cat
>>
>> On Fri, Apr 15, 2016 at 12:57 PM, Alexander Burger 
>> wrote:
>>
>> > On Fri, Apr 15, 2016 at 12:08:56PM -0400, cat stevens wrote:
>> > > Hi! I am very interested in the idea and look of PilOS; however, I'm
>> > having
>> > > some issues trying to get started with it. Can I ask about those here?
>> >
>> > Sure! :)
>> >
>> >
>> > > First, the command on the Wiki seems to have an issue, which I asked
>> > about
>> > > here
>> > > <
>> >
>> http://unix.stackexchange.com/questions/276480/booting-a-raw-disk-image-in-qemu
>> > >
>> > > -- it seems like it should be:
>> > >
>> > > qemu-system-x86_64 -drive format=raw,file=x86-64.img
>> >
>> > What I used for Qemu was
>> >
>> >$ qemu-system-x86_64  -m 4096  -smp 4  -ctrl-grab  -no-reboot
>> > pilos/x86-64.img
>> >
>> > so it is similar to what you wrote in the above link, and it worked fine
>> > for me.
>> >
>> >
>> >
>> > > Even when I run that (apparently more correct) command, PilOS gives
>> "READ
>> > > ERROR 09" and hangs.
>> >
>> > This is an error from the BIOS (Was this also Qemu?).
>> >
>> >
>> > > I also tried booting my laptop from the raw disk image written to a
>> USB
>>
>
>

Re: Is this the right place for bugs / questions about PilOS?

[Alexander Burger]

On Fri, Apr 15, 2016 at 03:46:06PM -0400, cat stevens wrote:
> > This is an error from the BIOS (Was this also Qemu?).
> 
> Yes, that was Qemu. Here's a screenshot .
> 
> It comes after the "Loading PilOS" text, and I found the string constant
> "READ ERROR 00" in the image binary (at 0xBF), so I thought that was PilOS.

Correct. PilOS prints this message after the $0x42 BIOS call (Extended
Read Sectors) returned an error (Carry bit set).


> I was kinda looking forward to having a Lisp OS on bare metal, but maybe
> this is why there aren't that many. :P

Until now we know that it works on

   - Acer TavelMate P-253E (mine)
   - Acer Aspire One 722 (Mattias Sundblad)

Perhaps you can try to find one of these second-hand?

♪♫ Alex
-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: Is this the right place for bugs / questions about PilOS?

[Robert Herman]

Cat,

Try an older version of qemu. If it works, you can try newer ones if they
have features or bugs corrected that may affect you.

I had the same problem, but thanks to Joe Bogner and Alex, I have it
running. Here's the link to the older qemu that worked:

http://qemu.weilnetz.de/w64/qemu-w64-setup-20140715.exe

I was running it on Win 8 64-bit at the time.


Regards,

Rob



On 16 April 2016 at 02:46, cat stevens  wrote:

> > This is an error from the BIOS (Was this also Qemu?).
>
> Yes, that was Qemu. Here's a screenshot .
>
> It comes after the "Loading PilOS" text, and I found the string constant
> "READ ERROR 00" in the image binary (at 0xBF), so I thought that was PilOS.
>
> I also recompiled using the provided source / instructions on the Wiki, and
> tried booting the resulting "x86_64.bin" in Qemu and bare metal with the
> same results.
>
> > Most of today's BIOSes seem to implement only the absolute minimum,
> > which is understandable as modern OSes don't call the BIOS so much any
> > more.
>
> My PC's BIOS is the same (un-updated) one it shipped with, but the trouble
> with BIOSes is that it's unlikely to find two identical confiugurations on
> any two systems. :)
>
> > This is a pity, and I don't know what to recommend. But at least
> > Qemu I would have expected to work ...
>
> I was kinda looking forward to having a Lisp OS on bare metal, but maybe
> this is why there aren't that many. :P
> I'm all ears if you've any suggestions, and I'll definitely keep an eye on
> development.
>
> ~ cat
>
> On Fri, Apr 15, 2016 at 12:57 PM, Alexander Burger 
> wrote:
>
> > On Fri, Apr 15, 2016 at 12:08:56PM -0400, cat stevens wrote:
> > > Hi! I am very interested in the idea and look of PilOS; however, I'm
> > having
> > > some issues trying to get started with it. Can I ask about those here?
> >
> > Sure! :)
> >
> >
> > > First, the command on the Wiki seems to have an issue, which I asked
> > about
> > > here
> > > <
> >
> http://unix.stackexchange.com/questions/276480/booting-a-raw-disk-image-in-qemu
> > >
> > > -- it seems like it should be:
> > >
> > > qemu-system-x86_64 -drive format=raw,file=x86-64.img
> >
> > What I used for Qemu was
> >
> >$ qemu-system-x86_64  -m 4096  -smp 4  -ctrl-grab  -no-reboot
> > pilos/x86-64.img
> >
> > so it is similar to what you wrote in the above link, and it worked fine
> > for me.
> >
> >
> >
> > > Even when I run that (apparently more correct) command, PilOS gives
> "READ
> > > ERROR 09" and hangs.
> >
> > This is an error from the BIOS (Was this also Qemu?).
> >
> >
> > > I also tried booting my laptop from the raw disk image written to a USB
>

Re: Is this the right place for bugs / questions about PilOS?

[cat stevens]

> This is an error from the BIOS (Was this also Qemu?).

Yes, that was Qemu. Here's a screenshot .

It comes after the "Loading PilOS" text, and I found the string constant
"READ ERROR 00" in the image binary (at 0xBF), so I thought that was PilOS.

I also recompiled using the provided source / instructions on the Wiki, and
tried booting the resulting "x86_64.bin" in Qemu and bare metal with the
same results.

> Most of today's BIOSes seem to implement only the absolute minimum,
> which is understandable as modern OSes don't call the BIOS so much any
> more.

My PC's BIOS is the same (un-updated) one it shipped with, but the trouble
with BIOSes is that it's unlikely to find two identical confiugurations on
any two systems. :)

> This is a pity, and I don't know what to recommend. But at least
> Qemu I would have expected to work ...

I was kinda looking forward to having a Lisp OS on bare metal, but maybe
this is why there aren't that many. :P
I'm all ears if you've any suggestions, and I'll definitely keep an eye on
development.

~ cat

On Fri, Apr 15, 2016 at 12:57 PM, Alexander Burger 
wrote:

> On Fri, Apr 15, 2016 at 12:08:56PM -0400, cat stevens wrote:
> > Hi! I am very interested in the idea and look of PilOS; however, I'm
> having
> > some issues trying to get started with it. Can I ask about those here?
>
> Sure! :)
>
>
> > First, the command on the Wiki seems to have an issue, which I asked
> about
> > here
> > <
> http://unix.stackexchange.com/questions/276480/booting-a-raw-disk-image-in-qemu
> >
> > -- it seems like it should be:
> >
> > qemu-system-x86_64 -drive format=raw,file=x86-64.img
>
> What I used for Qemu was
>
>$ qemu-system-x86_64  -m 4096  -smp 4  -ctrl-grab  -no-reboot
> pilos/x86-64.img
>
> so it is similar to what you wrote in the above link, and it worked fine
> for me.
>
>
>
> > Even when I run that (apparently more correct) command, PilOS gives "READ
> > ERROR 09" and hangs.
>
> This is an error from the BIOS (Was this also Qemu?).
>
>
> > I also tried booting my laptop from the raw disk image written to a USB

Re: Is this the right place for bugs / questions about PilOS?

[Alexander Burger]

On Fri, Apr 15, 2016 at 12:08:56PM -0400, cat stevens wrote:
> Hi! I am very interested in the idea and look of PilOS; however, I'm having
> some issues trying to get started with it. Can I ask about those here?

Sure! :)


> First, the command on the Wiki seems to have an issue, which I asked about
> here
> 
> -- it seems like it should be:
> 
> qemu-system-x86_64 -drive format=raw,file=x86-64.img

What I used for Qemu was

   $ qemu-system-x86_64  -m 4096  -smp 4  -ctrl-grab  -no-reboot  
pilos/x86-64.img

so it is similar to what you wrote in the above link, and it worked fine
for me.



> Even when I run that (apparently more correct) command, PilOS gives "READ
> ERROR 09" and hangs.

This is an error from the BIOS (Was this also Qemu?).


> I also tried booting my laptop from the raw disk image written to a USB. It
> said "Loading PilOS", then printed "Checking for long support..." and hung,
> not continuing for the time I let it sit at that screen (about 20 minutes).
> 
> My laptop is a Toshiba Satellite from 2012, it's 64-bit, has lots of ram
> and has inbuilt SSE 4.2 support, so I don't think it's my hardware.
> 
> Could anyone offer some pointers here? Thanks!

It seems I was lucky with my Acer Travelmate. All BIOS calls worked as
documented. But from the feedback I received meanwhile I get the
impression that this is rather the exception than the rule.

Most of today's BIOSes seem to implement only the absolute minimum,
which is understandable as modern OSes don't call the BIOS so much any
more.

This is a pity, and I don't know what to recommend. But at least
Qemu I would have expected to work ...

♪♫ Alex
-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Is this the right place for bugs / questions about PilOS?

[cat stevens]

Hi! I am very interested in the idea and look of PilOS; however, I'm having
some issues trying to get started with it. Can I ask about those here?

First, the command on the Wiki seems to have an issue, which I asked about
here

-- it seems like it should be:

qemu-system-x86_64 -drive format=raw,file=x86-64.img

Even when I run that (apparently more correct) command, PilOS gives "READ
ERROR 09" and hangs.

I also tried booting my laptop from the raw disk image written to a USB. It
said "Loading PilOS", then printed "Checking for long support..." and hung,
not continuing for the time I let it sit at that screen (about 20 minutes).

My laptop is a Toshiba Satellite from 2012, it's 64-bit, has lots of ram
and has inbuilt SSE 4.2 support, so I don't think it's my hardware.

Could anyone offer some pointers here? Thanks!