June 2020 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Bug in usb drivers? "Not enough bandwidth for new device state"
by Markus Egg 28 Feb '22

28 Feb '22

SuSE Tumbleweed with newest updates and upgrades. 5.7.1-1-default #1 SMP Wed Jun 10 11:53:46 UTC 2020 (6a549f6) x86_64 x86_64 x86_64 GNU/Linux Just recently started to give error messages when plugging in e.g. USB Headsets, Arduino Uno into some Exsys USB 3.0 hub. This was working fine in Tumbleweed before and in e.g. SuSE 13.1. The error message is e.g.: [...]usb 2-1.4.3: new full-speed USB device number 10 using xhci_hcd [...]usb 2-1.4.3: New USB device found, idVendor=2341, idProduct=0043, bcdDevice= 0.01 [...]usb 2-1.4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=220 [...]usb 2-1.4.3: Manufacturer: Arduino (www.arduino.cc) ...serialnumber... [...]kernel: usb 2-1.4.3: Not enough bandwidth for new device state. [...]kernel: usb 2-1.4.3: can't set config #1, error -28 This error message started on Jun 04, after making an update (zypper up) on June 3rd. A USB3.0 stick is working on the Exsys Hub. The Arduino is working on some other USB 3.0 Port of another hub. Regression? Any hints how to get this away? Found only another occurrence of this bug: http://opensuse92.rssing.com/chan-20813128/all_p1407.html Best regards -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 4

[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

Web Site Standards
by Bryan Tyson 25 Sep '21

25 Sep '21

On Wednesday 03 July 2002 03:38, Michael wrote: > I tried to visit this site. > http://www.bet365.com > The result upset me so much i sent them this. I sent the letter below, and I encourage everyone on the list to send a similar letter. ----------------------------------------- Subject: Create a Real Web Site Please From: Bryan S. Tyson <bryantyson(a)earthlink.net> To: webmaster(a)bet365.com When attempting to view your site using Konqueror 2.2.1 and Mozilla 0.9.4, both Linux web browsers, I was curtly informed that my browser is "incompatible." Your site, sir, is what is "incompatible." Stick with established standards and real html, not Microsoft proprietary "features." *************************************************** Powered by SuSE Linux 7.3 Professional KDE 2.2.1 KMail 1.3.1 This is a Microsoft-free computer Bryan S. Tyson bryantyson(a)earthlink.net ***************************************************

10 9

Mount Windows NT(NTFS) drive as drive Z: for all users
by Keith Jacobs 25 Sep '21

25 Sep '21

We have an winNT server and need to auto mount a shared folder as if it were a windose mapped drive Z: on SuSE8 Could someone please explain how to do this and how to make sure it is set-up for every user everytime the system is booted. Thanks Regards Keith Jacobs New to Linux

3 2

[opensuse] libc segfaults attaching an iPad
by Dave Howorth 26 Mar '21

26 Mar '21

I just tried to attach an iPad to my openSUSE 15.0 system, via USB. I think I've done it before, but this time it fails. Dmesg has: [9787970.148053] usb 3-9: new high-speed USB device number 96 using xhci_hcd [9787970.302089] usb 3-9: New USB device found, idVendor=05ac, idProduct=12a2 [9787970.302091] usb 3-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [9787970.302092] usb 3-9: Product: iPad [9787970.302093] usb 3-9: Manufacturer: Apple Inc. [9787970.302094] usb 3-9: SerialNumber: c4088xxxxxserialxredacted [9787971.044264] ipheth 3-9:4.2: Apple iPhone USB Ethernet device attached [9787991.101146] pool[16789]: segfault at 0 ip 00007f6ada593ef1 sp 00007f6ad6203bd8 error 4 in libc-2.26.so[7f6ada43a000+1b1000] Anybody have any idea what the problem is? Thanks, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 7

[opensuse] Raid, Raid6, what file system for good fault tolerance?
by cagsm 21 Dec '20

21 Dec '20

Hi list, speaking about software raid, not hardware controller based. I am trying to go for some local OpenSuse machine and adding some storage to it. Was considering Raid6, and now reading about a bit and people left and right scaremongering about the larger the disks these days in the double digit terabyte capacities even, the more likely it is that during a reconstruction of a raid subsequent errors would occur. I would absolutely like to keep my data consistent, and I am not thinking about double digit terabytes either, would stick to 2TB or 4TB disks, with Raid6 thats at least 4 physical drives. Now I am wondering if it possible to use a good robust file system that can add some more parity or check blocks or redundancy on top of the hardware disks, to absolutely be able to always read my data. I can't add multiple machines or like those high availability stuff like clusters and what not I read about DRBD (Distributed Replicated Block Device), or maybe I am just too scared by those technical terms or consider myself to be just a simpleton and wanting to keep it rather simple. My use case here is also not constant availablity, when a disk needs to be replaced, so be it, but I don't want to lose my data that I can not ever read certain parts of it again or such stuff. The thing that came to my mind was, if there is some file systems that would add redundancy and robustness onto the mdraid system of the linux kernel? Anyone with some useful insights? Roughly speaking, I was considering some simple pcie esata interfaced controller card and an external case enclosure with esata port and portmulitplier stuff inside, that can present at least 4 physical disks as JBOD, just a bunch of disks, so that the Linux can seem them all separately. Speed and rebuild times are not my concern, but data persistence and data integrity. Not even number of physical disks, I could live with even one of those 8 bay device enclosures and cases that are out there on the market. Thanks for any help and hints. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 23

[opensuse] Fw: [Bug 1128204] retext crashes with core dump
by Dave Howorth 15 Nov '20

15 Nov '20

Hmm, I just got this message from Atri, who I've seen looks at this list. I haven't migrated my bugzilla account because I don't want to continue to use the old account name. I just tried to respond and it wants details I cannot supply (I don't know what username/password are - I've never needed them - my browser supposedly knows them but apparently can't reproduce whatever information is required to respond to the 'migration portal') But more fundamentally, I don't use TW. I use Leap and I'm still on 15.0. Begin forwarded message: Date: Sun, 07 Jun 2020 19:16:08 +0000 From: bugzilla_noreply(a)suse.com To: ********* Subject: [Bug 1128204] retext crashes with core dump http://bugzilla.suse.com/show_bug.cgi?id=1128204 http://bugzilla.suse.com/show_bug.cgi?id=1128204#c11 --- Comment #11 from Atri Bhattacharya <badshah400(a)gmail.com> --- Sorry Dave, I missed the train on this one. Can you still reproduce this with the latest TW? -- You are receiving this mail because: You are on the CC list for the bug. You reported the bug. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2

