December 2017 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Wine applications slowing down more with ever Tumbleweed upgrade
by Christopher Myers 20 Dec '17

20 Dec '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 It seems like with every Tumbleweed upgrade, it takes longer and longer for my Wine applications to load. After they're loaded they seem to be fine, it's just that first initial start. I've tried kicking them up from the command line but haven't seen anything useful. Is this a known issue, or is there a good way to troubleshoot it? Chris -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEE7GM/Dul8WSWn72odQ1nEo4DFCIUFAlo6hrEACgkQQ1nEo4DF CIUoAwgAgQDKj9ld98cKWumf0p+1MSwultEMobtzpjBMunlvBhgY65KKnnU1Xzd0 jjWEdnZFkLOBv+HkYmTTo6M95OyY2ybgzO58lDSqSqgEFmsFOCLydPbWJtlDd3bd +v8GqCtmIeVuI3NmHbI5cTwB/IMA9J04DurnBOmY8t58GBVNBPqz9rsYsLwySc6r xuJ88Xs3gYyfkQ4wq0PrZLrg+o7G/T8wswDLRDEGPV3og/Z1yjjLfPxL6DT2Zaar QVaU6DqkTvUl9e4vrVqy2NC+BG2D4sQW42fR0m2TzR5pLBuYFxN2OKFyYwhex2Xq WYcNYTAMTysOIIxiL3dP4vy809fnnA== =ckKn -----END PGP SIGNATURE-----

1 0

[opensuse] USB3 mounts going away
by David T-G 20 Dec '17

20 Dec '17

Hi, all -- I wanted to mirror some data from one portable drive to another, so I plugged 'em in to my [new to me] Dell E6540 with SuSE to run rsync. Nothing automagically* showed up in the fstab file for me to use, so I let the notifier popup open the file manager for each of them, which then mounted them under /run/media/root/<vol-label> and away we went. Curiously, though, just minutes into the copy one or the other would disappear. Sometimes, by the time I walked past and saw the problem, the drive would [again?] be visible and I could click to open another file manager; sometimes it wouldn't show and I had to unplug the device to let it be recognized when I reconnected it. After a few of those, I got tired of the problem and just manually made /mnt/<vol-label} mount points and mounted 'em directly, but they STILL fell away. Uh oh. Do I suddenly have device issues? Did I buy a dud laptop? [Oh, and I am almost positive I rebooted at least once along the way just for giggles.] I took my Knoppix thumb drive out of my pocket and booted on that and -- on the same laptop with the same drives in the same USB slots -- we've been happily copying all night long and are still going strong. Yay that I don't have any hardware issues, but ... what's up with SuSE and its peripherals management? * I'll have to learn separately about USB and SD slot recognition, since I'd like to be able to mount something easily and without having to go and click somewhere, but that can be a separate thread. TIA & Happy Holidays :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 5

[opensuse] What is the current HowTo to get suspend to RAM working on Leap?
by David C. Rankin 20 Dec '17

20 Dec '17

All, What is the current link for getting s2ram working on Leap? I find https://en.opensuse.org/SDB:Suspend_to_RAM but that appears a bit old. I would like to get suspend working on my laptop, what is a good link to do this with leap? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 5

[opensuse] What file do I edit to fix 'systemd-modules-load' Failure?
by David C. Rankin 20 Dec '17

20 Dec '17

All, I have had this frustrating error on boot of Leap 42.2 ever since I installed, then uninstalled, the Nvidia drivers for my laptop. (I have since reinstalled the drivers after we got the backlight bug triaged and a xrandr workaround). However, I still have this nagging module fail to load error on every boot -- which I've ignored, but want to fix before attempting a 42.3 upgrade. The error is: Dec 19 19:18:54 wizard systemd-modules-load[110]: Failed to insert 'ppp_mppe': No such device Dec 19 19:18:54 wizard systemd-udevd[191]: Network interface NamePolicy= disabled by default. Dec 19 19:18:54 wizard systemd-modules-load[110]: Inserted module 'sg' Dec 19 19:18:54 wizard kernel: SCSI subsystem initialized Dec 19 19:18:54 wizard systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE Dec 19 19:18:54 wizard systemd[1]: Failed to start Load Kernel Modules. Dec 19 19:18:54 wizard systemd[1]: systemd-modules-load.service: Unit entered failed state. Dec 19 19:18:54 wizard systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. I don't know why it is looking for 'ppp_mppe' and don't know if it was related to the nvidia driver install/remove/reinstall, but it has been present ever since. There must be some file in the systemd-modules-load chain that is trying to load the module. What is that file and where does it live so I can go delete the 'ppp_mppe' entry. There is nothing in /etc/modules-load.d/, so where to check? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 7

