March 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 731499] New: Rescue May Require mount --bind of /run
by bugzilla_noreply＠novell.com 12 Mar '13

12 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=731499 https://bugzilla.novell.com/show_bug.cgi?id=731499#c0 Summary: Rescue May Require mount --bind of /run Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: rogers(a)isi.edu QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.2.24) Gecko/20111103 Firefox/3.6.24 Comments by Steffen Winterfeldt in bugzilla bug 717321 imply that starting with openSUSE 12.1, it may be necessary to mount --bind /run in addition to /dev, /run and /sys, prior to chrooting to perform certain rescue activities. I realize that rescue mode is intended for power users, but perhaps some documentation would help, or perhaps even a chroot helper script could be included on the rescue disk? Reproducible: Always Steps to Reproduce: 1.Install or upgrade openSUSE 12.1 2.Encounter a problem that prevents the system from rebooting. 3.Enter Rescue mode, mount the target system, mount --bind various things, and chroot. Attempt a fix, such as by running yast. Actual Results: Perhaps this explains my lack of success with attempting to use yast to update my grub configuration? Expected Results: Programs should work properly in the chroot environment. I can't guarantee that not applying mount --bind to /run caused my attempt to use yast to fail. Perhaps I'll run into similar circumstances when I attempt more updates to openSUSE 12.1. If so, I'll submit a more specific bug report. However, I felt motivated to report the introduction of "/run" as a possible progenitor of problems. While I'm at it, I'd like to mention that: http://www.novell.com/documentation/ does not have a section for openSUSE 12.1. Is it intended to keep updating the "www.novell.com" with reference documentatin for openSUSE, or will I start to see documentation appear on "opensuse.org"? -- 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 3

[Bug 733181] New: Fine-tuning for boot menu settings of "Memtest86+"
by bugzilla_noreply＠novell.com 12 Mar '13

12 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=733181 https://bugzilla.novell.com/show_bug.cgi?id=733181#c0 Summary: Fine-tuning for boot menu settings of "Memtest86+" Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Markus.Elfring(a)web.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- The following entry was added to my configuration file "/boot/grub/menu.lst" by the package "memtest86+ 4.20-3.1.1". ###Don't change this comment - YaST2 identifier: Original name: linux### title Memory Test (memtest86+) -- openSUSE 12.1 - Memory Test (memtest86+) kernel (hd2,1)/memtest.bin root=/dev/duda/root resume=/dev/disk/by-id/ata-SAMSUNG_SP2504C_S09QJ1UA109248-part5 splash=silent quiet showopts vga=0x31b Would you like to avoid the duplicate wording? How do you think about to omit the parameters "root", "resume" and "splash" for this application? -- 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 3

[Bug 727243] New: Memtest not in boot menu
by bugzilla_noreply＠novell.com 12 Mar '13

12 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=727243 https://bugzilla.novell.com/show_bug.cgi?id=727243#c0 Summary: Memtest not in boot menu Classification: openSUSE Product: openSUSE 12.1 Version: RC 1 Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: james.knott(a)rogers.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.4) Gecko/20100611 SUSE/3.6.4-6.1 Firefox/3.6.4 I installed memtest on 12.1 RC1 and moved it to the bottom of the boot list. After rebooting, memtest was not listed as a boot option. In Yast > Boot Loader, memtest is no longer listed, even though Software Management shows it is installed. Even trying to manually add memtest.bin fails. Reproducible: Always Steps to Reproduce: 1.Install memtest 2.Move in boot list (not sure if this step required) 3.Reboot Actual Results: Memtest is no longer a boot option and does not appear in Yast > Boot Loader Expected Results: Memtest should be in the boot list on reboot. -- 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 13

[Bug 734778] New: Open SuSE 12.1 64bit DVD install fails to update boot loader
by bugzilla_noreply＠novell.com 12 Mar '13

