> > So, maybe a bad option or a missing dependency when I try to compile
> > xorg-server-16.0.
> >
> > You can see here the full output for the configure line:
> > http://pastebin.com/wYpk5ek4
>
> (In the future, the config.log file would be more useful)
>
> The problem is this:
>
> > checking
On 09.08.2014 21:53, YuGiOhJCJ Mailing-List wrote:
>
> So, maybe a bad option or a missing dependency when I try to compile
> xorg-server-16.0.
>
> You can see here the full output for the configure line:
> http://pastebin.com/wYpk5ek4
(In the future, the config.log file would be more useful)
> > >>> The full log is here:
> > >>> http://pastebin.com/a51DRWg6
> > >>
> > >> (II) Loading sub module "glamoregl"
> > >> (II) LoadModule: "glamoregl"
> > >> (WW) Warning, couldn't open module glamoregl
> > >> (II) UnloadModule: "glamoregl"
> > >> (II) Unloading glamoregl
> > >> (EE) RADEON
On Sat, 09 Aug 2014 13:13:46 +0900
Michel Dänzer wrote:
> On 08.08.2014 20:23, YuGiOhJCJ Mailing-List wrote:
> >>>
> >>> The full log is here:
> >>> http://pastebin.com/a51DRWg6
> >>
> >> (II) Loading sub module "glamoregl"
> >> (II) LoadModule: "glamoregl"
> >> (WW) Warning, couldn't open mod
On 08.08.2014 20:23, YuGiOhJCJ Mailing-List wrote:
>>>
>>> The full log is here:
>>> http://pastebin.com/a51DRWg6
>>
>> (II) Loading sub module "glamoregl"
>> (II) LoadModule: "glamoregl"
>> (WW) Warning, couldn't open module glamoregl
>> (II) UnloadModule: "glamoregl"
>> (II) Unloading glamor
> >>> - xorg-server-1.16.0
> >>> - glamor-egl-0.6.0
> >>
> >> With xserver 1.16.0 or later, you should use glamor from the xserver
> >> tree, not from the separate glamor tree.
> >>
> >
> > Yes, for xorg-server-1.16.0, no problem I can use the embedded glamor.
> > When I am compiling xorg-server-1
On 07.08.2014 20:52, YuGiOhJCJ Mailing-List wrote:
>>> - xorg-server-1.16.0
>>> - glamor-egl-0.6.0
>>
>> With xserver 1.16.0 or later, you should use glamor from the xserver
>> tree, not from the separate glamor tree.
>>
>
> Yes, for xorg-server-1.16.0, no problem I can use the embedded glamor.
>
> > - xorg-server-1.16.0
> > - glamor-egl-0.6.0
>
> With xserver 1.16.0 or later, you should use glamor from the xserver
> tree, not from the separate glamor tree.
>
Yes, for xorg-server-1.16.0, no problem I can use the embedded glamor.
When I am compiling xorg-server-1.16.0, I do:
$ ./configure
On 07.08.2014 11:37, Russ Whitaker wrote:
> On Thu, 7 Aug 2014, YuGiOhJCJ Mailing-List wrote:
>
>> Here is the exact configure line I have used:
>> ./configure --prefix=/usr --sysconfdir=/etc --libdir=/usr/lib
> --mandir=/usr/man --docdir=/usr/doc/mesa-10.0.2
> --with-dri-driverdir=/usr/lib/xorg
On Thu, 7 Aug 2014, YuGiOhJCJ Mailing-List wrote:
Here is the exact configure line I have used:
./configure --prefix=/usr --sysconfdir=/etc --libdir=/usr/lib
--mandir=/usr/man --docdir=/usr/doc/mesa-10.0.2
--with-dri-driverdir=/usr/lib/xorg/modules/dri
--with-dri-drivers="i915,i965" --ena
> >> > But I see a last problem: I have no 3d acceleration!
> >> > As you can see here:
> >> > $ cat /var/log/Xorg.0.log | grep Direct
> >> > [ 7567.271] (WW) RADEON(0): Direct rendering disabled
> >> >
> >> > The full xorg log is available here: http://pastebin.com/hSKjXsvL
> >> >
> >> > Do you k
On 05.08.2014 23:10, YuGiOhJCJ Mailing-List wrote:
>>> But I see a last problem: I have no 3d acceleration!
>>> As you can see here:
>>> $ cat /var/log/Xorg.0.log | grep Direct
>>> [ 7567.271] (WW) RADEON(0): Direct rendering disabled
>>>
>>> The full xorg log is available here: http://pastebin.co
On Tue, Aug 5, 2014 at 10:10 AM, YuGiOhJCJ Mailing-List
wrote:
>> > But I see a last problem: I have no 3d acceleration!
>> > As you can see here:
>> > $ cat /var/log/Xorg.0.log | grep Direct
>> > [ 7567.271] (WW) RADEON(0): Direct rendering disabled
>> >
>> > The full xorg log is available here:
> > But I see a last problem: I have no 3d acceleration!
> > As you can see here:
> > $ cat /var/log/Xorg.0.log | grep Direct
> > [ 7567.271] (WW) RADEON(0): Direct rendering disabled
> >
> > The full xorg log is available here: http://pastebin.com/hSKjXsvL
> >
> > Do you know how to have 3d acc
On 04.08.2014 21:03, YuGiOhJCJ Mailing-List wrote:
>
> But I see a last problem: I have no 3d acceleration!
> As you can see here:
> $ cat /var/log/Xorg.0.log | grep Direct
> [ 7567.271] (WW) RADEON(0): Direct rendering disabled
>
> The full xorg log is available here: http://pastebin.com/hSKjXs
On Thu, 31 Jul 2014 23:14:34 +0900
Michel Dänzer wrote:
> On 31.07.2014 19:47, YuGiOhJCJ Mailing-List wrote:
> >>>
> >>> I give you my full Xorg.0.log here:
> >>> http://pastebin.com/fsPBgt5P
> >>>
> >>> If you find an interesting line telling me what driver I am using please
> >>> highlight it
On 31.07.2014 19:47, YuGiOhJCJ Mailing-List wrote:
>>>
>>> I give you my full Xorg.0.log here:
>>> http://pastebin.com/fsPBgt5P
>>>
>>> If you find an interesting line telling me what driver I am using please
>>> highlight it for me.
>>
>> The radeon driver fails to initialize because of this:
>>
On 2014-07-31 12:47 (GMT+0200) YuGiOhJCJ Mailing-List composed:
...
> I give you my full Xorg.0.log here:
> http://pastebin.com/fsPBgt5P
...
problem is because my radeon module is not loaded:
$ lsmod | grep radeon
So, I load it:
$ sudo modprobe radeon
...
This is my new full Xorg.0.log fil
> >> [...]
> >>> So, I think that I am using the "vesa" Xorg driver for generic VESA video
> >>> cards instead of the "ati" video driver.
> >>>
> >>> How to be sure about that?
> >>
> >> Have a look at Xorg logs, usually /var/log/Xorg.0.log.
> >> --
> >
> > Yeah, but it seems to load both drivers
Łukasz Maśko wrote:
$ cat /var/log/Xorg.0.log | grep LoadModule
[...]
[ 1684.745] (II) LoadModule: "ati"
[ 1684.746] (II) LoadModule: "radeon"
[ 1684.748] (II) LoadModule: "vesa"
[ 1684.749] (II) LoadModule: "fbdev"
You're deffinitely using the vesa driver. The radeon driver is loade
On 07/30/14 12:52 PM, Linda A. Walsh wrote:
Łukasz Maśko wrote:
$ cat /var/log/Xorg.0.log | grep LoadModule
[...]
[ 1684.745] (II) LoadModule: "ati"
[ 1684.746] (II) LoadModule: "radeon"
[ 1684.748] (II) LoadModule: "vesa"
[ 1684.749] (II) LoadModule: "fbdev"
You're deffinitely using the
On 30.07.2014 22:58, YuGiOhJCJ Mailing-List wrote:
>> [...]
>>> So, I think that I am using the "vesa" Xorg driver for generic VESA video
>>> cards instead of the "ati" video driver.
>>>
>>> How to be sure about that?
>>
>> Have a look at Xorg logs, usually /var/log/Xorg.0.log.
>> --
>
> Yeah, bu
Dnia środa, 30 lipca 2014 15:58:22 YuGiOhJCJ Mailing-List pisze:
> > [...]
> >
> > > So, I think that I am using the "vesa" Xorg driver for generic VESA
> > > video
> > > cards instead of the "ati" video driver.
> > >
> > > How to be sure about that?
> >
> > Have a look at Xorg logs, usually /va
> [...]
> > So, I think that I am using the "vesa" Xorg driver for generic VESA video
> > cards instead of the "ati" video driver.
> >
> > How to be sure about that?
>
> Have a look at Xorg logs, usually /var/log/Xorg.0.log.
> --
Yeah, but it seems to load both drivers (and other drivers too):
Dnia środa, 30 lipca 2014 14:52:47 YuGiOhJCJ Mailing-List pisze:
[...]
> So, I think that I am using the "vesa" Xorg driver for generic VESA video
> cards instead of the "ati" video driver.
>
> How to be sure about that?
Have a look at Xorg logs, usually /var/log/Xorg.0.log.
--
Łukasz Maśko
Hello,
My computer is an ASUS x102ba [1].
When I type:
$ startx
I see that my display is strange:
- 1 screen only used (the external VGA screen)
- the font is too big
- the "xrandr" command tells me "Failed to get size of gamma for output default"
So, I think that I am using the "vesa" Xorg dri
26 matches
Mail list logo