Re: Wheezy. Xorg failure at AMD Brazos netbook

[Leonid Korostyshevski]

On Thu, Feb 2, 2012 at 1:46 PM, Bob  wrote:

> On 02/01/2012 03:48 PM, Leonid Korostyshevski wrote:
>
>> Hello, list!
>>
>> Have installed Wheezy weekly build 30-01-2012 but cannot log into a
>> fresh system: there is just a noise on a screen instead of a logon
>> screen. Cannot escape to text console, Ctrl+Alt+F1...Fn does not works.
>> Ctrl+Alt+PrtScr+B works, though. Also, IMHO it is a good idea to enable
>> Ctrl+Alt+Backspace for "testing" distro.
>>
>> Not sure about "recovery" mode naming as a GRUB2 entry. It leads to the
>> same noise on screen, not to safe plain VGA CLI environment, as it
>> suppose to be IMHO. "Testing" shouldn't be "stuck with" IMHO :0)
>>
>> Hardware in use - netbook on AMD Brazos (C-60 + ATI 6250). No 'lspci' at
>> the moment, sorry. During installation process, 3.1.x.-486 kernel was
>> chosen.
>>
>> Would you, please, to give an advice how to override Xorg fault?
>>
>> Thanks a lot!
>> LK
>>
>
> Don't know how to fix this but I'm following the thread as I'm interested
> in The AMD Fusion APU E350 powered ASUS EeePc 11215B
>
>
Is anybody tried to install fresh weekly build and if you, please, can tell
is the issue got fixed?

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Stayvoid]

Hello.

It worked!
I ran apt-get update; apt-get -f upgrade; apt-get install xorg.

Now I want to find out which packages are really needed. Because xorg
installed a lot of stuff.

Thanks for your help.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cak5fs_gxp9jwz37-9fuastmernmoxydfiok_pec674dnkny...@mail.gmail.com

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Stayvoid]

> ..firmware?
> arnt@celsius:~$ dpkg -l |grep firmware-linux
> ii  firmware-linux   0.35
> Binary firmware for various drivers in the Linux kernel (meta-package)
> ii  firmware-linux-free  3
> Binary firmware for various drivers in the Linux kernel
> ii  firmware-linux-nonfree   0.35
> Binary firmware for various drivers in the Linux kernel
Here is mine:
ii  firmware-linux-free
2.6.32-35+gnewsense1   Binary firmware for
various drivers in the Linux kernel


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAK5fS_Hgbyx3S+8B5yxcPgYzr4q1x97+1f8R9Wv9=rtjj8x...@mail.gmail.com

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Arnt Karlsen]

On Thu, 1 Mar 2012 02:36:03 +0300, Stayvoid wrote in message 
:

> > This suggests something is missing from your kernel.

..firmware?
arnt@celsius:~$ dpkg -l |grep firmware-linux
ii  firmware-linux   0.35
Binary firmware for various drivers in the Linux kernel (meta-package)
ii  firmware-linux-free  3
Binary firmware for various drivers in the Linux kernel 
ii  firmware-linux-nonfree   0.35
Binary firmware for various drivers in the Linux kernel
arnt@celsius:~$  


> Could you be more specific?
> Will it help if I paste my .config?




-- 
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120305225331.15447...@nb6.lan

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Brian]

On Wed 29 Feb 2012 at 23:48:22 +0300, Stayvoid wrote:

> This guide wasn't helpful. "modprobe nouveau" outputs nothing and

It wouldn't output anything if the module was already in place.

> there is no nouveau module in the output of "lsmod." But nouveau

That is extremely surprising considering you have shown a dmesg output
elsewhere which displays it being brought into use and being used for
the framebuffer on the console.

> appears in the output of "lspci -vv."

I don't suppose it said 'Kernel driver in use: nouveau?

> Let's try to fix it in gNewSense. (My version is based on Squeeze.)

gNewSense is nearly three years old and, I think, based on Ubuntu. The
suggested mismatch is most likely the cause of X not running. In Debian
at that time nouveau packages were possibly classed as experimental.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120301004352.GB13677@desktop

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Stayvoid]

> This suggests something is missing from your kernel.
Could you be more specific?
Will it help if I paste my .config?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cak5fs_ei7fm69ruruuxwttb8sd2ufgsystu1wre9pxkgqno...@mail.gmail.com

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Andrei POPESCU]

On Mi, 29 feb 12, 23:48:22, Stayvoid wrote:
> 
> This guide wasn't helpful. "modprobe nouveau" outputs nothing and
> there is no nouveau module in the output of "lsmod." But nouveau
> appears in the output of "lspci -vv."
 
This suggests something is missing from your kernel.

> Let's try to fix it in gNewSense. (My version is based on Squeeze.)

"based" is the keyword here. Unless there is someone here familiar with 
gNewSense you're out of luck.

Kind regards,
Andrei
-- 
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic


signature.asc
Description: Digital signature

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Stayvoid]

> Earlier you mentioned
> http://nouveau.freedesktop.org/wiki/TroubleShooting
>
> did you check the section that applies to this error?
> http://nouveau.freedesktop.org/wiki/TroubleShooting#Xorg_fails_to_start_with_.22.28EE.29_.5Bdrm.5D_failed_to_open_device.22

This guide wasn't helpful. "modprobe nouveau" outputs nothing and
there is no nouveau module in the output of "lsmod." But nouveau
appears in the output of "lspci -vv."

> At this point I can only guess there is some mismatch between your
> kernel and Xorg. I would suggest you try to reproduce this on a pure
> Debian install[1][2], but if it works there is not much more we can do.
>
> [1] you mentioned using gNewSense
> [2] you are of course aware that Debian with only 'main' is free

Kernel: Linux-libre 3.2.4;
Xorg: 1:7.5+8+squeeze1.

I don't know how to check the versions of libdrm and nouveau DRM. And
I have no idea which ones are compatible.

Someone told me that I could check it this way:
$ grep DRICreatePCIBusID /usr/lib/xorg/modules/extensions/libdri*

Here is the output:
Binary file /usr/lib/xorg/modules/extensions/libdri.so matches

I don't know how to reinstall the whole system quickly or how to
install it harmlessly for the main system. (Could you provide a guide
on this?) It took me a lot of time to setup the current system.
And I don't really want to install Debain. [a]

Let's try to fix it in gNewSense. (My version is based on Squeeze.)

I'd also tried to ask gNewSense guys. [b]

Cheers

[a] http://www.gnu.org/distros/common-distros.html
[b] http://lists.nongnu.org/archive/html/gnewsense-users/2012-02/msg00011.html


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAK5fS_H__-xuNp3skQpoDiT_k4TP1iiqOERdf2i=pnc7vf7...@mail.gmail.com

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Andrei POPESCU]

On Mi, 29 feb 12, 05:21:03, Stayvoid wrote:

> (EE) [drm] failed to open device
> (EE) No devices detected.

Earlier you mentioned 
http://nouveau.freedesktop.org/wiki/TroubleShooting

did you check the section that applies to this error?
http://nouveau.freedesktop.org/wiki/TroubleShooting#Xorg_fails_to_start_with_.22.28EE.29_.5Bdrm.5D_failed_to_open_device.22

At this point I can only guess there is some mismatch between your 
kernel and Xorg. I would suggest you try to reproduce this on a pure 
Debian install[1][2], but if it works there is not much more we can do.

[1] you mentioned using gNewSense
[2] you are of course aware that Debian with only 'main' is free

Kind regards,
Andrei
-- 
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic


signature.asc
Description: Digital signature

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Stayvoid]

> Please attach your /var/log/Xorg.0.log

X.Org X Server 1.7.7
Release Date: 2010-05-04
X Protocol Version 11, Revision 0
xorg-server 2:1.7.7-14 (Julien Cristau )
Current version of pixman: 0.25.1
   Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log"
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(==) No Layout section.  Using the first Screen section.
(==) No screen section available. Using defaults.
(**) |-->Screen "Default Screen Section" (0)
(**) |   |-->Monitor ""
(==) No device specified for screen "Default Screen Section".
   Using the first device section listed.
(**) |   |-->Device "n"
(==) No monitor specified for screen "Default Screen Section".
   Using a default monitor configuration.
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
   Entry deleted from font path.
(WW) `fonts.dir' not found (or not valid) in
"/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType".
   Entry deleted from font path.
   (Run 'mkfontdir' on "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType").
(==) FontPath set to:
   /usr/share/fonts/X11/misc,
   /usr/share/fonts/X11/100dpi/:unscaled,
   /usr/share/fonts/X11/75dpi/:unscaled,
   /usr/share/fonts/X11/Type1,
   /usr/share/fonts/X11/100dpi,
   /usr/share/fonts/X11/75dpi,
   built-ins
(==) ModulePath set to "/usr/lib/xorg/modules"
(II) The server relies on udev to provide the list of input devices.
   If no devices become available, reconfigure udev or disable
AutoAddDevices.
(II) Loader magic: 0x81ecce0
(II) Module ABI versions:
   X.Org ANSI C Emulation: 0.4
   X.Org Video Driver: 6.0
   X.Org XInput driver : 7.0
   X.Org Server Extension : 2.0
(--) using VT number 7

(--) PCI:*(0:1:0:0) 10de:0a29:106b:00c7 rev 162, Mem @
0xc000/16777216, 0x9000/268435456, 0xa000/33554432, I/O @
0x2000/128, BIOS @ 0x/524288
(II) Open ACPI successful (/var/run/acpid.socket)
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
   compiled for 1.7.7, module version = 1.0.0
   Module class: X.Org Server Extension
   ABI class: X.Org Server Extension, version 2.0
(II) Loading extension SELinux
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
   compiled for 1.7.7, module version = 1.0.0
   Module class: X.Org Server Extension
   ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions/libglx.so
(II) Module glx: vendor="X.Org Foundation"
   compiled for 1.7.7, module version = 1.0.0
   ABI class: X.Org Server Extension, version 2.0
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions/librecord.so
(II) Module record: vendor="X.Org Foundation"
   compiled for 1.7.7, module version = 1.13.0
   Module class: X.Org Server Extension
   ABI class: X.Org Server Extension, version 2.0
(II) Loading extension RECORD
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions/libdri.so
(II) Module dri: vendor="X.Org Foundation"
   compiled for 1.7.7, module version = 1.0.0
   ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "dri2"
(II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
   compiled for 1.7.7, module version = 1.1.0
   ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "nouveau"
(II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
(II) Module nouveau: vendor="X.Org Foundation"
   compiled for 1.7.7, module version = 0.0.15
   Module class: X.Org Video Driver
   ABI class: X.Org Video Driver, version 6.0
(II) NOUVEAU driver Date:   Tue Mar 16 13:08:37 2010 +1000
(II) NOUVEAU driver for NVIDIA chipset

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Nick Lidakis]

On Mon, Feb 27, 2012 at 08:57:22PM -0500, Stefan Monnier wrote:
> While I admire the work the Nouveau guys are doing, after suffering for
> more than 4 years with an Nvidia GPU+chipset on my desktop, I just
> replaced the motherboard with a one based on the AMD E350 fusion chip,
> and suddenly all my problems are gone.  One of the best $200 I've
> spent recently.

Aside from the GPU, what problems did you have with the chipset?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120228044234.GA4280@phobos

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Stefan Monnier]

While I admire the work the Nouveau guys are doing, after suffering for
more than 4 years with an Nvidia GPU+chipset on my desktop, I just
replaced the motherboard with a one based on the AMD E350 fusion chip,
and suddenly all my problems are gone.  One of the best $200 I've
spent recently.
Only remaining problem: Gnome.


Stefan


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/jwv8vjn205n.fsf-monnier+gmane.linux.debian.u...@gnu.org

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Andrei POPESCU]

On Ma, 28 feb 12, 02:39:44, Stayvoid wrote:
> I've tried to use both packages, but I can't make X work.
> startx fails with (EE) [drm] failed to open device.
> 
> I tried to look through the kernel options, asked people about it,
> read a man page on troubleshooting [1], but all my attempts were
> unsuccesful.

Please attach your /var/log/Xorg.0.log

Kind regards,
Andrei
-- 
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic


signature.asc
Description: Digital signature

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Stayvoid]

I've tried to use both packages, but I can't make X work.
startx fails with (EE) [drm] failed to open device.

I tried to look through the kernel options, asked people about it,
read a man page on troubleshooting [1], but all my attempts were
unsuccesful.

[1] http://nouveau.freedesktop.org/wiki/TroubleShooting


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAK5fS_GKUnybZD1L=eoktrot0-mj4wru6qshua6fta4sq4v...@mail.gmail.com

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Camaleón]

On Thu, 02 Feb 2012 20:19:44 +, lee wrote:

> Camaleón  writes:

>>> Hum, did you ever try to get X11 to work with an ATI mach32 or mach64
>>> or, later, a Matrox G200, about 15 years ago?
>>
>> My first linux box (SuSE Linux 8.2) was installed on a Matrox G450,
>> IIRC. I had to do nothing, it worked out of the box. Maybe I was just
>> lucky.
>>
>> Afterwards, I have installed over nvidia (mostly in workstations), ATI
>> (in servers) and Intel (netbooks).
> 
> You must have been really lucky then :)

Yes... I also think so. True is that I always try to buy good hardware.

>>> Remember your huge 14 or 15" CRT monitor flickering and possibly being
>>> damaged when you got the frequencies too high in your xf86config while
>>> trying to get a less flickery image in an unbelieveably high 1024x768
>>> resolution?
>>
>> Nope, maybe because my displays were well supported (Sony) :-)
>>
>>> And remember trying to figure out modelines?
>>
>> Nope, in fact I've only had to deal with that at the time Xorg became
>> dynamic but not before (openSUSE had a very nice tool to configure this
>> called "SaX").
> 
> Yeah, there were some tools to calculate modelines ... Fortunately, I
> got away with specifying the frequencies.

"cvt" is a very old and useful tool for adding modelines and refresh 
frequencies. And to be sincere, I've only had to use it now with xrandr 
and not in the time xorg was static and predictable :-)
 
>>> Nowadays, you don´t really need to do anything ...
>>
>> No? Nothing? Really? I mean, really?
> 
> You are very likely to end up with a graphical display because all the
> drivers are (needlessly) installed through dependencies, and which one
> is used is being figured out automatically. That doesn´t mean that your
> display is optimally configured.

He, but having all the drivers installed does not guarantee they are 
going to work well ;-). In fact, having all the drivers installed can 
even aggravate the situation.

>> You do have to do many things now that were not needed in the old days.
>> For instance, try to install the closed source nvidia driver while
>> having nuvó installed.
> 
> Just put nuveau into /etc/modprobe.d/blacklist.

This *should *work, right? But it does not always work :-)

And how can you now use a vesa or fb driver? In the old days you only had 
to put "vesa" in xorg.conf, but now... he, he... is not that easy.

>> In the old times, editing one line at xorg.conf was all to get the
>> driver loaded.
> 
> In many cases, things work without xorg.conf.

Of course, but the problem arises when it does not.

>> Now you can be even forced to uninstall one set of the drivers to use
>> the other. And debugging has turned very difficult...
> 
> If you have had several different drivers for the same card 15 years
> ago, you´d probably have had the same problem.

Nope, because they collided and could not be installed at the same time.
 
>>> What hasn´t changed is that ATI cards (now made by AMD) cause nothing
>>> but trouble ...
>>
>> Well, "radeon" driver should be by now the best open source VGA driver
>> out there, it's almost open source and developers have been working on
>> it since many years...
> 
> ATI cards have been troublesome with OS/2 2.0 and 3.0, with various
> versions of Windoze and with Linux.
> 
> I have a Radeon card in this laptop, and when I switch over to that card
> with vgaswitcheroo, I don´t get any further screen output until I switch
> back to the Intel card. The open source driver for them might be great,
> it just doesn´t help me when there´s no screen output. If I could have
> bought this laptop with an NVDIA card, I would have. All the NVDIA cards
> I´ve had just worked fine, and all the ATI cards I´ve had and have seen
> were troublesome.

Yes, but that's not an expected situation, I mean, shouldn't the open 
source driver be the best one, in quality and stability terms? Why we do 
prefer nvidia over ATI cards?

>> Intel is another good choice if you don't want many problems and are
>> happy with a low-end 3D card.
> 
> The Intel card is ok unless I want to play a game. For games, it´s an
> euphemism to say that the performance is pathetic.

I can't tell for games because I do't play much :-) but for the usual 
tasks I find it enough.

>>> Unfortunately, the free NVIDA drivers are rather useless when you want
>>> to play games. You can install the non-free ones from the Debian
>>> packages.
>>
>> I've always been lucky with nvidia closed drivers. I don't

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Camaleón]

On Thu, 02 Feb 2012 18:59:47 +, Brian wrote:

> On Thu 02 Feb 2012 at 12:57:50 +, Camaleón wrote:
> 
>> On Wed, 01 Feb 2012 20:28:55 +, lee wrote:
>> 
>> > Nowadays, you don´t really need to do anything ...
>> 
>> No? Nothing? Really? I mean, really?
> 
> Yes, really. It's such an improvement on the past. 

I'm not that sure... 

It can be an improvement for portable devices (notebooks, netbooks) that 
need to add on-the-fly output devices and do not usually change the VGA 
card. But for a workstation or desktop computers it can be now a hell to 
get it working well. Moreover, video card vendors are adding difficulties 
to the hardware (e.g., hybrid graphics) while they do not provide free 
drivers for their inventions and so leaving the open source users to the 
deepest ostracism.

> Nouveau gets the console resolution right and gives a nice framebuffer.
> Start X and it just figures out everything. Then there's KMS. We're
> spoiled.

Nuvó is not an option for some users that need to get the best for their 
nvidia cards. Radeon driver is not always working as we would like (I 
have a chap with problems with his ati card -iMac5- that cannot work with 
gnome-shell, he has to use gnome classical because kernel and/or xorg 
segfaults). Intel driver had some annoying problems in the past but now 
seems to be a good option.

Nope, I don't like the status of the VGA in linux but that's nothing we 
(open source users) can do. Companies have to start releasing their code 
with an open source license, giving full specs and providing resources 
(developers) to build the drivers. Until that happens, we will still have 
many problems :-(

>> You do have to do many things now that were not needed in the old days.
>> For instance, try to install the closed source nvidia driver while
>> having nuvó installed. In the old times, editing one line at xorg.conf
>> was all to get the driver loaded. Now you can be even forced to
>> uninstall one set of the drivers to use the other. And debugging has
>> turned very difficult...
> 
> Sounds dreadful! I'm thankful to be among the 95% of PC users who do not
> need 3D acceleration.

The problem is not that *users* need 3D acceleration *but* Google Earth, 
gnome-shell, etc... I mean, applications, do ;-)

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/jgguqb$bgm$4...@dough.gmane.org

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[lee]

Camaleón  writes:

> On Wed, 01 Feb 2012 20:28:55 +, lee wrote:
>
>> Camaleón  writes:
>> 
>>> having to deal with the mess of installing a VGA card in linux. It
>>> never has been so difficult and so hard than now is (or at least I
>>> don't remember it was when no KMS and no dynamic Xorg existed).
>> 
>> Hum, did you ever try to get X11 to work with an ATI mach32 or mach64
>> or, later, a Matrox G200, about 15 years ago? 
>
> My first linux box (SuSE Linux 8.2) was installed on a Matrox G450, IIRC. 
> I had to do nothing, it worked out of the box. Maybe I was just lucky.
>
> Afterwards, I have installed over nvidia (mostly in workstations), ATI 
> (in servers) and Intel (netbooks).

You must have been really lucky then :)

>> Remember your huge 14 or 15" CRT monitor flickering and possibly being
>> damaged when you got the frequencies too high in your xf86config while
>> trying to get a less flickery image in an unbelieveably high 1024x768
>> resolution? 
>
> Nope, maybe because my displays were well supported (Sony) :-)
>
>> And remember trying to figure out modelines?
>
> Nope, in fact I've only had to deal with that at the time Xorg became 
> dynamic but not before (openSUSE had a very nice tool to configure this 
> called "SaX").

Yeah, there were some tools to calculate modelines ... Fortunately, I
got away with specifying the frequencies.

>> Nowadays, you don´t really need to do anything ... 
>
> No? Nothing? Really? I mean, really? 

You are very likely to end up with a graphical display because all the
drivers are (needlessly) installed through dependencies, and which one
is used is being figured out automatically. That doesn´t mean that your
display is optimally configured.

> You do have to do many things now that were not needed in the old days. 
> For instance, try to install the closed source nvidia driver while having 
> nuvó installed.

Just put nuveau into /etc/modprobe.d/blacklist.

> In the old times, editing one line at xorg.conf was all 
> to get the driver loaded.

In many cases, things work without xorg.conf.

> Now you can be even forced to uninstall one set of the drivers to use
> the other. And debugging has turned very difficult...

If you have had several different drivers for the same card 15 years
ago, you´d probably have had the same problem.

>> What hasn´t changed is that ATI cards (now made by AMD) cause nothing
>> but trouble ...
>
> Well, "radeon" driver should be by now the best open source VGA driver 
> out there, it's almost open source and developers have been working on it 
> since many years...

ATI cards have been troublesome with OS/2 2.0 and 3.0, with various
versions of Windoze and with Linux.

I have a Radeon card in this laptop, and when I switch over to that card
with vgaswitcheroo, I don´t get any further screen output until I switch
back to the Intel card. The open source driver for them might be great,
it just doesn´t help me when there´s no screen output. If I could have
bought this laptop with an NVDIA card, I would have. All the NVDIA cards
I´ve had just worked fine, and all the ATI cards I´ve had and have seen
were troublesome.

>> Stayvoid, you can use vgaswitcheroo to switch between cards. You need to
>> have the debugfs mounted for that. If you still get screen output after
>> switching over, you´re lucky --- I´m not and so I´m stuck with the slow
>> Intel card.
>
> Intel is another good choice if you don't want many problems and are 
> happy with a low-end 3D card.

The Intel card is ok unless I want to play a game. For games, it´s an
euphemism to say that the performance is pathetic.

>> Unfortunately, the free NVIDA drivers are rather useless when you want
>> to play games. You can install the non-free ones from the Debian
>> packages.
>
> I've always been lucky with nvidia closed drivers. I don't like the fact 
> they are closed but at least I get a stable system with few glitches.

Yeah, that´s why I keep buying NVDIA cards: they work. Now I didn´t have
a choice but to get an ATI card in this laptop, and of course, it
doesn´t work ...


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87vcnp0yzj@songoku.yagibdah.de

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Brian]

On Thu 02 Feb 2012 at 12:57:50 +, Camaleón wrote:

> On Wed, 01 Feb 2012 20:28:55 +, lee wrote:
> 
> > Nowadays, you don´t really need to do anything ... 
> 
> No? Nothing? Really? I mean, really? 

Yes, really. It's such an improvement on the past. Nouveau gets the
console resolution right and gives a nice framebuffer. Start X and it
just figures out everything. Then there's KMS. We're spoiled.

> You do have to do many things now that were not needed in the old days. 
> For instance, try to install the closed source nvidia driver while having 
> nuvó installed. In the old times, editing one line at xorg.conf was all 
> to get the driver loaded. Now you can be even forced to uninstall one set 
> of the drivers to use the other. And debugging has turned very 
> difficult...

Sounds dreadful! I'm thankful to be among the 95% of PC users who do not
need 3D acceleration.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120202185947.GH917@desktop

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Ralf Mardorf]

On Thu, 2012-02-02 at 12:57 +, Camaleón wrote:
> openSUSE

I started using Linux with Suse 9.0 and even today I've got an outdated
11.2 install. Suse supports settings for exotic German monitors, that
are unsupported by the X "calculators" in the Internet.

I agree that it was easier to set up X in the old days, than it is today
and I confirm that using the proprietary driver, if possible, is the
best way to go. If the proprietary driver doesn't work, e.g. because of
issues related to a kernel-rt, than I use the nv driver, that btw. was
dropped for Debian when I used Debian some month ago. On Arch Linux the
nv driver still is in the official repositories.

- Ralf


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1328200750.4596.31.camel@localhost.localdomain

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Tom H]

On Wed, Feb 1, 2012 at 6:08 AM, Ralf Mardorf  wrote:
>
> Serious, you're using a Mac [1], there's nothing I could imagine that's
> more un-libre. I really wonder why you won't use the proprietary driver.

Aren't you conflating Apple hardware and OS?1


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAOdo=sw+msvgfqekdkxjbj1iq8zm9yanfazdogettwepw+b...@mail.gmail.com

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Camaleón]

On Wed, 01 Feb 2012 20:28:55 +, lee wrote:

> Camaleón  writes:
> 
>> having to deal with the mess of installing a VGA card in linux. It
>> never has been so difficult and so hard than now is (or at least I
>> don't remember it was when no KMS and no dynamic Xorg existed).
> 
> Hum, did you ever try to get X11 to work with an ATI mach32 or mach64
> or, later, a Matrox G200, about 15 years ago? 

My first linux box (SuSE Linux 8.2) was installed on a Matrox G450, IIRC. 
I had to do nothing, it worked out of the box. Maybe I was just lucky.

Afterwards, I have installed over nvidia (mostly in workstations), ATI 
(in servers) and Intel (netbooks).

> Remember your huge 14 or 15" CRT monitor flickering and possibly being
> damaged when you got the frequencies too high in your xf86config while
> trying to get a less flickery image in an unbelieveably high 1024x768
> resolution? 

Nope, maybe because my displays were well supported (Sony) :-)

> And remember trying to figure out modelines?

Nope, in fact I've only had to deal with that at the time Xorg became 
dynamic but not before (openSUSE had a very nice tool to configure this 
called "SaX").

> Nowadays, you don´t really need to do anything ... 

No? Nothing? Really? I mean, really? 

You do have to do many things now that were not needed in the old days. 
For instance, try to install the closed source nvidia driver while having 
nuvó installed. In the old times, editing one line at xorg.conf was all 
to get the driver loaded. Now you can be even forced to uninstall one set 
of the drivers to use the other. And debugging has turned very 
difficult...

> What hasn´t changed is that ATI cards (now made by AMD) cause nothing
> but trouble ...

Well, "radeon" driver should be by now the best open source VGA driver 
out there, it's almost open source and developers have been working on it 
since many years...

> Stayvoid, you can use vgaswitcheroo to switch between cards. You need to
> have the debugfs mounted for that. If you still get screen output after
> switching over, you´re lucky --- I´m not and so I´m stuck with the slow
> Intel card.

Intel is another good choice if you don't want many problems and are 
happy with a low-end 3D card.

> Unfortunately, the free NVIDA drivers are rather useless when you want
> to play games. You can install the non-free ones from the Debian
> packages.

I've always been lucky with nvidia closed drivers. I don't like the fact 
they are closed but at least I get a stable system with few glitches.

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/jge18e$qa4$3...@dough.gmane.org

Re: Wheezy. Xorg failure at AMD Brazos netbook

[Bob]

On 02/01/2012 03:48 PM, Leonid Korostyshevski wrote:

Hello, list!

Have installed Wheezy weekly build 30-01-2012 but cannot log into a
fresh system: there is just a noise on a screen instead of a logon
screen. Cannot escape to text console, Ctrl+Alt+F1...Fn does not works.
Ctrl+Alt+PrtScr+B works, though. Also, IMHO it is a good idea to enable
Ctrl+Alt+Backspace for "testing" distro.

Not sure about "recovery" mode naming as a GRUB2 entry. It leads to the
same noise on screen, not to safe plain VGA CLI environment, as it
suppose to be IMHO. "Testing" shouldn't be "stuck with" IMHO :0)

Hardware in use - netbook on AMD Brazos (C-60 + ATI 6250). No 'lspci' at
the moment, sorry. During installation process, 3.1.x.-486 kernel was
chosen.

Would you, please, to give an advice how to override Xorg fault?

Thanks a lot!
LK


Don't know how to fix this but I'm following the thread as I'm 
interested in The AMD Fusion APU E350 powered ASUS EeePc 11215B



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4f2a5b6c.4060...@homeurl.co.uk

Re: OT: Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Ralf Mardorf]

On Thu, 2012-02-02 at 06:50 +0100, Ralf Mardorf wrote:
> On Wed, 2012-02-01 at 20:28 +, lee wrote:
> > Remember your huge 14 or
> > 15" CRT monitor flickering and possibly being damaged when you got the
> > frequencies too high
> 
> I still need to read some older replies, but I can't resist to answer OT
> now.
> 
> I'm a dino and trillions years ago it was possible to set up X by trial
> and error. One step after the other I never damaged hardware. If
> frequencies get to high, I saw "lines" and heard noise, from hardware
> that shouldn't make noise.
> 
> Today X don't allow you to go the trial and error way and X calculators
> only provide international common monitors.

PPS: The transistors that get damaged if you choose a frequency that is
muuuch to high, doesn't cost that much today. Usually they won't
burst, as long as you stop to go higher for the frequencies, when you
see lines or hear noise.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1328162273.4596.17.camel@localhost.localdomain

OT: Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Ralf Mardorf]

On Wed, 2012-02-01 at 20:28 +, lee wrote:
> Remember your huge 14 or
> 15" CRT monitor flickering and possibly being damaged when you got the
> frequencies too high

I still need to read some older replies, but I can't resist to answer OT
now.

I'm a dino and trillions years ago it was possible to set up X by trial
and error. One step after the other I never damaged hardware. If
frequencies get to high, I saw "lines" and heard noise, from hardware
that shouldn't make noise.

Today X don't allow you to go the trial and error way and X calculators
only provide international common monitors.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1328161851.4596.12.camel@localhost.localdomain

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[lee]

Camaleón  writes:

> having to deal with the mess of installing a VGA card in linux. It
> never has been so difficult and so hard than now is (or at least I
> don't remember it was when no KMS and no dynamic Xorg existed).

Hum, did you ever try to get X11 to work with an ATI mach32 or mach64
or, later, a Matrox G200, about 15 years ago? Remember your huge 14 or
15" CRT monitor flickering and possibly being damaged when you got the
frequencies too high in your xf86config while trying to get a less
flickery image in an unbelieveably high 1024x768 resolution? And
remember trying to figure out modelines?

Nowadays, you don´t really need to do anything ... What hasn´t changed
is that ATI cards (now made by AMD) cause nothing but trouble ...


Stayvoid, you can use vgaswitcheroo to switch between cards. You need to
have the debugfs mounted for that. If you still get screen output after
switching over, you´re lucky --- I´m not and so I´m stuck with the slow
Intel card.

Unfortunately, the free NVIDA drivers are rather useless when you want
to play games. You can install the non-free ones from the Debian
packages.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87obti1ens@songoku.yagibdah.de

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Sven Joachim]

On 2012-02-01 05:41 +0100, Stayvoid wrote:

>> What version of Debian do you have installed?
> I'm using gNewSense (AFAIK it's based on Squeeze).

That's certainly not optimal, you need something newer for your card.

>> What Nvidia graphics?
> NVIDIA GeForce 330M

This seems to be an NVA5 chip for which you need at least kernel 2.6.39
due to https://bugs.freedesktop.org/show_bug.cgi?id=26980.  And you have
to upgrade the userspace as well then (packages are in
squeeze-backports).

> + Intel HD

Well, that's bad.

>> Do you need perfect, very fast 3D acceleration?
> Yep, but the drivers should be free.

These demands clash, since very fast 3D is really only available with
proprietary drivers.  Free drivers offer moderately fast 3D at best.

Sven


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/8739auecgn@turtle.gmx.de

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Sven Joachim]

On 2012-02-01 12:42 +0100, Stayvoid wrote:

>> Serious, you're using a Mac [1], there's nothing I could imagine that's
>> more un-libre.
> I can't go back in time, but I can change the future.
>
>> I really wonder why you won't use the proprietary driver.
> It's a matter of principle.

I'd recommend to avoid NVidia hardware in the future then, especially on
laptops.

Cheers,
   Sven


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/877h06eckq@turtle.gmx.de

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Camaleón]

On Wed, 01 Feb 2012 13:50:53 +0300, Stayvoid wrote:

> I don't want to use non-free software.

That's a curious statement coming from a Mac user >:-)

Then consider using the Intel card and the Intel driver (if you can). 
Intel is the only manufacturer that develops an open source driver for 
their VGA chipsets (with little exceptions) and directly supports FOSS.

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/jgblnb$at5$6...@dough.gmane.org

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Camaleón]

On Tue, 31 Jan 2012 20:51:21 +0100, Sven Joachim wrote:

> On 2012-01-31 20:29 +0100, Ralf Mardorf wrote:
> 
>> xserver-xorg includes X and xserver-xorg-video-nouveau includes a
>> borked Nvidia driver for X.
> 
> This "borked" driver works fine for me.  YMMV, of course.
> 
> Sven,
>  maintainer of the "borked" package

:-)

Sven, do not take it as a personal attack, just think about the many 
users out there having to deal with the mess of installing a VGA card in 
linux. It never has been so difficult and so hard than now is (or at 
least I don't remember it was when no KMS and no dynamic Xorg existed).

Now, getting it working comes by pure luck.

Of course, the ones to blame here are not:

1/ Nuvó package maintainers
2/ Nuvó package developers
3/ Nuvó upstream developers
4/ Kernel people
5/ Xorg people

If someone wants to complain it should direct his/her gripes to the 
manufacturers (nvidia, ati) which are the only responsible for the 
current state of their drivers in the linux ecosystem.

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/jgbl99$at5$5...@dough.gmane.org

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Vincent Lefevre]

On 2012-01-31 15:28:19 -0700, Bob Proulx wrote:
> Gilbert Sullivan wrote:
> > Brian wrote:
> > > Sven Joachim wrote:
> > >> Sven,
> > >>  maintainer of the "borked" package
> > > 
> > > Seeing as you mention it - it is time to say 'thank you'.
> > 
> > + 1 to this.
> 
> +1 from me as well.  I am happily using the nouveau package and driver
> on several machines.  It made using them as easy as apt-get install
> when otherwise I would have been scrambling for a solution.

+1 from me as well. I'd just like bug 640464 to be fixed.

BTW, the "official" NVIDIA driver had its own bugs when I was using
it; in particular the virtual consoles had a bad number of lines.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120201151759.gd9...@ypig.lip.ens-lyon.fr

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Stayvoid]

> Serious, you're using a Mac [1], there's nothing I could imagine that's
> more un-libre.
I can't go back in time, but I can change the future.

> I really wonder why you won't use the proprietary driver.
It's a matter of principle.

Thanks for the links.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cak5fs_fxsamrxhupzcurhhy26kqz1f0v4pwsvyezv4mgeqc...@mail.gmail.com

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Ralf Mardorf]

On Wed, 2012-02-01 at 13:50 +0300, Stayvoid wrote:
> I don't want to use non-free software.

On a "regular non-Mac-PC" the nouveau driver very often doesn't work,
but even if it should work for you, take a look at
http://nouveau.freedesktop.org/wiki/ ,
http://nouveau.freedesktop.org/wiki/MesaDrivers .

Complete, fast 3D acceleration isn't supported yet:

"Current Status

Quick overview:

KernelModeSetting (KMS) is mandatory Suspend and resume is working for
many chips

2D support is in very good shape with EXA acceleration, Xv and Randr12
(dual-head, rotations, etc.). To understand how multiple monitors work
in X, see MultiMonitorDesktop.

For some Fermi cards, like the NVD9, check the firmware status as it is
required for acceleration.

Some 3D acceleration exists. Read MesaDrivers carefully.

Nvidia Optimus support is not implemented yet, you may not be able to
use the Nvidia GPU at all on Optimus laptops."

There're no other drivers than the proprietary nvidia and this nouveau
driver supporting 3D acceleration. If you won't use the proprietary,
than you probably are screwed.

Serious, you're using a Mac [1], there's nothing I could imagine that's
more un-libre. I really wonder why you won't use the proprietary driver.

Regards,
Ralf

[1] I've got Apple equipment myself. I didn't buy, but won it some days
ago. IMHO a proprietary graphics driver would be the last thing I would
worry about.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1328094524.1398.13.camel@localhost.localdomain

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Stayvoid]

I don't want to use non-free software.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cak5fs_gthf+khz8wyepvcbkpvk9xotf4lkib7ojniffy3un...@mail.gmail.com

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Ralf Mardorf]

On Wed, 2012-02-01 at 07:41 +0300, Stayvoid wrote:
> Hello!
> 
> > What version of Debian do you have installed?
> I'm using gNewSense (AFAIK it's based on Squeeze).
> 
> > What Nvidia graphics?
> NVIDIA GeForce 330M + Intel HD
> 
> > What computer?
> MacBookPro6,2

Phew! Take a look at
https://help.ubuntu.com/community/MacBookPro6-2/Maverick

I suspect you should use the non-free, aka non-libre, but gratis
proprietary nvidia driver.

> 
> > Do you need perfect, very fast 3D acceleration?
> Yep, but the drivers should be free.
> 
> > What screen resolution will you use?
> 1680 x 1050
> But I'm not sure about this one.
> 
> I also forgot to mention that I want to be able to switch between
> GPUs. What should I use for this purpose? What about VGA switcheroo?
> 
> 
> Cheers.




-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1328087549.7278.20.camel@localhost.localdomain

Wheezy. Xorg failure at AMD Brazos netbook

[Leonid Korostyshevski]

Hello, list!

Have installed Wheezy weekly build 30-01-2012 but cannot log into a fresh
system: there is just a noise on a screen instead of a logon screen. Cannot
escape to text console, Ctrl+Alt+F1...Fn does not works. Ctrl+Alt+PrtScr+B
works, though. Also, IMHO it is a good idea to enable Ctrl+Alt+Backspace
for "testing" distro.

Not sure about "recovery" mode naming as a GRUB2 entry. It leads to the
same noise on screen, not to safe plain VGA CLI environment, as it suppose
to be IMHO. "Testing" shouldn't be "stuck with" IMHO :0)

Hardware in use - netbook on AMD Brazos (C-60 + ATI 6250). No 'lspci' at
the moment, sorry. During installation process, 3.1.x.-486 kernel was
chosen.

Would you, please, to give an advice how to override Xorg fault?

Thanks a lot!
LK

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Stayvoid]

Hello!

> What version of Debian do you have installed?
I'm using gNewSense (AFAIK it's based on Squeeze).

> What Nvidia graphics?
NVIDIA GeForce 330M + Intel HD

> What computer?
MacBookPro6,2

> Do you need perfect, very fast 3D acceleration?
Yep, but the drivers should be free.

> What screen resolution will you use?
1680 x 1050
But I'm not sure about this one.

I also forgot to mention that I want to be able to switch between
GPUs. What should I use for this purpose? What about VGA switcheroo?


Cheers.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAK5fS_HpTmrx-EjkLUxpFUbEqfgKEKN++=6knhx+ixjjkh3...@mail.gmail.com

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Bob Proulx]

Gilbert Sullivan wrote:
> Brian wrote:
> > Sven Joachim wrote:
> >> Sven,
> >>  maintainer of the "borked" package
> > 
> > Seeing as you mention it - it is time to say 'thank you'.
> 
> + 1 to this.

+1 from me as well.  I am happily using the nouveau package and driver
on several machines.  It made using them as easy as apt-get install
when otherwise I would have been scrambling for a solution.

Thanks Sven!

Bob


signature.asc
Description: Digital signature

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Gilbert Sullivan]

On 01/31/2012 03:07 PM, Brian wrote:
> On Tue 31 Jan 2012 at 20:51:21 +0100, Sven Joachim wrote:
> 
>> Sven,
>>  maintainer of the "borked" package
> 
> Seeing as you mention it - it is time to say 'thank you'.
> 
> 

+ 1 to this.

Many thanks to Sven, not only for his work as a package maintainer but
as a contributor on this newsgroup.

The nouveau drivers made my Dell Precision workstation usable for the
last few months of its life. The binary blobs caused all sorts of
headaches with the various DEs I used on that computer (Gnome, LXDE,
Xfce). All of the little gotchas went away when I switched to nouveau.

Yeah, there were a couple of issues with nouveau, too. But -- because it
was open source -- I was able to figure some of them out myself, and get
answers for others -- most notably from Sven, himself. Having a properly
functioning DE is a lot more important for this old curmudgeon than
having 3D acceleration.

Regards,
Gilbert


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4f2868c0.4010...@comcast.net

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Ralf Mardorf]

On Tue, 2012-01-31 at 19:45 +, Brian wrote:
> On Tue 31 Jan 2012 at 21:30:59 +0300, Stayvoid wrote:
> 
> > Should I install Nouveau drivers after the installation of the server 
> > itself?
> 
> If you know you have an Nvidia card install xserver-xorg-video-nouveau
> first.

Camaleón asked for the goals. I agree with this question.

What version of Debian do you have installed?
What Nvidia graphics?
What computer?
Do you need perfect, very fast 3D acceleration?
What screen resolution will you use?

Depending to the answers one of 3 or 4 drivers might be ok.
Usually people will use the proprietary nvidia driver or the FLOSS
nouveau driver. Sometimes the old nv driver is the best way to go. Very
seldom vesa could be needed.

2 Cents,
Ralf


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1328046785.7278.14.camel@localhost.localdomain

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Brian]

On Tue 31 Jan 2012 at 20:51:21 +0100, Sven Joachim wrote:

> Sven,
>  maintainer of the "borked" package

Seeing as you mention it - it is time to say 'thank you'.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120131200715.GC917@desktop

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Brian]

On Tue 31 Jan 2012 at 21:30:59 +0300, Stayvoid wrote:

> Should I install Nouveau drivers after the installation of the server itself?

If you know you have an Nvidia card install xserver-xorg-video-nouveau
first.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120131194549.GB917@desktop

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Sven Joachim]

On 2012-01-31 20:29 +0100, Ralf Mardorf wrote:

> xserver-xorg includes X and xserver-xorg-video-nouveau includes a borked
> Nvidia driver for X.

This "borked" driver works fine for me.  YMMV, of course.

Sven,
 maintainer of the "borked" package


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/878vknk5vq@turtle.gmx.de

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Ralf Mardorf]

On Tue, 2012-01-31 at 19:47 +0300, Stayvoid wrote:
> Hello there!
> 
> What's the difference between these packages?
> 
> 
> Cheers.

xserver-xorg includes X and xserver-xorg-video-nouveau includes a borked
Nvidia driver for X.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1328038145.7278.5.camel@localhost.localdomain

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Camaleón]

On Tue, 31 Jan 2012 21:30:59 +0300, Stayvoid wrote:

>> In brief, the former will install (by dependencies) the full Xorg
>> server with all of the VGA drivers...

> Will it install Nouveau this way?

Which one, "xserver-xorg"? Yes, it will. And lot of additional stuff you 
may or may not want.

> Should I install Nouveau drivers after the installation of the server
> itself?

You're going too fast :-)

First define your goals and your current situation then we will able to 
provide the best solution for your needs.

Greetings,


-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/jg9dpp$6o6$1...@dough.gmane.org

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Stayvoid]

> In brief, the former will install (by dependencies) the full Xorg server
> with all of the VGA drivers...
Will it install Nouveau this way?

Should I install Nouveau drivers after the installation of the server itself?


Cheers.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAK5fS_HEFgXH9tiCLSeJx3tCjUzVCPqPnYVeBXsH=lzdstx...@mail.gmail.com

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Camaleón]

On Tue, 31 Jan 2012 19:47:29 +0300, Stayvoid wrote:

> What's the difference between these packages?

You can go here, search and read:

http://www.debian.org/distrib/packages

***
Package: xserver-xorg (1:7.5+8+squeeze1)
the X.Org X server

This package depends on the full suite of the server and drivers for the 
X.Org X server. It does not provide the actual server itself. 
***


***
Package: xserver-xorg-video-nouveau (1:0.0.15+git20100329+7858345-5)
X.Org X server -- Nouveau display driver (experimental)

This driver for the X.Org X server (see xserver-xorg for a further 
description) provides support for NVIDIA Riva, TNT, GeForce, and Quadro 
cards.

Although the nouveau project aims to provide full 3D support it is not 
yet complete, and these packages do not include any 3D support. Users 
requiring 3D support should use the non-free "nvidia" driver.

This package is built from the FreeDesktop.org xf86-video-nouveau driver. 
***

In brief, the former will install (by dependencies) the full Xorg server 
with all of the VGA drivers while the latter is just a set of FOSS  
drivers for nvidia cards.

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/jg98rp$6o6$8...@dough.gmane.org

Re: xserver-xorg vs. xserver-xorg-video-nouveau

[Sven Joachim]

On 2012-01-31 17:47 +0100, Stayvoid wrote:

> What's the difference between these packages?

See the package descriptions.  The xserver-xorg-video-nouveau package
contains a video driver for NVidia cards, while xserver-xorg is a
metapackage that depends on all necessary parts of the X window system:
The X server, input and video drivers and keyboard data.

Sven


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/8739avlqxb@turtle.gmx.de

xserver-xorg vs. xserver-xorg-video-nouveau

[Stayvoid]

Hello there!

What's the difference between these packages?


Cheers.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cak5fs_gafic92v17y9d_homwukr7dz8yguwura9c6f1jpry...@mail.gmail.com

Re: Re: Re: Squeeze 6.0.3 -> 6.0.4 broke my Xorg

[hardpenguin]

False alarm. I didn't know I need to reinstall proprietary NVIDIA
drivers. Now I made it and it works.

-- 
  
  hardpeng...@fastmail.fm

-- 
http://www.fastmail.fm - Email service worth paying for. Try it for free


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1327948717.2039.140661029897...@webmail.messagingengine.com

Re: Re: Squeeze 6.0.3 -> 6.0.4 broke my Xorg

[hardpenguin]

Hello there.

I'm pretty sure, last update (6.0.4) broke my Xorg or something. Before
update I could play my games without problem (King Arthur's Gold,
Baldur's Gate [Wine], League of Legends [Wine]), now they cannot
initialise display. Error message from KAG:

Linux 2.6.38-bpo.2-686 #1 SMP Tue Jun 14 11:43:18 UTC 2011 i686
X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  137 (NV-GLX)
  Minor opcode of failed request:  4 ()
  Resource id in failed request:  0x302
  Serial number of failed request:  36
  Current serial number in output stream:  36

Then crash. And error message from BG:

err:winediag:X11DRV_WineGL_InitOpenglInfo Unable to activate OpenGL
context, most likely your OpenGL drivers haven't been installed
correctly
err:wgl:X11DRV_WineGL_InitOpenglInfo  couldn't initialize OpenGL, expect
problems
err:d3d_caps:WineD3D_CreateFakeGLContext Can't find a suitable
iPixelFormat.

I didn't change anything in my system so I'm pretty sure it is because
of update.
-- 
  
  hardpeng...@fastmail.fm

-- 
http://www.fastmail.fm - Choose from over 50 domains or use your own


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1327938452.15490.140661029819...@webmail.messagingengine.com

Re: Squeeze 6.0.3 -> 6.0.4 broke my Xorg

[Alex Hutton]

On 30 January 2012 22:56, Ramon Hofer  wrote:
> On Mon, 30 Jan 2012 21:35:25 +1100, Alex Hutton wrote:
>
>> I'm running a dual monitor setup with fglrx.
>>
>> I have upgraded from Squeeze 6.0.3 to 6.0.4 and after reboot I only have
>> a one monitor desktop.
>>
>> I am wondering if anyone could tell me where my old xorg.conf went to?
>>
>> And is there a way to configure apt so that upgrades stop clobbering my
>> xorg.conf?
>
> I'm running a dual screen setup with my laptop and Squeeze too. But I
> didn't have any problems after updating.
>
> Usually I get asked what I want to do when there are new config files.
> Did you update with the yes option or something like this?
>
>
> Best regards
> Ramon
>

Thanks  everyone for the reply.

I must apologise... it appears the cord was loose. It's funny that
when a monitor is not plugged in during Xorg's startup, it goes to
single desktop rather than starting a dual setup and allowing the
mouse to pass off one screen and into a blank area.

Now it appears in my panic I've done something to the config file
because now even after I restored what I thought was the working
backup I'm only getting one screen (but this time it's the other
screen).

Oh well :) ... I'll  sort it out when I have the time.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAAvq_=ciE5RufQOB2qAM3awG5HEHKfDO=sujnn8veenhd8v...@mail.gmail.com

Re: Squeeze 6.0.3 -> 6.0.4 broke my Xorg

[Ramon Hofer]

On Mon, 30 Jan 2012 21:35:25 +1100, Alex Hutton wrote:

> I'm running a dual monitor setup with fglrx.
> 
> I have upgraded from Squeeze 6.0.3 to 6.0.4 and after reboot I only have
> a one monitor desktop.
> 
> I am wondering if anyone could tell me where my old xorg.conf went to?
> 
> And is there a way to configure apt so that upgrades stop clobbering my
> xorg.conf?

I'm running a dual screen setup with my laptop and Squeeze too. But I 
didn't have any problems after updating.

Usually I get asked what I want to do when there are new config files.
Did you update with the yes option or something like this?


Best regards
Ramon


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/jg60h0$9o5$2...@dough.gmane.org

Re: Squeeze 6.0.3 -> 6.0.4 broke my Xorg

[Scott Ferguson]

On 30/01/12 21:35, Alex Hutton wrote:
> Hi,
> 
> I'm running a dual monitor setup with fglrx.
> 
> I have upgraded from Squeeze 6.0.3 to 6.0.4 and after reboot I only
> have a one monitor desktop.
> 
> I am wondering if anyone could tell me where my old xorg.conf went to?

No idea - did you create one? Or are you just assuming you had one, and
now that your dual monitor setup is no longer working, assuming the
point release broke it?

Did you not make a backup?

I've run the latest point release on half a dozen Squeeze boxen running
KDE or Fluxbox - all use an xorg.conf, none had any problems.

I've never had a point release eat a file (in decades) - and every time
a config file is modified I've been prompted to chose which version to keep.

Relevant parts to the updates common to all my boxen updated so far:-
The following packages will be upgraded:
x11-common xorg xserver-common xserver-xorg xserver-xorg-core
xserver-xorg-input-all xserver-xorg-video-all

I stepped through one of the updates and can't work out how your
xorg.conf could possibly have been affected.

I suggest you try restarting your xserver (or rebooting).

> 
> And is there a way to configure apt so that upgrades stop clobbering
> my xorg.conf?

Why - seems like developing a strategy for dealing with an invasion of
little green men? ;-p

A. no-one else has reported the problem - seems unlikely the point
release picked on you alone.
B. $ cp /etc/X11/xorg.conf ~/

> 
> Cheers,
> Alex
> 
> 

Now would be a good time to consider a backup policy. :-)


Cheers

-- 
Iceweasel/Firefox extensions for finding answers to Debian questions:-
https://addons.mozilla.org/en-US/firefox/collections/Scott_Ferguson/debian/

NOTE: new update available for Debian Buttons
(New button for querying Debian Developer Package):-
https://addons.mozilla.org/en-US/firefox/addon/debian-buttons/


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4f268368.1080...@gmail.com

Re: Squeeze 6.0.3 -> 6.0.4 broke my Xorg

[Alexey Eromenko]

hmmm... ?
First time I heard that a point update could cause it...

-- 
-Alexey Eromenko "Technologov"


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAOJ6w=fzr+tcbcl2gxy4esdhkpqzzx7jam-2_h-bzpvoxsb...@mail.gmail.com

Squeeze 6.0.3 -> 6.0.4 broke my Xorg

[Alex Hutton]

Hi,

I'm running a dual monitor setup with fglrx.

I have upgraded from Squeeze 6.0.3 to 6.0.4 and after reboot I only
have a one monitor desktop.

I am wondering if anyone could tell me where my old xorg.conf went to?

And is there a way to configure apt so that upgrades stop clobbering
my xorg.conf?

Cheers,
Alex


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAAvq_=fkH9rjW7+9=dv27hqamwtanc3khslqrcz9m9whp0x...@mail.gmail.com

Re: Howto asses possible damage from downgrade Xorg

[Lisi]

On Sunday 16 October 2011 18:00:35 Harry Putnam wrote:
>  what does `stable-bpo' mean at:
> http://packages.qa.debian.org/x/xorg-server.html

Stable-bpo is stable-backports.

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201110161843.27844.lisi.re...@gmail.com

Re: Howto asses possible damage from downgrade Xorg

[Camaleón]

On Sun, 16 Oct 2011 12:00:35 -0500, Harry Putnam wrote:

> Camaleón  writes:
> 
>>> Can anyone guide me on this, or is this the kind of thing I should
>>> install a vm guest for?
>>
>> Synaptic makes a good job when it comes to manage the versions of the
>> packages you want to install. You select the desired package you want
>> to downgrade and jump to the "Versions" tab for instructions.
> 
> I must not have the screens you do.  Starting synaptic and finding
> `xserver-xorg-core'
> 
> For a moment there I was a bit stymied since there appears to be no
> `versions tab'.. but finally figured out I needed to press `properties'
> first.

Sorry, I must have tweaked the layout the first time I installed Debian 
and left that way. Did not remember it was not the default setting.

> But the only version shown is 2:1.11.1-1

So you have no previous package version installed?

> Somebody posted what that notation means earlier but not finding the
> info now... what does the `2' indicate?

Debian Policy Manual explains better:

5.6.12 Version
http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version

>>> Is there a page that just has 1 massive list?
>>
>> See above. Not a "just-one-massive" list though, but a "per package"
>> version comparison.
> 
> Thanks for the excellent help and URLs.
> 
> xserver-xorg   1:7.6+9
> xwerver-xorg-core  2:1.11
> 
> I think it is the `core' pkg that is referred to on the xorg list when
> the speak of the Xorg version.
> 
> aptitude show xserver-xorg says:
> 
>  This package depends on the full suite of the server and drivers for
>  the X.Org X server.  It does not provide the actual server itself.
> 
> Why so confusing... the name is xserver-xorg and yet it is not the
> server?

Xorg (upstream project) latest stable version is 7.6 (this one matches 
with the "xserver-xorg" package). But that's all I can tell for these two 
packages, I don't know why there exits both given that xorg server 
binaries are only provided by "xserver-xorg-core".

> Oh, and what does `stable-bpo' mean at:
> http://packages.qa.debian.org/x/xorg-server.html

"-bpo" tag indicates a package is from the "backports" repositories:

http://backports-master.debian.org/

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.10.16.17.20...@gmail.com

Re: Howto asses possible damage from downgrade Xorg

[Harry Putnam]

Camaleón  writes:


[...]

>> I'd like to experiment with the previous version 1.10.  Compare certain
>> behavior against the current version. But don't know what I'm doing well
>> enough to make a good assessment of what damage may be done to my system
>> by downgrading like that on such an important piece of software, that
>> has many many ramifications.
>> 
>> Can anyone guide me on this, or is this the kind of thing I should
>> install a vm guest for?
>
> Synaptic makes a good job when it comes to manage the versions of the 
> packages you want to install. You select the desired package you want to 
> downgrade and jump to the "Versions" tab for instructions.

I must not have the screens you do.  Starting synaptic and finding
`xserver-xorg-core'

For a moment there I was a bit stymied since there appears to be no
`versions tab'.. but finally figured out I needed to press
`properties' first.

But the only version shown is 2:1.11.1-1

Somebody posted what that notation means earlier but not finding the
info now... what does the `2' indicate?

[...]

>> Is there a page that just has 1 massive list?
>
> See above. Not a "just-one-massive" list though, but a "per package" 
> version comparison.

Thanks for the excellent help and URLs.

xserver-xorg   1:7.6+9
xwerver-xorg-core  2:1.11

I think it is the `core' pkg that is referred to on the xorg list when
the speak of the Xorg version.

aptitude show xserver-xorg says:

 This package depends on the full suite of the server and drivers for
 the X.Org X server.  It does not provide the actual server itself.

Why so confusing... the name is xserver-xorg and yet it is not the
server?

Oh, and what does `stable-bpo' mean at:
http://packages.qa.debian.org/x/xorg-server.html


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87fwisq3bg@newsguy.com

Re: Howto asses possible damage from downgrade Xorg

[Camaleón]

On Sat, 15 Oct 2011 09:33:21 -0500, Harry Putnam wrote:

> Running recently installed wheezy system
> 
> I see this version information concerning Xorg server:
> 
>  aptitude versions xserver-xorg-core
> i A 2:1.11.1-1   testing  500
>  
> I'd like to experiment with the previous version 1.10.  Compare certain
> behavior against the current version. But don't know what I'm doing well
> enough to make a good assessment of what damage may be done to my system
> by downgrading like that on such an important piece of software, that
> has many many ramifications.
> 
> Can anyone guide me on this, or is this the kind of thing I should
> install a vm guest for?

Synaptic makes a good job when it comes to manage the versions of the 
packages you want to install. You select the desired package you want to 
downgrade and jump to the "Versions" tab for instructions.

If you get any warning, dependency errors or extra package that are going 
to be downgraded, stop. Needless to say using a older version of Xorg can 
be problematic so don't do it unless you know how to recover your system 
from any unexpected situation.

> Can anyone say what version of Xorg is current in `stable'? 

7.5 ("xserver-xorg-core" is 1.7.7)

> Further, how can access that kind of information?  

Using the web package search service:

http://www.debian.org/distrib/packages

> Is there a list somewhere of the packages current on stable, testing,
> unstable?

http://packages.qa.debian.org/x/xorg.html

(left column, "versions" sub-section)
 
> I see this site http://packages.debian.org/wheezy/ where one could find
> that information but it has the software separated into the various sub
> divisions.
> 
> Is there a page that just has 1 massive list?

See above. Not a "just-one-massive" list though, but a "per package" 
version comparison.

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.10.15.20.28...@gmail.com

Howto asses possible damage from downgrade Xorg

[Harry Putnam]

Running recently installed wheezy system

I see this version information concerning Xorg server:

 aptitude versions xserver-xorg-core
i A 2:1.11.1-1   testing  500
 
I'd like to experiment with the previous version 1.10.  Compare
certain behavior against the current version. But don't know what I'm
doing well enough to make a good assessment of what damage may be done
to my system by downgrading like that on such an important piece of
software, that has many many ramifications.

Can anyone guide me on this, or is this the kind of thing I should
install a vm guest for?

Can anyone say what version of Xorg is current in `stable'?
Further, how can access that kind of information?  Is there a list
somewhere of the packages current on stable, testing, unstable?

I see this site http://packages.debian.org/wheezy/ where one could
find that information but it has the software separated into the
various sub divisions.  

Is there a page that just has 1 massive list?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/8762jqz5n2@newsguy.com

Re: `Xorg -configure' failure

[Tom H]

On Fri, Oct 7, 2011 at 9:52 PM, Scott Ferguson
 wrote:
> On 08/10/11 03:56, Harry Putnam wrote:
>> Scott Ferguson  writes:
>>
>> [...]
>>
> It's considered bad manners to cross post - why waste more peoples
> time?

 Why is that wasting anyones time.  Some people read it here some
 there, if they don't like the subject or content they move on.
>
> What happens it that most lists (officially or otherwise) have people
> who try and make sure all requests for assistance are answered - when
> you cross post it can happen that two people on different lists invest
> time (that could be spent elsewhere) on answering a question. Only one
> correct solution is useful - so the other work is redundant.
> In this instance the issue *is* upstream (X.org or the
> freedesktop.org.) - while I've suggested solutions that may work
> (work-arounds), the best solutions are ones made upstream - and they'll
> take time to come downstream.

I disagree. Even on this one list, there may be more than one person
"investing time" to answer a post. Big deal! As long as it isn't
no-genune, nuisance post as we've had in the past - and will probably
have in the future.

This "don't cross-post" convention is a pre-historic inheritance from
when there were a dozen Linux users subscribing to the same half-dozen
lists...


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAOdo=swezzuqvhfgzfrkuybpezcg-qxqrsfuh9+h34e25sh...@mail.gmail.com

Re: where are xorg-macros

[Harry Putnam]

Wayne Topa  writes:

> On 10/09/2011 07:16 PM, Harry Putnam wrote:
>> I've looked around with google and on xorg home site for this.
>>
>> xorg-macros
>>
>> I find reference to it but not how to get it.
>
> You use the debian tools, such as apt-cache.
> ie
>
> apt-cache search xorg-macros
> xutils-dev - X Window System utility programs for development
> Which is the package that contains xorg-macros
>
> apt-cache show xutils-dev
> will show you the information on xutils-dev package.

Ahh nice.  thanks


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87k48d8u9o@newsguy.com

Re: where are xorg-macros

[Wayne Topa]

On 10/09/2011 07:16 PM, Harry Putnam wrote:

I've looked around with google and on xorg home site for this.

xorg-macros

I find reference to it but not how to get it.


You use the debian tools, such as apt-cache.
ie

apt-cache search xorg-macros
xutils-dev - X Window System utility programs for development
Which is the package that contains xorg-macros

apt-cache show xutils-dev
will show you the information on xutils-dev package.



Do you have the debian-reference package installed?  You will find
that to be a good reference to how to run/mantain/understand the
Debian System.




When I run ./autogen.sh in a git clone of an xorg driver I get this
output. (I added the spacing and asterisks)

autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal

*
configure.ac:33: error: must install xorg-macros 1.8 or later before running 
autoconf/autogen
*

configure.ac:33: the top level
autom4te: /usr/bin/m4 failed with exit status: 1
aclocal: /usr/bin/autom4te failed with exit status: 1
autoreconf: aclocal failed with exit status: 1

----   ---=---   -  

I'm not finding where this might be found or if it might be part of a
pkg.

Anyone know?




   * Turkish - detected
   * English

   * English

  <#>


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4e923598.8050...@gmail.com

Re: where are xorg-macros

[Scott Ferguson]

On 10/10/11 10:16, Harry Putnam wrote:
> I've looked around with google and on xorg home site for this.
> 
> xorg-macros
> 
> I find reference to it but not how to get it.
> 
> When I run ./autogen.sh in a git clone of an xorg driver I get this
> output. (I added the spacing and asterisks)
> 
> autoreconf: Entering directory `.'
> autoreconf: configure.ac: not using Gettext
> autoreconf: running: aclocal 
> 
> *
> configure.ac:33: error: must install xorg-macros 1.8 or later before running 
> autoconf/autogen
> *
> 
> configure.ac:33: the top level
> autom4te: /usr/bin/m4 failed with exit status: 1
> aclocal: /usr/bin/autom4te failed with exit status: 1
> autoreconf: aclocal failed with exit status: 1
> 
> ----   ---=---   -   
> 
> I'm not finding where this might be found or if it might be part of a
> pkg.
> 
> Anyone know?
> 
> 
It's part of xutils-dev

Cheers


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4e922cd8.6080...@gmail.com

where are xorg-macros

[Harry Putnam]

I've looked around with google and on xorg home site for this.

xorg-macros

I find reference to it but not how to get it.

When I run ./autogen.sh in a git clone of an xorg driver I get this
output. (I added the spacing and asterisks)

autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal 

*
configure.ac:33: error: must install xorg-macros 1.8 or later before running 
autoconf/autogen
*

configure.ac:33: the top level
autom4te: /usr/bin/m4 failed with exit status: 1
aclocal: /usr/bin/autom4te failed with exit status: 1
autoreconf: aclocal failed with exit status: 1

----   ---=---   -   

I'm not finding where this might be found or if it might be part of a
pkg.

Anyone know?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87sjn17o2j@newsguy.com

Re: `Xorg -configure' failure

