[opensuse] issues with opensuse 11.3 x86_64
Folks, I finally got 11.r installed and for the most part it works great. However I wanted to know if anyone encountered the following Issues and if there is a known solution. I could Not find anything googling nor on the forum. 1. Both the live cd and dvd hang at partition detection. Cause is I have a dmraid array and this is not being handled correctly. 11.2 handled this perfectly. 2. As regular user I cannot mount luk cryptyo partitions. I get some dolphin error. Root can mount these ok. Worked fine in 11.e 3. Partition references in menu.lst are parr by-id and part be /dev device entry (root). Adding a new drive breaks grub booting. Seemed to work fine in 11.2 If there is documentation on these can someone point me to it? Otherwise another great release! Vahe Avedissian -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, Sep 04, 2010 at 02:05:54PM -0700, Vahe Avedissian wrote:
I finally got 11.r installed and for the most part it works great. However I wanted to know if anyone encountered the following Issues and if there is a known solution. I could Not find anything googling nor on the forum.
11.r = 11.3?
1. Both the live cd and dvd hang at partition detection. Cause is I have a dmraid array and this is not being handled correctly. 11.2 handled this perfectly.
2. As regular user I cannot mount luk cryptyo partitions. I get some dolphin error. Root can mount these ok. Worked fine in 11.e
11.e = 11.2? There was an issue with pam_mount in 11.3 which got fixed by a recent update. Please check the output of rpm -q --changelog pam_mount for lines stating: - rdconf: do not warn about missing fskeyhash when no fskey specified; (bnc#626127); http://bugs.debian.org/580430
3. Partition references in menu.lst are parr by-id and part be /dev device entry (root). Adding a new drive breaks grub booting. Seemed to work fine in 11.2
If there is documentation on these can someone point me to it?
Mount by-id is a feature and not a bug. Think of the situation when you add an additional disk (usb, esata, firewire). See for example http://forums.opensuse.org/english/get-help-here/install-boot-login/405704-w... Idependent of your actual version number of the old release and the new version number you use this is again an example why we have to point users to the release notes of previous releases. We cant't expect people to install every release. Please consider to check the wiki if there is some documentation about the /dev/disk/by-* stuff and if not feel free to add one.
Otherwise another great release!
Thanks! But this depends heavily on your hardware. There had been some reports that oS 11.3 was the worst thing SUSE release ever. Not a point I'm sharing. But all this depends on your hardware. Here even with about 10 very different systems (AMD and Intel based; very, very old and two very recent) I had only small issues. Most important is to check bugzilla and to report issues if they are not reported yet. The noise level on the different lists is simply to high. In particular as a developer your focus is on the upstream discussions and the bug trackers. Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
Hi Lars, Thank you for your reply.
I finally got 11.r installed and for the most part it works great. However I wanted to know if anyone encountered the following Issues and if there is a known solution. I could Not find anything googling nor on the forum.
1. Both the live cd and dvd hang at partition detection. Cause is I have a dmraid array and this is not being handled correctly. 11.2 handled this
11.r = 11.3? Yes, sorry I didn't see what I typed on my BB. perfectly.
2. As regular user I cannot mount luk cryptyo partitions. I get some
dolphin error.
Root can mount these ok. Worked fine in 11.e
11.e = 11.2? There was an issue with pam_mount in 11.3 which got fixed by a recent update. Please check the output of rpm -q --changelog pam_mount for lines stating: - rdconf: do not warn about missing fskeyhash when no fskey specified; (bnc#626127); http://bugs.debian.org/580430 Yes 11.e = 11.2, I checked that I have the latest pam_mount installed. I do not see the message above! I have pam_mount-1.34-3.1.1.x86_64 insrtalled and suse update shows that as the latest version. IS that correct?
3. Partition references in menu.lst are parr by-id and part be /dev device entry (root). Adding a new drive breaks grub booting. Seemed to work fine in 11.2
If there is documentation on these can someone point me to it?
Mount by-id is a feature and not a bug. Think of the situation when you add an additional disk (usb, esata, firewire). See for example http://forums.opensuse.org/english/get-help-here/install-boot-login/405704-w... Idependent of your actual version number of the old release and the new version number you use this is again an example why we have to point users to the release notes of previous releases. We cant't expect people to install every release. Please consider to check the wiki if there is some documentation about the /dev/disk/by-* stuff and if not feel free to add one. My issue with grub was for any boot option, the resume field is set up with disk by-id while the root field was set up by device. When adding (or removing) disks, the resume filed is still valid but the root field becomes invalid. Making root also disk by -id fixes this issue. My comment here was that 11.3 seems to do this like 11.1 and 11.2 seems to have done it more correctly. By the way, dmraid is now not enabled at boot time (just like 11.1) but 11.2 not only enabled dmraid at boot time, but also added entries into grub for OS's it found on the dmraid array. This does not seem to work now. I have to look at it more when I have time.
Otherwise another great release!
Thanks! But this depends heavily on your hardware. There had been some reports that oS 11.3 was the worst thing SUSE release ever. Not a point I'm sharing. But all this depends on your hardware. Here even with about 10 very different systems (AMD and Intel based; very, very old and two very recent) I had only small issues. My hardware is about 5-6 years old (Tyan K8WE based system). I hope that is not considered too old. Most important is to check bugzilla and to report issues if they are not reported yet. The noise level on the different lists is simply to high. In particular as a developer your focus is on the upstream discussions and the bug trackers. Lars Thanks, Vahe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (2)
-
Lars Müller
-
Vahe Avedissian