osso-product-info (settings/info) does not reveal version information anymore - maemo.org

Active Topics

Is there a section to talk about Java ME? Apps, etc. (0)
to General by Kalatti - 2 days, 16 hrs ago
Extra softwares in Sailfish using CLI, repositories, etc (117)
to SailfishOS by nieldk - 4 days, 13 hrs ago
Firefox with Leste (6)
to Maemo 7 / Leste by teroyk - 5 days, 10 hrs ago
more...

Thread Tools

	peterleinchen	2013-10-29 , 20:40
	Posts: 4,117 \| Thanked: 8,901 times \| Joined on Aug 2010 @ Ruhrgebiet, Germany	#1

Hi,

I had some (two) strange boot procedures (somehow interrupted and/or looped. But then it was stable again.

IDK if that caused this (just for information):
when selecting product info from system settings panel or using osso-product-info, my N900 does not give me information about installed OS and its version anymore.
This is output from osso-product-info:

Code:

~ $ osso-product-info 
OSSO_PRODUCT_HARDWARE='RX-51'
OSSO_PRODUCT_NAME='N900'
OSSO_PRODUCT_FULL_NAME='Nokia N900'
OSSO_PRODUCT_RELEASE_NAME='<unknown>'
OSSO_PRODUCT_RELEASE_FULL_NAME='<unknown>'
OSSO_PRODUCT_RELEASE_VERSION='<unknown>'
OSSO_PRODUCT_WLAN_CHANNEL='fcc/us'
OSSO_PRODUCT_KEYBOARD='German'
OSSO_PRODUCT_REGION='Germany'
OSSO_PRODUCT_SHORT_NAME='Nokia N900'
OSSO_VERSION='<unknown>'

and picture (only part, as mac of wlan and bt and IMEI are okay):
Name: Screenshot.jpg
Views: 882
Size: 22.2 KB

This is a continuation in its own dedicated thread from here on.
Anybody (except pichlo) also experienced that?
Some solutions?
Or what I would like to know: are there any bad side effects (as I know what OS in which version is installed

)?

Reinstalled already following packages:
osso-product-info
libossoproductinfo0
osso-applet-device
osso-applet-device-l10n-mr0
osso-applet-device-l10n-dede
to no avail.

__________________
SIM-Switcher, automated SIM switching with a Double (Dual) SIM adapter
--
Thank you all for voting me into the Community Council 2014-2016!

Please consider your membership / supporting Maemo e.V. and help to spread this by following/copying this link to your TMO signature:
[MC eV] Maemo Community eV membership application, http://talk.maemo.org/showthread.php?t=94257

editsignature, http://talk.maemo.org/profile.php?do=editsignature

Last edited by peterleinchen; 2013-10-29 at 20:46.

Quote & Reply |

pali	2013-10-29 , 21:15
Posts: 2,153 \| Thanked: 8,462 times \| Joined on May 2010	#2

when you flash any non fiasco image (e.g. kernel) with flasher-3.5 (or 0xFFFF) via usb, then NOLO automatically remove SW version string from CAL.

osso-product-info reading SW version string from CAL and parse it into OSSO_PRODUCT_* variables. If version is missing, it will use '<unknown>'.

So... now you know how this can happen.

Fix is easy, just set correct SW version string into CAL and reboot device. You can use 0xFFFF via usb mode (flasher-3.5 does support it *only* when you do full reflash) or via osso-product-info on device.

PR 1.3.1 Global SW version string is "RX-51_2009SE_21.2011.38-1_PR_MR0"

with 0xFFFF via usb:
$ 0xFFFF -S "RX-51_2009SE_21.2011.38-1_PR_MR0"

with osso-product-info on device:
$ osso-product-info -s OSSO_VERSION="RX-51_2009SE_21.2011.38-1_PR_MR0"

Quote & Reply |

The Following 7 Users Say Thank You to pali For This Useful Post:
fw190, misiak, mrsellout, peterleinchen, pichlo, reinob, sixwheeledbeast

	peterleinchen	2013-10-29 , 21:32
	Posts: 4,117 \| Thanked: 8,901 times \| Joined on Aug 2010 @ Ruhrgebiet, Germany	#3

THANK YOU!
You are really a Maemo god/goodness.

Going to reboot now (batt is flatt, so maybe result tomorrow morning).

Quote & Reply |

pali	2013-10-29 , 21:36
Posts: 2,153 \| Thanked: 8,462 times \| Joined on May 2010	#4

btw, reinstalling metapackage (e.g mp-fremantle-generic-pr or cssu one) should fix it too. See CSSU postinst script: https://gitorious.org/community-ssu/...ebian/postinst

Quote & Reply |

The Following 3 Users Say Thank You to pali For This Useful Post:
peterleinchen, pichlo, sixwheeledbeast

	peterleinchen	2013-10-29 , 21:45
	Posts: 4,117 \| Thanked: 8,901 times \| Joined on Aug 2010 @ Ruhrgebiet, Germany	#5

It made its way up and everything is fine again!
Dziky.

And thanks for more solution possibilities.

I think I know what caused this:
I had my N900 on a PC (Win7 64, I hate it!) with libusb drivers, just to install the drivers and test it (be prepared for possible full reflash). I just read out with "flasher -i", no more. As this is only thing I did, it is the most probable cause. Even I have no clue why?
Other weirdness of "all telephony disabled" and boot loops were possibly just squirks.

Quote & Reply |

« Previous Thread | Next Thread »

Forum Jump

All times are GMT. The time now is 19:58.

Active Topics

Is there a section to talk about Java ME? Apps, etc. (0)

Extra softwares in Sailfish using CLI, repositories, etc (117)

Firefox with Leste (6)