Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
No EDID on bus 1
No EDID on bus 2
No EDID on bus 3
No EDID on bus 4
No EDID on bus 5
No EDID on bus 6
No EDID on bus 7
No EDID on bus 8
Looks like no busses have an EDID. Sorry!
Attempting to use the classical VBE interface
Performing real mode VBE call
Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
Function unsupported
Call failed
VBE version 0
VBE string at 0x0 "O`"
VBE/DDC service about to be called
Report DDC capabilities
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
Function unsupported
Call failed
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function unsupported
Call failed
The EDID data should not be trusted as the VBE call failed
Error: output block unchanged
I'm sorry nothing was successful. Maybe try some other arguments
if you played with them, or send an email to Matthew Kern
What GPU? Intel? AMD? In debian buster with my AMD gpu, I had to add "firmware-amd-graphics" to have external monitor support. Which I didn't have to add in previous generations of debian. But I start with minimal installs.
$ lspci -nnk
You might also try the nomodeset kernel parameter. In either case it seems like you might be using fbdev or vesa drivers. Which are limited. Beyond that you could have a BAD HDMI CABLE. I've had that issue before. Perhaps other issues if you're using an HDMI to DVI adapter, which might block any EDID information from being seen. You don't need EDID to use the monitor, but having to manually setup a modeline to use the monitor kind of sucks. My guess like a previous poster is a hardware issue, aka bad cable.
WilliamTell
05-08-2007, 01:40 PM
I have a 42PF5421 Philips 42" HDTV, and its native resolution is 1366 x 768, but in the manual it lists the supported resolutions for PC use as 800x600 and 1024x768. I've read somewhere that I can ruin the TV by using wrong resolutions, and I don't want to do that. It's connected with a HDMI -> DVI cable, can I use any widescreen resolutions that are under 1024, or can the PC resolutions also go up to 1366.
WilliamTell
05-09-2007, 03:12 AM
I figure this should probably post this:
Monitor
Windows description......... Plug and Play Monitor
Manufacturer................ Philips
————————————————————————————
Plug and Play ID............ PHL4650
Serial number............... 9
EDID data source............ I2C bus (real-time)
————————————————————————————
Manufacture date............ 2005, ISO week 43
EDID revision............... 1.3
Display type and signal..... Digital
Sync input support.......... n/a
Screen size................. 710 x 400 mm (~34")
Power management............ Standby
Color characteristics
Display gamma............... 2.20
Red chromaticity............ Rx 0.617 - Ry 0.334
Green chromaticity.......... Gx 0.283 - Gy 0.590
Blue chromaticity........... Bx 0.143 - By 0.086
White point (default)....... Wx 0.284 - Wy 0.295
Standard timings supported
640 x 360 at 85Hz - VESA
640 x 480 at 60Hz - IBM VGA
640 x 480 at 60Hz - Philips
640 x 480 at 75Hz - VESA
720 x 480 at 60Hz - Philips
720 x 576 at 50Hz - Philips
800 x 450 at 85Hz - VESA
800 x 600 at 60Hz - VESA
800 x 600 at 75Hz - VESA
832 x 624 at 75Hz - Mac II
1024 x 576 at 85Hz - VESA
1024 x 768 at 60Hz - VESA
1024 x 768 at 75Hz - VESA
1152 x 648 at 75Hz - VESA
1280 x 720 at 50Hz - Philips
1280 x 720 at 60Hz - Philips
1280 x 720 at 60Hz - VESA
1280 x 768 at 60Hz - Philips
1920 x 540 at 50Hz - Philips
1920 x 540 at 60Hz - Philips
1920 x 1080 at 25Hz - Philips
1920 x 1080 at 30Hz - Philips
CE standard timings supported
640 x 480p at 59.94/60Hz (4:3) - Default
720 x 480p at 59.94/60Hz (16:9) - EDTV
1280 x 720p at 59.94/60Hz (16:9) - HDTV
1920 x 1080i at 59.94/60Hz (16:9) - HDTV
720 x 576p at 50Hz (16:9) - EDTV
1280 x 720p at 50Hz (16:9) - HDTV (Native)
1920 x 1080i at 50Hz (16:9) - HDTV
User/computer information
Registered user name........ TeleV
Registered organization..... n/a
Network user name........... TV
Network computer name....... TELEVISION
Windows version ............ Windows XP
Windows build .............. 5.01.2600 Service Pack 2
Installation date .......... 5/8/2007 12:00:00 PM
I also tried another laptop using a VGA->HDMI converter, which gave the modeline below, for a 1366x768 resolution, which gave a working display through the TV.
2005 was pre HDMI turn over for the USA. pre-OTA television anyway. AKA digital / ATSC. But under timings it has a few modes. Noticing that anything over 720 vertical is interlaced, not progressive. It seems it could do those interlaced modes. Not sure if that's at "native" resolution. Modern displays are pretty good about protecting themselves from bad settings. So might as well try if that interests you. Just be prepared to be blind until you reboot, or re-install if you don't have recovery "methods" that you can use (while blind) or via chroot on other installs / hardware.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.