[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] kihanos:
I have managed to install an Arch Linux system boot on my SGN 10.1 2014 edition (P600) on the external SD Card using the RECOVERY partition. I have encountered an issue though: I can't manage to get any screen output. That's why I'm calling for help here.

Let me sum up what I did and what's working first.

I flashed on my tablet Xluco's kernel (1.7, found in the thread) and installed Arch Linux on the external SD Card using Linux Deploy.

In the chroot, I got rid of systemd and replaced it by initscripts-fork (found on the AUR). That is because I could not manage to boot using systemd. I also tried openrc without success.

I copied the mfc firmware from android's system partition. I then configured some wireless connection with netcfg and enabled sshd.

I built Xluco's kernel 1.7 with a few tweaks: enabled virtual terminal and fbcon (as a module), changed the CMDLINE to be able to boot. I copied all that in my chrooted linux and mkinitcpio built an initial ramdisk for me. A finally packed all that in some flashable image for my recovery partition using abootimg.

I dd'd my image to the RECOVERY and rebooted.

So. It boots (after quite a long Samsung Galaxy Note screen, seems to be linked with enabling VT), I can log in through ssh. The problem is, I can't get the screen to work. Calling "modprobe fbcon" gives me

modprobe: ERROR: could not insert 'fbcon': Invalid argument

but nothing new in dmesg.

I also tried to configure an X server using fbdev as a video driver. The screen blinks as a call startx, but nothing more. It speaks a lot in dmesg though

# dmesg | grep fb
[ 1299.916361] s3c-fb exynos5-fb.1: + s3c_fb_blank mode 1
[ 1299.916372] s3c-fb exynos5-fb.1: pm_relax
[ 1300.224278] s3c-fb exynos5-fb.1: s3c_fb_clk_validation : 0, 0, 0, 0, 0
[ 1300.224283] s3c-fb exynos5-fb.1: ready to suspend!
[ 1300.224327] s3c-fb exynos5-fb.1: - s3c_fb_blank
[ 1301.288983] s3c-fb exynos5-fb.1: s3c_fb_pan_display::output_on is FALSE
[ 1301.290184] s3c-fb exynos5-fb.1: all clocks are ready!
[ 1301.290249] s3c-fb exynos5-fb.1: s3c_fb_clk_validation : 0, 0, 0, 0, 0
[ 1301.290255] s3c-fb exynos5-fb.1: ready to suspend!
.
.
.
[ 1301.542001] s3c-fb exynos5-fb.1: all clocks are ready!
[ 1301.548573] s3c-fb exynos5-fb.1: s3c_fb_clk_validation : 0, 0, 0, 0, 0
[ 1301.548580] s3c-fb exynos5-fb.1: ready to suspend!
[ 1302.254599] s3c-fb exynos5-fb.1: + s3c_fb_blank mode 0
[ 1302.255261] s3c-fb exynos5-fb.1: all clocks are ready!
[ 1302.256138] s3c-fb exynos5-fb.1: pm_stay_awake
[ 1302.256146] s3c-fb exynos5-fb.1: mali level : 0
[ 1302.256243] s3c-fb exynos5-fb.1: - s3c_fb_blank

The dots symbolize a few hundreds occurences of the three lines

[ 1301.542001] s3c-fb exynos5-fb.1: all clocks are ready!
[ 1301.548573] s3c-fb exynos5-fb.1: s3c_fb_clk_validation : 0, 0, 0, 0, 0
[ 1301.548580] s3c-fb exynos5-fb.1: ready to suspend!

My guess is, there should be nothing like "s3c_fb_pan_display::output_on is FALSE" in here...

Does anyone have any idea or suggestion to solve that problem? Or to get a better diagnosis at least?

Has someone managed to have it working?

EDIT:

I've tested to use the framebuffer through some low-level tools. Using

fbi -d /dev/fb0 -T 1 -a picture.jpg

drew the nice picture on my screen. No output in the log files though.