September 2021 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Kernel compilation the openSUSE way?
by Bjoern Voigt 28 Nov '21

28 Nov '21

I usually take the newest openSUSE kernel (from repository Kernel_stable). But since some month I have a DVB T2 HD card, which requires a patch (see https://bugzilla.kernel.org/show_bug.cgi?id=194171). So I need to compile kernels myself. I have a working compilation path. But the current path has 12 steps! It takes some time. I wonder, why it is so complicated to configure, compile and install a Kernel under openSUSE. Is there a better/easier/automated way to configure, compile and install a Kernel under openSUSE? I know this blog article. But the article uses Vanilla kernels and also needs 6 steps. With additional patches (4 steps), third-party modules (2 steps) and cleanup (1 step) the article would also need 13 steps: Compiling the Linux Kernel, the SUSE way https://www.suse.com/communities/blog/compiling-de-linux-kernel-suse-way/ This is my Kernel configuration, compilation and installation path: 1. Update kernel-source and kernel-default from Kernel_stable repository 2. Save kernel-source: cp -a /usr/src/linux-4.x.y-... /usr/src/linux-4.x.y-my 3. Apply my patches cd /usr/src/linux-4.x.y-my patch -b -p1 < ~myuser/.../my-kernel-patch.patch 4. Copy standard configuration: cd /usr/src/linux-4.x.y-my cp -v /boot/config-4.11.4-1.gcba98ee-default .config 5. Edit .config: remove CONFIG_LOCALVERSION, CONFIG_DEBUG_KERNEL, CONFIG_EXPERT remove some hardware-dependent settings 6. edit configuration interactively: Disable CONFIG_EXPERT and CONFIG_DEBUG_KERNEL, because otherwise "make binrpm-pkg" creates huge kernel binaries. make oldconfig [...] Local version - append to kernel release (LOCALVERSION) [] (NEW) -my1 * * Configure standard kernel features (expert users) * Configure standard kernel features (expert users) (EXPERT) [N/y/?] (NEW) Kernel debugging (DEBUG_KERNEL) [N/y/?] (NEW) make menuconfig Do some additional configuration. 7. Compile kernel (-j4 for four processor cores, ionice and nice to reduce the load, binrpm-pkg for RPM without source-RPM) make clean nice ionice -c idle make -j4 binrpm-pkg 8. Install the kernel RPM package rpm -Uvh /usr/src/packages/RPMS/x86_64/kernel-4.x.y_my1-....x86_64.rpm 9. Install necessary symbolic links for "dkms" cd /lib/modules/4.x.y-my1 ln -sv /usr/src/linux-4.x.y-my source ln -sv /usr/src/linux-4.x.y-my build 10. Update third-party modules (e.g. Nvidia driver): dkms install -m nvidia -v 375.66 -k 4.x.y-my1 11. Cleanup cd /usr/src/linux-4.x.y-my make clean 12. Select Grub configuration and reboot grub2-once --list | less grub2-once 2 reboot Greetings, Björn -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 13

MS Teams on current Tumbleweed
by Roger Oberholtzer 08 Oct '21

08 Oct '21

I have been using Teams on Tumbleweed without problems. After the last update to Tumbleweed, I now get this when running teams: [105506.729217] traps: Chrome_IOThread[2342] trap invalid opcode ip:5604615e6934 sp:7f4873ffd490 error:0 in teams[56045eff0000+5fbe000] Teams itself was not updated, and there seems not to be a new version available. I am using 1.4.00.13653-1 from the MS Linux repository. Anyone else see this? -- Roger Oberholtzer

5 6

[oS-en] They are talking of us :-)
by Carlos E. R. 03 Oct '21

03 Oct '21

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 at news:alt.folklore.computers or news:sci.crypt If you don't have an nntp client set up, you can see it here: https://groups.google.com/g/alt.folklore.computers/c/VM5_IvSR6gw - -- Cheers, Carlos E. R. (from openSUSE Leap 15.2 x86_64 (Minas Tirith)) -----BEGIN PGP SIGNATURE----- iJIEAREIADoWIQQt/vKEw5659AgM/X2NrxRtxRYzXAUCYVWMJBwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJEI2vFG3FFjNcX+8A/31aoU81jd98hZ2cRbPT pz3FiflM6ZTOTHRmAvJ7URfuAP9SzYXfvrDqRVrw3iUV4D3dkbYiVn6JEFl2mufn 9fEBIw== =rzBm -----END PGP SIGNATURE-----

9 34

oS 15.3 KDE mounting removable drives
by Roger Oberholtzer 01 Oct '21

01 Oct '21

My oS 15.3 / KDE (up-to-date as of today) does not pop up a window offering some activity when a removable USB drive is connected. The devices show up correctly in the system in general and can be mounted. But there is no activity in KDE. When looking at the Device Actions in the system configuration, I see that in the Open with File Manager menu, it says that "The device property Drive Type must equal Floppy" must match. A couple questions: Do USB drives have this property? How can I determine what the Drive Type for a USB disk is? How can I remove this requirement? I see that the field for Floppy is text, not a list of predefined types. Of course, it might be some other of the properties defined in this menu. I have: Ignored must equal false Usage must equal FileSystem type is StorageAccess DriveType must equal Floppy Do folks where this is working have the same settings? -- Roger Oberholtzer

2 1

jeos
by jdd＠dodin.org 01 Oct '21

01 Oct '21

Hello, I recently noticed my ISP (french "Free") that give me a new modem, in fact was giving a real computer. This computer have 4Gb ram (extendable up to 16Gb at least) and *4* sata disks places, raid capable. I fitted them with two old 350Gb laptop HDD and could create a raid1 array (ext4). then I could create a virtual machine (I don't know what is the software used, proprietary interface). Right now only for test purpose, 1Gb ram and 50Gb HDD. This FAI provided several templates as guest. One of them was openSUSE JeOs!! - the modem is arm powered (armada 8040). This install went perfectly well. less than 1.2Gb install :-). I had and could easily extend the disk and the system from 2Gb to the 50Gb size wanted. Yast is available. What I would like to know is is I can use it like my favorite Leap 15.3, server mode. The VM is EFI and BTRFS. Are the available applications for arm identical with the amd64 ones? any thing I have to know? The wiki is very short about jeos (https://en.opensuse.org/Portal:JeOS) thanks jdd -- http://dodin.org

2 3

zypper up with non-SUSE repos in Tumbleweed
by George from the tribe 30 Sep '21

30 Sep '21

Can someone tell me if this is a bad idea and why - I want to do regular updates, like security updates to google chrome and things like that, for all my programs and apps that are managed by non-openSUSE repositories. Then do regular zypper dup updates for the whole system only like once a month. That way I minimize my chances of something breaking right before a critical business trip or something like that, but still keep my security up to date. Any thoughts?

8 20

Updating Tumbleweed (zypper dup) - 3 problems:
by -pj 29 Sep '21

29 Sep '21

Hi, I am attempting to update my computer (openSUSE Tumbleweed with KDE plasma desktop installed). pj@localhost:~> sudo zypper dup [sudo] password for root: Loading repository data... Reading installed packages... Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Computing distribution upgrade... 3 Problems: Problem: the to be installed pipewire-0.3.35-1.2.x86_64 requires 'libpipewire-0_3-0 = 0.3.35', but this requirement cannot be provided Problem: the to be installed gstreamer-plugin-pipewire-0.3.36-2.1.x86_64 requires 'libpipewire-0.3.so.0()(64bit)', but this requirement cannot be provided Problem: the to be installed kwin5-5.22.5-1.2.x86_64 requires 'libpipewire-0.3.so.0()(64bit)', but this requirement cannot be provided Problem: the to be installed pipewire-0.3.35-1.2.x86_64 requires 'libpipewire-0_3-0 = 0.3.35', but this requirement cannot be provided deleted providers: libpipewire-0_3-0-0.3.35-2.4.x86_64 not installable providers: libpipewire-0_3-0-0.3.35-1.2.i586[download.opensuse.org-oss] libpipewire-0_3-0-0.3.35-1.2.x86_64[download.opensuse.org-oss] Solution 1: install libpipewire-0_3-0-0.3.35-1.2.x86_64 from vendor openSUSE replacing libpipewire-0_3-0-0.3.35-2.4.x86_64 from vendor http://packman.links2linux.de Solution 2: install pipewire-0.3.36-2.1.x86_64 from vendor http://packman.links2linux.de replacing pipewire-0.3.35-1.1.x86_64 from vendor openSUSE Solution 3: keep obsolete libpipewire-0_3-0-0.3.35-2.4.x86_64 Solution 4: break pipewire-0.3.35-1.2.x86_64 by ignoring some of its dependencies Choose from above solutions by number or skip, retry or cancel [1/2/3/4/s/r/c/d/?] (c): ===================================================================================================== 1. I think I have been told or read somewhere that the best option is to select the install from packman solution for each instance. 2. About 2 weeks ago I did select the packman option for a couple of problems. 3. What do you recommend? I wanted to put my mind to rest on this issue. -Regards and thanks once again.

2 2

wireshark using remote interface
by Dave Howorth 29 Sep '21

29 Sep '21

I want to monitor traffic on an interface on a remote machine and can't see the best way to do that. I have wireshark on my opensuse box and want to monitor traffic on the wlan0 wireless interface on a headless pi. I started by putting wireshark on the pi and remoting its interface via ssh-X to the opensuse box, but that gives me strange options in the capture window (ciscodump et al). Whenever I google I get confused about which end is 'remote' and which end is 'local'. I also tried installing tcpdump on the pi and got that to display in the opensuse xterm I'm running ssh to the pi in. But I don't understand how to connect that to wireshark. So what's best? Should I be running wireshark on the pi but displayed on the opensuse box, and if so how do I get it to show me the pi's interfaces? Or should I be running wireshark on the opensuse box and if so how do I get it to show me the pi's interfaces?

4 12

Yast Partitioner: Device Graph missing in Leap 15.3?
by Thomas Wagner 28 Sep '21

28 Sep '21

Hi! I upgraded to Leap 15.3 and the "Device Graphs" section in Yast -> Partitioner went missing. "zypper verify" says all dependencies are met after the upgrade. Does anyone have an idea, how to get the "Device Graphs" section back? Best regards Thomas

1 1

YaST is failing to set up wi-fi (wlan0) interface correctly.
by Marc Chamberlin 28 Sep '21

28 Sep '21

Hi - I have ran into a sudden unexpected failure on Yast2's part in setting up my wi-fi interface that I need help with. I am running OpenSuSE Leap 15.2 on my laptop, x64 bit version. I have had no problems with the wi-fi interface up until yesterday. I have a dual boot system where I can boot up Windows 10 on this laptop also. Windows 10 does NOT have any problems with the wi-fi interface so I can be pretty certain this is not a hardware failure. My problem began with either one of two events, the first being I had just updated my laptop with a bunch of updates, didn't keep track of what was installed, and cannot say for certain that the updates are the culprit. Second, I then attempted to use Yast to set up my wi-fi (wlan0) to use my Android phone as a mobile hotspot. (this is something I very rarely do, but was necessary in order to run a zoom session for a neighborhood meeting) The only thing I did in Yast was to scan for and change the access point so that my laptop would use my mobile phone instead. Everything else remains the same, account user name, password, encryption etc. And it failed! I couldn't figure out why so gave up and tried to reset Yast to use the access point that I normally use in my house, and that too failed in the same way. I got no idea why, I have rechecked all my setting in Yast and nothing else has changed or been touched. I even compared all the Yast settings for the wlan0 interface with another laptop that works, and no differences were found other than hostname. Lots of Googling has enabled me to find a workaround and get the wlan0 interface working, but it is a bit squirrelly and not exactly a repeatable sequence of commands to get the interface working again. FYI I use a dhcpd service to get an IP address for my laptop, but even setting it up with a static IP address still results in Yast not getting the interface to work. The workaround is as follows - After attempting to set up the wlan0 interface with Yast, I execute the following two commands to see if the interface is working and whether I have an IP address - > marcslaptop:/var/log # iwconfig wlan0 > wlan0 IEEE 802.11 ESSID:off/any > Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm > Retry short limit:7 RTS thr:off Fragment thr:off > Encryption key:off > Power Management:on > > marcslaptop:/var/log # ifconfig > eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 > ether 38:d5:47:31:54:0f txqueuelen 1000 (Ethernet) > RX packets 0 bytes 0 (0.0 B) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 0 bytes 0 (0.0 B) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 > inet 127.0.0.1 netmask 255.0.0.0 > inet6 ::1 prefixlen 128 scopeid 0x10<host> > loop txqueuelen 1000 (Local Loopback) > RX packets 22 bytes 2640 (2.5 KiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 22 bytes 2640 (2.5 KiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 > ether e4:a7:a0:46:83:e0 txqueuelen 1000 (Ethernet) > RX packets 0 bytes 0 (0.0 B) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 0 bytes 0 (0.0 B) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 As you can see, no joy. So my next step is to see if the wlan0 NIC can hear anything - > marcslaptop:/var/log # iwlist wlan0 scan > wlan0 Scan completed : > Cell 01 - Address: 00:12:17:A1:B0:10 > Channel:1 > Frequency:2.412 GHz (Channel 1) > Quality=32/70 Signal level=-78 dBm > Encryption key:on > ESSID:"hamshack" > Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s > 24 Mb/s; 36 Mb/s; 54 Mb/s > Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s > Mode:Master > Extra:tsf=000000630301e649 > Extra: Last beacon: 3420ms ago > IE: Unknown: 000868616D736861636B > IE: Unknown: 010882848B962430486C > IE: Unknown: 030101 > IE: Unknown: 2A0100 > IE: Unknown: 2F0100 > IE: IEEE 802.11i/WPA2 Version 1 > Group Cipher : CCMP > Pairwise Ciphers (1) : CCMP > Authentication Suites (1) : PSK > IE: Unknown: 32040C121860 > IE: Unknown: DD06001018020004 > Cell 02 - Address: 98:DE:D0:F9:93:CA > Channel:6 > Frequency:2.437 GHz (Channel 6) > Quality=70/70 Signal level=-21 dBm > Encryption key:on > ESSID:"ChamberlinCupola" > Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s > 24 Mb/s; 36 Mb/s; 54 Mb/s > Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s > Mode:Master > Extra:tsf=0000004db69159e4 > Extra: Last beacon: 3144ms ago > IE: Unknown: 00104368616D6265726C696E4375706F6C61 > IE: Unknown: 010882848B962430486C > IE: Unknown: 030106 > IE: Unknown: 2A0100 > IE: Unknown: 2F0100 > IE: IEEE 802.11i/WPA2 Version 1 > Group Cipher : CCMP > Pairwise Ciphers (1) : CCMP > Authentication Suites (1) : PSK > IE: Unknown: 32040C121860 > IE: Unknown: 0B0506001D0000 > IE: Unknown: > 2D1AFE1917FFFF000001000000000000000000000000000000000000 > IE: Unknown: > 3D1606051700000000000000000000000000000000000000 > IE: Unknown: 7F080400080000000040 > IE: Unknown: > DD760050F204104A0001101044000102103B00010310470010D96C7EFC2F8938F1EFBD6E5148BFA8121021000754502D4C494E4B10230005415033303010240006313233343536104200033030311054000800060050F2040001101100054150333030100800022008103C0001031049000600372A000120 > IE: Unknown: DD090010180206000C0000 > IE: Unknown: > DD180050F2020101840003A4000027A4000042435E0062322F00 > IE: Unknown: 46057208010000 > Cell 03 - Address: 88:DC:96:41:72:9F > Channel:11 > Frequency:2.462 GHz (Channel 11) > Quality=70/70 Signal level=-34 dBm > Encryption key:on > ESSID:"EnGeniusAP" > Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s > 9 Mb/s; 12 Mb/s; 18 Mb/s > Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s > Mode:Master > Extra:tsf=0000000cf0f00dbe > Extra: Last beacon: 3036ms ago > IE: Unknown: 000A456E47656E6975734150 > IE: Unknown: 010882848B960C121824 > IE: Unknown: 03010B > IE: Unknown: 0706555320010B1E > IE: Unknown: 2A0100 > IE: IEEE 802.11i/WPA2 Version 1 > Group Cipher : CCMP > Pairwise Ciphers (1) : CCMP > Authentication Suites (1) : PSK > IE: Unknown: 32043048606C > IE: Unknown: > 2D1AAD0103FFFF000000000000000000000100000000000000000000 > IE: Unknown: > 3D160B080400000000000000000000000000000000000000 > IE: Unknown: 4A0E14000A002C01C800140005001900 > IE: Unknown: 7F080100000000000040 > IE: Unknown: > DD180050F2020101000003A4000027A4000042435E0062322F00 > IE: Unknown: DD0900037F01010000FF7F > Cell 04 - Address: BC:30:7D:F6:54:5E > Channel:52 > Frequency:5.26 GHz (Channel 52) > Quality=53/70 Signal level=-57 dBm > Encryption key:on > ESSID:"DIRECTV_WVB_24100A9C" > Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s > 36 Mb/s; 48 Mb/s; 54 Mb/s > Mode:Master > Extra:tsf=0000004db6437c22 > Extra: Last beacon: 2440ms ago > IE: Unknown: > 0014444952454354565F5756425F3234313030413943 > IE: Unknown: 01088C129824B048606C > IE: Unknown: 030134 > IE: Unknown: 050B0203000000000000000000 > IE: Unknown: > 2D1ACE0117FFFFFFFFFEFFFFFFFF1F000001000000000018E6E71900 > IE: Unknown: > 3D16340D0500000000000000000000000000000000000000 > IE: Unknown: > DD180050F2020101010003A4000027A4000042435E0062322F00 > IE: IEEE 802.11i/WPA2 Version 1 > Group Cipher : CCMP > Pairwise Ciphers (1) : CCMP > Authentication Suites (1) : PSK > IE: Unknown: DD0B002686010300DD00000101 > IE: Unknown: > DD220050F204104A00011010440001011049000600372A00012010490006002686000101 > Cell 05 - Address: 98:DE:D0:F9:93:C9 > Channel:149 > Frequency:5.745 GHz > Quality=70/70 Signal level=-31 dBm > Encryption key:on > ESSID:"ChamberlinCupola_5G" > Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s > 36 Mb/s; 48 Mb/s; 54 Mb/s > Mode:Master > Extra:tsf=0000000016bac041 > Extra: Last beacon: 560ms ago > IE: Unknown: > 00134368616D6265726C696E4375706F6C615F3547 > IE: Unknown: 01088C129824B048606C > IE: Unknown: 050400010000 > IE: IEEE 802.11i/WPA2 Version 1 > Group Cipher : CCMP > Pairwise Ciphers (1) : CCMP > Authentication Suites (1) : PSK > IE: Unknown: 0B050000010000 > IE: Unknown: > 2D1AEF0917FFFF000000000000000000000000000000000000000000 > IE: Unknown: > 3D16950D0000000000000000000000000000000000000000 > IE: Unknown: 7F080400080000000040 > IE: Unknown: BF0CB259810FFAFF0000FAFF0000 > IE: Unknown: C005019B000000 > IE: Unknown: C30402020202 > IE: Unknown: > DD310050F204104A000110104400010210470010D96C7EFC2F8938F1EFBD6E5148BFA812103C0001031049000600372A000120 > IE: Unknown: DD090010180200001C0000 > IE: Unknown: > DD180050F2020101840003A4000027A400004243BC0062326600 > IE: Unknown: 46057208010000 > So yes, wlan0 can hear OK, AND AMAZINGLY sometimes this is all that it takes to get wlan0 working which I check by executing - > marcslaptop:/var/log # ifconfig > eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 > ether 38:d5:47:31:54:0f txqueuelen 1000 (Ethernet) > RX packets 0 bytes 0 (0.0 B) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 0 bytes 0 (0.0 B) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 > inet 127.0.0.1 netmask 255.0.0.0 > inet6 ::1 prefixlen 128 scopeid 0x10<host> > loop txqueuelen 1000 (Local Loopback) > RX packets 22 bytes 2640 (2.5 KiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 22 bytes 2640 (2.5 KiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 > inet 192.168.10.10 netmask 255.255.255.0 broadcast > 192.168.10.255 > inet6 fe80::e6a7:a0ff:fe47:83e0 prefixlen 64 scopeid 0x20<link> > ether e4:a7:a0:46:83:e0 txqueuelen 1000 (Ethernet) > RX packets 315 bytes 33055 (32.2 KiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 136 bytes 39494 (38.5 KiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 But if ifconfig does not report that wlan0 got an ip address assigned to it, then I drop a bigger hammer, which so far always works - > marcslaptop:/var/log # ip link set wlan0 up So why am I now having to execute these manual steps after using Yast to set up wlan0? Can't say that looking through log files has been very helpful either and I am starting to get a bit out of my league here. I just want to be able to rely on Yast to set up my network interfaces. I haven't tried setting eth0 yet, will await for any helpful ideas first, before spinning my wheels with eth0. Thanks as always, in advance, for any help offered, I much appreciate it especially when I have wandered off into some sort of quagmire like this issue that suddenly sprung up on me! Marc C. -- *"The Truth is out there" - Spooky* *_ _ . . . . . . _ _ . _ _ _ _ . . . . _ . . . . _ _ . _ _ _ . . . . _ _ . _ . . _ . _ _ _ _ . _ . _ . _ . _ . * Computers: the final frontier. These are the voyages of the user Marc. His mission: to explore strange new hardware. To seek out new software and new applications. To boldly go where no Marc has gone before! (/This email is digitally signed and the electronic signature is attached. If you know how, you can use my public key to prove this email indeed came from me and has not been modified in transit. My public key, which can be used for sending encrypted email to me also, can be found at - https://keys.openpgp.org/search?q=marc@marcchamberlin.com or just ask me for it and I will send it to you as an attachment. If you don't understand all this geek speak, no worries, just ignore this explanation and ignore the signature key attached to this email (it will look like gibberish if you open it) and/or ask me to explain it further if you like./)

4 18