Pingbo Posted July 26, 2015 Posted July 26, 2015 Hey,i'm getting the following error, when i try to login me as root: Authentication token manipulation errorThis error appears after i insert the first time the new password.I think this is an error in the Debian Image, isn't it ? Best RegardsPingbo
Igor Posted July 26, 2015 Posted July 26, 2015 Yes this is "normal" ... Debian Jessie related bug. I wasn't been able to nail it down yet. Workaround. Just wait until first boot is finished. You can normally login after first reboot. ps Wheezy and Ubuntu trusty doesn't have this issue.
Pingbo Posted July 26, 2015 Author Posted July 26, 2015 yes, i was waiting for the first reboot, but i still get the error. So here the steps i did: 1. Flash image through the installer you provide 2. start the cubox 3. wait until the first reboot is done and the ssh key and so on are generated. 4. after the second boot login with the root account 5. get the screen to change the password 6. type in my new password and get the Authentication token manipulation error I also tried to reboot it again after the second boot, but it doesn't work Will try another image from you EDIT: Tried all latest images from you, wheezy, jessie and the ubuntu 14.04 image. I getting the same error on all images
tkaiser Posted July 27, 2015 Posted July 27, 2015 i'm getting the following error, when i try to login me as root: Authentication token manipulation error You might also run into this error if for whatever reasons the rootfs is set read-only: I made this experience myself when fiddling around with other FS for the rootfs: http://forum.armbian.com/index.php/topic/120-f2fs-for-rootfs/?p=573 In case you're always using the same SD card I would first test whether it's physically ok. Use either H2testw or F3 on Linux or OS X.
Igor Posted July 27, 2015 Posted July 27, 2015 I made a test and it's working. With this one: http://mirror.igorpecovnik.com/Cubox-i_Ubuntu_2.9_trusty_3.14.14.zip
Pingbo Posted July 27, 2015 Author Posted July 27, 2015 You might also run into this error if for whatever reasons the rootfs is set read-only: I made this experience myself when fiddling around with other FS for the rootfs: http://forum.armbian.com/index.php/topic/120-f2fs-for-rootfs/?p=573 In case you're always using the same SD card I would first test whether it's physically ok. Use either H2testw or F3 on Linux or OS X. thanks will test the way with the rootfs. I think the sd card is ok, because other images running fine. I made a test and it's working. With this one: http://mirror.igorpecovnik.com/Cubox-i_Ubuntu_2.9_trusty_3.14.14.zip ok, let me test it. Will inform you with the results tommorrow
Pingbo Posted July 30, 2015 Author Posted July 30, 2015 sorry for the late test. As expected i get the same error again. Here two "screenshots" First run: http://fs2.directupload.net/images/150731/jc6hlost.jpg After the Reboot and the Login: http://fs1.directupload.net/images/150731/d4coj3wm.jpg
dinsdale Posted January 9, 2016 Posted January 9, 2016 Hi there, I'm trying to boot a hummingboard pro with the i2ex SOM. I am getting the same issue with both wheezy and jessie: "Authentication token manipulation error". I have allowed for multiple reboots and a generous wait time afterwards. Does the system require an Ethernet/Internet connection to complete the initialization process? I was hoping to bring the system up and then use the wi-fi to connect but I also see the brcm-4330 patch has failed. Any pointers? Thanks, Dinsdale
Igor Posted January 9, 2016 Posted January 9, 2016 Authentication token manipulation error You login root with 1234 Than again: 1234 Than your new pwd: somepassword Again your new pwd: somepassword You need to disable eth0 (/etc/network/interfaces) that to boot up with normal speed otherwise system is waiting some time for eth0 to be bough up. The rest I don't understand. Do you have a wifi on your board? It's not on by default - I have the one without for example.
dinsdale Posted January 9, 2016 Posted January 9, 2016 Apologies, it was totally my fault. I wasn't entering the root password a second time. Yes, I have the wi-fi option: a broadcom brcm 4330. The patch is failing: startpar: service(s) returned failure: brcm4330-patch... failed! I'll have a look later. Thank you so much! Russ
Igor Posted January 10, 2016 Posted January 10, 2016 OK, that patch is only for Bluetooth so wireless must work out of the box. What is iwconfig telling you?
dinsdale Posted January 10, 2016 Posted January 10, 2016 iwconfig wlan0 IEEE 802.11agn Essid:off/any mode:Managed access point: not-associated retry short limit: 7 rts thr:off Fragment thr:off Encryption key:off power Management: on ifconfig lists eth0 and lo. Edit: Since I have you here, I noticed this in the boot process: Running bootscript from mmc ... ## Executing script at 10800000 34768 bytes read in 169 ms (200.2 KiB/s) 6015384 bytes read in 537 ms (10.7 MiB/s) My question is where does u-boot get the values to read the script into 10800000 and where does the script live? I can follow the rest that you load from /boot. Thanks! Dinsdale
dinsdale Posted January 10, 2016 Posted January 10, 2016 Ah, think I've got it. I needed to add it to the/etc/networks/interfaces file. I'll have to update wpa_supplicant.conf and tell you how it goes. Thanks again! Er, okay, everything is in the interfaces file. I've got it up and running now. Sorry, I'm coming from FreeBSD. Apparently I have alot of reading to do... Dinsdale
Igor Posted January 10, 2016 Posted January 10, 2016 Yes, we use the standard Debian way of setting interfaces. Peek to the docs. Check /boot/boot.cmd ... the actual u-boot script is binary (boot.scr) which is compiled this way - in case you are going to change anything: mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr But leave those numbers as they are if you want to boot
Recommended Posts