Re: Cosmetics
On 25/03/2012, Robert Gauthier 321.rob...@gmail.com wrote: Under any load although the CPU fan revs up, sysctl -a | grep fan0 hw.sensors.it3.fan0: 51 RPM dmesg | grep it3 it3 at port 0x228-0x22f on isa0 With OpenBSD $ sysctl | grep fan0 hw.sensors.it0.fan0=2311 RPM $ dmesg | grep it0 it0 at isa0 port 0x2e/2: IT8720F rev 8, EC port 0x228 Sensors seem to be identified wrongly in dragonfly for this machine. I tried replacing openbsd's adress range for it0 and commenting out it3. No go. Anyone could help me dig further into this? Thanks, Robert. The address range part is identical -- both OpenBSD and DragonFly above are reading sensors from the 0x228-0x22f space. It seems like the latest it(4) from OpenBSD uses raw 16-bit readings for fans on newer ITE chips, instead of the legacy lm-style 8-bit reading with an extra fan divisor logic from register 0x0b. ITE no longer publishes any datasheets on their web-site since a couple of years ago (what they claim are datasheets on their web-site are simply tiny 16-page documents with pages intentionally left blank), but it seems like their newer chips may have repurposed the 0Bh register away from being Fan Tachnometer Divisor Register, so no wonder it doesn't seem to work. If it's an Asus board, you might try aibs(4), it usually works much-much better than it(4). Else, happy hacking! ;-) C.
Re: Firefox, Namoroka, Iceweasel
On 24 November 2010 08:48, Pierre Abbat p...@phma.optus.nu wrote: I'm accessing a site which doesn't recognize my Firefox and sends code that doesn't work. (It does work with Konqueror on my Linux box when I configure it to pretend to be MSIE, so the problem's not urgent.) I suspect it's because Firefox sends a browser ID string that doesn't say Firefox. It ends with Namoroka 3.6.3 instead. I'm using 2010Q1. If I upgrade (which I can't till after the semester), will it be fixed? This is clearly a bug in a web-site and not the browser, since the web-site is supposed to be testing for specific functionality, instead of any specific browsers. Please complain to site owners. Nonetheless, if you require modification of the user-agent string, IIRC, this could be adjusted in Mozilla web-browsers in about:config with the general.useragent.override variable (or some other variables underneath general.useragent, if you don't require complete user-agent string overwriting). C.
Re: New mirror in Russia
On 22/02/2009, Justin C. Sherrill jus...@shiningsilence.com wrote: http://df.v12.su/mirror/ It's mirroring from chlamydia.fs.ei.tum.de nightly, so it has ISOs, packages, etc. I get good speeds to it from the other side of the planet. It's listed on the Downloads page on the DragonFly website now too. I'll add FTP access when I can get to it. Speaking of mirrors in Russia, there is no internet in the Asian part of Russia, let alone any mirrors, so it's a bit strange that Russian mirrors are still listed in the Asian section of the mirrors page. :) C.
Re: Acer Aspire One (150)
On 12/11/2008, Christopher Rawnsley [EMAIL PROTECTED] wrote: While I don't have a Acer Aspire I do have a netbook of some kind and I would like to raise the general issue that you get with them. They don't have CD drives. From the sounds of things, it doesn't seem like too big a deal for you as you have an external one (although you have dropped in to the kernel debugger...) but I would imagine that many people don't have such a luxury. I think USB flash images are the way to go and I dug up a script from Dario Freni on FreeBSD front for converting ISO images to USB disc images[1]. I think this is a start and I would like to encourage the creation of one for the DragonFly Project. I want to work on this but it's bound to take me a while :) Anyone got any tips? References: [1] http://docs.freebsd.org/cgi/mid.cgi?4420AF56.60106 (Script is garbled a little so I've attached a cleaned up one) IMHO, that's the general problem with FreeBSD / DragonFly -- it's not possible to install them from an existing installation, at least not if you want to use the officially supported installation procedure. What I do when I want to install OpenBSD is: download an appropriate bsd.rd [0] to an existing OpenBSD installation on a USB HDD, boot from the said USB HDD on the new hardware to which brand-new HDD we're about to install an OS, type boot bsd.rd (or whatever the name you've given to your copy of a bsd.rd for this specific installation), and there we go -- no CDs wasted and no netboot configuration or expertise required, and we could easily be using the latest bsd.rd, so no further updates would be required after the installation. The above procedure is much better for the environment and usually saves a lot of time. YMMV. Cheers, Constantine. [0] http://www.openbsd.org/faq/faq4.html#bsd.rd
Re: [ANNOUNCEMENT] The pkgsrc-2008Q2 Branch
On 27/07/2008, Cristi Magherusan [EMAIL PROTECTED] wrote: Hello, On Sat, 2008-07-26 at 08:43 +0100, Alistair Crooks wrote: The pkgsrc-2008Q2 Branch The pkgsrc developers are very proud to announce the new pkgsrc-2008Q2 branch, which has support for more packages than previous branches. As well as updated versions of many packages, the infrastructure of pkgsrc itself has been improved for better platform and compiler support. Congratulations and many thanks to everyone who contributed! For the future releases, do you have any plans to include an officially supported tool that will properly update/rebuild all or some of the installed packages on a system, without removing everything and rebuilding from scratch, while still maintaining the binary consistency of the system? I'm thinking at something like the portupgrade tool from FreeBSD. Or like `pkg_add -u` on OpenBSD? :-) http://www.openbsd.org/faq/faq15.html#PkgUpdate http://www.openbsd.org/papers/ven05-espie/ br, cnst.su.
Re: Tickless system?
On 09/10/2007, Matthew Dillon [EMAIL PROTECTED] wrote: :...further development like full tickless systems, where the time :slice is controlled by the scheduler, variable frequency profiling, :and a complete removal of jiffies in the future. : :AFAIK this kind of thing is orthogonal to the goals of this project, :but it still seems an interesting idea -- one which might eventually :be of interest here. Dunno. : :Any opinions on this tickless idea, pros/cons/relevance? Well, DragonFly already uses its systimer API for nearly all timer events in the system. There is still a base tick but, for example, the scheduler has its own periodic event. The base tick in DragonFly drives process statistics, the 'ticks' counter, and the seconds counter, and that's pretty much it. The real issue here is probably cutting down on timer events when a system is idle - almost certainly to improve the efficiency of virtualized systems. I think it's a separate problem space. It would certainly be possible for our various subsystems to detect an idle condition and stop requesting periodic timeouts in that situations. I'm not sure its worth doing, though. It might be useful for power consumption purposes, too. For example, on my Core 2 Duo Allendale box, default FreeBSD 7.0-CURRENT consumes about 2W more power in the idle loop than DragonFly BSD or OpenBSD due to the increased number of clock interrupts that it processes. http://lists.freebsd.org/pipermail/freebsd-arch/2007-September/006807.html Whereas going from 1000HZ to 100HZ saves me 2W, I'm not going to guess how much savings one would get from going lower than 100HZ -- maybe there won't be any significant savings in that direction. C.
Re: Tickless system?
On 09/10/2007, walt [EMAIL PROTECTED] wrote: Constantine A. Murenin wrote: On 09/10/2007, Matthew Dillon [EMAIL PROTECTED] wrote: ... The real issue here is probably cutting down on timer events when a system is idle - almost certainly to improve the efficiency of virtualized systems... It might be useful for power consumption purposes, too. For example, on my Core 2 Duo Allendale box, default FreeBSD 7.0-CURRENT consumes about 2W more power in the idle loop than DragonFly BSD or OpenBSD due to the increased number of clock interrupts that it processes... Interesting point, thanks. How do you measure power consumption? I use a device called Kill A Watt: http://www.newegg.com/Product/Product.aspx?Item=N82E16882715001 C.
