LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices


Reply
  Search this Thread
Old 10-01-2015, 06:34 PM   #16
loshakova
Member
 
Registered: Apr 2012
Posts: 111

Original Poster
Rep: Reputation: Disabled

@ferrari:
Sorry about that -- you're right, I did mean computer. Long day. Weird about the port, though. I actually got out the schematic that came with my computer. Both the computer and the schematic have all the ports numbered for ease of identification. Printer scanner has a gray USB cord, and the gray USB cord is plugged into port #6, which is listed as being USB 2.0...oh, wait. Port 5 says "USB 3.0 connectors (USB connectors 5 and 6)". So Port 6 and Line Item 6 aren't synonymous. Line Item 6 goes with Ports 7 and 8. Derp. I'll climb under the desk again with the flashlight and get back to you.
 
Old 10-01-2015, 06:35 PM   #17
ferrari
LQ Guru
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 5,779

Rep: Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139
For test purposes, I would look at disabling it in the BIOS.
 
Old 10-01-2015, 06:48 PM   #18
loshakova
Member
 
Registered: Apr 2012
Posts: 111

Original Poster
Rep: Reputation: Disabled
No, strike that. I did read the schematic correctly, I just misremembered which port it was plugged into. It was plugged into Port 7, which is supposed to be USB 2.0. Just to remove all ambiguity, I unplugged it from that port and plugged it into Port 4, which is in another row and is also identified as USB 2.0 on the schematic. Then I ran $ sudo tail -f /var/log/syslog again. It's still coming up as USB 3.0.

Is there any sort of command I could have executed that could have confused the computer about what kind of port a peripheral is plugged into? I'm at point in my knowledge of Linux where I have learned just enough to be dangerous. I try to be careful and make sure I understand what each command is doing before I execute it, but I do screw things up sometimes.

Your only suggestion that I haven't tried yet is turning off XHCI. Will go try to find out what that does now.
 
Old 10-01-2015, 06:50 PM   #19
loshakova
Member
 
Registered: Apr 2012
Posts: 111

Original Poster
Rep: Reputation: Disabled
@ferrari:

By the way, thanks for your patience and clear explanations. I really appreciate it.
 
Old 10-01-2015, 07:30 PM   #20
ferrari
LQ Guru
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 5,779

Rep: Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139
Quote:
Is there any sort of command I could have executed that could have confused the computer about what kind of port a peripheral is plugged into? I'm at point in my knowledge of Linux where I have learned just enough to be dangerous. I try to be careful and make sure I understand what each command is doing before I execute it, but I do screw things up sometimes.
Making mistakes is part of learning, and with Linux one doesn't stop learning.

Quote:
Your only suggestion that I haven't tried yet is turning off XHCI. Will go try to find out what that does now.
Ultimately, only a bug report (with developer assistance) will fix any regressions associated with using the xhci_hcd driver. Disabling XHCI mode in the BIOS is only a workaround, and not suitable to implement for all users.

Quote:
@ferrari:

By the way, thanks for your patience and clear explanations. I really appreciate it.
My pleasure. I just hope we can help you resolve this issue, even if only by working around the problem for now.
 
Old 10-01-2015, 07:48 PM   #21
ferrari
LQ Guru
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 5,779

Rep: Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139
I don't want to complicate this thread, but for others who come searching and having problems with XHCI and scanner devices in particular, I want to share these openSUSE threads:

https://forums.opensuse.org/showthre...system-runtime
https://forums.opensuse.org/showthre...95#post2714695

In the latter thread, a user with a particular Intel host controller chipset provides details on how to configure individual USB ports as USB 2.0 contollers using the setpci command. This approach won't necessarily work with other controller chipsets though.

Quote:
I didn't actually think disabling USB3.0 would be a wise long-term decision for my new PC, so I looked around for possible software solutions. It is then that I stumbled on this interesting post (scroll down to where it says "setpci"):
http://superuser.com/questions/81202...ork-as-usb-2-0

