Introduced new section "Special views".
Take a look at: http://wiki.openwrt.org/toh/views/start

Comments please!

Yes, can you pad the white space 1 character to each side?

to me it does.

Would it be an idea to distinguish between Router and DSL Router?   

I'm adding a Fritz Box that has DSL   Or should I use Modem for tthis? 

The other fritzboxes have some inconsistencies

Router and WiFi Router is used  eventhough all have Wifi... 
When i'm looking specific for DSL i cant filter it  thats why i ask.

Pretty good, I think!

Yes, the idea was to use Modem for this. I was updating some data entries yesterday, and I perhaps Modem is not the perfect term.

Already tried that myself, but doesn't work.

Edit: Works now with a trick

(Last edited by tmo26 on 13 Sep 2015, 22:29)

What about making a selection box?

Router, WiFi, ADSL, ADSL2, ADSL2+, VDSL, G3, Fiber, DECT, etc,

Would that mess up existing entries?

BTW Is DSL still Modem?  Modulation / demodulation   Or is it real routing?

(Last edited by frietpan on 13 Sep 2015, 23:07)

The current _devicetype dropdown

¿, WiFi Router, Router, Travel Router, Travel Router - Battery powered, Single Board Computer, Modem, NAS, other

can be expanded, without messing up anything.

http://wiki.openwrt.org/toh/views/toh_admin_available - Great!
http://wiki.openwrt.org/toh/views/start - Great!

Getting this message when I click submit (2x) but the post goes through??

Sorry! The page could not be loaded.

Unable to send e-mail.
Please contact the forum administrator with the following error message reported by the SMTP server: "535 5.7.8 Error: authentication failed: authentication failure "

What I find missing from all these is the *reason* I would choose any of these. As a newcomer, I'm not sure I would understand what "ToH minimal, supported devices only" actually means *to me*. If had this text for the link, "Supported devices, current and older releases", that would help.

And the most helpful ToH for a newcomer would list "Devices supported by current stable release" (perhaps all devices, minimal info, filtered by 15.05).

(Last edited by richbhanover on 14 Sep 2015, 02:50)

@tmo26 - thanks for updating the top page of the wiki to remove the "Under Construction" banner.

Thanks, too for decreasing the length of the top-note on the ToH. It's still too long though, because the table is barely visible in some screens (see http://picpaste.com/ToH-partial_screen_1.png for what it looks like - I never run full-screen.) Perhaps the table could be <WRAP right 650px> ... </WRAP>

I also really liked the <color black/white>'' white fields ''</color> to emphasize where the filter criteria should be entered.

One more thing... The TP-Link tl-wr740n originally listed that it supported 15.05, but someone on Youtube https://www.youtube.com/watch?v=FvYhifdQ92Q reported that using 15.05, they ran out of storage attempting to install SQM. I changed the three dataentry's to say 14.07 (from 15.05).

But I wonder how these wound up at 15.05? Was this an import error?

(Last edited by richbhanover on 17 Sep 2015, 03:19)

Let's see if I understood this correctly: Someone was running out of flash storage space when he tried to install SQM?

EDIT: LOL!
"hi thanks for your fast reply..... I did install as your recommendations Chaos Calmer 15.05... it install fine in tl-wr740n as you said... i was happy..... the free size was 66% 424k ( in 12.09 is 88% 876k)   so I install luci-app-sqm with dependecies...... result No space left....7% free space left... so there is no enough room so I revert to 12.09 which has after mwan3 install 648k.......thanks so much  below the logs"

Summary: TP-Link tl-wr740n is not supported by 15.05, because someone wants to install a package which is too big for the remaining flash? LOL!

Honestly: Do we have some information, that the TP-Link tl-wr740n does not boot with 15.05 or otherwise completely malfunctions with 15.05? If so, I would accept the current 14.07, otherwise please change it back to 15.05.

P.S.: extroot exists: http://wiki.openwrt.org/doc/howto/extroot

(Last edited by tmo26 on 17 Sep 2015, 11:31)

OK. I take your point re: attempting to install a package that doesn't fit in flash storage. The initial report did state that 15.05 was working... I have set them back to 15.05.

But I am trying to understand the process here. It appears that some versions were imported as 10.10.3, others as 12.09, but then tmo26 changed them to 15.05

