PW2 App/tools compatibility thread

[twobob]

Heh - fair point I should add "By Me" Ill link that one from the main thread :P

[Mike76]

CoolReader works on PW2 (fw 5.4.0, SO, wifi-only).

[cryzed]

After applying the new Jailbreak and installing the latest USBNet version I get the error message: "N E failed to set usb0 ip, this is bad" during a restart of the device. (USBNet is set to auto)

My config looks like this:

KINDLE_IP=192.168.15.244
USE_WIFI="true"
USE_WIFI_SSHD_ONLY="false"
USE_OPENSSH="true"
TWEAK_MAC_ADDRESS="false"

[smstone2006]

Originally Posted by NiLuJe

Yes it has ;P.

Successfully，Thanks！

[NiLuJe]

@cryzed: Define 'latest' (there's a shiny KUAL button just for that in the snapshots).

Also: make sure your Kindle is completely *unplugged* during the (re)boot process.

[cryzed]

KUAL, Snapshots? I am not using KUAL, nor am I using a snapshot version. When you said "USBNet & LinkSS (snapshots) will work.", I assumed you were only talking about the snapshot version of LinkSS and not USBNet. As it stands I'm using the version linked here (USBNetwork v0.14.N).

When I restarted the device everything was unplugged, there was no cable attached -- same error. Where can I find the USBNetwork snapshot version in that case? Also using KUAL is possible with the Paperwhite 2 already? I never used it before, to be quite honest. I'm sorry, it seems I'm a bit misinformed.

EDIT: I think you might have meant this. I tried the "kindle-usbnet-0.14.N-r10129.tar.xz", after uninstalling the old one. After entering ";un" it takes a while, and then says "N E failed to set usb0 to ip, this is bad"; I can ssh into the device without problems afterwards though. I'm running the 5.4.2 firmware.

[twobob]

yeah. it can be a slow to notice you have unplugged the cable.

Keep an eye on the charging indicator. until it reverts from the battery symbol it still "thinks" it is plugged in.

Could be that?

EDIT: and by slow sometimes I mean a ridiculously long time. never did figure out why.

And yes the KUAL thread has been updated to be PWII compliant now.

[cryzed]

Hey there twobob, that is unfortunately not it. What happens is:
1) I boot with USBNet disabled
2) Optionally I unplug any cables attached to the Kindle
3) I wait until the normal battery gauge shows
4) I then enter ";un" into the search bar
5) After about 5 seconds I get the error message at the bottom of the screen and curiously my battery gauge changes for a short while to the charging icon, and after a few seconds back to the normal battery gauge again.

I hope I'm not the only one with this problem, and it is reproducible. I would of course be willing to install a debug version of the USBNet plugin, and share logs etc. to find the bug. Although I am not exactly sure what problems could arise if I just ignore the problem -- possibly that I can't SSH to the device over USB?

[twobob]

interesting. it's probably just a timing glitch. doubtless when Nliuje gets his greasy mitts on an honest to goodness device this will all turn out to be yet more funky powerd (or something) craziness to be worked around.

As you have noted in this instance the warning is harmless. if annoying.
The kindle 4 did some similar crazy stuff back in it's day too..

[knc1]

Originally Posted by cryzed

2) Optionally I unplug any cables attached to the Kindle

Not optional.

You are changing device drivers installed in the kernel, that can not be done reliably with the driver in-use.

[cryzed]

@twobob: thanks for the reassurances and help.

@knc1: by optional I meant: "If there is any cable attached to the device, I remove it." -- There definitely isn't or wasn't, at any point. Even before the restart.

[knc1]

Ok - was not the way I read it.

Yes - that message has appeared before in other Models, other firmware Versions.
It can probably be fixed.

best practice -
use the KUAL buttons -
watch the battery indicator -

it will change to the 'charging' icon while re-configuring the Kernel - -
an obvious lie, since no cables are attached.

when it changes back to the 'on battery' icon - its done.

[cryzed]

Alright, I'll do that, thank you.

EDIT: There are a few bugs though...
1) I can't properly toggle the addon (it keeps saying it is enabled)
2) When I then try to manually do it via ";un" it seems to work at first, it switches into the USB mode and I can attach it to the PC, but then it suddenly switches back -- causing the device to "eject", and get stuck at the USB Mode screen until I force a restart.

I just thought I'd mention that.

[NiLuJe]

@cryzed: Uninstall, wipe the usbnet folder manually, then reinstall (the snapshot version), and do not touch the config.

Check if it works over USB that way.

The warning is (usually) somewhat harmless if you use the default IPs, besides eating 15s of your time, but it isn't if you don't .

You might have a mangled config (because of the first install with a release not actually supporting the PW2).

That, or volumd got funky in 5.4.2, but I think others have it working on 5.4.2, so hopefully it's just a roundabout form of PEBKAC.

EDIT: Wait, scratch that, I forgot that I updated the stable USBNet release with the JailBreak. The gist of this post is still somewhat valid, but you don't necessarily have to go with the snapshots, as long as you're using USBNet >= 0.14.N.

[cryzed]

Gonna try that, although I doubt it was me. It might be that the KUAL extension doesn't work properly when using a manually modified config, and it keeps track of the changes made to it itself?

EDIT: I uninstalled the revision version, removed the usbnet folder, even the extension folder just in case there was something funky with it. Then I reinstalled the extension, added my authorized_keys, and am currently trying to toggle it properly without success. So yeah, I doubt it's PEBKAC somehow, unless I'm doing something very stupid. By "without success" I mean that I can enable it, but not disable it again afterwards, although if I try disabling it, it "breaks" i.e. I can't connect anymore (timeout) or properly re-activate it, unless I restart.

If I enable verbose mode and try to toggle it, the last message displayed (maybe keeps getting stuck at?) is "N stopping sshd". Scratch that, I changed the sshd to OpenSSH, it gets stuck at "N restoring iptables config", well at least it's the last message displayed without being changed for quite a while.

EDIT: I just disabled the SSH over USB functionality, and tried again -- I can't even shut down the sshd server properly when toggling USBNetwork, it just stays activated, nor does the status change.