January 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1017737] New: [doc] [grub2] Location of 'boot code options tab' section
by bugzilla_noreply＠novell.com 04 Jan '17

04 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1017737 Bug ID: 1017737 Summary: [doc] [grub2] Location of 'boot code options tab' section Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Documentation Assignee: fs(a)suse.com Reporter: richard.bos(a)xs4all.nl QA Contact: fs(a)suse.com Found By: --- Blocker: --- 12.3.3.3 <span class="guimenu">Boot Code Options</span> Tab https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.re… This section seems misplaced, it's part of the tab that is described in 12.3.1 https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.re… As such it seems logical to explain the additional settings right after section 12.3.1. It would prevent a lot of scrolling up and down between the two sections ( for the screenshot of the tab ). [] Set Active Flag in Partition Table for Boot Partition Activates the partition that contains the boot loader. Some legacy operating systems (such as Windows) can only boot from an active partition. - Remark: what is the advice for Linux (openSUSE) based systems? Should the following text be added: "For Linux (openSUSE) based systems this setting does not need to be enabled." [] Write Generic Boot Code to MBR Replaces the current MBR with generic, operating system independent code. - Remark: what is the advice: should this be enabled for Linux (openSUSE) based systems? Is it possible to add such an advice to the documentation. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 959230] Ralink 5370 wifi connection stalls
by bugzilla_noreply＠novell.com 04 Jan '17

04 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=959230 http://bugzilla.suse.com/show_bug.cgi?id=959230#c27 --- Comment #27 from Toomas Aas <toomas.aas(a)eesti.ee> --- No, but I know how to google :) I'll try bisecting and post the updates once I have something. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1017677] New: Better bootloader help
by bugzilla_noreply＠novell.com 04 Jan '17

04 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1017677 Bug ID: 1017677 Summary: Better bootloader help Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: openSUSE 42.2 Status: NEW Severity: Minor Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: richard.bos(a)xs4all.nl QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 708132 --> http://bugzilla.opensuse.org/attachment.cgi?id=708132&action=edit Bootloader help screen I'm in the process of moving an openSUSE (13.1) instance from one partition (/dev/sda3) to another at another disk (/dev/sdb6). It's a long bug report. Use it please to look carefully at the bootloader help and hopefully with the information I provide below, you can provide the best bootloader help of all linux distributions. Use case: As such I don't want to alter the bootloader config that is stored for /dev/sda. I want the bootloader config to be stored at /dev/sdb. With the idea that during the boot I select the disk to boot from (sdb), and use the bootloader that is located at that disk.... For the interested, it's like a bit as described in this article: http://sysadmin.compxtreme.ro/how-to-migrate-a-single-disk-linux-system-to-… In this article grub2-mkconfig grub-install /dev/sda grub-install /dev/sdb are used, but these commands are hidden by yast-bootloader. Back to yast bootloader: The help about 'edit disk boot order' states: "Disks Order To specify the order of the disks according to the order in BIOS, ......" Why is this boot order depending on the order in the bios? Is another (random) disk order allowed as well, if so what would be consequence? The boot loader location: what are the advantages of the three different boot loader locations (boot from root partition, MBR or custom partition? This is not mentioned at all in the help. In case of custom partition, can it be any partition (swap? A partition for /home or /srv or must e.g. /boot be located at the partition?). BTW: Why is it not: Boot from Custom Boot partition, just like the other two option. The menu can then become: Boot from: [] Root Partition [] Master Boot Record [] Custom Boot Partition Hmm, what is meant with Root Partition? The Root partition of what (when there are multiple openSUSE's on the disk, which root partition). And should it be 'Custom Root Partition' or indeed be boot partition (with /boot on it)? Is it possible to provide a drop down list of possible (boot) partitions for the custom Boot partition? BTW why is it called 'custom boot partition', why not just 'custom partition'? When should "write generic boot code to mbr" be used? There is no advice about that in the help. What happens when 'set active flag in parttion table for boot (root?? see boot loader location section above ) partition' is not used? In other words is it required, if so when and how. When all is set and configured, and the user clicks OK to get the bootloader created is it an idea to show a summary screen to show what settings have been chosen. After confirmation of the proposal continue created / changing the bootloader. As stated in the beginning, please consider improving the bootloader help based on my questions and remarks above. The bootloader may be obvious for the regular bootloader user, but may not be obvious for others ( although I'm an experienced linux user, so that is not the issue ). Looking forward to the improvements, hopefully already in 42.3! PS: I selected component bootloader, but perhaps yast2 is better -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1016607] i915 blinks; regression?
by bugzilla_noreply＠novell.com 04 Jan '17

04 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=1016607 http://bugzilla.suse.com/show_bug.cgi?id=1016607#c5 --- Comment #5 from Kenneth Ingham <ingham(a)i-pi.com> --- Created upstream bug: https://bugs.freedesktop.org/show_bug.cgi?id=99276 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1017938] Kernel 4.9: amdgpu regression; gui flickers
by bugzilla_noreply＠novell.com 04 Jan '17

04 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=1017938 http://bugzilla.suse.com/show_bug.cgi?id=1017938#c2 --- Comment #2 from Reimar Imhof <tuxuser(a)quantentunnel.de> --- filed bug report https://bugs.freedesktop.org/show_bug.cgi?id=99275 and put you to cc -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1017765] [yast2/bootloader]: Make it possible to exclude foreign OS' from the bootloader menu
by bugzilla_noreply＠novell.com 04 Jan '17

04 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=1017765 http://bugzilla.suse.com/show_bug.cgi?id=1017765#c5 --- Comment #5 from Richard Bos <richard.bos(a)xs4all.nl> --- Remark: it nicer although longer Operation System instead OS. There is sufficient space to write it full. As such the current 'Probe for foreign OS' can be become: Probe for foreign Operating System or Probe for other installed Operating Systems. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1017761] [yast2/bootloader]: Make it possible to save the bootloader to different disks for redundancy
by bugzilla_noreply＠novell.com 04 Jan '17

04 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=1017761 http://bugzilla.suse.com/show_bug.cgi?id=1017761#c3 Richard Bos <richard.bos(a)xs4all.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(richard.bos@xs4al | |l.nl) | --- Comment #3 from Richard Bos <richard.bos(a)xs4all.nl> --- > So this feature is already there, but it is never trivial recovery and > hardware raid works always more reliable. > > If this do not work for you, please attach logs, so I can see why it do > not work for you as it should be default install to both locations. I can't test it (now. Perhaps it is possibly in the future, but I really don't know when). According the docu, the default value is to save to Root partition and not to save to MBR... It is also not documented (not that I'm aware of) that in a RAID configuration the MBR is written to both disks... Is this GUI wise: Install bootloader at: [x] sda [x] sdb [x] sd...., etc when there are more disks Not easy to understand from a user point of view.... Allow multiple disk selection when applicable. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1016607] i915 blinks; regression?
by bugzilla_noreply＠novell.com 04 Jan '17

04 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=1016607 http://bugzilla.suse.com/show_bug.cgi?id=1016607#c4 --- Comment #4 from Kenneth Ingham <ingham(a)i-pi.com> --- The problem still exists in kernel-default-4.9.0-2.1.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1016607] i915 blinks; regression?
by bugzilla_noreply＠novell.com 04 Jan '17

04 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=1016607 http://bugzilla.suse.com/show_bug.cgi?id=1016607#c3 Kenneth Ingham <ingham(a)i-pi.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(ingham(a)i-pi.com) | --- Comment #3 from Kenneth Ingham <ingham(a)i-pi.com> --- Created attachment 708590 --> http://bugzilla.suse.com/attachment.cgi?id=708590&action=edit hwinfo output for affected system -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1018172] New: NTP hangs for an arbitrary amount of time on shutdown with no network connection
by bugzilla_noreply＠novell.com 04 Jan '17

04 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1018172 Bug ID: 1018172 Summary: NTP hangs for an arbitrary amount of time on shutdown with no network connection Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: aarch64 OS: openSUSE 42.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: alan(a)softiron.co.uk QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi, NTP hangs at shutdown for some arbitrary amount of time. 1. Boot Leap 42.2 on aarch64 with no network connected 2. login and run "shutdown -h now" 3. Observe: [ **] A stop job is running for NTP Server Daemon (10s / 1min 30s) The duration of the hang seems to be arbitrary[1]. It's completely reproducible when no network is connected. Thanks for having a look! Alan. [1] ie: the "10s" above is just where it was when I copied it. -- You are receiving this mail because: You are on the CC list for the bug.

1 0