Lenovo (Yoga) Slim 7 Pro X 14ARH7 #84
Labels
lenovo
Issue related to the Lenovo computer
Comments
|
Please first:
Then, can you provide the outputs of As well as the outputs of |
|
Hello, Here is the output of all 4 video devices: /dev/video0[maxime@laptop-mxm ~]$ v4l2-ctl -d /dev/video0 --list-formats-ext
ioctl: VIDIOC_ENUM_FMT
Type: Video Capture
[0]: 'MJPG' (Motion-JPEG, compressed)
Size: Discrete 1920x1080
Interval: Discrete 0.033s (30.000 fps)
Size: Discrete 1280x720
Interval: Discrete 0.033s (30.000 fps)
Size: Discrete 960x540
Interval: Discrete 0.033s (30.000 fps)
Size: Discrete 848x480
Interval: Discrete 0.033s (30.000 fps)
Size: Discrete 640x480
Interval: Discrete 0.033s (30.000 fps)
Size: Discrete 640x360
Interval: Discrete 0.033s (30.000 fps)
Size: Discrete 352x288
Interval: Discrete 0.033s (30.000 fps)
Size: Discrete 320x240
Interval: Discrete 0.033s (30.000 fps)
Size: Discrete 320x180
Interval: Discrete 0.033s (30.000 fps)
[1]: 'YUYV' (YUYV 4:2:2)
Size: Discrete 1920x1080
Interval: Discrete 0.200s (5.000 fps)
Size: Discrete 1280x720
Interval: Discrete 0.100s (10.000 fps)
Size: Discrete 960x540
Interval: Discrete 0.067s (15.000 fps)
Size: Discrete 848x480
Interval: Discrete 0.050s (20.000 fps)
Size: Discrete 640x480
Interval: Discrete 0.033s (30.000 fps)
Size: Discrete 640x360
Interval: Discrete 0.033s (30.000 fps)
Size: Discrete 352x288
Interval: Discrete 0.033s (30.000 fps)
Size: Discrete 320x240
Interval: Discrete 0.033s (30.000 fps)
Size: Discrete 320x180/dev/video1[maxime@laptop-mxm ~]$ v4l2-ctl -d /dev/video1 --list-formats-ext
ioctl: VIDIOC_ENUM_FMT
Type: Video Capture/dev/video2[maxime@laptop-mxm ~]$ v4l2-ctl -d /dev/video2 --list-formats-ext
ioctl: VIDIOC_ENUM_FMT
Type: Video Capture
[0]: 'GREY' (8-bit Greyscale)
Size: Discrete 640x360
Interval: Discrete 0.067s (15.000 fps)/dev/video3And here is the output of configure command with verbose parameter[maxime@laptop-mxm ~]$ sudo linux-enable-ir-emitter -v configure
[sudo] Mot de passe de maxime :
INFO: Ensure to not use the camera during the execution.
INFO: Warning to do not kill the process !
Is the ir emitter flashing (not just turn on) ? Yes/No ? no
DEBUG: unit: 4, selector: 2, cur control: 0 32, first control to test: 0 0, res control: 1 0, max control: 255 255
Is the ir emitter flashing (not just turn on) ? Yes/No ? no
Is the ir emitter flashing (not just turn on) ? Yes/No ? no
Is the ir emitter flashing (not just turn on) ? Yes/No ? no
Is the ir emitter flashing (not just turn on) ? Yes/No ? no
Is the ir emitter flashing (not just turn on) ? Yes/No ? no
DEBUG: Negative answer limit exceeded, skipping the pattern.
DEBUG: unit: 4, selector: 3, cur control: 0, first control to test: 1, res control: 1, max control: 255
CRITICAL: Cannot access to /dev/video2
ERROR: Impossible to reset the control.
INFO: Please keep this debug in case of issue :
DEBUG: unit: 4, selector: 3, control: 0
ERROR: The configuration has failed. |
|
Ok I see. The problem is that at the moment linux-enable-ir-emitter has no "memory" to ignore the problematic instructions that disabled (or crashed) the camera. I will think about implementing this feature. This is the first time I've seen this case. Unfortunately, I am going to be very busy until February. |
|
Hi |
|
You can test it on the dev branch, you have to install the OpenCV C++ libraries ( The software will ask you to shut down and boot and retry at some point I could not test as I cannot reproduce this problem; send me the outputs in case of issue Don't hesitate to ask me any question if you need help |
|
Thanks! Here is the output for the initial run in the dev branch: After rebooting, it asks me infinitely, and none of them work. Here is the output of where I am at. I did not close it yet, so if I should continue to do the answers, tell me. output after reboot |
|
OK! So little update 2 minutes after, I was very near the end of the script and it ended by itself, so here is the full output after the reboot, you can discard the one from before. Output after reboot |
There is always an ending, since it have to explore all the possibilities, and your camera has a lot. I've made a modification, could you please retry : I've added the parameter Although, your camera may require a more complex configuration, such as a combination of several instructions. This kind of case could also be done using a 100% automatic technique. |
|
That new version also did not work. BTW Did you see my second reply where I say I was able to go through all the possibilities one by one? I got the same result but it might be more precise than the new one. Anyways, here is the new output `sudo linux-enable-ir-emitter -v configure -l 1` output |
|
With the current version I can't do anything more for your problem. But I keep your issue in a corner of my head. When v5 will be ready, I hope it will be able to activate your camera |
|
Hey, I'm coming back to you with a new version that might be able to configure your camera. The installation method has changed, I no longer maintain the Fedora COPR, but a unique tarball. To configure your camera, run the command This can be a long process, but, since all you have to do is confirm whether it works, you don't have to be in the terminal all the time. You can let it search on the side, and cross your fingers, because this time (unless there's a bug in this pre-version) the tool will try everything it can try. And as a result, I don't think I'll be able to make a future version that will activate your emitter. If the transmitter is flashing and the terminal hasn't asked for confirmation, you'll have to switch to manual mode with If you no longer wish to configure your infrared camera, no problem, please just close the issue. |
|
Hey, thanks for replying with this, I am currently trying this, it seems it will take a very long time, doing 0-256 256 (I assume it is 256) times. Do you have a Matrix channel (or other ways of contact)? For now I am at the 200 2 attempt, still nothing but I guess there is hope! |
|
Yes indeed, it captures one second of video every time it tries something. So if there are a lot of possibilities, as in your case, it can take a long time. But normally, you don't have to do anything? No, I don't have a Matrix channel, but if you need, I can find out how it works. Or you can email me (the address is on my GitHub profile) and I'll send you my discord profile. |
EmixamPP
changed the title
|
Hey, please try the v6 #154. There is a bot comment with a link to the tarball. Please uninstall any existing version first: Execute |
|
Hello! I have just ran the software again, and at the step before the last one, I saw flashing! This is certainly a good sign. I have pasted below both the output of the software and the file in /etc/ /etc/linux-enable-ir-emitter/pci-0000\:05\:00.0-usbv2-0\:1\:1.2-video-index0Output of configure commandI am pretty sure the Also, do you have any idea if the drivers generated from your project could in any way be upstreamed if they are confirmed to work and have been tested? This could allow to unlock many laptops for many installs if only one person uses this program |
Oh nice!
This will work for a few people with exactly the same computer; so maybe another Lenovo (Yoga) Slim 7 Pro X 14ARH7 will not work using your configuration file, often the unit and selector are not the same. At first, since the configuration was done by sniffing a Windows VM, I asked people to bring up their configuration, but because of the problem I mentioned, I created this tool which normally enables any emitter with a single command. |
|
Thanks for the help! It turns out, the right instruction was After some more testing, I noticed that even if the configuration stays with the |
|
Execute |
|
Thanks! This seems to have worked to make the config persistent. Since this works, I think I will close the issue. Thanks a lot for your help and happy new year! |
|
Nice to hear! Happy new year! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you had 'ERROR: Impossible to reset the control' message, give the DEBUG info displayed
Ouput of
linux-enable-ir-emitter configure(used the default without the -d parameter. After the first fail I it does not ask me if I see the flashing, it just waits and gives the same error message)configure command output
Output of
v4l2-ctl --list-devicesOuput of
v4l2-ctl -d /dev/videoX --list-formats-extv4l2 device output
Additional info
Bus 005 Device 002: ID 30c9:0057 Luxvisions Innotech Limited Integrated RGB CameraThe text was updated successfully, but these errors were encountered: