Re: Merge request created [Re: Use isenkram to get around the firmware problem?]

2021-03-09 Thread Cyril Brulebois
Brian Potkin (2021-03-09): > On Mon 08 Mar 2021 at 22:41:53 +0100, Holger Wansing wrote: > > At the bare minimum, I have created a merge request for my > > "introduce a dialog to enter packages for firmware installation" > > approach, so it is at least officially documented somewhere... I have no

Re: Merge request created [Re: Use isenkram to get around the firmware problem?]

2021-03-09 Thread Brian Potkin
On Mon 08 Mar 2021 at 22:41:53 +0100, Holger Wansing wrote: > Hi, > > Holger Wansing wrote (Sun, 7 Mar 2021 17:02:06 +0100): > > And for the (graphics) firmware problem, isenkram is of no help as it > > seems, > > at least for Bullseye. > > I have reached the end of my path on this issue. >

Re: Merge request created [Re: Use isenkram to get around the firmware problem?]

2021-03-08 Thread Cyril Brulebois
Hallo Holger, Holger Wansing (2021-03-08): > Holger Wansing wrote (Sun, 7 Mar 2021 17:02:06 +0100): > > And for the (graphics) firmware problem, isenkram is of no help as it > > seems, > > at least for Bullseye. > > I have reached the end of my path on this issue. > > isenkram is apparently

Re: Merge request created [Re: Use isenkram to get around the firmware problem?]

2021-03-08 Thread Holger Wansing
Hi, Holger Wansing wrote (Mon, 8 Mar 2021 22:41:53 +0100): > At the bare minimum, I have created a merge request for my "introduce a dialog > to enter packages for firmware installation" approach, so it is at least > officially documented somewhere... Should have added a link. That's https://

Merge request created [Re: Use isenkram to get around the firmware problem?]

2021-03-08 Thread Holger Wansing
Hi, Holger Wansing wrote (Sun, 7 Mar 2021 17:02:06 +0100): > And for the (graphics) firmware problem, isenkram is of no help as it seems, > at least for Bullseye. I have reached the end of my path on this issue. isenkram is apparently no solution for Bullseye. At the bare minimum, I have crea