- openSUSE Support

[opensuse-support] TW Grub EFI menu & memtest86+
by Felix Miata 21 Jun '18

21 Jun '18

I wanted to be able to run memtest without having to hunt for a DVD to boot, so I did zypper in memtest86+ Zypper responded as I expected. I now see a two line comment pair in /boot/grub2/grub.cfg marking20_memtest86+. /etc/grub.d/20_memtest86+ exists, 1932 bytes. I don't find any memtest entry in Grub's menu on reboot however. What more is needed? Shouldn't installing memtest86+ have automatically caused an entry to show up in the menu at boot time? Is grub2-mkconfig supposed to be run manually to do it? How do I even know whether the Grub menu I see at boot time belongs to TW rather than 42.3, 15.0 or Debian? /boot/efi/EFI/ has directories for all 4 OSes. efibootmgr does list TW's 0000 first: BootCurrent: 0000 BootOrder: 0000,0005,0006,0001,0007,0008 0000* opensuse-tw 0005* opensuse 0006* debian 0001* opensuse423 0003 Hard Drive # sata HD? 0007* Hard Drive # M.2 with nothing yet installed? 0004* CD/DVD Drive # normal mode? 0008* CD/DVD Drive # EFI mode? fdisk -l Disk /dev/sda: 298.1 GiB, 320072933376 bytes, 625142448 sectors Disklabel type: gpt ... Device Start End Sectors Size Type /dev/sda1 2048 657407 655360 320M EFI System /dev/sda2 657408 5375999 4718592 2.3G Linux swap /dev/sda3 5376000 10078207 4702208 2.2G Linux filesystem /dev/sda4 10078208 23185407 13107200 6.3G Linux filesystem /dev/sda5 23185408 55953407 32768000 15.6G Linux filesystem /dev/sda6 55953408 70699007 14745600 7G Linux filesystem /dev/sda7 70699008 85444607 14745600 7G Linux filesystem /dev/sda8 85444608 100190207 14745600 7G Linux filesystem /dev/sda9 100190208 114935807 14745600 7G Linux filesystem Disk /dev/sdb: 238.5 GiB, 256060514304 bytes, 500118192 sectors Disklabel type: gpt ... Device Start End Sectors Size Type /dev/sdb1 2048 657407 655360 320M EFI System -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

3 8

[opensuse-support] leap15 rescue iso
by JJM de Faber 20 Jun '18

20 Jun '18

In the leap15 download diectory are live iso's. The live iso and the rescue iso. They both don't boot. Error: GRUB, Mokmanager.efi not found. Is this a bug or something else? -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

2 6

[opensuse-support] KVM and network bridges
by JSEvans 20 Jun '18

20 Jun '18

Hi all, I've got a weird issue. On my home server, I'm running a new clean installation of Leap 15 with KVM and I've bridged eth0 to be br0 so that I can get real IP's to my VMs. However, my vm's can't reach the network using br0 though they can with NAT. I also installed VirtualBox and used br0 and that had no problems. Any suggestions on things to check? Jason -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

2 1

[opensuse-support] snapper question
by Constant Brouerius van Nidek 20 Jun '18

20 Jun '18

On a newly installed Tumbleweed I choose BtRFS and XFS as my file-system. As I found with former installations this would automatically make a hidden directory /.snapshots and starts the usage of snapper. My latest installation did not finish a snapper setup and I am stuck with a instruction of reading the man snapper. Read it and I am not much wiser. The yast snapper is not able to help me out either. What is the instruction in order to have a functioning snapper? -- opensuse:tumbleweed:20180615 Qt: 5.11.0 KDE Frameworks: 5.46.0 - KDE Plasma: 5.13.0 - kwin 5.13.0 kmail2 5.8.2 - akonadiserver 5.8.2 - Kernel: 4.17.1-1-default -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

5 9

[opensuse-support] LDAP server on Leap 15.0/TW
by Wolfgang Rosenauer 19 Jun '18

19 Jun '18

Hi, I just noticed - while preparing a Leap 15.0 server to replace an old one - that YaST2 "auth-server" now configures and uses 389ds as LDAP service. There is probably nothing wrong with it but some things really surprised me: - https://doc.opensuse.org/documentation/leap/security/single-html/book.secur… reports itself as being valid for Leap 15.0 but it does not match at all what I'm seeing and describes openldap - the release notes have nothing about that fact and by far what surprised me most: 389ds is only available as a very basic package in the repos. There is none of the management/admin packages available? This really looks quite incomplete. What did I miss? Thanks, Wolfgang -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

1 1

[opensuse-support] How to wake-up USB ports?
by Bjoern Voigt 19 Jun '18

19 Jun '18

With my primary desktop PC I have the problemsince some years, that some USB ports do not reliable wake-up after a suspend (suspend to disk) and resume cycle. As the result, devices connected to these USB ports do often not work after resume. The affected USB ports are USB 2.0 ports. With my USB 3.0 PCI extension card the problem does not exists, even with the same external USB devices. I tried some tips from the internet but did not found a good solution. Do you have tips for me? The kernel error message, if I connect a device (e.g. a USB drive) to a "sleeping" USB port look like these: [22674.173306] hub 4-1:1.0: hub_ext_port_status failed (err = -32) [22674.520974] hub 4-1:1.0: hub_ext_port_status failed (err = -32) [22674.608968] hub 4-1:1.0: hub_ext_port_status failed (err = -32) Kernel: 4.16.12-3-default OS: openSUSE Tumbleweed 20180613 (x86_64) Greetings, Björn -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

