Surely we saw the table the wounds in southern climes sure she knew he'd found
a the bodies were to pay the raw and
agpae.gif
Description: GIF image
On Sun, Oct 08, 2006 at 04:16:58PM -0700, Matt Taggart wrote:
> No I mean the message from Yanko Kaneti <[EMAIL PROTECTED]> which says,
...
Yanko-san didn't have his facts quite right though I agree his
conclusion is correct:
linux-2.6.18/include/linux/pci_ids.h says:
#define PCI_DEVICE_ID_LSI_53
Package: linux-image-2.6.18-1-686
Version: 2.6.18-2
Mine is a Dell machine with SATA disk, I am using Debian sid, with
debian official kernel 2.6.18.
On boot time, it says:
ata1: SATA max UDMA/133 cmd 0xFE00 ctl 0xFE12 bmdma 0xFEA0 irq 58
ata2: SATA max UDMA/133 cmd 0xFE20 ctl 0xFE32 bmdma 0xFEA8
On Sun, 2006-10-08 at 21:16 -0600, Grant Grundler wrote:
> I didn't know Compaq used two different 53[cC]510 parts.
> Patch below adds the same tweak to the 0x0010 device ID.
>
> James or willy, this look good to you?
It seems reasonable.
Can we get confirmation from the bug submitter that it ac
Processing commands for [EMAIL PROTECTED]:
> clone 391451 -1
Bug#391451: Error detecting hard drive
Bug 391451 cloned as bug 391861.
> reassign -1 linux-2.6
Bug#391861: Error detecting hard drive
Bug reassigned from package `linux-kernel-di-powerpc-2.6' to `linux-2.6'.
> retitle -1 linux-2.6: [p
clone 391451 -1
reassign -1 linux-2.6
retitle -1 linux-2.6: [powerpc] Please enable the amd74xx driver
block 391451 with -1
thanks
> The on-board hard drive (40 GB Fujitsu MHT2040AS, 2.5", parallel ATA) is
> not detected. lspci shows the driver as an AMD 8111, but neither the
> kernel nor /lib/mo
James Bottomley writes...
> Er ... you mean the email that I sent pointing to a fix in the
> scsi-rc-fixes tree? Then yes, I think it's a correct fix. It's already
> in 2.6.18
No I mean the message from Yanko Kaneti <[EMAIL PROTECTED]> which says,
"Correct me if I am wrong but the fix mentio
Processing commands for [EMAIL PROTECTED]:
> reopen 391619
Bug#391619: p{re,ost}insts' comments contradict each other.
Bug reopened, originator not changed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debi
dann frazier writes...
> hey Grant/James,
> It looks like we're still having cpqarray/sym2 conflicts under
> 2.6.18 - any idea what this problem may be?
This is for dl380. At the very bottom (after the close of the bug) of
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=380272
someone sug
On Sun, 2006-10-08 at 14:40 -0700, Matt Taggart wrote:
> dann frazier writes...
>
> > hey Grant/James,
> > It looks like we're still having cpqarray/sym2 conflicts under
> > 2.6.18 - any idea what this problem may be?
>
> This is for dl380. At the very bottom (after the close of the bug) of
>
On Sun, 08 Oct 2006, Adam D. Barratt wrote:
> Hi (again),
>
> On Sun, 2006-10-08 at 02:34 -0700, Debian Bug Tracking System wrote:
> [...]
> > > clone 387331 -2
> > Bug#387331: Uninstallable due to unmet dep on kernel-image-2.4.27-3-686-smp
> > Bug 387331 cloned as bug 391706.
> [...]
> > retitl
Hi folks
Pending changes:
- xen images:
Remove 4gb fixup message again, it doses the machines.
Bastian
--
No one may kill a man. Not for any purpose. It cannot be condoned.
-- Kirk, "Spock's Brain", stardate 5431.6
signature.asc
Description: Digital signature
On 2006-10-06, Hilmar Preusse <[EMAIL PROTECTED]> wrote:
> On 05.10.06 Oleg Verych ([EMAIL PROTECTED]) wrote:
>> On Thu, Oct 05, 2006 at 09:49:58AM +0200, Hilmar Preusse wrote:
>
> Hi,
>
>> > Are the ready made Debian packages or do I have to build myself?
>>
>> I will, but it will be my first one
Hi (again),
On Sun, 2006-10-08 at 02:34 -0700, Debian Bug Tracking System wrote:
[...]
> > clone 387331 -2
> Bug#387331: Uninstallable due to unmet dep on kernel-image-2.4.27-3-686-smp
> Bug 387331 cloned as bug 391706.
[...]
> retitle -2 RM: kernel-image-2.4-686-smp -- RoM etch 2.6 only
I reali
On 2006-10-08, John Kelly wrote:
> On Sun, 8 Oct 2006 14:57:46 + (UTC), Oleg Verych
>>And this is possible without any *firmware* in debian/main and
>>installation process.
>
> Many things are possible for those doing the work. Are you doing the
> work?
Maybe, yes. There was one message here,
# See comments in body
tags 391709 = confirmed
merge 391709 379332
close 391710
close 391711
thanks
Hi,
On Sun, 2006-10-08 at 02:34 -0700, Debian Bug Tracking System wrote:
> Processing commands for [EMAIL PROTECTED]:
[...]
> > clone 389269 -5
> Bug#389269: kernel-patch-2.2.25-m68k: Shouldn't shi
On Sun, 8 Oct 2006 14:57:46 + (UTC), Oleg Verych
<[EMAIL PROTECTED]> wrote:
>> As for me, I want to make progress, to etch and a 2.6.18 kernel. The
>> debian kernel maintainers have a practical solution, and I agree with
>> them.
>[sounds ubuntu-like, but no flamewars, please]
Inflammatory
Hi Oleg
Sorry for taking so long to reply.
On Thursday 05 October 2006 06:55, you wrote:
> On Tue, Oct 03, 2006 at 04:30:13PM +0200, Georg Wittenburg wrote:
> > On Tuesday 03 October 2006 16:24, you wrote:
> > > On 2006-10-02, Georg Wittenburg <[EMAIL PROTECTED]> wrote:
>
> [.]
>
> > > Please don
On 2006-10-08, John Kelly wrote:
> On 2006-10-07, Oleg Verych wrote:
>
>> binary-firmware must be removed, or 15+ years of Debian are wasted
>
> If you want to re-live the past 15 years, take your own advice:
>
>> let them have own built kernel
>
> and do it yourself.
Hm. I have no problems doing
On 2006-10-07, Oleg Verych wrote:
> binary-firmware must be removed, or 15+ years of Debian are wasted
If you want to re-live the past 15 years, take your own advice:
> let them have own built kernel
and do it yourself.
As for me, I want to make progress, to etch and a 2.6.18 kernel. The
deb
Processing commands for [EMAIL PROTECTED]:
> clone 385273 -1
Bug#385273: kernel-headers-2.4.27-m68k: obsolete kernel, dummy bug
Bug 385273 cloned as bug 391705.
> reassign -1 ftp.debian.org
Bug#391705: kernel-headers-2.4.27-m68k: obsolete kernel, dummy bug
Bug reassigned from package `kernel-head
Your message dated Sun, 8 Oct 2006 11:16:41 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#391619: p{re,ost}insts' comments contradict each other.
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
22 matches
Mail list logo
