CWWK i5-1235U 6 port i226 report

[alaricljs]

Try nic to nic on the mini?

 

[diegoweb]

Try nic to nic on the mini?

How would I perform the test sending packets from 1 to another (via iperf3) ?

---EDIT
Ohhhh, I see....
After nic to nic I ran ethtool between those 2 ports.

root@proxmox:~# ethtool enp4s0
Settings for enp4s0:
        Supported ports: [  ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
                                2500baseT/Full
        Supported pause frame use: Symmetric
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
                                2500baseT/Full
        Advertised pause frame use: Symmetric
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Speed: 2500Mb/s
        Duplex: Full
        Auto-negotiation: on
        Port: Twisted Pair
        PHYAD: 0
        Transceiver: internal
        MDI-X: off (auto)
        Supports Wake-on: pumbg
        Wake-on: g
        Current message level: 0x00000007 (7)
                               drv probe link
        Link detected: yes

It's indeed 2.5GbE.
Now I need to solve why my Windows machine is not reaching 2.5GbE.

---EDIT2
By changing the cable to a cat5 patch cable (not even Cat5e) I was able to reach 2.5GbE. So probably my termination needs to improve. I will buy some Cat6 connectors.

root@proxmox:~# ethtool enp4s0
Settings for enp4s0:
        Supported ports: [  ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
                                2500baseT/Full
        Supported pause frame use: Symmetric
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
                                2500baseT/Full
        Advertised pause frame use: Symmetric
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Speed: 2500Mb/s
        Duplex: Full
        Auto-negotiation: on
        Port: Twisted Pair
        PHYAD: 0
        Transceiver: internal
        MDI-X: off (auto)
        Supports Wake-on: pumbg
        Wake-on: g
        Current message level: 0x00000007 (7)
                               drv probe link
        Link detected: yes

 

[diba]

Hi everybody,

i have an HUNSN RJ24. The Mainboard should be the same líke the ChangWang (see the attached photo). I have tried all patched Bios Files from fta, but no one works. When i am in the bios an try to open the advanced part, the system crashed. alt-ctrl-delete for reset works. With the Stock bios from ChangWang everthing works fine.

Is here somebody who have idea why it doesn't work ?

Best regards

Dirk

 

[diba]

Strange, it's working perfectly for me. Perhaps try restoring defaults in the BIOS, or alternatively clearing the CMOS with the button on the front?

Hi i have the same problem. Load default settings in the bios or pushing the cmos clear button doesn't help

 

[agh1701]

Has any noticed that the CWWK website has changed? Bios updates do not seem to be available anymore.

 

[alaricljs]

A chat w/ cwwk.net a week or so ago got me this site: 畅网官方网盘

 

[agh1701]

Thanks, Found the bios here:
畅网官方网盘

 

[pawasi]

Anyone have any idea why the keyboard isn't working after the bios update? Keyboard is recognized since ctl alt delete restarts it, but I can't navigate the bios at all. Flash back to stock and it works fine again.

I'm struggling with the same issue. Have you been able to solve this problem?

 

[pawasi]

Strange, it's working perfectly for me. Perhaps try restoring defaults in the BIOS, or alternatively clearing the CMOS with the button on the front?

Can you upload unlocked bios which you builded before @Conjurer tweaks? Im wondering if that might be the problem because then I flashed your unlocked bios and everything was fine, today I tried update your bios with @Conjurer updates and now I have keyboard problem.
Thanks
Edit: Ok, never mind I found old file ( was quoted in#5 post). I will try flash modified file from March and see if keyboard problem still be there
Edit2: I flashed February bios with modified file from #5 post, and my keyboard started working, but next I prepared new usb flash with the newly modified bios (HWP On - 02/07/2023: recommended) and keyboard after flash also working fine. I put usb with bios to usb3 (blue) port and keyboard to red port.

 

[diba]

Edit: Ok, never mind I found old file ( was quoted in#5 post). I will try flash modified file from March and see if keyboard problem still be there
Edit2: I flashed February bios with modified file from #5 post, and my keyboard started working, but next I prepared new usb flash with the newly modified bios (HWP On - 02/07/2023: recommended) and keyboard after flash also working fine. I put usb with bios to usb3 (blue) port and keyboard to red port.

Thanks for this post. with the bios from #5 post everything works fine for me. In the bios i have no problems with my keyboard. But with modified bios (HWP On - 02/07/2023: recommended) i have the same promblems with the keyboard like before. With the modified bios (HWP On - 06/08/2023) i have the same problem

@pawasi. How do you prepare the new usb flash ?

 

[pawasi]

How do you prepare the new usb flash ?[/B]

Normally with Rufus, pasted new changwang.bin file deleted old one and changed filename to proper. But second flash I executed on another usb flash drive (I don't know if it can have any influence)

 

[diba]

Normally with Rufus, pasted new changwang.bin file deleted old one and changed filename to proper. But second flash I executed on another usb flash drive (I don't know if it can have any influence)

Ok i used the same way. But only the modified Bios from #5 post works.

@pawasi did you make any settings in the bios between flashing the bios from #5 post to the modified HWP On - 02/07/2023: recommended ?

 

[Stevoni]

Thanks for this post. with the bios from #5 post everything works fine for me. In the bios i have no problems with my keyboard. But with modified bios (HWP On - 02/07/2023: recommended) i have the same promblems with the keyboard like before. With the modified bios (HWP On - 06/08/2023) i have the same problem

@pawasi. How do you prepare the new usb flash ?

Anyone have any idea why the keyboard isn't working after the bios update? Keyboard is recognized since ctl alt delete restarts it, but I can't navigate the bios at all. Flash back to stock and it works fine again.

@pawasi @NodeRunner222 I had the same problem but re-read the documentation (for the 20th time) and realized we must reinstall the drive first. The BIOS is probably crashing trying to load the NVMe settings on that page.

In this documentation (畅网 12代酷睿U系列迷你主机BIOS更新), I didn't understand that I couldn't navigate to the documentation until the drive was installed, but it made a ton of sense when I followed the steps to completion:

12. After re-entering the system, you can see the logo description of Changwang micro-control.
Press the power button once to shut down. Reinstall the hard drive and reboot.

 

[BugVito]

@pawasi @NodeRunner222 I had the same problem but re-read the documentation (for the 20th time) and realized we must reinstall the drive first. The BIOS is probably crashing trying to load the NVMe settings on that page.

In this documentation (畅网 12代酷睿U系列迷你主机BIOS更新), I didn't understand that I couldn't navigate to the documentation until the drive was installed, but it made a ton of sense when I followed the steps to completion:

That's an interesting take on a potential cause. However, if I recall properly the "stock" firmware does not exhibit this issue. I would assume that the step to reinstall the "hard drive" is simply to return to normal operation (able to boot the OS) since the hard drive must be removed during the BIOS update due to how the update script relies on an absolute path, if I recall properly.

I unfortunately don't have the ability to test currently, but I assume that you did. That leaves me with doubt regarding the quality of the BIOS if that's as intended; a BIOS should simply be able to cleanly report that no drives are detected. If that's not as intended however, if the stock BIOS does not exhibit this behavior; what else could have been disturbed in the "patching" process?

 

[beisser]

small anecdote from me. i actually did the latest bios update with my nvme drive in place (i wanted to see what happens).
worked like a charm.

 

[pawasi]

Ok i used the same way. But only the modified Bios from #5 post works.

@pawasi did you make any settings in the bios between flashing the bios from #5 post to the modified HWP On - 02/07/2023: recommended ?

No I flashed first bios from 5 post, next launched bios to check if keyboard is working and next, on another usb flash updated latest modified bios. Before flash bios from 5th post I cleared bios by CLR bios button. Also I didn't remove nvme drive, only boot usb flash from f11.

 

[m3e]

I've prepared my ventoy usb, and did some extensive testing. I've crated number of custom images:
1) 02.07 HWP off (7.68 MB file on MEGA - based on 02.07 installer)
2) 02.07 HWP on (old version - 7.68 MB file on MEGA - based on 02.07 installer)
3) 02.07 HWP on (new version - 16 MB file on MEGA - based on 02.07 installer)
4) 06.08 HWP on (16 MB file on MEGA - based on 02.07 installer)
5) 02.07 HWP on (new version - but based on the 06.08 installer)
6) 06.08 HWP on (based on the 06.08 installer)

I have version with Pentium 8505 and with CW-MBX-AD12-0 sticker on the motherboard. I do not believe that m.2 drive has anything to do with the process, but I've removed it anyway during testing. I've tried various upgrade paths and this is what I've found:
1) Only image 1 and 2 works correctly on my system
2) Previous installed FW does not matter (with and without CMOS CLR) for the new FW installation
3) Freeze on menu change does not always happen on the first screen. Sometimes it happens on n-th, but I was never able to do a full cycle between the menu screens, when I had broken bios
4) Working images have different "Main" screen in the BIOS. Clock and date is not immediately visible, and you need to scroll to the bottom of the screen to see them. Broken BIOS has the same "Main" screen as the stock one.
5) Original BIOS always works (regardless of version)

Judging by the size of the compressed BIN files maybe it's a padding issue, but it's being triggered only on some of the boards?

For the time being I'll go with the old version of 02.07 HWP on


EDIT: New versions of the modded BIOS are working fine when SSD is installed!

 

[Stevoni]

That's an interesting take on a potential cause. However, if I recall properly the "stock" firmware does not exhibit this issue. I would assume that the step to reinstall the "hard drive" is simply to return to normal operation (able to boot the OS) since the hard drive must be removed during the BIOS update due to how the update script relies on an absolute path, if I recall properly.

