On Tue, 04 Jan 2000, Tom Draffen wrote about, upgrading kernel, and a myriad of
questions:
>
> I've gotten 2.2.13 to compile easy enough - these are my steps
>
> make oldconfig answering no to all of the questions that pop up for new
> items.. since I am not upgrading kernel for usability, just experience?
> Ok.. question here.. which old config does this use anyway?
I was not aware it would work, i checked and it seems to get its defaults
from files called Config.in in each of the sub directorys of the kernel
source, if there is a file called .config in /usr/src/linux that file will
be used.
As to exachtly how make oldconfig works on a "clean" source tree i dont
know, i will have to look further to find out, however i dont have a lot of
time at the minute.
> After that not working. I've moved over to make menuconfig and have
> hammered through my books for what everything means so I know what to pick.
Ah!, what you could have used was 'make config'
But i imagen the make dep and bzImage afterwards produces a file in
/usr/src/linux/arch/i386/boot/ called bzImage
However it certanly does not suit many systems as it is a "minimal"
configuration and would not contain all the drivers you would need.
>
> from there, I " make dep clean bzlilo modules modules_install " as
> per the references and off it goes to compiling.
>
> I am running a /boot partition as recommended by the Redhat folks, but this
> always puts the new System.map and vmlinuz in the / directory.. should i be
> concerned about this? When I finish I normally just cp those files over to
> /boot after backing up the old ones. now off to lilo.conf adding a section
> for the new kernel looking something like this
I dont quite know how you get the files in / you possably did not edit
/usr/src/linux/Makefile and changed
#INSTALL_PATH=/boot
to
INSTALL_PATH=/boot
Its always a good idea to use the EXTRAVERSION option as well in the
Makefile, you can then define a version as 2.2.13-1 or 2.2.13-mycompile
That saves you having to backup the old kernel image before cp'ing the new
image.
Another way is to use make install, that should copy the image to /boot
(thats redhat spesific "i think").
>
> image=/boot/vmlinuz-2.2.13
> root=/dev/hda6 <-- a copy from the original image setup
> read-only
> label=new /* also the old image setup has
> a line initrd=/initrd-2.2.12-20.img that is never made
> by the new
> compile.. what's the deal here?
You dont need it, its made as an extra by some distro's.
>
>
> ok.. write and quit..
> I've already moved everything to /boot at this stage.. and now.. type
> "lilo" adds linx *, new, and dos.. as expected
> and then a reboot
>
> best case scenario so far? the kernel loads, but I'm missing a few
> things. here's what i get from make oldconfig run through. These error
> messages occur on the way through boot
>
> /etc/rc.d/rc.sysinit : /proc/sys/kernel/sysrq No such file or directory
This i belive is a redhat fault in the start scripts, (dont qoute me on
that one).
>
> can't locate module sound
> can't locate module midi
> and delay load of eth0 and it fails the load of the card previously set up
> using tulip.
That is possably caused by not having any aliases for the modules in
/etc/modules.conf or conf.modules.
Firstly check in /usr/src/linux/.config and see if there is a =m or =y on
each of the needed and required/desired drivers or network protocols etc.
example
CONFIG_EEXPRESS_PRO100=y
Compiles a driver for the ethernet express network card in the kernel. =m
is as a module.
> Got a lot to learn, I know. trying to catch up and ya'll seem to be the
> most friendly so far, so. Any help? and lastly, I bought the book
> Unleashing Redhat Llinux 6 (course after I had already bought 6.1 :P) and
> it's pretty thorough, but almost too much so. I'm looking for some
> reasonably decent beginner books that aren't too kid like, but step through
> things nicely. Any suggestions from folks out there that have had luck with
> them? The how-tos are nice, and i have them referenced all the time. But
> just basically getting to know the operating system would like some good
> tutorial type information.
As to books i belive more in the documentation on each distro itself, its
free and has just as much info as many books.
Take a look at the archives for more info on your problems.
For more information check out the archives at;
http://www.geocrawler.com/lists/3/Linux/47/0
Use the search engine there to find a "Keyword"
Another good place for info;
http://www.linuxtopia.com
Keywords for you would be.
alias modules kerneld kmod insmod etc etc.
For each command you certanly would know about;
man modprobe for example...
>
> Thanks for your time and help
>
> Tom Draffen
> programmer, kinda, networker sorta, dad and husband all the time
--
Regards Richard
[EMAIL PROTECTED]
http://people.zeelandnet.nl/pa3gcu/
Happy New Year
