On 5/7/2016 10:34 AM, Chuck Zmudzinski wrote:
Actually I found out that the system is not crashing at all. After setting up networking and sshd with my custom GENERIC 7.0/amd64 kernel with the i915drmkms support disabled, I tested the 7.0/amd64 GENERIC kernel again and even though the console screen powered off and I could not get it to power on by pressing a key on the keyboard, I could access the system remotely using ssh. So it is not really a system crash at all even though that is how it appeared at the console before I had sshd configured for remote access. I also tried a recent -current kernel with the 7.0 userland and got the same behavior, a blank screen at the console but able to sshd remotely over the network.On 5/7/2016 9:37 AM, coypu%SDF.ORG@localhost wrote:I will try -current and maybe some other things and report my findings probably by early next week when I have time...On Fri, May 06, 2016 at 10:42:29PM -0400, Chuck Zmudzinski wrote:Hello friends... I have a system with ASROCK B85M Pro4 Board and Intel Core i5-4590Sprocessor which has Intel HD 4600 integrated graphics. I thought I would try booting NetBSD/amd64 7.0 on it, since I read on the web that NetBSD plans tosupport Intel integrated graphics up to Haswell in NetBSD 7.0. It crashed using the GENERIC kernel a few seconds after the bootloaderloaded the kernel. On the console screen I could see that the i915drmkmsdriver crashed the system and the screen immediately went blank at that time.To get this system to boot I built a GENERIC kernel without the i915drmkmsoption, and used it to install and run on the system, and when runningstartx the system crashes immediately with the screen going blank. I thought maybe it would at least run X11 with the generic VESA driver. But it totally crashed the system. Obviously the support for Intel integrated graphics on the Haswell microarchitcture is hit and miss and NetBSD 7.0 does not supportall configurations. I also tried the legacy i915drm driver without kms which by default is disabled in the GENERIC kernel config, but that kernel config would not build without compilation errors.Any ideas of what to try? NetBSD/i386 7.0? or NetBSD current? Tweak some BIOS settings such as amount of shared videoram (mine was set to 256 MB)?Thanks Chuck --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirusTry -current, at least. You can get an image from nyftp.netbsd.org, no need to build your own. Feel free to file a bug report, especially if -current fails too: http://netbsd.org/cgi-bin/sendpr.cgi?gndb=netbsd
With a little more experimenting I found out that the screen goes blank with the i915drmkms support enabled only with an HDMI cable connected to the display. When using a VGA cable, the screen does not go blank even with the i915drmkms support enabled and I can login at the console after the booting process completes and I can run startx and the system works as expected.
Is there any reason NetBSD 7.0/amd64 cannot output to a display connected with an HDMI cable but can output to the same display connected with a VGA cable?
Although the i915drmkms support in NetBSD 7.0/amd64 does seem to work on my system with a VGA cable, it is not without errors. On the console after ending the X11 session there is an error reported nine times, (also reported by dmesg):
DRM error in intel_uncore_check_errors: Unclaimed register before interrupt DRM error in intel_uncore_check_errors: Unclaimed register before interrupt DRM error in intel_uncore_check_errors: Unclaimed register before interrupt DRM error in intel_uncore_check_errors: Unclaimed register before interrupt DRM error in intel_uncore_check_errors: Unclaimed register before interrupt DRM error in intel_uncore_check_errors: Unclaimed register before interrupt DRM error in intel_uncore_check_errors: Unclaimed register before interrupt DRM error in intel_uncore_check_errors: Unclaimed register before interrupt DRM error in intel_uncore_check_errors: Unclaimed register before interrupt Chuck --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus