Re: lp card not found

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Post a dmesg.

In general you only very rarely need to modprobe anything, it happens
automatically.

also post a "lspci -nn"

On Fri, Oct 16, 2020 at 10:26 PM ToddAndMargo via users
<users@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> On 10/16/20 6:35 PM, ToddAndMargo via users wrote:
> > Hi All,
> >
> > Fedora32 x64
> >
> > I just installed a
> >
> > https://lavaports.com/serial-parallel-cards/products-pcie-bus-io-cards/parallel-pcie/
> >
> >
> >
> > CUPS tells me the priner is not attqched.
> >
> > I did a
> >
> > # modprobe -r lp
> > # modprobe -r parport_pc
> > # modprobe parport_pc io=0x378,0xee00 irq=7,11
> > # modprobe lp
> >
> > Cups shows the printer idle
> >
> > Now jobs disappears as if it if printing,
> > but the printer shows nothing.
> >
> > I am not sure that this card is being
> > seen as /dev/lp0.  How do I
> > check that.
> >
> > And how do I check which lp my printer is attached to?
> >
> >
> > Many thanks,
> > -T
>
>
> After a fresh boot:
>
> $ udevadm info -a /dev/lp0
> Unknown device "/dev/lp0": No such device
>
> Same with lp1 and lp2 and lp3
>
>
> After the above modprobes:
>
> # udevadm info -a /dev/lp0
>
> Udevadm info starts with the device specified by the devpath and then
> walks up the chain of parent devices. It prints for every device
> found, all possible attributes in the udev rules key format.
> A rule to match, can be composed by the attributes of the device
> and the attributes from one single parent device.
>
>    looking at device '/devices/platform/parport_pc.888/printer/lp0':
>      KERNEL=="lp0"
>      SUBSYSTEM=="printer"
>      DRIVER==""
>
>    looking at parent device '/devices/platform/parport_pc.888':
>      KERNELS=="parport_pc.888"
>      SUBSYSTEMS=="platform"
>      DRIVERS=="parport_pc"
>      ATTRS{driver_override}=="(null)"
>
>    looking at parent device '/devices/platform':
>      KERNELS=="platform"
>      SUBSYSTEMS==""
>      DRIVERS==""
>
> _______________________________________________
> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux