You are not logged in.
Pages: 1
Hi everyone,
I decided to try Arch on my netbook (a Gateway LT3103u) and everything was great up until the time that I found that CPU frequency scaling is broken for my processor (an Athlon64 Neo L110), leading to about a one hour runtime away from a wall socket. I did a little research and found that this problem could be solved (or at least alleviated) by compiling a new kernel with a fixed DSDT. To make a long story somewhat short, I obtained a fixed DSDT (from here), downloaded the kernel 2.6.33.4 source, compiled with my current .config (including the new DSDT, as detailed here) and the modifying my GRUB menu.lst as I thought appropriate. Finally, the problem is that I cannot seem to boot with the new kernel. I select the appropriate listing in GRUB, but get the error:
Root device '/dev/disk/by-uuid/{partition uuid}' doesn't exist. Attempting to create it.
ERROR: Unable to determine major/minor number of root device '/dev/disk/by-uuid/{partition uuid}'I checked and double-checked the uuid, tried listing the root device as /dev/sda#, and even tried all four partitions individually (default Arch partitioning layout) in an attempt to get this thing to boot, but nothing has yet worked.
I was really in over my head when trying to compile a new kernel but everything appeared to go fine until this point, so I'm guessing/hoping that it's just a mistake in my menu.lst that's causing this problem.
For the record, here's the GRUB entry for the new kernel:
# (3) Arch Linux
title Arch Linux DSDT_FIX
root (hd0,0)
kernel /vmlinuz-2.6.33.4-DSDTFIX root=/dev/disk/by-uuid/{my uuid} ro
initrd /kernel26-DSDTFIX.img(To put my post succinctly, I compiled a 2.6.33.4 kernel with my old .config + a new DSDT, added a new GRUB entry, and now I can't boot)
So, can anyone help me? If I left out some critical information, please let me know and I'll post it ASAP.
Offline
So I presume you have a seperate /boot-partition and it is on /dev/sda1 (at least according to your menu.lst above.
Did you copy your newly-made vmlinuz and kernel26 to /boot?
Personally, I abhor disk-by-uuid since it gives you absolutely no frigging idea which partition it is. I admit it has its uses if you have more than one disk - especially if one is ide and one is sata - but mindlessly trying different partitions is a waste of time - you've got to know what you are doing.
I would say that the most likely error is that vmlinuz and kernel26 are _not_ found in /boot
Offline
I just double-checked and both my new vmlinuz and kernel26 are both in /boot.
Contents of /boot:
[amorris@amorris_astro ~]$ ls /boot/
grub kernel26.img System.map26-2.6.33.4-DSDTFIX
kernel26-DSDTFIX.img lost+found vmlinuz26
kernel26-fallback.img System.map26 vmlinuz-2.6.33.4-DSDTFIXComplete menu.lst:
# (0) Arch Linux
title Arch Linux
root (hd0,0)
kernel /vmlinuz26 root=/dev/disk/by-uuid/038817a4-c351-4364-8c91-7bcdb291a07e ro
initrd /kernel26.img
# (1) Arch Linux
title Arch Linux Fallback
root (hd0,0)
kernel /vmlinuz26 root=/dev/disk/by-uuid/038817a4-c351-4364-8c91-7bcdb291a07e ro
initrd /kernel26-fallback.img
# (2) Windows
#title Windows
#rootnoverify (hd0,0)
#makeactive
#chainloader +1
# (3) Arch Linux
title Arch Linux DSDT_FIX
root (hd0,0)
kernel /vmlinuz-2.6.33.4-DSDTFIX root=/dev/disk/by-uuid/038817a4-c351-4364-8c91-7bcdb291a07e ro
initrd /kernel26-DSDTFIX.imgI'm assuming that the GRUB entry for the new kernel should be identical to that for the orignal and fallback kernels except for the fact that I must point to the two new files (i.e. the location of the root directory should be the same), correct?
*EDIT* Is there any way for me to retrieve the log from the failed boot when it kicks me out to the recovery shell? I'd like to compare it to a good boot to see if I messed something up in the kernel itself.
Last edited by Brother Michigan (2010-05-25 04:17:46)
Offline
I guess you could try with a live cd, but I doubt very much it would be of any use because obviously the disk is not recognized by your new kernel, and hence you have no access to a filesystem!
Can you still boot your old (original) kernel?
If so - yup, you have screwed up your new kernel!!
Offline
this is slightly off topic, but I have the same netbook and my wireless constantly drops, do you have this problem?
Offline
How often? I haven't been connected for long periods of time before rebooting (the longest only being an hour or two), but it seems to be fairly stable.
I guess you could try with a live cd, but I doubt very much it would be of any use because obviously the disk is not recognized by your new kernel, and hence you have no access to a filesystem!
Can you still boot your old (original) kernel?
If so - yup, you have screwed up your new kernel!!
Yeah, both the normal and the fallback arch kernels boot just fine. I guess that means it's time to go try again!
Last edited by Brother Michigan (2010-05-25 15:43:07)
Offline
every 5 minutes
Offline
Pages: 1