[GH-ISSUE #1662] Live CDs and GParted not working in 2.0.88 -- Ethernet card doesn't come up #2098

Closed
opened 2026-03-01 18:38:28 +03:00 by kerem · 9 comments
Owner

Originally created by @andrechalella on GitHub (Aug 16, 2025).
Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/1662

[x]: This bug persists when memory is increased beyond 8GB.

Describe the bug

In 2.0.88, starting Live CDs (I tested Debian and Kali) or the util GParted hangs with:

Waiting for ethernet card(s) up... If this fails, maybe the ethernet card is not supported by the kernel 6.12.37+deb13-amd64

(kernel version mentioned above changes with the live CD/util)

Trying to install distros, however, works fine.

Additional context

Until 2.0.87:

  • Said Live CDs and GParted worked fine.
  • Several lines about loading modules/firmwares could be seen just before the Waiting for ethernet card(s) up... line. I can see my keyboard/mouse, SCSI stuff and network card there.

In 2.0.88, there are no lines about loading modules.

This was tested in two different computers (one 2012, the other 2017). Both have Realtek cards that use the module r8169.

Screenshots

2.0.87 - Working:

2.0.87 - Working

2.0.88 - Not working:

2.0.88 - Not working
Originally created by @andrechalella on GitHub (Aug 16, 2025). Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/1662 [x]: This bug persists when memory is increased beyond 8GB. <!-- Please validate that the issue is not a symptom of insufficient memory. Many installation media are based on live-cd images that require more than a few MB/GB of memory to run. --> **Describe the bug** In 2.0.88, starting Live CDs (I tested Debian and Kali) or the util GParted hangs with: > Waiting for ethernet card(s) up... If this fails, maybe the ethernet card is not supported by the kernel 6.12.37+deb13-amd64 (kernel version mentioned above changes with the live CD/util) Trying to install distros, however, works fine. **Additional context** Until 2.0.87: - Said Live CDs and GParted worked fine. - Several lines about loading modules/firmwares could be seen just before the `Waiting for ethernet card(s) up...` line. I can see my keyboard/mouse, SCSI stuff and network card there. In 2.0.88, there are no lines about loading modules. This was tested in two different computers (one 2012, the other 2017). Both have Realtek cards that use the module `r8169`. **Screenshots** ✅ 2.0.87 - Working: <img width="1684" height="1263" alt="2.0.87 - Working" src="https://github.com/user-attachments/assets/5a8eba44-9d1b-4402-9705-fc738d9dc424" /> ❌ 2.0.88 - Not working: <img width="1684" height="1263" alt="2.0.88 - Not working" src="https://github.com/user-attachments/assets/7de28abb-60e1-4e08-af56-b334f3dca008" />
kerem 2026-03-01 18:38:28 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@USBAkimbo commented on GitHub (Aug 21, 2025):

Also seeing the same - I'm using the Linuxserver.io image too

This is my working Compose config env vars using 2.0.87

services:
  netbootxyz:
    image: lscr.io/linuxserver/netbootxyz:0.7.6
    container_name: netbootxyz
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
      - MENU_VERSION=2.0.87
      - PORT_RANGE=30000:30010 #optional
      - SUBFOLDER=/ #optional
      - NGINX_PORT=80 #optional
      - WEB_APP_PORT=3000 #optional
<!-- gh-comment-id:3210156436 --> @USBAkimbo commented on GitHub (Aug 21, 2025): Also seeing the same - I'm using the Linuxserver.io image too This is my working Compose config env vars using `2.0.87` ``` services: netbootxyz: image: lscr.io/linuxserver/netbootxyz:0.7.6 container_name: netbootxyz environment: - PUID=1000 - PGID=1000 - TZ=Etc/UTC - MENU_VERSION=2.0.87 - PORT_RANGE=30000:30010 #optional - SUBFOLDER=/ #optional - NGINX_PORT=80 #optional - WEB_APP_PORT=3000 #optional ```
Author
Owner

@wrobelda commented on GitHub (Sep 26, 2025):

I tried with two different NICs (VirtIO, RTL8139) today, to no avail. Doesn't look like it's the upstream fault.

<!-- gh-comment-id:3339340157 --> @wrobelda commented on GitHub (Sep 26, 2025): I tried with two different NICs (VirtIO, RTL8139) today, to no avail. Doesn't look like it's the upstream fault.
Author
Owner

@wrobelda commented on GitHub (Sep 26, 2025):

This is a duplicate of #1626

<!-- gh-comment-id:3339409261 --> @wrobelda commented on GitHub (Sep 26, 2025): This is a duplicate of #1626
Author
Owner

@andrechalella commented on GitHub (Sep 26, 2025):

I was thinking it might be upstream. Why do you think it's not?

About the duplicate: yeah, looks like it is. I don't know why all over the internet (including the duplicate) people find this bug with Clonezilla, though.

<!-- gh-comment-id:3339618261 --> @andrechalella commented on GitHub (Sep 26, 2025): I was thinking it might be upstream. Why do you think it's not? About the duplicate: yeah, looks like it is. I don't know why all over the internet (including the duplicate) people find this bug with Clonezilla, though.
Author
Owner

@wrobelda commented on GitHub (Sep 26, 2025):

I was thinking it might be upstream. Why do you think it's not?

Actually might still be upstream indeed, just wanted to make sure it wasn't specific to a particular NIC.

About the duplicate: yeah, looks like it is. I don't know why all over the internet (including the duplicate) people find this bug with Clonezilla, though.

<!-- gh-comment-id:3339683916 --> @wrobelda commented on GitHub (Sep 26, 2025): > I was thinking it might be upstream. Why do you think it's not? Actually might still be upstream indeed, just wanted to make sure it wasn't specific to a particular NIC. > About the duplicate: yeah, looks like it is. I don't know why all over the internet (including the duplicate) people find this bug with Clonezilla, though.
Author
Owner

@KSebion commented on GitHub (Sep 26, 2025):

About the duplicate: yeah, looks like it is. I don't know why all over the internet (including the duplicate) people find this bug with Clonezilla, though.
Same problem with Grml too.

<!-- gh-comment-id:3339710657 --> @KSebion commented on GitHub (Sep 26, 2025): > About the duplicate: yeah, looks like it is. I don't know why all over the internet (including the duplicate) people find this bug with Clonezilla, though. Same problem with Grml too.
Author
Owner

@henkez73 commented on GitHub (Nov 7, 2025):

The initrd file for e.g. clonezilla/gparted does not have the drivers. I've replaced the initrd file with the one from the respective downloads (size was ~150k, downloaded one has size ~450k). Now the netboot works again as it has the drivers available...

<!-- gh-comment-id:3504861659 --> @henkez73 commented on GitHub (Nov 7, 2025): The initrd file for e.g. clonezilla/gparted does not have the drivers. I've replaced the initrd file with the one from the respective downloads (size was ~150k, downloaded one has size ~450k). Now the netboot works again as it has the drivers available...
Author
Owner

@antonym commented on GitHub (Nov 8, 2025):

I found that the iso processing logic was not handling the initrd layers on the newer structures. Fix is here and latest rebuilds of Clonezilla (Ubuntu) and Gparted are loading correctly in Dev.

github.com/netbootxyz/docker-iso-processor@7262fb896f

I'll work on getting this all released this weekend.

<!-- gh-comment-id:3506731225 --> @antonym commented on GitHub (Nov 8, 2025): I found that the iso processing logic was not handling the initrd layers on the newer structures. Fix is here and latest rebuilds of Clonezilla (Ubuntu) and Gparted are loading correctly in Dev. https://github.com/netbootxyz/docker-iso-processor/commit/7262fb896fe93aef95e62632d8cf8d9de6b5d199 I'll work on getting this all released this weekend.
Author
Owner

@antonym commented on GitHub (Nov 8, 2025):

Should be in Release 2.0.89 going out today, fixed Clonezilla/Gparted so far, any others should get picked up during future runs.

<!-- gh-comment-id:3506794364 --> @antonym commented on GitHub (Nov 8, 2025): Should be in Release 2.0.89 going out today, fixed Clonezilla/Gparted so far, any others should get picked up during future runs.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/netboot.xyz#2098
No description provided.