Re: a couple of things I dislike about BSD
On 7/23/2012 02:39, Pierre Abbat wrote: 1. When I run bc, I frequently edit the previous line and make a change: 15/56 .26785714285714285714 a(15/56) .26171350240120506395 a(15/56)*45/a(1) 14.99507912917598589467 In Linux, I hit uparrow and edit the line. In DFBSD, I have to type the whole line again. This is, I'm sure, a license issue; the readline library in DFly is GNU readline. The bugs section says It’s too big and too slow, so why not write a BSD version that's smaller and faster? (The calculation relates to the upper slope of my future house's roof.) That's a shell configuration issue, not a readline issue. I edit previous commands just fine just as you suggest. Pick the right shell and set it up via the .profile/.??rc/ etc files and it will work as you want. 2. less in Linux saves the screen when it starts and restores it when it ends. In DFly it doesn't; it leaves a screenful of the file visible when it exits. I've seen this via SSH but it doesn't do it the console. I'm sure it's another config issue, but being lazy I just use cat and scroll backwards rather than taking the time to fix it. :) John
Re: a couple of things I dislike about BSD
On Mon, 23 Jul 2012 02:39:24 +0200, Pierre Abbat p...@phma.optus.nu wrote: 1. When I run bc, I frequently edit the previous line and make a change: 15/56 .26785714285714285714 a(15/56) .26171350240120506395 a(15/56)*45/a(1) 14.99507912917598589467 In Linux, I hit uparrow and edit the line. In DFBSD, I have to type the whole line again. This is, I'm sure, a license issue; the readline library in DFly is GNU readline. The bugs section says It’s too big and too slow, so why not write a BSD version that's smaller and faster? (The calculation relates to the upper slope of my future house's roof.) Please try: http://87.78.98.243/tmp/bc_libedit.diff Sascha
Re: frequency scaling on D525MW not working properly
On Mon, Jul 23, 2012 at 09:44:06AM +0800, Sepherosa Ziehau wrote: On Mon, Jul 23, 2012 at 3:27 AM, Sascha Wildner s...@online.de wrote: On Sun, 22 Jul 2012 21:16:54 +0200, Sven Gaerner sgaer...@gmx.net wrote: On Sun, Jul 22, 2012 at 08:31:41PM +0200, Sascha Wildner wrote: On Sun, 22 Jul 2012 13:46:41 +0200, Sven Gaerner sgaer...@gmx.net wrote: [...] Hmm, disabling UEFI is OK, but make sure that you have enabled EST in BIOS (something probably read like enhanced speed step or something like P-state). There is no such option. And the only UEFI option is to enable booting of an UEFI compliant OS. Speed stepping cannot be configured. The BIOS options are very limited. Besides CPU P-State, you could also set allowable CPU C-State to C3 by setting sysctl hw.acpi.cpu.cx_lowest and put tunable hw.i8254.intr_disable=0 in /boot/loader.conf (you need to reboot after changing /boot/loader.conf). However, it should be noted that enabling C3 will disable LAPIC timer and i8254 timer will be used instead, which may cause extra overhead. This seems not to change anything. The temperature remains the same. And setting hw.acpi.cpu.cx_lowest returns with Invalid Argument. Updating the BIOS to a more recent version did also not help. Thanks for your hints. Sven
Re: frequency scaling on D525MW not working properly
On Mon, Jul 23, 2012 at 10:28:14AM +, Adrian Bocaniciu wrote: Intel Atom processors, unlike more expensive Intel processors, do not support frequency scaling. See for example the specifications for Atom D525 at: http://ark.intel.com/products/49490/ where it is stated that Enhanced Intel SpeedStep Technology is not supported. The same is written in all Atom datasheets. The only way to reduce the power consumption of Atom is to ensure that the processor is halted when it has nothing to do, i.e. in the idle loop, which I suppose that DragonFlyBSD does, or to use the ACPI C3 sleep state whenever you can tolerate the latency required for waking up the processor. I also have a couple of D525MW boards, but I have not tested DragonFlyBSD on them, and they are much less warm, but my Mini-ITX cases (Lian Li Antec) have case coolers that ensure an adequate air flow inside the cases even if both the motherboards and the power supplies are fanless. Thanks for the details. I did not look at that point as I expected at least frequency scaling which is supported by the Atom on the Fit-PC2 I also use. I think I will try to get the temperature down by using a fan. But then it is no longer a fanless system that I wanted to have running all the time. And a system in a mini-ITX case with a temperature of 55 degrees is not what I want to have running all the time. Thanks all for the help. I guess I will have to think about a replacement to get a cooler fanless system. Regards, Sven
Re: frequency scaling on D525MW not working properly
On Mon, 23 Jul 2012 21:24:38 +0200, Sven Gaerner sgaer...@gmx.net wrote: On Mon, Jul 23, 2012 at 09:44:06AM +0800, Sepherosa Ziehau wrote: On Mon, Jul 23, 2012 at 3:27 AM, Sascha Wildner s...@online.de wrote: On Sun, 22 Jul 2012 21:16:54 +0200, Sven Gaerner sgaer...@gmx.net wrote: On Sun, Jul 22, 2012 at 08:31:41PM +0200, Sascha Wildner wrote: On Sun, 22 Jul 2012 13:46:41 +0200, Sven Gaerner sgaer...@gmx.net wrote: [...] Hmm, disabling UEFI is OK, but make sure that you have enabled EST in BIOS (something probably read like enhanced speed step or something like P-state). There is no such option. And the only UEFI option is to enable booting of an UEFI compliant OS. Speed stepping cannot be configured. The BIOS options are very limited. It looks like the Atom D525 (along with the rest of D*) does not support it: http://ark.intel.com/products/49490 Only N*, Z* and E* Atoms seem to have it: http://en.wikipedia.org/wiki/List_of_Intel_Atom_microprocessors Sascha
Re: XFCE based LiveDVD/IMG
Thanks, I will definitely give this a try and let you know how it goes. Tim On Mon, Jul 23, 2012 at 3:01 PM, Sascha Wildner s...@online.de wrote: Hi, I've been working on and off on a better, XFCE based DVD/IMG for some time (hehe, more off than on). The result of my attempts so far is here: http://island.quantumachine.**net/~swildner/LiveDVD/x86_64/http://island.quantumachine.net/~swildner/LiveDVD/x86_64/ The USB image is larger than 4GB, unfortunately (I think around 5GB, as it was too full with 4GB). In addition to what we ship on our regular CD/IMG, it has the following packages installed: meta-pkgs/modular-xorg meta-pkgs/xfce4 meta-pkgs/xfce4-extras mail/thunderbird www/midori editors/emacs editors/vim misc/libreoffice multimedia/vlc chat/pidgin chat/irssi misc/tmux graphics/gimp graphics/xsane I have not yet verified how useful xsane is, or if it works at all. It might at least save some time for those who want to install or try out using these packages. Help, ideas, testing and comments are welcome. Sascha
Re: XFCE based LiveDVD/IMG
On Mon, Jul 23, 2012 at 6:01 PM, Sascha Wildner s...@online.de wrote: The USB image is larger than 4GB, unfortunately (I think around 5GB, as it was too full with 4GB). I don't think this is much of a problem. I would bet that the average USB flash drive size has climbed beyond 4G. Looking at newegg.com, I see more 8G sticks than 4G, and the price is under $10 either way. Help, ideas, testing and comments are welcome. Which pkgsrc release is it built with? (and does /usr/Makefile match it?) That's a question I could answer myself once I try it, I suppose.
Re: XFCE based LiveDVD/IMG
Sascha Wildner a écrit : I have not yet verified how useful xsane is, or if it works at all. In my case, xsane is working fine and allows me to use my ScanJet 3300C, I'm really satisfied up to now. My scanner don't work with /dev/uscanner0, so uscanner had to be disabled in the kernel and the generic device was used instead. Compiling sane without libusb might solve this problem, but I didn't try it. My printer also have the same problem with ulpt, I have to use ugen to use it. Thus, at boot time, I get this: ugen0: Samsung Electronics Co., Ltd. SCX-3200 Series, class 0/0, rev 2.00/1.00, addr 2 on uhub4 ugen1: Hewlett-Packard HP ScanJet 3300C, class 0/0, rev 1.00/0.00, addr 2 on uhub0 I changed the permissions of /dev/usb0 and /dev/ugen1 accordingly to allow users to use the scanner. But if the energy saving feature of my printer takes the printer down and the computer reboots (after a power outage for example), the printer is not detected at reboot, the scanner then takes ugen0. The permissions are then wrong and the print spool points to the scanner device. Until I find a better solution, my workaround is to shut both devices and reconnect them in order. With ugen, sane-find-scanner reports this: found USB scanner (vendor=0x03f0 [Hewlett-Packard], product=0x0205 [HP ScanJet 3300C]) at libusb:/dev/usb0:/dev/ugen1 The configuration file hp.conf had to be changed to allow users to use the scanner (otherwise only root could): /dev/ugen1 /dev/usb0 option connect-device scanimage was freezing when the last two lines weren't there. I don't know if the option connect-device is useful since sane-backends is supposed to use libusb, but I didn't try it without it. Hope this helps. SR
Re: frequency scaling on D525MW not working properly
On Tue, Jul 24, 2012 at 3:24 AM, Sven Gaerner sgaer...@gmx.net wrote: On Mon, Jul 23, 2012 at 09:44:06AM +0800, Sepherosa Ziehau wrote: On Mon, Jul 23, 2012 at 3:27 AM, Sascha Wildner s...@online.de wrote: On Sun, 22 Jul 2012 21:16:54 +0200, Sven Gaerner sgaer...@gmx.net wrote: On Sun, Jul 22, 2012 at 08:31:41PM +0200, Sascha Wildner wrote: On Sun, 22 Jul 2012 13:46:41 +0200, Sven Gaerner sgaer...@gmx.net wrote: [...] Hmm, disabling UEFI is OK, but make sure that you have enabled EST in BIOS (something probably read like enhanced speed step or something like P-state). There is no such option. And the only UEFI option is to enable booting of an UEFI compliant OS. Speed stepping cannot be configured. The BIOS options are very limited. Besides CPU P-State, you could also set allowable CPU C-State to C3 by setting sysctl hw.acpi.cpu.cx_lowest and put tunable hw.i8254.intr_disable=0 in /boot/loader.conf (you need to reboot after changing /boot/loader.conf). However, it should be noted that enabling C3 will disable LAPIC timer and i8254 timer will be used instead, which may cause extra overhead. This seems not to change anything. The temperature remains the same. And setting hw.acpi.cpu.cx_lowest returns with Invalid Argument. I mean following steps: 1) Add the following line into into /boot/loader.conf, then reboot: hw.i8254.intr_disable=0 2) sysctl hw.acpi.cpu.cx_lowest=C3 Best Regards, sephe -- Tomorrow Will Never Die
Re: frequency scaling on D525MW not working properly
On Tue, Jul 24, 2012 at 9:57 AM, Sepherosa Ziehau sepher...@gmail.com wrote: On Tue, Jul 24, 2012 at 3:24 AM, Sven Gaerner sgaer...@gmx.net wrote: On Mon, Jul 23, 2012 at 09:44:06AM +0800, Sepherosa Ziehau wrote: On Mon, Jul 23, 2012 at 3:27 AM, Sascha Wildner s...@online.de wrote: On Sun, 22 Jul 2012 21:16:54 +0200, Sven Gaerner sgaer...@gmx.net wrote: On Sun, Jul 22, 2012 at 08:31:41PM +0200, Sascha Wildner wrote: On Sun, 22 Jul 2012 13:46:41 +0200, Sven Gaerner sgaer...@gmx.net wrote: [...] Hmm, disabling UEFI is OK, but make sure that you have enabled EST in BIOS (something probably read like enhanced speed step or something like P-state). There is no such option. And the only UEFI option is to enable booting of an UEFI compliant OS. Speed stepping cannot be configured. The BIOS options are very limited. Besides CPU P-State, you could also set allowable CPU C-State to C3 by setting sysctl hw.acpi.cpu.cx_lowest and put tunable hw.i8254.intr_disable=0 in /boot/loader.conf (you need to reboot after changing /boot/loader.conf). However, it should be noted that enabling C3 will disable LAPIC timer and i8254 timer will be used instead, which may cause extra overhead. This seems not to change anything. The temperature remains the same. And setting hw.acpi.cpu.cx_lowest returns with Invalid Argument. I mean following steps: 1) Add the following line into into /boot/loader.conf, then reboot: hw.i8254.intr_disable=0 2) sysctl hw.acpi.cpu.cx_lowest=C3 I mean do step1) first, then do step 2) after step1)'s reboot. i8254 is intentionally disabled by default, so some mobo w/o it could boot properly. Best Regards, sephe Best Regards, sephe -- Tomorrow Will Never Die -- Tomorrow Will Never Die
