SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I was setting up alsa on my slak 10.2 kernel 2.4.31 box and during alsaconf the system froze, no keyboard no nothing. It was in the middle of oss set up. So, I rebooted and now neither root nor user can finish KDE 3.4 start up. It makes it to loading the window manager and freezes. I can't remember the command to ,pardon syntax here, re make kde environment. I know you can, or could, in the Gnome environment. I can access the command line b/c I don't boot to kdm. Can someone plz point me in the right direction.
It sounds to me like you "may" have an IRQ device resource conflict.
The alsaconf tool when it probes your hardware, will try all IRQ and DMA settings for whatever "module" it believe's it should try for your hardware. The "module" being a driver.
What I propose you do is give us the printout of "lspci" and paste it here.
In addition, I think you should pull out any "un-necessary" PCI cards that you may have. For example if you do not need a modem, the pull it out. You may also have to move the sound card to a different slot. You didnt specify if you have a laptop or desktop.
Lastly, check in the bios of your pc and check to see if there are any settings for the sound card there. Sometimes, in the bios there is a button to reset the bios to defaults for the sound card. I've found that for example windows, since it is a plug and play OS can change the settings to work the pc better but they may not be so good for you in linux. Resetting the bios may help.
Well hope this gives you some idea where to start.
Also, you can turn stop alsa from starting with your pc by making /etc/rc.d/rc.alsa not executable on startup so you can get into a gui if need be.
Also if you run 'xwmconfig' you can select fluxbox to run as your default window manager for the time being to get things cleared up.
Oh yea, you do have the isapnp tools installed correct?
Thanks for your quick reply. I'm using fluxbox now to get you the info you requested. I don't have any pci cards. Everything is onboard and is either SiS or Realtek.
00:00.0 Host bridge: Silicon Integrated Systems [SiS] 651 Host (rev 02)
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] Virtual PCI-to-PCI bridge (AGP)
00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS85C503/5513 (LPC Bridge) (rev 25)
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE]
00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] Sound Controller (rev a0)
00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f)
00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f)
00:03.2 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller
00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 91)
01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 65x/M650/740 PCI/AGP VGA Display Adapter
I've changed rc.alsa so that it's not executable on startup. I will check now to see if that was the conflict. c ya in a minute.
After rebooting KDE still won't start up, it's still hanging up at 'loading the window manager'. I didn't like flux or blackbox to much but xfce wasn't to bad. That's just my personal opinion and everyone has different tastes. If there is any other nfo I can provide you with let me know.
What causes dma to be turned off and what makes a file system unclean?? Both of these are coming up during boot. I didn't have this problem when this hd was in other pc, but since the switch to the faster pc (from p3 pc to 1.8ghz pc) it continues to come up. It specifically says dma is turned off on the hd and I didn't turn it off.
yea I was just mentioning that to you so you could use your computer still, while the solution for your issue is worked out.
just so you know you can run "fluxbox-generate_menu" and it will work up a menu for you that includes all the programs on your computer.
what makes a file system unclean??
I venture to guess that you hit the reset key to reboot your pc when it froze? Not properly rebooting will do that.
You can schedule a diskcheck on the hard drive with the "shutdown" command. Check the manpage it will tell you how to schedule the disk check on next reboot. use "man shutdown" and you'll see it there.
What causes dma to be turned off
try going the the 'dmesg' of the computer. see what it says about your hard drive.
also check the 'man hdparm' that's the utility to tweak the DMA settings and other IO parameter's of the hard drive. some people report that slackware doesnt put it on there correctly for them and that it was supposed to.
"hdparm -i /dev/hda" shows info for the drive /dev/hda for example
and this one helps"
"hdparm /dev/hda" also
I wonder if you might not be better to install the 2.6 kernel that slackware 10.2 ships in /testing to address your issues for the sound, and quite possibly your hard drive.
At this link here you can see that Mr. Pat V also includes some new alsa driver's as well in addition to the new kernel.
Thanks for your help Old_Fogie. You were correct about the reset button. The file system showed up clean when I booted up. I will use the man hdparm to turn dma on because hdparm /dev/hda* showed that dma was off. As far as alsa goes, it worked fine with the other hd I had in this machine b4 the swap. Not sure why there's a problem now.
KDE is still not functioning correctly. It hangs up at the same spot even w/ alsa stopped. Any suggestions would be greatly appreciated.
yes, you can try removing .kde, and clean out /tmp as well
also, if you are starting X from a console (ie, by typing "startx") there should be some error messages on that console when kde bombs out, make sure to search for solutions by searching for those exact error messages
another thing you could try as a last resort, if all else fails, is reinstalling kde (NOT the whole distro!), even though its unlikely the problem, you may have installed some corrupt/incomplete packages - you can grab them at slackware.com, then remove all existing kde packages by running "pkgtool" (as root) and install the new ones. be careful with the version you pick if you do that, try reinstalling the version you have installed now, so as not to run into dependency problems (by using the latest current version with a stock 10.2 install, for example).
Thanks for your help guys.
I tried the mv command and then restarted kde but didn't work. I loaded up bare Slack (vmlinuz) and everything work fine, so I removed the alsadriver(1.0.9) pkg's I loaded w/ pkgtool. working again. I did rm -rf .kde and mv .kde_old .kde then tried starting kde and voila... Only one prob I see is that some icons are now missing from b4 as well as my bookmarks in firefox. Hopefully my bookmarks are in the xfce directory still. I will look and see. I guess I will have to research some more on getting alsa-driver to work correctly and in unison w/ kde. Any clues how would be appreciated.