Bug#1056697: 12.2 Installation Report, Complete Failure of Network

[Pascal Hambourg]

On 25/11/2023 at 22:29, David Hillman wrote:

On 11/25/23 01:37, Cyril Brulebois wrote:

Extracting /var/log/syslog would be useful to understand what's going on
there. (...)

Thanks Cyril.  This system is running Debian 12, so there is no 
/var/log/syslog.


Cyril meant the installer syslog, which is saved in /var/log/installer 
on the installed system at the end of the installation.


(Gmail will probably reject this mail though)

Bug#1056697: 12.2 Installation Report, Complete Failure of Network

[Cyril Brulebois]

David Hillman  (2023-11-25):
> Thanks Cyril.  This system is running Debian 12, so there is no
> /var/log/syslog.  As I mentioned in the original report, I found nothing
> apparently related in the Journal.

I'm confused. You filed an installation report regarding a failure to
recognize network cards. I'm therefore assuming you're having issues
with the installation process, and requesting /var/log/syslog, which is
definitely where the installer logs what's going on. You also marked the
overall install with E = Error…

It'd make sense to clarify whether the problem affects the installer,
and/or the installed system.

Anyway, a copy of installer logs is available under /var/log/installer/
in the installed system.


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


signature.asc
Description: PGP signature

Bug#1056697: 12.2 Installation Report, Complete Failure of Network

[David Hillman]

On 11/25/23 01:37, Cyril Brulebois wrote:

Extracting /var/log/syslog would be useful to understand what's going on
there. A very quick search suggests this card might be supported by the
tg3 module (drivers/net/ethernet/broadcom/tg3.c), which is definitely
shipped in the installer. So maybe it's something that needs tweaking or
fixing on the firmware side (e.g. “modprobe dance”), or a missing
auxiliary bus (e.g. mhi) to make the card visible. Hard to tell without
any logs.

Thanks Cyril.  This system is running Debian 12, so there is no 
/var/log/syslog.  As I mentioned in the original report, I found nothing 
apparently related in the Journal.



--
David Hillman

Bug#1056697: 12.2 Installation Report, Complete Failure of Network

[Cyril Brulebois]

Lennart Sorensen  (2023-11-25):
> I suspect you are missing the firmware file for the network port.  I think 
> this one:
> 
> firmware-misc-nonfree: /lib/firmware/tigon/tg3.bin
> 
> The installer probably does not include that.

The netinst *definitely* does ship that package:
  
https://cdimage.debian.org/cdimage/release/current/amd64/list-cd/debian-12.2.0-amd64-netinst.list.gz


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


signature.asc
Description: PGP signature

Bug#1056697: 12.2 Installation Report, Complete Failure of Network

[Lennart Sorensen]

