That would explain why cups now hangs on the plug. If they disabled the parallel printer module in the kernel but  cups is still trying by default to load their LP_MODULE, well let the crying begin. That make perfect sense, because as part of the apt-get dist-upgrade the new 2.6.32-5-kirkwood was installed when my problem started.

thx

-mike

I think I have solved the problem. The issue was with LOAD_LP_MODULE defined in /etc/default/cups. It is set to "yes" which triggers the /etc/init.d/cups startup script to attempt to load a parallel printer module. I believe that when the attempt to load a module of a nonexistent device started the entire plug locked up, no ping, no login, game over.

Once I modifed 'LOAD_LP_MODULE=yes' to  'LOAD_LP_MODULE=no' in /etc/default/cups, I was able to execute "dpkg --configure -a" and complete the installation process. After that I was able to configure the print server and have successfully printed from all my home computers (Mac, Winbloze, Linux).

Mama is happy again !

-mike

Recently updated cups via apt-get only to have the plug hang/freeze/crash (no ping, no login). Since this plug acts mainly as a print server I reinstalled the OS (without cups) and once the install was complete reinstalled cups via the apt-get command. The apt-get install of cups once again freezes when the init script starts and dpkg is squawking about an interrupted install Here is the output:

root@sheeva2:/var/cache# dpkg --configure cups
Setting up cups (1.4.4-1) ...

Starting Common Unix Printing System: cupsd


The command line prompt never returns and every console/terminal I may have open is locked.

Anyone else having issues with the latest debian update of cups ?

-mike

Ok I found a solution in the Linux questions section of the forum

"update-initramfs error on Debian SID"

Apparently I was missing the uboot-mkimage binary,

# sudo aptitude install uboot-mkimage

-mike

Hi everyone,

As I am doing an apt-get I get this error msg.

update-initramfs: Generating /boot/initrd.img-2.6.32-5-kirkwood
cp: writing `/tmp/mkinitramfs_hgtqnY/init': No space left on device

Oddly /tmp is listed as Filesystem "overflow"
bailey@sheeva2 -> df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mmcblk0p2        1.6G  1.3G  274M  83% /
tmpfs                 252M     0  252M   0% /lib/init/rw
udev                  250M   92K  249M   1% /dev
tmpfs                 252M     0  252M   0% /dev/shm
/dev/mmcblk0p1        149M   22M  120M  16% /boot
overflow              1.0M  1.0M     0 100% /tmp

Normally it would be part of "/"

Any ideas why /tmp has gone astray ?

thx

-mike