xhost wierdness
using woody 4.0.1-0phase2v13. I haven't put these access rules (it showed up when I upgraded to XFree 4.0). Is this hardcoded or am I missing something ? > xhost access control enabled, only authorized clients can connect INET:localhost INET:my.host.com LOCAL: > xhost -my.host.com my.host.com being removed from access control list > xhost access control enabled, only authorized clients can connect INET:localhost INET:my.host.com LOCAL: -- Kresimir Kukulj[EMAIL PROTECTED] +--+ Old PC's never die. They just become Unix terminals.
release critical != important (was: Re: Bug#72135: not release critical
On Mon, Oct 16, 2000 at 12:39:25AM -0500, Branden Robinson wrote: > severity 72041 normal > severity 72135 normal > severity 70750 normal > thanks > > These are not release-critical problems. All are in reference to the 3.x > branch of XFree86, which not actively maintained. Patches for Hurd support > in 4.x are welcome, as will be a bug report against the 4.x server for > crashing problems; but please wait until 4.x .debs are officially released. The packages don't build on the Hurd. Bugs which cause the package to not build on some architecture have always been considered as bugs of severity "important". It's unfortunate that the BTS doesn't make a difference between released and unreleased architectures [1] and maintained and not maintained packages, but this is not a sound reason to strip the severity. In other words, please reverse the severity change. I have talked to Steve, and he will incorporate my patches and then they can be properly closed. Thanks, Marcus [1] We don't even know if the Hurd will or won't be released with the next Debian version. -- `Rhubarb is no Egyptian god.' Debian http://www.debian.org Check Key server Marcus Brinkmann GNUhttp://www.gnu.orgfor public PGP Key [EMAIL PROTECTED], [EMAIL PROTECTED]PGP Key ID 36E7CD09 http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ [EMAIL PROTECTED]
xhost wierdness
using woody 4.0.1-0phase2v13. I haven't put these access rules (it showed up when I upgraded to XFree 4.0). Is this hardcoded or am I missing something ? > xhost access control enabled, only authorized clients can connect INET:localhost INET:my.host.com LOCAL: > xhost -my.host.com my.host.com being removed from access control list > xhost access control enabled, only authorized clients can connect INET:localhost INET:my.host.com LOCAL: -- Kresimir Kukulj[EMAIL PROTECTED] +--+ Old PC's never die. They just become Unix terminals. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
release critical != important (was: Re: Bug#72135: not release critical
On Mon, Oct 16, 2000 at 12:39:25AM -0500, Branden Robinson wrote: > severity 72041 normal > severity 72135 normal > severity 70750 normal > thanks > > These are not release-critical problems. All are in reference to the 3.x > branch of XFree86, which not actively maintained. Patches for Hurd support > in 4.x are welcome, as will be a bug report against the 4.x server for > crashing problems; but please wait until 4.x .debs are officially released. The packages don't build on the Hurd. Bugs which cause the package to not build on some architecture have always been considered as bugs of severity "important". It's unfortunate that the BTS doesn't make a difference between released and unreleased architectures [1] and maintained and not maintained packages, but this is not a sound reason to strip the severity. In other words, please reverse the severity change. I have talked to Steve, and he will incorporate my patches and then they can be properly closed. Thanks, Marcus [1] We don't even know if the Hurd will or won't be released with the next Debian version. -- `Rhubarb is no Egyptian god.' Debian http://www.debian.org Check Key server Marcus Brinkmann GNUhttp://www.gnu.orgfor public PGP Key [EMAIL PROTECTED], [EMAIL PROTECTED]PGP Key ID 36E7CD09 http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Error during start X with i810 VGA card. :(
Chung, (or is it Ha-Nyung?) I believe the DRI/AGP features require a much newer kernel. If you try kernel 2.4.0-test*, being sure to build with agpgart support, I think your system will work with 4.0.1. But I can't be sure. :) Best of luck. * Chung, Ha-Nyung <[EMAIL PROTECTED]> [001016 06:14]: > > Currently, I update X to 4.0.1 phase2, maybe correct?, in woody. > I'm using Compaq Deskpro with VGA card using i810 chipset. > With XF86 3.3.6, I have no problem using X with this machine, > but after updating I got the error during startx. > /var/log/XFree86.0.log file is following... > > > XFree86 Version 4.0.1c / X Window System > (protocol Version 11, revision 0, vendor release 6400) > Release Date: 28 August 2000 > If the server is older than 6-12 months, or if your card is newer > than the above date, look for a newer version before reporting > problems. (see http://www.XFree86.Org/FAQ) > Operating System: Linux 2.2.17pre10 i686 [ELF] > Module Loader present > (==) Log file: "/var/log/XFree86.0.log", Time: Mon Oct 16 21:48:03 2000 > (==) Using config file: "/etc/X11/XF86Config-4" > Markers: (--) probed, (**) from config file, (==) default setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (??) unknown. > (==) ServerLayout "Default Layout" > (**) |-->Screen "Default Screen" (0) > (**) | |-->Monitor "Generic Monitor" > (**) | |-->Device "Generic Graphics Device" > (**) |-->Input Device "Generic Keyboard" > (**) Option "XkbRules" "xfree86" > (**) XKB: rules: "xfree86" > (**) Option "XkbModel" "pc104" > (**) XKB: model: "pc104" > (**) Option "XkbLayout" "us" > (**) XKB: layout: "us" > (**) |-->Input Device "Generic Mouse" > (**) FontPath set to > "/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/100dpi:unscaled,/usr/lib/X11/fonts/75dpi:unscaled,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/sun" > (==) RgbPath set to "/usr/X11R6/lib/X11/rgb" > (==) ModulePath set to "/usr/X11R6/lib/modules" > (--) using VT number 7 > > (II) Module ABI versions: > XFree86 ANSI C Emulation: 0.1 > XFree86 Video Driver: 0.3 > XFree86 XInput driver : 0.1 > XFree86 Server Extension : 0.1 > XFree86 Font Renderer : 0.1 > (II) Loader running on linux > (II) LoadModule: "bitmap" > (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a > (II) Module bitmap: vendor="The XFree86 Project" > compiled for 4.0.1c, module version = 1.0.0 > Module class: XFree86 Font Renderer > ABI class: XFree86 Font Renderer, version 0.1 > (II) Loading font Bitmap > (II) LoadModule: "pcidata" > (II) Loading /usr/X11R6/lib/modules/libpcidata.a > (II) Module pcidata: vendor="The XFree86 Project" > compiled for 4.0.1c, module version = 0.1.0 > ABI class: XFree86 Video Driver, version 0.3 > (II) PCI: Probing config type using method 1 > (II) PCI: Config type is 1 > (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 > (II) PCI: PCI scan (all values are in hex) > (II) PCI: 00:00:0: chip 8086,7124 card , rev 03 class 06,00,00 hdr 00 > (II) PCI: 00:01:0: chip 8086,7125 card 0e11,b191 rev 03 class 03,00,00 hdr 00 > (II) PCI: 00:1e:0: chip 8086,2418 card , rev 02 class 06,04,00 hdr 01 > (II) PCI: 00:1f:0: chip 8086,2410 card , rev 02 class 06,01,00 hdr 80 > (II) PCI: 00:1f:1: chip 8086,2411 card 8086,2411 rev 02 class 01,01,80 hdr 00 > (II) PCI: 00:1f:2: chip 8086,2412 card 8086,2412 rev 02 class 0c,03,00 hdr 00 > (II) PCI: 00:1f:5: chip 8086,2415 card 0e11,b189 rev 02 class 04,01,00 hdr 00 > (II) PCI: 01:09:0: chip 8086,1229 card 8086,0009 rev 05 class 02,00,00 hdr 00 > (II) PCI: End of PCI scan > (II) LoadModule: "scanpci" > (II) Loading /usr/X11R6/lib/modules/libscanpci.a > (II) Module scanpci: vendor="The XFree86 Project" > compiled for 4.0.1c, module version = 0.1.0 > ABI class: XFree86 Video Driver, version 0.3 > (II) UnloadModule: "scanpci" > (II) Unloading /usr/X11R6/lib/modules/libscanpci.a > (II) Host-to-PCI bridge: > (II) Bus -1: bridge is at (0:0:0), (-1,-1,0), BCTRL: 0x00 (VGA_EN is cleared) > (II) Bus -1 I/O range: > [0] -1 0x - 0x (0x1) IX[B] > (II) Bus -1 non-prefetchable memory range: > [0] -1 0x - 0x (0x0) MX[B] > (II) Bus -1 prefetchable memory range: > [0] -1 0x - 0x (0x0) MX[B] > (II) PCI-to-ISA bridge: > (II) Bus -1: bridge is at (0:31:0), (0,-1,0), BCTRL: 0x00 (VGA_EN is cleared) > (II) Bus -1 I/O range: > (II) Bus -1 non-prefetchable memory range: > (II) Bus -1 prefetchable memory range: > (II) PCI-to-PCI bridge: > (II) Bus 1: bridge is at (0:30:0), (0,1,1), BCTRL: 0x06 (VGA_EN is cleared) > (II) Bus 1 I/O range: > [0] -1 0x1000 - 0x10ff (0x100) IX[B] > [1] -1 0x1400 - 0x14ff (0x100) IX[B] > [2] -1 0x1800 - 0x0
Re: debian large fonts anti-aliasing
Check you /etc/X11/XF86Config file. I bet you have references to the 75 and 100 dpi fonts in your fontpath before the font server. Also try adding :noscale to the end of the 75dpi and 100dpi font directories. HTH * Fabricio Matheus Goncalves <[EMAIL PROTECTED]> [001016 09:28]: > > OS: Debian Gnu/Linux 2.2 > > Aplication: xfs (XFree86) 3.3.6-11 > > Problem: In redhat with the same XFree version (3.3.6) it can display nice > large fonts. > Now using debian that fonts show broken, a think that is missing > anti-aliasing, but i dont know. > When i point my debian X to use a redhat xfs running at another computer > all works fine. > So i try install redhat xfs using alien to convert package, but the result > is yet broken fonts. > Im very confuse, and didnt find any reference to this kind of throuble. > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >
Re: libX11 is borked (or is it glibc ?)
> > Binary compatibility means you con run programs linked against older > > libraries. Guess what, X and the libX11 linked apps still work don't they? > > To me "binary compatible" means that, things act as they did before > ... when linked with the old library. Which includes being able to > "run" your old libraries linked against old libraries. Your definition is incorrect. > > > % nm -g /usr/lib/debug/libc-2.1.3.so | egrep GLIB | egrep chown > > > 000913c8 T __chown@@GLIBC_2.1 > > > 000913c8 T chown@@GLIBC_2.1 > > > 00091454 T [EMAIL PROTECTED] > > > % nm -g /usr/lib/debug/libc-2.1.3.so | egrep GLIB | egrep fopen > > > 0004b5c4 T _IO_file_fopen@@GLIBC_2.1 > > > 0004da48 T [EMAIL PROTECTED] > > > 000481e0 T _IO_fopen@@GLIBC_2.1 > > > 0004a9a0 T [EMAIL PROTECTED] > > > 000481e0 T fopen@@GLIBC_2.1 > > > 0004a9a0 T [EMAIL PROTECTED] > > > > > > So either something bad has happened with the glibc versioning > > > upstream or glibc was built badly. > > > > No, this is inherent in versioned symbols. The old symbol is now "weak", > > which means it is there for using by old programs, but cannot be used when > > linking. A weak symbol keeps compatibility, which allowing the new strong > > symbol to be used for newly compiled applications. > > This seems wrong, for instance ulimit() is a weak alias for > __ulimit. But maybe you mean something different ? And applications/libs using ulimit() reference __ulimit instead. But if a lib referenced the ulimit weak symbol instead (somehow), then it would have to be recompiled if you wanted to link against it (but it would still continue to work as before). > I was pretty sure that I'd compiled/linked programs against glibc-2.1.3 > and another library that used 2.0.7. Maybe I'm getting senile in my > old age or maybe it worked but doesn't guarantee it. Not everything has to be recompiled. Just libs that use obsolete symbols (ones that have changed to weak symbols for compatibility, but now have newer versions of that symbol). We had this same issue with the 2.0.7 -> 2.1.0 upgrade. It was actually a lot more extensive than this upgrade. > Ahh well learn something bad every day I guess. Heh, I'd rather have this than have to recompile all applications because versioned symbols did not exist to begin with. Atleast with this scheme, we have an upgrade path (that wasn't there for the libc5 -> libc6 changeover). Ben -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---'
re: XtMakeGeometry errors resolved [UPDATE]
> On Sat, Oct 14, 2000 at 05:53:29PM -0500, Derek J Witt wrote: > > Hi, all. I figured out a way to resolve the "parent not composite" errors > > I've been getting from the xaw packages. I tried running apt-get to > > install X from the phase2 debbies. Of course, I started getting the > > error. > I talked to Keith Packard about this at ALS. > He says this is definitely a specification violation. It may be that > Athena can be recoded to fix it, however, as I understand it, since most > programs don't subclass the Athena widgets. and unfortunately not only anthena programms suffer, ie. netscape breaks too (try dragging a link from one netscape window to another, normaly the link would be opend in the new window but now netscape just quits.. - it doesn´t show the message, but a strace shows that it tried to display the error message) i guess the most programms which trigger XtMakeGeometry errors like gv, etc could fixed (easyly or not..) but for netscape i wouldn't hold breath :( -- Jens Hoffmann
debian large fonts anti-aliasing
OS: Debian Gnu/Linux 2.2 Aplication: xfs (XFree86) 3.3.6-11 Problem: In redhat with the same XFree version (3.3.6) it can display nice large fonts. Now using debian that fonts show broken, a think that is missing anti-aliasing, but i dont know. When i point my debian X to use a redhat xfs running at another computer all works fine. So i try install redhat xfs using alien to convert package, but the result is yet broken fonts. Im very confuse, and didnt find any reference to this kind of throuble.
Re: libX11 is borked (or is it glibc ?)
Ben Collins <[EMAIL PROTECTED]> writes: > On Mon, Oct 16, 2000 at 01:10:03AM -0400, James Antill wrote: > > Daniel Jacobowitz <[EMAIL PROTECTED]> writes: > > > > > On Mon, Oct 16, 2000 at 01:59:11AM +0200, Johannes Zellner wrote: > > > > Hello, > > > > > > > > I cannot link any more against libX11.so: > > > > > > > > /usr/X11R6/lib/libX11.so: undefined reference to `getpwnam_r@@GLIBC_2.0' > > > > > > > > this shows, even if I link a minimal c program. > > > > > > > > my versions: > > > > ii xlib6g 3.3.6-11 > > > > ii libc6 2.1.94-3 > > > > > > > > Any comments ? > > > > > > To compile against a library built under an old glibc, the library > > > needs to be recompiled to the new libc. > > > > If this is true then there isn't any binary compatibility. > > The whole point of the symbols looking like the above is so that > > there can be multiple versions of them. Eg. > > Binary compatibility means you con run programs linked against older > libraries. Guess what, X and the libX11 linked apps still work don't they? To me "binary compatible" means that, things act as they did before ... when linked with the old library. Which includes being able to "run" your old libraries linked against old libraries. > > % nm -g /usr/lib/debug/libc-2.1.3.so | egrep GLIB | egrep chown > > 000913c8 T __chown@@GLIBC_2.1 > > 000913c8 T chown@@GLIBC_2.1 > > 00091454 T [EMAIL PROTECTED] > > % nm -g /usr/lib/debug/libc-2.1.3.so | egrep GLIB | egrep fopen > > 0004b5c4 T _IO_file_fopen@@GLIBC_2.1 > > 0004da48 T [EMAIL PROTECTED] > > 000481e0 T _IO_fopen@@GLIBC_2.1 > > 0004a9a0 T [EMAIL PROTECTED] > > 000481e0 T fopen@@GLIBC_2.1 > > 0004a9a0 T [EMAIL PROTECTED] > > > > So either something bad has happened with the glibc versioning > > upstream or glibc was built badly. > > No, this is inherent in versioned symbols. The old symbol is now "weak", > which means it is there for using by old programs, but cannot be used when > linking. A weak symbol keeps compatibility, which allowing the new strong > symbol to be used for newly compiled applications. This seems wrong, for instance ulimit() is a weak alias for __ulimit. But maybe you mean something different ? I was pretty sure that I'd compiled/linked programs against glibc-2.1.3 and another library that used 2.0.7. Maybe I'm getting senile in my old age or maybe it worked but doesn't guarantee it. Ahh well learn something bad every day I guess. -- James Antill -- [EMAIL PROTECTED] "If we can't keep this sort of thing out of the kernel, we might as well pack it up and go run Solaris." -- Larry McVoy.
Re: Error during start X with i810 VGA card. :(
Chung, (or is it Ha-Nyung?) I believe the DRI/AGP features require a much newer kernel. If you try kernel 2.4.0-test*, being sure to build with agpgart support, I think your system will work with 4.0.1. But I can't be sure. :) Best of luck. * Chung, Ha-Nyung <[EMAIL PROTECTED]> [001016 06:14]: > > Currently, I update X to 4.0.1 phase2, maybe correct?, in woody. > I'm using Compaq Deskpro with VGA card using i810 chipset. > With XF86 3.3.6, I have no problem using X with this machine, > but after updating I got the error during startx. > /var/log/XFree86.0.log file is following... > > > XFree86 Version 4.0.1c / X Window System > (protocol Version 11, revision 0, vendor release 6400) > Release Date: 28 August 2000 > If the server is older than 6-12 months, or if your card is newer > than the above date, look for a newer version before reporting > problems. (see http://www.XFree86.Org/FAQ) > Operating System: Linux 2.2.17pre10 i686 [ELF] > Module Loader present > (==) Log file: "/var/log/XFree86.0.log", Time: Mon Oct 16 21:48:03 2000 > (==) Using config file: "/etc/X11/XF86Config-4" > Markers: (--) probed, (**) from config file, (==) default setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (??) unknown. > (==) ServerLayout "Default Layout" > (**) |-->Screen "Default Screen" (0) > (**) | |-->Monitor "Generic Monitor" > (**) | |-->Device "Generic Graphics Device" > (**) |-->Input Device "Generic Keyboard" > (**) Option "XkbRules" "xfree86" > (**) XKB: rules: "xfree86" > (**) Option "XkbModel" "pc104" > (**) XKB: model: "pc104" > (**) Option "XkbLayout" "us" > (**) XKB: layout: "us" > (**) |-->Input Device "Generic Mouse" > (**) FontPath set to >"/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/100dpi:unscaled,/usr/lib/X11/fonts/75dpi:unscaled,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/sun" > (==) RgbPath set to "/usr/X11R6/lib/X11/rgb" > (==) ModulePath set to "/usr/X11R6/lib/modules" > (--) using VT number 7 > > (II) Module ABI versions: > XFree86 ANSI C Emulation: 0.1 > XFree86 Video Driver: 0.3 > XFree86 XInput driver : 0.1 > XFree86 Server Extension : 0.1 > XFree86 Font Renderer : 0.1 > (II) Loader running on linux > (II) LoadModule: "bitmap" > (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a > (II) Module bitmap: vendor="The XFree86 Project" > compiled for 4.0.1c, module version = 1.0.0 > Module class: XFree86 Font Renderer > ABI class: XFree86 Font Renderer, version 0.1 > (II) Loading font Bitmap > (II) LoadModule: "pcidata" > (II) Loading /usr/X11R6/lib/modules/libpcidata.a > (II) Module pcidata: vendor="The XFree86 Project" > compiled for 4.0.1c, module version = 0.1.0 > ABI class: XFree86 Video Driver, version 0.3 > (II) PCI: Probing config type using method 1 > (II) PCI: Config type is 1 > (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 > (II) PCI: PCI scan (all values are in hex) > (II) PCI: 00:00:0: chip 8086,7124 card , rev 03 class 06,00,00 hdr 00 > (II) PCI: 00:01:0: chip 8086,7125 card 0e11,b191 rev 03 class 03,00,00 hdr 00 > (II) PCI: 00:1e:0: chip 8086,2418 card , rev 02 class 06,04,00 hdr 01 > (II) PCI: 00:1f:0: chip 8086,2410 card , rev 02 class 06,01,00 hdr 80 > (II) PCI: 00:1f:1: chip 8086,2411 card 8086,2411 rev 02 class 01,01,80 hdr 00 > (II) PCI: 00:1f:2: chip 8086,2412 card 8086,2412 rev 02 class 0c,03,00 hdr 00 > (II) PCI: 00:1f:5: chip 8086,2415 card 0e11,b189 rev 02 class 04,01,00 hdr 00 > (II) PCI: 01:09:0: chip 8086,1229 card 8086,0009 rev 05 class 02,00,00 hdr 00 > (II) PCI: End of PCI scan > (II) LoadModule: "scanpci" > (II) Loading /usr/X11R6/lib/modules/libscanpci.a > (II) Module scanpci: vendor="The XFree86 Project" > compiled for 4.0.1c, module version = 0.1.0 > ABI class: XFree86 Video Driver, version 0.3 > (II) UnloadModule: "scanpci" > (II) Unloading /usr/X11R6/lib/modules/libscanpci.a > (II) Host-to-PCI bridge: > (II) Bus -1: bridge is at (0:0:0), (-1,-1,0), BCTRL: 0x00 (VGA_EN is cleared) > (II) Bus -1 I/O range: > [0] -1 0x - 0x (0x1) IX[B] > (II) Bus -1 non-prefetchable memory range: > [0] -1 0x - 0x (0x0) MX[B] > (II) Bus -1 prefetchable memory range: > [0] -1 0x - 0x (0x0) MX[B] > (II) PCI-to-ISA bridge: > (II) Bus -1: bridge is at (0:31:0), (0,-1,0), BCTRL: 0x00 (VGA_EN is cleared) > (II) Bus -1 I/O range: > (II) Bus -1 non-prefetchable memory range: > (II) Bus -1 prefetchable memory range: > (II) PCI-to-PCI bridge: > (II) Bus 1: bridge is at (0:30:0), (0,1,1), BCTRL: 0x06 (VGA_EN is cleared) > (II) Bus 1 I/O range: > [0] -1 0x1000 - 0x10ff (0x100) IX[B] > [1] -1 0x1400 - 0x14ff (0x100) IX[B] > [2] -1 0x1800 - 0x0
Re: debian large fonts anti-aliasing
Check you /etc/X11/XF86Config file. I bet you have references to the 75 and 100 dpi fonts in your fontpath before the font server. Also try adding :noscale to the end of the 75dpi and 100dpi font directories. HTH * Fabricio Matheus Goncalves <[EMAIL PROTECTED]> [001016 09:28]: > > OS: Debian Gnu/Linux 2.2 > > Aplication: xfs (XFree86) 3.3.6-11 > > Problem: In redhat with the same XFree version (3.3.6) it can display nice > large fonts. > Now using debian that fonts show broken, a think that is missing > anti-aliasing, but i dont know. > When i point my debian X to use a redhat xfs running at another computer > all works fine. > So i try install redhat xfs using alien to convert package, but the result > is yet broken fonts. > Im very confuse, and didnt find any reference to this kind of throuble. > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 4.0.1 debs and potato
Well before X4 debs existed at all, I had a method (put together specifically for getting nVidia cards working with debian) for instaling X4 from source so that it sits in a seperate tree, alongside your normal debian X3.3.6 install. I wrote a quick HOWTO (basically for members of my local LUG), which is at: http://games.luv.asn.au/lsd Thanks Leigh On Mon, 16 Oct 2000 14:35:14 +0200, Charl P. Botha said: > Dear debian-xers, > > Thanks to Branden's debs I have the phase2 4.0.1 v15 debs running very > smoothly at home on woody on a GeForce 2 MX machine with the NVidia > drivers. > > I'm getting a work machine now with a GeForce 2 GTS 64MB and am obviously > putting debian on it, but I'd really prefer running potato with the 4.0.1 > phase 2 debs, seeing that the work machine is supposed to be a stablish > work station. I've tried building the 4.0.1 phase 2 debs from source on > potato before, but there are some built in dependencies (for instance on > later versions of glibc) which indicate that this is not such a wonderful > idea. > > Does anyone have any other experience with this, or other recommendations > perhaps? What is the general feeling about potato + 4.0.1? > > Any information would be greatly appreciated! > > Regards, > Charl > > -- > charl p. botha > delft university of technology > faculty of information technology and systems > computer graphics and cad/cam group > zuidplantsoen 4, room 2.339, 2628 bz delft, the netherlands > tel: +31 15 278 4698 fax: +31 15 278 7141 > mailto:[EMAIL PROTECTED] http://cpbotha.net/ > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > >
Xfree86 4.0.1-phase2v17 debs available for SPARC/UltraSPARC
I've finally got these compiled for Sparc. I haven't sent my patches to
Branden yet, but will soon. This is in the middle of uploading. Check the
.changes to make sure everything is there that you need. Yes, I built the
_all.deb packages too, but that's just to avoid version mismatches with
branden's stuff until I can get the patches to him, so he can put that
ultrasparc to use and start doing builds himself :)
A few caveats:
* The ATI (Mach64) driver does not work. It wont crash your machine, but
it wont properly detect your card either, so it just wont work.
* The fbdev driver also does not work
The SBUS drivers seem to work. I am running an Ultra30 dual head with a
Creator 3D and an ELite 3D card installed. Works perfectly. When you setup
your mouse, either use /dev/gpmdata (if you use gpm), or use
/dev/sunmouse. No longer are SBUS cards held down by the obsolete Xsun
servers and using the event driven proprietary mouse protocol. We now use
XF86Config just like everyone else, with full integration! DRI appears to
be working with the sunffb (Creator/Elite driver), if you have compiled
DRI support for it under a recent 2.4.0test kernel (I'm using test9 from
vger CVS). Quake-GL doesn't look right using glx though (lots of red), but
I'm not a GLX expert.
As for the keyboard. It sets up to use type5, edit /etc/X11/XF86Config-4 if
you need a type# different than that, or a ps/2 (pc104) keyboard.
A few warnings before I give out the URL:
1) DO NOT send bug reports directly to me or Branden (the Debian X
maintainer). If you are lucky, it will simply get forwarded to a list.
If you catch one of us on a bad day... To put it simply, most questions
are in Branden's FAQ, or can be answered by ppl on the list who aren't
as busy.
2) If you have SPARC specific questions, email to debian-sparc (or atleast
Cc to it, and email debian-x, which I prefer). Not all sparc folks are
on debian-x, so you might get some useless i386-centric reply if you
don't follow this warning.
3) DO NOT email the debian-sparc list about X-only related questions ("why
does my program not compile against XF4?")
4) The dexter script (X setup) with these deb's is modified slightly from
Branden's so it would list sunmouse and the Sun video driver modules.
Do not email Branden if this is broken. Just chalk it up to bad
luck/coding on my part, and try to fix things by hand. This is very
beta packaging (which is why it isn't in woody).
Now that you have read the warnings and caveats, you can scroll way down
and get the URL. No this is not an apt'able setup. Figure out the dep's
and stuff by hand, make good use of dpkg --force-depends to remove old
packages so these can be installed, etc...(don't blame me. if this scares
you, then don't use the packages, or setup an apt thingie of your own).
Most importantly, if you screw up your system because you didn't know what
you were doing, don't blame me :)
Please let me know of success/failures concerning tgx/leo/cg3/cg6/cg14/bw2
drivers.
http://auric.debian.org/~bcollins/xfree86-4/
--
---===-=-==-=---==-=--
/ Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \
` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] '
`---=--===-=-=-=-===-==---=--=---'
re: XtMakeGeometry errors resolved [UPDATE]
> On Sat, Oct 14, 2000 at 05:53:29PM -0500, Derek J Witt wrote: > > Hi, all. I figured out a way to resolve the "parent not composite" errors > > I've been getting from the xaw packages. I tried running apt-get to > > install X from the phase2 debbies. Of course, I started getting the > > error. > I talked to Keith Packard about this at ALS. > He says this is definitely a specification violation. It may be that > Athena can be recoded to fix it, however, as I understand it, since most > programs don't subclass the Athena widgets. and unfortunately not only anthena programms suffer, ie. netscape breaks too (try dragging a link from one netscape window to another, normaly the link would be opend in the new window but now netscape just quits.. - it doesn´t show the message, but a strace shows that it tried to display the error message) i guess the most programms which trigger XtMakeGeometry errors like gv, etc could fixed (easyly or not..) but for netscape i wouldn't hold breath :( -- Jens Hoffmann -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
debian large fonts anti-aliasing
OS: Debian Gnu/Linux 2.2 Aplication: xfs (XFree86) 3.3.6-11 Problem: In redhat with the same XFree version (3.3.6) it can display nice large fonts. Now using debian that fonts show broken, a think that is missing anti-aliasing, but i dont know. When i point my debian X to use a redhat xfs running at another computer all works fine. So i try install redhat xfs using alien to convert package, but the result is yet broken fonts. Im very confuse, and didnt find any reference to this kind of throuble. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: gv doesn't work with X4
On Mon, 16 Oct 2000, Wichert Akkerman wrote: > If I try to open a menu with gv it aborts with the following > error: > > Error: XtMakeGeometryRequest - parent not composite > > This might be an X problem, I've never seen it on any other version > of X. This has been mentioned on this list along with a workaround: http://lists.debian.org/debian-x-0010/msg00152.html has the answer. Keep well, Charl -- charl p. botha delft university of technology faculty of information technology and systems computer graphics and cad/cam group zuidplantsoen 4, room 2.339, 2628 bz delft, the netherlands tel: +31 15 278 4698 fax: +31 15 278 7141 mailto:[EMAIL PROTECTED] http://cpbotha.net/
gv doesn't work with X4
If I try to open a menu with gv it aborts with the following error: Error: XtMakeGeometryRequest - parent not composite This might be an X problem, I've never seen it on any other version of X. Wichert. -- _ / Nothing is fool-proof to a sufficiently talented fool \ | [EMAIL PROTECTED] http://www.liacs.nl/~wichert/ | | 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D |
Re: dexter and devfs
On Mon, Oct 16, 2000 at 01:38:03AM -0500, Branden Robinson wrote: > If someone gives me some (POSIX) shell scriptage, invoking no commands > that aren't in essential packages, which will decisively determine whether > or not a system is using devfs, I will add support for devfs filenames in > the mouse configuration section. if [ -c /dev/.devfsd ]; then echo "/dev is using devfs" fi is sufficient if you just want to check whether /dev is. -- Matthew Garrett | [EMAIL PROTECTED]
Re: libX11 is borked (or is it glibc ?)
On Mon, Oct 16, 2000 at 01:10:03AM -0400, James Antill wrote: > Daniel Jacobowitz <[EMAIL PROTECTED]> writes: > > > On Mon, Oct 16, 2000 at 01:59:11AM +0200, Johannes Zellner wrote: > > > Hello, > > > > > > I cannot link any more against libX11.so: > > > > > > /usr/X11R6/lib/libX11.so: undefined reference to `getpwnam_r@@GLIBC_2.0' > > > > > > this shows, even if I link a minimal c program. > > > > > > my versions: > > > ii xlib6g 3.3.6-11 > > > ii libc6 2.1.94-3 > > > > > > Any comments ? > > > > To compile against a library built under an old glibc, the library > > needs to be recompiled to the new libc. > > If this is true then there isn't any binary compatibility. > The whole point of the symbols looking like the above is so that > there can be multiple versions of them. Eg. Binary compatibility means you con run programs linked against older libraries. Guess what, X and the libX11 linked apps still work don't they? > % nm -g /usr/lib/debug/libc-2.1.3.so | egrep GLIB | egrep chown > 000913c8 T __chown@@GLIBC_2.1 > 000913c8 T chown@@GLIBC_2.1 > 00091454 T [EMAIL PROTECTED] > % nm -g /usr/lib/debug/libc-2.1.3.so | egrep GLIB | egrep fopen > 0004b5c4 T _IO_file_fopen@@GLIBC_2.1 > 0004da48 T [EMAIL PROTECTED] > 000481e0 T _IO_fopen@@GLIBC_2.1 > 0004a9a0 T [EMAIL PROTECTED] > 000481e0 T fopen@@GLIBC_2.1 > 0004a9a0 T [EMAIL PROTECTED] > > So either something bad has happened with the glibc versioning > upstream or glibc was built badly. No, this is inherent in versioned symbols. The old symbol is now "weak", which means it is there for using by old programs, but cannot be used when linking. A weak symbol keeps compatibility, which allowing the new strong symbol to be used for newly compiled applications. > > I think there's already a > > forthcoming X 3.3.6 upgrade which will be rebuilt against woody glibc - > > right, Branden? > > If it's woody, then it's probably an upstream problem but X 3.3.6 > _should not_ be upgraded (well not to fix this anyway, obviously there > may be other reasons to upgrade). Yes it should, just to fix this. Versioned symbols and their solution for binary compatibility, ensured that everything will still run as it did before. It does not mean that things wont have to be rebuilt to allow linking. -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---'
Re: dexter and devfs
On Mon, Oct 16, 2000 at 02:41:00AM -0500, Derek J Witt wrote: > I also found this to work as well: > > === > > #!/bin/sh > DEVFS=`grep devfs /proc/filesystems | cut -f2` > > [ $DEVFS = "devfs" ] && echo "You're using devfs. :-)" Needs to be more complex: #!/bin/sh # They may have more than one mounted, but always use the first DEVFS=$(egrep ' devfs ' /proc/mounts | head -1 | cut -f2) # No, devfsd does not have to be running for this to work. The file exists # for devfsd's usage, and is the same test that devfsd uses to make sure # it is operating on a devfs mount (did I say devfs enough?). if [ "$DEVFS" != "" ] && [ -f "$DEVFS/.devfsd" ]; then # we have devfs mounted, use it fi # ---end--- This makes sure they have it, and it is mounted. Note, if they have devfsd actually running, then they should be able to use the old devices, but that isn't guaranteed. Good thing about devfs, if the device exists, that driver is installed and working. So things like this are then possible: [ -f "$DEVFS/misc/sunmouse" ] && ... # add sunmouse as an option [ -f "$DEVFS/misc/psaux ] && ... # add the ps/2 options Also, if only one option is present then you can either use it blindly, or be nice enough to ask the user about it or an "other" entry. Branden, let me take this time to point out that sunmouse means either "BusMouse" or "PS/2" (I'm adding a patch so we can actually say "SunMouse" or "Sun", but it all points to BusMouse, just like in 3.3.6). PS/2 is just like the one on your Ultra. BTW, did you get the ati driver working? :) Ben -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---'
Error during start X with i810 VGA card. :(
Currently, I update X to 4.0.1 phase2, maybe correct?, in woody. I'm using Compaq Deskpro with VGA card using i810 chipset. With XF86 3.3.6, I have no problem using X with this machine, but after updating I got the error during startx. /var/log/XFree86.0.log file is following... XFree86 Version 4.0.1c / X Window System (protocol Version 11, revision 0, vendor release 6400) Release Date: 28 August 2000 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (see http://www.XFree86.Org/FAQ) Operating System: Linux 2.2.17pre10 i686 [ELF] Module Loader present (==) Log file: "/var/log/XFree86.0.log", Time: Mon Oct 16 21:48:03 2000 (==) Using config file: "/etc/X11/XF86Config-4" Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (??) unknown. (==) ServerLayout "Default Layout" (**) |-->Screen "Default Screen" (0) (**) | |-->Monitor "Generic Monitor" (**) | |-->Device "Generic Graphics Device" (**) |-->Input Device "Generic Keyboard" (**) Option "XkbRules" "xfree86" (**) XKB: rules: "xfree86" (**) Option "XkbModel" "pc104" (**) XKB: model: "pc104" (**) Option "XkbLayout" "us" (**) XKB: layout: "us" (**) |-->Input Device "Generic Mouse" (**) FontPath set to "/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/100dpi:unscaled,/usr/lib/X11/fonts/75dpi:unscaled,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/sun" (==) RgbPath set to "/usr/X11R6/lib/X11/rgb" (==) ModulePath set to "/usr/X11R6/lib/modules" (--) using VT number 7 (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.3 XFree86 XInput driver : 0.1 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.1 (II) Loader running on linux (II) LoadModule: "bitmap" (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor="The XFree86 Project" compiled for 4.0.1c, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.1 (II) Loading font Bitmap (II) LoadModule: "pcidata" (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor="The XFree86 Project" compiled for 4.0.1c, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.3 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,7124 card , rev 03 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,7125 card 0e11,b191 rev 03 class 03,00,00 hdr 00 (II) PCI: 00:1e:0: chip 8086,2418 card , rev 02 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,2410 card , rev 02 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,2411 card 8086,2411 rev 02 class 01,01,80 hdr 00 (II) PCI: 00:1f:2: chip 8086,2412 card 8086,2412 rev 02 class 0c,03,00 hdr 00 (II) PCI: 00:1f:5: chip 8086,2415 card 0e11,b189 rev 02 class 04,01,00 hdr 00 (II) PCI: 01:09:0: chip 8086,1229 card 8086,0009 rev 05 class 02,00,00 hdr 00 (II) PCI: End of PCI scan (II) LoadModule: "scanpci" (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor="The XFree86 Project" compiled for 4.0.1c, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.3 (II) UnloadModule: "scanpci" (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (II) Host-to-PCI bridge: (II) Bus -1: bridge is at (0:0:0), (-1,-1,0), BCTRL: 0x00 (VGA_EN is cleared) (II) Bus -1 I/O range: [0] -1 0x - 0x (0x1) IX[B] (II) Bus -1 non-prefetchable memory range: [0] -1 0x - 0x (0x0) MX[B] (II) Bus -1 prefetchable memory range: [0] -1 0x - 0x (0x0) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:31:0), (0,-1,0), BCTRL: 0x00 (VGA_EN is cleared) (II) Bus -1 I/O range: (II) Bus -1 non-prefetchable memory range: (II) Bus -1 prefetchable memory range: (II) PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:30:0), (0,1,1), BCTRL: 0x06 (VGA_EN is cleared) (II) Bus 1 I/O range: [0] -1 0x1000 - 0x10ff (0x100) IX[B] [1] -1 0x1400 - 0x14ff (0x100) IX[B] [2] -1 0x1800 - 0x18ff (0x100) IX[B] [3] -1 0x1c00 - 0x1cff (0x100) IX[B] (II) Bus 1 non-prefetchable memory range: [0] -1 0x4000 - 0x402f (0x30) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0x4040 - 0x404f (0x10) MX[B] (--) PCI:*(0:1:0) Intel i810e rev 3, Mem @ 0x4400/26, 0x4030/19 (II) Addressable bus resource ranges are [0] -1 0x - 0x (0x0) MX[B] [1] -1
Re: libX11 is borked (or is it glibc ?)
On Mon, Oct 16, 2000 at 01:10:03AM -0400, James Antill wrote: > Daniel Jacobowitz <[EMAIL PROTECTED]> writes: > > > On Mon, Oct 16, 2000 at 01:59:11AM +0200, Johannes Zellner wrote: > > > Hello, > > > > > > I cannot link any more against libX11.so: > > > > > > /usr/X11R6/lib/libX11.so: undefined reference to `getpwnam_r@@GLIBC_2.0' > > > > > > this shows, even if I link a minimal c program. > > > > > > my versions: > > > ii xlib6g 3.3.6-11 > > > ii libc6 2.1.94-3 > > > > > > Any comments ? > > > > To compile against a library built under an old glibc, the library > > needs to be recompiled to the new libc. > > If this is true then there isn't any binary compatibility. > The whole point of the symbols looking like the above is so that > there can be multiple versions of them. Eg. > > % nm -g /usr/lib/debug/libc-2.1.3.so | egrep GLIB | egrep chown > 000913c8 T __chown@@GLIBC_2.1 > 000913c8 T chown@@GLIBC_2.1 > 00091454 T [EMAIL PROTECTED] > % nm -g /usr/lib/debug/libc-2.1.3.so | egrep GLIB | egrep fopen > 0004b5c4 T _IO_file_fopen@@GLIBC_2.1 > 0004da48 T [EMAIL PROTECTED] > 000481e0 T _IO_fopen@@GLIBC_2.1 > 0004a9a0 T [EMAIL PROTECTED] > 000481e0 T fopen@@GLIBC_2.1 > 0004a9a0 T [EMAIL PROTECTED] > > So either something bad has happened with the glibc versioning > upstream or glibc was built badly. No, you misunderstand symbol versioning. There is -runtime- compatiblity - the old [EMAIL PROTECTED] is still there. However, there is no compile-time compatibility - a library referencing that [EMAIL PROTECTED] can no longer be linked to. This is, I believe, deliberate. Libraries must be recompiled to be linked to. Dan /\ /\ | Daniel Jacobowitz|__|SCS Class of 2002 | | Debian GNU/Linux Developer__Carnegie Mellon University | | [EMAIL PROTECTED] | | [EMAIL PROTECTED] | \/ \/
4.0.1 debs and potato
Dear debian-xers, Thanks to Branden's debs I have the phase2 4.0.1 v15 debs running very smoothly at home on woody on a GeForce 2 MX machine with the NVidia drivers. I'm getting a work machine now with a GeForce 2 GTS 64MB and am obviously putting debian on it, but I'd really prefer running potato with the 4.0.1 phase 2 debs, seeing that the work machine is supposed to be a stablish work station. I've tried building the 4.0.1 phase 2 debs from source on potato before, but there are some built in dependencies (for instance on later versions of glibc) which indicate that this is not such a wonderful idea. Does anyone have any other experience with this, or other recommendations perhaps? What is the general feeling about potato + 4.0.1? Any information would be greatly appreciated! Regards, Charl -- charl p. botha delft university of technology faculty of information technology and systems computer graphics and cad/cam group zuidplantsoen 4, room 2.339, 2628 bz delft, the netherlands tel: +31 15 278 4698 fax: +31 15 278 7141 mailto:[EMAIL PROTECTED] http://cpbotha.net/
Re: 4.0.1 debs and potato
Well before X4 debs existed at all, I had a method (put together specifically for getting nVidia cards working with debian) for instaling X4 from source so that it sits in a seperate tree, alongside your normal debian X3.3.6 install. I wrote a quick HOWTO (basically for members of my local LUG), which is at: http://games.luv.asn.au/lsd Thanks Leigh On Mon, 16 Oct 2000 14:35:14 +0200, Charl P. Botha said: > Dear debian-xers, > > Thanks to Branden's debs I have the phase2 4.0.1 v15 debs running very > smoothly at home on woody on a GeForce 2 MX machine with the NVidia > drivers. > > I'm getting a work machine now with a GeForce 2 GTS 64MB and am obviously > putting debian on it, but I'd really prefer running potato with the 4.0.1 > phase 2 debs, seeing that the work machine is supposed to be a stablish > work station. I've tried building the 4.0.1 phase 2 debs from source on > potato before, but there are some built in dependencies (for instance on > later versions of glibc) which indicate that this is not such a wonderful > idea. > > Does anyone have any other experience with this, or other recommendations > perhaps? What is the general feeling about potato + 4.0.1? > > Any information would be greatly appreciated! > > Regards, > Charl > > -- > charl p. botha > delft university of technology > faculty of information technology and systems > computer graphics and cad/cam group > zuidplantsoen 4, room 2.339, 2628 bz delft, the netherlands > tel: +31 15 278 4698 fax: +31 15 278 7141 > mailto:[EMAIL PROTECTED] http://cpbotha.net/ > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Xfree86 4.0.1-phase2v17 debs available for SPARC/UltraSPARC
I've finally got these compiled for Sparc. I haven't sent my patches to
Branden yet, but will soon. This is in the middle of uploading. Check the
.changes to make sure everything is there that you need. Yes, I built the
_all.deb packages too, but that's just to avoid version mismatches with
branden's stuff until I can get the patches to him, so he can put that
ultrasparc to use and start doing builds himself :)
A few caveats:
* The ATI (Mach64) driver does not work. It wont crash your machine, but
it wont properly detect your card either, so it just wont work.
* The fbdev driver also does not work
The SBUS drivers seem to work. I am running an Ultra30 dual head with a
Creator 3D and an ELite 3D card installed. Works perfectly. When you setup
your mouse, either use /dev/gpmdata (if you use gpm), or use
/dev/sunmouse. No longer are SBUS cards held down by the obsolete Xsun
servers and using the event driven proprietary mouse protocol. We now use
XF86Config just like everyone else, with full integration! DRI appears to
be working with the sunffb (Creator/Elite driver), if you have compiled
DRI support for it under a recent 2.4.0test kernel (I'm using test9 from
vger CVS). Quake-GL doesn't look right using glx though (lots of red), but
I'm not a GLX expert.
As for the keyboard. It sets up to use type5, edit /etc/X11/XF86Config-4 if
you need a type# different than that, or a ps/2 (pc104) keyboard.
A few warnings before I give out the URL:
1) DO NOT send bug reports directly to me or Branden (the Debian X
maintainer). If you are lucky, it will simply get forwarded to a list.
If you catch one of us on a bad day... To put it simply, most questions
are in Branden's FAQ, or can be answered by ppl on the list who aren't
as busy.
2) If you have SPARC specific questions, email to debian-sparc (or atleast
Cc to it, and email debian-x, which I prefer). Not all sparc folks are
on debian-x, so you might get some useless i386-centric reply if you
don't follow this warning.
3) DO NOT email the debian-sparc list about X-only related questions ("why
does my program not compile against XF4?")
4) The dexter script (X setup) with these deb's is modified slightly from
Branden's so it would list sunmouse and the Sun video driver modules.
Do not email Branden if this is broken. Just chalk it up to bad
luck/coding on my part, and try to fix things by hand. This is very
beta packaging (which is why it isn't in woody).
Now that you have read the warnings and caveats, you can scroll way down
and get the URL. No this is not an apt'able setup. Figure out the dep's
and stuff by hand, make good use of dpkg --force-depends to remove old
packages so these can be installed, etc...(don't blame me. if this scares
you, then don't use the packages, or setup an apt thingie of your own).
Most importantly, if you screw up your system because you didn't know what
you were doing, don't blame me :)
Please let me know of success/failures concerning tgx/leo/cg3/cg6/cg14/bw2
drivers.
http://auric.debian.org/~bcollins/xfree86-4/
--
---===-=-==-=---==-=--
/ Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \
` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] '
`---=--===-=-=-=-===-==---=--=---'
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: gv doesn't work with X4
On Mon, 16 Oct 2000, Wichert Akkerman wrote: > If I try to open a menu with gv it aborts with the following > error: > > Error: XtMakeGeometryRequest - parent not composite > > This might be an X problem, I've never seen it on any other version > of X. This has been mentioned on this list along with a workaround: http://lists.debian.org/debian-x-0010/msg00152.html has the answer. Keep well, Charl -- charl p. botha delft university of technology faculty of information technology and systems computer graphics and cad/cam group zuidplantsoen 4, room 2.339, 2628 bz delft, the netherlands tel: +31 15 278 4698 fax: +31 15 278 7141 mailto:[EMAIL PROTECTED] http://cpbotha.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
gv doesn't work with X4
If I try to open a menu with gv it aborts with the following error: Error: XtMakeGeometryRequest - parent not composite This might be an X problem, I've never seen it on any other version of X. Wichert. -- _ / Nothing is fool-proof to a sufficiently talented fool \ | [EMAIL PROTECTED] http://www.liacs.nl/~wichert/ | | 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dexter and devfs
On Mon, Oct 16, 2000 at 01:38:03AM -0500, Branden Robinson wrote: > If someone gives me some (POSIX) shell scriptage, invoking no commands > that aren't in essential packages, which will decisively determine whether > or not a system is using devfs, I will add support for devfs filenames in > the mouse configuration section. if [ -c /dev/.devfsd ]; then echo "/dev is using devfs" fi is sufficient if you just want to check whether /dev is. -- Matthew Garrett | [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: libX11 is borked (or is it glibc ?)
On Mon, Oct 16, 2000 at 01:10:03AM -0400, James Antill wrote: > Daniel Jacobowitz <[EMAIL PROTECTED]> writes: > > > On Mon, Oct 16, 2000 at 01:59:11AM +0200, Johannes Zellner wrote: > > > Hello, > > > > > > I cannot link any more against libX11.so: > > > > > > /usr/X11R6/lib/libX11.so: undefined reference to `getpwnam_r@@GLIBC_2.0' > > > > > > this shows, even if I link a minimal c program. > > > > > > my versions: > > > ii xlib6g 3.3.6-11 > > > ii libc6 2.1.94-3 > > > > > > Any comments ? > > > > To compile against a library built under an old glibc, the library > > needs to be recompiled to the new libc. > > If this is true then there isn't any binary compatibility. > The whole point of the symbols looking like the above is so that > there can be multiple versions of them. Eg. Binary compatibility means you con run programs linked against older libraries. Guess what, X and the libX11 linked apps still work don't they? > % nm -g /usr/lib/debug/libc-2.1.3.so | egrep GLIB | egrep chown > 000913c8 T __chown@@GLIBC_2.1 > 000913c8 T chown@@GLIBC_2.1 > 00091454 T [EMAIL PROTECTED] > % nm -g /usr/lib/debug/libc-2.1.3.so | egrep GLIB | egrep fopen > 0004b5c4 T _IO_file_fopen@@GLIBC_2.1 > 0004da48 T [EMAIL PROTECTED] > 000481e0 T _IO_fopen@@GLIBC_2.1 > 0004a9a0 T [EMAIL PROTECTED] > 000481e0 T fopen@@GLIBC_2.1 > 0004a9a0 T [EMAIL PROTECTED] > > So either something bad has happened with the glibc versioning > upstream or glibc was built badly. No, this is inherent in versioned symbols. The old symbol is now "weak", which means it is there for using by old programs, but cannot be used when linking. A weak symbol keeps compatibility, which allowing the new strong symbol to be used for newly compiled applications. > > I think there's already a > > forthcoming X 3.3.6 upgrade which will be rebuilt against woody glibc - > > right, Branden? > > If it's woody, then it's probably an upstream problem but X 3.3.6 > _should not_ be upgraded (well not to fix this anyway, obviously there > may be other reasons to upgrade). Yes it should, just to fix this. Versioned symbols and their solution for binary compatibility, ensured that everything will still run as it did before. It does not mean that things wont have to be rebuilt to allow linking. -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dexter and devfs
On Mon, Oct 16, 2000 at 02:41:00AM -0500, Derek J Witt wrote: > I also found this to work as well: > > === > > #!/bin/sh > DEVFS=`grep devfs /proc/filesystems | cut -f2` > > [ $DEVFS = "devfs" ] && echo "You're using devfs. :-)" Needs to be more complex: #!/bin/sh # They may have more than one mounted, but always use the first DEVFS=$(egrep ' devfs ' /proc/mounts | head -1 | cut -f2) # No, devfsd does not have to be running for this to work. The file exists # for devfsd's usage, and is the same test that devfsd uses to make sure # it is operating on a devfs mount (did I say devfs enough?). if [ "$DEVFS" != "" ] && [ -f "$DEVFS/.devfsd" ]; then # we have devfs mounted, use it fi # ---end--- This makes sure they have it, and it is mounted. Note, if they have devfsd actually running, then they should be able to use the old devices, but that isn't guaranteed. Good thing about devfs, if the device exists, that driver is installed and working. So things like this are then possible: [ -f "$DEVFS/misc/sunmouse" ] && ... # add sunmouse as an option [ -f "$DEVFS/misc/psaux ] && ... # add the ps/2 options Also, if only one option is present then you can either use it blindly, or be nice enough to ask the user about it or an "other" entry. Branden, let me take this time to point out that sunmouse means either "BusMouse" or "PS/2" (I'm adding a patch so we can actually say "SunMouse" or "Sun", but it all points to BusMouse, just like in 3.3.6). PS/2 is just like the one on your Ultra. BTW, did you get the ati driver working? :) Ben -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Error during start X with i810 VGA card. :(
Currently, I update X to 4.0.1 phase2, maybe correct?, in woody. I'm using Compaq Deskpro with VGA card using i810 chipset. With XF86 3.3.6, I have no problem using X with this machine, but after updating I got the error during startx. /var/log/XFree86.0.log file is following... XFree86 Version 4.0.1c / X Window System (protocol Version 11, revision 0, vendor release 6400) Release Date: 28 August 2000 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (see http://www.XFree86.Org/FAQ) Operating System: Linux 2.2.17pre10 i686 [ELF] Module Loader present (==) Log file: "/var/log/XFree86.0.log", Time: Mon Oct 16 21:48:03 2000 (==) Using config file: "/etc/X11/XF86Config-4" Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (??) unknown. (==) ServerLayout "Default Layout" (**) |-->Screen "Default Screen" (0) (**) | |-->Monitor "Generic Monitor" (**) | |-->Device "Generic Graphics Device" (**) |-->Input Device "Generic Keyboard" (**) Option "XkbRules" "xfree86" (**) XKB: rules: "xfree86" (**) Option "XkbModel" "pc104" (**) XKB: model: "pc104" (**) Option "XkbLayout" "us" (**) XKB: layout: "us" (**) |-->Input Device "Generic Mouse" (**) FontPath set to "/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/100dpi:unscaled,/usr/lib/X11/fonts/75dpi:unscaled,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/sun" (==) RgbPath set to "/usr/X11R6/lib/X11/rgb" (==) ModulePath set to "/usr/X11R6/lib/modules" (--) using VT number 7 (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.3 XFree86 XInput driver : 0.1 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.1 (II) Loader running on linux (II) LoadModule: "bitmap" (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor="The XFree86 Project" compiled for 4.0.1c, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.1 (II) Loading font Bitmap (II) LoadModule: "pcidata" (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor="The XFree86 Project" compiled for 4.0.1c, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.3 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,7124 card , rev 03 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,7125 card 0e11,b191 rev 03 class 03,00,00 hdr 00 (II) PCI: 00:1e:0: chip 8086,2418 card , rev 02 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,2410 card , rev 02 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,2411 card 8086,2411 rev 02 class 01,01,80 hdr 00 (II) PCI: 00:1f:2: chip 8086,2412 card 8086,2412 rev 02 class 0c,03,00 hdr 00 (II) PCI: 00:1f:5: chip 8086,2415 card 0e11,b189 rev 02 class 04,01,00 hdr 00 (II) PCI: 01:09:0: chip 8086,1229 card 8086,0009 rev 05 class 02,00,00 hdr 00 (II) PCI: End of PCI scan (II) LoadModule: "scanpci" (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor="The XFree86 Project" compiled for 4.0.1c, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.3 (II) UnloadModule: "scanpci" (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (II) Host-to-PCI bridge: (II) Bus -1: bridge is at (0:0:0), (-1,-1,0), BCTRL: 0x00 (VGA_EN is cleared) (II) Bus -1 I/O range: [0] -1 0x - 0x (0x1) IX[B] (II) Bus -1 non-prefetchable memory range: [0] -1 0x - 0x (0x0) MX[B] (II) Bus -1 prefetchable memory range: [0] -1 0x - 0x (0x0) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:31:0), (0,-1,0), BCTRL: 0x00 (VGA_EN is cleared) (II) Bus -1 I/O range: (II) Bus -1 non-prefetchable memory range: (II) Bus -1 prefetchable memory range: (II) PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:30:0), (0,1,1), BCTRL: 0x06 (VGA_EN is cleared) (II) Bus 1 I/O range: [0] -1 0x1000 - 0x10ff (0x100) IX[B] [1] -1 0x1400 - 0x14ff (0x100) IX[B] [2] -1 0x1800 - 0x18ff (0x100) IX[B] [3] -1 0x1c00 - 0x1cff (0x100) IX[B] (II) Bus 1 non-prefetchable memory range: [0] -1 0x4000 - 0x402f (0x30) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0x4040 - 0x404f (0x10) MX[B] (--) PCI:*(0:1:0) Intel i810e rev 3, Mem @ 0x4400/26, 0x4030/19 (II) Addressable bus resource ranges are [0] -1 0x - 0x (0x0) MX[B] [1] -1
Re: libX11 is borked (or is it glibc ?)
On Mon, Oct 16, 2000 at 01:10:03AM -0400, James Antill wrote: > Daniel Jacobowitz <[EMAIL PROTECTED]> writes: > > > On Mon, Oct 16, 2000 at 01:59:11AM +0200, Johannes Zellner wrote: > > > Hello, > > > > > > I cannot link any more against libX11.so: > > > > > > /usr/X11R6/lib/libX11.so: undefined reference to `getpwnam_r@@GLIBC_2.0' > > > > > > this shows, even if I link a minimal c program. > > > > > > my versions: > > > ii xlib6g 3.3.6-11 > > > ii libc6 2.1.94-3 > > > > > > Any comments ? > > > > To compile against a library built under an old glibc, the library > > needs to be recompiled to the new libc. > > If this is true then there isn't any binary compatibility. > The whole point of the symbols looking like the above is so that > there can be multiple versions of them. Eg. > > % nm -g /usr/lib/debug/libc-2.1.3.so | egrep GLIB | egrep chown > 000913c8 T __chown@@GLIBC_2.1 > 000913c8 T chown@@GLIBC_2.1 > 00091454 T [EMAIL PROTECTED] > % nm -g /usr/lib/debug/libc-2.1.3.so | egrep GLIB | egrep fopen > 0004b5c4 T _IO_file_fopen@@GLIBC_2.1 > 0004da48 T [EMAIL PROTECTED] > 000481e0 T _IO_fopen@@GLIBC_2.1 > 0004a9a0 T [EMAIL PROTECTED] > 000481e0 T fopen@@GLIBC_2.1 > 0004a9a0 T [EMAIL PROTECTED] > > So either something bad has happened with the glibc versioning > upstream or glibc was built badly. No, you misunderstand symbol versioning. There is -runtime- compatiblity - the old [EMAIL PROTECTED] is still there. However, there is no compile-time compatibility - a library referencing that [EMAIL PROTECTED] can no longer be linked to. This is, I believe, deliberate. Libraries must be recompiled to be linked to. Dan /\ /\ | Daniel Jacobowitz|__|SCS Class of 2002 | | Debian GNU/Linux Developer__Carnegie Mellon University | | [EMAIL PROTECTED] | | [EMAIL PROTECTED] | \/ \/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
4.0.1 debs and potato
Dear debian-xers, Thanks to Branden's debs I have the phase2 4.0.1 v15 debs running very smoothly at home on woody on a GeForce 2 MX machine with the NVidia drivers. I'm getting a work machine now with a GeForce 2 GTS 64MB and am obviously putting debian on it, but I'd really prefer running potato with the 4.0.1 phase 2 debs, seeing that the work machine is supposed to be a stablish work station. I've tried building the 4.0.1 phase 2 debs from source on potato before, but there are some built in dependencies (for instance on later versions of glibc) which indicate that this is not such a wonderful idea. Does anyone have any other experience with this, or other recommendations perhaps? What is the general feeling about potato + 4.0.1? Any information would be greatly appreciated! Regards, Charl -- charl p. botha delft university of technology faculty of information technology and systems computer graphics and cad/cam group zuidplantsoen 4, room 2.339, 2628 bz delft, the netherlands tel: +31 15 278 4698 fax: +31 15 278 7141 mailto:[EMAIL PROTECTED] http://cpbotha.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dexter and devfs
I also found this to work as well: === #!/bin/sh DEVFS=`grep devfs /proc/filesystems | cut -f2` [ $DEVFS = "devfs" ] && echo "You're using devfs. :-)" === Looks like it's going to be a simple thing to test anyway we do it. :-) ** Derek J Witt ** * Email: mailto:[EMAIL PROTECTED] * * Home Page: http://www.flinthills.com/~djw/ * *** "...and on the eighth day, God met Bill Gates." - Unknown **
Re: libX11 is borked (or is it glibc ?)
On Sun, Oct 15, 2000 at 09:02:42PM -0400, Daniel Jacobowitz wrote: > To compile against a library built under an old glibc, the library > needs to be recompiled to the new libc. I think there's already a > forthcoming X 3.3.6 upgrade which will be rebuilt against woody glibc - > right, Branden? Not exactly. When the 4.x packages are done, here's what will happen to 3.x, as can be previewed on samosa: 1) some 3.x servers will be built for alpha and i386 2) libc5-compatible X libraries will be built for i386 It is true however that the problem described will go away. -- G. Branden Robinson | Debian GNU/Linux| Never attribute to malice that which can [EMAIL PROTECTED] | be adequately explained by stupidity. http://www.debian.org/~branden/ | pgpCoygigScUY.pgp Description: PGP signature
Re: dexter and devfs
On Mon, Oct 16, 2000 at 01:38:03AM -0500, Branden Robinson wrote: > If someone gives me some (POSIX) shell scriptage, invoking no commands > that aren't in essential packages, which will decisively determine whether > or not a system is using devfs, I will add support for devfs filenames in > the mouse configuration section. You mean something like 'grep devfs /proc/mounts 2>&1 > /dev/null && echo Yes'? Zephaniah E. Hull. > > -- > G. Branden Robinson | To stay young requires unceasing > Debian GNU/Linux| cultivation of the ability to unlearn > [EMAIL PROTECTED] | old falsehoods. > http://www.debian.org/~branden/ | -- Robert Heinlein -- PGP EA5198D1-Zephaniah E. Hull <[EMAIL PROTECTED]>-GPG E65A7801 Keys available at http://whitestar.soark.net/~warp/public_keys. CCs of replies from mailing lists are encouraged. Welcome to [telco] hell. [...] You are in a maze of twisty little PVC's, all alike. A switching engineer throws a dart at you! -- Chris Saunderson <[EMAIL PROTECTED]> in the scary.devil.monastery pgpkNA68w7T6M.pgp Description: PGP signature
XtMakeGeometry errors resolved [UPDATE]
On Sat, Oct 14, 2000 at 05:53:29PM -0500, Derek J Witt wrote: > Hi, all. I figured out a way to resolve the "parent not composite" errors > I've been getting from the xaw packages. I tried running apt-get to > install X from the phase2 debbies. Of course, I started getting the > error. I talked to Keith Packard about this at ALS. He says this is definitely a specification violation. It may be that Athena can be recoded to fix it, however, as I understand it, since most programs don't subclass the Athena widgets. -- G. Branden Robinson | A great work of art has never caused any Debian GNU/Linux| social problems. Social problems are [EMAIL PROTECTED] | caused by those trying to protect http://www.debian.org/~branden/ | society from great works of art. pgpMyTYeMMOHn.pgp Description: PGP signature
Re: config file problems?
On Sat, Oct 14, 2000 at 02:00:15PM -0700, Seth Arnold wrote: > I just apt-get upgraded my system, and watched these messages roll past. > Has anyone else seen them, and if so, is this something that Branden > should know about or does know about? (Back to the `I don't support > upgrades between the testing versions'?) The latter, and I knew it would happen when I did it. These files don't exist in 3.x so there is no reason to declare a Replaces:. I'd been meaning to move xf86cfg out of there for a while but had forgotten. It depends on xlibs and I don't want the *server* package to depend on the X libraries. Kinda ruins the orthogonality of my packaging layout. -- G. Branden Robinson | "There is no gravity in space." Debian GNU/Linux| "Then how could astronauts walk around [EMAIL PROTECTED] |on the Moon?" http://www.debian.org/~branden/ | "Because they were wearing heavy boots." pgpzhaXebfAMc.pgp Description: PGP signature
Re: OpenGL & G400
On Sat, Oct 14, 2000 at 07:58:26PM +0200, Rafal Krzewski wrote: > Upgrades v13-v15 and v15-v17 also worked great, which means that either > I'm lucky or the phase2 packages are in better shape that it is widely > advertised :) Ssh! Quiet! -- G. Branden Robinson | Debian GNU/Linux|Please do not look directly into laser [EMAIL PROTECTED] |with remaining eye. http://www.debian.org/~branden/ | pgpzsldPZzqNi.pgp Description: PGP signature
Re: How do you want non-i386 handled in dexter? (+ mouse types)
On Sat, Oct 14, 2000 at 06:03:12PM -0400, Ben Collins wrote: > On Sat, Oct 14, 2000 at 02:23:49PM -0600, Joshua Shagam wrote: > > On Sat, Oct 14, 2000 at 09:03:20AM -0400, Ben Collins wrote: > > > Obviously the server list in dexter needs to be different on non-i386, > > > aswell as the generated keyboard lines (on sun there are two default > > > possibilies, i386 and type5). > > > > > > How do you forsee this happening? There isn't a clean way right now, > > > expect for outputting a complete list of servers for each arch (lots of > > > duplication). I don't think it can be handled cleanly in shell, so will > > > you change to perl (the var/string handling in shell loses in this case). > > > > Why not have dexter generate the list at runtime based on the files in > > /usr/X11R6/lib/modules/drivers? > > Sounds even better to me. Let me mull this over. Sounds good except that it's a little more complex because of the legacy 3.x servers supported on alpha and i386 (only, fortunately). -- G. Branden Robinson |Murphy's Guide to Science: Debian GNU/Linux|If it's green or squirms, it's biology. [EMAIL PROTECTED] |If it stinks, it's chemistry. http://www.debian.org/~branden/ |If it doesn't work, it's physics. pgp7kaaA3R7Cx.pgp Description: PGP signature
Re: Bug#74716: gnome-panel: several panel applets segfault under repeatable conditions
On Sat, Oct 14, 2000 at 11:51:34AM +0200, Christian Marillat wrote: > I like bug report like this one. Helix package and xlib6g 4.0 Yes, I like it too; cat /var/lib/dpkg/info/xlib6g.files with 4.0.1 installed shows me tons and tons of shared objects... -- G. Branden Robinson |Software engineering: that part of Debian GNU/Linux|computer science which is too difficult [EMAIL PROTECTED] |for the computer scientist. http://www.debian.org/~branden/ | pgpZAMHIQl2aW.pgp Description: PGP signature
XFree86 4.0.1 and libGLU status update
On Sat, Oct 14, 2000 at 02:38:16AM -0700, Seth Arnold wrote: > * Gordon Heydon <[EMAIL PROTECTED]> [001013 20:20]: > > but what about the libGLU and libGL libraries? don't you need those. At > > the moment I have the Utah ones is that enough. > > Well, yes, you do. XF86 4.0.1 currently provides libGL. Shortly they > will begin providing libGLU. (It is a technical issue -- it is the only > file in their distribution that uses C++.) Some news from ALS; I spoke to David Dawes about this. It will definitely happen. He has a patch from someone, he just needs to clear out his backlog, check it for problems, and commit it. Give him a little time, and me a little more. -- G. Branden Robinson | A celibate clergy is an especially good Debian GNU/Linux| idea, because it tends to suppress any [EMAIL PROTECTED] | hereditary propensity toward fanaticism. http://www.debian.org/~branden/ | -- Carl Sagan pgpynCHrT2BDQ.pgp Description: PGP signature
dexter and devfs
If someone gives me some (POSIX) shell scriptage, invoking no commands that aren't in essential packages, which will decisively determine whether or not a system is using devfs, I will add support for devfs filenames in the mouse configuration section. But not before; it's beyond my current knowledge since I have yet to play with USB or devfs myself. Remember, dexter needs to support those without devfs, too. I'm not going to break dexter to support only bleeding-edge devfs people. -- G. Branden Robinson | To stay young requires unceasing Debian GNU/Linux| cultivation of the ability to unlearn [EMAIL PROTECTED] | old falsehoods. http://www.debian.org/~branden/ | -- Robert Heinlein pgpt3S88f4tsR.pgp Description: PGP signature
Re: xserver-common phase2v15: dexter does not list /dev/gpmdata
On Thu, Oct 12, 2000 at 04:20:31AM -0700, [EMAIL PROTECTED] wrote:
> I hadn't extensively played with it either, since I have a rather custom
> config (dual head with fixed-frequency monitors). Though, it would be
> nice if dexter could accept more monitor information, perhaps even a full
> XFree86 modeline. Hopefully that kind of additional support could be
> added later on.
Barring overwhelming demand, I'm just not going to add this functionality.
Dexter's success is going to depend on constraining its focus, which is
getting the naive user without any X server configuration into X with a
minimal requirement of knowledge about his/her hardware and certainly
without any knowledge of the syntax of the XF86Config{-4} file.
Modelines are the deepest of magic. If you want to play with them, then
you belong in a text editor with the XF86Config{-4} file.
> At least it doesn't overwrite XF86Config. =)
Correct; the latest version will not overwrite without being told to do so.
--
G. Branden Robinson | If a man ate a pound of pasta and a
Debian GNU/Linux| pound of antipasto, would they cancel
[EMAIL PROTECTED] | out, leaving him still hungry?
http://www.debian.org/~branden/ | -- Scott Adams
pgpfgSHXVVMOs.pgp
Description: PGP signature
Re: xlibs 40.1-0phase2v13 break xawtv
On Wed, Oct 11, 2000 at 10:42:18PM -0500, Derek J Witt wrote: > Is xaw95g based on xaw3d or xaw6/7? AFAIK, xaw95g and xaw3d are distinct forks of Xaw6. Xaw7 did not yet exist at the time they were written, which was years ago. -- G. Branden Robinson |The greatest productive force is human Debian GNU/Linux|selfishness. [EMAIL PROTECTED] |-- Robert Heinlein http://www.debian.org/~branden/ | pgpBIUyS6czTO.pgp Description: PGP signature
Processed: not release critical
Processing commands for [EMAIL PROTECTED]: > severity 72041 normal Bug#72041: xfree86-1: [hurd]: Support for the Hurd Severity set to `normal'. > severity 72135 normal Bug#72135: xfree86-1: [hurd] Further porting Severity set to `normal'. > severity 70750 normal Bug#70750: xserver-svga: killing netscape crashes xserver on a millenium 2 Severity set to `normal'. > thanks Stopping processing here. Please contact me if you need assistance. Darren Benham (administrator, Debian Bugs database)
[johannes@zellner.org: xlib6g in debian]
He doesn't describe what he means by "latest"; I presume official. Does 3.3.6-11 (which was built against glibc 2.1.3) not work with 2.1.94? - Forwarded message from Johannes Zellner <[EMAIL PROTECTED]> - From: Johannes Zellner <[EMAIL PROTECTED]> To: Branden Robinson <[EMAIL PROTECTED]> Subject: xlib6g in debian Date: Sun, 15 Oct 2000 15:17:25 +0200 Delivered-To: [EMAIL PROTECTED] Message-ID: <[EMAIL PROTECTED]> User-Agent: Mutt/1.2.4i Hello Branden, there's a problem with the latest xlib6g: /usr/X11R6/lib/libX11.so: undefined reference to `getpwnam_r@@GLIBC_2.0' -- Johannes - End forwarded message - -- G. Branden Robinson|Measure with micrometer, Debian GNU/Linux |mark with chalk, [EMAIL PROTECTED] |cut with axe, http://deadbeast.net/~branden/ |hope like hell. pgpiS2EC0IjSc.pgp Description: PGP signature
[gaborliptak@usa.net: re. xserver-common 4.0.1]
- Forwarded message from Gábor Lipták <[EMAIL PROTECTED]> - From: "Gábor" "Lipták" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: re. xserver-common 4.0.1 Date: 13 Oct 00 22:32:55 EDT Delivered-To: [EMAIL PROTECTED] Message-ID: <[EMAIL PROTECTED]> X-Mailer: USANET web-mailer (34FM.0700.4.03) Would this above also replace xserver-3dlabs? As per: http://www.xfree86.org/4.0.1/RELNOTES3.html#19 a glint driver would also be included in the 4.0 package. Thanks Gábor Lipták Have you http://www.robofetch.com/ -ed today? Get free email and a permanent address at http://www.amexmail.com/?A=1 - End forwarded message - -- G. Branden Robinson|You don't just decide to break Kubrick's Debian GNU/Linux |code of silence and then get drawn away [EMAIL PROTECTED] |from it to a discussion about cough http://deadbeast.net/~branden/ |medicine. pgpjaBq9uXrk1.pgp Description: PGP signature
Re: dexter and devfs
I also found this to work as well: === #!/bin/sh DEVFS=`grep devfs /proc/filesystems | cut -f2` [ $DEVFS = "devfs" ] && echo "You're using devfs. :-)" === Looks like it's going to be a simple thing to test anyway we do it. :-) ** Derek J Witt ** * Email: mailto:[EMAIL PROTECTED] * * Home Page: http://www.flinthills.com/~djw/ * *** "...and on the eighth day, God met Bill Gates." - Unknown ** -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: libX11 is borked (or is it glibc ?)
On Sun, Oct 15, 2000 at 09:02:42PM -0400, Daniel Jacobowitz wrote: > To compile against a library built under an old glibc, the library > needs to be recompiled to the new libc. I think there's already a > forthcoming X 3.3.6 upgrade which will be rebuilt against woody glibc - > right, Branden? Not exactly. When the 4.x packages are done, here's what will happen to 3.x, as can be previewed on samosa: 1) some 3.x servers will be built for alpha and i386 2) libc5-compatible X libraries will be built for i386 It is true however that the problem described will go away. -- G. Branden Robinson | Debian GNU/Linux| Never attribute to malice that which can [EMAIL PROTECTED] | be adequately explained by stupidity. http://www.debian.org/~branden/ | PGP signature
Re: libX11 is borked (or is it glibc ?)
Daniel Jacobowitz <[EMAIL PROTECTED]> writes: > On Mon, Oct 16, 2000 at 01:59:11AM +0200, Johannes Zellner wrote: > > Hello, > > > > I cannot link any more against libX11.so: > > > > /usr/X11R6/lib/libX11.so: undefined reference to `getpwnam_r@@GLIBC_2.0' > > > > this shows, even if I link a minimal c program. > > > > my versions: > > ii xlib6g 3.3.6-11 > > ii libc6 2.1.94-3 > > > > Any comments ? > > To compile against a library built under an old glibc, the library > needs to be recompiled to the new libc. If this is true then there isn't any binary compatibility. The whole point of the symbols looking like the above is so that there can be multiple versions of them. Eg. % nm -g /usr/lib/debug/libc-2.1.3.so | egrep GLIB | egrep chown 000913c8 T __chown@@GLIBC_2.1 000913c8 T chown@@GLIBC_2.1 00091454 T [EMAIL PROTECTED] % nm -g /usr/lib/debug/libc-2.1.3.so | egrep GLIB | egrep fopen 0004b5c4 T _IO_file_fopen@@GLIBC_2.1 0004da48 T [EMAIL PROTECTED] 000481e0 T _IO_fopen@@GLIBC_2.1 0004a9a0 T [EMAIL PROTECTED] 000481e0 T fopen@@GLIBC_2.1 0004a9a0 T [EMAIL PROTECTED] So either something bad has happened with the glibc versioning upstream or glibc was built badly. > I think there's already a > forthcoming X 3.3.6 upgrade which will be rebuilt against woody glibc - > right, Branden? If it's woody, then it's probably an upstream problem but X 3.3.6 _should not_ be upgraded (well not to fix this anyway, obviously there may be other reasons to upgrade). -- James Antill -- [EMAIL PROTECTED] "If we can't keep this sort of thing out of the kernel, we might as well pack it up and go run Solaris." -- Larry McVoy.
