Please select To the mobile version | Continue to access the desktop computer version
View: 680|Reply: 7

SER6 Pro Max no networking on Proxmox 8

[Copy link]

1

Threads

1

Posts

15

Credits

Newbie

Rank: 1

Credits
15
Post time 2023-10-08 22:05:35 | Show all posts |Read mode
My SER6 Pro Max 6900HX arrived yesterday but I'm not able to use proxmox (pve) on it.
Version 8 does install and get an IP address, but no connection except localhost.
Version 7 and lower don't install at all (maybe driver problems).

Ubuntu live 22 (USB stick boot) works flawlessly. Networking and everything else. Ubuntu Server same game, no networking! It's curious.
Reply

Use magic Report

0

Threads

3

Posts

20

Credits

Newbie

Rank: 1

Credits
20
Post time 2023-10-09 23:35:24 | Show all posts
@GingerDog Ty !

I clicked on the first reddit link and found the solution,

if other people have the same problem, just open the grub configuration file (/etc/default/grub) and add and modify the GRUB_CMDLINE_LINUX_DEFAULT line like this:

GRUB_CMDLINE_LINUX_DEFAULT="quiet pcie_port_pm=off pcie_aspm.policy=performance"
Reply Support 1 Not support 0

Use magic Report

0

Threads

3

Posts

20

Credits

Newbie

Rank: 1

Credits
20
Post time 2023-10-09 01:02:38 | Show all posts
Hello, i have a similar problem, when I start proxmox on my SER6 MAX everything goes fine after a few hours it will be disconnected from the ethernet network with this error:

pve-sermax login: [18.904761 18.9048241 igc 0000:02:00.0: 18.904859 1gc 0000:02:00.0: [14] CmpltTO 19.0585391 24.8848541 24-0049081 igc 0000:02:00.0: 24.8849411 igc 0000:02:00.0: [14] CmpltTo 25.004283] Igc 0000:02:00.0: PCIe Bus Error: severity-Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) device [8086:15f3] error status/mask=00004000/00000000 genira: Flags mismatch irq 76. 00000000 (enp2s0) vs. 00000000 (enp2s©) igc 0000:02:00.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) device [8086:15f3] error status/mask=00004000/00000000 genira: Flags mismatch ira 76. 00000000 (enp2se) vs. 00000000 (enp2s@)


and here are the errors on my journalctl :

Oct 08 18:30:52 pve-ser6max kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP2.WWAN], AE_NOT_FOUND (20221020/dswl>
Oct 08 18:30:52 pve-ser6max kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20221020/psobject-220)
Oct 08 18:30:52 pve-ser6max kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP5.RTL8], AE_NOT_FOUND (20221020/dswl>
Oct 08 18:30:52 pve-ser6max kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20221020/psobject-220)
Oct 08 18:30:52 pve-ser6max kernel: hub 6-0:1.0: config failed, hub doesn't have any ports! (err -19)
Oct 08 18:30:52 pve-ser6max kernel: Bluetooth: hci0: FW download error recovery failed (-19)
Oct 08 18:30:52 pve-ser6max kernel: Bluetooth: hci0: sending frame failed (-19)
Oct 08 18:30:52 pve-ser6max kernel: Bluetooth: hci0: Failed to read MSFT supported features (-19)
Oct 08 18:30:54 pve-ser6max smartd[748]: Device: /dev/nvme1, number of Error Log entries increased from 83 to 84
Oct 08 18:30:55 pve-ser6max kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Reply Support Not support

Use magic Report

0

Threads

597

Posts

1997

Credits

Moderator

Rank: 7Rank: 7Rank: 7

Credits
1997
Post time 2023-10-09 10:09:14 | Show all posts
will test it, and then get back to you. thanks
Reply Support Not support

Use magic Report

0

Threads

3

Posts

20

Credits

Newbie

Rank: 1

Credits
20
Post time 2023-10-09 15:49:52 | Show all posts
great, thanks.
Reply Support Not support

Use magic Report

1

Threads

11

Posts

125

Credits

Member

Rank: 2

Credits
125
Post time 2023-10-09 16:07:28 | Show all posts
@AZYxV

From previous experience with this forum, I can't post links ... however if you google for :

I225-V pcie bus error

and choose the first link ( from reddit / buidapc ... ) you'll see someone suggesting it might be a bios/power saving issue, and perhaps adding some flags to the kernel will fix it.

I don't think the journalctl output is relevant. Given it did work with one ubuntu variant, makes me wonder what's changed between the livecd and the install - and that's probably something like the kernel version.
Reply Support Not support

