On 2/7/07, Grant Grundler <[EMAIL PROTECTED]> wrote:
On Tue, Feb 06, 2007 at 03:52:47PM +0400, Manu Abraham wrote:
> >attaching a dump of the regs (on 2.6.17.7) as well as the diff
>
> The device now works, used the demodulator driver alongwith the bridge
> driver.
Ok - thanks for the dmesg outp
On 2/7/07, Grant Grundler <[EMAIL PROTECTED]> wrote:
On Tue, Feb 06, 2007 at 03:52:47PM +0400, Manu Abraham wrote:
> >attaching a dump of the regs (on 2.6.17.7) as well as the diff
>
> The device now works, used the demodulator driver alongwith the bridge
> driver.
Ok - thanks for the dmesg outp
On Tue, Feb 06, 2007 at 03:52:47PM +0400, Manu Abraham wrote:
> >attaching a dump of the regs (on 2.6.17.7) as well as the diff
>
> The device now works, used the demodulator driver alongwith the bridge
> driver.
Ok - thanks for the dmesg output and log. I suspect you've already
tried cycling po
On 2/7/07, Luming Yu <[EMAIL PROTECTED]> wrote:
> none on the card, a flash or a firmware .. it has a 24c02 EEPROM for
> vendor information, that's all
Ok, sounds like windows driver can fix the broken EEPROM on you card.
Otherwise, I can not explain how windows driver can fix the problem for l
none on the card, a flash or a firmware .. it has a 24c02 EEPROM for
vendor information, that's all
Ok, sounds like windows driver can fix the broken EEPROM on you card.
Otherwise, I can not explain how windows driver can fix the problem for linux.
Anyway, this issue is NOT linux problem. right
On 2/6/07, Manu Abraham <[EMAIL PROTECTED]> wrote:
On 2/6/07, Luming Yu <[EMAIL PROTECTED]> wrote:
> > dang !
> >
> > rebooted it into 2.6.17.7
> >
> > no errors, during a bootup, BIST isn't running anymore
> > running M$ did change the status from dead to alive ??? shocked !!
>
> Interesting! d
On 2/6/07, Manu Abraham <[EMAIL PROTECTED]> wrote:
On 2/6/07, Manu Abraham <[EMAIL PROTECTED]> wrote:
> On 2/6/07, Luming Yu <[EMAIL PROTECTED]> wrote:
> > > dang !
> > >
> > > rebooted it into 2.6.17.7
> > >
> > > no errors, during a bootup, BIST isn't running anymore
> > > running M$ did change
On 2/6/07, Luming Yu <[EMAIL PROTECTED]> wrote:
> dang !
>
> rebooted it into 2.6.17.7
>
> no errors, during a bootup, BIST isn't running anymore
> running M$ did change the status from dead to alive ??? shocked !!
Interesting! does windows driver fixes the broken firmware/flash on this card?
dang !
rebooted it into 2.6.17.7
no errors, during a bootup, BIST isn't running anymore
running M$ did change the status from dead to alive ??? shocked !!
Interesting! does windows driver fixes the broken firmware/flash on this card?
attached lspci output in the very same setup as earlier,
On 2/6/07, Manu Abraham <[EMAIL PROTECTED]> wrote:
On 2/6/07, Grant Grundler <[EMAIL PROTECTED]> wrote:
> On Mon, Feb 05, 2007 at 09:33:39PM -0800, Andrew Morton wrote:
> > On Mon, 5 Feb 2007 22:03:31 -0700 Grant Grundler <[EMAIL PROTECTED]> wrote:
> >
> > > On Mon, Feb 05, 2007 at 09:55:28PM -07
On 2/6/07, Grant Grundler <[EMAIL PROTECTED]> wrote:
On Mon, Feb 05, 2007 at 09:33:39PM -0800, Andrew Morton wrote:
> On Mon, 5 Feb 2007 22:03:31 -0700 Grant Grundler <[EMAIL PROTECTED]> wrote:
>
> > On Mon, Feb 05, 2007 at 09:55:28PM -0700, Grant Grundler wrote:
> > ...
> > > > Control:
On 2/6/07, Manu Abraham <[EMAIL PROTECTED]> wrote:
On 2/6/07, Grant Grundler <[EMAIL PROTECTED]> wrote:
> On Mon, Feb 05, 2007 at 09:33:39PM -0800, Andrew Morton wrote:
> > On Mon, 5 Feb 2007 22:03:31 -0700 Grant Grundler <[EMAIL PROTECTED]> wrote:
> >
> > > On Mon, Feb 05, 2007 at 09:55:28PM -07
On 2/6/07, Grant Grundler <[EMAIL PROTECTED]> wrote:
On Mon, Feb 05, 2007 at 09:33:39PM -0800, Andrew Morton wrote:
> On Mon, 5 Feb 2007 22:03:31 -0700 Grant Grundler <[EMAIL PROTECTED]> wrote:
>
> > On Mon, Feb 05, 2007 at 09:55:28PM -0700, Grant Grundler wrote:
> > ...
> > > > Control:
On 2/6/07, Grant Grundler <[EMAIL PROTECTED]> wrote:
On Tue, Feb 06, 2007 at 09:20:15AM +0400, Manu Abraham wrote:
...
> >BIST is required to complete in 2 seconds. Either with success or failure.
> >I expect BIOS to have complained before launching grub/lilo.
...
> BIST is supposed to terminate
On Mon, Feb 05, 2007 at 09:33:39PM -0800, Andrew Morton wrote:
> On Mon, 5 Feb 2007 22:03:31 -0700 Grant Grundler <[EMAIL PROTECTED]> wrote:
>
> > On Mon, Feb 05, 2007 at 09:55:28PM -0700, Grant Grundler wrote:
> > ...
> > > > Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
>
On Tue, Feb 06, 2007 at 09:20:15AM +0400, Manu Abraham wrote:
...
> >BIST is required to complete in 2 seconds. Either with success or failure.
> >I expect BIOS to have complained before launching grub/lilo.
...
> BIST is supposed to terminate before, say the OS kernel is loaded?
Yes - that's what
On 2/6/07, Grant Grundler <[EMAIL PROTECTED]> wrote:
On Tue, Feb 06, 2007 at 10:28:56AM +0400, Manu Abraham wrote:
> On 2/6/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
> >On Mon, 5 Feb 2007 22:03:31 -0700 Grant Grundler
> ><[EMAIL PROTECTED]> wrote:
> >
> >> On Mon, Feb 05, 2007 at 09:55:28PM -0
On Tue, Feb 06, 2007 at 10:28:56AM +0400, Manu Abraham wrote:
> On 2/6/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
> >On Mon, 5 Feb 2007 22:03:31 -0700 Grant Grundler
> ><[EMAIL PROTECTED]> wrote:
> >
> >> On Mon, Feb 05, 2007 at 09:55:28PM -0700, Grant Grundler wrote:
> >> ...
> >> > > Control
On 2/6/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
On Mon, 5 Feb 2007 22:03:31 -0700 Grant Grundler <[EMAIL PROTECTED]> wrote:
> On Mon, Feb 05, 2007 at 09:55:28PM -0700, Grant Grundler wrote:
> ...
> > > Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- Fas
On Mon, Feb 05, 2007 at 10:03:31PM -0700, Grant Grundler wrote:
> On Mon, Feb 05, 2007 at 09:55:28PM -0700, Grant Grundler wrote:
> ...
> > > Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> > > Stepping- SERR- FastB2B-
> > > Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSE
On Mon, 5 Feb 2007 22:03:31 -0700 Grant Grundler <[EMAIL PROTECTED]> wrote:
> On Mon, Feb 05, 2007 at 09:55:28PM -0700, Grant Grundler wrote:
> ...
> > > Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> > > Stepping- SERR- FastB2B-
> > > Status: Cap- 66MHz- UDF- FastB2B-
On 2/6/07, Grant Grundler <[EMAIL PROTECTED]> wrote:
On Mon, Feb 05, 2007 at 05:09:01AM +0400, Manu Abraham wrote:
> Hi,
>
> I get this error on booting up 2.6.20 (Similar error on 2.6.17.7 also,
> the message is slightly different in 2.6.17.7)
>
> PCI Cannot allocate resource region 2 of device
On Mon, Feb 05, 2007 at 09:55:28PM -0700, Grant Grundler wrote:
...
> > Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> > Stepping- SERR- FastB2B-
> > Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> > SERR+ > Latency: 0, Cache Line Size 0c
> >
On Mon, Feb 05, 2007 at 05:09:01AM +0400, Manu Abraham wrote:
> Hi,
>
> I get this error on booting up 2.6.20 (Similar error on 2.6.17.7 also,
> the message is slightly different in 2.6.17.7)
>
> PCI Cannot allocate resource region 2 of device :02:0a.0
> PCI Error while updating region 000:02
On 2/5/07, Luming Yu <[EMAIL PROTECTED]> wrote:
On 2/5/07, Manu Abraham <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I get this error on booting up 2.6.20 (Similar error on 2.6.17.7 also,
> the message is slightly different in 2.6.17.7)
>
> PCI Cannot allocate resource region 2 of device :02:0a.0
Jus
Luming Yu wrote:
* Known BIOS problems we have to work around:
* - bogus I/O addresses above 64K used
On non-x86 architectures this might be just fine.
-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Mo
On 2/5/07, Manu Abraham <[EMAIL PROTECTED]> wrote:
Hi,
I get this error on booting up 2.6.20 (Similar error on 2.6.17.7 also,
the message is slightly different in 2.6.17.7)
PCI Cannot allocate resource region 2 of device :02:0a.0
Just did a search about this message around the kernel sourc
27 matches
Mail list logo
