projectdp

Pi k3w – Kindle 3 display for Raspberry Pi

Posted in projects by projectdp on September 24, 2012

Hello, my name is projectdp and I’m here to bring you Pi k3w, my version of the KindleBerry Pi.

I assume you have seen the “KindleBerry Pi” project by Damaru! It was my inspiration for this project, you can read about it here: http://www.ponnuki.net/2012/09/kindleberry-pi/.

If you are looking for a comprehensive guide to getting this to work for you, I hope this post serves as that guide. Let’s get started. As always, RTFM with anything that you’re installing, I am not the source of all knowledge, there are many other things you can do with the software packages.

pi k3w

Pi k3w, in all it’s naked glory.

Hardware:

  1. Kindle 3 Wireless edition (k3w).
  2. Raspberry Pi (rev. B).
  3. USB Keyboard (mechanical Noppoo Choc Mini if you’re curious).
  4. Cable (1/3): Kindle charger USB cable and power adapter.
  5. Cable (2/3): Motorola Droid Bionic USB cable (any ‘male micro USB’ to ‘male USB type A’ should work).
  6. Cable (3/3): Ethernet cable for providing internet to the Pi, you can use wireless if you want in lieu.
  7. Temporary monitor to configure the Pi and do testing (HDMI, or Composite out).
  8. Separate machine to configure Kindle
Pi k3w displaying top via tmux

Pi k3w displaying top via tmux

Kindle requirements:

  1. Jailbreak Kindle
  2. Install USBNetwork
  3. Install Launchpad
  4. Install Terminal emulator (Myts)

1.0 Jailbreak: Get binary – k3w 

Beware you could brick your kindle. You have been warned, take responsibility for what you do on your device.

A huge thanks to the Kindle community at MobileRead! You can download the Jailbreak build here: http://www.mobileread.com/forums/showthread.php?t=88004.

At the time of this writing the file is called: kindle-jailbreak-0.11.N.zip  Download and unzip this file.

1.1 Jailbreak: Copy & Install on Kindle – k3w 

Find the proper install binary for your device, see the README.txt for more information but I used: update_jailbreak_0.11.N_k3w_install.bin.

Plug in your Kindle to your desktop, transfer the aforementioned file to the root directory. After you have copied successfully, you may dismount the Kindle. Then navigate here on the Kindle to restart and install the jailbreak app: [HOME] -> [MENU] > Settings -> [MENU] > Restart. This should successfully install the jailbreak software. If it did not work, please thoroughly read the README.txt and if you still don’t get it, ask on the mobileread forum, I didn’t write the software! I will repeatedly refer to this process, it’s simple just remember that it comes up several times.

2.0 USBNetwork: Get binary – k3w 

Go back to the link in section 1.0, download the file: kindle-usbnetwork-0.43.N.zip Download and unzip this file.

Find the proper install binary for your device, see the README.txt for more information but I used: update_usbnetwork_0.43.N_k3w_install.bin.

2.1 USBNetwork: Copy & Install on Kindle – k3w 

Plug in your Kindle again, transfer the USBNetwork binary to the root directory. Copy your file successfully and then dismount the Kindle. Basically you will do the same thing as you did in 1.1 to restart and install that USBNetwork binary file.

Note: There is one tricky thing here. This utility will be disabled until you enable it. How do you enable it? You look for the file named: DISABLED_auto and rename that file to simply: auto. IMPORTANT: When you change this to auto, you will no longer be able to plug it into your Windows machine as a normal USB device. You can always reverse this process in a few ways:

  1. Myts: [Recommended] You can rename the file on the Kindle directly by navigating to the same folder /mnt/us/myts and issuing the command: mv auto DISABLED_auto
  2. SSH: You can ssh from your Pi to the Kindle: ssh root@192.168.2.2. Username:root Password:[empty password]. You then mount as rw (do this only if you are comfortable, mount it back as read only after you make the change). Navigate to the correct folder: cd /mnt/us/myts issue the command now: mv auto DISABLED_auto
  3. Kindle firmware: You can do a factory restore if you prefer. Follow the Kindle manual.

That wraps up USBNetwork, just remember you need to have this utility enabled in order to connect to it via ssh on the Pi.

3.0 Launchpad: Get binary – k3w 

Follow this link: http://www.mobileread.com/forums/showthread.php?t=97636 to get the Launchpad software which is required to run the terminal emulator later. Download the file: lpad-pkg-001c.zip and unzip.

Find the correct install binary for your device. I used: update_launchpad_0.0.1c_k3w_install.bin

3.1 Launchpad: Copy & Install on Kindle – k3w 

Plug in your Kindle yet again, transfer the binary to the root directory. Same steps as 1.1. Look for a successful install.

4.0 Myts terminal emulator: Get Binary – k3w 

This one was a little tricky as the version (6) listed on Damaru’s site did not work for me. I had to use a newer version (8) which I found on this page: http://www.mobileread.com/forums/showthread.php?t=154500&page=5

I will list the download link here too:

http://my.svgalib.org/kindle/myts-8.zip Extract this zip file.

4.1 Myts terminal emulator: Copy & Install on Kindle – k3w 

Plug in the kindle again. When you extract the file myts-8.zip you’ll be greeted by two folders: launchpad, and myts. Copy the myts folder to the root of your Kindle. Next you’re going to need to grab the extracted file in the launchpad folder called: myts.l.ini. You will put this file on the Kindle in the folder named launchpad. This will allow you to use Launchpad’s hotkeys on the Kindle to launch myts later. To make sure that this new ini configuration file is read, safely disconnect the Kindle and issue this hotkey sequence: [Shift] [Shift] [Space]. You should see a command ‘Success!’ notification on the Kindle when you issue this command. If it doesn’t work the first time do it slowly and deliberately.

To verify that the Myts emulator was installed, you should then be able to press: [Shift] T T. Again slow and deliberate. This should drop you into the Terminal. Success! You can hit the left back arrow (the Kindle’s page turning buttons) to exit temporarily. Or you can do [Shift] T A to kill sessions. Check the myts README file in the myts directory you extracted earlier. Also a good reference is: about.txt.

This concludes the Kindle software required.

Raspberry Pi Requirements:

  1. USBNetwork
  2. Terminal Multiplexer (tmux)

1.0 USBNetwork: Install script – Pi

This part is directly copied from Damaru, it works great. Use your favorite editor to edit the file /etc/network/interfaces on your Pi. Add the following lines:

allow-hotplug usb0
mapping hotplug
script grep
map usb0
iface usb0 inet static
address 192.168.2.1
netmask 255.255.255.0
broadcast 192.168.2.255
up iptables -I INPUT 1 -s 192.168.2.1 -j ACCEPT

This means that your USB port on your Raspberry Pi, is turned into an ethernet addressed port. This way you can access the Pi from your Kindle.

1.1 USBNetwork: Test Pi to Kindle – Pi

Plug in your Kindle to your Pi. So you don’t have to restart or toggle your entire network service you can issue this simple command from the Pi to test: ifconfig usb0 192.168.2.1

Once you have done that you should be able to ping your Kindle: ping 192.168.2.2. Success! (?)

This should be all you really need to ensure USBNetwork is working properly. If it isn’t working, make sure to read the note in this section above: 2.1 USBNetwork: Copy & Install on Kindle – k3w.

2.0 Terminal Multiplexer: Install and Intro to tmux – Pi

Well this is where I differ from Damaru. I like tmux better than the popular screen program. I’ll show you how to get it set up nicely. Here we go! On your Pi, make sure you’re connected to the internet and issue the command:

apt-get install tmux

Let aptitude do its thing and install tmux for you. It’s a beautiful thing. Really there aren’t other steps to installing your multiplexer. Here are a few some simple things that will help to get you started: man tmux. You can start tmux by simply typing that command: tmux, you can tell the terminal changes slightly, now to detatch the session, press Ctrl+b then press d. Now that you’re back at a normal terminal window, you probably want to attach to that window again. Where is it though? Find it with tmux ls. You will likely see 0: 1 windows (created blah blah blah)… So actually the name is going to be “0”. To attach to that particular window again you can do this: tmux attach -t 0. Magic! Now get out of there: exit. I’ll show you later how to name your tmux sessions, it’s pretty basic. There’s a lot to learn here. Read the man pages. Note: C-b-d is the syntax for: Ctrl+b then press d. Got it? Cake!

Automation:

  1. Overview
  2. Test Kindle as the Pi display!
  3. Users and Passwords
  4. Kindle
  5. Pi
  6. Testing

1.0 Overview: – auto

