Re: /usr/ports/xll/XFree86-4
On Wed, 3 Dec 2003, Dan Nelson wrote:
> In the last episode (Dec 03), Mike Hunter said:
> > On Dec 02, "Jamie Bowden" wrote:
> > > I have a new machine that I've just installed 5.1-R on, and cvsup'd
> > > to -C. I'm attempting to build X, and am getting a core dump from
> > > rman during the process.
> >
> > I had this happen too. I did something really hack-ish to get around
> > it (like delete that documentation or some other unspeakable hack.)
>
> The coredump is due to bugs in the rman command (which is installed by
> the imake port, believe it or not). I submitted a bugreport on it in
> July, and hopefully it will be in Xfree86 4.4.0. Installing the
> textproc/rman port may mask the bug until then, or you can drop this
> file into ports/devel/imake-4/files and rebuild imake.
Installing /usr/ports/emulators/linux_compat seems to fix this. I have no
idea why, but I went ahead and installed it so I could install the Nvidia
X driver. After I did that (built and installed linux_compat and built
and installed the Nvidia driver), I went ahead and re-entered
x11/XFree86-4/ and did a make install again (mostly just looking for the
error so I could comment the lines out of the makefile), and it built and
installed (after I rebuilt and reinstalled imake-4, just on principle).
There's an odd dependency hiding in there somewhere.
Now I just have to figure out why X only believes this LCD is capable of
640x480 or 320x240 instead of the 1920x1600 it's actually capable of, so
back to -mobile I go.
Jamie Bowden
--
"It was half way to Rivendell when the drugs began to take hold"
Hunter S Tolkien "Fear and Loathing in Barad Dur"
Iain Bowen <[EMAIL PROTECTED]>
--- ../extras/rman/rman.c.orig Tue Jul 15 23:53:53 2003
+++ ../extras/rman/rman.c Tue Jul 15 23:44:21 2003
@@ -4104,6 +4104,9 @@
}
}
break;
+case 0:
+ /* ignore */
+ break;
default: /* unknown escaped character */
sputchar(*p++);
}
@@ -4133,7 +4133,7 @@ source_out0(const char *pin, char end)
/* postpone check until after following character so catch closing tags */
if ((sI>=4+1 && plain[sI-1-1]==')') ||
/* (plain[sI-1]==' ' && (q=strchr(plain,' '))!=NULL && q<&plain[sI-1])) */
-(plain[sI-1]==' ' && !isalnum(plain[sI-1-1]))) {
+(sI>=2 && plain[sI-1]==' ' && !isalnum(plain[sI-1-1]))) {
/* regardless, flush buffer */
source_flush();
}
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /usr/ports/xll/XFree86-4
In the last episode (Dec 03), Mike Hunter said:
> On Dec 02, "Jamie Bowden" wrote:
> > I have a new machine that I've just installed 5.1-R on, and cvsup'd
> > to -C. I'm attempting to build X, and am getting a core dump from
> > rman during the process.
>
> I had this happen too. I did something really hack-ish to get around
> it (like delete that documentation or some other unspeakable hack.)
The coredump is due to bugs in the rman command (which is installed by
the imake port, believe it or not). I submitted a bugreport on it in
July, and hopefully it will be in Xfree86 4.4.0. Installing the
textproc/rman port may mask the bug until then, or you can drop this
file into ports/devel/imake-4/files and rebuild imake.
--
Dan Nelson
[EMAIL PROTECTED]
--- ../extras/rman/rman.c.orig Tue Jul 15 23:53:53 2003
+++ ../extras/rman/rman.c Tue Jul 15 23:44:21 2003
@@ -4104,6 +4104,9 @@
}
}
break;
+case 0:
+ /* ignore */
+ break;
default: /* unknown escaped character */
sputchar(*p++);
}
@@ -4133,7 +4133,7 @@ source_out0(const char *pin, char end)
/* postpone check until after following character so catch closing tags */
if ((sI>=4+1 && plain[sI-1-1]==')') ||
/* (plain[sI-1]==' ' && (q=strchr(plain,' '))!=NULL && q<&plain[sI-1])) */
-(plain[sI-1]==' ' && !isalnum(plain[sI-1-1]))) {
+(sI>=2 && plain[sI-1]==' ' && !isalnum(plain[sI-1-1]))) {
/* regardless, flush buffer */
source_flush();
}
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /usr/ports/xll/XFree86-4
On Dec 02, "Jamie Bowden" wrote: > I have a new machine that I've just installed 5.1-R on, and cvsup'd to -C. > I'm attempting to build X, and am getting a core dump from rman during the > process. I had this happen too. I did something really hack-ish to get around it (like delete that documentation or some other unspeakable hack.) Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
XFree86 ports / Font problem
Hi... after updating my 5.1-current machine: a) new kernel b) new world c) all packages (including XFree86) d) newest gnome-packages (using marcusmerge) i got these msgs in XFree86.0.log Warning: font renderer for ".pcf" already registered at priority 0 Warning: font renderer for ".pcf.Z" already registered at priority 0 Warning: font renderer for ".pcf.gz" already registered at priority 0 Warning: font renderer for ".snf" already registered at priority 0 Warning: font renderer for ".snf.Z" already registered at priority 0 Warning: font renderer for ".snf.gz" already registered at priority 0 Warning: font renderer for ".bdf" already registered at priority 0 Warning: font renderer for ".bdf.Z" already registered at priority 0 Warning: font renderer for ".bdf.gz" already registered at priority 0 Warning: font renderer for ".pmf" already registered at priority 0 The result is a fontless X... (okay enlightenment has it fonts... but mostly prgs do not... including gdm and all that things) Does anyone know something about this? Jan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD-Current and XFree86
On Fri, 2003-10-24 at 00:13, Thomas Schwarzkopf wrote: > On Friday 24 October 2003 02:00, James Tanis wrote: > > > From the log file: > > (II) Primary Device is: > > (--) Assigning device section with no busID to primary device > > (WW) RADEON: No matching Device section for instance (BusID > > PCI:1:0:1) found (EE) No devices detected. > > > > I did not attempt any different settings from the norm at > > this time since, if my memory serves me right this is the same exact > > error I was getting before and nothing I tried seemed to fix it. Here > > is the device section as it is now for my radeon 9800, these are the > > same settings that I used to use and worked perfectly fine with my > > radeon 7000, although I have tried a config without the extra options > > it did not seems to help nor is their any reason that I can think of > > that these options would not work with the 9800. > > > > Section "Device" > > Identifier "Radeon 9800" > > Driver "radeon" > > #VideoRam131072 > > # Insert Clocks lines here if appropriate > > Option "AGPMode" "4" > > Option "AGPFastWrite" "1" > > Option "EnablePageFlip""1" > > EndSection > > Have you tried adding a line like this > > BusID"PCI 01:00:0" > > to Section "Device"? Maybe also try "PCI 1:0:1" > I had the same error with a different card and this helped. Actually, the problem here (as I just replied in a private email) was that that card is newer than 4.2.99.12's radeon support, so it didn't probe the radeon. Solution I suggested was to try chipid 0x4e48 because his is 0x4e49, which is the same generation of chip. -- Eric Anholt[EMAIL PROTECTED] http://people.freebsd.org/~anholt/ [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD-Current and XFree86
At Thu, 23 Oct 2003 20:00:38 -0400, James Tanis wrote: > > Attempted this, first did a deinstall of XFree86-Server and then > built/installed XFree86-Server-snap. It built and installed perfectly fine, > from what I can see it runs fine too.. but I get the same error. You > weren't wrong, in the log once of the supported cards listed is the ATI > Radeon 9800 NH (AGP), although I have no idea what the NH stands for. The > only problem is I'm getting the same exact error I was previously.. > You could try running "XFree86 -configure" as root and see if there are any differences to you conf. -Richard ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD-Current and XFree86
On Friday 24 October 2003 02:00, James Tanis wrote: > From the log file: > (II) Primary Device is: > (--) Assigning device section with no busID to primary device > (WW) RADEON: No matching Device section for instance (BusID > PCI:1:0:1) found (EE) No devices detected. > > I did not attempt any different settings from the norm at > this time since, if my memory serves me right this is the same exact > error I was getting before and nothing I tried seemed to fix it. Here > is the device section as it is now for my radeon 9800, these are the > same settings that I used to use and worked perfectly fine with my > radeon 7000, although I have tried a config without the extra options > it did not seems to help nor is their any reason that I can think of > that these options would not work with the 9800. > > Section "Device" > Identifier "Radeon 9800" > Driver "radeon" > #VideoRam131072 > # Insert Clocks lines here if appropriate > Option "AGPMode" "4" > Option "AGPFastWrite" "1" > Option "EnablePageFlip""1" > EndSection Have you tried adding a line like this BusID"PCI 01:00:0" to Section "Device"? Maybe also try "PCI 1:0:1" I had the same error with a different card and this helped. Thomas ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD-Current and XFree86
On Thu, 2003-10-23 at 17:00, James Tanis wrote: > Attempted this, first did a deinstall of XFree86-Server and then > built/installed XFree86-Server-snap. It built and installed perfectly fine, > from what I can see it runs fine too.. but I get the same error. You > weren't wrong, in the log once of the supported cards listed is the ATI > Radeon 9800 NH (AGP), although I have no idea what the NH stands for. The > only problem is I'm getting the same exact error I was previously.. > > From the log file: > (II) Primary Device is: PCI 01:00:0 > (--) Assigning device section with no busID to primary device > (WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) found > (EE) No devices detected. > > I did not attempt any different settings from the norm at this > time since, if my memory serves me right this is the same exact error I was > getting before and nothing I tried seemed to fix it. Here is the device > section as it is now for my radeon 9800, these are the same settings that I > used to use and worked perfectly fine with my radeon 7000, although I have > tried a config without the extra options it did not seems to help nor is > their any reason that I can think of that these options would not work with > the 9800. > > Section "Device" > Identifier "Radeon 9800" > Driver "radeon" > #VideoRam131072 > # Insert Clocks lines here if appropriate > Option "AGPMode" "4" > Option "AGPFastWrite" "1" > Option "EnablePageFlip""1" > EndSection > > My problems seem to stem from the fact that the driver has no idea > what to do with BusID PCI 1:0:1 which may or may not be the actual device > that I want to be using.. I have no idea what to do about it though. This > is a plain vanilla ATI Radeon 9800 (AGP) not a pro or some other > upgraded/downgraded version.. I would think this would be supported by the > driver. > Thanks again for any input, James. > > > > At 05:12 PM 10/23/2003, Eric Anholt wrote: > >On Thu, 2003-10-23 at 13:59, James Tanis wrote: > > > I'm having problems with XFree86 that result from the fact that > > > the ATI Radeon 9800 is not supported by the current 4.3.0 radeon driver. I > > > would like to upgrade to current/cvs version of XFree86, 4.3.99 since the > > > next release isn't going to be for around another 2 months. My question > > is, > > > what is the most flawless way to do this? Is there a FreeBSD concentric > > > repository, or should I just get the sources from the standard XFree86 cvs > > > repository? Is there a place where I can instead get frequently updated > > > ports of the repository? Building from source is there any configure > > > switches that I need to successfully build? Last but not least is it > > > possible to build only the radeon drivers and use those in 4.3.0.. if so, > > > how do I go about doing that? I had some problems when I only downloaded > > > the graphics drivers module. > > > Thanks for any > > > >Please use XFree86-4-Server-snap if you are looking for CVS X Server. > >The snap is slightly out of date due to problems getting 4.2.99.14 > >building (the monolithic nature of XFree86 is a major issue for > >maintaining these ports), but it should include radeon 9800 support. > > > >-- > >Eric Anholt[EMAIL PROTECTED] > >http://people.freebsd.org/~anholt/ [EMAIL PROTECTED] > > > > > >___ > >[EMAIL PROTECTED] mailing list > >http://lists.freebsd.org/mailman/listinfo/freebsd-current > >To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > James Tanis > Email: [EMAIL PROTECTED] > > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > I may be well out of my league here, but if memory serves you prolly will require DRI HEAD to run, that or XFree86 CVS. Maybe Eric knows better, but that's off my recolection with ATI experience. Requiring the DRI head, that or you can install the drivers from the linux distro, and just not the kernel driver for obvious reasons. I have been known from time to time to use the ATI linux modules in FreeBSD, works quite well actually. Just a thought for you to try. You'll either have it work, or maybe a hard lock or no luck. 50/50 Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD-Current and XFree86
Attempted this, first did a deinstall of XFree86-Server and then built/installed XFree86-Server-snap. It built and installed perfectly fine, from what I can see it runs fine too.. but I get the same error. You weren't wrong, in the log once of the supported cards listed is the ATI Radeon 9800 NH (AGP), although I have no idea what the NH stands for. The only problem is I'm getting the same exact error I was previously.. From the log file: (II) Primary Device is: PCI 01:00:0 (--) Assigning device section with no busID to primary device (WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) found (EE) No devices detected. I did not attempt any different settings from the norm at this time since, if my memory serves me right this is the same exact error I was getting before and nothing I tried seemed to fix it. Here is the device section as it is now for my radeon 9800, these are the same settings that I used to use and worked perfectly fine with my radeon 7000, although I have tried a config without the extra options it did not seems to help nor is their any reason that I can think of that these options would not work with the 9800. Section "Device" Identifier "Radeon 9800" Driver "radeon" #VideoRam131072 # Insert Clocks lines here if appropriate Option "AGPMode" "4" Option "AGPFastWrite" "1" Option "EnablePageFlip""1" EndSection My problems seem to stem from the fact that the driver has no idea what to do with BusID PCI 1:0:1 which may or may not be the actual device that I want to be using.. I have no idea what to do about it though. This is a plain vanilla ATI Radeon 9800 (AGP) not a pro or some other upgraded/downgraded version.. I would think this would be supported by the driver. Thanks again for any input, James. At 05:12 PM 10/23/2003, Eric Anholt wrote: On Thu, 2003-10-23 at 13:59, James Tanis wrote: > I'm having problems with XFree86 that result from the fact that > the ATI Radeon 9800 is not supported by the current 4.3.0 radeon driver. I > would like to upgrade to current/cvs version of XFree86, 4.3.99 since the > next release isn't going to be for around another 2 months. My question is, > what is the most flawless way to do this? Is there a FreeBSD concentric > repository, or should I just get the sources from the standard XFree86 cvs > repository? Is there a place where I can instead get frequently updated > ports of the repository? Building from source is there any configure > switches that I need to successfully build? Last but not least is it > possible to build only the radeon drivers and use those in 4.3.0.. if so, > how do I go about doing that? I had some problems when I only downloaded > the graphics drivers module. > Thanks for any Please use XFree86-4-Server-snap if you are looking for CVS X Server. The snap is slightly out of date due to problems getting 4.2.99.14 building (the monolithic nature of XFree86 is a major issue for maintaining these ports), but it should include radeon 9800 support. -- Eric Anholt[EMAIL PROTECTED] http://people.freebsd.org/~anholt/ [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]" James Tanis Email: [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD-Current and XFree86
On Thu, 2003-10-23 at 13:59, James Tanis wrote: > I'm having problems with XFree86 that result from the fact that > the ATI Radeon 9800 is not supported by the current 4.3.0 radeon driver. I > would like to upgrade to current/cvs version of XFree86, 4.3.99 since the > next release isn't going to be for around another 2 months. My question is, > what is the most flawless way to do this? Is there a FreeBSD concentric > repository, or should I just get the sources from the standard XFree86 cvs > repository? Is there a place where I can instead get frequently updated > ports of the repository? Building from source is there any configure > switches that I need to successfully build? Last but not least is it > possible to build only the radeon drivers and use those in 4.3.0.. if so, > how do I go about doing that? I had some problems when I only downloaded > the graphics drivers module. > Thanks for any Please use XFree86-4-Server-snap if you are looking for CVS X Server. The snap is slightly out of date due to problems getting 4.2.99.14 building (the monolithic nature of XFree86 is a major issue for maintaining these ports), but it should include radeon 9800 support. -- Eric Anholt[EMAIL PROTECTED] http://people.freebsd.org/~anholt/ [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD-Current and XFree86
I'm having problems with XFree86 that result from the fact that the ATI Radeon 9800 is not supported by the current 4.3.0 radeon driver. I would like to upgrade to current/cvs version of XFree86, 4.3.99 since the next release isn't going to be for around another 2 months. My question is, what is the most flawless way to do this? Is there a FreeBSD concentric repository, or should I just get the sources from the standard XFree86 cvs repository? Is there a place where I can instead get frequently updated ports of the repository? Building from source is there any configure switches that I need to successfully build? Last but not least is it possible to build only the radeon drivers and use those in 4.3.0.. if so, how do I go about doing that? I had some problems when I only downloaded the graphics drivers module. Thanks for any help, James James Tanis Email: [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problems with XFree86-4
On Tue, 2003-10-14 at 17:21, Rossam Souza Silva wrote: > Hi, I'm running 5.1-CURRENT (sources/ports from Oct/13) and > the X package isn't compiling: > > FeaNoR# make package > ===> Installing for XFree86-4.3.0,1 > ===> XFree86-4.3.0,1 depends on executable: xvinfo - not found > ===>Verifying package for xvinfo in /usr/ports/x11/XFree86-4-clients > ===> Building for XFree86-clients-4.3.0_3 > making all in lib/lbxutil/lbx_zlib... > making all in lib/lbxutil/delta... > making all in lib/lbxutil/image... > making all in programs/appres... > making all in programs/bdftopcf... > make: don't know how to make > /home/FreeBSD/ports/x11/XFree86-4-clients/work/xc/exports/lib/libfntstubs.a. > Stop > *** Error code 2 > > Stop in /home/FreeBSD/ports/x11/XFree86-4-clients/work/xc/programs. > *** Error code 1 > > Stop in /home/FreeBSD/ports/x11/XFree86-4-clients. > *** Error code 1 > > Stop in /home/FreeBSD/ports/x11/XFree86-4. > > I had this same error a week ago, someone have a clue? Fixed yesterday. cvsup and try again. (The fix is in XFree86-4-libraries/files/ and XFree86-4-clients/scripts -- you need to cvs update both before rebuilding -clients) -- Eric Anholt[EMAIL PROTECTED] http://people.freebsd.org/~anholt/ [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Problems with XFree86-4
Hi, I'm running 5.1-CURRENT (sources/ports from Oct/13) and the X package isn't compiling: FeaNoR# make package ===> Installing for XFree86-4.3.0,1 ===> XFree86-4.3.0,1 depends on executable: xvinfo - not found ===>Verifying package for xvinfo in /usr/ports/x11/XFree86-4-clients ===> Building for XFree86-clients-4.3.0_3 making all in lib/lbxutil/lbx_zlib... making all in lib/lbxutil/delta... making all in lib/lbxutil/image... making all in programs/appres... making all in programs/bdftopcf... make: don't know how to make /home/FreeBSD/ports/x11/XFree86-4-clients/work/xc/exports/lib/libfntstubs.a. Stop *** Error code 2 Stop in /home/FreeBSD/ports/x11/XFree86-4-clients/work/xc/programs. *** Error code 1 Stop in /home/FreeBSD/ports/x11/XFree86-4-clients. *** Error code 1 Stop in /home/FreeBSD/ports/x11/XFree86-4. I had this same error a week ago, someone have a clue? Rossam. -- "Das Leben auf Erden ist ein gemeiner Krieg. Wir spielen, wir kämpfen, wir setzen alles auf Sieg." Megaherz -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: XFree86-4-clients port broken.
On Mon, 2003-10-13 at 14:54, David Gilbert wrote: > I don't really have a clue where to look for this fix as there seems > to be a serious amount of magic going into the divided XFree86-4 port > builds, but my XFree86-4-clients port fails saying: > > make: don't know how to make > /usr/ports/x11/XFree86-4-clients/work/xc/exports/lib/libfntstubs.a. Stop > > Dave. It should be fixed now. Please cvsup (in ~1hour) and try again. -- Eric Anholt[EMAIL PROTECTED] http://people.freebsd.org/~anholt/ [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: XFree86-4-clients port broken.
>>>>> "Peter" == Peter Wemm <[EMAIL PROTECTED]> writes: Peter> Eric Anholt wrote: >> On Mon, 2003-10-13 at 15:51, Peter Wemm wrote: > David Gilbert >> wrote: > > I don't really have a clue where to look for this fix as >> there seems > > to be a serious amount of magic going into the >> divided XFree86-4 port > > builds, but my XFree86-4-clients port >> fails saying: >> > > >> > > make: don't know how to make >> /usr/ports/x11/XFree86-4-clients/work/xc/exp Peter> orts >> > /lib/libfntstubs.a. Stop >> > >> > I ran into this on my amd64 box too. Is yours an i386? >> >> This is a problem on ref5, too. I am testing a fix right now. The >> confusing part is I can't find any change I (or anyone else) has >> made that would have caused this. Peter> Does the port have any exposure to make(1) at all? Its been Peter> futzed with fairly recently. I know it's supposed to use Peter> gmake, but perhaps there are still some "make" references? If you look at the port, it uses make fairly extensively now. The Makefile (from my limited understanding) seems to charge into building the port without calling gmake by adding sub directories much like the /usr/src makefile seems to do. Dave. -- |David Gilbert, Independent Contractor. | Two things can only be | |Mail: [EMAIL PROTECTED]| equal if and only if they | |http://daveg.ca | are precisely opposite. | =GLO ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: XFree86-4-clients port broken.
>>>>> "Peter" == Peter Wemm <[EMAIL PROTECTED]> writes: Peter> David Gilbert wrote: >> I don't really have a clue where to look for this fix as there >> seems to be a serious amount of magic going into the divided >> XFree86-4 port builds, but my XFree86-4-clients port fails saying: >> >> make: don't know how to make >> /usr/ports/x11/XFree86-4-clients/work/xc/exports Peter> /lib/libfntstubs.a. Stop Peter> I ran into this on my amd64 box too. Is yours an i386? Yes. I'm getting it on an intel centrino. Dave. -- |David Gilbert, Independent Contractor. | Two things can only be | |Mail: [EMAIL PROTECTED]| equal if and only if they | |http://daveg.ca | are precisely opposite. | =GLO ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: XFree86-4-clients port broken.
On Mon, 2003-10-13 at 16:05, Peter Wemm wrote: > Eric Anholt wrote: > > On Mon, 2003-10-13 at 15:51, Peter Wemm wrote: > > > David Gilbert wrote: > > > > I don't really have a clue where to look for this fix as there seems > > > > to be a serious amount of magic going into the divided XFree86-4 port > > > > builds, but my XFree86-4-clients port fails saying: > > > > > > > > make: don't know how to make /usr/ports/x11/XFree86-4-clients/work/xc/exp > orts > > > /lib/libfntstubs.a. Stop > > > > > > I ran into this on my amd64 box too. Is yours an i386? > > > > This is a problem on ref5, too. I am testing a fix right now. The > > confusing part is I can't find any change I (or anyone else) has made > > that would have caused this. > > Does the port have any exposure to make(1) at all? Its been futzed with > fairly recently. I know it's supposed to use gmake, but perhaps there are > still some "make" references? No, actually it uses the system (bsd) make. It generally is pretty resistant to differences with different types of make, though. Testing a new idea for a fix that will cut the build time/space required, too. -- Eric Anholt[EMAIL PROTECTED] http://people.freebsd.org/~anholt/ [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: XFree86-4-clients port broken.
Eric Anholt wrote: > On Mon, 2003-10-13 at 15:51, Peter Wemm wrote: > > David Gilbert wrote: > > > I don't really have a clue where to look for this fix as there seems > > > to be a serious amount of magic going into the divided XFree86-4 port > > > builds, but my XFree86-4-clients port fails saying: > > > > > > make: don't know how to make /usr/ports/x11/XFree86-4-clients/work/xc/exp orts > > /lib/libfntstubs.a. Stop > > > > I ran into this on my amd64 box too. Is yours an i386? > > This is a problem on ref5, too. I am testing a fix right now. The > confusing part is I can't find any change I (or anyone else) has made > that would have caused this. Does the port have any exposure to make(1) at all? Its been futzed with fairly recently. I know it's supposed to use gmake, but perhaps there are still some "make" references? Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: XFree86-4-clients port broken.
On Mon, 2003-10-13 at 15:51, Peter Wemm wrote: > David Gilbert wrote: > > I don't really have a clue where to look for this fix as there seems > > to be a serious amount of magic going into the divided XFree86-4 port > > builds, but my XFree86-4-clients port fails saying: > > > > make: don't know how to make /usr/ports/x11/XFree86-4-clients/work/xc/exports > /lib/libfntstubs.a. Stop > > I ran into this on my amd64 box too. Is yours an i386? This is a problem on ref5, too. I am testing a fix right now. The confusing part is I can't find any change I (or anyone else) has made that would have caused this. -- Eric Anholt[EMAIL PROTECTED] http://people.freebsd.org/~anholt/ [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: XFree86-4-clients port broken.
On Mon, Oct 13, 2003 at 03:51:06PM -0700, Peter Wemm wrote: > David Gilbert wrote: > > I don't really have a clue where to look for this fix as there seems > > to be a serious amount of magic going into the divided XFree86-4 port > > builds, but my XFree86-4-clients port fails saying: > > > > make: don't know how to make /usr/ports/x11/XFree86-4-clients/work/xc/exports > /lib/libfntstubs.a. Stop > > I ran into this on my amd64 box too. Is yours an i386? The port is broken on all architectures. anholt is looking into it. Kris pgp0.pgp Description: PGP signature
Re: XFree86-4-clients port broken.
David Gilbert wrote: > I don't really have a clue where to look for this fix as there seems > to be a serious amount of magic going into the divided XFree86-4 port > builds, but my XFree86-4-clients port fails saying: > > make: don't know how to make /usr/ports/x11/XFree86-4-clients/work/xc/exports /lib/libfntstubs.a. Stop I ran into this on my amd64 box too. Is yours an i386? Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
XFree86-4-clients port broken.
I don't really have a clue where to look for this fix as there seems to be a serious amount of magic going into the divided XFree86-4 port builds, but my XFree86-4-clients port fails saying: make: don't know how to make /usr/ports/x11/XFree86-4-clients/work/xc/exports/lib/libfntstubs.a. Stop Dave. -- |David Gilbert, Independent Contractor. | Two things can only be | |Mail: [EMAIL PROTECTED]| equal if and only if they | |http://daveg.ca | are precisely opposite. | =GLO ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Failed building XFree86-4-clients
On Tue, Oct 07, 2003 at 12:06:31PM -0700, James Satterfield wrote: > On a recent -current > FreeBSD bishop.uberduper.com 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Mon Oct 6 > 15:12:45 PDT 2003 > I am unable to build XFree86-4-clients from ports. Here's the last little bits > from the build. > > macro "in" not recognized -- ignoring > making all in programs/bdftopcf... > cc -O -pipe -mcpu=pentiumpro -ansi -Dasm=__asm -Wall -Wpointer-arith -Wundef > -I/usr/ports/x11/XFree86-4-clients/work/xc/include/fonts > -I/usr/ports/x11/XFree86-4-clients/work/xc/lib/font/include > -I/usr/ports/x11/XFree86-4-clients/work/xc/lib/font/bitmap > -I/usr/ports/x11/XFree86-4-clients/work/xc > -I/usr/ports/x11/XFree86-4-clients/work/xc/exports/include > -I/usr/X11R6/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -c > bdftopcf.c > In file included from /usr/include/string.h:40, > from > /usr/ports/x11/XFree86-4-clients/work/xc/exports/include/X11/Xfuncs.h:49, > from > /usr/ports/x11/XFree86-4-clients/work/xc/lib/font/include/fontmisc.h:38, > from bdftopcf.c:34: > /usr/include/sys/cdefs.h:173:51: warning: "__STDC_VERSION__" is not defined > /usr/include/sys/cdefs.h:184:5: warning: "__STDC_VERSION__" is not defined > /usr/include/sys/cdefs.h:372:5: warning: "_POSIX_C_SOURCE" is not defined > /usr/include/sys/cdefs.h:378:5: warning: "_POSIX_C_SOURCE" is not defined > make: don't know how to make > /usr/ports/x11/XFree86-4-clients/work/xc/exports/lib/libfntstubs.a. Stop > *** Error code 2 > > Any ideas? > > James. Well, I'm sure there's a *right* way to do this, but I got the installation to go through by copying the contents of /usr/ports/x11/XFree86-4-libraries/work/xc/exports/lib (which now that I look at it are links) to XFree86-4-clients/blah/blah... Good luck. Greg ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Failed building XFree86-4-clients
On a recent -current FreeBSD bishop.uberduper.com 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Mon Oct 6 15:12:45 PDT 2003 I am unable to build XFree86-4-clients from ports. Here's the last little bits from the build. macro "in" not recognized -- ignoring making all in programs/bdftopcf... cc -O -pipe -mcpu=pentiumpro -ansi -Dasm=__asm -Wall -Wpointer-arith -Wundef -I/usr/ports/x11/XFree86-4-clients/work/xc/include/fonts -I/usr/ports/x11/XFree86-4-clients/work/xc/lib/font/include -I/usr/ports/x11/XFree86-4-clients/work/xc/lib/font/bitmap -I/usr/ports/x11/XFree86-4-clients/work/xc -I/usr/ports/x11/XFree86-4-clients/work/xc/exports/include -I/usr/X11R6/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -c bdftopcf.c In file included from /usr/include/string.h:40, from /usr/ports/x11/XFree86-4-clients/work/xc/exports/include/X11/Xfuncs.h:49, from /usr/ports/x11/XFree86-4-clients/work/xc/lib/font/include/fontmisc.h:38, from bdftopcf.c:34: /usr/include/sys/cdefs.h:173:51: warning: "__STDC_VERSION__" is not defined /usr/include/sys/cdefs.h:184:5: warning: "__STDC_VERSION__" is not defined /usr/include/sys/cdefs.h:372:5: warning: "_POSIX_C_SOURCE" is not defined /usr/include/sys/cdefs.h:378:5: warning: "_POSIX_C_SOURCE" is not defined make: don't know how to make /usr/ports/x11/XFree86-4-clients/work/xc/exports/lib/libfntstubs.a. Stop *** Error code 2 Any ideas? James. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
linux emu, syscall, sysctl, XFree86
While doing a portupgrade on my 5.0R->5.1-CURRENT migrated
system I just saw the following message pass by on my screen:
XFree86-libs-4.0.3-5.i386.rpm
/sbin/ldconfig: File /usr/lib/libGL.so.1.0.4365 is too small, not checked.
/sbin/ldconfig: File /usr/lib/libGL.so.1 is too small, not checked.
[32mlinux: pid 41294 (glidelink): sysctl {1,23} is not implemented[0m
[32mlinux: pid 41294 (glidelink): syscall syslog not implemented[0m
[32mlinux: pid 41294 (glidelink): syscall syslog not implemented[0m
zlib-1.1.4-8.7x.i386.rpm
/sbin/ldconfig: File /usr/lib/libGL.so.1.0.4365 is too small, not checked.
/sbin/ldconfig: File /usr/lib/libGL.so.1 is too small, not checked.
libstdc++-2.96-112.7.1.i386.rpm
/sbin/ldconfig: File /usr/lib/libGL.so.1.0.4365 is too small, not checked.
/sbin/ldconfig: File /usr/lib/libGL.so.1 is too small, not checked.
kern.fallback_elf_brand: 3 -> -1
install -m 644 /u/ports/emulators/linux_base/files/yp.conf /compat/linux/etc
/usr/bin/touch /compat/linux/etc/mtab
Installation of the Linux base system is finished. The Linux kernel
mode, which must be enabled for Linux binaries to run, is now
enabled. Linux mode can be enabled permanently with the linux_enable
variable of rc.conf(5).
When using NIS, don't forget to edit yp.conf in /compat/linux/etc.
===> Registering installation for linux_base-7.1_5
The escaped (please forgive the escape sequences) were kernel
messages.
--
Chris Christoph P. U. Kukulies kukulies (at) rwth-aachen.de
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem with PS/2 mouse driver in XFree86 4.3.0
On Sun, 10 Aug 2003, Daniel Flickinger wrote: > I had the same problem starting about a year ago when I > finally gave up and upgraded to X4. The problem appears > to be that the X4 driver does not disable the console > mouse and the two of them fight over the interrupts. Well yeah moused and X can't both use the mouse at once. You should get a 'device busy' error. If you want to use moused then have X gets its events from moused (/dev/sysmouse) and not psm0. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem with PS/2 mouse driver in XFree86 4.3.0
Not to undermine what you guys said, but this is unrelated to the original post I think. The problem I was having related to acpi, which Shizuka pointed out. I'm not trying to play nanny here, just don't want people to get confused =) On Sun, 2003-08-10 at 21:16, Daniel Flickinger wrote: > Sent: Sun, 10 Aug 2003 15:32:28 -0700 (PDT) by Doug White > > + On Sun, 10 Aug 2003, Daniel Flickinger wrote: > + > + > I had the same problem starting about a year ago when I > + > finally gave up and upgraded to X4. The problem appears > + > to be that the X4 driver does not disable the console > + > mouse and the two of them fight over the interrupts. > + > + Well yeah moused and X can't both use the mouse at once. You > + should get a 'device busy' error. If you want to use moused > + then have X gets its events from moused (/dev/sysmouse) and > + not psm0. > > That's what I did, as I had done in the past with X3 > --upgrading to X4 is when the problem came up, and yes, > you get a mouse busy when you move it to /dev/psm0. > However, if you do not start the mouse for the virtual > screens (which I had no need for anyway), /dev/psm0 can > be opened for X4. > > Secondly, at the time, Xconfig would not accept > /dev/sysmouse as a ps2 style mouse and would not track > if I called it a generic mouse... that may have changed. > > CAVEAT: I admit that I have not revisted the problem > since then which was at least a year ago --it works, I > leave it alone despite several X4 upgrades. The remedy > at the time was to use /dev/psm0, not /dev/sysmouse. > Maybe in the next upgrade I'll revisit the aggravation > since I would prefer to be able to use virtual X > sessions on separate logins. > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
XFree86 on FreeBSD 5.1 w/ATI M9
I have an HP Compaq Presario X1000 (Model X1018CL) with an ATI Mobility Radeon 9200 (M9 / RV250?) and a 15.4" widescreen WSXGA+ capable of 1280x800. I installed XFree86 4.3.0 on FreeBSD 5.1 and it seems like the only odd message I'm getting before aborting the startx is a warning about a bad v_bios checksum. Any ideas on how to get this to work? I searched around and found a post similar to mine at http://lists.freebsd.org/pipermail/freebsd-stable/2003-April/000542.html , but there was no associated answer. I had X running with Mandrake 9.1 on the same computer, so I'm not sure what the problem may be. Also, at first there was a problem with not loading a certain library module. I just added a "Load "ddc"" in the "module" section of my XF86Config to fix that unresolved symbol. Thanks, Sukhjeet Attachment(s) XFree86.0.log XFree86.0.log Description: Binary data ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem with PS/2 mouse driver in XFree86 4.3.0
Yes, adding hint.acpi.0.disabled="1" to /boot/device.hints fixed the mouse problem. While this is somewhat pleasing, it also leaves me with uncertainty. I tried tweaking basically every CMOS combination I could think of. Do you suppose this is an incompatability between the apci driver and my motherboard? The behavior makes it appear as if something else is fighting over the same resources that the mouse uses. This would explain why it can only access the device once a second. When BIOS initializes, it does not list any other device with an IRQ of 12 (which I believe is the mouse interface). Does anyone have any experience with devices such as mice flaking out with apci? Thanks again! -Mike Bohan On Sun, 2003-08-10 at 04:02, Shizuka Kudo wrote: > --- Mike Bohan <[EMAIL PROTECTED]> wrote: > > Hello, > > > > I have an Abit KT266 based motherboard and am having some trouble using > > the PS/2 mouse driver under XFree86. I have the protocol set to "auto", > > and the device set to /dev/psm0. This configuration has worked with > > this same Intellimouse in the past. The symptoms are that that when the > > mouse is moved, the cursor is only updated about once a second. After > > searching google, I found the following URL in which another person > > experienced the same problem (from freebsd-bugs). Apparently it only > > shows up on certain chipsets (VIA based). I tried several other PS/2 > > mice, to no avail (same outcome). My system is running a day old > > -current build, but this other fellow reported the problem in 5.0 (does > > not affect 4.x). I'm wondering if anyone else has experienced this > > problem, and if so, are there any work-arounds? I've attached my > > 'dmesg' output, in the hopes that the information will be of value. > > Thank you in advance! > > > > Does disabling acpi make your mouse working? > > > URL: > > http://lists.freebsd.org/pipermail/freebsd-bugs/2003-April/000426.html > > > > -Mike Bohan > > > > Copyright (c) 1992-2003 The FreeBSD Project. > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > > The Regents of the University of California. All rights > > reserved. > > FreeBSD 5.1-CURRENT #3: Fri Aug 8 09:10:54 EDT 2003 > > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CABOOSE > > Preloaded elf kernel "/boot/kernel/kernel" at 0xc0424000. > > Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0424244. > > Timecounter "i8254" frequency 1193182 Hz > > CPU: AMD Athlon(tm) processor (1333.91-MHz 686-class CPU) > > Origin = "AuthenticAMD" Id = 0x644 Stepping = 4 > > > > > Features=0x183fbff > > AMD Features=0xc044 > > real memory = 268369920 (255 MB) > > avail memory = 256196608 (244 MB) > > Pentium Pro MTRR support enabled > > npx0: on motherboard > > npx0: INT 16 interface > > acpi0: on motherboard > > pcibios: BIOS version 2.10 > > Using $PIR table, 8 entries at 0xc00fdef0 > > acpi0: power button is handled as a fixed feature programming model. > > Timecounter "ACPI-fast" frequency 3579545 Hz > > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 > > acpi_cpu0: on acpi0 > > acpi_tz0: on acpi0 > > acpi_button0: on acpi0 > > acpi_button1: on acpi0 > > pcib0: port > > 0x5000-0x500f,0x4080-0x40ff,0x4000-0x407f,0xcf8-0xcff on acpi0 > > pci0: on pcib0 > > pcib0: slot 8 INTA is routed to irq 10 > > pcib0: slot 9 INTA is routed to irq 5 > > pcib0: slot 11 INTA is routed to irq 10 > > agp0: mem 0xe800-0xebff at > > device 0.0 on pci0 > > pcib1: at device 1.0 on pci0 > > pci1: on pcib1 > > pcib0: slot 1 INTA is routed to irq 11 > > pcib1: slot 0 INTA is routed to irq 11 > > pci1: at device 0.0 (no driver attached) > > dc0: port 0xd000-0xd0ff mem > > 0xef00-0xef0003ff irq 10 at device 8.0 on pci0 > > dc0: Ethernet address: 00:04:5a:40:b5:0d > > miibus0: on dc0 > > ukphy0: on miibus0 > > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > > dc1: port 0xd400-0xd4ff mem > > 0xef001000-0xef0010ff irq 5 at device 9.0 on pci0 > > dc1: Ethernet address: 00:a0:cc:34:54:93 > > miibus1: on dc1 > > dcphy0: on miibus1 > > dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > > dc2: <82c169 PNIC 10/100BaseTX> port 0xd800-0xd8ff mem > > 0xef002000-0xef0020ff irq 10 at device 11.0 on pci0 > > dc2:
Problem with PS/2 mouse driver in XFree86 4.3.0
Hello, I have an Abit KT266 based motherboard and am having some trouble using the PS/2 mouse driver under XFree86. I have the protocol set to "auto", and the device set to /dev/psm0. This configuration has worked with this same Intellimouse in the past. The symptoms are that that when the mouse is moved, the cursor is only updated about once a second. After searching google, I found the following URL in which another person experienced the same problem (from freebsd-bugs). Apparently it only shows up on certain chipsets (VIA based). I tried several other PS/2 mice, to no avail (same outcome). My system is running a day old -current build, but this other fellow reported the problem in 5.0 (does not affect 4.x). I'm wondering if anyone else has experienced this problem, and if so, are there any work-arounds? I've attached my 'dmesg' output, in the hopes that the information will be of value. Thank you in advance! URL: http://lists.freebsd.org/pipermail/freebsd-bugs/2003-April/000426.html -Mike Bohan Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-CURRENT #3: Fri Aug 8 09:10:54 EDT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CABOOSE Preloaded elf kernel "/boot/kernel/kernel" at 0xc0424000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0424244. Timecounter "i8254" frequency 1193182 Hz CPU: AMD Athlon(tm) processor (1333.91-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x644 Stepping = 4 Features=0x183fbff AMD Features=0xc044 real memory = 268369920 (255 MB) avail memory = 256196608 (244 MB) Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard pcibios: BIOS version 2.10 Using $PIR table, 8 entries at 0xc00fdef0 acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 acpi_cpu0: on acpi0 acpi_tz0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0x5000-0x500f,0x4080-0x40ff,0x4000-0x407f,0xcf8-0xcff on acpi0 pci0: on pcib0 pcib0: slot 8 INTA is routed to irq 10 pcib0: slot 9 INTA is routed to irq 5 pcib0: slot 11 INTA is routed to irq 10 agp0: mem 0xe800-0xebff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pcib0: slot 1 INTA is routed to irq 11 pcib1: slot 0 INTA is routed to irq 11 pci1: at device 0.0 (no driver attached) dc0: port 0xd000-0xd0ff mem 0xef00-0xef0003ff irq 10 at device 8.0 on pci0 dc0: Ethernet address: 00:04:5a:40:b5:0d miibus0: on dc0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc1: port 0xd400-0xd4ff mem 0xef001000-0xef0010ff irq 5 at device 9.0 on pci0 dc1: Ethernet address: 00:a0:cc:34:54:93 miibus1: on dc1 dcphy0: on miibus1 dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc2: <82c169 PNIC 10/100BaseTX> port 0xd800-0xd8ff mem 0xef002000-0xef0020ff irq 10 at device 11.0 on pci0 dc2: Ethernet address: 00:a0:cc:d6:ea:b4 miibus2: on dc2 bmtphy0: on miibus2 bmtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: at device 17.0 on pci0 isa0: on isab0 atapci0: port 0xdc00-0xdc0f at device 17.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 orm0: at iomem 0xc-0xcbfff on isa0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> Timecounter "TSC" frequency 1333905046 Hz Timecounters tick every 1.000 msec DUMMYNET initialized (011031) ipfw2 initialized, divert disabled, rule-based forwarding enabled, default to accept, logging disabled IP Filter: v3.4.31 initialized. Default = pass all, Logging = enabled acpi_cpu: throttling enabled, 2 steps (100% to 50.0%), currently 100.0% ad0: 39083MB [79408/16/63] at ata0-master UDMA100 ad1: 29333MB [59598/16/63] at ata0-slave UDMA66 ad2: 43979MB [89355/16/63] at ata1-master UDMA100 ad3: 43979MB [89355/16/63] at ata1-slave UDMA100 Mounting root from ufs:/dev/ad0s1a ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem with PS/2 mouse driver in XFree86 4.3.0
That indeed fixed the problem. It does appear like the problem relates
to a
specific BIOS version. I'm wondering if there's a certain set of people
I
should forward this information on to? It would be nice if a fix like
this could
find its way into the -current tree. Thank you Shizuka for your
intuitive thinking,
otherwise I surely never would have found a practical solution.
-Mike Bohan
On Sun, 2003-08-10 at 11:35, Shizuka Kudo wrote:
> --- Mike Bohan <[EMAIL PROTECTED]> wrote:
> > Yes, adding hint.acpi.0.disabled="1" to /boot/device.hints fixed the
> > mouse problem.
>
> Try this patch on acpi and see if it solves your problem.
>
> --- sys/dev/acpica/acpi_pci_link.c.orig Thu Jan 2 02:48:49 2003
> +++ sys/dev/acpica/acpi_pci_link.c Fri Feb 28 15:18:55 2003
> @@ -461,7 +461,10 @@
> return_ACPI_STATUS (error);
> }
>
> +/*
> if (!(sta & (ACPI_STA_PRESENT | ACPI_STA_FUNCTIONAL))) {
> +*/
> + if (!(sta & ACPI_STA_ENABLE)) {
> ACPI_DEBUG_PRINT((ACPI_DB_ERROR,
> "PCI interrupt link is not functional - %s\n",
> acpi_name(handle)));
>
>
> > While this is somewhat pleasing, it also leaves me with uncertainty. I
> > tried tweaking
> > basically every CMOS combination I could think of. Do you suppose this
> > is an
> > incompatability between the apci driver and my motherboard? The behavior
>
> I bet you might have problem with parallel port as well. My machine suffered
> from this behaviour when someone made the change as shown on the patch. I just
> reverted that one. If the patch solves your problem, I believe that this is
> related to BIOS not chipset. I have a Celeron on i815ep and the acpi message is
> shown below. I just notice that you have a similar acpi signature like mime.
>
> acpi0: on motherboard
> pcibios: BIOS version 2.10
> Using $PIR table, 10 entries at 0xc00fded0
>
> Good luck.
>
> > makes
> > it appear as if something else is fighting over the same resources that
> > the mouse uses.
> > This would explain why it can only access the device once a second.
> > When BIOS
> > initializes, it does not list any other device with an IRQ of 12 (which
> > I believe is the mouse interface).
> > Does anyone have any experience with devices such as mice flaking out
> > with apci?
> > Thanks again!
> >
> > -Mike Bohan
> >
> >
> > On Sun, 2003-08-10 at 04:02, Shizuka Kudo wrote:
> >
> > > --- Mike Bohan <[EMAIL PROTECTED]> wrote:
> > > > Hello,
> > > >
> > > > I have an Abit KT266 based motherboard and am having some trouble using
> > > > the PS/2 mouse driver under XFree86. I have the protocol set to "auto",
> > > > and the device set to /dev/psm0. This configuration has worked with
> > > > this same Intellimouse in the past. The symptoms are that that when the
> > > > mouse is moved, the cursor is only updated about once a second. After
> > > > searching google, I found the following URL in which another person
> > > > experienced the same problem (from freebsd-bugs). Apparently it only
> > > > shows up on certain chipsets (VIA based). I tried several other PS/2
> > > > mice, to no avail (same outcome). My system is running a day old
> > > > -current build, but this other fellow reported the problem in 5.0 (does
> > > > not affect 4.x). I'm wondering if anyone else has experienced this
> > > > problem, and if so, are there any work-arounds? I've attached my
> > > > 'dmesg' output, in the hopes that the information will be of value.
> > > > Thank you in advance!
> > > >
> > >
> > > Does disabling acpi make your mouse working?
> > >
> > > > URL:
> > > > http://lists.freebsd.org/pipermail/freebsd-bugs/2003-April/000426.html
> > > >
> > > > -Mike Bohan
> > > >
> > > > Copyright (c) 1992-2003 The FreeBSD Project.
> > > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
> > > > The Regents of the University of California. All rights
> > > > reserved.
> > > > FreeBSD 5.1-CURRENT #3: Fri Aug 8 09:10:54 EDT 2003
> > > > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CABOOSE
> > > > Preloaded elf kernel "
Re: Problem with PS/2 mouse driver in XFree86 4.3.0
--- Mike Bohan <[EMAIL PROTECTED]> wrote: > Hello, > > I have an Abit KT266 based motherboard and am having some trouble using > the PS/2 mouse driver under XFree86. I have the protocol set to "auto", > and the device set to /dev/psm0. This configuration has worked with > this same Intellimouse in the past. The symptoms are that that when the > mouse is moved, the cursor is only updated about once a second. After > searching google, I found the following URL in which another person > experienced the same problem (from freebsd-bugs). Apparently it only > shows up on certain chipsets (VIA based). I tried several other PS/2 > mice, to no avail (same outcome). My system is running a day old > -current build, but this other fellow reported the problem in 5.0 (does > not affect 4.x). I'm wondering if anyone else has experienced this > problem, and if so, are there any work-arounds? I've attached my > 'dmesg' output, in the hopes that the information will be of value. > Thank you in advance! > Does disabling acpi make your mouse working? > URL: > http://lists.freebsd.org/pipermail/freebsd-bugs/2003-April/000426.html > > -Mike Bohan > > Copyright (c) 1992-2003 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights > reserved. > FreeBSD 5.1-CURRENT #3: Fri Aug 8 09:10:54 EDT 2003 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CABOOSE > Preloaded elf kernel "/boot/kernel/kernel" at 0xc0424000. > Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0424244. > Timecounter "i8254" frequency 1193182 Hz > CPU: AMD Athlon(tm) processor (1333.91-MHz 686-class CPU) > Origin = "AuthenticAMD" Id = 0x644 Stepping = 4 > > Features=0x183fbff > AMD Features=0xc044 > real memory = 268369920 (255 MB) > avail memory = 256196608 (244 MB) > Pentium Pro MTRR support enabled > npx0: on motherboard > npx0: INT 16 interface > acpi0: on motherboard > pcibios: BIOS version 2.10 > Using $PIR table, 8 entries at 0xc00fdef0 > acpi0: power button is handled as a fixed feature programming model. > Timecounter "ACPI-fast" frequency 3579545 Hz > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 > acpi_cpu0: on acpi0 > acpi_tz0: on acpi0 > acpi_button0: on acpi0 > acpi_button1: on acpi0 > pcib0: port > 0x5000-0x500f,0x4080-0x40ff,0x4000-0x407f,0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib0: slot 8 INTA is routed to irq 10 > pcib0: slot 9 INTA is routed to irq 5 > pcib0: slot 11 INTA is routed to irq 10 > agp0: mem 0xe800-0xebff at > device 0.0 on pci0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > pcib0: slot 1 INTA is routed to irq 11 > pcib1: slot 0 INTA is routed to irq 11 > pci1: at device 0.0 (no driver attached) > dc0: port 0xd000-0xd0ff mem > 0xef00-0xef0003ff irq 10 at device 8.0 on pci0 > dc0: Ethernet address: 00:04:5a:40:b5:0d > miibus0: on dc0 > ukphy0: on miibus0 > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > dc1: port 0xd400-0xd4ff mem > 0xef001000-0xef0010ff irq 5 at device 9.0 on pci0 > dc1: Ethernet address: 00:a0:cc:34:54:93 > miibus1: on dc1 > dcphy0: on miibus1 > dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > dc2: <82c169 PNIC 10/100BaseTX> port 0xd800-0xd8ff mem > 0xef002000-0xef0020ff irq 10 at device 11.0 on pci0 > dc2: Ethernet address: 00:a0:cc:d6:ea:b4 > miibus2: on dc2 > bmtphy0: on miibus2 > bmtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > isab0: at device 17.0 on pci0 > isa0: on isab0 > atapci0: port 0xdc00-0xdc0f at device > 17.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > fdc0: port > 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > atkbdc0: port 0x64,0x60 irq 1 on acpi0 > atkbd0: flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0 > psm0: irq 12 on atkbdc0 > psm0: model IntelliMouse, device ID 3 > orm0: at iomem 0xc-0xcbfff on isa0 > vga0: at port 0x3c0-0x3df iomem 0xa-0xb on > isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > Timecounter "TSC" frequency 1333905046 Hz > Timecounters tick every 1.000 msec > DUMMYNET initialized (011031) > ipfw2 initialized, divert disabled, rule-based forwarding enabled, > default to accept, logging disabled > IP Filter: v3.4.31 initialized. Default = pass all, Logging = enabled > acpi_cpu: throttlin
Re: Problem with PS/2 mouse driver in XFree86 4.3.0
--- Mike Bohan <[EMAIL PROTECTED]> wrote:
> That indeed fixed the problem. It does appear like the problem relates
> to a
> specific BIOS version. I'm wondering if there's a certain set of people
> I
> should forward this information on to? It would be nice if a fix like
I have reported this problem two times, but seems got no interest. Here's the last
message I sent
to the list regarding this.
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1580299+0+archive/2003/freebsd-current/20030427.freebsd-current
> this could
> find its way into the -current tree. Thank you Shizuka for your
> intuitive thinking,
> otherwise I surely never would have found a practical solution.
>
> -Mike Bohan
>
>
>
> On Sun, 2003-08-10 at 11:35, Shizuka Kudo wrote:
>
> > --- Mike Bohan <[EMAIL PROTECTED]> wrote:
> > > Yes, adding hint.acpi.0.disabled="1" to /boot/device.hints fixed the
> > > mouse problem.
> >
> > Try this patch on acpi and see if it solves your problem.
> >
> > --- sys/dev/acpica/acpi_pci_link.c.orig Thu Jan 2 02:48:49 2003
> > +++ sys/dev/acpica/acpi_pci_link.c Fri Feb 28 15:18:55 2003
> > @@ -461,7 +461,10 @@
> > return_ACPI_STATUS (error);
> > }
> >
> > +/*
> > if (!(sta & (ACPI_STA_PRESENT | ACPI_STA_FUNCTIONAL))) {
> > +*/
> > + if (!(sta & ACPI_STA_ENABLE)) {
> > ACPI_DEBUG_PRINT((ACPI_DB_ERROR,
> > "PCI interrupt link is not functional - %s\n",
> > acpi_name(handle)));
> >
> >
> > > While this is somewhat pleasing, it also leaves me with uncertainty. I
> > > tried tweaking
> > > basically every CMOS combination I could think of. Do you suppose this
> > > is an
> > > incompatability between the apci driver and my motherboard? The behavior
> >
> > I bet you might have problem with parallel port as well. My machine suffered
> > from this behaviour when someone made the change as shown on the patch. I just
> > reverted that one. If the patch solves your problem, I believe that this is
> > related to BIOS not chipset. I have a Celeron on i815ep and the acpi message is
> > shown below. I just notice that you have a similar acpi signature like mime.
> >
> > acpi0: on motherboard
> > pcibios: BIOS version 2.10
> > Using $PIR table, 10 entries at 0xc00fded0
> >
> > Good luck.
> >
> > > makes
> > > it appear as if something else is fighting over the same resources that
> > > the mouse uses.
> > > This would explain why it can only access the device once a second.
> > > When BIOS
> > > initializes, it does not list any other device with an IRQ of 12 (which
> > > I believe is the mouse interface).
> > > Does anyone have any experience with devices such as mice flaking out
> > > with apci?
> > > Thanks again!
> > >
> > > -Mike Bohan
> > >
> > >
> > > On Sun, 2003-08-10 at 04:02, Shizuka Kudo wrote:
> > >
> > > > --- Mike Bohan <[EMAIL PROTECTED]> wrote:
> > > > > Hello,
> > > > >
> > > > > I have an Abit KT266 based motherboard and am having some trouble using
> > > > > the PS/2 mouse driver under XFree86. I have the protocol set to "auto",
> > > > > and the device set to /dev/psm0. This configuration has worked with
> > > > > this same Intellimouse in the past. The symptoms are that that when the
> > > > > mouse is moved, the cursor is only updated about once a second. After
> > > > > searching google, I found the following URL in which another person
> > > > > experienced the same problem (from freebsd-bugs). Apparently it only
> > > > > shows up on certain chipsets (VIA based). I tried several other PS/2
> > > > > mice, to no avail (same outcome). My system is running a day old
> > > > > -current build, but this other fellow reported the problem in 5.0 (does
> > > > > not affect 4.x). I'm wondering if anyone else has experienced this
> > > > > problem, and if so, are there any work-arounds? I've attached my
> > > > > 'dmesg' output, in the hopes that the information will be of value.
> > > > > Thank you in advance!
> > > > >
> > > >
> > > > Do
Re: Problem with PS/2 mouse driver in XFree86 4.3.0
--- Mike Bohan <[EMAIL PROTECTED]> wrote:
> Yes, adding hint.acpi.0.disabled="1" to /boot/device.hints fixed the
> mouse problem.
Try this patch on acpi and see if it solves your problem.
--- sys/dev/acpica/acpi_pci_link.c.orig Thu Jan 2 02:48:49 2003
+++ sys/dev/acpica/acpi_pci_link.c Fri Feb 28 15:18:55 2003
@@ -461,7 +461,10 @@
return_ACPI_STATUS (error);
}
+/*
if (!(sta & (ACPI_STA_PRESENT | ACPI_STA_FUNCTIONAL))) {
+*/
+ if (!(sta & ACPI_STA_ENABLE)) {
ACPI_DEBUG_PRINT((ACPI_DB_ERROR,
"PCI interrupt link is not functional - %s\n",
acpi_name(handle)));
> While this is somewhat pleasing, it also leaves me with uncertainty. I
> tried tweaking
> basically every CMOS combination I could think of. Do you suppose this
> is an
> incompatability between the apci driver and my motherboard? The behavior
I bet you might have problem with parallel port as well. My machine suffered
from this behaviour when someone made the change as shown on the patch. I just
reverted that one. If the patch solves your problem, I believe that this is
related to BIOS not chipset. I have a Celeron on i815ep and the acpi message is
shown below. I just notice that you have a similar acpi signature like mime.
acpi0: on motherboard
pcibios: BIOS version 2.10
Using $PIR table, 10 entries at 0xc00fded0
Good luck.
> makes
> it appear as if something else is fighting over the same resources that
> the mouse uses.
> This would explain why it can only access the device once a second.
> When BIOS
> initializes, it does not list any other device with an IRQ of 12 (which
> I believe is the mouse interface).
> Does anyone have any experience with devices such as mice flaking out
> with apci?
> Thanks again!
>
> -Mike Bohan
>
>
> On Sun, 2003-08-10 at 04:02, Shizuka Kudo wrote:
>
> > --- Mike Bohan <[EMAIL PROTECTED]> wrote:
> > > Hello,
> > >
> > > I have an Abit KT266 based motherboard and am having some trouble using
> > > the PS/2 mouse driver under XFree86. I have the protocol set to "auto",
> > > and the device set to /dev/psm0. This configuration has worked with
> > > this same Intellimouse in the past. The symptoms are that that when the
> > > mouse is moved, the cursor is only updated about once a second. After
> > > searching google, I found the following URL in which another person
> > > experienced the same problem (from freebsd-bugs). Apparently it only
> > > shows up on certain chipsets (VIA based). I tried several other PS/2
> > > mice, to no avail (same outcome). My system is running a day old
> > > -current build, but this other fellow reported the problem in 5.0 (does
> > > not affect 4.x). I'm wondering if anyone else has experienced this
> > > problem, and if so, are there any work-arounds? I've attached my
> > > 'dmesg' output, in the hopes that the information will be of value.
> > > Thank you in advance!
> > >
> >
> > Does disabling acpi make your mouse working?
> >
> > > URL:
> > > http://lists.freebsd.org/pipermail/freebsd-bugs/2003-April/000426.html
> > >
> > > -Mike Bohan
> > >
> > > Copyright (c) 1992-2003 The FreeBSD Project.
> > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
> > > The Regents of the University of California. All rights
> > > reserved.
> > > FreeBSD 5.1-CURRENT #3: Fri Aug 8 09:10:54 EDT 2003
> > > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CABOOSE
> > > Preloaded elf kernel "/boot/kernel/kernel" at 0xc0424000.
> > > Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0424244.
> > > Timecounter "i8254" frequency 1193182 Hz
> > > CPU: AMD Athlon(tm) processor (1333.91-MHz 686-class CPU)
> > > Origin = "AuthenticAMD" Id = 0x644 Stepping = 4
> > >
> > >
> >
>
Features=0x183fbff
> > > AMD Features=0xc044
> > > real memory = 268369920 (255 MB)
> > > avail memory = 256196608 (244 MB)
> > > Pentium Pro MTRR support enabled
> > > npx0: on motherboard
> > > npx0: INT 16 interface
> > > acpi0: on motherboard
> > > pcibios: BIOS version 2.10
> > > Using $PIR table, 8 entries at 0xc00fdef0
> > > acpi0: power button is handled as a fixed feature programming model.
> > > Timecounter "ACPI-fast" frequency 3579545 Hz
>
Re: Keyboard not working with XFree86
On Fri, Jul 18, 2003 at 03:28:05PM +0200, Daniel Lang wrote: > The XKeysymDB file was missing! (And as I found out later, the XErrorDB > file, as well). The open-motif port used to spam this file with its own version, which would then be removed when the port was deinstalled. I think this is now fixed, which could explain why it is no longer present on your system. This kind of "trespassing" by packages is difficult to recover from automatically (i.e. there's no way to indicate that the usual dependency ordering should be violated and XFree86-libraries should be reinstalled *after* open-motif (which depends on XFree86-libraries)). The solution is to reinstall by hand the package that had its files stomped on. Developing smarter tools to make sure that packages do not stomp existing registered files would also be a benefit. Kris pgp0.pgp Description: PGP signature
Re: Keyboard not working with XFree86
Hi Again, Daniel Lang wrote on Wed, Jul 16, 2003 at 05:16:23PM +0200: [..] > I've recently upgraded my Notebook to 5.1-CURRENT. > One of the main problems I ran into, is, that the > keyboard is not working when using X. [..] > If I start up X, I cannot put in any key. The mouse works > fine, though. I have to remote log into the box and kill > xdm to get rid of the problem. > > The keyboard works perfectly on the console. [..] I could solve the problem. First to complete the symptoms: - Keyboard works on the console - Keyboard does not work using X (regardless of using 'xdm' oder 'startx') - ZapServer (Ctrl-Alt-Backspace) DOES work. This lead my investigation to a problem with the keymap, but the real cause turned out to be utterly obscure. The XKeysymDB file was missing! (And as I found out later, the XErrorDB file, as well). But, it was listed in the +CONTENTS file of the XFree86-libraries port. So apprently it has been installed? But maybe was removed by something else? I certainly did not remove these files. I could solve the problem easily by copying the files back into place, and I cannot rule out, that the files have been lost due to my fault. If any of the XFree port maintainers are aware of fiddling with XKeysymDB or the like, maybe there is indeed a problem. Best regards, Daniel -- IRCnet: Mr-Spock - In dieser Mail ist ein Geist, der Dich in den Hintern beisst - Daniel Lang * [EMAIL PROTECTED] * +49 89 289 18532 * http://www.leo.org/~dl/ smime.p7s Description: S/MIME cryptographic signature
Keyboard not working with XFree86
Hi Folks, I've recently upgraded my Notebook to 5.1-CURRENT. One of the main problems I ran into, is, that the keyboard is not working when using X. For the update from 4.8 to 5.1 I've followed the UPDATING procedure and was successful. After that I deleted all ports/packages and installed most of the ports fresh, including XFree86. Now I have XFree86-Server-4.3.0_8 installed. If I start up X, I cannot put in any key. The mouse works fine, though. I have to remote log into the box and kill xdm to get rid of the problem. The keyboard works perfectly on the console. I searched the mailing list archives and bug reports, but did not find anything. I also tried to create a fresh XF86Config file using xf86cfg (GUI based) and xf86config (text based). Both resulting config files had the same problem as the original config file, i.e. everything works except the keyboard. Now I've updated my 5.1-CURRENT to a snapshot from July 15, and tried to rebuild the XFree86-4-Server port. Now, the portbuild fails in /usr/ports/x11-servers/XFree86-4-Server/work/xc/lib/GL/mesa/src/drv/radeon/ while trying to compile "radeon_vtxtmp_x86.S" error message are many lines of similar output, example: [..] radeon_vtxtmp_x86.S:400:34: pasting "_x86_MultiTexCoord2fARB_2" and ":" does not give a valid preprocessing token. I don't think thats a problem, but due to the recent gcc import, since the portrevision has not changed, this probably wouldn't solve my problem anyway. But for the keyboard problem, any hints are appreciated. Best regards, Daniel -- IRCnet: Mr-Spock - signs of absurd developments in the net community: #42: - "Wurstbrot gehoert m.E. zum Fruehstuecks-botnet von Cartoon" - Daniel Lang * [EMAIL PROTECTED] * +49 89 289 18532 * http://www.leo.org/~dl/ smime.p7s Description: S/MIME cryptographic signature
Patches for XFree86 for FreeBSD/amd64
I have the X server up and running on my machine at work, I'm currently using it in a desktop configuration (although not my primary desktop yet because I still need to have a place to finish off some kernel optimizations). The first patch is against ports/x11/XFree86-4-libraries: http://people.freebsd.org/~peter/amd64-libraries.diff The second is against ports/x11-servers/XFree86-4-server: http://people.freebsd.org/~peter/amd64-server.diff You need to patch both, because the imake config files come from the libraries port and is used in the server build. I've submitted these to the port maintainer, so hopefully something might get committed soon. Most of the rest of the diffs are to either add amd64 support to the FreeBSD configuration, or to fix XFree86 bugs where they assume that all amd64 systems are implicitly Linux based. These patches are very minimal and really need somebody with more knowledge of the XFree86 internals to go over them. But it should be enough to get up and running to play around with it. I'm using a MGA G450 at work FWIW. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
XFree86 kernel panic
Hi guys,
Attached is a gdb trace of a panic on a -current system from a few
days ago. It seems like it was caused by a select(2) in XFree86.
Although I was testing some unrelated changes in libthr kernel code,
I have seen this panic before (about 2 weeks ago) on a stock
kernel.
FreeBSD kokeb.ambesa.net 5.1-CURRENT FreeBSD 5.1-CURRENT #12:
Sat Jul 5 02:00:40 EDT 2003 [EMAIL
PROTECTED]:/a/current/obj/a/current/src/sys/THRTEST i386
Cheers.
--
Mike Makonnen | GPG-KEY: http://www.identd.net/~mtm/mtm.asc
[EMAIL PROTECTED] | D228 1A6F C64E 120A A1C9 A3AA DAE1 E2AF DBCC 68B9
[EMAIL PROTECTED]| FreeBSD - The Power To Serve
Script started on Sat Jul 5 19:43:02 2003
Jul/05 [EMAIL PROTECTED] ~% sudo gdb -k
/a/current/obj/a/current/src/sys/THRTEST/kernel.debug /var/crash/vmcore.9
Password:
GNU gdb 5.2.1 (FreeBSD)
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-undermydesk-freebsd"...
panic: page fault
panic messages:
---
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x818181b1
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc026a3e2
stack pointer = 0x10:0xd2657b08
frame pointer = 0x10:0xd2657b1c
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 3
current process = 735 (XFree86)
trap number = 12
panic: page fault
syncing disks, buffers remaining... 2223 2223 2221 2221 2219 2219 2219 2219 2219
2219 2219 2219 2219 2219 2219 2219 2219 2219 2219 2219 2219 2219 2219 2219
giving up on 154 buffers
Uptime: 16h51m12s
Dumping 255 MB
ata0: resetting devices ..
done
16 32 48 64 80 96 112 128 144 160 176 192 208 224 240
---
Reading symbols from /boot/kernel/snd_pcm.ko...done.
Loaded symbols for /boot/kernel/snd_pcm.ko
Reading symbols from /boot/kernel/snd_via82c686.ko...done.
Loaded symbols for /boot/kernel/snd_via82c686.ko
Reading symbols from /boot/kernel/acpi.ko...done.
Loaded symbols for /boot/kernel/acpi.ko
Reading symbols from /boot/kernel/netgraph.ko...done.
Loaded symbols for /boot/kernel/netgraph.ko
Reading symbols from /boot/kernel/ng_ether.ko...done.
Loaded symbols for /boot/kernel/ng_ether.ko
Reading symbols from /boot/kernel/ng_pppoe.ko...done.
Loaded symbols for /boot/kernel/ng_pppoe.ko
Reading symbols from /boot/kernel/ng_socket.ko...done.
Loaded symbols for /boot/kernel/ng_socket.ko
Reading symbols from /boot/kernel/if_tun.ko...done.
Loaded symbols for /boot/kernel/if_tun.ko
#0 doadump () at /a/current/src/sys/kern/kern_shutdown.c:240
240 dumping++;
(kgdb) bt
#0 doadump () at /a/current/src/sys/kern/kern_shutdown.c:240
#1 0xc023f1fd in boot (howto=256)
at /a/current/src/sys/kern/kern_shutdown.c:372
#2 0xc023f578 in panic () at /a/current/src/sys/kern/kern_shutdown.c:550
#3 0xc03d42a0 in trap_fatal (frame=0xd2657ac8, eva=0)
at /a/current/src/sys/i386/i386/trap.c:836
#4 0xc03d3fb3 in trap_pfault (frame=0xd2657ac8, usermode=0, eva=2172748209)
at /a/current/src/sys/i386/i386/trap.c:750
#5 0xc03d3b98 in trap (frame=
{tf_fs = 24, tf_es = 16, tf_ds = 16, tf_edi = 3, tf_esi = 36, tf_ebp =
-765101284, tf_isp = -765101324, tf_ebx = -1032921444, tf_edx = -1032921444, tf_ecx =
-1028802816, tf_eax = -2122219135, tf_trapno = 12, tf_err = 0, tf_eip = -1071209502,
tf_cs = 8, tf_eflags = 78466, tf_esp = -1032945408, tf_ss = 64})
at /a/current/src/sys/i386/i386/trap.c:435
#6 0xc03c56c8 in calltrap () at {standard input}:96
#7 0xc02654cf in selscan (td=0xc28bbd10, ibits=0xd2657b9c, obits=0xd2657b8c,
nfd=50) at file.h:272
#8 0xc0264f8d in kern_select (td=0xc28bbd10, nd=50, fd_in=0x81fba20,
fd_ou=0x0, fd_ex=0x0, tvp=0xd2657cd8)
at /a/current/src/sys/kern/sys_generic.c:822
#9 0xc0264b56 in select (td=0x0, uap=0xd2657d14)
at /a/current/src/sys/kern/sys_generic.c:726
#10 0xc03d459a in syscall (frame=
{tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = -1, tf_esi = 7482434, tf_ebp =
-1077937896, tf_isp = -765100684, tf_ebx = 0, tf_edx = 16, tf_ecx = 143876576, tf_eax
= 93, tf_trapno = 0, tf_err = 2, tf_eip = 673590515, tf_cs = 31, tf_eflags = 12870,
tf_esp = -1077938516, tf_ss = 47})
at /a/current/src/sys/i386/i386/trap.c:1023
#11 0xc03c571d in Xint0x80_syscall () at {standard input}:138
---Can't read userspace from dump, or kernel process---
(kgdb) qqui uit t
]2;mtm (ttyp2) kokeb:~]1;[EMAIL PROTECTED]:~Jul/05 [EMAIL PROTECTED] ~% ^Dexit
Script done on Sat Jul 5 19:44:17 2003
___
[EMAIL PROTECTED] mailing li
DRI/XFree86/FreeBSD/OpenGL problem
Hello, I have a problem with DRI on FreeBSD. Specifically, in some OpenGL programs, objects are not drawn at all (in some cases only some of them get drawn) (DRI enabled), but when DRI is disabled all work fine. A simple example of such program is: http://www.opengl.org/developers/code/glut_examples/examples/cube.c The hardware is: AMD Athlon XP 1800+, MSI KT4V (KT400/VT8235), 256MB DDR333 PC2700, Matrox G450 32MB AGP4X The system runs -CURRENT (last updated 2 days ago). Some of the XFree86 ports installed (and their versions): XFree86-4.3.0,1, XFree86-Server-4.3.0_8, XFree86-clients-4.3.0_2, XFree86-libraries-4.3.0_5 Other system information: http://members.hellug.gr/lefcha/dmesg http://members.hellug.gr/lefcha/drm http://members.hellug.gr/lefcha/glxinfo http://members.hellug.gr/lefcha/libgldebug http://members.hellug.gr/lefcha/XF86Config-4 http://members.hellug.gr/lefcha/pciconf Thanks ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Radeon VE 7000 VGA card support under xfree86 4.3.0
- Original Message - From: "nobody nobody" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, June 03, 2003 1:01 AM Subject: Radeon VE 7000 VGA card support under xfree86 4.3.0 > Hello, > > Thanks for the advices of the mailing group. I finally figure out the > problem of my previous mail concerning the X under XFree86 4.3.0 with > Freebsd-5.1 beta 2. I use the same VGA card with the crt mon and everything > work ok without extra work for the X-config file. The problem may be the > refresh rate of the LCD is too slow for the VGA card to pick up. I would > like to know if there exists any method that would fix the problem. Thanks > for your effort. > > Clarence > You'll likely need to hard-code the LCD's refresh rate in the config file. Involves manual hacking. Adam ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Radeon VE 7000 VGA card support under xfree86 4.3.0
Hello, Thanks for the advices of the mailing group. I finally figure out the problem of my previous mail concerning the X under XFree86 4.3.0 with Freebsd-5.1 beta 2. I use the same VGA card with the crt mon and everything work ok without extra work for the X-config file. The problem may be the refresh rate of the LCD is too slow for the VGA card to pick up. I would like to know if there exists any method that would fix the problem. Thanks for your effort. Clarence _ No masks required! Use MSN Messenger to chat with friends and family. http://go.msnserver.com/HK/25382.asp ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: XFree86 port does not compile in -current and other issues
Well, I am running a -CURRENT build from April 8. XF86-4.3.0 with a GF4 Ti4200 64MB with a 19" Sony Trinitron CRT (at 1600x1200, 72-75Hz), using the official NVIDIA binary driver kernel module (compiled/installed from /usr/ports/x11/nvidia-driver/). Here's my XF86config (note that it references a "Geforce256" -- ignore that, it only refers to an older NVIDIA card I had, I just didn't change it); it works for me...: # File generated by xf86config. # # Copyright (c) 1999 by The XFree86 Project, Inc. # # Permission is hereby granted, free of charge, to any person obtaining a # copy of this software and associated documentation files (the "Software"), # to deal in the Software without restriction, including without limitation # the rights to use, copy, modify, merge, publish, distribute, sublicense, # and/or sell copies of the Software, and to permit persons to whom the # Software is furnished to do so, subject to the following conditions: # # The above copyright notice and this permission notice shall be included in # all copies or substantial portions of the Software. # # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL # THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, # WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF # OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE # SOFTWARE. # # Except as contained in this notice, the name of the XFree86 Project shall # not be used in advertising or otherwise to promote the sale, use or other # dealings in this Software without prior written authorization from the # XFree86 Project. # # ** # Refer to the XF86Config(4/5) man page for details about the format of # this file. # ** # ** # Module section -- this section is used to specify # which dynamically loadable modules to load. # ** # Section "Module" # This loads the DBE extension module. #Load"dbe" # Double buffer extension # This loads the miscellaneous extensions module, and disables # initialisation of the XFree86-DGA extension within that module. #SubSection "extmod" # Option"omit xfree86-dga" # don't initialise the DGA extension #EndSubSection # This loads the Type1 and FreeType font modules #Load"type1" #Load"freetype" # This loads the GLX module #Load "glx" # From NVIDIA's driver config README Load "bitmap" Load "extmod" Load "dbe" Load "type1" Load "glx" Load "freetype" EndSection # ** # Files section. This allows default font and rgb paths to be set # ** Section "Files" # The location of the RGB database. Note, this is the name of the # file minus the extension (like ".txt" or ".db"). There is normally # no need to change the default. RgbPath "/usr/X11R6/lib/X11/rgb" # Multiple FontPath entries are allowed (which are concatenated together), # as well as specifying multiple comma-separated entries in one FontPath # command (or a combination of both methods) # # If you don't have a floating point coprocessor and emacs, Mosaic or other # programs take long to start up, try moving the Type1 and Speedo directory # to the end of this list (or comment them out). # FontPath "/usr/X11R6/lib/X11/fonts/local/" FontPath "/usr/X11R6/lib/X11/fonts/misc/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/Type1/" #FontPath "/usr/X11R6/lib/X11/fonts/Speedo/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/" # The module search path. The default path is shown here. #ModulePath "/usr/X11R6/lib/modules" EndSection # ** # Server flags section. # ** Section "ServerFlags" # Uncomment this to cause a core dump at the spot where a signal is # received. This may leave the console in an unusable state, but
XFree86 port does not compile in -current and other issues
I tried to build XFree86 from ports since somehow I had no X11 on my server machine - maybe I initially installed a system w/o X11. Now I want to install X and thought I just install /usr/ports/x11/XFree86. But compilation failed somewhere in wrapper.c, security/pam_misc.h not found. I cvsuped all, built world, kernel, resupped ports tree, same failure. Then I installed XFree86-4. That built but I get a core dump when doing a XFree86 -configure. My card is a GeForce2 MX400 64MB. Anyone having an XF86Config for me? Do I need the NVIDIA kernel module? -- Chris Christoph P. U. Kukulies [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Followup to: Trouble building XFree86-4-Clients.
> Well it was Xft. > > I feel stupid, sorry for wasting peoples time. > > Anyways I think I recall what happened, during the portupgrade I was playing > around with X and caused a system crash. This may have happened during the > Xft removal/upgrade stage of portupgrade. I had the same problem when upgrading my XF86 to 4.3.0 over the weekend. XFt is a prerequisite for a bunch of stuff, so it was installed on my machine along with XFree86-4.2.0. However, XFree86-4.2.0 had already installed its own version of libXft and the include files, so the Xft port installed on top of the XFree86-4.2.0 versions of those files. When I tried to upgrade to XFree86-4.3.0, *something* blew away the Xft files, because 'portversion' thought that the Xft package was still installed, even though the actual library and include files were missing. I'm guessing that when the XFree86-4.2.0 port is removed, it also removes the new Xft files. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Q) XFree86-4-Server
Thank you. I find that I haven't cvsup x11/XFree86-4-libraries for a while. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Q) XFree86-4-Server
On Sun, Mar 23, 2003 at 11:57:18AM +0900, Yamada Ken Takeshi wrote: > Is it only with me? > > XFree86-4-Server cannot be compiled on recent -current, > FreeBSD 5.0-CURRENT #34: Sat Mar 22 13:21:34 JST 2003, > with the following error (patch cannot be applied); I think it's you :) That patch does not exist in the ports tree. Kris pgp0.pgp Description: PGP signature
Q) XFree86-4-Server
Is it only with me? XFree86-4-Server cannot be compiled on recent -current, FreeBSD 5.0-CURRENT #34: Sat Mar 22 13:21:34 JST 2003, with the following error (patch cannot be applied); >>> ===> Applying FreeBSD patches for XFree86-Server-4.3.0_2 1 out of 2 hunks failed--saving rejects to lib/X11/imLcPrs.c.rej >> Patch patch-imLcPrs.c failed to apply cleanly. >> Patch(es) patch-FreeBSD.cf patch-Imake.cf patch-Imake.rules patch-Imake.tmpl patch-X11.tmpl patch-Xlc-fix patch-c2 patch-dps patch-dpsinfo patch-dri-Imakefile patch-f applied cleanly. *** Error code 1 Stop in /home/ports/x11-servers/XFree86-4-Server. >>> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Trouble building XFree86-4-Clients.
[moving to -ports, I'm not sure it's a -current issue] "Alastair G. Hogge" wrote: > On Saturday, 22 March 2003 22:17, Daniel O'Connor wrote: > > On Sat, 2003-03-22 at 20:38, Alastair G. Hogge wrote: > > > I've been able to portupgrade my XFree86-4.2.1 system[1] to 4.3.0 expect > > > the 4.3.0 clients port. I've tried completely removing and building it > > > manuly thru "make install" but I get the same. > > > -DMITSHM -DXFT -DXRENDER -c do_text.c > > > do_text.c:403:25: X11/Xft/Xft.h: No such file or directory > > > > Tried making sure Xft and fontconfig are up to date? > > Both were updated with portupgrade. I was bitten by this too, as reported here: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=369839+0+current/freebsd-ports and someone posted a follow-up reporting the same issue. I think this happened with the Xft2->Xft rename -- the upgrade clobbered the original libxft and xft.h from XFree86-4-libs v 4.2, but they were still in the +CONTENTS of XFree86-4-libs, and then the portupgrade of XFree86-4-libs to 4.3 removed both these files. This should be fixed. Already files aren't deleted if their original checksums don't match, unfortunately I think this is overruled with pkg_delete -f ... perhaps one needs an option which forces deleting if there are dependencies, but doesn't delete if there's a checksum mismatch? - Rahul To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Followup to: Trouble building XFree86-4-Clients.
Well it was Xft. I feel stupid, sorry for wasting peoples time. Anyways I think I recall what happened, during the portupgrade I was playing around with X and caused a system crash. This may have happened during the Xft removal/upgrade stage of portupgrade. All is well now, thanks Daniel To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Trouble building XFree86-4-Clients.
On Saturday, 22 March 2003 22:17, Daniel O'Connor wrote: > On Sat, 2003-03-22 at 20:38, Alastair G. Hogge wrote: > > I've been able to portupgrade my XFree86-4.2.1 system[1] to 4.3.0 expect > > the 4.3.0 clients port. I've tried completely removing and building it > > manuly thru "make install" but I get the same. > > -DMITSHM -DXFT -DXRENDER -c do_text.c > > do_text.c:403:25: X11/Xft/Xft.h: No such file or directory > > Tried making sure Xft and fontconfig are up to date? Both were updated with portupgrade. > I had trouble with that when I updated. Wait...blast Xft doesn't appear to be installed anymore. I know I updated to Xft-2.1_3 before the X-4.3.0 upgrade. Well I'll try clients again now, that I re-reinstall Xft. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Trouble building XFree86-4-Clients.
On Sat, 2003-03-22 at 20:38, Alastair G. Hogge wrote: > I've been able to portupgrade my XFree86-4.2.1 system[1] to 4.3.0 expect the > 4.3.0 clients port. I've tried completely removing and building it manuly > thru "make install" but I get the same. > -DMITSHM -DXFT -DXRENDER -c do_text.c > do_text.c:403:25: X11/Xft/Xft.h: No such file or directory Tried making sure Xft and fontconfig are up to date? I had trouble with that when I updated. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Trouble building XFree86-4-Clients.
Hello, I've been able to portupgrade my XFree86-4.2.1 system[1] to 4.3.0 expect the 4.3.0 clients port. I've tried completely removing and building it manuly thru "make install" but I get the same. The log from the build can be found here: http://www4.tpg.com.au/users/jhogge/log But here is the tail++ end: cc -O -pipe -mcpu=pentiumpro -ansi -Dasm=__asm -Wall -Wpointer-arith -Wundef -I/usr/X11R6/include -I/usr/local/include/ freetype2 -I/usr/local/include -I/usr/ports/x11/XFree86-4-clients/work/xc -I/usr/ports/x11/XFree86-4-clients/work/xc/ex ports/include -I/usr/X11R6/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -DMITSHM -DXFT -DXRENDER -c do_text.c do_text.c:403:25: X11/Xft/Xft.h: No such file or directory do_text.c:405: syntax error before '*' token do_text.c:405: warning: type defaults to `int' in declaration of `aafont' do_text.c:405: warning: data definition has no type or storage class do_text.c:406: syntax error before '*' token do_text.c:406: warning: type defaults to `int' in declaration of `aadraw' do_text.c:406: warning: data definition has no type or storage class do_text.c:407: syntax error before "aacolor" do_text.c:407: warning: type defaults to `int' in declaration of `aacolor' do_text.c:407: warning: data definition has no type or storage class do_text.c: In function `InitAAText': do_text.c:416: warning: implicit declaration of function `XftFontOpenName' do_text.c:416: warning: assignment makes pointer from integer without a cast do_text.c:425: warning: implicit declaration of function `XftDrawCreate' do_text.c:427: warning: assignment makes pointer from integer without a cast do_text.c:432: warning: implicit declaration of function `XftFontClose' do_text.c:439: warning: implicit declaration of function `XftColorAllocValue' do_text.c:446: warning: implicit declaration of function `XftDrawDestroy' do_text.c:453: request for member `height' in something not a structure or union do_text.c: In function `DoAAText': do_text.c:483: warning: implicit declaration of function `XftDrawString8' do_text.c: In function `EndAAText': do_text.c:508: warning: implicit declaration of function `XftColorFree' *** Error code 1 Stop in /usr/ports/x11/XFree86-4-clients/work/xc/programs/x11perf. *** Error code 1 Stop in /usr/ports/x11/XFree86-4-clients/work/xc/programs. *** Error code 1 Stop in /usr/ports/x11/XFree86-4-clients. Thanks in advance -Al 1]X system: /var/db/pkg/XFree86-4.3.0,1 /var/db/pkg/XFree86-FontServer-4.3.0 /var/db/pkg/XFree86-Server-4.3.0_2 /var/db/pkg/XFree86-VirtualFramebufferServer-4.3.0 /var/db/pkg/XFree86-documents-4.3.0 /var/db/pkg/XFree86-font100dpi-4.3.0 /var/db/pkg/XFree86-font75dpi-4.3.0 /var/db/pkg/XFree86-fontCyrillic-4.3.0 /var/db/pkg/XFree86-fontDefaultBitmaps-4.3.0 /var/db/pkg/XFree86-fontEncodings-4.3.0 /var/db/pkg/XFree86-fontScalable-4.3.0 /var/db/pkg/XFree86-libraries-4.3.0_1 /var/db/pkg/XFree86-manuals-4.3.0 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [Fwd: HELP GDM XFree86]
On Thu, 2003-03-20 at 03:59, CARTER Anthony wrote: > I can use XDM no problem, so I guess this is really a GDM problem... > > It is a temporary solution, but it will do. However, it isn't pretty and > I would like to use GDM... You cannot start gdm2 out of /etc/ttys. You need to read the gdm2 pkg-message, and use the included rc script to start gdm2. > > Even with XDM, i get this in my xsession-errors file: > > SESSION_MANAGER=local/intra241.intrasoft.lu:/tmp/.ICE-unix/904 > Window manager warning: Broken client! Window 0x600010 (xconsole) > changed client leader window or SM client ID > Gnome-Message: gnome_execute_async_with_env_fds: returning -1 > Gnome-Message: gnome_execute_async_with_env_fds: returning -1 > Extra content at the end of the document > Extra content at the end of the document > Extra content at the end of the document > Extra content at the end of the document > Extra content at the end of the document > Extra content at the end of the document > Extra content at the end of the document > Extra content at the end of the document > Extra content at the end of the document > Extra content at the end of the document > Extra content at the end of the document > Extra content at the end of the document > Extra content at the end of the document > Extra content at the end of the document > > ** (gnome-panel:935): WARNING **: Unable to load panel stock icon 'go' > > Extra content at the end of the document > > > I have already portupgrade -f gnome-panel... These messages are from nautilus and gnome-panel, they are "normal," and non-fatal. You can disregard. Joe > > Anthony Carter > > > On Thu, 2003-03-20 at 09:53, Anthony Carter wrote: > > From: CARTER Anthony <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > > Subject: HELP GDM XFree86 > > Date: 20 Mar 2003 09:23:02 +0100 > > > > Since upgrading to the latest version of XFree86 available on current > > (using portupgrade -r), I cannot login as any users using GDM. I can > > login as root... > > > > After doing a few things, I have the following: > > > > login as user > > enter password > > > > Your session lasted less than 10 seconds. If you didn't log out it could > > indicate a configuration problemblah blah... > > > > It gives an option to view the ~/.xsession error messages, but there is > > nothing there...and if I switch to command line (CTRL+ALT+1) then I see: > > > > gdm[585]: run_session_child: Could not open ~/.xsession-errors... > > > > Any ideas? > > > > Anthony Carter > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-current" in the body of the message > > > > __ > > > > From: CARTER Anthony <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > > Subject: Re: HELP GDM XFree86 > > Date: 20 Mar 2003 09:25:07 +0100 > > > > One more thing...I am running gdm as such from my /etc/ttys file: > > > > ttyv8 "/usr/X11R6/bin/gdm -nodaemon" xterm on secure > > > > Anthony Carter > > > > On Thu, 2003-03-20 at 09:23, CARTER Anthony wrote: > > > Since upgrading to the latest version of XFree86 available on current > > > (using portupgrade -r), I cannot login as any users using GDM. I can > > > login as root... > > > > > > After doing a few things, I have the following: > > > > > > login as user > > > enter password > > > > > > Your session lasted less than 10 seconds. If you didn't log out it could > > > indicate a configuration problemblah blah... > > > > > > It gives an option to view the ~/.xsession error messages, but there is > > > nothing there...and if I switch to command line (CTRL+ALT+1) then I see: > > > > > > gdm[585]: run_session_child: Could not open ~/.xsession-errors... > > > > > > Any ideas? > > > > > > Anthony Carter > > > > > > 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 > > > > __ > > > > From: Sean Chittenden <[EMAIL PROTECTED]> > > T
Re: HELP GDM XFree86
It depends on GNOME version... GNOME-1.4.something installs gdm that is started by init... GNOME-2.2.0 installs gdm that is supposed to start via /usr/X11R6/etc/rc.d/gdm.sh... Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] On Thu, 20 Mar 2003 [EMAIL PROTECTED] wrote: >On 20-Mar-2003 CARTER Anthony wrote: >> One more thing...I am running gdm as such from my /etc/ttys file: >> >> ttyv8 "/usr/X11R6/bin/gdm -nodaemon" xterm on secure > >I think the GDM documentation says, that you should start it via the supplied >rc.d autostart script in order to avoid certain problems. HTH > >Regards, >Julian Stecklina > >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: HELP GDM XFree86
On 20-Mar-2003 CARTER Anthony wrote: > One more thing...I am running gdm as such from my /etc/ttys file: > > ttyv8 "/usr/X11R6/bin/gdm -nodaemon" xterm on secure I think the GDM documentation says, that you should start it via the supplied rc.d autostart script in order to avoid certain problems. HTH Regards, Julian Stecklina To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86-4.3.0,1 +wrapper-1.0_2
You can forcibly delete wrapper package, and the do pkgdb -F and delete dependency on it... Only XFree metaport is depends on it. Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] On Thu, 20 Mar 2003, CARTER Anthony wrote: >I realise what wrapper is for, but if I type pkg_delete wrappe-1.0_2 at >the command line, I get: > >pkg_delete: package 'wrapper-1.0_2' is required by these other packages >and may not be deinstalled: >XFree86-4.3.0,1 > >I never installed wrapper, but when I did a portupgrade to the latest >XFree, I guess it installed wrapper as a dependency... > >I will forcably delete wrapper to see if that fixes the problem >(although I will try your solution first...I don't like deleting >dependencies)... > >Thanks, > >Anthony Carter > >On Thu, 2003-03-20 at 00:17, walt wrote: >> CARTER Anthony wrote: >> > Xfree requires wrapper but seems to break GDM for user logins. Is this >> > normal, and can I force un-install wrapper without breaking anything? >> >> Excuse me, I'm a bonehead. You don't need to uninstall wrapper, just >> change this symbolic link: >> >> /usr/X11R6/bin/X@ -> Xwrapper-4 >> >> to this: >> >> /usr/X11R6/bin/X@ -> XFree86 >> >> This *will* break 'startx' for ordinary users. 'Wrapper' is intended >> to replace xdm and friends to create the .Xauthority in your home >> directory. >> >> If xdm/gdm/kdm don't create the .Xauthority file then something else >> must do it -- that something else is 'wrapper'. >> >> You don't need to use both gdm and wrapper. >> >> >> 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: [Fwd: HELP GDM XFree86]
I can use XDM no problem, so I guess this is really a GDM problem... It is a temporary solution, but it will do. However, it isn't pretty and I would like to use GDM... Even with XDM, i get this in my xsession-errors file: SESSION_MANAGER=local/intra241.intrasoft.lu:/tmp/.ICE-unix/904 Window manager warning: Broken client! Window 0x600010 (xconsole) changed client leader window or SM client ID Gnome-Message: gnome_execute_async_with_env_fds: returning -1 Gnome-Message: gnome_execute_async_with_env_fds: returning -1 Extra content at the end of the document Extra content at the end of the document Extra content at the end of the document Extra content at the end of the document Extra content at the end of the document Extra content at the end of the document Extra content at the end of the document Extra content at the end of the document Extra content at the end of the document Extra content at the end of the document Extra content at the end of the document Extra content at the end of the document Extra content at the end of the document Extra content at the end of the document ** (gnome-panel:935): WARNING **: Unable to load panel stock icon 'go' Extra content at the end of the document I have already portupgrade -f gnome-panel... Anthony Carter On Thu, 2003-03-20 at 09:53, Anthony Carter wrote: > From: CARTER Anthony <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: HELP GDM XFree86 > Date: 20 Mar 2003 09:23:02 +0100 > > Since upgrading to the latest version of XFree86 available on current > (using portupgrade -r), I cannot login as any users using GDM. I can > login as root... > > After doing a few things, I have the following: > > login as user > enter password > > Your session lasted less than 10 seconds. If you didn't log out it could > indicate a configuration problemblah blah... > > It gives an option to view the ~/.xsession error messages, but there is > nothing there...and if I switch to command line (CTRL+ALT+1) then I see: > > gdm[585]: run_session_child: Could not open ~/.xsession-errors... > > Any ideas? > > Anthony Carter > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > > ______ > > From: CARTER Anthony <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Re: HELP GDM XFree86 > Date: 20 Mar 2003 09:25:07 +0100 > > One more thing...I am running gdm as such from my /etc/ttys file: > > ttyv8 "/usr/X11R6/bin/gdm -nodaemon" xterm on secure > > Anthony Carter > > On Thu, 2003-03-20 at 09:23, CARTER Anthony wrote: > > Since upgrading to the latest version of XFree86 available on current > > (using portupgrade -r), I cannot login as any users using GDM. I can > > login as root... > > > > After doing a few things, I have the following: > > > > login as user > > enter password > > > > Your session lasted less than 10 seconds. If you didn't log out it could > > indicate a configuration problemblah blah... > > > > It gives an option to view the ~/.xsession error messages, but there is > > nothing there...and if I switch to command line (CTRL+ALT+1) then I see: > > > > gdm[585]: run_session_child: Could not open ~/.xsession-errors... > > > > Any ideas? > > > > Anthony Carter > > > > 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 > > __ > > From: Sean Chittenden <[EMAIL PROTECTED]> > To: CARTER Anthony <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > Subject: Re: HELP GDM XFree86 > Date: 20 Mar 2003 00:26:06 -0800 > > > Since upgrading to the latest version of XFree86 available on current > > (using portupgrade -r), I cannot login as any users using GDM. I can > > login as root... > > > > After doing a few things, I have the following: > > > > login as user > > enter password > > > > Your session lasted less than 10 seconds. If you didn't log out it could > > indicate a configuration problemblah blah... > > > > It gives an option to view the ~/.xsession error messages, but there is > > nothing there...and if I switch to command line (CTRL+ALT+1) then I see: > > > > gdm[585]: run_session_child: Could not open ~/.xsession-errors... > > > > Any ideas? > > portupgrade -f wrapper > > You need to re-install x11/wrapper. -sc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HELP GDM XFree86
One more thing...I am running gdm as such from my /etc/ttys file: ttyv8 "/usr/X11R6/bin/gdm -nodaemon" xterm on secure Anthony Carter On Thu, 2003-03-20 at 09:23, CARTER Anthony wrote: > Since upgrading to the latest version of XFree86 available on current > (using portupgrade -r), I cannot login as any users using GDM. I can > login as root... > > After doing a few things, I have the following: > > login as user > enter password > > Your session lasted less than 10 seconds. If you didn't log out it could > indicate a configuration problemblah blah... > > It gives an option to view the ~/.xsession error messages, but there is > nothing there...and if I switch to command line (CTRL+ALT+1) then I see: > > gdm[585]: run_session_child: Could not open ~/.xsession-errors... > > Any ideas? > > Anthony Carter > > 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
HELP GDM XFree86
Since upgrading to the latest version of XFree86 available on current (using portupgrade -r), I cannot login as any users using GDM. I can login as root... After doing a few things, I have the following: login as user enter password Your session lasted less than 10 seconds. If you didn't log out it could indicate a configuration problemblah blah... It gives an option to view the ~/.xsession error messages, but there is nothing there...and if I switch to command line (CTRL+ALT+1) then I see: gdm[585]: run_session_child: Could not open ~/.xsession-errors... Any ideas? Anthony Carter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86-4.3.0,1 +wrapper-1.0_2
I realise what wrapper is for, but if I type pkg_delete wrappe-1.0_2 at the command line, I get: pkg_delete: package 'wrapper-1.0_2' is required by these other packages and may not be deinstalled: XFree86-4.3.0,1 I never installed wrapper, but when I did a portupgrade to the latest XFree, I guess it installed wrapper as a dependency... I will forcably delete wrapper to see if that fixes the problem (although I will try your solution first...I don't like deleting dependencies)... Thanks, Anthony Carter On Thu, 2003-03-20 at 00:17, walt wrote: > CARTER Anthony wrote: > > Xfree requires wrapper but seems to break GDM for user logins. Is this > > normal, and can I force un-install wrapper without breaking anything? > > Excuse me, I'm a bonehead. You don't need to uninstall wrapper, just > change this symbolic link: > > /usr/X11R6/bin/X@ -> Xwrapper-4 > > to this: > > /usr/X11R6/bin/X@ -> XFree86 > > This *will* break 'startx' for ordinary users. 'Wrapper' is intended > to replace xdm and friends to create the .Xauthority in your home > directory. > > If xdm/gdm/kdm don't create the .Xauthority file then something else > must do it -- that something else is 'wrapper'. > > You don't need to use both gdm and wrapper. > > > 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: XFree86-4.3.0,1 +wrapper-1.0_2
CARTER Anthony wrote: Xfree requires wrapper but seems to break GDM for user logins. Is this normal, and can I force un-install wrapper without breaking anything? Excuse me, I'm a bonehead. You don't need to uninstall wrapper, just change this symbolic link: /usr/X11R6/bin/X@ -> Xwrapper-4 to this: /usr/X11R6/bin/X@ -> XFree86 This *will* break 'startx' for ordinary users. 'Wrapper' is intended to replace xdm and friends to create the .Xauthority in your home directory. If xdm/gdm/kdm don't create the .Xauthority file then something else must do it -- that something else is 'wrapper'. You don't need to use both gdm and wrapper. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86-4.3.0,1 +wrapper-1.0_2
wrapper is needed to run script startx by ordinary user, not root... Seems like gdm works well for me without wrapper. Shall we need to make XFree86-4.3.0,1 an option to install without wrapper package? Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] On Wed, 19 Mar 2003, CARTER Anthony wrote: >Xfree requires wrapper but seems to break GDM for user logins. Is this >normal, and can I force un-install wrapper without breaking anything? > >Anthony > >XFreeOn Wed, 2003-03-19 at 14:43, walt wrote: >> CARTER Anthony wrote: >> > Hi, >> > >> > I updated XFree86 this morning after a cvsup using portupgrade -r...did >> > all packages for XFree86 (Server, libraries etc. etc.) >> > >> > I now have a problem with GDM... >> > >> > I can log in as root using the GDM, but if I log in as another user, it >> > pops a message up about my session not lasting longer than 10 seconds >> > and dumping me back to login. I get a "client 5 rejected from local >> > host" in my logs, and I get a "run_session_chiled: Could not open >> > ~/.xsession-errors" on the console (even though it exists)... >> >> I have vague recollections that your ~/.xsession should be marked >> executable for xdm/gdm/kdm to work properly. Is it? I can't >> recall if there is a special group added to /etc/group for the >> xsession manager but if there is one your users may need to belong >> to that group. Does gdm run SUID? Can't recall, but it may need to. >> If 'startx' works then I assume you have 'wrapper' installed. I'm >> not sure about the interaction of wrapper with gdm but you could >> try de-installing it. Only takes a second to re-install it. >> >> >> >> 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
XFree86-4.3.0,1 +wrapper-1.0_2
Xfree requires wrapper but seems to break GDM for user logins. Is this normal, and can I force un-install wrapper without breaking anything? Anthony XFreeOn Wed, 2003-03-19 at 14:43, walt wrote: > CARTER Anthony wrote: > > Hi, > > > > I updated XFree86 this morning after a cvsup using portupgrade -r...did > > all packages for XFree86 (Server, libraries etc. etc.) > > > > I now have a problem with GDM... > > > > I can log in as root using the GDM, but if I log in as another user, it > > pops a message up about my session not lasting longer than 10 seconds > > and dumping me back to login. I get a "client 5 rejected from local > > host" in my logs, and I get a "run_session_chiled: Could not open > > ~/.xsession-errors" on the console (even though it exists)... > > I have vague recollections that your ~/.xsession should be marked > executable for xdm/gdm/kdm to work properly. Is it? I can't > recall if there is a special group added to /etc/group for the > xsession manager but if there is one your users may need to belong > to that group. Does gdm run SUID? Can't recall, but it may need to. > If 'startx' works then I assume you have 'wrapper' installed. I'm > not sure about the interaction of wrapper with gdm but you could > try de-installing it. Only takes a second to re-install it. > > > > 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: Updated XFree86
Well, the .xsession is executable... adding my user to the gdm group didn't help... SUID...New to this...can you explain a little about this...? XFree86 is dependent on wrapper...it won't uninstall...I can force it...but... Anthony On Wed, 2003-03-19 at 14:43, walt wrote: > CARTER Anthony wrote: > > Hi, > > > > I updated XFree86 this morning after a cvsup using portupgrade -r...did > > all packages for XFree86 (Server, libraries etc. etc.) > > > > I now have a problem with GDM... > > > > I can log in as root using the GDM, but if I log in as another user, it > > pops a message up about my session not lasting longer than 10 seconds > > and dumping me back to login. I get a "client 5 rejected from local > > host" in my logs, and I get a "run_session_chiled: Could not open > > ~/.xsession-errors" on the console (even though it exists)... > > I have vague recollections that your ~/.xsession should be marked > executable for xdm/gdm/kdm to work properly. Is it? I can't > recall if there is a special group added to /etc/group for the > xsession manager but if there is one your users may need to belong > to that group. Does gdm run SUID? Can't recall, but it may need to. > If 'startx' works then I assume you have 'wrapper' installed. I'm > not sure about the interaction of wrapper with gdm but you could > try de-installing it. Only takes a second to re-install it. > > > > 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: Updated XFree86
CARTER Anthony wrote: Hi, I updated XFree86 this morning after a cvsup using portupgrade -r...did all packages for XFree86 (Server, libraries etc. etc.) I now have a problem with GDM... I can log in as root using the GDM, but if I log in as another user, it pops a message up about my session not lasting longer than 10 seconds and dumping me back to login. I get a "client 5 rejected from local host" in my logs, and I get a "run_session_chiled: Could not open ~/.xsession-errors" on the console (even though it exists)... I have vague recollections that your ~/.xsession should be marked executable for xdm/gdm/kdm to work properly. Is it? I can't recall if there is a special group added to /etc/group for the xsession manager but if there is one your users may need to belong to that group. Does gdm run SUID? Can't recall, but it may need to. If 'startx' works then I assume you have 'wrapper' installed. I'm not sure about the interaction of wrapper with gdm but you could try de-installing it. Only takes a second to re-install it. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Updated XFree86
Hi, I updated XFree86 this morning after a cvsup using portupgrade -r...did all packages for XFree86 (Server, libraries etc. etc.) I now have a problem with GDM... I can log in as root using the GDM, but if I log in as another user, it pops a message up about my session not lasting longer than 10 seconds and dumping me back to login. I get a "client 5 rejected from local host" in my logs, and I get a "run_session_chiled: Could not open ~/.xsession-errors" on the console (even though it exists)... I can stop the GDM running, and log in in the console and then run startx, and that runs fine (that is how I am writing this... ;)) Anyone got any ideas? Anthony To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86 4.3 and Cyrillic Xkb layouts
> Please try setting the locale: > export LC_CTYPE="ru_RU.KOI8-R" > or > setenv LC_CTYPE "ru_RU.KOI8-R" Yow! Worked -- which is a bit strange: with 4.2 nothing like this was necessary... > -- > Alexander Pohoyda > <[EMAIL PROTECTED]> Thanks, -- Andrei __ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86 4.3 and Cyrillic Xkb layouts
Andrei Popov <[EMAIL PROTECTED]> writes: > There's something fishy with Xkb in 4.3: whenever I try cyrillic > layouts (e.g. ru, bg, ua, etc.), I cannot type a thing (and yes, > cyrillic fonts are listed in font path). > Running xev shows that event is there. Anyone seen the same > behavior/knows what may be the cause? Please try setting the locale: export LC_CTYPE="ru_RU.KOI8-R" or setenv LC_CTYPE "ru_RU.KOI8-R" -- Alexander Pohoyda <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
XFree86 4.3 and Cyrillic Xkb layouts
There's something fishy with Xkb in 4.3: whenever I try cyrillic layouts (e.g. ru, bg, ua, etc.), I cannot type a thing (and yes, cyrillic fonts are listed in font path). Once I change it to any latin-based (us, pl, sk, cz, fr, etc.) -- all is ok. Running xev shows that event is there. Anyone seen the same behavior/knows what may be the cause? This is with 11th diff on a 4-5 days old -CURRENT (sorry for cross-posting, most of 4.3 discussion was on -stable list, but this is a -current system). A computer is a Toshiba Portege 7200. -- Andrei __ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with Current & XFree86
> Since it works with 4.7-STABLE it must(?) be a current problem > more than a XFree86 problem. Or? I had the same problem -- something to do with files left over from the original 4.7 installation. Cured by deinstalling XFree86-* ports, renaming /usr/X11R6 to something else (in case something was needed), and then reinstalling everything. Thanks to portupgrade this was pretty easy. I reused the old XF86Config. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Problems with Current & XFree86
Resending due to the fact that I didn' include the /var/log/XFree86.0.log I have a Compaq Evo N800c witch runs with 4.7-STABLE and XFree86 with no problems. The exact same configuration for X and same version of XFree86-libs etc does not run on Current a few days old. The problems started a few weeks ago. just for a test i cvsup-ed to the lates XFree86 code. Same result. Since it works with 4.7-STABLE it must(?) be a current problem more than a XFree86 problem. Or? Any suggestions? Attaching the log file -- Gunnar Flygt, Postmaster SR This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to [EMAIL PROTECTED] and patches submitted to [EMAIL PROTECTED] Before reporting bugs in pre-release versions, please check the latest version in the XFree86 CVS repository (http://www.XFree86.Org/cvs). XFree86 Version 4.2.99.901 (4.3.0 RC 1) Release Date: 8 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: FreeBSD 5.0-CURRENT i386 [ELF] Build Date: 10 February 2003 Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. 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: Mon Feb 10 11:15:19 2003 (==) Using config file: "/usr/X11R6/lib/X11/XF86Config-4" (==) ServerLayout "XFree86 Configured" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Monitor0" (**) | |-->Device "Card0" (**) |-->Input Device "Mouse0" (**) |-->Input Device "Keyboard0" (**) Option "XkbRules" "xfree86" (**) XKB: rules: "xfree86" (**) Option "XkbModel" "pc105" (**) XKB: model: "pc105" (**) Option "XkbLayout" "se" (**) XKB: layout: "se" (**) Option "XkbOptions" "compose:rwin" (**) XKB: options: "compose:rwin" (==) Keyboard: CustomKeycode disabled (**) FontPath set to "/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/" (**) RgbPath set to "/usr/X11R6/lib/X11/rgb" (**) ModulePath set to "/usr/X11R6/lib/modules" (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (II) Module ABI versions: XFree86 ANSI C Emulation: 0.2 XFree86 Video Driver: 0.6 XFree86 XInput driver : 0.4 XFree86 Server Extension : 0.2 XFree86 Font Renderer : 0.4 (II) Loader running on freebsd (II) LoadModule: "bitmap" (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor="The XFree86 Project" compiled for 4.2.99.901, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: "pcidata" (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor="The XFree86 Project" compiled for 4.2.99.901, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,1a30 card 0e11,004a rev 04 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,1a31 card , rev 04 class 06,04,00 hdr 01 (II) PCI: 00:1e:0: chip 8086,2448 card , rev 42 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,248c card , rev 02 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,248a card 0e11,004a rev 02 class 01,01,8a hdr 00 (II) PCI: 00:1f:5: chip 8086,2485 card 0e11,004a rev 02 class 04,01,00 hdr 00 (II) PCI: 01:00:0: chip 1002,4c57 card 0e11,004a rev 00 class 03,00,00 hdr 00 (II) PCI: 02:04:0: chip 11c1,0450 card 1468,0450 rev 02 class 07,80,00 hdr 00 (II) PCI: 02:06:0: chip 104c,ac50 card fffc, rev 02 class 06,07,00 hdr 02 (II) PCI: 02:08:0: chip 8086,1031 card 0e11,0093 rev 42 class 02,00,00 hdr 00 (II) PCI: 02:0e:0: chip 1033,0035 card 0e11,004a rev 41 class 0c,03,10 hdr 80 (II) PCI: 02:0e:1: chip 1033,0035 card 0e11,004a rev 41 class 0c,03,10 hdr 00 (II) PCI: 02:0e:2: chip 1033,00e0 card 0e11,004a rev 02 class 0c,03,20 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,3), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0]
Re: Problems with Current & XFree86
On Mon, Feb 10, 2003 at 11:20:24AM +0100, Gunnar Flygt wrote: > Since it works with 4.7-STABLE it must(?) be a current problem > more than a XFree86 problem. Or? > > Any suggestions? > > -- > Gunnar Flygt, SR Could you paste your /var/log/XFree86*.log with the error parts? Maybe some will be able to detemine the cause of the errors. JY -- "Without the userland, the kernel is useless." --inspired by The Tao of Programming To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Problems with Current & XFree86
Am I the only person having problems with a laptop with Current and XFree86? I have a Compaq Evo N800c witch runs with 4.7-STABLE and XFree86 with no problems. The exact same configuration for X and same version of XFree86-libs etc does not run on Current a few days old. The problems started a few weeks ago. just for a test i cvsup-ed to the lates XFree86 code. Same result. Since it works with 4.7-STABLE it must(?) be a current problem more than a XFree86 problem. Or? Any suggestions? -- Gunnar Flygt, SR To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: first snag with 5.0 - XFree86 4 (fwd)
Recompile and install the with X*4-Server from /usr/ports/x11-servers. Your X server was built on a RC kernel base not the RELEASE the /dev/io mappings are slightly different. The following is the offending line in your snippet Build Operating System: FreeBSD 5.0-RC i386 [ELF] It should say Build Operating System: FreeBSD 5.0-RELEASE i386 [ELF] It will then work and make sure you do a make buildworld if you upgraded to make sure all your libs are also RELEASE not RC :)oseph On Tue, 2003-01-21 at 10:41, fingers wrote: > hi > > it's been suggested that i send this to current@. Please let me know what > info you'd like to carry on debugging this. > > Regards > > --Rob > > -- Forwarded message -- > Date: Tue, 21 Jan 2003 16:05:34 +0200 (SAST) > From: fingers <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: first snag with 5.0 - XFree86 4 > > howdie > > built X 4 from source or using package I'm getting: > > > 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-RC 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: Tue Jan 21 11:15:10 2003 > (--) Using syscons driver with X support (version 2.0) > (--) using VT number 9 > > > Fatal server error: > xf86EnableIO: Failed to open /dev/io for extended I/O > > > when trying something like XFree86 -config. I trolled xfree86.org, found 1 > hit but don't see any response to it. > > fresh install of 5.0-RELEASE using Riva 128. Was previously working on > 5.0-CURRENT (build of about 2 weeks ago). > > /dev/io seems to exist. wrapper is installed. xf86cfg gives same error. > > any ideas? pnpinfo gives me "can't get i/o privelege" which doesn't seem > right. > > have tried 'hint.acpi.0.disabled=1' with same results. I'd think it was > XFree86 specific initially if it wasn't for the pnpinfo error. > > any suggestions appreciated. > > Regards > > --Rob > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" 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: first snag with 5.0 - XFree86 4 (fwd)
thanks all, securelevel was 2 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: first snag with 5.0 - XFree86 4 (fwd)
On Tue, Jan 21, 2003 at 08:41:27PM +0200, fingers wrote: > hi > > it's been suggested that i send this to current@. Please let me know what > info you'd like to carry on debugging this. > > Regards > > --Rob > > -- Forwarded message -- > Date: Tue, 21 Jan 2003 16:05:34 +0200 (SAST) > From: fingers <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: first snag with 5.0 - XFree86 4 > > howdie > > built X 4 from source or using package I'm getting: > > > 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-RC 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: Tue Jan 21 11:15:10 2003 > (--) Using syscons driver with X support (version 2.0) > (--) using VT number 9 > > > Fatal server error: > xf86EnableIO: Failed to open /dev/io for extended I/O What are the permissions on /dev/io? What's your securelevel set to (sysctl kern.securelevel)? -- Ray Kohler <[EMAIL PROTECTED]> Chism's Law of Completion: The amount of time required to complete a government project is precisely equal to the length of time already spent on it. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
first snag with 5.0 - XFree86 4 (fwd)
hi it's been suggested that i send this to current@. Please let me know what info you'd like to carry on debugging this. Regards --Rob -- Forwarded message -- Date: Tue, 21 Jan 2003 16:05:34 +0200 (SAST) From: fingers <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: first snag with 5.0 - XFree86 4 howdie built X 4 from source or using package I'm getting: 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-RC 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: Tue Jan 21 11:15:10 2003 (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 Fatal server error: xf86EnableIO: Failed to open /dev/io for extended I/O when trying something like XFree86 -config. I trolled xfree86.org, found 1 hit but don't see any response to it. fresh install of 5.0-RELEASE using Riva 128. Was previously working on 5.0-CURRENT (build of about 2 weeks ago). /dev/io seems to exist. wrapper is installed. xf86cfg gives same error. any ideas? pnpinfo gives me "can't get i/o privelege" which doesn't seem right. have tried 'hint.acpi.0.disabled=1' with same results. I'd think it was XFree86 specific initially if it wasn't for the pnpinfo error. any suggestions appreciated. Regards --Rob To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
5.0-CURRENT + Xfree86(radeon) blackout/hang
I previously reported the same symptoms which occurred (repeatably) a few minutes after booting and starting X after a fresh -RC2 install from ISO. The problem seemed to have gone away after rebuilding the OS after cvsuping -CURRENT on 30'dec. But... I just got it again (once) after being "up" since 30'dec. Typing away in -chat and the screen goes black (with "no signal" displayed) and the power light doesn't show "power save", but blinks green (meaning unknown). The keyboard is dead. I have to use my reset button. During next boot I get a LOR. (I see that in dmesg.yesterday too and it looks like others have reported the same thing, so I won't go into detail on that.) (The radeon driver has worked fine for me under 4.7-STABLE.) If someone wants to help me debug this, or at least give me some clues, I'm willing to spend some time on it, else I'll probably just see how often it happens or goes away after 5.0-RELEASE and/or go back to 4.7. Or are XFree86-on-FreeBSD problems better dealt with in XFree86 forums? Thanks. -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86 4.2.99.3 on -CURRENT
On Tue, Dec 31, 2002 at 11:51:34AM +0100, Frode Nordahl wrote: > On Tue, 2002-12-31 at 11:30, Szilveszter Adam wrote: > > Hmmm. I have the same version of X as you (roughly, the tag was already > > in place by the time I built although I always use HEAD, I built on 23rd > > December) and FreeBSD is from 25th December. > > I just updated the sources to HEAD, and I see changes was made in > FreeBSD related configfiles and other related .c files around December > 23. I would like to add, that at present, no source patches were required to compile X on -CURRENT. This should ease the upgrade of the port when 4.3.0 comes out. (Although I still have gripes with the way the XFree86-4 metaport works right now: it is very inefficient) Wish you good luck. -- Regards: Szilveszter ADAM Szombathely Hungary To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86 4.2.99.3 on -CURRENT
On Tue, 2002-12-31 at 11:30, Szilveszter Adam wrote:
> Hmmm. I have the same version of X as you (roughly, the tag was already
> in place by the time I built although I always use HEAD, I built on 23rd
> December) and FreeBSD is from 25th December.
I just updated the sources to HEAD, and I see changes was made in
FreeBSD related configfiles and other related .c files around December
23.
I will try to compile again and see what happends (I have tried to
compile from HEAD earlier with the same results)
I have a laptop with following hardware:
- VIA Chipset NB: VIA8603 SB: VIA686B
- Celeron 1.0Ghz
- S3 ProSavage ("Twister") AGP
--
Frode Nordahl <[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: XFree86 4.2.99.3 on -CURRENT
Hello, On Tue, Dec 31, 2002 at 11:09:28AM +0100, Frode Nordahl wrote: > Hello, > > Has anyone had any success with this combo? Yes. Apart from the known problem with my S3 Virge GX2 graphics adapter, which causes random freezes under X when only the reset button helps. But this has been happening since at least X version 4.2.0. Unfortunately, there seems to be no easy fix for the problem, apart from buying a new video card. > It compiles fine, but the X server aborts due to bus error (SIGBUS) > generated by something in xf86GetPciBridgeInfo() > > (xc/programs/Xserver/hw/xfree86/common/xf86pciBus.c) > > Running -CURRENT (World/kernel) as of December 29. XFree86 sources as > of December 30, cvsup'ed with tag xf-4_2_99_3 Hmmm. I have the same version of X as you (roughly, the tag was already in place by the time I built although I always use HEAD, I built on 23rd December) and FreeBSD is from 25th December. My hardware deatils: (they may be relevant) - 440LX chipset (yes, from '98) - PII 233 - S3 Virge GX2 in AGP slot - BIOS is still the original from spring 1998. I have AGP in the kernel, but I cannot say if X uses it or not, there is no word of it in the X log. I used the CVS to build X, but tweaked the config to use the expat, the freetype2 and libxml2 from the system (ports) instead of the packaged ones that are in the X repo. Additional info is available on request, including details of my build environment. -- Regards: Szilveszter ADAM Szombathely Hungary To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
XFree86 4.2.99.3 on -CURRENT
Hello, Has anyone had any success with this combo? It compiles fine, but the X server aborts due to bus error (SIGBUS) generated by something in xf86GetPciBridgeInfo() (xc/programs/Xserver/hw/xfree86/common/xf86pciBus.c) Running -CURRENT (World/kernel) as of December 29. XFree86 sources as of December 30, cvsup'ed with tag xf-4_2_99_3 Since this version is going to be XFree86 4.3.0 sometime in January, it would be nice to make sure it runs on FreeBSD 5.0 :) -- Frode Nordahl <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86 Fails with signal 11 in FreeBSD 4.6 and 4.7
On Tue, Oct 29, 2002 at 10:01:07PM -0800, Paul A. Scott wrote: > XFree86 exits on signal 11 immediately after starting on FreeBSD 4.6 and > 4.7. It is not possible to run the graphical configuration utility at all. > After running curses configuration utility, running startx produces signal > 11. No other debugging information is available. No other messages from the > server. This is off-topic for FreeBSD-current; please redirect to [EMAIL PROTECTED] Kris msg45615/pgp0.pgp Description: PGP signature
XFree86 Fails with signal 11 in FreeBSD 4.6 and 4.7
XFree86 exits on signal 11 immediately after starting on FreeBSD 4.6 and 4.7. It is not possible to run the graphical configuration utility at all. After running curses configuration utility, running startx produces signal 11. No other debugging information is available. No other messages from the server. Note that X runs fine on FreeBSD 4.5 and earlier, using the exact same machine and configuration. When XFree86 moved to a combined server (beginning in FreeBSD 4.6), something broke. Earlier versions (on FreeBSD 4.5 and earlier) using individual X server modules worked fine. Can anyone help me debug and resolve this problem? I've tried everything I can think of to no avail. Thanks, Paul A. Scott mailto:pscott@;skycoast.us http://skycoast.us/pscott/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Xfree86, GNOME, KDE freezing over
On Tue, 15 Oct 2002 11:39:22 -0700 (PDT) Saurabh Gupta <[EMAIL PROTECTED]> wrote: > Any help will be very much appreciated. When it freezes again, wait some minutes (~10). If it unfreezes then, it is a known problem. And if you see some aborts (signal 6) of XFree86, then it is a known problem too. Bye, Alexander. -- Secret hacker rule #11: hackers read manuals. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Xfree86, GNOME, KDE freezing over
Hi, I am running a current from 22nd of september. I compiled gnome2 using the ports method. after some help from people in this list i finally installed it. Now as soon as I startup gnome in X the computer freezes. So I compiled and installed kde3 and the same thing happens. Simple X with just twm seemed to run fine(xterm and a whole bunch of X utilities and all), untill I displayed a remote netscape on this display, which is when this froze over again. Other things that freeze the computer are mozilla running under twm within 10 seconds of startup even just the sawfish window manager freezes as soon as I resize any window. I have no idea how to get more info or catch this bug It just gives no error nothing, even in a generic Kernel with all the debugging features turned on! ANY CLUES, SUGGESTIONS Any one running these applications on current successfully? Anyways here is what I did further. It seems as if the problem is in some package that is used by all these applications. So I gathered a list of dependency packages for all these and started looking for common members. There are tons no surprise there. among all however the common members seem to be Dependency: libiconv-1.8_1 Dependency: lcms-1.08 Dependency: freetype2-2.1.2 of these lcms and libiconv seem to be ruled out in XFree-* dependency list. So the most/(only?) common package in all these software seems to be freetype2-2.1.2 Another thing i noticed is that kde starts up fine : displays a couple of windows and then right around then while displaying one of the windows it freezes half way through. Sort of leaving a feeling that it froze over while rendering some graphics or doing font manipulation calculation.. is freetype the real culprit, I do not know! ofcourse all this could very well be no more than a hunch. Any help will be very much appreciated. thanks and best regards, Saurabh Gupta To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: signal 6 to XFree86 (Re: cvs commit: src/tools/tools...)
On Fri, 4 Oct 2002 19:35:59 -0700 Kris Kennaway <[EMAIL PROTECTED]> wrote: > > >I had one today, they have decreased significantly since removing > > >the Type1 module from my server configuration. > > > > I've also found that disabling xscreensaver/xlockmore helps - or > > just set it to "blank screen only". (Some of those graphical modules > > use beziers.) > > My XFree86 crashes pretty much every time I turn my back on my PC for > a few minutes and let xscreensaver kick in. I don't have a fancy screensaver (blank screen + DPMS), and it even crashes when I do nothing... I've played some mp3s in a xterm and worked in the room *boom* signal 6. At the moment I'm running with http://people.freebsd.org/~deischen/sys.diffs, no signal 6 so far but the system is up only for 50 minutes... as already said in another mail, sometimes I'm able to work for 1-2 hours without a signal 6, sometimes I just have to start up my MUA. Bye, Alexander. -- Speak softly and carry a cellular phone. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: signal 6 to XFree86 (Re: cvs commit: src/tools/tools...)
[Moved to -current] > On Fri, Oct 04, 2002 at 06:30:09PM -0700, Lars Eggert wrote: > > Wesley Morgan wrote: > > >I had one today, they have decreased significantly since removing the > > >Type1 module from my server configuration. > > > > I've also found that disabling xscreensaver/xlockmore helps - or just > > set it to "blank screen only". (Some of those graphical modules use > > beziers.) > > My XFree86 crashes pretty much every time I turn my back on my PC for > a few minutes and let xscreensaver kick in. I don't use screensaver -- my belief is, that the power switch is the best form of screensaving :-) But I do use the Xft library (through KDE) and the xtt.o module (not Type1, though). -mi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: signal 6 to XFree86 (Re: cvs commit: src/tools/tools...)
On Fri, Oct 04, 2002 at 06:30:09PM -0700, Lars Eggert wrote: > Wesley Morgan wrote: > >I had one today, they have decreased significantly since removing the > >Type1 module from my server configuration. > > I've also found that disabling xscreensaver/xlockmore helps - or just > set it to "blank screen only". (Some of those graphical modules use > beziers.) My XFree86 crashes pretty much every time I turn my back on my PC for a few minutes and let xscreensaver kick in. Kris msg43992/pgp0.pgp Description: PGP signature
Re: XFree86 crash, Bezier thing (was Re: Is phk rewriting the kernel over the weekend?)
On Sun, Sep 29, 2002 at 12:17:54PM -0700, Eric Anholt wrote: > On Sun, 2002-09-29 at 10:25, Wesley Morgan wrote: > > Does this bug effect -stable? It only showed up in -current recently. > > Isn't it a bigger chance that something on the FreeBSD side made this bug > > much more visible? > > > > On Sun, 29 Sep 2002, Maxim Sobolev wrote: > > > > > I think it should be fixed in FreeBSD ports before 4.7, because it > > > is really annoying when server crashes without any particular > > > reason. > > > > > > Eric, what do you think about it? > > > > > > -Maxim > > >From what I had heard on the lists it was only a thing that happened > when people upgraded kernels, and that it had stopped after some date of > kernel. I hadn't experienced it, so I ignored it. I don't know about > that link posted, I thought that was a mozilla bug that was supposed to > be fixed. I don't think that it is related to kernel (what kernel has to do with Type1 font renderer in X server???). I'm seeing this problem when trying to open MS Word document in AbiWord, perhaps a bug in AbiWord itself, but IMO no application should be able to crash the server, so that we need to fix it ASAP. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86 crash, Bezier thing
Wesley Morgan wrote: > Yes, i don't see any -stable systems bombing out. But it _always_ occurrs > when typing. No matter what app... I've seen in most often when starting X/gnome. Almost always happens when gnome-panel is just appearing on screen. No typing going on yet, naturally. If gnome-panel is using a TypeI font that might account for it. Oddly, though, usually if I just type startx a second time it all starts OK. Later it may crash with mozilla also, of course. I took TypeI out of my fonts-path and so far no more crashes, but it's been less than 24 hours, so still a bit early to crow. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86 crash, Bezier thing (was Re: Is phk rewriting the kernelover the weekend?)
Yes, i don't see any -stable systems bombing out. But it _always_ occurrs when typing. No matter what app... Sometimes in the linux opera, sometimes in the konq address bar. I dont think it ever happened when typing in an Xterm though. On 29 Sep 2002, Frode Nordahl wrote: > On Sun, 2002-09-29 at 21:17, Eric Anholt wrote: > > >From what I had heard on the lists it was only a thing that happened > > when people upgraded kernels, and that it had stopped after some date of > > kernel. I hadn't experienced it, so I ignored it. I don't know about > > that link posted, I thought that was a mozilla bug that was supposed to > > be fixed. > > It seems like the bug has been present in XFree86 all the time. But > some thing has changed in CURRENT that tickles this bug. > > I started to experience this after I removed all ports and recompiled > XFree86 with the new GCC 3.2.1. > > X also dies with signal 11 some times, so theres more to it than the > Bezier bug. > > But if it is a CURRENT kernel or compiler issue, I don't understand why > / how this should affect -STABLE / -RELEASE. > > I'll take a backup of my current X installation and do some tests and > comparisons against the Aug 24 port build of XFree86. > > I'll have to find a sure way to reproduce the abort() and / or SIGSEGV > failure first though. > > > -- > > Eric Anholt <[EMAIL PROTECTED]> > > http://people.freebsd.org/~anholt/dri/ > > > > -- > Mvh, > Frode Nordahl > -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86 crash, Bezier thing (was Re: Is phk rewriting thekernel over the weekend?)
On Sun, 2002-09-29 at 21:17, Eric Anholt wrote: > >From what I had heard on the lists it was only a thing that happened > when people upgraded kernels, and that it had stopped after some date of > kernel. I hadn't experienced it, so I ignored it. I don't know about > that link posted, I thought that was a mozilla bug that was supposed to > be fixed. It seems like the bug has been present in XFree86 all the time. But some thing has changed in CURRENT that tickles this bug. I started to experience this after I removed all ports and recompiled XFree86 with the new GCC 3.2.1. X also dies with signal 11 some times, so theres more to it than the Bezier bug. But if it is a CURRENT kernel or compiler issue, I don't understand why / how this should affect -STABLE / -RELEASE. I'll take a backup of my current X installation and do some tests and comparisons against the Aug 24 port build of XFree86. I'll have to find a sure way to reproduce the abort() and / or SIGSEGV failure first though. > -- > Eric Anholt <[EMAIL PROTECTED]> > http://people.freebsd.org/~anholt/dri/ > -- Mvh, Frode Nordahl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86 crash, Bezier thing (was Re: Is phk rewriting thekernel over the weekend?)
On Sun, 2002-09-29 at 10:25, Wesley Morgan wrote: > Does this bug effect -stable? It only showed up in -current recently. > Isn't it a bigger chance that something on the FreeBSD side made this bug > much more visible? > > On Sun, 29 Sep 2002, Maxim Sobolev wrote: > > > I think it should be fixed in FreeBSD ports before 4.7, because it > > is really annoying when server crashes without any particular > > reason. > > > > Eric, what do you think about it? > > > > -Maxim >From what I had heard on the lists it was only a thing that happened when people upgraded kernels, and that it had stopped after some date of kernel. I hadn't experienced it, so I ignored it. I don't know about that link posted, I thought that was a mozilla bug that was supposed to be fixed. -- 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: XFree86 crash, Bezier thing (was Re: Is phk rewriting the kernelover the weekend?)
Does this bug effect -stable? It only showed up in -current recently. Isn't it a bigger chance that something on the FreeBSD side made this bug much more visible? On Sun, 29 Sep 2002, Maxim Sobolev wrote: > I think it should be fixed in FreeBSD ports before 4.7, because it > is really annoying when server crashes without any particular > reason. > > Eric, what do you think about it? > > -Maxim > > On Sun, Sep 29, 2002 at 03:17:41PM +0200, Frode Nordahl wrote: > > Hey, > > > > On Sun, 2002-09-29 at 14:51, walt wrote: > > [snip] > > > > > > I wonder if it could find the very annoying crashes in the X server. > > > > > > -- > > > I'm sick of hearing about how big my Beziers are! > > > > I found this on the Xpert mailinglist: > > http://www.xfree86.org/pipermail/xpert/2002-June/018300.html > > > > Seems like this won't get fixed until XFree86 4.3.0, but the bug seems > > to be in the "Type1" font handler only. (a call to abort()) > > > > I have removed it from my XFree86 config now, and I'm hoping for no more > > Bezier crashes :) > > > > > > Mvh, > > Frode Nordahl > > > > > > 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 > -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86 crash, Bezier thing (was Re: Is phk rewriting the kernel over the weekend?)
I think it should be fixed in FreeBSD ports before 4.7, because it is really annoying when server crashes without any particular reason. Eric, what do you think about it? -Maxim On Sun, Sep 29, 2002 at 03:17:41PM +0200, Frode Nordahl wrote: > Hey, > > On Sun, 2002-09-29 at 14:51, walt wrote: > [snip] > > > > I wonder if it could find the very annoying crashes in the X server. > > > > -- > > I'm sick of hearing about how big my Beziers are! > > I found this on the Xpert mailinglist: > http://www.xfree86.org/pipermail/xpert/2002-June/018300.html > > Seems like this won't get fixed until XFree86 4.3.0, but the bug seems > to be in the "Type1" font handler only. (a call to abort()) > > I have removed it from my XFree86 config now, and I'm hoping for no more > Bezier crashes :) > > > Mvh, > Frode Nordahl > > > 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
XFree86 crash, Bezier thing (was Re: Is phk rewriting the kernelover the weekend?)
Hey, On Sun, 2002-09-29 at 14:51, walt wrote: [snip] > > I wonder if it could find the very annoying crashes in the X server. > > -- > I'm sick of hearing about how big my Beziers are! I found this on the Xpert mailinglist: http://www.xfree86.org/pipermail/xpert/2002-June/018300.html Seems like this won't get fixed until XFree86 4.3.0, but the bug seems to be in the "Type1" font handler only. (a call to abort()) I have removed it from my XFree86 config now, and I'm hoping for no more Bezier crashes :) Mvh, Frode Nordahl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: trouble building XFree86-4-Server under yesterday's current
On Tue, 24 Sep 2002 17:22:36 +0300
Vallo Kallaste <[EMAIL PROTECTED]> wrote:
> On Tue, Sep 24, 2002 at 09:47:44AM -0400, Wesley Morgan
> <[EMAIL PROTECTED]> wrote:
>
> > I have built XFree86 at least 3 times in the past week, all with
> > varying levels of optimization, from -O to -O3 and ALWAYS with
> > -march=pentium3. All of the builds succeeded, although I had
> > stability problems with -O2 and above. Are you _certain_ this is a
> > compiler bug?
>
> To put myself to the safe side, no. I'll do yet another run of
> compilation on all of the CPUTYPE=p[234] levels and report how it
> did tomorrow.
No need. The bug is there and it is triggered by -march={athlon|p[234]}.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: trouble building XFree86-4-Server under yesterday's current
On Tue, Sep 24, 2002 at 09:47:44AM -0400, Wesley Morgan <[EMAIL PROTECTED]> wrote: > I have built XFree86 at least 3 times in the past week, all with varying > levels of optimization, from -O to -O3 and ALWAYS with -march=pentium3. > All of the builds succeeded, although I had stability problems with -O2 > and above. Are you _certain_ this is a compiler bug? To put myself to the safe side, no. I'll do yet another run of compilation on all of the CPUTYPE=p[234] levels and report how it did tomorrow. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
