Bug#290697: (fwd) Re: Bug#290697: SOLVED, kernel: no vesafb module in /etc/modules/'uname -r'

[maximilian attems <debian@sternwelten.at>]

reassign 290697 kernel-package
retitle 290697 add doc for initrd options
severity 290697 wishlist
thanks

bug submitter talks about make-kpkg, but perhaps it belongs to initrd.

----- Forwarded message from linux <alexxmed@linux.it> -----


Alle 21:13, sabato 5 febbraio 2005, hai scritto:
> severity 290697 normal
> thanks
>
> On Sun, 16 Jan 2005, Alex wrote:
> > I am,
> >
> > 1) booting with a debianized kernel-image-xxx (from 2.6.8-12 to
> > 2.6.10-1, all working perfectly)
> >
> > 2) cd into a new-clearly (and same version) kernel-source package
> >
> > 3) make oldconfig (no any changes)
>
> please post the .config you are using now at that stage?
>
> > 4) fakeroot make-kpkg --append-to-version=.yyy --initrd --revision
> > alex.xxx kernel_image
> >
> > 4) rebooting with another kernel
>
> why?
>
> > 5) rm /lib/modules/xxx.yyy
>
> whatfor?
>
> > 6) dpkg -i kernel-image-xxx-yyy
> >
> > 7) rebooting and have same blacked ttyN consoles.
> > Blinded writing is possible for logging, launch programs, other.
> >
> > X start normally with kdm.
> >
> > ===>> that is with kernel.deb compiled on my and other laptop
> > computer and is probed on my and another laptop computer.
> 

that is:

joint: fbcon, font, bitlib, vesafb, cfbcopyarea, cfbimgblt
cfbfillrect into /etc/mkinitrd/modules,

then:

# mkinitrd -o /boot/initrd.img-2.6-10-alex /lib/modules/2.6.10-alex
# ln -sf /boot/initrd.img-2.6.10-alex /initrd.img

obviously lilo or (what for) grub


then tty start normally and make-kpkg --initrd works fine.

That is all obious, Yet. but I think better 2 or 3 rows into man make-kpkg 
--initrd options like this: look for rights options 
into /etc/mkinitrd/modules IF YOU WILL TTY working ....

Bye! AND thanks anymore!

Alex

----- End forwarded message -----