This section is going to be pretty hefty. I’ll try to segment it as nicely for you as possible. I hope you’re doing alright so far. Leave a comment about your progress, or lack of progress so I can make fun of you. :)

In the Automation section we’re going to make the most out of this project. We’ll take a lot of the meaningless effort out of the loop. We’ll make it fast to connect and use. We’re going to make it a mainstay on the Pi for an easy portable screen in a pinch.

2.0 Test Kindle as the Pi display! ssh login – auto

Up to this point you have pretty much everything you need to now ssh from your Kindle to your Pi. Go ahead and do it, make sure your Kindle is still hooked up to your Pi. Grab your Kindle and get into myts: [Shift] T T. Steady. Now ssh to your Pi: ssh 192.168.2.1. Are you failing at entering the IP? Probably. Ok here’s where a specific file comes in handy. It’s called about.txt. I referenced it in Section 4.1. Read it. You can read it on your Kindle: cd myts then the command: cat about.txt. Basically you have to do some annoying stuff like this: ssh [Alt] q [Alt] o [Alt] w . [Alt] q… And so on. You’ll figure it out. I’m telling you, about.txt helps.  Success? Good. I’ll continue while you remember your passwords and such.

Pi k3w ssh login. Success!

Pi k3w ssh login. Success!

2.1 Test Kindle as the Pi display! use tmux – auto

You should be logged into your Pi now from your Kindle. That’s called a milestone. Start tmux from your Kindle: tmux. Now with the Pi keyboard issue the command: tmux ls. Connect to the one your Kindle is on, it should just show 0: 1 windows (…etc.), by issuing the command: tmux attach -t 0. Now you should be able to type on your Pi keyboard, and it should appear on your Kindle. Sexy. You can pretend that you have everything working properly by turning off your monitor, but you have a long way to go if you want the Pi to boot automatically displaying the Pi on the Kindle! Let’s get to it!

3.0 Users and Passwords: Introduction – auto

Alright let’s get our notes straight on user access. So far you have some user account on your Pi, you’re probably doing it wrong and using username: root password: root, or some other silly defaults. You’re all set with the Pi, how about the Kindle? Same thing. username: root password: [empty]. You really don’t want this, especially on the Pi, I leave the defaults on the Kindle myself. Login as root and issue: passwd to change the password.

What I recommend is creating a separate user for the Kindle instance. I was not very creative and I made the user: kindle. Issue the command: adduser kindle. Temporarily make the password extremely easy to type for testing on the Kindle (I used the password: aaa). Oh right to change the Kindle username’s password: passwd kindle. Test it from your kindle: ssh kindle@192.168.2.1. Note: the @ symbol is [Back] w, if you didn’t read about.txt.If you’re too lazy to even type this, you can hold off testing until you automate your login, but I suggest making sure this is working first.

4.0 Kindle: fast ssh to Pi – auto

Let’s make a simple script to login to the Pi from the Kindle over ssh. On your Pi (because it has that nice keyboard that makes typing convenient — Smart!) make a file named something really easy to type. I used the filename: aa. To create the file issue: touch aa. Then use your favorite editor to edit the file and append:

#!/bin/sh

ssh kindle@192.168.2.1

Save it. Now you need to make sure that you can execute the script once it is on the Kindle. Issue: chmod +x aa. Good now the only thing remaining is getting it to your Kindle. This takes some ninja tricks but let’s go for it: scp aa root@192.168.2.2:/mnt/us/myts. Remember: You’ll be entering a blank password for root on the Kindle. Now try it out. On the Kindle type: ./aa. How do you do the slash? [Back] v. Later on in the article I’ll make it even easier, but let’s test with this for now. Enter your password: aaa. There you go, all set for faster logins.

5.0 Pi: Boot into your kindle user’s account on tty1 -auto

Edit your /etc/inittab on your Pi. Comment out (disable!) the following line, by putting a # symbol in front of it:

1:2345:respawn:/sbin/getty 38400 tty1

Now add the following command beneath the previous line:

1:2345:respawn:/sbin/agetty -a kindle -8 -s tty1 linux

Note: this assumes you are using the kindle user to automatically log in to tty1, your default terminal on the Pi. Alternatively, you can use this other command that is reported to work, but I could not get it to work this way myself: 1:2345:respawn:/bin/login -f kindle tty1</dev/tty1>/dev/tty1 2>&1

Save this file and let’s continue on. You will notice that performing a restart at this point should boot you into the kindle user account directly. Go ahead and test that functionality.

