Hi,
On 2025-04-27 23:04 +03:00, Cyril Brulebois wrote:
> Alper Nebi Yasak (2025-04-27):
>> In the latest build where that partition.img exists [1], I see the
>> resulting SD card image is almost full (2.1 MiB free / 128.5 MiB) and is
>> built with the 6.12.22 kernel udeb
Hi,
On 2025-04-27 21:28 +03:00, Cyril Brulebois wrote:
> Hi,
>
> I can't investigate on my own, at least not right away, but d-i no
> longer (daily-)builds on arm64, with the netboot target breaking at:
>
> [...]
> gen-hd-image -v -z -p 32768 -b partition -s "15" -i
> "./tmp/netboot
Hello,
On 2024-12-28 13:51 +03:00, Cyril Brulebois wrote:
> Hi!
>
> Kentaro HAYASHI (2024-12-28):
>> * What led up to the situation?
>>
>> According to README [1], to know a list of available targets,
>> need to execute "make", but it takes huge amount of times.
>>
>> * What exactly did you
Hi,
On 26/06/2023 20:14, Holger Wansing wrote:
> Holger Wansing wrote (Wed, 14 Dec 2022 22:21:42 +0100):
>> Am 14. Dezember 2022 16:50:58 MEZ schrieb Alper Nebi Yasak
>> :
>>> So if I understand it right, things will go mostly in this flow:
>>>
>>>
On 01/06/2023 16:27, Emanuele Rocca wrote:
> Hi again,
>
> On 2023-05-31 05:46, Samuel Thibault wrote:
>> The problem is that both are frown-prone. I guess there is a reason why
>> on arm the default console is set to the serial port, e.g. for simpler
>> debugging or something like that.
>
> Also
Hi again,
On 03/12/2022 23:45, Alper Nebi Yasak wrote:
> I've been trying to make Debian easier to install and use on Chromebooks
> by adding integration to support their stock firmware/bootloader.
>
> [...]
>
> AFAICT the next steps after this are modifying the deb
On 15/12/2022 00:21, Holger Wansing wrote:
> Am 14. Dezember 2022 16:50:58 MEZ schrieb Alper Nebi Yasak
> :
>> So if I understand it right, things will go mostly in this flow:
>>
>> - depthcharge-tools-installer and partman-cross pass NEW review
>> - Holger uploads
Hi,
On 24/12/2022 21:57, Thorsten Alteholz wrote:
> Hi,
>
> did anybody approve the new udeb?
>
> Thorsten
Kibi sponsored it [1] (and another udeb-only src:partman-cros). I've
been assuming that would count and be enough, is it not? Anything else I
need(ed) to do?
[1] Debian Installer support
(Bcc:'ed to debian-boot@)
On 10/12/2022 16:27, Bastian Blank wrote:
> Our documented, I think, policy is, that we don't support loading new
> modules into an old kernel within the same ABI. This forces a reboot
> after kernel installation.
>
> However in a lot of cases this just worked. You cou
On 13/12/2022 22:36, Holger Wansing wrote:
> Ah, yes, you are right.
> I mixed things up here:
> those packages will come into unstable, if they are processed by ftpmaster in
> NEW queue.
> But they will then not migrate to testing automatically.
> For that, a source-only upload is needed.
>
> Ok
On 12/12/2022 03:15, Cyril Brulebois wrote:
> I've glanced at depthcharge-tools-installer and while I'm no debconf
> expert and I can't assess the postinst with high certainty, the overall
> impression was good enough for me to sign and upload; I did change the
> Maintainer to debian-boot@ (same as
On 04/12/2022 14:49, Holger Wansing wrote:
> Since the packages contain translatable material, my 2 cents here:
> I would propose to *not* add the new packages to the l10n machinery
> before the release of bookworm, given were are late in the development
> cycle.
> Means, the new packages would be
On 04/12/2022 00:08, Cyril Brulebois wrote:
> Alper Nebi Yasak (2022-12-03):
>> I'd like these two udebs to be sponsored. [...]
>
> I don't think that's going to be an issue timing-wise. To be fair, if they
> aren't perfect yet by the time the release h
Hi,
I've been trying to make Debian easier to install and use on Chromebooks
by adding integration to support their stock firmware/bootloader. The
major part of that work is 'depthcharge-tools' which manages
bootloader-specific stuff and kernel/initramfs upgrade hooks, recently
sponsored and now i
On 17/01/2021 12:10, John Paul Adrian Glaubitz wrote:
> Hello Alper!
>
> On 1/17/21 10:02 AM, Alper Nebi Yasak wrote:
>> Hope this is a good time to ask for this again, this time with a better
>> email subject.
>
> Is someone working to fix this bug in the kernel
On 22/12/2020 00:18, Alper Nebi Yasak wrote:
> On 02/12/2020 04:03, Cyril Brulebois wrote:
>> Alper Nebi Yasak (2020-12-01):
>>> There's a tiny unreleased change in the rootskel package that fixes d-i
>>> not launching on the framebuffer on arm64 QEMU machines [1
On 02/12/2020 04:03, Cyril Brulebois wrote:
> Alper Nebi Yasak (2020-12-01):
>> There's a tiny unreleased change in the rootskel package that fixes d-i
>> not launching on the framebuffer on arm64 QEMU machines [1], can that be
>> also included in the next alpha?
>
On 15/12/2020 20:17, Samuel Thibault wrote:
> Wang Shanker, le mer. 16 déc. 2020 01:05:58 +0800, a ecrit:
>> I carried out a simple test by limiting memory of my qemu machine
>> and appending `lowmem=2` to the kernel command line. I can confirm
>> that btrem and its font file get deleted.
>
> Ok,
On 12/12/2020 12:45, Shawn Guo wrote:
> On Sat, Dec 12, 2020 at 9:23 AM Cyril Brulebois wrote:
>> Alper Nebi Yasak (2020-12-11):
>>> Cyril: Shawn has filed a MR [1] on salsa to change arm64 cdrom gtk build
>>> from/to using xserver-xorg-input-{evdev->libinput}-ude
(Subject was: "Re: Missing libgudev-1.0-0 udeb package?")
On 11/12/2020 04:22, Shawn Guo wrote:
> On Thu, Dec 10, 2020 at 11:21 PM Timo Aaltonen wrote:
It seems that there is no libgudev-1.0-0 udeb at all, while it becomes
a dependency of xserver-xorg-input-libinput-udeb like below.
>>>
On 09/12/2020 02:15, Ryutaroh Matsumoto wrote:
> Hi Alper, thank you for paying attention.
>
>> On that specific question, you use the arrow keys to navigate between
>
> Neither the space bar nor arrow keys worked for me with Alpha 3...
I tried running it under different terminals (tmux, xfce4-t
On 07/12/2020 23:23, Holger Wansing wrote:
> Alper Nebi Yasak wrote:
>> I've tried debian-bullseye-DI-alpha3-arm64-netinst.iso on a QEMU VM, the
>> gtk installer refused to run with less than 578MiB (falling back to
>> newt). I could successfully go through the rest of
On 08/12/2020 13:30, Marcin Juszkiewicz wrote:
> W dniu 08.12.2020 o 11:13, Alper Nebi Yasak pisze:
>> On 08/12/2020 12:26, Marcin Juszkiewicz wrote:
>
>>> Both standard and graphical installer contain kernel modules for virtio
>>> framebuffer. And both ignore vi
On 08/12/2020 12:26, Marcin Juszkiewicz wrote:
> W dniu 08.12.2020 o 09:06, Ryutaroh Matsumoto pisze:
>> Hi Debian Arm users,
>>
>> I tried Bullseye d-i Alpha3 released on December 6 for
>> building a qemu disk image usable by qemu-system-aarch64.
>> To me, Alpha 3 d-i seems almost unusable for tha
Control: severity -1 normal
On 08/12/2020 10:59, Ryutaroh Matsumoto wrote:
> Dear Maintainer,
> As I reported at
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976807
> Bullseye arm64 d-i does not provide graphical installation
> to QEMU VMs. So I tried text-based installation. The
> installe
On 08/12/2020 10:33, Ryutaroh Matsumoto wrote:
> I tried to use Debian Bullseye arm64 d-i Alpha 3 to install Bullseye
> to a QEMU disk. I tried -device ramfb and -device virtio-gpu-pic
> for graphical installation by d-i Alpha 3. But neither of them were
> used by the Alpha 3 installer and text-bas
On 07/12/2020 19:57, john doe wrote:
> On 12/7/2020 5:18 PM, Alper Nebi Yasak wrote:
>> On 06/12/2020 23:11, Holger Wansing wrote:
>>> +
>>> +
>>> +For this architecture the &d-i; supports two different user interfaces: a
>>> +graphical one and
On 06/12/2020 23:11, Holger Wansing wrote:
> Hi,
>
> I read in alpha3 release-notes about the activation of the graphical
> installer for arm64.
>
> This needs to be documented in the installation-guide then.
>
> I have prepared a first patch for this, attached.
>
> There are two points remaini
Hello,
On 01/12/2020 04:36, Cyril Brulebois wrote:
> [...]
>
> And since I'm considering getting an updated console-setup into testing, I
> might try and squeeze the latest linux update into that release as well,
> provided it's otherwise ready to migrate when it reaches 5/5 days.
There's a tiny
On 01/11/2020 03:05, jeanneige666777888 wrote:
> Also I just noticed that pressing alt+F2 to F4 on my keyboard actually allows
> me to access the virtual terminals but I guess they are not handled by Debian
> Installer.
> Another weird behavior is that for virtual terminal 1, the HDMI output only
On 29/08/2020 12:58, Frank Mankel wrote:
Hello,
I have used these images for my RockPro64 in the past. But currently I
get a 404, am I looking in the wrong place?
With kind regards
Frank
https://d-i.debian.org/daily-images/arm64/daily/netboot/SD-card-images/
The daily images are frequently
On 06/08/2020 03:04, Forest wrote:
I used the installer image from over a week ago, because d-i.debian.org has
no newer daily images.
That happens frequently, as when the kernel is updated in the archive
the installer sources have to be manually updated to build for/with the
new kernel. The o
Hi, I just wanted to remind you of some patches I sent a while back. Do
you (or anyone else) have time to comment on / review / merge them?
On 19/05/2020 17:17, Alper Nebi Yasak wrote:
So I tested my earlier patch, and did a bit more. I've attached three
patches, first two for debian-inst
Control: reassign -1 debian-installer
Control: severity -1 normal
Control: retitle -1 Include drm modules in non-gtk arm64 cdrom initrds
Control: tag -1 patch
On 26/05/2020 20:40, Marcin Juszkiewicz wrote:
There are two initrds in that iso, 'install.a64/initrd.gz' doesn't
have drm modules, but t
On 22/05/2020 15:22, Holger Wansing wrote:
in the installation-guide, arm64 has the "bootable-usb" option set.
That leads to this chapter being included in the manual:
https://d-i.debian.org/doc/installation-guide/en.arm64/ch04s03.html
Is this true for arm64?
When I write netboot mini.iso imag
On 20/04/2020 19:36, 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.
I don't think this (hav
On 13/05/2020 03:43, Punit Agrawal wrote:
Incidentally, this does not work if '-m 1024' is missing. Kernel boot
fails to find 'init'. I suspect that the Qemu default RAM configuration
is not sufficient to unpack the initrd.
Thanks, that's it. I haven't noticed it the first time around because I
On 12/05/2020 13:02, Punit Agrawal wrote:
The above parameters do not launch the installer from the iso here. I am
not quite sure what the right arguments are. I wonder if
"root=" to the kernel will do the trick. Will give that a
try.
When I try:
$ qemu-system-x86_64 -cdrom *.iso -nographic -v
On 26/04/2020 05:54, Paul Wise wrote:
ISTR that CCing Andrew Morton can help get
patches into Linux if the maintainers of the code in question do not
reply. I suggest you try that after you fix the issue pointed out by
the bot.
Thanks! Do you mean CCing at the version with the fix, or at furth
On 21/04/2020 15:42, Wookey wrote:
One thought - can we just perhaps use /dev/console 'anyway' and
that'll get us the right thing even when tty0 has not been properly
enabled when it should have been? (I've forgotten how all this works
and would need to go read the runes again, and most of my tes
On 21/04/2020 14:14, Alper Nebi Yasak wrote:
Since you've already pushed to master, I'll try to do a full
installation once daily cdroms are available.
I've tested with today's (2020-04-27) weekly-built
debian-testing-arm64-xfce-CD-1.iso on my chromebook. Overall
On 20/04/2020 20:22, Steve McIntyre wrote:
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&#
On 20/04/2020 20:01, Steve McIntyre wrote:
On Mon, Apr 20, 2020 at 03:43:57PM +0100, Steve McIntyre wrote:
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 ma
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
b42e355d469c7cd8b54992f7 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/armh
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 no
On 06/04/2020 17:48, Steve McIntyre wrote:
Alper Nebi Yasak:
- added event-modules to arm64 netboot-gtk
- commented-out serial-modules from arm64 netboot
So why comment out the serial modules here? Do they cause a problem?
The "serial-modules" udeb isn't built on arm64 yet a
Jan 2019 03:13:40 +
Subject: [PATCH 2/3] Add missing modules (usb, fat, virtio) to arm64 netboot
build and xorg modules to netbook-gtk
Alper Nebi Yasak:
- added event-modules to arm64 netboot-gtk
- commented-out serial-modules from arm64 netboot
Signed-off-by: Alper Nebi Yasak
---
build/pkg-li
On 03/03/2020 18:51, Cyril Brulebois wrote:
partman-* is of course fine for udebs shipping partman stuff, but
depthcharge-support-installer strikes me as something that could be
named depthcharge-support-udeb, or maybe just depthcharge-udeb?
I mimicked the flash-kernel & flash-kernel-installer
I've uploaded a new version of depthcharge-tools to mentors.debian.net.
General changes:
- New upstream release v0.3.1, set version to 0.3.1-1
- Use *.{service,init} symlinks to install systemd/init.d files
- Export build-configuration variables in debian/rules
- Change GPL-2.0+ to GPL-2+ in debi
On 07/02/2020 17:31, Andrej Shadura wrote:
Same here as with #950717: how about talking to the DI team and
team-maintaining it and hosting it under
https://salsa.debian.org/installer-team?
That would be great. I'm not part of the installer team, but I'm willing
to join. (Any formal process to
On 07/02/2020 17:23, Andrej Shadura wrote:
How about talking to the DI team and team-maintaining it and hosting it
under https://salsa.debian.org/installer-team?
I think that's the best way to do it, especially for this package (as
other partman-* packages are).
Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: debian-boot@lists.debian.org
Dear mentors,
I am looking for a sponsor for my package "depthcharge-tools":
* Package name: depthcharge-tools
Version : 0.3.0-1
Upstream Author : Alper Nebi Yas
Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: debian-boot@lists.debian.org
Dear mentors,
I am looking for a sponsor for my package "partman-cros":
* Package name: partman-cros
Version : 1
Upstream Author : Alper Nebi Yasak
* URL
On 30/01/2020 16:43, Ben Hutchings wrote:
Oh, right, then I misunderstood what you were doing. I don't
understand how the two templates work together, so it may well be that
the first version was OK.
I don't really grok debconf, but from what I can tell:
1. at build-time, x may be set differe
can't install the compressor package.
Attaching a series of two patch files to replace the previous one. Hope
they resolve your concerns.
[0] quiet console=tty0 priority=critical \
base-installer/initramfs-tools/compression=git \
base-installer/kernel/linux/initramfs-tools/compr
/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
>From 2864137a59bcfbc957a7e8960b65e3e39977106a Mon Sep 17 00:00:00 2001
From: Alper Nebi Yasak
Date: Mon, 27 Jan 2020 21:16:10 +0300
Subject: [PATCH] Support configuring initramfs compression
Some machines/bootloaders do not
On 06/01/2020 23:48, andreimpope...@gmail.com wrote:
Ok, will look into it at some point. It seems Arch have a working kernel
for it.
Yeah, they have board-specific kernels built from Chrome OS sources.
Those could be a starting point, but other people might have tried first
and have more up-
On 05/01/2020 23:30, Andrei POPESCU wrote:
I'd be interested to test this on the Acer Chromebook R13 (elm).
Where / how do I start?
From what I can find on the internet: it doesn't look like mainline
Linux works on elm yet and Debian arm64 kernel doesn't even have
CONFIG_ARCH_MEDIATEK (and p
I've been working on getting Debian installer to run on my chromebook
(kevin) for a while and I've also tested Wookey's patches [1] for
enabling the graphical parts. The inputs didn't work with just those
udebs as reported then, but adding 'event-modules-${kernel:Version}' as
well to the pkg-li
On Thu, 23 May 2019 10:36:15 -0700 Vagrant Cascadian wrote:
Untested and refreshed patch against current git attached.
I wanted to extend this, but I ended up almost completely rewriting it:
https://salsa.debian.org/installer-team/flash-kernel/merge_requests/15/
Instead of only using a compres
On Tue, 13 Feb 2018 01:03:43 + Ben Hutchings wrote:
Now that I think about it, initramfs-tools does allow other packages to
override the configuration for mkinitramfs through shell scripts in
/usr/share/initramfs-tools/conf-hooks.d. This seems like a good reason
to do that.
I've recently i
Hi, I have been working on getting flash-kernel to work on some
Chromebooks (they have an unconventional way of booting). To help with
that situation I also did some work that could help flash-kernel in general.
Set root in kernel cmdline when there is no initramfs:
https://salsa.debian.org/ins
63 matches
Mail list logo
