Re: install/57542: NetBSD shuts down during installation on Intel Atom Baytrail Notebook with 32-bit EFI

[Werner Lehmann <lehmannwer%gmail.com@localhost>]

The following reply was made to PR install/57542; it has been noted by GNATS.

From: Werner Lehmann <lehmannwer%gmail.com@localhost>
To: RVP <rvp%SDF.ORG@localhost>
Cc: gnats-bugs%netbsd.org@localhost, martin%duskware.de@localhost
Subject: Re: install/57542: NetBSD shuts down during installation on Intel
 Atom Baytrail Notebook with 32-bit EFI
Date: Sun, 30 Jul 2023 18:55:45 +0200

 > Going by the Linux kernel messages you seem to have an RTL-8723BS
 > WiFi-BT wireless NIC. There's no driver for this even in NetBSD-HEAD.
 > And, since you don't appear to have any other ethernet device, I
 > would suggest that you buy a USB wireless adapter. Please ask on
 > the netbsd-users list for recommendations.
 What about the possibility of tethering an Android smartphone in order 
 to connect to the internet? Is that possible on NetBSD?
 
 > There appears to a driver (es8316ac) for the  `Everest Semi ES8316
 > LowPower Audio CODEC' corresponding to this (bytcht-es8316) sound
 > device on Linux, but it looks like an ARM-specific driver.
 >
 > For the battery issue too, there seems to be a compatible driver
 > present, but, again, this too seems ARM-only. I don't think either
 > of them will compile into an x86 kernel.
 >
 > So, for audio also, you'll have to invest in a USB device. 
 I don't quite understand: Why do the two drivers "look like 
 ARM-scecific" or "ARM-only" when we are talking about a Fedora x86_64 
 installation?
 
 > Please check the disk media too. You should not be seeing these
 > sorts of write errors on the drive:
 >
 > ```
 > [Â Â Â  15.904213] sdhc0: data crc error
 > [Â Â Â  15.917638] ld0d: error writing fsbn 6699648 of 6699648-6699775 
 > (ld0 bn 6699648; cn 830 tn 103 sn 39), retrying
 > [Â Â Â  15.924225] sdhc0: data crc error
 > [Â Â Â  15.939053] ld0d: error writing fsbn 6700256 of 6700256-6700383 
 > (ld0 bn 6700256; cn 830 tn 113 sn 17), retrying
 > [Â Â Â  15.939053] sdhc0: data crc error
 > [Â Â Â  15.953230] ld0d: error writing fsbn 6700416 of 6700416-6700543 
 > (ld0 bn 6700416; cn 830 tn 115 sn 51), retrying
 > [Â Â Â  15.954246] sdhc0: data crc error
 > ``` 
 Which "disk media" do you mean? The installation media (usb-stick) or 
 the internal SD card of the Notebook?
 
 Thanks.
 
 Werner
 
 
 On 7/28/23 09:46, RVP wrote:
 > On Thu, 27 Jul 2023, Werner Lehmann wrote:
 >
 >>> Â ```
 >>> Â dmesg > /var/log/dmesg.tx
 >>
 >> I was not able to do this,
 >>
 >
 > That's fine, there are easier ways to get a dmesg if needed, but,
 > I don't think it is now (see below)...
 >
 >> The network device is not recognized,
 >>
 >
 > Going by the Linux kernel messages you seem to have an RTL-8723BS
 > WiFi-BT wireless NIC. There's no driver for this even in NetBSD-HEAD.
 > And, since you don't appear to have any other ethernet device, I
 > would suggest that you buy a USB wireless adapter. Please ask on
 > the netbsd-users list for recommendations.
 >
 >> I think the sound device is not recognized either.
 >>
 >
 > There appears to a driver (es8316ac) for the  `Everest Semi ES8316
 > LowPower Audio CODEC' corresponding to this (bytcht-es8316) sound
 > device on Linux, but it looks like an ARM-specific driver.
 >
 > For the battery issue too, there seems to be a compatible driver
 > present, but, again, this too seems ARM-only. I don't think either
 > of them will compile into an x86 kernel.
 >
 > So, for audio also, you'll have to invest in a USB device.
 >
 >> X is not really usable,
 >>
 >
 > There are a couple of way to "fix" those artifacts in 9.3
 >
 > 1. Run a compositor (as suggested in the "Graphics" section here:
 > https://wiki.netbsd.org/laptops/)
 >
 > 2. Try these settings with the "intel" Xorg display-driver:
 >
 > ```
 > $ cat /etc/X11/xorg.conf.d/intel.conf
 > Section "Device"
 >     Identifier  "Card0"
 >     Driver      "intel"
 >     Option      "AccelMethod"       "UXA"
 >     # Option      "AccelMethod"     "blt"
 >
 >     # Option    "TearFree"          "on"
 >     # Option    "VSync"             "on"
 >     # Option    "PageFlip"          "on"
 >     # Option    "SwapbuffersWait"   "on"
 >     # Option    "TripleBuffer"      "on"
 >     # Option    "DRI"               "off"
 >
 >     # Option    "LinearFramebuffer" "on"
 >     # Option    "ReprobeOutputs"    "on"
 > EndSection
 > $
 > ```
 >
 > Choose either "UXA" or "blt", then uncomment the other lines
 > one-by-one to see which works best.
 >
 > You should also:
 >
 > a) see if there is a BIOS update
 > b) try the latest -HEAD image
 >
 > to see if this issue will go away:
 >
 > ```
 > [Â Â Â Â  1.000003] acpi0: autoconfiguration error: failed to evaluate 
 > _PRW for BRCM: AE_BAD_PARAMETER
 > [Â Â Â Â  1.000003] acpi0: autoconfiguration error: failed to evaluate 
 > _PRW for WLAN: AE_BAD_PARAMETER
 > [Â Â Â Â  1.000003] acpi0: autoconfiguration error: failed to evaluate 
 > _PRW for RTLW: AE_BAD_PARAMETER
 > [Â Â Â Â  1.000003] acpi0: autoconfiguration error: failed to evaluate 
 > _PRW for LID: AE_BAD_PARAMETER
 > ```
 >
 > Please check the disk media too. You should not be seeing these
 > sorts of write errors on the drive:
 >
 > ```
 > [Â Â Â  15.904213] sdhc0: data crc error
 > [Â Â Â  15.917638] ld0d: error writing fsbn 6699648 of 6699648-6699775 
 > (ld0 bn 6699648; cn 830 tn 103 sn 39), retrying
 > [Â Â Â  15.924225] sdhc0: data crc error
 > [Â Â Â  15.939053] ld0d: error writing fsbn 6700256 of 6700256-6700383 
 > (ld0 bn 6700256; cn 830 tn 113 sn 17), retrying
 > [Â Â Â  15.939053] sdhc0: data crc error
 > [Â Â Â  15.953230] ld0d: error writing fsbn 6700416 of 6700416-6700543 
 > (ld0 bn 6700416; cn 830 tn 115 sn 51), retrying
 > [Â Â Â  15.954246] sdhc0: data crc error
 > ```
 >
 > -RVP