[opensuse] Issue with smartd
by Carlos E. R. 21 Oct '20

21 Oct '20

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have one disk that is giving me problems with the smartd daemon. I get this in the log: <3.6> 2018-10-21T13:45:23.829155+02:00 Isengard smartd 1173 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], state written to /var/lib/smartmontools/smartd.WDC_WD80EZAZ_11TDBA0-2TKST2SD.ata.state <3.6> 2018-10-21T13:45:24.483719+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], opened <3.6> 2018-10-21T13:45:24.484570+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], WDC WD80EZAZ-11TDBA0, S/N:2TKST2SD, WWN:5-000cca-26af51579, FW:83.H0A83, 8.00 TB <3.6> 2018-10-21T13:45:24.503334+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], not found in smartd database. <3.6> 2018-10-21T13:45:24.525071+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], enabled SMART Attribute Autosave. <3.6> 2018-10-21T13:45:24.530486+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], enabled SMART Automatic Offline Testing. <3.6> 2018-10-21T13:45:24.535003+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], is SMART capable. Adding to "monitor" list. <3.6> 2018-10-21T13:45:24.535627+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], state read from /var/lib/smartmontools/smartd.WDC_WD80EZAZ_11TDBA0-2TKST2SD.ata.state <3.6> 2018-10-21T13:45:24.880219+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], state written to /var/lib/smartmontools/smartd.WDC_WD80EZAZ_11TDBA0-2TKST2SD.ata.state <3.6> 2018-10-21T14:15:25.233525+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 147 to 144 <3.6> 2018-10-21T15:45:31.681938+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], not capable of SMART self-check <3.2> 2018-10-21T15:45:33.632399+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], failed to read SMART Attribute Data <3.6> 2018-10-21T16:15:24.678100+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], read SMART Attribute Data worked again, warning condition reset after 1 email <3.6> 2018-10-21T18:15:31.767150+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], not capable of SMART self-check <3.2> 2018-10-21T18:15:33.717688+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], failed to read SMART Attribute Data <3.6> 2018-10-21T18:45:24.587304+02:00 Isengard smartd 11255 - - Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], read SMART Attribute Data worked again, warning condition reset after 1 email It intermitently but periodically fail to read atributes, triggering hundreds of emails sent to me to warn of the problem: +++------------ Subject: SMART error (FailedReadSmartData) detected on host: Isengard This message was generated by the smartd daemon running on: host name: Isengard DNS domain: valinor The following warning/error was logged by the smartd daemon: Device: /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 [SAT], failed to read SMART Attribute Data Device info: WDC WD80EZAZ-11TDBA0, S/N:2TKST2SD, WWN:5-000cca-26af51579, FW:83.H0A83, 8.00 TB For details see host's SYSLOG. You can also use the smartctl utility for further investigation. Another message will be sent in 24 hours if the problem persists. - ------------++- The disk is indeed smart capable and it works fine, as long as I call smartctl with "-d sat,16", which I do: Isengard:~ # smartctl --test=short -d sat,16 /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0\:0 smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.4.155-68-default] (SUSE RPM) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org === START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION === Sending command: "Execute SMART Short self-test routine immediately in off-line mode". Drive command "Execute SMART Short self-test routine immediately in off-line mode" successful. Testing has begun. Please wait 2 minutes for test to complete. Test will complete after Sun Oct 21 13:50:18 2018 Use smartctl -X to abort test. Isengard:~ # Isengard:~ # smartctl --health -d sat,16 /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0\:0 smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.4.155-68-default] (SUSE RPM) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED Isengard:~ # It is crucial to use "-d sat,16" or it fails: Isengard:~ # smartctl --health /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0\:0 smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.4.155-68-default] (SUSE RPM) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0: Unknown USB bridge [0x1058:0x25ee (0x4004)] Please specify device type with the -d option. Use smartctl -h to get a usage summary Isengard:~ # Of course I use that option on the config: Isengard:~ # cat /etc/smartd.conf | egrep -v "^[[:space:]]*$|^#" /dev/sda -a -o on -S on -s (S/../.././02|L/../../6/03) -m root(a)telcontar.valinor /dev/disk/by-id/wwn-0x5000000000000001 -a -o on -S on -s (S/../.././02|L/../../6/03) -m root(a)telcontar.valinor /dev/disk/by-id/wwn-0x5000c5009399305f -a -o on -S on -s (S/../.././02|L/../../6/03) -m root(a)telcontar.valinor /dev/disk/by-id/usb-WD_My_Book_25EE_32544B5354325344-0:0 -d sat,16 -a -o on -S on -s (S/../.././02|L/../../6/03) -m root(a)telcontar.valinor Isengard:~ # What else am I missing? Is smartd not using "-d sat,16" somewhere else? Is it some other problem? Isengard:~ # rpm -q smartmontools smartmontools-6.6-135.1.x86_64 Isengard:~ # - -- Cheers Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlvM5UMACgkQtTMYHG2NR9WCwQCePjOt8PSMKsx6DwSe9bZJRhHf 2lQAn02eBTrtfAqmEg5ydZVagvMfW2r6 =eIzR -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 7

[opensuse] OpenSUSE: simplest way to do a version upgrade
by Darryl Gregorash 27 Jul '20

27 Jul '20

Can a version upgrade be done entirely within YaST? Specifically: 1. amend all repositories from 15.1 to 15.2 2. use Online Update to do a "force update all" Also, can this be done from within a graphical session from a user account, should it be done when logged in as root, or should it be done strictly from a command line, but not logged into a graphical session? (Hopefully I've worded that so as not to be overly confusing ;) ) -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 32

[opensuse] Lacking a bootable partition?
by Michael Fischer 01 Jul '20

01 Jul '20

Hello all (and hopefully Andrei), While reading the recent thread (... Zypper dup renders 15.1 to 15.2...) I got curious about my own system - which had a reinstall (15.0) a few months ago, which went...poorly. It took several installs and boot attempts to get the thing to come up (which is really odd because it was a reinstall of 15.0 on top of the same 15.0 on seemingly perfectly good hardware) Now I see that perhaps my /boot/efi is not configured correctly? bootinfoscript doesn't even find/describe the disk where /boot/efi lives, (/dev/nvme0n1) for some reason. The guts of my system is $ df -h Filesystem Size Used Avail Use% Mounted on /dev/nvme0n1p2 233G 9.3G 212G 5% / /dev/nvme0n1p1 500M 5.1M 495M 2% /boot/efi /dev/sdb1 458G 97G 338G 23% /home There are a few data/backup/etc. disks attached, I ignore these for simplicity $ blkid /dev/nvme0n1* /dev/nvme0n1: PTUUID="c2d48243-da0e-456d-bd55-d3bee176dbec" PTTYPE="gpt" /dev/nvme0n1p1: SEC_TYPE="msdos" UUID="5591-235C" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="f95c0606-ecaa-44af-8fd0-51f9980f26a9" /dev/nvme0n1p2: UUID="65da4abd-8d32-4a12-a6d3-5f237343714d" TYPE="ext4" PARTLABEL="primary" PARTUUID="0c505856-c975-4f34-9119-7a9e70d78b2c" $ sudo fdisk -l /dev/nvme0n1* Disk /dev/nvme0n1: 238.5 GiB, 256060514304 bytes, 500118192 sectors 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: C2D48243-DA0E-456D-BD55-D3BEE176DBEC Device Start End Sectors Size Type /dev/nvme0n1p1 2048 1026047 1024000 500M Microsoft basic data /dev/nvme0n1p2 3147776 500117503 496969728 237G Linux filesystem Disk /dev/nvme0n1p1: 500 MiB, 524288000 bytes, 1024000 sectors 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: dos Disk identifier: 0x00000000 Disk /dev/nvme0n1p2: 237 GiB, 254448500736 bytes, 496969728 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes $ ls -al /boot/efi/EFI/opensuse/ total 3600 drwxr-xr-x 3 root root 8192 Feb 14 16:29 . drwxr-xr-x 4 root root 8192 Feb 14 11:07 .. -rwxr-xr-x 1 root root 58 Feb 14 11:07 boot.csv drwxr-xr-x 2 root root 8192 Feb 14 16:29 fw -rwxr-xr-x 1 root root 70464 Feb 14 16:29 fwupx64.efi -rwxr-xr-x 1 root root 155 Feb 14 11:07 grub.cfg -rwxr-xr-x 1 root root 1060704 Feb 14 11:07 grub.efi -rwxr-xr-x 1 root root 123904 Feb 14 11:07 grubx64.efi -rwxr-xr-x 1 root root 1158688 Feb 14 11:07 MokManager.efi -rwxr-xr-x 1 root root 1208968 Feb 14 11:07 shim.efi (that `fw` directory is empty) For comparison, a simple one-disk system I have (also on 15.0) which "makes sense" > sudo blkid /dev/sda1: LABEL="ESP" UUID="4A08-2713" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="bd98a04b-2b82-4a57-9652-75c0189aaf2a" /dev/sda2: UUID="b34af9ea-c375-4b96-9adb-5fc88bcdf2f1" TYPE="swap" PARTUUID="be766a1e-c3de-4283-b18d-0fa489b74b1f" /dev/sda3: UUID="7716718f-9d03-470a-8a21-11e2aba10247" TYPE="ext4" PARTUUID="45b0ca46-3e31-4dbe-8475-bfb53ecb119c" > sudo fdisk -l /dev/sda [sudo] password for root: Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors 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: 2E601350-1A64-4CD5-9D45-A9E7BB0C428F Device Start End Sectors Size Type /dev/sda1 2048 1333247 1331200 650M EFI System /dev/sda2 1333248 5527551 4194304 2G Linux swap /dev/sda3 5527552 1953525134 1947997583 928.9G Linux filesystem > ls -al /boot/efi/EFI/opensuse/ total 3492 drwxr-xr-x 2 root root 4096 Dec 3 2018 . drwxr-xr-x 6 root root 4096 Dec 3 2018 .. -rwxr-xr-x 1 root root 58 Dec 3 2018 boot.csv -rwxr-xr-x 1 root root 155 Dec 3 2018 grub.cfg -rwxr-xr-x 1 root root 1060704 Dec 3 2018 grub.efi -rwxr-xr-x 1 root root 123904 Dec 3 2018 grubx64.efi -rwxr-xr-x 1 root root 1158688 Dec 3 2018 MokManager.efi -rwxr-xr-x 1 root root 1208968 Dec 3 2018 shim.efi I note that the md5sums of the files in the two machines /boot/efi/EFI/opensuse are all different (not sure if that means anything or not). So, is this a case of "boot from rescue disk and run various grub commands to re-write /boot/efi and all should be well" or ...? Many thanks from a man afraid to reboot his main computer. Michael -- Michael Fischer michael(a)visv.net -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 25