February 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 779887] New: Yast bootloader keeps deleting console= when using grub2-efi bootloader
by bugzilla_noreply＠novell.com 10 Feb '14

10 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=779887 https://bugzilla.novell.com/show_bug.cgi?id=779887#c0 Summary: Yast bootloader keeps deleting console= when using grub2-efi bootloader Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: tonyj(a)suse.com QAContact: jsrain(a)suse.com Found By: Development Blocker: No This is on an Intel Tunnelmountain system. Setup for serial booting. using grub2-efi bootloader run yast bootloader, "Boot Loader Options" add console=ttyS0,115200 to end of "Optional Kernel Command Line Parameter" select ok to save bootloader nothing in /etc/default/grub nothing in /boot/grub2-efi/grub.cfg run yast bootloader, "Boot Loader Options" ... console= has been deleted also nothing in /etc/sysconfig/bootloader (what is the relationship between bootloader:DEFAULT_APPEND and grub:GRUB_CMDLINE_LINUX_DEFAULT) ? vi /etc/default/grub add console=ttyS0,115200 to end of GRUB_CMDLINE_LINUX_DEFAULT run yast bootloader, "Boot Loader Options" "console=ttyS0,115200" now shown in "Optional Kernel Command Line Parameter" select ok to save bootloader vi /etc/default/grub console= has been deleted run yast bootloader, "Boot Loader Options" console= has been deleted ----- Also what exactly does "Use serial console" and "console arguments" mean? Setting this value, all I see in grub.cfg is "console=ttyS0,115200" It's hard for me to tell if this is just limited to grub itself as my EFI has serial port redirection enabled. Should setting this option also attempt to do something intelligent regarding the kernel command line or is it strictly limited to grub? -- 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 6

[Bug 782913] New: Various Boot Loader Option problems
by bugzilla_noreply＠novell.com 10 Feb '14

10 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=782913 https://bugzilla.novell.com/show_bug.cgi?id=782913#c0 Summary: Various Boot Loader Option problems Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: 64bit OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: peterichardavis(a)gmx.net QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20100101 Firefox/15.0.1 1: On my computer, Help refers to pressing Set as Default. After an exhaustive search, I can't find any such thing to press, though the facility is in /etc/default/grub. 2: If I tick Hide Menu on Boot, I not only hide the menu but disable the choice. If I were to do that after changing the default to another operating system, I'd be unable to enter openSUSE to correct the error, and would presumably have to reinstall it. 3: When I used (K)ubuntu, I was able to set Windows as my default operating system, and reduce the Timeout in Seconds to zero without denying myself the choice of Linux. I liked to do this with my dual boot computer as an added security precaution, because I believed that most thieves wouldn't even realize that I had another operating system. With openSUSE, after doing the same thing, I did end up having to reinstall it. With 12.1, I was able to set the Timeout to 1 without disabling the choice, which at least meant that a thief would have to be fairly quick to spot what I'd done. With 12.2, I find that I have to extend that to 2 seconds, which, as I see it, is going the wrong way. I, of course, would prefer that things work the way I like, but, if openSUSE has good reasons for doing otherwise, it seems to me that it would be kind to spare the unwary from disabling the system in this way, either with a warning or by actually preventing the combination of defaulting to another system with disabling the choice of openSUSE. Reproducible: Always Steps to Reproduce: 1. Change default operating system to another. 2. Tick Hide Menu on Boot or reduce Timeout in Seconds below 2. 3. Restart computer. Actual Results: Inability to use openSUSE, requiring re-installation. Expected Results: I'd hoped to be able to start openSUSE by pressing the up arrow key without being able to see the choice on the screen. -- 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 780647] New: grub2 boots into black screen
by bugzilla_noreply＠novell.com 10 Feb '14

10 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=780647 https://bugzilla.novell.com/show_bug.cgi?id=780647#c0 Summary: grub2 boots into black screen Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: Rudolf.Goeldner(a)email.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20100101 Firefox/15.0 graphic Radeon 7750 (HIS iSilence5) monitor 1920 x 1080 OS 12.1 is installed at hd(1,0)/sdb1, boot from mbr OS 12.2 is installed at hd(1,5)/sdb5, boot from root partition grub2 is booted by chainloader from grub legacy menue grub2 boots correct in the FAILSAVE mode. grub2 boots also correct with the following parameters: video=1024 x 768, vga=0x317. But in this case the resulting resolution of the running OS12.2 is only 1024 x 768 and there is no way to change it. Use of any other resolution in the boot options results in a black screen. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 780638] New: Distribution of "grub2-emu" by a package?
by bugzilla_noreply＠novell.com 10 Feb '14

10 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=780638 https://bugzilla.novell.com/show_bug.cgi?id=780638#c0 Summary: Distribution of "grub2-emu" by a package? Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: Markus.Elfring(a)web.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- The utility "grub2-emu" is listed in the file "/usr/share/doc/packages/grub2/README.openSUSE". It seems that it is not provided by the package "grub2-2.00-1.6.1" so far. Would you like to suggest an alternative installation source for this software component? -- 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 775760] New: 12.2 grub.cfg dual boot doesn't automatic update after tumbleweed kernel updates
by bugzilla_noreply＠novell.com 10 Feb '14

