I'm working on a Thinkpad x230 which I've had for a long time. I love it, and NetBSD is working well. However, I can't seem to find good documentation about which pieces of software, or Kernel modules make things work. I know these laptops see a lot of use, and I'm sure someone can point me in the right direction. What I am looking for: - Suspend/Resume, Suspend to RAM - Brightness Function keys working (Is this just keymapping?) - Hardware Volume key solution (FVWM window manager) - Some type of desktop/finder/file manager option to deal with USB/SD card media. I want an icon to self populate onto the desktop which when clicked, opens a file manager window to an already automounted USB or SD card drive. I'm still working to get all the pieces of FVWM working, but I like it so far. I've not ruled out going back to xfce, but I wanted to try something different. Hopefully someone can point me in the right directions with some of this. cheers!

> @"0x1b"#p5434 Suspend/Resume, Suspend to RAM I don't use it but, some form of _suspend_ apears to work, I never recall which, ... to RAM or to disk 🤔 , @"nia"#43 > @"0x1b"#p5434 Brightness Function keys working `xbacklight` is broken, at least on Intel chips. > @"0x1b"#p5434 Hardware Volume key solution Easy, as @"pfr"#61 already said.

Thank you @"nia"#43 Just to clarify, > @"nia"#p5457 You just enable powerd In `rc.conf` with `powerd=YES` ? Cheers

Thinkpad install finalization

pfr

Hey, I am also running NetBSD on my X230, what an excellent laptop!

As far as I know (which isn't a lot) suspend/resume is not yet supported on NetBSD... (although I hope I'm wrong and that I also learn something here).
Screen brightness is also not supported, although programs like redshift can be used to change the screen gamma (software dimming). This is not the same as your "hardware" dimming where the screen backlight is dimmed etc. therefore battery life is unchanged when using something like this. I was also under the impression that xbacklight was a better solution as it is actually able to change the backlight, but it's not packaged for NetBSD (although @rvp did make a patch which I am still yet to try out).
I stole my redshift.conf from @pin (along with most everything else 😅), check it out if you like. I'm sure you can bind your brightness keys to trigger different settings.

For volume, this is from my .spectrwm.conf

# Volume Keys
program[raise_volume]	= mixerctl -w outputs.master+=12
bind[raise_volume]	= XF86AudioRaiseVolume
program[lower_volume]	= mixerctl -w outputs.master-=12
bind[lower_volume]	= XF86AudioLowerVolume
program[mute_volume]	= mixerctl -w outputs.master=[192 0]
bind[mute_volume]	= XF86AudioMute

However you may need to use xev to get the correct keybind under FVWM.
FYI, 192 = 100% volume. Hence the odd increments of 12 bound to the keys.

Lastly, I'm not to sure what your after, but it sounds like you want your USB/SD cards auto-mounted? Most GUI file browsers will be fine to view/manipulate files, but your drives need to be mounted first. I've got a key binding set up for this also:

program[mount]		= doas mount -t msdos /dev/sd0e /mnt
bind[mount]		= MOD+Shift+m
program[unmount]	= doas umount -t msdos /mnt
bind[unmount]		= MOD+Shift+u

Of course I needed to also set a nopass exception in my /usr/pkg/etc/doas.conf

permit nopass dave cmd mount
permit nopass dave cmd umount

Anyway, I hope this helps. I dont know anything about desktop icons etc as I use a tiling wm. I also know nothing about FVWM but I hear it's hugely configurable so reckon it should be possible. I'm sure some of the friendly BSD wizards will chime in soon and be able to give you some more pointers on that.
🙂

pfr FYI, 192 = 100% volume. Hence the odd increments of 12 bound to the keys.

192 should actually be 254 😉

pfr

pin 192 should actually be 254 😉

Oh really? This was from your config though.. haha anyway, the speakers on the X230 are horrendous so I don't need it a full volume!

0x1b Suspend/Resume, Suspend to RAM

I don't use it but, some form of suspend apears to work, I never recall which, ... to RAM or to disk 🤔 , @nia

0x1b Brightness Function keys working

xbacklight is broken, at least on Intel chips.

0x1b Hardware Volume key solution

Easy, as @pfr already said.

nia

Suspend/Resume, Suspend to RAM

Yes, NetBSD can do suspend... especially on thinkpads

sysctl -w hw.acpi.sleep.state=3, or trigger it through powerd if you want

Brightness Function keys working (Is this just keymapping?)

It works automatically on some thinkpad models but not on others, otherwise you have to set up keybindings using xrandr or something.

Hardware Volume key solution (FVWM window manager)

You always have to configure this in the window manager in X, it's done automatically in the framebuffer, however. The increments the volume control uses are actually chip-dependent...

0x1b

EDIT #2-

Sysctl works! Problems resolved.
Now I just have to configure lid_close

Thanks for the tips. I'll keep working!

pfr

0x1b Now I just have to configure lid_close

Please report back if you figure this out. I wouldn't mind setting this up also.

nia

pfr It's really easy. You just enable powerd and add the sysctl command to /etc/powerd/scripts/lid_switch.

pfr

Thank you @nia

Just to clarify,

nia You just enable powerd

In rc.conf with powerd=YES ?

Cheers

0x1b

So hw.acpi.sleep.state=3 works when entered as a command.
I can't get the lid_switch to do it. The program seems to run the script, but that's about it. It will not sleep.

0x1b

I GOT IT WORKING!

All I did finally, was add the sleep state to the PowerD Script.
Its not necessarily fast, but it works!

Here is the complete file of my /etc/powerd/scripts/lid_switch


#!/bin/sh -
#
#       $NetBSD: lid_switch,v 1.9 2010/12/31 09:33:10 jruoho Exp $
#
# Generic script for lid switch events.
#
# Arguments passed by powerd(8):
#
#       device event

case "${2}" in
pressed)

        # If you want to put the system into sleep when the lid
        # is closed, see the sleep_button -script for examples.
        #
        wsconsctl -d -w backlight=0 >/dev/null
        sysctl -w hw.acpi.sleep.state=3
        exit 0
        ;;

released)
        wsconsctl -d -w backlight=1 >/dev/null
        sysctl -w hw.acpi.sleep.state=0
        exit 0
        ;;

*)
        logger -p warning "${0}: unsupported event ${2} on device ${1}" >&1
        exit 1
esac
~

pfr

0x1b
Ok, I did exactly the same thing, and after closing the lid it does go into hibernation/sleep mode, but wont come back out... I just get a blank screen with a cursor block in the top left hand corner.
Same thing happens when running the sysctl command in a terminal and use the power button to try wake it up,

nia

pfr If it's coming back up into the wrong tty (probably an unintialized one) you can swich out of it with ctrl+alt+f...

pfr

nia ctrl+alt+F5 brought me back on tty4. Any other, more elegant way to avoid having to do that?
@0x1b you having this same issue?

0x1b

pfr 1000% having the same issue.
I have not really looked into it yet. I was too busy preping for a job this week, and getting read to head out of town. I'll probably look into it more this week.

MY to do list: Fix wake on lid_open / Fix backlight / fix wpa_gui / ...

Everything else seems to be stable at the moment.

rvp

0x1b Fix backlight

If you have an Intel graphics card, see this

0x1b

Other than the backlight, and the volume keys I haven't started on yet.
Is there a way to get the middle mouse button scroll wheel function to work?

rvp

0x1b Is there a way to get the middle mouse button scroll wheel function to work?

That should work without any config with standard USB mice. But, if you're using a custom xorg.conf, then make sure it has something like this (mouse driver):

Section "InputDevice"
    Identifier  "Mouse0"
    Driver      "mouse"
    Option      "Device" "/dev/wsmouse"
    Option      "ZAxisMapping" "4 5"
EndSection

or this, with the ws driver:

Section "ServerLayout"
    Identifier  "X.org Configured"
    InputDevice "Mouse0" "CorePointer"
EndSection

Section "InputDevice"
    Identifier  "Mouse0"
    Driver      "ws"
    Option      "Device" "/dev/wsmouse"
    Option      "ZAxisMapping" "4 5"
    Option      "WAxisMapping" "6 7"
EndSection

The "WAxisMapping" is kept for 2-finger scrolling--which doesn't work yet on NetBSD on my HW (Elantech touchpad).

0x1b

So it turns out the intel_backlight code works. I read about it on this forums somewhere, I think it comes form FreeBSD.

So now I have a system that sleeps on lid_switch, but my problem is that it wakes the wrong tty, and I'm not sure how to fix that. More reading.

Backlight works from command line. Have not mapped the keys yet.

pfr

Are intel_backlight and xbacklight the same thing?

rvp

pfr Are intel_backlight and xbacklight the same thing?

xbacklight: uses Xorg + extensions for backlight control; therefore, does not work in console-mode; probably obsolete (doesn't work on Linux/FreeBSD with the modesetting DRMKMS driver); should work on all X display drivers which can do backlight control.

intel_backlight: pokes HW directly; so, works both in console-mode and in X; works only on Intel graphics cards.

That said, xbacklight does work on OpenBSD. OpenBSD also has a display.brightness property which you can set using wsconsctl for changing the console backlight brightness.