qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Will Senn <will.senn@gmail.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	qemu-discuss@nongnu.org, qemu-devel <qemu-devel@nongnu.org>
Cc: "Hervé Poussineau" <hpoussin@reactos.org>,
	"John Snow" <jsnow@redhat.com>
Subject: Re: Minix 1.1 with QEMU
Date: Wed, 23 Sep 2020 12:00:01 -0500	[thread overview]
Message-ID: <6ab2235a-519b-2079-34eb-2dfe3b774fe4@gmail.com> (raw)
In-Reply-To: <edc82d55-e5d1-abba-9a8e-7954b1dbe66e@amsat.org>

[-- Attachment #1: Type: text/plain, Size: 3055 bytes --]

On 9/23/20 11:53 AM, Philippe Mathieu-Daudé wrote:
> Hi Will,
>
> On 9/23/20 6:45 PM, Will Senn wrote:
>> Long time user, first time poster :)
>>
>> So, I'd like to be able to run Minix 1.1 on my Macbook Pro mid-2012
>> w/16gb RAM (MacOS 10.14.6 Mojave). Qemu will run pretty ancient OS'es
>> such as DOS 2.0, which I use all of the time. However, I'm having some
>> difficulty getting Minix to run. I am able to boot the first floppy, but
>> when I change to the second floppy, the system freezes and I can't tell
>> what is going on. Here's what I did to get this far:
>>
>> brew install qemu
>>
>> qemu-system-i386 --version
>> QEMU emulator version 5.1.0
>>
>> mkdir ~/workspaces/retro-workspace/minix-1.1
>> cd ~/workspaces/retro-workspace/minix-1.1
>> aria2c
>> http://download.minix3.org/previous-versions/bzipped/Intel-1.1.tar.bz2
>> tar xvjf Intel-1.1.tar.bz2
>> cp Intel-1.1/floppy_disk1 ./Disk01.img
>> cp Intel-1.1/floppy_disk2 ./Disk02.img
>> cp Intel-1.1/floppy_disk3 ./Disk03.img
>> cp Intel-1.1/floppy_disk4 ./Disk04.img
>>
>>
>> qemu-system-i386 -drive
>> file=Disk01.img,format=raw,if=floppy,media=disk,readonly=off,index=0,snapshot=on
>> \
>>    -boot a \
>>    -no-fd-bootchk \
>>    -monitor telnet::2222,server,nowait -serial mon:stdio
>>
>> Qemu boots to the Minix 1.1 Boot screen and says to swap to floppy 2, so
>> in the monitor:
>> change floppy0 Disk02.img raw
>>
>> I press l (el) and it scans the disk, lists the files on the disk and
>> reports no errors, but when I press =, it does a carriage return and
>> just sits there. I'm pretty sure this is the Minix going bye bye and not
>> necessarily QEMU, but I'm wondering if there is a way to see what QEMU
>> thinks it is doing or if it is what's hung? Usually, at this point,
>> Minix reads the disk contents into a Ramdisk and boots Minix.
>>
>> Food for thought... Minix expects to run on an IBM PC (5150), IBM PC XT
>> (5160), or compatible, and therefore the I/O is written for whatever
>> floppy controller was extant at that time (I'm guessing here), so if
>> that's different than modern day floppies, I suppose this could cause
>> the problem I'm experiencing here. Is there a way to see the floppy
>> controller activity in QEMU? Similarly, I gather it expects a CGA
>> compatible monitor (EGA/VGA, etc should be fine).
> Can you try adding '-machine isapc', which is closer to the 5150?
>
>> I appreciate your help on this.
>>
>> Minix 1.1 works 'ok' in 86Box and other IBM PC emulations, so I know the
>> floppies are fine.
>>
>> Thanks!
>>
>> Will
>>
>>
>>
>> -- 
>> GPG Fingerprint: 68F4 B3BD 1730 555A 4462  7D45 3EAA 5B6D A982 BAAF
>>
Phillipe,

My new incantation is:

qemu-system-i386 -machine isapc -drive 
file=Disk01.img,format=raw,if=floppy,media=disk,readonly=off,index=0,snapshot=on 
-boot a   -no-fd-bootchk   -monitor telnet::2222,server,nowait -serial 
mon:stdio

with the same outcome :(. Thanks for the suggestion, I'll keep it in 
mind for other projects.

Will

-- 
GPG Fingerprint: 68F4 B3BD 1730 555A 4462  7D45 3EAA 5B6D A982 BAAF


[-- Attachment #2: Type: text/html, Size: 3973 bytes --]

  reply	other threads:[~2020-09-23 17:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5e534cc7-2a99-baa5-fc8f-63d0d8e85c97@gmail.com>
2020-09-23 16:53 ` Minix 1.1 with QEMU Philippe Mathieu-Daudé
2020-09-23 17:00   ` Will Senn [this message]
2020-09-25 17:27     ` John Snow

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6ab2235a-519b-2079-34eb-2dfe3b774fe4@gmail.com \
    --to=will.senn@gmail.com \
    --cc=f4bug@amsat.org \
    --cc=hpoussin@reactos.org \
    --cc=jsnow@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-discuss@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).