March 2024 - openSUSE Users - openSUSE Mailing Lists

RFC 6724
by James Knott 20 Aug '24

20 Aug '24

I was reading about proposed changes to RFC 6724 which determines the priority for IP address selection. In the original RFC 6724, IPv4 addresses are given preference to IPv6 Unique Local Addresses (ULA). The proposed changes would reverse that. However, in testing with ping, I see ULA is preferred, except for the computer being used for testing from. That is when a computer is pinging itself. Why the difference? Why is the proposed priority used when pinging a different device, but not the same device? Also, if I use the FQDN, instead of just the host name, then ULA is used. WTF??? I'm using the DNS resolver in pfSense. The host command returns both IPv4 and ULA addresses for both host name and FQDN Original - https://datatracker.ietf.org/doc/html/rfc6724 Proposed - https://datatracker.ietf.org/doc/draft-ietf-6man-rfc6724-update/ Running openSUSE 15.5 & KDE.

10 14

No Login, no Graphics after update to Tumbleweed 20230211-0
by Peter Maffter 20 Aug '24

20 Aug '24

Hello, after the update the screen only shows a '-'. All the usual other tty screens that you get with e.g. STRG-ALT-F1 are also gone. I can connect to the PC via ssh from my Ubuntu Laptop and check what is going on. I am using an old GTX 570 on that PC. Previously when the G06 stuff was installed instead of updating the needed G04 stuff, I was able to install NVIDIA-Linux-x86_64-390.157.run manually and the login and XFCE worked. But now even that fails. :-( Any pointers? Is that the beginning of the things that are named in Subject "Nvidia 390x driver users - glibc 2.37 will bring bad news" ? I do have strange output about signature and verification: 2023-02-13T00:08:13.628957+01:00 machine4 kernel: [ 3.411047][ T527] nvidia: loading out-of-tree module taints kernel. 2023-02-13T00:08:13.628957+01:00 machine4 kernel: [ 3.411690][ T527] nvidia: module license 'NVIDIA' taints kernel. 2023-02-13T00:08:13.628958+01:00 machine4 kernel: [ 3.412304][ T527] Disabling lock debugging due to kernel taint 2023-02-13T00:08:13.628958+01:00 machine4 kernel: [ 3.418769][ T527] nvidia: module verification failed: signature and/or required key missing - tainting kernel 2023-02-13T00:08:13.628963+01:00 machine4 kernel: [ 3.426827][ T538] tg3 0000:0d:00.0 eth0: Tigon3 [partno(BCM57781) rev 57785100] (PCI Express) MAC address 00:25:22:e6:5d:d3 2023-02-13T00:08:13.628964+01:00 machine4 kernel: [ 3.427483][ T538] tg3 0000:0d:00.0 eth0: attached PHY is 57765 (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1]) 2023-02-13T00:08:13.628964+01:00 machine4 kernel: [ 3.428122][ T538] tg3 0000:0d:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1] 2023-02-13T00:08:13.628965+01:00 machine4 kernel: [ 3.428740][ T538] tg3 0000:0d:00.0 eth0: dma_rwctrl[00000001] dma_mask[64-bit] 2023-02-13T00:08:13.628965+01:00 machine4 kernel: [ 3.482616][ T527] nvidia-nvlink: Nvlink Core is being initialized, major device number 241 2023-02-13T00:08:13.628966+01:00 machine4 kernel: [ 3.488784][ T527] nvidia 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem 2023-02-13T00:08:13.628971+01:00 machine4 kernel: [ 3.489637][ T527] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 390.157 Wed Oct 12 09:19:07 UTC 2022 (using threaded interrupts) 2023-02-13T00:08:13.628972+01:00 machine4 kernel: [ 3.499362][ T527] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 390.157 Wed Oct 12 09:15:25 UTC 2022 2023-02-13T00:08:13.628972+01:00 machine4 kernel: [ 3.505733][ T527] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver 2023-02-13T00:08:13.628973+01:00 machine4 kernel: [ 3.506428][ T527] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 1 Update openSUSE Tumbleweed 20230211-0 -> 20230212-0 did not help either. Boot to the recover modes of 6.1.10-1 or 6.1.8-1 does not help . 6.1.8-1 recovery at least says that "Failed to start X Display Manager" and gives the F1,F2,...ttys. but when I install NVIDIA-Linux-x86_64-390.157.run the F1,F2, ttys are also gone. Please help. Thanks in advance BR Pete

13 73

[oS-EN] [Leap 15.6 Alpha] Laicolasse - Beta
by Carlos E. R. 19 Aug '24

19 Aug '24

Hi, After a kernel Oops when attempting to connect via WiFi, on the next boot Network Manager is gone. How do I put it back in the panel? Using XFCE. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.6 Beta (Laicolasse))

6 7

Re: [opensuse] ZFS on SuSE-anyone, Distributed File System...
by Verner Kjærsgaard 16 Aug '24

16 Aug '24

Michael Folsom skrev: > Hi: > > Quick question - what are the advantages of ZFS over XFS? > > I'm not trying to start a flame war but as a happy XFS user wonder > what ZFS has to offer> > > Later - > > > Mike > > On Tue, Jun 10, 2008 at 2:35 PM, Verner Kjærsgaard <vk(a)os-academy.dk> wrote: >> Hi list, >> >> - has anyone tried SUN's ZFS on SuSE? Can it be done, is it at all feasible? >> >> - or another Distributed file system. I may need a file system, that will allow me to add storage ad hoc. >> >> Any hints, links? >> >> As always, thanks! >> >> -- >> -------------------------------------------- >> Med venlig hilsen/best regards >> Verner Kjærsgaard >> Novell Certified Linux Professional 10035701 >> www.os-academy.dk +45 56964223 >> -- >> To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org >> For additional commands, e-mail: opensuse+help(a)opensuse.org >> > I really don't know, if any? Are they not two different beasts? I tried looking for info about XFS, any good links, homepage? -- -------------------------------------------- Med venlig hilsen/best regards Verner Kjærsgaard Novell Certified Linux Professional 10035701 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

4 3

[opensuse] boot32.efi for 64 bits processor and Leap
by jdd 16 Aug '24

16 Aug '24