[Scott Ferguson]

On 08/10/11 13:52, Harry Putnam wrote:
> Scott Ferguson  writes:
> 
> [...] snipped 
> 
>> An alternative approach to a similar ends is available in KDE - use a
>> very large desktop and "zoom" into particular areas. Alternatively just
>> use more virtual desktops.
> 
> Thanks for the nice summary of where things stand and what to do about
> them.
> 
> The one above looks most appealing for the lazy.  I used kde for a
> long time at one time but grew to dislike it and wanted the simplicity
> of something like fluxbox.  So it would be no biggie to go back to KDE
> just for that panning stuff.

Fluxbox may well have a similar function - I'm just unfamiliar with it
(haven't used it extensively for some years).

Perhaps someone on the list can advise before you swap one learning
curve for another.

> 
> Using more virtual desktops really is so far from being the same as
> the ability to pan that its not really an alternative.  I rarely use
> more than 3/4.
> 
> I'm going to try the KDE approach now and see what its like.
> 
> I sent you a hellishly long email with all the threaded messages from
> all three threads.

Recieved thankyou (and replied to)



cheers


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4e8fc144.9020...@gmail.com

Re: `Xorg -configure' failure

[Harry Putnam]

Scott Ferguson  writes:

[...] snipped 

> An alternative approach to a similar ends is available in KDE - use a
> very large desktop and "zoom" into particular areas. Alternatively just
> use more virtual desktops.

Thanks for the nice summary of where things stand and what to do about
them.

The one above looks most appealing for the lazy.  I used kde for a
long time at one time but grew to dislike it and wanted the simplicity
of something like fluxbox.  So it would be no biggie to go back to KDE
just for that panning stuff.

Using more virtual desktops really is so far from being the same as
the ability to pan that its not really an alternative.  I rarely use
more than 3/4.

I'm going to try the KDE approach now and see what its like.

I sent you a hellishly long email with all the threaded messages from
all three threads.  Probably would be useful at some point.  When
you've gotten some of your time back maybe.  At least all the
information is there in some kind of order.

Thanks for you time and input.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87fwj46vpt@newsguy.com

Re: `Xorg -configure' failure

[Harry Putnam]

Sven Joachim  writes:

> The nv driver is gone and it's not coming back unless somebody
> reintroduces it, which is highly unlikely.  If you think about doing
> that yourself: http://bugs.debian.org/383465 is the nut you have to
> crack before the ftp-masters will let this driver in.

It only came up for me, in that I used it on a different linux distro
for a good while without problems so wondered if it would halp my
situation on debian.

About bug: 383465, egad what a mess eh?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87k48g6wcq@newsguy.com

Re: `Xorg -configure' failure

[Scott Ferguson]

On 08/10/11 03:56, Harry Putnam wrote:
> Scott Ferguson  writes:
> 
> [...]
> 
>>>> It's considered bad manners to cross post - why waste more peoples
>>>> time?
>>>
>>> Why is that wasting anyones time.  Some people read it here some 
>>> there, if they don't like the subject or content they move on.

What happens it that most lists (officially or otherwise) have people
who try and make sure all requests for assistance are answered - when
you cross post it can happen that two people on different lists invest
time (that could be spent elsewhere) on answering a question. Only one
correct solution is useful - so the other work is redundant.
In this instance the issue *is* upstream (X.org or the
freedesktop.org.) - while I've suggested solutions that may work
(work-arounds), the best solutions are ones made upstream - and they'll
take time to come downstream.

>> Nice attitude.
> 
> I'm not really sure why that is a bad attitude still but you have
> humbled me with your comment below.

And my post was unprofessional at best. Unnecessarily harsh. You don't
need excuses from me.

> 
>> Some people read things - that takes time.
> 
> I do suffer from some unwillingness to read some kinds of stuff.
> You might call it lazy and maybe it is, but what happens is that I do
> not understand large parts of it, and therefore am quite unable to
> really absorb the meaning.

Nothing unique there.

> 
> For me even to understand what the bugs we've discussed are truly
> saying would require going back to very basic stuff and studying hard
> for some mnths to begin to get a handle on this stuff.

It's either that or wait for a bug fix to trickle down (or revert to
earlier software). My method of attempting to fix everything myself is
not for everyone.

> 
> I guess I had hoped to find some solution without having to spend
> hours and hours pounding away at stuff I don't understand yet.
> 
> I've been able to run linux since early 90s,

When I recall almost *all* monitors required hand tweaking to configure
- whereas now X rarely requires tweaking except by experts or those that
require unusual customization.

> and have been able to
> have the large roomy desktop that pans since probably 97 or so.  I
> thought it could probably be done now too.

It can - with provisos. Also consider that your video card has three
screens.

> 
>> Not counting this post - there are 26 posts in the three threads you
>> have on this subject (panning) including three xorg logs - without
>> reading all of them I can't determine what *isn't* relevant. If you're
>> so certain about what it costs other people maybe you should fix your
>> own problems.
> 
> Again, I stand humbled. 

Was not my intention - my apologies. I took on more than I have time
for, and that incompetence translated into rudeness.

Hopefully you'll find a quick solution. At least these threads/posts can
provide others with a reference to what has been tried.

> I do really appreciate your work and the
> effort you've put in.  With your help I now have some understanding of
> how to use xrandr (note I say SOME understanding [very little])
> 
> Let me explain something at this point.  I did not realize any
> experiments I do with xrandr commands are regarded as basic changes in
> my setup.  I did not realize the xrandr setting from the command line
> are persistent.

They're not.
But something has changed - and it's a huge amount of material to parse
through trying to determine what, and whether those changes are
permanent or pertinent.

Again, my apologies - but I don't have the available time to pursue this
further (I still have many emails just to read). If I think of something
I will post.

I'd suggest you disable unused displays, freeing up space in your
virtual screen. Read the man for xrandr, the wiki.debian.org stuff is
outdated - still relevant, but no longer the full story. Incorporate
your xrandr changes into xorg.conf. Xorg.conf doesn't need to be
complete like in Lenny - but any "sections" must be complete. ie. udev
will create what's necessary unless it's hard coded into xorg.conf. Use
xrandr to create modes. Use xorg.conf to make use of them.

An alternative approach to a similar ends is available in KDE - use a
very large desktop and "zoom" into particular areas. Alternatively just
use more virtual desktops.

Good luck.



Cheers


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4e8facd8.30...@gmail.com

Re: `Xorg -configure' failure

[Sven Joachim]

On 2011-10-07 19:53 +0200, Ralf Mardorf wrote:

> On Fri, 2011-10-07 at 11:56 -0500, Harry Putnam wrote:
>
>> Do you have any recommendation?  On gentoo I was using the `nv' driver
>> that I do not see available for debian.
>
> I'm using testing, there's no nv driver for testing, but I'm using X
> from stable.
>
> On my testing it's xserver-xorg-video-nv 1:2.1.17-3, the internet says
> http://packages.debian.org/search?keywords=xserver-xorg-video-nv
> there'll be a nv driver for SID :).

You read wrong, those are outdated versions for unofficial architectures.

> So ONLY with testing we do have bad luck regarding to the nv driver.

The nv driver is gone and it's not coming back unless somebody
reintroduces it, which is highly unlikely.  If you think about doing
that yourself: http://bugs.debian.org/383465 is the nut you have to
crack before the ftp-masters will let this driver in.

Sven


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87ty7ko5y2@turtle.gmx.de

Re: `Xorg -configure' failure

[Harry Putnam]

Ralf Mardorf  writes:

> On Fri, 2011-10-07 at 11:56 -0500, Harry Putnam wrote:
>
>> Do you have any recommendation?  On gentoo I was using the `nv' driver
>> that I do not see available for debian.
>
> I'm using testing, there's no nv driver for testing, but I'm using X
> from stable.
>
> On my testing it's xserver-xorg-video-nv 1:2.1.17-3, the internet says
> http://packages.debian.org/search?keywords=xserver-xorg-video-nv
> there'll be a nv driver for SID :). So ONLY with testing we do have bad
> luck regarding to the nv driver.

Thanks for the info.  I'm just learning the whys and wherefores of
debian so please forgive any obviously stupid remarks or questions. 

Is it possible to get the pkg for sid into a testing setup.

I don't know what happens with cross use like that in the debian
scheme. 

Is installing that pkg likely to solve any problems raised in recent
threads regarding virtual screen size and mouse panning around on
oversize desktop?

You must have some different URLS in /etc/apt/sources.list

When I search the database these are all that turn up.

ap -s xserver-xorg-video-n
  
  i A xserver-xorg-video-neomagic - X.Org X server -- Neomag [...]
  i A xserver-xorg-video-nouveau  - X.Org X server -- Nouvea [...]
  p   xserver-xorg-video-nouveau-dbg  - X.Org X server -- Nouvea [..]
  p   xserver-xorg-video-nvidia   - NVIDIA binary Xorg driver   
  
  v   xserver-xorg-video-nvidia-any   -
   
Do you mind posting the sources.list for your `testing' rig.

I'm running `wheezy' and am a bit confused as to whether that is
`testing' or that `testing' is something else.

 my /etc/apt/sources.list

deb http://ftp.us.debian.org/debian/ wheezy main
deb-src http://ftp.us.debian.org/debian/ wheezy main

deb http://security.debian.org/ wheezy/updates main
deb-src http://security.debian.org/ wheezy/updates main


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87bots8q5n@newsguy.com

Re: `Xorg -configure' failure

[Ralf Mardorf]

On Fri, 2011-10-07 at 11:56 -0500, Harry Putnam wrote:

> Do you have any recommendation?  On gentoo I was using the `nv' driver
> that I do not see available for debian.

I'm using testing, there's no nv driver for testing, but I'm using X
from stable.

On my testing it's xserver-xorg-video-nv 1:2.1.17-3, the internet says
http://packages.debian.org/search?keywords=xserver-xorg-video-nv
there'll be a nv driver for SID :). So ONLY with testing we do have bad
luck regarding to the nv driver.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1318010035.11998.37.camel@debian

Re: `Xorg -configure' failure

[Harry Putnam]

Scott Ferguson  writes:

[...]

>>> It's considered bad manners to cross post - why waste more peoples
>>> time?
>> 
>> Why is that wasting anyones time.  Some people read it here some 
>> there, if they don't like the subject or content they move on.
> Nice attitude.

I'm not really sure why that is a bad attitude still but you have
humbled me with your comment below.

> Some people read things - that takes time.

I do suffer from some unwillingness to read some kinds of stuff.
You might call it lazy and maybe it is, but what happens is that I do
not understand large parts of it, and therefore am quite unable to
really absorb the meaning.

For me even to understand what the bugs we've discussed are truly
saying would require going back to very basic stuff and studying hard
for some mnths to begin to get a handle on this stuff.

I guess I had hoped to find some solution without having to spend
hours and hours pounding away at stuff I don't understand yet.

I've been able to run linux since early 90s, and have been able to
have the large roomy desktop that pans since probably 97 or so.  I
thought it could probably be done now too.

> Not counting this post - there are 26 posts in the three threads you
> have on this subject (panning) including three xorg logs - without
> reading all of them I can't determine what *isn't* relevant. If you're
> so certain about what it costs other people maybe you should fix your
> own problems.

Again, I stand humbled.  I do really appreciate your work and the
effort you've put in.  With your help I now have some understanding of
how to use xrandr (note I say SOME understanding [very little])

Let me explain something at this point.  I did not realize any
experiments I do with xrandr commands are regarded as basic changes in
my setup.  I did not realize the xrandr setting from the command line
are persistent.

If you see differences in my logs posted its because of me
experimenting.   From this moment on, if you ask me to try something I
will first reboot.  This machine is not doing any work that cannot be
interrupted whenever needed so I'll reboot, try whatever you suggest.

Post the Xorg.0.log.  Then reboot again, and so back to whatever I
have currently been given from the automated X startup process.

An Xorg.0.log (following a reboot) is inlined at the end.

Further, I've made a compilation of the three threads in this list
where this problem is discussed or different aspects of it.

Its in the form of one long list of all the posts, in the order they
were posted, and there fore should be searchable and fairly easy to
jump around in.  You'll find lines like this:

----   ---=---   -   
Subject: whatever
----   ---=---   -   

With the subject line between demarking the different threads.

I've sent it to your gmail address at prettyfly.  I hope that is not
another boner mistake.
 
> The problem you are having (and there is a problem) is complex.

I'm starting to see that now...

> The panning I'm able to do is just up and down (1024x600 display inside
> a 1024x768 virtual screen) is on different hardware and software (ASUS
> PC Eeee 701SDs running Squeeze with Trinity KDE - it's also done with
> xorg.conf - not xrandr.
>
> When I try and pan using a similar setup to you I run into a problem
> with insufficient space left in the virtual screen (I "suspect").
> When I disable those unused screens I get "BadRRCrtc (invalid Crtc
> parameter)" errors. I don't know whether those errors apply to later
> Xorg releases (I only use stable).
>
> There are a number of work-arounds - within the above constraints I am

[...]

>
> I spent time this morning feeding three different xorg logs through a
> screen reader, multiple times - and you argue nothing has changed.
> You may be correct - but my ears disagree.
>
> If nothing has changed all logs would be almost identical.

Note my comments above about how I will proceed starting now.

I'm sorry to have posted so much confusing information.

[...]

>> Further more, we have already hit upon commands that have done what
>> I wanted.  It no longer requires testing.  The problem is that the
>> mouse is not being allowed to wander out into the Virtual size.
>
> Then you don't need the work-around I tested.

Not true.  Previously you were saying there was no bug concerning
panning and asked me to post any links I'd seen.

If there is or are workarounds then I am interested in trying them
out.

I may not have the skills necessary to do a good job of it, so it may
be a bit of a crap shoot.

>>>> Subsection "Display" Depth   24 Modes   "1280x1024&q

Re: `Xorg -configure' failure

[Hugo Vanwoerkom]

Scott Ferguson wrote:

On 07/10/11 02:44, Harry Putnam wrote:

[NOTE:  This post or very similar was also posted to
gmane.comp.freedesktop.xorg.]


It's considered bad manners to cross post - why waste more peoples time?



Only a waste of time *if* you read both lists...

Hugo


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/j6n2aa$etm$1...@dough.gmane.org

Re: `Xorg -configure' failure

[Scott Ferguson]

On 07/10/11 15:21, Harry Putnam wrote:
> Scott Ferguson  writes:
> 
>> On 07/10/11 02:44, Harry Putnam wrote:
>>> [NOTE:  This post or very similar was also posted to 
>>> gmane.comp.freedesktop.xorg.]
>> 
>> It's considered bad manners to cross post - why waste more peoples
>> time?
> 
> Why is that wasting anyones time.  Some people read it here some 
> there, if they don't like the subject or content they move on.
Nice attitude.
Some people read things - that takes time.

Not counting this post - there are 26 posts in the three threads you
have on this subject (panning) including three xorg logs - without
reading all of them I can't determine what *isn't* relevant. If you're
so certain about what it costs other people maybe you should fix your
own problems.

The problem you are having (and there is a problem) is complex.

The panning I'm able to do is just up and down (1024x600 display inside
a 1024x768 virtual screen) is on different hardware and software (ASUS
PC Eeee 701SDs running Squeeze with Trinity KDE - it's also done with
xorg.conf - not xrandr.

When I try and pan using a similar setup to you I run into a problem
with insufficient space left in the virtual screen (I "suspect").
When I disable those unused screens I get "BadRRCrtc (invalid Crtc
parameter)" errors. I don't know whether those errors apply to later
Xorg releases (I only use stable).

There are a number of work-arounds - within the above constraints I am
able to get limited panning by enlarging the borders.

Gnome 3 "apparently" gets around the problem using this patch:-
http://cgit.freedesktop.org/xorg/xserver/commit/?id=d45f5b2493bc0a2882bf972849b5c9c50cd533ca

Until the upstream fixes trickle down you might find this useful:-
http://sourceforge.net/projects/xcursorclamp/

Or patch with this:-
http://lists.x.org/archives/xorg-devel/2010-November/015495.html
or:-
http://lists.x.org/archives/xorg-devel/2011-June/023715.html

> Where is the waste?

Time I could have spent on other things rather than trying to follow
these posts and threads.

> 
> I don't understand you.  What settings are you speaking of.  I've 
> tried to supply any information you requested.  Please say plainly 
> what information you want, instead of contained obliquely in a 
> complaint.

I spent time this morning feeding three different xorg logs through a
screen reader, multiple times - and you argue nothing has changed.
You may be correct - but my ears disagree.

If nothing has changed all logs would be almost identical.

> 
> My current setting haven't changed at all.  I'm talking here about 
> trying to come at the problem from a little different angle.
> Although I actually doubt it will work, because I suspect the same
> bug that is preventing it working with xrandr will prevent xorg.conf
> using a Virtual parameter too.
> 
> Further more, we have already hit upon commands that have done what
> I wanted.  It no longer requires testing.  The problem is that the
> mouse is not being allowed to wander out into the Virtual size.

Then you don't need the work-around I tested.

> 
> [...]
> 
>>>> From Section "Screen"
>>> 
>>> [...]
>>> 
>>> Subsection "Display" Depth   24 Modes   "1280x1024"
>>> #"1024x768" "800x600" "640x480" Virtual 2048 1536 ViewPort
>>> 0 0 EndSubsection
>>> 
>>> [...]
>>> 
>>> Its the virtual size I'm after.
>> 
>> Then change the virtual size - not the *display* size. That
>> section refers to the display size for the default monitor (not
>> even the monitor you currently use).
> 
> No, you are wrong there... but it's my fault for not fully
> explaining the origin of that piece of xorg.conf.  That very
> xorg.conf was used on a CRT, but when I changed to a 25.5 lcd that
> same section worked there too when running Gentoo.

You were running nouveau on Gentoo?

> 
> So what I said about it being the same hardware is true.
>> 
>> If those are the setting you want, and they are supported by the 
>> *different display* - then that's all that needs to be in 
>> /etc/X11/xorg.conf - X will deal with everything else. However you
>> will need to use xrandr to disable your other screens (TV and
>> VGA).
> 
> What is all I need of xorg.conf?  Do you mean just what is printed 
> above between the elisions?  The subsection of the sub section.  Do 
> you mean it could just say:
> 
> Subsection "Display" Depth   24 Modes   "1280x1024"
> #"1024x768" "800x600" "640x480" Virtual 2048 1536 ViewPort

Re: `Xorg -configure' failure

[Harry Putnam]

Scott Ferguson  writes:

> On 07/10/11 02:44, Harry Putnam wrote:
>> [NOTE:  This post or very similar was also posted to
>> gmane.comp.freedesktop.xorg.]
>
> It's considered bad manners to cross post - why waste more peoples time?

Why is that wasting anyones time.  Some people read it here some
there, if they don't like the subject or content they move on.  Where
is the waste?

> So no point in me making suggestions - my tests were done with settings
> that are probably no longer relevant judging from what you've written
> here. I don't have time to read all the posts in various subsequent
> threads to try and find out what your current settings are.

I don't understand you.  What settings are you speaking of.  I've
tried to supply any information you requested.  Please say plainly
what information you want, instead of contained obliquely in a
complaint.

My current setting haven't changed at all.  I'm talking here about
trying to come at the problem from a little different angle.  Although
I actually doubt it will work, because I suspect the same bug that is
preventing it working with xrandr will prevent xorg.conf using a
Virtual parameter too.

Further more, we have already hit upon commands that have done what I
wanted.  It no longer requires testing.  The problem is that the mouse
is not being allowed to wander out into the Virtual size.

[...]
 
>>>From Section "Screen"
>> 
>>   [...]
>> 
>> Subsection "Display"
>> Depth   24
>> Modes   "1280x1024" #"1024x768" "800x600" "640x480"
>> Virtual 2048 1536 
>> ViewPort0 0
>> EndSubsection
>> 
>>   [...]
>> 
>> Its the virtual size I'm after. 
>
> Then change the virtual size - not the *display* size. That section
> refers to the display size for the default monitor (not even the monitor
> you currently use).

No, you are wrong there... but it's my fault for not fully explaining
the origin of that piece of xorg.conf.  That very xorg.conf was used
on a CRT, but when I changed to a 25.5 lcd that same section worked there
too when running Gentoo.

So what I said about it being the same hardware is true.
>
> If those are the setting you want, and they are supported by the
> *different display* - then that's all that needs to be in
> /etc/X11/xorg.conf - X will deal with everything else. However you will
> need to use xrandr to disable your other screens (TV and VGA).

What is all I need of xorg.conf?  Do you mean just what is printed
above between the elisions?  The subsection of the sub section.  Do
you mean it could just say:

 Subsection "Display"
 Depth   24
 Modes   "1280x1024" #"1024x768" "800x600" "640x480"
 Virtual 2048 1536 
 ViewPort0 0
     EndSubsection

>> Its worked on this same hardware in
>> the past under Gentoo linux.
>
> Perhaps you "mean" the video card is the same...
>
> A CRT monitor is *not* a LCD monitor. So you *don't* have the same
> hardware. Monitors *are* hardware.

See above.  And sorry for misleading in previous posts.  That xorg
conf began life on a 17 inch CRT but was later used on the very
hardware including the 25.5 inch lcd monitor that I am using now.

> Gentoo doesn't use Nouveau - you do. So don't expect the same results
> when software and hardware have changed.

So is Nouveau incompatible with the ability to pan?  Do I need to
change drivers, scrap Nouveau?
 
>> And using xrandr to attain the virtual size has been discussed at some
>> length in another thread...
>
> Not on this list. Virtual size was discussed in passing. Panning was
> discussed at length.

Now I'm really confused.  When you speak of panning, what is being
panned into?  Is that not virtual size out beyond the monitors real
estate.

>> so far it hasn't worked.  It appears to be
>> because of a bug caused by certain code that prevents the mouse from
>> panning out into the virtual size. 
>
> AFAIK there is no such bug.

>> I'm trying to sneak up on that bug
>> by setting a virtual size in xorg.conf... It seem doubtful it will
>> work but I'm not sure what the details of the mouse panning bug are.
>
> Because no such bug exists.

>> I'm not sure there is an actual Debian bug about the mouse problem but
>> I see several other OS's are reporting such a bug.  Ubuntu and Redhat
>> specifically.
>
> Please post links to these bugs.

At least one (from redhat) was already mentioned in the previous
thread: Subject: wrestling with xrandr

 https://bugzilla.redhat.com/show_

Re: `Xorg -configure' failure

[Scott Ferguson]

On 07/10/11 02:44, Harry Putnam wrote:
> [NOTE:  This post or very similar was also posted to
> gmane.comp.freedesktop.xorg.]

It's considered bad manners to cross post - why waste more peoples time?

So no point in me making suggestions - my tests were done with settings
that are probably no longer relevant judging from what you've written
here. I don't have time to read all the posts in various subsequent
threads to try and find out what your current settings are.
> 
> Setup:
> 
> Single user machine running Debian (wheezy) 3.0.0-1-686-pae
> Graphics card: Nvidia FX 5700 LE
> 
> At present X is setup without any xorg.conf.  Its pretty much the
> defaults after install of new install medai, other than I've taken
> gdm3 out of service, preferring to `startx', and this I do with no
> problems.
> 
> However, I wanted to use an old setting from previous OS's on this
> same hardware that was set in /etc/X11/xorg.conf.
> 
> I thought I'd generate an xorg.conf and try to edit in my changes.
> 
> The desired addition from previous OS (Gentoo linux). 
> 
>>From Section "Screen"
> 
>   [...]
> 
> Subsection "Display"
> Depth   24
> Modes   "1280x1024" #"1024x768" "800x600" "640x480"
> Virtual 2048 1536 
> ViewPort0 0
> EndSubsection
> 
>   [...]
> 
> Its the virtual size I'm after. 

Then change the virtual size - not the *display* size. That section
refers to the display size for the default monitor (not even the monitor
you currently use).

If those are the setting you want, and they are supported by the
*different display* - then that's all that needs to be in
/etc/X11/xorg.conf - X will deal with everything else. However you will
need to use xrandr to disable your other screens (TV and VGA).


> Its worked on this same hardware in
> the past under Gentoo linux.

Perhaps you "mean" the video card is the same...

A CRT monitor is *not* a LCD monitor. So you *don't* have the same
hardware. Monitors *are* hardware.

Gentoo doesn't use Nouveau - you do. So don't expect the same results
when software and hardware have changed.

> 
> And using xrandr to attain the virtual size has been discussed at some
> length in another thread...

Not on this list. Virtual size was discussed in passing. Panning was
discussed at length.

> so far it hasn't worked.  It appears to be
> because of a bug caused by certain code that prevents the mouse from
> panning out into the virtual size. 

AFAIK there is no such bug.

> I'm trying to sneak up on that bug
> by setting a virtual size in xorg.conf... It seem doubtful it will
> work but I'm not sure what the details of the mouse panning bug are.

Because no such bug exists.

> 
> I'm not sure there is an actual Debian bug about the mouse problem but
> I see several other OS's are reporting such a bug.  Ubuntu and Redhat
> specifically.

Please post links to these bugs.

> 
> Another (related) bug #509699 would seem to indicate it won't work.
> ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=509699)

