Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 38512 - USB keyboard/mouse don't work when kernel is compiled by genkernel 3.0.1_beta4/5
Summary: USB keyboard/mouse don't work when kernel is compiled by genkernel 3.0.1_beta4/5
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High major (vote)
Assignee: Brad House
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-17 07:45 UTC by giovanni.bobbio
Modified: 2004-01-19 07:13 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
Output of dmesg for the kernel built by the 1.8 genkernel (dmesg.og,10.65 KB, text/plain)
2004-01-19 06:53 UTC, giovanni.bobbio
Details
Output of dmesg for the kernel built by the 3.0.1_beta6 genkernel (dmesg.ng,10.33 KB, text/plain)
2004-01-19 06:54 UTC, giovanni.bobbio
Details

Note You need to log in before you can comment on or make changes to this bug.
Description giovanni.bobbio 2004-01-17 07:45:52 UTC
When booting a kernel compiled with the 3.0.1 genkernels the keyboard and mouse are disabled when the USB and PCI hotplugging service is started.
The same kernel sources, with the same config files, work perfectly if compiled with genkernel 1.8.
Tested with the latest gentoo (2.4.22-r5) or ck sources (2.4.23-r1).

Reproducible: Always
Steps to Reproduce:
Comment 1 Brad House 2004-01-18 13:52:17 UTC
no way it could be genkernel's fault if the kernel config
and sources are the same. Just NOT possible.
Comment 2 giovanni.bobbio 2004-01-19 06:53:42 UTC
Created attachment 24073 [details]
Output of dmesg for the kernel built by the 1.8 genkernel
Comment 3 giovanni.bobbio 2004-01-19 06:54:09 UTC
Created attachment 24074 [details]
Output of dmesg for the kernel built by the 3.0.1_beta6 genkernel
Comment 4 giovanni.bobbio 2004-01-19 07:13:58 UTC
I understand your point, still... I can reproduce this at will.
It may well be that I erred, or that the bug is not in genkernel, but I am not able to diagnose it any better.
Please follow my procedure and see if there's something horribly wrong. I list the history of what I've done:

cp -R linux-2.4.22-gentoo-r5/ linux-2.4.22-gentoo-r5-og
[Make a copy of the source tree, og for old genkernel]
vi /usr/portage/profiles/package.mask
[Mask genkernel 3.0.1]
emerge genkernel
[1.8 gets installed]
cp linux-2.4.22-gentoo-r5/.config /etc/kernels/config-2.4.22-gentoo-r5
ln -sf linux-2.4.22-gentoo-r5-og/ linux
genkernel
[Kernel with old genkernel is compiled]
vi /usr/portage/profiles/package.mask
[Remove mask]
emerge genkernel
[Re-emerge genkernel 3.0.1_beta6
rm linux
ln -s linux-2.4.22-gentoo-r5 linux
cp linux-2.4.22-gentoo-r5-og/.config /usr/share/genkernel/x86/kernel-config-2.4
[Copy the old config over the template]
genkernel --install all
diff linux-2.4.22-gentoo-r5/.config linux-2.4.22-gentoo-r5-og/.config
[Check that the config files are identical. They are.]
vi /boot/grub/grub.conf
[Set up grub appropriately]

Booting the two kernels produces the symptoms described in the original post.
I am attaching the dmesg output of the to boot procedures, and remain available to supply any other info you may judge relevant.