You are not logged in.
Pages: 1
I recently downloaded and installed from the AUR the maxim patch to fix the mon0 problem with aircrack-ng.
Both makepkg and pacman -U finish without any issues.
The problem comes in when I try to set my system up to use the 2.6.8 kernel which is created by the process.
When it first finished, the new kernel was created on my "/" partition. I got them moved "/boot" partition in order to get my system set up.
The current files in my "/boot" are:
grub (folder)
lost+found (folder)
9a97750b-6285-42a6-9712-877d9ef12eca (uuid of the drive)
kernel26-img
kernel26-fallback.img
vmlinuz26
System.map26
kernel26-nx.img
kernel26-nx-fallback.img
vmlinuz26-nx
System.map26-nx
My /grub/menu.lst says:
# (0) Arch Linux
title Arch Linux
root (hd0,0)
kernel /vmlinuz26 root=/dev/disk/by-uuid/842288ba-e9a8-4a6e-8e60-4a54e4844dcd ro
initrd /kernel26-fallback.img
# (1) Arch Linux
title Arch Linux Fallback
root (hd0,0)
kernel /vmlinuz26 root=/dev/disk/by-uuid/842288ba-e9a8-4a6e-8e60-4a54e4844dcd ro
initrd /kernel26-fallback.img
Under this configuration is works fine. When I switch it to:
# (0) Arch Linux
title Arch Linux
root (hd0,0)
kernel /vmlinuz26-nx root=/dev/disk/by-uuid/842288ba-e9a8-4a6e-8e60-4a54e4844dcd ro
initrd /kernel26-nx-.img
# (1) Arch Linux
title Arch Linux Fallback
root (hd0,0)
kernel /vmlinuz26-nx root=/dev/disk/by-uuid/842288ba-e9a8-4a6e-8e60-4a54e4844dcd ro
initrd /kernel26-nx-fallback.img
It boots to "Waiting 10 seconds for drive..." Then puts me in to the ramfs because the drive does not respond. I am sure I am doing something wrong, I just don't know what.
Last edited by reddae (2011-04-06 05:13:19)
Toshiba NB255
ArchLinux / SLiM / E17
"Victory follows me, and all things follow victory." - Scudèri
Offline
I wonder if the UUIDs are being calculated differently by vmlinuz26 and vmlinuz26-nx. What if you change the UUID node for a /dev/sdaxx node ??
Please use BBCode code tags around file contents and program output. It makes it a lot easier to read. Thanks
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
I changed the boot string to:
root (hd0,0)
kernel /vmlinuz26-nx root=/dev/sda3 ro
initrd /kernel26-nx.img
Waiting 10 seconds for device /dev/sda3
ERROR: Unable to determine major/minor number of root device '/dev/sda3'
You are being dropped to a recovery shell
EDIT: I just tried with all of the drives, sda1,sda2,sda3,sda4 all with the same result.
Last edited by reddae (2011-04-06 06:03:38)
Toshiba NB255
ArchLinux / SLiM / E17
"Victory follows me, and all things follow victory." - Scudèri
Offline
Any chance your kernel is missing a required hardware driver ??
Does it contain built in or module support for the file system type of / ??
I am not experienced with that kernel, but I have built my share (Gentoo). You may need to compare the config files for the working and for the non-working kernel and see if there are relevant differences.
Signing off for the night
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
have you tried running fsck /dev/sd[x][x] from an live arch install cd/usb or another live image such as partedmagic ? then maybe booting fallback or recovery then rebuilding kernel by running mkinitcpio -p kernel26 ? those methods usually always fix those kinda of errors for me.
foggy shades, bright outside
Offline
Pages: 1