On Sunday 25 June 2006 16:00, Rich Kadel wrote:
> Hans - Thanks for the reply. Answers below...
>
> --
>
> Rich Kadel
> Know'bout, Inc.
> (858) 433-1747
> www.knowbout.com
>
> Do you know about Know'bout?
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
>
> [mailto:[EMAIL PROTECTED] On Behalf Of Hans Verkuil
>
> > Sent: Sunday, June 25, 2006 5:33 AM
> > To: Discussion list for development of the IVTV driver
> > Subject: Re: [ivtv-devel] System hangs loading driver modules for
> > PVR-500
> >
> > On Sunday 25 June 2006 08:57, Rich Kadel wrote:
> > > OK. I tried upgrading to the new 0.4.6 drivers (not that I
> > > expected a miracle since the change log didn't mention anything
> > > about fixing my problem).
> > >
> > > Still no luck.
> > >
> > > The PVR-250 still works fine, but as soon as I put the 500 in
> > > there, it locks up (now right at the start of the boot phase,
> > > when it says something like "probing hardware: something,
> > > something, audio" (I think.should have written it down).
> > >
> > > Anyway, some more details on my setup:
> > >
> > > Dell 2850, Dual Core Xeon processors, Intel E7520 chipset,
> > >
> > > One Dual Core IntelR XeonT Processor, 2x2MB Cache, 2.8GHz, 800MHz
> > > FSB
> > >
> > > 4GB RAM
> > >
> > > 3 PCI-X slots.
> > >
> > > And one other tidbit I referred to earlier. The front of the
> > > server has a status LCD. When the system fails, it goes from
> > > blue to amber. And in my case, when it locks up from the PVR-500,
> > > the message says:
> >
> > Hi Rich,
> >
> > I need some information first before I start to look into this.
> >
> > 1) The PVR250 works fine in a PCI-X slot, correct? You say it was
> > modified: do you know what was modified? Hauppauge did the
> > modification? My guess would be that the modification was to make
> > it work at 3.3V instead of 5V.
>
> Yes, Hauppauge did the modification of the PVR-250. I found a
> discussion on the net about this, and learned that you can either
> send Hauppauge and existing PCI card or just order it direct from
> Hauppauge. I don't know for sure what they modified, but rumor was
> it was to swap out one chip, and yes, that probably also made it work
> at 3.3V if it didn't already.
>
> > 2) Can you confirm that the same PVR500 works in a PCI-X slot with
> > the same hardware under Windows?
>
> I can't confirm that my PVR500 works in PCI-X (I don't have another
> machine with PCI-X to test it). But a Hauppauge engineer told me
> directly that the PVR-500 does not require modification to work in
> PCI-X (the PVR-150 and 250 do).
>
> The other thing is, until recently, the system WAS at least booting
> all the way up, and lspci -v was showing 2 normal-looking entries for
> the PVR-500's 2 tuner units. So at least the hardware was
> recognizing the card. (This gave me a false sense of confidence ;-)
>
> Now, however, the system locks up during boot with the PVR-500. It
> stops at:
>
> Starting udev: [OK]
> Initializing hardware... storage network audio
>
> It pauses for 30 seconds or so, and then the status light goes amber.
So this is before the ivtv driver is even loaded? If you remove the ivtv
driver and then restart the computer, does it still have problems
booting? In that case it certainly is not related to the ivtv driver
and you might look at BIOS and kernel updates.
>
> Can you tell me what it's doing with the card that early in the boot
> that I might have messed up?
Assuming that the hang is during the card initialization in the ivtv
driver, my guess is that it is either a hardware issue or something to
do with the PCI/DMA setup. But in that case I'd expect problems with
the PVR250 also.
> I'm guessing I installed some part of the driver that gets executed
> this early in the boot cycle (hotplug stuff? I don't know enough
> about the kernel to know what to undo here). I'd like to at least
> get it to boot up with the 500 installed so I can try to step through
> the driver install in debug or put some printlns in right after the
> firmware load, since that's the last message that went into the logs
> when it was getting that far.
>
> > 2) is of course the most important to know. This would confirm that
> > it is indeed a software issue and not a hardware issue. I tried to
> > google but I was unable to find any article that confirms a PVR500
> > working in a PCI-X slot, nor am I aware of anything that needs to
> > be done in the driver to make it work with PCI-X.
> >
> > I do know that the PVR500 has problems with certain kinds of
> > hardware/BIOS versions. For example, if I put my PVR500 in my AMD64
> > Asus server, then the server won't even boot.
> >
> > The ultimate test for these kinds of problems is always testing it
> > under Windows.
>
> Yes, unfortunately that would be a challenge for me too though. I am
> just about to deploy this server and don't have the budget for a
> second experimental one at this time.
Can't you swap out harddisks? And put Windows on the new disk?
I really first need proof that it works under Windows before I'm going
to spend time on this. And the first step would be to put printk's in
the driver (ivtv-driver.c) and see where it breaks down. Also note that
I expect to have little time for this anyway in the next two weeks.
Hans
> I can call Hauppauge again on Monday and ask if they've had any
> successes or issues, but I've already been told by their sales dept.
> that they don't support anything but Windows.
>
> > Regards,
> >
> > Hans
>
> _______________________________________________
> ivtv-devel mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