Did you read that bug report? I don't believe so or you'd have a better
understanding of what "virtual screen size" is - and why the actual bug
(three years ago) had nothing to do with virtual screen size (it was
where an actual screen was placed within a virtual screen).
Look for the comments by Brice Goglin (he's the one who can spell
"crash") :-)
The actual bug  (screen location within the virtual screen on a
multi-head video card) has since been fixed.


> 
> I haven't been able to generate xorg.conf so far because 
> `Xorg -configure' fails without generating a file.

For future reference you can't generate an xorg.conf from within a X
session using "Xorg -configure" (you can generate one from
/var/log/Xorg.0.log though).

> 
> I've included below, the output from running `Xorg -configure' as it was
> written to Xorg.0.log
> 
> Here is just a grep for (EE) error lines, below is the full log.
> 
> grep EE /var/log/Xorg.0.log
> 
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> [177036.473] (EE) Failed to load module "vmwgfx" (module does not exist, 0)
> [177036.473] (EE) vmware: Please ignore the above warnings about not being 
> able to to load module/driver vmwgfx
> [177036.474] (EE) vmware: Unexpected failure while loading the "vmwlegacy" 
> driver. Giving up.
> [177036.474] (EE) Failed to load module "vmware" (a required submodule could 
> not be loaded, 136110067)
> [177036.522] (EE) [drm] No DRICreatePCIBusID symbol
> 


>

Re: `Xorg -configure' failure

[Sven Joachim]

On 2011-10-06 22:48 +0200, Harry Putnam wrote:

> Sven Joachim  writes:
>
>>> Also does the Nouveau driver prevent other drivers such as nv from
>>> loading.
>>
>> Nouveau needs Kernel Modesetting, and both nv and vesa are not
>> compatible with that and will refuse to load if the nouveau.ko kernel
>> module is loaded with modesetting enabled (default).
>
> I know only a little about kernel modesetting;  With Nouveau module
> loading and kernel modesetting enabled... is it still possible to use
> an xorg.conf in that scenario?

Yes, absolutely.  Only the choice for the video driver is limited, to
nouveau and fbdev.

Sven


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87bott3hvr@turtle.gmx.de

Re: `Xorg -configure' failure

[Harry Putnam]

Sven Joachim  writes:

>> Also does the Nouveau driver prevent other drivers such as nv from
>> loading.
>
> Nouveau needs Kernel Modesetting, and both nv and vesa are not
> compatible with that and will refuse to load if the nouveau.ko kernel
> module is loaded with modesetting enabled (default).

I know only a little about kernel modesetting;  With Nouveau module
loading and kernel modesetting enabled... is it still possible to use
an xorg.conf in that scenario?



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87obxtalt4@newsguy.com

Re: `Xorg -configure' failure

[Sven Joachim]

On 2011-10-06 20:00 +0200, Harry Putnam wrote:

> Sven Joachim  writes:
>
>> It might have been easier to just restore the whole file.  And
>> http://wiki.debian.org/XStrikeForce/HowToRandR12 might have some
>> additional useful information for you.
>
> I didn't see discussion of a bug that causes the mouse NOT to pan out
> into a Virtual screen size... although there is such a bug.
>
> I've had good help finding the appropriate xandr commands and can see
> the screen enlarge, but the mouse will not go past the edge.  Far as I
> understood its because of code in some other aspect of things that is
> preventing it.

If you can't find a bug report about this problem, feel free to open one
yourself.

>> I get the same error, but there actually is an xorg.conf.new in the
>> current directory.  "Xorg -configure" does not load the dri module,
>> which seems to be the cause for this error.
>
> This is pretty raunchy of me, but I never thought to look.  There was
> no indication whatever that a file had been written.  But there it is.
>
> Is the dri module essential for starting X?

I don't think so, but it's loaded automatically (when running Xorg
without the -configure switch), although this can be disabled.

> Do you know which package it is in.

It's in xserver-xorg-core.

> Also does the Nouveau driver prevent other drivers such as nv from
> loading.

Nouveau needs Kernel Modesetting, and both nv and vesa are not
compatible with that and will refuse to load if the nouveau.ko kernel
module is loaded with modesetting enabled (default).

> Or is nv even available anymore? 

Not in Debian wheezy: http://bugs.debian.org/612189.

Sven


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87sjn62c6r@turtle.gmx.de

Re: `Xorg -configure' failure

[Harry Putnam]

Sven Joachim  writes:

[...]

> It might have been easier to just restore the whole file.  And
> http://wiki.debian.org/XStrikeForce/HowToRandR12 might have some
> additional useful information for you.

I didn't see discussion of a bug that causes the mouse NOT to pan out
into a Virtual screen size... although there is such a bug.

I've had good help finding the appropriate xandr commands and can see
the screen enlarge, but the mouse will not go past the edge.  Far as I
understood its because of code in some other aspect of things that is
preventing it.

[...]

> I get the same error, but there actually is an xorg.conf.new in the
> current directory.  "Xorg -configure" does not load the dri module,
> which seems to be the cause for this error.

This is pretty raunchy of me, but I never thought to look.  There was
no indication whatever that a file had been written.  But there it is.

Is the dri module essential for starting X?  Do you know which package
it is in.

Also does the Nouveau driver prevent other drivers such as nv from
loading.  Or is nv even available anymore? 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/878voy2e6t@newsguy.com

Re: `Xorg -configure' failure

[Sven Joachim]

On 2011-10-06 17:44 +0200, Harry Putnam wrote:

> Setup:
>
> Single user machine running Debian (wheezy) 3.0.0-1-686-pae
> Graphics card: Nvidia FX 5700 LE
>
> At present X is setup without any xorg.conf.  Its pretty much the
> defaults after install of new install medai, other than I've taken
> gdm3 out of service, preferring to `startx', and this I do with no
> problems.
>
> However, I wanted to use an old setting from previous OS's on this
> same hardware that was set in /etc/X11/xorg.conf.
>
> I thought I'd generate an xorg.conf and try to edit in my changes.

