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
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
Source: plymouth
Version: 0.9.4-1.1
Severity: important
Tags: patch
Plymouth includes most drm modules in the initramfs and makes it too big
for some machines which only support a limited-size image. These devices
are supportable by setting MODULES=dep in initramfs-tools configuration,
but
On 24/02/2020 19:50, Alper Nebi Yasak wrote:
I'm using Debian on an arm64 chromebook, and not setting "console=tty1"
in the kernel command line results in a number of weird behaviours
related to the initramfs.
Turns out my device-tree has (for debugging purposes?):
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
On 27/02/2020 02:10, Ben Hutchings wrote:
A device that is intended to be used with keyboard and video display
should not have this in the device tree for production units. If we
ship the device tree then we can correct that. If not, then the boot
loader should be configured to override it,
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
Package: initramfs-tools
Version: 0.136
Severity: minor
Dear kernel team,
I'm using Debian on an arm64 chromebook, and not setting "console=tty1"
in the kernel command line results in a number of weird behaviours
related to the initramfs.
During an ordinary boot, plymouth doesn't show the
Package: wnpp
Severity: wishlist
Owner: Alper Nebi Yasak
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: partman-cros
Version : 1
Upstream Author : Alper Nebi Yasak
* URL : http://salsa.debian.org/alpernebbi-guest/partman-cros
* License : GPL-2.0
Package: wnpp
Severity: wishlist
Owner: Alper Nebi Yasak
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: depthcharge-tools
Version : 0.3.0
Upstream Author : Alper Nebi Yasak
* URL : http://github.com/alpernebbi/depthcharge-tools
* License : GPL
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
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).
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
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 support initramfs images larger than a
certa
Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: debian-b...@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
Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: debian-b...@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
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/compression=git
>From e6949630a32e4930561e5fa9d9f443ab8ac
Source: parted
Version: 3.3-1
Severity: wishlist
Tags: fixed-upstream d-i
Dear Maintainer,
The firmware/bootloader in ChromeOS machines only attempts to boot from
partitions of a certain GPT partition type. Please cherry-pick my commit
08256913c307e0313ee014e0f292fa335cc18f1d from upstream
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
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
On 26/05/2020 15:03, Marcin Juszkiewicz wrote:
Devices with Mali gpu can use 'panfrost' driver to provide working
framebuffer. And then Debian installer can be run on screen instead of
serial console.
But 'panfrost' module is not available when d-i starts ;(
So please include 'panfrost' in
On 26/05/2020 20:09, Marcin Juszkiewicz wrote:
> RockPro64 does not enable screen at all. And there are no DRM modules in
netinstall image [1]:
~ # cd /lib/modules/5.6.0-1-arm64/
/lib/modules/5.6.0-1-arm64 # find . -name *drm*
/lib/modules/5.6.0-1-arm64 #
1.
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
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
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
>
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
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
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,
On 13/12/2020 12:05, Ryutaroh Matsumoto wrote:
> I verified that the reported symptom does NOT occur with
> qemu-system-x86_64 and ttyS0 serial console running on an amd64 host.
> This symptom seems unique to arm(64).
I had misunderstood you and was trying with -nographic earlier :) .
Found an
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 21/01/2021 03:08, Vagrant Cascadian wrote:
> It seems rockpro64-rk3399 and pinebook-pro-rk3399 fail to boot when usb
> is started. It hangs indefinitely at:
>
> ## Flattened Device Tree blob at 01f0
> Booting using the fdt blob at 0x1f0
>
> I have observed this also using
Package: firefox
Version: 98.0-2
Severity: important
Tags: upstream patch
Forwarded: https://bugzilla.mozilla.org/show_bug.cgi?id=1757571
X-Debbugs-Cc: debian-...@lists.debian.org
Hello,
I'm running Debian unstable with XFCE on an arm64 chromebook
(rk3399-gru-kevin). Firefox could no longer draw
Package: plymouth
Version: 0.9.5+git20211018-1
Severity: normal
Tags: patch
Hello,
The Plymouth initramfs-tools hook adds the Panfrost kernel module to the
initramfs, but that fails to probe without a devfreq governor and makes
hardware-accelerated graphics unavailable until the module is
Control: severity -1 important
On 2023-04-10 15:52 +03:00, Alper Nebi Yasak wrote:
> Source: linux
> Version: 6.1.20-2
> Severity: wishlist
I had this as wishlist because I didn't have that much time to work on
it until the release. But hardware support is "severity: important&
On 2023-09-21 13:39 +03:00, Simon McVittie wrote:
> On Thu, 21 Sep 2023 at 11:17:51 +0100, Simon McVittie wrote:
>> On Thu, 21 Sep 2023 at 09:41:25 +0300, Alper Nebi Yasak wrote:
>>> I've been using gdm3 without GNOME, and after recently upgrading gdm3 to
>>> 45~beta-1
Package: gdm3
Version: 45~beta-1
Severity: serious
Justification: missing dependency to function properly
Control: -1 notfound 44.1-2
Dear Maintainer,
I've been using gdm3 without GNOME, and after recently upgrading gdm3 to
45~beta-1 I started getting the gray "Oh no!" error message instead of
On 29/08/2022 16:35, Jérémy Lal wrote:
> Hi,
> now that I have three c201 chromebooks running debian/bookworm
> thanks to depthcharge-tools, I might be a good candidate to sponsor that
> package.
>
> Do you still care for it ?
Yes, and I actually had a talk on this at DebConf22 [1]!
But first
Version : 0.6.0-1
Upstream contact : Alper Nebi Yasak
* URL : https://github.com/alpernebbi/depthcharge-tools
* License : GPL-2+
* Vcs : https://salsa.debian.org/alpernebbi/depthcharge-tools
Section : admin
The source builds the following binar
ase have a look at https://wiki.debian.org/Teams/PythonTeam/HowToJoin
>>
>> After that, debian/control should be modified to be:
>> Maintainer: Alper Nebi Yasak
>> , Debian Python Team
>> Vcs-Browser:
>> https://salsa.debian.org/python-team/packages/depthcharge-to
Package: mtools
Version: 4.0.33-1+really4.0.32-1
Severity: wishlist
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps toolchain
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Hi,
I came across timestamp differences in FAT filesystem images while
trying to build
Source: linux
Version: 6.1.20-2
Severity: wishlist
Hi,
I've been going through ChromiumOS kernel configs [1] in hope that I
could reach a reasonable list of things to enable for hardware support
for more chromebooks. What I did is roughly:
- Prepend base.config, /common.config to
Package: thunderbird
Version: 1:115.0-1
Severity: important
X-Debbugs-CC: d...@fifthhorseman.net
Dear Maintainer,
I decided to upgrade Thunderbird to the version in experimental, and
noticed that its OpenPGP functionality is completely broken: the Key
Manager is empty, and it doesn't even
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.
>
>
Package: qemu-user-static
Version: 1:8.0.3+dfsg-3
Severity: normal
Control: found -1 1:8.0.3+dfsg-2
Dear QEMU maintainers,
I've recently noticed my armhf development chroot fails to upgrade
python3-minimal. I've tracked it down to a segmentation fault when
running python3 (for py3compile) as
Hi,
I'd hope "during a mini-DebCamp at ARM" is the perfect time to poke you
about kernel support for more ARM platforms?
On 2023-10-15 16:30 +03:00, Alper Nebi Yasak wrote:
> I'll also look into configs needed for ARM Chromebooks in more detail,
> but that'll take more time bec
46 matches
Mail list logo
