From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Sat, 2 Jan 2016 16:26:39 -0800 To: 9fans@9fans.net Message-ID: In-Reply-To: <20160102115515.GA498@polynum.com> References: <20160102115515.GA498@polynum.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Install: root file system Topicbox-Message-UUID: 7d3f6ccc-ead9-11e9-9d60-3106f5b1d025 i'm not sure what the root cause of your problem is, due to not enough data, but it does remind me of a limitation that has been bugging me. to boot from usb cleanly, i added a bit to the boot process that creates a loopback sd device /dev/sdu0 that points to the usb disk device. i've been booting my auth server this way for some time. it seems to me that i really screwed this up. what i really want is a sd device that always points to the boot drive, the one bios refers to as 0x80. givem this, one can then put something like "bootargs=local!#S/sdB0/fs" in plan9.ini. this will allow the 9atom usb install image to run off any bootable media (for which we have drivers). so, i'm preparing a patch that will present the boot device as /dev/sdB0 regardless of what underlying disk driver or protocol is being used. here's the output from my test machine. it's been booted over the network, but even so bios has assigned a 0x80 drive, and it's been found and configured: >> sdB loop #S/sdF0/data sdE ahci ahci port 0xfffffe00fb538000 pci 0.17.4: 64a ncq alp led clo pmb slum pslum ems apts alhd xonly smb elmt iss 3 ncs 31 np 4 ghc 80000002 isr 0 pi f 0-3 ver 10300 sdF ahci ahci port 0xfffffe00fb532000 pci 0.31.2: 64a ncq alp led clo pmb slum pslum ems apts alhd xonly smb elmt iss 3 ncs 31 np 6 ghc 80000002 isr 0 pi 3f 0-5 ver 10300 sdN nvme port 0xfffffe00fb410000 pci 2.0.0 v1.0 rst 0 ctg 1 ams 0 stride 1 to 20000 fatal 0 sdO nvme port 0xfffffe00fb300000 pci 4.0.0 v1.1 rst 0 ctg 1 ams 0 stride 1 to 30000 fatal 0 - erik