August 2019 - openSUSE Users - openSUSE Mailing Lists

[opensuse] optimus works on 15.1 - VITUALHEAD also
by jdd＠dodin.org 19 Aug '19

19 Aug '19

Hello, after some problems (see elsewhere), I made a fresh install of Leap 15.1. No question else that do you have the same experience? After some work, I could get back my usual working system, and better then It seems optimus/bumblebee works. It seems, because I only could test glfxdemos, but the fps goes from 60 to 430 :-) I also could bet back my full HD screen on said to be only 1366x768 monitor http://www.dodin.org/wiki/pmwiki.php?n=Doc.OptimusVideo in summary: optirun works with nouveau driver, bumblebee *remove* nvidia driver. xf86-video-intel was not installed and I had to use it to get VITUALHEAD (necessary on my Asus ASUS N550JK) openSUSE page https://en.opensuse.org/SDB:NVIDIA_Bumblebee seems a bit obsolete jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] apc stop connecting
by Patrick Shanahan 17 Aug '19

17 Aug '19

I have a UPS NS 1250 which I have used for several years, even had to replace the batteries last year or so. It no longer will connect, since yesterday. it is cable connected via usb and config (/etc/apcupsd/apcupsd.conf): UPSNAME paka-ups UPSCABLE usb UPSTYPE usb DEVICE POLLTIME 10 LOCKFILE /var/lock SCRIPTDIR /etc/apcupsd PWRFAILDIR /etc/apcupsd NOLOGINDIR /etc ONBATTERYDELAY 6 BATTERYLEVEL 5 MINUTES 3 TIMEOUT 0 ANNOY 300 ANNOYDELAY 60 NOLOGON disable KILLDELAY 0 NETSERVER on NISIP 0.0.0.0 NISPORT 3551 EVENTSFILE /var/log/apcupsd.events EVENTSFILEMAX 10 UPSCLASS standalone UPSMODE disable STATTIME 0 STATFILE /var/log/apcupsd.status LOGSTATS off DATATIME 0 UPSNAME paka-ups BATTDATE 01/04/18 SELFTEST 336 apcupsd is not running, fails with: # systemctl status apcupsd ● apcupsd.service - APC UPS Power Control Daemon for Linux Loaded: loaded (/usr/lib/systemd/system/apcupsd.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Sat 2019-08-17 11:22:39 EDT; 2s ago Process: 12425 ExecStartPre=/bin/rm -f /etc/apcupsd/powerfail (code=exited, status=0/SUCCESS) Process: 12429 ExecStart=/usr/sbin/apcupsd -b -f /etc/apcupsd/apcupsd.conf (code=exited, status=1/FAILURE) Main PID: 12429 (code=exited, status=1/FAILURE) Aug 17 11:22:39 crash apcupsd[12429]: apcsmart Aug 17 11:22:39 crash apcupsd[12429]: net Aug 17 11:22:39 crash apcupsd[12429]: snmplite Aug 17 11:22:39 crash apcupsd[12429]: pcnet Aug 17 11:22:39 crash apcupsd[12429]: modbus Aug 17 11:22:39 crash apcupsd[12429]: Most likely, you need to add --enable-usb to your ./configure options. Aug 17 11:22:39 crash apcupsd[12429]: apcupsd FATAL ERROR in apcupsd.c at line 196 Apcupsd cannot continue without a valid driver. Aug 17 11:22:39 crash systemd[1]: apcupsd.service: Main process exited, code=exited, status=1/FAILURE Aug 17 11:22:39 crash apcupsd[12429]: apcupsd error shutdown completed Aug 17 11:22:39 crash systemd[1]: apcupsd.service: Failed with result 'exit-code'. this all worked asis yesterday and years previous. to my knowledge nothing related has changed since the last start of apcupsd. google has lots of comments but cannot ask the correct question or just plain do not know where to look. tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 4

[opensuse] very annoying grub2 issue, Leap 15.0 / windows 10
by Mathias Homann 16 Aug '19

16 Aug '19

Hi guys, I have a extremely annoying issue with grub2, or more precisely grub2-once. I have two systems that both run a dual boot setup between Leap 15.0 and Windows 10. Both boot from UEFI with secure boot turned OFF. One of them i can choose what to boot next from the command line with grub2-once <number>, and it works just fine: I do "sudo grub2-once 3; sudo systemctl reboot" and I end up in windows, and on next reboot I get my grub menu again The other one, whenever I do the same sequence of "sudo grub2-once 3 ; sudo systemctl reboot" I bot into windows, but then I keep booting into windows - grub2 is not working anymore so the boot sequence defaults to the original windows bootloader... The only differences between the two systems that I can think of are: the working system has one harddisk, the nonworking one has two harddisks (but none of the actual OS installed on the second disk, in both windows and linux) the working system has windows 10 home, the broken one has windows 10 pro any ideas/hints? Cheers MH -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 4

