If you need to create a partition a drive larger than 2TB and you’re facing trouble, on gparted, you need to go to ‘Device’ -> ‘Create partition table’ and expand ‘Advanced’. There, you need to select ‘gpt’ as partition type. After that, you will be able to create any partition with any filesystem (as long as it suppots 4TB).
Jan 04 2012
Well, I finally found time to write a little howto on using your pendrive with the PlayBook. I’m sorry about the delay on publishing this, but i was out of home for a few days and couldn’t find time to write the howto.
Well, let’s go to the howto. Things you will need:
- BlackBerry PlayBook
- Root access to your PlayBook (thanks to dingleberry )
- Female USB A to micro USB cable and a soldering iron OR USB OTG cable (for example this one will work: Micro USB OTG Cable)
- A pendrive
Now i will try to make instructions as short and clear as possible. Just let me know if something is unclear. I would also like to let you know that i have only tested this on a 1.8.xxx PlayBook version, so results on OS2 are unknown (i haven’t got access to a PlayBook with OS2 and i’m not wishing to upgrade mine at the moment). Please keep this in mind when trying to use this method.
Get a USB OTG cable or just find a Female USB A to micro USB cable, open the micro USB side and solder pins 4 and 5 of the micro USB port together (this is what turns the USB port into host mode). The photo shows the first version i used. Then i decided to get a nice USB OTG angle cable as you can see in the first photo of the post. If you are interested in one of those, just let me know.
Second step – Console commands
When you have your USB OTG cable, you can proceed to run the commands to load the necessary kernel drivers. The nice part is that everything is already on the PlayBook, so you don’t really need to upload anything. The commands you will need to run are the following:
io-usb -domap4430-mg ioport=0x4a0ab000,irq=124
waitfor /dev/io-usb/io-usb 4
devb-umass cam pnp blk automount=+hd6t6:/accounts/1000/shared/usb:dos,automount=+hd6:/accounts/1000/shared/usb:dos
The only line you really need to pay attention to, is the last one. It shows where the pendrive will be automatically mounted after you connect it. You can specify different mount points for different partitions just separating them by comas (in my example command, hd6t6 and hd6 shown)
The other commands just kill the USB server running and start it with the required commands to be able to run the USB port as a host port. There is also a command to load the kernel driver (io-usb domap….).
Last step – Connect your pendrive
If all went well, you should now be able to connect your pendrive and access contents on the mount folder you selected. Please keep also in mind that you must first create this directory for the automount to work. I also noticed that sometimes the kernel modules does produce a bus error and crashes. If that happens, just try to run all the commands again.
I really expect to be able to improve this method or provide a ready app to execute all the process, but at the current time, this has no ETA. If you want, you can follow me on @guillemmateos and i will tweet any finding or progress I make about this.
If you have any suggestions or are able to get different OS versions working with this method I’d be really happy if you could post it here and let me know.
Dec 12 2011
I’ve been finally able to get USB Host working on the PlayBook so now i can carry with lots more movies or watch the camera images directly on the PB. I posted a demo vídeo to show it working:
I’ll be posting instructions soon on how to do this on your PlayBook, so keep checking here for updates.
UPDATE: Instructions here: playbook USB host – eltecnoblog
Dec 12 2011
Today i found a few problems trying to uninstall virtualbox-ose package for Ubuntu. The following happened:
Desinstalando virtualbox-ose …
* Stopping VirtualBox kernel modules * Cannot unload module vboxdrv
invoke-rc.d: initscript virtualbox-ose, action “stop” failed.
dpkg: error al procesar virtualbox-ose (–remove):
To solve this issue, just edit the file /etc/default/virtualbox-ose as root and modify the line about kernel module loading and leave it at 0.
Aug 29 2011
If you have problems with an exim + MailScanner config where emails get into your system but then they get stuck on queue and not delivered to final destination (incoming exim works but the one that sends email to the outside world after MailScanner does not) be sure to check the file /etc/exim/trusted-configs
Inside this file you must specify the two config files that MailScanner should use. For example:
Hope to save sometime to someone…
Next Page »