Re: [Bug 223066] Re: initrd fails to load disk drivers
A clean reinstall took care of the issue a long time ago. No longer an issue. Thank you, On Nov 30, 2012 5:45 AM, Thomas Hotz thomas.h...@gmail.com wrote: Is this still an issue for you? What Ubuntu version do you use? Thank you for telling us! ** Changed in: initramfs-tools (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/223066 Title: initrd fails to load disk drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/223066/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/223066 Title: initrd fails to load disk drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/223066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 368670] [NEW] Konsole curs_set() error
Public bug reported: Binary package hint: konsole Begining in Jaunty (Ubuntu 9.04) Konsole does not appear to respond to the curs_set() curses function as it has previously, causing any curses app that calls curs_set() to fail when accessed from Konsole. In testing, the app still works fine on xterm. The app in question is accessed through an ssh session...it is not a local app. Konsole would appear to be the only thing 'getting in the way' of this application working properly. Konsole in Hardy worked fine. Yakuake (which apparently uses Konsole) also fails with identical error messages. with $TERM set to vt100: Traceback (most recent call last): File /data_store/.client_db/client_db.py, line 511, in ? main() File /data_store/.client_db/client_db.py, line 508, in main curses.wrapper(dr_clientGUI) File /usr/lib64/python2.4/curses/wrapper.py, line 44, in wrapper return func(stdscr, *args, **kwds) File /data_store/.client_db/client_db.py, line 45, in __init__ curses.curs_set(0) _curses.error: curs_set() returned ERR I can find no mention of this bug anywhere else. ** Affects: kdebase (Ubuntu) Importance: Undecided Status: New -- Konsole curs_set() error https://bugs.launchpad.net/bugs/368670 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 280997] Re: solid-bluetooth needs update for bluez 4.x
I'm on a stock Jaunty install with all updates applied and I'm seeing the EXACT same behaviour. kbluetooth4 starts in 'offline mode', and I get: arguments to dbus_message_new_method_call() were incorrect, assertion path != NULL failed in file dbus-message.c line 1070 when running kbluetooth-devicemanager. Status updated to confirmed so that Jaunty can get some bluetooth love. ** Changed in: kdebase-workspace (Ubuntu Jaunty) Status: Fix Released = Confirmed -- solid-bluetooth needs update for bluez 4.x https://bugs.launchpad.net/bugs/280997 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-workspace in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 32123] Re: initramfs not generated correctly on dist-upgrade
Bug 223066 (which I just filed a few days ago) may be a duplicate of this issue. I saw the exact same behavior when upgrading from Fiesty to Gutsy. I continued running with the fiesty kernel (2.6.20.15 I believe is the only one that continues to boot), and I am still doing so even after upgrading to Hardy last week. I have uninstalled/reinstalled both the generic and 386 kernels and done half a dozen initrd recreations and so far nothing has done any good. I get dropped to a busybox, every single time. Given the activity on this Bug (plus the 10+ duplicates of it, not to mention the countless forum posts/mailing lists inquiries for the same issue) can we at the very least bump this to critical, and possibly get someone actually ASSIGNED to it? -- initramfs not generated correctly on dist-upgrade https://bugs.launchpad.net/bugs/32123 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 223066] [NEW] initrd fails to load disk drivers
Public bug reported: Binary package hint: initramfs-tools This has been an ongoing issue for me since kernel 2.6.20, but it was the (once again) unsuccessful upgrade that caused me to finally report it. From what I can tell the initrd-x.x.xx-x-generic begining on 2.6.22+ fails to load any of the disk drivers (libata, ata_generic, ata_piix), and this results in the boot hanging on Begin: Waiting for root filesystem. It then drops to a busy box. I can manually load the modules inside the busybox and get the thing to (somewhat) boot, but doing that bypasses a whole trunk full of stuff needed for the system to actually function. I upgraded to Hardy thinking that the issue might be resolved (it first appeared when I upgraded to gutsy), but sadly no. I'm still running with the durned Feisty kernel a this point, and it's beginning to cause issues. I have rebuilt the initrd a half a dozen times and using the -v option it does seem to build the proper kernels into the image, but for what ever reason they never get executed prior to the attempt to mount the root filesystem. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: boot disk initrd kernel -- initrd fails to load disk drivers https://bugs.launchpad.net/bugs/223066 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 223066] Re: initrd fails to load disk drivers
Modules, that should say. it builds the proper modules into the image: [EMAIL PROTECTED]:~$ cat init.out | grep ata Adding module /lib/modules/2.6.24-16-generic/kernel/drivers/ata/libata.ko Adding module /lib/modules/2.6.24-16-generic/kernel/drivers/scsi/eata.ko Copying module directory kernel/drivers/ata Adding module /lib/modules/2.6.24-16-generic/kernel/drivers/ata/ata_generic.ko Adding module /lib/modules/2.6.24-16-generic/kernel/drivers/ata/ahci.ko Adding module /lib/modules/2.6.24-16-generic/kernel/drivers/ata/pata_acpi.ko Adding module /lib/modules/2.6.24-16-generic/kernel/drivers/ata/ata_piix.ko Adding module /lib/modules/2.6.24-16-generic/kernel/drivers/ata/pata_artop.ko -- initrd fails to load disk drivers https://bugs.launchpad.net/bugs/223066 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 155278] Re: Kernel =2.6.22 hangs on boot
I can confirm that this bug is NOT fixed in 2.6.24 (Hardy). I experienced the same issue when upgrading from 2.6.20 (which boots) to 2.6.22 (which hangs immediately), and upgrading to 2.6.24 exhibits the exact same behavior. Status of this bug appears to be 'confirmed', so I'm not sure if I should change anything per Leann's post above -- Kernel =2.6.22 hangs on boot https://bugs.launchpad.net/bugs/155278 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
Re: [Bug 33269] Re: root filesystem fails to mount (sata_nv module is loaded)
I'm not even sure that my comment on this bug relates to the original issue - but as far as I know yes, this still exists, at least with the latest available Gutsy Kernel Anything 2.6.22 or newer fails to boot on my laptop, complaining that it can't mount the root filesystem. 2.6.20 or older works fine. It is a bit frustrating, as there is nothing unusual about this laptop (Acer with an intel board, i915), but yet I seem to be one of the only people experiencing this issue. Google searches have turned up a few other people with the same problem, but it doesn't appear to be wide spread enough that anyone has fixed it. Randall On Mon, Mar 3, 2008 at 8:43 PM, Leann Ogasawara [EMAIL PROTECTED] wrote: Hi All, There hasn't been any recent activity in this bug for a while and we were just wondering if this issue still exists in the latest Hardy Alpha release? The Hardy Heron Alpha series contains an updated version of the kernel. You can download and try the new Hardy Heron Alpha release from http://cdimage.ubuntu.com/releases/hardy/ . You should be able to then test the new kernel via the LiveCD. If you can, please verify if this bug still exists or not and report back your results. General information regarding the release can also be found here: http://www.ubuntu.com/testing/ . Also note that we'll keep this report open against the actively developed kernel bug against 2.6.20, 2.6.17, and 2.6.15 this will be closed. Thanks. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New = Incomplete ** Changed in: linux-source-2.6.15 (Ubuntu) Status: Incomplete = Won't Fix ** Changed in: linux-source-2.6.20 (Ubuntu) Status: Incomplete = Won't Fix -- 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 direct subscriber of the bug. -- Randall -- 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 can't say for certain if this is the same issue - I upgraded to the gibbon yesterday, and upon a reboot the system would not come up. The recovery kernel (2.6.22-14-generic, I think) shows: BEGIN: Waiting for root filesystem and it never boots. The Edgy kernel, 2.6.20-16, boots fine. I thought this to be an issue with the initrd image, so I reinstalled the 2.6.22-14-generic kernel, which did rebuild the image, but the problem persists. This is indeed a laptop, and it has a SATA drive that registers as /dev/sda. I only started experiencing this with the upgrade to gutsy, so that is why I can't say if it's related or should be a different bug. -- 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