[opensuse] Opening a program in a different computer
by Wolfgang Mueller 16 Aug '19

16 Aug '19

I have two computers installed as shown on this extract of /etc/hosts: 192.168.2.1 fritz.box fb # unknown 192.168.2.16 acer ac # Leap_15.1 192.168.2.11 susa se # SuSE_13.2 It is no problem to start a program, e.g. urxvt, from acer on susa. I simply do it by setting $DISPLAY to susa:0.0 on acer: setenv DISPLAY susa:0.0 urxvt & But the inverse setting does not work: setenv DISPLAY acer:0.0 urxvt & This produces the following error message: "urxvt: can't open display acer:0.0, aborting." In other words, a setting of $DISPLAY under SuSE_13.2 works no more under Leap_15.1. Also, disabling access control by setting xhost + does not help. What can I do to force acer to accept setting $DISPLAY to acer:0.0 ? Thanks in advance and best regards, Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

10 16

[opensuse] How can I set up an NFS server
by Wolfgang Mueller 16 Aug '19

16 Aug '19

Recently I installed Leap 15.1 on one of my computers. Since there is no NFS server available any more in Yast, I tried to make it run manually, setting up an /etc/exports file and enabling and starting "nfsserver" in the Services Manager of Yast, but in vain. Can somebody explain me, how to do it correctly? Thanks in advance and best regards, Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 5

[opensuse] Starting a program at boot time
by Wolfgang Mueller 15 Aug '19

15 Aug '19

In the good old days, it was sufficient to make a link to the program in /etc/init.d/rc3.d and /etc/init.d/rc5.d for starting it at boot time: /etc/init.d/rc3.d/S50My_program -> /home/wolfgang/bin/My_program /etc/init.d/rc5.d/S50My_program -> /home/wolfgang/bin/My_program But now under Leap 15.1, that does not work any more. Is there any other way to start a program a boot time? Thanks in advance, Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 18

[opensuse] Now I get martians on wlan0
by Carlos E. R. 15 Aug '19

15 Aug '19

Hi, After configuring eth0 to also have an IPv6 addresses, I get martians on wlan, which configured to get address via dhcp6 only, in order to detect when/if the ISP provides it. And of course, it never gets one. Isengard:~ # iwconfig lo no wireless extensions. wlan0 IEEE 802.11 ESSID:"......." Mode:Managed Frequency:2.437 GHz Access Point: 70:8B:CD:59:88:3C Bit Rate=150 Mb/s Tx-Power=22 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on Link Quality=62/70 Signal level=-48 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:17 Missed beacon:0 eth0 no wireless extensions. Isengard:~ # ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 4c:cc:6a:61:50:a1 brd ff:ff:ff:ff:ff:ff inet 192.168.1.16/24 brd 192.168.1.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fc00::16/64 scope global valid_lft forever preferred_lft forever inet6 fe80::4ecc:6aff:fe61:50a1/64 scope link valid_lft forever preferred_lft forever 3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether a0:d3:7a:82:b3:4c brd ff:ff:ff:ff:ff:ff inet6 fe80::a2d3:7aff:fe82:b34c/64 scope link valid_lft forever preferred_lft forever Isengard:~ # Isengard:~ # systemctl status network ● wicked.service - wicked managed network interfaces Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled; vendor preset: disabled) Active: active (exited) since Tue 2019-06-25 14:15:54 CEST; 1 months 13 days ago Process: 29081 ExecReload=/usr/sbin/wicked --systemd ifreload all (code=exited, status=0/SUCCESS) Main PID: 1232 (code=exited, status=0/SUCCESS) CPU: 56ms Jun 25 14:15:54 Isengard systemd[1]: Started wicked managed network interfaces. Aug 08 00:16:49 Isengard systemd[1]: Reloading wicked managed network interfaces. Aug 08 00:17:20 Isengard wicked[24538]: eth0 device-ready Aug 08 00:17:20 Isengard wicked[24538]: eth0 up Aug 08 00:17:20 Isengard wicked[24538]: wlan0 setup-in-progress Aug 08 00:17:20 Isengard systemd[1]: Reloaded wicked managed network interfaces. Aug 08 02:37:32 Isengard systemd[1]: Reloading wicked managed network interfaces. Aug 08 02:38:03 Isengard wicked[29081]: wlan0 device-ready Aug 08 02:38:03 Isengard wicked[29081]: wlan0 setup-in-progress Aug 08 02:38:03 Isengard systemd[1]: Reloaded wicked managed network interfaces. Isengard:~ # Why the martians? How do I stop them? <3.6> 2019-08-08T02:38:03.342398+02:00 Isengard wicked 29081 - - wlan0 device-ready <3.6> 2019-08-08T02:38:03.343768+02:00 Isengard wicked 29081 - - wlan0 setup-in-progress <3.6> 2019-08-08T02:38:03.344335+02:00 Isengard systemd 1 - - Reloaded wicked managed network interfaces. <0.4> 2019-08-08T02:42:34.133900+02:00 Isengard kernel - - - [3760166.225960] IPv4: martian source 192.168.1.255 from 192.168.1.16, on dev wlan0 <0.4> 2019-08-08T02:42:34.133934+02:00 Isengard kernel - - - [3760166.225966] ll header: 00000000: ff ff ff ff ff ff 4c cc 6a 61 50 a1 08 00 ......L.jaP... <0.4> 2019-08-08T02:42:35.977964+02:00 Isengard kernel - - - [3760168.069377] IPv4: martian source 192.168.1.255 from 192.168.1.16, on dev wlan0 <0.4> 2019-08-08T02:42:35.977996+02:00 Isengard kernel - - - [3760168.069383] ll header: 00000000: ff ff ff ff ff ff 4c cc 6a 61 50 a1 08 00 ......L.jaP... <0.4> 2019-08-08T02:42:35.978000+02:00 Isengard kernel - - - [3760168.070591] IPv4: martian source 192.168.1.255 from 192.168.1.16, on dev wlan0 <0.4> 2019-08-08T02:42:35.978003+02:00 Isengard kernel - - - [3760168.070594] ll header: 00000000: ff ff ff ff ff ff 4c cc 6a 61 50 a1 08 00 ......L.jaP... <0.4> 2019-08-08T02:42:38.129903+02:00 Isengard kernel - - - [3760170.219883] IPv4: martian source 192.168.1.255 from 192.168.1.16, on dev wlan0 <0.4> 2019-08-08T02:42:38.129933+02:00 Isengard kernel - - - [3760170.219889] ll header: 00000000: ff ff ff ff ff ff 4c cc 6a 61 50 a1 08 00 ......L.jaP... <0.4> 2019-08-08T02:42:38.129938+02:00 Isengard kernel - - - [3760170.222373] IPv4: martian source 192.168.1.255 from 192.168.1.16, on dev wlan0 <0.4> 2019-08-08T02:42:38.129941+02:00 Isengard kernel - - - [3760170.222379] ll header: 00000000: ff ff ff ff ff ff 4c cc 6a 61 50 a1 08 00 ......L.jaP... 192.168.1.16 is the same machine. 192.168.1.3 is the printer. (machine runs Leap 15.0) -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

