From owner-freebsd-hardware Sun Aug 31 08:43:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA08206 for hardware-outgoing; Sun, 31 Aug 1997 08:43:35 -0700 (PDT) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA08187; Sun, 31 Aug 1997 08:43:27 -0700 (PDT) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.5/8.8.5) with SMTP id KAA00507; Sun, 31 Aug 1997 10:43:13 -0500 (EST) Date: Sun, 31 Aug 1997 10:43:13 -0500 (EST) From: John Fieber To: Mike Smith cc: mjacob@feral.com, freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG, richard@pegasus.com Subject: Re: Is this (SCSI) tape drive compatible with FreeBSD? In-Reply-To: <199708310213.LAA00788@word.smith.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 31 Aug 1997, Mike Smith wrote: > Whilst the criticism that these drives are "slow" and the tapes > "expensive" is not entirely without basis, it's worth bearing in mind > that these drives are *robust*, and properly stored the media are very > stable. Alas, my viper appears to be failing. It streams nicely winding one direction, but chugs going the other with data rates dropping to about 50K/s from over 100K/s when nicely streaming. :( -john From owner-freebsd-hardware Wed Sep 3 17:31:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA18479 for hardware-outgoing; Wed, 3 Sep 1997 17:31:03 -0700 (PDT) Received: from roguetrader.com (brandon@cold.org [206.81.134.103]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA18471 for ; Wed, 3 Sep 1997 17:30:59 -0700 (PDT) Received: from localhost (brandon@localhost) by roguetrader.com (8.8.5/8.8.5) with SMTP id SAA00370 for ; Wed, 3 Sep 1997 18:30:57 -0600 (MDT) Date: Wed, 3 Sep 1997 18:30:57 -0600 (MDT) From: Brandon Gillespie To: hardware@freebsd.org Subject: disklabel fstype changes from 4.4BSD to System V? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm trying to add a Conner SCSI disk to my system. I'm running 2.2.2-RELEASE, with an AHA-2940W controller. The drive probes as: (ahc0:3:0): "CONNER CFP1060E SUN1.05 245C" type 0 fixed SCSI 2 sd1(ahc0:3:0): Direct-Access 1010MB (2070400 512 byte sectors) However, /stand/sysinstall doesn't seem to want to work right. I can add and write-out a partition for it (just allocating the whole disk to the partition--both True or untrue partition entries cause the same problem, explained below). However, when I go to label I try to make a single filesystem for the whole drive and it gives me the error when I write it out: Error mounting /dev/sd1s1e on /u4 : Invalid argument So I tried what the FAQ suggested, and did a direct disklabel -e sd1.. editing and adding the partition so my disk label looks like: ------------------------------------------------------------------------ # /dev/rsd1c: type: SCSI disk: sd1s1 label: flags: bytes/sector: 512 sectors/track: 3 tracks/cylinder: 36 sectors/cylinder: 108 cylinders: 19169 sectors/unit: 2070357 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 2070357 0 unused 0 0 # (Cyl. 0 -19169*) e: 2070357 0 4.4BSD 0 0 0 ------------------------------------------------------------------------ I can write and save it without receiving any errors. However, viewing the disklabel again shows that partition e has mutated to: e: 2070357 0 System V # (Cyl. 0 -19169*) Anybody have an idea as to what is occuring? -Brandon Gillespie From owner-freebsd-hardware Wed Sep 3 18:42:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA23602 for hardware-outgoing; Wed, 3 Sep 1997 18:42:22 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA23596 for ; Wed, 3 Sep 1997 18:42:18 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id LAA18047; Thu, 4 Sep 1997 11:34:05 +1000 Date: Thu, 4 Sep 1997 11:34:05 +1000 From: Bruce Evans Message-Id: <199709040134.LAA18047@godzilla.zeta.org.au> To: brandon@roguetrader.com, hardware@FreeBSD.ORG Subject: Re: disklabel fstype changes from 4.4BSD to System V? Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >8 partitions: ># size offset fstype [fsize bsize bps/cpg] > c: 2070357 0 unused 0 0 # (Cyl. 0 -19169*) > e: 2070357 0 4.4BSD 0 0 0 >------------------------------------------------------------------------ > >I can write and save it without receiving any errors. However, viewing >the disklabel again shows that partition e has mutated to: > > e: 2070357 0 System V # (Cyl. 0 -19169*) "4.4BSD" is not a valid fstype name. It is misinterpreted as fstype number atoi("4.4BSD") = 4, which happens to be FS_SYSV. Bruce From owner-freebsd-hardware Wed Sep 3 20:16:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA29142 for hardware-outgoing; Wed, 3 Sep 1997 20:16:31 -0700 (PDT) Received: from roguetrader.com (brandon@cold.org [206.81.134.103]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA29137 for ; Wed, 3 Sep 1997 20:16:29 -0700 (PDT) Received: from localhost (brandon@localhost) by roguetrader.com (8.8.5/8.8.5) with SMTP id VAA00830; Wed, 3 Sep 1997 21:16:17 -0600 (MDT) Date: Wed, 3 Sep 1997 21:16:17 -0600 (MDT) From: Brandon Gillespie To: Bruce Evans cc: hardware@FreeBSD.ORG Subject: Re: disklabel fstype changes from 4.4BSD to System V? In-Reply-To: <199709040134.LAA18047@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 4 Sep 1997, Bruce Evans wrote: > > "4.4BSD" is not a valid fstype name. It is misinterpreted as fstype > number atoi("4.4BSD") = 4, which happens to be FS_SYSV. Oops... I wonder how I started doing 4.4BSD rather than 4.2BSD... That looks like the only problem (still not sure what was up with /stand/sysinstall). Sorry for the noise :) -Brandon From owner-freebsd-hardware Wed Sep 3 20:48:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA01174 for hardware-outgoing; Wed, 3 Sep 1997 20:48:18 -0700 (PDT) Received: from hermes.svf.uib.no (hermes.svf.uib.no [129.177.128.15]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA01166 for ; Wed, 3 Sep 1997 20:48:11 -0700 (PDT) Received: from ronny (ti21a05-0034.dialup.online.no [130.67.193.98]) by hermes.svf.uib.no (8.8.7/8.7.3) with ESMTP id FAA25427 for ; Thu, 4 Sep 1997 05:45:43 +0200 (MET DST) Message-Id: <199709040345.FAA25427@hermes.svf.uib.no> From: "Ronny Jordalen" To: Subject: LS 120 Date: Thu, 4 Sep 1997 05:47:10 +0200 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi I just recently bought a new machine, and decided to go for the new LS 120 drive, that supports both standard floppy disks and a 120 meg disk. However, there are problems. Although I'm able to make the boot.flp for FreeBSD, the drive is unable to read it beyond the BOOT: stage. This is also true for Linux: I'm able to create both disks (boot and root), but the drive isn't able to read the root disk. I've tested the disks on another computer, and there they work flawlessly. Main board (Asus TX97-E) is supposed to support this device, and after upgrading to bios v1.07 it's now possible to boot from the LS-120 drive. The drive seems to be working allright under Windows, though I haven't tested it thoroughly. I was wondering if ppl have had similar experiences with this drive, or if it's a local problem? Has anyone been able to install FreeBSD from such a drive (and the 2.2.2 cd?). One might wonder if I wouldn't have been better of with a standard floppy drive and instead add a zip-drive? Well, my mistake :-) --Ronny From owner-freebsd-hardware Wed Sep 3 21:32:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA03578 for hardware-outgoing; Wed, 3 Sep 1997 21:32:20 -0700 (PDT) Received: from smoke.marlboro.vt.us (smoke.marlboro.vt.us [198.206.215.91]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA03570; Wed, 3 Sep 1997 21:32:08 -0700 (PDT) Received: (from cgull@localhost) by smoke.marlboro.vt.us (8.8.7/8.8.7/cgull) id AAA14263; Thu, 4 Sep 1997 00:32:03 -0400 (EDT) Date: Thu, 4 Sep 1997 00:32:03 -0400 (EDT) Message-Id: <199709040432.AAA14263@smoke.marlboro.vt.us> From: john hood MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-hardware@freebsd.org, freebsd-scsi@freebsd.org Subject: twiddling compression on a Sony SDT-7000 DAT drive, and slow dumps X-Mailer: VM 6.31 under Emacs 19.34.2 Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk so, i have this lovely little Sony SDT-7000 tape drive. it had the jumper that controls the compression default set to not compress. a couple days ago, i spent much, much too long trying to get this thing to enable compression, by way of the more-or-less usual compression mode page on DAT drives and scsi(8). no matter what i tried, i couldn't get anything to happen to the drive. i ended up applying the PC Solution (tm): rip the box apart and set the bleeding jumper. since i still want to be able to turn off compression occasionally, i'm still left with trying to get it to work in software. Sony tech support hasn't been much help so far (their DAT support people are out on vacation or somesuch). has anybody been able to get this to work? am i possibly beating my head against old firmware on the drive? am i missing something stupid? scsi -f /dev/rst0.ctl -c "0x15 0x10 0 0 0x14 0" \ -o 0x14 "14 0 10 0 0f e c0 80 0 0 0 20 0 0 0 0 0 0 0 0" [...] Aug 25 01:03:54 smoke /kernel: FreeBSD 2.2.2-RELEASE #2: Tue Aug 19 15:27:24 EDT 1997 Aug 25 01:03:54 smoke /kernel: cgull@smoke.marlboro.vt.us:/usr/src/sys/compile/NEWSMOKE [...] Aug 25 01:03:54 smoke /kernel: ncr0 rev 2 int a irq 9 on pci0:10 Aug 25 01:03:54 smoke /kernel: (ncr0:0:0): "SEAGATE ST12400N 8650" type 0 fixed SCSI 2 Aug 25 01:03:54 smoke /kernel: sd0(ncr0:0:0): Direct-Access Aug 25 01:03:54 smoke /kernel: sd0(ncr0:0:0): 10.0 MB/s (100 ns, offset 8) Aug 25 01:03:54 smoke /kernel: 2048MB (4194685 512 byte sectors) Aug 25 01:03:54 smoke /kernel: (ncr0:1:0): "SEAGATE ST11200N SUN1.05 9500" type 0 fixed SCSI 2 Aug 25 01:03:54 smoke /kernel: sd1(ncr0:1:0): Direct-Access Aug 25 01:03:54 smoke /kernel: sd1(ncr0:1:0): 10.0 MB/s (100 ns, offset 8) Aug 25 01:03:54 smoke /kernel: 1005MB (2059140 512 byte sectors) Aug 25 01:03:54 smoke /kernel: (ncr0:2:0): "TOSHIBA CD-ROM XM-3401TA 0283" type 5 removable SCSI 2 Aug 25 01:03:54 smoke /kernel: cd0(ncr0:2:0): CD-ROM Aug 25 01:03:55 smoke /kernel: cd0(ncr0:2:0): asynchronous. Aug 25 01:03:55 smoke /kernel: can't get the size Aug 25 01:03:55 smoke /kernel: (ncr0:4:0): "SONY SDT-7000 0150" type 1 removable SCSI 2 Aug 25 01:03:55 smoke /kernel: st0(ncr0:4:0): Sequential-Access Aug 25 01:03:55 smoke /kernel: st0(ncr0:4:0): 10.0 MB/s (100 ns, offset 8) Aug 25 01:03:55 smoke /kernel: density code 0x13, drive empty additionally, dumps run really slowly on this machine. i get about 350-400 KB/s dumping to /dev/null. the tape drive doesn't run any faster, obviously, and shoeshines away. tar or other filesystem users run at a reasonable speed. is this normal or not? any obvious suspects? --jh -- John Hood cgull@smoke.marlboro.vt.us Predictably, they all eventually wandered away, rubbing their bruises and brushing mud out of their hair. Some went off to work for the ESA, launching much smaller rockets into low orbits, while others elected to sit on their front porches drinking Jim Beam from the bottle and launching bottle rockets from the empties. [Jordan Hubbard] From owner-freebsd-hardware Thu Sep 4 03:39:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA20433 for hardware-outgoing; Thu, 4 Sep 1997 03:39:34 -0700 (PDT) Received: from mail.nacamar.de (mail.nacamar.de [194.162.162.200]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA20411; Thu, 4 Sep 1997 03:39:21 -0700 (PDT) Received: from newsfeed (newsfeed.nacamar.de [194.162.162.196]) by mail.nacamar.de (8.8.7/8.8.7) with SMTP id MAA09267; Thu, 4 Sep 1997 12:39:19 +0200 (CEST) Message-Id: <3.0.3.32.19970904123822.00b32d40@mail.nacamar.de> X-Sender: petzi@mail.nacamar.de X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Thu, 04 Sep 1997 12:38:22 +0200 To: hardware@freebsd.org, isp@freebsd.org From: Michael Beckmann Subject: FDDI experiences ? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greetings, I'd like to hear about people's experiences with a FDDI interface in a FreeBSD server. How good is the throughput, what about CPU load, and did you experience any problems with it ? How does it compare to a 100 Mbps Ethernet interface ? Michael From owner-freebsd-hardware Thu Sep 4 13:18:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA20845 for hardware-outgoing; Thu, 4 Sep 1997 13:18:56 -0700 (PDT) Received: from kalypso.cybercom.net (kalypso.cybercom.net [209.21.136.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA20840 for ; Thu, 4 Sep 1997 13:18:52 -0700 (PDT) Received: from atlanta (mfd-dial2-13.cybercom.net [209.21.137.45]) by kalypso.cybercom.net (8.8.5/8.6.12) with SMTP id QAA16345 for ; Thu, 4 Sep 1997 16:15:19 -0400 (EDT) Message-Id: <3.0.3.32.19970904101749.009f7a10@cybercom.net> X-Sender: ksmm@cybercom.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.3 (32) Date: Thu, 04 Sep 1997 10:17:49 -0400 To: hardware@freebsd.org From: The Classiest Man Alive Subject: Re: LS 120 In-Reply-To: <199709040345.FAA25427@hermes.svf.uib.no> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 05:47 AM 9/4/97 +0200, you wrote: >I was wondering if ppl have had similar experiences with this drive, or if >it's a local problem? Has anyone been able to install FreeBSD from such a >drive (and the 2.2.2 cd?). I looked into this drive and couldn't find any indication that anything besides Windows 95 was supported, including other 16- and 32-bit variants of Windows or OS/2, so I held off on buying one. I also remember something strange about the geometry (head/track count, or something), but I didn't think that would affect the ability to use standard floppies. >One might wonder if I wouldn't have been better >of with a standard floppy drive and instead add a zip-drive? Well, my >mistake :-) Ahh, life on the cutting edge. :-) K.S. From owner-freebsd-hardware Fri Sep 5 17:27:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA10529 for hardware-outgoing; Fri, 5 Sep 1997 17:27:48 -0700 (PDT) Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA10522 for ; Fri, 5 Sep 1997 17:27:43 -0700 (PDT) Received: (from arg@localhost) by arg1.demon.co.uk (8.8.5/8.8.5) id BAA09212; Sat, 6 Sep 1997 01:26:53 +0100 (BST) Date: Sat, 6 Sep 1997 01:26:52 +0100 (BST) From: Andrew Gordon X-Sender: arg@server.arg.sj.co.uk To: freebsd-hardware@freebsd.org Subject: Problems with 16650 UARTs Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a card with Startech 16C650CJ UARTs which is behaving rather oddly. Initially, I was testing with stock 2.2.2-R, assuming that these beasts were 16550-compatible by default. I later tried 2.2.2-STABLE, and the latter with the explicit 16650 support from -current merged into sio.c (resulting in a sio.c which is the same as -current apart from some stuff to do with COMCONSOLE). All give the same result. The behaviour is that the ports initially work OK, and will transmit or receive continuously without problems, but after a short burst of simultaneous transmission and reception, the receiver locks up such that all received characters are lost silently (Tx continues to work OK). Closing and re-opening the device unlocks it temporarily. Most of my testing was at 115200, but it failed just as easily at 19200. The problem occurs whether or not the port is configured for RTS/CTS flow control. My initial test was with pppd on both ends (the other machine having a conventional 16550). I then wrote a trivial dumb-terminal program for testing (hacked to transmit 1000 copies of each character I typed to generate enough traffic). While this could obviously be a faulty card, the fault is identical on both ports (and the card has two separate 16C650CJ chips, plus a minimal amount of TTL for address decode) so this seems unlikely. Besides ideas for fixes, I would be interested in any pointers to 16650 datasheets (Altavista offers me several companies called Startech that don't make UARTs, and lots of places that sell cards with 16650s on them, but not the manufacturer!). Thanks. Andrew. From owner-freebsd-hardware Fri Sep 5 19:22:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA14832 for hardware-outgoing; Fri, 5 Sep 1997 19:22:09 -0700 (PDT) Received: from bob.tri-lakes.net ([207.3.81.6]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id TAA14825 for ; Fri, 5 Sep 1997 19:22:04 -0700 (PDT) Received: from [207.3.81.149] by bob.tri-lakes.net (NTMail 3.02.13) with ESMTP id ka266692 for ; Fri, 5 Sep 1997 21:22:03 -0500 Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 05 Sep 1997 20:49:58 -0000 (GMT) From: Chris Dillon To: Andrew Gordon Subject: RE: Problems with 16650 UARTs Cc: freebsd-hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 06-Sep-97 Andrew Gordon wrote: >I have a card with Startech 16C650CJ UARTs which is behaving rather >oddly. > >Initially, I was testing with stock 2.2.2-R, assuming that these beasts >were 16550-compatible by default. I later tried 2.2.2-STABLE, and >the latter with the explicit 16650 support from -current merged into >sio.c >(resulting in a sio.c which is the same as -current apart from some >stuff to do with COMCONSOLE). All give the same result. > >The behaviour is that the ports initially work OK, and will transmit >or receive continuously without problems, but after a short burst of >simultaneous transmission and reception, the receiver locks up >such that all received characters are lost silently (Tx continues to work >OK). Closing and re-opening the device unlocks it temporarily. >Most of my testing was at 115200, but it failed just as easily at 19200. >The problem occurs whether or not the port is configured for RTS/CTS >flow control. > >My initial test was with pppd on both ends (the other machine having >a conventional 16550). I then wrote a trivial dumb-terminal program >for testing (hacked to transmit 1000 copies of each character I >typed to generate enough traffic). > >While this could obviously be a faulty card, the fault is identical >on both ports (and the card has two separate 16C650CJ chips, plus >a minimal amount of TTL for address decode) so this seems unlikely. > > >Besides ideas for fixes, I would be interested in any pointers to >16650 datasheets (Altavista offers me several companies called >Startech that don't make UARTs, and lots of places that sell cards >with 16650s on them, but not the manufacturer!). > Bingo... I have been plagued with this same problem for some time, but thought it was just my lousy, clueless ISP at the root of it all (uses NT of all things... and Telebit Netblazer term servers. Are those any good?). I run 2.2-STABLE (recently cvsupped and made world) with userland ppp on an internal USR Sportster 33k6 with the port locked at 115200 using hardware flow control. I can be chatting on IRC, browsing web pages, and downloading some mail when all incoming data comes to a halt (even sometimes when just doing nothing). The only fix seems to be to kill the ppp session and dial in again (I usually just 'quit' and then run userland ppp all over again). I know that outgoing packets still work because anything I type in an IRC channel makes it out into the world.. I just don't get anything back. I don't know if this means much, but it almost ALWAYS happens when I get my mail, as this initially made me think it was just some anomaly between my ISP's mail server and the terminal server. It happened most often with Netscape's POP3 client and with popclient, but almost never with XFMail's POP3 client. --- Chris Dillon --- cdillon@tri-lakes.net --- Powered by FreeBSD, the best free OS on the planet ---- (http://www.freebsd.org) From owner-freebsd-hardware Fri Sep 5 21:15:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA19502 for hardware-outgoing; Fri, 5 Sep 1997 21:15:33 -0700 (PDT) Received: from bob.tri-lakes.net ([207.3.81.6]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id VAA19495 for ; Fri, 5 Sep 1997 21:15:27 -0700 (PDT) Received: from [207.3.81.149] by bob.tri-lakes.net (NTMail 3.02.13) with ESMTP id ra266751 for ; Fri, 5 Sep 1997 23:15:27 -0500 Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 05 Sep 1997 21:29:46 -0000 (GMT) From: Chris Dillon To: freebsd-hardware@freebsd.org Subject: Tape geometries for the floppy-tape driver Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I notice that FreeBSD's ft driver has been stagnant for some time. I noticed this when trying to use some 2120EX and 2120XL tapes in my HP Colorado Jumbo 350. Apparently the standard 2120 tapes work fine, but /usr/src/sys/i386/isa/ft.c lists a very short and incomplete tape geometry table (a whole 6 tapes!). My attempts to find the geometries of these new, larger tapes has been fruitless so far (I'm assuming thats all I need to get these tapes to work). I've managed to figure out what some of the fields mean in the geometry table, but not all of them. Correct me if I'm wrong, but here is what I gather the table represents, for example: { 2, 2, "QIC-80", "307.5/550", 28, 150, 4800, 128, 19200 }, This is a standard DC2120 250MB compressed tape. First two fields just seem to be some kind of ID tag internal to the driver. The "307.5" is tape length in feet, and the 550 is the tape coercivity in oersteds. The next field is the number of serpentine tracks on the tape. The remainder of the fields elude me. 19200 could possibly be bits/inch, but i think it is supposed to be 14700 for this particular tape. Web index searches on the subject of tape geometries didn't get me much. I found the geometries of the DC2120 and DC2120XL tapes, and thats it. Basically, the whole point of all this hot air was to ask for some help in adding new geometries to the tape table. Actually.. anyone have any idea how hard it would be to port the Linux floppy-tape driver over? (I have no clue how to do so or I would have started already ) It looks almost as if it auto-adapts to any tape size as it has no geometry table. If it did, I would have already copied the relevant data from it. :( --- Chris Dillon --- cdillon@tri-lakes.net --- Powered by FreeBSD, the best free OS on the planet ---- (http://www.freebsd.org) From owner-freebsd-hardware Fri Sep 5 21:56:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA21998 for hardware-outgoing; Fri, 5 Sep 1997 21:56:00 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA21992 for ; Fri, 5 Sep 1997 21:55:56 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id VAA16643; Fri, 5 Sep 1997 21:55:33 -0700 (PDT) To: Chris Dillon cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Tape geometries for the floppy-tape driver In-reply-to: Your message of "Fri, 05 Sep 1997 21:29:46 -0000." Date: Fri, 05 Sep 1997 21:55:32 -0700 Message-ID: <16639.873521732@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I notice that FreeBSD's ft driver has been stagnant for some time. I This driver has been, in fact, abandoned. Jordan From owner-freebsd-hardware Fri Sep 5 23:54:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA28312 for hardware-outgoing; Fri, 5 Sep 1997 23:54:23 -0700 (PDT) Received: from lariat.lariat.org (ppp0.lariat.org@[129.72.251.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA28307 for ; Fri, 5 Sep 1997 23:54:20 -0700 (PDT) Received: from solo ([129.72.251.10] (may be forged)) by lariat.lariat.org (8.8.6/8.8.6) with SMTP id AAA22876; Sat, 6 Sep 1997 00:50:31 -0600 (MDT) Message-Id: <3.0.3.32.19970906005338.008a3d40@mail.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Sat, 06 Sep 1997 00:53:38 -0600 To: cdillon@tri-lakes.net, arg@arg1.demon.co.uk From: Brett Glass Subject: RE: Problems with 16650 UARTs Cc: freebsd-hardware@FreeBSD.ORG In-Reply-To: <8825650A.000FD662.00@IWNS2.infoworld.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 08:49 PM 9/5/97 +0000, cdillon@tri-lakes.net wrote: I've been working on an x86-specific, highly-tuned driver that's designed to work only with permanently-attached '550 or better UARTs. (Right now, it doesn't support shared IRQs, but I'm looking at ways to add this feature without killing efficiency.) The new driver uses code I developed years ago for the PC/AT, where timing was everything. It enables interrupts only when the port isn't receiving, and switches seamlessly to timer-driven polling when characters are streaming in. Overhead is about the lowest it can be given the data structures involved. (I'm using some code sequences that GCC never seems to generate.) Will publish this when it gets closer to production quality, and when I've got more confidence that I understand the kernel stuff. --Brett P.S. in anticipation of flames: I know that some folks will want (or need!) to stay with sio, but this driver will be good for those who need bleeding-edge speed on Intel platforms (e.g. ISPs using FreeBSD as a zillion-port terminal server). At 08:49 PM 9/5/97 +0000, you wrote: >Bingo... I have been plagued with this same problem for some time, but >thought it was just my lousy, clueless ISP at the root of it all (uses NT >of all things... and Telebit Netblazer term servers. Are those any good?). >I run 2.2-STABLE (recently cvsupped and made world) with userland ppp on an >internal USR Sportster 33k6 with the port locked at 115200 using hardware >flow control. I can be chatting on IRC, browsing web pages, and downloading >some mail when all incoming data comes to a halt (even sometimes when just >doing nothing). The only fix seems to be to kill the ppp session and dial >in again (I usually just 'quit' and then run userland ppp all over again). >I know that outgoing packets still work because anything I type in an IRC >channel makes it out into the world.. I just don't get anything back. >I don't know if this means much, but it almost ALWAYS happens when I get >my mail, as this initially made me think it was just some anomaly >between my ISP's mail server and the terminal server. It happened most >often with Netscape's POP3 client and with popclient, but almost never with >XFMail's POP3 client. > >--- Chris Dillon >--- cdillon@tri-lakes.net >--- Powered by FreeBSD, the best free OS on the planet >---- (http://www.freebsd.org) > > > > From owner-freebsd-hardware Sat Sep 6 04:44:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA10114 for hardware-outgoing; Sat, 6 Sep 1997 04:44:18 -0700 (PDT) Received: from mailhost.interact.se (mailhost.interact.se [194.18.135.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA10109 for ; Sat, 6 Sep 1997 04:44:13 -0700 (PDT) Received: from chris (rimi.interact.se [194.18.135.76]) by mailhost.interact.se (8.8.5/8.8.5) with SMTP id NAA04500 for ; Sat, 6 Sep 1997 13:42:37 +0200 (MET DST) Message-ID: <34114227.6A0C@interact.se> Date: Sat, 06 Sep 1997 13:44:39 +0200 From: Christopher Lindbergh Reply-To: Christopher.Lindbergh@interact.se X-Mailer: Mozilla 3.01Gold (WinNT; I) MIME-Version: 1.0 To: freebsd-hardware@FreeBSD.ORG Subject: TOKEN RING nic Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Are they anybody who made the driver for Token Ring NIC? From owner-freebsd-hardware Sat Sep 6 18:52:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA18214 for hardware-outgoing; Sat, 6 Sep 1997 18:52:30 -0700 (PDT) Received: from bob.tri-lakes.net ([207.3.81.6]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id SAA18202 for ; Sat, 6 Sep 1997 18:52:23 -0700 (PDT) Received: from [207.3.81.149] by bob.tri-lakes.net (NTMail 3.02.13) with ESMTP id pa267217 for ; Sat, 6 Sep 1997 20:52:30 -0500 Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <16639.873521732@time.cdrom.com> Date: Sat, 06 Sep 1997 20:44:47 -0000 (GMT) From: Chris Dillon To: "Jordan K. Hubbard" Subject: Re: Tape geometries for the floppy-tape driver Cc: freebsd-hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 06-Sep-97 Jordan K. Hubbard wrote: >> I notice that FreeBSD's ft driver has been stagnant for some time. I > >This driver has been, in fact, abandoned. > > Jordan I see.. That would explain the situation. :) But with the new proliferance of floppy-based tape devices (IDE too, but I won't go there..), wouldn't it be wise for *someone* to try and keep it just a little up to date? I am going to try (cross fingers) my best to add some tape geometries to that table (gonna have to read the source to find out what all those fields are, i guess.. unless someone is kind enough to tell me) and test them out. Would there be any problems with someone submitting the changes if I do so? --- Chris Dillon --- cdillon@tri-lakes.net --- Powered by FreeBSD, the best free OS on the planet ---- (http://www.freebsd.org) From owner-freebsd-hardware Sat Sep 6 21:01:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA24146 for hardware-outgoing; Sat, 6 Sep 1997 21:01:55 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA24139 for ; Sat, 6 Sep 1997 21:01:50 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id VAA15221; Sat, 6 Sep 1997 21:01:39 -0700 (PDT) To: Chris Dillon cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Tape geometries for the floppy-tape driver In-reply-to: Your message of "Sat, 06 Sep 1997 20:44:47 -0000." Date: Sat, 06 Sep 1997 21:01:39 -0700 Message-ID: <15218.873604899@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I see.. That would explain the situation. :) But with the new > proliferance of floppy-based tape devices (IDE too, but I won't go > there..), wouldn't it be wise for *someone* to try and keep it just a > little up to date? I am going to try (cross fingers) my best to add some Yes. Push forward a volunteer in -committers and it shall be. ;-) Jordan From owner-freebsd-hardware Sat Sep 6 23:20:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA29771 for hardware-outgoing; Sat, 6 Sep 1997 23:20:36 -0700 (PDT) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA29763 for ; Sat, 6 Sep 1997 23:20:32 -0700 (PDT) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id IAA06439; Sun, 7 Sep 1997 08:19:53 +0200 (CEST) To: Chris Dillon cc: "Jordan K. Hubbard" , freebsd-hardware@FreeBSD.ORG Subject: Re: Tape geometries for the floppy-tape driver In-reply-to: Your message of "Sat, 06 Sep 1997 20:44:47 -0000." Date: Sun, 07 Sep 1997 08:19:53 +0200 Message-ID: <6437.873613193@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message , Chris Dillon writes: > >On 06-Sep-97 Jordan K. Hubbard wrote: >>> I notice that FreeBSD's ft driver has been stagnant for some time. I >> >>This driver has been, in fact, abandoned. >> >> Jordan > >I see.. That would explain the situation. :) But with the new >proliferance of floppy-based tape devices (IDE too, but I won't go >there..), wouldn't it be wise for *someone* to try and keep it just a >little up to date? I am going to try (cross fingers) my best to add some >tape geometries to that table (gonna have to read the source to find out >what all those fields are, i guess.. unless someone is kind enough to tell >me) and test them out. Would there be any problems with someone >submitting the changes if I do so? By all means go for it! We'd be more than happy of you breath a little life into this driver! -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop."