Sorry guys when all else fails RTFM or Read The Entire Thread you guys are great framebuffer is working now just wondering why usb is not had it before but guess some stuff doesnt transfer well.

This is probably a dumb question, but how do I get the 2.6.1 kernel to appear in /boot/vmlinuz and rename the old 2.4 kernel from vmlinuz to vmlinuz.old?

mv /boot/vmlinuz /boot/vmlinuz.old

cp -v arch/i386/boot/bzImage /boot/vmlinuz-2.6

Hi everybody,

as a newbie i tried to follow all recommandations to build the new kernel on my slackware 9.1.
What i got is a blank screen after kernel boot.
The kernel is still there, working perfectly (apart not loading some module for network card), i can login in "blind mode" and even start X that works perfectly (nvidia driver still to come ) .
I had a similar problem with kernel 2.22, after starting X the nvidia driver leves a black screen if i logout from X.

Any hint ?

Ruggero

i just compiled my first kernel, 2.6.1, slackware 9.1, and everything worked very fine, thanx to all of you very polite and helpfull ppl.
but i do have some questions, the first one, how or where is the latest boot log? if you can get those, allt the things that come upp on the screen when you boot the kernel? :=) coz, i cant scroll allt the way upp, just some part..

than here comes the thing, i compiled the kernel with thing my computer need, for ex, agpgart, ide_scsi (really not shure if this one is needed), then ALSA for the sound card and the thing thats needed for my scard,
so, when it boots first thing:

Now that is really nice, everything was found and it worked, but here comes the funny thing, under that, i get this:

well, whats going on? i guess that agpgart, compiled into kernel was not found this time as module right? where do i control what module are loaded and what are not? i mean the sound works, but still the error message.. advise? explanation? :meconfused:
plus one more thing, how do i realy know if xwindows is running in DRI mode with accelerated xserver? that is using the hardware..

Thanx, any advice appriciated..

//Tisch

those are easy to fix!

edit /etc/rc.d/rc.modules and just comment out those modules (seeing as you dont need them )

then just run alsamixer or alsaconf then run 'alsactl store && alsactl restore'

and it should be good

1) How much memory do you have? If you have 1GB or more, you''l need to enable high memory support.

2) Remove all framebuffer support for your video card...VESA support should be fine.

Here is a snip from my kernel config under Device Drivers for reference...

# Graphics support
#
CONFIG_FB=y
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_IMSTT is not set
CONFIG_FB_VGA16=m
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_RADEON=m
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SIS is not set
# 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_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y

#
# Logo configuration
#
# CONFIG_LOGO is not set

Vega....thank you, that got my Lilo to work, but I had more trouble. I recompiled everything, blah blah, and applied the configuration for .config to prevent blank screen, but I still get blank screen. Anyone know why? I've checked it over 3 times and I can't find anything, and my .config file matches my 2.6.1 .config file.

Hey all, first I want to say thanks for this thread, it helped immensely when I decided to compile 2.6.1. Everything is working on the *counts* 5th try

I do have a couple questions though,

1) I compiled in support for the /proc filesystem. Somewhere along the line I read I should add to /etc/fstab the line:

This doesn't seem right to me, thought I would check here. My main problem with the /proc fs is understanding it. I'm not sure now where my CD-RW and DVD drive are. Or how to access the floppy drive. Obviously I'm missing something somewhere, I just don't know where, and don't know how to go about getting all my devices back. Short of re-compiling with devfs instead of proc.

2) I understand that the 2.6.x kernel doesn't require sending the SCSI stack to cdrecord, this is fixed in the CVS version of cdrecord? And after compiling, are there any flags I have to pass to -not- use the SCSI stack?

3) One final thing, I compiled a preemptible kernel for the Athlon CPU, some apps actually seem slower now... I use fluxbox as a wm, and running nautilus through fb seems to take twice as long. Any ideas on what I should check?

Thanks in advance,
Rahven

------edited, nvrmind

sorry

I just learned that you had to have a recent version of mod-init-tools in order for the new kernel (2.6.0) to work.

However, I can't seem to get it installed.

I downloaded mod-init-tools-0.9.11a-4mdk.i586.rpm tried to install it under root. (by the way, I'm running Mandrake 9.1)

here's what I get:

error: failed dependencies:
modultils < 2.4.22-10mdk conflicts wit module-init-tools-0.9.11a-4mdk
devfsd < 1.3.25-31mdk conflicts with module-init-tools-0.9.11a-4mdk


What should I do from here?

Hello Finally I got this (2.6.1) kernel to boot, BUT some problem thou

1. my system speaker dont work
2. the modules dont load when booting but loads fine with modprobe ( I got module-init-tools 0.9.13 )

this is what I get when I boot : QL_MODULES - function not implemented , but when I run "modprobe nvidia" it works fine

I don't want to sound rude, but this compile guide has a problem, I think. Read this:

http://www.ussg.iu.edu/hypermail/lin...07.3/0587.html

Quote from post:
"
And this is actually what has been the suggested environment for at
least the last five years. I don't know why the symlink business keeps
on living on, like a bad zombie. Pretty much every distribution still
has that broken symlink, and people still remember that the linux
sources should go into "/usr/src/linux" even though that hasn't been
true in a _loong_ time.
"
I was directed to this after telling someone how using a new kernel broke my old one.

Once the kernel source is in place, creating the new symlink takes care of this.