5.1 Pi: Configure .bashrc to handle joining scenarios – auto

Now as the kindle user, you’ll want to modify your .bashrc file. Navigate to your home directory: cd ~.  Edit the file: .bashrc. Append the following script:

if [ -z “$TMUX” ]; then
(tmux attach -t pi || tmux new -s pi )
fi

If you were having trouble with damaru’s script, try this out it works like a charm! If you’re using screen though, just make sure to translate the equivalent screen commands properly. If anyone is using screen and can put the proper environment variable and code in the comments I think people would appreciate it :)

Now your Pi should boot directly into a tmux session named pi. The cool part is, when your Kindle logs in to the Pi using the kindle username, you will automatically join the pi tmux session.

5.2 Pi: Configure ssh passwordless logins – auto

Here’s how you get to login without entering that aaa password from your Kindle, and using public keys instead. You will be utilizing the USBnetwork toolchain which includes the ssh client dropbear. To generate the proper keys you will need to use dropbearkey, the generator tool for dropbear ssh keys.

First, install the program with: sudo apt-get install dropbear. Now navigate to here: cd /home/kindle/.ssh/. Then issue the command: dropbearkey -t rsa -f id_rsa | grep ssh-rsa >> authorized_keys. You will then copy the public key to the Kindle with this command: scp id_rsa 192.168.2.2:/mnt/us/myts/id_rsa.

The very last step is to ssh into your Kindle and update that file we created earlier: aa to make the file look like this (I bolded the change for you below):

#!/bin/sh

ssh kindle@192.168.2.1 -i id_rsa

You are basically just specifying the key to join with. Now you can use your Kindle and try the ./aa command again. Are you winning yet? If so, celebrate and get on the Pi again and change your kindle user password.

6.0 Testing: Does it all work?

Now you should be all set. Let’s perform some checks:

Check 0: Try a Pi reboot with your monitor connected to watch the progress. Make sure the Pi logs in completely into the kindle account and begins the tmux session. You should be able to just wait and eventually be able to type on the tmux session command line without any other interaction.

Check 1: On the Kindle, open a myts terminal with [Shift] T T and issue the command ./aa (remember the forward slash is [Back] v). You should be logged in now with the Kindle to the Pi, attached to the same tmux session named pi.

Check 2: Unplug the monitor connected to the Pi’s HDMI or composite out. Reboot the system. Wait a few seconds, in the mean time, get ready on the Kindle to issue the ./aa command again (you should be able to hit up or left depending on your screen orientation to repeat the command). You can try several times blindly to connect, you’ll eventually be able to, and voila, you are ready to attach the Kindle to the Pi in a pinch!

6.1 Testing: Bugs

After performing Check 2, you might have noticed that tmux isn’t starting completely in full screen mode. The reason for this is because the terminal character dimensions was autoset by your monitor’s higher resolution. To combat this issue you can create the file: /boot/config.txt and append this to it:

framebuffer_width=1280
framebuffer_height=1024

Note: You can use any resolution you prefer, perhaps the resolution of the pi lapdock? :) but these were the dimensions of my test monitor.

If you notice any other bugs, please review the sections that are associated with those checks. If you still have problems drop some information in the comments and we’ll get it sorted.

Pi k3w running the top command over tmux

Pi k3w running the top command over tmux

That concludes the article! I hope you enjoyed this, I had a great time figuring all this out :D Leave a message with your project or anything relevant in the details!

References:

Video:

http://www.youtube.com/watch?v=Ny6mZi_fRJg

Reddit:

http://www.reddit.com/r/raspberry_pi/comments/zoivv/kindleberry_pi/

Forums discussing the original project:

http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=17001

http://www.element14.com/community/thread/19807?tstart=0

http://www.mobileread.com/forums/showthread.php?t=190951

Kindle:

http://blog.diannegorman.net/2010/09/kindle-3-keyboard-shortcuts-et-al/

About these ads

31 Responses

