Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
parport scanner: parport0 is not a valid device name SOLVED
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
javeree
Apprentice
Apprentice


Joined: 29 Jan 2006
Posts: 214

PostPosted: Mon Dec 10, 2007 8:46 pm    Post subject: parport scanner: parport0 is not a valid device name SOLVED Reply with quote

I finally managed to get my parallel port scanner to work again with my new kernel, and think it is worth posting the solution here. Maybe it can help someone.

Until kernel 2.6.18, I had a Lifetec 9891 parallel printer (mustek driver mustek_pp) that was working as it should with the help of the guide I found here.

After a switch to kernel 2.6.21 (and a further switch to 2.6.22), my scanner did not work anymore, and was not even detected

with the following in /etc/sane.d/mustek_pp.conf:
Quote:
scanner "LT9891" parport0 cis1200

the result of SANE_DEBUG_SANEI_PA4S2=128 scanimage -L
was
Quote:
[sanei_debug] Setting debug level of sanei_pa4s2 to 128.
[sanei_pa4s2] sanei_pa4s2: interface called for the first time
[sanei_pa4s2] sanei_pa4s2_open: called for device 'parport0'
[sanei_pa4s2] sanei_pa4s2_open: trying to connect to port
[sanei_pa4s2] pa4s2_open: trying to attach dev `parport0`
[sanei_pa4s2] pa4s2_init: static int first_time = 1
[sanei_pa4s2] pa4s2_init: called for the first time
[sanei_pa4s2] pa4s2_init: initializing libieee1284
[sanei_pa4s2] pa4s2_init: 3 ports reported by IEEE 1284 library
[sanei_pa4s2] pa4s2_init: port 0 is `0x278`
[sanei_pa4s2] pa4s2_init: port 1 is `0x378`
[sanei_pa4s2] pa4s2_init: port 2 is `0x3bc`
[sanei_pa4s2] pa4s2_init: allocating port list
[sanei_pa4s2] pa4s2_init: initialized successfully
[sanei_pa4s2] pa4s2_open: looking up port in list
[sanei_pa4s2] pa4s2_open: `parport0` is not a valid device name
[sanei_pa4s2] pa4s2_open: returning SANE_STATUS_INVAL
[sanei_pa4s2] sanei_pa4s2_open: connection failed


toavoid using parport0 explicitly, I changed /etc/sane.d/mustek_pp.conf to:
Quote:
scanner "LT9891" 0x378 cis1200

the result of SANE_DEBUG_SANEI_PA4S2=128 scanimage -L
was (only the relevant part)
Quote:
[sanei_pa4s2] pa4s2_init: 3 ports reported by IEEE 1284 library
[sanei_pa4s2] pa4s2_init: port 0 is `0x278`
[sanei_pa4s2] pa4s2_init: port 1 is `0x378`
[sanei_pa4s2] pa4s2_init: port 2 is `0x3bc`
[sanei_pa4s2] pa4s2_init: allocating port list
[sanei_pa4s2] pa4s2_init: initialized successfully
[sanei_pa4s2] pa4s2_open: looking up port in list
[sanei_pa4s2] pa4s2_open: port is in list at port[1]
[sanei_pa4s2] pa4s2_open: setting up port data
[sanei_pa4s2] pa4s2_open: name=0x378 in_use=SANE_TRUE
[sanei_pa4s2] pa4s2_open: enabled=SANE_FALSE mode=PA4S2_MODE_NIB
[sanei_pa4s2] pa4s2_open: opening device
[sanei_pa4s2] pa4s2_open: device `0x378` opened...
[sanei_pa4s2] pa4s2_open: returning SANE_STATUS_GOOD
[sanei_pa4s2] pa4s2_open: open dev `0x378` as fd 1
[sanei_pa4s2] sanei_pa4s2_open: connected to device using fd 1
[sanei_pa4s2] sanei_pa4s2_open: checking for scanner
[sanei_pa4s2] sanei_pa4s2_enable: called for fd 1 with value 1
[sanei_pa4s2] sanei_pa4s2_enable: enable port '0x378'
[sanei_pa4s2] pa4s2_enable: failed to claim the port (Error interfacing system)
[sanei_pa4s2] sanei_pa4s2_enable: failed to enable port
[sanei_pa4s2] sanei_pa4s2_enable: returning SANE_STATUS_IO_ERROR


I finally found a hint somewhere that there might be a problem with the kernel versions as of 2.6.21 concerning ppdev and the ieee1284 library. I also found there the suggestion that solved it all:

Code:

echo disallow method ppdev > /etc/ieee1284.conf


now resulted in scanimage -L
Quote:
device `mustek_pp:LT9891' is a Mustek 1200CP flatbed scanner


problem solved ! I hope this can
Back to top
View user's profile Send private message
javeree_work
Tux's lil' helper
Tux's lil' helper


Joined: 13 Apr 2005
Posts: 84

PostPosted: Tue Dec 11, 2007 8:51 am    Post subject: Reply with quote

And now that I know it is related to libieee1284, checking on gentoo bugzilla resulted in finding this bug report.

=> Upgrading to libieee1284-0.2.11.ebuild should help

I am going to try that this evening
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum