Hi Sir ,
On checking the RANDR status using "grep -i -C 2 randr
/var/log/Xorg.0.log".
Its found that RANDR is disabled .
It shows
[ 21.083] Initializing built-in extension XFIXES
[ 21.083] Initializing built-in extension RENDER
[ 21.083] Initializing built-in extension RANDR
[ 21.083] Initializing built-in extension COMPOSITE
[ 21.083] Initializing built-in extension DAMAGE
--
[ 21.209] (==) Depth 24 pixmap format is 32 bpp
[ 21.325] (II) FBDEV(0): display rotated; disabling DGA
[ 21.325] (II) FBDEV(0): using driver rotation; disabling
XRandR
[ 21.325] (==) FBDEV(0): Backing store disabled
[ 21.326] (==) FBDEV(0): DPMS enabled
[ 21.326] (--) RandR disabled
[ 21.443] (II) AIGLX: Screen 0 is not DRI2 capable
[ 21.443] (II) AIGLX: Screen 0 is not DRI capable
If you have any inputs on this issue please let me know
Regards ,
Jimmy
On Tuesday, 22 April 2014 16:01:13 UTC+5:30, [email protected] wrote:
>
> Hi Sir ,
>
> I was able to rotate the display by the below method display now
> works fine in portrait mode .
> But i having a new issue in System settings--> Display settings.
> It shows "Could not screen information RANDR extension is not
> present".
> If you have any inputs on this issue please let me know.
>
>
> Regards ,
> Jimmy
>
> On Thursday, 26 September 2013 23:45:39 UTC+5:30, Louis McCarthy wrote:
>>
>> Success!
>>
>> I installed fbdev (2:0.4.2-r17.0.12):
>> opkg install xf86-video-fbdev
>>
>> I then enabled fbdev in X11 by editing the "Device" section of
>> /etc/X11/xorg.conf to:
>> Section "Device"
>> Identifier "Builtin Default fbdev Device 0"
>> Driver "fbdev"
>> Option "Rotate" "CCW"
>> EndSection
>>
>> That rotated the screen, but the touchscreen needed to swap x and y, and
>> invert x, so I added two Options to the "evdev touchscreen catchall"
>> identifier of /usr/share/X11/xorg.conf.d/10-evdev.conf:
>> Section "InputClass"
>> Identifier "evdev touchscreen catchall"
>> MatchIsTouchscreen "on"
>> MatchDevicePath "/dev/input/event*"
>> Driver "evdev"
>> Option "SwapAxes" "true"
>> Option "InvertX" "true"
>> EndSection
>>
>> Which worked for the base X server (clock face pointer and login screen),
>> but as soon as the default user logged in, the touchscreen lost its swap
>> axes option. I could run:
>> xinput --set-prop "ti-tsc" "Evdev Axes Swap" 1
>> from an xterm window, to get it to work again, but I wanted it to be
>> automatic.
>>
>> At first I tried adding it to the .xprofile file, but that didn't work. I
>> then found that by modifying /etc/pointercal.xinput to the following:
>> xinput set-int-prop "ti-tsc" "Evdev Axis Calibration" 32 3733 367 79 3992
>> ; xinput set-int-prop "ti-tsc" "Evdev Axes Swap" 8 1;
>> everything worked on a reboot.
>>
>> Thanks for your help, Gary. I wish it would have worked with modesetting
>> and xrandr, but I will leave that as an exercise for another user :)
>>
>> And for the HDMI vs LCD driver, as far as I know, the base (internal to
>> the AM33xx) lcd controller is used for both. I looked at the source dts
>> file for HDMI and it defines a similar fb section as the LCD7 dts file.
>> But, at this point, I don't need to dig any deeper....
>>
>> Louis
>>
>>
>> On Wednesday, September 25, 2013 6:39:14 PM UTC-5, garyamort wrote:
>>>
>>>
>>>
>>> On Wednesday, September 25, 2013 3:21:14 PM UTC-4, Louis McCarthy wrote:
>>>>
>>>> Thanks for sticking with me. Knowing that KMS is a type helps me
>>>> understand more about the video system.
>>>>
>>>
>>> Hmm, learn something new. modesetting is a driver too! I thought it
>>> just referred to the KMS type of driver, but it also refers to a fallback
>>> driver for X11.
>>>
>>> And it only supports a couple of options, one of which is not rotate!
>>>
>>>
>>> If your using some form of debian variant, you can try:
>>> "sudo apt-get install xserver-xorg-video-fbdev"
>>>
>>> Install the basic fbdev driver and give that a shot.
>>>
>>> You can also try xserver-xorg-video-omap and xserver-xorg-video-omapfb
>>> [the name may be slightly different, so you can also try "apt-cache
>>> search fbdev", omap and omapfb
>>>
>>>
>>> Now the bad news: I /think/ none of the above will work because they
>>> will only be used by the HDMI display by default. Checking the device tree
>>> source for BB-BONE-LCD7 I see lines such as:
>>> /* Settings for ThreeFive S9700RTWV35TR / LCD7 cape: */
>>> panel {
>>> compatible = "tilcdc,panel";
>>>
>>> My gut feeling is that this specifies the driver to use: ie use the
>>> tildc-panel driver. You could try exiting x-windows and then running
>>> "sudo modprobe -v panel-generic-dpi" [might need to do "sudo modprobe -v
>>> panel-generic-dpi.ko"]
>>>
>>> If that succeeds, then reload x-windows and check the x11 logs to see if
>>> the driver has changed.
>>>
>>>
>>>
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
