LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 01-04-2014, 04:59 AM   #1
bobjusto
LQ Newbie
 
Registered: Jan 2014
Posts: 5

Rep: Reputation: Disabled
Question USB printer issues in slackware 14.1


Hi all,

since slack 14.1 all my USB printer don't work until i load "by the hand" the usblp module (modprobe usblp)
so far in 14.0 it worked!

I have profread all my rules in /lib/udev/rules.d, /etc/udev/rules.d
and i found this :
  • in 14.0 and 14.1 the rules are the same !
  • the usblp' module is loaded on printer' power up by the rule :
    DRIVER!="?*", ENV{MODALIAS}=="?*", IMPORT{builtin}="kmod load $env{MODALIAS}"
    (but don't work in 14.1)
    this rules is in /lib/udev/rules.d/80-drivers.rules (package udev-182-x86_64-7)
  • if i put in /etc/udev/rules.d a rule like that :

    DRIVER!="?*", ENV{MODALIAS}=="?*",RUN+="/sbin/modprobe usblp"

    it works , but it is awful (the usblp'module will be loading with all device ?)

I would appreciate any help.

Last edited by bobjusto; 01-04-2014 at 08:47 AM.
 
Old 01-04-2014, 11:58 AM   #2
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-14.1 on a Lenovo T61 6457-4XG
Posts: 3,970

Rep: Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936
Hi bobjusto and welcome on LQ.

Uncomment (remove the #) following line in /etc/rc.d/rc.modules
Code:
#/sbin/modprobe usblp

Last edited by Didier Spaier; 01-04-2014 at 12:01 PM. Reason: Forgot to say "Hi".
 
Old 01-04-2014, 01:42 PM   #3
bobjusto
LQ Newbie
 
Registered: Jan 2014
Posts: 5

Original Poster
Rep: Reputation: Disabled
yes i know that , but it's ugly , the usblp is always loaded ,even if all printers are powered off,

i want to load it only when it is powered on by using a rule ( as in former slackware)
 
Old 01-04-2014, 02:20 PM   #4
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-14.1 on a Lenovo T61 6457-4XG
Posts: 3,970

Rep: Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936
In any case once loaded (either applying an udev rule or otherwise), the kernel module will stay in memory even if you unplug the printer or power it off, as AFAIK there's no udev rule to unload it, so IMHO that doesn't make a big change...
 
Old 01-04-2014, 02:45 PM   #5
bobjusto
LQ Newbie
 
Registered: Jan 2014
Posts: 5

Original Poster
Rep: Reputation: Disabled
by the way that don't solve the issue ! why on the earth this rule don't work anymore in 14.1 ?
 
Old 01-04-2014, 03:20 PM   #6
ReaperX7
Senior Member
 
Registered: Jul 2011
Distribution: LFS-SVN, Slackware-14.1, PCBSD-10.0
Posts: 2,800
Blog Entries: 15

Rep: Reputation: 731Reputation: 731Reputation: 731Reputation: 731Reputation: 731Reputation: 731Reputation: 731
Ask Kay Sievers the maintainer of udev. He might know why rules get all borked with udev and it acts retarded from time to time. Then again, that's just udev.

Udev handles all hotplugging anymore so the driver will stay in the memory while cups and udev handle the device management protocols. It's either that or you learn the inner workings of kmod to load and unload drivers by hand.
 
Old 01-04-2014, 03:36 PM   #7
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-14.1 on a Lenovo T61 6457-4XG
Posts: 3,970

Rep: Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936
I think that your assumption "/lib/udev/rules.d/80-drivers.rules is the same, so we should see the same behavior" is wrong. Here is a diff of /lib/udev/rules.d/70-printers.rules beetween 14.0 (on the left) and 14.1 (on the right):
Code:
2,5c2
< ACTION=="add", SUBSYSTEM=="usb", ATTR{bInterfaceClass}=="07", ATTR{bInterfaceSubClass}=="01", TAG+="udev-configure-printer", RUN+="udev-configure-printer add %p"
< # usblp device add trigger (needed when usblp is already loaded)
< ACTION=="add", KERNEL=="lp*", TAG+="udev-configure-printer", RUN+="udev-configure-printer add %p"
< 
---
> ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ENV{ID_USB_INTERFACES}=="*:0701??:*", TAG+="systemd", ENV{SYSTEMD_WANTS}="configure-printer@usb-$env{BUSNUM}-$env{DEVNUM}.service"
I am not very good at deciphering udev rules, but this could make a plausible culprit

Last edited by Didier Spaier; 01-04-2014 at 03:39 PM.
 
Old 01-04-2014, 05:00 PM   #8
mancha
Member
 
Registered: Aug 2012
Posts: 279

Rep: Reputation: Disabled
@bobjusto:

Even though Pat added my patch to cups that addresses outstanding conflicts some printers have with usblp, he chose a conservative approach and also blacklisted "usblp" in Slackware 14.1.

You can disable the blacklisting by removing /lib/modprobe.d/cups-blacklist-usblp.conf.

--mancha

Last edited by mancha; 01-04-2014 at 05:11 PM.
 
Old 01-04-2014, 05:19 PM   #9
bobjusto
LQ Newbie
 
Registered: Jan 2014
Posts: 5

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Didier Spaier View Post
I think that your assumption "/lib/udev/rules.d/80-drivers.rules is the same, so we should see the same behavior" is wrong. Here is a diff of /lib/udev/rules.d/70-printers.rules beetween 14.0 (on the left) and 14.1 (on the right):
Code:
2,5c2
< ACTION=="add", SUBSYSTEM=="usb", ATTR{bInterfaceClass}=="07", ATTR{bInterfaceSubClass}=="01", TAG+="udev-configure-printer", RUN+="udev-configure-printer add %p"
< # usblp device add trigger (needed when usblp is already loaded)
< ACTION=="add", KERNEL=="lp*", TAG+="udev-configure-printer", RUN+="udev-configure-printer add %p"
< 
---
> ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ENV{ID_USB_INTERFACES}=="*:0701??:*", TAG+="systemd", ENV{SYSTEMD_WANTS}="configure-printer@usb-$env{BUSNUM}-$env{DEVNUM}.service"
I am not very good at deciphering udev rules, but this could make a plausible culprit
it was the first thing i had made : putting the 70-printerxxx of the 14.0 in /etc/udev/rules.d , didn't work by he hell!
 
Old 01-04-2014, 05:28 PM   #10
bobjusto
LQ Newbie
 
Registered: Jan 2014
Posts: 5

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by mancha View Post
@bobjusto:

Even though Pat added my patch to cups that addresses outstanding conflicts some printers have with usblp, he chose a conservative approach and also blacklisted "usblp" in Slackware 14.1.

You can disable the blacklisting by removing /lib/modprobe.d/cups-blacklist-usblp.conf.

--mancha
Thank you very much indeed , mancha, removing this file fixed this !

actually i didn't watch at the blacklisted modules in /lib/modprobe.d but in /etc/modprobe.d as in the old time!

now i will try to put an empty cups-blacklist-usblp.conf in /etc/modprobe.d to override the one in /lib/modprobe.d !
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Slackware 14.1 Canon MP-495 Multi-function Printer Setup Issues FirstHorseman Slackware 2 11-14-2013 04:29 PM
[SOLVED] USB Scanner configuration issues for HP all in one printer andy_o Linux - Hardware 6 09-08-2011 05:20 PM
Issues installing a Cannon Pixma MP640 Printer on Slackware 13.1 Luke_Wolf Linux - Hardware 7 02-06-2011 11:09 PM
USB Printer Issues - Red Hat Enterprise Linux 5.3 - HP Laser P2014 powmarday Linux - Hardware 0 04-06-2009 04:56 AM
help with HP printer issues? (USB) akshunj Slackware 2 10-08-2002 12:07 AM


All times are GMT -5. The time now is 02:41 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration