Re: Some problems and questions...
Some update information:
BF version is 3.0.22.
The problem may be that I'm stuck with a fairly old (1 month) CD set. I'm
making boot/root floppies and then taking the kernel and drivers off the
CD. It isn't clear how this interaction might break things...
Just to make sure, I'll be doing an install this afternoon using matching
root, boot, and driver disks and see if I get the same problems.
I'm also ordering a new first CD to see if that helps...
As to the "Neighbour Table Overflow" error, I've seen it since Potato on
several 486 and Pentium machines, both SCSI and IDE. The kernel comes from
the boot floppies found in the 1.44 directory (boot, root, and drivers).
If not there, then they are the kernel provided by the first CD. (I think
these two are the same...)
On my own machines, I build a custom kernel with just the drivers I need,
and I never see this error. My suspicion is that I must build a custom
boot kernel for replacement on the floppy to avoid this, but maybe I can
get rid of it by using a different boot kernel from the archives...
I'm also looking for some other hardware to test this on, so I should have
some better answers this evening.
On 14 Apr 2002, Adam Di Carlo wrote:
> Eduard Bloch <firstname.lastname@example.org> writes:
> > #include <hallo.h>
> > Adam Di Carlo wrote on Sat Apr 13, 2002 um 06:58:50PM:
> > > > B. After installing the drivers from CD, there is an informational
> > > > message indicating that drivers may already be loaded.
> > >
> > > No idea what that's about. Seems like it should be filed as a bug.
> > No. This is for all that dudes that complained about not beeing able to
> > find the driver for their network card, while the driver has been
> > already loaded in the kernel.
> Oh, I see, ok, good.
> > > That seems absolutely crippling to me, e.g., a Serious or higher
> > > boot-floppies bug. Does this happen on any particular flavor for
> > > i386? all flavors?
> > Which version of boot-floppies has been used? There was a buggy modconf
> > version, but it the current one should be okay. Do you have enough RAM,
> > did you make a swap partition?
> > > > Now, A isn't much of a problem, just confusing for new users, unless no
> > > > modules are actuall being loaded because of this. On the other hand, B is
> > > > simply confusing. C is a problem for my screen shot collection, but will
> > > > only impact those installs needing CD drivers, etc...
> > Tell more details. Modconf has to work.
> FYI, the other detail I realized is that he's running within bochs...
> Might be a bochs vs whiptail console thing...
> > > > 2. After the reboot, following the base install, I get a lot of screen
> > > > shots messed up because the kernel likes to throw "Neighbour Table
> > > > Overflow" error messages all over the screen.
> > This bug have also been fixed in one of the previous boot-floppies
> > releases.
> > > Well, I haven't even seen this. Are you using per chance the bf2.4
> > > flavor? This should be filed as a bug against the kernel-image-*
> > > package which is relevant.
> > Most likely because of missing lo-Interface configuration, which was not
> > saved by debootstrap in some situations in bfs << 3.0.20 or so.
> Dale, were you using 3.0.22? I thought you said you were... maybe we
> have some bugs we thought were fixed but which are not...
> ...Adam Di Carlo..<email@example.com>...<URL:http://www.onshored.com/>
_-_-_-_-_- Author of "Dwarf's Guide to Debian GNU/Linux" _-_-_-_-_-_-
_- aka Dale Scheetz Phone: 1 (850) 656-9769 _-
_- Flexible Software 11000 McCrackin Road _-
_- e-mail: firstname.lastname@example.org Tallahassee, FL 32308 _-
_-_-_-_-_- Released under the GNU Free Documentation License _-_-_-_-
available at: http://www.polaris.net/~dwarf/
To UNSUBSCRIBE, email to email@example.com
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org