This shows you the differences between two versions of the page.
tutorials:common:begining_on_lubuntu [2013/12/23 14:50] 127.0.0.1 external edit |
tutorials:common:begining_on_lubuntu [2014/07/12 12:19] (current) allen [Camera] |
||
---|---|---|---|
Line 29: | Line 29: | ||
Install openssh-service in computer and cubieboard. | Install openssh-service in computer and cubieboard. | ||
<code bash> | <code bash> | ||
- | $sudo apt-get install openssh-service | + | $sudo apt-get install openssh-server |
</code> | </code> | ||
Line 53: | Line 53: | ||
==== Set keyboard language ==== | ==== Set keyboard language ==== | ||
- | To be defined .... | + | |
+ | Refer to [[tutorials:common:set_keyboard_language|Set Keyboard Language]] | ||
==== Flashplayer ==== | ==== Flashplayer ==== | ||
Line 66: | Line 67: | ||
<code bash> | <code bash> | ||
- | $insmod /lib/modules/3.4.XX/kernel/drivers/net/wireless/XXX.ko | + | $insmod /lib/modules/$(uname -r)/kernel/drivers/net/wireless/XXX.ko |
</code> | </code> | ||
- | **CB3(cubietruck) has Integrated wifi chip .** | + | **CB3(cubietruck) has integrated wifi chip .** |
Type : ''modprobe bcmdhd'' to load the driver . | Type : ''modprobe bcmdhd'' to load the driver . | ||
Add "bcmdhd" at the end of file /etc/modules **to activate WiFi during boot**. For ecample with Lubuntu Desktop: | Add "bcmdhd" at the end of file /etc/modules **to activate WiFi during boot**. For ecample with Lubuntu Desktop: | ||
- | <code bash> $sudo nano /etc/modules</code> | + | <code bash> $sudo vi /etc/modules</code> |
**Configure wifi at cubieboards and cubietruck the same way as descibed her:** | **Configure wifi at cubieboards and cubietruck the same way as descibed her:** | ||
Line 213: | Line 214: | ||
</code> | </code> | ||
- | Modify the parameter according to the using HDMI displayer . | + | Modify the parameter according to the using HDMI displayer .For example ,''screen0_output_type = 3''set up HDMI output ,''screen0_output_type = 4''set up VGA output |
You can get more information about display from [[http://linux-sunxi.org/Display |Display]] and modify script.bin from [[http://docs.cubieboard.org/tutorials/common/edit_the_system_configuration |edit_the_system_configuration ]] | You can get more information about display from [[http://linux-sunxi.org/Display |Display]] and modify script.bin from [[http://docs.cubieboard.org/tutorials/common/edit_the_system_configuration |edit_the_system_configuration ]] | ||
==== VGA ==== | ==== VGA ==== | ||
Refer to HDMI section. | Refer to HDMI section. | ||
+ | Cubieboard1 and Cubieboard2 have no the VGA connector,but you can use [[http://docs.cubieboard.org/addons#cubie_breadboard|Cubie Breadboard]] to effect output. | ||
==== USB Host==== | ==== USB Host==== | ||
Line 224: | Line 226: | ||
IR had beed add into the kernel .If not, use command to load the moudle: | IR had beed add into the kernel .If not, use command to load the moudle: | ||
<code bash> | <code bash> | ||
- | $insmnod /lib/modules/3.4.X/kernel/drivers/input/keyboard/sun4i-ir.ko | + | $insmod /lib/modules/$(uname -r)/kernel/drivers/input/keyboard/sunxi-ir.ko |
</code> | </code> | ||
<code bash> | <code bash> | ||
- | $sudo cat /dev/input/event0 | hexdump | + | $sudo cat /dev/input/event0 | hexdump //or event1,event2 |
</code> | </code> | ||
Press the key of IR remote control,the terminal will print the message as: | Press the key of IR remote control,the terminal will print the message as: | ||
Line 239: | Line 241: | ||
The digital '0094' is keycode of the remote control . | The digital '0094' is keycode of the remote control . | ||
- | + | The sunxi-3.4 IR is exposed as a a keyboard on the Linux input device interface. For example, the following simple keybinder application might be used to run arbitrary commands when receiving a specific keycode via IR. You can install it by | |
+ | <code> | ||
+ | $ git clone https://bitbucket.org/emiliolopez/keybinder.git | ||
+ | $ cd keybinder | ||
+ | $ sudo make install | ||
+ | </code> | ||
+ | Configuration is handled on /etc/keybinder.conf, as a "keycode,command" pair per line. The application prints every keycode received, so you may as well use it to figure out the keycodes you want to use. | ||
+ | |||
+ | To execute the application, run | ||
+ | <code> | ||
+ | $ sudo keybinder /dev/input/event0 | ||
+ | </code> | ||
==== Headphone Jack ==== | ==== Headphone Jack ==== | ||
There are two audio devices HDMI and headphone in the cubieboard. | There are two audio devices HDMI and headphone in the cubieboard. | ||
Line 264: | Line 277: | ||
} | } | ||
</code> | </code> | ||
- | If | + | If plug in the headphone and type: |
- | Plug in the headphone and type: | + | |
<code bash> | <code bash> | ||
$speaker-test -twav -c2 | $speaker-test -twav -c2 | ||
Line 274: | Line 286: | ||
<code bash> | <code bash> | ||
$sudo apt-get install espeak | $sudo apt-get install espeak | ||
- | $espeak "hello" //say: hello | + | $espeak "hello" //say: hello |
- | $espeak "hello_cubieboar" //say: hello cubieboard | + | $espeak "hello_cubieboard" //say: hello cubieboard |
</code> | </code> | ||
- | ==== Camera ==== | + | ==== USB Camera ==== |
- | Most of the camera driver has integrated in the kernel,so it is available insert usb-camera into the cubieboard. | + | Most of the USB camera driver has integrated in the kernel,so it is available insert camera into the cubieboard. |
$sudo apt-get install luvcview | $sudo apt-get install luvcview | ||
$luvcview -s 1080x720 (can modify the resolution) | $luvcview -s 1080x720 (can modify the resolution) | ||
| | ||
+ | If cubieboard has installed mplayer ,use mplyaer to display | ||
+ | <code> | ||
+ | |||
+ | $mplayer tv:// | ||
+ | |||
+ | </code> | ||
==== Micro SD ==== | ==== Micro SD ==== | ||
TBD | TBD |