astlinux-users — AstLinux Users Mailing List

Re: [Astlinux-users] Coreutils compile problem (0.4 branch)

[Darrick H. <dha...@dj...>]

Sebastian Auriol wrote:
> AstLinux 0.4 branch from today (and older versions) fail to compile in the
> coreutils package. I wanted to create an AstLinux image with "The minimum
> needed to build a uClibc development system":
>   
Sebastian,

I'm trying to be as nice and patient as I can with your errors.  You get 
a D+ for following instructions though.

coreutils is not selected by default.  It is not needed for basic 
functionality on an astlinux box.  Most of these functions are already 
provided by busybox.

Please refer back to previous note messages which provide complete 
instructions to have a working box.  Could coreutils be fixed to work?  
Probably.  Is it even on our list?  No.  The goal of this project isn't 
to add everything that you might find on a full blown Linux box.  It's 
to provide the needed functionality in the smallest footprint necessary 
to provide that functionality.

Darrick

-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com

[Astlinux-users] Coreutils compile problem (0.4 branch)

[Sebastian A. <sp...@sy...>]

AstLinux 0.4 branch from today (and older versions) fail to compile in the
coreutils package. I wanted to create an AstLinux image with "The minimum
needed to build a uClibc development system":

config.status: creating po/Makefile
#Fix up the max number of open files per process, which apparently
# is not set when cross compiling
/var/spool/astlinux/0.4-svn-MAR/toolchain_build_i586/bin/sed -i -e
's,.*UTILS_OPEN_MAX.*,#define UTILS_OPEN_MAX 1019,g' \
        /var/spool/astlinux/0.4-svn-MAR/build_i586/coreutils-5.94/config.h
# This is undefined when crosscompiling...
/var/spool/astlinux/0.4-svn-MAR/toolchain_build_i586/bin/sed -i -e
's,.*HAVE_PROC_UPTIME.*,#define HAVE_PROC_UPTIME 1,g' \
        /var/spool/astlinux/0.4-svn-MAR/build_i586/coreutils-5.94/config.h
touch /var/spool/astlinux/0.4-svn-MAR/build_i586/coreutils-5.94/.configured
make -j1
CC=/var/spool/astlinux/0.4-svn-MAR/build_i586/staging_dir/bin/i586-linux-ucl
ibc-gcc -C /var/spool/astlinux/0.4-svn-MAR/build_i586/coreutils-5.94
make[1]: Entering directory
`/var/spool/astlinux/0.4-svn-MAR/build_i586/coreutils-5.94'
make  all-recursive
make[2]: Entering directory
`/var/spool/astlinux/0.4-svn-MAR/build_i586/coreutils-5.94'
Making all in lib
make[3]: Entering directory
`/var/spool/astlinux/0.4-svn-MAR/build_i586/coreutils-5.94/lib'
cp ./alloca_.h alloca.h-t
mv alloca.h-t alloca.h
make  all-am
make[4]: Entering directory
`/var/spool/astlinux/0.4-svn-MAR/build_i586/coreutils-5.94/lib'
/var/spool/astlinux/0.4-svn-MAR/build_i586/staging_dir/bin/i586-linux-uclibc
-gcc -DHAVE_CONFIG_H -DLIBDIR=\"/usr/lib\" -I. -I. -I..  -I.. -I.   -Os
-pipe  -c allocsa.c
/var/spool/astlinux/0.4-svn-MAR/build_i586/staging_dir/bin/i586-linux-uclibc
-gcc -DHAVE_CONFIG_H -DLIBDIR=\"/usr/lib\" -I. -I. -I..  -I.. -I.   -Os
-pipe  -c fprintftime.c
/var/spool/astlinux/0.4-svn-MAR/build_i586/staging_dir/bin/i586-linux-uclibc
-gcc -DHAVE_CONFIG_H -DLIBDIR=\"/usr/lib\" -I. -I. -I..  -I.. -I.   -Os
-pipe  -c full-read.c
/var/spool/astlinux/0.4-svn-MAR/build_i586/staging_dir/bin/i586-linux-uclibc
-gcc -DHAVE_CONFIG_H -DLIBDIR=\"/usr/lib\" -I. -I. -I..  -I.. -I.   -Os
-pipe  -c full-write.c
/var/spool/astlinux/0.4-svn-MAR/build_i586/staging_dir/bin/i586-linux-uclibc
-gcc -DHAVE_CONFIG_H -DLIBDIR=\"/usr/lib\" -I. -I. -I..  -I.. -I.   -Os
-pipe  -c localcharset.c
/var/spool/astlinux/0.4-svn-MAR/build_i586/staging_dir/bin/i586-linux-uclibc
-gcc -DHAVE_CONFIG_H -DLIBDIR=\"/usr/lib\" -I. -I. -I..  -I.. -I.   -Os
-pipe  -c mbswidth.c
/var/spool/astlinux/0.4-svn-MAR/build_i586/staging_dir/bin/i586-linux-uclibc
-gcc -DHAVE_CONFIG_H -DLIBDIR=\"/usr/lib\" -I. -I. -I..  -I.. -I.   -Os
-pipe  -c readtokens0.c
/var/spool/astlinux/0.4-svn-MAR/build_i586/staging_dir/bin/i586-linux-uclibc
-gcc -DHAVE_CONFIG_H -DLIBDIR=\"/usr/lib\" -I. -I. -I..  -I.. -I.   -Os
-pipe  -c strnlen1.c
/var/spool/astlinux/0.4-svn-MAR/build_i586/staging_dir/bin/i586-linux-uclibc
-gcc -DHAVE_CONFIG_H -DLIBDIR=\"/usr/lib\" -I. -I. -I..  -I.. -I.   -Os
-pipe  -c time_r.c
In file included from time_r.c:25:
time_r.h:42: error: conflicting types for 'restrict'
time_r.h:42: error: previous definition of 'restrict' was here
time_r.h:50: error: conflicting types for 'restrict'
time_r.h:50: error: previous definition of 'restrict' was here
time_r.h:54: error: conflicting types for 'restrict'
time_r.h:54: error: previous definition of 'restrict' was here
time_r.c:48: error: parse error before "tm"
time_r.c: In function `rpl_asctime_r':
time_r.c:49: error: number of arguments doesn't match prototype
time_r.h:42: error: prototype declaration
time_r.c:50: error: `buf' undeclared (first use in this function)
time_r.c:50: error: (Each undeclared identifier is reported only once
time_r.c:50: error: for each function it appears in.)
time_r.c:50: error: `tm' undeclared (first use in this function)
time_r.c: At top level:
time_r.c:60: error: parse error before "t"
time_r.c: In function `rpl_gmtime_r':
time_r.c:61: error: number of arguments doesn't match prototype
time_r.h:50: error: prototype declaration
time_r.c:62: error: `tp' undeclared (first use in this function)
time_r.c:62: error: `t' undeclared (first use in this function)
time_r.c: At top level:
time_r.c:66: error: parse error before "t"
time_r.c: In function `rpl_localtime_r':
time_r.c:67: error: number of arguments doesn't match prototype
time_r.h:54: error: prototype declaration
time_r.c:68: error: `tp' undeclared (first use in this function)
time_r.c:68: error: `t' undeclared (first use in this function)
make[4]: *** [time_r.o] Error 1
make[4]: Leaving directory
`/var/spool/astlinux/0.4-svn-MAR/build_i586/coreutils-5.94/lib'
make[3]: *** [all] Error 2
make[3]: Leaving directory
`/var/spool/astlinux/0.4-svn-MAR/build_i586/coreutils-5.94/lib'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/var/spool/astlinux/0.4-svn-MAR/build_i586/coreutils-5.94'
make[1]: *** [all] Error 2
make[1]: Leaving directory
`/var/spool/astlinux/0.4-svn-MAR/build_i586/coreutils-5.94'
make: ***
[/var/spool/astlinux/0.4-svn-MAR/build_i586/coreutils-5.94/src/vdir] Error 2
[seb@IVRA6 0.4-svn-MAR]$

BTW, this was with 1 concurrent job set to run; i386; i586; Generic i586.

Kind regards,

Sebastian 

Re: [Astlinux-users] trunk bash compile minor error

[Darrick H. <dha...@dj...>]

Kristian Kielhofner wrote:
>> I'm really tempted to make a proper VMware development environment so
>> I can say definitively that my environment isn't at fault. Maybe stick
>> that into the SVN repository as well?
>>     
>
>   While many people use VMWare, that really defeats the purpose of
> buildroot.  trunk now includes a basic dependency check.  I plan on
> extending that to check the host system for all of the various
> required software components, versions, etc.  That should drastically
> cut down on some of the problems people are having.
>   
There are several reasons to use VMWare.  The best reason is to prevent 
accidental mishaps.  This will go away with some of the changes in 
trunk, but currently, the makeimage.sh script must be run as root.  I 
know I've accidentially stayed as root and done some actions which could 
potentially cause problems to the host system.  Again, most of that risk 
will go away with trunk shortly.  Kristian has started using a method of 
making the images that doesn't require the user to be root.  (I believe 
this involves fakeroot).

The other reason for using vmware is to have a consistent build 
environment.  Most, if not all, of the development work has been done on 
CentOS4.  If someone doesn't have a spare PC around, they could setup a 
VMware image with CentOS in it (just for consistency).  However, it 
shouldn't matter which version of Linux you compile this on, as long as 
the basic system requirements are met. 
>   How would we stick a VmWare image into SVN?
>   
That would be absurd.  The host system requirements don't change often 
enough to require revision control.  (let along the size of the 
creature).  I don't think we need to distribute a virtual machine for 
the build environment.  It would be good to have the build system 
requirements documented better. Perhaps we need a wiki other than 
voip-info--the information gets too muddled there.

Darrick

-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com

Re: [Astlinux-users] trunk bash compile minor error

[Kristian K. <kri...@gm...>]

On 3/16/07, ast...@el... <ast...@el...> wrote:
>
> But the concurrent jobs setting was at the default 2...

  The only reason I asked was because the more concurrent jobs, the
harder it is to read errors from make, gcc, etc, as they are printed
on the screen.  It doesn't have anything to do with the actual number
of jobs.  It just makes it easier to read.

> I've reinstalled a fair amount of stuff, and ran with only 1
> concurrent job and that seemed to make it go away, I think.

  That could very well be the case.  Can you find out for sure?

> Using gcc 4.2 20070307, binutils 2.16.91.0.7 , and a hand fix in the
> makefile for syslinux so it doesn't call the windows stuff (changing
> the $(BOBJECTS) to $(BTARGET), I got a compile to finish properly.

  Hmmm...  That hand fix is not required with the standard
configuration.  Do you know why you needed to make this change?

> Too bad I don't have an easy way to test the image itself.

  "make iso" - load astlinux.iso into VmWare.  It will boot and run as
a live cd.

> I'm really tempted to make a proper VMware development environment so
> I can say definitively that my environment isn't at fault. Maybe stick
> that into the SVN repository as well?

  While many people use VMWare, that really defeats the purpose of
buildroot.  trunk now includes a basic dependency check.  I plan on
extending that to check the host system for all of the various
required software components, versions, etc.  That should drastically
cut down on some of the problems people are having.

  I should also point out that a lot of your problems come from using
