Re: No console output on 5.4-Current
On 2013-10-10, Bryan Chapman br...@honeypoocakes.net wrote: The only thing I see in /var/log/messages was on the end of the dmesg I posted: Oct 10 03:28:21 mystic /bsd: drm: initializing kernel modesetting (PITCAIRN 0x1002:0x6819 0x174B:0xE221). Oct 10 03:28:21 mystic /bsd: radeondrm0: VRAM: 2048M 0x - 0x7FFF (2048M used) Oct 10 03:28:21 mystic /bsd: radeondrm0: GTT: 512M 0x8000 - 0x9FFF Oct 10 03:28:21 mystic /bsd: ttm_pool_mm_shrink_init stub Oct 10 03:28:21 mystic /bsd: error: [drm:pid0:si_init_microcode] *ERROR* si_cp: Failed to load firmware radeon-pitcairn_pfp Oct 10 03:28:21 mystic /bsd: error: [drm:pid0:si_startup] *ERROR* Failed to load firmware! Oct 10 03:28:21 mystic /bsd: error: [drm:pid0:si_init] *ERROR* disabling GPU acceleration Oct 10 03:28:21 mystic /bsd: error: [drm:pid0:radeon_bo_unpin] *ERROR* 0xfe81b6de32b0 unpin not necessary Oct 10 03:28:21 mystic /bsd: error: [drm:pid0:radeon_bo_unpin] *ERROR* 0xfe81b6de32b0 unpin not necessary Oct 10 03:28:21 mystic /bsd: error: [drm:pid0:si_init] *ERROR* radeon: MC ucode required for NI+. Oct 10 03:28:21 mystic /bsd: : Fatal error during GPU init Oct 10 03:28:21 mystic /bsd: radeon_hwmon_fini stub Oct 10 03:28:21 mystic /bsd: drm: radeon: finishing device. Oct 10 03:28:21 mystic /bsd: Finalizing pool allocator Oct 10 03:28:21 mystic /bsd: ttm_pool_mm_shrink_fini stub Oct 10 03:28:21 mystic /bsd: drm: Zone kernel: Used memory at exit: 0 kiB Oct 10 03:28:21 mystic /bsd: drm: Zone dma32: Used memory at exit: 0 kiB Oct 10 03:28:21 mystic /bsd: drm: radeon: ttm finalized Oct 10 03:28:21 mystic /bsd: drm0 detached Oct 10 03:28:21 mystic /bsd: radeondrm0 detached Oct 10 03:28:21 mystic /bsd: vga1 at pci1 dev 0 function 0 ATI Radeon HD 7850 rev 0x00 Oct 10 03:28:21 mystic /bsd: wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation), using wskbd0 Oct 10 03:28:21 mystic /bsd: wskbd1: connecting to wsdisplay0 Oct 10 03:28:21 mystic /bsd: wsdisplay0: screen 1-5 added (80x25, vt100 emulation) Is there another place to look or debug to turn on? -Bryan You should get more information from a kernel built with 'option DRMDEBUG'.
Re: No console output on 5.4-Current
On Fri, Oct 11, 2013 at 09:32:13AM +, Stuart Henderson wrote: On 2013-10-10, Bryan Chapman br...@honeypoocakes.net wrote: The only thing I see in /var/log/messages was on the end of the dmesg I posted: Oct 10 03:28:21 mystic /bsd: drm: initializing kernel modesetting (PITCAIRN 0x1002:0x6819 0x174B:0xE221). Oct 10 03:28:21 mystic /bsd: radeondrm0: VRAM: 2048M 0x - 0x7FFF (2048M used) Oct 10 03:28:21 mystic /bsd: radeondrm0: GTT: 512M 0x8000 - 0x9FFF Oct 10 03:28:21 mystic /bsd: ttm_pool_mm_shrink_init stub Oct 10 03:28:21 mystic /bsd: error: [drm:pid0:si_init_microcode] *ERROR* si_cp: Failed to load firmware radeon-pitcairn_pfp Oct 10 03:28:21 mystic /bsd: error: [drm:pid0:si_startup] *ERROR* Failed to load firmware! Oct 10 03:28:21 mystic /bsd: error: [drm:pid0:si_init] *ERROR* disabling GPU acceleration Oct 10 03:28:21 mystic /bsd: error: [drm:pid0:radeon_bo_unpin] *ERROR* 0xfe81b6de32b0 unpin not necessary Oct 10 03:28:21 mystic /bsd: error: [drm:pid0:radeon_bo_unpin] *ERROR* 0xfe81b6de32b0 unpin not necessary Oct 10 03:28:21 mystic /bsd: error: [drm:pid0:si_init] *ERROR* radeon: MC ucode required for NI+. Oct 10 03:28:21 mystic /bsd: : Fatal error during GPU init Oct 10 03:28:21 mystic /bsd: radeon_hwmon_fini stub Oct 10 03:28:21 mystic /bsd: drm: radeon: finishing device. Oct 10 03:28:21 mystic /bsd: Finalizing pool allocator Oct 10 03:28:21 mystic /bsd: ttm_pool_mm_shrink_fini stub Oct 10 03:28:21 mystic /bsd: drm: Zone kernel: Used memory at exit: 0 kiB Oct 10 03:28:21 mystic /bsd: drm: Zone dma32: Used memory at exit: 0 kiB Oct 10 03:28:21 mystic /bsd: drm: radeon: ttm finalized Oct 10 03:28:21 mystic /bsd: drm0 detached Oct 10 03:28:21 mystic /bsd: radeondrm0 detached Oct 10 03:28:21 mystic /bsd: vga1 at pci1 dev 0 function 0 ATI Radeon HD 7850 rev 0x00 Oct 10 03:28:21 mystic /bsd: wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation), using wskbd0 Oct 10 03:28:21 mystic /bsd: wskbd1: connecting to wsdisplay0 Oct 10 03:28:21 mystic /bsd: wsdisplay0: screen 1-5 added (80x25, vt100 emulation) Is there another place to look or debug to turn on? -Bryan You should get more information from a kernel built with 'option DRMDEBUG'. In this case just install the firmware and reboot, DRMDEBUG isn't going to help and is overly verbose unless a few things are turned off. There is no 2d or 3d acceleration with radeonsi parts like pitcairn however because it requires a version of EGL with the drm/gbm platform instead of the x11 platform, the glamor library and a version of mesa compiled with llvm as the mesa radeonsi driver has a hard dep on llvm. I attempted to provide alternative paths to the linux only udev code in libgbm and co but didn't end up with a useable X session when testing glamor on a northern islands card. AMD don't support the usual xorg type acceleration for radeonsi, only glamor. And sadly it seems the mesa/3d driver is unuseable without glamor as well...
Re: No console output on 5.4-Current
Am Wed, 09 Oct 2013 17:36:22 -0400 schrieb Bryan Chapman br...@honeypoocakes.net: Just installed the Oct 3rd snapshot on my desktop. During the boot process it loses console output and just shows a blank screen. The screen doesn't go into power saving - just no output. At first I though the machine froze, but it continued running and I was able to SSH into the machine. Here is the DMESG. Looks like some issues with DRM. At a bit of a loss on the next troubleshooting steps, any ideas? -Bryan [...] Have you tried this? pkg_add http://firmware.openbsd.org/firmware/snapshots/radeondrm-firmware-20131002.tgz http://www.openbsd.org/faq/current.html#20130812 Ulrich
Re: No console output on 5.4-Current
On Wed, Oct 09, 2013 at 05:36:22PM -0400, Bryan Chapman wrote: Just installed the Oct 3rd snapshot on my desktop. During the boot process it loses console output and just shows a blank screen. The screen doesn't go into power saving - just no output. At first I though the machine froze, but it continued running and I was able to SSH into the machine. Here is the DMESG. Looks like some issues with DRM. At a bit of a loss on the next troubleshooting steps, any ideas? Exact same issue here... drm effect. boot -c disable radeondrm then install the firmware manually (firmware-update will not see it unfortunately). Then reboot. If your machine has network, jsg would probably be happy to see what's going on in /var/log/messages while the machine loses boot...
Re: No console output on 5.4-Current
On 10/10/13 05:34, Marc Espie wrote: On Wed, Oct 09, 2013 at 05:36:22PM -0400, Bryan Chapman wrote: Just installed the Oct 3rd snapshot on my desktop. During the boot process it loses console output and just shows a blank screen. The screen doesn't go into power saving - just no output. At first I though the machine froze, but it continued running and I was able to SSH into the machine. Here is the DMESG. Looks like some issues with DRM. At a bit of a loss on the next troubleshooting steps, any ideas? Exact same issue here... drm effect. boot -c disable radeondrm then install the firmware manually (firmware-update will not see it unfortunately). Then reboot. If your machine has network, jsg would probably be happy to see what's going on in /var/log/messages while the machine loses boot... Thanks -- installing the firmware package resolved the issue. I just assumed that the firmware updater would grab it if needed. -Bryan
Re: No console output on 5.4-Current
On Thu, Oct 10, 2013 at 1:38 PM, Bryan Chapman br...@honeypoocakes.net wrote: Thanks -- installing the firmware package resolved the issue. I just assumed that the firmware updater would grab it if needed. Indeed, fw_update needs to be fixed
Re: No console output on 5.4-Current
On Thu, Oct 10, 2013 at 07:38:56AM -0400, Bryan Chapman wrote: On 10/10/13 05:34, Marc Espie wrote: On Wed, Oct 09, 2013 at 05:36:22PM -0400, Bryan Chapman wrote: Just installed the Oct 3rd snapshot on my desktop. During the boot process it loses console output and just shows a blank screen. The screen doesn't go into power saving - just no output. At first I though the machine froze, but it continued running and I was able to SSH into the machine. Here is the DMESG. Looks like some issues with DRM. At a bit of a loss on the next troubleshooting steps, any ideas? Exact same issue here... drm effect. boot -c disable radeondrm then install the firmware manually (firmware-update will not see it unfortunately). Then reboot. If your machine has network, jsg would probably be happy to see what's going on in /var/log/messages while the machine loses boot... Thanks -- installing the firmware package resolved the issue. I just assumed that the firmware updater would grab it if needed. According to jsg@, the KMS code is able to figure out that the firmware is needed, and not do the video change if it's not installed. Obviously, that still fails from some cards: the KMS code doesn't get an error, and the video change still occur. So a log of what the kernel says when it's switching while not having the firmware would be useful for trying to fix that...
Re: No console output on 5.4-Current
On Thu, Oct 10, 2013 at 02:27:28PM +0200, David Coppa wrote: On Thu, Oct 10, 2013 at 1:38 PM, Bryan Chapman br...@honeypoocakes.net wrote: Thanks -- installing the firmware package resolved the issue. I just assumed that the firmware updater would grab it if needed. Indeed, fw_update needs to be fixed No, that's not the iusse. fw_update does its job: it updates firmwares it's aware of. Once you disable radeondrm in the kernel, it no longer sees it. The issue is the KMS code attempting to switch modes while there's no radeon firmware around on a card where it shouldn't do that.
Re: No console output on 5.4-Current
On Thu, Oct 10, 2013 at 6:24 PM, Marc Espie es...@nerim.net wrote: On Thu, Oct 10, 2013 at 02:27:28PM +0200, David Coppa wrote: On Thu, Oct 10, 2013 at 1:38 PM, Bryan Chapman br...@honeypoocakes.net wrote: Thanks -- installing the firmware package resolved the issue. I just assumed that the firmware updater would grab it if needed. Indeed, fw_update needs to be fixed No, that's not the iusse. fw_update does its job: it updates firmwares it's aware of. You're right: fw_update already knows about radeondrm. My bad for speaking before checking.
Re: No console output on 5.4-Current
On 10/10/13 12:23, Marc Espie wrote: On Thu, Oct 10, 2013 at 07:38:56AM -0400, Bryan Chapman wrote: On 10/10/13 05:34, Marc Espie wrote: On Wed, Oct 09, 2013 at 05:36:22PM -0400, Bryan Chapman wrote: Just installed the Oct 3rd snapshot on my desktop. During the boot process it loses console output and just shows a blank screen. The screen doesn't go into power saving - just no output. At first I though the machine froze, but it continued running and I was able to SSH into the machine. Here is the DMESG. Looks like some issues with DRM. At a bit of a loss on the next troubleshooting steps, any ideas? Exact same issue here... drm effect. boot -c disable radeondrm then install the firmware manually (firmware-update will not see it unfortunately). Then reboot. If your machine has network, jsg would probably be happy to see what's going on in /var/log/messages while the machine loses boot... Thanks -- installing the firmware package resolved the issue. I just assumed that the firmware updater would grab it if needed. According to jsg@, the KMS code is able to figure out that the firmware is needed, and not do the video change if it's not installed. Obviously, that still fails from some cards: the KMS code doesn't get an error, and the video change still occur. So a log of what the kernel says when it's switching while not having the firmware would be useful for trying to fix that... The only thing I see in /var/log/messages was on the end of the dmesg I posted: Oct 10 03:28:21 mystic /bsd: drm: initializing kernel modesetting (PITCAIRN 0x1002:0x6819 0x174B:0xE221). Oct 10 03:28:21 mystic /bsd: radeondrm0: VRAM: 2048M 0x - 0x7FFF (2048M used) Oct 10 03:28:21 mystic /bsd: radeondrm0: GTT: 512M 0x8000 - 0x9FFF Oct 10 03:28:21 mystic /bsd: ttm_pool_mm_shrink_init stub Oct 10 03:28:21 mystic /bsd: error: [drm:pid0:si_init_microcode] *ERROR* si_cp: Failed to load firmware radeon-pitcairn_pfp Oct 10 03:28:21 mystic /bsd: error: [drm:pid0:si_startup] *ERROR* Failed to load firmware! Oct 10 03:28:21 mystic /bsd: error: [drm:pid0:si_init] *ERROR* disabling GPU acceleration Oct 10 03:28:21 mystic /bsd: error: [drm:pid0:radeon_bo_unpin] *ERROR* 0xfe81b6de32b0 unpin not necessary Oct 10 03:28:21 mystic /bsd: error: [drm:pid0:radeon_bo_unpin] *ERROR* 0xfe81b6de32b0 unpin not necessary Oct 10 03:28:21 mystic /bsd: error: [drm:pid0:si_init] *ERROR* radeon: MC ucode required for NI+. Oct 10 03:28:21 mystic /bsd: : Fatal error during GPU init Oct 10 03:28:21 mystic /bsd: radeon_hwmon_fini stub Oct 10 03:28:21 mystic /bsd: drm: radeon: finishing device. Oct 10 03:28:21 mystic /bsd: Finalizing pool allocator Oct 10 03:28:21 mystic /bsd: ttm_pool_mm_shrink_fini stub Oct 10 03:28:21 mystic /bsd: drm: Zone kernel: Used memory at exit: 0 kiB Oct 10 03:28:21 mystic /bsd: drm: Zone dma32: Used memory at exit: 0 kiB Oct 10 03:28:21 mystic /bsd: drm: radeon: ttm finalized Oct 10 03:28:21 mystic /bsd: drm0 detached Oct 10 03:28:21 mystic /bsd: radeondrm0 detached Oct 10 03:28:21 mystic /bsd: vga1 at pci1 dev 0 function 0 ATI Radeon HD 7850 rev 0x00 Oct 10 03:28:21 mystic /bsd: wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation), using wskbd0 Oct 10 03:28:21 mystic /bsd: wskbd1: connecting to wsdisplay0 Oct 10 03:28:21 mystic /bsd: wsdisplay0: screen 1-5 added (80x25, vt100 emulation) Is there another place to look or debug to turn on? -Bryan
Re: No console output on 5.4-Current
Bryan Chapman [br...@honeypoocakes.net] wrote: Oct 10 03:28:21 mystic /bsd: error: [drm:pid0:si_init_microcode] *ERROR* si_cp: Failed to load firmware radeon-pitcairn_pfp Oct 10 03:28:21 mystic /bsd: error: [drm:pid0:si_startup] *ERROR* Failed to load firmware! Is there another place to look or debug to turn on? Maybe you need a file in /etc/firmware/radeon-pitcairn_pfp with a valid firmware image?