It might have been easier to just restore the whole file.  And
http://wiki.debian.org/XStrikeForce/HowToRandR12 might have some
additional useful information for you.

> I haven't been able to generate xorg.conf so far because 
> `Xorg -configure' fails without generating a file.
>
> I've included below, the output from running `Xorg -configure' as it was
> written to Xorg.0.log
>
> Here is just a grep for (EE) error lines, below is the full log.
>
> grep EE /var/log/Xorg.0.log
>
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> [177036.473] (EE) Failed to load module "vmwgfx" (module does not exist, 0)
> [177036.473] (EE) vmware: Please ignore the above warnings about not being 
> able to to load module/driver vmwgfx
> [177036.474] (EE) vmware: Unexpected failure while loading the "vmwlegacy" 
> driver. Giving up.
> [177036.474] (EE) Failed to load module "vmware" (a required submodule could 
> not be loaded, 136110067)

Those errors should be harmless.

> [177036.522] (EE) [drm] No DRICreatePCIBusID symbol

I get the same error, but there actually is an xorg.conf.new in the
current directory.  "Xorg -configure" does not load the dri module,
which seems to be the cause for this error.

Sven


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87y5wy2hq6@turtle.gmx.de

`Xorg -configure' failure

[Harry Putnam]

[NOTE:  This post or very similar was also posted to
gmane.comp.freedesktop.xorg.]

Setup:

Single user machine running Debian (wheezy) 3.0.0-1-686-pae
Graphics card: Nvidia FX 5700 LE

At present X is setup without any xorg.conf.  Its pretty much the
defaults after install of new install medai, other than I've taken
gdm3 out of service, preferring to `startx', and this I do with no
problems.

However, I wanted to use an old setting from previous OS's on this
same hardware that was set in /etc/X11/xorg.conf.

I thought I'd generate an xorg.conf and try to edit in my changes.

The desired addition from previous OS (Gentoo linux). 

>From Section "Screen"

  [...]

Subsection "Display"
Depth   24
Modes   "1280x1024" #"1024x768" "800x600" "640x480"
Virtual 2048 1536 
ViewPort0 0
EndSubsection

  [...]

Its the virtual size I'm after.  Its worked on this same hardware in
the past under Gentoo linux.

And using xrandr to attain the virtual size has been discussed at some
length in another thread... so far it hasn't worked.  It appears to be
because of a bug caused by certain code that prevents the mouse from
panning out into the virtual size.  I'm trying to sneak up on that bug
by setting a virtual size in xorg.conf... It seem doubtful it will
work but I'm not sure what the details of the mouse panning bug are.

I'm not sure there is an actual Debian bug about the mouse problem but
I see several other OS's are reporting such a bug.  Ubuntu and Redhat
specifically.

Another (related) bug #509699 would seem to indicate it won't work.
( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=509699)

I haven't been able to generate xorg.conf so far because 
`Xorg -configure' fails without generating a file.

I've included below, the output from running `Xorg -configure' as it was
written to Xorg.0.log

Here is just a grep for (EE) error lines, below is the full log.

grep EE /var/log/Xorg.0.log

(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[177036.473] (EE) Failed to load module "vmwgfx" (module does not exist, 0)
[177036.473] (EE) vmware: Please ignore the above warnings about not being able 
to to load module/driver vmwgfx
[177036.474] (EE) vmware: Unexpected failure while loading the "vmwlegacy" 
driver. Giving up.
[177036.474] (EE) Failed to load module "vmware" (a required submodule could 
not be loaded, 136110067)
[177036.522] (EE) [drm] No DRICreatePCIBusID symbol

----   ---=---   -   
----   ---=---   -   

Full content of Xorg.0.log

[177036.435] 
X.Org X Server 1.11.1
Release Date: 2011-09-24
[177036.438] X Protocol Version 11, Revision 0
[177036.439] Build Operating System: Linux 2.6.32-5-amd64 i686 Debian
[177036.440] Current Operating System: Linux reader 3.0.0-1-686-pae #1 SMP Sat 
Aug 27 16:41:03 UTC 2011 i686
[177036.440] Kernel command line: BOOT_IMAGE=/vmlinuz-3.0.0-1-686-pae 
root=UUID=83a94f1d-e6e6-432e-86ad-b24754755fff ro quiet splash
[177036.440] Build Date: 24 September 2011  10:02:42AM
[177036.441] xorg-server 2:1.11.1-1 (Cyril Brulebois ) 
[177036.444] Current version of pixman: 0.22.2
[177036.444]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[177036.445] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[177036.446] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct  6 08:28:20 
2011
[177036.446] (II) Loader magic: 0x822b800
[177036.447] (II) Module ABI versions:
[177036.447]X.Org ANSI C Emulation: 0.4
[177036.447]X.Org Video Driver: 11.0
[177036.447]X.Org XInput driver : 13.0
[177036.447]X.Org Server Extension : 6.0
[177036.448] (--) PCI:*(0:1:0:0) 10de:0343:1462:9590 rev 161, Mem @ 
0xfd00/16777216, 0xc000/268435456, BIOS @ 0x/131072
[177036.449] List of video drivers:
[177036.449]ztv
[177036.449]siliconmotion
[177036.449]sisusb
[177036.456]cirrus
[177036.456]radeon
[177036.456]neomagic
[177036.457]vmwlegacy
[177036.457]nouveau
[177036.457]vmware
[177036.457]savage
[177036.457]ati
[177036.457]geode
[177036.458]voodoo
[177036.458]s3
[177036.458]r128
[177036.458]tdfx
[177036.458]apm
[177036.459]s3virge
[177036.459]i128
[177036.459]ark
[177036.459]mga
[177036.459]mach64
[177036.459]i740
[177036.460]intel
[177036.460]openchrome
[177036.460]chips
[177036.460]trident
[177036.460]tseng
[177036.461]sis
[177036.461]rendition
[177036.461]fbdev
[177036.461]vesa
[177036.461] (II

Re: xserver-xorg-core and fglrx-driver

[Ralf Jung]

Hi,

> When I update this morning (wheezy one but with sid fglrx-driver), the
> xserver-xorg-core was updated.
> 
> my fglrx-driver was removed,
> 
> when I tried to install, it's reported:
> 
> fglrx-driver depends on xorg-video-abi-10 or -8 or -6. which are not
> avaiable.
> 
> then I checked package
> 
> xserver-xorg-core(2:1.11.1-1), which has already been installed.
> 
> xserver-xorg-core-udeb_1.11.1-1_amd64.udeb on AMD64 machines seems not a
> good choice.
> 
> seems the  fglrx-driver (1:11-8-3) dep: xserver-xorg-core (<< 2:1.10.99)
Yeah, unfortunately fglrx was removed from Debian testing recently, breaking 
3d acceleration on a whole lot of systems. Now at least I know why it is 
called "testing" ;-)
I hope AMD will release an update soon, and someone will set the priority to 
high so that it gets to testing quickly.

Kind regards,
Ralf


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201109301434.28208.ralfjun...@gmx.de

Re: xserver-xorg-core and fglrx-driver

[tv.deb...@googlemail.com]

30/09/2011 05:33, lina wrote:
> Hi,
> 
> When I update this morning (wheezy one but with sid fglrx-driver), the
> xserver-xorg-core was updated.
> 
> my fglrx-driver was removed,
> 
> when I tried to install, it's reported:
> 
> fglrx-driver depends on xorg-video-abi-10 or -8 or -6. which are not
> avaiable.
> 
> then I checked package
> 
> xserver-xorg-core(2:1.11.1-1), which has already been installed.
> 
> xserver-xorg-core-udeb_1.11.1-1_amd64.udeb on AMD64 machines seems not a
> good choice.
> 
> seems the  fglrx-driver (1:11-8-3) dep: xserver-xorg-core (<< 2:1.10.99)
> 
> Thanks for any suggestions,
> 
> 
> -- 
> Best Regards,
> 
> lina
> 
> 

Hi, you can either try to use the free driver for a while, AMD will
eventually deliver a compatible fglrx driver at some point ; or you can
go back in time and grab older packages on http://snapshot.debian.org/ .
Look at you apt[itude] logs to see exactly what has been upgraded,
download those packages from snapshot.debian.org, and install them with
"dpkg -i".
You must downgrade ALL xserver-xorg related packages which have been
upgraded, not just the core ones, the ABI change will make your mouse
and keyboard fail if you don't downgrade input packages for instance.

Hope it helps.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4e856b09.5010...@googlemail.com

xserver-xorg-core and fglrx-driver

[lina]

Hi,

When I update this morning (wheezy one but with sid fglrx-driver), the
xserver-xorg-core was updated.

my fglrx-driver was removed,

when I tried to install, it's reported:

fglrx-driver depends on xorg-video-abi-10 or -8 or -6. which are not
avaiable.

then I checked package

xserver-xorg-core(2:1.11.1-1), which has already been installed.

xserver-xorg-core-udeb_1.11.1-1_amd64.udeb on AMD64 machines seems not a
good choice.

seems the  fglrx-driver (1:11-8-3) dep: xserver-xorg-core (<< 2:1.10.99)

Thanks for any suggestions,


-- 
Best Regards,

lina

Re: nvidia binary drivers to get glx and xorg 1.11.0 on sid

[Camaleón]

On Fri, 23 Sep 2011 16:16:38 -0400, Mitchell Laks wrote:

> I have  been using the nvidia binary drivers
> NVIDIA-Linux-x86_64-173.14.25-pkg2.run
> NVIDIA-Linux-x86_64-173.14.30-pkg2.run
> NVIDIA-Linux-x86_64-173.14.31-pkg2.run
> 
> on my desktop running sid.

Those are very old nvidia drivers :-?

> Recently with the upgrade to linux kernel linux-image-3.0.0-1-amd64
> 
> I found that I had difficulty compiling nvidia drivers against 3.x
> kernels 

What error you got?

> and additionally I found that the current stable and beta nvidia
> drivers wont run with the current sid xorg version 1.11

That's something to report to nvidia or xorg guys...

> I have tried to go back to the older stable kernel
> 
> linux-image-2.6.32-5-amd64

Old stable kernel is 2.6.39-x, or at least that's what I have in wheezy.

> but when I try to compile I find that the gcc-4.3 that was used to
> compile the kernel which is neccessary to compile the nvidia drivers
> against the linux-headers linux-headers-2.6.32-5-common
> has been removed from sid since it conflicts with libgcc1.

Try to find whatever you need from the snaphot archive.

> I guess I have to compile my own kernel 2.6.32 kernel from source using
> a more recent gcc.
> 
> but what to do about the xorg version and not running against 1.11?

I read something about this yesterdy, it was in the changelog:

http://packages.debian.org/changelogs/pool/non-free/n/nvidia-graphics-drivers/nvidia-graphics-drivers_280.13.really.275.28-1/changelog

Maybe you only have to wait?

> unfortunately kernel.org is down. where can i get the older kernel
> sources. any other ideas?

I asked a similar question and I was told to download kernel sources from 
here:

https://github.com/torvalds/linux/downloads

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.09.24.09.46...@gmail.com

nvidia binary drivers to get glx and xorg 1.11.0 on sid

[Mitchell Laks]

Hi

I have  been using the nvidia binary drivers
NVIDIA-Linux-x86_64-173.14.25-pkg2.run
NVIDIA-Linux-x86_64-173.14.30-pkg2.run
NVIDIA-Linux-x86_64-173.14.31-pkg2.run

on my desktop running sid. 

Recently with the upgrade to linux kernel 
linux-image-3.0.0-1-amd64

I found that I had difficulty compiling nvidia drivers against 3.x kernels and 
additionally 
I found that the current stable and beta nvidia drivers wont run with 
the current sid xorg version 1.11

I have tried to go back to the older stable kernel 

linux-image-2.6.32-5-amd64

but when I try to compile I find that the gcc-4.3 that was used to compile the 
kernel
which is neccessary to compile the nvidia drivers against the linux-headers
linux-headers-2.6.32-5-common
has been removed from sid since it conflicts with libgcc1.

I guess I have to compile my own kernel 2.6.32 kernel from source using a more 
recent gcc.

but what to do about the xorg version and not running against 1.11?

unfortunately kernel.org is down. where can i get the older kernel sources.
any other ideas?

Mitchell


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110923201638.ga6...@earthlink.net

Re: xorg - MatchIsTouchpad not working properly

[Martin Steigerwald]

Am Mittwoch, 21. September 2011 schrieb David Roguin:
> Hi!

Hi David!

> I have an InputClass section in my xorg.conf that catches whenever a
> touchpad is detected (MatchIsTouchpad "on"), but the driver on that
> section never loads. If I change the MatchIsTouchpad for other Match
> like the MatchIsPointer the driver gets loaded, but of course it
> doesn't work properly.

Did you look at Xorg.log for any error messages regarding that touchpad 
input class section? Do you mind sharing the relevant section with us?

Best would be both. Relevant excerpt from log and the config section.

Ciao,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201109231831.53727.mar...@lichtvoll.de

Re: xorg - MatchIsTouchpad not working properly

[David Roguin]

On Sep 21, 2011, at 11:29 AM, Thierry Chatelet wrote:

> On Wednesday 21 September 2011 15:56:42 David Roguin wrote:
>> Hi!
>> 
>> I have an InputClass section in my xorg.conf that catches whenever a
>> touchpad is detected (MatchIsTouchpad "on"), but the driver on that
>> section never loads. If I change the MatchIsTouchpad for other Match like
>> the MatchIsPointer the driver gets loaded, but of course it doesn't work
>> properly.
>> 
>> I was wondering what is happening that triggers that kind of behavior. I'm
>> thinking maybe udev is not recognizing properly the tochpad… (i can't
>> think of anything else right now :) ) If udev is guilty, then how can I
>> add a rule to to that?
>> 
>> By the way, I have a macbook pro (8,1) with debian wheezy.
>> 
>> Any ideas?
>> Thanks!
>> --
>> David
> 
> What happen if you remove/comment out that inputclass section and let 
> udev/xorg 
> work things out by themselves?

It lets evdev driver handles the Pointer, and I have a touchpad as useful as a 
mouse with only one button.
There's an evdev that catches all the mouse like interfaces, and that's the one 
handling the touchpad events.

D.
> Thierry
> 


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/cdab218e-9030-4c1d-b780-70702d61f...@gmail.com

Re: xorg - MatchIsTouchpad not working properly

[Thierry Chatelet]

On Wednesday 21 September 2011 15:56:42 David Roguin wrote:
> Hi!
> 
> I have an InputClass section in my xorg.conf that catches whenever a
> touchpad is detected (MatchIsTouchpad "on"), but the driver on that
> section never loads. If I change the MatchIsTouchpad for other Match like
> the MatchIsPointer the driver gets loaded, but of course it doesn't work
> properly.
> 
> I was wondering what is happening that triggers that kind of behavior. I'm
> thinking maybe udev is not recognizing properly the tochpad… (i can't
> think of anything else right now :) ) If udev is guilty, then how can I
> add a rule to to that?
> 
> By the way, I have a macbook pro (8,1) with debian wheezy.
> 
> Any ideas?
> Thanks!
> --
> David

What happen if you remove/comment out that inputclass section and let udev/xorg 
work things out by themself?
Thierry


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201109211629.54435.tchate...@free.fr

xorg - MatchIsTouchpad not working properly

[David Roguin]

Hi!

I have an InputClass section in my xorg.conf that catches whenever a touchpad 
is detected (MatchIsTouchpad "on"), but the driver on that section never loads. 
If I change the MatchIsTouchpad for other Match like the MatchIsPointer the 
driver gets loaded, but of course it doesn't work properly.

