Libra 2 Very unstable Libra 2 with 4.33.19611 - Page 4

rtiangha · 06-24-2022, 06:48 PM

If you have access to the command line (telnet, ssh, koreader plugin, etc), you could run the command in my last post. Otherwise, I'm not sure what's easily accessible. Maybe there's something identifiable on the box?

And the entire point of getting people to post their hardware revision along with if they're having issues or not would be to see if there really is a difference.

PeterT · 06-24-2022, 08:27 PM

Just add the command to your NickleMenu config, redirecting output to a file

Sent from my Pixel 4a using Tapatalk

Sirtel · 06-25-2022, 04:46 AM

Quote:

Originally Posted by PeterT

Just add the command to your NickleMenu config, redirecting output to a file

Sent from my Pixel 4a using Tapatalk

I don't use NickelMenu or KOReader, nor do I have access to command line. The box was thrown out long ago. So no way to ascertain the hardware version then?

frostschutz · 06-25-2022, 04:55 AM

Quote:

Originally Posted by Sirtel

I don't use NickelMenu or KOReader, nor do I have access to command line. The box was thrown out long ago. So no way to ascertain the hardware version then?

With any luck the serial number alone will be sufficient... but we don't know yet, takes a brave soul to post detailed pictures and perhaps even pop off the back cover for a PCB picture.

Anyone who has had their Libra 2 for a while will be on the old revision though, as that seems to have surfaced only very recently...

Sirtel · 06-25-2022, 05:10 AM

Quote:

Originally Posted by frostschutz

With any luck the serial number alone will be sufficient... but we don't know yet, takes a brave soul to post detailed pictures and perhaps even pop off the back cover for a PCB picture.

Anyone who has had their Libra 2 for a while will be on the old revision though, as that seems to have surfaced only very recently...

I've had mine since November.

I wonder if there's a difference between black and white Libras? Mine is black.

npr · 06-25-2022, 05:46 AM

Looks like my Libra 2 is the older version.

42] PCB_LVL='B'
[43] HOME_LED_PWM='No'
[44] PMIC='RC5T619'
[45] FL_PWM='LM3630'
[46] RTC='RC5T619'

White model, purchased April 2022.
Not having any significant issues.

frostschutz · 06-25-2022, 06:24 AM

So there is a PCB_LVL='B' too... interesting. Oh well, it's not like I can change my device anyway.

That's assuming the new revisions actually improve things and not just due to availability/price of some of the parts...

rtiangha · 06-25-2022, 10:00 AM

Quote:

Originally Posted by PeterT

Just add the command to your NickleMenu config, redirecting output to a file

Ah, good point. Something like this, then:

Code:

menu_item :main    :ntx_hwconfig    :cmd_spawn    :quiet:/bin/ntx_hwconfig -s /dev/mmcblk0
 > /mnt/onboard/ntx_output.txt

rtiangha · 06-25-2022, 10:07 AM

Quote:

Originally Posted by frostschutz

So there is a PCB_LVL='B' too... interesting. Oh well, it's not like I can change my device anyway.

I guess there are at least five of them if that 'E' is to be believed.

Quote:

That's assuming the new revisions actually improve things and not just due to availability/price of some of the parts...

Yeah, that was I was thinking. Supply chain issues may have forced them to source different parts. Hopefully all of these issues can be fixed in software. I really was eyeing one of these to replace my Glo HD, although I wonder if I should wait for the Clara's successor instead before deciding.

davidfor · 06-25-2022, 10:46 AM

Quote:

Originally Posted by rtiangha

I guess there are at least five of them if that 'E' is to be believed.

But, they might not all have been released.

Quote:

Yeah, that was I was thinking. Supply chain issues may have forced them to source different parts. Hopefully all of these issues can be fixed in software.

It appears to be IC shortages. And hopefully it is fixable in software.

DNSB · 06-25-2022, 11:38 AM

Quote:

Originally Posted by rtiangha

Ah, good point. Something like this, then:

Code:

menu_item :main    :ntx_hwconfig    :cmd_spawn    :quiet:/bin/ntx_hwconfig -s /dev/mmcblk0
 > /mnt/onboard/ntx_output.txt

Worked on my Sage. Ran the item and then ran import books. Mulitple pages of interesting and uninteresting information.

Deobulakenyo · 06-25-2022, 10:33 PM

Quote:

Originally Posted by npr

Looks like my Libra 2 is the older version.

42] PCB_LVL='B'
[43] HOME_LED_PWM='No'
[44] PMIC='RC5T619'
[45] FL_PWM='LM3630'
[46] RTC='RC5T619'

White model, purchased April 2022.
Not having any significant issues.

Mine is

42] PCB_LVL='A'

Had issues before. after removing nanoclock, everything is fine

davidfor · 06-26-2022, 10:23 PM

Quote:

Originally Posted by Rkob

I noticed that the device generated some stack traces (.kobo/stack_*.log), which indicate Segmentation Faults (SIGSEGV) in the nickel process.

For the record, if possible, the device will upload the stack trace logs to Kobo. They do look at them. This should happen if you have the option turned on to share data (last option on the "Energy saving and privacy" page of the settings), the device is signed into a Kobo account (ie. not in sideloaded mode or using DB hack to bypass registration) and WiFi is on.

And I did talk to someone at Kobo about this. He reminded me of the above. Their problem at the moment is that the information they have is basically, "it crashed". They have not seen any steps to reproduce it yet. At the moment, all they can see is, "it crashes".

Barty · 06-27-2022, 02:07 PM

Quote:

Originally Posted by davidfor

For the record, if possible, the device will upload the stack trace logs to Kobo. They do look at them. This should happen if you have the option turned on to share data (last option on the "Energy saving and privacy" page of the settings), the device is signed into a Kobo account (ie. not in sideloaded mode or using DB hack to bypass registration) and WiFi is on.

And I did talk to someone at Kobo about this. He reminded me of the above. Their problem at the moment is that the information they have is basically, "it crashed". They have not seen any steps to reproduce it yet. At the moment, all they can see is, "it crashes".

It would help if following a crash the device pops up a message that says "it looks like your Kobo just crashed. Would you like to send the log to tech support to help us diagnose and fix the problem?"

Rkob · 07-03-2022, 09:03 AM

A sort of epilogue to this thread.

I returned my original Libra 2 and got a new one earlier this week.
It's a completely different experience!
While the previous Libra 2 was unstable to the point of being almost unusable, the new one has been extremely stable: not a single crash or freeze in the 5 days I've used it.
I tried with both 4.32 and the latest 4.33.

⇒ The conclusion is that I probably had a FW device the first time (RAM or flash).

Thanks to everyone who commented and gave advice in this thread. 😊

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Firmware 4.33.19611	geek1011	Kobo Reader	73	07-06-2022 06:37 AM
Instructions for patching firmware 4.33.19611	geek1011	Kobo Developer's Corner	12	06-29-2022 05:01 PM
Aura H2O Unstable system	Apofis	Kobo Developer's Corner	6	07-07-2017 02:49 AM
IQ Pocketbook unstable regardless of what I try	ebookof	PocketBook	9	11-08-2011 04:22 AM
6.12 Unstable	jquest	Calibre	9	09-15-2009 11:57 AM

06-24-2022, 06:48 PM	#46
rtiangha Evangelist Posts: 495 Karma: 356531 Join Date: Jul 2016 Location: 'burta, Canada Device: Kobo Glo HD	If you have access to the command line (telnet, ssh, koreader plugin, etc), you could run the command in my last post. Otherwise, I'm not sure what's easily accessible. Maybe there's something identifiable on the box? And the entire point of getting people to post their hardware revision along with if they're having issues or not would be to see if there really is a difference.

06-24-2022, 08:27 PM	#47
PeterT Grand Sorcerer Posts: 13,540 Karma: 78910202 Join Date: Nov 2007 Location: Toronto Device: Libra H2O, Libra Colour	Just add the command to your NickleMenu config, redirecting output to a file Sent from my Pixel 4a using Tapatalk

06-25-2022, 05:46 AM	#51
npr Zealot Posts: 119 Karma: 37418 Join Date: Jan 2013 Device: H2OE2, Libra 2	Looks like my Libra 2 is the older version. 42] PCB_LVL='B' [43] HOME_LED_PWM='No' [44] PMIC='RC5T619' [45] FL_PWM='LM3630' [46] RTC='RC5T619' White model, purchased April 2022. Not having any significant issues.

06-25-2022, 06:24 AM	#52
frostschutz Linux User Posts: 2,282 Karma: 6123806 Join Date: Sep 2010 Location: Heidelberg, Germany Device: none	So there is a PCB_LVL='B' too... interesting. Oh well, it's not like I can change my device anyway. That's assuming the new revisions actually improve things and not just due to availability/price of some of the parts...

07-03-2022, 09:03 AM	#60
Rkob Reader Posts: 7 Karma: 10 Join Date: Jun 2022 Device: Kobo Libra 2	A sort of epilogue to this thread. I returned my original Libra 2 and got a new one earlier this week. It's a completely different experience! While the previous Libra 2 was unstable to the point of being almost unusable, the new one has been extremely stable: not a single crash or freeze in the 5 days I've used it. I tried with both 4.32 and the latest 4.33. ⇒ The conclusion is that I probably had a FW device the first time (RAM or flash). Thanks to everyone who commented and gave advice in this thread. 😊