On Fri, Jan 31, 2014 at 4:14 PM, Mark Pupilli <[email protected]> wrote:
> Great! u-boot 2014.1 with the patch above and kernel 3.13.1-armv7-x9 worked
> first time. Usb camera and usb serial convertor show up in /dev now.
>
> Remaining problems are:
>
> 1. usb0 not working - it comes up after "ifconfig usb0 up" and "ifconfig
> usb0 192.168.0.20" both work, but the LEDS do not come on and no data is
> sent. Do I need a special driver for this? lsmod only shows:
> ftdi_sio 28716 0 - Live 0xbf1c2000
> usbserial 25040 1 ftdi_sio, Live 0xbf1b5000
> gspca_ov534 11132 0 - Live 0xbf19c000
> gspca_main 22504 1 gspca_ov534, Live 0xbf191000
> rtl8192cu 60073 0 - Live 0xbf175000
> rtl_usb 9251 1 rtl8192cu, Live 0xbf16e000
> rtl8192c_common 41155 1 rtl8192cu, Live 0xbf15d000
> rtlwifi 51753 2 rtl8192cu,rtl_usb, Live 0xbf149000
> mac80211 451022 3 rtl8192cu,rtl_usb,rtlwifi, Live 0xbf0b0000
> cfg80211 402423 2 rtlwifi,mac80211, Live 0xbf01f000
> rfkill 18946 1 cfg80211, Live 0xbf015000

Odd, as i just had a user report the musb port was working on the older beagle..

https://github.com/RobertCNelson/netinstall/issues/24

> 2. rootfs is mounted read-only - I thin I can change this in uboot?

I'm guessing Angstrom? (the u-boot patch default to ro for ubuntu/debian)

add to uEnv.txt:

mmcroot=/dev/mmcblk0p2 rw

> 3. and of course, the rtl8192cu driver doesn't work (but it never has - I
> always need to build realtek's version from their website - however, they do
> not seem to have a version which supports 3.13 :(

Use Atheros. ;)

> Nishanth - I would be glad to give whatever information is helpful but being
> a newbie I am not clear about some of the terminology you use e.g. "ensure
> latest linux-next tag and master tags are
> sane and report issues".

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to