NFS locks rpcbind port = 0 failed? - try #2
This is a continuation of 9.1 VM nfs3 locks over VPN - trying a different angle maybe it'll jostle someones memory. I now have a FreeBSD 9.2 VM at an offsite hosting company. hostname nl101vpn OpenVPN is installed on it, routed not bridged mode. I have multiple OSs installed on local network. I'm already exportings NFS off 9.1 with working locks. export nfsv3 or nfsv4 from nl101vpn - locks do not work. export nfsv3 from any local system, mount on nl101vpn - locks work. export nfsv3 from locally installed VM, mount on any local host or nl101vpn - locks work. No OpenVPN installed on it though. I even ran a tcpdump to see if something was getting lost - both sides match, nothing is getting dropped nl101vpn - /var/log/messages: Oct 14 12:21:01 nl101 kernel: NLM: failed to contact remote rpcbind, stat = 0, port = 0 (why port 0?) Oct 14 12:23:02 nl101 last message repeated 109 times Oct 14 12:25:48 nl101 last message repeated 177 times So I haven't exhausted every combination, or completely 100% replicated whats happening offsite, but it's getting pretty ridiculous now... I'm lost, and I need locking. Help :) ___ 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: Shared object libaprutil-1.so.4 not found, required by libserf-1.so.0
Antonio Olivares olivares14031 at gmail.com writes: On Thu, Sep 12, 2013 at 12:36 AM, Matthew Seaman m.seaman at infracaninophile.co.uk wrote: On 11/09/2013 21:03, Antonio Olivares wrote: [Info 19:57:22] Updating 'freebsd_texlive' source ports tree with method 'svn'. Shared object libaprutil-1.so.4 not found, required by libserf-1.so.0 [Error 19:57:22] Subversion update failed. [Error 19:57:22] Failed to update the 'freebsd_texlive' ports tree. Yeah -- you need to update or install the package that provides libaprutil-1.so. If you're using pkg(8) against a package repository rather than compiling your own, you could use: pkg check -d subversion-1.8.3 For portmaster dependencies should be auto-updated when you run portmaster devel/subversion It might be useful to run portmaster --force-config -f devel/subversion so you can recheck all the options settings of dependencies, but this will rebuild portmaster and everything it depends on. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey JID: matthew at infracaninophile.co.uk Dear Dr. Matthew, Thank you very much for your excellent advice. Worked like a champ! Now if I can get iced-teaweb/openjdk to open *.jnlp files to use java, it appears that itweb-javaws is not working correctly. Firefox reports that the file *.jnlp downloaded, but it is not opened by java. Thank you very much sir for your help. Best Regards, Antonio ___ freebsd-questions at freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscribe at freebsd.org Hello, I've had the same problem, also using portshaker and freebsd-texlive ports. I think the solution was in /usr/ports/UPDATING : 20130706: AFFECTS: users of devel/apr1 AUTHOR: oha...@freebsd.org APR was updated to 1.4.8 and APR-util was updated to 1.5.2. Please rebuild all ports which are using functions from APR/APR-util such as apache, subversion ... # portmaster -r apr or # portupgrade -r devel/apr1 or # pkg install -fR devel/apr1 Best regards ___ 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: Shared object libaprutil-1.so.4 not found, required by libserf-1.so.0
On Thu, Sep 12, 2013 at 12:36 AM, Matthew Seaman m.sea...@infracaninophile.co.uk wrote: On 11/09/2013 21:03, Antonio Olivares wrote: [Info 19:57:22] Updating 'freebsd_texlive' source ports tree with method 'svn'. Shared object libaprutil-1.so.4 not found, required by libserf-1.so.0 [Error 19:57:22] Subversion update failed. [Error 19:57:22] Failed to update the 'freebsd_texlive' ports tree. Yeah -- you need to update or install the package that provides libaprutil-1.so. If you're using pkg(8) against a package repository rather than compiling your own, you could use: pkg check -d subversion-1.8.3 For portmaster dependencies should be auto-updated when you run portmaster devel/subversion It might be useful to run portmaster --force-config -f devel/subversion so you can recheck all the options settings of dependencies, but this will rebuild portmaster and everything it depends on. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey JID: matt...@infracaninophile.co.uk Dear Dr. Matthew, Thank you very much for your excellent advice. Worked like a champ! Now if I can get iced-teaweb/openjdk to open *.jnlp files to use java, it appears that itweb-javaws is not working correctly. Firefox reports that the file *.jnlp downloaded, but it is not opened by java. Thank you very much sir for your help. Best Regards, Antonio ___ 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
Shared object libaprutil-1.so.4 not found, required by libserf-1.so.0
Dear folks, I am having problems with subject line. I have to fix error by reinstalling subversion, but it keeps coming back with this error message. Shared object libaprutil-1.so.4 not found, required by libserf-1.so.0 === Returning to list of ports depending on subversion-1.8.3 === Updating done for ports that depend on subversion-1.8.3 === The following actions were performed: Re-installation of subversion-1.8.3 Re-installation of portshaker-1.0.8 Re-installation of portshaker-config-1.0.8 === Exiting I did a # portmaster -d -r subversion I configured subversion to use serf because I am used to freebsd_texlive_* I run to update and I get [Info 19:57:22] Updating 'freebsd_texlive' source ports tree with method 'svn'. Shared object libaprutil-1.so.4 not found, required by libserf-1.so.0 [Error 19:57:22] Subversion update failed. [Error 19:57:22] Failed to update the 'freebsd_texlive' ports tree. machine has not been updated since 05/27, I read entry: 20130619: AFFECTS: users of devel/subversion AUTHOR: oha...@freebsd.org devel/subversion has been upgraded from 1.7.10 to 1.8.0 If you want to upgrade, and use http/https access to repositories, please check, that the SERF option is enabled, as NEON support is gone. Also, mod_dontdothat and svnauthz_validate are now enabled with one option TOOLS, among other new tools and SVNMUCC is enabled always. subversion-1.7.x is available as devel/subversion17 To stay on subversion-1.7.x set in /etc/make.conf WITH_SUBVERSION_VER=17 and use the following command # pkg set -o devel/subversion:devel/subversion17 or # portmaster -o devel/subversion17 devel/subversion I configured subversion to use serf option and tried it. Thanks for advice/ideas suggestions. Best Regards, Antonio ___ 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: Shared object libaprutil-1.so.4 not found, required by libserf-1.so.0
On 11/09/2013 21:03, Antonio Olivares wrote: [Info 19:57:22] Updating 'freebsd_texlive' source ports tree with method 'svn'. Shared object libaprutil-1.so.4 not found, required by libserf-1.so.0 [Error 19:57:22] Subversion update failed. [Error 19:57:22] Failed to update the 'freebsd_texlive' ports tree. Yeah -- you need to update or install the package that provides libaprutil-1.so. If you're using pkg(8) against a package repository rather than compiling your own, you could use: pkg check -d subversion-1.8.3 For portmaster dependencies should be auto-updated when you run portmaster devel/subversion It might be useful to run portmaster --force-config -f devel/subversion so you can recheck all the options settings of dependencies, but this will rebuild portmaster and everything it depends on. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey JID: matt...@infracaninophile.co.uk signature.asc Description: OpenPGP digital signature
Re: virtualbox-ose fails to build on FreeBSD 9.2-BETA2 #0 r253698
How to svn to 9-stable, make world (etc)? How to delete all installed ports? And then rm -rf /usr/local/*? Nice hints! Felix 发自我的 iPad 在 2013-8-5，3:53，John free...@growveg.net 写道： On 02/08/2013 16:54, John wrote: Hello list, I'm trying to install virtualbox on a new machine running FreeBSD 9.2-BETA2 #0 r253698. The ports version is 324162. Is it a problem with the port or my machine? This was fixed by: commenting everything out of /etc/make.conf svn to 9-stable, make world (etc) reboot then deleting all installed ports then removing everything from /usr/local then rm -rf /usr/ports portsnap install svn then checkout ports install virtualbox-ose sorry for the noise -- John ___ 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 ___ 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: virtualbox-ose fails to build on FreeBSD 9.2-BETA2 #0 r253698
On 02/08/2013 16:54, John wrote: Hello list, I'm trying to install virtualbox on a new machine running FreeBSD 9.2-BETA2 #0 r253698. The ports version is 324162. Is it a problem with the port or my machine? This was fixed by: commenting everything out of /etc/make.conf svn to 9-stable, make world (etc) reboot then deleting all installed ports then removing everything from /usr/local then rm -rf /usr/ports portsnap install svn then checkout ports install virtualbox-ose sorry for the noise -- John ___ 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
virtualbox-ose fails to build on FreeBSD 9.2-BETA2 #0 r253698
Hello list, I'm trying to install virtualbox on a new machine running FreeBSD 9.2-BETA2 #0 r253698. The ports version is 324162. Is it a problem with the port or my machine? Here is my make.conf: # cat /etc/make.conf CC=clang CXX=clang++ CPP=clang-cpp # added by use.perl 2013-07-30 20:08:48 PERL_VERSION=5.14.4 # no x11 WITHOUT_X11=yes I have no x11 because this is a server. Here is the error: In file included from /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/VBox/log.h:36, from /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/src/VBox/GuestHost/HGSMI/HGSMICommon.cpp:24: /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:251: error: 'size_t' does not name a type /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:253: error: expected initializer before '*' token /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1196: error: 'va_list' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1216: error: 'va_list' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1468: error: 'size_t' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1507: error: 'size_t' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1507: error: 'va_list' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1522: error: 'size_t' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1533: error: 'size_t' does not name a type /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1559: error: 'size_t' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1601: error: 'PFNRTLOGPREFIX' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1638: error: 'size_t' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1699: error: 'size_t' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1719: error: 'size_t' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1748: error: 'va_list' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1781: error: 'va_list' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1801: error: 'va_list' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1830: error: 'size_t' does not name a type /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1838: error: 'size_t' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1847: error: 'size_t' does not name a type /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1856: error: 'size_t' does not name a type /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1928: error: 'size_t' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1937: error: 'size_t' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1946: error: 'size_t' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1955: error: 'size_t' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1966: error: 'size_t' does not name a type /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1975: error: 'size_t' does not name a type /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/src/VBox/GuestHost/HGSMI/HGSMICommon.cpp:67: error: 'size_t' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/src/VBox/GuestHost/HGSMI/HGSMICommon.cpp: In function 'void* HGSMIHeapAlloc(HGSMIHEAP*, HGSMISIZE, uint8_t, uint16_t)': /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/src/VBox/GuestHost/HGSMI/HGSMICommon.cpp:303: error: 'size_t' was not declared in this scope /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/src/VBox/GuestHost/HGSMI/HGSMICommon.cpp:303: error: expected `;' before 'cbAlloc' /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/src/VBox/GuestHost/HGSMI/HGSMICommon.cpp:305: error: 'cbAlloc' was not declared in this scope kmk: *** [/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/out/freebsd.amd64/release/obj/HGSMIGuestR0Lib/HGSMICommon.o] Error 1 The failing command: @g++ -c
bwn0: RX decryption attempted (old 0 keyidx 0x2)
I have this wireless chip: siba_bwn0@pci0:48:0:0: class=0x028000 card=0x1371103c chip=0x431214e4 rev=0x02 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM4311 802.11a/b/g' class = network I use bwn(4) for it: siba_bwn0: Broadcom BCM4312 802.11a/b/g Wireless mem 0xc810-0xc8103fff irq 18 at device 0.0 on pci48 siba_bwn0: unsupported coreid (USB 1.1 Host) bwn0 on siba_bwn0 bwn0: WLAN (chipid 0x4311 rev 13) PHY (analog 4 type 2 rev 9) RADIO (manuf 0x17f ver 0x2050 rev 2) bwn0: DMA (64 bits) bwn0: Using 1 MSI messages bwn0: firmware version (rev 410 patch 2160 date 0x751a time 0x7c0a) I then use wpa_supplicant(8) to connect to the net. All this seems to work, often I see on the console: bwn0: RX decryption attempted (old 0 keyidx 0x2) repeated tens or maybe hundreds of times. What does this tell me? Could this be a symptom of other problems? Thanks Anton ___ 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
alq module kldload and unload and after that init 0 causes panic!
Dear Guys; When we kldload alq module, after that kldunload alq and after that init 0, system crashes! we are using FreeBSD 9. Could anybody help in this regard? thanks in advance ___ 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
AoE vblade reporting size 0
Hello, I'm trying to export a disk on FreeBSD 9.0-R4 over AoE (ATA over Ethernet) using vblade from ports. I run this as root: # vblade 1 1 em0 /dev/ada1 and the system returns this: ioctl returned -1 0 bytes pid 2629: e1.1, 0 sectors O_RDWR The drive nicely shows up on OSX and Linux as e1.1 but is has size 0 bytes and thus unusable. Has anyone successfully export a disk using AoE on FreeBSD that can shed some light on what I might be doing wrong? How do i get it to export the disk as 230 GB, the size of the disk? thanks in advance, Arno Beekman ___ 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: 0
1 On 10/15/12, abdou massnoue abdoumassnoue2...@gmail.com wrote: ___ 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 ___ 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
X server already running on display :0
I have a problem that I do not understand. At the prompt I give the command startx I get a message that /usr/local/bin/startxfce4 does not exist. Copy the file from another system and I get X server already running on display :0 /usr/local/etc/xdg/xfce4/xinitrc: Can't open /usr/local/etc/xdg/xfce4/xinitrc: File or catalog does not exist I have not knowingly made any changes to this machine. Any suggestions? Thanks /Leslie ___ 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: X server already running on display :0
At the prompt I give the command startx I get a message that /usr/local/bin/startxfce4 does not exist. Copy the file from another system and I get copying files instead of installing packages isn't bright idea, unless you copy complete /usr/local tree. ___ 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: X server already running on display :0
2012-07-21 18:42, Wojciech Puchar skrev: At the prompt I give the command startx I get a message that /usr/local/bin/startxfce4 does not exist. Copy the file from another system and I get copying files instead of installing packages isn't bright idea, unless you copy complete /usr/local tree. ___ 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 I understand that, but I needed to approach the problem some way to get some information. ___ 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: X server already running on display :0
Copy the file from another system and I get X server already running on display :0 /usr/local/etc/xdg/xfce4/xinitrc: Can't open /usr/local/etc/xdg/xfce4/xinitrc: File or catalog does not exist this is an answer i think ___ 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: X server already running on display :0
On Sat, 21 Jul 2012 18:24:26 +0200, Leslie Jensen wrote: I have a problem that I do not understand. At the prompt I give the command startx I get a message that /usr/local/bin/startxfce4 does not exist. This means your ~/.xinitrc contains a call to launch Xfce 4, typically the last command, prefixed by exec, in that file. It seems you don't have Xfce 4 installed. Copy the file from another system and I get X server already running on display :0 /usr/local/etc/xdg/xfce4/xinitrc: Can't open /usr/local/etc/xdg/xfce4/xinitrc: File or catalog does not exist I have not knowingly made any changes to this machine. It's not sufficient to copy just this start script (out of the Xfce 4 software package). You need to _completely_ install it, including all dependencies. You can use pkg_add -r to do this, or use the xfce metaport per make install. Any suggestions? Just install Xfce 4 in one of the usual ways. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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
SV: Re: X server already running on display :0
True! I copied this file as well and now xfce starts as usual. /Leslie Wojciech Puchar woj...@wojtek.tensor.gdynia.pl skrev: Copy the file from another system and I get X server already running on display :0 /usr/local/etc/xdg/xfce4/xinitrc: Can't open /usr/local/etc/xdg/xfce4/xinitrc: File or catalog does not exist this is an answer i think ___ 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
rm returns 0 although directory didn't exist and wasn't deleted ?
I've stumbled upon this *so weird* behaviour. # ls -la /var/tmp/stunnel/ ls: /var/tmp/stunnel/: No such file or directory # rm -Rf /var/tmp/stunnel/ # echo $? 0 Anyone knows if that's intended ? FreeBSD pf2.[snip].com 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Jun 19 10:45:31 CEST 2012 ___ 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: rm returns 0 although directory didn't exist and wasn't deleted ?
On 06/19/2012 03:37 PM, Damien Fleuriot wrote: I've stumbled upon this *so weird* behaviour. # ls -la /var/tmp/stunnel/ ls: /var/tmp/stunnel/: No such file or directory # rm -Rf /var/tmp/stunnel/ # echo $? 0 Anyone knows if that's intended ? rm without -f return 1 in this case ___ 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: rm returns 0 although directory didn't exist and wasn't deleted ?
You used -f which means rm will not complain if a file or directory cannot be deleted (or does not exist in the first place). On Tue, Jun 19, 2012 at 3:37 PM, Damien Fleuriot m...@my.gd wrote: I've stumbled upon this *so weird* behaviour. # ls -la /var/tmp/stunnel/ ls: /var/tmp/stunnel/: No such file or directory # rm -Rf /var/tmp/stunnel/ # echo $? 0 Anyone knows if that's intended ? FreeBSD pf2.[snip].com 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Jun 19 10:45:31 CEST 2012 ___ 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 ___ 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: rm returns 0 although directory didn't exist and wasn't deleted ?
I always assumed -f would only force removal, not modify the exit code. No bug then, working as intended, all good. Cheers On 6/19/12 3:43 PM, Fred Morcos wrote: You used -f which means rm will not complain if a file or directory cannot be deleted (or does not exist in the first place). On Tue, Jun 19, 2012 at 3:37 PM, Damien Fleuriot m...@my.gd wrote: I've stumbled upon this *so weird* behaviour. # ls -la /var/tmp/stunnel/ ls: /var/tmp/stunnel/: No such file or directory # rm -Rf /var/tmp/stunnel/ # echo $? 0 Anyone knows if that's intended ? FreeBSD pf2.[snip].com 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Jun 19 10:45:31 CEST 2012 ___ 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 ___ 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: rm returns 0 although directory didn't exist and wasn't deleted ?
The man page [1] explicitly states that if the file doesn't exist, -f will not show an error message nor alter the exit code. -f Attempt to remove the files without prompting for confirmation, regardless of the file's permissions. If the file does not exist, do not display a diagnostic message or modify the exit status to reflect an error. The -f option overrides any previous -i options. [1] http://www.freebsd.org/cgi/man.cgi?query=rmapropos=0sektion=0manpath=FreeBSD+9.0-RELEASEarch=defaultformat=html On Tue, Jun 19, 2012 at 4:16 PM, Damien Fleuriot m...@my.gd wrote: I always assumed -f would only force removal, not modify the exit code. No bug then, working as intended, all good. Cheers On 6/19/12 3:43 PM, Fred Morcos wrote: You used -f which means rm will not complain if a file or directory cannot be deleted (or does not exist in the first place). On Tue, Jun 19, 2012 at 3:37 PM, Damien Fleuriot m...@my.gd wrote: I've stumbled upon this *so weird* behaviour. # ls -la /var/tmp/stunnel/ ls: /var/tmp/stunnel/: No such file or directory # rm -Rf /var/tmp/stunnel/ # echo $? 0 Anyone knows if that's intended ? FreeBSD pf2.[snip].com 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Jun 19 10:45:31 CEST 2012 ___ 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 ___ 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: rm returns 0 although directory didn't exist and wasn't deleted ?
Damien Fleuriot m...@my.gd wrote: I've stumbled upon this *so weird* behaviour. # ls -la /var/tmp/stunnel/ ls: /var/tmp/stunnel/: No such file or directory # rm -Rf /var/tmp/stunnel/ # echo $? 0 Anyone knows if that's intended ? yes. ___ 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
make world error 9.0-RELEASE #0 i386
Hello All,
I'm trying to build world after having csupped, but the build fails
with:
c++ -O2 -pipe -I/usr/src/lib/clang/libclangsema/../../../contrib/llvm/include
-I/usr/src/lib/clang/libclangsema/../../../contrib/llvm/tools/clang/include
-I/usr/src/lib/clang/libclangsema/../../../contrib/llvm/tools/clang/lib/Sema
-I.
-I/usr/src/lib/clang/libclangsema/../../../contrib/llvm/../../lib/clang/include
-DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS
-DLLVM_HOSTTRIPLE=\i386-unknown-freebsd9.0\ -fstack-protector -fno-exceptions
-fno-rtti -c
/usr/src/lib/clang/libclangsema/../../../contrib/llvm/tools/clang/lib/Sema/SemaTemplateVariadic.cpp
c++ -O2 -pipe -I/usr/src/lib/clang/libclangsema/../../../contrib/llvm/include
-I/usr/src/lib/clang/libclangsema/../../../contrib/llvm/tools/clang/include
-I/usr/src/lib/clang/libclangsema/../../../contrib/llvm/tools/clang/lib/Sema
-I.
-I/usr/src/lib/clang/libclangsema/../../../contrib/llvm/../../lib/clang/include
-DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS
-DLLVM_HOSTTRIPLE=\i386-unknown-freebsd9.0\ -fstack-protector -fno-exceptions
-fno-rtti -c
/usr/src/lib/clang/libclangsema/../../../contrib/llvm/tools/clang/lib/Sema/SemaType.cpp
c++ -O2 -pipe -I/usr/src/lib/clang/libclangsema/../../../contrib/llvm/include
-I/usr/src/lib/clang/libclangsema/../../../contrib/llvm/tools/clang/include
-I/usr/src/lib/clang/libclangsema/../../../contrib/llvm/tools/clang/lib/Sema
-I.
-I/usr/src/lib/clang/libclangsema/../../../contrib/llvm/../../lib/clang/include
-DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS
-DLLVM_HOSTTRIPLE=\i386-unknown-freebsd9.0\ -fstack-protector -fno-exceptions
-fno-rtti -c
/usr/src/lib/clang/libclangsema/../../../contrib/llvm/tools/clang/lib/Sema/TargetAttributesSema.cpp
c++ -O2 -pipe -I/usr/src/lib/clang/libclangsema/../../../contrib/llvm/include
-I/usr/src/lib/clang/libclangsema/../../../contrib/llvm/tools/clang/include
-I/usr/src/lib/clang/libclangsema/../../../contrib/llvm/tools/clang/lib/Sema
-I.
-I/usr/src/lib/clang/libclangsema/../../../contrib/llvm/../../lib/clang/include
-DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS
-DLLVM_HOSTTRIPLE=\i386-unknown-freebsd9.0\ -fstack-protector -fno-exceptions
-fno-rtti -c
/usr/src/lib/clang/libclangsema/../../../contrib/llvm/tools/clang/lib/Sema/SemaChecking.cpp
{standard input}: Assembler messages:
{standard input}:57706: Warning: end of file not at end of a line; newline
inserted
{standard input}: Assembler messages:
{standard input}:71548: Warning: end of file not at end of a line; newline
inserted
{standard input}:71876: Error: no such instruction: `su'
{standard input}:58857: Error: suffix or operands invalid for `mov'
c++: Internal error: Killed: 9 (program cc1plus)
Please submit a full bug report.
See URL:http://gcc.gnu.org/bugs.html for instructions.
*** Error code 1
c++: Internal error: Killed: 9 (program cc1plus)
Please submit a full bug report.
See URL:http://gcc.gnu.org/bugs.html for instructions.
*** Error code 1
2 errors
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error
The build log is at:
http://wwwp.3dresearch.com/KONSTANZE2012041401_buildworld
Would you please advise?
--
Janos Dohanics
___
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: make world error 9.0-RELEASE #0 i386
On Sat, 14 Apr 2012 12:28:52 -0400
Janos Dohanics w...@3dresearch.com wrote:
Hello All,
I'm trying to build world after having csupped, but the build fails
with:
[...]
c++ -O2 -pipe
-I/usr/src/lib/clang/libclangsema/../../../contrib/llvm/include
-I/usr/src/lib/clang/libclangsema/../../../contrib/llvm/tools/clang/include
-I/usr/src/lib/clang/libclangsema/../../../contrib/llvm/tools/clang/lib/Sema
-I.
-I/usr/src/lib/clang/libclangsema/../../../contrib/llvm/../../lib/clang/include
-DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS
-D__STDC_CONSTANT_MACROS -DLLVM_HOSTTRIPLE=\i386-unknown-freebsd9.0
\ -fstack-protector -fno-exceptions -fno-rtti
-c
/usr/src/lib/clang/libclangsema/../../../contrib/llvm/tools/clang/lib/Sema/SemaChecking.cpp
{standard input}: Assembler messages: {standard input}:57706:
Warning: end of file not at end of a line; newline inserted {standard
input}: Assembler messages: {standard input}:71548: Warning: end of
file not at end of a line; newline inserted {standard input}:71876:
Error: no such instruction: `su' {standard input}:58857: Error:
suffix or operands invalid for `mov' c++: Internal error: Killed: 9
(program cc1plus) Please submit a full bug report. See
URL:http://gcc.gnu.org/bugs.html for instructions. *** Error code 1
c++: Internal error: Killed: 9 (program cc1plus) Please submit a full
bug report. See URL:http://gcc.gnu.org/bugs.html for instructions.
*** Error code 1
[...]
I wanted to note that the error occurred when I used make buildworld
with the -j8 switch. Without the -j8 switch the build completed
without errors.
--
Janos Dohanics
___
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
Détecteur D'alcoolémie Porte Clef à 0 euros
Skoopon est heureux de vous présenter les Skoops en National Afin de visualiser l'ensemble de la Newsletter cliquez sur ce liens : http://news.skoopon.fr/public/read_message.jsp?tsp=1333213729524custid=15101uid=15027764244sig=FEAHJFFGIEINCIHMmid=151435 Pour être sur de recevoir tous nos emails, ajoutez charlo...@info.skoopon.fr à votre carnet d´adresses. Skoop N°1: http://news.skoopon.fr/re?l=ot28ijI6wj553oI0req=wizzMailCircle%3Dfreebsd-questions%40freebsd.org DéTECTEUR D'ALCOOLéMIE PORTE CLEF OFFRE EXCLUSIVE ! SOYEZ PRUDENT AU VOLANT, SOUFFLEZ, ATTENDEZ, CONSTATEZ VOTRE TAUX D'ALCOOLéMIE ! PRENEZ LA ROUTE EN SéCURITé GRâCE à CE PORTE CLEF DéTECTEUR D'ALCOOLéMIE POUR 0€ ! Skoop N°2: http://news.skoopon.fr/re?l=ot28ijI6wj553oI1req=wizzMailCircle%3Dfreebsd-questions%40freebsd.org ROULEAU LED ECLAIREZ VOTRE BAR, VOTRE SALON OU L'EXTéRIEUR DE VOTRE MAISON, GRâCE AU ROULEAU LED, POUR SEULEMENT 49€ AU LIEU DE 149€ Skoop N°3: http://news.skoopon.fr/re?l=ot28ijI6wj553oI2req=wizzMailCircle%3Dfreebsd-questions%40freebsd.org FILM DE PROTECTION ALLIEZ PROTECTION ET CLASSE GRâCE AUX FILMS DE PROTECTION IPHONE 4/4S ! POUR SEULEMENT 7€ AU LIEU DE 19,90€ ! FDP INCLUS Skoop N°4: http://news.skoopon.fr/re?l=ot28ijI6wj553oI3req=wizzMailCircle%3Dfreebsd-questions%40freebsd.org SOUTIENS-GORGES AHH BRA UNE VéRITABLE RéVOLUTION, LES SOUTIENS-GORGES AHH BRA ! ULTRA CONFORT, GALBE LA POITRINE, UN MAINTIEN PARFAIT! VOTRE LOT DE 3 SOUTIENS-GORGES POUR SEULEMENT 19,90€ AU LIEU DE 69 € ! Skoop N°5: http://news.skoopon.fr/re?l=ot28ijI6wj553oI4req=wizzMailCircle%3Dfreebsd-questions%40freebsd.org ECIGARETTE-WEB CASE NE DéTRUISEZ PLUS VOTRE SANTé EN FUMANT ET DIMINUEZ PROGRESSIVEMENT VOTRE ACOUTUMANCE AU TABAC GRâCE à CETTE ECIGARETTE ! POUR SEULEMENT 9,95€ AU LIEU DE 38,50€ Vous recevez cet e-mail car vous faites confiance a Skoopon. Vous pouvez a tout moment décider de ne plus recevoir de message de notre part. Vous désinscrire : http://news.skoopon.fr/public/unsubscribe.jsp?gid=150377uid=15027764244mid=151435sig=FEHAIMBILLHHBGJM Le site skoopon.fr est une propriété de la société WIZZDEALS. La société WIZZDEALS est une société par actions simplifiée dont le siège social est situé, 6 rue Troyon - 92310 Sévres (France) et enregistrée au Registre du Commerce et des Sociétés de Paris sous le numéro 532 937 596. Mentions Légales : http://news.skoopon.fr/re?l=ot28ijI6wj553oI5 Conditions générales de ventes : http://news.skoopon.fr/re?l=ot28ijI6wj553oI6 ___ 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: /lib/exec/ld-elf.so.1: Shared object libpcre.so.0 not found, required by libxfsm-4.6.so.0 amd64 FreeBSD 8.2
On Thu, Feb 16, 2012 at 9:08 AM, Antonio Olivares olivares14...@gmail.com wrote: On Thu, Feb 16, 2012 at 8:18 AM, Ryan Frederick ryanrfreder...@gmail.com wrote: It looks like others have run into this problem with avahi-app as well: http://lists.freebsd.org/pipermail/freebsd-ports/2011-July/068658.html A cursory search shows that uninstalling avahi-app then reinstalling should take care of the compilation failure. Afterward you should be able to run portmaster as shown in the error message (minus 'net/avahi-app') to finish recompiling the ports that depend on pcre. Ryan This does make the desktop work again :) I followed the advice and am back in the saddle. Some things failed to compile, but I used -x parameter to not update them. I will track those ports later. I appreciate the help and advice provided. It appears that a new pcre update hits the ports later. I wonder if it bypasses the original problem. Regards, Antonio ___ 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: /lib/exec/ld-elf.so.1: Shared object libpcre.so.0 not found, required by libxfsm-4.6.so.0 amd64 FreeBSD 8.2
On Thu, 16 Feb 2012 09:08:54 -0600 Antonio Olivares wrote: On Thu, Feb 16, 2012 at 8:18 AM, Ryan Frederick ryanrfreder...@gmail.com wrote: It looks like others have run into this problem with avahi-app as well: http://lists.freebsd.org/pipermail/freebsd-ports/2011-July/068658.html A cursory search shows that uninstalling avahi-app then reinstalling should take care of the compilation failure. Afterward you should be able to run portmaster as shown in the error message (minus 'net/avahi-app') to finish recompiling the ports that depend on pcre. Thanks Ryan when I get home tonight, I will remove avahi-app and reinstall it and then recompile all the ports that depend on pcre. I ran into this problem yesterday and removing avahi-ap didn't fix it for me. In the end I identified some orphaned libraries under /usr/local/ and deleting those fixed the problem. ___ 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: /lib/exec/ld-elf.so.1: Shared object libpcre.so.0 not found, required by libxfsm-4.6.so.0 amd64 FreeBSD 8.2
It looks like others have run into this problem with avahi-app as well:
http://lists.freebsd.org/pipermail/freebsd-ports/2011-July/068658.html
A cursory search shows that uninstalling avahi-app then reinstalling
should take care of the compilation failure. Afterward you should be
able to run portmaster as shown in the error message (minus
'net/avahi-app') to finish recompiling the ports that depend on pcre.
Ryan
On 02/15/2012 10:55 PM, Antonio Olivares wrote:
On Wed, Feb 15, 2012 at 9:33 PM, Robert Bonomibon...@mail.r-bonomi.com wrote:
Antonio Olivaresolivares14...@gmail.com wrote;
I am doing this and see how it goes. I used ldd to check for
libprce.so and I got :
ldd /usr/local/lib/libprce.so:
libc.so.7 = /lib/libc.so.7 (0x800647000)
ldd /usr/local/lib/libprce.so.1:
libc.so.7 = /lib/libc.so.7 (0x800647000)
There are two of them :( Should there be only one?
This is _normal_. The .so (with no further sufix), is generally just a link
to the 'latest' .so *with* a numeric suffix.
I am in a not good state now. I broke two machines by updating to
latest and get the same error on both machines.
I get the /libexec/ld-elf.so.1: Shared object libpcre.so.0 is needed
by * and nothing works, I run
# portmaster -r pcre-8.30
and it bombs out with the following:
signals-marshal.c:186: warning: ISO C forbids conversion of object
pointer to function pointer type
CC libavahi_gobject_la-ga-client-enumtypes.lo
CC libavahi_gobject_la-ga-entry-group-enumtypes.lo
CC libavahi_gobject_la-ga-enums-enumtypes.lo
CCLD libavahi-gobject.la
GISCAN Avahi-0.6.gir
g-ir-scanner: warning: Option --strip-prefix has been deprecated;
see --identifier-prefix and --symbol-prefix.
/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 ';'
/libexec/ld-elf.so.1: Shared object libpcre.so.0 not found, required
by libavahi-glib.so.1
Command
'['/usr/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject/tmp-introspectGYNEXM/Avahi-0.6',
'--introspect-dump=/usr/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject/tmp-introspectGYNEXM/types.txt,/usr/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject/tmp-introspectGYNEXM/dump.xml']'
returned non-zero exit status 1
gmake[3]: *** [Avahi-0.6.gir] Error 1
gmake[3]: Leaving directory
`/usr/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject'
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory
`/usr/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr/ports/net/avahi-app/work/avahi-0.6.29'
gmake: *** [all] Error 2
*** Error code 1
Stop in /usr/ports/net/avahi-app.
=== make failed for net/avahi-app
=== Aborting update
=== Update for avahi-app-0.6.29_1 failed
=== Aborting update
=== Update for gvfs-1.6.6_2 failed
=== Aborting update
=== Update for Thunar-1.3.0 failed
=== Aborting update
Terminated
=== There are messages from installed ports to display,
but first take a moment to review the error messages
above. Then press Enter when ready to proceed.
=== pkg-message for gamin-0.1.10_4
===
Gamin will only provide realtime notification of changes for at most n files,
where n is the minimum value between (kern.maxfiles * 0.7) and
(kern.maxfilesperproc - 200). Beyond that limit, files will be polled.
If you often open several large folders with Nautilus, you might want to
increase the kern.maxfiles tunable (you do not need to set
kern.maxfilesperproc, since it is computed at boot time from kern.maxfiles).
For a typical desktop, add the following line to /boot/loader.conf, then
reboot the system:
kern.maxfiles=25000
The behavior of gamin can be controlled via the various gaminrc files.
See http://www.gnome.org/~veillard/gamin/config.html on how to create
these files. In particular, if you find gam_server is taking up too much
CPU time polling for changes, something like the following may help
in one of the gaminrc files:
# reduce polling frequency to once per 10 seconds
# for UFS file systems in order to lower CPU load
fsset ufs poll 10
===
=== pkg-message for liblqr-1-0.4.1_2
Re: /lib/exec/ld-elf.so.1: Shared object libpcre.so.0 not found, required by libxfsm-4.6.so.0 amd64 FreeBSD 8.2
On Thu, Feb 16, 2012 at 8:18 AM, Ryan Frederick ryanrfreder...@gmail.com wrote: It looks like others have run into this problem with avahi-app as well: http://lists.freebsd.org/pipermail/freebsd-ports/2011-July/068658.html A cursory search shows that uninstalling avahi-app then reinstalling should take care of the compilation failure. Afterward you should be able to run portmaster as shown in the error message (minus 'net/avahi-app') to finish recompiling the ports that depend on pcre. Ryan Thanks Ryan when I get home tonight, I will remove avahi-app and reinstall it and then recompile all the ports that depend on pcre. Then if successfull hopefully, I will report back. Thanks for your help guidance. Regards, Antonio ___ 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
/lib/exec/ld-elf.so.1: Shared object libpcre.so.0 not found, required by libxfsm-4.6.so.0 amd64 FreeBSD 8.2
Dear folks, I updated ports and one failed, gimp-app. I checked /usr/src/UPDATING and I followed advice there to run # portmaster -w devel/pcre and I did this, and now machine won't get X. How can I bypass this mistake? I am now hesitant to update the other machines :(, I will get into problems starting X because of some update of a certain lib. Any thoughts, ideas or suggestions? Regards, Antonio ___ 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: /lib/exec/ld-elf.so.1: Shared object libpcre.so.0 not found, required by libxfsm-4.6.so.0 amd64 FreeBSD 8.2
You can recompile all ports that depend on pcre so that they'll use the new shared library. You can do so with: # portmaster -r pcre-8.30 Ryan On 02/15/2012 08:42 PM, Antonio Olivares wrote: Dear folks, I updated ports and one failed, gimp-app. I checked /usr/src/UPDATING and I followed advice there to run # portmaster -w devel/pcre and I did this, and now machine won't get X. How can I bypass this mistake? I am now hesitant to update the other machines :(, I will get into problems starting X because of some update of a certain lib. Any thoughts, ideas or suggestions? Regards, Antonio ___ 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 ___ 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: /lib/exec/ld-elf.so.1: Shared object libpcre.so.0 not found, required by libxfsm-4.6.so.0 amd64 FreeBSD 8.2
You can recompile all ports that depend on pcre so that they'll use the new shared library. You can do so with: # portmaster -r pcre-8.30 Ryan On 02/15/2012 08:42 PM, Antonio Olivares wrote: Dear folks, I updated ports and one failed, gimp-app. I checked /usr/src/UPDATING and I followed advice there to run # portmaster -w devel/pcre and I did this, and now machine won't get X. How can I bypass this mistake? I am now hesitant to update the other machines :(, I will get into problems starting X because of some update of a certain lib. Any thoughts, ideas or suggestions? Regards, Antonio ___ I am doing this and see how it goes. I used ldd to check for libprce.so and I got : ldd /usr/local/lib/libprce.so: libc.so.7 = /lib/libc.so.7 (0x800647000) ldd /usr/local/lib/libprce.so.1: libc.so.7 = /lib/libc.so.7 (0x800647000) There are two of them :( Should there be only one? Thanks for your advice. Regards, Antonio ___ 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: /lib/exec/ld-elf.so.1: Shared object libpcre.so.0 not found, required by libxfsm-4.6.so.0 amd64 FreeBSD 8.2
Antonio Olivares olivares14...@gmail.com wrote; I am doing this and see how it goes. I used ldd to check for libprce.so and I got : ldd /usr/local/lib/libprce.so: libc.so.7 = /lib/libc.so.7 (0x800647000) ldd /usr/local/lib/libprce.so.1: libc.so.7 = /lib/libc.so.7 (0x800647000) There are two of them :( Should there be only one? This is _normal_. The .so (with no further sufix), is generally just a link to the 'latest' .so *with* a numeric suffix. ___ 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: /lib/exec/ld-elf.so.1: Shared object libpcre.so.0 not found, required by libxfsm-4.6.so.0 amd64 FreeBSD 8.2
On Wed, Feb 15, 2012 at 9:33 PM, Robert Bonomi bon...@mail.r-bonomi.com wrote:
Antonio Olivares olivares14...@gmail.com wrote;
I am doing this and see how it goes. I used ldd to check for
libprce.so and I got :
ldd /usr/local/lib/libprce.so:
libc.so.7 = /lib/libc.so.7 (0x800647000)
ldd /usr/local/lib/libprce.so.1:
libc.so.7 = /lib/libc.so.7 (0x800647000)
There are two of them :( Should there be only one?
This is _normal_. The .so (with no further sufix), is generally just a link
to the 'latest' .so *with* a numeric suffix.
I am in a not good state now. I broke two machines by updating to
latest and get the same error on both machines.
I get the /libexec/ld-elf.so.1: Shared object libpcre.so.0 is needed
by * and nothing works, I run
# portmaster -r pcre-8.30
and it bombs out with the following:
signals-marshal.c:186: warning: ISO C forbids conversion of object
pointer to function pointer type
CC libavahi_gobject_la-ga-client-enumtypes.lo
CC libavahi_gobject_la-ga-entry-group-enumtypes.lo
CC libavahi_gobject_la-ga-enums-enumtypes.lo
CCLD libavahi-gobject.la
GISCAN Avahi-0.6.gir
g-ir-scanner: warning: Option --strip-prefix has been deprecated;
see --identifier-prefix and --symbol-prefix.
/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 ';'
/libexec/ld-elf.so.1: Shared object libpcre.so.0 not found, required
by libavahi-glib.so.1
Command
'['/usr/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject/tmp-introspectGYNEXM/Avahi-0.6',
'--introspect-dump=/usr/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject/tmp-introspectGYNEXM/types.txt,/usr/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject/tmp-introspectGYNEXM/dump.xml']'
returned non-zero exit status 1
gmake[3]: *** [Avahi-0.6.gir] Error 1
gmake[3]: Leaving directory
`/usr/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject'
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory
`/usr/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr/ports/net/avahi-app/work/avahi-0.6.29'
gmake: *** [all] Error 2
*** Error code 1
Stop in /usr/ports/net/avahi-app.
=== make failed for net/avahi-app
=== Aborting update
=== Update for avahi-app-0.6.29_1 failed
=== Aborting update
=== Update for gvfs-1.6.6_2 failed
=== Aborting update
=== Update for Thunar-1.3.0 failed
=== Aborting update
Terminated
=== There are messages from installed ports to display,
but first take a moment to review the error messages
above. Then press Enter when ready to proceed.
=== pkg-message for gamin-0.1.10_4
===
Gamin will only provide realtime notification of changes for at most n files,
where n is the minimum value between (kern.maxfiles * 0.7) and
(kern.maxfilesperproc - 200). Beyond that limit, files will be polled.
If you often open several large folders with Nautilus, you might want to
increase the kern.maxfiles tunable (you do not need to set
kern.maxfilesperproc, since it is computed at boot time from kern.maxfiles).
For a typical desktop, add the following line to /boot/loader.conf, then
reboot the system:
kern.maxfiles=25000
The behavior of gamin can be controlled via the various gaminrc files.
See http://www.gnome.org/~veillard/gamin/config.html on how to create
these files. In particular, if you find gam_server is taking up too much
CPU time polling for changes, something like the following may help
in one of the gaminrc files:
# reduce polling frequency to once per 10 seconds
# for UFS file systems in order to lower CPU load
fsset ufs poll 10
===
=== pkg-message for liblqr-1-0.4.1_2
==
NOTE: In order to compile examples for liblqr, you will
also need pngwriter port (/usr/ports/graphics/pngwriter).
Examples are located in /usr/local/share/examples/liblqr-1
==
=== Done displaying pkg-message files
=== The following actions were performed:
Re-installation of pcre-8.30
Re-installation of glib-2.28.8_4
Re-installation of gamin-0.1.10_4
Re-installation of gio-fam-backend
how safe is kern.geom.part.check_integrity=0 ?
Hello, I upgraded today a gmirror'ed machine from 8.2-RELEASE to 9.0-RELEASE, but the system fails to mount my root mirror with an error 19 when I try to boot with the 9.0 kernel. I read that adding kern.geom.part.check_integrity=0 could solve the problem, but I haven't found any statement on the safety of setting this.. Any idea if it's safe ? Also I'm a bit disappointed that there is no entry in /usr/src/UPDATING about this issue ... Thanks, Julien ___ 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: Shared object libxcb-aux.so.0 not found, required by libxfsm-4.6.so.0 FreeBSD
Dear folks, I had a FreeBSD 9.0 BETA 2 Machine I was happily running since the release and only updated ports via portmaster -a, and now since Fedora 9 has officially been released, I ran make buildworld, make Correction here. Meant FreeBSD 9.0 not Fedora 9 :( Message probably ignored because of this. buildkernel, make installkernel and mergemaster -i, and make installworld and now X does not work, I get error in subject Shared object libxcb-aux.so.0 not found, required by libxfsm-4.6.so.0 FreeBSD any ideas/suggestions for a fix? Thanks in advance, Antonio Found a solution updated following advice in the other lib***.so message, recompiled the ports that depended on it and now I am running 9.0 Stable. $ uname -a FreeBSD e213-amd64-1.grullahighschool.org 9.0-STABLE FreeBSD 9.0-STABLE #1: Mon Jan 16 14:48:05 CST 2012 r...@e213-amd64-1.grullahighschool.org:/usr/obj/usr/src/sys/GENERIC amd64 $ uname -r 9.0-STABLE Regards, Antonio ___ 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: Shared object libxcb-aux.so.0 not found, required by libxfsm-4.6.so.0 FreeBSD
On Tue, Jan 17, 2012 at 12:05 PM, Antonio Olivares olivares14...@gmail.comwrote: Dear folks, I had a FreeBSD 9.0 BETA 2 Machine I was happily running since the release and only updated ports via portmaster -a, and now since Fedora 9 has officially been released, I ran make buildworld, make Correction here. Meant FreeBSD 9.0 not Fedora 9 :( Message probably ignored because of this. buildkernel, make installkernel and mergemaster -i, and make installworld and now X does not work, I get error in subject Shared object libxcb-aux.so.0 not found, required by libxfsm-4.6.so.0 FreeBSD any ideas/suggestions for a fix? Thanks in advance, Antonio Found a solution updated following advice in the other lib***.so message, recompiled the ports that depended on it and now I am running 9.0 Stable. $ uname -a FreeBSD e213-amd64-1.grullahighschool.org 9.0-STABLE FreeBSD 9.0-STABLE #1: Mon Jan 16 14:48:05 CST 2012 r...@e213-amd64-1.grullahighschool.org:/usr/obj/usr/src/sys/GENERIC amd64 $ uname -r 9.0-STABLE There is instructions in ports/UPDATING on how to update. http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/ports/UPDATING?rev=1.1193;content-type=text%2Fplain Regards, Antonio ___ 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 ___ 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: Shared object libxcb-aux.so.0 not found, required by libxfsm-4.6.so.0 FreeBSD
Even after following said instruction in UPDATING, libxcb-aux.so.0 does not get installed by any of the XCB ports #pkg_info |grep -i xcb libxcb-1.7 The X protocol C-language Binding (XCB) library xcb-proto-1.6 The X protocol C-language Binding (XCB) protocol xcb-util-0.3.8,1A module with libxcb/libX11 extension/replacement libraries xcb-util-renderutil-0.3.8 Convenience functions for the Render extension [15:02:44] root@jimmiejaz 156 [1] /usr/ports#grep -iR aux /usr/ports/x11/libxcb/ [15:02:46] root@jimmiejaz 157 [1] /usr/ports# [15:02:46] root@jimmiejaz 157 [1] /usr/ports#grep -iR aux /usr/ports/x11/xcb-proto/ [15:02:57] root@jimmiejaz 158 [1] /usr/ports# [15:02:57] root@jimmiejaz 158 [1] /usr/ports#grep -iR aux /usr/ports/x11/xcb-util/ /usr/ports/x11/xcb-util/pkg-descr:aux: Convenient access to connection setup and some core requests. /usr/ports/x11/xcb-util/pkg-plist:libdata/pkgconfig/xcb-aux.pc /usr/ports/x11/xcb-util/pkg-plist:include/xcb/xcb_aux.h [15:03:21] root@jimmiejaz 160 [1] /usr/ports#grep -iR aux /usr/ports/x11/xcb-util-renderutil/ [15:03:25] root@jimmiejaz 161 [1] /usr/ports# [15:03:49] root@jimmiejaz 162 [0] /usr/ports#ls -ali /usr/local/lib/libxcb* 4365562 -rw-r--r-- 1 root wheel5954 Jan 17 11:15 /usr/local/lib/libxcb-composite.a 4358679 -rwxr-xr-x 1 root wheel1122 Jan 17 11:15 /usr/local/lib/libxcb-composite.la 4358554 lrwxr-xr-x 1 root wheel 21 Jan 17 11:15 /usr/local/lib/libxcb-composite.so - libxcb-composite.so.0 4358144 -rwxr-xr-x 1 root wheel 10243 Jan 17 11:15 /usr/local/lib/libxcb-composite.so.0 4365621 -rw-r--r-- 1 root wheel3726 Jan 17 11:15 /usr/local/lib/libxcb-damage.a 4359908 -rwxr-xr-x 1 root wheel1101 Jan 17 11:15 /usr/local/lib/libxcb-damage.la 4359055 lrwxr-xr-x 1 root wheel 18 Jan 17 11:15 /usr/local/lib/libxcb-damage.so - libxcb-damage.so.0 4358823 -rwxr-xr-x 1 root wheel8124 Jan 17 11:15 /usr/local/lib/libxcb-damage.so.0 4365705 -rw-r--r-- 1 root wheel4934 Jan 17 11:15 /usr/local/lib/libxcb-dpms.a 4360413 -rwxr-xr-x 1 root wheel1087 Jan 17 11:15 /usr/local/lib/libxcb-dpms.la 4360286 lrwxr-xr-x 1 root wheel 16 Jan 17 11:15 /usr/local/lib/libxcb-dpms.so - libxcb-dpms.so.0 4360076 -rwxr-xr-x 1 root wheel9308 Jan 17 11:15 /usr/local/lib/libxcb-dpms.so.0 4365728 -rw-r--r-- 1 root wheel7446 Jan 17 11:15 /usr/local/lib/libxcb-dri2.a 4361232 -rwxr-xr-x 1 root wheel1087 Jan 17 11:15 /usr/local/lib/libxcb-dri2.la 4361186 lrwxr-xr-x 1 root wheel 16 Jan 17 11:15 /usr/local/lib/libxcb-dri2.so - libxcb-dri2.so.0 4360540 -rwxr-xr-x 1 root wheel 12443 Jan 17 11:15 /usr/local/lib/libxcb-dri2.so.0 4365820 -rw-r--r-- 1 root wheel 76298 Jan 17 11:15 /usr/local/lib/libxcb-glx.a 4360123 -rwxr-xr-x 1 root wheel1080 Jan 17 11:15 /usr/local/lib/libxcb-glx.la 4358974 lrwxr-xr-x 1 root wheel 15 Jan 17 11:15 /usr/local/lib/libxcb-glx.so - libxcb-glx.so.0 4357984 -rwxr-xr-x 1 root wheel 93658 Jan 17 11:15 /usr/local/lib/libxcb-glx.so.0 4365965 -rw-r--r-- 1 root wheel 33046 Jan 17 11:15 /usr/local/lib/libxcb-randr.a 4361383 -rwxr-xr-x 1 root wheel1094 Jan 17 11:15 /usr/local/lib/libxcb-randr.la 4361299 lrwxr-xr-x 1 root wheel 17 Jan 17 11:15 /usr/local/lib/libxcb-randr.so - libxcb-randr.so.1 4360759 -rwxr-xr-x 1 root wheel 42343 Jan 17 11:15 /usr/local/lib/libxcb-randr.so.1 4365973 -rw-r--r-- 1 root wheel8334 Jan 17 11:15 /usr/local/lib/libxcb-record.a 4361729 -rwxr-xr-x 1 root wheel1101 Jan 17 11:15 /usr/local/lib/libxcb-record.la 4361558 lrwxr-xr-x 1 root wheel 18 Jan 17 11:15 /usr/local/lib/libxcb-record.so - libxcb-record.so.0 4361389 -rwxr-xr-x 1 root wheel 13354 Jan 17 11:15 /usr/local/lib/libxcb-record.so.0 4364285 -rw-r--r-- 1 root wheel9352 Jan 17 11:17 /usr/local/lib/libxcb-render-util.a 4363760 -rwxr-xr-x 1 root wheel1160 Jan 17 11:17 /usr/local/lib/libxcb-render-util.la 4363404 lrwxr-xr-x 1 root wheel 23 Jan 17 11:17 /usr/local/lib/libxcb-render-util.so - libxcb-render-util.so.0 4361280 -rwxr-xr-x 1 root wheel 14635 Jan 17 11:17 /usr/local/lib/libxcb-render-util.so.0 4365981 -rw-r--r-- 1 root wheel 26920 Jan 17 11:15 /usr/local/lib/libxcb-render.a 4362055 -rwxr-xr-x 1 root wheel1101 Jan 17 11:15 /usr/local/lib/libxcb-render.la 4361857 lrwxr-xr-x 1 root wheel 18 Jan 17 11:15 /usr/local/lib/libxcb-render.so - libxcb-render.so.0 4361765 -rwxr-xr-x 1 root wheel 34109 Jan 17 11:15 /usr/local/lib/libxcb-render.so.0 4366287 -rw-r--r-- 1 root wheel4526 Jan 17 11:15 /usr/local/lib/libxcb-res.a 4362171 -rwxr-xr-x 1 root wheel1080 Jan 17 11:15 /usr/local/lib/libxcb-res.la 4362161 lrwxr-xr-x 1 root wheel 15 Jan 17 11:15 /usr/local/lib/libxcb-res.so - libxcb-res.so.0 4362061 -rwxr-xr-x 1 root wheel8938 Jan 17 11:15 /usr/local/lib/libxcb-res.so.0 4366313 -rw-r--r-- 1 root wheel
Re: Shared object libxcb-aux.so.0 not found, required by libxfsm-4.6.so.0 FreeBSD
On Tue, Jan 17, 2012 at 3:04 PM, Jimmie James jimmie...@gmail.com wrote: Even after following said instruction in UPDATING, libxcb-aux.so.0 does not get installed by any of the XCB ports It was replaced with libxcb-util.so.0. #pkg_info |grep -i xcb libxcb-1.7 The X protocol C-language Binding (XCB) library xcb-proto-1.6 The X protocol C-language Binding (XCB) protocol xcb-util-0.3.8,1A module with libxcb/libX11 extension/replacement libraries xcb-util-renderutil-0.3.8 Convenience functions for the Render extension [15:02:44] root@jimmiejaz 156 [1] /usr/ports#grep -iR aux /usr/ports/x11/libxcb/ [15:02:46] root@jimmiejaz 157 [1] /usr/ports# [15:02:46] root@jimmiejaz 157 [1] /usr/ports#grep -iR aux /usr/ports/x11/xcb-proto/ [15:02:57] root@jimmiejaz 158 [1] /usr/ports# [15:02:57] root@jimmiejaz 158 [1] /usr/ports#grep -iR aux /usr/ports/x11/xcb-util/ /usr/ports/x11/xcb-util/pkg-**descr:aux: Convenient access to connection setup and some core requests. /usr/ports/x11/xcb-util/pkg-**plist:libdata/pkgconfig/xcb-**aux.pc /usr/ports/x11/xcb-util/pkg-**plist:include/xcb/xcb_aux.h [15:03:21] root@jimmiejaz 160 [1] /usr/ports#grep -iR aux /usr/ports/x11/xcb-util-**renderutil/ [15:03:25] root@jimmiejaz 161 [1] /usr/ports# [15:03:49] root@jimmiejaz 162 [0] /usr/ports#ls -ali /usr/local/lib/libxcb* 4365562 -rw-r--r-- 1 root wheel5954 Jan 17 11:15 /usr/local/lib/libxcb-**composite.a 4358679 -rwxr-xr-x 1 root wheel1122 Jan 17 11:15 /usr/local/lib/ libxcb-**composite.la http://libxcb-composite.la 4358554 lrwxr-xr-x 1 root wheel 21 Jan 17 11:15 /usr/local/lib/libxcb-**composite.so - libxcb-composite.so.0 4358144 -rwxr-xr-x 1 root wheel 10243 Jan 17 11:15 /usr/local/lib/libxcb-**composite.so.0 4365621 -rw-r--r-- 1 root wheel3726 Jan 17 11:15 /usr/local/lib/libxcb-damage.a 4359908 -rwxr-xr-x 1 root wheel1101 Jan 17 11:15 /usr/local/lib/ libxcb-damage.**la http://libxcb-damage.la 4359055 lrwxr-xr-x 1 root wheel 18 Jan 17 11:15 /usr/local/lib/libxcb-damage.**so - libxcb-damage.so.0 4358823 -rwxr-xr-x 1 root wheel8124 Jan 17 11:15 /usr/local/lib/libxcb-damage.**so.0 4365705 -rw-r--r-- 1 root wheel4934 Jan 17 11:15 /usr/local/lib/libxcb-dpms.a 4360413 -rwxr-xr-x 1 root wheel1087 Jan 17 11:15 /usr/local/lib/ libxcb-dpms.la 4360286 lrwxr-xr-x 1 root wheel 16 Jan 17 11:15 /usr/local/lib/libxcb-dpms.so - libxcb-dpms.so.0 4360076 -rwxr-xr-x 1 root wheel9308 Jan 17 11:15 /usr/local/lib/libxcb-dpms.so.**0 4365728 -rw-r--r-- 1 root wheel7446 Jan 17 11:15 /usr/local/lib/libxcb-dri2.a 4361232 -rwxr-xr-x 1 root wheel1087 Jan 17 11:15 /usr/local/lib/ libxcb-dri2.la 4361186 lrwxr-xr-x 1 root wheel 16 Jan 17 11:15 /usr/local/lib/libxcb-dri2.so - libxcb-dri2.so.0 4360540 -rwxr-xr-x 1 root wheel 12443 Jan 17 11:15 /usr/local/lib/libxcb-dri2.so.**0 4365820 -rw-r--r-- 1 root wheel 76298 Jan 17 11:15 /usr/local/lib/libxcb-glx.a 4360123 -rwxr-xr-x 1 root wheel1080 Jan 17 11:15 /usr/local/lib/ libxcb-glx.la 4358974 lrwxr-xr-x 1 root wheel 15 Jan 17 11:15 /usr/local/lib/libxcb-glx.so - libxcb-glx.so.0 4357984 -rwxr-xr-x 1 root wheel 93658 Jan 17 11:15 /usr/local/lib/libxcb-glx.so.0 4365965 -rw-r--r-- 1 root wheel 33046 Jan 17 11:15 /usr/local/lib/libxcb-randr.a 4361383 -rwxr-xr-x 1 root wheel1094 Jan 17 11:15 /usr/local/lib/ libxcb-randr.la 4361299 lrwxr-xr-x 1 root wheel 17 Jan 17 11:15 /usr/local/lib/libxcb-randr.so - libxcb-randr.so.1 4360759 -rwxr-xr-x 1 root wheel 42343 Jan 17 11:15 /usr/local/lib/libxcb-randr.**so.1 4365973 -rw-r--r-- 1 root wheel8334 Jan 17 11:15 /usr/local/lib/libxcb-record.a 4361729 -rwxr-xr-x 1 root wheel1101 Jan 17 11:15 /usr/local/lib/ libxcb-record.**la http://libxcb-record.la 4361558 lrwxr-xr-x 1 root wheel 18 Jan 17 11:15 /usr/local/lib/libxcb-record.**so - libxcb-record.so.0 4361389 -rwxr-xr-x 1 root wheel 13354 Jan 17 11:15 /usr/local/lib/libxcb-record.**so.0 4364285 -rw-r--r-- 1 root wheel9352 Jan 17 11:17 /usr/local/lib/libxcb-render-**util.a 4363760 -rwxr-xr-x 1 root wheel1160 Jan 17 11:17 /usr/local/lib/ libxcb-render-**util.la http://libxcb-render-util.la 4363404 lrwxr-xr-x 1 root wheel 23 Jan 17 11:17 /usr/local/lib/libxcb-render-**util.so - libxcb-render-util.so.0 4361280 -rwxr-xr-x 1 root wheel 14635 Jan 17 11:17 /usr/local/lib/libxcb-render-**util.so.0 4365981 -rw-r--r-- 1 root wheel 26920 Jan 17 11:15 /usr/local/lib/libxcb-render.a 4362055 -rwxr-xr-x 1 root wheel1101 Jan 17 11:15 /usr/local/lib/ libxcb-render.**la http://libxcb-render.la 4361857 lrwxr-xr-x 1 root wheel 18 Jan 17 11:15 /usr/local/lib/libxcb-render.**so - libxcb-render.so.0 4361765 -rwxr-xr-x 1 root wheel 34109 Jan 17 11:15 /usr/local/lib/libxcb-render.**so.0 4366287 -rw-r--r-- 1 root wheel4526 Jan 17
Re: Shared object libxcb-aux.so.0 not found, required by libxfsm-4.6.so.0 FreeBSD
On 01/17/12 15:39, Michael Johnson wrote: On Tue, Jan 17, 2012 at 3:04 PM, Jimmie James jimmie...@gmail.com mailto:jimmie...@gmail.com wrote: Even after following said instruction in UPDATING, libxcb-aux.so.0 does not get installed by any of the XCB ports It was replaced with libxcb-util.so.0. So it's the xfce4-wm port that's broken now, since it's still looking for the old libs. When applications fail because they're looking for a library that's been removed, following UPDATING doesn't help. gmake[3]: Entering directory `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/settings-dialogs' CC xfwm4_settings-xfwm4-settings.o CCLD xfwm4-settings CC xfwm4_tweaks_settings-tweaks-settings.o CCLD xfwm4-tweaks-settings CC xfwm4_workspace_settings-workspace-settings.o CCLD xfwm4-workspace-settings libtool: link: cannot find the library `/usr/local/lib/libxcb-aux.la' or unhandled argument `/usr/local/lib/libxcb-aux.la' ___ 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: Shared object libxcb-aux.so.0 not found, required by libxfsm-4.6.so.0 FreeBSD
On Tue, 17 Jan 2012, Jimmie James wrote: On 01/17/12 15:39, Michael Johnson wrote: On Tue, Jan 17, 2012 at 3:04 PM, Jimmie James jimmie...@gmail.com mailto:jimmie...@gmail.com wrote: Even after following said instruction in UPDATING, libxcb-aux.so.0 does not get installed by any of the XCB ports It was replaced with libxcb-util.so.0. So it's the xfce4-wm port that's broken now, since it's still looking for the old libs. When applications fail because they're looking for a library that's been removed, following UPDATING doesn't help. Building xfce4-wm here just worked. It was rebuilt yesterday, too, as part of the portmaster xcb-util rebuild (which pretty much rebuilt everything). Did you do a 'make clean' before retrying? ___ 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: Shared object libxcb-aux.so.0 not found, required by libxfsm-4.6.so.0 FreeBSD
On 01/17/12 16:50, Warren Block wrote: On Tue, 17 Jan 2012, Jimmie James wrote: On 01/17/12 15:39, Michael Johnson wrote: On Tue, Jan 17, 2012 at 3:04 PM, Jimmie James jimmie...@gmail.com mailto:jimmie...@gmail.com wrote: Even after following said instruction in UPDATING, libxcb-aux.so.0 does not get installed by any of the XCB ports It was replaced with libxcb-util.so.0. So it's the xfce4-wm port that's broken now, since it's still looking for the old libs. When applications fail because they're looking for a library that's been removed, following UPDATING doesn't help. Building xfce4-wm here just worked. It was rebuilt yesterday, too, as part of the portmaster xcb-util rebuild (which pretty much rebuilt everything). Did you do a 'make clean' before retrying? Done a make clean. Even done pkg_delete with all the XCB ports installed, and re-installed them, still hitting libtool: link: cannot find the library `/usr/local/lib/libxcb-aux.la' or unhandled argument `/usr/local/lib/libxcb-aux.la' For S*@ts'n'Giggles, I'm going to re-run the portmaster option mentioned in UPDATING (for the 2nd time, 1st time I used the portupgrade method) and see if there's any difference. ___ 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: Shared object libxcb-aux.so.0 not found, required by libxfsm-4.6.so.0 FreeBSD
On 01/17/12 16:50, Warren Block wrote: On Tue, 17 Jan 2012, Jimmie James wrote: On 01/17/12 15:39, Michael Johnson wrote: On Tue, Jan 17, 2012 at 3:04 PM, Jimmie James jimmie...@gmail.com mailto:jimmie...@gmail.com wrote: Even after following said instruction in UPDATING, libxcb-aux.so.0 does not get installed by any of the XCB ports It was replaced with libxcb-util.so.0. So it's the xfce4-wm port that's broken now, since it's still looking for the old libs. When applications fail because they're looking for a library that's been removed, following UPDATING doesn't help. Building xfce4-wm here just worked. It was rebuilt yesterday, too, as part of the portmaster xcb-util rebuild (which pretty much rebuilt everything). Did you do a 'make clean' before retrying? I am totally out of ideas now. After portupgrade -r xcb-util-0\* AND portmaster -R -r xcb-util-0 which rebuild pretty much everything, a pkg_libchk | grep -E xcb-.+.so | sort is still showing: libxfce4gui-4.8.1: /usr/local/lib/libglade/2.0/libxfce4.so misses libxcb-atom.so.1 libxfce4gui-4.8.1: /usr/local/lib/libglade/2.0/libxfce4.so misses libxcb-aux.so.0 libxfce4gui-4.8.1: /usr/local/lib/libglade/2.0/libxfce4.so misses libxcb-event.so.1 libxfce4gui-4.8.1: /usr/local/lib/libxfcegui4.so.7 misses libxcb-atom.so.1 libxfce4gui-4.8.1: /usr/local/lib/libxfcegui4.so.7 misses libxcb-aux.so.0 libxfce4gui-4.8.1: /usr/local/lib/libxfcegui4.so.7 misses libxcb-event.so.1 mousepad-0.2.16_8: /usr/local/bin/mousepad misses libxcb-atom.so.1 mousepad-0.2.16_8: /usr/local/bin/mousepad misses libxcb-aux.so.0 mousepad-0.2.16_8: /usr/local/bin/mousepad misses libxcb-event.so.1 squeeze-0.2.3_2: /usr/local/bin/squeeze misses libxcb-atom.so.1 squeeze-0.2.3_2: /usr/local/bin/squeeze misses libxcb-aux.so.0 squeeze-0.2.3_2: /usr/local/bin/squeeze misses libxcb-event.so.1 thunar-vfs-1.2.0_1: /usr/local/lib/libthunar-vfs-1.so.5 misses libxcb-atom.so.1 thunar-vfs-1.2.0_1: /usr/local/lib/libthunar-vfs-1.so.5 misses libxcb-aux.so.0 thunar-vfs-1.2.0_1: /usr/local/lib/libthunar-vfs-1.so.5 misses libxcb-event.so.1 xfburn-0.4.3_2: /usr/local/bin/xfburn misses libxcb-atom.so.1 xfburn-0.4.3_2: /usr/local/bin/xfburn misses libxcb-aux.so.0 xfburn-0.4.3_2: /usr/local/bin/xfburn misses libxcb-event.so.1 xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop misses libxcb-atom.so.1 xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop misses libxcb-aux.so.0 xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop misses libxcb-event.so.1 xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop-settings misses libxcb-atom.so.1 xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop-settings misses libxcb-aux.so.0 xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop-settings misses libxcb-event.so.1 xfce4-mailwatch-plugin-1.1.0_13: /usr/local/libexec/xfce4/panel-plugins/xfce4-mailwatch-plugin misses libxcb-atom.so.1 xfce4-mailwatch-plugin-1.1.0_13: /usr/local/libexec/xfce4/panel-plugins/xfce4-mailwatch-plugin misses libxcb-aux.so.0 xfce4-mailwatch-plugin-1.1.0_13: /usr/local/libexec/xfce4/panel-plugins/xfce4-mailwatch-plugin misses libxcb-event.so.1 xfce4-notes-plugin-1.7.7: /usr/local/bin/xfce4-notes-settings misses libxcb-atom.so.1 xfce4-notes-plugin-1.7.7: /usr/local/bin/xfce4-notes-settings misses libxcb-aux.so.0 xfce4-notes-plugin-1.7.7: /usr/local/bin/xfce4-notes-settings misses libxcb-event.so.1 xfce4-notifyd-0.2.2_1: /usr/local/bin/xfce4-notifyd-config misses libxcb-atom.so.1 xfce4-notifyd-0.2.2_1: /usr/local/bin/xfce4-notifyd-config misses libxcb-aux.so.0 xfce4-notifyd-0.2.2_1: /usr/local/bin/xfce4-notifyd-config misses libxcb-event.so.1 xfce4-notifyd-0.2.2_1: /usr/local/lib/xfce4/notifyd/xfce4-notifyd misses libxcb-atom.so.1 xfce4-notifyd-0.2.2_1: /usr/local/lib/xfce4/notifyd/xfce4-notifyd misses libxcb-aux.so.0 xfce4-notifyd-0.2.2_1: /usr/local/lib/xfce4/notifyd/xfce4-notifyd misses libxcb-event.so.1 xfce4-parole-0.2.0.6_3: /usr/local/bin/parole misses libxcb-atom.so.1 xfce4-parole-0.2.0.6_3: /usr/local/bin/parole misses libxcb-aux.so.0 xfce4-parole-0.2.0.6_3: /usr/local/bin/parole misses libxcb-event.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint-settings misses libxcb-atom.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint-settings misses libxcb-aux.so.0 xfce4-print-4.6.1_7: /usr/local/bin/xfprint-settings misses libxcb-event.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4 misses libxcb-atom.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4 misses libxcb-aux.so.0 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4 misses libxcb-event.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4-manager misses libxcb-atom.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4-manager misses libxcb-aux.so.0 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4-manager misses libxcb-event.so.1 xfce4-print-4.6.1_7: /usr/local/lib/libxfprint.so.0 misses libxcb-atom.so.1 xfce4-print-4.6.1_7: /usr/local/lib/libxfprint.so.0 misses libxcb-aux.so.0 xfce4-print-4.6.1_7: /usr/local/lib/libxfprint.so.0 misses libxcb-event.so.1
Re: Shared object libxcb-aux.so.0 not found, required by libxfsm-4.6.so.0 FreeBSD
On 01/17/12 16:50, Warren Block wrote: On Tue, 17 Jan 2012, Jimmie James wrote: On 01/17/12 15:39, Michael Johnson wrote: On Tue, Jan 17, 2012 at 3:04 PM, Jimmie James jimmie...@gmail.com mailto:jimmie...@gmail.com wrote: Even after following said instruction in UPDATING, libxcb-aux.so.0 does not get installed by any of the XCB ports It was replaced with libxcb-util.so.0. So it's the xfce4-wm port that's broken now, since it's still looking for the old libs. When applications fail because they're looking for a library that's been removed, following UPDATING doesn't help. Building xfce4-wm here just worked. It was rebuilt yesterday, too, as part of the portmaster xcb-util rebuild (which pretty much rebuilt everything). Did you do a 'make clean' before retrying? As a follow up to http://docs.freebsd.org/cgi/getmsg.cgi?fetch=592587+0+current/freebsd-questions After a few hours of rebuilding various xcb bits, I've gotten most to build, xfce4-wm builds and installs fine, the rest here, I'm not sure of. #pkg_libchk | grep -E xcb-.+.so | sort mousepad-0.2.16_8: /usr/local/bin/mousepad misses libxcb-atom.so.1 mousepad-0.2.16_8: /usr/local/bin/mousepad misses libxcb-aux.so.0 mousepad-0.2.16_8: /usr/local/bin/mousepad misses libxcb-event.so.1 xfburn-0.4.3_2: /usr/local/bin/xfburn misses libxcb-atom.so.1 xfburn-0.4.3_2: /usr/local/bin/xfburn misses libxcb-aux.so.0 xfburn-0.4.3_2: /usr/local/bin/xfburn misses libxcb-event.so.1 xfce4-mailwatch-plugin-1.1.0_13: /usr/local/libexec/xfce4/panel-plugins/xfce4-mailwatch-plugin misses libxcb-atom.so.1 xfce4-mailwatch-plugin-1.1.0_13: /usr/local/libexec/xfce4/panel-plugins/xfce4-mailwatch-plugin misses libxcb-aux.so.0 xfce4-mailwatch-plugin-1.1.0_13: /usr/local/libexec/xfce4/panel-plugins/xfce4-mailwatch-plugin misses libxcb-event.so.1 xfce4-notes-plugin-1.7.7: /usr/local/bin/xfce4-notes-settings misses libxcb-atom.so.1 xfce4-notes-plugin-1.7.7: /usr/local/bin/xfce4-notes-settings misses libxcb-aux.so.0 xfce4-notes-plugin-1.7.7: /usr/local/bin/xfce4-notes-settings misses libxcb-event.so.1 xfce4-parole-0.2.0.6_3: /usr/local/bin/parole misses libxcb-atom.so.1 xfce4-parole-0.2.0.6_3: /usr/local/bin/parole misses libxcb-aux.so.0 xfce4-parole-0.2.0.6_3: /usr/local/bin/parole misses libxcb-event.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint-settings misses libxcb-atom.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint-settings misses libxcb-aux.so.0 xfce4-print-4.6.1_7: /usr/local/bin/xfprint-settings misses libxcb-event.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4 misses libxcb-atom.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4 misses libxcb-aux.so.0 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4 misses libxcb-event.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4-manager misses libxcb-atom.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4-manager misses libxcb-aux.so.0 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4-manager misses libxcb-event.so.1 xfce4-print-4.6.1_7: /usr/local/lib/libxfprint.so.0 misses libxcb-atom.so.1 xfce4-print-4.6.1_7: /usr/local/lib/libxfprint.so.0 misses libxcb-aux.so.0 xfce4-print-4.6.1_7: /usr/local/lib/libxfprint.so.0 misses libxcb-event.so.1 xfce4-print-4.6.1_7: /usr/local/lib/xfce4/xfprint-plugins/bsdlpr_plugin.so misses libxcb-atom.so.1 xfce4-print-4.6.1_7: /usr/local/lib/xfce4/xfprint-plugins/bsdlpr_plugin.so misses libxcb-aux.so.0 xfce4-print-4.6.1_7: /usr/local/lib/xfce4/xfprint-plugins/bsdlpr_plugin.so misses libxcb-event.so.1 xfce4-weather-plugin-0.7.4_1: /usr/local/libexec/xfce4/panel-plugins/xfce4-weather-plugin misses libxcb-atom.so.1 xfce4-weather-plugin-0.7.4_1: /usr/local/libexec/xfce4/panel-plugins/xfce4-weather-plugin misses libxcb-aux.so.0 xfce4-weather-plugin-0.7.4_1: /usr/local/libexec/xfce4/panel-plugins/xfce4-weather-plugin misses libxcb-event.so.1 I do know the missing libs are living in /usr/local/lib/compat/pkg/ (though, I don't understand the dates listed) #ls -ali /usr/local/lib/compat/pkg/libxcb* 4404817 -rwxr-xr-x 1 root wheel 15146 Oct 20 2008 /usr/local/lib/compat/pkg/libxcb-atom.so.0 4405755 -rwxr-xr-x 1 root wheel 16291 Dec 20 01:29 /usr/local/lib/compat/pkg/libxcb-atom.so.1 4405756 -rwxr-xr-x 1 root wheel 12079 Dec 20 01:29 /usr/local/lib/compat/pkg/libxcb-aux.so.0 4404820 -rwxr-xr-x 1 root wheel6812 Oct 20 2008 /usr/local/lib/compat/pkg/libxcb-event.so.0 4405813 -rwxr-xr-x 1 root wheel 12878 Dec 20 01:29 /usr/local/lib/compat/pkg/libxcb-event.so.1 4404822 -rwxr-xr-x 1 root wheel 17302 Oct 20 2008 /usr/local/lib/compat/pkg/libxcb-icccm.so.0 4405815 -rwxr-xr-x 1 root wheel 1 Dec 20 01:29 /usr/local/lib/compat/pkg/libxcb-icccm.so.1 4405816 -rwxr-xr-x 1 root wheel 16678 Dec 20 01:30 /usr/local/lib/compat/pkg/libxcb-image.so.0 4404857 -rwxr-xr-x 1 root wheel8644 Feb 7 2009 /usr/local/lib/compat/pkg/libxcb-keysyms.so.0 4405817 -rwxr-xr-x 1 root wheel9126 Dec 20 01:30 /usr/local/lib/compat/pkg/libxcb
Re: Shared object libxcb-aux.so.0 not found, required by libxfsm-4.6.so.0 FreeBSD [SOLVED]
Sorry for top posting in this message, but one reboot and a ldconfig -R allows everything to be rebuilt. Not sure which was the key here, but for others, I'd try ldconfig -R first. Not sure why portupgrade and portmaster failed though. On 01/18/12 00:11, Jimmie James wrote: On 01/17/12 16:50, Warren Block wrote: On Tue, 17 Jan 2012, Jimmie James wrote: On 01/17/12 15:39, Michael Johnson wrote: On Tue, Jan 17, 2012 at 3:04 PM, Jimmie James jimmie...@gmail.com mailto:jimmie...@gmail.com wrote: Even after following said instruction in UPDATING, libxcb-aux.so.0 does not get installed by any of the XCB ports It was replaced with libxcb-util.so.0. So it's the xfce4-wm port that's broken now, since it's still looking for the old libs. When applications fail because they're looking for a library that's been removed, following UPDATING doesn't help. Building xfce4-wm here just worked. It was rebuilt yesterday, too, as part of the portmaster xcb-util rebuild (which pretty much rebuilt everything). Did you do a 'make clean' before retrying? As a follow up to http://docs.freebsd.org/cgi/getmsg.cgi?fetch=592587+0+current/freebsd-questions After a few hours of rebuilding various xcb bits, I've gotten most to build, xfce4-wm builds and installs fine, the rest here, I'm not sure of. #pkg_libchk | grep -E xcb-.+.so | sort mousepad-0.2.16_8: /usr/local/bin/mousepad misses libxcb-atom.so.1 mousepad-0.2.16_8: /usr/local/bin/mousepad misses libxcb-aux.so.0 mousepad-0.2.16_8: /usr/local/bin/mousepad misses libxcb-event.so.1 xfburn-0.4.3_2: /usr/local/bin/xfburn misses libxcb-atom.so.1 xfburn-0.4.3_2: /usr/local/bin/xfburn misses libxcb-aux.so.0 xfburn-0.4.3_2: /usr/local/bin/xfburn misses libxcb-event.so.1 xfce4-mailwatch-plugin-1.1.0_13: /usr/local/libexec/xfce4/panel-plugins/xfce4-mailwatch-plugin misses libxcb-atom.so.1 xfce4-mailwatch-plugin-1.1.0_13: /usr/local/libexec/xfce4/panel-plugins/xfce4-mailwatch-plugin misses libxcb-aux.so.0 xfce4-mailwatch-plugin-1.1.0_13: /usr/local/libexec/xfce4/panel-plugins/xfce4-mailwatch-plugin misses libxcb-event.so.1 xfce4-notes-plugin-1.7.7: /usr/local/bin/xfce4-notes-settings misses libxcb-atom.so.1 xfce4-notes-plugin-1.7.7: /usr/local/bin/xfce4-notes-settings misses libxcb-aux.so.0 xfce4-notes-plugin-1.7.7: /usr/local/bin/xfce4-notes-settings misses libxcb-event.so.1 xfce4-parole-0.2.0.6_3: /usr/local/bin/parole misses libxcb-atom.so.1 xfce4-parole-0.2.0.6_3: /usr/local/bin/parole misses libxcb-aux.so.0 xfce4-parole-0.2.0.6_3: /usr/local/bin/parole misses libxcb-event.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint-settings misses libxcb-atom.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint-settings misses libxcb-aux.so.0 xfce4-print-4.6.1_7: /usr/local/bin/xfprint-settings misses libxcb-event.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4 misses libxcb-atom.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4 misses libxcb-aux.so.0 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4 misses libxcb-event.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4-manager misses libxcb-atom.so.1 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4-manager misses libxcb-aux.so.0 xfce4-print-4.6.1_7: /usr/local/bin/xfprint4-manager misses libxcb-event.so.1 xfce4-print-4.6.1_7: /usr/local/lib/libxfprint.so.0 misses libxcb-atom.so.1 xfce4-print-4.6.1_7: /usr/local/lib/libxfprint.so.0 misses libxcb-aux.so.0 xfce4-print-4.6.1_7: /usr/local/lib/libxfprint.so.0 misses libxcb-event.so.1 xfce4-print-4.6.1_7: /usr/local/lib/xfce4/xfprint-plugins/bsdlpr_plugin.so misses libxcb-atom.so.1 xfce4-print-4.6.1_7: /usr/local/lib/xfce4/xfprint-plugins/bsdlpr_plugin.so misses libxcb-aux.so.0 xfce4-print-4.6.1_7: /usr/local/lib/xfce4/xfprint-plugins/bsdlpr_plugin.so misses libxcb-event.so.1 xfce4-weather-plugin-0.7.4_1: /usr/local/libexec/xfce4/panel-plugins/xfce4-weather-plugin misses libxcb-atom.so.1 xfce4-weather-plugin-0.7.4_1: /usr/local/libexec/xfce4/panel-plugins/xfce4-weather-plugin misses libxcb-aux.so.0 xfce4-weather-plugin-0.7.4_1: /usr/local/libexec/xfce4/panel-plugins/xfce4-weather-plugin misses libxcb-event.so.1 I do know the missing libs are living in /usr/local/lib/compat/pkg/ (though, I don't understand the dates listed) #ls -ali /usr/local/lib/compat/pkg/libxcb* 4404817 -rwxr-xr-x 1 root wheel 15146 Oct 20 2008 /usr/local/lib/compat/pkg/libxcb-atom.so.0 4405755 -rwxr-xr-x 1 root wheel 16291 Dec 20 01:29 /usr/local/lib/compat/pkg/libxcb-atom.so.1 4405756 -rwxr-xr-x 1 root wheel 12079 Dec 20 01:29 /usr/local/lib/compat/pkg/libxcb-aux.so.0 4404820 -rwxr-xr-x 1 root wheel 6812 Oct 20 2008 /usr/local/lib/compat/pkg/libxcb-event.so.0 4405813 -rwxr-xr-x 1 root wheel 12878 Dec 20 01:29 /usr/local/lib/compat/pkg/libxcb-event.so.1 4404822 -rwxr-xr-x 1 root wheel 17302 Oct 20 2008 /usr/local/lib/compat/pkg/libxcb-icccm.so.0 4405815 -rwxr-xr-x 1 root wheel 1 Dec 20 01:29 /usr/local/lib/compat/pkg/libxcb-icccm.so.1 4405816 -rwxr-xr-x 1 root wheel 16678 Dec 20 01:30 /usr/local/lib/compat/pkg/libxcb
Shared object libxcb-aux.so.0 not found, required by libxfsm-4.6.so.0 FreeBSD
Dear folks, I had a FreeBSD 9.0 BETA 2 Machine I was happily running since the release and only updated ports via portmaster -a, and now since Fedora 9 has officially been released, I ran make buildworld, make buildkernel, make installkernel and mergemaster -i, and make installworld and now X does not work, I get error in subject Shared object libxcb-aux.so.0 not found, required by libxfsm-4.6.so.0 FreeBSD any ideas/suggestions for a fix? Thanks in advance, Antonio ___ 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
how to tell that a file exists and is not 0-len?
guys, access(filenamewithpath, F_OK) returned true as Zero if i have access to it. what do i use in C to tell me that a file is not empty? fstat? or is there something more common? thanks, gary -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Journey Toward the Dawn, E-Book: http://www.thought.org The 8.57a release of Jottings: http://jottings.thought.org Twenty-five years of service to the Unix community. ___ 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: how to tell that a file exists and is not 0-len?
On 28/12/2011 23:50, Gary Kline wrote: access(filenamewithpath, F_OK) returned true as Zero if i have access to it. what do i use in C to tell me that a file is not empty? fstat? or is there something more common? stat(2) which uses the file path -- unless you have an open file descriptor on the file, in which case use fstat(2). Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
RE: how to tell that a file exists and is not 0-len?
-Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- questi...@freebsd.org] On Behalf Of Gary Kline Sent: Wednesday, December 28, 2011 3:50 PM To: FreeBSD Mailing List Subject: how to tell that a file exists and is not 0-len? guys, access(filenamewithpath, F_OK) returned true as Zero if i have access to it. what do i use in C to tell me that a file is not empty? This should do: #include sys/types.h #include sys/stat.h ... struct stat sb; off_t size; if (!lstat(pathbuf, sb)) size = sb.st_size; ... -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ 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
+ahcich0: Timeout on slot 10 port 0
Could someone much more knowledgeable please give me a hint as to what might I look for and what rs and tfd means. I /think/ I am reading the OS is unhappy with the JMB363 chip (see second grep). TIA +ahcich0: is cs 0400 ss rs 0400 tfd 2451 serr cmd 1000ca17 I have a BluRay drive in here but it is connected to cd0, or: iirc grep cd0 /var/run/dmesg.boot cd0 at ahcich0 bus 0 scbus0 target 0 lun 0 cd0: HL-DT-ST BD-RE BH10LS30 1.00 Removable CD-ROM SCSI-0 device cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed cd0 at ahcich0 bus 0 scbus0 target 0 lun 0 cd0: HL-DT-ST BD-RE BH10LS30 1.00 Removable CD-ROM SCSI-0 device cd0: 150.000MB/s transfers (SATA 1.x, UDMA6, ATAPI 12bytes, PIO 8192bytes) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed cd0 at ahcich0 bus 0 scbus0 target 0 lun 0 cd0: HL-DT-ST BD-RE BH10LS30 1.00 Removable CD-ROM SCSI-0 device cd0: 150.000MB/s transfers (SATA 1.x, UDMA6, ATAPI 12bytes, PIO 8192bytes) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed iirc grep ahci /var/run/dmesg.boot ahcich8: [ITHREAD] ahcich9: AHCI channel at channel 1 on ahci1 ahcich9: [ITHREAD] ahci2: JMicron JMB363 AHCI SATA controller on atapci2 ahci2: [ITHREAD] ahci2: AHCI v1.00 with 2 3Gbps ports, Port Multiplier supported ahcich10: AHCI channel at channel 0 on ahci2 ahcich10: [ITHREAD] ahcich11: AHCI channel at channel 1 on ahci2 ahcich11: [ITHREAD] ahci3: Intel ICH10 AHCI SATA controller port 0xf900-0xf907,0xf800-0xf803,0xf700-0xf707,0xf600-0xf603,0xf500-0xf51f mem 0xfbffc000-0xfbffc7ff irq 19 at device 31.2 on pci0 ahci3: [ITHREAD] ahci3: AHCI v1.20 with 6 3Gbps ports, Port Multiplier supported ahcich12: AHCI channel at channel 0 on ahci3 ahcich12: [ITHREAD] ahcich13: AHCI channel at channel 1 on ahci3 ahcich13: [ITHREAD] ahcich14: AHCI channel at channel 2 on ahci3 ahcich14: [ITHREAD] ahcich15: AHCI channel at channel 3 on ahci3 ahcich15: [ITHREAD] ahcich16: AHCI channel at channel 4 on ahci3 ahcich16: [ITHREAD] ahcich17: AHCI channel at channel 5 on ahci3 ahcich17: [ITHREAD] ahcich7: Poll timeout on slot 0 port 0 ahcich7: is cs 0001 ss rs 0001 tfd 50 serr cmd 10004016 ada0 at ahcich9 bus 0 scbus10 target 0 lun 0 ada1 at ahcich12 bus 0 scbus13 target 0 lun 0 ada2 at ahcich13 bus 0 scbus14 target 0 lun 0 ada3 at ahcich14 bus 0 scbus15 target 0 lun 0 ada4 at ahcich15 bus 0 scbus16 target 0 lun 0 ada5 at ahcich16 bus 0 scbus17 target 0 lun 0 ada6 at ahcich17 bus 0 scbus18 target 0 lun 0 cd0 at ahcich0 bus 0 scbus0 target 0 lun 0 ahcich0: Timeout on slot 3 port 0 ahcich0: is cs 0008 ss rs 0008 tfd 2451 serr cmd 1000c317 ahcich0: Timeout on slot 3 port 0 ahcich0: is cs 0008 ss rs 0008 tfd 2451 serr cmd 1000c317 ahcich0: Timeout on slot 3 port 0 ahcich0: is cs 0008 ss rs 0008 tfd 2451 serr cmd 1000c317 ahcich0: Timeout on slot 3 port 0 ahcich0: is cs 0008 ss rs 0008 tfd 2451 serr cmd 1000c317 ahci0: Marvell 88SE9128 AHCI SATA controller port 0xdf00-0xdf07,0xde00-0xde03,0xdd00-0xdd07,0xdc00-0xdc03,0xdb00-0xdb0f mem 0xfb5ff000-0xfb5ff7ff irq 16 at device 0.0 on pci1 ahci0: [ITHREAD] ahci0: AHCI v1.20 with 8 6Gbps ports, Port Multiplier not supported ahcich0: AHCI channel at channel 0 on ahci0 ahcich0: [ITHREAD] ahcich1: AHCI channel at channel 1 on ahci0 ahcich1: [ITHREAD] ahcich2: AHCI channel at channel 2 on ahci0 ahcich2: [ITHREAD] ahcich3: AHCI channel at channel 3 on ahci0 ahcich3: [ITHREAD] ahcich4: AHCI channel at channel 4 on ahci0 ahcich4: [ITHREAD] ahcich5: AHCI channel at channel 5 on ahci0 ahcich5: [ITHREAD] ahcich6: AHCI channel at channel 6 on ahci0 ahcich6: [ITHREAD] ahcich7: AHCI channel at channel 7 on ahci0 ahcich7: [ITHREAD] ahci1: JMicron JMB363 AHCI SATA controller mem 0xfbbfe000-0xfbbf irq 17 at device 0.0 on pci8 ahci1: [ITHREAD] ahci1: AHCI v1.00 with 2 3Gbps ports, Port Multiplier supported ahcich8: AHCI channel at channel 0 on ahci1 ahcich8: [ITHREAD] ahcich9: AHCI channel at channel 1 on ahci1 ahcich9: [ITHREAD] ahci2: JMicron JMB363 AHCI SATA controller on atapci2 ahci2: [ITHREAD] ahci2: AHCI v1.00 with 2 3Gbps ports, Port Multiplier supported ahcich10: AHCI channel at channel 0 on ahci2 ahcich10: [ITHREAD] ahcich11: AHCI channel at channel 1 on ahci2 ahcich11: [ITHREAD] ahci3: Intel ICH10 AHCI SATA controller port 0xf900-0xf907,0xf800-0xf803,0xf700-0xf707,0xf600-0xf603,0xf500-0xf51f mem 0xfbffc000-0xfbffc7ff irq 19 at device 31.2 on pci0 ahci3: [ITHREAD] ahci3: AHCI v1.20 with 6 3Gbps ports, Port Multiplier supported ahcich12: AHCI channel at channel 0 on ahci3 ahcich12: [ITHREAD] ahcich13: AHCI channel at channel 1 on ahci3 ahcich13: [ITHREAD] ahcich14: AHCI channel at channel 2 on ahci3 ahcich14: [ITHREAD] ahcich15: AHCI channel
Re: portmaster -r libnotify-0 problems
Hi Mathew, On 09/09/2011 15:13, Scott Ballantyne wrote: I've been trying to update libnotify and libproxy following the instructions in UPDATING, which is to do portmaster -r libnotify-0 This trys to install ghostscript9, and fails. Apparently ghostscript9 conflicts with ghostscript8-8.71_6, which presumably is the reason for the failure. Could someone help me resolve this? The obvious solution of pkg_delete ghostscript8-8.71_6 doesn't work, because too many installed ports depend on ghostscript8-8.71_6. There are two approaches you might take here. Either * replace ghostscript8 with ghostscript9 or * work out why libnotify triggers a dependency on ghostscript9 and try and make it use ghostscript8 (or nothing) instead. The first is a relatively mechanical process, which should work fine from the point of view of doing all the port wrangling, but might result in further ghostscript8 vs ghostscript9 problems down the line. Just run: # portmaster -o print/ghostscript9 ghostscript8- That will change the dependency settings in your /var/db/pkg directory, which may or may not be appropriate for all ghostscript dependent ports, and indeed some may not work at all. (Although I rather doubt the simply not-working thing: functionality between those versions hasn't changed much at all.) The second is a more satisfying fix. Lets see... Try defining WITH_GHOSTSCRIPT_VER=8 in /etc/make.conf (the default is 9 nowadays) -- then try reinstalling libnotify according to the instructions in UPDATING. Read /usr/ports/Mk/bsd.port.mk for the details -- search for GHOSTSCRIPT to find the relevant bits. Thanks so much, I am in your debt. However, I also feel that I am in maze of twisty little passages, all different. The next step here is to portmaster -r libproxy-0, where I get: --- === Currently installed version: libproxy-0.4.6 === Port directory: /usr/ports/net/libproxy === Gathering distinfo list for installed ports === Launching 'make checksum' for net/libproxy in background === Gathering dependency list for net/libproxy from ports === Initial dependency check complete for net/libproxy === Checking ports that depend on libproxy-0.4.6 === Launching child to reinstall alacarte-0.13.2_1 libproxy-0.4.6 alacarte-0.13.2_1 === Port directory: /usr/ports/deskutils/alacarte === No DISTINFO_FILE in /usr/ports/x11-themes/gnome-art === Aborting update Terminated Terminated === Update for alacarte-0.13.2_1 failed === Aborting update -- gnome-art is peculiar. There is nothing in that directory but the work directory, no makefile or anything. And nothing I can find in UPDATE about alacarte or gnome-art. Any further thoughts, if you have time? Thanks again, Scott ___ 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: portmaster -r libnotify-0 problems
On 10/09/2011 16:12, Scott Ballantyne wrote: gnome-art is peculiar. There is nothing in that directory but the work directory, no makefile or anything. And nothing I can find in UPDATE about alacarte or gnome-art. Any further thoughts, if you have time? That is an ex-port. lucid-nonsense:/usr/ports:# grep gnome-art MOVED x11-themes/gnome-art||2011-08-02|Has expired: Upcoming ruby-gnome removes dependencies Kicked the bucket, shuffled off this mortal coil, run down the curtain and joined the bleeding choir invisible. Suggest you update your ports tree using csup(1) or portsnap(1) -- if necessary by blowing away what you already have under /usr/ports and starting from scratch. Seems that your current tree is in an inconsistent state. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: portmaster -r libnotify-0 problems
On 10/09/2011 16:12, Scott Ballantyne wrote: gnome-art is peculiar. There is nothing in that directory but the work directory, no makefile or anything. And nothing I can find in UPDATE about alacarte or gnome-art. =20 Any further thoughts, if you have time? That is an ex-port. lucid-nonsense:/usr/ports:# grep gnome-art MOVED x11-themes/gnome-art||2011-08-02|Has expired: Upcoming ruby-gnome removes dependencies Kicked the bucket, shuffled off this mortal coil, run down the curtain and joined the bleeding choir invisible. Suggest you update your ports tree using csup(1) or portsnap(1) -- if necessary by blowing away what you already have under /usr/ports and starting from scratch. Seems that your current tree is in an inconsistent state. Thanks again, Mathew. I csuped already, but will nuke the ports and start again. Thanks again so much for your generous help. Scott -- s...@ssr.com ___ 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
portmaster -r libnotify-0 problems
Hi, I've been trying to update libnotify and libproxy following the instructions in UPDATING, which is to do portmaster -r libnotify-0 This trys to install ghostscript9, and fails. Apparently ghostscript9 conflicts with ghostscript8-8.71_6, which presumably is the reason for the failure. Could someone help me resolve this? The obvious solution of pkg_delete ghostscript8-8.71_6 doesn't work, because too many installed ports depend on ghostscript8-8.71_6. Thanks in advance, Scott -- s...@ssr.com ___ 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: portmaster -r libnotify-0 problems
On 09/09/2011 15:13, Scott Ballantyne wrote: I've been trying to update libnotify and libproxy following the instructions in UPDATING, which is to do portmaster -r libnotify-0 This trys to install ghostscript9, and fails. Apparently ghostscript9 conflicts with ghostscript8-8.71_6, which presumably is the reason for the failure. Could someone help me resolve this? The obvious solution of pkg_delete ghostscript8-8.71_6 doesn't work, because too many installed ports depend on ghostscript8-8.71_6. There are two approaches you might take here. Either * replace ghostscript8 with ghostscript9 or * work out why libnotify triggers a dependency on ghostscript9 and try and make it use ghostscript8 (or nothing) instead. The first is a relatively mechanical process, which should work fine from the point of view of doing all the port wrangling, but might result in further ghostscript8 vs ghostscript9 problems down the line. Just run: # portmaster -o print/ghostscript9 ghostscript8- That will change the dependency settings in your /var/db/pkg directory, which may or may not be appropriate for all ghostscript dependent ports, and indeed some may not work at all. (Although I rather doubt the simply not-working thing: functionality between those versions hasn't changed much at all.) The second is a more satisfying fix. Lets see... Try defining WITH_GHOSTSCRIPT_VER=8 in /etc/make.conf (the default is 9 nowadays) -- then try reinstalling libnotify according to the instructions in UPDATING. Read /usr/ports/Mk/bsd.port.mk for the details -- search for GHOSTSCRIPT to find the relevant bits. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: Phenom II 975 BE shows 0 celsius
on 01/08/2011 03:28 Mario Lobo said the following: Hi to all In my desktop machine, I had an AM2+ ASROCK mobo with Phenom II 955 BE that showed each core temperature perfectly under FBSD 8-STABLE, via dev.cpu.x.temp. amdtemp.ko loaded. Unfortunately this Mobo died and only found AM3 boards for which my phenom 955 doesn't fit. So I got an ASUS M4A88T-V EVO with a Phenom II 975 BE. Funny thing. An AM3 phenom II fits on an AM2 board but an AM3 board doesn't accept an AM2/AM2+ phenom II :(. Anyway, now, under the very same system, it shows 0 degrees on dev.cpu.x.temp for all cores. Sorry, I've got lost in all the config changes. So what system do you have now? Can please also provide CPU-related information from dmesg? I've been looking through k8temp and amdtemp src code. I am definitely not sure of this but I believe something might have happened to those: From k8temp.h K10_THERM_REG 0xa4 K10_THERMTRIP_REG 0xe4 K10_CURTMP(val)(((val) 21) 0xfff) K10_THERMTRIP(val) ((val 1) 1) From amdtemp.c /* * Register control (K8 family) */ #define AMDTEMP_REG0F 0xe4 #define AMDTEMP_REG_SELSENSOR 0x40 #define AMDTEMP_REG_SELCORE 0x04 /* * Register control (K10 K11) family */ #define AMDTEMP_REG 0xa4 Output of k8temp -dn: CPUID: Vendor: AuthenticAMD, 0x100f43: Model=04 Family=f+1 Stepping=3 Advanced Power Management=0x1f9 Temperature sensor: Yes Frequency ID control: No Voltage ID control: No THERMTRIP support: Yes HW Thermal control: Yes SW Thermal control: Yes 100MHz multipliers: Yes HW P-State control: Yes TSC Invariant: Yes Temp=c0fef ThermTrip=1fc00c30 0 I keep a small win7 partition to test little things like this and see if the same thing happens there, and it doesn't, so I concluded that the sensors are there and are working. One thing is worth noting though. I have used a free gadget that shows activity/temp for each core. It worked fine with the previous MB/CPU.That ALSO stopped working with this new MB. Like FBSD, it shows 0 degrees for any core too, although it correctly displays each core load. Most likely that gadget just re-uses OS-provided information. The only windows tool that correctly shows the temperature are the ASUS tools that came with the mobo. Other than that, everything is working fine! The only thing I had to fix was the fstab ada location. I know this is not a big thing but I got accustomed to keeping an eye on those temperatures. I have googled for a few days now searching for Thermal register address or offsets for the Phenom II 975 BE, or anything related to this problem and found nothing. Every search on AMD site was fruitless. I could not find a single bit of tech info on this processor there, or any other tech info for that matter. http://support.amd.com/us/Processor_TechDocs/31116.pdf Would any one have any pointers/clues/suggestions on this? I would try to add some printfs (or used dtrace - whichever is easier for you) to see what's going on. Or you can even use pciconf to directly sneak a peek at what's reported by the hardware, e.g.: # pciconf -r pci0:0:24:3 0xa4 1c881880 You can read the BKDG to see how to interpret the value - search for F3xA4. See F3xE4 for offset calculation. Hopefully you should be able to see if hardware reports sane value and how the amdtemp ends up reporting 0°C. -- Andriy Gapon ___ 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: Phenom II 975 BE shows 0 celsius
On Monday 01 August 2011 10:14 am, Andriy Gapon wrote:
on 01/08/2011 03:28 Mario Lobo said the following:
Hi to all
In my desktop machine, I had an AM2+ ASROCK mobo with Phenom II
955 BE that showed each core temperature perfectly under FBSD
8-STABLE, via dev.cpu.x.temp. amdtemp.ko loaded.
Unfortunately this Mobo died and only found AM3 boards for which
my phenom 955 doesn't fit. So I got an ASUS M4A88T-V EVO with a
Phenom II 975 BE.
Funny thing. An AM3 phenom II fits on an AM2 board but an AM3
board doesn't accept an AM2/AM2+ phenom II :(.
Anyway, now, under the very same system, it shows 0 degrees on
dev.cpu.x.temp for all cores.
Sorry, I've got lost in all the config changes. So what system do
you have now? Can please also provide CPU-related information from
dmesg?
I've been looking through k8temp and amdtemp src code. I am
definitely not sure of this but I believe something might have
happened to those:
From k8temp.h
K10_THERM_REG 0xa4
K10_THERMTRIP_REG 0xe4
K10_CURTMP(val)(((val) 21) 0xfff)
K10_THERMTRIP(val) ((val 1) 1)
From amdtemp.c
/*
* Register control (K8 family)
*/
#define AMDTEMP_REG0F 0xe4
#define AMDTEMP_REG_SELSENSOR 0x40
#define AMDTEMP_REG_SELCORE 0x04
/*
* Register control (K10 K11) family
*/
#define AMDTEMP_REG 0xa4
Output of k8temp -dn:
CPUID: Vendor: AuthenticAMD, 0x100f43: Model=04 Family=f+1
Stepping=3 Advanced Power Management=0x1f9
Temperature sensor: Yes
Frequency ID control: No
Voltage ID control: No
THERMTRIP support: Yes
HW Thermal control: Yes
SW Thermal control: Yes
100MHz multipliers: Yes
HW P-State control: Yes
TSC Invariant: Yes
Temp=c0fef
ThermTrip=1fc00c30
0
I keep a small win7 partition to test little things like this and
see if the same thing happens there, and it doesn't, so I
concluded that the sensors are there and are working.
One thing is worth noting though. I have used a free gadget that
shows activity/temp for each core. It worked fine with the
previous MB/CPU.That ALSO stopped working with this new MB. Like
FBSD, it shows 0 degrees for any core too, although it correctly
displays each core load.
Most likely that gadget just re-uses OS-provided information.
The only windows tool that correctly shows the temperature are
the ASUS tools that came with the mobo.
Other than that, everything is working fine! The only thing I had
to fix was the fstab ada location.
I know this is not a big thing but I got accustomed to keeping an
eye on those temperatures.
I have googled for a few days now searching for Thermal register
address or offsets for the Phenom II 975 BE, or anything related
to this problem and found nothing. Every search on AMD site was
fruitless. I could not find a single bit of tech info on this
processor there, or any other tech info for that matter.
http://support.amd.com/us/Processor_TechDocs/31116.pdf
Would any one have any pointers/clues/suggestions on this?
I would try to add some printfs (or used dtrace - whichever is
easier for you) to see what's going on. Or you can even use
pciconf to directly sneak a peek at what's reported by the
hardware, e.g.:
# pciconf -r pci0:0:24:3 0xa4
1c881880
You can read the BKDG to see how to interpret the value - search
for F3xA4. See F3xE4 for offset calculation.
Hopefully you should be able to see if hardware reports sane value
and how the amdtemp ends up reporting 0�C.
I gave up the DiodeOffset recently because a lot of BIOSes do not set
any meaningful values. Instead, I added a tunable for that. Please
see the attached patch, which is also available from here:
http://people.freebsd.org/~jkim/amdtemp.diff
Jung-uk Kim
Index: share/man/man4/amdtemp.4
===
--- share/man/man4/amdtemp.4(revision 221788)
+++ share/man/man4/amdtemp.4(working copy)
@@ -25,12 +25,14 @@
.\
.\ $FreeBSD$
.\
-.Dd April 8, 2008
+.Dd May 11, 2011
.Dt AMDTEMP 4
.Os
.Sh NAME
.Nm amdtemp
-.Nd device driver for AMD K8, K10 and K11 on-die digital thermal sensor
+.Nd device driver for
+.Tn AMD
+processor on-die digital thermal sensor
.Sh SYNOPSIS
To compile this driver into the kernel,
place the following line in your
@@ -49,22 +51,48 @@ amdtemp_load=YES
The
.Nm
driver provides support for the on-die digital thermal sensor present
-in AMD K8, K10 and K11 processors.
+in
+.Tn AMD
+Family 0Fh, 10h, 11h, 12h, and 14h processors.
.Pp
-For the K8 family, the
+For Family 0Fh processors, the
.Nm
-driver reports each core's temperature through a sysctl node in the
-corresponding CPU devices's sysctl tree, named
-.Va dev.amdtemp.%d.sensor{0,1}.core{0,1} .
+driver reports each core's temperature through sysctl nodes, named
+.Va dev.amdtemp.%d.core{0,1}.sensor{0,1} .
The driver also
Re: Phenom II 975 BE shows 0 celsius
On Sunday 31 July 2011 08:28 pm, Mario Lobo wrote: Hi to all In my desktop machine, I had an AM2+ ASROCK mobo with Phenom II 955 BE that showed each core temperature perfectly under FBSD 8-STABLE, via dev.cpu.x.temp. amdtemp.ko loaded. Unfortunately this Mobo died and only found AM3 boards for which my phenom 955 doesn't fit. So I got an ASUS M4A88T-V EVO with a Phenom II 975 BE. Funny thing. An AM3 phenom II fits on an AM2 board but an AM3 board doesn't accept an AM2/AM2+ phenom II :(. Anyway, now, under the very same system, it shows 0 degrees on dev.cpu.x.temp for all cores. I've been looking through k8temp and amdtemp src code. I am definitely not sure of this but I believe something might have happened to those: From k8temp.h K10_THERM_REG 0xa4 K10_THERMTRIP_REG 0xe4 K10_CURTMP(val)(((val) 21) 0xfff) K10_THERMTRIP(val) ((val 1) 1) From amdtemp.c /* * Register control (K8 family) */ #define AMDTEMP_REG0F 0xe4 #define AMDTEMP_REG_SELSENSOR 0x40 #define AMDTEMP_REG_SELCORE 0x04 /* * Register control (K10 K11) family */ #define AMDTEMP_REG 0xa4 Output of k8temp -dn: CPUID: Vendor: AuthenticAMD, 0x100f43: Model=04 Family=f+1 Stepping=3 Advanced Power Management=0x1f9 Temperature sensor: Yes Frequency ID control: No Voltage ID control: No THERMTRIP support: Yes HW Thermal control: Yes SW Thermal control: Yes 100MHz multipliers: Yes HW P-State control: Yes TSC Invariant: Yes Temp=c0fef ThermTrip=1fc00c30 0 I keep a small win7 partition to test little things like this and see if the same thing happens there, and it doesn't, so I concluded that the sensors are there and are working. One thing is worth noting though. I have used a free gadget that shows activity/temp for each core. It worked fine with the previous MB/CPU.That ALSO stopped working with this new MB. Like FBSD, it shows 0 degrees for any core too, although it correctly displays each core load. The only windows tool that correctly shows the temperature are the ASUS tools that came with the mobo. FYI, FreeBSD has aibs(4) (or acpi_aiboost(4) depending on your FreeBSD version) and it does essentially the same thing. Jung-uk Kim Other than that, everything is working fine! The only thing I had to fix was the fstab ada location. I know this is not a big thing but I got accustomed to keeping an eye on those temperatures. I have googled for a few days now searching for Thermal register address or offsets for the Phenom II 975 BE, or anything related to this problem and found nothing. Every search on AMD site was fruitless. I could not find a single bit of tech info on this processor there, or any other tech info for that matter. Would any one have any pointers/clues/suggestions on this? Thanks, ___ 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: Phenom II 975 BE shows 0 celsius
On Sun, Jul 31, 2011 at 09:28:29PM -0300 I heard the voice of Mario Lobo, and lo! it spake thus: Unfortunately this Mobo died and only found AM3 boards for which my phenom 955 doesn't fit. Not that it helps you now, but the 955 _is_ perfectly compatible with AM3. It's only the initial 920 and 940 that were AM2-only. -- Matthew Fuller (MF4839) | fulle...@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ 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: Phenom II 975 BE shows 0 celsius
On Monday 01 August 2011 15:52:30 Matthew D. Fuller wrote: On Sun, Jul 31, 2011 at 09:28:29PM -0300 I heard the voice of Mario Lobo, and lo! it spake thus: Unfortunately this Mobo died and only found AM3 boards for which my phenom 955 doesn't fit. Not that it helps you now, but the 955 _is_ perfectly compatible with AM3. It's only the initial 920 and 940 that were AM2-only. I was just following this: http://support.amd.com/us/kbarticles/Pages/CPU-6-socket-am2-plus-phenom-ii- compatibility-alert.aspx -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio YET!!] (99% winblows FREE) ___ 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
Phenom II 975 BE shows 0 celsius
Hi to all In my desktop machine, I had an AM2+ ASROCK mobo with Phenom II 955 BE that showed each core temperature perfectly under FBSD 8-STABLE, via dev.cpu.x.temp. amdtemp.ko loaded. Unfortunately this Mobo died and only found AM3 boards for which my phenom 955 doesn't fit. So I got an ASUS M4A88T-V EVO with a Phenom II 975 BE. Funny thing. An AM3 phenom II fits on an AM2 board but an AM3 board doesn't accept an AM2/AM2+ phenom II :(. Anyway, now, under the very same system, it shows 0 degrees on dev.cpu.x.temp for all cores. I've been looking through k8temp and amdtemp src code. I am definitely not sure of this but I believe something might have happened to those: From k8temp.h K10_THERM_REG 0xa4 K10_THERMTRIP_REG 0xe4 K10_CURTMP(val)(((val) 21) 0xfff) K10_THERMTRIP(val) ((val 1) 1) From amdtemp.c /* * Register control (K8 family) */ #define AMDTEMP_REG0F 0xe4 #define AMDTEMP_REG_SELSENSOR 0x40 #define AMDTEMP_REG_SELCORE 0x04 /* * Register control (K10 K11) family */ #define AMDTEMP_REG 0xa4 Output of k8temp -dn: CPUID: Vendor: AuthenticAMD, 0x100f43: Model=04 Family=f+1 Stepping=3 Advanced Power Management=0x1f9 Temperature sensor: Yes Frequency ID control: No Voltage ID control: No THERMTRIP support: Yes HW Thermal control: Yes SW Thermal control: Yes 100MHz multipliers: Yes HW P-State control: Yes TSC Invariant: Yes Temp=c0fef ThermTrip=1fc00c30 0 I keep a small win7 partition to test little things like this and see if the same thing happens there, and it doesn't, so I concluded that the sensors are there and are working. One thing is worth noting though. I have used a free gadget that shows activity/temp for each core. It worked fine with the previous MB/CPU.That ALSO stopped working with this new MB. Like FBSD, it shows 0 degrees for any core too, although it correctly displays each core load. The only windows tool that correctly shows the temperature are the ASUS tools that came with the mobo. Other than that, everything is working fine! The only thing I had to fix was the fstab ada location. I know this is not a big thing but I got accustomed to keeping an eye on those temperatures. I have googled for a few days now searching for Thermal register address or offsets for the Phenom II 975 BE, or anything related to this problem and found nothing. Every search on AMD site was fruitless. I could not find a single bit of tech info on this processor there, or any other tech info for that matter. Would any one have any pointers/clues/suggestions on this? Thanks, -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio YET!!] (99% winblows FREE) ___ 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: ipfw nat inbound keep-state with net.inet.ip.fw.one_pass=0
On Thu, 23 Jun 2011, umage wrote: Some points: 1) I did use the handbook as reference, and my ruleset mimics the layout used there. Excuse the late response, I've been away. The best reference, apart from ipfw(8), is /etc/rc.firewall. 'Nuff said. 2) Handbook uses divert natd, which I used until I switched to the kernel nat approach. Assuming that was working, is changing to ipfw nat the only difference? Or is that when you added fwd to the mix? Is 192.168.0.55 another box on the LAN, or an IP alias on this box? What says 'netstat -finet -rn'? Is this on FreeBSD 8.x? 3) I did not find any concrete examples of ipfw nat rule usage, so I'm using them the old natd way. Apart from the 'NAT, REDIRECT AND LSNAT' section in ipfw(8), natd(8) is still useful as fuller reference, given a few less, renamed parameters. As mentioned in that section, libalias(3) gives detail of all functions. I did some more experiments, and noticed that for example, an inbound connection can still communicate both ways after the initial state table rule expires (20 seconds for some reason). ipfw(8) 'SYSCTL VARIABLES' covers timeouts (sysctl net.inet.ip.fw.dyn_*) 20 seconds suggests a SYN timeout, so a TCP connection - but see below. Perhaps that 'works' because you're not denying established connections and using only 'setup' on keep-state rules, again assuming TCP protocol? If they communicate while the state entry is alive, the timeout resets, but it seems like it doesn't matter at all. This leads me to believe that 'ipfw nat' keeps an internal state table, which cannot be viewed, but is checked when doing check-state. Or something... which I have no way of knowing. NAT aliasing tables are entirely distinct from ipfw dynamic rule state tables. Try adding 'log' (and maybe same_ports) to ipfw nat parameters at least while debugging connections. That log, 'ipfw -ted show' and a tcpdump on each interface should show exactly what's going on. 'ipfw nat 1 show config'. Here's a pruned version of the ruleset I used. Rule 600 is the one that adds that remote -- local state table entry that messes everything up. If I omit keep-state on it, then traffic from the local side will be the one creating the states when replying, with a 5-second timeout. sysctl net.inet.ip.fw.dyn_udp_lifetime is 5 seconds by default. So now we're talking UDP? Please be more specific, or best, cutpaste results. $fw add 100 allow all from any to any via $lan_if This passes all packets coming in from the LAN, bound for anywhere - ie this box OR the outside - but before/without performing NAT - as well as passing packets being transmitted to the LAN, whether locally generated or routed after having been NAT'd on inbound pass. Not what you wanted. You mentioned packets mistakenly reaching the outside with 192.168.* source addresses, that'll be this rule. Try specifying 'in recv $if' and 'out xmit $if' avoiding 'via' when it's ambiguous, especially on outbound packets where 'via $if' is also true when they've come _in_ on that specified interface. You need to do outbound NAT first anyway. $fw nat 1 config if $wan_if redirect_port 192.168.0.55:12345 12345 $fw add 200 nat 1 ip4 from any to any in via $wan_if Ok, you're doing inbound NAT before checking state, however you've not specified protocol (tcp or udp) with redirect_port. I can't find any example in ipfw(8), natd(8) or libalias(3) where proto is optional, but I haven't read the code or tried this myself. We can't tell from this (or rule 600) whether your port '12345' is TCP or UDP. $fw add 300 check-state At this point any packet, in or out, matching dynamic state tables will execute the action of the matching keep-state rule. For packets going out to the WAN the action is a skipto, so all ip4 packets matching that flow will execute the 'skipto 800', where you NAT the outbound packets, and allow the corresponding return packets. $fw add 400 skipto 800 ip4 from any to any out via $wan_if keep-state Again, 'out via $wan_if' is ambiguous, and includes packets _received_ on $wan_if and now being transmitted to the inside, again before NAT. Specify 'out xmit' if you only want to apply this to packets being sent out to $wan_if, as I think you do; these are the only ones you want to perform NAT on anyway. $fw add 500 allow all from any to any out keep-state Ok, only inbound packets get to here, and they've already been NAT'd .. $fw add 600 allow all from any to any dst-port 12345 in keep-state $fw add 700 deny all from any to any in While 'all | ip' will work for tcp or udp packets, better to specify the protocol targetted. Ok, not only outbound packets get here, but also the return packets coming in with matching state, from the skipto. $fw add 800 nat 1 ip4 from any to any out $fw add 900 allow all from any to any Bottom line is you need to do NAT on packets outbound
ipfw nat inbound keep-state with net.inet.ip.fw.one_pass=0
Hi, I'm an ipfw user that finally got the opportunity to set up NAT on an interface with a public IP. I was doing some multi-homing experiments using ipfw fwd combined with outbound ipfw nat - and since I needed to run both, and both immediately ended ipfw ruleset execution, I had to turn off net.inet.ip.fw.one_pass. This is where I discovered that with that setting turned off, my inbound NAT rule stopped working. Seems that with one-pass execution, the NAT rule also performs keep-state of some sort, the dynamic state table looks ok and everything works fine. But if I turn it off, and do my own allow all in keep-state after applying a static NAT rule on an inbound connection, I see that the state table has the remote IP on the left side and mine on the right side. I also see that my NAT setup breaks and my packets are sent to the internet with a 192.168.0.x source address. I'd like to ask if I'm doing anything wrong, or whether this is a bug. I checked the issue tracker, but found no relevant issues there. I also tried asking around, but it seems noone even uses ipfw anymore. Triggering the issue requires a modified kernel (ipfw forward and ipfw nat are not available by default), requires using ipfw nat (a relatively new thing) instead of the old natd daemon, and requires changing the value of a system setting. ___ 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
kgdb and vmcore.0 cannot access memory at 0x252d1
list, I am new to kernel debugging, I compiled a new kernel with options KDB and DDBin addition to the GENERIC config and booted with the new kernel.( Goal is to debug the coredumps in my laptops /var/crash/vmcore files and try to find and fix the panic/situation which produce these coredumps) I tried to analyze all of the vmcore filesin my /var/crash/vmcore.x core dumps steps done after booting into the new kernel # cd /usr/obj/usr/src/sys/MYCUSTORMKERNEL #kgdb kernel.debug /var/crash/vmcore.0 kgdb kernel.debug /var/crash/vmcore.0 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd... Cannot access memory at address 0x252d1 (kgdb) (kgdb) For all the vmcore files I am getting this output.. Cannot access memory at address 0x252d1, how can I proceed from here, How to debug what is happening, what makes the kernel to dump these vmcores and fix the issue by using further debugging.. what are the next steps , if there a message in kgdb Cannot access memory at address 0x252d1 or any address Please share your suggestion and hints to debug more from this point. I am stuck here.. Thanks in advance Dhanesh ___ 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
Get the dev.cpu.0.temperature from sysctl(3)
Hello, I would like to get the dev.cpu.0.temperature node from sysctlbyname(). It seems this node is an opaque type but how to check it and store it to the appropriate variable type ? Cheers, -- David Demelier ___ 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: Get the dev.cpu.0.temperature from sysctl(3)
On Tue, May 03, 2011 at 10:12:33AM +0200, David Demelier wrote:
Hello,
I would like to get the dev.cpu.0.temperature node from sysctlbyname().
It seems this node is an opaque type but how to check it and store it to
the appropriate variable type ?
The best way to determine this is to read the source. I did that some time ago
to fix the temperature display in sysutils/conky.
The sysctl dev.cpu.0.temperature returns an integer, see
/sys/dev/coretemp/coretemp.c (look for the string temperature), and you'll
see:
/*
* Add the temperature MIB to dev.cpu.N.
*/
sc-sc_oid = SYSCTL_ADD_PROC(device_get_sysctl_ctx(pdev),
SYSCTL_CHILDREN(device_get_sysctl_tree(pdev)),
OID_AUTO, temperature,
CTLTYPE_INT | CTLFLAG_RD,
dev, 0, coretemp_get_temp_sysctl, IK,
Current temperature);
If you look at the definition of coretemp_get_temp_sysctl in the same file:
coretemp_get_temp_sysctl(SYSCTL_HANDLER_ARGS)
{
device_t dev = (device_t) arg1;
int temp;
temp = coretemp_get_temp(dev) * 10 + TZ_ZEROC;
return (sysctl_handle_int(oidp, temp, 0, req));
}
So the returned value is an 'int'. Note that TZ_ZEROC is #defined as 2732 at
the beginning of the file. The returned value is therefore the temperature
in Kelvin times ten.
On my machine, it gives e.g.:
sysctl dev.cpu.0.temperature
dev.cpu.0.temperature: 46.0C
If we check the 'raw' return value;
sysctl -b dev.cpu.0.temperature|hd
78 0c 00 00 |x...|
0004
Running this value with the abovementioned algorithm in reverse through a
calculator, we get
(0x0c78-2732)/10 = 46°C
Hope this helps.
Roland
--
R.F.Smith http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)
pgpXPbScJFToy.pgp
Description: PGP signature
Re: Get the dev.cpu.0.temperature from sysctl(3)
On 03/05/2011 21:40, Roland Smith wrote:
On Tue, May 03, 2011 at 10:12:33AM +0200, David Demelier wrote:
Hello,
I would like to get the dev.cpu.0.temperature node from sysctlbyname().
It seems this node is an opaque type but how to check it and store it to
the appropriate variable type ?
The best way to determine this is to read the source. I did that some time ago
to fix the temperature display in sysutils/conky.
The sysctl dev.cpu.0.temperature returns an integer, see
/sys/dev/coretemp/coretemp.c (look for the string temperature), and you'll
see:
/*
* Add the temperature MIB to dev.cpu.N.
*/
sc-sc_oid = SYSCTL_ADD_PROC(device_get_sysctl_ctx(pdev),
SYSCTL_CHILDREN(device_get_sysctl_tree(pdev)),
OID_AUTO, temperature,
CTLTYPE_INT | CTLFLAG_RD,
dev, 0, coretemp_get_temp_sysctl, IK,
Current temperature);
If you look at the definition of coretemp_get_temp_sysctl in the same file:
coretemp_get_temp_sysctl(SYSCTL_HANDLER_ARGS)
{
device_t dev = (device_t) arg1;
int temp;
temp = coretemp_get_temp(dev) * 10 + TZ_ZEROC;
return (sysctl_handle_int(oidp,temp, 0, req));
}
So the returned value is an 'int'. Note that TZ_ZEROC is #defined as 2732 at
the beginning of the file. The returned value is therefore the temperature
in Kelvin times ten.
On my machine, it gives e.g.:
sysctl dev.cpu.0.temperature
dev.cpu.0.temperature: 46.0C
If we check the 'raw' return value;
sysctl -b dev.cpu.0.temperature|hd
78 0c 00 00 |x...|
0004
Running this value with the abovementioned algorithm in reverse through a
calculator, we get
(0x0c78-2732)/10 = 46°C
Hope this helps.
Roland
Thanks a lot!
I had a look into the src and I saw the format IK used to register the
sysctl node but I was also surprised that IK was not defined in man
sysctl(9)
But I finally understood that K should means Kelvin :)
Cheers,
--
David Demelier
___
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
npviewer and ELF binary type 0 not known
Hello, I had a power failure and a lot of fsck issues after. I don't know if my system is having corrupt files but I can't use flash player anymore : markand@Groseille ~ $ nspluginwrapper -v -a -i Auto-install plugins from /home/markand/.mozilla/plugins Looking for plugins in /home/markand/.mozilla/plugins ELF binary type 0 not known. /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin: 1: Syntax error: ( unexpected markand@Groseille ~ $ nspluginwrapper -v -i /usr/local/lib/npapi/linux-f10-flashplugin/libflashplayer.so ELF binary type 0 not known. /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin: 1: Syntax error: ( unexpected nspluginwrapper: no appropriate viewer found for /usr/local/lib/npapi/linux-f10-flashplugin/libflashplayer.so Even reinstalling nspluginwrapper or linux-10-flashplugin does not solve .. Cheers, -- David Demelier ___ 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: npviewer and ELF binary type 0 not known
On 06/04/2011 08:44, David Demelier wrote: Hello, I had a power failure and a lot of fsck issues after. I don't know if my system is having corrupt files but I can't use flash player anymore : markand@Groseille ~ $ nspluginwrapper -v -a -i Auto-install plugins from /home/markand/.mozilla/plugins Looking for plugins in /home/markand/.mozilla/plugins ELF binary type 0 not known. /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin: 1: Syntax error: ( unexpected markand@Groseille ~ $ nspluginwrapper -v -i /usr/local/lib/npapi/linux-f10-flashplugin/libflashplayer.so ELF binary type 0 not known. /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin: 1: Syntax error: ( unexpected nspluginwrapper: no appropriate viewer found for /usr/local/lib/npapi/linux-f10-flashplugin/libflashplayer.so Even reinstalling nspluginwrapper or linux-10-flashplugin does not solve .. Cheers, Sorry it's my fault, the linux_enable=YES was removed in my rc.conf. Solved. Cheers. -- David Demelier ___ 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: Thunderbird segfaults if UID 0
On 4/6/11 4:00 AM, Kevin Kinsey wrote:
Hello,
I've had trouble since upgrading mail/thunderbird from 2.X
to 3.1.9 --- as a non-root user, it segfaults.
As root, I have no issues.
I've tried:
1. Googling
2. mv .mozilla .mozilla-old thunderbird
3. sudo chmod 777 /dev/null thunderbird
(and similar stuff with /dev/fd/* and
the symlinks stdin, stdout and stderr.
I'm kind of stumped at this point. Here's the
last part of a ktrace:
54137 sh RET read 872/0x368
54137 sh CALL stat(0x283034d0,0xbfbfe638)
54137 sh NAMI /usr/local/lib/thunderbird/run-mozilla.sh
54137 sh STRU struct stat {dev=87, ino=6053072, mode=-rwxrwxrwx
, nlink=1, uid=0, gid=0, rdev=24241760, atime=1302052597,
stime=1301719584, ctime=1302044479, birthtime=1301719584, size=10461,
blksize=4096, blocks=24, flags=0x0 }
54137 sh RET stat 0
54137 sh CALL eaccess(0x283034d0,X_OK)
54137 sh NAMI /usr/local/lib/thunderbird/run-mozilla.sh
54137 sh RET eaccess 0
54137 sh CALL geteuid
54137 sh RET geteuid 1001/0x3e9
54137 sh CALL fork
54137 sh RET fork 54141/0xd37d
54137 sh CALL getpgrp
54137 sh RET getpgrp 54137/0xd379
54137 sh CALL wait4(0x,0xbfbfe778,WUNTRACED,0)
54137 sh RET wait4 54141/0xd37d
54137 sh CALL exit(0x8b)
Anyone got a clue what I've done?
Thanks,
Kevin Kinsey
___
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
Create a new user account, log in to it, run tbird ?
___
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: Thunderbird segfaults if UID 0
On Wed, Apr 06, 2011 at 06:09:21PM +0200, Damien Fleuriot wrote: Create a new user account, log in to it, run tbird ? Would that be any different then moving ~/.mozilla and trying to run it? Because that was a total failure ;-) KDK P.S. I'm thinking the answer is NO. I can give it a try after work tonight, I s'pose. ___ 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: Thunderbird segfaults if UID 0
2011-04-06 20:53, Kevin Kinsey: On Wed, Apr 06, 2011 at 06:09:21PM +0200, Damien Fleuriot wrote: Create a new user account, log in to it, run tbird ? Would that be any different then moving ~/.mozilla and trying to run it? Because that was a total failure ;-) KDK P.S. I'm thinking the answer is NO. I can give it a try after work tonight, I s'pose. Try moving ~/.thunderbird to some other name like ~/thunderbird and try again. ~/.mozilla is for firefox. ___ 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
Thunderbird segfaults if UID 0
Hello,
I've had trouble since upgrading mail/thunderbird from 2.X
to 3.1.9 --- as a non-root user, it segfaults.
As root, I have no issues.
I've tried:
1. Googling
2. mv .mozilla .mozilla-old thunderbird
3. sudo chmod 777 /dev/null thunderbird
(and similar stuff with /dev/fd/* and
the symlinks stdin, stdout and stderr.
I'm kind of stumped at this point. Here's the
last part of a ktrace:
54137 sh RET read 872/0x368
54137 sh CALL stat(0x283034d0,0xbfbfe638)
54137 sh NAMI /usr/local/lib/thunderbird/run-mozilla.sh
54137 sh STRU struct stat {dev=87, ino=6053072, mode=-rwxrwxrwx
, nlink=1, uid=0, gid=0, rdev=24241760, atime=1302052597,
stime=1301719584, ctime=1302044479, birthtime=1301719584, size=10461,
blksize=4096, blocks=24, flags=0x0 }
54137 sh RET stat 0
54137 sh CALL eaccess(0x283034d0,X_OK)
54137 sh NAMI /usr/local/lib/thunderbird/run-mozilla.sh
54137 sh RET eaccess 0
54137 sh CALL geteuid
54137 sh RET geteuid 1001/0x3e9
54137 sh CALL fork
54137 sh RET fork 54141/0xd37d
54137 sh CALL getpgrp
54137 sh RET getpgrp 54137/0xd379
54137 sh CALL wait4(0x,0xbfbfe778,WUNTRACED,0)
54137 sh RET wait4 54141/0xd37d
54137 sh CALL exit(0x8b)
Anyone got a clue what I've done?
Thanks,
Kevin Kinsey
___
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
atacontrol spindown 0 does not work
Hello, I don't like to hear the spin down from my hard drive, it does it every 10 seconds approximately. I used ataidle -P 0 /dev/ad0 to disable it and it works. When I saw there was a atacontrol command for this, I tried it, so I removed ataidle and I tried : markand@Melon ~ $ sudo atacontrol spindown ad0 0 markand@Melon ~ $ sudo atacontrol spindown ad0 ad0: idle spin down disabled But I can still hear the noise every 10 seconds, I think atacontrol does not totally close the APM feature of the device. Do you have any clue? Cheers, -- David Demelier ___ 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: atacontrol spindown 0 does not work
On Tue, 2011-03-01 at 09:21 +0100, David Demelier wrote: But I can still hear the noise every 10 seconds, I think atacontrol does not totally close the APM feature of the device. atacontrol's spindown setting doesn't change anything in the disk itself: it just controls a timer in the ad(4) driver which sends a spindown command when it expires. You'll need to keep using ataidle to fix the APM value. -- Bruce Cran ___ 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: atacontrol spindown 0 does not work
El día Tuesday, March 01, 2011 a las 09:15:01AM +, Bruce Cran escribió: On Tue, 2011-03-01 at 09:21 +0100, David Demelier wrote: But I can still hear the noise every 10 seconds, I think atacontrol does not totally close the APM feature of the device. atacontrol's spindown setting doesn't change anything in the disk itself: it just controls a timer in the ad(4) driver which sends a spindown command when it expires. You'll need to keep using ataidle to fix the APM value. To the OP: I have to use ataidle as well on an Acer Aspire D250 laptop to switch-off the spindown of the disk... I'm wondering why you would prefere atacontrol? Thanks matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ ___ 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: atacontrol spindown 0 does not work
On Tue, 2011-03-01 at 11:47 +0100, Matthias Apitz wrote: I'm wondering why you would prefere atacontrol? I think everyone's been looking for an official solution. -- Bruce Cran ___ 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: Set tty resolution using hint.sc.0.flags with VESA
Hello! 07.02.2011, 03:57, David Demelier demelier.da...@gmail.com: On 06/02/2011 17:52, Dima Panov wrote: Hello! [fluffy@Beastie] ~$ cat /boot/device.hints|grep sc.0 hint.sc.0.at=isa hint.sc.0.flags=0x180 hint.sc.0.vesa_mode=0x1f0 absolutely great! But where did you find these vesa_mode setting? It's not documented anywhere. man sc, at SYNOPSIS part But I have -CURRENT -- Dima Panov (flu...@freebsd.org) KDE@FreeBSD team Facebook: http://www.facebook.com/?id=10181104157 ___ 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: delay in boot: ata2: ATA channel 0 on atapci0
On Tue, 15 Feb 2011 04:01:58 + Alexander Best arun...@freebsd.org wrote: simply add options ATA_CAM to your kernel conf and your good to go after building installing the new kernel. To get the benefits of AHCI I think it's better to use the ahci(4) driver instead of the CAM-ATA wrapper. -- Bruce Cran ___ 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
delay in boot: ata2: ATA channel 0 on atapci0
I get about a 30 second delay during boot for each hard-drive connected to my PC. I'm running FreeBSD 8.1 AMD64 on an ASUS Sabertooth X58 motherboard. atapci0: [ITHREAD] ata2: ATA channel 0 on atapci0 ata2: [ITHREAD] ata3: ATA channel 1 on atapci0 Is there something I can define or disable to make these timeouts go faster? These lines get the delay: ata2: ATA channel 0 on atapci0 ata3: ATA channel 1 on atapci0 ___ 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: delay in boot: ata2: ATA channel 0 on atapci0
On Mon Feb 14 11, Xn Nooby wrote: I get about a 30 second delay during boot for each hard-drive connected to my PC. I'm running FreeBSD 8.1 AMD64 on an ASUS Sabertooth X58 motherboard. atapci0: [ITHREAD] ata2: ATA channel 0 on atapci0 ata2: [ITHREAD] ata3: ATA channel 1 on atapci0 Is there something I can define or disable to make these timeouts go faster? These lines get the delay: ata2: ATA channel 0 on atapci0 ata3: ATA channel 1 on atapci0 A) you can rebuild your kernel with optionsATA_REQUEST_TIMEOUT=3 to reduce the timeout to 3 seconds. that should be enough for new hdds/controllers. B) or you could try switching from ATA(4) to CAM(4) via the ATA_CAM kernel option (see ATA(4) for an explanation). since you're running pretty new hardware and a recent fbsd version you would defenately benefit from switching to CAM(4). it has much better ahci support e.g. simply add options ATA_CAM to your kernel conf and your good to go after building installing the new kernel. also the probelm might be in your BIOS. be sure to deactivate all ATA channels which don't have a device connected to them. otherwise fbsd will look for one until the timeout gets hit (both in ATA(4) and CAM(4)). in fact you might want to check the bios before trying any of the steps A) or B), because this very likely seems to be the problem in your case. cheers. alex -- a13x ___ 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: delay in boot: ata2: ATA channel 0 on atapci0
Hi Alex, I will double-check my BIOS, I thought I had unused ports disabled, but I might have missed some (it's a complex motherboard!). I probably wont recompile my kernel, because I think that would prohibit me from using the freebsd-update program. I can always just wait, it was a bigger problem when I had 6 drives in it. It almost seems to be pausing when it finds a drive, I have a CDROM and one HD in it now. On Mon, Feb 14, 2011 at 11:01 PM, Alexander Best arun...@freebsd.org wrote: On Mon Feb 14 11, Xn Nooby wrote: I get about a 30 second delay during boot for each hard-drive connected to my PC. I'm running FreeBSD 8.1 AMD64 on an ASUS Sabertooth X58 motherboard. atapci0: [ITHREAD] ata2: ATA channel 0 on atapci0 ata2: [ITHREAD] ata3: ATA channel 1 on atapci0 Is there something I can define or disable to make these timeouts go faster? These lines get the delay: ata2: ATA channel 0 on atapci0 ata3: ATA channel 1 on atapci0 A) you can rebuild your kernel with options ATA_REQUEST_TIMEOUT=3 to reduce the timeout to 3 seconds. that should be enough for new hdds/controllers. B) or you could try switching from ATA(4) to CAM(4) via the ATA_CAM kernel option (see ATA(4) for an explanation). since you're running pretty new hardware and a recent fbsd version you would defenately benefit from switching to CAM(4). it has much better ahci support e.g. simply add options ATA_CAM to your kernel conf and your good to go after building installing the new kernel. also the probelm might be in your BIOS. be sure to deactivate all ATA channels which don't have a device connected to them. otherwise fbsd will look for one until the timeout gets hit (both in ATA(4) and CAM(4)). in fact you might want to check the bios before trying any of the steps A) or B), because this very likely seems to be the problem in your case. cheers. alex -- a13x ___ 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
Set tty resolution using hint.sc.0.flags with VESA
Hello, I don't like much to use allscreens_flags to set my tty resolution because it's done at the end of /etc/rc process. I know we can edit the hint.sc.0.flags in /boot/device.hints to set the resolution at the earliest stage. I want to use the 1366x768 mode : # vidcontrol -i mode [... snip ...] 496 (0x1f0) 0x001f G 1366x768x32 D 8x16 0xa 64k 64k 0xc000 4128k To use this mode I should write hint.sc.0.flags=0x1f00180 where 80 means VESA mode following the sc(4) manpage. It seems that my resolution is like 1024x768 when I bootup and not the one I want. However when I use vidcontrol MODE_496 after boot it works pretty well. Is there something wrong on my line ? Cheers, -- David Demelier ___ 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: Set tty resolution using hint.sc.0.flags with VESA
Hello! [fluffy@Beastie] ~$ cat /boot/device.hints|grep sc.0 hint.sc.0.at=isa hint.sc.0.flags=0x180 hint.sc.0.vesa_mode=0x1f0 07.02.2011, 01:50, David Demelier demelier.da...@gmail.com: Hello, I don't like much to use allscreens_flags to set my tty resolution because it's done at the end of /etc/rc process. I know we can edit the hint.sc.0.flags in /boot/device.hints to set the resolution at the earliest stage. I want to use the 1366x768 mode : # vidcontrol -i mode [... snip ...] 496 (0x1f0) 0x001f G 1366x768x32 D 8x16 0xa 64k 64k 0xc000 4128k To use this mode I should write hint.sc.0.flags=0x1f00180 where 80 means VESA mode following the sc(4) manpage. It seems that my resolution is like 1024x768 when I bootup and not the one I want. However when I use vidcontrol MODE_496 after boot it works pretty well. Is there something wrong on my line ? Cheers, -- David Demelier ___ 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 -- Dima Panov (flu...@freebsd.org) KDE@FreeBSD team Facebook: http://www.facebook.com/?id=10181104157 ___ 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: Set tty resolution using hint.sc.0.flags with VESA
On 06/02/2011 17:52, Dima Panov wrote: Hello! [fluffy@Beastie] ~$ cat /boot/device.hints|grep sc.0 hint.sc.0.at=isa hint.sc.0.flags=0x180 hint.sc.0.vesa_mode=0x1f0 absolutely great! But where did you find these vesa_mode setting? It's not documented anywhere. Cheers, -- David Demelier ___ 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: Set tty resolution using hint.sc.0.flags with VESA
David Demelier wrote: hint.sc.0.vesa_mode=0x1f0 ... absolutely great! But where did you find these vesa_mode setting? It's not documented anywhere. Look again: syscons(4), in the Synopsis and the Driver Flags section. b. ___ 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: binutils problem? WAS [Re: static linking error: ELF binary type 0 not known. Exec format error. Binary file not executable.]
On Wed, Dec 15, 2010 at 06:58:50PM +0100, Tijl Coosemans wrote: On Monday 06 December 2010 16:16:30 Anton Shterenlikht wrote: On Mon, Dec 06, 2010 at 02:06:22PM +0100, Tijl Coosemans wrote: On Monday 29 November 2010 14:04:16 Anton Shterenlikht wrote: - Forwarded message from Marcel Moolenaar xcl...@mac.com - On Nov 10, 2010, at 5:32 AM, Anton Shterenlikht wrote: [ia64] ia64% file a.out a.out: ELF 64-bit LSB executable, IA-64, version 1 (SYSV), statically linked, not stripped [amd64] amd64% file a.out a.out: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), statically linked, for FreeBSD 9.0 (900023), not stripped The branding on ia64 is wrong. The executable is not marked as being a FreeBSD executable. It's declared as SYSV, whereas on amd64 it's properly declared as FreeBSD. This is a binutils problem. Anybody here can explain better what Marcel meant by binutils problem, and how to fix it? I've binutils-2.20.1_3 installed from devel/binutils. As a workaround you could manually brand the executable: brandelf -f 9 a.out this works fine. A fix has been committed to CURRENT, 8-STABLE and 7-STABLE. You should no longer have to brand executables manually. yes, just checked, many thanks. anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ 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: binutils problem? WAS [Re: static linking error: ELF binary type 0 not known. Exec format error. Binary file not executable.]
On Monday 06 December 2010 16:16:30 Anton Shterenlikht wrote: On Mon, Dec 06, 2010 at 02:06:22PM +0100, Tijl Coosemans wrote: On Monday 29 November 2010 14:04:16 Anton Shterenlikht wrote: - Forwarded message from Marcel Moolenaar xcl...@mac.com - On Nov 10, 2010, at 5:32 AM, Anton Shterenlikht wrote: [ia64] ia64% file a.out a.out: ELF 64-bit LSB executable, IA-64, version 1 (SYSV), statically linked, not stripped [amd64] amd64% file a.out a.out: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), statically linked, for FreeBSD 9.0 (900023), not stripped The branding on ia64 is wrong. The executable is not marked as being a FreeBSD executable. It's declared as SYSV, whereas on amd64 it's properly declared as FreeBSD. This is a binutils problem. Anybody here can explain better what Marcel meant by binutils problem, and how to fix it? I've binutils-2.20.1_3 installed from devel/binutils. As a workaround you could manually brand the executable: brandelf -f 9 a.out this works fine. A fix has been committed to CURRENT, 8-STABLE and 7-STABLE. You should no longer have to brand executables manually. signature.asc Description: This is a digitally signed message part.
Re: portupgrade causes kernel message: maxproc limit exceeded by uid 0
On 12/05/2010 10:45 AM, Lowell Gilbert wrote: Yuri y...@rawbw.com writes: Beginning at some time less than 1 month ago I started getting such message. Increasing maxproc doesn't help. Current values are like this: kern.maxproc: 6164 kern.maxprocperuid: 5547 What may be causing such condition? limits(1), perhaps? I DoSed a remote box building devel/glib20 too. Just now reproduced it locally. It manifested as a forkbomb somewhere in gnome-libtool while building glib-2.26.1 inside a clean chroot (not a jail). The issue seemed to only manifest within the chroot, regardless of whether the configuration was identical to the host or not. It did not occur when attempting to build on the host machine. Every other package I built worked just fine. I eventually tracked it down to a stray colon at the start of the PATH variable in my chroot build environment: PATH=:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin Thus, it might be a good idea to verify that your build environment variables and config files are sane. == mv -f .deps/gdatetime.Tpo .deps/gdatetime.Po /bin/sh /usr/obj/usr/ports/devel/glib20/work/gnome-libtool --tag=CC --mode=link cc -O2 -pipe -O2 -pipe -march=nocona -fno-strict-aliasing -Wall -L/usr/local/lib -lintl -o strfuncs strfuncs.o ../../glib/libglib-2.0.la -lm mv -f .deps/regex.Tpo .deps/regex.Po /bin/sh /usr/obj/usr/ports/devel/glib20/work/gnome-libtool --tag=CC --mode=link cc -O2 -pipe -O2 -pipe -march=nocona -fno-strict-aliasing -Wall -L/usr/local/lib -lintl -o string string.o ../../glib/libglib-2.0.la -lm printf: Cannot fork: Resource temporarily unavailable printf: Cannot fork: Resource temporarily unavailable printf: Cannot fork: Resource temporarily unavailable printf: Cannot fork: Resource temporarily unavailable printf: Cannot fork: Resource temporarily unavailable /libexec/ld-elf.so.1: Shared object libglib-2.0.so.0 not found, required by printf == -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net cyber...@cyberleo.net Furry Peace! - http://.fur.com/peace/ ___ 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: binutils problem? WAS [Re: static linking error: ELF binary type 0 not known. Exec format error. Binary file not executable.]
On Monday 29 November 2010 14:04:16 Anton Shterenlikht wrote: - Forwarded message from Marcel Moolenaar xcl...@mac.com - On Nov 10, 2010, at 5:32 AM, Anton Shterenlikht wrote: [ia64] ia64% file a.out a.out: ELF 64-bit LSB executable, IA-64, version 1 (SYSV), statically linked, not stripped [amd64] amd64% file a.out a.out: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), statically linked, for FreeBSD 9.0 (900023), not stripped The branding on ia64 is wrong. The executable is not marked as being a FreeBSD executable. It's declared as SYSV, whereas on amd64 it's properly declared as FreeBSD. This is a binutils problem. Anybody here can explain better what Marcel meant by binutils problem, and how to fix it? I've binutils-2.20.1_3 installed from devel/binutils. As a workaround you could manually brand the executable: brandelf -f 9 a.out signature.asc Description: This is a digitally signed message part.
Re: binutils problem? WAS [Re: static linking error: ELF binary type 0 not known. Exec format error. Binary file not executable.]
On Mon, Dec 06, 2010 at 02:06:22PM +0100, Tijl Coosemans wrote: On Monday 29 November 2010 14:04:16 Anton Shterenlikht wrote: - Forwarded message from Marcel Moolenaar xcl...@mac.com - On Nov 10, 2010, at 5:32 AM, Anton Shterenlikht wrote: [ia64] ia64% file a.out a.out: ELF 64-bit LSB executable, IA-64, version 1 (SYSV), statically linked, not stripped [amd64] amd64% file a.out a.out: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), statically linked, for FreeBSD 9.0 (900023), not stripped The branding on ia64 is wrong. The executable is not marked as being a FreeBSD executable. It's declared as SYSV, whereas on amd64 it's properly declared as FreeBSD. This is a binutils problem. Anybody here can explain better what Marcel meant by binutils problem, and how to fix it? I've binutils-2.20.1_3 installed from devel/binutils. As a workaround you could manually brand the executable: brandelf -f 9 a.out this works fine. many thanks anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ 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: portupgrade causes kernel message: maxproc limit exceeded by uid 0
Yuri y...@rawbw.com writes: Beginning at some time less than 1 month ago I started getting such message. Increasing maxproc doesn't help. Current values are like this: kern.maxproc: 6164 kern.maxprocperuid: 5547 What may be causing such condition? limits(1), perhaps? ___ 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
portupgrade causes kernel message: maxproc limit exceeded by uid 0
Beginning at some time less than 1 month ago I started getting such message. Increasing maxproc doesn't help. Current values are like this: kern.maxproc: 6164 kern.maxprocperuid: 5547 What may be causing such condition? Yuri --- sample log from portupgrade --- mv -f .deps/regex.Tpo .deps/regex.Po /bin/sh /usr/ports/devel/glib20/work/gnome-libtool --tag=CC --mode=link cc -O2 -pipe -fno-strict-aliasing -Wall -L/usr/local/lib -lintl -o markup-escape markup-escape.o ../../glib/libglib-2.0.la mv -f .deps/gdatetime.Tpo .deps/gdatetime.Po /bin/sh /usr/ports/devel/glib20/work/gnome-libtool --tag=CC --mode=link cc -O2 -pipe -fno-strict-aliasing -Wall -L/usr/local/lib -lintl -o markup-subparser markup-subparser.o ../../glib/libglib-2.0.la ./printf: Cannot fork: Resource temporarily unavailable ./printf: Cannot fork: Resource temporarily unavailable ./printf: Cannot fork: Resource temporarily unavailable ./printf: Cannot fork: Resource temporarily unavailable ./printf: Cannot fork: Resource temporarily unavailable ./printf: Cannot fork: Resource temporarily unavailable ./printf: Cannot fork: Resource temporarily unavailable ./printf: Cannot fork: Resource temporarily unavailable ./printf: Cannot fork: Resource temporarily unavailable ./printf: Cannot fork: Resource temporarily unavailable ./printf: Cannot fork: Resource temporarily unavailable ./printf: Cannot fork: Resource temporarily unavailable ./printf: Cannot fork: Resource temporarily unavailable ./printf: Cannot fork: Resource temporarily unavailable /printf: Cannot fork: Resource temporarily unavailable ./printf: Cannot fork: Resource temporarily unavailable cd: can't cd to /snprintf /snprintf /snprintf /snprintf /snprintf /snprintf /snprintf /printf /printf /printf /sprintf GLib-ERROR **: failed to fork test program: Resource temporarily unavailable aborting... GLib-ERROR **: failed to fork test program: Resource temporarily unavailable aborting... cd: can't cd to /snprintf /snprintf /snprintf /snprintf /snprintf /snprintf ___ 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
binutils problem? WAS [Re: static linking error: ELF binary type 0 not known. Exec format error. Binary file not executable.]
- Forwarded message from Marcel Moolenaar xcl...@mac.com - On Nov 10, 2010, at 5:32 AM, Anton Shterenlikht wrote: [ia64] ia64% file a.out a.out: ELF 64-bit LSB executable, IA-64, version 1 (SYSV), statically linked, not stripped [amd64] amd64% file a.out a.out: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), statically linked, for FreeBSD 9.0 (900023), not stripped The branding on ia64 is wrong. The executable is not marked as being a FreeBSD executable. It's declared as SYSV, whereas on amd64 it's properly declared as FreeBSD. This is a binutils problem. FYI, -- Marcel Moolenaar xcl...@mac.com - End forwarded message - Anybody here can explain better what Marcel meant by binutils problem, and how to fix it? I've binutils-2.20.1_3 installed from devel/binutils. many thanks anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ 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: kldunload(8) returns 0, although it fail
On Fri Nov 5 10, CyberLeo Kitsana wrote: On 11/03/2010 05:34 PM, Alexander Best wrote: hi there, is this a known issue with kldunload(8)? ***beginn*** otaku% kldunload sound otaku% echo $? 0 otaku% kldstat Id Refs AddressSize Name 1 35 0x8010 a2da40 kernel 21 0x80b2e000 295e8snd_hda.ko 31 0x80b58000 85110sound.ko 41 0x80bde000 da4bb8 nvidia.ko 54 0x81983000 418e0linux.ko 61 0x819c5000 80e8 ng_ubt.ko 72 0x819ce000 fa78 ng_hci.ko 82 0x819de000 2bd0 ng_bluetooth.ko 93 0x819e1000 15e68netgraph.ko 101 0x81c12000 3edb linprocfs.ko 113 0x81c16000 4698 pseudofs.ko 121 0x81c1b000 31b3 procfs.ko 131 0x81c1f000 a37 linsysfs.ko otaku% kldunload sound kldunload: attempt to unload file that was loaded by the kernel kldunload: can't unload file: Device busy sound.ko was presumably loaded by snd_hda.ko, as it is a dependency. You must unload all the modules depending on sound.ko before it will unload. At that point, I believe I've seen it unload itself. Same with netgraph.ko, and the modules that require it (ng_*.ko). thanks for your help. the issue is however not that i expect any of the modules i tested to unload successfully. as you pointed out sound.ko and netgraph.ko are being used so they cannot be unloaded. however kldunload suceeds, atlthough it shouldn't. only the second time it is being invoked it fails with EBUSY. it should also fail the first time. cheers. alex -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net cyber...@cyberleo.net Furry Peace! - http://.fur.com/peace/ -- a13x ___ 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: kldunload(8) returns 0, although it fail
On Wed Nov 3 10, Alexander Best wrote: hi there, is this a known issue with kldunload(8)? this is also very interesting: ***beginn*** otaku% kldstat -v|grep netgraph 73 0x80bfa000 15e68netgraph.ko (/boot/kernel/netgraph.ko) 6 netgraph otaku% sudo kldunload netgraph otaku% echo $? 0 otaku% kldstat -v|grep netgraph 72 0x80bfa000 15e68netgraph.ko (/boot/kernel/netgraph.ko) 6 netgraph otaku% ***end*** there seems to be a logical error in the ref counting code. cheers. alex ***beginn*** otaku% kldunload sound otaku% echo $? 0 otaku% kldstat Id Refs AddressSize Name 1 35 0x8010 a2da40 kernel 21 0x80b2e000 295e8snd_hda.ko 31 0x80b58000 85110sound.ko 41 0x80bde000 da4bb8 nvidia.ko 54 0x81983000 418e0linux.ko 61 0x819c5000 80e8 ng_ubt.ko 72 0x819ce000 fa78 ng_hci.ko 82 0x819de000 2bd0 ng_bluetooth.ko 93 0x819e1000 15e68netgraph.ko 101 0x81c12000 3edb linprocfs.ko 113 0x81c16000 4698 pseudofs.ko 121 0x81c1b000 31b3 procfs.ko 131 0x81c1f000 a37 linsysfs.ko otaku% kldunload sound kldunload: attempt to unload file that was loaded by the kernel kldunload: can't unload file: Device busy otaku% echo $? 1 otaku% ***end*** cheers. alex -- a13x -- a13x ___ 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: kldunload(8) returns 0, although it fail
On 11/03/2010 05:34 PM, Alexander Best wrote: hi there, is this a known issue with kldunload(8)? ***beginn*** otaku% kldunload sound otaku% echo $? 0 otaku% kldstat Id Refs AddressSize Name 1 35 0x8010 a2da40 kernel 21 0x80b2e000 295e8snd_hda.ko 31 0x80b58000 85110sound.ko 41 0x80bde000 da4bb8 nvidia.ko 54 0x81983000 418e0linux.ko 61 0x819c5000 80e8 ng_ubt.ko 72 0x819ce000 fa78 ng_hci.ko 82 0x819de000 2bd0 ng_bluetooth.ko 93 0x819e1000 15e68netgraph.ko 101 0x81c12000 3edb linprocfs.ko 113 0x81c16000 4698 pseudofs.ko 121 0x81c1b000 31b3 procfs.ko 131 0x81c1f000 a37 linsysfs.ko otaku% kldunload sound kldunload: attempt to unload file that was loaded by the kernel kldunload: can't unload file: Device busy sound.ko was presumably loaded by snd_hda.ko, as it is a dependency. You must unload all the modules depending on sound.ko before it will unload. At that point, I believe I've seen it unload itself. Same with netgraph.ko, and the modules that require it (ng_*.ko). -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net cyber...@cyberleo.net Furry Peace! - http://.fur.com/peace/ ___ 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
kldunload(8) returns 0, although it fail
hi there, is this a known issue with kldunload(8)? ***beginn*** otaku% kldunload sound otaku% echo $? 0 otaku% kldstat Id Refs AddressSize Name 1 35 0x8010 a2da40 kernel 21 0x80b2e000 295e8snd_hda.ko 31 0x80b58000 85110sound.ko 41 0x80bde000 da4bb8 nvidia.ko 54 0x81983000 418e0linux.ko 61 0x819c5000 80e8 ng_ubt.ko 72 0x819ce000 fa78 ng_hci.ko 82 0x819de000 2bd0 ng_bluetooth.ko 93 0x819e1000 15e68netgraph.ko 101 0x81c12000 3edb linprocfs.ko 113 0x81c16000 4698 pseudofs.ko 121 0x81c1b000 31b3 procfs.ko 131 0x81c1f000 a37 linsysfs.ko otaku% kldunload sound kldunload: attempt to unload file that was loaded by the kernel kldunload: can't unload file: Device busy otaku% echo $? 1 otaku% ***end*** cheers. alex -- a13x ___ 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
