From owner-freebsd-hardware@FreeBSD.ORG Sun Dec 11 10:13:56 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 781A516A41F for ; Sun, 11 Dec 2005 10:13:56 +0000 (GMT) (envelope-from unnaturalness@lordarchitecture.com) Received: from aws70.neoplus.adsl.tpnet.pl (aws70.neoplus.adsl.tpnet.pl [83.27.78.70]) by mx1.FreeBSD.org (Postfix) with SMTP id A3E2543D5E for ; Sun, 11 Dec 2005 10:13:55 +0000 (GMT) (envelope-from unnaturalness@lordarchitecture.com) Received: from unknown (HELO Barhop) (192.168.65.185) by aws70.neoplus.adsl.tpnet.pl with SMTP; Sun, 11 Dec 2005 11:13:59 +0100 Content-Transfer-Encoding: 7bit Message-Id: <11911097995.40715104676@aws70.neoplus.adsl.tpnet.pl> Content-Type: text/plain; charset=us-ascii To: freebsd-hardware@freebsd.org From: Montague Love X-Antivirus: avast! (VPS 0550-0, 2005-12-10), Outbound message X-Antivirus-Status: Clean Date: Sun, 11 Dec 2005 10:13:55 +0000 (GMT) Subject: Penis enhancement system that works for countless men worldwide. X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Dec 2005 10:13:56 -0000 Bigger, harder, and longer - lasting results NOW with a discreet little patch. http://www.kurevalw.net/pt/ Now is the time for all good men to come to. Laugh and the world laughs with you, snore and you sleep alone. He that is not open to conviction, is not qualified for discussion. Most joyful the Poet be;It is through him that all men see. We need men who can dream of things that never were. From owner-freebsd-hardware@FreeBSD.ORG Sun Dec 11 21:08:08 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A5BB416A41F for ; Sun, 11 Dec 2005 21:08:08 +0000 (GMT) (envelope-from shurup@gala.net) Received: from el.volia.net (el.volia.net [82.144.192.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id D7C8B43D58 for ; Sun, 11 Dec 2005 21:08:07 +0000 (GMT) (envelope-from shurup@gala.net) Received: from ip.85.202.200.236.dyn.sub-4.broadband.voliacable.com ([85.202.200.236] helo=.voliacable.com) by el.volia.net with esmtp (Exim 4.43 (FreeBSD)) id 1ElYQP-0008rj-Dz for freebsd-hardware@freebsd.org; Sun, 11 Dec 2005 23:08:06 +0200 Date: Sun, 11 Dec 2005 23:08:08 +0000 From: Alex To: freebsd-hardware@freebsd.org Message-Id: <20051211230808.386d2efc.shurup@gala.net> X-Mailer: Sylpheed version 2.0.0rc (GTK+ 2.6.8; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: One problem, HELP! X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Dec 2005 21:08:08 -0000 Please help me! I have a problem with AVermedia 305 My kernel is: # # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../conf/NOTES and NOTES files. # If you are in doubt as to the purpose or necessity of a line, check first # in NOTES. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.429.2.3.2.1 2005/10/28 19:22:41 jhb Exp $ machine i386 cpu I686_CPU ident GENERIC # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols #options SCHED_ULE # ULE scheduler options SCHED_4BSD # 4BSD scheduler options PREEMPTION # Enable kernel thread preemption options INET # InterNETworking options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options MD_ROOT # MD is a potential root device options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options NFS_ROOT # NFS usable as /, requires NFSCLIENT options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_GPT # GUID Partition Tables. options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev options AHC_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~128k to driver. options AHD_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~215k to driver. options ADAPTIVE_GIANT # Giant mutex is adaptive. options QUOTA #my options options IPFIREWALL #IPFW options IPFIREWALL_VERBOSE options IPFIREWALL_DEFAULT_TO_ACCEPT options IPFIREWALL_FORWARD options IPSTEALTH options DUMMYNET #IPFW options IPFILTER #IPFILTER options IPFILTER_LOG options ALTQ #IPFILTER options IPV6FIREWALL #firewall for IPv6 options IPV6FIREWALL_VERBOSE options IPV6FIREWALL_VERBOSE_LIMIT=100 options IPV6FIREWALL_DEFAULT_TO_ACCEPT options IPDIVERT #NAT-MASKARADING options TCP_DROP_SYNFIN # Access Control List support for UFS filesystems. The current ACL # implementation requires extended attribute support, UFS_EXTATTR, # for the underlying filesystem. # See src/sys/ufs/ufs/README.acls for more information. options UFS_ACL device apic # I/O APIC # Bus support. device eisa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device ataraid # ATA RAID drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID # Static device numbering # SCSI Controllers device ahb # EISA AHA1742 family device ahc # AHA2940 and onboard AIC7xxx devices device ahd # AHA39320/29320 and onboard AIC79xx devices device amd # AMD 53C974 (Tekram DC-390(T)) device isp # Qlogic family #device ispfw # Firmware for QLogic HBAs- normally a module device mpt # LSI-Logic MPT-Fusion #device ncr # NCR/Symbios Logic device sym # NCR/Symbios Logic (newer chipsets + those of `ncr') device trm # Tekram DC395U/UW/F DC315U adapters device adv # Advansys SCSI adapters device adw # Advansys wide SCSI adapters device aha # Adaptec 154x SCSI adapters device aic # Adaptec 15[012]x SCSI adapters, AIC-6[23]60. device bt # Buslogic/Mylex MultiMaster SCSI adapters device ncv # NCR 53C500 device nsp # Workbit Ninja SCSI-3 device stg # TMC 18C30/18C50 # SCSI peripherals device scbus # SCSI bus (required for SCSI) device ch # SCSI media changers device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) device ses # SCSI Environmental Services (and SAF-TE) # RAID controllers interfaced to the SCSI subsystem device amr # AMI MegaRAID device arcmsr # Areca SATA II RAID device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID device ciss # Compaq Smart RAID 5* device dpt # DPT Smartcache III, IV - See NOTES for options device hptmv # Highpoint RocketRAID 182x device iir # Intel Integrated RAID device ips # IBM (Adaptec) ServeRAID device mly # Mylex AcceleRAID/eXtremeRAID device twa # 3ware 9000 series PATA/SATA RAID # RAID controllers device aac # Adaptec FSA RAID device aacp # SCSI passthrough for aac (requires CAM) device ida # Compaq Smart RAID device mlx # Mylex DAC960 family device pst # Promise Supertrak SX6000 device twe # 3ware ATA RAID # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc # Enable this for the pcvt (VT220 compatible) console driver #device vt #options XSERVER # support for X server on a vt console #options FAT_CURSOR # start with block cursor device agp # support several AGP chipsets # Power management support (see NOTES for more options) #device apm # Add suspend/resume support for the i8254. device pmtimer # PCCARD (PCMCIA) support # PCMCIA and cardbus bridge support device cbb # cardbus (yenta) bridge device pccard # PC Card (16-bit) bus device cardbus # CardBus (32-bit) bus # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer device plip # TCP/IP over parallel device ppi # Parallel port interface device #device vpo # Requires scbus and da # If you've got a "dumb" serial or parallel PCI card that is # supported by the puc(4) glue driver, uncomment the following # line to enable it (connects to the sio and/or ppc drivers): #device puc # PCI Ethernet NICs. device de # DEC/Intel DC21x4x (``Tulip'') device em # Intel PRO/1000 adapter Gigabit Ethernet Card device ixgb # Intel PRO/10GbE Ethernet Card device txp # 3Com 3cR990 (``Typhoon'') device vx # 3Com 3c590, 3c595 (``Vortex'') # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device bfe # Broadcom BCM440x 10/100 Ethernet device bge # Broadcom BCM570xx Gigabit Ethernet device dc # DEC/Intel 21143 and various workalikes device fxp # Intel EtherExpress PRO/100B (82557, 82558) device lge # Level 1 LXT1001 gigabit Ethernet device nge # NatSemi DP83820 gigabit Ethernet device nve # nVidia nForce MCP on-board Ethernet Networking device pcn # AMD Am79C97x PCI 10/100(precedence over 'lnc') device re # RealTek 8139C+/8169/8169S/8110S device rl # RealTek 8129/8139 device sf # Adaptec AIC-6915 (``Starfire'') device sis # Silicon Integrated Systems SiS 900/SiS 7016 device sk # SysKonnect SK-984x & SK-982x gigabit Ethernet device ste # Sundance ST201 (D-Link DFE-550TX) device ti # Alteon Networks Tigon I/II gigabit Ethernet device tl # Texas Instruments ThunderLAN device tx # SMC EtherPower II (83c170 ``EPIC'') device vge # VIA VT612x gigabit Ethernet device vr # VIA Rhine, Rhine II device wb # Winbond W89C840F device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. pccard NICs included. device cs # Crystal Semiconductor CS89x0 NIC # 'device ed' requires 'device miibus' device ed # NE[12]000, SMC Ultra, 3c503, DS8390 cards device ex # Intel EtherExpress Pro/10 and Pro/10+ device ep # Etherlink III based cards device fe # Fujitsu MB8696x based cards device ie # EtherExpress 8/16, 3C507, StarLAN 10 etc. device lnc # NE2100, NE32-VL Lance Ethernet cards device sn # SMC's 9000 series of Ethernet chips device xe # Xircom pccard Ethernet # ISA devices that use the old ISA shims #device le # Wireless NIC cards device wlan # 802.11 support device an # Aironet 4500/4800 802.11 wireless NICs. device awi # BayStack 660 and others device ral # Ralink Technology RT2500 wireless NICs. device wi # WaveLAN/Intersil/Symbol 802.11 wireless NICs. #device wl # Older non 802.11 Wavelan wireless NIC. # Pseudo devices. device loop # Network loopback device random # Entropy device device ether # Ethernet support device sl # Kernel SLIP device ppp # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device gif # IPv6 and IPv4 tunneling device faith # IPv6-to-IPv4 relaying (translation) # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! # Note that 'bpf' is required for DHCP. device bpf # Berkeley packet filter # USB support device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device ehci # EHCI PCI->USB interface (USB 2.0) device usb # USB Bus (required) #device udbp # USB Double Bulk Pipe devices device ugen # Generic device uhid # "Human Interface Devices" device ukbd # Keyboard device ulpt # Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse device ural # Ralink Technology RT2500USB wireless NICs device urio # Diamond Rio 500 MP3 player device uscanner # Scanners # USB Ethernet, requires miibus device aue # ADMtek USB Ethernet device axe # ASIX Electronics USB Ethernet device cdce # Generic USB over Ethernet device cue # CATC USB Ethernet device kue # Kawasaki LSI USB Ethernet device rue # RealTek RTL8150 USB Ethernet # FireWire support device firewire # FireWire bus code device sbp # SCSI over FireWire (Requires scbus and da) device fwe # Ethernet over FireWire (non-standard!) options OVERRIDE_CARD=6 options OVERRIDE_TUNER=6 options OVERRIDE_MSP=1 options OVERRIDE_DBX=1 options BROOKTREE_SYSTEM_DEFAULT=BROOKTREE_PAL options BKTR_USE_PLL options BKTR_USE_FREEBSD_SMBUS device bktr device sound device "snd_cs4281" device iicbus device iicbb device smbus options BKTR_GPIO_ACCESS ##options BKTR_NO_MSP_RESET When reboot is gone i'm type: # dmesg | grep pci pci_link0: irq 10 on acpi0 pci_link1: irq 10 on acpi0 pci_link2: irq 5 on acpi0 pci_link3: irq 5 on acpi0 pci_link4: irq 11 on acpi0 pci_link5: irq 10 on acpi0 pci_link6: irq 10 on acpi0 pci_link7: irq 11 on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xe0000000-0xefffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) pci1: at device 0.1 (no driver attached) uhci0: port 0xef00-0xef1f irq 16 at device 29.0 on pci0 uhci1: port 0xef20-0xef3f irq 19 at device 29.1 on pci0 uhci2: port 0xef40-0xef5f irq 18 at device 29.2 on pci0 uhci3: port 0xef80-0xef9f irq 16 at device 29.3 on pci0 ehci0: mem 0xfebffc00-0xfebfffff irq 23 at device 29.7 on pci0 pcib2: at device 30.0 on pci0 pci2: on pcib2 pcm0: mem 0xfeafb000-0xfeafbfff,0xfeae0000-0xfeaeffff irq 22 at device 10.0 on pci2 pci2: at device 11.0 (no driver attached) rl0: port 0xd800-0xd8ff mem 0xfeafa800-0xfeafa8ff irq 20 at device 12.0 on pci2 rl1: port 0xd400-0xd4ff mem 0xfeaffc00-0xfeaffcff irq 21 at device 13.0 on pci2 isab0: at device 31.0 on pci0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 pci0: at device 31.3 (no driver attached) Help me please and sorry for my bad englesh, I'm frome Ukraine From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 12 14:42:33 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0AC8416A41F for ; Mon, 12 Dec 2005 14:42:33 +0000 (GMT) (envelope-from fierykylin@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C01F43D67 for ; Mon, 12 Dec 2005 14:42:31 +0000 (GMT) (envelope-from fierykylin@gmail.com) Received: by xproxy.gmail.com with SMTP id i26so1028551wxd for ; Mon, 12 Dec 2005 06:42:31 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=evJF9Qs1YSa08qP7ypCQFqM0TjiTPQOOFiWJSZQ3wN7lM7VzNUc3IyTTqQYnOH8TtWurUb9UuaXkRqYxUT6x7DsP/+nti7RGzWCy6j7rrvS8UIt7e2QEE4251lbtrijTQ8evb88idyMeSrB+WfjloFumtFUmyrrxPdkghFmmf7A= Received: by 10.70.79.11 with SMTP id c11mr9206258wxb; Mon, 12 Dec 2005 06:42:30 -0800 (PST) Received: by 10.70.18.16 with HTTP; Mon, 12 Dec 2005 06:42:30 -0800 (PST) Message-ID: <87ab37ab0512120642s14385a2agc9a210c861994e72@mail.gmail.com> Date: Mon, 12 Dec 2005 22:42:30 +0800 From: kylin To: freebsd-hardware@freebsd.org In-Reply-To: <20051212120037.2851116A420@hub.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20051212120037.2851116A420@hub.freebsd.org> Subject: Re: freebsd-hardware Digest, Vol 142, Issue 1 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 14:42:33 -0000 what is wrong with ur AVermedia 305,Dovulixi? does it miss the driver? On 12/12/05, freebsd-hardware-request@freebsd.org wrote: > Send freebsd-hardware mailing list submissions to > freebsd-hardware@freebsd.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > or, via email, send a message with subject or body 'help' to > freebsd-hardware-request@freebsd.org > > You can reach the person managing the list at > freebsd-hardware-owner@freebsd.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of freebsd-hardware digest..." > > > Today's Topics: > > 1. One problem, HELP! (Alex) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 11 Dec 2005 23:08:08 +0000 > From: Alex > Subject: One problem, HELP! > To: freebsd-hardware@freebsd.org > Message-ID: <20051211230808.386d2efc.shurup@gala.net> > Content-Type: text/plain; charset=3DUS-ASCII > > Please help me! > I have a problem with AVermedia 305 > My kernel is: > # > # GENERIC -- Generic kernel configuration file for FreeBSD/i386 > # > # dmesg | grep pci > pci_link0: irq 10 on acpi0 > pci_link1: irq 10 on acpi0 > pci_link2: irq 5 on acpi0 > pci_link3: irq 5 on acpi0 > pci_link4: irq 11 on acpi0 > pci_link5: irq 10 on acpi0 > pci_link6: irq 10 on acpi0 > pci_link7: irq 11 on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > agp0: mem 0xe0000000-0xefffffff at devic= e 0.0 on pci0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > pci1: at device 0.0 (no driver attached) > pci1: at device 0.1 (no driver attached) > uhci0: port 0xef00-0xef1f irq= 16 at device 29.0 on pci0 > uhci1: port 0xef20-0xef3f irq= 19 at device 29.1 on pci0 > uhci2: port 0xef40-0xef5f irq= 18 at device 29.2 on pci0 > uhci3: port 0xef80-0xef9f irq= 16 at device 29.3 on pci0 > ehci0: mem 0xfebffc00-0xfebfffff irq = 23 at device 29.7 on pci0 > pcib2: at device 30.0 on pci0 > pci2: on pcib2 > pcm0: mem 0xfeafb000-0xfeafbfff,0xfeae0000= -0xfeaeffff irq 22 at device 10.0 on pci2 > pci2: at device 11.0 (no driver attached) > rl0: port 0xd800-0xd8ff mem 0xfeafa800-0xfeaf= a8ff irq 20 at device 12.0 on pci2 > rl1: port 0xd400-0xd4ff mem 0xfeaffc00-0xfeaf= fcff irq 21 at device 13.0 on pci2 > isab0: at device 31.0 on pci0 > atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x1= 77,0x376,0xfc00-0xfc0f at device 31.1 on pci0 > ata0: on atapci0 > ata1: on atapci0 > pci0: at device 31.3 (no driver attached) > Help me please and sorry for my bad englesh, I'm frome Ukraine > > > ------------------------------ > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.or= g" > > End of freebsd-hardware Digest, Vol 142, Issue 1 > ************************************************ > -- we who r about to die,salute u! From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 12 18:29:37 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E67B416A41F for ; Mon, 12 Dec 2005 18:29:37 +0000 (GMT) (envelope-from harrow@yandex.ru) Received: from soapbox.yandex.ru (soapbox.yandex.ru [213.180.200.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77C2F43D53 for ; Mon, 12 Dec 2005 18:29:37 +0000 (GMT) (envelope-from harrow@yandex.ru) Received: from YAMAIL (soapbox.yandex.ru) by mail.yandex.ru id ; Mon, 12 Dec 2005 21:29:20 +0300 Date: Mon, 12 Dec 2005 21:29:20 +0300 (MSK) From: "harrow" Sender: harrow@yandex.ru Message-Id: <439DC180.000005.21440@soapbox.yandex.ru> MIME-Version: 1.0 X-Mailer: Yamail [ http://yandex.ru ] Errors-To: harrow@yandex.ru To: freebsd-hardware@freebsd.org In-Reply-To: <20051212120037.3FD7116A41F@hub.freebsd.org> References: <20051212120037.3FD7116A41F@hub.freebsd.org> X-Source-Ip: 62.76.89.34 X-Originating-Ip: 192.168.120.17, 10.111.0.8 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: AverMedia 305 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: harrow@yandex.ru List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 18:29:38 -0000 As I know, there are some modules for SAA713x (SAA7134 for AverMedia 305) chips exists for 5.x-6.x FreeBSD. Try search for them with (for example) google in such way: "+SAA7134 +FreeBSD" then... one of results is http://lists.freebsd.org/pipermail/freebsd-multimedia/2004-August/001317.html >Rohit Jalan rohitj at purpe.com >Fri Aug 27 02:55:29 PDT 2004 >Previous message: mplayer/mencoder with bktr(4) device >Next message: FreeBSD 5.x driver for SAA7134 PCI video capture/tuner boards >Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] > >-------------------------------------------------------------------------------- > >The driver and applications can be found at: > > http://download.purpe.com > > >For a list of cards based on the SAA7134 chip see: > > http://lxr.linux.no/source/Documentation/video4linux/CARDLIST.saa7134?v=2.6.5 > and > http://home.t-online.de/home/gunther.mayer/bttv/bttv-gallery.html > > >Rohit -- From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 12 22:29:46 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 59EB516A41F for ; Mon, 12 Dec 2005 22:29:46 +0000 (GMT) (envelope-from fhard@ccstores.com) Received: from mail.qcislands.net (mail.qcislands.net [209.53.238.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id CFED243D68 for ; Mon, 12 Dec 2005 22:29:45 +0000 (GMT) (envelope-from fhard@ccstores.com) Received: from [64.114.58.101] (helo=[192.168.1.4]) by mail.qcislands.net with esmtp (Exim 4.60) (envelope-from ) id 1ElwAz-000LPz-79; Mon, 12 Dec 2005 14:29:45 -0800 Message-ID: <439DF9D9.2040507@ccstores.com> Date: Mon, 12 Dec 2005 14:29:45 -0800 From: Jim Pazarena Organization: City Centre Stores Ltd User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hardware@freebsd.org References: <439A576E.3070302@ccstores.com> In-Reply-To: <439A576E.3070302@ccstores.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-local_scan: locally submitted (01) Subject: hardware incompatibility list was:watchdog timeout X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 22:29:46 -0000 Jim Pazarena wrote: > on FreeBSD 5.4 I simply never had this problem > on 6.0, it is continuous. > > A PCMCIA card, 3Com Megahertz 10/100 Lan Cardbus PC Card > 3CCFE575BT > > xl0: watchdog timeout > > over and over and over > > It has forced me to switch back to 5.4 on my laptop. > Can anyone offer an explanation why 5.4 wouldn't complain, > but 6.0 won't _stop_ ? > > Thanks, > Jim I have come to dis-trust the Hardware Compatibility list. The above 3Com model # worked flawlessly in 5.4, *is* present on the 6.0 compatibility list, but none-the-less doesn't work without multiple never-ending watchdog timeouts on 6.0. The same is true with a Specialix SX multiple serial I/O system. Just plain doesn't work with *5.4* _or_ 6.0. John Baldwin is helping me with that one. What I am getting at, is, that the Hardware Compatibility I am feared is woefully out of date. Old hardware may not work with the newer kernel (as evidenced by the 3Com failure in 6.0), and new hardware just plain doesn't work (as evidenced by the brand new Specialix card not working). I suggest that someone should attempt to validate all the listed hardware in the recent releases so that the end user (like myself) does not get stung spending money on new hardware which isn't compatible with newer kernel releases. Perhaps a form can be created for end-users to fill in the blanks (or pull-down from the list) to enter which hardware (they/we) are using, which OS version, etc, so a new list can be verified? respectfully, Jim From owner-freebsd-hardware@FreeBSD.ORG Tue Dec 13 02:34:34 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 08EA616A41F for ; Tue, 13 Dec 2005 02:34:34 +0000 (GMT) (envelope-from fredthetree@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3325D43D46 for ; Tue, 13 Dec 2005 02:34:32 +0000 (GMT) (envelope-from fredthetree@gmail.com) Received: by wproxy.gmail.com with SMTP id i11so30083wra for ; Mon, 12 Dec 2005 18:34:32 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=iyCx6zinuryHCHHxKsXLWVBlgzqzbqTEIPnfKPCii/5fW2yqzj3IDwf2SD2KWHANmSTyTCOpfOMaF+ULKLkXPgpKlij031Q/iipzOIx9hQnbjZnmZznwJ/ZgaTM7spTrs9pEAgCZANsUOj02tIy1iyyxmXWix9nO1qCrqvI3QUQ= Received: by 10.54.156.14 with SMTP id d14mr209974wre; Mon, 12 Dec 2005 18:34:31 -0800 (PST) Received: by 10.54.146.19 with HTTP; Mon, 12 Dec 2005 18:34:31 -0800 (PST) Message-ID: Date: Mon, 12 Dec 2005 22:34:31 -0400 From: fredthetree To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: ath0: device timeouts X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 02:34:34 -0000 FreeBSD 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 root@x64.samsco.home:/usr/obj/usr/src/sys/GENERIC i386 every so often i get a "device timeout" warning, but what really irks me, a file starts downloading, and it just hangs.............................. nothing happens at all, with fetch, with firefox, etc. i've found the problem only exists for a transfer of a single file, ie, if i have all sort= s of internet activity there is no problem. example situation: fetch x.y 5% done (hangs indefinately) in another terminal, if i type in "ping google.com" and either it starts pinging, and the transfer starts again, or nothing happens, then i get ath device timeout, ping again, and it starts up, if the only internet activit= y is fetch and ping, stopping ping will often stop the transfer. i lots of (continuous) small internet activity in order to keep any transfer going. ath on 5.4 has some weirdness as well, but not like this Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 root@x64.samsco.home:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel Pentium III (701.59-MHz 686-class CPU) Origin =3D "GenuineIntel" Id =3D 0x683 Stepping =3D 3 Features=3D0x387f9ff real memory =3D 536805376 (511 MB) avail memory =3D 515956736 (492 MB) ath_hal: 0.9.14.9 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413) npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) pci_link0: irq 11 on acpi0 pci_link1: irq 5 on acpi0 pci_link2: irq 9 on acpi0 pci_link3: irq 10 on acpi0 Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff,0x4000-0x4041,0x5000-0x500f on acpi0 pci0: on pcib0 agp0: mem 0xe0000000-0xe3ffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 7.1 on pci0 ata0: on atapci0 ata1: on atapci0 uhci0: port 0x9000-0x901f irq 10 at device 7.2 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: at device 7.3 (no driver attached) pcm0: port 0x9400-0x941f irq 9 at device 10.0 on pci0 pcm0: ath0: mem 0xe8000000-0xe800ffff irq 5 at device 11.0 on pci0 ath0: Ethernet address: 00:0f:3d:50:13:5c ath0: mac 5.9 phy 4.3 radio 4.6 fdc0: port 0x3f2-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0: port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 pmtimer0 on isa0 orm0: at iomem 0xc0000-0xcffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 umass0: Cowon Systems, Inc. iAUDIO M3 Digital Audio Player, rev 2.00/1.00, addr 2 ugen0: EPSON EPSON Scanner, rev 2.00/1.10, addr 3 Timecounter "TSC" frequency 701594095 Hz quality 800 Timecounters tick every 1.000 msec ad0: 8063MB at ata0-master UDMA33 ad1: 57241MB at ata0-slave UDMA33 acd0: CDRW at ata1-master UDMA33 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: 19073MB (39063024 512 byte sectors: 255H 63S/T 2431C) Trying to mount root from ufs:/dev/ad0s1a From owner-freebsd-hardware@FreeBSD.ORG Tue Dec 13 02:46:04 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 135D216A41F for ; Tue, 13 Dec 2005 02:46:04 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail13.syd.optusnet.com.au (mail13.syd.optusnet.com.au [211.29.132.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9975143D64 for ; Tue, 13 Dec 2005 02:46:01 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail13.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id jBD2jsJA021246 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 13 Dec 2005 13:45:55 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id jBD2jsHh077604; Tue, 13 Dec 2005 13:45:54 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id jBD2jrJU077603; Tue, 13 Dec 2005 13:45:53 +1100 (EST) (envelope-from pjeremy) Date: Tue, 13 Dec 2005 13:45:53 +1100 From: Peter Jeremy To: Jim Pazarena Message-ID: <20051213024553.GB77268@cirb503493.alcatel.com.au> References: <439A576E.3070302@ccstores.com> <439DF9D9.2040507@ccstores.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <439DF9D9.2040507@ccstores.com> User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc Cc: freebsd-hardware@freebsd.org Subject: Re: hardware incompatibility list was:watchdog timeout X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 02:46:04 -0000 On Mon, 2005-Dec-12 14:29:45 -0800, Jim Pazarena wrote: >What I am getting at, is, that the Hardware Compatibility I am feared >is woefully out of date. It does state "Feedback, updates, and corrections to this list are encouraged." >I suggest that someone should attempt to validate all the listed >hardware in the recent releases so that the end user (like myself) >does not get stung spending money on new hardware which isn't >compatible with newer kernel releases. I've been bitten by a related problem. In reality, what you want can't happen - no-one has the money to buy all the hardware or the time to test it in all. A very rough count gives just over 1400 entries in 6.0R/hardware-i386.html. Add to that vendors' propensity to totally redesign the hardware without changing the model number so you still can't be certain that what you just bought as a WizzBang XY656JT bears any resemblance to the one that was tested. (Which could be the problem with your Specialix card). The real solution is for hardware vendors to either directly support FreeBSD or provide adequate details to allow someone to independently write a driver. The size of the FreeBSD market means that this is very unlikely to happen in general. >Perhaps a form can be created for end-users to fill in the blanks >(or pull-down from the list) to enter which hardware (they/we) are >using, which OS version, etc, so a new list can be verified? This isn't perfect but may help. There's a similar list maintained for laptops. If you believe this is a worthwhile approach, how about you put something together and announce the URL here. -- Peter Jeremy From owner-freebsd-hardware@FreeBSD.ORG Tue Dec 13 13:26:11 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 43F5716A41F for ; Tue, 13 Dec 2005 13:26:11 +0000 (GMT) (envelope-from cajfox@mail.bg) Received: from mx1.mail.bg (mx1.mail.bg [193.201.172.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D37443D75 for ; Tue, 13 Dec 2005 13:26:10 +0000 (GMT) (envelope-from cajfox@mail.bg) Received: from localhost (web1.mail.bg [193.201.172.98]) by mx1.mail.bg (Postfix) with ESMTP id 635379000A19 for ; Tue, 13 Dec 2005 15:26:04 +0200 (EET) Received: from 87-126-34-18.btc-net.bg (87-126-34-18.btc-net.bg [87.126.34.18]) by mail.bg (mail.bG Webmail 4.0.1) with HTTP for ; Tue, 13 Dec 2005 15:26:04 +0200 Message-ID: <1134480364.0f0e31d464906@mail.bg> Date: Tue, 13 Dec 2005 15:26:04 +0200 From: cajfox@mail.bg To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1251" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: mail.bG Webmail 4.0-cvs X-Originating-IP: 87.126.34.18 Subject: Olympus VN240PC on FreeBSD-6.0R X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 13:26:11 -0000 Do You know how can I setup my Olympus VN240PC voice recorder under FreeBSD-6.0R? I have the CD with the drivers but they are for Windows. Ideas? -------------------------------------- =C1=E5=E7=EF=EB=E0=F2=ED=E0=F2=E0 =EF=EE=F9=E0 =E2 mail.bg =E2=E5=F7=E5 =E5 = 1GB! From owner-freebsd-hardware@FreeBSD.ORG Tue Dec 13 17:38:53 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF32216A420 for ; Tue, 13 Dec 2005 17:38:53 +0000 (GMT) (envelope-from alexandre.delay@free.fr) Received: from smtp2-g19.free.fr (smtp2-g19.free.fr [212.27.42.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE4CC43D62 for ; Tue, 13 Dec 2005 17:38:48 +0000 (GMT) (envelope-from alexandre.delay@free.fr) Received: from Cerbere-de-Troyes.cerbere23.com (eur10-1-82-241-181-23.fbx.proxad.net [82.241.181.23]) by smtp2-g19.free.fr (Postfix) with ESMTP id DC0BE5CE67 for ; Tue, 13 Dec 2005 18:38:47 +0100 (CET) Received: from artemis ([192.168.2.2]) by Cerbere-de-Troyes.cerbere23.com (8.13.3/8.13.3) with SMTP id jBDHck47090929 for ; Tue, 13 Dec 2005 18:38:47 +0100 (CET) (envelope-from alexandre.delay@free.fr) From: "Alexandre DELAY" To: Date: Tue, 13 Dec 2005 18:38:55 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: HDD X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 17:38:53 -0000 Hi guys, I would like to know what you think of hard drive disk running under FreeBSD. The fact is that it is quite difficult to keep it working with "hard power off". I added a small fsck_enable="YES" in my rc.conf file, but my system keeps have some trouble when the power fails. Is there a way to make FreeBSD running very well with power failure? I thought of Compact flash cards as system disk. Do you think it would make the system more stable with power failure? cheers Alex From owner-freebsd-hardware@FreeBSD.ORG Tue Dec 13 18:43:15 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D3C9B16A41F for ; Tue, 13 Dec 2005 18:43:15 +0000 (GMT) (envelope-from gaynw@bristolsystems.com) Received: from fed1rmmtao07.cox.net (fed1rmmtao07.cox.net [68.230.241.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA05943D60 for ; Tue, 13 Dec 2005 18:43:14 +0000 (GMT) (envelope-from gaynw@bristolsystems.com) Received: from workdog ([68.228.71.3]) by fed1rmmtao07.cox.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20051213184236.VLFH3131.fed1rmmtao07.cox.net@workdog>; Tue, 13 Dec 2005 13:42:36 -0500 From: "Gayn Winters" To: "'Alexandre DELAY'" , Date: Tue, 13 Dec 2005 10:42:54 -0800 Message-ID: <046a01c60015$0a44c4b0$6501a8c0@workdog> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal Cc: Subject: RE: HDD X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 18:43:15 -0000 > -----Original Message----- > From: owner-freebsd-hardware@freebsd.org > [mailto:owner-freebsd-hardware@freebsd.org] On Behalf Of > Alexandre DELAY > Sent: Tuesday, December 13, 2005 9:39 AM > To: freebsd-hardware@freebsd.org > Subject: HDD > > > Hi guys, > > I would like to know what you think of hard drive disk running under > FreeBSD. The fact is that it is quite difficult to keep it working > with "hard power off". I added a small fsck_enable="YES" in my rc.conf file, > but my system keeps have some trouble when the power fails. > > Is there a way to make FreeBSD running very well with power failure? > I thought of Compact flash cards as system disk. Do you think > it would make the system more stable with power failure? Use a UPS. -gayn Bristol Systems Inc. 714/532-6776 www.bristolsystems.com From owner-freebsd-hardware@FreeBSD.ORG Tue Dec 13 19:03:36 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 55C0816A420 for ; Tue, 13 Dec 2005 19:03:36 +0000 (GMT) (envelope-from alexandre.delay@free.fr) Received: from smtp5-g19.free.fr (smtp5-g19.free.fr [212.27.42.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 916BF43D55 for ; Tue, 13 Dec 2005 19:03:32 +0000 (GMT) (envelope-from alexandre.delay@free.fr) Received: from Cerbere-de-Troyes.cerbere23.com (eur10-1-82-241-181-23.fbx.proxad.net [82.241.181.23]) by smtp5-g19.free.fr (Postfix) with ESMTP id 5343916F10 for ; Tue, 13 Dec 2005 20:03:30 +0100 (CET) Received: from artemis ([192.168.2.2]) by Cerbere-de-Troyes.cerbere23.com (8.13.3/8.13.3) with SMTP id jBDJ3OM1092387 for ; Tue, 13 Dec 2005 20:03:24 +0100 (CET) (envelope-from alexandre.delay@free.fr) From: "Alexandre DELAY" To: Date: Tue, 13 Dec 2005 20:03:33 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <046a01c60015$0a44c4b0$6501a8c0@workdog> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal Subject: RE: HDD X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 19:03:36 -0000 he he! nice answer! The fact is that it is not exactly my question. You think it is normal that nowdays we are limited by this hardware??? hdds are more than 50 years old!! It has been invented in 1953 by some guy at IBM. > -----Message d'origine----- > De : owner-freebsd-hardware@freebsd.org > [mailto:owner-freebsd-hardware@freebsd.org]De la part de Gayn Winters > Envoye : mardi 13 decembre 2005 19:43 > A : 'Alexandre DELAY'; freebsd-hardware@freebsd.org > Objet : RE: HDD > > > > -----Original Message----- > > From: owner-freebsd-hardware@freebsd.org > > [mailto:owner-freebsd-hardware@freebsd.org] On Behalf Of > > Alexandre DELAY > > Sent: Tuesday, December 13, 2005 9:39 AM > > To: freebsd-hardware@freebsd.org > > Subject: HDD > > > > > > Hi guys, > > > > I would like to know what you think of hard drive disk running under > > FreeBSD. The fact is that it is quite difficult to keep it working > > with "hard power off". I added a small fsck_enable="YES" in my rc.conf > file, > > but my system keeps have some trouble when the power fails. > > > > Is there a way to make FreeBSD running very well with power failure? > > I thought of Compact flash cards as system disk. Do you think > > it would make the system more stable with power failure? > > Use a UPS. > > -gayn > > Bristol Systems Inc. > 714/532-6776 > www.bristolsystems.com > > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to > "freebsd-hardware-unsubscribe@freebsd.org" > From owner-freebsd-hardware@FreeBSD.ORG Wed Dec 14 00:35:36 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B89316A41F for ; Wed, 14 Dec 2005 00:35:36 +0000 (GMT) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED14343D5F for ; Wed, 14 Dec 2005 00:35:29 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.60 (FreeBSD)) (envelope-from ) id 1EmKcB-0004ws-Rg; Wed, 14 Dec 2005 00:35:28 +0000 Received: from localhost ([127.0.0.1] helo=roam.psg.com) by roam.psg.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1EmKc3-000Pil-Sp; Wed, 14 Dec 2005 07:35:19 +0700 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17311.26823.195210.842876@roam.psg.com> Date: Wed, 14 Dec 2005 07:35:19 +0700 To: "Alexandre DELAY" References: <046a01c60015$0a44c4b0$6501a8c0@workdog> Cc: freebsd-hardware@freebsd.org Subject: RE: HDD X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 00:35:36 -0000 > You think it is normal that nowdays we are limited by this hardware??? not at all. at least not if you don't want to use computers. i am sure some of us have slide rules we might be willing to sell. though they had hardware problems too, required alignment, are hard to see in the dark (when power is out), etc. good luck in your fantasy world. randy From owner-freebsd-hardware@FreeBSD.ORG Wed Dec 14 01:51:21 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D7EA316A41F for ; Wed, 14 Dec 2005 01:51:21 +0000 (GMT) (envelope-from woh@vault-tec.de) Received: from athen022.server4you.de (athen022.server4you.de [217.172.180.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F75543D55 for ; Wed, 14 Dec 2005 01:51:20 +0000 (GMT) (envelope-from woh@vault-tec.de) Received: from [10.0.1.9] (p5493DC39.dip.t-dialin.net [84.147.220.57]) (authenticated bits=0) by athen022.server4you.de (8.13.1/8.13.1/SuSE Linux 0.7) with ESMTP id jBE1pEPx031243; Wed, 14 Dec 2005 02:51:17 +0100 Message-ID: <439F7AF3.7000709@vault-tec.de> Date: Wed, 14 Dec 2005 02:52:51 +0100 From: Wolfram Huesken User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051209) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alexandre DELAY References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hardware@freebsd.org Subject: Re: HDD X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 01:51:22 -0000 You could mount the filesystem as read-only and use a ramdisk for the partitions that need write access like /tmp or /var. You also would prevent your CF-Card from damage because you cannot perform unlimited io operations on that card. I've already tested this with a kind of embedded appliance that acts as a router. - Wolfram Alexandre DELAY wrote: >he he! >nice answer! > >The fact is that it is not exactly my question. >You think it is normal that nowdays we are limited by this hardware??? > >hdds are more than 50 years old!! >It has been invented in 1953 by some guy at IBM. > > > >>-----Message d'origine----- >>De : owner-freebsd-hardware@freebsd.org >>[mailto:owner-freebsd-hardware@freebsd.org]De la part de Gayn Winters >>Envoye : mardi 13 decembre 2005 19:43 >>A : 'Alexandre DELAY'; freebsd-hardware@freebsd.org >>Objet : RE: HDD >> >> >> >> >>>-----Original Message----- >>>From: owner-freebsd-hardware@freebsd.org >>>[mailto:owner-freebsd-hardware@freebsd.org] On Behalf Of >>>Alexandre DELAY >>>Sent: Tuesday, December 13, 2005 9:39 AM >>>To: freebsd-hardware@freebsd.org >>>Subject: HDD >>> >>> >>>Hi guys, >>> >>>I would like to know what you think of hard drive disk running under >>>FreeBSD. The fact is that it is quite difficult to keep it working >>>with "hard power off". I added a small fsck_enable="YES" in my rc.conf >>> >>> >>file, >> >> >>>but my system keeps have some trouble when the power fails. >>> >>>Is there a way to make FreeBSD running very well with power failure? >>>I thought of Compact flash cards as system disk. Do you think >>>it would make the system more stable with power failure? >>> >>> >>Use a UPS. >> >>-gayn >> >>Bristol Systems Inc. >>714/532-6776 >>www.bristolsystems.com >> >> >>_______________________________________________ >>freebsd-hardware@freebsd.org mailing list >>http://lists.freebsd.org/mailman/listinfo/freebsd-hardware >>To unsubscribe, send any mail to >>"freebsd-hardware-unsubscribe@freebsd.org" >> >> >> >_______________________________________________ >freebsd-hardware@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-hardware >To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" > > > > From owner-freebsd-hardware@FreeBSD.ORG Wed Dec 14 16:45:43 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EE3CA16A41F for ; Wed, 14 Dec 2005 16:45:42 +0000 (GMT) (envelope-from alexandre.delay@free.fr) Received: from smtp1-g19.free.fr (smtp1-g19.free.fr [212.27.42.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5563343D55 for ; Wed, 14 Dec 2005 16:45:42 +0000 (GMT) (envelope-from alexandre.delay@free.fr) Received: from Cerbere-de-Troyes.cerbere23.com (eur10-1-82-241-181-23.fbx.proxad.net [82.241.181.23]) by smtp1-g19.free.fr (Postfix) with ESMTP id D391B68E68; Wed, 14 Dec 2005 17:45:40 +0100 (CET) Received: from artemis ([192.168.2.2]) by Cerbere-de-Troyes.cerbere23.com (8.13.3/8.13.3) with SMTP id jBEGjdnt030838; Wed, 14 Dec 2005 17:45:40 +0100 (CET) (envelope-from alexandre.delay@free.fr) From: "Alexandre DELAY" To: "Alexandre DELAY" Date: Wed, 14 Dec 2005 17:45:53 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <439F7AF3.7000709@vault-tec.de> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal Cc: freebsd-hardware@freebsd.org Subject: RE: HDD X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 16:45:43 -0000 Don't you think that flash drives are also a good solution? I am sure that it will be the future replacement for hard drive disks. see http://www.memtech.com/ for example With no buffer and 1ms access delay you minimise write failures. It is an interresting solution. cheers > -----Message d'origine----- > De : owner-freebsd-hardware@freebsd.org > [mailto:owner-freebsd-hardware@freebsd.org]De la part de Wolfram Huesken > Envoyé : mercredi 14 décembre 2005 02:53 > À : Alexandre DELAY > Cc : freebsd-hardware@freebsd.org > Objet : Re: HDD > > > You could mount the filesystem as read-only and use a ramdisk for the > partitions that need write access > like /tmp or /var. > You also would prevent your CF-Card from damage because you cannot > perform unlimited io operations on that card. > > I've already tested this with a kind of embedded appliance that acts as > a router. > > - Wolfram > > Alexandre DELAY wrote: > > >he he! > >nice answer! > > > >The fact is that it is not exactly my question. > >You think it is normal that nowdays we are limited by this hardware??? > > > >hdds are more than 50 years old!! > >It has been invented in 1953 by some guy at IBM. > > > > > > > >>-----Message d'origine----- > >>De : owner-freebsd-hardware@freebsd.org > >>[mailto:owner-freebsd-hardware@freebsd.org]De la part de Gayn Winters > >>Envoye : mardi 13 decembre 2005 19:43 > >>A : 'Alexandre DELAY'; freebsd-hardware@freebsd.org > >>Objet : RE: HDD > >> > >> > >> > >> > >>>-----Original Message----- > >>>From: owner-freebsd-hardware@freebsd.org > >>>[mailto:owner-freebsd-hardware@freebsd.org] On Behalf Of > >>>Alexandre DELAY > >>>Sent: Tuesday, December 13, 2005 9:39 AM > >>>To: freebsd-hardware@freebsd.org > >>>Subject: HDD > >>> > >>> > >>>Hi guys, > >>> > >>>I would like to know what you think of hard drive disk running under > >>>FreeBSD. The fact is that it is quite difficult to keep it working > >>>with "hard power off". I added a small fsck_enable="YES" in my rc.conf > >>> > >>> > >>file, > >> > >> > >>>but my system keeps have some trouble when the power fails. > >>> > >>>Is there a way to make FreeBSD running very well with power failure? > >>>I thought of Compact flash cards as system disk. Do you think > >>>it would make the system more stable with power failure? > >>> > >>> > >>Use a UPS. > >> > >>-gayn > >> > >>Bristol Systems Inc. > >>714/532-6776 > >>www.bristolsystems.com > >> > >> > >>_______________________________________________ > >>freebsd-hardware@freebsd.org mailing list > >>http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > >>To unsubscribe, send any mail to > >>"freebsd-hardware-unsubscribe@freebsd.org" > >> > >> > >> > >_______________________________________________ > >freebsd-hardware@freebsd.org mailing list > >http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > >To unsubscribe, send any mail to > "freebsd-hardware-unsubscribe@freebsd.org" > > > > > > > > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to > "freebsd-hardware-unsubscribe@freebsd.org" > From owner-freebsd-hardware@FreeBSD.ORG Wed Dec 14 16:48:09 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1460616A41F for ; Wed, 14 Dec 2005 16:48:09 +0000 (GMT) (envelope-from alexandre.delay@free.fr) Received: from smtp1-g19.free.fr (smtp1-g19.free.fr [212.27.42.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id B56D943D58 for ; Wed, 14 Dec 2005 16:48:07 +0000 (GMT) (envelope-from alexandre.delay@free.fr) Received: from Cerbere-de-Troyes.cerbere23.com (eur10-1-82-241-181-23.fbx.proxad.net [82.241.181.23]) by smtp1-g19.free.fr (Postfix) with ESMTP id 0FBAF64953; Wed, 14 Dec 2005 17:48:06 +0100 (CET) Received: from artemis ([192.168.2.2]) by Cerbere-de-Troyes.cerbere23.com (8.13.3/8.13.3) with SMTP id jBEGm6v1030884; Wed, 14 Dec 2005 17:48:06 +0100 (CET) (envelope-from alexandre.delay@free.fr) From: "Alexandre DELAY" To: "Randy Bush" , Date: Wed, 14 Dec 2005 17:48:19 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <17311.26823.195210.842876@roam.psg.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal Cc: Subject: RE: HDD X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 16:48:09 -0000 I was saying "hardware" thinking "technology". I think hdd magnetic technology is obsolete. see what happened with floppy disks replaced by optical disks and then take a look at http://www.memtech.com/ for flash drives. > -----Message d'origine----- > De : Randy Bush [mailto:randy@psg.com] > Envoye : mercredi 14 decembre 2005 01:35 > A : Alexandre DELAY > Cc : freebsd-hardware@freebsd.org > Objet : RE: HDD > > > > You think it is normal that nowdays we are limited by this hardware??? > > not at all. at least not if you don't want to use computers. i am > sure some of us have slide rules we might be willing to sell. though > they had hardware problems too, required alignment, are hard to see > in the dark (when power is out), etc. > > good luck in your fantasy world. > > randy > > From owner-freebsd-hardware@FreeBSD.ORG Thu Dec 15 01:53:12 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 00D1916A41F for ; Thu, 15 Dec 2005 01:53:12 +0000 (GMT) (envelope-from freebsd@sopwith.solgatos.com) Received: from schitzo.solgatos.com (c-67-168-241-176.hsd1.or.comcast.net [67.168.241.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8CDCF43D53 for ; Thu, 15 Dec 2005 01:53:11 +0000 (GMT) (envelope-from freebsd@sopwith.solgatos.com) Received: from sopwith.solgatos.com (uucp@localhost) by schitzo.solgatos.com (8.11.6/8.11.6) with UUCP id jBF1rMG02442 for freebsd-hardware@freebsd.org; Wed, 14 Dec 2005 17:53:22 -0800 Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id BAA02846; Thu, 15 Dec 2005 01:52:01 GMT Message-Id: <200512150152.BAA02846@sopwith.solgatos.com> To: freebsd-hardware@freebsd.org Date: Wed, 14 Dec 2005 17:52:01 +0000 From: Dieter Subject: HDD X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd@sopwith.solgatos.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 01:53:12 -0000 > Is there a way to make FreeBSD running very well with power failure? Add hw.ata.wc=0 to /boot/loader.conf (assuming SATA or PATA drives) and reboot. Add -U flag to newfs when making a new ffs. Add a UPS to your power cord. Mount filesystems read-only when possible. (e.g. /usr ) From owner-freebsd-hardware@FreeBSD.ORG Thu Dec 15 02:57:04 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 061C316A41F for ; Thu, 15 Dec 2005 02:57:04 +0000 (GMT) (envelope-from bob@immure.com) Received: from ylpvm43.prodigy.net (ylpvm43-ext.prodigy.net [207.115.57.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id A0DD643D55 for ; Thu, 15 Dec 2005 02:57:02 +0000 (GMT) (envelope-from bob@immure.com) Received: from pimout1-ext.prodigy.net (pimout1-int.prodigy.net [207.115.5.65]) by ylpvm43.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id jBF2v1ap016128 for ; Wed, 14 Dec 2005 21:57:01 -0500 X-ORBL: [66.136.206.1] Received: from maul.immure.com (adsl-66-136-206-1.dsl.austtx.swbell.net [66.136.206.1]) by pimout1-ext.prodigy.net (8.13.4 outbound domainkey aix/8.13.4) with ESMTP id jBF2v0Hj066518; Wed, 14 Dec 2005 21:57:00 -0500 Received: from rancor.immure.com (rancor.immure.com [10.1.132.9]) by maul.immure.com (8.13.4/8.13.4) with ESMTP id jBF2us12092185; Wed, 14 Dec 2005 20:56:54 -0600 (CST) (envelope-from bob@immure.com) Received: from rancor.immure.com (localhost.immure.com [127.0.0.1]) by rancor.immure.com (8.13.4/8.13.4) with ESMTP id jBF2uroV035520; Wed, 14 Dec 2005 20:56:53 -0600 (CST) (envelope-from bob@rancor.immure.com) Received: (from bob@localhost) by rancor.immure.com (8.13.4/8.13.1/Submit) id jBF2ur0Q035519; Wed, 14 Dec 2005 20:56:53 -0600 (CST) (envelope-from bob) Date: Wed, 14 Dec 2005 20:56:53 -0600 From: Bob Willcox To: Alexandre DELAY Message-ID: <20051215025653.GA35383@rancor.immure.com> References: <439F7AF3.7000709@vault-tec.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 X-immure-MailScanner-Information: Please contact the ISP for more information X-immure-MailScanner: Found to be clean X-MailScanner-From: bob@immure.com Cc: freebsd-hardware@freebsd.org Subject: Re: HDD X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Bob Willcox List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 02:57:04 -0000 On Wed, Dec 14, 2005 at 05:45:53PM +0100, Alexandre DELAY wrote: > Don't you think that flash drives are also a good solution? > > I am sure that it will be the future replacement for hard drive disks. > see http://www.memtech.com/ for example > > With no buffer and 1ms access delay you minimise write failures. It is an > interresting solution. Hmm, I see no prices listed on the Memtech web site (did I simply miss them?). So, what does a 96GB flash drive cost in comparison to a magnetic disk hard drive of similar capacity? Stories of the impending demise of magnetic disk drives have been circulating since at least the late '70s (back then I seem to remember that bubble and/or CCD memory was to spell their doom). So far, it appears that nothing has come along that has been able to compete on a cost per byte basis. Flash memory might be the technology to do it, but somehow I doubt it. Bob > > cheers > > > -----Message d'origine----- > > De : owner-freebsd-hardware@freebsd.org > > [mailto:owner-freebsd-hardware@freebsd.org]De la part de Wolfram Huesken > > Envoy? : mercredi 14 d?cembre 2005 02:53 > > ? : Alexandre DELAY > > Cc : freebsd-hardware@freebsd.org > > Objet : Re: HDD > > > > > > You could mount the filesystem as read-only and use a ramdisk for the > > partitions that need write access > > like /tmp or /var. > > You also would prevent your CF-Card from damage because you cannot > > perform unlimited io operations on that card. > > > > I've already tested this with a kind of embedded appliance that acts as > > a router. > > > > - Wolfram > > > > Alexandre DELAY wrote: > > > > >he he! > > >nice answer! > > > > > >The fact is that it is not exactly my question. > > >You think it is normal that nowdays we are limited by this hardware??? > > > > > >hdds are more than 50 years old!! > > >It has been invented in 1953 by some guy at IBM. > > > > > > > > > > > >>-----Message d'origine----- > > >>De : owner-freebsd-hardware@freebsd.org > > >>[mailto:owner-freebsd-hardware@freebsd.org]De la part de Gayn Winters > > >>Envoye : mardi 13 decembre 2005 19:43 > > >>A : 'Alexandre DELAY'; freebsd-hardware@freebsd.org > > >>Objet : RE: HDD > > >> > > >> > > >> > > >> > > >>>-----Original Message----- > > >>>From: owner-freebsd-hardware@freebsd.org > > >>>[mailto:owner-freebsd-hardware@freebsd.org] On Behalf Of > > >>>Alexandre DELAY > > >>>Sent: Tuesday, December 13, 2005 9:39 AM > > >>>To: freebsd-hardware@freebsd.org > > >>>Subject: HDD > > >>> > > >>> > > >>>Hi guys, > > >>> > > >>>I would like to know what you think of hard drive disk running under > > >>>FreeBSD. The fact is that it is quite difficult to keep it working > > >>>with "hard power off". I added a small fsck_enable="YES" in my rc.conf > > >>> > > >>> > > >>file, > > >> > > >> > > >>>but my system keeps have some trouble when the power fails. > > >>> > > >>>Is there a way to make FreeBSD running very well with power failure? > > >>>I thought of Compact flash cards as system disk. Do you think > > >>>it would make the system more stable with power failure? > > >>> > > >>> > > >>Use a UPS. > > >> > > >>-gayn > > >> > > >>Bristol Systems Inc. > > >>714/532-6776 > > >>www.bristolsystems.com > > >> > > >> > > >>_______________________________________________ > > >>freebsd-hardware@freebsd.org mailing list > > >>http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > > >>To unsubscribe, send any mail to > > >>"freebsd-hardware-unsubscribe@freebsd.org" > > >> > > >> > > >> > > >_______________________________________________ > > >freebsd-hardware@freebsd.org mailing list > > >http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > > >To unsubscribe, send any mail to > > "freebsd-hardware-unsubscribe@freebsd.org" > > > > > > > > > > > > > > _______________________________________________ > > freebsd-hardware@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > > To unsubscribe, send any mail to > > "freebsd-hardware-unsubscribe@freebsd.org" > > > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" -- Bob Willcox Men freely believe that what they wish to desire. bob@immure.com -- Julius Caesar Austin, TX From owner-freebsd-hardware@FreeBSD.ORG Thu Dec 15 09:44:25 2005 Return-Path: X-Original-To: hardware@freebsd.org Delivered-To: freebsd-hardware@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE93316A41F; Thu, 15 Dec 2005 09:44:25 +0000 (GMT) (envelope-from wsk@gddsn.org.cn) Received: from gddsn.org.cn (gddsn.org.cn [218.19.164.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id AEC3843D53; Thu, 15 Dec 2005 09:44:24 +0000 (GMT) (envelope-from wsk@gddsn.org.cn) Received: from [192.168.168.138] (unknown [192.168.168.138]) by gddsn.org.cn (Postfix) with ESMTP id 66B1A38CB41; Thu, 15 Dec 2005 17:44:22 +0800 (CST) Message-ID: <43A13AF6.90003@gddsn.org.cn> Date: Thu, 15 Dec 2005 17:44:22 +0800 From: wsk User-Agent: Thunderbird 1.5 (X11/20051128) MIME-Version: 1.0 To: current@freebsd.org, hardware@freebsd.org, stable@freebsd.org Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: 7bit Cc: Subject: Can support Intel's E8500 chipset on freebsd??? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 09:44:26 -0000 lists: with DELL PE6850, It seems 6.0 Can't support the Intel's E8500 XMB chipset pciconf -lv: none0@pci0:9:0: class=0x050000 card=0x01701028 chip=0x26208086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'E8500 XMB A/B/C/D Identification Registers' class = memory subclass = RAM none1@pci0:9:1: class=0x050000 card=0x01701028 chip=0x26218086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'E8500 XMB A/B/C/D Miscellaneous Registers' class = memory subclass = RAM none2@pci0:9:2: class=0x050000 card=0x01701028 chip=0x26228086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'E8500 XMB A/B/C/D Memory Interleaving Registers' class = memory subclass = RAM dmesg: %dmesg Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-RELEASE #0: Fri Dec 16 00:54:34 CST 2005 wsk@wfdb2.gddsn.org.cn:/usr/obj/usr/src/sys/WFDB2 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) MP CPU 3.00GHz (2995.52-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0xf41 Stepping = 1 Features=0xbfebfbff Features2=0x659d> AMD Features=0x20100800 real memory = 9395240960 (8960 MB) avail memory = 8288649216 (7904 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 6 cpu2 (AP): APIC ID: 8 cpu3 (AP): APIC ID: 14 ioapic1: Changing APIC ID to 1 ioapic1: WARNING: intbase 32 != expected base 24 ioapic2: Changing APIC ID to 2 ioapic2: WARNING: intbase 64 != expected base 56 ioapic3: Changing APIC ID to 3 ioapic3: WARNING: intbase 96 != expected base 88 ioapic4: Changing APIC ID to 4 ioapic4: WARNING: intbase 128 != expected base 120 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 32-55 on motherboard ioapic2 irqs 64-87 on motherboard ioapic3 irqs 96-119 on motherboard ioapic4 irqs 128-151 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) pci_link0: irq 11 on acpi0 pci_link1: irq 11 on acpi0 pci_link2: irq 5 on acpi0 pci_link3: irq 10 on acpi0 pci_link4: on acpi0 pci_link5: on acpi0 pci_link6: on acpi0 pci_link7: irq 3 on acpi0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pcib2: at device 2.0 on pci0 pci4: on pcib2 pcib3: at device 3.0 on pci0 pci7: on pcib3 pcib4: at device 4.0 on pci0 pci8: on pcib4 pcib5: at device 5.0 on pci0 pci11: on pcib5 pcib6: at device 6.0 on pci0 pci14: on pcib6 pcib7: mem 0xdf6ff000-0xdf6fffff at device 0.0 on pci14 pci15: on pcib7 pcib8: at device 0.2 on pci14 pci18: on pcib8 bge0: mem 0xdf8f0000-0xdf8fffff irq 64 at device 2.0 on pci18 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:12:3f:ff:81:47 bge1: mem 0xdf8e0000-0xdf8effff irq 65 at device 2.1 on pci18 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:12:3f:ff:81:48 pcib9: at device 7.0 on pci0 pci19: on pcib9 pcib10: at device 0.0 on pci19 pci20: on pcib10 amr0: mem 0xdd0f0000-0xdd0fffff,0xdf4c0000-0xdf4fffff irq 110 at device 14.0 on pci20 amr0: Firmware 521S, BIOS H430, 256MB RAM pcib11: at device 0.2 on pci19 pci21: on pcib11 pci0: at device 9.0 (no driver attached) pci0: at device 9.1 (no driver attached) pci0: at device 9.2 (no driver attached) pci0: at device 9.3 (no driver attached) pci0: at device 9.4 (no driver attached) pci0: at device 9.5 (no driver attached) pci0: at device 9.6 (no driver attached) pci0: at device 9.7 (no driver attached) pci0: at device 11.0 (no driver attached) pci0: at device 11.1 (no driver attached) pci0: at device 11.2 (no driver attached) pci0: at device 11.3 (no driver attached) pci0: at device 11.4 (no driver attached) pci0: at device 11.5 (no driver attached) pci0: at device 11.6 (no driver attached) pci0: at device 11.7 (no driver attached) pci0: at device 13.0 (no driver attached) pci0: at device 13.1 (no driver attached) pci0: at device 13.2 (no driver attached) pci0: at device 13.3 (no driver attached) pci0: at device 13.4 (no driver attached) pci0: at device 13.5 (no driver attached) pci0: at device 13.6 (no driver attached) pci0: at device 13.7 (no driver attached) pci0: at device 15.0 (no driver attached) pci0: at device 15.1 (no driver attached) pci0: at device 15.2 (no driver attached) pci0: at device 15.3 (no driver attached) pci0: at device 15.4 (no driver attached) pci0: at device 15.5 (no driver attached) pci0: at device 15.6 (no driver attached) pci0: at device 15.7 (no driver attached) uhci0: port 0x6ce0-0x6cff irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x6cc0-0x6cdf irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x6ca0-0x6cbf irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xdff00000-0xdff003ff irq 23 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub3: 6 ports with 6 removable, self powered uhub4: vendor 0x413c product 0xa001, class 9/0, rev 2.00/0.00, addr 2 uhub4: multiple transaction translators uhub4: 2 ports with 2 removable, self powered pcib12: at device 30.0 on pci0 pci22: on pcib12 pci22: at device 0.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A orm0: at iomem 0xc0000-0xc9fff,0xca000-0xcafff,0xcb000-0xcc7ff,0xec000-0xeffff on isa0 atkbdc0: at port 0x60,0x64 on isa0 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ums0: vendor 0x413c product 0x3010, rev 2.00/2.20, addr 2, iclass 3/1 ums0: 3 buttons and Z dir. ukbd0: Dell Dell USB Keyboard, rev 1.10/2.00, addr 3, iclass 3/1 kbd0 at ukbd0 Timecounters tick every 1.000 msec acd0: DVDROM at ata0-master UDMA33 amrd0: on amr0 amrd0: 1144320MB (2343567360 sectors) RAID 5 (optimal) ses0 at amr0 bus 0 target 6 lun 0 ses0: Fixed Processor SCSI-2 device ses0: SAF-TE Compliant Device SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #3 Launched! Trying to mount root from ufs:/dev/amrd0s1a bge0: link state changed to UP any ideas?? TIA From owner-freebsd-hardware@FreeBSD.ORG Thu Dec 15 09:58:14 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 726D316A41F for ; Thu, 15 Dec 2005 09:58:14 +0000 (GMT) (envelope-from ragnar@gatorhole.se) Received: from mail.packetfront.com (mail.packetfront.com [212.247.6.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE9FA43D45 for ; Thu, 15 Dec 2005 09:58:13 +0000 (GMT) (envelope-from ragnar@gatorhole.se) Received: from localhost (localhost [127.0.0.1]) by mail.packetfront.com (Postfix) with ESMTP id C3DA2A3FBB; Thu, 15 Dec 2005 10:58:11 +0100 (CET) Received: from mail.packetfront.com ([127.0.0.1]) by localhost (mail [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 22129-03; Thu, 15 Dec 2005 10:58:11 +0100 (CET) Received: from [192.168.1.159] (unknown [192.168.1.159]) by mail.packetfront.com (Postfix) with ESMTP id 84DA9A3FB7; Thu, 15 Dec 2005 10:58:11 +0100 (CET) Message-ID: <43A13E1B.9060106@gatorhole.se> Date: Thu, 15 Dec 2005 10:57:48 +0100 From: Ragnar Lonn Organization: Packetfront User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bob Willcox References: <439F7AF3.7000709@vault-tec.de> <20051215025653.GA35383@rancor.immure.com> In-Reply-To: <20051215025653.GA35383@rancor.immure.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at packetfront.com Cc: Alexandre DELAY , freebsd-hardware@freebsd.org Subject: Re: HDD X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 09:58:14 -0000 Bob Willcox wrote: >On Wed, Dec 14, 2005 at 05:45:53PM +0100, Alexandre DELAY wrote: > > >>Don't you think that flash drives are also a good solution? >> >>I am sure that it will be the future replacement for hard drive disks. >>see http://www.memtech.com/ for example >> >>With no buffer and 1ms access delay you minimise write failures. It is an >>interresting solution. >> >> > >Hmm, I see no prices listed on the Memtech web site (did I simply >miss them?). So, what does a 96GB flash drive cost in comparison to a >magnetic disk hard drive of similar capacity? > >Stories of the impending demise of magnetic disk drives have been >circulating since at least the late '70s (back then I seem to remember >that bubble and/or CCD memory was to spell their doom). So far, it >appears that nothing has come along that has been able to compete on a >cost per byte basis. Flash memory might be the technology to do it, but >somehow I doubt it. > > I like to build silent PCs on my spare time and avoiding any moving parts is of course a good way to achieve this goal. This makes me very interested in any memory-based hard disk replacements but so far, they seem to be hideously expensive. You have to pay over $1000 for 8 GB of storage. Multiply that with 10 or so and you're likely to have the cost of that 96GB flash drive. I too thought that memory disks would take over some five years ago or so, but conventional hard disk technology has managed to stay ahead all the time, providing lots more storage per dollar and often also throughput rates almost matching that of the solid state memories. I think we will see a shift sometime, but I've stopped trying to predict it. Hard disk technology has such a big lead that it may take a while yet, I think. /Ragnar From owner-freebsd-hardware@FreeBSD.ORG Thu Dec 15 14:51:58 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 99EFA16A41F; Thu, 15 Dec 2005 14:51:58 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B32043D49; Thu, 15 Dec 2005 14:51:57 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3864196 for multiple; Thu, 15 Dec 2005 09:49:56 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jBFEpqRv069483; Thu, 15 Dec 2005 09:51:52 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hardware@freebsd.org Date: Thu, 15 Dec 2005 09:52:20 -0500 User-Agent: KMail/1.8.2 References: <43A13AF6.90003@gddsn.org.cn> In-Reply-To: <43A13AF6.90003@gddsn.org.cn> MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512150952.22302.jhb@freebsd.org> X-Virus-Scanned: ClamAV version 0.87.1, clamav-milter version 0.87 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: stable@freebsd.org, current@freebsd.org, wsk , hardware@freebsd.org Subject: Re: Can support Intel's E8500 chipset on freebsd??? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 14:51:58 -0000 On Thursday 15 December 2005 04:44 am, wsk wrote: > lists: > with DELL PE6850, It seems 6.0 Can't support the > Intel's E8500 XMB chipset What doesn't work? > pciconf -lv: > none0@pci0:9:0: class=0x050000 card=0x01701028 chip=0x26208086 rev=0x00 > hdr=0x00 > vendor = 'Intel Corporation' > device = 'E8500 XMB A/B/C/D Identification Registers' > class = memory > subclass = RAM These types of devices don't need a driver to work. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-hardware@FreeBSD.ORG Thu Dec 15 14:51:58 2005 Return-Path: X-Original-To: hardware@freebsd.org Delivered-To: freebsd-hardware@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 99EFA16A41F; Thu, 15 Dec 2005 14:51:58 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B32043D49; Thu, 15 Dec 2005 14:51:57 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3864196 for multiple; Thu, 15 Dec 2005 09:49:56 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jBFEpqRv069483; Thu, 15 Dec 2005 09:51:52 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hardware@freebsd.org Date: Thu, 15 Dec 2005 09:52:20 -0500 User-Agent: KMail/1.8.2 References: <43A13AF6.90003@gddsn.org.cn> In-Reply-To: <43A13AF6.90003@gddsn.org.cn> MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512150952.22302.jhb@freebsd.org> X-Virus-Scanned: ClamAV version 0.87.1, clamav-milter version 0.87 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: stable@freebsd.org, current@freebsd.org, wsk , hardware@freebsd.org Subject: Re: Can support Intel's E8500 chipset on freebsd??? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 14:51:58 -0000 On Thursday 15 December 2005 04:44 am, wsk wrote: > lists: > with DELL PE6850, It seems 6.0 Can't support the > Intel's E8500 XMB chipset What doesn't work? > pciconf -lv: > none0@pci0:9:0: class=0x050000 card=0x01701028 chip=0x26208086 rev=0x00 > hdr=0x00 > vendor = 'Intel Corporation' > device = 'E8500 XMB A/B/C/D Identification Registers' > class = memory > subclass = RAM These types of devices don't need a driver to work. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-hardware@FreeBSD.ORG Thu Dec 15 17:48:04 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDB3616A423 for ; Thu, 15 Dec 2005 17:48:04 +0000 (GMT) (envelope-from alexandre.delay@free.fr) Received: from smtp3-g19.free.fr (smtp3-g19.free.fr [212.27.42.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id A880943D6B for ; Thu, 15 Dec 2005 17:47:40 +0000 (GMT) (envelope-from alexandre.delay@free.fr) Received: from Cerbere-de-Troyes.cerbere23.com (eur10-1-82-241-181-23.fbx.proxad.net [82.241.181.23]) by smtp3-g19.free.fr (Postfix) with ESMTP id A9F5144115; Thu, 15 Dec 2005 18:47:37 +0100 (CET) Received: from artemis ([192.168.2.2]) by Cerbere-de-Troyes.cerbere23.com (8.13.3/8.13.3) with SMTP id jBFHlVZB078070; Thu, 15 Dec 2005 18:47:31 +0100 (CET) (envelope-from alexandre.delay@free.fr) From: "Alexandre DELAY" To: "Ragnar Lonn" , "Bob Willcox" Date: Thu, 15 Dec 2005 18:47:49 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 In-Reply-To: <43A13E1B.9060106@gatorhole.se> Cc: freebsd-hardware@freebsd.org Subject: RE: HDD X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 17:48:05 -0000 The only prices I found about this kind of product is at: http://www.psism.com/flashdrive.htm It is still expensive, but when I see the price of last year's usb flash disks compared to todays, the ratio is 1/2. I bet this will follow usb drives prices. I'm happy to see that some people are interrested by this topic. cheers > -----Message d'origine----- > De : owner-freebsd-hardware@freebsd.org > [mailto:owner-freebsd-hardware@freebsd.org]De la part de Ragnar Lonn > Envoyé : jeudi 15 décembre 2005 10:58 > À : Bob Willcox > Cc : Alexandre DELAY; freebsd-hardware@freebsd.org > Objet : Re: HDD > > > Bob Willcox wrote: > > >On Wed, Dec 14, 2005 at 05:45:53PM +0100, Alexandre DELAY wrote: > > > > > >>Don't you think that flash drives are also a good solution? > >> > >>I am sure that it will be the future replacement for hard drive disks. > >>see http://www.memtech.com/ for example > >> > >>With no buffer and 1ms access delay you minimise write > failures. It is an > >>interresting solution. > >> > >> > > > >Hmm, I see no prices listed on the Memtech web site (did I simply > >miss them?). So, what does a 96GB flash drive cost in comparison to a > >magnetic disk hard drive of similar capacity? > > > >Stories of the impending demise of magnetic disk drives have been > >circulating since at least the late '70s (back then I seem to remember > >that bubble and/or CCD memory was to spell their doom). So far, it > >appears that nothing has come along that has been able to compete on a > >cost per byte basis. Flash memory might be the technology to do it, but > >somehow I doubt it. > > > > > > I like to build silent PCs on my spare time and avoiding any moving > parts is of course > a good way to achieve this goal. This makes me very interested in any > memory-based > hard disk replacements but so far, they seem to be hideously expensive. > You have to > pay over $1000 for 8 GB of storage. Multiply that with 10 or so and > you're likely > to have the cost of that 96GB flash drive. > > I too thought that memory disks would take over some five years ago or > so, but > conventional hard disk technology has managed to stay ahead all the > time, providing > lots more storage per dollar and often also throughput rates almost > matching that > of the solid state memories. I think we will see a shift sometime, but > I've stopped > trying to predict it. Hard disk technology has such a big lead that it > may take a > while yet, I think. > > /Ragnar > > > > > > > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to > "freebsd-hardware-unsubscribe@freebsd.org" > From owner-freebsd-hardware@FreeBSD.ORG Thu Dec 15 20:03:59 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED90B16A41F for ; Thu, 15 Dec 2005 20:03:59 +0000 (GMT) (envelope-from bob@immure.com) Received: from pimout4-ext.prodigy.net (pimout4-ext.prodigy.net [207.115.63.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE2E043D62 for ; Thu, 15 Dec 2005 20:03:58 +0000 (GMT) (envelope-from bob@immure.com) X-ORBL: [66.136.206.1] Received: from maul.immure.com (adsl-66-136-206-1.dsl.austtx.swbell.net [66.136.206.1]) by pimout4-ext.prodigy.net (8.13.4 outbound domainkey aix/8.13.4) with ESMTP id jBFJvpoo143470; Thu, 15 Dec 2005 14:57:56 -0500 Received: from rancor.immure.com (rancor.immure.com [10.1.132.9]) by maul.immure.com (8.13.4/8.13.4) with ESMTP id jBFJvkWC006936; Thu, 15 Dec 2005 13:57:46 -0600 (CST) (envelope-from bob@immure.com) Received: from rancor.immure.com (localhost.immure.com [127.0.0.1]) by rancor.immure.com (8.13.4/8.13.4) with ESMTP id jBFJvkGr040161; Thu, 15 Dec 2005 13:57:46 -0600 (CST) (envelope-from bob@rancor.immure.com) Received: (from bob@localhost) by rancor.immure.com (8.13.4/8.13.1/Submit) id jBFJvkPO040160; Thu, 15 Dec 2005 13:57:46 -0600 (CST) (envelope-from bob) Date: Thu, 15 Dec 2005 13:57:46 -0600 From: Bob Willcox To: Alexandre DELAY Message-ID: <20051215195746.GA39959@rancor.immure.com> References: <43A13E1B.9060106@gatorhole.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 X-immure-MailScanner-Information: Please contact the ISP for more information X-immure-MailScanner: Found to be clean X-MailScanner-From: bob@immure.com Cc: Ragnar Lonn , freebsd-hardware@freebsd.org Subject: Re: HDD X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Bob Willcox List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 20:04:00 -0000 On Thu, Dec 15, 2005 at 06:47:49PM +0100, Alexandre DELAY wrote: > The only prices I found about this kind of product is at: > http://www.psism.com/flashdrive.htm > > It is still expensive, but when I see the price of last year's usb flash > disks compared to todays, the ratio is 1/2. I bet this will follow usb > drives prices. Well, there's the rub. It will take a lot of price halvings for flash drives to even get close. If you take ZipZoomFly as a typical online retailer, they are selling 400GB IDE drives for $251 and 4GB flash drives for $236. That works out to $0.63/GB for the hard disk and $59/GB for the flash drive. This represents a ratio of almost 94:1. I think it will be a long time before flash drives can make up that price differential, and during that time hard drive capacities will likely continue to increase and their cost per GB continue to fall. It's been this way for the 30 years that I've been watching it, and I don't see any likely reason for that to change anytime soon. Of course, there are applications where flash memory drives have distinct advantages (e.g. portable devices), but for mainstream data storage, I don't see any real threat to hard drive technology in the foreseeable future. Bob > > I'm happy to see that some people are interrested by this topic. > > cheers > > > -----Message d'origine----- > > De : owner-freebsd-hardware@freebsd.org > > [mailto:owner-freebsd-hardware@freebsd.org]De la part de Ragnar Lonn > > Envoy? : jeudi 15 d?cembre 2005 10:58 > > ? : Bob Willcox > > Cc : Alexandre DELAY; freebsd-hardware@freebsd.org > > Objet : Re: HDD > > > > > > Bob Willcox wrote: > > > > >On Wed, Dec 14, 2005 at 05:45:53PM +0100, Alexandre DELAY wrote: > > > > > > > > >>Don't you think that flash drives are also a good solution? > > >> > > >>I am sure that it will be the future replacement for hard drive disks. > > >>see http://www.memtech.com/ for example > > >> > > >>With no buffer and 1ms access delay you minimise write > > failures. It is an > > >>interresting solution. > > >> > > >> > > > > > >Hmm, I see no prices listed on the Memtech web site (did I simply > > >miss them?). So, what does a 96GB flash drive cost in comparison to a > > >magnetic disk hard drive of similar capacity? > > > > > >Stories of the impending demise of magnetic disk drives have been > > >circulating since at least the late '70s (back then I seem to remember > > >that bubble and/or CCD memory was to spell their doom). So far, it > > >appears that nothing has come along that has been able to compete on a > > >cost per byte basis. Flash memory might be the technology to do it, but > > >somehow I doubt it. > > > > > > > > > > I like to build silent PCs on my spare time and avoiding any moving > > parts is of course > > a good way to achieve this goal. This makes me very interested in any > > memory-based > > hard disk replacements but so far, they seem to be hideously expensive. > > You have to > > pay over $1000 for 8 GB of storage. Multiply that with 10 or so and > > you're likely > > to have the cost of that 96GB flash drive. > > > > I too thought that memory disks would take over some five years ago or > > so, but > > conventional hard disk technology has managed to stay ahead all the > > time, providing > > lots more storage per dollar and often also throughput rates almost > > matching that > > of the solid state memories. I think we will see a shift sometime, but > > I've stopped > > trying to predict it. Hard disk technology has such a big lead that it > > may take a > > while yet, I think. > > > > /Ragnar > > > > > > > > > > > > > > > > _______________________________________________ > > freebsd-hardware@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > > To unsubscribe, send any mail to > > "freebsd-hardware-unsubscribe@freebsd.org" > > -- Bob Willcox Men freely believe that what they wish to desire. bob@immure.com -- Julius Caesar Austin, TX From owner-freebsd-hardware@FreeBSD.ORG Fri Dec 16 03:37:06 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 01F6116A41F for ; Fri, 16 Dec 2005 03:37:06 +0000 (GMT) (envelope-from jakub.laszczynski@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8ED4D43D5E for ; Fri, 16 Dec 2005 03:37:05 +0000 (GMT) (envelope-from jakub.laszczynski@gmail.com) Received: by zproxy.gmail.com with SMTP id i1so614522nzh for ; Thu, 15 Dec 2005 19:37:04 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=gaAbqot4Jhm07TV54h1TlXENUqKCnKknrNm8zKAMdqXj6vy5JM/uRO5MgoKkW+KhtK/CpPSNynV01xarDOPfG8E5CHB57frfq/X0LYtWHkgLUB9Vf/XiKu1qU1InHzYT1XuDVO26DGeUImHQgOaugQ3pOEaEjD9BNRc3HC9PojQ= Received: by 10.64.232.18 with SMTP id e18mr1782478qbh; Thu, 15 Dec 2005 19:37:04 -0800 (PST) Received: by 10.64.213.8 with HTTP; Thu, 15 Dec 2005 19:37:04 -0800 (PST) Message-ID: Date: Fri, 16 Dec 2005 04:37:04 +0100 From: =?ISO-8859-2?Q?Jakub_=A3aszczy=F1ski?= To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: problems with usb keyboard X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 03:37:06 -0000 hi. i'm doubling this post, couse anyone couldn't help me on freebsd-stable. i bought recently an usb keyboard. but when i connected it and started up fbsd-6.0-stable(ukbd is in kernel). when i tried to login, and enter my log/pass, it just did the ' ' (space character) instead of normal chars. my next step was editing /boot/loader.conf and inserting: hint.atkbd.0.flags=3D"0x1" reboot, and the same thing is happening. after inserting: ukbd_load=3D"YES" to /boot/loader.conf, the system just freezes after loading driver atkbd, i made some experiments connecting, plugged in my old ps2 keyboard and run simple loop doing ls /dev/kbd*, after i plugged in device appeared, and then i tried to do: kbdcontrol -k /dev/ukbd0 < /dev/console, but both keyboard freezed. do you have any suggestions, what might be wrong, what can i check or just what to do to make it work. the keyboard is: http://www.geniusnet.com.tw/product/product-1.asp?pdtno=3D548 From owner-freebsd-hardware@FreeBSD.ORG Fri Dec 16 06:37:24 2005 Return-Path: X-Original-To: freebsd-hardware@FreeBSD.org Delivered-To: freebsd-hardware@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D5EF616A422; Fri, 16 Dec 2005 06:37:24 +0000 (GMT) (envelope-from jrhett@mail.meer.net) Received: from outbound0.sv.meer.net (outbound0.sv.meer.net [205.217.152.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 16FC343D46; Fri, 16 Dec 2005 06:37:24 +0000 (GMT) (envelope-from jrhett@mail.meer.net) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) by outbound0.sv.meer.net (8.12.10/8.12.6) with ESMTP id jBG6bJQT039403; Thu, 15 Dec 2005 22:37:23 -0800 (PST) (envelope-from jrhett@mail.meer.net) Received: from mail.meer.net (localhost [127.0.0.1]) by mail.meer.net (8.13.3/8.13.3/meer) with ESMTP id jBG6atDb052466; Thu, 15 Dec 2005 22:36:55 -0800 (PST) (envelope-from jrhett@mail.meer.net) Received: (from jrhett@localhost) by mail.meer.net (8.13.3/8.13.3) id jBG6asct052465; Thu, 15 Dec 2005 22:36:54 -0800 (PST) (envelope-from jrhett) Date: Thu, 15 Dec 2005 22:36:54 -0800 From: Joe Rhett To: John Baldwin Message-ID: <20051216063654.GA49191@svcolo.com> References: <20051117050336.GB67653@svcolo.com> <20051201204625.W41849@delplex.bde.org> <20051205200546.GB13194@svcolo.com> <200512051522.41965.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200512051522.41965.jhb@freebsd.org> Organization: svcolo.com User-Agent: Mutt/1.5.9i Cc: hardware@FreeBSD.org, freebsd-hardware@FreeBSD.org Subject: Re: com1 incorrectly associated with ttyd1, com2 with ttyd0 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 06:37:25 -0000 > > On Thu, Dec 01, 2005 at 08:58:04PM +1100, Bruce Evans wrote: > > > It's not clear that disabling in the BIOS should disable for all OSes. > On Monday 05 December 2005 03:05 pm, Joe Rhett wrote: > > What? That's a fairly weird interpretation. If I want to disable inside a > > given OS, I do that inside the OS. If I want to disable for _ALL_ OSes, > > then I disable in the BIOS. What reasonable logic can argue otherwise? On Mon, Dec 05, 2005 at 03:22:40PM -0500, John Baldwin wrote: > The BIOS doesn't say "X is disabled", it just doesn't have any resources setup > for X. Well, this is where what the BIOS "says" and what the user is led to expect, are different that what you are arguing for. And on top of that, every major OS except for FreeBSD does the right thing (acts like it isn't there) Isn't it fairly obvious that no resources setup for a peripheral means "disabled in BIOS" and it would be best to ignore that resource? -- Jo Rhett senior geek SVcolo : Silicon Valley Colocation From owner-freebsd-hardware@FreeBSD.ORG Fri Dec 16 06:37:24 2005 Return-Path: X-Original-To: hardware@FreeBSD.org Delivered-To: freebsd-hardware@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D5EF616A422; Fri, 16 Dec 2005 06:37:24 +0000 (GMT) (envelope-from jrhett@mail.meer.net) Received: from outbound0.sv.meer.net (outbound0.sv.meer.net [205.217.152.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 16FC343D46; Fri, 16 Dec 2005 06:37:24 +0000 (GMT) (envelope-from jrhett@mail.meer.net) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) by outbound0.sv.meer.net (8.12.10/8.12.6) with ESMTP id jBG6bJQT039403; Thu, 15 Dec 2005 22:37:23 -0800 (PST) (envelope-from jrhett@mail.meer.net) Received: from mail.meer.net (localhost [127.0.0.1]) by mail.meer.net (8.13.3/8.13.3/meer) with ESMTP id jBG6atDb052466; Thu, 15 Dec 2005 22:36:55 -0800 (PST) (envelope-from jrhett@mail.meer.net) Received: (from jrhett@localhost) by mail.meer.net (8.13.3/8.13.3) id jBG6asct052465; Thu, 15 Dec 2005 22:36:54 -0800 (PST) (envelope-from jrhett) Date: Thu, 15 Dec 2005 22:36:54 -0800 From: Joe Rhett To: John Baldwin Message-ID: <20051216063654.GA49191@svcolo.com> References: <20051117050336.GB67653@svcolo.com> <20051201204625.W41849@delplex.bde.org> <20051205200546.GB13194@svcolo.com> <200512051522.41965.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200512051522.41965.jhb@freebsd.org> Organization: svcolo.com User-Agent: Mutt/1.5.9i Cc: hardware@FreeBSD.org, freebsd-hardware@FreeBSD.org Subject: Re: com1 incorrectly associated with ttyd1, com2 with ttyd0 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 06:37:25 -0000 > > On Thu, Dec 01, 2005 at 08:58:04PM +1100, Bruce Evans wrote: > > > It's not clear that disabling in the BIOS should disable for all OSes. > On Monday 05 December 2005 03:05 pm, Joe Rhett wrote: > > What? That's a fairly weird interpretation. If I want to disable inside a > > given OS, I do that inside the OS. If I want to disable for _ALL_ OSes, > > then I disable in the BIOS. What reasonable logic can argue otherwise? On Mon, Dec 05, 2005 at 03:22:40PM -0500, John Baldwin wrote: > The BIOS doesn't say "X is disabled", it just doesn't have any resources setup > for X. Well, this is where what the BIOS "says" and what the user is led to expect, are different that what you are arguing for. And on top of that, every major OS except for FreeBSD does the right thing (acts like it isn't there) Isn't it fairly obvious that no resources setup for a peripheral means "disabled in BIOS" and it would be best to ignore that resource? -- Jo Rhett senior geek SVcolo : Silicon Valley Colocation From owner-freebsd-hardware@FreeBSD.ORG Fri Dec 16 06:42:27 2005 Return-Path: X-Original-To: freebsd-hardware@FreeBSD.org Delivered-To: freebsd-hardware@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3FAAE16A41F; Fri, 16 Dec 2005 06:42:27 +0000 (GMT) (envelope-from jrhett@mail.meer.net) Received: from outbound0.sv.meer.net (outbound0.sv.meer.net [205.217.152.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7970543D5E; Fri, 16 Dec 2005 06:42:23 +0000 (GMT) (envelope-from jrhett@mail.meer.net) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) by outbound0.sv.meer.net (8.12.10/8.12.6) with ESMTP id jBG6gJQV039547; Thu, 15 Dec 2005 22:42:22 -0800 (PST) (envelope-from jrhett@mail.meer.net) Received: from mail.meer.net (localhost [127.0.0.1]) by mail.meer.net (8.13.3/8.13.3/meer) with ESMTP id jBG6fncs053692; Thu, 15 Dec 2005 22:41:49 -0800 (PST) (envelope-from jrhett@mail.meer.net) Received: (from jrhett@localhost) by mail.meer.net (8.13.3/8.13.3) id jBG6fmX7053689; Thu, 15 Dec 2005 22:41:48 -0800 (PST) (envelope-from jrhett) Date: Thu, 15 Dec 2005 22:41:48 -0800 From: Joe Rhett To: Bruce Evans Message-ID: <20051216064148.GB49191@svcolo.com> References: <20051117050336.GB67653@svcolo.com> <200511171030.36633.jhb@freebsd.org> <20051117220358.GA65127@svcolo.com> <20051130181757.GA29686@svcolo.com> <20051201204625.W41849@delplex.bde.org> <20051205200546.GB13194@svcolo.com> <20051208145124.C63825@delplex.bde.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051208145124.C63825@delplex.bde.org> Organization: svcolo.com User-Agent: Mutt/1.5.9i Cc: hardware@FreeBSD.org, John Baldwin , freebsd-hardware@FreeBSD.org Subject: Re: com1 incorrectly associated with ttyd1, com2 with ttyd0 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 06:42:27 -0000 > >On Thu, Dec 01, 2005 at 08:58:04PM +1100, Bruce Evans wrote: > >>It's not clear that disabling in the BIOS should disable for all OSes. > On Mon, 5 Dec 2005, Joe Rhett wrote: > >What? That's a fairly weird interpretation. If I want to disable inside a > >given OS, I do that inside the OS. If I want to disable for _ALL_ OSes, > >then I disable in the BIOS. What reasonable logic can argue otherwise? On Thu, Dec 08, 2005 at 03:13:00PM +1100, Bruce Evans wrote: > The BIOS might not be layered under _all_ OSes, either due to its design > or implementation, or OSes not understanding how to talk to the BIOS, or > there being no way to talk BIOS. eh? What does this have to do with the situation at hand? Here we can talk to the BIOS, and the BIOS is clearly indicating that peripheral A has 1,2,3 and peripheral B has 4,5,6 and peripheral C has no resources .. why are we ignoring this information? I'm not being rude, I'm entirely joking, but it sounds like a technician ignoring a customer complaint in her/his native language just because it *might* have been given in a different language... We see it. It is clear. Why are we ignoring it? > >>Don't know. I avoid ACPI if possible :-). I suspect that FreeBSD can see > >>ACPI tables but not all BIOS tables, so any soft disabling in the BIOS > >>gets lost. > >Can you really use everything without ACPI? What is lost by disabling > >ACPI? > It's system-dependent. ACPI is now essential for most portable > computers. I don't have one , and lose only faster interrupt handing > via the APIC on workstations. In any case, ACPI is also necessary to assign COM1 to port B, and COM2 to port A, which is what started this conversation in the first place. -- Jo Rhett senior geek SVcolo : Silicon Valley Colocation From owner-freebsd-hardware@FreeBSD.ORG Fri Dec 16 06:42:27 2005 Return-Path: X-Original-To: hardware@FreeBSD.org Delivered-To: freebsd-hardware@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3FAAE16A41F; Fri, 16 Dec 2005 06:42:27 +0000 (GMT) (envelope-from jrhett@mail.meer.net) Received: from outbound0.sv.meer.net (outbound0.sv.meer.net [205.217.152.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7970543D5E; Fri, 16 Dec 2005 06:42:23 +0000 (GMT) (envelope-from jrhett@mail.meer.net) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) by outbound0.sv.meer.net (8.12.10/8.12.6) with ESMTP id jBG6gJQV039547; Thu, 15 Dec 2005 22:42:22 -0800 (PST) (envelope-from jrhett@mail.meer.net) Received: from mail.meer.net (localhost [127.0.0.1]) by mail.meer.net (8.13.3/8.13.3/meer) with ESMTP id jBG6fncs053692; Thu, 15 Dec 2005 22:41:49 -0800 (PST) (envelope-from jrhett@mail.meer.net) Received: (from jrhett@localhost) by mail.meer.net (8.13.3/8.13.3) id jBG6fmX7053689; Thu, 15 Dec 2005 22:41:48 -0800 (PST) (envelope-from jrhett) Date: Thu, 15 Dec 2005 22:41:48 -0800 From: Joe Rhett To: Bruce Evans Message-ID: <20051216064148.GB49191@svcolo.com> References: <20051117050336.GB67653@svcolo.com> <200511171030.36633.jhb@freebsd.org> <20051117220358.GA65127@svcolo.com> <20051130181757.GA29686@svcolo.com> <20051201204625.W41849@delplex.bde.org> <20051205200546.GB13194@svcolo.com> <20051208145124.C63825@delplex.bde.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051208145124.C63825@delplex.bde.org> Organization: svcolo.com User-Agent: Mutt/1.5.9i Cc: hardware@FreeBSD.org, John Baldwin , freebsd-hardware@FreeBSD.org Subject: Re: com1 incorrectly associated with ttyd1, com2 with ttyd0 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 06:42:27 -0000 > >On Thu, Dec 01, 2005 at 08:58:04PM +1100, Bruce Evans wrote: > >>It's not clear that disabling in the BIOS should disable for all OSes. > On Mon, 5 Dec 2005, Joe Rhett wrote: > >What? That's a fairly weird interpretation. If I want to disable inside a > >given OS, I do that inside the OS. If I want to disable for _ALL_ OSes, > >then I disable in the BIOS. What reasonable logic can argue otherwise? On Thu, Dec 08, 2005 at 03:13:00PM +1100, Bruce Evans wrote: > The BIOS might not be layered under _all_ OSes, either due to its design > or implementation, or OSes not understanding how to talk to the BIOS, or > there being no way to talk BIOS. eh? What does this have to do with the situation at hand? Here we can talk to the BIOS, and the BIOS is clearly indicating that peripheral A has 1,2,3 and peripheral B has 4,5,6 and peripheral C has no resources .. why are we ignoring this information? I'm not being rude, I'm entirely joking, but it sounds like a technician ignoring a customer complaint in her/his native language just because it *might* have been given in a different language... We see it. It is clear. Why are we ignoring it? > >>Don't know. I avoid ACPI if possible :-). I suspect that FreeBSD can see > >>ACPI tables but not all BIOS tables, so any soft disabling in the BIOS > >>gets lost. > >Can you really use everything without ACPI? What is lost by disabling > >ACPI? > It's system-dependent. ACPI is now essential for most portable > computers. I don't have one , and lose only faster interrupt handing > via the APIC on workstations. In any case, ACPI is also necessary to assign COM1 to port B, and COM2 to port A, which is what started this conversation in the first place. -- Jo Rhett senior geek SVcolo : Silicon Valley Colocation From owner-freebsd-hardware@FreeBSD.ORG Fri Dec 16 06:43:31 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 431DF16A41F; Fri, 16 Dec 2005 06:43:31 +0000 (GMT) (envelope-from jrhett@mail.meer.net) Received: from outbound0.sv.meer.net (outbound0.sv.meer.net [205.217.152.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4928243D6A; Fri, 16 Dec 2005 06:43:22 +0000 (GMT) (envelope-from jrhett@mail.meer.net) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) by outbound0.sv.meer.net (8.12.10/8.12.6) with ESMTP id jBG6hKQV039575; Thu, 15 Dec 2005 22:43:21 -0800 (PST) (envelope-from jrhett@mail.meer.net) Received: from mail.meer.net (localhost [127.0.0.1]) by mail.meer.net (8.13.3/8.13.3/meer) with ESMTP id jBG6h6OD054017; Thu, 15 Dec 2005 22:43:06 -0800 (PST) (envelope-from jrhett@mail.meer.net) Received: (from jrhett@localhost) by mail.meer.net (8.13.3/8.13.3) id jBG6h677054015; Thu, 15 Dec 2005 22:43:06 -0800 (PST) (envelope-from jrhett) Date: Thu, 15 Dec 2005 22:43:06 -0800 From: Joe Rhett To: John Baldwin Message-ID: <20051216064300.GC49191@svcolo.com> References: <20051117050336.GB67653@svcolo.com> <200512011153.50287.jhb@freebsd.org> <20051205200709.GC13194@svcolo.com> <200512051526.48117.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200512051526.48117.jhb@freebsd.org> Organization: svcolo.com User-Agent: Mutt/1.5.9i Cc: freebsd-hardware@freebsd.org Subject: Re: com1 incorrectly associated with ttyd1, com2 with ttyd0 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 06:43:31 -0000 > On Monday 05 December 2005 03:07 pm, Joe Rhett wrote: > > So what's involved in simply having it say > > Found : disabled in BIOS > > instead of half a dozen complaints for each disabled device? On Mon, Dec 05, 2005 at 03:26:47PM -0500, John Baldwin wrote: > There's no disabled flag. If you have PNP OS set to yes in your BIOS, it is > free to leave any devices not needed for booting unconfigured (like printer > ports, serial ports, etc.) and there is no way for the OS to know if the BIOS > didn't alloc resources because it is disabled or because the BIOS was just > lazy. If this is impossible to know, why do Windows and Linux both handle it properly? -- Jo Rhett senior geek SVcolo : Silicon Valley Colocation From owner-freebsd-hardware@FreeBSD.ORG Fri Dec 16 06:43:32 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E30B16A41F; Fri, 16 Dec 2005 06:43:32 +0000 (GMT) (envelope-from jrhett@mail.meer.net) Received: from outbound0.sv.meer.net (outbound0.sv.meer.net [205.217.152.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id D6D4443D5A; Fri, 16 Dec 2005 06:43:21 +0000 (GMT) (envelope-from jrhett@mail.meer.net) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) by outbound0.sv.meer.net (8.12.10/8.12.6) with ESMTP id jBG6hKQR039575; Thu, 15 Dec 2005 22:43:21 -0800 (PST) (envelope-from jrhett@mail.meer.net) Received: from mail.meer.net (localhost [127.0.0.1]) by mail.meer.net (8.13.3/8.13.3/meer) with ESMTP id jBG6h0Pt053978; Thu, 15 Dec 2005 22:43:00 -0800 (PST) (envelope-from jrhett@mail.meer.net) Received: (from jrhett@localhost) by mail.meer.net (8.13.3/8.13.3) id jBG6h0M5053977; Thu, 15 Dec 2005 22:43:00 -0800 (PST) (envelope-from jrhett) Date: Thu, 15 Dec 2005 22:43:00 -0800 From: Joe Rhett To: John Baldwin , t@svcolo.com Message-ID: <20051216064300.GC49191@svcolo.com> References: <20051117050336.GB67653@svcolo.com> <200512011153.50287.jhb@freebsd.org> <20051205200709.GC13194@svcolo.com> <200512051526.48117.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200512051526.48117.jhb@freebsd.org> Organization: svcolo.com User-Agent: Mutt/1.5.9i Cc: freebsd-hardware@freebsd.org Subject: Re: com1 incorrectly associated with ttyd1, com2 with ttyd0 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 06:43:32 -0000 > On Monday 05 December 2005 03:07 pm, Joe Rhett wrote: > > So what's involved in simply having it say > > Found : disabled in BIOS > > instead of half a dozen complaints for each disabled device? On Mon, Dec 05, 2005 at 03:26:47PM -0500, John Baldwin wrote: > There's no disabled flag. If you have PNP OS set to yes in your BIOS, it is > free to leave any devices not needed for booting unconfigured (like printer > ports, serial ports, etc.) and there is no way for the OS to know if the BIOS > didn't alloc resources because it is disabled or because the BIOS was just > lazy. If this is impossible to know, why do Windows and Linux both handle it properly? -- Jo Rhett senior geek SVcolo : Silicon Valley Colocation From owner-freebsd-hardware@FreeBSD.ORG Fri Dec 16 16:25:06 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B194716A41F for ; Fri, 16 Dec 2005 16:25:06 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id D0CB043D5A for ; Fri, 16 Dec 2005 16:25:02 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3946539 for multiple; Fri, 16 Dec 2005 11:22:54 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jBGGOnx4080681; Fri, 16 Dec 2005 11:24:49 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hardware@freebsd.org Date: Fri, 16 Dec 2005 11:25:19 -0500 User-Agent: KMail/1.8.2 References: <20051117050336.GB67653@svcolo.com> <200512051522.41965.jhb@freebsd.org> <20051216063654.GA49191@svcolo.com> In-Reply-To: <20051216063654.GA49191@svcolo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512161125.19927.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1210/Thu Dec 15 10:23:22 2005 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Joe Rhett Subject: Re: com1 incorrectly associated with ttyd1, com2 with ttyd0 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 16:25:06 -0000 On Friday 16 December 2005 01:36 am, Joe Rhett wrote: > > > On Thu, Dec 01, 2005 at 08:58:04PM +1100, Bruce Evans wrote: > > > > It's not clear that disabling in the BIOS should disable for all > > > > OSes. > > > > On Monday 05 December 2005 03:05 pm, Joe Rhett wrote: > > > What? That's a fairly weird interpretation. If I want to disable > > > inside a given OS, I do that inside the OS. If I want to disable for > > > _ALL_ OSes, then I disable in the BIOS. What reasonable logic can > > > argue otherwise? > > On Mon, Dec 05, 2005 at 03:22:40PM -0500, John Baldwin wrote: > > The BIOS doesn't say "X is disabled", it just doesn't have any resources > > setup for X. > > Well, this is where what the BIOS "says" and what the user is led to > expect, are different that what you are arguing for. And on top of that, > every major OS except for FreeBSD does the right thing (acts like it isn't > there) > > Isn't it fairly obvious that no resources setup for a peripheral means > "disabled in BIOS" and it would be best to ignore that resource? No. You would understand that if you had actually read my earlier e-mails. If you set PnP OS to yes, then the BIOS is free to not enable any devices not needed for booting. Thus, even if you didn't have COM1 disabled if it didn't need COM1 to boot and you had PnP OS set to yes, it could not assign any resources to COM1 and require the OS to set the resources. There isn't any way for the OS to know if you disabled the device, or if you used PnP OS and the BIOS didn't configure that device _even_ _though_ _it_ _is_ _enabled_ _in_ _the_ _BIOS_ _setup_ because it didn't feel like it. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-hardware@FreeBSD.ORG Fri Dec 16 18:13:13 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B156416A41F for ; Fri, 16 Dec 2005 18:13:13 +0000 (GMT) (envelope-from pbauer@yes.ineedamiracle.com) Received: from yes.ineedamiracle.com (yes.ineedamiracle.com [66.92.251.132]) by mx1.FreeBSD.org (Postfix) with SMTP id 740F143D69 for ; Fri, 16 Dec 2005 18:13:11 +0000 (GMT) (envelope-from pbauer@yes.ineedamiracle.com) Received: from localhost (localhost [127.0.0.1]) by yes.ineedamiracle.com (Postfix) with ESMTP id AD65058F65 for ; Fri, 16 Dec 2005 10:13:10 -0800 (PST) Received: from yes.ineedamiracle.com ([127.0.0.1]) by localhost (yes.ineedamiracle.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 77010-08 for ; Fri, 16 Dec 2005 10:13:04 -0800 (PST) Received: by yes.ineedamiracle.com (Postfix, from userid 1001) id B01B158F74; Fri, 16 Dec 2005 10:13:03 -0800 (PST) Date: Fri, 16 Dec 2005 10:13:03 -0800 From: Paul Bauer To: freebsd-hardware@freebsd.org Message-ID: <20051216181302.GC98743@yes.ineedamiracle.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="n7zTieg8iIQ1Wja9" Content-Disposition: inline X-GnuPG-KeyID: B5E1CC6C X-GnuPG-Fingerprint: DC75 9D93 C12C 5F3E 6FC4 3CD6 4DA0 6430 B5E1 CC6 X-Useless-Header: Microsoft, where do you want to do today? Linux, where do you want to go tomorrow? BSD are you guys coming or what? X-Operating-System: FreeBSD yes.ineedamiracle.com 5.4-RELEASE-p8 FreeBSD 5.4-RELEASE-p8 X-Editor: VIM - Vi IMproved 6.3. User-Agent: mutt-ng/devel-r535 (FreeBSD) X-Virus-Scanned: amavisd-new at shorttermwhat.com Subject: RELENG_6_0 core dump X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 18:13:13 -0000 --n7zTieg8iIQ1Wja9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I have been trying to find out why a machine I have dumps. I finally read the handbook and got the dumping mechanism working. So then it was stable... It finally cored and this is what was produced: S kgdb kernel.debug /var/crash/vmcore.4 [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 "i386-marcel-freebsd". Unread portion of the kernel message buffer: panic: vm_page_insert: page already inserted Uptime: 19d5h10m10s Dumping 511 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 511MB (130816 pages) 496 480 464 448 432 416 400 384 368 352 336 320 304 288 272 256 240 224 208 192 176 160 144 128 112 96 80 64 48 32 16 #0 doadump () at pcpu.h:165 165 __asm __volatile("movl %%fs:0,%0" : "=r" (td)); I see a few references to the error on line 165 but no solution. Please let me know what I may do to help debug this further. I am pasting a dmesg below: Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-RELEASE #4: Sat Nov 12 17:18:45 PST 2005 root@skull.ineedamiracle.com:/usr/obj/usr/src/sys/SKULL Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.20GHz (2200.09-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf24 Stepping = 4 Features=0x3febf9ff real memory = 536870912 (512 MB) avail memory = 516042752 (492 MB) npx0: [FAST] npx0: on motherboard npx0: INT 16 interface cpu0 on motherboard pcib0: pcibus 0 on motherboard pir0: on motherboard pci0: on pcib0 agp0: mem 0xe0000000-0xe3ffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) rl0: port 0xec00-0xecff mem 0xdfffff00-0xdfffffff ir q 5 at device 8.0 on pci0 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:50:fc:41:f0:50 pci0: at device 11.0 (no driver attached) isab0: at device 17.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376, 0xfc00-0xfc0f at device 17.1 on pci0 ata0: on atapci0 ata1: on atapci0 uhci0: port 0xd800-0xd81f irq 11 at device 17.2 on p ci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xdc00-0xdc1f irq 11 at device 17.3 on p ci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xe000-0xe01f irq 11 at device 17.4 on p ci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered vr0: port 0xd400-0xd4ff mem 0xdffffe00-0xdfff feff irq 5 at device 18.0 on pci0 miibus1: on vr0 ukphy0: on miibus1 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vr0: Ethernet address: 00:07:95:b3:b0:bd pmtimer0 on isa0 orm0: at iomem 0xc0000-0xcafff,0xcb000-0xcefff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: [FAST] ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources (memory) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) Timecounter "TSC" frequency 2200092132 Hz quality 800 Timecounters tick every 1.000 msec ad0: 114473MB at ata0-master UDMA100 ad1: 286188MB at ata0-slave UDMA100 acd0: CDRW at ata1-master UDMA33 Trying to mount root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted WARNING: /home was not properly dismounted WARNING: /tmp was not properly dismounted WARNING: /usr was not properly dismounted WARNING: /var was not properly dismounted /var: mount pending error: blocks 4 files 1 WARNING: /jail_www was not properly dismounted /jail_www: mount pending error: blocks 4 files 1 WARNING: /jail_dns was not properly dismounted /jail_dns: mount pending error: blocks 4 files 1 rl0: link state changed to UP pid 23686 (mail), uid 0: exited on signal 6 (core dumped) panic: vm_page_insert: page already inserted Uptime: 19d5h10m10s Dumping 511 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 511MB (130816 pages) 496 480 464 448 432 416 400 384 368 352 336 320 304 288 272 256 240 224 208 192 176 160 144 128 112 96 80 64 48 32 16 ... ok Dump complete Automatic reboot in 15 seconds - press a key on the console to abort Thank you Paul --n7zTieg8iIQ1Wja9 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFDowOuTaBkMLXhzGwRAllwAJ4+9gbZISt/oJBhurXiWIcBHPKghgCfbptX ImMuUpGYanspAL6W2AEFEDg= =WUAo -----END PGP SIGNATURE----- --n7zTieg8iIQ1Wja9-- From owner-freebsd-hardware@FreeBSD.ORG Fri Dec 16 20:15:03 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9F0B16A41F for ; Fri, 16 Dec 2005 20:15:03 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBC4D43D55 for ; Fri, 16 Dec 2005 20:15:02 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3960717 for multiple; Fri, 16 Dec 2005 15:12:53 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jBGKElK0081886; Fri, 16 Dec 2005 15:14:47 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Joe Rhett Date: Fri, 16 Dec 2005 15:15:15 -0500 User-Agent: KMail/1.8.2 References: <20051117050336.GB67653@svcolo.com> <200512051526.48117.jhb@freebsd.org> <20051216064300.GC49191@svcolo.com> In-Reply-To: <20051216064300.GC49191@svcolo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512161515.16327.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1210/Thu Dec 15 10:23:22 2005 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: freebsd-hardware@freebsd.org Subject: Re: com1 incorrectly associated with ttyd1, com2 with ttyd0 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 20:15:04 -0000 On Friday 16 December 2005 01:43 am, Joe Rhett wrote: > > On Monday 05 December 2005 03:07 pm, Joe Rhett wrote: > > > So what's involved in simply having it say > > > Found : disabled in BIOS > > > instead of half a dozen complaints for each disabled device? > > On Mon, Dec 05, 2005 at 03:26:47PM -0500, John Baldwin wrote: > > There's no disabled flag. If you have PNP OS set to yes in your BIOS, it > > is free to leave any devices not needed for booting unconfigured (like > > printer ports, serial ports, etc.) and there is no way for the OS to know > > if the BIOS didn't alloc resources because it is disabled or because the > > BIOS was just lazy. > > If this is impossible to know, why do Windows and Linux both handle it > properly? Probably because currently most BIOSen still setup most ISA-type devices even though they aren't required to when PnP OS is set to YES and Windows and linux are probably just as lazy as we are when it comes to ISA-type devices that have no resources (i.e. just fail to attach instead of trying to figure out which resources to use and setting it up.) Really there should be an OS-dependent way of saying that you don't want to use a device and you could even turn devices off that the BIOS enables. We don't have and good way for handling that currently however. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-hardware@FreeBSD.ORG Sat Dec 17 10:49:45 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3421E16A41F for ; Sat, 17 Dec 2005 10:49:45 +0000 (GMT) (envelope-from mat@mat.cc) Received: from plouf.absolight.net (plouf.absolight.net [193.30.224.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E0C043D4C for ; Sat, 17 Dec 2005 10:49:44 +0000 (GMT) (envelope-from mat@mat.cc) Date: Sat, 17 Dec 2005 11:49:35 +0100 From: Mathieu Arnold To: Alexandre DELAY Message-ID: <0D162CCAE42F819501B87257@cc-126-240.int.t-online.fr> In-Reply-To: References: X-Mailer: Mulberry/3.1.6 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: freebsd-hardware@freebsd.org Subject: RE: HDD X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 10:49:45 -0000 +-le 14/12/2005 17:45 +0100, Alexandre DELAY =E9crivait : | Don't you think that flash drives are also a good solution? |=20 | I am sure that it will be the future replacement for hard drive disks. | see http://www.memtech.com/ for example |=20 | With no buffer and 1ms access delay you minimise write failures. It is an | interresting solution. Hum, flash has a *limited* ammount of possible write for each cell, for low cost, it's between 10K-50K and for heavy duty, industrial grade, bla bla bla, it's around 2M, so, hum, just imagine you have a solid state flash disk, and your swap on it. One day, your box begins swapping hard, and some time later, half of your drive can't be written to again... --=20 Mathieu Arnold From owner-freebsd-hardware@FreeBSD.ORG Sat Dec 17 10:55:09 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB33416A41F for ; Sat, 17 Dec 2005 10:55:09 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C9B043D5A for ; Sat, 17 Dec 2005 10:55:09 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.48.2]) by phk.freebsd.dk (Postfix) with ESMTP id 1C29DBC66; Sat, 17 Dec 2005 10:55:06 +0000 (UTC) To: Mathieu Arnold From: "Poul-Henning Kamp" In-Reply-To: Your message of "Sat, 17 Dec 2005 11:49:35 +0100." <0D162CCAE42F819501B87257@cc-126-240.int.t-online.fr> Date: Sat, 17 Dec 2005 11:55:06 +0100 Message-ID: <23984.1134816906@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: Alexandre DELAY , freebsd-hardware@freebsd.org Subject: Re: HDD X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 10:55:09 -0000 In message <0D162CCAE42F819501B87257@cc-126-240.int.t-online.fr>, Mathieu Arnol d writes: >+-le 14/12/2005 17:45 +0100, Alexandre DELAY =E9crivait : >| Don't you think that flash drives are also a good solution? >|=20 >| I am sure that it will be the future replacement for hard drive disks. >| see http://www.memtech.com/ for example >|=20 >| With no buffer and 1ms access delay you minimise write failures. It is an >| interresting solution. > >Hum, flash has a *limited* ammount of possible write for each cell, for low >cost, it's between 10K-50K and for heavy duty, industrial grade, bla bla bla, >it's around 2M, so, hum, just imagine you have a solid state flash disk, and >your swap on it. One day, your box begins swapping hard, and some time later, >half of your drive can't be written to again... Sorry but that is not how flash devices work. There is a very important piece of technology called a "flash adaptation layer" which performs what is usually called "wear levelling" in an attempt to get the maximum amount of lifetime out of the entire device by using a dynamic logical to physical mapping and keeping track of bad cells etc etc. Yes, you will kill a flash by doing a lot of writes, but it will not develop individual bad sectors like a disk. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-hardware@FreeBSD.ORG Sat Dec 17 11:25:51 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A6AD016A41F for ; Sat, 17 Dec 2005 11:25:51 +0000 (GMT) (envelope-from mat@mat.cc) Received: from plouf.absolight.net (plouf.absolight.net [193.30.224.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D0E743D45 for ; Sat, 17 Dec 2005 11:25:51 +0000 (GMT) (envelope-from mat@mat.cc) Date: Sat, 17 Dec 2005 12:25:49 +0100 From: Mathieu Arnold To: Poul-Henning Kamp Message-ID: <5C66F3C40FAC63FB21A0C626@cc-126-240.int.t-online.fr> In-Reply-To: <23984.1134816906@critter.freebsd.dk> References: <23984.1134816906@critter.freebsd.dk> X-Mailer: Mulberry/3.1.6 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: Alexandre DELAY , freebsd-hardware@freebsd.org Subject: Re: HDD X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 11:25:51 -0000 +-le 17/12/2005 11:55 +0100, Poul-Henning Kamp =E9crivait : | In message <0D162CCAE42F819501B87257@cc-126-240.int.t-online.fr>, Mathieu | Arnol d writes: |> +-le 14/12/2005 17:45 +0100, Alexandre DELAY =3DE9crivait : |>| Don't you think that flash drives are also a good solution? |>| =3D20 |>| I am sure that it will be the future replacement for hard drive disks. |>| see http://www.memtech.com/ for example |>| =3D20 |>| With no buffer and 1ms access delay you minimise write failures. It is an |>| interresting solution. |>=20 |> Hum, flash has a *limited* ammount of possible write for each cell, for = low |> cost, it's between 10K-50K and for heavy duty, industrial grade, bla bla |> bla, it's around 2M, so, hum, just imagine you have a solid state flash |> disk, and your swap on it. One day, your box begins swapping hard, and |> some time later, half of your drive can't be written to again... |=20 | Sorry but that is not how flash devices work. I do remember your NanoBSD talk 3 weeks ago :-) | Yes, you will kill a flash by doing a lot of writes, but it will | not develop individual bad sectors like a disk. but, taking into account that your flash is half filled with real non really changing data, and you have a swap partition, the flash adaptation layer will have the swap space slide on the available space, and it'll wrap up, after many times, it'll eventually have the free space unwritable (unless the flash adaptation layer is smart enough to move non changing data to cell which won't have many more write cycles left and continue to write to almost non used cells). But maybe I have it wrong. --=20 Mathieu Arnold From owner-freebsd-hardware@FreeBSD.ORG Sat Dec 17 12:04:27 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A5E916A41F for ; Sat, 17 Dec 2005 12:04:27 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B2E843D4C for ; Sat, 17 Dec 2005 12:04:26 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.48.2]) by phk.freebsd.dk (Postfix) with ESMTP id 8FA15BC66; Sat, 17 Dec 2005 12:04:24 +0000 (UTC) To: Mathieu Arnold From: "Poul-Henning Kamp" In-Reply-To: Your message of "Sat, 17 Dec 2005 12:25:49 +0100." <5C66F3C40FAC63FB21A0C626@cc-126-240.int.t-online.fr> Date: Sat, 17 Dec 2005 13:04:24 +0100 Message-ID: <24265.1134821064@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: Alexandre DELAY , freebsd-hardware@freebsd.org Subject: Re: HDD X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 12:04:27 -0000 In message <5C66F3C40FAC63FB21A0C626@cc-126-240.int.t-online.fr>, Mathieu Arnol d writes: >but, taking into account that your flash is half filled with real non really >changing data, and you have a swap partition, the flash adaptation layer will >have the swap space slide on the available space, and it'll wrap up, after >many times, it'll eventually have the free space unwritable (unless the flash >adaptation layer is smart enough to move non changing data to cell which >won't have many more write cycles left and continue to write to almost non >used cells). It is. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-hardware@FreeBSD.ORG Sat Dec 17 21:51:50 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E0DA16A41F; Sat, 17 Dec 2005 21:51:50 +0000 (GMT) (envelope-from jrhett@mail.meer.net) Received: from outbound0.sv.meer.net (outbound0.sv.meer.net [205.217.152.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id A180D43D66; Sat, 17 Dec 2005 21:51:46 +0000 (GMT) (envelope-from jrhett@mail.meer.net) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) by outbound0.sv.meer.net (8.12.10/8.12.6) with ESMTP id jBHLpjQN021300; Sat, 17 Dec 2005 13:51:45 -0800 (PST) (envelope-from jrhett@mail.meer.net) Received: from mail.meer.net (localhost [127.0.0.1]) by mail.meer.net (8.13.3/8.13.3/meer) with ESMTP id jBHLpX9j092637; Sat, 17 Dec 2005 13:51:33 -0800 (PST) (envelope-from jrhett@mail.meer.net) Received: (from jrhett@localhost) by mail.meer.net (8.13.3/8.13.3) id jBHLpXUh092635; Sat, 17 Dec 2005 13:51:33 -0800 (PST) (envelope-from jrhett) Date: Sat, 17 Dec 2005 13:51:33 -0800 From: Joe Rhett To: John Baldwin Message-ID: <20051217215133.GA92180@svcolo.com> References: <20051117050336.GB67653@svcolo.com> <200512051522.41965.jhb@freebsd.org> <20051216063654.GA49191@svcolo.com> <200512161125.19927.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200512161125.19927.jhb@freebsd.org> Organization: svcolo.com User-Agent: Mutt/1.5.9i Cc: freebsd-hardware@freebsd.org Subject: Re: com1 incorrectly associated with ttyd1, com2 with ttyd0 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 21:51:50 -0000 > On Friday 16 December 2005 01:36 am, Joe Rhett wrote: > > Well, this is where what the BIOS "says" and what the user is led to > > expect, are different that what you are arguing for. And on top of that, > > every major OS except for FreeBSD does the right thing (acts like it isn't > > there) > > > > Isn't it fairly obvious that no resources setup for a peripheral means > > "disabled in BIOS" and it would be best to ignore that resource? On Fri, Dec 16, 2005 at 11:25:19AM -0500, John Baldwin wrote: > No. You would understand that if you had actually read my earlier e-mails. I did, but out of order of this reply. Sorry. > If you set PnP OS to yes, then the BIOS is free to not enable any devices not > needed for booting. Thus, even if you didn't have COM1 disabled if it didn't > need COM1 to boot and you had PnP OS set to yes, it could not assign any > resources to COM1 and require the OS to set the resources. There isn't any > way for the OS to know if you disabled the device, or if you used PnP OS and > the BIOS didn't configure that device _even_ _though_ _it_ _is_ _enabled_ > _in_ _the_ _BIOS_ _setup_ because it didn't feel like it. Are you saying that changing PNP to "No" would make it easier for FreeBSD? Are there any disadvantages to this? -- Jo Rhett senior geek SVcolo : Silicon Valley Colocation