Ok, here's the deal... I'm a super newb as of one day ago and already coming up with problems that my best bud has never seen in his past 5 years in linux.

I'm using RH7.3 and I have hundreds of questions as would anyone new to linux. But one main concern is that when I'm in the KDE invironment logged in as user (not root) and I hit ctrl+alt+function key like say f1 to get konsole, My keyboard pretty much locks out on me and the screen scrolls "via82cxx warning: SG stopped or paused" over and over and over
if i ctrl alt del a few times it will reboot, but that's all that I can do when this happens...

what do you suppose could be causing this error or any possible solutions. If i ctrl+alt+f logged in as root, everything works fine, I can toggle between GUI/Text...

Any feedback would be appreciated no matter how small, I'm eager to learn as much as I can about Linux.
Thanks


Edit #1: Sorry, disreguard what I said about loggin in as root... when I logged in as root it was under the Gnome interface. I just logged in as root in KDE and same exact problem when i toggle to console. So the problem seems to reside in KDE itself. Gnome works well, and everything seems to run smooth aside from this scrolling madness in KDE. UGH =/

All I can tell you is that the warning refers to the via chipset on your motherboard.Kinda strange.It only does this in kde?
lynch

Ok, I have narrowed it down to the problem, but now for a solution. Possibly someone out there has heard of this before. I was running RH7.3 which I would still like to. Anywho, I have an Epox 8K3A+ mainboard and it has onboard 5.1 surround audio. I disabled the audio via bios and the problem went away. My RH7.3 distro comes with the new KDE 3 I believe so I installed Mandrake.... ummmmm.... 8.2 and that has an older version of KDE. To sum it up, Gnome doesn't have a problem in either Linux distros, and the older version of KDE runs fine. The problem is with in the new KDE that was released not too long ago.

So basically, if anyone can point me in the direction that I would need to go to fix this audio error I'd greatly appreciate it. This is just my luck though... every time I try something new, I come up with problems no one has ever heard of. hmph