I unfortunately don't have the ability to test currently, but I assume that you did. That leaves me with doubt regarding the quality of the BIOS if that's as intended; a BIOS should simply be able to cleanly report that no drives are detected. If that's not as intended however, if the stock BIOS does not exhibit this behavior; what else could have been disturbed in the "patching" process?

I ordered my 6 port i5-1235U from Amazon this weekend (https://www.amazon.com/dp/B0C1FJKN19) and it arrived today already running a BIOS from April: AD12R20230423

I tried two different flash drives, 32 GB and 16 GB, and after formatting the sticks with the original ISO I could navigate to Advanced without any issues. If I added any of the custom versions the BIOS would freeze for me from either direction, going right from Main or left from Chipset. I assumed it was something to do with the NVME settings since that was the only variable that changed since I manually powered off the device (although I didn't disconnect the power) when unplugging the thumb stick.

Also, I noticed moving keyboard or thumbstick would cause the system to essentially freeze and, for the keyboard, not taking any more input when moved. I gave up it unfreezing after letting it idle for a few minutes the first time so I would power it off manually between installation attempts.

I did try clearing CMOS for one run through with all the versions but with the same results when navigating in the BIOS.

If that's not as intended however, if the stock BIOS does not exhibit this behavior; what else could have been disturbed in the "patching" process?

I noticed the latest firmware automatically reset and a few times I flashed it multiple times as I missed powering off on the second reboot. Not that it seemed to make a difference from the previous results.

Unfortunately, after the several hours of frustration, I've got it flashed, settings updated, and already starting building VMs so I won't be able to assist further troubleshooting for a little bit.

 

[m3e]

I noticed the latest firmware automatically reset and a few times I flashed it multiple times as I missed powering off on the second reboot. Not that it seemed to make a difference from the previous results.

Unfortunately, after the several hours of frustration, I've got it flashed, settings updated, and already starting building VMs so I won't be able to assist further troubleshooting for a little bit.

Are you sure that you have installed the unlocked bios? It looks entirely different than the stock.

It's not the FW that does the reboot but the install scripts, and indeed with the stock installer for 06.08 FW it does reboot at the end. But the new installer looks for different bin file than the old one, so if you used the 02.07 name when you put it to the folder you'd still write the stock bios.

 

[Stevoni]

Are you sure that you have installed the unlocked bios? It looks entirely different than the stock.

It's not the FW that does the reboot but the install scripts, and indeed with the stock installer for 06.08 FW it does reboot at the end. But the new installer looks for different bin file than the old one, so if you used the 02.07 name when you put it to the folder you'd still write the stock bios.

How does it look different? I had the advanced options listed in #277 after following the instructions by downloading the ISO from the new CWWK website, the BIN files from Mega, formatting a thumb drive, and renaming the BIN file accordingly.