Setting up lightdm for autologin

Hello, all. I need you help in configuring lightdm for autologin on FreeBSD 14.1. The handbook does not explain how to do it, and only mentions that a greeter is not required in case of autologin: I therefore found no better me

Re: Setting up lightdm for autologin

Jonathan Chen: > > I need you help in configuring lightdm for autologin on > > FreeBSD 14.1. [...] > > My lightdm.conf works with the following, with x11/slick-greeter: > > # > # General Configuration > # > [LightDM] > minimum-vt=9 > lock-memory=false > > # > # Seat configuration > # > [Seat:*] >

Re: Setting up lightdm for autologin

Jonathan Chen: > > I need you help in configuring lightdm for autologin on > > FreeBSD 14.1. [...] > > My lightdm.conf works with the following, with x11/slick-greeter: > > # > # General Configuration > # > [LightDM] > minimum-vt=9 > lock-memory=false > > # > # Seat configuration > # > [Seat:*] >

Re: Setting up lightdm for autologin

I wrote: > I need you help in configuring lightdm for autologin on > FreeBSD 14.1. I fixed the problem by regenerating the lightdm pam.d rules: cd /usr/local/etc/pam.d cp lightdm.sample lightdm cp lightdm-autologin.sample lightdm-autologin Can any lightdm users /not/ using au

Re: FreeBSD Day 2024 - Colin Percival

Steven Friedrich: > Linux routes sound from the audio driver to the video > driver causing sound to come out of the HDMI cable. > FreeBSD can't. This affects ALL i3, i5, i7, i9 systems. > FreeBSD can't even support x11 on my GMKtec K8 with Radeon > 780M graphics. Linux Mint does. Sounds a tad r

Need help controlling laptom display brightness via sysctl

Hello, all. I need your help in setting up the brightness control on my HP 15-b0xx laptop via sysctl. Upon perusal of the following materials: https://docs.freebsd.org/en/books/handbook/config/#acpi-config https://forums.freebsd.org/threads/laptop-setting-display-brightness.80524/ I added

Re: Need help controlling laptom display brightness via sysctl

Christos Margiolis: > I opened a bug report about the same issue a while ago: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279184 Very well. I suggest that you inlclude the all the information that I provided in my original message: 1. The relevant parts of /boot/loader.conf 2. The

Re: Need help controlling laptom display brightness via sysctl

Christos Margiolis to Anton Shepelev: > > If you (or whever) has this working, please let us know > > the value of the `hw.acpi.video.lcd0.active' sysctl > > variable. > > I haven't solved it yet, but my hw.acpi.video.lcd0.active > is 0 as well. If you happe

Re: Need help controlling laptom display brightness via sysctl

I wrote: > I need your help in setting up the brightness control on > HP 15-b0xx laptop via sysctl. I was infored that this ability has been discountinued in favour of the backlight utility, so I gave up and wrote the following devd rule: notify 10 { match "system""ACPI" ;

Enabling volume Fn-contols on the HP 15-0bxx laptop

Now that I have enabled[1] the Fn-brighness controls on my HP 15-0bxx, the next step is to enable the Fn-volume controls. Unlike brightness, I do not see anything in /var/run/devd.pipe when pressing pressing those keys, and there no is acpi_sound driver, and acpi_hp provides no sound events or con

Re: Need help controlling laptom display brightness via sysctl

Kevin Oberman: > This is what I used. I have it in /etc/devd/thinkpad.conf. > > notify 100 { > match "system" "ACPI"; > match "subsystem" "IBM"; > match "notify" "0x10"; > action "/usr/bin/backlight +"; > }; > > no

Re: Need help controlling laptom display brightness via sysctl

I wrote to Kevin Oberman: > I fear you missed my point that HP seems to have a > different approach to these ACPI events. In ThinkPad, the > up- and down-brighness events have fixed notify codes: > 0x10 and 0x11. In HP, on the other hand, the notify codes > represent the target brightness level

Re: Change to FreeBSD release scheduling etc.

Andrea Venturoli to Peter: > > In short, it takes me about 3 months to catch the > > surprizes[*] and fix (or find out how to cope with) the > > concerning issues, regressions et al. that come along > > with a new release. Up to now that would then give > > another 9 months during which the system