From owner-freebsd-hackers Sat Nov 21 23:20:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA11275 for freebsd-hackers-outgoing; Sat, 21 Nov 1998 23:20:53 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles211.castles.com [208.214.165.211]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA11270 for ; Sat, 21 Nov 1998 23:20:50 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id XAA09602 for ; Sat, 21 Nov 1998 23:19:11 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811220719.XAA09602@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-hackers@FreeBSD.ORG Subject: Re: Changing the load address of the kernel? In-reply-to: Your message of "Fri, 20 Nov 1998 12:19:30 +0100." <199811201119.MAA23190@dorifer.heim3.tu-clausthal.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 21 Nov 1998 23:19:11 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > After posting this to freebsd-questions I realized that it's > probably much better suited for -hackers. I'm sorry for the > double posting. > > I'm trying to change the load address of the kernel, but > without success. The default seems to be f0100000 (causing the > bootloader to load it at 00100000). I tried to change it to > f0400000. I changed the load address in two files: > > /sys/i386/conf/Makefile.i386 (one line) > /sys/kern/link_aout.c (two lines) > > The bootloader (I'm using rawboot from a floppy) correctly > loads the kernel to 00400000, but it hangs right after that. > Did I miss anything? > > Any help would be greatly appreciated. Changing the kernel load address will require a great amount of effort. There are almost certainly hardcoded copies of the value scattered around. > BTW, I'm using a 3.0-19981103-SNAP with ELF userland and aout > kernel. I searched the mailing list archives on this topic, > but without success. > > Background of the problem: I'm trying to boot a diskless > computer with a network boot ROM by LanWorks > (www.lanworks.com). They require to make a bootable floppy > first, then put an image of that floppy on a tftp server. > The ROM loads that image, makes a RAM disk from it and boots > it. The problem is: That RAM disks seems to overlap with the > kernel at 00100000. There doesn't seem to be a way to change > the location of the RAM disk. That's ugly. 8( > BTW, I also tried to contact InCom (www.incom.de) for boot > ROMs, but they're completely unresponsive. The demo version > that they offer is from 1995 and doesn't seem to support any > PCI FastEthernet cards. :-( That's why it's the demo version. Their product is actually pretty good, although yes, they're not what you'd call super-responsive. If you're trying to boot with an EtherExpress Pro/100, note that erich@freebsd.org has a modified netboot that works with these cards. I've asked him to commit the changes (I think), but I haven't heard from him since. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message