non-standard options.  Your GCC snapshot and bleeding-edge binutils,
for instance.  Quite frankly, there is no way that we could possibly
support all of the various options and packages in buildroot.  Just
because an option for a given version of binutils (for instance), is
available it doesn't mean that it has been tested with all of the
various packages and other options.  As Darrick pointed out a while
ago, we only have the resources to support the default config.

  Most of the time you can change a few options, packages, etc without
causing too many problems.

  How would we stick a VmWare image into SVN?


-- 
Kristian Kielhofner

Re: [Astlinux-users] trunk bash compile minor error

[<ast...@el...>]

On 3/15/07, Kristian Kielhofner <kri...@gm...> wrote:
> On 3/12/07, ast...@el... <ast...@el...> wrote:
> > Got a bit of a surprise shock when I decided to go a little bleeding edge
> > with a trunk compile. Seems bash has a minor issue, though I hadn't seen
> > it before when I either was able to complete a compile, or at least get
> > much farther along.
> >
> > This is trunk 757 with gcc 4.2 snapshot 20070307 , compile with ObjC,
> > shared libraries, and libtool. This is on an older svn checkout where I
> > had wiped out toolchain, toolchain_buildi586, and build_i586 and did a svn
> > update to rebuild those parts cleanly while retaining the dl directory.
> >
>
> asterisk,
>
>   Wow, that is bleeding edge!
>
>   Anyways, I can't really make much sense out of that error.  Can you
> turn the number of parallel builds down and run make after script?
>
> --
> Kristian Kielhofner

But the concurrent jobs setting was at the default 2...

I've reinstalled a fair amount of stuff, and ran with only 1
concurrent job and that seemed to make it go away, I think.

Using gcc 4.2 20070307, binutils 2.16.91.0.7 , and a hand fix in the
makefile for syslinux so it doesn't call the windows stuff (changing
the $(BOBJECTS) to $(BTARGET), I got a compile to finish properly.

Too bad I don't have an easy way to test the image itself.

I'm really tempted to make a proper VMware development environment so
I can say definitively that my environment isn't at fault. Maybe stick
that into the SVN repository as well?

[Astlinux-users] trunk - madwifi and binutils 2.17.50.0.10 don't like each other

[<ast...@el...>]

During another rather bleeding edge trunk compile, madwifi had an issue

i386-elf.hal.o file format not recognized

Apparently, this is a known issue, and it's binutil's fault.

http://madwifi.org/ticket/1140

Re: [Astlinux-users] /proc/bus/usb and lsusb

[Sebastian A. <sp...@sy...>]

ast...@li... <> wrote:
> On 3/15/07, Sebastian Auriol <sp...@sy...> wrote:
>> Why is the /proc/bus/usb directory empty on AstLinux 0.4 when I have
>> three USB devices plugged in (and two - the keyboard and usb-storage
>> - certainly work)? 
>> 
>> Also, there is no lsusb utility. What is this usually installed by?
>> Usbutils? I haven't got that package installed, but I do have libusb
>> installed. 
>> 
>> Many thanks,
>> 
>> Sebastian
>> 
> 
> Sebastian,
> 
>   usbfs is not mounted by default in 0.4.  It is in 0.5.  Try this:
> 
> mount -t usbfs usbfs /proc/bus/usb

Thanks, that works!

Many thanks,

Sebastian

Re: [Astlinux-users] /proc/bus/usb and lsusb

[Kristian K. <kri...@gm...>]

On 3/15/07, Sebastian Auriol <sp...@sy...> wrote:
> Why is the /proc/bus/usb directory empty on AstLinux 0.4 when I have three
> USB devices plugged in (and two - the keyboard and usb-storage - certainly
> work)?
>
> Also, there is no lsusb utility. What is this usually installed by?
> Usbutils? I haven't got that package installed, but I do have libusb
> installed.
>
> Many thanks,
>
> Sebastian
>

Sebastian,

  usbfs is not mounted by default in 0.4.  It is in 0.5.  Try this:

mount -t usbfs usbfs /proc/bus/usb

-- 
Kristian Kielhofner

Re: [Astlinux-users] /proc/bus/usb and lsusb

[Darrick H. <dha...@dj...>]

Sebastian Auriol wrote:
> Sebastian Auriol wrote:
>   
>> Why is the /proc/bus/usb directory empty on AstLinux 0.4 when
>> I have three
>> USB devices plugged in (and two - the keyboard and
>> usb-storage - certainly
>> work)?
>>     
This is simple.  A line needs to be added to the fstab.  I'll make the 
change in 0.4.  I think Kristian may have already made this change in trunk.

Read more here:
http://www.linux-usb.org/USB-guide/x173.html

Darrick

-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com

Re: [Astlinux-users] /proc/bus/usb and lsusb

[Sebastian A. <sp...@sy...>]

Sebastian Auriol wrote:
> Why is the /proc/bus/usb directory empty on AstLinux 0.4 when
> I have three
> USB devices plugged in (and two - the keyboard and
> usb-storage - certainly
> work)?
> 
> Also, there is no lsusb utility. What is this usually installed by?
> Usbutils? I haven't got that package installed, but I do have libusb
> installed. 
> 
> Many thanks,
> 
> Sebastian

Scrap my second query: I worked out for myself that lsusb is installed by
the usbutils package. My first query still stands though.

Many thanks,

Sebastian

[Astlinux-users] /proc/bus/usb and lsusb

[Sebastian A. <sp...@sy...>]

Why is the /proc/bus/usb directory empty on AstLinux 0.4 when I have three
USB devices plugged in (and two - the keyboard and usb-storage - certainly
work)?

