ISO from gumanzoy's liveusb-doglinux-debian-12-2024.10.08

[fredx181]

@fredx181

For what it's worth, booted this on my old HP laptop, lspci gives:
18:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetLink BCM5787M Gigabit Ethernet PCI Express (rev 02)
It's using tg3 too, and no problems, eth0 connected instantly.

Interesting. Boot this .iso or another build? With porteus initrd or debian live-boot?

Yes, booted this ISO (using Ventoy) with porteus initrd.

[gumanzoy]

Yes, booted this ISO (using Ventoy) with porteus initrd.

amd64 kernel 6.10 or 5.10 ? or 32bit 6.1 ?

Can you try another kernels please.

[fredx181]

Yes, booted this ISO (using Ventoy) with porteus initrd.

amd64 kernel 6.10 or 5.10 ? or 32bit 6.1 ?

Can you try another kernels please.

Booted all fine to the Desktop on my HP Compaq 6710b laptop (tested with amd64 kernel 6.10, 5.10 and 32bit 6.1) , also wired connection works with all these.

edit: as a side note: on my newer laptop from 2022, booting with the 32bit 6.1 doesn't work out of the box (blank screen), but I knew that from earlier tests with 32-bit build.
Fixed it by creating /etc/X11/xorg.conf with content:

Code: Select all

Section "Device"
   Identifier "Device0"
   Driver "intel"
EndSection

[gumanzoy]

@fredx181

Please show lsmod | grep tg3 lsmod | grep broadcom

I suspect lack of kernel/drivers/net/phy/broadcom.ko in initrd.

But i think not all Broadcom tg3 adapters affected. In Clarity's lspci and in comment from my blog at may 2022 - same Broadcom Netlink BCM57780

@Clarity
Please try rmmod tg3 && modprobe tg3 after boot with unmodified initrd.
And if its start working after that - Please show lsmod | grep tg3 lsmod | grep broadcom and dmesg -t

EDIT: i look at source of kernel/drivers/net/phy/broadcom.ko and find BCM57780 but not BCM5787M
https://github.com/torvalds/linux/blob/ ... broadcom.c

Code: Select all

	/* Abort if we are using an untested phy. */
	if (BRCM_PHY_MODEL(phydev) != PHY_ID_BCM57780 &&
	    BRCM_PHY_MODEL(phydev) != PHY_ID_BCM50610 &&
	    BRCM_PHY_MODEL(phydev) != PHY_ID_BCM50610M &&
	    BRCM_PHY_MODEL(phydev) != PHY_ID_BCM54210E &&
	    BRCM_PHY_MODEL(phydev) != PHY_ID_BCM54810 &&
	    BRCM_PHY_MODEL(phydev) != PHY_ID_BCM54811)
		return;

Prototype of /usr/local/cr-initrd/initramfs/linuxrc changes for fix PXE support

Old version

Code: Select all

if [ $IP ]; then BOOTDEV=network; CFGDEV=/mnt/nfs
#   softdep for r8169 https://bugzilla.kernel.org/show_bug.cgi?id=204343
    modprobe realtek 2>/dev/null
    for x in `lspci | grep 0200: | cut -d: -f3-4 | sed s/:/.*/g | tr a-z A-Z`; do modprobe `grep $x /lib/modules/$(uname -r)/modules.alias | tail -n1 | rev | cut -d" " -f1 | rev` 2>/dev/null; done

New version

Code: Select all

if [ $IP ]; then BOOTDEV=network; CFGDEV=/mnt/nfs
#   softdep for r8169 https://bugzilla.kernel.org/show_bug.cgi?id=204343
    lspci | grep 0200: >/tmp/lspci; grep -q 10ec: /tmp/lspci && modprobe realtek 2>/dev/null
    grep -q 14e4: /tmp/lspci && modprobe broadcom 2>/dev/null
    for x in `cut -d: -f3-4 /tmp/lspci | sed s/:/.*/g | tr a-z A-Z`; do modprobe `grep $x /lib/modules/$(uname -r)/modules.alias | tail -n1 | rev | cut -d" " -f1 | rev` 2>/dev/null; done

Also need /usr/local/cr-initrd/mkinitrd and /usr/local/cr-initrd/initramfs/modlist changes

[fredx181]

@fredx181

Please show lsmod | grep tg3 lsmod | grep broadcom

I suspect lack of kernel/drivers/net/phy/broadcom.ko in initrd.

Code: Select all

root@live:~# lsmod | grep tg3
tg3                   221184  0
libphy                225280  1 tg3
root@live:~# lsmod | grep broadcom
root@live:~#

Probably that's right "I suspect lack of kernel/drivers/net/phy/broadcom.ko in initrd". no output of grep broadcom

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Btw, said it earlier, the Netsurf browser is terrible (made this post with it and got annoyed many times ).

edit: used firefox later to add some icons on previous line to express better my emotions about netsurf

[rcrsn51]

I can't find any evidence that the tg3.ko module needs the broadcom.ko module.

I no longer have a tg3 device but I remember seeing this problem. IIRC, I fixed it by using the method I described above.

[gumanzoy]

I can't find any evidence that the tg3.ko module needs the broadcom.ko module.

I no longer have a tg3 device but I remember seeing this problem. IIRC, I fixed it by using the method I described above.

Pls look at EDIT of my last post. I look at source https://github.com/torvalds/linux/blob/ ... broadcom.c and it have model BCM57780 but not BCM5787M

If Clarity check lsmod | grep broadcom after rmmod tg3 && modprobe tg3 we will see....

But better to remove tg3 from /usr/local/cr-initrd/initramfs/modlist network modules don't need to modprobe in initrd except for PXE booting.

[rcrsn51]

No reply from Clarity on either the tg3 or hdmi-audio issues.

[Clarity]

Pristine boot, launched via SG2D. Results on this PC that I thought has the adapter problem. I think I may be the other nvidia PC that had the problem.

Code: Select all

root@live:~# echo "run requested test for the developer";ip addr # check h/w for the;lsmod | grep broadcom # check for module;

run requested test for the developer
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 14:fe:b5:e6:f4:d9 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.27/24 brd 192.168.1.255 scope global noprefixroute eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::930b:263e:91d0:f34c/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
root@live:~# echo "funny...no problem. Will check the other nVidia test PC" 
funny...no problem. Will check the other nVidia test PC
root@live:~# 

Audio on this PC does not play via TV's speakers. Only via PC's internal speakers.

Audio setting will not route to HDMI TV speakers.png (368.02 KiB) Viewed 844 times

[Clarity]

OK, tested the correct PC with the problem.

Code: Select all

root@live:~# echo 'Run requested test for the Developer';ip addr;
Run requested test for the Developer
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
root@live:~# lsmod | grep broadcom
root@live:~# rmmod tg3 && modprobe tg3;ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
root@live:~# lsmod |grep tg3
root@live:~# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
root@live:~# 

[Clarity]

Hello @gumanzoy

This post has nothing to do with the problems I have, BUT it may have a broader audience in distros built in the PLDF forum.

Dont know it you participate in WoofCE Github development team, but if so, would you consider offering them the changes you have demonstrated in nvidia discovery at pristine boots?

Just a thougth! NO reply seeked or expected to this post. Its just a thought of what I see as this distro's valuable trait; namely the 'automation of video adapter discovery'.

[Clarity]

I have the ability to launch ISO files from either a Ventoy or SG2D USB (even can use ISObooter via either USB). I tried with NO success for the distro to boot to desktop via Ventoy whereas in SG2D launching the ISO file will progress to desktop with no problem.

When the distro boots starts, it will issue a message and wait for user to kit the enter-key, followed by it dropping to a console prompt with no ability to boot. I could run debugsave, but elected NOT because i think this distro will be upgraded soon: Message ==> from = Cheatcode is incorrect ... hit Enter-key

I have noticed that @fredx181 has tested with a porteus initrd which appears to allow this distro to go to desktop without issue.

[gumanzoy]

@Clarity

Hi

About HDMI sound problem. Pls look at my post1 and post2 for instructions.
Need to create .asoundrc file and unmute all S/PDIF in alsamixer

---

About Broadcom tg3

Can you check again on this PC
PC with lspci show this adapter
05:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetLink BCM57780 Gigabit Ethernet PCIe (rev 01)

I don't understand what happened in your post:

OK, tested the correct PC with the problem.

Code: Select all

root@live:~# echo 'Run requested test for the Developer';ip addr;
Run requested test for the Developer
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
root@live:~# lsmod | grep broadcom
root@live:~# rmmod tg3 && modprobe tg3;ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
root@live:~# lsmod |grep tg3
root@live:~# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
root@live:~# 

root@live:~# lsmod |grep tg3
Not show modules. Why?

Can you run this at next boot:

Code: Select all

lspci | grep -i broadcom
ifconfig
lsmod | grep tg3
lsmod | grep broadcom

rmmod tg3
modprobe tg3
dmesg -t > dmesg1.txt
ifconfig
lsmod | grep tg3
lsmod | grep broadcom

rmmod tg3
modprobe broadcom
modprobe tg3
dmesg -t > dmesg2.txt
ifconfig
lsmod | grep tg3
lsmod | grep broadcom

And attach dmesg1.txt and dmesg2.txt please.

---

About boot .iso from Ventoy

Can boot with Ventoy in normal mode. But need to enable VTOY_LINUX_REMOUNT option.

https://www.ventoy.net/en/plugin_control.html

[fredx181]

root@live:~# lsmod |grep tg3
Not show modules. Why?

Yes, when doing modprobe tg3 after rmmod tg3 it should show the modules again (if not, something is very wrong, I guess).

Code: Select all

root@live:~# lsmod |grep tg3
tg3                   221184  0
libphy                225280  1 tg3
root@live:~# rmmod tg3
root@live:~# lsmod |grep tg3
root@live:~# modprobe tg3
root@live:~# lsmod |grep tg3
tg3                   221184  0
libphy                225280  1 tg3
root@live:~# 

[Clarity]

Hello @gumanzoy
I ran your script as follows:

Code: Select all

lspci | grep -i broadcom
ifconfig
lsmod | grep tg3
lsmod | grep broadcom
read -p "Press Enter to continue ..."

rmmod tg3
modprobe tg3
dmesg -t > dmesg1.txt
ifconfig
lsmod | grep tg3
lsmod | grep broadcom
read -p "Press Enter to continue ..."

rmmod tg3
modprobe broadcom
modprobe tg3
dmesg -t > dmesg2.txt
ifconfig
lsmod | grep tg3
lsmod | grep broadcom
echo "LAN adapter tests completed"
echo "LAN adapter tests completed"

Results

Code: Select all

