Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #233290 > unrolled thread

WiFi Hardware not detected, during Debian NetInst Install

Back to article view | Back to linux.debian.user

Contents

  WiFi Hardware not detected, during Debian NetInst Install Kenneth Parker <sea7kenp@gmail.com> - 2021-03-21 23:30 +0100
    Re: WiFi Hardware not detected, during Debian NetInst Install Brian <ad44@cityscape.co.uk> - 2021-03-22 00:10 +0100
      Re: WiFi Hardware not detected, during Debian NetInst Install Kenneth Parker <sea7kenp@gmail.com> - 2021-03-22 01:20 +0100
        Re: WiFi Hardware not detected, during Debian NetInst Install Andrei POPESCU <andreimpopescu@gmail.com> - 2021-03-22 12:10 +0100
          Re: WiFi Hardware not detected, during Debian NetInst Install Kenneth Parker <sea7kenp@gmail.com> - 2021-03-22 20:00 +0100
            Re: WiFi Hardware not detected, during Debian NetInst Install Charles Curley <charlescurley@charlescurley.com> - 2021-03-22 21:00 +0100
              Re: WiFi Hardware not detected, during Debian NetInst Install Kenneth Parker <sea7kenp@gmail.com> - 2021-03-22 21:50 +0100
                Re: WiFi Hardware not detected, during Debian NetInst Install Brian <ad44@cityscape.co.uk> - 2021-03-22 22:00 +0100
                  Re: WiFi Hardware not detected, during Debian NetInst Install Charles Curley <charlescurley@charlescurley.com> - 2021-03-22 23:40 +0100
                    Re: WiFi Hardware not detected, during Debian NetInst Install Brian <ad44@cityscape.co.uk> - 2021-03-23 00:00 +0100
                      Re: WiFi Hardware not detected, during Debian NetInst Install Charles Curley <charlescurley@charlescurley.com> - 2021-03-23 02:00 +0100
                Re: WiFi Hardware not detected, during Debian NetInst Install Charles Curley <charlescurley@charlescurley.com> - 2021-03-23 00:00 +0100
                  Re: WiFi Hardware not detected, during Debian NetInst Install Kenneth Parker <sea7kenp@gmail.com> - 2021-03-23 00:10 +0100
              Re: WiFi Hardware not detected, during Debian NetInst Install Kenneth Parker <sea7kenp@gmail.com> - 2021-03-22 23:20 +0100
                Re: WiFi Hardware not detected, during Debian NetInst Install Brian <ad44@cityscape.co.uk> - 2021-03-23 00:00 +0100
                  Re: WiFi Hardware not detected, during Debian NetInst Install Kenneth Parker <sea7kenp@gmail.com> - 2021-03-23 01:30 +0100
                    Re: WiFi Hardware not detected, during Debian NetInst Install Greg Wooledge <greg@wooledge.org> - 2021-03-23 02:20 +0100
                      Re: WiFi Hardware not detected, during Debian NetInst Install Kenneth Parker <sea7kenp@gmail.com> - 2021-03-23 02:30 +0100
                    Re: WiFi Hardware not detected, during Debian NetInst Install Brian <ad44@cityscape.co.uk> - 2021-03-23 11:10 +0100
                      Re: WiFi Hardware not detected, during Debian NetInst Install Kenneth Parker <sea7kenp@gmail.com> - 2021-03-23 12:00 +0100
                        Re: WiFi Hardware not detected, during Debian NetInst Install Cmdte Alpha Tigre Z <santiagopinth@gmail.com> - 2021-03-24 23:00 +0100
                          Re: WiFi Hardware not detected, during Debian NetInst Install David Wright <deblis@lionunicorn.co.uk> - 2021-03-25 05:00 +0100
                            Re: WiFi Hardware not detected, during Debian NetInst Install Charles Curley <charlescurley@charlescurley.com> - 2021-03-25 05:30 +0100
                              Re: WiFi Hardware not detected, during Debian NetInst Install David Wright <deblis@lionunicorn.co.uk> - 2021-03-25 17:10 +0100
                                Re: WiFi Hardware not detected, during Debian NetInst Install Cmdte Alpha Tigre Z <santiagopinth@gmail.com> - 2021-03-25 20:20 +0100
                                Re: WiFi Hardware not detected, during Debian NetInst Install Kenneth Parker <sea7kenp@gmail.com> - 2021-03-25 22:40 +0100
                                  Re: WiFi Hardware not detected, during Debian NetInst Install Cmdte Alpha Tigre Z <santiagopinth@gmail.com> - 2021-03-26 00:10 +0100
                                    Re: WiFi Hardware not detected, during Debian NetInst Install Kenneth Parker <sea7kenp@gmail.com> - 2021-03-26 01:30 +0100
                            Re: WiFi Hardware not detected, during Debian NetInst Install Charles Curley <charlescurley@charlescurley.com> - 2021-03-25 20:10 +0100
                              Re: WiFi Hardware not detected, during Debian NetInst Install Cmdte Alpha Tigre Z <santiagopinth@gmail.com> - 2021-03-25 20:30 +0100
            Re: WiFi Hardware not detected, during Debian NetInst Install Brian <ad44@cityscape.co.uk> - 2021-03-22 21:50 +0100
              Re: WiFi Hardware not detected, during Debian NetInst Install Kenneth Parker <sea7kenp@gmail.com> - 2021-03-22 22:00 +0100
    Re: WiFi Hardware not detected, during Debian NetInst Install David Christensen <dpchrist@holgerdanske.com> - 2021-03-22 01:50 +0100
    Re: WiFi Hardware not detected, during Debian NetInst Install Robbi Nespu <robbinespu@gmail.com> - 2021-03-22 02:30 +0100
      Re: WiFi Hardware not detected, during Debian NetInst Install Kenneth Parker <sea7kenp@gmail.com> - 2021-03-22 02:50 +0100
        Re: WiFi Hardware not detected, during Debian NetInst Install David Wright <deblis@lionunicorn.co.uk> - 2021-03-22 15:50 +0100
          Re: WiFi Hardware not detected, during Debian NetInst Install Brian <ad44@cityscape.co.uk> - 2021-03-22 17:10 +0100
    Re: WiFi Hardware not detected, during Debian NetInst Install David Wright <deblis@lionunicorn.co.uk> - 2021-03-22 02:50 +0100

Page 2 of 2 — ← Prev page 1 [2]

#233448

Hi.

I saw the bug report.  Mr. Charles Curley provided relevant information
about the installation process stored on log files.  Perhaps it would be good
to follow Mr. David Wright's advice, you could help with bug-fixing process
sending some installation log information to narrow what the developers
should be looking for.  As for the reproduction of the bug, I think one
would need a similar hardware configuration to reach the problem;
at least you need the WiFi device, so it would be good if you could provide
more details, if you have the time, of course.

Have a good day.

[toc] | [prev] | [next] | [standalone]

#233458

On Wed 24 Mar 2021 at 17:58:58 (-0400), Cmdte Alpha Tigre Z wrote:
> 
> I saw the bug report.  Mr. Charles Curley provided relevant information
> about the installation process stored on log files.  Perhaps it would be good
> to follow Mr. David Wright's advice, you could help with bug-fixing process
> sending some installation log information to narrow what the developers
> should be looking for.  As for the reproduction of the bug, I think one
> would need a similar hardware configuration to reach the problem;
> at least you need the WiFi device, so it would be good if you could provide
> more details, if you have the time, of course.

I've just looked at bug report #985755 and there are, currently, a
mere four occurrences of the string 8723, only one of which is
actually in the text. Most of the logs appear to be about the
Intel PRO/Wireless 2200BG device, its module ipw2200 and firmware
ipw2200-bss.fw. My newly oldest computer, an Acer TravelMate 3201XCi,
built in 2004, contains one of these. If it's of any use to Charles,
I can warn that this laptop has the annoying habit of booting up
with the wifi blocked. (It has a pair of insanely placed toggling
buttons/lights for wifi and bluetooth, and I've never figured out
what the wifi light correlates with.) I know nothing about the R51
and whether there are any firmware buttons or function keys that
would affect its wifi.

As far as "my advice" is concerned (which really arose from an
apparent difference in how the d-i firmware is loaded in wheezy
and buster), we haven't yet been shown any direct evidence of
which module drives the 8723, nor of what firmware it uses.
(These can easily be determined from dmesg when the installed
system is running.) This should allow a more focussed report
from the installation logs (of which we've seen nothing IIRC).

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#233460

On Wed, 24 Mar 2021 22:52:31 -0500
David Wright <deblis@lionunicorn.co.uk> wrote:

> ... [W]e haven't yet been shown any direct evidence of
> which module drives the 8723, nor of what firmware it uses.
> (These can easily be determined from dmesg when the installed
> system is running.)

Also, more detail from /var/log/syslog while d-i is running, and
from /var/log/installer/ after installation is complete.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

[toc] | [prev] | [next] | [standalone]

#233491

On Wed 24 Mar 2021 at 22:25:42 (-0600), Charles Curley wrote:
> On Wed, 24 Mar 2021 22:52:31 -0500 David Wright wrote:
> 
> > ... [W]e haven't yet been shown any direct evidence of
> > which module drives the 8723, nor of what firmware it uses.
> > (These can easily be determined from dmesg when the installed
> > system is running.)
> 
> Also, more detail from /var/log/syslog while d-i is running, and
> from /var/log/installer/ after installation is complete.

Yes, that was my very next sentence, which you snipped: "This should
allow a more focussed report from the installation logs (of which
we've seen nothing IIRC)."

But it appears that I might need to point out that it's very easy and
quick to re-collect a failing installation log at any time if the
"original" ones were lost/overwritten or whatever:

 1. Boot with the appropriate installation medium.

 2. Proceed with expert installation in the original manner,
    as far as the "Detect Network Hardware", which of course fails.

 3. After the failure, and back at the Main Menu, select
    "Save debug logs".

 4. Insert a USB stick, switch to VC2, mount the stick and create
    a directory on it.

 5. Back at VC1, complete the directory name at the prompt and
    save the logs. (ls on VC2 if you want to check them.)

 6. Select "Abort the installation". All that should have taken
    about five or ten minutes so far.

 7. Read/edit/post excerpts from the logs at leisure. (That's when
    it helps to know what strings you're looking for.)

That's what's lacking from the bug report.

The OP wrote "The Problem is Recreated. It's hard to figure out how
to describe something so early in the Install Process."

That's how you do it.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#233509

I agree with Mr. Charles Curley and Mr. David Wright.
Following those advices will help more the "debugging" process.

[toc] | [prev] | [next] | [standalone]

#233514

[Multipart message — attachments visible in raw view] — view raw

On Thu, Mar 25, 2021, 12:09 PM David Wright <deblis@lionunicorn.co.uk>
wrote:

> On Wed 24 Mar 2021 at 22:25:42 (-0600), Charles Curley wrote:
> > On Wed, 24 Mar 2021 22:52:31 -0500 David Wright wrote:
> >
> > > ... [W]e haven't yet been shown any direct evidence of
> > > which module drives the 8723, nor of what firmware it uses.
> > > (These can easily be determined from dmesg when the installed
> > > system is running.)
> >
> > Also, more detail from /var/log/syslog while d-i is running, and
> > from /var/log/installer/ after installation is complete.
>
> Yes, that was my very next sentence, which you snipped: "This should
> allow a more focussed report from the installation logs (of which
> we've seen nothing IIRC)."
>
> But it appears that I might need to point out that it's very easy and
> quick to re-collect a failing installation log at any time if the
> "original" ones were lost/overwritten or whatever:
>
>  1. Boot with the appropriate installation medium.
>
>  2. Proceed with expert installation in the original manner,
>     as far as the "Detect Network Hardware", which of course fails.
>
>  3. After the failure, and back at the Main Menu, select
>     "Save debug logs".
>
>  4. Insert a USB stick, switch to VC2, mount the stick and create
>     a directory on it.
>
>  5. Back at VC1, complete the directory name at the prompt and
>     save the logs. (ls on VC2 if you want to check them.)
>
>  6. Select "Abort the installation". All that should have taken
>     about five or ten minutes so far.
>
>  7. Read/edit/post excerpts from the logs at leisure. (That's when
>     it helps to know what strings you're looking for.)
>

Since the actual logs from the Install are small, I proceeded, up to # 6.
And then, tarred the resulting directory, and sent it to the Bug Report.

That's what's lacking from the bug report.
>

Hopefully, this will help.

>
> The OP wrote "The Problem is Recreated. It's hard to figure out how
> to describe something so early in the Install Process."
>
> That's how you do it.
>

I overlooked the presence of the Debug Logs.

>
> Cheers,
> David.
>

Kenneth Parker

>

[toc] | [prev] | [next] | [standalone]

#233518

El jue, 25 mar 2021 a las 17:31, Kenneth Parker (<sea7kenp@gmail.com>) escribió:
> On Thu, Mar 25, 2021, 12:09 PM David Wright <deblis@lionunicorn.co.uk> wrote:
>> But it appears that I might need to point out that it's very easy and
>> quick to re-collect a failing installation log at any time if the
>> "original" ones were lost/overwritten or whatever:
>>
>>  1. Boot with the appropriate installation medium.
>>
>>  2. Proceed with expert installation in the original manner,
>>     as far as the "Detect Network Hardware", which of course fails.
>>
>>  3. After the failure, and back at the Main Menu, select
>>     "Save debug logs".
>>
>>  4. Insert a USB stick, switch to VC2, mount the stick and create
>>     a directory on it.
>>
>>  5. Back at VC1, complete the directory name at the prompt and
>>     save the logs. (ls on VC2 if you want to check them.)
>>
>>  6. Select "Abort the installation". All that should have taken
>>     about five or ten minutes so far.
>>
>>  7. Read/edit/post excerpts from the logs at leisure. (That's when
>>     it helps to know what strings you're looking for.)
>
>
> Since the actual logs from the Install are small, I proceeded, up to # 6.  And then, tarred the resulting directory, and sent it to the Bug Report.
>
>> That's what's lacking from the bug report.
>
>
> Hopefully, this will help.

Thank you, Mr. Kenneth Parker.

I noticed in the "syslog" that modprobe couldn't find the module "rtw_8723de"
that was not listed on the "hardware-summary"; instead, lsmod shows
"rtw88_8723de".
Then, the module "r8169" tried to load the firmware but that module
belongs to the
GbE card.

I think I'll be sending this to the bug report.

Have a nice day.

-- 
Time zone: GMT-4

[toc] | [prev] | [next] | [standalone]

#233521

[Multipart message — attachments visible in raw view] — view raw

On Thu, Mar 25, 2021, 7:02 PM Cmdte Alpha Tigre Z <santiagopinth@gmail.com>
wrote:

> El jue, 25 mar 2021 a las 17:31, Kenneth Parker (<sea7kenp@gmail.com>)
> escribió:
> > On Thu, Mar 25, 2021, 12:09 PM David Wright <deblis@lionunicorn.co.uk>
> wrote:
> >> But it appears that I might need to point out that it's very easy and
> >> quick to re-collect a failing installation log at any time if the
> >> "original" ones were lost/overwritten or whatever:
> >>
> >>  1. Boot with the appropriate installation medium.
> >>
> >>  2. Proceed with expert installation in the original manner,
> >>     as far as the "Detect Network Hardware", which of course fails.
> >>
> >>  3. After the failure, and back at the Main Menu, select
> >>     "Save debug logs".
> >>
> >>  4. Insert a USB stick, switch to VC2, mount the stick and create
> >>     a directory on it.
> >>
> >>  5. Back at VC1, complete the directory name at the prompt and
> >>     save the logs. (ls on VC2 if you want to check them.)
> >>
> >>  6. Select "Abort the installation". All that should have taken
> >>     about five or ten minutes so far.
> >>
> >>  7. Read/edit/post excerpts from the logs at leisure. (That's when
> >>     it helps to know what strings you're looking for.)
> >
> >
> > Since the actual logs from the Install are small, I proceeded, up to #
> 6.  And then, tarred the resulting directory, and sent it to the Bug Report.
> >
> >> That's what's lacking from the bug report.
> >
> >
> > Hopefully, this will help.
>
> Thank you, Mr. Kenneth Parker.
>
> I noticed in the "syslog" that modprobe couldn't find the module
> "rtw_8723de"
> that was not listed on the "hardware-summary"; instead, lsmod shows
> "rtw88_8723de".
> Then, the module "r8169" tried to load the firmware but that module
> belongs to the
> GbE card.
>
> I think I'll be sending this to the bug report.
>

Thank you!

Have a nice day.
>

You too.

>
> --
> Time zone: GMT-4
>

Kenneth Parker

[toc] | [prev] | [next] | [standalone]

#233508

On Wed, 24 Mar 2021 22:52:31 -0500
David Wright <deblis@lionunicorn.co.uk> wrote:

> My newly oldest computer, an Acer TravelMate 3201XCi,
> built in 2004, contains one of these. If it's of any use to Charles,
> I can warn that this laptop has the annoying habit of booting up
> with the wifi blocked. (It has a pair of insanely placed toggling
> buttons/lights for wifi and bluetooth, and I've never figured out
> what the wifi light correlates with.) I know nothing about the R51
> and whether there are any firmware buttons or function keys that
> would affect its wifi.

 A good thought, thank you. A careful inspection of the computer and
 search of the Hardware Maintenance Manual reveal no such physical
 switch. There is a function key switch which relies on OS support to
 actually do anything, and I doubt that is active in d-i.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

[toc] | [prev] | [next] | [standalone]

#233511

2021-03-25 15:01 GMT-04:00, Charles Curley <charlescurley@charlescurley.com>:
> On Wed, 24 Mar 2021 22:52:31 -0500
> David Wright <deblis@lionunicorn.co.uk> wrote:
>
>> My newly oldest computer, an Acer TravelMate 3201XCi,
>> built in 2004, contains one of these. If it's of any use to Charles,
>> I can warn that this laptop has the annoying habit of booting up
>> with the wifi blocked. (It has a pair of insanely placed toggling
>> buttons/lights for wifi and bluetooth, and I've never figured out
>> what the wifi light correlates with.) I know nothing about the R51
>> and whether there are any firmware buttons or function keys that
>> would affect its wifi.
>
>  A good thought, thank you. A careful inspection of the computer and
>  search of the Hardware Maintenance Manual reveal no such physical
>  switch. There is a function key switch which relies on OS support to
>  actually do anything, and I doubt that is active in d-i.

I also have an Acer minilaptop.  It also has a WiFi on/off hotkey (Fn+F3).
The led that belongs to the WiFi state is the fourth.
The difference here is that it works from startup.  If the WiFi
is disabled through this hotkey, Windows has no way to reenable it,
though it knows that the WiFi is disabled this way.

[toc] | [prev] | [next] | [standalone]

#233340

On Mon 22 Mar 2021 at 14:52:26 -0400, Kenneth Parker wrote:

> On Mon, Mar 22, 2021 at 7:06 AM Andrei POPESCU <andreimpopescu@gmail.com>
> wrote:

[...]
 
> > ...I'd suggest you file a bug
> > against debian-installer, preferably with reportbug immediately after
> > completing the installation.
> >
> 
> That's next on my list.

You have a prima facie case for that (I checked with the Debian
Bullseye Netinst CD). Have you checkd the relevant nodules have
been loaded? Have you tried loading firmware as David Wright
outlines?

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#233342

[Multipart message — attachments visible in raw view] — view raw

On Mon, Mar 22, 2021, 4:40 PM Brian <ad44@cityscape.co.uk> wrote:

> On Mon 22 Mar 2021 at 14:52:26 -0400, Kenneth Parker wrote:
>
> > On Mon, Mar 22, 2021 at 7:06 AM Andrei POPESCU <andreimpopescu@gmail.com
> >
> > wrote:
>
> [...]
>
> > > ...I'd suggest you file a bug
> > > against debian-installer, preferably with reportbug immediately after
> > > completing the installation.
> > >
> >
> > That's next on my list.
>
> You have a prima facie case for that (I checked with the Debian
> Bullseye Netinst CD). Have you checkd the relevant nodules have
> been loaded? Have you tried loading firmware as David Wright
> outlines?
>

I loaded "incomplete" (I think) firmware and, as noted in my response to
Charles, am fighting with getting the commands, needed to navigate WiFi.

But it sounds like a good time to go back to a networked system and figure
out how to put in an intelligent Bug Report.


> Brian.
>

Kenneth Parker

>

[toc] | [prev] | [next] | [standalone]

#233295

On 3/21/21 3:27 PM, Kenneth Parker wrote:
> Hello,
> 
> Later this week, I will be helping a friend install Debian onto a Lenovo
> Ideapad Laptop.  This will be in a Public Space with, only WiFi available.
> 
> Both his Lenovo, and my HP Laptop have the same WiFi hardware, found via a
> "lspci" command:
> 
>> Network controller: Realtek Semiconductor Co., Ltd. RTL8723DE 802.11b/g/n
> PCIe Adapter
> 
> So, to ensure that we can complete the Install, I wanted to test, using,
> first a Debian Bullseye Netinst CD and, when it failed, a Debian Buster
> 10.3 NetInst CD.
> 
> In both cases, I used my favorite, Text / Expert Install (but also tried
> Bullseye with the "normal" Text Install).  it gets to the step, to find,
> and configure the Network, but only finds the Ethernet Port which, for the
> purposes of my test, has no Cable attached.  So, obviously, the Network
> Configuration fails!
> 
> I was ready for it to Find the WiFi, and had, in advance, populated the
> /firmware directory of a USB Thumbdrive, but it never gets to the step,
> where it is asking for it.
> 
> Any Insights?


I cannot explain why the d-i is not prompting for the Wi-Fi adapter 
firmware, but I would use a complete installation image, ignore Wi-Fi, 
and then add Wi-Fi afterwards:

     https://www.debian.org/CD/


David

[toc] | [prev] | [next] | [standalone]

#233296

On 22/3/2021 6:27 am, Kenneth Parker wrote:
> Hello,
> 
> Later this week, I will be helping a friend install Debian onto a Lenovo 
> Ideapad Laptop.  This will be in a Public Space with, only WiFi available.
> 
> Both his Lenovo, and my HP Laptop have the same WiFi hardware, found via 
> a "lspci" command:
> 
>  > Network controller: Realtek Semiconductor Co., Ltd. RTL8723DE 
> 802.11b/g/n PCIe Adapter
> 
> So, to ensure that we can complete the Install, I wanted to test, using, 
> first a Debian Bullseye Netinst CD and, when it failed, a Debian Buster 
> 10.3 NetInst CD.
> 
> In both cases, I used my favorite, Text / Expert Install (but also tried 
> Bullseye with the "normal" Text Install).  it gets to the step, to find, 
> and configure the Network, but only finds the Ethernet Port which, for 
> the purposes of my test, has no Cable attached.  So, obviously, the 
> Network Configuration fails!
> 
> I was ready for it to Find the WiFi, and had, in advance, populated the 
> /firmware directory of a USB Thumbdrive, but it never gets to the step, 
> where it is asking for it.
> 
> Any Insights?
> 
> Thanks in advance!
> 
> Kenneth Parker
Does the installer said missing firmware? or nothing at all?

if the installer said missing firmware, you may take look my previous 
thread[2]  (my solution are here[2])

[1] https://lists.debian.org/debian-user/2021/02/msg00727.html
[2] https://lists.debian.org/debian-user/2021/02/msg00766.html

-- 
Email : Robbi Nespu <robbinespu AT SPAMFREE gmail DOT com>
PGP fingerprint : D311 B5FF EEE6 0BE8 9C91 FA9E 0C81 FA30 3B3A 80BA
PGP key : https://keybase.io/robbinespu/pgp_keys.asc

[toc] | [prev] | [next] | [standalone]

#233298

[Multipart message — attachments visible in raw view] — view raw

On Sun, Mar 21, 2021, 9:24 PM Robbi Nespu <robbinespu@gmail.com> wrote:

> On 22/3/2021 6:27 am, Kenneth Parker wrote:
> > Hello,
> >
> > Later this week, I will be helping a friend install Debian onto a Lenovo
> > Ideapad Laptop.  This will be in a Public Space with, only WiFi
> available.
> >
> > Both his Lenovo, and my HP Laptop have the same WiFi hardware, found via
> > a "lspci" command:
> >
> >  > Network controller: Realtek Semiconductor Co., Ltd. RTL8723DE
> > 802.11b/g/n PCIe Adapter
> >
> > So, to ensure that we can complete the Install, I wanted to test, using,
> > first a Debian Bullseye Netinst CD and, when it failed, a Debian Buster
> > 10.3 NetInst CD.
> >
> > In both cases, I used my favorite, Text / Expert Install (but also tried
> > Bullseye with the "normal" Text Install).  it gets to the step, to find,
> > and configure the Network, but only finds the Ethernet Port which, for
> > the purposes of my test, has no Cable attached.  So, obviously, the
> > Network Configuration fails!
> >
> > I was ready for it to Find the WiFi, and had, in advance, populated the
> > /firmware directory of a USB Thumbdrive, but it never gets to the step,
> > where it is asking for it.
> >
> > Any Insights?
> >
> > Thanks in advance!
> >
> > Kenneth Parker
> Does the installer said missing firmware? or nothing at all?
>

It sits for, about a minute in the "Detect Network Hardware" step.  Then,
when it continues, only the Ethernet Port is detected.  It does not, even
*ask* about Firmware.   So, nothing at all.

if the installer said missing firmware, you may take look my previous
> thread[2]  (my solution are here[2])
>
> [1] https://lists.debian.org/debian-user/2021/02/msg00727.html
> [2] https://lists.debian.org/debian-user/2021/02/msg00766.html


So, for my purposes, install without network is the best that I can do.
And then, in the running system, install the Firmware.

Thanks!

Kenneth Parker

>
>

[toc] | [prev] | [next] | [standalone]

#233325

On Sun 21 Mar 2021 at 21:48:30 (-0400), Kenneth Parker wrote:
> On Sun, Mar 21, 2021, 9:24 PM Robbi Nespu <robbinespu@gmail.com> wrote:
> > On 22/3/2021 6:27 am, Kenneth Parker wrote:
> > >
> > > Both his Lenovo, and my HP Laptop have the same WiFi hardware, found via
> > > a "lspci" command:
> > >
> > >  > Network controller: Realtek Semiconductor Co., Ltd. RTL8723DE
> > > 802.11b/g/n PCIe Adapter
> > >
> > > So, to ensure that we can complete the Install, I wanted to test, using,
> > > first a Debian Bullseye Netinst CD and, when it failed, a Debian Buster
> > > 10.3 NetInst CD.
> > >
> > > In both cases, I used my favorite, Text / Expert Install (but also tried
> > > Bullseye with the "normal" Text Install).  it gets to the step, to find,
> > > and configure the Network, but only finds the Ethernet Port which, for
> > > the purposes of my test, has no Cable attached.  So, obviously, the
> > > Network Configuration fails!
> > >
> > > I was ready for it to Find the WiFi, and had, in advance, populated the
> > > /firmware directory of a USB Thumbdrive, but it never gets to the step,
> > > where it is asking for it.
> > >
> > Does the installer said missing firmware? or nothing at all?
> >
> It sits for, about a minute in the "Detect Network Hardware" step.  Then,
> when it continues, only the Ethernet Port is detected.  It does not, even
> *ask* about Firmware.   So, nothing at all.
> 
> So, for my purposes, install without network is the best that I can do.
> And then, in the running system, install the Firmware.

So I assume that the running system finds the modules, loads them and
also some firmware for them (perhaps even rtl8723defw.bin?), yes?

If so, then it's worth knowing what the installer found. The file on
your installed system /var/log/installer/hardware-summary has its
lsmod output in the third section, after lspci and usb-list.

If they're found, then /var/log/installer/syslog (considerably larger)
should show the module (the rtlNNNN one) being loaded, followed by the
firmware. If you saw no messages on the console, then it's perfectly
possible that the module and its firmware were found and loaded
successfully, but they just didn't make the wifi work, which would be
a completely different bug.

If you've time to spare, you could of course retry the installer
*without* the firmware on a stick, deliberately provoking the module
(if it gets loaded) to complain. These "forensic" observations would
narrow the scope of potential bugs.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#233326

On Mon 22 Mar 2021 at 09:39:54 -0500, David Wright wrote:

> On Sun 21 Mar 2021 at 21:48:30 (-0400), Kenneth Parker wrote:
> > On Sun, Mar 21, 2021, 9:24 PM Robbi Nespu <robbinespu@gmail.com> wrote:
> > > On 22/3/2021 6:27 am, Kenneth Parker wrote:
> > > >
> > > > Both his Lenovo, and my HP Laptop have the same WiFi hardware, found via
> > > > a "lspci" command:
> > > >
> > > >  > Network controller: Realtek Semiconductor Co., Ltd. RTL8723DE
> > > > 802.11b/g/n PCIe Adapter
> > > >
> > > > So, to ensure that we can complete the Install, I wanted to test, using,
> > > > first a Debian Bullseye Netinst CD and, when it failed, a Debian Buster
> > > > 10.3 NetInst CD.
> > > >
> > > > In both cases, I used my favorite, Text / Expert Install (but also tried
> > > > Bullseye with the "normal" Text Install).  it gets to the step, to find,
> > > > and configure the Network, but only finds the Ethernet Port which, for
> > > > the purposes of my test, has no Cable attached.  So, obviously, the
> > > > Network Configuration fails!
> > > >
> > > > I was ready for it to Find the WiFi, and had, in advance, populated the
> > > > /firmware directory of a USB Thumbdrive, but it never gets to the step,
> > > > where it is asking for it.
> > > >
> > > Does the installer said missing firmware? or nothing at all?
> > >
> > It sits for, about a minute in the "Detect Network Hardware" step.  Then,
> > when it continues, only the Ethernet Port is detected.  It does not, even
> > *ask* about Firmware.   So, nothing at all.
> > 
> > So, for my purposes, install without network is the best that I can do.
> > And then, in the running system, install the Firmware.
> 
> So I assume that the running system finds the modules, loads them and
> also some firmware for them (perhaps even rtl8723defw.bin?), yes?
> 
> If so, then it's worth knowing what the installer found. The file on
> your installed system /var/log/installer/hardware-summary has its
> lsmod output in the third section, after lspci and usb-list.
> 
> If they're found, then /var/log/installer/syslog (considerably larger)
> should show the module (the rtlNNNN one) being loaded, followed by the
> firmware. If you saw no messages on the console, then it's perfectly
> possible that the module and its firmware were found and loaded
> successfully, but they just didn't make the wifi work, which would be
> a completely different bug.
> 
> If you've time to spare, you could of course retry the installer
> *without* the firmware on a stick, deliberately provoking the module
> (if it gets loaded) to complain. These "forensic" observations would
> narrow the scope of potential bugs.

All good advice. I think the modules that should be loaded are
rtw88_8723de, rtw88_8723d, rtw88_core and rtw88_pci. After doing
the "Detect Network Hardware" step the OP could use 'lsmod' in a
console.

The buster d-i kernel does not have these modules.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#233297

On Sun 21 Mar 2021 at 18:27:22 (-0400), Kenneth Parker wrote:
> 
> Later this week, I will be helping a friend install Debian onto a Lenovo
> Ideapad Laptop.  This will be in a Public Space with, only WiFi available.
> 
> Both his Lenovo, and my HP Laptop have the same WiFi hardware, found via a
> "lspci" command:
> 
> > Network controller: Realtek Semiconductor Co., Ltd. RTL8723DE 802.11b/g/n
> PCIe Adapter
> 
> So, to ensure that we can complete the Install, I wanted to test, using,
> first a Debian Bullseye Netinst CD and, when it failed, a Debian Buster
> 10.3 NetInst CD.
> 
> In both cases, I used my favorite, Text / Expert Install (but also tried
> Bullseye with the "normal" Text Install).  it gets to the step, to find,
> and configure the Network, but only finds the Ethernet Port which, for the
> purposes of my test, has no Cable attached.  So, obviously, the Network
> Configuration fails!
> 
> I was ready for it to Find the WiFi, and had, in advance, populated the
> /firmware directory of a USB Thumbdrive, but it never gets to the step,
> where it is asking for it.
> 
> Any Insights?

The tests I carried out at the end of last month showed that whereas
wheezy's installer could find "loose files" of firmware on a USB
stick, buster's was unable to.

So the choice nowadays seems to be either to copy .deb files of
firmware onto a USB stick, or to copy the loose files into the real
/lib/firmware directory any time before the "Detect Network Hardware"
step.

You might have to create /lib/firmware, and any subdirectory that the
firmware habitually inhabits, eg /lib/firmware/rtlwifi for rtl8192*.

Cheers,
David.

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | linux.debian.user

csiph-web