Can't get sound/printer working

vbguru12000 · 01-17-2005, 11:50 AM

Once again, I'm pretty new to Debian, and Linux alike so bare with me. I just installed Debian yesterday and am having a few problems.

1) My sound doesn't work. Besides checking the obvious like making sure the speakers are plugged in and turned on, I don't really know what to do.

2) I can't add my printer (Lexmark X75). When I go through all the steps, I get near the end and it asks for a login and password, no matter what I type, it says invalid. I've tried both my login, and root. I'm pretty confused as what to do next on this one too.

Any help would be greatly appreciated.

bobbens · 01-17-2005, 12:16 PM

ok ill work on your sound (because my printer is screwed up... somehow cupsys keeps on loading in parport0 mode and that's not cool). First of all i'd get alsa, do apt-get install alsa-base . Then once installed run alsaconf as root in the console, it'll ask which module you want for you graphic card, you choose it and then if it gives no errors it'll say you're ready to have sound. So then you run alsamixer and raise the volumne to the level you want. If all goes well you'll have sound and it'll work perfectly. If you are using an nforce2 chipset like me, after doing that download the official driver package from nvidia.com and run it with sh <package name> and it'll be all set.

Printer, i'd go with cupsys, download cupsys and the gimpprint drivers. Just run aptitude or synaptic and search for cupsys and gimpprint and get that. Then once it's installed and the cupsys daemon is working type: http://localhost:631/ in your browser using root password and username root. From there on just follow the big buttons to do whatever you want. And then technically after adding a printer you should be able to test it and it will print (worked for me, but when i update it got fucked up and haven't fixed it yet.

Well these are the basics, i hope they help somewhat, good luck.

EDIT: oh btw it seems like you are using the kprint dialog to install the printer, that is bad news, use the advice i gave you above. Good luck.

vbguru12000 · 01-17-2005, 12:35 PM

Quote:

Originally posted by bobbens
ok ill work on your sound (because my printer is screwed up... somehow cupsys keeps on loading in parport0 mode and that's not cool). First of all i'd get alsa, do apt-get install alsa-base . Then once installed run alsaconf as root in the console, it'll ask which module you want for you graphic card, you choose it and then if it gives no errors it'll say you're ready to have sound. So then you run alsamixer and raise the volumne to the level you want. If all goes well you'll have sound and it'll work perfectly. If you are using an nforce2 chipset like me, after doing that download the official driver package from nvidia.com and run it with sh <package name> and it'll be all set.

Printer, i'd go with cupsys, download cupsys and the gimpprint drivers. Just run aptitude or synaptic and search for cupsys and gimpprint and get that. Then once it's installed and the cupsys daemon is working type: http://localhost:631/ in your browser using root password and username root. From there on just follow the big buttons to do whatever you want. And then technically after adding a printer you should be able to test it and it will print (worked for me, but when i update it got fucked up and haven't fixed it yet.

Well these are the basics, i hope they help somewhat, good luck.

EDIT: oh btw it seems like you are using the kprint dialog to install the printer, that is bad news, use the advice i gave you above. Good luck.

When I run alsaconf, it says it can't find a supported PnP or PCI card. It asks, "Would you like to probe legacy ISA sound cards/chips?" which I answer yes to. It then outputs:

Code:

modinfo: snd-opl3sa2: no module by that name found
modinfo: snd-cs4236: no module by that name found
modinfo: snd-cs4232: no module by that name found
modinfo: snd-cs4231: no module by that name found
modinfo: snd-es18xx: no module by that name found
modinfo: snd-es1688: no module by that name found
modinfo: snd-sb16: no module by that name found
modinfo: snd-sb8: no module by that name found

Then it exits back to the console. Any ideas now?

btw, I have onboard sound.

bobbens · 01-17-2005, 12:57 PM

then this calls for drastic measures, try installing discover (not discover1). It'll remove discover1 if you have it. Then try running alsconf after rebooting. Discover detects hardware and sometimes is able to load modules for it. Or if you want to do it the hardware, knowing your chipset you can go modconf and then search for drivers/sound or something like that and load the module for your chipset, though discover should do this for you. Good luck.

vbguru12000 · 01-17-2005, 01:03 PM

Quote:

Originally posted by bobbens
then this calls for drastic measures, try installing discover (not discover1). It'll remove discover1 if you have it. Then try running alsconf after rebooting. Discover detects hardware and sometimes is able to load modules for it. Or if you want to do it the hardware, knowing your chipset you can go modconf and then search for drivers/sound or something like that and load the module for your chipset, though discover should do this for you. Good luck.

I'm extremely leary(sp?) of installing discover. I had done that yesterday and it locked up my system. After waiting about 30 min, I rebooted and Debian wouldn't boot up anymore. Actually, being stupid me, after reinstalling Debian, I tried to install discover again, with the same result. So yesterday, I had to reinstall Debian 3 times, I'd prefer not to do it again today. lol.

bobbens · 01-17-2005, 01:34 PM

which discover? discover1 or discover. If you got screwed up with discover, then try discover1, otherwise you will have to manually edit it in. Go apt-get install modconf and select the correct module.

vbguru12000 · 01-17-2005, 02:20 PM

How do I know what the correct module is?

bobbens · 01-17-2005, 02:41 PM

you gotta know the chipset is uses. The best way to know that is online, like for example i got a computer that sports a SiS 910 or something like that onboard sound chipset. Try doing a google search for your motherboard or check out the hcl here for your motherboard to see what drivers you should get. I used discover the first time, got it to load modules, then i uninstalled it, once everything was loaded, so it doesn't harass me anymore. If you cant run normal discover try discover1, it's completely different. Discover doesn't work on my computer, while discover1 does.

vbguru12000 · 01-17-2005, 03:57 PM

After doing some research, I think I know what's wrong, but I don't know how to fix it. Apparently, my particular chipset has a conflict with the two modules: via82cxxx and sound. lsmod shows this two modules in use. modconf however shows them as uninstalled ('-' next to them). Do you know how to stop them from loading?

vbguru12000 · 01-17-2005, 05:31 PM

Nm, I figured it out!!! I just upgraded my kernel to 2.6.8 and reran alsaconf. It found my sound device and installed the appropriate modules. So now I have working sound!!! Thank you so much Bobbens for your time, I couldn't have done it without you.

bobbens · 01-18-2005, 01:28 AM

No problem, i'm glad to have been of help.