Also, there is no lsusb utility. What is this usually installed by?
Usbutils? I haven't got that package installed, but I do have libusb
installed.

Many thanks,

Sebastian

Re: [Astlinux-users] Add drivers 0.4

[Manuel <lis...@gm...>]

Thanks Dominko, I will try this night.

 

Regards,

 

--

Manuel

 

De: ast...@li...
[mailto:ast...@li...] En nombre de Dominko
Vrljic
Enviado el: jueves, 15 de marzo de 2007 13:05
Para: AstLinux Users Mailing List
Asunto: Re: [Astlinux-users] Add drivers 0.4

 

Manuel,
in file /boot/grub/grub.conf line with safedefault  cause problem in latest
trunk version. Try remove this line:
-when see message Astlinux (Boot from... press e
-select line with safedefault and press d
-press b
and astlinux will boot successfully.

Dominko

Manuel <lis...@gm...> wrote:

Kristian,

I would like to use 0.5 but the problem is time. What is your plan for
releasing 0.5? I need to finish this system in a few weeks and by the moment
the system not boot. I need to resolve a lot of thinks (vlan, provisioning,
dial plan, sounds, directory...) and test the stability of all. My first
intention was always to start using trunk. Then make all the development and
when the 0.5 be ready try to upgrade. I have reviewed in kernel.org the
changes logs from 2.6.16.12 to 2.6.20. A lot of changes and several speaking
about mini-itx motherboards. In this moment I prefer go to trunk but the
problem is trying to install in my compact flash. The generated livecd works
but not the install part. I have tested grup but give me another error about
a file not found. I have seen that you are upgrading grup package. I will
try again this night and give you my results.

Only another question. Exists differences in trunk between Geni586 and Via
targets? 


Thanks,

--
Manuel


-----Mensaje original-----
De: ast...@li...
[mailto:ast...@li...] En nombre de Kristian
Kielhofner
Enviado el: jueves, 15 de marzo de 2007 6:30
Para: AstLinux Users Mailing List
Asunto: Re: [Astlinux-users] Add drivers 0.4

On 3/14/07, Manuel wrote:
> Kristian,
>
> Your patch not Works. When system boot the NIC is detected but DHCP fail
to
> get an IP address. I have put a static IP and tried to make a ping. I see
> leds in NIC and switch flashing but not receive any packet. I don't known
> where is the problem but following your patch I have compared de 2 r8169.c
> files from trunk and 0.4. I have seen many different and I have make a
patch
> to include all the changes. When try to compile in 0.4 give some errors
and
> not compile de module. I don't know what will be my next step. This night
> it's possible I try again with trunk.
>
> Darrick,
> If you like you can remove the patch from svn or make an image including
it,
> what you prefer.
>
>
> Kristian & Darrick thanks for all your efforts to help me,
>
> --
> Manuel
>

Manuel,

Dang. I was hoping that would do it. I guess that would have been too
easy.

It would be a lot of work to backport the full driver from 2.6.20.

0.4 is the stable tree and I won't upgrade the kernel. Do you have
any serious aversions to running 0.5 when it is released?

-- 
Kristian Kielhofner

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to
pa...@kr....


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to
pa...@kr....

 

  

  _____  

Don't pick lemons.
See all the new
<http://autos.yahoo.com/new_cars.html;_ylc=X3oDMTE0OGRsc3F2BF9TAzk3MTA3MDc2B
HNlYwNtYWlsdGFncwRzbGsDbmV3Y2Fycw-->  2007 cars at Yahoo!
<http://autos.yahoo.com/new_cars.html;_ylc=X3oDMTE0OGRsc3F2BF9TAzk3MTA3MDc2B
HNlYwNtYWlsdGFncwRzbGsDbmV3Y2Fycw-->  Autos.

Re: [Astlinux-users] Add drivers 0.4

[Dominko V. <dom...@ya...>]

Manuel,
in file /boot/grub/grub.conf line with safedefault  cause problem in latest trunk version. Try remove this line:
-when see message Astlinux (Boot from... press e
-select line with safedefault and press d
-press b
and astlinux will boot successfully.

Dominko

Manuel <lis...@gm...> wrote: Kristian,

I would like to use 0.5 but the problem is time. What is your plan for
releasing 0.5? I need to finish this system in a few weeks and by the moment
the system not boot. I need to resolve a lot of thinks (vlan, provisioning,
dial plan, sounds, directory...) and test the stability of all. My first
intention was always to start using trunk. Then make all the development and
when the 0.5 be ready try to upgrade.  I have reviewed in kernel.org the
changes logs from 2.6.16.12 to 2.6.20. A lot of changes and several speaking
about mini-itx motherboards. In this moment I prefer go to trunk but the
problem is trying to install in my compact flash. The generated livecd works
but not the install part. I have tested grup but give me another error about
a file not found. I have seen that you are upgrading grup package. I will
try again this night and give you my results.

Only another question. Exists differences in trunk between Geni586 and Via
targets? 


Thanks,

--
Manuel
 

-----Mensaje original-----
De: ast...@li...
[mailto:ast...@li...] En nombre de Kristian
Kielhofner
Enviado el: jueves, 15 de marzo de 2007 6:30
Para: AstLinux Users Mailing List
Asunto: Re: [Astlinux-users] Add drivers 0.4

On 3/14/07, Manuel 
 wrote:
> Kristian,
>
> Your patch not Works. When system boot the NIC is detected but DHCP fail
to
> get an IP address. I have put a static IP and tried to make a ping. I see
> leds in NIC and switch flashing but not receive any packet. I don't known
> where is the problem but following your patch I have compared de 2 r8169.c
> files from trunk and 0.4. I have seen many different and I have make a
patch
> to include all the changes. When try to compile in 0.4 give some errors
and
> not compile de module. I don't know what will be my next step. This night
> it's possible I try again with trunk.
>
> Darrick,
> If you like you can remove the patch from svn or make an image including
it,
> what you prefer.
>
>
> Kristian & Darrick thanks for all your efforts to help me,
>
> --
> Manuel
>

Manuel,

  Dang.  I was hoping that would do it.  I guess that would have been too
easy.

  It would be a lot of work to backport the full driver from 2.6.20.

  0.4 is the stable tree and I won't upgrade the kernel.  Do you have
any serious aversions to running 0.5 when it is released?

-- 
Kristian Kielhofner

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to
pa...@kr....


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....


 
---------------------------------
Don't pick lemons.
See all the new 2007 cars at Yahoo! Autos.

Re: [Astlinux-users] Interesting hardware

[Mark P. <g7...@g7...>]

Would be nice if there were some pictures of it.



On Thu, 2007-03-15 at 00:55 +0000, ast...@el... wrote:
> While not exactly an ideal platform for AstLinux, it nevertheless is an
> interesting platform for a VoIP appliance box.
> 
> http://www.dataevolution.com/dectop%20info%202.htm
> 
> This is the former AMD PIC thin client/stripped down PC for emerging
> markets. Runs a Geode GX or unspecified type. Apparently Data Evolution
> Corporation bought up the PIC assets after AMD killed off the PIC program.
> Unfortunately, no pricing data is available for now.

Re: [Astlinux-users] Add drivers 0.4

[Manuel <lis...@gm...>]

Kristian,

I would like to use 0.5 but the problem is time. What is your plan for
releasing 0.5? I need to finish this system in a few weeks and by the moment
the system not boot. I need to resolve a lot of thinks (vlan, provisioning,
dial plan, sounds, directory...) and test the stability of all. My first
intention was always to start using trunk. Then make all the development and
when the 0.5 be ready try to upgrade.  I have reviewed in kernel.org the
changes logs from 2.6.16.12 to 2.6.20. A lot of changes and several speaking
about mini-itx motherboards. In this moment I prefer go to trunk but the
problem is trying to install in my compact flash. The generated livecd works
but not the install part. I have tested grup but give me another error about
a file not found. I have seen that you are upgrading grup package. I will
try again this night and give you my results.

Only another question. Exists differences in trunk between Geni586 and Via
targets? 


Thanks,

--
Manuel
 

-----Mensaje original-----
De: ast...@li...
[mailto:ast...@li...] En nombre de Kristian
Kielhofner
Enviado el: jueves, 15 de marzo de 2007 6:30
Para: AstLinux Users Mailing List
Asunto: Re: [Astlinux-users] Add drivers 0.4

On 3/14/07, Manuel <lis...@gm...> wrote:
> Kristian,
>
> Your patch not Works. When system boot the NIC is detected but DHCP fail
to
> get an IP address. I have put a static IP and tried to make a ping. I see
> leds in NIC and switch flashing but not receive any packet. I don't known
> where is the problem but following your patch I have compared de 2 r8169.c
> files from trunk and 0.4. I have seen many different and I have make a
patch
> to include all the changes. When try to compile in 0.4 give some errors
and
> not compile de module. I don't know what will be my next step. This night
> it's possible I try again with trunk.
>
> Darrick,
> If you like you can remove the patch from svn or make an image including
it,
> what you prefer.
>
>
> Kristian & Darrick thanks for all your efforts to help me,
>
> --
> Manuel
>

Manuel,

  Dang.  I was hoping that would do it.  I guess that would have been too
easy.

  It would be a lot of work to backport the full driver from 2.6.20.

  0.4 is the stable tree and I won't upgrade the kernel.  Do you have
any serious aversions to running 0.5 when it is released?

-- 
Kristian Kielhofner

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to
pa...@kr....

Re: [Astlinux-users] Interesting hardware

[Kristian K. <kri...@gm...>]

On 3/15/07, Bryce Chidester <br...@rh...> wrote:
> I had a chance to play around with the Geode GX (and both other models,
> one of which is still sitting on my window sill), and while I commend
> AMD on putting together one heck of a demo box, the CPU itself just
> couldn't handle very much transcoding or echo cancellation. Simply
> terminating Zap calls into Echo() with zapata.conf's echocancel=yes
> would grind the system to a halt starting at exactly call number 8. It
> may be a good little desktop system, but it's strengths are definitely
> not in realtime processing. Admittedly, when AMD marketed the Geode to
> embedded applications, they emphasized the flexibility of a PC
> architecture, not the power - it's meant to be a low power, fan-less
> processor.
> Just my $.02.
>
> Regards,
> Bryce Chidester
> Rhino Equipment Corp.
> br...@rh...
> Tel: +1 (480) 940-1826 x6351
> Fax: +1 (480) 961-1826
> FWD: 633686 x6351
> IP: asterisk.rhinoequipment.com x6351
>

Agreed.

  The new GX isn't a whole lot better than the GX1 that is the SC1100
used in the net48xx/WRAP boads.

  AMD also makes the LX and NX.  The new Soekris (net5501) uses the
LX, which is faster than the GX but does not have the sweeeet FPU that
the NX has.  Check it out:

http://en.wikipedia.org/wiki/Geode_(processor)


-- 
Kristian Kielhofner

Re: [Astlinux-users] Interesting hardware

[Bryce C. <br...@rh...>]

I had a chance to play around with the Geode GX (and both other models, 
one of which is still sitting on my window sill), and while I commend 
AMD on putting together one heck of a demo box, the CPU itself just 
couldn't handle very much transcoding or echo cancellation. Simply 
terminating Zap calls into Echo() with zapata.conf's echocancel=yes 
would grind the system to a halt starting at exactly call number 8. It 
may be a good little desktop system, but it's strengths are definitely 
not in realtime processing. Admittedly, when AMD marketed the Geode to 
embedded applications, they emphasized the flexibility of a PC 
architecture, not the power - it's meant to be a low power, fan-less 
processor.
Just my $.02.

Regards,
Bryce Chidester
Rhino Equipment Corp.
br...@rh...
Tel: +1 (480) 940-1826 x6351
Fax: +1 (480) 961-1826
FWD: 633686 x6351
IP: asterisk.rhinoequipment.com x6351

THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE  PROPRIETARY MATERIAL and is thus for use only by the intended  recipient. If you received this in error, please contact the sender  and delete the email and its attachments from all computers.



ast...@el... wrote:
> While not exactly an ideal platform for AstLinux, it nevertheless is an
> interesting platform for a VoIP appliance box.
>
> http://www.dataevolution.com/dectop%20info%202.htm
>
> This is the former AMD PIC thin client/stripped down PC for emerging
> markets. Runs a Geode GX or unspecified type. Apparently Data Evolution
> Corporation bought up the PIC assets after AMD killed off the PIC program.
> Unfortunately, no pricing data is available for now.
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
>
>   

Re: [Astlinux-users] trunk bash compile minor error

[Kristian K. <kri...@gm...>]

On 3/12/07, ast...@el... <ast...@el...> wrote:
> Got a bit of a surprise shock when I decided to go a little bleeding edge
> with a trunk compile. Seems bash has a minor issue, though I hadn't seen
> it before when I either was able to complete a compile, or at least get
> much farther along.
>
> This is trunk 757 with gcc 4.2 snapshot 20070307 , compile with ObjC,
> shared libraries, and libtool. This is on an older svn checkout where I
> had wiped out toolchain, toolchain_buildi586, and build_i586 and did a svn
> update to rebuild those parts cleanly while retaining the dl directory.
>

asterisk,

  Wow, that is bleeding edge!

  Anyways, I can't really make much sense out of that error.  Can you
turn the number of parallel builds down and run make after script?

-- 
Kristian Kielhofner

Re: [Astlinux-users] Add drivers 0.4

[Kristian K. <kri...@gm...>]

On 3/14/07, Manuel <lis...@gm...> wrote:
> Kristian,
>
> Your patch not Works. When system boot the NIC is detected but DHCP fail to
> get an IP address. I have put a static IP and tried to make a ping. I see
> leds in NIC and switch flashing but not receive any packet. I don't known
> where is the problem but following your patch I have compared de 2 r8169.c
> files from trunk and 0.4. I have seen many different and I have make a patch
> to include all the changes. When try to compile in 0.4 give some errors and
> not compile de module. I don't know what will be my next step. This night
> it's possible I try again with trunk.
>
> Darrick,
> If you like you can remove the patch from svn or make an image including it,
> what you prefer.
>
>
> Kristian & Darrick thanks for all your efforts to help me,
>
> --
> Manuel
>

Manuel,

  Dang.  I was hoping that would do it.  I guess that would have been too easy.

  It would be a lot of work to backport the full driver from 2.6.20.

  0.4 is the stable tree and I won't upgrade the kernel.  Do you have
any serious aversions to running 0.5 when it is released?

-- 
Kristian Kielhofner

[Astlinux-users] Alternative bridging functionality (for trunk?)

[<ast...@el...>]

While trying to nail down more information about IAX, I came across this
in the mantis bug tracker.

http://bugs.digium.com/view.php?id=5841

This is work to put a form of alternative bridging functionality into
Asterisk, to solve some problems (getting around some MeetMe issues), and
to allow more things to be done through dialplan logic.


While the primary work on this is for Asterisk trunk, there seems to be
sufficient interest in backporting this functionality for Asterisk 1.2 it
seems.

I got into contact with Moises Silva, mentioned near the end of the bug
report comments, about his backport patch which should be the latest
version available for the 1.2.x series. He does not mind AstLinux using
it, though he desires some feedback in the bugreport to help improve the
bridge functionality overall (though there seems to be some negative
feelings regarding backport reporting in that bug comment thread
though...)

Anyways, the patch is here.

http://www.moythreads.com/asterisk/

You will need to edit the asterisk version info and path at the beginning
of the patch, then drop it into the asterisk package folder. I tried to
compile with it, but my compile box is starting to get strange, so I don't
trust it as much anymore. It seems to compile alright if  you don't
compile with mISDN stuff. If mISDN is present, the compile melts down near
the ISDN stuff, about not finding things. While the stated version is
intended for 1.2.12.1 it should be alright in higher versions.

Moises Silva indicated that the patch currently does not work with proxy
channels, such as Agent, but he's working on it. He specifically desired
feedback under heavy load, though I doubt we can provide meaningful
feedback in that aspect.




This brings up a small point I would like to make. Would it be possible to
add a small menuconfig option for something like Asterisk Custom under the
Asterisk package grouping? This would be so that you could turn off or on
compiling Asterisk with patches located in the packages/asterisk/custom
folder, which previously was being used to install the postgreSQL custom
patch. That way, I could drop in patches of interest to experiment with
relatively easily. This would be specific to Asterisk, as opposed to the
general experimental/unspported package choice.

[Astlinux-users] Interesting hardware

[<ast...@el...>]

While not exactly an ideal platform for AstLinux, it nevertheless is an
interesting platform for a VoIP appliance box.

http://www.dataevolution.com/dectop%20info%202.htm

This is the former AMD PIC thin client/stripped down PC for emerging
markets. Runs a Geode GX or unspecified type. Apparently Data Evolution
Corporation bought up the PIC assets after AMD killed off the PIC program.
Unfortunately, no pricing data is available for now.

Re: [Astlinux-users] Add drivers 0.4

[Darrick H. <dha...@dj...>]

Manuel wrote:
> Kristian,
>
> Your patch not Works. When system boot the NIC is detected but DHCP fail to
> get an IP address. I have put a static IP and tried to make a ping. I see
> leds in NIC and switch flashing but not receive any packet. I don’t known
> where is the problem but following your patch I have compared de 2 r8169.c
> files from trunk and 0.4. I have seen many different and I have make a patch
> to include all the changes. When try to compile in 0.4 give some errors and
> not compile de module. I don’t know what will be my next step. This night
> it's possible I try again with trunk.
>
> Darrick,
> If you like you can remove the patch from svn or make an image including it,
> what you prefer.
>   
Sounds like the changes involve more than just the PCI-id for the 
device. Unfortunately that means it won't be supported on 0.4.5. I'll 
talk with Kristian and decide if we're going to upgrade the kernel in 
0.4 or just maintain it as a security fix branch. If he's anticipating a 
0.5 release in the next month or so, I'm not going to bother upgrading 
the kernel on 0.4. If it's going to be longer, I'll take a look at it, 
but it's going to be a few weeks.

Darrick

-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com

Re: [Astlinux-users] PCMCIA Support - VIA EPIA MII 1200

[Lenir S. <fla...@ya...>]

ok guys, the only difference that i could find is that in the previous pcmcia.mk, this file would call $(BUSYBOX_DIR)/examples/depmod.pl and now the new pcmcia.mk (rev. 758) now calls $(DEPMOD) which calls /sbin/depmod. 
When i try to compile with $(BUSYBOX_DIR)/examples/depmod.pl, it compiles fine. But with $(DEPMOD), it looks like the main reason why it's failing is because the LINUX_VERSION variable is set up wrong or not at all. If that is the case, then that means that any package that needs $(DEPMOD) is likely to fail.

Lenir Santiago <fla...@ya...> wrote: Hi guys,

ok...i've tried everything i can and i cant figure out why depmod.pl is looking for files in /opt/astlinux2/astlinux/trunk/build_i586/root/lib/modules/2.6.20-astlinux//lib/modules/2.6.17-gentoo-r7

somehow is adding /lib/modules/2.6.17-gentoo-r7 which of course has to do with the kernel on my PC. Any ideas? this was working on 0.4.4

Any help would be appreciated.

Lenir Santiago <fla...@ya...> wrote: I think you missed something on the updated files, this is what get when i try to compile:


/usr/bin/install -D -m 0755 package/pcmcia/pcmcia-init /opt/astlinux2/astlinux/trunk/build_i586/root/etc/init.d/pcmcia
rm -rf /opt/astlinux2/astlinux/trunk/build_i586/root/etc/pcmcia/cis
[ -d /opt/astlinux2/astlinux/trunk/build_i586/root/lib/modules/2.6.20-astlinux ] &&  \
        /sbin/depmod \
                -b /opt/astlinux2/astlinux/trunk/build_i586/root/lib/modules/2.6.20-astlinux/ \
                -F /opt/astlinux2/astlinux/trunk/build_i586/linux-2.6.20-astlinux/System.map \
                >  /opt/astlinux2/astlinux/trunk/build_i586/root/lib/modules/2.6.20-astlinux/modules.dep
WARNING: Couldn't open directory /opt/astlinux2/astlinux/trunk/build_i586/root/lib/modules/2.6.20-astlinux//lib/modules/2.6.17-gentoo-r7: No such file or directory
FATAL: Could not open /opt/astlinux2/astlinux/trunk/build_i586/root/lib/modules/2.6.20-astlinux//lib/modules/2.6.17-gentoo-r7/modules.dep.temp for writing: No such file or directory
make: ***  [/opt/astlinux2/astlinux/trunk/build_i586/pcmcia-cs-3.2.8/.modules.dep] Error 1

Kristian Kielhofner <kri...@gm...> wrote: On 3/6/07, Lenir Santiago  wrote:
> Well, i got PCMCIA to work on astlinux, however a few changes needed to be
> applied to  package/pcmcia/pcmcia.mk, /etc/init.d/pcmcia and /etc/rc, which
> i have attached on this  email. Also, i used the latest pcmcia-cs package
> (3.2.8) So now i have my system booting off a USB flash pen and using a CF
> card as the KD. and is working fine...Astlinux should consider putting this
> on the next release.
>
> p.s. Make sure you do a 'cardmgr eject' before starting the pcmcia services
> and 'cardmgr insert' after you have started the pcmcia service.
>

Lenir,

  Thank you for  your fixes.  I have included these (with slight mods) in trunk.

Thanks again!


-- 
Kristian Kielhofner

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn  cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

   

---------------------------------
It's here! Your new message!
Get  new  email alerts with the free Yahoo! Toolbar.-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
     

---------------------------------
Looking for earth-friendly autos? 
 Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center.  -------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

 
---------------------------------
TV dinner still cooling?
Check out "Tonight's Picks" on Yahoo! TV.

Re: [Astlinux-users] PCMCIA Support - VIA EPIA MII 1200

[Lenir S. <fla...@ya...>]

Hi guys,

ok...i've tried everything i can and i cant figure out why depmod.pl is looking for files in /opt/astlinux2/astlinux/trunk/build_i586/root/lib/modules/2.6.20-astlinux//lib/modules/2.6.17-gentoo-r7

somehow is adding /lib/modules/2.6.17-gentoo-r7 which of course has to do with the kernel on my PC. Any ideas? this was working on 0.4.4

Any help would be appreciated.

Lenir Santiago <fla...@ya...> wrote: I think you missed something on the updated files, this is what get when i try to compile:


/usr/bin/install -D -m 0755 package/pcmcia/pcmcia-init /opt/astlinux2/astlinux/trunk/build_i586/root/etc/init.d/pcmcia
rm -rf /opt/astlinux2/astlinux/trunk/build_i586/root/etc/pcmcia/cis
[ -d /opt/astlinux2/astlinux/trunk/build_i586/root/lib/modules/2.6.20-astlinux ] && \
        /sbin/depmod \
                -b /opt/astlinux2/astlinux/trunk/build_i586/root/lib/modules/2.6.20-astlinux/ \
                -F /opt/astlinux2/astlinux/trunk/build_i586/linux-2.6.20-astlinux/System.map \
                >  /opt/astlinux2/astlinux/trunk/build_i586/root/lib/modules/2.6.20-astlinux/modules.dep
WARNING: Couldn't open directory /opt/astlinux2/astlinux/trunk/build_i586/root/lib/modules/2.6.20-astlinux//lib/modules/2.6.17-gentoo-r7: No such file or directory
FATAL: Could not open /opt/astlinux2/astlinux/trunk/build_i586/root/lib/modules/2.6.20-astlinux//lib/modules/2.6.17-gentoo-r7/modules.dep.temp for writing: No such file or directory
make: *** [/opt/astlinux2/astlinux/trunk/build_i586/pcmcia-cs-3.2.8/.modules.dep] Error 1

Kristian Kielhofner <kri...@gm...> wrote: On 3/6/07, Lenir Santiago  wrote:
> Well, i got PCMCIA to work on astlinux, however a few changes needed to be
> applied to  package/pcmcia/pcmcia.mk, /etc/init.d/pcmcia and /etc/rc, which
> i have attached on this  email. Also, i used the latest pcmcia-cs package
> (3.2.8) So now i have my system booting off a USB flash pen and using a CF
> card as the KD. and is working fine...Astlinux should consider putting this
> on the next release.
>
> p.s. Make sure you do a 'cardmgr eject' before starting the pcmcia services
> and 'cardmgr insert' after you have started the pcmcia service.
>

Lenir,

  Thank you for your fixes.  I have included these (with slight mods) in trunk.

Thanks again!


-- 
Kristian Kielhofner

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn  cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

   

---------------------------------
It's here! Your new message!
Get  new email alerts with the free Yahoo! Toolbar.-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

  
---------------------------------
Looking for earth-friendly autos? 
 Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center.  

Re: [Astlinux-users] Add drivers 0.4

[Manuel <lis...@gm...>]

Kristian,

Your patch not Works. When system boot the NIC is detected but DHCP fail =
to
get an IP address. I have put a static IP and tried to make a ping. I =
see
leds in NIC and switch flashing but not receive any packet. I don=92t =
known
where is the problem but following your patch I have compared de 2 =
r8169.c
files from trunk and 0.4. I have seen many different and I have make a =
patch
to include all the changes. When try to compile in 0.4 give some errors =
and
not compile de module. I don=92t know what will be my next step. This =
night
it's possible I try again with trunk.

Darrick,
If you like you can remove the patch from svn or make an image including =
it,
what you prefer.


Kristian & Darrick thanks for all your efforts to help me,

--
Manuel



-----Mensaje original-----
De: ast...@li...
[mailto:ast...@li...] En nombre de =
Kristian
Kielhofner
Enviado el: lunes, 12 de marzo de 2007 17:26
Para: AstLinux Users Mailing List
Asunto: Re: [Astlinux-users] Add drivers 0.4

On 3/12/07, Darrick Hartman <dha...@dj...> wrote:
> Manuel wrote:
> > Darrick,
> >
> > I am again with my problems. Please, can you guide me how can I =
install
the
> > drivers for my NIC in AstLinux? Not in details only a orientation. =
This
> > weekend I have tried to make a package with the drivers from Realtek
without
> > success. In the drivers not appears a configure file only a makefile =
and
I
> > have tried several thinks but not works. My Linux knowledge is very
limited.
> > I am really very frustrated. If I use trunk the image file not boot. =
If
use
> > 0.4 I need to install a NIC and remove the ISDN card.
> >
> >
> Manuel,
>
> If I recall this was a realtek driver?  0.4 branch builds r8169 kernel
> module by default if you use either the i586 or VIA image.
>
> Did you try modprobe 8169?
>
> Can you do an lspci -v > file.txt then attach file.txt to an email to =
me
> so we can see exactly what hardware you are working with?  Also please
> supply the motherboard brand and model.
>
> Also tell us what specific astlinux image you are using?  If this is =
an
> image you built yourself, please try the i586-RC2 image available =
here:
> http://www.djhsolutions.com/astlinux
>
> Darrick
>

Darrick,

  Manuel's problem is that his card's PCI ID is too new for the driver
in 2.6.16.12.  He has already sent me the output of lspci and we have
confirmed that it does work with newer kernels.

Manuel,

  0.4 is the stable branch of AstLinux.  We are not going to change
kernel versions in the stable branch.  I have just committed a kernel
patch for the r8169 driver for 2.6.16.12 in the 0.4 branch that adds
the PCI IDs from the r8169 driver in 2.6.20.

  This is a trivial patch and it should not effect the quality of the
0.4 branch.  The next releases that Darrick releases should have this
patch.

--=20
Kristian Kielhofner

-------------------------------------------------------------------------=

Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share =
your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to
pa...@kr....