Source: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/311191
Binary package hint: libsane
Epson 3490 wont run without the following modification
The following steps did it for me (running 8.04 Hardy, 8.10, 9.04):-
1) sudo apt-get install sane-utils
2) Go to the Users and Groups screen and add yourself (and other
scanner users) to the "scanner" group.
3) Log off and on (or reboot) to make 2) effective.
4) sudo mkdir /usr/share/sane/snapscan
5) sudo cp Esfw52.bin /usr/share/sane/snapscan
6) sudo chmod 644 /usr/share/sane/snapscan/Esfw52.bin
7) sudo gedit /etc/sane.d/snapscan.conf
Change firmware entry to say:-
firmware /usr/share/sane/snapscan/Esfw52.bin
Please note point 6 as the file was initially created with insufficient access.
Firmware .bin is attacted
http://ubuntuforums.org/showthread.php?t=108256&page=6 - is the scanner being discussed
=================
# How to scan from the shell:
scanimage --device-name snapscan:libusb:002:006 --resolution 200 --high-quality=no --mode Color --format=pnm > lastscan.pnm
# Convert the file to jpg:
convert lastscan.pnm 01.jpg
# To convert all the pnm files to jpg files, type this command on one line:
for i in `ls *.pnm`; do convert $i $i.jpg; done
=================
Friday, March 26, 2010
Wednesday, March 3, 2010
Ubuntu - how to fix the annoying error "resolvconf: Error: /etc/resolv.conf must be a symlink"
How to fix the error: "resolvconf: Error: /etc/resolv.conf must be a symlink"
1. Kill the NetworkManager process:
sudo kill -9 `ps aux | grep sbin/NetworkManager | grep -v grep | awk '{print $2}'`
2. Run the resolvconf reconfiguration tool:
sudo dpkg-reconfigure resolvconf
(select YES, OK )
3. Verify that the resolv.conf file is ok:
ls -la /etc/resolv.conf
It should look very close to this:
lrwxrwxrwx 1 root root 31 2010-03-03 19:53 /etc/resolv.conf -> /etc/resolvconf/run/resolv.conf
4. Check the contents, it should have your name server(s) listed. The following shows an example using Comcast nameservers, and includes a router with address 192.168.0.1:
cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 68.87.74.162
nameserver 68.87.68.162
nameserver 192.168.0.1
search wp.comcast.net
5. Verify that it all works, try a restart of your system, and start with:
ping google.com
If you get a reply, your network works.
Share
1. Kill the NetworkManager process:
sudo kill -9 `ps aux | grep sbin/NetworkManager | grep -v grep | awk '{print $2}'`
2. Run the resolvconf reconfiguration tool:
sudo dpkg-reconfigure resolvconf
(select YES, OK )
3. Verify that the resolv.conf file is ok:
ls -la /etc/resolv.conf
It should look very close to this:
lrwxrwxrwx 1 root root 31 2010-03-03 19:53 /etc/resolv.conf -> /etc/resolvconf/run/resolv.conf
4. Check the contents, it should have your name server(s) listed. The following shows an example using Comcast nameservers, and includes a router with address 192.168.0.1:
cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 68.87.74.162
nameserver 68.87.68.162
nameserver 192.168.0.1
search wp.comcast.net
5. Verify that it all works, try a restart of your system, and start with:
ping google.com
If you get a reply, your network works.
Share
Subscribe to:
Posts (Atom)