When attempting to log into the server, I was prompted for a password as if the server did not have my public key. It certainly did. Checking /var/log/auth.log, I noticed this:

# /var/log/auth.log
Nov 2 17:47:37 hostname sshd[2053]: Authentication refused: bad ownership or modes for directory /home/myuser

Somehow (likely due to user error), the permissions for /home/myuser was set to 0777!

1
2

$ ls -lah /home | grep myuser
drwxrwxrwx 119 myuser myuser 8.0K 2010-11-02 17:45 myuser

The solution was to restore the directory permissions to what they should be – r/w access for the owner only.

1
2
3

$ chmod 0755 ~myuser
$ ls -lah /home | grep myuser
drwxr-xr-x 119 myuser myuser 8.0K 2010-11-02 17:45 myuser

Hopefully now you’ll be able to log in with your private key.

1
2
3

$ ssh myhost
$ tail /var/log/auth.log
Nov  2 17:50:36 hostname sshd[2212]: Accepted publickey for myuser from 192.168.1.XXX port XXXXX ssh2

So, when going through my home folder one day, I came across a hidden file called .bash_history. Hmm, I wondered. Could this solve my problem? Yes! It can!

1
2
3

$ rm ~/.bash_history
# You can also clear your history with the following command:
$ history -c

After deleting the file, open BASH and hit the up key – you should get nothing but a pleasant beep. A wonderful representation of security. Of course, it’d be best to shred the file using a utility such as, well, shred, so that nobody can retrieve the deleted contents. Note that you can only use the below command to shred the file if you haven’t already deleted it.

1

shred ~/.bash_history

And all should be well. But, what if you don’t want it to keep a track of your history? Well, there’s a couple ways to do so. I pulled the examples from the following link:

http://gentoo-wiki.com/SECURITY_Bash_History_Functions

The easiest one, which I did (I don’t feel like wasting any more time on this), was the following command:

1

ln -s /dev/null ~/.bash_history

This creates a link so that .bash_history points to /dev/null. Anything sent to /dev/null never returns – thus the name. It is simply discarded.

It seems the problem was with myspell – the English dictionary for some reason was not installed. So, it was a simple fix:

1

$ emerge myspell-en

Restart the programs and it should work. It may also help to ensure you have your LINGUAS variable set in make.conf. For example:

1

LINGUAS="en_US en"

Crash note: Pre-2.6.27 (I was using 2.6.26), my PC would simply restart and complain about a Hyper Transport sync flood error once it rebooted (BIOS message). This would happen when the driver was loaded and the card was in use. I have not yet had this problem with the 2.6.27 kernel.

I recently purchased a Linksys wireless PCI card for my home computer and ran into a few problems with the driver installation under Gentoo using a 2.6.26 kernel. A simple “emerge rt61″ command would not work – the sources would not compile. I tried a number of things, including compiling support with the kernel (as included in 2.6.24 and up), but that still did not work.

Yes, this will require some compiling – but don’t be afraid of it. The process is quite simple.

First, to find out if we’re talking about the same type of card here, type lspci as root. Below is my output:

01:07.0 Network controller: RaLink RT2561/RT61 802.11g PCI

RaLink provides open source drivers for this card on their website, however, as I stated above, they do not seem to compile with 2.6.26 kernels. I finally came across the following wiki page:

http://gentoo-wiki.com/HARDWARE_rt2x00

The “Open Source…” section contains the information I used to get my card working. Be sure to read it in addition to this entry, as it provides you with additional information such as necessary kernel configuration options. The wiki page then instructs you to download the open source drivers that pertain to your card from the following website:

http://rt2x00.serialmonkey.com/wiki/index.php?title=Main_Page

In my case, the drivers I needed were “rt61″. Select the drivers that pertain to your system as stated by lspci. Download it, extract it, compile, and install (as root). Be sure to replace the wget URL below with the URL to the CVS tarball you require:


$ wget http://rt2x00.serialmonkey.com/rt61-cvs-daily.tar.gz
$ tar -xzvf *.tar.gz
$ cd rt*/Module
$ make
$ make install


That should be it! Again, as root, attempt to load the kernel module. Again, this will differ based off of the driver you installed:

$ modprobe rt61pci

At this point, the wiki does not go any further. So, if you don’t know how to manually configure wireless network settings, you’re kinda screwed. First, let’s make sure your wireless card is properly recognized:


$ iwconfig
$ iwlist wlan0 scan


When running the first command, you should see additional information next to “wlan0″ or a similar device. When running the second, you should see a list of all available networks within range. If you do NOT, then you may not have set it up correctly. Refer to the wiki and driver documentation for more information.

The problem only is, it is not yet set up. So, let’s get to that. In the Module directory of the tarball you extracted (if you haven’t closed the terminal you ran the make command in, you’re in the correct directory) there is a README file. Direct your attention to the “Configuration” section.

Wireless Configuration – GUI

It provides two options – a GUI or manual configuration. Let’s start with the GUI:

http://rt2x00.serialmonkey.com/wiki/index.php/Downloads

Download the graphical configuration tool. After you extract it, you will have to compile it:


$ ./configure.sh
$ make && make install


You may then run the command rutilt. If it does not recognize the command as root, try running it as a normal user. When needed, it will prompt you for your root password. Use the “Site Survey” tab and click “Scan” to list the available networks. Then, simply select one, enter the necessary information (such as the key, if you have one) and you should be on your way!

Wireless Configuration – Manual & Start on Boot

I noticed that when I upgraded my kernel to 2.6.27 and used the built-in driver rather than the one discussed above, the GUI tool no longer worked. I wanted to abandon it anyway – I didn’t want to set up my configuration every time I started my computer. I wanted it to start up automatically.

I referenced the following link from the Gentoo documentation:

http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=4&chap=4

Take a look over it and decide what method you would like to use. I decided to go with wireless-tools. In the example below, I am using DHCP to keep things simple. If DHCP works for you, then you can get into manually configuring your IP address. Again, refer to the documentation for more information, as this is just an example and provides little explanation.

In the example below, the ESSID I’m attempting to connect to is “Gerwitz Wireless Network” which uses an open WEP ASCII key. I replaced my actual key below with “XXXXX”.


$ emerge -av wireless-tools
$ vi /etc/conf.d/net

—–

/etc/conf.d/net:

modules=( "iwconfig" );

key_Gerwitz_Wireless_Network=”[1] s:XXXXX key [1] enc open”

preferred_aps=( “Gerwitz_Wireless_Network” )

config_Gerwitz_Wireless_Network=( “dhcp” )
fallback_Gerwitz_Wireless_Network=(” 192.168.1.10/24″ )
fallback_route_Gerwitz_Wireless_Network=( “default via 192.168.1.1″ )

—–


$ /etc/init.d/wlan0 restart
* Caching service dependencies ... [ ok ]
* Bringing down interface wlan0
* Bringing up interface wlan0
* Configuring wireless network for wlan0
* Scanning for access points
* Found "Gerwitz Wireless Network" at 00:15:E9:76:1A:EE, managed, encrypted
* Connecting to "Gerwitz Wireless Network" in managed mode (WEP enabled - open) ... [ ok ]
* wlan0 connected to SSID "Gerwitz Wireless Network" at 00:15:E9:76:1A:EE
* in managed mode (WEP enabled - open)
* dhcp ...
* Running dhcpcd ...
wlan0: dhcpcd 4.0.1 starting
wlan0: broadcasting for a lease
wlan0: offered 192.168.1.103 from 192.168.1.1
wlan0: checking 192.168.1.103 is available on attached networks
wlan0: acknowledged 192.168.1.103 from 192.168.1.1
wlan0: leased 192.168.1.103 for 10800 seconds [ ok ]
* received address 192.168.1.103/24 [ ok ]


