okay, fixad the thing with the modules but I want the system speaker to work how can i fix this ?
it got to be there somwere in the kernel but I cant find it

salted:
I know for me it was only a matter of adding VESA in the Console drivers. Try that and get back to us. Also, I'm really liking the LQ series kernel. Much smaller than the 2.6.1 (which might not matter much) and as quick as anything else I've used. Had the blank screen on that, went back in and added only VESA - problem solved!

Hope that helps!

I'm having the "Cannot mount root fs" problem. My root partition is ReiserFS and i have it enabled in the config but it still gives me an error. I used the old 2.4.23 configuration (changed the ReiserFS settings ofcource) and still no luck.

I just updated to 2.6.1 on my IBM T40.
everything is up and running but my console resolution is limited to the standard.
lilo.conf:
vga = 790 (which worked on my old kernel)

Why isnt it working? The laptop is running a Mobility Radeon x (forgot exact model number).

Any suggestions? Thanks in advance.

so long
fusion

PS
Excuse my poor english, isn't my mothertounge

Vega: I tried it, but it didn't work. Here's the output of my .config file:

# Graphics support
#
CONFIG_FB=y
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_IMSTT is not set
CONFIG_FB_VGA16=y
CONFIG_FB_VESA=y
CONFIG_VIDEO_SELECT=y
# CONFIG_FB_HGA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I810 is not set
# CONFIG_FB_MATROX is not set
#CONFIG_FB_MATROX_MILLENIUM is not set
CONFIG_FB_MATROX_MYSTIQUE=m
CONFIG_FB_MATROX_G450=m
CONFIG_FB_MATROX_G100=m
CONFIG_FB_MATROX_I2C=m
CONFIG_FB_MATROX_MAVEN=m
CONFIG_FB_MATROX_MULTIHEAD=y
CONFIG_FB_RADEON=m
CONFIG_FB_ATY128=m
CONFIG_FB_ATY=m
CONFIG_FB_ATY_CT=y
CONFIG_FB_ATY_GX=y
# CONFIG_FB_ATY_XL_INIT is not set
# CONFIG_FB_SIS is not set
CONFIG_FB_SIS_300=m
CONFIG_FB_SIS_315=m
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_VIRTUAL=m

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_PCI_CONSOLE=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
#
# Logo configuration
#
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_MONO=y
CONFIG_LOGO_LINUX_VGA16=y
CONFIG_LOGO_LINUX_CLUT224=y
#
Also, my cable doesn't seem to work, but that's the least of my worries right now lol.
Mmm, thanks for your help, if nothing else works then I'll just try to install 2.6.0 instead of 2.6.1. Thanks again.

It's been already quite some time that nice guy Linus told the community not to update the /usr/src/linux symlink, because of headers incompatibility between the new kernel and the binary libraries (mainly Glibc) that were built against the primitive kernel shipped with your distro.

He, three years and half ago, already explained that.
http://seclists.org/linux-kernel/2000/Jul/4404.html

"In short, the _only_ people who should update their /usr/include/linux
tree are the people who actually make library releases and compile their
own glibc", what most people often don't do.

I had recently some problems when upgrading my 2.4.20 slack kernel with the 2.6.0-test11, and I got really confused about it, because Linus is now so upset that his advice has not been taken into account that one can't really find some proper documentation about that.

Eventually I understood that the best way to avoid these quite elusive problems is to keep the old kernel in /usr/src/linux, and never update the symlink. The kernel can be compiled in your ~, and then built as root.

Did someone experience the same problems as I did ?

I really don't see why people are so reluctant to change their minds about that.

Regards,
jdif

salted,
the only difference I saw from mine is that I have CONFIG_FB_VGA16 is not set. I can only suggest trying that change.
What cable isn't working? Hook us up with some details on that and maybe we'll sort it out.

Hy ...I'm new here ...

I have a big problem ... maybe it's big just for me.

It's the first time I wanted to install SlackWare ....
Until now as Linux I understood RH ... the last version used was 8.0

I have a new hardware and wanted to install SlackWare 9.1 but I have a S-ATA HDD, which isn't detected by the def. kernel 2.4.22 ....
What I'm asking here is if I can update the kernel on the install CD1 of SlackWare .... and how it is done. I would like the whole steps pls ... and links for download.
And if possible ... some changes I have to do to the .config for my system ..

I have 2x512MB ... and a Hercules AIW ATI Radeon 9800SE.

P.S. sorry for the language but english isn't my base language ...

Yeah, I tried setting CONFIG_FB_VGA16 to not set, but that didn't work either, I'm still booting with a blank screen. I also set some file (I believe it was lilo.conf) to vga=ask or whatever like a previous post said, but no luck. I'm not sure if it matters, but I'm running an NVidia graphics card.

As far as my cable problems (that'd be cable modem, not cable that something connects too, sorry for the unclarity), I did dmesg and dmesg |grep eth0 and didn't return any results. It's odd because my 2.4.22 will read my Realtek Ethernet card at start up. Should I just try to load 2.6.0?

for realtek card, probably need the 8139too driver. It's in the Ethernet 10/100 section and that shouldn't be a problem for you. I have read about the NVidia cards around here saying that you need may need to get an updated driver. Search these pages for that and see what you can find.

jdif,

The quote that you put in there said /usr/include/linux not /usr/src/linux

Did you typo or were you just assuming they were the same?

Regarding the /usr/src/linux symlink...

In Slackware linux, there is no problem with updating the /usr/src/linux symlink. Here's why...

Slackware includes a packages called 'Kernel-Headers'. This includes parts of the kernel source for the default distro kernel. For slackware current, this is 2.4.24. The files reside in /usr/include/linux and /usr/include/asm, and are needed to compile software because of (i think..) glibc.

Anyway, as long as you have the 'Kernel Headers' package installed (and if you can compile stuff, and haven't messed with this stuff already, you do) it doesn't matter which kernel sources /usr/src/linux points to, since the includes are not linked to /usr/src/linux. Now - don't worry that the kernel headers package is not the same version as your kernel (ie 2.6.1), because it only needs to match glibc, which is compiled against the kernel that slackware was designed around.

In summary: If you have glibc and kernel headers packages from the same slackware version there is no problem with pointing /usr/src/linux to the 2.6.0 sources.

Hey .. you there ...
why don't wou help me guys ....
pls ... I haven't find any solution to my problem..
SlackWare and SATA HDD ...
Can I update the kernel on the install CD1 of SlackWare .... and how it is done. I would like the whole steps pls ... and links for download

DGAlexandru,
check out the Slackware site. You can use a kernel from a floppy but first you'll have to make one for your system, probably using your install disks to boot from. You would need to make a .bz image I believe and then, when prompted, you can look for a kernel there instead of on the CD.
Check out www.slackware.com. They might cover this in detail.
Check www.kernel.org to download source for the new kernel.

Hy there ...

Vincent_Vega, thanks for the help .... but I can't do that ... I have no FDD in my computer ... I can only boot from CD or HDD ...