The Volla Quintus (algiz) thread

Hardware Adaptation
141

zypper ls gives me:

ssu ls

Usage: ssu [-command-options] [arguments]

Repository management:
mode, m Show repository mode information.
Set repository mode as an integer (see docs).
Combo of modes to set from: DisableRepoManager RndMode
ReleaseMode LenientMode UpdateMode AppInstallMode
updaterepos, ur update repository files
repos, lr list configured repositories
[-m] format output suitable for kickstart
[device] use repos for ‘device’
[flags] additional flags
rnd= set rnd or release mode (default: take from host)
addrepo, ar add this repository
[url] specify URL, if not configured
removerepo, rr remove this repository from configuration
enablerepo, er enable this repository
disablerepo, dr disable this repository

Configuration management:
flavour, fl display flavour used (RnD only)
[newflavour] set new flavour
release, re display release used
[-r] use RnD release
[newrelease] set new (RnD)release
set display global variables
[-r] operate on repository only variables
display value of
set value of to
domain do display current device domain
[newdomain] set new domain
[-c] show domain configuration
-c show single domain variable
-c set single domain variable

Device management:
status, s print registration status and device information
register, r register this device
[-h] configure user for OBS home
unregister, unregister this device
update, up update repository credentials
[-f] force update
model, mo print name of device model (like N9)
brand, b print brand of device model

142

zypper dup does nothing:

zypper dup
Error building the cache:
[adaptation-community|plugin:ssu?repo=adaptation-community] Valid metadata not found at specified URL
History:

  • [adaptation-community|plugin:ssu?repo=adaptation-community] Repository type can’t be determined.

Warning: Skipping repository ‘adaptation-community’ because of the above error.
Error building the cache:
[adaptation-community-kernel|plugin:ssu?repo=adaptation-community-kernel] Valid metadata not found at specified URL
History:

  • [adaptation-community-kernel|plugin:ssu?repo=adaptation-community-kernel] Repository type can’t be determined.

Warning: Skipping repository ‘adaptation-community-kernel’ because of the above error.
Error building the cache:
[adaptation-halium|plugin:ssu?repo=adaptation-halium] Valid metadata not found at specified URL
History:

  • [adaptation-halium|plugin:ssu?repo=adaptation-halium] Repository type can’t be determined.

Warning: Skipping repository ‘adaptation-halium’ because of the above error.
Some of the repositories have not been refreshed because of an error.
Loading repository data…
Reading installed packages…
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See ‘man zypper’ for more information about this command.
Computing distribution upgrade…
Nothing to do.

143

Its probably easier to manually update the repo ursl by editing the file /usr/share//ssu/features.d/community-adaptation.ini

change the last few lines to

[repositories]
adaptation-community = https://repo.sailfishos.org/obs/nemo:/testing:/hw:/volla:/halium-algiz:/%(releaseMajorMinor)/sailfishos_%(releaseMajorMinor)_%(arch)
adaptation-halium = https://repo.sailfishos.org/obs/nemo:/testing:/hw:/halium:/13:/%(releaseMajorMinor)/sailfishos_%(releaseMajorMinor)_%(arch)

then

ssu ur

zypper ref

zypper dup

144

there are
adaption-community-common.ini
adaption-community.ini
adaption-halium.ini

which one is the right?

ok found on myself it’s adaption-communiy.ini

145

adaptation-community.ini

You should delete community-adaptatoin-halium.ini

You could get updates to droid-config-*, and then i -hope- you are properly et up with the correct new repo URLs

146

It’S doing some things at the moment. I will report after it has finished and rebooted

147

I wonder about the errors

Repository ‘adaptation-community’ wird aufgrund
des obigen Fehlers übersprungen.
Repository ‘adaptation-community-common’ ist
aktuell.

Metadaten von Repository 'adaptation-com[Fehler]
Repository ‘adaptation-community-kernel’ ist ung
ültig.
[adaptation-community-kernel|plugin:ssu?repo=ada
ptation-community-kernel] Keine gültigen Metadat
en bei dem festgelegten URL gefunden
Verlauf:

  • [adaptation-community-kernel|plugin:ssu?repo=
    adaptation-community-kernel] Repository type can
    't be determined.

Überprüfen Sie, ob die für dieses Repository bes
timmten URIs auf ein gültiges Repository verweis
en.
Repository ‘adaptation-community-kernel’ wird au
fgrund des obigen Fehlers übersprungen.
Metadaten von Repository 'adaptation-hal[Fehler]
Repository ‘adaptation-halium’ ist ungültig.
[adaptation-halium|plugin:ssu?repo=adaptation-ha
lium] Keine gültigen Metadaten bei dem festgeleg
ten URL gefunden
Verlauf:

  • [adaptation-halium|plugin:ssu?repo=adaptation
    -halium] Repository type can’t be determined.

Überprüfen Sie, ob die für dieses Repository bes
timmten URIs auf ein gültiges Repository verweis
en.
Repository ‘adaptation-halium’ wird aufgrund des
obigen Fehlers übersprungen

148

It says adaptation halium is invalid URL and will be ignored
zypper dup then gets interrupted and dies nothing

[root@RainerZufall defaultuser]# zypper dup
Fehler bei der Erstellung des Cache:
[adaptation-community-kernel|plugin:ssu?repo=ada
ptation-community-kernel] Keine gültigen Metadat
en bei dem festgelegten URL gefunden
Verlauf:

  • [adaptation-community-kernel|plugin:ssu?repo=
    adaptation-community-kernel] Repository type can
    't be determined.

Warnung: Repository 'adaptation-community-kernel
’ wird aufgrund des obigen Fehlers übersprungen.
Einige der Repositorys konnten aufgrund eines Fe
hlers nicht aktualisiert werden.
Repository-Daten werden geladen…
Installierte Pakete werden gelesen…
Warnung: Sie sind im Begriff, eine Distributions
aktualisierung mit allen aktivierten Repositorys
durchzuführen. Vergewissern Sie sich, dass dies
e Repositorys kompatibel sind, bevor Sie fortfah
ren. Weitere Informationen zu diesem Kommando fi
nden Sie unter ‘man zypper’.
Distributions-Aktualisierungen werden verarbeite
t…
Keine auszuführenden Aktionen.
[root@RainerZufall defaultuser]#

149

Device has booted into Sailfish again. Vibration and system sound is back. Aside from the main camera, the cameras work again as well. THANK YOU!

Repositories now look like that.

[root@Quintus defaultuser]# ssu lr
Enabled repositories (global):

Enabled repositories (user):

zypper ref returns no errors anymore.

If I have you at the moment so active. :innocent: Do you have any news about my main camera and flashlight. Is there a new vendor image?

150

I think you have to follow @piggz instructions from here:

1 Like
151

There is an updated file from volla, ill test it and get back to you

2 Likes
152

This sounds great. Thank you for your support. Will send you some beers.

1 Like
153

I followed the steps after a reboot, still the same.
I have the feeling that maybe here something is not correct

[root@RainerZufall features.d]# rpm -qi communit
y-adaptation-testing
Name : community-adaptation-testing
Version : 0.0.4
Release : 1.9.1.bso
Architecture: noarch
Install Date: Mo 03 Nov 2025 19:11:59 WET
Group : Unspecified
Size : 609
License : BSD-3-Clause
Signature : (none)
Source RPM : community-adaptation-testing-0.0.4
-1.9.1.bso.src.rpm
Build Date : Sa 14 Jun 2025 14:09:08 WEST
Build Host : phost18
Vendor : meego
Summary : Community HW adaptation setup, tes
ting flavour
Description :
Community HW adaptation setup, testing flavour.
[root@RainerZufall features.d]#

154

Is vendor meego correct?

Somewhere along the way I saw chum instead

155

You have replaced the two lines in adaption-community.ini?
And you have deleted adaption-halium.ini?

after that

ssu ur

zypper ref

zypper dup

156

Yes, still the same errors and zypper does nothing

n-com[Fehler]
Repository ‘adaptation-community’ ist ungültig.
[adaptation-community|plugin:ssu?repo=adaptation
-community] Keine gültigen Metadaten bei dem fes
tgelegten URL gefunden
Verlauf:

  • [adaptation-community|plugin:ssu?repo=adaptat
    ion-community] Repository type can’t be determin
    ed.

Überprüfen Sie, ob die für dieses Repository bes
timmten URIs auf ein gültiges Repository verweis
en.
Repository ‘adaptation-community’ wird aufgrund
des obigen Fehlers übersprungen.

157

have you copied and pasted it or did you write it into the file? Can you exclude a typo?

How does your repos look compared to my last posted list here: The Volla Quintus (algiz) thread - #149 by Fellfrosch

158

Something has gone terribly wrong with my device, but an old habit of mine probably saved me:

I avoid to delete files even when instructed to do so. I prefer to rename then, e. g. by appending .bak to their names and leave them.

I renamed the config file from yesterday or the day before back by removing the .bak, applied all required changes, and viola… this time it worked.

I have the crippled file still there (now the ending. fucked for some forensic investigations I can do when feeling bored one day.

Thanks @piggz for@piggzfor the great work. I will send you some beer, wine as well

Thanks @Fellfrosch for supporting here

1 Like
159

@Fellfrosch if you update again, you should get a new vendor image, please test if it changes anything

160

Holy crap, that was much faster than expected. I will test.

Edit:
New image installed. Unfortunately torch and main camera still out of order. So I guess I have to wait further on. Have you heard someting from the ubports community, regarding this problem? On their forums I haven’t found information. Before I flashed SF I flashed Ubuntu touch and the main cama was working there. Even though I’m not sure if everything worked like expected. If I rrmember correctly, there was not every camera exposed to choose. But I’m not sure if that is by intend or not.