In preparation for an official new release later this year, there's a
snapshot of the current subversion trunk with binary packages up on
the website at http://www.minix3.org/download/ .
I wouldn't go so far as to call this an interim release, as there are
quite a few known rough edges, but in order to give the rest of the
code some much-needed exposure, everyone who's interested is invited
to try and run it.
GSOC students, both while applying and while working, are expected to
run this release, or a newer version if available.
The SHA1 is 114839e1a8d9af39184fc5e25fc5958970d0952e.
some rough edges that are known are are being worked on that come to
mind are
. slower; due to vm implementation, this is still to be optimized
. no AHCI support; need to change to IDE mode in BIOS on new
hardware
. on new hardware, DMA sometimes doesn't work (at_wini panics); set
'ata_no_dma=1' in boot monitor
On the plus side, it should work out-of-the-box with vmware and qemu
(and presumably bochs). And other major (no more chmem hassle; no more
unnecessarily large X server) and minor improvements.
Please share your experience with us in the group, if you find a new
bug a bug can be filed in the bug tracker.
You can expect more of these snapshots in the near future, and until
the next official release.
Ben Gras wrote: > On the plus side, it should work out-of-the-box with vmware and qemu > (and presumably bochs). And other major (no more chmem hassle; no more > unnecessarily large X server) and minor improvements.
Just to follow on, VMWare's lance driver should work out of the box now. No need to fiddle around with Lance hacks. You will still need to modify the vmx file or change your VMWare hardware compatibility level, depending on your VMWare version. We're looking into this issue.
The booting issues with QEMU 0.9 should be gone. QEMU 0.10 works fine also; it never had the problem. If you're using QEMU or KVM, don't forget to set qemu_pci=1 in the boot monitor.
We'll have to investigate the VirtualBox Lance problems further. If you're a VBox user, you can try to restart the Lance driver (as Matthias Schmidt mentioned). It may work, but maybe not.
> Please share your experience with us in the group, if you find a new > bug a bug can be filed in the bug tracker.
> You can expect more of these snapshots in the near future, and until > the next official release.
> Enjoy!
Hi,
Today i installed Minix 3.1.4 and now i am trying to compile /usr/src/lib with "make all-gnu". Probably something is broken here 'cause gcc fails to compile /usr/src/lib/sysutil/profile.c with a lot of errors like this one:
profile.c:253 error: request for member '_' in something not a structure or union.
It should be a little problem with the u64_t type definition....
Using Qemu 0.9 on windows and I managed to get 3.1.4 installed but I
can't seem to get the lance driver to work, is there any notification
as to if its working once you enter qemu_pci=1? Once it starts the
networking process it just reports "nonamed" so I'm not sure if that
means its not working or if I did everything I was suppose to do.
So far no errors besides that user error, :)
On Mar 26, 1:55 pm, Ben Gras <b...@few.vu.nl> wrote:
> In preparation for an official new release later this year, there's a
> snapshot of the current subversion trunk with binary packages up on
> the website athttp://www.minix3.org/download/.
> I wouldn't go so far as to call this an interim release, as there are
> quite a few known rough edges, but in order to give the rest of the
> code some much-needed exposure, everyone who's interested is invited
> to try and run it.
> GSOC students, both while applying and while working, are expected to
> run this release, or a newer version if available.
> The SHA1 is 114839e1a8d9af39184fc5e25fc5958970d0952e.
> some rough edges that are known are are being worked on that come to
> mind are
> . slower; due to vm implementation, this is still to be optimized
> . no AHCI support; need to change to IDE mode in BIOS on new
> hardware
> . on new hardware, DMA sometimes doesn't work (at_wini panics); set
> 'ata_no_dma=1' in boot monitor
> On the plus side, it should work out-of-the-box with vmware and qemu
> (and presumably bochs). And other major (no more chmem hassle; no more
> unnecessarily large X server) and minor improvements.
> Please share your experience with us in the group, if you find a new
> bug a bug can be filed in the bug tracker.
> You can expect more of these snapshots in the near future, and until
> the next official release.
> Today i installed Minix 3.1.4 and now i am trying to compile > /usr/src/lib with "make all-gnu". > Probably something is broken here 'cause gcc fails to compile > /usr/src/lib/sysutil/profile.c with a lot of errors like this one:
> profile.c:253 error: request for member '_' in something not a > structure or union.
> It should be a little problem with the u64_t type definition....
Hi, with this patch it *should* works... or at least you will understand where the problem is:
*** profile.c Sat Mar 28 08:25:37 2009 --- new_profile.c Sat Mar 28 09:01:56 2009 *************** *** 64,70 **** if (cprof_locked) return; else cprof_locked = 1;
/* Read CPU cycle count into local variable. */ ! read_tsc(&start._[U64_HI], &start._[U64_LO]);
/* Run init code once after system boot. */ if (init == 0) { --- 64,71 ---- if (cprof_locked) return; else cprof_locked = 1;
/* Read CPU cycle count into local variable. */ ! read_tsc(&hi, &lo); ! start = make64(lo, hi);
/* Run init code once after system boot. */ if (init == 0) { *************** *** 108,115 **** }
/* Save initial cycle count on stack. */ ! cprof_stk[cprof_stk_top].start_1._[U64_HI] = start._[U64_HI]; ! cprof_stk[cprof_stk_top].start_1._[U64_LO] = start._[U64_LO];
/* Check available call path len. */ if (cpath_len + strlen(name) + 1 > CPROF_CPATH_MAX_LEN) { --- 109,115 ---- }
/* Save initial cycle count on stack. */ ! cprof_stk[cprof_stk_top].start_1 = start;
/* Again save CPU cycle count on stack. */ ! read_tsc(&cprof_stk[cprof_stk_top].start_2._[U64_HI], ! &cprof_stk[cprof_stk_top].start_2._[U64_LO]); cprof_locked = 0; }
On Mar 28, 1:42 am, Midnitte <midni...@gmail.com> wrote:
> Using Qemu 0.9 on windows and I managed to get 3.1.4 installed but I
> can't seem to get the lance driver to work, is there any notification
> as to if its working once you enter qemu_pci=1? Once it starts the
> networking process it just reports "nonamed" so I'm not sure if that
> means its not working or if I did everything I was suppose to do.
"nonamed" is actually your domain name resolver, it's supposed to
start as part of the network stack.
However, AFAIK Qemu does not emulate a Lance network card by default
but a Realtek card. Why did you pick Lance?
> Probably there is a bug in the floppy disk driver:
> When i try to do "mtools format /dev/fd0:" i get this error:
> fd0: disk interrupt timed out
> fs: I/O error on device 2/0
> It is not an hardware problem, it works on Minix 3.1.3 r3066
> I will file this bug in the bug tracker.
Ehmm, I can't reproduce this - reading and writing from and to the
block device works on my system, so does 'format -v /dev/fd0'. Is
there anything more you can tell me?
> Today i installed Minix 3.1.4 and now i am trying to compile
> /usr/src/lib with "make all-gnu".
> Probably something is broken here 'cause gcc fails to compile
> /usr/src/lib/sysutil/profile.c with a lot of errors like this one:
> profile.c:253 error: request for member '_' in something not a
> structure or union.
> It should be a little problem with the u64_t type definition....
True. Thanks for the report.. that was a fix to make ports a bit
easier. A fix is on its way. Thanks for the report!
>> Today i installed Minix 3.1.4 and now i am trying to compile >> /usr/src/lib with "make all-gnu". >> Probably something is broken here 'cause gcc fails to compile >> /usr/src/lib/sysutil/profile.c with a lot of errors like this one:
>> profile.c:253 error: request for member '_' in something not a >> structure or union.
>> It should be a little problem with the u64_t type definition....
> True. Thanks for the report.. that was a fix to make ports a bit > easier. A fix is on its way. Thanks for the report!
Should be fixed in HEAD now. Thanks for the bug report.
> Ehmm, I can't reproduce this - reading and writing from and to the > block device works on my system, so does 'format -v /dev/fd0'. Is > there anything more you can tell me?
Hi Ben,
'format -v /dev/fd0 1440' doesn't work for me, it fails with the same error. I will try to debug the floppy driver and i will tell you something more, ok?
however, i found two new problems:
1) "make hdboot" fails because of errors in framework/audio_fw.c
DEV_READ undefined DEV_WRITE undefined ..... unknown selector REP_PROC_NR illegal use of selector REP_PROC_NR
and so on....
2) I did a clean reinstall of Minix 3.1.4 and a terrible system panic (hard reboot) occurred, you can reproduce the problem (i hope) with the following sequence:
- Reinstall Minix 3.1.4 - Choose the "R" option (Reinstall Option, leave /home untouched) - Install all packages (packman 'all')
System panic occours when packman will try to "Update GCC Libraries"
Everything work fine if you choose the "F" option (Full Reinstall Option)
> 2) I did a clean reinstall of Minix 3.1.4 and a terrible system panic
> (hard reboot) occurred,
> you can reproduce the problem (i hope) with the following sequence:
Ahh as David suggested (IRL), it's probably due to installing all
packages - audio installs some sources files there. as audio is merged
with the base system, that package is obsolete and I've thrown it out,
which should fix this.
> >> Today i installed Minix 3.1.4 and now i am trying to compile
> >> /usr/src/lib with "make all-gnu".
> >> Probably something is broken here 'cause gcc fails to compile
> >> /usr/src/lib/sysutil/profile.c with a lot of errors like this one:
> >> profile.c:253 error: request for member '_' in something not a
> >> structure or union.
> >> It should be a little problem with the u64_t type definition....
> > True. Thanks for the report.. that was a fix to make ports a bit
> > easier. A fix is on its way. Thanks for the report!
> Should be fixed in HEAD now. Thanks for the bug report.
On Wed, Apr 1, 2009 at 5:18 PM, Edward Kaplan <t...@shlashdot.org> wrote:
> I've tried updating my /usr/src/lib to svn trunk, but the same error > occurs when building profile.c. Is the fix somewhere else?
The fix modified headers in /usr/src/include. If I understand you correctly, you updated /usr/src/lib only? If so, try updating all of /usr/src. Do a 'make clean' (just in case). Then, follow the instructions here: http://www.minix3.org/tracking-current.html.
There's a new snapshot up on the download page, of subversion revision
4220. A few quirks are fixed (randomness entropy, compiling system
libraries with gcc). Give it a shot, I'll take down the older snapshot
if nobody complains about this one.
I installed the 4220 version (all packages) in VMware running on RHEL
5. Seems to have gone OK though the GCC library update required > 60
minutes to complete with one of the cores pegged at 52% the entire
time; this is on an Intel Core 2 3 Ghz machine.
Also, the installer did not check the disk for bad sectors, it did do
this in previous versions.
Kudos for getting the NIC working properly under VMware without the
need to fiddle with it. ;-)
Hmm - actually upon further use I've realized that GCC did not install
properly and will not install.
The librarys are installed with the make install all-gnu, however the
GCC binary is not actually compiled by any method, packman, the easy
updater or by manuall compile.
Unfortunately I don't have the time to devote to tracing the cause.
>> Probably there is a bug in the floppy disk driver:
>> When i try to do "mtools format /dev/fd0:" i get this error:
>> fd0: disk interrupt timed out >> fs: I/O error on device 2/0
>> It is not an hardware problem, it works on Minix 3.1.3 r3066 >> I will file this bug in the bug tracker.
> Ehmm, I can't reproduce this - reading and writing from and to the > block device works on my system, so does 'format -v /dev/fd0'. Is > there anything more you can tell me?
Hi,
i'm trying to find this bug that prevent me to use the floppy drive.
However i need a little help: Should i look for the bug only inside floppy.c or there is some other component that can be involved in this behaviour?
-- -------------------- Maurizio Lombardi OpenSolaris 2008.11 on x86_64 --------------------