November 2011 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 624654] New: mkinitrd should not use sysfs for module names
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

http://bugzilla.novell.com/show_bug.cgi?id=624654 http://bugzilla.novell.com/show_bug.cgi?id=624654#c0 Summary: mkinitrd should not use sysfs for module names Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: mmarek(a)novell.com ReportedBy: msvec(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- In case the currently running kernel differs a lot from the one which is installed (for example a case of distro upgrade), mkinitrd might not get the module names correct as sysfs contains the old info. It should only use modalias and look up the names somewhere in the new (installed) kernel. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 2

[Bug 556953] New: can not boot with / on RAID10
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

http://bugzilla.novell.com/show_bug.cgi?id=556953 http://bugzilla.novell.com/show_bug.cgi?id=556953#c0 Summary: can not boot with / on RAID10 Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: i686 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: novellbmw(a)lsmod.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.23) Gecko/20090912 SUSE/1.1.18-1.2 SeaMonkey/1.1.18 Because of https://features.opensuse.org/305343 it is now possible to install openSUSE on RAID6 and RAID10, but a system with / on RAID10 will not boot after installation. Reproducible: Always Steps to Reproduce: 1. boot openSUSE-11.2-DVD-i586.iso 2. create 4 partitions with type FD=Linux RAID autodetect (2 partitions might suffice) 3. create RAID10 mounted on root (/) partition 4. use a non-raid or RAID1 for /boot 5. finish install Actual Results: on first boot, system stops in initrd: http://www.zq1.de/bernhard/temp/raid10-boot-fail.png Expected Results: should boot up as an equivalent RAID6 setup does Probable cause is that raid10.ko is missing from initrd. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 5

[Bug 598077] New: mkinitrd: domain search list not used
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

http://bugzilla.novell.com/show_bug.cgi?id=598077 http://bugzilla.novell.com/show_bug.cgi?id=598077#c0 Summary: mkinitrd: domain search list not used Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: All OS/Version: Linux Status: NEW Severity: Enhancement Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jengelh(a)medozas.de QAContact: qa(a)suse.de Found By: Beta-Customer Blocker: --- When boot-network.sh runs from an initramfs, /etc/resolv.conf is only populated with nameservers, but not the domain search list. This however, would be very welcome. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 4

[Bug 642235] New: multiple copies/versions of /lib/firmware/2.6.34-*/radeon in initrd
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=642235 https://bugzilla.novell.com/show_bug.cgi?id=642235#c0 Summary: multiple copies/versions of /lib/firmware/2.6.34-*/radeon in initrd Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: koenig(a)linux.de QAContact: qa(a)suse.de Found By: --- Blocker: --- running mkinitrd-2.6.0-2.3.x86_64 on my xen dom0 server after the 1st kernel update generates an initrd with all available copies of /lib/firmware/2.6.34*/radeon/ : $ zcat /boot/initrd-2.6.34.7-0.3-default | cpio -itv | grep R100_cp.bin -rw-r--r-- 1 root2 root 2048 Jun 29 20:05 lib/firmware/2.6.34-12-xen/radeon/R100_cp.bin -rw-r--r-- 1 root2 root 2048 Sep 16 01:14 lib/firmware/2.6.34.7-0.2-default/radeon/R100_cp.bin -rw-r--r-- 1 root2 root 2048 Sep 21 01:56 lib/firmware/2.6.34.7-0.3-xen/radeon/R100_cp.bin -rw-r--r-- 1 root2 root 2048 Jul 6 17:37 lib/firmware/2.6.34.1-0.0.6.82d7a13-xen/radeon/R100_cp.bin -rw-r--r-- 1 root2 root 2048 Sep 21 01:45 lib/firmware/2.6.34.7-0.3-default/radeon/R100_cp.bin 54780 blocks $ zcat /boot/initrd-2.6.34.7-0.3-default | cpio -it | grep /radeon/ | sed 's,[^/]*$,,' | uniq -c 54780 blocks 2 lib/firmware/radeon/ 27 lib/firmware/2.6.34-12-xen/radeon/ 27 lib/firmware/2.6.34.7-0.2-default/radeon/ 27 lib/firmware/2.6.34.7-0.3-xen/radeon/ 27 lib/firmware/2.6.34.1-0.0.6.82d7a13-xen/radeon/ 27 lib/firmware/2.6.34.7-0.3-default/radeon/ 1 lib/modules/2.6.34.7-0.3-default/kernel/drivers/gpu/drm/radeon/ reason for the multiple kernel versions is this $ grep ^multiversion /etc/zypp/zypp.conf multiversion = provides:multiversion(kernel) but in initrd-2.6.34.7-0.3-default there should be only /lib/firmware/2.6.34.7-0.3-default/* , isn't it?! $ rpm -qf /sbin/mkinitrd mkinitrd-2.6.0-2.3.x86_64 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 7

[Bug 623268] New: LVM support was lost for booting of updated system.
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

http://bugzilla.novell.com/show_bug.cgi?id=623268 http://bugzilla.novell.com/show_bug.cgi?id=623268#c0 Summary: LVM support was lost for booting of updated system. Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Markus.Elfring(a)web.de QAContact: jsrain(a)novell.com Found By: --- Blocker: --- I updated a couple of software components from current packages on Friday. Yesterday I was surprised that all Linux kernels I could select from the GRUB menu could not find the root file system which is contained in a logical volume. I reactivated an old kernel with the corresponding initial RAM disk to get a working openSUSE back. I am curious which update "dropped" the LVM2 support to boot as expected from /dev/mapper/system-root"". Which ways would be recommended to repair the contents of the other RAM disks? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 18

[Bug 723406] New: encrypted /var is not accessed by initrd
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=723406 https://bugzilla.novell.com/show_bug.cgi?id=723406#c0 Summary: encrypted /var is not accessed by initrd Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: yoshi314(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20100101 Firefox/8.0 I've installed opensuse 11.4 on a following layout root is on ssd. it's a GPT partition layout /var is on hdd, as a lvm volume which is inside of encrypted PV. 11.4 installer opens encrypted device and discovers lvm volumes. Setup goes without issues. Generated initrd does not include luks support (i've filed a bug about that), and after rebuilding with mkinitrd -A fails to open the luks device - it claims that aes-cbc-essiv is not supported by kernel, even though the installer kernel had no issues opening it. I've tried updating to tumbleweed kernel. Regenerated the initrd (mkinitrd -A as before). Hit similar issue as before. Either mkinitrd -A does not include crypto modules, or there is something wrong with stock kernel configuration. Using a dracut generated initrd from custom built vanilla kernel works with this installation. Reproducible: Always Steps to Reproduce: 1. Install system in aforementioned partition setup 2. Rebuild initrd 3. enter luks password at boot, no lvm volumes are found 4. manual attempts to use luksOpen from recovery shell fail due to errors suggesting lacking crypto features 5. Try again with tumbleweed kernel and -A generated kernel 6. no lvm volumes are found; will check for more info booted with parameters luks=box luks_box=/dev/sda1 Actual Results: system waits for /var lvm volume and times out. eventual recovery shell or botched boot. Expected Results: normal system boot luks volume info : LUKS header information for /dev/sda1 Version: 1 Cipher name: aes Cipher mode: cbc-essiv:sha256 Hash spec: sha1 Payload offset: 4096 (....) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 5

