Re: bttv problems in 2.4.0/2.4.1
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 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 other stupid things like hang abruptly for no apparent reason. -- -Matt If you suspect a man, don't employ him. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: bttv problems in 2.4.0/2.4.1
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 off when ACPI was loaded. Other times it would > do other stupid things like hang abruptly for no apparent reason. My video card isn't really supported by the framebuffer stuff, at least not for accelleration, so I don't have framebuffer support. I have been experiencing abrupt hangs recently too ... -- -Matt If you suspect a man, don't employ him. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: bttv problems in 2.4.0/2.4.1
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. 2 questions: What card in particular do you have? What version of the bttv drivers were you using in 2.4.0-test10? It comes with 0.7.38; did you patch it to a higher version? -- -Matt Today's weirdness is tomorrow's reason why. -- Hunter S. Thompson - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: bttv problems in 2.4.0/2.4.1
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 bttv 0.7.47, which works fine. > > > > 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 different slot. A lot of the cards > exceptionally do not like IRQ/DMA sharing, and a lot of the motherboards > share them between different slots. I will try this, but my card has (and does) worked with irq sharing for a long time. Its entry in /proc/interrupts: 9: 164935 165896 IO-APIC-level acpi, bttv I find it strange that a driver that had worked with shared interrupts for a long time would suddenly cease to function with shared interrupts, and would consider this a bug. I will try changing the slot, but getting it to not share interrupts will be difficult considering the number of pci devices I have. -- -Matt Today's weirdness is tomorrow's reason why. -- Hunter S. Thompson - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
bttv problems in 2.4.0/2.4.1
In 2.4.0 and 2.4.1, when I try to load the bttv driver, one of two things happens: the system hangs (even alt-sysrq doesn't work!), or the system powers off by itself (ATX mobo). Instant power-off usually happens after a soft reboot (init 6), while it usually hangs up after a hard reboot (power cycling). When it hangs, I noticed a very strange thing. If I push the power on/off button briefly, it un-hangs and seems to proceed as normal. The kernel does report an APIC error on each cpu (dual p3 700 system) when this happens. 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 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. PS: I'm not on the linux-kernel list, so please CC replies to me. -- -Matt Today's weirdness is tomorrow's reason why. -- Hunter S. Thompson - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
ppa driver failure in 2.4.0-test8 (fwd)
I sent this to the maintainer of the ppa driver some time ago, and have received no response. Please CC me on replies, I'm not on the list. -- -Matt SNAPPY REPARTEE: What you'd say if you had another chance. -- Forwarded message -- Date: Sat, 16 Sep 2000 20:40:26 -0400 (EDT) From: Matthew Gabeler-Lee <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: ppa driver failure in 2.4.0-test8 I have a relatively old ZIP drive (well back into the ppa era). I recently upgraded to 2.4.0-test8 from 2.4.0-test7, and the ppa driver now no longer seems to work properly. When I load the drier, the following gets put in the syslog: kernel: ppa: Version 2.05 (for Linux 2.2.x) kernel: ppa: Found device at ID 6, Attempting to use EPP 32 bit kernel: ppa: Communication established with ID 6 using EPP 32 bit kernel: scsi1 : Iomega VPI0 (ppa) interface kernel: scsi : 2 hosts. At this point, the system hangs up pretty bad. Alt-PrtScn stuff to set the console log level reveals that there is an infinite series of "Detected scsi disk sdXX", where it keeps incrementing the XX through all the letters, and into punctuation, etc. -- -Matt You can't have everything. Where would you put it? -- Steven Wright - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
