Re: Re: # portmaster -r pixman fails with !#/bin/sh list too long
On 10/03/2013 20:28, Antonio Olivares wrote: Have tried that, but it rebuilds pixman, but then X bombs out blurting out messages that libpixman.so is missing :( I have tried to remove print/texlive-scheme-full; removed it, but then run portmaster -R pixman, and portmaster -r pixman and the running of it stops with message that !#/bin/sh .. argument too long and comes up with texlive-?-?-_1 or similar. Have not been successful in fixing this issue. I have 2 machines working and 2 not working because of this. I am running out of ideas. Is there another way to fix this issue manually, i.e, going to /usr/ports/x11/pixman and rebuilding it there or have to go one by one? Is it vital to use the texlive ports you get via portshaker or could you switch to TEX_DEFAULT=texlive and use the texlive 2012 from official ports (which has a few huge instead of many tiny packages)? (If you want to switch, remove everything starting with texlive, check out a fresh ports tree without portshaker, since there is at least one port with the same name, and install print/texlive-full and maybe print/texlive-docs.) Cheers, Jan Henrik ___ 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: Bourne shell if syntax
On 06/10/2013 21:10, dte...@freebsd.org wrote: Character sentinels are not required. FreeBSD's sh(1) knows (because [ is a built-in) that when you quote a parameter, that it is not (even if the value begins with -) not an operator. What you are saying here is at least misleading. I just started up sh on 9.1 RELEASE and tried: $ A=-z $ if [ $A ] ; then echo z ; fi z $ if [ $A 1 ] ; then echo z ; fi $ if /bin/[ $A ] ; then echo z ; fi z $ if /bin/[ $A 1 ] ; then echo z ; fi $ Although -z is quoted, it is seen as an operator. It does not seem to have anything to do with whether the build-in or external [ is used. Cheers, Jan Henrik ___ 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: Re: bash Shell Scripting Question
On 09/20/2012 04:29, Polytropon wrote:
Correct. You could use different approaches which may or may
not fail due to the directory names you will encounter (like
directories with spaces or special characters).
#!/bin/sh
for DIR in `ls -LF | grep \/`; do
cd ${DIR}
# do stuff
done
Or you can use piping:
#!/bin/sh
ls -LF | grep \/ | while read DIR; do
cd ${DIR}
# do stuff
done
I'm quite confident there are even more elegant and fault-
tolerant solutions. You would maybe have to tweak the ls
command or play with IFS (space or newline).
Even if you start quoting ${DIR}, the first one will fail at least for
names containing spaces, the second one at least for names starting with
spaces. As you said, you would have to change IFS to maybe slash and
newline, assuming that you do not have names containing newlines, in
which case the approach cannot work.
I understand that you want all directories and links to directories not
starting with a period. How about trying all files not starting with a
period and skipping the non directories:
#!/bin/sh
for DIR in *
do
cd $DIR /dev/null 21 || continue
pwd
cd - /dev/null
done
This one works with names containing spaces or even newlines and does
not even need to spawn external commands or subshells. It may have other
caveats, though.
Cheers,
Jan Henrik
___
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
Swapping geli devices between machines: MD5 hash mismatch
I tried to attach a geli encrypted partition from a disk of a different machine attached via eSATA, but I got: geli: MD5 hash mismatch for ada1s2e. Putting the disk back to the old machine, I was able to attach and use the geli encrypted partition without an error. Before I investigate further, is this supported in general? The original machine is 9.0-RELEASE/i386 and does not support aesni. The disk in question is the only harddisk and shows up as: ada0 at ata0 bus 0 scbus0 target 0 lun 0 ada0: ST9160827AS 3.AAA ATA-8 SATA 1.x device ada0: 150.000MB/s transfers (SATA, UDMA5, PIO 8192bytes) ada0: 152627MB (312581808 512 byte sectors: 16H 63S/T 16383C) ada0: Previously was known as ad0 GEOM: ada0s2: geometry does not match label (255h,63s != 16h,63s). The machine with the error is 9.0-RELEASE/amd64 and has aesni loaded. The disk in question is attached via eSATA and shows up as: ada1 at ahcich3 bus 0 scbus3 target 0 lun 0 ada1: ST9160827AS 3.AAA ATA-8 SATA 1.x device ada1: 150.000MB/s transfers (SATA 1.x, UDMA6, PIO 8192bytes) ada1: Command Queueing enabled ada1: 152627MB (312581808 512 byte sectors: 16H 63S/T 16383C) ada1: Previously was known as ad10 GEOM: ada1s2: geometry does not match label (255h,63s != 16h,63s). The geli partition was initialized on 9.0-RELEASE/i386. The relevant data from fdisk are: cylinders=310101 heads=16 sectors/track=63 (1008 blks/cyl) The data for partition 2 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 83886081, size 125826429 (61438 Meg), flag 0 beg: cyl 1023/ head 255/ sector 63; end: cyl 1023/ head 255/ sector 63 The bsdlabel is: a: 48234496 04.2BSD0 0 0 b:2097152 48234496 swap c: 125826429 0unused0 0 # raw part, don't edit e: 75494781 503316484.2BSD0 0 0 I was able to mount and use the other (unencrypted) partition on the machine with the geli error. The major differences -- besides the completely different hardware -- are: SATA/eSATA, i386/amd64, and software/aesni. What could be the issue here? Thanks, Jan Henrik ___ 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: mkisofs increasing iso size by 100 MB
On 01/-10/-28163 20:59, Amitabh Kant wrote: I am trying to customise the bsdinstall auto script. I can mount the iso (amd64 arch / 9.0 RELEASE) and change the shell script as per my requirement. Once I try to re-create the iso file using mkisofs utility, the size of the final iso increases by 100 MB if -J (joliet) mode is used. If I remove the joliet mode, it still increases by around 97 MB. Even if no changes are made to any of the files, the result is same. The process I have followed is as follows: # mkdir /usr/iso # cd /usr/iso # dd if=/dev/cd0 of=org.iso bs=2048 # mdconfig -a -t vnode -f org.iso -u 0 # mount_cd9660 /dev/md0 /mnt # mkdir staging # cd staging # rsync -a /mnt/ . With Joliet mode # mkisofs -J -R -V CustomBSD -no-emul-boot -b boot/cdboot -iso-level 3 -o /usr/iso/my_custom.iso . Without Joliet mode # mkisofs -R -V CustomBSD -no-emul-boot -b boot/cdboot -iso-level 3 -o /usr/iso/my_custom1.iso . The original iso is 612M, custom.iso is 712M and custom1.iso is 709M. System details: FreeBSD amd64 9.0 RELEASE running inside a virtualbox with 2GB RAM. Where am I going wrong? There are many hardlinked files on the iso images. By the procedure above, you have them included multiple times. From the rsync manpage: Note that -a does not preserve hardlinks, because finding multiply-linked files is expensive. You must separately specify -H. You will probably want -cache-inodes for mkisofs as well (and maybe other options). Or you could look at src/release/amd64/mkisoimages.sh for the use of makefs -t cd9660. Cheers, Jan Henrik ___ 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
Wrong (000) UDF directory permissions with mkisofs
I have created a DVD image (on 8.2-RELEASE/amd64 using cdrtools-3.00_1) with mkisofs -R -J -udf -iso-level 3 -V NAME -o FILE.iso DIR/ (as described in the handbook), all files in DIR/ have 644 permission, all directories 755 permissions and all are owned by $USER:wheel. When I mount the ISO-9660+Rockridge layout (mount_cd9660 -j), everything is fine: The files have 444 permissions and the directories 555. Mounting the UDF layout (mount_udf), all files have 444 permissions, most (2795) directories have 555 permissions, but some (167) directories have 000 permissions and cannot be accessed by non-root users. What went wrong and how can I fix it? (I need the UDF layout, since some file names are truncated in the Joliet layout and the DVD will be used on Windows.) Cheers, Jan Henrik ___ 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: Wrong (000) UDF directory permissions with mkisofs
On 03/01/2011 15:01, Jan Henrik Sylvester wrote: mkisofs -R -J -udf -iso-level 3 -V NAME -o FILE.iso DIR/ [...] Mounting the UDF layout (mount_udf), all files have 444 permissions, most (2795) directories have 555 permissions, but some (167) directories have 000 permissions and cannot be accessed by non-root users. I found it was exactly the eights directory level that had 000 permissions. I am still not sure, why that is a problem for UDF, if it is non for Rockridge. Anyhow, using much more relaxed settings, I got a DVD that works: mkisofs -allow-leading-dots -allow-lowercase -allow-multidot -d -D -iso-level 4 -l -N -r -udf -V NAME -o FILE.iso DIR/ Probably, just -iso-level 4 -D would have been sufficient. Cheers, Jan Henrik ___ 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: What is the best way to image copy a FreeBSD system?
On 01/-10/-28163 20:59, Warren Block wrote: On Tue, 15 Feb 2011, Xn Nooby wrote: On Linux I use clonezilla, which understands the EXT3 filesystem, and it can skip unused space (I'm using about 3GB out of 1TB). On FreeBSD, I have to fill the 1TB drive with zero-filled files, then delete them, on each partiton, since CloneZilla uses DD+gzip on the entire drive. Some of the development versions of Clonezilla do understand UFS. It's been a few months since I looked at this, and I need to go back and figure out exactly which. I tried a version of Clonezilla that understood ufs and it was really fast copying a slice: It did not understand disklabels and copied only the a partition pretending that it did the entire slice. Did you try to copy a slice with multiple partitions? Cheers, Jan Henrik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 8.2: state of Kerberos, GSS-API and (Cyrus) SASL?
On 01/-10/-28163 20:59, Vallo Kallaste wrote: Googling for the subject keywords gave me quite disturbing overall feeling. I have no personal experience but it seems that things are broken from the second half of 2010 and still not recovered? I got GSSAPI of Heimdal 1.1 in FreeBSD base is still broken, GSSAPI of Heimdal 1.4 in ports is supposed to work, but I have not been successful with Cyrus SASL (see below). KDC up and working on 8.2-RC2 base Heimdal without any glitch, but this is to be expected. What's the state about GSS-API and cyrus-sasl2 integration with base Heimdal? With ports Heimdal? Can I replace base Heimdal with one from ports, is it supported? Any make.conf knobs to fiddle with? Any info appreciated. I am struggling with exactly the same problem. Unfortunately, I got no reply on this list about it: http://lists.freebsd.org/pipermail/freebsd-questions/2011-January/226495.html If you get any further, please, tell me. I am thinking about reposting my question to a different list: stable as that is where the earlier discussions happened or ports as that seems more appropriate. What I have not tried, yet, is using MIT Kerberos from ports instead of Heimdal, but since we use Heimdal here for everything, I am kind of reluctant. (Otherwise, I would have to setup some Linux server...) Cheers, Jan Henrik ___ 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: Re: Keyboard repeat issues with Dell Optiplex 980s
On 01/-10/-28163 20:59, Steve Polyack wrote: On 1/18/2011 5:56 PM, Jeremy Chadwick wrote: On Tue, Jan 18, 2011 at 04:40:13PM -0500, Steve Polyack wrote: We've recently upgraded a few desktop workstations from Dell Optiplex 960s to Optiplex 980s. We were running FreeBSD 8.1-RELEASE. The migration was performed by simply swapping the drives into the new systems. Immediately after switching people over, they all began to report bizarre keyboard issues - things like infinite key repeats (letters, numbers, enter) for keys they did not hold down. The key repeats continue indefinitely until another key is pressed. Occasionally, even mouse input will trigger similar infinite keyboard input repetition. In addition to the repeat issue, sometimes physical key-presses are not registered by FreeBSD, leading to typos and angry developers. We've tried doing fresh installs of FreeBSD 8.2-RC2 on two of these systems, and the issue persists. Because of the observed behavior, I'm thinking that this is due to new hardware in the 980s which isn't timing or handling interrupts correctly under the FreeBSD kernel. Looking at a 'pciconf -lvb' from each system, I noticed that the 980 has two USB controllers which probe under ehci(4), while the 960 (which does not exhibit this problem), enumerates six uhci(4) controllers and two ehci(4) controllers. To cut to the chase here, the 960 users' keyboards probe under a USB1.0 uhci(4), while the 980s only have ehci(4) devices to attach to. So, I guess what I'm asking is - has anyone else seen any keyboard repeat or other USB craziness with ehci(4) ports or otherwise Intel PCH controllers? Any fellow Optiplex 980 users? I'd be more than happy to provide pciconf or other output if requested. Try adding the following to /boot/loader.conf then reboot and see if the excessive repeat behaviour changes: hint.kbdmux.0.disabled=1 It would also help if you would state exactly what brand/model of keyboard is used. Yes, believe it or not, it matters. dmesg output would be helpful in this case. The keyboard is also a Dell model - model KB1421, or listed as Dell QuiteKey Keyboard under dmesg. The same keyboard does not exhibit the strange behavior when used with the older model of tower (Optiplex 960). I'll reboot today with the loader.conf hint you provided. I'll let you guys know if it helps. Thanks! I have 8.1-RELEASE running on an Optiplex 980 with no keyboard problems, but not with a Dell keyboard as we ordered Cherry keyboards with our Dells (the person evaluating the Dells thought the keyboard was way too light and fragile). Since I usually have the keyboard plugged into the hub in the display, I just tried it directly in the (rear) usb ports with no difference. Trying the Fujitsu and Sun keyboards from the other machines in my office does not immediately lead to problems, either. (Or how much would I have to type to reproduce the problem?) Maybe it is just the keyboards? Or a bios setting? (I cannot currently reboot to check if there are any keyboard related bios settings I changed.) Cheers, Jan Henrik ___ 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
ldap with GSSAPI using security/cyrus-sasl2 with security/heimdal?
Earlier I tried GSSAPI authentication for ldap against heimdal in 8.1-RELEASE base and failed. Now I tried again with security/heimdal. I got: security/heimdal security/cyrus-sasl2 with HEIMDAL_HOME=/usr/local/ net/openldap24-server with WITH_SASL When I first tried ldapmodify -Z -Y GSSAPI -I -D CRED -H ldap://FQDN, I got: ldap_sasl_interactive_bind_s: Unknown authentication method (-6) additional info: SASL(-4): no mechanism available: No worthy mechs found In /var/log/auth.log, I found for slapd and ldapmodify: unable to dlopen /usr/local/lib/sasl2/libgssapiv2.so.2: /usr/local/lib/sasl2/libgssapiv2.so.2: Undefined symbol gss_nt_service_name I found this discussion: http://www.mail-archive.com/heimdal-discuss@sics.se/msg00126.html Not sure what might be wrong with configure, I added the following line to config.h after running make configure and before make: #define HAVE_GSS_C_NT_HOSTBASED_SERVICE 1 With security/cyrus-sasl2 compiled that way, I do not get the Undefined symbol starting slapd anymore. Now ldapmodify gives me: ldap_sasl_interactive_bind_s: Other (e.g., implementation specific) error (80) additional info: SASL(-1): generic failure: GSSAPI Error: No credentials were supplied, or the credentials were unavailable or inaccessible. (unknown mech-code 0 for mech unknown) I am out of ideas. Do I even have the ldapmodify command correct? (I tried with -U u:USER and -X u:USER, too.) Is security/cyrus-sasl2 supposed to work with GSSAPI from security/heimdal? How should the undefined symbol be fixed properly? Is there anything more to fix with cyrus-sasl configure? Thanks for any ideas, Jan Henrik ___ 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: Firefox 3.6 and Java ?
On 01/-10/-28163 20:59, John Levine wrote: I gather that Firefox 3.6 still doesn't work with Java, since the glue hasn't been updated. Is anyone likely to be working on this? java/openjdk6 WITH_WEB will give you the plugin to use with www/firefox. You just have to enable it manually: cd ~/.mozilla/plugins/ ln -s /usr/local/openjdk6/jre/lib/IcedTeaPlugin.so Cheers, Jan Henrik ___ 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: Firefox 3.6 and Java ?
On 01/-10/-28163 20:59, John Levine wrote: I gather that Firefox 3.6 still doesn't work with Java, since the glue hasn't been updated. Is anyone likely to be working on this? java/openjdk6 WITH_WEB will give you the plugin to use with www/firefox. You just have to enable it manually: cd ~/.mozilla/plugins/ ln -s /usr/local/openjdk6/jre/lib/IcedTeaPlugin.so Cheers, Jan Henrik ___ 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: Intel WiFi Link 5100AGN Supported on FreeBSD-8.0?
On 01/-10/-28163 20:59, S Roberts wrote: The wireless nic on my laptop is the Intel WiFi Link 5100AGN. Is this card supported in FreeBSD as present? Support for that device got MFCed to 8-STABLE a short time after 8.0-RELEASE. Cheers, Jan Henrik ___ 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
AFS on FreeBSD 8?
I tried to get an AFS client on my 8.0-RELEASE (or 8-STABLE) system. What is the status of AFS on FreeBSD? Neither OpenAFS nor Arla seem to be in ports. I found the freebsd-afs mailing list with many posting from 2008/Dec but nothing from 2009 or 2010. The port-freebsd list on openafs.org has nothing newer, either. http://wiki.freebsd.org/afs has instructions for Arla, but the build fails on 8.0-RELEASE. http://wiki.freebsd.org/afs-server seems to be even older. http://wiki.freebsd.org/AFS_using_OpenAFS_%2B_Arla gives me: You are not allowed to view this page. Is there anything more current that I missed? Thanks, Jan Henrik ___ 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: Can't install octave
On 01/-10/-28163 20:59, Zbigniew Komarnicki wrote: I try to install octave (kde3, kde4 in erlier post) after fresh install FreeBSD 8.0 and freebsd-update to FreeBSD 8.0 p2 on i386 athlon-xp 1660 MHz, but with no success. I forgot to add that I csup-ed the ports tree today. If I try to rebuild x11-toolkits/fltk, I get the same error. My last build of fltk was done before the last commit to that port. The commit was based on this problem report: http://www.freebsd.org/cgi/query-pr.cgi?pr=143638 From the description of that pr: Note that fltk also has the problem of linking against its older version, so you have to deinstall the old version to do a successful build. I have not tested that as I am in no immediate need to rebuild fltk. HTH, Jan Henrik ___ 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: Can't install octave
On 03/05/2010 16:24, Jan Henrik Sylvester wrote: On 01/-10/-28163 20:59, Zbigniew Komarnicki wrote: I try to install octave (kde3, kde4 in erlier post) after fresh install FreeBSD 8.0 and freebsd-update to FreeBSD 8.0 p2 on i386 athlon-xp 1660 MHz, but with no success. I forgot to add that I csup-ed the ports tree today. If I try to rebuild x11-toolkits/fltk, I get the same error. My last build of fltk was done before the last commit to that port. The commit was based on this problem report: http://www.freebsd.org/cgi/query-pr.cgi?pr=143638 From the description of that pr: Note that fltk also has the problem of linking against its older version, so you have to deinstall the old version to do a successful build. I have not tested that as I am in no immediate need to rebuild fltk. There has been one more commit on that port: http://www.freebsd.org/cgi/cvsweb.cgi/ports/x11-toolkits/fltk/files/patch-src_filename_list.cxx.diff?r1=1.4;r2=1.5;f=h That one looks suspicious because (__FreeBSD_version = 73) make the clauses before obsolete. Before that commit, the condition was true for 8-STABLE and 9-CURRENT, but not for 8.0-RELEASE or 7-ANYTHING. The commit was supposed to fix 7.3-RELEASE (and probably 7-STABLE) but changed the behavior for 8.0-RELEASE, too, which probably has not been intended. I guess, (__FreeBSD_version = 73) should be replaced by (__FreeBSD_version = 73 __FreeBSD_version 79). The patch attached fixes the build for me on 8.0-RELEASE. (I have included the maintainer, gahr@, in Cc). Cheers, Jan Henrik diff -u x11-toolkits/fltk/files/patch-src_filename_list.cxx.orig x11-toolkits/fltk/files/patch-src_filename_list.cxx --- x11-toolkits/fltk/files/patch-src_filename_list.cxx.orig2010-02-25 14:36:59.0 +0100 +++ x11-toolkits/fltk/files/patch-src_filename_list.cxx 2010-03-05 16:39:03.0 +0100 @@ -14,7 +14,7 @@ #ifndef HAVE_SCANDIR int n = scandir(d, list, 0, sort); -#elif defined(__hpux) || defined(__CYGWIN__) -+#elif defined(__hpux) || defined(__CYGWIN__) || (defined(__FreeBSD__) (__FreeBSD_version = 96 || (__FreeBSD_version = 800501 __FreeBSD_version 90) || (__FreeBSD_version = 73))) ++#elif defined(__hpux) || defined(__CYGWIN__) || (defined(__FreeBSD__) (__FreeBSD_version = 96 || (__FreeBSD_version = 800501 __FreeBSD_version 90) || (__FreeBSD_version = 73 __FreeBSD_version 79))) // HP-UX, Cygwin define the comparison function like this: int n = scandir(d, list, 0, (int(*)(const dirent **, const dirent **))sort); #elif defined(__osf__) ___ 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
BIOS/FreeBSD? i7 laptop with constant fan and no c states on 8.0
I tried FreeBSD 8.0 on a Dell i7 laptop, but the fan is constantly spinning with maximal speed (and maximal noise). dev.cpu.0.cx_supported lists only C1. Maybe this is related to i386/135447 (but I am on 8.0/amd64 and not 7.2/i386). Even with powerd reducing the frequency to the lowest available, the fan still does not get quieter (it does on Windows 7). Is the BIOS doing something wrong or is it just FreeBSD not working with this fairly new processor, yet? Thanks, Jan Henrik ___ 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: zyd TEW-424UB
Albert Shih wrote: So I just buy a Trendnet TEW-424UB wifi usb adapter. I find this in the man zyd but when I plug my adapter (after add if_zyd_load=YES in my loader.conf and reboot) it's not working. According to http://linux-wless.passys.nl/query_part.php?brandname=TRENDware , there are two revisions of that device with totally different chipsets. Unfortunately, that is pretty common for wireless devices with only a few companies being exceptions. BTW: If you want to get a zyd device, be sure to get a ZD1211B version (see the source for hints which ones are). I had a ZD1211 (without B) that happened to cause kernel panics under load on FreeBSD 7. From my experience, ural or rum devices are stable. (I know nothing about uath, upgt, and urtw.) If you have that choice, cardbus or PCI tend to be better than USB, especially ath devices work well. Cheers, Jan Henrik ___ 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
disk with high frequency noise only on FreeBSD
The hard disk of a new computer makes annoying high frequency noises -- probably while seeking -- on FreeBSD 7.2-RELEASE. I booted up a Linux live CD and could not hear anything doing the same kind of access. (To test that, I put a ports tree on a FAT partition and did 'cat */*/Makefile' from FreeBSD and Linux.) Using sysutils/ataidle, I changed the AAM to different values with no effect. (The disk does not support APM.) What is different between FreeBSD and Linux in this regard? Is the disk probably broken? (I guess I would be out of luck with support if I cannot reproduce it on a different OS.) The disk is a WDC WD1600AAJS-07PSA0 with firmware 05.06H05. Thanks, Jan Henrik ___ 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: disk with high frequency noise only on FreeBSD
Tim Judd wrote: On 6/10/09, Jan Henrik Sylvester m...@janh.de wrote: The hard disk of a new computer makes annoying high frequency noises -- probably while seeking -- on FreeBSD 7.2-RELEASE. I booted up a Linux live CD and could not hear anything doing the same kind of access. (To test that, I put a ports tree on a FAT partition and did 'cat */*/Makefile' from FreeBSD and Linux.) Using sysutils/ataidle, I changed the AAM to different values with no effect. (The disk does not support APM.) What is different between FreeBSD and Linux in this regard? Is the disk probably broken? (I guess I would be out of luck with support if I cannot reproduce it on a different OS.) The disk is a WDC WD1600AAJS-07PSA0 with firmware 05.06H05. if it's the same high-frequency noise like an alarm, like a trouble No, it does not sound like a deliberate signal. It is more like high frequency scratching at the upper range of the hearable spectrum. I have heard a similar noise from other hard disks, but much more quiet and not quite as high. This one is extremely annoying. It cannot be due to overheating, since it is there from the first boot, but only on FreeBSD -- especially if I access many small files. Thanks, Jan Henrik ___ 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: Upgrade KDE from 4.2.2 to 4.2.3 fails
Odhiambo wrote: File /usr/ports/misc/kdeedu4/work/kdeedu-4.2.3/kalzium/src/solver/chem.ml, line 54, characters 43-54: Warning Y: unused variable nb_elements. File /usr/ports/misc/kdeedu4/work/kdeedu-4.2.3/kalzium/src/solver/chem.ml, line 1, characters 0-1: Error: /usr/local/lib/ocaml/facile/facile.cmi is not a compiled interface portupgrade -f math/facile http://mail.kde.org/pipermail/kde-freebsd/2009-April/005190.html I do not understand why that never happened. Cheers, Jan Henrik ___ 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: matlab 2009a
cat: /proc/cpuinfo: No such file or directory Error: Your computer's processor is missing the SSE2 instructions that are required for MATLAB to run correctly. For system requirements consult http://www.mathworks.com ... You have to mount linprocfs -- but there is a bug in the cpu features of linprocfs not returning SSE2, even if it is present. Compare the output of the following and see: /usr/compat/linux/bin/cat /proc/cpuinfo dmesg | grep Features Thus, you have to patch the matlab scripts to ignore that check. I have recently installed matlab2008b on FreeBSD 7.2-RELEASE changing the following in bin: In ldd and mexext: Linux) - FreeBSD) In matlab: #!/bin/sh - #!/usr/compat/linux/bin/sh In mbuild and util/oscheck.sh: Add an 'echo 1' line after the cpuinfo/sse2 line. Basic functionality is there. Maybe more similar changes are needed. Cheers, Jan Henrik ___ 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: USB WLAN Atheros and USB Ethernet FBSD 7.2
Marco wrote: iam thinking of building a router with usb wlan and usb ethernet controller attached. as the wlan device shall be an AP i would go for atheros stick. however, i'am unsure if anybody has expirience if or which devices should work out of the box with latest stable release. i read something about a uath device module but could not find it in my sys-tree. uath is only available in 8-CURRENT and I am not sure, if it does Host AP mode. (The same goes for upgt.) In 7.2-RELEASE (and 7-STABLE), the only usb wlan drivers are ural, rum, and zyd, but zyd does not do Host AP for what I know (and it was never stable for me). ural and rum both do Host AP. Maybe this is interesting for you: http://en.wikipedia.org/wiki/Comparison_of_Open_Source_Wireless_Drivers Anyhow, why does it have to be usb? From my own experience, usb devices do not work as well as Cardbus or (Mini)PCI. You will probably be much more happy, if you get an ath based MiniPCI card. Cheers, Jan Henrik ___ 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 create NTFS file system from FreeBSD?
Chris Rees wrote: 2009/4/11 Jan Henrik Sylvester m...@janh.de: Yuri wrote: I need to format NTFS partition to give HD to someone to write things mkntfs from sysutils/ntfsprogs should do it. Yuri had already written ONE LINE below your quote: I tried to use mkntfs from ports/ntfsprogs but it didn't finish after an extremely long time, 24hrs. Yes, sorry, I totally failed to make my point, since I scrapped that line and forgot about it writing the mail. (The important part was in the parenthesis you removed.) My point is that I had problems with ntfsresize from ntfsprogs-2.0.0 not working, while ntfsresize from ntfsprogs-1.13.1 was doing just fine. (I hit that twice -- on different computers.) Thus, I would suggest to try mkntfs from ntfsprogs-1.13.1, if mkntfs from ntfsprogs-2.0.0 fails. If the older mkntfs works, it would be another reason to revive the old port. ntfsprogs-2.0.0 was criticized, for example in the thread ending with this posting: http://www.redhat.com/archives/rhl-devel-list/2008-May/msg02306.html A developer from ntfs-3g that formerly worked on ntfsprogs recommends to use the older version: http://www.ntfs-3g.org/support.html#ntfsprogs I do not really know who is right, but ntfs-3g is actively developed while ntfsprogs is not, other people seem to trust ntfs-3g more than the newer version of ntfsprogs, and the arguments of the ntfs-3g developer sound reasonable. I wrote about it last year (before I actually hit problems): http://lists.freebsd.org/pipermail/freebsd-ports/2008-August/050157.html The reply was that there are no new problems known with the 2.0.0 version: http://lists.freebsd.org/pipermail/freebsd-ports/2008-August/050406.html I would like to have ntfsprogs-1.13.1 back -- as ports/ntfsprogs1 or by reverting ports/ntfsprogs. Thus, Yuri, please try and report back. Cheers, Jan Henrik ___ 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 create NTFS file system from FreeBSD?
Yuri wrote: I need to format NTFS partition to give HD to someone to write things mkntfs from sysutils/ntfsprogs should do it. (I did use mkntfs successfully with the 1.13.1 version, but never tried with 2.0.0. ntfsresize from 2.0.0 failed for me when 1.13.1 did work.) Jan Henrik ___ 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 list all the installed packages...
Olivier Nicole wrote: Is there a way to show a list of all installed packages that are not required by any other package? cd /var/db/pkg/ ; for i in *-* ; do if [ ! -e $i/+REQUIRED_BY ] ; then echo $i ; fi ; done Ultimately, that would give a list of software versus libraries. Not really. Only runtime dependencies are in +REQUIRED_BY, not build time dependencies. The question arise because, while installing a new machine, I found out that I have help2man installed, that is not required by any other package, that I did not install myself, that looks unneeded to me (until I may need it one day). So I would remove it; and would like to make a list of what is removable (that I did not install, and that is not required). help2man is a build dependency of flex, which is a build dependency of gstreamer. gstreamer is a runtime dependency of many application (wxwidget stuff; from kde world: amarok2, ktorrent; from gnome: gimp, pidgin, ...) If you update or rebuild gstreamer, help2man and flex will be reinstalled and the update takes longer than necessary. If you want to be able to update ports quickly, you should keep the build dependencies. Doing make pretty-print-build-depends-list in a ports directory gives you the build dependencies. Cheers, Jan Henrik ___ 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 list all the installed packages...
Alain G. Fabry wrote: On Fri, Mar 27, 2009 at 09:34:00AM +0100, Jan Henrik Sylvester wrote: Olivier Nicole wrote: Is there a way to show a list of all installed packages that are not required by any other package? cd /var/db/pkg/ ; for i in *-* ; do if [ ! -e $i/+REQUIRED_BY ] ; then echo $i ; fi ; done [...] If you want to be able to update ports quickly, you should keep the build dependencies. Doing make pretty-print-build-depends-list in a ports directory gives you the build dependencies. [...] How about pkg_cutleaves Is there anything about build dependencies in cutleaves? http://www.freebsd.org/cgi/cvsweb.cgi/ports/ports-mgmt/pkg_cutleaves/files/pkg_cutleaves?rev=1.2 I do not see it at a quick glance. Cheers, Jan Henrik ___ 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: best archiver? (for music)
Gary Kline wrote: my hearing is exceptionally good and while call myself an audiophile, [...] lectures. when i tried to cut the quality even by a bit it was evident immediately. rar compresses these file to If you care for quality (and call yourself an audiophile), you should read up on what you are doing before you start it. To compare different compression rates, you have to do both from the original. Applying lossy compression twice -- even with the same codec -- might give you artifacts that will not appear with just one run. For the same reason, you do not convert between lossy formats. Each might give different kinds of artifacts that you do not want to combine. (Of course, this does not really contradict the suggestions you got to try speex if you want to do a major reduction of bitrate for your voice mp3 files to save space.) The difference between lame with good settings and a bad mp3 encoder is probably bigger than between some better codec and mp3. Considering that, you should always stick to some --preset * options with lame, if you do not know better. Are you sure you can hear the difference between your flac originals and --preset standard lame encoded mp3? Consider a double blind test. This is probably all in the lame FAQ or similar sources. I do keep flac files after ripping CDs, too, but not because I think I can hear the difference between them and the ogg vorbis files I produce. I rather like the option to go to a different lossy format someday. (I must admit that I have never tested if I can hear the difference between an mp3 that come from the original or an mp3 that comes from a higher bitrate ogg. Actually, I doubt it.) I really do not see the point in saving one or two percent space by applying lzma/7z, rar, or similar compression. The savings in electricity by not doing that are better invested in a new hard drive. ;-) BTW: lzma is the default compression of 7z. GNU tar offers lzma, too, but without the 7z container. If you look at archivers/gtar history, you will see that it seems not to have finalized on the library (and format?): http://www.freebsd.org/cgi/cvsweb.cgi/ports/archivers/gtar/Makefile.diff?r1=1.63;r2=1.64 I am not an expert at all. You better read the lame (and ogg, speex, ...) manual and FAQ yourself that is hopefully written by some expert. Cheers, Jan Henrik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.1: iwi problem with intel 2200 pro wireless card
Erik Johnson wrote: I noticed on your loader.conf that you have the license at the end of WiFi Config. I placed mine at the beginning. as in the example below. Have you tried loading that first? I'm not sure if it makes a difference but might be worth a try. I'm interested in hearing back and keeping in contact since we share similar config for older hardware. --- legal.intel_iwi.license_ack=1 if_iwi_load=YES wlan_load=YES firmware_load=YES iwi_bss_load=YES iwi_ibss_load=YES iwi_monitor_load=YES The ordering in loader.conf does not matter. I abandoned iwi some time ago: http://lists.freebsd.org/pipermail/freebsd-current/2009-February/003125.html You might want to read the whole thread. Disabling bgscan is mentioned there somewhere. IIRC, that is a good idea. Do you really need ibss and monitor? Have you tried not loading three different firmwares at the same time? Last time I used iwi, I did not have to load the firmware manually. Up to 6.1 that was a requirement, but from 6.2 on, iwi could do it automatically. (And it worked better that way, IIRC.) Since the manual page tells you to do so, the loading of the firmware must have changed. When manual loading was required on 6.1, loading multiple at the same time was not a good idea. I never got monitor to receive any packages on 7.0, even after manually loading the firmware. It did work on 6.2, though. ibss was never really reliable. Cheers, Jan Henrik ___ 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: Flash9 and FreeBSD7.0 isssue
dhaneshk k wrote: I followed http://freebsd.langhans.com.pl/af/index.html To enable flash9 support for FreeBSD7.0 In contrast to the other replies, I have flash9 running with linux_base-fc-4_14 using compat.linux.osrelease=2.4.2 in a native firefox3 (not the linux version). It runs ok. Occasionally, the plugin crashes for a new page with flash, but it does not take firefox with it. Reloading the page usually fixes it. The important difference to your setup is that I run FreeBSD 7.1. Since the main bug rendering flash9 unstable was fixed in 7-STABLE between 7.1-RC1 and 7.1-RC2, I do not think anything will fix flash9 on FreeBSD 7.0. Maybe you get better results with osrelease=2.6.16 _and_ a newer linux_base, but that is not necessary. Updating to 7.1 is. noscript or at least flashblock is a must... The procedure: Get firefox3, flash9, and nspluginwrapper up to date, remove everything with nspluginwrapper as root and as your user, auto install every plugin as root (-a -i -v), and put links in your ~/.mozilla/plugins: cd ~/.mozilla/plugins/ ln -s /usr/local/lib/browser_plugins/npwrapper.libflashplayer.so You need linprocfs mounted to /usr/compat/linux/proc -- see the manpage of linprocfs. Cheers, Jan Henrik ___ 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: Flash9 and FreeBSD7.0 isssue
Warren Block wrote: On Fri, 6 Feb 2009, Jan Henrik Sylvester wrote: remove everything with nspluginwrapper as root and as your user, auto install every plugin as root (-a -i -v), and put links in your ~/.mozilla/plugins: Or just run nspluginwrapper -a -i as your web browser user. The only link I had to create by hand was for Java. The reason I recommended removing everything as root is that there could be an old version left from an old version of flash. For example, if you have 9.0r151 and 9.0r152 both wrapped in different directories, both will be picked up, which confuses firefox -- and you probably still have the vulnerability that was fixed with the upgrade. If there is just one wrapped version that all users link to symbolically, you just have to remember updating that after a portupgrade and everyone is up to date again. Of course, if you are the only user of your computer, keeping the wrapped versions in your home directory makes sense, too -- just avoid doing both. Cheers, Jan Henrik ___ 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: iwn driver on 7.1
Da Rock wrote: On Sun, 2009-01-18 at 14:17 -0600, Brandon Gooch wrote: I have a working driver for the Intel 4965, aka iwn(4), loaded on my Lenovo X300 running FreeBSD 7.1-RELEASE (amd64). This driver is a slightly-modified version of the iwn(4) driver backported from 8.0-CURRENT by Gavin Atkinson: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=221758+0+/usr/local/www/db/text/2008/freebsd-stable/20080928.freebsd-stable I was seeing the same symptoms described in these threads (among others): http://lists.freebsd.org/pipermail/freebsd-stable/2008-September/045264.html http://www.freebsd.org/cgi/getmsg.cgi?fetch=1334322+1338147+/usr/local/www/db/text/2009/freebsd-questions/20090118.freebsd-questions http://www.freebsd.org/cgi/getmsg.cgi?fetch=1418632+1421765+/usr/local/www/db/text/2009/freebsd-questions/20090118.freebsd-questions ...so I debugged and modified Gavin's driver for my system. The driver and the source tree diff can be downloaded here for any brave souls wanting to test it out: http://sites.google.com/site/bsdgooch/files I'm using the driver now to send this e-mail over a link to my TP-LINK TL-WR941ND access point (with WPA2). Feedback and bug reports would be useful. -brandon Sounds like you got to it before I did- thank god! :) Question though: have you got it figured for a channels yet? I'll test it for you and keep you updated with my results. Thanks for working on the driver! The only difference to the version of gavin that I could see is that the bands in iwn_bands that got commented out were brought back. Or did I miss something? Do you know why they were commented out and it was unnecessary? Or was it just to fix the crash? I did a few test runs: It does not crash immediately as the version from gavin, but the error I had with the perforce version iwn0: error, INTR=8200SW_ERROR,RX_INTR STATUS=0x1 iwn0: iwn_config: could not set power mode, error 35 is there -- in 3 out of 3 tries. So nothing improved there. (I hit that error on first use in about 50% of the cases before.) Moreover, at 3 out of 4 tries to 'kldunload if_iwn' after hitting the error (after '/etc/rc.d/netif stop iwn0' and 'ifconfig iwn0 down'), there was a crash: 2 page faults and 1 freeze. I have not had that with the perforce version. (Maybe once long ago, but I think I forgot to stop iwn0 at that time.) The one time I actually got the (WPA2) connection up, I was able to transfer with a similar speed as with the perforce version. Thus, for me, there are no improvement over the (old) perforce version. Probably by chance, but I had more crashes. I think the thread on stable@ should rather be continued than the one on questions@, but since Da Rock answered on questions@, I reinclude both. Cheers, Jan Henrik ___ 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: [Fwd: iwn driver on 7.1]
Sam Fourman Jr. wrote: From: Da Rock rock_on_the_web at comcen.com.au I've tried the driver on 7.0- 8.0 current is out of the question as [...] The driver patches compiles (iwn-7 from gavin), but when I load it goes through the channels and errors and finally dies with a full page fault. for what it is worth I too would very much like iwn working on freebsd 7.1, it works ok on 8-current See my previous post to stable@ in December, which was unfortunately unanswered: http://lists.freebsd.org/pipermail/freebsd-stable/2008-December/047142.html Short: The version from gavin crashes for me, too, but the initial version from perforce (before vap was introduced) works -- with some issues. There are only very few differences between those 2 versions. I guess someone with knowledge of vap would have to go through the perforce and current changes to find the stabilizing changes. Cheers, Jan Henrik ___ 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: Could not find package - using ports
Luca wrote: The reason that portupgrade -P was not using packages is that, by default it fetches packages built against the tree that's on the install disks, so there wont be any for updated ports. You can set portupgrade to fetch packages for the 7-stable development branch (you can google for how to do this). For the most part this will work, but occasionally there will be library problems. Thank you, now it's clear. I will try this as soon as I can. I did that and would not do it again for a massive upgrade: http://lists.freebsd.org/pipermail/freebsd-questions/2008-August/180336.html Using freebsd-update for a (minor version) upgrade to 7.1-RC1 and after that using 7.1-RELEASE packages for a portupgrade will probably take less time overall. See the 7.1-RC1 announcement on how to do the first part: http://lists.freebsd.org/pipermail/freebsd-stable/2008-December/047014.html When it is available, you should upgrade to 7.1-RELEASE, which will take less time with freebsd-update from 7.1-RC1 than from 7.0-RELEASE, since there are less configuration file changes to be merged. For the portupgrade, you should have in mind that portupgrade uses the ports tree to know what to upgrade to which version. Your ports tree is newer than the 7.1-RELEASE packages. Anyhow, if the newest package is not available but a newer one than the one installed, portupgrade usually works, too. Reading /usr/ports/UPDATING before is still advisable. You might still run into problems of the nature that kde was used to be build against openldap23-client at the time of 7.0-RELEASE, but the 7.1-RELEASE packages are build against openldap24-client and these two ports cannot coexist. With ports this is not a problem, since it can be build against either version. (AFAIR, this particular case will work out fine, but there was something else requiring manual work besides everything listed in UPDATING.) Probably not for 7.0-7.1, but in some cases removing all packages and reinstalling all takes less time than anything else. Cheers, Jan Henrik ___ 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: Kismet on FreeBSD 7.0-STABLE
Ludovit wrote: iwi0: Intel(R) PRO/Wireless 2200BG mem 0xfafef000-0xfafe irq 9 at device 3.0 on pci2 Monitor is broken on iwi on FreeBSD 7. I did report it during the 7.0-BETA, but there was at least one more report in the meantime. With exactly the same setup, I can use kismet with ural (ok), zyd (many broken packages), ral (ok), and ath (good, but see below). I do not receive a single package with iwi. I did replace my iwi miniPCI device by an ath one, which is more reliable anyhow. (iwi, as all Intel cards, occasionally dies and cannot reload firmware because of too little dma memory. That was reported a few times, too.) ath can monitor, even for longer periods of time, but if I do channel hopping in kismet, it often eventually stops receiving packages after a few minutes. Restarting kismet always fixes that. (I have had that with different ath cards.) iwi monitoring did work on 6.2, but often the card would not do regular networking after that until reboot and the problem with the firmware mentioned above was already present, although it was much better than on 6.1. For monitoring, you should either get a different card or try 6.X, 6-STABLE, or maybe 8-CURRENT. (I have no experience with the latter.) Cheers, Jan Henrik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Gimp-help not working after portupgrade
Mike wrote: After upgrading to Gimp 2.6.1 (on 6.4-RC1) I can't access the Gimp help files. graphics/gimp-app misses a dependency: http://lists.freebsd.org/pipermail/freebsd-gnome/2008-October/020978.html Install www/webkit-gtk2 and rebuild graphics/gimp-app. Please, report back if that solves the problem with gimp-help. If it does that might be an argument to add the dependency to gimp-app. (The pkg-plist of graphics/gimp-app must be fixed one way or the other.) Cheers, Jan Henrik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7-stable packages on 7.0-release system?
Torgeir wrote: I assume that it is not advisable, but what can I expect to happen if I try to use packages for 7-stable on a 7.0-release system? No, it is not advisable. I tried: http://lists.freebsd.org/pipermail/freebsd-questions/2008-June/177553.html As I said two weeks ago, that failure was predictable and the few offenders could be found, but I had another weird problem that could only be solved with recompile: http://lists.freebsd.org/pipermail/freebsd-questions/2008-July/179517.html For the opposite, using packages from an earlier point, compatibility is usually preserved, but not always, either: http://lists.freebsd.org/pipermail/freebsd-stable/2008-July/043950.html Not having newer binary packages for the latest RELEASE is a shortcoming on FreeBSD, but you will find many references that there are simply not enough resources. Cheers, Jan Henrik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 250GB hd: Can FreeBSD use 137GB (bios) as Linux or Windows do?
On 7/31/08, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Yesterday, I wrote about CANNOT READ BLK from my new hd that I filled via firewire: http://lists.freebsd.org/pipermail/freebsd-questions/2008-July/179646.html The response suggested to check for faulty hardware, which I am still trying to do. I found FreeBSD reporting the drive to have 128GB instead of 232GB as FreeBSD did when the drive was connected via firewire. Searching the web, I found one reference of someone else having problems with 128/137GB using the same (latest) bios on this five year old (Centrino) laptop (Acer TM800). FreeBSD has no such limit, at least not in recent versions (I'm using a 200 GB drive at this moment, and at home I have a system with a 500 GB and a 750 GB drive). Your problem is caused either by the BIOS I never said FreeBSD had a limit. With ddo, it works. (I am on 7.0.) lying to it (which is unlikely, because FreeBSD uses the BIOS value Yes, it is the bios. With ddo, the full disk is available; ddo supposingly does nothing but change the bios interrupt handlers. only for initial booting), or the hard drive itself lying. Does your Are you sure about only for initial booting? If that was the case, I would not understand why it shows ad0: 238475MB with ddo and ad0: 131072MB without. Moreover, I tried writing to a sector beyond 128GB unsuccessfully without ddo and successfully with ddo (using dd). drive have a jumper that causes it to report its capacity as 128GB for compatibility with older BIOSes? If so, remove the jumper and try again. These is no such jumper. With Linux and Windows seeing the correct size (without ddo), the drive must report it somehow correctly. Either your claim that FreeBSD is not relying on the bios is wrong, or I understand even less about the interaction of bios, drive, ddo handler, and os than I thought I would. (Please, enlighten me, if you know more.) Thanks for your input! Cheers, Jan Henrik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 250GB hd: Can FreeBSD use 137GB (bios) as Linux or Windows do?
I guess I should have put it more concise as some important details were lost in the middle of the background story. --- The important part: --- If I boot the FreeBSD 7.0-RELEASE livefs CD, I have my 232GB hd limited to 128GB. (According to dmesg and some dd writing tests.) If I boot the dynamic drive overlay MBR that changes the INT13 bios routines and let it boot the livefs CD, FreeBSD can access all 232GB. These two cases happen with the same MBR and the same content on the drive. --- (Important part ending) --- From my limited understanding: This cannot be about the FreeBSD installation transfered by firewire, since it is long gone. This cannot be about the FreeBSD MBR, since it is not involved. This is not about the partition table, since it is the same. Doing the same with a Linux live CD (Knoppix), I can access the whole drive in both cases. Windows reports 232GB, too, but according to this (German) posting http://www.acer-userforum.de/thread.php?postid=40207 writing above 128GB will wrap around for the 855GME chipset driver (I have 855PM). The posting claims ddo would solve it, which I cannot understand, if the Windows driver ignores the bios information. (The posting is about Acer Travelmate 661. I got the 800 from the same time.) My laptop is more than five years old and I have got the latest bios for years, apparently without 48bit LBA. I am kind of lost. I cannot understand the disassembled MBR and even if I could, I do not think I would want to create my own boot manager / INT13 handler. I guess reading FreeBSD source code would be next... but I am not very confident there, either. The alternative is that my understanding of the problem is totally wrong. Thanks for more helping to think through this mess of information I got during the last day. Cheers, Jan Henrik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
New harddisk: CANNOT READ BLK Cause?
I got a new harddisk for my laptop, attached it via firewire, used dump 0aLf - / | restore xf - (from the FAQ), and swapped it with my internal one. During that, I also migrated /var and /usr to separate bsdlabels. On reboot during fsck (ad0s1f), I got: CANNOT READ BLK: 251403296 CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 251403296, 251403297, 251403298, 251403299, LOOK FOR ALTERNATE SUPERBLOCKS? yes 32 is not a file system superblock SEARCH FOR ALTERNATE SUPER-BLOCK FAILED. YOU MUST USE THE Is there a problem with the harddisk? Did I do anything wrong? How do I find out? Since I never used bsdlabel and newfs by hand before for more than trivial cases, I might very well have messed something up. Here is what I came up with. Since I forgot to change it before swapping harddisks, I came up with this simple fstab: /dev/ad0s1b none swap sw 0 0 /dev/ad0s1a / ufs rw 1 1 /dev/ad0s1e /var ufs rw 1 2 /dev/ad0s1f /usr ufs rw 1 2 This is my bsdlabel for ad0s1: # /dev/ad0s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 2097152 164.2BSD 2048 16384 28552 b: 4194304 2097168 swap c: 3145687020unused0 0 # raw part, don't edit e: 16777216 62914724.2BSD 2048 16384 28552 f: 251658240 230686884.2BSD 2048 16384 28552 g: 33554432 274726928unused0 0 h: 6287342 308281360unused0 0 This is the fdisk partition ad0s1: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 314568702 (153597 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 124/ head 254/ sector 63 Anything else? (I could probably recall most of the commands I issued.) Thanks in advance for any help, Jan Henrik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Binary upgrade from legacy version + ports
Svein wrote: Is there a problem using the prebuilt packages from STABLE on a RELEASE box? If I want to run RELEASE, and still use the latest packages? The ABI is consistent between STABLE and RELEASE, right? Yes, there is a problem. See my posting here: http://lists.freebsd.org/pipermail/freebsd-questions/2008-June/177553.html Unfortunatelly, I have not got an answer, but it is obvious packages using this new symbol must fail: http://lists.freebsd.org/pipermail/cvs-src/2008-May/091586.html The question is, if other package may fail as well. I have had one more error that went away after recompiling a STABLE package: http://lists.freebsd.org/pipermail/freebsd-gnome/2008-July/020520.html I do not know if this is related, though. If you find out more, please, let me know. Cheers, Jan Henrik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
7.0 with packages-7-stable -- how to fix system
Since rebuilding 300 ports on my 7.0 system would have taken too long after the gettext bump, I used packages-7-stable for the portupgrade -- I should have known better... The kdevelop portupgrade failed with: /libexec/ld-elf.so.1: /lib/libc.so.7: version FBSD_1.1 required by gtar not found Searching all executables in /usr/local/ with readelf for FBSD_ but not FBSD_1.0, I have only found [EMAIL PROTECTED] in files from coreutils, dirmngr, gnupg, gpgme, gtar, and wget. Thus, I rebuild these. Now gtar starts and https in Firefox works again. Is my system back to a sane state or do I have to expect more problems, if I do not rebuild everything that came as 7-stable package? Thanks, Jan Henrik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Is Skype voice calling working for anyone? I get Call failed: problem with audio playback
Yuri wrote: Any time I am trying to make a call I get: Call failed: problem with audio playback Did you read /usr/ports/UPDATING (20080318)? You should upgrade to compat.linux.osrelease=2.6.16 with linux_base-fc6. Maybe you might want to read the thread linux 2.6 on 7.0-RELEASE on freebsd-emulation first. First one this month: http://lists.freebsd.org/pipermail/freebsd-emulation/2008-June/thread.html I get the same error message with compat.linux.osrelease=2.4.2 (fc-4). Changing to the totally unsupported compat.linux.osrelease=2.4.20, skype seems to work. As far as I understood, this is just luck, because 2.4.2 is the only supported 2.4 version and 2.6.16 the only (experimentally) supported 2.6 version. (Other Linux syscalls are not implemented.) Unsurprisingly, I can reproducibly crash googleearth with 2.4.20, while it runs fine with 2.4.2 -- 2.4.20 really only helps skype. For me, running evil skype in an unsupported setting is acceptable. Cheers, Jan Henrik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Linux compat library error: ELF file OS ABI invalid
system for a couple of days while it builds. The Linux version was Did you try the 7-STABLE package? It will probably work on 7.0-RELEASE, too. ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7-stable/editors/openoffice.org-2.4.0_3.tbz ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Interrupt storm with 7.0
lysergius2001 wrote: Recently installed 7.0-RELEASE on an i386 as upgrade from 6.3-RELEASE and now have a continuous interrupt storm on IRQ17. This is a shared IRQ for ath0 and echi0. Never saw this on 6.3??? Any suggestions? Just another contribution to the collection of interrupt storms maybe related to ath: Whenever I plug in my ath1 on cardbus0, I get exactly one storm: interrupt storm detected on irq10:; throttling interrupt source ath1: Atheros 5212 mem 0xd022-0xd022 irq 10 at device 0.0 on cardbus0 Anyhow, I am not sure, if it is really ath causing this. During boot, I get one storm, too, that is on irq 10, but my ath0 on pci2 is on irq 9: ath0: Atheros 5212 mem 0xd020-0xd020 irq 9 at device 4.0 on pci2 [...] interrupt storm detected on irq10:; throttling interrupt source I do not get interrupt storms on irq 9 and I have already had that storm before I replaced my minipci iwi0 with ath0: http://lists.freebsd.org/pipermail/freebsd-current/2007-October/078684.html The reply to that posting was that it is probably related to USB: http://lists.freebsd.org/pipermail/freebsd-current/2007-October/078687.html Moreover, I have a bunch of other devices sharing irq 10: vgapci0: VGA-compatible display port 0x3000-0x30ff mem 0xd800-0xdfff,0xd010-0xd010 irq 10 at device 0.0 on pci1 uhci0: Intel 82801DB (ICH4) USB controller USB-A port 0x1800-0x181f irq 10 at device 29.0 on pci0 uhci2: Intel 82801DB (ICH4) USB controller USB-C port 0x1840-0x185f irq 10 at device 29.2 on pci0 ehci0: Intel 82801DB/L/M (ICH4) USB 2.0 controller mem 0xd000-0xd3ff irq 10 at device 29.7 on pci0 fwohci0: Texas Instruments TSB43AB21/A/AI/A-EP mem 0xd0218000-0xd02187ff,0xd021-0xd0213fff irq 10 at device 7.0 on pci2 pcm0: Intel ICH4 (82801DB) port 0x1c00-0x1cff,0x18c0-0x18ff mem 0xdc00-0xddff,0xd800-0xd8ff irq 10 at device 31.5 on pci0 On our problematic irq, we both have got echi0. Thus, the second storm I get upon attaching ath1 might not be directly caused by ath. No suggestions, just more data. Cheers Jan Henrik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to see UNICODE character number?
On Wednesday 14 November 2007 02:19:35 am Yuri wrote: All programs just show the character itself when I paste it :-) Have you tried kcharselect ? Tried it now. When I paste the character to the box in the bottom and press Enter nothing happens. I would like to see it's UNICODE number (like 9991;) Have a look at the uft8 editor Yudit (in ports). The interface is kind of weird for a Unix program, but it shows 'Glyph Info' for each character (at least for 2-byte characters) and you can paste them. Cheers, Jan Henrik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
WPA
kalin wrote: having trouble to get the wi0 interface up with WPA. There is no WPA support in wi according to: http://www.freebsd.org/projects/ideas/#p-wi HTH, Jan Henrik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Reproducible panic of 6.2 on double mount ntfs
Hello! With '/dev/ad0s1 /mnt/ad0s1 ntfs ro,noauto 0 0' in fstab, if I issue 'mount /mnt/ad0s1' twice, I always get a panic with the message: panic: lockmgr: locking against myself If I issue 'mount_ntfs /dev/ad0s1 /mnt/ad0s1' twice, there is no panic. I only get 'mount_ntfs: /dev/ad0s1: Operation not permitted' as expected. For a different (non-ntfs) filesystem, using plain mount twice gives 'Operation not permitted', too. System is: FreeBSD janh.freebsd 6.2-RELEASE-p4 FreeBSD 6.2-RELEASE-p4 #0: Thu Apr 26 17:55:55 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP i386 Can anyone reproduce this? Just for my curiosity: What is mount doing differently than mount_ntfs? Thanks, Jan Henrik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Reproducible panic of 6.2 on double mount ntfs
Jan Henrik Sylvester wrote: With '/dev/ad0s1 /mnt/ad0s1 ntfs ro,noauto 0 0' in fstab, if I issue 'mount /mnt/ad0s1' twice, I always get a panic with the message: panic: lockmgr: locking against myself I should have done some more intelligent research before... kern/89966 (6.0-STABLE) is exactly what I see. (The difference between my mount+fstab and manual mount_ntfs is that the first includes ro.) kern/104393 (7.0-CURRENT) does not even have the ro, but is otherwise the same. kern/71391 (5.2.1-RELEASE) might be related... I wonder why a panic that seems to be so easy to reproduce is not analyzed and fixed -- probably ntfs is simply not very important to anyone and the panic can be avoided quite easily. Since I should be able to avoid issuing repeated execution of mount with some concentration (I ran into this four times now), it should not be too much of an issue for me, either... Regards, Jan Henrik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: error in portupgrading audio/libmtp : bad c++ code ?
Beni wrote: When trying to portupgrade audio/libmtp (and amarok), I'm getting this error : Bad C++ code. I asked the maintainer... it is known, it is being worked on, and the problem and fixes / workarounds are documented here: http://www.freebsd.org/cgi/query-pr.cgi?pr=115218 If you simply pkg_delete the old version before you compile, it will work (because it does not pick up the old header). HTH, Jan Henrik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Keyboard layout problem with xkeyboard-config-1.0
After updating to xkeyboard-config-1.0 (from 0.9_3) yesterday and booting for the first time after the update today, the KDE Keyboard Tool tray icon displays err with tooltip Error changing keyboard layout to 'us' (or 'de(deadgraveacute)' depending on what I try). Indeed, the keyboard layout does not change. I now have a weird keyboard layout with 'y', 'z', and most symbols being in place of the German keyboard layout, but the umlauts give some Greek letters and 'sz' and all 'Alt Gr' combinations are dead. (I have 'keymap=german.iso' in rc.conf.) I did a 'portupgrade xkeyboard-config'. Do I have to do some forced recursive recompile? I hesitate a bit, since it would involve synaptics, xf86-input-*, xf86-video-*, xorg, xorg-drivers, and xorg-server. Or is there anything else that might be wrong and easier to correct? (All my ports are up to date with current portsnap snapshot.) Thanks, Jan Henrik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Keyboard layout problem with xkeyboard-config-1.0
Answering myself: Jan Henrik Sylvester wrote: After updating to xkeyboard-config-1.0 (from 0.9_3) yesterday and booting for the first time after the update today, the KDE Keyboard Tool tray icon displays err with tooltip Error changing keyboard layout to 'us' (or 'de(deadgraveacute)' depending on what I try). Indeed, the keyboard layout does not change. After reading the x11@ archive, I found this: http://www.freebsd.org/cgi/query-pr.cgi?pr=114876 For me, it was not /usr/local/lib/X11/xkb/compiled that was missing, but /usr/local/share/X11/xkb/compiled. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rdesktop: segmentation fault under xorg 7.2
[EMAIL PROTECTED] wrote: On Tue, 5 Jun 2007, Jan Henrik Sylvester wrote: For me, rdesktop works -- I have all my ports upgraded... ldd `which rdesktop` says? /usr/local/bin/rdesktop: libcrypto.so.4 = /lib/libcrypto.so.4 (0x280a9000) libX11.so.6 = /usr/local/lib/libX11.so.6 (0x2819c000) libc.so.6 = /lib/libc.so.6 (0x28282000) libXau.so.6 = /usr/local/lib/libXau.so.6 (0x28367000) libXdmcp.so.6 = /usr/local/lib/libXdmcp.so.6 (0x2836a000) librpcsvc.so.3 = /usr/lib/librpcsvc.so.3 (0x2836f000) Jan Henrik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
'pkg_create -b iwi-firmware-kmod-3.0_2' failed
I produced packages of all installed ports with 'pkg_create -b' to transfer them to another machine. iwi-firmware-kmod failed: janh# pkg_create -b iwi-firmware-kmod-3.0_2 tar: Removing leading '/' from member names janh# pkg_delete iwi-firmware-kmod-3.0_2 janh# pkg_add iwi-firmware-kmod-3.0_2.tbz tar: /boot/modules/iwi_bss.ko: Cannot stat: No such file or directory tar: Error opening archive: Empty input file: Inappropriate file type or format pkg_add: extract_plist: can not invoke 77 byte tar pipeline: /usr/bin/tar cf - /boot/modules/iwi\_bss.ko|/usr/bin/tar --unlink -xpf - -C / I see that the port has: NO_PACKAGE= this is a modified version of a restricted firmware Anyhow, every other port that may not have a public package succeeded to pkg_create just fine. Should package creation work on NO_PACKAGE ports or not? Should I report to the maintainer? Thanks Jan Henrik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rdesktop: segmentation fault under xorg 7.2
For me, rdesktop works -- I have all my ports upgraded... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Thunderbird 2.0 dumps core on second file open op
Drew Sanford wrote: No, but I am seeing it core dump rather strangely. Each time it starts up, I can open a file dialog box to save an attachment or attach a file one time just fine. The second time I try to attach or save a file on any start up, it crashes. BTW: Firefox 2.0.X does the same. Use Save Link As... a few times in a row (2 is usually sufficient) and have a core dump. I had this happen with Firefox 2.0.X and Thunderbird 2.0.0 that I compiled myself as well as with this one (on 6.2-RELEASE): ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6-stable/www/firefox-2.0.0.3,1.tbz I guess someone should file a bug report... Here are my packages that are required by Firefox in case you want to compare versions: atk-1.12.3needs updating (port has 1.18.0) desktop-file-utils-0.11 needs updating (port has 0.12) expat-2.0.0_1 = up-to-date with port firefox-2.0.0.3,1 = up-to-date with port freetype2-2.2.1_1 = up-to-date with port glib-2.12.4 needs updating (port has 2.12.11) gtk-2.10.6_2 needs updating (port has 2.10.11) jpeg-6b_4 = up-to-date with port libIDL-0.8.7 needs updating (port has 0.8.8) libXft-2.1.7_1 = up-to-date with port libdrm-2.0.2= up-to-date with port libiconv-1.9.2_2= up-to-date with port nspr-4.6.3needs updating (port has 4.6.6) nss-3.11.3needs updating (port has 3.11.5) pango-1.14.7 needs updating (port has 1.16.3) perl-5.8.8 = up-to-date with port pkg-config-0.21 = up-to-date with port png-1.2.12_1 needs updating (port has 1.2.14) xorg-fonts-encodings-6.9.0_1 = up-to-date with port xorg-fonts-truetype-6.9.0 = up-to-date with port xorg-libraries-6.9.0_1 = up-to-date with port ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Thunderbird 2.0 dumps core on second file open op
Michel Le Cocq wrote: I think it's a global thunderbird 2 bug, because i have exactly the same trouble ona mac os 10.4 with a binary update. I do not think it is exactly the same -- see below. Howard Goldstein a écrit : Jan Henrik Sylvester wrote: Drew Sanford wrote: No, but I am seeing it core dump rather strangely. Each time it starts up, I can open a file dialog box to save an attachment or attach a file one time just fine. The second time I try to attach or save a file on any start up, it crashes. BTW: Firefox 2.0.X does the same. Use Save Link As... a few times in a row (2 is usually sufficient) and have a core dump. I had this happen with Firefox 2.0.X and Thunderbird 2.0.0 that I compiled myself as well as with this one (on 6.2-RELEASE): ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6-stable/www/firefox-2.0.0.3,1.tbz I guess someone should file a bug report... Looks like the same problem at ports/105589, perhaps it needs to be reopened, seems to be the same problem. Haven't tried the workaround. Not sure how to do that on someone else's gnats. (cc to the gnats person who closed it) After reading the discussion in the PR, I renamed libgnome-2.so.0 and tried again: no crashes with Firefox 2.0.3 or Thunderbird 2.0.0. I do run KDE -- I probably should compile Firefox and Thunderbird without the gnome dependencies to solve it for me. The relevant packages seem not to be among the Firefox package dependencies, but: libgnome-2.16.0 needs updating (port has 2.18.0) gnome-vfs-2.16.1 needs updating (port has 2.18.1) I guess I would have to update all gnome packages from 2.16 to 2.18 to see if it helps... but since Howard Goldstein rebuild all his ports, he can probably confirm that this happens with the current ports. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Qemu audio with win2k3 guest.
Hello! I run XP on QEMU 0.9.0 with sound (FreeBSD 6.2, KQEMU 1.3.0.p11). As it is mentioned in the QEMU FAQ, the driver for es1370 is automatically installed by Windows. Probably this applies to 2003, too. qemu -hda winxp.img -m 256 -soundhw es1370 -localtime -net nic -net user -cdrom /dev/acd0 HTH Jan Henrik ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: skype on freebsd problem
Hello, I install skype from port, but skype test call give me problem with sound device. I use freebsd6.2 with kde 3.5. Any suggestions? Did KDE use the sound system recently? After about a minute without sound, KDE releases it. Then it is free for Skype. (I am not sure, if the explanation is really correct, but waiting for a minute with KDE not using any sounds helped me with the same error.) Jan Henrik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.2 -- Linksys wusb11 wireless supported?
The only usb wlan driver in FreeBSD is ural (Ralink RT2500USB). Also, ndis (Windows driver wrapper) does not work for usb devices. Thus, you are out of luck. http://en.wikipedia.org/wiki/Comparison_of_Open_Source_Wireless_Drivers (Some people seem to be working on porting rum and zyd from OpenBSD to FreeBSD, but that won't help you, either.) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
6.1 to 6.2-RC2: iwi-firmware-kmod and monitor/ibbs
I could not find documentation about iwi-firmware-kmod and things do not work the way I expect them. If this is not the right place to ask this question, please, point me to an appropriate mailing list or forum. How do I use the ibbs and monitor mode with iwi-firmware-kmod (6.2-RC2)? If I try to go to mediaopt ibbs, I always get Device not configured. I would like to use kismet. My configuration file, which seemed to work with iwi-firmware (6.1), contains source=radiotap_bsd_b,iwi0,iwikismet. I only ever got a few packages with iwi-firmware (6.1), before it stopped working and sometimes crashed. With iwi-firmware-kmod (6.2-RC2), Kismet always immediately stops with a FATAL error, seemingly because promiscuous mode is not available. If I manually load iwi_monitor, dmesg gives me firmware_get: failed to load firmware image iwi_monitor iwi0: could not load firmware iwi0: promiscuous mode disabled -- I guess I should not do that. Without manually loading iwi_monitor, I get iwi0: could not allocate firmware DMA memory iwi0: promiscuous mode disabled -- something seems to be wrong here, too. How are ibbs and monitor supposed to work? Should I manually load the firmware or not? How do I invoke ibbs at all? Trying to switch between bbs, ibbs, and monitor, I noticed a few oddities: janh# ifconfig iwi0 down janh# ifconfig iwi0 mediaopt ibbs ifconfig: SIOCSIFMEDIA (media): Device not configured janh# ifconfig iwi0 mediaopt monitor janh# ifconfig iwi0 mediaopt bbs ifconfig: SIOCSIFMEDIA (media): Device not configured janh# ifconfig iwi0 -mediaopt monitor janh# kldstat | grep iwi 301 0xc383a000 d000 if_iwi.ko janh# kldload iwi_monitor janh# kldstat | grep iwi 301 0xc383a000 d000 if_iwi.ko 321 0xc4843000 2f000iwi_monitor.ko janh# kldunload iwi_monitor janh# kldstat | grep iwi 301 0xc383a000 d000 if_iwi.ko janh# kldload iwi_bbs kldload: can't load iwi_bbs: No such file or directory janh# kldload iwi_ibbs kldload: can't load iwi_ibbs: No such file or directory janh# ls /boot/modules iwi_bss.ko iwi_ibss.ko iwi_monitor.ko kqemu.kolinker.hints Something is wrong here, I guess. With iwi-firmware (6.1), I used to load the required firmware with iwicontrol and set the mediaopt with ifconfig. Many reboots were required to get back to a defined state. I had many crashes using ifconfig iwi0 [...] even without ibbs or monitor mode involved. With iwi-firmware-kmod (6.2-RC2), I had not a single crash, but sometimes lost the bbs connection for a few seconds and I could not get ibbs and monitor to work at all. I guess it is an improvement (stability over functionality). Oh, btw, is there any way to check the status of the radio button as with iwicontrol iwi0 -r on 6.1? A change usually shows up at dmesg, but I would like to get the current state. Thanks Jan Henrik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
