home *** CD-ROM | disk | FTP | other *** search
- > First: vmunix.335 works fine for me, but I have been unable to get
-
- vmunix.335 is *evil*! Don't *ever* use any rsd* or rst* devices on it, or
- you'll trash all over...
-
- > vmunix.366 to work at all. After it loads and prints the available
- > memory on the AmigaDOS window, it blanks the screen to white (OK),
- > and remains that way forever (not OK). Any ideas?
-
- The screen should never ever blank white.. Hmmmmm
-
- (noticed config bugs) config will probably change considerably soon, we got
- some new nice config code :-)
-
- > But there _is_ one slight problem _after_ compiling: the generated
- > vmunix doesn't work (for me anyway). It does precisely the same
- > thing
- > as vmunix.366, though I'm building from the .335 sources (actually
- > .317 plus the stuff in "changes-366"). Again, any ideas?
-
- Weird.. Well, I've never seen something like that, perhaps it would be
- a good idea to insert some serspit('a') to serspit('z') into the sources
- along the way it takes while booting, and watching on a serial console how
- far it gets, and WHERE it's causing this white screen. You need a serial
- terminal for this though.
-
- > The vmunix compiled under BSD is about 2K shorter than either
- > vmunix.335 or vmunix.366 (Markus's Amiga-compiled versions); I assume
- > this is because BSD is using GCC 2.4.3 while I guess Markus used
- > GCC 2.3.3 on the Amiga. Are there known bugs in 2.4.3 that might
- > be breaking the kernel?
-
- None that I'd know of.. I'm recompiling 2.4.5 right now, we'll see..
-
- -Markus
- --
- CHUUG/EUnet Switzerland Markus Wild
- Zweierstrasse 35 Tel: +41 1 291 45 80 mw@eunet.ch
- CH-8004 Zuerich Fax: +41 1 291 46 42 S=mw;P=EUnet;A=EUnet;C=CH
-
-