Hello,

first I tried compiling the kernel with the default configuration,
religiously following the Kernel Rebuilt Howto from
http://www.digitalhermit.com/~kwan/kernel.html.

For the first shot I used the default configuration. make xconfig gave
me a window with unreadable characters, but running
scripts/kconfig/qconf arch/i386/Kconfig directly got me pas that
problem.

I just saved the configurarion, set EXTRAVERSION, and did a 'make
bzImage', 'make modules', became root, 'make modules_install', created
the initial ramdisk then copied the bzImage to /boot, set up
grub.conf.

Here's what grub.conf looked like after installing Fedora then
upgrading with apt-get:

default=1
timeout=3
splashimage=(hd0,0)/grub/splash.xpm.gz
title Fedora Core (2.4.22-1.2188.nptl)
root (hd0,0)
kernel /vmlinuz-2.4.22-1.2188.nptl ro root=LABEL=/ rhgb
initrd /initrd-2.4.22-1.2188.nptl.img
title Fedora Core (2.4.22-1.2115.nptl)
root (hd0,0)
kernel /vmlinuz-2.4.22-1.2115.nptl ro root=LABEL=/ rhgb
initrd /initrd-2.4.22-1.2115.nptl.img

I added the following at the bottom:

title Test Kernel
root (hd0,0)
kernel /bzImage-2.6.6boby ro root=LABEL=/ rhgb
initrd /initrd-2.6.6boby.img

Now it looks like, contrary to lilo, you mustn't run grub to install
the changes, right? Anyway when things failed later on, I tried
running grub then exiting when I got the prompt.

I rebooted and hey, the new kernel worked. As expected it didn't fit
my computer perfectly (e.g. the usb mouse didn't worked).

Then I copied a .config from the "Linux on a ThinkPad X40" page
(http://www.chronox.de/x40_linux/linux_on_x40.html). make xconfig,
save it, build everything.

I was a little more daring this time, instead of making the ramdrive
and copying the kernel myself, I simply did 'make modules_install ;
make install'. I checked grub.conf; there was a new entry at near the
top, which I moved to the bottom:

title Fedora Core (2.6.6-x40)
root (hd0,0)
kernel /vmlinuz-2.6.6-x40 ro root=LABEL=/ rhgb
initrd /initrd-2.6.6-x40.img

When I tried to boot the new kernel, this time I got a panic because
it couldn't mount the root filesystem.

Weird, what's the difference with the "Test Kernel" entry. Putting a
"root=/dev/hda3" solved that problem. But does it? Anyway I want to
understand...

I also tried going back to manual mkinitrd, copy bzImage etc, still no
cigar.

Sadly, I still have no usb mouse; not even the internal mouse (my
computer is a laptop) works this time (it did with the Test Kernel).

I see that I have a bunch of '.ko' files in the apprpriate
/lib/modules directory (.o extension changed to .ko - kernel o,
right?):

lib/modules/2.6.6-x40/kernel/drivers/usb
/lib/modules/2.6.6-x40/kernel/drivers/usb/input/usbhid.ko
# ...
/lib/modules/2.6.6-x40/kernel/drivers/usb/core/usbcore.ko
/lib/modules/2.6.6-x40/kernel/sound/usb

....and lsusb says "cannot open /proc/bus/usb, No such file or
directory (2)".

Any help? TIA...
--
Jean-Louis Leroy

ps: my grub.conf in entirety:

default=1
timeout=3
splashimage=(hd0,0)/grub/splash.xpm.gz
title Fedora Core (2.4.22-1.2188.nptl)
root (hd0,0)
kernel /vmlinuz-2.4.22-1.2188.nptl ro root=LABEL=/ rhgb
initrd /initrd-2.4.22-1.2188.nptl.img
title Fedora Core (2.4.22-1.2115.nptl)
root (hd0,0)
kernel /vmlinuz-2.4.22-1.2115.nptl ro root=LABEL=/ rhgb
initrd /initrd-2.4.22-1.2115.nptl.img
title Test Kernel
root (hd0,0)
kernel /bzImage-2.6.6boby ro root=LABEL=/ rhgb
initrd /initrd-2.6.6boby.img
title Fedora Core (2.6.6-x40)
root (hd0,0)
kernel /vmlinuz-2.6.6-x40 ro root=LABEL=/ rhgb
initrd /initrd-2.6.6-x40.img


my fstab:

LABEL=/ / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /proc proc defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/hda5 swap swap defaults 0 0
toots:/home /mnt/toots/home nfs defaults,user,rw,noauto 0 0

....should I post my kernel .config?

On Tue, 11 May 2004 15:46:25 +0200, Jean-Louis Leroy wrote:

> Hello,
>
> first I tried compiling the kernel with the default configuration,
> religiously following the Kernel Rebuilt Howto from
> http://www.digitalhermit.com/~kwan/kernel.html.
>
> For the first shot I used the default configuration. make xconfig gave
> me a window with unreadable characters, but running
> scripts/kconfig/qconf arch/i386/Kconfig directly got me pas that
> problem.


Hmmm.... Did you first run 'make mrproper' after making sure you had the
correct packages needed for the 2.6 kernel (see below for some of the
RPM's you should have in place).


> I just saved the configurarion, set EXTRAVERSION, and did a 'make
> bzImage', 'make modules', became root, 'make modules_install', created
> the initial ramdisk then copied the bzImage to /boot, set up grub.conf.


You need to configure the kernel to your actual hardware specifications,
use a [.]config file similar to the /boot/config-2.4.22-1.2188 file.


> Here's what grub.conf looked like after installing Fedora then upgrading
> with apt-get:
>
> default=1
> timeout=3
> splashimage=(hd0,0)/grub/splash.xpm.gz title Fedora Core
> (2.4.22-1.2188.nptl)
> root (hd0,0)
> kernel /vmlinuz-2.4.22-1.2188.nptl ro root=LABEL=/ rhgb initrd
> /initrd-2.4.22-1.2188.nptl.img
> title Fedora Core (2.4.22-1.2115.nptl)
> root (hd0,0)
> kernel /vmlinuz-2.4.22-1.2115.nptl ro root=LABEL=/ rhgb initrd
> /initrd-2.4.22-1.2115.nptl.img
>
> I added the following at the bottom:
>
> title Test Kernel
> root (hd0,0)
> kernel /bzImage-2.6.6boby ro root=LABEL=/ rhgb initrd
> /initrd-2.6.6boby.img
>
> Now it looks like, contrary to lilo, you mustn't run grub to install the
> changes, right? Anyway when things failed later on, I tried running grub
> then exiting when I got the prompt.

Correct no need to re-run GRUB after making changes.


> I rebooted and hey, the new kernel worked. As expected it didn't fit my
> computer perfectly (e.g. the usb mouse didn't worked).
>
> Then I copied a .config from the "Linux on a ThinkPad X40" page
> (http://www.chronox.de/x40_linux/linux_on_x40.html). make xconfig, save
> it, build everything.


Why, is this your Laptop make and model?


> I was a little more daring this time, instead of making the ramdrive and
> copying the kernel myself, I simply did 'make modules_install ; make
> install'. I checked grub.conf; there was a new entry at near the top,
> which I moved to the bottom:
>
> title Fedora Core (2.6.6-x40)
> root (hd0,0)
> kernel /vmlinuz-2.6.6-x40 ro root=LABEL=/ rhgb initrd
> /initrd-2.6.6-x40.img
>
> When I tried to boot the new kernel, this time I got a panic because it
> couldn't mount the root filesystem.
>
> Weird, what's the difference with the "Test Kernel" entry. Putting a
> "root=/dev/hda3" solved that problem. But does it? Anyway I want to
> understand...

Red Hat / Fedora modifies the source kernels makes use of partition labels
while the source tree from kernel.org does not. You should use the actual
drive/partition and not the label.


> I also tried going back to manual mkinitrd, copy bzImage etc, still no
> cigar.
>
> Sadly, I still have no usb mouse; not even the internal mouse (my
> computer is a laptop) works this time (it did with the Test Kernel).
>
> I see that I have a bunch of '.ko' files in the apprpriate /lib/modules
> directory (.o extension changed to .ko - kernel o, right?):
>
> lib/modules/2.6.6-x40/kernel/drivers/usb
> /lib/modules/2.6.6-x40/kernel/drivers/usb/input/usbhid.ko # ...
> /lib/modules/2.6.6-x40/kernel/drivers/usb/core/usbcore.ko
> /lib/modules/2.6.6-x40/kernel/sound/usb
>
> ...and lsusb says "cannot open /proc/bus/usb, No such file or directory
> (2)".
>
> Any help? TIA...

You seemed to have missed a few things, try installing the updated
packages found here;

http://people.redhat.com/arjanv/2.6/RPMS.kernel/

(At least, versions newer then the listed are OK)
device-mapper-1.00.07-3.1.i386.rpm
initscripts-7.28-1.i386.rpm
lvm-1.0.3-17.i386.rpm
lvm2-2.00.08-2.i386.rpm
mkinitrd-3.5.15.1-2.i386.rpm
modutils-2.4.26-15.i386.rpm

And you need to create a /etc/modprobe.conf file for the 2.6 series
kernels (as root;/sbin/generate-modprobe.conf /etc/modprobe.conf). Do this
using one of the 2.4 kernels.

Hints; 'make clean' and 'make oldconfig' and then try again

Try using the kernel-source-2.6.5-1.356.i386.rpm (from the link
above) as your source kernel starting point. The 2.6.6 version
should be available in the next day or so.



--
"In short, without this exclusive franchise, called the Windows API,
we would have been dead a long time ago." M$ Senior VP Bob Muglia '96

>> Then I copied a .config from the "Linux on a ThinkPad X40" page
>> (http://www.chronox.de/x40_linux/linux_on_x40.html). make xconfig, save
>> it, build everything.
>
>
> Why, is this your Laptop make and model?

Yes.

> You seemed to have missed a few things, try installing the updated
> packages found here;
>
> http://people.redhat.com/arjanv/2.6/RPMS.kernel/
>
> (At least, versions newer then the listed are OK)
> device-mapper-1.00.07-3.1.i386.rpm
> initscripts-7.28-1.i386.rpm
> lvm-1.0.3-17.i386.rpm
> lvm2-2.00.08-2.i386.rpm
> mkinitrd-3.5.15.1-2.i386.rpm
> modutils-2.4.26-15.i386.rpm

Ok, did it. However, I still get a:

/dev/mapper/control: open failed: No such file or directory
Is device-mapper driver missing from kernel?
Command failed

[root@boby linux-2.6.6]# rpm -q device-mapper
device-mapper-1.00.07-3.1

....in the following two situations: while doing 'make install' after
compiling the kernel myself; and when I tried to install
kernel-2.6.5-1.356.i686 from people.redhat.com.

However, after doing what you say, things already work better. The usb
mouse works, but not the internal mouse. And there's no sound. I see
from lsmod that I used to have a i810_audio modules in the 2.4 kernel,
but not in 2.6.6.

....wait: after re-installing the 2.6.6 kernel once again and
rebooting, no usb mouse again!

In spite of the failure mentioned above during the kernel 2.6.5 rpm
installation, I tried booting that kernel too. I see a message related
to device-mapper (looks like an ok message), however, the kernel hangs
just after printing "Freeing unused kernel memory: 144k freed". When I
do ctrl-alt-del, I get a message related to md0 mode and the system
reboots - apparently in a clean fashion.
--
Jean-Louis Leroy
Sound Object Logic
http://www.soundobjectlogic.com

Jean-Louis Leroy <jll@soundobjectlogic.com> writes:

> However, after doing what you say, things already work better. The usb
> mouse works, but not the internal mouse. And there's no sound. I see
> from lsmod that I used to have a i810_audio modules in the 2.4 kernel,
> but not in 2.6.6.
>
> ...wait: after re-installing the 2.6.6 kernel once again and
> rebooting, no usb mouse again!

The "Linux on the Thinkpad T40" at http://bellet.info/laptop/t40.htm
contains information that applies to X40 as well it seems. It helped
me solve the dual touchpad/usb mouse problem.

WRT sound: it also says that ALSA works fine on both 2.4 and 2.6
kernels. I installed the modules and tried `modprobe
snd-intel8x0'. lsmod and kcontrol say the modules are there but still
no sound. And, lsmod says that nobody uses snd_intel8x0. Have I
forgotten someting?
--
Jean-Louis Leroy
Sound Object Logic
http://www.soundobjectlogic.com

On Wed, 12 May 2004 15:53:31 +0200, Jean-Louis Leroy wrote:

> Jean-Louis Leroy <jll@soundobjectlogic.com> writes:
>
>> However, after doing what you say, things already work better. The usb
>> mouse works, but not the internal mouse. And there's no sound. I see
>> from lsmod that I used to have a i810_audio modules in the 2.4 kernel,
>> but not in 2.6.6.
>>
>> ...wait: after re-installing the 2.6.6 kernel once again and rebooting,
>> no usb mouse again!
>
> The "Linux on the Thinkpad T40" at http://bellet.info/laptop/t40.htm
> contains information that applies to X40 as well it seems. It helped me
> solve the dual touchpad/usb mouse problem.

Good, glad to hear this. I was about to suggest that you go back to
http://www.chronox.de/x40_linux/linu...ing_the_kernel
and read the sections on GPM and XFree86.

> WRT sound: it also says that ALSA works fine on both 2.4 and 2.6
> kernels. I installed the modules and tried `modprobe snd-intel8x0'.
> lsmod and kcontrol say the modules are there but still no sound. And,
> lsmod says that nobody uses snd_intel8x0. Have I forgotten someting?

Check your /etc/modprobe.conf file (and modules.conf for 2.4 kernels) and
make sure you have something like (from http://www.alsa-project.org/);


# ALSA portion
alias char-major-116 snd
alias snd-card-0 snd-intel8x0
# module options should go here

# OSS/Free portion
alias char-major-14 soundcore
alias sound-slot-0 snd-card-0

# card #1
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss

And install the ALSA RPM's (if needed);

$ rpm -qa --queryformat '%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}.rpm\n'
"*alsa*"

alsa-driver-1.0.4-1.i386.rpm
alsa-lib-1.0.4-1.1.fc1.fr.i386.rpm
alsa-utils-1.0.4-1.1.fc1.fr.i386.rpm
xmms-alsa-1.2.10-1.1.fr.i386.rpm
(optional; part of the xmms installed RPM's)

It's important to note that with ALSA the default sound levels are muted
at boot up time. One way to fix this is to modify /etc/rc.d/rc.local and
add something like(as root of course);

# Restore Alsa sound defined volume levels

/bin/aumix-minimal -f /etc/aumixrc -L >/dev/null 2>&1;

If you like/want the speaker beeps add;

# Restore the PC Speaker beeps
/sbin/modprobe pcspkr


Sample /etc/aumixrc file (adjust the default levels to suit you);

vol:85:85:P
pcm:85:85:P
speaker:85:85:P
line:85:85:P
mic:85:85:R
cd:85:85:P
igain:85:85:P
line1:85:85:P
phin:85:85:P
video:85:85:P


--
"In short, without this exclusive franchise, called the Windows API,
we would have been dead a long time ago." M$ Senior VP Bob Muglia '96

In the meantime I had nearly everything else working...including the
internal ipw2100 wireless nic!

Suspend/resume is a bit unreliable though.

>> WRT sound: it also says that ALSA works fine on both 2.4 and 2.6
>> kernels. I installed the modules and tried `modprobe snd-intel8x0'.
>> lsmod and kcontrol say the modules are there but still no sound. And,
>> lsmod says that nobody uses snd_intel8x0. Have I forgotten someting?
>
> Check your /etc/modprobe.conf
> [...]
> It's important to note that with ALSA the default sound levels are muted
> at boot up time. One way to fix this [...]

Thanks a lot, now everything works!

> If you like/want the speaker beeps add;
>
> # Restore the PC Speaker beeps
> /sbin/modprobe pcspkr

Thank you for the information but no than you ;-)
--
Jean-Louis Leroy
Sound Object Logic
http://www.soundobjectlogic.com