On Wed, Aug 25, 2010 at 11:06:09PM +, s. keeling wrote:
> Nick Lidakis :
> > On Sat, Jul 24, 2010 at 02:13:08AM +0200, Thomas Amm wrote:
> > > Am 24.06.2010 20:06, schrieb Nick Lidakis:
> > > >
> > > > I figured, these days, getting to a 2d desktop with a 2 year old
> > > > video card would n
Nick Lidakis :
> On Sat, Jul 24, 2010 at 02:13:08AM +0200, Thomas Amm wrote:
> > Am 24.06.2010 20:06, schrieb Nick Lidakis:
> > >
> > > I figured, these days, getting to a 2d desktop with a 2 year old
> > > video card would not cause a machine to lock hard. Although,I am
> > > on unstable. You pa
On Sat, Jul 24, 2010 at 02:13:08AM +0200, Thomas Amm wrote:
> Am 24.06.2010 20:06, schrieb Nick Lidakis:
> >
> > I figured, these days, getting to a 2d desktop with a 2 year old video card
> > would not cause a machine to lock hard. Although,I am on unstable. You pays
> > your money
> > and you t
Am 24.06.2010 20:06, schrieb Nick Lidakis:
>
> I figured, these days, getting to a 2d desktop with a 2 year old video card
> would not cause a machine to lock hard. Although,I am on unstable. You pays
> your money
> and you takes your chances...
>
> Thanks for the suggestions.
Are, by any chanc
Hi,
Due to some unknown error to me, having quit my malfunctioning X, my
startx can't get into vt07 any more, but only into vt08.
I.e., CTRL-ALT-F7 gives me a black text screen, while CTRL-ALT-F8 is my
started X.
startx -- :1
starts xorg in vt08 as well. If the vt08 is occupied, t
; Cheers,
> Kelly Clowers
>
>
Yes. In any case, as the effect occasionally happens even before X is
started, it can't be anything to do with the xorg driver. On the other
hand, it doesn't happen with any kernel prior to 2.6.32-5-686, which
also causes the small font effect, so
On Wed, Jul 14, 2010 at 06:43, Wolodja Wentland
wrote:
>
> ... or just disable KMS (and yes it sounds like a KMS issue). You can
> find details on [1].
Seems that his KMS and DRI are already disabled.
>drmOpenDevice: node name is /dev/dri/card0
>[drm] failed to load kernel module "radeon"
>(EE)
; without X! So I don't think the problem is with xorg. I'm now using an
> > > installed version of stable and that has no crashes, so it seems to be
> > > something about how the latest kernel interacts with my system. There
> > > are no other linux-images around
On Wed, Jul 14, 2010 at 08:58 -0400, Stephen Powell wrote:
> On Wed, 14 Jul 2010 06:39:29 -0400 (EDT), Anthony Campbell wrote:
> >
> > After some more experimenting, I've found that it also happens even
> > without X! So I don't think the problem is with xorg.
On Wed, 14 Jul 2010 06:39:29 -0400 (EDT), Anthony Campbell wrote:
>
> After some more experimenting, I've found that it also happens even
> without X! So I don't think the problem is with xorg. I'm now using an
> installed version of stable and that has no crashes, so
among Debian users and developers:
> http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
After some more experimenting, I've found that it also happens even
without X! So I don't think the problem is with xorg. I'm now using an
installed version of stable and that has
On Mi, 14 iul 10, 06:58:24, Anthony Campbell wrote:
> At the moment I have a blank xorg.conf but I've also used one which has
> ati as the driver.
>
> Here is the log:
> (II) RADEON: Driver for ATI Radeon chipsets:
You need not mess with nouveau, because you have an ATI card and are
using the
ution to this? Any way to find a slightly earlier kernel?
> > (unfortunately I deleted the others)
>
> What driver are you using for Xorg? You might also want to post the full
> /var/log/Xorg.0.log
>
> Regards,
> Andrei
> --
> Offtopic discussions among Debian users
inor issue.
>
> I found some advice here to blacklist nouveau and put a file in
> /etc/modprobe.d with "options nouveau modeset=0" but no help.
>
> Is there any solution to this? Any way to find a slightly earlier kernel?
> (unfortunately I deleted the others)
What d
I upgraded the kernel to 2.6.32-5-686 and now X starts and works for a
bit but then starts flickering and is unusable. This is on a Thinkpad
Z61M.
The text terminals now have small text but that is a minor issue.
I found some advice here to blacklist nouveau and put a file in
/etc/modprobe.d w
ch with Xorg's ones.
> Out fo curiosity, I tried an
> Ubuntu live disc (10.04) with the Radeon 3450 installed. The machien
> locks up as well.
Wow... that could be pointing to "xorg" server or just a faulty card :-?
> Also, I dug out an old Saphire 256MB X1300 card t
ug out an old Saphire 256MB X1300 card that I had in a junk box. All
is well: 2d, 3d, s2ram. No lockups using 3d xscreensaver, like I had with the
Dell X1300. Ubuntu live works great. So, maybe the Dell cards
really do funny things.
> With open drivers and KMS, Xorg should work "out-of
On Wed, 23 Jun 2010 18:06:23 -0400, Nick Lidakis wrote:
> On Wed, Jun 23, 2010 at 01:36:10PM +, Camaleón wrote:
>> Have you tried with the proprietary driver? Just for testing purposes.
>
> No. I really don't want to use a closed driver. I purchased this card
> be
On Wed, Jun 23, 2010 at 01:36:10PM +, Camaleón wrote:
> Have you tried with the proprietary driver? Just for testing purposes.
No. I really don't want to use a closed driver. I purchased this card because
I read (Xorg wiki) that this slightly older tech was well supported for a 2D
On Tue, 22 Jun 2010 21:52:21 -0400, Nick Lidakis wrote:
> I seem to be having severe issues in getting a Radeon HD 3450 working
> with Xorg and Debian.
(...)
Have you tried with the proprietary driver? Just for testing purposes.
Another thing to try could be using KMS and no &quo
I seem to be having severe issues in getting a Radeon HD 3450 working with
Xorg and Debian.
System is:
latest Debian unstable
kernel 2.6.32-4-686
latest Xorg included in Debian unstable 7.5
xserver-xorg-video-radeon1:6.13.0-2
xserver-xorg-video-radeonhd
* From: Stephen Powell
* Date: Wed, 26 May 2010 17:41:29 -0400 (EDT)
> Please consider a reinstall first. Who knows how many other hidden
> problems are lurking in your system.
The freshly installed Squeeze is working almost as well
as Lenny did before Xmas. The Squeeze system rout
OK, I have created xorg.conf, but no change at all.
I'm attaching xorg.conf
Here is the glxgears output:
$ glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
20017 frames in 5.0 seconds = 4003.267 FPS
20048 frames in
From: Stephen Powell
Date: Tue, 08 Jun 2010 12:50:05 -0400 (EDT)
> My guess is that this problem [the video mode error
> message] was solved by a newer driver which got
> installed with the fresh install.
The other system which provided the replacement
monitor isn't Linux. On that system
Jan Hlodan wrote:
> /etc/X11/XF86Config
this is not used anymore
you'll have to create an xorg.conf file and try your luck there
try putting there specific options for the nvidia driver (proprietary or
not). I'm using intel here but installed recently kde4.4 with nvidia and
it's working fine. I t
On 8 Jun 2010, at 23:03, deloptes wrote:
Jan Hlodan wrote:
I set up Nvidia driver according to
http://wiki.debian.org/NvidiaGraphicsDrivers I used nvidia packages
from
Sid (when I installed Squeeze, 6 months ago). I'm attaching Xorg log.
Thank you for help!
Regards,
Jan Hlodan
Jan Hlodan wrote:
>
> I set up Nvidia driver according to
> http://wiki.debian.org/NvidiaGraphicsDrivers I used nvidia packages from
> Sid (when I installed Squeeze, 6 months ago). I'm attaching Xorg log.
> Thank you for help!
> Regards,
>
> Jan Hlodan
try removin
e hidden directories with
> dozens of hidden files in total. I can't help but wonder
> about the wisdom. A hidden file disabling X with no
> indication in Xorg.0.log seems bad.
To quote chief engineer Montgomery Scott from the movie
Star Trek III: The Search for Spock,
"The
of hidden files in total. I can't help but wonder
about the wisdom. A hidden file disabling X with no
indication in Xorg.0.log seems bad.
Thanks for the help Stephen,
... Peter E.
--
Carnot is down, waiting for a disk replacement.
Personal site work
On Tue, 08 Jun 2010 13:51:18 +0200, Jan Hlodan wrote:
> after upgrading KDE to 4.4, xorg process takes 50 - 90% of CPU and makes
> desktop really slow.
> I didn't find anything relevant, so if you can take a look at these
> outputs and give me some solution, I'll be ver
Hello,
after upgrading KDE to 4.4, xorg process takes 50 - 90% of CPU and
makes desktop really slow.
I didn't find anything relevant, so if you can take a look at these
outputs and give me some solution, I'll be very grateful.
$ uname -a
Linux napsugaram 2.6.32-trunk-686 #1 SMP Sun Ja
gt; Modes "1024x768" "800x600" "640x480"
> EndSubSection
> EndSection
>
> Section "ServerLayout"
> Identifier "Default Layout"
> Screen "Default Screen"
> EndSect
Modes "1024x768" "800x600" "640x480"
EndSubSection
EndSection
Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
EndSection
#Section "ServerFlags"
#
x27;re using a standard 15-pin
analog VGA connector on the back of your computer and a standard
analog monitor. If not, please provide the specifics.
Also, please post the /etc/X11/xorg.conf file that you used
and the resulting /var/log/Xorg.0.log file that resulted when
the server stayed running.
P
From: Stephen Powell
Date: Fri, 21 May 2010 11:21:16 -0400 (EDT)
>append="acpi=off"
> in your /etc/lilo.conf file.
X still exits with these lines.
SELinux: Disabled on system, not enabling in X server
waiting for X server to shut down.
This message from the monitor itself appears brief
On Sat, 22 May 2010 03:13:06 -0400 (EDT), Andrei Popescu wrote:
> On Sat,22.May.10, 00:55:34, David Jardine wrote:
>> Stephen Powell wrote:
>>>
>>> I see. All comments. Which is about the same as not having one. Hmm.
>>
>> Or is it? I'm as baffl
On Sat,22.May.10, 00:55:34, David Jardine wrote:
> >
> > I see. All comments. Which is about the same as not having one. Hmm.
>
> Or is it? I'm as baffled as anyone alse by xorg configuration, but
> can't such a file, blank though it be, override some othe
ious
> > experiments. Hasn't changed since the log was
> > recorded. Should be visible here.
> >
> > http://carnot.pathology.ubc.ca/dalton.xorg.conf
> >
>
> I see. All comments. Which is about the same as not having one. Hmm.
Or is it? I&#x
On Fri,21.May.10, 12:22:22, peasth...@shaw.ca wrote:
> From: Andrei Popescu
> Date: Fri, 21 May 2010 22:03:19 +0300
> > # echo 'APT::Default-Release "squeeze";' >> /etc/apt/apt.conf
>
> Somehow I had the impression that the order of the
> sources would prioritize them.
Yes (or at least that's w
From: Andrei Popescu
Date: Fri, 21 May 2010 22:03:19 +0300
> # echo 'APT::Default-Release "squeeze";' >> /etc/apt/apt.conf
Somehow I had the impression that the order of the
sources would prioritize them.
Thanks,... Peter E.
--
Google "pathology workshop".
In ETHNO click h
On Fri, 21 May 2010 14:55:52 -0400 (EDT), Peter Easthope wrote:
> Stephen Powell wrote:
>> If you need
>> instructions for how to pull in the Sid kernel without upgrading
>> your whole system ...
>
> As far as I know this line should be appended to /etc/apt/sources.list
> deb http://debian.ore
On Fri,21.May.10, 11:55:52, peasth...@shaw.ca wrote:
> > If you need
> > instructions for how to pull in the Sid kernel without upgrading
> > your whole system ...
>
> As far as I know this line should be appended to /etc/apt/sources.list
> deb http://debian.oregonstate.edu/debian/ sid main
From: Stephen Powell
Date: Fri, 21 May 2010 14:06:52 -0400 (EDT)
> As I explained in another post, yes, it is in Sid. If you need
> instructions for how to pull in the Sid kernel without upgrading
> your whole system to Sid, let me know and I can provide that.
> Also, you might try disabling
On Fri, 21 May 2010 13:07:26 -0400 (EDT), Peter Easthope wrote:
>
> Runs OK. These lines appear on the console.
> xserver-xorg-video-intel 2:2.9.1-3
> ...
:-)
> update-initramfs: Generating /boot/initrd.img-2.6.32-3-686
>
This should also have caused lilo
environment
> changes.
Runs OK. These lines appear on the console.
xserver-xorg-video-intel 2:2.9.1-3
...
update-initramfs: Generating /boot/initrd.img-2.6.32-3-686
The first seemed promising but no such luck. Under the
2.6.32-3 kernel X still shuts down with the mess
On Thu, 20 May 2010 14:31:43 -0400 (EDT), Stephen Powell wrote:
>
> There is a newer kernel available in squeeze now, 2.6.32-5.
> Maybe it will fix the problem.
Oops! I take that back. That kernel is still in Sid.
There are a couple of other things you can try. One is to
intentionally disable
On Thu, 20 May 2010 13:43:54 -0400 (EDT), Peter Easthope wrote:
> Stephen Powell wrote:
>> I suspect that something not
>> directly related to X is causing X to have a problem of some sort.
>> Sorry I can't be more specific at this point.
>
> http://carnot.pathology.ubc.ca/dalton.dmesg
> and
>
From: Stephen Powell
Date: Thu, 20 May 2010 11:37:42 -0400 (EDT)
> I suspect that something not
> directly related to X is causing X to have a problem of some sort.
> Sorry I can't be more specific at this point.
http://carnot.pathology.ubc.ca/dalton.dmesg
and
http://carnot.pathology.ubc.c
gisters (MTRR) and Advanced Configuration
and Power Interface (ACPI). I would investigate that. Check the
output of
dmesg|less
and
less /var/log/syslog
and other sources of kernel messages to see if you can find the
problem. Maybe something is disabled in your BIOS setup program that
From: Stephen Powell
Date: Wed, 19 May 2010 21:57:26 -0400 (EDT)
> Please post your /etc/lilo.conf file.
Sorry; make that http://carnot.pathology.ubc.ca/dalton.lilo.conf .
> The only way [acpi] should fail is if
> you have a kernel boot parameter to disable it.
I hope so, but the output fr
From: Stephen Powell
Date: Wed, 19 May 2010 21:57:26 -0400 (EDT)
> Please post your /etc/lilo.conf file.
Now at http://carnot.yi.org/dalton.lilo.conf .
> The only way [acpi] should fail is if
> you have a kernel boot parameter to disable it.
I hope so, but the output from
find /etc/ -ty
On Wed, 19 May 2010 18:43:41 -0400 (EDT), Peter Easthope wrote:
> Now in the log there is no (EE) and no /dev/fb0.
> This is what appears on the screen after startx is issued.
>
> pe...@dalton:~$ startx
> [many lines omitted]
> (==) Using system config directory "/usr/share/X11/xorg.conf.d"
>
From: Stephen Powell
Date: Wed, 19 May 2010 17:29:18 -0400 (EDT)
> Did you do a Ctrl+Alt+Backspace to request a shutdown?
> Or did it shutdown automatically?
I did nothing but issue startx. No intervention
to cause the server to shut down.
> If so, what caused the error?
Selinux or MTRR,
On Wed, 19 May 2010 15:32:01 -0400 (EDT), Peter Easthope wrote:
> Stephen Powell wrote:
>> Please post your /etc/X11/xorg.conf file as well.
>
> It contains only commented lines from previous
> experiments. Hasn't changed since the log was
> recorded. Should be visible here.
>
> http:
Date: Wed, 19 May 2010 13:32:33 -0400 (EDT)
From: Stephen Powell
> Please post your /etc/X11/xorg.conf file as well.
It contains only commented lines from previous
experiments. Hasn't changed since the log was
recorded. Should be visible here.
http://carnot.pathology.ubc.ca/dalto
On Sun, May 9, 2010 at 4:16 PM, Sven Joachim wrote:
> On 2010-05-09 08:00 +0200, Akira Kitada wrote:
>
>> I'm trying to set up X and I tried 'Xorg -configure' but it failed
>> with errors below.
>> I run Sid on a home-brew machine built on a GA-EP45-DS
On 2010-05-09 08:00 +0200, Akira Kitada wrote:
> I'm trying to set up X and I tried 'Xorg -configure' but it failed
> with errors below.
> I run Sid on a home-brew machine built on a GA-EP45-DS5 Motherboard and
> my monitor is BenQ FP222W.
>
> I tried Ubuntu 10.
Hi,
I'm trying to set up X and I tried 'Xorg -configure' but it failed
with errors below.
I run Sid on a home-brew machine built on a GA-EP45-DS5 Motherboard and
my monitor is BenQ FP222W.
I tried Ubuntu 10.04 Live CD to see how it works on the same box and
it just worked witho
Try to add your touchpad options to the InputClass section
> of the file /usr/lib/X11/xorg.conf.d/10-synaptics.conf as a first test.
>
> [...]
>
> I am curious to hear if this actually works because I cannot try it
> myself. (My up-to-date Sid desktop does not have a touchpad.)
Hi
On 27 April 2010 06:45, Wolodja Wentland wrote:
> On Tue, Apr 27, 2010 at 00:29 -0500, francis southern wrote:
>> On 14 April 2010 17:09, Wolodja Wentland
>> wrote:
>> > On Wed, Apr 14, 2010 at 22:06 +0200, Sjoerd Hardeman wrote:
>> >> After a large set
On Tue, Apr 27, 2010 at 00:29 -0500, francis southern wrote:
> On 14 April 2010 17:09, Wolodja Wentland
> wrote:
> > On Wed, Apr 14, 2010 at 22:06 +0200, Sjoerd Hardeman wrote:
> >> After a large set of updates today on testing, xorg no longer picks up
> >> my ude
On 14 April 2010 17:09, Wolodja Wentland wrote:
> On Wed, Apr 14, 2010 at 22:06 +0200, Sjoerd Hardeman wrote:
>> After a large set of updates today on testing, xorg no longer picks up
>> my udev rules file. A few months ago hal stopped working, as a change to
>> udev was r
On 2010-04-25, Felix Natter wrote:
> hello,
>
> I am currently running on VESA driver with Lenny's xorg (7.3),
> because my Geforce 310M is only supported in xserver-xorg-video-nv
>>= 2.1.17 (Squeeze).
>
> Now I can try to build the xorg, xorg-server and xserver-xo
hello,
I am currently running on VESA driver with Lenny's xorg (7.3),
because my Geforce 310M is only supported in xserver-xorg-video-nv
>= 2.1.17 (Squeeze).
Now I can try to build the xorg, xorg-server and xserver-xorg-video-nv
source packages and install them, but I must rely on this s
Florian Kulzer schreef:
> On Thu, Apr 15, 2010 at 23:27:41 +0200, Sjoerd Hardeman wrote:
>
> [...]
>
>> Hal is certainly no longer working, see #567389. Yet, udev now also
>> stopped working...
>
> OK, I think I understand a little bit better how this is supposed to be
> working now. Try to add
On Thu, Apr 15, 2010 at 23:27:41 +0200, Sjoerd Hardeman wrote:
[...]
> Hal is certainly no longer working, see #567389. Yet, udev now also
> stopped working...
OK, I think I understand a little bit better how this is supposed to be
working now. Try to add your touchpad options to the InputClass
gards,
Cédric
Xorg.0.log.failed2.gz
Description: Binary data
Xorg.0.log.success2.gz
Description: Binary data
signature.asc
Description: Digital signature
video-intel forced me to freeze my whole Xorg
> installation a while ago. Sorry for the noise, please disregard the bulk
> of what I have just written. It might nevertheless be interesting to
> compare the output of lshal and the Xorg log, to maybe get a clue which
> change broke t
On Thu, Apr 15, 2010 at 21:24:19 +0200, Florian Kulzer wrote:
[ blah, blah, blah ]
Uh-oh, the moment I sent my last message I finally remembered that I
currently use an outdated version of the synaptics driver, because a
serious bug of video-intel forced me to freeze my whole Xorg
installation
On Wed, Apr 14, 2010 at 19:38:23 -0500, francis southern wrote:
> On 14 April 2010 16:51, Florian Kulzer wrote:
> > On Wed, Apr 14, 2010 at 22:06:41 +0200, Sjoerd Hardeman wrote:
> >> Hi list,
> >>
> >> After a large set of updates today on testing, xorg no lon
Thierry Chatelet schreef:
> On Wednesday 14 April 2010 22:06:41 Sjoerd Hardeman wrote:
>> Hi list,
>>
>> After a large set of updates today on testing, xorg no longer picks up
>> my udev rules file. A few months ago hal stopped working, as a change to
>> ude
Wolodja Wentland schreef:
> On Wed, Apr 14, 2010 at 22:06 +0200, Sjoerd Hardeman wrote:
>> After a large set of updates today on testing, xorg no longer picks up
>> my udev rules file. A few months ago hal stopped working, as a change to
>> udev was required (see also the lis
Florian Kulzer schreef:
> On Wed, Apr 14, 2010 at 22:06:41 +0200, Sjoerd Hardeman wrote:
>> Hi list,
>>
>> After a large set of updates today on testing, xorg no longer picks up
>> my udev rules file. A few months ago hal stopped working, as a change to
>> ude
On 14 April 2010 16:51, Florian Kulzer wrote:
> On Wed, Apr 14, 2010 at 22:06:41 +0200, Sjoerd Hardeman wrote:
>> Hi list,
>>
>> After a large set of updates today on testing, xorg no longer picks up
>> my udev rules file. A few months ago hal stopped working, as a cha
On Wednesday 14 April 2010 22:06:41 Sjoerd Hardeman wrote:
> Hi list,
>
> After a large set of updates today on testing, xorg no longer picks up
> my udev rules file. A few months ago hal stopped working, as a change to
> udev was required (see also the list history for several
On Wed, Apr 14, 2010 at 22:06 +0200, Sjoerd Hardeman wrote:
> After a large set of updates today on testing, xorg no longer picks up
> my udev rules file. A few months ago hal stopped working, as a change to
> udev was required (see also the list history for several threads on that
>
On Wed, Apr 14, 2010 at 22:06:41 +0200, Sjoerd Hardeman wrote:
> Hi list,
>
> After a large set of updates today on testing, xorg no longer picks up
> my udev rules file. A few months ago hal stopped working, as a change to
> udev was required (see also the list history for sev
Hi list,
After a large set of updates today on testing, xorg no longer picks up
my udev rules file. A few months ago hal stopped working, as a change to
udev was required (see also the list history for several threads on that
topic). Now, udev stopped working? Did I miss any change to xorg
Jörg-Volker Peetz wrote:
> Concerning Xorg, look through the log file /var/log/Xorg.0.log, e.g.,
> the command
>
> $ grep -i dynamic
uuhm,
$ grep -i dynamic /var/log/Xorg.0.log
>
> should tell you if power saving ("Dynamic Clock Scaling") is enabled or not.
&g
Concerning Xorg, look through the log file /var/log/Xorg.0.log, e.g.,
the command
$ grep -i dynamic
should tell you if power saving ("Dynamic Clock Scaling") is enabled or not.
Generally, the problem of energy consumption can be tackled with the program
powertop best called as root.
just fine. I
even got 3d acceleration and Kwin effects. The problem is that the xorg
process is using the cpu and consuming much memory. The memory consumed is
about 160MB but that doesn't really bother me cause I got plenty of it :P.
Well the annoying thing is the cpu fan; xorg uses about 10% (a
On Fri, 19 Mar 2010 10:39:47 -0400 (EDT)
Stephen Powell wrote:
Hello Stephen,
> Great! That obviously means that the new driver now has support for
> your board/chipset, which means that we no longer have to resort to
Overrides aren't ideal, IMO. Mainly because I forget I've set them, and
the
On Fri, 19 Mar 2010 09:52:57 -0400 (EDT), Brad Rogers wrote:
> On Wed, 17 Mar 2010 16:30:01 -0400 (EDT), Stephen Powell wrote:
>> But we are making forward progress; so I don't want to give up just
>> yet.
>
> Thanks for you help Stephen. Today I performed a system update and
> noticed that XOrg's
On Wed, 17 Mar 2010 16:30:01 -0400 (EDT)
Stephen Powell wrote:
Hello Stephen,
> But we are making forward progress; so I don't want to give up just
> yet.
Thanks for you help Stephen. Today I performed a system update and
noticed that XOrg's nv driver was one of the packages updated. My
scree
that's OK; but I'm willing to keep trying
if you are. If you are willing to keep trying, please post the
exact /etc/X11/xorg.conf file that you used and the exact
/var/log/Xorg.0.log file that resulted. If it took the chipset override
without complaint, that's a good sign
On Wed, 17 Mar 2010 10:01:10 -0400 (EDT)
Stephen Powell wrote:
Hello Stephen,
> You're welcome, but I am disappointed too. I'm curious to know what
So, it's not just me then? :-)
> the failure symptom was. Did it complain that the chipset override was
The error message was unsupported de
I..-fvisibility=hidden -I/usr/include/xorg -I/usr/include/pixman-1
> -I/usr/include/drm -I/usr/include/X11/dri -g -O2 -MT init.lo -MD -MP -MF
> .deps/init.Tpo -c -o init.lo
> init.c
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -fvisibility=hidden
> -I/usr/include/xorg -I/usr/
On Tue, Mar 16, 2010 at 09:27:15PM -0500, Ron Johnson wrote:
>
> Yet I demonstrated that it's in xserver-xorg-dev. However, I'm
> running Sid and you're Squeeze.
>
> Maybe you need to upgrade.
Yup, that file is not available in any package for squeeze.
Cheers, O
On Wed, 17 Mar 2010 07:10:00 -0400 (EDT), Brad Rogers wrote:
> On Tue, 16 Mar 2010 21:43:21 -0400 (EDT), Stephen Powell wrote:
>>Chipset "GeForce 8300 GS"
>> in the "Device" section. I have no idea if it will work. It's a shot
>> in the dark.
>
> Sadly, no joy with that option, either.
>
>
On Wed, 17 Mar 2010 04:20:26 -0400 (EDT), Andrei Popescu wrote:
> On Tue,16.Mar.10, 13:56:27, Stephen Powell wrote:
>>
>> Maybe one of these days, when I feel more adventuresome, I may give
>> this a try myself. I have two systems at home with Nvidia video cards.
>> The trouble is, they're OLD Nv
On Tue, 16 Mar 2010 21:43:21 -0400 (EDT)
Stephen Powell wrote:
Hello Stephen,
>Chipset "GeForce 8300 GS"
> in the "Device" section. I have no idea if it will work. It's a shot
> in the dark.
Sadly, no joy with that option, either.
Once again, Stephen, thank you for all your assistance.
On Tue,16.Mar.10, 13:56:27, Stephen Powell wrote:
>
> Maybe one of these days, when I feel more adventuresome, I may give
> this a try myself. I have two systems at home with Nvidia video cards.
> The trouble is, they're OLD Nvidia cards. The proprietary driver
> may have dropped support for the
Yet I demonstrated that it's in xserver-xorg-dev. However, I'm
running Sid and you're Squeeze.
Maybe you need to upgrade.
On 2010-03-16 21:17, Rogerio Luz Coelho wrote:
Can't find it:
#apt-file -v.v search xf86Resources.h
D: Using cache directory /var/cache/apt
?
Tried this also:
r...@casa:~# locate -b 'xf86Re'
/usr/include/xorg/xf86Rename.h
r...@casa:~#
---
So I don't have it installed , anyone knows how to proceed? Why isn't it
installed via x11-dev packages?
Rogerio
2010/3/16 Ron Johnson
> On 2010-03-1
]
$ make install
Making install in
src
make[1]: Entrando no diretório
`/home/rogerio/xf86-video-sis-imedia/src'
/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
-I..-fvisibility=hidden -I/usr/inclu
but thanks for the tip.
>
>> If it doesn't, look in /var/log/Xorg.0.log for error messages.
>> Sometimes, if you give an invalid value for Chipset it will list
>> what the valid values are, and you may find something there that
>> is close enough to work.
>
>
checking if RANDR is defined... yes
checking if RENDER is defined... yes
checking if XV is defined... yes
*checking if XF86MISC is defined... no*
checking if DPMSExtension is defined... yes
checking for XORG... yes
checking for ANSI C header files... (cached) yes
checking for /usr/include/xorg/dri.h
ough, that occasionally I must go into
/usr/lib/xorg/modules/extensions and mv the xserver-xorg-core
libglx.so out of the way (usually to "libglx.so.software") and then
symlink nvidia's libglx.so.XXX.YY to libglx.so. That, too, is rare,
and only a little bit of manual intervention.
The cor
On 2010-03-16 21:59 +0100, Wayne wrote:
> Just tried to install the source package. listbugs reports that it
> has 2 bugs.
>
> 1. It won't compile
> and
> 2. bad attempt to nest fakeroot sessions.
>
> Testing on a 686.
>
> Just one more package, of many, that got to testing too fast.
You got it
On Tue, 16 Mar 2010 21:34:45 +0100
Sven Joachim wrote:
Hello Sven,
> If you run squeeze, you need to install the nvidia-* versions from sid.
> I don't know why the nvidia-graphics-drivers source package had not
> been removed from testing months ago, as it's utterly broken there (the
> missing n
601 - 700 of 2792 matches
Mail list logo
