Re: XFree 4.2.1 doesn't work with last CURRENT
Aurelien Nephtali wrote: On Mon, Dec 23, 2002 at 12:18:45AM +0100, Jens Rehsack wrote: Aurelien Nephtali wrote: Hi, I've upgraded from 4.2.0 to 4.2.1 and now X11 doesn't want to start :/ I've attached the error log. Any help would be appreciated :) -- Aurelien 1) How did you upgrade? 2) What's the name of your machine? I've upgraded using 'portupgrade' tool and my box is a Celeron 700 running on -CURRENT. -- Aurelien portupgrade and what kind of parameters? Send me please following outputs: 'pkg_info' 'dmesg' 'ifconfig -a' 'cat /etc/make.conf' 'cat /etc/rc.conf' I don't care if you're using a i486SX-33 or a Athlon-MP 2.2+ GHz Dual Box, the relevant information is the name of your machine. Please send me the output of previously requested commands. Jens -- L i W W W i Jens Rehsack LW W W L i W W W W i nnnLiWing IT-Services L iW W W Wi n n g g i W W i n n g gFriesenstraße 2 06112 Halle g g g Tel.: +49 - 3 45 - 5 17 05 91ggg e-Mail: <[EMAIL PROTECTED]> Fax: +49 - 3 45 - 5 17 05 92http://www.liwing.de/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree 4.2.1 doesn't work with last CURRENT
> On Mon, 23 Dec 2002 10:11:29 +0100, Aurelien Nephtali ><[EMAIL PROTECTED]> said: >> >I've upgraded from 4.2.0 to 4.2.1 and now X11 doesn't want to start :/ >> >I've attached the error log. >> > >> 1) How did you upgrade? >> 2) What's the name of your machine? >> Aurelien> I've upgraded using 'portupgrade' tool and my box is a Celeron 700 running on Aurelien> -CURRENT. Hi, Do a 'portupgrade -f wrapper' and try starting X. HTH Regards Sid -- Do what comes naturally now. Seethe and fume and throw a tantrum. Sid Carter - http://khader.net/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree 4.2.1 doesn't work with last CURRENT
On Mon, Dec 23, 2002 at 12:18:45AM +0100, Jens Rehsack wrote: > Aurelien Nephtali wrote: > >Hi, > > > >I've upgraded from 4.2.0 to 4.2.1 and now X11 doesn't want to start :/ > >I've attached the error log. > > > >Any help would be appreciated :) > > > >-- Aurelien > > 1) How did you upgrade? > 2) What's the name of your machine? > I've upgraded using 'portupgrade' tool and my box is a Celeron 700 running on -CURRENT. -- Aurelien msg49228/pgp0.pgp Description: PGP signature
Re: XFree 4.2.1 doesn't work with last CURRENT
Aurelien Nephtali wrote: Hi, I've upgraded from 4.2.0 to 4.2.1 and now X11 doesn't want to start :/ I've attached the error log. Any help would be appreciated :) -- Aurelien 1) How did you upgrade? 2) What's the name of your machine? -- L i W W W i Jens Rehsack LW W W L i W W W W i nnnLiWing IT-Services L iW W W Wi n n g g i W W i n n g gFriesenstraße 2 06112 Halle g g g Tel.: +49 - 3 45 - 5 17 05 91ggg e-Mail: <[EMAIL PROTECTED]> Fax: +49 - 3 45 - 5 17 05 92http://www.liwing.de/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree 4.2.1 doesn't work with last CURRENT
Hi Aurelien I was able to get X running once I recompiled (the server) with -fno-merge-constants. Unfortunately, I do not know if it has anything to do with the GCC ABI issue. Aurelien Nephtali wrote: Hi, I've upgraded from 4.2.0 to 4.2.1 and now X11 doesn't want to start :/ I've attached the error log. Any help would be appreciated :) -- Aurelien -- Regards Peter As always the organisation disavows knowledge of this email To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
XFree 4.2.1 doesn't work with last CURRENT
Hi, I've upgraded from 4.2.0 to 4.2.1 and now X11 doesn't want to start :/ I've attached the error log. Any help would be appreciated :) -- Aurelien Script started on Sun Dec 22 22:34:05 2002 [m[27m[Jnebula% [K[70C~[71Dsstartx xauth: (argv):1: bad display name "nebula.wanadoo.fr:0" in "list" command xauth: (argv):1: bad display name "nebula.wanadoo.fr:0" in "add" command XFree86 Version 4.2.1 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 3 September 2002 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/) Build Operating System: FreeBSD 5.0-CURRENT i386 [ELF] Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.0.log", Time: Sun Dec 22 22:34:07 2002 (==) Using config file: "/etc/X11/XF86Config" Not loading .rodata.str1.32 Not loading .rodata.str1.1 Not loading .rodata.cst8 Not loading .rodata.str1.1 Not loading .rodata.str1.32 Not loading .rodata.str1.32 Not loading .rodata.str1.1 Not loading .rodata.cst8 Not loading .rodata.str1.32 Not loading .rodata.str1.1 Not loading .rodata.str1.32 Not loading .rodata.str1.1 Not loading .rodata.str1.32 Not loading .rodata.str1.32 Not loading .rodata.str1.1 Not loading .rodata.str1.32 Not loading .rodata.str1.1 Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved!Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a is unresolved! Symbol from module /usr/X11R6/lib/modules/libbitmap.a
Re: XFree
On Fri, 8 Nov 2002, Terry Lambert wrote: > Horen wrote: > > Now the missing facts: > > > >4.x binaries will not run on 5.0, lib.c inconsistency. > > You are not running the most recent 5.x. We can't help you, I > think. > > > >Identical XFree86 sources compiled nativly on 4.6, 4.7 and 5.0. > >4.6-4.7: no problem > >5.0: logout from X blocks the graphic card, Matrox MGA 400 > > and also Nvidia GeForce2 MX200 > > Different compilers. You have failed to narrow the problem down; > here's where it might be: > > 1)In the configuration code > 2)In the difference in the patches between the versions of > the ports tree for X11 > 3)In the X11 libraries' handling of threads > 4)In the 5.x implementation of pthreads > 5)In the GCC compiler optimizer > 6)In the GCC compiler code generator > 7)In the X11 source code; there are certain assumptions > that the new compiler makes which it was always permissable > for it to make, but which the old compiler did not make, > even though it was allowed to (i.e. a revealed bug in the > X11 sources) > 8)A bug in the AGP (/dev/agpart) code > 9)A bug in the ACPI handling of monitor power-down code > 10) A bug in the ACPI BIOS information of your computer itself > 11) In a mismatch between kernel and kernel module versions > 12) In a difference in the values of manifest constants > > > I doubt, that something else than OS related issues are the > > cause. > > Doubt it all you want; from the small amount of information you > have provided us, it looks to me like there is a possibility > that it's 50% non-OS-releated. > > > > Switched back to 4.7 , will try again 5.0 in few weeks. > > If it happens again, be sure and give us useful information, > like: > > o Since Warner fixed the libc incompatabilities, have > you installed the 4.7 version of X11 on 5.x, and does > the problem still happen? Yes, it happened, I didn't make notes exact which version of X11 it was. 4.7 was updated on 11/1/2002 > o Does it happen if ACPI isn't loaded? Didn't test it. > o Does it happen with the Xvga server, or only with the > accelerated server? It happens with both server. > o Are you on a laptop or a desktop? It's a desktop with following hardware configuration: Tyan Thunder K7 (S2462) Motherboard ( with onboard ATI graphic chip ) not used Intel MultiProcessor Specification v1.4 activated 2 G Ram 2 x Athlon 2000+ Gr. Cards tested Matrox MGA400 Max and Nvidia GeForce2 MX200 2 IBM SCSI HD ( each 36 G ) Monitor Sony GDM F520 > o If a desktop, does turning the monitor off and back on > "fix" the problem for you? No, only a reboot. > o What the checkout date for your 5.x source tree? It's > unlikely that someone would be willing to spend 30 hours Last checkout 11/7/2002. -Horen > duplicating your test environment, but you never know... > o The results of any discriminating tests for the possible > causes, per the list, earlier in this email. > > Thanks, > -- Terry > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree
Horen wrote: > Now the missing facts: > >4.x binaries will not run on 5.0, lib.c inconsistency. You are not running the most recent 5.x. We can't help you, I think. >Identical XFree86 sources compiled nativly on 4.6, 4.7 and 5.0. >4.6-4.7: no problem >5.0: logout from X blocks the graphic card, Matrox MGA 400 > and also Nvidia GeForce2 MX200 Different compilers. You have failed to narrow the problem down; here's where it might be: 1) In the configuration code 2) In the difference in the patches between the versions of the ports tree for X11 3) In the X11 libraries' handling of threads 4) In the 5.x implementation of pthreads 5) In the GCC compiler optimizer 6) In the GCC compiler code generator 7) In the X11 source code; there are certain assumptions that the new compiler makes which it was always permissable for it to make, but which the old compiler did not make, even though it was allowed to (i.e. a revealed bug in the X11 sources) 8) A bug in the AGP (/dev/agpart) code 9) A bug in the ACPI handling of monitor power-down code 10) A bug in the ACPI BIOS information of your computer itself 11) In a mismatch between kernel and kernel module versions 12) In a difference in the values of manifest constants > I doubt, that something else than OS related issues are the > cause. Doubt it all you want; from the small amount of information you have provided us, it looks to me like there is a possibility that it's 50% non-OS-releated. > Switched back to 4.7 , will try again 5.0 in few weeks. If it happens again, be sure and give us useful information, like: o Since Warner fixed the libc incompatabilities, have you installed the 4.7 version of X11 on 5.x, and does the problem still happen? o Does it happen if ACPI isn't loaded? o Does it happen with the Xvga server, or only with the accelerated server? o Are you on a laptop or a desktop? o If a desktop, does turning the monitor off and back on "fix" the problem for you? o What the checkout date for your 5.x source tree? It's unlikely that someone would be willing to spend 30 hours duplicating your test environment, but you never know... o The results of any discriminating tests for the possible causes, per the list, earlier in this email. Thanks, -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree
On Fri, 8 Nov 2002, Horen wrote: > On Thu, 7 Nov 2002, Terry Lambert wrote: > > > Horen wrote: > > > On FreeBSD 4.6 or 4.7 works, on FreeBSD 5.0 it doesn't work. > > > Don't you think it is OS related. ? > > > > THere are a lot of MS-DOS programs that won't run on FreeBSD; > > I don't think that's FreeBSD-related, I think it's the code > > doing the wrong things to run on FreeBSD. > The purpose of trying FreeBSD 5.0 was to test development code. I'm positive, few MS-DOS programs won't run on FreeBSD, probably some Mac OS 7 - 9 programs either. I'm doing nms development on unix (spec. BSD) for a very long while, didn't use it to test if MS Office will run. Now the missing facts: 4.x binaries will not run on 5.0, lib.c inconsistency. Identical XFree86 sources compiled nativly on 4.6, 4.7 and 5.0. 4.6-4.7: no problem 5.0: logout from X blocks the graphic card, Matrox MGA 400 and also Nvidia GeForce2 MX200 I doubt, that something else than OS related issues are the cause. Switched back to 4.7 , will try again 5.0 in few weeks. Thanks, -Horen > > > > > > I even installed Linux RedHat 8.0 ( gcc 3.2x ) code. It works. > > > Only on FreeBSD 5,0 , it doesn't work. > > > > Have you tried running the 4.x binaries on 5.x, or are you > > running different binaries? It could be that the code is > > broken in a way that exercises a complier error; 5.x uses a > > different compiler than 4.x. > > > > I would recommend you install the 4.x binaries on 5.x, rather > > than running 5.x binaries. > > > > If the binaries are exactly the same, then I will be willing > > to blame the OS, even though you are one of the few persons > > who are running into problems. > > > > As far as root cause analysis goes, you've given us a report > > that looks like "it doesn't work". If you can make it so that > > the only thing that has changed is the OS, then it willbe much > > easier to blame the OS. > > > > I'm still not sure that it isn't the AGP driver being different. > > > > Have you tried an unaccelerated X server? I'm talking "Xvga", > > not just turning off the acceleration in the config file... > > > > -- Terry > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree
Horen <[EMAIL PROTECTED]> writes: > Posted a week ago the question, didn't get any reaction. > > Everything with current from last night works fine but killing > X or logging out ends in a black screen. No way to activate the > display without reboot. Remote login is fine. Typing blind works > too. I had similar problem when I upgraded to -current in september. I was using 800x600 VESA mode console at that time, and I found that removing SC_PIXEL_MODE from kernel, and returning back to the good old text mode solved problem for me. I have a G450. -- Krzysztof Jędruczyk To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree
Horen wrote: > On FreeBSD 4.6 or 4.7 works, on FreeBSD 5.0 it doesn't work. > Don't you think it is OS related. ? > > I even installed Linux RedHat 8.0 ( gcc 3.2x ) code. It works. > Only on FreeBSD 5,0 , it doesn't work. Install X from FreeBSD 4.6 or 4.7 on FreeBSD 5.0... plain enough? -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree
On Thu, Nov 07, 2002 at 05:02:14PM -0800, Terry Lambert wrote: > Horen wrote: > > > You stated "Typing blind starts X again". > > > > > > Can you tell us what you mean by this? > > > > > > o It restarts X, as if you typed "startx" > > > > Exactly that. > > The problem is clearly in the X11 code, then, since it is not > resetting the card to the video mode it was in before X started. > > You would do well to look at the XFree86 mailing list archives, > since your answer is likely to be there (this is not a FreeBSD > specific problem, if it is not happening because of FreeBSD > specific code). > > The only possible way this could be a FreeBSD specific problem > is if you were using, e.g., the AGP driver, and it wasn't working. I have exactly the same problem with 2 Millenium cards on an HX chipset board (Socket 7) - no AGP. But my XFree is rather old 4.2.0_1,1 from 16th Jun and I also prefer not to restart my xsessions so I never mentioned. -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree
Horen wrote: > > XFree86-Server-4.2.1_5 XFree86-4 X server and related programs > > Do you think, it makes sense, that I grab an other version, > 4.2.0 or even 4.1.x to check ? No, I think the source code version is much less relevent than the platform and compiler which was used to compile the X11 binaries. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree
Horen wrote: > > > X has exited cleanly only on 4.6 or 4.7 , never on 5.0 in the > > Exact same version of the X Server (pkg_info | grep XFree86-Server)? > XFree86-Server-4.2.1_5 XFree86-4 X server and related programs That's the version of the source code. Are you running the same binaries? Or were the broken binaries compiled on 5.x, with the new C compiler, etc.? -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree
Horen wrote: > On FreeBSD 4.6 or 4.7 works, on FreeBSD 5.0 it doesn't work. > Don't you think it is OS related. ? THere are a lot of MS-DOS programs that won't run on FreeBSD; I don't think that's FreeBSD-related, I think it's the code doing the wrong things to run on FreeBSD. > I even installed Linux RedHat 8.0 ( gcc 3.2x ) code. It works. > Only on FreeBSD 5,0 , it doesn't work. Have you tried running the 4.x binaries on 5.x, or are you running different binaries? It could be that the code is broken in a way that exercises a complier error; 5.x uses a different compiler than 4.x. I would recommend you install the 4.x binaries on 5.x, rather than running 5.x binaries. If the binaries are exactly the same, then I will be willing to blame the OS, even though you are one of the few persons who are running into problems. As far as root cause analysis goes, you've given us a report that looks like "it doesn't work". If you can make it so that the only thing that has changed is the OS, then it willbe much easier to blame the OS. I'm still not sure that it isn't the AGP driver being different. Have you tried an unaccelerated X server? I'm talking "Xvga", not just turning off the acceleration in the config file... -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree
> > > On 7 Nov 2002, Eric Anholt wrote: > > > On Thu, 2002-11-07 at 16:56, Horen wrote: > > > > > > > > > > > > On 7 Nov 2002, Eric Anholt wrote: > > > > > > > On Thu, 2002-11-07 at 04:40, Horen wrote: > > > > > > > > > > > > > > > On 6 Nov 2002, Eric Anholt wrote: > > > > > > > > > > > On Wed, 2002-11-06 at 18:34, Horen wrote: > > > > > > > > > > > > > > Posted a week ago the question, didn't get any reaction. > > > > > > > > > > > > > > Everything with current from last night works fine but killing > > > > > > > X or logging out ends in a black screen. No way to activate the > > > > > > > display without reboot. Remote login is fine. Typing blind works > > > > > > > too. > > > > > > > > > > > > How long has this been going on? Did it start at any particular point > > > > > > (a specific kernel or XFree86 upgrade)? What video card do you use? > > > > > > Does starting X again not work? > > > > > > > > > > > > > > > > It started sometimes in Oct, switched back to 4.7 stable. Did yesterday > > > > > an installation from scratch and built XFree86-Server after buildworld. > > > > > > > > I was asking if X has ever exited cleanly to console for you after > > > > logging out, and if it has, what you changed (particularly in your > > > > XFree86-Server version) between when it was working and when it wasn't. > > > > This is most likely just a failure of the driver to properly reset > > > > things for your card. Does disabling DRI in XF86Config help it exit > > > > cleanly? > > > > > > > > > > X has exited cleanly only on 4.6 or 4.7 , never on 5.0 in the > > > last 4-5 weeks. Didn't change anything. I disabled DRI but, didn't > > > help. Work normally with res 1600x1200 , tried 1024x768 to 1920x1440. > > > Nothing changed. > > > > Exact same version of the X Server (pkg_info | grep XFree86-Server)? > > > > XFree86-Server-4.2.1_5 XFree86-4 X server and related programs > Do you think, it makes sense, that I grab an other version, 4.2.0 or even 4.1.x to check ? -Horen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree
On 7 Nov 2002, Eric Anholt wrote: > On Thu, 2002-11-07 at 16:56, Horen wrote: > > > > > > > > On 7 Nov 2002, Eric Anholt wrote: > > > > > On Thu, 2002-11-07 at 04:40, Horen wrote: > > > > > > > > > > > > On 6 Nov 2002, Eric Anholt wrote: > > > > > > > > > On Wed, 2002-11-06 at 18:34, Horen wrote: > > > > > > > > > > > > Posted a week ago the question, didn't get any reaction. > > > > > > > > > > > > Everything with current from last night works fine but killing > > > > > > X or logging out ends in a black screen. No way to activate the > > > > > > display without reboot. Remote login is fine. Typing blind works > > > > > > too. > > > > > > > > > > How long has this been going on? Did it start at any particular point > > > > > (a specific kernel or XFree86 upgrade)? What video card do you use? > > > > > Does starting X again not work? > > > > > > > > > > > > > It started sometimes in Oct, switched back to 4.7 stable. Did yesterday > > > > an installation from scratch and built XFree86-Server after buildworld. > > > > > > I was asking if X has ever exited cleanly to console for you after > > > logging out, and if it has, what you changed (particularly in your > > > XFree86-Server version) between when it was working and when it wasn't. > > > This is most likely just a failure of the driver to properly reset > > > things for your card. Does disabling DRI in XF86Config help it exit > > > cleanly? > > > > > > > X has exited cleanly only on 4.6 or 4.7 , never on 5.0 in the > > last 4-5 weeks. Didn't change anything. I disabled DRI but, didn't > > help. Work normally with res 1600x1200 , tried 1024x768 to 1920x1440. > > Nothing changed. > > Exact same version of the X Server (pkg_info | grep XFree86-Server)? > XFree86-Server-4.2.1_5 XFree86-4 X server and related programs > -- > Eric Anholt <[EMAIL PROTECTED]> > http://people.freebsd.org/~anholt/dri/ > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree
On Thu, 2002-11-07 at 16:56, Horen wrote: > > > > On 7 Nov 2002, Eric Anholt wrote: > > > On Thu, 2002-11-07 at 04:40, Horen wrote: > > > > > > > > > On 6 Nov 2002, Eric Anholt wrote: > > > > > > > On Wed, 2002-11-06 at 18:34, Horen wrote: > > > > > > > > > > Posted a week ago the question, didn't get any reaction. > > > > > > > > > > Everything with current from last night works fine but killing > > > > > X or logging out ends in a black screen. No way to activate the > > > > > display without reboot. Remote login is fine. Typing blind works > > > > > too. > > > > > > > > How long has this been going on? Did it start at any particular point > > > > (a specific kernel or XFree86 upgrade)? What video card do you use? > > > > Does starting X again not work? > > > > > > > > > > It started sometimes in Oct, switched back to 4.7 stable. Did yesterday > > > an installation from scratch and built XFree86-Server after buildworld. > > > > I was asking if X has ever exited cleanly to console for you after > > logging out, and if it has, what you changed (particularly in your > > XFree86-Server version) between when it was working and when it wasn't. > > This is most likely just a failure of the driver to properly reset > > things for your card. Does disabling DRI in XF86Config help it exit > > cleanly? > > > > X has exited cleanly only on 4.6 or 4.7 , never on 5.0 in the > last 4-5 weeks. Didn't change anything. I disabled DRI but, didn't > help. Work normally with res 1600x1200 , tried 1024x768 to 1920x1440. > Nothing changed. Exact same version of the X Server (pkg_info | grep XFree86-Server)? -- Eric Anholt <[EMAIL PROTECTED]> http://people.freebsd.org/~anholt/dri/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree
On Thu, 7 Nov 2002, Terry Lambert wrote: > Horen wrote: > > > You stated "Typing blind starts X again". > > > > > > Can you tell us what you mean by this? > > > > > > o It restarts X, as if you typed "startx" > > > > Exactly that. > > The problem is clearly in the X11 code, then, since it is not > resetting the card to the video mode it was in before X started. > > You would do well to look at the XFree86 mailing list archives, > since your answer is likely to be there (this is not a FreeBSD > specific problem, if it is not happening because of FreeBSD > specific code). > > The only possible way this could be a FreeBSD specific problem > is if you were using, e.g., the AGP driver, and it wasn't working. > > You said it worked bofore; probably the place to start is "what > changed betewwn 'before' and 'now'?". > > -- Terry > On FreeBSD 4.6 or 4.7 works, on FreeBSD 5.0 it doesn't work. Don't you think it is OS related. ? I even installed Linux RedHat 8.0 ( gcc 3.2x ) code. It works. Only on FreeBSD 5,0 , it doesn't work. -Horen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree
Horen wrote: > > You stated "Typing blind starts X again". > > > > Can you tell us what you mean by this? > > > > o It restarts X, as if you typed "startx" > > Exactly that. The problem is clearly in the X11 code, then, since it is not resetting the card to the video mode it was in before X started. You would do well to look at the XFree86 mailing list archives, since your answer is likely to be there (this is not a FreeBSD specific problem, if it is not happening because of FreeBSD specific code). The only possible way this could be a FreeBSD specific problem is if you were using, e.g., the AGP driver, and it wasn't working. You said it worked bofore; probably the place to start is "what changed betewwn 'before' and 'now'?". -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree
On 7 Nov 2002, Eric Anholt wrote: > On Thu, 2002-11-07 at 04:40, Horen wrote: > > > > > > On 6 Nov 2002, Eric Anholt wrote: > > > > > On Wed, 2002-11-06 at 18:34, Horen wrote: > > > > > > > > Posted a week ago the question, didn't get any reaction. > > > > > > > > Everything with current from last night works fine but killing > > > > X or logging out ends in a black screen. No way to activate the > > > > display without reboot. Remote login is fine. Typing blind works > > > > too. > > > > > > How long has this been going on? Did it start at any particular point > > > (a specific kernel or XFree86 upgrade)? What video card do you use? > > > Does starting X again not work? > > > > > > > It started sometimes in Oct, switched back to 4.7 stable. Did yesterday > > an installation from scratch and built XFree86-Server after buildworld. > > I was asking if X has ever exited cleanly to console for you after > logging out, and if it has, what you changed (particularly in your > XFree86-Server version) between when it was working and when it wasn't. > This is most likely just a failure of the driver to properly reset > things for your card. Does disabling DRI in XF86Config help it exit > cleanly? > X has exited cleanly only on 4.6 or 4.7 , never on 5.0 in the last 4-5 weeks. Didn't change anything. I disabled DRI but, didn't help. Work normally with res 1600x1200 , tried 1024x768 to 1920x1440. Nothing changed. -Horen > -- > Eric Anholt <[EMAIL PROTECTED]> > http://people.freebsd.org/~anholt/dri/ > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree
On Thu, 7 Nov 2002, Terry Lambert wrote: > Horen wrote: > > Tried all combinations. Disabled every chip related feature, that isn't > > required to bring X up. Screensaver is disabled. No way to get > > any readable display back without reboot. > > > > Installed a fresh XFree86 built from the ports tree, hour before > > updated. No luck :-( > > You stated "Typing blind starts X again". > > Can you tell us what you mean by this? > > o It restarts X, as if you typed "startx" Exactly that. -Horen > o It restarts X, as if you typed "xinit" > o It restarts X, as in it comes back from video signal blanking > o It doesn't really restart X, you were lying... (8-)) > o Turning my monitor off, and back on works the same way > o ...something else happens > > -- Terry > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree
On Thu, 2002-11-07 at 04:40, Horen wrote: > > > On 6 Nov 2002, Eric Anholt wrote: > > > On Wed, 2002-11-06 at 18:34, Horen wrote: > > > > > > Posted a week ago the question, didn't get any reaction. > > > > > > Everything with current from last night works fine but killing > > > X or logging out ends in a black screen. No way to activate the > > > display without reboot. Remote login is fine. Typing blind works > > > too. > > > > How long has this been going on? Did it start at any particular point > > (a specific kernel or XFree86 upgrade)? What video card do you use? > > Does starting X again not work? > > > > It started sometimes in Oct, switched back to 4.7 stable. Did yesterday > an installation from scratch and built XFree86-Server after buildworld. I was asking if X has ever exited cleanly to console for you after logging out, and if it has, what you changed (particularly in your XFree86-Server version) between when it was working and when it wasn't. This is most likely just a failure of the driver to properly reset things for your card. Does disabling DRI in XF86Config help it exit cleanly? -- Eric Anholt <[EMAIL PROTECTED]> http://people.freebsd.org/~anholt/dri/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree
> From [EMAIL PROTECTED] Thu Nov 7 19:30:04 2002 > Date: Thu, 07 Nov 2002 16:19:57 -0800 > From: Terry Lambert <[EMAIL PROTECTED]> > To: Horen <[EMAIL PROTECTED]> > Cc: Eric Anholt <[EMAIL PROTECTED]>, [EMAIL PROTECTED] > Subject: Re: XFree > > Horen wrote: > > Tried all combinations. Disabled every chip related feature, that isn't > > required to bring X up. Screensaver is disabled. No way to get > > any readable display back without reboot. > > > > Installed a fresh XFree86 built from the ports tree, hour before > > updated. No luck :-( > > You stated "Typing blind starts X again". > > Can you tell us what you mean by this? > > o It restarts X, as if you typed "startx" > o It restarts X, as if you typed "xinit" > o It restarts X, as in it comes back from video signal blanking > o It doesn't really restart X, you were lying... (8-)) > o Turning my monitor off, and back on works the same way > o ...something else happens I think he meant "Typing commands blind works, up to and including running `startx' to start X again". - @ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree
Horen wrote: > Tried all combinations. Disabled every chip related feature, that isn't > required to bring X up. Screensaver is disabled. No way to get > any readable display back without reboot. > > Installed a fresh XFree86 built from the ports tree, hour before > updated. No luck :-( You stated "Typing blind starts X again". Can you tell us what you mean by this? o It restarts X, as if you typed "startx" o It restarts X, as if you typed "xinit" o It restarts X, as in it comes back from video signal blanking o It doesn't really restart X, you were lying... (8-)) o Turning my monitor off, and back on works the same way o ...something else happens -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree
Tried all combinations. Disabled every chip related feature, that isn't required to bring X up. Screensaver is disabled. No way to get any readable display back without reboot. Installed a fresh XFree86 built from the ports tree, hour before updated. No luck :-( -Horen > > > Thanks, > > will check on that, hope it will help. > > -Horen > > On Thu, 7 Nov 2002, Terry Lambert wrote: > > > Horen wrote: > > > > > How long has this been going on? Did it start at any particular point > > > > > (a specific kernel or XFree86 upgrade)? What video card do you use? > > > > > Does starting X again not work? > > > > > > Typing blind starts X again. > > > > > > Do you have any idea what could be the problem. > > > > xset s off > > > > ? > > > > -- Terry > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-current" in the body of the message > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree
Thanks, will check on that, hope it will help. -Horen On Thu, 7 Nov 2002, Terry Lambert wrote: > Horen wrote: > > > > How long has this been going on? Did it start at any particular point > > > > (a specific kernel or XFree86 upgrade)? What video card do you use? > > > > Does starting X again not work? > > > > Typing blind starts X again. > > > > Do you have any idea what could be the problem. > > xset s off > > ? > > -- Terry > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree
Horen wrote: > > > How long has this been going on? Did it start at any particular point > > > (a specific kernel or XFree86 upgrade)? What video card do you use? > > > Does starting X again not work? > > Typing blind starts X again. > > Do you have any idea what could be the problem. xset s off ? -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree
walt wrote: > Horen wrote: > > Posted a week ago the question, didn't get any reaction. > > > > Everything with current from last night works fine but killing > > X or logging out ends in a black screen. No way to activate the > > display without reboot. Remote login is fine. Typing blind works > > too. > > I have exactly the same problem on my NetBSD box but I haven't > spent any time trying to fix it. > > I wonder if the console font color is being reset to black. > You could try typing 'vidcontrol white black' to test that > theory. Dunno what might be causing it, though. I had the same problem. I made it go away by turning off all acceleration, and then turning on accelleration options, one by one, until the problem reappeared, and then leaving the three that cuased problems off. It seems that the driver was written for a rev. 2 of the NeoMagic chip, and my laptop actually has rev. 3. Most likely, you will find that turning off all chip-specific options, and then turning on only those which actually reliably work, will fix your problem. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree
> > > On 6 Nov 2002, Eric Anholt wrote: > > > On Wed, 2002-11-06 at 18:34, Horen wrote: > > > > > > Posted a week ago the question, didn't get any reaction. > > > > > > Everything with current from last night works fine but killing > > > X or logging out ends in a black screen. No way to activate the > > > display without reboot. Remote login is fine. Typing blind works > > > too. > > > > How long has this been going on? Did it start at any particular point > > (a specific kernel or XFree86 upgrade)? What video card do you use? > > Does starting X again not work? > > Typing blind starts X again. Do you have any idea what could be the problem. Thanks, -Horen > > It started sometimes in Oct, switched back to 4.7 stable. Did yesterday > an installation from scratch and built XFree86-Server after buildworld. > > Video card: Matrox MG 400 Max , box is double Athlon MP 2000+ on a > Tyan Motherboard. > > > --- > Nov 7 07:26:52 salome kernel: drm0: mem > 0xf600-0xf > 67f,0xf680-0xf6803fff,0xfc00-0xfdff irq 10 at device 5.0 > on pci1 > Nov 7 07:26:52 salome kernel: info: [drm] AGP at 0xf800 64MB > Nov 7 07:26:52 salome kernel: info: [drm] Initialized mga 3.0.2 20010321 > on min > or 0 > -- > > > -Horen > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree
Thanks for the tip, was my first idea too, because you can type blind. But it doesn't help, it still stays everything black. Remote login works fine, there are no suspicious processes running. -Horen On Thu, 7 Nov 2002, walt wrote: > Horen wrote: > > Posted a week ago the question, didn't get any reaction. > > > > Everything with current from last night works fine but killing > > X or logging out ends in a black screen. No way to activate the > > display without reboot. Remote login is fine. Typing blind works > > too. > > I have exactly the same problem on my NetBSD box but I haven't > spent any time trying to fix it. > > I wonder if the console font color is being reset to black. > You could try typing 'vidcontrol white black' to test that > theory. Dunno what might be causing it, though. > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree
Horen wrote: Posted a week ago the question, didn't get any reaction. Everything with current from last night works fine but killing X or logging out ends in a black screen. No way to activate the display without reboot. Remote login is fine. Typing blind works too. I have exactly the same problem on my NetBSD box but I haven't spent any time trying to fix it. I wonder if the console font color is being reset to black. You could try typing 'vidcontrol white black' to test that theory. Dunno what might be causing it, though. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree
On 6 Nov 2002, Eric Anholt wrote: > On Wed, 2002-11-06 at 18:34, Horen wrote: > > > > Posted a week ago the question, didn't get any reaction. > > > > Everything with current from last night works fine but killing > > X or logging out ends in a black screen. No way to activate the > > display without reboot. Remote login is fine. Typing blind works > > too. > > How long has this been going on? Did it start at any particular point > (a specific kernel or XFree86 upgrade)? What video card do you use? > Does starting X again not work? > It started sometimes in Oct, switched back to 4.7 stable. Did yesterday an installation from scratch and built XFree86-Server after buildworld. Video card: Matrox MG 400 Max , box is double Athlon MP 2000+ on a Tyan Motherboard. --- Nov 7 07:26:52 salome kernel: drm0: mem 0xf600-0xf 67f,0xf680-0xf6803fff,0xfc00-0xfdff irq 10 at device 5.0 on pci1 Nov 7 07:26:52 salome kernel: info: [drm] AGP at 0xf800 64MB Nov 7 07:26:52 salome kernel: info: [drm] Initialized mga 3.0.2 20010321 on min or 0 -- -Horen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree
On Wed, 6 Nov 2002, Steve Kargl wrote: > On Wed, Nov 06, 2002 at 09:34:39PM -0500, Horen wrote: > > > > Posted a week ago the question, didn't get any reaction. > > > > Everything with current from last night works fine but killing > > X or logging out ends in a black screen. No way to activate the > > display without reboot. Remote login is fine. Typing blind works > > too. > > > > Is there a fix in sight, would be great help. > > > > I just rebuilt world and XFree86 4.2.1. I > killed and restarted X several times while > getting my fvwm2 desktop back to normal. I > didn't have this black screen problem. > How old is your X and desktop? > > -- > Steve > OS is from 11/6 . Built XFree86 core was from snapshot 6/11, rebuilt XFree86-Server last night, still the same problem. -Horen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree
On Wed, 2002-11-06 at 18:34, Horen wrote: > > Posted a week ago the question, didn't get any reaction. > > Everything with current from last night works fine but killing > X or logging out ends in a black screen. No way to activate the > display without reboot. Remote login is fine. Typing blind works > too. How long has this been going on? Did it start at any particular point (a specific kernel or XFree86 upgrade)? What video card do you use? Does starting X again not work? -- Eric Anholt <[EMAIL PROTECTED]> http://people.freebsd.org/~anholt/dri/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree
On Wed, Nov 06, 2002 at 09:34:39PM -0500, Horen wrote: > > Posted a week ago the question, didn't get any reaction. > > Everything with current from last night works fine but killing > X or logging out ends in a black screen. No way to activate the > display without reboot. Remote login is fine. Typing blind works > too. > > Is there a fix in sight, would be great help. > I just rebuilt world and XFree86 4.2.1. I killed and restarted X several times while getting my fvwm2 desktop back to normal. I didn't have this black screen problem. How old is your X and desktop? -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
XFree
Posted a week ago the question, didn't get any reaction. Everything with current from last night works fine but killing X or logging out ends in a black screen. No way to activate the display without reboot. Remote login is fine. Typing blind works too. Is there a fix in sight, would be great help. Thanks, -Horen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
CURRENT an XFree
5.0 built and installed 10/22 runs fine on a Tyan Thunder K7 with 2 Athlons. Exception: Shutdown of the X server, no matter when and how, causes complete black display. The box is remotely reachable. The only way to restore the console display is to reboot. Guess a known issue. It happens always. -horen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree 4 DRM/DRI under -CURRENT
+---[ Sameh Ghane ]-- | Hi, | | Did anyone find a way to compile the x11-servers/XFree86-4-Server port ? | | According to the Makefile it is not possible to build it since FreeBSD 500013. | Will a package built under < 500013 work under > 500013 ? It's busted since the KSE changes went in, the changes are fairly easy to do, but, it involves a crapload of #ifdefing to do it properly... The pre 500013 kernel modules will not work for you, they will panic your system as soon as you try to access them d;) They're on my list of things to do someday if someone hasn't done them, by the time I get around to it. -- Totally Holistic Enterprises Internet| | Andrew Milton The Internet (Aust) Pty Ltd | | ACN: 082 081 472 ABN: 83 082 081 472 | M:+61 416 022 411 | Carpe Daemon PO Box 837 Indooroopilly QLD 4068|[EMAIL PROTECTED]| To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
XFree 4 DRM/DRI under -CURRENT
Hi, Did anyone find a way to compile the x11-servers/XFree86-4-Server port ? According to the Makefile it is not possible to build it since FreeBSD 500013. Will a package built under < 500013 work under > 500013 ? Another way to have DRI/M rendering with mga/G400 and XFree under -current ? Cheers, -- Sameh To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree 4.0 broken by libc changes ?
On Sun, 25 Feb 2001, Martin Blapp wrote: > > Daniel, > > > I don't know, what port builds libGL.so.1? > > Something has to link in the threads library... > > Yep, XFree86 libs should be linked against -lc_r, > I got this working with this. > > It's still broken in FreeBSD ports, all GL dependent > programms are broken for CURRENT at the moment. > > I've another issue now: > > /usr/local/bin/dcopidl ./konq_undo.h > konq_undo.kidl || rm -f > konq_undo.kidl /usr/libexec/ld-elf.so.1: /usr/lib/libc_r.so.5: Undefined > symbol "_flockfile" > /usr/local/bin/dcopidl2cpp --c++-suffix cc --no-stub konq_undo.kidl > /usr/libexec/ld-elf.so.1: /usr/lib/libc_r.so.5: Undefined symbol > "_flockfile > > This while I'm trying to build kdebase2 from ports. > > You've got an idea ? > > # objdump --dynamic-syms /usr/lib/libc_r.so.5 | grep _flockfile > 9068 gDF .text 0040 _flockfile_debug > D *UND* _flockfile Right, _flockfile is in libc.so.5 now. It should be picked up if the application is also linked with libc.so.5, I think. -- Dan Eischen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree 4.0 broken by libc changes ?
Hi, > konq_undo.kidl /usr/libexec/ld-elf.so.1: /usr/lib/libc_r.so.5: Undefined > symbol "_flockfile" > /usr/local/bin/dcopidl2cpp --c++-suffix cc --no-stub konq_undo.kidl > /usr/libexec/ld-elf.so.1: /usr/lib/libc_r.so.5: Undefined symbol > "_flockfile Sorry, fixed this with recompling qt. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree 4.0 broken by libc changes ?
Daniel, > I don't know, what port builds libGL.so.1? > Something has to link in the threads library... Yep, XFree86 libs should be linked against -lc_r, I got this working with this. It's still broken in FreeBSD ports, all GL dependent programms are broken for CURRENT at the moment. I've another issue now: /usr/local/bin/dcopidl ./konq_undo.h > konq_undo.kidl || rm -f konq_undo.kidl /usr/libexec/ld-elf.so.1: /usr/lib/libc_r.so.5: Undefined symbol "_flockfile" /usr/local/bin/dcopidl2cpp --c++-suffix cc --no-stub konq_undo.kidl /usr/libexec/ld-elf.so.1: /usr/lib/libc_r.so.5: Undefined symbol "_flockfile This while I'm trying to build kdebase2 from ports. You've got an idea ? # objdump --dynamic-syms /usr/lib/libc_r.so.5 | grep _flockfile 9068 gDF .text 0040 _flockfile_debug D *UND* _flockfile and right, it's undefined there ... Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree 3.3.6 authentication failed?
On Fri, Feb 25, 2000 at 03:06:55PM -0800, Joel Ray Holveck wrote: > [Followups to -current] > > >>I am running monday's current, Mesa-glx for Riva, XFree 3.3.6 and > >> KDE 1.1.2. All from monday's ports tree. > >>Well, I think I can't say I am running this system, for I am getting > >> the following message whenever I try startx: > > > Authentication failed - cannot start X server. > > > Perhaps you do not have console ownership? > > > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > > seems that you have built XFree with PAM support. > > Just rebuild without PAM -- it's broken. > > Could you give me a few more details about the brokenness? It's also in -STABLE. Basically, PAM was built without a crypt library linked in. When new is built with PAM support, it tries to access crypt in PAM. Then, it blows up. Build without PAM, or cvsup latest sources for the patch. It was mentioned in the mailing lists I think back in December? -- Joseph nugundam =best=com==/==\=IIGS=/==\=Playstation=/==\=Civic HX CVT=/==\ #Anime Expo 2000>> www.anime-expo.org/ > # FreeBSD: The Power to Serve >> www.freebsd.org > #The Ultimate Online Speed-Shop >> www.racesearch.com / To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree 3.3.6 authentication failed?
[Followups to -current] >> I am running monday's current, Mesa-glx for Riva, XFree 3.3.6 and >> KDE 1.1.2. All from monday's ports tree. >> Well, I think I can't say I am running this system, for I am getting >> the following message whenever I try startx: > > Authentication failed - cannot start X server. > > Perhaps you do not have console ownership? > > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > seems that you have built XFree with PAM support. > Just rebuild without PAM -- it's broken. Could you give me a few more details about the brokenness? Thanks, joelh -- Joel Ray Holveck - [EMAIL PROTECTED] Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree 3.3.6 authentication failed?
hi, there! On Wed, 23 Feb 2000 [EMAIL PROTECTED] wrote: > I am running monday's current, Mesa-glx for Riva, XFree 3.3.6 and > KDE 1.1.2. All from monday's ports tree. > Well, I think I can't say I am running this system, for I am getting > the following message whenever I try startx: > > Authentication failed - cannot start X server. > Perhaps you do not have console ownership? > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > giving up. > xinit: No such file or directory (errno 2): unable to connect to X server > xinit: No such process (errno 3): Server error. seems that you have built XFree with PAM support. Just rebuild without PAM -- it's broken. /fjoe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree 3.3.6 authentication failed?
Actually I think this is a pam.conf issue. You probably built 3.3.6 with PAM support? This happened to me as soon as 3.3.6 came out. try copying pam.conf from whereveryoubuildworld/etc to /etc and see if that fixes it. I think mergemaster would take care of this too, I dunno last time I used it it did more harm than good. -Will On Tue, 22 Feb 2000, Will Andrews wrote: > On Wed, Feb 23, 2000 at 02:10:00AM -0300, [EMAIL PROTECTED] wrote: > > Dear guys, > > > > I am running monday's current, Mesa-glx for Riva, XFree 3.3.6 and > > KDE 1.1.2. All from monday's ports tree. > > Well, I think I can't say I am running this system, for I am getting > > the following message whenever I try startx: > > > > Authentication failed - cannot start X server. > > Perhaps you do not have console ownership? > > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > > giving up. > > xinit: No such file or directory (errno 2): unable to connect to X server > > xinit: No such process (errno 3): Server error. > > > > Damn, I know this must be my mistake. However, I can't seem to get > > X up. However, /stand/sysinstall -> Configure -> XFree86 -> XF86Setup > > works smooth. Before you mention it: yeah, yeah, I tried startx as root > > against my best judgement; and no, it did not work. :) > > UCONSOLE is enabled. > > My .xinitrc follows at the end of this file. > > What am I missing? A new authentication system? My guess. I went > > through the FAQ and most of the simple docs; I must be overlooking something. > > Any and all help appreciated. Please CC: to [EMAIL PROTECTED], for I > > am subscribed to neither freebsd-questions nor freebsd-current. > > I apologize in advance for the CC: accross mailing lists. > > > > Regards, > > Mario Ferreira > > > > ps: Please, don't flame me. /dev/null appreciates it. Thanks again. > > 1) Do you have "XSERVER" option in kernel? I'm not sure if it's > required, but it might be. > > 2) You should start KDE with "startkde" not "kde". > > -- > Will Andrews <[EMAIL PROTECTED]> > GCS/E/S @d- s+:+>+:- a--->+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- > ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++> DI+++ D+ > G++>+++ e-> h! r-->+++ y? > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree 3.3.6 authentication failed?
On Wed, Feb 23, 2000 at 02:10:00AM -0300, [EMAIL PROTECTED] wrote: > Dear guys, > > I am running monday's current, Mesa-glx for Riva, XFree 3.3.6 and > KDE 1.1.2. All from monday's ports tree. > Well, I think I can't say I am running this system, for I am getting > the following message whenever I try startx: > > Authentication failed - cannot start X server. > Perhaps you do not have console ownership? [snip] You built X with PAM enabled. -- Crist J. Clark [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree 3.3.6 authentication failed?
On Wed, Feb 23, 2000 at 02:10:00AM -0300, [EMAIL PROTECTED] wrote: > Dear guys, > > I am running monday's current, Mesa-glx for Riva, XFree 3.3.6 and > KDE 1.1.2. All from monday's ports tree. > Well, I think I can't say I am running this system, for I am getting > the following message whenever I try startx: > > Authentication failed - cannot start X server. > Perhaps you do not have console ownership? > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > giving up. > xinit: No such file or directory (errno 2): unable to connect to X server > xinit: No such process (errno 3): Server error. > > Damn, I know this must be my mistake. However, I can't seem to get > X up. However, /stand/sysinstall -> Configure -> XFree86 -> XF86Setup > works smooth. Before you mention it: yeah, yeah, I tried startx as root > against my best judgement; and no, it did not work. :) > UCONSOLE is enabled. > My .xinitrc follows at the end of this file. > What am I missing? A new authentication system? My guess. I went > through the FAQ and most of the simple docs; I must be overlooking something. > Any and all help appreciated. Please CC: to [EMAIL PROTECTED], for I > am subscribed to neither freebsd-questions nor freebsd-current. > I apologize in advance for the CC: accross mailing lists. > > Regards, > Mario Ferreira > > ps: Please, don't flame me. /dev/null appreciates it. Thanks again. 1) Do you have "XSERVER" option in kernel? I'm not sure if it's required, but it might be. 2) You should start KDE with "startkde" not "kde". -- Will Andrews <[EMAIL PROTECTED]> GCS/E/S @d- s+:+>+:- a--->+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++> DI+++ D+ G++>+++ e-> h! r-->+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
XFree 3.3.6 authentication failed?
Dear guys, I am running monday's current, Mesa-glx for Riva, XFree 3.3.6 and KDE 1.1.2. All from monday's ports tree. Well, I think I can't say I am running this system, for I am getting the following message whenever I try startx: Authentication failed - cannot start X server. Perhaps you do not have console ownership? _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 _X11TransSocketUNIXConnect: Can't connect: errno = 2 giving up. xinit: No such file or directory (errno 2): unable to connect to X server xinit: No such process (errno 3): Server error. Damn, I know this must be my mistake. However, I can't seem to get X up. However, /stand/sysinstall -> Configure -> XFree86 -> XF86Setup works smooth. Before you mention it: yeah, yeah, I tried startx as root against my best judgement; and no, it did not work. :) UCONSOLE is enabled. My .xinitrc follows at the end of this file. What am I missing? A new authentication system? My guess. I went through the FAQ and most of the simple docs; I must be overlooking something. Any and all help appreciated. Please CC: to [EMAIL PROTECTED], for I am subscribed to neither freebsd-questions nor freebsd-current. I apologize in advance for the CC: accross mailing lists. Regards, Mario Ferreira ps: Please, don't flame me. /dev/null appreciates it. Thanks again. -- #!/bin/sh # $XConsortium: xinitrc.cpp,v 1.4 91/08/22 11:41:34 rws Exp $ userresources=$HOME/.Xresources usermodmap=$HOME/.Xmodmap sysresources=/usr/X11R6/lib/X11/xinit/.Xresources sysmodmap=/usr/X11R6/lib/X11/xinit/.Xmodmap # merge in defaults and keymaps if [ -f $sysresources ]; then xrdb -merge $sysresources fi if [ -f $sysmodmap ]; then xmodmap $sysmodmap fi if [ -f $userresources ]; then xrdb -merge $userresources fi if [ -f $usermodmap ]; then xmodmap $usermodmap fi # start some nice programs kde To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree build fine but don't install
I managed to fix this problem temporarily for myself, but was hoping the tree would fix itself soon enough. At the top of FSConServ.c add the line #define _P1003_1B_VISIBLE I believe (I deleeted the X source tree), and it'll build fine. Excerpts from FreeBSD-Current: 15-Oct-99 XFree build fine but don't .. by G. Giovannelli@giovannel > I tried to install from the ports XFree 3.3.5 in my 4.0-CURRENT box. > It compile well, but when it's the time of the install I receive this error : > > rm -f FSConnServ.o > cc -c -O2 -ansi -pedantic -Dasm=__asm -I../../include/fonts -I../.. > -I../../ex > ports/include -DCSRG_BASED -DFUNCPROTO=15 > -DNARROWPROTO -DMALLOC_0_RETURNS_N > ULL -DTCPCONN -DUNIXCONN -DHAS_STICKY_DIR_BIT -DFS_t -DTRANS_CLIENT > -DBSD44SOCKE > TS FSConnServ.c > In file included from /usr/include/sys/param.h:90, > from ../../exports/include/X11/Xpoll.h:66, > from FSConnServ.c:58: > /usr/include/sys/signal.h:212: syntax error before `siginfo_t' > In file included from /usr/include/sys/param.h:90, > from ../../exports/include/X11/Xpoll.h:66, > from FSConnServ.c:58: > /usr/include/sys/signal.h:285: field `sigev_value' has incomplete type > *** Error code 1 > Stop in /usr/ports/x11/XFree86/work/xc/lib/FS. > *** Error code 1 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
XFree build fine but don't install
I tried to install from the ports XFree 3.3.5 in my 4.0-CURRENT box. It compile well, but when it's the time of the install I receive this error : rm -f FSConnServ.o cc -c -O2 -ansi -pedantic -Dasm=__asm -I../../include/fonts -I../.. -I../../ex ports/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -DMALLOC_0_RETURNS_N ULL -DTCPCONN -DUNIXCONN -DHAS_STICKY_DIR_BIT -DFS_t -DTRANS_CLIENT -DBSD44SOCKE TS FSConnServ.c In file included from /usr/include/sys/param.h:90, from ../../exports/include/X11/Xpoll.h:66, from FSConnServ.c:58: /usr/include/sys/signal.h:212: syntax error before `siginfo_t' In file included from /usr/include/sys/param.h:90, from ../../exports/include/X11/Xpoll.h:66, from FSConnServ.c:58: /usr/include/sys/signal.h:285: field `sigev_value' has incomplete type *** Error code 1 Stop in /usr/ports/x11/XFree86/work/xc/lib/FS. *** Error code 1 I am sorry if this is a well known problem, but I couldn't read the mailing lists in the past days ... Thanks... Best Regards, Gianmarco Giovannelli , "Unix expert since yesterday" http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: try to build xfree under current siginfo_t
Fritz Heinrichmeyer wrote: > > as i accidentally deleted my libc.so.3 i thought it would be a good time > to rebuild xfree, but i came in a preprocessor hell due to siginfo_t > _POSIX_SOURCE or not ... definition at the stage of building makedepend. > In file included from main.c:41: > /usr/include/signal.h:72: warning: `union sigval' declared inside parameter \ > list > /usr/include/signal.h:72: warning: its scope is only this definition \ > or declaration, > /usr/include/signal.h:72: warning: which is probably not what you want. > /usr/include/signal.h:72: warning: parameter has incomplete type > /usr/include/signal.h:73: syntax error before `siginfo_t' > /usr/include/signal.h:74: syntax error before `siginfo_t' > > the offending code is between an #ifdef _P1003_1B_VISIBLE > construct. This caused by the recent namespace polution fixes. They were always defined before that, so this was not a problem. I think you should change #ifdef _P1003_1B_VISIBLE into #ifndef _POSIX_SOURCE for now. -- Marcel Moolenaarmailto:[EMAIL PROTECTED] SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD projectmailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
try to build xfree under current siginfo_t
as i accidentally deleted my libc.so.3 i thought it would be a good time to rebuild xfree, but i came in a preprocessor hell due to siginfo_t _POSIX_SOURCE or not ... definition at the stage of building makedepend. In file included from main.c:41: /usr/include/signal.h:72: warning: `union sigval' declared inside parameter \ list /usr/include/signal.h:72: warning: its scope is only this definition \ or declaration, /usr/include/signal.h:72: warning: which is probably not what you want. /usr/include/signal.h:72: warning: parameter has incomplete type /usr/include/signal.h:73: syntax error before `siginfo_t' /usr/include/signal.h:74: syntax error before `siginfo_t' the offending code is between an #ifdef _P1003_1B_VISIBLE construct. Fritz Heinrichmeyer mailto:[EMAIL PROTECTED] FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://ES-i2.fernuni-hagen.de/~jfh To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sdr25 wants to reinstall xfree
Randy Bush wrote: > is this for real or is it an aout-to-elf thing? This is for real. Tk80 is looking for ELFed X11 (You did recompile your X, Right? If not then it is an ELF thing). The XFree86 port is rather good, IMHO. M > randy > > > ===> Generating temporary packing list > /bin/ln -sf libtcl80.so.1 /usr/local/lib/libtcl80.so > /usr/bin/env OBJFORMAT=elf /sbin/ldconfig -m /usr/local/lib > /usr/bin/env PKG_PREFIX=/usr/local /bin/sh /usr/ports/lang/tcl80/pkg/INSTALL. tclsh > ===> Registering installation for tcl-8.0.4 > ===> Returning to build of tk-8.0.4 > ===> tk-8.0.4 depends on shared library: X11.6 - not found > ===>Verifying install for X11.6 in /usr/ports/x11/XFree86 > > Assuming that you have fetched a USA-Legal Wraphelp.c. > >> X333src-1.tgz doesn't seem to exist on this system. > >> Attempting to fetch from ftp://ftp.xfree86.org/pub/XFree86/3.3.3/source/. > Receiving X333src-1.tgz (16596763 bytes): 100% > 16596763 bytes transfered in 132.8 seconds (122.00 Kbytes/s) > >> X333src-2.tgz doesn't seem to exist on this system. > >> Attempting to fetch from ftp://ftp.xfree86.org/pub/XFree86/3.3.3/source/. > Receiving X333src-2.tgz (14501435 bytes): 100% > 14501435 bytes transfered in 111.4 seconds (127.07 Kbytes/s) > >> 3.3.3-3.3.3.1.diff.gz doesn't seem to exist on this system. > >> Attempting to fetch from ftp://ftp.xfree86.org/pub/XFree86/3.3.3.1/fixes/. > Receiving 3.3.3-3.3.3.1.diff.gz (178472 bytes): 100% > 178472 bytes transfered in 1.7 seconds (99.77 Kbytes/s) > ===> Extracting for XFree86-3.3.3.1 > >> Checksum OK for xc/X333src-1.tgz. > >> Checksum OK for xc/X333src-2.tgz. > >> Checksum OK for xc/3.3.3-3.3.3.1.diff.gz. > ===> Patching for XFree86-3.3.3.1 > ===> Applying distribution patches for XFree86-3.3.3.1 > ===> Configuring for XFree86-3.3.3.1 > *** I don't see the static library for tk version in /usr/local/lib. > *** XF86Setup will not be installed. If you want to build this program > *** install tk 4.2 or 8.0 first. > > Which servers do you wish to build, you can save a lot of disk space > by only compiling the server you will be using. It will also save you > considerable compile time. > Do you want to build the VGA16 server? [YES] ^C > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-multimedia" in the body of the message > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
sdr25 wants to reinstall xfree
is this for real or is it an aout-to-elf thing? randy ===> Generating temporary packing list /bin/ln -sf libtcl80.so.1 /usr/local/lib/libtcl80.so /usr/bin/env OBJFORMAT=elf /sbin/ldconfig -m /usr/local/lib /usr/bin/env PKG_PREFIX=/usr/local /bin/sh /usr/ports/lang/tcl80/pkg/INSTALL.tclsh ===> Registering installation for tcl-8.0.4 ===> Returning to build of tk-8.0.4 ===> tk-8.0.4 depends on shared library: X11.6 - not found ===>Verifying install for X11.6 in /usr/ports/x11/XFree86 Assuming that you have fetched a USA-Legal Wraphelp.c. >> X333src-1.tgz doesn't seem to exist on this system. >> Attempting to fetch from ftp://ftp.xfree86.org/pub/XFree86/3.3.3/source/. Receiving X333src-1.tgz (16596763 bytes): 100% 16596763 bytes transfered in 132.8 seconds (122.00 Kbytes/s) >> X333src-2.tgz doesn't seem to exist on this system. >> Attempting to fetch from ftp://ftp.xfree86.org/pub/XFree86/3.3.3/source/. Receiving X333src-2.tgz (14501435 bytes): 100% 14501435 bytes transfered in 111.4 seconds (127.07 Kbytes/s) >> 3.3.3-3.3.3.1.diff.gz doesn't seem to exist on this system. >> Attempting to fetch from ftp://ftp.xfree86.org/pub/XFree86/3.3.3.1/fixes/. Receiving 3.3.3-3.3.3.1.diff.gz (178472 bytes): 100% 178472 bytes transfered in 1.7 seconds (99.77 Kbytes/s) ===> Extracting for XFree86-3.3.3.1 >> Checksum OK for xc/X333src-1.tgz. >> Checksum OK for xc/X333src-2.tgz. >> Checksum OK for xc/3.3.3-3.3.3.1.diff.gz. ===> Patching for XFree86-3.3.3.1 ===> Applying distribution patches for XFree86-3.3.3.1 ===> Configuring for XFree86-3.3.3.1 *** I don't see the static library for tk version in /usr/local/lib. *** XF86Setup will not be installed. If you want to build this program *** install tk 4.2 or 8.0 first. Which servers do you wish to build, you can save a lot of disk space by only compiling the server you will be using. It will also save you considerable compile time. Do you want to build the VGA16 server? [YES] ^C To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-multimedia" in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: New syscons + XFree 3.3.3.1 = problem?
> >but that doesn't happen any- > >more. Instead, it uses the current one (i.e. if I'm on ttyv3 > >and start X, it uses ttyv3). Is this intentional, or is it a > >bug? Oops... I'm very sorry for the confusion... it was all my fault. There were as many gettys configured in in /etc/ttys as MAXCONS in the kernel, so XFree wasn't able to allocate an unused vty, obviously. Disabling one getty solved the problem. Maybe this pitfall could be documented somewhere... But then again, maybe I'm the only one who's too dumb to get it right. :-] Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:o...@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: New syscons + XFree 3.3.3.1 = problem?
>I'm using -current as of 1998-01-14 with the new syscons (with >separated keyboard driver) and XFree86 3.3.3.1 (XF86_SVGA on a >Matrox G200). The keyboard and mouse are plain PS/2 models, >they work fine under syscons (i.e. not using XFree). [...] >XFree used to allocate the next free virtual terminal when >started (in this case the 11th), Yes, and it still should be. >but that doesn't happen any- >more. Instead, it uses the current one (i.e. if I'm on ttyv3 >and start X, it uses ttyv3). Is this intentional, or is it a >bug? Hmm, no, this shouldn't be happening. How do you start X, by hand, or via a local shell script (i.e. rc.local or something), or via /etc/ttys? >While the above isn't really a serious problem, the following >is: When X has run for some time, the keyboard suddenly starts >being unresponsive and unusable. This can happen after a few >minutes or after a few hours. There are no error messages, no >syslog entries. It looks like the keypresses don't get to >XFree anymore, but to the vty beneath. Restarting X helps, >until it happens again. Quite annoying. It sounds like the X server and getty is fighting for keyboard input... How many vtys do you have (check MAXCONS in the kernel config)? How many of which will run getty (check /etc/ttys)? Kazu To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
New syscons + XFree 3.3.3.1 = problem?
Hi, I'm using -current as of 1998-01-14 with the new syscons (with separated keyboard driver) and XFree86 3.3.3.1 (XF86_SVGA on a Matrox G200). The keyboard and mouse are plain PS/2 models, they work fine under syscons (i.e. not using XFree). The kernel contains the following entries: controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 device psm0at isa? tty irq 12 device vga0at isa? port ? conflicts pseudo-device splash device sc0 at isa? tty options MAXCONS=10 options SC_HISTORY_SIZE=500 XFree used to allocate the next free virtual terminal when started (in this case the 11th), but that doesn't happen any- more. Instead, it uses the current one (i.e. if I'm on ttyv3 and start X, it uses ttyv3). Is this intentional, or is it a bug? While the above isn't really a serious problem, the following is: When X has run for some time, the keyboard suddenly starts being unresponsive and unusable. This can happen after a few minutes or after a few hours. There are no error messages, no syslog entries. It looks like the keypresses don't get to XFree anymore, but to the vty beneath. Restarting X helps, until it happens again. Quite annoying. Does anyone else experience the same problems? Am I doing something wrong? What can I do to help tracking down the problem? Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:o...@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
