-
Posts
14421 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by Igor
-
-
Just an idea how to fix this. Perhaps (I haven't check the code) the device tree for sun7i-a20-ainol-aw1.dts is faulty - remove it from the arch/arm/dts/Makefile ... and try to compile again.
-
It means you can't really use it much but yes it's booting. I think we got UART and USB ... and probably more. Since there is no network I didn't look anything else. U-boot is mainlined.
-
I built the image 5 days ago. Not ready for anything. I am uploading it and will be here:
Armbian_Orangepiplus_Debian_wheezy_4.4.0-rc4.zip
-
There was one issue with version - images were without - fixed.
-
it's possible since there were so many changes. I'll look into this part and fix.
-
Yes, files on Github should be O.K. but to write this without "should" I need to double check.
-
Thanks for sharing. BTW ... USB_STORAGE is build into all Armbian kernels for some time.
Well, you solved it. Good!
-
To be determined after several tests.
If you don't want to hear a fan running, then lowering the top might be an option. I made only few tests so it's hard to say what's better.
-
I made one image but I don't know why is not booting. I have to construct level convert to be able to use a normal serial console. I forgot the fact it uses different voltage logic.
You have serial console?
-
Ok, tell me which kernel version and/or system did you build?
Poslano z mojega MI 2S z uporabo Tapatalk
-
@Tido
Don't want to erase or alter anything unless it's really necessary. I am not that sensitive either
@khgoh
I can understand and support your genuine passion to build a good device. I really do.
Let's look on the device trough the marketing fog - what's reality, which we usually refuse to see, and what the history tells us. I don't believe that this board can bring any better experience if a business model remain unchanged.
SoC supplier Allwinner doesn't really have a good reputation in areas like: support, working with community, playing a fair game, ... Their release of crappy outdated source code is more like a joke and it usually doesn't work without blobs.
It needs heavy fixing and no one has done that for previous AW chip series (A80, A83, H3, ...) in about a year. Check their Github, what's released, when and what was done after that. AW doesn't properly support their products and you also won't (be able to). Board without support isn't worth a penny but it's possible to sell it. People buy numbers and promises.
Our community here is mostly interested in real Linux experience where the only interesting thing most likely won't never work - 4K video within Linux and/or inside KODI under Debian or within Openelec. It also looks like 4K can go up only to 30p which is totally useless for a desktop usage. I might be wrong about not providing 4k@60p but haven't found the opposite information.
Stripped down: yet another limited usage Android device/setup box without a proper box, PSU and cables. I don't know how much will this 15$ board cost when it hit retail. Let's take an example of Raspberry Pi ZERO "price fraud" - the lowest price (more or less) for 5$ valued RPi Zero is 14.95 EUR + shipping cost, which means 24.90 EUR in total to get it to my desk or let's say around 20 EUR for most EU folks.
We talked the other day with @tkaiser and come out with conclusion that current SoC market is getting flooded with shitty boards. Not even one new board can be undoubtedly recommended for general usage.
I am not offended, don't worry about it.
-
We are preparing a new build script, give it a try.
http://forum.armbian.com/index.php/topic/404-stable-vs-mainline-for-next/
Logs are in output/debug folder
-
Have you try this way:
root=UUID=e139ce78-9841-40fe-8823-96a304a09859
I'll recreate similar scenario later just to make sure.
-
Games?
For example - inside KODI you needs Mali for GUI operations while video playing goes over different engine.
-
OK, more logical. Fine with me.
-
Cubieboard A80 is under watch but unfortunately there are just too little people working on it. It was on my desk today and quickly went back in the drawer since I figured out I can't boot mainline u-boot just like that. It would require to sum up all the patches and maybe, maybe it will be possible to boot and than further to kernel 4.x I'll try again in the next few days. You can check the status:
http://linux-sunxi.org/Linux_mainlining_effort
https://linux-sunxi.org/Mainline_U-boot
Old 3.4. kernel for those board hasn't changed much since it was released and it's complete waste of time to deal with it.
-
To achieve this in current script is a bit hard but you are welcome to jump into testing branch, where this is possible out of the box. This was also one of the core reasons to rework the script.
Use this branch:
https://github.com/igorpecovnik/lib -b master
Remember to alter branch in this line before start and start from clean dir.
https://github.com/igorpecovnik/lib/blob/master/compile.sh#L78
It's a dev branch so please be patient ... and report if you encounter strange behavior.
-
Also the consoleblank=0 could / should do the job if you are using CLI console. For X is another story.
-
General public is easy to mislead to backup the project - general public aka kick-starter community is dumb as hell. It's all about marketing. SBC's are still hot stuff and hardware development become ridiculous cheap so it's a great way to make money.
As I see you already made it to persuade investors. Why bother developers community, where you don't intent to invest more then few free boards here and there and use our channels for free marketing? BTW: You can run your marketing campaign on your own website or wherever but here you need to ask for permission. I hate ads.
Even before your boards become stable (to be used by professionals which is stated in your first line of your marketing appeal) you will probably restart the whole thing with a "new and better" board and hope to catch as many backers as possible. All board manufacturers are using community's current and future contribution in their business models and everyone want's to become next RPi in numbers. This is the only way you don't need to pledge anyone. Until then, we control the game.
Free sample? I have a bunch of boards and so do other people who develop and contribute. I don't even think to support your boards without paradigm change toward community. You collected the money for our work and you kept it. What the f*?
You are an engineer. It's is not your fault nor responsibility to think about this in such way. Don't take it personally either.
-
Try to set desired root by it's UUID. It should work.
https://help.ubuntu.com/community/UsingUUID
edit /boot/boot.cmd and change parameter root= , save, recompile, reboot.
-
HDMI sound crash ... That "sounds" strange.
The kernel I am using is more or less stock + upgrades to .54 which should not have affect on this. I'll double check. Please address this issue to Solidrun if they have any clue about it.
-
Add
setenv fdtfile sun4i-a10-mk802ii.dtb
at the beginning of /boot/boot.cmd script, recompile and try to boot. Remember that not all things works in vanilla yet.
-
Hm, missed true meaning of clean level 4, "dell all output" in compile.sh is not descriptive enough in this case
I know.
More and better comments are needed. I made few test runs and it looks good ... busy with life until evening.
-
I am done until evening.
Some ideas:- I need to see new kernel features, so make olddefconfig / oldconfig must be an option and always out of dialog
- this dialog on/off option would be cool also a blank, no console output, only log
- when mostly done we can alter/adjust script names
Install Nand on CubieBoard1 fail
in Allwinner sunxi
Posted
Yes, it's possible to use this but it's not the proper way - upgrading will not work properly ...
Copy uEnv.txt, script.bin and uImage, located in /dev/nand1 to /boot , located in /dev/nand2 and reboot.
It will work.
I am searching for sources to fix this properly. I only found an working U-boot source for A20.
Current Uboot doesn't have support for NAND, that's why we need to use this prehistoric
Eventually this will change.