Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 189803
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo's Team for Core System packages <base-system@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Mario Hein <mhein02@gmx.de>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
libieee1284-0.2.11.ebuild libieee1284-0.2.11.ebuild text/plain Simone Scanzoni 2007-10-11 23:52 0000 518 bytes Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 189803 depends on: Show dependency tree
Bug 189803 blocks: 176188
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2007-08-22 08:40 0000
My old parallel port scanner stopped working since kernel 2.6.21. This seems to
happen due to a bug in libieee1284 or the kernel itself. The connection to the
scanner can't be established anymore. This happens with every kernel >= 2.6.21
and every libieee1284 version in the portage tree.
I 've found a site where the problem is discussed, but no solution has been
found for this.

Here is the link:
http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg177585.html

Reproducible: Always

------- Comment #1 From SpanKY 2007-08-22 22:59:41 0000 -------
so narrow it down between it being a userspace API breakage from kernel headers
or the kernel being broken

boot a 2.6.20 kernel and install 2.6.20 headers and rebuild libieee1284 and see
if it works

if that does, upgrade your kernel only and see if libieee1284 still works

------- Comment #2 From Mario Hein 2007-08-23 13:21:04 0000 -------
So...i followed your instructions and here are the results:
(i used libieee1284 in the unstable version 0.2.10 because it's the most recent
version in portage)

gentoo-sources-2.6.20-r8
linux-headers-2.6.17-r2
libieee1284-0.2.10
--> scanner works

gentoo-sources-2.6.21-r4
linux-headers-2.6.17-r2
libieee1284-0.2.10
-->scanner doesn't work

seems that changes have been made to the kernel

------- Comment #3 From SpanKY 2007-08-23 18:07:35 0000 -------
great ... for posterity sake, could you also test:
gentoo-sources-2.6.20-r8
linux-headers-2.6.21+
libieee1284-0.2.10

------- Comment #4 From Mario Hein 2007-08-23 20:18:24 0000 -------
OK... here the results for:
gentoo-sources-2.6.20-r8
linux-headers-2.6.21
libieee1284-0.2.10

functional ;)

------- Comment #5 From Carlos Silva (RETIRED) 2007-08-29 15:50:36 0000 -------
ok... after investigating this problem, i found out that since kernel 2.6.21
the sysctl interface in procfs (/proc/sys/) had some changes in it. One of them
was the hardlink count of dirs and files. From .21 onwards, all dirs under
/proc/sys will have hardlink count = 0 and all files = 1. So, this means that
libieee1284 should be fixed because i tests this values.
The patch to libieee1284 can be found in here:
http://sourceforge.net/tracker/index.php?func=detail&aid=1739643&group_id=29314&atid=395778

------- Comment #6 From Carlos Silva (RETIRED) 2007-08-29 22:56:38 0000 -------
just to clear things up, this is the original patch that makes this behavior
"normal" aka "the expected behavior from kernel":
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=77b14db502cb85a031fe8fde6c85d52f3e0acb63
(see function proc_sys_refresh_inode)

------- Comment #7 From Simone Scanzoni 2007-10-11 23:52:05 0000 -------
Created an attachment (id=133223) [details]
libieee1284-0.2.11.ebuild

Problem solved with version 0.2.11, found on the SourceForge site.

------- Comment #8 From SpanKY 2007-10-12 14:54:08 0000 -------
added to the tree ... do not post ebuilds as attachments if you didnt change
anything, just say "renaming the old ebuild worked for the new version"

Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug