I thought it was baked into the kernel driver for the display

R

RodoMa92•4/21/24, 8:54 AM

Nope

R

RodoMa92•4/21/24, 8:54 AM

dmidecode -t 11 | grep -- "String $SLOT" | cut -d ":" -f 2 | awk '{$1=$1};1'

dmidecode -t 11 | grep -- "String $SLOT" | cut -d ":" -f 2 | awk '{$1=$1};1'

dmidecode -t 11 | grep -- "String $SLOT" | cut -d ":" -f 2 | awk '{$1=$1};1'

dmidecode -t 11 | grep -- "String $SLOT" | cut -d ":" -f 2 | awk '{$1=$1};1'

A

antheasOP•4/21/24, 8:54 AM

No not that

A

antheasOP•4/21/24, 8:54 AM

The adaptive brightness part

R

RodoMa92•4/21/24, 8:55 AM

Oh, right.

R

RodoMa92•4/21/24, 8:55 AM

Not sure on that.

R

RodoMa92•4/21/24, 8:55 AM

Can try to just return 8 and see if it changes anything

Aantheas I thought it was baked into the kernel driver for the display

R

RodoMa92•4/21/24, 8:55 AM

Besides, I doubt that you need a script to read a dmi string from kernel side

R

RodoMa92•4/21/24, 8:56 AM

It's most likely handled from the Steam Client itself.

A

antheasOP•4/21/24, 8:56 AM

I don't know how the SD does adaptive brightness

R

RodoMa92•4/21/24, 8:56 AM

Nor do I.

R

RodoMa92•4/21/24, 8:56 AM

In desktop mode it doesn't work tho.

R

RodoMa92•4/21/24, 8:57 AM

So I can tell you it's not the kernel handling this.

R

RodoMa92•4/21/24, 8:57 AM

(Besides access to the ALS kernel driver ofc)

A

antheasOP•4/21/24, 8:57 AM

Can you look into the iio devices

A

antheasOP•4/21/24, 8:57 AM

To see if there's an als one

R

RodoMa92•4/21/24, 8:59 AM

Yep

R

RodoMa92•4/21/24, 8:59 AM

root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# ls
firmware_node                              name
in_illuminance_input                       power
in_illuminance_integration_time            subsystem
in_illuminance_integration_time_available  uevent
in_illuminance_raw                         waiting_for_supplier

root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# ls
firmware_node                              name
in_illuminance_input                       power
in_illuminance_integration_time            subsystem
in_illuminance_integration_time_available  uevent
in_illuminance_raw                         waiting_for_supplier

root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# ls
firmware_node                              name
in_illuminance_input                       power
in_illuminance_integration_time            subsystem
in_illuminance_integration_time_available  uevent
in_illuminance_raw                         waiting_for_supplier

root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# ls
firmware_node                              name
in_illuminance_input                       power
in_illuminance_integration_time            subsystem
in_illuminance_integration_time_available  uevent
in_illuminance_raw                         waiting_for_supplier

A

antheasOP•4/21/24, 8:59 AM

Do a for through them

A

antheasOP•4/21/24, 8:59 AM

What does name say

A

antheasOP•4/21/24, 8:59 AM

I don't have the for loop handy

R

RodoMa92•4/21/24, 8:59 AM

root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# cat name 
ltrf216a

root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# cat name 
ltrf216a

root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# cat name 
ltrf216a

root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# cat name 
ltrf216a

R

RodoMa92•4/21/24, 9:00 AM

This is on LCD.

A

antheasOP•4/21/24, 9:00 AM

That's more advanced than the legion go

R

RodoMa92•4/21/24, 9:00 AM

Not sure if OLED has a different sensors.

R

RodoMa92•4/21/24, 9:00 AM

https://wmsc.lcsc.com/wmsc/upload/file/pdf/v2/lcsc/2201211430_Lite-On-LTR-F216A_C2971916.pdf

R

RodoMa92•4/21/24, 9:01 AM

The datasheet for it

R

RodoMa92•4/21/24, 9:04 AM

Values from first covering it with my fingers, then shining a torch attached to the window on top of the screen:

R

RodoMa92•4/21/24, 9:04 AM

root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# cat in_illuminance_input 
5
root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# cat in_illuminance_input 
0
root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# cat in_illuminance_input 
6
root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# cat in_illuminance_input 
661
root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# cat in_illuminance_input 
12560

root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# cat in_illuminance_input 
5
root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# cat in_illuminance_input 
0
root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# cat in_illuminance_input 
6
root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# cat in_illuminance_input 
661
root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# cat in_illuminance_input 
12560

root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# cat in_illuminance_input 
5
root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# cat in_illuminance_input 
0
root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# cat in_illuminance_input 
6
root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# cat in_illuminance_input 
661
root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# cat in_illuminance_input 
12560

root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# cat in_illuminance_input 
5
root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# cat in_illuminance_input 
0
root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# cat in_illuminance_input 
6
root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# cat in_illuminance_input 
661
root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# cat in_illuminance_input 
12560

R

RodoMa92•4/21/24, 9:05 AM

Seem exponential, the two last ones have just the same torch with the penultimate one 5 centimeters away instead of right on top of it.

R

RodoMa92•4/21/24, 9:14 AM

root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# cat in_illuminance_integration_time
0.100000
root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# cat in_illuminance_integration_time_available 
0.400000 0.200000 0.100000 0.050000 0.025000

root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# cat in_illuminance_integration_time
0.100000
root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# cat in_illuminance_integration_time_available 
0.400000 0.200000 0.100000 0.050000 0.025000

root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# cat in_illuminance_integration_time
0.100000
root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# cat in_illuminance_integration_time_available 
0.400000 0.200000 0.100000 0.050000 0.025000

root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# cat in_illuminance_integration_time
0.100000
root@DeckDiMarco:/sys/bus/iio/devices/iio:device0# cat in_illuminance_integration_time_available 
0.400000 0.200000 0.100000 0.050000 0.025000

R

RodoMa92•4/21/24, 9:15 AM

Seems to match the datasheet correctly as a first glance

A

antheasOP•4/21/24, 9:21 AM

I'm gonna look it over later

A

antheasOP•4/21/24, 9:22 AM

Although from what I remember the legion go has a different name and I think less info

S

Stian0xF•4/21/24, 9:38 AM

When decky-loader have a update pending in the ui, do I update it trough cli and ujust. Since the ui is hanging in 0%

E

Ellis•4/21/24, 9:43 AM

@antheas antheussy

Original message was deleted

A

antheasOP•4/21/24, 9:54 AM

Kernel ver that drops with f40 should fix both

A

antheasOP•4/21/24, 9:55 AM

I don't think the new kernel is there yet

A

antheasOP•4/21/24, 9:55 AM

Should be in 1-2 days

A

antheasOP•4/21/24, 9:56 AM

I think testing has the stock fedora kernel

A

antheasOP•4/21/24, 9:56 AM

But the patches that fix the framerate, speaker and suspend have been found

T

TigraTT•4/21/24, 10:13 AM

Probably a stupid question: I have read that some devices had problems with usb devices and a kernel update with version 39-20240414. but I am not sure if the problem should be solved by now and if my case is related to it. I have a GPD WIN 4 (6800u) with the official USB-C dock. With all newer stable builds, my USB devices connected to the dock are no longer recognized after entering my LUKS password. The problem only occurs when I have the dock connected during the boot process. Disconnecting and reconnecting the dock does not solve the problem. If I cold start without the dock until I have a desktop and then connect the dock, the usb-hub and all connected devices are recognized. if I rebase to a version older than 39-20240414 everything works fine.

Original message was deleted

A

antheasOP•4/21/24, 10:33 AM

you're the second one to ask that today, it should be usable with kde but i dont know the details

A

antheasOP•4/21/24, 10:33 AM

maybe its hidden now

TTigraTT Probably a stupid question: I have read that some devices had problems with usb ...

A

antheasOP•4/21/24, 10:34 AM

we thought it was fixed but it turns out not

A

antheasOP•4/21/24, 10:34 AM

i head kde 6 is busted in nested desktop though

SStian0xF When decky-loader have a update pending in the ui, do I update it trough cli and...

H

HikariKnight•4/21/24, 10:34 AM

you can if the ui is not working
could maybe be a permission issue

HHikariKnight you can if the ui is not working could maybe be a permission issue

S

Stian0xF•4/21/24, 10:39 AM

mhm, im so happy the tdp stuff works there now, ill check into the permissions, think i know where to look. Thanks..

Aantheas we thought it was fixed but it turns out not

T

TigraTT•4/21/24, 11:27 AM

OK. Thanks for clarification

Z

Zatari•4/21/24, 11:35 AM

How can I open the keyboard in gaming mode? Rog Ally

I thought it was baked into the kernel driver for the display

Similar Threads

Similar Threads

Similar Threads