Forum Home
Press F1
Thread ID: 146140	2018-05-02 23:50:00	Wifi or scanner issue, Linux	piroska (17583)	Press F1

Post ID	Timestamp	Content	User
1449165	2018-05-02 23:50:00	My brother has a laptop with Mint Sylvia. And an MX726 printer/scanner. The printer and the scanner part both work just fine, via wifi on this. He installed Sylvia yesterday on the desktop. Printer, via USB wifi device, picked up and installed just fine. The scanner won't, running the install.sh gives no scanners found. How to troubleshoot this? I have no clues where to start, not using wifi at all on mine. Or is it to do with the scanner? Same driver he used on both machines. Same O/S and version too.	piroska (17583)
1449166	2018-05-03 04:20:00	I had a mx726, to get the scangearmp to work you follow the instructions on this site: tipsonubuntu.com As he already has the printer working you just need the scangearmp-common-64 and scangearmp-mx720series-64 (assuming he's got the 64 bit OS) So first add the ppa, then reload synaptic package manager, then search for scangearmp to get the software to work once you have it installed, you can type scangearmp into the terminal or make a desktop launcher to do it. Note: I first tried the official Canon version with no success.	KarameaDave (15222)
1449167	2018-05-03 04:55:00	Thanks. But he did get the driver. It installed just fine on laptop. On desktop it starts then says No Scanners found. You see? Same driver, same scanner, same O/S.	piroska (17583)
1449168	2018-05-03 07:05:00	If your brother or anyone else has these kinds of issues, you can get real time help from the community using hexchat, an IRC client, found in the Internet menu, it'll open up a channel in #linuxmint-help where you just ask if anyone can help you get your device (say make/model) working. My nick is 'talented' or my actual name but I only use that when discussing development issues. Remember timezone differences, most helpers seem US based, so you get more help at certain times during the day. The information they would normally want to see is: inxi -Fxxxzrc0 | nc termbin.com 9999 (There's a GUI tool to do this, I'll need to get back on what it is, but it is related to hardware information or maybe system) This creates a link of the information at termbin.com you share this link, it is specific information on your computer hardware which let's us know what computer, kernel, mint release, etc is in question. Now for USB, there's 2 ways I like to look at it, first, how it gets detected by the computer, so you unplug it, then plug it in and run the command: dmesg | tail | nc termbin.com 9999 Now dmesg is sort of a realtime log, you unplug a hot swappable device like USB it will tell you it's been disconnected, you plug it back in, another message will say it detected it, it will contain ID information about the device, possibly where it was mounted, etc. The command tail, which you piped to this character | to the command (just imagine it works left to right, dmesg pushes what it returned to tail and then tail pushes its results to nc (netcat, kinda like telnet) sends it over the internet to termbin. Anyways what tail does is grab the last (20?) lines of that report, 'head' grabs the top 20, you can add options to increase how many lines it grabs. So we hopefully only capture the USB part of it connecting. What's important here is that the computer sees it, if unplugging and plugging it back in shows nothing, it means the computer is not going to detect it, so we may have an issue between USB port to device, so determine if the port works, try maybe another USB device in it, if that works, we know port is good. Alternatively, plug the device in another USB port, if that fails, we may think ports or device still. If a USB hub is involved, plug direct to computer (USB hubs can sometimes be underpowered, same with front USB ports), when I test my own USB devices, I measure amps and voltage output to ensure its enough to power the device, but I wouldn't expect many to have the capabilities of testing their ports, I do, for development reasons. Anyways, just trying to give you ways on troubleshooting and what you could encounter. So if still nothing, we need to look at device, make sure its powered on, cable in properly etc. If still no go, change cable, it's the only thing we haven't eliminated. Anyways, its being detected, its printing, we got that going, hopefully in dmesg it shows us a printer and a scanner, I haven't used one of these devices in a while, so not sure if it separates them as 2 individual devices detected (it should in my views). OK so we have printer going, if dmesg detects scanner too, basically look at the description, if it says device ####:#### where those are numbers, it sees it but really does not know what it is, sometimes it can say its make followed by numbers (ID of the device), means it knows who makes it but still not sure what it is, this in most cases means we don't have the drivers, so search that make and ID and you may find drivers, or someone else with that issue. Another command I would run is if dmesg shows the device lsusb | nc termbin.com 9999 This shows you all USB devices detected, hub/ports, etc, it gives manufacturer, IDs, etc. This is just easier ID information to use for searching and to tell if the driver is installed correct else you'll just see the ID number. Anyways, that's just a few troubleshooting tips, you can compare this on the other computer to see any differences, it may help? Anyways, let's say everything is good, its all detected but the script can't detect the device. First off, let's try the script as a super user, if it works, it's permission problems, this means your user is missing a group it needs to belong to. This command groups Shows what groups you belong to, run it on both computers and see if there's any groups you don't belong to, sometimes its obvious. So maybe his user needs to belong to 'scan' or something similar. Anyways, that's my guess on what the problem could be without any information. Otherwise it maybe a udev issue, which I hope it's not, because that involves creating configs and Mint should be easier than that. I hope this information helps you out, I hope I didn't leave steps out, since I'm not behind my computer, but I should write tutorials on these methods for others to use.	Kame (312)
1449169	2018-05-03 07:56:00	wow Thanks. Very helpful. Don't understand a few bits, never mind, I could follow that. I have asked him to do 4 things in order. 1)Try it with firewall off 2)Download driver again, via Software Manager 3)Try my driver. All I can see is there are 2, scangearmp and scangearmp2. I suspect it's not so much model specific as a later version. (?) Anyway, worth a try. 4)Plug it in via usb cable. At present he is using it via wifi. That worked just fine with his laptop. Same driver (the first one). Why it should be any different on the desktop, when it is the same printer/scanner and same O/S is the issue. But my thought was, see if it finds it with the cable, and if so, then try connecting wifi.... If it still doesn't, well um...weird. It worked fine on laptop. The difference? Laptop has built in wifi, desktop has a usb wifi gadget. But so? It found the printer and installed perfectly well, so that to me, eliminates the wifi as the issue. Anyway, waiting on him trying those 4 steps....	piroska (17583)
1449170	2018-05-03 08:26:00	Sorry I left key things out: To add your user to the group, go Users and Groups found in Administration? Find your User, then enter a tab that says Groups or maybe a button? and then check the scanner? group. Sorry I am not sure of the group, but anything scanner related, possibly sane, it should not be lpadm or anything lp unless it was printer port but no harm adding to that group. Because I can't remember the group names the GUI is the best way to avoid me issuing bad commands. For some programs you run in terminal, you can add the -d option, which may give debugging information in the terminal while the program runs which may provide clues to what is the problem. OK, still avoiding udev but basically this is a user device configuration, you can literally control how you like the device to be setup to avoid automatic settings that your OS provides. Like you insert a particular USB thumb drive, you rather have it mounted as /mnt/mydrive (instead of the default /run/media/whatever) or you'd want something special to happen, like to unencrypt it etc. That's what udev is about, and you can also do permissions, etc. It just an advance way to configuring specific devices, maybe only you want it to mount but other users, you want nothing to happen, no mounting, etc, which prevents them being able to format it on that particular machine. Anyways, now I hope I haven't skipped anything. Much easier behind my computer but I'm on my phone. So WiFi works? OK, so in other words, networking to it works, but directly connected via USB doesn't. Again, I suggest he runs his scanner program as a super user. sudo name_of_scanner_program If it works as root, it's most like user permission. You are more than likely able to network without issues, accessing devices, especially physical, normally requires permission to do so, e.g. normal user should not be able to access memory directly, so some devices have these permissions needed, what let's users have automatic permission is because the driver installed is a user mode driver, but sometimes it's installed under the program, most scanners belong to sane/saned, so if you use that program, the program has rights to access it rather than the user. Try the super user to run the scanner program, it'll clear up an important piece.	Kame (312)
1449171	2018-05-03 23:38:00	OK, he got it to actually scan using an old scangear driver. 2.10. Why? No idea. It does scan but staright after it comes up with his in terminal. All I can think, is there's stuff missing? Why this on desktop yet newer driver works on laptop? Bizarre. Anyway PMed you... heres the screenshot8809	piroska (17583)
1449172	2018-05-04 08:08:00	OK, he must have to build/compile this driver which isn't the best way to get drivers. There are some deb files I noticed, latest version 3.9 that I could see at canon's asia site but not sure if he needs that or an older version. deb files will save him finding the needed dependencies if they can find all missing files in the repository. Anyways, instead of saying install this and that (on my phone again), you can do: apt search autoconf or apt contains file_thats_missing then sudo apt install a name like that as well as any with -dev on the end so if autoconf returned autotools, autotools-dev (just an example, not actual results) he can do: sudo apt install autotools{-dev} what {-dev} does is act like he ran the command twice, so sudo apt install autotools sudo apt install autotools-dev or it does sudo apt install autotools autotools-dev pretty good for saving on typing. looking at this he may only need to install build-essentials but in case it complains about things missing, especially errors, they need to be dealt to before it'll work. deb files are preferred, they are Mint's equivalent of .exe/.msi installation binaries.	Kame (312)
1449173	2018-05-04 09:02:00	As for his laptop vs PC, he may have already installed all the needed libraries and programs on his laptop before he installed the driver. I don't think his laptop is a fresh install. If he ran this on his laptop: dpkg --get-selections > mypackages this creates a text file called mypackages with all his packages installed on the laptop, via deb package managers like apt, gdebi, etc. He can then look through that text file, remove packages that maybe only for his laptop then take that text file to his PC and run: sudo dpkg --set-selections < mypackages sudo apt dselect-upgrade So it sets all the packages from that file to a type of queue then the apt command will install it, but only the missing packages that are not installed. Normally useful if you need to have similar programs on all machines.	Kame (312)
1449174	2018-05-04 14:56:00	I'm on my computer now so this will make things easier: Anyways lets avoid the source code he's using for now and use these debian driver packages found here: Printer Driver (Canon MX720 Series Inkjet Version 3.9): support-th.canon-asia.com Scanner Driver (Canon ScanGear MP Version 2.10): support-th.canon-asia.com Now these drivers are old so there's no guarantee they will work, when he downloads the file and extracts it, it should be a *.deb file, he can double click on it and gdebi will open. It will let him know if he can go ahead with the install or whether something can't be found. If it can't be found, it usually means it's also not available in the default repositories, maybe they require earlier versions that won't be installed, etc. In this case, he could try to force the installation, in which it will install and may work or not. ScanGear MP says it must be run with GIMP, bit overkill I think, but it's what it said in that image you posted.	Kame (312)
1 2