minix3 seems not to run on bochs? using minix3 iso
xzgfree...@sina.com
I don't know why ?
here is a snapshot which is captured when I start it from bochs :
cs ds text data bss stack
0001000 0007000 24176 3384 44384 0 kernel
0100000 0106000 21296 3108 93940 1024 pm
011e000 0129000 41536 5224 5019704 2048 fs
05f5000 05f7000 6848 840 20388 16384 rs
0601000 0602000 3280 464 1808 16384 ds
0607000 060e000 27072 5696 48104 1024 tty
061c000 061e000 6144 287784 3068 8192 memory
0668000 066a000 5968 572 63280 4096 log
067b000 067d000 7056 2412 1356 768 init
MINIX 3.1.2a. Copyright 2006, Vrije Universiteit, Amsterdam, The
Netherlands
Executing in 32-bit protected mode.
Building process table: pm fs rs ds tty mem log init.
Physical memory: total 32288 KB, system 5700 KB, free 26588 KB.
Looking for boot CD. This may take a minute.
Please ignore any error messages.
bad super block on /dev/c0d0p1 or CDROM: read block 2048 failed
No CD found
"bad super block on /dev/c0dop1 ": what is mean?
and I have verified its correctness of .iso file ,because the problem
don't turn up when I
install it in the VMWARE WORKSTATION .
the content of the bochs's boot configure file bochsrc.txt as
follows:
romimage: file=$BXSHARE\BIOS-bochs-latest, address=0xf0000
cpu: count=1, ips=10000000
megs: 32
vgaromimage: file=$BXSHARE\VGABIOS-lgpl-latest
vga: extension=vbe
ata0: enabled=1, ioaddr1=0x1f0, ioaddr2=0x3f0, irq=14
ata1: enabled=1, ioaddr1=0x170, ioaddr2=0x370, irq=15
ata2: enabled=0, ioaddr1=0x1e8, ioaddr2=0x3e0, irq=11
ata3: enabled=0, ioaddr1=0x168, ioaddr2=0x360, irq=9
ata0-slave: type=cdrom, path=J:, status=inserted or ata0-master:
type=cdrom, path=J:, cylinders=306, heads=4, spt=17
(attention:path=J; where J is my virtual driver or cdrom)
boot: cdrom
clock: sync=none, time0=local
log: bochsout.txt
panic: action=ask
error: action=report
info: action=report
debug: action=ignore
vga_update_interval: 300000
keyboard_serial_delay: 250
keyboard_paste_delay: 100000
mouse: enabled=0
keyboard_type: mf
end ,that is all for configure file
here is my setup file start.bat which is a batch file with suffix name
.bat as follows:
cd "C:\Program Files\Bochs-2.2.6\minix"
..\bochs.exe -q -f bochsrc.txt
attention:where "C:\Program Files\Bochs-2.2.6 " is the install
directoty of bochs
and I make a new directory minix ,and then I place two files onto minix
directory which are
bochsrc.txt and start.bat ,respectively.
when I double click the start.bat file ,it can start bochs software.
above is all problem which I have encountered ,and what I have done for
it.
can you make a solution to it ?(why it can't start up from cdrom,and
how I can configure my file )
my email:xzgfree...@hotmail.com
thanks!
FMorales
I unfortunately had the same problem, and frustrated by a night of
searching & nothing working, i decided to switch to Qemu. Now i'll note
this disclaimer, i'm not implying either is better than the other, Qemu
just happened to work correctly the first time, and has been very
pleasent to use. (Note: A HUGE plus for me w/ Qemu is the fact i didn't
have to build a cryptic config file) I'm not sure if you /can/ switch to
Qemu, if so this is what i did to get it going:
I downloaded the ISO & placed it in a special directory. Then i used the
command:
qemu-img create minix3.img 1024M
(NOTE: For some reason it doesn't like its G, for gigabyte, suffix very
much, so i just used that for a 1GB image (i didn't want to run out of
space while i played w/ Minix))
Then to install to your new minix image:
qemu -boot d -cdrom "IDE-3.1.2a.iso" -hda "minix3.img" -m 64 -localtime
Now there are a lot of options i'll let you read the help for those, but
these are your basic ones to get it going. For the '-boot' parameter,
'a' is floppy, 'c' is harddrive, 'd' is cdrom (for which device to boot
first).
The next 2 should be self explanatory, the '-m' parameter is how much
memory you want to use, and '-localtime' uses your host OS' time in
minix. Follow the regular on screen instructions to install. Once that's
complete, what i did was issued a 'shutdown' command, followed by 'off'
at the boot monitor, so i could start from the new image & verify it
worked. Now to boot the new image, simply use:
qemu -boot c -cdrom "IDE-3.1.2a.iso" -hda "minix3.img" -m 64 -localtime
(Notice the '-boot' option now specifies my "harddrive" as the first
boot device) I leave the ISO on there for the CD-ROM because once you're
back in Minix, you can issue the 'packman' command & it'll install all
your fancy helper utilities.
And that should be it, it's what i've used /several/ times, and it's
worked w/o problem. As i said you may not be able to switch, but if you
can i'd highly recommend it. I use Qemu on both my Windows XP & FreeBSD
computers, it's very easy to use, seems very efficient, etc...
Happy Minix'ing,
FMorales...
(Note: For networking, i chose option '4' for my network card. Once all
that was done & i was booted up, i issued the 'shutdown' command to get
to the boot monitor. There you need to type: qemu_pci = 1 , then you
can type: save , to save that 'variable' for later use. Then just type
'boot' to boot the default image. I know i had A LOT of grief trying to
get networking to work, and it was just that simple. Hope it helps)
FMorales
One thing i forgot to mention, on Windows, Qemu requires this command
line option:
-L "\Program Files\Qemu\bios"
It doesn't on FreeBSD (and perhaps Linux). That will be the source of a
large number headaches, if you don't put it in there.
FMorales...
Alex
Bochs, together with networking. The description might contain some
bugs, but overall it was working for me. I'll try to re-check the
how-to in a few days.
It's in the Minix wikibook - http://en.wikibooks.org/wiki/MINIX - go to
the lower link.