0
Pingbo

Cubox i2ex Problem

Recommended Posts

Hey,

i'm getting the following error, when i try to login me as root:

Authentication token manipulation error

This error appears after i insert the first time the new password.
I think this is an error in the Debian Image, isn't it :unsure: 

Best Regards
Pingbo

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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  :(

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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  :)

Share this post


Link to post
Share on other sites

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 

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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 ;)

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.
0