Kobo Start Menu 09

[davidfor]

Originally Posted by cvarrick

The affiliate is "Kobo".

Of topic by a bit, but are you a calibre user? If so, does calibre detect your device properly? You Aura H2O2 doesn't seem to be the same as others that have been seen here, so we are interested in finding out what is going on.

[tshering]

Originally Posted by cvarrick

Right now I am using web interface via wifi, haven't been able to get usbnet to work but that may be an issue with the host machine (Arch Linux).

Sorry, I should have known. KSM does not even try to enable usbnet on your device. Could you please tell me which files there are in /drivers/$PLATFORM/usb/gadget?

Originally Posted by cvarrick

At one point I did sideload the latest firmware, but subsequent factory resets seem to have removed that. Current FW is 4.6.10197 and device does not see any updates available.

From your first post I did not understand that you sideloaded the firmware. Therefore, I asked for the affiliate. Now everything is clear.

[geek1011]

Originally Posted by cvarrick

The affiliate is "Kobo".

Does sync work? I cannot seem to be able to check for updates.

Also, I will take a look in the firmware to see if I can find anything.

[tshering]

Originally Posted by geek1011

Does sync work? I cannot seem to be able to check for updates.

What do you mean by that? The response to a query is that there is no update available. So there is no obstacle to sync.

[cvarrick]

Originally Posted by davidfor

Of topic by a bit, but are you a calibre user? If so, does calibre detect your device properly? You Aura H2O2 doesn't seem to be the same as others that have been seen here, so we are interested in finding out what is going on.

I don't believe it does. I have installed the Kobo Utilities plugin and tried both the "main" and "extended" drivers but the "Devices" tab list is empty and the buttons disabled.

Copying to the device works fine but I'm guessing that simply relies on the USB storage being mounted.

[geek1011]

I have looked around a bit in the firmware and can confirm 378 is a device. It is in the strings along with mx6sll-ntx. There is also a Device::isSnow function. I will post more when I have more time to look at the disassembly of the iMX6Netronix::usbProductId function. There are also some embedded resources referencing snow.

I have also tried to brute-force the firmware download url, as it would reveal the hardware revision and a few other useful things. I have tried from kobo 0-9 and Jan2016 to April2018. I have not succeeded.

Originally Posted by tshering

What do you mean by that? The response to a query is that there is no update available. So there is no obstacle to sync.

If you check with the fw version 0.0, it should return the latest version as UpgradeType 3. It is how my firmware downloader works.

[geek1011]

Originally Posted by cvarrick

I don't believe it does. I have installed the Kobo Utilities plugin and tried both the "main" and "extended" drivers but the "Devices" tab list is empty and the buttons disabled.

Copying to the device works fine but I'm guessing that simply relies on the USB storage being mounted.

Can you post a dir list of the kobo device? On windows, it is:

DIR /S /B E:

where E: is the drive letter for the kobo. On linux, it is:

find /path/to/kobo/mount

On macOS, it is:

find /Volumes/KOBOeReader

[cvarrick]

Originally Posted by tshering

Sorry, I should have known. KSM does not even try to enable usbnet on your device. Could you please tell me which files there are in /drivers/$PLATFORM/usb/gadget?

### executed: ls -l /drivers/$PLATFORM/usb/gadget

Spoiler:

