Re: Alternative windowmanagers
On 05/08/2011 20:12, Christian Barthel wrote: Are there any other window manager worth looking? What is your window manager? When I'm not running KDE I like using Window Maker. -- 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: Uarduno driver compile fault?
On 08/08/2011 03:35, Axel Barnabas wrote: Has anyone successfully compiled the comms/uarduno driver? I keep getting I can confirm that it compiles fine on my 8.2-R-p2 amd64. Just make sure you grab the latest Makefile patch from PRs, otherwise it will mess up your /boot/kernel directory. Michael ___ 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
net/netatalk afpd causes abort on amd64?
Hi. After upgraded to current portversion of netatalk, I cannot start netatalk. I do rc.d/netatalk start then afpd fails SIGABRT. On i386 freebsd, netatalk/afpd works fine. Any solutions to use netatalk on amd64? pid 19160 (afpd), uid 0: exited on signal 6 (core dumped) pid 19175 (afpd), uid 0: exited on signal 6 (core dumped) pid 19188 (afpd), uid 0: exited on signal 6 (core dumped) -- kiwao m...@club.kyutech.ac.jp ___ 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: net/netatalk afpd causes abort on amd64?
On 8/8/11 7:46 AM, Kouichiro Iwao wrote: Hi. After upgraded to current portversion of netatalk, I cannot start netatalk. I do rc.d/netatalk start then afpd fails SIGABRT. On i386 freebsd, netatalk/afpd works fine. Any solutions to use netatalk on amd64? pid 19160 (afpd), uid 0: exited on signal 6 (core dumped) pid 19175 (afpd), uid 0: exited on signal 6 (core dumped) pid 19188 (afpd), uid 0: exited on signal 6 (core dumped) If you compiled with Zeroconf support (the default), then you need to make sure Avahi is running. Add avahi_daemon_enable=YES and avahi_dnsconf_enable=YES to rc.conf and reboot (or run the two rc.d scripts). Alternatively, you can rebuild netatalk without Zeroconf support. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ 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: Alternative windowmanagers
I have always enjoyed using Window Maker. Unfortunately there does not seem to be much activity around it anymore. ___ 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: net/netatalk afpd causes abort on amd64?
Heya, I just struggled with this the last few days and found that the problem lies in zeroconf. I didn't get any error message at all. Adding the flag -nozeroconf to the share the afpd.conf file made it work for me. I use avahi now to make the share available on the network. greets Arno Beekman On 8 aug 2011, at 13:46, Kouichiro Iwao wrote: Hi. After upgraded to current portversion of netatalk, I cannot start netatalk. I do rc.d/netatalk start then afpd fails SIGABRT. On i386 freebsd, netatalk/afpd works fine. Any solutions to use netatalk on amd64? pid 19160 (afpd), uid 0: exited on signal 6 (core dumped) pid 19175 (afpd), uid 0: exited on signal 6 (core dumped) pid 19188 (afpd), uid 0: exited on signal 6 (core dumped) -- kiwao m...@club.kyutech.ac.jp ___ 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: Alternative windowmanagers
On 08/07/2011 02:17 PM, Volodymyr Kostyrko wrote: 07.08.2011 16:24, Matthias Apitz wrote: El día Sunday, August 07, 2011 a las 12:05:12AM +0300, Volodymyr Kostyrko escribió: 05.08.2011 22:12, Christian Barthel wrote: As a Gnome 2.3x user too, I am also a bit nervouse. Gnome 3 is a big mistake. And there are also rumors that Gnome will be Linux only. Maybe, we will never see Gnome3 under FreeBSD, but this is not a tragedy :) Once a year I build up a Gnome or KDE to look at all this stuff... Then I go back to E17. I have installed /usr/ports/x11-wm/enlightenment Could you please point me to a starters guide for beginners? Normaly I'm using KDE 3.5.10, but will check it out. Thanks Try http://www.enlightenment.org for example. I'm starting it from .xsession like this: exec /usr/local/bin/enlightenment_start I used XFCE + Compiz + Emerald for a few years. Yes, bloated I know. It was not bloated enough (or so I thought) to matter. Now I use e17. It's light and useful, the features that increase productivity more than make-up for any limitations due to bugs. Make sure that Hardware acceleration is on however, I find the software acceleration a bit too crashy. ___ 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: High interrupt rate
On 8/7/11, Mario Lobo l...@bsd.com.br wrote: On Sunday 07 August 2011 18:34:27 b. f. wrote: I know 75% idle is not bad but this machine, when not under load on a saturday night like today, used to be at around 98% idle 99% of the time. Now its is at 72% idle 99.9% of the time. It has been like this all day. The only things with a high interrupt rate are cpu0: timer 46922025 2000 cpu1: timer 46918117 1999 What could be causing this? I don't know that 2 timer interrupts per-cpu, per kern.hz, is altogether unexpected for some configurations, under some conditions. What happens if you boot with kern.hz=100 in /boot/loader.conf, or set via the loader command line? What happens if you remove the DEVICE_POLLING option from your kernel (and _not_ just disable polling per-device)? What is the output from sysctl kern.timecounter kern.eventtimer? b. Thanks b. ! [~]sysctl kern.timecounter kern.timecounter.tick: 1 kern.timecounter.choice: TSC(-100) ACPI-safe(850) i8254(0) dummy(-100) kern.timecounter.hardware: ACPI-safe kern.timecounter.stepwarnings: 0 kern.timecounter.tc.i8254.mask: 65535 kern.timecounter.tc.i8254.counter: 39201 kern.timecounter.tc.i8254.frequency: 1193182 kern.timecounter.tc.i8254.quality: 0 kern.timecounter.tc.ACPI-safe.mask: 16777215 kern.timecounter.tc.ACPI-safe.counter: 1055460 kern.timecounter.tc.ACPI-safe.frequency: 3579545 kern.timecounter.tc.ACPI-safe.quality: 850 kern.timecounter.tc.TSC.mask: 4294967295 kern.timecounter.tc.TSC.counter: 1200011080 kern.timecounter.tc.TSC.frequency: 1995401152 kern.timecounter.tc.TSC.quality: -100 kern.timecounter.smp_tsc: 0 kern.timecounter.invariant_tsc: 1 [~]sysctl kern.hz kern.hz: 1000 [~]sysctl kern.eventtimer sysctl: unknown oid 'kern.eventtimer' I'll wait for your views on those before disabling polling on the kernel and hz=100. It looks like your interrupt rate, while probably higher than needed, is not unexpectedly high for your configuration. But you can lower it if you want to do so. You are using a system before the introduction of the new eventtimer code. If you use 9.x, that has the new code and some other timer-related improvements, and you are not performing polling, then you can achieve a large reduction in the number of timer interrupts when the system isn't busy. You can still achieve a reduction on 8.x, but the reduction usually won't be as large as on 9.x under similar conditions. To reduce timer interrupts on an idle system running 8.x or 9.x, if you do not need to poll (most systems do not), remove DEVICE_POLLING from your kernel, and lower kern.hz to a suitable value -- 100 or 250, for example. For many workloads, a lower value is not only adequate, but may also be better in some ways. Also, you may want to consider using your TSC as the system timecounter, because it is usually more efficient to do so. This may not work for SMP, because if there are multiple TSCs on your system, they may not be synchronized. In 9.x, there is a test for synchronization, and the TSCs are preferred to the ACPI-safe timer if they satisfy this test and meet some other requirements. In 8.x, the user has to tell the system that it is safe to use the TSCs by adding: kern.timecounter.smp_tsc=1 to /boot/loader.conf. If you are not putting your cores into the C3 state, then you could try setting this via the loader command line, booting, and then seeing if the kern.timecounter.tc.TSC.quality is positive, kern.timecounter.hardware is TSC, and everything is working as expected. If the results are satisfactory, then you could add the above entry to /boot/loader.conf. But it would be better to do this on 9.x, where there are some added safeguards. 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
make readmes no longer builds individual ports' README.html files?
Having been away from FreeBSD for a while, I'm still catching up with all the changes that took place while I was on hiatus, so bear with me here. :-) Trying to construct the ports' README.html files with: cd /usr/ports make readmes Much to my surprise, this only creates README.html at the top level and within each category, but nothing under the individual ports' directories. When did this change, and why? Mailing list search has turned up nothing useful on the subject. Or maybe I'm just doing it wrong? :-) Thanks. -- Conrad J. Sabatier conr...@cox.net ___ 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