10 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=775760 https://bugzilla.novell.com/show_bug.cgi?id=775760#c0 Summary: 12.2 grub.cfg dual boot doesn't automatic update after tumbleweed kernel updates Classification: openSUSE Product: openSUSE 12.2 Version: RC 2 Platform: HP OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: terje(a)nordland-teknikk.no QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20100101 Firefox/14.0.1 First, had tumbleweed vmlinuz-3.5.1-37 installed on /dev/sda2 with grub1 and menu.lst in use. Second, installed 12.2 RC2 on /dev/sda5 with grub2, and both system booted ok in dual boot from the grub2 startup menu. Third, tumbleweed was updated to newer kernel vmlinuz-3.5.1-38-desktop (which also upgraded the unused grub1 menu.lst). However, tumbleweed wasn't longer possible to boot from the current grub2 startup menu. Verified that grub.cfg had not been upgraded in the tumbleweed entry to take care of the latest 3.5.1-38 kernel update. Not before I ran 'grub2-mkconfig -o /boot/grub2/grub.cfg' the startup menu worked again to boot tumbleweed. This will confuse most users, and it cannot be expected that they know what to do. Wouldn't it be wise that the grub.cfg automatic being updated during each startup to solve this issue? Reproducible: Always Steps to Reproduce: 1.As described above 2. 3. Actual Results: As desribed above Expected Results: As described above -- 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 766304] New: plymouth/framebuffer is 1280x1023
by bugzilla_noreply＠novell.com 10 Feb '14

10 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=766304 https://bugzilla.novell.com/show_bug.cgi?id=766304#c0 Summary: plymouth/framebuffer is 1280x1023 Classification: openSUSE Product: openSUSE 12.2 Version: Beta 1 Platform: All OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bwiedemann(a)suse.com QAContact: qa-bugs(a)suse.de CC: aj(a)suse.com, mchang(a)suse.com, jslaby(a)suse.com, rwooninck(a)opensuse.org, i(a)coly.li Found By: System Test Blocker: --- openQA found that since some months, grub2 and framebuffer screen sizes in Qemu's emulated cirrus graphics lacks one line. E.g. currently it is 1280x1023 and 2012-04-12 it was observed at 1024x767 Steps To Reproduce: qemu-kvm -m 1000 -cdrom factory/iso/openSUSE-DVD-x86_64-12.2-Beta1.iso -monitor stdio -hda disk.img -boot dc install from NET/DVD in qemu-kvm (for DVD disable image-install to workaround another bug) when the system first reboots, stop within grub2 on qemu's monitor interface issue "screendump /tmp/test.ppm" > head -2 /tmp/test.ppm P6 1280 1023 interestingly, this does not show on later boots of the installed system. Then, there is a proper 1280 1024 so maybe 2nd stage changes something here? -- 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 6

[Bug 771539] New: Some issues with grub2 since new directory structure
by bugzilla_noreply＠novell.com 10 Feb '14

10 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=771539 https://bugzilla.novell.com/show_bug.cgi?id=771539#c0 Summary: Some issues with grub2 since new directory structure Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: ath(a)muffti.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=498660) --> (http://bugzilla.novell.com/attachment.cgi?id=498660) y2log User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20100101 Firefox/13.0.1 I have some issues since the directory structure of grub2 was changed (from all file resist in /boot/grub2 to /boot/grub2/i386....) 1. If I use such a new version, grub2 hangs in the rescue mode with message "... file not found..." o.s. 2. The directory structure look like false, the directory /boot/grub2/locale/ was empty. Even after a new installation of all "grub2 packages" 3. If no grub.cfg exists in the directory, it will also create no new one. If there is an empty grub.cfg exists from an older installation or an empty one they would created correctly. But the system will boot still in the rescue mode. 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 4

[Bug 767272] New: Missing boot entries for other distros.
by bugzilla_noreply＠novell.com 10 Feb '14

