From: klink@clouddancer.com (Colonel)
To: linux-kernel@vger.kernel.org
Cc: Dylan_G@bigfoot.com
Subject: Re: Annoying kernel behaviour
Date: Sat, 23 Jun 2001 02:05:42 -0700 (PDT) [thread overview]
Message-ID: <20010623090542.6019D7846F@mail.clouddancer.com> (raw)
In-Reply-To: <9h0r6s$fe7$1@ns1.clouddancer.com>
In-Reply-To: <3B33EFC0.D9C930D5@bigfoot.com> <9h0r6s$fe7$1@ns1.clouddancer.com>
In clouddancer.list.kernel, you wrote:
>
> I upgraded a fileserver to 2.4.5 because of the RAID support (the 0.90
>patch I grabbed did not apply cleanly to 2.2.19, despite it being a fresh
>copy).
Look in the people/mingo directory for a patch
> Besides a nice speed increase (the EEPro now pumps 10 megs a second,
>instead of 2 or 3), there is a problem with the video4linux in it. The box
>has a bttv card hooked up to a camera. Under 2.2.19, Apache had mod_video
>installed, which would produce a jpeg of the composite in on the card (a
>cheapy CCD camera is hooked up). Upon insmoding:
I have:
Linux video capture interface: v1.00
bttv: driver version 0.7.63 loaded
bttv: using 2 buffers with 2080k (4160k total) for capture
bttv: Host bridge needs ETBF enabled.
bttv: Bt8xx card found (0).
bttv0: Bt878 (rev 2) at 00:0b.0, irq: 10, latency: 32, memory: 0xe3000000
bttv0: subsystem: 144f:3000 => TView 99 (CPH063) => card=38
bttv0: model: BT878(TView99 CPH063) [autodetected]
bttv0: enabling ETBF (430FX/VP3 compatibilty)
i2c-core.o: adapter bt848 #0 registered as adapter 0.
working in 2.4.5-ac12 SMP+RAID. I used
Bttv-0.7.63-2.4.3.patch.bz2
from the website. Video4linux has always worked in the various 2.4
kernels I've tried.
>and accesing mod_video, the box locked up hard (not even sysrq worked). And
I don't run mod_video, but xawtv works fine. Did you try that or
rebuilding mod_video?
>when I rebooted, I found that some files is /etc were eaten -- even though
You must have grues.
--
"Or heck, let's just make the VM a _real_ Neural Network, that self
trains itself to the load you put on the system. Hideously complex and
evil? Well, why not wire up that roach on the floor, eating that stale
cheese doodle. It can't do any worse job on VM that some of the VM
patches I've seen..." -- Jason McMullan
ditto
next prev parent reply other threads:[~2001-06-23 9:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-23 1:24 Annoying kernel behaviour Dylan Griffiths
[not found] ` <9h0r6s$fe7$1@ns1.clouddancer.com>
2001-06-23 9:05 ` Colonel [this message]
2001-06-24 10:37 ` Dylan Griffiths
[not found] ` <9h4ft5$1ku$1@ns1.clouddancer.com>
2001-06-24 11:46 ` Colonel
2001-06-24 19:46 ` Dylan Griffiths
[not found] ` <9h5gbc$3mb$1@ns1.clouddancer.com>
2001-06-25 3:22 ` Colonel
2001-06-25 7:41 ` Gerd Knorr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010623090542.6019D7846F@mail.clouddancer.com \
--to=klink@clouddancer.com \
--cc=Dylan_G@bigfoot.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox