Hi.

I'm playing with the 2.6.4 kernel at the moment. Everything seems to work ok except for the sound and usb mass storage. I'm not too worried about the sound as of yet but the usb prob is annoying me.

When I first set up the kernel I included usb support as modules but forgot to inlcude vfat filesystem support in the kernel. Silly mistake I know. I did make menuconfig again and include vfat support as a module. Now when I try to mount my usb keyring I am told that there is no such device, '/dev/sda1'. This problem does not occur with the 2.4.25 kernel.

Any ideas??

For people who have trouble getting sounds from their pc-speaker:
Enable Drivers -> Input -> Misc in menuconfig
Then an option for your pc-speaker will appear.
I've had the same problem and it took me a while to figure it out. Still don't know why this is listed under inputdevices.

On another note, I've compiled the the 2.6.4 kernel and everything works fine, except for one little thingie: ALSA correctly detects my SB Audigy 1, but I can't seem to get my remotecontrol to work. I passed the enable_ir=1 option to the kernel, but it doesn't seem to do anything.
Some people suggested sending a special controlcode to /dev/snd/midiC0D1, but that doesn't work either.
groups.google.com gives me nothing, nor the alsa-docs or lirc mailinglists, so this is pretty much my last chance before I have to start ritually sacrificing goats.

Has anyone got his Audigy remote to work under kernel 2.6 with ALSA? I'd really like to find out how.

I don't know why but the version still shows up as 2.4....

dushkinup,


try after "make menuconfig" enter these commands as root:

make bzImage && make modules && make modules_install
cp arch/i386/boot/bzImage /boot/bzImage-2.6
cp System.map /boot/System.map
cd /boot
cp vmlinuz /boot/vmlinuz.bak.old

edit lilo.conf:
***
#
image = /boot/bzImage-2.6 #this is the newkernel from arch/i386/boot
root = /dev/hda10 #change this to your root directory
label = linux-2.6
read-only
# old slack kernel
image = /boot/vmlinuz.bak.old #this is the vmlinuz you copied
root = /dev/hda10 #change this to your root dir
label = linux-2.4
read-only
***

run lilo by typing "lilo"
if you get no errors then reboot.

if it still loads 2.4. login as "root" then type "lilo" again.. then reboot
if it still loads 2.4 check your /usr/src/linux if its linked to /usr/src/linux-2.6 by typing "ls -al /usr/src/linux

hope that helps

Hello, I have been trying to update to the 2.6.4 Kernel from 2.4.22 for the past few nights. The first time I tried I got the infamous blank screen at reboot. I have tried all the fixes I have found here, to no avail. I just tried to recompile from scratch again and now my new and my old Kernel do the same thing, blank screen at boot. I had to boot from my rescue floppy to get it up. I am obviously an amateur, and I'm sure I am overlooking something simple. The first time I compiled the 2.6.4 kernel, when it didn't work all I had to do was choose my slack.old kernel from lilo, and it would boot right back into my original. I followed the kernel recompile guide that is posted here, and everything went smoothly, even when I got the blank screen I was confident it would work out because I remembered all the post talking about how common it was. Anyway, after I tried all the fixes here, and none worked, I thought I should just try to recompile again. The second time I recompiled I skipped the first few steps in the guide, because I had already completed them previously. I'm sure that is where my problems got worse (now my new and my old Kernel do the same thing, blank screen). Any help would be greatly appreciated.

Thanks...


By the way, I am running a P4 3 GHz with Slackware 9.1, and a Nvidea Geforce 5900 FX 128 Mb video card.


P.S. I just started a local Linux User Group and I really need to get this resolved, so that I understand the issue and can help the members of the group recompile in the next couple of weeks. Thanks again...

make sure that you select the framebuffer options. That should fix the blank screen prob.

new kernel compile error ( post #1)

HI

I am running linux machine on 2.4.20-8(The red hat kernel which comes in shipping). It is working great. And all things are being configured.

Now i need to run 2.4.20 vanilla kernel for some project.First of all can i do that.

I am using the documentation on How to compile a new kernel. i am making new link

using ln -s linux-2.4.20 linux-2.4 in /usr/src directory.

ran make xconfig and loaded the configuration file from /usr/src/linux-2.4.20-8/.config

Saved it .

ran make dep

ran make

ran make modules

ran make modules_install

ran make bzImage

ran make install

Only error i get is that the image is too large to boot from the floppy disk. When i look into my /boot directory it has made the initrd-2.4.20.img and also System.map-2.4.20 also vmlinuz link to vminuz-2.4.20. But does not make "module-info-2.4.20"

Here are the contents of the boot directory expect the above i told you, which i deleted before POSTING this message as i am going to try it agian. So do not be confused

boot.b config-2.4.20-8smp kernel.h module-info System.map vmlinux-2.4.20-8
chain.b grub lost+found module-info-2.4.20-8 System.map-2.4.20 vmlinux-2.4.20-8smp
config-2.4.20 initrd-2.4.20-8.img message module-info-2.4.20-8smp System.map-2.4.20-8 vmlinuz-2.4.20-8
config-2.4.20-8 initrd-2.4.20-8smp.img message.ja os2_d.b System.map-2.4.20-8smp vmlinuz-2.4.20-8smp





It also made the entry into the "boot/grub/menu.lst file"

But when i try to load this kernel it says CPU=0 and frquency 0 and HANGS there.................grrrrrrrrr


I also checked the /lib/modules/2.4.20/build/.config file it is fine and present.

Please suggest what i am going wrong?

Thanx..

Gaurav

Hi,
I did my first recompile to 2.6.5. Again, I have sound problems but I'm not too worried about that. I got some errors telling that the modules cannot be loaded. I don't know why. Like, module for ntfs support. It is not allowing me to reinstall a newer version of alsa. It says ALSA is already built-in. How do I override it?

In my processor architecture what should I mention? i386 or Athlon.?
I have ATHLON 2200+ XP T-Bred.
Thanx in advance.

If you built alsa into the kernel then it will stay there...
If you want to be able to update it, it must be built as a module.
These days with things changing so fast, I build the kernel with
# Sound
#
CONFIG_SOUND=y

but then say no to alsa and OSS

then I get the latest alsa files from their website and install manually from the card specific instructions on their site. It always works for me, (soundblaster live) though I cant vouch for the other cards. It is a bit tedious as there are 3 or 4 .gz files to unpack and install, but it is all part of the fun...

I think someone should edit this post and add "You may need to reinstall ALSA and several other drivers"

I'm having the same problem. When i boot into the new kernel, i get a black screen. but when i boot into my old one, everything seems ok.

Someone replied and said to select the framerbuffer options... how do i do this?

edit: i re-compiled it again and im even more messed up. i think it got rid of my old vmlinuz.old and put the unworking 2.6.5 one there and dumped my working 2.4.22

how do i uninstall kernel 2.6? It wont let me use my network card and the oss doesnt work (open sound system) and I really just dont want to put up wit it.. I booted into the 2.4 kernel i was just wondering though how to remove the 2.6 kernel..

ok, i got rid of the black screen, but i get the error no screens found when starting xstart. ive configured xf86config

Hi,
Try running xf86config. Go through the options and carefully set it up. It should work fine!!

DaOne,

Thank you for such a great guide. I just installed my first kernel (2.6.5, successfuly) and am loving it. I had problems with sound, but I realized I hadn't selected support for ALSA when I did "make menuconfig."

All is great!