Vladimir Eroshenko

if your log file weighs gigabytes (as we have 3-5 GB) per day, then the check fails with an error. I know for sure that there should have been information...

I'm facing the same problem. to solve it temporarily, I simply changed the binding port from 8080 to 80 inside the container frontend. ``` ports: # - 9001:8080 - 9001:80...

I tried other kernels. - 6.12.12-2 - the same thing, there is no device /dev/io:device1 - 6.6.75-2 - There are no /de/iio* devices at all

Output command **iio_info**: ```bash > iio_info . . . iio:device0: mxc4005 (buffer capable) 4 channels found: accel_x: (input, index: 0, format: be:s12/16>>4) 4 channel-specific attributes found: attr 0: mount_matrix value:...

I guess this is the part of the file. ```bash        Device (ACMK)        {            Name (_ADR, Zero)  // _ADR: Address            Name (_HID, "MDA6655")  // _HID: Hardware ID            Name (_CID, "MDA6655")  //...

I was displaying a list of all iio:device* files with the command ```bash > ls -lahnd /sys/devices/pci0000:00/0000:00:*/*/*/*/*/*/iio:device* ``` and I found 104 directories. all device0, none device1 [ls_pci.txt](https://github.com/user-attachments/files/19073830/ls_pci.txt)

@rhalkyard Hey bro, is there anything we can do to help you solve this problem?

> So I saw that my sensor was using bus 11 and 12. this is a really cool option and it works. It's only a partial pity... when I ran...

HI @typhoe https://github.com/rhalkyard/minibook-dual-accelerometer/issues/3#issuecomment-2869854538 I applied this fix and every time I reboot the devices work despite their id. super but I also have problems with the orientation of the screen...

@typhoe I was thinking about your question about ACCEL_MOUNT_MATRIX. the ".rules" files use the value of ENV{ACCEL_MOUNT_MATRIX}="0,-1,0;1,0,0;0,0,1", but when I entered the `cat /sys/devices/pci command.:00/*/*/*/*/*/ in_accel_mount_matrix` I got 7 files...