Re: Plans for 1.8+ (2.0?)
Would file locking and range locking be handled separately? On Feb 19, 2007, at 11:11 PM, Matthew Dillon wrote: :Hey Matt, :1) Does your filesystem plan include the ability to grow and shrink a :partition/volume? ie. /home is running out of space so we could run :"shrinkfs" ... on /usr which has a lot of space and "growfs" ... on /home The filesystem's backing store will be segmented. Segment size can range from 1MB to 4GB (ish). A 'partition' would be able to hold multiple segments from the filesystem's point of view, but the main purpose of the segmentation is to create large, near-independant blocks of data which can be dealt with on a segment-by-segment basis (e.g. for recovery, fsck/check, replication, growing, and shrinking purposes). Having partition affinity would allow a LUN to be moved to a new host, and the vkernel moved along with it. Segmentation also means the filesystem's backing store is not restricted to a single block device but can be glued together with several block devices, or even mixed-and-matched between separate replicated data stores for recovery purposes. Maybe we can pull in some iSCSI initiator code. So, yes, it will be possible to grow or shrink the filesystem on a segment-by-segment basis. -Matt Matthew Dillon <[EMAIL PROTECTED]>
Re: Native jdk build - success
On Tue, Feb 20, 2007 at 03:52:51PM -0800, walt wrote: > Bill Hacker wrote: > > Francois Tigeot wrote: > >> Hi, > >> > >> Today, I finally succeeded in building a native version of wip/jdk14. > >> > >> The big difference with my previous attempts was the DragonFly version: > >> 1.4.5-RELEASE > >> > >> So, we have: > >> > >> 1.4.5 => success > >> 1.6.2 => failure > >> 1.8.0 => failure > > One annoying problem has been that the recent releases of Sun's jdk all > segfault on DragonFly. What version(s) are you using? I used the 1.4.2-09 linux binary; I believe everything below patch level 11 is okay. Beeing a lazy bastard I just issued a cvs update -D "1 year ago" in lang/sun-jre14 and lang/sun-jdk14 -- Francois Tigeot
Re: Native jdk build - success
On Wed, Feb 21, 2007 at 06:47:14AM +0800, Bill Hacker wrote: > Francois Tigeot wrote: > > > >Today, I finally succeeded in building a native version of wip/jdk14. > > > >So, we have: > > > >1.4.5 => success > >1.6.2 => failure > >1.8.0 => failure > > > >The error was also the same in all cases: > > > >Error: failed > >/usr/obj/pkgsrc/wip/jdk14/work/control/build/bsd-i586/lib/i386/client/libjvm.so, > > because Undefined symbol "JNI_CreateJavaVM" > > > >Sadly, I'm not sure I will be able to pinpoint what exactly has changed > >between > >1.4 and 1.6 to cause this. > > 'pinpoint' may be the gcc ver & libs installed by default at each of the > above releases? The compiler in 1.4.5 and 1.6.2 is the same: $ gcc -v Using built-in specs. Configured with: DragonFly/i386 system compiler Thread model: posix gcc version 3.4.5 20050809 (prerelease) [DragonFly] (propolice, visibility) -- Francois Tigeot
Re: bge not probed
Kris Kennaway wrote: I tried to netboot a dragonfly 1.8 kernel but it didn't probe bge, so it was unable to mount the nfs root. [EMAIL PROTECTED]:3:0: class=0x02 card=0x2b801022 chip=0x164814e4 rev=0x03 hdr=0x00 Seems the device is on some bridged pci bus which is not found. found-> vendor=0x1022, dev=0x7460, revid=0x07 [8Cbus=0, slot=6, func=0 [8Cclass=[BRIDGE]06-04-00, hdrtype=0x01, mfdev=0 [8Csubordinatebus=1 [7Csecondarybus=1 only this one appears, the remainder (non-pcib) is repeating over and over again, not sure if that is correct. I guess you also tried with ACPI disabled? Definitely some PCI routing/probing issue. cheers simon -- Serve - BSD +++ RENT this banner advert +++ASCII Ribbon /"\ Work - Mac +++ space for low €€€ NOW!1 +++ Campaign \ / Party Enjoy Relax | http://dragonflybsd.org Against HTML \ Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \ signature.asc Description: OpenPGP digital signature
Re: bge not probed
btw, your mail address bounces. is that intended? cheers simon -- Serve - BSD +++ RENT this banner advert +++ASCII Ribbon /"\ Work - Mac +++ space for low €€€ NOW!1 +++ Campaign \ / Party Enjoy Relax | http://dragonflybsd.org Against HTML \ Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \ signature.asc Description: OpenPGP digital signature
Re: Plans for 1.8+ (2.0?)
:Hey Matt, :Thanks for your answers, but i have one more question for you. Will the :new file system be capable of ACLs? : :Cheers, :Petr It will be capable of storing meta-data records for certain, so yes. However, the OS needs an ACL implementation to use the meta-data store the filesystem makes available. -Matt Matthew Dillon <[EMAIL PROTECTED]>
Re: RealPlayerGold?
On Wed, 21 Feb 2007, Huub wrote: > Hi, > > I run DFBSD 1.9. In pkgsrc/multimedia I find RealPlayerGold, but "make install > clean" stops in error. How do I build it? First download the rpm from > real.com? and then? Hm. I just installed with no problems. What error do you see?
Re: RealPlayerGold?
Hm. I just installed with no problems. What error do you see?
This:
# make install clean
Unknown modifier '1'
Unknown modifier 'u'
"../../emulators/suse_linux/../../mk/bsd.prefs.mk", line 568: Could not
find /mk/wrapper/wrapper-defs.mk
"../../emulators/suse_linux/../../mk/bsd.prefs.mk", line 571: Could not
find /mk/flavor/bsd.flavor-vars.mk
"../../emulators/suse_linux/../../mk/bsd.prefs.mk", line 574: Could not
find /mk/bsd.makevars.mk
"../../mk/bsd.pkg.mk", line 30: Could not find /bsd.prefs.mk
"../../mk/bsd.pkg.mk", line 32: Could not find /flavor/bsd.flavor-vars.mk
"../../mk/bsd.pkg.mk", line 33: Could not find /check/bsd.check-vars.mk
"../../mk/bsd.pkg.mk", line 34: Could not find /depends/bsd.depends-vars.mk
"../../mk/bsd.pkg.mk", line 35: Could not find /fetch/bsd.fetch-vars.mk
"../../mk/bsd.pkg.mk", line 36: Could not find
/checksum/bsd.checksum-vars.mk
"../../mk/bsd.pkg.mk", line 37: Could not find /extract/bsd.extract-vars.mk
"../../mk/bsd.pkg.mk", line 38: Could not find /patch/bsd.patch-vars.mk
"../../mk/bsd.pkg.mk", line 39: Could not find
/configure/bsd.configure-vars.mk
"../../mk/bsd.pkg.mk", line 40: Could not find /build/bsd.build-vars.mk
"../../mk/bsd.pkg.mk", line 41: Could not find /install/bsd.install-vars.mk
"../../mk/bsd.pkg.mk", line 43: Could not find /bsd.pkg.error.mk
"../../mk/bsd.pkg.mk", line 45: Could not find /bsd.hacks.mk
"../../mk/bsd.pkg.mk", line 107: Could not find /bsd.pkg.use.mk
Unknown modifier '1'
Unknown modifier '1'
"../../mk/bsd.pkg.mk", line 131: Malformed conditional
(${PKGTOOLS_VERSION} < ${PKGTOOLS_REQD})
"../../mk/bsd.pkg.mk", line 138: if-less endif
"../../mk/bsd.pkg.mk", line 359: Could not find /alternatives.mk
"../../mk/bsd.pkg.mk", line 362: Could not find
/pkginstall/bsd.pkginstall.mk
Unknown modifier '1'
"../../mk/bsd.pkg.mk", line 443: Could not find /internal/locking.mk
"../../mk/bsd.pkg.mk", line 446: Could not find /tools/bsd.tools.mk
"../../mk/bsd.pkg.mk", line 449: Could not find /bsd.pkg.barrier.mk
"../../mk/bsd.pkg.mk", line 452: Could not find /unprivileged.mk
"../../mk/bsd.pkg.mk", line 462: Could not find /compiler.mk
"../../mk/bsd.pkg.mk", line 464: Could not find /wrapper/bsd.wrapper.mk
"../../mk/bsd.pkg.mk", line 615: Could not find /flavor/bsd.flavor.mk
"../../mk/bsd.pkg.mk", line 617: Could not find /depends/bsd.depends.mk
"../../mk/bsd.pkg.mk", line 618: Could not find /check/bsd.check.mk
"../../mk/bsd.pkg.mk", line 619: Could not find /fetch/bsd.fetch.mk
"../../mk/bsd.pkg.mk", line 620: Could not find /checksum/bsd.checksum.mk
"../../mk/bsd.pkg.mk", line 621: Could not find /extract/bsd.extract.mk
"../../mk/bsd.pkg.mk", line 622: Could not find /patch/bsd.patch.mk
"../../mk/bsd.pkg.mk", line 623: Could not find /configure/bsd.configure.mk
"../../mk/bsd.pkg.mk", line 624: Could not find /build/bsd.build.mk
"../../mk/bsd.pkg.mk", line 625: Could not find /install/bsd.install.mk
"../../mk/bsd.pkg.mk", line 626: Could not find /package/bsd.package.mk
"../../mk/bsd.pkg.mk", line 628: Could not find /bsd.pkg.clean.mk
"../../mk/bsd.pkg.mk", line 629: Could not find /bsd.pkg.update.mk
Unknown modifier '1'
"../../mk/bsd.pkg.mk", line 686: Could not find /install/bin-install.mk
"../../mk/bsd.pkg.mk", line 760: Could not find /plist/bsd.plist.mk
"../../mk/bsd.pkg.mk", line 762: Could not find /bsd.utils.mk
"../../mk/bsd.pkg.mk", line 764: Could not find /subst.mk
"../../mk/bsd.pkg.mk", line 775: Could not find /bsd.pkg.readme.mk
"../../mk/bsd.pkg.mk", line 821: Could not find /misc/show.mk
"../../mk/bsd.pkg.mk", line 828: Could not find /misc/can-be-built-here.mk
make: fatal errors encountered -- cannot continue
su-3.2#
Thanks for helping out.
Re: bge not probed
On 2007-02-21, Simon 'corecode' Schubert <[EMAIL PROTECTED]> wrote: > This is an OpenPGP/MIME signed message (RFC 2440 and 3156) > --enig03488FB84BA7CEDA5560E208 > Content-Type: text/plain; charset=UTF-8; format=flowed > Content-Transfer-Encoding: quoted-printable > > Kris Kennaway wrote: >> I tried to netboot a dragonfly 1.8 kernel but it didn't probe bge, so i= > t >> was unable to mount the nfs root. > >> [EMAIL PROTECTED]:3:0: class=3D0x02 card=3D0x2b801022 chip=3D0x164814e4 >> re= > v=3D0x03 hdr=3D0x00 > > Seems the device is on some bridged pci bus which is not found. > >> found-> vendor=3D0x1022, dev=3D0x7460, revid=3D0x07 >> =1B[8Cbus=3D0, slot=3D6, func=3D0 >> =1B[8Cclass=3D[BRIDGE]06-04-00, hdrtype=3D0x01, mfdev=3D0 >> =1B[8Csubordinatebus=3D1 =1B[7Csecondarybus=3D1 > > only this one appears, the remainder (non-pcib) is repeating over and ove= > r again, not sure if that is correct. > > I guess you also tried with ACPI disabled? Yeah, disabling ACPI didn't help. > Definitely some PCI routing/probing issue. Oh, OK. Well, let me know (corrected address above) if you have ideas on getting it to work. Kris
Re: RealPlayerGold?
On Wed, Feb 21, 2007 at 08:03:21PM +0100, Huub wrote: > > > >Hm. I just installed with no problems. What error do you see? > > > > This: > > # make install clean For pkgsrc you must use bmake instead of make. -- La prueba más fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros.
Re: RealPlayerGold?
For pkgsrc you must use bmake instead of make. Uhhmmmthank you..but after successfully installing: $ /usr/pkg/bin/realplayergold /usr/pkg/lib/RealPlayer/realplay.bin: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory I guess I have to install something else as well, but what? I suppose rpm from rpmfind.net won't work :)..
Re: RealPlayerGold?
Huub wrote: >> >> For pkgsrc you must use bmake instead of make. >> > > Uhhmmmthank you..but after successfully installing: > > $ /usr/pkg/bin/realplayergold > /usr/pkg/lib/RealPlayer/realplay.bin: error while loading shared > libraries: libstdc++.so.5: cannot open shared object file: No such file > or directory > > I guess I have to install something else as well, but what? I suppose > rpm from rpmfind.net won't work :).. pkgsrc/meta-pkgs/suse10 contains the entire suse distribution except the kernel, so it's huge. Make sure you have plenty of disk space. You will also need to show linux apps where to find the fonts, but I can't remember how to do it. I think you put a symlink somewhere.
Re: RealPlayerGold?
pkgsrc/meta-pkgs/suse10 contains the entire suse distribution except the kernel, so it's huge. Make sure you have plenty of disk space. You will also need to show linux apps where to find the fonts, but I can't remember how to do it. I think you put a symlink somewhere. Thank you.
Re: hardware compatibility - Nvidia SATA controller
Hi Sascha, Thanks for building this. I installed it successfully on the Dell with SATA disks. -Jon * Sascha Wildner <[EMAIL PROTECTED]> [02-03-2007 19:13]: > > Jon Nathan wrote: > >If this isn't in the kernel on the install CD, it's probably not much > >use to me. > > Jon, > > I've put up a 1.8-RELEASE ISO with NATA compiled in at: > > http://leaf.dragonflybsd.org/~swildner/dfly.iso.bz2 > > It's larger than the normal ISO due to inclusion of debug symbols and > GCC 4.1 (forgot to turn both off). Haven't tried it, I hope the > installer works. > > Regards, > Sascha > > -- > http://yoyodyne.ath.cx
DragonFly testing
Hi. I'd like to introduce myself. I am Ben Jolitz, technologist and student. Recently, I tried to run DragonFly on an old Dell Latitude CPi. I detailed my tries with DF. Perhaps after reading this log you might have some suggestions. The log is at: http://ben.telemuse.net/27 One of my biggest questions is how would I get audio running? Snd_ess loaded, and spat out one line of DMA information, but never initialized the device... Thanks, Ben Jolitz
Re: DragonFly testing
Ben Jolitz wrote: Hi. I'd like to introduce myself. I am Ben Jolitz, technologist and student. Recently, I tried to run DragonFly on an old Dell Latitude CPi. I detailed my tries with DF. Perhaps after reading this log you might have some suggestions. The log is at: http://ben.telemuse.net/27 One of my biggest questions is how would I get audio running? Snd_ess loaded, and spat out one line of DMA information, but never initialized the device... Thanks, Ben Jolitz For your sound you need to load sound.ko + snd_ess.ko Best if you add snd_ess_load="YES" to /boot/loader.conf and in /dev you need to run sh MAKEDEV snd0 I think thats what has to be done. Petr
Re: DragonFly testing
On Thu, 22 Feb 2007 11:46:07 +1100 Petr Janda <[EMAIL PROTECTED]> wrote: > For your sound you need to load sound.ko + snd_ess.ko > > Best if you add snd_ess_load="YES" to /boot/loader.conf > > and in /dev you need to run sh MAKEDEV snd0 > Load snd_ess.ko only. It loads sound.ko as dependency. MAKEDEV was not necessary for me, however I had snd_ich. Regarding other parts of the log: as a freebsd-user, you should have had some basic idea on getting the pkgsrc tree and unpacking it (although I don't know what permits DF developers to include it on the CD, maybe licence? Or a /usr/sbin/getpkgsrc script would probably do as well.) It is much like the ports tree, expect the (very stupid) interactive setting of build options (this was one of the reasons I dropped freebsd). I have always considered the pkgsrc way of life quite straightforward, especially because I have FreeBSD and OpenBSD experience. Could you describe your pkgsrc problems more? (I admit that mplayer in pkgsrc tree is quite outdated.) -- Gergo Szakal <[EMAIL PROTECTED]> University Of Szeged, HU Faculty Of General Medicine /* Please do not CC me with replies, thank you. */
Re: DragonFly testing
Petr Janda wrote: For your sound you need to load sound.ko + snd_ess.ko Best if you add snd_ess_load="YES" to /boot/loader.conf and in /dev you need to run sh MAKEDEV snd0 I think thats what has to be done. Petr I was under the impression that sound.ko was loaded by association, as kldstat said. I had not done a ./MAKEDEV snd0, but I suspect it will not work, since Dells are notorious for having standard equipment in non-standard locations. Will research some more on forcing discovery of Crystal WDM. -- Ben
Re: DragonFly testing
On Thu, 22 Feb 2007, Gergo Szakal wrote: > Regarding other parts of the log: as a freebsd-user, you should have had > some basic idea on getting the pkgsrc tree and unpacking it (although I > don't know what permits DF developers to include it on the CD, maybe > licence? The pkgsrc infrastructure is BSD licensed. The individual patches for various software are generally just the same license as the software they patch. > Or a /usr/sbin/getpkgsrc script would probably do as well.) It > is much like the ports tree, expect the (very stupid) interactive > setting of build options (this was one of the reasons I dropped > freebsd). pkgsrc does not prompt for build options like FreeBSD Ports. (But pkgsrc does have build options that can be customized. It is a lot more consistent that FreeBSD ports which are hit and miss on how to configure stuff.) > I have always considered the pkgsrc way of life quite > straightforward, especially because I have FreeBSD and OpenBSD > experience. Could you describe your pkgsrc problems more? > (I admit that mplayer in pkgsrc tree is quite outdated.) For mplayer, you may want to send-pr it or turn in a bug report so it gets updated in pkgsrc. Or a polite note to the MAINTAINER. Jeremy C. Reed
distributed filesystem name
[ In response to Matt's note in kernel@ about needing a name for his filesystem ] My creative (beer) juices are flowing, so indulge or ignore as you see fit. Dragonfly larvae are called "nymphs", which can be pronounced the same way but written as "NymphFS" or shortened to "NymFS" if necessary. Seems somehow fitting that eggs are produced in quantities of hundreds or thousands. Plus, lots of fun nymph biology terms can be used to describe different processes as they relate to the filesystem. As nymphs grow, they molt (shed their skin). Molting can maybe describe the process of "Physical space recovery" or "Performance reorganization". Plenty of other verbs like hatch, fossilize, and metamorphose from which to choose. Nymphs apparently often feed on mosquito larvae, but unfortunately not on penguins. *shrug* Geoff
Re: distributed filesystem name
Oh... and the segment header, data table, and record table can be called the head, thorax, and abdomen. Geoff
Re: DragonFly testing
Regarding other parts of the log: as a freebsd-user, you should have had some basic idea on getting the pkgsrc tree and unpacking it (although I don't know what permits DF developers to include it on the CD, maybe licence? Or a /usr/sbin/getpkgsrc script would probably do as well.) I found the how to a little non specific. I do think that a getpkgsrc script would help set things up. There were no man pages (maybe install fubar'ed?) on pkgsrc, so unlike man ports, I could not get a man pkgsrc. It is much like the ports tree, expect the (very stupid) interactive setting of build options (this was one of the reasons I dropped freebsd). I have always considered the pkgsrc way of life quite straightforward, especially because I have FreeBSD and OpenBSD experience. Could you describe your pkgsrc problems more? (I admit that mplayer in pkgsrc tree is quite outdated.) I guess the problems lay in miscommunication, lack of documentation, and being 'new' to pkgsrc. I've only messed with ports and raw sources for most of my tenure with BSD.
Re: distributed filesystem name
DrachFS. Drache=Dragon in deutsch. Dragon -> Dragonfly, eh? Dragonfly larvae are called "nymphs", which can be pronounced the same way but written as "NymphFS" or shortened to "NymFS" if necessary. Seems somehow fitting that eggs are produced in quantities of hundreds or thousands. Plus, lots of fun nymph biology terms can be used to describe different processes as they relate to the filesystem. As nymphs grow, they molt (shed their skin). Molting can maybe describe the process of "Physical space recovery" or "Performance reorganization". Plenty of other verbs like hatch, fossilize, and metamorphose from which to choose. Hmm. Interesting. Nymphs apparently often feed on mosquito larvae, but unfortunately not on penguins. *shrug* Geoff Nice thing is dragons eat anything. On the side, why can't Fred eat a penguin? We could always put him through an enlarge ray. Ben
Re: KDE and OpenSSL = Broken
> > 3. who's bad? > > > > a. pkgsrc > > b. kdelibs > > c. libltdl > > d. rtld > > f. kernel > > > > a,b,c seems to be ok? > > i'm pretty sure it is in b or a. the warning messages are kind of > expected, because kde tries both old and new openssl symbols. I'm still suspecting lower layer. Can you tell me the following is sane or not? It's ok on NetBSD. program:
Re: distributed filesystem name
On 2/22/07, Ben Jolitz <[EMAIL PROTECTED]> wrote: On the side, why can't Fred eat a penguin? We could always put him through an enlarge ray. http://www.intuitor.com/moviephysics/mpmain.html#scaling I like the name 'NymFS' except for the other words that stem from the 'nymph' root. Probably best to avoid dirty jokes. "Can I use NymFS with an interface in promiscuous mode? Bwahaha" Why do file systems always end in 'FS'? It's one of the very few classes of software that almost universally has the same suffix. The other would have to be 'sh' for any kind of shell or shell remoter. Even ext2/ext3 are often named "extNfs", especially in BSD implementations. I guess you could give a nod to decades of BSD culture by including UFS in the name somehow, like NUFS (say "NewFS") for "Networked Unix File System". Not quite NFS or UFS, but still feels Unixy. --- Dmitri Nikulin Centre for Synchrotron Science Monash University Victoria 3800, Australia
Re: KDE and OpenSSL = Broken
On Wednesday 14 February 2007, Simon 'corecode' Schubert wrote: > > 3. who's bad? > > > > a. pkgsrc > > b. kdelibs > > c. libltdl > > d. rtld > > f. kernel > > > > a,b,c seems to be ok? > > i'm pretty sure it is in b or a. the warning messages are kind of > expected, because kde tries both old and new openssl symbols. I still suspect lower layer. Why does the following last command result in error? It's just ok on NetBSD. test program: http://www.hadaly.org/fuyuki/dltest.c dialogue: $ cc ./dltest.c $ ./a.out $ cc ./dltest.c -lssl $ ./a.out $ a.out: Undefined symbol "SSL_connect"
Re: KDE and OpenSSL = Broken
Oops. Wanted to reply to the list and ended up mailing the OP instead. Sorry, Kimura. === Hmmm. I downloaded dltest.c from the link you'd mentioned and tried this on my box: -- snip -- [EMAIL PROTECTED]: dltest $ gcc -L/usr/pkg/lib -lssl -o dltest dltest.c [EMAIL PROTECTED]: dltest $ ./dltest -- snip -- Seems to me there is nothing wrong with the lower layers. K.
Boot error?
If I need to post more information for this I will, but I think the first dmesg says it all. Should I be worried about "can't fetch resources"? Copyright (c) 2003, 2004, 2005, 2006, 2007 The DragonFly Project. Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. DragonFly 1.8.0-RELEASE #0: Wed Feb 21 20:36:53 PST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/DFCD TSC clock: 2131141072 Hz, i8254 clock: 1193147 Hz CPU: Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz (2131.21-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6 Features=0xbfebfbff Features2=0xe3bd Hyperthreading: 2 logical CPUs real memory = 2137686016 (2087584K bytes) avail memory = 2065498112 (2017088K bytes) Preloaded elf kernel "/kernel" at 0xc0773000. Preloaded elf module "/modules/acpi.ko" at 0xc0773378. Pentium Pro MTRR support enabled md0: Malloc disk ACPI: RSDP @ 0x0xfe020/0x0014 (v 0 INTEL ) ACPI: RSDT @ 0x0x7f6fd038/0x0050 (v 1 INTEL D946GZIS 0x002F 0x0113) ACPI: FACP @ 0x0x7f6fc000/0x0074 (v 1 INTEL D946GZIS 0x002F MSFT 0x0113) ACPI: DSDT @ 0x0x7f6f7000/0x44D7 (v 1 INTEL D946GZIS 0x002F MSFT 0x0113) ACPI: FACS @ 0x0x7f6a8000/0x0040 ACPI: APIC @ 0x0x7f6f6000/0x0078 (v 1 INTEL D946GZIS 0x002F MSFT 0x0113) ACPI: WDDT @ 0x0x7f6f5000/0x0040 (v 1 INTEL D946GZIS 0x002F MSFT 0x0113) ACPI: MCFG @ 0x0x7f6f4000/0x003C (v 1 INTEL D946GZIS 0x002F MSFT 0x0113) ACPI: ASF! @ 0x0x7f6f3000/0x00A6 (v 32 INTEL D946GZIS 0x002F MSFT 0x0113) ACPI: HPET @ 0x0x7f6f2000/0x0038 (v 1 INTEL D946GZIS 0x002F MSFT 0x0113) ACPI: SSDT @ 0x0x7f6f1000/0x01BC (v 1 INTEL CpuPm 0x002F MSFT 0x0113) ACPI: SSDT @ 0x0x7f6f/0x0175 (v 1 INTEL Cpu0Ist 0x002F MSFT 0x0113) ACPI: SSDT @ 0x0x7f6ef000/0x0175 (v 1 INTEL Cpu1Ist 0x002F MSFT 0x0113) ACPI: SSDT @ 0x0x7f6ee000/0x0175 (v 1 INTEL Cpu2Ist 0x002F MSFT 0x0113) ACPI: SSDT @ 0x0x7f6ed000/0x0175 (v 1 INTEL Cpu3Ist 0x002F MSFT 0x0113) npx0: on motherboard npx0: INT 16 interface Using XMM optimized bcopy/copyin/copyout acpi0: on motherboard acpi0: Power Button (fixed) Warning: ACPI is disabling APM's device. You can't run both can't fetch resources for \\_PR_.CPU0 - AE_TYPE can't fetch resources for \\_PR_.CPU1 - AE_TYPE can't fetch resources for \\_PR_.CPU2 - AE_TYPE can't fetch resources for \\_PR_.CPU3 - AE_TYPE acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 legacypci0 on motherboard -- Dave Hayes - Consultant - Altadena CA, USA - [EMAIL PROTECTED] >>> The opinions expressed above are entirely my own <<< Common sense and a sense of humor are the same thing, moving at different speeds. A sense of humor is just common sense, dancing.
Re: Boot error?
On Wed, Feb 21, 2007 at 09:42:25PM -0800, Dave Hayes wrote: > If I need to post more information for this I will, but I think the > first dmesg says it all. Should I be worried about "can't fetch resources"? No, you don't need to worry about the "can't fetch resources" message. I'll deal with it shortly. Cheers.
Re: DragonFly testing
On Wed, 21 Feb 2007 19:47:04 -0800 Ben Jolitz <[EMAIL PROTECTED]> wrote: > I found the how to a little non specific. I do think that a getpkgsrc > script would help set things up. There were no man pages (maybe install > fubar'ed?) on pkgsrc, so unlike man ports, I could not get a man pkgsrc. Try man packages -- C:>WIN | Directable Mirror Arrays The computer obeys and wins.| A better way to focus the sun You lose and Bill collects. |licences available see |http://www.sohara.org/
Re: DragonFly testing
Ben Jolitz wrote: I found the how to a little non specific. I do think that a getpkgsrc script would help set things up. There were no man pages (maybe install fubar'ed?) on pkgsrc, so unlike man ports, I could not get a man pkgsrc. Try 'man packages'. Sascha -- http://yoyodyne.ath.cx