12 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=734778 https://bugzilla.novell.com/show_bug.cgi?id=734778#c0 Summary: Open SuSE 12.1 64bit DVD install fails to update boot loader Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: stevet(a)copper.net QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20100101 Firefox/8.0 I got the iso and did an md5 check. Good. Booted the DVD and told it to check itself. Good. Did the install to /dev/sdb3 as an update install (from 11.1 64 bit). Have tried it three times, changing an option here and there. The end result is, the GRUB on /dev/sda1 is not updated to include the updated partition. It did see that /home is on a raid (md0). Reproducible: Always Steps to Reproduce: 1. Boot the DVD 2. Tell it to do an update boot 3. Allow the new boot process through the DVD (or manually do it w/ no DVD) and the GRUB loader menu does not contain the updated partition. Actual Results: The sdb3 partition does not have a file system that the SuSE 11.4 system knows about. Expected Results: I expected the 12.1 system to boot up, choke to death on the RAID "/home" (as it has on the last three SuSE releases) and have to fix a few things and then have it take off and work As I understand it, GRUB should have actually been replaced. The sdb1 partition did not have a loader in it (which it was setup for), and the sdb2 is a swap partition. sdb4 is the mirror copy of sda4 which is the /home partition. Using an AMD 2 core CPU with 8GB of RAM. The 11.4 system runs great out of sda3. -- 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 11

[Bug 679134] New: installer crash when not enough memory
by bugzilla_noreply＠novell.com 12 Mar '13

12 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=679134 https://bugzilla.novell.com/show_bug.cgi?id=679134#c0 Summary: installer crash when not enough memory Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: All OS/Version: All Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: modulistic(a)gmail.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b12) Gecko/20110222 Firefox/4.0b12 The installation process crashes in a dirty way when there is not enough memory. Reproducible: Always Steps to Reproduce: 1. Set up a virtualbox container with 128Mb RAM 2. Boot openSUSE-11.4-NET-x86_64.iso or equivalent (x86_64 is not a requirement) Actual Results: Installation process crashes with fireworks "Starting udev... sh: line 1: 103 Killed /bin/myudevstart" and goes a slightly bit deeper when choosing "Safe Settings Kernel". When booting straight into the installer, the boot splash keeps the error messages hidden, with a stale progress indicator. Both paths look like something broken or a nasty hardware incompatibility. Expected Results: The installation procedure should check the amount of available memory and properly report if there is not enough of it before aborting. It would be very cool if the installation procedure launched the text-based installer when there is enough memory for it to perform its duty (is a full installer this text-based default that comes up when something bad happens?) I am filing this as a bug report instead of a feature request because it gives the impression that the product is buggy or incompatible with some hardware. In my case I got this error while trying to install a minimal server with no X inside VirtualBox, and one of the options that came to my mind was to default to 11.3 instead, as I was in a hurry. -- 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 3

[Bug 728634] New: USB drive not loaded on boot (necessary for upgrade from RC1->RC2)
by bugzilla_noreply＠novell.com 12 Mar '13

12 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=728634 https://bugzilla.novell.com/show_bug.cgi?id=728634#c0 Summary: USB drive not loaded on boot (necessary for upgrade from RC1->RC2) Classification: openSUSE Product: openSUSE 12.1 Version: RC 1 Platform: x86 OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: howard.bryan.webb(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=460678) --> (http://bugzilla.novell.com/attachment.cgi?id=460678) /var/log/messages of boot, showing systemd/dbus msgs and USB disk not mounting User-Agent: Mozilla/5.0 (X11; Linux i686; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 Using 12.1 RC1, I believe I have the same problem as Bug#728542 (USB drives not loaded when plugged in). This problem is preventing me from upgrading to RC2!!!! or anything else :-( I got a copy of the 12.1 RC2 DVD ISO, and used the RC1 imagewriter (1.9) to copy the RC2 ISO to my USB stick. Because of the preference of my BIOS for windows, I cannot directly boot the ISO image. Instead, I am forced to boot RC1, then use a modified Grub entry to boot from the USB stick kernel image (which does the RC2 install). However, at the time Grub comes up, only the hard disk partitions are seen, not the USB stick ISO image partition!! So, I can never leave RC1 to upgrade to RC2 or anything else! Please help Since I cannot boot any USB image, I thought that the regular RC1 kernel should be the same as the ISO kernel in this regard. So, I supplied a bunch of systemd.* parameters on the command line that can hopefully guide you (1) to a fix, and (2) to help me out of this jam. So I boot the system, log in, and df: webbb@t4:~> df Filesystem 1K-blocks Used Available Use% Mounted on rootfs 153842884 19831040 126197028 14% / devtmpfs 1432796 60 1432736 1% /dev tmpfs 1439360 272 1439088 1% /dev/shm tmpfs 1439360 724 1438636 1% /run /dev/sda5 153842884 19831040 126197028 14% / tmpfs 1439360 0 1439360 0% /sys/fs/cgroup tmpfs 1439360 0 1439360 0% /media tmpfs 1439360 724 1438636 1% /var/lock tmpfs 1439360 724 1438636 1% /var/run /dev/sda1 156264220 48976636 107287584 32% /winxp2 /dev/sdb5 41283648 967348 38219048 3% /114 /dev/sdb1 185427 84641 91212 49% /114/boot /dev/sdb6 41283648 13244360 25942088 34% /114/usr /dev/sdb9 10316088 164580 9627476 2% /114/tmp /dev/sdb8 10317112 805620 8987412 9% /114/var /dev/sdb7 198032640 40494988 147477776 22% /114/home /dev/sdc is missing from the list of drives just like it would have been when booting from the ISO image: When looking at the attached /var/log/messages (messages.txt) file, sdc is the disk 4:0:0:0 is how it's known as a hardware resource (I think) CENTON is the mfgr name USB port 1-2 Reproducible: Always Steps to Reproduce: 1. Use imagewriter to write RC2 (or any) ISO image to a USB stick 2. Modify grub.lst to boot from USB stick /dev/sdc 3. Boot (hard disk) RC1 to initial grub screen 4. Verify that sdc is NOT known to the system (though it should be) 5. Attempt to boot USB stick entry, but it will never work. Actual Results: When grub list is displayed, /dev/sdc (the USB stick ISO image) is not known to the system, so boot errors occur. Expected Results: Expect to boot into the USB stick ISO, to upgrade to RC2 or whatever. -- 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 731823] New: HDIO_GET_IDENTITY failed x64_68
by bugzilla_noreply＠novell.com 12 Mar '13

12 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=731823 https://bugzilla.novell.com/show_bug.cgi?id=731823#c0 Summary: HDIO_GET_IDENTITY failed x64_68 Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: tneo(a)gmx.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Opera/9.80 (X11; Linux x86_64; U; en) Presto/2.9.168 Version/11.52 Installation through burned DVD (with correct checksum). Tried installing with safe settings, but same result. After completing the installation, selecting Gnome 3 as DE, the initial reboot fails. It staits HDIO_GET_IDENTITY failed /dev/sde It drops me to the "emergency console", but I have no clue what to there. My config is ain raid1, where /md125 = /, /md126 = /boot and /md127 = /home All formated with ext4 Prior to the message a fsck is done on the md device and that was successful. The follow mounting of / is correct as well. Reproducible: Always Steps to Reproduce: 1. Insert DVD and perfom install 2. Wait until the first reboot af the new install 3. Actual Results: System is not booted correctly and states a HDIO_GET_IDENTITY error message Expected Results: Finish the installation process or provide clear instruction on what to do -- 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 11

[Bug 676416] New: updating 11.3 to 11.4 via zypper dist: system start gives GRUB without anything.
by bugzilla_noreply＠novell.com 12 Mar '13

