Re: 6.4/hppa regression: no LAN or UWSCSI on C360
Mark Kettenis <[email protected]> Mon, 24 Dec 2018 21:19:32 +0100 (CET)
| Newsgroups | gmane.os.openbsd.hppa |
|---|---|
| Message-ID | <[email protected]> |
> From: Miod Vallat <[email protected]> > Date: Mon, 24 Dec 2018 20:05:02 +0000 (UTC) > > > I've just been trying to install OpenBSD on an HP C360, and running into > > some problems. OpenBSD 6.4 boots okay, but it does not recognize either > > the machine's LAN interface or its internal ultra-wide SCSI bus, making > > it pretty much useless except as a doorstop. > > > > I then tried installing older versions to see if this was a regression, > > and it is. OpenBSD 6.2 recognizes those devices just fine. > > Argh. This is a regression in the installation kernel only, which was > introduced by changes I wrote in the 6.4 development cycle. I > incorrectly removed the attachment rule for dino at uturn1. Sorry about > that. > > Unfortunately, there is no easy way to repair this from UKC; but if you > are able to use a serial console during the installation or upgrade, you > may use UKC to swap uturn0 and uturn1; instead of losing the on-board > devices (Ethernet, SCSI), this will lose the PCI cards (and thus, the > display). > > To achieve this, boot the installation media and, at the "boot>" prompt, > enter "-c". Then, at the "UKC>" prompt, enter "change uturn0". This will > continue in the following dialog, where you need to answer the questions > as follows: > > UKC> change uturn0 > 100 uturn0 at mainbus0 offset -1 irq -1 flags 0x0 > change (y/n) ? y > offset [-1] ? 0xff88000 > irq [-1] ? (press return) > flags [0] ? (press return) > 100 uturn0 changed > 100 uturn0 at mainbus0 offset 0xff88000 irq -1 flags 0x0 > UKC> > > Then when you're back at the "UKC>" prompt, enter "quit". The kernel > will resume booting, and will find the Ethernet and SCSI controllers, > but not the sti(4) display. > > You can then proceed with the installation or upgrade as usual. > > > Note that, once you have installed or upgraded your system, the regular > kernel does not suffer from this problem and will recognize all your > devices. > > > The source code fix can be found below. Should I commit that fix to -current? > Index: sys/arch/hppa/conf/RAMDISK > =================================================================== > RCS file: /OpenBSD/src/sys/arch/hppa/conf/RAMDISK,v > retrieving revision 1.111 > diff -u -p -r1.111 RAMDISK > --- sys/arch/hppa/conf/RAMDISK 20 Sep 2018 15:19:38 -0000 1.111 > +++ sys/arch/hppa/conf/RAMDISK 24 Dec 2018 19:41:12 -0000 > @@ -59,7 +59,7 @@ wax* at phantomas0 # Wax on [AB]* > wax* at uturn? # Wax on C* > mongoose* at mainbus0 irq 17 # EISA Bus Adapter (i82350 or TI???) > dino* at phantomas? # PCI bus bridge on [AB]* > -dino* at uturn0 # PCI bus bridge on [CJ]* > +dino* at uturn? # PCI bus bridge on [CJ]* > pci* at dino? > com1 at dino? irq 11 > > >