Re: Custom gtk installer similar to Proxmox VE installer

[Geert Stappers]

On Sun, Mar 17, 2024 at 03:35:15AM +, pve-hgoi9uef wrote:
> Hello,
> 
> I have been attempting to package my software (.deb packages served
> by a repository) into a custom Debian GNU/Linux installer for
> redistribution. I have been using the GTK netboot installer with a
> preseed file packaged into the initrd.
> 
> I did run into limitations with preseed though:
> 1. Install packages into /target before d-i apt-setup/local[0-9]
>repositories are loaded. (one being ca-certificates)
> 2. Run custom scripts at certain points in the installation process.
> 3. Change/add questions, display some text (put locale/language/kbd
>map all in one step, change the layout)
> 
> I tried debconf but it seems that I was not able to completely solve
> the problem, only ask custom questions.
> 
> I've done some research and found the Proxmox Virtualization Environment
> installer (https://git.proxmox.com/?p=pve-installer.git). My knowledge
> in this area of OS installers is very little, and after two weeks or
> so of attempting to get this to work (without much success), I thought
> that I would ask for help.
> 
> The Proxmox VE installer seems to be a customized one built with GTK3,
> html/CSS, and Perl. My question: How would I go about making a similar
> installer?

Start with just rebuilding that installer.  Verify that it is working.
Then change some text string and rebuild. Verify that it is still
working and your change is visible.
That known good point is starting point for further changes.


> Preferably, I would want to be able to customize how it looks with
> html templates, similar to what Proxmox does. There are many videos
> online of people going through the installer.
> 
> Here is my workflow for building the ISO (in a bookworm Docker container):
> 1. install dependencies
> 2. run debootstrap
> 3. fetch initrd from
>
> http://deb.debian.org/debian/dists/[version]/main/installer-[arch]/current/images/netboot/gtk/amd64
> 4. extract, add custom files, archive it back
> 5. use grub-mkrescue to create the ISO
> 
> Thank you very much for your help. I can attach a 'bounty' of some sort
> to be paid in cryptocurrency if this is a very hard task to accomplish.
 
Yeah, expressing the value of libre software is a challenge.


 
Groeten
Geert Stappers
-- 
Silence is hard to parse

Bug#1061820: Patch looks good

[Geert Stappers]

On Mon, Jan 29, 2024 at 08:26:14PM +, Ken Sharp wrote:
> 
> - Turns out I've attached the patch four times.

And the patch looks good.


Groeten
Geert Stappers
-- 
Silence is hard to parse


signature.asc
Description: PGP signature

Re: An appeal to d-i devs for software freedom

[Geert Stappers]

On Sun, Dec 31, 2023 at 10:55:06AM -0600, Russell Hernandez Ruiz wrote:
> Submitted merge requests
> here
> https://salsa.debian.org/installer-team/apt-setup/-/merge_requests/14

I have seen the request for further help.


> and here
> https://salsa.debian.org/installer-team/apt-setup/-/merge_requests/15
> 

Updated with "What is blocking the merge request?"



Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: An appeal to d-i devs for software freedom

[Geert Stappers]

On Sun, Dec 31, 2023 at 09:26:42AM -0600, Russell Hernandez Ruiz wrote:
> On Sun, 2023-12-31 at 16:13 +0100, Geert Stappers wrote:
> > Convert that into a patch and/or merge request.
> > 
> 
> I would have loved for that to be in the first, but I lack knowledge;
> would you kindly point me to where this is controlled? Then I am
> confident I could do it.
> 
> > Groeten
> > Geert Stappers
> > Yes, it is me
> 
> Ha, Geert Stappers!  Let's make this happen :)
> 

Poke me saturday 13 january


Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: An appeal to d-i devs for software freedom

[Geert Stappers]

On Sun, Dec 31, 2023 at 06:59:55AM -0600, Russell Hernandez Ruiz wrote:
> Dear debian-installer developers,
 
Hi Russell,
Hi Others,


> I feel the need to begin this message by stating what it is NOT. This message 
> is
> NOT meant to contest the decision to include non-free firmware in the 
> installer.
> This post concerns UI.
> 
> Primary proposal: that the priority of the question concerning 
> non-free-firmware
> in the installer be changed from "low" to "high".
> 
> The current situation is that debian.org proudly states "Debian is a complete
> Free Operating System!" with a big Download link. That link then serves the 
> user
> an installer of Debian+proprietary firmware. That installer then proceeds to
> install the proprietary firmware **without prompting.** Many of us do not find
> this acceptable.
> 
> However, I was able to confirm in IRC that the installer in fact already has 
> the
> ability to prompt about non-free firmware (the repository, wholesale), if only
> the user chose to "expertly" configure their system.
> 
> User "cheapie" on IRC reports that he "keeps running into users over and over
> again who seem to /not/ want firmware packages installed," and because of 
> that,
> "would personally prefer for the priority to be high."
> 
> Other users are also puzzled why Debian /seems/ to have decided to only allow
> rejecting the non-free components via the even more expert, hardly documented,
> boot flag mechanism.
> 
> I suggest that it is not an "expert" decision to choose freedom. The user
> downloaded what loudly purports to be Free Software, so they ought to be 
> offered
> a choice to get that. Furthermore, it's just the right thing to do, for their
> freedom's sake.
> 
> Please increase the priority, from "low" to "high", of the the 
> non-free-firmware
> installer question.
> 

Convert that into a patch and/or merge request.


> 
> Secondary proposal: improve the description of the non-free-firmware question.
> 
> Currently it is worded thusly:
> 
> > Some non-free firmware has been made to work with Debian. Though this 
> > firmware
> > is not at all a part of Debian, standard Debian tools can be used to install
> > it. This firmware has varying licenses which may prevent you from using,
> > modifying, or sharing it.
> 
> > Please choose whether you want to have it available anyway.
> 
> > Use non-free firmware?
> 
> I suggest the following wording:
> 
> > Some computer parts require that users install programs on them in order to
> > function fully or at all. For example, some Wi-Fi cards and audio chipsets 
> > may
> > not function without them. This type of program is called "firmware".
> 
> > Although not at all part of Debian, some non-free firmware has been made to
> > work with Debian. This firmware has varying licenses which restrict your
> > freedoms to use, modify, or share the software, and generally does not have
> > source forms that you may study.
> 
> > Please choose whether you want to have it available anyway, and 
> > automatically
> > installed according to your hardware.
> 
> > Use non-free firmware?
 
Convert that into a patch and/or merge request.

> It is important for users to understand the purpose of firmware, and the
> concequence of selecting "Yes", to make an informed decision.
> 

True


> 
> This letter is primarily concerned with the simple changes above, but I would
> like to document a good, relevant suggestion from IRC: to give a summary of 
> the
> non-free programs, and a way to customize the list, so that, for example, I 
> may
> consent to CPU microcode, but refuse to use the on-board network card. We
> understand, however, that this is a much more involved change.
 
> Kind regards,
> Russell Hernandez Ruiz
 

Groeten
Geert Stappers
Yes, it is me
-- 
Silence is hard to parse

Bug#1055167: Network interface lost IP when lease expired after switching from isc-dhcp-client

[Geert Stappers]

On Wed, Nov 01, 2023 at 02:44:13PM +0100, Larsen wrote:
>   ... but instead the package should take care of such a situation.

Please add logging of the install ( "apt" )  stop of isc-dhcp-client (
either journalctl or /var/log/ ) and start of udhcpc ( journalctl or log
)


Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: Daily d-i images for i386 not being built?

[Geert Stappers]

On Sun, Aug 27, 2023 at 10:12:09AM +0200, Holger Wansing wrote:
> Am 27. August 2023 08:48:20 MESZ schrieb Holger Wansing:
> > Hi,
> >
> > I noticed that the link to the daily built netinst image for i386 is "Not 
> > found" currently:
> > <https://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/>
> > on <https://www.debian.org/devel/debian-installer/index.en.html>
> >
> > The directory is not existing.
> >
> > Is this a known issue?
> 
> Ah, sorry. 

[1]


> By accident I found a bug against release-notes, which documents that
> i386 d-i images will be dropped for trixie.
> <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036358>
> 
> So, sorry for the noise.

No worries  (and [1] )

 
> OTOH I would then remove the i386 link from
> <https://www.debian.org/devel/debian-installer/index.en.html>
> now?

Please do.
If you can't, file a bugreport against pseudo package 'www.debian.org'.
( https://www.debian.org/Bugs/pseudo-packages )
 
 
> Holger


Groeten
Geert Stappers

[1] Sincere questions do not need a "sorry" follow-up.
-- 
Silence is hard to parse

Re: Bug#1034041: Should firmware-amd-graphics be automatically installed? Check inbox

[Geert Stappers]

On Mon, May 22, 2023 at 11:40:33PM +0200, Geert Stappers wrote:
> On Mon, May 22, 2023 at 01:30:23PM -0700, Keith Proctor wrote:
> > I must have sent 1/2 a dozen requests to unscript to this email address.
> > 
> > debian-boot-requ...@lists.debian.org 
> > <mailto:debian-boot-requ...@lists.debian.org>
> > 
> > This address was in the email headers.

The relevant header is:
  List-Unsubscribe: 
<mailto:debian-boot-requ...@lists.debian.org?subject=unsubscribe>

> > Why am I not being removed?
> 
> Maybe because the confirm request email is still in your inbox?
 
Was 'unsubscribe' in the subject?


Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: Bug#1034041: Should firmware-amd-graphics be automatically installed? Check inbox

[Geert Stappers]

On Mon, May 22, 2023 at 01:30:23PM -0700, Keith Proctor wrote:
> I must have sent 1/2 a dozen requests to unscript to this email address.
> 
> debian-boot-requ...@lists.debian.org 
> 
> 
> This address was in the email headers.
> 
> Why am I not being removed?

Maybe because the confirm request email is still in your inbox?

Re: Bug#1033546: Debian installer / Network configuration

[Geert Stappers]

On Mon, Mar 27, 2023 at 08:35:22AM +,  Christophe wrote:
> Configure network:      [E]
> 
> Comments/Problems:
> 
> This bug is present since many years.

  :-)


> Currently, tt's not possible to declare a network like this :
> 
> | IPv4:54.37.96.xxx/32
> | Gateway: 54.38.179.254
> 
> The installer tell "Unreachable gateway" but it's not true. If the
> network if configured with these values, everything is fine.
> 
> If i put this in /etc/network/interfaces, it works :
> 
> | auto eth0
> | iface eth0 inet static
> |     address 54.37.96.xxx/32
> |     gateway 54.38.179.254


Which feels wrong.

It is the  /32   that makes it odd.


Regards
Geert Stappers
Would like to see this bugreport to be closed.
-- 
Silence is hard to parse

Bug#1033488: Idea: use CROSS_GRADE_TO_ARCH, if set.

[Geert Stappers]

> cross-grading an ARM system from armhf to arm64

Idea for supporting such corner cases


if environmentvariable CROSS_GRADE_TO_ARCH is set
use it
else
dpkg --print-architecture



Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: no packages for 5.19.0-1-686

[Geert Stappers]

On Tue, Oct 25, 2022 at 12:12:08AM +0200, Geert Stappers wrote:
> 
> Hi,
> 
> With package debian-installer-12-netboot-i386 version 20220917+rebuild1 
> and an deb.debian.org as mirror, I got today
> 
>   anna[1546]: WARNING **: no packages matching running kernel 5.19.0-1-686 in 
> archive
> 
> 
> What is your advice on this?
> 
>  * Install an older Debian on that old hardware?
>  * Do other good things while it is being fixed?
>  

With the netboot.tar.gz from
 
https://ftp.nl.debian.org/debian/dists/bullseye/main/installer-i386/current/images/netboot/
the install continues.   \o/

 
> Groeten
> Geert Stappers
> Was surprised upon finding a debian-installer-12-netboot-i386 package

Was thinking that "i386" is no longer a release architecture.


Groeten
Geert Stappers
Didn't retry with package debian-installer-12-netboot-i386 version 
20220917+rebuild1 content
-- 
Silence is hard to parse

no packages for 5.19.0-1-686

[Geert Stappers]

Hi,

With package debian-installer-12-netboot-i386 version 20220917+rebuild1 
and an deb.debian.org as mirror, I got today

  anna[1546]: WARNING **: no packages matching running kernel 5.19.0-1-686 in 
archive


What is your advice on this?

 * Install an older Debian on that old hardware?
 * Do other good things while it is being fixed?
 

Groeten
Geert Stappers
Was surprised upon finding a debian-installer-12-netboot-i386 package
-- 
Silence is hard to parse

Re: Debian installer improvement suggestion

[Geert Stappers]

On Wed, Oct 05, 2022 at 05:01:53PM +0200, ben.gruse...@free.fr wrote:
> From: "Geert Stappers" 
> To: debian-boot@lists.debian.org
> > On Wed, Oct 05, 2022 at 12:48:54PM +0200, ben.gruse...@free.fr wrote:
> > > 
> > > Please have a look at this thread on the BunsenLabs forum regarding
> > > the bullseyes installer not detecting the cdrom while installing a
> > > new debian distro (BunsenLabs obviously) from and SD card:
> > > 
> > >   https://forums.bunsenlabs.org/viewtopic.php?pid=123929#p123929 
> > 
> > As I understood it:
> > 
> >ISO image
> >booting from non-CD-ROM-device ( e.g. thumb-drive SD-card)
> >boot is succesfull, debian-installer being started
> >d-i finds "I'm a ISO image"
> >d-i goes looking for CD-ROM-device
> >the CD-ROM-device is NOT found
> > 
> > The issue has "solutions" as 
> > 
> >  mount the_actual_device  /cdrom
> > 
> > 
> > I think the real solution is using  "HDD imsage".
> > (Or doing a netboot install)
> > 
> > So not using an image that is expecting a CD-ROM-device.
> > 
> thanks for your answer - obviously still learning here; i like you detailed 
> explanation
 
thanks for the thanks

 
> > > Thanks for your hard hard, rest assured it is really appreciated. 
> > 
> > In my best French:  Logiciel libre c'est ne pas logiciel gratuit.
> > 
> > 
> > My actual point:  Do more as just suggesting
 
Such reporting how good are the non-CD-ROM-images.

 
> best regards
> ben
 


Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: Debian installer improvement suggestion

[Geert Stappers]

On Wed, Oct 05, 2022 at 12:48:54PM +0200, ben.gruse...@free.fr wrote:
> 
> Hi all, 
> 
> 
> Please have a look at this thread on the BunsenLabs forum regarding
> the bullseyes installer not detecting the cdrom while installing a
> new debian distro (BunsenLabs obviously) from and SD card:
> 
>   https://forums.bunsenlabs.org/viewtopic.php?pid=123929#p123929 
 


As I understood it:

   ISO image
   booting from non-CD-ROM-device ( e.g. thumb-drive SD-card)
   boot is succesfull, debian-installer being started
   d-i finds "I'm a ISO image"
   d-i goes looking for CD-ROM-device
   the CD-ROM-device is NOT found

The issue has "solutions" as 

 mount the_actual_device  /cdrom


I think the real solution is using  "HDD imsage".
(Or doing a netboot install)

So not using an image that is expecting a CD-ROM-device.


> I suspect you are probably already aware of the issue... 

(-:

  Let me fill in the dots:

 Scott Adams,  Robert Greene and others have it documented.


:-)

Joking aside:
I don't know if "ISO image" has source code like

   If
  CD-ROM-device not found
   then
  register the attempt
  try next reasonable alternative


   If
  reasonable alternative failed
   the
  register the attempt
  try other option


   If
  other option failed
   then
  Present user nice text which says something like

 Mismatch on expection
 for attempt in list of registered_attempts
attempt has failed
 Retry another combination of install media and hardware


   # Continue
   Installation


> Thanks for your hard hard, rest assured it is really appreciated. 

In my best French:  Logiciel libre c'est ne pas logiciel gratuit.


My actual point:  Do more as just suggesting


> Best regards 
> ben 

No hard feelings

 
Groeten
Geert Stappers
-- 
Silence is hard to parse

Bug#1015887: debian-installer: Adding https repo doesn't work without manually installing ca-certificates

[Geert Stappers]

On Sun, Jul 24, 2022 at 12:15:24AM +1200, Richard Hector wrote:
> On 23/07/22 23:01, Cyril Brulebois wrote:
> 
> > As mentioned by Julien, getting the installer's syslog (compressed, to
> > make sure it reaches the mailing list) would help understand what's
> > going on.
> 
> Oh - uncompressed, it made it into the BTS,
 
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=1015887;filename=syslog;msg=27

Jul 23 01:08:13 in-target: Err:1 https://deb.debian.org/debian bullseye 
InRelease
Jul 23 01:08:13 in-target:   Certificate verification failed: The certificate 
is NOT trusted. The certificate issuer is unknown.  Could not handshake: Error 
in the certificate verification. [IP: 2a04:4e42:27::644 443]
Jul 23 01:08:13 in-target: Reading package lists...
Jul 23 01:08:13 in-target: 
Jul 23 01:08:13 in-target: W: 
https://deb.debian.org/debian/dists/bullseye/InRelease: No system certificates 
available. Try installing ca-certificates.
Jul 23 01:08:13 in-target: W: Failed to fetch 
https://deb.debian.org/debian/dists/bullseye/InRelease  Certificate 
verification failed: The certificate is NOT trusted. The certificate issuer is 
unknown.  Could not handshake: Error in the certificate verification. [IP: 
2a04:4e42:27::644 443]
Jul 23 01:08:13 in-target: W: Some index files failed to download. They have 
been ignored, or old ones used instead.
Jul 23 01:08:13 apt-setup: dpkg-divert: warning: diverting file 
'/sbin/start-stop-daemon' from an Essential package with rename is dangerous, 
use --no-rename
Jul 23 01:08:14 in-target: Err:1 https://deb.debian.org/debian bullseye 
InRelease
Jul 23 01:08:14 in-target:   Certificate verification failed: The certificate 
is NOT trusted. The certificate issuer is unknown.  Could not handshake: Error 
in the certificate verification. [IP: 2a04:4e42:27::644 443]
Jul 23 01:08:14 in-target: Reading package lists...
Jul 23 01:08:14 in-target: 
Jul 23 01:08:14 in-target: W: 
https://deb.debian.org/debian/dists/bullseye/InRelease: No system certificates 
available. Try installing ca-certificates.
Jul 23 01:08:14 in-target: W: Failed to fetch 
https://deb.debian.org/debian/dists/bullseye/InRelease  Certificate 
verification failed: The certificate is NOT trusted. The certificate issuer is 
unknown.  Could not handshake: Error in the certificate verification. [IP: 
2a04:4e42:27::644 443]
Jul 23 01:08:14 in-target: W: Some index files failed to download. They have 
been ignored, or old ones used instead.


no traces of manual install of ca-certificates found by me.


Regards
Geert Stappers
Failed to explain that httpS is NOT needed for apt.
Agrees that it is nice to have ca-certificates installed.
-- 
Silence is hard to parse

Bug#1015887: debian-installer: Adding https repo doesn't work without manually installing ca-certificates

[Geert Stappers]

Control: severity -1 wishlist

On Sat, Jul 23, 2022 at 03:49:55PM +1200, Richard Hector wrote:
> Dear Maintainer,
> 
> Using netinst bullseye 11.4 installer:
> 
> https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-11.4.0-amd64-netinst.iso
> 
> I chose to add a network mirror, using https, and the default
> 'deb.debian.org'.
> 
> I used (non-graphical) Expert Mode.
> 
> The problem first showed up when tasksel only displayed 'standard system
> utilities'. When I went ahead with that, the next screen was a red
> 'Installation step failed' screen.
> 
> The log on tty4 showed various dependency problems.
> 
> I tried to 'chroot /target' and 'apt update', which showed certificate
> problems. I then ran 'apt install ca-certificates', which worked
> (installing from the cd image?), after which 'apt update' worked, and I
> was also able to continue successfully with the installer.
> 
> I was able to reproduce this in a (kvm/qemu) VM (which is where I
> confirmed my steps); the original problem was on an HP Thin Client
> (t520). In both cases only 8G of storage was available.
> 
> It all works fine using http for the mirror.

And the archive mirror content is secured by checksums and signatures.

 
> I'm happy to do further testing with the VM; the thin client is less
> convenient as it has a job to do.

Another job that will help: Find other bug reports that ask for installing
ca-certificates.  Yeah, I recall have I seen such requests before.


Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: Net boot auto install failure with "No device for installation media was detected"

[Geert Stappers]

On Thu, Jul 21, 2022 at 06:26:09AM -0700, Shane Gibson wrote:
> On Wed, Jul 20, 2022 at 11:17 PM Geert Stappers 
> wrote:
>
> > > "No device for installation media was detected."
> >
> > My guess:   New hardware.
> >
>
> Thx for the response - I do appreciate.  The device being installed is a
> virtual machine in KVM, which has deployed previous Debian distros without
> issue.  I believe the "installation media" not being detected is related to
> changes between Buster and Bullseye - but I can't seem to find any
> changelogs on what has changed.

 ;-)


> > Please report back how a manual install goes.  As in: Share with the
> > community wether or not it is a netboot / preseed problem.
> >
>
> Manual installation from the same ISO works fine.
>

Check the install logs of that succesfull installation.
Pay special attention to the storage device.


Rerun the preseeded installation where the
> > > d-i partman-auto/disk string /dev/sda
> > > d-i grub-installer/choose_bootdev select /dev/sda
> > > d-i grub-installer/bootdev string /dev/sda
has the /dev/sda replaced with information from the succesfull install.
I do recall something like /dev/xda seen on a VM.  I might be wrong
about that. If it works report back.  If it doesn't work surely report
back with install logs of both (the succesfull manual one and the failed
preseed one).



Groeten
Geert Stappers
-- 
Silence is hard to parse


signature.asc
Description: PGP signature

Re: Net boot auto install failure with "No device for installation media was detected"

[Geert Stappers]

On Wed, Jul 20, 2022 at 08:02:20PM -0700, Shane Gibson wrote:
> Greetings,
> 
> We have an automated installation system that has been humming along
> beautifully from Debian 6 through 10.  Recently attempted to add support of
> net boot/pxe and autoinstall via d-i of Debian 11.4.0.  Our current Boot
> arguments and preseed config is producing a stop error of:
> 
> "No device for installation media was detected."

My guess:   New hardware.

 
> I saw notes that there should be netinst changes to boot and preseed
> directives - but I have been unable to unearth the changes.   Any pointers
> to documentation about the boot and preseed directive changelog changes, or
> any other hints related to this error message are greatly appreciated.   To
> date, I've spent a couple of days grubbing through searches, doc reading,
> etc... no dice.
> 
> For reference, the pxelinux boot directives and preseed that result in the
> above error message; are set to...  Note that the contents of the 11.4.0
> netinst ISO image are exploded out and available at the referenced preseed
> location 192.168.124.1:8091/debian-11/install
> 
> boot arguments:
> 
> DEFAULT debian-11-install
> PROMPT 0
> TIMEOUT 10
> LABEL debian-11-install
>   KERNEL debian-11/install/install.amd/vmlinuz
>   INITRD debian-11/install/install.amd/initrd.gz
> 
>   APPEND auto 
> preseed/url=http://192.168.124.1:8091/machines/821ea995-4813-4b01-a28d-e63874fe9a26/seed


Please report back how a manual install goes.  As in: Share with the community
wether or not it is a netboot / preseed problem.



Regards
Geert Stappers
DD
-- 
Silence is hard to parse


signature.asc
Description: PGP signature

Re: d-i user questions, web proxies, automated installation

[Geert Stappers]

On Sun, Mar 27, 2022 at 03:43:47PM +0200, Marc Haber wrote:
> Hi,
> 
> ... intro ...

Welcome
 
> In a small side project I am currently helping a company to design and
> implement a deployment process for embedded Debian to a headless
> multimedia controller based on amd64 (sic!). Those machines do have HDMI
> and USB, but hidden away inside the box so you need to open the case to
> access those ports. I would like to avoid that at least for the bulk of
> installations.
> 
> Unfortunately, I find the Installation Guide a bit terse on the topic of
> preseeded, headless installation, but am prepared to help improving the
> document. I would probably need some guidance in finding the "right" way
> to do things before writing them down (or, if weirdness turns out to be
> a bug, filing the appropriate bugs) and am wondering whether this list
> might be the correct medium to answer installation questions regarding
> preseeding. I am afraid that technical questions regarding preseeding
> will get drowned on debian-user, and probably not find in-depth answers
> on debian-user-german.
> 
> After a preseeded installation, a common task is to hand over the
> freshly installed system to some kind of configuration management like
> puppet. I have seen more or less ugly methods do to that, including a
> multi-hundred character long shell string as d-i preseed/late_command
> with advanced multi level quoting hell, having an localinit.deb which is
> installed along with the base system and which does that initialization
> and enrollment after first reboot into the fresly installed system,
> staying around for the entire life of the box, etc. Is there any
> documentation / opinion about doing this more elegantly?
> 
> And then: Can I have a single pre-seed file that would allow me to
> configure the Installer and Apt to choose the first web proxy from a
> list of proxies defined in some pre-seed data field, choosing the first
> one that happens to be available and responding, falling back to direct
> connection if none of the proxies is there? That would allow me to use
> the same Installer image for installations in a variety of places with
> various differnt proxy setups, avoiding the work to have an Installer
> image per site (giving the users the possibility to fail by just
> choosing the wrong USB stick).
 
A few days (a week?) ago wrote Phill something like
   There is https://hands.com/d-i/
   and would like revisited together with you
   for recent release
(Yeah, I staid in my email program, didn't visit the archive of
the mailinglist for the exact text)

> Imagine that I have a remote system in a network that I don't manage,
> for example a hosting network. I have a box running some kind of
> unnamed linux, a locally provided rescue system, or grml. I am currently
> installing in such environments by debootstrapping manually, chrooting
> into that system and using my existing configuration management to
> "personalize" the installation. Is there a possibility to start d-i
> proper in such a system to get all of d-i's magic, probably skipping
> partitioning and filesystem creation (that might already been done)?

url=the.remote.system
as boot parameter.
 

> And last question: How seriously pluggable is the Installer? Can I, for
> example, build my own udeb for apt configuration or my own, much less
> flexible partitioner and just throw those udebs into an installer tree
> and directly use it? Or do I need to delve in-depth into the build
> process of the entire Installer to do that?

Begin.
Start with what is already available.
That way you can find "your missing piece".
When "found" start wondering about how to optimize development
of the new piece.
 

> Thanks for helping. No need to Cc me any more, I am subscribed now.

Please consider to have one subject in a thread.

 
> Greetings
> Marc


Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: arm64/daily/netboot/debian-installer/arm64/initrd.gz - netconf crashes in an endless loop

[Geert Stappers]

On Wed, Mar 23, 2022 at 10:04:46PM +0100, Thomas Glanzmann wrote:
> Hello,
> so now that we have figured out how to see the debian installer, a few
> dialogs later (just before the network config) 'netconf' seems to crash
> in an endlessloop. See video:
> 
> https://tg.st/u/VID_20220323_215052568.mp4
 
At 0:06 of the 0:07 movie is MAC 00e04c682e37

Website https://macvendors.com hints it is
a NIC from realtek semiconductor.

Should the MacBook Air have such Network Interface Card?
Or is the NIC  on USB?

On the shell of the installer, which information can you get there?
What shows `ip a`?


> Cheers,
> Thomas
 
 
Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: Possible to force installing from the mirror instead of the installation media?

[Geert Stappers]

On Mon, Feb 21, 2022 at 12:05:53PM +0800, Glen Huang wrote:
> Hi,
> 
> I remember reading it somewhere in a Debian doc (though I can no
> longer find it) that only netboot automatically installs the base
> system from a mirror, other media install from the media itself and
> then upgrade via the mirror if allowed.
> 
> I wonder if it's possible to force the installer to use the mirror for
> installing the base system? Currently, my installer installs two
> versions of kernels, one from the media, the other from upgrading via
> the mirror, which seems like a waste.
> 
> I couldn't find the preseed directive that controls this.

:-)



Visit https://www.debian.org with a recent webbrowser
Click "download" to go to https://www.debian.org/download
Qouting that page:

  Thank you for downloading Debian!

  This is Debian 11, codenamed bullseye, netinst, for 64-bit PC (arch).

  If your download does not start automatically, click 
debian-11.2.0-arch-netinst.iso.

  Download checksum: SHA512SUMS Signature


The page presents also downloading debian-11.2.0-arch-netinst.iso.


> Would be grateful if someone could shed some light.

It is "netinst" that you are looking for.
At https://www.debian.org/distrib/ is that documented.
Page https://www.debian.org/download has the "distrib page" linked
in the section "Other Installers". Text from the distrib page:

   A small installation image: can be downloaded quickly and should be
   recorded onto a removable disk. To use this, you will need a machine
   with an Internet connection.


Page not linked on the download page
is www.catb.org/~esr/faqs/smart-questions.html  Introduction text from that
page:

   In the world of hackers, the kind of answers you get to your technical
   questions depends as much on the way you ask the questions as on the
   difficulty of developing the answer. This guide will teach you how
   to ask questions in a way more likely to get you a satisfactory answer.

 
> Regards,
> Glen

Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: Would allowing preseed to be a tarball a good idea?

[Geert Stappers]

On Fri, Feb 18, 2022 at 03:32:37PM +0100, Geert Stappers wrote:
> On Fri, Feb 18, 2022 at 03:55:30PM +0800, Glen Huang wrote:
> > On Feb 18, 2022, at 4:48 AM, Geert Stappers wrote:
> > >> On Feb 16, 2022, at 5:50 PM, Geert Stappers wrote:
> > >>> 
> > >>> The initrd of d-i can indeed be extended / appended.
> > >>> And in the "appendix" goes the desired extras. Then
> > >>> 
> > >>> d-i  preseed/early_commands  /myextras/early_script
> > >> 
> > >> If I’m not wrong, this requires repackaging the installer media?
> > > 
> > > Nope, append is append,  not repackaging.
> > 
> > The ideas sounds very interesting, but due to my limited knowledge
> > with regard to initrd, I have no idea what it means to “append”
> > to it. Googling “debian initrd append” or "initrd append” or
> > "initrd appendix” revealed nothing useful AFAICS. I wonder if you
> > could point me to some documents/manuals where I’d have a better
> > chance understanding it?
> 
> https://wiki.debian.org/DebianInstaller/NetbootFirmware#The_Solution:_Add_Firmware_to_Initramfs
>  
> 
> > My current mental model is like this: initrd bundles a temporary fs to
> > facilitate the startup process. You can change the files it contains
> > using a tool like cpio. So shouldn't appending files to it mean changing
> > the initrd file? If initrd file needs to be changed, shouldn’t the
> > installer media also be changed to incorporate the changed initrd file?
> > 

IIRC I have seen boot loaders that accept multiple 'initrd=path/to/file'
and assemble those initrd pieces to one single initrd for the kernel.



Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: Would allowing preseed to be a tarball a good idea?

[Geert Stappers]

On Fri, Feb 18, 2022 at 03:55:30PM +0800, Glen Huang wrote:
> On Feb 18, 2022, at 4:48 AM, Geert Stappers wrote:
> >> On Feb 16, 2022, at 5:50 PM, Geert Stappers wrote:
> >>> 
> >>> The initrd of d-i can indeed be extended / appended.
> >>> And in the "appendix" goes the desired extras. Then
> >>> 
> >>> d-i  preseed/early_commands  /myextras/early_script
> >> 
> >> If I’m not wrong, this requires repackaging the installer media?
> > 
> > Nope, append is append,  not repackaging.
> 
> The ideas sounds very interesting, but due to my limited knowledge
> with regard to initrd, I have no idea what it means to “append”
> to it. Googling “debian initrd append” or "initrd append” or
> "initrd appendix” revealed nothing useful AFAICS. I wonder if you
> could point me to some documents/manuals where I’d have a better
> chance understanding it?

https://wiki.debian.org/DebianInstaller/NetbootFirmware#The_Solution:_Add_Firmware_to_Initramfs
 

> My current mental model is like this: initrd bundles a temporary fs to
> facilitate the startup process. You can change the files it contains
> using a tool like cpio. So shouldn't appending files to it mean changing
> the initrd file? If initrd file needs to be changed, shouldn’t the
> installer media also be changed to incorporate the changed initrd file?
> 
> Regards,
> Glen


Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: Would allowing preseed to be a tarball a good idea?

[Geert Stappers]

On Thu, Feb 17, 2022 at 12:37:04PM +0800, Glen Huang wrote:
> 
> @Philip
> > On Feb 16, 2022, at 5:48 PM, Philip Hands  wrote:
> > 
> > Glen Huang  writes:
> > 
> >> Hi,
> >> 
> >> Currently, the preseed file needs to be a text file. I find it to be a
> >> bit limiting, especially if you want to do some non-trivial scripting
> >> in either early_command or late_command (let's call them runners).
> >> There are basically four options to address it AFAIK:
> > 
> > You can do rather complicated stuff actually, as seen in my (somewhat
> > rusty) example here:
> > 
> >  https://hands.com/d-i/
> 
> I learned a few tricks, thanks for sharing it.
> 
> I didn’t know about preseed/run, somehow missed it when reading
> the doc for the first time. It does #3 in a pretty elegant way, and
> with pressef_fetch, they basically allow me to treat the web server
> as a tarball.
> 
> @Geert
> > On Feb 16, 2022, at 5:50 PM, Geert Stappers  wrote:
> > 
> > The initrd of d-i can indeed be extended / appended.
> > And in the "appendix" goes the desired extras. Then
> > 
> > d-i  preseed/early_commands  /myextras/early_script
> 
> If I’m not wrong, this requires repackaging the installer media?
> 

Nope, append is append,  not repackaging.


> I do still think a direct tarball support would be icing on the
> cake. You can upload it to some public service and maybe shorten the
> url and then directly use it, obviating the needs for setting up a web
> server.

Yes, having a webserver with your extras  will you gain you the benefits
of getting the desired extras.

So go for it   :-)


> But I agree the current utilities provided by the installer
> already make things a breeze, so I wouldn’t complain. :)

(-:I ignore complains, but do listen to improvement proposals   :-)


 
> Regards,
> Glen

Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: Would allowing preseed to be a tarball a good idea?

[Geert Stappers]

On Wed, Feb 16, 2022 at 05:32:23PM +0800, Glen Huang wrote:
> > On Feb 16, 2022, at 5:19 PM, Glen Huang  wrote:
> >
> > Hi,
> >
> > Currently, the preseed file needs to be a text file. I find it to
> > be a bit limiting, especially if you want to do some non-trivial
> > scripting in either early_command or late_command (let's call them
> > runners). There are basically four options to address it AFAIK:
> >
> > 1. Strictly use one-liners in runners.
> > 2. Bundle the scripts in the install media, to be called by the
> >runners.
> > 3. Make runners download the scripts and then run them.
> > 4. Embed the scripts in preseed and then make runners redownload it,
> >parse the scripts out and run them.
> >
> > All of them are flawed:
> >
> > 1. If done manually, this is really awkward, and since in-target
> >uses chroot under the hood, you can’t use redirects directly,
> >not without sh -c, also awkward.
> > 2. The official install media can no longer be used directly, and
> >for a lot environments using a custom install media is not an option.
> > 3. This means you need to set up a web server that the installer
> >can access, which is quite painful, and the installer might not have
> >access to the Internet.
> > 4. This is the approach I currently take. However, it’s also
> >quite awkward, since each line of the embedded content has to be
> >commented out, and you also have to invent ad hoc file delimiters,
> >and it doesn’t work for binary files (unless (en|de)coded by base64
> >of course).
> >
> > I think there are many cases that require non-trial scripting. A
> > strong one could be doing provisioning in late_command.
> >
> > I wonder if allowing preseed to be a tarball would be a good idea? It
> > could define a content structure like this:
> >
> > early_commands/   # run executables in it at the point of early_command
> > late_commands/  # run executables in it at the point of late_command
> > late_in_target_commands/ # run executables in it at the point of 
> > late_command, chrooted to /target
> > in_target_files/ # files in it are copied to /target after installation 
> > finishes, maybe before late_command
> 
> Forgot a few things.
> 
> 1. #4 also means the preseed file needs be downloaded twice, since
>the one downloaded by the installer is immediately removed once the
>preseed is loaded into debconf db, before early_command.
> 2. Files parsed out in #4 needs to be stored somewhere. No matter
>where you place them, there is no guarantee that (future versions of)
>d-i won’t touch them.
> 3. The tarball should contain a /preseed file to provide the preseed.
> >
> > Thoughts?

The initrd of d-i can indeed be extended / appended.
And in the "appendix" goes the desired extras. Then

d-i  preseed/early_commands  /myextras/early_script


Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: Unable to set root password with clear text using preseed/early_command

[Geert Stappers]

On Tue, Feb 15, 2022 at 08:08:08PM +0800, Glen Huang wrote:
> Hi,
> 
> I want to set the root password to a random string. this is the preseed I use:
> 
> d-i preseed/early_command string \
> pw="$(tr -dc A-Za-z0-9  debconf-set passwd/root-password "$pw"; \
> debconf-set passwd/root-password-again "$pw"
> 
> However, the installer still prompts me for the root password.
> 
> Setting the crypted password works though:
> 
> d-i preseed/early_command string \
> debconf-set passwd/root-password-crypted ''
> 
> Directly setting the password also works:
> 
> d-i passwd/root-password password r00tme
> d-i passwd/root-password-again password r00tme
> 
> From https://sources.debian.org/src/user-setup/1.88/user-setup-ask/#L36,
> it seems the installer will ask for the root password if
> root-password-crypted is empty or !. My guess is that in the direct
> version, somehow root-password-crypted gets a corresponding value when
> only root-password and root-password-again are set, but I couldn't
> find the code responsible for that.
> 
> I'd be grateful if anyone could shed some light.
> 

Completely UNtested, a.k.a.  sharing a thought:

  d-i preseed/early_command string \
  tr -dc A-Za-z0-9  /tmp/pw ; \
  cat /tmp/pw | debconf-set passwd/root-password - ; \
  cat /tmp/pw | debconf-set passwd/root-password-again -

 
Groeten
Geert Stappers
Not knowing how much of the early_command_string gets into log file.
-- 
Silence is hard to parse

Re: At what time of the install process a script is executed with 'preseed/run'?

[Geert Stappers]

  
> In the description text, to me at least, it is not clear at what stage
> this command is executed!!! :)
> Having played a bit more, I can confirm that this command is not
> executed at the end of the installation process.
> 
> While I was looking to understand what was going on, I came across (1)
> and this is where Ubuntu differs from Debian:
> 
> "on a web server. In this example, if the preseed file sets preseed/run
> to /scripts/late_command.sh then the file will be fetched from
> http://autoserver.example.com/d-i/focal/./scripts/late_command.sh.;
> 
> I would love to see a rewording of the above text which would clearly
> state at what time the command is executed!!! :)
> 
> I realy appreciate your help.


That starts with smiling to the "works for me".
Next step is documenting how to reproduce "how it fails for me"
 

Groeten
Geert Stappers

1)  https://help.ubuntu.com/lts/installation-guide/s390x/apbs02.html
-- 
Silence is hard to parse

Re: At what time of the install process a script is executed with 'preseed/run'?

[Geert Stappers]

On Sun, Dec 26, 2021 at 07:18:26PM +0100, john doe wrote:
> On 12/26/2021 5:44 PM, Holger Wansing wrote:
> > Am 26. Dezember 2021 17:30:03 MEZ schrieb john doe:
> > > Debians,
> > > 
> > > From a preseed file I need to download and execute as the last command
> > > a script.
> > > I'm playing with 'd-i preseed/run string foo.sh' the script execute
> > > successfully but does not look to be executed as the last command in the
> > > install process.
> > > 
> > > Can someone confirm when 'preseed/run' is executed?
> > > 
> > > In other words, what is the best way to download and execute a script at
> > > the end of the install process.
> > 
> > Not exactly answering your question, but the installation-guide
> > has a chapter about this, see
> > https://d-i.debian.org/manual/en.amd64/apbs05.html

Qoute from that page
#d-i preseed/late_command string apt-install zsh; in-target chsh -s /bin/zsh
> > 
> > I guess, "preseed/late_command is what you want...
> > 
> 
> Actually I was more hoping for an equivalent of 'preseed/run' to the
> 'preseed/late_command'.
> The late_command will not per default download the *.sh file.

This is untested:

d-i preseed/late_command string in-target wget -O /target/myscript 
http://server.local/install_script ; in-target bash /myscript


Consider to share with the mailinglist (and the mailinglist archive)
what worked for you.


Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: At what time of the install process a script is executed with 'preseed/run'?

[Geert Stappers]

On Sun, Dec 26, 2021 at 05:30:03PM +0100, john doe wrote:
> Debians,
> 
> From a preseed file I need to download and execute as the last command
> a script.
> I'm playing with 'd-i preseed/run string foo.sh' the script execute
> successfully but does not look to be executed as the last command in the
> install process.
> 
> Can someone confirm when 'preseed/run' is executed?
> 
> In other words, what is the best way to download and execute a script at
> the end of the install process.

$ curl --silent https://d-i.debian.org/manual/en.arm64/apbs04.html | grep -e 
script
by creating a “preseed/run” script containing the following

 
> Any help is appreciated.

Express your self  for further help.

 
> John Doe
 

Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: Problem preseeding wifi password

[Geert Stappers]

On Wed, Nov 10, 2021 at 06:08:22PM -0800, VDRU VDRU wrote:
> On Wed, Nov 10, 2021 at 12:13 PM Geert Stappers  wrote:
> > On Wed, Nov 10, 2021 at 11:27:37AM -0800, VDRU VDRU wrote:
> > > >
> > > Hi, thanks for your reply! No, there are no single/double-quotes,
> > > apostrophes, or dollar signs. The password contains a-z, A-Z, 0-9, and
> > > _ only.
> > >
> > > Another thing I noticed but didn't mention is that in the ssid list,
> > > it splits the ssid into two entries in the menu. There's a "," in the
> > > ssid name and that's where the split occurs. No "," is shown in either
> > > menu entry. Maybe the ssid list is comma-separated rather than using a
> > > character that can't or is less likely to appear in a ssid? This seems
> > > to just be a cosmetic issue but could confuse users as to which entry
> > > to select in cases like that. Since my primary problem is the password
> > > preseeding and unrelated to this, I didn't mention it before.
> >
> > And is (temporary) removing the , from the SSID  tested?
> 
> Ok, I managed to make some time to do some wifi testing, much to my
> family's disgust. :)

Auch, that hurts
 

> Regarding preseeding the wifi password, I tried in this order:
> - removing the underscores from the password
> - cutting the password from 60 to 33 chars (alphanumeric only)
> - cutting the password down to 32 chars (alphanumeric only)
> - cutting the password down to 8 chars (alphanumeric only)
> - removing the "," from the ssid
> - trying a ssid consisting of 11 lowercase chars only
> - changed router security from "WPA2 - Personal" to "WPA/WPA2 - Personal"
> - changed router encryption from AES to AES/TKIP
> 
> None of these worked. Preseeding the password failed in all cases,
> even with a simple alphanumeric-only ssid and password.
> 
> Regarding an ssid with a "," in it creating two menu entries:
> If there ssid is "heres a, test ssid", it will result in a menu that looks 
> like:
> heres a
> test ssid
> 
> If I select either entry and enter the password, it fails. If I
> manually enter "heres a, test ssid" and then enter the password, it
> works fine. If I removed the "," so the ssid is "heres a test ssid",
> selecting the single "heres a test ssid" entry works fine.
> 
> So, to summarize... Using an ssid with a comma in it causes the
> installer to split the ssid into multiple menu entries at the comma,
> but manually entering a ssid with a comma works fine.

OK
As in "OK, that fits the expectations"


> And, preseeding just a wpa password fails in all cases.

That is unexpected.

Disclosure:
I myself never did preseed WIFI password.
(and didn't noticed previous reports about it not working)

I hope that this messages triggers  "works for me" notifications.
 
> Another discovery I made is that the wifi device wants nonfree
> firmware "rtlwifi/rtl8192cufw.bin". If I copy
> "rtlwifi/rtl8192cufw.bin" to the root dir of the usb stick, the
> installer fails to find it when I select yes. If I unplug the usb
> stick and connect it in a different usb port and select yes again, the
> installer finds it but sometimes takes a few tries. Maybe it's a good
> idea to have the installer automatically check the root dir of the usb
> it booted from for any missing firmware before asking the user for it?

I can't tell if effects the problem from the subject line.

 
> And the last thing I'll mention is the font used in the graphical
> installer isn't great when it comes to entering passwords. I found
> that at least the "I" (capital i) and "l" (lowercase L) look
> identical. That makes it a pain to verify a password was entered
> correctly.
> 
> Thanks for checking this stuff!
 
Thanks for the compliment.

 
Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: Problem preseeding wifi password

[Geert Stappers]

On Wed, Nov 10, 2021 at 11:27:37AM -0800, VDRU VDRU wrote:
> On Wed, Nov 10, 2021 at 10:59 AM Steve McIntyre  wrote:
> > On Wed, Nov 10, 2021 at 10:07:41AM -0800, VDRU VDRU wrote:
> > >Hi.
> > >
> > >Using the Debian testing net installer iso. I have a wifi password
> > >that is 60 chars long that contains underscores. When I preseed it
> > >with "d-i netcfg/wireless_wpa ", the installer spits out an
> > >error that the password is either too long (>64 chars) or too short
> > >(<8 chars). Neither is true and if I enter it manually instead of
> > >preseeding it, there's no problem. I have tried preseeding the
> > >password with and without quotes around it with no success. The only
> > >thing that comes to mind is maybe the underscores (or special chars in
> > >general) are not handled correctly by the installer..? I'm not sure a
> > >bug report is warranted just yet so I'm hoping to get feedback on the
> > >above before going that route.
> >
> > Hmmm, that's odd. I have to ask - does your long password contain
> > quotes (' or ") or $ symbols? Although the netcfg code here is in C,
> > it may end up using backend interfaces that might be confused by those
> > special characters. I have not tested this locally, but that would be
> > my immediate suspicion based on what you're describing...
> >
> Hi, thanks for your reply! No, there are no single/double-quotes,
> apostrophes, or dollar signs. The password contains a-z, A-Z, 0-9, and
> _ only.
> 
> Another thing I noticed but didn't mention is that in the ssid list,
> it splits the ssid into two entries in the menu. There's a "," in the
> ssid name and that's where the split occurs. No "," is shown in either
> menu entry. Maybe the ssid list is comma-separated rather than using a
> character that can't or is less likely to appear in a ssid? This seems
> to just be a cosmetic issue but could confuse users as to which entry
> to select in cases like that. Since my primary problem is the password
> preseeding and unrelated to this, I didn't mention it before.

And is (temporary) removing the , from the SSID  tested?

 
> Thanks!

Groeten
Geert Stappers
-- 
Silence is hard to parse

Bug#991867: Lamobo_R1

[Geert Stappers]

On Wed, Aug 04, 2021 at 01:51:49PM +1200, Nevyn wrote:
> 
> U-Boot works but loading kernel results in a blank screen (with cursor in
> top left corner).

And what happens on the serial port?




Regards
Geert Stappers
Has a R1, never used the HDMI port

Re: Installation comment

[Geert Stappers]

On Sun, Jul 25, 2021 at 03:43:18AM +1200, Richard Hector wrote:
> Hi all,
> 
> Sorry for the minimal detail - hopefully someone else will understand this
> much better than I do, and be able to fill in if required. Failing that, I
> might be able to do better later. Just spent many more hours on this than
> anticipated, and need sleep.
> 
> I installed bullseye on my HP ProBook 430 G3 (attempting to encrypt
> everything including /boot, but backed out of that - I don't think it was
> relevant in the end) - using UEFI. Grub failed to install. I looked at the
> logs on VT 3, and saw stuff about No space left on device. df showed my
> devices all seemed fine.
> 
> It turned out that my NVRAM was full of dump files. I don't know what
> they're for and why they had accumulated, but a page on the Arch wiki
> suggested deleting them, which allowed grub to install.
> 
> Is it worth putting comments about that in the release notes?

The way to go is having a closer look, finding out what is caused it,
solving the problem.

But hey, this email started with:   Sorry for the minimal detail ...

 
> Thanks,
> Richard
 


Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: /var/log mengling

[Geert Stappers]

On Fri, Jul 23, 2021 at 08:27:00PM -0300, __- -__ wrote:
> Hi,
> 
> Debian team list, we need a way to hardsoft ofuscating logs. It's very
> important to improvements related to hardware upgrades.
 
And what is actually "hardsoft ofuscation logs"?

I think / guess it is some kind of modification,
but what is desired to be altered into what???




 
Groeten
Geert Stappers
-- 
Silence is hard to parse

Bug#989593: installation report Raspberry Pi 4 UEFI

[Geert Stappers]

On Tue, Jun 08, 2021 at 09:49:15PM +0200, Marc Haber wrote:
>
> The more pressing issue IMO is the deletion of /sbin/start-stop-daemon.
>

Repeating this:

If you were to retry the installation, saving /var/log/syslog manually
before rebooting into the installed system would be useful. Without it,
I fear much guessing would be needed to try and figure out what happened
on that system specifically. Unless someone else has better ideas of
course.


Cheers,
--
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant

Re: Failure installing Debian Buster from netboot.tar.gz. Kernel not matching repository.

[Geert Stappers]

On Sat, Jun 05, 2021 at 06:57:32PM +0200, Guido Ackermann wrote:
> Hello,
> 
>  ...  please tell me how to fix this error to my
> netboot-infrastructure

What about fetching the netboot.tar.gz from the very same
repository as the repository used further in the install process?


> 
> regards
>   Guido Ackermann
>   Netzwerk & Systemspezialist
>   VRG-Grupppe
> 
> Schlage nie jemanden mit einer Brille.
> Nimm lieber einen Knüppel.



Regards
Geert Stappers
-- 
Silence is hard to parse

Re: How does the debian development team build Root Filesystems with Desktop UI Support?

[Geert Stappers]

On Wed, Jun 02, 2021 at 02:58:23PM +0900, Yuichi Tsujiwaki wrote:
> Hi, how does the debian development team create rootfs with a GUI?

AFAIK  not


> If you're using multistrap, could you please tell me where the config file
> is?
> I'm looking for a procedure to create a minimal Debian OS Root Filesystems
> with Desktop UI.


Do known there is in Debian the package `debos`


  Description: Debian OS builder
   debos is a tool to make creation of various Debian based OS "images"
   simpler. While most other tools focus on specific use-case, debos is
   more meant as a toolchain to make comon actions trivial while providing
   enough rope to do whatever tweaking that might be required behind
   the scenes.
  
  

HTH


Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: Netinstall over HTTPS with Custom Image

[Geert Stappers]

On Thu, May 13, 2021 at 02:00:01PM -0700, Nick Pleatsikas wrote:
> Hello,
> 
> There’s a net install setup that I’m having trouble with
>  ...
> Essentially here is the scenario:
> 
> We have a custom Debian image
> want to be able to remotely install this image using PXE.
> However, in order to meet certain security requirements,
> the remote systems have to PXE boot over HTTPS.
>  ...
> but if I’m going wildly in the wrong direction here I’m all
> ears for a better solution. If there’s anything you want me to clarify or
> try out, let me know and I’ll get back to you.

I see two solutions:
* Reconcider the security requirement a.k.a. be aware of how unsafe
  the environment is where the install happens.
* Abandon the idea of an image, transfer smaller parts over HTTPS.

 
> Thanks,
> 
> Nick Pleatsikas
> Site Reliability Engineer, ByteDance
> Email: nick.pleatsi...@bytedance.com

 
Groeten
Geert Stappers
-- 
Silence is hard to parse

Bug#987845: hardwired proxy settings by debian-installer with network-auto-config in proxy-auto-config network

[Geert Stappers]

On Fri, Apr 30, 2021 at 09:25:47PM +0200, Rado Q wrote:
> Installation network setup was auto-configured while the system was
> in a network with proxy-auto-config active.
> 
> Expectation:
> when choosing auto-configure-network during installation, the
> resulting system should be operative in every foreign environment.
> (think of notebook in roaming use)
> 
> Result:
> applications strictly following those hardwired configs can't operate
> outside the original installation network, where the given proxy exists,
> but nowhere else. PAC results during installation shouldn't be
> 'hardwired' into the system to last when moving to another network.
> 
> I tried to reproduce with WPAD or PAC in dhcp at home, but my knowledge
> of those technologies didn't suffice to set it up properly.
> If more info/details of the original network environment is required,
> then I must ask for permission to reproduce, can take time (school in 
> lockdown).
> 
> If the result is intentional for 'local use only', then this is no
> defect but feature-request to add another option to choose between
> 'automatic config for local use' and '... roaming use'.
> 

Acknowledge on the problem.

Which possible solutions do we see?


Groeten
Geert Stappers
-- 
Silence is hard to parse

Bug#987491: Fwd: Missing firmware not declared / kernel modules not included in initrd

[Geert Stappers]

Updating the issue with "previously missing information"

- Forwarded message from "Andrew M.A. Cater" -

Date: Sun, 25 Apr 2021 10:13:59 +
From: "Andrew M.A. Cater" 
To: debian-boot@lists.debian.org
Subject: Re: [AMD/ATI graphics] Missing firmware not declared / kernel modules 
not included in initrd

On Sun, Apr 25, 2021 at 10:26:42AM +0200, Holger Wansing wrote:
> Hi,
> 
> Holger Wansing  wrote (Sun, 25 Apr 2021 10:08:32 +0200):
> > >I don't understand:
> > >does this mean that the issue that you reported in
> > >https://lists.debian.org/debian-boot/2020/12/msg00026.html can be
> > >considered fixed? And that the situation improved between buster and
> > >bullseye?
> > 
> > For this (old) hardware: yes, seems so.
> > 
> > However, we have several user reports, that not installed firmware leads to 
> > problems 
> > like black or garbled screen.
> 
> To be more clear:
> 
> The main point of my report at
> https://lists.debian.org/debian-boot/2020/12/msg00026.html ist:
> the installer is - per design - unable to detect, that the hardware needs
> firmware to be installed.
> 
> And this situation did not change!
> 
> The bullseye installation yesterday did not install the firmware package.
> 
> What seems to have changed is:
> GNOME seems to work (at least on this hardware !!!), even without the 
> firmware 
> installed.
> 
> (Also: Look at the other reports I quoted in my mail above for more user 
> cases.)
> 
> 
> Holger
> 

Adding to this, if I may. 

I've got two machines which both turn out to need firmware-amd-graphics
rather than the more modern firmware-amdgpu.

Installing with Bullsye RC1 netinst for amd64 but NOT the unofficial firmware 
version. debian-bullseye-DI-rc1-amd64-netinst.iso 

Even on an expert text mode install.the installer does not prompt for the 
firmware-amd-graphics package to be installed - it does complain about 
Realtek ethernet drivers and a Ralink WiFi card suggesting that you install 
the firmware for these. Booting the install medium does show, in passing,
in text that you need Radeon firmware R600 for modesetting.

If you _do not_ install the firmware, then on these two machines at least
there is a fallback mode to 800x600x16 so graphics remains (just) usable.
GNOME and Wayland work but it's not really practicable.

AT that point, you can install firmware-amd-graphics and it just works.
The meta-package which does this is firmware-linux-nonfree which also includes 
amd64-microcode

Once the firmwre is installed, these machines will drive a 2k monitor

This is explicitly NOT amdgpu which is where people are reporting black 
screens and no output whatsoever, I think.

Hope this helps,

Andy C.
> 
> 
> -- 
> Holger Wansing 
> PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076
> 


- End forwarded message -


Those who feel more comformatable to close this issue than me,
should close this issue.


Groeten
Geert Stappers
-- 
Silence is hard to parse

Bug#987491: installation-reports: Successful install AMD A6 - nonfree AMD Radeon firmware needed

[Geert Stappers]

Moin moin,

On Sun, Apr 25, 2021 at 10:31:00AM +0200, Holger Wansing wrote:
> Hi,
> 
> "Andrew M.A. Cater"  wrote (Sat, 24 Apr 2021 15:26:00 
> +):
> > Initial boot:   [O ]
> > Detect network card:[O ]
> > Configure network:  [O ]
> > Detect media:   [O ]
> > Load installer modules: [O ]
> > Clock/timezone setup:   [O ]
> > User/password setup:[O ]
> > Detect hard drives: [O ]
> > Partition hard drives:  [O ]
> > Install base system:[O ]
> > Install tasks:  [O ]
> > Install boot loader:[O ]
> > Overall install:[O ]
> > 
> > Comments/Problems:
> > 
> > Requires non-free Radeon drivers for r600 - firmware-amd-graphics
> 
> please be more specific:
> What happened, when no firmware is installed?
> Did the system work so far (graphical UI is visible and usable)?
> Or was it suffering from problems like "black screen" or "garbled screen" as 
> other users reported?
> 

I think this installation report  now waits for one of these options

 * Reporter reports "It is okay, consider 'Requires non-free' as comment"
 * Reporter provides information which special install care
   the special hardware needs. Info that will help others.
 * Closed due "Time out"



Groeten
Geert Stappers
-- 
Silence is hard to parse


signature.asc
Description: PGP signature

Re: serial console install issues BIOS related

[Geert Stappers]

On Tue, Apr 13, 2021 at 12:42:41PM +1200, Richard Hector wrote:
> On 13/04/21 12:31 pm, Ben Hutchings wrote:
> > On Mon, 2021-04-12 at 13:48 +1200, Richard Hector wrote:
> > >
> > >   
> > > 
> > > But all that's irrelevant if I can't get to the linux commandline,
> > > because Syslinux is misbehaving.
> > > 
> > > Does anyone know if it's inherent in Syslinux that it won't work
> > > correctly with a 24-line serial terminal?
> > [...]
> > 
> > I think that syslinux is working through a BIOS-emulated display and
> > keyboard controller, and is not aware that a serial terminal is beign
> > used.  The code for SeaBIOS's serial console support is here:
> > <https://github.com/pcengines/seabios/blob/apu_support/src/sercon.c>.
> > It presents an 80x25 (or 40x25) text display as there is no VGA BIOS
> > mode number for 80x24.
> 
> Ah - so while syslinux can talk to a serial console, it's not using that in
> this case? Interesting, thanks. That could explain why I haven't seen this
> on previous serial console installations (an old Soekris box).
> 
> That might make it more difficult to solve in software, leaving more
> documentation as the only answer.

Please express proposals.



Regards
Geert Stappers
Voluntering for transforming update proposals into git commits.
-- 
Silence is hard to parse

Re: serial console install issues, all the links of the chain

[Geert Stappers]

On Tue, Apr 13, 2021 at 10:40:07AM +1200, Richard Hector wrote:
> On 12/04/21 6:18 pm, Geert Stappers wrote:
> } On Sun, Apr 11, 2021 at 10:05:22PM -0600
> } } Maybe because of used putty or screen as the app for interaction.
> > 
> > Do we know the "path" that original poster is using?
> > 
> > Possible format for answer to this
> > 
> >   - APU device
> >   - 9-pin serial connector
> >   - null-modem, cross connects everthing
> >   - 9-pin serial connector
> >   - USB-Serial-Adapter
> >   - Linux computer
> >   - XFCE desktop
> >   - "terminal window", sized at 80x26 character
> >   - application `screen`
> >   - User
> 
> More or less right.

Acknowlegde


> I'm not sure of the specs of the null-modem cable; I found it amongst
> my collection of junk. For all I know it's straight through and the
> USB adapter autodetects - is that a thing?

Let's consider the cable stuff being fine.

 
> But I also don't see the significance - I've had no issues that look like
> communications problems, flow control problems or anything like that.

I agree on that. The
> } } Maybe because of used putty or screen as the app for interaction.
and especial putty got my attention. Because PuTTY is to me "SSH client
for Microsoft Windows". My question about "chain of links" was to find
out if we were dealing with

 - device
 - cable
 - Linux box or another computer with SSH server
 - PuTTY
 - MS Windows version 
 

Now we known for sure. Question
> > Do we know the "path" that original poster is using?
is being answered.   :-)


> Cheers,
> Richard
 

Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: serial console install issues, all the links of the chain

[Geert Stappers]

On Sun, Apr 11, 2021 at 10:05:22PM -0600, Raymond Burkholder wrote:
> On 4/11/21 8:37 PM, Richard Hector wrote:
> > On 11/04/21 11:51 am, Richard Hector wrote:
> > > Then finally, I can't remember how, I discovered that it didn't like
> > > displaying on a 24-line terminal, which most of the terminals I
> > > tried default to.
> > > 
> > > With a 25-line terminal, it all seems useable - and Minicom mostly
> > > displays it ok too (not quite right; the blue box isn't quite drawn
> > > properly, and seems too low on the screen?
> > 
> > Using Minicom, I found I have to use a 26-line terminal, because Minicom
> > displays a status line, so a 25-line terminal only leaves 24 lines
> > usable, and the same problems remain.
> > 
> 
> 
>   ... I've never really had problems with 24 or 25 line issues. 
> Maybe because of used putty or screen as the app for interaction.
> 

Do we know the "path" that original poster is using?

Possible format for answer to this

 - APU device
 - 9-pin serial connector
 - null-modem, cross connects everthing
 - 9-pin serial connector
 - USB-Serial-Adapter
 - Linux computer
 - XFCE desktop
 - "terminal window", sized at 80x26 character
 - application `screen`
 - User

 

Regarding
Geert Stappers
-- 
Silence is hard to parse

Re: serial console install issues before d-i is started

[Geert Stappers]

On Sun, Apr 11, 2021 at 11:26:36AM +0200, Samuel Thibault wrote:
> Richard Hector, le dim. 11 avril 2021 21:18:49 +1200, a ecrit:
> > On 11/04/21 9:10 pm, Samuel Thibault wrote:
> > > $ git grep -i "Boot console" .
> > > en/boot-installer/parameters.xml:  Boot console
> > > po/[...]
> > > 
> > > That's very most probably it.
> > 
> > I think so, yes. But my problems started earlier than booting linux, at the
> > SysLinux menu.
> 
> See the section, it talks about kernel arguments, which are passed from
> the syslinux menu. See the section just before, "Boot Parameters".

And feel free to report back.


Groeten
Geert Stappers
DD
-- 
Silence is hard to parse

Re: serial console install issues

[Geert Stappers]

On Sun, Apr 11, 2021 at 11:10:20AM +0200, Samuel Thibault wrote:
> Geert Stappers, le dim. 11 avril 2021 10:55:28 +0200, a ecrit:
> > On Sun, Apr 11, 2021 at 08:57:38AM +0200, Geert Stappers wrote:
> > > 
> > > On how to prevent that more people solve a solved problem
   ...
> > > 
> > >   https://www.debian.org/releases/buster/amd64/ch05s03.en.html
> > > 
> > > which has a section called 'Boot console'.
> > > 
> > 
> > `git clone https://salsa.debian.org/installer-team/installation-guide.git` 
> > plus `git grep ttyS0` did bring me not
> > the filename for "ch05s03.en.html" 
> > 
> > Where to find it?
> 
> $ git grep -i "Boot console" .
> en/boot-installer/parameters.xml:  Boot console
> po/[...]
> 
> That's very most probably it.
> 

Yes, it is.  So now there
is 
https://salsa.debian.org/installer-team/installation-guide/-/commit/a1c7f0400ce6136f0c330158a827155bc2e17203



Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: serial console install issues

[Geert Stappers]

On Sun, Apr 11, 2021 at 08:57:38AM +0200, Geert Stappers wrote:
> On Sun, Apr 11, 2021 at 11:51:57AM +1200, Richard Hector wrote:
> > 
> >   a serial port and no video hardware.
> > 
> 
> On how to prevent that more people solve a solved problem
> was a websearch done
> 
>   https://duckduckgo.com/q=debian+installer+serial+line
> 
> One of the first hits is
> 
>   https://www.debian.org/releases/buster/amd64/ch05s03.en.html
> 
> which has a section called 'Boot console'.
> 

`git clone https://salsa.debian.org/installer-team/installation-guide.git` 
plus `git grep ttyS0` did bring me not
the filename for "ch05s03.en.html" 

Where to find it?


Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: serial console install issues

[Geert Stappers]

On Sun, Apr 11, 2021 at 11:51:57AM +1200, Richard Hector wrote:
> Hi all,

Hi Mailinglist,

 
> I'm commenting here partly because I don't know which bit of software is at
> fault for each problem ...
> 
> I have a PCEngines APU4, which has a serial port and no video hardware.
> 
> I'm using a USB-serial adapter, with a null-modem cable.
> 
> I'm using a Buster netinst USB stick - 10.1 I think - according to the cdrom
> lines in sources.list
> 
> My first issue was that xfce4-terminal (by default) traps F10, which I
> needed for the Coreboot/Seabios boot menu, but I've since discovered that's
> an option in the preferences. I got around that initially by using xterm.
> 
> My first try was with minicom. It connected ok, but it appeared the arrow
> keys weren't working, and the line drawing characters weren't displaying
> correctly either.
> 
> When I discovered screen acts as a serial terminal, that behaved rather
> better (colour, and nice line drawing characters), but still problems with
> arrows.
> 
> Then finally, I can't remember how, I discovered that it didn't like
> displaying on a 24-line terminal, which most of the terminals I tried
> default to.
> 
> With a 25-line terminal, it all seems useable - and Minicom mostly displays
> it ok too (not quite right; the blue box isn't quite drawn properly, and
> seems too low on the screen?
> 
> It then took me some time to realise that I needed to both add
> console=ttyS0,115200n8 at the end of the kernel line, and apparently remove
> the 'vga=xxx' part earlier in the line. I guess it's not possible for
> SysLinux to detect that?
> 
> Anyway, as I say I'm not sure whether the issues are in the terminal
> emulation (either the xterm or comms program), or in the menu system (is
> that SysLinux?) or somewhere else, or whether the mismatch in number of
> lines inevitably causes problems.
> 
> I hope this isn't to vague :-)

It is a clear story of a struggle that has been won   :-)


On how to prevent that more people solve a solved problem
was a websearch done

  https://duckduckgo.com/q=debian+installer+serial+line

One of the first hits is

  https://www.debian.org/releases/buster/amd64/ch05s03.en.html

which has a section called 'Boot console'.  Rereading that section
again made we wonder what could be improved.

I'm asking Original Poster to elaborate what should be changed.



Regards
Geert Stappers
DD
-- 
Silence is hard to parse

Re: Possible kernel bug

[Geert Stappers]

SPOILER ALERT

This message contains information you might not want to known.
You all have been warned.


On Wed, Mar 17, 2021 at 08:42:40PM -0700, Brian Koblenz wrote:
...
> I have observed hangs only during boot after usb_modeswitch
...
> Is this even the right place to report these kinds of issues?

No.

Mailinglist debian-boot@lists.debian.org is about development
of the software collection that make installation possible.


No advice on where to go next.


Advice: Dig deeper, research what is going on.

Start reading the usb_modeswitch manpage again.
Aim for the original goal.


Spoiler:
Hardware was bought with the assumption "supported by Linux"




Regards
Geert Stappers
Mocking good people over bad hardware decissions
-- 
Silence is hard to parse


signature.asc
Description: PGP signature

Re: Color choices for the installer

[Geert Stappers]

On Sat, Feb 13, 2021 at 08:09:16PM +0100, John Paul Adrian Glaubitz wrote:
> On 2/13/21 8:02 PM, Cyril Brulebois wrote:
> > Ben Hutchings  (2021-02-13):
> >> I remember there being cases in the past where red and blue components
> >> were swapped on some hardware.  I think you've just found another one
> >> of those cases.
> > 
> > That rings a bell, I think I've had that many years ago with some
> > graphical applications on powerpc (iBook G4).
> > 
> > Oh, look, 15+ years ago!
> >   https://bugs.debian.org/327497
> 
> FWIW, I'm testing the installer regularly on my iBook G4 and I have not run
> into this issue. Installer behaves correctly and colors aren't swapped either.

Acknowlegde

And acknowlegde on the original post.



Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: Problem installing Debian on Dell XPS 13 9360 laptop

[Geert Stappers]

On Fri, Feb 05, 2021 at 10:32:44PM +, Bernard McNeill wrote:
> On Fri, Feb 05, 2021 at 08:05:22PM +, Bernard McNeill wrote:
> > This machine does not have either CD or DVD drive. Does have internal SSD.
> > This machine normally runs Windows-10.
> > Objective is to have Debian on external HDD (Toshiba), connected to laptop
> > via USB3.
> >
> > Events:
> > Under Windows, downloaded iso to SSD.
> > Win32diskimage from SSD to HDD.
> > Restarted, F12, picked out HDD from bootlist, booted, got into Debian
> > installer.
> > Does a few steps (language etc).
> > Gets stuck at 'No common CD-ROM drive was detected'.
> >
> > Ideas?
> >
>
> Is there any chance this is related to Bug #981666?
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981666
> "cdrom-detect: Preseeding cdrom-detect/load_media and a high-enough priority 
> lead to failure"

Nope, that issue is about preseeding.



Please pursuit your objective, you will be rewarded with usefull knowledge.


Use https://www.debian.org/releases/stable/amd64/apas04.en.html
as guidance for further steps.


Groeten
Geert Stappers
-- 
Silence is hard to parse

Bug#980528: debian-installer: net-install impossible because link is always reset

[Geert Stappers]

Not noticing humor, is no proof for the absence of humor.


On Thu, Jan 21, 2021 at 04:40:14PM +, etkaar wrote:
> Good evening,
> 
> after some testing it seems that I am just a very stupid person.

Mmm,  one of my motivators for working on libre software projects
is collaborating with smart people.
I'm willing to lower the bar to "people who can think for themselfs"
After all is the idea of "I could be stupid" just brilant.

 
> The reason, why the interface is always down is - after I had a look
> into the source code of netcfg - that is simply fails *and*, before
> it fails, netcfg would always reset the link, remove any routes and
> ip addresses. At least that is what I assume.
> 
> But why can I manually configure the network? Because I used the onlink flag:
> 
> # ip link set ens1 up
> # ip addr add 255.255.8.243/29 dev ens1
> # ip route add default via 255.255.8.1 dev ens1 >>>onlink<<<
> 
> "onlink: pretend that the nexthop is directly attached to this link,
> even if it does not match any interface prefix."
> https://linux.die.net/man/8/ip
> 
> The /29 subnet actually does not exist on the host; in reality,
> it is a /24 subnet. While /etc/network/interfaces in the installed
> Debian system itself would be aware of whatever it is aware of - I
> just don't know - and automatically will configure the route using the
> onlink tag, in the debian installer that is not possible. It seems the
> only correct way would have been to configure the network with the /24
> notation and the according 255.255.255.0 netmask, which makes sense,
> because working with a /29 notation using MacVTap and VEPA does not
> make much sense for me if the subnet is configured as /24 on the host.

"netmask" is a layer 3 thingy.  My gutfeeling says the problem is
at layer 2, where "link" happens.
 
> However, I am not well-educated when it comes to networking at all. I
> think my assumptions are right, but if the debian installer should
> be aware of that (like the final Debian installation is), we should
> leave that issue open.

Message for those who encounter simular problem:
  Please express your observations.


My observation:
  An address like _._.8.1 is never in same network as _._.8.243/29


Regards
Geert Stappers
-- 
Silence is hard to parse

Bug#980528: debian-installer: net-install impossible because link is always reset

[Geert Stappers]

On Wed, Jan 20, 2021 at 04:18:52PM +, etkaar wrote:
> Moin Geert,

 :-)

 
> thanks for helping!
> 
> > ???
> > (the triple question marks are for expressing my "Realy?",
> > please elaborate what is going on.
> > Yes, my request could be recieved as "vague",
> > do know that is being transmitted as "open")
> 
> Do you refer to the IPv4 addresses starting with two 255 groups?

Yes

> It was only an example, not the actual notation I used.

And the example introduced confusion.

 
> > And after configuring is actual traffic possible? 
> Yes. And once I go back to the installer, the link is down again and
> I am impossible to use the network.
> 
> > If so, provide some proof.
> Here is a proof, I made a video: https://youtu.be/9NOQAf6LOdo

I have seen the video.  I have the succesfull ping.

Also seen that installer menu is used.
Thing I would have done, is switch to another terminal

As far as I know does have QEMU support for sending ALT-F2
and ALT-F1.  But there is no ALT-F2 on serial line connections.


Anyway, there is some networking possible.
(my conclusion follows)


 
> > > #
> > > # libvirt VM configuration
> > > #
> > > 
> > >   
> > >   
> >
> >  I'm not sure if that is correct.
> 
> Why do you think that?

Mostly for keeping options on what to explore open.


> I use it with all my VMs.
 
Acknowledge on that.

Do know that we should avoid comparing apples and oranges.

Thing I slightly want to warn about, is that debian-installer
not the very same thing as a full blown system.



> > > #
> > > # Preseed (which also does not work)
> > > #
> > > d-i netcfg/choose_interface select ens1
> > > d-i netcfg/disable_autoconfig boolean true
> > > 
> > > d-i netcfg/get_ipaddress string 255.255.8.243
> > > d-i netcfg/get_netmask string 255.255.255.248
> > > d-i netcfg/get_gateway string 255.255.8.1
> > > d-i netcfg/get_nameservers string 8.8.8.8
> > > d-i netcfg/confirm_static boolean true
> > > 
> >
> > The "preseed stuff" is for later.
> 
> What do you mean by later?

For getting focus on the network problem.
d-i without any preseed stuff should be able to do DHCP


> I would think that the network configuration also (and at least)
> applies for the installer.
> 
> Please find also attached the virt-install command I use at the bottom
> (if I use a preseed or not, makes no difference).
> 
> Kind Regards,
> --etkaar
> 
> #
> # virt-install command
> #
> VM_NAME="vps2"
> 
> virt-install \
> --virt-type kvm \
> --name $VM_NAME \
> --ram 2048 \
> --vcpus 2 \
> --disk path=/var/lib/libvirt/images/$VM_NAME.qcow2,size=24 \
> --os-type linux \
> --os-variant debian10 \
> --graphics none \
> --console pty,target_type=serial \
> --location /var/lib/libvirt/images/.os/debian-10.7.0-amd64-netinst.iso \
> --network type=direct,source=eth0,source_mode=vepa,model=e1000 \
> --initrd-inject=/home/kvm/conf/preseed.cfg \
> --extra-args 'console=ttyS0,115200n8'

I can't spot any holes it  (due lack of indepth knowlegde)



My conclusion: Some how doesn't detect d-i link on the NIC


Advice:  Further debugging


My approach would be:

 * Temporary drop on the wish of a serial console
 * no preseed stuff yet
 * `virt-install` with having multiple VT [1]
 * install in VT-1, watch logs in other VT
 * have in another VT a shell for the `ip` commands


You probably want the syslog of d-i outside the VM
for more convinend analysis (pardon my english)



Regards
Geert Stappers
[1] https://en.wikipedia.org/wiki/Virtual_console
-- 
Silence is hard to parse

Bug#980528: debian-installer: net-install impossible because link is always reset

[Geert Stappers]

Control: tag -1 moreinfo

On Wed, Jan 20, 2021 at 08:08:24AM +, etkaar wrote:
> Package: debian-installer
> Severity: important
> Tags: d-i
> 
> Good Morning!

Moin

 
> I noticed a strange bug with the debian installer when I wanted to
> install a virtual machine (KVM) using virt-install. I use MacVTap in
> VEPA mode for networking. While the host would create an interface
> such like "macvtap[n]@eth0", the VM gets an interface such like "ens1"
> when using the e1000 NIC.
> 
> The fact, which lets me think that it is actually a bug of the installer,is,

I think it is an interresting problem, not convinced about a "bug".


> that a) the network works without any problem in all VMs which are installed
> and b) that I can configure the network manually, but *only* using the shell,
> for instance:
> 
> > ip link set ens1 up
> > ip addr add 255.255.8.243/29 dev ens1
> > ip route add default via 255.255.8.1 dev ens1 onlink

???
(the triple question marks are for expressing my "Realy?",
 please elaborate what is going on.
 Yes, my request could be recieved as "vague",
 do know that is being transmitted as "open")

 
> The bug is, that the installer - e.g. even if I, after DHCP has failed, try 
> to manually configure it
> using the installer (not the shell) - always resets the link "ens1" to a 
> state where the link is not up:
> 
> > ~ # ip link show
> > ...
> > 2: ens1:  mtu 1500 qdisc pfifo_fast qlen 1000
> > link/ether 52:54:00:fb:a1:98 brd ff:ff:ff:ff:ff:ff
> 
> Expected is "", but the interface is always 
> set to down by the installer.
> If I enable it by typing "ip link set ens1 up" it gets up and I can configure 
> the network in the shell.

And after configuring is actual traffic possible? 
If so, provide some proof.


> I even tried it with a preseed file, but whatever I try, the interface is 
> always down and so it is
> impossible to configure it within the installation.
> 
> 
> #
> # libvirt VM configuration
> #
> 
>   
>   

I'm not sure if that is correct.


>   
>function='0x0'/>
> 
> 
> #
> # Preseed (which also does not work)
> #
> d-i netcfg/choose_interface select ens1
> d-i netcfg/disable_autoconfig boolean true
> 
> d-i netcfg/get_ipaddress string 255.255.8.243
> d-i netcfg/get_netmask string 255.255.255.248
> d-i netcfg/get_gateway string 255.255.8.1
> d-i netcfg/get_nameservers string 8.8.8.8
> d-i netcfg/confirm_static boolean true
> 

The "preseed stuff" is for later.



Regards
Geert Stappers
-- 
Silence is hard to parse

Re: 10.8 planning

[Geert Stappers]

On Sun, Jan 17, 2021 at 09:59:09PM +, Andy Simpkins wrote:
> On 16 January 2021 21:54:25 GMT, Cyril Brulebois  wrote:
> >Adam D. Barratt  (2021-01-16):
> >> Please could you confirm your availability, and any preferences, for
> >> the following:
> >> 
> >> - January 30th (would mean we would have to freeze next weekend, so
> >>   a bit tight)
> >> - February 6th

FOSDEM 2021

> >> 
> >> My personal preference would be the 6th.
> >
> >Me too. But I can do both if needs be.
> >
> I can do either, it's not like I can go anywhere either weekend :-)

FOSDEM is online:-)


> Isy is available to help as well.
> 
> /Andy


Regards
Geert Stappers
-- 
Silence is hard to parse

Re: os-prober | os-probes: probe microsoft OS on arm64 (!7)

[Geert Stappers]

On Thu, Jan 14, 2021 at 06:06:21PM +, Holger Wansing wrote:
> Hi,
> 
> Am Donnerstag, 14. Januar 2021 schrieb Shawn Guo:
> > 
> > 
> > 
> > Shawn Guo commented:
> > 
> > 
> > @holgerw Any comments? We really need the change to get installer be able 
> > to probe Windows on arm64 laptops.
> 
> I see these machines are a growing target...
> 
> Me personally, I am lacking the skills to judge on these changings,
> unfortenately. 
> 
> Could someone review this MR, please?

https://salsa.debian.org/installer-team/os-prober/-/merge_requests/7

It only adds stuff, unlikely it will break existing stuff.


> Are there any objections against merging?

No objection from me. And I even encourage the merge because it makes
it possible to get Libre software on more systems.


Regards
Geert Stappers
-- 
Silence is hard to parse

Re: remove email from message body

[Geert Stappers]

On Thu, Jan 14, 2021 at 04:53:12PM +, Andrew M.A. Cater wrote:
> On Thu, Jan 14, 2021 at 03:45:23PM +0200, nikos wrote:
> > Hi,
> > 
> > 
> > When I reported an issue many years ago I also added my email by mistake. If
> > you could please remove it
> > 
> > from the message that would be good.
> > 
> > 
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718720
> > 
> 
> Hi Nikos,
> 
> Sorry - there's no straightforward way to remove emails from the Debian lists.
> The lists are archived, others copy them, Google probably has a cache.
> 
> The more you try to do this, the worse the problem becomes - it's the 
> Streisand effect - and your mail requesting this has added to it.

https://en.wikipedia.org/wiki/Streisand_effect
 

> With apologies - but in this instance, it's beyond the ability of the Debian 
> project to do this even if we wished to.

So true

 
> With every good wish, as ever,
> 
> Andy C




Regards
Geert Stappers
-- 
Silence is hard to parse

Re: Trouble with preseeding keyboard layout

[Geert Stappers]

On Sun, Jan 03, 2021 at 08:13:27PM +0100, Laurențiu Păncescu wrote:
> Hello,
> 
> I'm trying to install Debian with a en_US locale and a German keyboard
> layout:
> 
> d-i debian-installer/language string en
> d-i debian-installer/country string DE
> d-i debian-installer/locale string en_US.UTF-8
> # Keyboard selection.
> d-i keyboard-configuration/xkb-keymap select de
> 
> This works as expected when I use the "zcat boot.img.gz > /dev/sdb" method
> and copy the debian installer ISO and the preseed file to the DOS partition,
> loading it via "file=/hd-media/preseed.cfg".
> 
> If I generate my own installer ISO, with the same preseed.cfg, included in
> initrd.gz as described by [1], the keyboard layout remains the default US, I
> can see this when trying to type the LUKS passphrase in the installer. Is
> something missing from [1]? I attached the full preseed.cfg, in case someone
> wants to take a look.
> 
> Thanks,
> Laurențiu
> 
> [1] https://wiki.debian.org/DebianInstaller/Preseed/EditIso


URL not visited.

Information I want to share is that there are debconf settings
that are already needed before de preseed is being read.

Those debconf settings should be set as kernel boot paramater.


Cheers
Geert Stappers


P.S.

It is perfectly OK to post your working configuration. It is just
me who removed the preseed data from this reply. I love to see a
 Subject: Re: Trouble with preseeding keyboard layout (solved)
with kernel boot parameters and preseed file.

Re: Bug#977194: installation-reports: Installation stalls on network devices search when wifi key plugged in

[Geert Stappers]

On Sun, Dec 13, 2020 at 08:36:44AM +0100, john doe wrote:
> On 12/12/2020 11:37 PM, Mathieu Van Nieuwenhuyse wrote:
> > stappers wrote:
> > > 
> > > There are now two options:
> > > 
> > > A: Closing this bugreport
> > > B: Keep this bugreport open for "fix bug"
> > > 
> > > 
> > > Option A is a clear path.
> > > 
> > > What do you expect from option B?
> > > 
> > Closing the case is fine with me.
> > 
> > I would have expected the installation to skip the "unknown" device to
> > use the known one, that's why I wanted to report this, but it's more up
> > to you to choose if it's worth the time to check this .
> > 
> 
> I can confirm this as well

Confirming what?
* skip unknown device??
* wanted to report this??
* if it's worth the time to check this

> and don't understand why this bug has been closed.

> > Closing the case is fine with me.



> To 'Mathieu Van Nieuwenhuyse', does it help if you use the kernel boot
> parameter 'interface' (1) to specify the desired interface?
> 
> 
> 1)  https://www.debian.org/releases/jessie/amd64/ch05s03.html.en
> 

@Mathieu: this mailinglist posting was Bcc-ed to you



Regards
Geert Stappers
-- 
Silence is hard to parse

Bug#977194: installation-reports: Installation stalls on network devices search when wifi key plugged in

[Geert Stappers]

Control: tag -1 moreinfo

Hello Mathieu,


On Sat, Dec 12, 2020 at 12:02:31PM +0100, Mathieu Van Nieuwenhuyse wrote:
> Package: installation-reports

Thanks for the report


> Severity: normal
> Tags: d-i
> X-Debbugs-Cc: mathieu.van.nieuwenhu...@gmail.com
> 
> Dear Maintainer,
> 
> 
>* What led up to the situation?
> I launched the installation (via usb key) with both a wifi stick plugged in
> (TP-link Archer T2U) and an ethernet connexion
> the search for network devices stalled : no error message, nothing to do.
> 
> I restarted the installation without the wifi stick.
> 
> Everything worked fine then.

Acknowledge.


There are now two options:

A: Closing this bugreport
B: Keep this bugreport open for "fix bug"


Option A is a clear path.

What do you expect from option B?



Regards
Geert Stappers
-- 
Silence is hard to parse

Re: Minimun hardware requirements innaccurate as documented

[Geert Stappers]

On Wed, Dec 02, 2020 at 10:23:05AM +0100, Samuel Thibault wrote:
> Hello,
> 
> Jim, le mar. 01 déc. 2020 17:29:52 -0800, a ecrit:
> > https://www.debian.org/releases/stable/i386/ch03s04.en.html 
> > 
> > it states 512M RAM is the minimum required for gui desktop.  However in
> > installing the 10.6 32bit livecd on a 32bit system with 784M RAM,
> 
> This link does not document the livecd image, but the installer only.
> 
> I added a note about this.
> 
> > I even tried this straight from the installer boot menu without
> > loading the desktop into RAM first, with the same results.
> 
> Even that will not be the same installer image, only the pure installer
> is documented there.
> 
> I just tried with qemu with 512M, it does install fine. With the
> installer image and not the livecd, that is.
> 

Does it mean that #976255: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976255  
can be closed?



Regards
Geert Stappers
Who created #976255 to prevent that the feedback might have got lost
-- 
Silence is hard to parse

Bug#976255: Minimun hardware requirements innaccurate as documented

[Geert Stappers]

Package: debian-installer

- Forwarded message from Jim  -

Date: Tue, 01 Dec 2020 17:29:52 -0800
From: Jim 
To: debian-boot@lists.debian.org
Subject: Minimun hardware requirements innaccurate as documented

According to this link:  
https://www.debian.org/releases/stable/i386/ch03s04.en.html 
it states 512M RAM is the minimum required for gui desktop.  However
in installing the 10.6 32bit livecd on a 32bit system with 784M RAM,
the installer refuses to install stating the minimum required RAM is
1G. I even tried this straight from the installer boot menu without
loading the desktop into RAM first, with the same results.
Please update your documentation.
Thanks-:)
Jim

- End forwarded message -

Regards
Geert Stappers
-- 
Silence is hard to parse

Bug#974122: email formatting thingy Was: Bug#974122: No network at Banana Pi M2 Ultra

[Geert Stappers]

On Tue, Nov 10, 2020 at 04:23:25PM +0100, William Bonnet wrote:
> I would like to know please if you did it "by hand" or used a tool to do
> the check ?

https://salsa.debian.org/installer-team/installation-report/-/blob/master/install-report.template

Re: Question about Installer

[Geert Stappers]

On Fri, Oct 23, 2020 at 07:18:47PM +0330, negin jafari wrote:
> Dear sir or madam,

Hello Mailinglist,


> I am a university Student trying to learn a lot of things about Debian.
> I searched all ur website about changes in installer framework in each
> release but I couldn’t find any useful data.
> As I know calamares is new in Debian-10 and before that Debian-installer
> was used . But I don’t know details of changes in each release .

https://wiki.debian.org/DebianInstaller/CheckOut
and "Check Out" refers to  "version control system check out"


> I really need to know this and I’d  be really thankful for your answer.

I really have different needs and I leave it to original poster
to meet us, d-i team, on common ground.


> Best regards
> Negin jafari


Regards
Geert Stappers
-- 
Silence is hard to parse

Bug#971984: installation-reports: installation report

[Geert Stappers]

Control: tag -1 moreinfo


On Sun, Oct 11, 2020 at 01:42:17AM -0400, WK Burke wrote:
> Package: installation-reports
> 
> Boot method: usb
> Image version: debian 10.0 iso
> 
> Machine: Dell Inspiron 15-3567
> 
> 
> Base System Installation Checklist:
> [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
> 
> Initial boot:   [ ]
> Detect network card:[ ]
> Configure network:  [ ]
> Detect CD:  [ ]
> Load installer modules: [ ]
> Clock/timezone setup:   [ ]
> User/password setup:[ ]
> Detect hard drives: [ ]
> Partition hard drives:  [ ]
> Install base system:[ ]
> Install tasks:  [ ]
> Install boot loader:[ ]
> Overall install:[ ]
> 
> Comments/Problems:
> 
>and ideas you had during the initial install.>
> 
> 
> 
> 
> 
> ==
> Installer lsb-release:
> ==
> DISTRIB_ID=Debian
> DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
> DISTRIB_RELEASE="10 (buster) - installer build 20190702"
> X_INSTALLATION_MEDIUM=cdrom
> 
> uname -a: Linux zues 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5 (2019-06-19) 
> x86_64 GNU/Linux



Please tell more about the installation success.

And that includes a message like "the install went just fine"   :-)




Regards
Geert Stappers
-- 
Silence is hard to parse

Bug#971606: installation-reports cubieboard 5

[Geert Stappers]

On Sun, Oct 04, 2020 at 01:03:00AM +0300, Валериан Пережигин wrote:
> 03.10.2020, 22:53, Geert Stappers
> > Please rerun the installer, find a shell, do `lsblk`
> > and pretty please report back.
> 
> BusyBox v1.30.1 (Debian 1:1.30.1-4) built-in shell (ash)
> Enter 'help' for a list of built-in commands.
> 
> ~ # lsblk
> /bin/sh: lsblk: not found
> ~ # ls
> ls lsmod lspci lsscsi
> ~ # blk
> blkdiscard blkid

Ah, yes that command


> ~ # blkid
> /dev/sda1: LABEL="cb5-boot" UUID="a3d6a5a1-9796-4605-a317-8bdc94af219e" 
> TYPE="ext2" PARTUUID="fdb06b7f-01"
> /dev/sda2: UUID="87c9e46c-1293-474e-801d-3a0f5ee3569d" TYPE="swap" 
> PARTUUID="fdb06b7f-02"
> /dev/sda3: LABEL="cb5" UUID="adb31049-edbb-4d50-b4a2-0aca6a82159b" 
> TYPE="ext4" PARTUUID="fdb06b7f-03"
> /dev/sda4: LABEL="cb5-home" UUID="29c228f9-6541-4ff7-bf5c-44ebb8eebe6d" 
> TYPE="ext4" PARTUUID="fdb06b7f-04"
> /dev/sdb1: LABEL_FATBOOT="BLACK16G" LABEL="BLACK16G" UUID="6088-862B" 
> TYPE="vfat" PARTUUID="b7bb8d8a-01"
> /dev/sdb2: LABEL="DebTry" UUID="e95a4f9e-e1fb-4679-9d1d-63a516e76a8a" 
> TYPE="ext4" PARTUUID="b7bb8d8a-02"
> /dev/sdb3: UUID="3ee578b5-a253-459e-810d-34885848b8b5" TYPE="swap" 
> PARTUUID="b7bb8d8a-03"
> /dev/sdb4: LABEL="DebTry-home" UUID="221e7afe-a030-40e5-8bdf-79bea0e0fcaa" 
> TYPE="ext4" PARTUUID="b7bb8d8a-04"
> /dev/loop0: UUID="2020-09-26-15-00-29-00" LABEL="Debian 10.6.0 armhf 1" 
> TYPE="iso9660" PTTYPE="dos"
> ~ #

/dev/sda, /dev/sdb  and /dev/loop0.

No /dev/mmcblk

 

> That's all. Usb storage device new, because old one already reused.

I'm not sure about that. I don't know what is attached to the
cubieboard. But /dev/sdb1, labelled BLACK16G, is something I would
inspect closer.

> The installer worked ok. I have no routine to install debian using uart.
> Normal questions, answer. Ui was uncomfortable, but worked fine.
> Excluding the fact that no sdcard (or mmc) showed up.
> 
> Then, when i tried to boot: system booted from mmc (to debian installer or
> android if ejected).
> 
> Expected behavior, since no processing to cards was made.
> 
> > > System worked
> >
> > "System worked" as: The installer came alive and showed behaviour as
> > seen at other installs ???
>
> "System worked" mean that cb5 (with debian just installed) showed login prompt
>_(after additional steps (3 described)).
> 

Mmm, chips.  So a working Debian system,
but getting that far was NOT that easy as expected.


Regards
Geert Stappers

P.S.
Please keep the BTS, the Bug Tracking System, in the loop.
-- 
Silence is hard to parse

Bug#971606: installation-reports cubieboard 5

[Geert Stappers]

Control: tag -1 moreinfo

On Sat, Oct 03, 2020 at 12:17:51AM +0300, Валериан Пережигин wrote:
> Package: installation-reports
> 
> Boot method: hd-media/sd-card-images + usb (fat32) with
> 
> debian-cd debian-10.6.0-armhf-xfce-CD-1.iso.
> 
> I was using uart (pl2303).
> Image version: 
> https://mirror.yandex.ru/debian-cd/10.6.0/armhf/bt-cd/debian-10.6.0-armhf-xfce-CD-1.iso.torrent
> Date: 2020-10-01 20:12 MSK
> 
> Machine: cubietech cubietrick plus (cubieboard 5)
> Processor: soc A83t (2GHz ?)
> Memory: 2GiB (DDR3 at 672MHz)
> 
> Comments/Problems:
> 
> No sdcard demonstrated, only usb and sata.
> No dp or hdmi.
> Installation to sata (manually prepared dos partitioning, just select 
> filesystems) sucsessed.
> Installation of u-boot climed sucsess yet failed (system was not bootable).
> 
> By main pc:
> 1. copyed boot partition (from sata) to sdcard.
> 2. installed by dd u-boot (from u-boot-sunxi_2020.10~rc5+dfsg-1_armhf.deb) to 
> sdcard.

Acknowledge


> 3. insertied sdcard to cb5.
> 
> System worked.

"System worked" as:   The installer came alive and showed behaviour as
seen at other installs ???


> But no video, no network, no sdcard.
> Uart work fine.
> Usb came up after long delay (with some errors).
> 
> Kernel update yet again claim no errors, but bootloader is stil to be 
> installed.
> 
> I regret sdcard not showed up.

Please rerun the installer, find a shell,  do  `lsblk`
and pretty please report back.



Regards
Geert Stappers
-- 
Silence is hard to parse

Bug#970678: Forwarding debian-boot posting

[Geert Stappers]

- Partly forwarded message from Bjørn Mork -

Date: Tue, 22 Sep 2020 12:17:38 +0200
From: Bjørn Mork
To: debian-boot@lists.debian.org
Subject: Re: Bug#970678: Network preseeding using http is broken

Ben Hutchings  writes:
>
> It's a udev regression, bug #967546.

Looks like that's deliberate, so probably Not A Bug.  Quoting from
https://github.com/systemd/systemd/commit/6b2229c6c60d0486 :

 "if people want to use udev from other init systems
  they should do this on their own,"

You might want to just fork udev while it still sort of works outside
systemd.


Bjørn

- End partly forwarded message -

I hope this helps both bugreports.


Regards
Geert Stappers
-- 
Silence is hard to parse

Bug#970678: Network preseeding using http is broken

[Geert Stappers]

On Mon, Sep 21, 2020 at 03:30:27PM +0200, Philip Hands wrote:
> Martin Samuelsson  writes:
> 
> > Booting the installer with DEBCONF_DEBUG=5 and debuging /bin/preseed_fetch, 
> > /bin/fetch-url and /usr/lib/fetch_url/http shows that wget404() in the 
> > latter is what's failing. It seems the pipeline fails since /dev/fd/4 does 
> > not exist.
> 
> Just to be clear on this point, are you saying that /dev/fd/4 does not
> exist when you look for it in a shell, or rather specifically when doing
> so in a context where it is in use?
> 
> If you noticed that it's not there when e.g. simply listing the contents
> of /dev/fd then that's normal AFAIK.
> 
> To illustrate this, here's some output from busybox shell, running on my
> laptop:
> 
> =-=-=-=-
> ~ $ echo /dev/fd/*
> /dev/fd/0 /dev/fd/1 /dev/fd/10 /dev/fd/2 /dev/fd/3
> ~ $ ( echo /dev/fd/* ) 4>&1
> /dev/fd/0 /dev/fd/1 /dev/fd/10 /dev/fd/2 /dev/fd/3 /dev/fd/4
> ~ $ ( echo /dev/fd/* ) 4>&1 5>&1
> /dev/fd/0 /dev/fd/1 /dev/fd/10 /dev/fd/2 /dev/fd/3 /dev/fd/4 /dev/fd/5
> ~ $  ( echo /dev/fd/* ) 6>&1
> /dev/fd/0 /dev/fd/1 /dev/fd/10 /dev/fd/2 /dev/fd/3 /dev/fd/6
> ~ $
> =-=-=-=-
> 


On Mon, Sep 21, 2020 at 02:58:36PM +0200, Philip Hands wrote:
 ...
> 
> The fact that /dev/fd/4 is missing does seem to be a separate bug, but a
> quick grep -lr suggests that this is the only place it's used in d-i, so
> perhaps a bug we need not worry about too much.
> 


Under which circumstance does the bug shows itself?



Regards
Geert Stappers
-- 
Silence is hard to parse

Bug#914813: Some additional informations

[Geert Stappers]

On Fri, Sep 18, 2020 at 10:42:05PM +0200, Bernhard wrote:
> Is it possible, that the RSB kernel module is missing (drivers/bus/)?
> Or, is it possible, that the AXP kernel module is missing?

The file /boot/config-$( uname -r )  can tell.


Regards
Geert Stappers
-- 
stappers@paddy:~
$ cd /boot/
stappers@paddy:/boot
$ ls
config-5.7.0-2-amd64  initrd.img-5.7.0-2-amd64  System.map-5.7.0-2-amd64
vmlinuz-5.8.0-1-amd64
config-5.8.0-1-amd64  initrd.img-5.8.0-1-amd64  System.map-5.8.0-1-amd64
grub  lost+foundvmlinuz-5.7.0-2-amd64
stappers@paddy:/boot
$ uname -r
5.8.0-1-amd64
stappers@paddy:/boot
$ ls -l /boot/config-$( uname -r )
-rw-r--r-- 1 root root 233667  5 sep 16:52 /boot/config-5.8.0-1-amd64
stappers@paddy:/boot
$ 

Re: Getting beyond hijacking, Salsa privilege

[Geert Stappers]

On Sun, Sep 06, 2020 at 02:45:49PM +0200, Camaleón wrote:
> El 2020-09-05 a las 20:30 +0200, Geert Stappers escribió:
> > On Sat, Sep 05, 2020 at 07:13:04PM +0200, Camaleón wrote:
> > > El 2020-09-05 a las 17:02 +0200, Holger Wansing escribió:
> > > > > ...
> > > > I just want to help with this conflict, please accept this help.
> > > 
  ...
> 
> > > P.S. As I already told Javier, this is the last time I translate these 
> > > files because I don't like to see my job being blatantly hijacked.
> > 
> > 
> > Acknowledge on "feeling hijacked".
> > 
> > Which ingredients has the email exchange to get beyond hijacking?
> 
> Maybe the term «hijacked» can sound strong wordings but that's how I felt.

I did recieve the "strong" words as  clear words.


> To describe it better, it happens when you have defined a way 
> to do translations in Debian Spanish, you follow the established way 
> and rules, and suddenly someone appears, gets your job, your files and 
> even without asking (this time I did not request for any help), does 
> whatever he wants, upload the files to GIT server, says there are 
> «errors» but it does not allow me, as the last translator, to make the 
> required changes, nor instructs me about where the problem lays so I
> can correct it by my own.

I do read that as Camaleón not yet having Salsa privileges
to update debian-boot translations.

@Camaleón would you be helped wiht git write access to debian-installer?

 
> In brief, acting in a dictatorial way, as he were the files' owner
> and dismissing your entire job. Well, that hurts, despite the status of 
> the person where it comes from.
> 
> > And a less retoric question:
> > What is possible for working together on the same goal?
> 
> We are all working on the same goal. There's a lot of translation work 
> to do in Debian and I'm fine translating other files; no problem on 
> my side. This episode was just the usual frictions that happens on teams 
> conformed by human people with human egos.

+1
Thanks for expressing that.

 
> So let's keep working to get the job done.

And the other jobs / tasks / duties  we have  :-)


Groeten
Geert Stappers
-- 
Silence is hard to parse

Getting beyond hijacking Was: Bug#969377: Bug reopen

[Geert Stappers]

On Sat, Sep 05, 2020 at 07:13:04PM +0200, Camaleón wrote:
> El 2020-09-05 a las 17:02 +0200, Holger Wansing escribió:
> > > ...
> > I just want to help with this conflict, please accept this help.
> 
> I do know, and I appreciate it. So you can keep the files as they are 
> now at the GIT repository and discard the ones I uploaded in BTS (bugs 
> id #969377, #969378, #969379, #969380 and #969381). 
> 
> Bugs can be closed.

Closing 969381  the one I updated with "Viva espanol"

 
> P.S. As I already told Javier, this is the last time I translate these 
> files because I don't like to see my job being blatantly hijacked.


Acknowledge on "feeling hijacked".

Which ingredients has the email exchange to get beyond hijacking?


And a less retoric question:
What is possible for working together on the same goal?



Regards
Geert Stappers

P.S.
The Cc for debian-boot@l.d.o.  is for the "lessons learnt"
-- 
Silence is hard to parse

Bug#969402: installation-reports: does not start with -q option specified

[Geert Stappers]

Control: tag 969402 +moreinfo

On Tue, Sep 01, 2020 at 11:56:41PM -0300, LILIAN wrote:
}  ... only the empty template ...

Pleaes tell more,
such as where your added the  -qand what you expect from it.


Groeten
Geert Stappers
-- 
Silence is hard to parse

Bug#969381: Viva espanol

[Geert Stappers]

On Tue, Sep 01, 2020 at 08:03:46PM +0200, Camaleón wrote:
> Hello,
> 
> I have to disagree.

I see content for a conflict.
Please proof me wrong and show the world that there is common ground.


Regards
Geert Stappers
DD
-- 
Silence is hard to parse

Bug#842626: Having history is good

[Geert Stappers]

On Sun, Aug 23, 2020 at 10:17:15AM +0200, Samuel Thibault wrote:
> Geert Stappers, le dim. 23 août 2020 09:57:23 +0200, a ecrit:
> > The win-win-win situation is
> > * There is a BR that i386 image checks for amd64 host and informs user 
> > about it
> > * Holgers good work is respected
> > * BTS has only open BR that deserve attention, which keeps developers
> >   motivated to check BTS for what needs to be done
> 
> I completely support Holgers' good work, that's not the question!

   :-)
 

> But point 3 contradicts what you wrote above: not having the information
> that the bug was already reported 4 years ago gives a wrong signal to
> developers: possibly we don't actually want to spend time implementing
> it, and just re-filing a bug report "just because yes it is still not
> implemented" gives a wrong priority signal.


I admit I was pushing too much to a fresh start.

Whom ever wants to work on the issue this bugreport is about, probably
doesn't need an open bugreport about it.  The persoon will need an  i386
machine to verify that the i386 image still works fine.  And also need
an  amd64 machine to verify that the i386 image can detect it is on
amd64 hardware.


Groeten
Geert Stappers
-- 
Silence is hard to parse


signature.asc
Description: PGP signature

Bug#924179: Info received (Bug#924179: marked as done (Package: installation-reports))

[Geert Stappers]

On Fri, Aug 21, 2020 at 05:36:47AM +0200, Andreas Plassmann wrote:
> On 21.08.20 05:33, Debian Bug Tracking System wrote:
> > Thank you for the additional information you have supplied regarding
> > this Bug report.
> > 
> > This is an automatically generated reply to let you know your message
> > has been received.
> > 
> > Your message is being forwarded to the package maintainers and other
> > interested parties for their attention; they will reply in due course.
> > 
> > Your message has been sent to the package maintainer(s):
> >   Debian Install Team 
> > 
> > If you wish to submit further information on this problem, please
> > send it to 924...@bugs.debian.org.
> > 
> 
> But not over 300 emails in 10 minutes, that's too much, sorry, that doesn't
> work. Then I say stop have been tracking it for a long time but haven't
> followed 300 emails in such a short time
> 

Please elaborate


Regards
Geert Stappers
-- 
Silence is hard to parse

Bug#968202: preseed: Checks only BOOTP filename and not DHCP option 67, "bootfile-name"

[Geert Stappers]

On Mon, Aug 10, 2020 at 05:00:31PM +0100, Bob Ham wrote:
> 
> The dhcp_preseed_url function in preseed.sh, part of preseed:
> 
> https://salsa.debian.org/installer-team/preseed/-/blob/399d9e8d56d64161449e9415cc8fe33ae88711f2/preseed.sh#L173
> 
> only checks for the "filename" entry in DHCP lease files.
> The "filename" entry is a holdover from the BOOTP protocol.

Yes, DHCP is EEE of BOOTP


> Some DHCP
> servers don't allow setting the filename at all.  OpenWRT's odhcpd,
> doesn't allow setting the filename in DHCP responses for classified
> clients, such as clients with a vendor class containing "d-i", it only
> allows setting DHCP options.

Server side stuff is not client side stuff ...


> It would be good if dhcp_preseed_url could take advantage of the
> DHCP "bootfile-name" option and not just the BOOTP filename.
 
It will require reseach on how the various DHCP clients in  d-i
write down "filename" in their lease file.


Regards
Geert Stappers
Who provides the preseed URL as kernel command line option during netboot
-- 
EEE = https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguish

Re: Mass-closing old installation-report bugs

[Geert Stappers]

On Tue, Aug 04, 2020 at 12:09:01AM +0200, Holger Wansing wrote:
> 
> I'm closing the reports below.
> 
> That's installation-reports for Debian 7 with
> - undefined errors
> - problems which are likely to have been fixed in the meantime
> - successful installation
> 
> Because of the age, there is no chance to analyse them further and therefore
> they are no longer relevant or of any use for current releases.
> 

Thank you for doing this.
Yes, I do apricate this is being done.


> Holger


Groeten
Geert Stappers
-- 
Silence is hard to parse


signature.asc
Description: PGP signature

Re: Pine64 RockPro64 Support, image generation help offer

[Geert Stappers]

On Fri, Jul 24, 2020 at 08:56:39PM +0200, Alexandre GRIVEAUX wrote:
> Hello,
> 
> 
> After some try (including checking the right image, the sdcard and the
> reader), i've managed to boot the Pine64 RockPro64 by doing:
> 
> - Getting firmware and partition of daily images for RockPro64 and
> assembling it to complete_image.img
> 
> - Copy it with dd on sdcard and plug it on board and powering the board.
> 
> - Using installer normally but instead of using the whole disk I
> formated the fat32 partition to ext4 and resized to the end of sdcard
> 
> (to avoiding erasing bootloader at beginning sdcard)
> 
> 
> - Used chroot on another machine to install flash-kernel and adding:
> 'Pine64 RockPro64' to /etc/flash-kernel/machine and:
> 
>   
> https://salsa.debian.org/installer-team/flash-kernel/-/merge_requests/21/diffs
> 
> To /etc/flash-kernel/db
> 
> 
> - Using programs on this order:
> 
> update-initramfs -u
> 
> flash-kernel
> 
> 
> After a reboot the board is now working !
> 
> 
> Now i would like to write u-boot on SPI flash instead of using sdcard to
> boot and facilitate me if i need to reinstalling Debian on it.
> 
> 
> How i can help to bring those features on mainling sdcard images ?
} How i can help to bring those features on mainline sdcard images ?

I think that question should be read as

  Which projectteam builds mainline SDcard images
  and how to contact them for offering help?


I don't know
and I don't know where to ask if it remains silent here.

So lets see what information comes along.


> 
> Thanks
> 

Thank YOU


Groeten
Geert Stappers
-- 
Silence is hard to parse

Bug#965263: debian-installer: Script exected in preseed/late_command on dual CPU socket system sees only Single CPU socket

[Geert Stappers]

On Sat, Jul 18, 2020 at 06:19:55PM +0530, Vasudev Kamath wrote:
> 
> Please let me know if you need more information.
> 

Both kernel versions

Re: preseed apt Dpkg Options force confnew

[Geert Stappers]

On Tue, Jun 30, 2020 at 05:32:35PM +, Neil Roza wrote:
> Is there a way to override the in-target `apt` configuration to effect
> something like
> 
> Dpkg::Options::="--force-confnew"
> 
> for the packages installed via `pkgsel/include`?
 
> I'm trying to force `dpkg` to install the maintainer's version of a
> config file.

That is default behaviour in a fresh install.

In other words: The "problem" does not exist.



Groeten
Geert Stappers

P.S.
In case there is a problem, describe it.
-- 
Silence is hard to parse

Bug#962802: nonfree firmware install media exists

[Geert Stappers]

Package: www.debian.org


Hello Website team,

We, Debian, as friendly as we are, have several welcoming entrances.
One entry point, install media that does support hardware
that insists on binary only artifacs, is poorly documented.

Please make it possible that unofficial/non-free/images-including-firmware
can be "clicked" through links.

I did know that page 
https://cdimage.debian.org/images/unofficial/non-free/images-including-firmware/daily-builds
exists, but had to find an extrenal websearch to get there again.


Regards
Geert Stappers
DD


On Sun, Jun 14, 2020 at 02:17:12PM +0200, Geert Stappers wrote:
> On Sun, Jun 14, 2020 at 01:03:09PM +0200, Dylan Lom wrote:
> > Package: installation-reports
> > 
> > Boot method: USB
> > Image version: 
> > http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-xfce-CD-1.iso
>  
> > Base System Installation Checklist:
> > 
> > Initial boot:   [O]
> > Detect network card:[E]
> > Configure network:  [O]
> > Overall install:[O]
> > 
>  
> > Comments/Problems:
> > 
> > The laptop uses the relatively new Realtek 8822CE card, which the
> > firmware-realtek package doesn't include yet. Running `dmesg | grep
> > network` contained an error about the rtw_pci module not being able
> > to find the driver (I didn't record the precise error).
> > 
> > I was able to get the WiFi working in the installer by downloading the
> > latest linux-firmware tarball[1] from git.kernel.org, and replacing
> > the files in /lib/firmware/rtw88 in a shell.
> > 
>  
> Woh, SKILLED[2]
> 
> Thanks for the install report  and especial from reporting how to add
> what is missing.
> 
> On the "firmware-realtek package doesn't include yet" are the expections
> not quiet right.  https://packages.debian.org/buster/firmware-realtek
> says that the package is in "non-free". Which means it wouldn't get
> included on official Debian install media.
> 
> Workaround is
> https://cdimage.debian.org/images/unofficial/non-free/images-including-firmware/
> 
> Please do an install with firmware-testing-amd64-netinst.iso from
> https://cdimage.debian.org/images/unofficial/non-free/images-including-firmware/daily-builds/sid_d-i/20200614-3/amd64/iso-cd/
> and report back.
> 
>  
> Regards
> Geert Stappers
> 
> [1] 
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-20200519.tar.gz
> [2] Yes, that is a compliment
> 

Groeten
Geert Stappers
-- 
Silence is hard to parse

Bug#962802: Installation Report Lenovo Yoga S730

[Geert Stappers]

Control: tag 962802 +moreinfo

On Sun, Jun 14, 2020 at 01:03:09PM +0200, Dylan Lom wrote:
> Package: installation-reports
> 
> Boot method: USB
> Image version: 
> http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-xfce-CD-1.iso
> Date: 2020-06-14

Hey, that is today

 
> Machine: Lenovo Yoga S730
 
> Base System Installation Checklist:
> 
> Initial boot:   [O]
> Detect network card:[E]
> Configure network:  [O]
> Overall install:[O]

;-)

> 
> Comments/Problems:
> 
> The laptop uses the relatively new Realtek 8822CE card, which the
> firmware-realtek package doesn't include yet. Running `dmesg | grep
> network` contained an error about the rtw_pci module not being able
> to find the driver (I didn't record the precise error).
> 
> I was able to get the WiFi working in the installer by downloading the
> latest linux-firmware tarball[1] from git.kernel.org, and replacing
> the files in /lib/firmware/rtw88 in a shell.
> 
 
Woh, SKILLED[2]

Thanks for the install report  and especial from reporting how to add
what is missing.

On the "firmware-realtek package doesn't include yet" are the expections
not quiet right.  https://packages.debian.org/buster/firmware-realtek
says that the package is in "non-free". Which means it wouldn't get
included on official Debian install media.

Workaround is
https://cdimage.debian.org/images/unofficial/non-free/images-including-firmware/

Please do an install with firmware-testing-amd64-netinst.iso from
https://cdimage.debian.org/images/unofficial/non-free/images-including-firmware/daily-builds/sid_d-i/20200614-3/amd64/iso-cd/
and report back.

 
Regards
Geert Stappers

[1] 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-20200519.tar.gz
[2] Yes, that is a compliment
-- 
Silence is hard to parse

Re: Bug#960390: x86_64: No serial port output

[Geert Stappers]

On Tue, May 12, 2020 at 04:20:58PM +0200, Bjørn Mork wrote:
> 
> The lack of serial console support is a very long standing bug in the
> Debian installer.  See for example https://bugs.debian.org/309223
> opened 15 years ago, and closed 10 years ago without any attempt to fix
> the problem.

   :-(


> The bug has been carefully forward ported from syslinux to grub, keeping
> the intended(?) non-working default.
> 
> I believe most users have given up.  After all, you rarely need to
> install Debian more than once one a system. And you easily live with
> having to modify the installer slightly.

Virtual Machines (Qemu, KVM, Xen, ... ) and OCI containters ( "Docker
images") are the new serial port only computers.

In other words: There are many servers without video hardware.


Regards
Geert Stappers

Yes, I should provide patches ...
-- 
Silence is hard to parse

Noise and more noise Was: Creating custom installer where only the Video Driver is changed

[Geert Stappers]

On Sun, May 10, 2020 at 08:12:05AM +0530, Arvind IK Chari wrote:
> Hello again, One update to my problem-

Please, pretty please,
be aware that you are NOT sending emails to your mom.

 
Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: Creating custom installer where only the Video Driver is changed

[Geert Stappers]

On Sun, May 10, 2020 at 07:38:08AM +0530, Arvind IK Chari wrote:
> Hi,
>  
> I wish to create a custom Debian installer where only the Video driver
> used is not the default one- it should be the Via Unichrome Driver
> (my Video card is a Via Chrome9 IGP- for this card the Linux Unichrome
> driver is available.)
>  
> I understand that I can build my own custom Linux Debian Distro-
> but how do I get the list of packages which are part of the default
> XFCE Distro- and then make a single change to install the Via Driver
> instead of the default Video driver?
>  
> Any help would be appreciated.

Start.  Yes, just start.
Take the existing sources of debian-installer and build d-i.
It is documented at https://wiki.debian.org/DebianInstaller

Now you have something that is build before.
Next step is making changing and rebuild.


> Thanks and sincerely,
> Arvind.
 

 
Groeten
Geert Stappers
-- 
Silence is hard to parse

image 2020-05-08 no isolinux.bin Was: An important problem

[Geert Stappers]

On Sat, May 09, 2020 at 12:53:51AM +0800, 朱煜昊 wrote:
> 
> 
> Hello,I have downloaded the iso file of debian from official 
> website：https://cdimage.debian.org/debian-cd/current/amd64/iso-dvd/
> It seems that the iso file which created in 2020.5.8 does not have file 
> "isolinux.bin".

Yes, I think that is an important problem.
So I give it better "Subject: line"


Regards
Geert Stappers
-- 
Silence is hard to parse

Re: EFI Grub installation

[Geert Stappers]

On Wed, Apr 22, 2020 at 11:32:51PM +0200, Ali Isin wrote:
> Hallo,
> 
> I noticed that when installing Debian Buster 10.3 - even afther trying
> several times - the installation of EFI-Grub fails..
> 
> I would send you the installation log - but unfortunately - I don't know
> the location..

The directory  /var/log/installer


> 
> I hopen to see this bug fixed,
> and friendly greetings..
> 
> Ali ISIN
> Student


Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: black screen after installation under virtualbox

[Geert Stappers]

On Thu, Apr 16, 2020 at 08:50:42PM +0200, Bernhard Brandt wrote:
> Dear ladies and gentlemen,
> 
> I want just to report the following bug. If this is not the right adress
> please elongate this to the right specialist.
> 
> After installation of Debian via DVD debian-10.3.0-amd64-DVD-1.iso under
> virtual box 6.0.20 (windows 10 rev 1909) with the vbox extension pack I
> received a black screen starting it.
> 
> The change of same parameters (i.e. simulated grafic card, more grafic ram,
> boost options, virtual hdisk type) did not change anything.
> 
> There was access to load debian software as kde files during the debian
> installation.
> 
> After installation of linuxmint on the very same virtualbox there was no
> problem.
> 
> So it had to do with the installation media of debian.

Yes, that is one possibility. Another possibility is how linuxmint
copes with the virtualbox hardware. (I'm thinking fiercy versus lazy
hardware checks, but can't tell). And there is a thrid option I think
about: Could nested virtualisation the cullprit?
 

> So may this helps. I am still interesting to explore debian.

Reporting breakage is indeed helpfull.

Yes, do explore Debian.  What about another install in VBox?
This time an installation that doesn't install KDE during install.
(Install KDE later on)

For feedback there is 
https://www.debian.org/releases/stable/amd64/ch05s04.en.html#problem-report
and https://www.debian.org/releases/stable/amd64/apas04.en.html for
succes stories.


Regards
Geert Stappers
-- 
Silence is hard to parse

Re: NIC not detected, unable to install (weekly + daily mini-iso)

[Geert Stappers]

On Wed, Apr 15, 2020 at 07:45:42PM +0200, Camaleón wrote:
> Hello,
> 
> Tried the mini-iso image to install testing (i386), with both, daily and 

i386?


> weekly files. To my surprise, the installer was unable to detect the wired
> NIC adapter and wifi required a non-free firmware that I was unable to 
> load (I tried by following the instructions and copying the files on a 
> secondary USB stick, but no way).
> 
> Kernel log showed something like «R8169 Unknown Chip XID 5A4».
> 
> This is running on pretty common netbook hardware:
> 
> 00:00.0 Host bridge: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx DMI 
> Bridge
> 00:02.0 VGA compatible controller: Intel Corporation Atom Processor 
> D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller
> 00:02.1 Display controller: Intel Corporation Atom Processor 
> D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller
> 00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition 
> Audio Controller (rev 02)
> 00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1 
> (rev 02)
> 00:1c.1 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 2 
> (rev 02)
> 00:1d.0 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI 
> Controller #1 (rev 02)
> 00:1d.1 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI 
> Controller #2 (rev 02)
> 00:1d.2 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI 
> Controller #3 (rev 02)
> 00:1d.3 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI 
> Controller #4 (rev 02)
> 00:1d.7 USB controller: Intel Corporation NM10/ICH7 Family USB2 EHCI 
> Controller (rev 02)
> 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
> 00:1f.0 ISA bridge: Intel Corporation NM10 Family LPC Controller (rev 02)
> 00:1f.2 SATA controller: Intel Corporation NM10/ICH7 Family SATA Controller 
> [AHCI mode] (rev 02)
> 00:1f.3 SMBus: Intel Corporation NM10/ICH7 Family SMBus Controller (rev 02)
> 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL810xE PCI 
> Express Fast Ethernet controller (rev 04)
> 01:00.1 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5288 PCI 
> Express Card Reader (rev 01)
> 02:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4313 802.11bgn 
> Wireless Network Adapter (rev 01)
> 
> Is it a known kernel issue, meaning should I wait?
> 
> Greetings,
> 
> Camaleón 


Regards
Geert Stappers
-- 
Silence is hard to parse

Re: Issue -Debian 10 upload speed over LAN and Wlan

[Geert Stappers]

On Sat, Mar 21, 2020 at 03:39:26AM +, Pedro Gumucio wrote:
> Hello, I have been researching the past week an issue that I have with the 
> upload speed using the last version of Debian 10/Raspbian GNU/Linux 10.
> My internet provider gives me 100/100 Mb/s. but my speed test upload speed is 
> only 3.8Mb/s
> 
> Retrieving speedtest.net configuration...
> Testing from Verizon Fios (100.36.172.81)...
> Retrieving speedtest.net server list...
> Selecting best server based on ping...
> Hosted by PBW Communications, LLC (Herndon, VA) [21.83 km]: 115.366 ms
> Testing download 
> speed
> Download: 84.38 Mbit/s
> Testing upload 
> speed..
> Upload: 3.85 Mbit/s
> 
> I tried fresh installations and ran it in raspberry pi 3+ and 4 having the 
> same results.

So you learned that transfer speed is totally independent from installation.


> Please help :/

You are asking at the wrong place.

 

Regards
Geert Stappers

P.S.
I could have totally ignore the original message.
-- 
Silence is hard to parse

Re: usper.debian.org docs

[Geert Stappers]

Welcome,

On Sun, Feb 23, 2020 at 03:00:08PM -0500, Neil Roza wrote:
> What is usper.debian.org? What's it doing? Where is it documented?

See https://db.debian.org/machines.cgi?host=usper


That link was found through this path:
* Knowning that there is db.debian.org,  db being/meaning DataBase
* https://db.debian.org/
* Upper left corner "Development machines"
* https://db.debian.org/machines.cgi
* `find` on "usper"


I do hope it answers the question of Original Poster.


Regards
Geert Stappers
DD
-- 
Silence is hard to parse

Bug#951367: debootstrap: Raspbian bootstrap: Failed getting release file --verbose

[Geert Stappers]

On Sun, Feb 16, 2020 at 11:52:27PM +0900, Hideki Yamane wrote:
> On Sun, 16 Feb 2020 15:31:56 +0100 Michael Büsch  wrote:
> > $ sudo debootstrap --arch=armhf --foreign --verbose 
> > --keyring=raspbian-archive-keyring-20120528.2/raspbian.public.key.gpg 
> > buster /tmp/debootstrap-test/ 
> > http://mirror1.hs-esslingen.de/pub/Mirrors/archive.raspbian.org/raspbian/
> 
>  Please try without --verbose, I guess its option is something wrong with.
> 

Confirmed



stappers@trancilo:~/Downloads
$ sudo debootstrap --arch=armhf --foreign --verbose 
--keyring=raspbian-archive-keyring-20120528.2/raspbian.public.key.gpg buster 
/tmp/debootstrap-test/ http://ftp.gwdg.de/pub/linux/debian/raspbian/raspbian/
I: Retrieving InRelease 
I: Retrieving Release 
E: Failed getting release file 
http://ftp.gwdg.de/pub/linux/debian/raspbian/raspbian/dists/buster/Release
stappers@trancilo:~/Downloads
$ sudo debootstrap --arch=armhf --foreign   
--keyring=raspbian-archive-keyring-20120528.2/raspbian.public.key.gpg buster 
/tmp/debootstrap-test/ http://ftp.gwdg.de/pub/linux/debian/raspbian/raspbian/
I: Retrieving InRelease 
I: Checking Release signature
I: Valid Release signature (key id A0DA38D0D76E8B5D638872819165938D90FDDD2E)
I: Retrieving Packages 
I: Validating Packages 
I: Resolving dependencies of required packages...
I: Resolving dependencies of base packages...
^CE: Interrupt caught ... exiting
stappers@trancilo:~/Downloads
$ 

Bug#951367: debootstrap: Raspbian bootstrap: Failed getting release file, reproduce URL

[Geert Stappers]

Two mirror URL  where reproducable the bugreport is possible


http://mirror1.hs-esslingen.de/pub/Mirrors/archive.raspbian.org/raspbian/  
http://ftp.gwdg.de/pub/linux/debian/raspbian/raspbian/



stappers@trancilo:~/Downloads
$ sudo debootstrap --arch=armhf --foreign --verbose 
--keyring=raspbian-archive-keyring-20120528.2/raspbian.public.key.gpg buster 
/tmp/debootstrap-test/ 
http://mirror1.hs-esslingen.de/pub/Mirrors/archive.raspbian.org/raspbian/  
I: Retrieving InRelease 
I: Retrieving Release 
E: Failed getting release file 
http://mirror1.hs-esslingen.de/pub/Mirrors/archive.raspbian.org/raspbian/dists/buster/Release
stappers@trancilo:~/Downloads
$ sudo debootstrap --arch=armhf --foreign --verbose 
--keyring=raspbian-archive-keyring-20120528.2/raspbian.public.key.gpg buster 
/tmp/debootstrap-test/ http://ftp.gwdg.de/pub/linux/debian/raspbian/raspbian/
I: Retrieving InRelease 
I: Retrieving Release 
E: Failed getting release file 
http://ftp.gwdg.de/pub/linux/debian/raspbian/raspbian/dists/buster/Release
stappers@trancilo:~/Downloads
$ 

Bug#951367: debootstrap: Raspbian bootstrap: Failed getting release file

[Geert Stappers]

On Sun, Feb 16, 2020 at 03:31:56PM +0100, Michael Büsch wrote:
> On Sun, 16 Feb 2020 14:47:37 +0100 Geert Stappers wrote:
> 
  
> 
> > And I do hope that bugreporter is aware that BR got human attention.
> 
> Erm, yes?
> 

Silence  and  "it works for me"   can be recieved as very cold.

So I made some effort to prevent that cold.

Bug#951367: debootstrap: Raspbian bootstrap: Failed getting release file

[Geert Stappers]

Hi,


On Sun, Feb 16, 2020 at 12:14:28PM +0100, Michael Büsch wrote:
> A different command has been used to "reproduce" this problem.

Please elaborate that.


> So I currently don't consider the unreproducible flag for this bug as valid.

With the keyring file inplace, I had a succesfull "build".
To me is the bugreport UNreproducible.

I have no idea how to dive deeper into this.
And I do hope that bugreporter is aware that BR got human attention.


Regards
Geert Stappers


stappers@trancilo:~/Downloads
$ wget 
http://mirrordirector.raspbian.org/raspbian//pool/main/r/raspbian-archive-keyring/raspbian-archive-keyring_20120528.2.tar.gz
--2020-02-16 14:22:31-- 
http://mirrordirector.raspbian.org/raspbian//pool/main/r/raspbian-archive-keyring/raspbian-archive-keyring_20120528.2.tar.gz
Resolving mirrordirector.raspbian.org (mirrordirector.raspbian.org)...
2a00:1098:0:80:1000:75:0:3, 93.93.128.193
Connecting to mirrordirector.raspbian.org
(mirrordirector.raspbian.org)|2a00:1098:0:80:1000:75:0:3|:80...
connected.
HTTP request sent, awaiting response... 302 Found
Location: 
http://mirror.serverius.net/raspbian/raspbian/pool/main/r/raspbian-archive-keyring/raspbian-archive-keyring_20120528.2.tar.gz
[following]
--2020-02-16 14:22:35-- 
http://mirror.serverius.net/raspbian/raspbian/pool/main/r/raspbian-archive-keyring/raspbian-archive-keyring_20120528.2.tar.gz
Resolving mirror.serverius.net (mirror.serverius.net)...
2a03:3f40:1::15, 5.255.95.70
Connecting to mirror.serverius.net
(mirror.serverius.net)|2a03:3f40:1::15|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 4949 (4.8K) [application/octet-stream]
Saving to: 'raspbian-archive-keyring_20120528.2.tar.gz'

raspbian-archive-keyring_201205
100%[>]   4.83K
--.-KB/sin 0.001s  

2020-02-16 14:22:39 (4.74 MB/s) -
'raspbian-archive-keyring_20120528.2.tar.gz' saved [4949/4949]

stappers@trancilo:~/Downloads
$ sha256sum raspbian-archive-keyring_20120528.2.tar.gz 
fdf50f775b60901a2783f21a6362e2bf5ee6203983e884940b163faa1293c002 
raspbian-archive-keyring_20120528.2.tar.gz
stappers@trancilo:~/Downloads
$ tar tf !$
tar tf raspbian-archive-keyring_20120528.2.tar.gz
raspbian-archive-keyring-20120528.2/
raspbian-archive-keyring-20120528.2/keyrings/
raspbian-archive-keyring-20120528.2/keyrings/raspbian-archive-keyring.gpg
raspbian-archive-keyring-20120528.2/debian/
raspbian-archive-keyring-20120528.2/debian/control
raspbian-archive-keyring-20120528.2/debian/debian-ports-archive-keyring.docs
raspbian-archive-keyring-20120528.2/debian/raspbian-archive-keyring.postinst
raspbian-archive-keyring-20120528.2/debian/copyright
raspbian-archive-keyring-20120528.2/debian/rules
raspbian-archive-keyring-20120528.2/debian/raspbian-archive-keyring.install
raspbian-archive-keyring-20120528.2/debian/compat
raspbian-archive-keyring-20120528.2/debian/raspbian-archive-keyring-udeb.install
raspbian-archive-keyring-20120528.2/debian/changelog
raspbian-archive-keyring-20120528.2/README
raspbian-archive-keyring-20120528.2/raspbian.public.key
stappers@trancilo:~/Downloads
$ tar xf raspbian-archive-keyring_20120528.2.tar.gz
stappers@trancilo:~/Downloads
$ echo gpg --dearmor raspbian-archive-keyring-20120528.2/raspbian.public.key 
gpg --dearmor raspbian-archive-keyring-20120528.2/raspbian.public.key
stappers@trancilo:~/Downloads
$ file !$
file raspbian-archive-keyring-20120528.2/raspbian.public.key
raspbian-archive-keyring-20120528.2/raspbian.public.key: PGP public key block 
Public-Key (old)
stappers@trancilo:~/Downloads
$ gpg --dearmor raspbian-archive-keyring-20120528.2/raspbian.public.key 
stappers@trancilo:~/Downloads
$ file !$
file raspbian-archive-keyring-20120528.2/raspbian.public.key
raspbian-archive-keyring-20120528.2/raspbian.public.key: PGP public key block 
Public-Key (old)
stappers@trancilo:~/Downloads
$ less !$
less raspbian-archive-keyring-20120528.2/raspbian.public.key
stappers@trancilo:~/Downloads
$ sudo debootstrap --arch=armhf --foreign --verbose 
--keyring=raspbian-archive-keyring-20120528.2/raspbian.public.key.gpg buster 
/tmp/debootstrap-test/ http://mirrordirector.raspbian.org/raspbian/
[sudo] password for stappers: 
I: Retrieving InRelease 
I: Checking Release signature
I: Valid Release signature (key id A0DA38D0D76E8B5D638872819165938D90FDDD2E)
I: Retrieving Packages 
I: Validating Packages 
I: Resolving dependencies of required packages...
I: Resolving dependencies of base packages...
I: Checking component main on http://mirrordirector.raspbian.org/raspbian...
I: Retrieving adduser 3.118
I: Validating adduser 3.118
I: Retrieving apt 1.8.2
I: Validating apt 1.8.2
I: Retrieving apt-utils 1.8.2
I: Validating apt-utils 1.8.2
I: Retrieving base-files 10.3+rpi1+deb10u3
I: Validating base-files 10.3+rpi1+deb10u3
I: Retrieving base-passwd 3.5.46
I: Validating base-passwd 3.5.46
I: Retrieving bash 5.0-4
I: Validating bash 5.0-4
I: Retrieving bsdmainutils 11.1.2
I: Val

Bug#951367: debootstrap: Raspbian bootstrap: Failed getting release file

[Geert Stappers]

On Sat, Feb 15, 2020 at 12:34:20PM +0100, Michael Büsch wrote:
> 
> Since debootstrap 1.0.117 Raspbian bootstrap fails with the following error 
> message:
> 
> $ debootstrap --arch=armhf --foreign --verbose 
> --keyring=keyrings/raspbian-archive-keyring.gpg buster /tmp/debootstrap-test 
> http://mirrordirector.raspbian.org/raspbian/
> I: Retrieving InRelease
> I: Retrieving Release
> E: Failed getting release file 
> http://mirrordirector.raspbian.org/raspbian/dists/buster/Release
> 

While reproducing here
| $ debootstrap --arch=armhf --foreign --verbose 
--keyring=keyrings/raspbian-archive-keyring.gpg buster /tmp/debootstrap-test 
http://mirrordirector.raspbian.org/raspbian/
| bash: debootstrap: opdracht niet gevonden
| $ sudo debootstrap --arch=armhf --foreign --verbose 
--keyring=keyrings/raspbian-archive-keyring.gpg buster /tmp/debootstrap-test 
http://mirrordirector.raspbian.org/raspbian/
| E: specified keyring file (keyrings/raspbian-archive-keyring.gpg) not found
| $ 

Please elaborate where to get raspbian-archive-keyring.


Other thing:  Can you `wget` the Release file?



Regards
Geert Stappers
Fully aware that this bugreport is currently tagged unreproducable
-- 
$ wget http://mirrordirector.raspbian.org/raspbian/dists/buster/Release
--2020-02-16 10:09:43-- 
http://mirrordirector.raspbian.org/raspbian/dists/buster/Release
Resolving mirrordirector.raspbian.org (mirrordirector.raspbian.org)...  
2a00:1098:0:80:1000:75:0:3, 93.93.128.193
Connecting to mirrordirector.raspbian.org 
(mirrordirector.raspbian.org)|2a00:1098:0:80:1000:75:0:3|:80...  connected.
HTTP request sent, awaiting response... 200 OK
Length: 14437 (14K)
Saving to: 'Release'
.
Release   100%[>]  14.10K  
--.-KB/sin 0.005s  
.
2020-02-16 10:09:43 (3.04 MB/s) - 'Release' saved [14437/14437]

Bug#951387: Please accept https://salsa.debian.org/installer-team/console-setup/merge_requests/3

[Geert Stappers]

On Sun, Feb 16, 2020 at 09:48:49AM +0200, Mantas Baltix wrote:
> I've added my patch to git and created merge request, see:
> https://salsa.debian.org/installer-team/console-setup/merge_requests/3

FWIW the changes 
https://salsa.debian.org/mantas-guest/console-setup/commit/209750047be3e943ca02be8dd186fb6525a76751
 

> Please accept :)

  ;-)

 

Groeten
Geert Stappers
-- 
Leven en laten leven

Re: Re: 8 more packages

[Geert Stappers]

On Mon, Jan 13, 2020 at 07:56:02AM +0100, mario.stro...@gmail.com wrote:
> Have you tested on different hardware? In example yours?
> 

In case the context was/is 
https://lists.debian.org/debian-boot/2020/01/msg00068.html
that message has

| Over here no hardware with _both_  WIFI and ethernet available
| for re-installs. And sacrificing an installed laptop doesn't make
| sense because what we are researching might be hardware related.


Regards
Geert Stappers
-- 
Leven en laten leven