12 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=676416 https://bugzilla.novell.com/show_bug.cgi?id=676416#c0 Summary: updating 11.3 to 11.4 via zypper dist: system start gives GRUB without anything. Classification: openSUSE Product: openSUSE 11.4 Version: RC 2 Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)novell.com ReportedBy: roeland(a)linux-it.nl QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101203 SUSE/3.6.13-3.1 Firefox/3.6.13 the system ran 11.3 patched on KVM (e.g. /dev/vda1 for boot and /dev/vda2 for the rest) -- I changed the installation sources to point to 11.4 and did a dist upgrade via zypper. all went well, no error at all. Restarted the system and the system ended with GRUB without any error at all. Using rescue, was not able to find /dev/vda2, the rootfs. Collegue of mine who had vnc access, used http://bugs.gentoo.org/259613 and fixed the setup with that bug info. Reproducible: Always Steps to Reproduce: 1. use kvm 11.3 2. change inst source to 11.4 (rc2 at the moment) 3. dist upgrade and reboot Actual Results: GRUB is displayed, no boot Expected Results: it should come up http://bugs.gentoo.org/259613 seems to be the fix -- 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 679163] New: BIOS hangs booting from 11.4 64bit-installation DVD on some HP notebooks
by bugzilla_noreply＠novell.com 12 Mar '13

12 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=679163 https://bugzilla.novell.com/show_bug.cgi?id=679163#c0 Summary: BIOS hangs booting from 11.4 64bit-installation DVD on some HP notebooks Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: d.novell(a)grafenhofer.at QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b12) Gecko/20110222 Firefox/4.0b12 Trying to boot from the 64-bit installation dvds of opensuse 11.4 fails on diverse HP Laptops. Starting up hangs displaying the BIOS startup screen. Diverse LED indicator items are blinking (indicating a wrong FS type according to HP support). Md5 checks and verification of dvd contents have been carried out. The same DVD boots fine on other machines. Also different brands, and DVD standards (+/-,R/RW) have been tried out. The affected machines have no trouble booting other installation media, like the opensuse 11.3 64-bit installation dvd. Everything hints at a BIOS bug instead of an opensuse issue. The following machines are reported up to now to be hit by the problem: HP Elitebook 8530p (my machine) HP ProBook 4710 HP Elitebook 6930p (Dirty) workaround: 1. Boot from opensuse 11.3 64-bit installation dvd 2. Halt boot when the grub menu appears 3. Eject the 11.3 dvd, replace it by the 11.4 one, and wait until the 11.4 dvd spins up 4. Then select "Installation" from the grub menu Related forum entries: http://forums.opensuse.org/english/get-technical-help-here/install-boot-log… http://forums.opensuse.org/english/get-technical-help-here/install-boot-log… Reproducible: Always Steps to Reproduce: 1. Insert install dvd 2. Turn on notebook 3. BIOS hangs -- 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 703581] New: Network installation from factory fails
by bugzilla_noreply＠novell.com 12 Mar '13

12 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=703581 https://bugzilla.novell.com/show_bug.cgi?id=703581#c0 Summary: Network installation from factory fails Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: i686 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: casualprogrammer(a)opensuse.org QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:5.0) Gecko/20100101 Firefox/5.0 Trying to install openSUSE 12.1 Mileston2 from http://download.opensuse.org/factory/repo/oss fails, as neither keyboard nor mouse are accessible after download and start of installation system. The screen displays the installation setup plus the initial YAST2 message box making aware of installing beta software ( "openSUSE Beta Distribution version openSUSE 12.1 Milestone 2...") waiting for OK to be pressed. Pressing any key or trying to move the cursor has no effect, the only working button is the power switch. Reproducible: Always Steps to Reproduce: 1. Boot from DVD 2. Press F4 Source 3. Choose HTTP 4. Enter Server and Directory 5. Choose Installation from the Menu 6. Loading Installation System ( 6 files ) 7. Display of Installation Environment plus YAST2 Message Box -- 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 3