Use magic Report

0

Threads

597

Posts

1997

Credits

Moderator

Rank: 7Rank: 7Rank: 7

Credits
1997
Post time 2023-10-10 09:14:04 | Show all posts
hello, they said it supports pve8.0-2. have a nice day!
Reply Support Not support

Use magic Report

0

Threads

1

Posts

29

Credits

Newbie

Rank: 1

Credits
29
Post time 2023-11-07 07:10:00 | Show all posts
Edited by ___ at 2023-11-07 07:12

I have a Beelink SER 6 Max 7735HS and the builtin Intel nic drops for me as well. I'm running Proxmox VE 8.04. The Beelink is only a month old purchased from Amazon.

I have also followed the advice from Reddit (and others) where they suggest disabling power management using the Grub parameters already mentioned. Verified they were applied after a reboot but the NIC still drops. There's no pattern to when, sometimes an hour after restart, other times days or weeks later.

I checked BIOS for PCIE power management options but I wasn't able to find any. It appears it is a common issue with the Intel I225-V devices.

This is what appears in the syslog/journalctl when the NIC drops:

  1. Oct 16 04:31:49 pve kernel: igc 0000:01:00.0 enp1s0: PCIe link lost, device now detached
  2. Oct 16 04:31:49 pve kernel: ------------[ cut here ]------------
  3. Oct 16 04:31:49 pve kernel: igc: Failed to read reg 0xc030!
  4. Oct 16 04:31:49 pve kernel: WARNING: CPU: 1 PID: 24 at drivers/net/ethernet/intel/igc/igc_main.c:6440 igc_rd32+0xa4/0xc0 [igc]
  5. Oct 16 04:31:49 pve kernel: Modules linked in: tcp_diag inet_diag ebtable_filter ebtables ip_set ip6table_raw iptable_raw ip6table_filter ip6_tables iptable_filter bpfilter nf_tables bonding tls softdog sunrpc nfnetlink_log nfnetlink binfmt_misc amdgpu snd_soc_dmic snd_soc_acp6x_mach snd_acp6x_pdm_dma snd_sof_amd_rembrandt snd_sof_amd_renoir intel_rapl_msr snd_sof_amd_acp intel_rapl_common snd_sof_pci snd_sof_xtensa_dsp edac_mce_amd snd_hda_codec_realtek iwlmvm snd_sof snd_hda_codec_generic iommu_v2 snd_sof_utils drm_buddy kvm_amd gpu_sched ledtrig_audio snd_soc_core drm_ttm_helper snd_hda_codec_hdmi mac80211 snd_compress ttm ac97_bus snd_hda_intel snd_pcm_dmaengine kvm snd_pci_ps snd_intel_dspcfg btusb snd_rpl_pci_acp6x drm_display_helper snd_intel_sdw_acpi btrtl snd_acp_pci libarc4 btbcm irqbypass snd_pci_acp6x cec snd_hda_codec crct10dif_pclmul btintel btmtk polyval_clmulni snd_hda_core snd_pci_acp5x polyval_generic rc_core ghash_clmulni_intel snd_hwdep bluetooth drm_kms_helper snd_rn_pci_acp3x
  6. Oct 16 04:31:49 pve kernel: input_leds iwlwifi snd_pcm i2c_algo_bit sha512_ssse3 snd_acp_config syscopyarea aesni_intel snd_timer snd_soc_acpi sysfillrect ecdh_generic crypto_simd snd cryptd cfg80211 rapl wmi_bmof pcspkr ecc k10temp sysimgblt snd_pci_acp3x ccp soundcore amd_pmc acpi_tad serio_raw mac_hid zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_net vhost vhost_iotlb tap drm efi_pstore dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq simplefb hid_sensor_hub hid_generic dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio libcrc32c xhci_pci xhci_pci_renesas nvme crc32_pclmul thunderbolt xhci_hcd nvme_core amd_sfh i2c_piix4 igc nvme_common video wmi i2c_hid_acpi i2c_hid hid
  7. Oct 16 04:31:49 pve kernel: CPU: 1 PID: 24 Comm: kworker/1:0 Tainted: P O 6.2.16-15-pve #1
  8. Oct 16 04:31:49 pve kernel: Hardware name: AZW SER/SER, BIOS SER6proMax_P5C8V20 08/15/2023
  9. Oct 16 04:31:49 pve kernel: Workqueue: events igc_watchdog_task [igc]
  10. Oct 16 04:31:49 pve kernel: RIP: 0010:igc_rd32+0xa4/0xc0 [igc]
  11. Oct 16 04:31:49 pve kernel: Code: c7 c6 20 65 3f c0 e8 3b e1 96 d6 48 8b bb 28 ff ff ff e8 4f 99 4c d6 84 c0 74 b4 44 89 e6 48 c7 c7 48 65 3f c0 e8 7c 4e d0 d5 <0f> 0b eb a1 b8 ff ff ff ff 31 d2 31 f6 31 ff e9 f8 51 cb d6 0f 1f
  12. Oct 16 04:31:49 pve kernel: RSP: 0018:ffff9d2b40247db8 EFLAGS: 00010246
  13. Oct 16 04:31:49 pve kernel: RAX: 0000000000000000 RBX: ffff8fb40c1bac60 RCX: 0000000000000000
  14. Oct 16 04:31:49 pve kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
  15. Oct 16 04:31:49 pve kernel: RBP: ffff9d2b40247dd0 R08: 0000000000000000 R09: 0000000000000000
  16. Oct 16 04:31:49 pve kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 000000000000c030
  17. Oct 16 04:31:49 pve kernel: R13: ffff8fb40c1ba000 R14: 0000000000000000 R15: ffff8fb400e19d80
  18. Oct 16 04:31:49 pve kernel: FS: 0000000000000000(0000) GS:ffff8fbb39c40000(0000) knlGS:0000000000000000
  19. Oct 16 04:31:49 pve kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
  20. Oct 16 04:31:49 pve kernel: CR2: 00007fad17bd0420 CR3: 0000000054010000 CR4: 0000000000750ee0
  21. Oct 16 04:31:49 pve kernel: PKRU: 55555554
  22. Oct 16 04:31:49 pve kernel: Call Trace:
  23. Oct 16 04:31:49 pve kernel: <TASK>
  24. Oct 16 04:31:49 pve kernel: ? show_regs+0x6d/0x80
  25. Oct 16 04:31:49 pve kernel: ? __warn+0x89/0x160
  26. Oct 16 04:31:49 pve kernel: ? igc_rd32+0xa4/0xc0 [igc]
  27. Oct 16 04:31:49 pve kernel: ? report_bug+0x17e/0x1b0
  28. Oct 16 04:31:49 pve kernel: ? handle_bug+0x46/0x90
  29. Oct 16 04:31:49 pve kernel: ? exc_invalid_op+0x18/0x80
  30. Oct 16 04:31:49 pve kernel: ? asm_exc_invalid_op+0x1b/0x20
  31. Oct 16 04:31:49 pve kernel: ? igc_rd32+0xa4/0xc0 [igc]
  32. Oct 16 04:31:49 pve kernel: ? igc_rd32+0xa4/0xc0 [igc]
  33. Oct 16 04:31:49 pve kernel: igc_update_stats+0xa5/0x750 [igc]
  34. Oct 16 04:31:49 pve kernel: igc_watchdog_task+0xf7/0x570 [igc]
  35. Oct 16 04:31:49 pve kernel: process_one_work+0x225/0x430
  36. Oct 16 04:31:49 pve kernel: worker_thread+0x50/0x3e0
  37. Oct 16 04:31:49 pve kernel: ? __pfx_worker_thread+0x10/0x10
  38. Oct 16 04:31:49 pve kernel: kthread+0xe9/0x110
  39. Oct 16 04:31:49 pve kernel: ? __pfx_kthread+0x10/0x10
  40. Oct 16 04:31:49 pve kernel: ret_from_fork+0x2c/0x50
  41. Oct 16 04:31:49 pve kernel: </TASK>
  42. Oct 16 04:31:49 pve kernel: ---[ end trace 0000000000000000 ]---
Copy the Code


If you Google " igc: Failed to read reg 0xc030", you'll get many others with similar experiences.

Intel hardware is revision 3:
  1. 01:00.0 Ethernet controller: Intel Corporation Ethernet Controller I225-V (rev 03)
Copy the Code


In the end, I couldn't trust the onboard Intel Nic so I purchased a usbc 2.5GB ethernet adapter (with a common realtek chip) and it's been perfectly fine.

I originally had the Realtek and Intel nics in a bond but latencies and IO waits went high before the Intel was about to bomb out so now the Intel is disabled completely.
Reply Support Not support

Use magic Report

You have to log in before you can reply Login | Sign up

Points Rules

Quick Reply To Top Return to the list