PINE64
An unofficial Debian Installer for Pinebook Pro - Printable Version

+- PINE64 (https://forum.pine64.org)
+-- Forum: Pinebook Pro (https://forum.pine64.org/forumdisplay.php?fid=111)
+--- Forum: Linux on Pinebook Pro (https://forum.pine64.org/forumdisplay.php?fid=114)
+--- Thread: An unofficial Debian Installer for Pinebook Pro (/showthread.php?tid=8487)

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45


RE: An unofficial Debian Installer for Pinebook Pro - moonwalkers - 01-12-2021

(01-12-2021, 02:32 PM)Quanifi Wrote: Daniel, thanks for your contributions to the Pinebook Pro forum. I am trying to update to Debian from Manjaro and I'm getting and error when trying to do the install. Says: "error: could not lock database; file exists, if you are sure a package manager is not already running, you can remove /vsr/lib/pacman/db/lck"
ANy suggestions to get this installed....???

The source of this message is https://github.com/daniel-thompson/pinebook-pro-debian-installer/blob/master/install-debian#L43, where the script tries to install the packages necessary to bootstrap Debian, and it uses `pacman` to do so. As to what to do about it - the error message you quoted pretty much laid out everything for you already. Check if there are any instances of `pacman` running, and if there are none - remove the file/dir it mentions, re-run the script, ..., profit.


RE: An unofficial Debian Installer for Pinebook Pro - ab1jx - 01-26-2021

BTW: debootstrap is just a Bash script in /usr/sbin.  Sometimes it helps to look under the hood at what it's doing.

I don't want GPT and I want to install into a specific existing partition on my nvme so I'm running debootstrap manually.  I've used it before a few times.  It hit an error in stage 1 and stopped I guess.  I came back and tried to do stage 2 but it stopped, looking for debootstrap/suite.  Looking at the source I see SUITE is a variable in debootstrap which gets written out to debotstrap/suite at the end of stage 1 and stage 2 looks for it.


RE: An unofficial Debian Installer for Pinebook Pro - Tharadash - 01-30-2021

(09-25-2020, 07:25 AM)danielt Wrote:
(09-11-2020, 01:55 PM)xmixahlx Wrote: if it is the neon complier issue... are you using gcc 10? just step back to gcc 9.x. or use a git gcc (master is fixed).

hardware decoding working great with the linux build script in pbp-tools.

It is dependant on gcc version although its not the neon issue that is causing the trouble (since that is easy to workaround). I've seen gcc-9 builds that do work but I'm not willing to ship a kernel that doesn't compile with the default Debian compiler... the installer is supposed to be staying as close as possible to pure Debian (and already has a few too many hacks) and shipping code that cannot be compiled with the default compiler isn't good distro engineering.

Hi @danielt 

Is there any update on the gcc issues you encountered?

Until now, my pinebookpro with your installer is running quite fine :-)
However, since the latest kernels did contain quite a lot of updates to schedutil - I'd love to daily drive one of those soon! :-)

Kind regards

Tharadash


RE: An unofficial Debian Installer for Pinebook Pro - Fish - 02-19-2021

Hi, I am trying to install Debian through the installer, but I'm having some trouble with it. The pinebook pro runs mrfixit's image from SD, and I'm trying to install Debian on the emmc. The installer is started with the following command:./install-debian BLKDEV=/dev/mmcblk1 (double checked of course). I posted the error below. What am I doing wrong?

The error:
I: Configuring dbus...
W: Failure while configuring base packages. This will be re-attempted up to five times.
W: See /home/rock/pinebook-pro-debian-installer/sysimage/debootstrap/debootstrap.log for details (possibly the package policykit-1 is at fault)
W: Failure while configuring base packages. This will be re-attempted up to five times.
W: See /home/rock/pinebook-pro-debian-installer/sysimage/debootstrap/debootstrap.log for details (possibly the package policykit-1 is at fault)
W: Failure while configuring base packages. This will be re-attempted up to five times.
W: See /home/rock/pinebook-pro-debian-installer/sysimage/debootstrap/debootstrap.log for details (possibly the package policykit-1 is at fault)
W: Failure while configuring base packages. This will be re-attempted up to five times.
W: See /home/rock/pinebook-pro-debian-installer/sysimage/debootstrap/debootstrap.log for details (possibly the package policykit-1 is at fault)
W: Failure while configuring base packages. This will be re-attempted up to five times.
W: See /home/rock/pinebook-pro-debian-installer/sysimage/debootstrap/debootstrap.log for details (possibly the package policykit-1 is at fault)


>>>> umount

umount: /home/rock/pinebook-pro-debian-installer/sysimage/dev: not mounted
umount: /home/rock/pinebook-pro-debian-installer/sysimage/proc: not mounted
umount: /home/rock/pinebook-pro-debian-installer/sysimage/sys: not mounted


RE: An unofficial Debian Installer for Pinebook Pro - moonwalkers - 02-19-2021

(02-19-2021, 01:40 PM)Fish Wrote: Hi, I am trying to install Debian through the installer, but I'm having some trouble with it. The pinebook pro runs mrfixit's image from SD, and I'm trying to install Debian on the emmc. The installer is started with the following command:./install-debian BLKDEV=/dev/mmcblk1 (double checked of course). I posted the error below. What am I doing wrong?

The error:
I: Configuring dbus...
W: Failure while configuring base packages.  This will be re-attempted up to five times.
W: See /home/rock/pinebook-pro-debian-installer/sysimage/debootstrap/debootstrap.log for details (possibly the package policykit-1 is at fault)
W: Failure while configuring base packages.  This will be re-attempted up to five times.
W: See /home/rock/pinebook-pro-debian-installer/sysimage/debootstrap/debootstrap.log for details (possibly the package policykit-1 is at fault)
W: Failure while configuring base packages.  This will be re-attempted up to five times.
W: See /home/rock/pinebook-pro-debian-installer/sysimage/debootstrap/debootstrap.log for details (possibly the package policykit-1 is at fault)
W: Failure while configuring base packages.  This will be re-attempted up to five times.
W: See /home/rock/pinebook-pro-debian-installer/sysimage/debootstrap/debootstrap.log for details (possibly the package policykit-1 is at fault)
W: Failure while configuring base packages.  This will be re-attempted up to five times.
W: See /home/rock/pinebook-pro-debian-installer/sysimage/debootstrap/debootstrap.log for details (possibly the package policykit-1 is at fault)


>>>> umount

umount: /home/rock/pinebook-pro-debian-installer/sysimage/dev: not mounted
umount: /home/rock/pinebook-pro-debian-installer/sysimage/proc: not mounted
umount: /home/rock/pinebook-pro-debian-installer/sysimage/sys: not mounted

Have you tried reading what's written on the tin?
Code:
See /home/rock/pinebook-pro-debian-installer/sysimage/debootstrap/debootstrap.log for details



RE: An unofficial Debian Installer for Pinebook Pro - Fish - 02-20-2021

During the installation there appears to be a debootstrap.log file, after the error it deletes the file and the debootstrap directory...


RE: An unofficial Debian Installer for Pinebook Pro - moonwalkers - 02-20-2021

(02-20-2021, 04:18 AM)Fish Wrote: During the installation there appears to be a  debootstrap.log file, after the error it deletes the file and the debootstrap directory...

Hmm... Try adding `--keep-debootstrap-dir` parameter somewhere in https://github.com/daniel-thompson/pinebook-pro-debian-installer/blob/master/install-debian#L168-L170? `debootstrap` itself deleting the whole target directory is the only reason I can think of that file being gone, as https://github.com/daniel-thompson/pinebook-pro-debian-installer/blob/master/install-debian#L291-L298 doesn't appear to be doing that.


RE: An unofficial Debian Installer for Pinebook Pro - KiteX3 - 02-20-2021

(02-19-2021, 01:40 PM)Fish Wrote: Hi, I am trying to install Debian through the installer, but I'm having some trouble with it. The pinebook pro runs mrfixit's image from SD, and I'm trying to install Debian on the emmc. The installer is started with the following command:./install-debian BLKDEV=/dev/mmcblk1 (double checked of course). I posted the error below. What am I doing wrong?

The error:
~snip~

I just solved this problem while installing Debian on my Pinebook Pro. I used a hint from the Github issues list.

What I did was I searched for and removed "network-manager" from line 170 of the `./install-debian` script. It seems network-manager tries to pull in policy-kit but doesn't know how to, and that causes issues during install. After removing it, wifi worked just fine on first boot if I installed the standard KDE desktop, because I think network-manager gets installed later as a dependency of KDE (probably for other desktops too) but since I wanted a minimal KDE install I also tried installing without full KDE; that broke all internet when I booted into the OS for the first time,  since network-manager never got installed. Turns out that you need to do a `./install-debian do_shell` to get a shell in the new OS as a chroot and then install network-manager while you can still lean on the host OS's network connection. (It's particularly convenient to do so anyway to install stuff like minimal KDE, or gvim, or whatever other must-have software you need out of the box, so you might as well anyway.)


RE: An unofficial Debian Installer for Pinebook Pro - Fish - 02-21-2021

(02-20-2021, 10:35 AM)KiteX3 Wrote:
(02-19-2021, 01:40 PM)Fish Wrote: Hi, I am trying to install Debian through the installer, but I'm having some trouble with it. The pinebook pro runs mrfixit's image from SD, and I'm trying to install Debian on the emmc. The installer is started with the following command:./install-debian BLKDEV=/dev/mmcblk1 (double checked of course). I posted the error below. What am I doing wrong?

The error:
~snip~

I just solved this problem while installing Debian on my Pinebook Pro. I used a hint from the Github issues list.

What I did was I searched for and removed "network-manager" from line 170 of the `./install-debian` script. It seems network-manager tries to pull in policy-kit but doesn't know how to, and that causes issues during install. After removing it, wifi worked just fine on first boot if I installed the standard KDE desktop, because I think network-manager gets installed later as a dependency of KDE (probably for other desktops too) but since I wanted a minimal KDE install I also tried installing without full KDE; that broke all internet when I booted into the OS for the first time,  since network-manager never got installed. Turns out that you need to do a `./install-debian do_shell` to get a shell in the new OS as a chroot and then install network-manager while you can still lean on the host OS's network connection. (It's particularly convenient to do so anyway to install stuff like minimal KDE, or gvim, or whatever other must-have software you need out of the box, so you might as well anyway.)

Worked like a charm! Removing network-manager from line 170 did the trick. It was also possible to select different wireless connections after the installation (Gnome3) despite not installing the network-manager.


RE: An unofficial Debian Installer for Pinebook Pro - KiteX3 - 02-21-2021

Glad I could help!

Unfortunately, I've since encountered problems with my own eMMC install of Debian using this installer since then. I was watching a video stream on it, and it was working fine. Then the computer froze at some point. After waiting a good while, I force-restarted my PBP. Now, if it's booting from eMMC, it doesn't even turn on the display at all. The only sign of life is the power LED; it seems to indicate the computer is in a boot loop, since the light tends to repeat a "30-seconds-on, blink off and back on" pattern until I force power off again.

I can still get into the chroot just fine through SD card and ./install-debian do_shell. Does anyone know what might be wrong, and more importantly, how I might fix it?

Edit: I figured it out. I just needed to wait longer, and the OS sorted itself out after several reboot cycles.