Camera Woe

Ok, the Kodak Easy Share digital camera still won't connect to Ubuntu.  The front end photo management software (such as F-Spot) will not pull images from the camera, and I typically get an error " Error initializing camera: -60: Could not lock the device" even when trying to open.

I've seen some references to applying camera.app via synaptic (done that) and also about elevating user rights for the device (have not tested that).

But, the most promising so far is this, which I will try this evening and see if it provides any solutions.

Apply to U9.04 and Kodak DX7590 = OK ********************************

sudo gedit /usr/share/hal/fdi/preprobe/10osvendor/20-libgphoto2.fdi
Search for "Kodak DX7590" (or your camera model)
Put in XML comment of this paragraph =

Reconnect your Kodak DX7590

Harder than it looks

I fully sympathize (empathize??) with people that maintain a weekly blog, let alone a daily blog.  I started this year to post some thoughts weekly.  And did fairly well for January I thought.  But, now February has come and gone and I didn't post a thing.  

Yes, work was a bit busier than normal, but you'd think I could squeak out a few minutes here and there.  I will try harder from now on though, and have lined up a few topics that should keep me going for a while.  Personal technology pains that I've had to deal with.

We'll see if I can time manage better as I go forward.

Temetum Lusus

Still working my Ubuntu 9.10 system into shape, and playing games on it to wile away the hours.  I've found some things that work very well, and some disturbing things as well.

The very well.  Again I wanted to see about pushing the video card a little bit.  I wasn't looking to find a FPS game to prove things out, I just wanted to see something that had 3D graphics, and would allow me to interact with the environment.  And, since it was/is a test I don't want to have to pay for it.

A little bit of searching, and I stumbled on Secondlife.  And found, I didn't have to fiddle with a windows installer under Wine.  Not saying anything bad about wine, but if there is a native client for anything, be it game or other app, it should be better than forcing it through a secondary system.  So, install this application is as simple as extracting the tar.bz file and then executing the startup script.

And, everything seemed to work right off.  Except. (there always is an expection)  It was apparently written specifically for RedHat, or at the very least a system that had KDE and not Gnome.  First things first, setup of your account is done through a web page, and not the viewer client.  So that done I start the client script and I see several errors flying by, a little worrisome, but the login is there.  Pressing on, I actually get into the system, and it appears that everything is rendering fine.  Since this is essentially a huge 3D rendered environment made for user interaction and chatting I wasn't really sure what to check out.  So, I went through the supplied tutorials, and found right away that my system would not play in game video's or in game sound.  (heavy sigh)

Referencing their secondlife wiki, and since this client is still beta release, I guess I shouldn't be too upset.  I verified that all the pre-requisite support software was loaded (for example minimum gstreamer 0.10) But in the end I find that there is a simple script setting commented out because it is still unstable.  Basically, review each of the known problems and solutions in the wiki.  For me just "uncomment the 'LL_BAD_ESD' line in the 'secondlife' script" and then going into the environment setup of the client to allow the streaming video and audio to flow through was enough.

The Disturbing.  And now to what I consider a disturbing, and as yet unexplained issue.  In facebook, there are a lot of games.  Most of them flash based, some of them interesting enough to play.   I had been having issues with them for as long as I could remember, and always just chalked it up to poor programming on the game writers part, or incompatibility with the supplied linux flash program.  The crux of this happens in FireFox, while accessing any flash game that opens a sub menu within the game itself.  Be this simple things like the poker games, or the farming games, or any of the various others.   If you go to open this sub menu, you get a cut-off weirdly truncated view with no active boundaries.  They just plain do not work.

I have found, purely by accident, and frustration that if I use the mozilla offshoot "Seamonkey" instead of the Ubuntu approved and supplied "FireFox" I have no issues at all.  And, after verifying support apps, I find that they are both running the same flash version.  I have gone through the typical troubleshooting as outlined on the firefox site, but no plugin or other add on appears to be the culprit.  Simple fact is though, it breaks in FF and it works in Seamonkey.   go figure.

Et Tu Printerus?

