double O seven reporting for duty....

just to make things going on by reporting some issues.....
three support requests :

##1

it's an old one i know but im now running experciences on DG834GT from Netgear, it's running well attitude adjustment, with filename :
http://archive.openwrt.org/attitude_adj … fs-cfe.bin
booting well...

doing the same thing to have a faster openwrt (att/adj is running slow enough) with the beloved backfire :
http://archive.openwrt.org/backfire/10. … fs-cfe.bin

freeezing on
VFS: Cannot open root device "mtdblock2" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

entire log for BB :
https://paste.fedoraproject.org/paste/Q … Rh4G1Q/raw

##2

two other things :
for people like me who prefer use our beloved openwrt version instead of the latest for personal and legitimate reasons (yes, it's legitimated to use old windows, old osx or  old linuxes too) is it possible to differentiate generated images with the release/version?

as example, for this model :
http://archive.openwrt.org/barrier_brea … fs-cfe.bin
http://archive.openwrt.org/chaos_calmer … fs-cfe.bin

the F5D7633 (example to illustrate the problem) has two very similar filenames and when you see them... you just cannot know on which openwrt version the file is. And it's a problem (yes, users are here for reporting that,   )

##3

and the latest (ok, that makes three) issue :
how to make wget supporting ssl ?
i absolutely need wget with ssl support to send data to an hotspot, i have
wget: not an http or ftp url

how could i solve that?

thank you very much for reading (and replying )

###3
You can install full-wget package _or_ build own image including busybox-wget with SSL.

1.  This device has 16 MB RAM so it is really limited in how much it can do and how late a kernel it can hold.  Considering there are know security vulnerabilities in old kernels and other packages, such a device and software should not be used online.

But the main problem with this boot is it did not know how to partition the flash and mount the rootfs.  I think those old versions required the flash partitions to be specified on the command line fed to the kernel from the bootloader (thus stored in bootloader config environment).

(Last edited by mk24 on 23 Apr 2018, 22:17)

thank you mk.
Related to §1, maybe you're right, maybe special usages made these old device running better with old owrt release instead of old OEM firmwares.. but it's another subject, and as online it could be useful as offline too.

regarding to §2, i think you're right.
i'm not a programmer, a developper or any coder professional, even not a passionate of programmation. The thing is att/adj is generating a working image for that device, instead of the backfire, without any change, doesnt launch, even when trying the official generated on downloads.openwrt.org servers.

there is why i'm wondering : how could be possible to update the backfire or let a file to explain how to fix it? we can't let this unbelievable bug stay here, available to so much people whom want to try backfire on their netgear for a little tiny hotspot as example...

thank you again for answers and how-to fix it

I'm thinking the problem may be in your bootloader config not passing a complete command line to the kernel-- not a problem in the build itself.  But I know very little about CFE / Broadcom bootup.  You could search for a post of the bootlog of a successful bootup of this model, and pay attention to the kernel command line and the MTD partitioning.

(Last edited by mk24 on 24 Apr 2018, 01:35)