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: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
> >ParErr- Stepping- SERR- FastB2B-
> >> > > Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> ><TAbort- <MAbort- >SERR+ <PERR+
> >> > > Latency: 0, Cache Line Size 0c
> >> > > BIST is running
> >> >
> >> > BIST is required to complete in 2 seconds. Either with success or
> >failure.
> >> > I expect BIOS to have complained before launching grub/lilo.
> >>
> >> Gregkh,
> >> I just realized linux-pci bus scan should ignore devices (print a
> >warning)
> >> which have BIST set. Want a patch for this?
> >>
> >> Slight risk some previously "working" device which violates the
> >> spec might get ignored...but I hope there aren't too many of those.
> >
> >Should we wait two seconds before declaring the device dead? To see
> >whether
> >it will come back?
> >
>
>
> Wonders !
>
> I was about to give the card it's last rites. I thought well let me
> try under the other OS
Could you be more specific? Which OS? FreeBSD? :)
> I didn't have any drivers for the same, since the demodulator driver
> doesn't exist in the other OS also, but the bridge device does have
> the driver.
>
> I plugged the card in, the OS searched for drivers, since i didn't
> have any didn't load any..
> So it went under a question mark.
>
> Looking under Resources,
>
> It showed the PCI information string like this ..
>
> PCI\VEN_1822&DEV_4E35&SUBSYS_00311822&REV_01\4&2E98101C&0&10F0
>
> then i thought try with the driver eventhough support for the
> demodulator doesn't exist ..
>
> Downloaded and installed drivers ..
>
> Lo ..!
>
> Memory Range: F87FF000 - F87FFFFF
> IRQ : 17
>
> it got assigned a memory region indeed.
Excellent.
> So, to wrap it up, the device is not dead .. We have something wrong
> in the PCI subsystem probably.
Hrm maybe but not likely. I'm more inclined to believe PCI subsystem
is missing hacks needed for that device and/or BIOS.
grant
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