total 482
-rw-r--r--    1 root     root         40904 Nov 20 08:13 configfs.ko
-rw-r--r--    1 root     root         13636 Nov 20 08:13 g_ether.ko
-rw-r--r--    1 root     root         13140 Nov 20 08:13 g_file_storage.ko
-rw-r--r--    1 root     root         13140 Nov 20 08:13 g_mass_storage.ko
-rw-r--r--    1 root     root         10484 Nov 20 08:13 g_ncm.ko
-rw-r--r--    1 root     root         10956 Nov 20 08:13 g_serial.ko
-rw-r--r--    1 root     root         14472 Nov 20 08:13 g_zero.ko
-rw-r--r--    1 root     root         26212 Nov 20 08:13 gadgetfs.ko
-rw-r--r--    1 root     root         61960 Nov 20 08:13 libcomposite.ko
-rw-r--r--    1 root     root         21476 Nov 20 08:13 u_ether.ko
-rw-r--r--    1 root     root         18088 Nov 20 08:13 u_serial.ko
-rw-r--r--    1 root     root         11564 Nov 20 08:13 usb_f_acm.ko
-rw-r--r--    1 root     root         14876 Nov 20 08:13 usb_f_ecm.ko
-rw-r--r--    1 root     root         12336 Nov 20 08:13 usb_f_ecm_subset.ko
-rw-r--r--    1 root     root         14072 Nov 20 08:13 usb_f_eem.ko
-rw-r--r--    1 root     root         38512 Nov 20 08:13 usb_f_fs.ko
-rw-r--r--    1 root     root         56708 Nov 20 08:13 usb_f_mass_storage.ko
-rw-r--r--    1 root     root         22100 Nov 20 08:13 usb_f_ncm.ko
-rw-r--r--    1 root     root          9708 Nov 20 08:13 usb_f_obex.ko
-rw-r--r--    1 root     root         28232 Nov 20 08:13 usb_f_rndis.ko
-rw-r--r--    1 root     root          8564 Nov 20 08:13 usb_f_serial.ko
-rw-r--r--    1 root     root         21788 Nov 20 08:13 usb_f_ss_lb.ko

If it is of any use, here is the dmesg output:

https://pastebin.com/ZhRhj5nz

[cvarrick]

Originally Posted by geek1011

Can you post a dir list of the kobo device? On windows, it is:

DIR /S /B E:

where E: is the drive letter for the kobo. On linux, it is:

find /path/to/kobo/mount

On macOS, it is:

find /Volumes/KOBOeReader

It basically looks like this (I have omitted some things - installed books , the stuff KSM installs, etc)

Spoiler:

|── .adobe-digital-editions
│** └── device.xml
├── .driveinfo.calibre
├── driveinfo.calibre
├── .kobo
│** ├── affiliate.conf
│** ├── BookReader.sqlite
│** ├── certificates
│** ├── device.salt.conf
│** ├── dict
│** │** ├── dicthtml-de-en.zip
│** │** ├── dicthtml-es-en.zip
│** │** ├── dicthtml-fr-en.zip
│** │** ├── dicthtml-it-en.zip
│** │** ├── dicthtml-pt-en.zip
│** │** └── dicthtml.zip
│** ├── guide
│** │** └── userguide.pdf
│** ├── kepub
│** ├── Kobo
│** │** ├── Analytics.conf
│** │** └── Kobo eReader.conf
│** ├── KoboReader.sqlite
│** └── version
├── .kobo-images

Is there something specific you are interested in?

[davidfor]

Originally Posted by cvarrick

I don't believe it does. I have installed the Kobo Utilities plugin and tried both the "main" and "extended" drivers but the "Devices" tab list is empty and the buttons disabled.

Copying to the device works fine but I'm guessing that simply relies on the USB storage being mounted.

We probably should take this to another thread. But...

Can you run the device detection and send me the log? See the last step in https://www.mobileread.com/forums/sh...d.php?t=118560.

And, what version of calibre are you running? There was a change in 3.20 that might solve it.

[cvarrick]

Originally Posted by davidfor

We probably should take this to another thread. But...

Can you run the device detection and send me the log? See the last step in https://www.mobileread.com/forums/sh...d.php?t=118560.

And, what version of calibre are you running? There was a change in 3.20 that might solve it.

EDIT: Running 3.20.0
My apologies, it does work now. Going to Preferences -> Plugins -> Kobo Utilities allowed me to add the device.

In the past I had been clicking on the Kobo Utilities toolbar icon which I assumed was a shortcut to the same interface (It looks identical).

I had also never run "Get information to setup the user defined device". I didn't do anything with the output but the one or both of these things results in it working.

[geek1011]

delete post

[davidfor]

Originally Posted by cvarrick

PRODUCT=snow, PRODUCT_ID=unknown, CPU=mx6sll, PLATFORM=mx6sll-ntx,
WIFI_MODULE=8189fs, WIFI_MODULE_PATH=/drivers/mx6sll-ntx/wifi/8189fs.ko
uname=Linux (none) 4.1.15-00104-gcd6a6a6 #9 SMP PREEMPT Wed Nov 15 15:40:03 CST 2017 armv7l GNU/Linux, FW=4.6.10197

