Date: Wed, 14 May 2003 17:02:16 +0200 From: "Thomas Weber" <thomas@youngarts.org> To: <freebsd-questions@freebsd.org> Subject: Re: loader(8) not loading ?!? -> top not working Message-ID: <061501c31a29$d056b2f0$0400a8c0@NEUROMANCER> References: <04af01c318c7$88071570$0400a8c0@NEUROMANCER> <20030513000533.GA962@gothmog.gr>
next in thread | previous in thread | raw e-mail | index | archive | help
things got worse :( Somehow i was playing with the boot-process and found something about /boot.config in the handbook and tried to modify it for loading /boot/loader. So i added the line "/boot/loader" to /boot.config. Now the Server does more or less nothing. :((( I have only SSH-Access to the machine and now i cant even ping it. There's a friend of mine who has no idea about unix, but physical access to the server. Is there any simple way i can tell hin to boot up the server without paying attention to /boot.config? @ Giorgos: Definetly don't have rebuild the kernel, it's a fresh installed 4.8 system (only made a cvsup and portupgrade on some ports). top wasn't working even at the first boot. I don't know what failed at the installation :( ----- Original Message ----- From: "Giorgos Keramidas" <keramida@ceid.upatras.gr> To: "Thomas Weber" <thomas@youngarts.org> Cc: <freebsd-questions@freebsd.org> Sent: Tuesday, May 13, 2003 2:05 AM Subject: Re: loader(8) not loading ?!? -> top not working > On 2003-05-12 22:46, Thomas Weber <thomas@youngarts.org> wrote: > > Hi, > > > > yesterday i installed a new server with FreeBSD4.8-RELEASE. Unfortunately > > now top doesn't work, when i call it i get the error "top: nlist failed". > > I saw in the handbook, that this is happening if /boot/loader is not used > > for booting, "but doing it directily from boot2". > > Actually it's the FAQ[1] that describes this in the "Troubleshooting" > section. But this is not the whole story. Not booting through > loader(8) is one of the two things listed there: > > : 5.22. Why do I get the error ``nlist failed'' when running, for > : example, top or systat? > : > : The problem is that the application you are trying to run is looking > : for a specific kernel symbol, but, for whatever reason, cannot find > : it; this error stems from one of two problems: > : > : * Your kernel and userland are not synchronized (i.e., you built a > : new kernel but did not do an installworld, or vice versa), and > : thus the symbol table is different from what the user > : application thinks it is. If this is the case, simply complete > : the upgrade process (see /usr/src/UPDATING for the correct > : sequence). > : > : * You are not using /boot/loader to load your kernel, but doing it > : directly from boot2 (see boot(8)). While there is nothing wrong > : with bypassing /boot/loader, it generally does a better job of > : making the kernel symbols available to user applications. > > Have you by any chance rebuilt & installed your kernel only lately? > > > Uhm....... how can i change to loader(8)? > > That depends on what this computer has installed, but in general you can > install the BootEasy loader using: > > # boot0cfg -v ad0 > > =============== > WORD OF CAUTION > =============== > > If you're running Windows NT, 2000 or XP I'm not sure if this is a good > idea. These OSes tend to be rather picky and insist on using their > special "loader". *ALWAYS* make sure you take backups of your MBR > before installing a new boot loader. > > - Giorgos >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?061501c31a29$d056b2f0$0400a8c0>