RE: Trouble with upgrade to unstable on SS20 SMP
> -----Original Message-----
> From: James Nelson [mailto:JNelson4765@verizon.net]
> Sent: 16 July 2004 03:37
> To: debian-sparc@lists.debian.org
> Subject: Trouble with upgrade to unstable on SS20 SMP
>
> I had Woody running on this thing for a while, and recently
> decided to
> upgrade to unstable (new QFE card - want iptables for a router/Squid
> box). I am having a bit of a problem, though - doing apt-get
> dist-upgrade fails, saying that due to my CPU, libc6 (= 2.3.2.ds1-13)
> needs kernel 2.4.21 or greater.
>
> Okay, so I apt-get install kernel-image-2.4-sparc32-smp, and
> get unmet
> dependency warnings on libc6 (2.2.5-11.5).
>
> I am stuck - can't upgrade the kernel w/o libc, can't upgrade
> libc w/o
> the kernel. Something appears to be broken in the
> dist-upgrade system -
> either that, or my machine has something screwy about it.
>
> 2xTI SuperSparc 50's (per /proc/cpuinfo), maybe?
>
> Is there a way to shoehorn unstable on this without running headlong
> into dependency hell? I mean, short of compiling a kernel on
> my Sparc
> (ZZZZZzzzzz....) is there some magic switch or command I
> overlooked to
> just make it work?
You're entering a whole World Of Pain that I was in a couple of weeks ago
here.
Long and short of it is that 2.4.x kernels are pretty much b0rked on sparc32
and are, unfortunately, a prerequisite for Sarge.
As Jan just pointed out in another thread 2.4 development for sparc32 isn't
going to go anywhere fast now 2.6 is out but 2.6 currently doesn't work very
well on sparc32, either (let alone in SMP mode).
If you're desperate to get a machine running Sarge you're going to have to
either compile a 2.4 kernel or download one from http://osinvestor.com
before you do the dist-upgrade but my SS20 with two Ross 150MHz cards never
managed to stay up for more than 5 or 10 minutes at a time before
spinlocking with 2.4 on Woody and 2.4+Sarge was a complete disaster.
I, too, wanted to use my SS20 as an iptables router/firewall but I've had to
stick with 2.2/ipchains for the time being.
Gary
Reply to: