Re: the continuing adventures of XFree86 4.0.1
"Christian T. Steigies" wrote: On Mon, Dec 11, 2000 at 04:29:12PM +0100, Michel Dänzer wrote: "Christian T. Steigies" wrote: On Mon, Dec 11, 2000 at 02:52:39PM +0100, Michel Dänzer wrote: Looked at xc/programs/Xserver/hw/xfree86/os-support/bus yet? Only so much as to use "generic" pci code for m68k as well. I need to know where the pcidata module is defined. xc/programs/Xserver/hw/xfree86/scanpci ? It fails after/during: (II) Loading /usr/X11R6/lib/modules/libpcidata.a On my i386 box: (II) LoadModule: "scanpci" comes later, so its not scanpci? locate or find shows that libpcidata.a is indeed built in the scanpci directory. Shouldnt it be enough to just jet it return silently? There is nothing to scan here, What about the m68k machines that do have PCI? Mine hasn't, somebody with a m68k/pci machine (if they exist at all?) can do that. Actually, I did not get _any_ feedback from debian-68k users on these packages. What shall I do, buy me all sorts of m68k machines to test it myself? No, of course not. But be prepared for those you ignore to cry up sooner or later. :) The code is the best documentation ;) _This_ code is hughe... I am not going to read it completely... The modules are rather self contained. 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]
Re: Tracking XFree86 CVS on a Potato system
* Juliusz Chroboczek [EMAIL PROTECTED] [001211 10:30]: First of all, I'd like to know whether building Branden's packages on a Potato system yields a usable version of XFree86. Thanks for the note about not needing CC:s. I never know when I see posts from new people. :) You can indeed build Branden's packages for potato, but Charl P. Botha has done this already! I submitted the URL he gave for this a while ago to google, so it should be able to find him and his packages without effort. (It would also be in the archives, but that takes more effort to search than google. :) Of course, I don't know if he tracks Branden as quickly as Branden tracks CVS -- so, Charl also wrote a quick description on building the 4.0.1 source packages Branden makes on potato. But, if you are truly making this a development box, why not go all out, and run woody, what with its often updates to everything? :) -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Tracking XFree86 CVS on a Potato system
On Mon, Dec 11, 2000 at 11:37:58AM -0800, Seth Arnold wrote: * Juliusz Chroboczek [EMAIL PROTECTED] [001211 10:30]: First of all, I'd like to know whether building Branden's packages on a Potato system yields a usable version of XFree86. You can indeed build Branden's packages for potato, but Charl P. Botha has done this already! I submitted the URL he gave for this a while ago to google, so it should be able to find him and his packages without effort. (It would also be in the archives, but that takes more effort to search than google. :) The potato xfree86 4.0.1 packages are apt-able with the following lines: deb http://people.debian.org/%7Ecpbotha/ xf401_potato/i386/ deb http://people.debian.org/%7Ecpbotha/ xf401_potato/all/ Of course, I don't know if he tracks Branden as quickly as Branden tracks CVS -- so, Charl also wrote a quick description on building the 4.0.1 source packages Branden makes on potato. I don't track him that quickly... on average I build every 2nd or 3d release that he makes. I'm planning a potato build of 4.0.1-11 as soon as that's in woody for a day or two. The ones that are apt-able at the moment are -8, and I find them rock-solid on my hardware. You can also find the howto on this at http://cpbotha.net/building_woody_xfree86_4.0.1_debs_on_potato.HOWTO -- charl p. botha | computer graphics and cad/cam http://cpbotha.net/ | http://www.cg.its.tudelft.nl/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: status on the donated blue white G3
On Dec 11, Branden Robinson [EMAIL PROTECTED] wrote:
Dan, are you *sure* we don't need an autobuilder? Not even for some
subsection of the archive? How about contrib? :)
If needed, I can set up an autobuilder on the B50 I'm installing and
which will become the new {ftp,http}.it.debian.org.
--
ciao,
Marco
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: building xfree86 4 for debian/arm
"Peter" == Peter Maydell [EMAIL PROTECTED] writes: Peter I tried putting together some patches based on a Peter combination of the 3.x ARM patches and the 4.0 patches for Peter other non-x86 architectures; it's now falling over with a Peter compile error in elfloader.c. It looks like the dynamic Peter loader has no ARM support at all, and I don't think I can Peter get away with just adding "|| defined(__arm__)" to cpp Peter conditionals for this one :- I have been playing with this for the last couple of weeks. After getting elfloader.c to compile with the most common relocation types (R_ARM_ABS32, R_ARM_REL32, R_ARM_PC24) defined, there are still a couple outstanding: (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a Elf_RelocateEntry() Unsupported relocation type 56 Elf_RelocateEntry() Unsupported relocation type 24 24 happens to be: #define R_ARM_GOTOFF24 /* 32 bit offset to GOT */ By itself this is pretty odd, but #56 is simply not defined in /usr/include/elf.h at all. I am rebuilding right now (a 10-hour process) with "Elf_Rel" rather than "Elf_Rela" setup, to see if that makes a difference. (Seing that ARM, like i386, unlike any of the other processors, is Little Endian). Peter I've temporarily put my patches-so-far at: Peter http://www.chiark.greenend.org.uk/~pmaydell/misc/patches.txt Peter if anybody else is interested. (NB that in particular the Peter list of 'which drivers to build' in xfree86.cf is totally Peter guesswork...) Framebuffer stuff. I have changed the section that starts with: #if defined(PpcArchitecture) || defined(Mc68020Architecture) to #if defined(PpcArchitecture) || defined(Mc68020Architecture) || \ defined(Arm32Architecture) -tor -- Får i ulveklær -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: quick fix for building nvidia xfree4 drivers on kernel 2.4.0-test11
thanks! sounds like agreat idea, but im fairly new to this so editing the complier flags would be a bit too much for me (now) mind showing me what this would look like? g On Mon, 11 Dec 2000, Raphael Deimel wrote: Date: Mon, 11 Dec 2000 23:49:40 +0100 From: Raphael Deimel [EMAIL PROTECTED] To: dude [EMAIL PROTECTED] Cc: debian-x Mailing List [EMAIL PROTECTED] Subject: Re: quick fix for building nvidia xfree4 drivers on kernel 2.4.0-test11 Resent-From: [EMAIL PROTECTED] i saw on on tomshardware site that worked for 2.2 is it essentialy the same for 2.4? i'm currently running xf4, kernel 2.4.0-test10 with NVidia's own accellerated drivers (hell, this is what graphics speed supposed to be ;) You could fetch the latest driver (0.9.5) and insert Mads Buus Jensen's code snippet in nv.h (as he suggested - THANKS for the quick'n'dirty fix). AND you should edit the Makefile to include -DKERNEL_2_3 within the compiler flags (think he forgot that one) -- 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: quick fix for building nvidia xfree4 drivers on kernel 2.4.0-test11
If the Makefile was written well, it will be simple. Open the Makefile with your favorite editor (vim is mine! :) and look for lines similar to -DSOMETHING. Add the -DKERNEL_2_3 bit to this line. Or, if there isn't something that looks right, see if there is a CCFLAGS line -- and add the -DKERNEL_2_3 flag there. HTH :) * dude [EMAIL PROTECTED] [001211 16:59]: thanks! sounds like agreat idea, but im fairly new to this so editing the complier flags would be a bit too much for me (now) mind showing me what this would look like? g On Mon, 11 Dec 2000, Raphael Deimel wrote: Date: Mon, 11 Dec 2000 23:49:40 +0100 From: Raphael Deimel [EMAIL PROTECTED] To: dude [EMAIL PROTECTED] Cc: debian-x Mailing List [EMAIL PROTECTED] Subject: Re: quick fix for building nvidia xfree4 drivers on kernel 2.4.0-test11 Resent-From: [EMAIL PROTECTED] i saw on on tomshardware site that worked for 2.2 is it essentialy the same for 2.4? i'm currently running xf4, kernel 2.4.0-test10 with NVidia's own accellerated drivers (hell, this is what graphics speed supposed to be ;) You could fetch the latest driver (0.9.5) and insert Mads Buus Jensen's code snippet in nv.h (as he suggested - THANKS for the quick'n'dirty fix). AND you should edit the Makefile to include -DKERNEL_2_3 within the compiler flags (think he forgot that one) -- 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] -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[mongoose@users.sourceforge.net: X upgrade policy]
- Forwarded message from Terry 'Mongoose' Hendrix II [EMAIL PROTECTED] - From: "Terry 'Mongoose' Hendrix II" [EMAIL PROTECTED] To: Branden Robinson [EMAIL PROTECTED] Subject: X upgrade policy Date: Mon, 11 Dec 2000 16:05:35 -0500 (EST) Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Sender: mongoose@localhost Reply-To: "Terry 'Mongoose' Hendrix" [EMAIL PROTECTED] In-Reply-To: [EMAIL PROTECTED] Message-ID: Pine.LNX.4.10.10012111559520.437-10@localhost Why have you made the upgrade path in X impossible? You can't run utah on 4.0 - yet you blindly install 4.0 over every system by dependcies. You don't even bother checking /proc to see what card is installed. A simple grep of /proc/pci shows I have an AGP G400, not a V3! I have a machine that has half 3.3.6-18 and 4.0 installed now - and I had the utah package installed! You should check for utah before 'upgrading' blindly over it. I told you people not to do this - 3d accel is very important - you shouldn't dissmiss it outright. I'm having to reinstall all my X libs and applications now, and I can't develop my projects while fixing your mistakes. cheers, Terry --- | GooseEgghttp://gooseegg.sourceforge.net | | QuakeForge http://www.quakeforge.net | | Personalhttp://www.westga.edu/~stu7440| | | | Dream is running Debian GNU/Linux| --- - End forwarded message - -- G. Branden Robinson| The greatest productive force is human Debian GNU/Linux | selfishness. [EMAIL PROTECTED] | -- Robert Heinlein http://deadbeast.net/~branden/ | PGP signature
[kteague@sprocket.ddts.net: xserver-xsun drivers]
Does anyone know which driver the TurboGX uses? - Forwarded message from Ken Teague [EMAIL PROTECTED] - From: Ken Teague [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: xserver-xsun drivers Date: Mon, 11 Dec 2000 13:29:55 -0800 Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Message-Id: [EMAIL PROTECTED] Hi Branden, sorry to bother you like this. I'm running Debian Sparc (woody) and can't find a listing of which driver to use for X with my TURBOXGX SBus card. I also checked www.xfree86.org but they don't list it either. Can you please point me to where I can find information about which driver I need for my frame buffer card? Thanks. - Ken - End forwarded message - -- G. Branden Robinson|Somewhere, there is a .sig so funny that Debian GNU/Linux |reading it will cause an aneurysm. This [EMAIL PROTECTED] |is not that .sig. http://deadbeast.net/~branden/ | PGP signature
[bossart@deesse.univ-lemans.fr: xfree86]
- Forwarded message from Romain Bossart [EMAIL PROTECTED] - From: Romain Bossart [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: xfree86 Date: Mon, 11 Dec 2000 17:36:44 +0100 (CET) Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Hi, I got a problem when I upgraded my xfree86 to the 4.0.1-10 version, the server doesn't start, and I get this message ; X: user not authorized to run the X server, aborting. what can I do to make it work again ? thank you -- ++ | Romain Bossart - Laboratoire d'Acoustique - LAUM-UMR CNRS 6613 | | Universite du Maine - av. O. Messiaen - 72000 Le Mans (France) | | tel: 02 43 83 36 18 fax: 02 43 83 35 20 | | http://www.univ-lemans.fr[EMAIL PROTECTED] | ++ - End forwarded message - -- G. Branden Robinson|It was a typical net.exercise -- a Debian GNU/Linux |screaming mob pounding on a greasy spot [EMAIL PROTECTED] |on the pavement, where used to lie the http://deadbeast.net/~branden/ |carcass of a dead horse. PGP signature
Re: [mongoose@users.sourceforge.net: X upgrade policy]
Terry, a few quick comments -- first, Utah-glx is in the past. While their work may have been nifty at one point, and for people running 3.3.x perhaps necessary, XF 4.0.1 has a *much* easier GL system. Second, I'm not sure what you mean by ``I have a g400, not a v3'' -- last time I ran the dexter program, it did not automatically assume I had any type of video card -- rather, it allowed me to select my g400 from a list. But then, I haven't run dexter lately. Third, welcome to life running Debian unstable. :) If you want nice stable operating, run potato. It is very good. If you want the latest and greatest (including XF4.0.1's much improved GLX support), then running woody is just fine -- though there will be bumps along the way. Those bumps are part of running woody, until it is declared stable. (Well, heck, bumps might happen then too, but we try to minimize them. :) Fourth, there is no pressing need to email Branden directly -- he is awful busy. Using lists such as debian-user (for most X questions) or debian-x (for questions specific to the debian packaging of X) will usually get responses much faster. Cheers! :) * Branden Robinson [EMAIL PROTECTED] [001211 19:35]: - Forwarded message from Terry 'Mongoose' Hendrix II [EMAIL PROTECTED] - From: "Terry 'Mongoose' Hendrix II" [EMAIL PROTECTED] To: Branden Robinson [EMAIL PROTECTED] Subject: X upgrade policy Date: Mon, 11 Dec 2000 16:05:35 -0500 (EST) Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Sender: mongoose@localhost Reply-To: "Terry 'Mongoose' Hendrix" [EMAIL PROTECTED] In-Reply-To: [EMAIL PROTECTED] Message-ID: Pine.LNX.4.10.10012111559520.437-10@localhost Why have you made the upgrade path in X impossible? You can't run utah on 4.0 - yet you blindly install 4.0 over every system by dependcies. You don't even bother checking /proc to see what card is installed. A simple grep of /proc/pci shows I have an AGP G400, not a V3! I have a machine that has half 3.3.6-18 and 4.0 installed now - and I had the utah package installed! You should check for utah before 'upgrading' blindly over it. I told you people not to do this - 3d accel is very important - you shouldn't dissmiss it outright. I'm having to reinstall all my X libs and applications now, and I can't develop my projects while fixing your mistakes. cheers, Terry --- | GooseEgghttp://gooseegg.sourceforge.net | | QuakeForge http://www.quakeforge.net | | Personalhttp://www.westga.edu/~stu7440| | | | Dream is running Debian GNU/Linux| --- - End forwarded message - -- G. Branden Robinson| The greatest productive force is human Debian GNU/Linux | selfishness. [EMAIL PROTECTED] | -- Robert Heinlein http://deadbeast.net/~branden/ | -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [harri@synopsys.COM: gdm and kdm can't start X]
Would the /etc/X11/Xwrapper.config file affect gdm or kdm? * Branden Robinson [EMAIL PROTECTED] [001211 19:46]: Not sure what the problem is here; I don't know what would make the X server become a zombie process. - Forwarded message from Harald Dunkel [EMAIL PROTECTED] - From: Harald Dunkel [EMAIL PROTECTED] To: Branden Robinson [EMAIL PROTECTED] Subject: gdm and kdm can't start X Date: Mon, 11 Dec 2000 20:30:59 +0100 Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.0-test11 i586) X-Accept-Language: en Hi Branden After the last update of XFree 4.0.1 gdm and kdm stopped working. The XServer doesn't come up. 'ps -ef' shows me '[ X defunct ]'. Is this an installation problem? Regards Harri -- Harald Dunkel | [EMAIL PROTECTED] | Against stupidity the very gods Synopsys GmbH | Kaiserstr. 100 | Themselves contend in vain. 52134 Herzogenrath, Germany | +49 2407 9558 (fax? 44: 0) | Schiller, The Maid of Orleans - End forwarded message - -- G. Branden Robinson|Men use thought only to justify their Debian GNU/Linux |wrong doings, and speech only to conceal [EMAIL PROTECTED] |their thoughts. http://deadbeast.net/~branden/ |-- Voltaire -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [mongoose@users.sourceforge.net: X upgrade policy]
Not to mention that the G400 driver for XFree 4 has 3D acceleration as well. It's currently kinda broken (stencils don't work at all (not even in software fallback - they're borked), and there are some pretty icky persistent texturing bugs, but it's usable. Just not very. Personally, I'm annoyed by the persistent brokenness of the DRI drivers, but I'm making do in my projects, and if I want to verify my code's correctness I can always use an LD_PRELOAD to force software mesa to check accuracy. It would be nice if the XFree 4 packages had a 'Conflicts: utah-glx' in it, but as has been said already, you ARE running Debian *usntable*, and you reap what you sow in that regard... don't take it out on Branden, please. -- Joshua Shagam /"\ ASCII Ribbon Campaign [EMAIL PROTECTED] \ / No HTML/RTF in email www.cs.nmsu.edu/~joshagam X No Word docs in email mp3.com/fluffyporcupine/ \ Respect for open standards -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [bossart@deesse.univ-lemans.fr: xfree86]
you need to reconfigure xserver-common i believe you cant 'apt-get --reconfigure xserver-common' and select 'anybbody' to starts windows. if that is wrong go to irc.debian.org room: #debian and look at the topic which will give you the answer ~ On Mon, 11 Dec 2000, Branden Robinson wrote: Date: Mon, 11 Dec 2000 22:46:55 -0500 From: Branden Robinson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: [[EMAIL PROTECTED]: xfree86] Resent-From: [EMAIL PROTECTED] - Forwarded message from Romain Bossart [EMAIL PROTECTED] - From: Romain Bossart [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: xfree86 Date: Mon, 11 Dec 2000 17:36:44 +0100 (CET) Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Hi, I got a problem when I upgraded my xfree86 to the 4.0.1-10 version, the server doesn't start, and I get this message ; X: user not authorized to run the X server, aborting. what can I do to make it work again ? thank you -- ++ | Romain Bossart - Laboratoire d'Acoustique - LAUM-UMR CNRS 6613 | | Universite du Maine - av. O. Messiaen - 72000 Le Mans (France) | | tel: 02 43 83 36 18 fax: 02 43 83 35 20 | | http://www.univ-lemans.fr[EMAIL PROTECTED] | ++ - End forwarded message - -- G. Branden Robinson|It was a typical net.exercise -- a Debian GNU/Linux |screaming mob pounding on a greasy spot [EMAIL PROTECTED] |on the pavement, where used to lie the http://deadbeast.net/~branden/ |carcass of a dead horse. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [mongoose@users.sourceforge.net: X upgrade policy]
On Mon, 11 Dec 2000, Joshua Shagam wrote: It would be nice if the XFree 4 packages had a 'Conflicts: utah-glx' in it, but as has been said already, you ARE running Debian *usntable*, and you reap what you sow in that regard... don't take it out on Branden, please. I told the X people months ago not to force out utah - that's why I'm pissed off. An overnight upgrade of gtk shouldn't break my x server. I also think hiding behind the debian stand-by "it's not even supposed to work" is why packages are always broken - no one cares. cheers, Terry --- | GooseEgghttp://gooseegg.sourceforge.net | | QuakeForge http://www.quakeforge.net | | Personalhttp://www.westga.edu/~stu7440| | | | Dream is running Debian GNU/Linux| --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [mongoose@users.sourceforge.net: X upgrade policy]
On Mon, 11 Dec 2000, Seth Arnold wrote: Terry, a few quick comments -- first, Utah-glx is in the past. While their work may have been nifty at one point, and for people running 3.3.x perhaps necessary, XF 4.0.1 has a *much* easier GL system. This is about poor forethought. I complained months ago about how the X team was moving to lock out utah-glx. Utah has more users than DRI - why do this? I woke up from an overnight upgrade of gtk to find my X install made unusable. The point is I need utah to delevop and run Open GL apps, until DRI matures - by making utah uninstallable and not accounting for an installed utah - branden has effectively banned it. You might want utah to play tribes2 or run a modeler one day too. cheers, Terry --- | GooseEgghttp://gooseegg.sourceforge.net | | QuakeForge http://www.quakeforge.net | | Personalhttp://www.westga.edu/~stu7440| | | | Dream is running Debian GNU/Linux| --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [mongoose@users.sourceforge.net: X upgrade policy]
On Tue, Dec 12, 2000 at 02:38:06AM -0500, Terry 'Mongoose' Hendrix II wrote: On Mon, 11 Dec 2000, Seth Arnold wrote: Terry, a few quick comments -- first, Utah-glx is in the past. While their work may have been nifty at one point, and for people running 3.3.x perhaps necessary, XF 4.0.1 has a *much* easier GL system. This is about poor forethought. I complained months ago about how the X team was moving to lock out utah-glx. Utah has more users than DRI - why do this? I woke up from an overnight upgrade of gtk to find my X install made unusable. Well, it was also a poor forethought for you to not issue a package hold on the XFree packages. It's easy enough to use dselect to request that a package not be upgraded... (hint: = key) -- Joshua Shagam /"\ ASCII Ribbon Campaign [EMAIL PROTECTED] \ / No HTML/RTF in email www.cs.nmsu.edu/~joshagam X No Word docs in email mp3.com/fluffyporcupine/ \ Respect for open standards -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [mongoose@users.sourceforge.net: X upgrade policy]
On Tue, 12 Dec 2000, Terry 'Mongoose' Hendrix II wrote: I told the X people months ago not to force out utah - that's why I'm pissed off. An overnight upgrade of gtk shouldn't break my x server. I also think hiding behind the debian stand-by "it's not even supposed to work" is why packages are always broken - no one cares. I don't think anyone is saying "it's not even supposed to work"what I think is the case here is that we're all trying to shake the bugs out of the DRI code using wider-spread testing. Keep in mind that woody will not be released next week, so the transition is actually quite timely and important. We could remain using XF86 v3.3.x forever, but I think that we would hear more about not trying to do the changeover at this point in woody's development. Keep in mind also that, while you may run on ix86, there are MANY of us that don't (I have two sparcs, three alphas, and a mips in my "home lab" that I run Debian on. This version of X using DRI is much improved on at least Alpha and has the potential (really soon now) to compile and run on my Indy sans huge amounts of patching, unlike any other X version prior. Lastly, the "no one cares" argument is rather insulting and, in my experience, will not persuade anyone to look into your problems or respect your opinion about the matter (last time someone insulted me, I just walked away...which, I suspect, is pretty common and civilised human behaviour). I can say, as a maintainer of more than four packages for Debian, WE DO CARE, but you have to allow us time to shake out problems. We've all made mistakes and released things that break "the norm", but that's part of knowing your package, the future roadmap of the packages involved, and the release cycle timing of unstable. I back Branden's decisions to proceed with the upgrade to DRI. He hosted experimental packages on his own for quite some time, hoping that he would get enough people to test them while trying to fix up the monumental packaging requirements of something this size. Whether he got the feedback he needed or not, he made the decision and I think that unstable is better because of it (now I finally have an X server that runs on my V3 in my main Alpha and a much less buggy X server on the other two). Sure, there's going to be some hiccups and problems, hence the neverending "startx is telling me that I'm not allowed to run the X server anymore" threads, but things happen in unstable and sometimes, we just have to weather through them or do what we have to do to suit our specific needs. To end this long reply, I suggest this: compile your own Xserver and utah and install it in /usr/local until things work out to the point where they are usable again for your setup. Running "unstable" means that YMMV, which sounds like an excuse, but it's really the truth and is not meant to discount complaints. Again, things happen, older software sometimes isn't compatible with newer software, etc...either way, the point is, we do care and, if you're looking for stability, stick with potato and just compile the packages from woody that you need yourself until woody is released. C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
status on the donated blue white G3
The machine arrived on Friday. Turns out it has 192MB of RAM, not 256. Oh darn. :) It's sawing through a compile of XFree86 4.0.1Z right now. I'll let everyone know the margin by which it beats my 56MB 7200/90. I'd like to publicly thank the donor, M Carling. Dan, are you *sure* we don't need an autobuilder? Not even for some subsection of the archive? How about contrib? :) -- G. Branden Robinson |I am sorry, but what you have mistaken Debian GNU/Linux|for malicious intent is nothing more [EMAIL PROTECTED] |than sheer incompetence! http://www.debian.org/~branden/ |-- J. L. Rizzo II pgpZZ6oru0uz1.pgp Description: PGP signature
Re: the continuing adventures of XFree86 4.0.1
On Thu, Dec 07, 2000 at 04:11:57PM -0500, Branden Robinson wrote: Please wait until you see source for 10pre11v2. There's no point wasting your time building v1 since I'm committing some fairly important bug fixes. MANIFEST.m68k for this version is on http://people.debian.org/~cts/x4.0/ I think I need some ideas how to make it work on m68k, just compiling it seems not to be enough. seems I need to fix some PCI functions, but I don't even know _where_ to start looking. Christian -- First they ignore you. Then they laugh about you. Then they fight you. And then you win. [Mahatma Gandhi]
Re: building xfree86 4 for debian/arm
Branden Robinson wrote: On Fri, Dec 08, 2000 at 06:09:51PM +, Peter Maydell wrote: # remove the upstream symlink X - XFree86 This symlink does not exist because the XFree86 server binary was not built in the first place and therefore no symlink was created. That's bad. [Would I be better off asking this question of the debian-arm list?] The actual porting will probably have to be done by someone familiar with the ARM, but something could likely be cooked up fairly quickly, based on the ARM patches for XFree86 3.x. [I've added debian-arm to the CC list] I tried putting together some patches based on a combination of the 3.x ARM patches and the 4.0 patches for other non-x86 architectures; it's now falling over with a compile error in elfloader.c. It looks like the dynamic loader has no ARM support at all, and I don't think I can get away with just adding || defined(__arm__) to cpp conditionals for this one :- I've temporarily put my patches-so-far at: http://www.chiark.greenend.org.uk/~pmaydell/misc/patches.txt if anybody else is interested. (NB that in particular the list of 'which drivers to build' in xfree86.cf is totally guesswork...) [Incidentally, I think the way that non-Intel Linux architectures are dealt with in the X sources is pretty vile; there's lots of places that go : #if defined(__powerpc__) || defined(__mc68000__) || defined(__alpha__) || ... /* stuff for not-x86 */ #else /* stuff for x86 */ #endif which is just completely backwards. And it would be much cleaner in elfloader.c to say #ifdef cpu_is_64_bit rather than #if defined (__alpha__) || defined (__ia64__) || (defined (__sparc (...) ] Peter Maydell
Re: the continuing adventures of XFree86 4.0.1
Christian T. Steigies wrote: On Thu, Dec 07, 2000 at 04:11:57PM -0500, Branden Robinson wrote: Please wait until you see source for 10pre11v2. There's no point wasting your time building v1 since I'm committing some fairly important bug fixes. MANIFEST.m68k for this version is on http://people.debian.org/~cts/x4.0/ I think I need some ideas how to make it work on m68k, just compiling it seems not to be enough. seems I need to fix some PCI functions, but I don't even know _where_ to start looking. Looked at xc/programs/Xserver/hw/xfree86/os-support/bus yet? 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
Re: the continuing adventures of XFree86 4.0.1
On Mon, Dec 11, 2000 at 02:52:39PM +0100, Michel Dänzer wrote: Looked at xc/programs/Xserver/hw/xfree86/os-support/bus yet? Only so much as to use generic pci code for m68k as well. I need to know where the pcidata module is defined. Shouldnt it be enough to just jet it return silently? There is nothing to scan here, maybe that would be sufficient for a quick hack (and mabye I could recompile and copy that module without rebuild the whole of X?). Maybe there is some hackers documentation which allows me to understand this quickly? I do not want to become an xfree hacker, I just want a small patch. Christian -- http://people.debian.org/~cts/
Re: the continuing adventures of XFree86 4.0.1
Christian T. Steigies wrote: On Mon, Dec 11, 2000 at 02:52:39PM +0100, Michel Dänzer wrote: Looked at xc/programs/Xserver/hw/xfree86/os-support/bus yet? Only so much as to use generic pci code for m68k as well. I need to know where the pcidata module is defined. xc/programs/Xserver/hw/xfree86/scanpci ? Shouldnt it be enough to just jet it return silently? There is nothing to scan here, What about the m68k machines that do have PCI? maybe that would be sufficient for a quick hack (and mabye I could recompile and copy that module without rebuild the whole of X?). Maybe there is some hackers documentation which allows me to understand this quickly? I do not want to become an xfree hacker, I just want a small patch. The code is the best documentation ;) No, seriously, the man to answer such questions is probably Egbert Eich [EMAIL PROTECTED]. 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
Re: the continuing adventures of XFree86 4.0.1
On Mon, Dec 11, 2000 at 04:29:12PM +0100, Michel Dänzer wrote: Christian T. Steigies wrote: On Mon, Dec 11, 2000 at 02:52:39PM +0100, Michel Dänzer wrote: Looked at xc/programs/Xserver/hw/xfree86/os-support/bus yet? Only so much as to use generic pci code for m68k as well. I need to know where the pcidata module is defined. xc/programs/Xserver/hw/xfree86/scanpci ? It fails after/during: (II) Loading /usr/X11R6/lib/modules/libpcidata.a On my i386 box: (II) LoadModule: scanpci comes later, so its not scanpci? Shouldnt it be enough to just jet it return silently? There is nothing to scan here, What about the m68k machines that do have PCI? Mine hasn't, somebody with a m68k/pci machine (if they exist at all?) can do that. Actually, I did not get _any_ feedback from debian-68k users on these packages. What shall I do, buy me all sorts of m68k machines to test it myself? The code is the best documentation ;) _This_ code is hughe... I am not going to read it completely... Christian -- http://people.debian.org/~cts/
Tracking XFree86 CVS on a Potato system
Dear all, I've recently switched to a Debian system and I am wondering how to track the XFree86 CVS version without wreaking havoc with the packaging system. I'm very happy with my Potato (2.2r2) system, and I definitely don't want to upgrade libc. (Just taking the opportunity to say how happy I am I did the switch.) First of all, I'd like to know whether building Branden's packages on a Potato system yields a usable version of XFree86. Assuming that's indeed the case, I can see three options. One would be to build an empty package that requires nothing but provides all the XFree86 packages that a Potato system needs. Then build and install from the XFree86 CVS sources without informing the package system. Yuck. Another option would be to grab Branden's source packages, overwrite the sources with the CVS version, build and install binary packages. Finally, I could do the same with Charles Botha's packages. Any other ideas? Any good advice youse could give me? Thanks a lot, Juliusz P.S. no need to CC me if you reply to the list.
Re: the continuing adventures of XFree86 4.0.1
Christian T. Steigies wrote: On Mon, Dec 11, 2000 at 04:29:12PM +0100, Michel Dänzer wrote: Christian T. Steigies wrote: On Mon, Dec 11, 2000 at 02:52:39PM +0100, Michel Dänzer wrote: Looked at xc/programs/Xserver/hw/xfree86/os-support/bus yet? Only so much as to use generic pci code for m68k as well. I need to know where the pcidata module is defined. xc/programs/Xserver/hw/xfree86/scanpci ? It fails after/during: (II) Loading /usr/X11R6/lib/modules/libpcidata.a On my i386 box: (II) LoadModule: scanpci comes later, so its not scanpci? locate or find shows that libpcidata.a is indeed built in the scanpci directory. Shouldnt it be enough to just jet it return silently? There is nothing to scan here, What about the m68k machines that do have PCI? Mine hasn't, somebody with a m68k/pci machine (if they exist at all?) can do that. Actually, I did not get _any_ feedback from debian-68k users on these packages. What shall I do, buy me all sorts of m68k machines to test it myself? No, of course not. But be prepared for those you ignore to cry up sooner or later. :) The code is the best documentation ;) _This_ code is hughe... I am not going to read it completely... The modules are rather self contained. 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
Re: Tracking XFree86 CVS on a Potato system
* Juliusz Chroboczek [EMAIL PROTECTED] [001211 10:30]: First of all, I'd like to know whether building Branden's packages on a Potato system yields a usable version of XFree86. Thanks for the note about not needing CC:s. I never know when I see posts from new people. :) You can indeed build Branden's packages for potato, but Charl P. Botha has done this already! I submitted the URL he gave for this a while ago to google, so it should be able to find him and his packages without effort. (It would also be in the archives, but that takes more effort to search than google. :) Of course, I don't know if he tracks Branden as quickly as Branden tracks CVS -- so, Charl also wrote a quick description on building the 4.0.1 source packages Branden makes on potato. But, if you are truly making this a development box, why not go all out, and run woody, what with its often updates to everything? :) -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.''
Re: Tracking XFree86 CVS on a Potato system
On Mon, Dec 11, 2000 at 11:37:58AM -0800, Seth Arnold wrote: * Juliusz Chroboczek [EMAIL PROTECTED] [001211 10:30]: First of all, I'd like to know whether building Branden's packages on a Potato system yields a usable version of XFree86. You can indeed build Branden's packages for potato, but Charl P. Botha has done this already! I submitted the URL he gave for this a while ago to google, so it should be able to find him and his packages without effort. (It would also be in the archives, but that takes more effort to search than google. :) The potato xfree86 4.0.1 packages are apt-able with the following lines: deb http://people.debian.org/%7Ecpbotha/ xf401_potato/i386/ deb http://people.debian.org/%7Ecpbotha/ xf401_potato/all/ Of course, I don't know if he tracks Branden as quickly as Branden tracks CVS -- so, Charl also wrote a quick description on building the 4.0.1 source packages Branden makes on potato. I don't track him that quickly... on average I build every 2nd or 3d release that he makes. I'm planning a potato build of 4.0.1-11 as soon as that's in woody for a day or two. The ones that are apt-able at the moment are -8, and I find them rock-solid on my hardware. You can also find the howto on this at http://cpbotha.net/building_woody_xfree86_4.0.1_debs_on_potato.HOWTO -- charl p. botha | computer graphics and cad/cam http://cpbotha.net/ | http://www.cg.its.tudelft.nl/
Re: status on the donated blue white G3
On Dec 11, Branden Robinson [EMAIL PROTECTED] wrote:
Dan, are you *sure* we don't need an autobuilder? Not even for some
subsection of the archive? How about contrib? :)
If needed, I can set up an autobuilder on the B50 I'm installing and
which will become the new {ftp,http}.it.debian.org.
--
ciao,
Marco
Re: quick fix for building nvidia xfree4 drivers on kernel 2.4.0-test11
i saw on on tomshardware site that worked for 2.2 is it essentialy the same for 2.4? i'm currently running xf4, kernel 2.4.0-test10 with NVidia's own accellerated drivers (hell, this is what graphics speed supposed to be ;) You could fetch the latest driver (0.9.5) and insert Mads Buus Jensen's code snippet in nv.h (as he suggested - THANKS for the quick'n'dirty fix). AND you should edit the Makefile to include -DKERNEL_2_3 within the compiler flags (think he forgot that one)
Re: building xfree86 4 for debian/arm
Peter == Peter Maydell [EMAIL PROTECTED] writes: Peter I tried putting together some patches based on a Peter combination of the 3.x ARM patches and the 4.0 patches for Peter other non-x86 architectures; it's now falling over with a Peter compile error in elfloader.c. It looks like the dynamic Peter loader has no ARM support at all, and I don't think I can Peter get away with just adding || defined(__arm__) to cpp Peter conditionals for this one :- I have been playing with this for the last couple of weeks. After getting elfloader.c to compile with the most common relocation types (R_ARM_ABS32, R_ARM_REL32, R_ARM_PC24) defined, there are still a couple outstanding: (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a Elf_RelocateEntry() Unsupported relocation type 56 Elf_RelocateEntry() Unsupported relocation type 24 24 happens to be: #define R_ARM_GOTOFF24 /* 32 bit offset to GOT */ By itself this is pretty odd, but #56 is simply not defined in /usr/include/elf.h at all. I am rebuilding right now (a 10-hour process) with Elf_Rel rather than Elf_Rela setup, to see if that makes a difference. (Seing that ARM, like i386, unlike any of the other processors, is Little Endian). Peter I've temporarily put my patches-so-far at: Peter http://www.chiark.greenend.org.uk/~pmaydell/misc/patches.txt Peter if anybody else is interested. (NB that in particular the Peter list of 'which drivers to build' in xfree86.cf is totally Peter guesswork...) Framebuffer stuff. I have changed the section that starts with: #if defined(PpcArchitecture) || defined(Mc68020Architecture) to #if defined(PpcArchitecture) || defined(Mc68020Architecture) || \ defined(Arm32Architecture) -tor -- Får i ulveklær
Re: quick fix for building nvidia xfree4 drivers on kernel 2.4.0-test11
thanks! sounds like agreat idea, but im fairly new to this so editing the complier flags would be a bit too much for me (now) mind showing me what this would look like? g On Mon, 11 Dec 2000, Raphael Deimel wrote: Date: Mon, 11 Dec 2000 23:49:40 +0100 From: Raphael Deimel [EMAIL PROTECTED] To: dude [EMAIL PROTECTED] Cc: debian-x Mailing List debian-x@lists.debian.org Subject: Re: quick fix for building nvidia xfree4 drivers on kernel 2.4.0-test11 Resent-From: debian-x@lists.debian.org i saw on on tomshardware site that worked for 2.2 is it essentialy the same for 2.4? i'm currently running xf4, kernel 2.4.0-test10 with NVidia's own accellerated drivers (hell, this is what graphics speed supposed to be ;) You could fetch the latest driver (0.9.5) and insert Mads Buus Jensen's code snippet in nv.h (as he suggested - THANKS for the quick'n'dirty fix). AND you should edit the Makefile to include -DKERNEL_2_3 within the compiler flags (think he forgot that one) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: quick fix for building nvidia xfree4 drivers on kernel 2.4.0-test11
If the Makefile was written well, it will be simple. Open the Makefile with your favorite editor (vim is mine! :) and look for lines similar to -DSOMETHING. Add the -DKERNEL_2_3 bit to this line. Or, if there isn't something that looks right, see if there is a CCFLAGS line -- and add the -DKERNEL_2_3 flag there. HTH :) * dude [EMAIL PROTECTED] [001211 16:59]: thanks! sounds like agreat idea, but im fairly new to this so editing the complier flags would be a bit too much for me (now) mind showing me what this would look like? g On Mon, 11 Dec 2000, Raphael Deimel wrote: Date: Mon, 11 Dec 2000 23:49:40 +0100 From: Raphael Deimel [EMAIL PROTECTED] To: dude [EMAIL PROTECTED] Cc: debian-x Mailing List debian-x@lists.debian.org Subject: Re: quick fix for building nvidia xfree4 drivers on kernel 2.4.0-test11 Resent-From: debian-x@lists.debian.org i saw on on tomshardware site that worked for 2.2 is it essentialy the same for 2.4? i'm currently running xf4, kernel 2.4.0-test10 with NVidia's own accellerated drivers (hell, this is what graphics speed supposed to be ;) You could fetch the latest driver (0.9.5) and insert Mads Buus Jensen's code snippet in nv.h (as he suggested - THANKS for the quick'n'dirty fix). AND you should edit the Makefile to include -DKERNEL_2_3 within the compiler flags (think he forgot that one) -- 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] -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.''
Re: debian-changelog-mode
[EMAIL PROTECTED] wrote: Hm. I thought I had cut and pasted it from dpkg -s dpkg-dev. I guess I must be wrong, or else Branden is really really evil, evil enough to put special misspell the DPL's name hooks in the X selection code. That is a beautiful idea. Overfiend: CuLUs!! -- see shy jo
[mongoose@users.sourceforge.net: X upgrade policy]
- Forwarded message from Terry 'Mongoose' Hendrix II [EMAIL PROTECTED] - From: Terry 'Mongoose' Hendrix II [EMAIL PROTECTED] To: Branden Robinson [EMAIL PROTECTED] Subject: X upgrade policy Date: Mon, 11 Dec 2000 16:05:35 -0500 (EST) Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Sender: [EMAIL PROTECTED] Reply-To: Terry 'Mongoose' Hendrix [EMAIL PROTECTED] In-Reply-To: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Why have you made the upgrade path in X impossible? You can't run utah on 4.0 - yet you blindly install 4.0 over every system by dependcies. You don't even bother checking /proc to see what card is installed. A simple grep of /proc/pci shows I have an AGP G400, not a V3! I have a machine that has half 3.3.6-18 and 4.0 installed now - and I had the utah package installed! You should check for utah before 'upgrading' blindly over it. I told you people not to do this - 3d accel is very important - you shouldn't dissmiss it outright. I'm having to reinstall all my X libs and applications now, and I can't develop my projects while fixing your mistakes. cheers, Terry --- | GooseEgghttp://gooseegg.sourceforge.net | | QuakeForge http://www.quakeforge.net | | Personalhttp://www.westga.edu/~stu7440| | | | Dream is running Debian GNU/Linux| --- - End forwarded message - -- G. Branden Robinson| The greatest productive force is human Debian GNU/Linux | selfishness. [EMAIL PROTECTED] | -- Robert Heinlein http://deadbeast.net/~branden/ | pgpWKwjAcmB6U.pgp Description: PGP signature
[kteague@sprocket.ddts.net: xserver-xsun drivers]
Does anyone know which driver the TurboGX uses? - Forwarded message from Ken Teague [EMAIL PROTECTED] - From: Ken Teague [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: xserver-xsun drivers Date: Mon, 11 Dec 2000 13:29:55 -0800 Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Message-Id: [EMAIL PROTECTED] Hi Branden, sorry to bother you like this. I'm running Debian Sparc (woody) and can't find a listing of which driver to use for X with my TURBOXGX SBus card. I also checked www.xfree86.org but they don't list it either. Can you please point me to where I can find information about which driver I need for my frame buffer card? Thanks. - Ken - End forwarded message - -- G. Branden Robinson|Somewhere, there is a .sig so funny that Debian GNU/Linux |reading it will cause an aneurysm. This [EMAIL PROTECTED] |is not that .sig. http://deadbeast.net/~branden/ | pgp3AA50uBAyF.pgp Description: PGP signature
[bossart@deesse.univ-lemans.fr: xfree86]
- Forwarded message from Romain Bossart [EMAIL PROTECTED] - From: Romain Bossart [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: xfree86 Date: Mon, 11 Dec 2000 17:36:44 +0100 (CET) Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Hi, I got a problem when I upgraded my xfree86 to the 4.0.1-10 version, the server doesn't start, and I get this message ; X: user not authorized to run the X server, aborting. what can I do to make it work again ? thank you -- ++ | Romain Bossart - Laboratoire d'Acoustique - LAUM-UMR CNRS 6613 | | Universite du Maine - av. O. Messiaen - 72000 Le Mans (France) | | tel: 02 43 83 36 18 fax: 02 43 83 35 20 | | http://www.univ-lemans.fr[EMAIL PROTECTED] | ++ - End forwarded message - -- G. Branden Robinson|It was a typical net.exercise -- a Debian GNU/Linux |screaming mob pounding on a greasy spot [EMAIL PROTECTED] |on the pavement, where used to lie the http://deadbeast.net/~branden/ |carcass of a dead horse. pgp3vSVELdzTj.pgp Description: PGP signature
[harri@synopsys.COM: gdm and kdm can't start X]
Not sure what the problem is here; I don't know what would make the X server become a zombie process. - Forwarded message from Harald Dunkel [EMAIL PROTECTED] - From: Harald Dunkel [EMAIL PROTECTED] To: Branden Robinson [EMAIL PROTECTED] Subject: gdm and kdm can't start X Date: Mon, 11 Dec 2000 20:30:59 +0100 Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.0-test11 i586) X-Accept-Language: en Hi Branden After the last update of XFree 4.0.1 gdm and kdm stopped working. The XServer doesn't come up. 'ps -ef' shows me '[ X defunct ]'. Is this an installation problem? Regards Harri -- Harald Dunkel | [EMAIL PROTECTED] | Against stupidity the very gods Synopsys GmbH | Kaiserstr. 100 | Themselves contend in vain. 52134 Herzogenrath, Germany | +49 2407 9558 (fax? 44: 0) | Schiller, The Maid of Orleans - End forwarded message - -- G. Branden Robinson|Men use thought only to justify their Debian GNU/Linux |wrong doings, and speech only to conceal [EMAIL PROTECTED] |their thoughts. http://deadbeast.net/~branden/ |-- Voltaire pgpYlqEezyV85.pgp Description: PGP signature
Re: [mongoose@users.sourceforge.net: X upgrade policy]
Terry, a few quick comments -- first, Utah-glx is in the past. While their work may have been nifty at one point, and for people running 3.3.x perhaps necessary, XF 4.0.1 has a *much* easier GL system. Second, I'm not sure what you mean by ``I have a g400, not a v3'' -- last time I ran the dexter program, it did not automatically assume I had any type of video card -- rather, it allowed me to select my g400 from a list. But then, I haven't run dexter lately. Third, welcome to life running Debian unstable. :) If you want nice stable operating, run potato. It is very good. If you want the latest and greatest (including XF4.0.1's much improved GLX support), then running woody is just fine -- though there will be bumps along the way. Those bumps are part of running woody, until it is declared stable. (Well, heck, bumps might happen then too, but we try to minimize them. :) Fourth, there is no pressing need to email Branden directly -- he is awful busy. Using lists such as debian-user (for most X questions) or debian-x (for questions specific to the debian packaging of X) will usually get responses much faster. Cheers! :) * Branden Robinson [EMAIL PROTECTED] [001211 19:35]: - Forwarded message from Terry 'Mongoose' Hendrix II [EMAIL PROTECTED] - From: Terry 'Mongoose' Hendrix II [EMAIL PROTECTED] To: Branden Robinson [EMAIL PROTECTED] Subject: X upgrade policy Date: Mon, 11 Dec 2000 16:05:35 -0500 (EST) Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Sender: [EMAIL PROTECTED] Reply-To: Terry 'Mongoose' Hendrix [EMAIL PROTECTED] In-Reply-To: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Why have you made the upgrade path in X impossible? You can't run utah on 4.0 - yet you blindly install 4.0 over every system by dependcies. You don't even bother checking /proc to see what card is installed. A simple grep of /proc/pci shows I have an AGP G400, not a V3! I have a machine that has half 3.3.6-18 and 4.0 installed now - and I had the utah package installed! You should check for utah before 'upgrading' blindly over it. I told you people not to do this - 3d accel is very important - you shouldn't dissmiss it outright. I'm having to reinstall all my X libs and applications now, and I can't develop my projects while fixing your mistakes. cheers, Terry --- | GooseEgghttp://gooseegg.sourceforge.net | | QuakeForge http://www.quakeforge.net | | Personalhttp://www.westga.edu/~stu7440| | | | Dream is running Debian GNU/Linux| --- - End forwarded message - -- G. Branden Robinson| The greatest productive force is human Debian GNU/Linux | selfishness. [EMAIL PROTECTED] | -- Robert Heinlein http://deadbeast.net/~branden/ | -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.''
Re: [harri@synopsys.COM: gdm and kdm can't start X]
Would the /etc/X11/Xwrapper.config file affect gdm or kdm? * Branden Robinson [EMAIL PROTECTED] [001211 19:46]: Not sure what the problem is here; I don't know what would make the X server become a zombie process. - Forwarded message from Harald Dunkel [EMAIL PROTECTED] - From: Harald Dunkel [EMAIL PROTECTED] To: Branden Robinson [EMAIL PROTECTED] Subject: gdm and kdm can't start X Date: Mon, 11 Dec 2000 20:30:59 +0100 Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.0-test11 i586) X-Accept-Language: en Hi Branden After the last update of XFree 4.0.1 gdm and kdm stopped working. The XServer doesn't come up. 'ps -ef' shows me '[ X defunct ]'. Is this an installation problem? Regards Harri -- Harald Dunkel | [EMAIL PROTECTED] | Against stupidity the very gods Synopsys GmbH | Kaiserstr. 100 | Themselves contend in vain. 52134 Herzogenrath, Germany | +49 2407 9558 (fax? 44: 0) | Schiller, The Maid of Orleans - End forwarded message - -- G. Branden Robinson|Men use thought only to justify their Debian GNU/Linux |wrong doings, and speech only to conceal [EMAIL PROTECTED] |their thoughts. http://deadbeast.net/~branden/ |-- Voltaire -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.''
Re: [mongoose@users.sourceforge.net: X upgrade policy]
Not to mention that the G400 driver for XFree 4 has 3D acceleration as well. It's currently kinda broken (stencils don't work at all (not even in software fallback - they're borked), and there are some pretty icky persistent texturing bugs, but it's usable. Just not very. Personally, I'm annoyed by the persistent brokenness of the DRI drivers, but I'm making do in my projects, and if I want to verify my code's correctness I can always use an LD_PRELOAD to force software mesa to check accuracy. It would be nice if the XFree 4 packages had a 'Conflicts: utah-glx' in it, but as has been said already, you ARE running Debian *usntable*, and you reap what you sow in that regard... don't take it out on Branden, please. -- Joshua Shagam /\ ASCII Ribbon Campaign [EMAIL PROTECTED] \ / No HTML/RTF in email www.cs.nmsu.edu/~joshagam X No Word docs in email mp3.com/fluffyporcupine/ \ Respect for open standards
Re: [bossart@deesse.univ-lemans.fr: xfree86]
you need to reconfigure xserver-common i believe you cant 'apt-get --reconfigure xserver-common' and select 'anybbody' to starts windows. if that is wrong go to irc.debian.org room: #debian and look at the topic which will give you the answer ~ On Mon, 11 Dec 2000, Branden Robinson wrote: Date: Mon, 11 Dec 2000 22:46:55 -0500 From: Branden Robinson [EMAIL PROTECTED] To: debian-x@lists.debian.org Subject: [EMAIL PROTECTED]: xfree86] Resent-From: debian-x@lists.debian.org - Forwarded message from Romain Bossart [EMAIL PROTECTED] - From: Romain Bossart [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: xfree86 Date: Mon, 11 Dec 2000 17:36:44 +0100 (CET) Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Hi, I got a problem when I upgraded my xfree86 to the 4.0.1-10 version, the server doesn't start, and I get this message ; X: user not authorized to run the X server, aborting. what can I do to make it work again ? thank you -- ++ | Romain Bossart - Laboratoire d'Acoustique - LAUM-UMR CNRS 6613 | | Universite du Maine - av. O. Messiaen - 72000 Le Mans (France) | | tel: 02 43 83 36 18 fax: 02 43 83 35 20 | | http://www.univ-lemans.fr[EMAIL PROTECTED] | ++ - End forwarded message - -- G. Branden Robinson|It was a typical net.exercise -- a Debian GNU/Linux |screaming mob pounding on a greasy spot [EMAIL PROTECTED] |on the pavement, where used to lie the http://deadbeast.net/~branden/ |carcass of a dead horse.
