From janskey_boy at yahoo.com Mon Jun 2 21:12:20 2008 From: janskey_boy at yahoo.com (janskey) Date: Mon Jun 2 23:13:02 2008 Subject: Dell Inspiron 1420 Message-ID: <932340.12291.qm@web51709.mail.re2.yahoo.com> Hi All, Does anyone tried installing freebsd 7.0 on Dell Inspiron 1420? Does all the drivers support? Thanks! cheers, janskey From aymeric.muntz at free.fr Thu Jun 5 17:28:02 2008 From: aymeric.muntz at free.fr (Aymeric MUNTZ) Date: Thu Jun 5 17:28:06 2008 Subject: ATHEROS AR8012 10/100 Mbps PHY Message-ID: <001901c8c72e$47714dd0$0101a8c0@artemis> Hi guys, I got a FBSD 5.4 box which I have to change the motherboard. It seams that it doesn't recognize the ATHEROS AR8012 10/100 Mbps PHY Anyone has any information about that? Thanks From brueffer at FreeBSD.org Fri Jun 6 07:20:54 2008 From: brueffer at FreeBSD.org (Christian Brueffer) Date: Fri Jun 6 07:21:05 2008 Subject: ATHEROS AR8012 10/100 Mbps PHY In-Reply-To: <001901c8c72e$47714dd0$0101a8c0@artemis> References: <001901c8c72e$47714dd0$0101a8c0@artemis> Message-ID: <20080606065050.GA1429@haakonia.hitnet.RWTH-Aachen.DE> On Thu, Jun 05, 2008 at 07:04:55PM +0200, Aymeric MUNTZ wrote: > Hi guys, > > > > I got a FBSD 5.4 box which I have to change the motherboard. > > It seams that it doesn't recognize the ATHEROS AR8012 10/100 Mbps PHY > > > > Anyone has any information about that? > Hi Aymeric, the FreeBSD release you're using is very old, so there's no driver support for your chip. In fact the driver that's likely to support it (age(4)) is only in CURRENT at the moment but will probably be merged to the STABLE branches soon. Could you provide the output of pciconf -lv so we can determine if your chip is supported by the age(4) driver? I have CCed Pyun YongHyeon, the age(4) driver writer, for additional insight. - Christian -- Christian Brueffer chris@unixpages.org brueffer@FreeBSD.org GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-hardware/attachments/20080606/46971cbd/attachment.pgp From randy at psg.com Fri Jun 6 15:40:04 2008 From: randy at psg.com (Randy Bush) Date: Fri Jun 6 15:40:06 2008 Subject: 3ware 9550sx adding drives to raid Message-ID: <48495A4A.1050503@psg.com> i have a 9550sx with a raid5. i want to add some drives to the running raid. there seems to be some cute trust-a-massive-gui path using the java based app setupFreeBSD_x86.sh. the install looks to bring in 42% of the ports tree. is there some useful simpler way to do this? is there a way to just do it with tw_cli that i am missing? randy From pyunyh at gmail.com Sat Jun 7 03:06:31 2008 From: pyunyh at gmail.com (Pyun YongHyeon) Date: Sat Jun 7 03:06:35 2008 Subject: ATHEROS AR8012 10/100 Mbps PHY In-Reply-To: <20080606065050.GA1429@haakonia.hitnet.RWTH-Aachen.DE> References: <001901c8c72e$47714dd0$0101a8c0@artemis> <20080606065050.GA1429@haakonia.hitnet.RWTH-Aachen.DE> Message-ID: <20080607023813.GB4565@cdnetworks.co.kr> On Fri, Jun 06, 2008 at 08:50:51AM +0200, Christian Brueffer wrote: > On Thu, Jun 05, 2008 at 07:04:55PM +0200, Aymeric MUNTZ wrote: > > Hi guys, > > > > > > > > I got a FBSD 5.4 box which I have to change the motherboard. > > > > It seams that it doesn't recognize the ATHEROS AR8012 10/100 Mbps PHY age(4) supports L1 Gigabit ethernet. It seems that your hardware might be Attansic/Atheros L2 fast ethernet which is not yet supported by FreeBSD. Supporting L2 wouldn't be hard as both OpenBSD/NetBSD already have a driver, lii(4). I don't have a L2 hardware so porting/writing a L2 driver is beyond scope of my ability. As Christian Brueffer said, knowing the output of pciconf -lvc would be big help to identify which hardware you've got. > > > > > > > > Anyone has any information about that? > > > > Hi Aymeric, > > the FreeBSD release you're using is very old, so there's no driver > support for your chip. In fact the driver that's likely to support > it (age(4)) is only in CURRENT at the moment but will probably be merged > to the STABLE branches soon. > Could you provide the output of pciconf -lv so we can determine if your > chip is supported by the age(4) driver? > > I have CCed Pyun YongHyeon, the age(4) driver writer, for additional insight. > > - Christian > > -- > Christian Brueffer chris@unixpages.org brueffer@FreeBSD.org > GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc > GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D -- Regards, Pyun YongHyeon From rpaulo at FreeBSD.org Sat Jun 7 10:52:44 2008 From: rpaulo at FreeBSD.org (Rui Paulo) Date: Sat Jun 7 10:52:48 2008 Subject: ATHEROS AR8012 10/100 Mbps PHY In-Reply-To: <20080607023813.GB4565@cdnetworks.co.kr> References: <001901c8c72e$47714dd0$0101a8c0@artemis> <20080606065050.GA1429@haakonia.hitnet.RWTH-Aachen.DE> <20080607023813.GB4565@cdnetworks.co.kr> Message-ID: <20080607105234.GA9282@epsilon.local> On Sat, Jun 07, 2008 at 11:38:13AM +0900, Pyun YongHyeon wrote: > On Fri, Jun 06, 2008 at 08:50:51AM +0200, Christian Brueffer wrote: > > On Thu, Jun 05, 2008 at 07:04:55PM +0200, Aymeric MUNTZ wrote: > > > Hi guys, > > > > > > > > > > > > I got a FBSD 5.4 box which I have to change the motherboard. > > > > > > It seams that it doesn't recognize the ATHEROS AR8012 10/100 Mbps PHY > > age(4) supports L1 Gigabit ethernet. It seems that your hardware > might be Attansic/Atheros L2 fast ethernet which is not yet > supported by FreeBSD. Supporting L2 wouldn't be hard as both > OpenBSD/NetBSD already have a driver, lii(4). I don't have a L2 > hardware so porting/writing a L2 driver is beyond scope of my > ability. I'm thinking about buying a Eee PC. So, I'll be able to do the port if no one has done it before. -- Rui Paulo From jrhett at netconsonance.com Sat Jun 7 19:45:52 2008 From: jrhett at netconsonance.com (Jo Rhett) Date: Sat Jun 7 19:45:56 2008 Subject: 3ware 9550sx adding drives to raid In-Reply-To: <48495A4A.1050503@psg.com> References: <48495A4A.1050503@psg.com> Message-ID: <6C59E050-A343-435A-9074-F94007281247@netconsonance.com> On Jun 6, 2008, at 8:39 AM, Randy Bush wrote: > i have a 9550sx with a raid5. i want to add some drives to the > running > raid. there seems to be some cute trust-a-massive-gui path using the > java based app setupFreeBSD_x86.sh. the install looks to bring in 42% > of the ports tree. is there some useful simpler way to do this? is > there a way to just do it with tw_cli that i am missing? You can do *everything* the controller can do with just tw_cli. Off the top of my head, something like /c0/u0 add drive=N <- where N is drive port number from "show" -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness From pyunyh at gmail.com Sun Jun 8 01:44:46 2008 From: pyunyh at gmail.com (Pyun YongHyeon) Date: Sun Jun 8 01:44:50 2008 Subject: ATHEROS AR8012 10/100 Mbps PHY In-Reply-To: <20080607105234.GA9282@epsilon.local> References: <001901c8c72e$47714dd0$0101a8c0@artemis> <20080606065050.GA1429@haakonia.hitnet.RWTH-Aachen.DE> <20080607023813.GB4565@cdnetworks.co.kr> <20080607105234.GA9282@epsilon.local> Message-ID: <20080608014438.GA8825@cdnetworks.co.kr> On Sat, Jun 07, 2008 at 11:52:34AM +0100, Rui Paulo wrote: > On Sat, Jun 07, 2008 at 11:38:13AM +0900, Pyun YongHyeon wrote: > > On Fri, Jun 06, 2008 at 08:50:51AM +0200, Christian Brueffer wrote: > > > On Thu, Jun 05, 2008 at 07:04:55PM +0200, Aymeric MUNTZ wrote: > > > > Hi guys, > > > > > > > > > > > > > > > > I got a FBSD 5.4 box which I have to change the motherboard. > > > > > > > > It seams that it doesn't recognize the ATHEROS AR8012 10/100 Mbps PHY > > > > age(4) supports L1 Gigabit ethernet. It seems that your hardware > > might be Attansic/Atheros L2 fast ethernet which is not yet > > supported by FreeBSD. Supporting L2 wouldn't be hard as both > > OpenBSD/NetBSD already have a driver, lii(4). I don't have a L2 > > hardware so porting/writing a L2 driver is beyond scope of my > > ability. > > I'm thinking about buying a Eee PC. So, I'll be able to do the port if no one > has done it before. Great! I received too many mails requesting for L2 driver. Now I can forward these mails to you. :-) > > -- > Rui Paulo -- Regards, Pyun YongHyeon From randy at psg.com Sun Jun 8 07:41:46 2008 From: randy at psg.com (Randy Bush) Date: Sun Jun 8 07:41:48 2008 Subject: 3dm2 connection reset (was: 3ware 9550sx adding drives to raid) In-Reply-To: <2hsj44drtoktgrcb6ud3nn6tovent3qqrf@4ax.com> References: <48495A4A.1050503@psg.com> <2hsj44drtoktgrcb6ud3nn6tovent3qqrf@4ax.com> Message-ID: <484B8D38.3050400@psg.com> thanks to a whack from mike at sentex.net i stopped trying to install the 3DM2_CLI-FreeBSD_x86-9.5.0.1.tgz monster from the 3ware site and simply installed the port (on i386 current). but after entering the 3ware password, my browser gets a connection reset. i am on macos 10.5.3, with firefox2, and i did hack the all.js, though it seemed unneeded. java* and cookies afre enabled. randy From rpaulo at FreeBSD.org Sun Jun 8 12:11:18 2008 From: rpaulo at FreeBSD.org (Rui Paulo) Date: Sun Jun 8 12:11:22 2008 Subject: ATHEROS AR8012 10/100 Mbps PHY In-Reply-To: <20080608014438.GA8825@cdnetworks.co.kr> References: <001901c8c72e$47714dd0$0101a8c0@artemis> <20080606065050.GA1429@haakonia.hitnet.RWTH-Aachen.DE> <20080607023813.GB4565@cdnetworks.co.kr> <20080607105234.GA9282@epsilon.local> <20080608014438.GA8825@cdnetworks.co.kr> Message-ID: <20080608121109.GA30926@epsilon.local> On Sun, Jun 08, 2008 at 10:44:38AM +0900, Pyun YongHyeon wrote: > Great! I received too many mails requesting for L2 driver. > Now I can forward these mails to you. :-) Okay. :-) I have contacted the EeeBSD guy because he says that someone is already porting it, but he doesn't know the status of it. This was last month, so I'm guessing nothing will come out of it. I decided to import the lli driver from NetBSD into my p4 user space. Regards, -- Rui Paulo From gary.wilson at coull.com Sun Jun 8 12:12:11 2008 From: gary.wilson at coull.com (Gary Wilson) Date: Sun Jun 8 12:12:25 2008 Subject: Intel 82571EB NIC Message-ID: I have been trying to determine (pre-purchasing) whether an Intel 82571EB - PRO/1000 PF Dual Port Server Adaptor will work with: FreeBSD 6.2-RELEASE-p11 i386 I am setting up a pfsense firewall and need a fiber NIC, the current documentation on 6.2R for both (i386 and ia64) mention that: "The em(4) driver supports Gigabit Ethernet adapters based on the Intel 82540, 82541ER, 82541PI, 82542, 82543, 82544, 82545, 82546, 82546EB, 82546GB, 82547, 82571, 82572 and 82573 controller chips", but this makes no specific reference to the 82571EB which is an LC Fiber Gigabit card. A search of the mailing lists has not clarified the issue for me, would anyone be able to advise me as to whether this NIC works on 6.2. Thanks in advance. Gary From koitsu at FreeBSD.org Sun Jun 8 13:09:46 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Sun Jun 8 13:09:49 2008 Subject: Intel 82571EB NIC In-Reply-To: References: Message-ID: <20080608130945.GA60675@eos.sc1.parodius.com> On Sun, Jun 08, 2008 at 01:00:03PM +0100, Gary Wilson wrote: > I have been trying to determine (pre-purchasing) whether an Intel > 82571EB - PRO/1000 PF Dual Port Server Adaptor will work with: > > FreeBSD 6.2-RELEASE-p11 i386 > > I am setting up a pfsense firewall and need a fiber NIC, the current > documentation on 6.2R for both (i386 and ia64) mention that: > > "The em(4) driver supports Gigabit Ethernet adapters based on the Intel > 82540, 82541ER, 82541PI, 82542, 82543, 82544, 82545, 82546, 82546EB, > 82546GB, 82547, 82571, 82572 and 82573 controller chips", but this makes I see 82571 listed in the above list. However, I'm not sure if the EB revision is different enough to justify separate mention. The em(4) driver does appear to have some fibre support, indicated via the "1000baseSX" operational mode. I've CC'd Jack Vogel, author of the em(4) driver, to confirm or deny support for the LC fibre model. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From jfvogel at gmail.com Mon Jun 9 03:51:07 2008 From: jfvogel at gmail.com (Jack Vogel) Date: Mon Jun 9 03:51:10 2008 Subject: Intel 82571EB NIC In-Reply-To: <20080608130945.GA60675@eos.sc1.parodius.com> References: <20080608130945.GA60675@eos.sc1.parodius.com> Message-ID: <2a41acea0806082022y48c31f65qd59b724fa80c43c8@mail.gmail.com> On Sun, Jun 8, 2008 at 6:09 AM, Jeremy Chadwick wrote: > On Sun, Jun 08, 2008 at 01:00:03PM +0100, Gary Wilson wrote: >> I have been trying to determine (pre-purchasing) whether an Intel >> 82571EB - PRO/1000 PF Dual Port Server Adaptor will work with: >> >> FreeBSD 6.2-RELEASE-p11 i386 >> >> I am setting up a pfsense firewall and need a fiber NIC, the current >> documentation on 6.2R for both (i386 and ia64) mention that: >> >> "The em(4) driver supports Gigabit Ethernet adapters based on the Intel >> 82540, 82541ER, 82541PI, 82542, 82543, 82544, 82545, 82546, 82546EB, >> 82546GB, 82547, 82571, 82572 and 82573 controller chips", but this makes > > I see 82571 listed in the above list. However, I'm not sure if the EB > revision is different enough to justify separate mention. > > The em(4) driver does appear to have some fibre support, indicated via > the "1000baseSX" operational mode. > > I've CC'd Jack Vogel, author of the em(4) driver, to confirm or deny > support for the LC fibre model. Yes, it is supported although not common, it should work no problem. Jack From gary.wilson at coull.com Mon Jun 9 09:41:18 2008 From: gary.wilson at coull.com (Gary Wilson) Date: Mon Jun 9 09:41:34 2008 Subject: Intel 82571EB NIC In-Reply-To: <2a41acea0806082022y48c31f65qd59b724fa80c43c8@mail.gmail.com> References: <20080608130945.GA60675@eos.sc1.parodius.com> <2a41acea0806082022y48c31f65qd59b724fa80c43c8@mail.gmail.com> Message-ID: Thank you both! That is great news. Take it easy. -----Original Message----- From: Jack Vogel [mailto:jfvogel@gmail.com] Sent: 09 June 2008 04:22 To: Jeremy Chadwick Cc: Gary Wilson; freebsd-hardware@freebsd.org Subject: Re: Intel 82571EB NIC On Sun, Jun 8, 2008 at 6:09 AM, Jeremy Chadwick wrote: > On Sun, Jun 08, 2008 at 01:00:03PM +0100, Gary Wilson wrote: >> I have been trying to determine (pre-purchasing) whether an Intel >> 82571EB - PRO/1000 PF Dual Port Server Adaptor will work with: >> >> FreeBSD 6.2-RELEASE-p11 i386 >> >> I am setting up a pfsense firewall and need a fiber NIC, the current >> documentation on 6.2R for both (i386 and ia64) mention that: >> >> "The em(4) driver supports Gigabit Ethernet adapters based on the Intel >> 82540, 82541ER, 82541PI, 82542, 82543, 82544, 82545, 82546, 82546EB, >> 82546GB, 82547, 82571, 82572 and 82573 controller chips", but this makes > > I see 82571 listed in the above list. However, I'm not sure if the EB > revision is different enough to justify separate mention. > > The em(4) driver does appear to have some fibre support, indicated via > the "1000baseSX" operational mode. > > I've CC'd Jack Vogel, author of the em(4) driver, to confirm or deny > support for the LC fibre model. Yes, it is supported although not common, it should work no problem. Jack From bg1tpt at gmail.com Mon Jun 9 14:14:16 2008 From: bg1tpt at gmail.com (Razor) Date: Mon Jun 9 14:14:20 2008 Subject: The wireless card can not use after I upgrade to 8-CURRENT. IBM THINKPAD T23 Message-ID: <5e81405d0806090649y7e615b93i3d97be08e29c42cf@mail.gmail.com> The card works well in FreeBSD 7.0-RELEASE. After I upgrade to 8-CURRENT. The wlan0 can not associate with my AP. Here is my rc.conf and wpa_supplicant.conf rc.conf: wlans_wi0=wlan0 ifconfig_wlan0="WPA DHCP" /etc/wpa_supplicant.conf: ctrl_interface=/var/run/wpa_supplicant network={ ssid="FreeBSD" scan_ssid=1 key_mgmt=NONE wep_tx_keyidx=0 wep_key0=ABCDEF01234567890ABCDEF012 } ifconfig wi0: wi0: flags=8843 metric 0 mtu 2290 ether 00:20:e0:8a:2d:88 media: IEEE 802.11 Wireless Ethernet autoselect mode 11b status: associated ifconfig wlan0: wlan0: flags=8843 metric 0 mtu 1500 ether 00:20:e0:8a:2d:88 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ssid "" channel 10 (2457 Mhz 11b) country US authmode WPA1+WPA2/802.11i privacy ON deftxkey UNDEF txpower 0 bmiss 7 scanvalid 60 roaming MANUAL bintval 0 From janskey_boy at yahoo.com Tue Jun 10 01:17:56 2008 From: janskey_boy at yahoo.com (janskey) Date: Tue Jun 10 01:46:21 2008 Subject: NIC driver not found - dell inspiron 1420 Message-ID: <966916.7263.qm@web51712.mail.re2.yahoo.com> Hi All, I'm trying to install freebsd 7.0 to my new dell inspiron 1420 laptop. Along the way of the installation, I encounter problem on my NIC (broadcom 59xx) that is not been detected. Any advice on how to fix this? Does freebsd 7 support this laptop model? Thanks! cheers, janskey From janskey_boy at yahoo.com Tue Jun 10 01:24:50 2008 From: janskey_boy at yahoo.com (janskey) Date: Tue Jun 10 01:53:48 2008 Subject: NIC driver not found - dell inspiron 1420 Message-ID: <997924.32077.qm@web51702.mail.re2.yahoo.com> Hi All, I'm trying to install freebsd 7.0 to my new dell inspiron 1420 laptop. Along the way of the installation, I encounter problem on my NIC (broadcom 59xx) that is not been detected. Any advice on how to fix this? Does freebsd 7 support this laptop model? Thanks! cheers, janskey From sam at freebsd.org Tue Jun 10 16:29:46 2008 From: sam at freebsd.org (Sam Leffler) Date: Tue Jun 10 16:29:49 2008 Subject: The wireless card can not use after I upgrade to 8-CURRENT. IBM THINKPAD T23 In-Reply-To: <5e81405d0806090649y7e615b93i3d97be08e29c42cf@mail.gmail.com> References: <5e81405d0806090649y7e615b93i3d97be08e29c42cf@mail.gmail.com> Message-ID: <484EA968.60303@freebsd.org> Razor wrote: > The card works well in FreeBSD 7.0-RELEASE. After I upgrade to > 8-CURRENT. The wlan0 can not associate with my AP. Here is my rc.conf > and wpa_supplicant.conf > > rc.conf: > > wlans_wi0=wlan0 > ifconfig_wlan0="WPA DHCP" > > /etc/wpa_supplicant.conf: > ctrl_interface=/var/run/wpa_supplicant > network={ > ssid="FreeBSD" > scan_ssid=1 > key_mgmt=NONE > wep_tx_keyidx=0 > wep_key0=ABCDEF01234567890ABCDEF012 > } > > ifconfig wi0: > wi0: flags=8843 metric 0 mtu 2290 > ether 00:20:e0:8a:2d:88 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11b > status: associated > > ifconfig wlan0: > wlan0: flags=8843 metric 0 mtu 1500 > ether 00:20:e0:8a:2d:88 > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) > status: no carrier > ssid "" channel 10 (2457 Mhz 11b) > country US authmode WPA1+WPA2/802.11i privacy ON deftxkey UNDEF > txpower 0 bmiss 7 scanvalid 60 roaming MANUAL bintval 0 > Intersil prism cards should work fine though they may require a firmware upgrade to ~rev 1.7. Unfortunately you've not shown the boot messages for the wi device so there's no way to tell what card you have. Other devices that used to be supported by wi were broken in the vap conversion. Someone else will need to step up and fix the driver to support them; I have no time right now. Sam From bg1tpt at gmail.com Tue Jun 10 17:07:10 2008 From: bg1tpt at gmail.com (Razor) Date: Tue Jun 10 17:07:14 2008 Subject: The wireless card can not use after I upgrade to 8-CURRENT. IBM THINKPAD T23 In-Reply-To: <484EA968.60303@freebsd.org> References: <5e81405d0806090649y7e615b93i3d97be08e29c42cf@mail.gmail.com> <484EA968.60303@freebsd.org> Message-ID: <5e81405d0806101007t1f86a481vee58b95c3c882a03@mail.gmail.com> OK, Thanks. And here is my boot messages of wi0: wi0: mem 0xec000000-0xec000fff irq 11 at device 2.0 on pci2 wi0: [ITHREAD] wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI) wi0: Intersil Firmware: Primary (1.1.0), Station (1.4.2) On Wed, Jun 11, 2008 at 12:18 AM, Sam Leffler wrote: > Razor wrote: >> >> The card works well in FreeBSD 7.0-RELEASE. After I upgrade to >> 8-CURRENT. The wlan0 can not associate with my AP. Here is my rc.conf >> and wpa_supplicant.conf >> >> rc.conf: >> >> wlans_wi0=wlan0 >> ifconfig_wlan0="WPA DHCP" >> >> /etc/wpa_supplicant.conf: >> ctrl_interface=/var/run/wpa_supplicant >> network={ >> ssid="FreeBSD" >> scan_ssid=1 >> key_mgmt=NONE >> wep_tx_keyidx=0 >> wep_key0=ABCDEF01234567890ABCDEF012 >> } >> >> ifconfig wi0: >> wi0: flags=8843 metric 0 mtu 2290 >> ether 00:20:e0:8a:2d:88 >> media: IEEE 802.11 Wireless Ethernet autoselect mode 11b >> status: associated >> >> ifconfig wlan0: >> wlan0: flags=8843 metric 0 mtu >> 1500 >> ether 00:20:e0:8a:2d:88 >> media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) >> status: no carrier >> ssid "" channel 10 (2457 Mhz 11b) >> country US authmode WPA1+WPA2/802.11i privacy ON deftxkey UNDEF >> txpower 0 bmiss 7 scanvalid 60 roaming MANUAL bintval 0 >> > > Intersil prism cards should work fine though they may require a firmware > upgrade to ~rev 1.7. Unfortunately you've not shown the boot messages for > the wi device so there's no way to tell what card you have. > > Other devices that used to be supported by wi were broken in the vap > conversion. Someone else will need to step up and fix the driver to support > them; I have no time right now. > > Sam > > From lfrigault at agneau.org Thu Jun 12 10:42:42 2008 From: lfrigault at agneau.org (Laurent Frigault) Date: Thu Jun 12 10:42:46 2008 Subject: Dell poweredge 1950 iii Message-ID: <20080612102329.GA63230@obelix.bergerie.agneau.org> Hi, Does anyone tried installing FreeBSD 7.0 on Dell poweredge 1950 iii? Any dmesg.boot for this hardware ? Is there any known issue with it ? Regards, -- Laurent Frigault | From freebsd at n9.ru Thu Jun 12 14:13:10 2008 From: freebsd at n9.ru (FreeBSD) Date: Thu Jun 12 14:13:17 2008 Subject: twe0 interrupt storm Message-ID: <319048390806120643n2033cfd1m795eaaf414c9f15c@mail.gmail.com> Hi, I have problem on FreeBSD 6.2, 7.0 with 3ware 8006-2LP RAID-1 controller: Model 8006-2LP Serial # L018501C7271467 Firmware FE8S 1.05.00.068 Driver 1.50.01.002 BIOS BE7X 1.08.00.048 Monitor ME7X 1.01.00.040 Memory Installed 512 kB # of Ports 2 # of Drives 2 # of Units 1 Jun 11 21:38:00 gans kernel: twe0: <3ware Storage Controller. Driver version 1.50.01.002> port 0xe800-0xe80f mem 0xfebffc00-0xfebffc0f,0xfe000000-0xfe7fffff irq 20 at device 2.0 on pci3 Jun 11 21:38:00 gans kernel: twe0: [GIANT-LOCKED] Jun 11 21:38:00 gans kernel: twe0: [ITHREAD] Jun 11 21:38:00 gans kernel: twe0: 2 ports, Firmware FE8S 1.05.00.068, BIOS BE7X 1.08.00.048 /var/log/messages Jun 10 14:51:36 gans kernel: interrupt storm detected on "irq21:"; throttling interrupt source Jun 10 14:52:07 gans last message repeated 31 times Jun 10 14:54:08 gans last message repeated 121 times Jun 10 15:04:09 gans last message repeated 598 times Jun 10 15:14:10 gans last message repeated 599 times Jun 10 15:24:11 gans last message repeated 600 times Jun 10 15:34:12 gans last message repeated 598 times Jun 10 15:44:13 gans last message repeated 598 times Jun 10 15:54:14 gans last message repeated 600 times Jun 10 16:04:15 gans last message repeated 600 times Jun 10 16:14:16 gans last message repeated 599 times Jun 10 16:24:17 gans last message repeated 598 times [root@gans /home/sg]# vmstat -w 5 procs memory page disk faults cpu r b w avm fre flt re pi po fr sr tw0 in sy cs us sy id 8 3 0 5389M 220M 1410 23 5 3 809 1762 0 11200 1377 3451 26 15 59 7 5 0 5505M 139M 16909 188 1 0 11025 0 81 565387 182791 30440 68 18 14 1 6 0 5468M 158M 19244 35 1 0 19469 0 42 563246 217685 7941 75 22 3 6 3 0 5276M 235M 23078 7 1 0 27426 0 135 555198 118844 73807 33 20 47 0 0 0 5177M 283M 9636 3 1 0 20972 0 108 564052 144113 6643 29 14 57 5 0 0 5176M 284M 8968 7 0 0 8607 0 22 567849 143837 6767 27 12 60 9 1 0 5199M 268M 14417 0 0 0 25905 0 31 567551 249480 6951 48 22 29 1 3 0 5341M 201M 8095 16 25 0 5087 0 112 565233 63826 6777 28 8 63 1 4 0 5356M 184M 30195 11 2 0 38720 0 95 560968 137901 52156 71 22 7 1 3 0 5266M 225M 13461 2 1 0 15518 0 46 564340 101664 9105 33 13 54 [root@gans /home/sg]# vmstat -i interrupt total rate irq1: atkbd0 4 0 irq16: ohci0 1 0 irq17: ohci1 ohci3 1 0 irq18: ohci2 ohci4 1 0 irq21: twe0 38629583391 101980 cpu0: timer 757587412 1999 cpu1: timer 757587403 1999 Total 40144758213 105980 I have recompiled kernel to 6.2-STABLE, 7.0-RELEASE, 7.0-RELEASE-p1, 7.0-STABLE but error persists. System work good for some time (few days) and than vmstat -i irq20; rate increases from 60-90 to 100000+ and than system hangs. After reboot system work good for some time. I have replaced sever, moved disks to another server with same hardware (and controller), and error persists. Kind Regards From aradford at gmail.com Thu Jun 12 22:48:41 2008 From: aradford at gmail.com (adam radford) Date: Thu Jun 12 22:48:44 2008 Subject: twe0 interrupt storm In-Reply-To: <319048390806120643n2033cfd1m795eaaf414c9f15c@mail.gmail.com> References: <319048390806120643n2033cfd1m795eaaf414c9f15c@mail.gmail.com> Message-ID: On Thu, Jun 12, 2008 at 6:43 AM, FreeBSD wrote: > Jun 11 21:38:00 gans kernel: twe0: <3ware Storage Controller. Driver > version 1.50.01.002> port 0xe800-0xe80f mem > 0xfebffc00-0xfebffc0f,0xfe000000-0xfe7fffff irq 20 at device 2.0 > on pci3 That's strange, the driver thinks it's hooked to irq 20, see above. > [root@gans /home/sg]# vmstat -i snip > irq21: twe0 38629583391 101980 snip > Total 40144758213 105980 > But here we are irq 21? -Adam From freebsd at n9.ru Fri Jun 13 00:47:52 2008 From: freebsd at n9.ru (FreeBSD) Date: Fri Jun 13 00:47:54 2008 Subject: twe0 interrupt storm In-Reply-To: References: <319048390806120643n2033cfd1m795eaaf414c9f15c@mail.gmail.com> Message-ID: <319048390806121747u6bcb58e4u19d00f1d07a51a20@mail.gmail.com> Hi, Thank you for fast reply. I'm sorry, on old server controller was installed on irq20, on new on irq21. The hardware is same on both servers, I use another slot, and error persist on both servers. So now: [root@gans /home/sg]# vmstat -i interrupt total rate irq1: atkbd0 3 0 irq16: ohci0 1 0 irq17: ohci1 ohci3 1 0 irq18: ohci2 ohci4 1 0 irq20: twe0 2392173 61 cpu0: timer 77623998 1999 cpu1: timer 77623962 1999 Total 157640139 4061 But after some time irq20 rate heavely increases to 100000+ and than system hangs... gstat shows disk usage avg. 20%. Don't know what to do, because I have used different kernels, and changed controller to new one. Kind Regards 2008/6/13 adam radford : > On Thu, Jun 12, 2008 at 6:43 AM, FreeBSD wrote: >> Jun 11 21:38:00 gans kernel: twe0: <3ware Storage Controller. Driver >> version 1.50.01.002> port 0xe800-0xe80f mem >> 0xfebffc00-0xfebffc0f,0xfe000000-0xfe7fffff irq 20 at device 2.0 >> on pci3 > > That's strange, the driver thinks it's hooked to irq 20, see above. > >> [root@gans /home/sg]# vmstat -i > snip >> irq21: twe0 38629583391 101980 > snip >> Total 40144758213 105980 >> > > But here we are irq 21? > > -Adam > > > From info_winner at speedlotto.com Sat Jun 14 01:12:20 2008 From: info_winner at speedlotto.com (Matilda Peterson) Date: Sat Jun 14 01:12:24 2008 Subject: SPEEDLOTTO AWARD WINNER Message-ID: <20080614032239.B97EEE7F3@nino.skgo.org> SPEEDLOTTO AWARD WINNER SL001QCMAJ2008 AUTHORIZATION NOTE SUBJECT: Guaranteed* Cash Notification £1,000,000.00 Pounds Unclaimed This is £1,000,000.00 GBP(One Million Great Britain Pounds)that was accredited to your e-mail address.You have been chosen as one of our Monthly Lucky winners. Do send the following informations to enable us process your claims Full Names: Contact/Mailing Address: Tel/ Fax Numbers: Nationality: Age / Sex DRAW DATE:Saturday, June 14,2008 Contact Agent; Matilda Peterson claims.dept108@gmail.com Tel:+44 701 114 9680 From freebsd at n9.ru Sat Jun 14 02:28:07 2008 From: freebsd at n9.ru (FreeBSD) Date: Sat Jun 14 02:28:11 2008 Subject: twe0 interrupt storm In-Reply-To: <319048390806120643n2033cfd1m795eaaf414c9f15c@mail.gmail.com> References: <319048390806120643n2033cfd1m795eaaf414c9f15c@mail.gmail.com> Message-ID: <319048390806131928r50719376s531413a57b31c1a6@mail.gmail.com> up From bseklecki at collaborativefusion.com Sat Jun 14 21:55:39 2008 From: bseklecki at collaborativefusion.com (Brian A. Seklecki) Date: Sat Jun 14 21:55:41 2008 Subject: Dell poweredge 1950 iii In-Reply-To: <20080612102329.GA63230@obelix.bergerie.agneau.org> References: <20080612102329.GA63230@obelix.bergerie.agneau.org> Message-ID: <1213479933.2823.154.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> On Thu, 2008-06-12 at 12:23 +0200, Laurent Frigault wrote: > Hi, > > Does anyone tried installing FreeBSD 7.0 on Dell poweredge 1950 iii? I'll have a 2950 r3 for you this week. I'll post a RELENG_7_0 dmesg(8) on the NYCBUG dmesgd(8) for you. ~BAS (PS the 2950 is a 1950 with more SAS bays) > Any dmesg.boot for this hardware ? > Is there any known issue with it ? > > Regards, -- Brian A. Seklecki Collaborative Fusion, Inc. From pisymbol at gmail.com Tue Jun 17 15:44:51 2008 From: pisymbol at gmail.com (Alexander Sack) Date: Tue Jun 17 15:44:54 2008 Subject: error messages dmesg/acpi on In-Reply-To: <483E9793.6080409@gmail.com> References: <483E9793.6080409@gmail.com> Message-ID: <3c0b01820806170818s6c53403bx9424855107fa554d@mail.gmail.com> On Thu, May 29, 2008 at 7:46 AM, sam wrote: > dmesg output > > ================================================== > # cat /var/run/dmesg.boot > Copyright (c) 1992-2008 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 7.0-STABLE #0: Wed May 21 18:24:33 MSD 2008 > root@stone:/usr/obj/usr/src/sys/STONE > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Pentium(R) III CPU family 1400MHz (1396.45-MHz 686-class > CPU) > Origin = "GenuineIntel" Id = 0x6b1 Stepping = 1 > Features=0x383fbff > real memory = 1610350592 (1535 MB) > avail memory = 1568567296 (1495 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 3 > cpu1 (AP): APIC ID: 0 > MADT: Forcing active-low polarity and level trigger for SCI > ioapic0 irqs 0-15 on motherboard > ioapic1 irqs 16-31 on motherboard > lapic3: Forcing LINT1 to edge trigger > kbd1 at kbdmux0 > acpi0: on motherboard > ACPI Warning (dswload-0794): Type override - [DEB_] had invalid type > (Integer) for Scope operator, changed to (Scope) [20070320] > ACPI Warning (dswload-0794): Type override - [MLIB] had invalid type > (Integer) for Scope operator, changed to (Scope) [20070320] > ACPI Warning (dswload-0794): Type override - [DATA] had invalid type > (String) for Scope operator, changed to (Scope) [20070320] > ACPI Warning (dswload-0794): Type override - [SIO_] had invalid type > (String) for Scope operator, changed to (Scope) [20070320] > ACPI Warning (dswload-0794): Type override - [SB__] had invalid type > (String) for Scope operator, changed to (Scope) [20070320] > ACPI Warning (dswload-0794): Type override - [PM__] had invalid type > (String) for Scope operator, changed to (Scope) [20070320] > ACPI Warning (dswload-0794): Type override - [ICNT] had invalid type > (String) for Scope operator, changed to (Scope) [20070320] > ACPI Warning (dswload-0794): Type override - [ACPI] had invalid type > (String) for Scope operator, changed to (Scope) [20070320] > ACPI Warning (dswload-0794): Type override - [LEDP] had invalid type > (String) for Scope operator, changed to (Scope) [20070320] > ACPI Warning (dswload-0794): Type override - [WUES] had invalid type > (String) for Scope operator, changed to (Scope) [20070320] > ACPI Warning (dswload-0794): Type override - [WUSE] had invalid type > (String) for Scope operator, changed to (Scope) [20070320] > ACPI Warning (dswload-0794): Type override - [CSB5] had invalid type > (String) for Scope operator, changed to (Scope) [20070320] > ACPI Warning (dswload-0794): Type override - [PM__] had invalid type > (String) for Scope operator, changed to (Scope) [20070320] > ACPI Warning (dswload-0794): Type override - [BIOS] had invalid type > (Integer) for Scope operator, changed to (Scope) [20070320] > ACPI Warning (dswload-0794): Type override - [CMOS] had invalid type > (Integer) for Scope operator, changed to (Scope) [20070320] > acpi0: [ITHREAD] > ACPI Error (evxfevnt-0288): Could not enable GlobalLock event [20070320] > ACPI Warning (evxface-0235): Could not enable fixed event 1 [20070320] > ACPI Error (evmisc-0487): No response from Global Lock hardware, disabling > lock [20070320] > acpi0: Power Button (fixed) > Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 > acpi_timer0: <32-bit timer at 3.579545MHz> port 0x508-0x50b on acpi0 > cpu0: on acpi0 > cpu1: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > atapci0: port > 0x1400-0x1407,0x1408-0x140b,0x1410-0x1417,0x140c-0x140f,0x1440-0x147f mem > 0xfe7a0000-0xfe7bffff irq 19 at device 2.0 on pci0 > atapci0: [ITHREAD] > ata2: on atapci0 > ata2: [ITHREAD] > ata3: on atapci0 > ata3: [ITHREAD] > fxp0: port 0x1480-0x14bf mem > 0xfe790000-0xfe790fff,0xfe760000-0xfe77ffff irq 21 at device 3.0 on pci0 > miibus0: on fxp0 > inphy0: PHY 1 on miibus0 > inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > fxp0: Ethernet address: 00:03:47:a5:6e:c9 > fxp0: [ITHREAD] > fxp1: port 0x14c0-0x14ff mem > 0xfe750000-0xfe750fff,0xfe720000-0xfe73ffff irq 20 at device 4.0 on pci0 > miibus1: on fxp1 > inphy1: PHY 1 on miibus1 > inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > fxp1: Ethernet address: 00:03:47:a5:6e:cb > fxp1: [ITHREAD] > vgapci0: port 0x1000-0x10ff mem > 0xfd000000-0xfdffffff,0xfe7f0000-0xfe7f0fff irq 18 at device 12.0 on pci0 > isab0: at device 15.0 on pci0 > isa0: on isab0 > atapci1: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x3a0-0x3af,0x410-0x413 at device 15.1 > on pci0 > ata0: on atapci1 > ata0: [ITHREAD] > ata1: on atapci1 > ata1: [ITHREAD] > pcib1: on acpi0 > pci1: on pcib1 > pcib2: on acpi0 > pci2: on pcib2 > atkbdc0: port 0x60,0x64 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > atkbd0: [ITHREAD] > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on > acpi0 > sio0: type 16550A > sio0: [FILTER] > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 > sio1: type 16550A > sio1: [FILTER] > pmtimer0 on isa0 > orm0: at iomem > 0xc0000-0xc7fff,0xc8000-0xd07ff,0xe4000-0xe7fff pnpid ORM0000 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 > ad4: 114473MB at ata2-master UDMA100 > ad6: 114473MB at ata3-master UDMA100 > ar0: 114440MB status: READY > ar0: disk0 READY (master) using ad4 at ata2-master > ar0: disk1 READY (mirror) using ad6 at ata3-master > lapic0: Forcing LINT1 to edge trigger > SMP: AP CPU #1 Launched! > Trying to mount root from ufs:/dev/ar0s1a > ================================================== > > part of kenv output > ================================================== > > smbios.bios.reldate="10/18/2001" > smbios.bios.vendor="Intel Corporation" > smbios.bios.version="SCB20.86B.0013.P02.0110181617 " > smbios.chassis.maker=" " > smbios.chassis.serial=" " > smbios.chassis.tag=" " > smbios.chassis.version=" " > smbios.planar.maker="Intel" > smbios.planar.product="SCB2A" > smbios.planar.serial="KKC115000476" > smbios.planar.version="A46043-607" > smbios.socket.enabled="2" > smbios.socket.populated="2" > smbios.system.maker="Intel" > smbios.system.product="SCB20" > ================================================== Those error messages I believe are coming from ACPI-CA (Intel's own code). Have you flashed the latest BIOS on the system? -aps From gmarkley at greatbaysoftware.com Wed Jun 18 17:24:36 2008 From: gmarkley at greatbaysoftware.com (Gabriel Markley) Date: Wed Jun 18 17:24:41 2008 Subject: Intel integrated RAID for the SR2500ALLXR freebsd support In-Reply-To: <20080530161249.GA46028@eos.sc1.parodius.com> Message-ID: <20080618172436.3CB738FC23@mx1.freebsd.org> This is what was found: dev.mfid.0.%desc: MFI Logical Disk dev.mfid.0.%driver: mfid dev.mfid.0.%parent: mfi0 hptmv.status: RocketRAID 182x SATA Controller driver Version v1.12 mfi driver Does anyone know the command to get a detailed status out of this driver? -- Gabriel Markley Systems Engineer Great Bay Software, Inc. v: 603.766.6146 | m: 603.498-3513 | f: 603.430.0713 | e: gmarkley@GreatBaySoftware.com -----Original Message----- From: Jeremy Chadwick [mailto:koitsu@FreeBSD.org] Sent: Friday, May 30, 2008 12:13 PM To: Gabriel Markley Cc: freebsd-hardware@freebsd.org Subject: Re: Intel integrated RAID for the SR2500ALLXR freebsd support On Fri, May 30, 2008 at 11:56:14AM -0400, Gabriel Markley wrote: > I am a systems engineer for Great Bay Software we are looking to move our > servers over to freebsd. > I am having trouble finding any documentation on using freebsd with Intel > integrated RAID for the SR2500ALLXR. > I need to find out if there is a driver available? > And can I pull status of the raid from it? i.e. H.D. failure and any other > possible problems... > Other then look in the bios and or look at the front plane to see if a > drive has failed. > > I am going to add the detailed specs that I was given below: > Active Mid-plane with SAS /SAS RAID Support > The active mid-plane is used to provide SAS / SAS RAID support. It has > integrated on to it an > Intel IOP80333 IO processor and an LSI* LSLSAS1068 3Gb/s SAS controller. This would probably fall under the mpt(4) or mfi(4) driver. I don't know if either of those drivers have support for that exact model of LSI controller, however. Best bet would be to get a FreeBSD livefs or bootonly CD and then see what is (or is not) detected. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | _______________________________________________ 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" __________ Information from ESET Smart Security, version of virus signature database 3148 (20080530) __________ The message was checked by ESET Smart Security. http://www.eset.com __________ Information from ESET Smart Security, version of virus signature database 3198 (20080618) __________ The message was checked by ESET Smart Security. http://www.eset.com From achilov-rn at askd.ru Thu Jun 19 04:01:35 2008 From: achilov-rn at askd.ru (Rashid N. Achilov) Date: Thu Jun 19 04:01:42 2008 Subject: Server periodically rebooted Message-ID: <200806191050.30665.achilov-rn@askd.ru> FreeBSD master.askd.ru 6.3-STABLE FreeBSD 6.3-STABLE #21: Mon Feb 18 13:05:59 NOVT 2008 root@master.askd.ru:/usr/obj/usr/src/sys/Master i386 Intel DQ965GF, Core Duo Jun 19 10:34:50 master kernel: sio4: on puc0 Jun 19 10:34:50 master kernel: sio4: type 16550A Periodically, server silently rebooted. That occassion will be only when exist active user, works on dial-up connection. NetMos installed, but not used, used motherboard COM port, used pppd with simply PAP auth. How to exclude these reboots? -- With Best Regards. Rashid N. Achilov (RNA1-RIPE), Web: http://www.askd.ru/~shelton OOO "ACK" telecommunications administrator, e-mail: achilov-rn [at] askd.ru PGP: 83 CD E2 A7 37 4A D5 81 D6 D6 52 BF C9 2F 85 AF 97 BE CB 0A From netslists at gmail.com Thu Jun 19 14:17:51 2008 From: netslists at gmail.com (Sten Daniel Soersdal) Date: Thu Jun 19 14:17:55 2008 Subject: FreeBSD and DELL PowerEdge Blade servers. Message-ID: <485A6486.1030305@gmail.com> I am considering a DELL PowerEdge Blade server for a project. The ones i have available (online webstore) are M600, M605, 1955 and M1000e. Does anyone have any experience, good or bad, about running FreeBSD on these or similar (older?) systems? Will FreeBSD (really) support either one of the FiberChannel cards? Qlogic QME2472 4Gbps FC4 HBA Card PCIe Emulex LPE1105-M4 FC4 HBA Card PCIe -- Sten Daniel Soersdal From andy.kosela at gmail.com Sun Jun 22 09:42:06 2008 From: andy.kosela at gmail.com (Andy Kosela) Date: Sun Jun 22 09:42:09 2008 Subject: Tape library HP MSL6030 Message-ID: <3cc535c80806220216t7c593583g88e66e44f5e58eed@mail.gmail.com> We are in the process of buying HP MSL6030 tape library. Our hardware provider is suggesting to use it with RHEL 5 and HP Data Protector software. However I would like to know what is the status of FreeBSD 7 support for this? Anyone using it in a production environment? and what software would you recommend? bacula, amanda, dump, rsync? -- Andy Kosela ora et labora From proks at logos.sky.od.ua Mon Jun 23 10:56:03 2008 From: proks at logos.sky.od.ua (Prokofiev S.P.) Date: Mon Jun 23 10:56:08 2008 Subject: ata driver and nvidia chipset problem ? Message-ID: <20080623130949.N41108@logos.sky.od.ua> I was installed FreeBSD 7-Stable i386 on motherboard Asus M2N-VM HDMI (chipset nvidia GeForce 7050PV/ nForce 630A(MCP68PVNT)) and 2 hdd : Seagate ST3250410AS SATA300. But I see by dmesg: ... ad4: 238475MB at ata2-master UDMA33 acd0: DVDR at ata2-slave UDMA33 ad6: 238475MB at ata3-master UDMA33 and by atacontrol: >atacontrol mode ad4 current mode = UDMA33 ata driver is not known this chipset ? Best regards, Sergey Prokofiev From mv at thebeastie.org Tue Jun 24 11:09:47 2008 From: mv at thebeastie.org (Michael Vince) Date: Tue Jun 24 11:09:50 2008 Subject: FreeBSD and Maxtor Basics USB drive Message-ID: <4860C78C.2070105@thebeastie.org> Hey everyone. I was looking at buying one of these 1 terabyte HDs for FreeBSD for backups etc, but I was wondering if there was actually a driver for it work on FreeBSD... Does any one know? http://www.maxtorsolutions.com/gb/catalog/Basics_Desktop/index.html Thanks Mike From alwin.roosen at webline.be Wed Jun 25 11:16:35 2008 From: alwin.roosen at webline.be (Alwin Roosen) Date: Wed Jun 25 11:17:01 2008 Subject: Would a Transcend USB Flash Module of 2GB work? Message-ID: <50A3BEAB67F03F44A2A063D55FC14D37119163@sbs2003.Webline.local> Hello, I have been searching quite a bit, but found nothing useful. I want to install FreeBSD onto an USB Flash Module from Transcend. The links below are the product page and datasheet in PDF. It says it should be compatible with OS that supports USB standard. Can anyone confirm that this would actually work? http://www.transcend.nl/Products/ModDetail.asp?LangNo=0 &ModNo=122 http://www.transcend.nl/support/dlcenter/datasheet/TS512M~4GUFM-V_H0409. pdf I am also wondering if it is a good approach to use USB dongles, instead of real Solid State devices on ATA. I see a lot of USB problems in the Mailing list Archives (see link below as example). I don't understand all of that, and I know there are many USB devices which can cause these issues. My hardware supplier recommends the USB dongles, because they are cheaper and easier to install (just plug it in an 10-pin USB port on the motherboard). http://lists.freebsd.org/mailman/htdig/freebsd-usb/2007-January/002939.h tml Thanks for your time! Alwin Roosen From koitsu at FreeBSD.org Wed Jun 25 12:05:13 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Wed Jun 25 12:05:16 2008 Subject: Would a Transcend USB Flash Module of 2GB work? In-Reply-To: <50A3BEAB67F03F44A2A063D55FC14D37119163@sbs2003.Webline.local> References: <50A3BEAB67F03F44A2A063D55FC14D37119163@sbs2003.Webline.local> Message-ID: <20080625120513.GA27643@eos.sc1.parodius.com> On Wed, Jun 25, 2008 at 12:56:28PM +0200, Alwin Roosen wrote: > I want to install FreeBSD onto an USB Flash Module from Transcend. The > links below are the product page and datasheet in PDF. It says it should > be compatible with OS that supports USB standard. > Can anyone confirm that this would actually work? > http://www.transcend.nl/Products/ModDetail.asp?LangNo=0&ModNo=122 This looks like nothing more than a USB flash drive (sometimes called USB pen drive), except instead of a standard Type-A USB connector, it uses a 10-pin connector like what's on PC motherboards. (I also like how their connector isn't even keyed, which means you could indeed plug the adapter in backwards; all present-day internal USB cables are keyed, so why aren't those?) The PDF contains absolutely no information about what type of flash is used, how flash I/O is performed, or if any form of wear levelling is implemented. There's also no MTBF, which is disappointing, although it does list erase cycle counts (100K). The closest thing to MTBF there is "Data Retention", which says "10 years". There's too much ambiguity there for me to believe it. > I am also wondering if it is a good approach to use USB dongles, instead > of real Solid State devices on ATA. > ... > My hardware supplier recommends the USB dongles, because they > are cheaper and easier to install (just plug it in an 10-pin USB port on > the motherboard). SSD is different than the product you list above. The most important aspect of present-day (past 2-3 years) SSD is how wear levelling is implemented. It's very well done on present-day SSD devices, while on USB storage devices like what you list, I strongly doubt it's done similarly. I would recommend you read the following documents: http://www.storagesearch.com/ssdmyths-endurance.html http://en.wikipedia.org/wiki/Wear_levelling With regards to the Wikipedia article, now you see why knowing what sort of wear levelling mechanism and "logic" is used in those USB devices. I would easily trust present-day SSD over a USB stick (which is really what those things are), period. Then there's the performance aspect. Those USB devices are going to top out at 33MByte/sec, and I'm willing to bet they don't even achieve that. Take a look at pages 6-8 of the following SSD review (compared against present-day hard disks): http://www.tomshardware.com/reviews/ssd-memoright,1926.html > I see a lot of USB problems in the Mailing list Archives (see link > below as example). I don't understand all of that, and I know there > are many USB devices which can cause these issues. Is there a question in here somewhere? :-) I think what you're indirectly trying to ask is "is USB on FreeBSD stable?" IMHO, the answer is a big fat no. I would not trust the present USB stack with the same reliability as, say, the SCSI CAM or (I'll regret saying this, I just know it) ATA subsystem. What goal are you trying to accomplish? Do you want to build a FreeBSD system using standard PC parts which doesn't involve storage media that has moving parts? -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From alwin.roosen at webline.be Wed Jun 25 13:47:35 2008 From: alwin.roosen at webline.be (Alwin Roosen) Date: Wed Jun 25 13:47:41 2008 Subject: Would a Transcend USB Flash Module of 2GB work? In-Reply-To: <073DF92AAE3443F79BA23004D60ED8AA@Webline.local> References: <50A3BEAB67F03F44A2A063D55FC14D37119163@sbs2003.Webline.local> <073DF92AAE3443F79BA23004D60ED8AA@Webline.local> Message-ID: <50A3BEAB67F03F44A2A063D55FC14D37119168@sbs2003.Webline.local> Hi Jeremy, Thank you for all the information! The purpose of this is to build a very simple DNS server which is controlled by some PHP command line scripting. It won't do much writing at all since it loads all DNS information from a separate database-server. Therefore I thought a very simple server without moving parts like unreliable disks would be the perfect match. I could make a copy of that dongle in case it ever breaks and be assured it would run for years and years. I have been reading the FreeBSD tutorial (http://www.freebsd.org/doc/en/articles/solid-state/index.html), which looks not too complicated to achieve. After reading your response, I will definitely buy a SSD instead of a USB dongle. Alwin Roosen -----Original Message----- From: Jeremy Chadwick [mailto:koitsu@FreeBSD.org] Sent: woensdag 25 juni 2008 14:15 To: Alwin Roosen Cc: freebsd-hardware@freebsd.org Subject: Re: Would a Transcend USB Flash Module of 2GB work? On Wed, Jun 25, 2008 at 12:56:28PM +0200, Alwin Roosen wrote: > I want to install FreeBSD onto an USB Flash Module from Transcend. The > links below are the product page and datasheet in PDF. It says it should > be compatible with OS that supports USB standard. > Can anyone confirm that this would actually work? > http://www.transcend.nl/Products/ModDetail.asp?LangNo=0&ModNo=122 This looks like nothing more than a USB flash drive (sometimes called USB pen drive), except instead of a standard Type-A USB connector, it uses a 10-pin connector like what's on PC motherboards. (I also like how their connector isn't even keyed, which means you could indeed plug the adapter in backwards; all present-day internal USB cables are keyed, so why aren't those?) The PDF contains absolutely no information about what type of flash is used, how flash I/O is performed, or if any form of wear levelling is implemented. There's also no MTBF, which is disappointing, although it does list erase cycle counts (100K). The closest thing to MTBF there is "Data Retention", which says "10 years". There's too much ambiguity there for me to believe it. > I am also wondering if it is a good approach to use USB dongles, instead > of real Solid State devices on ATA. > ... > My hardware supplier recommends the USB dongles, because they > are cheaper and easier to install (just plug it in an 10-pin USB port on > the motherboard). SSD is different than the product you list above. The most important aspect of present-day (past 2-3 years) SSD is how wear levelling is implemented. It's very well done on present-day SSD devices, while on USB storage devices like what you list, I strongly doubt it's done similarly. I would recommend you read the following documents: http://www.storagesearch.com/ssdmyths-endurance.html http://en.wikipedia.org/wiki/Wear_levelling With regards to the Wikipedia article, now you see why knowing what sort of wear levelling mechanism and "logic" is used in those USB devices. I would easily trust present-day SSD over a USB stick (which is really what those things are), period. Then there's the performance aspect. Those USB devices are going to top out at 33MByte/sec, and I'm willing to bet they don't even achieve that. Take a look at pages 6-8 of the following SSD review (compared against present-day hard disks): http://www.tomshardware.com/reviews/ssd-memoright,1926.html > I see a lot of USB problems in the Mailing list Archives (see link > below as example). I don't understand all of that, and I know there > are many USB devices which can cause these issues. Is there a question in here somewhere? :-) I think what you're indirectly trying to ask is "is USB on FreeBSD stable?" IMHO, the answer is a big fat no. I would not trust the present USB stack with the same reliability as, say, the SCSI CAM or (I'll regret saying this, I just know it) ATA subsystem. What goal are you trying to accomplish? Do you want to build a FreeBSD system using standard PC parts which doesn't involve storage media that has moving parts? -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From whizzter at gmail.com Wed Jun 25 13:53:10 2008 From: whizzter at gmail.com (Jonas Lund) Date: Wed Jun 25 13:53:16 2008 Subject: Would a Transcend USB Flash Module of 2GB work? In-Reply-To: <50A3BEAB67F03F44A2A063D55FC14D37119163@sbs2003.Webline.local> References: <50A3BEAB67F03F44A2A063D55FC14D37119163@sbs2003.Webline.local> Message-ID: <436c7eda0806250625u3408bcd2k61b69ed14c4c1b10@mail.gmail.com> > I want to install FreeBSD onto an USB Flash Module from Transcend. The > links below are the product page and datasheet in PDF. It says it should > be compatible with OS that supports USB standard. Like jeremy said the USB stack ain't overly sexy. Altho as far as i've used it umass hasn't caused too much problems. If you are building kiosks or similiar systems that are mostly used to launch programs and not write too much to the disk then installing on a 'el cheapo usb thingy might be just the thing. I did something similar a little while back (linux tho) and it's quite simple/cheap for something like that. 2 things. - mount with noatime (wearing the memory just because accessing files is quite stupid) - make sure your system has enough memory to avoid swapping, while you can certainly put a swap on flash i wouldn't recommend relying on it as the errors that finally crops up could be subtle and catastrophic or just errors. (how does freebsd handle a swap disk going bad?) / Jonas From alwin.roosen at webline.be Wed Jun 25 13:59:40 2008 From: alwin.roosen at webline.be (Alwin Roosen) Date: Wed Jun 25 13:59:45 2008 Subject: Would a Transcend USB Flash Module of 2GB work? In-Reply-To: <9793E60822024E76A88D70BCC9C1BE77@Webline.local> References: <50A3BEAB67F03F44A2A063D55FC14D37119163@sbs2003.Webline.local> <9793E60822024E76A88D70BCC9C1BE77@Webline.local> Message-ID: <50A3BEAB67F03F44A2A063D55FC14D37119169@sbs2003.Webline.local> Hi Jonas, Thank you for the tips! Could you explain to me how the swap partition would work? In the manual () they say to remove the swap from fstab. I don't know much of partitioning since this is setup-related and almost always the same on our servers. Normally you would create a swap partition twice the size of the memory capacity. But if you have a server with 1GB memory, and a 2GB flash-disk, how would this work? Alwin Roosen -----Original Message----- From: Jonas Lund [mailto:whizzter@gmail.com] Sent: woensdag 25 juni 2008 15:31 To: Alwin Roosen Cc: freebsd-hardware@freebsd.org Subject: Re: Would a Transcend USB Flash Module of 2GB work? > I want to install FreeBSD onto an USB Flash Module from Transcend. The > links below are the product page and datasheet in PDF. It says it should > be compatible with OS that supports USB standard. Like jeremy said the USB stack ain't overly sexy. Altho as far as i've used it umass hasn't caused too much problems. If you are building kiosks or similiar systems that are mostly used to launch programs and not write too much to the disk then installing on a 'el cheapo usb thingy might be just the thing. I did something similar a little while back (linux tho) and it's quite simple/cheap for something like that. 2 things. - mount with noatime (wearing the memory just because accessing files is quite stupid) - make sure your system has enough memory to avoid swapping, while you can certainly put a swap on flash i wouldn't recommend relying on it as the errors that finally crops up could be subtle and catastrophic or just errors. (how does freebsd handle a swap disk going bad?) / Jonas From telmnstr at 757.org Wed Jun 25 14:13:20 2008 From: telmnstr at 757.org (telmnstr@757.org) Date: Wed Jun 25 14:13:22 2008 Subject: Would a Transcend USB Flash Module of 2GB work? In-Reply-To: <50A3BEAB67F03F44A2A063D55FC14D37119169@sbs2003.Webline.local> References: <50A3BEAB67F03F44A2A063D55FC14D37119163@sbs2003.Webline.local> <9793E60822024E76A88D70BCC9C1BE77@Webline.local> <50A3BEAB67F03F44A2A063D55FC14D37119169@sbs2003.Webline.local> Message-ID: > our servers. Normally you would create a swap partition twice the size > of the memory capacity. But if you have a server with 1GB memory, and a > 2GB flash-disk, how would this work? That is best practices. You should be able to remove the swap partition altogether, and as long as you don't exceed the system RAM with programs you are fine. From soralx at cydem.org Wed Jun 25 15:16:02 2008 From: soralx at cydem.org (soralx@cydem.org) Date: Wed Jun 25 15:16:06 2008 Subject: Would a Transcend USB Flash Module of 2GB work? In-Reply-To: <50A3BEAB67F03F44A2A063D55FC14D37119168@sbs2003.Webline.local> References: <50A3BEAB67F03F44A2A063D55FC14D37119163@sbs2003.Webline.local> <073DF92AAE3443F79BA23004D60ED8AA@Webline.local> <50A3BEAB67F03F44A2A063D55FC14D37119168@sbs2003.Webline.local> Message-ID: <20080625071346.03709a9c@soralx> > The purpose of this is to build a very simple DNS server which is > controlled by some PHP command line scripting. It won't do much writing > at all since it loads all DNS information from a separate > database-server. Therefore I thought a very simple server without moving > parts like unreliable disks would be the perfect match. I could make a > copy of that dongle in case it ever breaks and be assured it would run > for years and years. Forgot to mention in my last email: if you need reliability, then don't use USB flash. I'm testing ZFS on the USB drives array, and a few days after I set it up, I've already seen a CRC error from ZFS -- that's data corruption (irrecoverable, needless to say). Even for a DNS server, USB flash is no good (unless all you use it for is bootstrap -- no writing or reading afterwards). [SorAlx] ridin' VS1400 From soralx at cydem.org Wed Jun 25 15:24:08 2008 From: soralx at cydem.org (soralx@cydem.org) Date: Wed Jun 25 15:24:17 2008 Subject: Would a Transcend USB Flash Module of 2GB work? In-Reply-To: <50A3BEAB67F03F44A2A063D55FC14D37119163@sbs2003.Webline.local> References: <50A3BEAB67F03F44A2A063D55FC14D37119163@sbs2003.Webline.local> Message-ID: <20080625082301.36dcc2d0@soralx> > [...] > I am also wondering if it is a good approach to use USB dongles, > instead of real Solid State devices on ATA. I see a lot of USB problems > in the Mailing list Archives (see link below as example). I don't > understand all of that, and I know there are many USB devices which can > cause these issues. My hardware supplier recommends the USB dongles, > because they are cheaper and easier to install (just plug it in an 10-pin > USB port on the motherboard). > [...] I'm a bit short on time at the moment, I shall be brief. I could expand on this later, be sure to remind me. USB flash drives don't work for anything other that temporary portable storage. They are _completely_ useless for keeping base system on, even if you have lots of RAM and don't need speed. I tried 4 USB drives (30MB/s read, 20MB/s writes datasheet) connected to two EHCI mainboard headers, striped in ZFS. Totally useless. The avg real life write speeds are ~5MB/s, reads ~12-20 MB/s, (four 'dd' reads give total 80MB/s), and the whole array is only good for about one(!) IOPS. The whole system freezes for seconds or tens of seconds at times. I'm not sure if it's hadrware limitation, or just kernel's USB stack implementation (which, IMHO, is quite flaky and ugly anyway) that's at fault. UFS without softupdates give write performance (while copying /boot/kernel) of a few kilobytes/s (well, maybe few hundred, if it feels like it). Short answer: don't waste your money. Small 46 mm hard drives are better (but not completely noiseless). [SorAlx] ridin' VN1500-B2 From gmarkley at greatbaysoftware.com Wed Jun 25 19:34:28 2008 From: gmarkley at greatbaysoftware.com (Gabriel Markley) Date: Wed Jun 25 19:34:32 2008 Subject: Admin Help Message-ID: <20080625193428.67D828FC14@mx1.freebsd.org> Can an Admin contact me? Please I have a question to ask. -- Gabriel Markley From jpalmer at totaldiver.net Wed Jun 25 20:19:03 2008 From: jpalmer at totaldiver.net (Jeff Palmer) Date: Wed Jun 25 20:19:08 2008 Subject: Admin Help In-Reply-To: <20080625193428.67D828FC14@mx1.freebsd.org> References: <20080625193428.67D828FC14@mx1.freebsd.org> Message-ID: <4862A15A.9050807@totaldiver.net> Gabriel, Your best bet is to ask your question. The reasons are: #1) The list gets archived. If you have a question, someone else may have the same question along the way. The replies you get will be archived and become searchable by most of the online search engines. Answering you often helps untold numbers of other people. #2) Nobody is going to be the "focal point" of your questions, without having an indication as to what those questions are. example: I send you an email, you ask me something about XYZ.. I know nothing about XYZ. so we've both just wasted our time, you're no further along in your quest for knowledge, and now you are depending on me for an answer I don't have. The above is just a polite way to say: Just ask your question. if someone has an answer, they'll offer it up. Jeff Gabriel Markley wrote: > Can an Admin contact me? Please I have a question to ask. > > > > From sfourman at gmail.com Wed Jun 25 20:55:54 2008 From: sfourman at gmail.com (Sam Fourman Jr.) Date: Wed Jun 25 20:55:59 2008 Subject: Admin Help In-Reply-To: <20080625193428.67D828FC14@mx1.freebsd.org> References: <20080625193428.67D828FC14@mx1.freebsd.org> Message-ID: <11167f520806251330w474dc9adw961d560ab99b215d@mail.gmail.com> On Wed, Jun 25, 2008 at 2:36 PM, Gabriel Markley < gmarkley@greatbaysoftware.com> wrote: > Can an Admin contact me? Please I have a question to ask. > I have a Few years of experince with FreeBSD based systems I may beable to help you out. what is your question Sam Fourman Jr. From vincentfrancois.pro at gmail.com Thu Jun 26 23:29:15 2008 From: vincentfrancois.pro at gmail.com (=?ISO-8859-1?Q?Vincent_Fran=E7ois?=) Date: Thu Jun 26 23:29:41 2008 Subject: FreeBSD 7.0 Release, Radeon RV350 9600 M10 Rev 0, System Freeze Message-ID: <14b028c20806261601n7c3ceb56n54e4116ef151dd4c@mail.gmail.com> FreeBSD 7.0 Release Graphic card : ATI RV350 Radeon 9600 M10 Rev 0 Xorg 1.4.0 Hello, I had a problem with the driver for the ATI Mobility 9600. At the start of the X Server, the system froze ! To solve this problem, I performed the operations listed below: 1) update the ports # portsnap fetch update 2) remove the xf86-video-ati package 2.1) detect version # pkg_version -v | grep xf86-video-ati xf86-video-ati-x.x.x x.x.x : version of package 2.2) delete package # pkg_delete xf86-video-ati.x.x.x 3) make and install new driver # cd /usr/ports/x11-driver/xf86-video-ati #make ... #make install 4) create new xorg config file (choose radeon driver) # xorgconfig 5) modify xorg config file ( /etc/X11/xorg.conf ) 5.1) modify device section Section "Device" Identifier "** ATI Radeon (Generic) [radeon]" Driver "radeon" VideoRam 131072 Option "DRI" "no" # Add this line BusID "PCI:1:0:0" # Add this line, for find the bus address use "pciconf -lv" EndSection 6) start server # startx Normaly, the X server now works ---- I tested with drm, it's ok. If you want to use the drm, here's how: 1) modify /etc/X11/xorg.conf, in section "Module" add: Load "drm" Load "radeon" # I'm not sure... 2) load radeon module # kldload radeon 3) start X server # startx From fbsd at dannysplace.net Fri Jun 27 02:52:05 2008 From: fbsd at dannysplace.net (Danny Carroll) Date: Fri Jun 27 02:52:10 2008 Subject: new server motherboard with SATA II Message-ID: <486450DB.4000907@dannysplace.net> Hello all, I'm looking to set up a file server at our office. It's a small office so price is a concern. Performance is also going to be important. The data will be replicated from another site so integrity of the data is not paramount. For this reason I think I'll be able to run with ZFS. I see it as a good opportunity to contribute to getting ZFS stable and non-experimental. What I am really concerned about is the SATA support. If I look at AMD64 as an arch, does anyone have any experience with good IO chipsets that can do full SATA-300? I don't mind if it is a on-board or if I get a good controller card so long as I can get decent performance out of the Seagate Barracuda 7200.11 drives. I'd be willing to go with intel arch although from a ZFS perspective it sounds like AMD64 is better. -D From dean at fragfest.com.au Fri Jun 27 02:55:05 2008 From: dean at fragfest.com.au (Dean Hamstead) Date: Fri Jun 27 02:55:08 2008 Subject: new server motherboard with SATA II In-Reply-To: <486450DB.4000907@dannysplace.net> References: <486450DB.4000907@dannysplace.net> Message-ID: <4864586B.1020702@fragfest.com.au> I have had good success with nforce boards with release-7.0 sataII seems to work well. Dean Danny Carroll wrote: > Hello all, > > I'm looking to set up a file server at our office. It's a small office > so price is a concern. Performance is also going to be important. > > The data will be replicated from another site so integrity of the data > is not paramount. For this reason I think I'll be able to run with ZFS. > I see it as a good opportunity to contribute to getting ZFS stable and > non-experimental. > > What I am really concerned about is the SATA support. > > If I look at AMD64 as an arch, does anyone have any experience with good > IO chipsets that can do full SATA-300? > > I don't mind if it is a on-board or if I get a good controller card so > long as I can get decent performance out of the Seagate Barracuda > 7200.11 drives. > > I'd be willing to go with intel arch although from a ZFS perspective it > sounds like AMD64 is better. > > -D > _______________________________________________ > 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" > -- http://fragfest.com.au From fbsd at dannysplace.net Fri Jun 27 02:57:02 2008 From: fbsd at dannysplace.net (Danny Carroll) Date: Fri Jun 27 02:57:06 2008 Subject: new server motherboard with SATA II In-Reply-To: <4864586B.1020702@fragfest.com.au> References: <486450DB.4000907@dannysplace.net> <4864586B.1020702@fragfest.com.au> Message-ID: <486456F1.6010005@dannysplace.net> Dean Hamstead wrote: > I have had good success with nforce boards with release-7.0 > > sataII seems to work well. Could you be more specific? Last time I looked there were a few generations of nForce chipsets. Was it on Intel or amd64? -D From koitsu at FreeBSD.org Fri Jun 27 04:05:45 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Fri Jun 27 04:05:49 2008 Subject: new server motherboard with SATA II In-Reply-To: <486450DB.4000907@dannysplace.net> References: <486450DB.4000907@dannysplace.net> Message-ID: <20080627040545.GA21856@eos.sc1.parodius.com> On Fri, Jun 27, 2008 at 12:30:51PM +1000, Danny Carroll wrote: > Hello all, > > I'm looking to set up a file server at our office. It's a small office > so price is a concern. Performance is also going to be important. > > The data will be replicated from another site so integrity of the data > is not paramount. For this reason I think I'll be able to run with ZFS. > I see it as a good opportunity to contribute to getting ZFS stable and > non-experimental. > > What I am really concerned about is the SATA support. > > If I look at AMD64 as an arch, does anyone have any experience with good > IO chipsets that can do full SATA-300? > > I don't mind if it is a on-board or if I get a good controller card so > long as I can get decent performance out of the Seagate Barracuda > 7200.11 drives. SATA150 and SATA300 both work just fine on FreeBSD, but its dependent upon what chipset you go with. I would strongly recommend you go with a board/system that uses Intel's ICH7, 8, or 9 southbridge. I have extensive experience using these in production environments, and they are very reliable, plus fast. FreeBSD works quite well with them. Second, I wouldn't bother considering using Intel MatrixRAID (which all of the above chipsets support) for any sort of failover for your root/OS disk, in case you're tempted to try it. FreeBSD has bugs pertaining to such support (see below Wiki URL for some examples). Third, I cannot recommend nVidia chipsets, because there have been numerous reports recently and in the past where the SATA disks are being detected as UDMA33. I believe there are some ATI/AMD chipsets which are doing the same. There is a rumour that the operational speed of the disks is still SATA150/300, and just that FreeBSD is labelling the negotiated speed wrong, but my recommendation is not to risk it. Fourth, because you'll likely have multiple disks in a ZFS zpool, you should probably be aware of the problem that haunts some users from time to time (re: DMA errors). http://wiki.freebsd.org/JeremyChadwick/ATA_issues_and_troubleshooting > I'd be willing to go with intel arch although from a ZFS perspective it > sounds like AMD64 is better. There was a recent discussion on developers@ (which is private) about some topics, which eventually lead into a discussion about ZFS, tuning, and a 2GB kmem limit in FreeBSD (which affects amd64 too). I can't copy the conversation/thread because developers@ has a strict "do not disclose" policy. We can discuss those topics separately here without issue -- I just mean I can't copy/paste what's already been said on another list. Just be aware you ***will*** need to tune ZFS on FreeBSD to make it as reliable as possible. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From frase at frase.id.au Fri Jun 27 04:27:36 2008 From: frase at frase.id.au (Fraser Tweedale) Date: Fri Jun 27 04:27:40 2008 Subject: new server motherboard with SATA II In-Reply-To: <486450DB.4000907@dannysplace.net> References: <486450DB.4000907@dannysplace.net> Message-ID: <20080627035137.GA9582@bacardi> On Fri, Jun 27, 2008 at 12:30:51PM +1000, Danny Carroll wrote: > Hello all, > > I'm looking to set up a file server at our office. It's a small office > so price is a concern. Performance is also going to be important. > > The data will be replicated from another site so integrity of the data > is not paramount. For this reason I think I'll be able to run with ZFS. > I see it as a good opportunity to contribute to getting ZFS stable and > non-experimental. > > What I am really concerned about is the SATA support. > > If I look at AMD64 as an arch, does anyone have any experience with good > IO chipsets that can do full SATA-300? > > I don't mind if it is a on-board or if I get a good controller card so > long as I can get decent performance out of the Seagate Barracuda > 7200.11 drives. > > I'd be willing to go with intel arch although from a ZFS perspective it > sounds like AMD64 is better. > > -D Intel ICH-9 works a treat; I run a combination of SATA-300 and SATA-150 drives on an ICH-9 southbridge, and have never had an issue. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-hardware/attachments/20080627/b52a486f/attachment.pgp From fbsd at dannysplace.net Fri Jun 27 05:12:05 2008 From: fbsd at dannysplace.net (Danny Carroll) Date: Fri Jun 27 05:12:10 2008 Subject: new server motherboard with SATA II In-Reply-To: <20080627040545.GA21856@eos.sc1.parodius.com> References: <486450DB.4000907@dannysplace.net> <20080627040545.GA21856@eos.sc1.parodius.com> Message-ID: <4864769C.4050002@dannysplace.net> Jeremy, thanks for your response. Jeremy Chadwick wrote: > SATA150 and SATA300 both work just fine on FreeBSD, but its dependent > upon what chipset you go with. I would strongly recommend you go with a > board/system that uses Intel's ICH7, 8, or 9 southbridge. I have > extensive experience using these in production environments, and they > are very reliable, plus fast. FreeBSD works quite well with them. I do have a board with an ICH10 chipset but the SATA drives are detected as UDMA-33. I guess the ICH* chipsets would not support AMD64, being an intel chip. > Second, I wouldn't bother considering using Intel MatrixRAID (which all > of the above chipsets support) for any sort of failover for your root/OS > disk, in case you're tempted to try it. FreeBSD has bugs pertaining to > such support (see below Wiki URL for some examples). Yeah, I'm not so keen of the modern trend to have on-board raid. I'd rather keep it simple and let FreeBSD handle it. Root disk will not be raid at all. > Third, I cannot recommend nVidia chipsets, because there have been > numerous reports recently and in the past where the SATA disks are being > detected as UDMA33. I believe there are some ATI/AMD chipsets which are > doing the same. There is a rumour that the operational speed of the > disks is still SATA150/300, and just that FreeBSD is labelling the > negotiated speed wrong, but my recommendation is not to risk it. Hmmm, some people say nforce4 chipsets are cool, some not... It's hard to know which way to go. > Fourth, because you'll likely have multiple disks in a ZFS zpool, you > should probably be aware of the problem that haunts some users from time > to time (re: DMA errors). I've seen it on old ATA hardware. > http://wiki.freebsd.org/JeremyChadwick/ATA_issues_and_troubleshooting > >> I'd be willing to go with intel arch although from a ZFS perspective it >> sounds like AMD64 is better. > > There was a recent discussion on developers@ (which is private) about > some topics, which eventually lead into a discussion about ZFS, tuning, > and a 2GB kmem limit in FreeBSD (which affects amd64 too). I can't copy > the conversation/thread because developers@ has a strict "do not > disclose" policy. I thought that the 2gb limit was less of a problem for AMD64 because of the addressing used. > Just be aware you ***will*** need to tune ZFS on FreeBSD to make it > as reliable as possible. We'll like I said, I'd be willing to jump on a list and provide info etc about my setup. I plan to have it running on a test bench with lots of IO for a week or so before I start using it. Even then the data will not be critical so if it breaks then I can rebuild without hassle. System disk will be UFS2 to keep it simple... I've got it running on desktop hardware (ASUS P5Q board with ICH5) while I wait for a decision on a permanent Motherboard. With this setup I see about 60mb write speeds on ZFS across 5 disks. I've done the basic tuning suggested in the Wiki. One thing I notice is that the CPU is used for 30% on Interrupts. It was firewire first, so I disabled it in the BIOS, then it went to UHCI so I disabled all USB ports. Now it is on the ATA controller. All of this was on the same interrupt (19). I'm thinking of getting a couple of Promise SATA-300 TX4 IO cards (non-raid). Perhaps that will offload the CPU. -D From frase at frase.id.au Fri Jun 27 05:31:18 2008 From: frase at frase.id.au (Fraser Tweedale) Date: Fri Jun 27 05:31:21 2008 Subject: new server motherboard with SATA II In-Reply-To: <4864769C.4050002@dannysplace.net> References: <486450DB.4000907@dannysplace.net> <20080627040545.GA21856@eos.sc1.parodius.com> <4864769C.4050002@dannysplace.net> Message-ID: <20080627053103.GB9582@bacardi> On Fri, Jun 27, 2008 at 03:11:56PM +1000, Danny Carroll wrote: > Jeremy, thanks for your response. > > Jeremy Chadwick wrote: > > SATA150 and SATA300 both work just fine on FreeBSD, but its dependent > > upon what chipset you go with. I would strongly recommend you go with a > > board/system that uses Intel's ICH7, 8, or 9 southbridge. I have > > extensive experience using these in production environments, and they > > are very reliable, plus fast. FreeBSD works quite well with them. > > I do have a board with an ICH10 chipset but the SATA drives are detected > as UDMA-33. > > I guess the ICH* chipsets would not support AMD64, being an intel chip. > Intel chips support AMD64 - the architecture is called that because AMD came up with it first. Intel calls their implementation EM64T (and x86-64 refers to the same thing), but it is all AMD64. As for the issue with those drives being detected as UDMA-33, I'm not sure, and defer my response. > > Second, I wouldn't bother considering using Intel MatrixRAID (which all > > of the above chipsets support) for any sort of failover for your root/OS > > disk, in case you're tempted to try it. FreeBSD has bugs pertaining to > > such support (see below Wiki URL for some examples). > > Yeah, I'm not so keen of the modern trend to have on-board raid. I'd > rather keep it simple and let FreeBSD handle it. Root disk will not be > raid at all. > > > Third, I cannot recommend nVidia chipsets, because there have been > > numerous reports recently and in the past where the SATA disks are being > > detected as UDMA33. I believe there are some ATI/AMD chipsets which are > > doing the same. There is a rumour that the operational speed of the > > disks is still SATA150/300, and just that FreeBSD is labelling the > > negotiated speed wrong, but my recommendation is not to risk it. > > Hmmm, some people say nforce4 chipsets are cool, some not... It's hard > to know which way to go. > For the record, I concur with Jeremy's sentiments. I also had issues with SATA on nForce 520, which prompted a shift to Intel for my main system. > > Fourth, because you'll likely have multiple disks in a ZFS zpool, you > > should probably be aware of the problem that haunts some users from time > > to time (re: DMA errors). > > I've seen it on old ATA hardware. > > > http://wiki.freebsd.org/JeremyChadwick/ATA_issues_and_troubleshooting > > > >> I'd be willing to go with intel arch although from a ZFS perspective it > >> sounds like AMD64 is better. > > > > There was a recent discussion on developers@ (which is private) about > > some topics, which eventually lead into a discussion about ZFS, tuning, > > and a 2GB kmem limit in FreeBSD (which affects amd64 too). I can't copy > > the conversation/thread because developers@ has a strict "do not > > disclose" policy. > > I thought that the 2gb limit was less of a problem for AMD64 because of > the addressing used. > > > Just be aware you ***will*** need to tune ZFS on FreeBSD to make it > > as reliable as possible. > > We'll like I said, I'd be willing to jump on a list and provide info etc > about my setup. I plan to have it running on a test bench with lots of > IO for a week or so before I start using it. Even then the data will > not be critical so if it breaks then I can rebuild without hassle. > System disk will be UFS2 to keep it simple... > > I've got it running on desktop hardware (ASUS P5Q board with ICH5) while > I wait for a decision on a permanent Motherboard. With this setup I see > about 60mb write speeds on ZFS across 5 disks. I've done the basic > tuning suggested in the Wiki. One thing I notice is that the CPU is > used for 30% on Interrupts. It was firewire first, so I disabled it in > the BIOS, then it went to UHCI so I disabled all USB ports. Now it is > on the ATA controller. All of this was on the same interrupt (19). > > I'm thinking of getting a couple of Promise SATA-300 TX4 IO cards > (non-raid). Perhaps that will offload the CPU. > > -D frase -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-hardware/attachments/20080627/308544e7/attachment.pgp From koitsu at FreeBSD.org Fri Jun 27 05:33:14 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Fri Jun 27 05:33:18 2008 Subject: new server motherboard with SATA II In-Reply-To: <4864769C.4050002@dannysplace.net> References: <486450DB.4000907@dannysplace.net> <20080627040545.GA21856@eos.sc1.parodius.com> <4864769C.4050002@dannysplace.net> Message-ID: <20080627053314.GA24239@eos.sc1.parodius.com> On Fri, Jun 27, 2008 at 03:11:56PM +1000, Danny Carroll wrote: > Jeremy, thanks for your response. > > Jeremy Chadwick wrote: >> SATA150 and SATA300 both work just fine on FreeBSD, but its dependent >> upon what chipset you go with. I would strongly recommend you go with a >> board/system that uses Intel's ICH7, 8, or 9 southbridge. I have >> extensive experience using these in production environments, and they >> are very reliable, plus fast. FreeBSD works quite well with them. > > I do have a board with an ICH10 chipset but the SATA drives are detected > as UDMA-33. This comes as no surprise, as there is no ICH10 knowledge in the PCI and ATA code at this time. ICH10 is ***very*** new, as in probably within the past 6 weeks, no? > I guess the ICH* chipsets would not support AMD64, being an intel chip. You're greatly confused with regards to what "amd64" means. FreeBSD's 32-bit operating system is called i386. FreeBSD's 64-bit operating system is called amd64. It has absolutely **nothing** to do with processor types (AMD vs. Intel). >> Second, I wouldn't bother considering using Intel MatrixRAID (which all >> of the above chipsets support) for any sort of failover for your root/OS >> disk, in case you're tempted to try it. FreeBSD has bugs pertaining to >> such support (see below Wiki URL for some examples). > > Yeah, I'm not so keen of the modern trend to have on-board raid. I'd > rather keep it simple and let FreeBSD handle it. Root disk will not be > raid at all. FreeBSD's ability to boot off of FreeBSD-managed-RAID'd volumes is horrible. Administrators have to go through a bunch of rigmarole to accomplish something that should be an absolute simplicity/necessity in this day and age. This is one reason why I myself have considered using Intel MatrixRAID, because then that "layer" is generally transparent to FreeBSD. In fact, ZFS on a root filesystem is still a "pain", yet Solaris has it down pat. >> Third, I cannot recommend nVidia chipsets, because there have been >> numerous reports recently and in the past where the SATA disks are being >> detected as UDMA33. I believe there are some ATI/AMD chipsets which are >> doing the same. There is a rumour that the operational speed of the >> disks is still SATA150/300, and just that FreeBSD is labelling the >> negotiated speed wrong, but my recommendation is not to risk it. > > Hmmm, some people say nforce4 chipsets are cool, some not... It's hard > to know which way to go. They're incredibly old, and you probably won't find them any more. >> Fourth, because you'll likely have multiple disks in a ZFS zpool, you >> should probably be aware of the problem that haunts some users from time >> to time (re: DMA errors). > > I've seen it on old ATA hardware. There's a chance you'll see it on brand new SATA300 disks with all sorts of different SATA controller hardware (not limited to just one vendor), too. The problem is somewhere within FreeBSD, and my Wiki page documents a workaround/patch that the FreeNAS guys came up with, which has sat ignored for over a year by the FreeBSD ATA maintainer. Not a good sign. >> http://wiki.freebsd.org/JeremyChadwick/ATA_issues_and_troubleshooting >> >>> I'd be willing to go with intel arch although from a ZFS perspective >>> it sounds like AMD64 is better. >> >> There was a recent discussion on developers@ (which is private) about >> some topics, which eventually lead into a discussion about ZFS, tuning, >> and a 2GB kmem limit in FreeBSD (which affects amd64 too). I can't copy >> the conversation/thread because developers@ has a strict "do not >> disclose" policy. > > I thought that the 2gb limit was less of a problem for AMD64 because of > the addressing used. You're confusing two issues (general maximum memory limit of x86/PC hardware and kmem). There is a known limit **in FreeBSD** that affects i386 and amd64 both, limiting the available amount of kmem to 2GB. You cannot increase it past that. It's a code issue, and is presently being addressed in HEAD (-CURRENT). ZFS uses kmem heavily. So, it doesn't matter if you have 16GB of RAM installed and are running amd64; kmem is still limited to 2GB. That means that effectively ZFS will only be able to use up to 1.5GB of your RAM (not 2GB, because you need to leave some available for other kernel related things; 512MB is enough). >> Just be aware you ***will*** need to tune ZFS on FreeBSD to make it >> as reliable as possible. > > We'll like I said, I'd be willing to jump on a list and provide info etc > about my setup. I plan to have it running on a test bench with lots of > IO for a week or so before I start using it. Even then the data will > not be critical so if it breaks then I can rebuild without hassle. Keep in mind that there have been some reports of ZFS on FreeBSD behaving incorrectly/oddly when a disk goes back, or a checksum error is found by ZFS. The disk will resilver for no apparent reason. > System disk will be UFS2 to keep it simple... > > I've got it running on desktop hardware (ASUS P5Q board with ICH5) while > I wait for a decision on a permanent Motherboard. With this setup I see > about 60mb write speeds on ZFS across 5 disks. I've done the basic > tuning suggested in the Wiki. One thing I notice is that the CPU is > used for 30% on Interrupts. It was firewire first, so I disabled it in > the BIOS, then it went to UHCI so I disabled all USB ports. Now it is > on the ATA controller. All of this was on the same interrupt (19). IRQ sharing is generally a "thing of the past", and interrupt conflicts are something from days prior to APICs being available on every motherboard under the sun. Meaning: "swapping around" IRQs for onboard devices rarely does anything in this day and age. > I'm thinking of getting a couple of Promise SATA-300 TX4 IO cards > (non-raid). Perhaps that will offload the CPU. I don't see how that's going to help with heavy interrupt usage. 30% interrupt usage across 5 disks doesn't sound too odd, and going with a Promise controller that doesn't have its own dedicated driver (read: it will use ata(4)) won't address that. You might be better off getting actual server hardware rather than "hacked up to be server" desktop hardware. Consider Supermicro stuff. I can personally recommend their PDSMi+ motherboard, and many other FreeBSD users rely heavily on their hardware. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From fbsd at dannysplace.net Fri Jun 27 07:02:33 2008 From: fbsd at dannysplace.net (Danny Carroll) Date: Fri Jun 27 07:02:38 2008 Subject: new server motherboard with SATA II In-Reply-To: <20080627053103.GB9582@bacardi> References: <486450DB.4000907@dannysplace.net> <20080627040545.GA21856@eos.sc1.parodius.com> <4864769C.4050002@dannysplace.net> <20080627053103.GB9582@bacardi> Message-ID: <48649080.1070802@dannysplace.net> Fraser Tweedale wrote: > Intel chips support AMD64 - the architecture is called that because AMD > came up with it first. Intel calls their implementation EM64T (and > x86-64 refers to the same thing), but it is all AMD64. Wow, never knew that.... Does that mean I can run the AMD64 version on my Core2 Duo E6550? -D From fbsd at dannysplace.net Fri Jun 27 07:18:06 2008 From: fbsd at dannysplace.net (Danny Carroll) Date: Fri Jun 27 07:18:11 2008 Subject: new server motherboard with SATA II In-Reply-To: <20080627053314.GA24239@eos.sc1.parodius.com> References: <486450DB.4000907@dannysplace.net> <20080627040545.GA21856@eos.sc1.parodius.com> <4864769C.4050002@dannysplace.net> <20080627053314.GA24239@eos.sc1.parodius.com> Message-ID: <48649424.4010700@dannysplace.net> Jeremy Chadwick wrote: > This comes as no surprise, as there is no ICH10 knowledge in the PCI and > ATA code at this time. ICH10 is ***very*** new, as in probably within > the past 6 weeks, no? > Yes.... It's a new desktop machine that I am toying with before it needs to go to it's permanent owner. > You're greatly confused with regards to what "amd64" means. FreeBSD's > 32-bit operating system is called i386. FreeBSD's 64-bit operating > system is called amd64. It has absolutely **nothing** to do with > processor types (AMD vs. Intel). You can understand how that can happen I guess. But thanks for setting me straight. > FreeBSD's ability to boot off of FreeBSD-managed-RAID'd volumes is > horrible. Administrators have to go through a bunch of rigmarole to > accomplish something that should be an absolute simplicity/necessity in > this day and age. This is one reason why I myself have considered using > Intel MatrixRAID, because then that "layer" is generally transparent to > FreeBSD. > > In fact, ZFS on a root filesystem is still a "pain", yet Solaris has it > down pat. I had that whole hassle with either vinum or gmirror (can't remember which). That's why this time I decided on a dedicated disk. So long as I have a backup I don't care about a days downtime for the OS. > There's a chance you'll see it on brand new SATA300 disks with all sorts > of different SATA controller hardware (not limited to just one vendor), > too. The problem is somewhere within FreeBSD, and my Wiki page > documents a workaround/patch that the FreeNAS guys came up with, which > has sat ignored for over a year by the FreeBSD ATA maintainer. Not a > good sign. Did it make it into 7-Current? > Keep in mind that there have been some reports of ZFS on FreeBSD > behaving incorrectly/oddly when a disk goes back, or a checksum error is > found by ZFS. The disk will resilver for no apparent reason. Hmmmm.... > IRQ sharing is generally a "thing of the past", and interrupt conflicts > are something from days prior to APICs being available on every > motherboard under the sun. Meaning: "swapping around" IRQs for onboard > devices rarely does anything in this day and age. > >> I'm thinking of getting a couple of Promise SATA-300 TX4 IO cards >> (non-raid). Perhaps that will offload the CPU. > > I don't see how that's going to help with heavy interrupt usage. 30% > interrupt usage across 5 disks doesn't sound too odd, and going with a > Promise controller that doesn't have its own dedicated driver (read: it > will use ata(4)) won't address that. 30%.... Even at idle? Granted it did not increase much with heavy IO but it surprised me a little that it's so high to start with. So which controllers have their own driver/processors onboard that can eliminate the CPU hogging. > You might be better off getting actual server hardware rather than > "hacked up to be server" desktop hardware. Consider Supermicro stuff. > I can personally recommend their PDSMi+ motherboard, and many other > FreeBSD users rely heavily on their hardware. Well I still have the option to choose something so I'm open to all sorts of suggestions. And actually that's kinda the point to me starting this post. To find out what hardware does great IO with Sata. I was also looking at TYAN gear. I've used it in the past and been happy (but performance was never really an issue then). Thanks so much for the tips so far. -D From koitsu at FreeBSD.org Fri Jun 27 07:36:12 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Fri Jun 27 07:36:15 2008 Subject: new server motherboard with SATA II In-Reply-To: <48649424.4010700@dannysplace.net> References: <486450DB.4000907@dannysplace.net> <20080627040545.GA21856@eos.sc1.parodius.com> <4864769C.4050002@dannysplace.net> <20080627053314.GA24239@eos.sc1.parodius.com> <48649424.4010700@dannysplace.net> Message-ID: <20080627073612.GA29122@eos.sc1.parodius.com> On Fri, Jun 27, 2008 at 05:17:56PM +1000, Danny Carroll wrote: >> There's a chance you'll see it on brand new SATA300 disks with all sorts >> of different SATA controller hardware (not limited to just one vendor), >> too. The problem is somewhere within FreeBSD, and my Wiki page >> documents a workaround/patch that the FreeNAS guys came up with, which >> has sat ignored for over a year by the FreeBSD ATA maintainer. Not a >> good sign. > > Did it make it into 7-Current? 7-CURRENT existed back in mid to late 2007; there is no 7-CURRENT now. And no, none of the patches provided by the FreeNAS people ever made it into the FreeBSD source tree. In fact, sos@ never even responded to their mails. This is the 5th or 6th time I've heard of this situation happening (ATA driver author not responding to people who submit patches, submit PRs, or general Email). It's growing very old. >> IRQ sharing is generally a "thing of the past", and interrupt conflicts >> are something from days prior to APICs being available on every >> motherboard under the sun. Meaning: "swapping around" IRQs for onboard >> devices rarely does anything in this day and age. >> >>> I'm thinking of getting a couple of Promise SATA-300 TX4 IO cards >>> (non-raid). Perhaps that will offload the CPU. >> >> I don't see how that's going to help with heavy interrupt usage. 30% >> interrupt usage across 5 disks doesn't sound too odd, and going with a >> Promise controller that doesn't have its own dedicated driver (read: it >> will use ata(4)) won't address that. > > 30%.... Even at idle? Granted it did not increase much with heavy IO > but it surprised me a little that it's so high to start with. No, it should not happen at idle. You said "interrupt usage across 5 disks", which I read to mean "interrupt usage is very high during I/O across a zpool consisting of 5 disks". I misunderstood. IRQ sharing could result in what you see, but it sounds more like some weird interrupt routing/bug that might be specific to that Asus board. > So which controllers have their own driver/processors onboard that can > eliminate the CPU hogging. The FreeBSD Handbook has a list of hardware. Anything that has its own xxx(4) driver (e.g. twa(4), twe(4), arcmsr(4), etc.) will suffice. Many of these cards handle SATA disks which appear as daX in FreeBSD, since they act as SCSI controllers. SCSI CAM on FreeBSD is quite reliable. Currently, the best SATA controllers I've seen that have native FreeBSD support (meaning the vendor supports FreeBSD) are Areca controllers. I have no experience with them due to their cost, but they are *very* fast. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From koitsu at FreeBSD.org Fri Jun 27 07:37:53 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Fri Jun 27 07:37:57 2008 Subject: new server motherboard with SATA II In-Reply-To: <48649080.1070802@dannysplace.net> References: <486450DB.4000907@dannysplace.net> <20080627040545.GA21856@eos.sc1.parodius.com> <4864769C.4050002@dannysplace.net> <20080627053103.GB9582@bacardi> <48649080.1070802@dannysplace.net> Message-ID: <20080627073753.GA29789@eos.sc1.parodius.com> On Fri, Jun 27, 2008 at 05:02:24PM +1000, Danny Carroll wrote: > Fraser Tweedale wrote: >> Intel chips support AMD64 - the architecture is called that because AMD >> came up with it first. Intel calls their implementation EM64T (and >> x86-64 refers to the same thing), but it is all AMD64. > > Wow, never knew that.... Does that mean I can run the AMD64 version on > my Core2 Duo E6550? Yes. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From fbsd at dannysplace.net Fri Jun 27 07:45:58 2008 From: fbsd at dannysplace.net (Danny Carroll) Date: Fri Jun 27 07:46:03 2008 Subject: new server motherboard with SATA II In-Reply-To: <20080627073612.GA29122@eos.sc1.parodius.com> References: <486450DB.4000907@dannysplace.net> <20080627040545.GA21856@eos.sc1.parodius.com> <4864769C.4050002@dannysplace.net> <20080627053314.GA24239@eos.sc1.parodius.com> <48649424.4010700@dannysplace.net> <20080627073612.GA29122@eos.sc1.parodius.com> Message-ID: <48649AAD.4050806@dannysplace.net> Jeremy Chadwick wrote: > No, it should not happen at idle. You said "interrupt usage across 5 > disks", which I read to mean "interrupt usage is very high during I/O > across a zpool consisting of 5 disks". I misunderstood. > > IRQ sharing could result in what you see, but it sounds more like some > weird interrupt routing/bug that might be specific to that Asus board. That's kinda what I fear might be the case. > The FreeBSD Handbook has a list of hardware. Anything that has its own > xxx(4) driver (e.g. twa(4), twe(4), arcmsr(4), etc.) will suffice. Many > of these cards handle SATA disks which appear as daX in FreeBSD, since > they act as SCSI controllers. SCSI CAM on FreeBSD is quite reliable. > > Currently, the best SATA controllers I've seen that have native FreeBSD > support (meaning the vendor supports FreeBSD) are Areca controllers. I > have no experience with them due to their cost, but they are *very* > fast. Ouch.... Are the any other options? I'd be happy with a card that simply exposed the drive to FreeBSD rather than implemented Raid. Although I won't rule hardware raid out either (given a product that was fast enough). -D From koitsu at FreeBSD.org Fri Jun 27 07:53:00 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Fri Jun 27 07:53:04 2008 Subject: new server motherboard with SATA II In-Reply-To: <48649AAD.4050806@dannysplace.net> References: <486450DB.4000907@dannysplace.net> <20080627040545.GA21856@eos.sc1.parodius.com> <4864769C.4050002@dannysplace.net> <20080627053314.GA24239@eos.sc1.parodius.com> <48649424.4010700@dannysplace.net> <20080627073612.GA29122@eos.sc1.parodius.com> <48649AAD.4050806@dannysplace.net> Message-ID: <20080627075300.GA30448@eos.sc1.parodius.com> On Fri, Jun 27, 2008 at 05:45:49PM +1000, Danny Carroll wrote: > Jeremy Chadwick wrote: >> No, it should not happen at idle. You said "interrupt usage across 5 >> disks", which I read to mean "interrupt usage is very high during I/O >> across a zpool consisting of 5 disks". I misunderstood. >> >> IRQ sharing could result in what you see, but it sounds more like some >> weird interrupt routing/bug that might be specific to that Asus board. > > That's kinda what I fear might be the case. > >> The FreeBSD Handbook has a list of hardware. Anything that has its own >> xxx(4) driver (e.g. twa(4), twe(4), arcmsr(4), etc.) will suffice. Many >> of these cards handle SATA disks which appear as daX in FreeBSD, since >> they act as SCSI controllers. SCSI CAM on FreeBSD is quite reliable. >> >> Currently, the best SATA controllers I've seen that have native FreeBSD >> support (meaning the vendor supports FreeBSD) are Areca controllers. I >> have no experience with them due to their cost, but they are *very* >> fast. > > Ouch.... Are the any other options? > I'd be happy with a card that simply exposed the drive to FreeBSD rather > than implemented Raid. Although I won't rule hardware raid out either > (given a product that was fast enough). In that case, Promise cards are probably your best bet. They'll use the ata(4) driver, and disks will show up as adX, and they're inexpensive. Plus, the FreeBSD ATA author (sos@) has significant documentation on them, so they're fairly well supported. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From soralx at cydem.org Fri Jun 27 08:23:20 2008 From: soralx at cydem.org (soralx@cydem.org) Date: Fri Jun 27 08:23:24 2008 Subject: new server motherboard with SATA II In-Reply-To: <4864769C.4050002@dannysplace.net> References: <486450DB.4000907@dannysplace.net> <20080627040545.GA21856@eos.sc1.parodius.com> <4864769C.4050002@dannysplace.net> Message-ID: <20080627012253.07e629e0@freen0de> > I'm thinking of getting a couple of Promise SATA-300 TX4 IO cards > (non-raid). Perhaps that will offload the CPU. Loading PCI bus with more plain SATA controllers? Don't expect any positive results. How about something like this: http://cgi.ebay.ca/ws/eBayISAPI.dll?ViewItem&item=330240176734 (PERC 5/i SAS RAID controller HBA, PCIe x8, 256MB RAM) -- $120 This should give you ~300-400 MB/s with your 5 drives. It might not work with your mainboard, though -- but there's a trick to isolate SMBus pins the card edge connector (search the Net). > -D [SorAlx] ridin' VN1500-B2 From fbsd at dannysplace.net Fri Jun 27 08:35:07 2008 From: fbsd at dannysplace.net (Danny Carroll) Date: Fri Jun 27 08:35:12 2008 Subject: new server motherboard with SATA II In-Reply-To: <20080627075300.GA30448@eos.sc1.parodius.com> References: <486450DB.4000907@dannysplace.net> <20080627040545.GA21856@eos.sc1.parodius.com> <4864769C.4050002@dannysplace.net> <20080627053314.GA24239@eos.sc1.parodius.com> <48649424.4010700@dannysplace.net> <20080627073612.GA29122@eos.sc1.parodius.com> <48649AAD.4050806@dannysplace.net> <20080627075300.GA30448@eos.sc1.parodius.com> Message-ID: <20080627183506.atac8jmckkswcgc8@www.dannysplace.net> Quoting Jeremy Chadwick : > In that case, Promise cards are probably your best bet. They'll use the > ata(4) driver, and disks will show up as adX, and they're inexpensive. > Plus, the FreeBSD ATA author (sos@) has significant documentation on > them, so they're fairly well supported. That's a shame that there is no middle of the road... It does not seem a lot to ask for an IO card that can ease processing on the CPU for SATA II devices. Like I said I'd be happy to let FreeBSD handle the raid stuff because ZFS just looks so handy. -D From fbsd at dannysplace.net Fri Jun 27 08:42:18 2008 From: fbsd at dannysplace.net (Danny Carroll) Date: Fri Jun 27 08:42:22 2008 Subject: new server motherboard with SATA II In-Reply-To: <20080627012253.07e629e0@freen0de> References: <486450DB.4000907@dannysplace.net> <20080627040545.GA21856@eos.sc1.parodius.com> <4864769C.4050002@dannysplace.net> <20080627012253.07e629e0@freen0de> Message-ID: <20080627184216.m7nz0snpwso8c4k4@www.dannysplace.net> Quoting soralx@cydem.org: > Loading PCI bus with more plain SATA controllers? Don't expect any > positive results. I was under the impression that the promise cards actually offloaded some of the work, but I guess that can only happen with raid cards that present one disc to the OS. > How about something like this: > http://cgi.ebay.ca/ws/eBayISAPI.dll?ViewItem&item=330240176734 > (PERC 5/i SAS RAID controller HBA, PCIe x8, 256MB RAM) -- $120 > > This should give you ~300-400 MB/s with your 5 drives. It might not work > with your mainboard, though -- but there's a trick to isolate SMBus pins > the card edge connector (search the Net). Definately has potential. I think I might first focus on a motherboard that has a well supported IO chipset. If I can get over 200Mb accross the whole array then I'll be happy. After that I will look at a decent quality raid card. -D From soralx at cydem.org Fri Jun 27 15:11:14 2008 From: soralx at cydem.org (soralx@cydem.org) Date: Fri Jun 27 15:11:21 2008 Subject: new server motherboard with SATA II In-Reply-To: <20080627184216.m7nz0snpwso8c4k4@www.dannysplace.net> References: <486450DB.4000907@dannysplace.net> <20080627040545.GA21856@eos.sc1.parodius.com> <4864769C.4050002@dannysplace.net> <20080627012253.07e629e0@freen0de> <20080627184216.m7nz0snpwso8c4k4@www.dannysplace.net> Message-ID: <20080627080939.23c29ea8@soralx> I wrote: > > How about something like this: > > http://cgi.ebay.ca/ws/eBayISAPI.dll?ViewItem&item=330240176734 > > (PERC 5/i SAS RAID controller HBA, PCIe x8, 256MB RAM) -- $120 > > > > This should give you ~300-400 MB/s with your 5 drives. It might not work > > with your mainboard, though -- but there's a trick to isolate SMBus pins > > the card edge connector (search the Net). > > Definately has potential. Scratch that, the card's performance is super low, lower than the grass. I'm testing it right now with two 15k.4 Cheetahs in mirror RAID. Two simultaneous reads [0] give ~19MB/s each (the drives can do >90MB/s each). Looks like the drives are getting thrashed with seeks (i.e., it can't read from both simultaneously!). Write performance [1] is only 50MB/s for single thread, and 20MB/s for 2 threads. bonnie++ measures ~22MB/s for writes too; the other figures look respectable, though, and blogbench shows some all right results (I can redo benchmarks and copy the results later if anyone cares). Maybe it performs better in striped arrays. I remember seeing figures like 500MB/s on forums, but I guess they tested only one thread at a time. [0] `dd if=/dev/mfid0 bs=64k count=65535 &` `dd if=/dev/mfid0 bs=64k count=65535 skip=132768 &` [1] dd'ing to file[s] on UFS2 slice > I think I might first focus on a motherboard that has a well supported > IO chipset. If I can get over 200Mb accross the whole array then I'll > be happy. > > After that I will look at a decent quality raid card. > > -D [SorAlx] ridin' VS1400 From bseklecki at collaborativefusion.com Mon Jun 30 15:36:41 2008 From: bseklecki at collaborativefusion.com (Brian A. Seklecki) Date: Mon Jun 30 15:36:44 2008 Subject: PERC5 (LSI MegaSAS) Patrol Read crashes In-Reply-To: <1195160114.4042.154.camel@new-host> References: <20071114122210.42E8613C4BB@mx1.freebsd.org> <1195160114.4042.154.camel@new-host> Message-ID: <1214840198.18670.43.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> On Thu, 2007-11-15 at 15:55 -0500, Brian A Seklecki (Mobile) wrote: > Normally I'd be praising Dell, but I think a little vendor bashing is > due here. All: Just to follow up, we've been running these 1st-generation 2950s in our lab with RHEl5.2 x86_64 for ~3 weeks w/o any disk or I/O problems. It must have been some random bug with the FreeBSD mfi(4) that only affected that revision of the PERC5, or, since the motherboard/CPU family/chipset is entirely different in R2 and R3, something with FreeBSD and how it was handling the controller (ACPI?) We never had any stability problems with R2 and R3 on RELENG_6_3 on the 2950 or 1950. >From now on we'll wait for R2 before we go anywhere near new Dell gear. What do you think the chances of them dumping LSI for Acera and Broadcom for Intel? :) ~BAS > Its a software bug (driver). It can probably be easily fixed. I > think there's a PR on it somewhere (will check). -- Brian A. Seklecki Collaborative Fusion, Inc. From scottl at samsco.org Mon Jun 30 16:47:33 2008 From: scottl at samsco.org (Scott Long) Date: Mon Jun 30 16:47:35 2008 Subject: PERC5 (LSI MegaSAS) Patrol Read crashes In-Reply-To: <1214840198.18670.43.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> References: <20071114122210.42E8613C4BB@mx1.freebsd.org> <1195160114.4042.154.camel@new-host> <1214840198.18670.43.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> Message-ID: <486909B1.3020309@samsco.org> Brian A. Seklecki wrote: > On Thu, 2007-11-15 at 15:55 -0500, Brian A Seklecki (Mobile) wrote: >> Normally I'd be praising Dell, but I think a little vendor bashing is >> due here. > > All: > > Just to follow up, we've been running these 1st-generation 2950s in our > lab with RHEl5.2 x86_64 for ~3 weeks w/o any disk or I/O problems. > > It must have been some random bug with the FreeBSD mfi(4) that only > affected that revision of the PERC5, or, since the motherboard/CPU > family/chipset is entirely different in R2 and R3, something with > FreeBSD and how it was handling the controller (ACPI?) > > We never had any stability problems with R2 and R3 on RELENG_6_3 on the > 2950 or 1950. > >>From now on we'll wait for R2 before we go anywhere near new Dell > gear. > > What do you think the chances of them dumping LSI for Acera and Broadcom > for Intel? :) > > ~BAS > >> Its a software bug (driver). It can probably be easily fixed. I >> think there's a PR on it somewhere (will check). The problem is a firmware bug in the Megaraid SAS controller. It seems that while the controller can handle 512 or more concurrent commands, it can only handle 128 concurrent commands to each array. Patrols reads aren't the primary cause, they just help the problem appear; when a patrol read cycle runs, it tends to slow down i/o enough that commands to the array get backed up, and you tend to reach the 128 limit. I don't know if there is a firmware fix from Dell/LSI, or if there will ever be a fix. FreeBSD drivers tend to stress hardware a lot more than Linux and Windows do, and since the latter two are used as the QA yardstick, anything that doesn't affect them doesn't usually get fixed. An easy work-around for the driver is to change the following line in /sys/dev/mfi/mfi.c::mfi_alloc_commands() ncmds = sc->mfi_max_fw_cmds; to ncmds = 128; A more complete solution requires me writing an i/o scheduler in the driver, something that would take quite a bit of effort. With all this said, I still stand behind LSI controllers. This bug, while unfortunate, is relatively minor and easy to work around, and it's the only significant bug that has turned up in over two and half years with this hardware. Scott From felipebgn at gmail.com Mon Jun 30 21:05:46 2008 From: felipebgn at gmail.com (Felipe Neuwald) Date: Mon Jun 30 21:05:49 2008 Subject: FreeBSD and IBM Blades Message-ID: <928b5da90806301338g748ec7e6y1ef0531b43fbf164@mail.gmail.com> Hi All, Does anybody running FreeBSD on IBM Blades? If yes (or no), can tell me about your experience? Thanks, Felipe Neuwald.