From: watermodem <aquamodem@ameritech.net>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test4 on to mpegs and DVB
Date: Thu, 04 Sep 2003 19:23:18 -0500 [thread overview]
Message-ID: <3F57D776.4050404@ameritech.net> (raw)
In-Reply-To: <3F560DC6.2090709@ameritech.net>
Ok...
So I switched to the following suggested utilities:
module-init-tools-0.9.13-0.2bor.src.rpm
hotplug-2003_08_05-0.1bor.src.rpm
initscripts-7.06-18mdk.1bor.src.rpm
then did a merge on modprobe.conf/rpmnew and added one little directory
to the path in the sysinit file.
The printer is still hosed but I do see the usb tree under proc now.
Everything else needed excepting the BT848 card (i2 stuff and video)
probed and loaded. So I insmoded the rest to continue testing.
Mandrake will need to get their SUPERMOUNT working for DVDs, CDs and floppy.
Now for some performance reports. I have a server, in the basement,
with mp3s, mpegs and such being served via samba to the local net.
MP3's seemed to be ok but mpeg was awful. Now the local net is a 24
port switch that should be able to do 100mbits/full duplex (it does
under 2.4). So, to see if it was networking at fault (I, also, had to
switch to E100 as the eepro100 driver doesn't seem to work in 2.6), I
played a local DVD. The DVD looked and sounded great, but, it was using
98% of the CPU! 2.4 never used that much. I am wondering if the
timing in the dispatcher is a tad off for video or if the different
timeslices that are generated are not able to resonate with video
display/capture/frame frequencies. Should the timing for desktops tend
to have some sort of natural resonance with motion video display
critical timing? (lots of folks watch mpegs and dvi and dvd ...)
next prev parent reply other threads:[~2003-09-05 0:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 15:50 2.6.0-test4 watermodem
2003-09-03 19:36 ` 2.6.0-test4 Greg KH
2003-09-05 0:23 ` watermodem [this message]
2003-09-05 0:39 ` 2.6.0-test4 on to mpegs and DVB Andrew Morton
2003-09-05 1:52 ` watermodem
2003-09-05 2:17 ` tonildg
2003-09-05 20:22 ` watermodem
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=3F57D776.4050404@ameritech.net \
--to=aquamodem@ameritech.net \
--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