Igor
-
Posts
13658 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by Igor
-
-
I think the problem is kernel loading address. Check this (working) boot script:
setenv bootargs root=/dev/mmcblk0p1 rootfstype=ext4 rootwait console=tty1 video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24,bpp=32 rd.dm=0 rd.luks=0 rd.lvm=0 raid=noautodetect pci=nomsi ahci_imx.hotplug=1 consoleblank=0 vt.global_cursor_default=0 quiet ext2load mmc 0 0x18000000 /boot/dtb/${fdt_file} ext2load mmc 0 0x12000000 /boot/zImage bootz 0x12000000 - 0x18000000Forget about converting. I think it needs to be zImage.
-
Which kernel are you using?
-
You are doing everything O.K.
Change console output to serial to see what's going on and where it's stuck.
setenv bootargs root=/dev/mmcblk0p1 rootfstype=ext4 rootwait console=ttymxc1,115200
-
No, you don't need to recompile kernel, u-boot or download anything. You need to de-compile device tree blob (/boot/imx6q-hummingboard.dtb or /boot/imx6dl-hummingboard.dtb), edit / add, compile back. DTC compiler is within the image.
@Moorviper
Patches are added to the source.
-
Yes, I'll simplify this procedure some day.
Wrote on mobile phone
-
Huh, I am a bit confused. Image with kernel 3.4 should work normally but it's possible that you need to use this module:
bcmdhd
Its from Cubietruck which is practically identical.
-
And remember to add this boot script:
/boot/boot.cmd
setenv bootargs root=/dev/mmcblk0p1 rootfstype=ext4 rootwait console=tty1 video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24,bpp=3 2 ahci_imx.hotplug=1 quiet ext2load mmc 0 0x18000000 /boot/dtb/imx6q-udoo.dtb ext2load mmc 0 0x12000000 /boot/zImage bootz 0x12000000 - 0x18000000
And convert it to the uboot format:
mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr
And of course adjust according to your conditions. This is for one partition SD card. If you have first FAT than some extra work is needed.
-
OK, I think the only problem is that architecture name does not match.
I think this should help:
dpkg --add-architecture armhf
-
Have you try to install this on my image or some other?
-
No. Everything is prepared until:
"Get driver source & type make ARCH=arm"
From there you are on your own. I can guarantee that the driver will work. Install part is also on your own / from the driver if exits.
P.S.
But there is a driver already on the system:
rt2500usb rt2800lib rt2800usb rt2x00lib rt2x00usb
-
The reason why I want to use 5 GHZ network is because the 2,4 GHZ is over crowded in my location. Nobody is using 5 GHZ.
I am having a similar situation but failed to find appropriate / cheap 5Ghz AP. I own three dual band wifi devices (2 x mPCI 1 x USB) and this one is the only one that it (almost?) work. Others, Atheros 9382 doesn't work at all and Intel 7260AC simply does not support AP in 5Ghz.
You'll need to ask driver maintainer for additional help & tips:
-
You can eliminate one error with upgrade:
apt-get update
apt-get upgrade
reboot
-
That sounds great. BTW: Testing with 4.2-rc3 I always ended up relinking /boot/zImage manually (no idea why).
BTW: The sunxi-mmc patch seems to work so I would propose an immediate inclusion: http://www.bananapi.com/index.php/forum/general-discussion-for-bpi-m2/995-working-wifi-on-modern-kernels-4-1-tested?start=30#3038
No idea either
. I'll take a look. I am fixing the whole build structure. BTW: apt-get update works now 
. Need some more testing to make sure.sunx-mmc patch caused an build error on 4.1.3 .. huh
-
Ignore errors, you are running DEV version. Not related.
Try loading the driver with:
modprobe saa711x
Are you running PRO Banana with Wifi or normal one?
What you got under lsmod
If you want to tweak kernel more I suggest you to establish DEV environment like suggested before.
-
Not much but look what I did.
- latest fresh image 4.1.2
- git clone https://github.com/gnab/rtl8812au
- make and load driver
- use default hostapd-rt.conf and hostapd-rt binnary
- use interfaces.hostapd
it works normally. Not tested for 5ghz.. busy @moment.
-
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, ...
-
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.
Change ramlog to direct log writing in kernel 3.4.107
in Allwinner sunxi
Posted
Yes I did. It was irrelevant.
The problem is that if you are using NAND, you are using NAND uboot. So Uboot is not related - at least not the one on SD card
Are you using any "strange" applications?