The Device Page only mentions BB release. (http://wiki.openwrt.org/toh/tp-link/tl-wr740n) So how did you know to change them? Thanks.

Simple assumption: If $device is supported in 14.07, and an image exists in 15.05, then $device is also supported in 15.05, unless someone has evidence that 15.05 leads to serious booting issues or even the most basic functions of $device do not work due to insufficient RAM, or any other serious issues.

I think... there is always the risk of bricking or other problems with a new and untested image.
And, we don't really know how good the 14.07 indication is either (perhaps it worked in 12.09, and someone wrote 14.07 with the same argument).

I think 14.07 -> 15.05 should primarily be done by someone who has firsthand information (installing) or second hand information (reading on the forum about successful installation).

A good think with this is that we get an indication what devices are actually used, and we can focus our Device Page effort on those devices.

Finally, I think available space for packages should not be a requirement... as long as there is enough to make reasonable configuration of the default install. It should be enough with 10-20kb, perhaps 50kb. 16MB of RAM is not enough, though.

(Last edited by zo0ok on 17 Sep 2015, 18:50)

As someone who has installed quite a varied number of different units with 15.05 I can tell you there are some cases where the 15.05 image is broken.  Off the top of my head I know the RouterBoard 532 image is broken and the Linksys WRTu54G-TM is also broken.  I also ran into a couple of units that are non-functional with 15.05 because of increased memory demands over 14.07.  I'll try to update the wiki this weekend with my findings.

This leads me to ask the question if there ate wiki stats available.

What wiki pages are most populair? And why, are they populair because of good info, or are people going back over and over again?

Is there a way to collect user feedback? And use that feedback to improve the wiki. 
Maybe only on a small selection of pages. Then people who are not editing the wiki can still give input.

@rayknight:
1) What does "broken image" mean exactly?
2) Is there a general rule, that 4/32 devices will not work with 15.05?

Not really a ToH specific question.

https://forum.openwrt.org/viewtopic.php … 02#p292302

I want to second this. As I remember our early discussions, I thought we agreed that an update to the "supported" version indicates that someone has successfully installed the newest version.

A second benefit: this is another clue to which devices are popular, so that people can come up with a list of routers to recommend.

In view of these benefits, and @rayknight's experience with 15.05 not working in all cases, my vote is to let people update their router's dataentry page after they've successfully installed a version.

I also agree. 

Users will take the version value to mean it is know to work as opposed to believe it works, and this could lead to someone bricking a marginal spec device believing there to be no issue or was tested.

Unfortunately we can only HOPE a user will update the ToH.  This brings us back to promoting device maintenance in ToH header, home page and other ways.

We need to accept that the ToH will always have holes in it.  I expect out of the 900 devices that less than 40 account for over 80% of the user base (Pareto's Principle).  Download stats would help us ID this set of devices.
https://forum.openwrt.org/viewtopic.php … 04#p292404

In this thread I made the comment

but actually think as we potentially have user and download, we could conceptually direct mail them for assistance on maintaining their specific device. 

To calm the naysayers, collecting and using this or any other website data would only be for internal use.

Might it work to request the people on the forum to help testing and reporting.

Set everything to unknown/untested and only tested devices will then get an addition of:
working with Chaos Calmer
or
incompatible Chaos Calmer

I got a request to update the dropdowns for Instructionset / Sub Instructionset.
Since neither myself nor the one proposing this change are "pros" regarding the above items, I would like to get some validation of this proposal prior to any update of the dropdowns.

Current:
Instructionset:
AVR32
ARM
MIPS
MIPS64
PPC
x86
x86_64
other

Sub Instructionset:
ARMv4
ARMv5
ARMv6
ARMv7
ARMv7-A
MIPS IV
MIPS32
MIPS 4K
MIPS 4Kc
MIPS 4Kec
MIPS 24Kc
MIPS 24Kec
MIPS 74Kc
other

Proposal: ADD MIPS IV; CHG MIPS -> MIPS32
Instructionset:
AVR32
ARM
MIPS IV
MIPS32 (in place of “MIPS”)
MIPS64
PPC (maybe it would be better to name it “PowerPC”? I don’t think that everybody knows this shortcut)
x86
x86_64
other

Sub Instructionset: DEL MIPS IV, MIPS32; CHG MIPS32 (e.g. MIPS32 24Kec -> MIPS32 24K/E)
ARMv4
ARMv5
ARMv6
ARMv7
ARMv7-A
MIPS32 4K/E series
MIPS32 24K/E series
MIPS32 34K series
MIPS32 74K series
MIPS32 1004K series
MIPS32 1074K series
other

- Adding of new dropdown values is no problem
- Deleting of existing dropdown values: Existing values in dataentries will stay there, but only be visible in the wikisource, not in the dataentry editor. Reason: The dropdown values are also restrictions for valid values for the respective fields. If you take out a value from the dropdowns, this value is suddenly not valid any longer, hence not being displayed any more, although still available in the wikisource.

=> Deleting/changing valid values for dropdowns needs to be coordinated with the affected dataentries, i.e. first change the valid values (wiki admin area -> my job), then update the dataentries. Since the latter is quite a bit of work (624 devices alone with instructionset = MIPS), I suggest to do this as a batch update, like the initial upload.

Please comment on the above proposal, if it is correct, and if we should implement it like shown above.