-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
just short little experiments for now, but more coming:
http://www.restivo.org/blog
Supposedly this will work in iTunes, though I haven't booted into OSX recently to check it:
feed:http://www.restivo.org/blog/?feed=rss2&cat=2
The answers to some of the inevitable technical questions are here:
http://www.restivo.org/blog/?page_id=14
Though most of you-all probably already know the answers :-)
- -ken
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFFkz5Ue8HF+6xeOIcRAnvFAKCoouZJBlEsXnSQrjPd0Qzf5J3DvACgtReS
vHx0J/1RKdfonj5KrgaxkJw=
=cDFP
-----END PGP SIGNATURE-----
Thanks for the replies about the latest realtime kernel. I
was considering updating from the version I'm now using
(2.6.16-rt26) because I'm planning to install a TV card
(probably a Philips SAA7134 chipset), and I wanted to get
the best available support for it.
I take the point about not updating unless it's necessary,
but if I do need to, is there an ebuild (for Gentoo) for a
patched kernel more recent than mine?
Peter C
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
*sigh*, also having a hard time locating the dyne:bolic kernel sources.
So far, dyne:bolic is the only working realtime kernel I've found that will actually:
a) boot on my Mac Mini,
b) recognize and correctly operate the hda-intel card on the Mac Mini, and,
c) contain realtime ingo patches
But, I don't want/need/like all the dyne:bolic stuff, I use debian. I just need the kernel. Luckily it's GPL, so the sources should be somewhere, I just have to find out where.
Their website appears to be down right now.
Any ideas?
- -ken
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFFk1vTe8HF+6xeOIcRAhBWAJ9BR77LAQNretLEroJ7OGaSSIu3zgCfZagO
jkBey1xP15JtpCd7nEVf/f8=
=shRa
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
There doesn't appear to be a kernel-source-2.4.18 package in 64studio.
Any idea where I could get the source for the 64studio kernel?
- -ken
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFFk0LUe8HF+6xeOIcRAuwlAJ9RJ7+LlrVn65HZQ97SsWofjLIYHwCg9sze
a8IRvQzmdudhQiOLduqbxiE=
=ejPE
-----END PGP SIGNATURE-----
October:
>>
>> On Thu, Dec 21, 2006 at 10:39:30AM -0500, Dave Phillips wrote:
>>> Greetings;
>>>
>>> I'm happy as a clam in mud with my new machine, but it's developed a
>>> problem. I purchased an inexpensive nVidia-based card that's starting to
>>> behave poorly. I think the hardware itself is buggy, the display will
>>> sometimes shudder rapidly side-to-side, blurring the screen view.
>>> Sometimes it stops and stays stopped, other times it goes on until I
>>> have to reboot. The problem doesn't appear to be a heating problem, but
>>> I've decided to go for a much better card anyway.
>>>
>>> So, I want an nVidia-based card with 256 MB video RAM and a decent
>>> cooling fan, preferably under $200. Any recommendations ?
>>>
>>> Best,
>>>
>>> dp
>>
>> I've been happy so far with a Gigabyte GV-NX66256DP2, based on the
>> GeForce 6600. It's PCI-Express. Not a high-end card at all, it cost
>> $95 in April 2006, but so far works flawlessly, and it's fanless.
>>
>
> I have a 6600LE card, but I'm unable to run at higher resolution than
> 1024x786 with the nv driver. Can you do that?
>
> That will also depend on what monitor you are running and how it is
> configured in X.
Hmm, well. I have tried various things, and most of it works with the
nvidia driver, but nothing have so far worked with the nv driver.
> I've got an old ViewSonic A90 19" and a 6600GT that by
> default will run 1280x1024 @ 85Hz with the "nv" driver.
>
Thats impressive. I have googled around, have never not seen anyone
succeeding running a 6600 chipset with 1280x1024 using the nv driver
(many people compaining though).
Please mail me your /etc/X11/xorg.conf file and the output of "uname -a".
That information might help the author of the nv driver to get it into
shape.
amSynth version 1.2.0 is now available!
Changes in this release:
-----------------------------------
+ nicer graphics (including new knob graphics)
+ fixed crash upon startup on some machines
+ handle all notes off midi message
+ new about dialog
+ improved per-user installation process
http://downloads.sourceforge.net/amsynthe/amSynth-1.2.0.tar.gz
/nixx
What's the current status of the realtime-enabled kernel?
Up till now I've been using the patched 2.6.16-rt26 on an
i686. I just re-synced my Gentoo packages list and found
that the latest standard kernel is 2.6.19-r2. I'm using
rezound and muse with JACK. Do I still need to use a
patched kernel - or has the necessary realtime capability
found its way into the mainstream kernel? If so, I guess I
would still need the realtime module. Is this correct?
Thanks,
Peter C
Greetings:
My ancient 800 MHz machine has dead PS/2 ports so I plugged my mouse and
keyboard into its available USB ports. Alas, the keyboard disappears
after selecting my kernel image (Demudi) in grub. I'm away from the
machine right now so I don't have the exact text of the error message.
However, I do recall that it refers to a USB-related IRQ error.
I tried to install the 32-bit version of 64Studio, but the error occurs
during the configuration process: As soon as I press Enter at the boot
prompt the keyboard is no longer present to the system. :(
I Googled for some more information regarding the problem and found that
it is in fact a known issue. However, none of the proposed solutions
worked for me. I also sent messages to the 64Studio dev list and to Free
and Daniel, but I've heard nothing back from them or the list (I think
my email to the list isn't getting there).
One thing does work: Dynebolic includes a nohid boot parameter that does
the trick ('linux nohid'), so I can still boot into the machine and
access my data. So, my question is: What's Dynebolic doing that the
other distros aren't ? I'd surely like to boot directly into my system,
and I'd like to install 32-bit 64Studio, but I can't do either until I
solve this problem.
Any suggestions ?
Best,
dp
Greetings:
Sometimes I like to use aplaymidi to playback MIDI files for recording
to Ardour or ecasound. Yesterday I noticed that the program was rushing
the first few milliseconds of playback when used to play a series of files :
aplaymidi *.mid
The MIDI data stream was directed to an external synth. The problem did
not occur when using another MIDI player (Seq+ in DOSemu).
Is this a known problem or is it unique to ALSA in the 2.6.18 kernel ?
I'm running 64Studio on AMD64 hardware. More details available if needed.
Best,
dp