headers
EmaRsk | 2 Jul 2009 11:19
Picon

Ubuntu: "libasound2-plugins misses alsa pcm jack plugin"

Hi, regarding going from Debian to Ubuntu as a base for future 64
Studio releases, please be aware of Ubuntu's bug #84900
(https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/84900).
libasound2-plugins was migrated to main for pulseaudio, but because
jackd's source remains in universe, they cannot build
libasound2-plugins with jackd plugin support, according to Ubuntu's
policy.
This is a serious issue for an audio distro; 64 Studio will need its
own custom libasound2-plugins package, or a libasound2-plugins-extra
one with just the missing files.

--
Emanuele
Permalink | Reply | 0 comments |
headers
Ralf Mardorf | 4 Jul 2009 15:47

I build a package for Rubberband and wrote a HOWTO compile Qtractor CVS plus Rubberband (not only) for 64 Studio 3.0-beta3

Hi *developers* :)

maybe you want to use my package for Rubberband for the distro, I can 
copy and paste a description to the package and build it again, but I 
only know how to compile for amd64. For replies keep in mind, that I 
don't receive mails from the developers mailing list.

Hi *users* :)

unfortunately I couldn't build a package for today's [checkout at 
Jul/04/2009 14:00:00 CEST] CVS version of Qtractor, with complete 
featured functions, including VST support.

You can download the amd64 versions of Rubberband 1.3 as package from here:

    https://disc.alice-dsl.net/
    Username: ralf.mardorf@...
    Passwort: 64studio

First try to install the package by 'sudo dpkg -i PACKAGENAME' without 
running 'sudo ldconfig' in addition, if you get trouble run 'sudo ldconfig'.
Maybe you will compile Rubberband and Qtractor by yourself, it's 
recommended to do this at least for Qtractor from time to time, because 
Qtractor still is elementary, but under heavy development. There's no 
guarantee that my package and howto are fine and won't damage something, 
I didn't make tests, but I launched Qtractor and I guess that didn't 
damage my machine and didn't start eliminating the universe.

This is the howto for compiling Qtractor and Rubberband.
(Continue reading)

Permalink | Reply | 0 comments |
headers
salsaman | 4 Jul 2009 16:54
Picon
Picon
Favicon

Re: Including LiVES in 64 studio

On Mon, June 29, 2009 19:40, salsaman@... wrote:
> On Mon, June 29, 2009 17:18, Daniel James wrote:
>> Hi Salsaman,
>>
>>> I have mentioned this a couple of times before about including LiVES in
>>> 64
>>> studio - definately I would think it is something that our users would
>>> like to see.
>>
>> I totally agree, my only reservation has to do with software patents on
>> proprietary and MPEG video codecs.
>>
>> Cheers!
>>
>> Daniel
>>
>
>
> Then worry not. LiVES contains no proprietary codecs - it uses only
> external libraries for encoding/decoding.
>
> - If you have libmjpegtools installed, LiVES will compile against this,
> but in fact it uses only some enums internal to the library.
>
> - dv and ogg/theora are optionally supported by decoder plugins, but
> neither of these formats are patented.
>
> Cheers,
> Gabriel "salsaman",
> http://lives.sourceforge.net
(Continue reading)

Permalink | Reply | 0 comments |
headers
64 Studio | 12 Jul 2009 19:30
Favicon

Re: [64 Studio] #499: No disk drive detected error on install for Asus P5Q motherboard

#499: No disk drive detected error on install for Asus P5Q motherboard
---------------------------------+------------------------------------------
 Reporter:  daniel@...  |        Owner:  free      
     Type:  defect               |       Status:  new       
 Priority:  high                 |    Milestone:  3.0       
Component:  packages             |      Version:  3.0 beta 3
 Severity:  major                |   Resolution:            
 Keywords:                       |  
---------------------------------+------------------------------------------

Comment(by guido@...):

 Works for me. I own a P5Q Pro and had this problem installing 64studio
 2.1. Not 3.0 beta3. If this bug is the one described in this LKML thread:

 http://www.gossamer-threads.com/lists/linux/kernel/968813

 it is solved since version 2.6.27 of the kernel and so it is already fixed
 in 64studio 3.0.

--

-- 
Ticket URL: <http://trac.64studio.com/64studio/ticket/499#comment:1>
64 Studio <http://trac.64studio.com/64studio>
Permalink | Reply | 0 comments |
headers
64 Studio | 12 Jul 2009 19:48
Favicon

Re: [64 Studio] #479: Garbage in /var/lib/dbus/machine-id

