Igor
-
Posts
13669 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by Igor
-
-
If you are not in rush I'll try to add it to next kernel build.
-
I made a test and it's working.
With this one:
http://mirror.igorpecovnik.com/Cubox-i_Ubuntu_2.9_trusty_3.14.14.zip
-
If you have serial console you can manually execute boot commands to boot any kernel. And if you upgrade / downgrade kernel it should not affect what you have installed on the system.
If you can't boot is probably because of not proper U-boot. You always need to install that to. (I wrote FAQ to minimize such troubles).
-
Also, am I compiling the kernel correctly?
Short answer. No.
You can compile on a image the driver if you have a source and required dependencies.
If you manage to compile a driver the usual output is:
something.ko
than you load it with
insmod something.ko
if you got no error, try to insert a hardware and check what is kernel telling you with:
dmesg
But you will probably need a whole source and build a kernel with all dependencies if this is not so. I recommend you to compile on some X86 machine otherwise you will compile whole day.
The proper start would be here:
https://github.com/igorpecovnik/lib
Stick to latest stable kernel 4.1.3 but still you might run into troubles.
-
OK, than I need to see what's going on
Gimme a day. -
Xserver in that repository should be accelerated regardless of desktop. You only need to install it properly.
-
My experiences regarding desktop are limited. Especially in this case
On Cubox I only built KODI / XBMC using the same repo and GL (menus) and video acceleration are working perfectly well.
-
Yes this is "normal" ... Debian Jessie related bug. I wasn't been able to nail it down yet.
Workaround. Just wait until first boot is finished. You can normally login after first reboot.
ps
Wheezy and Ubuntu trusty doesn't have this issue.
-
Sure. In the mean time I am preparing deb repository so if everything went ok, next build will be apt-get update-able.
-
Like I said with Bananian or Raspian there is no problem with BananaPro and Lemaker LCD...
Any idea?
I guess the script file is bad - I just copy it from lemaker Github - but we nail down another bug
I'll fix this asap.Just get the latest build 3.4.108 ... some 3.4.107 have stability issues.
-
Oh
Nice to meet you again!I just checked and it's working out of the box. First I used some old 3.4.107 image with link to bananapilcd7.bin since I have normal Banana not PRO ... (try bin from normal Banana. Anyway it should work)
Than I made an upgrade to latest 3.4.108 kernel together with u-boot. Reboot. Again, no problem ... boot output is to LCD.
With default modules on Wheezy:
hci_uart gpio_sunxi rfcomm hidp sunxi-ir bonding spi_sun7i 8021q a20_tp
Edit:
Made another test with fresh Ubuntu trusty 3.2 with 3.4.108cd /boot ln -sf bin/bananapilcd7.bin script.bin reboot
working.
-
I have one 7inch LCD from Lemaker around and the last time it was working.
Have you load the driver - add this to /etc/modules
ft5x_ts
Can you check it?
Yes, I'll and put to faq.
-
Yes, you only need to re-link to proper one. Same size is nothing unusual since the difference is most likely only LCD enable / disable. 1 / 0
And yes, you can use the one from Lemaker. I got them there and I don't think I made any modifications.
-
In added this long time ago to kernel 3.4 ... which is not supported anymore by the author. We should try this with kernel 4.x ... i haven't done the tests - I read somewhere that we don't gain much. Can't remember where
-
Aha, this is missing from FAQ.
Download latest root filesystem and install with dpkg -iThis is the latest at the moment:
http://mirror.igorpecovnik.com/rootfs/linux-wheezy-root-lamobo-r1_3.2_armhf.deb
Kernel upgrade is also advisable. That's described in FAQ. If you are on 3.4.10 upgrade to latest 3.4.x, if you are on 3.19 or higher upgrade to latest 4.x .. You can also upgrade from 3.4 to 4.x but make sure you know about the limitations and changes.
-
Very simple
You don't need to edit anything.git clone https://github.com/gnab/rtl8812au cd rtl8812au make ARCH=arm insmod 8812au.ko
Plug-in WiFi adapter and voila.
AP mode @2.4 working out of the box, I can try 5G tomorrow.
Kernel is 4.0.5, board Orange Pi.
Can you paste your network configuration. Maybe there is a problem?
-
Thomas, thanks for assistance on this.
I am already building 4.1.3 with - I hope - all requests and changing u-boot to latest stable 2015.07 ...
I'll do basic testings and double check to fix all known issues before releasing.
-
I realized that I mixed up something here. This patch is only for SPDIF which is not what you need. Huh. I2S, Damn
The author of both implementations is nikkov@gmail.com ... try.
-
Hard to comment on this. If you can't connect it's not working
Try open mode - without password. The config looks fine but I guess the driver is probably not capable of AP @5Ghz Try the suggested driver. I think it's the best we have than check / open an issue.I know. Pity
P.S.
I have two sample hostapd.config for my hostapd binary. Have you tried that?/etc/hostapd.conf-rt
and
/etc/hostapd.conf
-
Uh
No ideas for a simple strait answer. It's not simple but also not so complex.http://askubuntu.com/questions/18802/how-to-correctly-add-a-custom-daemon-to-init-d
http://minecraft.gamepedia.com/Tutorials/Server_startup_script
Try google for more info if this is not enough.
It's strange because I use similar desktop configuration and it's working without a problem. Also it's pity that Ramlog is not supported anymore: http://www.tremende.com/ramlog/ Try to ping author
-
I would suggest to disable ramlog service with:
service ramlog disable
it's disabled after reboot. If you upgraded to Jessie, Ramlog can't work - not compatible with systemd.
If you are still on Wheezy than try to tweak the boot sequence. Ramlog should be started as early as possible.
-
Little further on is a solution worth to try:
http://www.cubieforums.com/index.php/topic,1081.msg23222.html#msg23222
If you have compile environment just merge and try or wait that I add this to the kernel pack.
-
If you can play less than 24 bit than it's fixable. There is a patch for 24bit playback which is not implemented yet.
-
I never try this myself but according to user feedback I2S is working well on Cubietruck and Banana PRO with the kernel source you are pointing to. I think the problem is if it is wired to the connector and of course if your device settings are correct. On which board you are trying to do that?
On Cubietruck should work out of the box, on Banana PRO you might need to adjust FEX settings (script.bin with decompile, edit, compile back).
[i2s_para] i2s_used = 1 i2s_channel = 2 i2s_mclk = port:PB05<2><1><default><default> i2s_bclk = port:PB06<2><1><default><default> i2s_lrclk = port:PB07<2><1><default><default> i2s_dout0 = port:PB08<2><1><default><default> i2s_dout1 = i2s_dout2 = i2s_dout3 = i2s_din = port:PB12<2><1><default><default>
More info:
How to configure Kernel to activate extra options/modules
in Advanced users - Development
Posted
It's much simpler and faster to add this functionality than teach you step by step how to do it ... even if it's written clearly enough for average Linux user. But problems might occur and this bring more questions.
Read forum / FAQ and you'll get much needed info. It's simple but you need to invest some time.
Download this image and burn to SD (wait until it's uploaded)
http://mirror.igorpecovnik.com/Bananapi_Debian_3.3_wheezy_4.1.3.zip
I added support for Philips SAA7111/3/4/5 video decoders
You need to use my image for easy update. For rest read FAQ. Some manual work is needed. I never try to compile kernel on device because it's way to slow. I don't know if my tool works without any fixes but in any case you need to download a proper Linux source.
And I hope you know limitations of kernels 3.4 vs 4.x ? BTW: most important things are documented on my blog, sunxi wiki, ...