D-Link DIR-2150 A1 support

Flashing several D-Link devices indeed got more complicated with newer browser and or Linux kernels. It's true that maybe OEM firmware works better, but I have definitely also seen a degrade of success probability with the exact same file, after upgrading Linux.

We have factory encryption support ready (c.f. pull request), but still there needs to be a way of unbricking (or reverting to OEM) of course.

The last time it worked for me on Linux was using Wine Internet Explorer, Opening the recovery web interface, selecting the upload file, then rebooting the device to recovery mode again and only then clicking upload (without re-loading the recovery web interface, so the first HTTP request the recovery would see is the POST, not the weird stuff modern browsers send to servers in addition to the main url these days).
This had a chance of about 40% of working with devices like COVR-C1200... Later, it did not work for me at all in Linux, but on Windows using IE10 in quirks mode :joy:

Luckily, someone wrote a script in the meantime, that unfortunately was not accepted to be included in the official OpenWrt scripts/flashing folder, but it's on the wiki for COVR-P2500:

Users reported it also works great for the DIR-2600/1960/.. devices, so it should also for DIR-2150 :slightly_smiling_face:

Regarding your issues with Ethernet and/or wifi, could this be due to an accidentally overwritten mtk-eeprom partition? that would indeed be an issue (you might try a dump from a different DIR-2150, though the calibration would be off, degrading wifi).
I had also seen incomplete uploads via the recovery at some points, so that the firmware was only partially working and behaving strangely. Do you see any I/O errors etc. in dmesg?

Feel free to try reverting to OEM using the script mentioned above, and then flashing latest master (encrypted factory image from @Lucky1 from the post above, flashed the normal way via D-Link Web UI).

How is the WiFi performance and stability on dir-2150 and dir-882 compared to stock?

It seems dlink has abandoned both devices.

I test compile of current snapshot with PR for 2150 & 3040

So some great good news and some bad ones.

So none of of the images worked in 'recovery boot' - although the -recovery suffixed got close to the DIR-2150A1_V106B01_unencrypted_with_header - as it confirmed all headers OK

to check image type

Check image validation:
Image1 Header Magic Number --> OK
Image1 Header Checksum --> OK
Image1 Data Checksum --> OK

image is unencrypto kernel images
*********** len: 1355, s->dataSize: 1355

But at this point it stops - so still only 882 & 2660 firmware image files pass this test.

So then I've flashed this file via serial line over 'tftp' which now works - so I've restored to Dlink-2150 official firmware and it GUI.

Here comes the greatest news - the -factory.bin image file in your new test dir is now ACCEPTED by GUI firmware upgrade dialog - so the user can now flash 2150 router through the GUI without any need of recovery boot!

However now your recent snapshot build does suffer some WiFi problems on this device - I've tried to restore my relayd configuration - however the Wireless connection was always disconnected with some auth errors:

[  689.426790] phy1-sta0: authenticate with xx:xx:xx:xx:xx:xx
[  689.438166] phy1-sta0: send auth to xx:xx:xx:xx:xx:xx (try 1/3)
[  691.475999] phy1-sta0: send auth to xx:xx:xx:xx:xx:xx (try 2/3)
[  693.533145] phy1-sta0: send auth to xx:xx:xx:xx:xx:xx (try 3/3)
[  695.556010] phy1-sta0: authentication with xx:xx:xx:xx:xx:xx timed out

Later on reverting back to the previously working build 23.05.0-b76d880406e5 fully restored the functionality of wireless extender.

(And yeah - it's kind of ugly to restore luci-proto-relay when it's missing in the official builds - I'd vote to include those relay packages as default....)

So I may just assume something is currently broken with the wireless authentication in the recent snapshot build - not sure what - and unclear how can I diagnose what it could be,

However your -recovery build now allows users to go to the OpenWrt directly from GUI which is superb result - although then user may currently need to 'sysupgrade -F' back to your working release 23.05 for stable Wireless usage (-F is needed for this message:

upgrade: Device dlink,dir-2150-a1 not supported by this image Tue Feb 13 09:28:12 UTC 2024 upgrade: Supported devices: dlink,dir-1960-a1 Image check failed.

as likely your current snapshot identifies now itself correctly as 2150 - while the old build is using incorrect signature of 1960.

How is the WiFi performance and stability on dir-2150 and dir-882 compared to stock?
It seems dlink has abandoned both devices.

Speed is on pair at least to my measureable hw performance :wink:

The main important part is however the openwrt is actually way more stable on 5G part compared with stock on 882 dlink firmware. With Dlinks firmware it had always had some wierd issues on 5G - while with OpenWrt it's performance works well over many many speedtest runs :wink:

1 Like

something I think is buried way back in this thread
that you don't know that build really is just a DIR-1960-A1 public build
just to configure the radio's then sysupdate to the normal DIR-1960-A1 firmware
add the missing wireless driver and other software they want
this was just to allow people to use a current pubic version with out having to locally compile everything
it was a stop gap to test until he PR passed and it has it's own version

I'm not sure why but but the link to factory calibration
looks broken for these devices
I maybe wrong maybe some where in the back ground is was set
i just can't see where atm


Updated * wan led not auto assigned

I'm not sure why but but the link to factory calibration

So is it worth to retest updated snapshots for WiFi usage on 2150 ?
Was the 1960 also affected and now works ?

I'm running some couple weeks old snapshot on 882 and there the WiFi seems to be fine - but your referred patch looks like it's not affecting 882.

Also is there anything more I could test/check comment? (before I'll let go 2150 to its final destination, where any retesting would be much much more difficult....)

myself I would just be using the DIR-1960-A1 firmware and add the extra wifi driver
just so I can use the current public compiled software library
until the PR passes & it has it's own maybe V24

and it was only the NAND flash devices affected that use a common file

HI @frkca
how are you going with this PR ?