headers
Leon Woestenberg | 1 Mar 2006 22:07

[Voyage-linux] Fixed UGLY HACK on wiki - future PXE boot?

Hello,

Kim-man "Punky" TSE wrote:
> I am new to PXE.  If you have some good input for PXE, please add your 
> remarks in the wiki page so we could document the knowledge there.
>
I saw that older versions of Voyage-Linux had the Atheros (madwifi) 
driver *in* the kernel, is that right? That would allow PXE boot over 
WiFi I guess.

I now just took the 2.6.15 kernel plus patches plus config and then set 
the National Semiconductor Ethernet driver to be non-modular. That was 
the only thing needed (as far as I remember) that needed to be modified.

The rest was PXE server configuration (which can be tricky due to a mix 
of DHCP, PXELINUX, /etc/hosts.allow/deny, TFTP, NFS), kernel command 
line options (so that the Voyage Linux kernel booted over PXE will 
actually mount its root FS from the NFS server).

>
> If you have wonderful idea, please make use of the wiki 
> (wiki.voyage.hk).  It is a good knowledge sharing tool for the 
> community.  (I don't like dokuwiki right now, and want to move to 
> mediawiki, comments?).
Dunno, I found the wiki simple to work with and it looks user friendly. 
I have no experience with wiki backends so I really cannot advise.

Regards,

Leon.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Leon Woestenberg | 1 Mar 2006 22:10

[Voyage-linux] Atheros madwifi-ng

Hello,

I was driven to Voyage-Linux because I wanted a Linux 2.6 distro with 
madwifi-ng driver.

This new driver model allows Atheros chipsets to operate with virtual 
wireless instances.

One chipset can be a number of stations and a number of access points 
*at the same time*.

Is support for this present, or is someone working on it?

Regards,

Leon.
Permalink | Reply | 2 comments |
headers
arthur | 2 Mar 2006 18:34
Picon
Favicon

[Voyage-linux] Atheros madwifi-ng

Leon Woestenberg napisa?:

> 
> This new driver model allows Atheros chipsets to operate with virtual 
> wireless instances.
> 
> One chipset can be a number of stations and a number of access points 
> *at the same time*.
> 
> Is support for this present, or is someone working on it?

AFAIK, it can have a number of AP instances, but only one sta instance. 
I also enthusiastically tried this new driver, but it was so unstable on 
my aries 5212 cards that I've ended up switching back to the January 
release of Voyage with the madwifi-old drivers. The -ng drivers were 
causing my sta cards in 802.11a to go channel skipping whenever brought 
up, instead  of just sticking to the freq of the AP. Anyone else have 
the same problem? It seems to have been filed as a bug with ticket #433 
at madwifi.org
Permalink | Reply | 1 comment |
headers
Leon Woestenberg | 2 Mar 2006 20:34

[Voyage-linux] Atheros madwifi-ng

Hello,

On Thu, 02 Mar 2006 10:34:24 +0100, "arthur" <auriga <at> o2.pl> said:
> Leon Woestenberg napisa&#322;:
> 
> > 
> > This new driver model allows Atheros chipsets to operate with virtual 
> > wireless instances.
> > 
> > One chipset can be a number of stations and a number of access points 
> > *at the same time*.
> > 
> > Is support for this present, or is someone working on it?
> 
> AFAIK, it can have a number of AP instances, but only one sta instance. 
>
You are correct.

> release of Voyage with the madwifi-old drivers. The -ng drivers were 
> causing my sta cards in 802.11a to go channel skipping whenever brought 
> up, instead  of just sticking to the freq of the AP. Anyone else have 

Did you instantiate multiple virtual interfaces? If so, the order in
which you do seems to matter (at this point, due to a bug) and may cause
weird behaviour. I read this on the Wiki.

However, I will experiment a bit more once I get my antenna pigtails in.
It's hard to set up a wireless connection without an antenna (but
sometimes it works :-)).
(Continue reading)

Permalink | Reply | 0 comments |
headers
Greg | 2 Mar 2006 22:25
Favicon

[Voyage-linux] lm sensor

Hello

I recently upgraded to unstable with 2.6.15 kernel image. I Find that my 
LM sensor has stopped giving me love. Is there a kernel image with the 
relevant drivers compiled or is it a case of roll your own

Regards

Greg
Permalink | Reply | 3 comments |
headers
Kim-man "Punky" TSE | 3 Mar 2006 01:01
Favicon

[Voyage-linux] lm sensor

Hi Greg,

I believe you are using wrap?  So which kernel you has been using that 
lm sensors works.  Which related modules in your old kernel works?  And 
which part of lm senors not work?  I am getting no idea.

- Punky

Greg wrote:
> Hello
>
> I recently upgraded to unstable with 2.6.15 kernel image. I Find that 
> my LM sensor has stopped giving me love. Is there a kernel image with 
> the relevant drivers compiled or is it a case of roll your own
>
> Regards
>
> Greg
>
> _______________________________________________
> Voyage-linux mailing list
> Voyage-linux <at> list.voyage.hk
> http://list.voyage.hk/mailman/listinfo/voyage-linux

--

