Bug 1321886

Summary: RFE: ARM disk images do not work for cubox-i
Product: [Fedora] Fedora Reporter: billiboy
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab, pbrobinson
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-29 14:33:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
serial.log
none
config-local
none
dmesg.log
none
Xorg.0.log none

Description billiboy 2016-03-29 10:13:49 UTC 
Created attachment 1141184 [details]
serial.log

Description of problem:

RFE: ARM disk images do not work for cubox-i

Version-Release number of selected component (if applicable):

Fedora-*-armhfp-24_Alpha-7 disk images

How reproducible:

Always with Fedora-Minimal-armhfp-24_Alpha-7, Fedora-LXDE-armhfp-24_Alpha-7

Steps to Reproduce:

Build e.g. mainline u-boot-2016.03.tar.bz2 (make mx6cuboxi_defconfig and make)
Copy disk imge to microSD card (e.g. dd if=Fedora-Minimal-armhfp-24_Alpha-7-sda.raw of=/dev/sdX)
Copy SPL to microSD card (e.g. dd if=SPL of=/dev/sdX bs=1k seek=1; sync)
Copy u-boot.img to microSD card (e.g. dd if=u-boot.img of=/dev/sdX bs=1k seek=69; sync)
Flip microSD card in cubox-i and power up

Actual results:

U-boot splash shows up at HDMI video
After "Starting kernel ..." the HDMI video turns black with no further output
The serial console get stuck after round about 43 seconds, see "serial.log" for reference

Expected results:

A working graphical desktop after a short time with user space setup applied

Additional info:

Rebuilding e.g. kernel-4.5.0-0.rc7.git0.2.fc24.src.rpm with attached "config-local" (i.e. flipping some modules to buld-in) and reinstalling the result works for me
See "dmesg.log" and "Xorg.0.log" for reference
Comment 1 billiboy 2016-03-29 10:15:55 UTC 
Created attachment 1141185 [details]
config-local
Comment 2 billiboy 2016-03-29 10:17:15 UTC 
Created attachment 1141186 [details]
dmesg.log
Comment 3 billiboy 2016-03-29 10:18:10 UTC 
Created attachment 1141187 [details]
Xorg.0.log
Comment 4 Peter Robinson 2016-03-29 14:33:36 UTC 
This is actually booting fine.

There's two issues here:
1) no X display, already being addressed in rhbz #1321330
2) you need to specify a console= parameter to ensure initial setup runs on the serial port in /boot/extlinux/extlinuxc.conf and that's where this is getting stuck on the serial console.

The first is a bug we're already tracking, the second issue isn't a bug.

No idea why you're specifying a config-local, but shows you're using a custom kernel. We already have most of those options, or we explicitly can't ship them that way due to needing to support generic kernels for all devices.

*** This bug has been marked as a duplicate of bug 1321330 ***
Comment 5 billiboy 2016-03-29 16:00:13 UTC 
(In reply to Peter Robinson from comment #4)
> This is actually booting fine.
> 
> There's two issues here:
> 1) no X display, already being addressed in rhbz #1321330

I will wait for the outcome of bug 1321330, maybe a hint, I have also to set "CONFIG_REGULATOR_ANATOP=y" to get HDMI video working with the buil-in CONFIG_IMX_* modules.

> 2) you need to specify a console= parameter to ensure initial setup runs on
> the serial port in /boot/extlinux/extlinuxc.conf and that's where this is
> getting stuck on the serial console.

There where already console= parameters given as can be seen from "append: ro root=UUID=ea75933f-764f-4a3a-9c03-261c408be548 console=ttymxc0,115200n8 console=tty1" in serial log, but maybe it is not working cause of HDMI video not working.
With the same parameters on the rebuild kernel I get consoles on serial and HDMI video.

> The first is a bug we're already tracking, the second issue isn't a bug.
> 
> No idea why you're specifying a config-local, but shows you're using a
> custom kernel. We already have most of those options, or we explicitly can't
> ship them that way due to needing to support generic kernels for all devices.

Fedora kernel has already all those options from config-local as modules, I only flipped them to build-in to make it work for cubox-i.