Jump to content

Uli Nichtder

Members
  • Posts

    5
  • Joined

  • Last visited

  1. Hi, I just got a mini ITX Board for just 20 bucks, with PCIe x1 Slot, an M.2 Slot and a miniPCIe Slot - okay, only 1 Gig of Ram and only dualcore, but hey... Advantech Freescale RSB-6410 NXP ARM® Cortex®-A9 i.MX6 Dual/Quad Mini-ITX Motherboard Manufacturer Dropbox Images Wiki Page... I thought, how hard can it be to bootstream armbian/debian on this device, but despite chroot'ing into debian I did not really succseed and stuck in a really (!) crappy Yocto Linux environment without any packet manager and crappiest QT Interface you can think of... In the Dropbox folder of the manufacturer there are a couple of sd card images, but everything I try does not boot, or boots into a "non screen" Environment (core-image-full-cmdline-imx6qrsb6410a2-20180809071407.rootfs.sdcard - seems that there is only console via Serial) or a slightly newer kerne (4.15) again in combination with a terrible, tool-less Yocto QT GUI (fsl-image-qt5-imx6qrsb6410a2-20180809063135.rootfs.sdcard) - the other files don't boot at all... Nevertheless, armbian/debian has to be installed... Since this Board is not supported out of the box yet, could someone tell me how to adapt the already released i.MX6 builds to this board? I got the whole environment saved and especially the dtb file for this board is also saved. Would be nice if someone could help me roughly which steps are mandatory for adding this board to the build environmet. I am not new to linux, but I am new to adding hardware-platforms to anything :-) Thanks a lot! Cheers, P.S.: Anyone who has asked himlself why the InFlight Entertainment in many planes is slow, crappy and freezes suddenly should take a look at yocto with qt5.... the demos delivered with the yocto thingie reminds me of the QNX 3,5" Demo Disk of the late 1990ies with a RTOS and a Webbrowser on it - but, the QNX Demo Disk was faster, and better in any way :-)
  2. Ouch.... that is even more quick'n dirtier than my rc.local solution eeeehh.....:) Didn't think that was possible:-) (Because: since is is user related, you cannot directly find it in the /etc if you are searching for something like that) Cheers
  3. ...its the networkmanager 'crap' which is causing the problems.... I did a very quick and dirty hack und added # By default this script does nothing. ip add add 192.168.64.82/24 dev eth0 ip ro add default via 192.168.64.254 exit 0 in /etc/rc.local.... and guess what, my orange pi is booting with network connection established every time. So, it has to be the network manager causing the trouble... Cheers,
  4. I am just uploading this: http://ix.io/1n9U (when or where is this data collected? because that is not true, neither for eth0 nor for wlan0 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 02:42:38:94:64:9d brd ff:ff:ff:ff:ff:ff) Currently THAT is the correct state...: 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 inet 192.168.64.81/24 scope global eth0 valid_lft forever preferred_lft forever The funny thing is though, when I kept ethernet unpluged while booting, plugged it in after booting, I got a DHCP Address the first time. Then I configured (again) a fixed IP address with armbian-config, which did NOT work after a plugged reboot. Then I repeated that, gaining access again and configured additionaly wifi (which gets also an IP address by DHCP but from a completey different Network). After the next reboot (ethernet plugged in) Wifi was accessible, ethernet was not. But now I could log in via Wifi and saw "eth0" was up (!) but had not been assigned any IP Address - since it should be a fixed one now, the problem does not be dhcp related it seems. The very funny thing is, if i do (and I did :-) a ip add add 192.168.64.81/64 dev eth0 everything I gained a connection again.... So.... nic drivers are good, 'ip li sho' tells me it's detected a link but neither dhcp nor fixed ip address by networkmanager assigns correctly.... so it seems to be a network manager issue. I'll investigate this further... Cheers,
  5. Hi there, after upgrading my OneZero "Farm" as well, I got the same problem. After upgrading to the latest release (they were shut down for a couple of months) and the mandatory reboot after that none of my three Pi Zeros were reachable by ethernet any more... Checking the config on the cards all seems fine. I can confirm that your workaround is the only working one so far - If I plug in the network cable after they're bootet up gives me a valid IP address as well. But thats a real showstopper for a small opi-zero cluster for testing...:-) The funny thing is, I modified my Image with the config Editor ./armbian-image-config Armbian_5.59_Orangepizero_Debian_stretch_next_4.14.65.img ethernet static 192.168.64.81 255.255.255.0 192.168.64.254 192.168.64.254 mynet.lan remote ssh enabled ethernet network with ip 192.168.64.81 active for image: Armbian_5.59_Orangepizero_Debian_stretch_next_4.14.65.img Which is *completely* ignored... (but if I configure a static IP after booting, this config is kept.. but the reboot problem with connected ethernet persists anyway :-( Did something essental got changed regarding the network configuration? Thanks alot! Cheers Uli
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines