Re: [LinuxRMS] Re: Sheevaplug configuration for RMS Gateway?
Thank you for this information. I've thrown my Sheevaplug under the table for now. I managed to "brick" the thing updating the Kernel and it is more trouble than it is worth to reboot from a USB stick and fix it. It also produced harmonically rich RF through 148 MHz strong enough to break the squelch on mobile radios 300 feet away. So I've lost interest in them.
--- On Sat, 5/30/09, Jim Kusznir <jkusznir@...> wrote:
From: Jim Kusznir <jkusznir@...>
Subject: Re: [LinuxRMS] Re: Sheevaplug configuration for RMS Gateway?
Date: Saturday, May 30, 2009, 3:13 PM
I'm developing for the SheevaPlug for my "day job": Washington State
University AI Lab Manager. We use several USB aps with ours, but I
also replaced the stock OS with Gentoo to match our other systems.
With correct kernel support, you should be able to simply plug in the
USB adapter and it will create usb adapters. With my gentoo
installation, I get /dev/ttyUSB* created.
A word of caution, though: Based on what was said in the OpenWRT
thread on this list, there is a binary module required for linuxRMS.
As the Sheeva is an ARM device, you'll need to get this compiled for
ARM, which it sounds like doesn't exist yet. As such, its likely that
you won't be able to actually run linuxRMS on sheeva without the
On Sat, May 16, 2009 at 8:57 PM, Ron <dox_nairobi@ yahoo.com> wrote:
> Charlie k7gbb,
> Thank you for this information and the offer. For now I'm stymied on the USB
> to Serial connection. There is not /dev/ttyUSB anything and no
> /dev/usb/ttyUSB anything either. So I tried this:
> root@debian: /# lsusb
> Bus 001 Device 003: ID 06cd:0131 Keyspan
> Bus 001 Device 001: ID 0000:0000
> root@debian: /# modprobe usbserial vendor=0x06cd product=0×0131
> FATAL: Could not load /lib/modules/ 220.127.116.11/ modules.dep: No such file or
> Then this:
> root@debian: /# cd /lib/modules
> root@debian: /lib/modules# dir
> root@debian: /lib/modules#
> Oh my! It would seem this kernel was compiled without this line:
> make modules modules_install
> Unless I find another way to enable the USB to Serial connection I'm done
> until I figure out how to compile a new kernel for this little Sheevaplug.
> Before I do that I think I'll post some other plug computer blogs and see
> what comes back at me. :(
> --- In LinuxRMS@yahoogroup s.com, C Schuman <k4gbb1@...> wrote:
>> Ubuntu 9.04 does not have fsdev compiled into the distro.
>> That is why all the device names looks different.
>> If you have to use MKISS you will have to use a New set of AX.25 tools.
>> Ax25ipd and MKISS have to be re-written to work with Udev.
>> When I tested the Beta release I was able to setup two Ports.
>> Look at the /dev/ dir and see if there are any ttyUSB* devices.
>> The list that you did looks like the USB ports and Hubs.
>> I have some source code from an earlier experiment that appears to work
>> with MKISS and
>> some scripts that set up ax25 ports, but they use the /dev/ttyUSB names.
>> Ron wrote:
>> > I've been working away figuring out the Sheevaplug
>> > <http://www.marvell. com/products/ embedded_ processors/ developer/ kirkwood/ sheevaplug. jsp>.
>> > I've been adding software packages and configuring the thing. So far
>> > I have managed to get the following working after reading pages of
>> > blog notes beginning at:
>> > http://ubuntuforums .org/showthread. php?t=1082489& page=1 .
>> > * Did an apt-get-update and had an error message about missing
>> > directories. Learned that if I created them they were in RAM
>> > and would not be there after a reboot.
>> > * Added this to /etc/rc.local and stopped the problem missing
>> > directories after a reboot.
>> > 1. #!/bin/sh -e
>> > 2. mkdir -p /var/cache/apt/ archives/ partial
>> > 3. cd /
>> > 4. #Get the date
>> > 5. /usr/sbin/ntpdate- debian
>> > 6. insmod /boot/fat.ko
>> > 7. insmod /boot/vfat.ko
>> > * Added this to /etc/ntp.conf so that ntpdate-debian could get the
>> > right time from the internet
>> > 1. server ntp.ubuntu.com
>> > 2. server 0.us.pool.ntp. org
>> > 3. server 3.us.pool.ntp. org
>> > 4. server 2.us.pool.ntp. org
>> > 5. server 1.us.pool.ntp. org
>> > * Added this to /etc/resolv. conf for Domain name resolution to IP
>> > addresses for internet access
>> > for command line statements such as 'wget
>> > http://software_ I_need.com/ goodstuff' and to access"
>> > the above listed time servers.
>> > 1. nameserver 18.104.22.168
>> > 2. nameserver 22.214.171.124
>> > * AX25 support and tools is installed
>> > * MySQL-Client- 5.0 is installed
>> > * GCC compiler and libraries are installed
>> > * Other misc. packages listed on the Google RMS Software site
>> > <http://groups. yahoo.com/ group/LinuxRMS/> are installed.
>> > * The RMS Gateway is downloaded and unpacked on the Sheevaplug and
>> > waiting on me to compile it
>> > The thing came with Ubuntu Jaunty version 126.96.36.199 already
>> > installed. There is no graphic interface and I am accessing it using
>> > my terminal in openSUSE by SSH. The command is: ' ssh
>> > root@...' (this IP was given by my local network DHPC
>> > server). I found the IP address by going into my DD-WRT Control panel
>> > via my web browser pointed to 192.168.1.1. I think you have a similar
>> > server in your home network. I have to be the "root" user to access
>> > it from the ssh command line and the password for these things comes
>> > set as "nosoup4u".
>> > Assuming that AX25 was properly compiled which I'm hoping it was on
>> > the originally installed kernel, then about all I should have to do to
>> > get this RMS Gateway going is to finish compiling and configuring the
>> > RMS Linux software, figure out how to use the USB port to feed into a
>> > serial connection and I think this syntax will do that... modprobe
>> > ftdi_sio vendor=0x9e88 product=0x9e8f . I just have to figure out the
>> > vendor information for the USB to Serial connection. My ACER Netbook
>> > running Kubuntu did automatically pick up the Keyspan 4 port Serial to
>> > USB device and gave it these names: ttyUSB0, ttyUSB1, ttyUSB2,
>> > ttyUSB3. I was then able to use those names in my Minicom terminal
>> > and adjust the serial port settings for the TNC and worked FB. The
>> > Sheevaplug is not doing this automatically for me. What changes in
>> > the /dev directory are the "usbdev1.2" series get added when the
>> > Keyspan 4 port Serial to USB device is plugged into it.
>> > * root@debian: /dev# dir usb*
>> > * usbdev1.1 usbdev1.2 usbdev1.2_ep02 usbdev1.2_ep81
>> > * usbdev1.1_ep00 usbdev1.2_ep00 usbdev1.2_ep04 usbdev1.2_ep88
>> > * usbdev1.1_ep81 usbdev1.2_ep01 usbdev1.2_ep06
>> > So I'm at the point where I have to find a way to configure a serial
>> > port for the TNC using a USB to Serial adapter. If you are reading
>> > this and know what I need to do, please let me know and of course any
>> > other advice, directions, or recommendations will be cosidered!
>> > Ron
>> > KA7U