Hello,
I ran into an issue trying to use the vesa driver on my slackware laptop when I
try to add a resolution greater than 1024 x 768.
My previous call for help located here :
https://www.linuxquestions.org/questions/slackware-14/adding-a-resolution-when-using-xorg-vesa-conf-4175673896/
[http
On 21/01/2020 12:38, Michel Dänzer wrote:
On 2020-01-21 12:31 a.m., Danie Wessels wrote:
On 20/01/2020 15:39, Michel Dänzer wrote:
On 2020-01-20 6:37 a.m., Danie Wessels wrote:
On 17/01/2020 13:16, Michel Dänzer wrote:
On 2020-01-16 10:49 p.m., Danie Wessels wrote:
Hi
I have just upgraded C
On 2020-01-21 12:31 a.m., Danie Wessels wrote:
> On 20/01/2020 15:39, Michel Dänzer wrote:
>> On 2020-01-20 6:37 a.m., Danie Wessels wrote:
>>> On 17/01/2020 13:16, Michel Dänzer wrote:
On 2020-01-16 10:49 p.m., Danie Wessels wrote:
> Hi
>
> I have just upgraded Centos 7 to 8 on th
On 20/01/2020 15:39, Michel Dänzer wrote:
On 2020-01-20 6:37 a.m., Danie Wessels wrote:
On 17/01/2020 13:16, Michel Dänzer wrote:
On 2020-01-16 10:49 p.m., Danie Wessels wrote:
Hi
I have just upgraded Centos 7 to 8 on this same hardware and previous
gnome installation was fine with 1920x1200
On 20/01/2020 15:39, Michel Dänzer wrote:
On 2020-01-20 6:37 a.m., Danie Wessels wrote:
On 17/01/2020 13:16, Michel Dänzer wrote:
On 2020-01-16 10:49 p.m., Danie Wessels wrote:
Hi
I have just upgraded Centos 7 to 8 on this same hardware and previous
gnome installation was fine with 1920x1200
On 2020-01-20 6:37 a.m., Danie Wessels wrote:
> On 17/01/2020 13:16, Michel Dänzer wrote:
>> On 2020-01-16 10:49 p.m., Danie Wessels wrote:
>>> Hi
>>>
>>> I have just upgraded Centos 7 to 8 on this same hardware and previous
>>> gnome installation was fine with 1920x1200 resolution on the HP LP2465
On 17/01/2020 13:16, Michel Dänzer wrote:
On 2020-01-16 10:49 p.m., Danie Wessels wrote:
Hi
I have just upgraded Centos 7 to 8 on this same hardware and previous
gnome installation was fine with 1920x1200 resolution on the HP LP2465
(24" ) monitor. (BTW: Upgrade did not go smooth due to insuffi
On 2020-01-16 10:49 p.m., Danie Wessels wrote:
> Hi
>
> I have just upgraded Centos 7 to 8 on this same hardware and previous
> gnome installation was fine with 1920x1200 resolution on the HP LP2465
> (24" ) monitor. (BTW: Upgrade did not go smooth due to insufficient
> space on root partition).
>
Radeon HD 6900 Series,
AMD Radeon HD 6900M Series, Mobility Radeon HD 6000 Series, BARTS,
AMD Radeon HD 6800 Series, AMD Radeon HD 6700 Series, TURKS, CAICOS,
ARUBA, TAHITI, PITCAIRN, VERDE, OLAND, HAINAN, BONAIRE, KABINI,
MULLINS, KAVERI, HAWAII
[ 115.956] (II) modesetting: Driver for M
On Mon, 2018-05-21 at 17:12 +, G. Sebastián Pedersen wrote:
/[ 25.201] (II) VESA: driver for VESA chipsets: vesa />>/[ 25.201] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not
permitted) />
Pretty sure this means your X server isn't running as root, and needs
On Mon, 2018-05-21 at 18:35 +, G. Sebastián Pedersen wrote:
> May 21, 2018 6:31 PM, "Adam Jackson" wrote:
>
> > On Mon, 2018-05-21 at 17:12 +, G. Sebastián Pedersen wrote:
> >
> > > [ 25.201] (II) VESA: driver for VESA chipsets: vesa
> > > [
May 21, 2018 6:31 PM, "Adam Jackson" wrote:
> On Mon, 2018-05-21 at 17:12 +, G. Sebastián Pedersen wrote:
>
>> [ 25.201] (II) VESA: driver for VESA chipsets: vesa
>> [ 25.201] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not
>> permitted)
On Mon, 2018-05-21 at 17:12 +, G. Sebastián Pedersen wrote:
> [25.201] (II) VESA: driver for VESA chipsets: vesa
> [25.201] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not
> permitted)
Pretty sure this means your X server isn't running as root, and needs
Hi guys,
I recently update my Parabola Linux (essentially Arch) and X window stop
working.
Since a few years I use the vesa driver.
Asking in the Parabola irc, someone suggest it may be an upstream "problem"
with the xorg-server.
Here is my Xorg.0.log
Any help would be really ap
As I have been told by MrElendig, there is probably an upstream bug in
1.17.1 version of xorg when dealing with VESA driver.
After upgrading to 1.17.1 I also have confirmed that XFCE works remotely
in X2GO but it's not working locally. I suppose that's because X2GO
doesn'
> > 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 deffinitel
t;fbdev"
You're deffinitely using the vesa driver. The radeon driver is loaded, but
then the vesa driver is initialized as first and it takes control over your
card, so finally, according to line #1700, the radeon driver is unloaded:
Side question --
Was it unloaded because Vesa loa
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
[ 1684.746] (II) LoadModule: "radeon"
> [ 1684.748] (II) LoadModule: "vesa"
> [ 1684.749] (II) LoadModule: "fbdev"
> [...]
>
> I give you my full Xorg.0.log here:
> http://pastebin.com/fsPBgt5P
>
> If you find an interesting line telling
> [...]
> > 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
>From time to time, I find myself having to use the xf86-video-vesa
driver when my xf86-video-r128 driver fails after an upgrade (I'll
make a separate post about that).
When I use the vesa driver, I have a problem with my X11 screen going
into what I call dim-mode, where the graphic s
I am trying to analyse the Xorg.0.log in /var/log on an openSUSE 12.3
install in a Hyper-V virtual machine.
CentOS 6.3 and Ubuntu 12.04 LTS both loaded fine, but for some reason the
vesa driver for the virtualized graphics card (Microsoft graphics card) did
not load only the primitive fbdev and
I am trying to analyse the Xorg.0.log in /var/log on an openSUSE 12.3
install in a Hyper-V virtual machine.
CentOS 6.3 and Ubuntu 12.04 LTS both loaded fine, but for some reason the
vesa driver for the virtualized graphics card (Microsoft graphics card) did
not load only the primitive fbdev and
On Thu, 22 Mar 2012 09:48:27 -0400
Adam Jackson wrote:
> On Thu, 2012-03-22 at 13:38 +0100, Henrik Pauli wrote:
>
> > it appears to me that xorg-driver-vesa-2.3.0 does not compile with
> > the latest X, and it hasn't been updated since 2010. Are there any
> > plans to release a new version or i
On Thu, 2012-03-22 at 13:38 +0100, Henrik Pauli wrote:
> it appears to me that xorg-driver-vesa-2.3.0 does not compile with the
> latest X, and it hasn't been updated since 2010. Are there any plans to
> release a new version or is there another driver that should be used
> instead as a generic f
Hi,
it appears to me that xorg-driver-vesa-2.3.0 does not compile with the
latest X, and it hasn't been updated since 2010. Are there any plans to
release a new version or is there another driver that should be used
instead as a generic fallback?
___
xo
47 matches
Mail list logo
