Re: r128 driver, unresolved symbols, XF86 4.0.2-1
On Sat, Jan 06, 2001 at 01:23:32AM +0100, Michel Dänzer wrote: jingai wrote: And I was specifying "r128" in the Device section before this release, which worked up until now. "ati" works fine though, so it's not a huge deal, but it's obviously a buglet, probably introduced when merging the two drivers. I'm not sure. The merge happened before 4.0.1e so it was even in earlier debs. BTW I forgot that you're also running on PPC; this is very interesting because "r128" works for me. Now I'm very confused. I presume that if you explicitly mention enough things in the Modules section of the XF86Config-4 file, the module dependencies will be satisfied accidentally. -- G. Branden Robinson | Debian GNU/Linux|Please do not look directly into laser [EMAIL PROTECTED] |with remaining eye. http://www.debian.org/~branden/ | PGP signature
Re: XFree86 4.0.2 status
"Chris" == Chris Rutter [EMAIL PROTECTED] writes: Chris I've heard now that a variety of different people are Chris working on XF4 for arm -- could the people who actually Chris are/ possibly stick their hand up; I'm willing to patch up Chris anything that I can, but I don't wish to tread on anyone's Chris toes... *one hand, hesitantly* I don't think you need to worry about the stepping part. The sooner any of us can show anything, the better. :-/ I've given it two more shots the last two days (it takes about 12 hours to build), after getting a working gcc/g++ and glibc22 in order. Each time I did something stupid (had uninstalled zlib-dev, and forgotten to reapply a couple of patches I hadn't given Branden yet, after getting new source). I'm doing another build right now. :^} -tor -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: XFree86 4.0.2 status
I don't think you need to worry about the stepping part. The sooner any of us can show anything, the better. :-/ I'd suggest you go ahead and upload the client and library packages, even if you can't make the server work. That way at least the autobuilder can start to clear the backlog of packages that are stuck waiting for xlibs-dev to become available. p. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: r128 driver, unresolved symbols, XF86 4.0.2-1
Branden Robinson wrote: On Sat, Jan 06, 2001 at 01:23:32AM +0100, Michel Dänzer wrote: jingai wrote: And I was specifying "r128" in the Device section before this release, which worked up until now. "ati" works fine though, so it's not a huge deal, but it's obviously a buglet, probably introduced when merging the two drivers. I'm not sure. The merge happened before 4.0.1e so it was even in earlier debs. BTW I forgot that you're also running on PPC; this is very interesting because "r128" works for me. Now I'm very confused. I presume that if you explicitly mention enough things in the Modules section of the XF86Config-4 file, the module dependencies will be satisfied accidentally. Here's mine: Section "Module" Load"dbe" Load"extmod" Load"type1" Load"freetype" Load"glx" EndSection AFAIR that's none of the modules jingai has unresolved symbols from? This part of the log is interesting: (II) LoadModule: "r128" (II) Loading /usr/X11R6/lib/modules/drivers/r128_drv.o (II) Module r128: vendor="The XFree86 Project" compiled for 4.0.2, module version = 4.0.1 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.3 (II) LoadModule: "ati" (II) Loading /usr/X11R6/lib/modules/drivers/ati_drv.o (II) Module ati: vendor="The XFree86 Project" compiled for 4.0.2, module version = 6.2.3 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.3 (II) LoadModule: "mouse" (II) Loading /usr/X11R6/lib/modules/input/mouse_drv.o (II) Module mouse: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.0.0 Module class: XFree86 XInput Driver ABI class: XFree86 XInput driver, version 0.1 (II) ATI: ATI driver (version 6.2.3) for chipsets: ati (II) R128: Driver for ATI Rage 128 chipsets: ATI Rage 128 RE (PCI), It does in fact first load the r128 module and then the ati one. Michel -- Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and The DRI Project -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[authorization] fails silently for normal users, cannot start server
Package: xserver-xfree86 Version: 4.0.1-9 Severity: important When I try to start X server as a user, the X server complains that the authorization has failed and terminates. Likewise when trying to login from gdm (tried other display managers, too) I can't paste anything now but as far as I can summarize: from auth.log, a message like PAM_unix[...]: authentication failure; (uid=0) - exa for gdm service exa is a normal user here, and gdm is the standard gdm. exa's uid is 1000 That's when I try to login from gdm. When I try to login from console the error is more silent. PAM_unix[..]: (login) session opened for user exa by LOGIN(uid=0) what is going on here? :((( none of our users can login to X for the past 6 weeks!!! help please. Thanks, -- System Information Debian Release: woody Architecture: i386 Kernel: Linux borg 2.2.14 #1 Wed Mar 29 19:43:52 EEST 2000 i686 Versions of packages xserver-xfree86 depends on: ii debconf 0.5.34 Debian configuration management sy ii libc6 2.2-6 GNU C Library: Shared libraries an ii xserver-common4.0.1-11 files and utilities common to all ii zlib1g1:1.1.3-11 compression library - runtime -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Fw: Hello
- Original Message - From: Rudy Hardeman [EMAIL PROTECTED] To: Jon Pennington [EMAIL PROTECTED] Sent: Saturday, January 06, 2001 11:04 AM Subject: Re: Hello - Original Message - From: Jon Pennington [EMAIL PROTECTED] To: Rudy Hardeman [EMAIL PROTECTED] Sent: Tuesday, January 02, 2001 5:25 PM Subject: Re: Hello Rudy Hardeman wrote: Happy nieuw year The same to you :) i have try to install the Xfree 4 but there were trobbeles during the install i upgrade the system and hav X running but on a resolution 800x600 and i want to run on 1024x768 and the system wont do that and a nother problem my mouse, reacts badd if i move the mouse then he clicks and moves to the other site of the screen, I have a PS/2 Mous on the /dev/psaux It sounds like a) you actually have an IMPS/2 mouse (one with a wheel) or b) you're running GPM at the same time. Fix one or both. aswel i downloaded the 2.2.18 kernel but kent find DRM support and AGP support in the kernel It sounds like you didn't enable `Experimental Code' in your kernel configuration. -- -=|JP|=-"Why, oh, why didn't I take the blue pill?" Jon Pennington| Atipa Linux Solutions -o) [EMAIL PROTECTED] | http://www.atipa.com/\\ Kansas City, MO, USA | 816-595-3000 x1550 _\_V 6D04 39E0 CAE9 9ADA 2CA3 2EBE 898A 6C37 CA1E A29C my X is running now but there are problems with mesa3 if i run my UnrealTournament he starts until he neet to load glide then he gives the error Video memory unprotected and i get get my resolution right he only wands to run on 800x600 but i want him to run on 1024x768 can you help me for the last time -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: r128 driver, unresolved symbols, XF86 4.0.2-1
Some Mach64 based chips cause problems with 2.2 kernels so he might need to also use a 2.4 one or a patch from Michael Schmitz (check the -powerpc archives). Or use yaboot. Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
compile problems.
Hello, I am having a problem compiling imlib2 it seems that the XShmAttach doesn't seem to exist anymore. I have the latest version of the deb's from brandens development area. Gordon. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
XFree86 4 not in testing?
Hi, I see that XFree86 4 is not in testing. Does that mean that 4 will not be in the next release of Debian? Any chance of getting at least the client-side in? Juliusz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: XFree86 4.0.2 status
"Branden" == Branden Robinson [EMAIL PROTECTED] writes: Branden If you absolutely have to make changes to the 4.0.2-1 Branden sources, please do them by stealth Ok. Unfortunately the patches I sent you earlier don't build an X server for ARM, so I will do what you just said. (I.e. send you updated patches, once it is built cleanly, and upload binary-only as 4.0.2-1). -tor -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: r128 driver, unresolved symbols, XF86 4.0.2-1
On Sat, Jan 06, 2001 at 01:23:32AM +0100, Michel Dänzer wrote: jingai wrote: And I was specifying r128 in the Device section before this release, which worked up until now. ati works fine though, so it's not a huge deal, but it's obviously a buglet, probably introduced when merging the two drivers. I'm not sure. The merge happened before 4.0.1e so it was even in earlier debs. BTW I forgot that you're also running on PPC; this is very interesting because r128 works for me. Now I'm very confused. I presume that if you explicitly mention enough things in the Modules section of the XF86Config-4 file, the module dependencies will be satisfied accidentally. -- G. Branden Robinson | Debian GNU/Linux|Please do not look directly into laser [EMAIL PROTECTED] |with remaining eye. http://www.debian.org/~branden/ | pgp54Kfb0vOwn.pgp Description: PGP signature
Re: XFree86 4.0.2 status
I don't think you need to worry about the stepping part. The sooner any of us can show anything, the better. :-/ I'd suggest you go ahead and upload the client and library packages, even if you can't make the server work. That way at least the autobuilder can start to clear the backlog of packages that are stuck waiting for xlibs-dev to become available. p.
Re: r128 driver, unresolved symbols, XF86 4.0.2-1
Branden Robinson wrote: On Sat, Jan 06, 2001 at 01:23:32AM +0100, Michel Dänzer wrote: jingai wrote: And I was specifying r128 in the Device section before this release, which worked up until now. ati works fine though, so it's not a huge deal, but it's obviously a buglet, probably introduced when merging the two drivers. I'm not sure. The merge happened before 4.0.1e so it was even in earlier debs. BTW I forgot that you're also running on PPC; this is very interesting because r128 works for me. Now I'm very confused. I presume that if you explicitly mention enough things in the Modules section of the XF86Config-4 file, the module dependencies will be satisfied accidentally. Here's mine: Section Module Loaddbe Loadextmod Loadtype1 Loadfreetype Loadglx EndSection AFAIR that's none of the modules jingai has unresolved symbols from? This part of the log is interesting: (II) LoadModule: r128 (II) Loading /usr/X11R6/lib/modules/drivers/r128_drv.o (II) Module r128: vendor=The XFree86 Project compiled for 4.0.2, module version = 4.0.1 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.3 (II) LoadModule: ati (II) Loading /usr/X11R6/lib/modules/drivers/ati_drv.o (II) Module ati: vendor=The XFree86 Project compiled for 4.0.2, module version = 6.2.3 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.3 (II) LoadModule: mouse (II) Loading /usr/X11R6/lib/modules/input/mouse_drv.o (II) Module mouse: vendor=The XFree86 Project compiled for 4.0.2, module version = 1.0.0 Module class: XFree86 XInput Driver ABI class: XFree86 XInput driver, version 0.1 (II) ATI: ATI driver (version 6.2.3) for chipsets: ati (II) R128: Driver for ATI Rage 128 chipsets: ATI Rage 128 RE (PCI), It does in fact first load the r128 module and then the ati one. Michel -- Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and The DRI Project
[authorization] fails silently for normal users, cannot start server
Package: xserver-xfree86 Version: 4.0.1-9 Severity: important When I try to start X server as a user, the X server complains that the authorization has failed and terminates. Likewise when trying to login from gdm (tried other display managers, too) I can't paste anything now but as far as I can summarize: from auth.log, a message like PAM_unix[...]: authentication failure; (uid=0) - exa for gdm service exa is a normal user here, and gdm is the standard gdm. exa's uid is 1000 That's when I try to login from gdm. When I try to login from console the error is more silent. PAM_unix[..]: (login) session opened for user exa by LOGIN(uid=0) what is going on here? :((( none of our users can login to X for the past 6 weeks!!! help please. Thanks, -- System Information Debian Release: woody Architecture: i386 Kernel: Linux borg 2.2.14 #1 Wed Mar 29 19:43:52 EEST 2000 i686 Versions of packages xserver-xfree86 depends on: ii debconf 0.5.34 Debian configuration management sy ii libc6 2.2-6 GNU C Library: Shared libraries an ii xserver-common4.0.1-11 files and utilities common to all ii zlib1g1:1.1.3-11 compression library - runtime
Fw: Hello
- Original Message - From: Rudy Hardeman [EMAIL PROTECTED] To: Jon Pennington [EMAIL PROTECTED] Sent: Saturday, January 06, 2001 11:04 AM Subject: Re: Hello - Original Message - From: Jon Pennington [EMAIL PROTECTED] To: Rudy Hardeman [EMAIL PROTECTED] Sent: Tuesday, January 02, 2001 5:25 PM Subject: Re: Hello Rudy Hardeman wrote: Happy nieuw year The same to you :) i have try to install the Xfree 4 but there were trobbeles during the install i upgrade the system and hav X running but on a resolution 800x600 and i want to run on 1024x768 and the system wont do that and a nother problem my mouse, reacts badd if i move the mouse then he clicks and moves to the other site of the screen, I have a PS/2 Mous on the /dev/psaux It sounds like a) you actually have an IMPS/2 mouse (one with a wheel) or b) you're running GPM at the same time. Fix one or both. aswel i downloaded the 2.2.18 kernel but kent find DRM support and AGP support in the kernel It sounds like you didn't enable `Experimental Code' in your kernel configuration. -- -=|JP|=-Why, oh, why didn't I take the blue pill? Jon Pennington| Atipa Linux Solutions -o) [EMAIL PROTECTED] | http://www.atipa.com/\\ Kansas City, MO, USA | 816-595-3000 x1550 _\_V 6D04 39E0 CAE9 9ADA 2CA3 2EBE 898A 6C37 CA1E A29C my X is running now but there are problems with mesa3 if i run my UnrealTournament he starts until he neet to load glide then he gives the error Video memory unprotected and i get get my resolution right he only wands to run on 800x600 but i want him to run on 1024x768 can you help me for the last time
Re: XFree86 4.0.2 status
On Fri, Jan 05, 2001 at 01:48:44PM -0500, Branden Robinson wrote: Bah. Oh maybe youre lucky. Hesaid X4.0 is next on his list, for powrpc though. Put xserver-fbdev on hold, and upgrade as much of XFree86 as will upgrade. I reinstalled xserver-fbdev from 3.3.6 (should be functionally equivalent to your proposal?), edit my config a little (had to add a Driver line to the Framebuffer Device) and started xdm: XFree86 Version 4.0.2 / X Window System (protocol Version 11, revision 0, vendor release 6400) Release Date: 18 December 2000 [...] (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module XFree86 Font Renderer: vendor=XFree86 Font Renderer compiled for 4.0.2, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Symbol memcpy from module /usr/X11R6/lib/modules/fonts/libbitmap.a is unresolved! [...] Fatal server error: Caught signal 11. Server aborting Same with startx. If I XF68_FBDev though (after removing Driver again, unknown keyword otherwise...) I do get X to run, but I don't get any window manager or xterm to start. Pretty useless. This try was with a remote ssh login, if I do it from the console, it simply crashes with signal 8. Weird. Anyhow, this does not look like a solution, since the modules are makeing trouble right now? Christian.
Xfree-3.3.6 + i810 + krnl-2.2.18 : precisions wanted
Hi all, I spent my friday afternoon, installing potato (r2) on a dell optiplex gx100 with a i810 on board card. Everything went fluently except the configuration of xfree. We already avec a buch of boxes here with i810 cards under debian and Mandrake and until now I didn't have much trouble. After browsing changelogs, searching mailing lists and using google quite intensively I found an answer from Brenden to a similar problem. From memory : - the implementation of the agpgart module in kernel-2.2.18 is not compatible with xfree-3.3.6 and the solution proposed where : - downgrade to 2.2.17 - use C. Botha unofficial xfree-4.0 packages for potato. First remark : - I would be nice if this information where more accessible : On the debian-x page under the agpgart section for exemple. Better would be in the documentation comming with the xserver-svga package. I did try the unofficial xfree4 packages (deb http://people.debian.org/~cpbotha/ xf401_potato/i386/) but i seems the dependence tree is broken : xserver-xfree86: Depends: xserver-common (4.0) but 3.3.6-11potato15 is to be installed So i did revert to kernel 2.2.17 and everything is ok. Now if i didn't misunderstood anything, we can't have kernel-2.2.18 + xfree-3.3.6 + i810 cards actualy on potato. If that's the case, it's an RC bug in the minute, 'cause potato r2 is shipped with kernel-2.2.18PRExx. otherwise I would appreciate if so could explain what I did wrong and what is the pb with xfree-3.3.6 and krnel-2.2.18. Thank's for your time, Fab
Re: XFree86 4.0.2 status
On Sat, Jan 06, 2001 at 06:16:00PM +0100, Christian T. Steigies wrote: On Fri, Jan 05, 2001 at 01:48:44PM -0500, Branden Robinson wrote: Bah. Oh maybe youre lucky. Hesaid X4.0 is next on his list, for powrpc though. Put xserver-fbdev on hold, and upgrade as much of XFree86 as will upgrade. I reinstalled xserver-fbdev from 3.3.6 (should be functionally equivalent to your proposal?), edit my config a little (had to add a Driver line to the Framebuffer Device) and started xdm: XFree86 Version 4.0.2 / X Window System (protocol Version 11, revision 0, vendor release 6400) Release Date: 18 December 2000 [...] (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module XFree86 Font Renderer: vendor=XFree86 Font Renderer compiled for 4.0.2, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Symbol memcpy from module /usr/X11R6/lib/modules/fonts/libbitmap.a is unresolved! [...] Fatal server error: Caught signal 11. Server aborting Same with startx. If I XF68_FBDev though (after removing Driver again, unknown keyword otherwise...) I do get X to run, but I don't get any window manager or xterm to start. Pretty useless. This try was with a remote ssh login, if I do it from the console, it simply crashes with signal 8. Weird. Anyhow, this does not look like a solution, since the modules are makeing trouble right now? Could you try not stripping the modules? I recall alpha having a similar problem. Dan /\ /\ | Daniel Jacobowitz|__|SCS Class of 2002 | | Debian GNU/Linux Developer__Carnegie Mellon University | | [EMAIL PROTECTED] | | [EMAIL PROTECTED] | \/ \/
Re: r128 driver, unresolved symbols, XF86 4.0.2-1
Some Mach64 based chips cause problems with 2.2 kernels so he might need to also use a 2.4 one or a patch from Michael Schmitz (check the -powerpc archives). Or use yaboot. Michael
compile problems.
Hello, I am having a problem compiling imlib2 it seems that the XShmAttach doesn't seem to exist anymore. I have the latest version of the deb's from brandens development area. Gordon.
Re: XFree86 4.0.2 status
Philip == Philip Blundell [EMAIL PROTECTED] writes: Philip I'd suggest you go ahead and upload the client and library Philip packages, even if you can't make the server work. That Philip way at least the autobuilder can start to clear the Philip backlog of packages that are stuck waiting for xlibs-dev Philip to become available. Good enough, I will make a NMU upload tomorrow. (I just started another build, before seeing this message). -tor -- Får i ulveklær
Re: XFree86 4.0.2 status
On Sat, Jan 06, 2001 at 06:06:37PM -0800, Tor Slettnes wrote: Philip == Philip Blundell [EMAIL PROTECTED] writes: Philip I'd suggest you go ahead and upload the client and library Philip packages, even if you can't make the server work. That Philip way at least the autobuilder can start to clear the Philip backlog of packages that are stuck waiting for xlibs-dev Philip to become available. Good enough, I will make a NMU upload tomorrow. (I just started another build, before seeing this message). Why an NMU? Please don't. If you change the version number it will turn the clock back on the dinstall. If you absolutely have to make changes to the 4.0.2-1 sources, please do them by stealth (e.g., do a binary upload with the same version number despite the fact that your source doesn't match the official one). I know that's technically illegal but as long as you send me all the changes everything will be fine. Again, please, do NOT upload anything but 4.0.2-1. Otherwise you will keep X, and everything that depends on it, out of testing for at least another 14 days. -- G. Branden Robinson | Debian GNU/Linux|Please do not look directly into laser [EMAIL PROTECTED] |with remaining eye. http://www.debian.org/~branden/ | pgpWePn69udAJ.pgp Description: PGP signature
