RE: [gentoo-embedded] Network appliance with sound

RE: [gentoo-embedded] Network appliance with sound

[Marcel Romijn]

> > 
> >
------------------------------------------------------------------------
--------
> > From: Thierry Carrez [mailto:koon@gentoo.org]
> > Sent: Tue 8/30/2005 8:34 PM
> > To: gentoo-embedded@lists.gentoo.org
> > Subject: Re: [gentoo-embedded] Network appliance with sound
> > 
> > 
> > See the GNAP Advanced User Guide : the kernel.config file is located
in
> > the specs directory (which you should find in /usr/lib/gnap).
> 
> Yup. I emerged gnap-dev and I found the kernel configuration.
> I created a new kernel based on the gnap kernel configuration, but
then modified for my processor family, ALSA and my sound interface.
> Creating an ISO with it worked without problems and the machine nicely
boots from it!!!
> 
> 'dmesg' shows me that it has ALSA enabled and shows my sound
interface.
> 
> Thanks for the pointers!!!
> 
> Next on my list is your second suggestion: remaster a gnap core with
the alsa-utils as extension.

Sorry to bother you again with this...

I have tried to remaster a gnap core with a alsa-utils.

'ebuild'-ing the alsa-utils:
# ebuild /usr/portage/media-sound/alsa-utils/alsa-utils-1.0.9a.ebuild
install

Making the extension:
# cd /var/tmp/portage/alsa-utils-1.0.9a/image
# tar -cjvf /usr/lib/gnap/extensions/gnapext_alsa-utils.tbz2 *

Remaster the core with the modified kernel and the alsa-util extension:
#gnap_remaster -k kernel.tar.bz2 -m modules.tar.bz2 -e alsa-utils -o
newcore.tar

Then I can create my boot image:
# gnap_overlay -g newcore.tar ....

This boots nicely and running Gentoo has all the built files from
alsa-utils. However, they won't work.
In my enthausiasm I forgot that alsa-utils is probably depending on
other packages.

And indeed:

# emerge --pretend --emptytree --tree alsa-utils

    These are the packages that I would merge, in reverse order:

    Calculating dependencies  ...done!
    [ebuild  N    ] media-sound/alsa-utils-1.0.9a
    [ebuild  N    ]  dev-util/dialog-1.0.20050206
    [ebuild  N    ]  sys-apps/pciutils-2.1.11-r5
    [ebuild  N    ]  media-libs/alsa-lib-1.0.9
    [ebuild  N    ]   media-sound/alsa-headers-1.0.9b
    [ebuild  N    ]   sys-kernel/gentoo-sources-2.6.12-r9
    [ebuild  N    ]    sys-devel/make-3.80-r2
    [ebuild  N    ]    sys-apps/sed-4.1.4
    [ebuild  N    ]     sys-devel/gettext-0.14.4
    [ebuild  N    ]      sys-libs/glibc-2.3.5-r1
    [ebuild  N    ]       sys-kernel/linux-headers-2.6.11-r2
    [ebuild  N    ]       sys-devel/gcc-3.3.5.20050130-r1
    [ebuild  N    ]        sys-devel/binutils-2.15.92.0.2-r10
    [ebuild  N    ]         sys-devel/binutils-config-1.8-r5
    [ebuild  N    ]          app-shells/bash-3.0-r12
    [ebuild  N    ]        sys-libs/zlib-1.2.3
    [ebuild  N    ]        sys-apps/texinfo-4.8
    [ebuild  N    ]        sys-devel/gnuconfig-20050324
    [ebuild  N    ]        sys-devel/gcc-config-1.3.11-r4
    [ebuild  N    ]        sys-devel/bison-1.875d
    [ebuild  N    ]         sys-devel/m4-1.4.3
    [ebuild  N    ]        sys-libs/ncurses-5.4-r6
    [ebuild  N    ]         sys-libs/gpm-1.20.1-r4
    [ebuild  N    ]     sys-devel/patch-2.5.9

I assume that some of these will probably already be available in the
original GNAP core.
But some of them I need to add.

What would be the best way to figure out which ones are already in the
original GNAP core and which ones I need to add?
Also, is there a way to 'ebuild' alsa-utils and its dependencies in one
go?

Again, thanks for the help so far..!

Marcel Romijn


-- 
gentoo-embedded@gentoo.org mailing list

Re: [gentoo-embedded] Network appliance with sound

[Thierry Carrez]

Marcel Romijn wrote:

> I have tried to remaster a gnap core with a alsa-utils.
> 
> 'ebuild'-ing the alsa-utils:
> # ebuild /usr/portage/media-sound/alsa-utils/alsa-utils-1.0.9a.ebuild
> install
> 
> Making the extension:
> # cd /var/tmp/portage/alsa-utils-1.0.9a/image
> # tar -cjvf /usr/lib/gnap/extensions/gnapext_alsa-utils.tbz2 *

That's not the way extensions are built. This way you end up with
(incomplete) extensions that won't work on the uclibc system.

> What would be the best way to figure out which ones are already in the
> original GNAP core and which ones I need to add?

You don't need to. The extensions process takes care of everything.
Please read the advanced user guide, there is a chapter about building
extensions and you apparently didn't read it :

http://www.gentoo.org/proj/en/base/embedded/gnap-advancedguide.xml#doc_chap4

-- 
Koon
-- 
gentoo-embedded@gentoo.org mailing list

RE: [gentoo-embedded] Network appliance with sound

[Marcel Romijn]

 

> -----Original Message-----
> From: Thierry Carrez [mailto:koon@gentoo.org] 
> Sent: Friday, 02 September, 2005 13:19
> To: gentoo-embedded@lists.gentoo.org
> Subject: Re: [gentoo-embedded] Network appliance with sound
> 
> Marcel Romijn wrote:
> 
> 
> That's not the way extensions are built. This way you end up with
> (incomplete) extensions that won't work on the uclibc system.
> 
> > What would be the best way to figure out which ones are 
> already in the
> > original GNAP core and which ones I need to add?
> 
> You don't need to. The extensions process takes care of everything.
> Please read the advanced user guide, there is a chapter about building
> extensions and you apparently didn't read it :
> 
> http://www.gentoo.org/proj/en/base/embedded/gnap-advancedguide
> .xml#doc_chap4

Oops... you are right. Mea culpa...

I read the normal user guide:
http://www.gentoo.org/proj/en/base/embedded/gnap-userguide.xml#doc_chap5
and assumed it was enough to create the .tbz2 file.

> -- 
> Koon
> -- 
> gentoo-embedded@gentoo.org mailing list
> 

Marcel Romijn

-- 
gentoo-embedded@gentoo.org mailing list

RE: [gentoo-embedded] Network appliance with sound

[Marcel Romijn]

[-- Attachment #1: Type: text/plain, Size: 1085 bytes --]

> 
> --------------------------------------------------------------------------------
> From: Thierry Carrez [mailto:koon@gentoo.org]
> Sent: Tue 8/30/2005 8:34 PM
> To: gentoo-embedded@lists.gentoo.org <mailto:gentoo-embedded@lists.gentoo.org> 
> Subject: Re: [gentoo-embedded] Network appliance with sound
> 
> 
> See the GNAP Advanced User Guide : the kernel.config file is located in
> the specs directory (which you should find in /usr/lib/gnap).

Yup. I emerged gnap-dev and I found the kernel configuration.
I created a new kernel based on the gnap kernel configuration, but then modified for my processor family, ALSA and my sound interface.
Creating an ISO with it worked without problems and the machine nicely boots from it!!!

'dmesg' shows me that it has ALSA enabled and shows my sound interface.

Thanks for the pointers!!!

Next on my list is your second suggestion: remaster a gnap core with the alsa-utils as extension.

> --
> Koon
> --
> gentoo-embedded@gentoo.org <mailto:gentoo-embedded@gentoo.org>  mailing list
> 

Marcel Romijn



[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 3783 bytes --]

RE: [gentoo-embedded] Network appliance with sound

[Marcel Romijn]

 

> -----Original Message-----
> From: Natanael Copa [mailto:mlists@tanael.org] 
> Sent: Tuesday, 30 August, 2005 9:41
> To: gentoo-embedded@lists.gentoo.org
> Subject: Re: [gentoo-embedded] Network appliance with sound
> 
> >
> >Maybe your kernel lacks squashfs support 
> >  
> >
> 
> Or maybe it lacks loop device support?

See my reply to Thierry Carrez about starting off with the GNAP
kernel...

Thanks :-)

Marcel Romijn

-- 
gentoo-embedded@gentoo.org mailing list

RE: [gentoo-embedded] Network appliance with sound

[Marcel Romijn]

 

> -----Original Message-----
> From: Thierry Carrez [mailto:koon@gentoo.org] 
> Sent: Tuesday, 30 August, 2005 9:32
> To: gentoo-embedded@lists.gentoo.org
> Subject: Re: [gentoo-embedded] Network appliance with sound
> 
> > 
> > However, since I did not have my setup ready for CF, I tested it by
> > using gnap_overlay to create an ISO. Booting from the ISO 
> resulted in
> > the following:
> > 
> >>>Mounting squashfs filesystem
> > mount: Mounting /newroot/mnt/cdrom/livecd.squash on 
> /newroot/mnt/livecd
> > failed: No such device
> 
> Maybe your kernel lacks squashfs support ?

That might be the case...
Maybe instead of using my own kernel configuration, I should take it the
other way around: start off with the kernel sources and kernel
configuration that GNAP uses and add ALSA and my sound interface.

Can you give me a pointer to where the GNAP kernel configuration is?

I used the gentoo kernel sources... Are they the same as the sources
used for the GNAP kernel?

> 
> 
> The "ebuild" command is your friend. For example :
> 
> ebuild /usr/portage/app-whatever/whatever-2.0.ebuild install
> 
> will unpack, compile, and prepare installation for whatever-2.0. The
> image containing all the files will be located in :
> 
> /var/tmp/portage/whatever-2.0/install

That looks very interesting...!

Marcel Romijn

-- 
gentoo-embedded@gentoo.org mailing list

Re: [gentoo-embedded] Network appliance with sound

[Thierry Carrez]

Marcel Romijn wrote:

> Can you give me a pointer to where the GNAP kernel configuration is?

See the GNAP Advanced User Guide : the kernel.config file is located in
the specs directory (which you should find in /usr/lib/gnap).

-- 
Koon
-- 
gentoo-embedded@gentoo.org mailing list

RE: [gentoo-embedded] Network appliance with sound

[Marcel Romijn]

 

> -----Original Message-----
> From: Thierry Carrez [mailto:koon@gentoo.org] 
> Sent: Monday, 29 August, 2005 13:50
> To: gentoo-embedded@lists.gentoo.org
> Subject: Re: [gentoo-embedded] Network appliance with sound
> 
> 
> No. The GNAP kernel config does not include sound capabilities. It
> recognizes your hardware but ignores it :
> 
> # CONFIG_SOUND is not set

Ah...

> So you will need three things:
> 
> 1/ replace the kernel by one that supports sound (making a kernpackage
> from the one in your hard-disk-that-works and use 
> gnap_remaster with it
>  should do the trick).

I used genkernel, with the --minkernpackage and --modulespackage
options, to create a kernel.tar.bz2 and modules.tar.bz2. This has
support for ALSA and my sound interface. With gnap_remaster I created a
new core.

However, since I did not have my setup ready for CF, I tested it by
using gnap_overlay to create an ISO. Booting from the ISO resulted in
the following:

<snip>
>> Mounting squashfs filesystem
mount: Mounting /newroot/mnt/cdrom/livecd.squash on /newroot/mnt/livecd
failed: No such device
</snip>

After that, it shows some collateral damage ending in a kernel panic for
not finding /bin/sh

Could this be caused by a badly burned CD-RW? Or is there something else
wrong?

> 2/ add any software needed to play sound. You probably will 
> need to make
> an extension with alsa-utils (which will pull all the others required
> deps) and remaster a core with it included.

Here I was wondering...

How can I emerge alsa-utils in such a way that I know which files it
pulled down?
If I just do an 'emerge alsa-utils', the files will end up in my
development environment. Is there a way to isolate where the emerged
files end up? Is it a chroot trick?
 
> 3/ Boot the resulting GNAP system, run alsaconf to configure 
> everything.
> When everything is configured properly, copy the resulting 
> configuration
> files to make an configuration overlay with them, so that you can
> produce preconfigured GNAP systems directly. Don't forget to add
> "alsasound" to the START_SERVICES parameter in overlay.conf...
> 
> Best of luck.

Thanks...!

Looks like I might need it ;-)

> -- 
> Koon
> -- 
> gentoo-embedded@gentoo.org mailing list
> 

Marcel Romijn

-- 
gentoo-embedded@gentoo.org mailing list

Re: [gentoo-embedded] Network appliance with sound

[Thierry Carrez]

Marcel Romijn wrote:

