Closing this bug report due to lack of activity.
If the problem still exists in 10.10, feel free to open a new report.
** Changed in: initramfs-tools (Ubuntu)
Status: Incomplete => Invalid
--
Kernel panic 2.6.12-8-amd64-k8
https://bugs.launchpad.net/bugs/21481
You received this bug notif
Thank you for posting this bug.
Does this occur in Lucid?
--
Kernel panic 2.6.12-8-amd64-k8
https://bugs.launchpad.net/bugs/21481
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
h
check your fstab file or grub.confg file.
--
Kernel panic 2.6.12-8-amd64-k8
https://bugs.launchpad.net/bugs/21481
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.ubun
** Changed in: initramfs-tools (Ubuntu)
Assignee: Brian Murray (brian-murray) => (unassigned)
--
Kernel panic 2.6.12-8-amd64-k8
https://bugs.launchpad.net/bugs/21481
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mai
Alright, thanks for trying Jason.
A last update for any future bug sufferers is that I was able to load
the aforementioned kernel modules by modprobing them all individually.
--
Kernel panic 2.6.12-8-amd64-k8
https://bugs.launchpad.net/bugs/21481
You received this bug notification because you ar
I'm at a loss. I have no idea why the kernel would not be recognizing
the /dev/sdXY devices. Sorry that I cannot help more.
--
Kernel panic 2.6.12-8-amd64-k8
https://bugs.launchpad.net/bugs/21481
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subsc
Guys, I'm sorry to rush you but I really need to wipe my workstation and
this bug is the only thing stopping me. Could you provide a decision
list of things for me to try rather than a constant back and forth. Or
better, can we do this over chat? Thanks.
--
Kernel panic 2.6.12-8-amd64-k8
https://
I found another user with this problem but he couldn't fix it so he
traded his laptop in for a new model :/
http://ubuntuforums.org/archive/index.php/t-609277.html
--
Kernel panic 2.6.12-8-amd64-k8
https://bugs.launchpad.net/bugs/21481
You received this bug notification because you are a member
Jason, when I run that command I get:
> [435.476895]: scsi_mod: Unknown parameter: sd_mod
> FATAL: Error inserting scsi_mod. Unknown symbol or unknown parameter.
When I run `modprobe scsi_mod' I get `SCSI subsystem initialized' but no
new devices.
--
Kernel panic 2.6.12-8-amd64-k8
https://bugs.
The "error opening volume" message is probably because vol_id needs to
be run as root. But that doesn't matter because the problem is
/dev/sda* entries are not being created.
Maybe scsi drivers are not loaded? You could try running "modprobe
scsi_mod sd_mod sr_mod st sg" from -19 recovery consol
In the initramfs shell I have no sd*/hd* entries in /dev so nothing to
run vol_id on. After booting the -18 kernel:
-> ls /dev/sd* /dev/hd*
ls: cannot access /dev/hd*: No such file or directory
0 brw-
Your fstab and menu.lst look good to me same to me. And if they didn't
match, I would expect the error messages to be different.
So if you boot into -19 recovery console, you see entries in /dev ? Do
you at least have /dev/hda or /dev/sda entries for your drive? If so, I
don't know why it is n
I have an identical 64-bit workstation that is running the -19 kernel
and 32-bit hardy. The menu.lst and fstab files are essentially the same.
--
Kernel panic 2.6.12-8-amd64-k8
https://bugs.launchpad.net/bugs/21481
You received this bug notification because you are a member of Ubuntu
Bugs, which
Before we updated initramfs udev wasn't doing much of anything based on
the contents of /dev, but now there are hundreds of entries there. The
value of ROOT is /dev/disk/by-uuid/ but /dev/disk doesn't exist.
Could it be because fstab and menu.lst are out of sync? I see some UUID
entries in the menu
It pauses at "Begin: Waiting for root file system" because the entries
in /dev are not available. It pauses hoping that they will soon appear.
I'm not sure why they are not there. Could be udev not starting?
--
Kernel panic 2.6.12-8-amd64-k8
https://bugs.launchpad.net/bugs/21481
You received t
Please compare my menu.lst (above) with my fstab (here).
** Attachment added: "/etc/fstab"
http://launchpadlibrarian.net/16283970/fstab
--
Kernel panic 2.6.12-8-amd64-k8
https://bugs.launchpad.net/bugs/21481
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The usplash issue was fixed for a german ubuntu user here by
reinstalling libc6. That fix did not work for me (and as seen above I am
no longer getting that error since we ran update-initramfs).
http://tinyurl.com/reinstall-libc6
The AE_NOT_FOUND issue is documented in Bug #218118 and doesn't appe
I ran these commands:
> sudo su
> echo 'export LD_LIBRARY_PATH=/lib64' >
> /etc/initramfs-tools/conf.d/ld_library_path
>update-initramfs -u -k 2.6.24-19-generic
Then rebooted int the -19 kernel (normal and Recovery, -18 still works fine),
and got the following output:
--
I've attached the output of `update-initramfs -uv -k 2.6.24-19-generic'.
** Attachment added: "update-initramfs.log"
http://launchpadlibrarian.net/16283129/update-initramfs.log
--
Kernel panic 2.6.12-8-amd64-k8
https://bugs.launchpad.net/bugs/21481
You received this bug notification because y
I suspect that the linker is trying to load libc from from
/lib/libc.so.6 rather than /lib64/libc.so.6, where it reside in the
initrd you provided. Can you show the output of the command "update-
initramfs -uv -k 2.6.24-19-generic"? That may fix the problem depending
on how it updates the initrd.
I attached the 2.6.24-19 guy
** Attachment added: "initrd.img-2.6.24-19-generic"
http://launchpadlibrarian.net/16272598/initrd.img-2.6.24-19-generic
--
Kernel panic 2.6.12-8-amd64-k8
https://bugs.launchpad.net/bugs/21481
You received this bug notification because you are a member of Ubuntu
Bu
Sorry, it is 2.6.24-19-generic that is not booting properly? Could you
attach /boot/initrd.img-2.6.24-19-generic then?
--
Kernel panic 2.6.12-8-amd64-k8
https://bugs.launchpad.net/bugs/21481
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
Would you mind attaching /boot/initrd.img-2.6.25-2-amd64 ?
--
Kernel panic 2.6.12-8-amd64-k8
https://bugs.launchpad.net/bugs/21481
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
h
running `ls /dev/disk/by-uuid' is going to be problematic:)
> ls /dev
console null tty0 ... tty8
--
Kernel panic 2.6.12-8-amd64-k8
https://bugs.launchpad.net/bugs/21481
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mail
menu.lst is attached. Note that I added the amd64 kernel earlier today
from debian as a troubleshooting step but it hasn't changed any behavior
and gets the same error as the -19 kernel.
** Attachment added: "menu.lst"
http://launchpadlibrarian.net/16271531/menu.lst
--
Kernel panic 2.6.12-8-a
Could you add your '/boot/grub/menu.lst' file as an attachment to your
bug report? Additionally the results of 'ls /dev/disk/by-uuid/' when
booting the 2.6.26-19 would be interesting.
--
Kernel panic 2.6.12-8-amd64-k8
https://bugs.launchpad.net/bugs/21481
You received this bug notification becau
When booting that kernel without usplash I still get the same error
output, including the usplash_write error. I removed all instances of
usplash from my menu.lst file and for the time being I'm able to boot
into my -18 kernel. I don't get the usplash menu on this kernel so I
know I removed it corr
It would be useful to know what happens when you boot the 2.6.26-19
kernel without usplash. You can do this by editing the grub boot line
and removing the word 'usplash'.
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed => Incomplete
--
Kernel panic 2.6.12-8-amd64-k8
https://bug
Without my workstation I can't get any work done. If someone has read
this bug report and decided not to act on it I would appreciate you
telling me that. I have not wiped this workstation as a service to
Canonical, but if this bug is going to be ignored I am wasting my time!
--
Kernel panic 2.6.
I am experiencing this issue - three years after the initial bug report
- on my present system. The hardware is 3 Ghz Core 2 Duos with 8GB of
ram and an nVidia 8800GT with 64-bit Ubuntu Hardy Heron and whichever
kernel is current in apt today (-19 IIRC)
The specific error message:
--
In my case it says at boot time:
"/sbin/usplash_write error while loading shared libraries: libc.so.6
.."
the old kernel works good, so i guess the new kernel is badly configures
or something.
--
Kernel panic 2.6.12-8-amd64-k8
https://bugs.launchpad.net/bugs/21481
You received this bug noti
I have just upgraded to hardy and i have the same error.
I had this error when i upgraded to edgy but i compiled my own kernel.
Now it woks very fine with the old kernel 2.6.22 i have compiled.
Hovever, i am not abe to run kernel 2.6.24 from feisty.
It seems that mkinitramfs is buggy. It compil
i mean i had thsi probel when i upgraded to gutsy and to feisty (i don't
remeber for edgy)
It seems the only solution is to reinstall the hole ubuntu from
scratch???
This is because i have a very old ubuntu upgraded each time a new
distribution came out.
--
Kernel panic 2.6.12-8-amd64-k8
https:
Hello,
I have a amd64 machine.
I have upgraded from dapper to edgy, from edgy to feisty and from feisty to
gutsy. After the first upgrade and sice then, I have some errors when trying to
boot some ubuntu kernels (2.6.15 and 2.6.22-14-generic from gutsy) :
depmod: error while loading shared libr
Thanks again for taking the time to report and troubleshoot this issue
and I am glad that a newer version of Ubuntu is now working for you.
Feel free to submit any future bugs you may find.
** Changed in: initramfs-tools (Ubuntu)
Status: Needs Info => Rejected
--
Kernel panic 2.6.12-8-amd
Thanks Brian for contacting me about this problem. It is however no issue for
me anymore because I did a fresh install of Ubuntu. So the cause remains
unclear i'm afraid.
Thanks again and best regards,
Herko
--
Kernel panic 2.6.12-8-amd64-k8
https://bugs.launchpad.net/bugs/21481
You received th
Thanks for taking the time to report this bug and helping to make Ubuntu
better. You reported this bug a while ago and there hasn't been any
activity in it recently. We were wondering is this still an issue for
you? Thanks in advance.
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unas
It seems, mkinitramfs is including the libraries in /lib64, whereas the
started initramfs is looking in /lib. However, I don't know how to
change that behaviour...
--
Kernel panic 2.6.12-8-amd64-k8
https://launchpad.net/bugs/21481
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://
Hi!
I have the exact same problem on Dapper. Am I missing something
somewhere else? Unfortunately, this errors does not seem to have been
resolved...
Kernel 2.6.15-26-amd64-generic (or, BTW any older version of supplied kernels)
Athlon 3200
MSI-Board
Of course, I would be willing to assist in an
39 matches
Mail list logo