6 12

[opensuse] Linux Kernel Allows 0.0.0.0/8 as a Valid Address Range
by James Knott 15 Aug '19

15 Aug '19

IPv6 has been around for years. Why don't some people get with the program, instead of coming up with hacks to get around the address shortage. Even with this block, there still won't be enough IPv4 addresses just for mobile devices, let alone everything else. The longer people take to move to IPv6, the worse the problem is going to get. By comparison, on IPv6, the smallest address block, /64 provides as many addresses as the entire IPv4 address space squared. I get 256 of those /64s from my ISP. Some ISPs provide 65K of them to each customer. Why are we wasting our time trying to squeeze more life out of something that should have been retired years ago? Incidentally, this block represents less than 0.4% of the IPv4 address space. Will it really make a difference? https://www.technotification.com/2019/08/linux-kernel-allows-0-0-0-0-8-as-a… -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

8 59

[opensuse] Repository appears to be outdated. Consider using a different mirror or server.
by Admin Beckspaced 14 Aug '19

14 Aug '19

Dear opensuse users, since weeks I do receive this message when checking for updates: zypper up Loading repository data... Warning: Repository 'Hauptaktualisierungs-Repository (NON-OSS)' appears to be outdated. Consider using a different mirror or server. Reading installed packages... Nothing to do. The repo in question is: leap-15.0-repo-update-non-oss Hauptaktualisierungs-Repository (NON-OSS) http://download.opensuse.org/update/leap/15.0/non-oss/ Is there anything I can do to resolve this? Already cleaned the repo. Did a repo refresh. Tried the https URI Nothing actually really helped ... should I be worried about this? thanks & greetings Becki -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] geoip with 4.12.14-lp151.28.10-default
by Holger Jakob 13 Aug '19

13 Aug '19

I am considering to upgrade from 15.0 to 15.1 but cannot see the respective package to support GEOIP at the kernel level (xtables-addons-kmp-default) in the repositories. Does that mean xt_geoip.ko is not available and thus package xtables-geoip is broken in 15.1? I searched the buglist and could only find an entry for 15.0: Bug 1098188 - iptables geoip is not working kernel 4.12.14-lp150.12.4-default Does that not mean 15.1 is affected as well? Any recommendations for a work around? Holger -- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 14