root@live:~# LANadapterTest.sh 
05:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetLink BCM57780 Gigabit Ethernet PCIe (rev 01)
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 2  bytes 140 (140.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2  bytes 140 (140.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

tg3                   221184  0
libphy                225280  1 tg3
Press Enter to continue ...
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 2  bytes 140 (140.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2  bytes 140 (140.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

tg3                   221184  0
libphy                225280  3 tg3,broadcom,bcm_phy_lib
broadcom               28672  1
bcm_phy_ptp            20480  1 broadcom
bcm_phy_lib            32768  2 bcm_phy_ptp,broadcom
libphy                225280  3 tg3,broadcom,bcm_phy_lib
Press Enter to continue ...
eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 00:25:64:e4:40:8f  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 17  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 2  bytes 140 (140.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2  bytes 140 (140.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

tg3                   221184  0
libphy                225280  3 tg3,broadcom,bcm_phy_lib
broadcom               28672  1
bcm_phy_ptp            20480  1 broadcom
bcm_phy_lib            32768  2 bcm_phy_ptp,broadcom
libphy                225280  3 tg3,broadcom,bcm_phy_lib
LAN adapter tests completed
LAN adapter tests completed
root@live:~#

Adapter is now present!

[gumanzoy]

@Clarity

Nice.

But i don't understand now why second run of ifconfig after rmmod tg3; modprobe tg3 now show eth0
As i see lsmod show exactly same at second and last step.

Code: Select all

tg3                   221184  0
libphy                225280  3 tg3,broadcom,bcm_phy_lib
broadcom               28672  1
bcm_phy_ptp            20480  1 broadcom
bcm_phy_lib            32768  2 bcm_phy_ptp,broadcom
libphy                225280  3 tg3,broadcom,bcm_phy_lib

You not save dmesg1.txt and dmesg2.txt ? Can you attach this please.

Next step to check should be is remove tg3 from /usr/local/cr-initrd/initramfs/modlist, run mkinitrd and boot with new initrd1.xz

To fix function in runtime but not PXE. Remove tg3 from /usr/local/cr-initrd/initramfs/modlist
Then run /usr/local/cr-initrd/mkinitrd to create new initrd1.xz for kernel you use.
But i don't know how you can update it in .iso file. I recommend to boot from live folder makes easy to update some modules.

I make it for default kernel 6.10.12 and upload https://wdho.ru/syWl/initrd1.xz
Can you download it and replace live/initrd1.xz

I hope to adapter present at boot with updated initrd1.xz.

EDIT: For Ventoy you can use my installation method. To boot from folder, but not from .iso file.

And for Ventoy i have better way to installation described in install_en.txt
By custom grub2 menu ventoy/ventoy_grub.cfg

Copy folders live live32 and ventoy to drive.
When boot Ventoy menu appears - press F6 to show DebianDog menu.

This makes easier to update live/initrd1.xz

@fredx181

Hi.

Can you please test it too with your old HP laptop.

For what it's worth, booted this on my old HP laptop, lspci gives:
18:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetLink BCM5787M Gigabit Ethernet PCI Express (rev 02)
It's using tg3 too, and no problems, eth0 connected instantly.

[fredx181]

Can you please test it too with your old HP laptop.

For what it's worth, booted this on my old HP laptop, lspci gives:
18:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetLink BCM5787M Gigabit Ethernet PCI Express (rev 02)
It's using tg3 too, and no problems, eth0 connected instantly.

Tested booting with https://wdho.ru/syWl/initrd1.xz and works OK, tg3 loaded and got eth0 connection.

[rcrsn51]

I once owned an HP thin client t510 with the tg3 problem. I could fix it by unloading/reloading the module before the DHCP request.

Some googling suggests that the problem is caused by the broadcom.ko module missing from the initrd, as mentioned above.

I may have to find another t510 to test this.

[gumanzoy]

I once owned an HP thin client t510 with the tg3 problem.

I may have to find another t510 to test this.

Hi

This would be nice. Need to test PXE boot with tg3 Broadcom NetLink BCM57780

I could fix it by unloading/reloading the module before the DHCP request.

Some googling suggests that the problem is caused by the broadcom.ko module missing from the initrd.

I told the same .

I suspect lack of kernel/drivers/net/phy/broadcom.ko in initrd.

EDIT: i look at source of kernel/drivers/net/phy/broadcom.ko and find BCM57780 but not BCM5787M
https://github.com/torvalds/linux/blob/ ... broadcom.c

But better to remove tg3 from /usr/local/cr-initrd/initramfs/modlist network modules don't need to modprobe in initrd except for PXE booting.

I hope i fix it now.

I make it for default kernel 6.10.12 and upload https://wdho.ru/syWl/initrd1.xz

[Clarity]

Hi @gumanzoy

Sorry, I forgot to attached the dmesg files before PC shutdown.

On the initrd replacements, I ONLY do ISO file booting for my Frugal usage. Your methods suggest to have and extraction type of installation environment. On that PC there is no OSes or extracted versions of an OS of any sort.

Thus, in my case, I would have to unload the ISO file to a folder, then extract, then rebuild a new ISO and reboot. I do not install any Linux OSes anymore.

Forum distros are to my liking as they offer the ability to launch ISO files for desktop use and persistence over time.

If there are other test that I can run using the ISO to help, I will.

@fredx181, althought I have not done so for your DOGs, I will begin a DOGs table that mirrors the tables done for most of the other forum distros...soon. The table will attempt to reflect ISO boot tests such that each person who builds using the DOGs builders will be able to know what works from "ISO boots to persistence" on bare-metal as well as in KVMs. I will only concentrate on 64bit distros (not enough time in my day to cover OSes for PCs that existed over 2 decades ago).

EDIT: After posting, I reflected that all of my 64bit PCs are OLD with the youngest born in 2016, an AIO. I am OLD!!! ... with OLD stuff!!! HA and WOW!

[gumanzoy]

On the initrd replacements, I ONLY do ISO file booting for my Frugal usage. Your methods suggest to have and extraction type of installation environment. On that PC there is no OSes or extracted versions of an OS of any sort.

Thus, in my case, I would have to unload the ISO file to a folder, then extract, then rebuild a new ISO and reboot. I do not install any Linux OSes anymore.

Run DogLinux from live folder - is not OS installation.
Just copy live folder with distro and ventoy folder with config to USB drive with Ventoy - same as you do it with .iso files.
When boot from Ventoy USB drive - press F6 after Ventoy menu appears to enter to DebianDog boot menu.

[Clarity]

Edit 1: OK, I made a mistake in my report as I booted the wrong USB.

Correct now, the distro boots via F6 with the identical LAN behavior .

Will need some time to make the change of the initrd you request.

Edit 2: Using your latest initrd, the distro is finding the adapter on boot to desktop; namely 'eth0' is now found and IP assignment proceeded successfully.

[gumanzoy]

Annother way for create iso from liveusb tree described in iso_doglinux/iso_doglinux_readme_en.txt
Provided iso_doglinux/boot/grub/grub.cfg

Code: Select all

mv live* ./iso_doglinux
grub-mkrescue --locales= -volid DogLinux -o doglinux.iso ./iso_doglinux

Сan use this way to create updated .iso.
Boot existing .iso.
Connect internet.

Code: Select all

apt update
apt -y install grub-common grub-pc-bin grub-efi-amd64-bin mtools xorriso

Copy iso_doglinux folder from .iso to some rw partition (filesystem type doesn't matter)
Copy live folder to iso_doglinux
Copy updated initrd1.xz to iso_doglinux/live/initrd1.xz
Run

Code: Select all

grub-mkrescue --locales= -volid DogLinux -o doglinux.iso ./iso_doglinux

Finally get updated doglinux.iso

[Clarity]

See above, your post for an updated status. The quote you are using was deleted when I discovered an error on my end.

Hope the status is helpful.

[fredx181]

Against my better judgement, I copied both live & ventoy folders from the ISO onto the Ventoy partition of my USB drive. Booting the USB and hitting F6 produces a boot error where it cannot find the .cfg file it is looking for.

What error exactly?
Can not find ventoy/ventoy_grub.cfg ?
...

Works for me, just copied the live folder and the ventoy folder (containing ventoy_grub.cfg) to the first Ventoy partition (where I have my ISO's too) and pressed F6.

edit: oh I see now that you made it work, nice.

[gumanzoy]

Edit 2: Using your latest initrd, the distro is finding the adapter on boot to desktop; namely 'eth0' is now found and IP assignment proceeded successfully.

Hope the status is helpful.

Thanks. I think we fix problem with tg3 Broadcom Netlink BCM57780 Ethernet adapter

viewtopic.php?p=134013#p134013

Thanks to @gumanzoy and @Clarity (for testing) , changes:
- the upgrade-kernel package is upgraded in the repository, now v1.16.0

[rcrsn51]

Thanks. I think we fix problem with tg3 Broadcom Netlink BCM57780 Ethernet adapter

What was the solution - to remove tg3 or to include the broadcom module?

[gumanzoy]

Thanks. I think we fix problem with tg3 Broadcom Netlink BCM57780 Ethernet adapter

What was the solution - to remove tg3 or to include the broadcom module?

Hi

For normal boot - remove tg3 from modlist

For PXE network boot add broadcom module to initrd + add to linuxrc code to modprobe broadcom in case of PXE boot. But it need to test. I no have such hardware.

Code: Select all

+   copy_including_deps /$LMK/kernel/drivers/net/phy/broadcom.*
    copy_including_deps /$LMK/kernel/drivers/net/phy/realtek.*

Code: Select all

 echo $i"searching for $CFG file"
 if [ $IP ]; then BOOTDEV=network; CFGDEV=/mnt/nfs
 #   softdep for r8169 https://bugzilla.kernel.org/show_bug.cgi?id=204343
-    modprobe realtek 2>/dev/null
-    for x in `lspci | grep 0200: | cut -d: -f3-4 | sed s/:/.*/g | tr a-z A-Z`; do modprobe `grep $x /lib/modules/$(uname -r)/modules.alias | tail -n1 | rev | cut -d" " -f1 | rev` 2>/dev/null; done
+    lspci | grep 0200: >/tmp/lspci; grep -q 10ec: /tmp/lspci && modprobe realtek 2>/dev/null
+    grep -q 14e4: /tmp/lspci && modprobe broadcom 2>/dev/null
+    for x in `cut -d: -f3-4 /tmp/lspci | sed s/:/.*/g | tr a-z A-Z`; do modprobe `grep $x /lib/modules/$(uname -r)/modules.alias | tail -n1 | rev | cut -d" " -f1 | rev` 2>/dev/null; done

[rcrsn51]

Just out of curiosity - tg3 uses firmware but I can't see anywhere in the initrd scripts where firmware gets included.

[gumanzoy]

Just out of curiosity - tg3 uses firmware but I can't see anywhere in the initrd scripts where firmware gets included.

No firmware included in initrd now.

realtek r8169 have firmware too /lib/firmware/rtl_nic/ but it works without it.
I think most popular is realtek now. I use PXE boot frequently and not see any problem without realtek firmware.

As i told before. We need to test PXE boot with tg3 adapters.

If some firmware really need to some adapter works - it can be included by modify mkinitrd