fysafysa has quit [Read error: Connection reset by peer]
tl_lim has quit [Ping timeout: 245 seconds]
vagrantc has quit [Quit: leaving]
neal has joined #linux-rockchip
neal has quit [Client Quit]
kaspter has joined #linux-rockchip
anarsoul|3 has quit [Ping timeout: 276 seconds]
ganbold has quit [Quit: This computer has gone to sleep]
lurchi_ is now known as lurchi__
cnxsoft has joined #linux-rockchip
tl_lim has joined #linux-rockchip
equaa has quit [Ping timeout: 256 seconds]
nots has quit [Quit: Page closed]
tl_lim has quit [Ping timeout: 260 seconds]
tl_lim has joined #linux-rockchip
vagrantc has joined #linux-rockchip
alyssa has joined #linux-rockchip
<alyssa>
On a C201 running mainline with depthcharge (partitioned with cgpt), is it possible to expand the kernel partition / shrink the adjacent data partition, without needing to rebuild the whole system externally? If bad goes to worse, I do have backups, but I'm hoping for something cleaner if possible.
<alyssa>
(I'm trying to switch from a minimal custom kernel to a standard Debian one. For reasons I don't remember and now regret dearly, my kernel partition is only 16MB, fine for the minimal image. The packed/signed Debian kernel is 20MB.)
<vagrantc>
in my experience there was a limit to how much data depthcharge would take in the kernel partition ...
<vagrantc>
i don't remember if it was 16MB or 32MB ...
<vagrantc>
it was definitely not enough for debian-installer
* vagrantc
switched to using xz compression for the initrd which helped a lot
<vagrantc>
that said, i've never had it working all that well
* vagrantc
was really excited about the progress hanetzer made with u-boot
<alyssa>
bleh
<alyssa>
vagrantc: I have it working on an external USB so presumably depthcharge doesn't care :p
<vagrantc>
for reasons exactly like arbitrary size limits and inability to have a menu or any trivial way to select between kernel versions
<alyssa>
just don't want to trash my internal partition, since I have a lot to do tomorrow and restoring backups is not on the list ;)
<vagrantc>
alyssa: then it was probably 32MB
<vagrantc>
i should give mainline coreboot a try again; i think there were issues with the old libreboot version i had regarding the emmc
* alyssa
is probably running that old libreboot version
<vagrantc>
alyssa: which model? 2gb ram or 4gb?
* vagrantc
suspects problems with certain eMMC modules
<alyssa>
4gb
<vagrantc>
hm.
<alyssa>
I do have issues with eMMC but it's usually tolerable and not the issue at hand :p
<vagrantc>
same here... but the eMMC module may be different, or who knows what
<vagrantc>
mine pretty much halts the machine
<vagrantc>
even if i'm booting with usb or microsd rootfs
<vagrantc>
e.g. not trying to use the eMMC
* vagrantc
would really like to get it working, having been futzing with it since 2016 now...
<alyssa>
ah, hm. not an issue I've dealt withthen
<vagrantc>
it was tantalizingly useable with linux 4.8 ... and then stretch released with 4.9 and it never really worked
<vagrantc>
alyssa: i don't have much experience resizing GPT partitions ... especially those made with cgpt
<alyssa>
in any event, I'm spending way too much time on IRC (again). guess I'll come back to hacking on this later... thanks anyways :)
<vagrantc>
in theory it should be fine ... hah
<vagrantc>
e.g. resize the filesystem to a smaller size, delete the partitions and create new ones...
<vagrantc>
alyssa: good luck!
<alyssa>
:)
* vagrantc
waves
vagrantc has quit [Quit: leaving]
tl_lim has quit [Ping timeout: 260 seconds]
tl_lim has joined #linux-rockchip
<hanetzer>
alyssa: don't you bleh me :< :P
lurchi_ has joined #linux-rockchip
lurchi__ has quit [Ping timeout: 248 seconds]
vstehle has joined #linux-rockchip
cnxsoft1 has joined #linux-rockchip
cnxsoft has quit [Read error: Connection reset by peer]
cnxsoft1 is now known as cnxsoft
kaspter has quit [Quit: kaspter]
hanetzer has quit [Ping timeout: 248 seconds]
LongChair_ has joined #linux-rockchip
Omegamoon has joined #linux-rockchip
tl_lim has quit [Ping timeout: 260 seconds]
tl_lim has joined #linux-rockchip
hanetzer has joined #linux-rockchip
cyteen_ has quit [Quit: Leaving]
tl_lim has quit [Ping timeout: 260 seconds]
tl_lim has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
lukasz_ has joined #linux-rockchip
<sphalerite>
alyssa: at one point I repartitioned an existing ancient debian install from its own initrd
<sphalerite>
if you pass break=premount to the kernel you can get a shell, mount the root filesystem yourself, copy the programs like fdisk (presumably cgpt instead for you) and mke2fs into the initramfs's root file system, unmount the root filesystem again, and use the tools to repartition :)
tl_lim has quit [Read error: Connection reset by peer]
kaspter has joined #linux-rockchip
yann has joined #linux-rockchip
sphalerite has quit [Ping timeout: 240 seconds]
mcan has quit [Ping timeout: 276 seconds]
matthias_bgg has quit [Remote host closed the connection]
lkcl has joined #linux-rockchip
lkcl has quit [Ping timeout: 245 seconds]
lkcl has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
sphalerite has joined #linux-rockchip
lkcl has quit [Ping timeout: 256 seconds]
lkcl has joined #linux-rockchip
kaspter has quit [Read error: Connection reset by peer]
fireglow has quit [Remote host closed the connection]
fireglow has joined #linux-rockchip
kaspter has joined #linux-rockchip
lukasz_ has quit [Ping timeout: 252 seconds]
lukasz_ has joined #linux-rockchip
nighty-- has quit [Quit: Disappears in a puff of smoke]
kaspter has quit [Quit: kaspter]
equaa has joined #linux-rockchip
lurchi_ is now known as lurchi__
afaerber has quit [Quit: Leaving]
afaerber has joined #linux-rockchip
cnxsoft has quit [Quit: cnxsoft]
JohnDoe_71Rus has joined #linux-rockchip
tllim has joined #linux-rockchip
afaerber has quit [Ping timeout: 265 seconds]
afaerber has joined #linux-rockchip
yann has quit [Ping timeout: 245 seconds]
yann has joined #linux-rockchip
afaerber has quit [Ping timeout: 276 seconds]
lkcl has quit [Ping timeout: 268 seconds]
tl_lim has joined #linux-rockchip
tllim has quit [Ping timeout: 245 seconds]
Easyfab has joined #linux-rockchip
yann has quit [Ping timeout: 245 seconds]
LargePrime has quit [Read error: Connection reset by peer]
aalm has joined #linux-rockchip
ezequielg has joined #linux-rockchip
<ezequielg>
mmind00: i'm seeing this:
<ezequielg>
WARNING: CPU: 3 PID: 129 at /home/zeta/repos/linux/next/drivers/gpu/drm/rockchip/rockchip_drm_vop.c:1010 vop_crtc_atomic_flush+0x220/0x238
<ezequielg>
on rk3288 and rk3399 too, in linux-next.
<ezequielg>
kind of odd, because nobody reported it.
<ezequielg>
IOW: it's a vblank timeout.
lkcl has joined #linux-rockchip
lukasz_ has quit [Quit: Leaving]
<ezequielg>
i'll bisect a little bit, perhaps it's the psr code.
vagrantc has joined #linux-rockchip
Svenska has joined #linux-rockchip
<Svenska>
hi. i've got a small rockchip-based tablet (rk3126) and was wondering about the linux-support. apart from the mali, are any major drivers missing?
<Svenska>
the tablet currently runs a kernel 3.10, but has enough hardware otherwise to make for a decent linux system
<vagrantc>
there are no device-tree files for rk3126 in mainline linux ... so that's not promising
<vagrantc>
there are for rk3188
<vagrantc>
no idea how similar they are; maybe they share some drivers
anarsoul|3 has joined #linux-rockchip
<Svenska>
how do i read the devicetree from the device (no root, and no /sys/firmware/device-tree/fdt file)?
<Svenska>
the kernel feels rather ancient by now ;)
<vagrantc>
is there /proc/kconfig.gz ?
<Svenska>
no
<vagrantc>
maybe check /proc/device-tree (which is a symlink on recent versions, but maybe this is old enough)
<Svenska>
no, it's a symlink
<vagrantc>
er, /proc/config.gz
<Svenska>
neither :)
<Svenska>
checked that already :)
<vagrantc>
might be pre-devicetree
<Svenska>
well, /proc/device-tree and /sys/firmware/device-tree exist
<vagrantc>
but there's nothing in them?
<Svenska>
so that's rather unlikely, i assume? (i have no experience with pre-devicetree kernels)
<Svenska>
no, it's populated
<vagrantc>
oh
<vagrantc>
ok, i misunderstood you, then
<Svenska>
$ find /sys/firmware/devicetree/|wc -l
<Svenska>
4595
<vagrantc>
i *think* you can use device-tree-compiler/dtc to generate a device-tree from the directory
<vagrantc>
it's essentially just another view of the same data
<Svenska>
okay... need to get root first :)
<vagrantc>
you can't read the files in it?
<Svenska>
not all of them
<vagrantc>
well, good luck ... :)
<Svenska>
i've heard that rockchip mainline support is rather good (due to rockchip contributing)
<Svenska>
mh, the adb pull worked, so apparently i can read the complete tree.
<Svenska>
do you know how the general state of mainline for rockchip is?
libv_ has joined #linux-rockchip
libv has quit [Ping timeout: 248 seconds]
<beeble>
Svenska: depends on the SoC
<Svenska>
rk3126? :D
<Svenska>
the closest in numbers i see in linux 4.16 is rk3188
<Svenska>
but i don't know how similar they are.
<beeble>
there is 4.4 vendor support
<Svenska>
sunxi does have nicer webpages, but i only had the choice between "does android 4.4" and "does android 6.0", and the latter seemed more useful. also, i broke the former device by dropping it :(
<beeble>
Svenska: but there are upstream patches in the queue
<beeble>
but just basic stuff for now
<mmind00>
ezequielg: I also don't remember seeing this in recent times ... my I did tests on rk3288 recently and the display did come up correctly ... so maybe you're hitting some sort of timing issue (different probe order, resulting in something not being enabled or so)
<Svenska>
for this chipset?
<Svenska>
the status matrix from rockchip only mentions rk3399, rk3288 and rk3328 unfortunately
<fysa>
ayufan, thanks for all your work on the rock64 .. I am setup full-time with rock64 4GB as my main work portable desktop .. VSS code, lamp, nodejs, zfs, good enough desktop @ 1080p, media server with plex/tvheadend/mopidy/mpd/nzb and everything else you could need (sans kodi) .. 400mb RAM used after boot, going to try dual monitor with a displaylink soon