[linux-gru] Black screen on boot after kernel upgrade

[ThirstyShark]

Hi, after upgrading to 4.4-166 on the linux-gru kernel (i am using a samsung chromebook plus) the device no longer boots arch linux. After clicking Ctrl-U at the boot screen, the screen goes black. Normally, after about 2 seconds (after the rockchip driver loads) the screen turns on and the boot process continues. However, after the upgrade, the screen simply does not turn on.

I had wiped my package cache at some point, so I didn't have an older kernel saved, so I extracted 4.4-164 from the linux-gru-latest image. After booting that kernel, however, wifi no longer worked, the wireless interface didn't even show up. I have reflashed the kernel several times to no avail on either version. Wifi still works fine in ChromeOS which is probably on a way older kernel.

I have been using alarm for a couple months and have done several kernel upgrades fine until now.

So, I am looking for either a new kernel version that boots properly, another kernel version that is saved in an archive somewhere (I counl't find a working package archive), or a way to fix wifi on the older kernel (I was using that kernel previously with wifi fine; but after upgrading and downgrading it has stopped for some reason).

[tuxcoder]

I ran into the same problem last night on my Samsung Chromebook Plus. I didn't have time to manually revert to my previous kernel, and probably won't get a chance to until Tuesday evening.

Off-topic "comedy" of errors: whole-home humidifier sprung a leak 2 days ago so I shut it off --> house humidity dropped a lot --> everyone is "sparky" now as I say --> after this "gru" model kernel problem I grabbed my Samsung Chromebook 2 ("peach pit" model) as a spare --> inadvertently and very indirectly shocked it, which caused it to cold-reset and also magically disabled USB boot.



I got the Chromebook 2 back into Arch ARM pretty easily, at least.

[ramsey]

Same problem here too. I reinstalled everything and had 4.4.164. That has black screen on shutdown, but works. I updated to mainline kernel, and no more black screens, however, now no usb-storage works.

[TheCycoONE]

I've hit this issue as well. How did you go about getting an old kernel on it with the black screen?

[ramsey]

$this->bbcode_second_pass_quote('TheCycoONE', 'I')'ve hit this issue as well. How did you go about getting an old kernel on it with the black screen?

[TheCycoONE]

I asked on irc and was instructed to chroot into the sd card and install an old kernel from the package cache. I did that, and flashed it manually with dd (from the install instructions) and that worked.

Thanks

[bneumeier]

I have the same issue, also on samsung chromebook plus; but I do not have a package cache containing an old kernel. Is there a place I can get a working kernel?

[ramsey]

Turns out USB storage is working, just not FAT filesystems. I noticed a ISO9660 would mount, then tried an ext4 and that worked too. But if I plug a FAT formatted disk in, I get nothing in /dev/sd* and dmesg spits out,

[ 599.085125] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work [rockchipdrm]] Not connected. Disabling cdn
[ 612.236929] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work [rockchipdrm]] Not connected. Disabling cdn

I can work with this. If I find out why it doesn't like FAT before thread is locked, I'll post back.

[summers]

Is it able to load the fat kernel modules? try something like $this->bbcode_second_pass_code('', 'modprobe fat'). It should then be listed in $this->bbcode_second_pass_code('', 'cat /proc/filesystems').