2 1

[opensuse-support] Latest snapshot 20180613 does not show up after zypper dup
by Constant Brouerius van Nidek 18 Jun '18

18 Jun '18

On one machine I am presented with an update from 2135 packages. On the other machine it is only 105 packages without mentioning that it is the snapshot update from 20180606 -> 20180613. Whatever I try I get the message that most packages are up to date and only some packages from KDE Extra and Packman need an update. This is after zypper dup but I get the same result after zypper clean && zypper ref && zypper dup. It shows only 105 packages to update without mentioning the snapshot update. What went wrong? -- opensuse:tumbleweed:20180606 Qt: 5.11.0 KDE Frameworks: 5.46.0 - KDE Plasma: 5.12.5 - kwin 5.12.5 kmail2 5.8.1 - akonadiserver 5.8.1 - Kernel: 4.16.12-2-default -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

2 4

[opensuse-support] snapshot 20180613: kcminit segfaults
by mh＠mike.franken.de 17 Jun '18

17 Jun '18

Hi *, after installing the latest snapshot, kcminit crashes with segfault right after having entered user and passord information on login: Application: KCMInit (kdeinit5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff3bb1f6380 (LWP 2494))] Thread 2 (Thread 0x7ff3a6bde700 (LWP 2495)): #0 0x00007ff3b92df5d9 in poll () from /lib64/libc.so.6 #1 0x00007ff3ba673377 in ?? () from /usr/lib64/libxcb.so.1 #2 0x00007ff3ba674f8a in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x00007ff3a958a939 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x00007ff3b967b93c in ?? () from /usr/lib64/libQt5Core.so.5 #5 0x00007ff3b795c554 in start_thread () from /lib64/libpthread.so.0 #6 0x00007ff3b92e9fdf in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7ff3bb1f6380 (LWP 2494)): [KCrash Handler] #6 0x00007ff3b0ac11ea in ?? () from /usr/lib64/libKF5ConfigCore.so.5 #7 0x00007ff3b0ac639b in ?? () from /usr/lib64/libKF5ConfigCore.so.5 #8 0x00007ff3b0ac64bb in ?? () from /usr/lib64/libKF5ConfigCore.so.5 #9 0x00007ff3b0aba929 in ?? () from /usr/lib64/libKF5ConfigCore.so.5 #10 0x00007ff3b0aca2ee in KConfigGroup::readEntry(char const*, QString const&) const () from /usr/lib64/libKF5ConfigCore.so.5 #11 0x00007ff3a5353844 in ?? () from /usr/lib64/qt5/plugins/kcm_mouse.so #12 0x00007ff3a534b25a in kcminit_mouse () from /usr/lib64/qt5/plugins/kcm_mouse.so #13 0x00007ff3aa30a86d in ?? () from /usr/lib64/libkdeinit5_kcminit_startup.so #14 0x00007ff3aa30b2f5 in ?? () from /usr/lib64/libkdeinit5_kcminit_startup.so #15 0x00007ff3aa30b6c1 in ?? () from /usr/lib64/libkdeinit5_kcminit_startup.so #16 0x00007ff3aa30c5af in kdemain () from /usr/lib64/libkdeinit5_kcminit_startup.so #17 0x000055fac06fed87 in ?? () #18 0x000055fac06fb63f in ?? () #19 0x00007ff3b921211b in __libc_start_main () from /lib64/libc.so.6 #20 0x000055fac06fc3ca in _start () Should I open a bug for this or is there something wrong with my system? TIA. Bye. Michael. -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

4 7

[opensuse-support][TW] mount.nfs: error: no such device
by Felix Miata 17 Jun '18

17 Jun '18

20180613, but was happening prior to today's upgrade from 20180410. Same PC has had two TW installations for more than two years. This happens only one one of them. Host 'lanserver' is running 42.3. This NFS mounting that works on one but not the other is "normally" occurring by running an alias from ~/.bashrc that is much too old to remember, and also refers to several fstab entries. # showmount -e lanserver /public 192.168.0.0/255.255.255.0 # mount -t nfs lanserver:/public /mnt/ls/public mount.nfs: No such device # mount -t nfs 192.168.#.#:/public /mnt/ls/public mount.nfs: No such device No messages regarding nfs show up in journalctl or dmesg. What device? How do I figure out why I'm getting this message instead of a successful NFS mount? -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

2 1

[opensuse-support] latest Tumbleweed snapshot: Digest verification failed for file 'ghc-base-4.11.1.0-1.1.x86_64.rpm'
by mh＠mike.franken.de 15 Jun '18

15 Jun '18

Hi *, running zypper dup to get the latest Tumbleweed snapshot I get: Warning: Digest verification failed for file 'ghc-base-4.11.1.0-1.1.x86_64.rpm' [/var/cache/zypp/packages/Haupt_Repository_OSS__Tumbleweed/x86_64/ghc-base-4.11.1.0-1.1.x86_64.rpm] expected 51a118143d31e24600907387eb24626c372a0dcc3851caea4d1102ef0311a1a5 but got 7a58d240a74d8f899d4feed23b26661a45b4b79f7aaa77c0d685abdf1d544c49 Accepting packages with wrong checksums can lead to a corrupted system and in extreme cases even to a system compromise. However if you made certain that the file with checksum '7a58..' is secure, correct and should be used within this operation, enter the first 4 characters of the checksum to unblock using this file on your own risk. Empty input will discard the file. This didn't solve in the last 12 hours. Is there a mirror with defect packages or is it a more generell problem? TIA. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

1 0