From gpagnoni at gmail.com Thu Oct 2 16:53:13 2008 From: gpagnoni at gmail.com (Giuseppe Pagnoni) Date: Thu Oct 2 16:53:20 2008 Subject: LG combo drive and Attansic Technology ethernet card on Asus P5Q Pro Message-ID: <92056ebc0810020932w680c593er585dd865ef8af538@mail.gmail.com> Dear FreeBSD experts, I am trying to install FreeBSD 7.0 on a new i386 machine with no OS installed yet. I start the install process with the 1st CD of the distribution, and I go through the partition phase with no problem. However, when I get to the point where I select the installation media (CD/DVD) it says that it cannot find the CD/DVD. I read on the FAQ list on the FreeBSD site that this can happen when the drive is configured as a slave with no master. So I opened up the box, and I saw that the drive has its own ATAPI/IDE cable/slot on the motherboard and the jumpers on the drive are set as MASTER. The drive is a new LG combo drive, I believe GH22LP20 or something close to it. I also tried to install Ubuntu and it works fine (but I really would like to have FreeBSD!). On an unrelated topic, does anybody know whether the network card Attansic Technology on Asus P5Q Pro motherboard is compatible with FreeBSD? Any help or suggestion will be highly appreciated, thanks in advance giuseppe -- Dip. Scienze Biomediche Sezione Fisiologia Univ. di Modena e Reggio Emilia Via Campi 287 I-41100 Modena, Italy Tel: +39-059-205-5742 Fax: +39-059-205-5363 From koitsu at FreeBSD.org Thu Oct 2 23:18:51 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Thu Oct 2 23:19:22 2008 Subject: LG combo drive and Attansic Technology ethernet card on Asus P5Q Pro In-Reply-To: <92056ebc0810020932w680c593er585dd865ef8af538@mail.gmail.com> References: <92056ebc0810020932w680c593er585dd865ef8af538@mail.gmail.com> Message-ID: <20081002231848.GA13467@icarus.home.lan> On Thu, Oct 02, 2008 at 06:32:20PM +0200, Giuseppe Pagnoni wrote: > I am trying to install FreeBSD 7.0 on a new i386 machine with no OS > installed yet. I start the install process with the 1st CD of the > distribution, and I go through the partition phase with no problem. > However, when I get to the point where I select the installation media > (CD/DVD) it says that it cannot find the CD/DVD. > > I read on the FAQ list on the FreeBSD site that this can happen when > the drive is configured as a slave with no master. So I opened up the > box, and I saw that the drive has its own ATAPI/IDE cable/slot on the > motherboard and the jumpers on the drive are set as MASTER. > > The drive is a new LG combo drive, I believe GH22LP20 or something close to it. > > I also tried to install Ubuntu and it works fine (but I really would > like to have FreeBSD!). The only thing I can think of is that the P5Q boards use a Marvell ATA/IDE controller (yes, you read that correctly). I wonder if FreeBSD somehow lacks support for this... What confuses me is that you can boot the CD media, and FreeBSD will load kernel modules and a copy of the mini filesystem into memory off the CD, yet it can't actually find the CD come installation time. > On an unrelated topic, does anybody know whether the network card > Attansic Technology on Asus P5Q Pro motherboard is compatible with > FreeBSD? Asus was somewhat vague as to what model of Attansic/Atheros IC they used on the P5Q series. I have one of these boards, so I can assure you it's an Attansic L1E. It's sometimes referred to as an Atheros AR8121, AR8113, or AR8114. FreeBSD 7.1-PRERELEASE has support for this NIC; age(4) is the driver. 7.0 will very likely not support this NIC. Please download the 7.1-PRERELEASE ISO from here, and try installing using it instead. ftp://ftp4.freebsd.org/pub/FreeBSD/snapshots/200809/ If finding the CD/DVD media still does not work, let us know and I will try to reproduce the problem on my P5Q SE. -- | 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 michael at fuckner.net Fri Oct 3 07:58:18 2008 From: michael at fuckner.net (Michael Fuckner) Date: Fri Oct 3 07:58:26 2008 Subject: LG combo drive and Attansic Technology ethernet card on Asus P5Q Pro In-Reply-To: <20081002231848.GA13467@icarus.home.lan> References: <92056ebc0810020932w680c593er585dd865ef8af538@mail.gmail.com> <20081002231848.GA13467@icarus.home.lan> Message-ID: <48E5CC2F.4070009@fuckner.net> Jeremy Chadwick wrote: > On Thu, Oct 02, 2008 at 06:32:20PM +0200, Giuseppe Pagnoni wrote: >> The drive is a new LG combo drive, I believe GH22LP20 or something close to it. >> >> I also tried to install Ubuntu and it works fine (but I really would >> like to have FreeBSD!). > > The only thing I can think of is that the P5Q boards use a Marvell > ATA/IDE controller (yes, you read that correctly). I wonder if FreeBSD > somehow lacks support for this... > > What confuses me is that you can boot the CD media, and FreeBSD will > load kernel modules and a copy of the mini filesystem into memory off > the CD, yet it can't actually find the CD come installation time. First sectors are read by the bios, the kernel is loaded and executed. The Kernel doesn't know anything about this Controller, so it can't access the CD. My advice is to disable the crappy Marvell Chip and get a SATA-DVD. I'm sorry, I don't know about the status of the Attansic-Lan. You can add another supported NIC with Intel Chipset or something else that is supported. Regards, Michael! From pyunyh at gmail.com Fri Oct 3 08:25:01 2008 From: pyunyh at gmail.com (Pyun YongHyeon) Date: Fri Oct 3 08:25:09 2008 Subject: LG combo drive and Attansic Technology ethernet card on Asus P5Q Pro In-Reply-To: <20081002231848.GA13467@icarus.home.lan> References: <92056ebc0810020932w680c593er585dd865ef8af538@mail.gmail.com> <20081002231848.GA13467@icarus.home.lan> Message-ID: <20081003082257.GC71518@cdnetworks.co.kr> On Thu, Oct 02, 2008 at 04:18:48PM -0700, Jeremy Chadwick wrote: > On Thu, Oct 02, 2008 at 06:32:20PM +0200, Giuseppe Pagnoni wrote: [...] > > > On an unrelated topic, does anybody know whether the network card > > Attansic Technology on Asus P5Q Pro motherboard is compatible with > > FreeBSD? > > Asus was somewhat vague as to what model of Attansic/Atheros IC they > used on the P5Q series. I have one of these boards, so I can assure > you it's an Attansic L1E. It's sometimes referred to as an Atheros > AR8121, AR8113, or AR8114. > > FreeBSD 7.1-PRERELEASE has support for this NIC; age(4) is the driver. > 7.0 will very likely not support this NIC. > If the controller is AR8121/AR8113 PCI-E adapters(also known as L1E) there is no working driver for FreeBSD. Because the controller is quite different from its predecessor L1, new driver should be written for the controller. It's not feasible for me to write the driver until I can actually access the hardware. :-( -- Regards, Pyun YongHyeon From koitsu at FreeBSD.org Fri Oct 3 10:58:31 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Fri Oct 3 10:58:38 2008 Subject: LG combo drive and Attansic Technology ethernet card on Asus P5Q Pro In-Reply-To: <20081003082257.GC71518@cdnetworks.co.kr> References: <92056ebc0810020932w680c593er585dd865ef8af538@mail.gmail.com> <20081002231848.GA13467@icarus.home.lan> <20081003082257.GC71518@cdnetworks.co.kr> Message-ID: <20081003105828.GA27057@icarus.home.lan> On Fri, Oct 03, 2008 at 05:22:57PM +0900, Pyun YongHyeon wrote: > On Thu, Oct 02, 2008 at 04:18:48PM -0700, Jeremy Chadwick wrote: > > On Thu, Oct 02, 2008 at 06:32:20PM +0200, Giuseppe Pagnoni wrote: > > [...] > > > > > > On an unrelated topic, does anybody know whether the network card > > > Attansic Technology on Asus P5Q Pro motherboard is compatible with > > > FreeBSD? > > > > Asus was somewhat vague as to what model of Attansic/Atheros IC they > > used on the P5Q series. I have one of these boards, so I can assure > > you it's an Attansic L1E. It's sometimes referred to as an Atheros > > AR8121, AR8113, or AR8114. > > > > FreeBSD 7.1-PRERELEASE has support for this NIC; age(4) is the driver. > > 7.0 will very likely not support this NIC. > > > > If the controller is AR8121/AR8113 PCI-E adapters(also known as > L1E) there is no working driver for FreeBSD. Because the controller > is quite different from its predecessor L1, new driver should be > written for the controller. > It's not feasible for me to write the driver until I can actually > access the hardware. :-( Wow, I was under the impression the L1 and the L1E were identical, except that the L1E was PCI Express-based vs. PCI-based. The Attansic L1E stuff is becoming more and more common here on motherboards in the States. Yong-Hyeon, I can get you a P5Q SE motherboard and send it your way (with CPU + memory as well, if need be), if you'd like. -- | 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 gpagnoni at gmail.com Fri Oct 3 14:50:39 2008 From: gpagnoni at gmail.com (Giuseppe Pagnoni) Date: Fri Oct 3 14:50:45 2008 Subject: LG combo drive and Attansic Technology ethernet card on Asus P5Q Pro In-Reply-To: <20081002231848.GA13467@icarus.home.lan> References: <92056ebc0810020932w680c593er585dd865ef8af538@mail.gmail.com> <20081002231848.GA13467@icarus.home.lan> Message-ID: <92056ebc0810030750g7275e60fw147983fb9efa7ab6@mail.gmail.com> Dear Jeremy, thank you very much for your help. I downloaded the 7.1 prerelease, but unfortunately didn't solve the problem with the CD/DVD. As for the ethernet card, it's a kind of catch 22: to see if the card is working I should install the OS, but I cannot from the DVD. I cannot even install over FTP, because the institution I am in wants my MAC address to allow this pc to connect to internet and I cannot get to the MAC address without installing an OS (at least, I don't know how... I tried an Ubuntu LiveCD, but it doesn't recognize the ethernet card, either). Since I have other problems with this machine, I am thinking about returning it. I wonder whether you could point me to some sure FreeBSD compatible hardware which is in the ballpark of this machine in terms of configuration. I tried to look in the Release Hardware note, but it's a bit difficult for me to match all the hardware codes to their physical counterparts! This is what I have currently: Motherboard: Asus P5Q Pro Processor: INTEL Core 2 Duo E8500 CD/DVD: LG GH22LP20 Graphics: nVidia GeForce 8500GT (512Mb PCI-E) Controller EIDE PCI + SATA 2 RAID (500Gb each) RAM: 4 GB, 800 Mhz (by the way, I never understood if the processor can address or not 4GB... should I just get 3GB?) Thank you very much for any advice, but please ignore this if it takes too much of your time. very best giuseppe On Fri, Oct 3, 2008 at 1:18 AM, Jeremy Chadwick wrote: > On Thu, Oct 02, 2008 at 06:32:20PM +0200, Giuseppe Pagnoni wrote: >> I am trying to install FreeBSD 7.0 on a new i386 machine with no OS >> installed yet. I start the install process with the 1st CD of the >> distribution, and I go through the partition phase with no problem. >> However, when I get to the point where I select the installation media >> (CD/DVD) it says that it cannot find the CD/DVD. >> >> I read on the FAQ list on the FreeBSD site that this can happen when >> the drive is configured as a slave with no master. So I opened up the >> box, and I saw that the drive has its own ATAPI/IDE cable/slot on the >> motherboard and the jumpers on the drive are set as MASTER. >> >> The drive is a new LG combo drive, I believe GH22LP20 or something close to it. >> >> I also tried to install Ubuntu and it works fine (but I really would >> like to have FreeBSD!). > > The only thing I can think of is that the P5Q boards use a Marvell > ATA/IDE controller (yes, you read that correctly). I wonder if FreeBSD > somehow lacks support for this... > > What confuses me is that you can boot the CD media, and FreeBSD will > load kernel modules and a copy of the mini filesystem into memory off > the CD, yet it can't actually find the CD come installation time. > >> On an unrelated topic, does anybody know whether the network card >> Attansic Technology on Asus P5Q Pro motherboard is compatible with >> FreeBSD? > > Asus was somewhat vague as to what model of Attansic/Atheros IC they > used on the P5Q series. I have one of these boards, so I can assure > you it's an Attansic L1E. It's sometimes referred to as an Atheros > AR8121, AR8113, or AR8114. > > FreeBSD 7.1-PRERELEASE has support for this NIC; age(4) is the driver. > 7.0 will very likely not support this NIC. > > Please download the 7.1-PRERELEASE ISO from here, and try installing > using it instead. > > ftp://ftp4.freebsd.org/pub/FreeBSD/snapshots/200809/ > > If finding the CD/DVD media still does not work, let us know and I will > try to reproduce the problem on my P5Q SE. > > -- > | 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 | > > -- Dip. Scienze Biomediche Sezione Fisiologia Univ. di Modena e Reggio Emilia Via Campi 287 I-41100 Modena, Italy Tel: +39-059-205-5742 Fax: +39-059-205-5363 From scheidell at secnap.net Fri Oct 3 19:18:20 2008 From: scheidell at secnap.net (Michael Scheidell) Date: Fri Oct 3 19:18:51 2008 Subject: Intel 6300ESB SATA150 cannot find disk or boot under 6.3 Message-ID: <48E66ACE.7060702@secnap.net> Amazingly, this has been going on after a switch from 6.2 (which worked) to 6.3. lots of people have reported it, and we accidentally fixed it (but we can't find documentation on what we fixed). it also doesn't work on 7.0 either. here is a dmsg for a 6.3 one that accidentally works. (i have a kernel that works), tech playing around with it months ago can't remember if he used 6.2 drivers or found an obscure patch. Now that 5.5 is EOL, and we can't get ports for 5.5, it might be important for freebsd folks (in their spare time after 7.1 and 6.4 beta) to fix this. or, at least to fix it in 6.4. Yes, DELL 750, worked fine in 5.5 (lots of 5.5 systems I can't upgrade). suggestions that we replace the (faulty?) hard disk controller cause lots of problems. Its a different tech (more expensive) in the field that has to replace hardware, vs the one who can plug in a 6.3 CD rom and passively watch an automated upgrade. 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 6.3-RELEASE-p1 #0: Mon Apr 28 20:18:31 EDT 2008 root@someware Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2800.11-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf34 Stepping = 4 Features=0xbfebfbff Features2=0x441d Logical CPUs per core: 2 real memory = 1073479680 (1023 MB) avail memory = 1045966848 (997 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 2 ioapic1: Changing APIC ID to 3 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 cpu1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 3.0 on pci0 pci1: on pcib1 em0: port 0xece0-0xecff mem 0xfe3e0000-0xfe3fffff irq 18 at device 1.0 on pci1 em0: Ethernet address: 00:11:43:cd:36:d8 pcib2: at device 28.0 on pci0 pci2: on pcib2 em1: port 0xdcc0-0xdcff mem 0xfe1e0000-0xfe1fffff,0xfe1c0000-0xfe1dffff irq 24 at device 1.0 on pci2 em1: Ethernet address: 00:30:64:05:ef:58 em2: port 0xdc80-0xdcbf mem 0xfe1a0000-0xfe1bffff,0xfe180000-0xfe19ffff irq 25 at device 1.1 on pci2 em2: Ethernet address: 00:30:64:05:ef:59 uhci0: port 0xbce0-0xbcff irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xbcc0-0xbcdf irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci0: at device 29.4 (no driver attached) pci0: at device 29.7 (no driver attached) pcib3: at device 30.0 on pci0 pci3: on pcib3 em3: port 0xccc0-0xccff mem 0xfdee0000-0xfdefffff irq 21 at device 2.0 on pci3 em3: Ethernet address: 00:11:43:cd:36:d9 pci3: at device 14.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfea0-0xfeaf at device 31.2 on pci0 ata0: on atapci0 ata1: on atapci0 pci0: at device 31.3 (no driver attached) atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A orm0: at iomem 0xc0000-0xc7fff,0xc8000-0xc8fff,0xc9000-0xc9fff,0xec000-0xeffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec ipfw2 initialized, divert loadable, rule-based forwarding enabled, default to accept, logging disabled acd0: CDROM at ata0-master UDMA33 ad2: 38146MB at ata1-master SATA150 SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/ad2s1a bridge0: Ethernet address: aa:29:32:48:bd:5a wan: link state changed to UP con0: link state changed to UP -- Michael Scheidell, CTO Phone: 561-999-5000, x 1259 > *| *SECNAP Network Security Corporation * Certified SNORT Integrator * Everything Channel Hot Product of 2008 * Shaping Information Security Award 2008 * CRN Magazine Top 40 Emerging Security Vendors _________________________________________________________________________ This email has been scanned and certified safe by SpammerTrap(r). For Information please see http://www.spammertrap.com _________________________________________________________________________ From purchasing at itcomware1.com Fri Oct 3 22:10:53 2008 From: purchasing at itcomware1.com (purchasing) Date: Fri Oct 3 22:10:59 2008 Subject: Channel Partner-New Q4/08 Budget Available To Spend For Inventory & Orders. ( $2 Mil Per Mo.To Spend On Surplus Cisco) Message-ID: <5912d01c925a4$e3632680$6501a8c0@itemail> The following list of used gear is needed for purchase. This requirement is for used equipment. A new Q4 2008 budget is available to buy surplus Cisco, Nortel, Sun, Avaya, Lucent, Extreme, 3COM, IBM & HP products. I am ready to buy now and can pay the prices listed. Some items are for inventory and others for orders. If you have any situations like customer trade-in, failed deployment, overstock or decommissioned gear, send me a list and I will get you a cash offer immediately. Cisco WS-X4448-GB-RJ45 $1200.00 Cisco WS-X4548-GB-RJ45 $1,800.00 Cisco WS-C3560-8PC-S $475.00 Nortel 5510-48t $1,500.00 Brocade Silkworm 3250 $2,200.00 Cisco WS-C3750G-24TS-New $2,700.00 Cisco PA-MC-8TE1+ $2,050.00 Sun Micro 125-XUZ1C11GHZ $500.00 Dell PowerEdge 2950 2x 2.33GHz $2,500.00 Cisco AS5300 4E1 120 VoIP $2,400.00 Juniper Netscreen 208 NS-208-001 $1,000.00 Cisco NPE-G2 $7,000.00 CiscoNM-1T3/E3 $1,900.00 CiscoWS-X6704-10GE $5,200.00 Cisco WS-C3560-24TS-E $1,100.00 Cisco 2811 $700.00 Cisco WS-X4516 $2,300.00 Cisco 2821 $1100.00 Bob Ronzio International Buyer Itcomware 73 Defco Park Road North Haven, CT 06473 866.739.6291 - toll free 203.234.7248 - local 203.234.7507 - fax Skype - joe cisco Aim - itcomwarejp To be taken off this list, send a blank e-mail to purchasing@itcomware1.com From koitsu at FreeBSD.org Sat Oct 4 03:45:27 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Sat Oct 4 03:45:34 2008 Subject: LG combo drive and Attansic Technology ethernet card on Asus P5Q Pro In-Reply-To: <92056ebc0810030750g7275e60fw147983fb9efa7ab6@mail.gmail.com> References: <92056ebc0810020932w680c593er585dd865ef8af538@mail.gmail.com> <20081002231848.GA13467@icarus.home.lan> <92056ebc0810030750g7275e60fw147983fb9efa7ab6@mail.gmail.com> Message-ID: <20081004034524.GA44662@icarus.home.lan> On Fri, Oct 03, 2008 at 04:50:36PM +0200, Giuseppe Pagnoni wrote: > thank you very much for your help. I downloaded the 7.1 prerelease, > but unfortunately didn't solve the problem with the CD/DVD. As for > the ethernet card, it's a kind of catch 22: to see if the card is > working I should install the OS, but I cannot from the DVD. Understood. This situation is very frustrating; people often run into on Windows as well ("How do I get the Ethernet driver for my NIC from the web site if Windows doesn't already have support for my NIC?!"). > I cannot even install over FTP, because the institution I am in wants > my MAC address to allow this pc to connect to internet and I cannot > get to the MAC address without installing an OS (at least, I don't > know how... I tried an Ubuntu LiveCD, but it doesn't recognize the > ethernet card, either). Yong-Hyeon covered this; I was incorrect in assuming the Attansic L1E was just a PCI Express version of the L1. They are apparently different chips and are initialised differently. Yong-Hyeon doesn't have access to any hardware which uses the L1E, so writing a driver for it is going to be a bit difficult. :-( If needed, I can ship him an Asus P5Q SE board + CPU/RAM for testing and development (I have the CPU/RAM, but I would need to purchase the board). As far as the ATA/IDE stuff goes, that's going to be more difficult. I'm really surprised FreeBSD doesn't work with it. I might have to experiment with why that is on my own P5Q SE box; this would require Soren Schmidt (ata(4) author)'s involvement. > Since I have other problems with this machine, I am thinking about > returning it. I wonder whether you could point me to some sure > FreeBSD compatible hardware which is in the ballpark of this machine > in terms of configuration. I tried to look in the Release Hardware > note, but it's a bit difficult for me to match all the hardware codes > to their physical counterparts! This is what I have currently: My recommendation would be to keep the motherboard and purchase two pieces of hardware: 1) Intel Pro/1000 PT NIC (PCI Express) -- about US$35-45, 2) Any SATA-based Pioneer DVD drive -- about US$25-30. If you were in the States I'd send you the NIC free of cost, as my way of saying "I'm sorry for all the issues you're having with FreeBSD's hardware support". But I see you're in Italy. :-) If you want to go with another NIC, that's fine too -- I would recommend staying away from Realtek NICs. If you can find an older Intel Pro/100 NIC somewhere, that might be cheaper; those use the fxp(4) driver. This should allow you to get online reliably, and allow you to perform the FreeBSD installation using a SATA-based DVD drive hooked to the ICH controller, rather than the Marvell ATA/IDE controller. When FreeBSD gets support for the Attansic L1E chip, switching over to it would be painless. :-) > RAM: 4 GB, 800 Mhz (by the way, I never understood if the > processor can address or not 4GB... should I just get 3GB?) The processor and system *most definitely* can address more than 4GB. It just depends on how the OS supports it. FreeBSD has two flavours: i386 (32-bit) and amd64 (64-bit). i386 can address up to 4GB of RAM natively (see below), but you will probably only get ~3GB of that usable. The reason is limited memory address space; PCI Express, ACPI, and many other features (I can provide you a list or reference material if you want to see) cause some of the memory addressing space to be taken up. If you install more than 4GB on i386, you will have to use what's known as PAE mode. It's an Intel addressing extension to support >4GB of RAM on i386. There are many problems with it though; there's a performance hit, and there are known issues with drivers and FreeBSD features which you cannot use in PAE mode. When it comes to i386, I recommend people stick with 2 or 3GB, and avoid PAE mode at all costs. amd64 can address up to 256TB of RAM. Don't let the "amd64" term make you think it's intended for AMD processors; it works fine on both Intel and AMD processors. If you plan on installing 4GB or more memory in a system, I recommend considering amd64. However, there's one thing I remember reading somewhere. Someone will have to correct me if I'm wrong -- if you plan on using X Windows on an am64 system, be aware that nVidia does not provide an amd64-compatible video driver for FreeBSD. Hope this helps in your decisions. -- | 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 satz at iranger.com Sat Oct 4 06:22:05 2008 From: satz at iranger.com (satz@iranger.com) Date: Sat Oct 4 06:22:11 2008 Subject: Intel 6300ESB SATA150 cannot find disk or boot under 6.3 In-Reply-To: <48E66ACE.7060702@secnap.net> References: <48E66ACE.7060702@secnap.net> Message-ID: <51738.66.117.128.236.1223100187.squirrel@fnu.iranger.com> It is good to know this problem is larger then just me. It is a real issue in that I cannot begin to use the new port tools using 6.1. This exposes me to current and future security risks unless and until this problem is resolved. I don't know if the developers can determine how much risk there is out there but at least we know it is larger then 1. Anything I can do to help expedite this I will do. Thanks, Greg > Amazingly, this has been going on after a switch from 6.2 (which worked) > to 6.3. > lots of people have reported it, and we accidentally fixed it (but we > can't find documentation on what we fixed). > > it also doesn't work on 7.0 either. > here is a dmsg for a 6.3 one that accidentally works. > (i have a kernel that works), tech playing around with it months ago > can't remember if he used 6.2 drivers or found an obscure patch. > > Now that 5.5 is EOL, and we can't get ports for 5.5, it might be > important for freebsd folks (in their spare time after 7.1 and 6.4 beta) > to fix this. > > or, at least to fix it in 6.4. > > Yes, DELL 750, worked fine in 5.5 (lots of 5.5 systems I can't > upgrade). suggestions that we replace the (faulty?) hard disk > controller cause lots of problems. > Its a different tech (more expensive) in the field that has to replace > hardware, vs the one who can plug in a 6.3 CD rom and passively watch an > automated upgrade. > > 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 6.3-RELEASE-p1 #0: Mon Apr 28 20:18:31 EDT 2008 > root@someware > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2800.11-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf34 Stepping = 4 > Features=0xbfebfbff > Features2=0x441d > Logical CPUs per core: 2 > real memory = 1073479680 (1023 MB) > avail memory = 1045966848 (997 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > ioapic0: Changing APIC ID to 2 > ioapic1: Changing APIC ID to 3 > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 24-47 on motherboard > acpi0: on motherboard > acpi0: Power Button (fixed) > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 > cpu0: on acpi0 > cpu1: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: at device 3.0 on pci0 > pci1: on pcib1 > em0: port > 0xece0-0xecff mem 0xfe3e0000-0xfe3fffff irq 18 at device 1.0 on pci1 > em0: Ethernet address: 00:11:43:cd:36:d8 > pcib2: at device 28.0 on pci0 > pci2: on pcib2 > em1: port > 0xdcc0-0xdcff mem 0xfe1e0000-0xfe1fffff,0xfe1c0000-0xfe1dffff irq 24 at > device 1.0 on pci2 > em1: Ethernet address: 00:30:64:05:ef:58 > em2: port > 0xdc80-0xdcbf mem 0xfe1a0000-0xfe1bffff,0xfe180000-0xfe19ffff irq 25 at > device 1.1 on pci2 > em2: Ethernet address: 00:30:64:05:ef:59 > uhci0: port 0xbce0-0xbcff irq 16 at device > 29.0 on pci0 > uhci0: [GIANT-LOCKED] > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > uhci1: port 0xbcc0-0xbcdf irq 19 at device > 29.1 on pci0 > uhci1: [GIANT-LOCKED] > usb1: on uhci1 > usb1: USB revision 1.0 > uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub1: 2 ports with 2 removable, self powered > pci0: at device 29.4 (no driver attached) > pci0: at device 29.7 (no driver attached) > pcib3: at device 30.0 on pci0 > pci3: on pcib3 > em3: port > 0xccc0-0xccff mem 0xfdee0000-0xfdefffff irq 21 at device 2.0 on pci3 > em3: Ethernet address: 00:11:43:cd:36:d9 > pci3: at device 14.0 (no driver attached) > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfea0-0xfeaf at device 31.2 on pci0 > ata0: on atapci0 > ata1: on atapci0 > pci0: at device 31.3 (no driver attached) > atkbdc0: port 0x60,0x64 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on > acpi0 > sio0: type 16550A > orm0: at iomem > 0xc0000-0xc7fff,0xc8000-0xc8fff,0xc9000-0xc9fff,0xec000-0xeffff on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio1: port may not be enabled > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > Timecounters tick every 1.000 msec > ipfw2 initialized, divert loadable, rule-based forwarding enabled, default > to accept, logging disabled > acd0: CDROM at ata0-master UDMA33 > ad2: 38146MB at ata1-master SATA150 > SMP: AP CPU #1 Launched! > Trying to mount root from ufs:/dev/ad2s1a > bridge0: Ethernet address: aa:29:32:48:bd:5a > wan: link state changed to UP > con0: link state changed to UP > > > -- > Michael Scheidell, CTO > Phone: 561-999-5000, x 1259 > > *| *SECNAP Network Security Corporation > > * Certified SNORT Integrator > * Everything Channel Hot Product of 2008 > * Shaping Information Security Award 2008 > * CRN Magazine Top 40 Emerging Security Vendors > > _________________________________________________________________________ > This email has been scanned and certified safe by SpammerTrap(r). > For Information please see http://www.spammertrap.com > _________________________________________________________________________ > > !DSPAM:48e66ac8893435209328925! > > From koitsu at FreeBSD.org Sat Oct 4 06:45:17 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Sat Oct 4 06:45:24 2008 Subject: Intel 6300ESB SATA150 cannot find disk or boot under 6.3 In-Reply-To: <48E66ACE.7060702@secnap.net> References: <48E66ACE.7060702@secnap.net> Message-ID: <20081004064515.GA48654@icarus.home.lan> On Fri, Oct 03, 2008 at 02:56:14PM -0400, Michael Scheidell wrote: > Amazingly, this has been going on after a switch from 6.2 (which worked) > to 6.3. > lots of people have reported it, and we accidentally fixed it (but we > can't find documentation on what we fixed). > > it also doesn't work on 7.0 either. > here is a dmsg for a 6.3 one that accidentally works. > (i have a kernel that works), tech playing around with it months ago > can't remember if he used 6.2 drivers or found an obscure patch. > > Now that 5.5 is EOL, and we can't get ports for 5.5, it might be > important for freebsd folks (in their spare time after 7.1 and 6.4 beta) > to fix this. > > or, at least to fix it in 6.4. > > Yes, DELL 750, worked fine in 5.5 (lots of 5.5 systems I can't upgrade). > suggestions that we replace the (faulty?) hard disk controller cause lots > of problems. > Its a different tech (more expensive) in the field that has to replace > hardware, vs the one who can plug in a 6.3 CD rom and passively watch an > automated upgrade. A few questions: 1) What does "accidentally works" mean? 2) Do I understand you correctly: 6300ESB works on FreeBSD 5.5 and 6.2, "accidentally works" on 6.3, but does not work on 7.0? 3) Have you tried 7.1-PRERELEASE? I make no promises, but additional confirmation would be helpful. ftp://ftp4.freebsd.org/pub/FreeBSD/snapshots/200809/ 4) Have you contacted the ata(4) author, Soren Schmidt about this driver regression? 5) Is there a PR open on this matter, or have you filed one? -- | 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 pyunyh at gmail.com Sat Oct 4 06:51:01 2008 From: pyunyh at gmail.com (Pyun YongHyeon) Date: Sat Oct 4 06:51:08 2008 Subject: LG combo drive and Attansic Technology ethernet card on Asus P5Q Pro In-Reply-To: <20081003105828.GA27057@icarus.home.lan> References: <92056ebc0810020932w680c593er585dd865ef8af538@mail.gmail.com> <20081002231848.GA13467@icarus.home.lan> <20081003082257.GC71518@cdnetworks.co.kr> <20081003105828.GA27057@icarus.home.lan> Message-ID: <20081004064858.GE76137@cdnetworks.co.kr> On Fri, Oct 03, 2008 at 03:58:28AM -0700, Jeremy Chadwick wrote: > On Fri, Oct 03, 2008 at 05:22:57PM +0900, Pyun YongHyeon wrote: > > On Thu, Oct 02, 2008 at 04:18:48PM -0700, Jeremy Chadwick wrote: > > > On Thu, Oct 02, 2008 at 06:32:20PM +0200, Giuseppe Pagnoni wrote: > > > > [...] > > > > > > > > > On an unrelated topic, does anybody know whether the network card > > > > Attansic Technology on Asus P5Q Pro motherboard is compatible with > > > > FreeBSD? > > > > > > Asus was somewhat vague as to what model of Attansic/Atheros IC they > > > used on the P5Q series. I have one of these boards, so I can assure > > > you it's an Attansic L1E. It's sometimes referred to as an Atheros > > > AR8121, AR8113, or AR8114. > > > > > > FreeBSD 7.1-PRERELEASE has support for this NIC; age(4) is the driver. > > > 7.0 will very likely not support this NIC. > > > > > > > If the controller is AR8121/AR8113 PCI-E adapters(also known as > > L1E) there is no working driver for FreeBSD. Because the controller > > is quite different from its predecessor L1, new driver should be > > written for the controller. > > It's not feasible for me to write the driver until I can actually > > access the hardware. :-( > > Wow, I was under the impression the L1 and the L1E were identical, > except that the L1E was PCI Express-based vs. PCI-based. > > The Attansic L1E stuff is becoming more and more common here on > motherboards in the States. > Correct. Newer Eee PC also seems to have the controller. > Yong-Hyeon, I can get you a P5Q SE motherboard and send it your way > (with CPU + memory as well, if need be), if you'd like. > Yeah, that would make me write a driver for L1E and I'm willing to do that. I greatly appreciate your support. -- Regards, Pyun YongHyeon From freebsd at sopwith.solgatos.com Sat Oct 4 06:52:10 2008 From: freebsd at sopwith.solgatos.com (Dieter) Date: Sat Oct 4 06:52:17 2008 Subject: LG combo drive and Attansic Technology ethernet card on Asus P5Q Pro In-Reply-To: Your message of "Fri, 03 Oct 2008 20:45:24 PDT." <20081004034524.GA44662@icarus.home.lan> Message-ID: <200810040649.GAA19778@sopwith.solgatos.com> >> The drive is a new LG combo drive, I believe GH22LP20 or something close to it. I have an older LG PATA combo drive which works ok. Does it show up when booting? (Does dmesg work from the installation shell?) Maybe you need to "kldload atapicam" ? Or is that only needed for writing, I forget... > The only thing I can think of is that the P5Q boards use a Marvell > ATA/IDE controller (yes, you read that correctly). I wonder if FreeBSD > somehow lacks support for this... 7.0 ata man page claims support for: Marvell 88SX5040, 88SX5041, 88SX5080, 88SX5081, 88SX6041, 88SX6081, 88SX6101, 88SX6141. > I also tried to install Ubuntu and it works fine (but I really would > like to have FreeBSD!). Have you tried NetBSD or OpenBSD? > > thank you very much for your help. I downloaded the 7.1 prerelease, > > but unfortunately didn't solve the problem with the CD/DVD. As for > > the ethernet card, it's a kind of catch 22: to see if the card is > > working I should install the OS, but I cannot from the DVD. Who says you *have* to install from a DVD? You might be able to install from NetBSD or OpenBSD, or maybe even penguinix. Or connect the disk to some other FreeBSD box. Installing Unix is basically fdisk and/or disklabel, newfs, mount, tar, edit config files, reboot. Sometimes you need to get creative. # mount partition(s) for FreeBSD on /mnt # mount iso on /mnt2 export DESTDIR=/mnt cd /mnt2/7.0-RELEASE for foo in base doc catpages dict games info manpages proflibs ports lib32 do cd ${foo} ./install.sh cd .. done > Understood. This situation is very frustrating; people often run into > on Windows as well ("How do I get the Ethernet driver for my NIC from > the web site if Windows doesn't already have support for my NIC?!"). Plug in a working Ethernet card. Use RS-232 and ppp. CD/DVD attach disk to a working machine etc. etc. > > I cannot even install over FTP, because the institution I am in wants > > my MAC address to allow this pc to connect to internet and I cannot > > get to the MAC address without installing an OS (at least, I don't > > know how... I tried an Ubuntu LiveCD, but it doesn't recognize the > > ethernet card, either). Sometimes the MAC address is printed on a sticker. Copy files to a local machine, ftp from that machine? Copy ISOs to a spare partition somehow. Then mount the ISOs using mdconfig kludge. From koitsu at FreeBSD.org Sat Oct 4 07:33:07 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Sat Oct 4 07:33:59 2008 Subject: LG combo drive and Attansic Technology ethernet card on Asus P5Q Pro In-Reply-To: <200810040649.GAA19778@sopwith.solgatos.com> References: <20081004034524.GA44662@icarus.home.lan> <200810040649.GAA19778@sopwith.solgatos.com> Message-ID: <20081004073304.GA48931@icarus.home.lan> On Fri, Oct 03, 2008 at 11:49:01PM +0100, Dieter wrote: > >> The drive is a new LG combo drive, I believe GH22LP20 or something close to it. > > I have an older LG PATA combo drive which works ok. > > Does it show up when booting? (Does dmesg work from the installation shell?) > > Maybe you need to "kldload atapicam" ? Or is that only needed for writing, > I forget... > > > The only thing I can think of is that the P5Q boards use a Marvell > > ATA/IDE controller (yes, you read that correctly). I wonder if FreeBSD > > somehow lacks support for this... > > 7.0 ata man page claims support for: > > Marvell 88SX5040, 88SX5041, 88SX5080, 88SX5081, 88SX6041, > 88SX6081, 88SX6101, 88SX6141. None of these are what's on the P5Q series boards. The P5Q series boards use a Marvell 88SE6102 Super I/O chip, which also drives IDE/PATA devices. (SATA is driven via ICH10 or ICH10R). I'm left to believe FreeBSD simply lacks support for this very new Marvell chip. I'm willing to bet there is no sign of ata(4) devices nor atapci(4) PCI association during boot-up. > > > I cannot even install over FTP, because the institution I am in wants > > > my MAC address to allow this pc to connect to internet and I cannot > > > get to the MAC address without installing an OS (at least, I don't > > > know how... I tried an Ubuntu LiveCD, but it doesn't recognize the > > > ethernet card, either). > > Sometimes the MAC address is printed on a sticker. This is an on-board NIC/PHY. I'm fairly sure there's no printed label of the MAC on the motherboard, although if there was, I'd say it's probably on the underside/back of the board. http://www.unitycorp.co.jp/asus/motherboard/intel/lga775/p5q_pro/big_photo.jpg I'm going to get Yong-Hyeon a P5Q SE motherboard with CPU and RAM, and ship it to him in South Korea. Once it arrives, he should be able to work on developing a driver for it over the next few months. -- | 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 Sat Oct 4 07:34:13 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Sat Oct 4 07:34:57 2008 Subject: LG combo drive and Attansic Technology ethernet card on Asus P5Q Pro In-Reply-To: <20081004064858.GE76137@cdnetworks.co.kr> References: <92056ebc0810020932w680c593er585dd865ef8af538@mail.gmail.com> <20081002231848.GA13467@icarus.home.lan> <20081003082257.GC71518@cdnetworks.co.kr> <20081003105828.GA27057@icarus.home.lan> <20081004064858.GE76137@cdnetworks.co.kr> Message-ID: <20081004073411.GA49725@icarus.home.lan> On Sat, Oct 04, 2008 at 03:48:58PM +0900, Pyun YongHyeon wrote: > On Fri, Oct 03, 2008 at 03:58:28AM -0700, Jeremy Chadwick wrote: > > On Fri, Oct 03, 2008 at 05:22:57PM +0900, Pyun YongHyeon wrote: > > > On Thu, Oct 02, 2008 at 04:18:48PM -0700, Jeremy Chadwick wrote: > > > > On Thu, Oct 02, 2008 at 06:32:20PM +0200, Giuseppe Pagnoni wrote: > > > > > > [...] > > > > > > > > > > > > On an unrelated topic, does anybody know whether the network card > > > > > Attansic Technology on Asus P5Q Pro motherboard is compatible with > > > > > FreeBSD? > > > > > > > > Asus was somewhat vague as to what model of Attansic/Atheros IC they > > > > used on the P5Q series. I have one of these boards, so I can assure > > > > you it's an Attansic L1E. It's sometimes referred to as an Atheros > > > > AR8121, AR8113, or AR8114. > > > > > > > > FreeBSD 7.1-PRERELEASE has support for this NIC; age(4) is the driver. > > > > 7.0 will very likely not support this NIC. > > > > > > > > > > If the controller is AR8121/AR8113 PCI-E adapters(also known as > > > L1E) there is no working driver for FreeBSD. Because the controller > > > is quite different from its predecessor L1, new driver should be > > > written for the controller. > > > It's not feasible for me to write the driver until I can actually > > > access the hardware. :-( > > > > Wow, I was under the impression the L1 and the L1E were identical, > > except that the L1E was PCI Express-based vs. PCI-based. > > > > The Attansic L1E stuff is becoming more and more common here on > > motherboards in the States. > > > > Correct. Newer Eee PC also seems to have the controller. > > > Yong-Hyeon, I can get you a P5Q SE motherboard and send it your way > > (with CPU + memory as well, if need be), if you'd like. > > > > Yeah, that would make me write a driver for L1E and I'm willing to > do that. I greatly appreciate your support. Yong-Hyeon, Please (privately) provide me your address in South Korea and I'll get all of this stuff shipped off to you within the next few weeks. You can keep the hardware, resell it, or ship it back (if you so desire) when finished with it. :-) Thanks! -- | 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 Sat Oct 4 07:39:33 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Sat Oct 4 07:39:39 2008 Subject: LG combo drive and Attansic Technology ethernet card on Asus P5Q Pro In-Reply-To: <20081004073304.GA48931@icarus.home.lan> References: <20081004034524.GA44662@icarus.home.lan> <200810040649.GAA19778@sopwith.solgatos.com> <20081004073304.GA48931@icarus.home.lan> Message-ID: <20081004073930.GA49756@icarus.home.lan> On Sat, Oct 04, 2008 at 12:33:04AM -0700, Jeremy Chadwick wrote: > On Fri, Oct 03, 2008 at 11:49:01PM +0100, Dieter wrote: > > >> The drive is a new LG combo drive, I believe GH22LP20 or something close to it. > > > > I have an older LG PATA combo drive which works ok. > > > > Does it show up when booting? (Does dmesg work from the installation shell?) > > > > Maybe you need to "kldload atapicam" ? Or is that only needed for writing, > > I forget... > > > > > The only thing I can think of is that the P5Q boards use a Marvell > > > ATA/IDE controller (yes, you read that correctly). I wonder if FreeBSD > > > somehow lacks support for this... > > > > 7.0 ata man page claims support for: > > > > Marvell 88SX5040, 88SX5041, 88SX5080, 88SX5081, 88SX6041, > > 88SX6081, 88SX6101, 88SX6141. > > None of these are what's on the P5Q series boards. The P5Q series > boards use a Marvell 88SE6102 Super I/O chip, which also drives IDE/PATA > devices. (SATA is driven via ICH10 or ICH10R). > > I'm left to believe FreeBSD simply lacks support for this very new > Marvell chip. I'm willing to bet there is no sign of ata(4) devices nor > atapci(4) PCI association during boot-up. Mac folks are seeing the same problem: http://forum.insanelymac.com/index.php?showtopic=128985 http://www.insanelymac.com/lofiversion/index.php/t99634.html Wikipedia states the 88SE6121, not the 88SE6102, is used on P5Q series boards. But the P5Q SE motherboard manual states it's a 88SE6102. http://en.wikipedia.org/wiki/List_of_Marvell_Technology_Group_chipsets So either the motherboard manual is wrong, Wikipedia is wrong, or the P5Q SE and P5Q Pro contain different models/versions of ICs. When I get a P5Q SE for Yong-Hyeon, I'll make note of what's silkscreened on the ASIC. -- | 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 scheidell at secnap.net Sat Oct 4 10:42:49 2008 From: scheidell at secnap.net (Michael Scheidell) Date: Sat Oct 4 10:42:55 2008 Subject: Intel 6300ESB SATA150 cannot find disk or boot under 6.3 In-Reply-To: <20081004064515.GA48654@icarus.home.lan> References: <48E66ACE.7060702@secnap.net> <20081004064515.GA48654@icarus.home.lan> Message-ID: <48E748B3.7000108@secnap.net> > A few questions: > > 1) What does "accidentally works" mean? > one of our techs found a patch for 6.3 that worked. > 2) Do I understand you correctly: 6300ESB works on FreeBSD 5.5 and 6.2, > "accidentally works" on 6.3, but does not work on 7.0? > > I have a compiled kernel that works, but we lost the patch. normal 6.3 doesn't. generic 6.3 doesn't. i 6.3 current didn't work. I can send you a dell 750 with 6.3 on it that does work (custom 6.3 kernel, again, lost the source, can't repeduce 'fix' no matter what I tried) even upgraded dell 750 to latest firmware. other anomaly: teying to man times to boot 6.3 hosed a hard disk. fried the hardware (hard disk) somehow. > 3) Have you tried 7.1-PRERELEASE? I make no promises, but additional > confirmation would be helpful. > > not yet. since I didn't see any CLOSED pr talking about fixing it, and all the hardware notes on 6.2, 6.3, 6.4, 7.0 and 7.1 say just it does generic support for SATA150. > ftp://ftp4.freebsd.org/pub/FreeBSD/snapshots/200809/ > > 4) Have you contacted the ata(4) author, Soren Schmidt > about this driver regression? > > 5) Is there a PR open on this matter, or have you filed one? > > after replying to freebsd-hardware post, I found this, but have found other posts going back to feb 2008. http://www.freebsd.org/cgi/query-pr.cgi?pr=127391 -- Michael Scheidell, CTO Phone: 561-999-5000, x 1259 > *| *SECNAP Network Security Corporation * Certified SNORT Integrator * Everything Channel Hot Product of 2008 * Shaping Information Security Award 2008 * CRN Magazine Top 40 Emerging Security Vendors _________________________________________________________________________ This email has been scanned and certified safe by SpammerTrap(r). For Information please see http://www.spammertrap.com _________________________________________________________________________ From satz at iranger.com Sat Oct 4 14:29:47 2008 From: satz at iranger.com (satz@iranger.com) Date: Sat Oct 4 14:29:53 2008 Subject: Intel 6300ESB SATA150 cannot find disk or boot under 6.3 In-Reply-To: <20081004064515.GA48654@icarus.home.lan> References: <48E66ACE.7060702@secnap.net> <20081004064515.GA48654@icarus.home.lan> Message-ID: <53691.66.117.128.236.1223130585.squirrel@fnu.iranger.com> > A few questions: > > 1) What does "accidentally works" mean? > > 2) Do I understand you correctly: 6300ESB works on FreeBSD 5.5 and 6.2, > "accidentally works" on 6.3, but does not work on 7.0? >From my perspective it is currently working right now for me under 6.1 but I cannot get it to work under 6.3 per the pr. > 3) Have you tried 7.1-PRERELEASE? I make no promises, but additional > confirmation would be helpful. > > ftp://ftp4.freebsd.org/pub/FreeBSD/snapshots/200809/ I will try this and add the results to the pr. > 4) Have you contacted the ata(4) author, Soren Schmidt > about this driver regression? I just added Soren to this thread. Thanks for the reference. > 5) Is there a PR open on this matter, or have you filed one? I opened http://www.freebsd.org/cgi/query-pr.cgi?pr=127391 a few weeks ago and after it was reclassified it has just sat there. Thanks, Greg From freebsd at sopwith.solgatos.com Sat Oct 4 21:30:56 2008 From: freebsd at sopwith.solgatos.com (Dieter) Date: Sat Oct 4 21:31:07 2008 Subject: alpha/127248: System crashes when many (7) serial port terminals (vt320-vt510) connected to the server via com to usb adapter and 2-usb hubs. In-Reply-To: Your message of "Thu, 25 Sep 2008 21:00:22 +0200." <20080925190022.GB93308@cicely7.cicely.de> Message-ID: <200810042129.VAA24823@sopwith.solgatos.com> > > Surely a "good" USB to RS-232 bridge (if one exists?) or a RS-232 > > filter/isolator (assuming they exist?) would be *far* less expensive > > than the server class alpha you suggest below. > > It depend on how much RS232 you need and how many slots the OP has free. > Nevertheless a "good" RS232 bridge if needed in number are not cheap > either - ntoe that you can get affordable PCI extenders as well. The PCI expanders I've seen cost almost as much as getting an entire additional machine. > > > > The problem with PCI is the limited number of slots. :-( > > > > > > Well - not realy with server class alphas... > > > > In my world, a "server" means 1-4 full height 19" racks with quite large > > price tags and power&cooling requirements. Some people think a server > > is a pee-cee. So I'm not sure what you mean by "server class alphas". > > Server doesn't mean rack, but beside from a few OEM boards and small > 19" system all alphas have lots of free slots available. > > > I have what I would call a "workstation" class alpha, which cost an > > obscene amount to get 6 PCI slots instead of 4, and at times they are > > all full. So I can't use up a slot just to get a couple more RS-232 > > ports. How many PCI slots does a server class alpha have? > > Well the AS4100 I have already has 8 slots which is not that uncommon > for alpha servers. I'd call an alpha with only 8 slots a workstation class machine. It wouldn't take much to fill up 8 slots. > The real big ones can even have a few hundred slots. A few hundred slots would be server class. And I'm sure a price tag to match, along with floor space, power, and cooling requirements. > > USB to RS-232 bridge could be a good solution, if I knew which > > make&model of bridge worked well with *BSD. Poking around on the web > > I can't even find what chip they have inside. > > Really forget about USB to RS232. > It is not the chip which is the problem it is the principal. > You really need galvanic isolation, because USB can't handle ground > loops, which no cheap device has. > You can use any kind of chip with propper isolation, but then it > is likely more expensive than any other kind of solution. I assume this is marketing driven. Adding a few optos can't increase the manufacturing cost *that* much. Sounds like a market opportunity for someone. > > Do these bridges actually work properly, or do they have gotchas > > like the USB to SATA/PATA bridges? > > The prolific bridges work well enough if you don't have a ground > loop and FTDI chips are better IMHO. Thanks. From ticso at cicely7.cicely.de Sun Oct 5 10:36:07 2008 From: ticso at cicely7.cicely.de (Bernd Walter) Date: Sun Oct 5 10:36:25 2008 Subject: alpha/127248: System crashes when many (7) serial port terminals (vt320-vt510) connected to the server via com to usb adapter and 2-usb hubs. In-Reply-To: <200810042129.VAA24823@sopwith.solgatos.com> References: <20080925190022.GB93308@cicely7.cicely.de> <200810042129.VAA24823@sopwith.solgatos.com> Message-ID: <20081005103559.GI3228@cicely7.cicely.de> On Sat, Oct 04, 2008 at 02:29:08PM +0100, Dieter wrote: > > > Surely a "good" USB to RS-232 bridge (if one exists?) or a RS-232 > > > filter/isolator (assuming they exist?) would be *far* less expensive > > > than the server class alpha you suggest below. > > > > It depend on how much RS232 you need and how many slots the OP has free. > > Nevertheless a "good" RS232 bridge if needed in number are not cheap > > either - ntoe that you can get affordable PCI extenders as well. > > The PCI expanders I've seen cost almost as much as getting an entire > additional machine. For PCI you are right, but Exsys for example makes extenders with PCIe uplinks for a good price. > > Well the AS4100 I have already has 8 slots which is not that uncommon > > for alpha servers. > > I'd call an alpha with only 8 slots a workstation class machine. It > wouldn't take much to fill up 8 slots. It is not the biggest server class, but I wouldn't put it on my desk either. > > > USB to RS-232 bridge could be a good solution, if I knew which > > > make&model of bridge worked well with *BSD. Poking around on the web > > > I can't even find what chip they have inside. > > > > Really forget about USB to RS232. > > It is not the chip which is the problem it is the principal. > > You really need galvanic isolation, because USB can't handle ground > > loops, which no cheap device has. > > You can use any kind of chip with propper isolation, but then it > > is likely more expensive than any other kind of solution. > > I assume this is marketing driven. Adding a few optos can't > increase the manufacturing cost *that* much. Sounds like a > market opportunity for someone. You also need a DC-DC converter to get power behind the isolation and 8 opto channels. It wouldn't increase manufactoring costs that much if produced in numbers, but it would make these devices about two or three times bigger. Another point is the additional power requirement. There are alternatives for optos, that don't consume that much power, but they are more expensive and you still have the loss for the DC-DC. Power consumption is an important factor for mobile computing. So yes - this is marketing driven, but not only for prices. I produce 12V adapters myself, so I know the size requirements for adding DCDC converters. Guess I will add optos one day. But even those without are already too expensive for adding terminals compared to e.g. ethernet based RS232. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From nick at van-laarhoven.org Tue Oct 7 21:45:25 2008 From: nick at van-laarhoven.org (Nick Hibma) Date: Tue Oct 7 21:45:32 2008 Subject: Modem GPRS USB In-Reply-To: <1e31c7980805160832j7aac492v77469255f483490f@mail.gmail.com> References: <1e31c7980805130830w15aa90a0jfe19a279a4e6a628@mail.gmail.com> <482ABC29.9030002@FreeBSD.org> <1e31c7980805160832j7aac492v77469255f483490f@mail.gmail.com> Message-ID: <200810072333.18566.nick@van-laarhoven.org> > May 16 12:17:08 vinnix ppp[1262]: tun0: Warning: 0.0.0.0: Change route > failed: errno: No such process > May 16 12:17:08 vinnix ppp[1262]: tun0: Warning: ff02:5::: Change route > failed: errno: Network is unreachable > > The PPP fails to get a default route, after connect. > Can you help-me with this? You might not get a valid route from the PPP server or you need to add the following to /etc/ppp/ppp.linkup shell route delete default shell route add default -interface INTERFACE to use the interface instead of the destination IP address. You can try this manually after PPP has established a connection. Nick From nick at van-laarhoven.org Tue Oct 7 22:03:43 2008 From: nick at van-laarhoven.org (Nick Hibma) Date: Tue Oct 7 22:03:49 2008 Subject: Modem GPRS USB - testers needed for 3G USB based data cards. In-Reply-To: <1e31c7980805130830w15aa90a0jfe19a279a4e6a628@mail.gmail.com> References: <1e31c7980805130830w15aa90a0jfe19a279a4e6a628@mail.gmail.com> Message-ID: <200810080003.38358.nick@van-laarhoven.org> Would you mind trying the driver below, after patching in the appropriate IDs and removing ubsa from the kernel/unloading it? http://people.freebsd.org/~n_hibma/ It's a driver that currently supports Option and Huawei USB based PCMCIA cards. It supports multiple serial ports on the devices, which is neat if you want to find out signal strength while PPP is connected. It also includes the reset needed for the Huawei to change it from a umass to a ucom device. Other people currently using the ubsa driver for 3G cards, like Novatal, Sierra and Qualcomm, might want to try this driver out as well. Once this driver hits the tree (once I have rebuilt my CURRENT machine), devices from ubsa will be transferred across. These devices have a) high data transfer rates, b) usually have multiple serial ports listed in USB interfaces, c) need extra initialisation to change appearance and d) do not support nor need the setting of serial port settings as the serial port is simply used for transferring serial data, not driving an actual serial port. So they should have their own driver. Cheers, Nick > Hi People, > > First, sorry about my poor english. > I have modem usb: hsdpa/edge/gprs, but I don't know how to > make this work. This is the description about the device: > > umass0: 1.10/0.00, addr 2> on uhub2 > cd0 at umass-sim0 bus 0 target 0 lun 0 > cd0: Removable CD-ROM SCSI-2 device > cd0: 1.000MB/s transfers > cd0: cd present [4623 x 2048 byte records] > GEOM_LABEL: Label for provider cd0 is iso9660/ONDAMODEM > > At my kernel configuration file we find: > device ugen # Generic > device ucom # Modem UCOM > device ugencom # Modem CDMA MSM > device umodem # Modem COM > > Thanks in advice for any light. > > Best regards, > Vinnix > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to > "freebsd-hardware-unsubscribe@freebsd.org" From freebsd-hardware at dino.sk Wed Oct 8 07:46:37 2008 From: freebsd-hardware at dino.sk (Milan Obuch) Date: Wed Oct 8 07:46:43 2008 Subject: Modem GPRS USB - testers needed for 3G USB based data cards. In-Reply-To: <200810080003.38358.nick@van-laarhoven.org> References: <1e31c7980805130830w15aa90a0jfe19a279a4e6a628@mail.gmail.com> <200810080003.38358.nick@van-laarhoven.org> Message-ID: <200810080934.58273.freebsd-hardware@dino.sk> On Wednesday 08 October 2008 00:03:37 Nick Hibma wrote: > Would you mind trying the driver below, after patching in the appropriate > IDs and removing ubsa from the kernel/unloading it? > > http://people.freebsd.org/~n_hibma/ > > It's a driver that currently supports Option and Huawei USB based PCMCIA > cards. It supports multiple serial ports on the devices, which is neat if > you want to find out signal strength while PPP is connected. It also > includes the reset needed for the Huawei to change it from a umass to a > ucom device. > I tried building under both 7.1-PRERELASE from Sep 19 and 8.0-CURRENT (two days old or so). It builds under the former, but does not build under the latter, complaining about missing TS_CALLOUT. That beeing said, under 7.1 it kldloads/kldunloads, and as soon as I have an access to Huawei E220 (temporary), I will test whether it works. Is there anything special necessary to use this driver? Or is it just like using normal modem with ppp? I would like to know because my access to this device is currently limited only for some occasions. Regards, Milan From nick at van-laarhoven.org Wed Oct 8 07:47:55 2008 From: nick at van-laarhoven.org (Nick Hibma) Date: Wed Oct 8 07:48:02 2008 Subject: Modem GPRS USB - testers needed for 3G USB based data cards. In-Reply-To: <200810080934.58273.freebsd-hardware@dino.sk> References: <1e31c7980805130830w15aa90a0jfe19a279a4e6a628@mail.gmail.com> <200810080003.38358.nick@van-laarhoven.org> <200810080934.58273.freebsd-hardware@dino.sk> Message-ID: <200810080947.40594.nick@van-laarhoven.org> > I tried building under both 7.1-PRERELASE from Sep 19 and 8.0-CURRENT > (two days old or so). It builds under the former, but does not build > under the latter, complaining about missing TS_CALLOUT. Thanks. I will check into that this week. > That beeing said, under 7.1 it kldloads/kldunloads, and as soon as I have > an access to Huawei E220 (temporary), I will test whether it works. Is > there anything special necessary to use this driver? Or is it just like > using normal modem with ppp? I would like to know because my access to > this device is currently limited only for some occasions. Nope. You will get multiple /dev/cuaUX devices (4 in this case I believe) and you need to pick /dev/cuaU0. Start ppp with your usual entry and before typing dial you set the device to set device /dev/cuaU0 Don't forget to set the baud rate to 115200 or higher to set buffering correctly in the TTY layer. Oh no, that still needs fixing in the ucom driver. You will get lots of warnings. Increase 256 to 1024 in the following line: #define U3GBUFSZ 256 The problem here is that ucom doesn't properly initialise the tty struct. Setting this value isn't the proper way of doing this but it works. With screen /dev/cuaU2 and then typing in AT+CSQ you can view signal strength. Depending on the device the following commands you can try (while on the move): AT+CREG=1 GSM connection status AT+CGREG=1 GPRS connection status AT+CREG=2 GSM connection status including mast IDs AT+CGREG=2 GPRS connection status including mast IDs AT_OSSYS=1 Async selected system reporting (Option) AT_OSQI=1 Async Signal Quality Reporting (Option) Thanks for testing. Cheers, Nick From nick at van-laarhoven.org Wed Oct 8 09:46:22 2008 From: nick at van-laarhoven.org (Nick Hibma) Date: Wed Oct 8 09:46:28 2008 Subject: Problem / question about u3g driver In-Reply-To: <48EC7785.8030303@catpipe.net> References: <48EC7785.8030303@catpipe.net> Message-ID: <200810081146.13435.nick@van-laarhoven.org> I'll look into your question on the config descriptor index. I'm not sure which device we have to test, but I will get back to you for testing. Wrt to current: I have not yet done any porting of the driver there so I don't know why you have problems. I will do so hopefully this week so I can commit the driver and MFC shortly afterwards. Be patient. My time for FBSD work is limited. None of this is rocket science, so it will get there in time. For now you have your patched ubsa driver in any case. Thanks for the testing! Nick > Hi, > > PHK pointed me to the u3g driver on your site. I did a quick test on > -current which wasn't that successful. > > To make a bit of context I made a patch for ubsa.c which allows my > Huawei E220 usb device to work (it's based on phk's latest commit to > -current) > > This part works great - but what I found out during my investigation was > that according to atleast netbsd it's an error to use 1 as config_index. > It should be 0. > This removes my configure "STALLED" messages and makes the device attach > proberly (after the reprobe). So my questions is if you know > what is the correct index - I can see that the u3g driver uses 1 as > config index but what i fear is that this is actually > different for different devices. > > I hope you can shed some light on this. > > Back to my testing of the u3g driver on current with the E220 adapter I > get instant crash when attach fails - I'll do a backtrace later but my > best bet is that it's the config index that needs to be changed. > > I'll look forward to hearing from you. > > Cheers, > Nicolai Petri > > Ps. I have made a patch for freebsd-stable which makes huawei devices > work - only thing I'm puzzled about is the change of config index from 1 > to 0. It can be found here : > http://hobbes.bsd-dk.dk/~npp/ubsa.patch-stable From soala at gmx.de Wed Oct 8 16:17:47 2008 From: soala at gmx.de (soala@gmx.de) Date: Wed Oct 8 16:49:39 2008 Subject: Chipset Driver Message-ID: <20081008155104.181990@gmx.net> Hello, I use FreeBSD 6.2 and have the chipset "Mobile Intel 945GM Express + ICH7". Do you have any chipset driver for me? I have problem with my SATA connectors - the SATA speed is so slow.... Please help me Thank you Best regards Andi -- Psssst! Schon vom neuen GMX MultiMessenger geh?rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger From koitsu at FreeBSD.org Wed Oct 8 18:39:09 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Wed Oct 8 18:40:20 2008 Subject: Chipset Driver In-Reply-To: <20081008155104.181990@gmx.net> References: <20081008155104.181990@gmx.net> Message-ID: <20081008183908.GA83512@icarus.home.lan> On Wed, Oct 08, 2008 at 05:51:04PM +0200, soala@gmx.de wrote: > Hello, > > I use FreeBSD 6.2 and have the chipset "Mobile Intel 945GM Express + ICH7". > Do you have any chipset driver for me? > I have problem with my SATA connectors - the SATA speed is so slow.... > Please help me Does the problem go away if you run 7.0 or 7.1-PRERELEASE? BTW, the ICH7 is the piece which controls SATA, not the 945GM. -- | 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 kungfujesus06 at gmail.com Thu Oct 9 03:21:34 2008 From: kungfujesus06 at gmail.com (Adam Stylinski) Date: Thu Oct 9 03:21:41 2008 Subject: Generic Marvell 88SX7042 Cards Message-ID: <96af083b0810081957x6dc89c5dy65c8d2b8bee3b2e1@mail.gmail.com> Hello, I've been scouring through the Hardware Support list to find that nothing under this chipset seems to be supported. Linux recently supports this with the sata_mv module and I was wondering if there was any effort to port a driver to BSD. I have a Rosewill RC-218 card, which is a non-raid SATA-II Controller with 4 ports. I would like to expand my zraid with this card. Any more information to the progress of this would be extremely appreciated. Thanks. From jgrosch at MooseRiver.com Thu Oct 9 20:44:44 2008 From: jgrosch at MooseRiver.com (Josef Grosch) Date: Thu Oct 9 20:44:56 2008 Subject: FreeBSD support for HP DL180/G5 Message-ID: <20081009202521.GA57222@mooseriver.com> Does anyone have experience running FreeBSD 6.x and 7.x on an HP DL180/G5? The company I work for is looking to get a number of these to be put in production. Your general impressions would be a good start. Josef -- Josef Grosch | Another day closer to a | FreeBSD 6.3 jgrosch@MooseRiver.com | Micro$oft free world | Berkeley, Ca. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 155 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-hardware/attachments/20081009/f3e96321/attachment.pgp From subhro.kar at gmail.com Thu Oct 9 21:53:04 2008 From: subhro.kar at gmail.com (Subhro) Date: Thu Oct 9 21:53:11 2008 Subject: FreeBSD support for HP DL180/G5 In-Reply-To: <20081009202521.GA57222@mooseriver.com> References: <20081009202521.GA57222@mooseriver.com> Message-ID: HP produces pretty good boxes and historically I have been able to get them working without any troubles. However I would say DL180 is a pretty non customizable box. The hardware works perfectly with FreeBSD 7.0. I didnt try it with 6.3, so cant comment on that. However I would say DL380 is a better off. The main advantage of DL3xx boxes are there is a lot of room to play with add-on cards. Also not all the latest and greatest processors are available with DL1xx family of servers. Also make sure that you go for an external RAID controller like 3ware or Areca. I prefer Areca more :-D. The HP RAID controller cant take the beating I give to it. Thanks Subhro On Fri, Oct 10, 2008 at 1:55 AM, Josef Grosch wrote: > > Does anyone have experience running FreeBSD 6.x and 7.x on an HP DL180/G5? > The company I work for is looking to get a number of these to be put in > production. Your general impressions would be a good start. > > > > Josef > > -- > Josef Grosch | Another day closer to a | FreeBSD 6.3 > jgrosch@MooseRiver.com | Micro$oft free world | Berkeley, Ca. > From nick at van-laarhoven.org Thu Oct 9 21:56:21 2008 From: nick at van-laarhoven.org (Nick Hibma) Date: Thu Oct 9 21:56:28 2008 Subject: Request for testers: Option 3G cards, also Sierra, Huawei and Novatel Message-ID: <200810092344.10388.nick@van-laarhoven.org> Just now I have committed a driver for Option and Huawei cards previously supported by the ubsa driver. More information is in the commit message. I am looking for people who would be able to provide more information after testing with the 3G cards branded by: OEM: Merlin Huawei Option Sierra Novatel Qualcomm Rebranded: Dell Vodafone Note: The driver can be copied across to FreeBSD 7-STABLE if you copy the sys/modules/u3g directory and sys/dev/usb/u3g.c and sys/dev/usb/usbdevs files from HEAD and _move_ the ID from ubsa to u3g. More information can be found on http://people.freebsd.org/~n_hibma/u3g.html Thanks, Nick ---------- Forwarded Message ---------- Subject: svn commit: r183735 - in head: share/man/man4 sys/conf sys/dev/usb sys/i386/conf sys/modules sys/modules/u3g Date: Thu October 9 2008 From: Nick Hibma To: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Author: n_hibma Date: Thu Oct 9 21:25:01 2008 New Revision: 183735 URL: http://svn.freebsd.org/changeset/base/183735 Log: Say hello to the u3g driver, implementing support for 3G modems. This was located in the ubsa driver, but should be moved into a separate driver: - 3G modems provide multiple serial ports to allow AT commands while the PPP connection is up. - 3G modems do not provide baud rate or other serial port settings. - Huawei cards need specific initialisation. - ubsa is for Belkin adapters, an Linuxy choice for another device like 3G. Speeds achieved here with a weak signal at best is ~40kb/s (UMTS). No spooky STALLED messages as well. Next: Move over all entries for Sierra and Novatel cards once I have found testers, and implemented serial port enumeration for Sierra (or rather have Andrea Guzzo do it). They list all endpoints in 1 iface instead of 4 ifaces. Submitted by: aguzzo@anywi.com MFC after: 3 weeks Added: head/share/man/man4/u3g.4 (contents, props changed) head/sys/dev/usb/u3g.c (contents, props changed) head/sys/modules/u3g/ head/sys/modules/u3g/Makefile (contents, props changed) Modified: head/share/man/man4/Makefile head/sys/conf/NOTES head/sys/conf/files head/sys/dev/usb/ubsa.c head/sys/dev/usb/usbdevs head/sys/i386/conf/GENERIC head/sys/modules/Makefile Modified: head/share/man/man4/Makefile ============================================================================== --- head/share/man/man4/Makefile Thu Oct 9 20:51:25 2008 (r183734) +++ head/share/man/man4/Makefile Thu Oct 9 21:25:01 2008 (r183735) @@ -384,6 +384,7 @@ MAN= aac.4 \ twe.4 \ tx.4 \ txp.4 \ + u3g.4 \ uark.4 \ uart.4 \ ubsa.4 \ Added: head/share/man/man4/u3g.4 ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/share/man/man4/u3g.4 Thu Oct 9 21:25:01 2008 (r183735) @@ -0,0 +1,100 @@ +.\" +.\" Copyright (c) 2008 AnyWi Technologies +.\" All rights reserved. +.\" +.\" This code is derived from uark.c +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.\" $FreeBSD$ +.\" +.Dd October 7, 2008 +.Dt U3G 4 +.Os +.Sh NAME +.Nm u3g +.Nd USB support for 3G datacards +.Sh SYNOPSIS +To compile this driver into the kernel, +place the following lines in your +kernel configuration file: +.Bd -ragged -offset indent +.Cd "device u3g" +.Cd "device ucom" +.Ed +.Pp +Alternatively, to load the driver as a +module at boot time, place the following line in +.Xr loader.conf 5 : +.Bd -literal -offset indent +u3g_load="YES" +.Ed +.Sh DESCRIPTION +The +.Nm +driver provides support for the multiple USB-to-serial interfaces exposed by +many 3G usb/pccard modems. +.Pp +The device is accessed through the +.Xr ucom 4 +driver which makes it behave like a +.Xr tty 4 . +.Sh HARDWARE +The +.Nm +driver supports the following adapters: +.Pp +.Bl -bullet -compact +.It +Option Globetrotter 3G Fusion (only 3G part, not WLAN) +.It +Option Globetrotter 3G Fusion Quad (only 3G part, not WLAN) +.It +Option Globetrotter 3G Quad +.It +Option Globetrotter 3G +.It +Vodafone Mobile Connect Card 3G +.It +Huawei E220 (E270?) +.It +Huawei Mobile +.El +.Pp +The supported 3G cards provide the necessary modem port for ppp, +pppd, or mpd connections as well as extra ports (depending on the specific +device) to provide other functions (diagnostic port, SIM toolkit port) +.Sh SEE ALSO +.Xr tty 4 , +.Xr ucom 4 , +.Xr usb 4 , +.Xr ubsa 4 +.Sh HISTORY +The +.Nm +driver +appeared in +.Fx 7.0 . +The +.Xr ubsa 4 +manual page was modified for +.Nm +by +.An Andrea Guzzo Aq aguzzo@anywi.com +in September 2008. +.Sh AUTHORS +The +.Nm +driver was written by +.An Andrea Guzzo Aq aguzzo@anywi.com . +Hardware for testing provided by AnyWi Technologies, Leiden, NL. Modified: head/sys/conf/NOTES ============================================================================== --- head/sys/conf/NOTES Thu Oct 9 20:51:25 2008 (r183734) +++ head/sys/conf/NOTES Thu Oct 9 21:25:01 2008 (r183735) @@ -2416,6 +2416,8 @@ device uscanner # # USB serial support device ucom +# USB support for 3G modem cards by Option, Huawei and Sierra +device u3g # USB support for Technologies ARK3116 based serial adapters device uark # USB support for Belkin F5U103 and compatible serial adapters @@ -2441,7 +2443,6 @@ device aue # ASIX Electronics AX88172 USB 2.0 ethernet driver. Used in the # LinkSys USB200M and various other adapters. - device axe # Modified: head/sys/conf/files ============================================================================== --- head/sys/conf/files Thu Oct 9 20:51:25 2008 (r183734) +++ head/sys/conf/files Thu Oct 9 21:25:01 2008 (r183735) @@ -1327,6 +1327,7 @@ dev/usb/ohci_pci.c optional ohci pci dev/usb/sl811hs.c optional slhci dev/usb/slhci_pccard.c optional slhci pccard dev/usb/uark.c optional uark +dev/usb/u3g.c optional u3g dev/usb/ubsa.c optional ubsa dev/usb/ubser.c optional ubser dev/usb/ucom.c optional ucom Added: head/sys/dev/usb/u3g.c ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/sys/dev/usb/u3g.c Thu Oct 9 21:25:01 2008 (r183735) @@ -0,0 +1,330 @@ +/* + * Copyright (c) 2008 AnyWi Technologies + * Author: Andrea Guzzo + * * based on uark.c 1.1 2006/08/14 08:30:22 jsg * + * * parts from ubsa.c 183348 2008-09-25 12:00:56Z phk * + * + * Permission to use, copy, modify, and distribute this software for any + * purpose with or without fee is hereby granted, provided that the above + * copyright notice and this permission notice appear in all copies. + * + * THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES + * WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF + * MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR + * ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES + * WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN + * ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF + * OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. + * + * $FreeBSD$ + */ + +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include + +#include +#include +#include + +#include + +#include "usbdevs.h" + +#ifdef U3G_DEBUG +#define DPRINTFN(n, x) do { if (u3gdebug > (n)) printf x; } while (0) +int u3gtebug = 0; +#else +#define DPRINTFN(n, x) +#endif +#define DPRINTF(x) DPRINTFN(0, x) + +#define U3GBUFSZ 1024 +#define U3G_MAXPORTS 4 + +struct u3g_softc { + struct ucom_softc sc_ucom[U3G_MAXPORTS];; + device_t sc_dev; + usbd_device_handle sc_udev; + u_char sc_msr; + u_char sc_lsr; + u_char numports; + + usbd_interface_handle sc_intr_iface; /* interrupt interface */ +#ifdef U3G_DEBUG + int sc_intr_number; /* interrupt number */ + usbd_pipe_handle sc_intr_pipe; /* interrupt pipe */ + u_char *sc_intr_buf; /* interrupt buffer */ +#endif + int sc_isize; +}; + +struct ucom_callback u3g_callback = { + NULL, + NULL, + NULL, + NULL, + NULL, + NULL, + NULL, + NULL, +}; + +static const struct usb_devno u3g_devs[] = { + /* OEM: Option */ + { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GT3G }, + { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GT3GQUAD }, + { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GT3GPLUS }, + { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GTMAX36 }, + { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_VODAFONEMC3G }, + /* OEM: Huawei */ + { USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_MOBILE }, + { USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E220 }, + + { 0, 0 } +}; + +#ifdef U3G_DEBUG +static void +u3g_intr(usbd_xfer_handle xfer, usbd_private_handle priv, usbd_status status) +{ + struct u3g_softc *sc = (struct u3g_softc *)priv; + device_printf(sc->sc_dev, "INTERRUPT CALLBACK\n"); +} +#endif + +static int +u3g_huawei_reinit(usbd_device_handle dev) +{ + /* The Huawei device presents itself as a umass device with Windows + * drivers on it. After installation of the driver, it reinits into a + * 3G serial device. + */ + usb_device_request_t req; + usb_config_descriptor_t *cdesc; + + /* Get the config descriptor */ + cdesc = usbd_get_config_descriptor(dev); + if (cdesc == NULL) + return (UMATCH_NONE); + + /* One iface means umass mode, more than 1 (4 usually) means 3G mode */ + if (cdesc->bNumInterface > 1) + return (UMATCH_VENDOR_PRODUCT); + + req.bmRequestType = UT_WRITE_DEVICE; + req.bRequest = UR_SET_FEATURE; + USETW(req.wValue, UF_DEVICE_REMOTE_WAKEUP); + USETW(req.wIndex, UHF_PORT_SUSPEND); + USETW(req.wLength, 0); + + (void) usbd_do_request(dev, &req, 0); + + return UMATCH_NONE; /* mismatch; it will be gone and reappear */ +} + +static int +u3g_match(device_t self) +{ + struct usb_attach_arg *uaa = device_get_ivars(self); + + if (uaa->iface != NULL) + return (UMATCH_NONE); + + if (uaa->vendor == USB_VENDOR_HUAWEI) + return u3g_huawei_reinit(uaa->device); + + if (usb_lookup(u3g_devs, uaa->vendor, uaa->product)) + return UMATCH_VENDOR_PRODUCT; + + return UMATCH_NONE; +} + +static int +u3g_attach(device_t self) +{ + struct u3g_softc *sc = device_get_softc(self); + struct usb_attach_arg *uaa = device_get_ivars(self); + usbd_device_handle dev = uaa->device; + usbd_interface_handle iface; + usb_interface_descriptor_t *id; + usb_endpoint_descriptor_t *ed; + usbd_status error; + int i, n; + usb_config_descriptor_t *cdesc; + struct ucom_softc *ucom = NULL; + char devnamefmt[32]; + + sc->sc_dev = self; +#ifdef DEBUG + sc->sc_intr_number = -1; + sc->sc_intr_pipe = NULL; +#endif + /* Move the device into the configured state. */ + error = usbd_set_config_index(dev, 1, 1); + if (error) { + device_printf(self, "failed to set configuration: %s\n", + usbd_errstr(error)); + goto bad; + } + + /* get the config descriptor */ + cdesc = usbd_get_config_descriptor(dev); + + if (cdesc == NULL) { + device_printf(self, "failed to get configuration descriptor\n"); + goto bad; + } + + sc->sc_udev = dev; + sc->numports = (cdesc->bNumInterface <= U3G_MAXPORTS)?cdesc->bNumInterface:U3G_MAXPORTS; + for ( i = 0; i < sc->numports; i++ ) { + ucom = &sc->sc_ucom[i]; + + ucom->sc_dev = self; + ucom->sc_udev = dev; + error = usbd_device2interface_handle(dev, i, &iface); + if (error) { + device_printf(ucom->sc_dev, + "failed to get interface, err=%s\n", + usbd_errstr(error)); + ucom->sc_dying = 1; + goto bad; + } + id = usbd_get_interface_descriptor(iface); + ucom->sc_iface = iface; + + ucom->sc_bulkin_no = ucom->sc_bulkout_no = -1; + for (n = 0; n < id->bNumEndpoints; n++) { + ed = usbd_interface2endpoint_descriptor(iface, n); + if (ed == NULL) { + device_printf(ucom->sc_dev, + "could not read endpoint descriptor\n"); + goto bad; + } + if (UE_GET_DIR(ed->bEndpointAddress) == UE_DIR_IN && + UE_GET_XFERTYPE(ed->bmAttributes) == UE_BULK) + ucom->sc_bulkin_no = ed->bEndpointAddress; + else if (UE_GET_DIR(ed->bEndpointAddress) == UE_DIR_OUT && + UE_GET_XFERTYPE(ed->bmAttributes) == UE_BULK) + ucom->sc_bulkout_no = ed->bEndpointAddress; + } + if (ucom->sc_bulkin_no == -1 || ucom->sc_bulkout_no == -1) { + device_printf(ucom->sc_dev, "missing endpoint\n"); + goto bad; + } + ucom->sc_parent = sc; + ucom->sc_ibufsize = U3GBUFSZ; + ucom->sc_obufsize = U3GBUFSZ; + ucom->sc_ibufsizepad = U3GBUFSZ; + ucom->sc_opkthdrlen = 0; + + ucom->sc_callback = &u3g_callback; + + sprintf(devnamefmt,"U%d.%%d", device_get_unit(self)); + DPRINTF(("u3g: in=0x%x out=0x%x, devname=%s\n", + ucom->sc_bulkin_no, ucom->sc_bulkout_no, devnamefmt)); +#if __FreeBSD_version < 800000 + ucom_attach_tty(ucom, TS_CALLOUT, devnamefmt, i); +#else + ucom_attach_tty(ucom, devnamefmt, i); +#endif + } +#ifdef U3G_DEBUG + if (sc->sc_intr_number != -1 && sc->sc_intr_pipe == NULL) { + sc->sc_intr_buf = malloc(sc->sc_isize, M_USBDEV, M_WAITOK); + error = usbd_open_pipe_intr(sc->sc_intr_iface, + sc->sc_intr_number, + USBD_SHORT_XFER_OK, + &sc->sc_intr_pipe, + sc, + sc->sc_intr_buf, + sc->sc_isize, + u3g_intr, + 100); + if (error) { + device_printf(self, + "cannot open interrupt pipe (addr %d)\n", + sc->sc_intr_number); + goto bad; + } + } +#endif + device_printf(self, "configured %d serial ports (/dev/cuaU%d.X)", + sc->numports, device_get_unit(self)); + + return 0; + +bad: + DPRINTF(("u3g_attach: ATTACH ERROR\n")); + ucom->sc_dying = 1; + return ENXIO; +} + +static int +u3g_detach(device_t self) +{ + struct u3g_softc *sc = device_get_softc(self); + int rv = 0; + int i; + + DPRINTF(("u3g_detach: sc=%p\n", sc)); + + for (i = 0; i < sc->numports; i++) { + if(sc->sc_ucom[i].sc_udev) { + sc->sc_ucom[i].sc_dying = 1; + rv = ucom_detach(&sc->sc_ucom[i]); + if(rv != 0) { + device_printf(self, "Can't deallocat port %d", i); + return rv; + } + } + } + +#ifdef U3G_DEBUG + if (sc->sc_intr_pipe != NULL) { + int err = usbd_abort_pipe(sc->sc_intr_pipe); + if (err) + device_printf(self, + "abort interrupt pipe failed: %s\n", + usbd_errstr(err)); + err = usbd_close_pipe(sc->sc_intr_pipe); + if (err) + device_printf(self, + "close interrupt pipe failed: %s\n", + usbd_errstr(err)); + free(sc->sc_intr_buf, M_USBDEV); + sc->sc_intr_pipe = NULL; + } +#endif + + return 0; +} + +static device_method_t u3g_methods[] = { + /* Device interface */ + DEVMETHOD(device_probe, u3g_match), + DEVMETHOD(device_attach, u3g_attach), + DEVMETHOD(device_detach, u3g_detach), + + { 0, 0 } +}; + +static driver_t u3g_driver = { + "ucom", + u3g_methods, + sizeof (struct u3g_softc) +}; + +DRIVER_MODULE(u3g, uhub, u3g_driver, ucom_devclass, usbd_driver_load, 0); +MODULE_DEPEND(u3g, usb, 1, 1, 1); +MODULE_DEPEND(u3g, ucom, UCOM_MINVER, UCOM_PREFVER, UCOM_MAXVER); Modified: head/sys/dev/usb/ubsa.c ============================================================================== --- head/sys/dev/usb/ubsa.c Thu Oct 9 20:51:25 2008 (r183734) +++ head/sys/dev/usb/ubsa.c Thu Oct 9 21:25:01 2008 (r183735) @@ -161,8 +161,6 @@ SYSCTL_INT(_hw_usb_ubsa, OID_AUTO, debug struct ubsa_softc { struct ucom_softc sc_ucom; - int sc_huawei; - int sc_iface_number; /* interface number */ usbd_interface_handle sc_intr_iface; /* interrupt interface */ @@ -228,24 +226,11 @@ static const struct ubsa_product { { USB_VENDOR_GOHUBS, USB_PRODUCT_GOHUBS_GOCOM232 }, /* Peracom */ { USB_VENDOR_PERACOM, USB_PRODUCT_PERACOM_SERIAL1 }, - /* Dell version of the Novatel 740 */ - { USB_VENDOR_DELL, USB_PRODUCT_DELL_U740 }, - /* Option Vodafone MC3G */ - { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_VODAFONEMC3G }, - /* Option GlobeTrotter 3G */ - { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GT3G }, - /* Option GlobeTrotter 3G QUAD */ - { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GT3GQUAD }, - /* Option GlobeTrotter 3G+ */ - { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GT3GPLUS }, - /* Option GlobeTrotter Max 3.6 */ - { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GTMAX36 }, - /* Huawei Mobile */ - { USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_MOBILE }, - { USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E270 }, + /* Merlin */ { USB_VENDOR_MERLIN, USB_PRODUCT_MERLIN_V620 }, /* Qualcomm, Inc. ZTE CDMA */ { USB_VENDOR_QUALCOMMINC, USB_PRODUCT_QUALCOMMINC_CDMA_MSM }, + /* Novatel */ { USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_CDMA_MODEM }, /* Novatel Wireless Merlin ES620 */ { USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_ES620 }, @@ -256,6 +241,8 @@ static const struct ubsa_product { /* Novatel Wireless Merlin U740 */ { USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_U740 }, { USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_U740_2 }, + /* Dell version of the Novatel 740 */ + { USB_VENDOR_DELL, USB_PRODUCT_DELL_U740 }, /* Novatel Wireless Merlin U950D */ { USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_U950D }, /* Novatel Wireless Merlin V620 */ @@ -341,52 +328,6 @@ MODULE_DEPEND(ubsa, usb, 1, 1, 1); MODULE_DEPEND(ubsa, ucom, UCOM_MINVER, UCOM_PREFVER, UCOM_MAXVER); MODULE_VERSION(ubsa, UBSA_MODVER); -/* - * Huawei Exxx radio devices have a built in flash disk which is their - * default power up configuration. This allows the device to carry its - * own installation software. - * - * Instead of following the USB spec, and create multiple configuration - * descriptors for this, the devices expects the driver to send - * UF_DEVICE_REMOTE_WAKEUP to endpoint 2 to reset the device, so it - * reprobes, now with the radio exposed. - */ - -static usbd_status -ubsa_huawei(device_t self, struct usb_attach_arg *uaa) { - usb_device_request_t req; usbd_device_handle dev; - usb_config_descriptor_t *cdesc; - - if (self == NULL) - return (UMATCH_NONE); - if (uaa == NULL) - return (UMATCH_NONE); - dev = uaa->device; - if (dev == NULL) - return (UMATCH_NONE); - /* get the config descriptor */ - cdesc = usbd_get_config_descriptor(dev); - if (cdesc == NULL) - return (UMATCH_NONE); - - if (cdesc->bNumInterface > 1) - return (0); - - /* Bend it like Beckham */ - device_printf(self, "Kicking Huawei device into radio mode\n"); - memset(&req, 0, sizeof req); - req.bmRequestType = UT_WRITE_DEVICE; - req.bRequest = UR_SET_FEATURE; - USETW(req.wValue, UF_DEVICE_REMOTE_WAKEUP); - USETW(req.wIndex, 2); - USETW(req.wLength, 0); - - /* We get error return, but it works */ - (void)usbd_do_request(dev, &req, 0); - return (UMATCH_NONE); -} - - static int ubsa_match(device_t self) { @@ -399,9 +340,6 @@ ubsa_match(device_t self) for (i = 0; ubsa_products[i].vendor != 0; i++) { if (ubsa_products[i].vendor == uaa->vendor && ubsa_products[i].product == uaa->product) { - if (uaa->vendor == USB_VENDOR_HUAWEI && - ubsa_huawei(self, uaa)) - break; return (UMATCH_VENDOR_PRODUCT); } } @@ -424,9 +362,6 @@ ubsa_attach(device_t self) dev = uaa->device; ucom = &sc->sc_ucom; - if (uaa->vendor == USB_VENDOR_HUAWEI) - sc->sc_huawei = 1; - /* * initialize rts, dtr variables to something * different from boolean 0, 1 @@ -575,8 +510,6 @@ ubsa_request(struct ubsa_softc *sc, u_in usbd_status err; /* The huawei Exxx devices support none of these tricks */ - if (sc->sc_huawei) - return (0); req.bmRequestType = UT_WRITE_VENDOR_DEVICE; req.bRequest = request; USETW(req.wValue, value); Modified: head/sys/dev/usb/usbdevs ============================================================================== --- head/sys/dev/usb/usbdevs Thu Oct 9 20:51:25 2008 (r183734) +++ head/sys/dev/usb/usbdevs Thu Oct 9 21:25:01 2008 (r183735) @@ -1434,7 +1434,7 @@ product HTC SMARTPHONE 0x0a51 SmartPhon /* HUAWEI products */ product HUAWEI MOBILE 0x1001 Huawei Mobile -product HUAWEI E270 0x1003 Huawei HSPA modem +product HUAWEI E220 0x1003 Huawei HSDPA modem /* HUAWEI 3com products */ product HUAWEI3COM WUB320G 0x0009 Aolynk WUB320g Modified: head/sys/i386/conf/GENERIC ============================================================================== --- head/sys/i386/conf/GENERIC Thu Oct 9 20:51:25 2008 (r183734) +++ head/sys/i386/conf/GENERIC Thu Oct 9 21:25:01 2008 (r183735) @@ -304,6 +304,7 @@ device urio # Diamond Rio 500 MP3 play device uscanner # Scanners # USB Serial devices device ucom # Generic com ttys +device u3g # USB-based 3G modems (Option, Huawei, Sierra) device uark # Technologies ARK3116 based serial adapters device ubsa # Belkin F5U103 and compatible serial adapters device uftdi # For FTDI usb serial adapters Modified: head/sys/modules/Makefile ============================================================================== --- head/sys/modules/Makefile Thu Oct 9 20:51:25 2008 (r183734) +++ head/sys/modules/Makefile Thu Oct 9 21:25:01 2008 (r183735) @@ -269,6 +269,7 @@ SUBDIR= ${_3dfx} \ twe \ tx \ txp \ + u3g \ uark \ uart \ ubsa \ Added: head/sys/modules/u3g/Makefile ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/sys/modules/u3g/Makefile Thu Oct 9 21:25:01 2008 (r183735) @@ -0,0 +1,8 @@ +# $FreeBSD$ + +.PATH: ${.CURDIR}/../../dev/usb + +KMOD= u3g +SRCS= u3g.c ucomvar.h opt_usb.h device_if.h bus_if.h usbdevs.h + +.include _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" ------------------------------------------------------- From matheus at eternamente.info Fri Oct 10 02:27:04 2008 From: matheus at eternamente.info (Nenhum_de_Nos) Date: Fri Oct 10 02:27:10 2008 Subject: Request for testers: Option 3G cards, also Sierra, Huawei and Novatel In-Reply-To: <200810092344.10388.nick@van-laarhoven.org> References: <200810092344.10388.nick@van-laarhoven.org> Message-ID: <08cc4125205c11d9df338d6ee95a1d35.squirrel@cygnus.homeunix.com> hi, this works for huwaei E226 as well ? I'm willing to test this on stable this weekend :) I did tried the umass-out-of-kernel way and although it did connected, it created a route to 127.0.0.1 and no navigation worked. matheus -- We will call you cygnus, The God of balance you shall be From vibarus at googlemail.com Tue Oct 14 02:25:22 2008 From: vibarus at googlemail.com (Vincent Barus) Date: Tue Oct 14 02:25:47 2008 Subject: LG combo drive and Attansic Technology ethernet card on Asus P5Q Pro In-Reply-To: <20081004073930.GA49756@icarus.home.lan> References: <20081004034524.GA44662@icarus.home.lan> <200810040649.GAA19778@sopwith.solgatos.com> <20081004073304.GA48931@icarus.home.lan> <20081004073930.GA49756@icarus.home.lan> Message-ID: Hi, maybe Andrey Elsukov can help with this Marvell chips: http://butcher.heavennet.ru/patches/kernel/ata/marvell/README.txt He worked on it for a few months. Regards, Vincent On Sat, Oct 4, 2008 at 9:39 AM, Jeremy Chadwick wrote: > On Sat, Oct 04, 2008 at 12:33:04AM -0700, Jeremy Chadwick wrote: >> On Fri, Oct 03, 2008 at 11:49:01PM +0100, Dieter wrote: >> > >> The drive is a new LG combo drive, I believe GH22LP20 or something close to it. >> > >> > I have an older LG PATA combo drive which works ok. >> > >> > Does it show up when booting? (Does dmesg work from the installation shell?) >> > >> > Maybe you need to "kldload atapicam" ? Or is that only needed for writing, >> > I forget... >> > >> > > The only thing I can think of is that the P5Q boards use a Marvell >> > > ATA/IDE controller (yes, you read that correctly). I wonder if FreeBSD >> > > somehow lacks support for this... >> > >> > 7.0 ata man page claims support for: >> > >> > Marvell 88SX5040, 88SX5041, 88SX5080, 88SX5081, 88SX6041, >> > 88SX6081, 88SX6101, 88SX6141. >> >> None of these are what's on the P5Q series boards. The P5Q series >> boards use a Marvell 88SE6102 Super I/O chip, which also drives IDE/PATA >> devices. (SATA is driven via ICH10 or ICH10R). >> >> I'm left to believe FreeBSD simply lacks support for this very new >> Marvell chip. I'm willing to bet there is no sign of ata(4) devices nor >> atapci(4) PCI association during boot-up. > > Mac folks are seeing the same problem: > > http://forum.insanelymac.com/index.php?showtopic=128985 > http://www.insanelymac.com/lofiversion/index.php/t99634.html > > Wikipedia states the 88SE6121, not the 88SE6102, is used on P5Q series > boards. But the P5Q SE motherboard manual states it's a 88SE6102. > > http://en.wikipedia.org/wiki/List_of_Marvell_Technology_Group_chipsets > > So either the motherboard manual is wrong, Wikipedia is wrong, or the > P5Q SE and P5Q Pro contain different models/versions of ICs. > > When I get a P5Q SE for Yong-Hyeon, I'll make note of what's > silkscreened on the ASIC. > > -- > | 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" > -- ~ vb From koitsu at FreeBSD.org Tue Oct 14 04:27:15 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Tue Oct 14 04:27:22 2008 Subject: LG combo drive and Attansic Technology ethernet card on Asus P5Q Pro In-Reply-To: <20081004073930.GA49756@icarus.home.lan> References: <20081004034524.GA44662@icarus.home.lan> <200810040649.GAA19778@sopwith.solgatos.com> <20081004073304.GA48931@icarus.home.lan> <20081004073930.GA49756@icarus.home.lan> Message-ID: <20081014042713.GA39900@icarus.home.lan> On Sat, Oct 04, 2008 at 12:39:30AM -0700, Jeremy Chadwick wrote: > On Sat, Oct 04, 2008 at 12:33:04AM -0700, Jeremy Chadwick wrote: > > On Fri, Oct 03, 2008 at 11:49:01PM +0100, Dieter wrote: > > > >> The drive is a new LG combo drive, I believe GH22LP20 or something close to it. > > > > > > I have an older LG PATA combo drive which works ok. > > > > > > Does it show up when booting? (Does dmesg work from the installation shell?) > > > > > > Maybe you need to "kldload atapicam" ? Or is that only needed for writing, > > > I forget... > > > > > > > The only thing I can think of is that the P5Q boards use a Marvell > > > > ATA/IDE controller (yes, you read that correctly). I wonder if FreeBSD > > > > somehow lacks support for this... > > > > > > 7.0 ata man page claims support for: > > > > > > Marvell 88SX5040, 88SX5041, 88SX5080, 88SX5081, 88SX6041, > > > 88SX6081, 88SX6101, 88SX6141. > > > > None of these are what's on the P5Q series boards. The P5Q series > > boards use a Marvell 88SE6102 Super I/O chip, which also drives IDE/PATA > > devices. (SATA is driven via ICH10 or ICH10R). > > > > I'm left to believe FreeBSD simply lacks support for this very new > > Marvell chip. I'm willing to bet there is no sign of ata(4) devices nor > > atapci(4) PCI association during boot-up. > > Mac folks are seeing the same problem: > > http://forum.insanelymac.com/index.php?showtopic=128985 > http://www.insanelymac.com/lofiversion/index.php/t99634.html > > Wikipedia states the 88SE6121, not the 88SE6102, is used on P5Q series > boards. But the P5Q SE motherboard manual states it's a 88SE6102. > > http://en.wikipedia.org/wiki/List_of_Marvell_Technology_Group_chipsets > > So either the motherboard manual is wrong, Wikipedia is wrong, or the > P5Q SE and P5Q Pro contain different models/versions of ICs. > > When I get a P5Q SE for Yong-Hyeon, I'll make note of what's > silkscreened on the ASIC. Yong-Hyeon received my hardware yesterday. Before I shipped it, I made note of the silkscreening on numerous chips: Atheros AR8121-AL1E = GigE NIC + PHY Marvell 88SE6102-NNC1 = ATA/IDE controller Nuvoton/Winbond W83667HG-A = Super I/O + hardware monitoring -- | 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 primus008 at yandex.ru Wed Oct 15 00:55:31 2008 From: primus008 at yandex.ru (Borodin Oleg) Date: Wed Oct 15 00:55:38 2008 Subject: Patch for correct determine & work uplcom R232-USB Profilic chips PL2303HX Message-ID: <48F53CAE.3010509@yandex.ru> Patch for correct determine & work uplcom with R232-USB Profilic PL2303HX chips Borodin Oleg Kaliningrad, Russia --- ./sys/dev/usb/uplcom.c.orig 2008-10-04 10:23:55.000000000 +0300 +++ ./sys/dev/usb/uplcom.c 2008-10-14 07:56:45.000000000 +0300 @@ -243,6 +243,10 @@ /* ST Lab USB-SERIAL-4 */ { USB_VENDOR_PROLIFIC, USB_PRODUCT_PROLIFIC_PL2303, 0x300, TYPE_PL2303X }, + /* TRENDnet TU-S9, Rover Computers Ltd and other PL2303HX based USB-RS232 */ + { USB_VENDOR_PROLIFIC, USB_PRODUCT_PROLIFIC_PL2303, + 0x400, TYPE_PL2303X }, + /* IOGEAR/ATEN UC-232A (also ST Lab USB-SERIAL-1) */ { USB_VENDOR_PROLIFIC, USB_PRODUCT_PROLIFIC_PL2303, -1, TYPE_PL2303 }, /* HAMLET exagerate XURS232 */ -------------- next part -------------- --- ./sys/dev/usb/uplcom.c.orig 2008-10-04 10:23:55.000000000 +0300 +++ ./sys/dev/usb/uplcom.c 2008-10-14 07:56:45.000000000 +0300 @@ -243,6 +243,10 @@ /* ST Lab USB-SERIAL-4 */ { USB_VENDOR_PROLIFIC, USB_PRODUCT_PROLIFIC_PL2303, 0x300, TYPE_PL2303X }, + /* ST Lab USB-SERIAL-4 */ + { USB_VENDOR_PROLIFIC, USB_PRODUCT_PROLIFIC_PL2303, + 0x400, TYPE_PL2303X }, + /* IOGEAR/ATEN UC-232A (also ST Lab USB-SERIAL-1) */ { USB_VENDOR_PROLIFIC, USB_PRODUCT_PROLIFIC_PL2303, -1, TYPE_PL2303 }, /* HAMLET exagerate XURS232 */ From hselasky at c2i.net Wed Oct 15 07:53:49 2008 From: hselasky at c2i.net (Hans Petter Selasky) Date: Wed Oct 15 07:53:56 2008 Subject: Patch for correct determine & work uplcom R232-USB Profilic chips PL2303HX In-Reply-To: <48F53CAE.3010509@yandex.ru> References: <48F53CAE.3010509@yandex.ru> Message-ID: <200810150855.50141.hselasky@c2i.net> Hi Borodin, Please make a PR, attach your patch and assign it to USB so that it does not get lost. --HPS On Wednesday 15 October 2008, Borodin Oleg wrote: > Patch for correct determine & work uplcom with R232-USB Profilic > PL2303HX chips > > Borodin Oleg > Kaliningrad, Russia > > --- ./sys/dev/usb/uplcom.c.orig 2008-10-04 10:23:55.000000000 > +0300 > +++ ./sys/dev/usb/uplcom.c 2008-10-14 07:56:45.000000000 > +0300 > @@ -243,6 +243,10 > @@ > > /* ST Lab USB-SERIAL-4 > */ > > { USB_VENDOR_PROLIFIC, > USB_PRODUCT_PROLIFIC_PL2303, > > 0x300, TYPE_PL2303X > }, > > + /* TRENDnet TU-S9, Rover Computers Ltd and other PL2303HX based > USB-RS232 > */ > > + { USB_VENDOR_PROLIFIC, > USB_PRODUCT_PROLIFIC_PL2303, > > + 0x400, TYPE_PL2303X > }, > > + > > /* IOGEAR/ATEN UC-232A (also ST Lab USB-SERIAL-1) > */ > { USB_VENDOR_PROLIFIC, USB_PRODUCT_PROLIFIC_PL2303, -1, > TYPE_PL2303 }, > /* HAMLET exagerate XURS232 > */ From primus008 at yandex.ru Wed Oct 15 11:03:51 2008 From: primus008 at yandex.ru (Borodin Oleg) Date: Wed Oct 15 11:03:58 2008 Subject: Patch for correct determine & work uplcom R232-USB Profilic chips PL2303HX In-Reply-To: <200810150855.50141.hselasky@c2i.net> References: <48F53CAE.3010509@yandex.ru> <200810150855.50141.hselasky@c2i.net> Message-ID: <48F5CE0F.7000809@yandex.ru> Hi! I send PR, usb/128115 Thx, Borodin Oleg Kaliningrad, Russia Hans Petter Selasky ?????: > Hi Borodin, > > Please make a PR, attach your patch and assign it to USB so that it does not > get lost. > > --HPS > > On Wednesday 15 October 2008, Borodin Oleg wrote: > >> Patch for correct determine & work uplcom with R232-USB Profilic >> PL2303HX chips >> >> Borodin Oleg >> Kaliningrad, Russia >> >> --- ./sys/dev/usb/uplcom.c.orig 2008-10-04 10:23:55.000000000 >> +0300 >> +++ ./sys/dev/usb/uplcom.c 2008-10-14 07:56:45.000000000 >> +0300 >> @@ -243,6 +243,10 >> @@ >> >> /* ST Lab USB-SERIAL-4 >> */ >> >> { USB_VENDOR_PROLIFIC, >> USB_PRODUCT_PROLIFIC_PL2303, >> >> 0x300, TYPE_PL2303X >> }, >> >> + /* TRENDnet TU-S9, Rover Computers Ltd and other PL2303HX based >> USB-RS232 >> */ >> >> + { USB_VENDOR_PROLIFIC, >> USB_PRODUCT_PROLIFIC_PL2303, >> >> + 0x400, TYPE_PL2303X >> }, >> >> + >> >> /* IOGEAR/ATEN UC-232A (also ST Lab USB-SERIAL-1) >> */ >> { USB_VENDOR_PROLIFIC, USB_PRODUCT_PROLIFIC_PL2303, -1, >> TYPE_PL2303 }, >> /* HAMLET exagerate XURS232 >> */ >> > > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" > > From jontheil at gmail.com Wed Oct 15 13:03:15 2008 From: jontheil at gmail.com (Jon Theil Nielsen) Date: Wed Oct 15 13:03:25 2008 Subject: RAID 5 - serious problem Message-ID: <8f82c35c0810150532o52ae50b5kef7c685fd23a0af4@mail.gmail.com> Dear list, Something happened that I don't think should be possible. I "lost" all three disks in my RAID 5 array simultaneously after approx. two years without any problem. And I fear I will never see my data again. But I really hope some of you clever persons can give me some hints. My system is: FreeBSD 7.0-Release Intel D975XBX2 motherboard (Intel Matrix Storage Technology) 3 WD Raptor 74 GB in a RAID 5 array 1 WD Raptor 150 GB as a standalone disk / and /var mounted on the standalone,, /usr on the RAID 5 I believe what happened was that one of the disks didn't respond for such a long time, that is was marked "bad". And afterwards the same thing happened for the other disks. When I try to boot the system, all three disks are marked "Offline". The BIOS utility for the host controller has no option to force the disks back online. I have another machine with a S5000XVN board and Intel Embedded Server RAID Technology II. The BIOS configuration utility on this board has the option to force offline drives back online. I am very desperate not to lose my data, so I don't know if I dare moving the drives to the other machine and try to make them online again. Do you think I should try? In general, are there any procedures I can try to recover my RAID array? Or is the offline status definitive ? and all data definitely lost? I guess some specialized companies have the expertise to recover lost data from a broken RAID array, but I don't know. And I don't know the price of such a service. I would really, really appreciate any kind of help. I have backups of most user data, but not of the system configuration (and maybe even not the databases). This is of course pretty stupid. In the future, I will not rely on RAID 5 as a foolproof solution? Regards, Jon -- *Jon Theil Nielsen* From koitsu at FreeBSD.org Wed Oct 15 13:15:49 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Wed Oct 15 13:15:55 2008 Subject: RAID 5 - serious problem In-Reply-To: <8f82c35c0810150532o52ae50b5kef7c685fd23a0af4@mail.gmail.com> References: <8f82c35c0810150532o52ae50b5kef7c685fd23a0af4@mail.gmail.com> Message-ID: <20081015131546.GA78192@icarus.home.lan> On Wed, Oct 15, 2008 at 02:32:25PM +0200, Jon Theil Nielsen wrote: > Dear list, > > Something happened that I don't think should be possible. I "lost" all three > disks in my RAID 5 array simultaneously after approx. two years without any > problem. And I fear I will never see my data again. But I really hope some > of you clever persons can give me some hints. My system is: > FreeBSD 7.0-Release > Intel D975XBX2 motherboard (Intel Matrix Storage Technology) Are you using the Matrix Storage Technology? If so, immediately stop. FreeBSD's support for this is very, very bad, and will nearly guarantee data loss. There are many of us who have tried it, and it's known to be buggy on FreeBSD. http://wiki.freebsd.org/JeremyChadwick/ATA_issues_and_troubleshooting I recommend you stop using this feature and start using ZFS or gvinum for what you need. > 3 WD Raptor 74 GB in a RAID 5 array > 1 WD Raptor 150 GB as a standalone disk > / and /var mounted on the standalone,, /usr on the RAID 5 > I believe what happened was that one of the disks didn't respond for such a > long time, that is was marked "bad". And afterwards the same thing happened > for the other disks. When I try to boot the system, all three disks are > marked "Offline". > The BIOS utility for the host controller has no option to force the disks > back online. > I have another machine with a S5000XVN board and Intel Embedded Server RAID > Technology II. The BIOS configuration utility on this board has the option > to force offline drives back online. Any "embedded" RAID is usually BIOS RAID managed by either a "software RAID IC" (e.g. an IC on the motherboard that handles LBA/CHS addressing for creating a pseudo-array, but the OS still does all of the management and does not off-load anything). > I am very desperate not to lose my data, so I don't know if I dare moving > the drives to the other machine and try to make them online again. Do you > think I should try? No, but you might not have any choice. It honestly sounds like the metadata on your disks is in a bad state. I would recommend you try booting Linux, since their support for MatrixRAID is significantly better/more advanced. Ideally, you should be able to bring the RAID members back online using their tools, then reboot into FreeBSD and cross your fingers that your data becomes accessible. Once accessible, offload it somewhere immediately, and follow my above recommendations. > In general, are there any procedures I can try to recover my RAID array? Or > is the offline status definitive ? and all data definitely lost? I guess > some specialized companies have the expertise to recover lost data from a > broken RAID array, but I don't know. And I don't know the price of such a > service. > I would really, really appreciate any kind of help. > I have backups of most user data, but not of the system configuration (and > maybe even not the databases). This is of course pretty stupid. In the > future, I will not rely on RAID 5 as a foolproof solution? RAID 5 is a fine solution, but you have learned a very valuable lesson, one which I will enclose in asterisks to make it crystal clear: ***RAID DOES NOT REPLACE BACKUPS***. Repeat this mantra over and over until you accept it. :-) -- | 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 mex at active.sk Wed Oct 15 13:41:49 2008 From: mex at active.sk (MeX) Date: Wed Oct 15 13:41:56 2008 Subject: RAID 5 - serious problem In-Reply-To: <20081015131546.GA78192@icarus.home.lan> References: <8f82c35c0810150532o52ae50b5kef7c685fd23a0af4@mail.gmail.com> <20081015131546.GA78192@icarus.home.lan> Message-ID: <6bb891ca5bbd9ba095a5fa61e1b8e3cd.squirrel@mail.active.sk> Hello, On Str, Okt?ber 15, 2008 15:15, Jeremy Chadwick wrote: > Are you using the Matrix Storage Technology? If so, immediately stop. > FreeBSD's support for this is very, very bad, and will nearly guarantee > data loss. There are many of us who have tried it, and it's known to > be buggy on FreeBSD. > > http://wiki.freebsd.org/JeremyChadwick/ATA_issues_and_troubleshooting > > I recommend you stop using this feature and start using ZFS or gvinum > for what you need. do you think that ZFS code in FreeBSD 7.0-R (7.1-R) is enough stable for using it in production environment for RAID-1 even also for RAID-5? About 5 years ago I tried vinum for RAID1 if I remember clearly, but I never tried gvinum. It's production ready piece of cake? Many thanks MeX From jontheil at gmail.com Wed Oct 15 13:51:21 2008 From: jontheil at gmail.com (Jon Theil Nielsen) Date: Wed Oct 15 13:51:29 2008 Subject: RAID 5 - serious problem In-Reply-To: <20081015131546.GA78192@icarus.home.lan> References: <8f82c35c0810150532o52ae50b5kef7c685fd23a0af4@mail.gmail.com> <20081015131546.GA78192@icarus.home.lan> Message-ID: <8f82c35c0810150651r78387c2fle2868f69e9eeb7d3@mail.gmail.com> 2008/10/15 Jeremy Chadwick > On Wed, Oct 15, 2008 at 02:32:25PM +0200, Jon Theil Nielsen wrote: > > Dear list, > > > > Something happened that I don't think should be possible. I "lost" all > three > > disks in my RAID 5 array simultaneously after approx. two years without > any > > problem. And I fear I will never see my data again. But I really hope > some > > of you clever persons can give me some hints. My system is: > > FreeBSD 7.0-Release > > Intel D975XBX2 motherboard (Intel Matrix Storage Technology) > > Are you using the Matrix Storage Technology? If so, immediately stop. > FreeBSD's support for this is very, very bad, and will nearly guarantee > data loss. There are many of us who have tried it, and it's known to > be buggy on FreeBSD. > > http://wiki.freebsd.org/JeremyChadwick/ATA_issues_and_troubleshooting > > I recommend you stop using this feature and start using ZFS or gvinum > for what you need. > > > 3 WD Raptor 74 GB in a RAID 5 array > > 1 WD Raptor 150 GB as a standalone disk > > / and /var mounted on the standalone,, /usr on the RAID 5 > > I believe what happened was that one of the disks didn't respond for such > a > > long time, that is was marked "bad". And afterwards the same thing > happened > > for the other disks. When I try to boot the system, all three disks are > > marked "Offline". > > The BIOS utility for the host controller has no option to force the disks > > back online. > > I have another machine with a S5000XVN board and Intel Embedded Server > RAID > > Technology II. The BIOS configuration utility on this board has the > option > > to force offline drives back online. > > Any "embedded" RAID is usually BIOS RAID managed by either a "software > RAID IC" (e.g. an IC on the motherboard that handles LBA/CHS addressing > for creating a pseudo-array, but the OS still does all of the management > and does not off-load anything). > > > I am very desperate not to lose my data, so I don't know if I dare moving > > the drives to the other machine and try to make them online again. Do you > > think I should try? > > No, but you might not have any choice. It honestly sounds like the > metadata on your disks is in a bad state. > > I would recommend you try booting Linux, since their support for > MatrixRAID is significantly better/more advanced. Ideally, you should > be able to bring the RAID members back online using their tools, then > reboot into FreeBSD and cross your fingers that your data becomes > accessible. Once accessible, offload it somewhere immediately, and > follow my above recommendations. > > > In general, are there any procedures I can try to recover my RAID array? > Or > > is the offline status definitive ? and all data definitely lost? I guess > > some specialized companies have the expertise to recover lost data from a > > broken RAID array, but I don't know. And I don't know the price of such a > > service. > > I would really, really appreciate any kind of help. > > I have backups of most user data, but not of the system configuration > (and > > maybe even not the databases). This is of course pretty stupid. In the > > future, I will not rely on RAID 5 as a foolproof solution? > > RAID 5 is a fine solution, but you have learned a very valuable lesson, > one which I will enclose in asterisks to make it crystal clear: ***RAID > DOES NOT REPLACE BACKUPS***. Repeat this mantra over and over until you > accept it. :-) > > -- > | 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 | > > Hi Jeremy, Thanks for your advice. As I understand you, the best bet is to boot from Linux and try to repair. And that trying with my other controller might be the second best. Would it be an idea to try to run som sort of Linux live cd? I have no machines with Linux installed. Regards, Jon From koitsu at FreeBSD.org Wed Oct 15 13:53:43 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Wed Oct 15 13:53:49 2008 Subject: RAID 5 - serious problem In-Reply-To: <6bb891ca5bbd9ba095a5fa61e1b8e3cd.squirrel@mail.active.sk> References: <8f82c35c0810150532o52ae50b5kef7c685fd23a0af4@mail.gmail.com> <20081015131546.GA78192@icarus.home.lan> <6bb891ca5bbd9ba095a5fa61e1b8e3cd.squirrel@mail.active.sk> Message-ID: <20081015135341.GA78986@icarus.home.lan> On Wed, Oct 15, 2008 at 03:27:26PM +0200, MeX wrote: > Hello, > > On Str, Okt?ber 15, 2008 15:15, Jeremy Chadwick wrote: > > Are you using the Matrix Storage Technology? If so, immediately stop. > > FreeBSD's support for this is very, very bad, and will nearly guarantee > > data loss. There are many of us who have tried it, and it's known to > > be buggy on FreeBSD. > > > > http://wiki.freebsd.org/JeremyChadwick/ATA_issues_and_troubleshooting > > > > I recommend you stop using this feature and start using ZFS or gvinum > > for what you need. > > do you think that ZFS code in FreeBSD 7.0-R (7.1-R) is enough stable for > using it in production environment for RAID-1 even also for RAID-5? What you're asking is completely unrelated to the topic of this thread. The OP should consider his alternatives to Intel MatrixRAID -- it really doesn't matter what the alternatives are, because they're going to be better than the situation/scenario he's in right now. Heck, in this situation, he'd be better off not using MatrixRAID at all, and instead having one filesystem per disk! Losing one filesystem would be better than losing *all* of them. If you want RAID-1, you have the choice of ccd, gmirror, or ZFS. If you want RAID-5, you have the choice of gvinum or ZFS. None of them are perfect, but they're all decent. There are still ZFS stability issues which need to be hammered out, but most of those have been addressed in CURRENT. I'm familiar enough with ZFS tuning at this point that I would trust using it on RELENG_7 (sans root filesystem on ZFS -- I don't want to deal with the hassles involved). > About 5 years ago I tried vinum for RAID1 if I remember clearly, but I > never tried gvinum. It's production ready piece of cake? I have no personal experience with gmirror or gvinum. I experimented with vinum on FreeBSD 3.x, and I was thoroughly disappointed. When reading that comment, take into consideration that vinum != gvinum, and that was in the FreeBSD 3.x days. Those who have used gmirror have reported immense success with it. -- | 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 Wed Oct 15 14:01:34 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Wed Oct 15 14:01:43 2008 Subject: RAID 5 - serious problem In-Reply-To: <8f82c35c0810150651r78387c2fle2868f69e9eeb7d3@mail.gmail.com> References: <8f82c35c0810150532o52ae50b5kef7c685fd23a0af4@mail.gmail.com> <20081015131546.GA78192@icarus.home.lan> <8f82c35c0810150651r78387c2fle2868f69e9eeb7d3@mail.gmail.com> Message-ID: <20081015140132.GB78986@icarus.home.lan> On Wed, Oct 15, 2008 at 03:51:19PM +0200, Jon Theil Nielsen wrote: > 2008/10/15 Jeremy Chadwick > > > On Wed, Oct 15, 2008 at 02:32:25PM +0200, Jon Theil Nielsen wrote: > > > Dear list, > > > > > > Something happened that I don't think should be possible. I "lost" all > > three > > > disks in my RAID 5 array simultaneously after approx. two years without > > any > > > problem. And I fear I will never see my data again. But I really hope > > some > > > of you clever persons can give me some hints. My system is: > > > FreeBSD 7.0-Release > > > Intel D975XBX2 motherboard (Intel Matrix Storage Technology) > > > > Are you using the Matrix Storage Technology? If so, immediately stop. > > FreeBSD's support for this is very, very bad, and will nearly guarantee > > data loss. There are many of us who have tried it, and it's known to > > be buggy on FreeBSD. > > > > http://wiki.freebsd.org/JeremyChadwick/ATA_issues_and_troubleshooting > > > > I recommend you stop using this feature and start using ZFS or gvinum > > for what you need. > > > > > 3 WD Raptor 74 GB in a RAID 5 array > > > 1 WD Raptor 150 GB as a standalone disk > > > / and /var mounted on the standalone,, /usr on the RAID 5 > > > I believe what happened was that one of the disks didn't respond for such > > a > > > long time, that is was marked "bad". And afterwards the same thing > > happened > > > for the other disks. When I try to boot the system, all three disks are > > > marked "Offline". > > > The BIOS utility for the host controller has no option to force the disks > > > back online. > > > I have another machine with a S5000XVN board and Intel Embedded Server > > RAID > > > Technology II. The BIOS configuration utility on this board has the > > option > > > to force offline drives back online. > > > > Any "embedded" RAID is usually BIOS RAID managed by either a "software > > RAID IC" (e.g. an IC on the motherboard that handles LBA/CHS addressing > > for creating a pseudo-array, but the OS still does all of the management > > and does not off-load anything). > > > > > I am very desperate not to lose my data, so I don't know if I dare moving > > > the drives to the other machine and try to make them online again. Do you > > > think I should try? > > > > No, but you might not have any choice. It honestly sounds like the > > metadata on your disks is in a bad state. > > > > I would recommend you try booting Linux, since their support for > > MatrixRAID is significantly better/more advanced. Ideally, you should > > be able to bring the RAID members back online using their tools, then > > reboot into FreeBSD and cross your fingers that your data becomes > > accessible. Once accessible, offload it somewhere immediately, and > > follow my above recommendations. > > > > > In general, are there any procedures I can try to recover my RAID array? > > Or > > > is the offline status definitive ? and all data definitely lost? I guess > > > some specialized companies have the expertise to recover lost data from a > > > broken RAID array, but I don't know. And I don't know the price of such a > > > service. > > > I would really, really appreciate any kind of help. > > > I have backups of most user data, but not of the system configuration > > (and > > > maybe even not the databases). This is of course pretty stupid. In the > > > future, I will not rely on RAID 5 as a foolproof solution? > > > > RAID 5 is a fine solution, but you have learned a very valuable lesson, > > one which I will enclose in asterisks to make it crystal clear: ***RAID > > DOES NOT REPLACE BACKUPS***. Repeat this mantra over and over until you > > accept it. :-) > > > > -- > > | 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 | > > > > Hi Jeremy, > > Thanks for your advice. As I understand you, the best bet is to boot from > Linux and try to repair. > And that trying with my other controller might be the second best. You risk corrupting or losing the metadata using another controller. The two controllers are *not* identical; just because they're Intel doesn't mean they speak the same metadata format. :-) > Would it be an idea to try to run som sort of Linux live cd? I have > no machines with Linux installed. Yes, absolutely. I assume any Linux distribution which uses libata should be able to speak to Intel MatrixRAID disks and BIOSes. Linux refers to this feature as "Intel SATA RAID" or "Intel Software RAID", Any present-day 2.6.x kernel uses libata; the newer the better. I do not know how to manipulate or interface with MatrixRAID on Linux. You will have to Google for how to get support in that regard. My quick searches turn up the following useful links: http://linux-ata.org/faq-sata-raid.html http://gentoo-wiki.com/HOWTO_Gentoo_Install_on_Bios_(Onboard)_RAID http://www.intel.com/support/chipsets/imsm/sb/cs-020663.htm http://iswraid.sourceforge.net/ (old/outdated from the look of it) It would appear the tool to manipulate the metadata is called dmraid(8). I believe the -a flag is what you might require, but I do not know for sure: http://www.linuxmanpages.com/man8/dmraid.8.php http://people.redhat.com/~heinzm/sw/dmraid/ Final note: I *will not* be held responsible for what happens if you use any of these tools. I have absolutely no experience doing any of what I've described; I'm simply articulating the route I'd choose in this scenario. -- | 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 freebsd at sopwith.solgatos.com Wed Oct 15 17:18:14 2008 From: freebsd at sopwith.solgatos.com (Dieter) Date: Wed Oct 15 17:18:20 2008 Subject: RAID 5 - serious problem In-Reply-To: Your message of "Wed, 15 Oct 2008 14:32:25 +0200." <8f82c35c0810150532o52ae50b5kef7c685fd23a0af4@mail.gmail.com> Message-ID: <200810151714.RAA23995@sopwith.solgatos.com> > FreeBSD 7.0-Release > Intel D975XBX2 motherboard (Intel Matrix Storage Technology) > 3 WD Raptor 74 GB in a RAID 5 array > 1 WD Raptor 150 GB as a standalone disk > / and /var mounted on the standalone,, /usr on the RAID 5 > I believe what happened was that one of the disks didn't respond for such a > long time, that is was marked "bad". And afterwards the same thing happened > for the other disks. When I try to boot the system, all three disks are > marked "Offline". > I am very desperate not to lose my data, In that case, step one is to use dd(1) to make a bit-for-bit copy of the three drives to some trusted media. Since they are marked bad/offline, you might need to move them to a controller that doesn't know anything about RAID. (Note that there is risk here, and in almost anything you do at this point.) Once you have this bit-for-bit backup, you can run any experiment you like to attempt to recover your data. If the experiment goes bad, you can dd the exact original contents back using dd, then try a different experiment. While you're at it, make a normal backup using dump(8) or whatever you normally use, of / and /var. Once you have *everything* backed up, you can do risky experiments like booting linux. My personal approach to avoiding data loss is (a) avoid buggy things like inthell and linux. (b) FFS with softdeps and the disk write cache turned off, (c) full backups. I don't have enough ports to run RAID. :-( The downside is that FreeBSD doesn't have NCQ support yet (when? when? when?) so writes are slow. :-( From koitsu at FreeBSD.org Wed Oct 15 18:46:02 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Wed Oct 15 18:46:13 2008 Subject: RAID 5 - serious problem In-Reply-To: <200810151714.RAA23995@sopwith.solgatos.com> References: <8f82c35c0810150532o52ae50b5kef7c685fd23a0af4@mail.gmail.com> <200810151714.RAA23995@sopwith.solgatos.com> Message-ID: <20081015184558.GA84665@icarus.home.lan> On Wed, Oct 15, 2008 at 10:14:42AM +0100, Dieter wrote: > > FreeBSD 7.0-Release > > Intel D975XBX2 motherboard (Intel Matrix Storage Technology) > > 3 WD Raptor 74 GB in a RAID 5 array > > 1 WD Raptor 150 GB as a standalone disk > > / and /var mounted on the standalone,, /usr on the RAID 5 > > I believe what happened was that one of the disks didn't respond for such a > > long time, that is was marked "bad". And afterwards the same thing happened > > for the other disks. When I try to boot the system, all three disks are > > marked "Offline". > > > I am very desperate not to lose my data, > > In that case, step one is to use dd(1) to make a bit-for-bit copy of the > three drives to some trusted media. Since they are marked bad/offline, > you might need to move them to a controller that doesn't know anything > about RAID. (Note that there is risk here, and in almost anything you do > at this point.) Once you have this bit-for-bit backup, you can run any > experiment you like to attempt to recover your data. If the experiment > goes bad, you can dd the exact original contents back using dd, then > try a different experiment. While you're at it, make a normal backup > using dump(8) or whatever you normally use, of / and /var. Once you have > *everything* backed up, you can do risky experiments like booting linux. > > My personal approach to avoiding data loss is (a) avoid buggy things like > inthell and linux. Interesting, being as we have another thread going as of late that seems to link transparent data loss with AMD AM2-based systems with certain models of Adaptec and possibly LSI Logic controller cards. I like Intel as much as I like AMD -- but it's important to remember that it's becoming more and more difficult to provide "flawless" stability on things as the complexities increase. And I have no idea what your beef is with Linux. If the OP is successfully able to bring his array on-line using Linux, I would think that says something about the state of things in FreeBSD, would you agree? Both OSes have their pros and cons. > (b) FFS with softdeps and the disk write cache turned off, This has been fully discussed by developers, particularly Matt Dillon. I can point you to a thread discussing why doing this is not only silly, but a bad idea. And if you'd like, I can show you just how bad the performance is on disks with WC disabled using UFS2 + softupdates. When I say bad, I'm serious -- we're talking horrid. And yes, I have tried it -- see PR 127717 for evidence that I *have* tried it. :-) There *may* be advantages to disabling a disk's write cache when using a hardware RAID controller that offers its own on-board cache (DIMMs, etc.), but that cache should be battery-backed for safety reasons. > (c) full backups. I'm curious what your logic is here too -- this one is debatable, so I'd like to hear your view. > I don't have enough ports to run RAID. :-( The downside is that > FreeBSD doesn't have NCQ support yet (when? when? when?) so writes are > slow. :-( NCQ will not necessarily improve write performance. There have been numerous studies done proving this fact, and I can point you to those as well. TCQ, on the other hand, does offer performance benefits when there are a large number of simultaneous transactions occurring (think: it's more like SCSI's command queueing). I believe Andrey Elsukov is working on getting NCQ support working when AHCI is in use (assuming I remember correctly). -- | 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 freebsd at sopwith.solgatos.com Wed Oct 15 20:30:56 2008 From: freebsd at sopwith.solgatos.com (Dieter) Date: Wed Oct 15 20:31:02 2008 Subject: RAID 5 - serious problem In-Reply-To: Your message of "Wed, 15 Oct 2008 11:45:58 PDT." <20081015184558.GA84665@icarus.home.lan> Message-ID: <200810152028.UAA24285@sopwith.solgatos.com> > > My personal approach to avoiding data loss is (a) avoid buggy things like > > inthell and linux. > > Interesting, being as we have another thread going as of late that seems > to link transparent data loss with AMD AM2-based systems with certain > models of Adaptec and possibly LSI Logic controller cards. This is the SCSI with >= 4 GiB thread? Sounds like an address map problem. > I like Intel as much as I like AMD That is your right. Inthell has a long history of buggy products, attempting to hide/ignore bugs, poor customer support, outright theft, etc. AMD isn't perfect, but the list of bad things is far far shorter. And there are other companies to consider besides just inthell and AMD. > -- but it's important to remember that it's > becoming more and more difficult to provide "flawless" stability on > things as the complexities increase. Computers are complex devices and always have been. Yes this makes it difficult to get everything right. Yet it is possible to achieve very high levels of reliability, better than "5 9s". > And I have no idea what your beef is with Linux. The quality is crap. Endless problems, including scrambled data. > If the OP is > successfully able to bring his array on-line using Linux, I would think > that says something about the state of things in FreeBSD, would you > agree? Both OSes have their pros and cons. It says linux got something right that FreeBSD got wrong. I never said that BSD gets *everything* right, or that linux gets *everything* wrong. > > (b) FFS with softdeps and the disk write cache turned off, > > This has been fully discussed by developers, particularly Matt Dillon. > I can point you to a thread discussing why doing this is not only silly, > but a bad idea. And if you'd like, I can show you just how bad the > performance is on disks with WC disabled using UFS2 + softupdates. When > I say bad, I'm serious -- we're talking horrid. And yes, I have tried > it -- see PR 127717 for evidence that I *have* tried it. :-) I am WELL aware of how bad write performance is on disks with the write cache turned off. I get only about 10% of what the hardware can do, and with large files that is very noticeable. :-( But data integrity is important. > > (c) full backups. > > I'm curious what your logic is here too -- this one is debatable, so I'd > like to hear your view. Things go wrong, and when they do backups are useful. The obvious problem is that a backup quickly becomes out of date as data changes. RAID stays current, but doesn't help with accidental file deletions, in cases where the entire machine dies (fire. flood, etc.), and so on. A proper RAID (that actually helps reliability rather than hurting it) plus off site backups gets you pretty close. A RAID with an off site mirror plus off site backups would be about as reliable as you can get. But if the rate of data changes is high the communication charges could be prohibitive. It all comes down to how important your data is and how much money is available. > NCQ will not necessarily improve write performance. I doubt it will help if you have the disk's write cache turned on. I'm pretty sure it will help with write cache turned off. > I believe Andrey Elsukov is working on getting NCQ support working when > AHCI is in use (assuming I remember correctly). I look forward to having NCQ available. Write performance without it is really pathetic. From koitsu at FreeBSD.org Wed Oct 15 21:16:16 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Wed Oct 15 21:16:22 2008 Subject: RAID 5 - serious problem In-Reply-To: <200810152028.UAA24285@sopwith.solgatos.com> References: <20081015184558.GA84665@icarus.home.lan> <200810152028.UAA24285@sopwith.solgatos.com> Message-ID: <20081015211611.GA88511@icarus.home.lan> On Wed, Oct 15, 2008 at 01:28:43PM +0100, Dieter wrote: > > > My personal approach to avoiding data loss is (a) avoid buggy things like > > > inthell and linux. > > > > Interesting, being as we have another thread going as of late that seems > > to link transparent data loss with AMD AM2-based systems with certain > > models of Adaptec and possibly LSI Logic controller cards. > > This is the SCSI with >= 4 GiB thread? Sounds like an address map > problem. It's the "am2 MBs - 4g + SCSI wipes out root partition" thread. > > I like Intel as much as I like AMD > > That is your right. Inthell has a long history of buggy products, > attempting to hide/ignore bugs, poor customer support, outright > theft, etc. AMD isn't perfect, but the list of bad things is far > far shorter. And there are other companies to consider besides > just inthell and AMD. I'd rather not debate this, as it's off-topic. We can take it up privately if you desire, but keep in mind that my ideal system would be an AMD processor on an Intel chipset board -- but I'll probably be dead by the time that ever happens. Both companies could have much to learn from one another. > > And I have no idea what your beef is with Linux. > > The quality is crap. Endless problems, including scrambled data. I'm not even going to touch this one. > > If the OP is > > successfully able to bring his array on-line using Linux, I would think > > that says something about the state of things in FreeBSD, would you > > agree? Both OSes have their pros and cons. > > It says linux got something right that FreeBSD got wrong. I never said > that BSD gets *everything* right, or that linux gets *everything* > wrong. I don't really consider it an issue of right or wrong; a very different, and unique viewpoint you have! (And I do mean that sincerely) > > > (b) FFS with softdeps and the disk write cache turned off, > > > > This has been fully discussed by developers, particularly Matt Dillon. > > I can point you to a thread discussing why doing this is not only silly, > > but a bad idea. And if you'd like, I can show you just how bad the > > performance is on disks with WC disabled using UFS2 + softupdates. When > > I say bad, I'm serious -- we're talking horrid. And yes, I have tried > > it -- see PR 127717 for evidence that I *have* tried it. :-) > > I am WELL aware of how bad write performance is on disks with the write > cache turned off. I get only about 10% of what the hardware can do, > and with large files that is very noticeable. :-( But data integrity is > important. Your 10% claim is about right. Here's some actual tests I just did (filesystem layer is in the way, but you get the idea): atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f irq 18 at device 31.2 on pci0 ata0: on atapci0 ata0: [ITHREAD] ad0: 114473MB at ata0-master SATA150 testbox# ./atacontrol cap ad0 | grep write write cache yes yes testbox# dd if=/dev/zero of=/usr/testfile bs=1m count=1024 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 20.199726 secs (53156257 bytes/sec) testbox# ./atacontrol wc ad0 off testbox# ./atacontrol cap ad0 | grep write write cache yes no testbox# dd if=/dev/zero of=/usr/testfile bs=1m count=1024 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 155.745314 secs (6894216 bytes/sec) That's about 13% of the full capability. No administrator in their right mind is going to disable WC unless the disks are behind some form of controller that does caching. (For NCQ stuff, see below.) As for the reading material: http://lists.freebsd.org/pipermail/freebsd-stable/2008-September/045495.html http://lists.freebsd.org/pipermail/freebsd-stable/2008-September/045542.html > > > (c) full backups. > > > > I'm curious what your logic is here too -- this one is debatable, so I'd > > like to hear your view. > > Things go wrong, and when they do backups are useful. The obvious problem > is that a backup quickly becomes out of date as data changes. RAID stays > current, but doesn't help with accidental file deletions, in cases > where the entire machine dies (fire. flood, etc.), and so on. A proper > RAID (that actually helps reliability rather than hurting it) plus > off site backups gets you pretty close. A RAID with an off site mirror > plus off site backups would be about as reliable as you can get. But if > the rate of data changes is high the communication charges could be > prohibitive. It all comes down to how important your data is and how > much money is available. Ah sorry, I misinterpreted what you wrote! For some reason I thought you were advocating *not* performing full level-0 backups. :-) > > NCQ will not necessarily improve write performance. > > I doubt it will help if you have the disk's write cache turned on. > I'm pretty sure it will help with write cache turned off. One thing I haven't tested or experimented with is disabling write caching on a drive that has NCQ. Since FreeBSD lacks NCQ right now, we could test this on Linux to see what the I/O difference is (I'm talking purely from a dd or bonnie++ perspective). I can do said testing if need be (on Linux, with disks that do NCQ). > > I believe Andrey Elsukov is working on getting NCQ support working when > > AHCI is in use (assuming I remember correctly). > > I look forward to having NCQ available. Write performance without it > is really pathetic. Hearing you on FM! -- | 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 freebsd at sopwith.solgatos.com Thu Oct 16 00:00:56 2008 From: freebsd at sopwith.solgatos.com (Dieter) Date: Thu Oct 16 00:01:07 2008 Subject: RAID 5 - serious problem In-Reply-To: Your message of "Wed, 15 Oct 2008 14:16:11 PDT." <20081015211611.GA88511@icarus.home.lan> Message-ID: <200810152353.XAA23954@sopwith.solgatos.com> > > > I like Intel as much as I like AMD > > > > That is your right. Inthell has a long history of buggy products, > > attempting to hide/ignore bugs, poor customer support, outright > > theft, etc. AMD isn't perfect, but the list of bad things is far > > far shorter. And there are other companies to consider besides > > just inthell and AMD. > > I'd rather not debate this, as it's off-topic. We can take it up > privately if you desire, but keep in mind that my ideal system would be > an AMD processor on an Intel chipset board -- but I'll probably be dead > by the time that ever happens. Both companies could have much to learn > from one another. Inthell apparently has some good fab people. If they were a designless fab house they might not be on my black list. > No administrator in their > right mind is going to disable WC unless the disks are behind some form > of controller that does caching. (For NCQ stuff, see below.) The only setup I have found that doesn't lose data is FFS+softdep+WC off. So you think I am insane for wanting to not lose data? > > > NCQ will not necessarily improve write performance. > > > > I doubt it will help if you have the disk's write cache turned on. > > I'm pretty sure it will help with write cache turned off. > > One thing I haven't tested or experimented with is disabling write > caching on a drive that has NCQ. Since FreeBSD lacks NCQ right now, we > could test this on Linux to see what the I/O difference is (I'm talking > purely from a dd or bonnie++ perspective). The filesystem may be significant, and last time I looked, linux didn't support FFS r/w. I read something indicating that recent disks do NCQ much better than earlier ones, so "NCQ support" isn't binary. This, and people testing NCQ with the write cache on, could explain the results where NCQ doesn't help. From pluknet at gmail.com Thu Oct 16 13:37:47 2008 From: pluknet at gmail.com (pluknet) Date: Thu Oct 16 13:37:55 2008 Subject: AACRAID Driver v5.2.0 Build 15753 available. Message-ID: Hello. I found that lastest vendor's driver has improvements which could be integrated into the FreeBSD tree. http://www.adaptec.com/en-US/speed/raid/aac/unix/aacraid_freebsd5_b15753_tar_gz.htm wbr, pluknet From koitsu at FreeBSD.org Thu Oct 16 14:47:36 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Thu Oct 16 14:47:43 2008 Subject: AACRAID Driver v5.2.0 Build 15753 available. In-Reply-To: References: Message-ID: <20081016144731.GA12628@icarus.home.lan> On Thu, Oct 16, 2008 at 05:05:05PM +0400, pluknet wrote: > Hello. > > I found that lastest vendor's driver has improvements which could be > integrated into the FreeBSD tree. > > http://www.adaptec.com/en-US/speed/raid/aac/unix/aacraid_freebsd5_b15753_tar_gz.htm > > wbr, > pluknet Can you file a PR on this please? -- | 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 pluknet at gmail.com Thu Oct 16 15:15:24 2008 From: pluknet at gmail.com (pluknet) Date: Thu Oct 16 15:15:31 2008 Subject: AACRAID Driver v5.2.0 Build 15753 available. In-Reply-To: <20081016144731.GA12628@icarus.home.lan> References: <20081016144731.GA12628@icarus.home.lan> Message-ID: 2008/10/16 Jeremy Chadwick : > On Thu, Oct 16, 2008 at 05:05:05PM +0400, pluknet wrote: >> Hello. >> >> I found that lastest vendor's driver has improvements which could be >> integrated into the FreeBSD tree. >> >> http://www.adaptec.com/en-US/speed/raid/aac/unix/aacraid_freebsd5_b15753_tar_gz.htm >> >> wbr, >> pluknet > > Can you file a PR on this please? > Probably, this evening. btw, it works on IBM ServeRAID 8k. wbr, pluknet From pluknet at gmail.com Thu Oct 16 15:24:10 2008 From: pluknet at gmail.com (pluknet) Date: Thu Oct 16 15:24:18 2008 Subject: AACRAID Driver v5.2.0 Build 15753 available. In-Reply-To: References: <20081016144731.GA12628@icarus.home.lan> Message-ID: 2008/10/16 pluknet : > 2008/10/16 Jeremy Chadwick : >> On Thu, Oct 16, 2008 at 05:05:05PM +0400, pluknet wrote: >>> Hello. >>> >>> I found that lastest vendor's driver has improvements which could be >>> integrated into the FreeBSD tree. >>> >>> http://www.adaptec.com/en-US/speed/raid/aac/unix/aacraid_freebsd5_b15753_tar_gz.htm Ouch, of course it should be: http://www.adaptec.com/en-US/speed/raid/aac/unix/aacraid_freebsd6_b15753_tar_gz.htm >> >> Can you file a PR on this please? >> > > Probably, this evening. > btw, it works on IBM ServeRAID 8k. wbr, pluknet From pluknet at gmail.com Thu Oct 16 22:43:13 2008 From: pluknet at gmail.com (pluknet) Date: Thu Oct 16 22:43:19 2008 Subject: AACRAID Driver v5.2.0 Build 15753 available. In-Reply-To: References: <20081016144731.GA12628@icarus.home.lan> Message-ID: 2008/10/16 pluknet : > 2008/10/16 Jeremy Chadwick : >> On Thu, Oct 16, 2008 at 05:05:05PM +0400, pluknet wrote: >>> Hello. >>> >>> I found that lastest vendor's driver has improvements which could be >>> integrated into the FreeBSD tree. >>> >>> http://www.adaptec.com/en-US/speed/raid/aac/unix/aacraid_freebsd5_b15753_tar_gz.htm >> >> Can you file a PR on this please? >> > > Probably, this evening. > btw, it works on IBM ServeRAID 8k. kern/128165. wbr, pluknet From stevefranks at ieee.org Sat Oct 18 00:12:36 2008 From: stevefranks at ieee.org (Steve Franks) Date: Sat Oct 18 00:12:57 2008 Subject: LG combo drive and Attansic Technology ethernet card on Asus P5Q Pro In-Reply-To: <20081014042713.GA39900@icarus.home.lan> References: <20081004034524.GA44662@icarus.home.lan> <200810040649.GAA19778@sopwith.solgatos.com> <20081004073304.GA48931@icarus.home.lan> <20081004073930.GA49756@icarus.home.lan> <20081014042713.GA39900@icarus.home.lan> Message-ID: <539c60b90810171648m39106b4ao28ffa07ea990a639@mail.gmail.com> On Mon, Oct 13, 2008 at 9:27 PM, Jeremy Chadwick wrote: > On Sat, Oct 04, 2008 at 12:39:30AM -0700, Jeremy Chadwick wrote: >> On Sat, Oct 04, 2008 at 12:33:04AM -0700, Jeremy Chadwick wrote: >> > On Fri, Oct 03, 2008 at 11:49:01PM +0100, Dieter wrote: >> > > >> The drive is a new LG combo drive, I believe GH22LP20 or something close to it. >> > > >> > > I have an older LG PATA combo drive which works ok. >> > > >> > > Does it show up when booting? (Does dmesg work from the installation shell?) >> > > >> > > Maybe you need to "kldload atapicam" ? Or is that only needed for writing, >> > > I forget... >> > > >> > > > The only thing I can think of is that the P5Q boards use a Marvell >> > > > ATA/IDE controller (yes, you read that correctly). I wonder if FreeBSD >> > > > somehow lacks support for this... >> > > >> > > 7.0 ata man page claims support for: >> > > >> > > Marvell 88SX5040, 88SX5041, 88SX5080, 88SX5081, 88SX6041, >> > > 88SX6081, 88SX6101, 88SX6141. >> > >> > None of these are what's on the P5Q series boards. The P5Q series >> > boards use a Marvell 88SE6102 Super I/O chip, which also drives IDE/PATA >> > devices. (SATA is driven via ICH10 or ICH10R). >> > >> > I'm left to believe FreeBSD simply lacks support for this very new >> > Marvell chip. I'm willing to bet there is no sign of ata(4) devices nor >> > atapci(4) PCI association during boot-up. >> >> Mac folks are seeing the same problem: >> >> http://forum.insanelymac.com/index.php?showtopic=128985 >> http://www.insanelymac.com/lofiversion/index.php/t99634.html >> >> Wikipedia states the 88SE6121, not the 88SE6102, is used on P5Q series >> boards. But the P5Q SE motherboard manual states it's a 88SE6102. >> >> http://en.wikipedia.org/wiki/List_of_Marvell_Technology_Group_chipsets >> >> So either the motherboard manual is wrong, Wikipedia is wrong, or the >> P5Q SE and P5Q Pro contain different models/versions of ICs. >> >> When I get a P5Q SE for Yong-Hyeon, I'll make note of what's >> silkscreened on the ASIC. > > Yong-Hyeon received my hardware yesterday. Before I shipped it, I > made note of the silkscreening on numerous chips: > > Atheros AR8121-AL1E = GigE NIC + PHY > Marvell 88SE6102-NNC1 = ATA/IDE controller > Nuvoton/Winbond W83667HG-A = Super I/O + hardware monitoring > > -- > | 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" > In a related issue, I've got a L2 (not L1 or L1E) that shows up when I boot PC-BSD, but not with 7.1 prerelease. KDE drove me nuts, though, so I just bought a $15 pci 100T to replace it. Still, I'm suprized that the driver shows up in PC-BSD - perhaps more of a config problem? best, Steve From pyunyh at gmail.com Sat Oct 18 01:01:43 2008 From: pyunyh at gmail.com (Pyun YongHyeon) Date: Sat Oct 18 01:01:50 2008 Subject: LG combo drive and Attansic Technology ethernet card on Asus P5Q Pro In-Reply-To: <539c60b90810171648m39106b4ao28ffa07ea990a639@mail.gmail.com> References: <20081004034524.GA44662@icarus.home.lan> <200810040649.GAA19778@sopwith.solgatos.com> <20081004073304.GA48931@icarus.home.lan> <20081004073930.GA49756@icarus.home.lan> <20081014042713.GA39900@icarus.home.lan> <539c60b90810171648m39106b4ao28ffa07ea990a639@mail.gmail.com> Message-ID: <20081018005938.GA31303@cdnetworks.co.kr> On Fri, Oct 17, 2008 at 04:48:34PM -0700, Steve Franks wrote: [...] > In a related issue, I've got a L2 (not L1 or L1E) that shows up when I > boot PC-BSD, but not with 7.1 prerelease. KDE drove me nuts, though, > so I just bought a $15 pci 100T to replace it. Still, I'm suprized > that the driver shows up in PC-BSD - perhaps more of a config problem? > stas@ committed ae(4) to HEAD but it was not MFCed to stable/7 yet. I'm not sure where PC-BSD got L2 driver but stas may have more information on MFC. CCed to Stanislav Sedov. -- Regards, Pyun YongHyeon From stas at FreeBSD.org Sat Oct 18 11:06:14 2008 From: stas at FreeBSD.org (Stanislav Sedov) Date: Sat Oct 18 11:06:20 2008 Subject: LG combo drive and Attansic Technology ethernet card on Asus P5Q Pro In-Reply-To: <20081018005938.GA31303@cdnetworks.co.kr> References: <20081004034524.GA44662@icarus.home.lan> <200810040649.GAA19778@sopwith.solgatos.com> <20081004073304.GA48931@icarus.home.lan> <20081004073930.GA49756@icarus.home.lan> <20081014042713.GA39900@icarus.home.lan> <539c60b90810171648m39106b4ao28ffa07ea990a639@mail.gmail.com> <20081018005938.GA31303@cdnetworks.co.kr> Message-ID: <20081018143219.f68287e3.stas@FreeBSD.org> On Sat, 18 Oct 2008 09:59:38 +0900 Pyun YongHyeon mentioned: > On Fri, Oct 17, 2008 at 04:48:34PM -0700, Steve Franks wrote: > > [...] > > In a related issue, I've got a L2 (not L1 or L1E) that shows up when I > > boot PC-BSD, but not with 7.1 prerelease. KDE drove me nuts, though, > > so I just bought a $15 pci 100T to replace it. Still, I'm suprized > > that the driver shows up in PC-BSD - perhaps more of a config problem? > > > > stas@ committed ae(4) to HEAD but it was not MFCed to stable/7 yet. > I'm not sure where PC-BSD got L2 driver but stas may have more > information on MFC. CCed to Stanislav Sedov. > I've requested the MFC but haven't got a reply from re@ yet. So not sure if they'll agree for MFC or not. -- Stanislav Sedov ST4096-RIPE -------------- 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/20081018/2b827711/attachment.pgp From kungfujesus06 at gmail.com Sun Oct 19 01:00:00 2008 From: kungfujesus06 at gmail.com (Adam Stylinski) Date: Sun Oct 19 01:00:07 2008 Subject: Will the following work in FreeBSD7? Message-ID: <96af083b0810181759t2320098dt7b1b00127e0b7013@mail.gmail.com> http://www.newegg.com/Product/Product.aspx?Item=N82E16816103058 It appears to have the identical marvell based SATA controller on it as my Rosewill RC-218, which doesn't appear to be working with FreeBSD7. Does anyone have any more information to offer? And if it doesn't work with the latest kernel, does anybody know of a 4 port SATA controller that's <=120.00USD that operates on PCI-Express and is compatible with FreeBSD? From ltning at anduin.net Mon Oct 20 06:39:58 2008 From: ltning at anduin.net (=?ISO-8859-1?Q?Eirik_=D8verby?=) Date: Mon Oct 20 06:40:05 2008 Subject: FreeBSD-AMD64 on Xeon MP Message-ID: <6D397584-2B6B-4F1A-B5C4-2A7B77AE52EB@anduin.net> Hi, > > Hi all, > > > > I try to run FreeBSD-7-AMD64 on a Quad Xeon (Xeon MP 7320) and > 32GB RAM. > > The Board is a X7QC3 by supermicro and the installation is done on > > another system, updated and plugged to this system. So I have a > drive > > with 7-STABLE compiled today. > > > > The last line I see from dmesg is vga0- then the system freezes. > > > > Anyone using a similar configuration or knows what could be wrong? I > > still have some days left to play with it, before this box gets > shipped > > to the customer. > > This looks very, very similar to what I had once, on similar hardware > (4x Xeon 7xxx, SuperMicro). I didn't find a solution and didn't bother > since the box isn't intended for FreeBSD. I did find (by accident) a > curious workaround: I booted Linux (I used Ubuntu 8.04 amd64 LiveCD - > just to boot it, without installing), then rebooted and booted > FreeBSD - > worked every time, but it's obviously not a long-term solution. If you > can also verify that this "solves" the problem, then someone might > work > with you to produce a patch. I just received four such servers, all intended for FreeBSD.... And I'm seeing exactly the same problem. I'm going to try booting Linux and then back into FreeBSD, but it's obviously not a solution. Anyone who might want to work on this can have a box like this to work on via remote KVM (including remote boot media capability) any time. I'm going to go poke the supplier and Supermicro for some updated firmware. Any progress on your end? Some additional info: Safe mode boot gets a bit further, to the point where it tries to mount/read from /dev/md0, but then hangs hard. /Eirik From krassi at bulinfo.net Mon Oct 20 14:22:17 2008 From: krassi at bulinfo.net (Krassimir Slavchev) Date: Mon Oct 20 14:22:25 2008 Subject: Controlling NIC bandwidth via IFG? Message-ID: <48FC8CCB.9050906@bulinfo.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello All, I am looking for a NIC (supported by FreeBSD) which has ability to set IFG (Inter Frame Gap) bigger than default (960ns for 100Mbit/s, 96ns for 1Gbit/s). I would like to decrease the NIC bandwidth (burst rate) using this way to ~40Mbit/s. Best Regards -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFI/IzLxJBWvpalMpkRAkovAJ0WrckKEPNeYU4JpfCpng3hHMMN/ACfU3ax Ys3jzyKkhhTRlnfw782zGUI= =fefr -----END PGP SIGNATURE----- From stevefranks at ieee.org Mon Oct 20 17:18:52 2008 From: stevefranks at ieee.org (Steve Franks) Date: Mon Oct 20 17:18:59 2008 Subject: sata hotswap on Intel ICH7 Message-ID: <539c60b90810201018v455513a0tdc97d7465e6623c3@mail.gmail.com> Just curious if this works, what I need to do, etc, good/bad experiences... Since I'm actually talking about internal drives, does cabling matter, is the power supposed to mate before/after data, etc? Doesn't seem to be much on the subject in the handbook or man atacontrol. I assume we've had scsi hotswapping for quite some time, right? Best, Steve From koitsu at FreeBSD.org Mon Oct 20 17:25:17 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Mon Oct 20 17:25:24 2008 Subject: sata hotswap on Intel ICH7 In-Reply-To: <539c60b90810201018v455513a0tdc97d7465e6623c3@mail.gmail.com> References: <539c60b90810201018v455513a0tdc97d7465e6623c3@mail.gmail.com> Message-ID: <20081020172515.GA8705@icarus.home.lan> On Mon, Oct 20, 2008 at 10:18:50AM -0700, Steve Franks wrote: > Just curious if this works, what I need to do, etc, good/bad > experiences... Since I'm actually talking about internal drives, does > cabling matter, is the power supposed to mate before/after data, etc? Hot-swapping on SATA requires an actual hot-swap-capable SATA backplane. You *cannot* just "yank a disk out of a PC" by removing the SATA data or power cable. It also requires that you be using SATA in "Enhanced" mode, or under AHCI. Using SATA in "Emulation" or "Compatible" mode (e.g. a 2-channel SATA controller will assign disks as ata0-master and ata0-slave) will not work how you expect. AHCI is preferred, if available. Assuming you meet these criteria, all you need to do on FreeBSD is: - Unmount any filesystems using the disk (you may need to shut down or kill off processes using files on those filesystems before you can unmount). If you forget to do this, you will panic the box. - atacontrol list, and determine what channel to detach (E.g. ata0) - atacontrol detach - Kernel should show the disk disappearing. - Remove disk from machine, replace with new disk. - Wait for disk to spin up (sometimes the drive LEDs will be lit; wait for them to turn off) - atacontrol attach And that's all. Note that there are known problems with this when using BIOS-level RAID methods such as Intel MatrixRAID, so please do not use those. > Doesn't seem to be much on the subject in the handbook or man > atacontrol. You can file a PR to get this added, if you'd like. :-) > I assume we've had scsi hotswapping for quite some time, right? Correct, but it requires similar hardware as above. SCA drives, for example, are hot-swappable, while yanking a drive off a LVD cable will probably not do what you expect. camcontrol(8) is the utility you want to use for all that. -- | 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 stevefranks at ieee.org Mon Oct 20 18:09:20 2008 From: stevefranks at ieee.org (Steve Franks) Date: Mon Oct 20 18:09:27 2008 Subject: sata hotswap on Intel ICH7 In-Reply-To: <20081020172515.GA8705@icarus.home.lan> References: <539c60b90810201018v455513a0tdc97d7465e6623c3@mail.gmail.com> <20081020172515.GA8705@icarus.home.lan> Message-ID: <539c60b90810201109t4504d87dy727220c6663a4281@mail.gmail.com> > It also requires that you be using SATA in "Enhanced" mode, or under > AHCI. Using SATA in "Emulation" or "Compatible" mode (e.g. a 2-channel > SATA controller will assign disks as ata0-master and ata0-slave) will > not work how you expect. AHCI is preferred, if available. Ok, I followed the rest, but is the part above a function of the bios, the hardware, a sysctl, or what? Sounds like bios, I'll have a look... Thanks, Steve From koitsu at FreeBSD.org Mon Oct 20 18:11:21 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Mon Oct 20 18:11:27 2008 Subject: sata hotswap on Intel ICH7 In-Reply-To: <539c60b90810201109t4504d87dy727220c6663a4281@mail.gmail.com> References: <539c60b90810201018v455513a0tdc97d7465e6623c3@mail.gmail.com> <20081020172515.GA8705@icarus.home.lan> <539c60b90810201109t4504d87dy727220c6663a4281@mail.gmail.com> Message-ID: <20081020181119.GA9777@icarus.home.lan> On Mon, Oct 20, 2008 at 11:09:19AM -0700, Steve Franks wrote: > > It also requires that you be using SATA in "Enhanced" mode, or under > > AHCI. Using SATA in "Emulation" or "Compatible" mode (e.g. a 2-channel > > SATA controller will assign disks as ata0-master and ata0-slave) will > > not work how you expect. AHCI is preferred, if available. > > Ok, I followed the rest, but is the part above a function of the bios, > the hardware, a sysctl, or what? Sounds like bios, I'll have a > look... Yep, this would be in the BIOS. Sorry I didn't specify, my bad. :-) -- | 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 scheidell at secnap.net Tue Oct 21 14:36:10 2008 From: scheidell at secnap.net (Michael Scheidell) Date: Tue Oct 21 14:36:16 2008 Subject: kern/127391: [ata] Intel 6300ESB SATA150 cannot find disk and boot under 6.3 [regression] In-Reply-To: <20081004064515.GA48654@icarus.home.lan> References: <48E66ACE.7060702@secnap.net> <20081004064515.GA48654@icarus.home.lan> Message-ID: <48FDE8E0.2030509@secnap.net> More information: I have a dmidecode, dmesg.boot and pciconf from A) old dell 750 (using a 6.3 kernel that we got to work by accident, don't remember how) B) new dell 750 that will boot anything. Biggest different seems to be a different motherboard. new one doesn't have an acpi apci bios, has a dual core cpu, old one has hyperthread cpu. I can build any kernel I want on the newer dell 750, it will boot just about anything. three different kernels that booted on new dell won't boot on old one. kernel that boots on old one, will boot on new one. I will upload. as a reminder, all systems, up and including freebsd 5.5 and 6.2 booted on all of these. A 'fix' somewhere in 6.3 broke the pci bridge? sata controller? disk init? 7.0 didn't fix it either, so whatever was changed was changed in 7.0 also. another reminder, and explanation. Several months ago, when investigating this, looking at a lot of problems documented and found by google, one of our techs came across a fix. we have a 6.3 kernel with that fix it it, but tech did not document it, and we have not been able to find fix or reproduce fix. -- Michael Scheidell, CTO Phone: 561-999-5000, x 1259 > *| *SECNAP Network Security Corporation * Certified SNORT Integrator * King of Spam Filters, SC Magazine 2008 * Information Security Award 2008, Info Security Products Guide * CRN Magazine Top 40 Emerging Security Vendors _________________________________________________________________________ This email has been scanned and certified safe by SpammerTrap(r). For Information please see http://www.spammertrap.com _________________________________________________________________________ From scheidell at secnap.net Wed Oct 22 15:03:55 2008 From: scheidell at secnap.net (Michael Scheidell) Date: Wed Oct 22 15:04:07 2008 Subject: fixed, maybe: Re: kern/127391: [ata] Intel 6300ESB SATA150 cannot find disk and boot under 6.3 [regression] In-Reply-To: <48FDE8E0.2030509@secnap.net> References: <48E66ACE.7060702@secnap.net> <20081004064515.GA48654@icarus.home.lan> <48FDE8E0.2030509@secnap.net> Message-ID: <48FF40E1.80708@secnap.net> i think its the acpi module. you have to build it in the kernel, you have to make SURE you build it in kernel. if you delete all the modules rm /boot/modules and you DON'T BUILD THE MODULES AT ALL, OR ERASE THEM WHEN DONE, and put device acpi in kernel, it should work. I will complete testing. -- Michael Scheidell, CTO Phone: 561-999-5000, x 1259 > *| *SECNAP Network Security Corporation * Certified SNORT Integrator * King of Spam Filters, SC Magazine 2008 * Information Security Award 2008, Info Security Products Guide * CRN Magazine Top 40 Emerging Security Vendors _________________________________________________________________________ This email has been scanned and certified safe by SpammerTrap(r). For Information please see http://www.spammertrap.com _________________________________________________________________________ From mcdouga9 at egr.msu.edu Sat Oct 25 21:48:01 2008 From: mcdouga9 at egr.msu.edu (Adam McDougall) Date: Sat Oct 25 21:48:08 2008 Subject: Request for testers: Option 3G cards, also Sierra, Huawei and Novatel In-Reply-To: <200810092344.10388.nick@van-laarhoven.org> References: <200810092344.10388.nick@van-laarhoven.org> Message-ID: <20081025212935.GV61867@egr.msu.edu> Seems to work fine with my Novatel V740 (EVDO from Verizon) Expresscard. I'm using the latest version with the bufsize patch and I'm glad I no longer have to hack in a patch to get relatively fast speeds through it (just got 140kB/sec in a test which is just over 1Mbit/sec). On Thu, Oct 09, 2008 at 11:44:09PM +0200, Nick Hibma wrote: Just now I have committed a driver for Option and Huawei cards previously supported by the ubsa driver. More information is in the commit message. I am looking for people who would be able to provide more information after testing with the 3G cards branded by: OEM: Merlin Huawei Option Sierra Novatel Qualcomm Rebranded: Dell Vodafone Note: The driver can be copied across to FreeBSD 7-STABLE if you copy the sys/modules/u3g directory and sys/dev/usb/u3g.c and sys/dev/usb/usbdevs files from HEAD and _move_ the ID from ubsa to u3g. More information can be found on http://people.freebsd.org/~n_hibma/u3g.html Thanks, Nick ---------- Forwarded Message ---------- Subject: svn commit: r183735 - in head: share/man/man4 sys/conf sys/dev/usb sys/i386/conf sys/modules sys/modules/u3g Date: Thu October 9 2008 From: Nick Hibma To: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Author: n_hibma Date: Thu Oct 9 21:25:01 2008 New Revision: 183735 URL: http://svn.freebsd.org/changeset/base/183735 Log: Say hello to the u3g driver, implementing support for 3G modems. This was located in the ubsa driver, but should be moved into a separate driver: - 3G modems provide multiple serial ports to allow AT commands while the PPP connection is up. - 3G modems do not provide baud rate or other serial port settings. - Huawei cards need specific initialisation. - ubsa is for Belkin adapters, an Linuxy choice for another device like 3G. Speeds achieved here with a weak signal at best is ~40kb/s (UMTS). No spooky STALLED messages as well. Next: Move over all entries for Sierra and Novatel cards once I have found testers, and implemented serial port enumeration for Sierra (or rather have Andrea Guzzo do it). They list all endpoints in 1 iface instead of 4 ifaces. Submitted by: aguzzo@anywi.com MFC after: 3 weeks Added: head/share/man/man4/u3g.4 (contents, props changed) head/sys/dev/usb/u3g.c (contents, props changed) head/sys/modules/u3g/ head/sys/modules/u3g/Makefile (contents, props changed) Modified: head/share/man/man4/Makefile head/sys/conf/NOTES head/sys/conf/files head/sys/dev/usb/ubsa.c head/sys/dev/usb/usbdevs head/sys/i386/conf/GENERIC head/sys/modules/Makefile Modified: head/share/man/man4/Makefile ============================================================================== --- head/share/man/man4/Makefile Thu Oct 9 20:51:25 2008 (r183734) +++ head/share/man/man4/Makefile Thu Oct 9 21:25:01 2008 (r183735) @@ -384,6 +384,7 @@ MAN= aac.4 \ twe.4 \ tx.4 \ txp.4 \ + u3g.4 \ uark.4 \ uart.4 \ ubsa.4 \ Added: head/share/man/man4/u3g.4 ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/share/man/man4/u3g.4 Thu Oct 9 21:25:01 2008 (r183735) @@ -0,0 +1,100 @@ +.\" +.\" Copyright (c) 2008 AnyWi Technologies +.\" All rights reserved. +.\" +.\" This code is derived from uark.c +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.\" $FreeBSD$ +.\" +.Dd October 7, 2008 +.Dt U3G 4 +.Os +.Sh NAME +.Nm u3g +.Nd USB support for 3G datacards +.Sh SYNOPSIS +To compile this driver into the kernel, +place the following lines in your +kernel configuration file: +.Bd -ragged -offset indent +.Cd "device u3g" +.Cd "device ucom" +.Ed +.Pp +Alternatively, to load the driver as a +module at boot time, place the following line in +.Xr loader.conf 5 : +.Bd -literal -offset indent +u3g_load="YES" +.Ed +.Sh DESCRIPTION +The +.Nm +driver provides support for the multiple USB-to-serial interfaces exposed by +many 3G usb/pccard modems. +.Pp +The device is accessed through the +.Xr ucom 4 +driver which makes it behave like a +.Xr tty 4 . +.Sh HARDWARE +The +.Nm +driver supports the following adapters: +.Pp +.Bl -bullet -compact +.It +Option Globetrotter 3G Fusion (only 3G part, not WLAN) +.It +Option Globetrotter 3G Fusion Quad (only 3G part, not WLAN) +.It +Option Globetrotter 3G Quad +.It +Option Globetrotter 3G +.It +Vodafone Mobile Connect Card 3G +.It +Huawei E220 (E270?) +.It +Huawei Mobile +.El +.Pp +The supported 3G cards provide the necessary modem port for ppp, +pppd, or mpd connections as well as extra ports (depending on the specific +device) to provide other functions (diagnostic port, SIM toolkit port) +.Sh SEE ALSO +.Xr tty 4 , +.Xr ucom 4 , +.Xr usb 4 , +.Xr ubsa 4 +.Sh HISTORY +The +.Nm +driver +appeared in +.Fx 7.0 . +The +.Xr ubsa 4 +manual page was modified for +.Nm +by +.An Andrea Guzzo Aq aguzzo@anywi.com +in September 2008. +.Sh AUTHORS +The +.Nm +driver was written by +.An Andrea Guzzo Aq aguzzo@anywi.com . +Hardware for testing provided by AnyWi Technologies, Leiden, NL. Modified: head/sys/conf/NOTES ============================================================================== --- head/sys/conf/NOTES Thu Oct 9 20:51:25 2008 (r183734) +++ head/sys/conf/NOTES Thu Oct 9 21:25:01 2008 (r183735) @@ -2416,6 +2416,8 @@ device uscanner # # USB serial support device ucom +# USB support for 3G modem cards by Option, Huawei and Sierra +device u3g # USB support for Technologies ARK3116 based serial adapters device uark # USB support for Belkin F5U103 and compatible serial adapters @@ -2441,7 +2443,6 @@ device aue # ASIX Electronics AX88172 USB 2.0 ethernet driver. Used in the # LinkSys USB200M and various other adapters. - device axe # Modified: head/sys/conf/files ============================================================================== --- head/sys/conf/files Thu Oct 9 20:51:25 2008 (r183734) +++ head/sys/conf/files Thu Oct 9 21:25:01 2008 (r183735) @@ -1327,6 +1327,7 @@ dev/usb/ohci_pci.c optional ohci pci dev/usb/sl811hs.c optional slhci dev/usb/slhci_pccard.c optional slhci pccard dev/usb/uark.c optional uark +dev/usb/u3g.c optional u3g dev/usb/ubsa.c optional ubsa dev/usb/ubser.c optional ubser dev/usb/ucom.c optional ucom Added: head/sys/dev/usb/u3g.c ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/sys/dev/usb/u3g.c Thu Oct 9 21:25:01 2008 (r183735) @@ -0,0 +1,330 @@ +/* + * Copyright (c) 2008 AnyWi Technologies + * Author: Andrea Guzzo + * * based on uark.c 1.1 2006/08/14 08:30:22 jsg * + * * parts from ubsa.c 183348 2008-09-25 12:00:56Z phk * + * + * Permission to use, copy, modify, and distribute this software for any + * purpose with or without fee is hereby granted, provided that the above + * copyright notice and this permission notice appear in all copies. + * + * THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES + * WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF + * MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR + * ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES + * WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN + * ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF + * OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. + * + * $FreeBSD$ + */ + +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include + +#include +#include +#include + +#include + +#include "usbdevs.h" + +#ifdef U3G_DEBUG +#define DPRINTFN(n, x) do { if (u3gdebug > (n)) printf x; } while (0) +int u3gtebug = 0; +#else +#define DPRINTFN(n, x) +#endif +#define DPRINTF(x) DPRINTFN(0, x) + +#define U3GBUFSZ 1024 +#define U3G_MAXPORTS 4 + +struct u3g_softc { + struct ucom_softc sc_ucom[U3G_MAXPORTS];; + device_t sc_dev; + usbd_device_handle sc_udev; + u_char sc_msr; + u_char sc_lsr; + u_char numports; + + usbd_interface_handle sc_intr_iface; /* interrupt interface */ +#ifdef U3G_DEBUG + int sc_intr_number; /* interrupt number */ + usbd_pipe_handle sc_intr_pipe; /* interrupt pipe */ + u_char *sc_intr_buf; /* interrupt buffer */ +#endif + int sc_isize; +}; + +struct ucom_callback u3g_callback = { + NULL, + NULL, + NULL, + NULL, + NULL, + NULL, + NULL, + NULL, +}; + +static const struct usb_devno u3g_devs[] = { + /* OEM: Option */ + { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GT3G }, + { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GT3GQUAD }, + { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GT3GPLUS }, + { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GTMAX36 }, + { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_VODAFONEMC3G }, + /* OEM: Huawei */ + { USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_MOBILE }, + { USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E220 }, + + { 0, 0 } +}; + +#ifdef U3G_DEBUG +static void +u3g_intr(usbd_xfer_handle xfer, usbd_private_handle priv, usbd_status status) +{ + struct u3g_softc *sc = (struct u3g_softc *)priv; + device_printf(sc->sc_dev, "INTERRUPT CALLBACK\n"); +} +#endif + +static int +u3g_huawei_reinit(usbd_device_handle dev) +{ + /* The Huawei device presents itself as a umass device with Windows + * drivers on it. After installation of the driver, it reinits into a + * 3G serial device. + */ + usb_device_request_t req; + usb_config_descriptor_t *cdesc; + + /* Get the config descriptor */ + cdesc = usbd_get_config_descriptor(dev); + if (cdesc == NULL) + return (UMATCH_NONE); + + /* One iface means umass mode, more than 1 (4 usually) means 3G mode */ + if (cdesc->bNumInterface > 1) + return (UMATCH_VENDOR_PRODUCT); + + req.bmRequestType = UT_WRITE_DEVICE; + req.bRequest = UR_SET_FEATURE; + USETW(req.wValue, UF_DEVICE_REMOTE_WAKEUP); + USETW(req.wIndex, UHF_PORT_SUSPEND); + USETW(req.wLength, 0); + + (void) usbd_do_request(dev, &req, 0); + + return UMATCH_NONE; /* mismatch; it will be gone and reappear */ +} + +static int +u3g_match(device_t self) +{ + struct usb_attach_arg *uaa = device_get_ivars(self); + + if (uaa->iface != NULL) + return (UMATCH_NONE); + + if (uaa->vendor == USB_VENDOR_HUAWEI) + return u3g_huawei_reinit(uaa->device); + + if (usb_lookup(u3g_devs, uaa->vendor, uaa->product)) + return UMATCH_VENDOR_PRODUCT; + + return UMATCH_NONE; +} + +static int +u3g_attach(device_t self) +{ + struct u3g_softc *sc = device_get_softc(self); + struct usb_attach_arg *uaa = device_get_ivars(self); + usbd_device_handle dev = uaa->device; + usbd_interface_handle iface; + usb_interface_descriptor_t *id; + usb_endpoint_descriptor_t *ed; + usbd_status error; + int i, n; + usb_config_descriptor_t *cdesc; + struct ucom_softc *ucom = NULL; + char devnamefmt[32]; + + sc->sc_dev = self; +#ifdef DEBUG + sc->sc_intr_number = -1; + sc->sc_intr_pipe = NULL; +#endif + /* Move the device into the configured state. */ + error = usbd_set_config_index(dev, 1, 1); + if (error) { + device_printf(self, "failed to set configuration: %s\n", + usbd_errstr(error)); + goto bad; + } + + /* get the config descriptor */ + cdesc = usbd_get_config_descriptor(dev); + + if (cdesc == NULL) { + device_printf(self, "failed to get configuration descriptor\n"); + goto bad; + } + + sc->sc_udev = dev; + sc->numports = (cdesc->bNumInterface <= U3G_MAXPORTS)?cdesc->bNumInterface:U3G_MAXPORTS; + for ( i = 0; i < sc->numports; i++ ) { + ucom = &sc->sc_ucom[i]; + + ucom->sc_dev = self; + ucom->sc_udev = dev; + error = usbd_device2interface_handle(dev, i, &iface); + if (error) { + device_printf(ucom->sc_dev, + "failed to get interface, err=%s\n", + usbd_errstr(error)); + ucom->sc_dying = 1; + goto bad; + } + id = usbd_get_interface_descriptor(iface); + ucom->sc_iface = iface; + + ucom->sc_bulkin_no = ucom->sc_bulkout_no = -1; + for (n = 0; n < id->bNumEndpoints; n++) { + ed = usbd_interface2endpoint_descriptor(iface, n); + if (ed == NULL) { + device_printf(ucom->sc_dev, + "could not read endpoint descriptor\n"); + goto bad; + } + if (UE_GET_DIR(ed->bEndpointAddress) == UE_DIR_IN && + UE_GET_XFERTYPE(ed->bmAttributes) == UE_BULK) + ucom->sc_bulkin_no = ed->bEndpointAddress; + else if (UE_GET_DIR(ed->bEndpointAddress) == UE_DIR_OUT && + UE_GET_XFERTYPE(ed->bmAttributes) == UE_BULK) + ucom->sc_bulkout_no = ed->bEndpointAddress; + } + if (ucom->sc_bulkin_no == -1 || ucom->sc_bulkout_no == -1) { + device_printf(ucom->sc_dev, "missing endpoint\n"); + goto bad; + } + ucom->sc_parent = sc; + ucom->sc_ibufsize = U3GBUFSZ; + ucom->sc_obufsize = U3GBUFSZ; + ucom->sc_ibufsizepad = U3GBUFSZ; + ucom->sc_opkthdrlen = 0; + + ucom->sc_callback = &u3g_callback; + + sprintf(devnamefmt,"U%d.%%d", device_get_unit(self)); + DPRINTF(("u3g: in=0x%x out=0x%x, devname=%s\n", + ucom->sc_bulkin_no, ucom->sc_bulkout_no, devnamefmt)); +#if __FreeBSD_version < 800000 + ucom_attach_tty(ucom, TS_CALLOUT, devnamefmt, i); +#else + ucom_attach_tty(ucom, devnamefmt, i); +#endif + } +#ifdef U3G_DEBUG + if (sc->sc_intr_number != -1 && sc->sc_intr_pipe == NULL) { + sc->sc_intr_buf = malloc(sc->sc_isize, M_USBDEV, M_WAITOK); + error = usbd_open_pipe_intr(sc->sc_intr_iface, + sc->sc_intr_number, + USBD_SHORT_XFER_OK, + &sc->sc_intr_pipe, + sc, + sc->sc_intr_buf, + sc->sc_isize, + u3g_intr, + 100); + if (error) { + device_printf(self, + "cannot open interrupt pipe (addr %d)\n", + sc->sc_intr_number); + goto bad; + } + } +#endif + device_printf(self, "configured %d serial ports (/dev/cuaU%d.X)", + sc->numports, device_get_unit(self)); + + return 0; + +bad: + DPRINTF(("u3g_attach: ATTACH ERROR\n")); + ucom->sc_dying = 1; + return ENXIO; +} + +static int +u3g_detach(device_t self) +{ + struct u3g_softc *sc = device_get_softc(self); + int rv = 0; + int i; + + DPRINTF(("u3g_detach: sc=%p\n", sc)); + + for (i = 0; i < sc->numports; i++) { + if(sc->sc_ucom[i].sc_udev) { + sc->sc_ucom[i].sc_dying = 1; + rv = ucom_detach(&sc->sc_ucom[i]); + if(rv != 0) { + device_printf(self, "Can't deallocat port %d", i); + return rv; + } + } + } + +#ifdef U3G_DEBUG + if (sc->sc_intr_pipe != NULL) { + int err = usbd_abort_pipe(sc->sc_intr_pipe); + if (err) + device_printf(self, + "abort interrupt pipe failed: %s\n", + usbd_errstr(err)); + err = usbd_close_pipe(sc->sc_intr_pipe); + if (err) + device_printf(self, + "close interrupt pipe failed: %s\n", + usbd_errstr(err)); + free(sc->sc_intr_buf, M_USBDEV); + sc->sc_intr_pipe = NULL; + } +#endif + + return 0; +} + +static device_method_t u3g_methods[] = { + /* Device interface */ + DEVMETHOD(device_probe, u3g_match), + DEVMETHOD(device_attach, u3g_attach), + DEVMETHOD(device_detach, u3g_detach), + + { 0, 0 } +}; + +static driver_t u3g_driver = { + "ucom", + u3g_methods, + sizeof (struct u3g_softc) +}; + +DRIVER_MODULE(u3g, uhub, u3g_driver, ucom_devclass, usbd_driver_load, 0); +MODULE_DEPEND(u3g, usb, 1, 1, 1); +MODULE_DEPEND(u3g, ucom, UCOM_MINVER, UCOM_PREFVER, UCOM_MAXVER); Modified: head/sys/dev/usb/ubsa.c ============================================================================== --- head/sys/dev/usb/ubsa.c Thu Oct 9 20:51:25 2008 (r183734) +++ head/sys/dev/usb/ubsa.c Thu Oct 9 21:25:01 2008 (r183735) @@ -161,8 +161,6 @@ SYSCTL_INT(_hw_usb_ubsa, OID_AUTO, debug struct ubsa_softc { struct ucom_softc sc_ucom; - int sc_huawei; - int sc_iface_number; /* interface number */ usbd_interface_handle sc_intr_iface; /* interrupt interface */ @@ -228,24 +226,11 @@ static const struct ubsa_product { { USB_VENDOR_GOHUBS, USB_PRODUCT_GOHUBS_GOCOM232 }, /* Peracom */ { USB_VENDOR_PERACOM, USB_PRODUCT_PERACOM_SERIAL1 }, - /* Dell version of the Novatel 740 */ - { USB_VENDOR_DELL, USB_PRODUCT_DELL_U740 }, - /* Option Vodafone MC3G */ - { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_VODAFONEMC3G }, - /* Option GlobeTrotter 3G */ - { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GT3G }, - /* Option GlobeTrotter 3G QUAD */ - { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GT3GQUAD }, - /* Option GlobeTrotter 3G+ */ - { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GT3GPLUS }, - /* Option GlobeTrotter Max 3.6 */ - { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GTMAX36 }, - /* Huawei Mobile */ - { USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_MOBILE }, - { USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E270 }, + /* Merlin */ { USB_VENDOR_MERLIN, USB_PRODUCT_MERLIN_V620 }, /* Qualcomm, Inc. ZTE CDMA */ { USB_VENDOR_QUALCOMMINC, USB_PRODUCT_QUALCOMMINC_CDMA_MSM }, + /* Novatel */ { USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_CDMA_MODEM }, /* Novatel Wireless Merlin ES620 */ { USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_ES620 }, @@ -256,6 +241,8 @@ static const struct ubsa_product { /* Novatel Wireless Merlin U740 */ { USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_U740 }, { USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_U740_2 }, + /* Dell version of the Novatel 740 */ + { USB_VENDOR_DELL, USB_PRODUCT_DELL_U740 }, /* Novatel Wireless Merlin U950D */ { USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_U950D }, /* Novatel Wireless Merlin V620 */ @@ -341,52 +328,6 @@ MODULE_DEPEND(ubsa, usb, 1, 1, 1); MODULE_DEPEND(ubsa, ucom, UCOM_MINVER, UCOM_PREFVER, UCOM_MAXVER); MODULE_VERSION(ubsa, UBSA_MODVER); -/* - * Huawei Exxx radio devices have a built in flash disk which is their - * default power up configuration. This allows the device to carry its - * own installation software. - * - * Instead of following the USB spec, and create multiple configuration - * descriptors for this, the devices expects the driver to send - * UF_DEVICE_REMOTE_WAKEUP to endpoint 2 to reset the device, so it - * reprobes, now with the radio exposed. - */ - -static usbd_status -ubsa_huawei(device_t self, struct usb_attach_arg *uaa) { - usb_device_request_t req; usbd_device_handle dev; - usb_config_descriptor_t *cdesc; - - if (self == NULL) - return (UMATCH_NONE); - if (uaa == NULL) - return (UMATCH_NONE); - dev = uaa->device; - if (dev == NULL) - return (UMATCH_NONE); - /* get the config descriptor */ - cdesc = usbd_get_config_descriptor(dev); - if (cdesc == NULL) - return (UMATCH_NONE); - - if (cdesc->bNumInterface > 1) - return (0); - - /* Bend it like Beckham */ - device_printf(self, "Kicking Huawei device into radio mode\n"); - memset(&req, 0, sizeof req); - req.bmRequestType = UT_WRITE_DEVICE; - req.bRequest = UR_SET_FEATURE; - USETW(req.wValue, UF_DEVICE_REMOTE_WAKEUP); - USETW(req.wIndex, 2); - USETW(req.wLength, 0); - - /* We get error return, but it works */ - (void)usbd_do_request(dev, &req, 0); - return (UMATCH_NONE); -} - - static int ubsa_match(device_t self) { @@ -399,9 +340,6 @@ ubsa_match(device_t self) for (i = 0; ubsa_products[i].vendor != 0; i++) { if (ubsa_products[i].vendor == uaa->vendor && ubsa_products[i].product == uaa->product) { - if (uaa->vendor == USB_VENDOR_HUAWEI && - ubsa_huawei(self, uaa)) - break; return (UMATCH_VENDOR_PRODUCT); } } @@ -424,9 +362,6 @@ ubsa_attach(device_t self) dev = uaa->device; ucom = &sc->sc_ucom; - if (uaa->vendor == USB_VENDOR_HUAWEI) - sc->sc_huawei = 1; - /* * initialize rts, dtr variables to something * different from boolean 0, 1 @@ -575,8 +510,6 @@ ubsa_request(struct ubsa_softc *sc, u_in usbd_status err; /* The huawei Exxx devices support none of these tricks */ - if (sc->sc_huawei) - return (0); req.bmRequestType = UT_WRITE_VENDOR_DEVICE; req.bRequest = request; USETW(req.wValue, value); Modified: head/sys/dev/usb/usbdevs ============================================================================== --- head/sys/dev/usb/usbdevs Thu Oct 9 20:51:25 2008 (r183734) +++ head/sys/dev/usb/usbdevs Thu Oct 9 21:25:01 2008 (r183735) @@ -1434,7 +1434,7 @@ product HTC SMARTPHONE 0x0a51 SmartPhon /* HUAWEI products */ product HUAWEI MOBILE 0x1001 Huawei Mobile -product HUAWEI E270 0x1003 Huawei HSPA modem +product HUAWEI E220 0x1003 Huawei HSDPA modem /* HUAWEI 3com products */ product HUAWEI3COM WUB320G 0x0009 Aolynk WUB320g Modified: head/sys/i386/conf/GENERIC ============================================================================== --- head/sys/i386/conf/GENERIC Thu Oct 9 20:51:25 2008 (r183734) +++ head/sys/i386/conf/GENERIC Thu Oct 9 21:25:01 2008 (r183735) @@ -304,6 +304,7 @@ device urio # Diamond Rio 500 MP3 play device uscanner # Scanners # USB Serial devices device ucom # Generic com ttys +device u3g # USB-based 3G modems (Option, Huawei, Sierra) device uark # Technologies ARK3116 based serial adapters device ubsa # Belkin F5U103 and compatible serial adapters device uftdi # For FTDI usb serial adapters Modified: head/sys/modules/Makefile ============================================================================== --- head/sys/modules/Makefile Thu Oct 9 20:51:25 2008 (r183734) +++ head/sys/modules/Makefile Thu Oct 9 21:25:01 2008 (r183735) @@ -269,6 +269,7 @@ SUBDIR= ${_3dfx} \ twe \ tx \ txp \ + u3g \ uark \ uart \ ubsa \ Added: head/sys/modules/u3g/Makefile ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/sys/modules/u3g/Makefile Thu Oct 9 21:25:01 2008 (r183735) @@ -0,0 +1,8 @@ +# $FreeBSD$ + +.PATH: ${.CURDIR}/../../dev/usb + +KMOD= u3g +SRCS= u3g.c ucomvar.h opt_usb.h device_if.h bus_if.h usbdevs.h + +.include _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" ------------------------------------------------------- _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From spork at bway.net Sun Oct 26 07:14:57 2008 From: spork at bway.net (Charles Sprickman) Date: Sun Oct 26 07:15:04 2008 Subject: PCI-X SATA Card + Server Recommendation Message-ID: Hello all, I have two questions regarding hardware support for two servers. One is an older Supermicro with a X5DPR-iG2+ mainboard, the other is a suggestion for a brand new box that is well-supported... Both boxes will be in a co-lo, so stuff needs to not be "quirky". First the old box. I need an SATA controller, non-RAID. I'll be using gmirror. I have PCI-X slots, so I'd like to go with a PCI-X controller. There seem to be very few out there, and this one keeps popping up everywhere: http://www.newegg.com/Product/Product.aspx?Item=N82E16816124014 The comments there mention the chip is a Silicon Image 3124, but I don't know if I can trust a random NewEgg user. Can anyone confirm that controller as working and free of quirks? Are there other cards I should be looking at? Next, I'm looking for a basic 1U server for light webhosting. Reliability and compatibility are the two main concerns. I'm very happy with 3Ware RAID cards, so I will likely add that in myself. The server would optimally already have a hot swap SATA backplane and 4 drive bays. I'm open to the semi-barebones route like the Supermicro servers as well as major vendors like Dell and HP. Having some type of IP-KVM-like functionality as an option would also be nice, but I'll settle for a serial console. I'd like to keep this under $2K. Both servers will be running FreeBSD 7.1 (if it's out in time). Thanks, Charles From koitsu at FreeBSD.org Sun Oct 26 12:50:19 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Sun Oct 26 12:50:25 2008 Subject: PCI-X SATA Card + Server Recommendation In-Reply-To: References: Message-ID: <20081026125017.GA88016@icarus.home.lan> On Sun, Oct 26, 2008 at 02:48:16AM -0400, Charles Sprickman wrote: > Hello all, > > I have two questions regarding hardware support for two servers. One is > an older Supermicro with a X5DPR-iG2+ mainboard, the other is a > suggestion for a brand new box that is well-supported... Both boxes will > be in a co-lo, so stuff needs to not be "quirky". > > First the old box. I need an SATA controller, non-RAID. I'll be using > gmirror. I have PCI-X slots, so I'd like to go with a PCI-X controller. > There seem to be very few out there, and this one keeps popping up > everywhere: > > http://www.newegg.com/Product/Product.aspx?Item=N82E16816124014 > > The comments there mention the chip is a Silicon Image 3124, but I don't > know if I can trust a random NewEgg user. That card does in fact use a Silicon Image chip -- I've confirmed by looking at the PCB itself (you can see the Silicon Image logo printed on it), and by looking at the Windows drivers: http://www.adeltek.com/Product%20Manual/PCI%20IO%20CONTROLLER/SD-PCXSA2-2E2R.jpg http://www.adeltek.com/Product%20Driver/PCI-X%20controller/sd-pcxsa2-2e2r.zip Stay away from this card. > Can anyone confirm that controller as working and free of quirks? > Are there other cards I should be looking at? I was hoping the X5DPR-iG2+ would have a UIO slot, but it doesn't. Too old I guess. PCI-X is also slowly getting phased out too, so it's becoming harder to find native PCI-X cards. These are cards I can recommend for your situation. Yes, they do RAID, they all support JBOD; just plug the disks in and go. http://www.highpoint-tech.com/USA/series_2000.htm HighPoint RocketRAID 2210 (hptrr(4) driver; be sure to read NOTES) HighPoint RocketRAID 2220 (hptrr(4) driver; be sure to read NOTES) HighPoint RocketRAID 2224 (hptrr(4) driver; be sure to read NOTES) HighPoint RocketRAID 2240 (hptrr(4) driver; be sure to read NOTES) http://www.areca.com.tw/products/pcix.htm Areca ARC-1110 (arcmsr(4) driver) Areca ARC-1120 (arcmsr(4) driver) Areca ARC-1130 (arcmsr(4) driver) Areca ARC-1160 (arcmsr(4) driver) Areca ARC-1130ML (arcmsr(4) driver) Areca ARC-1160ML (arcmsr(4) driver) The FreeBSD community members who have Areca cards have been thrilled with them, and *do* use the native RAID features reliably. Other cards which might work, but there's no confirmation of it, so I have to assume they aren't supported (in the case of the SX4300, I even see a mail dated January 2007 from someone asking for support for the card): Promise FastTrak SX4300 Promise FastTrak SX8300 Promise SuperTrak EX8300 I'm glad you have good experiences with 3Ware, but as for me, I'm too wary of their stuff based on a history of firmware bugs/issues. It's purely a personal decision of mine, so I don't "slam" 3Ware at all. > Next, I'm looking for a basic 1U server for light webhosting. > Reliability and compatibility are the two main concerns. I'm very happy > with 3Ware RAID cards, so I will likely add that in myself. The server > would optimally already have a hot swap SATA backplane and 4 drive bays. > I'm open to the semi-barebones route like the Supermicro servers as well > as major vendors like Dell and HP. Having some type of IP-KVM-like > functionality as an option would also be nice, but I'll settle for a > serial console. I'd like to keep this under $2K. There's a bunch of Supermicro systems which meet your needs. The first four are very new, and use the Intel X48 chipset. I don't know of any FreeBSD people using the X7SBU board, but I'm sure there are some. http://www.supermicro.com/products/system/1U/ Supermicro SuperServer 5015B-URB (~US$975) Supermicro SuperServer 5015B-NTRB (~US$975) Supermicro SuperServer 5015B-UB (~US$785) Supermicro SuperServer 5015B-NTB (~US$785) Supermicro SuperServer 5015B-MTB (~US$655) bsdhwmon(8) supports the 5015B-MTB (X7SBi), but doesn't support the others (X7SBU). If someone out there has an X7SBU, please get in touch with me so I can add support for it! Specifically with regards to the 5015B-MTB: note no floppy drive. Supermicro replaced it with a front-panel USB/COM port thingus, which can be removed and replaced with a floppy drive (purchased from a distributor). I believe the front is COM2, while the rear is COM1. "Why do I care about floppy drives?" I don't usually... except some Supermicro boards have compatibility problems with certain brand/model/revisions of USB flash drives. You can read about my experience (and my interaction with engineering) on my blog: http://koitsu.wordpress.com/2008/04/05/supermicro-pdsmi-bios-bugs/ http://koitsu.wordpress.com/2008/04/26/supermicro-pdsmi-bios-bugs-part-2/ http://koitsu.wordpress.com/2008/07/10/supermicro-pdsmi-bios-bugs-finale/ Regarding KVM-over-IP: the Supermicro boards support an IPMI card add-on which does this, but I **highly** recommend avoiding it. I know guys over at Yahoo who complain constantly about these cards being flaky (mostly card firmware bugs), people on the mailing lists have stated this, and folks on #bsdports as well. Go with serial if possible. But if you do have to get the IPMI card, buy one which has a dedicated NIC; DO NOT buy one which "piggybacks" on top of an on-board NIC, it will only cause you problems. If you really want a KVM-over-IP solution, consider a KVM-over-IP device like ones from Aten; they'll work with anything. -- | 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 spork at bway.net Sun Oct 26 19:30:13 2008 From: spork at bway.net (Charles Sprickman) Date: Sun Oct 26 19:30:21 2008 Subject: PCI-X SATA Card + Server Recommendation In-Reply-To: <20081026125017.GA88016@icarus.home.lan> References: <20081026125017.GA88016@icarus.home.lan> Message-ID: On Sun, 26 Oct 2008, Jeremy Chadwick wrote: > On Sun, Oct 26, 2008 at 02:48:16AM -0400, Charles Sprickman wrote: >> Hello all, >> >> I have two questions regarding hardware support for two servers. One is >> an older Supermicro with a X5DPR-iG2+ mainboard, the other is a >> suggestion for a brand new box that is well-supported... Both boxes will >> be in a co-lo, so stuff needs to not be "quirky". >> >> First the old box. I need an SATA controller, non-RAID. I'll be using >> gmirror. I have PCI-X slots, so I'd like to go with a PCI-X controller. >> There seem to be very few out there, and this one keeps popping up >> everywhere: >> >> http://www.newegg.com/Product/Product.aspx?Item=N82E16816124014 >> >> The comments there mention the chip is a Silicon Image 3124, but I don't >> know if I can trust a random NewEgg user. > > That card does in fact use a Silicon Image chip -- I've confirmed by > looking at the PCB itself (you can see the Silicon Image logo printed on > it), and by looking at the Windows drivers: > > http://www.adeltek.com/Product%20Manual/PCI%20IO%20CONTROLLER/SD-PCXSA2-2E2R.jpg > http://www.adeltek.com/Product%20Driver/PCI-X%20controller/sd-pcxsa2-2e2r.zip > > Stay away from this card. Will do. Google was very unhelpful with finding info on Silicon Image and FreeBSD, so I thank you for that. >> Can anyone confirm that controller as working and free of quirks? >> Are there other cards I should be looking at? > > I was hoping the X5DPR-iG2+ would have a UIO slot, but it doesn't. Too > old I guess. PCI-X is also slowly getting phased out too, so it's > becoming harder to find native PCI-X cards. > > These are cards I can recommend for your situation. Yes, they do RAID, > they all support JBOD; just plug the disks in and go. > > http://www.highpoint-tech.com/USA/series_2000.htm > HighPoint RocketRAID 2210 (hptrr(4) driver; be sure to read NOTES) > HighPoint RocketRAID 2220 (hptrr(4) driver; be sure to read NOTES) > HighPoint RocketRAID 2224 (hptrr(4) driver; be sure to read NOTES) > HighPoint RocketRAID 2240 (hptrr(4) driver; be sure to read NOTES) Ouch. I was thinking more along the lines of a dead-simple SATA card in the under $50 range. I'm not up at all on PCI-X stuff, but I assume I can go with a normal PCI card, right? Or 64-bit PCI (or is that PCI-X)? What kind of performance hit would I have going from a PCI-X card to something else, and if I remove the PCI-X restriction, is there another recommended card? > http://www.areca.com.tw/products/pcix.htm > Areca ARC-1110 (arcmsr(4) driver) > Areca ARC-1120 (arcmsr(4) driver) > Areca ARC-1130 (arcmsr(4) driver) > Areca ARC-1160 (arcmsr(4) driver) > Areca ARC-1130ML (arcmsr(4) driver) > Areca ARC-1160ML (arcmsr(4) driver) > > The FreeBSD community members who have Areca cards have been thrilled > with them, and *do* use the native RAID features reliably. I looked at those last time I was shopping. The only thing that really bugged me about them was the fan on the card. I know that sounds silly, but when you're spending 4 figures and a $3 fan is what's keeping the card from frying, and you can't monitor that fan... I just didn't like that. I really like the 9550SX. I abused the hell out of it while I had the server at home. Unclean shutdowns during drive rebuilds, shutdowns while growing an array, all sorts of "OMG! Don't do that!" scenarios and I could not break it. My expectations were low though, as my previous experience was with Adaptec SCSI RAID controllers. >> Next, I'm looking for a basic 1U server for light webhosting. >> Reliability and compatibility are the two main concerns. I'm very happy >> with 3Ware RAID cards, so I will likely add that in myself. The server >> would optimally already have a hot swap SATA backplane and 4 drive bays. >> I'm open to the semi-barebones route like the Supermicro servers as well >> as major vendors like Dell and HP. Having some type of IP-KVM-like >> functionality as an option would also be nice, but I'll settle for a >> serial console. I'd like to keep this under $2K. > > There's a bunch of Supermicro systems which meet your needs. The first > four are very new, and use the Intel X48 chipset. I don't know of any > FreeBSD people using the X7SBU board, but I'm sure there are some. > > http://www.supermicro.com/products/system/1U/ > Supermicro SuperServer 5015B-URB (~US$975) > Supermicro SuperServer 5015B-NTRB (~US$975) > Supermicro SuperServer 5015B-UB (~US$785) > Supermicro SuperServer 5015B-NTB (~US$785) > Supermicro SuperServer 5015B-MTB (~US$655) Thanks for the lineup, I'll check those out. > Regarding KVM-over-IP: the Supermicro boards support an IPMI card add-on > which does this, but I **highly** recommend avoiding it. I know guys > over at Yahoo who complain constantly about these cards being flaky > (mostly card firmware bugs), people on the mailing lists have stated > this, and folks on #bsdports as well. Go with serial if possible. But > if you do have to get the IPMI card, buy one which has a dedicated NIC; > DO NOT buy one which "piggybacks" on top of an on-board NIC, it will > only cause you problems. We have one Supermicro at a client site with the IPMI card. A total waste of money. It was/is flakey as hell and not something we rely on at all. I'd never even look at IPMI again. > If you really want a KVM-over-IP solution, consider a KVM-over-IP device > like ones from Aten; they'll work with anything. I'm a bit intrigued by the Dell and HP add-in cards that are NOT IPMI, but do offer a full remote console. The cost appears to be about the same as an IPMI card. I've never bought either brand before though, and I have no idea how well supported these things are under FreeBSD (especially their own branded RAID controllers). Dell PowerEdge R200 (upgrade CPU to C2D or Xeon, add RAID, add DRAC card) - around $1500 http://configure.us.dell.com/dellstore/config.aspx?oc=becwuk1&c=us&l=en&s=bsd&cs=04&kc=category~rack_optimized The DRAC card, which has it's own ethernet port and supports booting from an ISO, etc.: http://accessories.us.dell.com/sna/products/Networking_Communication/productdetail.aspx?c=us&l=en&s=bsd&cs=04&sku=313-2822 On the HP side, the DL160 looks interesting as well. Like the Dell, info on the RAID controllers is pretty slim. Here's their "lights out" management option: http://h30094.www3.hp.com/product.asp?sku=3778577 Apparently it's already on the server, and you license advanced features. Probably a shared NIC situation... Any opinions on this mess are welcome... Thanks, Charles > -- > | 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 Sun Oct 26 20:49:37 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Sun Oct 26 20:49:44 2008 Subject: PCI-X SATA Card + Server Recommendation In-Reply-To: References: <20081026125017.GA88016@icarus.home.lan> Message-ID: <20081026204935.GA2429@icarus.home.lan> On Sun, Oct 26, 2008 at 03:30:11PM -0400, Charles Sprickman wrote: > On Sun, 26 Oct 2008, Jeremy Chadwick wrote: >> I was hoping the X5DPR-iG2+ would have a UIO slot, but it doesn't. Too >> old I guess. PCI-X is also slowly getting phased out too, so it's >> becoming harder to find native PCI-X cards. >> >> These are cards I can recommend for your situation. Yes, they do RAID, >> they all support JBOD; just plug the disks in and go. >> >> http://www.highpoint-tech.com/USA/series_2000.htm >> HighPoint RocketRAID 2210 (hptrr(4) driver; be sure to read NOTES) >> HighPoint RocketRAID 2220 (hptrr(4) driver; be sure to read NOTES) >> HighPoint RocketRAID 2224 (hptrr(4) driver; be sure to read NOTES) >> HighPoint RocketRAID 2240 (hptrr(4) driver; be sure to read NOTES) > > Ouch. I was thinking more along the lines of a dead-simple SATA card in > the under $50 range. I'm not up at all on PCI-X stuff, but I assume I > can go with a normal PCI card, right? Or 64-bit PCI (or is that PCI-X)? > What kind of performance hit would I have going from a PCI-X card to > something else, and if I remove the PCI-X restriction, is there another > recommended card? Any PCI 2.x or 3.x revision card should work fine in a PCI-X slot. Of course, the card will only run at 33MHz 32-bit (vs. 133MHz 64-bit, which is what native PCI-X is), but it'll still work. Most PCI cards are 32-bit 33MHz, but a 64-bit 33MHz PCI card should also work. The only PCI 1.x cards will probably fry your motherboard; they use a 5V bus, not a 3.3V bus. :-) This doesn't apply to your situation, but it's good knowledge for others who are reading: You can also use a PCI-X card in a PCI slot -- some of the connector pins will "hang off" the end of the slot without worry -- but ONLY IF the PCI-X card specifically states it works in 32-bit 33MHz mode. The specsheet/manual will state something like this; it if doesn't, don't risk it. >> http://www.areca.com.tw/products/pcix.htm >> Areca ARC-1110 (arcmsr(4) driver) >> Areca ARC-1120 (arcmsr(4) driver) >> Areca ARC-1130 (arcmsr(4) driver) >> Areca ARC-1160 (arcmsr(4) driver) >> Areca ARC-1130ML (arcmsr(4) driver) >> Areca ARC-1160ML (arcmsr(4) driver) >> >> The FreeBSD community members who have Areca cards have been thrilled >> with them, and *do* use the native RAID features reliably. > > I looked at those last time I was shopping. The only thing that really > bugged me about them was the fan on the card. I know that sounds silly, > but when you're spending 4 figures and a $3 fan is what's keeping the > card from frying, and you can't monitor that fan... I just didn't like > that. Regarding the fan -- the card has RPM monitoring of the on-board fan, and it's reported inside of the card BIOS, as well as the CLI utilities. Also, the user manual states the following: ========= Included in the product box is a field replaceable passive heatsink to be used only if there is enough airflow to adequately cool the passive heatsink. The "Controller Fan Detection" function is available in the version 1.36 date: 2005-05-19 and later for preventing the Buzzer warning. When using the passive heatsink, disable the "Controller Fan Detection" function through this McBIOS RAID manager setting. The following screen shot shows how to change the McBIOS RAID manager setting to disable the beeper function. (This function is not available in the web browser setting.) ========= I believe this means, assuming you set up monitoring of the card properly, you can monitor fan RPMs, and also get an alert if the fan dies (presumably RPM == 0, or possibly RPM < 250). There's an audible buzzer (see above) which also gets emit if the fan dies. Finally, tihe Areca CLI utilities are FreeBSD-native and do not require Linux emulation. I refuse to buy any card or software which requires such -- absolutely preposterous in this day and age. (I'm looking at you, Brother (printer manufacturer)) > We have one Supermicro at a client site with the IPMI card. A total > waste of money. It was/is flakey as hell and not something we rely on at > all. I'd never even look at IPMI again. IPMI -- great in concept, *horribly* implemented because there's really no "standard" to how all these vendors do it. >> If you really want a KVM-over-IP solution, consider a KVM-over-IP device >> like ones from Aten; they'll work with anything. In reply to my own comment, there's something I should mention about KVM-over-IP switches: "virtual media" support. They all require a USB connection between the KVM-over-IP switch and the host system. That made me pretty much ignore "virtual media" with such switches, but all the rest of the features are useful. Also, there's a huge problem with KVM-over-IP that isn't immediately thought of until one is actually in the situation (and I've witnessed this twice in private mails when helping other FreeBSD users): KVM-over-IP switches remove your ability to copy/paste data from the VGA console into, say, an Email. If you're needing to debug something in a bootloader or in the kernel and it requires more than a page of output, you're kinda screwed (what're you going to do, take 50 photos with a digital camera as fast as the screen scrolls?). Just something to keep in mind for those who might be considering this route. > I'm a bit intrigued by the Dell and HP add-in cards that are NOT IPMI, > but do offer a full remote console. The cost appears to be about the > same as an IPMI card. I've never bought either brand before though, and > I have no idea how well supported these things are under FreeBSD > (especially their own branded RAID controllers). > > Dell PowerEdge R200 (upgrade CPU to C2D or Xeon, add RAID, add DRAC card) > - around $1500 > http://configure.us.dell.com/dellstore/config.aspx?oc=becwuk1&c=us&l=en&s=bsd&cs=04&kc=category~rack_optimized > > The DRAC card, which has it's own ethernet port and supports booting from > an ISO, etc.: > > http://accessories.us.dell.com/sna/products/Networking_Communication/productdetail.aspx?c=us&l=en&s=bsd&cs=04&sku=313-2822 > > On the HP side, the DL160 looks interesting as well. Like the Dell, info > on the RAID controllers is pretty slim. Here's their "lights out" > management option: > > http://h30094.www3.hp.com/product.asp?sku=3778577 > > Apparently it's already on the server, and you license advanced features. > Probably a shared NIC situation... iLO/iLO2 = Integrated Lights-Out (v2), which means the remote management chip is on-board, rather than requiring purchase of an add-in card. LOM/LOM2 are terms for the older systems which require the actual external card. The best remote management I've ever seen has been on HP/Compaq Proliant systems with iLO/LOM/LOM2. Downright one of the most useful features I've ever seen. It was a total trip seeing an ex-roommate of mine sit in our living room with his Windows laptop, installing Red Hat onto a server in Australia, using the Red Hat CD in his laptop, while having pure control over the system even before it boots. That is *absolutely* how it should be done. Of course, the "virtual media" feature of the iLO often requires a license of some kind, which costs $$$. Regarding shared NIC on iLO: absolutely not. HP/Compaq knows better than this. All the iLO stuff has a pure dedicated NIC. See "Rear panel components" in the service guide manual, note item #11: http://Fbizsupport.austin.hp.com/bc/docs/support/SupportManual/c01555951%2Fc01555951.pdf On the other hand, IMHO, HP/Compaq hardware is *incredibly* overpriced for no justified reason. And if I remember right, you're forced to buy all of your H/W from them (hard disks, cards, RAM, whatever). The iLO is one thing which is truly remarkable about 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 koitsu at FreeBSD.org Sun Oct 26 20:52:29 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Sun Oct 26 20:52:35 2008 Subject: PCI-X SATA Card + Server Recommendation In-Reply-To: <20081026204935.GA2429@icarus.home.lan> References: <20081026125017.GA88016@icarus.home.lan> <20081026204935.GA2429@icarus.home.lan> Message-ID: <20081026205225.GA3719@icarus.home.lan> On Sun, Oct 26, 2008 at 01:49:35PM -0700, Jeremy Chadwick wrote: > http://Fbizsupport.austin.hp.com/bc/docs/support/SupportManual/c01555951%2Fc01555951.pdf I typo'd this while removing the URL entity encoding variables. God I hate it when people write CGIs which blindly rewrite all characters rather than just the ones covered by the RFC... http://bizsupport.austin.hp.com/bc/docs/support/SupportManual/c01555951/c01555951.pdf -- | 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 louie at transsys.com Sun Oct 26 22:22:23 2008 From: louie at transsys.com (Louis Mamakos) Date: Sun Oct 26 22:22:31 2008 Subject: PCI-X SATA Card + Server Recommendation In-Reply-To: <20081026204935.GA2429@icarus.home.lan> References: <20081026125017.GA88016@icarus.home.lan> <20081026204935.GA2429@icarus.home.lan> Message-ID: <53B2E924-A690-4DAE-B937-076B1DA89F8E@transsys.com> On Oct 26, 2008, at 4:49 PM, Jeremy Chadwick wrote: > On Sun, Oct 26, 2008 at 03:30:11PM -0400, Charles Sprickman wrote: >> On Sun, 26 Oct 2008, Jeremy Chadwick wrote: >> >> Ouch. I was thinking more along the lines of a dead-simple SATA >> card in >> the under $50 range. I'm not up at all on PCI-X stuff, but I >> assume I >> can go with a normal PCI card, right? Or 64-bit PCI (or is that >> PCI-X)? >> What kind of performance hit would I have going from a PCI-X card to >> something else, and if I remove the PCI-X restriction, is there >> another >> recommended card? > > Any PCI 2.x or 3.x revision card should work fine in a PCI-X slot. Of > course, the card will only run at 33MHz 32-bit (vs. 133MHz 64-bit, > which is > what native PCI-X is), but it'll still work. Most PCI cards are 32- > bit > 33MHz, but a 64-bit 33MHz PCI card should also work. > > The only PCI 1.x cards will probably fry your motherboard; they use > a 5V > bus, not a 3.3V bus. :-) This has been a concern of mine. I just bought a Dell Poweredge 2650 off of eBay, and was going to outfit it with a USB2/Firewire PCI card so I can attach some cheap bulk storage to it for backup purposes. The Dell has PCI-X slots; backwards compatible with PCI, right? Try to find a USB PCI board that doesn't require a 5V capable PCI slot.. I haven't been able to; of course it's pretty obvious in that the USB host is supposed to supply 5V power to the peripherals.. D'oh! Oh well. You'll have to try extra hard to fry your machine with the wrong flavor card as the PC card connectors are keyed differently, and unless you try Really Hard or try to plug it in backwards, it just won't fit. louie From groot at kde.org Sun Oct 26 22:43:03 2008 From: groot at kde.org (Adriaan de Groot) Date: Sun Oct 26 22:43:10 2008 Subject: PCI-X SATA Card + Server Recommendation In-Reply-To: <20081026204935.GA2429@icarus.home.lan> References: <20081026204935.GA2429@icarus.home.lan> Message-ID: <200810262325.45865.groot@kde.org> On Sunday 26 October 2008 21:49:35 Jeremy Chadwick wrote: > > Ouch. ?I was thinking more along the lines of a dead-simple SATA card in > > ? the under $50 range. ?I'm not up at all on PCI-X stuff, but I assume I > > can go with a normal PCI card, right? ?Or 64-bit PCI (or is that PCI-X)? > > What kind of performance hit would I have going from a PCI-X card to > > something else, and if I remove the PCI-X restriction, is there another > > recommended card? In the "cheap and it seems functional in my 4-drive GEOM mirror setup" -- software raid, so easy to migrate, there's SiI3124-based cards. Addonics makes a 4-port PCI-X card which I ran in a 32-bit PCI slot for a while. Note that these don't do any kind of HW raid, so it might not be applicable at all (I haven't read this entire thread). There's also a 2-port 3132 based PCIe x1 card and a 4-port PCIe x4 card (I suppose that's 3124 again, but don't know). It's all the same architecturally, and supported by ata(4). [ade] From koitsu at FreeBSD.org Sun Oct 26 23:31:22 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Sun Oct 26 23:31:29 2008 Subject: PCI-X SATA Card + Server Recommendation In-Reply-To: <53B2E924-A690-4DAE-B937-076B1DA89F8E@transsys.com> References: <20081026125017.GA88016@icarus.home.lan> <20081026204935.GA2429@icarus.home.lan> <53B2E924-A690-4DAE-B937-076B1DA89F8E@transsys.com> Message-ID: <20081026233120.GA5517@icarus.home.lan> On Sun, Oct 26, 2008 at 05:58:07PM -0400, Louis Mamakos wrote: > On Oct 26, 2008, at 4:49 PM, Jeremy Chadwick wrote: > >> On Sun, Oct 26, 2008 at 03:30:11PM -0400, Charles Sprickman wrote: >>> On Sun, 26 Oct 2008, Jeremy Chadwick wrote: >>> >>> Ouch. I was thinking more along the lines of a dead-simple SATA >>> card in >>> the under $50 range. I'm not up at all on PCI-X stuff, but I assume >>> I >>> can go with a normal PCI card, right? Or 64-bit PCI (or is that >>> PCI-X)? >>> What kind of performance hit would I have going from a PCI-X card to >>> something else, and if I remove the PCI-X restriction, is there >>> another >>> recommended card? >> >> Any PCI 2.x or 3.x revision card should work fine in a PCI-X slot. Of >> course, the card will only run at 33MHz 32-bit (vs. 133MHz 64-bit, >> which is >> what native PCI-X is), but it'll still work. Most PCI cards are 32- >> bit >> 33MHz, but a 64-bit 33MHz PCI card should also work. >> >> The only PCI 1.x cards will probably fry your motherboard; they use a >> 5V >> bus, not a 3.3V bus. :-) > > > This has been a concern of mine. I just bought a Dell Poweredge 2650 > off of eBay, and was going to outfit it with a USB2/Firewire PCI card > so I can attach some cheap bulk storage to it for backup purposes. The > Dell has PCI-X slots; backwards compatible with PCI, right? Try to > find a USB PCI board that doesn't require a 5V capable PCI slot.. > > I haven't been able to; of course it's pretty obvious in that the USB > host is supposed to supply 5V power to the peripherals.. D'oh! Oh well. Why do you think think the voltage provided on the USB bus is directly proportional to the voltage provided across the PCI bus? A PCI 3.3V expansion card (for USB ports) card *most definitely* provides 5V to the USB bus. The voltage increase is done with a very small amount of circuitry on the card itself. (I've confirmed this with two separate EE folks I know; I showed them your message, and they're equally as confused why you think that.) Maybe what you're trying to say is that your PowerEdge 2650 box only has the old 5V PCI slots, thus you need a USB PCI card that works in such scenarios? If so, I'm baffled as to why you're having such difficulty. Many PCI cards (including PCI USB cards -- I've Googled and found many!) are "Universal PCI" cards (keyed to work on both 3.3V and 5V PCI slots), and those will work fine. How to determine what's what: http://en.wikipedia.org/wiki/Image:PCI_Keying.png The Dell PowerEdge 2650 Systems Installation and Troubleshooting Guide indicates that the mainboard uses a riser board to provide three (3) PCI-X slots: http://support.dell.com/support/edocs/systems/pe2650/en/it/5g375aa0.htm#1046001 Googling around for a few minutes turns up some photos of the 6H580 riser board, which confirm the slots are 64-bit PCI-X 3.3V: http://cgi.ebay.com/Dell-6H580-PowerEdge-2650-PCI-Riser-Board-Card-TESTED_W0QQitemZ200218132010QQcmdZViewItem But what revision of PCI-X? Well, the speeds (MHz) available for each slot change depending upon what's installed where. Here's that reference: http://support.dell.com/support/edocs/systems/pe2650/en/it/5g375c60.htm#1059976 Which says the maximum rate is 133MHz, confirming these are PCI-X 1.0 slots. Have fun. :-) -- | 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 louie at transsys.com Mon Oct 27 01:27:14 2008 From: louie at transsys.com (Louis Mamakos) Date: Mon Oct 27 01:27:21 2008 Subject: PCI-X SATA Card + Server Recommendation In-Reply-To: <20081026233120.GA5517@icarus.home.lan> References: <20081026125017.GA88016@icarus.home.lan> <20081026204935.GA2429@icarus.home.lan> <53B2E924-A690-4DAE-B937-076B1DA89F8E@transsys.com> <20081026233120.GA5517@icarus.home.lan> Message-ID: <2F0DB513-B639-46CB-8D8F-E6D9410FE401@transsys.com> On Oct 26, 2008, at 7:31 PM, Jeremy Chadwick wrote: >> >> This has been a concern of mine. I just bought a Dell Poweredge 2650 >> off of eBay, and was going to outfit it with a USB2/Firewire PCI card >> so I can attach some cheap bulk storage to it for backup purposes. >> The >> Dell has PCI-X slots; backwards compatible with PCI, right? Try to >> find a USB PCI board that doesn't require a 5V capable PCI slot.. >> >> I haven't been able to; of course it's pretty obvious in that the USB >> host is supposed to supply 5V power to the peripherals.. D'oh! Oh >> well. > > Why do you think think the voltage provided on the USB bus is directly > proportional to the voltage provided across the PCI bus? A PCI 3.3V > expansion card (for USB ports) card *most definitely* provides 5V to > the > USB bus. The voltage increase is done with a very small amount of > circuitry on the card itself. (I've confirmed this with two > separate EE > folks I know; I showed them your message, and they're equally as > confused why you think that.) I'm well aware of the existence of switching power supply regulators; however the selection of USB/Firewire boards I was able to find didn't appear to be universal cards -- at least based on the photos provided of the actual products. The last board I bought for another system didn't have any on-board power source -- other than PTC fuses, the power just came off the PCI backplane connector. It's the easy and obvious solution. Perhaps not quite as obvious these days with 3.3V only buses. > > Maybe what you're trying to say is that your PowerEdge 2650 box only > has > the old 5V PCI slots, thus you need a USB PCI card that works in such > scenarios? If so, I'm baffled as to why you're having such > difficulty. > Many PCI cards (including PCI USB cards -- I've Googled and found > many!) > are "Universal PCI" cards (keyed to work on both 3.3V and 5V PCI > slots), > and those will work fine. How to determine what's what: > > http://en.wikipedia.org/wiki/Image:PCI_Keying.png The 2650 only has 3.3V slots. This determined by the physical keying of the connectors on the riser. I looked a bunch of boards on Amazon, and they didn't appear to be universal PCI cards. And if you look at the photos, there's nothing there that would appear to be a small switcher to generate the +5V for the USB interface. > > > The Dell PowerEdge 2650 Systems Installation and Troubleshooting Guide > indicates that the mainboard uses a riser board to provide three (3) > PCI-X slots: > > http://support.dell.com/support/edocs/systems/pe2650/en/it/5g375aa0.htm#1046001 > > Googling around for a few minutes turns up some photos of the 6H580 > riser board, which confirm the slots are 64-bit PCI-X 3.3V: > > http://cgi.ebay.com/Dell-6H580-PowerEdge-2650-PCI-Riser-Board-Card-TESTED_W0QQitemZ200218132010QQcmdZViewItem > > But what revision of PCI-X? Well, the speeds (MHz) available for each > slot change depending upon what's installed where. Here's that > reference: > > http://support.dell.com/support/edocs/systems/pe2650/en/it/5g375c60.htm#1059976 > > Which says the maximum rate is 133MHz, confirming these are PCI-X 1.0 > slots. My bandwidth needs are modest, just to run the USB/Firewire interfaces. The 2650 is pretty cost effective on ebay these days, though you're constrained to using SCA SCSI drives which are somewhat more expensive than your generic SATA drives these days. I've got 5 bays populated with 73GB drives which is sufficient for the usual email/www server, I'd like to drop some larger, less performant drives for over-the-net backup use. The search continues.. louie > > > Have fun. :-) > > -- > | 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 lbaron at freedomtc.com Mon Oct 27 05:20:05 2008 From: lbaron at freedomtc.com (Lanny Baron) Date: Mon Oct 27 05:20:35 2008 Subject: PCI-X SATA Card + Server Recommendation In-Reply-To: References: Message-ID: <49054942.4000802@freedomtc.com> Have a look at http://www.freedomtc.com/featured_1u_server.php Regards, +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+= Lanny Baron Freedom Technologies Corporation High Performance Servers and RAID Systems Toll Free: 1.877.963.1900 http://www.freedomtc.com +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+= Charles Sprickman wrote: > Hello all, > > I have two questions regarding hardware support for two servers. One is > an older Supermicro with a X5DPR-iG2+ mainboard, the other is a > suggestion for a brand new box that is well-supported... Both boxes > will be in a co-lo, so stuff needs to not be "quirky". > > First the old box. I need an SATA controller, non-RAID. I'll be using > gmirror. I have PCI-X slots, so I'd like to go with a PCI-X controller. > There seem to be very few out there, and this one keeps popping up > everywhere: > > http://www.newegg.com/Product/Product.aspx?Item=N82E16816124014 > > The comments there mention the chip is a Silicon Image 3124, but I don't > know if I can trust a random NewEgg user. > > Can anyone confirm that controller as working and free of quirks? > Are there other cards I should be looking at? > > Next, I'm looking for a basic 1U server for light webhosting. > Reliability and compatibility are the two main concerns. I'm very happy > with 3Ware RAID cards, so I will likely add that in myself. The server > would optimally already have a hot swap SATA backplane and 4 drive > bays. I'm open to the semi-barebones route like the Supermicro servers > as well as major vendors like Dell and HP. Having some type of > IP-KVM-like functionality as an option would also be nice, but I'll > settle for a serial console. I'd like to keep this under $2K. > > Both servers will be running FreeBSD 7.1 (if it's out in time). > > Thanks, > > Charles > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" From mcdouga9 at egr.msu.edu Mon Oct 27 13:32:13 2008 From: mcdouga9 at egr.msu.edu (Adam McDougall) Date: Mon Oct 27 13:32:28 2008 Subject: Request for testers: Option 3G cards, also Sierra, Huawei and Novatel In-Reply-To: <200810092344.10388.nick@van-laarhoven.org> References: <200810092344.10388.nick@van-laarhoven.org> Message-ID: <20081025212935.GV61867@egr.msu.edu> Seems to work fine with my Novatel V740 (EVDO from Verizon) Expresscard. I'm using the latest version with the bufsize patch and I'm glad I no longer have to hack in a patch to get relatively fast speeds through it (just got 140kB/sec in a test which is just over 1Mbit/sec). On Thu, Oct 09, 2008 at 11:44:09PM +0200, Nick Hibma wrote: Just now I have committed a driver for Option and Huawei cards previously supported by the ubsa driver. More information is in the commit message. I am looking for people who would be able to provide more information after testing with the 3G cards branded by: OEM: Merlin Huawei Option Sierra Novatel Qualcomm Rebranded: Dell Vodafone Note: The driver can be copied across to FreeBSD 7-STABLE if you copy the sys/modules/u3g directory and sys/dev/usb/u3g.c and sys/dev/usb/usbdevs files from HEAD and _move_ the ID from ubsa to u3g. More information can be found on http://people.freebsd.org/~n_hibma/u3g.html Thanks, Nick ---------- Forwarded Message ---------- Subject: svn commit: r183735 - in head: share/man/man4 sys/conf sys/dev/usb sys/i386/conf sys/modules sys/modules/u3g Date: Thu October 9 2008 From: Nick Hibma To: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Author: n_hibma Date: Thu Oct 9 21:25:01 2008 New Revision: 183735 URL: http://svn.freebsd.org/changeset/base/183735 Log: Say hello to the u3g driver, implementing support for 3G modems. This was located in the ubsa driver, but should be moved into a separate driver: - 3G modems provide multiple serial ports to allow AT commands while the PPP connection is up. - 3G modems do not provide baud rate or other serial port settings. - Huawei cards need specific initialisation. - ubsa is for Belkin adapters, an Linuxy choice for another device like 3G. Speeds achieved here with a weak signal at best is ~40kb/s (UMTS). No spooky STALLED messages as well. Next: Move over all entries for Sierra and Novatel cards once I have found testers, and implemented serial port enumeration for Sierra (or rather have Andrea Guzzo do it). They list all endpoints in 1 iface instead of 4 ifaces. Submitted by: aguzzo@anywi.com MFC after: 3 weeks Added: head/share/man/man4/u3g.4 (contents, props changed) head/sys/dev/usb/u3g.c (contents, props changed) head/sys/modules/u3g/ head/sys/modules/u3g/Makefile (contents, props changed) Modified: head/share/man/man4/Makefile head/sys/conf/NOTES head/sys/conf/files head/sys/dev/usb/ubsa.c head/sys/dev/usb/usbdevs head/sys/i386/conf/GENERIC head/sys/modules/Makefile Modified: head/share/man/man4/Makefile ============================================================================== --- head/share/man/man4/Makefile Thu Oct 9 20:51:25 2008 (r183734) +++ head/share/man/man4/Makefile Thu Oct 9 21:25:01 2008 (r183735) @@ -384,6 +384,7 @@ MAN= aac.4 \ twe.4 \ tx.4 \ txp.4 \ + u3g.4 \ uark.4 \ uart.4 \ ubsa.4 \ Added: head/share/man/man4/u3g.4 ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/share/man/man4/u3g.4 Thu Oct 9 21:25:01 2008 (r183735) @@ -0,0 +1,100 @@ +.\" +.\" Copyright (c) 2008 AnyWi Technologies +.\" All rights reserved. +.\" +.\" This code is derived from uark.c +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.\" $FreeBSD$ +.\" +.Dd October 7, 2008 +.Dt U3G 4 +.Os +.Sh NAME +.Nm u3g +.Nd USB support for 3G datacards +.Sh SYNOPSIS +To compile this driver into the kernel, +place the following lines in your +kernel configuration file: +.Bd -ragged -offset indent +.Cd "device u3g" +.Cd "device ucom" +.Ed +.Pp +Alternatively, to load the driver as a +module at boot time, place the following line in +.Xr loader.conf 5 : +.Bd -literal -offset indent +u3g_load="YES" +.Ed +.Sh DESCRIPTION +The +.Nm +driver provides support for the multiple USB-to-serial interfaces exposed by +many 3G usb/pccard modems. +.Pp +The device is accessed through the +.Xr ucom 4 +driver which makes it behave like a +.Xr tty 4 . +.Sh HARDWARE +The +.Nm +driver supports the following adapters: +.Pp +.Bl -bullet -compact +.It +Option Globetrotter 3G Fusion (only 3G part, not WLAN) +.It +Option Globetrotter 3G Fusion Quad (only 3G part, not WLAN) +.It +Option Globetrotter 3G Quad +.It +Option Globetrotter 3G +.It +Vodafone Mobile Connect Card 3G +.It +Huawei E220 (E270?) +.It +Huawei Mobile +.El +.Pp +The supported 3G cards provide the necessary modem port for ppp, +pppd, or mpd connections as well as extra ports (depending on the specific +device) to provide other functions (diagnostic port, SIM toolkit port) +.Sh SEE ALSO +.Xr tty 4 , +.Xr ucom 4 , +.Xr usb 4 , +.Xr ubsa 4 +.Sh HISTORY +The +.Nm +driver +appeared in +.Fx 7.0 . +The +.Xr ubsa 4 +manual page was modified for +.Nm +by +.An Andrea Guzzo Aq aguzzo@anywi.com +in September 2008. +.Sh AUTHORS +The +.Nm +driver was written by +.An Andrea Guzzo Aq aguzzo@anywi.com . +Hardware for testing provided by AnyWi Technologies, Leiden, NL. Modified: head/sys/conf/NOTES ============================================================================== --- head/sys/conf/NOTES Thu Oct 9 20:51:25 2008 (r183734) +++ head/sys/conf/NOTES Thu Oct 9 21:25:01 2008 (r183735) @@ -2416,6 +2416,8 @@ device uscanner # # USB serial support device ucom +# USB support for 3G modem cards by Option, Huawei and Sierra +device u3g # USB support for Technologies ARK3116 based serial adapters device uark # USB support for Belkin F5U103 and compatible serial adapters @@ -2441,7 +2443,6 @@ device aue # ASIX Electronics AX88172 USB 2.0 ethernet driver. Used in the # LinkSys USB200M and various other adapters. - device axe # Modified: head/sys/conf/files ============================================================================== --- head/sys/conf/files Thu Oct 9 20:51:25 2008 (r183734) +++ head/sys/conf/files Thu Oct 9 21:25:01 2008 (r183735) @@ -1327,6 +1327,7 @@ dev/usb/ohci_pci.c optional ohci pci dev/usb/sl811hs.c optional slhci dev/usb/slhci_pccard.c optional slhci pccard dev/usb/uark.c optional uark +dev/usb/u3g.c optional u3g dev/usb/ubsa.c optional ubsa dev/usb/ubser.c optional ubser dev/usb/ucom.c optional ucom Added: head/sys/dev/usb/u3g.c ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/sys/dev/usb/u3g.c Thu Oct 9 21:25:01 2008 (r183735) @@ -0,0 +1,330 @@ +/* + * Copyright (c) 2008 AnyWi Technologies + * Author: Andrea Guzzo + * * based on uark.c 1.1 2006/08/14 08:30:22 jsg * + * * parts from ubsa.c 183348 2008-09-25 12:00:56Z phk * + * + * Permission to use, copy, modify, and distribute this software for any + * purpose with or without fee is hereby granted, provided that the above + * copyright notice and this permission notice appear in all copies. + * + * THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES + * WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF + * MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR + * ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES + * WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN + * ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF + * OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. + * + * $FreeBSD$ + */ + +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include + +#include +#include +#include + +#include + +#include "usbdevs.h" + +#ifdef U3G_DEBUG +#define DPRINTFN(n, x) do { if (u3gdebug > (n)) printf x; } while (0) +int u3gtebug = 0; +#else +#define DPRINTFN(n, x) +#endif +#define DPRINTF(x) DPRINTFN(0, x) + +#define U3GBUFSZ 1024 +#define U3G_MAXPORTS 4 + +struct u3g_softc { + struct ucom_softc sc_ucom[U3G_MAXPORTS];; + device_t sc_dev; + usbd_device_handle sc_udev; + u_char sc_msr; + u_char sc_lsr; + u_char numports; + + usbd_interface_handle sc_intr_iface; /* interrupt interface */ +#ifdef U3G_DEBUG + int sc_intr_number; /* interrupt number */ + usbd_pipe_handle sc_intr_pipe; /* interrupt pipe */ + u_char *sc_intr_buf; /* interrupt buffer */ +#endif + int sc_isize; +}; + +struct ucom_callback u3g_callback = { + NULL, + NULL, + NULL, + NULL, + NULL, + NULL, + NULL, + NULL, +}; + +static const struct usb_devno u3g_devs[] = { + /* OEM: Option */ + { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GT3G }, + { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GT3GQUAD }, + { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GT3GPLUS }, + { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GTMAX36 }, + { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_VODAFONEMC3G }, + /* OEM: Huawei */ + { USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_MOBILE }, + { USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E220 }, + + { 0, 0 } +}; + +#ifdef U3G_DEBUG +static void +u3g_intr(usbd_xfer_handle xfer, usbd_private_handle priv, usbd_status status) +{ + struct u3g_softc *sc = (struct u3g_softc *)priv; + device_printf(sc->sc_dev, "INTERRUPT CALLBACK\n"); +} +#endif + +static int +u3g_huawei_reinit(usbd_device_handle dev) +{ + /* The Huawei device presents itself as a umass device with Windows + * drivers on it. After installation of the driver, it reinits into a + * 3G serial device. + */ + usb_device_request_t req; + usb_config_descriptor_t *cdesc; + + /* Get the config descriptor */ + cdesc = usbd_get_config_descriptor(dev); + if (cdesc == NULL) + return (UMATCH_NONE); + + /* One iface means umass mode, more than 1 (4 usually) means 3G mode */ + if (cdesc->bNumInterface > 1) + return (UMATCH_VENDOR_PRODUCT); + + req.bmRequestType = UT_WRITE_DEVICE; + req.bRequest = UR_SET_FEATURE; + USETW(req.wValue, UF_DEVICE_REMOTE_WAKEUP); + USETW(req.wIndex, UHF_PORT_SUSPEND); + USETW(req.wLength, 0); + + (void) usbd_do_request(dev, &req, 0); + + return UMATCH_NONE; /* mismatch; it will be gone and reappear */ +} + +static int +u3g_match(device_t self) +{ + struct usb_attach_arg *uaa = device_get_ivars(self); + + if (uaa->iface != NULL) + return (UMATCH_NONE); + + if (uaa->vendor == USB_VENDOR_HUAWEI) + return u3g_huawei_reinit(uaa->device); + + if (usb_lookup(u3g_devs, uaa->vendor, uaa->product)) + return UMATCH_VENDOR_PRODUCT; + + return UMATCH_NONE; +} + +static int +u3g_attach(device_t self) +{ + struct u3g_softc *sc = device_get_softc(self); + struct usb_attach_arg *uaa = device_get_ivars(self); + usbd_device_handle dev = uaa->device; + usbd_interface_handle iface; + usb_interface_descriptor_t *id; + usb_endpoint_descriptor_t *ed; + usbd_status error; + int i, n; + usb_config_descriptor_t *cdesc; + struct ucom_softc *ucom = NULL; + char devnamefmt[32]; + + sc->sc_dev = self; +#ifdef DEBUG + sc->sc_intr_number = -1; + sc->sc_intr_pipe = NULL; +#endif + /* Move the device into the configured state. */ + error = usbd_set_config_index(dev, 1, 1); + if (error) { + device_printf(self, "failed to set configuration: %s\n", + usbd_errstr(error)); + goto bad; + } + + /* get the config descriptor */ + cdesc = usbd_get_config_descriptor(dev); + + if (cdesc == NULL) { + device_printf(self, "failed to get configuration descriptor\n"); + goto bad; + } + + sc->sc_udev = dev; + sc->numports = (cdesc->bNumInterface <= U3G_MAXPORTS)?cdesc->bNumInterface:U3G_MAXPORTS; + for ( i = 0; i < sc->numports; i++ ) { + ucom = &sc->sc_ucom[i]; + + ucom->sc_dev = self; + ucom->sc_udev = dev; + error = usbd_device2interface_handle(dev, i, &iface); + if (error) { + device_printf(ucom->sc_dev, + "failed to get interface, err=%s\n", + usbd_errstr(error)); + ucom->sc_dying = 1; + goto bad; + } + id = usbd_get_interface_descriptor(iface); + ucom->sc_iface = iface; + + ucom->sc_bulkin_no = ucom->sc_bulkout_no = -1; + for (n = 0; n < id->bNumEndpoints; n++) { + ed = usbd_interface2endpoint_descriptor(iface, n); + if (ed == NULL) { + device_printf(ucom->sc_dev, + "could not read endpoint descriptor\n"); + goto bad; + } + if (UE_GET_DIR(ed->bEndpointAddress) == UE_DIR_IN && + UE_GET_XFERTYPE(ed->bmAttributes) == UE_BULK) + ucom->sc_bulkin_no = ed->bEndpointAddress; + else if (UE_GET_DIR(ed->bEndpointAddress) == UE_DIR_OUT && + UE_GET_XFERTYPE(ed->bmAttributes) == UE_BULK) + ucom->sc_bulkout_no = ed->bEndpointAddress; + } + if (ucom->sc_bulkin_no == -1 || ucom->sc_bulkout_no == -1) { + device_printf(ucom->sc_dev, "missing endpoint\n"); + goto bad; + } + ucom->sc_parent = sc; + ucom->sc_ibufsize = U3GBUFSZ; + ucom->sc_obufsize = U3GBUFSZ; + ucom->sc_ibufsizepad = U3GBUFSZ; + ucom->sc_opkthdrlen = 0; + + ucom->sc_callback = &u3g_callback; + + sprintf(devnamefmt,"U%d.%%d", device_get_unit(self)); + DPRINTF(("u3g: in=0x%x out=0x%x, devname=%s\n", + ucom->sc_bulkin_no, ucom->sc_bulkout_no, devnamefmt)); +#if __FreeBSD_version < 800000 + ucom_attach_tty(ucom, TS_CALLOUT, devnamefmt, i); +#else + ucom_attach_tty(ucom, devnamefmt, i); +#endif + } +#ifdef U3G_DEBUG + if (sc->sc_intr_number != -1 && sc->sc_intr_pipe == NULL) { + sc->sc_intr_buf = malloc(sc->sc_isize, M_USBDEV, M_WAITOK); + error = usbd_open_pipe_intr(sc->sc_intr_iface, + sc->sc_intr_number, + USBD_SHORT_XFER_OK, + &sc->sc_intr_pipe, + sc, + sc->sc_intr_buf, + sc->sc_isize, + u3g_intr, + 100); + if (error) { + device_printf(self, + "cannot open interrupt pipe (addr %d)\n", + sc->sc_intr_number); + goto bad; + } + } +#endif + device_printf(self, "configured %d serial ports (/dev/cuaU%d.X)", + sc->numports, device_get_unit(self)); + + return 0; + +bad: + DPRINTF(("u3g_attach: ATTACH ERROR\n")); + ucom->sc_dying = 1; + return ENXIO; +} + +static int +u3g_detach(device_t self) +{ + struct u3g_softc *sc = device_get_softc(self); + int rv = 0; + int i; + + DPRINTF(("u3g_detach: sc=%p\n", sc)); + + for (i = 0; i < sc->numports; i++) { + if(sc->sc_ucom[i].sc_udev) { + sc->sc_ucom[i].sc_dying = 1; + rv = ucom_detach(&sc->sc_ucom[i]); + if(rv != 0) { + device_printf(self, "Can't deallocat port %d", i); + return rv; + } + } + } + +#ifdef U3G_DEBUG + if (sc->sc_intr_pipe != NULL) { + int err = usbd_abort_pipe(sc->sc_intr_pipe); + if (err) + device_printf(self, + "abort interrupt pipe failed: %s\n", + usbd_errstr(err)); + err = usbd_close_pipe(sc->sc_intr_pipe); + if (err) + device_printf(self, + "close interrupt pipe failed: %s\n", + usbd_errstr(err)); + free(sc->sc_intr_buf, M_USBDEV); + sc->sc_intr_pipe = NULL; + } +#endif + + return 0; +} + +static device_method_t u3g_methods[] = { + /* Device interface */ + DEVMETHOD(device_probe, u3g_match), + DEVMETHOD(device_attach, u3g_attach), + DEVMETHOD(device_detach, u3g_detach), + + { 0, 0 } +}; + +static driver_t u3g_driver = { + "ucom", + u3g_methods, + sizeof (struct u3g_softc) +}; + +DRIVER_MODULE(u3g, uhub, u3g_driver, ucom_devclass, usbd_driver_load, 0); +MODULE_DEPEND(u3g, usb, 1, 1, 1); +MODULE_DEPEND(u3g, ucom, UCOM_MINVER, UCOM_PREFVER, UCOM_MAXVER); Modified: head/sys/dev/usb/ubsa.c ============================================================================== --- head/sys/dev/usb/ubsa.c Thu Oct 9 20:51:25 2008 (r183734) +++ head/sys/dev/usb/ubsa.c Thu Oct 9 21:25:01 2008 (r183735) @@ -161,8 +161,6 @@ SYSCTL_INT(_hw_usb_ubsa, OID_AUTO, debug struct ubsa_softc { struct ucom_softc sc_ucom; - int sc_huawei; - int sc_iface_number; /* interface number */ usbd_interface_handle sc_intr_iface; /* interrupt interface */ @@ -228,24 +226,11 @@ static const struct ubsa_product { { USB_VENDOR_GOHUBS, USB_PRODUCT_GOHUBS_GOCOM232 }, /* Peracom */ { USB_VENDOR_PERACOM, USB_PRODUCT_PERACOM_SERIAL1 }, - /* Dell version of the Novatel 740 */ - { USB_VENDOR_DELL, USB_PRODUCT_DELL_U740 }, - /* Option Vodafone MC3G */ - { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_VODAFONEMC3G }, - /* Option GlobeTrotter 3G */ - { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GT3G }, - /* Option GlobeTrotter 3G QUAD */ - { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GT3GQUAD }, - /* Option GlobeTrotter 3G+ */ - { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GT3GPLUS }, - /* Option GlobeTrotter Max 3.6 */ - { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GTMAX36 }, - /* Huawei Mobile */ - { USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_MOBILE }, - { USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E270 }, + /* Merlin */ { USB_VENDOR_MERLIN, USB_PRODUCT_MERLIN_V620 }, /* Qualcomm, Inc. ZTE CDMA */ { USB_VENDOR_QUALCOMMINC, USB_PRODUCT_QUALCOMMINC_CDMA_MSM }, + /* Novatel */ { USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_CDMA_MODEM }, /* Novatel Wireless Merlin ES620 */ { USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_ES620 }, @@ -256,6 +241,8 @@ static const struct ubsa_product { /* Novatel Wireless Merlin U740 */ { USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_U740 }, { USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_U740_2 }, + /* Dell version of the Novatel 740 */ + { USB_VENDOR_DELL, USB_PRODUCT_DELL_U740 }, /* Novatel Wireless Merlin U950D */ { USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_U950D }, /* Novatel Wireless Merlin V620 */ @@ -341,52 +328,6 @@ MODULE_DEPEND(ubsa, usb, 1, 1, 1); MODULE_DEPEND(ubsa, ucom, UCOM_MINVER, UCOM_PREFVER, UCOM_MAXVER); MODULE_VERSION(ubsa, UBSA_MODVER); -/* - * Huawei Exxx radio devices have a built in flash disk which is their - * default power up configuration. This allows the device to carry its - * own installation software. - * - * Instead of following the USB spec, and create multiple configuration - * descriptors for this, the devices expects the driver to send - * UF_DEVICE_REMOTE_WAKEUP to endpoint 2 to reset the device, so it - * reprobes, now with the radio exposed. - */ - -static usbd_status -ubsa_huawei(device_t self, struct usb_attach_arg *uaa) { - usb_device_request_t req; usbd_device_handle dev; - usb_config_descriptor_t *cdesc; - - if (self == NULL) - return (UMATCH_NONE); - if (uaa == NULL) - return (UMATCH_NONE); - dev = uaa->device; - if (dev == NULL) - return (UMATCH_NONE); - /* get the config descriptor */ - cdesc = usbd_get_config_descriptor(dev); - if (cdesc == NULL) - return (UMATCH_NONE); - - if (cdesc->bNumInterface > 1) - return (0); - - /* Bend it like Beckham */ - device_printf(self, "Kicking Huawei device into radio mode\n"); - memset(&req, 0, sizeof req); - req.bmRequestType = UT_WRITE_DEVICE; - req.bRequest = UR_SET_FEATURE; - USETW(req.wValue, UF_DEVICE_REMOTE_WAKEUP); - USETW(req.wIndex, 2); - USETW(req.wLength, 0); - - /* We get error return, but it works */ - (void)usbd_do_request(dev, &req, 0); - return (UMATCH_NONE); -} - - static int ubsa_match(device_t self) { @@ -399,9 +340,6 @@ ubsa_match(device_t self) for (i = 0; ubsa_products[i].vendor != 0; i++) { if (ubsa_products[i].vendor == uaa->vendor && ubsa_products[i].product == uaa->product) { - if (uaa->vendor == USB_VENDOR_HUAWEI && - ubsa_huawei(self, uaa)) - break; return (UMATCH_VENDOR_PRODUCT); } } @@ -424,9 +362,6 @@ ubsa_attach(device_t self) dev = uaa->device; ucom = &sc->sc_ucom; - if (uaa->vendor == USB_VENDOR_HUAWEI) - sc->sc_huawei = 1; - /* * initialize rts, dtr variables to something * different from boolean 0, 1 @@ -575,8 +510,6 @@ ubsa_request(struct ubsa_softc *sc, u_in usbd_status err; /* The huawei Exxx devices support none of these tricks */ - if (sc->sc_huawei) - return (0); req.bmRequestType = UT_WRITE_VENDOR_DEVICE; req.bRequest = request; USETW(req.wValue, value); Modified: head/sys/dev/usb/usbdevs ============================================================================== --- head/sys/dev/usb/usbdevs Thu Oct 9 20:51:25 2008 (r183734) +++ head/sys/dev/usb/usbdevs Thu Oct 9 21:25:01 2008 (r183735) @@ -1434,7 +1434,7 @@ product HTC SMARTPHONE 0x0a51 SmartPhon /* HUAWEI products */ product HUAWEI MOBILE 0x1001 Huawei Mobile -product HUAWEI E270 0x1003 Huawei HSPA modem +product HUAWEI E220 0x1003 Huawei HSDPA modem /* HUAWEI 3com products */ product HUAWEI3COM WUB320G 0x0009 Aolynk WUB320g Modified: head/sys/i386/conf/GENERIC ============================================================================== --- head/sys/i386/conf/GENERIC Thu Oct 9 20:51:25 2008 (r183734) +++ head/sys/i386/conf/GENERIC Thu Oct 9 21:25:01 2008 (r183735) @@ -304,6 +304,7 @@ device urio # Diamond Rio 500 MP3 play device uscanner # Scanners # USB Serial devices device ucom # Generic com ttys +device u3g # USB-based 3G modems (Option, Huawei, Sierra) device uark # Technologies ARK3116 based serial adapters device ubsa # Belkin F5U103 and compatible serial adapters device uftdi # For FTDI usb serial adapters Modified: head/sys/modules/Makefile ============================================================================== --- head/sys/modules/Makefile Thu Oct 9 20:51:25 2008 (r183734) +++ head/sys/modules/Makefile Thu Oct 9 21:25:01 2008 (r183735) @@ -269,6 +269,7 @@ SUBDIR= ${_3dfx} \ twe \ tx \ txp \ + u3g \ uark \ uart \ ubsa \ Added: head/sys/modules/u3g/Makefile ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/sys/modules/u3g/Makefile Thu Oct 9 21:25:01 2008 (r183735) @@ -0,0 +1,8 @@ +# $FreeBSD$ + +.PATH: ${.CURDIR}/../../dev/usb + +KMOD= u3g +SRCS= u3g.c ucomvar.h opt_usb.h device_if.h bus_if.h usbdevs.h + +.include _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" ------------------------------------------------------- _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From fbsd at dannysplace.net Tue Oct 28 11:18:20 2008 From: fbsd at dannysplace.net (Danny Carroll) Date: Tue Oct 28 11:18:33 2008 Subject: PCI-X SATA Card + Server Recommendation In-Reply-To: <20081026125017.GA88016@icarus.home.lan> References: <20081026125017.GA88016@icarus.home.lan> Message-ID: <4906F123.30908@dannysplace.net> Jeremy Chadwick wrote: > These are cards I can recommend for your situation. Yes, they do RAID, > they all support JBOD; just plug the disks in and go. > > http://www.highpoint-tech.com/USA/series_2000.htm > HighPoint RocketRAID 2210 (hptrr(4) driver; be sure to read NOTES) > HighPoint RocketRAID 2220 (hptrr(4) driver; be sure to read NOTES) > HighPoint RocketRAID 2224 (hptrr(4) driver; be sure to read NOTES) > HighPoint RocketRAID 2240 (hptrr(4) driver; be sure to read NOTES) > > http://www.areca.com.tw/products/pcix.htm > Areca ARC-1110 (arcmsr(4) driver) > Areca ARC-1120 (arcmsr(4) driver) > Areca ARC-1130 (arcmsr(4) driver) > Areca ARC-1160 (arcmsr(4) driver) > Areca ARC-1130ML (arcmsr(4) driver) > Areca ARC-1160ML (arcmsr(4) driver) One other thing that those in the know might be able to answer for me. When thinking about ZFS or Geom (or even vinum!) and a decent SATA card in JBOD mode: What happens with the write caching? Do the caches only work when you build an array? If they also work in JBOD mode, then I guess it is important to disable all write caching (can you even do that with these cards?) unless you also buy the BBU? I'd be interested to know for sure so I know if I must shell out for a BBU as well as the card itself.... -D From fbsd at dannysplace.net Tue Oct 28 11:18:22 2008 From: fbsd at dannysplace.net (Danny Carroll) Date: Tue Oct 28 11:18:34 2008 Subject: PCI-X SATA Card + Server Recommendation In-Reply-To: <20081026125017.GA88016@icarus.home.lan> References: <20081026125017.GA88016@icarus.home.lan> Message-ID: <4906EF86.7050702@dannysplace.net> Jeremy Chadwick wrote: > http://www.highpoint-tech.com/USA/series_2000.htm > HighPoint RocketRAID 2210 (hptrr(4) driver; be sure to read NOTES) > HighPoint RocketRAID 2220 (hptrr(4) driver; be sure to read NOTES) > HighPoint RocketRAID 2224 (hptrr(4) driver; be sure to read NOTES) > HighPoint RocketRAID 2240 (hptrr(4) driver; be sure to read NOTES) Can you (or someone else) please tell me a little more about this? Do the drives (in JBOD mode) present themselves as part of the ATA bus or SCSI bus? Do you know if NCQ and SATA-II support is in there? Can you do Smart queries to the drives? > http://www.areca.com.tw/products/pcix.htm > Areca ARC-1110 (arcmsr(4) driver) > Areca ARC-1120 (arcmsr(4) driver) > Areca ARC-1130 (arcmsr(4) driver) > Areca ARC-1160 (arcmsr(4) driver) > Areca ARC-1130ML (arcmsr(4) driver) > Areca ARC-1160ML (arcmsr(4) driver) > > The FreeBSD community members who have Areca cards have been thrilled > with them, and *do* use the native RAID features reliably. Personally I am torn right now between an Adapted 31205, a 3ware 9650SE-12ML and an Areca 1230. I'm going for ZFS so I really want a fast SATA card with lots of ports (8-12) and no raid functionality. There is not much out there and it's all expensive. > There's a bunch of Supermicro systems which meet your needs. The first > four are very new, and use the Intel X48 chipset. I don't know of any > FreeBSD people using the X7SBU board, but I'm sure there are some. > > http://www.supermicro.com/products/system/1U/ > Supermicro SuperServer 5015B-URB (~US$975) > Supermicro SuperServer 5015B-NTRB (~US$975) > Supermicro SuperServer 5015B-UB (~US$785) > Supermicro SuperServer 5015B-NTB (~US$785) > Supermicro SuperServer 5015B-MTB (~US$655) > > bsdhwmon(8) supports the 5015B-MTB (X7SBi), but doesn't support the > others (X7SBU). If someone out there has an X7SBU, please get in > touch with me so I can add support for it! I have an X7SBE, so I'm, keen to try out bsdhwmon. Installing right now... Out of curiosity (and way OT)I get a lot of ACPI messages on my supermicro board: Oct 22 11:50:29 nas kernel: ACPI Error (psargs-0459): [\_SB_.PCI0.PSMS] Namespace lookup failure, AE_NOT_FOUND Oct 22 11:50:29 nas kernel: ACPI Error (psparse-0626): Method parse/execution failed [\_SB_.PCI0.LPC0.SIO_.MSE0._STA] (Node 0xffffff00013a6260), AE_NOT_FOUND If you use supermicro boards a lot then perhaps you have seen these? -D From koitsu at FreeBSD.org Tue Oct 28 12:14:27 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Tue Oct 28 12:14:34 2008 Subject: PCI-X SATA Card + Server Recommendation In-Reply-To: <4906EF86.7050702@dannysplace.net> References: <20081026125017.GA88016@icarus.home.lan> <4906EF86.7050702@dannysplace.net> Message-ID: <20081028121425.GA48941@icarus.home.lan> On Tue, Oct 28, 2008 at 08:55:02PM +1000, Danny Carroll wrote: > Jeremy Chadwick wrote: > > http://www.highpoint-tech.com/USA/series_2000.htm > > HighPoint RocketRAID 2210 (hptrr(4) driver; be sure to read NOTES) > > HighPoint RocketRAID 2220 (hptrr(4) driver; be sure to read NOTES) > > HighPoint RocketRAID 2224 (hptrr(4) driver; be sure to read NOTES) > > HighPoint RocketRAID 2240 (hptrr(4) driver; be sure to read NOTES) > > Can you (or someone else) please tell me a little more about this? Do > the drives (in JBOD mode) present themselves as part of the ATA bus or > SCSI bus? The hptrr(4) driver relies on SCSI CAM/da(4), and does not use the ata(4) driver in any way. > Do you know if NCQ and SATA-II support is in there? Re: SATAII: if the product data sheet or the user manual states the card supports SATA300, then yes. Re: NCQ: the user manual probably answers this question, or a FAQ/KB article. I hope you're not planning on disabling write caching on your disks (as people often ask if controllers or drives supports command queueing so they can do this. NCQ does not provide the amount of performance increase like SCSI command queuing does. On the other hand, TCQ (often found on SAS drives) does.) > Can you do Smart queries to the drives? I have no idea. I suppose it would have to support pass(4), or provide the functionality itself (Areca controllers do the latter). > > http://www.areca.com.tw/products/pcix.htm > > Areca ARC-1110 (arcmsr(4) driver) > > Areca ARC-1120 (arcmsr(4) driver) > > Areca ARC-1130 (arcmsr(4) driver) > > Areca ARC-1160 (arcmsr(4) driver) > > Areca ARC-1130ML (arcmsr(4) driver) > > Areca ARC-1160ML (arcmsr(4) driver) > > > > The FreeBSD community members who have Areca cards have been thrilled > > with them, and *do* use the native RAID features reliably. > > Personally I am torn right now between an Adapted 31205, a 3ware > 9650SE-12ML and an Areca 1230. I'm going for ZFS so I really want a > fast SATA card with lots of ports (8-12) and no raid functionality. I recommend avoiding Adaptec. I will repeat that: avoid Adaptec. You are not going to find a SATA card that has non-RAID capability with that amount of ports. Besides, it shouldn't matter to you if the card has RAID capability, because nothing forces you to use it. All that should matter to you is the following: * Is the card version/model supported under FreeBSD? * Does the card supports disks in a JBOD fashion (not part of an array)? * Can I get SMART stats from the drive (or via CLI; see below)? * Is there a native FreeBSD CLI binary for controlling features of the controller if I need it? > There is not much out there and it's all expensive. But neither of these are FreeBSD problems. The same would apply if you were using any operating system. > > There's a bunch of Supermicro systems which meet your needs. The first > > four are very new, and use the Intel X48 chipset. I don't know of any > > FreeBSD people using the X7SBU board, but I'm sure there are some. > > > > http://www.supermicro.com/products/system/1U/ > > Supermicro SuperServer 5015B-URB (~US$975) > > Supermicro SuperServer 5015B-NTRB (~US$975) > > Supermicro SuperServer 5015B-UB (~US$785) > > Supermicro SuperServer 5015B-NTB (~US$785) > > Supermicro SuperServer 5015B-MTB (~US$655) > > > > bsdhwmon(8) supports the 5015B-MTB (X7SBi), but doesn't support the > > others (X7SBU). If someone out there has an X7SBU, please get in > > touch with me so I can add support for it! > > I have an X7SBE, so I'm, keen to try out bsdhwmon. Installing right now... > > Out of curiosity (and way OT)I get a lot of ACPI messages on my > supermicro board: > > Oct 22 11:50:29 nas kernel: ACPI Error (psargs-0459): [\_SB_.PCI0.PSMS] > Namespace lookup failure, AE_NOT_FOUND > Oct 22 11:50:29 nas kernel: ACPI Error (psparse-0626): Method > parse/execution failed [\_SB_.PCI0.LPC0.SIO_.MSE0._STA] (Node > 0xffffff00013a6260), AE_NOT_FOUND > > If you use supermicro boards a lot then perhaps you have seen these? I have not seen these on any of our systems. Chances are they're ACPI or AML errors which can be fixed by the vendor with a BIOS upgrade. I would recommend asking about this on freebsd-acpi instead. -- | 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 Tue Oct 28 12:19:16 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Tue Oct 28 12:19:22 2008 Subject: PCI-X SATA Card + Server Recommendation In-Reply-To: <4906F123.30908@dannysplace.net> References: <20081026125017.GA88016@icarus.home.lan> <4906F123.30908@dannysplace.net> Message-ID: <20081028121914.GB48941@icarus.home.lan> On Tue, Oct 28, 2008 at 09:01:55PM +1000, Danny Carroll wrote: > Jeremy Chadwick wrote: > > These are cards I can recommend for your situation. Yes, they do RAID, > > they all support JBOD; just plug the disks in and go. > > > > http://www.highpoint-tech.com/USA/series_2000.htm > > HighPoint RocketRAID 2210 (hptrr(4) driver; be sure to read NOTES) > > HighPoint RocketRAID 2220 (hptrr(4) driver; be sure to read NOTES) > > HighPoint RocketRAID 2224 (hptrr(4) driver; be sure to read NOTES) > > HighPoint RocketRAID 2240 (hptrr(4) driver; be sure to read NOTES) > > > > http://www.areca.com.tw/products/pcix.htm > > Areca ARC-1110 (arcmsr(4) driver) > > Areca ARC-1120 (arcmsr(4) driver) > > Areca ARC-1130 (arcmsr(4) driver) > > Areca ARC-1160 (arcmsr(4) driver) > > Areca ARC-1130ML (arcmsr(4) driver) > > Areca ARC-1160ML (arcmsr(4) driver) > > One other thing that those in the know might be able to answer for me. > When thinking about ZFS or Geom (or even vinum!) and a decent SATA card > in JBOD mode: > > What happens with the write caching? Do the caches only work when you > build an array? If they also work in JBOD mode, then I guess it is > important to disable all write caching (can you even do that with these > cards?) unless you also buy the BBU? This has been discussed recently on -hardware. I will stand firm on my statement: don't disable write caching on disks. http://lists.freebsd.org/pipermail/freebsd-hardware/2008-October/005450.html -- | 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 groot at kde.org Tue Oct 28 12:19:30 2008 From: groot at kde.org (Adriaan de Groot) Date: Tue Oct 28 12:19:37 2008 Subject: PCI-X SATA Card + Server Recommendation In-Reply-To: References: <20081026125017.GA88016@icarus.home.lan> Message-ID: <200810281517.37226.groot@kde.org> [ re-visiting this thread ] On Sunday 26 October 2008, Charles Sprickman wrote: > > Stay away from this card. Jeremy, any specific reasons for that? Yes, it's a low-end piece of crap consumer electronics, but as a straightforward 4-port SATA card it seems to do well enough. It's just part of ata(4) and one of the ones I've got has been up for 395 days driving striped mirrored GEOMs under reasonable (but certainly not high) load. > Will do. ?Google was very unhelpful with finding info on Silicon Image and > FreeBSD, so I thank you for that. Strange. They're supported out of the box in ata(4) now. The right search string would have been "sii 3124 driver freebsd" which turns up some of my older work on it, or http://www.freebsd.org/cgi/man.cgi?query=ata&apropos=0&sektion=4&manpath=FreeBSD+7.0-RELEASE&format=html which will get you the ata(4) manpage which now lists 3124 and 3132. Again, this is a low end cheap-ass SATA card. Unlike the RTL 8139 it doesn't "redefine the notion of low-end", but it seems to get the job done. -- These are your friends - Adem GPG: FEA2 A3FE Adriaan de Groot From fbsd at dannysplace.net Tue Oct 28 12:22:57 2008 From: fbsd at dannysplace.net (Danny Carroll) Date: Tue Oct 28 12:23:03 2008 Subject: PCI-X SATA Card + Server Recommendation In-Reply-To: <20081028121425.GA48941@icarus.home.lan> References: <20081026125017.GA88016@icarus.home.lan> <4906EF86.7050702@dannysplace.net> <20081028121425.GA48941@icarus.home.lan> Message-ID: <4907041E.4050705@dannysplace.net> Jeremy Chadwick wrote: > Re: SATAII: if the product data sheet or the user manual states the card > supports SATA300, then yes. > > Re: NCQ: the user manual probably answers this question, or a FAQ/KB > article. I hope you're not planning on disabling write caching on your > disks (as people often ask if controllers or drives supports command > queueing so they can do this. NCQ does not provide the amount of > performance increase like SCSI command queuing does. On the other > hand, TCQ (often found on SAS drives) does.) That's a good point about the cache, I forgot about the one on the drives. > I have no idea. I suppose it would have to support pass(4), or provide > the functionality itself (Areca controllers do the latter). 3ware as well I am told. > I recommend avoiding Adaptec. I will repeat that: avoid Adaptec. I appreciate the comment, can you tell me why or is it a personal preference? > You are not going to find a SATA card that has non-RAID capability with > that amount of ports. Besides, it shouldn't matter to you if the card > has RAID capability, because nothing forces you to use it. All that > should matter to you is the following: > > * Is the card version/model supported under FreeBSD? > * Does the card supports disks in a JBOD fashion (not part of an array)? > * Can I get SMART stats from the drive (or via CLI; see below)? > * Is there a native FreeBSD CLI binary for controlling features of the > controller if I need it? Yup. > >> There is not much out there and it's all expensive. > > But neither of these are FreeBSD problems. The same would apply if you > were using any operating system. No, I agree it is not a Freebsd problem. It's everything to do with demand at the moment. > I have not seen these on any of our systems. Chances are they're ACPI > or AML errors which can be fixed by the vendor with a BIOS upgrade. > I would recommend asking about this on freebsd-acpi instead. Thanks! -D From fbsd at dannysplace.net Tue Oct 28 12:24:40 2008 From: fbsd at dannysplace.net (Danny Carroll) Date: Tue Oct 28 12:24:46 2008 Subject: PCI-X SATA Card + Server Recommendation In-Reply-To: <20081028121914.GB48941@icarus.home.lan> References: <20081026125017.GA88016@icarus.home.lan> <4906F123.30908@dannysplace.net> <20081028121914.GB48941@icarus.home.lan> Message-ID: <4907048D.6080800@dannysplace.net> Jeremy Chadwick wrote: > This has been discussed recently on -hardware. I will stand firm on my > statement: don't disable write caching on disks. Ok, but what about the write caching on the array controller. Is it for writes in JBOD mode or simply when configured as an array? Just trying to figure out if I should be budgeting for a BBU as well. -D From koitsu at FreeBSD.org Tue Oct 28 12:30:38 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Tue Oct 28 12:30:45 2008 Subject: PCI-X SATA Card + Server Recommendation In-Reply-To: <200810281517.37226.groot@kde.org> References: <20081026125017.GA88016@icarus.home.lan> <200810281517.37226.groot@kde.org> Message-ID: <20081028123037.GA49386@icarus.home.lan> On Tue, Oct 28, 2008 at 03:17:36PM +0100, Adriaan de Groot wrote: > [ re-visiting this thread ] > > On Sunday 26 October 2008, Charles Sprickman wrote: > > > Stay away from this card. > > Jeremy, any specific reasons for that? Yes, it's a low-end piece of crap > consumer electronics, but as a straightforward 4-port SATA card it seems to > do well enough. It's just part of ata(4) and one of the ones I've got has > been up for 395 days driving striped mirrored GEOMs under reasonable (but > certainly not high) load. A large number of problems people report to the FreeBSD lists involve Silicon Image controllers. There are confirmed problems within certain models of their SATA controllers which cause silent data corruption and other issues, affecting Linux, FreeBSD, and Windows. See "Product Alerts" below, then try Googling "silicon image corruption". I'm not talking out of my ass. http://en.wikipedia.org/wiki/Silicon_Image If you have one that works, "good for you". :-) But based on the above, I **will NOT** recommend these controllers. I'm not even willing to trust later revisions like the 3124; not catching data corruption during QA/testing is simply unacceptable regardless of what "class" of product it is. I would be very surprised to hear someone advocate use of Silicon Image controllers after reading the above. -- | 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 michel.belanger at mediom.qc.ca Tue Oct 28 19:00:27 2008 From: michel.belanger at mediom.qc.ca (=?ISO-8859-1?Q?Michel_B=E9langer?=) Date: Tue Oct 28 19:00:34 2008 Subject: My 3 Questions Message-ID: <490759B3.4030705@mediom.qc.ca> I want buying a server for running FreeBSD 7.0 but i have three questions. 1- Freebsd can support Dual Quad Xeon CPU (QUAD CORE XEON E5405 2.0G 12M 1333 XD VT) ? 2- FreeBSD can support this network card (DUAL INTEL 82563EB GIGABIT ETHERNET 10/100/1000) ? 3- What is the best FreeBSD version (i386, amd64) ? If a install amd64, the 32 bits application works well ? I have searching on google but i did'nt find answer. Thanks a lot. MICHEL B?LANGER From note at note2email.com Tue Oct 28 17:43:57 2008 From: note at note2email.com (note@note2email.com) Date: Tue Oct 28 20:44:51 2008 Subject: PCI-X SATA Card + Server Recommendation Message-ID: <49074acebedc1@note2email.com> > A large number of problems people report to the FreeBSD lists involve > Silicon Image controllers. There are confirmed problems within certain > models of their SATA controllers which cause silent data corruption and > other issues, affecting Linux, FreeBSD, and Windows. See "Product > Alerts" below, then try Googling "silicon image corruption". I'm not > talking out of my ass. > > http://en.wikipedia.org/wiki/Silicon_Image Which points to http://osdir.com/ml/ide/2005-03/msg00126.html which says: "It's basically because of faulty SATA implementation of the affected seagate hard drives combined with standard-compliant but peculiar behavior of silicon image controllers." So you blame Silicon Image for Seagate's bug. Nice. I have been using the 3512 with Seagate drives and NetBSD for several years with zero data corruption. If FreeBSD has problems with Silicon Image controllers it isn't Silicon Image's fault. Word is that the 3124 and 3132 are much better and faster than the 1st generation controllers such as my 3512. They are documented, datasheets are available on the web, unlike some SATA controllers. I would consider them. > This has been discussed recently on -hardware. I will stand firm on my > statement: don't disable write caching on disks. > > http://lists.freebsd.org/pipermail/freebsd-hardware/2008-October/005450.html Write caching on disks enabled: data loss, fast writes Write caching on disks disabled, no NCQ: no data loss, slow writes Write caching on disks disabled, NCQ: no data loss, fast writes Sorry, but data loss is simply not acceptable. When can we expect NCQ support for FreeBSD? The ability to turn the disk's write cache on and off is essential. I haven't found a USB-to-SATA bridge that allows this, limiting their usefulness to testing new disks, mounting read-only or for data which is expendable. > Besides, it shouldn't matter to you if the card > has RAID capability, because nothing forces you to use it. The problem is that cards with real RAID are far more expensive. ____________________________________________________________________ Do not reply to this message. If this e-mail is unsolicited and you would like to report it please visit the following link: http://www.note2email.com/flag/id/2870b2637347d14b1a7e14eef1416313 This note was sent to : freebsd-hardware@freebsd.org from the following IP address: 208.100.241.202 (c) 2008 note2email.com. All rights reserved. From alive at dienub.org Tue Oct 28 23:14:17 2008 From: alive at dienub.org (Rada alive) Date: Tue Oct 28 23:14:24 2008 Subject: My 3 Questions In-Reply-To: <490759B3.4030705@mediom.qc.ca> References: <490759B3.4030705@mediom.qc.ca> Message-ID: On Tue, Oct 28, 2008 at 7:28 PM, Michel B?langer < michel.belanger@mediom.qc.ca> wrote: > I want buying a server for running FreeBSD 7.0 but i have three questions. > > 1- Freebsd can support Dual Quad Xeon CPU (QUAD CORE XEON E5405 2.0G 12M > 1333 XD VT) ? > 2- FreeBSD can support this network card (DUAL INTEL 82563EB GIGABIT > ETHERNET 10/100/1000) ? > 3- What is the best FreeBSD version (i386, amd64) ? If a install amd64, > the 32 bits application works well ? > > I have searching on google but i did'nt find answer. > > Thanks a lot. > > MICHEL B?LANGER > > _______________________________________________ > 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 > " > 1. Yes 2. Yes 3. Use amd64, install libs32. If you can, compile your applications from ports. If proprietary, check ports or ask software vendor if they have 64bit binaries. From koitsu at FreeBSD.org Tue Oct 28 23:42:35 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Tue Oct 28 23:42:42 2008 Subject: PCI-X SATA Card + Server Recommendation In-Reply-To: <49074acebedc1@note2email.com> References: <49074acebedc1@note2email.com> Message-ID: <20081028232948.GA61480@icarus.home.lan> On Tue, Oct 28, 2008 at 10:24:30AM -0700, note@note2email.com wrote: > > A large number of problems people report to the FreeBSD lists involve > > Silicon Image controllers. There are confirmed problems within certain > > models of their SATA controllers which cause silent data corruption and > > other issues, affecting Linux, FreeBSD, and Windows. See "Product > > Alerts" below, then try Googling "silicon image corruption". I'm not > > talking out of my ass. > > > > http://en.wikipedia.org/wiki/Silicon_Image > > Which points to > > http://osdir.com/ml/ide/2005-03/msg00126.html > > which says: > > "It's basically because of faulty SATA implementation of the > affected seagate hard drives combined with standard-compliant > but peculiar behavior of silicon image controllers." > > So you blame Silicon Image for Seagate's bug. Nice. Wow, thanks, I see you really did your research before posting this. Let's ignore the hundreds of posts between users on forums talking about data corruption on SiI controllers with NON-SEAGATE disks, as well as an equally large number of posts on Linux mailing lists with the same facts. I will not let you hold me responsible for Wikipedia's reference material being sparse. I'll also point you to similar 'misleading' information about nForce controllers and Maxtor disks. There are known incompatibilities with some versions of nVidia MCPs and Maxtor disks. The problem has to do with NCQ support, but absolutely no one is certain if the problem is with nVidia's chip or Maxtor's firmware. nVidia has done absolutely nothing about the problem, while Maxtor has documented the problem and offers -- assuming you ask for it -- a disk firmware that works around the problem by changing the NCQ implementation. But the same disks work fine on Intel, VIA, SiS, Promise, and even SiI controllers. So who's to blame? :-) I really, *really* hope you get my point. Let's not turn this thread a "usual BSD thread", where a bunch of administrators sit around and do burn-outs in parking lots, getting absolutely nothing accomplished other than gnashing of teeth. > I have been using the 3512 with Seagate drives and NetBSD for > several years with zero data corruption. If FreeBSD has problems > with Silicon Image controllers it isn't Silicon Image's fault. I've provided enough evidence that the problem has NOTHING to do with FreeBSD. The problem is OS-independent. Since you're explicitly ignoring this fact, I have to classify this as trolling. > Word is that the 3124 and 3132 are much better and faster than the > 1st generation controllers such as my 3512. They are documented, > datasheets are available on the web, unlike some SATA controllers. > I would consider them. > > > This has been discussed recently on -hardware. I will stand firm on my > > statement: don't disable write caching on disks. > > > > http://lists.freebsd.org/pipermail/freebsd-hardware/2008-October/005450.html > > Write caching on disks enabled: data loss, fast writes > Write caching on disks disabled, no NCQ: no data loss, slow writes > Write caching on disks disabled, NCQ: no data loss, fast writes > > Sorry, but data loss is simply not acceptable. When can we expect NCQ > support for FreeBSD? Matt Dillon and some others have explained why disabling write caching is simply unreasonable, and why it gives people a false sense of security ("if I disable write caching, my data will ALWAYS be written to the disk!" is simply untrue). It doesn't even matter if you have a controller that has a BBU. > The ability to turn the disk's write cache on and off is essential. See kern/127717. Despite not being an advocate of disabling write caching, I've no problem extending tools/drivers to provide features. > I haven't found a USB-to-SATA bridge that allows this, limiting > their usefulness to testing new disks, mounting read-only or > for data which is expendable. > > > Besides, it shouldn't matter to you if the card > > has RAID capability, because nothing forces you to use it. > > The problem is that cards with real RAID are far more expensive. The OP has specific requirements for SATA controllers. The specifics greatly limit what choices he has. The fact of the matter is, there are only two companies which make ""affordable"" consumer SATA controllers: Promise and HighPoint. I'm specifically excluding SiI from the list for what at this point should be obvious. -- | 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 peterjeremy at optushome.com.au Wed Oct 29 14:08:07 2008 From: peterjeremy at optushome.com.au (Peter Jeremy) Date: Wed Oct 29 14:08:14 2008 Subject: PCI-X SATA Card + Server Recommendation In-Reply-To: <49074acebedc1@note2email.com> References: <49074acebedc1@note2email.com> Message-ID: <20081029061606.GN1137@server.vk2pj.dyndns.org> On 2008-Oct-28 10:24:30 -0700, "note@note2email.com" wrote: >Sorry, but data loss is simply not acceptable. So, you're happy to use SATA controllers with known data corruption problems but the use of write caching (which may result in data loss if there's a power loss) is "not acceptable". > When can we expect NCQ support for FreeBSD? When someone implements it. If it's a serious issue for you, either implement it or offer to pay someone to implement it for you. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. -------------- 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/20081029/60617b55/attachment.pgp From groot at kde.org Wed Oct 29 15:24:18 2008 From: groot at kde.org (Adriaan de Groot) Date: Wed Oct 29 15:24:26 2008 Subject: PCI-X SATA Card + Server Recommendation In-Reply-To: <20081029061606.GN1137@server.vk2pj.dyndns.org> References: <49074acebedc1@note2email.com> <20081029061606.GN1137@server.vk2pj.dyndns.org> Message-ID: <200810291632.06845.groot@kde.org> On Wednesday 29 October 2008 07:16:06 am Peter Jeremy wrote: > > ?When can we expect NCQ support for FreeBSD? > > When someone implements it. ?If it's a serious issue for you, either > implement it or offer to pay someone to implement it for you. If I remember correctly -- this is from nearly a year ago -- Soren was going to do so for at least AHCI (Intel) things. It's a pretty big change in the way ata(4) works, because of the pervasive assumption that one ATA command results in one corresponding response. That assumption made doing FIS-based things (for SiI3124 support, oh irony in this thread) complicated as well. I really don't know what the status of this work on Soren's side is. Nor do I remember anything of my attempts to work NCQ into the SiI driver parts of ata(4). I think I ran quite quickly into issues of simply remembering which slots were in use; it was going to be a horrific hack on my part in any case. Note that drivers like the Areca one do do NCQ, but they hook in to the SCSI subsystem where that fits better with the design as a whole. [ade] -- Adriaan de Groot From steve at kcilink.com Wed Oct 29 18:12:12 2008 From: steve at kcilink.com (Steve Scally) Date: Wed Oct 29 18:12:19 2008 Subject: Dell PE1900 DAT72 drive failing FreeBSD 7 Message-ID: All, I have a Dell PE1900 with an internal DAT72 drive. The drive appears to fail midway through a dump after detecting the end of tape and prompting for a new one. There is no specific sequence in which it fails. Sometimes it could be after the first tape or after the second tape. Dumps will complete for weeks at a time with no issue then suddenly fail. There are no logs with errors except for the dmesg.boot file after a reboot, which fixes the issue. Before the dump there are these two lines: "ahd0: SCSI Cell parity error SSTAT3 == 0x2 ahd0: Missing case in ahd_handle_scsiint. status = 0" I did a search and found this posting http://lists.freebsd.org/pipermail/freebsd-scsi/2007-February/002869.html which suggests to upgrade the BIOS and any other firmware. I tried this suggestion and updated the Dell BIOS from v2.0.1 to v2.3.1 and the Base Management Controller firmware from v1.69 to v2.09 however, the issue still occurs. Durning this time all other services such as mail, samba, and nfs remain functional. The only service affected is SSH. When you try to login after the failure occurs you receive "PTY allocation request failed on channel 0." Thank you in advance for the help. If you need anymore information let me know. Steve Uname -a FreeBSD 7.0-PRERELEASE #1: Wed Jan 23 22:52:15 EST 2008 amd64 pciconf -l | grep ahd ahd0@pci0:8:1:0: class=0x010000 card=0x00409005 chip=0x80169005 rev=0x10 hdr=0x00 ahd1@pci0:8:1:1: class=0x010000 card=0x00409005 chip=0x80169005 rev=0x10 hdr=0x00 ahd0: port 0xec00-0xecff, 0xe800-0xe8ff mem 0xfcb7e000-0xfcb7ffff irq 32 at device 1.0 on pci8 ahd0: [ITHREAD] >>>>>>>>>>>>>>>>>> Dump Card State Begins <<<<<<<<<<<<<<<<< ahd0: Dumping Card State at program address 0x1c Mode 0x33 Card was paused INTSTAT[0x8] SELOID[0x9] SELID[0x0] HS_MAILBOX[0x0] INTCTL[0x80] SEQINTSTAT[0x0] SAVED_MODE[0x11] DFFSTAT[0x33] SCSISIGI[0x18] SCSIPHASE[0x0] SCSIBUS[0x80] LASTPHASE[0x1] SCSISEQ0[0x40] SCSISEQ1[0x12] SEQCTL0[0x0] SEQINTCTL[0x0] SEQ_FLAGS[0xc0] SEQ_FLAGS2[0x0] QFREEZE_COUNT[0x0] KERNEL_QFREEZE_COUNT[0x0] MK_MESSAGE_SCB[0xff00] MK_MESSAGE_SCSIID[0xff] SSTAT0[0x10] SSTAT1[0x0] SSTAT2[0x0] SSTAT3[0x0] PERRDIAG[0x0] SIMODE1[0xa4] LQISTAT0[0x0] LQISTAT1[0x0] LQISTAT2[0x0] LQOSTAT0[0x0] LQOSTAT1[0x0] LQOSTAT2[0x0] SCB Count = 512 CMDS_PENDING = 8 LASTSCB 0xffff CURRSCB 0x1f7 NEXTSCB 0x0 qinstart = 16 qinfifonext = 16 QINFIFO: WAITING_TID_QUEUES: 9 ( 0x1f7 ) 10 ( 0x1f6 ) 11 ( 0x1f5 ) 12 ( 0x1f4 ) 13 ( 0x1f3 ) 14 ( 0x1f2 ) 15 ( 0x1f1 ) 6 ( 0x1f9 ) Pending list: 505 FIFO_USE[0x0] SCB_CONTROL[0x40] SCB_SCSIID[0x67] 497 FIFO_USE[0x0] SCB_CONTROL[0x40] SCB_SCSIID[0xf7] 498 FIFO_USE[0x0] SCB_CONTROL[0x40] SCB_SCSIID[0xe7] 499 FIFO_USE[0x0] SCB_CONTROL[0x40] SCB_SCSIID[0xd7] 500 FIFO_USE[0x0] SCB_CONTROL[0x40] SCB_SCSIID[0xc7] 501 FIFO_USE[0x0] SCB_CONTROL[0x40] SCB_SCSIID[0xb7] 502 FIFO_USE[0x0] SCB_CONTROL[0x40] SCB_SCSIID[0xa7] 503 FIFO_USE[0x0] SCB_CONTROL[0x40] SCB_SCSIID[0x97] Total 8 Kernel Free SCB lists: Any Device: 504 506 507 508 509 510 511 496 495 494 493 492 491 490 489 488 487 486 485 484 483 482 481 480 479 478 477 476 475 474 473 472 471 470 469 468 467 466 465 464 463 462 461 460 459 458 457 456 455 454 453 452 451 450 449 448 447 446 445 444 443 442 441 440 439 438 437 436 435 434 433 432 431 430 429 428 427 426 425 424 423 422 421 420 419 418 417 416 415 414 413 412 411 410 409 408 407 406 405 404 403 402 401 400 399 398 397 396 395 394 393 392 391 390 389 388 387 386 385 384 383 382 381 380 379 378 377 376 375 374 373 372 371 370 369 368 367 366 365 364 363 362 361 360 359 358 357 356 355 354 353 352 351 350 349 348 347 346 345 344 343 342 341 340 339 338 337 336 335 334 333 332 331 330 329 328 327 326 325 324 323 322 321 320 319 318 317 316 315 314 313 312 311 310 309 308 307 306 305 304 303 302 301 300 299 298 297 296 295 294 293 292 291 290 289 288 287 286 285 284 283 282 281 280 279 278 277 276 275 274 273 272 271 270 269 268 267 266 265 264 263 262 261 260 259 258 257 256 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Sequencer Complete DMA-inprog list: Sequencer Complete list: Sequencer DMA-Up and Complete list: Sequencer On QFreeze and Complete list: ahd0: FIFO0 Free, LONGJMP == 0x80ff, SCB 0x0 SEQIMODE[0x3f] SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89] SG_CACHE_SHADOW[0x2] SG_STATE[0x0] DFFSXFRCTL[0x0] SOFFCNT[0x0] MDFFSTAT[0x5] SHADDR = 0x00, SHCNT = 0x0 HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10] ahd0: FIFO1 Free, LONGJMP == 0x8063, SCB 0x1f9 SEQIMODE[0x3f] SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89] SG_CACHE_SHADOW[0x2] SG_STATE[0x0] DFFSXFRCTL[0x0] SOFFCNT[0x0] MDFFSTAT[0x5] SHADDR = 0x00, SHCNT = 0x0 HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10] LQIN: 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 ahd0: LQISTATE = 0x0, LQOSTATE = 0x0, OPTIONMODE = 0x42 ahd0: OS_SPACE_CNT = 0x20 MAXCMDCNT = 0x0 ahd0: SAVED_SCSIID = 0x0 SAVED_LUN = 0x0 SIMODE0[0xc] CCSCBCTL[0x4] ahd0: REG0 == 0x1f9, SINDEX = 0x10e, DINDEX = 0x10e ahd0: SCBPTR == 0x1f7, SCB_NEXT == 0xffc0, SCB_NEXT2 == 0x1f6 CDB 12 0 0 0 24 0 STACK: 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 <<<<<<<<<<<<<<<<< Dump Card State Ends >>>>>>>>>>>>>>>>>> sa0: Removable Sequential Access SCSI-3 device sa0: 80.000MB/s transfers (40.000MHz, offset 32, 16bit) From jhb at freebsd.org Thu Oct 30 13:36:24 2008 From: jhb at freebsd.org (John Baldwin) Date: Thu Oct 30 13:36:36 2008 Subject: Dell PE1900 DAT72 drive failing FreeBSD 7 In-Reply-To: References: Message-ID: <200810300928.18621.jhb@freebsd.org> On Wednesday 29 October 2008 01:54:26 pm Steve Scally wrote: > All, > > I have a Dell PE1900 with an internal DAT72 drive. The drive appears > to fail midway through a dump after detecting the end of tape and > prompting for a new one. There is no specific sequence in which it > fails. Sometimes it could be after the first tape or after the second > tape. Dumps will complete for weeks at a time with no issue then > suddenly fail. There are no logs with errors except for the > dmesg.boot file after a reboot, which fixes the issue. Before the > dump there are these two lines: > "ahd0: SCSI Cell parity error SSTAT3 == 0x2 > ahd0: Missing case in ahd_handle_scsiint. status = 0" You will probably have better lucking sending this to freebsd-scsi@FreeBSD.org as I know several SCSI folks are on that list, but I'm not sure they are on this one. > I did a search and found this posting http://lists.freebsd.org/pipermail/freebsd-scsi/2007-February/002869.html > which suggests to upgrade the BIOS and any other firmware. I tried > this suggestion and updated the Dell BIOS from v2.0.1 to v2.3.1 and > the Base Management Controller firmware from v1.69 to v2.09 however, > the issue still occurs. Durning this time all other services such as > mail, samba, and nfs remain functional. The only service affected is > SSH. When you try to login after the failure occurs you receive "PTY > allocation request failed on channel 0." Thank you in advance for the > help. If you need anymore information let me know. > > Steve > > Uname -a > FreeBSD 7.0-PRERELEASE #1: Wed Jan 23 22:52:15 EST 2008 amd64 > > pciconf -l | grep ahd > > ahd0@pci0:8:1:0: class=0x010000 card=0x00409005 chip=0x80169005 > rev=0x10 hdr=0x00 > ahd1@pci0:8:1:1: class=0x010000 card=0x00409005 chip=0x80169005 > rev=0x10 hdr=0x00 > > ahd0: port 0xec00-0xecff, > 0xe800-0xe8ff mem 0xfcb7e000-0xfcb7ffff irq 32 at device 1.0 on pci8 > ahd0: [ITHREAD] > > >>>>>>>>>>>>>>>>>> Dump Card State Begins <<<<<<<<<<<<<<<<< > ahd0: Dumping Card State at program address 0x1c Mode 0x33 > Card was paused > INTSTAT[0x8] SELOID[0x9] SELID[0x0] HS_MAILBOX[0x0] > INTCTL[0x80] SEQINTSTAT[0x0] SAVED_MODE[0x11] DFFSTAT[0x33] > SCSISIGI[0x18] SCSIPHASE[0x0] SCSIBUS[0x80] LASTPHASE[0x1] > SCSISEQ0[0x40] SCSISEQ1[0x12] SEQCTL0[0x0] SEQINTCTL[0x0] > SEQ_FLAGS[0xc0] SEQ_FLAGS2[0x0] QFREEZE_COUNT[0x0] > KERNEL_QFREEZE_COUNT[0x0] MK_MESSAGE_SCB[0xff00] MK_MESSAGE_SCSIID[0xff] > SSTAT0[0x10] SSTAT1[0x0] SSTAT2[0x0] SSTAT3[0x0] PERRDIAG[0x0] > SIMODE1[0xa4] LQISTAT0[0x0] LQISTAT1[0x0] LQISTAT2[0x0] > LQOSTAT0[0x0] LQOSTAT1[0x0] LQOSTAT2[0x0] > > SCB Count = 512 CMDS_PENDING = 8 LASTSCB 0xffff CURRSCB 0x1f7 NEXTSCB > 0x0 > qinstart = 16 qinfifonext = 16 > QINFIFO: > WAITING_TID_QUEUES: > 9 ( 0x1f7 ) > 10 ( 0x1f6 ) > 11 ( 0x1f5 ) > 12 ( 0x1f4 ) > 13 ( 0x1f3 ) > 14 ( 0x1f2 ) > 15 ( 0x1f1 ) > 6 ( 0x1f9 ) > Pending list: > 505 FIFO_USE[0x0] SCB_CONTROL[0x40] SCB_SCSIID[0x67] > 497 FIFO_USE[0x0] SCB_CONTROL[0x40] SCB_SCSIID[0xf7] > 498 FIFO_USE[0x0] SCB_CONTROL[0x40] SCB_SCSIID[0xe7] > 499 FIFO_USE[0x0] SCB_CONTROL[0x40] SCB_SCSIID[0xd7] > 500 FIFO_USE[0x0] SCB_CONTROL[0x40] SCB_SCSIID[0xc7] > 501 FIFO_USE[0x0] SCB_CONTROL[0x40] SCB_SCSIID[0xb7] > 502 FIFO_USE[0x0] SCB_CONTROL[0x40] SCB_SCSIID[0xa7] > 503 FIFO_USE[0x0] SCB_CONTROL[0x40] SCB_SCSIID[0x97] > Total 8 > Kernel Free SCB lists: > Any Device: 504 506 507 508 509 510 511 496 495 494 493 492 491 490 > 489 488 487 486 485 484 483 482 481 480 479 478 477 476 475 474 473 > 472 471 470 469 468 467 466 465 464 463 462 461 460 459 458 457 456 > 455 454 453 452 451 450 449 448 447 446 445 444 443 442 441 440 439 > 438 437 436 435 434 433 432 431 430 429 428 427 426 425 424 423 422 > 421 420 419 418 417 416 415 414 413 412 411 410 409 408 407 406 405 > 404 403 402 401 400 399 398 397 396 395 394 393 392 391 390 389 388 > 387 386 385 384 383 382 381 380 379 378 377 376 375 374 373 372 371 > 370 369 368 367 366 365 364 363 362 361 360 359 358 357 356 355 354 > 353 352 351 350 349 348 347 346 345 344 343 342 341 340 339 338 337 > 336 335 334 333 332 331 330 329 328 327 326 325 324 323 322 321 320 > 319 318 317 316 315 314 313 312 311 310 309 308 307 306 305 304 303 > 302 301 300 299 298 297 296 295 294 293 292 291 290 289 288 287 286 > 285 284 283 282 281 280 279 278 277 276 275 274 273 272 271 270 269 > 268 267 266 265 264 263 262 261 260 259 258 257 256 255 254 253 252 > 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 > 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 > 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 > 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 > 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 > 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 > 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 > 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 > 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 > 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 > 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 > 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 > 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 > 2 1 0 > Sequencer Complete DMA-inprog list: > Sequencer Complete list: > Sequencer DMA-Up and Complete list: > Sequencer On QFreeze and Complete list: > > ahd0: FIFO0 Free, LONGJMP == 0x80ff, SCB 0x0 > SEQIMODE[0x3f] SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89] > SG_CACHE_SHADOW[0x2] SG_STATE[0x0] DFFSXFRCTL[0x0] > SOFFCNT[0x0] MDFFSTAT[0x5] SHADDR = 0x00, SHCNT = 0x0 > HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10] > > ahd0: FIFO1 Free, LONGJMP == 0x8063, SCB 0x1f9 > SEQIMODE[0x3f] SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89] > SG_CACHE_SHADOW[0x2] SG_STATE[0x0] DFFSXFRCTL[0x0] > SOFFCNT[0x0] MDFFSTAT[0x5] SHADDR = 0x00, SHCNT = 0x0 > HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10] > LQIN: 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 > 0x0 0x0 0x0 0x0 > ahd0: LQISTATE = 0x0, LQOSTATE = 0x0, OPTIONMODE = 0x42 > ahd0: OS_SPACE_CNT = 0x20 MAXCMDCNT = 0x0 > ahd0: SAVED_SCSIID = 0x0 SAVED_LUN = 0x0 > SIMODE0[0xc] > CCSCBCTL[0x4] > ahd0: REG0 == 0x1f9, SINDEX = 0x10e, DINDEX = 0x10e > ahd0: SCBPTR == 0x1f7, SCB_NEXT == 0xffc0, SCB_NEXT2 == 0x1f6 > CDB 12 0 0 0 24 0 > STACK: 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 > <<<<<<<<<<<<<<<<< Dump Card State Ends >>>>>>>>>>>>>>>>>> > > sa0: Removable Sequential Access > SCSI-3 device sa0: 80.000MB/s transfers (40.000MHz, offset 32, 16bit) > _______________________________________________ > 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" > -- John Baldwin From fbsd at dannysplace.net Thu Oct 30 20:14:55 2008 From: fbsd at dannysplace.net (Danny Carroll) Date: Thu Oct 30 20:15:02 2008 Subject: Areca vs. ZFS performance testing. Message-ID: <490A782F.9060406@dannysplace.net> Hello all, I've just become the proud new owner of an Areca 1231-ML which I plan to use to set up an office server. I'm very curious as to how ZFS compares to a hardware solution so I plan to run some tests before I put this thing to work. The purpose of this email is to find out if anyone would like to see specific things tested as well as perhaps get some advice on how to get the most information out of the tests. My setup: Supermicro X7SBE board with 2Gb ram and an E6550 Core 2 Duo. FreeBSD 7.0-Stable compiled with amd64 sources from mid August. 1 x ST9120822AS 120gb disk (for the OS) For the array(s) 9 x ST31000340AS 1tb disks 1 x ST31000333AS 1tb disk (trying to swap this for a ST31000340AS) My thoughts are to do the following tests with bonnie++: 1 5 disk Areca Raid5 2 5 Disk ZFS RaidZ1 (Connected to Areca in JBOD mode) 3 5 Disk ZFS RaidZ1 (Connected to ICH9 On board SATA controller) 4 5 disk Areca Raid6 5 5 Disk ZFS RaidZ2 (Connected to Areca in JBOD mode) 6 5 Disk ZFS RaidZ2 (Connected to ICH9 On board SATA controller) 7 10 disk Areca Raid5 8 10 Disk ZFS RaidZ1 (Connected to Areca in JBOD mode) 9 10 disk Areca Raid6 10 10 Disk ZFS RaidZ2 (Connected to Areca in JBOD mode) My aim is to see what sort of performance gain you get by buying an Areca card for use in JBOD as well as seeing how ZFS compares to the hardware solution which offers write caching etc. I'm really only interested in testing ZFS's volume management performance, so for that reason I will also put ZFS on the Areca Raid drives. Not sure if it's a good idea to create 2 Raid drives and stripe them or simply use 1 large disk and give it to ZFS. Any thoughts on this setup as well as advice on what options to give to bonnie++ (or suggestions on another disk testing package) are very welcome. I do have some concern about the size of the eventual array and ZFS' use of system memory. Are there guidelines available that give advice on how much memory a box should have with large ZFS arrays? Can an AMD64 kernel make use of memory above 2g? -D From koitsu at FreeBSD.org Thu Oct 30 20:32:10 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Thu Oct 30 20:32:22 2008 Subject: Areca vs. ZFS performance testing. In-Reply-To: <490A782F.9060406@dannysplace.net> References: <490A782F.9060406@dannysplace.net> Message-ID: <20081031033208.GA21220@icarus.home.lan> Cross-posting this to freebsd-fs, as I'm sure people there will have other recommendations. (This is one of those rare cross-posting situations.....) On Fri, Oct 31, 2008 at 01:14:55PM +1000, Danny Carroll wrote: > I've just become the proud new owner of an Areca 1231-ML which I plan to > use to set up an office server. > > I'm very curious as to how ZFS compares to a hardware solution so I plan > to run some tests before I put this thing to work. > > The purpose of this email is to find out if anyone would like to see > specific things tested as well as perhaps get some advice on how to get > the most information out of the tests. > > My setup: > Supermicro X7SBE board with 2Gb ram and an E6550 Core 2 Duo. > FreeBSD 7.0-Stable compiled with amd64 sources from mid August. > 1 x ST9120822AS 120gb disk (for the OS) > For the array(s) > 9 x ST31000340AS 1tb disks > 1 x ST31000333AS 1tb disk (trying to swap this for a ST31000340AS) > > My thoughts are to do the following tests with bonnie++: > 1 5 disk Areca Raid5 > 2 5 Disk ZFS RaidZ1 (Connected to Areca in JBOD mode) > 3 5 Disk ZFS RaidZ1 (Connected to ICH9 On board SATA controller) > 4 5 disk Areca Raid6 > 5 5 Disk ZFS RaidZ2 (Connected to Areca in JBOD mode) > 6 5 Disk ZFS RaidZ2 (Connected to ICH9 On board SATA controller) > 7 10 disk Areca Raid5 > 8 10 Disk ZFS RaidZ1 (Connected to Areca in JBOD mode) > 9 10 disk Areca Raid6 > 10 10 Disk ZFS RaidZ2 (Connected to Areca in JBOD mode) > > My aim is to see what sort of performance gain you get by buying an > Areca card for use in JBOD as well as seeing how ZFS compares to the > hardware solution which offers write caching etc. I'm really only > interested in testing ZFS's volume management performance, so for that > reason I will also put ZFS on the Areca Raid drives. Not sure if it's a > good idea to create 2 Raid drives and stripe them or simply use 1 large > disk and give it to ZFS. > > Any thoughts on this setup as well as advice on what options to give to > bonnie++ (or suggestions on another disk testing package) are very welcome. I think these sets of tests are good. There are some others I'd like to see, but they'd only be applicable if the 1231-ML has hardware cache. I can mention what those are if the card does have hardware caching. > I do have some concern about the size of the eventual array and ZFS' use > of system memory. Are there guidelines available that give advice on > how much memory a box should have with large ZFS arrays? The general concept is: "the more RAM the better". However, if you're using RELENG_7, then there's not much point (speaking solely about ZFS) to getting more than maybe 3 or 4GB; you're still limited to a 2GB kmap maximum. Regarding size of the array vs. memory usage: as long as you tune kmem and ZFS ARC, you shouldn't have much trouble. There have been some key people reporting lately that they run very large ZFS arrays without issue, with proper tuning. Also, just a reminder: do not pick a value of 2048M for kmem_size or kmem_size_max; the machine won't boot/work. You shouldn't go above something like 1536M, although some have tuned slightly above that with success. (You need to remember that there is more to kernel memory allocation than just this, so you don't want to exhaust it all assigning it to kmap. Hope that makes sense...) > Can an AMD64 kernel make use of memory above 2g? Only on CURRENT; 7.x cannot, and AFAIK, will never be able to, as the engineering efforts required to fix it are too great. I look forward to seeing your numbers. Someone here might be able to compile them into some graphs and other whatnots to make things easier for future readers. Thanks for doing all of this! -- | 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 Thu Oct 30 21:08:01 2008 From: fbsd at dannysplace.net (Danny Carroll) Date: Thu Oct 30 21:08:08 2008 Subject: Areca vs. ZFS performance testing. In-Reply-To: <20081031033208.GA21220@icarus.home.lan> References: <490A782F.9060406@dannysplace.net> <20081031033208.GA21220@icarus.home.lan> Message-ID: <490A849C.7030009@dannysplace.net> Jeremy Chadwick wrote: > I think these sets of tests are good. There are some others I'd like to > see, but they'd only be applicable if the 1231-ML has hardware cache. I > can mention what those are if the card does have hardware caching. The card comes standard with 256Mb of cache. >> I do have some concern about the size of the eventual array and ZFS' use >> of system memory. Are there guidelines available that give advice on >> how much memory a box should have with large ZFS arrays? > > The general concept is: "the more RAM the better". However, if you're > using RELENG_7, then there's not much point (speaking solely about ZFS) > to getting more than maybe 3 or 4GB; you're still limited to a 2GB kmap > maximum. > > Regarding size of the array vs. memory usage: as long as you tune kmem > and ZFS ARC, you shouldn't have much trouble. There have been some > key people reporting lately that they run very large ZFS arrays without > issue, with proper tuning. I followed the recommendations here: http://wiki.freebsd.org/ZFSTuningGuide vm.kmem_size="1024M" vm.kmem_size_max="1024M" vfs.zfs.debug=1 And : kern.maxvnodes=400000 I have not added the following because they were listed in the i386 section. (These values were quoted for a machine with 768Mb of ram) vfs.zfs.arc_max="40M" vfs.zfs.vdev.cache.size="5M" Am I right in assuming these do not apply to amd64? The article was not specific. > > Also, just a reminder: do not pick a value of 2048M for kmem_size or > kmem_size_max; the machine won't boot/work. You shouldn't go above > something like 1536M, although some have tuned slightly above that > with success. (You need to remember that there is more to kernel > memory allocation than just this, so you don't want to exhaust it all > assigning it to kmap. Hope that makes sense...) It makes sense. I'm using 1024 at the moment, but I've never really looked into what memory is actually being used. Tuning advice here would be well received :-) >> Can an AMD64 kernel make use of memory above 2g? > > Only on CURRENT; 7.x cannot, and AFAIK, will never be able to, as the > engineering efforts required to fix it are too great. > > I look forward to seeing your numbers. Someone here might be able to > compile them into some graphs and other whatnots to make things easier > for future readers. Ahhh, well, that will eventually decide my upgrade path when RELENG_8 is released and stable. > Thanks for doing all of this! No worries, hopefully it will be useful information to future google searches :-P -D From koitsu at FreeBSD.org Thu Oct 30 21:34:14 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Thu Oct 30 21:34:26 2008 Subject: Areca vs. ZFS performance testing. In-Reply-To: <490A849C.7030009@dannysplace.net> References: <490A782F.9060406@dannysplace.net> <20081031033208.GA21220@icarus.home.lan> <490A849C.7030009@dannysplace.net> Message-ID: <20081031043412.GA22289@icarus.home.lan> On Fri, Oct 31, 2008 at 02:07:56PM +1000, Danny Carroll wrote: > Jeremy Chadwick wrote: > > I think these sets of tests are good. There are some others I'd like to > > see, but they'd only be applicable if the 1231-ML has hardware cache. I > > can mention what those are if the card does have hardware caching. > > The card comes standard with 256Mb of cache. I'd like to see the performance difference between these scenarios: - Memory cache enabled on Areca, write caching enabled on disks - Memory cache enabled on Areca, write caching disabled on disks - Memory cache disabled on Areca, write caching enabled on disks - Memory cache disabled on Areca, write caching disabled on disks I don't know if the controller will let you disable use of memory cache, but I'm hoping it does. I'm pretty sure it lets you disable disk write caching in its BIOS or via the CLI utility. > >> I do have some concern about the size of the eventual array and ZFS' use > >> of system memory. Are there guidelines available that give advice on > >> how much memory a box should have with large ZFS arrays? > > > > The general concept is: "the more RAM the better". However, if you're > > using RELENG_7, then there's not much point (speaking solely about ZFS) > > to getting more than maybe 3 or 4GB; you're still limited to a 2GB kmap > > maximum. > > > > Regarding size of the array vs. memory usage: as long as you tune kmem > > and ZFS ARC, you shouldn't have much trouble. There have been some > > key people reporting lately that they run very large ZFS arrays without > > issue, with proper tuning. > > I followed the recommendations here: > http://wiki.freebsd.org/ZFSTuningGuide > > vm.kmem_size="1024M" > vm.kmem_size_max="1024M" > vfs.zfs.debug=1 > > And : kern.maxvnodes=400000 > > I have not added the following because they were listed in the i386 > section. (These values were quoted for a machine with 768Mb of ram) > vfs.zfs.arc_max="40M" > vfs.zfs.vdev.cache.size="5M" > > Am I right in assuming these do not apply to amd64? The article was not > specific. All of the tuning variables apply to i386 and amd64. You do not need the vfs.zfs.debug variable; I'm not sure why you enabled that. I imagine it will have some impact on performance. I do not know anything about kern.maxvnodes, or vfs.zfs.vdev.cache.size. The tuning variables I advocate for a system with 2GB of RAM or more, on RELENG_7, are: vm.kmem_size="1536M" vm.kmem_size_max="1536M" vfs.zfs.arc_min="16M" vfs.zfs.arc_max="64M" vfs.zfs.prefetch_disable="1" You can gradually increase arc_min and arc_max by ~16MB increments as you see fit; you should see general performance improvements as they get larger (more data being kept in the ARC), but don't get too crazy. I've tuned arc_max up to 128MB before with success, but I don't want to try anything larger without decreasing kmem_size_*. > > Also, just a reminder: do not pick a value of 2048M for kmem_size or > > kmem_size_max; the machine won't boot/work. You shouldn't go above > > something like 1536M, although some have tuned slightly above that > > with success. (You need to remember that there is more to kernel > > memory allocation than just this, so you don't want to exhaust it all > > assigning it to kmap. Hope that makes sense...) > > It makes sense. I'm using 1024 at the moment, but I've never really > looked into what memory is actually being used. > > Tuning advice here would be well received :-) The only reason you need to adjust kmem_size and kmem_size_max is to increase the amount of available kmap memory which ZFS relies heavily on. If the values are too low, under heavy I/O, the kernel will panic with kmem exhaustion messages (see the ZFS Wiki for what some look like, or my Wiki). I would recommend you stick with a consistent set of loader.conf tuning variables, and focus entirely on comparing the performance of ZFS on the Areca controller vs. the ICH controller. You can perform a "ZFS tuning comparison" later. One step at a time; don't over-exert yourself quite yet. :-) You can add raidz2 to this comparison list too if you feel it's worthwhile, but I think most people will be using raidz1. -- | 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 Thu Oct 30 21:47:49 2008 From: fbsd at dannysplace.net (Danny Carroll) Date: Thu Oct 30 21:47:56 2008 Subject: Areca vs. ZFS performance testing. In-Reply-To: <20081031043412.GA22289@icarus.home.lan> References: <490A782F.9060406@dannysplace.net> <20081031033208.GA21220@icarus.home.lan> <490A849C.7030009@dannysplace.net> <20081031043412.GA22289@icarus.home.lan> Message-ID: <490A8DFB.8030405@dannysplace.net> Jeremy Chadwick wrote: > On Fri, Oct 31, 2008 at 02:07:56PM +1000, Danny Carroll wrote: > - Memory cache enabled on Areca, write caching enabled on disks > - Memory cache enabled on Areca, write caching disabled on disks > - Memory cache disabled on Areca, write caching enabled on disks > - Memory cache disabled on Areca, write caching disabled on disks Does it matter what type of disk we are talking about? What I mean is, do you want to see this with both Raid5 and Raid6 arrays? Also, I'm pretty sure that in JBod mode the cache (on the card) will do nothing. But I am not certain, so I'll do the tests there as well. What about stripe sizes? I mainly use big files so I was going to stripe accordingly. But the bonnie++ tests might give strange results in that case. > I don't know if the controller will let you disable use of memory cache, > but I'm hoping it does. I'm pretty sure it lets you disable disk > write caching in its BIOS or via the CLI utility. > It's been a while since I've had a hardware raid card. I'll see what is available. > All of the tuning variables apply to i386 and amd64. > > You do not need the vfs.zfs.debug variable; I'm not sure why you enabled > that. I imagine it will have some impact on performance. Consider it gone. > I do not know anything about kern.maxvnodes, or vfs.zfs.vdev.cache.size. > At the moment I am not hitting anywhere near the max vnodes setting. So I think it is irrelevant. > The tuning variables I advocate for a system with 2GB of RAM or more, > on RELENG_7, are: > > vm.kmem_size="1536M" > vm.kmem_size_max="1536M" > vfs.zfs.arc_min="16M" > vfs.zfs.arc_max="64M" > vfs.zfs.prefetch_disable="1" > > You can gradually increase arc_min and arc_max by ~16MB increments as > you see fit; you should see general performance improvements as they > get larger (more data being kept in the ARC), but don't get too crazy. > I've tuned arc_max up to 128MB before with success, but I don't want > to try anything larger without decreasing kmem_size_*. What is the arc? Is it the ZFS file cache? > The only reason you need to adjust kmem_size and kmem_size_max is to > increase the amount of available kmap memory which ZFS relies heavily > on. If the values are too low, under heavy I/O, the kernel will panic > with kmem exhaustion messages (see the ZFS Wiki for what some look > like, or my Wiki). > > I would recommend you stick with a consistent set of loader.conf > tuning variables, and focus entirely on comparing the performance of > ZFS on the Areca controller vs. the ICH controller. Once I am settled on a 'starting point' I won't be altering it for the tests. > You can perform a "ZFS tuning comparison" later. One step at a time; > don't over-exert yourself quite yet. :-) Yeah, this is weekend stuff for me at the moment, it will take me some time to get things done. Firstly I need to figure out how I am going to hook up 10 drives to my system. I don't have the drive-bay space and I am not shelling out for a new case so I am hunting around for an ancient external disk cabinet. > You can add raidz2 to this comparison list too if you feel it's > worthwhile, but I think most people will be using raidz1. I might as well do both. -D From fbsd at dannysplace.net Thu Oct 30 21:55:02 2008 From: fbsd at dannysplace.net (Danny Carroll) Date: Thu Oct 30 21:55:14 2008 Subject: Areca vs. ZFS performance testing. In-Reply-To: <20081031043412.GA22289@icarus.home.lan> References: <490A782F.9060406@dannysplace.net> <20081031033208.GA21220@icarus.home.lan> <490A849C.7030009@dannysplace.net> <20081031043412.GA22289@icarus.home.lan> Message-ID: <490A8FAD.8060009@dannysplace.net> Jeremy Chadwick wrote: > > I'd like to see the performance difference between these scenarios: > > - Memory cache enabled on Areca, write caching enabled on disks > - Memory cache enabled on Areca, write caching disabled on disks > - Memory cache disabled on Areca, write caching enabled on disks > - Memory cache disabled on Areca, write caching disabled on disks > > I don't know if the controller will let you disable use of memory cache, > but I'm hoping it does. I'm pretty sure it lets you disable disk > write caching in its BIOS or via the CLI utility. The manual suggests that the write cache can be disabled. Perhaps there is no read cache for this card. -D From koitsu at FreeBSD.org Fri Oct 31 02:35:27 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Fri Oct 31 02:35:34 2008 Subject: Areca vs. ZFS performance testing. In-Reply-To: <580369.72525.qm@web36607.mail.mud.yahoo.com> References: <580369.72525.qm@web36607.mail.mud.yahoo.com> Message-ID: <20081031093524.GA27933@icarus.home.lan> On Fri, Oct 31, 2008 at 01:44:25AM -0700, Simun Mikecin wrote: > Jeremy Chadwick wrote: > > The tuning variables I advocate for a system with 2GB of RAM or more, > > on RELENG_7, are: > > vm.kmem_size="1536M" > > vm.kmem_size_max="1536M" > > There is no point in setting vm.kmem_size_max. Setting vm.kmem_size is > enough. vm.kmem_size_max is used for auto-tuning of kmem size which is > in this case actually overriden by manually setting vm.kmem_size. This information hasn't been mentioned by anyone before, so it's news to me. > > vfs.zfs.arc_min="16M" > > vfs.zfs.arc_max="64M" > > vfs.zfs.prefetch_disable="1" > > You can gradually increase arc_min and arc_max by ~16MB increments as > > you see fit; you should see general performance improvements as they > > get larger (more data being kept in the ARC), but don't get too crazy. > > I've tuned arc_max up to 128MB before with success, but I don't want > > to try anything larger without decreasing kmem_size_*. > > Can you explain why would you have to decrease kmem_size to use larger > ARC? AFAIK it should be contrary to what you are saying: when you use > larger kmem_size you can also use larger arc_max. Well, my understanding (which is probably wrong) is that the memory used for the ARC is somehow separate from that of the kmap. I was under the impression the kmap was used by ZFS for other things, and did not include ARC. If I'm incorrect, please state so -- it's cool, I just need to know. :-) > My suggestion if you are using kmem_size of 1536M would be to not tune > arc_min and arc_max if your system isn't panicing. If it does you > should try decreasing arc_max (from it's default value) until it > doesn't. People have advocated increasing arc_min and arc_max in the past, citing large performance gains as arc_max gets larger; you might see people mentioning that they see great performance increases when increasing arc_max from 64M to 128M. My understanding is that increasing the ARC provides more actual cached data that ZFS can reference (vs. pulling it off disk). Again, if I'm incorrect, please state so. -- | 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 numisemis at yahoo.com Fri Oct 31 02:11:07 2008 From: numisemis at yahoo.com (Simun Mikecin) Date: Fri Oct 31 04:24:50 2008 Subject: Areca vs. ZFS performance testing. Message-ID: <580369.72525.qm@web36607.mail.mud.yahoo.com> Jeremy Chadwick wrote: > The tuning variables I advocate for a system with 2GB of RAM or more, > on RELENG_7, are: > vm.kmem_size="1536M" > vm.kmem_size_max="1536M" There is no point in setting vm.kmem_size_max. Setting vm.kmem_size is enough. vm.kmem_size_max is used for auto-tuning of kmem size which is in this case actually overriden by manually setting vm.kmem_size. > vfs.zfs.arc_min="16M" > vfs.zfs.arc_max="64M" > vfs.zfs.prefetch_disable="1" > You can gradually increase arc_min and arc_max by ~16MB increments as > you see fit; you should see general performance improvements as they > get larger (more data being kept in the ARC), but don't get too crazy. > I've tuned arc_max up to 128MB before with success, but I don't want > to try anything larger without decreasing kmem_size_*. Can you explain why would you have to decrease kmem_size to use larger ARC? AFAIK it should be contrary to what you are saying: when you use larger kmem_size you can also use larger arc_max. My suggestion if you are using kmem_size of 1536M would be to not tune arc_min and arc_max if your system isn't panicing. If it does you should try decreasing arc_max (from it's default value) until it doesn't. From numisemis at yahoo.com Fri Oct 31 04:57:19 2008 From: numisemis at yahoo.com (Simun Mikecin) Date: Fri Oct 31 05:04:35 2008 Subject: Areca vs. ZFS performance testing. Message-ID: <174490.95560.qm@web36607.mail.mud.yahoo.com> Jeremy Chadwick wrote: > Well, my understanding (which is probably wrong) is that the memory > used for the ARC is somehow separate from that of the kmap. I was > under the impression the kmap was used by ZFS for other things, and > did not include ARC. kmem is used by ARC. You can check your total kmem usage by ZFS using 'vmstat -m' under the line that says 'solaris'. > People have advocated increasing arc_min and arc_max in the past, citing > large performance gains as arc_max gets larger; you might see people > mentioning that they see great performance increases when increasing > arc_max from 64M to 128M. My understanding is that increasing the ARC > provides more actual cached data that ZFS can reference (vs. pulling it > off disk). Again, if I'm incorrect, please state so. You are correct about the benefits of increasing arc_max. I don't know of any benefits of tuning arc_min. Maybe someone else can answer this. By default on 7-STABLE arc_max will be 3/4 of kmem_size. So if you are using 1536M for kmem_size, arc_max will be 1152M by default. But some people will maybe need to lower it to avoid panic during heavy I/O since in those scenarios ARC cache size could for short periods of time be larger than arc_max and reach kmem limit. From ivoras at freebsd.org Fri Oct 31 06:08:15 2008 From: ivoras at freebsd.org (Ivan Voras) Date: Fri Oct 31 06:08:22 2008 Subject: Areca vs. ZFS performance testing. In-Reply-To: <490A782F.9060406@dannysplace.net> References: <490A782F.9060406@dannysplace.net> Message-ID: Danny Carroll wrote: > Any thoughts on this setup as well as advice on what options to give to > bonnie++ (or suggestions on another disk testing package) are very welcome. I'd suggest two more tests, because bonnie++ won't tell you the performance of random IO and file system overhead: 1) randomIO: http://arctic.org/~dean/randomio/ 2) blogbench: http://www.pureftpd.org/project/blogbench Be sure to select appropriate parameters for both (and the same parameters in every test so they can be compared) and study how they are used so you don't, for example, benchmark your system drive instead of the array :) ! (try not to put the system on the array - use the array only for benchmarks). For example, use blogbench "-c 30 -i 20 -r 40 -W 5 -w 5" to simulate a read-mostly environment. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 252 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-hardware/attachments/20081031/298ddd54/signature.pgp From grarpamp at gmail.com Fri Oct 31 09:53:52 2008 From: grarpamp at gmail.com (grarpamp) Date: Fri Oct 31 09:53:58 2008 Subject: PCI-X SATA Card Message-ID: http://www.supermicro.com/products/accessories/addon/AoC-SAT2-MV8.cfm supermicro aoc-sat2-mv8 marvell 88sx6081, 8port, jbod, 64bit/133mhz, $95 Search the recent FreeBSD lists for it, seems to work. Hope to have a few soon. From grarpamp at gmail.com Fri Oct 31 09:59:20 2008 From: grarpamp at gmail.com (grarpamp) Date: Fri Oct 31 09:59:27 2008 Subject: Benchmark tools: was Areca vs ZFS Message-ID: Don't randomio, blogbench [and bonnie] pretty much do a subset of what iozone does? iozone.org: Read, write, re-read, re-write, read backwards, read strided, fread, fwrite, random read/write, pread/pwrite variants From grarpamp at gmail.com Fri Oct 31 10:13:54 2008 From: grarpamp at gmail.com (grarpamp) Date: Fri Oct 31 10:14:01 2008 Subject: PCI-X SATA Card Message-ID: http://www.supermicro.com/products/accessories/addon/AoC-SAT2-MV8.cfm supermicro aoc-sat2-mv8 marvell 88sx6081, 8port, jbod, 64bit/133mhz, $95 Search the recent FreeBSD lists for it, seems to work. Hope to have a few soon.