You are not logged in.
Pages: 1
I upgraded to the latest kernel(2.6.13) in testing and got the message..
>>> If you use any DevFS paths in your GRUB menu.lst, then you will not
>>> be able to boot! Change your root= parameter to use the classic
>>> naming scheme.
>>>
>>> EXAMPLES:
>>> - change root=/dev/discs/disc0/part3 to root=/dev/hda3
>>> - change root=/dev/md/0 to root=/dev/md0
My GRUB menu.lst is currently "root=/dev/discs/disc0/part2 ro" so if i reboot now i'll not be able to boot the kernel, correct? Since I don't have a /dev/hd* (except hdc) I have no idea what i'm supposed to put? Some help with this would be great.
my /etc/fstab
/dev/discs/disc0/part3 swap swap defaults 0 0
/dev/discs/disc0/part2 / ext3 defaults 0 1
/dev/discs/disc0/part4 /home ext3 defaults 0 1
df -h
[root@localhost lowe]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/scsi/host0/bus0/target0/lun0/part2
9.2G 3.0G 5.8G 35% /
none 505M 0 505M 0% /dev/shm
tmpfs 505M 200K 505M 1% /tmp
/dev/scsi/host0/bus0/target0/lun0/part4
176G 86G 82G 52% /home
Offline
it's not all that hard:
/dev/discs/disc0/part1 <-> /dev/hda1
/dev/discs/disc0/part2 <-> /dev/hda2
/dev/discs/disc0/part3 <-> /dev/hda3
/dev/discs/disc0/part4 <-> /dev/hda4
/dev/discs/disc0/disc <-> /dev/hda
Same with disc1 <-> hdb
EDIT: note: if you use SCSI or SATA drives, the "hd" is replaced with "sd"
Offline
Ok I did that rebooted and when it boots the kernel it says something like "Cannot open initial console" I guess i need to reinstall? =/
Offline
Last I looked the AL Wiki had a section about what to do if this happened under the "Udev How To".
Boot using the AL install CD
mount your root partition (example:
"mount /dev/hda3 /mnt")
chroot to the newly mounted dir (example:
"chroot /mnt")
create missing static nodes in /dev with:
cd /dev
mknod -m 660 console c 5 1
mknod -m 660 null c 1 3
HTH
Skeeter
Rule #1: There are NO RULES!
Offline
skeeter: Thanks a lot that worked.
Now it gets stuck at lshwd, It's just not my day.
Offline
Ah well I went back to 2.6.12 and it works fine, the new kernel must be borked in some way.
Offline
Did you follow the udev wiki how to at all? kernel .13 doesn't support devfs at all, the way .12 does. Sooner or later you're going to have get udev sorted
Offline
Ah well I went back to 2.6.12 and it works fine, the new kernel must be borked in some way.
Yep, I loaded 2.6.13 last night but had to revert back, too. It worked, but not without a number of issues.
I'm betting that there'll be a lot of problems posted once 2.6.13 hits the main repo and people begin to upgrade. It might be the right time to consider releasing Arch Linux 0.8 with the new kernel in it.
oz
Offline
Did you follow the udev wiki how to at all? kernel .13 doesn't support devfs at all, the way .12 does. Sooner or later you're going to have get udev sorted
I have udev working on 2.6.12 so that's not the problem with .13.
Offline
I've been using udev for a couple of months now, but I'm beginning to wonder if the new kernel will reveal any lingering issues releated to devfs?
oz
Offline
Boot using the AL install CD
mount your root partition (example:
"mount /dev/hda3 /mnt")
from the wiki it says it should be
"mount your root partition (example: "mount /dev/discs/disc0/part3 /mnt")"
and that worked, but you are right as to what the package says when the kernel is upgraded from testing, it says to mount the partition using the new udev way and not the old devfs way. i guess we need to tell the package maintainers about that, it is confusing and doesnt work. yeah the wiki has all the correct info, but the package should too
He may look like an idiot and talk like an idiot but don't let that fool you. He really is an idiot.
- - - Groucho Marx
Registered Linux User #319935
Registered Linux Machine #204881
Offline
Pages: 1