Package: xserver-xorg-video-ati
Version: 1:6.6.3-2
Severity: normal
Writing text with glutBitmap function gives poor results. Looks like some pixel
rows are not drawn.
Problem goes away if i make the window large (near maximised or maximised).
Problem does not occur when rendering is software o
Package: xserver-xorg-video-ati
Version: 1:6.6.3-2
Severity: important
Blender crashes before even getting started (segmentation fault).
Crash occurs in R when using the rgl library (R's interface to opengl) -
if i zoom in the whole system freezes and doesn't recover.
Drawing wire objects with
eks.
>
> Thanks,
> Brice
Not at all.
Many thanks,
Alex
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
- I don't know where to start
searching for a solution...
Greets,
Alex
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
This is correct, tested on unstable and is fixed.
On Thursday 14 August 2008 21:48:08 Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the xkb-data package:
>
> #485702: xorg: setxkbmap fails to properly set romanian std mapp
differences are only in memory addresses).
Alex
X.Org X Server 1.4.2
Release Date: 11 June 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux Debian (xorg-server 2:1.4.2-6)
Current Operating System: Linux 193-170-133-226 2.6.26-1-amd64 #1 SMP Wed Sep 10 15:31:12 UTC 2008 x86_64
Build Date
Package: xorg
Severity: important
In a huge variety of applications e.g. iceweasel, openoffice, openbox (menu
entries, window titles), text is either missing, out of place on the page, or
the font is incorrect color. This usually affects a whole line, but sometimes
just the first letter. After
Followup-For: Bug #489495
Package: xserver-xorg
Version: 1:7.3+18
*** Please type your report below this line ***
I confirm this for Unstable (I don't know how useful my input is, as the
problem is already described at least
by http://www.shallowsky.com/linux/x-screen-blanking.html and
http://g
On Fri, Apr 16, 2010 at 01:11:33AM +0200, Cyril Brulebois wrote:
> Hi,
>
> Alex Bennee (15/04/2010):
> > Since a recent update to sid (in the last 2 weeks) resume from
> > suspend has become unreliable.
>
>
> please upgrade your kernel from your current 2.6.32
On Sun, Apr 18, 2010 at 01:48:40PM +0200, Julien Cristau wrote:
> On Sun, Apr 18, 2010 at 10:55:16 +0200, Alex wrote:
> > On Fri, Apr 16, 2010 at 01:11:33AM +0200, Cyril Brulebois wrote:
> > > Alex Bennee (15/04/2010):
> >
> > Seems more stable but have had it bla
On Sun, Apr 18, 2010 at 05:17:10PM +0200, Julien Cristau wrote:
> Please run
> /usr/share/bug/xserver-xorg/script 3>/tmp/xorg-bug-577996.txt
> and send the resulting file to this bug.
>
> Cheers,
> Julien
Attached.
--
Alex, homepage: http://www.bennee.com/~alex/
It
Package: xserver-xorg-input-evdev
Version: 1:2.3.2-6
Severity: important
Tags: upstream
after a mouse is unplugged/replugged, X no longer sends any events except to
the current window; including the WM. xev running in background does not
receive motionNotify. affects both keyboard and mouse.
via patch Revert "dix: use the event mask of the grab for TryClientEvents."
http://cgit.freedesktop.org/xorg/xserver/patch/?id=1884db430a5680e37e94726dff46686e2218d525
http://lists.freedesktop.org/archives/xorg-announce/2010-July/001354.html
grabbutton would cause the input mask to be incorrectly
scratch that; still broken on 1.10.1 in testing for laptop, just took
a while to trigger. following up in upstream bug
https://bugs.freedesktop.org/show_bug.cgi?id=26213
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@l
Package: Xdmx
Version: 1.19.3-2
Severity: important
Dear Maintainer,
Xdmx segfaults when starting it with Xdmx -display 192.168.102.57:0
-norender :1
I am not sure if the parameters are correct as I was setting it up, but
it should not segfault anyway.
The trace is:
(II) dmx[o0/192.168.102.57:0]
Package: libx11-6
Version: 2:1.8.10-2
Severity: important
File: libx11
Tags: l10n
X-Debbugs-Cc: a...@alex.com
Dear Maintainer,
There seems to be parsing issues occurring in Trixie. I installed using the
alpha installer (debian-trixie-DI-alpha1-amd64-netinst.iso) and subsequently
added my custom k
shes regularly. I've spent one hour to figure out the
issue and to find this bug.
I've apply the work around to save my life but a regular user couldn't
do that.
Best regards,
Alex.
Le 26/04/2018 à 16:56, Uwe Kleine-König a écrit :
The freedesktop guys are responsible for the kernel, too. So it was
addressed to the right people.
Right, but what's on Debian? Does the package xorg is relevant?
Best regards,
Alex.
ernal
monitor port). We can double check by posting your dmesg output.
MUX-less systems aren't supported yet as we need a fair amount of drm
and X infrastructure to handle buffer sharing between GPUs and
decoupled display and rendering.
Alex
> - Craig
> --
> Craig Small VK2XLZ http:
On Sun, Jan 8, 2012 at 2:15 AM, Craig Small wrote:
> On Wed, Jan 04, 2012 at 09:48:50AM -0500, Alex Deucher wrote:
>> Is there any chance you are using a hybrid laptop with both Intel and
>> AMD GPUs in it? Based on your log this looks like it a MUX-less one
> It is definite
b covers and more. The reason radeonfb is
still around is that it covers a few corner cases (suspend and resume
on ppc mac cards) which hasn't been ported over to radeon yet. On
x86, there is no reason to use radeonfb.
Alex
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
152x864
The xserver (not the driver) is picking 1152x864 since it's the
largest common mode supported by both monitors. You'll have to use
xrandr to choose a different mode (or specify different default modes
in your xorg.conf). Alternatively, you can start up X with one
monitor attached
On Mon, Mar 5, 2012 at 12:42 PM, Christopher Dow
wrote:
> Unfortunately, my problem is that I can't change the display modes to the
> native resolution. Even with one display disabled, I still can't set the
> native resolution. I get the same "input timing not supported" message every
> time
On Sun, Aug 21, 2011 at 1:13 PM, Willian Veiga wrote:
> Alex Deucher, I have an AMD Radeon HD 6470M but I can't select which
> card I want to use in the BIOS setup.
>
> How do I know if my GPU display is MUXes or MUX-less? I've tried to
> select the discrete card using
On Mon, Aug 22, 2011 at 1:38 PM, Willian Gustavo Veiga
wrote:
> Of course I can Alex. It's attached.
> Thank you very much.
The radeon has no connectors specified in the vbios so it's muxless.
Not much we can do with it until X gets re-architected to decouple
display and
I was planning to update this machine to Wheezy, I can retest this. I still
owe the BTS another bug about the driver regression anyway, so I could
hopefully test that also.
- Original Message -
From: Daniel Kahn Gillmor
To: 605...@bugs.debian.org; 605051-submit...@bugs.debian.org
Cc:
I can confirm the same activity as David. No longer segfaults.
The driver itself still seems regressed. It did work in Lenny, I cannot get a
usable screen through auto-detection with Squeeze or Wheezy.
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscr
. However, it sounds
like you are using an environment that is mostly software rendering.
As such in order for the CPU to access tiled buffers, the GPU has to
copy them to a linear buffer before CPU can access it properly.
Alex
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.deb
On Sun, Nov 13, 2011 at 1:34 PM, Iustin Pop wrote:
> On Thu, Nov 10, 2011 at 06:15:43PM +0100, Michel Dänzer wrote:
>> On Don, 2011-11-10 at 18:01 +0100, Michal Suchanek wrote:
>> > On 10 November 2011 17:46, Alex Deucher wrote:
>> > > On Wed, Nov 9, 2011
appens when doing nothing with the system but when audio is
> playing. Running Gnome3 in the fallback mode works OK and no freeze happens.
>
I would suggest using KMS rather than UMS. When you switch to KMS,
I'd also suggest using the r600 gallium 3D driver and removing the
Virtual line
On Mon, Nov 14, 2011 at 9:34 AM, Joost Kraaijeveld
wrote:
> On Mon, 2011-11-14 at 09:15 -0500, Alex Deucher wrote:
>> I would suggest using KMS rather than UMS. When you switch to KMS,
>> I'd also suggest using the r600 gallium 3D driver and removing the
>> Virtual line
ffer and the
compositor is responsible for updating the display buffer with the new
Xv data.
Alex
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/cadnq5_ovcej17kinr5uwwdedkv3rf-5mklxcmkoikso0_bl...@mail.gmail.com
0,B1,B2,B3,B4,B5,B6,B7,B8,B9,BA,BB,BC,BD,BE,BF,C0,C1,C2,C3,C4,C5,C6,C7,C8,C9,CA,CB,CC,CD,CE,CF,D0,D1,D2,D3,D4,D5,D6,D7,D8,D9,DA,DB,DC,DD,DE,DF,E0,E1,E2,E3,E4,E5,E6,E7,E8,E9,EA,EB,EC,ED,EE,EF,F0,F1,F2,F3,F4,F5,F6,F7,F8,F9,FA,FB,FC,FD,FE,FF,ramlsfw
E: NAME="ACPI Virtual Keyboard Device"
E: P
lems disappears completely.
To clarify, do you mean that after a dpms cycle both monitors work
correctly? Does a newer kernel help? 3.2 is pretty old. There were
a number of display related fixes that went into 3.7 for example.
Alex
--
To UNSUBSCRIBE, email to debian-x-requ..
On Wed, Apr 3, 2013 at 2:22 PM, Pablo Oliveira wrote:
> On Wed, Apr 3, 2013 at 3:34 PM, Alex Deucher wrote:
>>
>> On Tue, Apr 2, 2013 at 10:04 AM, Pablo Oliveira wrote:
>> > Package: xserver-xorg-video-ati
>> > Version: 1:6.14.4-8
>> > Followup-For: B
Are we really sure it's a service to debian users or debian as a
distribution to simply remove compiz from wheezy based on a number of
minor(?) issues that are so obscure that they needed a fake RC bug?
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscri
gt;
Also note that rendering can only be synchronized to one head at a
time to avoid tearing. If you have windows that span multiple heads,
you may get tearing on the non-synced heads.
Alex
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CADnq5_PQq+-_nu+JyBMwAGsnpwL028pub1ZJE8ûHtyPv...@mail.gmail.com
When you switch VTs,
just the display base address is changed. The gamma is not changed.
I suspect this may affect other drivers as well so probably needs to
be fixed in common code.
Alex
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsub
writing from a different wheezy
> install).
Make sure you install the firmware package and that the firmware is
available in the initrd if you are using one.
Alex
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm
ack into Linux. I'm booting with grub-efi.
If apple uses the built in GPU backlight controller, it may work with
the new backlight control patches in my drm-3.7 branch:
http://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-3.7-wip
Alex
--
To UNSUBSCRIBE, email to debian-x-req
o have this problem. Can anyone suggest ways in
> which I can troubleshoot/resolve it?
Can you try a newer kernel? 3.6 or 3.7? That may help with the
modesettings. As for the acceleration, corruption, you might try a
newer version of mesa.
Alex
--
To UNSUBSCRIBE, email
wer kernel or if you are using EFI to boot, try
using the legacy bios option. Unfortunately, macs do just about
everything differently you may need some sort of mac specific quirk to
make it work properly, especially with EFI boot.
Alex
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
w
ay want to use the driver without X, e.g., wayland, or
headless compute. Additionally, if you have the driver loaded you can
use advanced power management features and dpms which are not
available with vesa or vga mode.
Alex
>
> Cheers,
> Julien
>
> ___
With KMS, the kernel driver inits and manages the hw so it
takes relatively longer to load and the ddx may try and access the
kernel driver before it's finished loading leading to fail.
Alex
>
> --
> Robert Millan
>
> ___
> xorg
til the X driver is
> started.
>
> Furthermore, there's some additional initialization needed for the X
> driver itself to work, which for some reason only happens after
> starting & stopping X repeatedly.
>
>
> Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Is t
n't loading - only black screen. With working fglrx GNOME also
> loading
> in fallback mode. In Windows graphic card work correct.
>
Can you try a newer kernel? 3.2.0 is pretty old.
Alex
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/CADnq5_O0vRSrid4gB=�=cWfcD5JpD=w58vpf9pa0xdqjw...@mail.gmail.com
uot; "sna" didn't help me.
Also works fine via OpenGL.
Regards,
Alex
Cool, it works with the version from experimental -
2:2.99.911+git20140607-1~exp1 !
Also it seems that the source package has missing buid-deps, I had to
install these 3 package in order to build it on jessy:
libxcb-randr0-dev
libxcb-shape0-dev
libxcb-xfixes0-dev
Thanks,
Alex
On Tue, Jun 10
Package: xdm
Version: 4.2.1-4
Severity: grave
Justification: renders package unusable
the init.d xdm script fails to start X. "xdm" from the command line
also fails to start X. i can start it just fine with "startx", though.
hope this helps.
alex.
-- System Informa
into this problem, the machine has been rebooted and successfully
restarted xdm.
to me it looks like the xdm package is rendered unusable by xdm failing
to start X, and that matched the "grave" severity option in the list
provided by reportbug. what bug severity would you suggest?
alex.
t
- Forwarded message from -
Date: Sun, 2 Mar 2003 20:21:30 +0100
To: debian-x@lists.debian.org
Subject: Report of Server Crash
Dear Fellows,
unfortunately I cannot start the X-Server anymore after upgrading. I
use Debian GNU/Linux 3.0. The upgrade repository was the apt-source:
http://pe
ng it anymore).
I used debconf to configure the server, and then modified the frequencies
of my monitor by hand, but it shouldn't have mattered, should it?
I'd be happy to assist in further diagnostics, if you told me how to :-)
Alex
--
Alexander Roitman http://ebner.neuroscience
Package: xserver-xfree86
Version: 4.2.1-6
Severity: important
Tags: sid
After upgrading to 4.2.1-6, the savage driver stopped working for
me. The X-server still starts up normally, but many parts of the
display (including fonts and filled-rectangles) are not rendered at
all.
from output of lsp
Package: xdm
Version: 4.2.1-4
Severity: grave
Justification: renders package unusable
the init.d xdm script fails to start X. "xdm" from the command line
also fails to start X. i can start it just fine with "startx", though.
hope this helps.
alex.
-- System Informa
into this problem, the machine has been rebooted and successfully
restarted xdm.
to me it looks like the xdm package is rendered unusable by xdm failing
to start X, and that matched the "grave" severity option in the list
provided by reportbug. what bug severity would you suggest?
alex.
t
- Forwarded message from -
Date: Sun, 2 Mar 2003 20:21:30 +0100
To: [EMAIL PROTECTED]
Subject: Report of Server Crash
Dear Fellows,
unfortunately I cannot start the X-Server anymore after upgrading. I
use Debian GNU/Linux 3.0. The upgrade repository was the apt-source:
http://people.deb
ng it anymore).
I used debconf to configure the server, and then modified the frequencies
of my monitor by hand, but it shouldn't have mattered, should it?
I'd be happy to assist in further diagnostics, if you told me how to :-)
Alex
--
Alexander Roitman http://ebner.neuroscience
Package: xserver-xfree86
Version: 4.2.1-6
Severity: important
Tags: sid
After upgrading to 4.2.1-6, the savage driver stopped working for
me. The X-server still starts up normally, but many parts of the
display (including fonts and filled-rectangles) are not rendered at
all.
from output of lsp
e exec sessreg -a -l
"$DISPLAY" -u /var/run/utmp. alternatively, you can set no-use-sessreg
in /etc/X11/xdm/xdm.options
hope this helps.
--alex--
--
| I believe the moment is at hand when, by a paranoiac and active |
| advance of the mind, it will be possible (simultaneously with |
Package: libglu1-xorg-dev
Version: 6.8.2.dfsg.1-2
Severity: normal
since this package was presumably compiled with gcc v4 (libglu1-xorg
provides libglu1c2) it should depend instead on libstdc++6-4.0-dev.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy:
Using a vanilla Testing basic install and xserver-xfree86 version 4.3.0-7
with a Radeon 8500 (ATI brand) card and a Dell 20" LCD flat panel monitor.
Both card connectors (DVI and VGA) are plugged into the monitor for this.
I'm just trying to get as far as having the server up, and an xterm visible.
tting engine...
I'd be grateful for any help. I hesitated to post the complete XFree log,
kernel config, and dmesg for both cases, but please let me know if I should.
Thanks for any leads,
Alex
--
Alexander Roitman http://ebner.neuroscience.umn.edu/people/alex.html
Dept. of Neuroscienc
en[i] = 0;
}
}
for (i = 0; i < nchildren; i++) {
if (children[i])
XKillClient (dpy, children[i]);
}
XFree ((char *)children);
XSync (dpy, 0);
XSetErrorHandler (NULL); /* pretty stupid way to do things... */
return 0;
}
/
en[i] = 0;
}
}
for (i = 0; i < nchildren; i++) {
if (children[i])
XKillClient (dpy, children[i]);
}
XFree ((char *)children);
XSync (dpy, 0);
XSetErrorHandler (NULL); /* pretty stupid way to do things... */
return 0;
}
/**/
--
Alex Owen
[EMAIL PROTECTED]
nd doesn't provide an edid. you'll
need to force both monitors monitors on using:
Option "MonitorLayout" "LCD, CRT"
and you'll have to specify the h and v sync ranges for the second
monitor using the crt2hsync and crt2vrefresh options. See the rad
On 8/12/07, Alberto Mardegan <[EMAIL PROTECTED]> wrote:
> Alex Deucher wrote:
> > you monitor is not being detected and doesn't provide an edid. you'll
> > need to force both monitors monitors on using:
> > Option "MonitorLayout"
On 8/13/07, Michel Dänzer <[EMAIL PROTECTED]> wrote:
> On Sun, 2007-08-12 at 10:21 -0400, Alex Deucher wrote:
> >
> > Option "MonitorLayout" "LCD, CRT"
>
> That should be "LVDS,CRT", shouldn't it?
>
Right :)
On 8/13/07, Alberto Mardegan <[EMAIL PROTECTED]> wrote:
> Alex Deucher wrote:
> > You've switched driver versions since your last email. those options
> > only apply to ati master and 6.6.193 (mergedfb). the logs you've
> > attached this time are from the xra
me
monitor. See bug 11781:
https://bugs.freedesktop.org/show_bug.cgi?id=11781
As a work around for now you can specify a monitorlayout to disable
the secondary head:
Option "MonitorLayout" "CRT, NONE"
Alex
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
r was not able to
get any edid info from the VGA port so it does not know what modes to
add. As such you will have to manually add the modes you want to use
to that output. You will need the latest release of xrandr (1.2.2) to
do this.
xrandr --addmode VGA-0 1024x768
xrandr --output VGA-0 --mo
you are trying to enable more than two
outputs. turn off tv if you want to enable VGA.
xrandr --output S-video --off
Alex
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On 8/27/07, Marcus Better <[EMAIL PROTECTED]> wrote:
> Alex Deucher wrote:
> > You only have two crtcs and you are trying to enable more than two
> > outputs. turn off tv if you want to enable VGA.
>
> Yes, that helps, but why is it enabling S-video in the first pla
ally add a mode:
xrandr --addmode VGA-0 1280x1024
regarding the edid, two factors could be at work. Either we are using
the wrong ddc line or we need to adjust the i2c timing a bit.
Alex
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On 8/29/07, Marcus Better <[EMAIL PROTECTED]> wrote:
> Alex Deucher wrote:
> > xrandr --addmode VGA-0 1280x1024
>
> Tried that:
>
> ~$ xrandr --addmode VGA-0 1280x1024
> xrandr: cannot find mode "1280x1024"
>
try adding 1280x1024 to the modes line in
On 8/29/07, Marcus Better <[EMAIL PROTECTED]> wrote:
> Alex Deucher wrote:
> >> The X server log (see earlier messages) contains some EDID data...
>
> > was it for the LVDS or the monitor? I can't seem to find your old
> > log.
>
That edid is from yo
; > --
> > (II) RADEON(0): Manufacturer: SAM Model: 91 Serial#: 1312961073
> > (II) RADEON(0): Year: 2005 Week: 14
> > (II) RADEON(0): EDID Version: 1.3
> > (II) RADEON(0): Digital Display Input
>
> Note the 'Digital Display Input' (and
On 8/30/07, Michel Dänzer <[EMAIL PROTECTED]> wrote:
> On Thu, 2007-08-30 at 09:54 -0400, Alex Deucher wrote:
>
> > Branden, remind me again what card this is and what connectors your
> > card has. Actually, the full log would be useful. It's it a mac,
> > we
On 8/30/07, Branden Robinson <[EMAIL PROTECTED]> wrote:
> On Thu, Aug 30, 2007 at 10:25:49AM -0400, Alex Deucher wrote:
> > On 8/30/07, Michel Dänzer <[EMAIL PROTECTED]> wrote:
> > > On Thu, 2007-08-30 at 09:54 -0400, Alex Deucher wrote:
> > >
> > &g
On 8/30/07, Branden Robinson <[EMAIL PROTECTED]> wrote:
> On Thu, Aug 30, 2007 at 01:17:29PM -0400, Alex Deucher wrote:
> > Ok. now we just need to figure out how the ports are mapped. Since
> > you have two DVI ports I suspect the one you are currently using it
> > dri
On 8/31/07, Branden Robinson <[EMAIL PROTECTED]> wrote:
> A bit more info:
>
> On Thu, Aug 30, 2007 at 08:16:04PM -0400, Alex Deucher wrote:
> > > http://redwald.deadbeast.net/tmp/branden_grief_4.jpeg
> > > http://redwald.deadbeast.net/tmp/branden_grief_5.jp
On 8/31/07, Branden Robinson <[EMAIL PROTECTED]> wrote:
> On Thu, Aug 30, 2007 at 08:16:04PM -0400, Alex Deucher wrote:
> > > Any mode change fixes the problem, but modes with resolutions smaller than
> > > 1600x1200 get rejected as being too small. Michel Dänzer seemed
On 9/1/07, Branden Robinson <[EMAIL PROTECTED]> wrote:
> On Fri, Aug 31, 2007 at 11:22:29PM -0400, Alex Deucher wrote:
> > It appears the driver thinks have two monitors connected. do you?
>
> Nope. Just the one, the Samsung SyncMaster 213T.
>
> I haven't switche
if dynamic clocks causes the problem, can you try removing that option
from your config and do a full power down cycle?
On 9/12/07, Nadav Kavalerchik <[EMAIL PROTECTED]> wrote:
> i've taken some "screen captures" with an external camera since the normal
> screen capture application ksnapshot does
ode is 1280 by
1024 and the physical size is according to the edid from the monitor:
II) RADEON(0): Supported additional Video Mode:
(II) RADEON(0): clock: 108.0 MHz Image Size: 317 x 254 mm
(II) RADEON(0): h_active: 1280 h_sync: 1328 h_sync_end 1440
h_blank_end 1688 h_border: 0
(II) RADEON(0): v_active: 1024 v_sync: 1025 v_sync_end 1028
v_blanking: 1066 v_border: 0
Alex
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On 9/7/07, Branden Robinson <[EMAIL PROTECTED]> wrote:
> On Sat, Sep 01, 2007 at 11:21:18AM -0400, Alex Deucher wrote:
> > On 9/1/07, Branden Robinson <[EMAIL PROTECTED]> wrote:
> > > That's three more experiments:
> > >
> > > 1) xrandr --ou
video hardware behind
the driver's back. Ideally you'd want to disable that and use acpi
events to have X blank the screen directly.
Alex
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
e for virtual size.
>
> However, on the very system where it fixes the mode selection it
> caused a lockup.
>
> 01:00.1 0380: 1002:5940 (rev 01)
>
> Radeon 9250 (reported as Radeon 9200 PRO) rv280
>
> Should I file a different bug about the lockups or is there one amon
akefile.linux
or
make -f Makefile.linux LINUXDIR=/path/to/kernel/src
depending on where your kernel source is located. make sure you have
run at least make dep on the kernel source.
Alex
>
> Cheers, Ariel
>
>
>
__
Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!
http://webhosting.yahoo.com/ps/sb/
the hw involved, this patch might help:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=66c2b84ba6256bc5399eed45582af9ebb3ba2c15
Alex
>
>Simon
>
> -- System Information:
> Debian Release: 8.0
> APT prefers testing
> APT policy: (990, 'testi
previous version was working correctly?
Does the problem only happen when you physically power off the
monitor? Does it come back ok when you let dpms kick in? How about
when you physically disconnect the monitor from the computer? Also,
what screensavers are you using? There may be a problema
mmand line in
grub or at runtime using xrandr (e.g., xrandr --output HDMI-0 --set
audio off). If that helps, can you try kernel 4.1?
Alex
>
> Owen Riddy
> Email: owen.ri...@gmail.com
> Mobile: 040 163 2663
>
> --
>
> On 18 May 2015 at 12:56, Michel Dänzer wrote:
>>
. Maybe Catalyst is a bit
> more forgiving or maybe there is some configuration issue here I don't
> understand.
>
> My problem is solved; there may still be a minor bug here in how the
> auto-configuration of the driver works.
The open source driver does not support YCbCr
ou appear to have disabled kms somehow and you are getting the vesa
driver rather than the native radeon driver.
Alex
> [18.639] (II) [KMS] drm report modesetting isn't supported.
> [18.639] (II) [KMS] drm report modesetting isn't supported.
> [18.639] (II) [KMS] dr
s a few years ago). If I move the mouse form the
primary display to the secondary display then X crashes.
zaphod mode ("classic" dualhead) is currently busted in radeon master.
If you want dualhead you'll need to use the old driver or use
mergedfb.
Alex
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
#355811 and it was fixed. This bug
> looks also like mine.
Does:
Option "BusType" "PCI"
fix the problem?
Alex
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On 7/28/07, Patrick Plattes <[EMAIL PROTECTED]> wrote:
> Alex Deucher schrieb:
> > Does:
> >
> > Option "BusType" "PCI"
> >
> > fix the problem?
>
> Yes, it works! Thanks! Do you know what the problem is?
>
> I only hav
s a VIA chipset (can't recall the brand/model can see later if
> needed)
Does
Option "BusType" "PCI"
help? You might also try the latest code in ati git master.
Alex
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
. I have
> attached the log file from an attempt to start the X server with the
> lid closed.
If the lid is closed, the panel is off and the driver find no
connected displays. Generally, if you start X with the lid closed
most users want to use one or more external monitors rather than the
i
tool! :-)
>
> Here's the culprit:
>
> f3d2ec3a5ae61215c792018320158750e7aa937c is first bad commit
> commit f3d2ec3a5ae61215c792018320158750e7aa937c
> Author: Alex Deucher <[EMAIL PROTECTED](none)>
> Date: Tue Dec 11 11:57:27 2007 -0500
>
> RADEON: rewrite PLL computation
&
seems that the lid is closed so the lvds is disabled. Can you diff
> the logs from the working and non-working cases?
If you are trying to start X with the lid closed and no external
monitors attached, it will not detect any connected outputs.
Generally when users start X with the lid closed, the
1 - 100 of 393 matches
Mail list logo