However, looking into the specifications of the motherboard, my PC has the 9-series chipset of Intel, for which the documentation can be found here
http://www.intel.com/content/www/us/...datasheet.html

WARNING: all the below is chipset specific for the Intel 9 series
 
Old 10-05-2015, 06:59 PM   #22
loshakova
Member
 
Registered: Apr 2012
Posts: 111

Original Poster
Rep: Reputation: Disabled
@ferrari:
I'm sorry for the delay. I have been working on this in the evenings, but I can't figure out how to disable XHCI in pre-boot. I've gone through each feature of each menu tab in the BIOS, and there is nothing that mentions XHCI.

In the Advanced tab, there are only three possible things to disable (all currently enabled):
Intel (R) SIPP Support
CPU CRID Support
Chipset CRID Support

I've been reading around other forums in case someone else had this problem and came up with a solution. I found two discussions of xhci problems that asked the person to run some diagnostics you hadn't yet asked me to run, so I ran them in case they will be helpful:

$ dmesg | grep xhci
Code:
[    0.606224] xhci_hcd 0000:00:14.0: xHCI Host Controller
[    0.606226] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 3
[    0.606311] xhci_hcd 0000:00:14.0: cache line size of 64 is not supported
[    0.606324] xhci_hcd 0000:00:14.0: irq 41 for MSI/MSI-X
[    0.606371] usb usb3: Manufacturer: Linux 3.13.0-37-generic xhci_hcd
[    0.609285] xhci_hcd 0000:00:14.0: xHCI Host Controller
[    0.609287] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 4
[    0.609320] usb usb4: Manufacturer: Linux 3.13.0-37-generic xhci_hcd
[    1.445357] usb 3-2: new high-speed USB device number 2 using xhci_hcd
[    1.657173] usb 3-10: new high-speed USB device number 3 using xhci_hcd
[    1.801480] usb 4-2: new SuperSpeed USB device number 2 using xhci_hcd
[    1.905190] usb 3-2.1: new high-speed USB device number 4 using xhci_hcd
[    2.034050] usb 3-2.4: new high-speed USB device number 5 using xhci_hcd
[    2.153822] usb 4-2.1: new SuperSpeed USB device number 3 using xhci_hcd
[    2.249760] usb 4-2.4: new SuperSpeed USB device number 4 using xhci_hcd
[    2.357112] usb 3-2.4.3: new low-speed USB device number 6 using xhci_hcd
[    2.453383] usb 3-2.4.4: new low-speed USB device number 7 using xhci_hcd
$ dmesg | grep ehci
Code:
[    0.575616] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    0.575627] ehci-pci: EHCI PCI platform driver
[    0.575705] ehci-pci 0000:00:1a.0: EHCI Host Controller
[    0.575708] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
[    0.575723] ehci-pci 0000:00:1a.0: debug port 2
[    0.579625] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
[    0.579636] ehci-pci 0000:00:1a.0: irq 17, io mem 0xf7138000
[    0.589977] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
[    0.590010] usb usb1: Manufacturer: Linux 3.13.0-37-generic ehci_hcd
[    0.590225] ehci-pci 0000:00:1d.0: EHCI Host Controller
[    0.590228] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
[    0.590243] ehci-pci 0000:00:1d.0: debug port 2
[    0.594139] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
[    0.594148] ehci-pci 0000:00:1d.0: irq 23, io mem 0xf7137000
[    0.605962] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
[    0.605988] usb usb2: Manufacturer: Linux 3.13.0-37-generic ehci_hcd
[    0.606136] ehci-platform: EHCI generic platform driver
[    0.901752] usb 1-1: new high-speed USB device number 2 using ehci-pci
[    1.145623] usb 2-1: new high-speed USB device number 2 using ehci-pci
 
Old 10-05-2015, 08:40 PM   #23
ferrari
LQ Guru
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 5,779