> I used genkernel, with the --minkernpackage and --modulespackage
> options, to create a kernel.tar.bz2 and modules.tar.bz2. This has
> support for ALSA and my sound interface. With gnap_remaster I created a
> new core.
> 
> However, since I did not have my setup ready for CF, I tested it by
> using gnap_overlay to create an ISO. Booting from the ISO resulted in
> the following:
> 
>>>Mounting squashfs filesystem
> mount: Mounting /newroot/mnt/cdrom/livecd.squash on /newroot/mnt/livecd
> failed: No such device

Maybe your kernel lacks squashfs support ?

> How can I emerge alsa-utils in such a way that I know which files it
> pulled down?
> If I just do an 'emerge alsa-utils', the files will end up in my
> development environment. Is there a way to isolate where the emerged
> files end up? Is it a chroot trick?

The "ebuild" command is your friend. For example :

ebuild /usr/portage/app-whatever/whatever-2.0.ebuild install

will unpack, compile, and prepare installation for whatever-2.0. The
image containing all the files will be located in :

/var/tmp/portage/whatever-2.0/install

-- 
Koon
-- 
gentoo-embedded@gentoo.org mailing list

Re: [gentoo-embedded] Network appliance with sound

[Natanael Copa]

Thierry Carrez wrote:

>Marcel Romijn wrote:
>  
>
>>    
>>
>>>>Mounting squashfs filesystem
>>>>        
>>>>
>>mount: Mounting /newroot/mnt/cdrom/livecd.squash on /newroot/mnt/livecd
>>failed: No such device
>>    
>>
>
>Maybe your kernel lacks squashfs support 
>  
>

Or maybe it lacks loop device support?

-- 
Natanael Copa


-- 
gentoo-embedded@gentoo.org mailing list

[gentoo-embedded] Network appliance with sound

[Marcel Romijn]

Hello,

I want my Epia VIA board to act as a network appliance that produces
music.

Using GNAP, I can make a disk image on a CF from which the board boots.
Works out-of-the-box !!

When I exchange the CF with a regular harddisk, I can install Gentoo
with ALSA and it plays music (following
http://www.gentoo.org/doc/en/alsa-guide.xml).
Now I want the board to boot from CF with ALSA enabled. I can see that
during booting with the GNAP kernel, my sound interface is recognized.
So I don't have to modify the kernel.
Am I correct in assuming that the driver for my sound interface is
compiled as module?

So I guess that the 'only' thing I have to do is make an extension out
of ALSA and use gnap_remaster to create a new, customized core.
I have not used gnap_remaster before, but what I read from the manual,
it should not be too hard.

However, I have no clue of what files need to be included for ALSA...
The ALSA guide emerges the 'alsa-utils'. It then uses 'alsaconf' (if the
sound interface is a module) and adds a service to start at boot. It
also uses 'alsamixer' to unmute the sound interface and set mixer
values.
How do I find out what files I need for the GNAP extension?

Does anyone have experience in this area?

Any help is greatly appreciated :-)

Marcel Romijn

-- 
gentoo-embedded@gentoo.org mailing list

Re: [gentoo-embedded] Network appliance with sound

[Thierry Carrez]

Marcel Romijn wrote:

> I want my Epia VIA board to act as a network appliance that produces
> music.
> 
> Using GNAP, I can make a disk image on a CF from which the board boots.
> Works out-of-the-box !!

Good !

> When I exchange the CF with a regular harddisk, I can install Gentoo
> with ALSA and it plays music (following
> http://www.gentoo.org/doc/en/alsa-guide.xml).
> Now I want the board to boot from CF with ALSA enabled. I can see that
> during booting with the GNAP kernel, my sound interface is recognized.
> So I don't have to modify the kernel.
> Am I correct in assuming that the driver for my sound interface is
> compiled as module?

No. The GNAP kernel config does not include sound capabilities. It
recognizes your hardware but ignores it :

# CONFIG_SOUND is not set

So you will need three things:

1/ replace the kernel by one that supports sound (making a kernpackage
from the one in your hard-disk-that-works and use gnap_remaster with it
 should do the trick).

2/ add any software needed to play sound. You probably will need to make
an extension with alsa-utils (which will pull all the others required
deps) and remaster a core with it included.

3/ Boot the resulting GNAP system, run alsaconf to configure everything.
When everything is configured properly, copy the resulting configuration
files to make an configuration overlay with them, so that you can
produce preconfigured GNAP systems directly. Don't forget to add
"alsasound" to the START_SERVICES parameter in overlay.conf...

Best of luck.

-- 
Koon
-- 
gentoo-embedded@gentoo.org mailing list