Re: Installing kernel upgrade from 2.4 to 2.6
On Wed, Jun 21, 2006 at 05:47:25PM -0400, Sam Rosenfeld wrote: I am using Debian Sarge with a 2.4.27 linux kernel. I have tried to install a new kernel with: aptitude install kernel-image-2.6-i686 but it does not replace my old kernel (2.4.27), even after a cold start. I don't feel entirely comfortable with Debian, so I'd appreciate any help. I am including a copy of /boot/grub/menu.lst and of /etc/apt/sources.lst The /etc/apt/sources.lst should not be needed. What error messages did you get? # menu.lst - See: grub(8), info grub, update-grub(8) #grub-install(8), grub-floppy(8), #grub-md5-crypt, /usr/share/doc/grub #and /usr/share/doc/grub-doc/. default 0 timeout 5 color cyan/blue white/blue title Debian GNU/Linux, kernel 2.4.27-2-386 root (hd0,0) kernel/boot/vmlinuz-2.4.27-2-386 root=/dev/hda1 ro initrd/boot/initrd.img-2.4.27-2-386 savedefault boot title Debian GNU/Linux, kernel 2.4.27-2-386 (recovery mode) root (hd0,0) kernel/boot/vmlinuz-2.4.27-2-386 root=/dev/hda1 ro single initrd/boot/initrd.img-2.4.27-2-386 savedefault boot Did you try update-grub as root? -- Chris. == -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing kernel upgrade from 2.4 to 2.6
Hi, On 6/22/06, Sam Rosenfeld [EMAIL PROTECTED] wrote: I am using Debian Sarge with a 2.4.27 linux kernel. I have tried to install a new kernel with: aptitude install kernel-image-2.6-i686 but it does not replace my old kernel (2.4.27), even after a cold start. I don't feel entirely comfortable with Debian, so I'd appreciate any help. snip As Chris said, run update-grub to notify grub that a new kernel has to be included. When you install a kernel-image, the bootloader (configuration) is not automatically updated. This is controlled by the contents of the file /etc/kernel-img.conf. More details about this configuration can be found in the kernel-img.conf(5) man page. You might want to look at that file so that you don't have such problems in future. I personally never felt like configuring it, so won't be able to help you much. But you should look at /usr/share/doc/kernel-package/examples/sample.kernel-img.conf for a sample configuration. Hope this helps. Srinidhi. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: installing kernel 2.6
On (20/11/05 15:24), Rafael Alexandre Schmitt wrote: * Clive Menzies ([EMAIL PROTECTED]) wrote: On (20/11/05 10:31), Rafael Alexandre Schmitt wrote: * Jeff Lucas ([EMAIL PROTECTED]) wrote: I am having problems after installing the kernel 2.6.14.2. it comes up with a kernel panic and says something about not being able to boot from the hard drive. I'm a new linux user and like it so far, but I'm having trouble getting things to work for me. This is happening with me too. Can you post the output of # ls -l /boot and # cat /etc/boot/menu.lst Sorry, engage brain :) /boot/grub/menu.lst Helo , Here it is: [EMAIL PROTECTED]:~$ ls -l /boot total 6308 -rw-r--r-- 1 root root 512 2005-11-08 15:08 boot.0300 lrwxrwxrwx 1 root root 11 2005-11-08 15:07 boot.b - boot-menu.b -rw-r--r-- 1 root root 308326 2005-11-08 17:58 coffee.bmp -rw-r--r-- 1 root root 16984 2005-11-08 15:04 config-2.4.18-bf2.4 -rw-r--r-- 1 root root 61109 2005-09-27 00:38 config-2.6.12-1-686 lrwxrwxrwx 1 root root 15 2005-11-08 17:49 debian.bmp - /boot/sarge.bmp -rw-r--r-- 1 root root 153720 2005-11-08 17:58 debianlilo.bmp -rw-r--r-- 1 root root 1794048 2005-11-20 17:14 initrd.img-2.6.12-1-686 -rw--- 1 root root 44032 2005-11-20 17:17 map -rw-r--r-- 1 root root 23662 2005-11-08 17:58 sarge.bmp -rw-r--r-- 1 root root 24116 2005-11-08 17:58 sid.bmp -rw-r--r-- 1 root root 559088 2005-11-08 15:04 System.map-2.4.18-bf2.4 -rw-r--r-- 1 root root 862526 2005-09-27 02:01 System.map-2.6.12-1-686 -rw-r--r-- 1 root root 1263339 2005-11-08 15:04 vmlinuz-2.4.18-bf2.4 -rw-r--r-- 1 root root 1292638 2005-09-27 02:01 vmlinuz-2.6.12-1-686 It doesn't look as though 2.6.14-2 is installed; can you boot into either of the kernels shown? I see you're using lilo it's been a while since I've used it but it would be worth posting the lilo.conf file (you don't have grub installed and so won't have menu.lst). Regards Clive -- www.clivemenzies.co.uk ... ...strategies for business -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: installing kernel 2.6
Clive Menzies wrote: On (20/11/05 15:24), Rafael Alexandre Schmitt wrote: * Clive Menzies ([EMAIL PROTECTED]) wrote: On (20/11/05 10:31), Rafael Alexandre Schmitt wrote: * Jeff Lucas ([EMAIL PROTECTED]) wrote: I am having problems after installing the kernel 2.6.14.2. it comes up with a kernel panic and says something about not being able to boot from the hard drive. I'm a new linux user and like it so far, but I'm having trouble getting things to work for me. This is happening with me too. Can you post the output of # ls -l /boot and # cat /etc/boot/menu.lst Sorry, engage brain :) /boot/grub/menu.lst Helo , Here it is: [EMAIL PROTECTED]:~$ ls -l /boot total 6308 -rw-r--r-- 1 root root 512 2005-11-08 15:08 boot.0300 lrwxrwxrwx 1 root root 11 2005-11-08 15:07 boot.b - boot-menu.b -rw-r--r-- 1 root root 308326 2005-11-08 17:58 coffee.bmp -rw-r--r-- 1 root root 16984 2005-11-08 15:04 config-2.4.18-bf2.4 -rw-r--r-- 1 root root 61109 2005-09-27 00:38 config-2.6.12-1-686 lrwxrwxrwx 1 root root 15 2005-11-08 17:49 debian.bmp - /boot/sarge.bmp -rw-r--r-- 1 root root 153720 2005-11-08 17:58 debianlilo.bmp -rw-r--r-- 1 root root 1794048 2005-11-20 17:14 initrd.img-2.6.12-1-686 -rw--- 1 root root 44032 2005-11-20 17:17 map -rw-r--r-- 1 root root 23662 2005-11-08 17:58 sarge.bmp -rw-r--r-- 1 root root 24116 2005-11-08 17:58 sid.bmp -rw-r--r-- 1 root root 559088 2005-11-08 15:04 System.map-2.4.18-bf2.4 -rw-r--r-- 1 root root 862526 2005-09-27 02:01 System.map-2.6.12-1-686 -rw-r--r-- 1 root root 1263339 2005-11-08 15:04 vmlinuz-2.4.18-bf2.4 -rw-r--r-- 1 root root 1292638 2005-09-27 02:01 vmlinuz-2.6.12-1-686 It doesn't look as though 2.6.14-2 is installed; can you boot into either of the kernels shown? I see you're using lilo it's been a while since I've used it but it would be worth posting the lilo.conf file (you don't have grub installed and so won't have menu.lst). Regards Clive menu.lst is under /boot/grub regards Thierry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: installing kernel 2.6
* Jeff Lucas ([EMAIL PROTECTED]) wrote: I am having problems after installing the kernel 2.6.14.2. it comes up with a kernel panic and says something about not being able to boot from the hard drive. I'm a new linux user and like it so far, but I'm having trouble getting things to work for me. This is happening with me too. Rafael. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: installing kernel 2.6
On (20/11/05 10:31), Rafael Alexandre Schmitt wrote: * Jeff Lucas ([EMAIL PROTECTED]) wrote: I am having problems after installing the kernel 2.6.14.2. it comes up with a kernel panic and says something about not being able to boot from the hard drive. I'm a new linux user and like it so far, but I'm having trouble getting things to work for me. This is happening with me too. Can you post the output of # ls -l /boot and # cat /etc/boot/menu.lst Regards Clive -- www.clivemenzies.co.uk ... ...strategies for business -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: installing kernel 2.6
* Clive Menzies ([EMAIL PROTECTED]) wrote: On (20/11/05 10:31), Rafael Alexandre Schmitt wrote: * Jeff Lucas ([EMAIL PROTECTED]) wrote: I am having problems after installing the kernel 2.6.14.2. it comes up with a kernel panic and says something about not being able to boot from the hard drive. I'm a new linux user and like it so far, but I'm having trouble getting things to work for me. This is happening with me too. Can you post the output of # ls -l /boot and # cat /etc/boot/menu.lst Helo , Here it is: [EMAIL PROTECTED]:~$ ls -l /boot total 6308 -rw-r--r-- 1 root root 512 2005-11-08 15:08 boot.0300 lrwxrwxrwx 1 root root 11 2005-11-08 15:07 boot.b - boot-menu.b -rw-r--r-- 1 root root 308326 2005-11-08 17:58 coffee.bmp -rw-r--r-- 1 root root 16984 2005-11-08 15:04 config-2.4.18-bf2.4 -rw-r--r-- 1 root root 61109 2005-09-27 00:38 config-2.6.12-1-686 lrwxrwxrwx 1 root root 15 2005-11-08 17:49 debian.bmp - /boot/sarge.bmp -rw-r--r-- 1 root root 153720 2005-11-08 17:58 debianlilo.bmp -rw-r--r-- 1 root root 1794048 2005-11-20 17:14 initrd.img-2.6.12-1-686 -rw--- 1 root root 44032 2005-11-20 17:17 map -rw-r--r-- 1 root root 23662 2005-11-08 17:58 sarge.bmp -rw-r--r-- 1 root root 24116 2005-11-08 17:58 sid.bmp -rw-r--r-- 1 root root 559088 2005-11-08 15:04 System.map-2.4.18-bf2.4 -rw-r--r-- 1 root root 862526 2005-09-27 02:01 System.map-2.6.12-1-686 -rw-r--r-- 1 root root 1263339 2005-11-08 15:04 vmlinuz-2.4.18-bf2.4 -rw-r--r-- 1 root root 1292638 2005-09-27 02:01 vmlinuz-2.6.12-1-686 [EMAIL PROTECTED]:~$ cat /etc/boot/menu.lst cat: /etc/boot/menu.lst: Arquivo ou diretório não encontrado There is no /etc/boot on my machine. -- Rafael Alexandre Schmitt Blumenau - Santa Catarina - Brasil
Re: installing kernel 2.6
Jeff Lucas wrote: I am having problems after installing the kernel 2.6.14.2. it comes up with a kernel panic and says something about not being able to boot from the hard drive. I'm a new linux user and like it so far, but I'm having trouble getting things to work for me. This thread from October has some good tips for kernel compiling newbies. Read the whole thread. http://lists.debian.org/debian-user/2005/10/msg03195.html Another problem I'm having is installin the driver for my video card. It's a Nvidia Gforce 4 MX420. When I try to install the .run program it tells me something about the kernel source. If someone can help me I would Greatly Appreciate it. I can't help you there. I don't use non-free drivers. I'd be surprised if there isn't a few pages on the Web about installing nVidia drivers though. Good luck! -- Mitch Wiedemann Webmaster - Ithaca Free Software Association http://ithacafreesoftware.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: installing kernel?
0debian user [EMAIL PROTECTED] writes: Hi I am running Debian unstable with kernel image 2.2.18 (! But I guess if you installed woody from a non-bf24 kernel and then updated, you could legitimately have something this ancient.) 1) What kernel should I install (a 2.4.24 stable kernel or a more risky 2.6.0)? I would suggest staying with the 2.4.x series until 2.6.x has proved itself a little more; YMMV. 2) How does one install kernel image package in Debian? Do I have to move ny old modules directory away so they are not overwritten if the new kernel fails and I must boot the old one? No, that shouldn't be necessary... 3) How does one install kernel from source in Debian? After it is compiled I should move the kernel image to /vmlinuz and copy over the System.map file to / ? I should run lilo -v before reboot? You should install the kernel-package package, and use that to build your kernel source and install it. There's a document linked to from http://newbiedoc.sourceforge.net/ which explains how to do this; you can also read kernel-package's documentation. But essentially, you run make-kpkg on a configured kernel source tree, it chews on things for a while, and eventually spits out a kernel-image .deb package. You install that with 'dpkg --install', which deals with making sure /vmlinuz points somewhere sane. Run 'lilo' if you need to and reboot. 4) What should I add to /etc/lilo.conf so it will let me select old or new kernel? Should work out-of-the-box, with options to boot /vmlinuz and /vmlinuz.old. 5) What is initrd and is it good to use? It's a system where the kernel boots from a ramdisk, loads some modules, and then goes on with life. It's useful if you don't know what needs to be compiled into the kernel, which is particularly important if you're building an official distribution kernel that everyone uses. It's probably more of a pain than it's worth if you're compiling a kernel for one specific machine. 6) How do I know what in the kernel config I should let the kernel load as modules and what should be compiled into the kernel image? If you're not using initrd, you must compile in drivers for your root disk and root filesystem. I'd suggest building modules for any removable device (so if you get a new USB mumble, you don't need to rebuild to have a driver for it), and not building modules for non-removable devices you don't have (e.g., ISA Ethernet cards). But building extra modules doesn't hurt, except in compile time and disk space. 7) Is there a good kernel install/config guide that is tailored to Debian and addresses 2.4.24 or 2.6.0 kernel? See earlier-referenced http://newbiedoc.sourceforge.net/ article. -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: installing kernel?
* 0debian user [EMAIL PROTECTED] [040110 15:07]: 1) What kernel should I install (a 2.4.24 stable kernel or a more risky 2.6.0)? Well I installed 2.6.0 three days ago, and it didn't crashed, and still works on my workstation and my notebook. However: I won't install any 2.6 Kernel on my productive server, until I'm realy sure, that it will work. If I don't encounter any problems, perhaps in three or four weeks. If you use your computer just for fun, try 2.6, its nice. In any other case you should answer your question yourself ;) 2) How does one install kernel image package in Debian? Like installing every other package: apt-cache search kernel-image, choose one, apt-get install your-choosen-kernel-image Do I have to move ny old modules directory away so they are not overwritten if the new kernel fails and I must boot the old one? No, you don't have to. Take a look at /lib/modules. There are subdirectories for each kernel-version. 3) How does one install kernel from source in Debian? You can either apt-cache search kernel-source ; apt-get install one-source-package, or get the vanilla sources from a kernel.org mirror near to you. I prefer to compile my kernels with the make-kpkg-tool in the package kernel-package. This tool will create your very own kernel-image debian package, which you can easily install. After it is compiled I should move the kernel image to /vmlinuz and copy over the System.map file to / ? I should run lilo -v before reboot? If you use make-kpkg and install the resulting deb, you don't need to do this. When you install the package, the vmlinuz / vmlinuz.old symlinks will be updated, and lilo will be run. /etc/lilo allready contains an entry fpr vmlinuz.old. 4) What should I add to /etc/lilo.conf so it will let me select old or new kernel? Debian's default lilo-configuration allready contains a section for /vmlinuz and /vmlinuz.old, but if you install an debian kernel, you might need to add initrd=/initrd to the vmlinuz section. You will be told about that, when installing the kernel. 5) What is initrd and is it good to use? initrd is an initial ramdisk containing everything, which is needed access your hard discs. There are quite many discs drivers, drivers for scsi adaptors, filesystems and so on, a gerneral multi purpose kernel from a distribution should be able to access all these devices, therefore it would became realy big. To get a small multi purpose kernel, you can compile all those drivers as module, and throw them in a small virtual disc image, your initial ramdisc. Now if your small kernel knows, where this disc image is, it can access it, load the necasary modules, and is then able to access your hard disc. If you compile your own kernel for one machine, your propaly won't use it, and instead compile your kernel with included support for your filesystems and disc adaptors. 6) How do I know what in the kernel config I should let the kernel load as modules and what should be compiled into the kernel image? Compile everything, which is needed to boot and access your disc (don't forget filesystems!), direct in the kernel. You may leave everything else as a module. 7) Is there a good kernel install/config guide that is tailored to Debian and addresses 2.4.24 or 2.6.0 kernel? Don't know, ask google. Yours sincerely, Alexander signature.asc Description: Digital signature
Re: installing kernel?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, Jan 10, 2004 at 09:07:56AM -0500, 0debian user wrote: 1) What kernel should I install (a 2.4.24 stable kernel or a more risky 2.6.0)? Go with 2.6.0. The water's fine. 8:o) 2) How does one install kernel image package in Debian? Do I have to move ny old modules directory away so they are not overwritten if the new kernel fails and I must boot the old one? 3) How does one install kernel from source in Debian? After it is compiled I should move the kernel image to /vmlinuz and copy over the System.map file to / ? I should run lilo -v before reboot? [...] 7) Is there a good kernel install/config guide that is tailored to Debian and addresses 2.4.24 or 2.6.0 kernel? Leave your current image package installed, just apt-get yourself a new image. If you want to compile from source, get kernel-source-2.6.0 and it should automatically pull in the dev tools you need, plus kernel-package. Look in /usr/share/doc/kernel-package for documentation on how to compile a Debianized kernel package with your own options. 4) What should I add to /etc/lilo.conf so it will let me select old or new kernel? Don't. The Debian packages just make symlinks point where things need to go so it doesn't have to keep changing lilo.conf 5) What is initrd and is it good to use? 6) How do I know what in the kernel config I should let the kernel load as modules and what should be compiled into the kernel image? initrd is INITial Ram Disk. It's someplace to load kernel modules from required to boot if you like using lots of modules (for smaller, faster kernels). Most people won't notice the difference of not using an initrd and having the required stuff compiled straight in, but initrd doesn't require you to know what you need, just compile all the modules. It seems to be a matter of preference in whether you want to have the hassle at compile time or not, for a small convienence down the road. - -- .''`. Paul Johnson [EMAIL PROTECTED] : :' : `. `'` proud Debian admin and user `- Debian - when you have better things to do than fix a system -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAAI4UUzgNqloQMwcRAurjAKDF0ynb9PB7tcwQDhwMl8ziol1ZAgCgo0RM gQLRagMoBtsLGiYMkxvDYpw= =DWfX -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing kernel 2.4 in Woody
On Sat, Nov 01, 2003 at 01:06:01PM -0500, Jack Dodds said I'm installing Woody on a Pentium Pro. I've done a net install, but have not run tasksel yet. The net install leaves me with kernel 2.2. I'd like to have the 2.4 kernel becasue I need the capability to mount a subdirectory, which according to the man page is available in 2.4 but not 2.2. Yup, bind mounts, very handy. Before I install 2.4 I have some questions which I hope some helpful person can comment on! - Do I simply do an apt-get install kernel-image-2.4.18-1-686 and reboot, or is there more to it than that? This is basically it. You do, however, have to add a single line to your /etc/lilo.conf and rerun lilo before you reboot. If you don't, your new kernel will not be bootable. Don't panic if this happens, just boot your previous one with a simple linuxold at the lilo: prompt. - Both 2.4.16 and 2.4.18 are in the package lists for woody. Is there any reason not to choose the latest version? None that I know of. - It seems to me to make more sense to upgrade the kernel first and run tasksel after. Am I right? Could tasksel cause kernel 2.4 to be uninstalled? It shouldn't really matter. The Debian package tools are very careful to only upgrade or otherwise play around with kernels if you explicitly tell them to. - Is 2.4 likely to cause any problems or conflicts with the packages that would typically be loaded by tasksel? I would be selecting all the development tasks, the desktop environment task, and the scientific applications task. Your kernel is largely unrelated to your userland programs. Some things like hardware temperature monitor applets or hardware accelerated 3d drivers require kernel support, but 95% of programs won't know or care what kernel you have installed. You certainly won't have any problems installing KDE or GNOME or emacs or apache or whatever if you upgrade your kernel. -- Rob Weir [EMAIL PROTECTED] | [EMAIL PROTECTED] | Do I look like I want a CC? Words of the day: SHA Fidel Castro DES Ft. Bragg ASDIC credit card AUTODIN signature.asc Description: Digital signature
Re: Installing kernel-image-2.4.17-k7
Manoj Srivastava wrote: The new warning reads: == As a reminder, in order to configure lilo, you need to add an 'initrd=/initrd.img' to the image=/vmlinuz stanza of your /etc/lilo.conf == Clarified. == I repeat, You need to configure your boot loader. If you have already done so, and you wish to get rid of this message, please put `do_initrd = Yes' in /etc/kernel-img.conf. Note that this is optional, but if you do not, you'll contitnue to see this message whenever you install a kernel image using initrd. == Much improved! Strong work, Manoj!
Re: Installing kernel-image-2.4.17-k7
Stan == Stan Kaufman [EMAIL PROTECTED] writes: Stan This was good; it pointed out which RTFM was germane. A note Stan that the new 2.4.x kernel images use initrd whereas the 2.2.x Stan kernels didn't would help those of us who don't follow kernel Stan development realize that there's something new that we need to Stan pay attention here. Well, initrd's are not inherent to 2.4.x kernels (none of my 2.4 kernels use initrd, but you may make a 2.2 initrd image if you wish), so we can't make general statements like that. However, the fact that you are getting this message indicates that something strange is going on, no? Stan More explicit instructions about where in /etc/lilo.conf the Stan line should go would have made the fix easier--that it should Stan go in the image=/vmlinuz section, and not at, say, the end of Stan the file. Perhaps this is obvious once you know, but it's those Stan of us who don't know who need clear instructions! ;-) From the Stan number of posts I found on this topic in the archives, Stan apparently there are a few of us out there. The new warning reads: == As a reminder, in order to configure lilo, you need to add an 'initrd=/initrd.img' to the image=/vmlinuz stanza of your /etc/lilo.conf == Stan This confused me a bit. At first I thought maybe Stan /etc/kernel-img.conf was necessary for the kernel to install, Clarified. == I repeat, You need to configure your boot loader. If you have already done so, and you wish to get rid of this message, please put `do_initrd = Yes' in /etc/kernel-img.conf. Note that this is optional, but if you do not, you'll contitnue to see this message whenever you install a kernel image using initrd. == Stan So, I'm not clear how this particular warning aids the Stan process. Should the user be allowed to eliminate the warning Stan even if they haven't done the Right Thing with lilo.conf yet? Hey. The customer is always right. Perhaps LILO is not the primary boot loader -- suppose they now use grub, but never really removed lilo from the machine. Suppose they did remove lilo, but did not purge it. Far be it for me to programmatically over rule the human. Stan Thanks for requesting input, Manoj, and thanks for maintaining Stan the package!! You're welcome. manoj -- The opulence of the front office door varies inversely with the fundamental solvency of the firm. Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/%7Esrivasta/ 1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Re: Installing kernel-image-2.4.17-k7
Bill == Bill Moseley [EMAIL PROTECTED] writes: Bill I think those are clear, now that the parts are making more Bill sense to me. It might be helpful to show the lilo line in the Bill first message box, Well, the first message is spit out before we have determined what boot loader is being used. See, the first message should be output to all users, whether or not they use lilo (silo, quik, palo, vmelilo, yaboot, zipl, grub, or nettrom are the other loaders that kernel-package tries to support -- pardon me if I missed a couple). The second message is lilo specific. Bill and maybe say what an initrd kernel image means. But, it's Hmm. == You are attempting to install an initrd kernel image (version $version) This will not work unless you have configured your boot loader to use initrd. (An initrd image is a kernel image that expects to use an INITial Ram Disk to mount a minimal root file system into RAM and use that for booting). == Bill I'm not exactly clear what installing from a package does -- Bill copies the image to /boot, sets up the symlinks, copies the Bill modules to /lib/modules. I guess it also let's you manage the Bill compiled kernel as a package. That's most of it. It does take the tedium out of the process of compiling kernels as well (which was the primary motivation, back when I had a 386 and compiling a kernel took most of the disk space and an evening, and having to go back since you forgot step 3 was a royal pain). manoj -- It's the RINSE CYCLE!! They've ALL IGNORED the RINSE CYCLE!! Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/%7Esrivasta/ 1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Re: Installing kernel-image-2.4.17-k7
Stan == Stan Kaufman [EMAIL PROTECTED] writes: Stan Should be enough; the package maintainer's scripts clearly said Stan Don't go any further until you've fixed your bootloader. It Stan would have been more helpful if there had been more explicit Stan info about how to do so, but that's what the archives of this Stan list are for! Any suggestions for improved wording? This is what is there now: == You are attempting to install an initrd kernel image (version $version) This will not work unless you have configured your boot loader to use initrd. == People running lilo also get this message: == As a reminder, in order to configure lilo, you need to add an 'initrd=/initrd.img' in your /etc/lilo.conf == Everyone gets this: == I repeat, You need to configure your boot loader. If you have already done so, and you wish to get rid of this message, please put `do_initrd = Yes' in /etc/kernel-img.conf. == Some lilo users, who have this line in lilo.conf, get warned: == In addition, the line ramdisk = 0 should be removed or commented. == (non lilo users do not get the lilo specific message, of course). manoj -- We're here to give you a computer, not a religion. attributed to Bob Pariseau, at the introduction of the Amiga Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/%7Esrivasta/ 1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Re: Installing kernel-image-2.4.17-k7
At 12:21 AM 02/28/02 -0600, Manoj Srivastava wrote: Any suggestions for improved wording? This is what is there now: == You are attempting to install an initrd kernel image (version $version) This will not work unless you have configured your boot loader to use initrd. == People running lilo also get this message: == As a reminder, in order to configure lilo, you need to add an 'initrd=/initrd.img' in your /etc/lilo.conf == I think those are clear, now that the parts are making more sense to me. It might be helpful to show the lilo line in the first message box, and maybe say what an initrd kernel image means. But, it's mostly user error on my part. It's just a lot to understand the first time through. I just finished building 2.4.17 from kernel-source into a .deb, and installing that. The only step I forgot this time was to add my ethernet card to /etc/modules on first boot. Minor problem. I'm not exactly clear what installing from a package does -- copies the image to /boot, sets up the symlinks, copies the modules to /lib/modules. I guess it also let's you manage the compiled kernel as a package. Anyway, I do think the messages are fine. Thanks for your help, -- Bill Moseley mailto:[EMAIL PROTECTED]
Re: Installing kernel-image-2.4.17-k7
Manoj Srivastava wrote: Any suggestions for improved wording? This is what is there now: == You are attempting to install an initrd kernel image (version $version) This will not work unless you have configured your boot loader to use initrd. == This was good; it pointed out which RTFM was germane. A note that the new 2.4.x kernel images use initrd whereas the 2.2.x kernels didn't would help those of us who don't follow kernel development realize that there's something new that we need to pay attention here. People running lilo also get this message: == As a reminder, in order to configure lilo, you need to add an 'initrd=/initrd.img' in your /etc/lilo.conf == More explicit instructions about where in /etc/lilo.conf the line should go would have made the fix easier--that it should go in the image=/vmlinuz section, and not at, say, the end of the file. Perhaps this is obvious once you know, but it's those of us who don't know who need clear instructions! ;-) From the number of posts I found on this topic in the archives, apparently there are a few of us out there. Everyone gets this: == I repeat, You need to configure your boot loader. If you have already done so, and you wish to get rid of this message, please put `do_initrd = Yes' in /etc/kernel-img.conf. == This confused me a bit. At first I thought maybe /etc/kernel-img.conf was necessary for the kernel to install, but then I realized that it just shuts off the warning. I ended up just editing /etc/lilo.conf in another terminal and resuming the kernel install without messing with /etc/kernel-img.conf and when the install found /etc/lilo.conf to be in proper shape, all went well. So, I'm not clear how this particular warning aids the process. Should the user be allowed to eliminate the warning even if they haven't done the Right Thing with lilo.conf yet? If they have, they won't get the warning anyway. Seems to me that all would be clearer if this particular message were just dropped, or replaced by a repeat of the You can't get past this step of the install until you've fixed your boot loader message. Some lilo users, who have this line in lilo.conf, get warned: == In addition, the line ramdisk = 0 should be removed or commented. == (non lilo users do not get the lilo specific message, of course). manoj Thanks for requesting input, Manoj, and thanks for maintaining the package!! Stan
Re: Installing kernel-image-2.4.17-k7
Manoj == Manoj Srivastava [EMAIL PROTECTED] writes: Stan == Stan Kaufman [EMAIL PROTECTED] writes: Manoj Any suggestions for improved wording? This is what is Manoj there now: == You are attempting to install an initrd kernel image (version $version) This will not work unless you have configured your boot loader to use initrd. == Manoj People running lilo also get this message: == As a reminder, in order to configure lilo, you need to add an 'initrd=/initrd.img' in your /etc/lilo.conf == I actually thought the warning was great and it worked perfectly for me. I just had to 'man lilo.conf' to figure out where that line went (being completely new to initrd). Perhaps text suggesting that I add the initrd section to the 'vmlinuz' image section would have helped, but it's easy enough to RTFM. Cheers! Shyamal
Re: Installing kernel-image-2.4.17-k7
On 27 Feb 2002, Bill Moseley wrote: I had started the process of building a kernel yesterday before being so rudely interrupted by sleep. I'm currently running 2.2.20 but upgrading to 2.4.17. I had tried once before to use a kernel-image, but ended up with a kernel-panic that I never followed up on. This system was installed Woody and upgraded to Sid. I'd like to try using kernel-image-2.4.17-k7 for the experience of using a packaged kernel, and then also I'd have a very close .config to start with when I want to build my own kernel from source. So, I'd like to avoid the kernel panic this time with the kernel-image-2.4.17-k7 package. What steps do I need to take to make sure I will end up with a bootable image? Someone mentioned that moving to the more modular 2.4 kernel might have been the problem - something about not setting up initrd? I'd also like to also use lilo.conf to be able to select which kernel (I can figure this out, but I mention it as I'm not sure if just apt-get'ing the kernel-image will do this by default). Anyway, last time I just apt-get install kernel-image-2.4.17-k7, but perhaps that was not enough. I poked around looking for docs, but mostly found info about compiling my own. Any pointers? Hi Bill, i would personally not bother at all with the precompiled images. It is a very straightforward matter to compile your own kernel. You also don't need a .config file to start with. When you start up make menuconfig or make xconfig it will present you with its list of default settings. If you were to make no changes at all but simply exit and save you would get a default .config. In most cases choosing options using xconfig is very straightforward, unless you have exotic hardware. You can (and should) generally turn off entire subsystems which are enabled by default like usb or sound if you don't have the appropriate hardware. If you need to enable them, you probably should look at te appropriate howtos (if they exist). Examples of the kinds of issues that come up are a) Do I compile it into the kernel or as a module? As a rule of thumb, devices external to the base system (device drivers etc) are a good choice to compile as modules. Sometimes they need to be loaded in a particular order. b) If you are dualbooting with a Windows installation, you might want to enable fat32/ntfs filesystem read support. c) You'll want to disable pcmia if you are not using it. This seems to be something that doesn't have a proper default. At least it I don't explicly disable it, the kernel compile process always stops and asks me questions during compilation. d) You should enable ext3 support. It is simple to configure and works fine with 2.4.17. e) In some cases you can't enable some option till you have enabled another. It is sometimes not obvious (and not well documented) what that other option should be. f) You'll need to need to know in advance which drivers are needed by your sound card, ethernet card, etc. For this, it can be helpful to have another networked machine handy so you can use Google. If you want to send me a copy of your .config (as an email attachment) if you are not sure about something, and a description of your hardware I can make specific suggestions. I don't know what initrd is, but that has never affected me, and I've built kernels on several different systems AMD/Intel with 100% success (no issues whatsoever). The first time I did it I had just finished reading the docs and didn't know anything more than you do now. It is quite easy as long as you are careful. Don't let anyone convince you otherwise. Sincerely, Faheem Mitha.
Re: Installing kernel-image-2.4.17-k7
Faheem Mitha wrote: On 27 Feb 2002, Bill Moseley wrote: So, I'd like to avoid the kernel panic this time with the kernel-image-2.4.17-k7 package. What steps do I need to take to make sure I will end up with a bootable image? Someone mentioned that moving to the more modular 2.4 kernel might have been the problem - something about not setting up initrd? I just installed 2.4.17 on a new woody box, which involved an upgrade from the 2.2.14 potato system my floppy install disks created. The kernel-image package provided clear notice during installation that the bootloader needs to be altered in order to find the new image, since it's handled differently from the 2.2.x kernels. Since I use lilo, it was a simple matter of adding a couple of lines to the right entry in /etc/lilo.conf: image=/vmlinuz label=Linux initrd=/initrd.img root=/dev/hda2 # wherever your boot partition is read-only etc etc... You'd have to handle this differently with different bootloaders no doubt; perhaps sid now does things differently too (?). Anyway, once you've altered lilo.conf and run lilo, the kernel install runs flawlessly. Anyway, last time I just apt-get install kernel-image-2.4.17-k7, but perhaps that was not enough. I poked around looking for docs, but mostly found info about compiling my own. Any pointers? Should be enough; the package maintainer's scripts clearly said Don't go any further until you've fixed your bootloader. It would have been more helpful if there had been more explicit info about how to do so, but that's what the archives of this list are for! That said, all of Faheem's suggestions about rolling your own kernel are great ones. Stan
Re: Installing kernel-image-2.4.17-k7
On Wed, 27 Feb 2002, Stan Kaufman wrote: Faheem Mitha wrote: On 27 Feb 2002, Bill Moseley wrote: So, I'd like to avoid the kernel panic this time with the kernel-image-2.4.17-k7 package. What steps do I need to take to make sure I will end up with a bootable image? Someone mentioned that moving to the more modular 2.4 kernel might have been the problem - something about not setting up initrd? I just installed 2.4.17 on a new woody box, which involved an upgrade from the 2.2.14 potato system my floppy install disks created. The kernel-image package provided clear notice during installation that the bootloader needs to be altered in order to find the new image, since it's handled differently from the 2.2.x kernels. Since I use lilo, it was a simple matter of adding a couple of lines to the right entry in /etc/lilo.conf: Hmm. I use grub and I didn't have to do anything different to setup the 2.4 kernels. I believe that kernel-package has now some support for grub, but I don't know the details. I just did update-grub and modify the entries as necessary. Grub seems to be an easier method than lilo in this situation, as it is in others. Here is what the entry on one of my machines looks (created by update-grub; I just modified the root from (hd0,0) and the root from /dev/hda1.) title Debian GNU/Linux, kernel 2.4.17 root(hd0,5) kernel /boot/vmlinuz-2.4.17 root=/dev/hda6 ro savedefault title Debian GNU/Linux, kernel 2.4.17 (recovery mode) root(hd0,5) kernel /boot/vmlinuz-2.4.17 root=/dev/hda6 ro single savedefault Faheem.
Re: Installing kernel-image-2.4.17-k7
#include hallo.h Bill Moseley wrote on Wed Feb 27, 2002 um 06:41:05AM: So, I'd like to avoid the kernel panic this time with the kernel-image-2.4.17-k7 package. What steps do I need to take to make sure I will end up with a bootable image? Someone mentioned that moving to the more modular 2.4 kernel might have been the problem - something about not setting up initrd? Edit /etc/lilo.conf. Locate the line containing = /vmlinuz. Insert a line after that with initrd = /initrd.img. I'd also like to also use lilo.conf to be able to select which kernel (I can figure this out, but I mention it as I'm not sure if just apt-get'ing the kernel-image will do this by default). It will set the /vmlinuz symlink to point to the recently installed image. /vmlinuz is normally used in lilo.conf as the default kernel. And /vmlinuz.old as the previous kernel. Anyway, last time I just apt-get install kernel-image-2.4.17-k7, but perhaps that was not enough. I poked around looking for docs, but mostly found info about compiling my own. Any pointers? If you are not sure, use the kernel-image-2.4.17-bf2.4 package. It is compiled without initrd and should have the same boot behaviour as 2.2.x kernels. Gruss/Regards, Eduard. -- Wenn einer träumt, bleibt es ein Traum. Wenn viele träumen, beginnt der Traum, Wirklichkeit zu werden.
Re: Installing kernel-image-2.4.17-k7
At 12:04 PM 02/27/02 -0800, Stan Kaufman wrote: I just installed 2.4.17 on a new woody box, which involved an upgrade from the 2.2.14 potato system my floppy install disks created. The kernel-image package provided clear notice during installation that the bootloader needs to be altered in order to find the new image, since it's handled differently from the 2.2.x kernels. What's handled differently? Since I use lilo, it was a simple matter of adding a couple of lines to the right entry in /etc/lilo.conf: image=/vmlinuz label=Linux initrd=/initrd.img root=/dev/hda2 # wherever your boot partition is read-only etc etc... You'd have to handle this differently with different bootloaders no doubt; perhaps sid now does things differently too (?). Anyway, once you've altered lilo.conf and run lilo, the kernel install runs flawlessly. Ok. Did you leave both kernels in you lilo.conf? I'm also a bit confused by: http://www.debian.org/doc/manuals/quick-reference/ch-kernel.en.html#s-kernel-net That's been my biggest question -- I'm not clear about what I need to do differently for the modularized kernel. The other question that's been bugging me is how I can have one /etc/modules that works for two different kernels. Thanks again for all the help! My boss has been keeping me from the more important tasks of trying to get this kernel built today. Geeze! -- Bill Moseley mailto:[EMAIL PROTECTED]
Re: Installing kernel-image-2.4.17-k7
Bill Moseley [EMAIL PROTECTED] writes: At 12:04 PM 02/27/02 -0800, Stan Kaufman wrote: I just installed 2.4.17 on a new woody box, which involved an upgrade from the 2.2.14 potato system my floppy install disks created. The kernel-image package provided clear notice during installation that the bootloader needs to be altered in order to find the new image, since it's handled differently from the 2.2.x kernels. What's handled differently? Since I use lilo, it was a simple matter of adding a couple of lines to the right entry in /etc/lilo.conf: image=/vmlinuz label=Linux initrd=/initrd.img root=/dev/hda2 # wherever your boot partition is read-only etc etc... You'd have to handle this differently with different bootloaders no doubt; perhaps sid now does things differently too (?). Anyway, once you've altered lilo.conf and run lilo, the kernel install runs flawlessly. Ok. Did you leave both kernels in you lilo.conf? I'm also a bit confused by: http://www.debian.org/doc/manuals/quick-reference/ch-kernel.en.html#s-kernel-net That's been my biggest question -- I'm not clear about what I need to do differently for the modularized kernel. The other question that's been bugging me is how I can have one /etc/modules that works for two different kernels. Thanks again for all the help! My boss has been keeping me from the more important tasks of trying to get this kernel built today. Geeze! Personally, I'd scrap the initrd stuff and compile your own kernels, building in the necessary disk adapter and file system for your box, i.e., not as modules but directly built into the kernel. The purpose of initrd, in general, is to compile all the disk and file systems drivers as modules and then they don't have to supply a bunch of different boot images for different configurations during an initial install (because building all the disk adapter drivers and file systems directly into the kernel made it too large to fit on a floppy). initrd certainly serves a useful purpose for installation sets, but I find my system boots slower with it and I always build my own kernels anyway so I scrapped it. Gary
Re: installing kernel-debs
Joerg Johannes wrote: Hello list I have, in the last few weeks, compiled a lot of kernels (with make-kpkg) Well, I have installed these kernel-image-blah.deb's, but without removing the old ones. dpkg -l shows ii kernel-image-2. # -- dpk -l does not show more of the package version ii kernel-image-2. ii kernel-image-2. ii kernel-image-2. ... How can I safely remove the old ones (whose files were overwritten by the newer ones) ? I could make a 2.4.5 kernel and remove all the 2.4.3.deb's, but will this work? won't dpkg complain about files that are not there but should be there? joerg OK, Thanks to everyone. COLUMS=200 dpkg | grep kernel-image helped me so that could apt-get remove all the old kernel packages. joerg -- Did you know that if you play a Windows 2000 cd backwards, you will hear the voice of Satan? That's nothing! If you play it forward, it'll install Windows 2000.
Re: installing kernel-debs
On Fri, Jul 20, 2001 at 01:37:09PM +0200, Joerg Johannes wrote: I have, in the last few weeks, compiled a lot of kernels (with make-kpkg) Well, I have installed these kernel-image-blah.deb's, but without removing the old ones. dpkg -l shows ii kernel-image-2. # -- dpk -l does not show more of the package version ii kernel-image-2. ii kernel-image-2. ii kernel-image-2. ... This is broken dpkg behaviour. You can work around it by typing: COLUMS=200 dpkg -l foobar How can I safely remove the old ones (whose files were overwritten by the newer ones) ? No files should be overwritten, or else there is a bug in kernel-package. I could make a 2.4.5 kernel and remove all the 2.4.3.deb's, but will this work? won't dpkg complain about files that are not there but should be there? Unless you know how to play with flavours, you will not have multiple instances of the same kernel version installed on your system. What files do you mean that dpkg should complain about? Every kernel-image package has its own files, that must not be overwritten by any other packages. If you try to install a kernel-image of a kernel version that already has a kernel-image installed, then dpkg will treat the new install as an upgrade and cleanly replace all files. Cheers, Joost
Re: installing kernel-debs
On Fri, 20 Jul 2001, Joerg Johannes wrote: Hello list I have, in the last few weeks, compiled a lot of kernels (with make-kpkg) Well, I have installed these kernel-image-blah.deb's, but without removing the old ones. dpkg -l shows ii kernel-image-2. # -- dpk -l does not show more of the package version ii kernel-image-2. ii kernel-image-2. ii kernel-image-2. ... How can I safely remove the old ones (whose files were overwritten by the newer ones) ? I could make a 2.4.5 kernel and remove all the 2.4.3.deb's, but will this work? won't dpkg complain about files that are not there but should be there? Perhaps this is evil, but it might workt: # dpkg --get-selections installeddebs edit the file and remove all old kernel-images # echo installeddebs | dpkg --set-selections Greetz, Sebastiaan
Re: installing kernel-debs
[EMAIL PROTECTED] wrote: Hello list I have, in the last few weeks, compiled a lot of kernels (with make-kpkg) Well, I have installed these kernel-image-blah.deb's, but without removing the old ones. dpkg -l shows ii kernel-image-2. # -- dpk -l does not show more of the package version 'COLUMNS=200 dpkg -l' (at least on unstable). That's part of the package *name*, though, not the version. You can just purge the old ones. The files won't have been overwritten, or at least if they were you would have been warned about it at the time and can go ahead and purge things now. dselect will let you see the full names and will let you purge them easily (hit '_'). -- Colin Watson [EMAIL PROTECTED]
Re: installing kernel-debs
Joerg, By a coincidence, I had opened a bug yesterday on this very topic. Here is the link which also contains the maintainer response. Regards, Jor-el On Fri, 20 Jul 2001, Joerg Johannes wrote: Hello list I have, in the last few weeks, compiled a lot of kernels (with make-kpkg) Well, I have installed these kernel-image-blah.deb's, but without removing the old ones. dpkg -l shows ii kernel-image-2. # -- dpk -l does not show more of the package version ii kernel-image-2. ii kernel-image-2. ii kernel-image-2. ... How can I safely remove the old ones (whose files were overwritten by the newer ones) ? I could make a 2.4.5 kernel and remove all the 2.4.3.deb's, but will this work? won't dpkg complain about files that are not there but should be there? joerg -- Did you know that if you play a Windows 2000 cd backwards, you will hear the voice of Satan? That's nothing! If you play it forward, it'll install Windows 2000. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: installing kernel-debs
Joerg, Of course, it would be good if I had included the link too, wouldnt it? http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=105964repeatmerged=yes Regards, Jor-el On Fri, 20 Jul 2001, Jor-el wrote: Joerg, By a coincidence, I had opened a bug yesterday on this very topic. Here is the link which also contains the maintainer response. Regards, Jor-el On Fri, 20 Jul 2001, Joerg Johannes wrote: Hello list I have, in the last few weeks, compiled a lot of kernels (with make-kpkg) Well, I have installed these kernel-image-blah.deb's, but without removing the old ones. dpkg -l shows ii kernel-image-2. # -- dpk -l does not show more of the package version ii kernel-image-2. ii kernel-image-2. ii kernel-image-2. ... How can I safely remove the old ones (whose files were overwritten by the newer ones) ? I could make a 2.4.5 kernel and remove all the 2.4.3.deb's, but will this work? won't dpkg complain about files that are not there but should be there? joerg -- Did you know that if you play a Windows 2000 cd backwards, you will hear the voice of Satan? That's nothing! If you play it forward, it'll install Windows 2000. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing kernel sources on alternative partition problem
On 8 Nov 2000, Hubert Chan wrote: Kieren Diment [EMAIL PROTECTED] writes: Hi there, I have a slightly obscure problem recompiling my potato kernel-source-2.2.17 on a P100 laptop. I have a disk space problem and therefore tried to unpack the kernel sources on my other partition, which is a now redundant vfat partition that had win 95 on it. When I extract the tarball, I get the following error message: tar: kernel-source-2.2.17/include/asm: Cannot create symlink to asm-i386': Operation not permitted tar: Error exit delayed from previous errors Hmm. Does vfat even support symlinks? That may be the problem. If you don't No it does not. AFAIK, the Linux kernel needs a UNIX file system to compile.
Re: Installing kernel sources on alternative partition problem
Kieren Diment [EMAIL PROTECTED] writes: Hi there, I have a slightly obscure problem recompiling my potato kernel-source-2.2.17 on a P100 laptop. I have a disk space problem and therefore tried to unpack the kernel sources on my other partition, which is a now redundant vfat partition that had win 95 on it. When I extract the tarball, I get the following error message: tar: kernel-source-2.2.17/include/asm: Cannot create symlink to asm-i386': Operation not permitted tar: Error exit delayed from previous errors Hmm. Does vfat even support symlinks? That may be the problem. If you don't need the partition, you should try reformatting to ext2fs. (Or maybe, is there a tool out there that will convert the partition?) Well, what it's trying to do is symlink kernel-source-2.2.17/include/asm to kernel-source-2.2.17/include/asm-i386. I think it needs that to be a symlink, and I don't think you can just copy the directory (although it probably wouldn't hurt to try). Hubert -- | --- | / --+-- | / ___|___Hubert Chan [EMAIL PROTECTED] | \ | _|_ | |__| |__|__|GCS/M d- s:- a-- C++ UL+() P++ L++ E++ W++ N++ o? || K? w--- O++ M- V- PS-- PE+++ Y+ PGP+ t+ 5 X R- tv+ b+ | / | \ DI D G e++ h! !r !y | / | \ || -- http://www.crosswinds.net/~hackerhue/ PGP/GnuPG fingerprint: 6CC5 822D 2E55 494C 81DD 6F2C 6518 54DF 71FD A37F Key can be found at http://www.crosswinds.net/~hackerhue/hackerhue.asc Experience the Power to Change -- http://www.powertochange.org/ CAUCE member -- Stop Spam! -- http://www.cauce.org/ Linux: Where do you want to go tomorrow? -- http://www.linux.com/ International Alliance for Compatible Technology -- http://www.iact.net/
Re: Installing kernel sources
CHEONG, Shu Yang [Patrick] [EMAIL PROTECTED] writes: $tar xvf kernel-source-2.2.17 Nowadays it is: tar -xvIf kernel-source-2.2.17.tar.bz2 (note the `I' in between, it is to unpack the bzipped archive). Greetings, joachim
RE: Installing kernel sources
$apt-get install kernel-source-2.2.17... However, I normally use dselect... Once completed cd to /usr/src...and you will find a file kernel-source-2.2.17.bz2...just $bzunzip2 kernel-source-2.2.17.bz2 you should now have a file kernel-source-2.2.17.tar. Do $tar xvf kernel-source-2.2.17 and you should see the file contents flyby on your screen. Since the generic place for keeping the kernel sources is in /usr/src/linux, crate a symlink from /usr/src/linux to /usr/src/kernel-source-2.2.17 using the following $ln -s /usr/src/kernel-source-2.2.17 /usr/src/linux Now cd into /usr/src/linux and continue with make config (or menuconfig or xconfig), make dep, make modules, make modules_install and make bzImageI suggest you read the man pages for compiling the kernel HTH Patrick Cheong Information Systems Assurance Measat Broadcast Network Systems e-mail: mailto:[EMAIL PROTECTED] Visit us at: http://www.astro.com.my -Original Message- From: Ray Percival [SMTP:[EMAIL PROTECTED] Sent: Friday, October 20, 2000 8:15 AM To: debian-user@lists.debian.org Subject: Installing kernel sources Does anyone out there have a step by step to install kernel sources on 2.2. Thanks very much -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: Installing kernel sources
S.Salman Ahmed wrote: RP == Ray Percival [EMAIL PROTECTED] writes: RP Does anyone out there have a step by step to install kernel RP sources on 2.2. Thanks very much RP Installing kernel sources is as easy as 1, 2! 1) Download source for the current stable kernel (2.2.17) from the Linux Kernel Archives site: http://www.kernel.org 2) Untar and extract in /usr/src: tar Ixvf linux-2.2.17.tar.bz2 OR tar zxvf linux-2.2.17.tar.gz if you downloaded the gzipped tarball And you are done. Optionally you may want to create a symlink in /usr/src: ln -s linux-2.2.17 linux Then cd into /usr/src/linux and go nuts! -- Salman Ahmed ssahmed AT pathcom DOT com -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null after getting the _tarball_ ready (as described above), you may want to use kernel-package to rock your kernel. (apt-get install kernel-package.) then: # make menuconfig; make-kpkg clean; make-kpkg --revision=custom.1.0 kernel_image (make sure you have ncurses (if you want to use menuconfig.) (apt-get install ncurses) when it's done, install your newly rocked kernel: # cd .. # dpkg -i kernel* reboot. (before you start, you may want to have a boot disk handy.) good luck. bentley taylor. (potato on 2.2.17) //
Re: Installing kernel sources
On Thu, Oct 19, 2000 at 06:15:24PM -0600, Ray Percival wrote: Does anyone out there have a step by step to install kernel sources on 2.2. Thanks very much o uname -a, to determine which kernel version you are currently running. o apt-get install kernel-source-2.x.x, where x.x is determined by uname -a. Or, you could just install the latest if you wish. o do like the other message replies said about creating the link to /usr/src/linux I'm not sure you need a deb-src line in your /etc/apt/sources file or not. (Is the kernel source package really considered a source deb?) If the apt-get fails, then you need to add the following line as a minimum to /etc/apt/sources: deb-src http://http.us.debian.org/debian/ potato main John -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- We host web sites: http://www.skink.net buy my stuff: http://cgi6.ebay.com/aw-cgi/ebayISAPI.dll?ViewListedItemsLinkButtons[EMAIL PROTECTED]
Re: Installing kernel sources
cls--colo spgs wrote: S.Salman Ahmed wrote: RP == Ray Percival [EMAIL PROTECTED] writes: RP Does anyone out there have a step by step to install kernel RP sources on 2.2. Thanks very much RP Installing kernel sources is as easy as 1, 2! 1) Download source for the current stable kernel (2.2.17) from the Linux Kernel Archives site: http://www.kernel.org 2) Untar and extract in /usr/src: tar Ixvf linux-2.2.17.tar.bz2 OR tar zxvf linux-2.2.17.tar.gz if you downloaded the gzipped tarball And you are done. Optionally you may want to create a symlink in /usr/src: ln -s linux-2.2.17 linux Then cd into /usr/src/linux and go nuts! -- Salman Ahmed ssahmed AT pathcom DOT com -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null after getting the _tarball_ ready (as described above), you may want to use kernel-package to rock your kernel. (apt-get install kernel-package.) then: # make menuconfig; make-kpkg clean; make-kpkg --revision=custom.1.0 kernel_image (make sure you have ncurses (if you want to use menuconfig.) (apt-get install ncurses) when it's done, install your newly rocked kernel: # cd .. # dpkg -i kernel* [snip] # lilo [snip] reboot. (before you start, you may want to have a boot disk handy. good luck. bentley taylor. (potato on 2.2.17) // -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
RE: Installing kernel sources
Ray wrote: Does anyone out there have a step by step to install kernel sources on 2.2. Thanks very much The other couple of replies referred to the more 'generic' kernel compile instructions. If you want to do it the 'Debian way', I would recommend checking out the 2.2 install guide section 8.5 at http://www.debian.org/releases/2.2/i386/ch-post-install.en.html#s-kernel-bak ing This method will probably save you trouble later on when you try and work out why apt-get decided to replace your custom kernel with its own one! - Chris
Re: installing kernel
Hi, I've been using debian slink and the 2.0.36 kernel for a while now, and have just compiled the 2.2.4 kernel. I have my linux partition (ext2fs) on hda2. When booting the new kernel, it tells me something like installed root fiesystem (ext. 2) kernel panic: can't find init. try passing init= as kernel option. Init is sitting in /sbin/init, where it should. Anyway, even passing init= as kernel command line via lilo to the kernel doesn't make any difference. i have two ideas: 1) all older kernel have a bug in the ext2-fs-driver, which could make your partition unreadable for new kernels, but to be honest, i don't know, which effects the bug has. 2) are you sure, that you mounted the right partition? did you try the root= option? note, that everything, that comes before init= on the kernel command line is dropped (at least by some kernels). btw: kernel 2.2.4 is not out yet - and won't be for the next three months, from what i've heard. -- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! -- Linux - the last service pack you'll ever need.
Re: installing kernel
btw: kernel 2.2.4 is not out yet - and won't be for the next three months, from what i've heard. ehhhm - bullshit! i confused 2.4.0 with 2.2.4. *shame* -- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! -- Linux - the last service pack you'll ever need.
Re: installing kernel
On Fri, May 12, 2000 at 12:22:17PM +0200, Oswald Buddenhagen wrote: Hi, I've been using debian slink and the 2.0.36 kernel for a while now, and have just compiled the 2.2.4 kernel. I have my linux partition Hi, as far as I know there were some nasty problems in early 2.2.x kernels. I think it would be safer to use the current stable 2.2.15 kernel. cheers, Jens
Re: installing kernel
Yep, everything I've read or heard suggests if your going to use 2.2, use 2.2.14+ kernels. I'm now running 2.2.15 (pre19-1) with no probs whatsoever. Cheers, Corey Popelier http://members.dingoblue.net.au/~pancreas Work Email: [EMAIL PROTECTED] On Fri, 12 May 2000, Jens Guenther wrote: On Fri, May 12, 2000 at 12:22:17PM +0200, Oswald Buddenhagen wrote: Hi, I've been using debian slink and the 2.0.36 kernel for a while now, and have just compiled the 2.2.4 kernel. I have my linux partition Hi, as far as I know there were some nasty problems in early 2.2.x kernels. I think it would be safer to use the current stable 2.2.15 kernel. cheers, Jens -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: installing kernel
kernel panic: can't find init. try passing init= as kernel option. Init is sitting in /sbin/init, where it should. Anyway, even passing init= as kernel command line via lilo to the kernel doesn't make any difference. I've had this happen to me on numerous occasions, even with 2.2.14 kernels. 'Twas only recently that I learned what was causing it... you need to configure your new kernel to include ELF binaries support. The one you need to enable (and not as a module) is CONFIG_BINFMT_ELF From the help on kernel support for MISC binaries, it sounds like you don't need the ELF binaries support. The help states If you say Y here, you won't need 'Kernel support for Java binaries' or 'Kernel support for Linux/Intel ELF binaries' as this is a more general solution. Bur try adding the BINFMT_ELF support, recompiling, and seeing if that helps at all. Good luck! - Colin McMillen
Re: installing kernel
Corey Popelier wrote: Yep, everything I've read or heard suggests if your going to use 2.2, use 2.2.14+ kernels. I'm now running 2.2.15 (pre19-1) with no probs whatsoever. i'm running 2.0.36 (slink kernel? with potato packages) without any problems whatsoever. until i run into problems and it's too late, what motivation do i have to go thru the cold sweats of replacing my kernel? -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- Their is five errers in this sentance.
Re: installing kernel
To learn more about Linux. To make the kernel smaller so you have shorter boot times. Those are a couple of reasons to do so. I bet I could come up with more but I have to eat:) kent w trillich wrote: Corey Popelier wrote: Yep, everything I've read or heard suggests if your going to use 2.2, use 2.2.14+ kernels. I'm now running 2.2.15 (pre19-1) with no probs whatsoever. i'm running 2.0.36 (slink kernel? with potato packages) without any problems whatsoever. until i run into problems and it's too late, what motivation do i have to go thru the cold sweats of replacing my kernel? -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- Their is five errers in this sentance.
