Hi Cyril,
> That's not what it does. It is there to determine whether it's a bad
> idea to reload a module. That's quite a different story… And no, between
> two mainloop iterations, that part wouldn't change anyway.
indeed.
I thought the device would be configured after upnics at the beginning
On Mon, Feb 6, 2023, at 7:34 AM, Cyril Brulebois wrote:
>
> That's not to say I won't try and get a tentative patch before then…
> Would you be happy to test a custom netinst that I would build locally
> (i.e. outside cdimage.debian.org and the official infrastructure)?
I'd be happy to test an
Brandon Werner (2023-02-06):
> This makes sense, and both solutions seem like they would work. It
> seems like the second solution of keeping the unconditional reload and
> testing if the list of files was smaller after the reload would be
> easier to implement for Bookworm, but I think you and
On Mon, Feb 6, 2023, at 5:33 AM, Cyril Brulebois wrote:
> Hi Brandon,
>
> Brandon Werner (2023-02-06):
>> Thanks for your response. I have included the syslog lines from the
>> installer log you requested.
>
> OK, that's basically what I thought was happening, but it's always a
> good idea to
Hi Brandon,
Brandon Werner (2023-02-06):
> Thanks for your response. I have included the syslog lines from the
> installer log you requested.
OK, that's basically what I thought was happening, but it's always a
good idea to check a hypothesis before deciding what to do about it. :)
I think I
On Mon, Feb 6, 2023, at 4:36 AM, Cyril Brulebois wrote:
> Hi Brandon,
>
> Brandon Werner (2023-02-05):
>> I saw the recent work to the installer surrounding firmware handling
>> and thought I would test on my machines to see how this all was
>> working. I used one of the daily sid_d-i netinst
Alexander Dalm (2023-02-06):
> But there is actually a function nic_is_configured() that is used to
> determine if the module has to be removed and reloaded after files are
> installed.
That's not what it does. It is there to determine whether it's a bad
idea to reload a module. That's quite a
Hi Brandon,
Brandon Werner (2023-02-05):
> I saw the recent work to the installer surrounding firmware handling
> and thought I would test on my machines to see how this all was
> working. I used one of the daily sid_d-i netinst cds including
> firmware. I noticed some problems around the
Hi Brandon,
good point.
currently hw-detect / check-missing-firmware doesn't checks if a specific
firmware file is optional or required, I even considered asking for the
optional ones as well as a feature.
But there is actually a function nic_is_configured() that is used to
determine if the
package: hw-detect
version: 1.154
Hello,
I saw the recent work to the installer surrounding firmware handling and
thought I would test on my machines to see how this all was working. I used one
of the daily sid_d-i netinst cds including firmware. I noticed some problems
around the installer
10 matches
Mail list logo