Subscribe to comments with RSS.

  1. Bosstiger said, on September 27, 2012 at 2:51 am

    Reblogged this on Gigable – Tech Blog.

  2. Richard Capuozzo said, on October 1, 2012 at 7:37 am

    I renamed Disabled to auto and at that point, the kindle no longer showed up on my desktop. I’m using an iMac and cannot install Myts. If I install Myts first, and then rename Disabled to auto, I get no response from the Control TT command at all. Everything installed perfectly up to the point where I changed to auto. What can I do now?

  3. projectdp said, on October 1, 2012 at 7:52 am

    To be clear you, for USBNetwork, you renamed “DISABLED_auto” to “auto”, correct?

    I’m not sure what you mean by the part about having an iMac, is it just because it’s a zip file? Also, you’re going to issue [Shift] T T, not Control TT on the Kindle to get to the shell once you’ve installed it.

    Richard, if the Kindle is no longer showing on your desktop it means you can go ahead and SSH to the Kindle. See section “1.1 USBNetwork: Test Pi to Kindle – Pi”

    • Richard Capuozzo said, on October 1, 2012 at 8:09 am

      Yes, I renamed to “auto”. I just wanted to let you know that I’m a Mac user and when I plug in my Kindle, it normally appears on my desktop. And I meant “Shift TT” not Control as I indicated. I thought I would have to install myts before testing pi to kindle. If I can’t see the kindle on my desktop, I have no way of getting to the root directory on the kindle to install myts.

      • projectdp said, on October 1, 2012 at 8:20 am

        I see now, I should reorganize those notes because if you follow that in sequence you’re going to get stuck like that.

        I still recommend you SSH to the Kindle and set “auto” to “DISABLED_auto” until you have Myts installed successfully. You only need to change DISABLED_auto to auto when you are ready to SSH and have a terminal to use. This was bad writing on my part, I just organized the notes for that software under the software, rather than in the correct sequence — sorry!

      • Richard Capuozzo said, on October 1, 2012 at 2:15 pm

        I restarted the process and carefully followed the directions but could not get myts to install on the Kindle, no matter what. The Kindle is a 2.5 version; perhaps I need to use version 6 instead of version 8. I looked around but could not locate version 6. Any thoughts?

      • projectdp said, on October 2, 2012 at 8:34 am

        If you want to try version 6 check here: http://www.mobileread.com/forums/showthread.php?t=154500 (page five of this was linked in my article showing version 8, version 6 was on page 1.) Hope that gets it installed. You know if that doesn’t work you can try another terminal emulator, myts isn’t the only one!

  4. ForthPi said, on October 9, 2012 at 1:15 pm

    First of all, thank a lot for this infos.

    I think I followed the instructions up to step 4.1
    I don´t get a reaction on trying [shift][shift]space or [shift] T T on my kindle.
    I do this on my kindle home screen, yes?

    Can´t find out what I did wrong and how to proceed.
    Any help appreciated.

    • projectdp said, on October 10, 2012 at 12:12 pm

      Hello FourthPi!

      If you’re not getting a response with those commands, there is something wrong with Launchpad, did you make sure to install it in section 3.0?

      Launchpad is definitely the program that controls those hotkeys. :)

      Yes you do them from the Kindle home screen. Read the instructions for Launchpad on mobileread forums if you’re not able to figure it out with my instructions.

      I hope you can get it working, I really enjoyed this project. Let me know if you have any issues! Have fun FourthPi!

      • ForthPi said, on October 11, 2012 at 9:17 pm

        hi projectdp
        thanks for your reply.

        Making progress, after two factory resets and trying out versions i have launchpad and myts working now. Some suggestions for your text follow:

        1) Install procedure: First time installing as described by you went fine.
        After the factory reset it did *not* work any more, installation was not successful.
        I had to “update your kindle” instead of “restart” to make it work now.
        Would be worth mentioning to try the kindle update if restart does not work.

        2) USBNetwork. As already suggested here 2.1 should be formulated slightly different.
        It´s not really obvious to the first time reader *when* she must enable it.

        3) regarding same chapter 2.1
        looks to me as if the path (given twice) in the recovery section should point to
        the usbnet folder instead of myts.

      • ForthPi said, on October 11, 2012 at 9:25 pm

        an afterthought regarding sequence of the procedure:

        to avoid difficulties with too early enabling USBNetwork why not install in the following sequence:
        1. jailbreak
        2. launchpad
        3. myts
        4. USBNetwork

        IIRC i did it like this in my 3rd (successful!) attempt.

  5. damarusama said, on October 23, 2012 at 3:22 am

    Wow! Thanks for the expanded, clearer version of this hack! Hope you are having fun with your kindle berry pi!

    • projectdp said, on October 30, 2012 at 2:09 pm

      Hello Damarusama!

      I sure am, I use it whenever I don’t have another screen handy, just plug in and go! :)

      Thanks again for your original post!

  6. skidoobond said, on March 15, 2013 at 8:11 am

    I am stuck at the section 5.2. I issue the scp command to add the id_rsa file to the kindle. I am asked for the kindle password. I don’t recall setting one and just pressing enter only asks for the password again. i tried to change the password via ssh but it won’t write to the password file claiming permission denied.

    • projectdp said, on March 15, 2013 at 9:02 pm

      Hi skidoobond,

      You may have changed the permissions on the directory you are copying to. You can issue: ls -al to see the directory in full and check the permissions in /mnt/us/myts/. Then you can use chown to fix it. If you don’t know what you’re doing there, you can use the root account on your kindle to scp to the directory. Here’s how you would do that: scp id_rsa root@192.168.2.2:/mnt/us/myts/id_rsa and then enter the password, which should be blank as described in section: 2.1 USBNetwork: Copy & Install on Kindle – k3w Bullet number 2.

      What’s happening now is that you’re issuing the scp command from your local user on your Pi which probably doesn’t match any account on your Kindle device.

      Hope that helps!

      • skidoobond said, on March 19, 2013 at 11:05 am

        Thanks, I used putty to login to the Pi as root.I am then able to scp … root@192.168.2.2:…. just fine, thanks.

        Now I have a new issue. When I rotate the kindle screen to landscape mode, I see the pi shell just fine. When I have the kindle in the portrait mode, the to left corner is blank, but long commands lines can be seen peeking out from behind this “blank” area. Any ideas? I can issue commands and everything else seems to be working except for this blank zone. The kindle screen still works because I can use it as normal without problems.

      • projectdp said, on March 19, 2013 at 11:54 am

        Hi skidoobond,

        Are you using tmux when that’s happening or just the shell? Maybe you can look into redrawing/refreshing the screen. Tmux usually will show you asterisks if your original screen size on the pi is rather small. Redrawing is the solution there. Hm I will think about this a bit and try to remember if I had encountered this issue. Hope you’re having fun with it!

  7. skidoobond said, on March 20, 2013 at 11:55 am

    Without the kindle attached to the Pi, I shift -T-T in portrait mode and get the blank zone.
    I am unfamiliar with tmux. How do you force a screen redraw?

    And, yes, this is awesome (at least in landscape mode).

  8. skidoobond said, on March 20, 2013 at 11:59 am

    I guess that would be myts not tmux? Anyway, I don’t know much about myts either.

  9. skidoobond said, on March 20, 2013 at 12:05 pm

    I think I fixed it. I used the kindle’s previous page button to get back to the kindle’s home screen. Then I did shift T-A. Then shift-TT to re enter a new session. Maybe there was still an open session blocking the current one?

  10. Tim said, on April 9, 2013 at 10:14 am

    I opened the terminal 1 by shift T T successfully but I can not exit it. I have pressed Left< and tried shift T A. It doesn't work. Is there any means to force it to quit? Thanks.

  11. kindle said, on May 23, 2013 at 7:07 pm

    I am glad I came across your site. I really enjoy gaining knowledge everyday and your site did just that. Thank you for the post.

  12. JARVIS (@JARVISPi) said, on June 16, 2013 at 6:16 am

    Hey, I’ve been trying to install a terminal on my Kindle 3 WiFi running the 3.4 OS using your guide.
    But I always seem to get stuck getting launchpad to work. I follow the directions perfectly, but the [Shift][Shift][Space] key combo never does anything. Any ideas as to my problem?

  13. d4ZFFA0Zxa said, on July 16, 2013 at 2:46 pm

    934506 421602Id should talk with you here. Which is not some thing I do! I spend time reading an write-up that could get individuals to feel. Also, appreciate your allowing me to comment! 83688

  14. J said, on May 31, 2014 at 2:41 pm

    Thanks for the detailed instructions. I’m using a Kindle DXG, and I’m on step 2.1. I’ve succeeded in using ssh to connect to the Kindle and using tmux to display the Raspberry Pi’s terminal. However, after about a minute, I get this error message on the Kindle: “Write failed.Broken pipe.” Then I’m kicked off the Pi’s terminal and returned to the mnt/us/myts prompt. I can reconnect and rejoin the tmux session, but I always get kicked off again after a minute.

    Looking for instructions, many people recommend adding the lines “ClientAliveInterval 300″ to /etc/ssh/sshd_config and “ServerAliveInterval 300″ to /etc/ssh/ssh_config. I’ve tried this and it doesn’t seem to help. It seems like this strategy only helps when the connection breaks after the devices have been left idle for a minute or two. But my connection generally breaks mid-word when I’m typing.

    Another post suggested that my network might be trying to reassign the IP addresses of the Kindle or Raspberry Pi. I’ve disconnected the ethernet from the Pi and turned off wireless on the Kindle, so that should no longer be a problem.

    Any guesses as to what I”m doing wrong?

    • David said, on June 14, 2014 at 4:20 am

      J, I’m having the same problems… did you find a fix?

      • J said, on June 16, 2014 at 12:23 pm

        Not yet. Are you also using DXG?

      • J said, on June 28, 2014 at 11:13 am

        I have managed to find two solutions to the two minute timeout problem. It works for my needs. I don’t know if it will work for yours. Solution one is to use a K3W, as projectdp did.

        The second solution is instead of SSHing from the Kindle into the RPi, I’m SSHing from the RPi into the Kindle. For whatever reason, this does not lead to the 2-minute timeout. To do this I had to install tmux and libevent onto my Kindle using these instructions: http://www.timelesssky.com/blog/linux-apps-for-kindle

        To run the programs I had to add /mnt/us/local/bin to the PATH environment. At the moment I can’t remember the file path to the profile file where this is stored.

        There was one error message I solved with the following command:

        ln -s /mnt/us/local/lib/libevent-2.0.so.5 /usr/lib/libevent-2.0.so.5

        I had to change the root password using the command:

        passwd root (Simply typing passwd asked me to type the current password, which I didn’t know)

        Then, from the RPi,

        ssh root@192.168.2.2
        password:
        tmux attach -t 0

        I haven’t made it automatic yet, so I still have to use a second monitor when I’m entering those lines on the RPi. Hopefully it is easy to have it execute those commands when it boots up.

  15. J said, on June 16, 2014 at 5:09 pm

    I’ve got one more issue I’ve run into. I’ve finished the rest of the steps and almost everything works great. The problem is that the public key login is not actually passwordless for me. In fact, it asks for two passwords now. First I’m prompted

    Enter passphrase for key ‘id_rsa’ :

    This apparently is empty and I can just hit enter. Then I’m prompted

    kindle@192.168.2.1’s password:

    Any ideas?

  16. […] 把Kindle作为raspberry pi的屏幕,再加一个USB键盘,一个便携的小霸王编程机就诞生了,看hello worlp: 硬件:1. Kindle3:淘宝2. raspberry PI:易络盟3. microUSB充电器一个:淘宝4. USB转microUSB数据线一条:淘宝5. USB键盘一个:淘宝6. 视频线一条+电视一个 或 HDMI线一条+显示器一个:用于初始化设置raspberry PI, 以后就不用了。7. SD卡一个:SanDisk闪迪 Ultra 高速 SD卡 SDHC 16G Class10 30M/s 200X 高清8. SSD读卡器一个:淘宝9. 网线:淘宝软件:1. Kindle3 越狱包:update_jailbreak_0.6.N_k3g_install.bin2. Kindle3 usbnetwork:update_usbnetwork_0.33.N_k3g_install.bin3. Kindle3 launchpad:update_launchpad_0.0.1c_k3g_install.bin4. Kindle3 myts(Kindle3的虚拟终端):myts-7.zip5. Kindle3 usbnetwork的Windows驱动:XP-RNDIS-Ethernet-Gadget6. win32DiskImage:Win32DiskImager.exe7. raspberry pi镜像:2012-09-18-wheezy-raspbian.img8. raspberry tmux:使用电视启动后,sudo apt-get install9. raspberry dropbear:使用电视启动后,sudo apt-get install原理:1. pi启动时自动登录,且自动使用tmux/screen共享session2. kindle和pi使用usbnetwork创建连接 3. kindle自动登录pi,且自动使用tmux/screen共享session4. USB键盘和Kindle键盘分别操作两个pi和kindle,但是两者共享session,所以看起来是一样的。参考:http://projectdp.wordpress.com/2012/09/24/pi-k3w-kindle-3-display-for-raspberry-pi/ […]


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.

Join 330 other followers

%d bloggers like this: