Path: utzoo!attcan!uunet!seismo!sundc!pitstop!sun!amdcad!ames!zodiac!joyce!csl!porthos!aida From: aida@porthos.csl.sri.com (Hitoshi Aida) Newsgroups: comp.unix.wizards Subject: Re: Autoconfig Message-ID: <5699@csl.CSL.SRI.COM> Date: 30 Jun 88 01:15:51 GMT References: <9600@eddie.MIT.EDU> Sender: usenet@csl.CSL.SRI.COM Reply-To: aida@porthos.UUCP (Hitoshi Aida) Organization: Computer Science Lab, SRI International Lines: 25 In article <9600@eddie.MIT.EDU> nessus@athena.mit.edu (Doug Alan) writes: > ... > A more preculiar mode of failure happens when I remove a >second disk controller. The autoconfig sequence finds the first >controller twice! And both times it finds it at the same CSR address. >It assigns each disk drive to two different device names. The >autoconfig sequence then merrily continues on, and seems to be working >fine, until the system finally gets to the point where it tries to >give you a /bin/sh. At this point it hangs. The problem is "the standard addresses" embedded in the driver. If autoconf fails to find second controller at the address specified in the configuration file, then try to find it at the standard addresses and finally finds the first controller located at one of such addresses! I think the best solution is to never use standard addresses. You can either patch source or object of the driver so that the first element of udastd[] etc. will have a value of 0 (short). -------- Hitoshi AIDA (aida%inosai.u-tokyo.junet%utokyo-relay@relay.cs.net) Dept. of Electrical Engineering, The University of Tokyo Current Address: aida@csl.sri.com Computer Science Lab, SRI International