22 Jul
2008
22 Jul
'08
1:19 p.m.
On Tuesday 22 July 2008 17:49:28 Emanuel Rumpf wrote:
2008/7/22 David Baron <d_baron(a)012.net.il>il>:
Actually, without that link, I get:
Trying RTC timer...
fatal error: open /dev/rtc failed: No such file or directory
Trying ALSA timer...
got timer = 20
starting with default template
showMarker 0
3set realtime scheduler: Operation not permitted
With the symlink I get.
Trying RTC timer...
got timer = 20
starting with default template
showMarker 0
3set realtime scheduler: Operation not permitted
So nothing is really different. How do I get the realtime scheduler? The
rlimits is for the audio group to have that!
Also get
watchdog process 7192 _NOT_ running SCHED_FIFO
OK, but that "enhanced realtime clock
support is menued as "new". The
rtc.c does hpet refences.
Snd-rcttimer will not be built this way.
That's what I said. I don't have it.
But which/what is using/requiring snd-rtctimer btw?
The question is will muse run without
snd-rtc-timer.
yes
but create a link:
ln -s /dev/rtc0 /dev/rtc
for the new rtc-device, so that muse can find it.
2008/7/22 David Baron <d_baron(a)012.net.il>il>:
I can try that when I have time to let that go on again!
Something else I just noticed in the kernel
builds:Section mismatches! 24
in image and 9 in the modules.
maybe the build is not clean
have you run
make-kpkg clean
??
I have sometimes had problems
that "make clean" could not remove.
Starting with fresh sources
and a known working config
helped in most cases.