Re: Custom kernel for Debian-installer howto?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sat, 04 Mar 2006 16:18:07 +0100
Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de> wrote:
> Jacob S <stormspotter@6Texans.net> writes:
>
> > Hello list,
> >
> > I'm trying to install Debian Sarge on an AMD Athlon64 3200+. The
> > problem is the installer doesn't recognize my Uli 1689 SATA chipset.
> > However, this chipset appears to be supported in 2.6.12 and later
> > kernels with the sata_uli module.
> >
> > I have found some discussions about how to rebuild the
> > debian-installer with a custom kernel, but I am not sure if it will
> > work in my case. Being the new machine is my only AMD64 machine so
> > far, I will have to build the debian-installer and kernel on a
> > 32bit AMD running Sid, or my AMD64 machine running 32bit Knoppix.
> > Is there anything special I would need to do to get it to build
> > right?
>
> How about a Knoppix for amd64, Ubuntu live-cd for amd64 or even gentoo
> live-cd for amd64?
Thanks. I had not realized there was a Knoppix 64. Should have known
there's a live cd for everything. :-)
> You need 64bit unless you know what you are doing and are willing to
> hack around a lot.
>
> > Any other tips or suggestions on how to get the AMD64 port of Debian
> > installed on this machine?
>
> Install 32bit, install 64bit kernel, setup a 64bit chroot with
> (c)debootstrap, make it boot that.
hmm... Sounds complicated. I was just realizing I probably overlooked
the easiest option. The motherboard can do plain IDE, so all I have to
do is find a spare IDE around the house and install to that, upgrade
the kernel and copy the installation over to the SATA.
With 13 computers around the house (9 of them PCs) you would think a
spare IDE would be easy. hmm... which computer to cannabalize
temporarily... :-)
Thanks,
Jacob
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFECbRLkpJ43hY3cTURAqFaAJ9Q1ei/zZI1CkJuo00NclEL1pdNhgCcCJNc
ho0V2ZcRoMghhLiVnrClWoA=
=1KUp
-----END PGP SIGNATURE-----
Reply to: