Misc i386 questions

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Misc i386 questions

Sean Kamath-5
Hi.

In my odyssey to get larger disks on my Alix machines, I bought some 16G CompactFlash cards. I put install65.fs on a card and tried to boot it on the Alix, but it just reboots after it loads the kernel.

Meanwhile, the VM I used to dd the install65.fs file to the CF card is running 6.0, so figured I should update it (with a reinstall, rather than updates).  I tried to boot bsd.rd and install 6.5, but it didn’t see the SCSI drive on the VM (but 6.0 did with no issue).  I even downloaded install65.iso and tried to install on a brand new VM (VMware Fusion 11.5 on a Mac running Mojave) with a SCSI drive, but nope.  IDE drives are seen just fine.

So. . . did I just miss something about i386 and SCSI support?  Any suggestions on what to do with the Alix board?  I’m going to see if I can install on the CF card from the VM next.

Sean

Reply | Threaded
Open this post in threaded view
|

Re: Misc i386 questions

Sean Kamath-5
Doh!

set tty com0

Alix is coming along OK now.  Still have questions about i386 and SCSI. . .

Sean


> On Oct 12, 2019, at 23:13, Sean Kamath <[hidden email]> wrote:
>
> Hi.
>
> In my odyssey to get larger disks on my Alix machines, I bought some 16G CompactFlash cards. I put install65.fs on a card and tried to boot it on the Alix, but it just reboots after it loads the kernel.
>
> Meanwhile, the VM I used to dd the install65.fs file to the CF card is running 6.0, so figured I should update it (with a reinstall, rather than updates).  I tried to boot bsd.rd and install 6.5, but it didn’t see the SCSI drive on the VM (but 6.0 did with no issue).  I even downloaded install65.iso and tried to install on a brand new VM (VMware Fusion 11.5 on a Mac running Mojave) with a SCSI drive, but nope.  IDE drives are seen just fine.
>
> So. . . did I just miss something about i386 and SCSI support?  Any suggestions on what to do with the Alix board?  I’m going to see if I can install on the CF card from the VM next.
>
> Sean

Reply | Threaded
Open this post in threaded view
|

Re: Misc i386 questions

Nick Holland
On 10/13/19 12:39 AM, Sean Kamath wrote:

> Doh!
>
> set tty com0
>
> Alix is coming along OK now.  Still have questions about i386 and
> SCSI. . .
>
> Sean
>
>
>> On Oct 12, 2019, at 23:13, Sean Kamath <[hidden email]>
>> wrote:
>>
>> Hi.
>>
>> In my odyssey to get larger disks on my Alix machines, I bought
>> some 16G CompactFlash cards. I put install65.fs on a card and tried
>> to boot it on the Alix, but it just reboots after it loads the
>> kernel.
>>
>> Meanwhile, the VM I used to dd the install65.fs file to the CF card
>> is running 6.0, so figured I should update it (with a reinstall,
>> rather than updates).  I tried to boot bsd.rd and install 6.5, but
>> it didn’t see the SCSI drive on the VM (but 6.0 did with no
>> issue).  I even downloaded install65.iso and tried to install on a
>> brand new VM (VMware Fusion 11.5 on a Mac running Mojave) with a
>> SCSI drive, but nope.  IDE drives are seen just fine.
>>
>> So. . . did I just miss something about i386 and SCSI support?

What SCSI hw are you emulating in your VM?
What happens if you change that?

And to be clear -- when you say it doesn't see the SCSI drive, how
are you not seeing it (i.e., what did you do to "see it" and what
was the result?).

Nick.

Reply | Threaded
Open this post in threaded view
|

Re: Misc i386 questions

Sean Kamath-5


> On Oct 14, 2019, at 20:06, Nick Holland <[hidden email]> wrote:
>
> What SCSI hw are you emulating in your VM?

There doesn’t seem to be a lot of options in VMware Fusion.  There’s a popup in the config for “Bus Type” and you can select “SCSI” or “IDE”, “SATA” and “NVMe”.

On the 6.0 installation, using “SCIS”, I get:

bha3 at pci0 dev 16 function 0 "BusLogic MultiMaster" rev 0x01: apic 1 int 17, BusLogic 9xxC SCSI
bha3: model BT-958, firmware 5.07B
bha3: sync, parity
scsibus2 at bha3: 8 targets, initiator 7
sd0 at scsibus2 targ 0 lun 0: <VMware,, VMware Virtual S, 1.0> SCSI2 0/direct fixed
sd0: 8192MB, 512 bytes/sector, 16777216 sectors

> What happens if you change that?

Not sure what you mean by “that”.  There is no other option for SCSI.  If I change it to “IDE”, for example, I get a “wd0” device:

pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x01
ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x01
pci1 at ppb0 bus 1
pcib0 at pci0 dev 7 function 0 "Intel 82371AB PIIX4 ISA" rev 0x08
pciide0 at pci0 dev 7 function 1 "Intel 82371AB IDE" rev 0x01: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility
wd0 at pciide0 channel 0 drive 0: <VMware Virtual IDE Hard Drive>
wd0: 64-sector PIO, LBA, 6144MB, 12582912 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2’


Note that’s on 6,3

> And to be clear -- when you say it doesn't see the SCSI drive, how
> are you not seeing it (i.e., what did you do to "see it" and what
> was the result?).

By “see it” I mean the installer says there are no disks available to install on.

From the dmesg when I set it to “SCSI”:




If you’d like I can boot the installer for 6.0, 6,.1, etc, and see where it starts to not see it. . .

Sean

PastedGraphic-2.png (21K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Misc i386 questions

Todd C. Miller-3
On Tue, 15 Oct 2019 00:34:38 -0700, Sean Kamath wrote:

> On the 6.0 installation, using 'SCSI', I get:
>
> bha3 at pci0 dev 16 function 0 "BusLogic MultiMaster" rev 0x01: apic 1 int 17
> , BusLogic 9xxC SCSI
> bha3: model BT-958, firmware 5.07B
> bha3: sync, parity
> scsibus2 at bha3: 8 targets, initiator 7
> sd0 at scsibus2 targ 0 lun 0: <VMware,, VMware Virtual S, 1.0> SCSI2 0/direct
>  fixed
> sd0: 8192MB, 512 bytes/sector, 16777216 sectors

There's your problem.  The bha driver is no longer supported by
OpenBSD.  You should use SATA or IDE as the disk type in VMWare.

 - todd

Reply | Threaded
Open this post in threaded view
|

Re: Misc i386 questions

Todd C. Miller-3
On Tue, 15 Oct 2019 10:37:41 -0600, Todd C. Miller wrote:

> There's your problem.  The bha driver is no longer supported by
> OpenBSD.  You should use SATA or IDE as the disk type in VMWare.

Alternately, you should be able to switch the VM to use the mpi
driver by editing the .vmx file for your VM (after shutting down
the VM first).  Just change the lines like:

scsi0.virtualDev = "buslogic"

to:

scsi0.virtualDev = "lsilogic"

VMWare doesn't even support the buslogic driver on 64-bit guests
these days.  New VMs created by VMWare fusion use lsilogic by
default.

 - todd

Reply | Threaded
Open this post in threaded view
|

Re: Misc i386 questions

Sean Kamath-5
I missed that (deprecating buslogic).  Sadly, Fusion on a Mac defaults to buslogic, but doesn’t put it in the config file.  Anyway, switching to lsilogic worked like a charm.  Thank you!

Sean

> On Oct 15, 2019, at 09:49, Todd C. Miller <[hidden email]> wrote:
>
> On Tue, 15 Oct 2019 10:37:41 -0600, Todd C. Miller wrote:
>
>> There's your problem.  The bha driver is no longer supported by
>> OpenBSD.  You should use SATA or IDE as the disk type in VMWare.
>
> Alternately, you should be able to switch the VM to use the mpi
> driver by editing the .vmx file for your VM (after shutting down
> the VM first).  Just change the lines like:
>
> scsi0.virtualDev = "buslogic"
>
> to:
>
> scsi0.virtualDev = "lsilogic"
>
> VMWare doesn't even support the buslogic driver on 64-bit guests
> these days.  New VMs created by VMWare fusion use lsilogic by
> default.
>
> - todd