On Wed, 24 Jan 2024 07:33:59 +
Tixy wrote:
> On Tue, 2024-01-23 at 13:34 -0700, Charles Curley wrote:
> [...]
>
> As you've already found out, that's not the latest one, and if I'm not
> mistaken is the one that introduce a wifi bug [1], so that could
> explain it getting stuck in the wif
On Tue, 2024-01-23 at 13:34 -0700, Charles Curley wrote:
> I went to shut down the machine, and it got stuck trying to shut down
> wpa_supplicant and Network Manager. Ten minutes into the shutdown, I
> finally pulled the plug. A few reboots and shutdowns later, I decided
> to try another kernel. I
On Wed, 24 Jan 2024 09:25:58 +0700
Max Nikulin wrote:
> On 24/01/2024 03:34, Charles Curley wrote:
> > So I purged the newer kernel, inux-image-6.1.0-15-amd64
>
> The current kernel is linux-image-6.1.0-17-amd64
>
> Perhaps you have not restored your sources.list or apt preferences
> after th
On 24/01/2024 03:34, Charles Curley wrote:
So I purged the newer kernel, inux-image-6.1.0-15-amd64
The current kernel is linux-image-6.1.0-17-amd64
Perhaps you have not restored your sources.list or apt preferences after
the accidents with kernel bugs. Check that nothing extra is added and
n
run chromium, I get:
>
> charles@jhegaala:~$ chromium &
> [2] 33609
> charles@jhegaala:~$ libva error:
> /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
>
> charles@jhegaala:~$
I seem to have solved this problem, entirely by accident.
I went to shut down the
On 19/01/2024 04:08, Charles Curley wrote:
charles@jhegaala:~$ chromium chrome://gpu
libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
^C
Killed
charles@jhegaala:~$
I did a killall -9 in another window to kill it.
Does it happen in the case of a new system user and a new
On 19/01/2024 04:08, Charles Curley wrote:
On Fri, 19 Jan 2024 00:02:44 +0700
Max Nikulin wrote:
Have you faced real issues namely with hardware acceleration?
Other than this, not that I know of.
I do not think the message concerning iHD is related to any real issue.
I see "oops" in the
itches in
https://peter.sh/experiments/chromium-command-line-switches/, to no
avail.
>
> chrome://gpu may provide more info.
>
Alas, chromium never gets far enough to deliver useful information.
charles@jhegaala:~$ chromium chrome://gpu
libva error: /usr/lib/x86_64-linux-gnu/dri
On 14/01/2024 00:19, Charles Curley wrote:
charles@jhegaala:~$ chromium &
[2] 33609
charles@jhegaala:~$ libva error:
/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
charles@jhegaala:~$ vainfo
libva info: VA-API version 1.17.0
libva info: Trying to open
/usr/lib/x86_64-linux-gnu
aala:~$ libva error:
/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
charles@jhegaala:~$ ps
PID TTY TIME CMD
32502 pts/800:00:00 bash
32506 pts/800:00:04 emacs
33609 pts/800:00:00 chromium
33630 pts/800:00:00 chromium
33631 pts/800:00:00 chromium
3
d be added to /etc/environment:
LIBVA_DRIVERS_PATH=/usr/lib/x86_64-linux-gnu/dri LIBVA_DRIVER_NAME=iHD
I can't vouch for any of this, especially the last part.
error messages
yoda-mini [rramesh] 43 > fgrep EE /var/log/Xorg.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 3134.273] (EE) open /dev/dri/card0: No such file or directory
[ 3134.273] (EE) open /dev/dri/card0: No such file or directory
[ 3134.
[rramesh] 43 > fgrep EE /var/log/Xorg.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 3134.273] (EE) open /dev/dri/card0: No such file or directory
[ 3134.273] (EE) open /dev/dri/card0: No such file or directory
[ 3134.274] (EE) Unable to find a va
stefan djurdjanovic wrote:
> Hi,
>
> i have problem with DRI Missing file.
I doubt in the previous post you found your answer, better post what is your
video card.
DRIVER
check if your video driver is configured properly
check what it says regarding DRI in the log file
[77
Hi,
i have problem with DRI Missing file.
Hi,
I have problem with DRI missing file. I find this solution:
I encountered an issue with the same symptoms (no /dev/dri so X won't
start) which I believe is actually caused by a udev update. I had upgraded
from udev-171 to udev-181 (and several other packages), and when I
rebooted, X f
Hi,
as mentioned in earlier thread,
(EE) AIGLX error: failed to open
/usr/X11R6/lib64/modules/dri/fglrx_dri.so,
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared
object file: No such file or directory]
When I ln /usr/lib64/dri/fglrx_dri.so to /usr/X11R6/lib64/modules/dri
it
On Dec 10, 2013 at 14:54, Chris Bannister wrote:
> On Sat, Dec 07, 2013 at 08:06:42PM +0100, Ralf Mardorf wrote:
> >
> > Sometimes there are insane hard dependencies, but what's bad with those
> > dependencies? Take a look at the modules compiled into the default
> > kernel, most modules are unne
On Tue, Dec 10, 2013 at 04:20:57PM +0100, Ralf Mardorf wrote:
> On Wed, 2013-12-11 at 01:54 +1300, Chris Bannister wrote:
> > On Sat, Dec 07, 2013 at 08:06:42PM +0100, Ralf Mardorf wrote:
> > >
> > > Sometimes there are insane hard dependencies, but what's bad with those
>
On Wed, 2013-12-11 at 01:54 +1300, Chris Bannister wrote:
> On Sat, Dec 07, 2013 at 08:06:42PM +0100, Ralf Mardorf wrote:
> >
> > Sometimes there are insane hard dependencies, but what's bad with those
^^^
> > dependencies? Take
On Sat, Dec 07, 2013 at 08:06:42PM +0100, Ralf Mardorf wrote:
>
> Sometimes there are insane hard dependencies, but what's bad with those
> dependencies? Take a look at the modules compiled into the default
> kernel, most modules are unneeded on your machine ;).
Huh? That is not insane at all! It
On Sat, Dec 07, 2013 at 06:06:09PM +0200, Ivan Kovnatsky wrote:
> When trying to remove either libdrm-nouveau2 or libdrm-radeon1 I obviously get
> a message that this required packages. Thing is I really do not need them.
> What options do I have to get rid of them like normally using apt/aptitude
On Sat, 2013-12-07 at 18:06 +0200, Ivan Kovnatsky wrote:
> libgl1-mesa-dri
http://packages.debian.org/wheezy/libgl1-mesa-dr
That are hard dependencies, you could take a look if you could recompile
it without the unneeded parts, or test if a dummy package shouldn't
break it. Sometimes t
On 2013-12-07 17:06 +0100, Ivan Kovnatsky wrote:
> I have blindly (I guess/installed and forgot about it) installed on
> my laptop these packages as requirements to libgl1-mesa-dri: libdrm-intel1,
> libdrm-nouveau2, libdrm-radeon1. OK, first one libdrm-intel1 is what I real
Hi Guys! I have blindly (I guess/installed and forgot about it) installed on
my laptop these packages as requirements to libgl1-mesa-dri: libdrm-intel1,
libdrm-nouveau2, libdrm-radeon1. OK, first one libdrm-intel1 is what I really
need:
00:02.0 VGA compatible controller: Intel Corporation
xorg.conf file present in
/etc/X11 the ending lines of the Xorg.0.log file are as follows:
[ 91799.286] drmOpenDevice: node name is /dev/dri/card0
[ 91799.292] drmOpenByBusid: Searching for BusID pci::02:00.0
[ 91799.292] drmOpenDevice: node name is /dev/dri/card0
[ 91799.296] drmOpenByBusid
On 2010-11-20 21:28 +0100, Borden Rhodes wrote:
> Once again, Sven, I owe you my sanity. I've read that Debian was still
> looking into framebuffer issues with Intel, whether to keep UMS or
> migrate to KMS. Is that debate related to the DRI/shadow issue?
Well, yes. The attem
Once again, Sven, I owe you my sanity. I've read that Debian was still
looking into framebuffer issues with Intel, whether to keep UMS or
migrate to KMS. Is that debate related to the DRI/shadow issue?
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subje
#Option "NoAccel" # []
> #Option "SWcursor" # []
> #Option "ColorKey" #
> #Option "CacheLines"#
> #Option "Dac6Bit" #
I've spent about two hours in the man pages and on Google trying to
figure this one out with no success. I can't get DRI, and therefore
hardware acceleration, working. Relevant info:
# dmesg | grep agp
[0.737743] Linux agpgart interface v0.103
[0.737941] agpgart-intel :00:0
On Sun, Jan 31, 2010 at 01:20, Klistvud wrote:
> Dne, 31. 01. 2010 03:52:01 je Kelly Clowers napisal(a):
>>
>> AMD has published all 2d and 3d info for r100 through r700 (r800/5xxx is
>> in the pipeline):
>> http://www.x.org/docs/AMD/
>
> I stand corrected. That's like music to my ears.
>
>> DRI2/
Dne, 31. 01. 2010 03:52:01 je Kelly Clowers napisal(a):
AMD has published all 2d and 3d info for r100 through r700 (r800/5xxx
is
in the pipeline):
http://www.x.org/docs/AMD/
I stand corrected. That's like music to my ears.
DRI2/KMS is theoretically usable with 2.6.32, Mesa 7.7, XServer 1.7
On Sat, Jan 30, 2010 at 16:00, Klistvud wrote:
> Dne, 30. 01. 2010 16:32:02 je Joost Kraaijeveld napisal(a):
>>
>> Hi,
>>
>> Does the radeonhs driver support acceleration?
>
> That's a question I'm very much interested in too. I've always been under
> the impression that the radeon and radeonhd dr
Dne, 30. 01. 2010 16:32:02 je Joost Kraaijeveld napisal(a):
Hi,
Does the radeonhs driver support acceleration?
That's a question I'm very much interested in too. I've always been
under the impression that the radeon and radeonhd drivers only support
basic 2D acceleration, and only for some
DRI.
(II) RADEONHD(0): [agp] You may want to make sure the agpgart kernel
module
And further in the file:
(II) AIGLX: Screen 0 is not DRI2 capable
(II) AIGLX: Screen 0 is not DRI capable
But the agpart is loaded:
panoramix:/home/jkr# lsmod | grep agp
amd64_agp 6814 0
agpgart
On Fri, Apr 24, 2009 at 10:20:32 +0800, jida...@jidanni.org wrote:
> I wonder how to stop this error.
> (EE) AIGLX error: dlopen of /usr/lib/dri/swrast_dri.so failed
> (/usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or
> directory)
> (EE) GLX: could no
On Fri,24.Apr.09, 10:20:32, jida...@jidanni.org wrote:
> I wonder how to stop this error.
> (EE) AIGLX error: dlopen of /usr/lib/dri/swrast_dri.so failed
> (/usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or
> directory)
> (EE) GLX: could not load so
I wonder how to stop this error.
(EE) AIGLX error: dlopen of /usr/lib/dri/swrast_dri.so failed
(/usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or
directory)
(EE) GLX: could not load software renderer
(II) GLX: no usable GL providers found for screen 0
I don't u
installed. I'm sorry in fact because I forgot about
>> > this thread: I actually found what was the problem. ATI cards need an
>> > additional option in xorg.conf in the section "Device":
>> >
>> > Option "DRI"
>>
y found what was the problem. ATI cards need an
> > additional option in xorg.conf in the section "Device":
> >
> > Option "DRI"
> >
> > For those who would seek for the same information, I attach my xorg.conf
> > to this email.
xorg.conf in the section "Device":
>
> Option "DRI"
>
> For those who would seek for the same information, I attach my xorg.conf to
> this email. As latest xorg now uses evdev instead of kbd, I attach my working
> evdev config un hal. I don't know i
t; the driver you are using. This means, the latest 3D drivers usually use
> the latest mesa libraries.
Yes, all of these is installed. I'm sorry in fact because I forgot about this
thread: I actually found what was the problem. ATI cards need an additional
option in xorg.conf in th
On Mon, 2 Feb 2009 19:14:36 +0100
Thomas Preud'homme wrote:
[snip]
>
> glxgears
> 1008 frames in 5.0 seconds = 201.471 FPS
> 1226 frames in 5.0 seconds = 245.142 FPS
> 1237 frames in 5.0 seconds = 247.393 FPS
> 1236 frames in 5.0 seconds = 247.034 FPS
>
> If I play a game or a 3D screensaver i
) like a charm.
glxinfo | grep render gives :
direct rendering: Yes
I also have :
egrep "^.*Load.*(m|M)odule.*radeonhd" /var/log/Xorg.0.log
(II) LoadModule: "radeonhd"
(II) Loading /usr/lib/xorg/modules/drivers//radeonhd_drv.so
and
egrep "^.*Load.*(m|M)odule.*dri&quo
d not map ring
> (EE) RADEON(0): [agp] AGP failed to initialize. Disabling the DRI.
> (II) RADEON(0): [agp] You may want to make sure the agpgart kernel
^^
> module is
Florian Kulzer wrote:
On Fri, Nov 07, 2008 at 19:41:38 -0800, Jason C. Wells wrote:
I'm having trouble with DRI on my Radeon 9600 Pro.
(II) RADEON(0): [agp] Mode 0x1f000207 [AGP 0x1002/0x5833; Card
0x1002/0x4150]
(II) RADEON(0): [agp] 8192 kB allocated with handle 0x0001
(II) RAD
On Fri, Nov 07, 2008 at 19:41:38 -0800, Jason C. Wells wrote:
> I'm having trouble with DRI on my Radeon 9600 Pro.
[...]
> [EMAIL PROTECTED] ~ $ uname -a
> Linux w17 2.6.26-1-686 #1 SMP Wed Sep 10 16:46:13 UTC 2008 i686 GNU/Linux
>
> [EMAIL PROTECTED] ~ $ dmesg
On Fri Nov 7 19:41 , "Jason C. Wells" sent:
I'm having trouble with DRI on my Radeon 9600 Pro. From everything that
I have read, it should be working. I don't really know what to ask,
except to ask, "Can you help me?"
These are the errors from Xorg.0.log
(
I'm having trouble with DRI on my Radeon 9600 Pro. From everything that
I have read, it should be working. I don't really know what to ask,
except to ask, "Can you help me?"
These are the errors from Xorg.0.log
(EE) RADEON(0): [agp] Could not map ring
(EE) RADEON(0):
> >
> > > [MIS A JOUR] libgl1-mesa-dri 7.0.3-6 -> 7.2-1
> > > [MIS A JOUR] libgl1-mesa-glx 7.0.3-6 -> 7.2-1
> > > [MIS A JOUR] xserver-xorg 1:7.3+18 -> 1:7.4~4
> > > [MIS A JOUR] xserver-xorg-core 2:1.4.2-7 -> 2:1.5.2-1
> > > [MIS A JOUR]
The Friday 24 October 2008 04:09:07 Amit Uttamchandani, you wrote :
> > Yeah I did upgrade the xorg and mesa to be able to install radeonhd. Here
> > are the package that have been upgraded :
> >
> > [MIS A JOUR] libgl1-mesa-dri 7.0.3-6 -> 7.2-1
> > [MIS A JOUR]
>
> Yeah I did upgrade the xorg and mesa to be able to install radeonhd. Here are
> the package that have been upgraded :
>
> [MIS A JOUR] libgl1-mesa-dri 7.0.3-6 -> 7.2-1
> [MIS A JOUR] libgl1-mesa-glx 7.0.3-6 -> 7.2-1
> [MIS A JOUR] xserver-xorg 1:7.3+18 ->
The Thursday 23 October 2008 20:32:58 Amit Uttamchandani, you wrote :
> > I'd like to know if you experienced same things with same driver *and*
> > other drivers. If you do experience the same problem, then I'd like to
> > disable the loading of dri in xorg but unfo
>
> I'd like to know if you experienced same things with same driver *and* other
> drivers. If you do experience the same problem, then I'd like to disable the
> loading of dri in xorg but unfortunetely neither commenting Load dri (because
> now xorg know what to load
Greetings,
I have a xorg crashing when launching any opengl apps (a video in vlc or a
game). Here is what changed to have this behaviour :
I have a Radeon Mobility X1600 which uses the r500 chipset. I saw in the
radeonhd changelog that version 1.2.2 now supports DRI for r500 and r600
readon
Using the linux-image-2.6.24-1-686 version 2.6.24-5 which is in
unstable (sid) solves the problem.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
It does seem to be this incompatibility between i915,drm modules and the
kernel itself. I have downloaded and compiled the DRM modules and got further,
but now there seems to be another problem along the same lines as what users of
other distributions have faced and solved:
http://forums.fedo
I recently updated lenny to pick up the new 2.6.24 kernel. Since then DRI is
not working for me:
(II) intel(0): [drm] DRM interface version 1.0
(II) intel(0): [drm] drmSetBusid failed (8, pci::00:02.0), Permission denied
(EE) intel(0): [dri] DRIScreenInit failed. Disabling DRI.
I've ch
Hi
I built DRI from source since I needed some very recent fix. I don't
know how long it takes for new code to reach debian unstable/testing
repositories, which are the ones I'm using. The installation is as
simple as copying the compiled libraries to the relevant places, so I
co
On Wed July 11 2007 20:57, David Fox wrote:
> > It is worth a try; if that doesn't work then you can also try to run the
> > nvidia installer script again. When I was still using the nvidia
> > installer I had to run it again whenever xserver-xorg-core was upgraded.
>
> I finally got around to tryi
It is worth a try; if that doesn't work then you can also try to run the
nvidia installer script again. When I was still using the nvidia
installer I had to run it again whenever xserver-xorg-core was upgraded.
I finally got around to trying this again ;).
No go on the reinstall, in fact, it
On Sun, Jun 24, 2007 at 13:56:44 -0700, David Fox wrote:
> On 6/24/07, Florian Kulzer wrote:
[...]
>> The Xorg glx module is loaded instead of the one from nvidia. How did
>> you install the nvidia driver, from the Debian packages or with the
>> installer from nvidia's website?
>
> The driver cou
On 6/24/07, Florian Kulzer <[EMAIL PROTECTED]> wrote:
First of all, I would quickly try if the crash on shutdown goes away
when you use the "nv" or the "vesa" driver. (Just to make sure that we
only have to worry about the nvidia driver and nothing else.)
I guess I could try that.
The Xo
David Fox wrote:
Hello, when I was running etch I had the nvidia driver on a Geforce FX
5200 running just fine.
I've done a recent (as of a few days ago) dist-upgrade to lenny and
the DRI no longer works.
Additionally, I'm seeing a stack backtrace and a sig11 from the X
On Sun, Jun 24, 2007 at 08:36:12 -0700, David Fox wrote:
> Hello, when I was running etch I had the nvidia driver on a Geforce FX
> 5200 running just fine.
>
> I've done a recent (as of a few days ago) dist-upgrade to lenny and
> the DRI no longer works.
>
> Additi
Hello, when I was running etch I had the nvidia driver on a Geforce FX 5200
running just fine.
I've done a recent (as of a few days ago) dist-upgrade to lenny and the DRI
no longer works.
Additionally, I'm seeing a stack backtrace and a sig11 from the X server on
shutdown. I j
Jacob S wrote:
> Howdy List,
>
> I'm trying to setup Debian Etch on a new Dell Inspiron 1501. X is
> working great so far, except that I cannot get DRI enabled. I can
> modprobe radeon and tell the xorg.conf to use the radeon driver, but
> glxinfo still reports no D
On Tue, Jun 05, 2007 at 08:42:32PM -0700, chris wrote:
> On Tue, Jun 05, 2007 at 09:55:50PM -0500, John Hasler wrote:
> > Christopher Nelson writes:
> > > But the module will taint the kernel. And, if you're using unstable, the
> > > driver will require you to mess with holds of x.org and/or use a
On Tue, Jun 05, 2007 at 09:55:50PM -0500, John Hasler wrote:
> Christopher Nelson writes:
> > But the module will taint the kernel. And, if you're using unstable, the
> > driver will require you to mess with holds of x.org and/or use a
> > (further) illegal hack.
>
> What's illegal here?
Potenti
Christopher Nelson writes:
> But the module will taint the kernel. And, if you're using unstable, the
> driver will require you to mess with holds of x.org and/or use a
> (further) illegal hack.
What's illegal here?
--
John Hasler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
On Tue, Jun 05, 2007 at 06:12:58PM -0500, Jacob S wrote:
> Howdy List,
>
> I'm trying to setup Debian Etch on a new Dell Inspiron 1501. X is
> working great so far, except that I cannot get DRI enabled. I can
> modprobe radeon and tell the xorg.conf to use the radeon driver,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Howdy List,
I'm trying to setup Debian Etch on a new Dell Inspiron 1501. X is
working great so far, except that I cannot get DRI enabled. I can
modprobe radeon and tell the xorg.conf to use the radeon driver, but
glxinfo still reports n
On Tue, 2007-05-29 at 17:19 +0200, Georg Heinrich wrote:
> Yes, that did it.
> Strange enough, the touchpad still works!
> Thank you very much,
You probably need to rebuild synaptics from source (and file a debian
bug report). The touchpad is ADB or USB ? The ADB one just works fine
without, but t
Benjamin Herrenschmidt ([EMAIL PROTECTED]) wrote on Tue, 29 May
2007 09:51:57 +1000:
>> Backtrace:
>> 0: /usr/bin/X(xf86SigHandler+0x94) [0x1008eb98]
>> 1: [0x100374]
>> 2: [0x7fcac80c]
>> 3: /usr/lib/xorg/modules/libxaa.so(XAAFillMono8x8PatternRectsScreenOrigin
>> +0xdc) [0xf75301c]
>> 4: /usr/li
> Backtrace:
> 0: /usr/bin/X(xf86SigHandler+0x94) [0x1008eb98]
> 1: [0x100374]
> 2: [0x7fcac80c]
> 3: /usr/lib/xorg/modules/libxaa.so(XAAFillMono8x8PatternRectsScreenOrigin
> +0xdc) [0xf75301c]
> 4: /usr/lib/xorg/modules/libxaa.so(XAAPaintWindow+0x52c) [0xf761090]
> 5: /usr/bin/X [0x10138684]
> 6:
On Mon, May 28, 2007 at 11:00:54 +0200, Georg Heinrich wrote:
> Hello,
>
> I have received some useful hints on how to post (thanks to Roger and
> Florian), that's why I give the information again:
>
> ===
>
> Hardware:
> Apple Powe
15] -1 0 0x9100 - 0x91ff (0x100) MX[B](B)
[16] -1 0 0x - 0x (0x1) IX[B]
[17] -1 0 0x - 0x00ff (0x100) IX[B]
(II) LoadModule: "bitmap"
(II) Reloading /usr/lib/xorg/modules/fonts/libbitmap.so
(II) Loading font Bitm
On 05/27/2007 09:28 AM, Georg Heinrich wrote:
Mumia W.. ([EMAIL PROTECTED]) wrote on Sat, 26
May 2007 23:15:29 -0500:
On 05/26/2007 04:07 PM, Georg Heinrich wrote:
Mumia W.. ([EMAIL PROTECTED]) wrote on Sat, 26
May 2007 13:17:45 -0500:
Start reconfiguring xorg: "dpkg-reconfigure xserver-xorg
Mumia W.. ([EMAIL PROTECTED]) wrote on Sat, 26
May 2007 23:15:29 -0500:
>On 05/26/2007 04:07 PM, Georg Heinrich wrote:
>> Mumia W.. ([EMAIL PROTECTED]) wrote on Sat, 26
>> May 2007 13:17:45 -0500:
>>
>>> Start reconfiguring xorg: "dpkg-reconfigure xserver-xorg"
>>>
>>> Then select the VESA driver
Florian Reitmeir ([EMAIL PROTECTED]) wrote on Sun, 27 May 2007
01:23:57 +0200:
>please post the output from:
>
>uname -a
Linux gh-mob-lx 2.6.18-4-powerpc #1 Mon Mar 26 09:11:14 CEST 2007 ppc
GNU/Linux
>lspci
Is attached (lspci.out)
>and your Xorg.0.log
Is attached, too.
Thanks.
G. Heinri
On 05/26/2007 04:07 PM, Georg Heinrich wrote:
Mumia W.. ([EMAIL PROTECTED]) wrote on Sat, 26
May 2007 13:17:45 -0500:
Start reconfiguring xorg: "dpkg-reconfigure xserver-xorg"
Then select the VESA driver when it asks you.
I do not get this option.
Thanks anyway.
G. Heinrich
Install xs
On Sat, 26 May 2007, Georg Heinrich wrote:
> I get this error message after startup at the login prompt.
thats not clearly an error.
please post the output from:
uname -a
lspci
and your Xorg.0.log
> Any hint is welcome.
> Thanks in advance,
--
Florian Reitmeir
--
To UNSUBSCRIBE, email to [
Florian Kulzer ([EMAIL PROTECTED]) wrote on Sat, 26 May 2007
20:07:27 +0200:
>The AIGLX message should go away if you put this in your
>/etc/X11/xorg.conf:
>
>Section "ServerFlags"
> Option "AIGLX" "false"
>EndSection
>
Ok, things changed. No X11 fails with
Fatal server error:
Caug
Mumia W.. ([EMAIL PROTECTED]) wrote on Sat, 26
May 2007 13:17:45 -0500:
>> I get this error message after startup at the login prompt.
>> [...]
>>
>> I don't need dri, I don't even need glx, I just want to have X running
>> at the login prompt.
>
Sudev Barar ([EMAIL PROTECTED]) wrote on Sat, 26 May 2007 22:26:59 +0530:
>You will be able to run everything. First append the following in the
>bootline of your kernel in /boot/grub/menu.lst
>
>vga=771
>
There is no /boot/grub/ directory.
Thanks anyway.
G. Heinrich
--
To UNSUBSCRIBE, e
On 05/26/2007 10:34 AM, Georg Heinrich wrote:
Hello,
I get this error message after startup at the login prompt.
[...]
I don't need dri, I don't even need glx, I just want to have X running
at the login prompt.
Any hint is welcome.
Thanks in advance,
G. Heinrich
Start rec
; dpkg-reconfigure xserver-xorg
> and disabled either dri or glx or both, to no avail. X just doesn't
> start at the login, with various error messages.
>
> I'm so desperate that I even consider to recompile the xserver-xorg
> package and configure it without dri. Ho
On 26/05/07, Georg Heinrich <[EMAIL PROTECTED]> wrote:
I'm so desperate that I even consider to recompile the xserver-xorg
package and configure it without dri. However I didn't figure out how to
do that. I got the source with
apt-get source xserver-xorg
and am stuck
Hello,
I get this error message after startup at the login prompt.
The HW is:
Apple PowerBook G4 12" (PowerBook 6,8) 1,5 GHz
NVidia GeForce FX Go5200
I have already tried
dpkg-reconfigure xserver-xorg
and disabled either dri or glx or both, to no avail. X just doesn't
st
On Monday 02 April 2007, [EMAIL PROTECTED] wrote:
> > Has anybody gotten direct rendering to work with the legacy mach64
> > Rage Pro Mobility card .. with the etch version of Xorg?
> >
> > The ATI web site does not provide drivers for this antique so I'll
> > have to use the one that's provided wi
On Sun, Apr 01, 2007 at 10:41:40PM EDT, Mark Grieveson wrote:
> > > I did manage to get this working with a former linux kernel image of
> > > Etch, but I've had no luck with the more recent kernel image of
> > > Etch.
>
> > Would that be 2.4.27?
>
> I got direct rendering, with the aforement
> > I did manage to get this working with a former linux kernel image of
> > Etch, but I've had no luck with the more recent kernel image of
> > Etch.
> Would that be 2.4.27?
I got direct rendering, with the aforementioned driver, running on
2.6.16-2. I currently have 2.6.18-4, and for some
On Sun, 01 Apr 2007 18:31:48 -0400
cga2000 <[EMAIL PROTECTED]> wrote:
> On Sun, Apr 01, 2007 at 06:01:56PM EDT, Mark Grieveson wrote:
> > On Sun, 2007-04-01 at 13:01 -0400, cga2000 wrote:
> > > Has anybody gotten direct rendering to work with the legacy mach64
> > > Rage Pro Mobility card .. with
On Sun, Apr 01, 2007 at 06:01:56PM EDT, Mark Grieveson wrote:
> On Sun, 2007-04-01 at 13:01 -0400, cga2000 wrote:
> > Has anybody gotten direct rendering to work with the legacy mach64
> > Rage Pro Mobility card .. with the etch version of Xorg?
> >
> > The ATI web site does not provide drivers fo
On Sun, 2007-04-01 at 13:01 -0400, cga2000 wrote:
> Has anybody gotten direct rendering to work with the legacy mach64
> Rage Pro Mobility card .. with the etch version of Xorg?
>
> The ATI web site does not provide drivers for this antique so I'll
> have to use the one that's provided with Xorg.
On Sun, Apr 01, 2007 at 01:54:15PM EDT, Hans du Plooy wrote:
> On Sun, 2007-04-01 at 13:01 -0400, cga2000 wrote:
> > Has anybody gotten direct rendering to work with the legacy mach64 Rage
> > Pro Mobility card .. with the etch version of Xorg?
> >
> > The ATI web site does not provide drivers for
On Sun, 2007-04-01 at 13:01 -0400, cga2000 wrote:
> Has anybody gotten direct rendering to work with the legacy mach64 Rage
> Pro Mobility card .. with the etch version of Xorg?
>
> The ATI web site does not provide drivers for this antique so I'll have
> to use the one that's provided with Xorg.
Has anybody gotten direct rendering to work with the legacy mach64 Rage
Pro Mobility card .. with the etch version of Xorg?
The ATI web site does not provide drivers for this antique so I'll have
to use the one that's provided with Xorg.
$ lspci
[..] ATI Technologies Inc Rage Mobility P/M AGP 2
vers doesn't allow composite.
>
>> I have an Ati mobility radeon X700 and I didn't manage to activate
>> composite with those drivers. BUT, on january, debian released new
>> mesa glx and dri packages which supports 3D hardware acceleration for
>
1 - 100 of 521 matches
Mail list logo
