c0nn3ct / x-wrt

Automatically exported from code.google.com/p/x-wrt
0 stars 0 forks source link

USB page empty #100

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Go to Status/USB
2. Look :)
3.

What is the expected output? What do you see instead?
By default there is no package installed for USB support, so USB devices
are not recognised. There is no sign of what to do, it would be very
helpful for new users if there was a button or link to install the required
packages, like there is on the ntp, the qos, or the bandwidth page.

What version of the product are you using? On what operating system and web
browser?
r13370, same with previous releases. Xpsp3enu, Firefox 3.0.4

Please provide any additional info below.

Original issue reported on code.google.com by ivbela on 29 Nov 2008 at 9:59

GoogleCodeExporter commented 8 years ago

Original comment by kemen04@gmail.com on 30 Nov 2008 at 11:43

GoogleCodeExporter commented 8 years ago
Correction: Used X-Wrt version is r4607, the r13370 is the Kamikaze release 
number

Original comment by ivbela on 30 Nov 2008 at 11:46

GoogleCodeExporter commented 8 years ago
The biggest issue here is how to determine what usb driver is needed. Any ideas?

Original comment by kemen04@gmail.com on 10 Jan 2009 at 2:59

GoogleCodeExporter commented 8 years ago
Sure!

I think these packages should be installed by a link/button:
kmod-usb-uhci-iv or kmod-usb-uhci-iv (maybe the script could determine by hw 
version?)
kmod-usb2
kmod-usb-storage
kmod-usb-printer

Or as an alternative, there should be links/buttons for all of them, just like 
on the
WoL page, and then the user can decide which one he/she needs.

On top of that, there should be some small help text to guide new users around,
instead of the unfriendly empty page. I remember when i was new to that page, it
would help a lot if i found the required information there!

This is just a quick idea though, i don't know if it is possible to realise 
it...

Original comment by ivbela on 11 Jan 2009 at 10:31

GoogleCodeExporter commented 8 years ago
The best way I see to do this is to compile a list of hw the needs what driver 
and
display the needed driver to the user, then display all buttons if the hw 
doesn't
match anything in the list.

Original comment by kemen04@gmail.com on 17 Feb 2009 at 2:18