MobileRead Forums - View Single Post

DonTomme · 12-10-2013, 09:50 AM

Hi there, sorry for the late reply but I became a dad in the meantime ;-)

Where can I check my firmware version? I am using an unregistered Kobo Mini so I never got into the real user menu. This is my linux version: Linux version 2.6.35.3-850-gbc67621+ (gallen@gallen-P5KPL-AM-BM) (gcc version 4.4.4 (4.4.4_09.06.2010) ) #617 PREEMPT Mon Apr 22 11:07:47 CST 2013
That seems to be the same kernel as yours.

But: How do I do a real firmware downgrade?
I read that the Kobo actually is not downgradable. I tried two different update packages from the firmware thread but they both locked down the Kobo during boot. One of them was 2.1.4 I think. Am I missing another source for firmware files?

I tested rtcwake with different modifications of this script via nohup sleeptest.sh >> test.log &:

Code:

echo 1 > /sys/power/state-extended
sh /mnt/weather/wifi-down.sh
/mnt/weather/busybox_kobo rtcwake -a -s 30 -m mem
sh /mnt/weather/wifi-up.sh
zcat /mnt/weather/moon.raw.gz | /usr/local/Kobo/pickel showpic

I used different options for rtcwake (-a, -u, -l) but nothing worked. It never refreshed the screen, came up with telnet or wrote something to the logfile.

I think this could be important:
What I also did in my desperation was to compile an rtc testing binary (on my ARM NAS) from the official rtc documentation and ran it on the Kobo: https://www.kernel.org/doc/Documentation/rtc.txt (source at the end of the file).
This is what it tested and what did and did not work:

Test the availability of an RTC device: works
Read the current time from RTC: works
Set an alarm (+5 seconds): seems to work
Read the alarm time: always gives 00:00:00
Wait for the alarm: never fires

So because that testing binary uses ioctl() to set the alarm, there can only be an issue either with the kernel/rtc-driver or with the hardware itself.

12-10-2013, 09:50 AM	#69
DonTomme Junior Member Posts: 3 Karma: 10 Join Date: Nov 2013 Device: Kobo Mini	Hi there, sorry for the late reply but I became a dad in the meantime ;-) Where can I check my firmware version? I am using an unregistered Kobo Mini so I never got into the real user menu. This is my linux version: Linux version 2.6.35.3-850-gbc67621+ (gallen@gallen-P5KPL-AM-BM) (gcc version 4.4.4 (4.4.4_09.06.2010) ) #617 PREEMPT Mon Apr 22 11:07:47 CST 2013 That seems to be the same kernel as yours. But: How do I do a real firmware downgrade? I read that the Kobo actually is not downgradable. I tried two different update packages from the firmware thread but they both locked down the Kobo during boot. One of them was 2.1.4 I think. Am I missing another source for firmware files? I tested rtcwake with different modifications of this script via nohup sleeptest.sh >> test.log &: Code: echo 1 > /sys/power/state-extended sh /mnt/weather/wifi-down.sh /mnt/weather/busybox_kobo rtcwake -a -s 30 -m mem sh /mnt/weather/wifi-up.sh zcat /mnt/weather/moon.raw.gz \| /usr/local/Kobo/pickel showpic I used different options for rtcwake (-a, -u, -l) but nothing worked. It never refreshed the screen, came up with telnet or wrote something to the logfile. I think this could be important: What I also did in my desperation was to compile an rtc testing binary (on my ARM NAS) from the official rtc documentation and ran it on the Kobo: https://www.kernel.org/doc/Documentation/rtc.txt (source at the end of the file). This is what it tested and what did and did not work: Test the availability of an RTC device: works Read the current time from RTC: works Set an alarm (+5 seconds): seems to work Read the alarm time: always gives 00:00:00 Wait for the alarm: never fires So because that testing binary uses ioctl() to set the alarm, there can only be an issue either with the kernel/rtc-driver or with the hardware itself.