October 2019 - openSUSE Users - openSUSE Mailing Lists

[opensuse] smartctl usage & GSmartControl
by Dave Howorth 22 Oct '19

22 Oct '19

Prompted by recent discussions about SSD vs HDD I decided to check out my devices with smartctl. But I'm overwhelmed by the smartctl man page! My main disk - sda - is reported to be fine :) My backup disk - sdb - is not found # smartctl -P show /dev/sdb smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.12.14-lp150.12.7-default] (SUSE RPM) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org /dev/sdb: Unknown USB bridge [0x4971:0xce23 (0x000)] Please specify device type with the -d option. Use smartctl -h to get a usage summary So I tried telling it that the disk is SATA and with that it can find it: # smartctl -P show -d sat /dev/sdb smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.12.14-lp150.12.7-default] (SUSE RPM) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org Drive found in smartmontools Database. Drive identity strings: MODEL: Hitachi HDS721010CLA332 FIRMWARE: JP4OA3EA match smartmontools Drive Database entry: MODEL REGEXP: (Hitachi )?HDS7210((16|25)CLA[36]82|(32|50)CLA[36]62|(64|75|10)CLA[36]3[02]) FIRMWARE REGEXP: .* MODEL FAMILY: Hitachi Deskstar 7K1000.C ATTRIBUTE OPTIONS: None preset; no -v options are required. but how do I get it to actually scan it regularly like my main disk? I installed GSmartControl in the hope it would be simpler to use. But the Help/Help button does nothing, and for my backup disk it says: Drive information: /dev/sdb (scsi), 1.00 TB, HDS721010CLA332 Basic health check: Unknown Model family: Unknown and the checkboxes to Enable SMART and to Enable Offline Data Collection are both greyed out. So how come it doesn't seem to be able to access the same data as smartctl? Does anybody use it, or is it really as useless as it seems? YaST Partitioner can see it without me having to do anything special, why can't smart? Similar questions also apply to an SD card I happen to have plugged in at the moment! -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2

[opensuse] Tumbleweed boot difficulty
by Roger Oberholtzer 22 Oct '19

22 Oct '19

I have done a new Tumbleweed install. All went fine. But booting is a problem. I need to run the original installer + update to get it to boot. Then, after doing the update (basically installing any new packages), it boots in to the OS fine. But on it's own, I get the graphic boot menu. Then a black window that lists the name of the kernel, and the name if the initrd file. Then ... nothing. No complaint. It just waits. No keys can do anything (e.g., an alternative console) When it boots, it is working fine, I can do most everything I have tried. I see that /proc/cmdline says: BOOT_IMAGE=/boot/vmlinuz-5.3.2-1-default root=UUID=02e67b6d-c8b5-4de1-8ac5-96a13174a855 splash=silent resume=/dev/disk/by-id/ata-WDC_WD10EARS-003BB1_WD-WCAV5J249635-part3 quiet splash=silent resume=/dev/disk/by-id/ata-WDC_WD10EARS-003BB1_WD-WCAV5J249635-part3 quiet mitigations=off The devices and UUID look correct. I'm just curious why the resume= and quite are listed twice. Could that be the problem? I know that the kernel was updated in all of this. The dracut is whatever the kernel packages does. I have not changed anything. I have tried various boot alternatives (rescue, a snapshot, etc). All do the same. This is a new one on me. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 18

[opensuse] Help Reading Serial Device /dev/bus/usb/001/010
by David C. Rankin 22 Oct '19

22 Oct '19

All, I have a small ARM board that I am working with: http://processors.wiki.ti.com/index.php/LAUNCHXL2-RM46 I can build for the board using gcc-arm-none-eabi and flash the firmware with the TI UniFlash software. However I cannot figure out how to connect a serial device to it. The manual says I should be able to: Configure Baud Rate: 19200, Data Bits: 8, Stop Bits: 2 and Parity: None http://processors.wiki.ti.com/index.php/LAUNCHXL2_RM46:_Project_1 When connected there are two /dev/tty devices created: crw-rw-rw- 1 root dialout 166, 0 Oct 12 21:55 /dev/ttyACM0 crw-rw-rw- 1 root dialout 166, 1 Oct 12 21:55 /dev/ttyACM1 These are in some manner related to: /sys/devices/pci0000\:00/0000\:00\:1c.7/0000\:26\:00.0/usb1/1-1 and the character device /dev/char/189:9 I have tried minicom through /dev/ttyACM0, without success. I can find the device and query it through: # udevadm test /sys/devices/pci0000\:00/0000\:00\:1c.7/0000\:26\:00.0/usb1/1-1 calling: test version 228 This program is for debugging only, it does not run any program specified by a RUN key. It may show incorrect results, because some values may be different, or not available at a simulation run. === trie on-disk === tool version: 228 file size: 7007575 bytes header size 80 bytes strings 1743863 bytes nodes 5263632 bytes Load module index <snip> starting '/usr/lib/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1c.7/0000:26:00.0/usb1/1-1 1 10' '/usr/lib/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1c.7/0000:26:00.0/usb1/1-1 1 10'(out) '0' Process '/usr/lib/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1c.7/0000:26:00.0/usb1/1-1 1 10' succeeded. MODE 0666 /etc/udev/rules.d/71-ti-permissions.rules:10 handling device node '/dev/bus/usb/001/010', devnum=c189:9, mode=0666, uid=0, gid=0 preserve permissions /dev/bus/usb/001/010, 020666, uid=0, gid=0 preserve already existing symlink '/dev/char/189:9' to '../bus/usb/001/010' created db file '/run/udev/data/c189:9' for '/devices/pci0000:00/0000:00:1c.7/0000:26:00.0/usb1/1-1' ACTION=add BUSNUM=001 DEVNAME=/dev/bus/usb/001/010 DEVNUM=010 DEVPATH=/devices/pci0000:00/0000:00:1c.7/0000:26:00.0/usb1/1-1 DEVTYPE=usb_device DRIVER=usb ID_BUS=usb ID_MODEL=XDS110__03.00.00.02__Embed_with_CMSIS-DAP ID_MODEL_ENC=XDS110\x20\x2803.00.00.02\x29\x20Embed\x20with\x20CMSIS-DAP ID_MODEL_ID=bef3 ID_REVISION=0100 ID_SERIAL=Texas_Instruments_XDS110__03.00.00.02__Embed_with_CMSIS-DAP_HLR46000 ID_SERIAL_SHORT=HLR46000 ID_USB_INTERFACES=:020201:0a0000:ff0000:030000: ID_VENDOR=Texas_Instruments ID_VENDOR_ENC=Texas\x20Instruments ID_VENDOR_FROM_DATABASE=Texas Instruments, Inc. ID_VENDOR_ID=0451 MAJOR=189 MINOR=9 PRODUCT=451/bef3/100 SUBSYSTEM=usb TYPE=239/2/1 USEC_INITIALIZED=120561513447 run: '/usr/lib/virtualbox/VBoxCreateUSBNode.sh 189 9 ef' Unload module index Unloaded link configuration context. This is the correct udev rule for the device, but that is where I am stuck. What I need to do is get a serial console open to it so that when I load an executable that reads/writes to stdin/stdout I can see the output and provide the input. (blinking diodes are the board are nice, but worthless for providing user authentication through) Connecting a serial console seems like a simple process, but I must be missing something stupid simple about it. Minicom can be configured for either /dev/ttyACM0 or /dev/ttyACM1 (and N82 19200) but there is nothing ever output on either (even after loading a program that generates output to stdout) Yes, the flash goes fine and I can load different executables to make the diodes respond in varying ways -- so the fact that the code is loaded and running correctly if verified, but how do I interface with the serial terminal on this thing? Anybody been down this road before? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 9

[opensuse] restoring efi boot / home after failed SSD
by gumb 20 Oct '19

20 Oct '19

I recently suffered a cataclysmic SSD failure. This machine has two SSD drives, the M.2 drive (sdb) holds the root partition (sdb1) and swap, which is all still intact, whilst the SATA drive which failed (sda) held the boot/efi partition in addition to the /home partition, and hence all my personal data. I've installed a new replacement SATA SSD, booted the openSUSE rescue system from a USB stick, changed root to the original oS installation on sdb1 and then, from within yast2, created a new /boot/efi partition (sda1) and /home (sda2) on the new disk. What is the next step to get this to boot? Currently I'm at the error: no such device: /efi/boot/fallback.efi -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] SSH Public Key Authentication Broken By Upgrade [zypper dup]
by Adam Tauno Williams 19 Oct '19

19 Oct '19

After doing a zypper dup to 15.1 all appears to be working great - as expected - except however for SSH public key authentication. GNOME does not prompt for the passphrase and authentication falls back to password mode [assuming the server allows it]. Tips / pointers? __agent is running, correctly linked in environment__ awilliam@beast01:~> ps ax | grep key ... 7245 ? S 0:00 /usr/bin/ssh-agent -D -a /run/user/1000/keyring/.ssh awilliam@beast01:~> ls -l /run/user/1000/keyring/.ssh srw------- 1 awilliam users 0 Oct 17 08:39 /run/user/1000/keyring/.ssh awilliam@beast01:~> env | grep SSH SSH_AUTH_SOCK=/run/user/1000/keyring/ssh SSH_ASKPASS=/usr/lib/ssh/ssh-askpass SSH_AGENT_PID=3113 __OS Relase__ awilliam@beast01:/etc> cat os-release NAME="openSUSE Leap" VERSION="15.1 " ID="opensuse-leap" ID_LIKE="suse opensuse" VERSION_ID="15.1" PRETTY_NAME="openSUSE Leap 15.1" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:leap:15.1" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" __agent knows the keys__ awilliam@beast01:/etc> ssh-add -l 1024 SHA256:Mom8WjkrR5gYjlRXsH4ROtA7HcsvC0UI/2c+BFsEp0U ogo(a)workflow.mormail.com (DSA) 1024 SHA256:xVXJ4TscK0z/lZRf6t6n/9yt3G9sIxy46bmGd2RDCr4 awilliam(a)linux-yu4c.site (DSA) 1024 SHA256:ZNRZeqkdHCI266I72nNCOiwagJ85XLScOkmEtwYIilk awilliam(a)linux-86wr.site (DSA) __entering the passphrase 'works' but is not effective__ awilliam@beast01:/etc> ssh-add Enter passphrase for /home/awilliam/.ssh/id_dsa: Identity added: /home/awilliam/.ssh/id_dsa (/home/awilliam/.ssh/id_dsa) __gcr-ssh-askpass is installed__ awilliam@beast01:~> ls -l /usr/lib/gcr-ssh-askpass -rwxr-xr-x 1 root root 43920 Feb 24 2019 /usr/lib/gcr-ssh-askpass awilliam@beast01:~> rpm -qf /usr/lib/gcr-ssh-askpass gcr-ssh-askpass-3.28.1-lp151.1.1.x86_64 -- Adam Tauno Williams <mailto:awilliam@whitemice.org> GPG D95ED383 OpenGroupware Developer <http://www.opengroupware.us/> -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 10

[opensuse] SegFault 7-times today just to retrieve packages during Zypper Up (no fix yet?)
by David C. Rankin 19 Oct '19

19 Oct '19

All, This is bizarre. Today on Leap 15, I went to zypper up and it SegFaulted 7 times before it finally downloaded all packages. It would download 3-4 packages, then segfault. This was apparently already reported as a bug several weeks ago. Is a fix or workaround out? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2

[opensuse] Run script when a program ends
by Istvan Gabor 17 Oct '19

17 Oct '19

Hello: I have a program which saves data in a file. It writes the file when the user quits the program. I would like to automatically save a copy of the data file when/after the program quits. How can I achieve that? I could write a script that makes a copy of the file, but don't know how to start the script when the program quits. Any idea or solution is welcomed. Thanks in advance, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 12

[opensuse] urgent help needed: Leap 15.1, firewalld, router not forwarding IPv6
by Mathias Homann 15 Oct '19

15 Oct '19

Hi, I just upgraded my firewall/router from 15.0 to 15.1 with zypper, and now it's not forwarding IPv6 anymore. I have not changed anything about the firewall settings (internal interface is in trusted, external in external, masquerade is on in external), before the upgrade I could talk IPv6 from any internal host just fine, now i can't. I can talk IPv6 from the router itself, but not from any machines behind it. Any ideas? Cheers *Mathias Homann* Mathias.Homann@openSUSE:.org[1] irc: [Lemmy] @ freenode, ircnet obs: lemmy04 *gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102* -------- [1] mailto:Mathias.Homann@eregion.de

3 4

[opensuse] sig 7 bus error
by David T-G 14 Oct '19

14 Oct '19