10 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=767272 https://bugzilla.novell.com/show_bug.cgi?id=767272#c0 Summary: Missing boot entries for other distros. Classification: openSUSE Product: openSUSE 12.2 Version: Milestone 3 Platform: All OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: hippolyte(a)shaw.ca QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20100101 Firefox/12.0 Sometimes os-prober fails to mount a partition, often Ubuntu root partition but not always. As a consequence it cannot read the the Grub menu and add a boot entry. It happens randomly but regularly with different os-prober versions, on different distros and different machines. This bug is NOT the same as the one decribed here https://bugzilla.novell.com/show_bug.cgi?id=759635 which affects only ufs2 partitions (solved in version 1.5.3 in my repo). Reproducible: Sometimes Steps to Reproduce: Boot openSUSE and run os-prober. If all systems are detected, reboot another OS, such as Ubuntu, (so its root partition will be mounted), then reboot openSUSE and run os-prober again. It may take several tries before it fails. Once it fails, running os-prober multiple times will consistently fail to access the other OS, thinking it needs a file system check. Actual Results: # OSPDEBUG=yes os-prober No volume groups found /dev/sda1:Windows NT/2000/XP (loader):Windows:chain /dev/sda13:Fedora release 16 (Verne):Fedora:linux /dev/sda15:Debian GNU/Linux (squeeze/sid):Debian:linux /dev/sda3:FreeBSD:FreeBSD 8.1-RELEASE:freebsd mount: wrong fs type, bad option, bad superblock on /dev/sda6, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so /dev/sdb1:Windows NT/2000/XP (loader):Windows1:chain /dev/sdc1:Windows NT/2000/XP (loader):Windows2:chain /dev/sdc6:Gentoo Base System release 1.12.13:Gentoo:linux Expected Results: # OSPDEBUG=yes os-prober No volume groups found /dev/sda1:Windows NT/2000/XP (loader):Windows:chain /dev/sda13:Fedora release 16 (Verne):Fedora:linux /dev/sda15:Debian GNU/Linux (squeeze/sid):Debian:linux /dev/sda3:FreeBSD:FreeBSD 8.1-RELEASE:freebsd /dev/sda6:Ubuntu 11.10 (11.10):Ubuntu:linux /dev/sdb1:Windows NT/2000/XP (loader):Windows1:chain /dev/sdc1:Windows NT/2000/XP (loader):Windows2:chain /dev/sdc6:Gentoo Base System release 1.12.13:Gentoo:linux OSPDEBUG is a flag I added to prevent redirecting standard error and see what happened. Mount failures can be seen in /var/log/messages: Jun 15 05:00:35 bareil os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda6 Jun 15 05:00:35 bareil kernel: [36610.164065] EXT4-fs (sda6): INFO: recovery required on readonly filesystem Jun 15 05:00:35 bareil kernel: [36610.164069] EXT4-fs (sda6): write access unavailable, cannot proceed It seems that this partition would need a file system check (however it is not the case), which can not proceed because it is mounted read only. This is due to a call to the function ro_partition, defined in /usr/share/os-prober/common.sh: ro_partition () { if type blockdev >/dev/null 2>&1 && \ [ "$(blockdev --getro "$1")" = 0 ] && \ blockdev --setro "$1"; then cleanup_ro_partitions="${cleanup_ro_partitions:+$cleanup_ro_partitions }$1" trap cleanup EXIT HUP INT QUIT TERM fi } It explicitely sets the partition read only (blockdev --setro). Commenting out this function call in /usr/lib/os-probes/50mounted-tests solves the problem but I'm not sure how safe it is, because all partitions will be accessed read-write in this case (I guess). # ro_partition "$partition" Now sda6 can be mounted, grub.cfg can be read and the boot entry will be added (see expected results above). Next, you could uncomment ro_partition in /usr/lib/os-probes/50mounted-tests, and os-prober would mount it this time. Once a partition has been already mounted, os-prober has no problem to mount it again. Therefore a safer workaround would be to mount the failing partition manually until this bug has been fixed. -- 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 34

[Bug 755137] New: /usr/bin/grub2-kbdcomp bash script requires missing application ckbcomp
by bugzilla_noreply＠novell.com 10 Feb '14

10 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=755137 https://bugzilla.novell.com/show_bug.cgi?id=755137#c0 Summary: /usr/bin/grub2-kbdcomp bash script requires missing application ckbcomp Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: All OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: jmcdaniel3(a)austin.rr.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20100101 Firefox/11.0 Running the (bash script) command: /usr/bin/grub2-kbdcomp Produces the output: /usr/bin/grub2-kbdcomp: line 11: ckbcomp: command not found ERROR: no keycodes found. Check output of ckbcomp. The reason is that the application ckbcomp is not installed. DESCRIPTION The ckbcomp keymap compiler converts a description of an XKB keymap into a console keymap that can be read directly by loadkeys. Reproducible: Always Steps to Reproduce: 1. Type command: /usr/bin/grub2-kbdcomp as root 2. Get error output due to missing ckbcomp application 3. Actual Results: /usr/bin/grub2-kbdcomp: line 11: ckbcomp: command not found ERROR: no keycodes found. Check output of ckbcomp. Expected Results: The ckbcomp keymap compiler converts a description of an XKB keymap into a console keymap that can be read directly by loadkeys. -- 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 6

[Bug 853868] New: 1. stage mkinitrd ends with error
by bugzilla_noreply＠novell.com 10 Feb '14

10 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=853868 https://bugzilla.novell.com/show_bug.cgi?id=853868#c0 Summary: 1. stage mkinitrd ends with error Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: yast2-maintainers(a)suse.de ReportedBy: gjn(a)gjn.priv.at QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 This is a UEFI installation with secure boot enabled. (Asus P9D WS) should or must this configuration work ? in this system is a Raid controller LSI 9271-i8 On the Bootable Drive (Raid 10) is win installed, we have a second Drive Raid1 SSD, on this I like to install opensuse 13.1 When I configure to install with the existing EFI Partition (Raid10) mkinitrd can't create the Files for Kernel initrd... or can't write the Grub-efi Boot Config Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 21