-- 
Regards,
Punky
P U N K N ! X . c o m
Technology + Lifestyle
(http://www.punknix.com)
(Continue reading)

Permalink | Reply | 2 comments |
headers
Kim-man "Punky" TSE | 3 Mar 2006 01:17
Favicon

[Voyage-linux] lm sensor

Greg,

OK.  I recalled I had seen same issue.  It had occurred once in my 
experience.  There is no /sys/bus/i2c/drivers/lm77/0-0048.  So you 
should check if the scx200_acb and lm77 drivers are loaded properly 
(lsmod).  If so please reload manually again. (rmmod and modprobe)

Just FYI.  In some newer voyage releases, you will have the follow lines 
in /etc/modules if you select WRAP option in voyage.update:

lm77
scx200_acb base=0x820,0

As you are upgrading and not a fresh install, you may not have these 
line.  But I don't know if this matters, just in case... 

- Punky

Kim-man "Punky" TSE wrote:
> Hi Greg,
>
> I believe you are using wrap?  So which kernel you has been using that 
> lm sensors works.  Which related modules in your old kernel works?  
> And which part of lm senors not work?  I am getting no idea.
>
> - Punky
>
> Greg wrote:
>> Hello
>>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Kay Obermueller | 3 Mar 2006 10:52
Picon

[Voyage-linux] IPSec, kame - racoon and shorewall on voyage

Hi all,
I'm new here, but Voyage seems to me very suitable, because I want a small
IPSec gateway and firewall. I would like to run it on a WRAP board. On a
normal Debian Sarge I already have such a gateway running on an
ordinary PC with a self compiled kernel 2.6.11 according to this little guide here:
http://lists.shorewall.net/pipermail/shorewall-users/2005-May/018358.html
or:
http://64.233.179.104/search?q=cache:KHlzy-SA-moJ:lists.shorewall.net/pipermail/shorewall-users/2005-May/018358.html+&hl=en&ct=clnk&cd=1&client=opera
(one can search for the posting in google, in case it seems inaccessible...)
These patches were used:
http://shorewall.net/pub/shorewall/contrib/IPSEC/2.6.11/
and from patch-o-matic-ng the policy patch.
Further I applied a h323 patch (of course not for ipsec..). Are these
patches also applied to the voyage kernels? Where (or how) can I find out
which patches were applied to voyage kernels?
At least this gives the same output as on my working machines:
'iptables -m policy --help'
'iptables -N foo -m policy --pol none'

Greets
Kay
Permalink | Reply | 1 comment |
headers
Stagg Shelton | 3 Mar 2006 14:56

[Voyage-linux] Voyage, Asterisk, Soekris Net4801

Hello,

I have been looking into different distributions to use for an asterisk 
PBX on a Soekris net4801.  I tried astlinux, but got really frusterated 
with the whole readonly nature of that system, and also had many 
difficulties getting stuff into it and working, such as AMP.  I started 
looking around last week for another distribution, and was about to try 
to make pebble linux work when I stumbled onto voyage.  Anyways, I'm not 
here to write a novel, I wanted to let you know what I have accomplished 
this week.

I have successfully implemented asterisk 1.2.4, zaptel 1.2.4, libpri 
1.2.2, addons 1.2.1, sounds 1.2.1, and a Digium TE110P single span T1/E1 
on my net4801 with voyage-0.2pre4.  I'm also running freePBX (formerly 
Asterisk Management Portal), apache2, php4.  Mysql Server is running on 
a remote server that this system will have access to.  I'm using a 4GB 
microdrive so disk capacity and disk writes shouldn't be an issue.  
Downside to microdrive is that I now have a mechanical device in an 
otherwise solid-state system. 

I had to make a new kernel to get some things in zaptel to work 
correctly, and to have the kernel built for the processor in the net4801.

I read on the website that asterisk was one of the goals for this 
distribution to take on.  I would like to contribute back what I have 
learned, and the kernel configuration changes that I made, but don't 
really know how to do that, so I figured this list would be a good place 
to start.

Stagg Shelton
(Continue reading)

Permalink | Reply | 1 comment |
headers
Kim-man "Punky" TSE | 3 Mar 2006 15:12
Favicon

[Voyage-linux] IPSec, kame - racoon and shorewall on voyage

Hi Kay,

As far as I know, the ipsec pom patch doesn't patch or compile 
successfully on 2.6.15.  Moreover, rebuild iptables package is a hurdle 
for me actually. 

To include IPSEC, kame and raccoon support, if you have the following, I 
can help to provide it in later voyage.
- ipsec kernel patches for 2.6.15
- iptables deb package (with source please) with policy patch.

Any volunteer?

- Punky

Kay Obermueller wrote:
> Hi all,
> I'm new here, but Voyage seems to me very suitable, because I want a small
> IPSec gateway and firewall. I would like to run it on a WRAP board. On a
> normal Debian Sarge I already have such a gateway running on an
> ordinary PC with a self compiled kernel 2.6.11 according to this little guide here:
> http://lists.shorewall.net/pipermail/shorewall-users/2005-May/018358.html
> or:
> http://64.233.179.104/search?q=cache:KHlzy-SA-moJ:lists.shorewall.net/pipermail/shorewall-users/2005-May/018358.html+&hl=en&ct=clnk&cd=1&client=opera
> (one can search for the posting in google, in case it seems inaccessible...)
> These patches were used:
> http://shorewall.net/pub/shorewall/contrib/IPSEC/2.6.11/
> and from patch-o-matic-ng the policy patch.
> Further I applied a h323 patch (of course not for ipsec..). Are these
> patches also applied to the voyage kernels? Where (or how) can I find out
(Continue reading)

Permalink | Reply | 0 comments |

Gmane