RE: make-kpkg continued
| hi
|
| my first custom kernel was yet another 2.2.20 and was perfect.
Congratulations!
| i have now made three 2.4.18 kernels and none of them will "work" meaning
| that none of them gets gdm to start, or has any virtual terminals to log
| into (ctrl/alt/f1), cannot connect via ssh and cannot return a ping.
|
| almost none of the startup (dmesg, messages, etc) gets logged... just a
| few lines:
|
| Apr 19 12:03:02 bilbo -- MARK --
| Apr 19 12:22:43 bilbo kernel: Kernel logging (proc) stopped.
| Apr 19 12:22:43 bilbo exiting on signal 15
| Apr 19 12:27:57 bilbo syslogd 1.4.1#10: restart.
|
| there was an unsuccessful boot of 2.4.18 right after 12:22:43
|
| something is preventing the kernel logger from starting at the end of the
| startup. btw, the screen looks normal during the startup process, but it
| goes so fast... obviously, the network isn't getting started.
|
| i tried to model my .config file after the successful 2.2.20 one.
|
| any sugestions? i think i will download the 2.4.18 kernel-image package
| from testing and see if that will start.
Okay, you are probably close.
I'll give you how I do it...
1) Install source for 2.4.18 (or whatever) (obviuos)
2) copy .config from 2.2.20 kernel source or /boot directory to kernel
source
3) go to kernel source and do a "make oldconfig", answering any questions
4) do a "make menuconfig" to look things over and tweak
5) make-kpkg clean
6) make-kpkg --revision=(plug in today's date) kernel_image
7) dpkg -i (new kernel package)
I think where you may be going wrong is step 3. The 2.2.x and 2.4.x kernels
have different options, but the "make oldconfig" should fix things up
famously.
HTH,
Brooks
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: