Re: [PROPOSAL] 2.4.27 as default 2.4 kernel for sarge
On Fri, Aug 27, 2004 at 10:52:54AM +0200, Sven Luther wrote:
> On Fri, Aug 27, 2004 at 07:53:09AM +0200, Christian Perrier wrote:
> >
> > > > Based on discussions on the debian-kernel list[1], I'd like to propose
> > > > that we use 2.4.27 as the 2.4 kernel for all architectures with 2.4 kernels
> > > > in sarge. The strongest arguments for 2.4.27, as opposed to 2.4.26 were noted
> > > > by tbm [3].
> > >
> > > One thing to bear in mind when making this kind of decision it that it
> > > seems to take d-i about 2 weeks to transition to a new kernel once the
> >
> > What are the plans regarding 2.6??
>
> It will be 2.6.8. The plans regarding this have been made by the debian-kernel
> team over a mont h ago now, and the 2.6.7 kernel has been almost abandoned
> since then. And we are not over enjoyed to be told to have to backport all
> this amount of work to 2.6.7, plus who know how many fixes where in mainline
> 2.6.8. Furthermore many of the debian specific 2.6.7 patches have been
> submitted upstream for 2.6.8.
>
> > Yesterday, I installed a HP Proliant DL240, with Broadcom Gigabit
> > Ethernet controllers....2.6.7 tg3 module does not seem to support
> > these while I've been told that 2.6.8 does.
>
> Yes, tg3 is one of the things that got fixed in 2.6.8. hotplug and sub don't
> play well together with my pegasos box on 2.6.7 too, and we gained at least
> s390 as new 2.6 arch with 2.6.8, maybe sparc and m68k too, depending on
> deadline.
To clarify, this most likely does not work on 2.4.26/27 because some
non dsg free firmware was recently removed from. Does 2.6.8 have this
code, or is it using the bcm5700 driver, or is there some code that
should be backported to 2.4.26/27.
All I know is that ever since the firmware was removed people have been
complaining, but no one seems to have offered a viable solution. I am
all ears.
--
Horms
Reply to: