April 2016 - openSUSE Factory - openSUSE Mailing Lists

Re: [opensuse-factory] EFI bootloader broken during update of Tumbleweed
by Andrei Borzenkov 21 Apr '16

21 Apr '16

09.04.2016 00:16, Daniel Morris пишет: > On Fri, Apr 08, 2016 at 07:46:39PM +0300, Andrei Borzenkov wrote: >> 08.04.2016 19:23, Daniel Morris пишет: >>> But the net effect is the same. >> >> Unfortunately you forgot to tell what happens when you boot. >> >>> It seems as though the step between EFI >>> and grub2 is missing. Could anyone suggest where to look next? >> >> Please show "efibootmgr -v" output and describe what happens when system >> boots. >> > > chunk:~ # efibootmgr -v > efibootmgr: EFI variables are not supported on this system. > You are booted in legacy BIOS mode. > The BIOS complains that it can't find a bootable medium, asks for one to > be inserted. The SSD is the first detected drive from the BIOS and the > highest priority, with the DVD drive next. > Which hints again that your firmware attempts legacy BIOS boot. > I'm currently having to boot the system via the Tumbleweed DVD > (selecting /dev/sda3 and picking one of the kernels found etc), but it > worked fine for three months and I've not made any changes to the BIOS > config. > May be. The fact is that based on your description firmware tries legacy BIOS boot and not EFI. This is outside of control of either bootloader or operating system. If you think this is wrong you need to verify your "BIOS" settings. That is something we cannot do from here, sorry. Or please make sure to actually boot in EFI mode and provide "efibootmgr -v" output again so we can verify firmware bootmanager setup. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 15

Re: [opensuse-factory] EFI bootloader broken during update of Tumbleweed
by Daniel Morris 21 Apr '16

21 Apr '16

