https://wiki.archlinux.org/api.php?action=feedcontributions&user=Kolo&feedformat=atomArchWiki - User contributions [en]2024-03-28T15:57:16ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Talk:EFI_system_partition&diff=617632Talk:EFI system partition2020-06-01T13:26:00Z<p>Kolo: /* Some firmware requires esp/EFI/BOOT/BOOTX64.EFI path */ new section</p>
<hr />
<div>== You must use the root= kernel parameter in order to boot using this method ==<br />
<br />
The sentence "You ''must'' use the {{ic|1=root=}} [[Kernel parameters#Parameter list|kernel parameter]] in order to boot using this method" from [[EFI system partition#Using bind mount]] has been bugging me for while now. I traced its origins to [[Special:Diff/277007]].<br />
<br />
Are there situations where it's possible to omit the {{ic|1=root=}} parameter (not counting [[REFInd#Without configuration|boot loader magic]] since it also passes the parameter to the kernel)?<br />
<br />
-- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 08:50, 20 April 2019 (UTC)<br />
<br />
:Technically its possible if you get systemd-auto-gpt-generator run in initramfs or you hard coded it in a custom kernel or initramfs. Of course this is unsupported.<br />
:[[User:Marcthe12|Marcthe12]] ([[User talk:Marcthe12|talk]]) 05:42, 12 November 2019 (UTC)<br />
<br />
::Although the wiki was updated after [https://github.com/systemd/systemd/commit/1a14a53cfded6e78c6e8dfb73fdff0039971d642#diff-c6c5ce1bf5c4c31d86955bf2cb8e94a9 systemd-auto-gpt-generator came into existence], I don't think it's referencing that. I have a slight suspicion that it could be about grub-mkconfig not liking a bind mounted {{ic|/boot}}. I'll test it when I get the time. -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 15:41, 12 November 2019 (UTC)<br />
<br />
== Some firmware requires esp/EFI/BOOT/BOOTX64.EFI path ==<br />
<br />
Had an issue with "no bootable image found" on an HP Elitebook. It appears that someone else had a similar problem here:<br />
<br />
https://forums.opensuse.org/showthread.php/493175-Issues-with-booting-GPT-and-UEFI/page4<br />
<br />
The solution is to change the path from, e.g. esp/EFI/arch_grub/grubx64.efi to esp/EFI/BOOT/BOOTX64.EFI (simply by copying the efi file).<br />
<br />
Is this worth adding to the Troubleshooting section?</div>Kolohttps://wiki.archlinux.org/index.php?title=Talk:TrackPoint&diff=602504Talk:TrackPoint2020-03-25T02:04:08Z<p>Kolo: /* HP pointing stick sensitivity with libinput - probably applies to other vendors too */ new section</p>
<hr />
<div>== Udev rule ==<br />
:''Merged from Accuracy template in [[Trackpoint#udev configuration rule]]. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 11:18, 24 July 2015 (UTC)''<br />
I couldn't get the previous rule to trigger on boot unless I used the following:<br />
{{hc|1=/etc/udev/rules.d/10-trackpoint.rules|2=<br />
SUBSYSTEM=="serio", DRIVERS=="psmouse", '''ACTION=="add"''', ENV{SERIO_TYPE}=="05", '''WAIT_FOR="/sys/devices/platform/i8042/serio1/serio2/press_to_select"''', ATTR{press_to_select}="1", ATTR{sensitivity}="230", ATTR{speed}="200"<br />
}}<br />
The <code>WAIT_FOR</code> part instructs udev to wait for the trackpoint to be properly initialized before changing attributes (path might differ on trackpoint-only devices).<br />
<br />
-- 10:28, 12 May 2015 [[User:Jabbourb|Jabbourb]] <br />
<br />
:The <code>WAIT_FOR</code> attribute was removed with the release of [[systemd]] 222-1 ([https://github.com/systemd/systemd/commit/f2b8052fb648b788936dd3e85be6a9aca90fbb2f See the commit on github]). There does not seem to be a workaround available at the moment.<br />
:-- 09:45, 24 July 2015 [[User:Matthiasr94|Matthiasr94]]<br />
<br />
::I reported the issue as it was described in the comments at github. The report can be found [https://bugzilla.kernel.org/show_bug.cgi?id=102461 here]. Not everyone seems to agree. [[User:Meidell|Meidell]] ([[User talk:Meidell|talk]]) 21:06, 7 August 2015 (UTC)<br />
<br />
:::Does the [[TrackPoint#Tap_to_select|tmpfiles way]] work for you? -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 14:34, 2 September 2015 (UTC)<br />
<br />
::::Actually disregard this, apparently the tmpfiles way does not work even for the OP.[https://wiki.archlinux.org/index.php?title=TrackPoint&diff=397586&oldid=397569] [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 18:40, 2 September 2015 (UTC)<br />
<br />
A solution to the deprecated <code>WAIT_FOR</code> statement is to use a different udev event as described in this discussion [https://bbs.archlinux.org/viewtopic.php?pid=1568223#p1568223]. <br />
{{hc|1=/etc/udev/rules.d/10-trackpoint.rules|2=<br />
ACTION=="add",SUBSYSTEM=="input",ATTR{name}=="TPPS/2 IBM TrackPoint",ATTR{device/sensitivity}="200",ATTR{device/speed}="120"<br />
}}<br />
--[[User:The ben|The ben]] ([[User talk:The ben|talk]]) 13:08, 14 October 2015 (UTC)<br />
<br />
:The rule as of [https://wiki.archlinux.org/index.php?title=TrackPoint&diff=422058&oldid=421189 24 February 2016] works for me on a [[Lenovo ThinkPad X201|X201]]. Can this be closed? -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 13:38, 18 July 2016 (UTC)<br />
<br />
== Middle-button scrolling with libinput ==<br />
The article mentions that "When using xf86-input-libinput, middle-button scrolling is enabled by default".<br />
That may be so, but not when using a PS/2-to-USB adapter. This way middle-button scrolling does not work.<br />
It used to work with evdev.<br />
If anybody knows where to set the needed properties for libinput, please amend the article.<br />
<br />
--[[User:Tskevy|Tskevy]] ([[User talk:Tskevy|talk]]) 13:17, 16 March 2017 (UTC)<br />
<br />
== udev hwdb entry out-of-date ==<br />
<br />
As yurb (Yuriy Bulka?) has noticed, this seems to be removed: [https://cgit.freedesktop.org/wayland/libinput/commit/src/evdev.c?id=3669fa10dff95371658647272ef7ac7a3ef29a61].<br />
: I have updated the section, but will appreciate if someone reviewed it. Thanks. --[[User:Setthemfree|Setthemfree]] ([[User talk:Setthemfree|talk]]) 15:29, 13 June 2018 (UTC)<br />
<br />
== HP pointing stick sensitivity with libinput - probably applies to other vendors too ==<br />
<br />
Problem: I was unable to adjust sensitivity on a HP pointing stick (listed as "PS/2 Generic Mouse" by xinput) using any of the described methods. There's no "sensitivity" or "deceleration" or similar properties when runing "xinput list-props" and fiddling with the other properties doesn't affect sensitivity.<br />
<br />
Solution: One can finely adjust speed using the "Coordinate Transformation Matrix", by changing (only) the first two entries of the main diagonal - that is the first two 1's in the default configuration, to something higher. <br />
<br />
In fact, it's possible to make other changes such as direction, etc, (i.e. if one wish to invert an axis or rotate, for whatever reason) or to make one axis more sensitive. Some details regarding how the matrix is applied are listed in the driver documentation here:<br />
<br />
https://wayland.freedesktop.org/libinput/doc/1.1.0/group__config.html#ga09a798f58cc601edd2797780096e9804<br />
<br />
I did a quick search and there's no mention of this on the libinput article either. On the one hand maybe it's worth adding in somewhere because it seems rather useful. On the other, I'm not sure if it's the feature is supposed to be used this way since I've only seen it mentioned in regards to touchscreen calibration, so I'm a little reluctant.<br />
<br />
[[User:Kolo|Kolo]] ([[User talk:Kolo|talk]]) 02:04, 25 March 2020 (UTC)</div>Kolo