Nope, this is also needed ahead of time
# cd /usr/src/sys
# make obj
otherwise, sys/stand and sys/lib don't have obj@ subtrees, and the
later compile will reach into the wrong places.
Experienced developers can forget about this because they always have
obj subtrees...
> # cd
If you say that 6.7 works, then the changes in the logs to look at are
the following.
It isn't that many diffs, see below.
Compiling the bootblocks is not hard
cd /usr/src
make obj # YES FROM THE TOP OF THE TREE
cd sys/arch/sparc64/stand
make
> Date: Sat, 13 Nov 2021 15:45:19 -0700
> From: Ted Bullock
>
> On 2021-11-04 4:04 p.m., Ted Bullock wrote:
> > On 2021-11-02 5:36 p.m., Ted Bullock wrote:
> >> Reporting an issue that is causing my SunBlade 100 (ultrasparc64)
> >> workstation to be unable too boot.
> >
> > I've identified
On 2021-11-04 4:04 p.m., Ted Bullock wrote:
On 2021-11-02 5:36 p.m., Ted Bullock wrote:
Reporting an issue that is causing my SunBlade 100 (ultrasparc64)
workstation to be unable too boot.
I've identified the malfunctioning component that is causing installs
after 6.7 to fail for this
Did the vm previously have a fdc? I doubt it. I am surprised fdcprobe()
returns a success.
Klemens Nanni wrote:
> Just upgraded a standard test install in vmm(4) to the latest snap and
> noticed new and garbled output:
>
> fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
> intr_establish:
Just upgraded a standard test install in vmm(4) to the latest snap and
noticed new and garbled output:
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
intr_establish: pic pic0 pin 6: can't share type 3 with 2
com0 at isa0 port 0x3f8/8 irq 4: ns8250, no fifo
...
On Mon, Nov 01, 2021 at 06:53:38PM +0100, Matthieu Herrb wrote:
> On Mon, Nov 01, 2021 at 12:30:19PM +0100, Landry Breuil wrote:
> > Le Mon, Nov 01, 2021 at 12:15:01PM +0100, Matthieu Herrb a écrit :
> > >
> > > The problem I see with this approach is that it provides a tool that
> > > make it
