fysa has quit [Read error: Connection reset by peer]
fysa has joined #linux-rockchip
cnxsoft has joined #linux-rockchip
lurchi_ is now known as lurchi__
equaa has quit [Ping timeout: 245 seconds]
lkcl has quit [Ping timeout: 245 seconds]
nots has quit [Quit: Page closed]
kaspter has quit [Remote host closed the connection]
kaspter has joined #linux-rockchip
lurchi_ has joined #linux-rockchip
lurchi__ has quit [Ping timeout: 260 seconds]
vstehle has joined #linux-rockchip
kaspter has quit [Remote host closed the connection]
kaspter has joined #linux-rockchip
cnxsoft has quit [Ping timeout: 252 seconds]
kaspter has quit [Remote host closed the connection]
kaspter has joined #linux-rockchip
lukasz_ has joined #linux-rockchip
<sphalerite>
So my C201 chromebook seems to hang on boot nondeterministically, but almost always right after printing "[ 2.051778] backlight_regulator: disabling". This happens every time as far as I've been able to tell if I boot with my yubikey in the USB port, and only some of the time if I remove it. What might be going on here?
<Ke>
you will need to have support for initramfs and the compression type your initramfs is using, some compression algos require special parameters to work for initramfs
<Ke>
"find . | cpio -H newc -o | lzop -9c" is what I use for lzo
<sphalerite>
it's the nixos standard kernel config and the nixos-built initramfs so I don't think that should be an issue
<sphalerite>
mine is just gzipped
<sphalerite>
oh hm you have the fdt before the ramdisk, maybe that makes a difference?
<Ke>
no idea, you can try
<Ke>
mine definitely works
<Ke>
I have encrypted rootfs and would not be typing on this machine, if it did not work
<sphalerite>
:)
<sphalerite>
alright, brb, trying it
<sphalerite>
hm nope
<sphalerite>
It's not a size issue either, right? initramfs is 7.2M and kernel is 6.1M
kaspter has quit [Read error: Connection reset by peer]
kaspter has joined #linux-rockchip
<sphalerite>
ok, I'm now using the exact same .its as you modulo the paths. So I think we can rule that out
tllim has quit [Quit: Leaving]
<sphalerite>
Does the kernel need any special options or something for it to work?
rompelstompel has quit [Read error: Connection reset by peer]
rompelstompel has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
jailbox has quit [Ping timeout: 248 seconds]
<Ke>
sphalerite: can't help you here, I think the size limit may be 32M for the whole package
<sphalerite>
so that's not it :/ and you don't pass anything particular on the commandline?
<Ke>
console=tty1 mostly, and then some options of my own
<sphalerite>
hm ok, I'm passing rockchip.usb_uart console=ttyS2,115200 to get a serial console, but those things aren't relevant to the initramfs…
jailbox has joined #linux-rockchip
afaerber has quit [Quit: Leaving]
cnxsoft has quit [Ping timeout: 252 seconds]
<sphalerite>
if the kernel didn't find the initramfs, it also wouldn't have unloaded it, right? So if it's loaded it should still be hanging about somewhere in memory?
<Ke>
sphalerite: there are some ttl pins on some usb port or something?
<sphalerite>
or is this a gross misunderstanding? (I don't know that much about the low-level stuff)
<sphalerite>
yep, passing rockchip.usb_uart turns one of the USB ports into a TTL serial port, accessible on ttyS2
<Ke>
sphalerite: thanks, good to know
<sphalerite>
found out about this from hanetzer and mmind00
<sphalerite>
It's been very helpful
<Ke>
how about samsung chromebook plus?
<Ke>
would be lovely to have some central docs repo for things like this
<sphalerite>
the docs say "On Rockchip SoCs" (Documentation/admin-guide/kernel-parameters.txt)
<sphalerite>
so it should probably work there too.
<Ke>
yeah, but the pinout
<sphalerite>
"When active, the signals of the debug-uart get routed to the D+ and D- pins of the usb port and the regular usb controller gets disabled."
<Ke>
if you use like couple of characters more for the docs it's like good
<Ke>
like rx to D+, tx to D- GND to GND
<sphalerite>
GND to GND is obvious, and as for rx and tx you're going to get them wrong on the first attempt no matter what ;)
afaerber has joined #linux-rockchip
<sphalerite>
GOOGLE_MEMCONSOLE_COREBOOT is conditional on GOOGLE_FIRMWARE, which is described as being specific to google's proprietary servers, but is this perhaps also what's used on chromebooks? I'm missing /sys/firmware/log on the mainline kernel, and it does appear in chromeos
cnxsoft has joined #linux-rockchip
afaerber has quit [Quit: Leaving]
BenG83 has joined #linux-rockchip
lkcl has joined #linux-rockchip
afaerber has joined #linux-rockchip
kloczek has quit [Ping timeout: 260 seconds]
ganbold has joined #linux-rockchip
aalm has quit [Ping timeout: 245 seconds]
aalm has joined #linux-rockchip
wzyy2 has quit [Read error: Connection reset by peer]
wzyy2 has joined #linux-rockchip
kloczek has joined #linux-rockchip
equaa has joined #linux-rockchip
lkcl has quit [Ping timeout: 252 seconds]
<paulk-gagarine>
sphalerite, didn't know that tric about rockchip.usb_uart, neat
<paulk-gagarine>
trick
<sphalerite>
holy crap I helped paulk-gagarine
<sphalerite>
although all credit goes to mmind00 and hanetzer as mentioned before :p
<paulk-gagarine>
:)
<paulk-gagarine>
sphalerite, I definitely think GOOGLE_FIRMWARE is relevant for CrOS devices as well
<hanetzer>
sphalerite: nah, don' give me credit. I just parroted it :P
<paulk-gagarine>
sphalerite, wanna craft a patch to clarify the help text?
<sphalerite>
This looks like an opportunity for my first commit in linux then :D
<paulk-gagarine>
:)
<paulk-gagarine>
feel free to CC me
<hanetzer>
sphalerite: you never forget your first :)
<sphalerite>
What do I base it on, and where do I send it?
Omegamoon has joined #linux-rockchip
<hanetzer>
sphalerite: wherever ./scripts/get_maintainer.pl spits out
<paulk-gagarine>
sphalerite, use linus' master tree for base
<hanetzer>
yep.
<paulk-gagarine>
and yeah, then get_maintainers
<sphalerite>
thanks!
<paulk-gagarine>
apparently this was reworked on the cros kernel side to match mainline in 3.14
<paulk-gagarine>
ah nevermind, it was there in 3.10 as well
<paulk-gagarine>
but not enabled in my config
<paulk-gagarine>
mhh
<paulk-gagarine>
ah they had it under "depends on X86" in 3.10
<paulk-gagarine>
not my problem
<paulk-gagarine>
also GOOGLE_MEMCONSOLE is also under it and makes sense on ARM too
<paulk-gagarine>
although*
adj__ has quit [Quit: Leaving]
lurchi_ is now known as lurchi__
vagrantc has joined #linux-rockchip
kaspter has quit [Quit: kaspter]
return0e_ has quit [Read error: Connection reset by peer]
aalm has quit [Quit: xyz 2.0.1]
JohnDoe_71Rus has joined #linux-rockchip
cnxsoft has quit [Quit: cnxsoft]
tllim has joined #linux-rockchip
matthias_bgg has quit [Ping timeout: 245 seconds]
Easyfab has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
fysafysa has joined #linux-rockchip
fysa has quit [Read error: Connection reset by peer]
<vagrantc>
beeble: running linux 4.16.x, puma-rk3399 isn't recognizing usb3 devices ... it sees a USB3 hub, but nothing plugged into the usb3 ports ... am i maybe missing some obvious kernel module or something?
<beeble>
vagrantc: it probably sees only the usb2 part of the hub (lsusb -t)