[gentoo-dev] 2.6.16 and packages in conflict

[gentoo-dev] 2.6.16 and packages in conflict

[Daniel Drake]

Hi,

Linux 2.6.16 will be in the tree very soon. Assuming there aren't any 
major problems, we'll hopefully be marking it stable in 2-3 weeks.

As usual, please bring any conflicts (e.g. compilation failures of 
kernel module ebuilds against 2.6.16) to our attention by making them 
block bug 126972.

Thanks!
Daniel
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] 2.6.16 and packages in conflict

[Daniel Drake]

Daniel Drake wrote:
> Hi,
> 
> Linux 2.6.16 will be in the tree very soon. Assuming there aren't any 
> major problems, we'll hopefully be marking it stable in 2-3 weeks.

We're planning to mark it stable on 10th April. Maybe a few days later, 
need to double check that we don't have any in-kernel 2.6.16 showstoppers.

Please ensure your packages are fixed in the stable tree.

Daniel

-- 
gentoo-dev@gentoo.org mailing list

[gentoo-dev] Re: 2.6.16 and packages in conflict

[Duncan]

Daniel Drake posted <44312B63.1090009@gentoo.org>, excerpted below,  on
Mon, 03 Apr 2006 15:04:19 +0100:

>> Linux 2.6.16 will be in the tree very soon. Assuming there aren't any 
>> major problems, we'll hopefully be marking it stable in 2-3 weeks.
> 
> We're planning to mark it stable on 10th April. Maybe a few days later, 
> need to double check that we don't have any in-kernel 2.6.16 showstoppers.

This isn't a show-stopper, but it's possible you'll get others running
into the issue that understand as little as I did about it...  Maybe this
will save folks the hair tearing frustration I went thru tracing it.

AMD64 > 4G memory:  SCSI formerly (2.6.15 and earlier) used
bounce-buffers.  It now relies on the IOMMU, either the hardware GART
IOMMU for true AMD64, or a software emulation thereof for Intel's EM64T. 
It'll need to be configured into the kernel and working.  Also, here, I
had a BIOS issue.  AGP Hypertransport Fast-writes had to be disabled in
ordered for the IOMMU (and DRI/DRM) to function.  Because the kernel froze
every time I tried IOMMU, I had the kernel configured without it, so I had
/two/ changes to trace down and make, before it would work, thus the
problem, since either one alone wasn't enough.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html


-- 
gentoo-dev@gentoo.org mailing list