On Fri, 12 Nov 2010 05:29:44 -0500 (EST), Rodolfo Medina wrote: > Stephen Powell <zlinux...@wowway.com> writes: >> So the warning message disappears. Good. But what about the virtual console >> characters? Are the characters still smaller than they were before? What >> about the other "strange things"? Are they still strange? In other words, >> is the failure of the printer to work the only symptom of moving >> /etc/modprobe.conf to the /etc/modprobe.d directory and naming it >> parport.conf? Does everything else in your system behave the way it did >> before you installed the printer driver? Or is something else different? > > After moving /etc/modprobe.conf to the /etc/modprobe.d directory and naming it > parport.conf and rebooting, apparently everything else in my system behaves > the > way it did before I installed the printer driver. The only problem is that > the > printer doesn't work. If I want it to work, I have to leave > /etc/modprobe.conf > there where Samsung put it.
OK, good. The rest of your system is working as before. That's what I wanted to know. Now look for evidence that the parport_pc module is getting the options passed to it in the options statement in /etc/modprobe.d/parport.conf. For example: dmesg|grep parport You should see a message that identifies the I/O port address, the interrupt level (IRQ) and the DMA channel that was specified in /etc/modprobe.d/parport.conf. If you do, then it is safe to assume that the correct options are being passed to the kernel module. And that, after all, is the intended purpose of /etc/modprobe.d/parport.conf. If the correct options are being passed to kernel module parport_pc, then the problem must be that something in the printer driver, perhaps a boot-up script, perhaps not, is explicitly looking for /etc/modprobe.conf and trying to parse its data. If that is the case, you may be able to find the script and edit it to look in /etc/modprobe.d/parport.conf instead. If the logic is in a compiled program, and the manufacturer does not provide source code for their driver, then you are pretty much out of luck. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/786888053.333064.1289573295382.javamail.r...@md01.wow.synacor.com
