Do we need this junk?
Can anything in the list below be removed from CURRENT? legacyfree1# cd dev/ legacyfree1# grep -irsn isa ./ | grep -i include ./acpica/acpi.c:54:#include isa/isavar.h ./acpica/acpi.c:55:#include isa/pnpvar.h ./acpica/acpi_acad.c:46:#include isa/isavar.h ./acpica/acpi_acad.c:47:#include isa/pnpvar.h ./acpica/acpi_isab.c:44:#include isa/isavar.h ./advansys/adv_eisa.c:51:#include dev/eisa/eisaconf.h ./advansys/adv_isa.c:63:#include isa/isavar.h ./aha/aha_isa.c:72:#include isa/isavar.h ./aha/aha_mca.c:44:#include isa/isavar.h ./ahb/ahb.c:52:#include dev/eisa/eisaconf.h ./aic/aic_cbus.c:39:#include isa/isavar.h ./aic/aic_isa.c:39:#include isa/isavar.h ./aic7xxx/ahc_eisa.c:37:#include dev/eisa/eisaconf.h ./aic7xxx/ahc_isa.c:44:#include isa/isavar.h ./an/if_an_isa.c:69:#include isa/isavar.h ./an/if_an_isa.c:70:#include isa/pnpvar.h ./ar/if_ar_isa.c:57:#include isa/isavar.h ./ar/if_ar_isa.c:58:#include isa_if.h ./arcmsr/arcmsr.c:80:#include isa/rtc.h ./arl/if_arl_isa.c:57:#include isa/isavar.h ./arl/if_arl_isa.c:58:#include isa/pnpvar.h ./arl/if_arl_isa.c:59:#include isa/isa_common.h ./asr/osd_util.h:80:# includei386/isa/dpt_osd_defs.h ./asr/osd_util.h:83:# includei386/isa/dpt_osd_defs.h ./asr/sys_info.h:55:# includei386/isa/dpt_osd_util.h ./asr/sys_info.h:58:# includei386/isa/dpt_osd_util.h ./ata/ata-cbus.c:45:#include isa/isavar.h ./ata/ata-isa.c:45:#include isa/isavar.h ./atkbdc/atkbd.c:57:#include isa/isareg.h ./atkbdc/atkbdc.c:54:#include isa/isareg.h ./atkbdc/atkbdc_isa.c:45:#include isa/isareg.h ./atkbdc/atkbdc_isa.c:46:#include isa/isavar.h ./atkbdc/psm.c:64:#include opt_isa.h ./atkbdc/psm.c:87:#include isa/isavar.h ./buslogic/bt_eisa.c:46:#include dev/eisa/eisaconf.h ./buslogic/bt_isa.c:46:#include isa/isavar.h ./buslogic/bt_mca.c:58:#include isa/isavar.h ./cs/if_cs_isa.c:46:#include isa/isavar.h ./ct/ct_isa.c:59:#include dev/isa/isareg.h ./ct/ct_isa.c:60:#include dev/isa/isavar.h ./ct/ct_isa.c:61:#include dev/isa/isadmavar.h ./ct/ct_isa.c:82:#include isa/isavar.h ./ctau/if_ct.c:44:#include isa/isavar.h ./cx/if_cx.c:47:#include isa/isavar.h ./cy/cy_isa.c:48:#include isa/isavar.h ./dpt/dpt_eisa.c:31:#include opt_eisa.h ./dpt/dpt_eisa.c:45:#include dev/eisa/eisaconf.h ./dpt/dpt_isa.c:41:#include isa/isavar.h ./dpt/dpt_scsi.c:53:#include opt_eisa.h ./ed/if_ed_cbus.c:47:#include isa/isavar.h ./ed/if_ed_isa.c:49:#include isa/isavar.h ./eisa/eisaconf.c:36:#include opt_eisa.h ./eisa/eisaconf.c:51:#include dev/eisa/eisaconf.h ./eisa/eisaconf.h:37:#include eisa_if.h ./ep/if_ep_eisa.c:41:#include dev/eisa/eisaconf.h ./ep/if_ep_isa.c:49:#include isa/isavar.h ./ep/if_ep_isa.c:55:#include i386/isa/elink.h ./ex/if_ex.c:70:#include isa/isavar.h ./ex/if_ex.c:71:#include isa/pnpvar.h ./ex/if_ex_isa.c:48:#include isa/isavar.h ./ex/if_ex_isa.c:49:#include isa/pnpvar.h ./fb/splash_bmp.c:42:#include isa/isareg.h ./fb/vga.c:62:#include isa/isareg.h ./fdc/fdc.c:84:#include isa/isavar.h ./fdc/fdc.c:85:#include isa/isareg.h ./fdc/fdc.c:87:#include isa/rtc.h ./fdc/fdc_isa.c:44:#include isa/isavar.h ./fdc/fdc_isa.c:45:#include isa/isareg.h ./fe/if_fe_cbus.c:50:#include isa/isavar.h ./fe/if_fe_isa.c:49:#include isa/isavar.h ./hfa/hfa_eisa.c:88:#include dev/eisa/eisa_busreg.h ./hfa/hfa_eisa.c:89:#include dev/eisa/eisa_busvar.h ./ida/ida_eisa.c:49:#include dev/eisa/eisaconf.h ./ie/if_ie.c:144:#include i386/isa/elink.h ./ie/if_ie_isa.c:60:#include isa/isavar.h ./ie/if_ie_isa.c:61:#include isa/pnpvar.h ./ie/if_ie_isa.c:63:#include i386/isa/elink.h ./ieee488/ibfoo.c:50:#include isa/isavar.h ./ieee488/pcii.c:52:#include isa/isavar.h ./ieee488/upd7210.c:51:#include isa/isavar.h ./ipmi/ipmi_isa.c:43:#include isa/isavar.h ./joy/joy_isa.c:46:#include isa/isavar.h ./joy/joy_isa.c:47:#include isa_if.h ./le/if_le_cbus.c:57:#include isa/isavar.h ./le/if_le_isa.c:96:#include isa/isavar.h ./lmc/if_lmc.c:272:# include i386/isa/dma.h ./lmc/if_lmc.c:273:# include i386/isa/isavar.h ./mcd/mcd.c:63:#include isa/isavar.h ./mcd/mcd_isa.c:24:#include isa/isavar.h ./mse/mse.c:88:#include isa/isavar.h ./mse/mse_cbus.c:88:#include isa/isavar.h ./mse/mse_isa.c:88:#include isa/isavar.h ./ncv/ncr53c500_pccard.c:58:#include cam/scsi/scsi_low_pisa.h ./nsp/nsp_pccard.c:57:#include cam/scsi/scsi_low_pisa.h ./pbio/pbio.c:50:#include isa/isavar.h ./pccbb/pccbb_isa.c:52:#include isa/isavar.h ./pcf/pcf_isa.c:50:#include isa/isareg.h ./pcf/pcf_isa.c:51:#include isa/isavar.h ./pci/isa_pci.c:44:#include isa/isavar.h ./pdq/if_fea.c:49:#include dev/eisa/eisaconf.h ./ppc/ppc_acpi.c:30:#include opt_isa.h ./ppc/ppc_acpi.c:39:#include isa/isareg.h ./ppc/ppc_acpi.c:40:#include isa/isavar.h ./ppc/ppc_isa.c:43:#include isa/isareg.h ./ppc/ppc_isa.c:45:#include isa/isavar.h ./rc/rc.c:57:#include isa/isavar.h ./rp/rp_isa.c:57:#include isa/isavar.h ./sbni/if_sbni_isa.c:48:#include isa/isavar.h ./scd/scd.c:65:#include isa/isavar.h ./scd/scd_isa.c:23:#include isa/isavar.h ./si/si.c:46:#include opt_eisa.h ./si/si_eisa.c:37:#include dev/eisa/eisaconf.h
Porting FreeBSD to a new Architecture?
Hello, I'm looking for documentation that could possibly help me port FreeBSD to a new architecture. I'm mainly interested in how you guys did the xbox and amd64 ports. i.e. x86 instruction set. Thanks! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Porting FreeBSD to a new Architecture?
On 4/4/07, Rink Springer [EMAIL PROTECTED] wrote: Hi Nikolas, On Wed, Apr 04, 2007 at 02:23:44AM -0500, Nikolas Britton wrote: I'm looking for documentation that could possibly help me port FreeBSD to a new architecture. I'm mainly interested in how you guys did the xbox and amd64 ports. i.e. x86 instruction set. I can answer the Xbox question for you... basically, what I did was get a good understanding of how the xbox internals worked (i.e. what the exact differences are between an ordinary PC and an Xbox). Based on this understanding, I patched the Xbox boot loader (Cromwell) so it could properly load FreeBSD ELF images. Once that was done, I worked my way up from the first piece of code executed (that is in i386/i386/locore.s). I crafted some assembly code which could control the Xbox LED's, and I used this to determine where the Xbox would crash... Once I got the initial machine-dependant stuff out of the way, I created a console driver so I could see what was going on (which I later on totally rewrote); and worked my way up from here... Expect a lot of painstaking debugging in the progress... Thanks! Can anyone explain how the /usr/src/sys/conf directory works? I'd like to get a better feel of how everything is laid out in sys but I can't find anything in the developer handbook or man hier. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Amd64 Unstable Areca
On 3/30/07, Phillip Neumann [EMAIL PROTECTED] wrote: El dom, 25-03-2007 a las 10:11 -0600, Scott Long escribió: Please try the following patch against the latest 6-STABLE driver sources: http://people.freebsd.org/~scottl/arcmsr.simq.diff. Scott Just in case you mind, the problem does not seem to be present with the patch. Havent had crash in days. (When one occur, ill notify) thanks!! Have you tried making it crash? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Amd64 Unstable Areca
On 3/30/07, Scott Long [EMAIL PROTECTED] wrote: Nikolas Britton wrote: On 3/30/07, Phillip Neumann [EMAIL PROTECTED] wrote: El dom, 25-03-2007 a las 10:11 -0600, Scott Long escribió: Please try the following patch against the latest 6-STABLE driver sources: http://people.freebsd.org/~scottl/arcmsr.simq.diff. Scott Just in case you mind, the problem does not seem to be present with the patch. Havent had crash in days. (When one occur, ill notify) thanks!! Have you tried making it crash? Erich Chen pointed a problem with the patch I generated, but I think it's mostly harmless. Good to know that it seems to be helping the problem. Scott And??? don't leave us hanging, what's the problem? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Amd64 Unstable Areca
On 3/25/07, Scott Long [EMAIL PROTECTED] wrote: Nikolas Britton wrote: Yeah are hardware is nearly identical. I don't remember what I did to my custom driver, I know I fixed some syntax errors and merged in changes that were made on top of the 1.20.00.02 code base. I'm not sure but I think most of those changes were thrown out with the import of 1.20.00.13 and 14. Yes ..0.13 is the driver from 6.2-RELEASE-p2 and no I don't see any g_vfs errors, I do see a crap load of httpd errors that someone needs to investigate, lucky me. :-/ It's not likely I'd see them anyhow because the business slows way down during this time of year: Please try the following patch against the latest 6-STABLE driver sources: http://people.freebsd.org/~scottl/arcmsr.simq.diff. Thanks Scott... Unfortunately, or fortunately depending on your outlook, spring break ends today and I've got a crap load of studying to do, so no time to play guinea pig... But because I'm such a nice guy I've compiled i386 and amd64 binaries so the others can play along. I compiled everything against 6.2-RELEASE-p2... Download them here: http://www.nbritton.org/uploads/areca/fb62/ Do you have any testing scripts so the group can do repeatable comparison tests using the old and new kernel modules? Thanks. Oh and here's a file list but gmail is probably going to mutilate it: arcmsr.c.1824: ASCII C program text arcmsr.h.1142: ISO-8859 C program text arcmsr.kld.fb62.i386.032607: ELF 32-bit LSB relocatable, Intel 80386, version 1 (FreeBSD), not stripped arcmsr.ko.debug.fb62.amd64.032607: ELF 64-bit LSB relocatable, AMD x86-64, version 1 (FreeBSD), not stripped arcmsr.ko.fb62.amd64.032607: ELF 64-bit LSB relocatable, AMD x86-64, version 1 (FreeBSD), not stripped arcmsr.ko.fb62.i386.032607:ELF 32-bit LSB shared object, Intel 80386, version 1 (FreeBSD), not stripped arcmsr.o.fb62.amd64.032607:ELF 64-bit LSB relocatable, AMD x86-64, version 1 (FreeBSD), not stripped arcmsr.o.fb62.i386.032607: ELF 32-bit LSB relocatable, Intel 80386, version 1 (FreeBSD), not stripped i386_build_log.txt:ASCII text, with very long lines ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Amd64 Unstable Areca
On 3/24/07, Jan Mikkelsen [EMAIL PROTECTED] wrote: Hi, Nikolas Britton wrote: If that doesn't work move back down to 1.20.00.12: http://www.nbritton.org/uploads/areca/ I could consistently make 1.20.00.12 corrupt data. If you are going to go back, that's probably a bad choice. 1.20.00.02 didn't seem to have corruption problems. The 1.20.00.12 driver I pointed to was a custom hack I did for my servers, It worked fine for the 7 months I was using it... I'm assuming we're talking about I/O load, the servers rarely see high cpu loads... the hardware: http://www.supermicro.com/products/motherboard/Xeon1333/5000P/X7DBE.cfm arcmsr0: Areca SATA Host Adapter RAID Controller (RAID6 capable) ARECA RAID ADAPTER0: Driver Version 1.20.00.13 2006-8-18 ARECA RAID ADAPTER0: FIRMWARE VERSION V1.41 2006-5-24 pass1 at arcmsr0 bus 0 target 16 lun 0 pass1: Areca RAID controller R001 Fixed Processor SCSI-0 device da0 at arcmsr0 bus 0 target 0 lun 0 da0: Areca ARC-1220-VOL#00 R001 Fixed Direct Access SCSI-3 device da0: 166.666MB/s transfers (83.333MHz, offset 32, 16bit), Tagged Queueing Enabled da0: 1430511MB (2929687040 512 byte sectors: 255H 63S/T 182364C) I just upgraded them for the DST change. :-/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Amd64 Unstable Areca
On 3/24/07, Jan Mikkelsen [EMAIL PROTECTED] wrote: Nikolas Britton wrote: On 3/24/07, Jan Mikkelsen [EMAIL PROTECTED] wrote: Hi, Nikolas Britton wrote: If that doesn't work move back down to 1.20.00.12: http://www.nbritton.org/uploads/areca/ I could consistently make 1.20.00.12 corrupt data. If you are going to go back, that's probably a bad choice. 1.20.00.02 didn't seem to have corruption problems. The 1.20.00.12 driver I pointed to was a custom hack I did for my servers, It worked fine for the 7 months I was using it... I'm assuming we're talking about I/O load, the servers rarely see high cpu loads... the hardware: http://www.supermicro.com/products/motherboard/Xeon1333/5000P/X7DBE.cfm arcmsr0: Areca SATA Host Adapter RAID Controller (RAID6 capable) ARECA RAID ADAPTER0: Driver Version 1.20.00.13 2006-8-18 ARECA RAID ADAPTER0: FIRMWARE VERSION V1.41 2006-5-24 pass1 at arcmsr0 bus 0 target 16 lun 0 pass1: Areca RAID controller R001 Fixed Processor SCSI-0 device da0 at arcmsr0 bus 0 target 0 lun 0 da0: Areca ARC-1220-VOL#00 R001 Fixed Direct Access SCSI-3 device da0: 166.666MB/s transfers (83.333MHz, offset 32, 16bit), Tagged Queueing Enabled da0: 1430511MB (2929687040 512 byte sectors: 255H 63S/T 182364C) I just upgraded them for the DST change. :-/ Interesting. How did you modify the 1.20.00.12 driver from Areca? Is the 1.20.00.13 driver mentioned above the one from 6.2-RELEASE? If so, do you ever see g_vfs_done errors on this machine when it is under heavy I/O load? From the machine I used to test the corruption issue (currently running 6-STABLE): arcmsr0: Areca SATA Host Adapter RAID Controller (RAID6 capable) mem 0xc850-0xc8500fff,0xc8c0-0xc8ff irq 16 at device 14.0 on pci10 ARECA RAID ADAPTER0: Driver Version 1.20.00.14 2007-2-05 ARECA RAID ADAPTER0: FIRMWARE VERSION V1.42 2006-10-13 pass4 at arcmsr0 bus 0 target 16 lun 0 pass4: Areca RAID controller R001 Fixed Processor SCSI-0 device This is an ARC-1220 in a Supermicro X7DB8 based machine. Yeah are hardware is nearly identical. I don't remember what I did to my custom driver, I know I fixed some syntax errors and merged in changes that were made on top of the 1.20.00.02 code base. I'm not sure but I think most of those changes were thrown out with the import of 1.20.00.13 and 14. Yes ..0.13 is the driver from 6.2-RELEASE-p2 and no I don't see any g_vfs errors, I do see a crap load of httpd errors that someone needs to investigate, lucky me. :-/ It's not likely I'd see them anyhow because the business slows way down during this time of year: uptime: 11:53PM up 3 days, 8:56, 1 user, load averages: 0.00, 0.00, 0.00 I remember seeing that g_vfs error one time when one of the sata cables came loose. All hell broke loose and FreeBSD had a major brain fart, I've had several other sata cable 'incidents' but that's the only time FreeBSD croaked (with an areca card). The cable incidents happen with all are sata raid gear and it's not specific to areca products. I've come to the conclusion that the sata cables simply vibrate loose. I'm debating at the moment if we should move to sas multi-lane backplanes. The biggest problem I forsee is if one of the multi-lane cables comes loose, if that happened the array is toast .. anyhow... I simply rebooted the server, rebuilt the array, verified the array, and ran fsck. The file system corruption was typical of a power failure during disk write. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Amd64 Unstable Areca
A newer version of the driver has been release to fix this problem (I think): http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/arcmsr/ If that doesn't work move back down to 1.20.00.12: http://www.nbritton.org/uploads/areca/ Added erich and scott to the cc list. On 3/22/07, Phillip Neumann [EMAIL PROTECTED] wrote: Dear FreeBSD-stable... My amd64 box is not very stable. In its hardware list, you can see there is an areca 1210 card, wich suffer the errata of 6.2-release (high load crash) Last week or so, i saw a commit where the areca bugs were fixed, so i updated the system. I can still see the mashine crashing under load attached are dmesg -a, and a simple 'bt' of kgdb. sometimes (under load) i see this message: Interrupt storm detected on swi2:; throttling interrupt source i get the same behaviour with sched_bsd or sched_ule Is this info useful to determine where the problem is? If so, where is it? :-) Has this something to do with the fs? or the scheduler? thanks! killfill. [EMAIL PROTECTED] /usr/obj/usr/src/sys/WORM]# kgdb kernel.debug /var/crash/vmcore.1 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol ps_pglobal_lookup] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-marcel-freebsd. Unread portion of the kernel message buffer: panic: handle_workitem_remove: lost inodedep cpuid = 0 Uptime: 2h19m9s Dumping 2047 MB (2 chunks) chunk 0: 1MB (156 pages) ... ok chunk 1: 2047MB (524016 pages) 2031 2015 1999 1983 1967 1951 1935 1919 1903 1887 1871 1855 1839 1823 1807 1791 1775 1759 1743 1727 1711 1695 1679 1663 1647 1631 1615 1599 1583 1567 1551 1535 1519 1503 1487 1471 1455 1439 1423 1407 1391 1375 1359 1343 1327 1311 1295 1279 1263 1247 1231 1215 1199 1183 1167 1151 1135 1119 1103 1087 1071 1055 1039 1023 1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 #0 doadump () at pcpu.h:172 172 __asm __volatile(movq %%gs:0,%0 : =r (td)); (kgdb) bt #0 doadump () at pcpu.h:172 #1 0x0004 in ?? () #2 0x804085e7 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409 #3 0x80408c81 in panic (fmt=0xff007a9cd980 #65533;VTx) at /usr/src/sys/kern/kern_shutdown.c:565 #4 0x80589fc6 in handle_workitem_remove (dirrem=0xff001a6c7b40, xp=0x0) at /usr/src/sys/ufs/ffs/ffs_softdep.c:3599 #5 0x8058a3dc in process_worklist_item (mp=0xff0031482630, flags=0) at /usr/src/sys/ufs/ffs/ffs_softdep.c:962 #6 0x8058fd3d in softdep_process_worklist (mp=0xff0031482630, full=0) at /usr/src/sys/ufs/ffs/ffs_softdep.c:851 #7 0x80590031 in softdep_flush () at /usr/src/sys/ufs/ffs/ffs_softdep.c:762 #8 0x803ed647 in fork_exit (callout=0x8058fee0 softdep_flush, arg=0x0, frame=0xb49abc50) at /usr/src/sys/kern/kern_fork.c:821 #9 0x80615b0e in fork_trampoline () at /usr/src/sys/amd64/amd64/exception.S:394 #10 0x in ?? () #11 0x in ?? () #12 0x0001 in ?? () #13 0x in ?? () #14 0x in ?? () #15 0x in ?? () #16 0x in ?? () #17 0x in ?? () #18 0x in ?? () #19 0x in ?? () #20 0x in ?? () #21 0x in ?? () #22 0x in ?? () #23 0x in ?? () #24 0x in ?? () #25 0x in ?? () #26 0x in ?? () #27 0x in ?? () #28 0x in ?? () #29 0x in ?? () #30 0x in ?? () #31 0x in ?? () #32 0x in ?? () ---Type return to continue, or q return to quit--- #33 0x in ?? () #34 0x in ?? () #35 0x in ?? () #36 0x in ?? () #37 0x in ?? () #38 0x in ?? () #39 0x in ?? () #40 0x in ?? () #41 0x in ?? () #42 0x00b7d000 in ?? () #43 0x in ?? () #44 0xff002d080600 in ?? () #45 0x in ?? () #46 0xff00785456b0 in ?? () #47 0xff007a9f2000 in ?? () #48 0xb49ab878 in ?? () #49 0xff007a9cd980 in ?? () #50 0x8041ed56 in sched_switch (td=0x0, newtd=0x0, flags=1) at /usr/src/sys/kern/sched_4bsd.c:973 #51 0x in ?? () #52 0x in ?? () #53 0x in
Re: Xen Dom0, are we making progress?
On 3/13/07, Kip Macy [EMAIL PROTECTED] wrote: I know you were working on Xen support in FreeBSD, but web about it (http://www.fsmware.com/xenofreebsd/7.0/STATUS) has one year old info (support planned in FreeBSD 6.1). So is there any progress, or Xen will not be in any near future release? Basically Xen did not mature in the fashion that I anticipated. As far as I can tell it is really only good for server consolidation for large Linux distro vendors. You need to have what amounts to a private branch. The xen developers don't appear to understand the importance of interface versioning. They broke ABI compatibility going from 3.0.2 - 3.0.3 (trivial to fix, but that is not the point). When last I worked on it, they had one branch that was in constant flux and another branch that only received minor bug fixes and was 18 months behind from a functionality standpoint (think 5.x / 4.x). There are numerous other logging / supportability issues that I think are only addressed by the major distros. As it stood 6 months ago, unless you understood the internals of various bits of the code, there was no way of diagnosing failures due to a misconfiguration. This is not to say that it isn't cool technology, but rather that isn't going to be useful for the things I wanted to use it for so my time is being directed elsewhere. If I ever have a need for EC2 I may look at it again. One of the guys who ported FreeBSD to the xbox has expressed interest - so something may yet come of it. I'm happy to provide technical support to an individual who is largely self-sustaining in working on the code. What about implementing something like DragonFly BSD virtual kernels? Matthew Dillon talks about it in is bsdtalk interview: http://cisx1.uma.maine.edu/~wbackman/bsdtalk/bsdtalk098.mp3 I suppose it's sorta like linux compat / windows on windows / coLinux... Towards the end of the interview he talk about it being extremely easy to implement: 1. signal mailboxes. 2. memory map / virtual page table support. 3. vm space management. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Don't buy AMD products (was Re: Xorg and ATI card query.)
We need to start hounding on AMD to publish the developer documentation for all radeon chipsets. I for one will not buy any AMD or ATI components until they decide to fix the problem. Here's the email address of AMD's president: [EMAIL PROTECTED] Give him your two cents. On 3/12/07, Daniel O'Connor [EMAIL PROTECTED] wrote: On Tuesday 13 March 2007 05:10, Yann Golanski wrote: I have an ATI Radeon X1950 Sapphire and I am trying to get X/FreeBSD working with it. My system is a clean install of FreBSD. I've managed to get VESA to work but cannot get much more than that. There is no open source support for this card (alas). It's VESA or fglrx. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Xen Dom0, are we making progress?
Free Solaris DVD software kits (Free shipping too): http://www.sun.com/solaris/freemedia Sweet! On 3/12/07, Nikolas Britton [EMAIL PROTECTED] wrote: Is FreeBSD making any progress in Xen Dom0 / Intel VT support? I'd really like to consolidate some underutilized FreeBSD servers. Are their any alternative solutions that will enable me to do this kind of stuff with FreeBSD, or would it be better to go with Solaris Dom0 + FreeBSD DomU? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Xen Dom0, are we making progress?
Is FreeBSD making any progress in Xen Dom0 / Intel VT support? I'd really like to consolidate some underutilized FreeBSD servers. Are their any alternative solutions that will enable me to do this kind of stuff with FreeBSD, or would it be better to go with Solaris Dom0 + FreeBSD DomU? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Xen Dom0, are we making progress?
On 3/12/07, Ivan Voras [EMAIL PROTECTED] wrote: Nikolas Britton wrote: Free Solaris DVD software kits (Free shipping too): http://www.sun.com/solaris/freemedia Or NetBSD: http://www.netbsd.org/Ports/xen/ Yes that was my next choice after FreeBSD but they don't support the Areca RAID controllers we use and IIRC they have no plans to port the FreeBSD arcmsr driver. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Xen Dom0, are we making progress?
On 3/12/07, Ronald Klop [EMAIL PROTECTED] wrote: On Mon, 12 Mar 2007 20:16:32 +0100, Nikolas Britton [EMAIL PROTECTED] wrote: Is FreeBSD making any progress in Xen Dom0 / Intel VT support? I'd really like to consolidate some underutilized FreeBSD servers. Are their any alternative solutions that will enable me to do this kind of stuff with FreeBSD, or would it be better to go with Solaris Dom0 + FreeBSD DomU? http://docs.freebsd.org/44doc/papers/jail/jail.html google: jail freebsd Yes I'd like to know more about jails, is there a high level / executive summary type document that I can read somewhere? From what I remember jails are mostly designed to partition stuff... for security reasons. What I'd really love to do is split up each service (httpd, postgres, samba/nfs, ldap/nis, asterisk, etc.) into discrete virtual machines. It's too much work trying to make them all play nice on one system, especially during upgrades. As it is right now I don't upgrade any services once a system is in production use. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Xen Dom0, are we making progress?
On 3/12/07, Andras Gót [EMAIL PROTECTED] wrote: Nikolas Britton wrote: On 3/12/07, Ronald Klop [EMAIL PROTECTED] wrote: On Mon, 12 Mar 2007 20:16:32 +0100, Nikolas Britton [EMAIL PROTECTED] wrote: Is FreeBSD making any progress in Xen Dom0 / Intel VT support? I'd really like to consolidate some underutilized FreeBSD servers. Are their any alternative solutions that will enable me to do this kind of stuff with FreeBSD, or would it be better to go with Solaris Dom0 + FreeBSD DomU? http://docs.freebsd.org/44doc/papers/jail/jail.html google: jail freebsd Yes I'd like to know more about jails, is there a high level / executive summary type document that I can read somewhere? From what I remember jails are mostly designed to partition stuff... for security reasons. What I'd really love to do is split up each service (httpd, postgres, samba/nfs, ldap/nis, asterisk, etc.) into discrete virtual machines. It's too much work trying to make them all play nice on one system, especially during upgrades. As it is right now I don't upgrade any services once a system is in production use. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] Hi, For first read man jail. :) Apache, bind, mysql and postfix run fine in a jail. For postgres you've to turn on the jail.ipc. This is basicly not so bad, but definitely reduces security. For samba/nfs/ldap/nis and asterisk I don't have the experience, but if they not need ipc, they'll run fine out of the box. In jails I suggest that you mount your ports tree with some nullfs mount. With this you'll save some hd capacity. (The installed port list is in /var, not in /usr/ports.) In jails you can't do resource control, so keep that in mind. Is their anyway to transfer jails on the fly between systems... For example, say I wanted to transfer the http service to a more powerful box because load was too high, can you do stuff like this? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD and make -j# buildworld usability
On 10/13/06, Kent Stewart [EMAIL PROTECTED] wrote: On Friday 13 October 2006 07:31, Buki wrote: Hi, I searched the archives and web a little but found many different opinions on stability/usability of using make -j# with buildworld (and buildkernel). So I am asking if it is a good idea to use make -j on production boxes. I tested buildworlds with different values for -j. On single processors, using a script that basically looked like time make -j? ... yielded fastest builds when I didn't specify a value for -j. On dual cpu's a value around -j8 yielded the fastest build. That's odd, your results don't jive with this: http://people.freebsd.org/~fsmp/SMP/akgraph-a/graph1.html Although that report is quite old... My general rule of thumb for -j is n +1, where n equals the total number of cpu cores. This is generally enough to keep to processor(s) occupied without over stressing the system. Maybe n * 2 is more appropriate, can you post the results from your test? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 16M RAM enough for FreeBSD 6.1?
On 8/27/06, Peter Jeremy [EMAIL PROTECTED] wrote: On Sun, 2006-Aug-27 11:00:30 +0200, Torfinn Ingolfsen wrote: On Sun, 27 Aug 2006 17:13:29 +1000 Peter Jeremy [EMAIL PROTECTED] wrote: The CD-ROMs create a RAMdisk and need a minimum of 24MB last I checked. And I guess that the floppies work in the same way? Yes. Once you have FreeBSD installed, it will limp along in 16MB (though not very happily). Hmm, I see. I'm planning to run X on this old box (it's going to be a PictureFrame project), perhaps that will not work. I think you would be thrashing if there was any actual activity. I'll prod a friend with the same setup to comment tomorrow. I strongly suggest you find a SODIMM to expand it. Ok. Are all SODIMMs equal (ie. a real standard), or do I hvae to look specifically for memory upgrades for the Armada 1580 (or 1500 series)? I'm 99% certain that you can't use anything bigger than 64MB (at least a 128MB Cpq Armada SODIMM that I had wouldn't work in any of the 15xx machines I tried it in - that included a 1580). I'm not sure how interchangeable they are. Max mem size and chip density is a function of the MCH, If you post a copy of dmesg here I can look it up for you. From the service manual: The computer supports optional 8-, 16-, 32-, and 64-MB memory boards. The memory boards are 60 ns EDO RAM without parity. System memory can be expanded to 80-MB of DRAM depending on the model. The Service Manual is here: http://h2.www2.hp.com/bizsupport/TechSupport/CoreRedirect.jsp?redirectReason=DocIndexPDFprodSeriesId=96219targetPage=http%3A%2F%2Fh2.www2.hp.com%2Fbc%2Fdocs%2Fsupport%2FSupportManual%2Fc00139858%2Fc00139858.pdf And Addendum to the service manual is here: http://h2.www2.hp.com/bizsupport/TechSupport/CoreRedirect.jsp?redirectReason=DocIndexPDFprodSeriesId=96219targetPage=http%3A%2F%2Fh2.www2.hp.com%2Fbc%2Fdocs%2Fsupport%2FSupportManual%2Fc00139129%2Fc00139129.pdf -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 16M RAM enough for FreeBSD 6.1?
On 8/26/06, Torfinn Ingolfsen [EMAIL PROTECTED] wrote: Hello, I have an old laptop, a Compaq Armada 1580DMT, with 16M RAM, 2GB hd, floppy and CD-rom. It doesn't have built in networking, neither wired nor wireless. It does have PC card slots. It has had FreeBSD 4.9-release installed a long time, and was recently upgraded to 4.11-release from CD, sucessfully. However, I would like better pccard support, ie. 32 bit cardbus and wireless network cards, so I would like to install 6.1-release (or -stable) on it. How do you know it has CardBus / PCMCIA 2.1 / JEIDA 4.2? have you checked? This standard was introduced in 1995. However, when I try the 6.1-release CD (CD1), it boots as far as loading the kernel, botting the kernel, and then reboots again?? I have also tried 6.0-release, and 7.0-current (both July 06 and Aug 06 snapshots) with the same results. Are 16 Megs of RAM to little to install FreeBSD 6.0 or newer? Yep. Try DragonFly BSD, it's based on FreeBSD 4.x code so it should be able to cope with an antique such as this. NetBSD would also be a good choice. I would say at least 32MB for FreeBSD 6.x... my FreeBSD 6.1-STABLE kernel is using 52MB (I think I have debugging enabled though). -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 16M RAM enough for FreeBSD 6.1?
On 8/26/06, Nikolas Britton [EMAIL PROTECTED] wrote: On 8/26/06, Torfinn Ingolfsen [EMAIL PROTECTED] wrote: Hello, I have an old laptop, a Compaq Armada 1580DMT, with 16M RAM, 2GB hd, floppy and CD-rom. It doesn't have built in networking, neither wired nor wireless. It does have PC card slots. It has had FreeBSD 4.9-release installed a long time, and was recently upgraded to 4.11-release from CD, sucessfully. However, I would like better pccard support, ie. 32 bit cardbus and wireless network cards, so I would like to install 6.1-release (or -stable) on it. How do you know it has CardBus / PCMCIA 2.1 / JEIDA 4.2? have you checked? This standard was introduced in 1995. However, when I try the 6.1-release CD (CD1), it boots as far as loading the kernel, botting the kernel, and then reboots again?? I have also tried 6.0-release, and 7.0-current (both July 06 and Aug 06 snapshots) with the same results. Are 16 Megs of RAM to little to install FreeBSD 6.0 or newer? Yep. Try DragonFly BSD, it's based on FreeBSD 4.x code so it should be able to cope with an antique such as this. NetBSD would also be a good choice. I would say at least 32MB for FreeBSD 6.x... my FreeBSD 6.1-STABLE kernel is using 52MB (I think I have debugging enabled though). Ok I checked three other 6.x boxes. Dmesg reports the kernel using 35MB, 34MB, and 19MB of RAM at system startup. Top reports 297MB, 38MB, 167MB, and 621MB active... The two largest numbers are running X11/KDE and the two smallest numbers are servers. -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RocketRAID 2224
On 8/25/06, Dave Kingsley [EMAIL PROTECTED] wrote: I am attemping to use a RocketRAID 2224 8 channel card to set up a storage server. The server board is an Intel SE7230NH1-E with a P4-D 2.8GHz, 2GB RAM. When I set up a RAID5 with 7 750GB drives I get nothing but wierdness. Using sysinstall - Configure - Fdisk I can see the full size: DISK Geometry: 547149 cyls/255 heads/63 sectors = 8789948685 sectors (4291967MB) But Label sees: Disk: da0 Partition name: da0s1 Free: 200014030 blocks (97663MB) What am I doing wrong? Nothing. Sysinstall can't handle disks that big. There is a 2TB soft limit. UFS2 can support disks up to 8 ZettaBytes (8,589,934,592 TeraBytes) but some of the software tools have not been converted yet, see here: http://www.freebsd.org/projects/bigdisk/index.html -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: suggestions for SATA RAID cards
On 8/24/06, Andreas Klemm [EMAIL PROTECTED] wrote: On Wed, Aug 23, 2006 at 09:23:00AM +0100, Steven Hartland wrote: The Areca cards I can recommend. Highpoint 1820a is surprisingly good Many many years ago I bought a HighPoint HPT366 ATA66 controller. Thought its a good deal because it was cheap. Thought, an ATA interface can't be that complicated anymore so that its safe to buy a cheap product. Turned out that I was very wrong with my theorie. I ran into timeout problems, that couldn't be fixed. After days and nights of troubleshooting and testing I didn't get it to work reliably. I replaced it by buying a more expensive Promise controller. Since then I had zero problems. Since that time I lost trust in HighPoint products. Good stuff has its price. It must not always be the most expensive hardware. But going with the cheapest (and I assume the HighPoint product will again be in the low price segment) can be troublesome. As the owner of a HPT2220 and HPT1820A I have nothing but good things to say about it. In fact my experience is the inverse of yours. I've had nothing but problems with my Promise card. To make matters worse Promise doesn't support FreeBSD... No drivers, No docs, Nothing. HighPoint does support FreeBSD by providing their own FreeBSD drivers and HighPoint's code is in FreeBSD. The one bad thing I have to say about HighPoint is that their drivers are locked up in binary blobs. Areca's drivers on the other hand are fully open sourced and they have the fastest SATA hardware in the land thanks to the onboard 600MHz Intel XScale IOP and DDR333 cache. http://tweakers.net/reviews/557/1 Their new hardware (coming soon) will have a 800MHz XScale with DDR2-533 cache. This is from an ARC-1220 with 256MB cache and 7x300GB drives in RAID6: diskinfo -t da0 da0 512 # sectorsize 149764480 # mediasize in bytes (1.4T) 2929687040 # mediasize in sectors 182364 # Cylinders according to firmware. 255 # Heads according to firmware. 63 # Sectors according to firmware. Seek times: Full stroke: 250 iter in 5.022332 sec = 20.089 msec Half stroke: 250 iter in 3.809019 sec = 15.236 msec Quarter stroke: 500 iter in 4.055315 sec =8.111 msec Short forward:400 iter in 0.998948 sec =2.497 msec Short backward: 400 iter in 2.519062 sec =6.298 msec Seq outer: 2048 iter in 0.187788 sec =0.092 msec Seq inner: 2048 iter in 0.219632 sec =0.107 msec Transfer rates: outside: 102400 kbytes in 0.353485 sec = 289687 kbytes/sec middle:102400 kbytes in 0.372773 sec = 274698 kbytes/sec inside:102400 kbytes in 0.543272 sec = 188488 kbytes/sec Chad Leigh has an ARC-1130 with 1GB cache and he's getting even better numbers (300~400MB/s) using ZFS + Solaris Express. -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: suggestions for SATA RAID cards
On 8/24/06, Daniel O'Connor [EMAIL PROTECTED] wrote: On Thursday 24 August 2006 01:16, Nikolas Britton wrote: Stay away from Adaptec and Promise because they don't support FreeBSD. I would recommend Areca and/or HighPoint because they do officially support FreeBSD. 3Ware does support FreeBSD but I don't have experience with their cards so I can't say anything good or bad about them. I believe Promise *do* support FreeBSD quite a bit. Maybe as an after thought. I also don't see any link on their site for FreeBSD support, lets check google: http://www.google.com/search?q=site%3Awww.promise.com+FreeBSD http://www.google.com/search?q=site%3Ahighpoint-tech.com+FreeBSD So 7 Links Vs. 90 Links. Also if you click on that first link google gives you, about the up coming RAID6 SuperTrak EX4350 and EX12350 with support for FreeBSD etc.. Those card are clones of Areca's ARC-1210 and ARC-1230 cards... Striped down clones at that, they only have a 500MHz XScale IOP333... Areca is already moving from the 600MHz XScale IOP333 to the 800MHz XScale IOP341 with DDR2-533 support... Hell I bet they're just going to patch arcmsr(4) and call it there own. Areca's Erich Chen put a lot of work into arcmsr(4). There wouldn't be an arcmsr(4) in FreeBSD if it wasn't for Areca commitment to support FreeBSD. Now we have Promise trying to claim they support FreeBSD by patching a few lines of code from another company. Butch of BS is what that is. -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: suggestions for SATA RAID cards
On 8/23/06, Willem Jan Withagen [EMAIL PROTECTED] wrote: Hi, I've ran into sort of a snag with building a 2T file server. Given all the good press here for 3ware and the talk to the guys at the CeBIT I decided to go for a 9550SX-LP8. With that I bought a ASUS serverboard: K8N-LR with 165 dual core opteron. In itself is this a combo that I thing would do for a long time at my home. ;) However the 3ware controler decided not to play nice with 2 of the PCI-X boards I have here. It gets stuck in the bios disc scan. Disable int 13. The card is probably trying to load it's boot BIOS and another card is interfering with it... I had a Promise card that loved to f**k with my HighPoint controller. The solution to the problem was disabling int 13 on the HighPoint card by re-flashing the cards BIOS with a special switch set, I didn't need to boot from this card anyways. So I'm looking for alternatives with good support under amd64. I've seen that the Adaptecs are supported under aac(4). But what about Promisse or Highpoint RAID controllers? Stay away from Adaptec and Promise because they don't support FreeBSD. I would recommend Areca and/or HighPoint because they do officially support FreeBSD. 3Ware does support FreeBSD but I don't have experience with their cards so I can't say anything good or bad about them. If you want to go 64-bit Areca drivers are open source and the FreeBSD man page states that they work on amd64. -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: suggestions for SATA RAID cards
On 8/23/06, Bob Willcox [EMAIL PROTECTED] wrote: On Wed, Aug 23, 2006 at 12:02:47PM +0200, Willem Jan Withagen wrote: Steven Hartland wrote: The Areca cards I can recommend. Highpoint 1820a is surprisingly good for its price and the later cards have better performance still apparently. N.B. Use the min stripe size when creating the array for max performance with this card under FreeBSD. I was more thinking along the lines of a HighPoint 2720, but perhaps a 1820 would also do fine. What device driver would one use with that. [Ahhh, 'man -k highpoint' is your friend] Now what I liked about the 3ware stuff was that there are tools to work the raid from within FreeBSD. So that would require the newers ones... But the hardware list is only showing the 2320 and 2322 with a rr232x(4) driver. Which sort of makes me wonder for all the other stuff and their drivers. The motherboard has both PCI-X and PCI-E so that should not be a connector problem. Now which bus is faster: 64Bit PCI-X at 133 Mhz, or a PCI-E 16x? The x16 PCI-E has considerably faster theoretical speed than 133 PCI-X (appx. 4GBs vs. 1GBs). However, the RAID controllers that I've seen are at most x8 so they are only capable of transfer rates half that fast (2GBs). Personally, I would go with PCI-E since in some performance tests I did with Areca cards last year (both PCI-E and PCI-X) there appeared to be a slight performance advantage to the PCI-E cards (sorry, I don't recall any of the specifics anymore, so please take that for what it's worth). I agree. PCIe 8x is a faster bus and it's typically connected directly to the MCH (north bridge) unlike PCI-X which is stuck on the ICH (south bridge). Also the 2GB/s that was quoted for PCIe 8x is it's one-way data rate after calculating in overhead. It's a dual simplex interface meaning it has one path to send data and another path to receive data. Imagine a simple two lane road. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: suggestions for SATA RAID cards
On 8/23/06, Nikolas Britton [EMAIL PROTECTED] wrote: On 8/23/06, Bob Willcox [EMAIL PROTECTED] wrote: On Wed, Aug 23, 2006 at 12:02:47PM +0200, Willem Jan Withagen wrote: Steven Hartland wrote: The Areca cards I can recommend. Highpoint 1820a is surprisingly good for its price and the later cards have better performance still apparently. N.B. Use the min stripe size when creating the array for max performance with this card under FreeBSD. I was more thinking along the lines of a HighPoint 2720, but perhaps a 1820 would also do fine. What device driver would one use with that. [Ahhh, 'man -k highpoint' is your friend] Now what I liked about the 3ware stuff was that there are tools to work the raid from within FreeBSD. So that would require the newers ones... But the hardware list is only showing the 2320 and 2322 with a rr232x(4) driver. Which sort of makes me wonder for all the other stuff and their drivers. The motherboard has both PCI-X and PCI-E so that should not be a connector problem. Now which bus is faster: 64Bit PCI-X at 133 Mhz, or a PCI-E 16x? The x16 PCI-E has considerably faster theoretical speed than 133 PCI-X (appx. 4GBs vs. 1GBs). However, the RAID controllers that I've seen are at most x8 so they are only capable of transfer rates half that fast (2GBs). Personally, I would go with PCI-E since in some performance tests I did with Areca cards last year (both PCI-E and PCI-X) there appeared to be a slight performance advantage to the PCI-E cards (sorry, I don't recall any of the specifics anymore, so please take that for what it's worth). I agree. PCIe 8x is a faster bus and it's typically connected directly to the MCH (north bridge) unlike PCI-X which is stuck on the ICH (south bridge). Also the 2GB/s that was quoted for PCIe 8x is it's one-way data rate after calculating in overhead. It's a dual simplex interface meaning it has one path to send data and another path to receive data. Imagine a simple two lane road. I take that back. For PCIe 8x imagine a divided highway with 8 lanes in each direction. The speed limit for each lane of traffic is 250MegaBytes/sec. So if you can move 8 semi-trucks filled with data in parallel your effective data rate is 2GigaBytes/sec. simple eh? :-) -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RocketRAID 2224
On 8/18/06, Nikolas Britton [EMAIL PROTECTED] wrote: On 8/18/06, Dave Kingsley [EMAIL PROTECTED] wrote: I am attemping to use a RocketRAID 2224 8 channel card to set up a storage server. The server board is an Intel SE7230NH1-E with a P4-D 2.8GHz, 2GB RAM. FreeBSD doesn't see it at all. I've noticed that the kernel config has options built in for the RocketRAID 182x. Are there options I can add for the newer card? If so, will they work with FreeBSD 6.1 so that I can reconfigure for it rather than 6.0 that's running now? Basically we're trying to set up backups to disk with a RAID of about 4.5TB. FreeBSD has native support for the following: $whatis highpoint hptmv(4) - HighPoint RocketRAID 182x device driver rr232x(4)- HighPoint RocketRAID 232x device driver You have have a 2224 so no. You will need to use HighPoint's FreeBSD drivers. You can download everything from here: http://www.highpoint-tech.com/USA/bios_rr2224.htm While your at it update your cards BIOS (if needed) and grab a copy of CLI FreeBSD v2.2, the RAID management utility. After you download the driver and un-tar it use the rr222x-bsd-6.img file... It's designed for FreeBSD 6.0 but works perfect on FreeBSD 6.1... Follow the steps below, remember to change /dev/md0 if needed: This installs the device driver: # mdconfig -a -t vnode -f rr222x-bsd-6.img # mount /dev/md0 /mnt # cp /mnt/hptmv6-6.0.ko /boot/modules/ # echo 'hptmv6_load=yes' /boot/loader.conf This installs the console management utility: # pkg_add hptraidconf-2.2.tbz # pkg_add hotsvr-3.12.tbz That's it, after you reboot everything will be working. You should print out the pdf manual for the console management utility. If you need more help just ask... I myself have an HPT 2220. Sorry for the errors, here are the corrected steps: This installs the device driver: # mdconfig -a -t vnode -f rr222x-bsd-6.img # mount /dev/md0 /mnt # cp /mnt/hptmv6-6.0.ko /boot/modules/hptmv6.ko # echo 'hptmv6_load=YES' /boot/loader.conf This installs the console management utility: # pkg_add hptsvr-3.12.tbz # pkg_add hptraidconf-2.2.tbz -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: diffs to add newer Intel ATA and ICHSMB IDs
On 6/1/06, Jack Vogel [EMAIL PROTECTED] wrote:
I occasionally run into issues that newer PCI device IDs are
not yet supported, these in particular are on a new box
I am working on. Can someone see that these changes
get integrated please :)
Cheers,
Jack
--- dev/ata/ata-chipset.orig.c Fri Jun 2 05:39:18 2006
+++ dev/ata/ata-chipset.c Fri Jun 2 05:38:34 2006
@@ -1595,6 +1595,8 @@
{ ATA_I82801GB_R1, 0, AHCI, 0x00, ATA_SA300, ICH7 },
{ ATA_I82801GB_M, 0, AHCI, 0x00, ATA_SA300, ICH7 },
{ ATA_I82801GB_AH, 0, AHCI, 0x00, ATA_SA300, ICH7 },
+ { ATA_I631xESB,0,0, 0x00, ATA_UDMA5, 631xESB },
+ { ATA_I631xESB_S1, 0, AHCI, 0x00, ATA_SA300, 631xESB },
{ ATA_I31244, 0,0, 0x00, ATA_SA150, 31244 },
{ 0, 0, 0, 0, 0, 0}};
char buffer[64];
--- dev/ata/ata-pci.orig.h Fri Jun 2 05:30:03 2006
+++ dev/ata/ata-pci.h Fri Jun 2 05:30:47 2006
@@ -148,6 +148,8 @@
#define ATA_I82801FB_S1 0x26518086
#define ATA_I82801FB_R1 0x26528086
#define ATA_I82801FB_M 0x26538086
+#define ATA_I631xESB_S1 0x26808086
+#define ATA_I631xESB0x269e8086
#define ATA_I82801GB0x27df8086
#define ATA_I82801GB_S1 0x27c08086
#define ATA_I82801GB_R1 0x27c38086
--- dev/ichsmb/ichsmb_pci.orig.cFri Jun 2 05:17:21 2006
+++ dev/ichsmb/ichsmb_pci.c Fri Jun 2 05:20:04 2006
@@ -74,6 +74,7 @@
#define ID_82801DC 0x24C38086
#define ID_82801EB 0x24D38086
#define ID_6300ESB 0x25a48086
+#define ID_631xESB 0x269b8086
#define PCIS_SERIALBUS_SMBUS_PROGIF0x00
@@ -145,6 +146,9 @@
break;
case ID_6300ESB:
device_set_desc(dev, Intel 6300ESB (ICH) SMBus controller);
+ break;
+ case ID_631xESB:
+ device_set_desc(dev, Intel 631xESB (ESB2) SMBus controller);
break;
default:
if (pci_get_class(dev) == PCIC_SERIALBUS
___
Did this ever get commited? I have a Intel 5000p MCH + 6321ESB ICH and
onboard SATA is basically completely broken. If you hookup more then
one SATA drive it will hang the system at boot... I've played with
every setting in the BIOS... I'm Running 6-STABLE 20060818. Would
this fix my problems?
--
BSD Podcasts @:
http://bsdtalk.blogspot.com/
http://freebsdforall.blogspot.com/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: diffs to add newer Intel ATA and ICHSMB IDs
On 8/20/06, Jack Vogel [EMAIL PROTECTED] wrote:
On 8/20/06, Nikolas Britton [EMAIL PROTECTED] wrote:
On 6/1/06, Jack Vogel [EMAIL PROTECTED] wrote:
I occasionally run into issues that newer PCI device IDs are
not yet supported, these in particular are on a new box
I am working on. Can someone see that these changes
get integrated please :)
Cheers,
Jack
--- dev/ata/ata-chipset.orig.c Fri Jun 2 05:39:18 2006
+++ dev/ata/ata-chipset.c Fri Jun 2 05:38:34 2006
@@ -1595,6 +1595,8 @@
{ ATA_I82801GB_R1, 0, AHCI, 0x00, ATA_SA300, ICH7 },
{ ATA_I82801GB_M, 0, AHCI, 0x00, ATA_SA300, ICH7 },
{ ATA_I82801GB_AH, 0, AHCI, 0x00, ATA_SA300, ICH7 },
+ { ATA_I631xESB,0,0, 0x00, ATA_UDMA5, 631xESB },
+ { ATA_I631xESB_S1, 0, AHCI, 0x00, ATA_SA300, 631xESB },
{ ATA_I31244, 0,0, 0x00, ATA_SA150, 31244 },
{ 0, 0, 0, 0, 0, 0}};
char buffer[64];
--- dev/ata/ata-pci.orig.h Fri Jun 2 05:30:03 2006
+++ dev/ata/ata-pci.h Fri Jun 2 05:30:47 2006
@@ -148,6 +148,8 @@
#define ATA_I82801FB_S1 0x26518086
#define ATA_I82801FB_R1 0x26528086
#define ATA_I82801FB_M 0x26538086
+#define ATA_I631xESB_S1 0x26808086
+#define ATA_I631xESB0x269e8086
#define ATA_I82801GB0x27df8086
#define ATA_I82801GB_S1 0x27c08086
#define ATA_I82801GB_R1 0x27c38086
--- dev/ichsmb/ichsmb_pci.orig.cFri Jun 2 05:17:21 2006
+++ dev/ichsmb/ichsmb_pci.c Fri Jun 2 05:20:04 2006
@@ -74,6 +74,7 @@
#define ID_82801DC 0x24C38086
#define ID_82801EB 0x24D38086
#define ID_6300ESB 0x25a48086
+#define ID_631xESB 0x269b8086
#define PCIS_SERIALBUS_SMBUS_PROGIF0x00
@@ -145,6 +146,9 @@
break;
case ID_6300ESB:
device_set_desc(dev, Intel 6300ESB (ICH) SMBus
controller);
+ break;
+ case ID_631xESB:
+ device_set_desc(dev, Intel 631xESB (ESB2) SMBus
controller);
break;
default:
if (pci_get_class(dev) == PCIC_SERIALBUS
___
Did this ever get commited? I have a Intel 5000p MCH + 6321ESB ICH and
onboard SATA is basically completely broken. If you hookup more then
one SATA drive it will hang the system at boot... I've played with
every setting in the BIOS... I'm Running 6-STABLE 20060818. Would
this fix my problems?
As far as I know this hasnt been committed, I've not looked.
Will it fix your problem, hmm, depends on if its one of the devices
I'm adding, is it?
Can you not patch yourself and test it?
Not exactly. I'm putting this new server in production as we speak! I
was using an IDE drive in the testing phase, I assumed the SATA drives
I planned to transfer to this new server from another server would
just work even if only in legacy mode. dead wrong! Commitments have
already been made so I can't stop. Luckily plan B worked so I just
disabled onboard SATA. Thank for the info...
--
BSD Podcasts @:
http://bsdtalk.blogspot.com/
http://freebsdforall.blogspot.com/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RocketRAID 2224
On 8/18/06, Dave Kingsley [EMAIL PROTECTED] wrote: I am attemping to use a RocketRAID 2224 8 channel card to set up a storage server. The server board is an Intel SE7230NH1-E with a P4-D 2.8GHz, 2GB RAM. FreeBSD doesn't see it at all. I've noticed that the kernel config has options built in for the RocketRAID 182x. Are there options I can add for the newer card? If so, will they work with FreeBSD 6.1 so that I can reconfigure for it rather than 6.0 that's running now? Basically we're trying to set up backups to disk with a RAID of about 4.5TB. FreeBSD has native support for the following: $whatis highpoint hptmv(4) - HighPoint RocketRAID 182x device driver rr232x(4)- HighPoint RocketRAID 232x device driver You have have a 2224 so no. You will need to use HighPoint's FreeBSD drivers. You can download everything from here: http://www.highpoint-tech.com/USA/bios_rr2224.htm While your at it update your cards BIOS (if needed) and grab a copy of CLI FreeBSD v2.2, the RAID management utility. After you download the driver and un-tar it use the rr222x-bsd-6.img file... It's designed for FreeBSD 6.0 but works perfect on FreeBSD 6.1... Follow the steps below, remember to change /dev/md0 if needed: This installs the device driver: # mdconfig -a -t vnode -f rr222x-bsd-6.img # mount /dev/md0 /mnt # cp /mnt/hptmv6-6.0.ko /boot/modules/ # echo 'hptmv6_load=yes' /boot/loader.conf This installs the console management utility: # pkg_add hptraidconf-2.2.tbz # pkg_add hotsvr-3.12.tbz That's it, after you reboot everything will be working. You should print out the pdf manual for the console management utility. If you need more help just ask... I myself have an HPT 2220. -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
gzip is faster with -O3
dd if=/dev/random of=testfile bs=1m count=5000 gzip compiled with -O3: # date ; nice -10 ./gzip -c9 testfile testfile.gz ; date Wed Aug 9 08:01:21 CDT 2006 Wed Aug 9 08:09:06 CDT 2006 465 Seconds. gzip compiled with -O2: # date ; nice -10 ./gzip -c9 testfile testfile.gz ; date Wed Aug 9 08:19:14 CDT 2006 Wed Aug 9 08:27:06 CDT 2006 472 Seconds. 7 second difference, it's not much but I still wanted to share it with the group. -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gzip is faster with -O3
On 8/9/06, Matthias Andree [EMAIL PROTECTED] wrote: 1. gzip isn't usually used to compress incompressible data. 2. use time to figure out how much CPU time it actually burns. 5 GB are somewhat I/O bound, but gcc options don't help with that, so CPU time is better than wallclock time. dd if=/dev/zero of=testfile bs=1m count=5000 gzip comiled with -O3 # time nice -10 ./gzip -c9 testfile /dev/null 73.187u 8.682s 2:08.41 63.7%70+617k 40161+0io 0pf+0w gzip compiled with -O2 # time nice -10 ./gzip -c9 testfile /dev/null 61.183u 8.468s 2:00.14 57.9%58+609k 40162+0io 0pf+0w Now... what do all of those numbers mean, I've never used time before... thanks for the tip btw? -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Professional sound card
On 8/7/06, Marco Pirovano [EMAIL PROTECTED] wrote: Hello, I'm looking for a professional sound card available under FreeBSD-stable. Any suggestions ? Thank you very much. Read the first two and the fourth links here if you want a Envy24 based card: http://groups.google.com/groups/search?ie=UTF-8oe=UTF-8q=group%3A%2A.freebsd.%2A+%22Status+of+VIA+Envy24%22qt_s=Search -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Xen / FreeBSD 6.2
Will FreeBSD 6.2 support Xen dom0? I have a new Xeon system with VT and I'm chomping at the bit here, considering -CURRENT for a production server... or worse... running Linux to get my fix. -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Xen / FreeBSD 6.2
Can't. NetBSD doesn't have the arcmsr(4) driver... My choice is limited to FreeBSD, Solaris, or Linux. On 8/6/06, Luke [EMAIL PROTECTED] wrote: Perhaps you should consider NetBSD if FreeBSD will not have support for it? On Sun, 6 Aug 2006, Nikolas Britton wrote: Will FreeBSD 6.2 support Xen dom0? I have a new Xeon system with VT and I'm chomping at the bit here, considering -CURRENT for a production server... or worse... running Linux to get my fix. -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Xen / FreeBSD 6.2
On 8/6/06, Kip Macy [EMAIL PROTECTED] wrote: I haven't been keeping the xen port up to date. There is an SoC student who is making some progress with it but he is looking more at what is required to make the installer work with it. Making 6.2 work would not be that difficult, but no one is currently working on it. How difficult are we talking? Could someone with extremely limited C programming experience do it? On Sun, 6 Aug 2006, Nikolas Britton wrote: Will FreeBSD 6.2 support Xen dom0? I have a new Xeon system with VT and I'm chomping at the bit here, considering -CURRENT for a production server... or worse... running Linux to get my fix. -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em(4) update for 6-STABLE
On 8/3/06, Gleb Smirnoff [EMAIL PROTECTED] wrote: Colleagues, here is a patch that merges HEAD em(4) driver to RELENG_6. First, it significantly improves perfromance of the driver under high pps load. Second, it adds support for few new chips. You need to update your system to fresh RELENG_6. The driver will not compile on 6.1-RELEASE. Then you need to run the following sequence: cd /usr/src/sys/dev/em fetch http://people.freebsd.org/~glebius/em-6.0.5.RELENG_6.patch.gz gunzip em-6.0.5.RELENG_6.patch.gz patch em-6.0.5.RELENG_6.patch and then rebuild your kernel and reboot. 1 out of 73 hunks failed--saving rejects to if_em_hw.h.rej raidbackup1# more if_em_hw.h.rej I'd send to .rej file but Opera9/Gmail is plotting against me. It's seems to just be the Intel copyright notice that that failed ti merge... I'll try sending it later. -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GIANT in arcmsr(4)
On 7/31/06, Mike Tancsa [EMAIL PROTECTED] wrote: At 07:13 AM 30/07/2006, Nikolas Britton wrote: On 7/29/06, Nikolas Britton [EMAIL PROTECTED] wrote: Anyone know why the giant is in arcmsr(4) or how to kill him? I did some work on the arcmsr(4) driver: http://www.freebsd.org/cgi/query-pr.cgi?pr=101045 Is not the driver from the Areca site just plugin compatible ? I havent updated my Areca boxes in a bit, but I recall just dropping the source code in place of what was there and recompiling. I was also told by Areca to make sure I had the latest firmware at the time too. I don't know but I do know it won't compile if you just dropped it in, I had to fix a few syntax errors: diff arcmsr.h.1200012 arcmsr.h.freebsd.new 36a37 ** $FreeBSD$ 112c113 #define dma_addr_hi32(addr) (u_int32_t) ((addr16)16 --- #define dma_addr_hi32(addr) (u_int32_t) ((addr16)16) 518,519c519,520 u_int32_t num_resets u_int32_t num_aborts --- u_int32_t num_resets; u_int32_t num_aborts; 523c524 u_int32_t firm_ide_channels; /*4,16-19* --- u_int32_t firm_ide_channels; /*4,16-19*/ I asked the Areca people what their plans were for the driver on the website and they said they submitted the driver to be merged into the tree, but either didnt email the right people, or no one had time to do the merge/import. Perhaps Scott Long knows ? ---Mike CC'd Erich Chen, the person who made the driver. -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GIANT in arcmsr(4)
On 7/31/06, erich [EMAIL PROTECTED] wrote: Dear Nikolas Britton, Sorry I had new arcmsr driver version 1.20.00.13 for FreeBSD i386/amd64/ppc plateform. This version add ARECA new generation RAID adapters ( SATA / SAS ) into arcmsr. Its xfer rate more than 800MB/sec. I need more time to test arcmsr on PowerMac G5 even SPARC machine in my Lab. Any comments and opinion with this driver will win acceptance. Best Regards Erich Chen Do you have a link to download v1.20.00.13? and have you MFC'd the changes we made back into your new code?: Here are the changes we made to 1.20.00.02: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/arcmsr/arcmsr.c Could I also suggest sed 's/.$//' to convert those pesky CR+LF Windows files to UNIX format. -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GIANT in arcmsr(4)
On 7/29/06, Nikolas Britton [EMAIL PROTECTED] wrote: Anyone know why the giant is in arcmsr(4) or how to kill him? I did some work on the arcmsr(4) driver: http://www.freebsd.org/cgi/query-pr.cgi?pr=101045 -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
GIANT in arcmsr(4)
Anyone know why the giant is in arcmsr(4) or how to kill him? -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Monitoring temperature with acpi (sysctls)
On 7/26/06, David Duchscher [EMAIL PROTECTED] wrote: On Jul 26, 2006, at 11:09 AM, Bruno Ducrot wrote: On Tue, Jul 25, 2006 at 11:51:25AM -0400, Mike Jakubik wrote: I need to be able to get the cpu and fan information from my motherboard, however none of the monitoring utilities in the ports seems to support my motherboard (Supermicro PDSMi, Intel E7230 (Mukilteo) Chipset). On my older VIA based motherboards and some Nvidia, i can get this information using ACPI and the hw.acpi.thermal sysctl. This however is not available on this motherboard. Would this be a shortcoming of the motherboards ACPI implementation, or a lack of support by freebsd? Does this one support IPMI? Yes, the Supermicro PDSMi supports the IPMI 2.0 module and I can confirm that it works with the IPMI ported driver from current on 6.1. The module is optional so you will have to purchase one for the system, around 0. You will also need the latest BIOS loaded on the motherboard for it to work. http://www.supermicro.com/products/accessories/addon/AOC-IPMI20-E.cfm What about their other IPMI 2.0 cards: http://www.supermicro.com/products/accessories/addon/SIM.cfm Specifically the AOC-SIMLP? and what ported IPMI driver are we talking about? Also does anyone have an IPMI primer, I've never used it before? -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Xen dom0 support?
Does FreeBSD support Xen 3 dom0 yet??? What's the current status of domU support? Does Net/Open BSD support Xen 3 dom0? -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Xen dom0 support?
On 7/22/06, Nikolas Britton [EMAIL PROTECTED] wrote: Does FreeBSD support Xen 3 dom0 yet??? What's the current status of domU support? Does Net/Open BSD support Xen 3 dom0? NetBSD has Xen 3 dom0 support: http://mail-index.netbsd.org/port-xen/2006/07/03/.html -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Gigabit ethernet very slow.
What's up with my computer, it's only getting 30MB/s? hostB: nc -4kl port /dev/null hostA: nc host port /dev/zero hostB: Athlon64 3000, Asus A8R-MVP, FreeBSD 6.1/amd64): $ sysctl -a net.inet.tcp|grep space net.inet.tcp.sendspace: 32768 net.inet.tcp.recvspace: 131072 sk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 6500 options=8VLAN_MTU inet6 fe80::215:f2ff:fed9:ae2a%sk0 prefixlen 64 scopeid 0x2 inet 192.168.1.242 netmask 0xff00 broadcast 192.168.1.255 ether 00:15:f2:d9:ae:2a media: Ethernet 1000baseTX full-duplex (1000baseTX full-duplex,flag0,flag1) status: active top: last pid: 730; load averages: 0.53, 0.41, 0.41 26 processes: 1 running, 25 sleeping CPU states: 2.6% user, 0.0% nice, 12.4% system, 25.9% interrupt, 59.0% idle Mem: 11M Active, 7832K Inact, 23M Wired, 10M Buf, 189M Free Swap: 483M Total, 483M Free PID USERNAME THR PRI NICE SIZERES STATETIME WCPU COMMAND 557 root1 980 3964K 956K select 7:48 9.57% nc $ vmstat -n 0 5 procs memory page faults cpu r b w avmfre flt re pi po fr sr in sy cs us sy id 1 0 0 31368 194048 15 0 0 0 13 0 12705 110013 21101 1 38 61 1 0 0 31368 1940480 0 0 0 0 0 9638 84515 14842 1 28 71 0 0 0 31368 1940480 0 0 0 0 0 10228 89549 15756 1 31 68 0 0 0 31368 1940480 0 0 0 0 0 13055 114963 20048 1 38 60 0 0 0 31368 1940480 0 0 0 0 0 9325 81653 14384 0 28 72 --- hostA: P4 3GHz Prescott, Intel SE7210TP1E, FreeBSD 6.1/i386): $ sysctl -a net.inet.tcp|grep space net.inet.tcp.sendspace: 65536 net.inet.tcp.recvspace: 65536 em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 6500 options=bRXCSUM,TXCSUM,VLAN_MTU inet6 fe80::204:23ff:feba:3870%em0 prefixlen 64 scopeid 0x1 inet 192.168.1.2 netmask 0xff00 broadcast 192.168.1.255 ether 00:04:23:ba:38:70 media: Ethernet 1000baseTX full-duplex status: active top: last pid: 1190; load averages: 0.10, 0.21, 0.28 50 processes: 1 running, 49 sleeping CPU states: 0.7% user, 0.0% nice, 11.6% system, 9.0% interrupt, 78.7% idle Mem: 72M Active, 222M Inact, 147M Wired, 12K Cache, 111M Buf, 552M Free Swap: 6144M Total, 6144M Free PID USERNAME THR PRI NICE SIZERES STATETIME WCPU COMMAND 997 root1 40 1528K 720K sbwait 1:37 15.82% nc $ vmstat -n 0 5 procs memory page faults cpu r b w avmfre flt re pi po fr sr in sy cs us sy id 2 0 0 169608 563404 36 0 0 0 28 0 9149 109489 14087 3 34 64 0 0 0 169608 5634049 0 0 0 9 0 8224 92285 11696 2 24 74 1 0 0 169608 563404 13 0 0 0 13 0 8818 99341 12541 2 28 70 0 0 0 169608 5634049 0 0 0 9 0 8645 97585 12303 2 28 70 0 0 0 169608 563404 13 0 0 0 13 0 7610 85517 10830 1 26 73 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Gigabit ethernet very slow.
On 6/25/06, Sean Bryant [EMAIL PROTECTED] wrote: /dev/zero not exactly the best way to test sending data across the network. Especially since you'll be reading a 8k chunks. I could be wrong, strong possibility that I am. I only got 408mb when doing a /dev/zero test. I've managed to saturate though. Using other software that I wrote. On 6/25/06, Nikolas Britton [EMAIL PROTECTED] wrote: What's up with my computer, it's only getting 30MB/s? hostB: nc -4kl port /dev/null hostA: nc host port /dev/zero 408MByte/s or 408Mbit/s and what measuring stick are you using? I'm trying to rule in/out problems with the disks, I'm only getting ~25MB/s on a 6 disk RAID0 over the network... would it be better to setup an memory backed disk, md(4) , to read from? -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Gigabit ethernet very slow.
On 6/25/06, Nikolas Britton [EMAIL PROTECTED] wrote: On 6/25/06, Sean Bryant [EMAIL PROTECTED] wrote: /dev/zero not exactly the best way to test sending data across the network. Especially since you'll be reading a 8k chunks. I could be wrong, strong possibility that I am. I only got 408mb when doing a /dev/zero test. I've managed to saturate though. Using other software that I wrote. On 6/25/06, Nikolas Britton [EMAIL PROTECTED] wrote: What's up with my computer, it's only getting 30MB/s? hostB: nc -4kl port /dev/null hostA: nc host port /dev/zero 408MByte/s or 408Mbit/s and what measuring stick are you using? I'm trying to rule in/out problems with the disks, I'm only getting ~25MB/s on a 6 disk RAID0 over the network... would it be better to setup an memory backed disk, md(4) , to read from? Now I'm getting 523.2Mbit/s (65.4MB/s) with netcat, I wiped out the FreeBSD 6.1/amd64 install with FreeBSD 6.1/i386... and... After a kernel rebuild (recompiled nc too): CPUTYPE?=athlon-mp CFLAGS+= -mtune=athlon64 COPTFLAGS+= -mtune=athlon64 I'm up to 607.2Mbit/s (75.9MB/s). What else can I do to get that number higher, and how can I get interrupts lower? Before recompile: load averages: 0.94, 0.91, 0.66 CPU states: 2.6% user, 0.0% nice, 21.5% system, 64.6% interrupt, 11.3% idle --- After recompile: load averages: 0.99, 0.96, 0.76 CPU states: 3.0% user, 0.0% nice, 33.7% system, 58.2% interrupt, 5.1% idle -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bug in systat: ifstat?
Now it shows: 13228401022664.000 b (12TB)... Which means I transferred 3.226TB in 330 minutes... or 170.84MB/s, which is not possible using a gigabit Ethernet link to say the least. On 6/24/06, Nikolas Britton [EMAIL PROTECTED] wrote: Look at the Totals column (gmail may wrap it): /0 /1 /2 /3 /4 /5 /6 /7 /8 /9 /10 Load Average Interface Traffic PeakTotal lo0 in 0.000 KB/s 0.000 KB/s9.446 KB out 0.000 KB/s 0.000 KB/s9.446 KB sk0 in 29.485 MB/s 34.525 MB/s 9681495918456.000 b out 753.799 KB/s889.657 KB/s 29.710 GB -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Effects of changing tar's -b option.
Test Setup: 250 50MB files (13068252KB) dd if=/dev/random of=testfile bs=1m count=50 Ethernet mtu=6500 Transferred files were wiped after every test with 'rm -r *'. Test: hostB: nc -4l port | tar xpbf n - hostA: date; tar cbf n - . | nc hostB port; date Test Results: seconds = n 645sec. = 1024 670sec. = 512 546sec. = 256 503sec. = 128 500sec. = 128 (control) 515sec. = 96 508sec. = 64 501sec. = 20 (default) Conclusions: Make your own. -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xorg build failed
On 6/2/06, Manfred Lotz [EMAIL PROTECTED] wrote: Hi there, Trying to build xorg-server 6.9.3 I get Where did you get Xorg 6.9.3 from? -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PCI Radeon 7000/VE (RV100) on AMD64
On 5/3/06, Wilde, Donald [EMAIL PROTECTED] wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nikolas Britton Sent: Tuesday, May 02, 2006 2:46 PM To: Alastair G. Hogge Cc: freebsd-stable@freebsd.org Subject: Re: PCI Radeon 7000/VE (RV100) on AMD64 On 3/27/06, Alastair G. Hogge [EMAIL PROTECTED] wrote: G'day Having some problem with Xorg-6.9.0 and the radeon or ati driver on mad64 system. X seems to look up at a black screen after setting the resolution and then resets the computer. I have drm and radeon defined in my kernel config and I've also added the appropriate lines to xorg.conf This may or may not be relavent... but I have a triple-head setup using three Radeon cards; 1 agp based 8500LE and 2 pci based 7000/VE's. I've never had DRI / X working... The problem(s) you're having sounds like the problems I was having... Comment out 'Load dri' in xorg.conf and try it again. Nikolas, Alistair - There is still active work going on in the DRI/DRM section of X.org for ATI/Radeon. There were some partial fixes posted to FreeDesktop.org's bugzilla, but they require X 6.9.0-CURRENT. Nikolas' suggestion (commenting Load DRI) does work, but I was able to get the DRI to function (with 3D OpenGL) using CURRENT X (as of two months ago; it may be even better now.) I can't seem to find any devel snapshots on the xorg website?... and I'm already running 6.9.0 (It's still broken, but fails more gracefully.): xorg-clients-6.9.0_2 xorg-libraries-6.9.0 xorg-server-6.9.0_1 dri-6.4.1,2 gle-3.0.3_2 -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PCI Radeon 7000/VE (RV100) on AMD64
On 3/27/06, Alastair G. Hogge [EMAIL PROTECTED] wrote: G'day Having some problem with Xorg-6.9.0 and the radeon or ati driver on mad64 system. X seems to look up at a black screen after setting the resolution and then resets the computer. I have drm and radeon defined in my kernel config and I've also added the appropriate lines to xorg.conf This may or may not be relavent... but I have a triple-head setup using three Radeon cards; 1 agp based 8500LE and 2 pci based 7000/VE's. I've never had DRI / X working... The problem(s) you're having sounds like the problems I was having... Comment out 'Load dri' in xorg.conf and try it again. -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
ICH7 SATA RAID Broken, Was (Re: Timescale for 6.1-RELEASE...)
On 4/12/06, Ted Mittelstaedt [EMAIL PROTECTED] wrote: -Original Message- From: Ted Mittelstaedt [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 11, 2006 6:04 PM To: Nikolas Britton Cc: Harrison Peter CSA BIRKENHEAD; freebsd-questions@freebsd.org Subject: RE: Timescale for 6.1-RELEASE... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Nikolas Britton Sent: Tuesday, April 11, 2006 1:25 PM To: Ted Mittelstaedt Cc: Harrison Peter CSA BIRKENHEAD; freebsd-questions@freebsd.org Subject: Re: Timescale for 6.1-RELEASE... I think the ICH7 sata problem has already been fixed, check the logs here: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/ata/ if not jump onto the stable mailing list and start waving your hands. I'm doing a make release on today's cvs as we speak, I'll see tomorrow if it recognizes the disks. Nikolas, Just an update, no the ICH7R problem has not been fixed. OpenSUSE recognizes the array, though. Send email to Søren Schmidt [EMAIL PROTECTED] and/or post this on the stable mailing list, their is nothing I can do personally that will fix it for you. You could start hacking away at the problem if you know some C, digging around in /usr/src/sys/dev/ata/ If you're just now joining us this is about: http://www.freebsd.org/cgi/query-pr.cgi?pr=95184 P.S. I'm cc'ing this to freebsd-stable and soren, removed freebsd-questions -- BSD Podcasts @ http://bsdtalk.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disappointed
On 4/6/06, [LoN]Kamikaze [EMAIL PROTECTED] wrote: Alexey Karagodov wrote: hi. i think, this unstablity happaning just because developers trying to make two systems at one time, one is 6.0 and another 7.0 current and they supporting old version, lower then 6.0 i want to ask developers, why you developing new system, 7.0, if you don't finish old, 6.0 ?! finish 6.0, make it work, and upgrade it to 7.0 and to 8.0 and to 9.0 and so on ... what so new and revolutionary in 7.0 in comparison with 6.0 ?! to use your system i must be a DEVELOPER, but i don't have so much time! i don't want to develope! i want to use, i want to help you with some advise ( e.g. what feature to add, what feature to change etc), i can and i want to share some of my hardware to feet your needs, make a mirror, make a test server/workstation/notebook/PDA etc. i'm not an freebsd developer. i'm just admin and a user. your system is most greatest i ever seen. another wonderful system is SOLARIS. but your's is so unstable ... All this is described in many places. It all comes down to this: if you don't want to be a developer, JUST USE THE RELEASE BRANCH. That means Releng_6_0 for now. Stable only means compatible to previous versions of the same branch. Not that the system is stable. Maybe they/we should change the name of -STABLE to -APISTABLE or -ABISTABLE. I've always had to go out of my way to explain what -STABLE is to newbies that assumed it was stable changing this name should keep them off the developer branches. oh and we should change -CURRENT to -THISWILLBREAKYOURSYSTEM for all those Gentoo Linux type people. :-) 1 bad experience is equal to 10 good ones. -- BSD Podcasts @ http://bsdtalk.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 Release day
On 4/6/06, Norbert Augenstein [EMAIL PROTECTED] wrote: On Thu, Apr 06, 2006 at 01:41:23PM +0200, Erik Trulsson wrote: On Thu, Apr 06, 2006 at 12:20:09PM +0300, SoHo.NET wrote: Dear Sir, Can you notify me with date of FreeBSD 6.1 RELEASE? It have to be released in 1 or 2 weeks after Announcement 20 march 2006 As I can see here http://www.freebsd.org/releases/6.1R/schedule.html I don't think the final release date has been decided yet. As you note it was originally planned to be released on March 20, but the schedule has slipped quite a bit (just as it did for every previous release too.) Personally I would *guess* that it will be released about 1-2 weeks from now, but that is only my personal guess and I do not have any special inside information on this matter. 6.1 is branched, but i would like to see some ReleaseCandidates first. Really?... It, releng, said the cut for the 6.1 branch was yesterday... can you confirm this, have you cvsup'd to RELENG_6_1? -- BSD Podcasts @ http://bsdtalk.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Pros and Cons of amd64 (versus i386).
Hello all, I will be getting my very first 64-bit x86 system tomorrow and I don't know anything about the platform at the software level. The last time I touched an AMD based system was in the socket 7 days. HELP!, what do I do with the extra 32-bits of CPU goodness? :-) $200 bucks got me a Athlon 64 3000+ Venice and a ASUS A8V Motherboard. I'll be converting my Pentium 4 2.26GHz desktop system that has FreeBSD 6.1-PRERELEASE i386 on it, gcc is currently set to build with -march=pentium2 and -mtune=pentium4 via make.conf * How do I buildworld to amd64, and should I? * What are the best gcc -mtune / -march flags to use? * What do all the other -m flags do? * What -march flags won't run on the AMD platform, will CPUTYPE=p2 work on AMD? * Can I still build packages for other i386 (non 64-bit) systems? * Where can I find more info about FreeBSD on AMD? * What did I forget to add here? Thanks guys. -- BSD Podcasts @ http://bsdtalk.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Is mount_smbfs broken in 6.1-PRERELEASE?
Anyone know if mount_smbfs is broken in 6.1, I'm trying to run this: mount_smbfs -I 192.168.1.2 //[EMAIL PROTECTED]/music2 /mnt/network/music/ And then it asks for my password, I type it in, and then I get this error: mount_smbfs: unable to open connection: syserr = Authentication error I've had this same problem on another 6.1 box too... I can run this same command on a 6.0-RELEASE box, right next to the 6.1 box, on the same network etc. without problems. What gives? Did I forget to setup something on the new 6.1 boxes or is mount_smbfs broken, IIRC I didn't do anything special to get mount_smbfs working on the 6.0 box? File Server: samba-3.0.21b,1 uname -a: FreeBSD puddlejumper.local 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #0: Tue Mar 14 12:15:56 CST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SE7210TP1E i386 Workstation: uname -a: FreeBSD cake.local 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #0: Tue Mar 28 17:47:28 CST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CAKE i386 The box that mount_smbfs works on: uname -a: FreeBSD musicbox1.local 6.0-STABLE FreeBSD 6.0-STABLE #0: Sat Jan 7 21:57:14 CST 2006 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/GENERIC i386 -- BSD Podcasts @ http://bsdtalk.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Is mount_smbfs broken in 6.1-PRERELEASE?
On 3/30/06, Gavin Atkinson [EMAIL PROTECTED] wrote: On Thu, 30 Mar 2006, Nikolas Britton wrote: Anyone know if mount_smbfs is broken in 6.1, I'm trying to run this: mount_smbfs -I 192.168.1.2 //[EMAIL PROTECTED]/music2 /mnt/network/music/ And then it asks for my password, I type it in, and then I get this error: mount_smbfs: unable to open connection: syserr = Authentication error I've had this same problem on another 6.1 box too... I can run this same command on a 6.0-RELEASE box, right next to the 6.1 box, on the same network etc. without problems. What gives? Did I forget to setup something on the new 6.1 boxes or is mount_smbfs broken, IIRC I didn't do anything special to get mount_smbfs working on the 6.0 box? This was accidentally broken as part of a load of kernel clean-ups. [EMAIL PROTECTED] (cc'd) committed a fix to -CURRENT Sun Mar 5 22:52:16 2006 ( http://docs.FreeBSD.org/cgi/mid.cgi?200603052252.k25MqHpb094838 ) with an MFC of 5 days, but it doesn't seem to have been merged yet. It may have been turned down by re@, or it may have just been forgotton about. (I hope it's the latter, as I think it's an important fix to get into 6.1-R). Hopefully yar@ will be able to MFC this. Gavin Thanks for the info! and I've got mount_smbfs working now, Scott Robbins suggested in a previous reply to add 'options NETSMBCRYPTO' to the kernel for a temp work around... This did the trick. I hope they get this MFC'd for 6.1-RELEASE. -- BSD Podcasts @ http://bsdtalk.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
-march=pentium2 + -mtune=pentium4 faster then -march=pentium4?
Why does GCC produce faster code using -march=pentium2 -mtune=pentium4 on a Pentium 4 chip versus plain -march=pentium4? Try it... CPUTYPE=pentium2 CFLAGS+= -mtune=pentium4 COPTFLAGS+= -mtune=pentium4 -- BSD Podcasts @ http://bsdtalk.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: -march=pentium2 + -mtune=pentium4 faster then -march=pentium4?
On 3/27/06, Kris Kennaway [EMAIL PROTECTED] wrote: On Mon, Mar 27, 2006 at 01:05:13PM -0600, Nikolas Britton wrote: Why does GCC produce faster code using -march=pentium2 -mtune=pentium4 on a Pentium 4 chip versus plain -march=pentium4? Try it... CPUTYPE=pentium2 CFLAGS+= -mtune=pentium4 COPTFLAGS+= -mtune=pentium4 Talk to the gcc developers (and provide benchmarks). What would be an adequate, proof, benchmark? I've already run several tests with nbench, testing all of the possible configurations of -march and -mtune. -- BSD Podcasts @ http://bsdtalk.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: well-supported SATA RAID card?
On 3/10/06, Brian Szymanski [EMAIL PROTECTED] wrote: Howdy... After not having much success with the hptmv driver for highpoint's rocketraid 1820A, I'm wondering if other folks have had good luck with any SATA RAID cards with at least 6 ports... Is there a SATA RAID card with utilities that let you manage while the OS is running that folks have had good luck with? I've been happy with the megaraid series on linux at my job, but I'm wondering if the management utilities are there on freebsd, etc. Anyone care to comment on Areca's ARC-11xx PCI-X cards? I'm thinking about getting an 1130 (12-port version). *Is the arcmsr driver in FreeBSD stable? *Any issues with arrays larger then 2TB? *Rebuild times? *Command Line management software? *Is the company BSD friendly, no binary blob object in the driver? *Competent tech support? *What does the ethernet port on the ARC-1130 do? I'm primarily interested in this card because it can do RAID level 6 and based on the benchmarks I've seen it's a top performer. Anyhow, to the OP, stay way from promise cards. -- BSD Podcasts @ http://bsdtalk.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: When is the 6.1 branch going to be cut?
On 3/11/06, M. Warner Losh [EMAIL PROTECTED] wrote: In message: [EMAIL PROTECTED] Nikolas Britton [EMAIL PROTECTED] writes: : March 5th was the scheduled date, what's the hold up? I think we're going to see another BETA (BETA4) shortly. The hold up is that there's still enough problems that need to be fixed that the release isn't near enough to do the branch. The schedules are done based on a best-guess approach, but in real life there can be a deviation between ones best guesses and what actually happens. Since FreeBSD isn't released based on a date[*], but based on when things in the branch are good, some slippage is bound to happen from time to time. Warner [*] We are moving to having the calendar drive more things than in the past, but that was done with the understanding that the dates are targets and we make choices to get as close to the targets as possible. Thanks for the status update, take all the time you need... All I ask is you keep the community in the loop. Have you thought about putting up a page on the website where FreeBSD committers and core members can easily post news, such as this, in an informal and/or casual manner?... wiki, blog, etc. Anyhow, Thanks for responding to my inquiry. -- BSD Podcasts @ http://bsdtalk.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
When is the 6.1 branch going to be cut?
March 5th was the scheduled date, what's the hold up? http://www.freebsd.org/releases/6.1R/schedule.html -- BSD Podcasts @ http://bsdtalk.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: loader_color=YES
On 3/9/06, Pete Slagle [EMAIL PROTECTED] wrote: Ruslan Ermilov wrote: loader_color is deprecated. One should use loader_logo as described in loader.conf(5) instead. Hmmm. Contrary to what you say, when I run 'man 5 loader.conf' on my 6.0-RELEASE-p4 box there is no mention whatsoever of loader_logo, and loader_color is recommended. Perhaps this has changed recently? man 5 loader.conf | grep -nC 2 logo 140- 141- loader_logo (``fbsdbw'') 142: Selects a desired logo in the beastie boot menu. Possi- 143- ble values are: ``fbsdbw'', ``beastiebw'', ``beastie'', 144- and ``none''. uname -a FreeBSD infomatic.intranet 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #0: Mon Feb 20 00:11:39 CST 2006 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/INFOMATIC i386 -- BSD Podcasts @ http://bsdtalk.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
loader_color=YES
What happen to 'loader_color=YES' if FreeBSD 6.x? If you put this in loader.conf it would make a color daemon in the boot menu. -- BSD Podcasts @ http://bsdtalk.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: loader_color=YES
On 2/28/06, Holger Kipp [EMAIL PROTECTED] wrote: On Tue, Feb 28, 2006 at 04:55:49AM -0600, Nikolas Britton wrote: What happen to 'loader_color=YES' if FreeBSD 6.x? If you put this in loader.conf it would make a color daemon in the boot menu. Please use loader_logo=beastie loader_color=YES Afaik the defaultness of the beastie-logo was dropped for political correctness. sarcasm Yippee! /sarcasm Thanks for you help. -- BSD Podcasts @ http://bsdtalk.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: loader_color=YES
On 2/28/06, Pete Slagle [EMAIL PROTECTED] wrote: Holger Kipp wrote: Please use loader_logo=beastie loader_color=YES loader_logo does not appear in /boot/defaults/loader.conf, at least not in 6.0-RELEASE-p4. Is that an oversight? Their are lots of undocumented feature in FreeBSD. loader_color=YES AFAIK It was never document in 5.x, I found it by accident -- BSD Podcasts @ http://bsdtalk.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Søren!!!, Promise FastTrak TX2300 semph ore timeouts, 6.1-BETA2
Nevermind, I followed my own advice, everything's working perfect now. 1. Removed promise and highpoint cards. 2. Connected the primary drive to the onboard SATA controllor. 3. Installed BETA2. 4. cvsup'd new src, checked if sos's patches were in there, it was. so he missed BETA2. 5. rebuilt kernel. 6. reinstalled highpoint card to check if highpoint's drivers where compatable with 6.1, yes. 7. Removed the highpoint card. 8. edited /etc/fstab to change ad4 to ar0 9. disabled onboard SATA. 10. Installed promise card and reconnected drives, setup RAID1 from BIOS. 11. highpoint drivers: echo 'hptmv6_load=YES' /boot/loader.conf 12. reinstalled highpoint card. 13. installed highpoint raid managment software. 14. ran build/install world/kern. On 2/25/06, Nikolas Britton [EMAIL PROTECTED] wrote: I'm getting ad(x): req=0xc(foobar) setfeatures set transfer mode semphore timeout !! Danger Will Robinson !! after I installed BETA2 on my server (Intel SE7210TP-E). I get the messages a few minutes after the systems booted up, and then it deadlocks. I had to go to great length just to get BETA2 installed... If I tried to install FreeBSD on ar0 sysinstall would just hang... I had to set the two drives up (Seagate 80GB SATA w/NCQ) in JOBD mode, install FreeBSD on ad4, reboot, edit /etc/fstab to point to ar0, and then set the RAID up in the BIOS. I had this server working just fine with the ata-mk3n patch set in 5.4, though I did see this error once before when I ran: nice -20 make -j2 buildworld /usr/data/buildworld.log. /usr/data points to da0e, the highpoint RAID5 array (8 300GB Maxtor maxline III drives) --- The other ata/disk problems I noticed with BETA2 is that FreeBSD probes and sets up my HighPoint RocketRAID 2220 as ata3, ata4, ata5, ata6, ata7, ata8, ata9, and ata10... FreeBSD shouldn't even touch it... as the card needs highpoints drivers for it to work correctly, when the drivers are install it will show up as a da device. I haven't had a chance to install the drivers yet, so I just removed the card. When I ran setup in verbose mode FreeBSD seemed to mix the promise card and this card together as one device... I wasn't paying close attention though. I also tried using the onboard Adaptec HostRAID but it shows up in FreeBSD as ata20 and ata22 when I have the highpoint card is installed, wtf! :-) http://groups.google.com/group/muc.lists.freebsd.current/browse_thread/thread/efd503b8311aecea/ I saw your thread from the current mailling list that you might have already fixed this, but I'm not sure if you MFC'd it in time for BETA2, maybe I will try and reinstall FreeBSD in JOBD mode again and then cvsup all the new src and rebuild world? - I could really use some help, This server has to be back online by 9am monday morning... If I can't get 6.x working I'll have to wait until this time next year to try again and thats no fun. Thanks... I'm going to bed now. -- BSD Podcasts @ http://bsdtalk.blogspot.com/ -- BSD Podcasts @ http://bsdtalk.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Søren!!!, Promise FastTrak TX2300 semphore ti meouts, 6.1-BETA2
I'm getting ad(x): req=0xc(foobar) setfeatures set transfer mode semphore timeout !! Danger Will Robinson !! after I installed BETA2 on my server (Intel SE7210TP-E). I get the messages a few minutes after the systems booted up, and then it deadlocks. I had to go to great length just to get BETA2 installed... If I tried to install FreeBSD on ar0 sysinstall would just hang... I had to set the two drives up (Seagate 80GB SATA w/NCQ) in JOBD mode, install FreeBSD on ad4, reboot, edit /etc/fstab to point to ar0, and then set the RAID up in the BIOS. I had this server working just fine with the ata-mk3n patch set in 5.4, though I did see this error once before when I ran: nice -20 make -j2 buildworld /usr/data/buildworld.log. /usr/data points to da0e, the highpoint RAID5 array (8 300GB Maxtor maxline III drives) --- The other ata/disk problems I noticed with BETA2 is that FreeBSD probes and sets up my HighPoint RocketRAID 2220 as ata3, ata4, ata5, ata6, ata7, ata8, ata9, and ata10... FreeBSD shouldn't even touch it... as the card needs highpoints drivers for it to work correctly, when the drivers are install it will show up as a da device. I haven't had a chance to install the drivers yet, so I just removed the card. When I ran setup in verbose mode FreeBSD seemed to mix the promise card and this card together as one device... I wasn't paying close attention though. I also tried using the onboard Adaptec HostRAID but it shows up in FreeBSD as ata20 and ata22 when I have the highpoint card is installed, wtf! :-) http://groups.google.com/group/muc.lists.freebsd.current/browse_thread/thread/efd503b8311aecea/ I saw your thread from the current mailling list that you might have already fixed this, but I'm not sure if you MFC'd it in time for BETA2, maybe I will try and reinstall FreeBSD in JOBD mode again and then cvsup all the new src and rebuild world? - I could really use some help, This server has to be back online by 9am monday morning... If I can't get 6.x working I'll have to wait until this time next year to try again and thats no fun. Thanks... I'm going to bed now. -- BSD Podcasts @ http://bsdtalk.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
