Reply
Thread Tools
Posts: 46 | Thanked: 37 times | Joined on Aug 2015
#11
You guys are gold - the signature errors are gone!

after some successful updating, apt-get update still produces a couple of lines like these though:
N: Skipping acquire of configured file 'main/binary-armel/Packages' as repository 'https://maedevu.maemo.org/leste chimaera-devel InRelease' doesn't support architecture 'armel'

How does this armel stuff get in there...?
 
Posts: 61 | Thanked: 55 times | Joined on Jul 2023 @ Europe
#12
That's a good question...don't know what's going on with your install.
Did you manually add armel stuff from Fremantle or ?

Anyway, that's probably better to restart from the beginning and 'burn' a new img in your sd card.

FYI there is no armel stuff in Leste, it uses armhf on N900. Armel pkg's from Fremantle can't run on Leste, they must be ported. (See Leste wiki)

Last edited by Arno_11; 2024-02-19 at 10:43.
 

The Following User Says Thank You to Arno_11 For This Useful Post:
Posts: 46 | Thanked: 37 times | Joined on Aug 2015
#13
Oh man... yup... I must have sneaked it in and forgot about it.
Got rid of it by
Code:
dpkg --remove-architecture armel
 
Posts: 46 | Thanked: 37 times | Joined on Aug 2015
#14
All seems to be running well now, many thanks!
Weird though that "apt-get update" sometimes works, but sometimes throws this error:

Code:
Err:1 https://maedevu.maemo.org/leste chimaera-devel InRelease
  Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate.  Could not handshake: Error in the certificate verification. [IP: 95.217.97.169 443]
Also: You spoke of a new image that's coming up... Any idea of an ETA?
 
Posts: 61 | Thanked: 55 times | Joined on Jul 2023 @ Europe
#15
The way it works means you don't really need a new image, just dist-upgrade when needed and you'll have the same result.

For the error, that's weird and i can't reproduce it on my device, so no idea ATM.
 

The Following User Says Thank You to Arno_11 For This Useful Post:
Posts: 46 | Thanked: 37 times | Joined on Aug 2015
#16
Originally Posted by teroyk View Post
Please come here to make announcement when next one is out for download.
Merry Christmas everyone!
https://phoenix.maemo.org/job/leste-.../arm-sdk/dist/
 

The Following User Says Thank You to sebar For This Useful Post:
Posts: 46 | Thanked: 37 times | Joined on Aug 2015
#17
Interesting! Could the errors I frequently get when using "apt-get update" be connected to the overclocking? When overclocked like this:
Code:
echo 1 > /sys/devices/system/cpu/cpufreq/boost
the system is running seemingly stable, but dpkg maybe not so much - could that be? Once I even got a segfault when trying to update. All gets well when I restore "/var/lib/dpkg/status":
Code:
cp /var/backups/dpkg.status.0 /var/lib/dpkg/status
and returning to stock speed:
Code:
echo 0 > /sys/devices/system/cpu/cpufreq/boost
 
Posts: 61 | Thanked: 55 times | Joined on Jul 2023 @ Europe
#18
Maybe 850MHz is a bit too much for your device:

In

Code:
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
You can try 805MHz as the maximum frequency and see if things work better.
 

The Following User Says Thank You to Arno_11 For This Useful Post:
Posts: 46 | Thanked: 37 times | Joined on Aug 2015
#19
Thanks! That might have been the culprit. I didn't know that a too high clock speed can have an impact of that kind.
 
Posts: 61 | Thanked: 55 times | Joined on Jul 2023 @ Europe
#20
I think there is no direct impact but apt runs usually at the max frequency so it could explain why things are not stable enough during updates.

BTW you can choose 720, 805 or 850 as max frequency when boost is activated.

( Or you can simply deactivate boost during update as a workaround )

Last edited by Arno_11; 2023-12-27 at 11:32.
 
Reply


 
Forum Jump


All times are GMT. The time now is 07:50.