Re: X11 modul for pinebook?
On Mon, Apr 20, 2020 at 12:49:34PM -0700, Vagrant Cascadian wrote: > On 2020-04-20, Andreas Tille wrote: > > I have a pinebook of the first generation installed with Stretch. I > > naively assumed that it would the right time to upgrade to Buster. > > Unfortunately X does not start any more: > > > > # grep EE /var/log/Xorg.[01].log > > /var/log/Xorg.0.log:[12.349] Current Operating System: Linux pinebook > > 3.10.105-bsp-1.2-ayufan-118 #1 SMP PREEMPT Sun Oct 15 21:40:57 UTC 2017 > > aarch64 > > /var/log/Xorg.0.log:(WW) warning, (EE) error, (NI) not implemented, > > (??) unknown. > > /var/log/Xorg.0.log:[12.363] (EE) fbturbo: module ABI major version > > (23) doesn't match the server's version (24) > > /var/log/Xorg.0.log:[12.364] (EE) Failed to load module "fbturbo" > > (module requirement mismatch, 0) > ... > > I thought it would help to build and install > > > > https://salsa.debian.org/raspi-team/xf86-video-fbturbo > > The pinebook is pretty much my primary machine (using it right now to > type this), and X is working fine here... It's not fancy accelerated > graphics, but it does work. I mostly have been using newer kernels from > buster-backports/sid/experimental, but the buster generation of kernels > worked fine for me last I tried. > > Maybe you have some customization in /etc/X11/xorg.conf* that's telling > it to use fbturbo instead of fbdev? > > What version of u-boot are you running? Again, it's been a while since I > tested the version in buster, but I've been using all the versions > uploaded since. Mainline (and Debian packaged) u-boot properly > configures the framebuffer for quite some releases... > > Good luck! > > live well, > vagrant I believe you may have quoted the wrong part of the message. They're still using a custom kernel so I'd push a bit harder trying out a debian kernel to see if that fixes their issue. -- Efraim Flashner אפרים פלשנר GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted signature.asc Description: PGP signature
Re: X11 modul for pinebook?
On 2020-04-20, Andreas Tille wrote: > I have a pinebook of the first generation installed with Stretch. I > naively assumed that it would the right time to upgrade to Buster. > Unfortunately X does not start any more: > > # grep EE /var/log/Xorg.[01].log > /var/log/Xorg.0.log:[12.349] Current Operating System: Linux pinebook > 3.10.105-bsp-1.2-ayufan-118 #1 SMP PREEMPT Sun Oct 15 21:40:57 UTC 2017 > aarch64 > /var/log/Xorg.0.log:(WW) warning, (EE) error, (NI) not implemented, (??) > unknown. > /var/log/Xorg.0.log:[12.363] (EE) fbturbo: module ABI major version (23) > doesn't match the server's version (24) > /var/log/Xorg.0.log:[12.364] (EE) Failed to load module "fbturbo" (module > requirement mismatch, 0) ... > I thought it would help to build and install > > https://salsa.debian.org/raspi-team/xf86-video-fbturbo The pinebook is pretty much my primary machine (using it right now to type this), and X is working fine here... It's not fancy accelerated graphics, but it does work. I mostly have been using newer kernels from buster-backports/sid/experimental, but the buster generation of kernels worked fine for me last I tried. Maybe you have some customization in /etc/X11/xorg.conf* that's telling it to use fbturbo instead of fbdev? What version of u-boot are you running? Again, it's been a while since I tested the version in buster, but I've been using all the versions uploaded since. Mainline (and Debian packaged) u-boot properly configures the framebuffer for quite some releases... Good luck! live well, vagrant signature.asc Description: PGP signature
X11 modul for pinebook?
Hi, I have a pinebook of the first generation installed with Stretch. I naively assumed that it would the right time to upgrade to Buster. Unfortunately X does not start any more: # grep EE /var/log/Xorg.[01].log /var/log/Xorg.0.log:[12.349] Current Operating System: Linux pinebook 3.10.105-bsp-1.2-ayufan-118 #1 SMP PREEMPT Sun Oct 15 21:40:57 UTC 2017 aarch64 /var/log/Xorg.0.log:(WW) warning, (EE) error, (NI) not implemented, (??) unknown. /var/log/Xorg.0.log:[12.363] (EE) fbturbo: module ABI major version (23) doesn't match the server's version (24) /var/log/Xorg.0.log:[12.364] (EE) Failed to load module "fbturbo" (module requirement mismatch, 0) /var/log/Xorg.0.log:[12.364] (EE) No drivers available. /var/log/Xorg.0.log:[12.364] (EE) /var/log/Xorg.0.log:[12.364] (EE) no screens found(EE) /var/log/Xorg.0.log:[12.364] (EE) /var/log/Xorg.0.log:[12.364] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. /var/log/Xorg.0.log:[12.364] (EE) /var/log/Xorg.0.log:[12.364] (EE) Server terminated with error (1). Closing log file. /var/log/Xorg.1.log:[ 1220.291] Current Operating System: Linux pinebook 3.10.105-bsp-1.2-ayufan-118 #1 SMP PREEMPT Sun Oct 15 21:40:57 UTC 2017 aarch64 /var/log/Xorg.1.log:(WW) warning, (EE) error, (NI) not implemented, (??) unknown. /var/log/Xorg.1.log:[ 1221.220] (EE) AIGLX: reverting to software rendering I thought it would help to build and install https://salsa.debian.org/raspi-team/xf86-video-fbturbo However, this did not changed anything. :-( Any idea what to do? Kind regards Andreas. -- http://fam-tille.de
Re: Graphical installer on arm64 (netboot and cdrom)
On Mon, Apr 20, 2020 at 07:36:42PM +0300, Alper Nebi Yasak wrote: >On 20/04/2020 18:38, Steve McIntyre wrote: >> Does /dev/tty0 show up in /proc/consoles in your setup? We might need >> to tweak that yet... > >Here is a small but untested patch for rootskel's reopen-console for that. Hmmm. Is this the right answer, though? I've got totally headless arm64 machines that also have a /dev/tty0. Would we want to run d-i there? Maybe, I'm genuinely not sure. It might be harmless, I guess...? >(Thanks for the cd image, it'll probably take me until tomorrow to test and >report back on it) Cool. :-) -- Steve McIntyre, Cambridge, UK.st...@einval.com "... the premise [is] that privacy is about hiding a wrong. It's not. Privacy is an inherent human right, and a requirement for maintaining the human condition with dignity and respect." -- Bruce Schneier
Re: Graphical installer on arm64 (netboot and cdrom)
On Mon, Apr 20, 2020 at 03:43:57PM +0100, Steve McIntyre wrote: >On Mon, Apr 20, 2020 at 03:21:20PM +0100, Steve McIntyre wrote: >>On Mon, Apr 20, 2020 at 05:03:02PM +0300, Alper Nebi Yasak wrote: >>>On 20/04/2020 16:36, Steve McIntyre wrote: I'm just going to test again with that change included, then I can push a netinst image somewhere for you to test... >>> >>>I'd appreciate it. Here's another patch, this time for the armhf graphical >>>cdrom. I checked that it boots into a graphical installer when run in a QEMU >>>arm VM (still with 'direct kernel boot') but no further. If you can also make >>>an armhf netinst image from this I can test that too (at least in a VM, not >>>sure the configs for my chromebook were enabled on the armhf kernel..). >> >>Ah, OK. I wasn't sure if it was worth trying to add this on armhf >>too... :-) >> >>I'm just building with a different local patch to add the setting >>GRAPHICAL_INSTALLER=y in arm64.cfg and using that to add (or not) the >>graphical installer to each of the grub-gencfg calls. I'll let that >>finish first... > >Try the image at > > http://cdimage.debian.org/cdimage/unofficial/arm64-gi/ > >please? OK, so this lot seems to work in a VM at least (thanks Marcin!), so I've pushed this set of patches to master now. I'm not sure about adding the graphical installer for armhf right now, but I'm open to being convinced... Once we have a working d-i daily build I'll also push my changes for debian-cd to use it on arm64. -- Steve McIntyre, Cambridge, UK.st...@einval.com "I can't ever sleep on planes ... call it irrational if you like, but I'm afraid I'll miss my stop" -- Vivek Das Mohapatra
Re: Graphical installer on arm64 (netboot and cdrom)
On 20/04/2020 19:35, Wookey wrote: On 2020-04-20 17:51 +0200, Marcin Juszkiewicz wrote: W dniu 20.04.2020 o 17:38, Steve McIntyre pisze: Does /dev/tty0 show up in /proc/consoles in your setup? We might need to tweak that yet... ~ # cat /proc/consoles ttyAMA0 -W- (EC p a) 204:64 What platform is this? The idea is that the kernel should know (better than DI) what the valid consoles are so we use that list (every 'enabled' console which is what the 'E' indicates). But you have a machine with no tty0, but it does have a framebuffer? Wookey It should be an aarch64 QEMU VM, I'm also seeing that behaviour there. Long story short, there is an ACPI Serial Port Console Redirection table specifying a serial console, Linux registers it as a preferred console very early (as a boot console first), and later when VT tries to register itself as a less-than-preferred console that request is ignored since there is already a preferred one already registered. There's nothing wrong with the framebuffer or tty0 at all.
Re: Graphical installer on arm64 (netboot and cdrom)
On 20/04/2020 18:38, Steve McIntyre wrote:
Does /dev/tty0 show up in /proc/consoles in your setup? We might need
to tweak that yet...
Here is a small but untested patch for rootskel's reopen-console for that.
(Thanks for the cd image, it'll probably take me until tomorrow to test
and report back on it)
>From 1713b6544d4950d2861710b48aff16b4b0a119af Mon Sep 17 00:00:00 2001
From: Alper Nebi Yasak
Date: Mon, 20 Apr 2020 19:27:18 +0300
Subject: [PATCH] Use /dev/tty0 as a console even if it's not in /proc/consoles
Signed-off-by: Alper Nebi Yasak
---
src/sbin/reopen-console-linux | 7 +++
1 file changed, 7 insertions(+)
diff --git a/src/sbin/reopen-console-linux b/src/sbin/reopen-console-linux
index 13b15a3..0816be4 100755
--- a/src/sbin/reopen-console-linux
+++ b/src/sbin/reopen-console-linux
@@ -78,6 +78,13 @@ do
fi
done
+# /dev/tty0 may not show up in /proc/consoles (at least on QEMU aarch64),
+# debian-installer should run on it anyway if it exists.
+if [ -c /dev/tty0 ] && ! { echo "$consoles" | grep -q "^tty0$"; }; then
+ consoles="${consoles:+$consoles$NL}tty0"
+ log " Adding tty0 to possible consoles list"
+fi
+
if [ -z "$consoles" ]; then
# Nothing found? Default to /dev/console.
log "Found no consoles! Defaulting to /dev/console"
--
2.26.1
Re: Graphical installer on arm64 (netboot and cdrom)
On 2020-04-20 17:51 +0200, Marcin Juszkiewicz wrote: > W dniu 20.04.2020 o 17:38, Steve McIntyre pisze: > > Does /dev/tty0 show up in /proc/consoles in your setup? We might need > > to tweak that yet... > > ~ # cat /proc/consoles > ttyAMA0 -W- (EC p a) 204:64 What platform is this? The idea is that the kernel should know (better than DI) what the valid consoles are so we use that list (every 'enabled' console which is what the 'E' indicates). But you have a machine with no tty0, but it does have a framebuffer? Wookey -- Principal hats: Linaro, Debian, Wookware, ARM http://wookware.org/ signature.asc Description: PGP signature
Re: Graphical installer on arm64 (netboot and cdrom)
On Mon, Apr 20, 2020 at 06:06:55PM +0200, Marcin Juszkiewicz wrote: >W dniu 20.04.2020 o 17:54, Steve McIntyre pisze: > >> OK. Can you edit the grub command line and add "console=tty0" before >> starting please? > >Now I have two d-i running. One on tty0, one on ttyAMA0: Yay! Progress - that's what we're aiming for. :-) You should be able to use either of them now - this is how we support multiple different hardware configurations. Can you use the one on tty0 OK? That's what I'm hoping to see here... -- Steve McIntyre, Cambridge, UK.st...@einval.com < Aardvark> I dislike C++ to start with. C++11 just seems to be handing rope-creating factories for users to hang multiple instances of themselves.
Re: Graphical installer on arm64 (netboot and cdrom)
W dniu 20.04.2020 o 17:54, Steve McIntyre pisze:
> OK. Can you edit the grub command line and add "console=tty0" before
> starting please?
Now I have two d-i running. One on tty0, one on ttyAMA0:
Apr 20 16:04:09 entropy-source: haveged not needed: rng detected
Apr 20 16:04:10 reopen-console: Looking at console tty0 from /proc/consoles
Apr 20 16:04:10 reopen-console:Adding tty0 to possible consoles list
Apr 20 16:04:10 reopen-console:tty0 is preferred
Apr 20 16:04:10 reopen-console: Looking at console ttyAMA0 from /proc/consoles
Apr 20 16:04:10 reopen-console:Adding ttyAMA0 to possible consoles list
Apr 20 16:04:10 reopen-console: Adding inittab entry for tty0
Apr 20 16:04:10 reopen-console: Adding inittab entry for ttyAMA0
Apr 20 16:04:10 reopen-console: Restarting init to start d-i on the console(s)
we found
Apr 20 16:04:10 init: reloading /etc/inittab
Apr 20 16:04:10 init: starting pid 271, tty '/dev/tty4': '/usr/bin/tail -f
/var/log/syslog'
Apr 20 16:04:10 init: starting pid 275, tty '/dev/tty0':
'/sbin/debian-installer'
Apr 20 16:04:10 init: starting pid 276, tty '/dev/ttyAMA0':
'/sbin/debian-installer'
Apr 20 16:04:11 debconf: Setting debconf/language to en
Apr 20 16:04:11 main-menu[312]: INFO: Falling back to the package description
for brltty-udeb
Apr 20 16:04:11 main-menu[312]: INFO: Menu item 'localechooser' selected
Apr 20 16:04:12 init: process '/sbin/debian-installer' (pid 275) exited.
Scheduling for restart.
Apr 20 16:04:12 init: starting pid 326, tty '/dev/tty0':
'/sbin/debian-installer'
Apr 20 16:04:13 debconf: Setting debconf/language to en
Apr 20 16:04:14 debconf: Setting debconf/language to en
Apr 20 16:04:14 main-menu[398]: INFO: Falling back to the package description
for brltty-udeb
Apr 20 16:04:15 main-menu[398]: INFO: Menu item 'localechooser' selected
Apr 20 16:04:22 localechooser: info: Language = 'en'
Apr 20 16:04:22 localechooser: info: line=en;0;US;en_US.UTF-8;;console-setup
Apr 20 16:04:22 localechooser: info: Set debian-installer/language = 'en'
Apr 20 16:04:22 localechooser: info: Default country = 'US'
Apr 20 16:04:22 localechooser: info: Default locale = 'en_US.UTF-8'
Apr 20 16:04:22 localechooser: info: Set debian-installer/consoledisplay =
'console-setup'
Apr 20 16:04:22 debconf: Setting debconf/language to en
Apr 20 16:04:23 localechooser: info: Set debian-installer/country = 'US'
Apr 20 16:04:23 debconf: Setting debconf/language to en
Apr 20 16:04:24 gtk-set-font: Switching to font 'DejaVu Sans' for 'en'
Apr 20 16:04:25 localechooser: info: Set debian-installer/locale = 'en_US.UTF-8'
Apr 20 16:04:25 localechooser: info: System locale (debian-installer/locale) =
'en_US.UTF-8'
Apr 20 16:04:26 main-menu[312]: INFO: Falling back to the package description
for brltty-udeb
Apr 20 16:04:26 main-menu[312]: INFO: Falling back to the package description
for brltty-udeb
Apr 20 16:04:26 main-menu[312]: INFO: Falling back to the package description
for brltty-udeb
Apr 20 16:04:26 main-menu[312]: INFO: Menu item 'brltty-udeb' selected
Apr 20 16:04:26 main-menu[312]: WARNING **: Unable to set title for brltty-udeb.
Apr 20 16:04:26 main-menu[312]: INFO: Falling back to the package description
for brltty-udeb
Apr 20 16:04:26 main-menu[312]: INFO: Falling back to the package description
for brltty-udeb
Apr 20 16:04:26 main-menu[312]: INFO: Menu item 'console-setup-udeb' selected
Apr 20 16:04:54 main-menu[312]: INFO: Menu item 'console-setup-udeb' succeeded
but requested to be left unconfigured.
Apr 20 16:04:54 main-menu[312]: INFO: Falling back to the package description
for brltty-udeb
Apr 20 16:04:56 main-menu[312]: INFO: Falling back to the package description
for brltty-udeb
Apr 20 16:04:56 main-menu[312]: INFO: Menu item 'di-utils-shell' selected
168 root 0 IW [kworker/u4:2]
205 root 2228 S/sbin/syslogd -m 0 -O /var/log/syslog -S
207 root 2228 S/sbin/klogd -c 2
268 root 0 IW< [kworker/0:1H]
269 root 2228 S/bin/busybox init
270 root 2228 S/bin/busybox init
271 root 2228 S/usr/bin/tail -f /var/log/syslog
276 root 2228 S{debian-installe} /bin/sh /sbin/debian-installer
304 root 94160 SXorg -noreset -nolisten tcp
305 root 11196 Sdebconf -o d-i /usr/bin/main-menu
312 root 2112 S/usr/bin/main-menu
326 root 2228 S{debian-installe} /bin/sh /sbin/debian-installer
391 root 112m Sdebconf -o d-i /usr/bin/main-menu
398 root 2112 S/usr/bin/main-menu
405 root 2172 Sudpkg --configure --force-configure localechooser
406 root 2228 S{localechooser.p} /bin/sh -e /var/lib/dpkg/info/loca
407 root 2344 S{localechooser} /bin/sh /usr/bin/localechooser
1610 root 2172 Sudpkg --configure --force-configure di-utils-shell
1611 root 2228 S{di-utils-shell.} /bin/sh /var/lib/dpkg/info/di-util
1612 root 2228 S{start-shell} /bin/sh /bin/start-shell di-utils-shel
1613
Re: Graphical installer on arm64 (netboot and cdrom)
On Mon, Apr 20, 2020 at 05:51:03PM +0200, Marcin Juszkiewicz wrote: >W dniu 20.04.2020 o 17:38, Steve McIntyre pisze: >> Hey Marcin! >> >> On Mon, Apr 20, 2020 at 05:36:30PM +0200, Marcin Juszkiewicz wrote: >>> W dniu 20.04.2020 o 16:43, Steve McIntyre pisze: >>> Try the image at http://cdimage.debian.org/cdimage/unofficial/arm64-gi/ >>> >>> Booted VM with it. Debian installer started on serial port still >>> despite selecting 'graphical install' in grub menu. >>> >>> Graphical display in meantime displayed only blinking cursor. >>> >>> Maybe it was because on aarch64 framebuffer is available after >>> 'virtio_gpu' kernel module gets loaded so d-i starts too early >>> to notice it. >> >> Does /dev/tty0 show up in /proc/consoles in your setup? We might need >> to tweak that yet... > >~ # cat /proc/consoles >ttyAMA0 -W- (EC p a) 204:64 >~ # > >Syslog: > >Apr 20 15:41:17 entropy-source: haveged not needed: rng detected >Apr 20 15:41:18 reopen-console: Looking at console ttyAMA0 from /proc/consoles >Apr 20 15:41:18 reopen-console:Adding ttyAMA0 to possible consoles list >Apr 20 15:41:18 reopen-console:ttyAMA0 is preferred >Apr 20 15:41:18 reopen-console: Adding inittab entry for ttyAMA0 >Apr 20 15:41:18 reopen-console: Restarting init to start d-i on the console(s) >we found >Apr 20 15:41:18 init: reloading /etc/inittab >Apr 20 15:41:18 init: starting pid 261, tty '/dev/tty4': '/usr/bin/tail -f >/var/log/syslog' >Apr 20 15:41:18 init: starting pid 265, tty '/dev/ttyAMA0': >'/sbin/debian-installer' >Apr 20 15:41:19 debconf: Setting debconf/language to en >Apr 20 15:41:20 main-menu[284]: INFO: Falling back to the package description >for brltty-udeb >Apr 20 15:41:20 main-menu[284]: INFO: Menu item 'localechooser' selected >Apr 20 15:41:21 debconf: Setting debconf/language to >Apr 20 15:41:23 main-menu[284]: INFO: Menu item 'localechooser' succeeded but >requested to be left unconfigured. >Apr 20 15:41:23 main-menu[284]: INFO: Falling back to the package description >for brltty-udeb >Apr 20 15:41:25 main-menu[284]: INFO: Falling back to the package description >for brltty-udeb >Apr 20 15:41:25 main-menu[284]: INFO: Menu item 'di-utils-shell' selected > >Just before d-i started on serial line there was some message >about missing framebuffer. OK. Can you edit the grub command line and add "console=tty0" before starting please? -- Steve McIntyre, Cambridge, UK.st...@einval.com Who needs computer imagery when you've got Brian Blessed?
Re: Graphical installer on arm64 (netboot and cdrom)
W dniu 20.04.2020 o 17:38, Steve McIntyre pisze: > Hey Marcin! > > On Mon, Apr 20, 2020 at 05:36:30PM +0200, Marcin Juszkiewicz wrote: >> W dniu 20.04.2020 o 16:43, Steve McIntyre pisze: >> >>> Try the image at >>> >>> http://cdimage.debian.org/cdimage/unofficial/arm64-gi/ >> >> Booted VM with it. Debian installer started on serial port still >> despite selecting 'graphical install' in grub menu. >> >> Graphical display in meantime displayed only blinking cursor. >> >> Maybe it was because on aarch64 framebuffer is available after >> 'virtio_gpu' kernel module gets loaded so d-i starts too early >> to notice it. > > Does /dev/tty0 show up in /proc/consoles in your setup? We might need > to tweak that yet... ~ # cat /proc/consoles ttyAMA0 -W- (EC p a) 204:64 ~ # Syslog: Apr 20 15:41:17 entropy-source: haveged not needed: rng detected Apr 20 15:41:18 reopen-console: Looking at console ttyAMA0 from /proc/consoles Apr 20 15:41:18 reopen-console:Adding ttyAMA0 to possible consoles list Apr 20 15:41:18 reopen-console:ttyAMA0 is preferred Apr 20 15:41:18 reopen-console: Adding inittab entry for ttyAMA0 Apr 20 15:41:18 reopen-console: Restarting init to start d-i on the console(s) we found Apr 20 15:41:18 init: reloading /etc/inittab Apr 20 15:41:18 init: starting pid 261, tty '/dev/tty4': '/usr/bin/tail -f /var/log/syslog' Apr 20 15:41:18 init: starting pid 265, tty '/dev/ttyAMA0': '/sbin/debian-installer' Apr 20 15:41:19 debconf: Setting debconf/language to en Apr 20 15:41:20 main-menu[284]: INFO: Falling back to the package description for brltty-udeb Apr 20 15:41:20 main-menu[284]: INFO: Menu item 'localechooser' selected Apr 20 15:41:21 debconf: Setting debconf/language to Apr 20 15:41:23 main-menu[284]: INFO: Menu item 'localechooser' succeeded but requested to be left unconfigured. Apr 20 15:41:23 main-menu[284]: INFO: Falling back to the package description for brltty-udeb Apr 20 15:41:25 main-menu[284]: INFO: Falling back to the package description for brltty-udeb Apr 20 15:41:25 main-menu[284]: INFO: Menu item 'di-utils-shell' selected Just before d-i started on serial line there was some message about missing framebuffer.
Re: Graphical installer on arm64 (netboot and cdrom)
Hey Marcin! On Mon, Apr 20, 2020 at 05:36:30PM +0200, Marcin Juszkiewicz wrote: >W dniu 20.04.2020 o 16:43, Steve McIntyre pisze: > >> Try the image at >> >> http://cdimage.debian.org/cdimage/unofficial/arm64-gi/ > >Booted VM with it. Debian installer started on serial port still >despite selecting 'graphical install' in grub menu. > >Graphical display in meantime displayed only blinking cursor. > >Maybe it was because on aarch64 framebuffer is available after >'virtio_gpu' kernel module gets loaded so d-i starts too early >to notice it. Does /dev/tty0 show up in /proc/consoles in your setup? We might need to tweak that yet... -- Steve McIntyre, Cambridge, UK.st...@einval.com Armed with "Valor": "Centurion" represents quality of Discipline, Honor, Integrity and Loyalty. Now you don't have to be a Caesar to concord the digital world while feeling safe and proud.
Re: Graphical installer on arm64 (netboot and cdrom)
W dniu 20.04.2020 o 16:43, Steve McIntyre pisze: > Try the image at > > http://cdimage.debian.org/cdimage/unofficial/arm64-gi/ Booted VM with it. Debian installer started on serial port still despite selecting 'graphical install' in grub menu. Graphical display in meantime displayed only blinking cursor. Maybe it was because on aarch64 framebuffer is available after 'virtio_gpu' kernel module gets loaded so d-i starts too early to notice it.
Re: Graphical installer on arm64 (netboot and cdrom)
On Mon, Apr 20, 2020 at 03:21:20PM +0100, Steve McIntyre wrote: >On Mon, Apr 20, 2020 at 05:03:02PM +0300, Alper Nebi Yasak wrote: >>On 20/04/2020 16:36, Steve McIntyre wrote: >>> I'm just going to test again with that change included, then I can >>> push a netinst image somewhere for you to test... >> >>I'd appreciate it. Here's another patch, this time for the armhf graphical >>cdrom. I checked that it boots into a graphical installer when run in a QEMU >>arm VM (still with 'direct kernel boot') but no further. If you can also make >>an armhf netinst image from this I can test that too (at least in a VM, not >>sure the configs for my chromebook were enabled on the armhf kernel..). > >Ah, OK. I wasn't sure if it was worth trying to add this on armhf >too... :-) > >I'm just building with a different local patch to add the setting >GRAPHICAL_INSTALLER=y in arm64.cfg and using that to add (or not) the >graphical installer to each of the grub-gencfg calls. I'll let that >finish first... Try the image at http://cdimage.debian.org/cdimage/unofficial/arm64-gi/ please? -- Steve McIntyre, Cambridge, UK.st...@einval.com "Because heaters aren't purple!" -- Catherine Pitt
Re: Graphical installer on arm64 (netboot and cdrom)
On Mon, Apr 20, 2020 at 05:03:02PM +0300, Alper Nebi Yasak wrote: >On 20/04/2020 16:36, Steve McIntyre wrote: >> I'm just going to test again with that change included, then I can >> push a netinst image somewhere for you to test... > >I'd appreciate it. Here's another patch, this time for the armhf graphical >cdrom. I checked that it boots into a graphical installer when run in a QEMU >arm VM (still with 'direct kernel boot') but no further. If you can also make >an armhf netinst image from this I can test that too (at least in a VM, not >sure the configs for my chromebook were enabled on the armhf kernel..). Ah, OK. I wasn't sure if it was worth trying to add this on armhf too... :-) I'm just building with a different local patch to add the setting GRAPHICAL_INSTALLER=y in arm64.cfg and using that to add (or not) the graphical installer to each of the grub-gencfg calls. I'll let that finish first... -- Steve McIntyre, Cambridge, UK.st...@einval.com "We're the technical experts. We were hired so that management could ignore our recommendations and tell us how to do our jobs." -- Mike Andrews
Re: Graphical installer on arm64 (netboot and cdrom)
On 20/04/2020 16:36, Steve McIntyre wrote:
I'm just going to test again with that change included, then I can
push a netinst image somewhere for you to test...
I'd appreciate it. Here's another patch, this time for the armhf
graphical cdrom. I checked that it boots into a graphical installer when
run in a QEMU arm VM (still with 'direct kernel boot') but no further.
If you can also make an armhf netinst image from this I can test that
too (at least in a VM, not sure the configs for my chromebook were
enabled on the armhf kernel..).
>From b194a1f9d4619eceb42e355d469c7cd8b54992f7 Mon Sep 17 00:00:00 2001
From: Alper Nebi Yasak
Date: Mon, 20 Apr 2020 16:50:07 +0300
Subject: [PATCH] Add modules and build files for armhf graphical installer
cdrom
Signed-off-by: Alper Nebi Yasak
---
build/config/armhf/cdrom.cfg | 2 +-
build/config/armhf/cdrom/gtk.cfg | 19 +++
build/pkg-lists/cdrom/grub/gtk/armhf.cfg | 11 +++
3 files changed, 31 insertions(+), 1 deletion(-)
create mode 100644 build/config/armhf/cdrom/gtk.cfg
create mode 100644 build/pkg-lists/cdrom/grub/gtk/armhf.cfg
diff --git a/build/config/armhf/cdrom.cfg b/build/config/armhf/cdrom.cfg
index 2a6fafd77..68cc87078 100644
--- a/build/config/armhf/cdrom.cfg
+++ b/build/config/armhf/cdrom.cfg
@@ -1,4 +1,4 @@
# el-torito is too large at the moment, so is disabled.
-FLAVOUR_SUPPORTED = grub
+FLAVOUR_SUPPORTED = grub gtk
MEDIA_TYPE = CD-ROM
diff --git a/build/config/armhf/cdrom/gtk.cfg b/build/config/armhf/cdrom/gtk.cfg
new file mode 100644
index 0..76024e2f1
--- /dev/null
+++ b/build/config/armhf/cdrom/gtk.cfg
@@ -0,0 +1,19 @@
+TARGET = $(INITRD) $(KERNEL) $(DEBIAN_CD_INFO)
+
+MANIFEST-KERNEL = "kernel for use with EFI to build a CD (graphical)"
+MANIFEST-INITRD = "initrd for use with EFI to build a CD (graphical)"
+MANIFEST-DEBIAN_CD_INFO = "EFI config files for CD (graphical)"
+
+TYPE = cdrom/grub/gtk
+
+EXTRANAME = gtk/
+
+IS_PURE_GTK = 1
+
+KEEP_GI_LANGS = 1
+
+VIDEO_MODE=$(VIDEO_MODE_GTK)
+
+# All images that include cdebconf should include symbols needed by these
+# plugins.
+EXTRAUDEBS += cdebconf-gtk-entropy
diff --git a/build/pkg-lists/cdrom/grub/gtk/armhf.cfg b/build/pkg-lists/cdrom/grub/gtk/armhf.cfg
new file mode 100644
index 0..bda77cdab
--- /dev/null
+++ b/build/pkg-lists/cdrom/grub/gtk/armhf.cfg
@@ -0,0 +1,11 @@
+#include "gtk-linux"
+
+#mouse-modules-${kernel:Version}
+event-modules-${kernel:Version}
+xserver-xorg-input-evdev-udeb
+xserver-xorg-video-fbdev-udeb
+
+#speakup-modules-${kernel:Version}
+#sound-modules-${kernel:Version}
+#console-setup-linux-fonts-udeb
+#espeakup-udeb
--
2.26.1
Re: Graphical installer on arm64 (netboot and cdrom)
On Sun, Apr 19, 2020 at 10:23:06PM +0300, Alper Nebi Yasak wrote:
>On 16/04/2020 15:40, Steve McIntyre wrote:
>> On Tue, Apr 14, 2020 at 05:43:36PM +0100, Steve McIntyre wrote:
>> >
>> > ACK.
>> >
>> > Building locally to test here...
>>
>> And I have a build that looks OK by eye. Unfortunately, my local test
>> machine (Macchiatobin) seems to be dying and I can't test this
>> effectively now. :-(
>
>Ah, OK. Thanks for spending time on this.
>
>> It needs some tiny debian-cd changes and then we'll get
>> netinst, DVD images etc. also including the graphical installer. Final
>> thing missing - the grub.cfg that's generated for the CD/DVD/USB boot
>> doesn't include menu entries for graphical boot.
>Adding INITRD_GTK to build/config/arm.cfg as in:
>
>diff --git a/build/config/arm.cfg b/build/config/arm.cfg
>index fe8cf80f9..898795658 100644
>--- a/build/config/arm.cfg
>+++ b/build/config/arm.cfg
>@@ -23,6 +23,7 @@ arch_cd_info_dir: arm_grub_efi
> grub-gencfg \
> KERNEL /%install%/vmlinuz \
> INITRD /%install%/initrd.gz \
>+ INITRD_GTK /%install%/gtk/initrd.gz \
> HEADER boot/$(ARCH)/grub/grub-efi.cfg \
> > $(TEMP_CD_INFO_DIR)/grub/grub.cfg; \
> cp -a $(GRUB_FONT) $(TEMP_CD_INFO_DIR)/grub/font.pf2; \
>
>seems to be enough for the last part, I'm getting "Graphical install" and
>others in both cdrom{,/gtk}/debian-cd_info.tar.gz files' grub.cfg files.
>
>I expect that change will make the "Graphical" entries appear also on armhf
>where there isn't a cdrom/gtk build yet, so I'll also have a look at that.
>
>Hopefully I can learn enough debian-cd to build and test with proper images
>this time around :)
I'm just going to test again with that change included, then I can
push a netinst image somewhere for you to test...
--
Steve McIntyre, Cambridge, UK.st...@einval.com
"When C++ is your hammer, everything looks like a thumb." -- Steven M. Haflich
