Jump to content

AurelianRQ

Members
  • Posts

    6
  • Joined

  • Last visited

Posts posted by AurelianRQ

  1. On 11/2/2020 at 11:58 AM, gprovost said:

     

    @wurmfood and @357up it could be an issue with the wire harness. Can you do more try by swapping the cable between the bay slots and sata ports in order to narrow down the problem to the wire harness. If it's the case then you can contact us to support@kobol.io and we will help you from there.

     

    @AurelianRQ Regarding the issue for 2.5GbE port that doesn't perform properly when used in 1000Mb mode, unfortunately there is no fix that can be done by software. But it's actually pretty easy to fix on the board itself, it only requires to solder one wire between 2 points. Our mistake is that we didn't connect center tap of the 2.5Gb MAGJACK to 2.5V power rail (connected to ground instead) in order to provide common mode for MDI signals which is required for 1000Mb mode somehow. We will post a PCN bulletin to explain better this limitation and how to fix it for people who are up for a bit of soldering.

     

    @aegiap Unfortunately your link aggregation is going to be impacted to the issue mentioned above. The 2.5GbE doesn't perform properly in 1000Mb mode.

     

     

    T

    On 11/2/2020 at 11:58 AM, gprovost said:

    Cool, well I can do that I guess if that does not void the warranty in this case, Honestly to get a 300 E switch to manage 2.5 or 100 E adapters that I don't even know they work, I prefer to fix it the easy way if possible. Thanks and I guess waiting for your details. 

     

  2. 14 minutes ago, AurelianRQ said:

    Could we please know what is the design mistake and at least that means that we cannot use the second port ? so we have a 2.5G port and if we want to use it as 1Gbps it fails I assume, is there any fix for this or not ? as I'm currently using this as 1Gbps connection and it seems that every few days I get a kernel crash or something as the system error led gets blinking and I do have to keep on force restart it from the button to be able to have access to it. 

     

    The funny part is that I have both connections on but once it fails I cannot reach to it from any network so completely dead .

    Just did a test and while on eth0 I get : 

     

    [ ID] Interval           Transfer     Bitrate         Retr

    [  5]   0.00-30.00  sec  3.18 GBytes   912 Mbits/sec  876             sender

    [  5]   0.00-30.00  sec  3.18 GBytes   911 Mbits/sec                  receiver 

     

    which is normal, same test on eth1 I get : 

    [ ID] Interval           Transfer     Bitrate         Retr

    [  5]   0.00-30.00  sec   403 MBytes   113 Mbits/sec  5610             sender

    [  5]   0.00-30.00  sec   402 MBytes   113 Mbits/sec                  receiver

     

    And it seems between eth1 of both Helios 64 I get : 

     

    [ ID] Interval           Transfer     Bitrate         Retr

    [  5]   0.00-30.00  sec   348 MBytes  97.3 Mbits/sec  5817             sender

    [  5]   0.00-30.00  sec   348 MBytes  97.2 Mbits/sec                  receiver

     

    which Is a total mess and I guess I cannot use this connection. 

  3. On 10/19/2020 at 9:47 AM, gprovost said:

     

    We will do an announcement soon but we realized we made a design mistake on the Helios64 2.5GbE port (LAN2 | eth1) which makes it not perform well in 1000Mb/s mode, however no impact in 2500baseT mode.

     

    Regarding your iperf test, seems a bit funny. You sure your routing table is correct for traffic to go really to the expected interface since you are on the same subnet.

    Can you do the same tests, but for each test disconnect the cable of the interface you are not testing.... or at least use different subnet.

    Also can you check interface speed with ethtool (ethtool eth0 and ethtool eth1).

    Could we please know what is the design mistake and at least that means that we cannot use the second port ? so we have a 2.5G port and if we want to use it as 1Gbps it fails I assume, is there any fix for this or not ? as I'm currently using this as 1Gbps connection and it seems that every few days I get a kernel crash or something as the system error led gets blinking and I do have to keep on force restart it from the button to be able to have access to it. 

     

    The funny part is that I have both connections on but once it fails I cannot reach to it from any network so completely dead .

  4. Apparently Kobol team recommended to stay off the new kernels and to use their recommended ones. The problem is that every few days I get the Red System error led flashing and the box is not reachable so I have to force restart it so I can have access to it again 

     

    so far I get this : 

    while seeing the dmessages I get : 

    [ 0.017590] ARM_SMCCC_ARCH_WORKAROUND_1 missing from firmware
    [ 2.656869] Serial: AMBA driver
    [ 2.658516] cacheinfo: Unable to detect cache hierarchy for CPU 0
    [ 2.670600] loop: module loaded
    [ 3.034951] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
    [ 3.040546] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
    [ 3.040753] pci 0000:01:00.0: [197b:0585] type 00 class 0x010601
    [ 3.040874] pci 0000:01:00.0: reg 0x10: initial BAR value 0x00000000 invalid
    [ 3.040882] pci 0000:01:00.0: reg 0x10: [io size 0x0080]
    [ 3.040917] pci 0000:01:00.0: reg 0x14: initial BAR value 0x00000000 invalid
    [ 3.040925] pci 0000:01:00.0: reg 0x14: [io size 0x0080]
    [ 3.040959] pci 0000:01:00.0: reg 0x18: initial BAR value 0x00000000 invalid
    [ 3.040966] pci 0000:01:00.0: reg 0x18: [io size 0x0080]
    [ 3.041000] pci 0000:01:00.0: reg 0x1c: initial BAR value 0x00000000 invalid
    [ 3.041007] pci 0000:01:00.0: reg 0x1c: [io size 0x0080]
    [ 3.041041] pci 0000:01:00.0: reg 0x20: initial BAR value 0x00000000 invalid
    [ 3.041048] pci 0000:01:00.0: reg 0x20: [io size 0x0080]
    [ 3.041083] pci 0000:01:00.0: reg 0x24: [mem 0x00000000-0x00001fff]
    [ 3.041118] pci 0000:01:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
    [ 3.041156] pci 0000:01:00.0: Max Payload Size set to 256 (was 128, max 512
    [ 3.047177] pci_bus 0000:01: busn_res: [bus 01-1f] end is updated to 01
    [ 3.047208] pci 0000:00:00.0: BAR 14: assigned [mem 0xfa000000-0xfa0fffff]
    [ 3.047232] pci 0000:01:00.0: BAR 6: assigned [mem 0xfa000000-0xfa00ffff pref]
    [ 3.047242] pci 0000:01:00.0: BAR 5: assigned [mem 0xfa010000-0xfa011fff]
    [ 3.047262] pci 0000:01:00.0: BAR 0: no space for [io size 0x0080]
    [ 3.047270] pci 0000:01:00.0: BAR 0: failed to assign [io size 0x0080]
    [ 3.047278] pci 0000:01:00.0: BAR 1: no space for [io size 0x0080]
    [ 3.047285] pci 0000:01:00.0: BAR 1: failed to assign [io size 0x0080]
    [ 3.047292] pci 0000:01:00.0: BAR 2: no space for [io size 0x0080]
    [ 3.047299] pci 0000:01:00.0: BAR 2: failed to assign [io size 0x0080]
    [ 3.047306] pci 0000:01:00.0: BAR 3: no space for [io size 0x0080]
    [ 3.047313] pci 0000:01:00.0: BAR 3: failed to assign [io size 0x0080]
    [ 3.047320] pci 0000:01:00.0: BAR 4: no space for [io size 0x0080]
    [ 3.047327] pci 0000:01:00.0: BAR 4: failed to assign [io size 0x0080]
    [ 3.047338] pci 0000:00:00.0: PCI bridge to [bus 01]
    [ 9.989921] input: adc-keys as /devices/platform/adc-keys/input/input1
    [ 10.059999] rk_gmac-dwmac fe300000.ethernet: IRQ eth_wake_irq not found
    [ 10.060011] rk_gmac-dwmac fe300000.ethernet: IRQ eth_lpi not found
    [ 10.060164] rk_gmac-dwmac fe300000.ethernet: PTP uses main clock
    [ 10.060327] rk_gmac-dwmac fe300000.ethernet: clock input or output? (input).
    [ 10.060339] rk_gmac-dwmac fe300000.ethernet: TX delay(0x28).
    [ 10.060349] rk_gmac-dwmac fe300000.ethernet: RX delay(0x20).
    [ 10.060364] rk_gmac-dwmac fe300000.ethernet: integrated PHY? (no).
    [ 10.060450] rk_gmac-dwmac fe300000.ethernet: cannot get clock clk_mac_speed
    [ 10.060458] rk_gmac-dwmac fe300000.ethernet: clock input from PHY
    [ 10.065534] rk_gmac-dwmac fe300000.ethernet: init for RGMII

    11.571344] dw-apb-uart ff1a0000.serial: forbid DMA for kernel console
    [ 13.327166] usb 2-1.4: reset SuperSpeed Gen 1 USB device number 3 using xhci-hcd
    [ 13.730681] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: user_xattr,acl
    [ 13.875498] zram: Added device: zram0
    [ 13.876283] zram: Added device: zram1
    [ 13.876953] zram: Added device: zram2
    [ 13.916911] zram1: detected capacity change from 0 to 1992331264
    [ 14.049513] cdn-dp fec00000.dp: Direct firmware load for rockchip/dptx.bin failed with error -2
    [ 14.049764] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes
    [ 14.977397] Adding 1945632k swap on /dev/zram1. Priority:5 extents:1 across:1945632k SSFS
    [ 15.109777] zram0: detected capacity change from 0 to 52428800
    [ 16.065460] cdn-dp fec00000.dp: Direct firmware load for rockchip/dptx.bin failed with error -2
    [ 17.158086] systemd[1]: Started Armbian ZRAM config.
    [ 17.163966] systemd[1]: Starting Armbian memory supported logging...
    [ 17.224816] EXT4-fs (zram0): mounted filesystem without journal. Opts: discard
    [ 17.224855] ext4 filesystem being mounted at /var/log supports timestamps until 2038 (0x7fffffff)
    [ 19.275437] systemd[1]: Started Armbian memory supported logging.
    [ 19.280814] systemd[1]: Starting Journal Service...
    [ 19.430698] systemd[1]: Started Journal Service.
    [ 19.478887] systemd-journald[727]: Received request to flush runtime journal from PID 1
    [ 19.603930] random: crng init done
    [ 19.603939] random: 7 urandom warning(s) missed due to ratelimiting
    [ 19.852787] cfg80211: Loading compiled-in X.509 certificates for regulatory database
    [ 19.857488] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
    [ 19.858097] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
    [ 19.858111] cfg80211: failed to load regulatory.db
    [ 19.928741] rk_gmac-dwmac fe300000.ethernet eth0: PHY [stmmac-0:00] driver [RTL8211F Gigabit Ethernet] (irq=POLL)
    [ 19.934085] rk_gmac-dwmac fe300000.ethernet eth0: No Safety Features support found
    [ 19.934109] rk_gmac-dwmac fe300000.ethernet eth0: PTP not supported by HW
    [ 19.934122] rk_gmac-dwmac fe300000.ethernet eth0: configuring for phy/rgmii link mode
    [ 20.112591] r8152 2-1.4:1.0 eth1: carrier on
    [ 20.193411] cdn-dp fec00000.dp: Direct firmware load for rockchip/dptx.bin failed with error -2
    [ 21.368123] NFSD: Using UMH upcall client tracking operations.
    [ 21.368136] NFSD: starting 90-second grace period (net f00000a1)
    [ 13.462038] r8152 2-1.4:1.0 (unnamed net_device) (uninitialized): netif_napi_add() called with weight 256


    and many many others. I don't see network activity as well on the front panel, is that pending as well ? It would be nice to have something functional that does not crash . Is this a hardware issue or just software issue ? 

    Running your image 5.8.14-rockchip64 #20.08.10 SMP PREEMPT Tue Oct 13 16:58:01 CEST 2020 aarch64 GNU/Linux

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines