[Bug 1872108] Re: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal
@Alejandro Miranda I've noticed the command moves the sound from the top speakers to the bottom. Sounds, no doubt, but seems to disable to speakers up top. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872108 Title: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 269851] Re: Bluetooth Logitech Dinovo Edge Keyboard/Mouse dones not work anymore
There was a question posted about this issue here: https://answers.launchpad.net/ubuntu/+question/105987 I purchased a separate bluetooth dongle and was able to get my keyboard to sync by logging in from another computer and pairing the keyboard with the other dongle. The disadvantage of using this separate dongle is that I don't have access to the keyboard until the OS has loaded. Hopefully the late April release will solve this as I wasn't happy about having to buy a separate bluetooth dongle and new users might never be able to sort the issue out. -- Bluetooth Logitech Dinovo Edge Keyboard/Mouse dones not work anymore https://bugs.launchpad.net/bugs/269851 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 269851] Re: Bluetooth Logitech Dinovo Edge Keyboard/Mouse dones not work anymore
No "bluetooth" file in the /etc/default directory -- not sure where the file went but assuming this would mean default values were used. Will check later today whether restoring the file brings back the pre-Lucid functionality. -- Bluetooth Logitech Dinovo Edge Keyboard/Mouse dones not work anymore https://bugs.launchpad.net/bugs/269851 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 269851] Re: Bluetooth Logitech Dinovo Edge Keyboard/Mouse dones not work anymore
Problem is back on Lucid -- unplugging and replacing doesn't fix it anymore -- I will check to see if the HID2HCI_ENABLED setting has changed. -- Bluetooth Logitech Dinovo Edge Keyboard/Mouse dones not work anymore https://bugs.launchpad.net/bugs/269851 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 367464] Re: Jaunty freezes randomly
I have been experiencing freezes as well -- many/most of them accompanied by a blinking caps lock. I run the latest updates of Jaunty on a Lenovo x301. I do not run ext4 either. I have been able to avoid freezes by turning off the wireless devices (including both bluetooth and wifi via the physical switch). -- Jaunty freezes randomly https://bugs.launchpad.net/bugs/367464 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 329713] Re: Jaunty: default DPI settings much too high
I have had this problem ever since I started using a TV as a display (DVI to HDMI cable from an nVidia 9600GT). Although I never checked the DPI reported by X in Intrepid, I did have the huge GDM, Etherape and Google Earth fonts. For most other apps, I can usually able to change application settings to compensate, but I would prefer to fix the setting globally or have it default to 96 DPI. Great link, Bryce -- definitely on point for me, but my problem remains. A few comments: My Display is a 40" 1080 television. 1920 (horizontal pixels) divided by 35 (horizontal inches) equals 54. X is reporting the same 305 (is that the max?). "xrandr --verbose" reports "0mm x 0mm" (I'll guess this is the root problem) but "get-edid" doesn't exist and the "read-edid" package "has no installation candidate" on Jaunty. This seems needlessly complex - can't I just hard-code 96 DPI somewhere? Also not digging the "wont fix" status -- this stuff "just works" on Windows. Or does this just me the bug will be fixed in a different module? -- Jaunty: default DPI settings much too high https://bugs.launchpad.net/bugs/329713 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 269851] Re: Intrepid Ibex Alpha 5 Bluetooth Logitech Dinovo Edge Keyboard/Mouse don't work
I tried Jaunty last week and can confirm that the problem exists on 2.6.28 as well. Something was broken in Intrepid. For more detail, the connection between the dongle and the keyboard remains/resumes after rebooting. I can navigate BIOS fine and have no problem navigating the boot menu when I use a LIve CD. The disconnection happens after Ubuntu starts loading so I no longer have control by the time X is running. Removing and reinserting the dongle (then pairing it again) seems to be the only way to fix it (because there is no input). I could try logging in remotely and executing some diagnostic commands, but I have no idea which ones would be useful. Ideas? I will also try a Live CD for another 2.6.27 or 2.6.28 distribution (probably sometime this weekend) to see if the problem is specific to Ubuntu. If you get a chance to try that first, please let us know how it goes. -- Intrepid Ibex Alpha 5 Bluetooth Logitech Dinovo Edge Keyboard/Mouse don't work https://bugs.launchpad.net/bugs/269851 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 269851] Re: Intrepid Ibex Alpha 5 Bluetooth Logitech Dinovo Edge Keyboard/Mouse don't work
I am having new problems with my diNovo as well - I think it may have something to do with a difference in the way that the dongle is being recognized and initialized during startup because I am able to get it to work if I follow these steps: (1) unplug the dongle from the USB slot, (2) plug the dongle back in to the USB slot (3) pair the dongle and keyboard I have to do this every time I boot the machine now where with Hardy I only had to do step #3 -- Intrepid Ibex Alpha 5 Bluetooth Logitech Dinovo Edge Keyboard/Mouse don't work https://bugs.launchpad.net/bugs/269851 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 33269] Re: root filesystem fails to mount (sata_nv module is loaded)
Thanks, Michael (and Bernd). Confirming that adding "large-memory" to lilo.conf does resolve the issue for me. -- root filesystem fails to mount (sata_nv module is loaded) https://bugs.launchpad.net/bugs/33269 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 33269] Re: root filesystem fails to mount (sata_nv module is loaded)
Thanks for the link, Bernd. Yes, I am running lilo. It is worth noting that the file I've been using since building my kernel (shows up as 2.6.24.3) is actually quite large. It probably shouldn't be, but even the 2.6.22 files are over 8 megabytes: -rw-r--r-- 1 root root 8564557 2008-04-18 00:52 initrd.img-2.6.22-14-generic -rw-r--r-- 1 root root 8562568 2008-04-01 07:20 initrd.img-2.6.22-14-generic.bak -rw-r--r-- 1 root root 8943650 2008-04-22 01:33 initrd.img-2.6.24-16-generic -rw-r--r-- 1 root root 8872726 2008-04-19 11:13 initrd.img-2.6.24-16-generic.bak -rw-r--r-- 1 root root 44920220 2008-04-22 07:21 initrd.img-2.6.24.3 -rw-r--r-- 1 root root 44919345 2008-04-21 19:11 initrd.img-2.6.24.3.bak The 2.6.24-16 files above don't work -- all the others do. -- root filesystem fails to mount (sata_nv module is loaded) https://bugs.launchpad.net/bugs/33269 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 33269] Re: root filesystem fails to mount (sata_nv module is loaded)
I compiled a custom 2.6.24 kernel to get around the "bad gzip magic numbers" problem I was having. Unfortunately, I still can not use 3d acceleration or sound with this new compiled kernel - I guess I'll be watching for 2.6.24-17 generic. Hardy releases in 3-days ... really? I am leaving this thread now to look for solutions for my new 3d and sound issues - but I will be happy to provide test results or other information if someone is interested in the 2.6.24-16 issues. -- root filesystem fails to mount (sata_nv module is loaded) https://bugs.launchpad.net/bugs/33269 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 33269] Re: root filesystem fails to mount (sata_nv module is loaded)
In my test, 2.6.22 was re-created fine. -- root filesystem fails to mount (sata_nv module is loaded) https://bugs.launchpad.net/bugs/33269 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 33269] Re: root filesystem fails to mount (sata_nv module is loaded)
Thanks for the suggestion. "pci=nomsi" does not work for me. I am going to try generating a new 2.6.22 image to see if that works (I don't think I have created a 2.6.22 since the move to hardy) - this should tell me whether the problem is in creating the images or if the problem is in loading them. -- root filesystem fails to mount (sata_nv module is loaded) https://bugs.launchpad.net/bugs/33269 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 33269] Re: root filesystem fails to mount (sata_nv module is loaded)
Confirmed the problem still exists for me on 2.6.24-16. "checking if image is initramfs...it isn't (bad gzip magic numbers); looks like an initrd" Nobody else seems to be getting the above message -- I am attaching my image to this comment. For more information, the machine is a Core2 Duo and I am running the 64-bit version of Hardy. I have tried appending the following at boot: acpi=off irqpoll apm=on noapic I note that this thread appears similar to that of bug #32123. Based on that discussion, I have also tried "sudo dpkg-reconfigure linux- image-2.6.24-16-generic" with no success. Is there something else I should try? ** Attachment added: "boot image -- uploaded to determine what is wrong with it" http://launchpadlibrarian.net/13369241/initrd.img-2.6.24-16-generic -- root filesystem fails to mount (sata_nv module is loaded) https://bugs.launchpad.net/bugs/33269 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 33269] Re: root filesystem fails to mount (sata_nv module is loaded)
I am also experiencing difficulties booting 2.6.24-15. ASUS P5K-E with 3 SATA drives in RAID-1 containing root and boot. 2.6.22-14 (and lower) boot fine. I have tried 2.6.24-12 through 2.6.24-15 and always get the following message: "checking if image is initramfs...it isn't (bad gzip magic numbers); looks like an initrd" I have tried "update-initramfs -k 2.6.24-15-generic -u" but I still get the message above. I am able to boot from a desktop/live CD (2.6.24) and install mdadm then mount the RAID successfully, but I can't seem to boot 2.6.24 in any other way. -- root filesystem fails to mount (sata_nv module is loaded) https://bugs.launchpad.net/bugs/33269 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 8497] All caused by installation process failing to configure for UUIDs?
I agree that it is possible (likely even) that the comments here reflect several problems and not just one. As an end-user, I report on symptoms as best I can (i.e. "wont boot after kernel update"), the underlying problems are probably better identified by those more familiar with the structure of the operating system (you?) - symptoms can then be grouped by their underlying causes. In this case, the similarity appears to be that changing the ordering of drive references can make the machine fail to boot. I gather that the UUID would not change between consecutive boots, but I don't really understand when you say "you should be using UUIDs." The installation process I followed did not ask me whether I wanted to use UUIDs. I could certainly read up on how to make the proposed change, but perhaps an update/fix is still warranted if the installation process should have been configuring to use UUIDs. -- grub guessed BIOS disk order incorrectly https://bugs.launchpad.net/bugs/8497 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 148325] Re: Certain processes show incorrect memory usage when using xgl
I get it too: xgl+x64 and restricted nVidia -- Certain processes show incorrect memory usage when using xgl https://bugs.launchpad.net/bugs/148325 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107249] Re: failed kernel update followed by boot failure
Problem solved (again) I used the liveCD from Gutsy to boot, and re-assembled the array using info from this page: http://ubuntuforums.org/showthread.php?t=408461 mounted the volume and then ran lilo following some information I found here: http://www.syrlug.org/contrib/boot-loaders.html#LILO and finally rebooted into Feisty - where the failed kernel update repeated itself. Fortunately, I could still work on the problem because the system hadn't been rebooted. This time, I solved the problem by removing a section of my lilo.conf file corresponding to a windows boot. I am not sure why the windows section was there (perhaps as a courtesy?) because I didn't add it (when I want to boot from windows, I just select the windows boot device from BIOS). In fact, I have never touched the lilo.conf file before today. In any case, I think the lilo configuration was no longer valid because the order of the drives (as reported by BIOS?) was changed between kernel updates - possibly relating to an issue documented in bug #8497. Anyway, good news today. So until next time - hope NOT to see you so soon. -- failed kernel update followed by boot failure https://bugs.launchpad.net/bugs/107249 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 8497] Re: grub guessed BIOS disk order incorrectly
I am wondering if my bug #107249 is also being caused by this. In my case, kernel updates have sometimes failed and have resulted in the system presently being unbootable. My machine, an Asus A8V, reports 4 sata drives, two on each controller. Three of these drives are being used by linux: a bootable RAID-1 (3 disks), and a RAID-5 (3 disks) for data. The fourth drive contains a bootable XP partition. If lilo depends on a consistent ordering of the four drives, is it possible that the random reordering (as reported to linux by the bios) could have caused lilo to attempt to update a kernel on the XP drive instead of one from the linux array? -- grub guessed BIOS disk order incorrectly https://bugs.launchpad.net/bugs/8497 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107249] Re: failed kernel update followed by boot failure
Over the weekend some process caused me to need to reboot the machine - which is a problem because the machine "doesn't have a valid boot signature" as of the last kernel update. This is the third time a failed semi-automatic kernel update has left the computer unusable (I typically accept kernel updates because I'm hoping one of them will address one of the many USB/scanner problems). Perhaps the update- manager should confirm the update could be completed before actually writing to the drive? I am now in the same situation I was in on April 17th (can't boot) ... please let me know if there are any other log files I should attempt to pick up before I re-install with Gutsy. -- failed kernel update followed by boot failure https://bugs.launchpad.net/bugs/107249 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107249] Re: failed kernel update followed by boot failure
The latest kernel update has failed. This time the message that I receive is "Fatal: First sector of /dev/sda1 doesn't have a valid boot signature". This does not appear to have anything to do with the RAID - mdstat shows all volumes are up: Personalities : [raid1] [raid6] [raid5] [raid4] md1 : active raid5 sda2[0] sdd2[2] sdb2[1] 468856832 blocks level 5, 64k chunk, algorithm 2 [3/3] [UUU] md0 : active raid1 sda1[0] sdd1[2] sdb1[1] 9767424 blocks [3/3] [UUU] unused devices: I am not sure why the drive devices keep showing up in a different order - note that last time sdc, sdb, and sdd were listed - this time sda, sdd, and sdb are listed. I hope I don't have to look forward to a different problem every time the kernel is updated ... ** Attachment added: "screenshot of error message" http://launchpadlibrarian.net/9087224/Screenshot.png -- failed kernel update followed by boot failure https://bugs.launchpad.net/bugs/107249 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107249] Re: failed kernel update followed by boot failure
So I added sdc1 back to the md0 array. This was enough to get me past the errors in the upgrade and everything checks out ok. I guess I'll really know when I next try to reboot. It is not clear to me why sdc1 was dropped from the array ... I will look for a log to see if I can find an explanation. sdc2 remained in the second array so I know that the drive itself is functional. here is the output from apt-get install: Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libgoffice-0-common gdesklets-data gnome-cups-manager Use 'apt-get autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 0B of archives. After unpacking 0B of additional disk space will be used. Setting up linux-image-2.6.20-16-generic (2.6.20-16.29) ... Running depmod. update-initramfs: Generating /boot/initrd.img-2.6.20-16-generic Warning: '/proc/partitions' does not match '/dev' directory structure. Name change: '/dev/dm-0' -> '/dev/horizon/swp' Added Linux * Added LinuxOLD Added Windows The Master boot record of /dev/sdc has been updated. Warning: /dev/sdd is not on the first disk The Master boot record of /dev/sdd has been updated. Warning: /dev/sdb is not on the first disk The Master boot record of /dev/sdb has been updated. Not updating initrd symbolic links since we are being updated/reinstalled (2.6.20-16.28 was configured last, according to dpkg) Not updating image symbolic links since we are being updated/reinstalled (2.6.20-16.28 was configured last, according to dpkg) You already have a LILO configuration in /etc/lilo.conf Running boot loader as requested Testing lilo.conf ... Testing successful. Installing the partition boot sector... Running /sbin/lilo ... Installation successful. -- failed kernel update followed by boot failure https://bugs.launchpad.net/bugs/107249 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107249] Re: failed kernel update followed by boot failure
i think this has something to do with my RAID, for whatever reason. "cat /proc/mdstat" produces the following output, suggesting md0 is not fully functional. Personalities : [raid1] [raid6] [raid5] [raid4] md1 : active raid5 sdc2[0] sdb2[2] sdd2[1] 468856832 blocks level 5, 64k chunk, algorithm 2 [3/3] [UUU] md0 : active raid1 sdd1[1] sdb1[2] 9767424 blocks [3/2] [_UU] unused devices: the following URLs seemed to support this theory: http://www.issociate.de/board/post/28744/lilo_boot_problems.html http://wpkg.org/index.php/Software_RAID_in_Linux -- failed kernel update followed by boot failure https://bugs.launchpad.net/bugs/107249 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107249] Re: failed kernel update followed by boot failure
With the last kernel update, I think I've encountered the problem again. My guess is that this machine will not be able to reboot so I hope to keep it running for long enough to provide any log files that might be related. To start with, I'm attaching a screenshot which shows the error message. ** Attachment added: "screenshot displaying error message" http://launchpadlibrarian.net/8063921/Screenshot-1.png -- failed kernel update followed by boot failure https://bugs.launchpad.net/bugs/107249 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107249] Re: failed kernel update followed by boot failure
The latest kernel update worked fine so I am assuming that the problem no longer exists. This report should be closed. -- failed kernel update followed by boot failure https://bugs.launchpad.net/bugs/107249 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107249] Re: failed kernel update followed by boot failure
I have re-installed using the release version. I did save all of the contents from my /var/log directory so any files that would have been there are still available. Also - I recovered my firefox session where I was searching for an answer after the upgrade failure and before the reboot. The string I had been searching on was: "Fatal: First sector of /dev/sdc1 doesn't have a valid boot signature" I note that sdc1 (not sure which drive it was referring to) shouldn't have had a boot signature as I was booting from md0. -- failed kernel update followed by boot failure https://bugs.launchpad.net/bugs/107249 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107249] Re: failed kernel update followed by boot failure
the /var/log/dist-upgrade directory is empty. BTW: mounted md0 by the following steps: installed mdadm (not positive this was necessary) created directory /mnt/md0 typed "sudo mount -t auto /dev/md0 /mnt/md0" -- failed kernel update followed by boot failure https://bugs.launchpad.net/bugs/107249 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107249] Re: failed kernel update followed by boot failure
Right now I don't have access to md0 which contains that directory. If I could install RAID support after booting from the live CD, then I might be able to access these files. -- failed kernel update followed by boot failure https://bugs.launchpad.net/bugs/107249 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107249] Re: failed kernel update followed by boot failure
I expect to install the release version of Feisty tomorrow evening - I've decided that having a running system is far more important than preserving the configuration data stored on /etc/openvpn, /etc/apache2, and /var (addressing the repair/restore install issue). However, I still fear that the update manager will break my system again the next time it tries to install a new kernel. -- failed kernel update followed by boot failure https://bugs.launchpad.net/bugs/107249 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107249] Re: failed kernel update followed by boot failure
** Description changed: I installed feisty from the 4/14/07 alternate CD (to support software RAID) and was able to boot thanks to the fix to bug #103177. The system worked fine for a day or so - then the update manager provided kernel 2.6.20-15, which was not able to install (not sure why). Apparently the failed install ruined my boot setup / LILO and now I am unable to boot. When I try to boot, I see the following message: "EBDA is big; Kernel setup stack overlaps LILO second stage" System is configured as follows: 4 SATA drives: 1x74GB containing windows XP; 3x250GB configured as 2 RAIDs: md0: RAID1: 10GB: / - md1: RAID5: ~490GB: LVM: + md1: RAID5: 480GB: LVM: /home /swp /tmp My guess is that the updater didn't understand how to make the changes to LILO on the RAID1 volume. The "recovery" install apparently does not know how to do this either because I am not presented with my md0 partition when I try to fix it - instead, I get only home, swp, and tmp (from md1) and the component partitions for the RAIDs and the XP drive. Because I use LILO rather than GRUB (I think this was necessary to boot from RAID), I do not have any boot-menu options. I do not know of any other way to boot and I would like to avoid wiping my md0 volume because it (hopefully still) has important information in /etc/openvpn, /etc/apache2, and /var. -- failed kernel update followed by boot failure https://bugs.launchpad.net/bugs/107249 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107249] Re: failed kernel update followed by boot failure
** Description changed: I installed feisty from the 4/14/07 alternate CD (to support software - RAID) and was able to boot thanks to the fix to bug #103177: - - https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/103177 + RAID) and was able to boot thanks to the fix to bug #103177. The system worked fine for a day or so - then the update manager provided kernel 2.6.20-15, which was not able to install (not sure why). Apparently the failed install ruined my boot setup / LILO and now I am unable to boot. When I try to boot, I see the following message: "EBDA is big; Kernel setup stack overlaps LILO second stage" System is configured as follows: 4 SATA drives: 1x74GB containing windows XP; 3x250GB configured as 2 RAIDs: md0: RAID1: 10GB: / md1: RAID5: ~490GB: LVM: /home /swp /tmp My guess is that the updater didn't understand how to make the changes to LILO on the RAID1 volume. The "recovery" install apparently does not know how to do this either because I am not presented with my md0 partition when I try to fix it - instead, I get only home, swp, and tmp (from md1) and the component partitions for the RAIDs and the XP drive. Because I use LILO rather than GRUB (I think this was necessary to boot from RAID), I do not have any boot-menu options. I do not know of any other way to boot and I would like to avoid wiping my md0 volume because it (hopefully still) has important information in /etc/openvpn, /etc/apache2, and /var. ** Tags added: installation update-manager -- failed kernel update followed by boot failure https://bugs.launchpad.net/bugs/107249 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107249] failed kernel update followed by boot failure
Public bug reported: I installed feisty from the 4/14/07 alternate CD (to support software RAID) and was able to boot thanks to the fix to bug #103177: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/103177 The system worked fine for a day or so - then the update manager provided kernel 2.6.20-15, which was not able to install (not sure why). Apparently the failed install ruined my boot setup / LILO and now I am unable to boot. When I try to boot, I see the following message: "EBDA is big; Kernel setup stack overlaps LILO second stage" System is configured as follows: 4 SATA drives: 1x74GB containing windows XP; 3x250GB configured as 2 RAIDs: md0: RAID1: 10GB: / md1: RAID5: ~490GB: LVM: /home /swp /tmp My guess is that the updater didn't understand how to make the changes to LILO on the RAID1 volume. The "recovery" install apparently does not know how to do this either because I am not presented with my md0 partition when I try to fix it - instead, I get only home, swp, and tmp (from md1) and the component partitions for the RAIDs and the XP drive. Because I use LILO rather than GRUB (I think this was necessary to boot from RAID), I do not have any boot-menu options. I do not know of any other way to boot and I would like to avoid wiping my md0 volume because it (hopefully still) has important information in /etc/openvpn, /etc/apache2, and /var. ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- failed kernel update followed by boot failure https://bugs.launchpad.net/bugs/107249 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 103177] Re: boot-time race condition initializing md
I believe I am having this same problem. My machine contains 4 sata drives, 3 of which are being used for linux, configured as two RAIDs: md0: RAID1: / md1: RAID5: LVM: /home /tmp swap The above configuration worked well in Edgy, but I didn't have access to my wireless ethernet (WPA). The latest attempt was after installing from this morning's (4/5/07) alternate CD. I don't know how to use either of the above workarounds (not sure how to "boot with break=premount" and I don't have access to the file-system because I haven't learned how to mount the RAID file-system manually when I boot from the live CD). -- boot-time race condition initializing md https://bugs.launchpad.net/bugs/103177 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
