From owner-freebsd-hardware@FreeBSD.ORG Sun Jun 24 04:06:01 2007 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2CADE16A41F for ; Sun, 24 Jun 2007 04:06:01 +0000 (UTC) (envelope-from rp_freebsd@mac.com) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.182]) by mx1.freebsd.org (Postfix) with ESMTP id 1A51813C45A for ; Sun, 24 Jun 2007 04:06:01 +0000 (UTC) (envelope-from rp_freebsd@mac.com) Received: from webmail032 (webmail032-s [10.13.128.32]) by smtpout.mac.com (Xserve/smtpout12/MantshX 4.0) with ESMTP id l5O3o437016487 for ; Sat, 23 Jun 2007 20:50:04 -0700 (PDT) Date: Sat, 23 Jun 2007 20:50:04 -0700 From: Ravi Pokala To: freebsd-hardware@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Originating-IP: 67.170.251.81 Received: from [67.170.251.81] from webmail.mac.com with HTTP; Sat, 23 Jun 2007 20:50:04 -0700 X-Brightmail-Tracker: AAAAAA== X-Brightmail-scanned: yes Subject: Looking for a motherboard with lots of SATA ports, supported in 6.2-STABLE 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, 24 Jun 2007 04:06:01 -0000 Hi folks, The motherboard in my home server recently toasted itself, so it's time to go shopping for a new one. I don't like the bleeding edge enough to run -CURRENT, so I'm looking for something that's supported by 6.2-STABLE. I'm okay with doing simple MFCs to pull down a few drivers if needed. My main concerns are that the networking is well supported (GigE preferred of course), and that there are lots of supported on-board SATA ports. I currently have four SATA drives, so I'd prefer six or eight ports on the new board for growth. I don't care too much whether the new board is for Intel or AMD CPUs, as long as it supports dual-core CPUs. I can order ECC DIMMs cheap from work, so that's preferred but by no means necessary. I'd also like decent on-board graphics, on the off chance I want to dual-boot it to play some older games. In FreeBSD, it just needs to be supported enough to give me a VGA console. I'd like to keep it under $150 for the motherboard. Any suggestions? Many thanks, --rp From owner-freebsd-hardware@FreeBSD.ORG Sun Jun 24 07:56:11 2007 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A8E0416A41F for ; Sun, 24 Jun 2007 07:56:11 +0000 (UTC) (envelope-from etc@fluffles.net) Received: from auriate.fluffles.net (cust.95.160.adsl.cistron.nl [195.64.95.160]) by mx1.freebsd.org (Postfix) with ESMTP id 5EE1013C448 for ; Sun, 24 Jun 2007 07:56:11 +0000 (UTC) (envelope-from etc@fluffles.net) Received: from 195-241-125-45.dsl.ip.tiscali.nl ([195.241.125.45] helo=[10.0.0.18]) by auriate.fluffles.net with esmtpa (Exim 4.66 (FreeBSD)) (envelope-from ) id 1I2Mwt-000IRY-3e; Sun, 24 Jun 2007 09:55:55 +0200 Message-ID: <467E2392.6010109@fluffles.net> Date: Sun, 24 Jun 2007 09:56:02 +0200 From: Fluffles User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: Ravi Pokala 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: Looking for a motherboard with lots of SATA ports, supported in 6.2-STABLE 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, 24 Jun 2007 07:56:11 -0000 Ravi Pokala wrote: > My main concerns are that the networking is well supported (GigE preferred of course), and that there are lots of supported on-board SATA ports. I currently have four SATA drives, so I'd prefer six or eight ports on the new board for growth. > > I'd also like decent on-board graphics, on the off chance I want to dual-boot it to play some older games. In FreeBSD, it just needs to be supported enough to give me a VGA console. > You probably won't find 8 SATA ports and onboard video, these two just don't match. You either take a high-end board with lots of features, but *never* have onboard video (IGP), of you take a microATX board with onboard video which have 2 maybe 4 SATA ports. So you may want to drop this demand and get a PCI videocard and focus on boards with lots of Serial ATA connectors. Also be sure to check if these are supplied by the chipset (best) or by some second chip on the motherboard. Sometimes these 'extra' chips use the old and obsolete PCI bus for data transfer, which can be very slow especially in a RAID configuration. Maybe you can search for boards and post them on the mailinglist, so we can check if the SATA and gigabit works? Good luck! - Veronica From owner-freebsd-hardware@FreeBSD.ORG Tue Jun 26 14:24:50 2007 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E8C7216A421 for ; Tue, 26 Jun 2007 14:24:50 +0000 (UTC) (envelope-from bseklecki@collaborativefusion.com) Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by mx1.freebsd.org (Postfix) with ESMTP id AA39013C448 for ; Tue, 26 Jun 2007 14:24:50 +0000 (UTC) (envelope-from bseklecki@collaborativefusion.com) Received: from collaborativefusion.com (mx01.pub.collaborativefusion.com [206.210.89.201]) (TLS: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Tue, 26 Jun 2007 10:24:50 -0400 id 00056415.468121B2.00002F15 Received: from Internal Mail-Server by mx01 (envelope-from bseklecki@collaborativefusion.com) with RC4-MD5 encrypted SMTP; 26 Jun 2007 09:24:49 -0500 From: "Brian A. Seklecki" To: Koldo Aingeru In-Reply-To: <980beae00706140652o405fb72kef2c0063dcc2e81d@mail.gmail.com> References: <980beae00706140652o405fb72kef2c0063dcc2e81d@mail.gmail.com> Organization: Collaborative Fusion, Inc. Date: Tue, 26 Jun 2007 10:24:49 -0400 Message-Id: <1182867889.67654.16.camel@soundwave.pgh.priv.collaborativefusion.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-Mailer: Evolution 2.6.3 FreeBSD GNOME Team Port x-pineapp-mail-mail-from: bseklecki@collaborativefusion.com x-pineapp-mail-rcpt-to: koldo.aingeru@gmail.com Cc: freebsd-hardware@freebsd.org Subject: Re: Dell Poweredge 1950, boot problem 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, 26 Jun 2007 14:24:51 -0000 We run various Dell PE 8th gen and 9th gen. W/ and W/O the Dell PERC4/PERC5. A lot of 6.2 and 6.1/i386 on the 8th gen, some amd64. All amd64 on the 9th gen. We've never seen this problem. Try 6.2-p3 amd64 instead. Avoid buying these units w/o PERC5. If you're not going to get PERC5, you're better off w/ white box. ~BAS On Thu, 2007-06-14 at 15:52 +0200, Koldo Aingeru wrote: > Hi, > > I just read your message > (http://lists.freebsd.org/pipermail/freebsd-hardware/2006-December/004111.html) > and I have a similar problem with a dell 2850, we have it now running > at safe mode, did you manage to get the problem solved? > > Regards. > > Koldo. > _______________________________________________ > 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" -- Brian A. Seklecki Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. From owner-freebsd-hardware@FreeBSD.ORG Wed Jun 27 19:39:30 2007 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5F29416A400 for ; Wed, 27 Jun 2007 19:39:30 +0000 (UTC) (envelope-from patpro@patpro.net) Received: from postfix1-g20.free.fr (postfix1-g20.free.fr [212.27.60.42]) by mx1.freebsd.org (Postfix) with ESMTP id DDB3913C46A for ; Wed, 27 Jun 2007 19:39:29 +0000 (UTC) (envelope-from patpro@patpro.net) Received: from smtp1-g19.free.fr (smtp1-g19.free.fr [212.27.42.27]) by postfix1-g20.free.fr (Postfix) with ESMTP id 5FB9B146E3FD for ; Wed, 27 Jun 2007 21:16:52 +0200 (CEST) Received: from [192.168.0.4] (boleskine.patpro.net [82.235.12.223]) by smtp1-g19.free.fr (Postfix) with ESMTP id ED39C1AB3C0 for ; Wed, 27 Jun 2007 21:16:50 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v752.2) Content-Transfer-Encoding: 7bit Message-Id: <7D3EA7E7-CF83-4385-A8FC-611B886CC7E3@patpro.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-hardware@freebsd.org From: Patrick Proniewski Date: Wed, 27 Jun 2007 21:16:49 +0200 X-Mailer: Apple Mail (2.752.2) Subject: hardware/driver incompatibility ? 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, 27 Jun 2007 19:39:30 -0000 Hello, Since the end of 2006, I'm running a FreeBSD 6.x on this box: - TYAN Tiger i7520SD motherboard - 2 Intel Xeon LV Sossaman 1,66 GHz - 2 Western Digital WD2500YS hard drives - 1GB RAM Two weeks ago, I've added a DLink DWL-G520 Wifi PCI card (ath chipset), and turned this FreeBSD box into a wifi access point. Then, the PC started to crash from time to time, always when I'm not at home. Today, I've had the 2nd crash. Symptom: the PC crashes and shows an "invalid partition" message when I try to reboot it. The first time, after playing around with the restore tools of the install CD, I've erased the HD, reinstalled, then try to boot... only to read on the screen the infamous "invalid partition" message. I've taken a look into the BIOS, changing boot sequence, saving, re-changing, re-saving. The next reboot was an happy ending. Then I've spent 1 day to restore my various files/ settings/softwares. Today, I was a little bit more lucky, when I came back, the PC was stuck, and the screen read: ad4: FAILURE - device detached subdisk4: detached g_vfs_done():ad4s1f[WRITE(offset=84513456128, length=16384)]error = 6 ad4: det_avcfhse_dd g_vfs_done():ad4s1f... g_vfs_done():ad4s1a... ... ad4 is my boot HD (the other one, ad6, is a backup drive, non-bootable) I've rebooted, discovering ad4 was nowhere to be found (boot sequence was slow, and the BIOS eventually disabled the first HD). I've rebooted again, to enter the bios: first disk still missing shutdown, unplug the 1st HD, reboot, shutdown, plug the 1st HD, reboot -> victory. FreeBSD booted fine, and fsck did its job. Now the box is up & running. No problem so far. I've removed the Wifi PCI card, and removed wifi related settings in rc.conf and loader.conf, just in case. So my question is: is there any known incompatibility between ath related kernel modules and any of my existing hardware, or has my HD suddenly decided to die ? Is there any way I could test my HD to detect/prevent failure ? Any lead/idea is welcome, thanks patpro -- atheros related dmesg lines: ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) ath0: mem 0xd8120000-0xd812ffff irq 21 at device 5.0 on pci6 ath0: Ethernet address: 00:19:5b:ca:31:3a ath0: mac 7.9 phy 4.5 radio 5.6 current /boot/loader.conf: (wifi commented out after today's fix) cpufreq_load = "YES" #if_ath_load="YES" #wlan_wep_load="YES" #wlan_tkip_load="YES" #wlan_ccmp_load="YES" #wlan_xauth_load="YES" #wlan_acl_load="YES" current kldstat: Id Refs Address Size Name 1 8 0xc0400000 3ae6d4 kernel 2 1 0xc07af000 a9d4 cpufreq.ko 3 1 0xc07ba000 59e80 acpi.ko 4 1 0xc5155000 2000 pflog.ko 5 1 0xc515f000 2a000 pf.ko 6 1 0xc52d3000 2000 green_saver.ko current dmesg: Copyright (c) 1992-2007 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-RELEASE-p5 #0: Sat Jun 16 15:51:22 CEST 2007 root@xxxxxxxxxxxxx:/usr/obj/usr/src/sys/PATPRO-20061208 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 000 @ 1.66GHz (1666.79-MHz 686- class CPU) Origin = "GenuineIntel" Id = 0x6e8 Stepping = 8 Features=0xbfebfbff Features2=0xc1a9,> AMD Features=0x100000 Cores per package: 2 real memory = 1072824320 (1023 MB) avail memory = 1040695296 (992 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 est0: on cpu0 p4tcc0: on cpu0 cpu1: on acpi0 est1: on cpu1 p4tcc1: on cpu1 cpu2: on acpi0 est2: on cpu2 p4tcc2: on cpu2 cpu3: on acpi0 est3: on cpu3 p4tcc3: on cpu3 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 1.0 (no driver attached) pcib1: irq 16 at device 2.0 on pci0 pci1: on pcib1 pcib2: irq 16 at device 4.0 on pci0 pci2: on pcib2 pcib3: irq 16 at device 5.0 on pci0 pci3: on pcib3 em0: port 0x2000-0x201f mem 0xd8020000-0xd803ffff,0xd8000000-0xd801ffff irq 16 at device 0.0 on pc i3 em0: Ethernet address: 00:e0:81:42:e3:aa em1: port 0x2020-0x203f mem 0xd8060000-0xd807ffff,0xd8040000-0xd805ffff irq 17 at device 0.1 on pc i3 em1: Ethernet address: 00:e0:81:42:e3:ab pcib4: irq 16 at device 6.0 on pci0 pci4: on pcib4 pcib5: at device 28.0 on pci0 pci5: on pcib5 uhci0: port 0x1400-0x141f 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 0x1420-0x143f 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 pci0: at device 29.4 (no driver attached) pci0: at device 29.5 (no driver attached) ehci0: mem 0xd8402400-0xd84027ff irq 23 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb2: EHCI version 1.0 usb2: companion controllers, 2 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub2: 4 ports with 4 removable, self powered pcib6: at device 30.0 on pci0 pci6: on pcib6 fxp0: port 0x3400-0x343f mem 0xd8130000-0xd8130fff,0xd8100000-0xd811ffff irq 16 at device 0.0 on pci6 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:e0:81:42:e3:69 pci6: at device 12.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1460-0x146f at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 atapci1: port 0xf4a8-0xf4af, 0xf49c-0xf49f,0xf4a0-0xf4a7,0xf498-0xf49b,0xf470-0xf47f irq 18 at device 31.2 on pci0 ata2: on atapci1 ata3: on atapci1 ichsmb0: port 0x1440-0x145f irq 17 at device 31.3 on pci0 ichsmb0: [GIANT-LOCKED] smbus0: on ichsmb0 smb0: on smbus0 acpi_button0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] 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,0x778-0x77f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: on ppc0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 pmtimer0 on isa0 orm0: at iomem 0xc0000-0xc8fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec acd0: CDROM at ata1-master PIO4 ad4: 239372MB at ata2-master SATA150 ad6: 239372MB at ata3-master SATA150 SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #3 Launched! Trying to mount root from ufs:/dev/ad4s1a From owner-freebsd-hardware@FreeBSD.ORG Thu Jun 28 04:43:44 2007 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6EE8316A41F for ; Thu, 28 Jun 2007 04:43:44 +0000 (UTC) (envelope-from soralx@cydem.org) Received: from cydem.org (S01060060977141e2.vc.shawcable.net [24.87.15.201]) by mx1.freebsd.org (Postfix) with ESMTP id 375D013C447 for ; Thu, 28 Jun 2007 04:43:00 +0000 (UTC) (envelope-from soralx@cydem.org) Received: from soralx (soralx [192.168.0.240]) by cydem.org (Postfix/FreeBSD) with ESMTP id 1A47A7ECF8 for ; Wed, 27 Jun 2007 21:43:02 -0700 (PDT) Date: Wed, 27 Jun 2007 21:43:00 -0700 From: To: Message-ID: <20070627214300.319cbe41@soralx> In-Reply-To: <7D3EA7E7-CF83-4385-A8FC-611B886CC7E3@patpro.net> References: <7D3EA7E7-CF83-4385-A8FC-611B886CC7E3@patpro.net> X-Mailer: Claws Mail 2.9.1 (GTK+ 2.10.12; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: hardware/driver incompatibility ? 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, 28 Jun 2007 04:43:44 -0000 > - 2 Western Digital WD2500YS hard drives > - 1GB RAM [...] > Is there any way I could test my HD to detect/prevent failure ? install smartmontools from ports then: smarctl -t long /dev/ad4 after a couple hours check status: smartctl -a /dev/ad4 Western Digital harddisks are notoriously unreliable (I just had 2 WD5000YS fail recently, at about the same time; one had ~200 hrs on it, the other ~1700h), especially the YS models. Also, WDC won't replace them... Beware. [SorAlx] ridin' VN1500-B2 From owner-freebsd-hardware@FreeBSD.ORG Thu Jun 28 07:06:02 2007 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F41E116A46B for ; Thu, 28 Jun 2007 07:06:01 +0000 (UTC) (envelope-from patpro@patpro.net) Received: from smtp.univ-lyon2.fr (smtp.univ-lyon2.fr [159.84.143.102]) by mx1.freebsd.org (Postfix) with ESMTP id B5E7D13C45D for ; Thu, 28 Jun 2007 07:06:01 +0000 (UTC) (envelope-from patpro@patpro.net) Received: from localhost (localhost [127.0.0.1]) by smtp.univ-lyon2.fr (Postfix) with ESMTP id 18D543A720CC; Thu, 28 Jun 2007 08:44:26 +0200 (CEST) X-Virus-Scanned: amavisd-new at univ-lyon2.fr Received: from smtp.univ-lyon2.fr ([127.0.0.1]) by localhost (smtp.univ-lyon2.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GYfQ0jPtlsmU; Thu, 28 Jun 2007 08:44:24 +0200 (CEST) Received: from [159.84.148.60] (patpro.univ-lyon2.fr [159.84.148.60]) by smtp.univ-lyon2.fr (Postfix) with ESMTP id ACE473A720C5; Thu, 28 Jun 2007 08:44:24 +0200 (CEST) In-Reply-To: <20070627214300.319cbe41@soralx> References: <7D3EA7E7-CF83-4385-A8FC-611B886CC7E3@patpro.net> <20070627214300.319cbe41@soralx> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <5F2FFD72-768A-44E0-933B-87E725491E79@patpro.net> Content-Transfer-Encoding: 7bit From: Patrick Proniewski Date: Thu, 28 Jun 2007 07:38:05 +0200 To: freebsd-hardware@freebsd.org X-Mailer: Apple Mail (2.752.2) Cc: Subject: Re: hardware/driver incompatibility ? 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, 28 Jun 2007 07:06:02 -0000 On 28 juin 07, at 06:43, wrote: >> Is there any way I could test my HD to detect/prevent failure ? > > install smartmontools from ports > then: smarctl -t long /dev/ad4 > after a couple hours check status: smartctl -a /dev/ad4 I've tested the disk after the crash with smartmontools (long, short, ...), but nothing, no error. But I know a passed SMART test does not mean anything. > Western Digital harddisks are notoriously unreliable (I just had 2 > WD5000YS fail recently, at about the same time; one had ~200 hrs on > it, > the other ~1700h), especially the YS models. Also, WDC won't replace > them... Beware. argh, crap. Too bad Maxtor Maxline III drives where not available at the time I bought all this hardware. thanks, patpro From owner-freebsd-hardware@FreeBSD.ORG Sat Jun 30 02:55:15 2007 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B0D0016A421 for ; Sat, 30 Jun 2007 02:55:15 +0000 (UTC) (envelope-from conrads@cox.net) Received: from eastrmmtao104.cox.net (eastrmmtao104.cox.net [68.230.240.46]) by mx1.freebsd.org (Postfix) with ESMTP id 6BFD413C465 for ; Sat, 30 Jun 2007 02:55:15 +0000 (UTC) (envelope-from conrads@cox.net) Received: from eastrmimpo01.cox.net ([68.1.16.119]) by eastrmmtao106.cox.net (InterMail vM.7.08.02.01 201-2186-121-102-20070209) with ESMTP id <20070630022044.RZBI1381.eastrmmtao106.cox.net@eastrmimpo01.cox.net> for ; Fri, 29 Jun 2007 22:20:44 -0400 Received: from serene.no-ip.org ([72.200.17.85]) by eastrmimpo01.cox.net with bizsmtp id HeLk1X0061q7YRk0000000; Fri, 29 Jun 2007 22:20:44 -0400 Received: from serene.no-ip.org (localhost [127.0.0.1]) by serene.no-ip.org (8.14.1/8.14.1) with ESMTP id l5U2Ki3q032669 for ; Fri, 29 Jun 2007 21:20:44 -0500 (CDT) (envelope-from conrads@cox.net) Message-Id: <200706300220.l5U2Ki3q032669@serene.no-ip.org> Date: Fri, 29 Jun 2007 21:20:38 -0500 From: "Conrad J. Sabatier" To: freebsd-hardware@FreeBSD.org X-Mailer: Claws Mail 2.9.2 (GTK+ 2.10.13; amd64-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: Need help/advice on memory upgrade for HP Pavilion a530n 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, 30 Jun 2007 02:55:15 -0000 I just discovered the dmidecode utilities this evening and ran them on my machine. Can someone possibly help me understand the output below? Every online source states that this machine (HP Pavilion a530n) is limited to a maximum of either 1 or 2 GB of memory (the OEM says 1, others say 2; which is it already, folks?), using two DIMM sockets (I currently have 1 GB installed, using two 512 MB modules). The "Memory Controller Information" below seems to support the claim of a 1 GB limit. But then, further down, the "Physical Memory Array" section lists a 4 GB capacity. I'm really not very well-versed in memory lingo, and am utterly confused at the moment. Am I currently "maxed out" at 1 GB, or could I safely upgrade to 2 or even 4 GB? Help! :-) Here's the relevant output from dmidecode: # dmidecode 2.8 SMBIOS 2.3 present. Handle 0x0008, DMI type 5, 20 bytes Memory Controller Information Error Detecting Method: 64-bit ECC Error Correcting Capabilities: None Supported Interleave: One-way Interleave Current Interleave: One-way Interleave Maximum Memory Module Size: 512 MB Maximum Total Memory Size: 1024 MB Supported Speeds: 70 ns 60 ns Supported Memory Types: SIMM DIMM SDRAM Memory Module Voltage: 3.3 V Associated Memory Slots: 2 0x0009 0x000A Enabled Error Correcting Capabilities: None Handle 0x0009, DMI type 6, 12 bytes Memory Module Information Socket Designation: DIMM0 Bank Connections: 1 0 Current Speed: Unknown Type: DIMM SDRAM Installed Size: 512 MB (Double-bank Connection) Enabled Size: 512 MB (Double-bank Connection) Error Status: OK Handle 0x000A, DMI type 6, 12 bytes Memory Module Information Socket Designation: DIMM1 Bank Connections: 3 2 Current Speed: Unknown Type: DIMM SDRAM Installed Size: 512 MB (Single-bank Connection) Enabled Size: 512 MB (Single-bank Connection) Error Status: OK Handle 0x002A, DMI type 16, 15 bytes Physical Memory Array Location: System Board Or Motherboard Use: System Memory Error Correction Type: None Maximum Capacity: 4 GB Error Information Handle: Not Provided Number Of Devices: 2 Handle 0x002C, DMI type 17, 27 bytes Memory Device Array Handle: 0x002A Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 512 MB Form Factor: DIMM Set: None Locator: DIMM0 Bank Locator: BANK0 Type: SDRAM Type Detail: Synchronous Speed: Unknown Manufacturer: Manufacturer0 Serial Number: SerNum0 Asset Tag: AssetTagNum0 Part Number: PartNum0 Handle 0x002E, DMI type 17, 27 bytes Memory Device Array Handle: 0x002A Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 512 MB Form Factor: DIMM Set: None Locator: DIMM1 Bank Locator: BANK1 Type: SDRAM Type Detail: Synchronous Speed: Unknown Manufacturer: Manufacturer1 Serial Number: SerNum1 Asset Tag: AssetTagNum1 Part Number: PartNum1 -- Conrad J. Sabatier