From owner-freebsd-hardware@FreeBSD.ORG Sun Jul 20 16:27:33 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E416137B401 for ; Sun, 20 Jul 2003 16:27:33 -0700 (PDT) Received: from mx0.gmx.net (mx0.gmx.de [213.165.64.100]) by mx1.FreeBSD.org (Postfix) with SMTP id C9A8043FA3 for ; Sun, 20 Jul 2003 16:27:32 -0700 (PDT) (envelope-from naroz@gmx.net) Received: (qmail 30620 invoked by uid 0); 20 Jul 2003 23:27:31 -0000 Date: Mon, 21 Jul 2003 01:27:32 +0200 (MEST) From: naroz@gmx.net To: freebsd-hardware@freebsd.org MIME-Version: 1.0 X-Priority: 3 (Normal) X-Authenticated-Sender: #0010008911@gmx.net X-Authenticated-IP: [212.202.49.114] Message-ID: <8776.1058743652@www56.gmx.net> X-Mailer: WWW-Mail 1.6 (Global Message Exchange) X-Flags: 0001 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Subject: IBM xSeries 345 freezes after 15 min. (4.8, 5.0, 5.1, current) X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Jul 2003 23:27:34 -0000 Hello, I'm really depressed and hope someone can help me here. Hardware: IBM xSeries 345 Server, 2 x Xeon 2.8 GHz 533, 2 x 512MB IBM ECC RAM, ICP Vortex GDT8514RZ RAID, 5 x IBM 36GB HDD U320. The server comes with an IBM serveRaid 5-i controller but I replaced it with the ICP controller, because of the known FreeBSD ips driver bug. I have installed FBSD 4.8 and everything looks fine. But it does not matter what I am doing after the installation, the server freezes after approximately 15 mins. The same happens with a new compiled kernel too. dmesg shows no problems. After that I tried to install fbsd 5.0, 5.1, current and I realized the same behavior - well, with a slight difference: the keyboard freezes at boot process: "atkbd unable to set the command byte". I musst disable ACPI to continue... Remarks - after the server freezes: - no warnings on screen - the server ist still pingable - the ssh client does not disconnect - I can still type but without reaction - system temperature is o.k. - I tried 2 different rams - I tried a different raid controller with external hdds linux runs without problems... Thanks. -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ Jetzt ein- oder umsteigen und USB-Speicheruhr als Prämie sichern! From owner-freebsd-hardware@FreeBSD.ORG Sun Jul 20 22:52:40 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3057F37B405 for ; Sun, 20 Jul 2003 22:52:40 -0700 (PDT) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 8C8B643FA3 for ; Sun, 20 Jul 2003 22:52:38 -0700 (PDT) (envelope-from alexander.pohoyda@gmx.net) Received: (qmail 31348 invoked by uid 65534); 21 Jul 2003 05:52:37 -0000 Received: from p508BF3D1.dip.t-dialin.net (EHLO oak.pohoyda.family) (80.139.243.209) by mail.gmx.net (mp006) with SMTP; 21 Jul 2003 07:52:37 +0200 Received: from oak.pohoyda.family (oak.pohoyda.family [127.0.0.1]) by oak.pohoyda.family (8.12.9/8.12.6) with ESMTP id h6L5qNKg000533; Mon, 21 Jul 2003 07:52:24 +0200 (CEST) (envelope-from apog@oak.pohoyda.family) Received: (from apog@localhost) by oak.pohoyda.family (8.12.9/8.12.9/Submit) id h6L5qK28000530; Mon, 21 Jul 2003 07:52:20 +0200 (CEST) Date: Mon, 21 Jul 2003 07:52:20 +0200 (CEST) Message-Id: <200307210552.h6L5qK28000530@oak.pohoyda.family> From: Alexander Pohoyda To: Josef Karthauser In-reply-to: <20030714174759.GA728@genius.tao.org.uk> (message from Josef Karthauser on Mon, 14 Jul 2003 18:47:59 +0100) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="2003-07-21T07:50:40+0200_=_d45e3272" References: <20030714174759.GA728@genius.tao.org.uk> cc: usb-bsd@eleetbsd.org cc: freebsd-hardware@FreeBSD.org Subject: Re: USB 2.0 Hub, patch for BSD stack {-3.7} X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jul 2003 05:52:40 -0000 > This is a multipart message in MIME format. --2003-07-21T07:50:40+0200_=_d45e3272 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit > > A new Cytronix 4-port USB 2.0 Hub (Cypress CY7C65640 chip) didn't > > work in both FreeBSD 4.8-STABLE and 5.0-CURRENT. > > > > I have managed to fix this with a following patch: > > --- uhub.c.orig Fri Jul 4 20:17:50 2003 > > +++ uhub.c Fri Jul 4 21:57:31 2003 > > @@ -185,7 +185,7 @@ > > /* Get hub descriptor. */ > > req.bmRequestType = UT_READ_CLASS_DEVICE; > > req.bRequest = UR_GET_DESCRIPTOR; > > - USETW(req.wValue, 0); > > + USETW2(req.wValue, (dev->address > 1 ? UDESC_HUB : 0), 0); > > USETW(req.wIndex, 0); > > USETW(req.wLength, USB_HUB_DESCRIPTOR_SIZE); > > DPRINTFN(1,("usb_init_hub: getting hub descriptor\n")); > > > > Hub is working now. > I've committed this to -current, and will MFC to -stable in a week or > so. Thank you. This patch, however, does not seem to be generic enough. It may even not work on other systems at all. I would really like to hear some explanation. Here are two minor patches. -- Alexander Pohoyda --2003-07-21T07:50:40+0200_=_d45e3272 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8bit Content-Disposition: attachment; filename="usr.src.sys.dev.usb.usbdevs.h.diff" Content-Description: usr.src.sys.dev.usb.usbdevs.h.diff --- usbdevs.h.orig Wed Jul 2 21:20:39 2003 +++ usbdevs.h Wed Jul 2 21:25:06 2003 @@ -544,6 +544,7 @@ #define USB_PRODUCT_CYPRESS_MOUSE 0x0001 /* mouse */ #define USB_PRODUCT_CYPRESS_THERMO 0x0002 /* thermometer */ #define USB_PRODUCT_CYPRESS_FMRADIO 0x1002 /* FM Radio */ +#define USB_PRODUCT_CYPRESS_SLIM_HUB 0x6560 /* Slim Hub, 4 ports */ /* Daisy Technology products */ #define USB_PRODUCT_DAISY_DMC 0x6901 /* USB MultiMedia Reader */ --2003-07-21T07:50:40+0200_=_d45e3272 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8bit Content-Disposition: attachment; filename="usr.src.sys.dev.usb.usbdevs_data.h.diff" Content-Description: usr.src.sys.dev.usb.usbdevs_data.h.diff --- usbdevs_data.h.orig Wed Jul 2 21:25:37 2003 +++ usbdevs_data.h Wed Jul 2 21:26:48 2003 @@ -640,6 +640,12 @@ "FM Radio", }, { + USB_VENDOR_CYPRESS, USB_PRODUCT_CYPRESS_SLIM_HUB, + 0, + "Cypress Semiconductor", + "Slim Hub", + }, + { USB_VENDOR_DAISY, USB_PRODUCT_DAISY_DMC, 0, "Daisy Technology", --2003-07-21T07:50:40+0200_=_d45e3272-- From owner-freebsd-hardware@FreeBSD.ORG Mon Jul 21 14:56:07 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C329F37B401 for ; Mon, 21 Jul 2003 14:56:07 -0700 (PDT) Received: from smtp012.mail.yahoo.com (smtp012.mail.yahoo.com [216.136.173.32]) by mx1.FreeBSD.org (Postfix) with SMTP id 20CAC43FB1 for ; Mon, 21 Jul 2003 14:56:07 -0700 (PDT) (envelope-from ARTV2@prodigy.net) Received: from unknown (HELO bloodygoat.prodigy.net) (ARTV2@prodigy.net@66.153.102.238 with login) by smtp.mail.vip.sc5.yahoo.com with SMTP; 21 Jul 2003 21:56:06 -0000 Message-Id: <5.2.0.9.2.20030721173238.00b2c3e8@wheresmymailserver.com> X-Sender: ARTV2@prodigy.net@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Mon, 21 Jul 2003 17:53:46 -0400 To: freebsd-hardware@freebsd.org From: "Artur V." Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: Logitech MouseMan Optical weird movement in KDE X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jul 2003 21:56:08 -0000 Hello. I tried looking through google and lots of other places, but I just couldn't find anything that addressed this specific problem. The problem is that when I start X and it goes into KDE, the mouse does work (Logitech MouseMan Optical), but when I move the mouse it's as if there is a 2-3 second delay in the movement. When I move the mouse, I don't see any path of the pointer, I just see the pointer 2-3 seconds later somewhere else on the screen. Note that the pointer does go where it's supposed to, it's not stuck in the upper left corner of the screen. I tried many different combinations of Protocols, Devices, and Drivers in XF86Config, but the combinations that did work don't fix the problem, the mouse movement is still jagged. Here's my current XF86Config: Section "Input Device" Identifier "Mouse0" Driver "mouse" Option "Protocol" "PS/2" #Also worked with Auto and Logitech Option "Device" "/dev/psm0" #Also worked with /dev/sysmouse EndSection The mouse is USB, but it's using the PS/2 adapter and is working perfectly in XP Pro and RedHat 9. I did try disabling moused but that didn't do anything. It doesn't seem to be an issue with the driver itself since it kind of works, maybe it's something to do with the Resolution of the mouse or just some extra config option for the driver? Any help is appreciated. Oh yeah, I'm using FreeBSD 5.1 (very nice KDE 3.1 desktop). Art ________________________________________________________________________________ There is a way that seems right to a man, but it's end is the way of death. Proverbs 16:25 NKJV From owner-freebsd-hardware@FreeBSD.ORG Tue Jul 22 03:43:58 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 13CE237B40B; Tue, 22 Jul 2003 03:43:58 -0700 (PDT) To: freebsd-hardware@FreeBSD.ORG Date: Tue, 22 Jul 2003 03:43:58 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20030722104358.13CE237B40B@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Subject: nVidia nForce2 potential owners please read X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jul 2003 10:43:58 -0000 Ok, so, it occured to me recently to try to convince nVidia to cough up programming documentation for their MCP ethernet controller. However, in order to do that, I need to be able to show that there is in fact sufficient demand for a FreeBSD (or even NetBSD or OpenBSD) driver to make it worth their while. nVidia doesn't listen to end users, only OEMs, and if the OEMs don't ask for support for a given OS, then support will not materialize. My goal is to convince them to pull their heads far enough out from between their legs to realize that Linux is not the be-all, end-all of open source, and that just because OEMs haven't mentioned FreeBSD, NetBSD or OpenBSD by name doesn't mean there aren't people who want MCP ethernet support in BSD. For this, I need your help. What I need is to gather proof of demand. What I want you do to is e-mail me (oh god, I can't believe I'm setting myself up for this) if: - You wanted to purchase a computer system with an nVidia nForce2 chipset but _didn't_ once you realized there was no BSD driver support for the on-board ethernet. - You bought an nVidia nForce2 system without realizing the on-board ethernet wasn't supported in BSD, were really disappointed once you found out, and complained to the manufacturer _OR_ you wanted to complain but didn't (because you weren't sure who to complain to, or you didn't get around to it yet, or you forgot, or you were abducted by aliens, or your dog ate your homework, or whatever). - You are in a position to approve or recommend the purchase of a computer system (or several systems) for your company, research group, espionage organization or other institution with money to spend, but won't because there's no BSD driver support for the on-board ethernet. - You never heard of nVidia, the nForce2 or the MCP ethernet controller until I mentioned them, but now that you have, and you've gone out and searched the interweb or visited your local computer store, you think they're all really spiffy and would happily buy an nForce2 system, but will hold off until there's a BSD driver for the on-board ethernet. - You want to give me free large bags of cash. Do *NOT* e-mail me if: - You want me to help you transfer a large sum of money out of Nigeria or some other African nation. - You think I'm dying of cancer and my dying wish is to collect e-mails from all over the world. - You think I want to MAKE MONEY FAST (if I wanted to do that, I wouldn't be writing device drivers for free). - You work for SCO or the RIAA. I think you get the idea. Consider it a petition of sorts. All I need is an e-mail from you, with a line or two explaining your particular circumstances. If you did not buy an nForce2-based computer due to lack of BSD support, say so. If you did, but you were pissed by the lack of BSD support, say so. If you told your friends, relatives, cow-orkers or purchasing office not to buy nForce2-based computers because of the lack of BSD support, say so. Cite the OEM vendor of the computer (or computer) and the model (or models) where appropriate. If more than one computer was involved, say how many. Every lost sale or dissatisfied customer I can present as evidence makes it that much easier to convince nVidia to unclench its tight... fists... and provide the documentation needed to write a BSD driver. NOTE: Please do make up phony e-mails just to bloat the figures or or cobble together a perl script to send me hundreds of auto-generated messages from forged addresses. Play nice, you scum. So, send your cards and letters to wpaul@freebsd.org. And don't be afraid to spread the word. Ask other people on other mailing lists. Ask your friends. Ask your enemies. Ask not what your OS can do for you: ask what you can do for your OS. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= "If stupidity were a handicap, you'd have the best parking spot." ============================================================================= From owner-freebsd-hardware@FreeBSD.ORG Wed Jul 23 15:21:55 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1AC8737B405; Wed, 23 Jul 2003 15:21:55 -0700 (PDT) Received: from borg-cube.com (netblock-66-159-209-110.dslextreme.com [66.159.209.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF41B43F85; Wed, 23 Jul 2003 15:21:53 -0700 (PDT) (envelope-from dburr@borg-cube.com) Received: from borg-cube.com (dburr@borg-cube.com [66.159.209.110]) by borg-cube.com (8.12.9/8.12.8) with ESMTP id h6NMLjwq037331; Wed, 23 Jul 2003 15:21:46 -0700 (PDT) (envelope-from dburr@borg-cube.com) Date: Wed, 23 Jul 2003 15:21:45 -0700 (PDT) From: Donald Burr of Borg To: FreeBSD Questions Message-ID: <20030723150744.L13432@borg-cube.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Status: No, hits=-100.0 required=3.0 tests=USER_IN_WHITELIST version=2.55 X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: FreeBSD Hardware Subject: Trouble reading BSD formatted HD in USB hard drive... but it works fine in Linux! X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 22:21:55 -0000 I recently decided to move one of the drives in my main system into an external USB 2.0 case. This was done so that I could take this drive between several systems (it is primarily used for backup and data archival). Yes, I know that 1394 (FireWire) would be faster, but not all of my machines are capable of it. And some of them literally do *not* have any free PCI slots which I could insert a 1394 card into. Like I said, the drive I installed in my USB case was already formatted as a FreeBSD drive. However, once I inserted it into a USB case, I am now unable to mount the drive again. Here are the appropriate dmesg printouts: umass0: Acer Labs USB 2.0 Storage Device, rev 2.00/1.03, addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-0 device da0: 650KB/s transfers da0: 76319MB (156301488 512 byte sectors: 64H 32S/T 10783C) da0: reading primary partition table: error reading fsbn 0 da0: reading primary partition table: error reading fsbn 0 (The "reading primary partition table" errors appear when I try the following mount command: mount -t ufs /dev/da0s1 /mnt/backup) Now, here's the kicker: I took the same drive over to a friend's Linux box (he is running Mandrake 9.1, with Linux kernel 2.4.21-0.13mdk). Linux has had the ability, for some time now, to mount UFS partitions. So I figured "what the heck" and decided that I'd try mounting it on his system. Here is the dmesg printouts from when I plugged in the USB hard drive to this Linux box: hub.c: new USB device 00:11.3-1, assigned address 2 usb.c: USB device 2 (vend/prod 0x402/0x5621) is not claimed by any active driver. Initializing USB Mass Storage driver... usb.c: registered new driver usb-storage scsi2 : SCSI emulation for USB Mass Storage devices Vendor: USB 2.0 Model: Storage Device Rev: 0100 Type: Direct-Access ANSI SCSI revision: 02 Attached scsi disk sda at scsi2, channel 0, id 0, lun 0 SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB) /dev/scsi/host2/bus0/target0/lun0: p1 p1: Aha! It seems that it is able to detect this disk just fine, and it does see a BSD filesystem on it. And sure enough, issuing the command "mount -t ufs -o ro,ufstype=44bsd /dev/sda1 /mnt/bsd" works fine!! I am able to read any and all files on this drive. I'd really like to get this sucker going under FreeBSD, but I am frankly out of ideas and at my wit's end. I am grateful to anyone who can offer any assistance or hints/clues at this point. The kernel configuration from my FreeBSD machine is available if anyone would like to see it. In short, I enabled all USB options in the kernel config file, as well as the SCSI base code. The USB case in question is a generic case labeled only "ME-320 Series 3.5"/5.25" External Enclosure." It is available in several configurations; mine is the single-port USB 1.1/2.0 configuration. It apparently uses an Acer Labs USB-to-IDE bridge chip, tho I can't tell what the chip's part number is. Thanks!! -- Donald Burr of Borg | FreeBSD: The Power to Serve! Website: http://www.borg-cube.com/ | http://www.freebsd.org/ PO Box 91212, Santa Barbara CA 93190-1212 \----------------------------- Tel: (805)563-0672 ICQ# 16997506 Present Day... Present Time! From owner-freebsd-hardware@FreeBSD.ORG Thu Jul 24 15:57:02 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id E7F4637B401; Thu, 24 Jul 2003 15:57:02 -0700 (PDT) To: freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG, freebsd-net@FreeBSD.ORG, freebsd-chat@FreeBSD.ORG Date: Thu, 24 Jul 2003 15:57:02 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20030724225702.E7F4637B401@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Subject: Update on nVidia/MCP ethernet X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 22:57:03 -0000 First off, response to my announcement has been amazing. I've received 150 e-mails so far, and they're still coming. Thanks to everyone who has responded. An extra special thanks to those people who agreed to talk to contacts they have within nVidia. I'm still waiting for for info from these people. As soon as I learn something new, I'll pass it along. I have also made some progress on another front. It occured to me that since nVidia is known for GPU expertise rather than networking expertise that maybe their 'proprietary design' wasn't really anything of the sort. Well, I was right: what nVidia calls "MCP ethernet" is really a Conexant CX25870/1 "jedi" controller. I have contacted Conexant and am in the process of trying to obtain a copy of the programming manual for this device. There are some NDA issues to deal with, however I've been told they will not prevent me from releasing driver source. I hope to get this resolved soon. Stay tuned. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= "If stupidity were a handicap, you'd have the best parking spot." ============================================================================= From owner-freebsd-hardware@FreeBSD.ORG Thu Jul 24 17:30:50 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E68237B404; Thu, 24 Jul 2003 17:30:50 -0700 (PDT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5019A43F75; Thu, 24 Jul 2003 17:30:49 -0700 (PDT) (envelope-from jkim@niksun.com) Received: from daemon.mj.niksun.com (daemon.mj.niksun.com [10.70.0.244]) h6P0UPlT067741; Thu, 24 Jul 2003 20:30:25 -0400 (EDT) (envelope-from jkim@niksun.com) X-RAV-AntiVirus: This e-mail has been scanned for viruses. From: Jung-uk Kim Organization: Niksun, Inc. To: wpaul@freebsd.org (Bill Paul), freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org, freebsd-net@freebsd.org, freebsd-chat@freebsd.org Date: Thu, 24 Jul 2003 20:30:25 -0400 User-Agent: KMail/1.5.1 References: <20030724225702.E7F4637B401@hub.freebsd.org> In-Reply-To: <20030724225702.E7F4637B401@hub.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="euc-kr" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200307242030.25276.jkim@niksun.com> Subject: Re: Update on nVidia/MCP ethernet X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2003 00:30:51 -0000 On Thursday 24 July 2003 06:57 pm, Bill Paul wrote: > I have also made some progress on another front. It occured to me > that since nVidia is known for GPU expertise rather than networking > expertise that maybe their 'proprietary design' wasn't really > anything of the sort. Well, I was right: what nVidia calls "MCP > ethernet" is really a Conexant CX25870/1 "jedi" controller. I have > contacted Conexant and am in the process of trying to obtain a copy > of the programming manual for this device. There are some NDA > issues to deal with, however I've been told they will not prevent > me from releasing driver source. AFAIK, CX25870/1 is a video encoder. http://www.conexant.com/products/entry.jsp?id=278 Jung-uk Kim From owner-freebsd-hardware@FreeBSD.ORG Thu Jul 24 19:13:31 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 17AE837B401 for ; Thu, 24 Jul 2003 19:13:31 -0700 (PDT) Received: from pit.databus.com (p70-227.acedsl.com [66.114.70.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3944D43F85 for ; Thu, 24 Jul 2003 19:13:30 -0700 (PDT) (envelope-from barney@pit.databus.com) Received: from pit.databus.com (localhost [127.0.0.1]) by pit.databus.com (8.12.9/8.12.9) with ESMTP id h6P2DTn8046741 for ; Thu, 24 Jul 2003 22:13:29 -0400 (EDT) (envelope-from barney@pit.databus.com) Received: (from barney@localhost) by pit.databus.com (8.12.9/8.12.9/Submit) id h6P2DTf4046740 for hardware@freebsd.org; Thu, 24 Jul 2003 22:13:29 -0400 (EDT) (envelope-from barney) Date: Thu, 24 Jul 2003 22:13:29 -0400 From: Barney Wolff To: hardware@freebsd.org Message-ID: <20030725021329.GA46653@pit.databus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: [lcamtuf@ghettot.org: Certain operating systems can be sometimes locally DoSed when running on particular types of hardware with certain versions of BIOS in specific multiboot configurations (and you thought XSS is too much?)] X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2003 02:13:31 -0000 Where do fbsd 4- and 5- stand on this? ----- Forwarded message from Michal Zalewski ----- List-Id: Date: Thu, 24 Jul 2003 22:23:30 +0200 (CEST) Yes, of course the subject line is silly... but in fact, the vulnerable combination actually occurs quite often. Still, I'm posting it here not because it's a very serious flaw, but because I find it amusing and unique. It's a CPU/BIOS/OS vulnerability, of sorts, and nobody's at fault, of course. Thanks to Bulba for wasting his time on helping me figure out what's going on, and for a number of people for risking their lives testing this problem on their systems. To the point. If your machine: - is equipped with Pentium II or better, - has a certain type of BIOS - tested and confirmed vulnerable (the list is definitely open and incomplete): IBM ThinkPad X IZET9AWW 2.22 (09/2002) Dell Latitude CPx H* revision A09 Dell Latitude CPi A* revision A15 Compaq 686T2 v08.22.1999 Tested but not vulnerable: Dell Latitude C800 revision A17 Dell OptiPlex GX150 revision A10 Dell Latitude C640 revision A08 ...and either... - dual boots between a fairly recent system that supports fast syscalls via SYSENTER (say, Windows XP) and a system that does not (say, Linux 2.4), ...or... - had run a newer SYSENTER-enabled unstable/patched kernel, later downgraded to a stable version... ...then your system can be DoSed in a fairly ugly way by any of your users. Pentium II introduced SYSENTER/SYSEXIT, a new, fast system call interface that is considerably more effective than the traditional entry method via INT or LCALL. When you boot to a system that supports this mechanism, the system will configure certain MSRs (model-specific registers) of the CPU - primarily 0x174 (CS) and 0x176 (EIP) - to point to a specific handler code. Once 0x174 is set, an invocation of SYSENTER opcode will cause the CPU to attempt to switch to the segment and address described in those registers. When 0x174 is zeroed, SYSENTER will simply fail, raising GPF. Quite unfortunately, certain BIOSes do not zero those MSRs on reboot. It is not clear to me why the CPU does not reset those registers itself, even after a triple fault, but it does not. There seems to be no reasonable explanation for persistence of this setting, yet this behavior has been confirmed with several chips - Pentium II, Pentium III Katmai and Coppermine and others. As a result, when a SYSENTER-enabled system is shut down and the machine is rebooted - but not powered down - the old setup is preserved. If a system that does not have a working SYSENTER support - as it is the case with all stable releases of Linux - is then booted up, the new system will continue to run with the "inherited" MSR settings. At this point, any user can issue a SYSENTER opcode to crash the system. Note that those MSRs remain persistent on those boxes over subsequent warm boots, so the attack can be successful even after a very long period of time since the other system was last booted up. Well, that's the story. If you're concerned, you don't have to rewire your CPU or update your BIOS - the fix is to compile the following code and invoke it from your rc scripts after '/sbin/insmod msr': -- sysleave.c -- #include #include #include #include int main(void) { unsigned long long w = 0; int i = open("/dev/cpu/0/msr",O_WRONLY); if (i<0) { printf("Cannot open MSR device (no module?).\n"); exit(1); } lseek(i,0x174,SEEK_SET); if (write(i,&w,8) < 0) { printf("MSR write error.\n"); exit(2); } printf("SYSENTER disabled.\n"); return close(i); } -- EOF -- If you want to test your system, you can follow the guidelines posted at http://lcamtuf.coredump.cx/bioses.txt . Cheers! -- ------------------------- bash$ :(){ :|:&};: -- Michal Zalewski * [http://lcamtuf.coredump.cx] Did you know that clones never use mirrors? --------------------------- 2003-07-24 16:48 -- ----- End forwarded message ----- -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. From owner-freebsd-hardware@FreeBSD.ORG Fri Jul 25 07:22:59 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0AD6737B401 for ; Fri, 25 Jul 2003 07:22:59 -0700 (PDT) Received: from vijit.vijit.com (h-66-134-231-114.CHCGILGM.covad.net [66.134.231.114]) by mx1.FreeBSD.org (Postfix) with SMTP id D75FB43FBD for ; Fri, 25 Jul 2003 07:22:57 -0700 (PDT) (envelope-from madsen@vijit.com) Received: (qmail 9232 invoked by uid 1000); 24 Jul 2003 09:33:09 -0000 Message-ID: <20030724093309.9231.qmail@eunited.vijit.com> From: madsen@vijit.com To: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Date: Thu, 24 Jul 2003 04:33:09 -0500 (CDT) X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: SATA \\ Promise PDC20376 \\ Promise TX2 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2003 14:22:59 -0000 I'm trying to get a single SATA drive running on my computer (MSI K7N2 Delta ILSR) which uses the Promise PDC20376. If I don't configure the drive in an array, FreeBSD 5.1 can access the drive just fine, but Windoze XP Pro doesn't see it, and neither does any other bootable utility. If I do configure it as a single "striped" drive in an array (there is no JBOD option according to MSI support), FreeBSD gets an "access error" when trying to do ANYTHING with the drive. But of course, 'doze and everything else sees it just fine. And I can't seem to boot from the drive no matter what. Yes, I've changed the boot devices in the BIOS, trying all "HDD-x" selections. It'll boot from my SCSI drive (FreeBSD), though. :-) I'm looking for a controller that will (1) handle a single SATA disk with no problems or hassles; (2) work with both 'doze and FreeBSD. It looks like the Promise FastTrak S150 TX2 is supported by both and the specs say it does JBOD, so I'm thinking of that one. However, all I can find is the TX2 __PLUS__ model, not the "plain" TX2. Is that a problem for the FreeBSD [4.8,5.1] driver? Or, does anyone have any better suggestion on how I can best get an SATA drive working here? Thanks! Dave Madsen ---dcm From owner-freebsd-hardware@FreeBSD.ORG Fri Jul 25 16:04:31 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E750E37B401 for ; Fri, 25 Jul 2003 16:04:30 -0700 (PDT) Received: from blount.mail.mindspring.net (blount.mail.mindspring.net [207.69.200.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E07543F3F for ; Fri, 25 Jul 2003 16:04:30 -0700 (PDT) (envelope-from jtanis@mindspring.com) Received: from user-1120ivn.dsl.mindspring.com ([66.32.75.247] helo=192.168.0.102) by blount.mail.mindspring.net with esmtp (Exim 3.33 #1) id 19gBbw-0000aY-00; Fri, 25 Jul 2003 19:04:29 -0400 From: James Tanis To: madsen@vijit.com Date: Fri, 25 Jul 2003 19:04:43 -0400 User-Agent: KMail/1.5.2 References: <20030724093309.9231.qmail@eunited.vijit.com> In-Reply-To: <20030724093309.9231.qmail@eunited.vijit.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200307251904.43281.jtanis@mindspring.com> cc: freebsd-hardware@freebsd.org Subject: Re: SATA \\ Promise PDC20376 \\ Promise TX2 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2003 23:04:31 -0000 SIIG's SiI 3112, this is a plain vanilla card - no raid, works perfectly fine for me. I am using 5.1-current though, I do not think support for SIIG's cards were included in 5.1 release. On Thursday 24 July 2003 05:33, madsen@vijit.com wrote: > I'm trying to get a single SATA drive running on my computer (MSI K7N2 > Delta ILSR) which uses the Promise PDC20376. If I don't configure the > drive in an array, FreeBSD 5.1 can access the drive just fine, but > Windoze XP Pro doesn't see it, and neither does any other bootable > utility. If I do configure it as a single "striped" drive in an array > (there is no JBOD option according to MSI support), FreeBSD gets an > "access error" when trying to do ANYTHING with the drive. But of > course, 'doze and everything else sees it just fine. > > And I can't seem to boot from the drive no matter what. Yes, I've > changed the boot devices in the BIOS, trying all "HDD-x" selections. > It'll boot from my SCSI drive (FreeBSD), though. :-) > > I'm looking for a controller that will (1) handle a single SATA disk > with no problems or hassles; (2) work with both 'doze and FreeBSD. It > looks like the Promise FastTrak S150 TX2 is supported by both and the > specs say it does JBOD, so I'm thinking of that one. However, all I can > find is the TX2 __PLUS__ model, not the "plain" TX2. Is that a problem > for the FreeBSD [4.8,5.1] driver? > > Or, does anyone have any better suggestion on how I can best get an SATA > drive working here? > > Thanks! > > Dave Madsen ---dcm > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" From owner-freebsd-hardware@FreeBSD.ORG Fri Jul 25 16:18:42 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F36D637B401 for ; Fri, 25 Jul 2003 16:18:41 -0700 (PDT) Received: from noc.mainstreet.net (noc.mainstreet.net [207.5.0.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D5FA43F75 for ; Fri, 25 Jul 2003 16:18:41 -0700 (PDT) (envelope-from freebsd@noc.mainstreet.net) Received: from noc.mainstreet.net (m.mainstreet.net [204.69.218.218]) by noc.mainstreet.net (8.12.9/8.12.9) with ESMTP id h6PNIfwl088735 for ; Fri, 25 Jul 2003 16:18:41 -0700 (PDT) Sender: mark@noc.mainstreet.net Message-ID: <3F21BAD1.5C8C6F43@noc.mainstreet.net> Date: Fri, 25 Jul 2003 16:18:41 -0700 From: Mark Kent X-Mailer: Mozilla 4.78 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: fxp0: device timeout revisited X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd@noc.mainstreet.net List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2003 23:18:42 -0000 Back in June the following was reported: http://lists.freebsd.org/pipermail/freebsd-hardware/2003-June/000243.html and it ends with: >> There's also a PR open on this: kern/45568 I recently moved four machines, all with built-in fxp0 ports, to 4.8-stable and today one of them dropped off the net with "fxp0: device timeout" I have console access, so I poked around and couldn't restart the port, so I rebooted. But the reboot hung on the way down. I power cycled and it came back to life. That message above seems to close the thread, but it still leaves me hanging. Are we waiting for something? FYI, The platform is an Intel ISP2150 (L440GX0), twin 550MHz PIII. Thanks, -mark