Rep: Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139
Unfortunately, that output shows little more than what you already posted when attaching your scanner. It does show that you have a USB 2.0 port (port 2?) available. If XHCI can't be disabled, I'm not sure what else to suggest, other than to try locating and attaching to the USB 2.0 port. When you do so, you should observe dmesg output referencing the ehci_pci driver only.

Last edited by ferrari; 10-05-2015 at 08:41 PM.
 
Old 10-05-2015, 08:48 PM   #24
ferrari
LQ Guru
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 5,779

Rep: Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139
Another idea that may or may not appeal, is to consider purchasing and installing a cheap USB 2.0 card as a workaround.
 
Old 10-06-2015, 05:54 PM   #25
loshakova
Member
 
Registered: Apr 2012
Posts: 111

Original Poster
Rep: Reputation: Disabled
@ferrari:
The scanner was working perfectly when I first installed Mint 17.1, so I was pretty sure I could fix the problem again without additional hardware by doing a clean install.

As a last-ditch experiment, I unplugged the scanner cable from the dedicated USB 2.0 port on the computer, and plugged it into my USB 3.0 power strip (which is plugged into one of the USB 3.0 ports). Xsane now loads in seconds without a reboot. Yay! I'm still not sure why this is, though. Do the results of my experiment suggest that I have a bad port on my computer? If so, I can get it repaired under warranty. Or, could I have done something to screw up the software instructions to one port (but not another) when I was trying to get my older scanner working in VueScan?

In case it will help any to know this, I have a small partition set up with a Windows 7 dual boot, and in Win7 the keyboard and mouse (which are both plugged into the USB 3.0 power strip that just fixed the scanner problem) have only ever worked in Safe Mode. I was blaming that on Microsoft, but now I'm wondering.
 
Old 10-06-2015, 11:01 PM   #26
ferrari
LQ Guru
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 5,779

Rep: Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139
Quote:
As a last-ditch experiment, I unplugged the scanner cable from the dedicated USB 2.0 port on the computer, and plugged it into my USB 3.0 power strip (which is plugged into one of the USB 3.0 ports). Xsane now loads in seconds without a reboot. Yay! I'm still not sure why this is, though.
Good to know that this works for you. It would need further analysis of the kernel messaging to know why the difference.

Quote:
Do the results of my experiment suggest that I have a bad port on my computer? If so, I can get it repaired under warranty. Or, could I have done something to screw up the software instructions to one port (but not another) when I was trying to get my older scanner working in VueScan?
I doubt that bad hardware is at play here. Do other devices behave properly when attached to these ports? Installing software won't have impacted either. The hardware is controlled and communicated with via kernel drivers at a low level, and full speed (USB 2.0) hardware not always handled correctly with XHCI drivers and certain chipsets. It is possible to debug further, but only worthwhile doing if you're wanting to submit a kernel bug report IMO.

Last edited by ferrari; 10-06-2015 at 11:02 PM.
 
Old 10-07-2015, 12:00 AM   #27
loshakova
Member
 
Registered: Apr 2012
Posts: 111

Original Poster
Rep: Reputation: Disabled
@ferrari:
Would submitting a kernel but report possibly help to fix a bug, or make other users able to find it more easily? If so, then I'd be happy to file a report. I haven't ever done one before, so I looked around and found this page. Is that a good place to start? Or do you have other suggestions given what you know of my issue?
 
Old 10-19-2015, 02:00 PM   #28
debguy
Member
 
Registered: Oct 2014
Location: U.S.A.
Distribution: mixed, mostly debian slackare today
Posts: 207

Rep: Reputation: 19
they (used to?) have excellent scanners at drug stores, and also at office supply / copy store. great quality and cheap: on film or on disk

you might consider if it's not worth your time not to make use of those quality services

----------------------
i never got a scanner for that reason: huge image files low quality, and took people all day to do, and many had to fool with (even in win95) continual "doesn't work as inteded" issues (yet more time lost to getting intended purchase results).

i still use a pin-impact printer (the kind automotive uses in various station equipment because: they never ever fail, per say. even more reliable is supposed to be thermal.)

