That i know - still it wont help fix no hw acceleration. Also, image 1.3 is ubuntu, so it doesn't help with this image.
same here (applied the load fix this morning). however, i did notice one thing: using the 1.3-ubuntu image, i get glxgear-FPS about 45FPS (showing "GL_RENDERER: GC2000 Graphics engine" - which should be HW-acceleration i guess) using the debian-image with load-fix, i get 47FPS (but showing "GL_RENDERER = Software Rasterizer" - should be no HW-acceleration only) so eighter debian is really this much faster - or it's only showing to use hw-acceleration, but isn't in reality...??
What is your cpu usage in both case? FPS with glxgears is not really reliable but if you have less CPU usage in the Ubuntu, then it could be the HW acceleration.
ubuntu: glxgears at about 40% (however, Xorg takes about 60% - so cpu is at 100% here). however, load average stays below 1 even if i run it for quite some minutes. debian: glxgears takes 99% (xorg sometimes 1-2%). load average seems to go up quickly...
System only has around 600mb of ram. I noticed the thread about this issue here: http://www.udoo.org/forum/viewtopic.php ... lit=memory If i understand correctly, the ubuntu download got updated to fix this. Will the same happen for this minimal hf debian?
Yep, just collecting some feedbacks in order to update the image with more fixes... Any idea on how to integrate hw video acceleration on debian armhf?
Hi all, I'm trying to test the "minimal quad" image but the boot freezes at "Freeing init memory: 192K" The other image with LXDE works very well! Any ideas?
There is an issue on the minimal . If you look it via serial this is what you'll get . Try to connect with SSH and you should have terminal access
I'm afraid not. Not yet comfortable (at all) with the kernel and driver level things. That is why I'm so happy seeing you've put together a minimal debian. (ty!)
Many thanks for creating this image. Please please please consider migrating/extending the image so that it resides on an f2fs filesystem. f2fs greatly prolonges the life of an SD-card. On my raspberry pies for example I had to replace the sd-card once a month (+/-) and with f2fs they've been running for months already. F2FS kind of(!) lays an extra wearleveling layer onto the SD-card by not overwriting but storing data always in a new location. Only when the card has fully been filled, it starts to erase the "old data" flash segments and writing them with new data. So if you have 2GB of free space on the SD-card, that would mean you have 2GB of wearlevelling space. The newer version of F2Fs also stores data in the inode, reducing the disk space required.
Good to know Flok. Is there good support from Windows?Mac utilities that can cope with f2fs (as that is a consideration... the ability for people to write images to the SD cards on a host PC).
Does Windows have support for ext3 right now? +1 for F2FS, don't care about windows support since only dd like tools should be enough
NEVERMIND NEVERMIND... I removed and reinstalled sudo and the problem went away. When I try to run "sudo visudo", on the Quad Minimal Version I get the following error: using apt-get install shows that it's the latest version. any suggestions
Hello, I am trying to use the non-GUI minimal image to install kali. I tried the maximal, too much stuffz already there, conflicts, etc. QUESTION: How do I get the minimal image, or ANY image to use the full size my card? I'm using a Sandisk 64gb card.
So anyone have any issues getting stuck on first boot? I just loaded an SD with the quad minimal image and I'm constantly getting stuck at/around "Freeing init memory: 192K". Connected via serial and then I can't send and don't receive anything back, the terminal just freezes (no disconnect though). Any ideas?
