SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I compiled and installed the new kernel (2.6.5) or whatever its name is.
anyways, when I boot up, I can't see anything, so I sit waiting 'til I see the IDE lights stop glowing, and I write my acc and pass. then "startx" and I can see. but why can't I see shit during bootup? I "think" I configured it correctly. and it's always worked with former kernels...
question nr 2:
Even thought I load the module and such in the new kernel, I can't get alsa working. (works in former kernel)
question nr 3:
I need to make my ntfs partition writeable. But even thought I enable write support in NTFS in the kernel configuration, it won't work. why!?!??!
1) look at the framebuffer configuration in the kernel setup.
3) write support for NTFS is not well-supported in Linux. It can write, but it will be easy to mess things up. So for your own good, it is not easy to enable the buggy write support. It is meant to be read-only. If you must write to the partition, there is something called 'captive-ntfs'.
Make sure you chose the right thing. And, try different 'vga=' boot options. Try 'vga=ask', then enter one of the numbers listed for different resolutions.
the weird thing is, I didn't modify Lilo. lilo's the same settings now as be4, which worked! but hey, I'll try that. screen's like... comepletely black :S
I had the same problem, my video card is nvdia geforce 440 mx, I solved it by disable all framebuffer specials features like logo, change resolution..., just enable vga.
And in your lilo config, comment the line with vga settings.
Ok, I fixed everything 'but the sound now. It says "snd_mixer_oss" or some BS like that doesn't exist. (module). wtf? why's that? since I wasn't quite sure, I made every possible sound module!! Why doesn't it exist? and why doesn't my emu10k1 load automatically anymore? gah...
Oh, and my system also got kinda "unstable" and slow after I updated the kernel
Did you enable the hotplug feature in kernel config ? If not (and if you don't want hotplug) try add "modprobe snd-emu10k1" in /etc/rc.local file to automaticly load sound blaster driver at boot.
For my part, I enabled hotplug and now, near all modules (tulip driver, emu10k1, usb mouse...) load during boot (without any rc config).
For sound, disable in Device Drivers > Sound > Open Sound System
Enable instead the ALSA oss emulation (oss mixer api, oss pcm api, optional : oss sequencer api)
After that, enable your audio card driver (you should know if it is a pci card or usb or other, the card id product and manufacturer). Enable all your sounds driver as module if possible.
Reboot, as root do alsaconf to let alsa discover your audio card, do alsamixer to unmute the master audio channel in the mixer, alsactl to store your channels settings.
Maybe you will have to upgrade your alsa pkg. Mines are :
alsa-driver-1.0.4-i486-1
alsa-oss-1.0.4-i486-1
alsa-lib-1.0.4-i486-1
alsa-utils-1.0.4-i486-1
I can't say anything for slowness of your system, maybe a dmesg command or a tail /var/log/messages contains something that may help to point to what may be wrong.
Does the slowness occur just in X environment or in your system in general ?
Seems I am repeating myself over and over with this same issue time and time again... Read HOWTOs saves much headache....
Basicly in a nutshell YOU DO NOT compile your sound card into the kernel if using alsa. Under the sound section you only answer (y) to the first one Enable sound support. all others you may or may not need should be (m) or (n).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.