[sane-devel] PIXMA: 1 Bit B/W Lineart for pixma_mp150 and pixma_mp810 Subdrivers
Hi Allan, I still reused the code from the genesys backend. But without a capable genesys or epjitsu scanner I took the code snippets I understood. Please give me a short summary about the missing parts. Especially of the needed interface parameters and the frontend usage e.g. xsane. Many thanks, Rolf Am 03.02.2012 22:40, schrieb m. allan noah: Cool. You might also want to look at the dynamic thresholding code I added to the epjitsu backend. Stef was able to copy it to genesys as well. Basically adds a sliding window and some hysteresis to the threshold determination, brings out text on gray backgrounds and such. I'd like to add it to sanei_magic someday, but don't have the time right now. allan On Fri, Feb 3, 2012 at 4:31 PM, Rolf Benschrolf at bensch-online.de wrote: Hello, I just commited 1 bit B/W lineart for all scanners in the pixma_mp150 and pixma_mp810 subdrivers to the git tree. Due to the fact that these ccd scanners doesn't support generic lineart, I implemented software-lineart. The graphic frontend (Xsane) provides a slider to set the threshold. pixma_mp810 subdriver has been tested well with these scanners: Canoscan 8800F Canoscan 9000F Canon Pixma MP810 Canon Pixma MP960 pixma_mp150 subdriver isn't tested yet. This code should run, because it is similar to the pixma_mp810 code and I compared the diff files. Please report other working scanners to the ML. Cheers, Rolf -- 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
[sane-devel] PIXMA: 1 Bit B/W Lineart for pixma_mp150 and pixma_mp810 Subdrivers
Hello, I just commited 1 bit B/W lineart for all scanners in the pixma_mp150 and pixma_mp810 subdrivers to the git tree. Due to the fact that these ccd scanners doesn't support generic lineart, I implemented software-lineart. The graphic frontend (Xsane) provides a slider to set the threshold. pixma_mp810 subdriver has been tested well with these scanners: Canoscan 8800F Canoscan 9000F Canon Pixma MP810 Canon Pixma MP960 pixma_mp150 subdriver isn't tested yet. This code should run, because it is similar to the pixma_mp810 code and I compared the diff files. Please report other working scanners to the ML. Cheers, Rolf
[sane-devel] Support for CanoScan 9000F and others: Modify dpi_list
Hello, Some scanners supported from the PIXMA driver have different dpi capabilities for flatbed and ADF/TPU modes: e.g. CS9000F supports 75-4800 dpi in flatbed mode and 300-9600 dpi in TPU mode. There are two new parameters in pixma_config_t: ext_min_dpi and ext_max_dpi to configure different dpi settings for ADF/TPU mode vs. normal (flatbed) mode. Normally there are no scanners with ADF and TPU on one device, so this can be handled with the same parameters. Following scanners are affected: Canon PIXMA MG8100 Canon PIXMA MG8200 Canon PIXMA MP800 Canon PIXMA MP800R Canon PIXMA MP810 Canon PIXMA MP830 Canon PIXMA MP960 Canon PIXMA MP970 Canon PIXMA MP980 Series Canon PIXMA MP990 Series Canoscan 8800F Canoscan 9000F This is available in git now or in the next daily git snapshot. Cheers, Rolf
[sane-devel] How to submit new scanner backend code
Hello Bruce, Am 21.01.2012 18:43, schrieb Bruce Karsh: Then we should name this scanner as it is: MX882. Please try the attached patch. Yes, it works Due to an open bug (#313452) I changed the scanner name to Canon PIXMA MX880 Series. There is a reference to the MX882 and MX885 scanners in the man page: PIXMA MX880 Series, MX882, MX885. The new code is available in git now. Cheers, Rolf
[sane-devel] How to submit new scanner backend code
Hi Bruce, Am 21.01.2012 16:11, schrieb Bruce Karsh: Thanks for adding this printer. I tried it and it works. I have a couple of comments about the doc. 1. Canon sells this device as the Canon 882, but it reports itself as an 880. (880 probably refers to a family of simialr printer models, not a specific model). Someone who just bought one wouldn't necessarily know that. So is there a way for the docs to also mention 882? Then we should name this scanner as it is: MX882. Please try the attached patch. If everything works, I also can change the doc files and commit this change to git. 2. In pixma.desc it says ADF empty buggy. For the record, I can confirm that it is still buggy. I tried scanning using the ADF with the ADF empty and xsane threw up error dialogs. Adding documents didn't help. Turning the printer off then on didn't help. When I restarted xsane, it could no longer contact the printer. What worked was to unplug the printer, plug it back in, then start xsane. I ran strace to try to diagnose the problem. Strace showed that xsane could not connect to port 8612 on the printer. I'm guessing that this is the same bug as in PIXMA_870, not something newly introduced. Please report this to the bug tracker. Cheers, Rolf -- next part -- A non-text attachment was scrubbed... Name: pixma_mp150.c.diff Type: text/x-patch Size: 1182 bytes Desc: not available URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20120121/28e734ad/attachment.bin
[sane-devel] Support for CanoScan 9000F and others: 48 bit support for flatbed mode
Hello, I would like to add 48 bits support for flatbed color scans to the pixma_mp810 sub-driver. This can be controlled by the capability PIXMA_CAP_48BIT. Does it mean that the scanner will always scan color images with 48 bits? Is there any parameter available to select 24 bits or 48 bits images from a front end or the command line? Cheers, Rolf
[sane-devel] Support for CanoScan 9000F and others: splitting pixma_mp150.c into two drivers
Hi Gernot, On Mon, Dec 19, 2011 at 12:52:00AM +0900, Gernot Hassenpflug wrote: More updates: Compiled latest SANE from git successfully and tested MP810 as example device. Worked fine at 4800 dpi in TPU mode. I am attaching the diffs (diff -u current git file modified file ) for all the files that were modified to create and support the new sub-driver, which I call pixma_mp810.c after the lowest-named device it supports. The attached file is a RARed file which expands into a sub-directory named sub-driver-pixma_mp810. It an be un-compressed using: unrar x pixma_mp810.rar The new or modified files are (all in /backend sub-directory): Makefile.am pixma_rename.h pixma_common.c pixma.h pixma.c pixma_mp150.c pixma_mp810.c More below. In flatbed mode CS9000F does not support 9600 dpi. I added a patch similar to readjusting the lowest resolution (150 dpi or 300 dpi) in TPU mode. Maybe you need to change the patch if other scanners support 9600 dpi in flatbed mode. I found no other functional differences comparing pixma_mp810.c with the latest patched pixma_150.c Many thanks for your excellent job! Rgds, Rolf -- next part -- A non-text attachment was scrubbed... Name: pixma_mp810.c.diff Type: text/x-patch Size: 821 bytes Desc: not available URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20111227/78e1e348/attachment.bin
[sane-devel] SANE and VirtualBox 4.0
Hi, I am using SANE 1.0.22 with the PIXMA subdriver on my Ubuntu 10.04.1 LTS host. My USB scanner works fine. After upgrading VirtualBox 3.2 to 4.0, I need root privileges to use my scanner. Does somebody has an idea how to solve this? Many thanks in advance. Rolf
[Bug 459639] Re: X server starts randomly in failsafe when starting from cold boot
While analysing this problem dont't forget that vga16 and nvidia (and other graphic drivers) are sharing the same primary frame buffer device /dev/fb0 (https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/459639/comments/52). Vga16 is the first available graphics driver at boot time, and will be replaced by other graphic drivers later on. In kdm.conf the watched event graphics-device-added fb0 PRIMARY_DEVICE_FOR_DISPLAY=1 isn't secure if a 2nd graphics driver is used. To fix this, a new event should be emitted from all graphics drivers or from upstart or from udev or ... as start condition for kdm.conf. And upstart must know if there is any other graphics installed beside vga16 (ok, typically on every home and business pc, but what's about small systems and servers). -- X server starts randomly in failsafe when starting from cold boot https://bugs.launchpad.net/bugs/459639 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 585930] Re: kdm starts before nvidia driver is fully loaded
This is a duplicate of bug #459639. Robert, your comment #9 shows the main problem. vga16 and nvidia use the same frame buffer device /dev/fb0 during boot up (see: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/459639/comments/52). With this the start conditions in kdm.conf for the graphics device doesn't work if nvidia kernel driver isn't loaded or is still loading. This problem does not only affect nvidia kernel drivers. I think this is an essential problem of startup. -- kdm starts before nvidia driver is fully loaded https://bugs.launchpad.net/bugs/585930 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-workspace in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 578732] Re: boot hangs on splash screen, does not show kdm
It seems that this (https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/459639/comments/53) solved both problems (1) X server starts randomly in failsafe when starting from cold boot and (2) boot hangs on splash screen. -- boot hangs on splash screen, does not show kdm https://bugs.launchpad.net/bugs/578732 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-workspace in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Ubuntu-x-swat] [Bug 459639] Re: [Karmic] X server starts randomly in failsafe when starting from cold boot
I found the reason for this problem. The kernel initialises the framebuffer /dev/fb0 device with the vesa driver (vga16fb) before it starts loading the nvidia driver. You can see this in the attached syslog file. ** Attachment added: syslog http://launchpadlibrarian.net/51976046/syslog -- [Karmic] X server starts randomly in failsafe when starting from cold boot https://bugs.launchpad.net/bugs/459639 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 459639] Re: [Karmic] X server starts randomly in failsafe when starting from cold boot
I patched kdm.conf with a sleep before any other commands will be executed. For debugging kdm.conf wites 2 messages into syslog: start kdm and sleep and resume kdm after sleep. Maybe you need to extend the sleep time, if your graphic card takes more time to load the nvidia driver than mine. I respawn kdm, so I can cancel the message boxes if any error occurs and kdm will start up later. This is only a workaround! Does anybody has an idea how to recognise a ready loaded graphics driver from the kernel? Looking for /dev/fb0 is not safe for every hardware configuration. A solution should work with any free and proprietary graphics driver. ** Patch added: kdm.patch http://launchpadlibrarian.net/51976665/kdm.patch -- [Karmic] X server starts randomly in failsafe when starting from cold boot https://bugs.launchpad.net/bugs/459639 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 459639] Re: [Karmic] X server starts randomly in failsafe when starting from cold boot
Here is a syslog file with the debug messages from kdm. It shows that kdm starts before the nvidia drivers are loaded and the sleeping time before kdm resumes. ** Attachment added: syslog_with_patch http://launchpadlibrarian.net/51977120/syslog_with_patch -- [Karmic] X server starts randomly in failsafe when starting from cold boot https://bugs.launchpad.net/bugs/459639 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Bug 459639] Re: [Karmic] X server starts randomly in failsafe when starting from cold boot
I found the reason for this problem. The kernel initialises the framebuffer /dev/fb0 device with the vesa driver (vga16fb) before it starts loading the nvidia driver. You can see this in the attached syslog file. ** Attachment added: syslog http://launchpadlibrarian.net/51976046/syslog -- [Karmic] X server starts randomly in failsafe when starting from cold boot https://bugs.launchpad.net/bugs/459639 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 459639] Re: [Karmic] X server starts randomly in failsafe when starting from cold boot
I patched kdm.conf with a sleep before any other commands will be executed. For debugging kdm.conf wites 2 messages into syslog: start kdm and sleep and resume kdm after sleep. Maybe you need to extend the sleep time, if your graphic card takes more time to load the nvidia driver than mine. I respawn kdm, so I can cancel the message boxes if any error occurs and kdm will start up later. This is only a workaround! Does anybody has an idea how to recognise a ready loaded graphics driver from the kernel? Looking for /dev/fb0 is not safe for every hardware configuration. A solution should work with any free and proprietary graphics driver. ** Patch added: kdm.patch http://launchpadlibrarian.net/51976665/kdm.patch -- [Karmic] X server starts randomly in failsafe when starting from cold boot https://bugs.launchpad.net/bugs/459639 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 459639] Re: [Karmic] X server starts randomly in failsafe when starting from cold boot
Here is a syslog file with the debug messages from kdm. It shows that kdm starts before the nvidia drivers are loaded and the sleeping time before kdm resumes. ** Attachment added: syslog_with_patch http://launchpadlibrarian.net/51977120/syslog_with_patch -- [Karmic] X server starts randomly in failsafe when starting from cold boot https://bugs.launchpad.net/bugs/459639 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 538524] Re: boot hangs on splash screen, doesn't switch to KDM
Addendum to my last comment. It seems that this problem occurs: - only at a cold boot. - never at a warm boot (reboot). - only with proprietray NVIDIA graphics driver (never with nouveau). -- boot hangs on splash screen, doesn't switch to KDM https://bugs.launchpad.net/bugs/538524 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 538524] Re: boot hangs on splash screen, doesn't switch to KDM
Addendum to my last comment. It seems that this problem occurs: - only at a cold boot. - never at a warm boot (reboot). - only with proprietray NVIDIA graphics driver (never with nouveau). -- boot hangs on splash screen, doesn't switch to KDM https://bugs.launchpad.net/bugs/538524 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-workspace in ubuntu. -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 538524] Re: boot hangs on splash screen, doesn't switch to KDM
This is also not fixed for me. I have the same symptoms as Alvin described. I'm using a fresh installed Kubuntu with the latest upgrades. X server runs with NVIDIA driver. -- boot hangs on splash screen, doesn't switch to KDM https://bugs.launchpad.net/bugs/538524 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 538524] Re: boot hangs on splash screen, doesn't switch to KDM
This is also not fixed for me. I have the same symptoms as Alvin described. I'm using a fresh installed Kubuntu with the latest upgrades. X server runs with NVIDIA driver. -- boot hangs on splash screen, doesn't switch to KDM https://bugs.launchpad.net/bugs/538524 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-workspace in ubuntu. -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 527401] Re: grub-installer fails to install on a raid1 array
I just installed Lucid Beta2 Server with separated Raid1 for /boot. Grub has been installed on both hard disks. While creating the md devices, the newly added superblocks are available as free raid devices. To avoid faulty configurations please hide them. -- grub-installer fails to install on a raid1 array https://bugs.launchpad.net/bugs/527401 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