On Fri, Nov 24, 2023 at 12:34:50PM -0600, David Hillman wrote:
> 
> Package: installation-reports
> 
> Boot method: USB stick
> Image version: 
> https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-12.2.0-amd64-netinst.iso
> Date: 2023-November-23 11PM GMT
> 
> Machine: Dell R720
> Processor: 2 x Xeon E5-2650
> Memory: 192GB
> 
> Base System Installation Checklist:
> [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
> 
> Initial boot:   [O ]
> Detect network card:    [E ]
> Configure network:  [E ]
> Detect media:   [ ]
> Load installer modules: [ ]
> Detect hard drives: [O ]
> Partition hard drives:  [O ]
> Install base system:    [ ]
> Clock/timezone setup:   [ ]
> User/password setup:    [O ]
> Install tasks:  [ ]
> Install boot loader:    [ ]
> Overall install:    [E ]
> 
> Comments/Problems:
> 
> 
> Installer completely failed to identify the presence of all four integrated
> Broadcom BCM5720 ethernet ports, and even after manually adding and
> configuring the four interfaces, no network connectivity is to be had. 
> Interfaces are allegedly "UP", but cannot ping anything nor respond to any
> communication.  IDRAC card interface works fine -- on the same subnet.  A
> half-dozen other multi-interface machines on the same subnet are working
> fine, as well.
> 
> Ubuntu 20 and 22 installers work just fine on the same hardware, so this is
> a Debian-specific issue.  All four interfaces work just fine under both
> Ubuntu 20 and 22, but are totally dysfunctional with Debian 12.
> 
> Journal entries for NetworkManager and avahi-daemon appear to show the
> correct IP addresses being registered for all four interfaces, and "ip"
> agress, all to no avail.  No related error messages exist in the journal.

I suspect you are missing the firmware file for the network port.  I think this 
one:

firmware-misc-nonfree: /lib/firmware/tigon/tg3.bin

The installer probably does not include that.

-- 
Len Sorensen

Bug#1056697: 12.2 Installation Report, Complete Failure of Network

[Diederik de Haas]

On Saturday, 25 November 2023 08:37:09 CET Cyril Brulebois wrote:
> Hard to tell without any logs.

The output of `lsmod` and `dmesg` from both Ubuntu and Debian may also help to 
figure out why it's working in one but not the other.

signature.asc
Description: This is a digitally signed message part.

Bug#1056697: 12.2 Installation Report, Complete Failure of Network

[Holger Wansing]

Hi,

Am 24. November 2023 23:54:49 MEZ schrieb David Hillman 
:
>On 11/24/23 12:59, Holger Wansing wrote:
>Thanks Holger.  I could do that, but that would completely defeat the purpose. 
> I installed Debian 12 on this machine as a test, to confirm that everything 
>necessary works, before installing it on a dozen or so other similar machines.

Trying a debian 13 image was meant as some sort of debugging. 
It would involve a newer kernel for example, in case it's a kernel issue...


Holger



-- 
Sent from /e/ OS on Fairphone3

Bug#1056697: 12.2 Installation Report, Complete Failure of Network

[Cyril Brulebois]

Hi David,

David Hillman  (2023-11-24):
> Thanks Holger.  I could do that, but that would completely defeat the
> purpose.  I installed Debian 12 on this machine as a test, to confirm that
> everything necessary works, before installing it on a dozen or so other
> similar machines.
> 
> And clearly, the opposite is the case, and it isn't ready for use yet, at
> least, not on server hardware.  I have D12 running on a laptop, and a few
> virtual machines, and it doesn't suffer this problem, but I will apparently
> have to stay with Ubuntu for a while on the servers.

Extracting /var/log/syslog would be useful to understand what's going on
there. A very quick search suggests this card might be supported by the
tg3 module (drivers/net/ethernet/broadcom/tg3.c), which is definitely
shipped in the installer. So maybe it's something that needs tweaking or
fixing on the firmware side (e.g. “modprobe dance”), or a missing
auxiliary bus (e.g. mhi) to make the card visible. Hard to tell without
any logs.


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


signature.asc
Description: PGP signature

Bug#1056697: 12.2 Installation Report, Complete Failure of Network

[David Hillman]

On 11/24/23 12:59, Holger Wansing wrote:

Hi,

David Hillman  wrote (Fri, 24 Nov 2023 12:34:50 -0600):

Ubuntu 20 and 22 installers work just fine on the same hardware, so this
is a Debian-specific issue.  All four interfaces work just fine under
both Ubuntu 20 and 22, but are totally dysfunctional with Debian 12.

Maybe you could try a preview Debian 13 image?
https://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/



Thanks Holger.  I could do that, but that would completely defeat the 
purpose.  I installed Debian 12 on this machine as a test, to confirm 
that everything necessary works, before installing it on a dozen or so 
other similar machines.


And clearly, the opposite is the case, and it isn't ready for use yet, 
at least, not on server hardware.  I have D12 running on a laptop, and a 
few virtual machines, and it doesn't suffer this problem, but I will 
apparently have to stay with Ubuntu for a while on the servers.



--
David Hillman

Bug#1056697: 12.2 Installation Report, Complete Failure of Network

[Holger Wansing]

Hi,

David Hillman  wrote (Fri, 24 Nov 2023 12:34:50 -0600):
> Ubuntu 20 and 22 installers work just fine on the same hardware, so this 
> is a Debian-specific issue.  All four interfaces work just fine under 
> both Ubuntu 20 and 22, but are totally dysfunctional with Debian 12.

Maybe you could try a preview Debian 13 image?
https://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/


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

Bug#1056697: 12.2 Installation Report, Complete Failure of Network

[David Hillman]

Package: installation-reports

Boot method: USB stick
Image version: 
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-12.2.0-amd64-netinst.iso

Date: 2023-November-23 11PM GMT

Machine: Dell R720
Processor: 2 x Xeon E5-2650
Memory: 192GB

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O ]
Detect network card:    [E ]
Configure network:  [E ]
Detect media:   [ ]
Load installer modules: [ ]
Detect hard drives: [O ]
Partition hard drives:  [O ]
Install base system:    [ ]
Clock/timezone setup:   [ ]
User/password setup:    [O ]
Install tasks:  [ ]
Install boot loader:    [ ]
Overall install:    [E ]

Comments/Problems:


Installer completely failed to identify the presence of all four 
integrated Broadcom BCM5720 ethernet ports, and even after manually 
adding and configuring the four interfaces, no network connectivity is 
to be had.  Interfaces are allegedly "UP", but cannot ping anything nor 
respond to any communication.  IDRAC card interface works fine -- on the 
same subnet.  A half-dozen other multi-interface machines on the same 
subnet are working fine, as well.


Ubuntu 20 and 22 installers work just fine on the same hardware, so this 
is a Debian-specific issue.  All four interfaces work just fine under 
both Ubuntu 20 and 22, but are totally dysfunctional with Debian 12.


Journal entries for NetworkManager and avahi-daemon appear to show the 
correct IP addresses being registered for all four interfaces, and "ip" 
agress, all to no avail.  No related error messages exist in the journal.




--
David Hillman