32 bit bigotry running under 64 bit 2.6.6?
Chris Horn
machine is running, thanks to the DFS AMD64 kernel. My old custom 32 bit
2.4.22 kernel wouldn't boot, so I booted from the DFS CD and used the
mount-the-system-disks, chroot and dpkg-repack trick to get the new AMD64
one installed.
As expected, though, I can't compile anything for 64 bits (everything in
userland is 32; there is no /lib64 directory). For me, this was the
nVidia X drivers. After some thought, though, I've decided this is okay.
For the time being, I'm going to sit out 64 bits just run everything in
32. Sure it won't be 20% faster, but I don't really want to use Mandrake
or SuSE and Debian doesn't seem ready enough for me to run a multiarch (or
biarch) setup.
My question is this:
I'm trying to recompile a custom 2.6.6 kernel, but the configurator won't
let me choose anything but a 64 bit kernel! What's going on!?! Since my
2.4.22 one won't boot, how am I supposed to build a kernel that will just
mope around in 32 bits until Debian biarch gets on its feet? Do I need to
install a pre-packaged K7 kernel, or something?
Thanks.
Chris Horn.
--
To UNSUBSCRIBE, email to debian-amd...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Rob Weir
> My question is this:
> I'm trying to recompile a custom 2.6.6 kernel, but the configurator won't
> let me choose anything but a 64 bit kernel! What's going on!?! Since my
Does "make ARCH=i386 menuconfig" work?
--
Words of the day: Khaddafi enigma explosion eavesdropping infowar ISEC Area 51
Goswin von Brederlow
> So, my new hardware (Asus SK8V + Opteron) came and is installed. The
> machine is running, thanks to the DFS AMD64 kernel. My old custom 32 bit
> 2.4.22 kernel wouldn't boot, so I booted from the DFS CD and used the
> mount-the-system-disks, chroot and dpkg-repack trick to get the new AMD64
> one installed.
>
> As expected, though, I can't compile anything for 64 bits (everything in
> userland is 32; there is no /lib64 directory). For me, this was the
> nVidia X drivers. After some thought, though, I've decided this is okay.
>
> For the time being, I'm going to sit out 64 bits just run everything in
> 32. Sure it won't be 20% faster, but I don't really want to use Mandrake
> or SuSE and Debian doesn't seem ready enough for me to run a multiarch (or
> biarch) setup.
>
> My question is this:
> I'm trying to recompile a custom 2.6.6 kernel, but the configurator won't
> let me choose anything but a 64 bit kernel! What's going on!?! Since my
> 2.4.22 one won't boot, how am I supposed to build a kernel that will just
> mope around in 32 bits until Debian biarch gets on its feet? Do I need to
> install a pre-packaged K7 kernel, or something?
>
> Thanks.
> Chris Horn.
You have to to use the linux32 package.
MfG
Goswin
Chris Horn
Thanks. Someone on IRC pointed me in that direction, but I still couldn't
make it work. I have no idea what the problem was.
My solution was to build an i386 32 bit 2.6.6 Opteron kernel on an i386
box. That procedure went as it usually does (without a hitch) and I just
installed that deb on the new Opteron box. It boots just fine and life
with a custom kernel is good (except onbaord SK8V sound doesn't seem to be
supported).
It's a shame to not use the 64 bit side of the Opteron, but for now it's
going to have to do. I want to play my 32 bit only 3D game (RTCW)! Life
would certainly be easier if I hadn't started playing the occasional game
again (pure64).
If you're wondering what my kernel config looks like, email me.
Alternatively, I will probably post it soon to <http://blog.beefstew.net>.
Chris.
Chris Horn
> * Chris Horn [2004-06-03 12:52:02 -0400]:
> > My solution was to build an i386 32 bit 2.6.6 Opteron kernel on an i386
> > box. That procedure went as it usually does (without a hitch) and I just
> > installed that deb on the new Opteron box. It boots just fine and life
> > with a custom kernel is good (except onbaord SK8V sound doesn't seem to be
> > supported).
>
> Opteron 142 on it), running 2.4.26 (I won't touch Linux 2.6 until
> OpenAFS support is available for it). I managed to build and boot
> a 32/64 2.4.26 kernel, but discovered that I needed the biarch
> modutils in order to load the modules. They're easy enough to
> install, of course, but for now I've drawn the line at that point.
I'll have to check it out. What's the chip I should build support for
(modprobe will tell you which module is actually loaded)? In the mean-time,
I just dropped in an old Ensoniq AudioPCI (ens1370) I had lying around.
Beautiful sound in no time at all.
> I think you expressed an interest in the NVidia modules. I hope you
> noticed there is a separate release for amd64 (5332 rather thab
> 5336). I haven't yet tried to build it myself, but it should work.
I did notice this, but the problem then becomes that the game may not run
properly... It's still 32 bit. I guess I could try, but right now I'm just
happy that everything is working. Also, as far as I can tell, the biarch
port is being abandoned in favor of the more general multiarch one - but
multiarch is far from even being planned out!
> > It's a shame to not use the 64 bit side of the Opteron, but for now it's
> > going to have to do. I want to play my 32 bit only 3D game (RTCW)! Life
> > would certainly be easier if I hadn't started playing the occasional game
> > again (pure64).
>
> Lucky you. I must maintain 32-bit support for plenty of other reasons
> (e.g., my old NAG f95 compiler only runs in 32-bit mode).