March 2020 - openSUSE Users - openSUSE Mailing Lists

[opensuse] initrd for nfsroot: only for a single system?
by Daniel Spannbauer 09 Mar '20

09 Mar '20

Hello, is a initrd create for nfsroot bound to a single mac address? Or can I boot several systems with the same initrd? Regards Daniel -- Daniel Spannbauer Systemadministration marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11 Rechbergstr. 4-6, D 87727 Babenhausen Mobil +49 171 4033220 http://www.marco.de/ Email ds(a)marco.de Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Tumbleweed and NVIDIA's drivers
by Roger Oberholtzer 09 Mar '20

09 Mar '20

A couple weeks ago, an update of the kernel in Tumbleweed caused problems if one was using the NVIDIA drivers. I now find that I need to start using those drivers (NVIDIA GPU code that I need to use). Has the problem been resolved? That is, will the NVIDIA drivers and a current Tumbleweed play nice together? Since there has been so little discussion, I suspect that all is working as expected. I have been happily using the Nouveau driver. But I guess I cannot do so any more... -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

8 21

[opensuse] Google
by Doug McGarrett 08 Mar '20

08 Mar '20

Running Tumbleweed. And Firefox. For a while, I was able to get FF to open in Google, but now it has reverted to the OpenSuse screen. This is a PITA! When I click on the FF icon, I want it to open in Google, because right after I click on the icon, I start typing the question, and it turns out that the Suse screen doesn't know anything about that and I have to type it over again. How do I get back so the icon opens in Google? Thanx--doug -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 10

[opensuse] Tumbleweed yast partitioner
by Michael Hamilton 07 Mar '20

07 Mar '20

I've noticed that the Tumbleweed yast partitioner doesn't complete all operations before exiting when finished is press. I can see the cryptsetup and mkfs running as a processes after it exits. In my case this would be for making a encrypted ext4 or xfs whole disk partition and file system on an external USB drive. Is it supposed to work that way? If so, perhaps it should tell the user not to do anything like unplug the drive before checking that all associated processes have completed. Michael -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] unsubscribe
by ka1ifq 07 Mar '20

07 Mar '20

-- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] CUDA versions on Tumbleweed
by Roger Oberholtzer 06 Mar '20

06 Mar '20

I am trying to set up a CUDA ecosystem that includes building CUDA based programs. I am targeting Tumbleweed. I have sorted out the details of getting CUDA 10.2 to compile stuff. I am now trying to get the run environment set up. I know that this is a known fun area. Anyway, I have some questions: CUDA 10 requires NVIDIA drivers >= 410.48. For Tumbleweed, this is satisfied for the G05 drivers (cards > 600). Unfortunately, the G04 drivers for older cards (which I have in my development system) is 390.132. When I try to run my shiny new program, I get: CUDA Error: CUDA driver version is insufficient for CUDA runtime version Which seems about right. As it turns out, in the CUDA development repo (http://developer.download.nvidia.com/compute/cuda/repos/opensuse15/x86_64/) there are newer G04 versions. However, these seem not to be specifically for Tumbleweed's 5.5.6 kernel. I am guessing that installing one of these will mess everything up. The Legacy info page at NVIDIA (https://www.nvidia.com/en-us/drivers/unix/legacy-gpu/) says that older cards are supported in the 390 series of drivers. But they seem to supply a newer version in the CUDA development area. Question 1: Why might NVIDIA not be supplying the latest G04 drivers in the Tumbleweed repo? It seems the drivers do exist. Anyone know why they are not the versions provided? Question 2: Has anyone installed a newer G04 (>= 410.48) driver on a current Tumbleweed? If so, how? Just installing the RPMs seems iffy. I am not certain there is a .run install with the newer G04 drivers. Or at least not that I can tell. I am guessing that I should just get a new NVIDIA card and skip all this nonsense. But where is the challenge in that? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 15

[opensuse] Re: [opensuse-kde] Bluetooth connection failure
by stakanov 06 Mar '20

06 Mar '20

In data venerdì 6 marzo 2020 10:14:06 CET, gumb ha scritto: > On 06/03/2020 05:23, Marc Chamberlin wrote: > > Hello - I am running OpenSuSE Leap 15.0 with version 5.12.5 of the > > Bluetooth applet on my ASUS laptop. I am trying to make a Bluetooth > > connection to a gadget I have (a TinyTrack4 with the Bluetooth adapter) > > and it is not succeeding. I have no problems with making a Bluetooth > > connection to my Android phone so I don't think I have done anything > > wrong in setting up this Bluetooth device and indeed the Bluetooth > > applet shows the TinyTrack4 as an available device I can connect to. But > > when I try to connect, it appears that I get a momentary successful > > connection but then it almost immediately disconnects. The messages log > > file shows the following error message - > > > > 2020-03-05T19:50:15.949381-08:00 marcslaptop plasmashell[2455]: > > org.kde.bluez: PendingCall Error: "In Progress" > > > > I have no idea what that means and Google was of no help either... And > > FWIW when I dual boot my laptop over to Windows 10, I have no problems > > connecting to my TinyTrack4 with the Bluetooth connection. > > > > So any and all help will be much appreciated, and thanks in advance... I > > hope some kind guru can guide me and my laptop to a joyful Bluetooth > > union with my TinyTrak4 gizmo... > > > > Marc... > > Whilst I can't offer any specific help, I've stumbled on a few quirks > and foibles with bluetooth recently. With one device I found that when > trying to pair the device using a PIN, or sending a file to the PC, > although the device sends the PIN / file, in Plasma the notification > doesn't pop up (this is on Leap 15.1) so it always fails. In that case I > was able to go into the Advanced Settings tab of Bluetooth Settings on > the PC, and check Accept automatically Trusted devices. > > With another device - a very very old feature phone, I've found the > connection drops after a few seconds. I've had to reboot the PC and > sometimes that gets it to make a stable connection. But using Wammu to > connect to the phone and transfer files, I can only succeed using a Leap > 42.3 installation on an old PC, not with Leap 15.1. > > gumb with me it has proven useful to go to 15.1 less problems. And when I have a dongle I extract it, wait for 30 seconds to be sure it unloaded and plug it. It is possible that windows sets the BT hardware in a non recoverable undocumented energy saving state. Would not be the first time. If laptop: try to take off the battery and line and press for 30 seconds the interrupter. Try to start in opensuse at once and perform the procedure. If it suddenly works you have an idea. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 1

[opensuse] Leap 15.1 transactional server, temporarily remount volumes rw
by Paul Neuwirth 06 Mar '20

06 Mar '20

Hi, I like that idea/concept with the transactional servers very and I am currently testing it. Especially during setting up everything, it would be a great help to remount the current mounted snapshot with write access, so you could use a package manager with UI, like yast. It leads to many reboots, to find out, there are other packages necessary, etc. The shell command of transactional-update is a big help, but in that chroot environment, many tests cannot be done (complexer software/services, kernel modules, etc etc). So is there any way to get the current system (temporarily) r/w? mount -o rw doesn't work, even the command seems to succeed, but it still says "Read-only file system" on opening a file with write permission. If it is currently not possible, would it be hard (or discussable) to implement? Regards Paul -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

Re: [opensuse] Leap 15.1 - Nvidia Graphics driver = grub2 does not boot anymore - help very appreciated
by Michael Hamilton 05 Mar '20

05 Mar '20

On Monday 24 February 2020, stakanov wrote: > I have the problem of a machine with a broken Grub post Nivida driver update. > This is nothing new that Nvidia is crap, but I find myself in the situation > that I will have to coach over the phone how to repair the grub to a user with > limited knowledge (no way to go down to Italy right now, for obvious reason) > and honestly: never did the procedure and have no idea about it. > > The error message: after booting into the /sda1/gub-efi fat partition the > system stalls with: > Minimal BASH-like line editing is supported. > For the first word, TAB lists possible command completions. > Anywhere else TAB lists possible device or file completions. > > So, what do I have to do and what do I need? Thank you. > > (The user currently should have only a installation DVD. So I suppose - > without knowing it - that this shall be a case for live usb or for a rescue > disc? Else?) > > > > _________________________________________________________________ > ________________________________________________________ > Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de > > > In my notes I saved this message from the past. The suggestion gets the broken root mounted and then suggests using yast to reestablish grub: Re: [opensuse] Boot problem after latest TW dup Date: Today 01:19:10 From: "Knurpht@openSUSE" <knurpht(a)opensuse.org> (opensuse.org) > ... Boot from an install medium, escape to a console by Ctrl-Alt-F2 In the bit below replace sdX# by the /dev/sdX# entry where your root fs is located, f.e. /dev/sda2 Then do: mount /dev/sdX# /mnt mount --bind /dev /mnt/dev mount --bind /proc /mnt/proc mount --bind /sys /mnt/sys chroot /mnt yast This worked for me last time (ext4 rootfs). There might be a simpler way, but it go me up and running. Once bootable, I often resolved nvidia X11 issues by just deinstalling then reinstalling the relevant nvidia driver. Generally I've had no issues with nvidia except when I've switched the hardware and need new drivers. I don't find it to be the cause of many woes (tried Radian once for a short while a decade ago, thought it was worse). Michael -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 15

[opensuse] switched fabric using qla2xxx pci card (fwd)
by Paul Neuwirth 05 Mar '20

05 Mar '20

Hello group, I am trying to evaluate use of fibre channel switched fabric. But I am not able to get it working (openSUSE Leap 15.1). I would appreciate, if anybody knows something or where to find (working) instructions. All instructions I found refer to old/or proprietary drivers/methods (kernel 2.6 or older). I use following hardware: -HP branded (AE312 - 60001) QLogic Corp. ISP2432 4G HBA PCIe -IBM branded (2005-B16) Brocade 200E 16 Port FC switch -DS14MK2 Disk Shelf All of those products are EOS and I am not able to get proprietary drivers or firmware updates. According to switch config everything looks fine, I even put all devices into one zone. According to switch configuration, all the targets should be accessible by the initiators: https://www.swabian.net/extern/opensuse/fcaccessibility.png Having set up following options for qla2xxx module ql2xmaxqdepth=16 qlport_down_retry=10 ql2xloginretrycount=30 ql2xextended_error_logging=1 I get plenty of messages I do not understand, but it contains matching WWPN's of the fabric: [ 1050.235686] qla2xxx [0000:01:00.0]-28d9:2: Async-gnlist WWPN 22:09:00:0a:33:0c:45:d6 [ 1050.235688] qla2xxx [0000:01:00.0]-28da:2: Async-gnlist - OUT WWPN 22:09:00:0a:33:0c:45:d6 hndl 0 [ 1050.235692] qla2xxx [0000:01:00.0]-28d9:2: Async-gnlist WWPN 22:09:00:0a:33:0c:47:4c [ 1050.235693] qla2xxx [0000:01:00.0]-28d9:2: Async-gnlist WWPN 22:09:00:0a:33:0c:46:e5 [ 1050.235694] qla2xxx [0000:01:00.0]-28d9:2: Async-gnlist WWPN 22:0d:00:0a:33:48:14:36 [ 1050.235695] qla2xxx [0000:01:00.0]-28d9:2: Async-gnlist WWPN 22:09:00:0a:33:0c:47:3b [and many more] I uploaded the dmesg output from rmmod && modprobe: https://www.swabian.net/extern/opensuse/fcdmesg.txt some information about used firm/software: HBA (shown on boot): HPAE312A PCI Fibre Channel ROM BIOS Version 3.29 Subsystem Vendor ID 103C Copyright (C) QLogic Corporation 1993-20 Firmware Version 8.01.02 Switch: > version Kernel: 2.4.19 Fabric OS: v5.1.0b Made on: Fri May 26 23:48:35 2006 Flash: Sun Dec 3 12:44:30 2006 BootProm: 4.5.3 Switch > zoneinfo [...] Effective configuration: cfg: testzoning zone: fc_zone1 22:08:00:0a:33:0c:45:b4 22:08:00:0a:33:0c:45:d5 22:08:00:0a:33:0c:45:d6 22:08:00:0a:33:0c:45:dd 22:08:00:0a:33:0c:45:de 22:08:00:0a:33:0c:45:e1 22:08:00:0a:33:0c:46:e2 22:08:00:0a:33:0c:46:e5 22:08:00:0a:33:0c:47:3b 22:08:00:0a:33:0c:47:49 22:08:00:0a:33:0c:47:4c 22:08:00:0a:33:12:62:aa 22:08:00:0a:33:12:64:33 22:08:00:0a:33:12:64:3f 22:0c:00:0a:33:48:14:36 22:0c:00:0a:33:48:14:37 50:01:43:80:04:c5:9e:55 50:01:43:80:04:c5:9e:57 22:0a:00:0a:33:0c:45:d5 22:09:00:0a:33:0c:45:d5 22:0a:00:0a:33:0c:45:b4 22:09:00:0a:33:0c:45:b4 22:09:00:0a:33:0c:45:d6 22:0a:00:0a:33:0c:45:d6 22:09:00:0a:33:0c:45:dd 22:0a:00:0a:33:0c:45:dd 22:0a:00:0a:33:0c:45:de 22:09:00:0a:33:0c:45:de 22:0a:00:0a:33:0c:45:e1 22:09:00:0a:33:0c:45:e1 22:0a:00:0a:33:0c:46:e2 22:09:00:0a:33:0c:46:e2 22:09:00:0a:33:0c:46:e5 22:0a:00:0a:33:0c:46:e5 22:0a:00:0a:33:0c:47:3b 22:09:00:0a:33:0c:47:3b 22:0a:00:0a:33:0c:47:49 22:09:00:0a:33:0c:47:49 22:0a:00:0a:33:0c:47:4c 22:09:00:0a:33:0c:47:4c 22:0a:00:0a:33:12:62:aa 22:09:00:0a:33:12:62:aa 22:09:00:0a:33:12:64:33 22:0a:00:0a:33:12:64:33 22:09:00:0a:33:12:64:3f 22:0a:00:0a:33:12:64:3f 22:0d:00:0a:33:48:14:36 22:0e:00:0a:33:48:14:36 22:0d:00:0a:33:48:14:37 22:0e:00:0a:33:48:14:37 50:01:43:80:04:c5:9e:54 50:01:43:80:04:c5:9e:56 1,16 1,17 1,18 1,19 > switchShow switchName: fcsw1 switchType: 34.0 switchState: Online switchMode: Native switchRole: Principal switchDomain: 1 switchId: fffc01 switchWwn: 10:00:00:05:1e:03:d8:ae zoning: ON (testzoning) switchBeacon: OFF Area Port Media Speed State ============================== 16 0 id N2 Online L-Port 9 public, 7 private 17 1 id N2 Online L-Port 6 public, 10 private 18 2 id N4 Online F-Port 50:01:43:80:04:c5:9e:56 19 3 id N4 Online F-Port 50:01:43:80:04:c5:9e:54 20 4 id N4 No_Light 21 5 id N4 No_Light 22 6 id N4 No_Light 23 7 id N4 No_Light 24 8 id N4 No_Light 25 9 id N4 No_Light 26 10 id N4 No_Light 27 11 id 2G No_Light 28 12 id N4 No_Light 29 13 id N4 No_Light 30 14 id N4 No_Light 31 15 id N4 No_Light Thank you and regards, Paul -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

10 47