rimez wrote:
> It seems that quite a few people are having problems with their printers and
> SUSE when using Kernel 2.2.x. I'm one of those people.
> I do have the entries that he speaks of. Am I to chage it?
Did you install 6.X fresh or upgrade ? Which printer package are you
using lprold or lpd? Some folks have problems with lpd. You may have
better luck with lprold. I use lpd with no problems.
>
> >Which kernel do you use? printing as a module? With 2.2.x there are a
> >few entries in conf.modules to make the damm thing work. (if modules)
> >Took me some time to:
>
> ># post-install paride insmod frpw
> ># pre-remove paride rmmod frpw
> >alias parport_lowlevel parport_pc
> >options parport_pc io=0x378
>
> When I check the status of my printer it keeps telling me that it's idle or
> that it's offline? It doesn't matter if I am root or not... the results are
> always the same.
lpc up <printer name> will bring it online for you. Something I did was
change my printer from polling to interrupt driven by adding an irq=7
parameter in /etc/conf.modules to my parport_pc options line, and adding
this to my /etc/rc.d/boot.local file: /usr/bin/tunelp /dev/lp0 -i 7. I
have the same printer as you so this should work for you.
> Another question.... I was having problems with rc.d when I first upgraded to
> 6.0. I kept getting a screenful of errorson boot up about modprobe not being
> able to find certain modules... kinda like this:
> modprobe: can't locate module blah blah blah
> modprobe: can't locate module blah blah blah
> modprobe: can't locate module blah blah blah
> I have since fixed this using a hack from C Johnson (the serial hack).
> I want to know if this has been (or will be) fixed in 6.1?
Sounds like you conf.modules doesn't have the correct aliases more than
anything else, besides ppp compression, I haven't really had modprobe
errors out of SuSE 6.0. Well I lie there is one other one:
block-major-8 (sd_mod). Clues anyone? I have been to lazy to search
the source for it!
> Oh yeah.. one last question. Does anyone know what it means when I keep getting
> DMA messages in /var /log/messages like this:
> Apr 18 13:21:01 rimez kernel: es1371: dma timed out??
> Apr 18 13:25:33 rimez kernel: es1371: dma timed out??
> I don't understand... everyting seems to be working OK.
> TIA,
> rimez
sounds like you don't have the card setup right with isapnp or
conf.modules . That usually happens when you aren't using the same dma
with isapnp and the module, or the dma is conflicting with another
device trying to use it so the es1371 module can't initialize it. Hope
I have been helpful.
--
Aduanne Carter
[EMAIL PROTECTED] / [EMAIL PROTECTED]
--
To get out of this list, please send email to [EMAIL PROTECTED] with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
archive at http://www.suse.com/Mailinglists/suse-linux-e/index.html
