Bugzilla – Bug 212234
YaST2 printer module deletes /dev/lp0
Last modified: 2007-03-07 15:04:45 UTC
When starting the printer module of Yast2 the device /dev/lp0 is deleted and a test of the newly installed printer is not possible. After rebooting the device is present again. Nevertheless the printer setup with the detached printer is possible
please attach a log files
It seems that lp module is unloaded
NO! The module is loaded, the device is deleted! parasol:/tmp # lsmod | grep lp lp 14756 0 parport 36936 2 parport_pc,lp parasol:/tmp # yast2 Command: /sbin/yast2 printer & [1]+ Stopped yast2 parasol:/tmp # bg [1]+ yast2 & parasol:/tmp # lsmod | grep lp lp 14756 0 parport 36936 2 lp,parport_pc parasol:/tmp # l /dev/lp0 /bin/ls: /dev/lp0: Datei oder Verzeichnis nicht gefunden
I'm suffering similar problem too. SuSE 10.2 i586 GM. Updated from 10.0. Printer HP Laserjet was working properly before the update. No problems in the update till first time I needed to print something in OpenOfffice: I got a print error. Well, I guessed I needed to configure again the printer. Used yast2 to configure and first surprise: It detected a wrong printer I never had. Nothing about my HP printer. Then investigating I saw that /dev/lp0 has gone. After reisntall devs rpm this is what I get: alcazaba:/dev # la lp* crw-rw---- 1 root lp 6, 0 nov 25 22:38 lp0 crw-rw---- 1 root lp 6, 1 nov 25 22:38 lp1 crw-rw---- 1 root lp 6, 2 nov 25 22:38 lp2 Yes, it seems the device is there. Then I discovered lp is not used :( alcazaba:/dev # lsmod | grep lp usblp 17792 0 usbcore 114896 5 usb_storage,usbhid,usblp,ehci_hcd,uhci_hcd and about parport alcazaba:/dev # lsmod | grep parport parport_pc 42084 0 parport 39752 2 parport_pc,ppdev If I try to check the hardware with yast2 /dev/lp0 disappear. I suposse something was not upgraded properly. Any sugestion?
Hi Again, I uploaded lp using modprobe alcazaba:/dev # lsmod | grep lp lp 15652 0 parport 39752 2 lp,ppdev usblp 17792 0 usbcore 114896 5 usb_storage,usbhid,usblp,ehci_hcd,uhci_hcd And AGAIN yast2 deleted /dev/lp0 after a try to configure the printer. I forgot to tell what printer it found. Is an USB printer CANON-FP-L170/MF350/L380/L398 I never heard or seen this printer !?
sounds really strange ;-( could you provide yast logs http://en.opensuse.org/Bugs/YaST with "hwinfo --printer" output?
Well, I replaced /dev/lp0 using rpm devs. Then alcazaba:~ # la /dev/lp* crw-rw---- 1 root lp 6, 0 nov 25 22:38 /dev/lp0 crw-rw---- 1 root lp 6, 1 nov 25 22:38 /dev/lp1 crw-rw---- 1 root lp 6, 2 nov 25 22:38 /dev/lp2 And now I check the printer info alcazaba:~ # hwinfo --printer 20: USB 00.0: 10900 Printer [Created at usb.122] UDI: /org/freedesktop/Hal/devices/usb_device_ffffffff_ffffffff_noserial Unique ID: FKGF.mZowMakqrN1 Parent ID: pBe4.+SlVeP8a1eC SysFS ID: /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0 SysFS BusID: 2-1:1.0 Hardware Class: printer Model: "Canon FP-L170/MF350/L380/L398" Hotplug: USB Vendor: usb 0x04a9 "Canon" Device: usb 0x2655 "FP-L170/MF350/L380/L398" SubVendor: "Canon" SubDevice: "FP-L170/MF350/L380/L398" Serial ID: "2251CCkM" Driver: "usblp" Driver Modules: "usblp" Device File: /dev/usb/lp0 Device Files: /dev/usb/lp0, /dev/usblp0 Device Number: char 180:0 Speed: 12 Mbps Module Alias: "usb:v04A9p2655d0000dc00dsc00dp00ic07isc01ip02" Driver Info #0: Driver Status: usblp is active Driver Activation Cmd: "modprobe usblp" Config Status: cfg=yes, avail=yes, need=no, active=unknown Attached to: #16 (Hub) And then, /dev/lp0 IS GONE alcazaba:~ # la /dev/lp* crw-rw---- 1 root lp 6, 1 nov 25 22:38 /dev/lp1 crw-rw---- 1 root lp 6, 2 nov 25 22:38 /dev/lp2 I can sure you I have not any usb printer ;-)
Er, I need some more cofee, actually the Canon device found is a fax i had conected in a usb connector at the backside of the system, almost inaccesible to me. The fax is in other room just beside mine :(. Sorry, how can I be so stupid, I was thinking in a printer. But still I cannot figure out why yast deletes /dev/lp0. The lp module is loaded.
You still didn't provide yast logs (comment #6) ...
Finally I found the source of problems, I think!. In one of my several re-start the system I discovered a fatal-error in modprobe in booting logs related to parport_pc module. So I read carefully the file /etc/modprobe.conf This was the culprit line: options parport_pc 0x2f8 io=0x378 I commented it and uncommented this one options parport_pc io=0x378 irq=none,none After reestart error messages disapeared and /dev/lp0 was regenerated :-). And the printer is working well again. I don't know why that line in /etc/modprobe was there. May be in one of my zillions of panic attempts to configuring the lp0 port un yast2->printer module. I missunderstood the comment #6 and didn't provide yast2 logs, sorry again. Must I now attach the logs?. y2logs.tgz has more than 3 MB.
No, I don't need yast logs now. But for future - there is wikipage about reporting and debugging yast, I don't know what is hard to understand. This bugreport is similar as #116655 >I don't know why that line in /etc/modprobe was there. May be in one of my zillions of panic attempts to ... That lines are not by default so I close it as an INVALID
I updated to openSuse 10.2 a few days ago; the problem of the disappearing /dev/lp0 (comment #3) is still present. So I think it's not o.k. to close this bug!
For me yast2 adds a mystery /dev/usb/lp0 which I can't delete. I do have a USB printer, but it is correctly configured elsewhere. This /dev/usb/lp0 appeared only when I changed the default printer. YAST2's printer setup is spooky.
Bryce: we are planing some changes to 10.3 (I hope to improving usability) But if you have ANY suggestions or comments, send it to me, please Driver is reloaded because of hwinfo --printer detection YaST can't do anything here (we need hwinfo) Steffen, it's yours - why lp kernel module is reloaded?
I can't do anything either. Reloading the parport* modules is the only way to trigger parport device detection. What exactly is the problem with that?
The problem is : parport in ECP mode doesn't work after rmmod & insmod https://bugzilla.novell.com/show_bug.cgi?id=116655 so when yast calls "hwinfo --printer" and lp module is reloaded, on some machines is parallel port broken But as you wrote you need to do it, I close it as a duplicate of that bug ;-( *** This bug has been marked as a duplicate of bug 116655 ***