testing distribution kernel upgrade question when mixing signed and unsigned
note: DO NOT DO THIS ON A PRODUCTION SYSTEM. last week i was running an unsigned kernel and went to upgrade it to a signed version and it came back with asking me about removing a running kernel. in recent times that hasn't been and issue so i aborted the install and then downloaded the desired kernel and installed it by hand myself. in the process of doing that i screwed up a few links but was able to recover since i had a bootable stable partition. i eventually got the unsigned kernel version removed and replaced by the desired signed version. todays upgrade went smoothlyy as expected. the question is for someone who has a system they're willing to play with and see if you can replicated my problem or not as i'd like to file a bug if there is indeed a problem. songbird
Re: Kernel upgrade question
On Fri, Sep 14, 2007 at 22:48:42 -0700, Bill Moseley wrote: On Fri, Sep 14, 2007 at 08:03:25PM -0700, Bill Moseley wrote: I've got one machine running Debian Sid that has not be upgraded in a month or so. It's running a custom kernel I built who-knows-when (2.6.6). Frankly, I can't remember the reason for the custom kernel. So am I wedged? $ sudo apt-get -f install Preparing to replace libc6 2.5-9+b1 (using .../libc6_2.6.1-4_i386.deb) ... WARNING: POSIX threads library NPTL requires kernel version 2.6.8 or later. If you use a kernel 2.4, please upgrade it before installing glibc. Ok, so try and install a new Kernel: $ sudo apt-get install linux-image-k7 Reading package lists... Done Building dependency tree... Done You might want to run `apt-get -f install' to correct these: The following packages have unmet dependencies: kernel-patch-xfs: Depends: grep-dctrl libc6-dev: Depends: libc6 (= 2.6.1-4) but 2.5-9+b1 is to be installed linux-image-k7: Depends: linux-image-2.6-k7 but it is not going to be installed locales: Depends: glibc-2.6-1 E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). You could try something like this: - boot a Debian(-based) live/rescue CD with a new enough kernel - chroot into your normal installation - update libc6 et al. - install the new kernel image - verify that grub knows about the new kernel - reboot your system with the new kernel image I think this should work, but I never tried anything like that myself, therefore I cannot guarantee anything. -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Kernel upgrade question
I've got one machine running Debian Sid that has not be upgraded in a month or so. It's running a custom kernel I built who-knows-when (2.6.6). Frankly, I can't remember the reason for the custom kernel. But, I'm a bit concerned because I probably compiled most features into the kernel and not as modules. Anyway, the upgrade is asking to upgrade glibc and says: WARNING: POSIX threads library NPTL requires kernel version 2.6.8 or later. If you use a kernel 2.4, please upgrade it before installing glibc. I'm not clear on the image to install. Is linux-image-2.6-k7 a dummy package for the most recent image (linux-image-2.6.22-2-k7)? So, linux-image-2.6-k7 is the correct kernel? Here's my modules, cpuinfo, and lspci -- just in case anything jumps out that might be a problem. $ lsmod Module Size Used by mga 103792 0 lp 10564 0 uhci_hcd 30672 0 ohci1394 34756 0 ieee1394 108340 1 ohci1394 w83627hf 28612 0 eeprom 7752 0 i2c_sensor 2944 2 w83627hf,eeprom i2c_isa 2048 0 i2c_viapro 7052 0 i2c_core 23044 5 w83627hf,eeprom,i2c_sensor,i2c_isa,i2c_viapro $ cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 6 model : 6 model name : AMD Athlon(tm) Processor stepping: 2 cpu MHz : 1150.591 cache size : 256 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mp mmxext 3dnowext 3dnow bogomips: 2260.99 $ lspci 00:00.0 Host bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333] 00:01.0 PCI bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333 AGP] 00:06.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 07) 00:06.1 Input device controller: Creative Labs SB Live! Game Port (rev 07) 00:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 00:09.0 FireWire (IEEE 1394): Texas Instruments TSB12LV26 IEEE-1394 Controller (Link) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8233 PCI to ISA Bridge 00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 00:11.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 1b) 00:11.3 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 1b) 00:11.4 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 1b) 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 10) 01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G550 AGP (rev 01) -- Bill Moseley [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel upgrade question
On Fri, Sep 14, 2007 at 08:03:25PM -0700, Bill Moseley wrote: I've got one machine running Debian Sid that has not be upgraded in a month or so. It's running a custom kernel I built who-knows-when (2.6.6). Frankly, I can't remember the reason for the custom kernel. So am I wedged? $ sudo apt-get -f install Preparing to replace libc6 2.5-9+b1 (using .../libc6_2.6.1-4_i386.deb) ... WARNING: POSIX threads library NPTL requires kernel version 2.6.8 or later. If you use a kernel 2.4, please upgrade it before installing glibc. Ok, so try and install a new Kernel: $ sudo apt-get install linux-image-k7 Reading package lists... Done Building dependency tree... Done You might want to run `apt-get -f install' to correct these: The following packages have unmet dependencies: kernel-patch-xfs: Depends: grep-dctrl libc6-dev: Depends: libc6 (= 2.6.1-4) but 2.5-9+b1 is to be installed linux-image-k7: Depends: linux-image-2.6-k7 but it is not going to be installed locales: Depends: glibc-2.6-1 E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). -- Bill Moseley [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Kernel upgrade question: apt-kpkg??
I've upgraded my kernel before, with the ususal procedures. I noticed in Debian Planet http://www.debianplanet.org/debianplanet/sections.php?op=viewarticleartid=4 the suggestion that it is better after using make menuconfig or make config to make a kernel package from the kernel_image, using make-kpkg kernel_image, and then dpkg -i on the package that is created. I can see how this would be useful if I had a number of identical boxes. The suggestion is that this is safer and easier even for users of single Linux boxes. Before I upgrade to 2.4.1, is there any merit to this? It seems like the extra steps wouldn't be easier, especially if I have to make changes to the kernel_image. Any idea how this might be safer ? Thanks, Glen
Re: Kernel upgrade question: apt-kpkg??
On Sat, Feb 24, 2001 at 11:51:43AM -0500, Glen Snyder wrote: I've upgraded my kernel before, with the ususal procedures. I noticed in Debian Planet http://www.debianplanet.org/debianplanet/sections.php?op=viewarticleartid=4 the suggestion that it is better after using make menuconfig or make config to make a kernel package from the kernel_image, using make-kpkg kernel_image, and then dpkg -i on the package that is created. I can see how this would be useful if I had a number of identical boxes. The suggestion is that this is safer and easier even for users of single Linux boxes. Before I upgrade to 2.4.1, is there any merit to this? It seems like the extra steps wouldn't be easier, especially if I have to make changes to the kernel_image. Any idea how this might be safer ? Thanks, There are less steps doing it the debian way. Take a look at - http://www.debian.org/doc/FAQ/ch-kernel.html I've done it both ways. Single system or multiple, personally I like the debian way. Your choice. kent -- From seeing and seeing the seeing has become so exhausted First line of The Panther - R. M. Rilke
Re: Kernel upgrade question: apt-kpkg??
Hi Glen, I have used both. I really like the dpkg approach better then the line/by/line approach. The way I look at it, is that I'm lucky enough to be running debain and get to play with these killer tools :) I never used the xconfig tool here. but make menuconfig has worked quite well, and it's nice since I can easily do this on remote boxes via a slow 56k modem. tatah On Saturday 24 February 2001 08:51, Glen Snyder wrote: I've upgraded my kernel before, with the ususal procedures. I noticed in Debian Planet http://www.debianplanet.org/debianplanet/sections.php?op=viewarticleartid= 4 the suggestion that it is better after using make menuconfig or make config to make a kernel package from the kernel_image, using make-kpkg kernel_image, and then dpkg -i on the package that is created. I can see how this would be useful if I had a number of identical boxes. The suggestion is that this is safer and easier even for users of single Linux boxes. Before I upgrade to 2.4.1, is there any merit to this? It seems like the extra steps wouldn't be easier, especially if I have to make changes to the kernel_image. Any idea how this might be safer ? Thanks, Glen -- Jaye Inabnit, ARS ke6sls e-mail: [EMAIL PROTECTED] 707-442-6579 h/m 707-268-4074 http://www.qsl.net/ke6slsICQ# 12741145 This mail composed with kmail on kde on X on linux warped by debian If it's stupid, but works, it ain't stupid.
