(01-14-2020, 09:14 PM)ab1jx Wrote: This is fun, I like it because it uses debootstrap and you potentially end up with a cutting-edge system.  But I wonder if it's possible to toughen it so it drops breadcrumbs and checks for those as it goes along.  For those of us with unreliable networks where everything isn't likely to get done at once.  I got up to choosing software, lxde, web server, etc, then everything went dead.  Restarted and it went back and partitioned the SD again, got up to about the same place and died again.  My new SD boots to a very basic system with no network.   Since I think I can muddle through by doing dpkg -i downloaded debs on usb devices until I get network I'll probably continue.

But if it could recognize waypoints from a partial install like make does it would save time for those of us with imperfect networks.  Could these use make?

I decided to give it one more shot and it got through the downloads without stopping, now it's installing.  A newer than I've ever seen Debian on my first ever new laptop, always bought fixer-uppers before.  50% done,  unpacking.

(01-14-2020, 06:50 PM)ThatGeoGuy Wrote: I'm trying to figure out what the rough edges would be, but not having encryption support on a laptop is a pretty big one for me.I assume by default most of the inputs work, and WiFi / Bluetooth is in good shape? If so, it doesn't seem too limited in comparison to default debian, so I'll take your word for it. My plan is to avoid most DEs anyways, and probably stick to awesomewm/sway/i3 anyways. So assuming the basics are working, I don't think my needs are too complex

(01-15-2020, 12:01 PM)bisco Wrote: Hi, thanks for the installer script, that makes installing a nearly pure Debian much easier!

I was trying to build my own kernel based on the posts in this thread, but when cloning https://gitlab.manjaro.org/tsys/linux-pinebook-pro and then running

Code:

make ARCH=arm64 pinebook_pro_defconfig
make KBUILD_IMAGE=arch/arm64/boot/Image bindeb-pkg

there are still a lot of unset kernel options and the config script goes through all of them.
Did you first base the config on the config of the system you built the kernel on and then used the `pinebook_pro_defconfig`?

(01-16-2020, 04:47 AM)danielt Wrote: Currently I do the following to configure:

Code:

make pinebook_pro_defconfig
scripts/config --set-str LOCALVERSION -1-pinebookpro-arm64
scripts/config --enable COMPAT
scripts/config --disable MODULE_COMPRESS
scripts/config --enable PREEMPT
scripts/config --disable HARDEN_EL2_VECTORS
scripts/config --enable RTC_DRV_RK808
make olddefconfig

Quote:PS I'm happy to point you at my exact kernel sources if you have problems getting something working but, to be honest, putting focus on my kernel is just splitting the development community. Using the Manjaro kernel for your work is, IMHO, better for everyone for now... and you can switch to "real" mainline as soon as Thomas' lands the remaining patches.

(01-15-2020, 05:28 PM)Antoine Wrote:

Code:

antoine@frisbee:~$ vainfo
libva info: VA-API version 1.6.0
libva info: Trying to open /usr/lib/aarch64-linux-gnu/dri/rockchip_drv_video.so
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit

(01-16-2020, 09:40 PM)rillian Wrote: Where is a good place to keep track of bugs related to the Bullseye image? Maybe on the installer github project? It's easy for issues to get lost on the forum, but filing directly with Debian or upstream makes it hard for Pinebook community members to see the status of thing.