Igor
-
Posts
13659 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by Igor
-
-
Firmware upgrade is not needed because it's the same. Libc also not. Technically you only need to change kernel, U-boot is highly recommended since you can only boot up with one CPU if you don't change u-boot. This part might be fixed with latest u-boot but with the one available for download you need to do.
If you want to boot old kernel you need to remove file .next in /boot That's the trick to mention - but it's seen from boot.cmd ... What else can be wrong? 4.0.5 ... If you are booting from SATA it's possible that it's not supported in this kernel yet. Rather use more recent kernel. That one boots from SATA for sure.
Next image is coming with apt-get upgrade for kernel.
-
v3.19.0 does not exists. For valid tags check here:
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/refs/tags
v3.19.8 is what you need.
-
-
How big is your SDSIZE ? And are you constructing desktop too?
I am about to make this part little hard in next update. -
ARM kernel might be very different than what we have on PC and support for our devices just started around 3.16 ... Further. Ubuntu kernels are different than Vanilla's kernel.org
Best chances are with 4.x or latest 3.19
Wrote on mobile phone
-
Yes, this is O.K.. now.
-
OK, for proper future updating you need to mount the media of your boot. But if you boot from SD it's a bit more complex. Under /boot you need to mount a directory /boot from SD card - device /dev/mmcblk0p1
/dev/mmcblk0p1 /media/mmc ext4 defaults 0 0 /media/mmc/boot /boot none bind 0 0
-
OK. than you need to load some extra modules - in this order:
hci_uart gpio_sunxi bt_gpio wifi_gpio rfcomm hidp sunxi-ir bonding spi_sun7i bcmdhd
You can skip some but first try this order.
-
There is no extra boot partition if you boot from SD. One partition, boot is under /boot
-
4.1.3 will be (unofficial) installed as module in my next release. As is.
-
Why would you go for 3.16? It's possible, just change TAG.
-
More about cryptography support. Version which is in kernel 3.4 is very old ...
If you need on board audio you don't have much choice. Kernel 3.4.108
-
I would go for iptables (do it on your own). It's also fun to learn the basis. Other usually just have some more or less fancy interface.
For a simple mostly static setup is more than enough. It's supported by most kernels by default.
Perhaps start here:
https://help.ubuntu.com/community/IptablesHowTo
Basically you pack commands into some startup script and voila.
-
Than let's check which modules do you load. What's inside your /etc/modules or better what's loaded:
lsmod
It should be:
cpufreq_userspace 3524 0 bcmdhd 539724 0 sunxi_ir 4037 0 bnep 14462 2 hidp 17640 0 rfcomm 58686 0 bt_gpio 2741 0 wifi_gpio 6375 2 bcmdhd,bt_gpio hci_uart 25000 0 bluetooth 264185 12 bnep,hidp,hci_uart,rfcomm
and which script.bin are you using. Where is /boot/script.bin pointing to?
-
Maybe the mountpoint for /boot is stored somewhere on sata and therefor I need to unmount /boot and mount to /boot on sd card one time so that correct files are used?
Yes it is
Forgot about that, alter /etc/fstab on your hard drive and you are fine. -
I read there were problems regarding I2C with latest kernel. Try 4.0.8 or other.
The rest I think you are doing right. You should get an error if firmware is missing.
Thanks.
-
No, there are problems with booting on certain Cubietruck with latest image. But the problem is that ethernet is not initialized properly. The fix will be released soon - you can use some older images. Check archive.
If it reboots after a while this is normal and a good sign. At second start you also need to wait a little longer since it's creating swap space. You should get login prompt when everything is done.
-
Exactly which image? Kernel version?
How long do you wait? First time it takes few minutes.
Try another SD card.
-
If SD is inserted and there is an u-boot on it than it will always start from SD card.
Forget about my install procedures. They are only good for fresh start.
1. Create SD card
2. Boot, wait that it finish first boot
3. Login and alter boot scripts to point root to /dev/sda1
4. Copy /lib/modules/ to /dev/sda1 to make sure you have right modules
5. Reboot
I think that's all.
-
If /dev/nand1 is mounted under boot your SD card boot was most likely ignored.
I suggest you to forget about NAND and use good/fast SD card for best performance with less troubles as possible.
-
I am going to add root pwd expiry and setting hwclock to some fixed date, 1.1.2015 to firstrun script?
Next build will also come with new uboot 2015.07 which might help with this issue. I don't have those problems so hard to tell.
-
Power button is not supported by kernel 3.4.108 which is currently the only one where audio features and boot from NAND works. This is common for all distros.
Possible solution is by using any A20 board with kernel 4.x and some supported external DAC while boot loader must remain on SD card. Loading system from SSD is possible in any case.
-
No, if you were booting from NAND and running from SATA before.
-
If you already have your roofs on sata all you need is to change parameter:
from
root=/dev/mmcblk0p1
to
root=/dev/sda1
inside boot.cmd and conver it to boot.scr.
How to change motd?
in Allwinner sunxi
Posted
Don't know yet since I didn't even notice this