Firstly, thank you for your help and patience - I am pleased to report I now have a booting system. It wasn't quite plain sailing, further details below (just in case it helps anyone in the future). On Tue, Apr 12, 2016 at 03:39:19PM -0600, Chris Murphy wrote: > On Tue, Apr 12, 2016 at 11:47 AM, Daniel Morris <danielm(a)ecoscentric.com> wrote: > > chunk:~ # efibootmgr > > BootCurrent: 0003 > > Timeout: 2 seconds > > BootOrder: 0003,0001,0002,0004 > > Boot0001* Hard Drive > > Boot0002* CD/DVD Drive > > Boot0003* UEFI: USB > > Boot0004 Removable Drive > > Well, the BootOrder and the Boot numbers don't include an opensuse > option anymore. Is this a complete list? And yet, the fallback for > bootx64.efi isn't happening. Huh. Definitely weird. Yup! > > Please post the results for all of the following: > > # ls -l /sys/firmware/efi/efivars/ > # dd if=/dev/sda count=1 2>/dev/null | hexdump -C > # efibootmgr -v > # efibootmgr -c -w -L openSUSE -d /dev/sda -p 1 -l \\EFI\\opensuse\\shim.efi > # efibootmgr -v chunk:~ # ls -l /sys/firmware/efi/efivars/ total 0 -rw-r--r-- 1 root root 8 Apr 20 14:27 AAFTaddr-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9 -rw-r--r-- 1 root root 37 Apr 20 14:27 AMITSESetup-c811fa38-42c8-4579-a9bb-60e94eddfb34 -rw-r--r-- 1 root root 7 Apr 20 14:27 ASR_USER_DEF_TSE-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9 -rw-r--r-- 1 root root 5 Apr 20 14:27 ASR_USER_DEF_VER-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9 -rw-r--r-- 1 root root 8 Apr 20 14:27 AcpiGlobalVariable-af9ffd67-ec10-488a-9dfc-6cbf5ee22c2e -rw-r--r-- 1 root root 1210 Apr 20 14:27 Boot0001-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r-- 1 root root 224 Apr 20 14:27 Boot0002-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r-- 1 root root 154 Apr 20 14:27 Boot0003-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r-- 1 root root 154 Apr 20 14:27 Boot0004-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r-- 1 root root 6 Apr 20 14:27 BootCurrent-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r-- 1 root root 8 Apr 20 14:27 BootFlow-ef152fb4-7b2f-427d-bdb4-7e0a05826e64 -rw-r--r-- 1 root root 12 Apr 20 14:27 BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r-- 1 root root 68 Apr 20 14:27 Boot_Dev_name-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r-- 1 root root 5 Apr 20 14:27 Boot_Last_Device-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9 -rw-r--r-- 1 root root 72 Apr 20 14:27 ConIn-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r-- 1 root root 72 Apr 20 14:27 ConInDev-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r-- 1 root root 34 Apr 20 14:27 ConOut-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r-- 1 root root 34 Apr 20 14:27 ConOutDev-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r-- 1 root root 12 Apr 20 14:27 DefaultBootOrder-45cf35f6-0d6e-4d04-856a-0370a5b16f53 -rw-r--r-- 1 root root 40 Apr 20 14:27 DefaultLegacyDevOrder-3c4ead08-45ae-4315-8d15-a60eaa8caf69 -rw-r--r-- 1 root root 34 Apr 20 14:27 ErrOut-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r-- 1 root root 34 Apr 20 14:27 ErrOutDev-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r-- 1 root root 8 Apr 20 14:27 EzConfigData-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9 -rw-r--r-- 1 root root 5 Apr 20 14:27 GoodNightLed-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9 -rw-r--r-- 1 root root 32 Apr 20 14:27 HddBootDev-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9 -rw-r--r-- 1 root root 8 Apr 20 14:27 HddInfo4_InitStrings_HiiHandle-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9 -rw-r--r-- 1 root root 12 Apr 20 14:27 HiiDB-1b838190-4625-4ead-abc9-cd5e6af18fe0 -rw-r--r-- 1 root root 12 Apr 20 14:27 HobRomImage-dde1bc72-d45e-4209-ab85-14462d2f5074 -rw-r--r-- 1 root root 48 Apr 20 14:27 IccAdvancedSetupDataVar-7b77fb8b-1e0d-4d7e-953f-3980a261e077 -rw-r--r-- 1 root root 7 Apr 20 14:27 Lang-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r-- 1 root root 7 Apr 20 14:27 LangCodes-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r-- 1 root root 40 Apr 20 14:27 LegacyDevOrder-a56074db-65fe-45f7-bd21-2d2bdd8e9652 -rw-r--r-- 1 root root 5 Apr 20 14:27 LoadSetupDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r-- 1 root root 8 Apr 20 14:27 MemCeil.-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r-- 1 root root 8 Apr 20 14:27 MonotonicCounter-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r-- 1 root root 3028 Apr 20 14:27 MrcS3Resume-87f22dcb-7304-4105-bb7c-317143ccc23b -rw-r--r-- 1 root root 21 Apr 20 14:27 NBPlatformData-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9 -rw-r--r-- 1 root root 140 Apr 20 14:27 NvRamSpdMap-717fc150-abd9-4614-8015-0b3323eab95c -rw-r--r-- 1 root root 28 Apr 20 14:27 OA3MSDMvariable-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r-- 1 root root 14 Apr 20 14:27 OemCpuData-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9 -rw-r--r-- 1 root root 40 Apr 20 14:27 OldLegacyDevOrder-a56074db-65fe-45f7-bd21-2d2bdd8e9652 -rw-r--r-- 1 root root 13 Apr 20 14:27 PLLOvFlag-181e874d-c089-4c99-8ec2-6d6761348220 -rw-r--r-- 1 root root 7 Apr 20 14:27 PNP0400_0_NV-560bf58a-1e0d-4d7e-953f-2980a261e031 -rw-r--r-- 1 root root 13 Apr 20 14:27 PNP0400_0_VV-560bf58a-1e0d-4d7e-953f-2980a261e031 -rw-r--r-- 1 root root 7 Apr 20 14:27 PNP0501_0_NV-560bf58a-1e0d-4d7e-953f-2980a261e031 -rw-r--r-- 1 root root 13 Apr 20 14:27 PNP0501_0_VV-560bf58a-1e0d-4d7e-953f-2980a261e031 -rw-r--r-- 1 root root 7 Apr 20 14:27 PNP0501_1_NV-560bf58a-1e0d-4d7e-953f-2980a261e031 -rw-r--r-- 1 root root 13 Apr 20 14:27 PNP0501_1_VV-560bf58a-1e0d-4d7e-953f-2980a261e031 -rw-r--r-- 1 root root 7 Apr 20 14:27 PNP0510_0_NV-560bf58a-1e0d-4d7e-953f-2980a261e031 -rw-r--r-- 1 root root 13 Apr 20 14:27 PNP0510_0_VV-560bf58a-1e0d-4d7e-953f-2980a261e031 -rw-r--r-- 1 root root 7 Apr 20 14:27 PNP0604_0_NV-560bf58a-1e0d-4d7e-953f-2980a261e031 -rw-r--r-- 1 root root 13 Apr 20 14:27 PNP0604_0_VV-560bf58a-1e0d-4d7e-953f-2980a261e031 -rw-r--r-- 1 root root 8 Apr 20 14:27 PchInit-e6c2f70a-b604-4877-85ba-deec89e117eb -rw-r--r-- 1 root root 20 Apr 20 14:27 PchS3Peim-e6c2f70a-b604-4877-85ba-deec89e117eb -rw-r--r-- 1 root root 10 Apr 20 14:27 PlatformLang-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r-- 1 root root 10 Apr 20 14:27 PlatformLangCodes-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r-- 1 root root 5 Apr 20 14:27 Q_ASR_QUICKON-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9 -rw-r--r-- 1 root root 12 Apr 20 14:27 S3SS-4bafc2b4-02dc-4104-b236-d6f1b98d9e84 -rw-r--r-- 1 root root 28 Apr 20 14:27 SaPegData-c4975200-64f1-4fb6-9773-f6a9f89d985e -rw-r--r-- 1 root root 8 Apr 20 14:27 SbAslBufferPtrVar-01f33c25-764d-43ea-aeea-6b5a41f3f3e8 -rw-r--r-- 1 root root 12 Apr 20 14:27 ScramblerBaseSeed-87f22dcb-7304-4105-bb7c-317143ccc23b -rw-r--r-- 1 root root 8 Apr 20 14:27 Setup-80e1202e-2697-4264-9cc9-80762c3e5863 -rw-r--r-- 1 root root 679 Apr 20 14:27 Setup-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9 -rw-r--r-- 1 root root 17 Apr 20 14:27 SetupPlatformData-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9 -rw-r--r-- 1 root root 14 Apr 20 14:27 SetupSnbPpmFeatures-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9 -rw-r--r-- 1 root root 1203 Apr 20 14:27 StdDefaults-4599d26f-1a11-49b8-b91f-858745cff824 -rw-r--r-- 1 root root 5 Apr 20 14:27 TdtAdvancedSetupDataVar-7b77fb8b-1e0d-4d7e-953f-3980a261e076 -rw-r--r-- 1 root root 6 Apr 20 14:27 Timeout-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r-- 1 root root 5 Apr 20 14:27 TxtFeatures-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9 -rw-r--r-- 1 root root 12 Apr 20 14:27 USB_POINT-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r-- 1 root root 6 Apr 20 14:27 UsbMassDevNum-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9 -rw-r--r-- 1 root root 20 Apr 20 14:27 UsbMassDevValid-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9 -rw-r--r-- 1 root root 35 Apr 20 14:27 UsbSupport-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9 -rw-r--r-- 1 root root 5 Apr 20 14:27 WdtPersistentData-78ce2354-cfbc-4643-aeba-07a27fa892bf chunk:~ # dd if=/dev/sda count=1 2>/dev/null | hexdump -C 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 000001c0 01 00 ee fe ff ff 01 00 00 00 af 4b f9 0d 00 00 |...........K....| 000001d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.| 00000200 chunk:~ # efibootmgr -v BootCurrent: 0004 Timeout: 1 seconds BootOrder: 0001,0002,0004,0003 Boot0001* Hard Drive BBS(HD,,0x0)AMGOAMNO........o.S.a.m.s.u.n.g. .S.S.D. .8.4.0. .E.V.O. .1.2.0.G.B....................A...........................>..Gd-.;.A..MQ..L.1.S.5.D.S.N.F.B.1.3.5.4.5.3. .J. . . . ......AMBOAMNO........q.S.a.n.D.i.s.k. .U.l.t.r.a. .I.I. .4.8.0.G.B.........................rN.D+..,.\...........B..Gd-.;.A..MQ..L.S.a.n.D.i.s.k. .U.l.t.r.a. .I.I. .4.8.0.G.B......AMBOAMNO........c.S.A.M.S.U.N.G. .H.D.1.0.3.S.J.........................rN.D+..,.\...........4..Gd-.;.A..MQ..L.S.A.M.S.U.N.G. .H.D.1.0.3.S.J......AMBOAMNO........c.S.A.M.S.U.N.G. .H.D.1.0.3.S.J.........................rN.D+..,.\...........4..Gd-.;.A..MQ..L.S.A.M.S.U.N.G. .H.D.1.0.3.S.J......AMBOAMNO........o.S.a.m.s.u.n.g. .S.S.D. .8.4.0. .E.V.O. .1.2.0.G.B....................A...........................>..Gd-.;.A..MQ..L.1.S.5.D.S.N.F.B.1.3.7.4.8.9. .M. . . . ......AMBOAMNO........o.S.A.M.S.U.N.G. .H.D.7.5.3.L.J....................A...........................>..Gd-.;.A..MQ..L.1.S.U.3.X.J.B.0.0.3.6.0.3.9. . . . . . ......AMBOAMNO........o.S.A.M.S.U.N.G. .H.D.1.0.3.U.J....................A...........................>..Gd-.;.A..MQ..L.1.S.P.3.9.J.Q.0.2.A.9.5.6.3. . . . . . ......AMBO Boot0002* CD/DVD Drive BBS(CDROM,,0x0)AMGOAMNO........o.A.T.A.P.I. . . .i.H.A.S.3.2.4. . . .B....................A...........................>..Gd-.;.A..MQ..L.5.3.4.2.1.2. .9.4.3.0.8.4.4.0.5.9.0.8.5......AMBO Boot0003 USB BBS(USB,,0x0)AMGOAMNOu.......U.U.S.B.2...0....................A............................."..Gd-.;.A..MQ..L.U.S.B.2...0......AMBO Boot0004* UEFI: USB2.0 PciRoot(0x0)/Pci(0x1a,0x0)/USB(1,0)/USB(1,0)/HD(1,MBR,0x4294967218,0x118,0x1d88)AMBO chunk:~ # efibootmgr -c -w -L openSUSE -d /dev/sda -p 1 -l \\EFI\\opensuse\\shim.efi BootCurrent: 0004 Timeout: 1 seconds BootOrder: 0000,0001,0002,0004,0003 Boot0001* Hard Drive Boot0002* CD/DVD Drive Boot0003 USB Boot0004* UEFI: USB2.0 Boot0000* openSUSE chunk:~ # efibootmgr -v BootCurrent: 0004 Timeout: 1 seconds BootOrder: 0000,0001,0002,0004,0003 Boot0000* openSUSE HD(1,GPT,7e019023-b05a-4eab-988c-95fd54bcfbad,0x800,0x4e000)/File(\EFI\opensuse\shim.efi) Boot0001* Hard Drive BBS(HD,,0x0)AMGOAMNO........o.S.a.m.s.u.n.g. .S.S.D. .8.4.0. .E.V.O. .1.2.0.G.B....................A...........................>..Gd-.;.A..MQ..L.1.S.5.D.S.N.F.B.1.3.5.4.5.3. .J. . . . ......AMBOAMNO........q.S.a.n.D.i.s.k. .U.l.t.r.a. .I.I. .4.8.0.G.B.........................rN.D+..,.\...........B..Gd-.;.A..MQ..L.S.a.n.D.i.s.k. .U.l.t.r.a. .I.I. .4.8.0.G.B......AMBOAMNO........c.S.A.M.S.U.N.G. .H.D.1.0.3.S.J.........................rN.D+..,.\...........4..Gd-.;.A..MQ..L.S.A.M.S.U.N.G. .H.D.1.0.3.S.J......AMBOAMNO........c.S.A.M.S.U.N.G. .H.D.1.0.3.S.J.........................rN.D+..,.\...........4..Gd-.;.A..MQ..L.S.A.M.S.U.N.G. .H.D.1.0.3.S.J......AMBOAMNO........o.S.a.m.s.u.n.g. .S.S.D. .8.4.0. .E.V.O. .1.2.0.G.B....................A...........................>..Gd-.;.A..MQ..L.1.S.5.D.S.N.F.B.1.3.7.4.8.9. .M. . . . ......AMBOAMNO........o.S.A.M.S.U.N.G. .H.D.7.5.3.L.J....................A...........................>..Gd-.;.A..MQ..L.1.S.U.3.X.J.B.0.0.3.6.0.3.9. . . . . . ......AMBOAMNO........o.S.A.M.S.U.N.G. .H.D.1.0.3.U.J....................A...........................>..Gd-.;.A..MQ..L.1.S.P.3.9.J.Q.0.2.A.9.5.6.3. . . . . . ......AMBO Boot0002* CD/DVD Drive BBS(CDROM,,0x0)AMGOAMNO........o.A.T.A.P.I. . . .i.H.A.S.3.2.4. . . .B....................A...........................>..Gd-.;.A..MQ..L.5.3.4.2.1.2. .9.4.3.0.8.4.4.0.5.9.0.8.5......AMBO Boot0003 USB BBS(USB,,0x0)AMGOAMNOu.......U.U.S.B.2...0....................A............................."..Gd-.;.A..MQ..L.U.S.B.2...0......AMBO Boot0004* UEFI: USB2.0 PciRoot(0x0)/Pci(0x1a,0x0)/USB(1,0)/USB(1,0)/HD(1,MBR,0x4294967218,0x118,0x1d88)AMBO At this point I powered down and removed the USB key, rebooted, saw the grub2 GUI but it errored trying to load any kernel image. I poked around the grub2 shell for a while, weirdly it could see /boot and 'hd0,gpt3' but thinking back (and comparing with now fixed) I suspect it was trying to use the linux & initrd directives instead of linuxefi & initrdefi. Booting again via TW USB key I simply re-ran yast's bootloader to set everything straight. With a successful boot I let the hubris overwhelm me, and applied the 473 updates that I've missed over the last couple of weeks. In effect, pausing for a moment to change hammers. As these started to apply so the machine flipped out, ejecting me from the vt console login as failing logrotate messages whizzed passed moaning that btrfs filesystem was full. Sadly I had forgotten that in order to "simplify" my setup I'd taken several mounts out of /etc/fstab, including /var/backup that stores rsnapshot's of my work area, /etc and other critical data every few hours. As cron has dutifully triggered this process for at least a dozen years it saw no reason to stop, creating a 45GiB initial backup and (very small) deltas onto /var/backup which was just a subvolume on the small 110GiB SSD. I had realised this sometime last week, paused the cronjob and thought I'd cleaned up. What I also forgot was that snapper had created its own snapshots of the rsnapshots. I foolishly hadn't bothered checking how much disk space was free before the updates as I was expecting at least 30GiB to still be free! Remembering other threads about btrfs usage, once I'd worked out what was going on I was able to create a large file, mount as a loop device, add it to btrfs and then run a full-balance which reclaimed the many missing gigabytes, remove, then finish the updates :) It was about this point that I remembered that I have had a smart phone for a few years and could have browsed a wiki or online docs for help, as my laptop had run out of power a few hours earlier and I'd left the charger at home. Doh! One of my intentions in switching to TW was to learn about using some of the newer Linux features, so there's one goal accomplished... > > > Yes I'd like to see efibootmgr -v before and after trying to manually > add a new entry for opensuse. If you get any errors, check dmesg and > include anything recent and relevant in your next email. > > Definitely check firmware is up to date before bothering with all of > this. I'm pretty close to leaning in the direction you've got at least > one firmware related bug going on. I did update the BIOS first, which was an adventure in itself, leading me to think the unthinkable - that I'd have to get a copy of Windows and install it in order to use the BIOS updater, despite the UEFI BIOS having an "InstantFlash" feature. In frustration I contacted ASRock support, and got really helpful replies from their Dutch team - they don't advertise the "raw" images on their website as some serial numbers of the motherboard were affected by the B2 SATA stepping bug (I had to wait several weeks when I bought the parts for this machine to get a B3 model). Their Windows installer seems to have been defensively written to check the serial number and apply the relevant update to prevent bricking the board. After physically checking the serial number I was able to get the right image (2.10) from their ftp site, copy to a FAT formatted USB and the update went smoothly. Now that I've poked a lot around this version of the BIOS, it still seems that there is no means to "lock" the BIOS into UEFI or Legacy mode. Also it auto-probes for hardware whenever I go into the setup, repopulating its boot priorities and order of disks etc. For example, plugging a USB key in, rebooting and going into setup automatically adds it to the boot order, twice! Firstly as 'USB: USB2.0' and latterly as other 'UEFI: USB'. I find that a little counter-intuitive, but guess password protecting the BIOS may be wise. The theory of efibootvars filling, or not been written until garbage collection might explain how I arrived here in the first place. At least if I have problems updating in the future I'll be a little more aware of how to recover. Daniel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] New Tumbleweed snapshot 20160417 released!
by Ludwig Nussel 20 Apr '16

20 Apr '16

Please note that this mail was generated by a script. The described changes are computed based on the x86_64 DVD. The full online repo contains too many changes to be listed here. Please check the known defects of this snapshot before upgrading: https://openqa.opensuse.org/tests/overview?distri=opensuse&groupid=1&versio… Packages changed: MozillaFirefox (45.0.1 -> 45.0.2) amarok gettext-runtime libva (1.6.2 -> 1.7.0) libva-gl (1.6.2 -> 1.7.0) perl-Devel-Symdump (2.15 -> 2.16) util-linux (2.27.1 -> 2.28) util-linux-systemd (2.27.1 -> 2.28) vaapi-intel-driver (1.6.2 -> 1.7.0) xapian-core (1.2.21 -> 1.2.23) === Details === ==== MozillaFirefox ==== Version update (45.0.1 -> 45.0.2) Subpackages: MozillaFirefox-translations-common - Mozilla Firefox 45.0.2: * Fix an issue impacting the cookie header when third-party cookies are blocked (bmo#1257861) * Fix a web compatibility regression impacting the srcset attribute of the image tag (bmo#1259482) * Fix a crash impacting the video playback with Media Source Extension (bmo#1258562) * Fix a regression impacting some specific uploads (bmo#1255735) * Fix a regression with the copy and paste with some old versions of some Gecko applications like Thunderbird (bmo#1254980) ==== amarok ==== - Copy download icon from Breeze on Leap 42.1 and Tumbleweed - Add Fix-for-infinite-loop-with-some-Audio-CDs.patch to fix the infinite loop in case a home-burned or old audio CD (without CDTEXT) is inserted (kde#339190) ==== gettext-runtime ==== Subpackages: gettext-tools - Add gettext-runtime-grep-2.24.patch: Fix test suite with grep 2.24 (https://savannah.gnu.org/bugs/index.php?47674). ==== libva ==== Version update (1.6.2 -> 1.7.0) Subpackages: libva-drm1 libva-x11-1 libva1 vaapi-dummy-driver - Update to version 1.7.0 * Bump VA API version to 0.39 * Add support for VP9 10bit decode API * Allow libva to load the vaapi driver provided by Mesa Gallium for nouveau and radeon * Fix libva-glx against OpenGL 3.1 or above ==== libva-gl ==== Version update (1.6.2 -> 1.7.0) Subpackages: libva-egl1 libva-glx1 - Update to version 1.7.0 * Bump VA API version to 0.39 * Add support for VP9 10bit decode API * Allow libva to load the vaapi driver provided by Mesa Gallium for nouveau and radeon * Fix libva-glx against OpenGL 3.1 or above - Update baselibs.conf to work with new multi-spec file approach. ==== perl-Devel-Symdump ==== Version update (2.15 -> 2.16) - updated to 2.16 see /usr/share/doc/packages/perl-Devel-Symdump/Changes 2016-04-11 k <andk(a)cpan.org> * release 2.16 * docs only change: create a real link to perlref.pod (Slaven Rezi?) ==== util-linux ==== Version update (2.27.1 -> 2.28) Subpackages: libblkid-devel libblkid1 libblkid1-32bit libfdisk1 libmount1 libmount1-32bit libsmartcols1 libuuid-devel libuuid1 libuuid1-32bit - Update to version 2.28: * Many changes and improvements, most notably: * Now cfdisk, sfdisk and fdisk wipe all filesystem and RAID signatures when creating a new disk label in interactive mode. See --wipe[=auto|never|always]. * lsns -- this NEW COMMAND lists information about all currently accessible namespaces or about the given namespace. * The command sfdisk supports new operations --delete, - -move-data and --reorder. * The command blkdiscard supports a new option --zeroout to zero-fill rather than discard a specified area. * The command cal supports a new option --span to span the date when displaying multiple months. * The command chrt supports the DEADLINE scheduling class and the new options --sched-runtime --sched-period and - -sched-deadline. * The command logger supports RFC 5424 structured data through the new options --sd-id and --sd-param. * The command losetup supports a new option --direct-io. * The command lsblk allows to sort output by unprinted columns. * The command mount applies the nofail mount option to ENOMEDIUM errors. * The commands nsenter and unshare support a new option - -cgroup for work with cgroups namespaces (CLONE_NEWCGROUP). * The library libmount has been improved to properly detect already mounted btrfs subvolumes. * The library libsmartcols has been massively improved to print table ranges, multi-line cells, table titles and to support continuous printing. * The package build system and code have been improved to be more portable to non-Linux systems (BSD, OSX). * The package does not provide fallback solutions for openat-family functions anymore. * The python binding for libsmartcols is available in separate project at https://github.com/ignatenkobrain/python-smartcols * Security issue: CVE-2016-2779 is NOT FIXED yet. - Remove old util-linux-noenc-suse.patch ==== util-linux-systemd ==== Version update (2.27.1 -> 2.28) - Update to version 2.28: * Many changes and improvements, most notably: * Now cfdisk, sfdisk and fdisk wipe all filesystem and RAID signatures when creating a new disk label in interactive mode. See --wipe[=auto|never|always]. * lsns -- this NEW COMMAND lists information about all currently accessible namespaces or about the given namespace. * The command sfdisk supports new operations --delete, - -move-data and --reorder. * The command blkdiscard supports a new option --zeroout to zero-fill rather than discard a specified area. * The command cal supports a new option --span to span the date when displaying multiple months. * The command chrt supports the DEADLINE scheduling class and the new options --sched-runtime --sched-period and - -sched-deadline. * The command logger supports RFC 5424 structured data through the new options --sd-id and --sd-param. * The command losetup supports a new option --direct-io. * The command lsblk allows to sort output by unprinted columns. * The command mount applies the nofail mount option to ENOMEDIUM errors. * The commands nsenter and unshare support a new option - -cgroup for work with cgroups namespaces (CLONE_NEWCGROUP). * The library libmount has been improved to properly detect already mounted btrfs subvolumes. * The library libsmartcols has been massively improved to print table ranges, multi-line cells, table titles and to support continuous printing. * The package build system and code have been improved to be more portable to non-Linux systems (BSD, OSX). * The package does not provide fallback solutions for openat-family functions anymore. * The python binding for libsmartcols is available in separate project at https://github.com/ignatenkobrain/python-smartcols * Security issue: CVE-2016-2779 is NOT FIXED yet. - Remove old util-linux-noenc-suse.patch ==== vaapi-intel-driver ==== Version update (1.6.2 -> 1.7.0) - Update to version 1.7.0 * Add support for Kabylake - Decoding: H.264/MPEG-2/VC-1/JPEG/VP8/HEVC/HEVC 10-bit/VP9/VP9 10-bit - Encoding: H.264/MPEG-2/JPEG/VP8/HEVC - VPP: CSC/scaling/NoiseReduction/Deinterlacing{Bob, MotionAdaptive, MotionCompensated}/ColorBalance/STD * Add new SKL and BXT PCI IDs * Fix lots of VP9 decoding issues on BXT ==== xapian-core ==== Version update (1.2.21 -> 1.2.23) - Update to 1.2.23 * API + PostingSource: Public member variables are now wrapped by methods * chert backend + xapian-check now performs additional consistency checks for chert. * omega + Fix HTML/XML entity decoding to be O(n) not O(n�) - indexing HTML/XML with a lot of entities is now much faster. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] qt5ct
by emanuel 20 Apr '16

20 Apr '16

qt5ct starts on plasma5 as well as in the intended desktop/s needing qt5ct, qt5ct should be configured 'unloaded' on plasma5 session as it is not needed on that particular session. qt5ct info; https://gist.github.com/2404e3fdde2acbf0930d59ef344da477 session intended for and working as should be; System: Host: linux-s4s1 Kernel: 4.5.0-3-default x86_64 (64 bit gcc: 5.3.1) Desktop: Cinnamon 2.8.8 (Gtk 3.20.3) dm: sddm,sddm Distro: openSUSE Tumbleweed (20160416) session where qt5ct plugin is active but not needed; System: Host: linux-s4s1 Kernel: 4.5.0-3-default x86_64 (64 bit gcc: 5.3.1) Desktop: KDE Plasma 5.6.2 (Qt 5.5.1) dm: sddm,sddm Distro: openSUSE Tumbleweed (20160416) clip from terminal showing kate startup and qt5ct also active in a plasma5 session; https://gist.github.com/anonymous/aa4b20e81b285ebacb69b23ed35d9102 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

[opensuse-factory] Test my new account
by poliglot 20 Apr '16

20 Apr '16

123 -- Marco Calistri opensuse Tumbleweed 64 bit - Kernel 4.5.0-3-default Gnome 3.20 Intel® Core™ i5-2410M CPU @ 2.30GHz × 4 - Intel® Sandybridge Mobile -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

