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
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
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
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
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,
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
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
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
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
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
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
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
--
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
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
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
--
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
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
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
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 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
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
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
501 - 522 of 522 matches
Mail list logo