[opensuse] zypper hangs - strange network-related issue?
by Mikhail Ramendik 20 Dec '17

20 Dec '17

Hello, When I start zypper in something, zypper sometimes hangs. I have looked into /var/log/zypper.log and here is where it hangs: https://pastebin.com/5EPs2gyW The last line is: 2017-12-20 02:36:20 <1> ramendik-desktop(22593) [zypp++] MediaCurl.cc(doGetDoesFileExist):1195 URL: http://download.opensuse.org/distribution/leap/42.3/repo/oss/content However, pings to download.opensuse.org pass successfully. What might be going on? -- Yours, Mikhail Ramendik Unless explicitly stated, all opinions in my mail are my own and do not reflect the views of any organization -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 6

[opensuse] RTL8812AU woes - now "works" but some things hang
by Mikhail Ramendik 20 Dec '17

20 Dec '17

Hello, Well, while I was trying to get a tcpdump output. the RTL8812AU thing started working. Sort of. It got an IPv4 address. Then after a reboot pings started working. That may have been caused by me retyping the WPA-PSK password, or not. However, not all is well. While pings are stable, some network transactions just hang. Google Mail gets mysteriously stuck at "still working" and zypper gets stuck at a download that, actually, works fine with wget. I even created a thread on zypper but then realized it might be the card, and it was. Of course I tried lowering MTU but it just won't lower MTU. Using yast, I set it to 1400 in the /etc/sysconfig editor (then rebooted), and it is also at 1400 in the network settings editor, but it is still 1500 in the ifconfig output. So I reverted to the old 2.4Ghz card which also has an MTU of 1500 but everything works right. How can I troubleshoot this now? If the dongle is broken, it's broken in a very strange way. And anyway a lower MTU *should* help, because pings work - but I can't lower the MTU and that is certainly not a hardware issue. -- Yours, Mikhail Ramendik Unless explicitly stated, all opinions in my mail are my own and do not reflect the views of any organization -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] 4KB physical sector drives
by Greg Freemyer 19 Dec '17

19 Dec '17

On Fri, Dec 15, 2017 at 5:08 AM, Wols Lists <antlists(a)youngman.org.uk> wrote: > On 15/12/17 00:31, Felix Miata wrote: >> Dave Plater composed on 2017-12-14 17:53 (UTC+0200): >> >>> Not sure but I think that some large disks >>> have physical sectors of 4096 bytes. >> >> Most (if not all) >500GB made in the past ~6 years have 4Kb physical sectors: >> <https://www.seagate.com/tech-insights/advanced-format-4k-sector-hard-drives…> >> > Drifting off topic (if not more here), while most drives had a > compatibility mode, many newer drives do not. > > If your drive ONLY supports 4K sectors, and your fdisk or gpt or > whatever has an "off-by-one" specifying the partition size in 512B > sectors, then this can cripple disk access speeds. > > (I think I've explained it right - but it's definitely an "off by one" > problem, and if your disk performance is awful, that could be why) Hopefully on topic: Modern versions of openSUSE use tools that default the partition alignment to 1 MB boundaries. If you have a 4KB drive it is best to ensure it doesn't do an optimization for aligning with the old practice of starting the first partition on sector 63. I've never seen one that supported the sector 63 alignment, but I understand those that do have a jumper to control it. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Wi-Fi dongle not getting IPv4 address
by Mikhail Ramendik 19 Dec '17

19 Dec '17