Hi again, all -- This time I do have a real problem. I shut down my laptop davidtg@wench:~> uname -a ; cat /etc/os-release Linux wench 4.4.140-62-default #1 SMP Tue Jul 17 12:14:34 UTC 2018 (951943d) x86_64 x86_64 x86_64 GNU/Linux NAME="openSUSE Leap" VERSION="42.3" ID=opensuse ID_LIKE="suse" VERSION_ID="42.3" PRETTY_NAME="openSUSE Leap 42.3" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:leap:42.3" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" to bring it home, and when I brought it back up I suddenly couldn't run Chrome (Chromium); it pops up its window but then immediately dies. Here's what it throws: davidtg@wench:~> /usr/bin/chromium --disable-gpu --user-data-dir=/mnt/data/home/davidtg/.chromium/profiles/gift [5387:5387:1004/222017.561228:ERROR:gpu_process_transport_factory.cc(1016)] Lost UI shared context. libva info: VA-API version 0.39.4 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib64/dri/i965_drv_video.so libva info: va_openDriver() returns -1 [5471:5471:1004/222017.875318:ERROR:vaapi_wrapper.cc(323)] vaInitialize failed: unknown libva error Received signal 7 BUS_ADRERR 7f4faef5c1bc #0 0x556ce6714fae <unknown> #1 0x556ce41f78a0 <unknown> #2 0x556ce6715367 <unknown> #3 0x7f4fc5203c10 <unknown> #4 0x556ce6a23f9a <unknown> #5 0x556ce6a2423c <unknown> #6 0x556ce6a1eb51 <unknown> #7 0x556ce6a1ed17 <unknown> #8 0x556ce6a1f6da <unknown> #9 0x556ce69e2275 <unknown> #10 0x556ce67846ec <unknown> #11 0x556ce6784859 <unknown> #12 0x556ce6785423 <unknown> #13 0x556ce7d28569 <unknown> #14 0x556ce7d419d0 <unknown> #15 0x556ce7d41f6c <unknown> #16 0x556ce9b89991 <unknown> #17 0x556ce668e448 <unknown> #18 0x556ce66e5afd <unknown> #19 0x556ce6721ff2 <unknown> #20 0x556ce66e769e <unknown> #21 0x556ce67373a4 <unknown> #22 0x556ce6737904 <unknown> #23 0x556ce6722621 <unknown> #24 0x7f4fc51fb724 start_thread #25 0x7f4fbc645e8d __clone r8: 00007f4f9269ccc8 r9: 0000556ceb968721 r10: 0000556ce6a231f0 r11: 0000000000000014 r12: 000008e930b9c928 r13: 00007f4f9269cd80 r14: 00007f4f9269cec4 r15: 0000556ceb90ef38 di: 000008e930b9c928 si: 0000000000000002 bp: 00007f4f9269ccb0 bx: 000008e930b9c928 dx: 00007f4faef5a600 ax: 00007f4faef5c1bc cx: 0000556ceb968721 sp: 00007f4f9269cc50 ip: 0000556ce6a23f9a efl: 0000000000010202 cgf: 0000000000000033 erf: 0000000000000004 trp: 000000000000000e msk: 0000000000000000 cr2: 00007f4faef5c1bc [end of stack trace] Calling _exit(1). Core file will not be generated. Firefox gives me a much shorter error with similar disappearing-window results: davidtg@wench:~> /usr/bin/firefox -p gift ExceptionHandler::GenerateDump cloned child 6233 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... Bus error (core dumped) I've actually bounced the box a few times with no better luck. I know that I tried something else that failed, but I don't recall just what it was. Dolphin works, though, and shotcut will view a video file, so it isn't simply all graphics stuff. Um, what did I miss here?!? TIA & HANN :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 11

[opensuse] close lid => suspend => can't boot
by David T-G 14 Oct '19

14 Oct '19

Hi, all -- This stupid laptop really has me ticked off this morning. I took it from the desk to bed where I'm home for a sick day (yes, my patience is already thin!) and found, much to my surprise, that it suddenly goes to sleep when I close the lid. ?!? Well, fine; I just won't close the lid when I put it back later, right? But I opeend it and it failed to resume, so I had to power-cycle it ... and it still won't boot! ARRRRRGH!!! Whether I try a normal boot or recovery mode, I only get as far as [ 5.214975] radeon 0000:01:00.0: failed VCE resume (-110). after a few very brief flashes of boot scroll that I can't catch. I went googling around for how to disable the sleep thing, but if I can't get it running again then that part is moot. Any idea how I can get this unstuck? TIA again :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 1