(12-09-2019, 05:12 AM)danielt Wrote: The kernel is handled by the package manager (it's just a ` make bindeb-pkg` from the kernel build system though) with a tiny hack thrown in to ensure the kernel is uncompressed when it is installed to /boot (the u-boot distro boot protocol doesn't work with compressed kernels).
However the kernel is just a download rather than a proper apt repo so there is no kernel upgrade path. A PPA is a good idea although hopefully it can be obsoleted even more quickly than my installer: providing the fuel guage driver and the panel-simple update get upstreamed this cycle PPA can be obsolete as soon as Debian adopts v5.6 kernel!
This has me salivating. I'm easily excited, I guess. :-)
-- Jeremiah
— Jeremiah Cornelius
"Be the first person not to do something, that no one has thought of not doing before’’
— Brian Eno, "Oblique Strategies"
hi there,
nice work and thank you. is there something that can be done regarding the boot speed?
the original debian img boots up in few seconds but after trying the v5.4 kernel installer the screen is blank for a 60seconds and then starts output the boot sequence. i tried the crypted version and had few errors during the script install sequence, but the system boots. i had to set the boot flag to the partition but am not sure now if it was necessary or i was just too impatient and turned off the machine before the screen started the output. and i haven't managed to get the wpa_supplicant to connect to my wifi yet but i'll have a look at that during the weekend.
Audio should be working buy the DAC is muted by default. You can use alsamixer -D hw:0 to unmute the Left and Right Headphone Mixer DACs. This is what the comments about "priming the ALSA state" are about... if the installer did that then the DACs would be unmuted by default.
The boot time is a more complex issue. AFAIK the slow boot time occurs because u-boot hands some of the cores to Linux when they are running at a very low clock speed. This makes all the kernel operations until the cpufreq driver comes up perform very badly (much of the time you spend waiting with a black screen is simply a decompression algorithm that would normally take less than 2 seconds). I've not looked any further than this just yet... although I did wonder if the best fix might end up in u-boot rather than the kernel anyway.
Has anyone found Bluetooth to work when installed in this way? I had a self-made Ubuntu rootFS I was using with tsys' kernel, which had broken Bluetooth. Tried this installer to see if it worked there, but it's broken in the same way.