8 22

[opensuse-factory] Fail to run VirtualBox virtual machine
by Mikael Springer 20 Apr '16

20 Apr '16

When I try to start a virtual machine using VirtualBox I get an error message: Kernel driver not installed (rc=-1908) The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing '/sbin/rcvboxdrv setup' as root. If it is available in your distribution, you should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary. where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT. VirtualBox is installed from Tumbleweed repos. /sbin/rcvboxdrv doesn't exist so reinstalling the kernel module using this is not an option. What's wrong? Regards, Micke. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 4

RE: [opensuse-factory] Phone does not begin charging unless I am logged in to Desktop?
by stakanov＠freenet.de 20 Apr '16

20 Apr '16

> -----Ursprüngliche Nachricht----- > Von: Howard Guo > Gesendet: Mi. 13.04.2016 08:15 > An: opensuse-factory(a)opensuse.org > Betreff: [opensuse-factory] Phone does not begin charging unless I am logged in to Desktop? > > Hello fellow Tumbleweed users. > > I noticed a strange phenmenon with charging my Sony phone on this Tumbleweed workstation - it does not charge > in multi-user.target, or VT, or display-manager. It only charges after I have logged into desktop. Does anyone > know how to alter the behaviour so that Linux will allow it to charge as long as the system is powered up? > > Thanks. > > Regards, > Howard > -- > To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org > > > > -----Ursprüngliche Nachricht Ende----- This is not only a problem of Tumbleweed but of all installations and does AFAIK more depend on the BIOS setting. Two solutions come to my mind: a) you set the "usb-legacy" support to "on" in the BIOS. That should power up USB even if the desktop is not logged in. b) you use a dedicated usb plug (some of the machines have a special plug that charges even if no OS has been started up). Maybe that has also to do with PAM as the Sony will probably charge when recognized as a usb-key or token. For security reasons it is possible that the PAM setting does not allow to mount such devices (mass storage) but only after the authorized user logged in. However I do not know sufficiently about PAM to tell with certainty. --- Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! https://email.freenet.de/mail/Uebersicht?epid=e9900000451 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 7

[opensuse-factory] virt-manager fails to start
by Michael Ströder 19 Apr '16

19 Apr '16

HI! Since a recent update virt-manager fails to start with this message: (process:2567): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed Any idea what's going on? Ciao, Michael. # zypper info virt-manager Loading repository data... Reading installed packages... Information for package virt-manager: ------------------------------------- Repository: Main Repository (OSS) Name: virt-manager Version: 1.3.2-6.1 Arch: noarch Vendor: openSUSE Installed: Yes Status: up-to-date Installed Size: 2.6 MiB Summary: Virtual Machine Manager

3 5

[opensuse-factory] did a 32bit to 64bit HTTP offline TW/KDE3 upgrade
by Felix Miata 19 Apr '16

19 Apr '16

Several days ago I tried to chroot to do a TW update, which reminded me no can do due to different arches. So, Sunday night, on this, a Haswell, my primary machine, which spends 99.7% of the time not running TW, I shut down 42.1 to do $SUBJECT. Machine has 13.1 32 bit on md1, 13.2 32 bit on md2, 42.1 on md4, and until Sunday night, TW on md3 was 32 bit, last updated somewhere around 7 weeks ago. I used 20160415's linux and initrd with upgrade=1 started with 13.1's Grub 0.97-194. Before proceeding with installation phase, I re-enabled KDE3 and one other I've already forgotten, maybe Mozilla, maybe Packman. As usual post-13.1, I selected install no bootloader. Grub2* got installed anyway. I'm not sure whether I had had it locked out or not. Removing all of grub2* was performed as one of the first first-boot operations. Manual resolution was required only to permit the locked kernel-pae to be removed. IMO, too many new files got installed: upgraded 957 new 368 removed 15 (of which 6 were kernels as old as 9 months) A large part of the new were -32bit packages. Afterward I removed them all by removing glibc-32bit, somewhere short of 200 total, then added back glibc-32bit right away, after which in order to run old mozilla.org binaries I added pangox-compat-32bit, then a few more that Firefox 3 complained not found, which collectively via deps added back a somewhat more than half the number of 32bit packages removed by removing glibc-32bit. Reported ETA remained >2:00:00 until the packages remaining count was reduced to zero. :-( Some logs: http://fm.no-ip.com/Tmp/SUSE/Factory/updTestcase20160418004624-msi85tw.zip http://fm.no-ip.com/Tmp/SUSE/Factory/yast2logs-msi85tw20160415.zip http://fm.no-ip.com/Tmp/SUSE/Factory/zypplogs-msi85tw20160415.zip In summary, the overall process went well enough, and easier than a fresh install, under an hour, with a lot better result than when I tried to update a 32 bit 13.2 installation to 42.1 a few weeks before 42.1 release. As an aside, TW and 42.1 are both nicely running modeset X driver instead of intel. TW's KDE3 was writing mildly corrupted titlebars on background windows until I disabled text shadowing in its theme. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] VirtualBox module and kernel versions out of sync for Leap 42.1
by Larry Finger 18 Apr '16

18 Apr '16

Currently, the latest kernel for Leap is 4.1.20_11; however, the recently rebuilt VirtualBox modules are for 4.1.15_8. As a result, VB features such as shared folders are not available. Is there something in the spec file that needs to be changed? The only statement that seems to pertain to this issue is the following: %(sed -e '/^Provides: multiversion(kernel)/d' %{_libexecdir}/rpm/kernel-module-subpackage > %{_builddir}/virtualbox-kmp-template) The output file from the previous statement is later used in the following command: %kernel_module_package -t %{_builddir}/virtualbox-kmp-template -p %{SOURCE8} -n %{name}-guest -f %{SOURCE6} -x kdump um xen xenpae pv Thanks, Larry -- If I was stranded on an island and the only way to get off the island was to make a pretty UI, I’d die there. Linus Torvalds -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1