#479: Garbage in /var/lib/dbus/machine-id
-------------------------------+--------------------------------------------
 Reporter:  guido@...  |        Owner:  free      
     Type:  defect             |       Status:  closed    
 Priority:  normal             |    Milestone:  3.0       
Component:  build              |      Version:            
 Severity:  blocker            |   Resolution:  worksforme
 Keywords:                     |  
-------------------------------+--------------------------------------------

Comment(by guido@...):

 I think I found the culprit.

 /var/lib/dbus/machine-id is not created during installation. It gets
 created during the first boot. But on my system, the boot sequence ends
 with gdm trying to start X and totally freezing the system, since I'm the
 lucky owner of a Radeon X1300 RV515 video card! At that time, the file
 holds uncommitted data.

 I managed to install without this problem, still using jfs.

 I suggest patching /etc/init.d/gdm so it issues a sync command before
 doing anything. This should save part of the trouble to those with badly
 supported video cards.

--

-- 
Ticket URL: <http://trac.64studio.com/64studio/ticket/479#comment:2>
64 Studio <http://trac.64studio.com/64studio>
(Continue reading)

Permalink | Reply | 0 comments |
headers
64 Studio | 12 Jul 2009 22:14
Favicon

[64 Studio] #502: RAID array does not start

#502: RAID array does not start
-------------------------------+--------------------------------------------
 Reporter:  guido@...  |       Owner:  free
     Type:  defect             |      Status:  new 
 Priority:  normal             |   Milestone:      
Component:  build              |     Version:      
 Severity:  normal             |    Keywords:      
-------------------------------+--------------------------------------------
 I fixed my 32-bit install of 3.0 beta3 by replacing a defective
 installation DVD. Now all is fine except this one (and maybe something
 with the video card).

 Shouldn't the kernel automatically create md* devices when it detects
 partitions which belong to a RAID? I keep data on a mirror of two IDE
 disks (which I connected after installation), and they are not detected.
 Moreover, when I issue "sudo dpkg-reconfigure mdadm" I get these errors
 (after the dialogs):

 Generating array device nodes... rm: cannot remove `md0-': Read-only file
 system
 mknod: `md0-': Read-only file system
 rm: cannot remove `md0-': Read-only file system
 rm: cannot remove `md1-': Read-only file system
 mknod: `md1-': Read-only file system
 rm: cannot remove `md1-': Read-only file system
 rm: cannot remove `md2-': Read-only file system
 mknod: `md2-': Read-only file system
 rm: cannot remove `md2-': Read-only file system
 [omissis...]
 rm: cannot remove `md31-': Read-only file system
(Continue reading)

Permalink | Reply | 3 comments |
headers
Gustin Johnson | 13 Jul 2009 05:26
Picon

Re: [64 Studio] #502: RAID array does not start


64 Studio wrote:
> #502: RAID array does not start
> -------------------------------+--------------------------------------------
>  Reporter:  guido@...  |       Owner:  free
<snip>
>  #!/bin/sh
>  test -e /dev/md0 || /sbin/mdadm --assemble /dev/md0 /dev/sdb1 /dev/sdc1
> 
I can't say how 64Studio handles software RAID yet (this is something I
will be testing).  Anyway, in this script you are better off using the
/dev/disk/by-<id>/<uuid>/<label> instead of /dev/sdXN.
Permalink | Reply | 1 comment |
headers
Quentin Harley | 13 Jul 2009 07:49
Favicon

Sempron Support

http://www.64studio.com/support#comment-5604

Any ideas?  Could this be a Hardy installer problem?

Cheers,
Quentin
Permalink | Reply | 1 comment |
headers
Gustin Johnson | 13 Jul 2009 08:41
Picon

Re: Sempron Support


Quentin Harley wrote:
> http://www.64studio.com/support#comment-5604
> 
> Any ideas?  Could this be a Hardy installer problem?
> 
The exact error would be useful.  At this point all we know is that
something, somewhere, broke for this guy.

If the CPU does not support something that the kernel requires it will
usually throw a kernel panic (like say booting a kernel that expects PAE
on a first gen netbook).
Permalink | Reply | 0 comments |
headers
Guido Piazzi | 13 Jul 2009 22:40
Picon
Favicon

Re: [64 Studio] #502: RAID array does not start

On dom, 2009-07-12 at 21:26 -0600, Gustin Johnson wrote:
> I can't say how 64Studio handles software RAID yet (this is something I
> will be testing).  Anyway, in this script you are better off using the
> /dev/disk/by-<id>/<uuid>/<label> instead of /dev/sdXN.

Done!  Thanks for the hint.

Guido
Permalink | Reply | 0 comments |

Gmane