Help with Gutsy Upgrade
Ubuntu developers. I know this is not the place for the usual requests for help with Ubuntu, but I don't know where else to look. I've posted to the Ubuntu-users list, the Ubuntu and Kubuntu forums and I've be visited both #ubuntu and #kubuntu on IRC. I've even added my comment to a Launchpad bug report, #190588. I've gotten several suggestions to fix my problem, but so far none of them have made a difference. I've also tried to post to ubuntu-devel, but the moderator refused the post and recommended I post here instead. About 2 weeks ago I tried to upgrade my PC using the instructions found here http://www.kubuntu.org/announcements/7.10-release.php. The upgrade froze at Installing packages 2%. After a couple of hours I stopped the upgrade process and tried again. This time the upgrade finished successfully. I rebooted the PC expecting to get a new Gutsy desktop, but instead got the Busy Box initramfs prompt and this message... Check root= bootarg cat /proc/cmdline or missing modules, devices: cat /proc/modules ls /dev ALERT! /dev/disk/by-uuid/(my boot disk uuid) does not exist. Dropping to a shell. All modules seem to be present and loaded but ls /dev/disk/by-uuid shows I have no hard drives (I actually have 2 hard drives, both EIDE devices, not SATA). I can boot using the prior Feisty 2.6.20-16-generic kernel and am able to trouble shoot using the older kernel. As I said above, I have tried several suggestions to fix this problem, but so far none have had any effect. I've tried re-installing the 2.6.22-14-generic kernel. I've tried modifying initramfs. I've re-installed and updated GRUB. I've modified GRUB's menu.lst to use /dev/sd and /dev/hd drive identifiers. I've tried to re-run the upgrade, both form the internet and from the alternate CD, but both methods say my system is up to date and can't be upgraded. I don't know if this may be important information, but when I upgraded from Dapper to Feisty my system refused to recognize the new /dev/sd drive identifiers and I had to modify GRUB and /etc/fstab to use /dev/hd instead, but that didn't work this time. While this may not be a common problem with the Feisty / Gutsy upgrade, a Google search shows the several are have the same or similar upgrade errors. Can someone here please give me some suggestions to fix this problem? Thanks, Rick Knight -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Problem with Grub being installed in MBR as default (GG)
I've just installed Gutsy Gibbon on a harddrive with 4 distros on it. The install went ok, and was able to select which partitions I wanted to use to install Gutsy Gibbon on, but after that the install went into auto mode, and post install I find that Gutsy Gibbons Grub has been installed in the MBR, replacing my FC2's Grub, that had chainloader links to my 2 Debian installs, and to the FC3 install, which partitions are now being used by GG. I've reinstalled FC2's grub in the MBR, but up to now havn't found out how to install GG's Grub into GG's / partition (hda9). When I can, I can simply create another chainloader entry in FC2's Grub, so as to be able to boot GG. The request I have is, is it possible to include options as to where the bootloader is going to be installed in Gutsy Gibbons installer program, as are present in other distros. The default is usually the MBR, but you are usually presented with other places to install the bootloader. Nigel. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Problem with Grub being installed in MBR as default (GG)
On Tue, 2008-04-01 at 19:23 +0200, Nigel Henry wrote: The request I have is, is it possible to include options as to where the bootloader is going to be installed in Gutsy Gibbons installer program, as are present in other distros. The default is usually the MBR, but you are usually presented with other places to install the bootloader. It's an option in the Advanced button on the confirmation page of the installer that says what's going where, what settings you chose, and lists that GRUB is going on the MBR. signature.asc Description: This is a digitally signed message part -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Problem with Grub being installed in MBR as default (GG)
On Tue, 2008-04-01 at 20:53 +0200, Nigel Henry wrote: On Tuesday 01 April 2008 19:35, Mackenzie Morgan wrote: On Tue, 2008-04-01 at 19:23 +0200, Nigel Henry wrote: The request I have is, is it possible to include options as to where the bootloader is going to be installed in Gutsy Gibbons installer program, as are present in other distros. The default is usually the MBR, but you are usually presented with other places to install the bootloader. It's an option in the Advanced button on the confirmation page of the installer that says what's going where, what settings you chose, and lists that GRUB is going on the MBR. Thanks for your quick reply. I've since got the Grub bootloader for Gutsy Gibbon installed on the / partition for GG, and now have access to all 4 distros on the harddrive again. I'll try another install of GG, if I can find space on another drive. I'd obviously missed the Advanced button on the confirmation page of the installer. By confirmation page, I just mean that last page before you hit the Apply or Install or whatever it is button where it lists all your choices. signature.asc Description: This is a digitally signed message part -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Massive breakage on my system with April 1st updates
On 4/2/08, Conrad Knauer [EMAIL PROTECTED] wrote: Not an April Fool's joke... or if it is, I'm not laughing ;) Today I lost: - sound (due to latest kernel, linux-image-2.6.24-13-generic; selecting 2.6.24-12 in GRUB gets sound working) - most of my GNOME theme settings (because several theme-related packages upgraded?) - compiz (possibly related to one or both of the above?) It is a bit disconcerting to me that this is happening so close to release... You manually installed the 2.6.24-13 kernel, right? Browsing the linux-meta source package on Launchpad shows that it still depends on 2.6.24-12. You probably haven't installed the various other 2.6.24-13 packages (linux-ubuntu-modules - where your sound driver lives, linux-restricted-modules - where your graphics driver probably lives), or they haven't yet been built. Once they're all built, linux-meta will be updated to depend on the -13 kernel packages, and will automatically pull in the new kernel + necessary associated packages. I haven't seen any problems with GNOME theme settings. This may be related, or may be a real bug - it's difficult to tell. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Massive breakage on my system with April 1st updates
(sorry; it e-mailed only the first time) On Tue, Apr 1, 2008 at 6:13 PM, Christopher Halse Rogers [EMAIL PROTECTED] wrote: You manually installed the 2.6.24-13 kernel, right? All I did was press the Reload, Mark all upgrades and Apply buttons in Synaptic. [...] AH!!! I see what happened: I have virtualbox-ose-modules-generic installed, which just upgraded its latest version depends on virtualbox-ose-modules-2.6.24-13-generic which in turn depends on linux-image-2.6.24-13-generic I haven't seen any problems with GNOME theme settings. This may be related, or may be a real bug - it's difficult to tell. I will attempt to revert some of the recent changes to see what might have caused the problem. CK -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Massive breakage on my system with April 1st updates
Conrad Knauer wrote: You manually installed the 2.6.24-13 kernel, right? All I did was press the Reload, Mark all upgrades and Apply buttons in Synaptic. [...] AH!!! I see what happened: I have virtualbox-ose-modules-generic installed, which just upgraded its latest version depends on virtualbox-ose-modules-2.6.24-13-generic which in turn depends on linux-image-2.6.24-13-generic Daniel, please wait for linux-meta to be updated before changing your package to depend upon the new kernel - you do temporarily break systems by doing this. Thanks Hobbsee signature.asc Description: OpenPGP digital signature -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Got Hardy? With Sound?
Op maandag 31-03-2008 om 11:17 uur [tijdzone +0200], schreef Oliver Grawert: Am Freitag, den 28.03.2008, 01:00 +0100 schrieb Jan Claeys: Op vrijdag 28-03-2008 om 09:07 uur [tijdzone +1100], schreef Luke Yelavich: and flash has libflashsupport, which provides pulseaudio output for flash. Does that work on 64-bit systems now? (It didn't work (easily) in gutsy.) libflashsupport was added to the lib32 package, so it should work with nspluginwrapper now. I can say now that indeed it works. :-) My main problem now is the PulseAudio daemon crashing occasionally (which os not related to libflashsupport). :-/ -- Jan Claeys -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Unneeded System Tools menu
Op maandag 31-03-2008 om 09:05 uur [tijdzone -0700], schreef George Farris: The best example lately is and I suppose it was a technical reason and so maybe not avoidable because of gvfs is: moving the Removable drives and Media from the preferences. That was really a horrible move. There aren't even drives in the menu any more and yet it still says Drives. +1 Do you have a bug report # for that? -- Jan Claeys -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
