Comments (12)
from ddcutil.
from ddcutil.
from ddcutil.
from ddcutil.
from ddcutil.
from ddcutil.
Hi Sanford
Thank you for looking at my problem.
Both 'ddcutil setvcp d0 x11' and 'ddcutil setvcp d0 x12' give me the error message "Invalid display number".
Please find attached the output of the commands you have been asking for (including also the result of 'ddcutil interrogate'). The output looks fairly "normal" and "unsuspicious" to me. Being not an expert, I can only guess what might be wrong or missing. Maybe I need to load more I2C kernel modules (i2c_dev, i2c_piix4)?
ddcutil environment.txt
ddcutil detect --verbose --ddc --force-slave-address.txt
ddcutil environment --verbose.txt
ddcutil interrogate.txt
from ddcutil.
Here we go:
- "[...] you're using an HP desktop with a Xeon processor having integrated graphics. Is that correct? Model?" => It's a HP EliteDesk 800 Mini PC (model F6X30EA#UUZ) with an i7-4785T CPU and an Integrated Graphics Controller.
- "Is there a secondary video card in the system?" => Nope.
- "If this happens to be a laptop, [...]" => It's not a laptop and there is no docking station.
- "Please try the following commands and send me the output." => Output:
ddcutil detect --verbose --trace ddc --trace i2c --stats.txt
ddcutil getvcp 10 --verbose --trace ddc --trace i2c --stats.txt
ddcutil getvcp 10 --bus 6 --force --verbose --trace ddc --trace i2c --stats.txt
FYI: I have just built and configured ddcutil for my Raspberry Pi. The output for the first set of commands looks similar, i.e. on the Raspi I also get the "Invalid display" and "DDC communication failed" errors:
ddcutil environment.raspi.txt
ddcutil detect --verbose --ddc --force-slave-address.raspi.txt
ddcutil environment --verbose.raspi.txt
ddcutil interrogate.raspi.txt
Thank you.
from ddcutil.
Hi again. You had the same thoughts as I did: In the user manual of the monitor there is an "Extra" tab mentioned on the OSD menu with an DDC-CI option for turning on/off DDC-CI support - on my monitor this option was turned off (default) :‑/ . So I have turned on DDC-CI and bingo: ddcutil does not complain anymore, i.e. I now get information for "Display 1" and the "DDC communication" error has gone.
The next problem was that switching interfaces with 'ddcutil setvcp d0 x11' (Linux PC -> Raspi) and 'ddcutil setvcp d0 x0f' (Raspi -> Linux PC) did not work: "Unrecognized VCP feature code: 0d". Finally, I have also found the solution for this remaining obstacle. The output of 'ddcutil capabilities' told me that the code for my monitor for changing input sources is 60 (and not 0d). So the working CLI commands for switching interfaces in my situation are 'ddcutil setvcp 60 x11' (Linux PC -> Raspi) and 'ddcutil setvcp 60 x0f' (Raspi -> Linux PC) - for both I have now defined handy keyboard shortcuts - mission accomplished :-))
Sanford, let me apologize for the fact that I have opened an issue here because of a wrong OSD default setting. I hope you have not spent too much time investigating my problem. I thank you very much for your efforts! You might want to consider adding a hint on your documentaton site (http://www.ddcutil.com/) for checking OSD settings before using ddcutil or reporting problems.
I owe you one!
from ddcutil.
I'm glad you say that the effort was worth it.
-
"Let me know if you can switch in both directions from the PC or the Pi." => Yes, it's working in both directions: On the Linux PC I enter 'ddcutil setvcp 60 x11' which switches to HDMI-1 where the Raspi is attached, and on the Raspi the command 'ddcutil setvcp 60 x0f' switches to DisplayPort-1 with my Linux PC attached. Apart from being very convenient, switching via ddcutil is much faster (<< 1s) than pressing the respective monitor button (~ 5s).
-
Please find attached the output of 'ddcutil interrogate' from both machines:
ddcutil interrogate.LinuxPC.txt
ddcutil interrogate.Raspi.txt
Let me thank you again for your help and for the many interesting explanations that you have provided. Please keep up your excellent work - ddcutil is a very useful and cool tool!
All the best from Switzerland & kind regards,
Fabian M.
from ddcutil.
"What I'm wondering is whether, just from the Linux PC, you can issue the command "ddcutil setvcp 60 x11" to switch to the Pi and then, again from the Linux PC, issue the command "ddcutil setvcp 60 x0f" to switch back." => This is working as well. While the monitor was showing the screen of my Raspi I've ssh'ed from my Android smartphone to my Linux PC and launched 'ddcutil setvcp 60 x0f' - the result was that my monitor switched back to the Linux PC - hope this helps.
from ddcutil.
Thanks for the advice. I'm just re-compiling ddcutil with the option --disable-usb ;-)
Update:
# before # ./configure --disable-usb && make && make install :
-rwxr-xr-x 1 1182084 17:03:01 2017-02-26 /usr/local/bin/ddcutil
# after ## ./configure --disable-usb && make && make install :
-rwxr-xr-x 1 881852 23:56:25 2017-02-26 /usr/local/bin/ddcutil
# delta (with both executables unstripped): 300232 bytes
from ddcutil.
Related Issues (20)
- Ubuntu 24.04 LTS prebuild package HOT 2
- Unable to set input source on Gigabyte M27Q HOT 2
- Failed assertion in check_video_adapters_list_implements_drm HOT 1
- Small suggestion for ddcutil documentation on the website HOT 1
- Dell UltraSharp 2209WAf: DDC communication failed HOT 8
- Ubuntu and Debian packages in OBS are missing libddcutil.so.x.x.x HOT 2
- Enhancement - consider packaging module loading HOT 2
- "Keeping adjust sleep multiplier" warning shown many times HOT 1
- Monitor resets many times on boot after new udev rule installed HOT 26
- System cannot enter S0ix sleep after running ddcutil detect HOT 7
- No (DisplayLink) displays found on 2.1.4, but works on 2.0.0 HOT 6
- ddcutil 2.1.4-1: DDC communication failed HOT 3
- [debian] updating linux-image pkg fails due to ddcutil dkms module failure HOT 2
- Cannot get capabilities: Maximum DDC retries exceeded. HOT 8
- Add an option to return the capabilities for a specific feature. HOT 4
- DDC communication failed (getvcp of feature x10 returned Error_Info[DDCRC_RETRIES in ddc_write_read_with_retry, causes: DDCRC_DDC_DATA(15)]) HOT 1
- Ddcutil crashes when some usb devices are connected HOT 1
- `ddcutil` ignores the final entry in `XDG_DATA_DIRS` when looking for an `mccs` file HOT 1
- Cannot update beyond 1.2.2-1 HOT 2
- Samsung C24F390 - DDC communication failed HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ddcutil.