Woodsman

I tried that. This is strange. Kubuntu recognized the port and so did SW 12.1. I have to believe that it is something indigenous to this latest release...

Could you please actually show us the output of lsmod as allend asked?
Actually,
would be better.

Also, have you checked your logs? Please show us anything you think is relevant (ie. any errors or warnings) in

• dmesg
• /var/log/syslog
• /var/log/messages
• /var/log/cups/*

What kernel are you using?

shadow

Allend did not ask FOR the output of any command. He asked WHAT the output was--indicating to me that I was to take his advice and see what the results were and proceed from there.

I am using the vanilla/generic kernel that PatV supplied--2.26.27.7-smp. I appreciate the help but the questions seem to be trying to put the issue down to me when I haven't done anything different with this install than with SW 10.2, 11, 12, 12.1...I know it's hard to admit but this may be a bug in our beloved Slackware...

Whenever a new Slackware version is released people are *very* quick to dismiss their problem as a bug instead of a configuration error. And, although it *may* be a bug, there is a very good chance that is is not. Please try to work WITH the people trying to help you instead of insisting it is a bug. What is the output of `id -rnG` as your normal user? Also, I would not attempt to use KDE's setup tools to set up your printer. I usually use http://localhost:631 to setup my printers as well.

Also, you could actually post the output of the commands, as shadowsnipes stated.
Uh...he is asking what the output is, implying that you should post it. We can't help you if you think you know everything -- you may not (I know I sure don't). You may be missing something obvious -- or something hidden. Many eyes are always better than one. Please post the ouput instead of complaining that you were not asked to. Now two people have asked for the ouput and it still is not posted.

[edit]Even if it *is* a bug, do you actually want to get it to work so a patch could be released? Without actually getting it to work, NO ONE will know what's wrong (unless someone has a suspiscion about what the problem may be). Again -- please work WITH people trying to help you, not against them.[/edit]

I posted because of a problem that is apparent in Slackware 12.2. After reading T3Slider's post, let's just consider the matter closed. I think this thread is headed in the wrong direction.

I'll take what I did get by way of replies and see if I can resolve the issue myself. I do not want to get into any strife nor waste my time.

Thanks for the help guys and happy holidays...

Obviously the direction of actually SOLVING your problem instead of complaining about it is the wrong direction. Don't mind me, I'm just a sarcastic guy with a dry sense of humour. I'm not trying to offend you. However, you *still* haven't posted any actual output. If you want your problem solved, *PLEASE* post some output. No one is going to be rude if you cooperate. I hate unresolved threads, so I really would like to help -- if I can (and I'm sure others feel the same way).

"I hate unresolved threads, so I really would like to help -- if I can (and I'm sure others feel the same way)"

The issue has been resolved and this matter--as well as the thread--is closed.

Happy Holidays.

I am not assuming anything. We can't really say something is a bug until other people have confirmed it to be so, and we cannot say it is a configuration issue unless someone solves it by changing the configuration. Either way, questions have to be asked and answered to be able to determine anything. The fact that you have not done anything different for your various Slackware installs is irrelevant. In reality, you must do something slightly different for each new version which is why Robby compiles the nice CHANGES_AND_HINTS.TXT.

Do you have this problem if you use the huge-smp kernel? What about the Slackware 12.1 kernels (they do work still)?

How was the issue resolved? If you figured out the answer to the problem please post the answer so that other people can potentially learn from your experience.

As I have said before, nobody has yet confirmed the issue to be a bug or a configuration issue. I don't have a parallel port printer to test myself (sorry).

For completeness of information, the solution to this issue can be found here:

http://www.linuxquestions.org/questi...01#post3376901