Hi All,
I have just moved from Angstrom to Debian.
I have a terrible quality picture on my HDMI monitor which used to be perfect under Angstrom.
xrandr is giving me an error saying that it cannot get gamma and it’s set to 0:0:0. I assume this is a clue as to why the display image appears to be a stretched resolution, it’s almost unreadable.
xrandr: Failed to get size of gamma for output default
Info from xrandr is:
`
debian@beaglebone:~$ xrandr --verbose
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080
default connected 1920x1080+0+0 (0x102) normal (normal) 0mm x 0mm
Identifier: 0x101
Timestamp: 1938778
Subpixel: unknown
Clones:
CRTC: 0
CRTCs: 0
Transform: 1.000000 0.000000 0.000000
0.000000 1.000000 0.000000
0.000000 0.000000 1.000000
filter:
1920x1080 (0x102) 0.0MHz *current
h: width 1920 start 0 end 0 total 1920 skew 0 clock 0.0KHz
v: height 1080 start 0 end 0 total 1080 clock 0.0Hz
`
Any ideas?
The other issue I have, is that lxpanel doesn’t seem to start, so I have to run it from a terminal window to get the bottom panel up???
I presume this is a simple config file issue somewhere?
Anyone else had these issues getting Debian to run on BBB?
This is what’s installed:
Linux beaglebone 3.8.13-bone79 #1 SMP Tue Oct 13 20:44:55 UTC 2015 armv7l GNU/Linux
My EDID says:
`
parse-edid: parse-edid version 2.0.0
parse-edid: EDID checksum passed.
EDID version 1 revision 3
Section “Monitor”
Block type: 2:0 3:fd
Block type: 2:0 3:fc
Identifier “D2342P”
VendorName “GSM”
ModelName “D2342P”
Block type: 2:0 3:fd
HorizSync 30-83
VertRefresh 56-61
Max dot clock (video bandwidth) 150 MHz
Block type: 2:0 3:fc
Block type: 2:0 3:ff
DPMS capabilities: Active off:yes Suspend:yes Standby:yes
Mode “1920x1080” # vfreq 60.000Hz, hfreq 67.500kHz
DotClock 148.500000
HTimings 1920 2008 2052 2200
VTimings 1080 1084 1089 1125
Flags “+HSync” “+VSync”
EndMode
Block type: 2:0 3:fd
Block type: 2:0 3:fc
Block type: 2:0 3:ff
EndSection
`
On Thu, 17 Dec 2015 05:45:00 -0800 (PST), Richard Markham
<richard.g.markham@gmail.com> declaimed the
following:
xrandr is giving me an error saying that it cannot get gamma and it's set
to 0:0:0. I assume this is a clue as to why the display image appears to be
a stretched resolution, it's almost unreadable.
Gamma normally refers to how brighness curves are implemented to map
linear color space to phosphor response. Not anything related to
resolution.
Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080
default connected 1920x1080+0+0 (0x102) normal (normal) 0mm x 0mm
I'd consider that 0mm to be significant...
1920x1080 (0x102) 0.0MHz *current
h: width 1920 start 0 end 0 total 1920 skew 0 clock
0.0KHz
v: height 1080 start 0 end 0 total 1080 clock
0.0Hz
Similar to those scan rates of 0.0...
So what’s causing the discrepancy between what the EDID is saying and what xrandr is saying?
On Fri, 18 Dec 2015 03:25:46 -0800 (PST), Richard Markham
<richard.g.markham@gmail.com> declaimed the
following:
So what's causing the discrepancy between what the EDID is saying and what
xrandr is saying?
Unfortunately that is out of my experience... I once tried mine on the
HDMI input of my computer monitor, but it was horrible...
My monitor is a 16:10 aspect, not 16:9, and was trying to scale the
1920x1080 from the BBB to fit 1920x1200 monitor.
On my Samsung TVs, OTOH, I had to set the TVs into a "fit screen" mode,
as the normal 16:9 mode seemed to incorporate overscan. I didn't even
realize there was an icon bar at the bottom of the display at first, as it
was way off the bottom. On "fit screen" it works well, should I want to
hook up the Logitech wireless keyboard/mouse, and operate with no network.