linux-kernel - Re: Parallel Driver(s) Broke in 2.6.31

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 16 Nov 2009 09:26:36 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Steve Meisner <smeisner@...rter.net>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Parallel Driver(s) Broke in 2.6.31

On Sun, 15 Nov 2009 21:54:47 -0500
Steve Meisner <smeisner@...rter.net> wrote:

> I posted to the Mandriva forum with no luck yet.  I recently upgraded to 
> Mandriva 2010.0 and in doing so lost ability to use my parallel printer.  
> After many hours of debugging effort and finding nothing in logs or 
> hardware/driver error messages, I went on a hunch that it could be related to 
> the kernel.  So I rolled back to the 2009.1 kernel 2.6.29 and printing 
> returned.  I don't know how to proceed with determining the root cause as I 
> cannot find any error in the logs or differences in hardware detection and 
> module loading.  I don't even know the hierarchy of the modules involved 
> (parport, parport, pc, lp, and ppdev).   Should I start diffing those modules 
> and see if I get lucky applying hacking 101 techniques?  Please CC me 
> (smeisner@...rter.net) if you have any suggestions (except for buying a new 
> printer).

Start by looking at the boot messages from each ("dmesg" as a command
will show you them after boot).

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/