Re: What was that?
> However, neither the keyboard or mouse were functioning.
> I unplugged the wireless dongles for both of them and
> plugged them back in, and now the mouse works, but the
> keyboard still doesn't work.
I've been seeing stuff like this in the syslog from recent kernels:
Sep 30 08:59:34 dorotea kernel: usb 1-3: new full-speed USB device
number 3 using xhci_hcd
Sep 30 08:59:34 dorotea kernel: usb 1-3: New USB device found,
idVendor=046d, idProduct=c52b, bcdDevice=12.09
Sep 30 08:59:34 dorotea kernel: usb 1-3: New USB device strings:
Mfr=1, Product=2, SerialNumber=0
Sep 30 08:59:34 dorotea kernel: usb 1-3: Product: USB Receiver
Sep 30 08:59:34 dorotea kernel: usb 1-3: Manufacturer: Logitech
Sep 30 08:59:34 dorotea kernel: input: Logitech USB Receiver as
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/0003:046D:C52B.0001/input/input18
Sep 30 08:59:34 dorotea kernel: hid-generic 0003:046D:C52B.0001:
input,hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on
usb-:00:14.0-3/input0
Sep 30 08:59:34 dorotea kernel: input: Logitech USB Receiver Mouse as
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.1/0003:046D:C52B.0002/input/input19
Sep 30 08:59:34 dorotea kernel: input: Logitech USB Receiver Consumer
Control as
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.1/0003:046D:C52B.0002/input/input20
Sep 30 08:59:34 dorotea kernel: input: Logitech USB Receiver System
Control as
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.1/0003:046D:C52B.0002/input/input21
Sep 30 08:59:34 dorotea kernel: hid-generic 0003:046D:C52B.0002:
input,hiddev96,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on
usb-:00:14.0-3/input1
Sep 30 08:59:34 dorotea kernel: hid-generic 0003:046D:C52B.0003:
hiddev97,hidraw2: USB HID v1.11 Device [Logitech USB Receiver] on
usb-:00:14.0-3/input2
Sep 30 08:59:34 dorotea kernel: usb 1-3: USB disconnect, device number 3
Sep 30 08:59:34 dorotea mtp-probe[1544]: checking bus 1, device 3:
"/sys/devices/pci:00/:00:14.0/usb1/1-3"
Sep 30 08:59:39 dorotea kernel: usb 1-3: new full-speed USB device
number 4 using xhci_hcd
Sep 30 08:59:39 dorotea kernel: usb 1-3: New USB device found,
idVendor=046d, idProduct=c52b, bcdDevice=12.09
Sep 30 08:59:39 dorotea kernel: usb 1-3: New USB device strings:
Mfr=1, Product=2, SerialNumber=0
Sep 30 08:59:39 dorotea kernel: usb 1-3: Product: USB Receiver
Sep 30 08:59:39 dorotea kernel: usb 1-3: Manufacturer: Logitech
The device is recognized, then something called mtp-probe comes along
and blows it out of the water. The cycle repeats until either
mtp-probe gives up and lets the device work, or the device itself
gives up:
Sep 30 09:00:10 dorotea kernel: usb 1-3: Device not responding to setup address.
A workaround (found on the interwebs) is to add a udev rule in, say,
/etc/udev/rules.d/99-mtp-no-probe.rules:
ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c52b", ENV{MTP_NO_PROBE}="1"
Now there are messages like this:
Oct 2 10:18:09 dorotea mtp-probe[973]: checking bus 1, device 3:
"/sys/devices/pci:00/:00:14.0/usb1/1-5"
Oct 2 10:18:09 dorotea mtp-probe[973]: bus: 1, device: 3 was not an MTP device
But so far nothing bad has happened.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Background when wakeuo from suspend
Hi all, running F32 with MATE desktop I had a nice background when the laptop wakes up from suspend. Suddenly this background has changed. I don't like it and want the old Background back. How/where to set this background image? I didn't find a solution in all MATE settings. Greetings, Frank ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Background when wakeuo from suspend
On 10/2/20 8:44 AM, Frank Elsner via users wrote: running F32 with MATE desktop I had a nice background when the laptop wakes up from suspend. Suddenly this background has changed. I don't like it and want the old Background back. How/where to set this background image? I didn't find a solution in all MATE settings. Possibly the lock screen background? I was about to say that Gnome lets you set that background separately from the desktop background, but when I went to check, that option has completely disappeared. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Resizing LVM on VPS machine
Hi, I have a fedora32 install that was created by our VPS provider and they didn't allocate the entire 480GB SSD, but apparently just chose the default partitioning in fedora that only uses a 15GB root partition. How do I extend this partition to utilize the rest of the space on / or create a /home partition that utilizes the remainder of the space? I believe to resize the root partition I would need to do it outside of the running OS, correct? I've read several docs already, but I really must be missing something. Can xfs partitions even be resized? I've tried to use lvextend to resize root, but I don't understand the proper syntax according to this doc: https://opensource.com/business/16/9/linux-users-guide-lvm Below is the fdisk output for the partition info and the fstab below. # fdisk -l Disk /dev/sda: 480 GiB, 515396075520 bytes, 1006632960 sectors Disk model: QEMU HARDDISK 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: 0x9325d531 Device Boot StartEndSectors Size Id Type /dev/sda1 * 2048209919920971521G 83 Linux /dev/sda2 2099200 1006632959 1004533760 479G 8e Linux LVM Disk /dev/mapper/fedora_209--216--100--114-root: 15 GiB, 16106127360 bytes, 31457280 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 Disk /dev/mapper/fedora_209--216--100--114-swap: 8.66 GiB, 9281994752 bytes, 18128896 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 /dev/mapper/fedora_209--216--100--114-root / xfs defaults0 0 UUID=49e1a837-e82a-4ae0-8979-94ccd7365394 /boot xfs defaults0 0 /dev/mapper/fedora_209--216--100--114-swap none swapdefaults0 0 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Resizing LVM on VPS machine
type "pvs" and see how big the /dev/sda2 pv is. It appears to be all of the disk right now. /dev/sda1 and /dev/sda2 are partitions. the rest are lv's inside a vg on the //dev/sda2(pv) in lvm. That would mean that you need lvresize current ones and/or lvcreate new new lv's to create fses on. Find a lvm tutorial document and it should explain it. The basics are pv are physical volumes on a disk device, vg are volume groups (with one or more pv in the vg), and lv are logical volumes and 1 or more of them exist in inside a vg. Note that xfs_growfs will grow the filesystem, but you cannot shrink a xfs filesysteem without doing the create new copy the data and delete old (and have 2x the space around). installing it like they did allows you to choose how you use the rest (enlarge / or create new lv's with their own fs'es). On Fri, Oct 2, 2020 at 5:14 PM Alex wrote: > > Hi, > > I have a fedora32 install that was created by our VPS provider and > they didn't allocate the entire 480GB SSD, but apparently just chose > the default partitioning in fedora that only uses a 15GB root > partition. > > How do I extend this partition to utilize the rest of the space on / > or create a /home partition that utilizes the remainder of the space? > I believe to resize the root partition I would need to do it outside > of the running OS, correct? > > I've read several docs already, but I really must be missing > something. Can xfs partitions even be resized? I've tried to use > lvextend to resize root, but I don't understand the proper syntax > according to this doc: > https://opensource.com/business/16/9/linux-users-guide-lvm > > Below is the fdisk output for the partition info and the fstab below. > > # fdisk -l > Disk /dev/sda: 480 GiB, 515396075520 bytes, 1006632960 sectors > Disk model: QEMU HARDDISK > 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: 0x9325d531 > > Device Boot StartEndSectors Size Id Type > /dev/sda1 * 2048209919920971521G 83 Linux > /dev/sda2 2099200 1006632959 1004533760 479G 8e Linux LVM > > Disk /dev/mapper/fedora_209--216--100--114-root: 15 GiB, 16106127360 > bytes, 31457280 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 > > Disk /dev/mapper/fedora_209--216--100--114-swap: 8.66 GiB, 9281994752 > bytes, 18128896 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 > > /dev/mapper/fedora_209--216--100--114-root / xfs > defaults0 0 > UUID=49e1a837-e82a-4ae0-8979-94ccd7365394 /boot xfs >defaults0 0 > /dev/mapper/fedora_209--216--100--114-swap none > swapdefaults0 0 > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
