USB OTG Mouse Support and page turn on PW3(possible KV/KOA) - Page 6

knc1 · 09-21-2016, 11:49 AM

Quote:

Originally Posted by lucida

poll/select
enough said.

That should do the trick.
The kernel can suspend and resume while maintaining the state of that.

zxczxc · 09-22-2016, 12:27 PM

Here is a video of the tool I made (that I will share soon when it supports a config file and is a bit nicer)

https://www.youtube.com/watch?v=Ti_KD58UWuc

Thanks for all the help

This is exactly what I wanted!

I will make a thread here when I make it more presentable for the end user.

aconicq1 · 10-30-2016, 09:15 AM

Hi Lucida,
I am trying to get the modules you compiled to work on my PW2 FW5.8.2.1 but they do not work as they are supposed to. The device is not properly recognised as device[2,3] but instead as a mice which has an inappropriate ioctl. Is it possible that the three .ko modules need to be compiled specifically for each device? If so can you please explain how you managed to compile these modules, or perhaps possibly compile these for us to test with? I am so keen to get OTG up and running but I can't find the right information on compiling modules

Many thanks

knc1 · 10-30-2016, 09:23 AM

Modules are kernel version specific.
Interface to them is hardware version specific.

Please provide more information -
What is the kernel version running in that firmware?
What is the kernel message given when you try to load the kernel modules?

aconicq1 · 10-30-2016, 09:37 AM

kernel version: 3.0.35-lab126

dmesg | tail after loading modules:
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
mousedev: PS/2 mouse device common for all mice

knc1 · 10-30-2016, 09:47 AM

Quote:

Originally Posted by aconicq1

kernel version: 3.0.35-lab126

dmesg | tail after loading modules:
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
mousedev: PS/2 mouse device common for all mice

So they load without any error messages.
IIRC - they where built for 3.0.35 but you can check with
modinfo /full/path/and/filename.ko
(full path so you are certain to get the new ones)

What is your starting point with re-compiling the modules?
I.E: Background.

As in:
Have you compiled the kernel and kernel modules for anything before?
What is your working environment (MacOSx, Windoze, Linux, *BSD, other)?
Details like that about what you have to work with.

= = = = =

Since the modules seem to load without any errors, the problem is most likely your model has a different event device ordering than the scripting expects.
This is a load time / run time variation from what is expected.

The current release does not support hotplug, so it can't support u-dev, which means the event devices can't be 'stabilized' by the kernel's auto-loader and supporting software.

Which means the code has to be hand-tweaked per device.

aconicq1 · 10-30-2016, 10:31 AM

Thanks for the quick responses knc1

correct - no error messages when loading modules
modinfo shows the same version, only slight difference is with ARMv7 p2v8 in module but ARMv7 rev 10 (v7l) [full info -> CPU architecture: 7, CPU variant : 0x2, CPU part : 0xc09, CPU revision : 10] in PW2 kernel

My background is limited. I am a novice who can follow instructions well. Never compiled kernel or modules before. I am most comfortable in windows but can use linux competently.

I have been trying to get information from Yifan's webpage but links to cross-compilers are dead and I'm not sure if I have to do all the steps just for the modules. Also most of Christian Hoff's good work on this topic is no longer hosted on the web.

====
In terms of event device ordering, the only device that gets added is the 'mice' which is not properly configured... i.e. when USB is attached and modules started, 'mice' shows in /dev/input, but does not show in cat /proc/bus/input/devices...

So the script does fail and give an error when run because there is no device[2,3].

===
I also get the following message in dmesg that has been discussed previously but I'm not sure what the implications are:
is_otg_connected() 0 audio_enumerated 1

knc1 · 10-30-2016, 11:25 AM

I don't have a PW-2 myself, so sorting out OTG hardware issues will be difficult, but
lets check what we can check:
make a copy of /proc/config.gz and attach it to your next post.

I'll read through that configuration file and see if it has any show-stoppers in it.
- - - - -
Use the 'advanced editor' here (if you are not in the 'advanced editor - there will be a "go advanced" button below this text box -
Scroll past this text entry box and there you will find a 'manage attachments' section.

- - - - -

The PW-2 ***should*** have working OTG.

The references you are reading are very, very out-of-date.

With limited cross-compile experience, I suggest you start out simple - -

Install qemu-static/bin_fmt_misc on your Linux installation.
You didn't mention the Distribution you are running, but nearly all modern versions support that.

With that addition, your Linux box can run ARM code.
I.E: Allow you to do "native builds" under emulation.

Since this may turn into a big chore -

Update your PW-2 to the most recent Amazon firmware release.
If you jail broke it following the directions on this site, your jail break will survive (you will get progress messages from the update bridge code on screen when the newly installed update is first booted).

- - - -

aconicq1 · 10-31-2016, 12:13 AM

Please see copy of /proc/config.gz attached.

I upgraded to latest FW 5.8.5.0.1 with no change.

I have debian running in a VM. I don't understand how if the modules are compiled for the correct kernel there are problems... Suggested further debugging steps would be greatly appreciated.

Please let me know if you find anything or if anyone has managed to get OTG working on PW2

Thanks

aconicq1 · 10-31-2016, 07:11 AM

Perhaps a module is missing or different? Can we compare the available modules and the live modules between the PW2 and PW3?

Here are the modules for the PW2:
# all available modules

Spoiler:

# all live modules when additional .ko files are added from KindleLazy

Spoiler:

knc1 · 10-31-2016, 10:09 AM

Quote:

Originally Posted by aconicq1

Please see copy of /proc/config.gz attached.

I upgraded to latest FW 5.8.5.0.1 with no change.

Broke is broke.
The update suggestion was to increase the time span of what we create, rather than have it break again as soon as you go on-line.

You probably want to install the update blocker directory name on your Kindle.
If you haven't already, see Step #7 of the current jb instructions.

Quote:

Originally Posted by aconicq1

I have debian running in a VM. I don't understand how if the modules are compiled for the correct kernel there are problems... Suggested further debugging steps would be greatly appreciated.

Some modules will be compiled in, some will be external and loadable, some will not be even used.
Those three sets may be different and the differences significant.

Quote:

Originally Posted by aconicq1

Please let me know if you find anything or if anyone has managed to get OTG working on PW2

Thanks

If anyone has, they haven't posted about it here.

Quote:

Originally Posted by aconicq1

Perhaps a module is missing or different? Can we compare the available modules and the live modules between the PW2 and PW3?

Yes, I have the the other models with known working (from Amazon) OTG support and that is part of what I intend to do.

Quote:

Originally Posted by aconicq1

Here are the modules for the PW2:
# all available modules

Spoiler:

# all live modules when additional .ko files are added from KindleLazy

Spoiler:

This is going to turn into a long documentary for people to refer to in the future as we stumble through it the first time.

So any information attached to the posts might be of help to future readers.

Ah,
That also means we get to make our mistakes in public, hope you don't embarrass easily.

Which just means the next reader can read about them, rather than take the time to learn-by-doing them themself.

Running Linux in a VM should not make a difference -
It might slow things down a bit, but it isn't like we will be doing this every day from now on.

Again - Which Linux distribution? Name and version please.
And I do hope you installed a 32-bit flavor of it.

Amazon posts all source code on:
https://www.amazon.com/gp/help/custo...deId=200203720

In your case, this should be the one to work with (paperwhite 6th. generation):
https://s3.amazonaws.com/kindledownl...7510002.tar.gz

I haven't looked at it yet, so I am hoping that Lab126 didn't screw it up - they sometimes do.

hmm...
Debian.
Here is a couple of links to getting ARM code to run under Debian:
https://wiki.debian.org/QemuUserEmulation
https://wiki.debian.org/EmDebian/Cro...strap_approach

They are not specifically for kernel building, but consider them an introduction.
I'll post what I do to set them up (a mix-and-match of both sets of directions).
So for now, those are just background information.

**OUR** end goal will be to install a Debian/Jessie/ARMel system into you Linux VM under (I suppose) Windoze.

Edit: The source above ships the 3.0.35 (rather than the 3.10.53) version the other OTG devices are using.
Do a:
uname -a
on your Kindle to make sure they didn't screw that up.

knc1 · 10-31-2016, 11:18 AM

Hmm...
The PW-3 source code bundle contains the exact same archives of Linux, module-init-tools and multi-touch as the PW-2 does for 5.8.5.0.1

PW-3 - this add-in created for.
PW-2 - the hardware we want it to run on.

So if Lab126 did not screw-up, and include the wrong source code archive in one of those . . . .

hmm...
My PW-3 is still running 5.6.1.1 and I don't want to change that.
I guess I will have to use NiLuJe's PW-3 (which is still disassembled) as an update victim.

So there will be a delay as I finish NiLuJe's PW-3.

And then I need disk space to do all of this comparison stuff - -
Both my 2TB and my 1TB disk arrays are out of service.
The 0.5TB NAS disk array is packed (I have more free space on the Kindles sitting here than on that one).

Expect a few days delay while I re-organize, repair, and generally make everything working again here.

(And then there is the upcoming appointment with my Psychiatrist - if she lets me loose on the streets again. . . .)

knc1 · 10-31-2016, 12:27 PM

Hopes for working hot-plug just hit a speed-bump:

Code:

# CONFIG_USB_ANNOUNCE_NEW_DEVICES is not set

aconicq1 · 11-01-2016, 08:33 AM

Thanks for joining the journey knc1. I haven't been able to do anything today. Will get on it tomorrow. (I did have a 64 bit installation...!)

So as the source code is identical, I take it we are only looking to change the compilation options (in the kbuild file) to try get it working on this harware? Is there anything else involved?

Shame about hotplugging...

knc1 · 11-01-2016, 09:42 AM

Quote:

Originally Posted by aconicq1

Thanks for joining the journey knc1. I haven't been able to do anything today. Will get on it tomorrow. (I did have a 64 bit installation...!)

So as the source code is identical, I take it we are only looking to change the compilation options (in the kbuild file) to try get it working on this harware? Is there anything else involved?

Shame about hotplugging...

It could be how the SoC chip is wired out on the pc board.
Kind of hard to change that on a 4-layer board in the field.

8th gen devices - (kernel: 3.10.53)
KT-3, KOA -
Known not to work, there are people here which would like to see it working.
KOA - No Bluetooth.
KT-3 - Bluetooth. No 3G.

7th gen devices - (kernel: 3.0.35)
KT-2, KV, PW-3
KV -
KT2 - No 3G.
PW-3 - This add-in developed for the PW-3
No Bluetooth.

6th gen devices - (kernel: 3.0.35)
PW-2 - Our target, firmware support for OTG, hardware support un-tested.
No bluetooth.

= = = =

I'll fix up that list above as we go along (Anybody that knows differently, please post here so I can correct that list).

I would like to see general purpose OTG support in all of them, not just support for this add-in.

I would like to see general purpose Bluetooth support in those that support Bluetooth. (One of mine does, and that is enough incentive).

(Hey, if we are going to re-configure and re-build the kernel(s) - why not go for broke? This is not a trivial exercise.

)

09-22-2016, 12:27 PM	#77
zxczxc Addict Posts: 229 Karma: 136002 Join Date: Apr 2013 Device: PW	Here is a video of the tool I made (that I will share soon when it supports a config file and is a bit nicer) https://www.youtube.com/watch?v=Ti_KD58UWuc Thanks for all the help This is exactly what I wanted! I will make a thread here when I make it more presentable for the end user. Last edited by zxczxc; 09-22-2016 at 03:03 PM.

10-31-2016, 07:11 AM	#85
aconicq1 Member Posts: 13 Karma: 29938 Join Date: Feb 2014 Device: pw2	Perhaps a module is missing or different? Can we compare the available modules and the live modules between the PW2 and PW3? Here are the modules for the PW2: # all available modules Spoiler: [root@kindle root]# modprobe -l /lib/modules/3.0.35-lab126/kernel/compat-wireless/net/wireless/cfg80211.ko /lib/modules/3.0.35-lab126/kernel/compat-wireless/drivers/net/wireless/ath/ath6kl/ath6kl_sdio.ko /lib/modules/3.0.35-lab126/kernel/compat-wireless/drivers/net/wireless/ath/ath.ko /lib/modules/3.0.35-lab126/kernel/fs/nls/nls_utf8.ko /lib/modules/3.0.35-lab126/kernel/fs/nls/nls_ascii.ko /lib/modules/3.0.35-lab126/kernel/fs/fuse/fuse.ko /lib/modules/3.0.35-lab126/kernel/drivers/video/mxc/mxc_epdc_fb.ko /lib/modules/3.0.35-lab126/kernel/drivers/net/ppp_generic.ko /lib/modules/3.0.35-lab126/kernel/drivers/net/slhc.ko /lib/modules/3.0.35-lab126/kernel/drivers/net/wan/pkt_monitor.ko /lib/modules/3.0.35-lab126/kernel/drivers/net/wan/mwan.ko /lib/modules/3.0.35-lab126/kernel/drivers/net/ppp_async.ko /lib/modules/3.0.35-lab126/kernel/drivers/usb/host/ehci-hcd.ko /lib/modules/3.0.35-lab126/kernel/drivers/usb/serial/option.ko /lib/modules/3.0.35-lab126/kernel/drivers/usb/serial/usbserial.ko /lib/modules/3.0.35-lab126/kernel/drivers/usb/serial/usb_wwan.ko /lib/modules/3.0.35-lab126/kernel/drivers/usb/otg/fsl_otg_arc.ko /lib/modules/3.0.35-lab126/kernel/drivers/usb/gadget/g_serial.ko /lib/modules/3.0.35-lab126/kernel/drivers/usb/gadget/g_file_storage.ko /lib/modules/3.0.35-lab126/kernel/drivers/usb/gadget/arcotg_udc.ko /lib/modules/3.0.35-lab126/kernel/drivers/usb/gadget/g_ether.ko /lib/modules/3.0.35-lab126/kernel/drivers/misc/mxs-perfmon.ko /lib/modules/3.0.35-lab126/kernel/drivers/input/misc/als_max44009.ko /lib/modules/3.0.35-lab126/kernel/drivers/input/misc/prox_pic12lf1822.ko /lib/modules/3.0.35-lab126/kernel/drivers/input/keyboard/fsr_keypad.ko /lib/modules/3.0.35-lab126/kernel/drivers/input/keyboard/drv26xx_haptics.ko /lib/modules/3.0.35-lab126/kernel/drivers/input/touchscreen/cyttsp4_i2c.ko /lib/modules/3.0.35-lab126/kernel/drivers/input/touchscreen/cyttsp4_loader.ko /lib/modules/3.0.35-lab126/kernel/drivers/input/touchscreen/cyttsp4_device_access.ko /lib/modules/3.0.35-lab126/kernel/drivers/input/touchscreen/cyttsp4_mt_b.ko /lib/modules/3.0.35-lab126/kernel/drivers/input/touchscreen/cyttsp4_core.ko /lib/modules/3.0.35-lab126/kernel/drivers/input/touchscreen/zforce2.ko /lib/modules/3.0.35-lab126/kernel/drivers/input/touchscreen/cyttsp4_debug.ko /lib/modules/3.0.35-lab126/kernel/crypto/tcrypt.ko /lib/modules/3.0.35-lab126/kernel/lib/crc-ccitt.ko /lib/modules/3.0.35-lab126/extra/mxc_epdc_eink.ko # all live modules when additional .ko files are added from KindleLazy Spoiler: [root@kindle root]# cat /proc/modules mousedev 9072 0 - Live 0xbf31f000 usbhid 18029 0 - Live 0xbf316000 hid 67608 1 usbhid, Live 0xbf300000 ath6kl_sdio 197174 0 - Live 0xbf0c5000 cfg80211 170499 1 ath6kl_sdio, Live 0xbf08f000 g_file_storage 35603 0 - Live 0xbf080000 arcotg_udc 26338 1 g_file_storage, Live 0xbf074000 cyttsp4_mt_b 8180 0 - Live 0xbf06e000 cyttsp4_core 41372 2 - Live 0xbf05c000 cyttsp4_i2c 2563 1 - Live 0xbf058000 fuse 60020 2 - Live 0xbf042000 ehci_hcd 53568 0 - Live 0xbf02e000 fsl_otg_arc 15613 3 ehci_hcd, Live 0xbf026000 mxc_epdc_fb 89437 3 - Live 0xbf006000 mxc_epdc_eink 8771 1 mxc_epdc_fb, Live 0xbf000000 (P)

10-31-2016, 11:18 AM	#87
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	Hmm... The PW-3 source code bundle contains the exact same archives of Linux, module-init-tools and multi-touch as the PW-2 does for 5.8.5.0.1 PW-3 - this add-in created for. PW-2 - the hardware we want it to run on. So if Lab126 did not screw-up, and include the wrong source code archive in one of those . . . . hmm... My PW-3 is still running 5.6.1.1 and I don't want to change that. I guess I will have to use NiLuJe's PW-3 (which is still disassembled) as an update victim. So there will be a delay as I finish NiLuJe's PW-3. And then I need disk space to do all of this comparison stuff - - Both my 2TB and my 1TB disk arrays are out of service. The 0.5TB NAS disk array is packed (I have more free space on the Kindles sitting here than on that one). Expect a few days delay while I re-organize, repair, and generally make everything working again here. (And then there is the upcoming appointment with my Psychiatrist - if she lets me loose on the streets again. . . .) Last edited by knc1; 10-31-2016 at 11:23 AM.

10-31-2016, 12:27 PM	#88
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	Hopes for working hot-plug just hit a speed-bump: Code: # CONFIG_USB_ANNOUNCE_NEW_DEVICES is not set

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Tools Software Jailbreak for PW2, PW3, PW3W, KT2, KV, KOA and KT3	knc1	Kindle Developer's Corner	3376	05-31-2023 09:43 AM
USB device to turn the page	arnicas	Kindle Developer's Corner	23	02-20-2017 01:20 PM
CC and USB/OTG support	GEB	Calibre Companion	2	05-30-2015 12:24 PM
ebook android readers and usb host - otg support	sasimako	Which one should I buy?	4	02-18-2015 06:26 AM
USB OTG	Mythic	Bookeen	7	11-11-2007 12:39 PM

10-30-2016, 09:15 AM	#78
aconicq1 Member Posts: 13 Karma: 29938 Join Date: Feb 2014 Device: pw2	Hi Lucida, I am trying to get the modules you compiled to work on my PW2 FW5.8.2.1 but they do not work as they are supposed to. The device is not properly recognised as device[2,3] but instead as a mice which has an inappropriate ioctl. Is it possible that the three .ko modules need to be compiled specifically for each device? If so can you please explain how you managed to compile these modules, or perhaps possibly compile these for us to test with? I am so keen to get OTG up and running but I can't find the right information on compiling modules Many thanks

10-30-2016, 09:23 AM	#79
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	Modules are kernel version specific. Interface to them is hardware version specific. Please provide more information - What is the kernel version running in that firmware? What is the kernel message given when you try to load the kernel modules?

10-30-2016, 09:37 AM	#80
aconicq1 Member Posts: 13 Karma: 29938 Join Date: Feb 2014 Device: pw2	kernel version: 3.0.35-lab126 dmesg \| tail after loading modules: usbcore: registered new interface driver usbhid usbhid: USB HID core driver mousedev: PS/2 mouse device common for all mice

10-30-2016, 10:31 AM	#82
aconicq1 Member Posts: 13 Karma: 29938 Join Date: Feb 2014 Device: pw2	Thanks for the quick responses knc1 correct - no error messages when loading modules modinfo shows the same version, only slight difference is with ARMv7 p2v8 in module but ARMv7 rev 10 (v7l) [full info -> CPU architecture: 7, CPU variant : 0x2, CPU part : 0xc09, CPU revision : 10] in PW2 kernel My background is limited. I am a novice who can follow instructions well. Never compiled kernel or modules before. I am most comfortable in windows but can use linux competently. I have been trying to get information from Yifan's webpage but links to cross-compilers are dead and I'm not sure if I have to do all the steps just for the modules. Also most of Christian Hoff's good work on this topic is no longer hosted on the web. ==== In terms of event device ordering, the only device that gets added is the 'mice' which is not properly configured... i.e. when USB is attached and modules started, 'mice' shows in /dev/input, but does not show in cat /proc/bus/input/devices... So the script does fail and give an error when run because there is no device[2,3]. === I also get the following message in dmesg that has been discussed previously but I'm not sure what the implications are: is_otg_connected() 0 audio_enumerated 1

10-30-2016, 11:25 AM	#83
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	I don't have a PW-2 myself, so sorting out OTG hardware issues will be difficult, but lets check what we can check: make a copy of /proc/config.gz and attach it to your next post. I'll read through that configuration file and see if it has any show-stoppers in it. - - - - - Use the 'advanced editor' here (if you are not in the 'advanced editor - there will be a "go advanced" button below this text box - Scroll past this text entry box and there you will find a 'manage attachments' section. - - - - - The PW-2 *should* have working OTG. The references you are reading are very, very out-of-date. With limited cross-compile experience, I suggest you start out simple - - Install qemu-static/bin_fmt_misc on your Linux installation. You didn't mention the Distribution you are running, but nearly all modern versions support that. With that addition, your Linux box can run ARM code. I.E: Allow you to do "native builds" under emulation. Since this may turn into a big chore - Update your PW-2 to the most recent Amazon firmware release. If you jail broke it following the directions on this site, your jail break will survive (you will get progress messages from the update bridge code on screen when the newly installed update is first booted). - - - -

11-01-2016, 08:33 AM	#89
aconicq1 Member Posts: 13 Karma: 29938 Join Date: Feb 2014 Device: pw2	Thanks for joining the journey knc1. I haven't been able to do anything today. Will get on it tomorrow. (I did have a 64 bit installation...!) So as the source code is identical, I take it we are only looking to change the compilation options (in the kbuild file) to try get it working on this harware? Is there anything else involved? Shame about hotplugging...

Advert

Advert