Re: CUPS printer problems - #!/bin/bash
On 29.11.2014 22:18, Duncan Patton a Campbell wrote:
On Sat, 29 Nov 2014 00:57:18 +0100
Antoine Jacoutot ajacou...@bsdfrog.org wrote:
Not that I can find, but what you're saying here is what I'm
seeing:
bash _was_ on the system for a short time a while back when it was
needed
to get grolog to run on OBSD64. Afterward it was removed. But
cups-foomatic is going out when it gets installed, and finding
some bashism,
preferentially configures for it. In newer versions of foom* this
becomes an explicitly configurable param.
If that were to be the case, it would have called
/usr/local/bin/bash, not /bin/bash...
I dunno. This thing sets up for /bin/bash iff it finds some kind of
bashism.
/usr/local/bin/bash was left over in shells, but that's not where
it got this from. In the openprinting code it makes reference to
bash as
a preferred shell or something, so I think something in the old
foom*
is finding .bash.history or some other cruft and automagically
selecting
Sorry for interrupting..isn't it this?
$ pwd
/usr/ports/print/cups-filters
$ egrep -ri bash *
Makefile: perl -pi -e 's,/bin/bash,/bin/ksh,g'
${WRKSRC}/filter/textonly
patches/patch-filter_foomatic-rip_foomaticrip_c:-char modern_shell[64]
= /bin/bash;
$
for it.
Dhu
--
Antoine
Re: CUPS printer problems - #!/bin/bash
Sorry for interrupting..isn't it this? We are explicitely patching so that it is *not* it... -- Antoine
Re: CUPS printer problems - #!/bin/bash
On Sat, 29 Nov 2014 00:57:18 +0100 Antoine Jacoutot ajacou...@bsdfrog.org wrote: Not that I can find, but what you're saying here is what I'm seeing: bash _was_ on the system for a short time a while back when it was needed to get grolog to run on OBSD64. Afterward it was removed. But cups-foomatic is going out when it gets installed, and finding some bashism, preferentially configures for it. In newer versions of foom* this becomes an explicitly configurable param. If that were to be the case, it would have called /usr/local/bin/bash, not /bin/bash... I dunno. This thing sets up for /bin/bash iff it finds some kind of bashism. /usr/local/bin/bash was left over in shells, but that's not where it got this from. In the openprinting code it makes reference to bash as a preferred shell or something, so I think something in the old foom* is finding .bash.history or some other cruft and automagically selecting for it. Dhu -- Antoine -- Ne obliviscaris, vix ea nostra voco.
Re: CUPS printer problems - #!/bin/bash
On Fri, 28 Nov 2014 17:38:46 +0100 Antoine Jacoutot ajacou...@bsdfrog.org wrote: On Fri, Nov 28, 2014 at 09:23:41AM -0700, Duncan Patton a Campbell wrote: On Fri, 28 Nov 2014 11:15:26 +0100 Antoine Jacoutot ajacou...@bsdfrog.org wrote: On Thu, Nov 27, 2014 at 03:54:10PM -0700, Duncan Patton a Campbell wrote: On Thu, 27 Nov 2014 15:01:44 -0700 Duncan Patton a Campbell campb...@neotext.ca wrote: The kludge that killz (bugz;): # cd /bin # ln -s sh bash And now my printer works! Yes but the Print Self-Test Page does not. Cups claims it does but foomatic says something else (attached). The Shell sez bash but it's pointing to /bin/sh. The problem could some shell diff between ksh and bash, or something entirely else I don't see how bash ended up in the process... Foomatic was patched to use ksh. You sure you don't have an old foomatic configuration around? I just spotted a misused of bash in cups-filters actually, but it's for the textonly filter, so that does not concern that particular issue. bash has _been_ on the system before, so it must be going out and finding some dead config. I've been doing installs not upgrades on the system and then hooking up the user disks after the fact. Looking in the most recent foomatic code I find statements like 2003-12-21 Till Kamppeter till.kamppe...@gmx.net * Makefile.in: Fixed compatibility for non-bash systems: Used VAR=VALUE; export VAR instead of export VAR=VALUE (Thanks to Florian Diesch die...@spamfence.net). 2006-10-03 Till Kamppeter till.kamppe...@gmail.com * foomatic-rip.in: Fixed bashism. but also Unfortunately, this technique does not work for `CONFIG_SHELL' due to an Autoconf bug. Until the bug is fixed you can use this workaround: CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash Yeah but that has nothing to do with why your foomatic is trying to invoke /bin/bash. You are mixing apples and oranges here. I only used that to point out that there's bashisms thruout the codebase... but I'd guess that somewhere Fruitco is conflating apples and oranges into the round_fruit set (as distinct from long_fruit like bananas and pine cones). If I build foomatic from net sources I get # ./foomatic-rip -v foomatic rip version 4.0.12.246 man foomatic-rip for help. # # pkg_info| grep foom foomatic-db-4.0.20131218 Foomatic PPD data foomatic-db-engine-4.0.11 Foomatic PPD generator but that's NOT what the package installs: # foomatic-rip -v foomatic-rip of cups-filters version 1.0.54 man foomatic-rip for help. This is the version in the /tmp/foomatic*.log files. I just removed the /bin/bash - sh link and got the same log file: foomatic-rip version 1.0.54 running... ... Error: Executing /bin/bash So cups is installing old filtre code imported from foo-1.0.54 but the foo-packages think they're at 4.0.? Something is funky here, and it goes further than my machine. Dhu -- Antoine -- Ne obliviscaris, vix ea nostra voco.
Re: CUPS printer problems - #!/bin/bash
I only used that to point out that there's bashisms thruout the codebase... but I'd guess that somewhere Fruitco is conflating apples and oranges into the round_fruit set (as distinct from long_fruit like bananas and pine cones). If I build foomatic from net sources I get What net sources? I am not interested about external non official sources. I am only interested in fixing out packages. The only official net source of foomatic-rip is cups-filters. The one from openprinting is not maintained anymore. $ pkglocate foomatic-rip cups-filters-1.0.61p1:print/cups-filters:/usr/local/bin/foomatic-rip cups-filters-1.0.61p1:print/cups-filters:/usr/local/libexec/cups/filter/foomatic-rip cups-filters-1.0.61p1:print/cups-filters:/usr/local/man/man1/foomatic-rip.1 Sorry but I will not help with locally compiled external softwares, only with official ports/packages. -- Antoine
Re: CUPS printer problems - #!/bin/bash
On Fri, 28 Nov 2014 19:34:35 +0100 Antoine Jacoutot ajacou...@bsdfrog.org wrote: I only used that to point out that there's bashisms thruout the codebase... but I'd guess that somewhere Fruitco is conflating apples and oranges into the round_fruit set (as distinct from long_fruit like bananas and pine cones). If I build foomatic from net sources I get What net sources? I am not interested about external non official sources. I am only interested in fixing out packages. The only official net source of foomatic-rip is cups-filters. The one from openprinting is not maintained anymore. I'm not running that code. As I pointed out the official openbsd foomatic packages are NAME/NUMBERED like like the openprinting version 4.012, but inside they are something else branched from a much older version: version 1.1 is from circa 2002. This is version 1.0.54 # which foomatic-rip /usr/local/bin/foomatic-rip l /usr/local/bin/foomatic-rip lrwxr-xr-x 1 root wheel 43 Nov 26 11:44 /usr/local/bin/foomatic-rip - /usr/local/libexec/cups/filter/foomatic-rip # l /usr/local/libexec/cups/filter/foomatic-rip -r-xr-xr-x 1 root bin 108536 Jul 31 07:06 /usr/local/libexec/cups/filter/foomatic-rip /usr/local/bin/foomatic-rip -v foomatic-rip of cups-filters version 1.0.54 man foomatic-rip for help. The code from openprinting returns foomatic rip version 4.0.12.246 $ pkglocate foomatic-rip that's netbsd. are these packages xcompiled? cups-filters-1.0.61p1:print/cups-filters:/usr/local/bin/foomatic-rip cups-filters-1.0.61p1:print/cups-filters:/usr/local/libexec/cups/filter/foomatic-rip cups-filters-1.0.61p1:print/cups-filters:/usr/local/man/man1/foomatic-rip.1 Sorry but I will not help with locally compiled external softwares, only with official ports/packages. It's the Official port/package that is CALLING BASH. # pkg_info | grep cups cups-1.7.4p2Common Unix Printing System cups-filters-1.0.54p2 OpenPrinting CUPS filters cups-libs-1.7.4 CUPS libraries and headers # pkg_info | grep foom foomatic-db-4.0.20131218 Foomatic PPD data foomatic-db-engine-4.0.11 Foomatic PPD generator Dhu -- Antoine -- Ne obliviscaris, vix ea nostra voco.
Re: CUPS printer problems - #!/bin/bash
I'm not running that code. As I pointed out the official openbsd foomatic packages are NAME/NUMBERED like like the openprinting version 4.012, but inside they are something else branched from a much older version: version 1.1 is from circa 2002. This is version 1.0.54 # which foomatic-rip /usr/local/bin/foomatic-rip l /usr/local/bin/foomatic-rip lrwxr-xr-x 1 root wheel 43 Nov 26 11:44 /usr/local/bin/foomatic-rip - /usr/local/libexec/cups/filter/foomatic-rip # l /usr/local/libexec/cups/filter/foomatic-rip -r-xr-xr-x 1 root bin 108536 Jul 31 07:06 /usr/local/libexec/cups/filter/foomatic-rip /usr/local/bin/foomatic-rip -v foomatic-rip of cups-filters version 1.0.54 man foomatic-rip for help. The code from openprinting returns foomatic rip version 4.0.12.246 How is that relevant to the bash issue; you confuse me... did I miss something? $ pkglocate foomatic-rip that's netbsd. are these packages xcompiled? What do you mean that's netbsd? And what do you mean by xcompiled? cups-filters-1.0.61p1:print/cups-filters:/usr/local/bin/foomatic-rip cups-filters-1.0.61p1:print/cups-filters:/usr/local/libexec/cups/filter/foomatic-rip cups-filters-1.0.61p1:print/cups-filters:/usr/local/man/man1/foomatic-rip.1 Sorry but I will not help with locally compiled external softwares, only with official ports/packages. It's the Official port/package that is CALLING BASH. Nowhere in the installed cups-filters code I can see it calling bash... Just grep for it yourself and you'll see. So there must be something specific on your system. Did you make sure you don't have an old config laying around? -- Antoine
Re: CUPS printer problems - #!/bin/bash
On Sat, 29 Nov 2014 00:34:17 +0100 Antoine Jacoutot ajacou...@bsdfrog.org wrote: I'm not running that code. As I pointed out the official openbsd foomatic packages are NAME/NUMBERED like like the openprinting version 4.012, but inside they are something else branched from a much older version: version 1.1 is from circa 2002. This is version 1.0.54 # which foomatic-rip /usr/local/bin/foomatic-rip l /usr/local/bin/foomatic-rip lrwxr-xr-x 1 root wheel 43 Nov 26 11:44 /usr/local/bin/foomatic-rip - /usr/local/libexec/cups/filter/foomatic-rip # l /usr/local/libexec/cups/filter/foomatic-rip -r-xr-xr-x 1 root bin 108536 Jul 31 07:06 /usr/local/libexec/cups/filter/foomatic-rip /usr/local/bin/foomatic-rip -v foomatic-rip of cups-filters version 1.0.54 man foomatic-rip for help. The code from openprinting returns foomatic rip version 4.0.12.246 How is that relevant to the bash issue; you confuse me... did I miss something? $ pkglocate foomatic-rip that's netbsd. are these packages xcompiled? What do you mean that's netbsd? And what do you mean by xcompiled? pkglocate is a netbsd utility. I didn't know it had been ported. xcompiled == cross-compiled. cups-filters-1.0.61p1:print/cups-filters:/usr/local/bin/foomatic-rip cups-filters-1.0.61p1:print/cups-filters:/usr/local/libexec/cups/filter/foomatic-rip cups-filters-1.0.61p1:print/cups-filters:/usr/local/man/man1/foomatic-rip.1 Sorry but I will not help with locally compiled external softwares, only with official ports/packages. It's the Official port/package that is CALLING BASH. Nowhere in the installed cups-filters code I can see it calling bash... Just grep for it yourself and you'll see. So there must be something specific on your system. Did you make sure you don't have an old config laying around? Not that I can find, but what you're saying here is what I'm seeing: bash _was_ on the system for a short time a while back when it was needed to get grolog to run on OBSD64. Afterward it was removed. But cups-foomatic is going out when it gets installed, and finding some bashism, preferentially configures for it. In newer versions of foom* this becomes an explicitly configurable param. Dhu -- Antoine -- Ne obliviscaris, vix ea nostra voco.
Re: CUPS printer problems - #!/bin/bash
Not that I can find, but what you're saying here is what I'm seeing: bash _was_ on the system for a short time a while back when it was needed to get grolog to run on OBSD64. Afterward it was removed. But cups-foomatic is going out when it gets installed, and finding some bashism, preferentially configures for it. In newer versions of foom* this becomes an explicitly configurable param. If that were to be the case, it would have called /usr/local/bin/bash, not /bin/bash... -- Antoine
Re: CUPS printer problems Yes!
On Thu, 27 Nov 2014 14:53:05 -0700 Duncan Patton a Campbell campb...@neotext.ca wrote: On Thu, 27 Nov 2014 14:27:56 -0700 Duncan Patton a Campbell campb...@neotext.ca wrote: cd /var/log tar cf log.cups.1.tar mv log.cups.1.tar /tmp/ cd /tmp # l Oi. Cut'n'pasted from the wrong window... the attached log.cups.2.tar.gz contains the complete record.. it was made after I noticed the foomatic(!bash) log. Dhu -- Ne obliviscaris, vix ea nostra voco. The kludge that killz (bugz;): # cd /bin # ln -s sh bash And now my printer works! Dhu Thanks to all. I wouldn't have got to this point without Antoine killing some real bugs along the way. -- Ne obliviscaris, vix ea nostra voco.
Re: CUPS printer problems
Hi Bernte. Can you tell me what kind of printer you are using? I am still having problems with this and it may be a usb1 compatability issue. Thanks, Dhu On Tue, 25 Nov 2014 07:49:18 + Bernte ber...@fams.de wrote: On 25/11/14 04:30, Antoine Jacoutot wrote: On Mon, Nov 24, 2014 at 10:04:59PM +, Bernte wrote: Hi - Since upgrading to 5.6, I am having problems to detect my Brother USB printer in CUPS. The problem is that the printer is not found by the 'usb' backend: Your cups package is not up to date. You need the one from 5.6 stable. Thanks Antoine, upgrading to cups-1.7.4p1 made CUPS detect my printer. Issue fixed. Bernd -- Ne obliviscaris, vix ea nostra voco.
CUPS printer problems
Hi - Since upgrading to 5.6, I am having problems to detect my Brother USB printer in CUPS. The problem is that the printer is not found by the 'usb' backend: # /usr/local/libexec/cups/backend/usb DEBUG: Loading USB quirks from /usr/local/share/cups/usb. DEBUG: Loaded 68 quirks. DEBUG: list_devices DEBUG: libusb_get_device_list=8 DEBUG: Failed to check whether 04f9:001a has the usblp kernel module attached The error looks suspicious, though I did not find anything useful about it googling the web (it seems to be an error caused by libusb). The printer does show up in usbdevs -vd: # usbdevs -vd Controller /dev/usb0: addr 1: high speed, self powered, config 1, EHCI root hub(0x), RDC(0x17f3), rev 1.00 uhub0 port 1 powered port 2 powered Controller /dev/usb1: addr 1: high speed, self powered, config 1, EHCI root hub(0x), RDC(0x17f3), rev 1.00 uhub1 port 1 powered port 2 powered Controller /dev/usb2: addr 1: full speed, self powered, config 1, OHCI root hub(0x), RDC(0x17f3), rev 1.00 uhub2 port 1 powered port 2 addr 2: full speed, self powered, config 1, product 0x001a(0x001a), Brother Industries(0x04f9), rev 1.00 ugen0 Controller /dev/usb3: addr 1: full speed, self powered, config 1, OHCI root hub(0x), RDC(0x17f3), rev 1.00 uhub3 port 1 powered port 2 addr 2: full speed, power 100 mA, config 1, Logitech BT Mini-Receiver(0x0b04), Logitech(0x046d), rev 49.00 uhub4 port 1 powered port 2 addr 3: full speed, power 98 mA, config 1, Logitech BT Mini-Receiver(0xc713), Logitech(0x046d), rev 49.00, iSerialNumber 001F203C2558 uhidev0 port 3 addr 4: full speed, power 98 mA, config 1, Logitech BT Mini-Receiver(0xc714), Logitech(0x046d), rev 49.00, iSerialNumber 001F203C2558 uhidev1 As explained in the pkg-readme, I have disabled the ulpt driver in the kernel, as well as changed the ownership of the devices: # ls -la /dev/usb2 /dev/ugen0.* crw-rw 1 _cups wheel 63, 0 Nov 21 19:35 /dev/ugen0.00 crw-rw 1 _cups wheel 63, 1 Nov 21 19:35 /dev/ugen0.01 crw-rw 1 _cups wheel 63, 2 Nov 21 19:35 /dev/ugen0.02 crw-rw 1 _cups wheel 63, 3 Nov 21 19:35 /dev/ugen0.03 crw-rw 1 _cups wheel 63, 4 Nov 21 19:35 /dev/ugen0.04 crw-rw 1 _cups wheel 63, 5 Nov 21 19:35 /dev/ugen0.05 crw-rw 1 _cups wheel 63, 6 Nov 21 19:35 /dev/ugen0.06 crw-rw 1 _cups wheel 63, 7 Nov 21 19:35 /dev/ugen0.07 crw-rw 1 _cups wheel 63, 8 Nov 21 19:35 /dev/ugen0.08 crw-rw 1 _cups wheel 63, 9 Nov 21 19:35 /dev/ugen0.09 crw-rw 1 _cups wheel 63, 10 Nov 21 19:35 /dev/ugen0.10 crw-rw 1 _cups wheel 63, 11 Nov 21 19:35 /dev/ugen0.11 crw-rw 1 _cups wheel 63, 12 Nov 21 19:35 /dev/ugen0.12 crw-rw 1 _cups wheel 63, 13 Nov 21 19:35 /dev/ugen0.13 crw-rw 1 _cups wheel 63, 14 Nov 21 19:35 /dev/ugen0.14 crw-rw 1 _cups wheel 63, 15 Nov 21 19:35 /dev/ugen0.15 crw-rw 1 _cups wheel 61, 2 Nov 21 19:35 /dev/usb2 Any hints on how to track down my problem would be welcome. Regards, Bernd dmesg: OpenBSD 5.6 (GENERIC) #2: Tue Oct 28 16:56:54 CET 2014 r...@stable-56-i386.mtier.org:/binpatchng/work-binpatch56-i386/src/sys/arch/i386/compile/GENERIC cpu0: Vortex86 SoC (586-class) 934 MHz cpu0: FPU,TSC,CX8,MMX real mem = 1039691776 (991MB) avail mem = 1010257920 (963MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 11/26/10, BIOS32 rev. 0 @ 0xf0010 apm0 at bios0: Power Management spec V1.2 pcibios0 at bios0: rev 3.0 @ 0xf/0x1 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf2fe0/240 (13 entries) pcibios0: no compatible PCI ICU found: ICU vendor 0x17f3 product 0x6036 pcibios0: Warning, unable to fix up PCI interrupt routing pcibios0: PCI bus #0 is the last bus bios0: ROM list: 0xc/0x8000 cpu0 at mainbus0: (uniprocessor) pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 vendor RDC, unknown product 0x6022 rev 0x00 rl0 at pci0 dev 1 function 0 Realtek 8139 rev 0x10: irq 11, address 44:4d:50:07:1b:19 rlphy0 at rl0 phy 0: RTL internal PHY rl1 at pci0 dev 2 function 0 Realtek 8139 rev 0x10: irq 11, address 44:4d:50:07:1b:1a rlphy1 at rl1 phy 0: RTL internal PHY pcib0 at pci0 dev 7 function 0 vendor RDC, unknown product 0x6036 rev 0x00 vte0 at pci0 dev 8 function 0 RDC R6040 Ethernet rev 0x00: irq 6, address 00:1b:eb:25:30:9e rdcphy0 at vte0 phy 1: R6040 10/100 PHY, rev. 1 ohci0 at pci0 dev 10 function 0 RDC R6060 USB rev 0x12: irq 7, version 1.0, legacy support ehci0 at pci0 dev 10 function 1 RDC R6061 USB2 rev 0x03: irq 3 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 RDC EHCI root hub rev 2.00/1.00 addr 1 ohci1 at pci0 dev 11 function 0 RDC R6060 USB rev 0x12: irq 5, version 1.0, legacy support ehci1 at pci0 dev 11 function 1 RDC R6061 USB2 rev 0x03: irq 9 usb1 at ehci1: USB revision 2.0 uhub1 at usb1 RDC EHCI root hub rev 2.00/1.00 addr 1 pciide0
Re: CUPS printer problems
On Mon, Nov 24, 2014 at 10:04:59PM +, Bernte wrote: Hi - Since upgrading to 5.6, I am having problems to detect my Brother USB printer in CUPS. The problem is that the printer is not found by the 'usb' backend: Your cups package is not up to date. You need the one from 5.6 stable. # /usr/local/libexec/cups/backend/usb DEBUG: Loading USB quirks from /usr/local/share/cups/usb. DEBUG: Loaded 68 quirks. DEBUG: list_devices DEBUG: libusb_get_device_list=8 DEBUG: Failed to check whether 04f9:001a has the usblp kernel module attached The error looks suspicious, though I did not find anything useful about it googling the web (it seems to be an error caused by libusb). The printer does show up in usbdevs -vd: # usbdevs -vd Controller /dev/usb0: addr 1: high speed, self powered, config 1, EHCI root hub(0x), RDC(0x17f3), rev 1.00 uhub0 port 1 powered port 2 powered Controller /dev/usb1: addr 1: high speed, self powered, config 1, EHCI root hub(0x), RDC(0x17f3), rev 1.00 uhub1 port 1 powered port 2 powered Controller /dev/usb2: addr 1: full speed, self powered, config 1, OHCI root hub(0x), RDC(0x17f3), rev 1.00 uhub2 port 1 powered port 2 addr 2: full speed, self powered, config 1, product 0x001a(0x001a), Brother Industries(0x04f9), rev 1.00 ugen0 Controller /dev/usb3: addr 1: full speed, self powered, config 1, OHCI root hub(0x), RDC(0x17f3), rev 1.00 uhub3 port 1 powered port 2 addr 2: full speed, power 100 mA, config 1, Logitech BT Mini-Receiver(0x0b04), Logitech(0x046d), rev 49.00 uhub4 port 1 powered port 2 addr 3: full speed, power 98 mA, config 1, Logitech BT Mini-Receiver(0xc713), Logitech(0x046d), rev 49.00, iSerialNumber 001F203C2558 uhidev0 port 3 addr 4: full speed, power 98 mA, config 1, Logitech BT Mini-Receiver(0xc714), Logitech(0x046d), rev 49.00, iSerialNumber 001F203C2558 uhidev1 As explained in the pkg-readme, I have disabled the ulpt driver in the kernel, as well as changed the ownership of the devices: # ls -la /dev/usb2 /dev/ugen0.* crw-rw 1 _cups wheel 63, 0 Nov 21 19:35 /dev/ugen0.00 crw-rw 1 _cups wheel 63, 1 Nov 21 19:35 /dev/ugen0.01 crw-rw 1 _cups wheel 63, 2 Nov 21 19:35 /dev/ugen0.02 crw-rw 1 _cups wheel 63, 3 Nov 21 19:35 /dev/ugen0.03 crw-rw 1 _cups wheel 63, 4 Nov 21 19:35 /dev/ugen0.04 crw-rw 1 _cups wheel 63, 5 Nov 21 19:35 /dev/ugen0.05 crw-rw 1 _cups wheel 63, 6 Nov 21 19:35 /dev/ugen0.06 crw-rw 1 _cups wheel 63, 7 Nov 21 19:35 /dev/ugen0.07 crw-rw 1 _cups wheel 63, 8 Nov 21 19:35 /dev/ugen0.08 crw-rw 1 _cups wheel 63, 9 Nov 21 19:35 /dev/ugen0.09 crw-rw 1 _cups wheel 63, 10 Nov 21 19:35 /dev/ugen0.10 crw-rw 1 _cups wheel 63, 11 Nov 21 19:35 /dev/ugen0.11 crw-rw 1 _cups wheel 63, 12 Nov 21 19:35 /dev/ugen0.12 crw-rw 1 _cups wheel 63, 13 Nov 21 19:35 /dev/ugen0.13 crw-rw 1 _cups wheel 63, 14 Nov 21 19:35 /dev/ugen0.14 crw-rw 1 _cups wheel 63, 15 Nov 21 19:35 /dev/ugen0.15 crw-rw 1 _cups wheel 61, 2 Nov 21 19:35 /dev/usb2 Any hints on how to track down my problem would be welcome. Regards, Bernd dmesg: OpenBSD 5.6 (GENERIC) #2: Tue Oct 28 16:56:54 CET 2014 r...@stable-56-i386.mtier.org:/binpatchng/work-binpatch56-i386/src/sys/arch/i386/compile/GENERIC cpu0: Vortex86 SoC (586-class) 934 MHz cpu0: FPU,TSC,CX8,MMX real mem = 1039691776 (991MB) avail mem = 1010257920 (963MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 11/26/10, BIOS32 rev. 0 @ 0xf0010 apm0 at bios0: Power Management spec V1.2 pcibios0 at bios0: rev 3.0 @ 0xf/0x1 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf2fe0/240 (13 entries) pcibios0: no compatible PCI ICU found: ICU vendor 0x17f3 product 0x6036 pcibios0: Warning, unable to fix up PCI interrupt routing pcibios0: PCI bus #0 is the last bus bios0: ROM list: 0xc/0x8000 cpu0 at mainbus0: (uniprocessor) pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 vendor RDC, unknown product 0x6022 rev 0x00 rl0 at pci0 dev 1 function 0 Realtek 8139 rev 0x10: irq 11, address 44:4d:50:07:1b:19 rlphy0 at rl0 phy 0: RTL internal PHY rl1 at pci0 dev 2 function 0 Realtek 8139 rev 0x10: irq 11, address 44:4d:50:07:1b:1a rlphy1 at rl1 phy 0: RTL internal PHY pcib0 at pci0 dev 7 function 0 vendor RDC, unknown product 0x6036 rev 0x00 vte0 at pci0 dev 8 function 0 RDC R6040 Ethernet rev 0x00: irq 6, address 00:1b:eb:25:30:9e rdcphy0 at vte0 phy 1: R6040 10/100 PHY, rev. 1 ohci0 at pci0 dev 10 function 0 RDC R6060 USB rev 0x12: irq 7, version 1.0, legacy support ehci0 at pci0 dev 10 function 1 RDC R6061 USB2 rev 0x03: irq 3 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 RDC EHCI root hub rev 2.00/1.00 addr 1 ohci1 at pci0 dev 11 function 0
Re: CUPS printer problems
Howdy Bernte? I'm having the same problems, with both i386 and amd64. I'm now thinking that I will build an earlier version of cups (say from b4 Fruitco), althouth my suspicions are on the cups/usb interface so I'm thinking of building an earlier port. Dhu On Mon, 24 Nov 2014 22:04:59 + Bernte ber...@fams.de wrote: Any hints on how to track down my problem would be welcome. Regards, Bernd -- Ne obliviscaris, vix ea nostra voco.
Re: CUPS printer problems
On Tue, 25 Nov 2014 05:30:53 +0100 Antoine Jacoutot ajacou...@bsdfrog.org wrote: On Mon, Nov 24, 2014 at 10:04:59PM +, Bernte wrote: Hi - Since upgrading to 5.6, I am having problems to detect my Brother USB printer in CUPS. The problem is that the printer is not found by the 'usb' backend: Your cups package is not up to date. You need the one from 5.6 stable. Bj Antoine. cups-1.7.4p0.tgz is in release, and cups-2.0.1.tgz is in snapshot. Is there something in between, that would be in the errata if there was one for snapshot like there's a http://www.openbsd.org/plus.html between 5.6 and 5.6+ ? I've tried 1.7.4p0 on both i386 and amd64 with results strikingly like those describe by Bernte. Hmmm. Do I build 2.0 from ports or up to the snap and take my chances on other things Or attempt to backup to 1.4 or 1.5? Thanks, Dhu # /usr/local/libexec/cups/backend/usb DEBUG: Loading USB quirks from /usr/local/share/cups/usb. DEBUG: Loaded 68 quirks. DEBUG: list_devices DEBUG: libusb_get_device_list=8 DEBUG: Failed to check whether 04f9:001a has the usblp kernel module attached The error looks suspicious, though I did not find anything useful about it googling the web (it seems to be an error caused by libusb). The printer does show up in usbdevs -vd: # usbdevs -vd Controller /dev/usb0: addr 1: high speed, self powered, config 1, EHCI root hub(0x), RDC(0x17f3), rev 1.00 uhub0 port 1 powered port 2 powered Controller /dev/usb1: addr 1: high speed, self powered, config 1, EHCI root hub(0x), RDC(0x17f3), rev 1.00 uhub1 port 1 powered port 2 powered Controller /dev/usb2: addr 1: full speed, self powered, config 1, OHCI root hub(0x), RDC(0x17f3), rev 1.00 uhub2 port 1 powered port 2 addr 2: full speed, self powered, config 1, product 0x001a(0x001a), Brother Industries(0x04f9), rev 1.00 ugen0 Controller /dev/usb3: addr 1: full speed, self powered, config 1, OHCI root hub(0x), RDC(0x17f3), rev 1.00 uhub3 port 1 powered port 2 addr 2: full speed, power 100 mA, config 1, Logitech BT Mini-Receiver(0x0b04), Logitech(0x046d), rev 49.00 uhub4 port 1 powered port 2 addr 3: full speed, power 98 mA, config 1, Logitech BT Mini-Receiver(0xc713), Logitech(0x046d), rev 49.00, iSerialNumber 001F203C2558 uhidev0 port 3 addr 4: full speed, power 98 mA, config 1, Logitech BT Mini-Receiver(0xc714), Logitech(0x046d), rev 49.00, iSerialNumber 001F203C2558 uhidev1 As explained in the pkg-readme, I have disabled the ulpt driver in the kernel, as well as changed the ownership of the devices: # ls -la /dev/usb2 /dev/ugen0.* crw-rw 1 _cups wheel 63, 0 Nov 21 19:35 /dev/ugen0.00 crw-rw 1 _cups wheel 63, 1 Nov 21 19:35 /dev/ugen0.01 crw-rw 1 _cups wheel 63, 2 Nov 21 19:35 /dev/ugen0.02 crw-rw 1 _cups wheel 63, 3 Nov 21 19:35 /dev/ugen0.03 crw-rw 1 _cups wheel 63, 4 Nov 21 19:35 /dev/ugen0.04 crw-rw 1 _cups wheel 63, 5 Nov 21 19:35 /dev/ugen0.05 crw-rw 1 _cups wheel 63, 6 Nov 21 19:35 /dev/ugen0.06 crw-rw 1 _cups wheel 63, 7 Nov 21 19:35 /dev/ugen0.07 crw-rw 1 _cups wheel 63, 8 Nov 21 19:35 /dev/ugen0.08 crw-rw 1 _cups wheel 63, 9 Nov 21 19:35 /dev/ugen0.09 crw-rw 1 _cups wheel 63, 10 Nov 21 19:35 /dev/ugen0.10 crw-rw 1 _cups wheel 63, 11 Nov 21 19:35 /dev/ugen0.11 crw-rw 1 _cups wheel 63, 12 Nov 21 19:35 /dev/ugen0.12 crw-rw 1 _cups wheel 63, 13 Nov 21 19:35 /dev/ugen0.13 crw-rw 1 _cups wheel 63, 14 Nov 21 19:35 /dev/ugen0.14 crw-rw 1 _cups wheel 63, 15 Nov 21 19:35 /dev/ugen0.15 crw-rw 1 _cups wheel 61, 2 Nov 21 19:35 /dev/usb2 Any hints on how to track down my problem would be welcome. Regards, Bernd dmesg: OpenBSD 5.6 (GENERIC) #2: Tue Oct 28 16:56:54 CET 2014 r...@stable-56-i386.mtier.org:/binpatchng/work-binpatch56-i386/src/sys/arch/i386/compile/GENERIC cpu0: Vortex86 SoC (586-class) 934 MHz cpu0: FPU,TSC,CX8,MMX real mem = 1039691776 (991MB) avail mem = 1010257920 (963MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 11/26/10, BIOS32 rev. 0 @ 0xf0010 apm0 at bios0: Power Management spec V1.2 pcibios0 at bios0: rev 3.0 @ 0xf/0x1 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf2fe0/240 (13 entries) pcibios0: no compatible PCI ICU found: ICU vendor 0x17f3 product 0x6036 pcibios0: Warning, unable to fix up PCI interrupt routing pcibios0: PCI bus #0 is the last bus bios0: ROM list: 0xc/0x8000 cpu0 at mainbus0: (uniprocessor) pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 vendor RDC, unknown product 0x6022 rev 0x00 rl0 at pci0 dev 1 function 0 Realtek 8139 rev 0x10: irq 11,
Re: CUPS printer problems
On Mon, Nov 24, 2014 at 10:59:10PM -0700, Duncan Patton a Campbell wrote: On Tue, 25 Nov 2014 05:30:53 +0100 Antoine Jacoutot ajacou...@bsdfrog.org wrote: On Mon, Nov 24, 2014 at 10:04:59PM +, Bernte wrote: Hi - Since upgrading to 5.6, I am having problems to detect my Brother USB printer in CUPS. The problem is that the printer is not found by the 'usb' backend: Your cups package is not up to date. You need the one from 5.6 stable. Bj Antoine. cups-1.7.4p0.tgz is in release, and cups-2.0.1.tgz is in snapshot. Is there something in between, that would be in the errata if there was one for snapshot like there's a http://www.openbsd.org/plus.html between 5.6 and 5.6+ ? Use ports. Just checkout the OPENBSD_5_6 branch. http://www.openbsd.org/faq/faq15.html#PortsSecurity I've tried 1.7.4p0 on both i386 and amd64 with results strikingly like those describe by Bernte. Hmmm. Do I build 2.0 from ports or up to the snap and take my chances on other things Or attempt to backup to 1.4 or 1.5? 1.7.4p0 is not the latest port for OpenBSD 5.6, it is 1.7.4p1. Revision 1.182.2.1 / (download) - annotate - [select for diffs], Thu Sep 11 09:55:33 2014 UTC (2 months, 2 weeks ago) by ajacoutot Branch: OPENBSD_5_6 Changes since 1.182: +2 -2 lines Diff to previous 1.182 (colored) next main 1.183 (colored) Fix USB printing. -- Antoine
Re: CUPS printer problems
On Tue, 25 Nov 2014 07:10:07 +0100 Antoine Jacoutot ajacou...@bsdfrog.org wrote: On Mon, Nov 24, 2014 at 10:59:10PM -0700, Duncan Patton a Campbell wrote: On Tue, 25 Nov 2014 05:30:53 +0100 Antoine Jacoutot ajacou...@bsdfrog.org wrote: On Mon, Nov 24, 2014 at 10:04:59PM +, Bernte wrote: Hi - Since upgrading to 5.6, I am having problems to detect my Brother USB printer in CUPS. The problem is that the printer is not found by the 'usb' backend: Your cups package is not up to date. You need the one from 5.6 stable. Bj Antoine. cups-1.7.4p0.tgz is in release, and cups-2.0.1.tgz is in snapshot. Is there something in between, that would be in the errata if there was one for snapshot like there's a http://www.openbsd.org/plus.html between 5.6 and 5.6+ ? Use ports. Just checkout the OPENBSD_5_6 branch. http://www.openbsd.org/faq/faq15.html#PortsSecurity Well it appears to be building ;-) I don't exaclty run a polyblade machine here. I've tried 1.7.4p0 on both i386 and amd64 with results strikingly like those describe by Bernte. Hmmm. Do I build 2.0 from ports or up to the snap and take my chances on other things Or attempt to backup to 1.4 or 1.5? 1.7.4p0 is not the latest port for OpenBSD 5.6, it is 1.7.4p1. Revision 1.182.2.1 / (download) - annotate - [select for diffs], Thu Sep 11 09:55:33 2014 UTC (2 months, 2 weeks ago) by ajacoutot ?450 ports/packages altho' you might be. merci. Branch: OPENBSD_5_6 Changes since 1.182: +2 -2 lines Diff to previous 1.182 (colored) next main 1.183 (colored) Fix USB printing. -- Antoine -- Ne obliviscaris, vix ea nostra voco.
Re: CUPS printer problems
On 25/11/14 04:30, Antoine Jacoutot wrote: On Mon, Nov 24, 2014 at 10:04:59PM +, Bernte wrote: Hi - Since upgrading to 5.6, I am having problems to detect my Brother USB printer in CUPS. The problem is that the printer is not found by the 'usb' backend: Your cups package is not up to date. You need the one from 5.6 stable. Thanks Antoine, upgrading to cups-1.7.4p1 made CUPS detect my printer. Issue fixed. Bernd
