On Sun, Oct 22, 2000 at 07:48:40PM -0700, Steve Bowman wrote: > On Mon, Oct 23, 2000 at 03:30:56AM +0200, Marcus Brinkmann wrote: > > On Sun, Oct 22, 2000 at 05:22:11PM -0700, Steve Bowman wrote: > > > I had some problems with X 3.3.6 on cvs hurd last night I was going > > > to report, then your message arrived so I'll combine that report with > > > my response.... > > > > Okay, let's see... > > > [snip] > > > > I don't know which CVS you mean, so I don't know which sources you actually > > compiled. > > export CVSROOT=:pserver:[EMAIL PROTECTED]:/cvs > cd .../hurd > cvs update > > updated 20001020 at 21:02 MST (GMT -0700)
Ah, I thought you were recompiling X... this explains a lot of my confusion, sorry :) > > > I'm wondering if there's something going on with the hurd that X is > > > triggering. What's changed since the 20000921 hurd except the tunnel > > > changes? > > > > Nothing. I suspect that your build is broken, but I don't know which sources > > you actually compiled. No official source or repository I know of carries my > > patches. > > Just hurd cvs. The X 3.3.6 packages were the standard debs available > on the mirrors. Your patches are just for X right, no uncommited hurd > patches? Well, I changed mainly (only?) pfinet, and that's certainly unrelated if you don't use TCPCONN, and even then. I will have to patch the mouse translator, and maybe fix the kbd translator, but kbd is mostly usable and mouse is broken in X as well, so go figure. > > > I haven't tried restoring the old hurd yet to verify that X works again, > > > but I actually did the same thing last weekend and restoring the old > > > (0921) hurd cured X. I didn't report it yet because I wanted to rebuild > > > and reinstall hurd to make sure the problem wasn't there. AFAICT, > > > it's a clean build except as noted in [1]. > > > > Mmmh. If you really can verify that it works with the 0921 hurd, but not > > with your new one, I will retract what I said above :) > > Verified. X 3.3.6 works with 0921 hurd but not with cvs hurd. > I just retested X (failed), downgraded hurd, and retested X (success). > An extract of the X output log is in [1]. This time, the failed X test > went a little differently. I didn't try to see what would happen on > a restart so I didn't get the "X is already running" error and such. > I was just trying to confirm the same X worked on 0921 and not on cvs > (20001020) hurd. That looks quite bad. Seems your Hurd build went hovac. I never saw something like this, but I didn't test the recent CVS in full, only pfinet. I will prepare a new Debian Hurd package soon, and then I'll see if I can reproduce that. Try replacing only the /hurd/lbd translator, if that's the culprit. > > I have something better, the 4.0 patch, see above. All of the upstream > > related changes in the 3.3.6 patch are integrated. BTW, this patch is for > > the official 401 tar file, not for the Debian source. I don't have the > > Debian source here currently, so I can't work from that. Will do it tomorrow > > or later this week. But progress is steady, and I am not concerned about the > > Debian packaging, it's not hard. What needs work is the display and mouse > > stuff, and if you can help fixing that, great. But if you don't have much > > time, I'll probably beat you to that because I really want to push this > > through. > > OK. I'll see about downloading 401 tonight and try your patch if I can > find room to build it. My hurd partition is starting to get full, so > I'll try building into an nfs-mounted partition which has more space. > (My local ext2fs partitions are too big to use :-( but nfs-mounted > partitions don't seem to have that limit :-).) Just as a guideline: du xc ... 227360 xc That's a full build without debugging symbols. I checked the cvs logs, but they don't reveal much. David Dawes frobbed the Hurd mouse handling code, and if we can't resolve it, I will contact him for help. But we should at least make an honest attempt to fix it ourselve. I saw my card is not supported under X4.0 (Trio64). I still don't know if the vga part should work anyway. > > My primary goal is to get the upstream source in shape and commit the patch > > to the X group and Branden. Then the Debian packaging will be adjusted. > > ACK, I'll see if I can keep up with you :-). First I have to catch up.... I will get some sleep now, so you have some time to do it :) > Fatal server error: > Cannot set event mode on keyboard (Inappropriate ioctl for device) That indicates some /dev/kbd problem. > Fatal server error: > can't reset keyboard mode (Inappropriate ioctl for device) > > ----- Stop Cut ----- > Then several thousand lines of the same before I got the server shut down. It should really try once and fail entirely... Thanks, Marcus -- `Rhubarb is no Egyptian god.' Debian http://www.debian.org [EMAIL PROTECTED] Marcus Brinkmann GNU http://www.gnu.org [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.marcus-brinkmann.de
