Re: Bug#1036019: debian-installer: Broken X display with QEMU under UEFI with cirrus and std graphics

On Sun, 2023-05-14 at 19:40 +0200, Ben Hutchings wrote: [...] > This works for me with all the QEMU graphics devices. But I haven't > tested on real hardware. Now tested successfully on 2 custom desktops: - Asus P8Z68-V LX motherboard, Intel Core i5 2500 CPU, integrated GPU - ASRoc

Re: Bug#1036019: debian-installer: Broken X display with QEMU under UEFI with cirrus and std graphics

Control: tag -1 patch On Sun, 2023-05-14 at 00:21 +0200, Ben Hutchings wrote: [...] > So I suppose there's a regression in either efifb or fbdev_drv. I'm not spotting any functional changes in fbdev or the submodules it depends on between bullseye and bookworm. So this implicates

Re: Bug#1036019: debian-installer: Broken X display with QEMU under UEFI with cirrus and std graphics

lready have linux in > Built-Using via its udebs, so copying things around from linux-image > wouldn't change anything there, would it? > > Of course in the long run, if having those modules is desired, it will > be better to have them merged in linux and to drop the nasty code, e.g. > in a point release. [...] Definitely. I will spend some time investigating this, but I doubt I'll come up with a better fix in time. Ben. -- Ben Hutchings Life would be so much easier if we could look at the source code. signature.asc Description: This is a digitally signed message part

Bug#831420: RM: xserver-xorg-input-vmmouse -- RoQA; obsolete and conflicts with kernel

Package: ftp.debian.org Severity: normal This is a driver for the VMware virtual mouse device. We now enable the Linux kernel driver for this device, so Xorg will support it through its generic libinput or evdev driver. Further, the kernel and Xorg vmmouse drivers cannot be used at the same time

Re: Bug#831286: installation-reports: Reiser4 (SFRN 4.0.1) linux-image-4.6.0-1+reiser4.0.1-amd64(4.6.3-1) d-i on Jessie successful install on HP Pavilion

st not depend on the vmmouse driver. However, the Xorg vmmouse driver will continue to be used in jessie. The custom kernel used in this image should not include the vmmouse driver and should not declare that it breaks xserver-xorg-input- vmmouse.  This is what has been done in the jessi

Re: Bug#825916: installation-reports: Installing Debian with AMD/ATI Radeon graphics card does not go well

b is presumably preferable on UEFI systems.  uvesafb is another option but requires a userland helper. Ben. > Then maybe the user is able to find information on the web/IRC to fix the > problem. -- Ben Hutchings Any sufficiently advanced bug is indistinguishable from a feature. signature.asc Description: This is a digitally signed message part

Bug#779515: Should enable the qxl kernel driver when installed

Source: xserver-xorg-video-qxl Version: 0.1.1-2 Severity: normal I've enabled the kernel's qxl driver, but disabled by default so that it doesn't conflict with wheezy's version of xserver-xorg-video-qxl. Please install a modprobe configuration file with the line: options qxl modeset=1 (When

Re: Removing old unmaintained X drivers

workaround > is to disable acceleration. Truly a case of "bad breath is better than > no breath". This sounds like a good reason to remove it, unless both vesa and fbdev also fail on this hardware. Ben. -- Ben Hutchings The world is coming to an end. Please log off. signature.asc Description: This is a digitally signed message part

Improving hardware support in Debian stable

will require new logic in initramfs-tools to find the updated drivers. I'll keep thinking about how to solve this, but would appreciate suggestions from others... Ben. -- Ben Hutchings Experience is what causes a person to make new mistakes instead of old ones. signature.asc Description: This is a digitally signed message part

Re: Bug#572754: Closing

render when you switch back to its VT, whether or not the kernel is doing modesetting for it. X maintainers, could you comment on this? Ben. -- Ben Hutchings Never attribute to conspiracy what can adequately be explained by stupidity. signature.asc Description: This is a digitally signed message part

Re: 702668: not possible to select screen left of other screen, only clone mode is possible (solved)

On Sat, 2013-04-06 at 11:14 +, Jaap van Wingerde wrote: > Bug 702668 is solved with package . > > The problem with loading radeon firmware still exists. [...] How is this a problem? You have chosen not to install it. Ben. -- Ben Hutchings Power corrupts. Absolute power is kin

Re: Bug#702668: RV350 AQ: not possible to select screen left of other screen, only clone mode is possible

often cause memory corruption or a blank screen. However, for the older chips such as the R300 family radeon should be able to do KMS without any firmware (only 3D acceleration will be disabled, as before). I changed the driver again in 3.2.39-1 to revert to the previous behaviour for these chips.

Re: Bug#697029: [ilk] using GNOME 3 makes computer sluggish after a few minutes

up with some wording (though I > also wouldn't mind if someone else does). "Graphics rendering may be very slow on Intel 'Ironlake M' GPUs (PCI ID 8086:0046) when an IOMMU (VT-d) is enabled. The IOMMU functionality can be disabled for the GPU by adding the kernel

Bug#635137: Sometimes hangs after suspend & resume

Package: compiz Version: 0.8.4-4 Severity: important After suspending and resuming my laptop (Thinkpad T61 with Intel GM965 GPU) compiz sometimes appears to hang, leaving the X display blank except for the mouse pointer. The kernel, GPU and X server are still working: the mouse pointer is respons

Re: iMac-G3 fails to boot with 2.6.37-1-powerpc (Bug#614221)

On Sat, 2011-03-05 at 20:43 +, Ben Hutchings wrote: [...] > * Has anyone tested 2.6.37-{1,2} on a non-Mac system yet, and does > vga16fb work there? I'm still interested in the answer to this. [...] > * Could some Mac users test and report whether i915 or nouveau can > succe

Bug#616301: xserver-xorg-video-radeon:screen goes black, system hangs after 2sec:[youtube(FF/Opera)-reset req.]

gt; > having interrupting access / watchdog is nice if your driver can do that > > Ben Hutchings wrote: [...] Don't top-post. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part

Bug#616301: xserver-xorg-video-radeon:screen goes black, system hangs after 2sec:[youtube(FF/Opera)-reset req.]

On Sun, 2011-03-06 at 13:08 -0500, Alex Deucher wrote: > On Fri, Mar 4, 2011 at 8:50 PM, Ben Hutchings wrote: > > On Fri, 2011-03-04 at 21:01 +0200, Faidon Liambotis wrote: > >> severity 616301 critical > >> thanks > > > > No, not unless it will affect a

Re: Bug#616093: Possible Solution

On Sun, 2011-03-06 at 17:13 +0100, Martin Künstner wrote: > Am Sonntag, den 06.03.2011, 15:54 + schrieb Ben Hutchings: > > On Thu, 2011-03-03 at 16:13 +0100, Martin Künstner wrote: > > > Hello, > > > > > > after searching for "QFont::fromStri

Re: Bug#616093: Possible Solution

ole switching keystrokes should still work. Could you temporarily remove ibus and test that Strg-Alt-F1 works when the system is in this state? Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part

Bug#616301: xserver-xorg-video-radeon:screen goes black, system hangs after 2sec:[youtube(FF/Opera)-reset req.]

should be assigned to the kernel. Even without KMS, a Mesa driver should be considered untrusted and should not be able to trigger a crash or hang. With KMS, this applies to the X driver too. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part

Re: Bug#595511: linux-image-2.6.32-5-686: Blacklisting KMS for i8xx makes xorg intel driver unusable on these chipsets

and we generally follow their advice on what options and patches to use. We're not working with Ubuntu on this, though we did follow their lead in blacklisting those chips. Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking.

Bug#576393: qemu-kvm provokes segfault in X server

./../hw/xfree86/common/xf86Events.c (gdb) info locals x = 136180172 y = 134914603 (gdb) up #4 0x08074040 in Dispatch () at ../../dix/dispatch.c:407 407 ../../dix/dispatch.c: No such file or directory. in ../../dix/dispatch.c (gdb) info locals result = client = 0xa375870 nready = 0 start_tick = 1340 (gdb) up #5 0x0806693a in main (argc=9, argv=0xffc31114, envp=0xffc3113c) at ../../dix/main.c:285 285 ../../dix/main.c: No such file or directory. in ../../dix/main.c (gdb) info locals i = alwaysCheckForInput = {0, 1} -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part

Bug#576393: qemu-kvm provokes segfault in X server

Package: xserver-xorg Version: 1:7.5+5 Severity: important I've been exercising graphics in qemu-kvm a bit more and have seen the host's X server crash a couple of times. I expect I can reproduce it again if you want me to gather more information. The backtrace from Xorg.0.log.old is: Backtrace

Re: Packagaing nouveau firmware

On Mon, 2010-03-29 at 07:23 +0200, Sven Joachim wrote: > On 2010-03-29 03:36 +0200, Ben Hutchings wrote: > > > On Fri, 2010-03-26 at 18:43 +0100, Sven Joachim wrote: > >> Followed by the text of the actual license. Since Nvidia does not > >> distribute the files the

Re: Packagaing nouveau firmware

On Fri, 2010-03-26 at 18:43 +0100, Sven Joachim wrote: > On 2010-03-26 16:26 +0100, Ben Hutchings wrote: > > > On Fri, 2010-03-26 at 10:51 +0100, Sven Joachim wrote: > >> Thanks for the explanation. Speaking of the firmware, is anyone working > >> on packaging

Re: Bug#572067: linux-libc-dev: Can not install, file conflict with libdrm

On Fri, 2010-03-05 at 10:59 +0100, Julien Cristau wrote: > On Fri, Mar 5, 2010 at 04:03:15 +0000, Ben Hutchings wrote: > > > On Mon, 2010-03-01 at 13:50 +0100, Jens-Michael Hoffmann wrote: > > > Package: linux-libc-dev > > > Version: 2.6.33-1~experim

Bug#572067: Processed: reassign 572592 to linux-libc-dev, forcibly merging 572067 572592

On Fri, 2010-03-05 at 19:37 +0100, Bastian Blank wrote: > reassign 572067 libdrm-dev > thanks > > The linux kernel is source of the drm headers in the meantime. It *is*, but it shouldn't be. Let's fix this now. Ben. -- Ben Hutchings The most exhausting thing in l

Re: Bug#572067: linux-libc-dev: Can not install, file conflict with libdrm

linux-libc-dev. I'm happy to have libdrm-dev provide them all. What do you want to do? Ben. -- Ben Hutchings Q. Which is the greater problem in the world today, ignorance or apathy? A. I don't know and I couldn't care less. signature.asc Description: This is a digitally signed message part

Re: [ubuntu-x] Status of kernel X drivers

On Sun, 2010-02-21 at 23:20 +, Ben Hutchings wrote: [...] > I think this is something we will also consider doing in Debian. A year > from now I expect nv to be dead and radeon UMS to be removed upstream, > making it impractical to backport new hardware support. Given that, the >

Re: [ubuntu-x] Status of kernel X drivers

he backported drm, should we ask Greg K-H to pull that? Ben. -- Ben Hutchings 73.46% of all statistics are made up. signature.asc Description: This is a digitally signed message part

Bug#569103: Uses obsolete V4L1 API

Package: xserver-xorg-video-v4l Version: 3.95.dfsg.1-8.1 Severity: serious The V4L1 API is obsolete and does not work with most new V4L drivers. You can use libv4l as an emulation layer; see . Ben. -- System Information: Debian Release: squeeze/sid

Re: loading kernel mode setting drivers

Julien Cristau wrote: > On Mon, Jan 25, 2010 at 00:27:48 +0000, Ben Hutchings wrote: > > > What about my suggestion of removing the MODULE_DEVICE_TABLE > > declarations from fb modules, so they do not appear in modules.pcimap > > etc? Did you see any problem with that? &

Re: loading kernel mode setting drivers

ist $(basename $mod .ko); done > could work (possibly excluding some generic and backlight drivers, if > those should be autoloaded?). What about my suggestion of removing the MODULE_DEVICE_TABLE declarations from fb modules, so they do not appear in modules.pcimap etc? Did you see any probl

Re: loading kernel mode setting drivers

asible? Are there other/better solutions? That sounds like it might be a problem to maintain. Would it be feasible for each X video driver to blacklist the conflicting fb driver(s), in the same way that KMS-capable X video drivers set module parameters to enable KMS? Ben. -- Ben Hutchings The g

Re: Nouveau kernel driver

On Tue, 2010-01-05 at 22:15 +, Chris Lamb wrote: > Ben Hutchings wrote: > > > I'd like to pull nouveau from 2.6.33 into Debian's 2.6.32. I'm hoping > > this would allow for replacement of nv and its dodgy source with nouveau > > This sounds like a goo

Nouveau kernel driver

I'd like to pull nouveau from 2.6.33 into Debian's 2.6.32. I'm hoping this would allow for replacement of nv and its dodgy source with nouveau (I realise nouveau has its own issues with non-free bits, but they're more easily separable). Does this sound like a good idea? Ben

Bug#383465: Replacement of xserver-xorg-video-nv

Is nouveau likely to be in good enough shape to replace nv for squeeze? Ben. -- Ben Hutchings If at first you don't succeed, you're doing about average. signature.asc Description: This is a digitally signed message part

Bug#508126: xine-ui: ctrl/shift key press emulation implementation broken

On Sat, 2009-01-03 at 18:00 +0100, Julien Cristau wrote: > On Fri, Jan 2, 2009 at 15:30:01 +0000, Ben Hutchings wrote: > > > #508126: x11-utils: xprop -spy does not handle destruction properly > > > the xprop patch looks reasonable afaict, so go ahead and NMU. somebody

Bug#508126: xine-ui: ctrl/shift key press emulation implementation broken

themselves, RC. I have now proposed fixes for all of these, and the result appears to be robust. Should I NMU with these fixes? Should any of these bugs be down/upgraded? Ben. -- Ben Hutchings Lowery's Law: If it jams, force it. If it breaks, it needed replacing anyway. signatur

Bug#508126: x11-utils: xprop -spy does not handle destruction properly

if (props) { int i; --- END --- -- Ben Hutchings All the simple programs have been written, and all the good names taken. signature.asc Description: This is a digitally signed message part

Bug#508126: x11-utils: xprop -spy does not handle destruction properly

Package: x11-utils Version: 7.3+2 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I would expect xprop -spy to exit cleanly when the target window is destroyed. The actual behaviour is that it sometimes dies with a BadWindow error and sometimes hangs around after the target has

Bug#502675: closed by Julien Cristau <[EMAIL PROTECTED]> (Bug#502675: fixed in libdrm 2.3.1-2)

Julien Cristau <[EMAIL PROTECTED]> wrote: > libdrm (2.3.1-2) unstable; urgency=high > . > * Remove from the source package a bunch of files that are only used by the > kernel drm component. This gets rid of the mga, r128 and radeon > microcode, and thus closes:

Bug#502675: libdrm: Binary firmware in driver source

Package: libdrm Version: 2.3.1-1 Severity: serious Justification: Policy 2.2.1 The libdrm source package includes the DRM drivers mga, r128, radeon which include sourceless firmware images. These could all be removed from the source package since the drivers are built as part of linux-2.6. Ben.

cloning 490601, reassign -1 to xorg-server

# Automatically generated email from bts, devscripts version 2.10.34 clone 490601 -1 reassign -1 xorg-server 2:1.4.2-2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#491979: X server can return BadMatch to WM instead of BadWindow

@ -245,7 +245,7 @@ { int rc; rc = dixLookupDrawable((DrawablePtr*)pWin, id, client, M_WINDOW, access); -return (rc == BadDrawable) ? BadWindow : rc; +return (rc == BadDrawable || rc == BadMatch) ? BadWindow : rc; } _X_EXPORT int -- Ben Hutchings Usenet is essentially a HUGE

Bug#491979: [Fwd: Re: Bug#490601: fails with many xio errors when started from xdm]

Forwarded Message From: Ben Hutchings <[EMAIL PROTECTED]> To: Tuomo Valkonen <[EMAIL PROTECTED]> Cc: Ion general <[EMAIL PROTECTED]> Subject: Re: Bug#490601: fails with many xio errors when started from xdm Date: Mon, 21 Jul 2008 01:00:41 +0100 I got a rep

Bug#486606: xdm:unable to login - XDM authorization key matches an existing client

On Sun, Jun 29, 2008 at 06:24:18PM +0200, Julien Cristau wrote: > On Sun, Jun 29, 2008 at 15:41:08 +0100, Ben Hutchings wrote: > > > On Sun, Jun 29, 2008 at 04:11:04PM +0200, Brice Goglin wrote: > > > Ben Hutchings wrote: > > > > In the interim, I made an NMU

Bug#486606: xdm:unable to login - XDM authorization key matches an existing client

On Sun, Jun 29, 2008 at 04:11:04PM +0200, Brice Goglin wrote: > Ben Hutchings wrote: > > In the interim, I made an NMU with the following trivial change. > > > > Did you read the bug log before doing so? Julien committed a fix for > this bug and another one and marke

Bug#486606: xdm:unable to login - XDM authorization key matches an existing client

XDM-AUTHORIZATION in favour of MIT-MAGIC-COOKIE (closes: #486606) + + -- Ben Hutchings <[EMAIL PROTECTED]> Sun, 29 Jun 2008 12:23:37 + + xdm (1:1.1.8-1) unstable; urgency=low * Drop lintian overrides, they're unused anyway. diff -u xdm-1.1.8/debian/rules xdm-1.1.8/debian/rules --

Bug#487834: xserver-xorg-video-radeon: Image scaling busted with XAA on Mobility Radeon 9600

Package: xserver-xorg-video-radeon Version: 1:6.8.191-3 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 In Iceweasel 3 I see black rectangles in place of images that are scaled. This doesn't happen if I enable EXA, but that is currently too slow to be usable on this hardware.

Bug#487834: xserver-xorg-video-radeon: Image scaling busted with XAA on Mobility Radeon 9600

Option "XaaNoOffscreenPixmaps" seems to fix this, so presumably it should be enabled by default on this hardware. Ben. -- Ben Hutchings Never attribute to conspiracy what can adequately be explained by stupidity. signature.asc Description: This is a digitally signed message part

Bug#421025: XCreateFontSet fails with fixed 13 as first font pattern in UTF-8 environment

On Sun, 2007-09-23 at 06:29 +0100, Ben Hutchings wrote: > Run this with the argument > "-*-fixed-*-*-*-*-*-*-*-*-*-*-JISX0208.1983-0" and you should see the > bug (or not). I suspect you won't see it. With my normal X server I get: $ ./listfonts -*-fixed-*-*-*-*-13-*

Bug#421025: XCreateFontSet fails with fixed 13 as first font pattern in UTF-8 environment

On Fri, 2007-08-10 at 11:48 +0200, Brice Goglin wrote: > Ben Hutchings wrote: > > If list->charset_list != NULL and list->charset_count == 0, the Xmalloc > > call in copy_string_list might return NULL (I don't know whether it > > supports a size of 0), causing cop

Bug#421025: XCreateFontSet fails with fixed 13 as first font pattern in UTF-8 environment

of 0), causing copy_string_list and XCreateFontSet() to return NULL. This seems unlikely to be triggered only by the exact font pattern lists I identified though. Ben. -- Ben Hutchings If God had intended Man to program, we'd have been born with serial I/O ports. signature.asc Description: This is a digitally signed message part

Bug#421025: XCreateFontSet fails with fixed 13 as first font pattern in UTF-8 environment

try to debug a little bit and see while it fails? I don't know where to look. strace shows no system call failures, but it can dump the X protocol conversation (-e read=3 -e write=3). Would that be useful? Ben. -- Ben Hutchings Life would be so much easier if we could look at the sour

Bug#421025: XCreateFontSet fails with fixed 13 as first font pattern in UTF-8 environment

Package: libx11-6 Version: 2:1.0.3-7 Severity: normal --- Please enter the report below this line. --- Test program: -- BEGIN -- #include #include #include #include int main(int argc, char ** argv) { Display * display; XFontSet fs; char ** missing = 0; int nmissing; char

Bug#333273: xvfb: Uses incorrect line padding when depth>8

x in the current version in Debian. Therefore I'm closing this with the first version number for xorg-server in Debian. Ben. -- Ben Hutchings It is easier to change the specification to fit the program than vice versa. signature.asc Description: This is a digitally signed message part

Bug#333273: xvfb: Uses incorrect line padding when depth>8

Package: xvfb Version: 4.3.0.dfsg.1-14sarge1 Severity: important According to the Xvfb manual page, the -fbdir option can be used to make it expose its framebuffer in X window dump format. However, if it is run with a depth of 32, the bytes_per_line member of the XWDHeader structure is set to 4 *