i845 support
Is there any plan to include i845 support in the 4.2.x releases? Michael Cardenas posted a patch about a year ago and it was maybe scheduled to go in to 4.2.1-4, but it isn't in the changelog and I can't find the patch in debian/patches, so I'm assuming it isn't in. Would it be possible to get this patch in, or is it going to be better to wait for 4.3? (And I didn't even ask when 4.3 was going to be uploaded :)
i845 support
Is there any plan to include i845 support in the 4.2.x releases? Michael Cardenas posted a patch about a year ago and it was maybe scheduled to go in to 4.2.1-4, but it isn't in the changelog and I can't find the patch in debian/patches, so I'm assuming it isn't in. Would it be possible to get this patch in, or is it going to be better to wait for 4.3? (And I didn't even ask when 4.3 was going to be uploaded :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#213339: Upgrading from Woody XF86Config-4 (and Xwrapper.config) are not written
Package: xserver-xfree86 Version: 4.2.1-11 Severity: normal NB: This bug report is for a non-net-connected Sun Ultra 5. I installed woody from disk 1 only, selected X window system task. Added an unstable APT line and apt-get upgraded. When I then started X it did not have a config file. It seemed that dpkg-reconfigure xserver-xfree86 did not work - it complained about the file not existing. I touched the config and it complained about no stored checksum. So I added an md5sum in /var/lib/xfree86 and it wrote the file OK. I also had the same problem with Xwrapper.config, and I get this message when reconfiguring xserver-xfree86: Note: not updating /etc/X11/X; file has been customized. Unfortunately I didn't try X before the upgrade.
Bug#213339: Upgrading from Woody XF86Config-4 (and Xwrapper.config) are not written
Package: xserver-xfree86 Version: 4.2.1-11 Severity: normal NB: This bug report is for a non-net-connected Sun Ultra 5. I installed woody from disk 1 only, selected X window system task. Added an unstable APT line and apt-get upgraded. When I then started X it did not have a config file. It seemed that dpkg-reconfigure xserver-xfree86 did not work - it complained about the file not existing. I touched the config and it complained about no stored checksum. So I added an md5sum in /var/lib/xfree86 and it wrote the file OK. I also had the same problem with Xwrapper.config, and I get this message when reconfiguring xserver-xfree86: Note: not updating /etc/X11/X; file has been customized. Unfortunately I didn't try X before the upgrade. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: a small C program to test xdm's /dev/mem reading on your architecture
On Monday 26 Aug 2002 7:20 am, Branden Robinson wrote: > I need people with root on machines of your given architecture to > compile and run the attached C program. It consists of code borrowed > from xdm's genauth.c program. Runs OK on hppa (712/80, hppa1.1, Woody).
Re: [debian-x] DRI device permissions
On Thursday 02 Aug 2001 2:33 am, you wrote: > If you want to be able to access the dri by a normal user you need to > either create a dri group or open the premissions up to everybody with a > chmod -R 666 /dev/dri Thanks. Are there plans to create a dri group by default on Debian systems in the future?
DRI device permissions
Direct rendering is only working for root on my system (unstable/4.1.0). The permissions for the DRI device files are: /dev/dri: drwxrwx---2 root root 4096 Aug 1 15:22 dri /dev/dri/*: crw-rw1 root root 10, 63 Aug 1 15:22 card0 glxinfo as non-root: [EMAIL PROTECTED]:~$ glxinfo name of display: :0.0 libGL error: failed to open DRM: Operation not permitted libGL error: reverting to (slow) indirect rendering Are my permissions incorrect?
Re: [debian-x] DRI device permissions
On Thursday 02 Aug 2001 2:33 am, you wrote: > If you want to be able to access the dri by a normal user you need to > either create a dri group or open the premissions up to everybody with a > chmod -R 666 /dev/dri Thanks. Are there plans to create a dri group by default on Debian systems in the future? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
DRI device permissions
Direct rendering is only working for root on my system (unstable/4.1.0). The permissions for the DRI device files are: /dev/dri: drwxrwx---2 root root 4096 Aug 1 15:22 dri /dev/dri/*: crw-rw1 root root 10, 63 Aug 1 15:22 card0 glxinfo as non-root: will@dogfox:~$ glxinfo name of display: :0.0 libGL error: failed to open DRM: Operation not permitted libGL error: reverting to (slow) indirect rendering Are my permissions incorrect? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