when i want quality and number: i let the office store do it, it's way cheaper per page

if i'm stuck and need something printed: i use my hand, or the ever reliable dot-impact

(in 30 years this printer has needed: one perhaps two ribbon replacement for $12. ouch what a time loss huh?)

if i'm in a hurry i can simply copy text to it: no drivers necessary, in the old days hardware had internal drivers that worked and extended drivers for extra features

today's equivalent which doesn't even exist would be: i could copy an mpeg to my /dev/vid00 file and it would show up on the screen. but it wont! because the video card has no internal support even if it does have an mpeg chip today's hardware generally is CRAP - having no built-in functionality that actually works unless special code mothers it and "offers it only to inteded OS such as microsoft".

another example: serial port or even scsi port. USB you need drivers to detect or no can talk. serial: could talk to anything with no drivers using telnet, and many devices were build with a few features so you could (pull data) without any extended knowlege of features

today's hardware is thrown together chips without any internal functionality: it does not work except with proprietary drivers that are *sometimes* available in linux.

it's all crap is why. no BIOS.

now video cards had VGA/VESA bios some still do: even that many remove (ie, ATI, broken vga/vesa, you needed special driver to enable VGA. why? VGA was not in silicon or in BIOS !! was cheap as crap and thrown together. obviously.)
 
Old 10-19-2015, 02:08 PM   #29
debguy
Member
 
Registered: Oct 2014
Location: U.S.A.
Distribution: mixed, mostly debian slackare today
Posts: 207

Rep: Reputation: 19
now consider IDE USB (assuming USB drivers loaded and kernel with usb ide support). not such a problem right? well #1 it has support in linux. #2 it does have some IDE functionality built-in is why it's not a total B*t ch. but many devices do not have anything built-in - just a pile of chips (plus 1 generic pci chip) that do not know how to do a thing until a driver talks to it using a special bit protocol (and even then, many issues: modality and buss issues must be worked around for the thing to actaully function)

i'm sitting next to a VGA 11x8.5" full page MONITOR (B&W though) with a serial connector that's right you can litterally copy text to this monitor from your terminal and it appears on the screen or put it in a mode to do graphics if you know how (give it commands to). it has built-in serial io bios and IBM characters is why. it's from an old PC (non dos/intel based, motorolla based) that was expensive and back then though all terminals were devices you could copy text to and have it directly on the screen, with cursor and color support (sometimes vector graphics too) built-in to the "monitor/keyboard". that's a "real terminal"! really does what it does no drivers required, works with any system.
 
Old 10-19-2015, 11:46 PM   #30
loshakova
Member
 
Registered: Apr 2012
Posts: 111

Original Poster
Rep: Reputation: Disabled
@debguy: Thank you for your suggestions. It's difficult for me to travel to a place where I could get scans or copies made, so it was worth the effort to get my printer working. I'm still not able to use SimpleScan, which I really liked, but I'm managing with XSane, so I'll probably close the thread.

FWIW, I agree with you on the durability of older hardware. I'm still using a large VGA monitor with a serial connector myself. I never had a dot matrix printer for home, but I used one at work for years and it never broke down. The last time I had to get a new computer, I looked for the one with the best build quality and the fewest bells and whistles. I have been very happy with my choice so far.

Best regards.
 
  


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] Linux Mint 17 mate on asus eee seashell somewhat slow jf.vdbosch Linux - Laptop and Netbook 12 09-24-2014 02:11 AM
[SOLVED] Have DCP=7065DN all in one laser on Linux Mint 17 Mate help with scanner install 1sweetwater! Linux - Hardware 1 06-30-2014 07:07 AM
Mint Maya - Mate cannot load peripherals or programs Hatman KZN Linux Mint 1 08-06-2012 02:52 PM
downloading the proper driver for my epson v30 scanner, on mint 13 mate, louiemat Linux - Newbie 0 07-29-2012 02:26 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 08:36 AM.

Main Menu
Advertisement
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
Open Source Consulting | Domain Registration