Date: Sun, 7 Feb 1999 15:13:43 -0600 From: Chris Costello <chris@holly.dyndns.org> To: "Wayne M. Barnes" <wayne@barnes1.wustl.edu> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: syscons.o crashes kernel build Message-ID: <19990207151343.O11699@holly.dyndns.org> In-Reply-To: <199902072118.PAA11559@barnes1.wustl.edu>; from Wayne M. Barnes on Sun, Feb 07, 1999 at 03:18:45PM -0600 References: <199902072118.PAA11559@barnes1.wustl.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Feb 7, 1999, Wayne M. Barnes put this into my mailbox: > Dear FreeBSD stabilizers, > > Starting from 2.2.8, I have been trying to get to 3.0-stable. Which is fairly dangerous. > > Using /stand/sysinstall, I 'upgraded' to the smallest 3.0 > system to get the binaries. > I downloaded the port-current and unpacked them. > I cd'd to /usr/ports/net/cvsup to make all install. > The cvsup install kindly noticed that my X11R6 was out > of date, and updated it to 3.3.3; this was something I needed. > I did a cvsup with cvs tag=RELENG_3 > ( I also tried =. with the same result below) > I performed a 'make world' which seemed to finish okay. > > [ This is not my main trouble report, but when I rebooted, I > could not log in, as all my passwords were rejected. Readonly > inspection of /etc/master.passwd revealed no visible problems. > /stand/sysinstall would not let me set the root password unless > I performed a minimal binary install again. This I did, > and I had to delete my users from master.passwd and adduser them > again. Luckily, there weren't too many yet, and now I can > reboot and log in. ] > > NOW THE TROUBLE STARTS > > When I try to build a new kernel, the build crashes with > references to syscons.o [ see APPENDIX below for screen dump ] > I notice that this is coincident with the first paragraph of > /usr/src/UPDATING, which says syscons is being reworked. > I did the recommended 'make clean', which did not help. > > MY QUESTIONS ARE: > > 1. Am I the only one who can't build a kernel without > these errors? No, many other people haven't read and followed all the instructions in the updating docs ;) > > 2. Is it possible to get a version without these errors? > Also, I would like to have a new enough version > of FreeBSD to have PCI device 'rl' supported. > > 3. Have I made some error or omission? Yes. Copy GENERIC to a new kernel and re-add your devices according to LINT or the updating documentation. Make sure you have the keyboard device installed! Then try cleaning out the old compile directory, config, and then try rebuilding your kernel. All should go well. > > Thank you for your attention, > > Wayne M. Barnes, Ph.D. wayne@barnes1.wustl.edu > Biochemistry Dept. 8231 > Washington Univ. Medical School 314.362.3351 fax 7183 > 660 South Euclid Ave., St. Louis, MO 63110 > http://barnes1.wustl.edu Just plain Taq is old tech anymore. > > --- APPENDIX --- > Partial screen dump: > syscons.o(.text+0x56c5): undefined reference to `kbdsw' > syscons.o: In function `update_kbd_state': > syscons.o(.text+0x5729): undefined reference to `kbdsw' > syscons.o(.text+0x5780): undefined reference to `kbdsw' > syscons.o: In function `update_kbd_leds': > syscons.o(.text+0x57ca): undefined reference to `kbdsw' > syscons.o: In function `set_mode': > syscons.o(.text+0x5805): undefined reference to `vidsw' > syscons.o(.text+0x583f): undefined reference to `vidsw' > syscons.o(.text+0x58ca): undefined reference to `vidsw' > syscons.o(.text+0x5927): undefined reference to `vidsw' > syscons.o: In function `set_border': > syscons.o(.text+0x5957): undefined reference to `vidsw' > syscons.o(.text+0x5a98): more undefined references to `vidsw' follow > *** Error code 1 > > Stop. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990207151343.O11699>