Florin Andrei:
On Fri, 2004-07-23 at 06:55, Dave Griffiths wrote:
>> Before the gig I went through my cron jobs commenting them all out just in
>> case. slocate is particually annoying - I guess most people disable this
>> anyway - even with jack using such a large buffer, all the disk access caused
>> problems.
>
>slocate is always among the first packages i remove after installing a
>system. Have no use for it, and it is very annoying.
I do a more general approach; turn off all cron-jobs if anyone is logged
in.
After installation, this script is run:
"
if grep "run-parts " >/dev/null /etc/crontab ; then
cp -f /etc/crontab /etc/crontab.org
sed s/run-parts\ /run-parts2\ / </etc/crontab.org >/etc/crontab
echo "crontab changed"
fi
if grep "run-parts " >/dev/null /etc/anacrontab ; then
cp -f /etc/anacrontab /etc/anacrontab.org
sed s/run-parts\ /run-parts2\ / </etc/anacrontab.org >/etc/anacrontab
echo "anacrontab changed"
fi
"
and /usr/bin/run-parts2 looks like this:
"
#!/bin/bash
if ! ps -A |grep ssh-agent ; then
run-parts $@
fi
"
At least this works for fedora core 1. Don't know about other
distributions.
--
I rebuilt the latest Fedora 2 kernel update to enable preempt and
IO-APIC.
I'm not yet sure about preempt, but IO-APIC has been acting weird.
It gave me more interrupts (up to 21 instead of 15), but the devices
were distributed suboptimal.
Without APIC, the nvidia module was alone on its own interrupt, the
EMU10K1 was alone, the ide and eth modules were on separate interrupts,
etc. Quite ok.
With IO-APIC, nvidia, EMU10K1 and bttv were on the same interrupt, ide2,
ide3 and eth0 were on the same interrupt.
Instead of messing with the kernel again, i just rebooted with the
"noapic" parameter and now the interrupts are looking good again.
BTW, anyone has any measurements on how bad it is to put essential
devices on the same interrupt? (in terms of xruns)
--
Florin Andrei
http://florin.myip.org/
->I run almost the same setup, except I have a Asus A7N8X mobo with
the Athlon 2500 overclocked to 2100Mhz @ 200Mhz fsb on Fedora with the
CCRMA 2.4.26-1.ll kernel. The problem I always run into is that my
setup will not run the low latency (ll) "athlon" kernel without locking
up like you described. I have found that if I manually install the i686
kernel and ALSA from the CCRMA rpms, it will boot just fine and is very
stable. In other words don't use apt-get to install the kernel and ALSA
because it will always pick the Athlon versions. I haven't found any
problems using apt-get after the kernel,alsa rpm installation, although
when a new kernel comes out you do have to install it manually.<-
Thanks to everyone who responded. My friend Kevin Ernste pointed me to
one of many forum threads which talk about using "noapic nolapic" (hey,
that's a good rhyme!) as kernel arguments for the nforce2 chipset. Like
this one:
http://www.linuxquestions.org/questions/showthread.php?s=&postid=1035056#po…
I did that early this morning (actually, I just passed nolapic so far),
and have not had a single problem at the normal clock speed, throwing
everything I could at it. I had qjackctl open running alsaplayer into a
simple jack-rack amplifier into freqtweak into a rezound record, while
burning a CD, encoding an mp3, and playing with Celestia. Aside from
Celestia and the mp3 encoder being fairly slow and the cpu temp reaching
41C during that episode, everything seems pretty solid.
Thanks,
Matt
Hello guys,
I'm writing here because I have a large sample of a Mellotron that I have
not time to convert to pat or sf2. Inside there are the 3 instruments of a
real Mellotron sampled note by note (I guess).
The author of the samples, a friend of mine, when asked said that we can
use it like we did with the rhodes one that he made
(http://www.yeeking.net/index.php?location=Sound%20Fonts), making a GPL
sound font or gus patch (he's asking only a mention of his website on the
README)
Since the sample is 23 Mb, and I don't have so much bandwidth, I can make
it available on my home pc to the ones that are really interested. You can
reach me via email or on irc on #agnula #lad or #hydrogen (nick "emillo")
Ciao
--
Emiliano Grilli
Linux user #209089
http://www.emillo.net
->Something just hit me while reading this post again, check the
CPU speed jumper on your mobo. It needs to be at 133/166mhz for stock
operation or 100mhz if your trying to run at 200mhz fsb (overclocking)<-
Don't think so. I have set the clock to 200mhz in the BIOS. When I
removed the clock jumper (which is how you set it to 100mhz) it won't go
any higher even if you tell it to in the BIOS. The BIOS goes up in
single mhz to 300.
M
Hiya.
I use Beyer DT150 headphones. They are solid, repairable, and have a
better bass end than the old DT100.
They are closed, but this can be a good thing as you get less spill from
the headphones onto the mic than with open cans+less level is needed.
You can blow them up, but it's pretty hard, and the drivers are not too
expensive to replace. The old DT100 was a bit of an industry standard,
and the DT150 looks likely to follow in it's footsteps.
This might not be an appropriate place to ask this question, but I've
gotten help here before on a number of things...
So I have an Athlon XP 2500+ and a DFI motherboard with the nvidia
nforce2 chipset. I have run it for almost a year, and it has been rock
solid under linux (not as much under Windows), red hat 9 and planet
ccrma kernel/drivers/software -- 2.4.26-1.ll.rh90.ccrma. RME hdsp
multiface, and um... 2x512MB Crucial unbuffered DDR400. Great, except -
I have never been able to set the appropriate bus clock in the BIOS
without linux becoming COMPLETELY unstable. If I set it to the
published specs (166Mhz bus, x11 multiplier == 1.83Ghz), I usually can't
even get through the linux boot process; if it makes it through the boot
process, it will usually hang at the NVIDIA screen, or at the signin...
if it makes it past that, I can sign in, do a few things in a shell, but
then after about 2 minutes at most, the system freezes. And we're
talking about a hard freeze - no ctl-alt-del, no ctl-alt-backspace, no
response at all. Windows runs as fine as it ever has. The only way I
can get linux to run stably is to underclock the system at 100Mhz, which
puts my CPU clock at a wimpy 1.1Ghz. Setting the multiplier higher than
11 but maintaining the 100Mhz bus clock results in the same problem. I
thought for a moment that the memory clock and the bus clock weren't
syncing, so I set them in 1:1 ratio - linux still hates it at any
frequency. You can lock AGP at 66Mhz, still nothing doing. This is a
board and proc combo that has been renowned for mega overclocking - I
shouldn't have to underclock it to have things run right. Windows runs
fine so I'm wondering if it's not a problem in my kernel or distro
rather than the bios or hardware. I have not as yet tried to boot
another kernel, but I will tomorrow when my mind is clear (I just
started trying to fix it today, and I'm weary). Any ideas about it, or
about where I could read to fix it?
Thanks, Matt