Hello, We see more and more often very small but powerfull computers, atom multicore 64 bits, but with UEFI 32 bits firmware. I have one now ("It Works TW891" paid 129€ - 32Gb ssd + 2Gb ram, runs almost perfectly windows 10 32bits or Debian 64bits). these computers can be installed with 64 bits distros, but they need absolutely a 32 bits loader. Right now I on ly know of the hybrid debian 32/64bits dvd to be able to install. Notice that *only the loader* have to be 32bits, the generic name being boot32.efi copying a generic loader to the Leap EFI folder allows booting, and probably installing (I couldn't make all the tests), but the generic one gives only a grub prompt, not handy. Could it be possible to add to the Leap isos this 32 bits loader? only this one have to be 32bits, AFAIK nothing else have to be changed. thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 9

[opensuse] How to make sure that each vNIC in guest is always associated with a correct VLAN?
by Martin T 14 Aug '24

14 Aug '24

Hi, I have six virtual bridges in xen host machine and following virtual machine configuration file section defining the vifs: vif = [ 'bridge=br10', 'bridge=br20', 'bridge=br30', 'bridge=br40', 'bridge=br50', 'bridge=br60' ] This means that in the guest(openSUSE Leap 42.1) I have six vNICs(eth0 - eth5). Can I be sure that eth0 is always connected to br10, eth1 to br20, etc? Or should I specify a MAC address for each vNIC created like this: vif = [ 'bridge=br10, mac=00:14:5E:11:C6:F1', 'bridge=br20, mac=00:14:5E:11:C6:F2', 'bridge=br30, mac=00:14:5E:11:C6:F3', 'bridge=br40, mac=00:14:5E:11:C6:F4', 'bridge=br50, mac=00:14:5E:11:C6:F5', 'bridge=br60, mac=00:14:5E:11:C6:F6' ] .. and then configure udev rules which make sure that interface associated with MAC 00:14:5E:11:C6:F1 and br10 is always named eth0, interface associated with MAC 00:14:5E:11:C6:F2 and br20 is always named eth1, etc? Or maybe there is a better way using /etc/sysconfig/network/ifcfg-* files? thanks, Martin -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 5

Bad blocks on a ReiserFS volume. How to retrieve files?
by Silviu Marin-Caea 14 Aug '24

14 Aug '24

I have a large hard-disk (120 GB) on which some blocks went bad. Now, it cannot be mounted. Attached is what debugreiserfs says. What can I do; I'm newbie to reiserfs architecture. I thought that ReiserFS keeps copies of the superblock or something, like ext2/3 does. reiserfsck says "error occured looks like hardware problem. bread cannot read block 13271040". That's the actual number it displays. PS I have asked the same question on the reiserfs-list, but it's extremely low traffic. Maybe someone here knows more. Thank you Filesystem state: consistency is not checked after last mounting Reiserfs super block in block 16 on 0x1642 of format 3.6 with standard journal Count of blocks on the device: 29945160 Number of bitmaps: 914 Blocksize: 4096 Free blocks (count of blocks - used [journal, bitmaps, data, reserved] blocks): 29154954 Root block: 14969 Filesystem is NOT clean Tree height: 4 Hash function used to sort names: "r5" Objectid map size 10, max 972 Journal parameters: Device [0x0] Magic [0x34ae2c74] Size 8193 blocks (including 1 for journal header) (first block 18) Max transaction length 1024 blocks Max batch size 900 blocks Max commit age 30 Blocks reserved by journal: 0 Fs state field: 0x0 sb_version: 2 inode generation number: 35482 UUID: 48d29ced-fe37-4c68-adf8-32ace9f2be45 LABEL: Set flags in SB: ATTRIBUTES CLEAN

3 4

[opensuse] LABEL : using tune2fs to create swap partition label
by ellanios82 10 Jul '24

10 Jul '24

Hello List . what please is correct syntax to create label for swap partition : - am getting error : " tune2fs: No such file or directory while trying to open swap Couldn't find valid filesystem superblock " .............. thanks -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 3

kde6 for leap?
by cagsm 09 Jul '24

09 Jul '24

Users, the new KDE 6 release, is this feasibly for next leap? ty

9 11

1st microOS fails boot
by bent fender 04 Jul '24

04 Jul '24

snapshot of realsnapshot opened w. gimp on my TW splashma6 DT: https://imgur.com/vb1wwCR.png it's about permission denied for swap? /etc/fstab: https://paste.opensuse.org/pastes/6dff150c46fd mOS is on partition 17, I wanted to test Audacity # fdisk -l Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: Samsung SSD 860 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 2CB71AC7-D2DB-4B81-A559-02802643D197 Device Start End Sectors Size Type /dev/sda1 2048 2099199 2097152 1G Linux filesystem /dev/sda2 1348483072 1350580223 2097152 1G BIOS boot /dev/sda3 4196352 16779263 12582912 6G Linux swap /dev/sda4 16779264 16781311 2048 1M Linux filesystem /dev/sda5 16781312 16783359 2048 1M Linux filesystem /dev/sda6 16783360 16785407 2048 1M Linux filesystem /dev/sda7 16785408 16787455 2048 1M Linux filesystem /dev/sda8 16787456 16789503 2048 1M Linux filesystem /dev/sda9 16789504 16791551 2048 1M Linux filesystem /dev/sda10 16791552 593508351 576716800 275G Linux filesystem /dev/sda11 593508352 761280511 167772160 80G Linux filesystem /dev/sda12 761280512 929052671 167772160 80G Linux filesystem /dev/sda13 929052672 1096824831 167772160 80G Linux filesystem /dev/sda14 1096824832 1264596991 167772160 80G Linux filesystem /dev/sda15 1350580224 1518352383 167772160 80G Linux filesystem /dev/sda16 1518352384 1686124543 167772160 80G Linux filesystem /dev/sda17 1686124544 1853896703 167772160 80G Linux filesystem Partition table entries are not in disk order. Disk /dev/sdb: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors Disk model: WDC WD20EZBX-00A Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 6EED7FA9-4976-4436-9309-71A2D6371B80 Device Start End Sectors Size Type /dev/sdb1 2048 3907029134 3907027087 1.8T Linux filesystem Disk /dev/sdd: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors Disk model: WDC WD4004FZWX-0 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 5B4D1C05-A8F3-4016-8848-C666C8A320C3 Device Start End Sectors Size Type /dev/sdd1 2048 7814037134 7814035087 3.6T Linux filesystem

7 8