So I thought it was the RTL8812AU driver, but now I used a version tested by Linux Kamarada of this list (thanks!) and I am still having the problem. I have a new Wi-Fi dongle (5 GHz/2.4GHz, wlan1) as well as a PCI card (2.4 only, which is why I want to use the new dongle; wlan0). I configure both with wicked in yast. Unfortunately, while the new dongle appears to connect to the wireless network, it fails to get an IPv4 address and no communication happens. After ifdown wlan1 and ifup wlan1 , I see "setup-in-progress". The only stuff added in dmesg at ifup wlan1: [ 1525.360875] cfg80211: Regulatory domain changed to country: GB [ 1525.360878] cfg80211: DFS Master region: ETSI [ 1525.360878] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 1525.360882] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) [ 1525.360884] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 1525.360886] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 1525.360887] cfg80211: (5490000 KHz - 5710000 KHz @ 160000 KHz), (N/A, 2700 mBm), (0 s) [ 1525.360889] cfg80211: (57000000 KHz - 66000000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A) iwconfig and ifconfig outputs, which show the problem: # iwconfig wlan1 wlan1 IEEE 802.11abgn ESSID:"Ramendik_44_5Ghz" Mode:Managed Frequency:5.18 GHz Access Point: 70:50:AF:CC:3B:05 Bit Rate=867 Mb/s Tx-Power=12 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality=36/70 Signal level=-74 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 # ifconfig wlan1 wlan1 Link encap:Ethernet HWaddr 00:0F:00:37:B8:6D inet6 addr: fe80::20f:ff:fe37:b86d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:871 errors:0 dropped:670 overruns:0 frame:0 TX packets:72 errors:0 dropped:78 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:81082 (79.1 Kb) TX bytes:11537 (11.2 Kb) When I look into the admin interface of the router, I actually see this device listed under the IPv6 address. But normal communication is IPv4 and that does not work. I tried to set "DHCP version 4 only" for this interface in yast, this does not change anything. Unfortunately, the router does not let me disable its "Enable IPv6 DHCP server" setting. This is also not some incompatibility of the router with Linux. A laptop that runs Fedora (with the iwlwifi driver for its built-in WLAN) connects to the same 5GHz network just fine. So how do I make wlan1 use IPv4 as normal? And are there any other logs I should look at? Of course this is a new dongle ordered from China, so there is a chance of a hardware failure. But this looks like a strange kind of hardware failure? Or should I suspect one? I do have a Windows 10 machine, so if I have no other option I can try and set the dongle up in that machine just to see if it works. But I'd rather resolve my problems just with Linux. -- Yours, Mikhail Ramendik Unless explicitly stated, all opinions in my mail are my own and do not reflect the views of any organization -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 4

[opensuse] multiboot vis-a-vis /boot/efi/EFI/opensuse
by Felix Miata 19 Dec '17

19 Dec '17

Neither https://en.opensuse.org/openSUSE:UEFI nor anything I've found so far suggests how to multiboot multiple releases of the same distribution. I see I can create new entries with efibootmgr, but can each openSUSE installation ever use the same /boot/efi/EFI/opensuse/, or does each need its own directory with unique names? Do I create a new entry for the first after renaming the original (TW20171214 is already installed), or after copying the original to a new name? Does the Grub that actually does the work on a / partition need to be reconfigured with a unique directory name in /boot/efi/EFI/? Nothing was evident in the bootloader phase of TW installation to address EFI directory naming. My ultimate expectation is to EFI boot more or less the same way as with Legacy Grub and MBR, with a main boot menu I configure on a partition not managed by any installed distro, possibly rEFInd or AiR-Boot, and each distro's own bootloader configured by it to exclude any other installed distro (os-prober disabled). With EFI, I anticipate efibootmgr to be sufficient to the task at least initially. -- "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+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 7

[opensuse] Does iperf3 work???
by James Knott 19 Dec '17

19 Dec '17

I installed iperf3 on my desktop and notebook computers. When I run it as a server on my desktop, it displays a text box that say server listening on 5201. I then run it as a client on my notebook computer. After a while it times out saying it can't reach the server, even though pinging the same address works. When I run Wireshark, I don't see any traffic from iperf3. Any ideas? tnx jk -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1