I can see that PRODUCT_ID is set by getmodelnr.sh which reads /mnt/onboard/.kobo/version, which is this:

N867xx2xxxxx,4.1.15,4.6.10197,4.1.15,4.1.15,00000000-0000-0000-0000-000000000378

So PRODUCT_ID = 378

Because of the differences identified here, I asked Kobo on the beta list to about what was happening.

They have done an update to the hardware for both the Aura H2O Edition 2 and the Aura Edition 2. The update is to change the CPU. The CPU in them is the i.MX 6SLL. Support for these CPUs was added in the 4.6.x firmware.

There doesn't appear to be anything about packaging that shows which version it is, but the serial number can tell you. In this, 7th character of the serial number will be a 0 for the first version and 2 for the updated version. To identify them when connected, the product id of 378 is for the Aura H2O Edition 2 Version 2 and 379 for the Aura Edition 2 Version 2. In the USB identifiers, the value of BCD has changed to "0x401". This was reported by calibre users as calibre was connecting to some devices. The new BCD value was added in calibre v3.20.

The only firmware released for them is the factory firmware. This should be 4.6.10197. This will be updated with the next firmware release. The updates won't be in the Mark6 package. I don't know if it will be a mark7 package or something else. The main difference for the package will be the kernel. It was updated for the new CPU. And Kobo have advised not to install the Mark6 package on these devices.

I'm assuming the Clara HD will use the same CPU, but, I don't know for sure. The Kobo employees on the beta list seem to like to tease me whenever I ask about new devices.

If I hear anything else, I'll do an update.

[geek1011]

Originally Posted by davidfor

Because of the differences identified here, I asked Kobo on the beta list to about what was happening.

They have done an update to the hardware for both the Aura H2O Edition 2 and the Aura Edition 2. The update is to change the CPU. The CPU in them is the i.MX 6SLL. Support for these CPUs was added in the 4.6.x firmware.

There doesn't appear to be anything about packaging that shows which version it is, but the serial number can tell you. In this, 7th digit of the serial number will be a 0 for the first version and 2 for the updated version. To identify them when connected, the product id of 378 is for the Aura H2O Edition 2 Version 2 and 379 for the Aura Edition 2 Version 2. In the USB identifiers, the value of BCD has changed to "0x401". This was reported by calibre users as calibre was connecting to some devices. The new BCD value was added in calibre v3.20.

The only firmware released for them is the factory firmware. This should be 4.6.10197. This will be updated with the next firmware release. The updates won't be in the Mark6 package. I don't know if it will be a mark7 package or something else. The main difference for the package will be the kernel. It was updated for the new CPU. And Kobo have advised not to install the Mark6 package on these devices.

I'm assuming the Clara HD will use the same CPU, but, I don't know for sure. The Kobo employees on the beta list seem to like to tease me whenever I ask about new devices.

If I hear anything else, I'll do an update.

Sounds good. I'll try to figure out if it is a mark 7 by looking through the assembly. Can cvarrick send me a copy of libnickel.so.1.0.0 so I can have a look and compare it with the other copies?

I'll also add a note to my kobo firmware downloader warning users who have fw 4.6.10197. Someone should update the wiki page. Also, I finished my rewrite for my firmware downloader. The link is below.

[davidfor]

Originally Posted by geek1011

Sounds good. I'll try to figure out if it is a mark 7 by looking through the assembly. Can cvarrick send me a copy of libnickel.so.1.0.0 so I can have a look and compare it with the other copies?

You don't need to. The way Kobo builds the firmware, anything in the libnickel version for 4.6.10197 will be in 4.7.10413. The bit you will be missing is the kernel.

The build number points suggests the firmware was built in Mid November. It would be good to get the actual date from the device info screen.

I'll also add a note to my kobo firmware downloader warning users who have fw 4.6.10197. Someone should update the wiki page. Also, I finished my rewrite for my firmware downloader. The link is below.

The WiKi does need to be updated. I might try tonight, but more likely on the weekend. But, if someone else wants to...