On Saturday 16 March 2002 01:30, you wrote:
Hi, all you have to do is recompile the kernel.
cd /usr/src/linux make cloneconfig make xconfig or make menuconfig do you changes recompile
Got "recompile command not found". What do I do? Cheers, Brian
On Sat, Mar 16, 2002 at 11:06:26PM +0700, durant@cbn.net.id wrote:
On Saturday 16 March 2002 01:30, you wrote:
Hi, all you have to do is recompile the kernel.
cd /usr/src/linux make cloneconfig make xconfig or make menuconfig do you changes recompile
Got "recompile command not found". What do I do?
ROFL! 'recompile' isn't a command. It's the next step that you have to do. Try: make clean make dep make bzlilo then make modules make modules_install. I would recommend reading the Kernel-HOWTO, in particular: http://www.linuxdoc.org/HOWTO/Kernel-HOWTO-5.html HTH... -- David Smith Work Email: Dave.Smith@st.com STMicroelectronics Home Email: David.Smith@ds-electronics.co.uk Bristol, England
On Saturday 16 March 2002 23:18, you wrote:
Try:
make clean make dep make bzlilo
then
make modules make modules_install.
I would recommend reading the Kernel-HOWTO, in particular:
OK, anyway I can test this before I shutdown? I have completed all the steps. Thanks to all for the help. BTW, Nils, I thought you said this was easy! Cheers, Brian
On Sun, Mar 17, 2002 at 12:41:00AM +0700, durant@cbn.net.id wrote:
OK, anyway I can test this before I shutdown? I have completed all the steps. Thanks to all for the help.
Well, you get something along the lines of added linux* added suse added memtest86 at the end of 'make bzlilo'. Also, the various stages of make should end relatively hopefully (i.e. not shouting "ERROR!" all over the place... But no, you can't test a kernel without booting it. If you want, you can 'make bzdisk' instead of 'make bzlilo' to make a bootable floppy instead of overwriting your installation, or if you're up for a bit more hacking, you could add an extra boot option to the lilo.conf, and install your kernel image in a different place, but this is for people who know more about what they're doing :-) Of course, the 'suse' option should remain, in case you stuff up your default kernel.
BTW, Nils, I thought you said this was easy!
It is. :-) (relatively). To a long-time linux user, compiling a kernel, playing around with lilo configurations, etc. is almost second nature. To a new user, it can be a little bewildering, but it's pretty easy if you just follow the steps. -- David Smith Work Email: Dave.Smith@st.com STMicroelectronics Home Email: David.Smith@ds-electronics.co.uk Bristol, England
lördagen den 16 mars 2002 17.06 skrev du:
On Saturday 16 March 2002 01:30, you wrote:
Hi, all you have to do is recompile the kernel.
cd /usr/src/linux make cloneconfig make xconfig or make menuconfig do you changes recompile
Got "recompile command not found". What do I do?
Cheers,
Brian
Hi, first you should install the kenelsource. Start upp yast2 software install/remove software, be sure to have the first cd in the cdplayer. Look for kernel-source in zall. mark it and install. Recompile is not a command it was just a short word for make clean make dep make bzlilo I would sugest that you read reference manual page 229 Rgds Nisse
On Saturday 16 March 2002 23:35, you wrote:
first you should install the kenelsource. Start upp yast2 software install/remove software, be sure to have the first cd in the cdplayer. Look for kernel-source in zall. mark it and install.
Recompile is not a command it was just a short word for make clean make dep make bzlilo
I would sugest that you read reference manual page 229
Thanks for the tip. Do I need to do a #make modules" for the ACPI or do I just end with "make bzlilo"? Cheers, Brian
Brian Durant wrote:
Thanks for the tip. Do I need to do a #make modules" for the ACPI or do I just end with "make bzlilo"?
Cheers,
Brian
This is how I installed the 2.4.18 kernel on SuSE 7.3. I hope it helps. JDL ===================================================================== Downloaded and installed kernel 2.4.18.SuSE-0 from mirror.ac.uk mirror of SuSE. You can get it from ftp://ftp.suse.com under people/mantel/next/linux-2.4.18.SuSE-0.tar.bz2 Saved it in directory and copied (actually linked) it to /usr/src/linux-2.4.18.SuSE-0/.tar.bz2 # cd /usr/src # tar Ixvf linux-2.4.18.SuSE-0.tar.bz2 [creates new directory /usr/src/linux-2.4.18.SuSE] # rm linux [removes old link] # ln -s linux-2.4.18.SuSE linux # cd /usr/src/linux-2.4.18.SuSE Now copy file test-25.12.01 from 2.4.16 kernel directory to /usr/src/linux-2.4.18.SuSE and rename it to test-4.3.02 ... (Instead I could have used hidden file .config in original kernel directory, but this will require less work in configuring. This trick makes sure that in the few cases where I'm not sure what makes sense, I should get the SuSE default settings.) # make mrproper # make xconfig [needs to be done with root (# sux ) access] Load configurations from test-4.3.02. Sound stuff looks like (I want alsa for emu10k1): y Sound card support m BT878 audio dma m C-media PCI y Enable legacy FM y Enable legacy MPU-401 y Enable joystick y Support CMI8738... n Inverse S/PDIF in for CMI8738 y Enable S/PDIF loop for CMI8738 m Creative SBLive! (EMU10K1) y Creative SBLive! MIDI Everything else m for sound card and default y/n values for anything else. Probably could say no to everything else and save some compilation time. Check (takes a while - lots of settings), save and exit # make dep [ takes about 2 minutes (500MHz Celeron) ] # make clean # make bzImage [takes about 12 minutes] # make modules [takes about 30 minutes ] # make modules_install [won't overwrite anything] ...5.3.02... copy bzImage from /usr/src/linux-2.4.18.SuSE/arch/i386/boot to /boot and rename vmlinuz-2.4.18-4GB copy System.map from /usr/src/linux-2.4.18.SuSE to /boot and rename System.map-2.4.18-4GB # mk_initrd -k "vmlinuz-2.4.18-4GB" -i "initrd-2.4.18-4GB" -s auto edit /etc/lilo.conf and change kernel to 2.4.16 (doesn't remove old kernel or modules) # lilo -b /dev/fd0 [installs lilo on a floppy. If it doesn't work, I still haven't lost anything] reboot (from floppy) This all worked without problems, except sound was lost (as expected). As root... # lilo [This time installs on hard disk] Acttually I used lilo -b /dev/hda because lilo doesn't work unless I use -b # lilo reboot and install alsa as follows... used alsa-driver-0.5.12a (needed for 2.4.14+ kernels) in /usr/src/packages/SOURCES/alsa-driver-0.5.12a //# cd /usr/src/packages/SOURCES //# tar zxvf alsa-driver-0.5.12a.tar.gz //# cd alsa-driver-0.5.12a and compiled... # modprobe soundcore (probably not needed) [root] Hmmm. modprobe: Can't locate module soundcore # CFLAGS="-O2 -march=i686" ./configure [Don't use the -march=i686 flag if you have an Athlon!] # make install [root] # ./snddevices [root] (probably not needed) All successful.
Don't forget to run mk_initrd and lilo after you do all the steps to compile a new kernel or you won't be booting. :) -=Ben --=====-----=====-- mailto:ben@whack.org --=====-- "I've never been quarantined. But the more I look around the more I think it might not be a bad thing." -JC --=====-----=====--
On Sat, Mar 16, 2002 at 10:14:16AM -0800, ben@whack.org wrote:
Don't forget to run mk_initrd and lilo after you do all the steps to compile a new kernel or you won't be booting. :)
Yes, I forgot about mk_initrd, since that doesn't apply to me (and probably doesn't apply to most people). However, 'make bzlilo' removes the requirement for a separate running of lilo. -- David Smith | Tel: +44 (0)1454 462380 Home: +44 (0)1454 616963 STMicroelectronics | Fax: +44 (0)1454 617910 Mobile: +44 (0)7932 642724 1000 Aztec West | TINA: 065 2380 Almondsbury | Work Email: Dave.Smith@st.com BRISTOL, BS32 4SQ | Home Email: David.Smith@ds-electronics.co.uk
You have to rerun lilo after mk_initrd or so I was told. No matter when it was run in the past. The two last things that should be done on 7.2 or 7.3 and the upcoming 8.0 are mk_initrd and lilo to update it so it knows where the correct initrd is ;) Cheers! -=Ben * Dave Smith (Dave.Smith@st.com) [020316 10:25]: ->On Sat, Mar 16, 2002 at 10:14:16AM -0800, ben@whack.org wrote: ->> ->> Don't forget to run mk_initrd and lilo after you do all the steps to ->> compile a new kernel or you won't be booting. :) -> ->Yes, I forgot about mk_initrd, since that doesn't apply to me (and probably ->doesn't apply to most people). However, 'make bzlilo' removes the ->requirement for a separate running of lilo. --=====-----=====-- mailto:ben@whack.org --=====-- "I've never been quarantined. But the more I look around the more I think it might not be a bad thing." -JC --=====-----=====--
On Sat, Mar 16, 2002 at 10:28:03AM -0800, ben@whack.org wrote:
You have to rerun lilo after mk_initrd or so I was told. No matter when it was run in the past. The two last things that should be done on 7.2 or 7.3 and the upcoming 8.0 are mk_initrd and lilo to update it so it knows where the correct initrd is ;)
I stand corrected (I don't need an initrd, so I usually forget this stage). However, the chances are that given the person involved appears to have little linux experience, they are unlikely to have a setup requiring an initrd (ReiserFS/NFS/SCSI root). OK, they might have SCSI disks, but I'd wager that an initrd is unnecessary. I'm trying to keep things as simple as possible :-) -- David Smith Work Email: Dave.Smith@st.com STMicroelectronics Home Email: David.Smith@ds-electronics.co.uk Bristol, England
On Saturday 16 March 2002 19.35, Dave Smith wrote:
On Sat, Mar 16, 2002 at 10:28:03AM -0800, ben@whack.org wrote:
You have to rerun lilo after mk_initrd or so I was told. No matter when it was run in the past. The two last things that should be done on 7.2 or 7.3 and the upcoming 8.0 are mk_initrd and lilo to update it so it knows where the correct initrd is ;)
I stand corrected (I don't need an initrd, so I usually forget this stage).
However, the chances are that given the person involved appears to have little linux experience, they are unlikely to have a setup requiring an initrd (ReiserFS/NFS/SCSI root). OK, they might have SCSI disks, but I'd wager that an initrd is unnecessary. I'm trying to keep things as simple as possible :-)
It was a while since I did a fresh install last so my memory may be deceiving me, but I was pretty sure reiser was the default in 7.3, so for most people, certainly all "newbies" who select default, mk_initrd will be necessary. //Anders
On Saturday, 16 March 2002 13:40, Anders Johansson wrote:
It was a while since I did a fresh install last so my memory may be deceiving me, but I was pretty sure reiser was the default in 7.3
Hi! I just did one (7.3-pers, since 7.3-pro may be different). It's a mixed bag: the installer starts offering 'reiserfs' as default, but the moment you choose one partition to be 'ext2' (like /boot; who's going to reiserfs a 12MB partition?), then the following partitions will be 'ext2' by default, regardless of size. But 'initrd' is necessary, I think, since it is in /etc/rc.config: INITRD_MODULES="reiserfs" gr (in /usually/ sunny, balmy Florida) ¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬ Transcendental Questions: "Since money doesn't buy hapiness, what about a credit card?"
USB and PCMCIA modes are often listed in the initrd. :) If one is using 7.2 --> up then SuSE makes use of the initrd :) A good way is to check /etc/rc.config and see. If one doesn't see this section...then they are most likely not using and initrd. :) -- INITRD_MODULES=" <whatever modules maybe listed> " -- If the above has modules listed after it in the /etc/rc.config then initrd is used. :) Remember a newbie who hasn't been running SuSE for more then a few months will most likely be running 7.2 or 7.3 :) Cheers! and Have a good weekend. * Dave Smith (Dave.Smith@st.com) [020316 10:36]: ->On Sat, Mar 16, 2002 at 10:28:03AM -0800, ben@whack.org wrote: ->> You have to rerun lilo after mk_initrd or so I was told. No matter when ->> it was run in the past. The two last things that should be done on 7.2 ->> or 7.3 and the upcoming 8.0 are mk_initrd and lilo to update it so it ->> knows where the correct initrd is ;) -> ->I stand corrected (I don't need an initrd, so I usually forget this stage). -> ->However, the chances are that given the person involved appears to have ->little linux experience, they are unlikely to have a setup requiring an ->initrd (ReiserFS/NFS/SCSI root). OK, they might have SCSI disks, but ->I'd wager that an initrd is unnecessary. I'm trying to keep things as ->simple as possible :-) -> ->-- ->David Smith Work Email: Dave.Smith@st.com ->STMicroelectronics Home Email: David.Smith@ds-electronics.co.uk ->Bristol, England -> ->-- ->To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com ->For additional commands send e-mail to suse-linux-e-help@suse.com ->Also check the FAQ at http://www.suse.com/support/faq and the ->archives at http://lists.suse.com -> --=====-----=====-- mailto:ben@whack.org --=====-- "I've never been quarantined. But the more I look around the more I think it might not be a bad thing." -JC --=====-----=====--
On Sat, Mar 16, 2002 at 07:40:08PM +0100, andjoh@cicada.linux-site.net wrote:
It was a while since I did a fresh install last so my memory may be deceiving me, but I was pretty sure reiser was the default in 7.3, so for most people, certainly all "newbies" who select default, mk_initrd will be necessary.
I'm still on 7.2, so I assumed ext2 was still the default :-) On Sat, Mar 16, 2002 at 10:42:50AM -0800, ben@whack.org wrote:
USB and PCMCIA modes are often listed in the initrd. :)
If one is using 7.2 --> up then SuSE makes use of the initrd :)
I thought modules were only placed in the initrd if they were required for booting or mounting the root FS? e.g. PCMCIA modules if booting from a PCMCIA network card, etc. On my 7.2 system, which is relatively default, no initrd was required. Things may be (probably are) different for 7.3, though.
A good way is to check /etc/rc.config and see. If one doesn't see this section...then they are most likely not using and initrd. :)
INITRD_MODULES=" <whatever modules maybe listed> "
I was going to say that, but I couldn't remember the name of the variable, and I don't currently have access to a SuSE machine. Anyway, we've pretty much done this subject to death now... <g> -- David Smith Work Email: Dave.Smith@st.com STMicroelectronics Home Email: David.Smith@ds-electronics.co.uk Bristol, England
On Sunday 17 March 2002 01:35, you wrote:
I stand corrected (I don't need an initrd, so I usually forget this stage).
However, the chances are that given the person involved appears to have little linux experience, they are unlikely to have a setup requiring an initrd (ReiserFS/NFS/SCSI root). OK, they might have SCSI disks, but I'd wager that an initrd is unnecessary. I'm trying to keep things as simple as possible :-)
Well, it looks like I have done everything I can do. Hopefully you will hear from me again tomorrow morning without this subject heading on my e-mails ;-) Thanks again to all for support and patience. Brian
On Sunday 17 March 2002 01:24, you wrote:
Yes, I forgot about mk_initrd, since that doesn't apply to me (and probably doesn't apply to most people). However, 'make bzlilo' removes the requirement for a separate running of lilo.
Does mk_initrd apply to me? I checked lilo in YAST2 and it seems to be setup properly. Brian
On Saturday 16 March 2002 01:30 pm, Brian Durant wrote:
Does mk_initrd apply to me? I checked lilo in YAST2 and it seems to be setup properly.
mk_initrd is relatively fast, it doesn't hurt to run it just to be on the safe side. -- Down with categorical imperative!
participants (8)
-
Anders Johansson -
Ben Rosenberg -
Brian Durant -
Dave Smith -
gilson redrick -
John Lamb -
Joshua Lee -
Nils Sjöholm