piCore 5.0.alpha3

[bmarkus]

It works here. What are you doing after modifying the file? Try:

Code: [Select]

sudo echo hdmi_drive=2 >> /mnt/mmcblk0p1/config.txt
sudo sync

before doing anything else to force writing back cache to physical media.

There is a

#hdmi_drive=2

line in the original config file so would be better to remove trailing # than adding it to the end.

[sbp]

Nope any change I make is still not present after a reboot?

[bmarkus]

Nope any change I make is still not present after a reboot?

Can't reproduce.

[sbp]

Hi bmarkus.

Just tested an idea.

Doing all this via ssh using dropbear results in my previous findings, that changes does not survive a reboot.

However, working directly at the rpi with a keyboard, then the changes do survive a reboot.

So somehow there is a problem using ssh and dropbear.

I don't know if it has any importance but in order to use dropbear, I had to make a password for user tc. But it is not different from what I did in version 4.7.7 and here everything is well also via ssh and dropbear.

Steen

[bmarkus]

Have no idea how it can be related to dropbear. My test was done also via SSH but using openssh.

[sbp]

Hi bmarkus

I started from scratch again.

From a clean picore5 I installed Dropbear.
Then made a passwd for tc:

Code: [Select]

sudo passwd tcThen manually started dropbear

Code: [Select]

sudo /usr/local/etc/init.d/dropbear start
Then logged in via SSH and:

Code: [Select]

mount /dev/mmcblk0p1
sudo echo hdmi_drive=2 >> /mnt/mmcblk0p1/config.txt
Then rebooted - I hurrah the change survived a reboot.

********************************************
Then I would like microcore to remember its passwd and to start Dropbear automatically, therefore I made the following changes:
The content of /opt/.filetool.lst:

Code: [Select]

opt
home
etc/passwd
etc/shadow
usr/local/etc/dropbear/dropbear_dss_host_key
usr/local/etc/dropbear/dropbear_rsa_host_key

And the content of /opt/bootlocal.sh

Code: [Select]

#!/bin/sh
# put other system startup commands here
usr/local/etc/init.d/dropbear start
Now Dropbear starts automatically and I can log in using user:tc and password:(the one I just made)  ---   but any changes I make to the /mnt/mmcblk0p1/config.txt file does not survive a reboot

**********************************************
If I instead changes the content of /opt/.filetool.lst to  (removes etc/shadow) :

Code: [Select]

opt
home
etc/passwd
usr/local/etc/dropbear/dropbear_dss_host_key
usr/local/etc/dropbear/dropbear_rsa_host_key

Then Dropbear still starts but microcore does not remember the passwd for tc, so I cant log in via SSH until I via keyboard connected to rpi make a password again like

Code: [Select]

sudo passwd tc
Then I momentarily can connect from another computer via SSH, and any change I make to the /mnt/mmcblk0p1/config.txt file can survive a reboot.

So I think somehow the user management/password is involved in the problem or the etc/shadow backup in the .filetool.lst?

Steen

 

[sbp]

Hi bmarkus

What do you think about this problem?
Do you think that it could be something about the password or user management in version5 compared with version 4.7.7 ?

Steen

[bmarkus]

No idea. Sounds local probéem, not related to piCore 5.0alphax

Can't reproduce.

[sbp]

No idea. Sounds local probéem, not related to piCore 5.0alphax

Can't reproduce.

I'm really sorry that you can't reproduce using dropbear.

Can you spot if I have done anything wrong in my post above?

I will give it one more try, otherwise I will stick to version 4.7.7 which is working fine.

Steen

[bmarkus]

Can you make a copy of your SD card with DD and send it?

[sbp]

Hi bmarkus

Here is a link to the image. : http://rapidshare.com/share/13300978A521499EC521F8221763E0B5

I have once again started from scratch and only installed dropbear, made a password for tc and change .filletool.lst and opt/bootlocal.sh

Dropbear is starting automatically and you login with user=tc   password=nosoup4u

Once again you can't save changes to the config.txt file via SSH but it saves fine when directly connected.

You will have to mount the mmcblk0p1 first:
mount /mnt/mmcblk0p1

Hope you find the problem.

Steen

[bmarkus]

Hi Steen

will take a look during the weekend.

Bela

[bmarkus]

Steen

tested with your image. Procedure works correctly as expected. Logging via SSH I can add a text line to config.txt as you described. After rebooting the previously appended line is there and config.txt file time is correctly indicates time of modification. It works, can't reproduce your situation.

Regards... Bela

[sbp]

Hi bmarkus


Thank you very much for looking into this.

I really had tried to understand this problem, but as you were unable to confirm even with my own image - then the problem must be at my end. That made me think it all over again, and the only difference I could see was that we used different SD-cards.
Therefore, I purchased a new card, and voila now it is working. So my old card seem to be responsible for my issue - and I will try to see if I can figure out how?

Onece again thank you for your tremendous support.  Everything is fine now.

Steen

[bmarkus]

Steen

glad to hear your problem solved. Still I do not understand how it happened.

Bela