"Brian N. Borg" <[EMAIL PROTECTED]> writes:

> I have a working 2.1.31 kernel that I compiled.  Some of the modules, 
> such as vfat and serial, load ok but scsi_mod has missing symbols 
> that prevent my aic7xxx from loading.
> 
> --Brian.
> 
> 
> Hamish Moffatt wrote:
> > 
> > Anyone having much luck with 2.1.3x?
> > I'm running 2.1.29 and it's fine, except that the nfs module doesn't insert.
> > But no luck with 2.1.33 or 2.1.35; both have lots of missing symbols
> > on all the hardware drivers, probably relating to PNP support.
> > 
> > I just ftpd the whole 2.1.35 source and the new modutils 2.1.34
> > and will see how it goes, I have been patching up.
> > 
> > Anyone else having this? Nobody in the linux.dev.kernel group
> > (or the mailing list) seem to have mentioned it.
> > 
> > Hamish

I just compiled a fresh 2.1.35 kernel for my home machine (IDE-based).
When I try to boot this kernel, either from the IDE disk or from a
floppy disk, I get the messages about uncompressing the kernel, then
"now booting the kernel", then nothing.  Well, actually not nothing.
There is a whole lot of disk activity on the IDE disk at this point,
even when booting off the floppy.  When I eventually halt this and
reboot an old kernel, it has to fsck my disk partitions because they
look dirty.

So I don't even get as far as finding out that there are missing symbols.

We were able to compile and boot a 2.1.35 kernel for my office machine
but that has / on a SCSI disk.  We do have an old IDE drive in there
as well and this morning the driver for that got jammed to the point
that we had to reboot.

It appears that the 2.1.3x series of kernels are indeed development
versions.  I think I will stay with the 2.0.3x series for a while.

-- 
Douglas Bates                            [EMAIL PROTECTED]
Statistics Department                    608/262-2598
University of Wisconsin - Madison        http://www.stat.wisc.edu/~bates/


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Reply via email to