Remember to replace “wlan0″ with your interface. It should now start up on boot.

Granted, this guide does not cover everything – it is simply to help you to get your card working.

So, for those of you who have this problem – start by plugging it into a wired connection and updating your repositories (sudo apt-get update). Then in System -> Administration -> Hardware Drivers, the driver for your wireless device should be listed. Simply install it and restart and you should be good to go.

After debating whether or not to return it, I decided to keep it. v2s are out now, so v1 I assume will be discontinued – RockBox will eventually support it. And I’d like to provide aid to the RockBox team however I can. Unfortunately I have not looked into the firmware so I will not be much help in the actual development, however I will provide whatever information I can regarding the player, as the dev team does not own any v2s.

Using the Sansa e200v2 Series on GNU/Linux

So, in deciding to keep it, I ran into a few problems. It was a bit frustrating, and in order to help save you guys some of the frustration, I’ll post some information on how to use it with GNU/Linux. Specifically, Ubuntu Gutsy.

Connecting to your PC

Right when my Sansa arrived, I had a big problem – Ubuntu didn’t seem to recognize it. Depending on your firmware version, there’s a couple ways to solve this. I assume this applies to other distributions as well.

Before you begin, you need to load the necessary module. When it could not recognize my device, I checked dmesg and noticed the following message:

[38018.977087] usb 2-3: new high speed USB device using ehci_hcd and address 6

Entering the following command in the terminal should solve the problem of your device not being recognized:

sudo modprobe ehci_hcd

You probably don’t want to run that command every time you restart your computer, so open /etc/modules in your favorite editor (I recommend VIM, but gedit may be easier for some) as root and add “ehci_hcd” to the list. For example:

sudo gedit /etc/modules

Check your firmware version:

1. Start your Sansa e200v2 and navigate to the “Settings” menu
2. Scroll down to “Info” and select it
3. Note your firmware version at the top (ex: V03.01.14A)

Firmware version 03.01.14A:
You must put the device into MSC mode:

1. Go back to the “Settings” menu
2. Select “USB Mode”
3. Select “MSC”
4. Connect your device to the PC with the supplied USB cable

Older v2 firmware versions (03.XX.XX)
You need to place the device into recovery mode:

1. Turn the player off
2. Slide the top button into the lock position (toward the headphone jack)
3. Hold the rewind button (|<<)
4. Plug the USB cable into the player and computer
5. Keep holding the button until your distribution recognizes the device (in Ubuntu Nautilus will display the device after it mounts)

If your device did not mount, please ensure you loaded the ehci_hcd module as discussed above. Run “dmesg” from a terminal to see any errors if it still does not work.

How to correctly disconnect

If you just pull out the USB cable from your device to disconnect from the computer after writing data, chances are you may lose something. If you have written data to the device, unmount the device before disconnecting the cable. Ubuntu users may use the following method:

1. Open Nautilus (if it’s not open you can go to Places – Computer)
2. Either on the left sidebar or, if you’re in “Computer”, in the main area, right-click on your device (it may be labeled “sansa”, “disk”, etc)
3. Select “unmount”
4. Wait until a balloon states it is safe to disconnect the device, then you may remove the USB cable.

You may also use the “umount” command from the terminal.

Upgrading the Firmware

Above I mentioned two types of firmware. If you do not have the newest version, I recommend that you get it (so that the USB Mode menu is available). To upgrade:

1. First download the V03.01.14A firmware from this website
2. Connect your device to your PC and place the firmware file into the root directory of the device (for example, /media/disk). The root directory contains the AUDIBLE, MUSIC, PHOTO, RECORD and VIDEO directories.
3. Disconnect your device from the computer (SEE ABOVE FOR THE CORRECT WAY TO DISCONNECT YOUR DEVICE)

Alas, No OGG support

I was rather annoyed and disappointed to see that SanDisk did not add OGG support in their v2 series. All my music I had converted to OGG format from mp3s and I had deleted the old mp3 files. So, I had to convert all of them back (I still keep them in OGG format on my computer) in order for the Sansa to play them. Once RockBox works, out with the mp3s again.

Copying Music to the Device

Once your music is in MP3 format, you may copy it to your device simply by placing it into the “MUSIC” folder. You may organize the music however you wish – feel free to place them in their own subfolders. As long as they are within the MUSIC directory, Sansa will recognize them.

Note that, for users who use MTP mode (Windows users or Linux users with MTP support), those files are not visible in MSC mode. Similarly, files in MSC mode are not visible in MTP mode.

Deleting Music from the Device

In GNOME (I’m unsure with others), when you delete a file, it places it into a trash folder (unless you delete it with the “rm” command or use the Nautilus delete command rather than “Move to Trash). The files will not be removed from your device if you simply pull the USB cable, but the device will no longer list the music. So, it’ll be taking up space, but will be in a hidden folder (.trash). So, use the above method to properly disconnect from the computer. If you do so, it’ll prompt you to empty the trash on the device.

Music Metadata (Song Title & Track Order Problems)

You may notice that some of your music isn’t properly displayed. The title, artist, etc may be displayed as “Unknown”, or the title may be the filename. This was something that had frustrated me for a while. So, I have a fix for you.

Download EasyTag (below step for Ubuntu users):
sudo apt-get install easytag

Once you have EasyTag installed, run it (for Ubuntu users it’ll be under “Applications – Sound & Video”). Don’t get too carried away yet. This is the part that frustrated me. If you try anything now, you may still have some problems. You’ll be able to save the track titles, artists, etc, however the track number will not properly save. So your tracks will be out of order. This is because the firmware does not support ID3v2.4, which is the default for EasyTag.

1. Go to Settings – Preferences
2. Select the “ID3 Tag Settings” tab
3. Select “ID3v2.3″ for Version
4. Click the “Save” button

Now we can get to work. EasyTag will attempt to get as much information as it can from the filenames and other sources, so you should not have to enter much, if anything, by hand (I didn’t have to).

1. On the left, navigate to your device’s MUSIC folder
2. Wait very patiently while EasyTag retrieves the songs. This may take a while if you have a large number of songs with long filenames.
3. All the songs listed in red have to be saved. Check through the list and make sure EasyTag generated them correctly and make modifications as needed. Or, just skip this step if you’re lazy and trust EasyTag’s skills.
4. Select “File – Save File(s)” or click the corresponding button in the toolbar
5. Don’t forget to unmount before disconnecting the USB cable

Tada! You should now have properly named songs and correct track listings.

Album Art

This one also bugged me. Some other sites suggested using EasyTag to embed the album art in the MP3 file itself, but it never worked for me. So I figured out some alternate solutions. The Sansa was designed to work with Windows Media Player, so I looked at some old folders back from when I used Windows, before I ditched it for GNU/Linux. It would save the album art as “Folder.jpg”. So I copied Folder.jpg to the folder containing the album I wanted art for on the device, and sure enough, it worked!

1. Organize the tracks into folders for their albums
2. Get a hold of the album art for your tracks. I use Exaile as my media player, so I simply went to “.exaile” in my home folder and retrieved the album art from there.
3. Place the album art in the folder containing the tracks for that album, and rename the file to either “Folder.jpg” or “Album Art.jpg”. Case-sensitive.

Enjoy your album art

Playlists

Yes, the v2 series supports M3U playlists! In EasyTag, you can generate a playlist by selecting files and clicking “Write Playlist…” in the toolbar. Save it anywhere in the MUSIC folder – you may also save them in sub-directories.

Rockbox Development Progress

I’ll add more information on the Sansa if I can recall what else I had looked into. However, my true interest is in RockBox. Therefore, you can track the progress via the following links:

http://www.rockbox.org/twiki/bin/view/Main/SansaE200v2
http://forums.rockbox.org/index.php?topic=13961.0
http://forums.rockbox.org/index.php?topic=14064.0

Good luck!