On 09/13/17 02:21, Jan Stary wrote:
> On Sep 12 21:48:04, n...@holland-consulting.net wrote:
>> On 09/12/17 14:16, Jan Stary wrote:
>> > On Sep 12 19:29:16, h...@stare.cz wrote:
>> >> This is current/i386 from https://ftp.eu.openbsd.org/pub/OpenBSD
>> >> The upgrade went just fine as always, but the installed /bsd
>> >> just goes to a black screen at some point during the boot sequence;
>> >> the machine does not answer to a ping.
>> > 
>> > Ech, it's an amd64 machine. Sorry for the noise.
>> > 
>> >> Here is a previous dmesg on the same machine:
>> >> http://stare.cz/dmesg/intel-i7.20170827
>> > 
>> > And here is the amd64 dmesg.
>> > http://stare.cz/dmesg/intel-i7.20170911
>> > 
>> > 
>> > To get a lesson out of this screwup: why exactly is it
>> > that an i386 bsd.rd boots at this but an i386 bsd does not?
>> 
>> well...  short answer is the kernels are different.
>> bsd.rd is smaller than the full kernel, AND has "built in"
>> utilities...so there's a lot missing from bsd.rd.
>> 
>> "Blank screen" sounds to me like drm issue.  At the "boot>" prompt, you
>> could try a "boot -c" then "disable inteldrm" at the ukc prompt.  If it
>> comes up, sounds like an unhappy regression from something that worked a
>> couple weeks ago.  (I see your working dmesg has inteldrm handling the
>> display).
>> 
>> However, before I say bug, I'm confused...you keep talking about i386
>> not booting, but it's amd64 that you have shown as having worked.  So
>> I'm a little confused here.  What's the actual problem?
>> 
>> old amd64 worked, new amd64 doesn't?
>> old amd64 worked, new i386 doesn't?
>> 
>> Is there any possibilities you got i386 and amd64 binaries mixed, maybe
>> kernel i386 and amd64 X or other way around, such as by changing
>> platforms by "upgrade"?  (WRONG! re-install).
> 
> It's an amd64 machine where current/amd64 has always worked.
> The dmesg are at http://stare.cz/dmesg/intel-i7.*
> 
> Yesterday, I "upgraded" the machine to current/i386.
> That's where I observed that bsd.rd boots but bsd does not.
> It was an i386 bsd.rd that booted and an i386 bsd that did not.
> 
> After ealizing this, I upgraded again, this time to current/amd64
> - which works fine, like it always has.
> 
> I believe you are right about the inteldrm. Usually, the boot sequence
> switches to a smaller font once it gets to graphics. After the i386 upgrade,
> it stayed 80x25 before it went black. That's hardly a bug report of course.

Ok...if you "upgraded" i386 over amd64...all bets off.  Too much can go
wrong there.  And in this case, the reason bsd.rd worked and the regular
kernel doesn't /could/ be because the bsd.rd kernel is completely
self-contained -- all tools are in the kernel.  The regular kernel uses
stuff on the disk, if it pulled in an amd64 program on an i386
kernel...well, unhappy things are expected.

Now, if you did a fresh install of i386, then there might be an issue.
Or it could be that it's never worked and no one ever tested before.

Nick.

Reply via email to