xorg: Changes to 'debian-unstable'
debian/po/nn.po | 1368 1 files changed, 1368 insertions(+) New commits: commit c208c80ba8ebe5b64bb1386f05f148454302f124 Author: Christian Perrier [EMAIL PROTECTED] Date: Sun Mar 18 09:30:50 2007 +0100 Norwegian translation added diff --git a/debian/po/nn.po b/debian/po/nn.po new file mode 100644 index 000..aadab6f --- /dev/null +++ b/debian/po/nn.po @@ -0,0 +1,1368 @@ +# translation of xserver-xorg_nn.po to Norwegian nynorsk +# +#Translators, if you are not familiar with the PO format, gettext +#documentation is worth reading, especially sections dedicated to +#this format, e.g. by running: +# info -n '(gettext)PO Files' +# info -n '(gettext)Header Entry' +#Some information specific to po-debconf are available at +#/usr/share/doc/po-debconf/README-trans +# or http://www.debian.org/intl/l10n/po-debconf/README-trans# +#Developers do not need to manually edit POT or PO files. +# +# Håvard Korsvoll [EMAIL PROTECTED], 2006, 2007. +msgid +msgstr +Project-Id-Version: xserver-xorg_nn\n +Report-Msgid-Bugs-To: \n +POT-Creation-Date: 2006-10-21 11:30+0200\n +PO-Revision-Date: 2007-03-11 10:07+0100\n +Last-Translator: Håvard Korsvoll [EMAIL PROTECTED]\n +Language-Team: Norwegian nynorsk [EMAIL PROTECTED]\n +MIME-Version: 1.0\n +Content-Type: text/plain; charset=UTF-8\n +Content-Transfer-Encoding: 8bit\n +X-Generator: KBabel 1.11.4\n +Plural-Forms: nplurals=2; plural=(n != 1);\n + +#. Type: multiselect +#. Description +#: ../xserver-xorg.templates:1001 +msgid Video modes to be used by the X server: +msgstr Videomodusar som X-tenaren skal bruke: + +#. Type: multiselect +#. Description +#: ../xserver-xorg.templates:1001 +msgid +Please keep only the resolutions you would like the X server to use. +Removing all of them is the same as removing none, since in both cases the X +server will attempt to use the highest possible resolution. +msgstr +Ta vare på berre dei oppløysingane du vil at X-tenaren skal bruke. Fjernar +du alle er det det same som å fjerne ingen, for i begge tilfeller vil X- +tenaren forsøkje å bruke den høgast mogelege oppløysinga. + +#. Type: boolean +#. Description +#: ../xserver-xorg.templates:2001 +msgid Attempt to autodetect video hardware? +msgstr Forsøkje å finne info om videoutstyret automatisk? + +#. Type: boolean +#. Description +#: ../xserver-xorg.templates:2001 +msgid +You should choose this option if you would like to attempt to autodetect the +recommended X server and driver module for your video card. If the +autodetection fails, you will be asked to specify the desired X server and/ +or driver module. If it succeeds, further configuration questions about +your video hardware will be pre-answered. +msgstr +Vel dette om du vil prøve å finne tilrådd X-tenar og drivarmodul for +videoutstyret automatisk. Viss dette mislukkast, vil du bli spurd om å +oppgje X-tenar og drivarmodul. Viss det går bra, vil dei resterande +spørsmåla om grafikkort og skjerm ha førehandsutfylte svar. + +#. Type: boolean +#. Description +#: ../xserver-xorg.templates:2001 +msgid +If you would rather select the X server and driver module yourself, do not +choose this option. You will not be asked to select the X server if there +is only one available. +msgstr +Viss du heller vil velje X-tenar og drivarmodul sjølv, så må du ikkje velje +dette. Du vil ikkje bli spurd om å velje X-tenar viss det berre er ein +tilgjengeleg. + +#. Type: note +#. Description +#: ../xserver-xorg.templates:3001 +msgid No X server known for your video hardware +msgstr Ingen kjent X-tenar for videoutstyret ditt. + +#. Type: note +#. Description +#: ../xserver-xorg.templates:3001 +msgid +There is either no video hardware installed on this machine (e.g. serial +console only), or the \discover\ program was unable to determine which X +server is appropriate for the video hardware. This could be due to +incomplete information in discover's hardware database, or because your +video hardware is not supported by the available X servers. +msgstr +Det er ikkje noko videoutstyr installert på denne maskina (t.d. berre +konsoll på serieport), eller «discover»-programmet klarte ikkje å finne ut +kva for X-tenar som passar for videoutstyret ditt. Dette kan vere fordi +databasen til «discover»-programmet ikkje er komplett, eller fordi +videoutstyret ditt ikkje er støtta av dei tilgjengelege X-tenarane. + +#. Type: note +#. Description +#: ../xserver-xorg.templates:4001 +msgid Multiple potential default X servers for your hardware +msgstr Det er fleire mogelege standard X-tenarar for denne maskina + +#. Type: note +#. Description +#. Type: note +#. Description +#: ../xserver-xorg.templates:4001 ../xserver-xorg.templates:8001 +msgid +Multiple video cards have been detected, and different X servers are +required to support the various devices. It is thus not possible to
Bug#333960: config script should honour preseeded debconf value for keyboard/options
On Fri, Oct 14, 2005 at 06:44:45PM +0200, Miroslav Kure wrote: the config script sets debconf variable xserver-xorg/config/inputdevice/keyboard/options without actually checking for existing preseeded value and therefore overwrides it headlessly. You can trigger this easily on new installs in Czech where localization-config sets .../keyboard/layout to us,cz_qwerty .../keyboard/options to grp:shift_toggle,grp_led:scroll but after this config we end up with empty .../keyboard/options, thus locking users in foreign keyboard layout. These days we do not have localization-config anymore, but when preseeding these keyboard options in the d-i preseed file, everything works as expected (i.e. xorg.conf is generated with preseeded values), therefore I propose to close the bug. -- Miroslav Kure -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#333960: marked as done (config script should honour preseeded debconf value for keyboard/options)
Your message dated Sun, 18 Mar 2007 16:51:25 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#333960: config script should honour preseeded debconf value for keyboard/options has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: xserver-xorg Hi, the config script sets debconf variable xserver-xorg/config/inputdevice/keyboard/options without actually checking for existing preseeded value and therefore overwrides it headlessly. You can trigger this easily on new installs in Czech where localization-config sets .../keyboard/layout to us,cz_qwerty .../keyboard/options to grp:shift_toggle,grp_led:scroll but after this config we end up with empty .../keyboard/options, thus locking users in foreign keyboard layout. On a similar note, dpkg-reconfigure initializes value of xserver-xorg/config/inputdevice/keyboard/layout with value based on installation keyboard and not with current debconf value, which I consider rather strange. -- Miroslav Kure ---End Message--- ---BeginMessage--- On Sun, Mar 18, 2007 at 16:37:07 +0100, Miroslav Kure wrote: These days we do not have localization-config anymore, but when preseeding these keyboard options in the d-i preseed file, everything works as expected (i.e. xorg.conf is generated with preseeded values), therefore I propose to close the bug. Thanks for following up! Closing the bug per submitter. Cheers, Julien signature.asc Description: Digital signature ---End Message---
Processed: In 2:1.1.1-19 as well
Processing commands for [EMAIL PROTECTED]: found 410696 2:1.1.1-19 Bug#410696: /usr/bin/X: Uncommon X crash with backtrace Bug#410386: Xorg segfaults randomly Bug marked as found in version 2:1.1.1-19. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410696: In 2:1.1.1-19 as well
found 410696 2:1.1.1-19 thanks Backtrace: 0: /usr/bin/X(xf86SigHandler+0x84) [0x80c4354] 1: [0xb7fe2420] 2: /usr/bin/X(Dispatch+0x81) [0x8086b91] 3: /usr/bin/X(main+0x489) [0x806e699] 4: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xc8) [0xb7de9ea8] 5: /usr/bin/X(FontFileCompleteXLFD+0xa9) [0x806d9d1] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#409314: Solved
Hello, I was in contact with upstream via https://bugs.freedesktop.org/show_bug.cgi?id=10121 and we solved my problem. As there are now packages in experimental this bug can be closed. Thanks, Tobias Knieper -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: reassign 409314 to xserver-xorg-video-intel
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 reassign 409314 xserver-xorg-video-intel Bug#409314: i810 modesetting driver claims no modes found on either pipe Bug reassigned from package `xserver-xorg-video-i810-modesetting' to `xserver-xorg-video-intel'. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#409314: marked as done (i810 modesetting driver claims no modes found on either pipe)
Your message dated Sun, 18 Mar 2007 18:56:18 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#409314: Solved has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: xserver-xorg-video-i810-modesetting Version: 1.6.5.git20061014.ac1-1 The current version of the i810 modesetting driver in unstable fails to find any modes on my machine (00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)). I researched the web and found out that people using the latest upstream version don't seem to run into this problem. So packaging a more current snapshot could resolve the issue. Thanks and best regards, Tobias Knieper Just for completneness: [snip] (EE) I810(0): detecting ch7xxx (EE) I810(0): Unable to read from DVOI2C_E Slave 236. (II) I810(0): I2C device CRTDDC_A:ddc2 registered at address 0xA0. (II) I810(0): I2C device CRTDDC_A:ddc2 removed. (EE) I810(0): DDC Analog 0, 5010 (II) I810(0): I2C device LVDSDDC_C:ddc2 registered at address 0xA0. (II) I810(0): I2C device LVDSDDC_C:ddc2 removed. (EE) I810(0): DDC LVDS 1, 5018 (II) I810(0): I2C device DVODDC_D:ddc2 registered at address 0xA0. (II) I810(0): I2C device DVODDC_D:ddc2 removed. (EE) I810(0): DDC DVO 2, 501C (II) I810(0): Found BDB block type 254 (II) I810(0): Found BDB block type 1 (II) I810(0): Found BDB block type 254 (II) I810(0): Found BDB block type 2 (II) I810(0): Found BDB block type 3 (II) I810(0): Found BDB block type 4 (II) I810(0): Found BDB block type 254 (II) I810(0): Found BDB block type 5 (II) I810(0): Found BDB block type 6 (II) I810(0): Found BDB block type 7 (II) I810(0): Found BDB block type 8 (II) I810(0): Found BDB block type 10 (II) I810(0): Found BDB block type 11 (II) I810(0): Found BDB block type 12 (II) I810(0): Found BDB block type 13 (II) I810(0): Found BDB block type 14 (II) I810(0): Found BDB block type 15 (II) I810(0): Found BDB block type 16 (II) I810(0): Found BDB block type 17 (II) I810(0): Found BDB block type 18 (II) I810(0): Found BDB block type 19 (II) I810(0): Found BDB block type 40 (II) I810(0): Found BDB block type 41 (II) I810(0): Found panel of size 768x16384 in BIOS VBT tables (II) I810(0): Panel mode h active 54 blank 0 rate 6451.851852 v active 0 blank 0 rate inf (II) I810(0): Found BDB block type 42 (II) I810(0): Monitoring connected displays enabled (--) I810(0): Pre-allocated VideoRAM: 8060 kByte (==) I810(0): VideoRAM: 65536 kByte (==) I810(0): video overlay key set to 0x101fe (**) I810(0): page flipping disabled (==) I810(0): Using gamma correction (1.0, 1.0, 1.0) Executing (ax == 0x5f01) BIOS call at ../../src/i830_driver.c:500 (II) I810(0): BIOS Build: 2894 (II) I810(0): No active displays on Pipe A. (II) I810(0): Currently active displays on Pipe B: (II) I810(0): LFP (local flat panel) (==) I810(0): Display is using Pipe B (--) I810(0): Maximum frambuffer space: 65368 kByte (--) I810(0): Maximum space available for video modes: 8000 kByte (WW) I810(0): Mode 1024x768 is out of range. (WW) I810(0): Valid modes must be between 320x200-768x16384 (WW) I810(0): Mode 800x600 is out of range. (WW) I810(0): Valid modes must be between 320x200-768x16384 (II) I810(0): Valid mode using panel fitting: 640x480x60 (II) I810(0): Total number of valid FP mode(s) found: 4 (II) I810(0): Printing probed modes for pipe 1 (II) I810(0): Not using default mode 640x480x60 (bad mode clock/interlace/doublescan) (II) I810(0): Not using default mode 720x400x60 (bad mode clock/interlace/doublescan) (II) I810(0): Not using default mode 640x400x60 (bad mode clock/interlace/doublescan) (II) I810(0): Not using default mode 640x350x60 (bad mode clock/interlace/doublescan) (II) I810(0): I2C device CRTDDC_A:ddc2 registered at address 0xA0. (II) I810(0): I2C device CRTDDC_A:ddc2 removed. (II) I810(0): Printing probed modes for pipe 0 Fatal server error: No modes found on either pipe ---End Message--- ---BeginMessage--- Version: 2:1.9.92-1 On Sun, Mar 18, 2007 at 18:42:07 +0100, Tobias Knieper wrote: Hello, I was in contact with upstream via https://bugs.freedesktop.org/show_bug.cgi?id=10121 and we solved my problem. As there are now packages in experimental this bug can be closed. Thanks, marking as fixed in 2.0rc2. Cheers, Julien signature.asc Description: Digital signature ---End Message---
Processed: Re: Not abel to set (working) modes higher than 1280x1024
Processing commands for [EMAIL PROTECTED]: reassign 408815 xserver-xorg-video-intel Bug#408815: Not abel to set (working) modes higher than 1280x1024 Bug reassigned from package `xserver-xorg-video-i810-modesetting' to `xserver-xorg-video-intel'. tags 408815 moreinfo Bug#408815: Not abel to set (working) modes higher than 1280x1024 There were no tags set. Tags added: moreinfo thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#408815: Not abel to set (working) modes higher than 1280x1024
reassign 408815 xserver-xorg-video-intel tags 408815 moreinfo thanks On Sun, Jan 28, 2007 at 15:08:10 +0100, Bernhard Mähr wrote: My situation: I have a Mac Mini with a Xoro-LCD (LCD-TV HTL 3742 w) supporting a native resolution of 1920x1080. I would like to use this resolution with the debian installed on the Mac Mini. I'm able to use this resolution with MacOS at a frequency of 12 Hz or 60Hz interlaced. I'm also able to use this resolution with 60Hz interlaced on Windows. But with the mode-setting-driver I'm not able to get a working setup with more than 1280x1024. Hi, could you test the xserver-xorg-video-intel and xserver-xorg-core packages from experimental and report the result? Thanks, Julien signature.asc Description: Digital signature
Processed: Re: xserver-xorg-video-i810-modesetting: After X is started, switching back to console: console is corrupted
Processing commands for [EMAIL PROTECTED]: reassign 401218 xserver-xorg-video-intel Bug#401218: xserver-xorg-video-i810-modesetting: After X is started, switching back to console: console is corrupted Bug reassigned from package `xserver-xorg-video-i810-modesetting' to `xserver-xorg-video-intel'. tags 401218 moreinfo Bug#401218: xserver-xorg-video-i810-modesetting: After X is started, switching back to console: console is corrupted There were no tags set. Tags added: moreinfo thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#401218: xserver-xorg-video-i810-modesetting: After X is started, switching back to console: console is corrupted
reassign 401218 xserver-xorg-video-intel tags 401218 moreinfo thanks On Fri, Dec 1, 2006 at 21:16:36 +0100, Tobias Frost wrote: After X is started. switching back to a text console (Ctrl+F1 as example), the text console just flickers and is completly unusable. (However, the console is responsible, so a blind login works.. Therefore this bug is not so critical, but annoying..) Hi, could you install the xserver-xorg-core and xserver-xorg-video-intel from experimental and tell us if your problem is fixed there? Thanks, Julien signature.asc Description: Digital signature
Processed: Re: xserver-xorg-video-i810-modesetting: dpkg-reconfigure doesn't detect correct video modes
Processing commands for [EMAIL PROTECTED]: reassign 414034 xserver-xorg-video-intel Bug#414034: xserver-xorg-video-i810-modesetting: dpkg-reconfigure doesn't detect correct video modes Bug reassigned from package `xserver-xorg-video-i810-modesetting' to `xserver-xorg-video-intel'. tags 414034 moreinfo Bug#414034: xserver-xorg-video-i810-modesetting: dpkg-reconfigure doesn't detect correct video modes There were no tags set. Tags added: moreinfo thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#414034: xserver-xorg-video-i810-modesetting: dpkg-reconfigure doesn't detect correct video modes
reassign 414034 xserver-xorg-video-intel tags 414034 moreinfo thanks On Thu, Mar 8, 2007 at 20:24:30 +0100, Hermann Kraus wrote: I just tried this package as I had a problem with the regular i810 driver. I wanted to create a new config by running dpgk-reconfigure -plow xserver-xorg and selected monitor autodetection. The detected modes were 640x480 800x600 1024x768 but my display is 1280x800. The normal driver detects the correct resolution. Hi Hermann, could you install the xserver-xorg-core and xserver-xorg-video-intel packages from experimental and report the result to this bug? Please send your full X config and log files. Thanks, Julien signature.asc Description: Digital signature
Bug#415354: RM: xserver-xorg-video-intel-modesetting -- RoM; superseded by xserver-xorg-video-intel
Package: ftp.debian.org Hi, the xserver-xorg-video-intel-modesetting package in experimental has been renamed/superseded by xserver-xorg-video-intel. Please remove it from the archive. Thanks, Julien signature.asc Description: Digital signature
Bug#199032: it`s bailey
hello, I am pretty russian girl, bored tonight. would you like to chat with me and see my pics? if so then email me at [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410696: In 2:1.1.1-19 as well
Johan Walles wrote: found 410696 2:1.1.1-19 thanks Backtrace: 0: /usr/bin/X(xf86SigHandler+0x84) [0x80c4354] 1: [0xb7fe2420] 2: /usr/bin/X(Dispatch+0x81) [0x8086b91] 3: /usr/bin/X(main+0x489) [0x806e699] 4: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xc8) [0xb7de9ea8] 5: /usr/bin/X(FontFileCompleteXLFD+0xa9) [0x806d9d1] Since you reproduced this bug a couple times with several versions of the X server, do you have any idea how we could try to reproduce it for sure? Also, I don't see in the BTS that you ever tried a more recent X server. 1.1.1 is actually pretty outdated nowadays. The latest upstream (1.3-rc2) is currently in experimental, you could eventually try it (xserver-xorg-core 2:1.2.99.902-1). If you don't like testing a release candidate X server, the previous stable one (1.2.0, the official server of Xorg 7.2) has been in experimental for a while earlier. You could grab it from: http://snapshot.debian.net/archive/2007/03/03/debian/pool/main/x/xorg-server/xserver-xorg-core_1.2.0-6_i386.deb Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#415227: Compiz interferes with Screensaver -- unable to unlock a session
George Aprozeanu wrote: When enabling compiz via the compiz --replace command, as soon as the screensaver starts in its default configuration, you cannot see the actual image of the screensaver but a blank screen. What kind of image is that? fullscreen? regular non-moving 2D image? or some complex 3d stuff that could be hard to combine with the compiz layer? Does the problem occur with xscreensaver instead of gnome-screensaver? Does the problem seem fullscreen-related? (any other fullscreen program having problem?) I'm using Debian etch with pretty much default stuff and updated. Screensaver is gnome-screensaver 2.14.3-3. Compiz is 0.2.2-1. My video card is Intel 950G and i use the i810 driver. Other things work fine with compiz. There are multiple more recent upstream releases that could possibly fix this problem. If you have time to debug, you could try some of the following packages from experimental: * compiz, compiz-core, ... 0.3.6-1 * xserver-xorg-core 2:1.2.99.902-1 (eventually with xserver-xorg-video-intel and xserver-xorg-video-i810 2:1.9.92-1) * maybe mesa 6.5.2-3 too Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#413721: Acknowledgement (xserver-xorg-video-ati: The current version of the ati driver in experimental crashes frequently.)
Anant wrote: Backtrace: 0: /usr/bin/X(xf86SigHandler+0x84) [0x80c1d74] 1: [0xb7eed420] 2: /usr/lib/xorg/modules/drivers//radeon_drv.so(RADEONDisplayPowerManagementSet+0x132) [0xb7bb86a2] 3: /usr/bin/X(DPMSSet+0xc5) [0x80c1215] 4: /usr/lib/xorg/modules/extensions//libextmod.so [0xb7ee7ead] 5: /usr/bin/X [0x81491ae] 6: /usr/bin/X(Dispatch+0x1ab) [0x80880cb] 7: /usr/bin/X(main+0x489) [0x806fef9] 8: /lib/i686/cmov/libc.so.6(__libc_start_main+0xd8) [0xb7ceaea8] 9: /usr/bin/X(FontFileCompleteXLFD+0xa1) [0x806f231 It might be related to https://bugs.freedesktop.org/show_bug.cgi?id=9892 which has been reported after 6.6.3 was released and does not occur with 6.6.3 (the 6.6.3-5 ati driver currently in experimental is actually not 6.6.3, the numbering should be 6.6.99foo). Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#415147: xserver-xorg: Keyboard input stops being accepted
John Goerzen wrote: You might notice that I'm running the fglrx driver on here. I don't think that should be related to the problem I'm having, but I did notice on a collague's machine that the radeon driver now can be coerced to work with our displays, so I will try it and, after a few days, let you know if there seems to be any change. [...] VGA-compatible devices on PCI bus: 01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AP [Radeon 9600] Yes, you should be able to use the free ati driver on this board. You could also try some packages from experimental. xserver-xorg-core 2:1.2.99.902-1 would be a good candidate (but fglrx won't probably work at all then). Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
