From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu Subject: Re: [9fans] problems with SCSI card and file server From: nemo@gsyc.escet.urjc.es MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-evxsawuyizepsonijfqerrsydf" Message-Id: <20010511064046.28573199E3@mail.cse.psu.edu> Date: Fri, 11 May 2001 08:46:15 +0200 Topicbox-Message-UUID: 9e6fc8d4-eac9-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-evxsawuyizepsonijfqerrsydf Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit The (ide) fs kernel I use seems to disklike some floppy units on some machines; the simptom is like yours. I tried replacing the unit it dislikes w/ one it worked with on a different machine. It didn't work either. Thus I think it's the controller on the main board the thing that the kernel did not like (same floppy unit, same floppy). But I didn't track this any further, sorry. (both floppy units work properly w/ other operating systems, so I think it's just the way the fs kernel uses it). hth --upas-evxsawuyizepsonijfqerrsydf Content-Type: message/rfc822 Content-Disposition: inline Return-Path: <9fans-admin@cse.psu.edu> Received: from mail.cse.psu.edu (postfix@psuvax1.cse.psu.edu [130.203.4.6]) by gsyc.escet.urjc.es (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id VAA17326; Thu, 10 May 2001 21:09:36 +0200 X-Authentication-Warning: gsyc.escet.urjc.es: Host postfix@psuvax1.cse.psu.edu [130.203.4.6] claimed to be mail.cse.psu.edu Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.8.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 15D3E19A20; Thu, 10 May 2001 15:09:12 -0400 (EDT) Received: from cosym.net (gcollyer-14.dsl.speakeasy.net [216.254.93.14]) by mail.cse.psu.edu (CSE Mail Server) with SMTP id 2A3E8199F8 for <9fans@cse.psu.edu>; Thu, 10 May 2001 15:08:31 -0400 (EDT) From: anothy@cosym.net To: 9fans@cse.psu.edu MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Message-Id: <20010510190831.2A3E8199F8@mail.cse.psu.edu> Subject: [9fans] problems with SCSI card and file server Sender: 9fans-admin@cse.psu.edu Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0.1 Precedence: bulk Reply-To: 9fans@cse.psu.edu List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Archive: Date: Thu, 10 May 2001 15:04:06 -0400 two seperate problems: adding SCSI to a terminal and setting up a fs. 1) i've got an IDE terminal running the current distribution. works great. i've added a SCSI card (buslogic BT-948). still no problem. but when i attach disks to that card, the system hangs halfway through booting. after a bunch of debugging prints, it seems that things are hanging in this line in init.c: execl("/bin/rc", "rc", "-c", ". /rc/bin/termrc; home=/usr/$user; cd; . lib/profile", 0); it's completing termrc properly - adding "rc" to the end gives me a prompt from which things like 'cat' work. so i did the rest of the line manually. it fails on 'cd'. it just hangs. the kernel's still working (mouse moves, responds to ^t^tp), but cd never returns. skipping that, it'll fail on 'rio' in my lib/profile. does anyone understand what's going on? the system is an AMD Athlon 1.2Ghz system, ASUS A7V133 motherboard. 2) i'm trying to build a file server. i've built the kernel, but it hangs before getting up to config. turning on chat in dosfs.c indicates it's hanging in getclust (i see the 'getclust read addr 0' line, then nothing). this is on the above system, but the behaviour is the same with or without SCSI card and/or disks. i then tried the same floppy on another system - a Pentium 100, unknown motherboard - and it fails very differently: it gets to the normal cpu0: line, then prints 'cpu0: 100Mhz' five times on a line, for several lines, before panicing. confused by the two very different failure modes, i threw the disk into someone else's Compaq Presario - and it came up fine, dropping right into config mode (the nvr on the floppy is junk). this isn't useful, as this system has no SCSI disks (and isn't mine), but might be informative. so again, i'm confused here. the floppy drive on these systems are all known to be good - i can read back and verify the entire contents of the disk - and the floppy itself is aparently fine, as it works on the compaq. i've also tried getting the kernel via bootp, which doesn't change the behaviour at all. anyone? help on either of these problems would be very appreciated. -α. --upas-evxsawuyizepsonijfqerrsydf--