Hello;
Regier Avery J wrote:
> Last night, after a year of waiting for Linux to finally work with my
> hardware and other assorted challenges, I was finally able to get almost
> everything in the tool chain to compile! I had to make some changes in the
> mknbi-jos Makefile and mknbi.c to get mknbi to compile with Etherboot 4.2.?.
> I also found that a few things in the tool chain are undocumented. For
> instance, I had to get the blackdown JDK, but no where in the docs was that
I don't actually use either Kaffe or blackdown (I could never seem to get Kaffe
happy anything), but instead use the "guavac" Java compiler which comes with
RedHat 6.0.
> mentioned, and no mention of what version was required and/or known to work
> either. I ended up getting the latest (1.1.7v3) and it compiles, though I
> don't know about running yet. I am using newer version of Etherboot and
> nasm than the tested versions, so I don't know yet whether they will run or
> not (they do finally compile). I also discovered that bootp is no longer
> recommended or distributed with RedHat 6.0. I had to go back and find in in
Hmm... I am using stock RedHat 6.0, and bootp is there and works fine (I think
I had to enable it via either chkconfig or linuxconf).
> 5.2. I still don't know if this is going to work. According to the
> Etherboot documents, DHCP(?) is now recommended instead of bootp in RedHat
> 6. I don't know why this is the case, but we may need to consider upgrading
> our tool chain in order to keep current. I can't go back to RedHat 5.2
> because of the above mentioned hardware compatibility problems which were
> finally solved with RedHat 6. (RedHat 6, BTW, I have found to be far
> superior and much easier to use and work with than 5.2 was. I heartily
> recommend an upgrade if you are on 5.2.)
Like I said, I am using RedHat 6.0 with the existing toolchain. I'll be more
than happy to help you get this working. I do not think that there should be
any issue with respect to the version of NASM you're using -- we don't really do
anything, er, creative with it (I think there's only some 300 lines of asm). I
*do* know there *are* problems with pre-4.0 Etherboot (related to the maximum
workable size of the downloaded image, and, at 9MB, we're pretty much pushing
the envelope).
> Here are my outstanding problems:
> * The i386 build compiles, but the host build does not. It is complaining
> about missing a file: /etc/lib/gnu/types.h (or something like that, I dont'
> have it in front of me.) And lo and behold, the directory is there, but not
> the file. Am I missing an RPM? If so, which one might that be?
Ah. You probably need to remake the "dependencies" in the Makefile by building
the "depend" target. I seem to recall an issue concerning the exact format of
the "Don't delete this line, makedepend depends upon it" between Todd's
distribution and my RedHat one. We should probably separate out that into a
separate "included" part of the Makefile so as to make this easier.
> * I was able to build the floppy and I tried to boot JJOS over my home
> network, but for some reason it couldn't find my NIC. Was there maybe a
> configuration step that I could have been missing? What are the standard
> steps you need to go through to get that to work reliably I am reasonably
> sure I have the right driver (Tulip) for my NIC.
There is a configuration step in how you build the floppy -- you must also "dd"
onto the floppy the right NIC-specific driver (the directions that come with
Etherboot explain this). Please also be advised that somebody else (I forget
who) uses Netboot instead, which uses NDIS packet-drivers (which I understand
are easier to come by) instead of custom assembly drivers. Either should work
fine.
> * The above DHCP vs. bootp question.
I am using BOOTP. I do not know of anybody who has successfully used DHCP.
(Hell, I don't know anybody who even *tried*.)
> I'm looking forward to actually seeing this thing run and be able to
> contribute!
Great! Let me know what else I can do to help!
-jm
--
==== John Morrison ==== MaK Technologies, Inc.
==== Chief Technology Officer ==== 185 Alewife Brook Pkwy, Cambridge, MA 02138
==== [EMAIL PROTECTED] ==== http://www.mak.com/welcome.html
==== vox:617-876-8085 x115 ==== fax:617-876-9208
_______________________________________________
Kernel maillist - [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/kernel
