Within the last day, I have gained the ability to compile my own test firmware, based on mini_generic. Through experimentation I have determined that the best settings for the LED gpio's are these:
usb_gpio = 0x002;
wlan_gpio = 0x004;
Previous assumption that the wl0 LED was 136 for active low (based on information I got from other people) was probably incorrect.
With setting as shown above, WLAN LED is on when radio is on, off when radio is disabled, and blinks when radio passes packets. WAN LED works as expected: off when ethernet cable is unplugged, on when cable is connected, blinks with traffic.
Note: that's another boardnum. 3 different USR5465's, 3 different boardnums.
Maybe used as board serial number, ie every board has its unique number?
Many days ago I had tried to deduce the boardnum by reading USR's GPL source code, and I think your suspicion has some merit. My recollection is that the boardnum was not a simple #define, so obfuscated that I gave up in favor of reading it directly from the nvram. It's interesting that the USR5461 does not follow the same scheme, despite having much of its code in common with the USR5465.
I like to give back to the community. Attached here is a mini firmware which might be useful for your USR5465 or USR5455. It will probably NOT work in any other router.
It is only at svn13302 (edit: now 13525) because it has been a while since I have worked on it. I need to do more research about whether newer svn's would actually help these routers; many recent changes are for functions not on these routers. If there is interest from the community, I'll recompile.
Features of my firmware:
* FTP server (proftpd on the services:NAS tab) is working.
* CIFS Automount and JFFS2 are included (administration tab) but untested. Maybe somebody will test for me? (edit: the incomplete CIFS support has since been removed.)
* USB1.1 is working. USB2.0 also works but is not 100% reliable yet, so I'm not using it. I'll check later if alternate USB2.0 drivers work better.
* LEDs work properly.
Because USB is working, Frater's "optware the right way" (link) works great on an external hard drive. I'm using it now mainly to run Samba to make a shared NAS accessible by windows boxes, which is simpler than FTP for the users.
Note for USR5455: I have not tested this "access point" model. However, my experience with the USR5461 and USR5432 leads me to say the following. If you are still using USRobotics factory firmware, upgrade to the latest version, and make sure you configure and know the AP's STATIC IP. After you flash with this 3rd-party firmware and erase nvram and reboot, DD-WRT will think the single ethernet port is a WAN port, so at first telnet or http access will only work on the wireless at ssid=dd-wrt. To keep from being locked out if you do "something wrong" with the radio settings, you should first turn on one or more "hardwired" administrative access options. If you leave it in AP mode, enable "Remote Access" in the administration tab; in client bridge mode, enable "Assign WAN Port to Switch" in basic setup. Then connect through the wire to confirm. The good news is that the 30/30/30 reset DOES apparently work on my URS5465, so bricking seems less of a possibility.
Disclaimer: All the usual caveats for any other version of DD-WRT apply. Do a 30/30/30 etc. If any of the above terms are unfamiliar to you, do some research before using this firmware, and/or stick with the factory firmware.
I've only 1 problem, but I think it's not the fw's problem. I've a printer (HP Officejet J3680) and I can't print on it over the router... With the original fw there was the same problem, I've turned off the advanced printing the bi-directional communication and many other options, with another printer (HP Officejet 4110) and with the original fw I can print over the router. But the other printer goes wrong, and this new printer do the following: from the printer's property page send a job to print the test page, ok, printing starts. About 1-2 lines from the page is printed then the printer stops and in the spool the job get an "Error" flag, can't stop the job and if I want to delete it I need to turn off the printer. Of course if I print directly from my computer it works. Any ideas? :)
I have compiled svn 13525 for the USR5465/5455. All the caveats I mentioned above for my custom 13302 apply to this one.
Optware works better on this version, vis-a-vis especially startup and shutdown. If you installed optware on 13302, please wipe it and reinstall after flashing this 13525.
Does anybody need help installing? Just ask and I'll find and post links to the TFTP method, and if pressed, I'll make a version flashable over the USR factory web GUI.
I should have confessed I have never tested USB printing in any version of DD-WRT, be it on the USR5465 or any other manufacturer/model router in my stable.
A few years ago I started buying printers only if they had an ethernet port, assuming I'm going to share it on the network, and these problems just don't happen for me. However, I do remember some initial angst with setting up drivers and shares and so on till I settled on my current modus operandi.
On windows (which I'm guessing you are using, but you didn't say), I do the same thing with the ethernet-capable printers as I did with shared USB or parallel printers hooked to other computers. I install the driver with "have disk" in the add new printer wizard as if the printer was connected directly to the computer I want to print from. After the wizard finishes, I open the printer properties and set it to print to a tcp/ip port using a static IP or the netbios name of the remote printer server (i.e. the other computer or ethernet interface built into the printer). While playing with that aspect of it, you can change the spooling and data format. I think over the network, the RAW format often worked best. You've already mentioned the bidirectional stuff.
Many printers depend on the PC's CPU and driver rather than their embedded CPU to do the bulk of the processing, and I believe the OfficeJet and other "All in One" printer/scanners are typically in this category, but I forget where I heard or read this. Anyway, HP has a support forum much like this one (google is your friend). I think I read there a tip there to use one of the DeskJet drivers built into windows XP (or 2000 a few years ago). There may have been a link to another support page. For example, for the PhotoSmart 2750 printer/scanner, an alternate driver for printing over the network was the DeskJet 990c driver. It has worked and saved me from installing the bloated HP software package with the scanner drivers, which are not real useful for a device in the other room anyway when all you want to do is print some stuff.