make, bmake and gmake
Hi: Is there a difference between 'make' and 'bmake' on DragonFly BSD 2.4.1 ? i noticed that /usr/pkgsrc/ builds require 'bmake' eg. to compile /usr/pkgsrc/devel/gmake while 'make' crashes out with many errors. Additionally, /usr/src/test/amd64/ system tests require 'gmake'. A quick check of the man pages shows make : make(1) DragonFly 2.4 March 30, 2005 bmake: make(1) DragonFly 2.4 September 7, 2009 Can the more experienced folks, share their perspective on which make is recommended to be used ? thanks Saifi.
Re: Is chlamydia.fs.ei.tum.de down? can't git pull src
On Wed, Oct 21, 2009 at 10:39 AM, Dmitri Nikulin dniku...@gmail.com wrote: On Wed, Oct 21, 2009 at 3:56 PM, Siju George sgeorge...@gmail.com wrote: My internet connection is fine but I get this error while git pull in /usr/src dfly-bkpsrv# git pull chlamydia.fs.ei.tum.de[0: 129.187.54.14]: errno=Operation timed out chlamydia.fs.ei.tum.de[0: 2001:4ca0:22ff:10::14]: errno=No route to host fatal: unable to connect a socket (No route to host) Maybe fs.ei.tum.de finally received Doxycycline :) It is working now :-) thanks --Siju
Re: make, bmake and gmake
On Wed, 21 Oct 2009, Stathis Kamperis wrote: 2009/10/21 Saifi Khan saifi.k...@datasynergy.org: Hi: Is there a difference between 'make' and 'bmake' on DragonFly BSD 2.4.1 ? make is our make utility which belongs to our base. It's the very same make utility that is used to build world and kernel or to checkout the git src repository when you type 'make src-checkout' inside /usr. make(1) can only parse our own Makefiles. One more query i have is that, the 'make' referred to in the parallism analysis posted by Simon Shubert is the native DragonFly BSD make, is that correct ? i would like to run the tests on my AMD64 dual core box and hopefully can contribute some data for Simon Shubert's analysis. thanks Saifi.
Re: Realtek NIC issue
On Sun, Oct 18, 2009 at 9:12 AM, Saifi Khan saifi.k...@datasynergy.org wrote:
i've a laptop with identical hardware, running FreeBSD
8-CURRENT-200906 (ie. this one, used to write this mail)
and the following lines are seen in the driver code
src/sys/pci/if_rl.c
...
if (sc-rl_type == 0) {
device_printf(dev, unknown device ID: %x assuming 8139\n,
rl_did);
sc-rl_type = RL_8139;
/*
* Read RL_IDR register to get ethernet address as accessing
* EEPROM may not extract correct address.
*/
for (i = 0; i ETHER_ADDR_LEN; i++)
eaddr[i] = CSR_READ_1(sc, RL_IDR0 + i);
}
...
What do you think ?
Thank you for the submission, please cherry-pick:
d9893ddff7cb5a3cadf0051f7b80831951499854
to 2.4 branch and test.
Best Regards,
sephe
--
Live Free or Die
Re: make, bmake and gmake
Saifi Khan wrote: Is there a difference between 'make' and 'bmake' on DragonFly BSD 2.4.1 ? make is our make utility which belongs to our base. It's the very same make utility that is used to build world and kernel or to checkout the git src repository when you type 'make src-checkout' inside /usr. make(1) can only parse our own Makefiles. One more query i have is that, the 'make' referred to in the parallism analysis posted by Simon Shubert is the native DragonFly BSD make, is that correct ? Yes. Standard buildworld/buildkernel procedure. i would like to run the tests on my AMD64 dual core box and hopefully can contribute some data for Simon Shubert's analysis. if I find the time I'll commit a small script which will do all the processing. cheers simon -- 3 the future +++ RENT this banner advert +++ ASCII Ribbon /\ rock the past +++ space for low CHF NOW!1 +++ Campaign \ / Party Enjoy Relax | http://dragonflybsd.org Against HTML \ Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \
[Fwd: pkgbox64 pkgsrc DragonFly 2.5.1/x86_64 2009-10-16 21:12]
Binary package build for DragonFly 2.5.x on amd64 has completed, with a greater-than-I-expected number of packages building. It's at: http://avalon.dragonflybsd.org/packages/amd64/DragonFly-2.5.1/stable/ These should work for all amd64 versions, via pkgin or pkg_radd or manual download. The report didn't upload because of a permissions problem, which I've fixed and the next run (already started) should have an up-to-date report to accompany it. Original Message Subject: pkgbox64 pkgsrc DragonFly 2.5.1/x86_64 2009-10-16 21:12 From:Charlie Root r...@pkgbox64.dragonflybsd.org Date:Wed, October 21, 2009 7:50 am To: jus...@shiningsilence.com -- pkgsrc bulk build report DragonFly 2.5.1/x86_64 Compiler: gcc Build start: 2009-10-16 21:12 Build end: 2009-10-21 11:37 Full report: http://avalon.dragonflybsd.org/reports//20091016.2112/meta/report.html Machine readable version: http://avalon.dragonflybsd.org/reports//20091016.2112/meta/report.bz2 Total number of packages: 8969 Successfully built: 7475 Failed to build: 359 Depending on failed package: 574 Explicitly broken or masked: 497 Depending on masked package:64 Packages breaking the most other packages Package Breaks Maintainer - lang/ruby18-base 269 t...@netbsd.org print/ghostscript115 pkgsrc-us...@netbsd.org lang/ocaml35 a...@netbsd.org lang/mono 29 kef...@netbsd.org graphics/evas 15 ya...@yazzy.org textproc/xerces-c 12 pkgsrc-us...@netbsd.org x11/kdebase-workspace411 ma...@netbsd.org audio/mpg123 8 pkgsrc-us...@netbsd.org www/w3m7 uebay...@netbsd.org math/gap 7 c...@netbsd.org Build failures Package Breaks Maintainer - archivers/star uebay...@netbsd.org audio/akode-plugins-mpc ha...@netbsd.org audio/bmp-macpkgsrc-us...@netbsd.org audio/buzztard 1 pkgsrc-us...@netbsd.org audio/csound4pkgsrc-us...@netbsd.org audio/libmusepack 1 pkgsrc-us...@netbsd.org audio/maplay pkgsrc-us...@netbsd.org audio/mpg123 8 pkgsrc-us...@netbsd.org audio/py-id3lib pkgsrc-us...@netbsd.org py26-id3lib-0.5.1pkgsrc-us...@netbsd.org py25-id3lib-0.5.1pkgsrc-us...@netbsd.org audio/tremor-tools ch...@netbsd.org benchmarks/iozonepkgsrc-us...@netbsd.org benchmarks/randread gr...@netbsd.org biology/py-mol pkgsrc-us...@netbsd.org py26-mol-0.98nb4 pkgsrc-us...@netbsd.org biology/rasmol pkgsrc-us...@netbsd.org cad/atlc dmcmah...@netbsd.org chat/finch pkgsrc-us...@netbsd.org chat/galepkgsrc-us...@netbsd.org chat/silc-client 1 s...@netbsd.org chat/silc-server s...@netbsd.org chat/tircpkgsrc-us...@netbsd.org chat/zircon pkgsrc-us...@netbsd.org comms/asterisk16 jnem...@netbsd.org comms/conserver pkgsrc-us...@netbsd.org comms/mgetty+sendfax pkgsrc-us...@netbsd.org comms/modemd tsa...@netbsd.org comms/plptools pkgsrc-us...@netbsd.org cross/h8300-hms-gcc pkgsrc-us...@netbsd.org cross/i386-cygwin32 pkgsrc-us...@netbsd.org cross/i386-linux pkgsrc-us...@netbsd.org cross/i386-mingw32 pkgsrc-us...@netbsd.org cross/i386-msdosdjgpppkgsrc-us...@netbsd.org cross/mipsEEel-netbsdpkgsrc-us...@netbsd.org databases/gnats re...@netbsd.org databases/openldap-smbk5pwd g...@netbsd.org databases/php-mssql1 jdole...@netbsd.org php4-mssql-4.4.9 1 jdole...@netbsd.org devel/binutils pkgsrc-us...@netbsd.org
Re: Comparison of PgSQL Performance on HAMMER and UFS
Zitat von Matthew Dillon dil...@apollo.backplane.com: I'd like to see how those results compare with the various MPSAFE sysctls turned on, and also with fsync disabled (so we can get an idea how badly fsync effects write transactions, since we know fsync is very expensive on HAMMER): vfs.getattr_mpsafe=1 vfs.read_mpsafe=1 And vfs.hammer.fsync_mode=2 And also with the recent buffer cache work on master. The meta-data for a 5GB dataset should be cachable but prior to the work buffer cache data was being thrown out of the backing VM page caches too quickly. Another thing we know about HAMMER is that the initial B-Tree layout is pretty horrible. It takes a reblocking pass to fix it up. It shouldn't effect a dataset that small with the cache priorities fixed in master, though. -Matt I redid the tests as suggested and with a slighlty different test setup. Results attached. Next step: Redo the tests on -DEVELOPMENT. Regards, Jan This message was sent using IMP, the Internet Messaging Program. HAMMER_pgsql.pdf Description: Adobe PDF document
Re: [Fwd: pkgbox64 pkgsrc DragonFly 2.5.1/x86_64 2009-10-16 21:12]
On Wed, 21 Oct 2009, Justin C. Sherrill wrote: Binary package build for DragonFly 2.5.x on amd64 has completed, with a greater-than-I-expected number of packages building. Total number of packages: 8969 Successfully built: 7475 Failed to build: 359 Depending on failed package: 574 Explicitly broken or masked: 497 Depending on masked package:64 Justin, thats awesome piece of work. Do you think it is a good idea to weigh build-fail/broken/masked packages against a usage list like https://www.osscensus.org/packages-rank-public.php?offset=0limit=778page=0 Using that approach one can showcase certain apps that work/build exceptionally well on the DragonFlyBSD platform. Perhaps somebody may have already reflected on this and that is something not obvious to a newbie like me. thanks Saifi.
Re: [Fwd: pkgbox64 pkgsrc DragonFly 2.5.1/x86_64 2009-10-16 21:12]
Justin C. Sherrill wrote: These should work for all amd64 versions, via pkgin or pkg_radd or manual download. The report didn't upload because of a permissions problem, which I've fixed and the next run (already started) should have an up-to-date report to accompany it. Do you think you can push the report still or is it too late? Are you performing incremental builds? cheers simon
how to apply patches on a system that doesnot have functional network device ?
Hi: Here is a situation that i'm facing on a Compaq C301TU laptop. The NIC card (Realtek) does not work due to driver issue. The WLAN card (Broadcom) does not work due to driver issue. Currently, i review the possible patch visually on an identical laptop (running FreeBSD-8) and then type out the code on the other laptop in sys/dev/netif/rl/if_rl.c file. Is there a better way to apply patches on a system that doesnot have functional network devices ? i'm leaning towards USB-Ethernet and was wondering if there is a USB-Ethernet device that is known to work fine with DragonFly BSD 2.4.1 ? Please accept my apologies for this newbie query and look forward to suggestions from the more experienced folks on this matter. thanks Saifi.
Re: how to apply patches on a system that doesnot have functional network device ?
Saifi Khan wrote: Hi: Here is a situation that i'm facing on a Compaq C301TU laptop. The NIC card (Realtek) does not work due to driver issue. The WLAN card (Broadcom) does not work due to driver issue. Currently, i review the possible patch visually on an identical laptop (running FreeBSD-8) and then type out the code on the other laptop in sys/dev/netif/rl/if_rl.c file. Is there a better way to apply patches on a system that doesnot have functional network devices ? You could transfer the sources via a USB pen drive, that's what I'd try. cheers simon
Re: [Fwd: pkgbox64 pkgsrc DragonFly 2.5.1/x86_64 2009-10-16 21:12]
Justin C. Sherrill wrote: On Wed, October 21, 2009 12:36 pm, Simon 'corecode' Schubert wrote: Justin C. Sherrill wrote: These should work for all amd64 versions, via pkgin or pkg_radd or manual download. The report didn't upload because of a permissions problem, which I've fixed and the next run (already started) should have an up-to-date report to accompany it. Do you think you can push the report still or is it too late? Are you performing incremental builds? Too late - it already has 3,500 packages since my post this morning, so I figured a delay of a day wouldn't hurt. Some of the broken packages match the existing i386 results, so these are not necessarily amd64-specific problems. The builds are incremental. This and the others took so long because it was the first 2009Q3 build. sweeet!
Re: [Fwd: pkgbox64 pkgsrc DragonFly 2.5.1/x86_64 2009-10-16 21:12]
On Wed, October 21, 2009 12:36 pm, Simon 'corecode' Schubert wrote: Justin C. Sherrill wrote: These should work for all amd64 versions, via pkgin or pkg_radd or manual download. The report didn't upload because of a permissions problem, which I've fixed and the next run (already started) should have an up-to-date report to accompany it. Do you think you can push the report still or is it too late? Are you performing incremental builds? Too late - it already has 3,500 packages since my post this morning, so I figured a delay of a day wouldn't hurt. Some of the broken packages match the existing i386 results, so these are not necessarily amd64-specific problems. The builds are incremental. This and the others took so long because it was the first 2009Q3 build.
Re: how to apply patches on a system that doesnot have functional network device ?
On Wed, October 21, 2009 12:34 pm, Saifi Khan wrote: Hi: Here is a situation that i'm facing on a Compaq C301TU laptop. The NIC card (Realtek) does not work due to driver issue. The WLAN card (Broadcom) does not work due to driver issue. Currently, i review the possible patch visually on an identical laptop (running FreeBSD-8) and then type out the code on the other laptop in sys/dev/netif/rl/if_rl.c file. Is there a better way to apply patches on a system that doesnot have functional network devices ? If you have a USB memory stick, that would at least save you the retyping.
Re: [Fwd: pkgbox64 pkgsrc DragonFly 2.5.1/x86_64 2009-10-16 21:12]
On Wed, October 21, 2009 12:19 pm, Saifi Khan wrote: Justin, thats awesome piece of work. Do you think it is a good idea to weigh build-fail/broken/masked packages against a usage list like https://www.osscensus.org/packages-rank-public.php?offset=0limit=778page=0 That's a good idea for prioritizing needed fixes, but there's something in the existing reports that that I think mostly covers it. Most of the items with a high usage rate in the report you linked tend to have a high downstream dependency, so if they break, lots of other packages break. The email report that comes from a bulk build shows a list of the top packages who break other packages by not building, so we should be able to get a list of what needs to be done directly from there, and it should follow the same general pattern as that usage list.
Re: how to apply patches on a system that doesnot have functional network device ?
2009/10/21 Saifi Khan saifi.k...@datasynergy.org Hi: Here is a situation that i'm facing on a Compaq C301TU laptop. The NIC card (Realtek) does not work due to driver issue. The WLAN card (Broadcom) does not work due to driver issue. Currently, i review the possible patch visually on an identical laptop (running FreeBSD-8) and then type out the code on the other laptop in sys/dev/netif/rl/if_rl.c file. Is there a better way to apply patches on a system that doesnot have functional network devices ? i'm leaning towards USB-Ethernet and was wondering if there is a USB-Ethernet device that is known to work fine with DragonFly BSD 2.4.1 ? Please accept my apologies for this newbie query and look forward to suggestions from the more experienced folks on this matter. I have an USB WLAN device supported by the ural(4) driver which works fine. Regards, Michael
qemu-system-x86_.core: not in executable format: File format not recognized
Hi: On a AMD64 X2 box running DragonFly BSD i'm trying to setup test/amd64, amd64x2# uname -a DragonFly amd64x2 2.4.1-RELEASE DragonFly v2.4.1-RELEASE #7: Wed Sep 30 18:16:27 PDT 2009 r...@pkgbox64.dragonflybsd.org:/usr/obj/usr/src-misc/sys/AMD64_GENERIC amd64 After building 'make scratch' for test/amd64 on the AMD64 X2 box (2GB DDR2, ASUS M2N-MX SE, 320 GB SATA II Seagate, nVidia Gigabit, nVidia SATA controller), the following message was seen WARNING: 64 bit loader installed, if it doesn't work then use 'sysloader' to install the 32 bit one cp /boot/loader /root/qemu//root/boot/loader sync Run the environment with: make QEMUDIR=/root/qemu/ run On running the command, amd64x2# make QEMUDIR=/root/qemu/ run Bus error (core dumped) *** Error code 138 Stop in /usr/src/test/amd64. amd64x2# On attempting to debug, amd64x2# gdb `qemu-system-x86_64 -curses -hda root.img -m 128 -no-fd-bootchk` qemu-system-x86_.core We need a terminal output gdb 6.7.1 This GDB was configured as amd64-dragonfly... /root/qemu/qemu-system-x86_.core: not in executable format: File format not recognized (gdb) q amd64x2# file qemu-system-x86_.core qemu-system-x86_.core: ELF 64-bit LSB core file x86-64, version 1 (FreeBSD), FreeBSD-style, from 'stem-x86_' amd64x2# Have some of the folks experienced with AMD64 observed this issue ? How do i get gdb to show atleast a stack trace of the generated core file ? thanks Saifi.
Re: USB WLAN/USB Ethernet device
On Wed, 21 Oct 2009, Michael Neumann wrote: 2009/10/21 Saifi Khan saifi.k...@datasynergy.org i'm leaning towards USB-Ethernet and was wondering if there is a USB-Ethernet device that is known to work fine with DragonFly BSD 2.4.1 ? I have an USB WLAN device supported by the ural(4) driver which works fine. Regards, Michael Hi Michael: Thank you for your reply. Can you share the USB WLAN device model details ? Any suggestions on an USB-Ethernet device as well ? thanks Saifi.
Re: USB WLAN/USB Ethernet device
2009/10/21 Saifi Khan saifi.k...@datasynergy.org On Wed, 21 Oct 2009, Michael Neumann wrote: 2009/10/21 Saifi Khan saifi.k...@datasynergy.org i'm leaning towards USB-Ethernet and was wondering if there is a USB-Ethernet device that is known to work fine with DragonFly BSD 2.4.1 ? I have an USB WLAN device supported by the ural(4) driver which works fine. Regards, Michael Hi Michael: Thank you for your reply. Can you share the USB WLAN device model details ? It's an D-Link DWL-G122. But you have to be careful, because it can be that depending on the revision of the device it's a different chipset! I can't tell you right now what revision has my device but I read here [1] (in German) that HW Ver C1 is a Ralink RT73 which seems to be not supported by the ural(4) driver. So according to the manpage you should buy revision b1. [1]: http://weblog.christoph-probst.com/article.php/20070402153533359 Regards, Michael
Re: Realtek NIC issue
On Wed, 21 Oct 2009, Sepherosa Ziehau wrote:
On Sun, Oct 18, 2009 at 9:12 AM, Saifi Khan saifi.k...@datasynergy.org
wrote:
i've a laptop with identical hardware, running FreeBSD
8-CURRENT-200906 (ie. this one, used to write this mail)
and the following lines are seen in the driver code
src/sys/pci/if_rl.c
...
if (sc-rl_type == 0) {
device_printf(dev, unknown device ID: %x assuming 8139\n,
rl_did);
sc-rl_type = RL_8139;
/*
* Read RL_IDR register to get ethernet address as accessing
* EEPROM may not extract correct address.
*/
for (i = 0; i ETHER_ADDR_LEN; i++)
eaddr[i] = CSR_READ_1(sc, RL_IDR0 + i);
}
...
What do you think ?
Thank you for the submission, please cherry-pick:
d9893ddff7cb5a3cadf0051f7b80831951499854
to 2.4 branch and test.
Best Regards,
sephe
Thank you Sephe, the Realtek NIC is working fine now.
i could successfully run some traffic through ping, pkg_radd.
thanks
Saifi.
ACPI Exception: AE_NO_HARDWARE_RESPONSE
Hi: On Compaq C301TU laptop, the following lines get dumped on screen everytime there is a change in the power state (on-off, off-on). system power profile changed to 'economy' ACPI Exception: AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] 20090521 evregion-531 ACPI Error (psparse-0633): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.PCLK] (Node 0xc40694cc), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0633): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_._Q1D] (Node 0xc406956c), AE_NO_HARDWARE_RESPONSE system power profile changed to 'performance' ACPI Exception: AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] 20090521 evregion-531 ACPI Error (psparse-0633): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.PCLK] (Node 0xc40694cc), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0633): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_._Q1D] (Node 0xc406956c), AE_NO_HARDWARE_RESPONSE system power profile changed to 'economy' ACPI Exception: AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] 20090521 evregion-531 ACPI Error (psparse-0633): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.PCLK] (Node 0xc40694cc), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0633): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_._Q1D] (Node 0xc406956c), AE_NO_HARDWARE_RESPONSE system power profile changed to 'performance' The power profile change notification is expected, but the ACPI Error|Exception notification is surprising as i don't see this on an identical laptop running FreeBSD-8. The 'dmesg extract' below show information specific to ACPI. Copyright (c) 2003-2009 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 2.4.1-RELEASE #2: Thu Oct 22 03:37:54 UTC 2009 r...@laptop.datasynergy.org:/usr/obj/usr/src/sys/DF241-P-SZ-RL-OS TSC clock: 1596044328 Hz, i8254 clock: 1193215 Hz CPU: Intel(R) Celeron(R) M CPU420 @ 1.60GHz (1596.01-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6e8 Stepping = 8 Features=0xafe9fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE Features2=0xc109SSE3,MON,TM2,xTPR,PDCM real memory = 2137522176 (2087424K bytes) avail memory = 2063863808 (2015492K bytes) kbd1 at kbdmux0 Pentium Pro MTRR support enabled fildesc_drvinit() building stdin, stdout, stderr: md0: Malloc disk ACPI: RSDP 0xf6510 00014 (v0 PTLTD ) ACPI: RSDT 0x7f68cbda 0004C (v1 HPQOEM SLIC-MPC 0604 LTP ) ACPI: FACP 0x7f693c86 00074 (v1 HP NISSAN 0604 LOHR 005A) ACPI: DSDT 0x7f68d506 06780 (v1 HP NISSAN 0604 INTL 20060608) ACPI: FACS 0x7f694fc0 00040 ACPI: APIC 0x7f693cfa 00068 (v1 HP NISSAN 0604 LOHR 005A) ACPI: HPET 0x7f693d62 00038 (v1 HP NISSAN 0604 LOHR 005A) ACPI: MCFG 0x7f693d9a 0003C (v1 HP NISSAN 0604 LOHR 005A) ACPI: BOOT 0x7f693fd8 00028 (v1 PTLTD $SBFTBL$ 0604 LTP 0001) ACPI: SLIC 0x7f693e08 00176 (v1 HPQOEM SLIC-MPC 0604 LOHR ) ACPI: APIC 0x7f693f7e 0005A (v1 PTLTDAPIC 0604 LTP ) ACPI: SSDT 0x7f68d2f8 0020A (v1 SataRe SataAhci 1000 INTL 20060217) ACPI: SSDT 0x7f68d11c 001DC (v1 PmRef Cpu0Cst 3001 INTL 20060217) ACPI: SSDT 0x7f68cc26 004F6 (v1 PmRefCpuPm 3000 INTL 20060217) npx0: math processor on motherboard npx0: INT 16 interface Using XMM optimized bcopy/copyin/copyout acpi0: HPQOEM SLIC-MPC on motherboard acpi0: Power Button (fixed) ACPI Error: Could not enable SleepButton event 20090521 evxfevnt-298 ACPI Warning: Could not enable fixed event 3 20090521 evxface-235 acpi0: Sleep Button (fixed) Warning: ACPI is disabling APM's device. You can't run both acpi_ec0: Embedded Controller: GPE 0x19 port 0x66,0x62 on acpi0 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 cpu0: ACPI CPU on acpi0 cpu_cst0: ACPI CPU C-State on cpu0 acpi_tz0: Thermal Zone on acpi0 acpi_tz1: Thermal Zone on acpi0 acpi_lid0: Control Method Lid Switch on acpi0 acpi_button0: Power Button on acpi0 battery0: ACPI Control Method Battery on acpi0 atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 How do I fix the ... ACPI Exception: AE_NO_HARDWARE_RESPONSE ... notification lines ? thanks Saifi.
[Fwd: pkgbox64 pkgsrc DragonFly 2.5.1/x86_64 2009-10-21 14:07]
New version of the 2.5 amd64 build - this time, the links to the work logs at: http://avalon.dragonflybsd.org/reports/20091021.1407/ work! So if there's something you want to fix, please look for it. Original Message Subject: pkgbox64 pkgsrc DragonFly 2.5.1/x86_64 2009-10-21 14:07 From:Charlie Root r...@pkgbox64.dragonflybsd.org Date:Wed, October 21, 2009 7:50 pm To: jus...@shiningsilence.com -- pkgsrc bulk build report DragonFly 2.5.1/x86_64 Compiler: gcc Build start: 2009-10-21 14:07 Build end: 2009-10-21 23:38 Full report: http://avalon.dragonflybsd.org/reports//20091021.1407/meta/report.html Machine readable version: http://avalon.dragonflybsd.org/reports//20091021.1407/meta/report.bz2 Total number of packages: 8969 Successfully built: 7480 Failed to build: 356 Depending on failed package: 572 Explicitly broken or masked: 497 Depending on masked package:64 Packages breaking the most other packages Package Breaks Maintainer - lang/ruby18-base 269 t...@netbsd.org print/ghostscript115 pkgsrc-us...@netbsd.org lang/ocaml35 a...@netbsd.org lang/mono 29 kef...@netbsd.org graphics/evas 15 ya...@yazzy.org textproc/xerces-c 12 pkgsrc-us...@netbsd.org x11/kdebase-workspace411 ma...@netbsd.org audio/mpg123 8 pkgsrc-us...@netbsd.org www/w3m7 uebay...@netbsd.org math/gap 7 c...@netbsd.org Build failures Package Breaks Maintainer - archivers/star uebay...@netbsd.org audio/akode-plugins-mpc ha...@netbsd.org audio/bmp-macpkgsrc-us...@netbsd.org audio/buzztard 1 pkgsrc-us...@netbsd.org audio/csound4pkgsrc-us...@netbsd.org audio/libmusepack 1 pkgsrc-us...@netbsd.org audio/maplay pkgsrc-us...@netbsd.org audio/mpg123 8 pkgsrc-us...@netbsd.org audio/py-id3lib pkgsrc-us...@netbsd.org py26-id3lib-0.5.1pkgsrc-us...@netbsd.org py25-id3lib-0.5.1pkgsrc-us...@netbsd.org audio/tremor-tools ch...@netbsd.org benchmarks/iozonepkgsrc-us...@netbsd.org benchmarks/randread gr...@netbsd.org biology/py-mol pkgsrc-us...@netbsd.org py26-mol-0.98nb4 pkgsrc-us...@netbsd.org biology/rasmol pkgsrc-us...@netbsd.org cad/atlc dmcmah...@netbsd.org chat/finch pkgsrc-us...@netbsd.org chat/galepkgsrc-us...@netbsd.org chat/silc-client 1 s...@netbsd.org chat/silc-server s...@netbsd.org chat/tircpkgsrc-us...@netbsd.org chat/zircon pkgsrc-us...@netbsd.org comms/asterisk16 jnem...@netbsd.org comms/conserver pkgsrc-us...@netbsd.org comms/mgetty+sendfax pkgsrc-us...@netbsd.org comms/modemd tsa...@netbsd.org comms/plptools pkgsrc-us...@netbsd.org cross/h8300-hms-gcc pkgsrc-us...@netbsd.org cross/i386-cygwin32 pkgsrc-us...@netbsd.org cross/i386-linux pkgsrc-us...@netbsd.org cross/i386-mingw32 pkgsrc-us...@netbsd.org cross/i386-msdosdjgpppkgsrc-us...@netbsd.org cross/mipsEEel-netbsdpkgsrc-us...@netbsd.org databases/gnats re...@netbsd.org databases/openldap-smbk5pwd g...@netbsd.org databases/php-mssql1 jdole...@netbsd.org php4-mssql-4.4.9 1 jdole...@netbsd.org devel/binutils pkgsrc-us...@netbsd.org devel/electricfence pkgsrc-us...@netbsd.org devel/elfsh pkgsrc-us...@netbsd.org devel/gsoap chrisware...@chriswareham.demon.co.uk devel/gtl
Re: [Fwd: pkgbox64 pkgsrc DragonFly 2.5.1/x86_64 2009-10-21 14:07]
Justin C. Sherrill wrote: lang/ruby18-base 269 t...@netbsd.org Ruby breaks because it installs files into lib/ruby/1.8/x86_64-dragonfly/, whereas pkgsrc expects them to be in lib/ruby/1.8/amd64-dragonfly/. This is because configure automatically converts amd64 to x86_64, and netbsd calls the platform (and architecture) x86_64. I think we should bite the bullet now and call it x86_64 in uname, instead of trying to hack around this in pkgsrc. cheers simon -- 3 the future +++ RENT this banner advert +++ ASCII Ribbon /\ rock the past +++ space for low CHF NOW!1 +++ Campaign \ / Party Enjoy Relax | http://dragonflybsd.org Against HTML \ Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \
Re: [Fwd: pkgbox64 pkgsrc DragonFly 2.5.1/x86_64 2009-10-21 14:07]
Many packages were prefailed with [bsd.options.mk] One of the following options must be selected: inet
Re: [Fwd: pkgbox64 pkgsrc DragonFly 2.5.1/x86_64 2009-10-21 14:07]
On Wed, October 21, 2009 8:28 pm, Jeremy C. Reed wrote: Many packages were prefailed with [bsd.options.mk] One of the following options must be selected: inet I didn't mess with this option in any of the builds, so this must be caused by something farther down the line, so to speak. I don't know what, as I haven't dug into the mk files.
USB-serial setup
Hi: A USB-serial adapter has been connected to my Compaq C301TU laptop. the other end connects to my AMD64 X2 box. Both the systems are running DragonFly BSD 2.4.1. On the laptop, the USB-serial device is detected as ugen0: Prolific Technology Inc. USB-Serial Controller, class 0/0, rev 1.10/3.00, addr 2 on uhub0 The entries in the /dev directory look like crw-r--r-- 1 root operator 27, 0x Oct 22 09:33 /dev/ugen0 crw-r--r-- 1 root operator 27, 0x0001 Oct 22 09:33 /dev/ugen0.1 crw-r--r-- 1 root operator 27, 0x0002 Oct 22 09:33 /dev/ugen0.2 crw-r--r-- 1 root operator 27, 0x0003 Oct 22 09:33 /dev/ugen0.3 The output of the usbdevs -d -v command is Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 uhub0 port 1 addr 2: full speed, power 100 mA, config 1, USB-Serial Controller(0x2303), Prolific Technology Inc.(0x067b), rev 3.00 ugen0 port 2 powered Controller /dev/usb1: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 uhub1 port 1 powered port 2 powered Controller /dev/usb2: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 uhub2 port 1 powered port 2 powered The generic 'ucom' driver has been loaded using laptop# kldload -v ucom Loaded ucom, id=5 My query is: i donot see any cua0, ttyS0, ttyUSB0, so, what is the virtual serial device to be specified while running cu ? ie. # cu -s 19200 -l /dev/device thanks Saifi.
