Your message dated Thu, 01 May 2025 17:27:01 +0200 (CEST)
with message-id <20250501152701.9ae62be2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #1038103,
regarding Missing PHY module for Odroid N2+ in debian-ins
Your message dated Thu, 20 Feb 2025 16:04:56 +0100
with message-id
and subject line Re: Bug#1007837: linux: Missing gpio_zynq in arm64 debian
installer initrd
has caused the Debian Bug report #1007837,
regarding linux: Missing gpio_zynq in arm64 debian installer initrd
to be marked as done
Hi,
On 2/20/25 14:33, Salvatore Bonaccorso wrote:
Control: tags -1 + moreinfo
Hi,
On Mon, May 30, 2022 at 02:16:36PM +0200, Michal Simek wrote:
Hi,
it should be enough to enable this option to get this driver to initrd
CONFIG_GPIO_ZYNQ=m
This is actually enabled for arm64 since 4.19.16-1
Processing control commands:
> tags -1 + moreinfo
Bug #1007837 [src:linux] linux: Missing gpio_zynq in arm64 debian installer
initrd
Added tag(s) moreinfo.
--
1007837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007837
Debian Bug Tracking System
Contact ow...@bugs.debian.org w
Control: tags -1 + moreinfo
Hi,
On Mon, May 30, 2022 at 02:16:36PM +0200, Michal Simek wrote:
> Hi,
>
> it should be enough to enable this option to get this driver to initrd
>
> CONFIG_GPIO_ZYNQ=m
This is actually enabled for arm64 since 4.19.16-1. Is still something
missing (or relevant at t
Your message dated Wed, 19 Feb 2025 16:09:42 +0100 (CET)
with message-id <20250219150942.08806be2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #992238,
regarding debian-installer: Installation fails on HP ProLian
On Thu, Dec 19, 2024 at 04:28:52PM -0500, Noah Meyerhans wrote:
> On Thu, Dec 19, 2024 at 09:53:27PM +0100, Chris Hofstaedtler wrote:
> > > > > In theory, if we don't want to explicitly install the package in d-i,
> > > > > another possibility might be to bump it to Priority: standard and let
> > >
Hello,
I was finally able to track down the problem this morning which breaks
debian-installer console output on powerpc and ppc64 since kernel v6.8.
There is a patch [1] in the current Debian kernel package which was supposed
to fix the exact same problem [2] on ppc64el and it was introduced
Your message dated Sun, 25 Aug 2024 10:02:16 +
with message-id
and subject line Bug#1076539: fixed in initramfs-tools 0.142+deb12u1
has caused the Debian Bug report #1076539,
regarding debian-installer: /boot partition created by installer isn't big
enough
to be marked as done.
This
Processing control commands:
> reassign -1 initramfs-tools
Bug #1076695 [src:debian-installer] debian-installer: /boot partition created
by installer isn't big enough
Bug reassigned from package 'src:debian-installer' to 'initramfs-tools'.
No longer marked as found
the
> configuration entry CONFIG_DM_INTEGRITY=m and possibly add the
> "dm-integrity" module's name to /etc/initramfs-tools/modules file in
> order to automatically activate at boot time the LVM volumes with the
> integrity feature enabled.
The first bit has been here fo
Hi,
A commit to address the Xen virtual keyboard large uevent/modalias
failure has been merged into upstream linux for the upcoming 6.10
release:
https://git.kernel.org/torvalds/c/0774d19038c496f0c3602fb505c43e1b2d8eed85
This should address https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983357
mage-6.1.0-12-amd64'
Bug reassigned from package 'linux-image-6.1.0-12-amd64' to 'src:linux'.
Ignoring request to alter found versions of bug #1052978 to the same values
previously set
Ignoring request to alter fixed versions of bug #1052978 to the same values
previously s
Processing control commands:
> reassign -1 src:linux 6.1.27-1
Bug #1038103 [debian-installer] Missing PHY module for Odroid N2+ in
debian-installer (bookworm)
Bug reassigned from package 'debian-installer' to 'src:linux'.
Ignoring request to alter found versions of b
e, dated 2023/06/07:
> Linux bootstrap 6.1.0-9-arm64 #1 SMP Debian 6.1.27-1 (2023-05-08) aarch64
> GNU/Linux
Thanks for the report and all the details.
Reassigning to the linux kernel, which should get an update to ship
those modules in the relevant udeb. Those probably should go along with
m
Earlier merge request was redundant, after futher tracing I believe this merge
request directly addresses the root of the remaining issues:
https://salsa.debian.org/installer-team/debian-installer/-/merge_requests/34
- Original Message -
> From: "Timothy Pearson"
> T
nday, June 5, 2023 2:02:55 PM
> Subject: Re: Bug#990016: marked as done (Debian installer images missing
> ASpeed video driver)
> Unfortunately it appears the bug persists. On the latest ppc64el netinst
> weekly
> build there is no trace of the ast module:
>
> ~ # modprobe as
Unfortunately it appears the bug persists. On the latest ppc64el netinst
weekly build there is no trace of the ast module:
~ # modprobe ast
modprobe: FATAL: Module ast not found in directory
/lib/modules/6.1.0-9-powerpc64le
Control: tag -1 - patch
Hi,
Thanks for the proposed patch but as discussed elsewhere it seemed too
risky to force 32 bpp on everyone, so I went for what looked like the
least risky (adding bochs.ko and cirrus.ko, manually and for the time
being).
Ben Hutchings (2023-05-14):
> I think the proble
On Sun, 2023-05-14 at 19:40 +0200, Ben Hutchings wrote:
[...]
> This works for me with all the QEMU graphics devices. But I haven't
> tested on real hardware.
Now tested successfully on 2 custom desktops:
- Asus P8Z68-V LX motherboard, Intel Core i5 2500 CPU, integrated GPU
- ASRock B450 PRO4, A
native).
+ [ Ben Hutchings ]
+ * Always use 32 bpp for GRUB EFI graphical menu (Closes: #1036019)
+
-- Cyril Brulebois Thu, 27 Apr 2023 22:52:15 +0200
debian-installer (20230427) unstable; urgency=medium
signature.asc
Description: This is a digitally signed message part
nstaller shows
up with both std and cirrus.
- With Bookworm RC 2 netinst amd64 (again under UEFI), switch from
default “Graphical install” to “Install”: the screen is garbled
with std, split with cirrus.
This is easily confirmed:
- Triggering a debian-installer “netboot” build (not
hould note GRUB itself is “text-like” with RC 1,
while it's “graphical” with RC 2.
Reverting the following commit in debian-installer.git and building a
netboot-gtk image against unstable gives me a working graphical
installer with `-vga std` (or no options) and `-vga cirrus`. I
0.178-3):
[...]
> Those contents are defined via those files in linux.git:
>
> kibi@tokyo:~/debian-kernel/linux.git (sid=)$ cat
> debian/installer/modules/amd64/fb-modules
> #include
>
> vesafb ?
> vga16fb
>
> kibi@tokyo:~/debian-kernel/linux.g
Package: debian-installer
Version: 20230427
Severity: important
X-Debbugs-Cc: debian-...@lists.debian.org, debian-kernel@lists.debian.org,
debia...@lists.debian.org
Hi everyone,
I'm reaching out to all the aforementioned teams because I know nothing
about UEFI, kernel-side DRM modules,
Your message dated Sun, 19 Mar 2023 19:00:10 +
with message-id
and subject line Bug#990016: fixed in linux 6.1.20-1
has caused the Debian Bug report #990016,
regarding Debian installer images missing ASpeed video driver
to be marked as done.
This means that you claim that the problem has
Hello Salvatore,
On Sat, 11 Mar 2023 at 08:19, Salvatore Bonaccorso wrote:
> > I have opened an MR in salsa:
> > https://salsa.debian.org/kernel-team/linux/-/merge_requests/676
> I assume you were able to test it accordingly it works as expected?
>
> Looks fine IMHO, but wanted to double-ch
Hi Héctor,
On Sat, Mar 11, 2023 at 01:15:31AM +0100, Héctor Orón Martínez wrote:
> Hello,
>
> I have opened an MR in salsa:
> https://salsa.debian.org/kernel-team/linux/-/merge_requests/676
I assume you were able to test it accordingly it works as expected?
Looks fine IMHO, but wanted to do
Hello,
I have opened an MR in salsa:
https://salsa.debian.org/kernel-team/linux/-/merge_requests/676
Regards
--
Héctor Orón -.. . -... .. .- -. -.. . ...- . .-.. --- .--. . .-.
Ben Hutchings wrote on Thu, Jun 30, 2022 at 02:08:24AM +0200:
> > Sorry this wasn't clear. I didn't mean obsolete as no longer useful,
> > just that it is old: wireless-regdb-udeb hasn't been updated in two
> > years, while the main wireless-regdb package keeps getting updates
> > regularly.
>
> Y
On Tue, 2022-06-14 at 08:27 +0900, Dominique Martinet wrote:
> Ben Hutchings wrote on Mon, Jun 13, 2022 at 04:39:23PM +0200:
> > On Fri, 2022-06-10 at 09:39 +0900, Dominique Martinet wrote:
> > > the udeb regdb is also slightly obsolete, I'm not sure why it was needed
> > > in the first place but i
Your message dated Wed, 29 Jun 2022 23:32:25 +
with message-id
and subject line Bug#1012601: fixed in wireless-regdb 2022.04.08-2
has caused the Debian Bug report #1012601,
regarding wireless-regdb: alternative broken on debian-installer install
to be marked as done.
This means that you
Ben Hutchings wrote on Mon, Jun 13, 2022 at 04:39:23PM +0200:
> On Fri, 2022-06-10 at 09:39 +0900, Dominique Martinet wrote:
> > the udeb regdb is also slightly obsolete, I'm not sure why it was needed
> > in the first place but it might be possible to use the normal package
> > instead?
>
> Why d
On Fri, 2022-06-10 at 09:39 +0900, Dominique Martinet wrote:
[...]
> The original cause for this is that deian-installer copies the files
> because of the combinaison of these two:
> https://salsa.debian.org/installer-team/debian-installer/-/blob/master/build/pkg-lists/base#L34
> - wi
/# ls -l /lib/firmware/regulatory.db
lrwxrwxrwx 1 root root 31 Jun 10 00:23 /lib/firmware/regulatory.db ->
/etc/alternatives/regulatory.db
The original cause for this is that deian-installer copies the files
because of the combinaison of these two:
https://salsa.debian.org/installer-team/
Hi,
it should be enough to enable this option to get this driver to initrd
CONFIG_GPIO_ZYNQ=m
Thanks,
Michal
Hi,
Cian Donovan (2022-05-20):
> Since the latest version of the debian-installer-11-netboot-amd64
> package on Debian Bullseye, the ncurses text installer no longer
> respects the orientation of the framebuffer console.
>
> Before, if I set the orientation with the kernel par
d as found in versions linux/5.17~rc8-1~exp1.
> reassign 1009127 debian-installer
Bug #1009127 [network install initramfs "initrd.gz".] Missing phy_gmii_sel.ko
in dists/bullseye/main/installer-armhf/current/images/netboot/netboot.tar.gz
Warning: Unknown package 'network'
War
Source: linux
Version: 5.10.84-1
Severity: normal
Dear Maintainer,
I tried the latest arm64 installer on Xilinx SOM board which is using cadence
macb driver with ethernet phy which required reset over gpio. DT has proper
description for it but gpio_zynq driver is not the part of installer as bu
Hello,
Asking debian-kernel about firmwares: is the firmware-intel-sound
package needed for getting sound on some hardware?
Do you know if arm64 has some platforms which require such kind of sound
firmwares?
Samuel
Samuel Thibault, le lun. 14 févr. 2022 12:55:15 +0100, a ecrit:
> Arnaud Rebillo
Justus Winter writes:
> Steve McIntyre writes:
>
>> OK, this is not looking good. I'll ask some of the Arm folks to have a
>> look here in case they can help.
>
> Thanks!
Any news from Arm?
Justus
signature.asc
Description: PGP signature
means ppc64el, arm64,
riscv, sparc64 in practice.
- Original Message -
> From: "Jochen Sprickerhof"
> To: "Timothy Pearson" , 990...@bugs.debian.org
> Sent: Saturday, July 10, 2021 1:09:14 PM
> Subject: Re: Bug#990016: Debian installer images missing ASpeed v
>>U-Boot 2013.04 (Oct 02 2015 - 14:44:51)
>
> I moved all my Mustangs over to UEFI (edk2) rather than U-Boot, but I
> honestly don't know if that's an option for the m400.
I put the cartridge in UEFI mode. AIUI, it starts using U-Boot, then
chainloads UEFI.
>>[
=off" to the
>> kernel command line?
>
>Interesting. Yeah, I actually tried that last week, but it failed:
:-( Argh.
Oh wow, just noticed:
>U-Boot 2013.04 (Oct 02 2015 - 14:44:51)
I moved all my Mustangs over to UEFI (edk2) rather than U-Boot, but I
honestly don't know i
Steve McIntyre writes:
> On Mon, Aug 16, 2021 at 12:54:47PM +0200, Justus Winter wrote:
>>Steve McIntyre writes:
>>> On Mon, Aug 16, 2021 at 10:09:49AM +0200, Justus Winter wrote:
>>>>Package: debian-installer
>>>>Version: 20210731
>>>>Seve
On Mon, Aug 16, 2021 at 12:54:47PM +0200, Justus Winter wrote:
>Steve McIntyre writes:
>> On Mon, Aug 16, 2021 at 10:09:49AM +0200, Justus Winter wrote:
>>>Package: debian-installer
>>>Version: 20210731
>>>Severity: critical
>>>Tags: d-i
>>
Hi Steve :)
Steve McIntyre writes:
> Reassigning to the right package. While you're seeing this during d-i,
> the problem is clearly coming from the Linux kernel.
Thanks!
> On Mon, Aug 16, 2021 at 10:09:49AM +0200, Justus Winter wrote:
>>Package: debian-installer
Processing control commands:
> severity -1 important
Bug #992238 [debian-installer] debian-installer: Installation fails on HP
ProLiant m400 Server: additional cores crash, kernel hangs in acpi_init
Severity set to 'important' from 'critical'
> reassign -1 src:linux
Bug
Cyril Brulebois (2021-07-26):
> > ## proposed solution
> >
> > If others agree, I suggest we add the following somewhere in the
> > installation guide (I don't think we should have a specific warning
> > in the installer; or more specifically it would be way too late to
> > have it be shown local
Your message dated Wed, 28 Jul 2021 06:03:43 +
with message-id
and subject line Bug#961056: fixed in linux 5.10.46-3
has caused the Debian Bug report #961056,
regarding debian-installer: qemu-system-s390x installation fails due to
incorrect serial device
to be marked as done.
This means
inning, and many no-desktop installation
tests after that. I haven't used the installed systems much though,
since I'm working on the installer side. :)
Adding #969264 in cc to chime in: that's still current as of
linux-image-5.10.0-8-amd64 (version 5.10.46-2), both in the Debian
HI Cyril,
On Mon, Jul 26, 2021 at 06:14:09AM +0200, Cyril Brulebois wrote:
> @KT:
>
> I haven't uploaded it since I'm seeing iwlwifi requesting what appears
> to be a debug-only firmware (iwl-debug-yoyo.bin), that's even requested
> via an aptly-named firmware_request_nowarn() function in linux.g
TL;DR: No progress on the social side (doc) yet, but lots of progress on
the technical side (making firmware-enabled images work better)!
Kernel team, feel free to skip to @KT for a little question.
I'd like to thank Ben again for the modalias thing, this made it very
easy to deploy firmwa
Hi,
On Tue, May 19, 2020 at 08:24:27PM +0200, Valentin Vidić wrote:
> On Tue, May 19, 2020 at 07:23:21PM +0200, John Paul Adrian Glaubitz wrote:
> > Please see #926539 [1].
>
> Thanks, I have sent the patch for the driver instead:
>
> https://lkml.org/lkml/2020/5/19/854
This appears to be app
Processing control commands:
> reassign -1 src:linux
Bug #990016 [debian-installer] Debian installer images missing ASpeed video
driver
Bug reassigned from package 'debian-installer' to 'src:linux'.
Ignoring request to alter found versions of bug #990016 to the same
Ping :). AR9271 dominates modern free-software-friendly wireless dongles and I
would love to see their support in Bullseye. Please let me know if I can help.
signature.asc
Description: This is a digitally signed message part.
Processing control commands:
> block -1 by 900171 931283
Bug #934822 [debian-installer] debian-installer: include free firmware-ath9k-htc
934822 was not blocked by any bugs.
934822 was not blocking any bugs.
Added blocking bug(s) of 934822: 931283 and 900171
--
934822: https://bugs.debian.
On 2019-03-09, Adam D. Barratt wrote:
> On Thu, 2019-03-07 at 22:01 +, Ben Hutchings wrote:
>> On Thu, 2019-03-07 at 14:39 +0100, Cyril Brulebois wrote:
>> [...]
>> > > * Rebuild the debian-installer images, pulling in updates from
>> > > stretch-upda
On Thu, 2019-03-07 at 22:01 +, Ben Hutchings wrote:
> On Thu, 2019-03-07 at 14:39 +0100, Cyril Brulebois wrote:
> [...]
> > > * Rebuild the debian-installer images, pulling in updates from
> > > stretch-updates, leaving only armhf netboot targets broken.
> >
&
Vagrant Cascadian (2019-03-07):
> If that's indeed the case, then that does seem like the best approach.
> Happy to test images to confirm.
Rebuilding the stretch debian-installer source package within stretch
should give you everything you need to test. Beware if you go for a
m
Ben Hutchings (2019-03-07):
> On Thu, 2019-03-07 at 14:39 +0100, Cyril Brulebois wrote:
> [...]
> > > * Rebuild the debian-installer images, pulling in updates from
> > > stretch-updates, leaving only armhf netboot targets broken.
> >
> > Expanding a bit:
On 2019-03-07, Ben Hutchings wrote:
> On Thu, 2019-03-07 at 14:39 +0100, Cyril Brulebois wrote:
> [...]
>> > * Rebuild the debian-installer images, pulling in updates from
>> > stretch-updates, leaving only armhf netboot targets broken.
>>
>> Expanding a
On Thu, 2019-03-07 at 14:39 +0100, Cyril Brulebois wrote:
[...]
> > * Rebuild the debian-installer images, pulling in updates from
> > stretch-updates, leaving only armhf netboot targets broken.
>
> Expanding a bit: rebuilding src:debian-installer from the stretch
> br
Hi,
Vagrant Cascadian (2019-03-06):
> Even rebuilding the debian-installer images, while pulling in a
> working kernel that would boot, debian-installer would load .udeb
> modules from stretch, not stretch-updates. This might be ok for
> hd-media targets or targets that do not load
Due to #922478, the debian-installer images for stretch are currently
not bootable on the armhf architecture.
While the linux kernel packages have been fixed in stretch-updates and
stretch-proposed-updates, the debian-installer images still were built
with the broken kernel.
Even rebuilding the
On Mon, Aug 13, 2018 at 01:44:48PM +0200, Julien Cristau wrote:
>On 08/13/2018 01:57 AM, Steve McIntyre wrote:
>> On Thu, Aug 02, 2018 at 10:56:59AM +0200, Cyril Brulebois wrote:
>>> => Question: should we restrict architectures we build images for?
>>
>> Probably. I'm only thinking x86, arm64 and
On 08/13/2018 01:57 AM, Steve McIntyre wrote:
> On Thu, Aug 02, 2018 at 10:56:59AM +0200, Cyril Brulebois wrote:
>> => Question: should we restrict architectures we build images for?
>
> Probably. I'm only thinking x86, arm64 and maybe armhf. Wait for
> people to ask for others and add on a case-b
Apologies for taking a while to get back to you here... :-/
Also adding a CC to the -kernel list.
On Thu, Aug 02, 2018 at 10:56:59AM +0200, Cyril Brulebois wrote:
>
>This is a long read… I've highlighted “to do”-like items with an arrow
>(=>).
ACK!
>debian-installer
>==
Your message dated Thu, 19 Jul 2018 19:17:38 +
with message-id
and subject line Bug#903122: fixed in linux 4.9.110-2
has caused the Debian Bug report #903122,
regarding debian-installer-9-netboot-amd64: Please add char/virtio_console
module (paravirtualized serial) to netinst
to be marked as
Your message dated Thu, 12 Jul 2018 04:20:43 +
with message-id
and subject line Bug#903122: fixed in linux 4.17.6-1
has caused the Debian Bug report #903122,
regarding debian-installer-9-netboot-amd64: Please add char/virtio_console
module (paravirtualized serial) to netinst
to be marked as
On Tue, 2018-07-10 at 02:32 +0200, Cyril Brulebois wrote:
> Control: reassign -1 src:linux
> Control: tag -1 patch
>
> Ben Hutchings (2018-07-09):
> > I would say virtio-modules. All the virtio class drivers depend on
> > virtio and virtio_ring, which means that adding them to any other
> > pack
Processing control commands:
> reassign -1 src:linux
Bug #903122 [debian-installer-9-netboot-amd64]
debian-installer-9-netboot-amd64: Please add char/virtio_console module
(paravirtualized serial) to netinst
Bug reassigned from package 'debian-installer-9-netboot-amd64' to 'sr
er -- Release team member -- Freelance Consultant
From 90196cd7fb99232c3990600634032a64693ec2ba Mon Sep 17 00:00:00 2001
From: Cyril Brulebois
Date: Tue, 10 Jul 2018 02:22:04 +0200
Subject: [PATCH] udeb: Add virtio_console to virtio-modules (Closes: #903122).
Reported-by: Vincent Caron
---
debian/changelog
On Sun, 2018-07-08 at 06:37 +0200, Cyril Brulebois wrote:
[...]
> Vincent Caron (2018-07-06):
[...]
> > If this module makes it to netinst's initrd, one would use those kvm
> > args:
> >
> > -chardev file,path=virtiocon0.log,id=virtiocon0
> > -device virtio-serial
> > -device virtconsole,chardev=
Hi Vincent,
Vincent Caron (2018-07-06):
> Package: debian-installer-9-netboot-amd64
> Severity: wishlist
> Tags: d-i
>
> Dear Maintainer,
>
> while automating Debian image creations thru netinst + KVM, I stumbled
> upon a limitation from the emulated UARTs (if one sen
Package: debian-installer
Severity: serious
Justification: graphical installer regression
Hi,
Ever since we switched from linux 4.15 to 4.16, the graphical installer
gets a black screen. Comparing Xorg logs, everything is exactly the same
except for the kernel version and timestamps. syslog has
Hi Erik,
On Tue, Jan 02, 2018 at 11:09:03AM -0800, E Barker wrote:
> Hello,
>
> Just wondering when we can expect an update to the linux and initrd
> images within the netboot debian-installer tree?
See https://lists.debian.org/debian-stable-announce/2017/12/msg2.html
The ne
Hello,
Just wondering when we can expect an update to the linux and initrd
images within the netboot debian-installer tree?
I had to apply the numa=off workaround for PXE installs but the
date/time stamp for the files still show 12/5/17, 7:51:00 AM:
ftp://ftp.ca.debian.org/debian/dists/jessie
...@rasqual.e4ward.com]
Gesendet: Mittwoch, 2. August 2017 13:38
An: Steve McIntyre ; Cyril Brulebois ;
867...@bugs.debian.org
Cc: Paschedag, Robert ;
debian-kernel@lists.debian.org; debian...@lists.debian.org
Betreff: Re: Bug#867898: debian-installer-netboot-images:
debian-installer-9-netboot
Hi Robert,
After digging a bit, I think my issue lies with the APT source I used.
At work (ESXi host), netboot works because it points to a proper apt-
mirror.
On the other hand, at home I frankenbuilt mine using the DVD iso and
specifying debian-installer/allow_unauthenticated=true. I retried
Hello all,
Steve, what is the suggested resolution then?
For testing, I booted the initrd's and kernels extracted from standard DVD
and netboot iso's via PXE. While they cannot progress further for obvious
reasons, by switching to tty2, /dev/sda does appear in the listing. Those
do ship with th
rs/message/fusion/mptfc.ko
./lib/modules/3.16.0-4-amd64/kernel/drivers/message/fusion/mptbase.ko
root@server#
Soas these modules have been "moved" to scsi-modules (see
https://www.debian.org/devel/debian-installer/News/2016/20160521), but
scsi-modules is "excluded"
On Thu, Jul 13, 2017 at 01:09:58AM +0100, Steve McIntyre wrote:
>On Thu, Jul 13, 2017 at 01:50:34AM +0200, Cyril Brulebois wrote:
>>
>>> But this package is also missing on the "release" DVDs for "amd64".
>>> Nearly every other architecture has this package within an image
>>> (whether "netinst" od
On Thu, Jul 13, 2017 at 01:50:34AM +0200, Cyril Brulebois wrote:
>Paschedag, Robert (2017-07-12):
>> thank you for your hints on the packages, that *are* available for
>> amd64. The package we need is
>>
>> scsi-modules-4.9.0-3-amd64-di_4.9.30-2_amd64.udeb
>>
>> this one contains the needed modu
Hi,
Paschedag, Robert (2017-07-12):
> thank you for your hints on the packages, that *are* available for
> amd64. The package we need is
>
> scsi-modules-4.9.0-3-amd64-di_4.9.30-2_amd64.udeb
>
> this one contains the needed modules for the LSI logic controller (and
> several other)
>
> ...
> .
Control: severity -1 important
Hi Robert & kernel maintainers,
Paschedag, Robert (2017-07-10):
> Package: debian-installer-netboot-images
> Version: 20170615
> Severity: serious
>
> Trying to perform a PXE installation with the debian 9 (stretch)
> netboot image and a De
On 06/15/2017 12:57 PM, Karsten Merker wrote:
> Cyril Brulebois wrote:
>> On Thu, Jun 15, 2017 at 10:43:18AM +0100, Ben Hutchings wrote:
>>> Control: tag -1 moreinfo
>>>
>>> On Thu, 2017-06-15 at 08:34 +0200, Heinrich Schuchardt wrote:
>>>>
On 06/15/2017 11:43 AM, Ben Hutchings wrote:
> Control: tag -1 moreinfo
>
> On Thu, 2017-06-15 at 08:34 +0200, Heinrich Schuchardt wrote:
>> Package: debian-installer
>> Version: stretch
>> Severity: normal
>>
>> Dear Maintainer,
>>
>> the
Ben Hutchings (2017-06-15):
> Control: tag -1 moreinfo
>
> On Thu, 2017-06-15 at 08:34 +0200, Heinrich Schuchardt wrote:
> > Package: debian-installer
> > Version: stretch
> > Severity: normal
> >
> > Dear Maintainer,
> >
> > the Lamobo R1
Processing control commands:
> retitle 864807 b53_mdio module doesn't get loaded automatically on Lamobo R1
Bug #864807 [debian-installer] debian-installer: Lamobo R1 requires modprobe
b53_mdio
Changed Bug title to 'b53_mdio module doesn't get loaded automatically on
Lamob
Your message dated Wed, 03 May 2017 06:00:14 +
with message-id
and subject line Bug#859366: fixed in linux 4.9.25-1
has caused the Debian Bug report #859366,
regarding linux: Please enable suffix for m68k debian-installer kernel image
to be marked as done.
This means that you claim that the
Source: linux
Version: 4.9.18-1
Severity: normal
Tags: patch
User: debian-...@lists.debian.org
Usertags: m68k
Hi!
While working on fixing debian-installer on m68k, I ran into the
following problem after updating the m68k-specific configuration
to use the common m68k image:
# Set up modules.dep
Hi Ronald,
Ronald Maas (2017-02-08):
> Good news. I was able to successfully install Stretch RC2 on the
> Gigabyte MP30-AR0 motherboard. Also the installer was able to
> recognize the network properly, so this bug and also bug 820022 can be
> closed.
>
> Attached the dmesg output for reference.
Source: debian-installer
Version: 20161031
Severity: important
Hi boot/kernel people,
The recent bugfix for Built-Using generation meant we moved from:
linux-signed (= $LINUX_VERSION)
to the following:
linux-signed (= $LINUX_SIGNED_VERSION)
as a first step, which was later changed to
Your message dated Tue, 07 Jun 2016 07:01:03 +
with message-id
and subject line Bug#692333: fixed in linux 4.6.1-1
has caused the Debian Bug report #692333,
regarding debian-installer: Softlink target path for /initrd.img is different
from /vmlinuz
to be marked as done.
This means that you
Karsten Merker (2016-05-22):
> I am not familiar with the webml syntax, so I can currently
> only supply a wording proposal:
>
> -8<--8<--8<--8<--8<--8<-
>
> Wired ethernet non-functional on certain arm-based systems
>
Hi,
Karsten Merker (2016-05-22):
> On Sun, May 22, 2016 at 01:37:42PM +0200, Karsten Merker wrote:
> > On Sat, May 21, 2016 at 11:13:17PM +0200, Cyril Brulebois wrote:
> >
> > > The Debian Installer team[1] is pleased to announce the sixth alpha
> > > rele
Your message dated Sun, 07 Feb 2016 19:01:03 +
with message-id
and subject line Bug#796096: fixed in linux 4.3.5-1
has caused the Debian Bug report #796096,
regarding debian-installer: USB devices dont work during install
to be marked as done.
This means that you claim that the problem has
Source: debian-installer
Severity: serious
Justification: FTBFS
Hi,
linux received this change a while ago, and it has now reached
unstable and testing:
| linux (4.3~rc3-1~exp1) experimental; urgency=medium
|
| […]
| * [i386] Replace 586 flavour with 686
| - Enable support for OLPC and
I just spent many hours installing Jessie onto a vivopc, VM42, which
seems to have this same keyboard. The driver really should be loaded on
the installer!
I'm surprised that the only place (so far) that I've found this
referenced is in this bug report over a year old now...
(I ended up inst
1 - 100 of 302 matches
Mail list logo
