From owner-freebsd-hardware@FreeBSD.ORG Sun Sep 21 20:58:52 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 4CE1B16A4B3; Sun, 21 Sep 2003 20:58:52 -0700 (PDT) Received: from mprelay.uc.edu (mprelay.uc.edu [129.137.3.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0881843FBF; Sun, 21 Sep 2003 20:58:51 -0700 (PDT) (envelope-from troyertm@email.uc.edu) Received: from mirapoint.uc.edu (mirapoint.uc.edu [10.23.4.254]) by mprelay.uc.edu (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id ACK18772; Sun, 21 Sep 2003 23:37:57 -0400 (EDT) Received: from 65.150.221.52 by mirapoint.uc.edu (Mirapoint Messaging Server MOS 3.3.6-GR) with HTTP/1.1; Sun, 21 Sep 2003 23:37:57 -0400 Date: Sun, 21 Sep 2003 23:37:57 -0400 From: Travis Troyer To: freebsd-questions@freebsd.org X-Mailer: Webmail Mirapoint Direct 3.3.6-GR MIME-Version: 1.0 Message-Id: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-hardware@freebsd.org Subject: External modem suddenly not working (USR V.Everything) 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, 22 Sep 2003 03:58:52 -0000 I have a US Robotics V.Everything external modem connected to my system running FreeBSD 5.1 stable. I got my ppp.conf and ppp.linkup files setup properly, and was able to dial-up to my provider many times. I was connected when I accidentally knocked the power supply out of the wall socket, and lost my connection. I plugged it back in, turned it off and back on, and tried to connect, without success. So, I rebooted, with no success. I tried shutting down both the modem and the system and cold-booting; still no go. The modem connects fine under Windows (dual-boot), but refuses to even dial in FreeBSD. Any suggestions? Thanks, Travis Troyer From owner-freebsd-hardware@FreeBSD.ORG Sun Sep 21 23:37:29 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 1E0FB16A4B3 for ; Sun, 21 Sep 2003 23:37:29 -0700 (PDT) Received: from anon.securenym.net (anon.securenym.net [209.113.101.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4803E43FE0 for ; Sun, 21 Sep 2003 23:37:28 -0700 (PDT) (envelope-from dincht@SECURENYM.NET) Received: (from root@localhost) by anon.securenym.net (8.11.7/8.11.7) id h8M6TGG14019 for freebsd-hardware@freebsd.org.filtered; Mon, 22 Sep 2003 01:29:16 -0500 (CDT) Message-Id: <200309220629.h8M6TGG14019@anon.securenym.net> X-Securenym: dincht From: "C. Ulrich" To: Travis Troyer In-Reply-To: References: Content-Type: text/plain Organization: The Peter Jennings Fan Club Mime-Version: 1.0 Date: Mon, 22 Sep 2003 02:28:36 -0400 Content-Transfer-Encoding: 7bit cc: freebsd-questions@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Re: External modem suddenly not working (USR V.Everything) 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, 22 Sep 2003 06:37:29 -0000 On Sun, 2003-09-21 at 23:37, Travis Troyer wrote: > I have a US Robotics V.Everything external modem connected to > my system running FreeBSD 5.1 stable. I got my ppp.conf and > ppp.linkup files setup properly, and was able to dial-up to > my provider many times. I was connected when I accidentally > knocked the power supply out of the wall socket, and lost my > connection. I plugged it back in, turned it off and back on, > and tried to connect, without success. So, I rebooted, with > no success. I tried shutting down both the modem and the > system and cold-booting; still no go. The modem connects > fine under Windows (dual-boot), but refuses to even dial in > FreeBSD. > > Any suggestions? > > Thanks, > > Travis Troyer See what happens when you try to interact with the modem manually with an old-fashioned serial terminal program like kermit or minicom. You'll have to figure out how to use the program first, but once you do, the following commands might help troubleshoot the problem: ATZ : Reset the modem ATDTxxxxxxx : Dial phone number xxxxxxx ATH0 : Hang up the modem Look around on the net for an AT command reference for more information on these. Oh, and I assume this is a _serial_ external modem and not USB? If it's USB there may be some further trickery involved. C. Ulrich -- http://bityard.net From owner-freebsd-hardware@FreeBSD.ORG Sun Sep 21 23:52: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 82B6316A4B3; Sun, 21 Sep 2003 23:52:59 -0700 (PDT) Received: from oahu.WURLDLINK.NET (oahu.wurldlink.net [66.193.144.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id A4A4743FBD; Sun, 21 Sep 2003 23:52:58 -0700 (PDT) (envelope-from vince@oahu.WURLDLINK.NET) Received: from oahu.WURLDLINK.NET (vince@localhost.WURLDLINK.NET [127.0.0.1]) by oahu.WURLDLINK.NET (8.12.9/8.12.9) with ESMTP id h8M6oNOt094359; Sun, 21 Sep 2003 20:50:36 -1000 (HST) Received: from localhost (vince@localhost)h8M6oNYh094356; Sun, 21 Sep 2003 20:50:23 -1000 (HST) Date: Sun, 21 Sep 2003 20:50:23 -1000 (HST) From: Vincent Poy To: "C. Ulrich" In-Reply-To: <200309220629.h8M6TGG14019@anon.securenym.net> Message-ID: <20030921204846.W64375-100000@oahu.WURLDLINK.NET> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Travis Troyer cc: freebsd-questions@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Re: External modem suddenly not working (USR V.Everything) 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, 22 Sep 2003 06:52:59 -0000 On Mon, 22 Sep 2003, C. Ulrich wrote: > On Sun, 2003-09-21 at 23:37, Travis Troyer wrote: > > I have a US Robotics V.Everything external modem connected to > > my system running FreeBSD 5.1 stable. I got my ppp.conf and > > ppp.linkup files setup properly, and was able to dial-up to > > my provider many times. I was connected when I accidentally > > knocked the power supply out of the wall socket, and lost my > > connection. I plugged it back in, turned it off and back on, > > and tried to connect, without success. So, I rebooted, with > > no success. I tried shutting down both the modem and the > > system and cold-booting; still no go. The modem connects > > fine under Windows (dual-boot), but refuses to even dial in > > FreeBSD. > > > > Any suggestions? > > > > Thanks, > > > > Travis Troyer > > See what happens when you try to interact with the modem manually with > an old-fashioned serial terminal program like kermit or minicom. You'll > have to figure out how to use the program first, but once you do, the > following commands might help troubleshoot the problem: > > ATZ : Reset the modem > ATDTxxxxxxx : Dial phone number xxxxxxx > ATH0 : Hang up the modem > > Look around on the net for an AT command reference for more information > on these. > > Oh, and I assume this is a _serial_ external modem and not USB? If it's > USB there may be some further trickery involved. > > C. Ulrich Actually, the manual is built into the modem... He should check the following: ATI4 ATI5 ATI7 and then try this: AT%$ AT$ AT&$ The last three is the AT command set. But post the output from ATI4, ATI5, ATI7 so that we can help you out. Cheers, Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] WurldLink Corporation / / / / | / | __] ] San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin From owner-freebsd-hardware@FreeBSD.ORG Mon Sep 22 20:01:37 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 4E8C816A4B3 for ; Mon, 22 Sep 2003 20:01:37 -0700 (PDT) Received: from brmea-mail-3.sun.com (brmea-mail-3.Sun.COM [192.18.98.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C0CA43FA3 for ; Mon, 22 Sep 2003 20:01:36 -0700 (PDT) (envelope-from Mikore.Li@sun.com) Received: from phys-sport-1.PRC.Sun.COM ([129.158.216.23]) by brmea-mail-3.sun.com (8.12.10/8.12.9) with ESMTP id h8N31Ykv017607 for ; Mon, 22 Sep 2003 21:01:35 -0600 (MDT) Received: from sun.com (beige [129.158.218.106])ESMTP id h8N31Xh17563 for ; Tue, 23 Sep 2003 11:01:33 +0800 (CST) Message-ID: <3F6FB769.7040100@sun.com> Date: Tue, 23 Sep 2003 11:00:57 +0800 From: "Mikore.Li" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Hi, do you have datasheet of any Emulex Fibre Channel Adapter? 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, 23 Sep 2003 03:01:37 -0000 If you have, send to me a copy, please. Especially, I want to get a datasheet for Emulex LP95X. Best Regards Mikore Li From owner-freebsd-hardware@FreeBSD.ORG Tue Sep 23 09:56: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 2123E16A4B3 for ; Tue, 23 Sep 2003 09:56:50 -0700 (PDT) Received: from sedcsb9.nrl.navy.mil (sedcsb9.nrl.navy.mil [132.250.138.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F14D43FE3 for ; Tue, 23 Sep 2003 09:56:48 -0700 (PDT) (envelope-from machine@sedcsb9.nrl.navy.mil) Received: from sedcsb9.nrl.navy.mil (localhost.nrl.navy.mil [127.0.0.1]) by sedcsb9.nrl.navy.mil (8.12.9/8.12.8) with ESMTP id h8NGw8HE050286 for ; Tue, 23 Sep 2003 12:58:08 -0400 (EDT) (envelope-from machine@sedcsb9.nrl.navy.mil) Received: from localhost (localhost [[UNIX: localhost]]) by sedcsb9.nrl.navy.mil (8.12.9/8.12.8/Submit) id h8NGw8kc050262 for freebsd-hardware@freebsd.org; Tue, 23 Sep 2003 12:58:08 -0400 (EDT) From: Carl Glen Henshaw Organization: U.S. Naval Research Laboratory To: freebsd-hardware@freebsd.org Date: Tue, 23 Sep 2003 12:58:07 -0400 User-Agent: KMail/1.5.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200309231258.08050.ghenshaw@space.nrl.navy.mil> Subject: Logitech cordless mouse/keyboard 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, 23 Sep 2003 16:56:50 -0000 Hi all, I'm running FreeBSD 4.8 on a MicronPC TransPort GX3 laptop. I just got a Logitech cordless comfort duo, which consists of a cordless MouseMan optical mouse and a cordless desktop pro keyboard. This system has both a USB connector and a serial mouse port connector coming from the receiver. It also comes with a dongle that supposedly converts from the USB connector to a serial port connector, so one can plug the keyboard in via a keyboard port. The instructions state that one should either 1) plug in the keyboard port converter, and then plug both the mouse and keyboard connectors into the appropriate serial ports, or 2) use the USB connector. Apparently you can't use the USB connector *and* the mouse port connector simultaneously. My laptop has only one serial port, so it appears that USB is the way to go. For the life of me, I can't make these things work with FreeBSD. If I plug the cordless receiver into the USB port, per the instructions, nothing I do to either my XF86Config or to moused makes the mouse respond at all. I can make the keyboard work by issuing the command "kbdcontrol -k /dev/kbd1 < /dev/ttyv0", although that switches off the built-in laptop keyboard, and I get lots of extraneous characters when I type. If I unplug the usb connection and plug the mouse port connector into my serial port, after a reboot the mouse does work but of course I don't get the keyboard. If I plug the keyboard connector into the serial port then I get the keyboard but not the mouse. Nothing I can figure out gets me both the keyboard and the mouse at the same time. My rc.conf has usbd_enable="YES" moused_enable="YES" and my XF86Config is at the bottom of this message. dmesg reports: usb0: on uhci0 usb0: USB revision 1.0 usb1: on uhci1 usb1: USB revision 1.0 usb2: on uhci2 usb2: USB revision 1.0 ... ums0: Logitech USB Receiver, rev 1.10/17.00, addr 2, iclass 3/1 ums0: 7 buttons and Z dir. Can anyone tell me the magic to make this work? Please respond to me by email as I don't subscribe to this list: ghenshaw at space.nrl.navy.mil Thanks, Glen ____________________________________________________________ Dr. Glen Henshaw Naval Center for Space Technology U.S. Naval Research Laboratory (202) 767-1196 # File generated by xf86config. # # Copyright (c) 1999 by The XFree86 Project, Inc. # # Permission is hereby granted, free of charge, to any person obtaining a # copy of this software and associated documentation files (the "Software"), # to deal in the Software without restriction, including without limitation # the rights to use, copy, modify, merge, publish, distribute, sublicense, # and/or sell copies of the Software, and to permit persons to whom the # Software is furnished to do so, subject to the following conditions: # # The above copyright notice and this permission notice shall be included in # all copies or substantial portions of the Software. # # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL # THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, # WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF # OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE # SOFTWARE. # # Except as contained in this notice, the name of the XFree86 Project shall # not be used in advertising or otherwise to promote the sale, use or other # dealings in this Software without prior written authorization from the # XFree86 Project. # # ********************************************************************** # Refer to the XF86Config(4/5) man page for details about the format of # this file. # ********************************************************************** # ********************************************************************** # Module section -- this section is used to specify # which dynamically loadable modules to load. # ********************************************************************** # Section "Module" # This loads the DBE extension module. Load "dbe" # Double buffer extension # This loads the miscellaneous extensions module, and disables # initialisation of the XFree86-DGA extension within that module. SubSection "extmod" Option "omit xfree86-dga" # don't initialise the DGA extension EndSubSection # This loads the Type1 and FreeType font modules Load "type1" Load "speedo" # Load "freetype" # Load "xtt" # This loads the GLX module Load "glx" # This loads the DRI module Load "dri" EndSection # ********************************************************************** # Files section. This allows default font and rgb paths to be set # ********************************************************************** Section "Files" # The location of the RGB database. Note, this is the name of the # file minus the extension (like ".txt" or ".db"). There is normally # no need to change the default. RgbPath "/usr/X11R6/lib/X11/rgb" # Multiple FontPath entries are allowed (which are concatenated together), # as well as specifying multiple comma-separated entries in one FontPath # command (or a combination of both methods) # # If you don't have a floating point coprocessor and emacs, Mosaic or other # programs take long to start up, try moving the Type1 and Speedo directory # to the end of this list (or comment them out). # FontPath "/usr/X11R6/lib/X11/fonts/local/" FontPath "/usr/X11R6/lib/X11/fonts/misc/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/Speedo/" FontPath "/usr/X11R6/lib/X11/fonts/Type1/" # FontPath "/usr/X11R6/lib/X11/fonts/TrueType/" # FontPath "/usr/X11R6/lib/X11/fonts/freefont/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/" # The module search path. The default path is shown here. # ModulePath "/usr/X11R6/lib/modules" EndSection # ********************************************************************** # Server flags section. # ********************************************************************** Section "ServerFlags" # Uncomment this to cause a core dump at the spot where a signal is # received. This may leave the console in an unusable state, but may # provide a better stack trace in the core dump to aid in debugging # Option "NoTrapSignals" # Uncomment this to disable the VT switch sequence # (where n is 1 through 12). This allows clients to receive these key # events. # Option "DontVTSwitch" # Uncomment this to disable the server abort sequence # This allows clients to receive this key event. # Option "DontZap" # Uncomment this to disable the / mode switching # sequences. This allows clients to receive these key events. # Option "Dont Zoom" # Uncomment this to disable tuning with the xvidtune client. With # it the client can still run and fetch card and monitor attributes, # but it will not be allowed to change them. If it tries it will # receive a protocol error. # Option "DisableVidModeExtension" # Uncomment this to enable the use of a non-local xvidtune client. # Option "AllowNonLocalXvidtune" # Uncomment this to disable dynamically modifying the input device # (mouse and keyboard) settings. # Option "DisableModInDev" # Uncomment this to enable the use of a non-local client to # change the keyboard or mouse settings (currently only xset). # Option "AllowNonLocalModInDev" EndSection # ********************************************************************** # Input devices # ********************************************************************** # ********************************************************************** # Core keyboard's InputDevice section # ********************************************************************** Section "InputDevice" Identifier "Keyboard1" Driver "Keyboard" # For most OSs the protocol can be omitted (it defaults to "Standard"). # When using XQUEUE (only for SVR3 and SVR4, but not Solaris), # uncomment the following line. # Option "Protocol" "Xqueue" Option "AutoRepeat" "500 30" # Specify which keyboard LEDs can be user-controlled (eg, with xset(1)) # Option "Xleds" "1 2 3" # Option "LeftAlt" "Meta" # Option "RightAlt" "ModeShift" # To customise the XKB settings to suit your keyboard, modify the # lines below (which are the defaults). For example, for a non-U.S. # keyboard, you will probably want to use: # Option "XkbModel" "pc102" # If you have a US Microsoft Natural keyboard, you can use: # Option "XkbModel" "microsoft" # # Then to change the language, change the Layout setting. # For example, a german layout can be obtained with: # Option "XkbLayout" "de" # or: # Option "XkbLayout" "de" # Option "XkbVariant" "nodeadkeys" # # If you'd like to switch the positions of your capslock and # control keys, use: # Option "XkbOptions" "ctrl:swapcaps" # These are the default XKB settings for XFree86 # Option "XkbRules" "xfree86" # Option "XkbModel" "pc101" # Option "XkbLayout" "us" # Option "XkbVariant" "" # Option "XkbOptions" "" # Option "XkbDisable" Option "XkbRules" "xfree86" Option "XkbModel" "pc101" Option "XkbLayout" "us" EndSection # ********************************************************************** # Core Pointer's InputDevice section # ********************************************************************** Section "InputDevice" # Identifier and driver Identifier "Mouse1" Driver "mouse" Option "Protocol" "Auto" Option "Device" "/dev/sysmouse" Option "ZAxisMapping" "4 5" # Mouse-speed setting for PS/2 mouse. # Option "Resolution" "256" # When using XQUEUE, comment out the above two lines, and uncomment # the following line. # Option "Protocol" "Xqueue" # Baudrate and SampleRate are only for some Logitech mice. In # almost every case these lines should be omitted. # Option "BaudRate" "9600" # Option "SampleRate" "150" # Emulate3Buttons is an option for 2-button Microsoft mice # Emulate3Timeout is the timeout in milliseconds (default is 50ms) Option "Emulate3Buttons" # Option "Emulate3Timeout" "50" # ChordMiddle is an option for some 3-button Logitech mice # Option "ChordMiddle" EndSection Section "InputDevice" Identifier "Touchpad" Driver "mouse" Option "Protocol" "Auto" Option "Device" "/dev/psm0" #Option "Emulate3Buttons" Option "Buttons" "5" Option "ZAxisMapping" "4 5" EndSection # ********************************************************************** # Other input device sections # this is optional and is required only if you # are using extended input devices. This is for example only. Refer # to the XF86Config man page for a description of the options. # ********************************************************************** # # Section "InputDevice" # Identifier "Mouse2" # Driver "mouse" # Option "Protocol" "MouseMan" # Option "Device" "/dev/mouse2" # EndSection # # Section "InputDevice" # Identifier "spaceball" # Driver "magellan" # Option "Device" "/dev/cua0" # EndSection # # Section "InputDevice" # Identifier "spaceball2" # Driver "spaceorb" # Option "Device" "/dev/cua0" # EndSection # # Section "InputDevice" # Identifier "touchscreen0" # Driver "microtouch" # Option "Device" "/dev/ttyS0" # Option "MinX" "1412" # Option "MaxX" "15184" # Option "MinY" "15372" # Option "MaxY" "1230" # Option "ScreenNumber" "0" # Option "ReportingMode" "Scaled" # Option "ButtonNumber" "1" # Option "SendCoreEvents" # EndSection # # Section "InputDevice" # Identifier "touchscreen1" # Driver "elo2300" # Option "Device" "/dev/ttyS0" # Option "MinX" "231" # Option "MaxX" "3868" # Option "MinY" "3858" # Option "MaxY" "272" # Option "ScreenNumber" "0" # Option "ReportingMode" "Scaled" # Option "ButtonThreshold" "17" # Option "ButtonNumber" "1" # Option "SendCoreEvents" # EndSection # ********************************************************************** # Monitor section # ********************************************************************** # Any number of monitor sections may be present Section "Monitor" Identifier "MicronLCD" # HorizSync is in kHz unless units are specified. # HorizSync may be a comma separated list of discrete values, or a # comma separated list of ranges of values. # NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S # USER MANUAL FOR THE CORRECT NUMBERS. HorizSync 31.5 - 64.3 # HorizSync 30-64 # multisync # HorizSync 31.5, 35.2 # multiple fixed sync frequencies # HorizSync 15-25, 30-50 # multiple ranges of sync frequencies # VertRefresh is in Hz unless units are specified. # VertRefresh may be a comma separated list of discrete values, or a # comma separated list of ranges of values. # NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S # USER MANUAL FOR THE CORRECT NUMBERS. VertRefresh 50-90 ModeLine "1400x1050" 155.0 1400 1464 1784 1912 1050 1052 1064 1090 -HSync -VSync EndSection # ********************************************************************** # Graphics device section # ********************************************************************** # Any number of graphics device sections may be present # Standard VGA Device: Section "Device" Identifier "Standard VGA" VendorName "Unknown" BoardName "Unknown" # The chipset line is optional in most cases. It can be used to override # the driver's chipset detection, and should not normally be specified. # Chipset "generic" # The Driver line must be present. When using run-time loadable driver # modules, this line instructs the server to load the specified driver # module. Even when not using loadable driver modules, this line # indicates which driver should interpret the information in this section. Driver "vga" # The BusID line is used to specify which of possibly multiple devices # this section is intended for. When this line isn't present, a device # section can only match up with the primary video device. For PCI # devices a line like the following could be used. This line should not # normally be included unless there is more than one video device # intalled. # BusID "PCI:0:10:0" # VideoRam 256 # Clocks 25.2 28.3 EndSection # Device configured by xf86config: Section "Device" Identifier "ATI Radeon Mobility 7500" Driver "radeon" VendorName "ATI Radeon Mobility 7500" BoardName "ATI Radeon Mobility 7500" VideoRam 32768 Option "AGPMode" "1" Option "PanelSize" "1400x1050" Option "CrtScreen" "False" Option "DDCMode" "on" Option "CloneDisplay" "1" # Insert Clocks lines here if appropriate EndSection # ********************************************************************** # Screen sections # ********************************************************************** # Any number of screen sections may be present. Each describes # the configuration of a single screen. A single specific screen section # may be specified from the X server command line with the "-screen" # option. Section "Screen" Identifier "Screen 1" Device "ATI Radeon Mobility 7500" Monitor "MicronLCD" DefaultDepth 24 Subsection "Display" Depth 8 Modes "1600x1200" "1400x1050" "1280x1024" "1024x768" "800x600" "640x480" ViewPort 0 0 EndSubsection Subsection "Display" Depth 16 Modes "1600x1200" "1400x1050" "1280x1024" "1024x768" "800x600" "640x480" ViewPort 0 0 EndSubsection Subsection "Display" Depth 24 #Modes "1600x1200" "1400x1050" "1280x1024" "1024x768" "800x600" "640x480" Modes "1400x1050" "1280x1024" "1024x768" ViewPort 0 0 EndSubsection EndSection Section "DRI" Mode 0666 EndSection # ********************************************************************** # ServerLayout sections. # ********************************************************************** # Any number of ServerLayout sections may be present. Each describes # the way multiple screens are organised. A specific ServerLayout # section may be specified from the X server command line with the # "-layout" option. In the absence of this, the first section is used. # When now ServerLayout section is present, the first Screen section # is used alone. Section "ServerLayout" # The Identifier line must be present Identifier "Simple Layout" # Each Screen line specifies a Screen section name, and optionally # the relative position of other screens. The four names after # primary screen name are the screens to the top, bottom, left and right # of the primary screen. In this example, screen 2 is located to the # right of screen 1. Screen "Screen 1" # Each InputDevice line specifies an InputDevice section name and # optionally some options to specify the way the device is to be # used. Those options include "CorePointer", "CoreKeyboard" and # "SendCoreEvents". InputDevice "Mouse1" "CorePointer" InputDevice "Touchpad" "SendCoreEvents" InputDevice "Keyboard1" "CoreKeyboard" EndSection # Section "DRI" # Mode 0666 # EndSection From owner-freebsd-hardware@FreeBSD.ORG Wed Sep 24 07:41:52 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 B9F5216A4B3 for ; Wed, 24 Sep 2003 07:41:52 -0700 (PDT) Received: from web12811.mail.yahoo.com (web12811.mail.yahoo.com [216.136.174.128]) by mx1.FreeBSD.org (Postfix) with SMTP id F302744001 for ; Wed, 24 Sep 2003 07:41:49 -0700 (PDT) (envelope-from mglyer@yahoo.com) Message-ID: <20030924144149.16515.qmail@web12811.mail.yahoo.com> Received: from [65.197.254.5] by web12811.mail.yahoo.com via HTTP; Wed, 24 Sep 2003 07:41:49 PDT Date: Wed, 24 Sep 2003 07:41:49 -0700 (PDT) From: Michael Glyer To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Video Card Support 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, 24 Sep 2003 14:41:52 -0000 Hello, This is my first post. I am runnig freebsd 4.8. I have an old laptop made by Umax, a scanner maker. The video card in this thing is a NeoMagic Magicgraph 128XD. I am not running and X-windows, but I cannot get it to display in anything other than 80x30. I have tried the vidcontrol -i mode command, and it appears as though I should be able to display in something better. Is this card supported? I cannot find a supported hardware list for display adapters. All I want to do is to be able to set my display to more lines. Below is a copy of the vidcontrol command. mode# flags type size font window linear buffer ------------------------------------------------------------------------------ 0 (0x000) 0x00000001 T 40x25 8x8 0xb8000 32k 32k 0x00000000 32k 1 (0x001) 0x00000001 T 40x25 8x8 0xb8000 32k 32k 0x00000000 32k 2 (0x002) 0x00000001 T 80x25 8x8 0xb8000 32k 32k 0x00000000 32k 3 (0x003) 0x00000001 T 80x25 8x8 0xb8000 32k 32k 0x00000000 32k 4 (0x004) 0x00000003 G 320x200x2 1 8x8 0xb8000 32k 32k 0x00000000 32k 5 (0x005) 0x00000003 G 320x200x2 1 8x8 0xb8000 32k 32k 0x00000000 32k 6 (0x006) 0x00000003 G 640x200x1 1 8x8 0xb8000 32k 32k 0x00000000 32k 13 (0x00d) 0x00000003 G 320x200x4 4 8x8 0xa0000 64k 64k 0x00000000 256k 14 (0x00e) 0x00000003 G 640x200x4 4 8x8 0xa0000 64k 64k 0x00000000 256k 16 (0x010) 0x00000003 G 640x350x2 2 8x14 0xa0000 64k 64k 0x00000000 128k 18 (0x012) 0x00000003 G 640x350x4 4 8x14 0xa0000 64k 64k 0x00000000 256k 19 (0x013) 0x00000001 T 40x25 8x14 0xb8000 32k 32k 0x00000000 32k 20 (0x014) 0x00000001 T 40x25 8x14 0xb8000 32k 32k 0x00000000 32k 21 (0x015) 0x00000001 T 80x25 8x14 0xb8000 32k 32k 0x00000000 32k 22 (0x016) 0x00000001 T 80x25 8x14 0xb8000 32k 32k 0x00000000 32k 23 (0x017) 0x00000001 T 40x25 8x16 0xb8000 32k 32k 0x00000000 32k 24 (0x018) 0x00000001 T 80x25 8x16 0xb8000 32k 32k 0x00000000 32k 26 (0x01a) 0x00000003 G 640x480x4 4 8x16 0xa0000 64k 64k 0x00000000 256k 27 (0x01b) 0x00000003 G 640x480x4 4 8x16 0xa0000 64k 64k 0x00000000 256k 28 (0x01c) 0x00000003 G 320x200x8 1 8x8 0xa0000 64k 64k 0x00000000 64k 30 (0x01e) 0x00000001 T 80x50 8x8 0xb8000 32k 32k 0x00000000 32k 32 (0x020) 0x00000001 T 80x30 8x16 0xb8000 32k 32k 0x00000000 32k 34 (0x022) 0x00000001 T 80x60 8x8 0xb8000 32k 32k 0x00000000 32k 37 (0x025) 0x00000003 G 320x240x8 4 8x8 0xa0000 64k 64k 0x00000000 256k 112 (0x070) 0x00000000 T 80x43 8x8 0xb8000 32k 32k 0x00000000 32k 113 (0x071) 0x00000001 T 80x43 8x8 0xb8000 32k 32k 0x00000000 32k 256 (0x100) 0x0000000f G 640x400x8 1 8x16 0xa0000 64k 64k 0xfd000000 1984k 257 (0x101) 0x0000000f G 640x480x8 1 8x16 0xa0000 64k 64k 0xfd000000 1984k 258 (0x102) 0x0000000b G 800x600x4 4 8x16 0xa0000 64k 64k 0x00000000 1984k 259 (0x103) 0x0000000f G 800x600x8 1 8x16 0xa0000 64k 64k 0xfd000000 1984k 260 (0x104) 0x0000000b G 1024x768x4 4 8x16 0xa0000 64k 64k 0x00000000 1984k 261 (0x105) 0x0000000f G 1024x768x8 1 8x16 0xa0000 64k 64k 0xfd000000 1984k 269 (0x10d) 0x0000000f G 320x200x15 1 8x16 0xa0000 64k 64k 0xfd000000 1984k 270 (0x10e) 0x0000000f G 320x200x16 1 8x16 0xa0000 64k 64k 0xfd000000 1984k 272 (0x110) 0x0000000f G 640x480x15 1 8x16 0xa0000 64k 64k 0xfd000000 1984k 273 (0x111) 0x0000000f G 640x480x16 1 8x16 0xa0000 64k 64k 0xfd000000 1984k 274 (0x112) 0x0000000f G 640x480x24 1 8x16 0xa0000 64k 64k 0xfd000000 1984k 275 (0x113) 0x0000000f G 800x600x15 1 8x16 0xa0000 64k 64k 0xfd000000 1984k 276 (0x114) 0x0000000f G 800x600x16 1 8x16 0xa0000 64k 64k 0xfd000000 1984k 277 (0x115) 0x0000000f G 800x600x24 1 8x16 0xa0000 64k 64k 0xfd000000 1984k 278 (0x116) 0x0000000f G 1024x768x15 1 8x16 0xa0000 64k 64k 0xfd000000 1984k 279 (0x117) 0x0000000f G 1024x768x16 1 8x16 0xa0000 64k 64k 0xfd000000 1984k 288 (0x120) 0x0000000f G 320x240x8 1 8x8 0xa0000 64k 64k 0xfd000000 1984k 289 (0x121) 0x0000000f G 320x240x16 1 8x8 0xa0000 64k 64k 0xfd000000 1984k 290 (0x122) 0x0000000f G 400x300x8 1 8x8 0xa0000 64k 64k 0xfd000000 1984k 291 (0x123) 0x0000000f G 400x300x16 1 8x8 0xa0000 64k 64k 0xfd000000 1984k 292 (0x124) 0x0000000f G 512x384x8 1 8x8 0xa0000 64k 64k 0xfd000000 1984k 293 (0x125) 0x0000000f G 512x384x16 1 8x8 0xa0000 64k 64k 0xfd000000 1984k --------------------------------- Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software From owner-freebsd-hardware@FreeBSD.ORG Wed Sep 24 07:52:17 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 8E77A16A4BF; Wed, 24 Sep 2003 07:52:17 -0700 (PDT) Received: from sedcsb9.nrl.navy.mil (sedcsb9.nrl.navy.mil [132.250.138.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 951E343FAF; Wed, 24 Sep 2003 07:52:16 -0700 (PDT) (envelope-from machine@sedcsb9.nrl.navy.mil) Received: from sedcsb9.nrl.navy.mil (localhost.nrl.navy.mil [127.0.0.1]) by sedcsb9.nrl.navy.mil (8.12.9/8.12.8) with ESMTP id h8OErbPn007008; Wed, 24 Sep 2003 10:53:37 -0400 (EDT) (envelope-from machine@sedcsb9.nrl.navy.mil) Received: by sedcsb9.nrl.navy.mil (8.12.9/8.12.8/Submit) id h8OEraJX007007; Wed, 24 Sep 2003 10:53:36 -0400 (EDT) From: Carl Glen Henshaw Organization: U.S. Naval Research Laboratory To: John Baldwin Date: Wed, 24 Sep 2003 10:53:36 -0400 User-Agent: KMail/1.5.3 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200309241053.36552.ghenshaw@space.nrl.navy.mil> cc: freebsd-hardware@FreeBSD.org Subject: Re: Logitech cordless mouse/keyboard 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, 24 Sep 2003 14:52:17 -0000 On Wednesday 24 September 2003 10:34 am, John Baldwin wrote: > Drop the moused_enable line, usbd already runs moused for you. If > multiple moused's don't work, then this could be why your mouse > isn't working. Okay, done. No change though. > Your mouse works then via USB. Can you see if a moused is > running? Also, try 'vidcontrol -m on' in a text console and > see if the mouse works. moused is running, and 'vidcontrol -m on' in a text console doesn't give me anything. The pointer blinks for s split second and then disappears. Interestingly enough, my previous mouse, a wired USB mouse, works fine. Glen ____________________________________________________________ Dr. Glen Henshaw Naval Center for Space Technology U.S. Naval Research Laboratory (202) 767-1196 From owner-freebsd-hardware@FreeBSD.ORG Wed Sep 24 19:25:35 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 276F816A4B3 for ; Wed, 24 Sep 2003 19:25:35 -0700 (PDT) Received: from tmgcon.com (tmgcon.com [128.121.216.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 884C944020 for ; Wed, 24 Sep 2003 19:25:34 -0700 (PDT) (envelope-from gentoo@tmgcon.com) Received: from gentoo (210-54-105-177.dialup.xtra.co.nz [210.54.105.177]) (authenticated bits=0) by tmgcon.com (8.12.9p1/8.12.6) with ESMTP id h8P2PVPi089516 for ; Thu, 25 Sep 2003 03:25:33 +0100 (BST) From: Tom Munro Glass To: freebsd-hardware@freebsd.org Date: Thu, 25 Sep 2003 14:25:31 +1200 User-Agent: KMail/1.5.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200309251425.31918.gentoo@tmgcon.com> Subject: FreeBSD 4.8 on Dell PowerEdge 1600SC? 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, 25 Sep 2003 02:25:35 -0000 Can anyone please confirm if 4.8-RELEASE will run on a Dell PowerEdge 1600SC, using the onboard Ultra 320 SCSI rather than Dell's RAID. I've checked everything I can from the 4.8 HARDWARE.TXT but I'd really appreciate hearing from someone who is successfully running this hardware/software combination. Regards, Tom Munro Glass From owner-freebsd-hardware@FreeBSD.ORG Fri Sep 26 23:24:09 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 47B5616A4B3 for ; Fri, 26 Sep 2003 23:24:09 -0700 (PDT) Received: from smtp.covadmail.net (mx04.covadmail.net [63.65.120.64]) by mx1.FreeBSD.org (Postfix) with SMTP id D7EDE43FEA for ; Fri, 26 Sep 2003 23:24:07 -0700 (PDT) (envelope-from strick@covad.net) Received: (covad.net 15942 invoked from network); 27 Sep 2003 06:24:02 -0000 Received: from unknown (HELO ice.nodomain) (68.164.196.84) by sun-qmail04 with SMTP; 27 Sep 2003 06:24:02 -0000 Received: from ice.nodomain (localhost [127.0.0.1]) by ice.nodomain (8.12.8p1/8.12.8) with ESMTP id h8R6OBHt000842; Fri, 26 Sep 2003 23:24:12 -0700 (PDT) (envelope-from dan@ice.nodomain) Received: (from dan@localhost) by ice.nodomain (8.12.8p1/8.12.8/Submit) id h8R6OBjS000841; Fri, 26 Sep 2003 23:24:11 -0700 (PDT) Date: Fri, 26 Sep 2003 23:24:11 -0700 (PDT) From: Dan Strick Message-Id: <200309270624.h8R6OBjS000841@ice.nodomain> To: freebsd-hardware@freebsd.org cc: dan@ice.nodomain Subject: bad BIOS confuses boot0 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: Sat, 27 Sep 2003 06:24:09 -0000 The AWARD BIOS on my Gigabyte 8KNXP motherboard has been giving me a hard time for several weeks. Tonight I got around to instrumenting a copy of /usr/src/sys/boot/i386/boot0/boot0.s and verified my suspicion. The AWARD BIOS loads the MBR from the first drive in the BIOS drive list, drive code 0x80, but passes the value 0x81 to the bootstrap program through the %dl register. This has a couple of consequences: 1) The boot0 program lists the partition on the first drive but boots the selected partition from the second drive, and 2) The boot0 program may overwrite the MBR on the second drive with a copy of the MBR from the first drive. My workaround was to do: boot0cfg -Bv -d 0x80 -o setdrv,noupdate ad0 The noupdate option is intended to prevent a major disaster if this drive should ever be assigned a different number by the BIOS. I don't like this workaround. It is clumsy and restrictive. The drive configuration on my PC is in a state of flux. Has anyone noticed such antisocial BIOS behavior in the past? Is there actually a standard for passing the BIOS drive number through the %dl register? Do I have grounds for *demanding* that the motherboard manufacturer get the BIOS fixed? Dan Strick strick@covad.net From owner-freebsd-hardware@FreeBSD.ORG Sat Sep 27 07:56:44 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 C362416A4BF; Sat, 27 Sep 2003 07:56:44 -0700 (PDT) Received: from mprelay.uc.edu (mprelay.uc.edu [129.137.3.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id 052F444033; Sat, 27 Sep 2003 07:56:43 -0700 (PDT) (envelope-from troyertm@email.uc.edu) Received: from mirapoint.uc.edu (mirapoint.uc.edu [10.23.4.254]) by mprelay.uc.edu (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id ACX41517; Sat, 27 Sep 2003 10:56:41 -0400 (EDT) Received: from 24.51.124.61 by mirapoint.uc.edu (Mirapoint Messaging Server MOS 3.3.6-GR) with HTTP/1.1; Sat, 27 Sep 2003 10:56:41 -0400 Date: Sat, 27 Sep 2003 10:56:41 -0400 From: Travis Troyer To: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org X-Mailer: Webmail Mirapoint Direct 3.3.6-GR MIME-Version: 1.0 Message-Id: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Sil680 RAID Support while installing 5.1-Release 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: Sat, 27 Sep 2003 14:56:44 -0000 I just purchased a Sil680 IDE RAID controller, and have setup a striped RAID array. When I boot from the 5.1 installation CD-ROM, FreeBSD does not recognize them as one disk. I checked the hardware notes, and "Sil680 UDMA6" is listed. Seeing Sil680 listed, I assumed that the RAID capabilities would also be supported. I read something posted awhile back referring to the Sil680 controller, saying it was supported, but dangerous unless using 5.1-Current. Does anybody know anything about the current status of this? Is there anyway to get the FreeBSD installation to recognize my RAID array, or should I just buy another controller? Thanks, Travis Troyer From owner-freebsd-hardware@FreeBSD.ORG Sat Sep 27 08:17:57 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 3D58A16A4B3 for ; Sat, 27 Sep 2003 08:17:57 -0700 (PDT) Received: from mail.foremind.com (mail.inform.com.hk [206.220.132.130]) by mx1.FreeBSD.org (Postfix) with SMTP id C71954402D for ; Sat, 27 Sep 2003 08:17:54 -0700 (PDT) (envelope-from achan@achan.com) Received: (qmail 47330 invoked by uid 0); 27 Sep 2003 15:17:51 -0000 Received: from unknown (HELO pluto) (achan@achan.com@203.169.183.155) by mail.inform.com.hk with SMTP; 27 Sep 2003 15:17:51 -0000 Message-ID: <004d01c3850a$81935730$1700a8c0@pluto> From: "Andrew Chan" To: "Travis Troyer" References: Date: Sat, 27 Sep 2003 23:17:46 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 cc: freebsd-hardware@freebsd.org Subject: Re: Sil680 RAID Support while installing 5.1-Release 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: Sat, 27 Sep 2003 15:17:57 -0000 I don't know about 5.1-Current, but if you look at the ata-raid.* code in the 5.1-Release kernel source tree, you will find that only Promise and Highpoint chips are supported. This is a pity because the Sil0680 chip is the cheapest and most widely available around. It is selling for less than US$20 here in Hong Kong with ATA133 and full "RAID" capabilities. While it may not be super fast, it does work alright under Windows environment. If it is indeed supported under 5.1-Current, that is great news. Andrew ----- Original Message ----- From: "Travis Troyer" To: ; Sent: Saturday, September 27, 2003 10:56 PM Subject: Sil680 RAID Support while installing 5.1-Release > I just purchased a Sil680 IDE RAID controller, and have setup > a striped RAID array. When I boot from the 5.1 installation > CD-ROM, FreeBSD does not recognize them as one disk. I > checked the hardware notes, and "Sil680 UDMA6" is listed. > Seeing Sil680 listed, I assumed that the RAID capabilities > would also be supported. I read something posted awhile back > referring to the Sil680 controller, saying it was supported, > but dangerous unless using 5.1-Current. Does anybody know > anything about the current status of this? Is there anyway to > get the FreeBSD installation to recognize my RAID array, or > should I just buy another controller? From owner-freebsd-hardware@FreeBSD.ORG Sat Sep 27 09:12:20 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 8395A16A4B3 for ; Sat, 27 Sep 2003 09:12:20 -0700 (PDT) Received: from iota.root-servers.ch (iota.root-servers.ch [193.41.193.195]) by mx1.FreeBSD.org (Postfix) with SMTP id 70B9244013 for ; Sat, 27 Sep 2003 09:12:15 -0700 (PDT) (envelope-from gaml@buz.ch) Received: (qmail 10605 invoked from network); 27 Sep 2003 16:12:14 -0000 Received: from dclient217-162-130-157.hispeed.ch (HELO ga) (217.162.130.157) by 0 with SMTP; 27 Sep 2003 16:12:14 -0000 Date: Sat, 27 Sep 2003 18:13:28 +0200 From: Gabriel Ambuehl X-Mailer: The Bat! (v2.00.6) UNREG / CD5BF9353B3B7091 X-Priority: 3 (Normal) Message-ID: <3295038640.20030927181328@buz.ch> To: Travis Troyer In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: freebsd-questions@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Re: Sil680 RAID Support while installing 5.1-Release X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Gabriel Ambuehl List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Sep 2003 16:12:20 -0000 Hi Travis Troyer, you wrote. TT> I just purchased a Sil680 IDE RAID controller, and have setup TT> a striped RAID array. When I boot from the 5.1 installation TT> CD-ROM, FreeBSD does not recognize them as one disk. I TT> checked the hardware notes, and "Sil680 UDMA6" is listed. TT> Seeing Sil680 listed, I assumed that the RAID capabilities TT> would also be supported. I read something posted awhile back TT> referring to the Sil680 controller, saying it was supported, TT> but dangerous unless using 5.1-Current. Does anybody know TT> anything about the current status of this? Is there anyway to TT> get the FreeBSD installation to recognize my RAID array, or TT> should I just buy another controller? I was wondering about the online Sil 3112 SATA RAID controller on my Gigabyte 7VAXP board. The 5.1 RELEASE boot CD crashes saying it couldn't write to root (which is weird, considering it usually should be able to write to memfs??). Regards, Gabriel From owner-freebsd-hardware@FreeBSD.ORG Sat Sep 27 21:32:48 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 D423616A4B3 for ; Sat, 27 Sep 2003 21:32:48 -0700 (PDT) Received: from smtp.covadmail.net (mx04.covadmail.net [63.65.120.64]) by mx1.FreeBSD.org (Postfix) with SMTP id AED0F44028 for ; Sat, 27 Sep 2003 21:32:47 -0700 (PDT) (envelope-from strick@covad.net) Received: (covad.net 27161 invoked from network); 28 Sep 2003 04:32:42 -0000 Received: from unknown (HELO ice.nodomain) (68.164.194.23) by sun-qmail10 with SMTP; 28 Sep 2003 04:32:42 -0000 Received: from ice.nodomain (localhost [127.0.0.1]) by ice.nodomain (8.12.8p1/8.12.8) with ESMTP id h8S4Wn0S000579; Sat, 27 Sep 2003 21:32:50 -0700 (PDT) (envelope-from dan@ice.nodomain) Received: (from dan@localhost) by ice.nodomain (8.12.8p1/8.12.8/Submit) id h8S4WmT6000578; Sat, 27 Sep 2003 21:32:48 -0700 (PDT) Date: Sat, 27 Sep 2003 21:32:48 -0700 (PDT) From: Dan Strick Message-Id: <200309280432.h8S4WmT6000578@ice.nodomain> To: freebsd-hardware@freebsd.org cc: dan@ice.nodomain cc: gaml@buz.ch Subject: Re: Sil680 RAID Support while installing 5.1-Release 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, 28 Sep 2003 04:32:49 -0000 on Sat, 27 Sep 2003, gaml@buz.ch wrote: > I was wondering about the online Sil 3112 SATA RAID controller on my > Gigabyte 7VAXP board. The 5.1 RELEASE boot CD crashes saying it > couldn't write to root (which is weird, considering it usually should > be able to write to memfs??). That also seems odd to me. My Gigabyte 8KNXP motherboard also has a Sil 3112 SATA RAID controller. I can configure it in BIOS to operate in either "base" (i.e. SATA) mode or in "raid" mode. My 5.1-RELEASE system just ignores the PCI device in either case because there is no 5.1-RELEASE driver for either personality. (The controller identifies itself slightly differently in its PCI configuration space header depending on the mode.) I recall booting the 5.1-RELEASE CD with the Sil 3112 controller in base mode to see if 5.1-RELEASE had a driver for it and had no problem (and no luck either). Someone recently wrote in one of the freebsd-mailing-lists that they had recently committed a Sil 3112 driver (personality unstated) in the 5.1-current branch. Dan Strick