Maybe my kernel will work

[Net Llama!]

On Mon, 30 Dec 2002, Bonez wrote:
> I figured out how to write to the drive. I guess when I updated /etc/fstab
> before, I hadn't booted my system down to a level  to get it to reread the
> changes. I am sure there is a way to accomplish this, to 'source it' or
> something. Please enlighten me if this is an option.

mount -a
re-reads everything in fstab and mounts everything that should be mounted
at bootup.

> > I'd be quite surprised if anything worked on that kernel.  Its a blackhole
> > of bugs & instabilities, and i donit' know that it ever had much in the
> > way of decent USB functionality.
>
> Oh, such confidence. Now I'll worry myself silly until I get it updated. Yes
> I was working on upgrading to the 2.4.20 kernel with XFS enabled. Here's what
> I have tried in the past and where i am with that project.
>
> I run Win4Lin to enable one persistent app for which I find no suitable linux
> analogue, yet. I have followed instructions from Netraverse on patching the
> 2.4.20 kernel source files, and then compiling and trying to run that. I
> succeed in getting 2.4.20 to boot up and run, and it does run Win4Lin when
> it's booted up. However, my NIC, sound and some other things all fail upon
> boot, despite the new kernel using similar settings. I assume that during the
> make/make install process it looks at the settings of my current working

THe kernel configuration is not anywhere that intelligent.  It doesn't
look at anything, other than what you instruct it to look at.  Thus,
if you just went with the defaults, then you're getting a kernel which is
in no way shape or form optimizaed for your system.  There have been many
many changes to the kernel (configuration) since 2.4.2.  You'll need to go
through all the options and make sure that you're selecting sane choices.
I'm surprised that you even have a bootable kernel with the defaults,
since some of them are fairly way off the mark.

> I downloaded a fresh archive of 2.4.20 from kernel.org and ran all the
> patching that I needed and that worked before, rendering NO FAILED HUNK
> notices. When I run the XFS patch file, there are many many failed hunk
> messages. This is what baffles me. I think I need to work the bugs out and
> get 2.4.20 working without including the XFS support first, resolving the
> failure of various modules and other items to load at boot time. Then I can
> compile in the XFS functions and move to that point.

Its quite possible & likely that the patch for the Win4Lin stuff is
conflicting with the patch for XFS.  Or you're just not patching XFS
correctly.

> I welcome any assistance and am very very grateful for the list here, and
> being able to share my experience and learn from you all. If you need me to
> post .log files or want to point me to the files I need to examine to find
> out where the new kernel breaks when loading, please point the way.

SHow us the command(s) you issued, and the resulting output.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Lonni J Friedman				netllama at linux-sxs.org
Linux Step-by-step & TyGeMo		     http://netllama.ipfox.com