Problems installing on a recent (Kaby Lake) system

To: port-amd64%netbsd.org@localhost
Subject: Problems installing on a recent (Kaby Lake) system
From: Dave Huang <khym%azeotrope.org@localhost>
Date: Thu, 23 Mar 2017 15:00:44 -0500
Hi, I recently got a new system, a SuperMicro X11SSM-F motherboard
with a Pentium G4560 (Kaby Lake) CPU, and am having trouble getting
NetBSD installed. I have a monitor connected to the VGA port, and a
USB keyboard plugged in. The motherboard has pretty decent remote
management over IPMI, which I'm also using: it has serial console
redirection, where BIOS messages are also sent to the serial port. It
has serial over LAN, where one of the serial ports is accessible over
the network (which is what I'm using--all references to the serial
port below are serial over LAN). It has a network KVM where you can
get full graphics console access over the network. And it lets you put
an ISO CD image on an SMB share and mount it over the network (I don't
have a physical CD/DVD drive in the machine).

I first tried 7.1 and ran into some issues that I was able to work
around--main one was that Kaby Lake got rid of uhci/ehci and xhci is
the only USB controller. 7.1 doesn't have xhci enabled in the INSTALL
kernel, so no keyboard. I was able to use serial console, but then ran
into another issue, which maybe I could work around too, but since
xhci is a requirement, I decided to try -current. I might try more
with 7.1 later, but for now, I'll focus on the issues I had with
-current.

Booting CD Image
----------------
I first tried NetBSD-7.99.66-amd64.iso from the 20170322 nightly. I
mounted the ISO as a virtual CD and booted it in UEFI mode. My monitor
said that the display signal was out of its supported range, so I
connected the network KVM and and found that the display had been set
to 1600x1200 resolution, which my monitor doesn't support (1280x1024
max). The NetBSD boot block was running though and I was able to get
to the commandline:

> gop list
 0: 640x480 BGRR pitch 640 bpp 32
 1: 800x600 BGRR pitch 800 bpp 32
 2: 1024x768 BGRR pitch 1024 bpp 32
 3: 1280x1024 BGRR pitch 1280 bpp 32
*4: 1600x1200 BGRR pitch 1600 bpp 32

> text list
 0: 80x25
 1: 80x50
 2: 100x31
*3: 200x63

So, I'm guessing the NetBSD bootloader set the resolution to the
highest one available? I think it should avoid the higher resolutions
and stick with maybe 80x50 or 100x31 max. I did "text 2" and got a
good-looking display on the monitor (and the remote KVM too).

However, booting failed:

> boot
open netbsd: bad partition
boot: hd0a:netbsd: bad partition
open netbsd.gz: bad partition
boot: hd0a:netbsd.gz: bad partition

etc... apparently the bootloader doesn't see the virtual CD?

I then tried booting the virtual CD in BIOS compatibility mode. It
just displayed a blank screen (on both the monitor and remote KVM).
But I noticed that if I enabled the BIOS serial port redirection, I
got the boot menu over the serial port. While I don't really have any
hard evidence that this is a problem, I did notice that the BIOS sets
the video mode to something other than 80x25. Maybe NetBSD's BIOS boot
can't output to that?

Booting starts to load the kernel, but fails:

command(s): rndseed /var/db/entropy-file;boot netbsd
18185936+813132+1005492read section headers: Input/output error
boot: cd0a:netbsd: Input/output error
18185936+813132+1005492read section headers: Input/output error
boot: cd0a:netbsd: Input/output error

Incidentally, this is the basically the method I used to boot
NetBSD-7.1-amd64.iso, and it was able to load the kernel and boot
fine, but as I mentioned at the beginning of this message, 7.1 had
other issues. So I don't know why it's getting an Input/output error
with the -current ISO... I verified the SHA512 and it matches, so I
didn't get a bad download.

Booting UEFI USB image
------------------------
Next up, I wrote NetBSD-7.99.66-amd64-uefi-install.img to a USB flash
drive and booted from that. As with the EFI boot from CD, it came up
in the 1600x1200 video mode. I did "text 2" to change it to something
my monitor could handle and booted. It loaded the kernel and booted,
but the video was messed up (on both the monitor and remote KVM). See
http://imgur.com/wG2UVWt . If I set it to "text 1" or "text 0", the
bootloader displays OK, but the kernel's messages are even more messed
up: http://imgur.com/DwPPfMf

If I leave the video mode at 1600x1200, my monitor can't display it,
but the remote KVM can, and the display looks OK (see
http://imgur.com/WdwFLur). However, it can't find the root device:

boot device: <unknown>
root device:

The kernel did configure the boot USB flash drive as sd0, but the
keyboard doesn't work, so I can't tell it to try sd0. The kernel also
configured both the USB keyboard and network KVM keyboard.

Since the keyboard wasn't working, what about
NetBSD-7.99.66-amd64-uefi-install.img with serial console? I selected
the menu option to Drop to boot prompt and typed "consdev com1"
(serial console is on 0x2f8). However, that seemed to have no
effect... output was still displaying on the monitor, and nothing was
being displayed over the serial port. I did notice that if I type on
the serial console, I see what I typed on the monitor and interact
with the bootloader. This seems to be a result of the BIOS serial
console redirection though--that happens even if I don't do "consdev
com1". If I disable the BIOS serial console redirection, that no
longer happens. But "consdev com1" still doesn't do anything.

Booting BIOS USB image
------------------------
And finally, I tried NetBSD-7.99.66-amd64-install.img. Similarly to
booting the ISO in BIOS mode, it shows the boot menu on the redirected
serial console. And it has problems loading the kernel, though it
seems to be a different problem:

Option 1 will be chosen in 0 seconds.
18185936+813132+1005492 [1173288+805075|

And it hangs there with no spinning progress.

So, to summarize,

UEFI bootloader:
* Sets the video mode to 1600x1200, which is too high
* consdev doesn't work to change the console to the serial port
* Doesn't see the virtual CD drive

BIOS bootloader:
* Doesn't display anything on the monitor, but the redirected serial
  console works. Maybe the first thing it should do is make some INT
  call to reset the video mode to text 80x25?
* Seems to have trouble loading the -current kernel (but the 7.1 BIOS
  bootloader can load its kernel)

kernel:
* Keyboard doesn't work
* Doesn't display text properly if you change the video mode in the
  UEFI bootloader from the default
* Can't find root device, even when autoconf sees it

It seems that I actually got the furthest trying to boot the 7.1 ISO
image. I was able to use "consdev com1" to switch to serial console,
boot the kernel, and interact with it. It didn't recognize the virtual
CD though, so maybe I'll try copying the ISO to a USB flash drive.
Here's a dmesg from booting 7.1 (while I was able to get a -current
kernel to boot, without serial console, it's not practical to get all
the boot messages):

Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
    2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017
    The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
    The Regents of the University of California.  All rights reserved.

NetBSD 7.1 (GENERIC.201703111743Z)
total memory = 32589 MB
avail memory = 31626 MB
WARNING: module error: module `cd9660' pushed by boot loader already exists
kern.module.path=/stand/amd64/7.1/modules
mainbus0 (root)
ACPI: RSDP 0xf05b0 000024 (v02 SUPERM)
ACPI: XSDT 0x7d7be0a8 0000D4 (v01 SUPERM   SUPERM 01072009 AMI  00010013)
ACPI: FACP 0x7d7e0790 00010C (v05                 01072009 AMI  00010013)
ACPI: DSDT 0x7d7be218 022571 (v02 SUPERM SMCI--MB 01072009 INTL 20120913)
ACPI: FACS 0x7dd58f80 000040
ACPI: APIC 0x7d7e08a0 000084 (v03                 01072009 AMI  00010013)
ACPI: FPDT 0x7d7e0928 000044 (v01                 01072009 AMI  00010013)
ACPI: FIDT 0x7d7e0970 00009C (v01                 01072009 AMI  00010013)
ACPI: SPMI 0x7d7e0a10 000040 (v05 SUPERM SMCI--MB 00000000 AMI. 00000000)
ACPI: MCFG 0x7d7e0a50 00003C (v01 SUPERM SMCI--MB 01072009 MSFT 00000097)
ACPI: HPET 0x7d7e0a90 000038 (v01 SUPERM SMCI--MB 01072009 AMI. 0005000B)
ACPI: LPIT 0x7d7e0ac8 000094 (v01 INTEL      GNLR 00000000 MSFT 0000005F)
ACPI: SSDT 0x7d7e0b60 000248 (v02 INTEL  sensrhub 00000000 INTL 20120913)
ACPI: SSDT 0x7d7e0da8 002BAE (v02 INTEL  PtidDevc 00001000 INTL 20120913)
ACPI: SSDT 0x7d7e3958 000BE3 (v02 INTEL  Ther_Rvp 00001000 INTL 20120913)
ACPI: DBGP 0x7d7e4540 000034 (v01 INTEL           00000000 MSFT 0000005F)
ACPI: DBG2 0x7d7e4578 000054 (v00 INTEL           00000000 MSFT 0000005F)
ACPI: PRAD 0x7d7e45d0 0000CA (v02 PRADID  PRADTID 00000001 INTL 20120913)
ACPI: SSDT 0x7d7e46a0 00547E (v02 SaSsdt  SaSsdt  00003000 INTL 20120913)
ACPI: UEFI 0x7d7e9b20 000042 (v01                 00000000      00000000)
ACPI: SSDT 0x7d7e9b68 000E73 (v02 CpuRef  CpuSsdt 00003000 INTL 20120913)
ACPI: DMAR 0x7d7ea9e0 000070 (v01 INTEL      SKL  00000001 INTL 00000001)
ACPI: EINJ 0x7d7eaa50 000130 (v01    AMI AMI.EINJ 00000000 AMI. 00000000)
ACPI: ERST 0x7d7eab80 000230 (v01  AMIER AMI.ERST 00000000 AMI. 00000000)
ACPI: BERT 0x7d7eadb0 000030 (v01    AMI AMI.BERT 00000000 AMI. 00000000)
ACPI: HEST 0x7d7eade0 00027C (v01    AMI AMI.HEST 00000000 AMI. 00000000)
ACPI: All ACPI Tables successfully acquired
ioapic0 at mainbus0 apid 2
cpu0 at mainbus0 apid 0: Intel(R) Pentium(R) CPU G4560 @ 3.50GHz, id 0x906e9
cpu1 at mainbus0 apid 2: Intel(R) Pentium(R) CPU G4560 @ 3.50GHz, id 0x906e9
cpu2 at mainbus0 apid 1: Intel(R) Pentium(R) CPU G4560 @ 3.50GHz, id 0x906e9
cpu3 at mainbus0 apid 3: Intel(R) Pentium(R) CPU G4560 @ 3.50GHz, id 0x906e9
acpi0 at mainbus0: Intel ACPICA 20131218
mpacpi: PCI bus 5 int routing already done!
ACPI: SSDT 0x7d151c18 00037F (v02  PmRef  Cpu0Cst 00003001 INTL 20120913)
ACPI: SSDT 0x0 00037F (v02  PmRef  Cpu0Cst 00003001 INTL 20120913)
ACPI: SSDT 0x7d152798 0006E4 (v02  PmRef  Cpu0Ist 00003000 INTL 20120913)
ACPI: SSDT 0x0 0006E4 (v02  PmRef  Cpu0Ist 00003000 INTL 20120913)
ACPI: SSDT 0x7d151618 0005AA (v02  PmRef    ApIst 00003000 INTL 20120913)
ACPI: SSDT 0x0 0005AA (v02  PmRef    ApIst 00003000 INTL 20120913)
ACPI: SSDT 0x7d177c18 000119 (v02  PmRef    ApCst 00003000 INTL 20120913)
ACPI: SSDT 0x0 000119 (v02  PmRef    ApCst 00003000 INTL 20120913)
hpet0 at acpi0: high precision event timer (mem 0xfed00000-0xfed00400)
acpiec0 at acpi0 (H_EC, PNP0C09-1)
acpiec0: unable to evaluate _GPE: AE_NOT_FOUND
SIO1 (PNP0C02) at acpi0 not configured
UAR1 (PNP0501) at acpi0 not configured
UAR2 (PNP0501) at acpi0 not configured
FWHD (INT0800) at acpi0 not configured
LDRC (PNP0C02) at acpi0 not configured
LDR2 (PNP0C02) at acpi0 not configured
attimer1 at acpi0 (TIMR, PNP0100): io 0x40-0x43,0x50-0x53 irq 0
CWDT (INT3F0D) at acpi0 not configured
SPMI (IPI0001) at acpi0 not configured
PDRC (PNP0C02) at acpi0 not configured
IOTR (PNP0C02) at acpi0 not configured
EPC (INT0E0C) at acpi0 not configured
acpibut0 at acpi0 (SLPB, PNP0C0E): ACPI Sleep Button
acpibut1 at acpi0 (PWRB, PNP0C0C): ACPI Power Button
PMT1 (ACPI000D) at acpi0 not configured
PTID (INT340E) at acpi0 not configured
acpifan0 at acpi0 (FAN0, PNP0C0B-0): ACPI Fan
acpifan1 at acpi0 (FAN1, PNP0C0B-1): ACPI Fan
acpifan2 at acpi0 (FAN2, PNP0C0B-2): ACPI Fan
acpifan3 at acpi0 (FAN3, PNP0C0B-3): ACPI Fan
acpifan4 at acpi0 (FAN4, PNP0C0B-4): ACPI Fan
acpitz0 at acpi0 (TZ00)
acpitz0: active cooling level 0: 71.0C
acpitz0: active cooling level 1: 55.0C
acpitz0: active cooling level 2: 50.0C
acpitz0: active cooling level 3: 45.0C
acpitz0: active cooling level 4: 40.0C
acpitz1 at acpi0 (TZ01)
ACPI: Enabled 6 GPEs in block 00 to 7F
ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131218/hwxface-646)
ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131218/hwxface-646)
ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131218/hwxface-646)
ipmi0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1
pchb0 at pci0 dev 0 function 0: vendor 0x8086 product 0x590f (rev. 0x05)
vendor 0x8086 product 0xa135 (miscellaneous prehistoric, revision 0x31) at pci0 dev 19 function 0 not configured
vendor 0x8086 product 0xa12f (USB serial bus, xHCI, revision 0x31) at pci0 dev 20 function 0 not configured
vendor 0x8086 product 0xa131 (miscellaneous DASP, revision 0x31) at pci0 dev 20 function 2 not configured
vendor 0x8086 product 0xa13a (miscellaneous communications, revision 0x31) at pci0 dev 22 function 0 not configured
vendor 0x8086 product 0xa13b (miscellaneous communications, revision 0x31) at pci0 dev 22 function 1 not configured
ahcisata0 at pci0 dev 23 function 0: vendor 0x8086 product 0xa102 (rev. 0x31)
ahcisata0: interrupting at ioapic0 pin 16
ahcisata0: AHCI revision 1.31, 8 ports, 32 slots, CAP 0xe334ff47<EMS,PSC,SSC,PMD,SAM,ISS=0x3=Gen3,SCLO,SAL,SSNTF,SNCQ,S64A>
atabus0 at ahcisata0 channel 0
atabus1 at ahcisata0 channel 1
atabus2 at ahcisata0 channel 2
atabus3 at ahcisata0 channel 3
atabus4 at ahcisata0 channel 4
atabus5 at ahcisata0 channel 5
atabus6 at ahcisata0 channel 6
atabus7 at ahcisata0 channel 7
ppb0 at pci0 dev 28 function 0: vendor 0x8086 product 0xa110 (rev. 0xf1)
ppb0: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x4 @ 8.0GT/s
pci1 at ppb0 bus 1
ppb1 at pci0 dev 29 function 0: vendor 0x8086 product 0xa118 (rev. 0xf1)
ppb1: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x1 @ 8.0GT/s
ppb1: link is x1 @ 2.5GT/s
pci2 at ppb1 bus 2
wm0 at pci2 dev 0 function 0: I210-T1 Ethernet Server Adapter (rev. 0x03)
wm0: interrupting at ioapic0 pin 16
wm0: Ethernet address 0c:c4:7a:e2:02:a4
ukphy0 at wm0 phy 1: OUI 0x000ac2, model 0x0000, rev. 0
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
ppb2 at pci0 dev 29 function 1: vendor 0x8086 product 0xa119 (rev. 0xf1)
ppb2: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x1 @ 8.0GT/s
ppb2: link is x1 @ 2.5GT/s
pci3 at ppb2 bus 3
wm1 at pci3 dev 0 function 0: I210-T1 Ethernet Server Adapter (rev. 0x03)
wm1: interrupting at ioapic0 pin 17
wm1: Ethernet address 0c:c4:7a:e2:02:a5
ukphy1 at wm1 phy 1: OUI 0x000ac2, model 0x0000, rev. 0
ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
ppb3 at pci0 dev 29 function 2: vendor 0x8086 product 0xa11a (rev. 0xf1)
ppb3: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x1 @ 8.0GT/s
ppb3: link is x1 @ 2.5GT/s
pci4 at ppb3 bus 4
ppb4 at pci4 dev 0 function 0: vendor 0x1a03 product 0x1150 (rev. 0x03)
ppb4: PCI Express capability version 1 <PCI-E to PCI/PCI-X Bridge>
pci5 at ppb4 bus 5
genfb0 at pci5 dev 0 function 0: vendor 0x1a03 product 0x2000 (rev. 0x30)
pcib0 at pci0 dev 31 function 0: vendor 0x8086 product 0xa149 (rev. 0x31)
vendor 0x8086 product 0xa121 (miscellaneous memory, revision 0x31) at pci0 dev 31 function 2 not configured
ichsmb0 at pci0 dev 31 function 4: vendor 0x8086 product 0xa123 (rev. 0x31)
ichsmb0: interrupting at ioapic0 pin 16
iic0 at ichsmb0: I2C bus
isa0 at pcib0
com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
com1: console
pcppi0 at isa0 port 0x61
midi0 at pcppi0: PC speaker
sysbeep0 at pcppi0
attimer1: attached to pcppi0
acpicpu0 at cpu0: ACPI CPU
coretemp0 at cpu0: thermal sensor, 1 C resolution
acpicpu1 at cpu1: ACPI CPU
coretemp1 at cpu1: thermal sensor, 1 C resolution
acpicpu2 at cpu2: ACPI CPU
acpicpu3 at cpu3: ACPI CPU
ahcisata0 port 0: device present, speed: 6.0Gb/s
ahcisata0 port 3: device present, speed: 6.0Gb/s
ahcisata0 port 4: device present, speed: 6.0Gb/s
ahcisata0 port 5: device present, speed: 6.0Gb/s
ahcisata0 port 1: device present, speed: 6.0Gb/s
ahcisata0 port 2: device present, speed: 6.0Gb/s
wd0 at atabus0 drive 0
wd0: <WDC WD30EFRX-68EUZN0>
wd0: 2794 GB, 5814021 cyl, 16 head, 63 sec, 512 bytes/sect x 5860533168 sectors
dk0 at wd0: 6037cf84-0f97-11e7-a29c-0cc47ae202a4
dk0: 204800 blocks at 40, type: msdos
dk1 at wd0: 605832ae-0f97-11e7-a29c-0cc47ae202a4
dk1: 5860328288 blocks at 204840, type:
wd1 at atabus1 drive 0
wd1: <WDC WD30EFRX-68EUZN0>
wd1: 2794 GB, 5814021 cyl, 16 head, 63 sec, 512 bytes/sect x 5860533168 sectors
dk2 at wd1: c631a7a4-0d2b-11e7-a9cb-0cc47ae202a4
dk2: 4194304 blocks at 4096, type: swap
dk3 at wd1: c6531383-0d2b-11e7-a9cb-0cc47ae202a4
dk3: 5856333824 blocks at 4198400, type:
wd2 at atabus2 drive 0
wd2: <WDC WD30EFRX-68EUZN0>
wd2: 2794 GB, 5814021 cyl, 16 head, 63 sec, 512 bytes/sect x 5860533168 sectors
dk4 at wd2: c5fc531a-0d2b-11e7-a9cb-0cc47ae202a4
dk4: 4194304 blocks at 4096, type: swap
dk5 at wd2: c62287ab-0d2b-11e7-a9cb-0cc47ae202a4
dk5: 5856333824 blocks at 4198400, type:
wd3 at atabus3 drive 0
wd3: <WDC WD30EFRX-68EUZN0>
wd3: 2794 GB, 5814021 cyl, 16 head, 63 sec, 512 bytes/sect x 5860533168 sectors
dk6 at wd3: c9667c86-0d2b-11e7-a9cb-0cc47ae202a4
dk6: 4194304 blocks at 4096, type: swap
dk7 at wd3: c98732e1-0d2b-11e7-a9cb-0cc47ae202a4
dk7: 5856333824 blocks at 4198400, type:
wd4 at atabus4 drive 0
wd4: <WDC WD30EFRX-68EUZN0>
wd4: 2794 GB, 5814021 cyl, 16 head, 63 sec, 512 bytes/sect x 5860533168 sectors
dk8 at wd4: c903984d-0d2b-11e7-a9cb-0cc47ae202a4
dk8: 4194304 blocks at 4096, type: swap
dk9 at wd4: c92b5073-0d2b-11e7-a9cb-0cc47ae202a4
dk9: 5856333824 blocks at 4198400, type:
wd5 at atabus5 drive 0
wd5: <WDC WD30EFRX-68EUZN0>
wd5: 2794 GB, 5814021 cyl, 16 head, 63 sec, 512 bytes/sect x 5860533168 sectors
dk10 at wd5: c78b37a4-0d2b-11e7-a9cb-0cc47ae202a4
dk10: 4194304 blocks at 4096, type: swap
dk11 at wd5: c7b7c3bf-0d2b-11e7-a9cb-0cc47ae202a4
dk11: 5856333824 blocks at 4198400, type:
pad0: outputs: 44100Hz, 16-bit, stereo
audio0 at pad0: half duplex, playback, capture
boot device: <unknown>
root device:

-- 
Name: Dave Huang         |  Mammal, mammal / their names are called /
INet: khym%azeotrope.org@localhost |  they raise a paw / the bat, the cat /
FurryMUCK: Dahan         |  dolphin and dog / koala bear and hog -- TMBG
Dahan: Hani G Y+C 41 Y++ L+++ W- C++ T++ A+ E+ S++ V++ F- Q+++ P+ B+ PA+ PL++
Follow-Ups:
- Re: Problems installing on a recent (Kaby Lake) system
  - From: Dave Huang
Prev by Date: Re: Intel 100 series chipset (Skylake / Sunrise Point)
Next by Date: Re: Problems installing on a recent (Kaby Lake) system
Previous by Thread: AMD64 won't boot on certain mainboards since beginning of V7
Next by Thread: Re: Problems installing on a recent (Kaby Lake) system
Indexes:
Home | Main Index | Thread Index | Old Index