wlr-randr doesn't seem to see my screens connected to my dock, if it's connected after logging in.
Linux
A community for everything relating to the linux operating system
Also check out [email protected]
Original icon base courtesy of [email protected] and The GIMP
Hmm. You should probably report that on their issue tracker, perhaps that's a bug they didn't catch (yet), https://todo.sr.ht/~emersion/wlr-randr
I have four identical machines. Each with the following set of disks:
2x NVMe
2x 2.5" SSD
4x 3.5" HDD in hardware RAID6
now, the device nodes for the SSDs and the RAID seems random. These populate /dev/sda through sdc, but which is which varies between the machines.
Is it possible to somehow reassign the device nodes so that I have the RAID show up as sdc on all machines?
How about using labels in etc-fstab ? That should be all you really need to be able to refer to disks in a cohesive fashion between nodes.
@[email protected] is correct, it's the order you connected them in (see tldp). Use UUIDs or devices lables for consistency or connect them in the order you want.
AFAIK the a-b-c enumeration comes from hardware, so for example whichever sata port you use in a motherboard would always get the same identifier. You'd need to turn off all four nodes and check the disks are indeed connected in exactly the same ports. If that fails, then I'd assume the motherboards are from different batched or soldered differently for whatever reasons.
Gnome says that, it will turn on osk and screen rotation automatically when in tablet mode, but that doesn't work in my laptop. Is there anything I can do to fix this?
Does your laptop include the hardware sensors to detect its positioning? Tablets have that, it's not only software (and firmware?)
It has all the hardware for a convertible laptop. Right now, I am using an auto-rotate gnome extension, and it works, but for some reason gnome doesn't recognize when I flip my laptop to go into tablet mode. Although my firmware recognize it properly, seeing as they turn off keyboard light automatically. So my guess is, the problem is on Gnome's side.