I was wondering what is happening that triggers that kind of behavior. I'm 
thinking maybe udev is not recognizing properly the tochpad… (i can't think of 
anything else right now :) )
If udev is guilty, then how can I add a rule to to that?

By the way, I have a macbook pro (8,1) with debian wheezy.

Any ideas?
Thanks!
--
David

Re: xserver-xorg-video-intel does sometimes not resume

[Rainer Dorsch]

Julien,

many thanks for the quick and useful reply.

Am Tuesday, 20. September 2011 schrieb Julien Cristau:
> On Tue, Sep 20, 2011 at 12:32:46 +0200, Rainer Dorsch wrote:
> > Hello,
> > 
> > I have occasionally (maybe once a week) the problem, that my system does
> > not resume after a suspend. To be precise: the screen has no signal, but
> > the system itself is up an running (and re-suspends after 10 minutes of
> > inactivity as configured). When I resume the re-suspend, that usually
> > works. I.e. here the complete sequence:
> > 
> > 1. System suspends
> > 2. Resume, but occasionally no video signal available
> > 3. System re-suspends automatically after 10 minutes of inactivity
> > 4. Resume usually works (or sampling rate too small to hit the problem)
> > 
> > I am wondering what I could do to figure out the root cause of the
> > problem. I forgot to try, but I assume, that I could ssh into the
> > machine and do some diagnosis, when the problem occurs. Are there logs
> > which could help? I attach the syslog below...
> 
> Boot with drm.debug=6 and compare dmesg from a successful vs failed
> resume.

I booted with drm.debug=6 and found that there is an intermittent detection 
problem with the monitor ("CRT not detected via hotplug"):

rd@blackbox:~/tmp.nobackup$ diff -u syslog-intel.drm-1303.part syslog-
intel.drm-1340.part 
--- syslog-intel.drm-1303.part  2011-09-21 13:52:26.103280388 +0200
+++ syslog-intel.drm-1340.part  2011-09-21 13:54:31.949381096 +0200
@@ -9,14 +9,6 @@
 [drm:drm_crtc_helper_set_config], 
 [drm:drm_crtc_helper_set_config], [CRTC:3] [FB:17] #connectors=1 (x y) (0 0)
 [drm:drm_crtc_helper_set_config], [CONNECTOR:8:HDMI-A-1] to [CRTC:3]
-[drm:intel_crt_detect], CRT not detected via hotplug
-[drm:output_poll_execute], [CONNECTOR:5:VGA-1] status updated from 2 to 2
-[drm:intel_sdvo_debug_write], SDVOB: W: 0B 
(SDVO_CMD_GET_ATTACHED_DISPLAYS)
-[drm:intel_sdvo_read_response], SDVOB: R: (Success) 01 00
-[drm:intel_sdvo_detect], SDVO response 1 0 [1]
-[drm:intel_sdvo_debug_write], SDVOB: W: 7A 02  
(SDVO_CMD_SET_CONTROL_BUS_SWITCH)
-[drm:intel_sdvo_debug_write], SDVOB: W: 7A 02  
(SDVO_CMD_SET_CONTROL_BUS_SWITCH)
-[drm:output_poll_execute], [CONNECTOR:8:HDMI-A-1] status updated from 1 to 1
 [drm:i915_get_vblank_counter], trying to get vblank count for disabled pipe B
 [drm:intel_opregion_setup], graphic opregion physical addr: 0xcf78e0f4
 [drm:intel_opregion_setup], Public ACPI methods supported
@@ -97,10 +89,8 @@
 [drm:drm_mode_debug_printmodeline], Modeline 13:"640x480" 60 25200 640 656 
752 800 480 490 492 525 0x40 0xa
 [drm:drm_mode_debug_printmodeline], Modeline 14:"720x400" 70 28320 720 738 
846 900 400 412 414 449 0x40 0x6
 [drm:drm_mode_getconnector], [CONNECTOR:8:?]
-[drm:drm_mode_addfb], [FB:24]
 [drm:intel_crtc_cursor_set], 
-[drm:drm_mode_addfb], [FB:21]
-[drm:drm_mode_addfb], [FB:24]
+[drm:drm_mode_addfb], [FB:25]
 [drm:intel_crt_detect], CRT not detected via hotplug
 [drm:output_poll_execute], [CONNECTOR:5:VGA-1] status updated from 2 to 2
 [drm:intel_sdvo_debug_write], SDVOB: W: 0B 
(SDVO_CMD_GET_ATTACHED_DISPLAYS)
rd@blackbox:~/tmp.nobackup$ 

Monitor is an EIZO FlexScan L767

Full log is here

http://bokomoko.de/~rd/syslog-drm.6

around 13:03 the resume was not detecting the monitor, around 13:40 the resume 
was detecting the monitor.

Does anybody have an idea what could go wrong?

Does anybody have an idea what I could do as a workaround? E.g. can I ask the 
driver to retry three times, when the CRT is not detected? Can I enforce that 
the monitor is driven (it is a desktop and never changed)? Other ideas?

Thanks,
Rainer

-- 
Rainer Dorsch
http://bokomoko.de/


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201109211412.01145...@bokomoko.de

Re: xserver-xorg-video-intel does sometimes not resume

[Julien Cristau]

On Tue, Sep 20, 2011 at 12:32:46 +0200, Rainer Dorsch wrote:

> Hello,
> 
> I have occasionally (maybe once a week) the problem, that my system does not 
> resume after a suspend. To be precise: the screen has no signal, but the 
> system itself is up an running (and re-suspends after 10 minutes of 
> inactivity 
> as configured). When I resume the re-suspend, that usually works. I.e. here 
> the 
> complete sequence:
> 
> 1. System suspends
> 2. Resume, but occasionally no video signal available
> 3. System re-suspends automatically after 10 minutes of inactivity
> 4. Resume usually works (or sampling rate too small to hit the problem)
> 
> I am wondering what I could do to figure out the root cause of the problem. I 
> forgot to try, but I assume, that I could ssh into the machine and do some 
> diagnosis, when the problem occurs. Are there logs which could help? I attach 
> the syslog below...
> 
Boot with drm.debug=6 and compare dmesg from a successful vs failed
resume.

Cheers,
Julien


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110920183223.gz3...@radis.liafa.jussieu.fr

xserver-xorg-video-intel does sometimes not resume

[Rainer Dorsch]

Hello,

I have occasionally (maybe once a week) the problem, that my system does not 
resume after a suspend. To be precise: the screen has no signal, but the 
system itself is up an running (and re-suspends after 10 minutes of inactivity 
as configured). When I resume the re-suspend, that usually works. I.e. here the 
complete sequence:

1. System suspends
2. Resume, but occasionally no video signal available
3. System re-suspends automatically after 10 minutes of inactivity
4. Resume usually works (or sampling rate too small to hit the problem)

I am wondering what I could do to figure out the root cause of the problem. I 
forgot to try, but I assume, that I could ssh into the machine and do some 
diagnosis, when the problem occurs. Are there logs which could help? I attach 
the syslog below...

I am using an ASUS P5E-VM HDMI board with an Intel G35 chipset and onboard 
graphics: 

00:02.0 VGA compatible controller: Intel Corporation 82G35 Express Integrated 
Graphics Controller (rev 03) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device 8276
Flags: bus master, fast devsel, latency 0, IRQ 44
Memory at fe80 (32-bit, non-prefetchable) [size=1M]
Memory at d000 (64-bit, prefetchable) [size=256M]
I/O ports at cc00 [size=8]
Expansion ROM at  [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Kernel driver in use: i915



Here I attach some lines from syslog:

11:55 - First resume, no video signal (Step 2)
12:07 - Second resume, video signal there (Step 4)

Sep 20 11:21:06 blackbox dbus[1313]: [system] Successfully activated service 
'org.kde.powerdevil.backlighthelper'
Sep 20 11:28:06 blackbox NetworkManager[1510]:  sleep requested 
(sleeping: no  enabled: yes)
Sep 20 11:28:06 blackbox NetworkManager[1510]:  sleeping or disabling...
Sep 20 11:28:07 blackbox anacron[13799]: Anacron 2.3 started on 2011-09-20
Sep 20 11:28:07 blackbox anacron[13799]: Normal exit (0 jobs run)
Sep 20 11:28:07 blackbox kernel: [ 6834.435396] EXT4-fs (sdc): re-mounted. 
Opts: discard,data=ordered,errors=remount-ro,commit=0
Sep 20 11:28:07 blackbox kernel: [ 6834.666554] PM: Syncing filesystems ... 
done.
Sep 20 11:28:07 blackbox kernel: [ 6834.724441] PM: Preparing system for mem 
sleep
Sep 20 11:55:47 blackbox acpid: client 2070[0:0] has disconnected
Sep 20 11:55:47 blackbox kernel: [ 6834.760206] Freezing user space processes 
... 
Sep 20 11:55:47 blackbox kernel: [ 6837.528247] ata4.00: exception Emask 0x0 
SAct 0x1 SErr 0x0 action 0x6 frozen
Sep 20 11:55:47 blackbox kernel: [ 6837.528255] ata4.00: failed command: READ 
FPDMA QUEUED
Sep 20 11:55:47 blackbox kernel: [ 6837.528263] ata4.00: cmd 
60/40:00:b5:d4:6f/00:00:2b:00:00/40 tag 0 ncq 32768 in
Sep 20 11:55:47 blackbox kernel: [ 6837.528264]  res 
50/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Sep 20 11:55:47 blackbox kernel: [ 6837.528271] ata4.00: status: { DRDY }
Sep 20 11:55:47 blackbox kernel: [ 6837.528278] ata4: hard resetting link
Sep 20 11:55:47 blackbox kernel: [ 6841.492022] ata4: SATA link up 3.0 Gbps 
(SStatus 123 SControl 300)
Sep 20 11:55:47 blackbox kernel: [ 6841.496846] ata4.00: configured for 
UDMA/133
Sep 20 11:55:47 blackbox kernel: [ 6841.512032] ata4: EH complete
Sep 20 11:55:47 blackbox NetworkManager[1510]:  (eth0): carrier now OFF 
(device state 1)
Sep 20 11:55:47 blackbox NetworkManager[1510]:  (eth0): carrier now ON 
(device state 1)
Sep 20 11:55:47 blackbox kernel: [ 6841.544025] (elapsed 6.78 seconds) done.
Sep 20 11:55:47 blackbox kernel: [ 6841.544027] Freezing remaining freezable 
tasks ... (elapsed 0.01 seconds) done.
Sep 20 11:55:47 blackbox kernel: [ 6841.560029] PM: Entering mem sleep
Sep 20 11:55:47 blackbox kernel: [ 6841.560057] Suspending console(s) (use 
no_console_suspend to debug)
Sep 20 11:55:47 blackbox kernel: [ 6841.560407] sd 4:0:0:0: [sdc] 
Synchronizing SCSI cache
Sep 20 11:55:47 blackbox kernel: [ 6841.560438] sd 4:0:0:0: [sdc] Stopping 
disk
Sep 20 11:55:47 blackbox kernel: [ 6841.560463] sd 3:0:0:0: [sdb] Stopping 
disk
Sep 20 11:55:47 blackbox kernel: [ 6841.560565] sd 0:0:0:0: [sda] Stopping 
disk
Sep 20 11:55:47 blackbox kernel: [ 6841.564065] i8042 aux 00:0c: wake-up 
capability disabled by ACPI
Sep 20 11:55:47 blackbox kernel: [ 6841.564070] i8042 kbd 00:0b: wake-up 
capability enabled by ACPI
Sep 20 11:55:47 blackbox kernel: [ 6841.564398] serial 00:09: disabled
Sep 20 11:55:47 blackbox kernel: [ 6841.564402] serial 00:09: wake-up 
capability disabled by ACPI
Sep 20 11:55:47 blackbox kernel: [ 6841.564571] ehci_hcd :00:1d.7: PCI INT 
A disabled
Sep 20 11:55:47 blackbox kernel: [ 6841.564586] uhci_hcd :00:1d.2: PCI INT 
C disabled
Sep 20 11:55:47 blackbox kernel: [ 6841.564589] uhci_hcd :00:1d.1: PCI INT 
B disabled
Sep 20 11:55:47 blackbox kernel: [ 6841.564595] uhci_hcd :00:1d.0: PCI INT 
A disabled
Sep 20 11:55:47 blackbox k

Re: xorg configuration

[Brian]

On Sun 28 Aug 2011 at 20:54:58 +0200, Andreas Berglund wrote:

> I have xorg on autodetect, but it frequently gets things wrong about the  
> resolution the monitor provides. When it gets things right is there any  
> way to extract the configuration of the running instane of xorg into a  
> configuration file?

You may want an /etc/X11/xorg.conf which is something like this:

Section "Monitor"
Identifier   "1905FP"
Modeline "1280x1024_60.00"  109.00  1280 1368 1496 1712  1024 1027 1034 
1063 -hsync +vsync
HorizSync 30-81
VertRefresh   56-76
EndSection

Section "Screen"
Identifier"Default Screen"
Monitor   "1905FP"
DefaultDepth   16
SubSection "Display"
Depth  16
Modes "1280x1024_60.00"
EndSubSection
EndSection

The Modeline information could come from /var/log/Xorg.0.log I suppose,
but I used cvt to generate it.

   cvt 1280 1024


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110829094507.GA28063@desktop

Re: xorg configuration

[Scott Ferguson]

On 29/08/11 04:54, Andreas Berglund wrote:

I have xorg on autodetect, but it frequently gets things wrong about the
resolution the monitor provides. When it gets things right is there any
way to extract the configuration of the running instane of xorg into a
configuration file?

/Andreas




On Squeeze man Xorg says:-

-configure
 When this option is specified, the Xorg server loads all
 video driver modules, probes for available hardware, and
 writes out an initial xorg.conf(5) file based on what was
 detected. This option currently has some problems on some
 platforms, but in most cases it is a good way to bootstrap
 the configuration process. This option is only available
 when the server is run as root (i.e, with real-uid 0).

My suggestion would be:-
# /etc/init.d/gdm stop
# Xorg -configure
# /etc/init.d/gdm start

Substitute kdm for gdm with KDE


Cheers

--
"I've got a bathtub and an imagination, I'm staying indoors this summer.
That way I can listen to music that I like."
— Bill Hicks


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4e5aed05.1010...@gmail.com

Re: xorg configuration

[Ralf Mardorf]

> >  Forwarded Message 
> > From: Andreas Berglund 
> > To: debian-user@lists.debian.org
> > Subject: xorg configuration
> > Date: Sun, 28 Aug 2011 20:54:58 +0200
> > 
> > I have xorg on autodetect, but it frequently gets things wrong about the 
> > resolution the monitor provides. When it gets things right is there any 
> > way to extract the configuration of the running instane of xorg into a 
> > configuration file?
> > 
> > /Andreas

AFAIK no, you need to configure it by trial and error ;). If you are
using a CRT and you have good luck some of the "modeline calculators" in
the web might help you.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1314561578.4267.24.camel@debian

xorg configuration

[Andreas Berglund]

I have xorg on autodetect, but it frequently gets things wrong about the 
resolution the monitor provides. When it gets things right is there any 
way to extract the configuration of the running instane of xorg into a 
configuration file?


/Andreas


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4e5a8f02.3080...@gmail.com

Re: Debian Xorg server release version confusion

[Camaleón]

On Fri, 05 Aug 2011 09:18:55 -0700, Tech Geek wrote:

> I think I found out the reason...Every X release i.e. X11RX.X has a X
> server version associated with it. For example, X11R7.5 has X Server
> version 1.7 and the latest X11R7.6 has X Server version 1.9 [1] which
> clears the confusion.
> 
> [1] ttp://en.wikipedia.org/wiki/X_Window_System#Release_history

Additional info is available here:

http://wiki.debian.org/Xorg

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.08.05.16.21...@gmail.com