Disabling ACPI (all of power management, really. SMP so no APM) seems
to have made it work in 2.4.1 for me.
On Fri, 9 Feb 2001, Dr. Kelsey Hudson wrote:
> Do you have framebuffer console compiled into your kernel? I noticed
> similar behavior on my system when I had framebuffer console
On Fri, 9 Feb 2001, Dr. Kelsey Hudson wrote:
> Do you have framebuffer console compiled into your kernel? I noticed
> similar behavior on my system when I had framebuffer console compiled in,
> ACPI or APM (cant remember which, probably ACPI) compiled in, and bttv as
> modules. System would
Do you have framebuffer console compiled into your kernel? I noticed
similar behavior on my system when I had framebuffer console compiled in,
ACPI or APM (cant remember which, probably ACPI) compiled in, and bttv as
modules. System would power off when ACPI was loaded. Other times it would
do
Do you have framebuffer console compiled into your kernel? I noticed
similar behavior on my system when I had framebuffer console compiled in,
ACPI or APM (cant remember which, probably ACPI) compiled in, and bttv as
modules. System would power off when ACPI was loaded. Other times it would
do
On Fri, 9 Feb 2001, Dr. Kelsey Hudson wrote:
Do you have framebuffer console compiled into your kernel? I noticed
similar behavior on my system when I had framebuffer console compiled in,
ACPI or APM (cant remember which, probably ACPI) compiled in, and bttv as
modules. System would power
Disabling ACPI (all of power management, really. SMP so no APM) seems
to have made it work in 2.4.1 for me.
On Fri, 9 Feb 2001, Dr. Kelsey Hudson wrote:
Do you have framebuffer console compiled into your kernel? I noticed
similar behavior on my system when I had framebuffer console compiled
ok!!
archan
[EMAIL PROTECTED]
[EMAIL PROTECTED]
John Jasen wrote:
> On Wed, 31 Jan 2001, archan wrote:
>
>> I am using "Pixel View TV tuner card" based on "bttv". It works perfect
>> in Windows with default TV application, and also responding well in
>> Linux 2.2.17 and 2.4.0-test10 kernel.
On 31 Jan 2001, Gerd Knorr wrote:
> > The card is a video only capture that came with a camera (and has a
> > connector to power that camera next to the video connector).
>
> Sure the box is really dead? These very cheap cards with just the bt848
[snip]
> some sanity checks on the i2c bus
> The card is a video only capture that came with a camera (and has a
> connector to power that camera next to the video connector).
Sure the box is really dead? These very cheap cards with just the bt848
and nothing else often have a non-working i2c bus (because they have no
chips connected to
My bttv is at IRQ 3 and it still hangs the machine :(
I dont even have acpi built in.
btw I am testing with 2.4.1-pre9
--
Prasanna Subash --- [EMAIL PROTECTED] --- TurboLinux, INC
Linux, the choice |
On Wed, 31 Jan 2001, archan wrote:
> I am using "Pixel View TV tuner card" based on "bttv". It works perfect
> in Windows with default TV application, and also responding well in
> Linux 2.2.17 and 2.4.0-test10 kernel. The device is getting detected
> perfectly by 2.4 kernel but I could not be
On Tue, 30 Jan 2001, Matthew Gabeler-Lee wrote:
> On Tue, 30 Jan 2001, adrian wrote:
>
> >I have a bt848 based video capture card, and get near the same results:
> > 2.4.0-test10 through 2.4.1 all lock when i2c registers the device. The
> > card has its own interrupt. With 2.2.18, the
I am using "Pixel View TV tuner card" based on "bttv". It works perfect
in Windows with default TV application, and also responding well in
Linux 2.2.17 and 2.4.0-test10 kernel. The device is getting detected
perfectly by 2.4 kernel but I could not be able to check whether the
card in 2.4
> > > I have sent all this info to Gerd Knorr but, as far as I know, he hasn't
> > > been able to track down the bug yet. I thought that by posting here,
> > > more eyes might at least make more reports of similar situations that
> > > might help track down the problem.
> >
> > Try flipping the
I have sent all this info to Gerd Knorr but, as far as I know, he hasn't
been able to track down the bug yet. I thought that by posting here,
more eyes might at least make more reports of similar situations that
might help track down the problem.
Try flipping the card into a
On Tue, 30 Jan 2001, Matthew Gabeler-Lee wrote:
On Tue, 30 Jan 2001, adrian wrote:
I have a bt848 based video capture card, and get near the same results:
2.4.0-test10 through 2.4.1 all lock when i2c registers the device. The
card has its own interrupt. With 2.2.18, the card
On Wed, 31 Jan 2001, archan wrote:
I am using "Pixel View TV tuner card" based on "bttv". It works perfect
in Windows with default TV application, and also responding well in
Linux 2.2.17 and 2.4.0-test10 kernel. The device is getting detected
perfectly by 2.4 kernel but I could not be able
My bttv is at IRQ 3 and it still hangs the machine :(
I dont even have acpi built in.
btw I am testing with 2.4.1-pre9
--
Prasanna Subash --- [EMAIL PROTECTED] --- TurboLinux, INC
Linux, the choice |
The card is a video only capture that came with a camera (and has a
connector to power that camera next to the video connector).
Sure the box is really dead? These very cheap cards with just the bt848
and nothing else often have a non-working i2c bus (because they have no
chips connected to
On 31 Jan 2001, Gerd Knorr wrote:
The card is a video only capture that came with a camera (and has a
connector to power that camera next to the video connector).
Sure the box is really dead? These very cheap cards with just the bt848
[snip]
some sanity checks on the i2c bus first
On Tue, 30 Jan 2001, adrian wrote:
>I have a bt848 based video capture card, and get near the same results:
> 2.4.0-test10 through 2.4.1 all lock when i2c registers the device. The
> card has its own interrupt. With 2.2.18, the card initialized and the
> kernel continued to boot.
Hmmm,
I have a bt848 based video capture card, and get near the same results:
2.4.0-test10 through 2.4.1 all lock when i2c registers the device. The
card has its own interrupt. With 2.2.18, the card initialized and the
kernel continued to boot. Interesting.
Regards,
Adrian
On Tue, 30
I have experienced similar issues with 2.4.0 and its test. I have a bttv848 chipset.
I even tried compiling in kdb as a part of the kernel to see if it oopses, but no luck.
I will try trying 0.7.47 today.
this works on 2.2.16, last time i tried.
--
Prasanna Subash --- [EMAIL PROTECTED]
On Tue, 30 Jan 2001, John Jasen wrote:
> On Tue, 30 Jan 2001, Matthew Gabeler-Lee wrote:
>
> > These errors all occur in the same way (as near as I can tell) in
> > kernels 2.4.0 and 2.4.1, using bttv drivers 0.7.50 (incl. w/ kernel),
> > 0.7.53, and 0.7.55.
> >
> > I am currently using
On Tue, 30 Jan 2001, Matthew Gabeler-Lee wrote:
> These errors all occur in the same way (as near as I can tell) in
> kernels 2.4.0 and 2.4.1, using bttv drivers 0.7.50 (incl. w/ kernel),
> 0.7.53, and 0.7.55.
>
> I am currently using 2.4.0-test10 with bttv 0.7.47, which works fine.
>
> I have
On Tue, 30 Jan 2001, Matthew Gabeler-Lee wrote:
These errors all occur in the same way (as near as I can tell) in
kernels 2.4.0 and 2.4.1, using bttv drivers 0.7.50 (incl. w/ kernel),
0.7.53, and 0.7.55.
I am currently using 2.4.0-test10 with bttv 0.7.47, which works fine.
I have sent all
On Tue, 30 Jan 2001, John Jasen wrote:
On Tue, 30 Jan 2001, Matthew Gabeler-Lee wrote:
These errors all occur in the same way (as near as I can tell) in
kernels 2.4.0 and 2.4.1, using bttv drivers 0.7.50 (incl. w/ kernel),
0.7.53, and 0.7.55.
I am currently using 2.4.0-test10 with
I have experienced similar issues with 2.4.0 and its test. I have a bttv848 chipset.
I even tried compiling in kdb as a part of the kernel to see if it oopses, but no luck.
I will try trying 0.7.47 today.
this works on 2.2.16, last time i tried.
--
Prasanna Subash --- [EMAIL PROTECTED]
Hmmm,
I have a bt848 based video capture card, and get near the same results:
2.4.0-test10 through 2.4.1 all lock when i2c registers the device. The
card has its own interrupt. With 2.2.18, the card initialized and the
kernel continued to boot. Interesting.
Regards,
Adrian
On Tue, 30
On Tue, 30 Jan 2001, adrian wrote:
I have a bt848 based video capture card, and get near the same results:
2.4.0-test10 through 2.4.1 all lock when i2c registers the device. The
card has its own interrupt. With 2.2.18, the card initialized and the
kernel continued to boot. Interesting.
30 matches
Mail list logo