I haven’t opened my switch, so I don’t have photos, but I think we should try to get both officially supported by OpenWrt together. The only needed change from the `A1`/`v1` is the differing POE configuration.
I agree. And if there is a way to get our PoE working without "unsupported" options that would be ideal for long term support.
I will say, getting the switch open did not seem difficult or dangerous: three screws and a system of gotten metal is all that kept mine in place with no ribbon cables or adhesives to be found. Not hard worth a standard Phillips bit used.
I looked at the site for uploading switch pictures and I didn't see at first glance where to put them but will say mine looked practically identical. I don't have a great camera given the budget android phone I use. 
That said, all of the text files I have dumped don't require any resolution beyond a terminal. 
There are photos of two different versions of the GS1900-10HP at https://svanheule.net/switches/gs1900-10hp. And the wikidevi page has images of what the svanheule.net page indicates is V1 with pretty comprehensive details regarding the chips used in that version.
Ok. I was maybe able to figure out how to post my information to the website. Looking at recent file changes it looks like you have some experience posting there so if anyone wants to let me know what to correct (or has their own account to make corrections themselves) I would much appreciate any advice.
I tried to only post relevant text documents and still have some more to add (e.g. meminfo, ifconfig, etc) but would rather get feedback here (or from the mods on the website) to let me know if I am doing something wrong in my uploads.
Edit: I previously looked into svanheule.net but was not able to figure out how to easily upload my dumps/pictures let alone categorize them. I think a wiki makes a little more sense for an initial upload. 
For any struggling individuals like me which has passworded SKS8300-8X - password is admin
Summary
###########################################
######## Uboot for Flash Main Menu ########
###########################################
[1] Enable Network On
[2] Config Ethernet Environment Variables
[3] Ping Host IP Address
[4] Running the System Kernel image
[5] Burn the production firmware Bin
[6] Set Serail Number&System CPU MAC&Software License
[7] Set Serail Number&System CPU MAC
[8] Perform Reset of the Uboot
[9] Show Uboot Saved Info
Enter your selection:
Enter the password:(1-32 characters)
********************
Please wait for PHY init-time ...
Password:***** <---- admin
Boot# nopw
2772 bytes written, 0 bytes skipped
2772 bytes written, 0 bytes skipped
The boot password has been removed successfully!
Boot#
Boot# debug_unish_env
RTL9300#
It could be found in mtd1 (don't know how you could get there). Then do strings <dump file>:
...
[bootpassword]
**21232f297a57a5a743894a0e4a801fc3
...
This value is a SHA-1 hash of password. Copy that and go to any unhashing service:
That's your password. Than you might run nopw to remove this password
P.S. I definitely saw this a year ago, but I can't find it now. So this message is a product of many hours of struggling and digging through this thread. Thanks anyone for hints
1 Like
Looks like I misunderstood which model you were looking at GS1900-8HP vs GS1900-10HP! Looks like you missed getting the Brand/Model for the RAM and Flash memory. I can see that the RAM is Winbond, but the image isn’t high enough resolution to determine the model. The flash looks like it could be Macronix. Interesting that this model appears almost identical to the GS1900-10HP with the SFP cages not populated. The V1.2 model from my entry is significantly different in appearance.
Let's continue SKS8300-8X obvious tips - DO NOT RUN saveenv INSIDE U-BOOT!!! In my case it lead to erasing one block and subsequent hangup. But I was lucky, it just disabled first four SFP ports (completely, in bootloader and linux)
But if you did...
If you still have access to linux, you can go to your switch .dts, remove read-only property from u-boot partition, flash this new firmware using sysupgrade, and then try to write correct uboot image to mtd0. BUT YOU MUST BE EXTRA CAREFUL!!!
1 Like
Some kind soul helped with formatting over on the wiki page I created. I have used their formatting to add in the additional information that the OpenWRT new device page calls for.
@RaylynnKnight If you can point out which chip on the board is the memory chip I can take a clearer picture. Unfortunately the best camera I have access to is in my phone and though it is not the best it does the best it can with the poor conditions I give it to work with. Poor picture quality is very much on me.
The chip just to the right of the SOC which has the heatsink is the RAM. It appears to be labeled “winbond” in your image which would be the Brand. The Model should be the line just below that. The flash chip should be the smaller chip just to the right of that.
I wonder if the power circuitry is the same between -8HP and -10HP in their B1 revisions? Because nominally, the 10HP has a 7 W higher PoE budget for an identical number of copper ports.
A phone camera can often take more than adequate close up photos of chips etc. if you give them enough light. 
1 Like
Hi all, first post here. I would like to volunteer as a guinea pig.
I bought an Xikestor SKS8310-8X in the hopes that it would be similar to the SKS8300-8X and I could at least boot the kernel, but the bootloader is different than what is in the git commit for 8300 and the password is different also.
U-Boot 2011.12.(3.6.11.55242) (Dec 05 2025 - 14:41:20)
Board: RTL9300 CPU:800MHz LX:175MHz DDR:400MHz
DRAM: 512 MB
SPI-F: MXIC/C22019/MMIO32-4/ModeC 1x32 MB (plr_flash_info @ 83fc1f68)
Loading(93) 65536B env. variables from offset 0x1c0000
boardId_init40
Net: Net Initialization Skipped
No ethernet found.
Press A to stop autoboot:
1: Run application
2: Set factory mac-address
3: Set product serial number
4: Download bootrom
5: Download host
6: OEM config
7: Set factory IP
#: Restore admin user default password
<Choice> :
Upon using options 4 and 5 it proceeds to download an image from TFTP, but it only downloads about 512k and errors out with invalid image message. No SFP setup was necessary, the bootloader detected the 10G SFP in port 1 automatically.
The boot log of the factory image:
Booting image from partition ... 0
Booting kernel from Legacy Image at 81000000 ...
Image Name: RTK_SDK
Created: 2025-12-05 14:59:53 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 12423553 Bytes = 11.8 MB
Load Address: 80000000
Entry Point: 803873e0
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Starting kernel ...
init started: BusyBox v1.34.1 (2025.11.19-09:25+0000) multi-call binary
Starting pid 33, console : start
RTCORE LKM Insert...
RTCORE Driver Module Initialize (LKM)
IOAL init
Log init
Hardware-profile probe (RTL9303_8XGE_V1)
Hardware-profile init
Intr Probe (unit 0)
GPIO probe (unit 0): (found)
GPIO Init
SPI init (unit 0)
I2C probe (unit 0)
I2C init (unit 0)
RTL8231 probe (unit 0): (found)
RTL8231 init (unit 0)
TC probe (unit 0): (found)
TC init (unit 0)
TC util init (isr)
SIOCSIFADDR: No such device
Starting pid 73, console /dev/ttyS0: start
Loading ...
RJGT102_CheckVersion:32 30 84 71
1RJGT102_SecurityCertificate iRet=0x0
+i1T1...
Poe firmware process4(0xffffffff chip:0 dev:2).
Poe firmware load(0xfffffc17)...done.
.........Done
login:
EDIT: Correct instructions found (see below).
I've been running a HP JG926A for weeks without issue and suddenly today, connections seem to be limited at 500M speed instead of 1GB across all links. Link speed is reported as 1GB.
Has anyone encountered this issue before? Reboot did not change anything. Nothing unusual in logs and no configuration changes recently. POE delivered is between 40-50W which is well within spec and 8 ports on the switch are unused at the moment.
The SKS8310-8X is supported too in OpenWrt. It is quite different to the SKS8300-8X but easier/better. Have that one on my desk too.
2 Likes
Thanks! For some reason that commit was not in my search results. It worked!
Ah yes. Bug in latest main and 25.10-rc. The code path for traffic limits was finally activated, but the default settings are wrong.
3 Likes
Thank you for sharing this...can confirm this seems to be the fix. Do you need me to submit a PR or is that already in progress?
https://github.com/openwrt/openwrt/pull/21900 for 25.12, and it’s already fixed in main.
3 Likes
Hello,
on my Realtek 8380M based TP-Link switch I can manipulate the VLAN priority for interfaces and the queueing, for example:
T1500G-8T#sh qos queue interface gigabitEthernet 1/0/1
Gi1/0/1----LAG: N/A
Queue Schedule Mode Weight
----- ---------- -----
TC0 WRR 1
TC1 WRR 1
TC2 WRR 1
TC3 WRR 4
TC4 WRR 1
TC5 WRR 1
TC6 Strict N/A
TC7 WRR 1
Is it possible to achieve this also with OpenWRT?
I have a HDMI over IP extender and would like to prioritize the VLAN over other traffic in order to avoid image distortions or loss of signal if there is higher load on the trunk.
I have a PR open for this. Please have a try if you find some time.
1 Like