[64studio-devel] terratec phase 22 support + ALSA in 64studio roadmap

Wed Jan 17 11:52:58 UTC 2007

Hello,
2 quick questions : 
1. How do you install (what's the cleanest way) the latest ALSA source code, drivers, firware. I need terratec phase 22 support which is in the current RC1 of ALSA. Do I need to recompile my kernel or could I use the new modules straight out of the box... well the makefile ! I'm talking snd-ice1724 support here 

2. What will be included ( kernel + alsa) in the next 64studio release ?

THANKS

> Message du 17/01/07 07:47
> De : 64studio-devel-request at 64studio.com
> A : 64studio-devel at 64studio.com
> Copie à : 
> Objet : 64studio-devel Digest, Vol 22, Issue 17
> 
> Send 64studio-devel mailing list submissions to
> 64studio-devel at 64studio.com
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.64studio.com/mailman/listinfo/64studio-devel
> or, via email, send a message with subject or body 'help' to
> 64studio-devel-request at 64studio.com
> 
> You can reach the person managing the list at
> 64studio-devel-owner at 64studio.com
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of 64studio-devel digest..."
> 
> 
> Today's Topics:
> 
> 1. Re: [64 Studio] #258: Consoles ignore keyboard localisation
> (64 Studio)
> 2. Re: [64 Studio] #16: Package Gnash player and plugin (64 Studio)
> 3. Re: [64 Studio] #16: Package Gnash player and plugin (64 Studio)
> 4. Re: [64 Studio] #16: Package Gnash player and plugin (Jimmy)
> 5. Re: [64 Studio] #275: Enable highmem feature on the 2.6.18
> (32 bits) kernel version (64 Studio)
> 6. Re: [64 Studio] #275: Enable highmem feature on the 2.6.18
> (32 bits) kernel version (Yo)
> 7. Re: [64 Studio] #275: Enable highmem feature onthe 2.6.18 (32
> bits) kernel version ( Charles Wyble )
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Tue, 16 Jan 2007 15:32:20 -0000
> From: 64 Studio 
> Subject: Re: [64studio-devel] [64 Studio] #258: Consoles ignore
> keyboard localisation
> To: 64studio-devel at 64studio.com
> Message-ID: <048.9f8f314002c7a74bf3e6df7dcd048c5d at 64studio.com>
> Content-Type: text/plain; charset="utf-8"
> 
> #258: Consoles ignore keyboard localisation
> ----------------------+-----------------------------------------------------
> Reporter: daniel | Owner: free 
> Type: defect | Status: closed
> Priority: normal | Milestone: 2.0 
> Component: packages | Version: 1.0 
> Severity: normal | Resolution: fixed 
> Keywords: | 
> ----------------------+-----------------------------------------------------
> Changes (by free):
> 
> * resolution: => fixed
> * status: new => closed
> 
> Comment:
> 
> (In [1215]) * Added console-setup and console-common (closes #258)
> 
> -- 
> Ticket URL: 
> 64 Studio <>
> 
> ------------------------------
> 
> Message: 2
> Date: Tue, 16 Jan 2007 16:26:31 -0000
> From: 64 Studio 
> Subject: Re: [64studio-devel] [64 Studio] #16: Package Gnash player
> and plugin
> To: 64studio-devel at 64studio.com
> Message-ID: <048.3c73fa146e2bcc2d42444575fac27e1e at 64studio.com>
> Content-Type: text/plain; charset="utf-8"
> 
> #16: Package Gnash player and plugin
> -------------------------+--------------------------------------------------
> Reporter: free | Owner: free
> Type: enhancement | Status: new 
> Priority: high | Milestone: 2.0 
> Component: packages | Version: 
> Severity: normal | Resolution: 
> Keywords: | 
> -------------------------+--------------------------------------------------
> Comment (by free at 64studio.com):
> 
> Gnash is now in sid:
> 
> http://packages.debian.org/unstable/utils/gnash
> 
> shall we include it then?
> 
> -- 
> Ticket URL: 
> 64 Studio <>
> 
> ------------------------------
> 
> Message: 3
> Date: Tue, 16 Jan 2007 16:39:20 -0000
> From: 64 Studio 
> Subject: Re: [64studio-devel] [64 Studio] #16: Package Gnash player
> and plugin
> To: 64studio-devel at 64studio.com
> Message-ID: <048.65ada0cffc8ce2cea9c96ec5bb48f0a2 at 64studio.com>
> Content-Type: text/plain; charset="utf-8"
> 
> #16: Package Gnash player and plugin
> -------------------------+--------------------------------------------------
> Reporter: free | Owner: free
> Type: enhancement | Status: new 
> Priority: high | Milestone: 2.0 
> Component: packages | Version: 
> Severity: normal | Resolution: 
> Keywords: | 
> -------------------------+--------------------------------------------------
> Comment (by free at 64studio.com):
> 
> BTW I've just installed mozilla-plugin-gnash on my 64 Studio partition, it
> seems to work out of the box, although I'm not an expert of flash sites
> :),
> so I can't really say
> 
> -- 
> Ticket URL: 
> 64 Studio <>
> 
> ------------------------------
> 
> Message: 4
> Date: Tue, 16 Jan 2007 10:50:58 +0000
> From: Jimmy 
> Subject: Re: [64studio-devel] [64 Studio] #16: Package Gnash player
> and plugin
> To: 64studio-devel at 64studio.com
> Message-ID: <45ACAE12.9010109 at mailcan.com>
> Content-Type: text/plain; charset=UTF-8; format=flowed
> 
> 64 Studio wrote:
> > #16: Package Gnash player and plugin
> > -------------------------+--------------------------------------------------
> > Reporter: free | Owner: free
> > Type: enhancement | Status: new 
> > Priority: high | Milestone: 2.0 
> > Component: packages | Version: 
> > Severity: normal | Resolution: 
> > Keywords: | 
> > -------------------------+--------------------------------------------------
> > Comment (by free at 64studio.com):
> >
> > Gnash is now in sid:
> >
> > http://packages.debian.org/unstable/utils/gnash
> >
> > shall we include it then?
> 
> Free, I just gave Gnash a try: www.dalejr.com/8.html , uses Flash 7, and 
> it did not work. :-(
> 
> -- 
> Regards,
> Jimmy
> Registered Linux User #380263
> 
> 
> 
> 
> ------------------------------
> 
> Message: 5
> Date: Tue, 16 Jan 2007 21:00:52 -0000
> From: 64 Studio 
> Subject: Re: [64studio-devel] [64 Studio] #275: Enable highmem feature
> on the 2.6.18 (32 bits) kernel version
> To: 64studio-devel at 64studio.com
> Message-ID: <048.9b5e3d09331f2abf64465480a77c2262 at 64studio.com>
> Content-Type: text/plain; charset="utf-8"
> 
> #275: Enable highmem feature on the 2.6.18 (32 bits) kernel version
> -----------------------------------+----------------------------------------
> Reporter: yoyo at xrousse.org | Owner: free
> Type: enhancement | Status: new 
> Priority: high | Milestone: 
> Component: build | Version: 
> Severity: normal | Resolution: 
> Keywords: kernel highmem nvidia | 
> -----------------------------------+----------------------------------------
> Changes (by nomadxf at gmail.com):
> 
> * keywords: kernel highmem => kernel highmem nvidia
> 
> Comment:
> 
> Rather then changing the old kernel, better to fix the new. A temporary
> workaround for the nvidia installer problem (Assuming you mean the nvidia
> offical package and not the debian package) .. and if it is the
> Makefile.modpost -w Invalid Option error is to simply edit:
> 
> /usr/src/linux-headers-2.6.19-1-multimedia-amd64/scripts/Makefile.modpost
> 
> and edit line 66 changing -w to -a ... this will allow you continue the
> installation... The nvidia sanity check (sh NVIDIA..... --sanity) doesnt
> complain about the finished result and it seems to be running quite well
> on my system... This is with nvidia 9746 and the amd64 kernel, but I'm
> guessing its the same problem in 32 bits.
> 
> -- 
> Ticket URL: 
> 64 Studio <>
> 
> ------------------------------
> 
> Message: 6
> Date: Tue, 16 Jan 2007 23:26:31 +0100
> From: Yo 
> Subject: Re: [64studio-devel] [64 Studio] #275: Enable highmem feature
> on the 2.6.18 (32 bits) kernel version
> To: 64studio-devel at 64studio.com
> Message-ID: <45AD5117.9020103 at xrousse.org>
> Content-Type: text/plain; charset=UTF-8; format=flowed
> 
> 
> > /usr/src/linux-headers-2.6.19-1-multimedia-amd64/scripts/Makefile.modpost
> >
> > and edit line 66 changing -w to -a ... this will allow you continue the
> > installation... The nvidia sanity check (sh NVIDIA..... --sanity) doesnt
> > complain about the finished result and it seems to be running quite well
> > on my system... This is with nvidia 9746 and the amd64 kernel, but I'm
> > guessing its the same problem in 32 bits.
> >
> > 
> Thanks for your answer. I applied your workaround but it doesn't work. I 
> think the probem is elsewhere.
> When I launch the nvidia installer, I have the problem before the gcc 
> compilation. I just have a warning (the same as in the log file bellow). 
> I've tried to change option, to use expert mode, to specify 
> kernel-source-path .... No way...
> 
> I also have a problem of compilation with my webcam driver so it's maybe 
> not a nvidia driver issue (problem in kernel headers ?)... I didn't find 
> anything relevant in google, I think I will give up and stay in version 
> 2.6.18-2. :-(
> 
> I confirm that I use nvidia driver and not the Debian package.
> 
> nvidia-installer log file '/var/log/nvidia-installer.log'
> creation time: Tue Jan 16 23:05:43 2007
> 
> option status:
> license pre-accepted : false
> update : false
> force update : false
> expert : true
> uninstall : false
> driver info : false
> precompiled interfaces : false
> no ncurses color : false
> query latest version : false
> OpenGL header files : true
> no questions : false
> silent : false
> no recursion : false
> no backup : false
> kernel module only : false
> sanity : false
> add this kernel : false
> no runlevel check : false
> no network : false
> no ABI note : false
> no RPMs : false
> no kernel module : false
> force SELinux : default
> no X server check : false
> force tls : (not specified)
> X install prefix : (not specified)
> X library install path : (not specified)
> X module install path : (not specified)
> OpenGL install prefix : (not specified)
> OpenGL install libdir : (not specified)
> utility install prefix : (not specified)
> utility install libdir : (not specified)
> doc install prefix : (not specified)
> kernel name : 2.6.19-1-multimedia-486
> kernel include path : (not specified)
> kernel source path : /usr/src/linux-headers-2.6.19-1-multimedia-486/
> kernel output path : (not specified)
> kernel install path : (not specified)
> proc mount point : /proc
> ui : (not specified)
> tmpdir : /tmp
> ftp mirror : ftp://download.nvidia.com
> RPM file list : (not specified)
> 
> chdir("./")
> Using: nvidia-installer ncurses user interface
> -> Searching for system utilities:
> -> found `ldconfig` : `/sbin/ldconfig`
> -> found `ldd` : `/usr/bin/ldd`
> -> found `ld` : `/usr/bin/ld`
> -> found `objcopy` : `/usr/bin/objcopy`
> -> found `grep` : `/bin/grep`
> -> found `dmesg` : `/bin/dmesg`
> -> found `tail` : `/usr/bin/tail`
> -> found `cut` : `/usr/bin/cut`
> -> found `chcon` : `/usr/bin/chcon`
> -> found `pkg-config` : `/usr/bin/pkg-config`
> -> found `X` : `/usr/bin/X`
> -> Searching for module utilities:
> -> found `insmod` : `/sbin/insmod`
> -> found `modprobe` : `/sbin/modprobe`
> -> found `rmmod` : `/sbin/rmmod`
> -> found `lsmod` : `/sbin/lsmod`
> -> found `depmod` : `/sbin/depmod`
> -> License accepted.
> -> There appears to already be a driver installed on your system 
> (version: 1.0-
> 9746). As part of installing this driver (version: 1.0-9746), the 
> existing
> driver will be uninstalled. Are you sure you want to continue? ('no' 
> will a
> bort installation) (Answer: Yes)
> -> Kernel module installation path (Answer:
> '/lib/modules/2.6.19-1-multimedia-486/kernel/drivers/video')
> -> Kernel module installation path: 
> /lib/modules/2.6.19-1-multimedia-486/kernel
> /drivers/video
> -> Not probing for precompiled kernel interfaces.
> -> Checking development tools:
> -> found `cc` : `/usr/bin/cc`
> -> found `make` : `/usr/bin/make`
> -> Performing CC sanity check with CC="cc".
> -> Using the kernel source path
> '/usr/src/linux-headers-2.6.19-1-multimedia-486/' as specified by the
> '--kernel-source-path' commandline option.
> -> Kernel source path (Answer:
> '/usr/src/linux-headers-2.6.19-1-multimedia-486/')
> -> Kernel source path: '/usr/src/linux-headers-2.6.19-1-multimedia-486/'
> -> Kernel output path: '/usr/src/linux-headers-2.6.19-1-multimedia-486/'
> ERROR: If you are using a Linux 2.4 kernel, please make sure
> you either have configured kernel sources matching your
> kernel or the correct set of kernel headers installed
> on your system.
> 
> If you are using a Linux 2.6 kernel, please make sure
> you have configured kernel sources matching your kernel
> installed on your system. If you specified a separate
> output directory using either the "KBUILD_OUTPUT" or
> the "O" KBUILD parameter, make sure to specify this
> directory with the SYSOUT environment variable or with
> the equivalent nvidia-installer command line option.
> 
> Depending on where and how the kernel sources (or the
> kernel headers) were installed, you may need to specify
> their location with the SYSSRC environment variable or
> the equivalent nvidia-installer command line option.
> ERROR: Installation has failed. Please see the file
> '/var/log/nvidia-installer.log' for details. You may find 
> suggestions
> on fixing installation problems in the README available on the Linux
> driver download page at www.nvidia.com.
> 
> -- 
> Yohann 
> http://www.xrousse.org | mailto:yo at xrousse.org | MSN yoyo at xrousse.org | GPG: 0x43D83E36
> 
> C'est toi le nouveau ?
> Je ne sais pas, je viens d'arriver
> 
> 
> 
> 
> ------------------------------
> 
> Message: 7
> Date: Wed, 17 Jan 2007 06:47:07 +0000
> From: " Charles Wyble " 
> Subject: Re: [64studio-devel] [64 Studio] #275: Enable highmem feature
> onthe 2.6.18 (32 bits) kernel version
> To: "Yo" , 64studio-devel-bounces at 64studio.com,
> 64studio-devel at 64studio.com
> Message-ID:
> <247209925-1169016395-cardhu_blackberry.rim.net-1992052024- at bxe008-cell02.bisx.prod.on.blackberry>
> 
> Content-Type: text/plain
> 
> Try setting environment variables
> Sent via BlackBerry from T-Mobile 
> 
> -----Original Message-----
> From: Yo 
> Date: Tue, 16 Jan 2007 23:26:31 
> To:64studio-devel at 64studio.com
> Subject: Re: [64studio-devel] [64 Studio] #275: Enable highmem feature on
> the 2.6.18 (32 bits) kernel version
> 
> 
> > /usr/src/linux-headers-2.6.19-1-multimedia-amd64/scripts/Makefile.modpost
> >
> > and edit line 66 changing -w to -a ... this will allow you continue the
> > installation... The nvidia sanity check (sh NVIDIA..... --sanity) doesnt
> > complain about the finished result and it seems to be running quite well
> > on my system... This is with nvidia 9746 and the amd64 kernel, but I'm
> > guessing its the same problem in 32 bits.
> >
> > 
> Thanks for your answer. I applied your workaround but it doesn't work. I 
> think the probem is elsewhere.
> When I launch the nvidia installer, I have the problem before the gcc 
> compilation. I just have a warning (the same as in the log file bellow). 
> I've tried to change option, to use expert mode, to specify 
> kernel-source-path .... No way...
> 
> I also have a problem of compilation with my webcam driver so it's maybe 
> not a nvidia driver issue (problem in kernel headers ?)... I didn't find 
> anything relevant in google, I think I will give up and stay in version 
> 2.6.18-2. :-(
> 
> I confirm that I use nvidia driver and not the Debian package.
> 
> nvidia-installer log file '/var/log/nvidia-installer.log'
> creation time: Tue Jan 16 23:05:43 2007
> 
> option status:
> license pre-accepted : false
> update : false
> force update : false
> expert : true
> uninstall : false
> driver info : false
> precompiled interfaces : false
> no ncurses color : false
> query latest version : false
> OpenGL header files : true
> no questions : false
> silent : false
> no recursion : false
> no backup : false
> kernel module only : false
> sanity : false
> add this kernel : false
> no runlevel check : false
> no network : false
> no ABI note : false
> no RPMs : false
> no kernel module : false
> force SELinux : default
> no X server check : false
> force tls : (not specified)
> X install prefix : (not specified)
> X library install path : (not specified)
> X module install path : (not specified)
> OpenGL install prefix : (not specified)
> OpenGL install libdir : (not specified)
> utility install prefix : (not specified)
> utility install libdir : (not specified)
> doc install prefix : (not specified)
> kernel name : 2.6.19-1-multimedia-486
> kernel include path : (not specified)
> kernel source path : /usr/src/linux-headers-2.6.19-1-multimedia-486/
> kernel output path : (not specified)
> kernel install path : (not specified)
> proc mount point : /proc
> ui : (not specified)
> tmpdir : /tmp
> ftp mirror : ftp://download.nvidia.com
> RPM file list : (not specified)
> 
> chdir("./")
> Using: nvidia-installer ncurses user interface
> -> Searching for system utilities:
> -> found `ldconfig` : `/sbin/ldconfig`
> -> found `ldd` : `/usr/bin/ldd`
> -> found `ld` : `/usr/bin/ld`
> -> found `objcopy` : `/usr/bin/objcopy`
> -> found `grep` : `/bin/grep`
> -> found `dmesg` : `/bin/dmesg`
> -> found `tail` : `/usr/bin/tail`
> -> found `cut` : `/usr/bin/cut`
> -> found `chcon` : `/usr/bin/chcon`
> -> found `pkg-config` : `/usr/bin/pkg-config`
> -> found `X` : `/usr/bin/X`
> -> Searching for module utilities:
> -> found `insmod` : `/sbin/insmod`
> -> found `modprobe` : `/sbin/modprobe`
> -> found `rmmod` : `/sbin/rmmod`
> -> found `lsmod` : `/sbin/lsmod`
> -> found `depmod` : `/sbin/depmod`
> -> License accepted.
> -> There appears to already be a driver installed on your system 
> (version: 1.0-
> 9746). As part of installing this driver (version: 1.0-9746), the 
> existing
> driver will be uninstalled. Are you sure you want to continue? ('no' 
> will a
> bort installation) (Answer: Yes)
> -> Kernel module installation path (Answer:
> '/lib/modules/2.6.19-1-multimedia-486/kernel/drivers/video')
> -> Kernel module installation path: 
> /lib/modules/2.6.19-1-multimedia-486/kernel
> /drivers/video
> -> Not probing for precompiled kernel interfaces.
> -> Checking development tools:
> -> found `cc` : `/usr/bin/cc`
> -> found `make` : `/usr/bin/make`
> -> Performing CC sanity check with CC="cc".
> -> Using the kernel source path
> '/usr/src/linux-headers-2.6.19-1-multimedia-486/' as specified by the
> '--kernel-source-path' commandline option.
> -> Kernel source path (Answer:
> '/usr/src/linux-headers-2.6.19-1-multimedia-486/')
> -> Kernel source path: '/usr/src/linux-headers-2.6.19-1-multimedia-486/'
> -> Kernel output path: '/usr/src/linux-headers-2.6.19-1-multimedia-486/'
> ERROR: If you are using a Linux 2.4 kernel, please make sure
> you either have configured kernel sources matching your
> kernel or the correct set of kernel headers installed
> on your system.
> 
> If you are using a Linux 2.6 kernel, please make sure
> you have configured kernel sources matching your kernel
> installed on your system. If you specified a separate
> output directory using either the "KBUILD_OUTPUT" or
> the "O" KBUILD parameter, make sure to specify this
> directory with the SYSOUT environment variable or with
> the equivalent nvidia-installer command line option.
> 
> Depending on where and how the kernel sources (or the
> kernel headers) were installed, you may need to specify
> their location with the SYSSRC environment variable or
> the equivalent nvidia-installer command line option.
> ERROR: Installation has failed. Please see the file
> '/var/log/nvidia-installer.log' for details. You may find 
> suggestions
> on fixing installation problems in the README available on the Linux
> driver download page at www.nvidia.com.
> 
> -- 
> Yohann 
> http://www.xrousse.org | mailto:yo at xrousse.org | MSN yoyo at xrousse.org | GPG: 0x43D83E36
> 
> C'est toi le nouveau ?
> Je ne sais pas, je viens d'arriver
> 
> 
> _______________________________________________
> 64studio-devel mailing list
> 64studio-devel at 64studio.com
> http://lists.64studio.com/mailman/listinfo/64studio-devel
> 
> 
> ------------------------------
> 
> _______________________________________________
> 64studio-devel mailing list
> 64studio-devel at 64studio.com
> http://lists.64studio.com/mailman/listinfo/64studio-devel
> 
> 
> End of 64studio-devel Digest, Vol 22, Issue 17
> **********************************************
> ---------------------------------------------------------------------------------------
> Orange vous informe que cet e-mail a ete controle par l'anti-virus mail. 
> Aucun virus connu a ce jour par nos services n'a ete detecte.
> 
> 
> 
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.64studio.com/pipermail/64studio-devel/attachments/20070117/f97cc516/attachment-0001.html 