gahabana
-
Posts
36 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by gahabana
-
-
I've got a quick question about the Armbian Ubuntu Xenial install. I want to make sure I'm not in the wrong here before looking around for where to submit a bug report. It seems that at least on the C2s, & NanoPI Neos that I have that the /etc/resolv.conf file is not a link to /run/resolvconf/resolv.conf. That doesn't seem right to me, is there a reason it's a regular file and not a link?
It messes things up when moving the computer to different networks as it doesn't update with new DNS settings. Possibly more glaringly it could be a security issue for those unaware or not paying attention while using things like openvpn.
yes, you are right.
thats why after every fresh install i run
sudo dpkg-reconfigure resolvconf
-
I've got a quick question about the Armbian Ubuntu Xenial install. I want to make sure I'm not in the wrong here before looking around for where to submit a bug report. It seems that at least on the C2s, & NanoPI Neos that I have that the /etc/resolv.conf file is not a link to /run/resolvconf/resolv.conf. That doesn't seem right to me, is there a reason it's a regular file and not a link?
It messes things up when moving the computer to different networks as it doesn't update with new DNS settings. Possibly more glaringly it could be a security issue for those unaware or not paying attention while using things like openvpn.
yes, you are right.
thats why after every fresh install i run
sudo dpkg-reconfigure resolvconf
-
Thanks for your reply.
I have my doubts about your thoughts
1.This C2 board runs fine with the stock Hardkernel Ubuntu 16.04 image.
2. This eMMC card has had;
Ubuntu 16.04 running fine.
Arch ARM runnIng fine.
3. Armbian restarts/shutsdown no problem if I do not upgrade.
I do note your point;
I will maybe consider this but I will also consider waiting for the next image release...
hi @mrneilypops ,
well , i think then you must be right
i built images for jessie while 5.17 release and since have been on ubuntu/Xenial ... once i did have a problem when kernel did not upgrade properly but that got fixed by Armbian team next day.
I also have not experimented with GUI/X-Windows - i just used bare/console which may have contributed to your problems.
Solid blue light usually means u-boot doesnt move on to the kernel ... .maybe after you do upgrade but before booting see what is the difference between then /boot/boot.ini file and what you had before. Beyond that it gets too 'geeky' for me and only Armbian folks may be able to help
-
Hi,
I am on my third attempt at running armbian on my C2.
16GB eMMC (purchased through Hardkernel) card.
The image is;
Armbian_5.20_Odroidc2_Debian_jessie_3.14.79_desktop.img
On the last two attempts I have followed the getting started guide and performed an update/upgrade after install;
apt-get update
apt-get upgrade
All setup proceeded without issue.
However, the C2 refused to restart with a steady blue light on the board (no heartbeat).
This is my third attempt and so far I have not upgraded and have tested restart and shutdown a few times...all working well.
Can you give me any advice on this issue?
Should I wait for a new image?
Hi,
i haven't had any such issues ... it happened on few occasions (3 out of 50+) that remote restart (sudo reboot via ssh) didn't work and i had to unplug and poweroff C2 and powerit on again.
I think either your SD card has problems or board has problems.
The only issue (maybe) after sudo apt-get upgrade to do sudo apt-get dist-upgrade (or 1st see if you have any issues)
I always - 1. boot fresh image, let initial boot resize root partition (few sseconds), change root password and create additional user id
2. then i reboot
3. only then i do 1st update/upgrade/dist-upgradew
4. reboot
try that if it doesnt work i think your SD card is faulty or the board itself
-
Please try this headers package: https://dl.dropboxusercontent.com/u/5385968/linux-headers-odroidc2_5.20_arm64.deb
@Zador - you are HERO !!!
yes, that did the trick ! I managed to compile the driver successfully after that (it did not work as i have v2 of TP-Link TL-WN823N) which is 8912eu not 8192cu). Found several versions on github for 8192eu ... couldn't compile any of them due to missing include (error on implicit declaration of ipv6 checksum) - (probably because kernel is bit old - 3.14.xx ). Anyhow, for anyone googling - solution is 2-fold:
1. edit core/rtw_br_ext.c (thats where compile error happens)
2. around line 51 where it says #include <net/checksum.h> ... add line below that which says: #include <net/ip6_checksum.h>
3. compile will finish now (make ARCH=arm64)
4. sudo make install
Second issue i had then was that interface was not called 'wlan0' but 'esxAABBCCDDEEFF0123' which is esx+mac-address of wifi adapter.
Not sure if there is CLEAN way around this ... after some googling i had to add these 2 lines to the file /etc/udev/rules.d/10-network.rules (had to create the file):
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="18:a6:f7:18:61:42", NAME="wlan0" SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="18:a6:f7:18:61:42",KERNEL=="enx18a6f7186142", NAME="wlan0"Lastly, of course, in '/etc/network/interfaces' i uncommented lines for wlan0 interface and changed SSID and passcode.@Zador, 2 quick questions:1. saw couple of minutes ago that there is new update: linux-headers-odroidc2 (ubuntu is what i used as armbian build). Is that the same thing you shared via dropbox in the post above ? if yes -2. is there anything you'd recommend to get in a more standardized way to 'wlan0' name for the wireless interface ?Thanks again !!! -
Some files appear to be missing in kernel headers package. This should be fixed in new release.
hi - that is awesome - by new release do you mean 5.21 ? Any idea how long that would take ? ... week, month ?
Sadly, Armbian is the only tool to build proper working Linux system
either Debian or Ubuntu !thank you !
-
hi,
I installed latest Armbian (Debian/Jessia) as well as built Xenial Ubuntu (5.20 kernel 3.14.79 in both cases). Board is Odroid-C2.
As i have a Wifi USB - TP-Link TL-WN823N I need to build a driver for it as it is not included in kernel.
Found instructions at Armbian documentation: http://docs.armbian.com/User-Guide_Advanced-Features/#how-to-build-a-wireless-driver but after starting with make ARCH=arm64 it fails with error that ... xen.h is missing.
Does anyone have recipe for success ?
Below is failure log on Debian-Jesse (exactly same issue on Xenial-Ubuntu).
Tx in advance !!!
root@odroidc2:/home/zh/rtl8192cu-fixes# make ARCH=arm64 make ARCH=arm64 CROSS_COMPILE= -C /lib/modules/3.14.79-odroidc2/build M=/home/zh/rtl8192cu-fixes modules make[1]: Entering directory '/usr/src/linux-headers-3.14.79-odroidc2' CC [M] /home/zh/rtl8192cu-fixes/core/rtw_cmd.o In file included from /usr/src/linux-headers-3.14.79-odroidc2/arch/arm64/include/asm/dma-mapping.h:27:0, from include/linux/dma-mapping.h:76, from include/linux/skbuff.h:33, from include/linux/if_ether.h:23, from include/uapi/linux/ethtool.h:17, from include/linux/ethtool.h:16, from include/linux/netdevice.h:42, from /home/zh/rtl8192cu-fixes/include/osdep_service.h:765, from /home/zh/rtl8192cu-fixes/core/rtw_cmd.c:23: /usr/src/linux-headers-3.14.79-odroidc2/arch/arm64/include/asm/xen/hypervisor.h:1:50: fatal error: ../../arm/include/asm/xen/hypervisor.h: No such file or directory #include <../../arm/include/asm/xen/hypervisor.h> ^ compilation terminated. scripts/Makefile.build:308: recipe for target '/home/zh/rtl8192cu-fixes/core/rtw_cmd.o' failed make[2]: *** [/home/zh/rtl8192cu-fixes/core/rtw_cmd.o] Error 1 Makefile:1278: recipe for target '_module_/home/zh/rtl8192cu-fixes' failed make[1]: *** [_module_/home/zh/rtl8192cu-fixes] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-3.14.79-odroidc2' Makefile:584: recipe for target 'modules' failed make: *** [modules] Error 2 -
yup - @zador.blood.stained - thank you - this fixed it !
haven't tested if those changes cause new behaviours (not sure what those cachemodule in kernel does - i assume its caching of the filesystem, the other one i have even less insight on
thanks !
-
hi, i just had the Error during build process .... have reinstalled Armbian build environment from scratch to be sure
git clone https://github.com/igorpecovnik/lib --depth 1 cp lib/compile.sh . sudo ./compile.h
I select Odroid-C2 as target and either 'Kernel, u-boot etc' or Full OS Image, I get error message:
mv: missing destination file operand after '/home/zh/Downloads/ip/output/debs/'Try 'mv --help' for more information. [ error ] ERROR in function compile_kernel [ common.sh:203 ] [ error ] Failed moving kernel DEBs [ o.k. ] Process terminated
Prior to that i think Kernel build fails which is causing source/destination .deb (kernel) NOT to be built and that is why move above fails:
Building modules, stage 2. │ │ MODPOST 1045 modules │ │ ERROR: "get_pfnblock_flags_mask" [fs/cachefiles/cachefiles.ko] undefined! │ │ /home/zh/Downloads/ip/sources/linux-odroidc2/odroidc2-3.14.y/scripts/Makefile.modpost:90: recipe for ta │ │ make[3]: *** [__modpost] Error 1 │ │ Makefile:999: recipe for target 'modules' failed │ │ make[2]: *** [modules] Error 2 │ │ /home/zh/Downloads/ip/sources/linux-odroidc2/odroidc2-3.14.y/scripts/package/Makefile:90: recipe for ta │ │ make[1]: *** [deb-pkg] Error 2 │ │ Makefile:1131: recipe for target 'deb-pkg' failed │ │ make: *** [deb-pkg] Error 2
It used to work until 2 days ago so am not sure if anything changed in kernel itself (dont see any changes in last 48 hours in github), but don't see any on Igor's github either ...
anyone has a clue ?
thanks in advance !!!
-
hi Igor,
fantastic job !!! I've managed to get Roon Endpoint nicely and smoothly running on Odroid-C2 ONLY because you built distro that can do it
(Xenial Ubuntu server).... all it took is to install armhf libraries for 32bit code from Roon to run on it !Out of curiousity i tried to build the image myself. All went well ... version i got is NEWER then the one you had share (Armbian_5.17_Odroidc2_Ubuntu_xenial_3.14.79 rather then rather then the one that can be downloaded which is Armbian_5.14_Odroidc2_Ubuntu_xenial_3.14.79). Worked ok in limited testing ... on both i had to do 'dpkg-reconfigure resolvconf' as it was had my external ISP (or google one) as DNS server so couldnt recognise machines on my LAN without that.
However, when i do apt-get update and then apt-get upgrade it wants to install 'newer' kernel linux-image-odroidc2 and headers though they are older (i have kernel 79 vs 74 in repository) ... if i accept upgrade, it 'bricks' the machine -doesnt boot anymore. I am sure that will be 'fixed' when you release update image but it would be great if there was a way to tell to apt-get to not upgrade kernel until version number is larger then the one currently installed.
Just to be on a safe side (cause i would miss future upcoming updates) i reverted to 'stock' build - 5.14 version and am very happy !!!
What are your thoughts ?
thank you !
Kernel dev (4.9) - which board runs reasonably well - Orange PI One , NanoPI Neo or something else ?
in Beginners
Posted
hi all,
would love to run 'mainline' kernel on some of the boards. Armbian does provide 'choice' today for most/many Orange boards as well as NanoPI ... tu build the image with mainline/4.9 kernel. my needs are not too complex
a) Ethernet
...
Is there anyone on a forum who has tried recent 4.9-rc or maybe even 4.8 and it worked well and if yes which boards did you use ?
I am running Odroid-C2 happily with Armbian and 3.14.79 kernel but some of the very old bugs have been fixed later on (kernel bugs) and am looking for a board that might run recent kernel well (enough).
Thank you !