[SOLVED] Re: www/179397: I used mouse focus in open-motif and shift-click3 to iconify xterms, doing so causes cursor to disappear and mouse is unusable!
According to freebsd-gnats-sub...@freebsd.org on Fri, 06/07/13 at 06:40:
Thank you very much for your problem report.
It has the internal identification `www/179397'.
The individual assigned to look at your
report is: freebsd-www.
You can access the state of your problem report at any time
via this link:
http://www.freebsd.org/cgi/query-pr.cgi?pr=179397
Category: www
Responsible:freebsd-www
Synopsis: I used mouse focus in open-motif and shift-click3 to iconify
xterms, doing so causes cursor to disappear and mouse is unusable!
Arrival-Date: Fri Jun 07 10:40:00 UTC 2013
I may be one of the few people left who use x11-toolkits/open-motif on
the FreeBSD desktop, but be that as it may, there is a bug that needs
to be fixed in the /usr/ports/x11-servers/xorg-server/files/ directory.
In May 2013 this directory included this file:
-rw-r--r-- 1 root wheel 3487 May 2 13:08 extra-dix_events.c
I upgraded my ports on a nearly identical system on May 23 and
again on June 5th of 2013:
unix% ll /usr/ports/x11-servers/xorg-server/files/
total 40
drwxr-xr-x 2 root wheel 1024 Jun 5 11:20 .
drwxr-xr-x 4 root wheel 512 Jun 5 12:06 ..
-rw-r--r-- 1 root wheel 402 Jun 5 11:20
extra-Xserver-hw-xfree86-os-support-bsd-sparc64_video.c
-rw-r--r-- 1 root wheel 350 Jun 5 11:20 extra-Xserver-os-xprintf.c
-rw-r--r-- 1 root wheel 5536 May 23 12:19 extra-arch-ia64
-rw-r--r-- 1 root wheel 438 May 23 12:19 extra-arch-powerpc
-rw-r--r-- 1 root wheel 2467 Jun 5 11:20 extra-clang
-rw-r--r-- 1 root wheel 799 May 23 12:19 extra-include_eventstr.h
-rw-r--r-- 1 root wheel 493 Jun 5 11:20 extra-new-arch-i386
-rw-r--r-- 1 root wheel 511 Jun 5 11:20 extra-old-arch-i386
-rw-r--r-- 1 root wheel 645 Jun 5 11:20 extra-os-utils.c
-rw-r--r-- 1 root wheel 320 Jun 5 11:20 extra-servermd.h
-rw-r--r-- 1 root wheel 384 May 23 12:19
patch-Xserver-hw-xfree86-common-xf86Config.c
-rw-r--r-- 1 root wheel 469 May 23 12:19
patch-Xserver-hw-xfree86-os-support-bsd-i386_video.c
-rw-r--r-- 1 root wheel 471 May 23 12:19 patch-xorgconf.cpp
-rw-r--r-- 1 root wheel 155 May 23 12:19 pkg-deinstall.in
-rw-r--r-- 1 root wheel 551 May 23 12:19 pkg-install.in
The lack of the extra-dix_events.c patch file caused using my three
button USB mouse with x11-toolkits/open-motif to fail. Note: all ports
were rebuilt on Jun 5th after running svn update /usr/ports from within
/usr/ports.
Once the mouse failed, all I could do was CTRL-ALT-BS and revert to
virtual terminals - not a very good desktop substitute.
It turns out that the last patch segment of extra-dix_events.c was omitted
(along with the entire patch file itself):
@@ -3632,7 +3583,8 @@ CheckPassiveGrabsOnWindow(
{
FixUpEventFromWindow(device, xE, grab-window, None, TRUE);
- TryClientEvents(rClient(grab), device, xE, count, mask,
+ TryClientEvents(rClient(grab), device, xE, count,
+GetEventFilter(device, xE),
GetEventFilter(device, xE), grab);
}
The lack of this last patch segment was the cause of my problems with mwm
(part of the x11-toolkits/open-motif port) but it did not impact other
window managers such as FVWM which may be why this patch was overlooked.
Regards,
web...
--
William Bulley Email: w...@umich.edu
72 characters width template -|
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
9.1-STABLE with xterm-292 oddity
Recently (last week) I upgraded two systems to 9.1-STABLE. One system is i386 and the other is amd64. The upgrades were done about one day apart. While I have not checked every single commit, for the purposes of this problem, I am assuming these two systems have the same ports, src, and docs changes applied. This is how I began these upgrades: % cd /usr % rm -rf src ports doc % svn co svn://svn.freebsd.org/base/stable/9 src % svn co svn://svn.freebsd.org/doc/head doc % svn co svn://svn.freebsd.org/ports/head ports Note: these systems are desktop systems, not headless servers. The hardware of both systems is nearly identical, in particular, the graphics card (ATI) is identical on each system. After each upgrade, I wiped all my ports and rebuilt all the ports on the list of ports I use on these systems. While these two lists are slightly different, the basics are the same in both cases. I run Xorg on both systems along with open-motif and xterms: xorg-7.5.2 open-motif-2.3.4 xterm-292 The /var/db/ports/xterm/options files on both systems are identical. # This file is auto-generated by 'make config'. # Options for xterm-292 _OPTIONS_READ=xterm-292 _FILE_COMPLETE_OPTIONS_LIST=256COLOR DABBREV DECTERM GNOME LUIT PCRE WCHAR OPTIONS_FILE_UNSET+=256COLOR OPTIONS_FILE_UNSET+=DABBREV OPTIONS_FILE_UNSET+=DECTERM OPTIONS_FILE_UNSET+=GNOME OPTIONS_FILE_SET+=LUIT OPTIONS_FILE_UNSET+=PCRE OPTIONS_FILE_SET+=WCHAR Also the /usr/ports/x11/xterm/work/xterm-292/xtermcfg.h files are the same on both systems. The oddity is this: on one system, when I iconify/minimize/close an open xterm window, the resulting small icon window holds a pixmap (48x48) that is monochrome. It resembles an outline drawing of an old style dumb terminal. On the other system, when I perform the same operation (close/iconify an xterm window), the resulting small icon window contains a color pixmap (48x48) of our Beastie! While I have an .Xdefaults file in my home directory on both systems, and there are XTerm resources configured therein, I do not configure any resources that control xterm icons. In fact, those .Xdefaults files are identical in the XTerm resource lines. I have rebuilt the x11/xterm port on the system with the color Beastie pixmap for closed/iconic xterm windows using the following steps: # cd /usr/ports/x11/xterm # make deinstall # /bin/rm -rf work # make install The results are the same as before, unfortunately. Interesting enough, one can see the color Beastie pixmap _inside_ the unstripped xterm executable on each system using this command: % strings /usr/local/bin/xterm | less The Beastie embedded pixmap appears after scrolling to about the 83% point (and runs up to about the 93% point) of the strings output. I am at a loss as to how one system is displaying the unwanted color pixmap while the other is showing the desired monochrome pixmap. Any ideas, or suggested avenues for further detective work, on this issue would be greatly appreciated. Thanks in advance. Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: failure building www/webkit-gtk2 on 8.2-STABLE
According to Koop Mast k...@rainbow-runner.nl on Fri, 12/02/11 at 07:03: Can you check if you got the video option selected? make config if you haven't, please select it and do a make clean before trying to build it. Excellent advice!!! Thank you very much! Looks like -questions comes through again. You folks are wonderful. :-) Now for some questions and issues to resolve this once and for all. How could I have possibly known that this option (WITH_VIDEO=yes) was required? I looked back at when I last built www/webkit-gtk2 and that was here: -rw-r--r-- 0 root wheel 215 Jan 19 2010 webkit/options In that file I found: WITHOUT_VIDEO=yes So about a year ago www/webkit-gtk2 built just fine WITHOUT the video option. What changed? I checked and there is no match (using grep) in the /usr/ports/UPDATING file (whose first entry dates from 20080108): % grep -i webkit /usr/ports/UPDATING % So I wouldn't have found anything there. I see in the Makefile that WITH_VIDEO has a default of on. That must not have been the case a year ago. Should I blame the www/xxxterm for having a dependency on www/webkit-gtk2? During the attempted build of www/xxxterm I was not asked for any options for www/webkit-gtk2 since I had a previous file /var/db/ports/webkit/options from back about a year ago. This is now a moot point, since the port did build correctly with this change (thanks again!), but for completeness sake and for my own sanity, how would I have been able to avoid this problem? Thanks. :-) Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: failure building www/webkit-gtk2 on 8.2-STABLE
According to Robert Bonomi bon...@mail.r-bonomi.com on Wed, 11/30/11 at 16:12:
From owner-freebsd-questi...@freebsd.org Wed Nov 30 09:14:56 2011
Date: Wed, 30 Nov 2011 10:12:23 -0500
From: William Bulley w...@umich.edu
To: freebsd-questions@freebsd.org
Cc: gn...@freebsd.org
Subject: failure building www/webkit-gtk2 on 8.2-STABLE
This is a freshly csup'd ports tree as of 11/24/2011 and uname -a gives:
FreeBSD dell 8.2-STABLE FreeBSD 8.2-STABLE #0: Sun May 29 08:36:55 EDT
2011
root@dell:/usr/obj/usr/src/sys/DELL amd64
When I try to make install in www/xxxterm this is what I get:
=== xxxterm-1.518 depends on file: /usr/local/bin/perl5.14.1 - found
=== xxxterm-1.518 depends on file: /usr/local/bin/intltool-extract -
found
=== xxxterm-1.518 depends on executable: pkg-config - found
=== xxxterm-1.518 depends on shared library: gnutls.47 - found
=== xxxterm-1.518 depends on shared library: soup-2.4 - found
=== xxxterm-1.518 depends on shared library: webkitgtk-1.0 - not found
*THIS* 'not found' indicates the linking (at least) of the exuecutable will
probably fail.
Thanks for the reply. This knowledge is not all that useful. The process of
making this port will, of course, make all dependencies of this port. By not
finding that item forces the installation of www/webkit-gtk2 below. This is
not an error.
===Verifying install for webkitgtk-1.0 in /usr/ports/www/webkit-gtk2
=== Building for webkit-gtk2-1.4.3
gmake all-am
gmake[1]: Entering directory `/usr/ports/www/webkit-gtk2/work/webkit-1.4.3'
GENWebKit-1.0.gir
/usr/local/bin/gmkdir -p ./.deps/DerivedSources
/usr/include/machine/endian.h:123: syntax error, unexpected '{' in ' return
(__extension__ ({ register __uint64_t __X = (_x); __asm (bswap %0 : +r
(__X)); __X; }));' at '{'
/usr/include/machine/endian.h:123: syntax error, unexpected ';' in ' return
(__extension__ ({ register __uint64_t __X = (_x); __asm (bswap %0 : +r
(__X)); __X; }));' at ';'
/usr/include/machine/endian.h:130: syntax error, unexpected '{' in ' return
(__extension__ ({ register __uint32_t __X = (_x); __asm (bswap %0 : +r
(__X)); __X; }));' at '{'
/usr/include/machine/endian.h:130: syntax error, unexpected ';' in ' return
(__extension__ ({ register __uint32_t __X = (_x); __asm (bswap %0 : +r
(__X)); __X; }));' at ';'
_these_ errors may be a separate issue They indicate an incompatibility
between the code and the -compiler- being used. This could be an artifact
of other errors, like the one implied below, or they could be from unrelated
causes. Eliminate the other errors, and see if this remains.
The port maintainers are responsible for assuring the compiler matches the
code, and that the code compiles with that compiler. This is clearly an
error, but one that I have no idea how to fix.
Source/WebKit/gtk/webkit/webkitversion.h:33: Warning: WebKit:
symbol='WEBKITGTK_API_VERSION': Unknown namespace for symbol
'WEBKITGTK_API_VERSION'
This is probably directly related to the 'not found' error above.
Not so sure about that. But again, how is this (and other errors) to be
fixed? Why don't the port maintainers respond to this thread?
/usr/ports/www/webkit-gtk2/work/webkit-1.4.3/tmp-introspectiHsaMf/WebKit-1.0.o(.data+0x2e8):
undefined reference to `webkit_dom_html_media_element_get_type'
/usr/ports/www/webkit-gtk2/work/webkit-1.4.3/tmp-introspectiHsaMf/WebKit-1.0.o(.data+0x3c0):
undefined reference to `webkit_dom_media_error_get_type'
/usr/ports/www/webkit-gtk2/work/webkit-1.4.3/tmp-introspectiHsaMf/WebKit-1.0.o(.data+0x450):
undefined reference to `webkit_dom_time_ranges_get_type'
as are all these.
Again, not so sure about that.
Can anyone tell me what is going on here and how I can correct it?
Can it be that this port does not build correctly on AMD hardware?
Again, thanks for the reply, but it doesn't get me all that much closer
to getting this port built. Anyone else have any ideas or pointers?
Regards,
web...
--
William Bulley Email: w...@umich.edu
72 characters width template -|
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
failure building www/webkit-gtk2 on 8.2-STABLE
-introspectiHsaMf/WebKit-1.0.o']' returned non-zero exit status 1 gmake[1]: *** [WebKit-1.0.gir] Error 1 gmake[1]: Leaving directory `/usr/ports/www/webkit-gtk2/work/webkit-1.4.3' gmake: *** [all] Error 2 *** Error code 1 Stop in /usr/ports/www/webkit-gtk2. *** Error code 1 Stop in /usr/ports/www/webkit-gtk2. *** Error code 1 Stop in /usr/ports/www/xxxterm. Can anyone tell me what is going on here and how I can correct it? Can it be that this port does not build correctly on AMD hardware? Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: where to ask about problems with bsdinstall in 9.0RC2?
According to Ian Smith smi...@nimnet.asn.au on Tue, 11/22/11 at 23:48: Sorry William, this arrived not long after I crashed, 18-hour odd time difference .. I've since seen Frank Shute advise how to csup from 8.2-S to RELENG_9_0 and in your case that's likely the easiest way to go. Sorry about the time difference - not much I can do about that... :-) As you see, you got exactly the same error I got with BETA1, and for the same reason - bsdinstall isn't running newfs on your existing partitions before trying to extract the distribution. I thought that was going to be fixed before release, but clearly not yet. It really needs the newfs toggle option of sysinstall/sade before it'll be useful as sysinstall. The docs are very much a work in progress. Even sysinstall requires you to at least enter the mountpoints for your existing partitions (within a slice); they're needed for install and of course to build /etc/fstab. In my case, wanting to preserve /home, seems I'll have to NOT supply a mountpoint for that partition in order for it to be left alone, and then add it into fstab afterwards, probably having to merge any newly created user there from /usr/home, revert the symlink etc. Messy. Did you try running sysinstall (or sade), just to do the slicing + partitioning / newfs'ing from Live CD mode, only on DVD1 I guess? In your case I think a source upgrade and building is probably the way to go. In my case, my 8.2 is on another slice (s4), but I want 9.0 on s2, over an existing 7.4-RELEASE, because that slice has enough space for a decent ongoing 9.x system, and because I'd hoped to contribute to debugging bsdinstall - but then I moved and had no net access for nearly a month. Still, I'm persisting with that plan and I'll keep hassling until this regression in functionality is fixed, for 9.1 now I guess. The third time is the charm! I was successful (and am now running 9.0-PRERELEASE!) with the upgrade of this older Dell laptop. The first (failed attempt) was from 8.2-S to 9.x anything (turned out to be RC1 at the time). This was a source upgrade (csup/buildworld/installworld) but failed during the compilation of the kernel. At this point I decided to just grab the DVD1 and install over my 8.2-S since I was not invested in anything on the disk (although I had csup'd the ports tree and was running Xorg successfully at that point). The DVD1 ISO install of 9.0-RC1 was unsuccessful due to the oddness of the bsdinstall program as you describe above. At about this time RC1 was transitioning to RC2, so I decided to grab the bootonly RC2 ISO and yesterday ran into the same bsdinstall issues. So I was forced to try the source upgrade again, hoping that by this time the kernel compilation problem had been fixed. Well, evidently it was, because the csup/buildworld/installworld method worked like a charm and I am now happily running 9.0-PRERELEASE. Thanks for all the replies and suggestions. I am going to try to avoid using bsdinstall like the plague and I advise others to do likewise, at least until it becomes more mature. It seems to me that the inclusion of the bsdinstall program as the default installer in 9.0 is illadvised at best. Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freebsd-questions Digest, Vol 390, Issue 3
According to Galati, Michael mcg+f...@sulfegate.org on Wed, 11/23/11 at
00:40:
If you still have trouble compiling, you could always do a fresh
install off one of the 9.0-RC2 images on a spare machine (or on
virtual machine; VirtualBox works well for this), and build the
sources there. Once the make build{world,kernel} steps complete, copy
(or export over NFS) /usr/{src,obj} to the machine to be upgraded, and
do the usual make install{kernel,world} (and mergemaster) steps.
I just did this just yesterday to bring a test box up from stable/8 to
stable/9; worked like a charm. YMMV.
Apparently freebsd-update(8) works for binary updates as well, but
I've never used it (check the release announcement on freebsd-current
or freebsd-stable from the 17th).
Good luck! ^_^'
Thanks. I am now happily running 9.0-PRERELEASE (!) and finally past
all those weird bsdinstall issues. What a mess! Thanks for all the
replies and help. I didn't use anything other than what I view as the
standard (t/m) way to upgrade: csup-of-stable/buildworld/installworld
which method has always worked in the past for me, but had trouble in
the attempt to upgrade to a 9.x variant before it was ready for prime
time. I would not normally have done this, but there were extenuating
circumstances that required the attempt. Thanks again. :-)
Regards,
web...
--
William Bulley Email: w...@umich.edu
72 characters width template -|
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: where to ask about problems with bsdinstall in 9.0RC2?
According to Ian Smith smi...@nimnet.asn.au on Sat, 11/19/11 at 13:29: Unfortunately that concentrates on creating a GPT layout, encouraging a Linux-like single (plus a boot) partition - forget using dump/restore - and says nothing much about installing over an existing setup with MBR partitioning and multiple slices, a not uncommon setup on many existing laptops .. eg here I want to install over a previous 7.2-RELEASE 60GB slice partitioned as I want it - 1GB /, 4GB /var, 16GB /usr and ~37GB /home. Further, I want to preserve /home as is, despite having backups. sysinstall's partitioning is more sophisticated; you get to specifically toggle on or off newfs'ing each partition, as well as specifying newfs options if you want. So it's clear whether you'll be newfs'ing / and which other partitions, and which you'll be leaving alone, eg /home. On BETA1 I recorded Extract Error while extracting base.txz: can't set user=0/group=0 for /var/empty Can't update time for /var/empty .. which someone/s else also reported, which turned out to be misleading .. the basic problem is that the filesystem isn't empty, ie as after newfs. I hate to be a pest about this, but bsdinstall just isn't working for me. I grabbed the 9.0RC2 bootonly ISO for i386 and tried again to load this onto this Dell laptop. This time the *.txz files had to be gotten over the network which took longer that with the DVD1 ISO. :-( The files were fetched, and checked/verified, then the actual installation (extraction) began. Unfortunately, I got the same error pop-up message. This time I have the exact text of that error message: Error while extracting base.txz: Can't set user=0/group=0 for var/emptyCan't update time for var/empty Note the missing space or CR before the second Can't What confused me at first was the missing slash (/) character before the two var pathnames. But I now understand that is because I am updating (not installing) from a previously working (was 8.2-STABLE in this case) system where the four partitions (root, swap, /var, and /usr) are present and full of FreeBSD files, etc. If this is a feature of bsdinstall, then it should be mentioned in the documentation somewhere. I used the Manual configuration method where I was asked to name the mount points for root, /var and /usr. My question is this: if bsdinstall can't handle installing over top of an already existing system on disk, then why ask the user for mount points on those already existing partitions? This seems weird to me. So now I am back to square one. I want to load 9.0RC2 onto this laptop for reasons that aren't relevant to this thread, yet I am unable to do so because as of 9.0 sysinstall has been replaced by bsdinstall. For the record, how do I upgrade to 9.0RC2 (or any 9.0 variant) from a system already running 8.2-STABLE? Had this attempt been using the sysinstall method, I would have long since been up and running FreeBSD 9.x on this laptop. Please advise. Thanks in advance. Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: where to ask about problems with bsdinstall in 9.0RC2?
According to Frank Shute fr...@shute.org.uk on Tue, 11/22/11 at 13:36: Can't help you with your bsdinstall woes but to upgrade from 8.2-STABLE to 9.0-RELEASE(currently RC2) branch you want to do a csup(1)/buildworld cycle. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html You should use the tag: *default release=cvs tag=RELENG_9_0 in your supfile. More details at: http://www.shute.org.uk/misc/freebsd_uptodate.html Thanks. :) Perhaps you came into this thread late, but that was my first attempt. But at that time, a few weeks ago, we were still at 9.0RC1 and my then buildworld/installworld attempt failed during the kernel compile step. Now that 9.0RC2 is available, I reckon it is worth a try dealing with the csup/buildworld/installworld process. I hope this works this time. Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: where to ask about problems with bsdinstall in 9.0RC2?
According to Thomas Mueller mueller6...@bellsouth.net on Sun, 11/20/11 at 05:46: It looks like tar in extraction mode automatically recognizes xz compression in the file to be extracted from. Section from the man page for tar in FreeBSD 9.0-RC1: -J, --xz (c mode only) Compress the resulting archive with xz(1). In extract or list modes, this option is ignored. Note that, unlike other tar implementations, this implementation recognizes XZ com- pression automatically when reading archives. You see? That just goes to show you... ;^) The above section is missing from my 8.2-STABLE platform tar(1) man page. The whole problem is my trying to get there from here - which was what started this thread... :-) Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: where to ask about problems with bsdinstall in 9.0RC2?
manually newfs needed partitions. I hope someone will correct any now-obsolete concerns I've expressed :) Thanks again. I think sysinstall is excellent and should be retained. I will try the bootonly approach _with_ sysinstall and see if I can get 9.0RC2 loaded properly. :-) Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: where to ask about problems with bsdinstall in 9.0RC2?
According to Robert Bonomi bon...@mail.r-bonomi.com on Sat, 11/19/11 at 10:08: IIRC, the error message was out of inodes. This means something was trying to put *lots* (where 'lots' is relative number, depending on the size of the filesystem :) of little files on the filesystem. You were _not_ out of 'free space' on the filesystem, just out of slots for file 'metadata'. Newfs, if not told specifically how many inodes to allocate, makes a 'guess' based on the size of the slice -- thus increasing the size of a partition will have an automatic 'side effect' of increasing the total number of inodes. However, by explicitly stating the number of inodes, or the inodes per unit of storage, when running newfs, one can get more (or fewer) inodew _without_ having to change partition sizes. Most significantly, one can do this -- change the number of inodes, that is -- *without* having to destroy/recreate any other partitions on the same physical device. SECONDLY, if this happened -during- the install, and the complaint was about /var -- as distinct from something like '/a/var', or '/mnt/var' Then the problem is *NOT* on the drives you are installing *ONTO*, but on the media you are installing _from_. At a guess, the installer is using /var -- probably /var/tmp -- to keep scratchpad files in, and there are not enough inodes for the installer. could it be unpacking tarfiles there, move/copy onto the 'target' media? You're installing from a memory stick right? You may need to rebuild the filesystem on the stick, _manually_ specifying a larger number of inodes for the filesystem that /var is part of. No that was not the error. The error was something along the lines of: var/ but I don't recall the exact text of the error message - the main point of my previous messages was to point out the missing leading slash, not /var, but just var - which at the time I thought was most unusual. This was happening during an attempted install of 9.0RC2 from DVD ISO as in: FreeBSD-9.0-RC2-i386-dvd1.iso and was not an attempt from a memory stick. Thanks for the reply, but based on another reply, I think my problem has stemmed from the use of bsdinstall which apparently doesn't do a very good job of installing a subsequent version of FreeBSD on top of an existing (prior) version of same. Had I been able to upgrade using the normal methods (buildworld and installworld) from 8.2-STABLE to 9.0RC1 or 9.0RC2 I would have, but during the kernel compile process I got a compile time error (that was trying to upgrade to RC1 just prior to the arrival of RC2) and there was no way I could deal with that. Interestingly enough, in looking around following that failed upgrade attempt, the RC1 ISOs and so forth were missing from ftp.freebsd.org which I thought was odd. Shortly thereafter RC2 was being seen around *.freebsd.org in various places, so I must have been making this attempt during the transition from RC1 to RC2 in all the distribution places. This convinced me to burn a new DVD (against the RC2 ISO) but then I got hammered by the not-ready-for-prime-time bsdintall program... :-( Thanks again. Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: where to ask about problems with bsdinstall in 9.0RC2?
According to Daniel Staal dst...@usa.net on Sat, 11/19/11 at 10:06: --As for the rest, it is mine. Just as a quick digression... xz has only marginal improvements in compressed size over bzip2, and takes a lot more cpu/memory resources to compress. In most cases, I'd say it's the wrong choice for a compression format. However, the one place where it is unequivocally the *best* choice is one that will make it well known: Distributing archives. It does beat bzip2 by a small amount, and it's *decompression* time is *much* faster than bzip2 - on par with gzip. Plus decompression can be done in a fixed amount of RAM, regardless of the size of the files being uncompressed. For files that are compressed once and then decompressed many times on many different boxes - like a FreeBSD release - it's a definite win. But for files that will be compressed and uncompressed regularly, or compressed and usually never touched again, it's worth thinking about what's the best balance of resources. Thanks for that explanation! :-) Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: where to ask about problems with bsdinstall in 9.0RC2?
According to Matthew Seaman m.sea...@infracaninophile.co.uk on Sat, 11/19/11 at 03:14: xz(1) is the latest compression program around. It usually gets better results than bzip2 so lots of usages are being switched to it. .txz is a tar archive compressed with xz. Thanks. Then it is so new that I'd not heard about it while trying to manage my other responsibilities... :-) Hmmm.. I wonder if the base.txz file on your install media has become corrupt? If you've got a FreeBSD machine around (any supported 7.x or 8.x would do), you could just mount your 9.0 disk on it, find that file wherever it is in the disk, and see if 'tar -tvf base.txz' will show you the contents without errors. Possible, but unlikely. Plus I doubt that 'tar -tvf base.txz' without a pipe having an xzcat(1) in front of the tar(1) command. Maybe there is an xz option for tar(1) during extraction mode, but my tar(1) man page doesn't list any, sigh... It does list -y and -z options for other compression/decompression modes, hmmm :-( The other possibility is that you ran out of space in the partition you were trying to write to. You'ld have to open an emergency holographic shell to investigate (does the new installer even have that wording? It should...) One thing to check is not only space usage but inode usage too. There's an ongoing discussion about installing onto small drives and whether the bytes-to-inode ratio should be modified there. As I have previously stated, my root, /var, and swap partitions are all 4 GB in size, and my /usr partition is 99 GB - likely plenty room in all. The lack of a leading '/' on the path you saw is normal -- your hard drive is mounted at something like /mnt while the system is installed onto it. The installer is just using paths relative to that mountpoint. Well, now that is interesting! I hadn't thought of that possibility... Thanks again for your reply. Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: where to ask about problems with bsdinstall in 9.0RC2?
According to Edward Martinez eam1edw...@gmail.com on Sat, 11/19/11 at 19:02: I got interested and downloaded it to try myself. I installed 9.0 in virtualbox using the guided option and it installed. just wondering if you tried installing with guided option instead of manual? Now I will try using manual and see what happens I did not try guided. Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
where to ask about problems with bsdinstall in 9.0RC2?
I tried to install 9.0RC2 from the DVD ISO today. This defaults to using bsdinstall instead of the 8.x sysinstall. This process gave me an error, but I'm not sure in which forum to discuss this problem/error. Thanks in advance. Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: where to ask about problems with bsdinstall in 9.0RC2?
According to Matthew Seaman m.sea...@infracaninophile.co.uk on Fri, 11/18/11 at 17:41: On 18/11/2011 21:27, William Bulley wrote: I tried to install 9.0RC2 from the DVD ISO today. This defaults to using bsdinstall instead of the 8.x sysinstall. This process gave me an error, but I'm not sure in which forum to discuss this problem/error. Thanks in advance. freesd-questions@ is fine to talk about this sort of problem. At least, initially. Give us more detail on exactly what you did, what then happened, (and maybe why you think that was wrong) and we can probably help you get your system installed. If it turns out to be a bug in the new installer rather than operator error, then freebsd-current@ is the place to take it. Okay, here goes. :-) I was loading a decent but somewhat older Dell laptop with FreeBSD for a friend who bailed since he didn't want to bother configuring Xorg. Since this is fairly trivial these days, I said, sure, I'd do that for you - silly me... :-( Anyway, do to the user requirements, I found it necessary to load a version 9.x system on this laptop. I burned this version to DVD: FreeBSD-9.0-RC2-i386-dvd1.iso The laptop had no trouble booting from this DVD. Unfortunately, I forgot about the new bsdinstall program. I was dubious but it seemed to start out okay. I had some User Interface issues with the Manual disk partition screen, but that is a matter of taste or a feature request, and not the bug. Everything progressed just fine as the various *.txz files were loaded, checked and installed. Or so it seemed... As the progress bar moved to the right toward 100% completion, a window popped up telling me that it (bsdinstall) could not handle the base.txz (BTW, what does the suffix .txz mean?) - it could not uncompress it and said something about unable to write and the string was something like: var/base.txz (note the lack of a leading slash in front of var). It asked me if I wanted to continue or restart and I said yes, but the bsdinstall started over from scratch and failed in the same manner. Unfortunately I had to bail on the attempt... :-( Prior to this, I had loaded and configured 8.2-RELEASE and had upgraded it to 8.2-STABLE. I csup'd the ports tree and built enough ports to run Xorg. And I got X11 running after a bit. But when I tried to upgrade again to 9.x (anything) I ran into problems there (slips my mind why at present) which led me to trying the FreeBSD-9.0-RC2-i386-dvd1.iso approach. What a mess... :-( Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: where to ask about problems with bsdinstall in 9.0RC2?
According to Edward Martinez eam1edw...@gmail.com on Fri, 11/18/11 at 19:53: Have you tried installing with ACPI disabled. http://www.freebsd.org/doc/handbook/bsdinstall-install-trouble.html#Q3.10.2.1. this also may be of some help: http://www.freebsd.org/doc/handbook/bsdinstall-partitioning.html Thanks. I will try disabling ACPI but this wasn't necessary for the install of 8.2-RELEASE from CD which, as I said, went in just as I expected. I would not think that much would have changed in 9.0RC2 in this area. Maybe I am wrong about that. The second URL describes the Manual vs. Guided install and partition section of bsdinstall. I had read this several days before the 9.0RC2 install attempt from DVD. It seemed pretty reasonable, but a little bit different from sysinstall. Was worth a try. What I saw when I selected Manual partitioning, was a complete tree: ad0 ad0s1 [FreeBSD Boot Manager from 8.2] ad0s1a [was my previous root partition] ad0s1d [was my previous swap partition] ad0s1d [was my previous /var partition] ad0s1e [was my previous /usr partition] or something very close to that, missing only my mount points from my previous 8.2-STABLE system. I added the mount points (this is the area where I thought bsdinstall had some weaknesses in the User Experience) and went on after selecting Finish. The problem occurred much later after I selected all four install files. When I said the equivalent of Go, it began the process of loading them off the DVD, checking their checksums, and compressing them prior to installing them. It was while processing the first (base.txz) chunk that the popup appeared giving me the unable to write or unable to uncompress message. Can't recall the exact error now some hours later... :-( So the extraction step failed the first file, and I never made it to the Post-Installation phase, sigh... :-( Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: where to ask about problems with bsdinstall in 9.0RC2?
According to Fbsd8 fb...@a1poweruser.com on Fri, 11/18/11 at 21:02: I think you have under sized /usr and the uncompress ran out of space during the install. Start over again, wipe the disk clean (ie: delete all slices)and re-allocate your slices with larger space allocations. Thanks. While this is an older Dell laptop as I said earlier, it still has a decent sized drive. And I am following the guidelines in the handbook at the beginning of section 2.6.5 Creating Partitions Using Disklabel: / (root) is 4 GB swap is 4 GB /var is 4 GB /usr is the rest of the disk - in this case 99 GB Bottom line, I think this is sufficient - it was for 8.2-RELEASE and -STABLE. Plus the handbook says at least 8 GB for /usr. Oh, and this is a dangerously dedicated drive housing only FreeBSD. That is, I'm using the entire disk for FreeBSD. Thanks again. Or, perhaps you are saying 4 GB is insufficient for /var? Since it seems to be complaining about not being able to write to var/. Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Thinkpad audio question
According to Warren Block wbl...@wonkity.com on Wed, 09/14/11 at 20:21: Two things you can do to improve the situation. Thanks. First, describe the appropriate settings and files on http://laptop.bsdgroup.de/freebsd/ Done. Then write some updates to the man page, or at least describe what is missing, and submit a PR. I will do this, but I first have to go through the procedure of how to do this (by reading the handbook, very likely). This can be worthwhile doing just for yourself. If a man page is missing something for me once, chances are I'll hit it again later. Helping others is a side benefit. It isn't for me that I am doing this. It is to help others - really. :-) Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Thinkpad audio question
According to Jakub Lach jakub_l...@mailplus.pl on Wed, 09/14/11 at 23:11: It was mav (Alexander Motin), he proposed those hints after I complained that sound stopped working after update. He wondered how I got sound to work in the first place, with hints I had previously. I would have wondered the same. The question that remains to be answered is: how did mav (Alexander Motin) suss out the details of how to do this in the first place? :-) I don't think pushing those specific hints somewhere would be so beneficial, subtle hardware revision could change pin associations. (e.g. Your friend's T500?) True, but it might give someone an idea of where to start looking... I don't think man page is missing something, it's verbose and exhaustive, with 4 examples of hints for various purposes. (The truth is out there! heh.) We can agree to disagree, perhaps. The man page is complete, I agree, but it isn't a great read for a user who doesn't understand audio hardware, has never dealt with anything other than stereo speakers and stereo headphones (with or without microphone). The four (4!) examples all refer to the one (1!) HP Compaq system. And these explanations don't give a good description of the connection between AS, NID, SEQ, etc. That is, there are examples there, but the explainations assume that the reader knows more about the underlying hardware and how audio systems and chips work in general than is likely the case for most users with laptops using the snd_hda(4) driver supported hardware. I hope that run-on sentence is comprehensible to folks... :-) The problem is, most people don't want (or don't know they need) to swap line-out and speaker functions, to split headphones and mic to separate device etc. This is completly true - I agree wholeheartedly with this. They do not know why default pinout is not working as it should, and what they should change. Yep. They just want to have headphones and speakers working as intended :) Well, d'oh! :-) But I'm afraid this can't be directly addressed, as possibilities of default wrong pin associations are endless. Sadly, I must agree with you here also, sigh... :-( If you think otherwise you are free to submit PR as well :) I am going to submit a PR (when I learn how from the handbook), but not to suggest new text or wording. Rather, I will make suggestions of areas that could be improved for readability and understanding. best regards, - Jakub Lach PS. I suspected that If by chance my device.hints will just work, the pedantic engineer in you would be silenced somehow :P Well, then you don't know me very well then, do you?? ;^) Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Thinkpad audio question
A friend of mine has an IBM T500 Thinkpad which is nearly identical to the one I have. We both have interesting audio issues. Any ideas as to why the problems explained below exist would be greatly appreciated. My T500 shows two devices /dev/mixer0 and /dev/mixer1 corresponding to pcm0 and pcm1 as displayed by % cat /dev/sndstat in 8.2-PRERELEASE from January 2011. I am able to hear audio on the built-in speakers using /dev/mixer1 but not able to hear audio when plugging stereo headphones into the green audio out jack. However, the speaker audio is muted when the headphones are plugged in. I have tried two different head sets to rule out flawed hardware. My friend's T500 is more up-to-date than mine (likely 8.2-STABLE) but in his case headphone audio works perfectly and he has had no luck in getting audio out of his built-in laptop speakers. Very weird... This situation sucks, but we have not been able to suss out what the problem is. He and I have been running FreeBSD for over a decade, so we are not clueless, but this laptop audio weirdness has us stumped. Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Thinkpad audio question
According to Daniel Staal dst...@usa.net on Wed, 09/14/11 at 10:20: Quick thought: What versions of the BIOS are each of you running? Can't speak for him, but here is the output from biosdecode(8): thinkpad% biosdecode | m # biosdecode 2.10 VPD present. BIOS Build ID: 6FET66WW Box Serial Number: R8XYZ03 Motherboard Serial Number: VQ0VP98J5WA Machine Type/Model: 2081CTO SMBIOS 2.4 present. Structure Table Length: 2627 bytes Structure Table Address: 0x000E0010 Number Of Structures: 74 Maximum Structure Size: 120 bytes BIOS32 Service Directory present. Revision: 0 Calling Interface Address: 0x000FDC80 ACPI 2.0 present. OEM Identifier: LENOVO RSD Table 32-bit Address: 0x7CB6A207 XSD Table 64-bit Address: 0x7CB6A273 PNP BIOS 1.0 present. Event Notification: Not Supported Real Mode 16-bit Code Address: E192:1920 Real Mode 16-bit Data Address: 0040: 16-bit Protected Mode Code Address: 0x000F8AD7 16-bit Protected Mode Data Address: 0x0400 I don't know what to make of all this. I hope this answers your above question. :-) Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Thinkpad audio question
According to Jakub Lach jakub_l...@mailplus.pl on Wed, 09/14/11 at 13:10: See man snd_hda, you probably need to set device.hints. For example, I with T400 have something like this in device hints: hint.hdac.0.cad0.nid22.config=as=1 seq=15 hint.hdac.0.cad0.nid24.config=as=3 hint.hdac.0.cad0.nid26.config=as=1 hint.hdac.0.cad0.nid29.config=as=2 Thanks. This looks very promising. It is too bad the man page is so busy and complex... :-( I had viewed this man page before, but I hoped I would never have to deal with the details. And I haven't until now... :-) One thing that could be made more clear is the lack of how to invoke the verbose or reporting mode. The word verbose appears just three (3!) times in the man page, but there is no explicit description of how to get the driver to provide a verbose report. The word report in the EXAMPLES section refers to an HP/Compaq system housing a Realtek ALC888 HDA codec whose driver can list the default pin configuration as show. Except the man page never explains how. :-( After a great deal of back and forth, I finally discovered the hint dev.hdac.%d.pindump just above the EXAMPLES section. As soon as I put that entry in my /etc/sysctl.conf file (dev.hdac.0.pindump=1) and did a reboot, the following appeared in my dmesg(8) output: :-) Intel 82801I HDAC mem 0xfc02-0xfc023fff irq 17 at device 27.0 on pci0 High Definition Audio Controller Driver Revision: 20100226_0142 HDA Codec #0: Conexant CX20561 (Hermosa) HDA Codec #1: Conexant (Unknown) = this seems confusing... Dumping AFG cad=0 nid=1 pins: nid 22 0x022140f0 as 15 seq 0Headphones Jack jack 1 loc 2 color Green misc 0 Caps:OUT HP Sense: 0x7fff nid 23 0x61a190f0 as 15 seq 0 Mic None jack 1 loc 33 color Pink misc 0 [DISABLED] Caps: IN VREF Sense: 0x7fff nid 24 0x02a190f0 as 15 seq 0 Mic Jack jack 1 loc 2 color Pink misc 0 Caps: IN VREF Sense: 0x7fff nid 25 0x40f000f0 as 15 seq 0 Other None jack 0 loc 0 color Unknown misc 0 [DISABLED] Caps:OUT Sense: 0x7fff nid 26 0x901701f0 as 15 seq 0 Speaker Fixed jack 7 loc 16 color Unknown misc 1 Caps:OUTEAPD nid 27 0x40f001f0 as 15 seq 0 Other None jack 0 loc 0 color Unknown misc 1 [DISABLED] Caps:OUTEAPD nid 28 0x40f001f0 as 15 seq 0 Other None jack 0 loc 0 color Unknown misc 1 [DISABLED] Caps:OUT nid 29 0x90a601f0 as 15 seq 0 Mic Fixed jack 6 loc 16 color Unknown misc 1 Caps: IN NumGPIO=4 NumGPO=0 NumGPI=0 GPIWake=0 GPIUnsol=1 GPIO: data=0x enable=0x direction=0x wake=0x unsol=0xsticky=0x Dumping AFG cad=0 nid=1 pins: nid 22 0x022140f0 as 15 seq 0Headphones Jack jack 1 loc 2 color Green misc 0 Caps:OUT HP Sense: 0x7fff nid 23 0x61a190f0 as 15 seq 0 Mic None jack 1 loc 33 color Pink misc 0 [DISABLED] Caps: IN VREF Sense: 0x7fff nid 24 0x02a190f0 as 15 seq 0 Mic Jack jack 1 loc 2 color Pink misc 0 Caps: IN VREF Sense: 0x7fff nid 25 0x40f000f0 as 15 seq 0 Other None jack 0 loc 0 color Unknown misc 0 [DISABLED] Caps:OUT Sense: 0x7fff nid 26 0x901701f0 as 15 seq 0 Speaker Fixed jack 7 loc 16 color Unknown misc 1 Caps:OUTEAPD nid 27 0x40f001f0 as 15 seq 0 Other None jack 0 loc 0 color Unknown misc 1 [DISABLED] Caps:OUTEAPD nid 28 0x40f001f0 as 15 seq 0 Other None jack 0 loc 0 color Unknown misc 1 [DISABLED] Caps:OUT nid 29 0x90a601f0 as 15 seq 0 Mic Fixed jack 6 loc 16 color Unknown misc 1 Caps: IN NumGPIO=4 NumGPO=0 NumGPI=0 GPIWake=0 GPIUnsol=1 GPIO: data=0x enable=0x direction=0x wake=0x unsol=0xsticky=0x Now, re-reading the snd_hda man page with the above in hand, I just may be able to make changes similar to what you have shown above provided I can make sense of the above verbose output. Thanks for all your help. :-) Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Thinkpad audio question
According to Jakub Lach jakub_l...@mailplus.pl on Wed, 09/14/11 at 16:25: For maximum verbosity you can also try setting in sysctl.conf hw.snd.verbose=3 I've had that setting for years, but it didn't help in this case, sigh... :-( and $ cat /dev/sndstat then. Sure, that is what I always do to check which sound driver I have. Not sure if you really need it though. True, it wasn't any help for this problem. As for man page, that was my experience as well, and I just shamelessly copied device.hints some kind spirit provided, so I'm not exactly pinout expert either :) Heh... :-) On a lighter note, once correct pinout will be set, you shouldn't have any more problems with CX20561, it's common and well supported chip. That is nice to know... Here is the deal: when I % cat /dev/sndstat it shows both pcm0 and psm1 as: HDA Conexant CX20561 (Hermosa) but not in the verbose output below from dmesg(8). Right now I have this (after some reformatting - no TABs either!): HDA Codec #0: Conexant CX20561 (Hermosa) HDA Codec #1: Conexant (Unknown) = not sure why this is Dumping AFG cad=0 nid=1 pins: nid 22 0x022140f0 as 15 seq 0 Headphones Jack jack 1 loc 2 color Green misc 0Caps: OUT HP Sense: 0x 7fff nid 23 0x61a190f0 as 15 seq 0 Mic None jack 1 loc 33 color Pink misc 0 [DISABLED] Caps: IN VREF Sense: 0x 7fff nid 24 0x02a190f0 as 15 seq 0 Mic Jack jack 1 loc 2 color Pink misc 0Caps: IN VREF Sense: 0x 7fff nid 25 0x40f000f0 as 15 seq 0 Other None jack 0 loc 0 color Unknown misc 0 [DISABLED] Caps: OUT Sense: 0x 7fff nid 26 0x901701f0 as 15 seq 0 Speaker Fixed jack 7 loc 16 color Unknown misc 1Caps: OUT EAPD nid 27 0x40f001f0 as 15 seq 0 Other None jack 0 loc 0 color Unknown misc 1 [DISABLED] Caps: OUT EAPD nid 28 0x40f001f0 as 15 seq 0 Other None jack 0 loc 0 color Unknown misc 1 [DISABLED] Caps: OUT nid 29 0x90a601f0 as 15 seq 0 Mic Fixed jack 6 loc 16 color Unknown misc 1Caps: IN After disregarding the DISABLED lines I have this: nid 22 0x022140f0 as 15 seq 0 Headphones Jack jack 1 loc 2 color Green misc 0Caps: OUT HP Sense: 0x 7fff nid 24 0x02a190f0 as 15 seq 0 Mic Jack jack 1 loc 2 color Pink misc 0Caps: IN VREF Sense: 0x 7fff nid 26 0x901701f0 as 15 seq 0 Speaker Fixed jack 7 loc 16 color Unknown misc 1Caps: OUT EAPD nid 29 0x90a601f0 as 15 seq 0 Mic Fixed jack 6 loc 16 color Unknown misc 1Caps: IN The snd_hda(4) man page does not discuss what EAPD is, nor what VREF is, nor what HP is. It also does not discuss Caps: but I can infer what IN and OUT are. :-) So, I have a speaker (big whoop) and two jacks: one pink and one green (but I already knew that, too). I note that there is only one AS (15, or is that 14?) and only one seq (0) which doesn't mesh well with your earlier T400 suggestion: hint.hdac.0.cad0.nid22.config=as=1 seq=15 hint.hdac.0.cad0.nid24.config=as=3 hint.hdac.0.cad0.nid26.config=as=1 hint.hdac.0.cad0.nid29.config=as=2 For example, where did 'AS'es 1, 2, 3 come from? And where did seq 15 come from? :-( However, it is mighty curious that your four nids match my four non-DISABLED nids - hmmm... :-) Recognizing from your comments above that you may not be able to answer these rhetorical questions, but if I just try your suggestions blind what are the chances it will just work for me? I do hate just copying something without knowing what the heck it means -- just the pedantic engineer in me, I reckon... :-) The snd_hda(4) man page is not very helpful in explaining what your four hints would do for my T500 problem, but I guess it is worth a try. Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Thinkpad audio question
According to Jakub Lach jakub_l...@mailplus.pl on Wed, 09/14/11 at 17:01: I would love to investigate it properly further, however I'm critically low on time, so I can only offer pinout dump with my device.hints at this time, sorry http://pastebin.com/ig54CwT9 good luck, Thanks! But no thanks -- because I got it to work with your T400 hints! :-) You have been most helpful and I really appreciate it. I wonder just who came up with those in the first place? :-) Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
can't build graphics/xfig-3.2.5b on 8.2-STABLE nor databases/p5-DBD-Oracle with lang/perl5.14
First there is the xfig issue: No matter what the setting is for I18N (WITH or WITHOUT) there is this: cc -c -O2 -fno-strict-aliasing -pipe -I/usr/local/include -I/usr/local/include/libpng -I/usr/local/include/X11 -I. -I/usr/local/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -DUSE_INLINE -DUSE_XPM -DXAW3D -DXAW3D1_5E -DUSE_JPEG -DI18N -DNEWARROWTYPESe_edit.c e_edit.c: In function 'generic_window': e_edit.c:3214: warning: cast from pointer to integer of different size e_edit.c: In function 'str_panel': e_edit.c:4252: error: 'XtNinternational' undeclared (first use in this function) e_edit.c:4252: error: (Each undeclared identifier is reported only once e_edit.c:4252: error: for each function it appears in.) *** Error code 1 Stop in /usr/ports/graphics/xfig/work/xfig.3.2.5b. *** Error code 1 Stop in /usr/ports/graphics/xfig. *** Error code 1 I tracked this down to a problem in the Imakefile around line 153: #define I18N This line was not commented out when building xfig using: # make install (and WITHOUT_I18N=true inside /var/db/ports/xfig/options) Looking further I found these two lines: -XCOMM #define I18N +#define I18N inside the /usr/ports/graphics/xfig/files/patch-Imakefile patch file. I think this may be incorrect. After commenting out the #define in the Imakefile, the build of xfig was successful. Secondly, I found that building databases/p5-DBD-Oracle when Perl 5.14 (from lang/perl5.14) was present failed in the compilation of the Oracle.c file. It seems that several Perl constants sv_undef, sv_yes, and sv_no (and others) changed between Perl 5.12.3 and Perl 5.14 to PL_sv_undef, PL_yes, and PL_sv_no, respectively. I didn't take the time to debug this further since I had other Perl 5.14 issues that forced me to completely rebuild my system from scratch starting with Perl 5.12.3 (lang/perl5.12) this time. Once I had Perl 5.12.3 built, databases/p5-DBD-Oracle built just fine. My other problems with Perl 5.14 were observed trying to launch apache2 (2.2.19) with mod_perl2 (2.0.5). Those problems also went away once I rebuilt my ports starting with Perl 5.12.3 version. This makes me suspect Perl 5.14 changes or the effect those changes have had on other ports in the ports tree. Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
system upgrade introduced oddball apache error...
Running FreeBSD 8.2-STABLE #0: Thu Jun 9 09:25:05 EDT 2011 on i386 and rebuilt all my ports from source shortly after the upgrade. Got weird error when I tried to start apache2 (using % apachectl -t first): [Mon Jun 13 10:16:15 2011] [error] syntax error at (eval 21) line 1, near require Apache2::Const -\n [Mon Jun 13 10:16:15 2011] [error] Can't load Perl module Apache2::Const -compile = ':common' for server localhost:80, exiting... The Perl module in question is present here: freebsd% ls -l /usr/local/lib/perl5/site_perl/5.14.0/mach/Apache2/Const.pm -r--r--r-- 1 root wheel 25924 Jun 10 17:08 /usr/local/lib/perl5/site_perl/5.14.0/mach/Apache2/Const.pm The only reference to it is in an Apache config include file: PerlModule Apache2::Const -compile = ':common' I have these ports: perl-5.14.0 apache-2.2.19 ap22-mod_perl2-2.0.5,3 In the /usr/local/etc/apache22/httpd.conf file, there is this line: LoadModule perl_module libexec/apache22/mod_perl.so but the httpd.conf file was unchanged from before the upgrade. Neither of these two commands gave any output at all: freebsd% perl -e 'use Apache2::Const qw( :common ); freebsd% perl -M'Apache2::Const -compile = qw(:common)' -e 1; This command gave one line of output: freebsd% perl -MApache2::Const -e 'print $Apache2::Const::VERSION, \n'; 2.05 This problem did not occur before the upgrade when I was running: perl-5.12.3 apache-2.2.17_1 ap22-mod_perl2-2.0.4_2,3 I don't know how to debug this problem. No log files in /var/log were changed by running the apachectl(8) command and there have been no new lines added to /var/log/httpd-error.log since I rebooted and shut down apache2 on June 9th as part of the upgrade. Any and all ideas welcome. Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problem building GIMP 2.6.11 on 8.2-PRERELEASE
]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/usr/ports/graphics/gimp-app/work/gimp-2.6.11/plug-ins' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/graphics/gimp-app/work/gimp-2.6.11' gmake: *** [all] Error 2 *** Error code 1 Stop in /usr/ports/graphics/gimp-app. *** Error code 1 Stop in /usr/ports/graphics/gimp-app. *** Error code 1 Stop in /usr/ports/graphics/gimp. *** Error code 1 Stop in /usr/ports/graphics/gimp. Investigating this I found poppler.h in this directory: /usr/local/include/poppler/glib/ on another system recently upgraded where the Gimp had built successfully. This directory did not exist here! That directory was the one I had to manually delete earlier when making clean for graphics/poppler. Since this directory was not recreated (coupled with the fact that it wasn't removed via make deinstall) indicates there may be a problem with the packing list of graphics/poppler. I found the missing include files in this directory: /usr/ports/graphics/poppler/work/poppler-0.14.5/glib/ After I copied them to /usr/local/include/poppler/glib/ (having made it with mkdir) I was successfully able to build the Gimp. All this is very strange... Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problem building GIMP 2.6.11 on 8.2-PRERELEASE
According to Lowell Gilbert freebsd-questions-lo...@be-well.ilk.org on Thu, 01/27/11 at 11:04: William Bulley w...@umich.edu writes: Everything up to this point builds okay. Then this happens: Making all in common gmake[3]: Entering directory `/usr/ports/graphics/gimp-app/work/gimp-2.6.11/plug-ins/common' cc -DHAVE_CONFIG_H -I. -I../.. -I../.. -D_THREAD_SAFE -D_REENTRANT -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/atk-1.0 -I/usr/local/include/cairo -I/usr/local/include/gdk-pixbuf-2.0 -I/usr/local/include/pango-1.0 -I/usr/local/include/gio-unix-2.0/ -I/usr/local/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/pixman-1 -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/local/include -DGIMP_DISABLE_DEPRECATED -DGDK_MULTIHEAD_SAFE -DGTK_MULTIHEAD_SAFE -O2 -fno-strict-aliasing -pipe -Wall -Wdeclaration-after-statement -Wmissing-prototypes -Wmissing-declarations -Winit-self -Wpointer-arith -Wold-style-definition -MT file_pdf-file-pdf.o -MD -MP -MF .deps/file_pdf-file-pdf.Tpo -c -o file_pdf-file-pdf.o `test -f 'file-pdf.c' || echo './'`file-pdf.c file-pdf.c:30:21: error: poppler.h: No such file or directory [...] And poppler.h exists here: /usr/local/include/poppler/glib/poppler.h and here: /usr/ports/graphics/poppler/work/poppler-0.14.5/glib/poppler.h and here: /usr/ports/graphics/poppler-gtk/work/poppler-0.14.5/glib/poppler.h and they are all identical. Only the first counts, and it's the one that should be used. Just wanted to show that the include file was present. You may be doing something strange in the build; you don't mention how you started the build. Definitely make sure you do a make clean before restarting it, and make sure that poppler shows up up in the list of installed ports (pkg_info). I start the build in graphics/gimp followed by make install freebsd% pkg_info | grep -i poppler poppler-0.14.5 A PDF rendering library poppler-data-0.4.4 Poppler encoding data poppler-gtk-0.14.5 Gtk bindings to poppler Same results doing a make install after a make clean... :-( Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problem building GIMP 2.6.11 on 8.2-PRERELEASE
According to David Demelier demelier.da...@gmail.com on Thu, 01/27/11 at 11:39: It seems that gmake does not call `pkg-config --libs --cflags poppler`. do you have pkg-config and poppler installed correctly? /usr/local/libdata/pkgconfig/poppler-cairo.pc /usr/local/libdata/pkgconfig/poppler-cpp.pc /usr/local/libdata/pkgconfig/poppler-splash.pc /usr/local/libdata/pkgconfig/poppler.pc These files must be installed by poppler. In your case I will reinstall graphics/poppler by hand and verify that pkg-config finds it. You mention gmake, yet I use # make install all the time. Is this really gmake under the covers? I see both executables and they differ: freebsd% ls -l /usr/local/bin/gmake /usr/bin/make -r-xr-xr-x 1 root wheel 378392 Jan 25 10:12 /usr/bin/make -r-xr-xr-x 1 root wheel 156592 Jan 25 11:29 /usr/local/bin/gmake This is what I found when looking for those four above files: freebsd% ls -l /usr/local/libdata/pkgconfig/poppler-cairo.pc /usr/local/libdata/pkgconfig/poppler-cpp.pc /usr/local/libdata/pkgconfig/poppler-splash.pc /usr/local/libdata/pkgconfig/poppler.pc ls: /usr/local/libdata/pkgconfig/poppler-cairo.pc: No such file or directory -r--r--r-- 1 root wheel 304 Jan 27 11:43 /usr/local/libdata/pkgconfig/poppler-cpp.pc -r--r--r-- 1 root wheel 222 Jan 27 11:43 /usr/local/libdata/pkgconfig/poppler-splash.pc -r--r--r-- 1 root wheel 222 Jan 27 11:43 /usr/local/libdata/pkgconfig/poppler.pc I rebuilt (make deinstall; make clean; make install) graphics/poppler. It made and installed cleanly (as did pkg-config earlier this week). I have these packages: poppler-0.14.5 A PDF rendering library poppler-data-0.4.4 Poppler encoding data poppler-gtk-0.14.5 Gtk bindings to poppler pkg-config-0.25_1 A utility to retrieve information about installed libraries Which is the correct port to install this poppler-cairo file? I see two copies in the ports tree: /usr/ports/graphics/poppler/work/poppler-0.14.5/poppler-cairo.pc and /usr/ports/graphics/poppler-gtk/work/poppler-0.14.5/poppler-cairo.pc When I run this: # pkg-config --libs --cflags poppler I see this: -I/usr/local/include/poppler -L/usr/local/lib -lpoppler Is that to be expected? Note that the file poppler.h exists here: /usr/local/include/poppler/glib/poppler.h so would that not imply that -I/usr/local/include/poppler is wrong and instead should be: -I/usr/local/include/poppler/glib ?? Thanks for all the suggestions, but I am still in a pickle... :-( Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problem building GIMP 2.6.11 on 8.2-PRERELEASE
According to Chris Brennan xa...@xaerolimit.net on Thu, 01/27/11 at 12:03:
gmake is GNU Make, some applications don't talk nice w/ bsdmake ('make' on
your bsd system). If your installing GIMP from ports then you should be
correctly using something like 'make install clean'. The only time I've
invoked gmake was when building something by hand vs letting a ports
makefile do the footwork for me.
Okay, thanks. However I still have a broken poppler (somehow) which
means I am unable to build the Gimp from the ports tree. What should I
next look for? I have re-built/installed graphics/poppler and also
graphics/gimp (using make install) but I still get the same error. :-(
Regards,
web...
--
William Bulley Email: w...@umich.edu
72 characters width template -|
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Problem building GIMP 2.6.11 on 8.2-PRERELEASE
Everything up to this point builds okay. Then this happens: Making all in common gmake[3]: Entering directory `/usr/ports/graphics/gimp-app/work/gimp-2.6.11/plug-ins/common' cc -DHAVE_CONFIG_H -I. -I../.. -I../.. -D_THREAD_SAFE -D_REENTRANT -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/atk-1.0 -I/usr/local/include/cairo -I/usr/local/include/gdk-pixbuf-2.0 -I/usr/local/include/pango-1.0 -I/usr/local/include/gio-unix-2.0/ -I/usr/local/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/pixman-1 -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/local/include -DGIMP_DISABLE_DEPRECATED -DGDK_MULTIHEAD_SAFE -DGTK_MULTIHEAD_SAFE -O2 -fno-strict-aliasing -pipe -Wall -Wdeclaration-after-statement -Wmissing-prototypes -Wmissing-declarations -Winit-self -Wpointer-arith -Wold-style-definition -MT file_pdf-file-pdf.o -MD -MP -MF .deps/file_pdf-file-pdf.Tpo -c -o file_pdf-file-pdf.o `test -f 'file-pdf.c' || echo './'`file-pdf.c file-pdf.c:30:21: error: poppler.h: No such file or directory file-pdf.c:70: error: expected ')' before '*' token file-pdf.c:77: error: expected ')' before '*' token file-pdf.c:80: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token file-pdf.c:83: error: expected ')' before '*' token file-pdf.c: In function 'run': file-pdf.c:330: error: 'PopplerDocument' undeclared (first use in this function) file-pdf.c:330: error: (Each undeclared identifier is reported only once file-pdf.c:330: error: for each function it appears in.) file-pdf.c:330: error: 'doc' undeclared (first use in this function) file-pdf.c:331: warning: ISO C90 forbids mixed declarations and code file-pdf.c:356: warning: implicit declaration of function 'open_document' file-pdf.c:364: warning: implicit declaration of function 'load_dialog' file-pdf.c:380: error: 'PopplerPage' undeclared (first use in this function) file-pdf.c:380: error: 'test_page' undeclared (first use in this function) file-pdf.c:380: warning: implicit declaration of function 'poppler_document_get_page' file-pdf.c:405: warning: implicit declaration of function 'load_image' file-pdf.c:449: error: 'page' undeclared (first use in this function) file-pdf.c:453: warning: implicit declaration of function 'poppler_page_get_size' file-pdf.c:458: warning: implicit declaration of function 'get_thumbnail' file-pdf.c:458: warning: assignment makes pointer from integer without a cast file-pdf.c: At top level: file-pdf.c:515: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token file-pdf.c:570: error: expected ')' before '*' token file-pdf.c:680: error: expected ')' before '*' token file-pdf.c:729: error: expected specifier-qualifier-list before 'PopplerDocument' file-pdf.c: In function 'thumbnail_thread': file-pdf.c:762: warning: implicit declaration of function 'poppler_document_get_n_pages' file-pdf.c:762: error: 'ThreadData' has no member named 'document' file-pdf.c:768: error: 'ThreadData' has no member named 'selector' file-pdf.c:772: error: 'ThreadData' has no member named 'document' file-pdf.c:773: warning: assignment makes pointer from integer without a cast file-pdf.c:777: error: 'ThreadData' has no member named 'stop_thumbnailing' file-pdf.c: At top level: file-pdf.c:785: error: expected ')' before '*' token gmake[3]: *** [file_pdf-file-pdf.o] Error 1 gmake[3]: Leaving directory `/usr/ports/graphics/gimp-app/work/gimp-2.6.11/plug-ins/common' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/usr/ports/graphics/gimp-app/work/gimp-2.6.11/plug-ins' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/graphics/gimp-app/work/gimp-2.6.11' gmake: *** [all] Error 2 *** Error code 1 Stop in /usr/ports/graphics/gimp-app. *** Error code 1 Stop in /usr/ports/graphics/gimp-app. *** Error code 1 Stop in /usr/ports/graphics/gimp. *** Error code 1 Stop in /usr/ports/graphics/gimp. And poppler.h exists here: /usr/local/include/poppler/glib/poppler.h and here: /usr/ports/graphics/poppler/work/poppler-0.14.5/glib/poppler.h and here: /usr/ports/graphics/poppler-gtk/work/poppler-0.14.5/glib/poppler.h and they are all identical. Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg 7.5 and OpenMotif: mouse stuck in box
Giuseppe Pagnoni wrote: I am resending this because it seems to me a really critical bug (prevents you from using OpenMotif or lesstif applications), but apparently nothing has been changed since last july. Upgrading xorg to 1.7.7 does fix the problem, but I wonder if this may cause dependency problems in the ports tree. Also, if this is the correct fix, is there a reason why it hasn't been integrated in the ports yet? thanks again giuseppe I am having a problem with xorg 1.7.5 and OpenMotif resulting in the mouse being stuck in certain areas of the Motif windows that are supposed to open dialog boxes when right-clicked. I noticed that somebody else reported the problem already in this list, and that it seems to have been fixed in xorg 1.7.7. However xorg 1.7.7 is not yet available in the ports tree, nor it looks like a patch is in for the current version (I tried to recompile xorg today after a port tree update). Is manually compiling Xorg the only solution right now? thanks in advance for any advice giuseppe This is what I found recently. Hope this helps you. - Forwarded message from William Bulley w...@umich.edu - To: FreeBSD Questions freebsd-questions@freebsd.org From: William Bulley w...@umich.edu Date: Thu, 2 Sep 2010 11:31:15 -0400 Subject: SOLVED: serious (for me) Xorg 7.5 mouse/kbd problem in 8.1-STABLE Cc: x...@freebsd.org, st...@freebsd.org See below for details of solution. - Forwarded message from William Bulley w...@umich.edu - To: FreeBSD Questions freebsd-questions@freebsd.org From: William Bulley w...@umich.edu Date: Wed, 25 Aug 2010 07:38:34 -0400 Subject: serious (for me) Xorg 7.5 mouse/kbd problem in 8.1-STABLE For years I have run Open-Motif on FreeBSD without issue. I use a USB keyboard and a USB three button mouse attached to a Dell Optiplex 960. This combination has worked fine for the past year. This week I upgraded from 8.0-STABLE circa January 2010 to 8.1-STABLE. I do this by doing a buildworld/installworld sequence after csup-ing stable-supfile and rebooting. In this case I also pkg_deleted all of my ports and am rebuilding them from source. Building Xorg is one of the very first ports I attempt since I prefer to work in xterms not virtual terminals. This upgrade moved me from Xorg 7.3 to Xorg 7.5, but Open-Motif stayed the same - open-motif-2.2.3_6 - it hasn't changed in years. After building Xorg, as root, I ran the Xorg -configure command to generate my xorg.conf.new file. Since a working /etc/X11/xorg.conf file was still around after the upgrade from 8.0-STABLE/Xorg 7.3, I felt no need to change anything in that file (later file comparisons confirmed that nothing had changed). My only relevant additions to /etc/X11/xorg.conf are these: Section ServerFlags Option AutoAddDevices off Option DontZap false EndSection In my /etc/rc.conf file I have dbus and hald enabled, and that has not changed since the beginning of 2010 after the confusion abated. As a normal user, I start Xorg using /usr/local/bin/xinit as always. I have several xterms configured in my ~/.xinitrc file. All those came up in the correct location and state. I was able to open those that started in iconic mode. In an open/raised xterm I could enter carriage returns and see my shell prompt move down the window. But when I tried to close/minimize an open/raised xterm, things failed. I use the following keyboard/mouse combination (configured in my .mwmrc file) to close (minimize) an xterm (and other applications): Shift Btn3Click window f.minimize This is also unchanged for some years. This particular setting has no bearing on the problem I came across yesterday. I merely state it for the record. However, this configuration triggers the bug. The problem is as soon as I use that Shift/Btn3Click combination, my arrow cursor disappears, then I cannot move to or select other xterms - I am frozen, or locked, into the xterm I was trying to close/minimize. All I can do at this point is to kill(1) the /usr/local/bin/xinit command to return to the virtual terminal where I launched my Xorg session. I am now reluctantly using the good old /usr/local/bin/twm which is always built when Xorg is built from source. I am at a loss as to what to look for next. I suspect Xorg, or the keyboard and mouse driver, not the video driver, that came with. It might be a problem with hald(8), but again, I don't know how to debug this. Any help with this very odd bug would be greatly appreciated. - End forwarded message - This problem is known (and fixed) in newer versions of xorg-server. See this URL for details of the problem. http://cgit.freedesktop.org/xorg/xserver/commit/?id=1884db430a5680e37e94726dff46686e2218d525 I have also attached the changes I made to the dit/events.c file. After rebuilding xorg-server with those patches, the Open Motif (mwm) window manager now works with the above
Re: Xorg 7.5 and OpenMotif: mouse stuck in box
According to Giuseppe Pagnoni gpagn...@gmail.com on Mon, 10/11/10 at 10:57: thank you very much for your reply, it does seem to be the same type of bug. However, and I apologize for being dense here, it is not immediate to me how to proceed practically to apply the patch from within the ports framework. Also, I still wonder why the patch hasn't been incorporated in the tree given that the bug is known I am not able to answer your final question - that is left to the ports maintainers to address. I simply installed the latest (was it 1.7.5) xorg-server at that time and added those half dozen patches. If 1.7.7 solved the problem, then I'm not sure what issue(s) you have. If you want to have FreeBSD ports upgraded, I would contact the port's maintainers directly. I chose not to install xorg-server 1.7.7 since I was unsure if there were other dependencies or issues that might arise from doing so. I'm not used to patching a mature, released port, so for me even that was a leap of faith! :-) Just for clarity, I did not formally patch this port (xorg-server). I went into the directory tree beneath the work directory, found the dit/events.c file, and made those above mentioned (about six or so) small source code patches. I then re-made the port and re-installed the port. After it tested successfully, I reported my results to the -questions list in case it would help others. YMMV. And good luck! Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
SOLVED: serious (for me) Xorg 7.5 mouse/kbd problem in 8.1-STABLE
See below for details of solution.
- Forwarded message from William Bulley w...@umich.edu -
To: FreeBSD Questions freebsd-questions@freebsd.org
From: William Bulley w...@umich.edu
Date: Wed, 25 Aug 2010 07:38:34 -0400
Subject: serious (for me) Xorg 7.5 mouse/kbd problem in 8.1-STABLE
For years I have run Open-Motif on FreeBSD without issue.
I use a USB keyboard and a USB three button mouse attached to a Dell
Optiplex 960. This combination has worked fine for the past year.
This week I upgraded from 8.0-STABLE circa January 2010 to 8.1-STABLE.
I do this by doing a buildworld/installworld sequence after csup-ing
stable-supfile and rebooting. In this case I also pkg_deleted all of
my ports and am rebuilding them from source. Building Xorg is one of
the very first ports I attempt since I prefer to work in xterms not
virtual terminals.
This upgrade moved me from Xorg 7.3 to Xorg 7.5, but Open-Motif stayed
the same - open-motif-2.2.3_6 - it hasn't changed in years.
After building Xorg, as root, I ran the Xorg -configure command to
generate my xorg.conf.new file. Since a working /etc/X11/xorg.conf
file was still around after the upgrade from 8.0-STABLE/Xorg 7.3, I
felt no need to change anything in that file (later file comparisons
confirmed that nothing had changed).
My only relevant additions to /etc/X11/xorg.conf are these:
Section ServerFlags
Option AutoAddDevices off
Option DontZap false
EndSection
In my /etc/rc.conf file I have dbus and hald enabled, and that has
not changed since the beginning of 2010 after the confusion abated.
As a normal user, I start Xorg using /usr/local/bin/xinit as always.
I have several xterms configured in my ~/.xinitrc file. All those
came up in the correct location and state. I was able to open those
that started in iconic mode. In an open/raised xterm I could enter
carriage returns and see my shell prompt move down the window. But
when I tried to close/minimize an open/raised xterm, things failed.
I use the following keyboard/mouse combination (configured in my
.mwmrc file) to close (minimize) an xterm (and other applications):
Shift Btn3Click window f.minimize
This is also unchanged for some years. This particular setting has
no bearing on the problem I came across yesterday. I merely state
it for the record. However, this configuration triggers the bug.
The problem is as soon as I use that Shift/Btn3Click combination,
my arrow cursor disappears, then I cannot move to or select other
xterms - I am frozen, or locked, into the xterm I was trying to
close/minimize. All I can do at this point is to kill(1) the
/usr/local/bin/xinit command to return to the virtual terminal
where I launched my Xorg session.
I am now reluctantly using the good old /usr/local/bin/twm which
is always built when Xorg is built from source. I am at a loss
as to what to look for next. I suspect Xorg, or the keyboard and
mouse driver, not the video driver, that came with. It might be
a problem with hald(8), but again, I don't know how to debug this.
Any help with this very odd bug would be greatly appreciated.
- End forwarded message -
This problem is known (and fixed) in newer versions of xorg-server.
See this URL for details of the problem.
http://cgit.freedesktop.org/xorg/xserver/commit/?id=1884db430a5680e37e94726dff46686e2218d525
I have also attached the changes I made to the dit/events.c file.
After rebuilding xorg-server with those patches, the Open Motif
(mwm) window manager now works with the above minimize keyboard
and mouse squence. Thanks for all the help.
Regards,
web...
--
William Bulley Email: w...@umich.edu
72 characters width template -|
for (; grab; grab = grab-next)
{
DeviceIntPtrgdev;
XkbSrvInfoPtr xkbi = NULL;
/* 3471 Maskmask = 0; */
gdev= grab-modifierDevice;
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
}
xE = core;
count = 1;
/* 3586 mask = grab-eventMask; */
} else if (match XI2_MATCH)
{
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
count = 1;
/* 3599 * FIXME: EventToXI2 returns NULL for enter events, so
* dereferencing the event is bad. Internal event types are
* aligned with core events, so the else clause is valid.
* long-term we should use internal events for enter/focus
* as well *
if (xE)
mask =
grab-xi2mask[device-id][((xGenericEvent*)xE)-evtype/8];
else if (event-type == XI_Enter || event-type == XI_FocusIn)
mask = grab-xi2mask[device-id][event-type/8]; */
} else
{
rc = EventToXI((InternalEvent*)event, xE, count
Re: serious (for me) Xorg 7.5 mouse/kbd problem in 8.1-STABLE
According to Polytropon free...@edvax.de on Wed, 08/25/10 at 10:03: In case you're using HAL + DBUS, the setting now has to be coded in XML in some arbitrary file at a decentral location buried deep in the /usr/local subtree. According to the handbook 5.4.2 Configuring X11 http://www.freebsd.org/doc/handbook/x-config.html this is /usr/local/etc/hal/fdi/policy/x11-input.fdi with ?xml version=1.0 encoding=ISO-8859-1? deviceinfo version=0.2 device match key=info.capabilities contains=input.keyboard merge key=input.x11_options.XkbOptions type=stringterminate:ctrl_alt_bksp/merge /match /device /deviceinfo as well as /etc/X11/xorg.conf will need to be added Section ServerFlags Option DontZap off EndSection And the handbook also suggests a reboot (?!) to make sure HAL will pick up the new setting. Next time, you will have to reboot in order to make a mouse pointer position change visible. :-) Thanks for all the suggestions. Here is where things stand: I am still having the same problem since upgrading to 8.1-STABLE. First, what has changed. Then a clarification of the problem. xterm has changed: now 2.6.1 was 2.5.3 xorg has changed: now 7.5 was 7.3 xorg-server has changed: now 1.7.5,1 was 1.6.1,1 xf86-input-keyboard: now 1.4.0 was 1.3.2_2 xf86-input-mouse: now 1.5.0 was 1.4.0_6 hal has changed: now 0.5.14_8 was 0.5.13_12 kernel has changed: now 8.1-STABLE was 8.0-STABLE Note that open-motif _has_ _not_ _changed_ for some time. The problem is not in the method of shutting down my Xorg session. The problem is not the disappearance of my arrow cursor/pointer per se, although that may be a symptom of the underlying problem. The problem is that I am unable (now) to use open-motif through no change in my configs or my settings. Something has changed in the underlying applications, or system libraries, or kernel. In my use of open-motif, I use and depend on mouse focus. This means that when I move my mouse, the xterm I was in looses focus and the xterm into which I move my mouse pointer gains focus. This feature is also present in TWM, but open-motif (MWM) gives me the additional feature that the window having focus is also raised to the top - above all other windows/applications. This feature is critical for me and why I prefer using open-motif. When I first experienced this bug, all I could do at that point was to exit my xorg session (various folks have helped make that more normal). I have modified my .xinitrc file to include: /usr/local/bin/setxkbmap -option terminate:ctrl_alt_bksp and now Ctrl/Alt/BS sequence works as it used to in the old days. I have commented out ServerFlags section of my /etc/X11/xorg.conf file and I have rebooted my workstation. Both hald and dbus are still enabled in my /etc/rc.conf file. Nothing has changed. When I run open-motif, I still experience the crippling loss of mouse focus when I enter the sequence Shift/Btn3Click. The prevents me from using _any_ of my other windows or xterms or applications since I can no longer select them (give them focus). Recall this setting in my ~/.mwmrc file: Shift Btn3Click window f.minimize OTOH _everything_ works in /usr/local/bin/twm. I much prefer the features of MWM compared to TWM. I don't want to relearn another window manager just because of this problem, and I'd rather not reassign my f.minimize feature to a difference key and mouse sequence, since some day, some application may require me to enter Shift/Btn3Click which would effectively ruin that Xorg session. Since TWM works and the xterms therein also work just fine, I doubt that xterm is at fault. I also hold open-motif blameless since it has not changed in years. I think something in Xorg or one of its support modules is not properly registering the Shift/Btn3Click event to the xorg-server, or that xorg-server has changed so that this particular event causes my pointer focus to disappear. Unfortunately, I don't know how to track down this bug or to narrow the search for what changed. I was hoping someone in FreeBSD-land would have some suggestions. I have heard that contacting the Xorg developers may not result in a timely resolution. I greatly appreciate the comments on -questions to date. Thanks guys. Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: serious (for me) Xorg 7.5 mouse/kbd problem in 8.1-STABLE
According to Warren Block wbl...@wonkity.com on Wed, 08/25/10 at 11:03: You are telling xorg-server to not use hald with the AutoAddDevices line: Section ServerFlags Option AutoAddDevices off Option DontZap false EndSection And the other option is already a default. So removing or commenting that section would let xorg-server use hald. I don't know if this will affect your window manager. Probably not, but worth testing. Did that. Made that change. No joy... :-( Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
serious (for me) Xorg 7.5 mouse/kbd problem in 8.1-STABLE
For years I have run Open-Motif on FreeBSD without issue. I use a USB keyboard and a USB three button mouse attached to a Dell Optiplex 960. This combination has worked fine for the past year. This week I upgraded from 8.0-STABLE circa January 2010 to 8.1-STABLE. I do this by doing a buildworld/installworld sequence after csup-ing stable-supfile and rebooting. In this case I also pkg_deleted all of my ports and am rebuilding them from source. Building Xorg is one of the very first ports I attempt since I prefer to work in xterms not virtual terminals. This upgrade moved me from Xorg 7.3 to Xorg 7.5, but Open-Motif stayed the same - open-motif-2.2.3_6 - it hasn't changed in years. After building Xorg, as root, I ran the Xorg -configure command to generate my xorg.conf.new file. Since a working /etc/X11/xorg.conf file was still around after the upgrade from 8.0-STABLE/Xorg 7.3, I felt no need to change anything in that file (later file comparisons confirmed that nothing had changed). My only relevant additions to /etc/X11/xorg.conf are these: Section ServerFlags Option AutoAddDevices off Option DontZap false EndSection In my /etc/rc.conf file I have dbus and hald enabled, and that has not changed since the beginning of 2010 after the confusion abated. As a normal user, I start Xorg using /usr/local/bin/xinit as always. I have several xterms configured in my ~/.xinitrc file. All those came up in the correct location and state. I was able to open those that started in iconic mode. In an open/raised xterm I could enter carriage returns and see my shell prompt move down the window. But when I tried to close/minimize an open/raised xterm, things failed. I use the following keyboard/mouse combination (configured in my .mwmrc file) to close (minimize) an xterm (and other applications): Shift Btn3Click window f.minimize This is also unchanged for some years. This particular setting has no bearing on the problem I came across yesterday. I merely state it for the record. However, this configuration triggers the bug. The problem is as soon as I use that Shift/Btn3Click combination, my arrow cursor disappears, then I cannot move to or select other xterms - I am frozen, or locked, into the xterm I was trying to close/minimize. All I can do at this point is to kill(1) the /usr/local/bin/xinit command to return to the virtual terminal where I launched my Xorg session. I am now reluctantly using the good old /usr/local/bin/twm which is always built when Xorg is built from source. I am at a loss as to what to look for next. I suspect Xorg, or the keyboard and mouse driver, not the video driver, that came with. It might be a problem with hald(8), but again, I don't know how to debug this. Any help with this very odd bug would be greatly appreciated. Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: serious (for me) Xorg 7.5 mouse/kbd problem in 8.1-STABLE
According to jhell jh...@dataix.net on Wed, 08/25/10 at 09:24: On 08/25/2010 07:38, William Bulley wrote: For years I have run Open-Motif on FreeBSD without issue. I use a USB keyboard and a USB three button mouse attached to a Dell Optiplex 960. This combination has worked fine for the past year. This week I upgraded from 8.0-STABLE circa January 2010 to 8.1-STABLE. I do this by doing a buildworld/installworld sequence after csup-ing stable-supfile and rebooting. In this case I also pkg_deleted all of my ports and am rebuilding them from source. Building Xorg is one of the very first ports I attempt since I prefer to work in xterms not virtual terminals. This upgrade moved me from Xorg 7.3 to Xorg 7.5, but Open-Motif stayed the same - open-motif-2.2.3_6 - it hasn't changed in years. After building Xorg, as root, I ran the Xorg -configure command to generate my xorg.conf.new file. Since a working /etc/X11/xorg.conf file was still around after the upgrade from 8.0-STABLE/Xorg 7.3, I felt no need to change anything in that file (later file comparisons confirmed that nothing had changed). My only relevant additions to /etc/X11/xorg.conf are these: Section ServerFlags Option AutoAddDevices off Option DontZap false EndSection In my /etc/rc.conf file I have dbus and hald enabled, and that has not changed since the beginning of 2010 after the confusion abated. As a normal user, I start Xorg using /usr/local/bin/xinit as always. I have several xterms configured in my ~/.xinitrc file. All those came up in the correct location and state. I was able to open those that started in iconic mode. In an open/raised xterm I could enter carriage returns and see my shell prompt move down the window. But when I tried to close/minimize an open/raised xterm, things failed. I use the following keyboard/mouse combination (configured in my .mwmrc file) to close (minimize) an xterm (and other applications): Shift Btn3Click window f.minimize This is also unchanged for some years. This particular setting has no bearing on the problem I came across yesterday. I merely state it for the record. However, this configuration triggers the bug. The problem is as soon as I use that Shift/Btn3Click combination, my arrow cursor disappears, then I cannot move to or select other xterms - I am frozen, or locked, into the xterm I was trying to close/minimize. All I can do at this point is to kill(1) the /usr/local/bin/xinit command to return to the virtual terminal where I launched my Xorg session. I am now reluctantly using the good old /usr/local/bin/twm which is always built when Xorg is built from source. I am at a loss as to what to look for next. I suspect Xorg, or the keyboard and mouse driver, not the video driver, that came with. It might be a problem with hald(8), but again, I don't know how to debug this. Any help with this very odd bug would be greatly appreciated. Though I can't really help you with the mouse disapearing I can say if you wish to modify you key-map to allow ctrl+alt+bksp you can add this to your .xinitrc ( setxkbmap -option terminate:ctrl_alt_bksp ) Thanks. Interestingly enough, I do have this line in my /etc/X11/xorg.conf file: Section InputDevice Option XkbOptions terminate:ctrl_alt_bksp EndSection But that never has seemed to work. :-( I will try your suggestion. I hope it works, although killing the xinit process is not much more difficult. Of course, your suggestion (and my workaround) to return to the virtual terminal command line depends upon a working keyboard... :-) Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: serious (for me) Xorg 7.5 mouse/kbd problem in 8.1-STABLE
According to Warren Block wbl...@wonkity.com on Wed, 08/25/10 at 09:49: If you are running hald, why not use it? And the DontZap default is back to where it used to be (off), so you could remove or comment that entire ServerFlags section. Not sure what you mean by using hald. Assuming I knew how to use hald, how would that solve my problem of the disappearing mouse pointer and consequent loss of functionality of my window manager? Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
CUPS between systems
When the CUPS server (cupsd) is built with GSSAPI support, the CUPS Administration tab (localhost:631/admin) contains this checkbox under the Server Settings: section: (x) Use Kerberos authentication (FAQ) Unfortunately for me on FreeBSD 8.0-STABLE running cups-base-1.4.2_3 the GSSAPI option is not present in the Makefile: CONFIGURE_ARGS+= --disable-gssapi ... As a result my localhost:631/admin screen lacks this Kerberos checkbox. This condition is still present in CUPS 1.4.3 according to the Makefile at http://www.freebsd.org/cgi/cvsweb.cgi/ports/print/cups-base/ I need Kerberos support in order to use CUPS to print to a network printer here. As a workaround, I was able to use a co-workers MacOS X system which was running CUPS to print to the same printer. This Mac was upgraded to MacOS 10.6.4 today, and this workaround failed. :-( So I am back to trying to use CUPS on FreeBSD to talk directly to the network printer, but without the Kerberos feature, I am locked out. Upgrading to CUPS 1.4.3 is unlikely to give me Kerberos support. It seems FreeBSD has Kerberos support in base at /usr/src/kerberos5. But I don't see how to bridge this gap. FWIW, using CUPS 1.3.10 in the Fall of 2009, I did have Kerberos support (via GSSAPI) and I was able to talk directly to the network printer. Does anyone have any suggestions for me to consider trying? Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
CUPS in ports (e.g., v1.4.3) --disable-gssapi WHY??
I recall building CUPS from ports last Fall (9/2009) at version 1.3.10 or 1.3.11 which had GSSAPI (Kerberos 5) support as an option. Today, the cups-base-1.4.3 port specifically excludes GSSAPI support (--disable-gssapi in the Makefile) which means CUPS cannot perform Kerberos authentication (to get a ticket granting ticket for printing). Why is this the case? Can someone elaborate on this, or point me to the correct forum to get an answer? Thanks in advance. Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Suitable laptop for FreeBSD?
According to Warren Block wbl...@wonkity.com on Wed, 03/03/10 at 10:30: Umm... that's incorrect. Maybe you mean ATI doesn't supply closed drivers for FreeBSD (although they do have Linux drivers, I think). xorg's open xf86-video-ati driver supports ATI video cards, including the Radeon Mobility cards in two notebooks I've tested. Well , i'm on ThinkPad R400 , ATI Mobile HD 3400 and an integrated Video Card FBSD doesn't boot when i switched to ATI Video card. Are you saying the R400 has both integrated and discrete video cards? Lenovo's web site doesn't seem very oriented to telling potential customers details about their newer computers. I think yes. At least in my case. I have a T500 and it came with both integrated Intel video plus an additional ATI mini-card. I don't recall if there was an Nvidia video choice. Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: vi question
According to gahn ipfr...@yahoo.com on Fri, 02/19/10 at 16:11: How could I use vi to repeat a word, say, 100 times in the same line, of course with a space in between? Edit your file: (vi xyz) On an empty line, enter: ispacewordspace(esc) Back up (left arrow) to the front of this line (column zero) Enter this sequence: 2dw (the line will disappear) Enter this sequence: 100P (voila!) Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cannot build GIMP 2.6.8-1 on 8.0-STABLE
According to Warren Block wbl...@wonkity.com on Mon, 02/15/10 at 16:39: webkit-gtk2 wants gnome-config to build gstreamer to support video. You can disable the VIDEO option in the webkit-gtk2 config settings, or just disable HELPBROWSER in the graphics/gimp-app port. Last I looked, the help was very outdated anyway. Don't know why the webkit-gtk2 build dies, though. Thanks. That suggestion allowed me to build the GIMP successfully. Although I still don't know why the GIMP depends on gnome-keyring... :-( Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
cannot build GIMP 2.6.8-1 on 8.0-STABLE
I am trying to build the GIMP on 8.0-STABLE but had a problem. For what it's worth, I have these ports installed: gtk-1.2.10_21 gtk-2.18.6_1 It is not clear to me why GIMP (or webkit-gtk2) depends on having Gnome2 (gnome-config) installed (I use open-motif): checking for GSTREAMER... gnome-config: not found gnome-config: not found gnome-config: not found configure: error: Package requirements (gstreamer-0.10 = 0.10 gstreamer-base-0.10 gstreamer-pbutils-0.10 gstreamer-plugins-base-0.10 gstreamer-video-0.10) were not met: No package 'gstreamer-pbutils-0.10' found No package 'gstreamer-plugins-base-0.10' found No package 'gstreamer-video-0.10' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables GSTREAMER_CFLAGS and GSTREAMER_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. === Script configure failed unexpectedly. Please run the gnomelogalyzer, available from http://www.freebsd.org/gnome/gnomelogalyzer.sh;, which will diagnose the problem and suggest a solution. If - and only if - the gnomelogalyzer cannot solve the problem, report the build failure to the FreeBSD GNOME team at gn...@freebsd.org, and attach (a) /usr/ports/www/webkit-gtk2/work/webkit-1.1.15.4/config.log, (b) the output of the failed make command, and (c) the gnomelogalyzer output. Also, it might be a good idea to provide an overview of all packages installed on your system (i.e. an `ls /var/db/pkg`). Put your attachment up on any website, copy-and-paste into http://freebsd-gnome.pastebin.com, or use send-pr(1) with the attachment. Try to avoid sending any attachments to the mailing list (gn...@freebsd.org), because attachments sent to FreeBSD mailing lists are usually discarded by the mailing list software. *** Error code 1 Stop in /usr/ports/www/webkit-gtk2. *** Error code 1 Stop in /usr/ports/www/webkit-gtk2. *** Error code 1 Stop in /usr/ports/graphics/gimp-app. *** Error code 1 Stop in /usr/ports/graphics/gimp-app. *** Error code 1 Stop in /usr/ports/graphics/gimp. *** Error code 1 Stop in /usr/ports/graphics/gimp. Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
confounding finding in print/cups-base (CUPS 1.4.2)
Since I need the GSSAPI (for Kerberos) feature of CUPS in FreeBSD
8.0-STABLE, I was somewhat taken aback when I found the cupsd server
failed to read its configuration file cupsd.conf when the line:
DefaultAuthType Negotiate
was present in that file upon server start/restart. The Negotiate
keyword is the way to indicate Kerberos support in CUPS according to
the CUPS documentation.
Attempting to start the CUPS server cupsd(8) from the command line
as root resulted in this error:
freebsd# /usr/local/etc/rc.d/cupsd start
Starting cupsd.
Message from sysl...@itcom245 at Feb 4 10:35:31 ...
itcom245 cupsd: Unable to read configuration file
'/usr/local/etc/cups/cupsd.conf' - exiting!
cupsd: Child exited with status 1!
/usr/local/etc/rc.d/cupsd: WARNING: failed to start cupsd
freebsd# /usr/local/etc/rc.d/cupsd stop
cupsd not running?
and in the /var/log/cups/error.log file I found this line:
Unknown default authorization type Negotiate on line 6.
Once line six (6) was removed, the cupsd server was able to start
without error (of course, Kerberos support was unavailable...) :-(
The file print/cups-base/work/cups-1.4.2/scheduler/conf.c has this
section:
#ifdef HAVE_GSSAPI
else if (!strcasecmp(value, negotiate))
{
loc-type = CUPSD_AUTH_NEGOTIATE;
if (loc-level == CUPSD_AUTH_ANON)
loc-level = CUPSD_AUTH_USER;
}
#endif /* HAVE_GSSAPI */
which would normally be controlled by running ./configure at build
time and affecting lines such as these in work/cups-1.4.2/config.h:
/*
* Do we have the GSSAPI support library (for Kerberos support)?
*/
/* #undef HAVE_GSSAPI */
/* #undef HAVE_GSSAPI_H */
/* #undef HAVE_GSSAPI_GSSAPI_H */
/* #undef HAVE_GSSAPI_GSSAPI_GENERIC_H */
/* #undef HAVE_GSSAPI_GSSAPI_KRB5_H */
/* #undef HAVE_GSSKRB5_REGISTER_ACCEPTOR_IDENTITY */
/* #undef HAVE_GSS_C_NT_HOSTBASED_SERVICE */
/* #undef HAVE_KRB5_CC_NEW_UNIQUE */
/* #undef HAVE_KRB5_IPC_CLIENT_SET_TARGET_UID */
/* #undef HAVE_KRB5_H */
/* #undef HAVE_HEIMDAL */
Interestingly the Makefile in print/cups-base has this line inside
the CONFIGURE_ARGS section which makes all the above irrelevant:
--disable-gssapi
So, my question is: why is the GSSAPI feature disabled in CUPS
1.4.2 when it was a configurable OPTION in CUPS 1.3.9 last Fall?
What should I do if I desire Kerberos support in CUPS 1.4.2 ??
Regards,
web...
--
William Bulley Email: w...@umich.edu
72 characters width template -|
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: dbus/hal in freebsd 7.2 hangs X11
According to Giuseppe Pagnoni gpagn...@gmail.com on Fri, 09/25/09 at 03:32: I am trying to use hal/dbus on a i386 machine with FreeBSD 7.2 (ports updated to the latest tree snapshot as of yesterday), but despite spending a full day looking up the handbook, faq, and google, I cannot make it work properly. More specifically, when I use either xfce4 or xmonad after having enabled dbus/hald in rc.conf: hald_enable=YES dbus_enable=YES both window managers become very unresponsive and hang as if hal was trying to access/mount something. For example, the terminal may take *seconds* to display typed in characters and in xfce if you click on the desktop icons for home directory etc., they don't open up at all in the thunar file manager (they do though, if you right click on them and choose 'open'). I, too, have seen this same problem, but with OpenMotif (mwm) as my window manager. I have solved the problem by changing the lines: dbus_enable=YES hald_enable=YES to dbus_enable=NO hald_enable=NO in my /etc/rc.conf file. This makes things in xorg-7.4_2 and open-motif-2.2.3_6 and 7.2-STABLE FreeBSD 7.2-STABLE #0: Tue Sep 15 14:33:54 EDT 2009 work for me. Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Repeatable X lockups
According to Jimmie James jimmie...@gmail.com on Sat, 05/02/09 at 15:46: When using the xv output driver for vlc or mplayer, X will lockup, crash instantly, trashing the screen and forcing a reboot Image of screen corruption: http://img.photobucket.com/albums/v287/jimmiejaz/xcrash.jpg This just started manifesting in the past week or so. I have experienced the same problem, but I didn't see any suggestions or answers to your posting. Have you had any success yet with this? Have you tried any other output drivers? This is something I plan to try in the next few days. My system is i386 with Intel 915 graphics on the motherboard. Xorg 7.4 runs fine. When I run mplayer from the command line, in an xterm under open-motif, the X Windows session dies and I am tossed back to the vty. When I similarly run vlc from the command line, the screen is locked in an even worse state than your above URL. I am forced to ssh(1) in from another FreeBSD workstation to reboot. Before the reboot, ps(1) reports no processes running xorg or any of its child processes, it seems as if my video hardware has been left in some ugly, locked-up, unusable state. What is interesting to me is that the same flash file that causes vlc and mplayer to crash runs just fine in ffplay(1) (part of ffmpeg port). Yet at least vlc uses ffmpeg, while it doesn't look like mplayer does. This is 7.2-PRERELEASE built on 24 Apr 2009 with the ports of mplayer and vlc built on 2 May 2009 following a csup(1) of complete ports tree on either 24 Apr or 25 Apr - so approximately the same timeframe as you. Regards, web... -- William Bulley Email: w...@umich.edu The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately, and delete this message. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
fatal error from /usr/ports/Mk/bsd.linux-apps.mk
On Friday I ran the following:
# cd /usr/local/etc/cvsup
# csup -L2 ports-supfile
# csup -L2 doc-supfile
# csup -L2 stable-supfile (tag=RELENG_7)
I then rebuilt the world and installed it. When I rebooted,
I was very pleasantly surprised to find:
% uname -a
FreeBSD freebsd 7.2-PRERELEASE FreeBSD 7.2-PRERELEASE #0:
Fri Apr 24 16:13:56 EDT 2009 [snip] i386
I began the process of rebuilding my all ports on Saturday:
# pkg_delete -a
# \rm -rf /usr/ports/*/work
Things progressed fine until I started building any ports
having some dependency on Linux emulation:
[this is true for /usr/ports/print/acroread8 and 9
astro/google-earth, multimedia/linux-realplayer,
www/opera-linuxplugins, etc.]
# make install clean
/usr/ports/Mk/bsd.linux-apps.mk, line 72: Malformed conditional
(${LINUX_DIST_SUFFIX}==)
/usr/ports/Mk/bsd.linux-apps.mk, line 130: Malformed conditional
(${LINUX_DIST_SUFFIX} == -f8)
Error expanding embedded variable.
Here are the relevant settings in the indicated files:
/etc/fstab
linprocfs /compat/linux/proc linprocfs rw 0 0
# kldstat
Id Refs AddressSize Name
1 12 0xc040 48d204 kernel
21 0xc088e000 6a45cacpi.ko
31 0xc5403000 7000 linprocfs.ko
41 0xc540f000 22000linux.ko
/etc/rc.conf
linux_enable=YES
/etc/make.conf
OVERRIDE_LINUX_BASE_PORT=f9
OVERRIDE_LINUX_NONBASE_PORTS=f9
/etc/sysctl.conf
compat.linux.osrelease=2.6.16
I don't know what to do to fix this problem. I don't
know whether I should submit a pr or try to determine
what is going on myself. Not sure I would succeed at
the latter. Please advise. If more information or
detail is required, let me know.
The next thing I will try is changing /etc/make.conf
to override f8 instead of f9
Regards,
web...
--
William Bulley Email: w...@umich.edu
The information contained in this message may be CONFIDENTIAL
and is for the intended addressee only. Any unauthorized use,
dissemination of the information, or copying of this message
is prohibited. If you are not the intended addressee, please
notify the sender immediately, and delete this message.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: short-changed on SD card?
According to Brad Mettee bmet...@pchotshots.com on Mon, 02/02/09 at 15:55: Does an XP machine also detect it as 960MB? If not, can you put more than 960M on it and verify that it's all intact? Yes, Windows XP sees it as a 960MB FAT16 drive. And when formatting it under Windows XP it never gave me the option to up this number, so somewhere (boot block, MBR?) the concept of 960MB is retained. Create a 100MB zip file, put 10+ copies on the card. Then test to see if the CRC is correct on all of the copies. If they're alls ok, then the card is in fact 2GB. If you start getting errors on any of the files (and can wipe/repeat the problem), then I'd say you've been ripped off and it's only a 1GB card. Did you intend to have me put this ZIP file on the SD card using Windows XP or FreeBSD, or does it matter? I wish I didn't have to touch Windows XP at all, grrr... :-( Regards, web... -- William Bulley Email: w...@umich.edu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: short-changed on SD card?
According to Warren Block wbl...@wonkity.com on Mon, 02/02/09 at 15:29: newfs_msdos(8) Learned something new there. Thanks! It's generally not useful to slice/partition a small SD card. Without a slice table, the whole device is just one slice. Agreed. I just want a big chuck of storage (in this case the 2.0 GB that I paid for, sigh...) and I don't care what format it is in. As I said, I am happy with FAT16 as long as I can use all (approximately) 2.0 GB of it. Offhand I don't know if you can overwrite an existing slice table (boot block) with just a 'newfs_msdos /dev/da1'. Probably. This is something I will try. If not, you can just 'dd if=/dev/zero of=/dev/da1 bs=512 cnt=1' and then do the newfs_msdos. Okay. This is worth a try. If you plan to use that card in a camera, you are a little safer doing a full or low-level format with the card in the camera. Some cameras create and like not-quite-right filesystems. Older Canon cameras, for instance. This is not for use in a camera. It is just a quick and dirty way for me to grab (about) 2.0 GB from one FreeBSD system and plop it onto another. Finally, there are more than a few reports of SD cards with false capacities bought on ebay. This SD card was purchased from a reputable firm in New York whose name you would recognize were I to mention it. I have had nothing but good experiences buying from them in the past (many years four). Regards, web... -- William Bulley Email: w...@umich.edu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: short-changed on SD card?
According to Tim Judd taj...@gmail.com on Mon, 02/02/09 at 18:13: Nobody's blamed the SD/CF reader. I call dibs to blame the SD/CF reader. Isolate the problem to find the culprit... Check the USB reader -- I'm curious to see if that fixes the problem. This is a FANTASTIC suggestion - never occurred to me. I will have to try a different device with the same 2.0 GB card. Thanks! And FYI -- No matter the Heads/Sectors/Cylinders, there are ~200 512byte sectors, roughly equal to 1GB. Yep. If it's not the adapter, you got cheated in the purchase. Thanks again. Regards, web... -- William Bulley Email: w...@umich.edu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: short-changed on SD card?
According to Mike Jeays mike.je...@rogers.com on Mon, 02/02/09 at 19:38: I think I would try dd if=/dev/zero of=/dev/da1 bs=1M without the count option, and see how many blocks it writes. You at least start with a clean slate, and can run fdisk and newfs, if you want a BSD-only device. Make sure you write on the right device! So you don't think the bad card reader suggestion is relevant? I will also try this approach. Thanks for all the feedback. Now, I've got some avenues of testing to work through. Later... Regards, web... -- William Bulley Email: w...@umich.edu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
short-changed on SD card?
Recently purchased a brand new 2.0 GB secure digital (SD) card. When I plugged this into a USB dongle and plugged the USB dongle into an available USB socket on my FreeBSD 7.0-STABLE system the output from dmesg(8) reported this: da1: 960MB (1967616 512 byte sectors: 64H 32S/T 960C) This is much closer to 1.0 GB than 2.0 GB so I at once wondered if I had been scammed in my purchase of this brand new SD card. Once I'd mounted /dev/da1s1 on /mnt, the df(1) command also reported 960 MB. I then copied a 300+ megabyte file onto /mnt and then ran the df(1) command again. This time it reported 1.9 GB total and 1.6 GB available. WHAT IS GOING ON HERE? Am I going crazy? Is this normal behaviour for a FAT16 formatted (raw/blank) SD card? Is there something I can do using the fdisk(8) or similar command to change the SD card so that it believes (and FreeBSD believes) that it is truly a 2.0 GB card? As I continued writing (large, multi-hundred megabyte) files to the mounted SD card, the system eventually seized up and I had to reboot. I expect this had something to do with my having crossed the 960 MB boundary on this SD card. Help! Any ideas gratefully accepted. Regards, web... -- William Bulley Email: w...@umich.edu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: short-changed on SD card?
According to Jerry McAllister jerr...@msu.edu on Mon, 02/02/09 at 14:12: I am a little lost here and haven't tried a lot on USB devices yet - though I haven't had these kind of problems. But, after doing the fdisk stuff and before trying to mount, did you do a newfs? Another thing would be to try the old dd if=/dev/zero of=/dev/da1 bs=512 count=1024 and see if it will write to it and wipe enough stuff to free it up. Up the count if you think it makes any difference. Thanks. According to the newfs(8) man page it is used only for BSD style file systems (ufs and ufs2). I am okay with the FAT16 formatted SD card, I'm just upset that I paid for a 2.0 GB card and ended up with what seems to be a 1.0 GB card. I would be happy if I could make the SD card look like this: slice 1 2.0 GB (well, 1920 MB if you insist) slice 2 UNUSED slice 3 UNUSED slice 4 UNUSED And I thought I had done just that using fdisk(8). But I must have gotten some of the beg and end paramaters set up wrong. If the card is indeed 2.0 GB in size, and following in the style of the originally reported parameters of this card: da1: 960MB (1967616 512 byte sectors: 64H 32S/T 960C) that is, 64 heads, 32 sectors per track, and 960 cylinders, (this evidently from what the BIOS reports and understands) I had assumed that I could merely increase the cylinder count up to 1920 and leave the head and sector information as it was. But as I said earlier, this didn't seem to work. I know I have to leave room at the beginning for the MBR or the like, but the tools are either too low level, or too high level, or my understanding of all this is not up to speed. Why can't an SD card advertised (and sold) as a 2.0 GB card actually hold (approximately) 2.0 GB? That is what bugs me... I believe that FAT16 is capable of addressing a 2.0 GB disk drive, yes? Regards, web... -- William Bulley Email: w...@umich.edu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: short-changed on SD card?
According to Mel fbsd.questi...@rachie.is-a-geek.net on Mon, 02/02/09 at 12:46: On Monday 02 February 2009 07:52:44 William Bulley wrote: Recently purchased a brand new 2.0 GB secure digital (SD) card. When I plugged this into a USB dongle and plugged the USB dongle into an available USB socket on my FreeBSD 7.0-STABLE system the output from dmesg(8) reported this: da1: 960MB (1967616 512 byte sectors: 64H 32S/T 960C) This is much closer to 1.0 GB than 2.0 GB so I at once wondered if I had been scammed in my purchase of this brand new SD card. Once I'd mounted /dev/da1s1 on /mnt, the df(1) command also reported 960 MB. I then copied a 300+ megabyte file onto /mnt and then ran the df(1) command again. This time it reported 1.9 GB total and 1.6 GB available. WHAT IS GOING ON HERE? Am I going crazy? On a hunch, it's really 1G FAT, 1G HFS (mac). You could reformat it using fdisk/newfs. That might be a good hunch, but the SD card itself just says 2.0 GB on the outside - no mention there or when I purchased it to have any Mac-ness. I don't recall seeing anything Mac-ish when I ran the fdisk(8) command as % fdisk da1 The output then seemed to correctly reflect that partition (slice) one (1) was 960 MB in size. I tried later (once the system had recovered and the fsck(8) had finished) to use fdisk(8) to put 1920 MB into slice one. But that didn't seem to work. I marked all the other three slices as UNUSED. Is there any trick to using fdisk(8) that is hidden in the man page which I evidently missed? I used the -i flag and it led me by the had through each slice - I thought I did the right thing, but I was never able to mount(8) the SD card after that, even though dmesg(8) reported da1 as being there. I kept getting invalid parameter or the like when I tried mounting as I am used to: # mount_msdosfs -l /dev/da1s1 /mnt I also tried: # mount_msdosfs -l /dev/da1 /mnt But both versions failed. Finally, in desperation, I formatted the SD card on a Windows XP laptop. Windows put it back into FAT shape (using the low level - not the quick - format there) and gave it 960 MB, sigh... :-( Regards, web... -- William Bulley Email: w...@umich.edu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
help for a wounded disk drive...
I damaged a Seagate 80 GB EIDE drive that was attached to a FreeBSD 5.4 system (as ufs) some time ago, and I would like to recover the data on this drive - if that is possible. All positive suggestions are welcome. The drive is mechanically and electrically good. I just can't mount it and use it under FreeBSD. It was a dual boot drive with a DOS partition on the first partition and FreeBSD 5.4 on partition two. I did the normal sysinstall for FreeBSD 5.5 as I had done many times before. Unfortunately, I had the older, FreeBSD 5.4 drive cabled up (and powered up) on the second IDE channel (using cable select) of an i386 motherboard while I did the 5.5 install on a new, blank drive on the first IDE channel. I told sysinstall to add the standard FreeBSD bootloader on the new drive. I don't recall if I allowed for a DOS partition or just used the entire disk. The FreeBSD 5.4 disk on the second IDE channel also had the standard FreeBSD bootloader from my earlier sysinstall of 5.4 on that disk. When I completed the install, I figured I could just mount the second (older) drive manually. When I tried to do this, things went from bad to worse, and the new system could never recognize the drive. I believe the installation process attempted to (or succeeded in) putting (an unnecessary) bootloader on the older drive. Had it not been connected, it would probably be okay today. I learned an important lesson at that time... I don't know what steps to take to recover this drive so I can mount it in a read-only mode. I just want to recover the files on this drive. It is very small by today's standards, so I will likely not use the drive in production. I am comfortable running any required shell commands (as root), but I don't want to damage the disk drive any further. I hope I don't have to resort to using dd(1) on the raw device! Thanks in advance for any pointers. Regards, web... -- William Bulley Email: [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
where are base, info, kernels, dict, doc, games, manpages, ports, src, etc. for 7.0-REL?
I can't seem to find the distributions listed in the Subject: line on any of the 7.0-RELEASE ISO images. What am I missing? I know the 7.0-RELEASE announcement says the bootable ISO can be used along with FTP to finish the install, but I can't get FTP (or passive FTP, for that matter) to work as it has in the past. I am behind a m0n0wall firewall, but I believe I have used passive FTP in the past to get around that problem. I even opened up the firewall with a pass all rule, but it still didn't work. It looked like it could not resolve ftp.freebsd.org or ftp9.freebsd.org since it hung there trying to connect with... until it gave up. I tried several different (known good) DNS server IP addresses, but nothing worked. Then I went looking for the distributions in the ISO images. Not finding them there either has really had a negative impact on my install today, sigh... :-( Regards, web... -- William Bulley Email: [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: where are base, info, kernels, dict, doc, games, manpages, ports, src, etc. for 7.0-REL?
According to Sean Cavanaugh [EMAIL PROTECTED]: are you using 7.0-RELEASE--bootonly.iso or 7.0-RELEASE--Disc1.iso the later has the files on it and can be installed without any network connection at all. Thanks. I have 7.0-RELEASE-i386-disc1.iso and burned it onto a CD-ROM, but that didn't seem to work either. I will try it again... It is curious why the contents of the ISOs is not listed somewhere. The only way I could find to inspect them was: # mdconfig -a -t vnode -f whatever.iso -u 0 # mount -t cd9660 /dev/md0 /mnt which is from section 18.6.2 of the Handbook. Regards, web... -- William Bulley Email: [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: thankee, thankee!
According to Tim Daneliuk [EMAIL PROTECTED]: Before you go down this road too far, you should take a look at Python as an implementation language. If what you're doing involves text and string manipulation, Python is loaded with good modules that will make your task a snap. Having coded extensively in many assemblers, C, BASIC, ... I now find myself reaching exclusively for Python when writing applications and utilities unless the task at hand must have the performance of native C. Try it ... you'll be shocked how fast your program comes together. Might the same not be said for Perl? Regards, web... -- William Bulley Email: [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
WPA and EAP-TTLS oddity
length 8 rlm_eap: No EAP Start, assuming it's an on-going EAP conversation modcall[authorize]: module eap returns updated for request 5 users: Matched entry foo at line 217 modcall[authorize]: module files returns ok for request 5 rlm_pap: Found existing Auth-Type, not changing it. modcall[authorize]: module pap returns noop for request 5 modcall: leaving group authorize (returns updated) for request 5 rad_check_password: Found Auth-Type EAP auth: type EAP Processing the authenticate section of radiusd.conf modcall: entering group authenticate for request 5 rlm_eap: EAP Identity rlm_eap: No such EAP type md5 rlm_eap: Failed in EAP select modcall[authenticate]: module eap returns invalid for request 5 modcall: leaving group authenticate (returns invalid) for request 5 auth: Failed to validate the user. Trying to look up name of unknown client 127.0.0.1. Login incorrect: [foo/no User-Password attribute] (from client UNKNOWN-CLIENT port 261 cli 00-xx-xx-xx-xx-xx) TTLS: Got tunneled Access-Reject rlm_eap: Handler failed in EAP/ttls TTLS: Freeing handler for user foo rlm_eap: Failed in EAP select modcall[authenticate]: module eap returns invalid for request 5 modcall: leaving group authenticate (returns invalid) for request 5 auth: Failed to validate the user. =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*= This one has me stumped. :-( Regards, web... -- William Bulley Email: [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
boot manager oddity (two IDE drives, two o/s)
I have two IDE drives (ad0 and ad1) on a Dell system that is running Windows XP on ad0 and FreeBSD 6.2 on ad1. Drive ad0 is 80 GB. Drive ad1 is 250 GB. When I installed FreeBSD onto ad1, I installed the FreeBSD boot manager onto both ad0 and ad1 disk drives. When the machine powers up from a cold start, I don't see the ad0 boot manager at all. I see the ad1 boot manager. It looks like this. F1 FreeBSD F5 Drive 0 and FreeBSD boots just fine if I select F1. I don't see the ad0 boot manager until I reboot FreeBSD and select F5 from the above menu. Then I get this: F1 ??? F2 DOS F5 Drive 1 Hitting F5 gives me the expected: F1 FreeBSD F5 Drive 0 But, if I want to boot up Windows, I hit F2, and then Windows starts up. If I shut down Windows (restart), then I again see this: F1 ??? F2 DOS F5 Drive 1 But this time, when I hit F5 nothing happens!?!?!?! Here is the output of two boot0cfg(8) commands: freebsd% boot0cfg -v ad0 # flag start chs type end chs offset size 1 0x00 0: 1: 1 0xde 4:254:63 6380262 2 0x00 5: 0: 1 0x07 1023:254:6380325156151800 version=1.0 drive=0x80 mask=0xf ticks=182 options=nopacket,update,nosetdrv default_selection=F5 (Drive 1) freebsd% boot0cfg -v ad1 # flag start chs type end chs offset size 1 0x80 0: 1: 1 0xa5 1023:254:63 63524281212 version=1.0 drive=0x81 mask=0xf ticks=182 options=nopacket,update,nosetdrv default_selection=F1 (Slice 1) What I want to know is am I doing something wrong, or, am I not doing enough to configure (using the boot0cfg(8) command) the two boot managers (one on each drive)? BTW, the ??? slice above is the Windows recovery (or diagnostic?) slice, I believe. I have looked in the Handbook to no avail. Any ideas? Help! Regards, web... -- William Bulley Email: [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
odd HP 1320 printer behaviour...
I have an HP 1320 (only has USB and parallel support) hooked to a FreeBSD 6.2-STABLE box using a USB cable. I have configured /dev/ulpt0 into my /etc/printcap file. Everything works fine and I am happy with this setup except for one odd behaviour. The last page of a multi-page print job will linger - somewhere - while the green light on the HP continues to blink -- as if data were being sent to it. The lpq(1) command reports no entries when run, and then about a minute or two later, this last page gets printed. Is there some configuration that I am missing? Is this an artifact of the USB protocol? Is this the way the HP 1320 laser printer operates? Is this a feature (or bug) of the USB printer driver /dev/ulpt0 that is not documented? I've read the man pages and searched using Google to see if this is a known problem. Any suggestions will be gladly accepted. I can live with this behaviour, but it seems very odd. Regards, web... -- William Bulley Email: [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: odd HP 1320 printer behaviour...
According to Nikola Lecic [EMAIL PROTECTED]: Do you have any ulpt0 configuration in /etc/rc.local? If the printer port is interrupt-driven, try polled standard mode, i.e. add lptcontrol -p -d /dev/[printer-port] to your /etc/rc.local. The kind of behaviour you described can occur in the interrupt mode (including cutting pages, printing them in chunks, etc.). Also try to switch the printer to the parallel port; if both can serve the printer, I'd always use the parallel one. If this doesn't help, please post here the content of your /etc/printcap and 'dmesg | grep ulpt0'. I have no /etc/rc.local file on this machine. Correct me if I am wrong, but doesn't lptcontrol(8) deal with the parallel port printer? I have USB connected. Parallel port connection is unfeasible in my situation. content of your /etc/printcap: lp|default|hp|HP|ps|PS|Hewlett Packard LaserJet 1320 PostScript Printer:\ :sh:\ :lp=/dev/ulpt0:\ :sd=/var/spool/lpd/hp:\ :lf=/var/log/lpd-errs:\ :mx#0: 'dmesg | grep ulpt0': ulpt0: Hewlett-Packard hp LaserJet 1320 series, rev 1.10/1.00, addr 5, iclass 7/1 ulpt0: using bi-directional mode ulpt0: at uhub0 port 2 (addr 5) disconnected ulpt0: detached ulpt0: Hewlett-Packard hp LaserJet 1320 series, rev 1.10/1.00, addr 5, iclass 7/1 ulpt0: using bi-directional mode ulpt0: at uhub0 port 2 (addr 5) disconnected ulpt0: detached ulpt0: Hewlett-Packard hp LaserJet 1320 series, rev 1.10/1.00, addr 5, iclass 7/1 ulpt0: using bi-directional mode ulpt0: offline ulpt0: at uhub0 port 2 (addr 5) disconnected ulpt0: detached ulpt0: Hewlett-Packard hp LaserJet 1320 series, rev 1.10/1.00, addr 5, iclass 7/1 ulpt0: using bi-directional mode Regards, web... -- William Bulley Email: [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: odd HP 1320 printer behaviour...
According to Warren Block [EMAIL PROTECTED]: If the print job is plain text, does it end in a formfeed? If not, the printer may wait for one, and eventually timeout and print the page. I only send PostScript to this printer. My WWW browsers do this for me automatically and the FreeBSD port print/enscript-letter does the rest for me (plain text or ASCII files). Depending on what processing you do to the source file, you may find utilities like /usr/ports/print/enscript useful. I have been using enscript for about twenty years now... :-) Regards, web... -- William Bulley Email: [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
problems with libglade2...
I am trying to run a Linux binary under FreeBSD Linux compatibility mode (linux_base-fc-4_9) on 6.2-PRERELEASE. The error I get is: error while loading shared libraries: /usr/X11R6/lib/libglade-2.0.so.0: ELF file OS ABI invalid freebsd% pkg_info | grep -i glade libglade2-2.6.0 GNOME glade library freebsd% ldd foobah foobah: foobah: error while loading shared libraries: /usr/X11R6/lib/libglade-2.0.so.0: ELF file OS ABI invalid foobah: exit status 127 freebsd% file foobah foobah: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.2.0, dynamically linked (uses shared libs), stripped freebsd% file /usr/X11R6/lib/libglade-2.0.so.0 /usr/X11R6/lib/libglade-2.0.so.0: ELF 32-bit LSB shared object, Intel 80386, version 1 (FreeBSD), not stripped According to the foobah README: Executable is tested to work with: OS: Fedora Core 3, Suse 9.2 Platform: i386, Athlon, i686 What am I missing? What steps (short of tossing the whole idea out) should I take to successfully run the Linux binary foobah? Thanks. Regards, web... -- William Bulley Email: [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: In search of the ultimate .muttrc
According to Roman Neuhauser [EMAIL PROTECTED]: here's mine. i'm not sure it will be of any use for you, stuff like this is purely matter of taste and habit. parts were stripped for privacy reasons. How about dotfiles.com ?? Regards, web... -- William Bulley Email: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
