Re: kernel not upgraded to wheezy
On 01 Jul 2013, Joel Rees wrote: Although I have installed the 3.9 kernel and it is present in /boot/grub/menu.lst, it never appears in the menu when I boot. Repeated runs of update-grub don't fix this. I reverted to grub-legacy because of configuration problems with grub2 but that didn't allow the new kernel to appear either. grub2 of course ignores menu.lst, but you say you are using legacy grub. I have been considering going back to legacy grub, since chaining and multibooting in general was easier back then. But it was almost ten years ago that I was mixing BSDs and Linuxes and solaris (6 OS mulitboot, at one point) on the one box. I think legacy was no longer doing that nicely when grub2 started being used. Update-grub with grub2 finds pretty much all my Linux kernels on all my Linux OSses. Finds them, but can't boot them all. I've recently had Mint and Fedora in a spare partition on the first drive, but it would not boot those with any stability. Sometime, I need to find out why. -- Joel Rees For some reason a recent upgrade of grub2 led to a failed configure. I found other people on Google, mainly ubuntu users,with a similar problem but no obvious solution. I purged grub2 and reinstalled, but the same error appeared. That was why I reverted to legacy grub, which at least allowed grub-mkconfig to work but still the new kernel did not appear at boot. -- Anthony Campbell - a...@acampbell.org.uk http://www.acupuncturecourse.org.uk http://www.smashwords.com/profile.view/acampbell https://itunes.apple.com/ca/artist/anthony-campbell/id73235412 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130702070959.gh2...@acampbell.org.uk
Re: kernel not upgraded to wheezy
On 02 Jul 2013, Anthony Campbell wrote: For some reason a recent upgrade of grub2 led to a failed configure. I found other people on Google, mainly ubuntu users,with a similar problem but no obvious solution. I purged grub2 and reinstalled, but the same error appeared. That was why I reverted to legacy grub, which at least allowed grub-mkconfig to work but still the new kernel did not appear at boot. I've just discovered that the new kernel is there but you have to select Advanced during the boot sequence. It is then one of the options offered. AC -- Anthony Campbell - a...@acampbell.org.uk http://www.acupuncturecourse.org.uk http://www.smashwords.com/profile.view/acampbell https://itunes.apple.com/ca/artist/anthony-campbell/id73235412 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130702174100.ga2...@acampbell.org.uk
Re: kernel not upgraded to wheezy
On 01 Jul 2013, Andrei POPESCU wrote: 1. Since the kernel packages have different names they are not upgrades in the sense of the package manager (like installing package foo version 1.2.3 to upgrade from foo version 0.1.2 is). If you want/need this to be handled by the package manager have a look at the linux-image-flavour packages. 2. The method of installing is irrelevant, the kernel will not be used until you reboot anyway ;) Although I have installed the 3.9 kernel and it is present in /boot/grub/menu.lst, it never appears in the menu when I boot. Repeated runs of update-grub don't fix this. I reverted to grub-legacy because of configuration problems with grub2 but that didn't allow the new kernel to appear either. AC -- Anthony Campbell - a...@acampbell.org.uk http://www.acupuncturecourse.org.uk http://www.smashwords.com/profile.view/acampbell https://itunes.apple.com/ca/artist/anthony-campbell/id73235412 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130701070858.gb2...@acampbell.org.uk
Re: kernel not upgraded to wheezy
On Mon, Jul 1, 2013 at 12:47 PM, Andrei POPESCU andreimpope...@gmail.comwrote: On Lu, 01 iul 13, 09:19:31, Joel Rees wrote: Short story: upgraded squeeze to wheezy, kernel did not. But OS seems to run, so I'm using synaptic to install the kernel. (I know I should use apt-cache and apt-get, but I'm lazy and trying to do some other work that needs to be done today.) Wondering why, wondering how big a hole-in-my-foot I'm going to end up with. We'll see. Wondering if this has happened to anyone else. ... Comments? Two: 1. Since the kernel packages have different names they are not upgrades in the sense of the package manager (like installing package foo version 1.2.3 to upgrade from foo version 0.1.2 is). So, in the case of the smaller install, the dependencies picked up the kernel. But in the case of the larger install, the dependencies somehow got clipped without registering an actual hold anywhere. Ouch. If you want/need this to be handled by the package manager have a look at the linux-image-flavour packages. Yeah, that was what I used to install the new kernel. 2. The method of installing is irrelevant, the kernel will not be used until you reboot anyway ;) You should only avoid synaptic when the upgrade may involve parts of your GUI infrastructure (*dm, DE/WM, etc.), otherwise I'm sure it might be a viable alternative for the dist-upgrade. Okay, I see that I didn't explicitly say I took the two step approach. I did, and the kernel was not pulled in at either apt-get upgrade or apt-get diist-upgrade. (Got about 500 MB of stuff on upgrade, another 1500 MB on dist-upgrade, left it going overnight, checking progress when I got up to chase my son to bed, etc. Probably missed some important question while I was asleep.) -- Joel Rees
Re: kernel not upgraded to wheezy
On Mon, Jul 1, 2013 at 4:08 PM, Anthony Campbell a...@acampbell.org.ukwrote: On 01 Jul 2013, Andrei POPESCU wrote: 1. Since the kernel packages have different names they are not upgrades in the sense of the package manager (like installing package foo version 1.2.3 to upgrade from foo version 0.1.2 is). If you want/need this to be handled by the package manager have a look at the linux-image-flavour packages. 2. The method of installing is irrelevant, the kernel will not be used until you reboot anyway ;) Although I have installed the 3.9 kernel and it is present in /boot/grub/menu.lst, it never appears in the menu when I boot. Repeated runs of update-grub don't fix this. I reverted to grub-legacy because of configuration problems with grub2 but that didn't allow the new kernel to appear either. grub2 of course ignores menu.lst, but you say you are using legacy grub. I have been considering going back to legacy grub, since chaining and multibooting in general was easier back then. But it was almost ten years ago that I was mixing BSDs and Linuxes and solaris (6 OS mulitboot, at one point) on the one box. I think legacy was no longer doing that nicely when grub2 started being used. Update-grub with grub2 finds pretty much all my Linux kernels on all my Linux OSses. Finds them, but can't boot them all. I've recently had Mint and Fedora in a spare partition on the first drive, but it would not boot those with any stability. Sometime, I need to find out why. -- Joel Rees
kernel not upgraded to wheezy
Short story: upgraded squeeze to wheezy, kernel did not. But OS seems to run, so I'm using synaptic to install the kernel. (I know I should use apt-cache and apt-get, but I'm lazy and trying to do some other work that needs to be done today.) Wondering why, wondering how big a hole-in-my-foot I'm going to end up with. We'll see. Wondering if this has happened to anyone else. Long story: I have an AMD sempron 32 bit CPU, three disks. Currently only two OSses, both Debian, both were squeeze last week. One is on the first hard disk, it controls the dual-boot process. (This was for when I was mostly running Fedora and sometimes playing with other stuff. I still plan to play with other stuff, if I can figure out how to chain grub to non-MSWindows OSses.) The other is the working OS on the second disk, both the family accounts and some of my work accounts. The first disk is a very small install, single partition, minimal set of apps. I upgraded it using apt-get update with no problems. (That I've noticed yet. Haven't tried sound and some other not-so-simple stuff.) In other words, I got into /etc/apt/sources.list and commented out the squeeze lines and added wheezy lines, per the documented procedures at http://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html Since that went fairly well, I tried the same thing on my working OS. Lots of things show that I need to tune settings, I expected that. I may have missed it in the middle of the night, but I didn't see any messages about not being able to install the kernel. No holds show up anywhere, either. While restoring the PAM settings that keep my kids from logging in after 11:00 at night (not the right solution, I know.), I noticed that the kernel was still at 2.6.32. No sign of 3.2 in /boot or anywhere. Synaptic says it's not loaded. So, I'm just doing the point-and-click install of the 3.2 kernel, hoping nothing too strange happens. Comments? -- Joel Rees
Re: kernel not upgraded to wheezy
FWIW, upgrading the kernel via synaptic seems to have worked. The shell is much more responsive, and doesn't get strange video glitches like it had been getting since the upgrade to wheezy. Still need to check the rest of /etc. On Mon, Jul 1, 2013 at 9:19 AM, Joel Rees joel.r...@gmail.com wrote: Short story: upgraded squeeze to wheezy, kernel did not. But OS seems to run, so I'm using synaptic to install the kernel. (I know I should use apt-cache and apt-get, but I'm lazy and trying to do some other work that needs to be done today.) Wondering why, wondering how big a hole-in-my-foot I'm going to end up with. We'll see. Wondering if this has happened to anyone else. Long story: I have an AMD sempron 32 bit CPU, three disks. Currently only two OSses, both Debian, both were squeeze last week. One is on the first hard disk, it controls the dual-boot process. (This was for when I was mostly running Fedora and sometimes playing with other stuff. I still plan to play with other stuff, if I can figure out how to chain grub to non-MSWindows OSses.) The other is the working OS on the second disk, both the family accounts and some of my work accounts. The first disk is a very small install, single partition, minimal set of apps. I upgraded it using apt-get update with no problems. (That I've noticed yet. Haven't tried sound and some other not-so-simple stuff.) In other words, I got into /etc/apt/sources.list and commented out the squeeze lines and added wheezy lines, per the documented procedures at http://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html Since that went fairly well, I tried the same thing on my working OS. Lots of things show that I need to tune settings, I expected that. I may have missed it in the middle of the night, but I didn't see any messages about not being able to install the kernel. No holds show up anywhere, either. While restoring the PAM settings that keep my kids from logging in after 11:00 at night (not the right solution, I know.), I noticed that the kernel was still at 2.6.32. No sign of 3.2 in /boot or anywhere. Synaptic says it's not loaded. So, I'm just doing the point-and-click install of the 3.2 kernel, hoping nothing too strange happens. Comments? -- Joel Rees -- -- Joel Rees
Re: kernel not upgraded to wheezy
On Lu, 01 iul 13, 09:19:31, Joel Rees wrote: Short story: upgraded squeeze to wheezy, kernel did not. But OS seems to run, so I'm using synaptic to install the kernel. (I know I should use apt-cache and apt-get, but I'm lazy and trying to do some other work that needs to be done today.) Wondering why, wondering how big a hole-in-my-foot I'm going to end up with. We'll see. Wondering if this has happened to anyone else. ... Comments? Two: 1. Since the kernel packages have different names they are not upgrades in the sense of the package manager (like installing package foo version 1.2.3 to upgrade from foo version 0.1.2 is). If you want/need this to be handled by the package manager have a look at the linux-image-flavour packages. 2. The method of installing is irrelevant, the kernel will not be used until you reboot anyway ;) You should only avoid synaptic when the upgrade may involve parts of your GUI infrastructure (*dm, DE/WM, etc.), otherwise I'm sure it might be a viable alternative for the dist-upgrade. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
