please choosego to mobile | Continue to access the PC version
Author: loboris

Linux Distributions for Orange PI H3 boards

  [Copy link]

0

threads

4

posts

44

credits

Novice

Rank: 1

credits
44
Published in 2015-11-5 04:28:39 | Show all floors
palmercr, thanks. I could not find "syslog" in repository, but
sudo apt-get install rsyslog helped.

0

threads

8

posts

38

credits

Novice

Rank: 1

credits
38
Published in 2015-11-5 22:38:53 | Show all floors
I'm trying to run through this solution to see if I can get the Realtek USB wifi to work.  I got to the point where you do the "make" command and I get the error no such file or directory.  The problem seems to be that the symlinks /lib/modules/3.4.39/build and /lib/modules/3.4.39/source point to /home/LoBo2_Razno/OrangePI/kernel_3.4.9/linux-3.4 which obviously doesn't exist.  So I cloned the kernel from [url]https://github.com/loboris/OrangePI-Kernel[/url]  using git and then changed the symlinks to point to the linux-3.4 folder in that download.

That worked but now I get the following error when I run make.  Any ideas?

  1. make ARCH=armv7l CROSS_COMPILE= -C /lib/modules/3.4.39/build M=/home/orangepi/Downloads/RTL8188C_8192C_USB_linux_v4.0.2_9000.20130911/driver/rtl8188C_8192C_usb_linux_v4.0.2_9000.20130911  modules
  2. make[1]: Entering directory '/home/orangepi/OrangePI-Kernel/linux-3.4'
  3. Makefile:567: /home/orangepi/OrangePI-Kernel/linux-3.4/arch/armv7l/Makefile: No such file or directory
  4. make[1]: gcc: Command not found
  5. make[1]: *** No rule to make target '/home/orangepi/OrangePI-Kernel/linux-3.4/arch/armv7l/Makefile'.  Stop.
  6. make[1]: Leaving directory '/home/orangepi/OrangePI-Kernel/linux-3.4'
  7. Makefile:584: recipe for target 'modules' failed
  8. make: *** [modules] Error 2
Copy code

0

threads

8

posts

38

credits

Novice

Rank: 1

credits
38
Published in 2015-11-5 22:41:55 | Show all floors
Oh I should probably add that I already figured out that folder armv7l doesn't exist.  I guess my question is do I need it?  If I do how do I get it?  If not how do I get it to stop looking for it.

0

threads

12

posts

132

credits

Registered member

Rank: 2

credits
132
Published in 2015-11-6 04:33:49 | Show all floors
Glitch69 replied at 2015-11-4 18:49
Hi,
may I ask you to send me some details, what do i have to enable to get the same result as you  ...

Have you installed pull-up resistor between Vcc and 1-Wire DATA ?

2

threads

42

posts

1613

credits

Gold member

Rank: 6Rank: 6

credits
1613
Published in 2015-11-6 04:42:34 | Show all floors
Edited by Fourdee at 2015-11-6 04:44

Simply excellent images loboris!
There so good, we've created the DietPi Orange Pi images using your Debian Jessie image as the baseline.

DietPi - Lightweight justice for your Orange Pi. http://dietpi.com

1

threads

11

posts

108

credits

Registered member

Rank: 2

credits
108
Published in 2015-11-6 12:28:34 | Show all floors
wellwei replied at 2015-11-4 18:12
i am also face the problem

still need help!!!

1

threads

90

posts

769

credits

Senior member

Rank: 4

credits
769
Published in 2015-11-6 14:38:08 | Show all floors
Edited by lymon at 2015-11-6 14:47
etopi replied at 2015-11-5 22:38
I'm trying to run through this solution to see if I can get the Realtek USB wifi to work.  I got to  ...

trying to build that driver on the OPI will not work and you also seem to miss a (cross)compiler and probably other dependencies needed to build the driver correctly


anyway..I have build the driver for you:

cd /tmp
wget https://github.com/lymon66/ORANGEPI-PC/blob/master/8192cu.ko?raw=true
mv /tmp/8192cu.ko\?raw\=true   /lib/modules/3.4.39/kernel/drivers/net/wireless/8192cu.ko
depmod -a

and to check if it is installed correctly:
modinfo 8192cu

I don't have a USB wifi interface with this particular chipset myself, so couldn't test it...



2

threads

3

posts

16

credits

Novice

Rank: 1

credits
16
Published in 2015-11-6 14:51:20 | Show all floors
Hi use OrangePi PC and image Ubuntu_wily_mini.img [2015.10.23] of loboris  in: http://www.orangepi.org/orangepi ... =342&extra=page%3D1
I have a problem:
------------
1. If I only write image to SDcard via Win32DiskImager and NOT rename [script.bin.OPI-PC_720p60_hdmi] to script.bin then Orangepi Pc boot normal (But ethernet not working because not exits script.bin).
---------
2. But if i RENAME [script.bin.OPI-PC_720p60_hdmi]to script.bin then orangepi not boot to os and orangepi Stop in here:
.....
[    3.756383] [wifi_pm]: no wifi used in configuration
[    3.763808] ALSA device list:
[    3.768988]   #0: audiocodec
[    3.774076]   #1: sndhdmi
[    3.778870] Warning: unable to open an initial console.
[    3.790746] Freeing init memory: 6140K
[    4.270097] [DISP] disp_device_attached_and_enable,line:159:attched ok, mgr0<-->device0, type=4, mode=31 <===stop in here and not into os
-------------------------------------------------

Can anyone help me fix problem?

0

threads

12

posts

132

credits

Registered member

Rank: 2

credits
132
Published in 2015-11-6 18:06:55 | Show all floors
BUGBEAR replied at 2015-10-31 12:54
Hello

Iam having a issue with kswapd0 process

edit /etc/sysctl.conf   and append at the end

vm.swappiness=0
vm.overcommit_ratio=2
vm.dirty_background_ratio=2
vm.dirty_ratio=4




reboot the system ... test an report to me

10

threads

448

posts

5073

credits

Moderator

Rank: 7Rank: 7Rank: 7

credits
5073
 Author| Published in 2015-11-6 18:12:52 | Show all floors
@Survive-Pi  To solve the problem with btrfs:
edit the install_to_emmc script, find the mkfs.btrfs command and change it so that it looks like:
  1. mkfs.btrfs -O ^extref,^skinny-metadata -f -L emmclinux ${sdcard}p2 > /dev/null 2>&1
Copy code
There was some changes in new btrfs-tools which make skinny-metadata option default, and it is not supported in the OPI kernel
Make the same change in any script that uses mkfs.btrfs or if you use btrfs format manualy.


@lymon @etopi  The 8192cu.ko driver is allready available in kernel modules directory (/lib/modules/3.4.39[-01-lobo]/kernel/drivers/net/wireless/rtlwifi/rtl8192cu directory)
The driver requires the firmware loading, and it it does not work on Ubuntu Vivid/Willy , same as any driver which requires firmware loading.
You need to log in before you can reply login | Register

Points Rule

Quick reply Top Return list