users April 2018

users@lists.fedoraproject.org

107 participants
93 discussions

USB issues in fedora-27 ("can't get device qualifier: Resource temporarily unavailable") not happening when booted into CentOS-6.2, same hardware
by Tom Hodder 01 Apr '18

01 Apr '18

Hi All, I've been having a bunch of trouble with the USB ports on my desktop, in particular the webcam doesn't work and there are lots of errors in the output <https://paste.fedoraproject.org/paste/qYxQ2rH-tlsE8pJqWz442w> of *"lsusb -v"* when I try to debug. (I get the "can't get device qualifier: Resource temporarily unavailable" errors, whether the webcam is plugged in or not, which seems to eliminate the webcam itself as the source of the problem) On the positive side, a usb keyboard, mouse and USB sticks seem to work ok. The hardware is a Supermicro SuperWorkstation 7037A-i <https://www.supermicro.com/products/system/tower/7037/sys-7037a-i.cfm>, with an X9dai motherboard <https://www.supermicro.com/products/motherboard/xeon/c600/x9dai.cfm>. I assumed the problem was hardware related and raised a ticket with supermicro. They asked me to test the machine using a supported OS, and the nearest to fedora-27 was CentOS 6.2 (compatibility matrix <https://www.supermicro.com/support/resources/OS/C602_listing2.cfm>). So today I booted into Centos-6.2. To my surprise there were no errors in the "lsusb -v" output <https://paste.fedoraproject.org/paste/yVFlRYGi9m4ZCt9PZPF3Gg>, no errors in dmesg or syslog, and the webcam worked fine. This seems to suggest it's not a hardware problem, but some difference in the drivers. I am pretty sure the usb/webcam used to work, but that's going back a few versions of fedora, and probably 3/4 years. Any ideas on what might be causing this? Many Thanks, Tom Various debugging output; *Fedora-27* lsusb -v https://paste.fedoraproject.org/paste/qYxQ2rH-tlsE8pJqWz442w dmidecode https://paste.fedoraproject.org/paste/gW9D10O0fy6-p58I-YgJOQ dmesg https://paste.fedoraproject.org/paste/hnVj1hyjDpyYtiInxPGZ3Q lsmod https://paste.fedoraproject.org/paste/bZTVW-7P8mD19cLO6nogww *CentOS-6.2* lsusb -v https://paste.fedoraproject.org/paste/yVFlRYGi9m4ZCt9PZPF3Gg dmesg output https://paste.fedoraproject.org/paste/TTyqm9zDrf1m4kID9rl09Q dmidecode https://paste.fedoraproject.org/paste/FfafH1-KdNzy5IA17oD9mg lsmod https://paste.fedoraproject.org/paste/~orePKeYsJRlBRmP1P2vvw Plugging in the webcam produces this; Mar 30 02:19:24 pc03.config kernel: usb 2-1.7: new high-speed USB device number 8 using ehci-pci Mar 30 02:19:25 pc03.config kernel: usb 2-1.7: New USB device found, idVendor=045e, idProduct=0294 Mar 30 02:19:25 pc03.config kernel: usb 2-1.7: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 30 02:19:25 pc03.config kernel: usb 2-1.7: Product: Video Camera Mar 30 02:19:25 pc03.config kernel: usb 2-1.7: Manufacturer: Microsoft Mar 30 02:19:25 pc03.config kernel: usb 2-1.7: SerialNumber: 000F330333475838 Mar 30 02:19:25 pc03.config kernel: uvcvideo: Found UVC 1.00 device Video Camera (045e:0294) Mar 30 02:19:26 pc03.config kernel: uvcvideo 2-1.7:1.0: Entity type for entity Extension 3 was not initialized! Mar 30 02:19:26 pc03.config kernel: uvcvideo 2-1.7:1.0: Entity type for entity Processing 2 was not initialized! Mar 30 02:19:26 pc03.config kernel: uvcvideo 2-1.7:1.0: Entity type for entity Camera 1 was not initialized! ... Mar 30 02:19:19 pc03.config kernel: uvcvideo: Failed to set UVC probe control : -71 (exp. 26). Mar 30 02:19:19 pc03.config kernel: uvcvideo: Failed to set UVC probe control : -71 (exp. 26). Mar 30 02:19:19 pc03.config kernel: uvcvideo: Failed to set UVC probe control : -71 (exp. 26). Mar 30 02:19:19 pc03.config kernel: uvcvideo: Failed to set UVC probe control : -71 (exp. 26).

2 3

easiest way to encrypt existing home dir?
by Neal Becker 01 Apr '18

01 Apr '18

I'm running f27 with everything on one drive. /home is 1 btrfs subvolume and / is another btrfs subvolume. I want to move my /home to encryption. One possibility seems to be to use ecryptfs. I tried creating a test user, and the following: https://cloud-ninja.org/2014/04/05/fedora-encrypting-your-home-directory/ (following "easy way" instructions). This didn't do anything AFAICT, the test user's files still appear to be unencrypted, and I don't see any ecryptfs mount. Any suggestions? Is ecryptfs the way to go here or something else? Thanks, Neal

5 8

rpm says package isn't installed but it is, and related question
by Chris Murphy 31 Mar '18

31 Mar '18

[chris@f27h ~]$ rpm -q kernel-core kernel-core-4.16.0-0.rc6.git2.1.fc29.x86_64 kernel-core-4.15.12-300.fc27.x86_64 kernel-core-4.16.0-0.rc7.git1.1.fc29.x86_64 kernel-core-4.15.14-300.fc27.x86_64 [chris@f27h ~]$ sudo rpm -q -i kernel-core-4.15.14-300.fc27.x86_64.rpm Name : kernel-core Version : 4.15.14 Release : 300.fc27 Architecture: x86_64 Install Date: (not installed) Group : System Environment/Kernel Size : 60650235 License : GPLv2 and Redistributable, no modification permitted Signature : (none) Source RPM : kernel-4.15.14-300.fc27.src.rpm Build Date : Thu 29 Mar 2018 11:02:25 AM MDT Build Host : bkernel02.phx2.fedoraproject.org Relocations : (not relocatable) Packager : Fedora Project Vendor : Fedora Project URL : http://www.kernel.org/ Bug URL : https://bugz.fedoraproject.org/kernel Summary : The Linux kernel Description : The kernel package contains the Linux kernel (vmlinuz), the core of any Linux operating system. The kernel handles the basic functions of the operating system: memory allocation, process allocation, device input and output, etc. [chris@f27h Downloads]$ This specific rpm file I'm getting info on, was installed yesterday. But this query says it's not installed. In fact all RPMs I've downloaded and installed, when -qi is run on them, say they're not installed. Wha wha waht? Also, is there any way to know whether and what kind of compression is used in an RPM? I'm guessing the Size value of 60M above is installed size. The package size is 24M so there must be some kind of compression being used. But 'man rpm | grep -i compress' yields no results. -- Chris Murphy

2 2