Processing commands for [EMAIL PROTECTED]:
> severity 499067 important
Bug#499067: radeonhd: The screen remains black, altough there are no crashes
Severity set to `important' from `grave'
> retitle 499067 radeonhd: black screen with Mobility 3470 and 3GB of RAM (Asus
> Pro72S)
Bug#499067: radeo
severity 499067 important
retitle 499067 radeonhd: black screen with Mobility 3470 and 3GB of RAM (Asus
Pro72S)
thank you
Alex wrote:
> The radeonhd driver is not able to show any image on the screen, while
> the "vesa" and "ati" drivers can. This $
> looks a bit like the one described by the
Your message dated Thu, 18 Sep 2008 07:58:55 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#498690: video-intel: [G43] DVI disabled by starting X
has caused the Debian Bug report #498690,
regarding video-intel: [G43] DVI disabled by starting X
to be marked as done.
This means
Rainer Dorsch wrote:
> When I boot the T61p on a port replicator with an external screen attached, I
> get
>
> (II) NV(0): LVDS native size 738x414
>
> vs
>
> (II) NV(0): LVDS native size 1920x1200
>
> when I boot the laptop standalone.
>
What if you boot on a port replicator witho
On Wed, Sep 17, 2008 at 9:27 AM, Michel Dänzer <[EMAIL PROTECTED]> wrote:
> As Alex pointed out, the flicker is likely due to the two display
> controllers and the accelerator fighting for memory bandwidth. You could
> try playing with Option "DisplayPriority".
Results in the other bug.
zw
On Wed, Sep 17, 2008 at 11:15 AM, Zack Weinberg <[EMAIL PROTECTED]> wrote:
> So I had to work a little harder than I'd have liked to disable one of
> the monitors (disconnect the DVI cable *and* comment out everything
> related to it in xorg.conf, including the Virtual line) but yeah,
> there's no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Mohammed Adnène Trojette escreveu:
> On Wed, Jan 16, 2008, André Luís Lopes wrote:
>>So, it seems it was really something in 1.1~cvs.20080104.1-1 which
>> broke it for me. I'm not sure what was it, but I would guess it could be
>> the fix f
On Wed, Sep 17, 2008 at 7:36 AM, Alex Deucher <[EMAIL PROTECTED]> wrote:
> This is very likely related to multiple monitors. Please try EXA with
> one monitor and see if you still have the same problem.
So I had to work a little harder than I'd have liked to disable one of
the monitors (disconnec
On Wed, Sep 17, 2008 at 19:36:57 +0200, Brice Goglin wrote:
> Stephen Frazier wrote:
> > After some testing I have found that adding "DefaultDepth 24" in the
> > Section "Screen" of file xorg.conf will correct the problem with
> > s3virge_drv.so not displaying the correctly on my machine.
>
> You
Your message dated Wed, 17 Sep 2008 20:03:27 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#461074: More info
has caused the Debian Bug report #461074,
regarding xkb-data: No dead_tilde using "US Alternative international (former
us_intl)" on white MacBook 13"
to be marked as
Stephen Frazier wrote:
> After some testing I have found that adding "DefaultDepth 24" in the
> Section "Screen" of file xorg.conf will correct the problem with
> s3virge_drv.so not displaying the correctly on my machine.
You might want to send this update directly to the upstream bug at
https://b
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.35
> forwarded 486925 http://bugs.freedesktop.org/show_bug.cgi?id=17634
Bug#486925: xorg: only displays top half of KDE screen
Noted your statement that Bug has been forwarded to
http://
Antoon Pardon wrote:
> Package: xorg
> Version: 1:7.3+16
> Severity: normal
>
>
> After loging in with gdm, all seems to work fine until I want to
> go to a console via CTRL-ALT-Fn.
>
> Upon doing so, I find that the text console seems to be expanded
> vertically, making the two top lines and the b
Processing commands for [EMAIL PROTECTED]:
> reassign 498571 xserver-xorg-core
Bug#498571: xserver-xorg-video-intel: selects wrong resolution at startup
Bug reassigned from package `xserver-xorg-video-intel' to `xserver-xorg-core'.
> retitle 498571 Xserver shouldn't force the exact same resolutio
After some testing I have found that adding "DefaultDepth 24" in the Section "Screen" of file
xorg.conf will correct the problem with s3virge_drv.so not displaying the correctly on my machine.
On another machine that uses vmware_drv.so the screen is displayed correctly with the supplied
xorg.co
On Wed, Sep 17, 2008 at 7:36 AM, Alex Deucher <[EMAIL PROTECTED]> wrote:
> On Tue, Sep 16, 2008 at 8:25 PM, Zack Weinberg <[EMAIL PROTECTED]> wrote:
>>
>> With EXA enabled on a Radeon R580 (or possibly an X1900, ATI's numbering
>> conventions confuse me) I see several sorts of display flicker:
>
>
On Wed, 2008-09-17 at 08:53 -0700, Zack Weinberg wrote:
> On Tue, Sep 16, 2008 at 9:56 PM, Brice Goglin <[EMAIL PROTECTED]> wrote:
> > Zack Weinberg wrote:
> >> (II) RADEON(0): Generation 2 PCI interface, using max accessible memory
> >> (II) RADEON(0): Detected total video RAM=524288K, accessible=
On Wed, Sep 17, 2008 at 7:41 AM, Alex Deucher <[EMAIL PROTECTED]> wrote:
> On Tue, Sep 16, 2008 at 8:52 PM, Zack Weinberg <[EMAIL PROTECTED]> wrote:
>> Per the bug I just filed, XAA is painfully slow at drawing a rotated display
>> on the hardware I've got, so I tried EXA - but then the X server cr
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.35
> severity 499304 wishlist
Bug#499304: xserver-xorg: debconf no longer allows setting up monitor properties
Severity set to `wishlist' from `important'
>
End of message, stopping proc
Package: xserver-xorg
Version: 1:7.3+15
Severity: important
Hello
I looked at the debconf templates fo X and I no longer find the options
for setting up monitor parameters. There are several reasons why one
might need these:
- the monitor detection fails. Ideally this should be fixed in the X
On Tue, Sep 16, 2008 at 9:56 PM, Brice Goglin <[EMAIL PROTECTED]> wrote:
> Zack Weinberg wrote:
>> (II) RADEON(0): Generation 2 PCI interface, using max accessible memory
>> (II) RADEON(0): Detected total video RAM=524288K, accessible=262144K
>> (PCI BAR=262144K)
>> (--) RADEON(0): Mapped VideoRAM:
On Tue, Sep 16, 2008 at 9:46 PM, Brice Goglin <[EMAIL PROTECTED]> wrote:
>
> I might be the Xserver core choosing the same resolution at startup (so
> that the login screen appears in the middle of both monitors instead of
> risking of having it outside one of them).
>
> You should be able to work
On Tue, Sep 16, 2008 at 8:52 PM, Zack Weinberg <[EMAIL PROTECTED]> wrote:
> Package: xserver-xorg-video-radeon
> Version: 1:6.9.0+git20080826.a3cc1d7a-1
> Severity: normal
>
> Per the bug I just filed, XAA is painfully slow at drawing a rotated display
> on the hardware I've got, so I tried EXA - b
On Tue, Sep 16, 2008 at 8:25 PM, Zack Weinberg <[EMAIL PROTECTED]> wrote:
> Package: xserver-xorg-video-radeon
> Version: 1:6.9.0+git20080826.a3cc1d7a-1
> Severity: normal
>
> With EXA enabled on a Radeon R580 (or possibly an X1900, ATI's numbering
> conventions confuse me) I see several sorts of d
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.35
> reassign 499278 xserver-xorg-video-ati
Bug#499278: xorg: CTRL-ALT-Fn Doesn't work properly
Bug reassigned from package `xorg' to `xserver-xorg-video-ati'.
>
End of message, stopping
# Automatically generated email from bts, devscripts version 2.10.35
reassign 499278 xserver-xorg-video-ati
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: xorg
Version: 1:7.3+16
Severity: normal
After loging in with gdm, all seems to work fine until I want to
go to a console via CTRL-ALT-Fn.
Upon doing so, I find that the text console seems to be expanded
vertically, making the two top lines and the bottom line invisible,
seeming to be ab
On Wed, Sep 17, 2008 at 01:20:59PM +0200, Julien Cristau wrote:
> On Wed, Sep 17, 2008 at 12:16:34 +0200, Antoon Pardon wrote:
>
> > (II) LoadModule: "mouse"
> > (WW) Warning, couldn't open module mouse
> > (II) UnloadModule: "mouse"
> > (EE) Failed to load module "mouse" (module does not exist, 0
Hi all,
I just found an accelerated video driver for SGI O2. It has been
developed for netbsd and is available at
ftp://ftp.ticklers.org/pub/NetBSD/NetBSD-current/xsrc/xfree/xc/programs/Xserver/hw/xfree86/drivers/crime/
Is there anyone interested in packaging it? I may test the resulting
package.
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.26
> forcemerge 451791 484307
Bug#451791: [965G EXA] Fonts and many other items fail to render legibly
Bug#484307: gdm: don't see fonts
Bug#452268: [965G EXA] all fonts are unreadable
Bug#
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.26
> reassign 484307 xserver-xorg-video-intel
Bug#484307: gdm: don't see fonts
Bug reassigned from package `gdm' to `xserver-xorg-video-intel'.
>
End of message, stopping processing here.
Your message dated Wed, 17 Sep 2008 13:20:59 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#499238: xorg.conf and Xorg.0.log
has caused the Debian Bug report #499238,
regarding xorg: No input possible after upgrade
to be marked as done.
This means that you claim that the probl
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.35
> tags 499238 moreinfo
Bug#499238: xorg: No input possible after upgrade
There were no tags set.
Tags added: moreinfo
> severity 499238 important
Bug#499238: xorg: No input possible a
xorg.conf
# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manu
Your message dated Wed, 17 Sep 2008 10:59:24 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#499121: PCI: (3:0:1) ATI Technologies Inc unknown
chipset (0x5b75) rev 128, Mem @ 0xf801/16
has caused the Debian Bug report #499121,
regarding PCI: (3:0:1) ATI Technologies Inc unk
Antoon Pardon wrote:
> Package: xorg
> Version: 1:7.3+16
> Severity: grave
> Justification: renders package unusable
>
>
> After upgrading xorg and related packages, the computer no
> longer responds to mouse movements and keyboard input.
>
> It doesn't matter whether I try with gdm or via the cons
Hello Antoon & XOrg maint,
I'm experiencing a similar issue since the last week or so, see #499198.
I gave the reason to a kernel problem, since not even a remote access
via SSH is possible, and nothing is written to system logs (so it's
something "bigger" than xorg).
Sandro
--
Sandro Tosi (aka
Package: xorg
Version: 1:7.3+16
Severity: grave
Justification: renders package unusable
After upgrading xorg and related packages, the computer no
longer responds to mouse movements and keyboard input.
It doesn't matter whether I try with gdm or via the console
and startx. I tried to build a new
Am Dienstag, den 16.09.2008, 13:29 +0200 schrieb Julien Cristau:
> > Do you need more information?
> >
> Is there an actual problem?
Sorry for being unclear.:(
I just want to help with the information to get this chipset into the
database so its not unknown anymore.
If it doesn't make any sens
39 matches
Mail list logo
