You are not logged in.
Got a weird problem Actually made me laugh when i noticed what was going on. Not laughing anymore tho since i cant find a solution for the problem.
Setup:
Disk are (by-uuid) in grub, and it finds the kernel just fine.
sda = windows
sdb = arch
When i boot with 2.6.36, the harddrives gets switched around, so the kernel thinks sda is my linux disk & sdb is my windows disk, obvisouly it cannot find my root disk since its not on sda.
This is a slimmed down kernel config that i used for awhile, i went thru the make oldconfig without seeing anything that should make this behavior appear, but i obviously missed something.
vanilla 2.6.35-arch kernel works fine on the system.
Dont know what i need to change, is it 2.6.36 vs udev, or did something change in 2.6.36 that i need to adjust.
Last edited by pshr (2010-11-02 16:08:08)
Offline
You said grub is using uuid for the partitions. Is your /etc/fstab also using UUIDs?
Nai haryuvalyë melwa rë
Offline
The disks should also be specified by UUID in your /etc/fstab.
https://wiki.archlinux.org/index.php/UU … _naming.3F
-- edit: too slow.
Last edited by Stebalien (2010-11-02 16:26:19)
Offline
Hmm, i was thinking the problem started earlier but il check it out. Thanks for offering your help !
Offline
Nope, no dice...the problems starts when the disks themself are recognized.
windows - "sda" should be... sda1 sda5
linux - "sdb" should be.. sdb1 sdb2 sdb3 sdb4
When 2.6.36 boots, it throws that around so..
windows - "sda" ends up like this... sda1 sda2 sda3 sda4
linux - "sdb" ends up like this.. sdb1 sdb5
which leaves me clueless since the 2.6.35 kernel boots like it should..
Last edited by pshr (2010-11-02 17:11:00)
Offline
Messed around with some options, and got the kernel working, booted fine. Now when i rebooted the problem is back..wth How is that possible..
Anyways,im tired of it and will go back to 2.6.35, and manually patch ck..
Offline