[Bug 727352] New: df displays wrong device names
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=727352 https://bugzilla.novell.com/show_bug.cgi?id=727352#c0 Summary: df displays wrong device names Classification: openSUSE Product: openSUSE 12.1 Version: RC 1 Platform: i686 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: rhg(a)marxmeier.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.2.23) Gecko/20110920 Firefox/3.6.23 This is a server system using a MD/LVM layout. MD is RAID1: /dev/md0 -> /boot (EXT2) /dev/md1 -> swap /dev/md2 -> LVM Logical volumes: /dev/vg00/root -> / /dev/vg00/usr -> /usr /dev/vg00/opt -> /opt /dev/vg00/var -> /var Below is the df -h output. Note the /dev/dm-2 device name, should be: /dev/mapper/vg00-usr # df -h Filesystem Size Used Avail Use% Mounted on rootfs 1014M 192M 823M 19% / devtmpfs 2,0G 44K 2,0G 1% /dev tmpfs 2,0G 0 2,0G 0% /dev/shm tmpfs 2,0G 288K 2,0G 1% /run /dev/mapper/vg00-root 1014M 192M 823M 19% / /dev/dm-2 3,0G 1,4G 1,6G 47% /usr tmpfs 2,0G 0 2,0G 0% /sys/fs/cgroup tmpfs 2,0G 0 2,0G 0% /media /dev/mapper/vg00-opt 1014M 33M 982M 4% /opt /dev/mapper/vg00-var 2,0G 103M 1,9G 6% /var tmpfs 2,0G 288K 2,0G 1% /var/lock tmpfs 2,0G 288K 2,0G 1% /var/run /dev/md0 250M 27M 211M 12% /boot Reproducible: Always -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 8

[Bug 618442] New: Minimal X install comes up in twm rather than IceWM Lite
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

http://bugzilla.novell.com/show_bug.cgi?id=618442 http://bugzilla.novell.com/show_bug.cgi?id=618442#c0 Summary: Minimal X install comes up in twm rather than IceWM Lite Classification: openSUSE Product: openSUSE 11.3 Version: RC 1 Platform: x86 OS/Version: openSUSE 11.3 Status: NEW Severity: Minor Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: znmeb(a)borasky-research.net QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.6) Gecko/20100626 SUSE/3.6.6-1.1 Firefox/3.6.6 I installed a VirtualBox guest from the i586 openSUSE 11.3 RC1 DVD. For desktop I selected "Minimal X". I was expecting it to come up in IceWM. I checked the packages to be installed before the install and "IceWM Lite" was indeed installed. But when I logged in after the install, the system came up in "twm", not "IceWM". I'm still searching the web for how to configure the system so it comes up in IceWM, but I was assuming that it would come up that way automatically - that's the way an appliance built with SUSE Studio with the "Minimal X" pattern works. This isn't by any stretch of the imagination a show-stopper, but it would be nice if a minimal X install came up in IceWM. Reproducible: Always Steps to Reproduce: 1. Install a system with the "Minimal X" desktop option 2. Boot it up 3. Log in Actual Results: System came up in "twm" Expected Results: It should have come up in IceWM -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 3

[Bug 725684] New: booting with pxe and root on nfs fails due to no dhcp interface found
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=725684 https://bugzilla.novell.com/show_bug.cgi?id=725684#c0 Summary: booting with pxe and root on nfs fails due to no dhcp interface found Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: i686 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: per(a)opensuse.org QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10 I'm booting a Factory system over PXE and with root on NFS. This stops very quickly with the following: running dhcpcd on interface err, no interface specified I've investigated it a bit further, and determined that the variable 'dhcp_macaddresses' is not set when run_all.sh is called. It therefore ends up defaulting to a MAC-address of the system where the initrd was built which means boot/12-network.sh cannot identify the interface, hence "err, no interface specified" It is quite possible that this is a direct effect of bug#724775, but for the moment there is no obvious connection. Reproducible: Always -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 9

[Bug 724775] New: initramfs and ifup-sysctl
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=724775 https://bugzilla.novell.com/show_bug.cgi?id=724775#c0 Summary: initramfs and ifup-sysctl Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: aj(a)suse.com QAContact: qa(a)suse.de CC: mmarek(a)suse.com, fcrozat(a)suse.com Found By: Product Management Blocker: --- Created an attachment (id=457191) --> (http://bugzilla.novell.com/attachment.cgi?id=457191) screenshot of initial boot with error message I was able to catch the appended screenshot: udevd[202]: failed to execute /etc/sysconfig/network/scripts/ifup-sysctl... This is done from initial ramdisk. This is with current openSUSE factory as of 2011-10-18 under kvm (but noticed the same problem on real hardware). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 35