[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: OSKit-Mach boot failure




Thanks for your email Joachim. I figured one of the necessary steps after installing the OS was to build a kernel for it, primarily for the ata100 driver, but secondarily for kernel building experience.

I've looked around and I can't figure out where development is being done on the hurd. I'm guessing by your use of 'the old OSKit-Mach' that this is no longer the development branch being used for the hurd u-kernel?

Is the main development branch for the hurd u-kernel l4 now? The reason I ask is that I saw a note on the L4-hurd page http://www.gnu.org/non-gnu/l4hurd/ that stated "this project is dead and the information here is outdated. Check out savannah.gnu.org....".

I don't want to start down the path of debugging this if the development is being done elsewhere, as I will have to setup a remote debugging session on a machine which isn't x86. (And I'm not sure this will work properly because of the different architectures.)

Chris

On Sat, 5 Feb 2005, Joachim Nilsson wrote:

Chris Gorman wrote:
First off, I'm not sure this is the correct venue for this topic, so if I should post to help-hurd, hurd-devel or some other list, please let me know.

I think we used bug-hurd for the old OSKit-Mach discussions, oh well...

I've built OSKit-Mach and have attempted to install it on my machine which is an AMD K7 with a VIA VT82C586B main board. My main reason for this is that with the default kernel, I am unable to see my second onboard ide controller, which is a Promise PDC202xx, with the default kernel. During my searches it appeared to me that Joachim Nilsson had worked on a patch for ATA100 support, and I hoped that by it's absense on his hurd page, http://hurd.gnufans.org/bin/view/Hurd/JoachimNilssonHurdPage that it was now in cvs.

I should update that page and note that the ATA100 work has been abandoned
due to lack of time.  The ATA100 work never made it into CVS, it was too
unstable for that - all I ever got it to was detecting the controller,
so it wasn't too useful.

The state of ATA100 in Linux-2.2, which was what I used, wasn't altogether
that good either.  So the resulting port to OSKit was quite hard.  OSKit
lacks a lot of "features" that are available in Linux native so some stuff
must be redone quite extensively to squeeze it in.

I'm hoping that the L4 guys will provide a better driver framework in their
userspace driver server, or whatever it will be labeled.

Unfortunatly oskit-mach does not load for me at all. My initial build included no debug suppport, so I don't have much info on this other than the console output.
Welcome to GNU Mach 1.91!
Kernel page fault at address 0x1, eip = 0x1
Kernel Page fault trap, eip 0x1
kernel trap, type 14, code = 0
Dump of trap_state at 0x002aafb8:
EAX 0000dfdf EBX 00117930 ECX 00000007 EDX 00000000
ESI 00000000 EDI 00000000 EBP 218f6fd8 ESP 002aaffc
EIP 00000001 EFLAGS 00010002
CS 0010 SS 0028 DS 0028 ES 0028 FS 0000 GS 0000
trapno 14, error 00000000, from kernel mode
page fault linear address c0000001
c0000001 00000001 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
trap
Backtrace: fp=2aaf48
 0022f049 0013e013 001412cb
_exit(1) called; rebooting...
If anyone has any ideas or pointers please let me know.

Terribly sorry Chris, but that's one of the reasons I stopped working with
the OSKit port of Mach.  All I can say is that back when I actually made
it work I had an older oskit-mach tree than CVS, gcc-2.95 and a PII that I
used for "cross" compiling.  That doesn't help you at all, but should at
least give you a hint as to the sheer amount of possible faults that could
be causing this.

Regards
/Jocke

--
Joachim Nilsson :: <joachim AT vmlinux DOT org>
+46(0)21-123348 :: <http://vmlinux.org/joachim/>


--
To UNSUBSCRIBE, email to debian-hurd-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org






Reply to: