From: "J. Mayer" <l_indien@magic.fr>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Open Hack'Ware 0.4-pre2
Date: Mon, 14 Mar 2005 15:35:11 +0100 [thread overview]
Message-ID: <1110810911.28694.32.camel@rapid> (raw)
Open Hack'Ware 0.4-pre2 is available for tests here:
<http://perso.magic.fr/l_indien/OpenHackWare/0.4-pre2/OpenHackWare-0.4-pre2_bin.tar.bz2>
<http://perso.magic.fr/l_indien/OpenHackWare/0.4-pre2/OpenHackWare-0.4-pre2_svn.tar.bz2>
It includes all fixes that went into 0.4-pre1, of course. A lot of new
images have been tested and OHW is now able at least to start booting
most of them.
Please consult the README file for more details:
<http://perso.magic.fr/l_indien/OpenHackWare/0.4-pre2/README>
The main known issues are:
- PREP boot is broken (regression)
- kernel boot in memory is broken (regression, at least for PREP).
Those two points will be fixed for 0.4 release.
- Linux 2.6 frame-buffer is buggy. Some of the symptoms are known to
appear on real Macs, some other will have to be fixed.
- Linux 2.6 seem to have some problems with some parts of the hardware
emulation (at least IDE & ADB: seem to be qemu issues)
- NE2k emulation in qemu seems incomplete: most installer will fail if
trying to autoconfigure the network when no dhcp server is found (then,
using tun networking): installers all want to probe ethernet link but
MII seem not to answer properly.
For now, only Debian Sarge and Gentoo are known to be installable.
Please note that top in Debian Sarge is buggy when using recent kernels
(even 2.4) and would crash after 2 refreshes. This seems to be a known
issue due to /proc/stat format changes. This does not happen with Gentoo
distribution.
Please report any other issue / success.
--
J. Mayer <l_indien@magic.fr>
Never organized
next reply other threads:[~2005-03-14 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-14 14:35 J. Mayer [this message]
2005-03-14 16:39 ` [Qemu-devel] Open Hack'Ware 0.4-pre2 Asko Kauppi
2005-03-14 21:51 ` J. Mayer
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=1110810911.28694.32.camel@rapid \
--to=l_indien@magic.fr \
--cc=qemu-devel@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).