Printing under Ubuntu (under any flavor of Linux I'm sure) is not always as expected.  If its your local machine, with a directly attached printer, not that bad.  Like any other OS, you need to have the proper drivers, and luckily with the current state of driver development, many printers are supported.  Thought I think I would probably check for fully supported printers before purchasing my next one.

I have the Epson All In One printer NX-400, and as a printer it works just fine.  But, as a scanner, it is unrecognizable.  So also, is its faxing capabilities from the computer. Stand alone, it appears to be fine, also plugged into a Windows XP system it all appears to be fine.  But, hooked to my main system running Ubuntu 9.10, it has its sore spots.

First off the scanner portion is totally unrecognizable.  Trying several driver options, and settings, gets nothing to see.  Good thing I still have an old flatbed scanner that I use, and it works flawlessly.  All I really wanted from this NX-400 was a printer, so I am not totally upset about the scanner/fax.

So, all is happy in whooville?  Of course not.  As soon as I have the printer working, I get requests from everyone else in the family to be able to print to it.  Sigh.  So that's three Windows XP systems, and a Windows Vista system I need to get printer sharing out to from my Ubuntu workstation.  Maybe its time to deploy a home centered server solution (another day).

Some of this has been lost in a haze, and I'm a little bit reluctant to hear the cries and gnashing of teeth of our new printer going offline. (If I were to disable everything and start over verifying each step that actually worked)  From what I recall I took the first step of getting my printer working locally, and for that I assumed it needed to have the latest CUPS installed.  Fairly easy procedure under Ubuntu

sudo apt-get install cupsys cupsys-client

So now, right or wrong, I think I have the printer ready.  In order to configure my specific printer I have to start the Printer Configuration Tool which can be found under System ->; Administration ->; Printing.
Clicking the New Printer icon, you go through the simple dialog steps of configuring your printer, and if luck holds your printer is known by Ubuntu, and can be chosen from the pick list (If not, then a round of searching for apropos drivers will be needed, or buying a printer that is more linux compatable).  Anyway, I find my NX-400 in the list, and go to add, and Apply the changes.  (The install option in these dialogs is for installing a driver from a download, or external media.  but, most modern printers are already available and this step is typically not needed)  So, now I have a local printer, it shows as "Ready" in the Printers display, and all looks good.

Now to make my workstation serve out this printer as a sharable resource. Going back to the Printer Configuration dialog window, then on the menu bar selecting server and then settings to open up the basic server sharing configurations.


Since this is my workstation, and not a dedicated server, I decided to choose the two options Show printers shared by other systems and Publish shared printers connected to this system and then under the printer properties page I made sure the option Shared was set and click Apply.

On each of the Windows computers in the house network I ran through the following simple setup.

1. Control Panel -> Printers -> Add Printer
2. Use the Add Printer Wizard
3. Add a network printer
4. Choose connect to printer on the internet and type in the following format http://PRINTSERVERNAME:631/printers/PRINTERNAME (where the printservername is the IPaddress or DNS name for my Ubuntu workstation sharing out the printer and the printername is the name of printer being shared)
5. On the next screen choose the correct driver for this printer.  (In my case, Windows did NOT know what driver to use and I had to go download it from the Epson site, and come back to this step)
6. Print Test page

Interesting point here, is that all the printing worked until the Ubuntu system got rebooted, then no printing worked at all.  I verified the sharing options, and all previously installed components, and even checked to see if the CUPS daemon was running.  And, I even verified that my workstation reboot just didn't give me a new IPaddress from DHCP.  Yet it wouldn't print.

The fix in this case was to install Samba

Installing samba was nothing more than installing the following through the synaptic manager, and then modifying the conf file to allow for printer sharing.

System -> Administration -> Synaptic Package Manager    And then enter in samba for the search term and apply to install.

So once complete, open the /etc/samba/smb.conf and look for the section  on printers:

sudo gedit /etc/samba/smb.conf

[printers]
   comment = All Printers
   browseable = no
   path = /var/spool/samba
   printable = yes
   guest ok = yes
   read only = yes
   create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
   comment = Printer Drivers
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   guest ok = no

And then restart samba

sudo /etc/init.d/samba reload

From here the Windows workstation is able to see the printers again, and has not had any problems losing configurations.

The whole ordeal to get the CUPS system working with a Windows client is weird and yet satisfying once its working.


Installing CUPS on Ubuntu
Installing SAMBA on Ubuntu

Far and away

I have spent the last couple of weeks adding and getting some frustrations to adding new applications to my Ubuntu 9.10 desktop system. The following have been installed and met with varying degrees of success.

• Online games 
• GuildWars
• Dungeons and Dragons
• Eve Online
• Secondlife
• facebook browser flash games
• seamonkey
• gpodder
• Kodak digital camera 

Needless to say, these have revealed to me that, even though I am a proponent of linux systems, and I find many of the tools and server level applications critical to my use within a business environment.  These end user, recreational applications on relatively modern equipment and newer released distribution have proved to be less than glowing.

To start in this posting, I'll hit one of my high points.  Installing GuildWars MMORPG.  Ok, I knew this was a Windows released game, had some higher level graphics requirements, some networking needs, and did periodic system updates while ingame.  I expected some pain.   I also knew this would require either a vmware solution to run under a copy of Windows (not a viable solution in my list), or purchasing the Cedega or Codeweavers solution that's been tuned for gaming on linux, or the repo included Wine solution.  Since I didn't want to mess with virtual machines, and the inherent problems there, and I didn't want to begin this endeavor by paying for a subscription service, I decided to try Wine.

So, Wine, install simply and easily via the Ubuntu repository using the Synaptic manager.  I have to say, that everything I've found so far is extremely simple to install and update if its in a subscribed repo.  Basically startup Synaptic, do a quick search for what I want, hit one checkbox marking for install, then apply.

Once the base Wine updates were completed, I went out to the winehq site and did a quick check on the status of GuildWars.  According to the DB there, this application is listed at a "platinum" level for all major linux distro's. Which according to Winehq Platinum is "...Applications which install and run flawlessly on an out-of-the-box Wine installation..."

Now on to the real fun, seeing if this commercial Windows game would really install.  Inserting the install CDrom media, and using gnome gui browser to locate the setup.exe application.  Once found, a right click on the program opened a menu option allowing to run under wine.  This initiated what appeared to be a typical installation session.  At the end, I have a new desktop entry, and a shortcut in the wine/applications menu.

Launching this proved to hold no surprises, an initial installation of this game requires patience as it first will download all patches since the install media was released.  Plus any world updates.  This alone took over an hour, but would be the same whether this were Windows or not.

But, once completed, I was able to load and play the game without any problems.  I had full sound effects, and was able to adjust the various display options without any snags.  And, running at a high level for graphics appears to have no slowdowns of FPS loss that was noticeable. 

I just wish my other forays into setting up commercial games was as successfully easy to do.  I will hit on the highpoints and lowpoints to the installation of those in a later posting.

winehq - Run Windows applications in Linux, BSD, Solaris, and Mac OS.
Quick link to the GuildWars installation instructions within winedb.
Ubuntu Linux
Cedega Transgaming application
Codeweavers cross over games application

Ab initio

From the beginning, seems little less overbearing than saying what first came to mind for a first posting on this blog (and I won't go into that now, seriously bad religious overtones). But, since its a new year, I'm in a new job with less restrictions on my technical knowledge, and I finally let loose some personal money and got a new computer. This title seems apropos.

I retired a very old, yet functional Compaq 5000 seris computer (1.1Ghz AMD Athalon, 512Mb ram, 40Gb hard drive) Originally bought with Windows ME, and most recently running a very respectable implementation of Ubuntu 9.04 where I even got the Compiz portions to work after installing an old Nvidia 5950 AGP video card. Its replacement came because of the inability to run simple yet graphically taxing games (like guildwars), online video streaming (like Youtube), and online music (like Pandora). It is still available for boot, just not a primary system anymore.

In all it was nice to push the limits of really really old hardware and make it functional. Yet all good things must come to and end, computer systems age faster and this one was well past its life expectancy.

So, in with the new. I work on servers every day, sometimes having to deal with hardware, but for years that wasn't an area of my expertise. Too many things to remember, and worry myself over items which others can do very well for me. But, this was to be a basic system for home use, not a multi-user server, nor a platform for playing with virtual machines. AND, not a MAC or Windows system. SO, I went barebones. (figured I couldn't have forgotten everything on installing computer hardware)

There are a lot of companies selling these kinds of systems, pick the one you like. The prices I found for an adequate upgrade machine were fair. And I finally decided on a cheap system based on an MSI board and AMD chipset.

Unboxing was fun, and other than a bit of trepidation over the tangle of wires on the cases power supply, the special cooling fan I got was huge, and the fact that I had a SATA DVD drive and no data cable. Everything was fine.

Ok not so. Not having done hardware in years, I was probably more careful than I typically am when dealing with servers. I carefully reviewed each of the parts, simple as they are

• ATX system case with 450W PSU
• MSI K9N6PGM2-V Mobo
• AMD Athalon 64 X2 5000+
• Corsair XMS2 2Gb RAM
• LG DVD writer
• Seagate Barracuda HD
• MSI 9500 Video card
• Ultra Wind AM2 cooling fan

Installing the motherboard first, I opened the case and all the associated hardware, and became concerned because there were a series of paper washers included. I had never seen these in the systems, but like I say, it has been years. Maybe something had changed. Quick Google search I find people talking on everything from these being useless(1), to being critical(2) to preventing electrical short circuits(3). Uh yea. Last thing I'd use as an electrical insulator is paper. And, if the manufacturer of this motherboard (Mobo) had power runs so close to a mounting hole that the mount screw would short it out, I didn't really want that Mobo.  But, I'm thinking that it can't hurt for vibration and put them in place anyway.

Getting all the brass standoffs placed on the new case, to line up with the ATX Mobo mounting holes wasn't too hard. Just have to pay attention to the included instructions, try not to be distracted by the poor English translations, and don't be afraid to actually put the hardware together.

Next I go for the CPU(4). Easy installation, again just following the included directions, line up the pins and making sure I am grounded before touching anything. Carefully slipping it into place, and sliding the mounting latch into position.  Interesting note on these, it says it can handle only a limited number of insertions.  My best guess there is due to pin crimping, or possible bent pin damage.

So, now I'm looking at this huge CPU cooling fan and I realize the memory must go in before this does as I won't be able to put memory in afterwards. Even with the most nimble fingers reaching under the cooling fins, it would just not fit.  Fine, next is memory then.

Memory installation(5) was relatively simple, with the hardest part being the act of pushing in hard enough to latch down the DIMM, yet not so hard as to damage the Motherboard from flexing it. Seems the board should possibly have better standoffs to support it in that area.

And now the cooling fan(6). Might be a great CPU fan, but after much contortions, and some cut fingers (the copper fins are very sharp) I find that it is installed, but touching the top of my memory stick! Ok, fallback, remove this extra fan, and use the included cpu cooling fan as delivered with the AM2 cpu.  Much smaller, not as high on the "looking cool" scale, but should be effective.

Now, placement of the hard drive, and DVD drive required a minor bit of dis-assembly of the case to allow for mounting screws for each, and easier routing of the power and data cables.  Nothing terribly difficult either, but not oultined in any instructions I found included.  Oh one minor point, if the Mobo has SATA couplings, the Hard Drive and DVD drive is SATA, make sure you have data cables or a source to get some if they are not included in the kit.

The video card(7). Installation again, very simple, following the supplied instructions and some online references.  No surprises here.

And last, the power, control, and data cables needed to be hooked up. Luckily the included manual on the motherboard is very thorough in spec, if not completely clear (to someone that doesn't do hardware everyday) on what plug components need to go where. And, after many careful references back to said manual in the "measure twice - cut once" frame of mind, I finally got everything plugged and ready for power.

First power is always scary.  You are second guessing yourself all the way, "did I leave a critical line unplugged", "Are any of these line reversed", "did I drop a screw and its sitting just out of site, ready to short everything".  And, of course first power here resulted in nothing, not even a BIOS post screen.  Just that sickening single "beep" of which the supplied manual had no reference.

Sigh. (in the end, after backtracking into component by component troubleshooting mode, I got it ready for operating system installation)

Now, there were a few items of interest that didn't go as expected (besides the cooling fan)

1. The case power supply wiring harness was strung out so at least one of the control cables from the front of the case would not reach the spot on the Mobo to plug it in.  I found that the cable was long enough if it didn't go through an oddly placed hole in the front plate. Route along a side bar, and over the Mobo and it had plenty of length.
2. The cables for the front panel electrical did not match up clearly for this motherboard, in either color coding or etched numbers.  But some deductive reasoning and physical wire tracing got all of these installed. Yet I have not found any completely clear explanation whether anything special needs be done to use the USB1 or the USB2 plugs. (Plugged in USB2 as I wanted the higher speed specs - hoping the BIOS was configured to auto detect)
   
3. The memory installation failed, possibly due to trying to make the extra large cooling fan work, didn't get seated properly and the initial power up resulted in nothing but a post beep indicating a memory issue. Reseating didn't seem to help, and I thought I damaged the DIMM.  So I bought a replacement 2Gb and it booted right up. Deciding that maybe it was a fluke, or some sort of configuration detection problem I installed the old one as well and have a machine with 4Gb ram instead. (bonus)
   
4. Lastly, the keyboard I had available is an older usb cable keyboard(8) (Scavanged from the retired Compaq 5000). This keyboard did not want to be recognized from any of the usb sockets. Even though the Logitech usb wireless mouse had no issue from the start. And, yes, I did get a ps2 plug keyboard to get into the bios settings and set the usb mode to "legacy" with no real success. This issue is still intermittent. Some times it boots and keyboard is non-responsive, and other times it is just fine. I have found that either I reset the computer to get keyboard (not the first best choice) or if I unplug the keyboard, and plug it back in will get it working again after boot time.
   

From this point on it was all Operating System (OS) installation(9), I assumed the Mobo BIOS was new enough, and I'd be able to update that later if needed. I typically don't worry over BIOS updates on servers unless there is a specific reason to update, so I figured this was a good route on a home machine as well. The plan now was to get Ubuntu 9.10 installed from an already downloaded and burned installation CD.  The choice of OS being along the lines of "make it simple, this is not a work machine, I want it to just work, and it will NOT be any flavor of Windows"

This OS portion of the system build has been completed, but like the hardware it had its own share of issues. Though I was pleasantly surprised to see the base install detected every bit of new hardware, and had no troubles connecting to my home ethernet. I'll go over those installation items in a later posting.

References:

(1) Motherboard paper washer reference 1
(2) Motherboard paper washer reference 2
(3) Motherboard paper washer reference 3
(4) Installing the AMD AM2 CPU
(5) Installing DIMM memory
(6) Installing AM2 cooling fan
(7) Video card installation
(8) Usb keyboard problem solutions
(9) Installing Ubuntu 9.10

Barebones Computer Kit Dealers
TigerDirect - OutletPC - Geeks - NewEgg - Dell - Hp - etc.

Welcome 2010

Yea, so everyone starts out the year this way (queue the loud cheering, heavy sighs, or whatever apropos expletive desired here).

As I go into this, I want to take a new front on things, and with this particular blog have more of a technical nature to it. Therefore I want it to cover these topic points with my own take on things. It may not always be correct (I am always open to learning a new functional way of doing things), but I will endeavor to always make it interesting.

• Linux
  
• Windows
• NetWare
• Identity Management
• ldap
• ldif
• html

Oh heck with the list, I'm going to talk about anything under the sun.

Comment Policy

Comments are always appreciated here - but some ways of posting comments are more appreciated than others, for example when they help me or help others.

That said, some guidelines need to be put in place.

Comments: Notes From the Edge of Spacetime is not responsible for any comments made by contributors in the Comments pages. However Notes From the Edge of Spacetime will exercise its right to moderate and edit comments which are deemed to be offensive or unsuited to the subject matter of this site.

• As of this time, only registered users are allowed to comment.  No anonymous commenting is allowed.
  
• Please always post comments about specific issues under a post discussing that issue. If you have a technical comment or question, comment under a post with an appropriate title. 
• A comment which does not add to the conversation, runs off on an inappropriate tangent, or kills the conversation may be edited, moved, or deleted.
  
• The comment form must be filled in with a proper or legitimate sounding name and URL. Comments using keywords, spam-like URLs, or suspicious information in the comment form will be edited or deleted. Any comment assumed to be possible comment spam will be deleted.
• All email, snail mail, phone numbers, and any private and personal information posted in any comment will be deleted as soon as possible to protect the privacy of the commenter. To prevent such editing, never share this private information within the blog comment.
• This blog is “family friendly” and comments which include offensive or inappropriate language, or considered by to be rude and offensive, will be edited or deleted. Play nice. Be civilized.
• No personal attacks are permitted in this blog’s comments. You may question or argue the content, but not attack me, nor any other commenters.
• The blog owner, administrator, contributor, editor, and/or author reserve the right to edit, delete, move, or mark as spam any and all comments.
• All comments within this blog are the responsibility of the commenter, not the blog owner, administrator, contributor, editor, or author. By submitting a comment on my blog, you agree that the comment content is your own, and to hold this site, Notes From the Edge of Spacetime , and all subsidiaries and representatives harmless from any and all repercussions, damages, or liability.

With those guidelines in mind, I'll look forward to seeing your comments.