[sane-devel] [sane-pixma] Canon MF4150 v. PIXMA_CAP_LINEART
Hi Samuel,
Am 27.08.2013 13:05, schrieb Samuel Adam:
> clang had spit out a few warnings on pixma_imageclass.c; such were
> simple format string issues which seemed on a relevant codepath, and
> are fixed in the attached patch. My trivial tweak did not fix the
> segfault (although uint64_t is indeed wider than %u on my machine).
> pixma_imageclass.c now compiles without warnings.
Many thanks for your patch.
Am 28.08.2013 08:55, schrieb Samuel Adam:
> Skimming the code, I am about 80% certain that:
>
> (1) It is dying between these two points in the codepath:
>
> (a) pixma_imageclass.c: iclass_check_param()
> (b) pixma.c: start_reader_task()
>
> (Viz.: Successfully completes the former; segfaults at an undetermined
> point before reaching or completing the latter.)
>
> (2) Up to that point, the *only* substantive changes induced by the
> patch are alterations to the values of various data structures.
>
> ===> Therefore: Is there anything which jumps out to those familiar
> with the code between point (a) and point (b) which would or could choke
> upon a change in the size, shape, or contents of pixma_scan_param_t
> structure? (There is one other blackmagic blob of bit-stuffing changed
> before that. The change is only effective if the "--mode" is set to
> "Lineart", however; whereas the segfault occurs regardless.)
>
The segfault is produced inside iclass_check_param(). You can see in the
log that the segfault happens somewhere between the log output lines
"PDBG (pixma_dbg (4, "*iclass_check_param* Initially: ... ));"
and
"PDBG (pixma_dbg (4, "*iclass_check_param* Finally: ... ));"
The attached patch should fix this item.
Some background info how lineart scan is working (if you like to debug
this by yourself):
(1) The frontend requests a lineart scan with 1 bit per pixel.
(2) The backend scans a grayscale image with 8 bits per pixel.
(3) The backend converts 8 bits per pixel to 1 bit per pixel for each
single line.
If you need debug infos you only have to insert "PDBG (pixma_dbg (4, ...
));" with the needed data to the code.
If the code is still buggy, please send a log file offlist again.
Cheers,
Rolf
-- next part --
--- ./pixma_imageclass.c2013-08-28 21:57:59.0 +0200
+++ ../sane-backends/backend/pixma_imageclass.c 2013-08-28 21:58:03.0
+0200
@@ -505,7 +505,7 @@
sp->depth = 8;
sp->software_lineart = 0;
- if (sp->param->mode == PIXMA_SCAN_MODE_LINEART)
+ if (sp->mode == PIXMA_SCAN_MODE_LINEART)
{
sp->software_lineart = 1;
sp->channels = 1;
[sane-devel] Updated info for Canon LiDE 500F
Hi Stef, thanks for getting back to me. Outputs of "lsusb -v" and "sane-find-scanner" are attached. Thanks, Dan On 28 August 2013 05:33, Stef wrote: > On 24/08/2013 10:45, Daniel Ellis wrote: > > I wasn't certain the info on the unsupported Canon CanoScan LiDE 500F > was correct: > > http://www.sane-project.org/unsupported/canon-canoscan-lide-500f.html > > On this page it says the chipset is GL841. I have given up on this > scanner, so I decided to take it apart to check the chip, and it turns out > the chip is a GL120. > > Picture of the chip: http://postimg.org/image/y53f9ekpv/ > > I would be grateful if someone could update the webpage, and hopefully > this info may help someone else have some better luck with this scanner! > > Regards, > Daniel Ellis. > > > > Hello, > > what does 'lsusb -v' reports for your device ? > > Regards, > Stef > -- next part -- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130828/f3f27fc2/attachment.html> -- next part -- Bus 002 Device 004: ID 04a9:221f Canon, Inc. CanoScan LiDE 500F Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 255 Vendor Specific Subclass bDeviceProtocol 255 Vendor Specific Protocol bMaxPacketSize064 idVendor 0x04a9 Canon, Inc. idProduct 0x221f CanoScan LiDE 500F bcdDevice3.03 iManufacturer 1 Canon iProduct2 CanoScan iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0001 1x 1 bytes bInterval 8 Device Qualifier (for other device speed): bLength10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 255 Vendor Specific Subclass bDeviceProtocol 255 Vendor Specific Protocol bMaxPacketSize064 bNumConfigurations 1 Device Status: 0x0002 (Bus Powered) Remote Wakeup Enabled -- next part -- # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. found USB scanner (vendor=0x04a9 [Canon], product=0x221f [CanoScan], chip=GL842) at libusb:002:004 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. # Not checking for parallel port scanners. # Most Scanners connected to the parallel port or other proprietary ports # can't be detected by this program.
[sane-devel] Canonscan N 650U LIDE Scanner does not scan but makes terrible noise
oise > scan @ 50 dpi --> OK, no noise > close xsane, open xsane > preview --> OK, no noise > close xsane, open xsane, scan @ 50 dpi --> NOISE!!! > disconnect/reconnect --> no noise > scan @ 50 dpi --> I/O Error > close xsane, open xsane --> NOISE! > (with noise still there) scan @ 50 dpi --> OK! (and noise stops) > close xsane, disconnect the scanner > > another attempt: > connect scanner, open xsane --> no noise > scan @ 50 dpi --> NOISE! > cancel scan, disconnect --> scan canceled > connect --> no noise > scan @ 50 dpi --> I/O Error > close xsane, open xsane --> NOISE! > scan @ 50 dpi --> NOISE! > disconnect, cancel scan --> xsane freezes > kill xsane, connect, open xsane --> NOISE! > close xsane --> xsane freezes (still noise) > disconnect, kill xsane, connect, open xsane --> NOISE! > (with noise still there) scan @ 50 dpi --> OK! (and noise stops)... > what's the difference between the situation here and the preceding NOISE > after the scan? > close xsane, disconnect the scanner > > Il giorno lun, 26/08/2013 alle 17.13 +0200, Winni ha scritto: > > Hi, > > again, I tried 20 minutes to scan with the Canonscan N 650U. In > > comparison to the last time, all attempts resulted this time in this > > awful noise. > > I booted WinXP 32-bit (twain drivers) and within 2 minutes two pages > > were scanned perfectly. > > > > How can I help you guys with this? Is there anything I can contribute to > > make this scan device work for Linux OS without having skills of writing > > code? > > > > Thanx und regards, > > > > Winni > > > > > > > > Original-Nachricht > > Betreff: Re: [sane-devel] Canonscan N 650U LIDE Scanner does not scan > > but makes terrible noise > > Datum: Sun, 11 Aug 2013 20:25:06 +0200 > > Von: Winni <"windose"@kabelmail.de> > > An: sane-devel at lists.alioth.debian.org > > > > Hi, > > > > I tried with different dpi resolutions. Most of the time it starts with > > the horrible noise but sometimes it works. I'd say every 5th try works. > > Even calibrating under XSane results in that noise... > > > > I searched for a plustek config file but could not find it. > > > > By the way, there is a hint about "awfull noise" in the FAQ.gz at > > /usr/share/doc/libsane/plustek/ > > > > > > SYMPTOM: Scanner makes awful noise > > > > > > > > > PROBLEM: > > > > > > This can have two major causes: > > > - You have an ASIC96001/3 based scanner, then the sensor hits the > > > scanbed: !!! TURN OFF SCANNER POWER !!! > > > > > > - You have an ASIC98001 based scanner, then the motor control does > > > not work correctly --> hit the cancel button > > > > > > SOLUTION: > > > - > > > For the first case (ASIC 96001/3), there's no solution available. This > > > happens, when the driver can't keep track of the stepper motor. The image > > > you get is normally unusable. > > > The second case is often reported when the printer driver lp.o is > > > already loaded. So remove lp.o before loading pt_drv. > > > > > > Regards, > > Winni > > > > > > > > > > > > -- > sane-devel mailing list: sane-devel at lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to sane-devel-request at lists.alioth.debian.org -- next part -- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130828/0f7408cf/attachment.html>
[sane-devel] Canonscan N 650U LIDE Scanner does not scan but makes terrible noise
oise > scan @ 50 dpi --> OK, no noise > close xsane, open xsane > preview --> OK, no noise > close xsane, open xsane, scan @ 50 dpi --> NOISE!!! > disconnect/reconnect --> no noise > scan @ 50 dpi --> I/O Error > close xsane, open xsane --> NOISE! > (with noise still there) scan @ 50 dpi --> OK! (and noise stops) > close xsane, disconnect the scanner > > another attempt: > connect scanner, open xsane --> no noise > scan @ 50 dpi --> NOISE! > cancel scan, disconnect --> scan canceled > connect --> no noise > scan @ 50 dpi --> I/O Error > close xsane, open xsane --> NOISE! > scan @ 50 dpi --> NOISE! > disconnect, cancel scan --> xsane freezes > kill xsane, connect, open xsane --> NOISE! > close xsane --> xsane freezes (still noise) > disconnect, kill xsane, connect, open xsane --> NOISE! > (with noise still there) scan @ 50 dpi --> OK! (and noise stops)... > what's the difference between the situation here and the preceding NOISE > after the scan? > close xsane, disconnect the scanner > > Il giorno lun, 26/08/2013 alle 17.13 +0200, Winni ha scritto: > > Hi, > > again, I tried 20 minutes to scan with the Canonscan N 650U. In > > comparison to the last time, all attempts resulted this time in this > > awful noise. > > I booted WinXP 32-bit (twain drivers) and within 2 minutes two pages > > were scanned perfectly. > > > > How can I help you guys with this? Is there anything I can contribute to > > make this scan device work for Linux OS without having skills of writing > > code? > > > > Thanx und regards, > > > > Winni > > > > > > > > Original-Nachricht > > Betreff: Re: [sane-devel] Canonscan N 650U LIDE Scanner does not scan > > but makes terrible noise > > Datum: Sun, 11 Aug 2013 20:25:06 +0200 > > Von: Winni <"windose"@kabelmail.de> > > An: sane-devel at lists.alioth.debian.org > > > > Hi, > > > > I tried with different dpi resolutions. Most of the time it starts with > > the horrible noise but sometimes it works. I'd say every 5th try works. > > Even calibrating under XSane results in that noise... > > > > I searched for a plustek config file but could not find it. > > > > By the way, there is a hint about "awfull noise" in the FAQ.gz at > > /usr/share/doc/libsane/plustek/ > > > > > > SYMPTOM: Scanner makes awful noise > > > > > > > > > PROBLEM: > > > > > > This can have two major causes: > > > - You have an ASIC96001/3 based scanner, then the sensor hits the > > > scanbed: !!! TURN OFF SCANNER POWER !!! > > > > > > - You have an ASIC98001 based scanner, then the motor control does > > > not work correctly --> hit the cancel button > > > > > > SOLUTION: > > > - > > > For the first case (ASIC 96001/3), there's no solution available. This > > > happens, when the driver can't keep track of the stepper motor. The image > > > you get is normally unusable. > > > The second case is often reported when the printer driver lp.o is > > > already loaded. So remove lp.o before loading pt_drv. > > > > > > Regards, > > Winni > > > > > > > > > > > > -- > sane-devel mailing list: sane-devel at lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to sane-devel-request at lists.alioth.debian.org -- next part -- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130828/62c1e0a7/attachment-0001.html>
[sane-devel] scanbd daemon does not load firmware
On Wed, 2013-08-28, Wilhelm wrote:
> Am 28.08.2013 07:11, schrieb Ilya V. Ivanchenko:
> > I created a neat setup using xinet + scanbd service + scanbd daemon (for
> > buttons) + sane (client) to use Epson GT-1500 (with ADF) as a workhorse
> > of a network scanner, with scanner buttons hooked to various jobs.
> > Everything is working great, except...
> >
> > I encountered a problem after the scanner is powered off and then on
> > again. The buttons service (scanbd daemon) stops reading the buttons and
> > keeps getting "communication error" in the syslog.
>
> that shouldn't happen. Normally, scanbd gets via udev | hal | dbus a
> device-removed event and then abandones the device until it gets plugged
> in again.
Good to know that scanbd should manage firmware loading, it answers the
questions I had. Now it seems we better dig to the root of the
problem...
> So, please show the syslog from beginning of the scanbd log messages and
> in the situation when the device is removed.
I've pasted syslog snippet with the problem when firmware is not loaded
(with scanbd debug-level=7) here (device was removed on Aug 28 18:02:28,
communication error happens on Aug 28 18:03:19):
http://pastebin.com/BweSr5p2
(it will expire in 1 month)
>
> And please: how did you configure / compile, which platform, ...
Ubuntu 12.04LTS on Intel amd64, 1st installed sane and Epson's iscan:
sudo apt-get install sane-utils
sudo dpkg -i iscan-data_1.23.0-1_all.deb
sudo dpkg -i iscan_2.29.1-5~usb0.1.ltdl7_amd64.deb
sudo dpkg -i iscan-plugin-gt-1500_2.2.0-1_amd64.deb
scanimage -L
# works
2nd downloaded scanbd (181-trunk)
Prepared:
sudo apt-get install build-essential checkinstall
sudo apt-get install libconfuse-dev libsane-dev libudev-dev
sudo apt-get install libconfuse-dev libusb-dev libudev-dev libdbus-1-dev
dbus libsane-dev
## Sane option will only work if sane backend supports reading buttons
from the scanner (use "scanimage -A" to check):
# ./configure --prefix= --with-user=saned --with-group=scanner
## Use scanbuttond backend (embedded into scanbd):
./configure --prefix= --with-user=saned --with-group=scanner
--enable-scanbuttond
I patched 2 files:
- src/scanbuttond/backends/epson_vphoto.c - added VID/PID 04B8/0133 for
Epson GT-1500:
{ 0x04B8, 0x0133, 5 } // Epson GT-1500, buttons: 1=scan, 2=copy,
3=email, 4=pdf, 5=stop
...
{ "Epson", "GT-1500"}
- src/scanbd/scanbuttond_wrapper.c function scanbtnd_button_name()
(upped the assert for button count <=4 to <=5 and renamed buttons per
Epson line above)
BTW - it would be nice if device definitions can name their own buttons
instead of hard-coded values.That first list with VID/PID/count_buttons
could contain an array of strings for that.
Then I compiled:
make
sudo make install
The system configuration involved some editing in /etc/, but I think it
is not the issue here. Anyway let me know if you need any other
information.
Regards,
--
Ilya
[sane-devel] Canonscan N 650U LIDE Scanner does not scan but makes terrible noise
Hi, as said in a previous message, I experience the same problem with my N650U on Ubuntu 12.04 LTS. I have done some testing, to understand if the problem depends on the resolution, or on some other aspects. The answer is: I don't know, because the noise sometimes appear on the preview, sometimes on the scan, sometimes just appears connecting the scanner (if it was grinding the last time it was disconnected). Other times it does not grind, and scans smoothly at 50, 100, 300, 600 dpi. Someone here on the list was wondering about the USB cable (shielded, unshielded, I think) playing a role on this... I have only 1 cable at the moment, so I cannot test other ones. But, the question is, would it make sense that the same cable does not work with sane, but works perfectly in windoze? Thanks very much, Andrea Here is a sort of log: Connect the scanner Scan @ 50 dpi --> OK, no noise close xsane, disconnect and reconnect the scanner, open xsane Preview --> OK, no noise Scan @ 50 dpi --> NOISE! disconnect (--> xsane freezes), kill xsane, reconnect the scanner, open xsane --> NOISE! scan, cancel scan --> still noise, xsane freezes kill xsane disconnect, reconnect the scanner --> NOISE! (without opening xsane) (*) open xsane --> still noise scan --> ancora noise cancel scan --> scan does not cancel, xsane freezes, still noise kill xsane --> still noise disconnect, reconnect --> no noise (! : what does make this different from (*) above?) open xsane --> NOISE! preview --> OK, noise stops and the preview works ...so, it seems that the scan works, the preview itself works too, but the preview makes any operation after it get grinding? close xsane, disconnect/reconnect the scanner, open xsane scan @ 50 dpi --> OK scan @ 100 dpi --> OK scan @ 300 dpi --> OK scan @ 600 dpi --> OK so, now scan works at different resolutions preview --> NOISE! so, now the preview itself does not work... cancel preview --> does not cancel disconnect the scanner --> xsane pops up message "scan canceled" connect the scanner --> no noise so, now, try again: close xsane, open xsane --> NOISE! preview --> still noise, xsane freezed disconnect/reconnect the scanner --> no noise kill xsane, open xsane --> still no noise scan @ 50 dpi --> no noise, but when the lamp start going back to its initial position --> NOISE! (NB every trial was made selecting a little square (2x2 inches) for scanning, except this one, where it was scanning the whole A4 page) disconnect, reconnect --> no noise scan @ 50 dpi --> xsane message "I/O Error" close xsane, open xsane --> still no noise scan @ 50 dpi --> OK, no noise close xsane, open xsane preview --> OK, no noise close xsane, open xsane, scan @ 50 dpi --> NOISE!!! disconnect/reconnect --> no noise scan @ 50 dpi --> I/O Error close xsane, open xsane --> NOISE! (with noise still there) scan @ 50 dpi --> OK! (and noise stops) close xsane, disconnect the scanner another attempt: connect scanner, open xsane --> no noise scan @ 50 dpi --> NOISE! cancel scan, disconnect --> scan canceled connect --> no noise scan @ 50 dpi --> I/O Error close xsane, open xsane --> NOISE! scan @ 50 dpi --> NOISE! disconnect, cancel scan --> xsane freezes kill xsane, connect, open xsane --> NOISE! close xsane --> xsane freezes (still noise) disconnect, kill xsane, connect, open xsane --> NOISE! (with noise still there) scan @ 50 dpi --> OK! (and noise stops)... what's the difference between the situation here and the preceding NOISE after the scan? close xsane, disconnect the scanner Il giorno lun, 26/08/2013 alle 17.13 +0200, Winni ha scritto: > Hi, > again, I tried 20 minutes to scan with the Canonscan N 650U. In > comparison to the last time, all attempts resulted this time in this > awful noise. > I booted WinXP 32-bit (twain drivers) and within 2 minutes two pages > were scanned perfectly. > > How can I help you guys with this? Is there anything I can contribute to > make this scan device work for Linux OS without having skills of writing > code? > > Thanx und regards, > > Winni > > > > Original-Nachricht > Betreff: Re: [sane-devel] Canonscan N 650U LIDE Scanner does not scan > but makes terrible noise > Datum: Sun, 11 Aug 2013 20:25:06 +0200 > Von: Winni <"windose"@kabelmail.de> > An: sane-devel at lists.alioth.debian.org > > Hi, > > I tried with different dpi resolutions. Most of the time it starts with > the horrible noise but sometimes it works. I'd say every 5th try works. > Even calibrating under XSane results in that noise... > > I searched for a plustek config file but could not find it. > > By the way, there is a hint about "awfull noise" in the FAQ.gz at > /usr/share/doc/libsane/plustek/ > > > > SYMPTOM: Scanner makes awful noise > > > > > > PROBLEM: > > > > This can have two major causes: > > - You have an ASIC96001/3 based scanner, then the sensor hits the > > scanbed: !!! TURN OFF SCANNER POWER !!! > > > > - You have an ASIC98001 based scanner, then the m
[sane-devel] scanbd daemon does not load firmware
Hello,
Am 28.08.2013 07:11, schrieb Ilya V. Ivanchenko:
> I created a neat setup using xinet + scanbd service + scanbd daemon (for
> buttons) + sane (client) to use Epson GT-1500 (with ADF) as a workhorse
> of a network scanner, with scanner buttons hooked to various jobs.
> Everything is working great, except...
>
> I encountered a problem after the scanner is powered off and then on
> again. The buttons service (scanbd daemon) stops reading the buttons and
> keeps getting "communication error" in the syslog.
that shouldn't happen. Normally, scanbd gets via udev | hal | dbus a
device-removed event and then abandones the device until it gets plugged
in again.
So, please show the syslog from beginning of the scanbd log messages and
in the situation when the device is removed.
And please: how did you configure / compile, which platform, ...
> I tried various things until it occurred to me that Epson GT-1500 uses
> iscan plugin that loads firmware file (/usr/share/iscan/esfw86.bin) and
> the power off-on resets the scanner and thus wipes out the firmware. It
> seems like scanbd daemon does not load the firmware when the scanner is
> powered back on (at least I was not able to find how to configure it to
> do so), and it gets into trouble trying to read the buttons from device
> without its firmware.
This seems to be a consequence of the above failure: the device isn't
closed correctly and not reopened therefore. So the firmware isn't
loaded again (should be done on device opening).
>
> I have few questions to scanbd team:
>
> 1. Can scanbd daemon automatically load firmware file and what should be
> done in the config files to achieve that? sane config files seem to have
> "firmware" option, but I don't see anything in scanbd documentation.
as stated above: should be done on openeing the device
>
> 2. If scanbd daemon currently cannot load the firmware, are there any
> plans to add this feature?
see above
>
> 3. If not, what is the recommended way to set scanbd up so it will work
> with scanners that require firmware to be loaded?
see above
>
> I spent few hours and came up with the following rework using udev rule
> that invokes "scanimage -L" command to pull the command chain that loads
> the firmware. It works fine and I have not seen "communication error" since.
>
> A. Create a script that causes firmware to be loaded (I'm open to other
> methods, but scanimage -L is the only I found so far)
> sudo tee /etc/scanbd/scanner.d/on_insert.sh > /dev/null << CATEOF
> #! /bin/bash
> logger=/usr/bin/logger -t scanbd
> $logger "Loading firmware for $1"
> /usr/sbin/service scanbd stop 2>&1 >/dev/null
> /usr/bin/scanimage -L 2>&1 | $logger
> /usr/sbin/service scanbd start 2>&1 >/dev/null
> $logger "Done loading firmware for $1"
> CATEOF
> sudo chmod a+x /etc/scanbd/scanner.d/on_insert.sh
>
> B. Create udev rule to call the above script.
> sudo tee /etc/udevd/rules.d/98-epson.rules > /dev/null << CATEOF
> # Force firmware load for EPSON GT-1500
> ACTION=="add", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04b8",
> ATTRS{idProduct}=="0133", RUN+="/etc/scanbd/scanner.d/on_insert.sh %p"
> CATEOF
>
>
>
--
Wilhelm
w.meier at unix.net
[sane-devel] Updated info for Canon LiDE 500F
On 24/08/2013 10:45, Daniel Ellis wrote: > I wasn't certain the info on the unsupported Canon CanoScan LiDE 500F > was correct: > > http://www.sane-project.org/unsupported/canon-canoscan-lide-500f.html > > On this page it says the chipset is GL841. I have given up on this > scanner, so I decided to take it apart to check the chip, and it turns > out the chip is a GL120. > > Picture of the chip: http://postimg.org/image/y53f9ekpv/ > > I would be grateful if someone could update the webpage, and hopefully > this info may help someone else have some better luck with this scanner! > > Regards, > Daniel Ellis. > > Hello, what does 'lsusb -v' reports for your device ? Regards, Stef -- next part -- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130828/26db1651/attachment.html>
[sane-devel] [sane-pixma] Canon MF4150 v. PIXMA_CAP_LINEART
On Tue, 27 Aug 2013 13:11:40 -0400, Samuel Adam wrote: > I applied your patch against git version af107912. It segfaults > without producing any noticeable activity in the scanner; and the > segfault occurs whether --mode is set to "Lineart", "Gray", or > "Color". I find this baffling, as on a brief glance the new lineart > code path *seems* to be largely branched over in other modes (at > least > in the logical beginning thereof). [...] > Compiling without the patch, git af107912 seeks to work (with some > flakiness). Skimming the code, I am about 80% certain that: (1) It is dying between these two points in the codepath: (a) pixma_imageclass.c: iclass_check_param() (b) pixma.c: start_reader_task() (Viz.: Successfully completes the former; segfaults at an undetermined point before reaching or completing the latter.) (2) Up to that point, the *only* substantive changes induced by the patch are alterations to the values of various data structures. ===> Therefore: Is there anything which jumps out to those familiar with the code between point (a) and point (b) which would or could choke upon a change in the size, shape, or contents of pixma_scan_param_t structure? (There is one other blackmagic blob of bit-stuffing changed before that. The change is only effective if the "--mode" is set to "Lineart", however; whereas the segfault occurs regardless.) Yes, I am aware that I may get some "wtf" for not simply attaching a debugger. Samuel Adam
