From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Nielsen To: 9fans@cse.psu.edu Subject: Re: [9fans] venti+fossil, the boot process, and 48-bit lba Message-ID: <20031022171017.GZ834@cassie.foobarbaz.net> References: <20031022154323.GY834@cassie.foobarbaz.net> <2fe61d2b01e01d7db540f3315d679848@caldo.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2fe61d2b01e01d7db540f3315d679848@caldo.demon.co.uk> User-Agent: Mutt/1.5.3i Date: Wed, 22 Oct 2003 10:10:17 -0700 Topicbox-Message-UUID: 77cdeb7c-eacc-11e9-9e20-41e7f4b1d025 On Wed, Oct 22, 2003 at 04:57:55PM +0100, Charles Forsyth wrote: > > how does 9load cause that to happen? > the thing that starts venti is a normal kernel, which > should handle 48-bit LBA. does 9load (not knowing > about them) leave the ATA in a state where the kernel > can't use 48-bits either? no idea. my conclusion was a semi-educated guess. > i can see that 9load not knowing 48-bit addressing wouldn't > be able to see boot/9fat partitions beyond a certain point, > or perhaps with the right geometry. something weird is going on. i originally had the venti conf on one of the 167G drives, it would get to 'time...' in the boot sequence, and then suicide with an invalid address. so i moved the venti conf to one of the smaller discs, and then it found the venti conf and barfed because it couldn't open the arenas on the 167G discs. based on that, i am assuming something is hating those large discs. do you have any other ideas? -- Christopher Nielsen "They who can give up essential liberty for temporary safety, deserve neither liberty nor safety." --Benjamin Franklin