[vox-tech] I got 2.6 working!

[Ken Bloom]

--yrj/dFKFPuw6o+aM
Content-Type: text/plain; Format=Flowed; DelSp=Yes; charset=ISO-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable


On 2004.02.04 12:24, Peter Jay Salzman wrote:
> hi ken,
>=20
> On Wed 04 Feb 04, 12:15 PM, Ken Bloom <kabloom@ucdavis.edu> said:
> > Becuase I was discussing it with people at the meeting last night, =20
> I'm =20
> > sending out my status on the 2.6 kernel, maybe peopel can learn =20
> from =20
> > it.
> =20
> cool beans!
>=20
> > I had 2 major questions:
> > 1) Why the vesa framebuffer wasn't working in 2.6.0
>=20
> because many patches / driver fixes weren't merged with 2.6.0.  this =20
> was
> a known problem that got fixed.
>=20
> > 2) If I have to recompile several times, making small configuraiton =20
> > changes, how do I save time by using the binaries that I built last =20
> > time that haven't changed?
> =20
> why was this necessary?
>=20
> snip (i don't use debian's kernel compiling.  maybe i should...)
>=20
> >=20
> > 3) Another lesson learned
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
> > Make sure you have IDE disk support enabled, otherwise you'll get a =20
> > kernel panic that you can't mount the root drive.
> =20
> 1. hmmm.  that's wierd.  for me, 2.6.0 has CONFIG_IDE already set to
>    "y".  was it set differently for you?
>=20
>    i recall that a kernel shipped with ext2 turned off by default, =20
> but
>    that was ... years ago.
>=20
> 2. did you not use "make oldconfig"?  i find it VERY useful when
>    building new kernels.
>=20
> pete

I started out with no config at all (on my very first run to compile =20
2.6.0), and got it working and bootable except for the vesa =20
framebuffer. I did a make oldconfig from my 2.6.0 kernel, but when =20
moving to 2.6.2, I realized since I was compiling from scratch anyway, =20
I ought to do away with the need for an initrd. When I was doing this, =20
I forgot about the IDE disk support (CONFIG_BLK_DEV_IDEDISK) which had =20
been a module in 2.6.0 and was loaded off the ramdisk. So I had to =20
change some configuration options and recompile. Figuring out how to =20
rebuild only those things that had changed shortened the process for =20
the second attempt from 45 minutes to less than 5 minutes. (And had I =20
not figured out that I had to change *that particular option* the =20
second time around, I might have needed to recompile a few more times).

In short - I don't compile kernels the debian way, but once I compile =20
them, I package them the Debian way.

--Ken

--=20
I usually have a GPG digital signature included as an attachment.
See http://www.gnupg.org/ for info about these digital signatures.
My key was last signed 10/14/2003. If you use GPG *please* see me about=20
signing the key. ***** My computer can't give you viruses by email. ***

--yrj/dFKFPuw6o+aM
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBAIYINlHapveKyytERAr/8AJ9d2hCZUtZTfl1RpPRm02IeAG2SGQCgjBNg
bSB42ZNbETbe6cSfSUWmLfg=
=l1VL
-----END PGP SIGNATURE-----

--yrj/dFKFPuw6o+aM--