The MF4150 is still running well. The only snag seems to occur when it's installed paper size (letter) does not match the document size (A4). However that can be cured by a restart of the printer and printing application (i.e., LibreOffice Write in this case).

On another note, our thoughts and prayers go to the people of Turkey in the wake of this most recent earthquake. Friends with whom I've trained have already received their deployment orders from FEMA and are en route with search dogs. One can only hope that all the missing are accounted for and there is nothing for them to find.

Peace.

Steve

Victory!

MF4150 is now working.  Lisa and SW, I owe you both . . . big time!

In executing the commands in SW's last post I found that the last couple of files did not get copied over.  Took care of that and finished running SW's commands and voila . . . I gots me a printer!

Thanks again!

-Steve

Well, just when I thought I was getting somewhere, I'm stymied again.

Everything seems to have installed properly, but nothing prints.  Every test printer or document I send apparently is logged by the system somehow because the test pages produce a message "Test Page submitted as job 10" (For the last one. I've tried seven test pages and three documents).

Device URI is: usb://Canon/MF4100%20Series?serial=SDF690313517B&interface=1

What next?

-Steve

Thank you both, SW and Lisa!  I've executed all the steps you describe.  Lisa, I managed to get rid of the usblp error messages.  SW, I was able to drag the new folders into the root directory, and drag the contents of the existing folders (usr, lib, etc.) into their counterparts in the root directory.

The Printer Configuration applet recognized the MF41500 series as before, but there are still no MF4100 series (or anything similar) in the Canon drivers section in the New Printer listing.

Does anyone have any ideas where to go from here?

Steve

PS: Just to let you know, my impatience got the better of me, so I tried moving the files from the command line yesterday.  That didn't work, but soon thereafter I started moving some JPG files onto a USB stick and KDE suddenly when black.  Had to do a hard shut down. After that Pardus would only boot to the command line.  Attempts to start KDE from there failed, as did attempts to fix things with the Live and Installation DVDs.  Long story short, I reinstalled Pardus.  Thus the above attempts to get the printer working are on a brand new, squeaky clean install.  <sigh>

I've executed the rpm2targz on the two RPM files.  This yielded two folders.  They are:

etc, with subfolders
       cngplp
usr, with subfolders
       bin
       include
       lib
       local
       share

Please pardon my noobness, but to what directories do I copy these.  My best guess is that it would be their counterparts in the Root directory, but Dolphin won't allow me to copy them and won't start with root access from the command line (with a "sudo dolphin" command that is).  I've trying to execute the copies from the command line, but I'm just not getting it right.

Oops! The text file didn't make it here it is with just a tweak in the file name.

Hi Lisa,

Thanks for the reply.  The results of the "dmesg" command do not look like what you describe.  Instead there was a rather lengthy reply.  Because I am as yet far from qualified to interpret those results I've attached them in the text  file dmesg_output_21OCT11_1130.

When running New Printer in the printer applet a dialog box appears (see attached NewPrinterSnapshot_21OCT11_1146.jpg).  The fields are populated as follows:

Canon MF4100 Series -- Description -- A printer connected to a USB port.

Canon MF4100 Series (FAX) -- Description -- A printer connected to a USB port.

Serial Port #1 -- Enter device URI -- <Blank field>

AppSocket/HP JetDirect -- Location of the Network Printer -- Host: -- <Blank field> Port number: 9100

Internet Printing Protocol (https) -- Enter device URI -- https

Internet Printing Protocol (ipp) -- IPP Printer -- Host: <Blank field> -- Queue: /printers/ -- URI <Greyed out>

LPD/LPR Host or Printer -- Location of the LPD network printer -- Host: localhost -- Queue <blank field>

Windows Printer via SAMBA -- SMB Printer -- smb:// <Blank field> -- smb://[workgroup/]server[:port]/printer -- Authentication -- <Radio button checked> Prompt user if authentication is required -- <Radio button unchecked> Set authentication details now -- <Greyed out fields -- Username, Password, Verify>

Other -- Enter Device URI -- <Blank field>

When I select "Forward" from the "Canon MF4100 Series -- Description -- A printer connected to a USB port window" I get a list of printer makes.  Choosing Canon, I get a list of Canon models, but none are in the MF series (your Pixma is, though).

I wonder if I can get away with choosing an ImageRunner of the same vintage as the MF4150?  Might they share the same UFRII driver?

Thanks again,

-Steve

SUCCESS!

Based on the content of another post in this forum I decided to remove the laptop's second hard drive. Voila, Pardus installed just fine.

Happily working with Pardus!

-Steve

Repeated attempts to install Pardus 2011.2 have failed on my Dell E4310 laptop
(i5 processor with 4GB RAM, two 500GB hard drives, and Intel graphics). The
laptop was a dual-boot Win7-Mint11 machine. I deleted the Mint11 partition and
attempted to install Pardus and was met with the Unhandled exception -- cannot
find partition instance sdb4 error message (backtrace below). Installation checksum was verified with MD5sum.

As a test I started both Ubuntu 11.04 and Mint11 installs through the partition
locating phase and both identified the partitions and 107GB of unallocated
space intended for Pardus. I aborted both test installs (because i REALLY want
Pardus on both my machines).

Reproducible: Always

Steps to Reproduce:
Steps taken:
1. Run Pardus installation from CD
2. Validate packages
3. Attempt identification of hard drives (fail)
Actual Results: 
cannot find partition instance sdb4
<class 'yali.storage.devices.partition. PartitionError'>

Backtrace:
   File "/usr/lib/python2.7/site-packages/yali/gui/ScrDateTime.py", line 221,
in startStorageInitialize
   ctx.storageInitialized=yali.storage.initialize(ctx.storage, ctx.interface)
  File "/usr/lib/python2.7/site-packages/yali/storage/_init_.py", line 35, in
initialize
    storage.reset()
  File "/usr/lib/pythin2.7/site-packages/yali/storage/_init_.py", line 316, in
reset
     self.addDevice(device)
  File "/usr/lib/python2.7/site-packages/yali/storage/devicetree.py", line
1617, in populate
    self.addDevice(device)
  File "usr/lib/python 2.7/site-packages/yali/storage/devicetree.py", line
1048, in addDevice
     device-self.addPartiton(info)
  File "/usr/lib/python2.7/site-packages/yali/storage/devices/devicetree.py",
line 938, in addPartition
      exists=True, parents=[disk])
  File "/usr/lib/python2.7/site-packages/yali/storage/devices/partition.py",
line 102, in_init_
      raise PartitionError("cannot find parted partition instance", self.name)

Can anyone point me toward guidance on installing a Canon MF4150 multifunction laser printer in Pardus 2011.2. I've struck surfing eh web for solutions.  I've downloaded Linux drivers from Canon's website, and once extracted there are both DEB and RPM versions, but I'm at a loss as to how to install from there.

The printer configuration applet correctly identifies the printer as a Canon MF4100 series, but when I hit Next there are no drivers for it.

Any help would be greatly appreciated.

-Steve

Thanks for the quick reply with information and links. 

I will post a separate thread if the next installation attempt fails.

Greetings where can I find the proper checksum values for Pardus-2011.2-Cervus-elaphus-i686.iso? Using MD5sums both copies of separately downloaded ISOs I have show a value of:

ba03d549c1252c5fd12b862857ba7ffa

I'm having trouble with one of my Pardus installations (2011.2 32-bit).  The iso seemed to burn properly and install on my desktop machine. However, on my Dell E4310 laptop using the same DVD installation hangs with an "unhandled exception" error during the search for available partitions. Before I wade into the problem from the hardware end I'd like to make sure my iso is clean and complete.

Thanks,

-Steve