headers
Xavier Martinez | 2 Jun 2008 14:03
Picon

Re: madwifi trunk r3573 + adhoc tests on voyage

Finally (with the help of a developer) if managed to compile the
newest madwifi driver and got it installed on a WRAP board with two
CM9 cards. However, it only ups one interface (wifi0) during boot.
Doing a "ifup ath1" after boot wakes up the second interface, so it is
not a problem of configuration file. Dmesg doesn't show any error
message. Any idea?

Here is my /etc/network/interfaces:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
        address 10.225.1.1
        netmask 255.255.255.0
        gateway 10.225.1.3

auto ath0
iface ath0 inet static
       address 10.225.0.49
       netmask 255.255.255.248
        pre-up wlanconfig ath0 create wlandev wifi0 wlanmode sta
        pre-up iwconfig ath0 channel 11
        up iwconfig ath0 essid guifibages-supernode-SC-PG
        up sysctl -w dev.wifi0.diversity=0
        up sysctl -w dev.wifi0.txantenna=2
        up sysctl -w dev.wifi0.rxantenna=2
        up athctrl i wifi0 -d 3000
        up iwpriv ath0 mode 3
(Continue reading)

Permalink | Reply | 0 comments |
headers
Xavier Martinez | 2 Jun 2008 16:19
Picon

Re: madwifi trunk r3573 + adhoc tests on voyage

I've put "options ath_pci autocreate=none" in /etc/modprobe.d/madwifi
and now it wakes up both wireless interfaces on boot.
Let's see if this madwifi version is stable...

Thanks!

2008/6/2 Petr Lascak <hwsoft@...>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Xavier Martinez napsal(a):
> | Finally (with the help of a developer) if managed to compile the
> | newest madwifi driver and got it installed on a WRAP board with two
> | CM9 cards. However, it only ups one interface (wifi0) during boot.
> | Doing a "ifup ath1" after boot wakes up the second interface, so it is
> | not a problem of configuration file. Dmesg doesn't show any error
> | message. Any idea?
> |
>
> I think that you have only insmod ath_pci in /etc/modules without the
> autocreate=none. Then you must first run wlanconfig ath1 destroy, and
> after this will be ath1 get up OK.
>
>
> - --
> ~    Petr Lascak
> ~    ITF FreeNet Liberec
> ~    http://www.lbcfree.net/
> ~    NFX founder http://www.nfx.cz/
> -----BEGIN PGP SIGNATURE-----
(Continue reading)

Permalink | Reply | 1 comment |
headers
Ryan Harden | 2 Jun 2008 18:17
Picon

NO_PUBKEY Errors with apt-get update


Hello,

I booted the latest 0.5.0 live-cd and installed it to a hard drive.
Upon rebooting I went to run apt-get update and apt-get dist-upgrade to
mitigate the SSL vulnerability. Unfortunately I was met with the
following errors. My exact method of doing this worked flawlessly two
weeks ago.

W: GPG error: http://www.voyage.hk ./ Release: The following signatures
couldn't be verified because the public key is not available: NO_PUBKEY
FC05444194EFBFA6
W: GPG error: http://www.voyage.hk ./ Release: The following signatures
couldn't be verified because the public key is not available: NO_PUBKEY
FC05444194EFBFA6
W: You may want to run apt-get update to correct these problems

I've obviously ran apt-get update again and the problem persists. I have
verified that the key 94EFBFA6 doesn't exist on any known keyservers. Is
there something I'm missing here?

/Ryan

--
Ryan M. Harden, BS, KC9IHX		Office: 217-265-5192
CITES - Network Engineering		Cell:  	630-363-0365
2130 Digital Computer Lab		Fax:    217-244-7089
1304 W. Springfield	 		email:  hardenrm@...
Urbana, IL  61801
(Continue reading)

Permalink | Reply | 1 comment |
headers
Kim-man 'Punky' TSE | 3 Jun 2008 03:24
Favicon

Re: NO_PUBKEY Errors with apt-get update

Hi all,

This is secure apt feature that I've just added to 0.5 and experimental 
repositories.  However, although apt-get complains about the missing, 
you could still be able to add the packages from voyage apt repository.

To get rid of the error message:
    voyage:~# wget http://www.voyage.hk/dists/experimental/archive.key 
-O - | apt-key add -

Regards,
Punky

Ryan Harden wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello,
>
> I booted the latest 0.5.0 live-cd and installed it to a hard drive.
> Upon rebooting I went to run apt-get update and apt-get dist-upgrade to
> mitigate the SSL vulnerability. Unfortunately I was met with the
> following errors. My exact method of doing this worked flawlessly two
> weeks ago.
>
> W: GPG error: http://www.voyage.hk ./ Release: The following signatures
> couldn't be verified because the public key is not available: NO_PUBKEY
> FC05444194EFBFA6
> W: GPG error: http://www.voyage.hk ./ Release: The following signatures
> couldn't be verified because the public key is not available: NO_PUBKEY
(Continue reading)

Permalink | Reply | 0 comments |
headers
Dimitri Michaux | 3 Jun 2008 11:27
Picon

Installing samba server on voyage

Hey,

I've just installed voyage on my little home server and I'm loving it,
everything works and it is easy to install.

But, I can't get samba server to behave. I can install it and it will
work, but then it gets impossible for me to mount the root file system
as read only. So, I used lsof to find out what was going on here and
it looks like samba is opening some files in /etc and tries to write
to them.

Is there anyway to make that I can mount these folders in the same way
as /var is mounted? Or does someone know how you can get samba to work
with voyage.

Regards,
Dimitri
Permalink | Reply | 0 comments |
headers
Ryan Harden | 3 Jun 2008 21:13
Picon

Re: Post-install connection issues


Try this:

# cat /proc/sys/net/ipv4/ip_forward
If that is 0 then...
# echo 1 > /proc/sys/net/ipv4/ip_forward

If that helps, you'll need to add it to a script that runs at boot. It
basically tells the box that it's okay to take packets from one
interface and send them along through another.

/Ryan

Dave Rush wrote:
| So I have 050 installed on my alix 2.c3.
|
| The alix can get out just fine, and I can install things with apt-get.
Pinging
| from the alix works. but any devices connected behind it are unable to
get out
| to even the 192.168.1.0 network set up by the PP router, which dhcps
the alix.
|
| Everything on the router is default. All I've done is configure the
interfaces
| by uncommenting them, and added the nat script on connection of eth0.
Did I do
| that right, or is there something else that needs to be done to allow
access to
| the outside world? I don't see ANY documentation on this, or anyone
(Continue reading)

Permalink | Reply | 0 comments |
headers
Nick L. | 4 Jun 2008 01:10
Picon

cpio and language locale error

In trying to update my ALIX 32c today I get:

The following packages will be upgraded:
  cpio libvorbis0a libvorbisenc2 libvorbisfile3
4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 192kB/325kB of archives.
After unpacking 8192B disk space will be freed.
Do you want to continue [Y/n]?
WARNING: The following packages cannot be authenticated!
  cpio libvorbis0a libvorbisenc2 libvorbisfile3
Authentication warning overridden.
Get:1 http://security.debian.org stable/updates/main libvorbis0a 1.1.2.dfsg-1.4 [98.2kB]
Get:2 http://security.debian.org stable/updates/main libvorbisenc2 1.1.2.dfsg-1.4 [75.3kB]
Get:3 http://security.debian.org stable/updates/main libvorbisfile3 1.1.2.dfsg-1.4 [18.9kB]
Fetched 192kB in 0s (612kB/s)
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
        LANGUAGE = (unset),
        LC_ALL = (unset),
        LANG = "en_US"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
debconf: delaying package configuration, since apt-utils is not installed
(Reading database ... 8507 files and directories currently installed.)
Preparing to replace cpio 2.6-18 (using .../cpio_2.6-18.1+etch1_i386.deb) ...
Unpacking replacement cpio ...
Replaced by files in installed package tar ...
dpkg: error processing /var/cache/apt/archives/cpio_2.6-18.1+etch1_i386.deb (--unpack):
 unable to create `./usr/share/locale/da/LC_MESSAGES/cpio.mo': No such file or directory
Preparing to replace libvorbis0a 1.1.2.dfsg-1.3 (using .../libvorbis0a_1.1.2.dfsg-1.4_i386.deb) ...
Unpacking replacement libvorbis0a ...
Preparing to replace libvorbisenc2 1.1.2.dfsg-1.3 (using .../libvorbisenc2_1.1.2.dfsg-1.4_i386.deb) ...
Unpacking replacement libvorbisenc2 ...
Preparing to replace libvorbisfile3 1.1.2.dfsg-1.3 (using .../libvorbisfile3_1.1.2.dfsg-1.4_i386.deb) ...
Unpacking replacement libvorbisfile3 ...
Errors were encountered while processing:
 /var/cache/apt/archives/cpio_2.6-18.1+etch1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
voyage:/home/nick#

-----------------------------------------------------------------------------------------------------------------------------------------------

How do I resolve the locale error? What about cpio?

_______________________________________________
Voyage-linux mailing list
Voyage-linux@...
http://list.voyage.hk/mailman/listinfo/voyage-linux
Permalink | Reply | 0 comments |
headers
Kim-man 'Punky' TSE | 4 Jun 2008 03:39
Favicon

Re: Post-install connection issues

Hi Dave,

I think you did it wrong, if eth0 is for outside internet and eth1 for 
internal.  If you look at the original example in 
/etc/network/interfaces, it look like below:

#auto wlan0
#iface wlan0 inet static
#        address 10.1.10.1
#        netmask 255.255.255.0
#        broadcast 10.1.10.255
#        up iwconfig wlan0 essid voyage mode Master
#        up nat.sh wlan0 eth0 "10.1.10.0/24"

replace wlan0 with eth1, and of cource remove iwconfig line.

Regards,
Punky

Dave Rush wrote:
> So I have 050 installed on my alix 2.c3.
>
> The alix can get out just fine, and I can install things with apt-get. Pinging
> from the alix works. but any devices connected behind it are unable to get out
> to even the 192.168.1.0 network set up by the PP router, which dhcps the alix.
>
> Everything on the router is default. All I've done is configure the interfaces
> by uncommenting them, and added the nat script on connection of eth0. Did I do
> that right, or is there something else that needs to be done to allow access to
> the outside world? I don't see ANY documentation on this, or anyone else with
> the same problem so I'm thinking that I've somehow screwed up the one line of
> code I've typed. ;)
> This would be a good entry for the wiki, the post-install config. 
>
> Thanks in advance.
>
> -------------
> voyage:~# cat /etc/network/interfaces
> # Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or
> # /usr/share/doc/ifupdown/examples for more information.
> auto lo
> iface lo inet loopback
>
> auto eth0
> iface eth0 inet dhcp
>         up nat.sh eth0 eth1 "10.1.20.0/24"
> auto eth1
> iface eth1 inet static
>        address 10.1.20.1
>        netmask 255.255.255.0
>        broadcast 10.1.20.255
>
> auto eth2
> iface eth2 inet static
>        address 10.1.30.1
>        netmask 255.255.255.0
>        broadcast 10.1.30.255
>
>
>
> _______________________________________________
> Voyage-linux mailing list
> Voyage-linux@...
> http://list.voyage.hk/mailman/listinfo/voyage-linux
>   

--

-- 
Regards,
Punky

Voyage Solutions (http://solution.voyage.hk)
* Embedded Solutions and Systems
  - Mesh Networking, Captive Portal, IP Surveillance, VoIP/PBX
  - Network Engineering, Development Platform and Consultation
Permalink | Reply | 2 comments |
headers
Dave Rush | 4 Jun 2008 06:47
Picon

Re: Post-install connection issues

Oh good, I'm relieved that it was that simple, thank you.

I read it here, not from any Voyage linux documentation.
http://www.enterprisenetworkingplanet.com/nethub/article.php/3700026

Thanks again!

On 6/3/08, Kim-man 'Punky' TSE <punkytse@...> wrote:
> Hi Dave,
>
> I think you did it wrong, if eth0 is for outside internet and eth1 for
> internal.  If you look at the original example in
> /etc/network/interfaces, it look like below:
>
> #auto wlan0
> #iface wlan0 inet static
> #        address 10.1.10.1
> #        netmask 255.255.255.0
> #        broadcast 10.1.10.255
> #        up iwconfig wlan0 essid voyage mode Master
> #        up nat.sh wlan0 eth0 "10.1.10.0/24"
>
> replace wlan0 with eth1, and of cource remove iwconfig line.
>
> Regards,
> Punky
>
> Dave Rush wrote:
>> So I have 050 installed on my alix 2.c3.
>>
>> The alix can get out just fine, and I can install things with apt-get.
>> Pinging
>> from the alix works. but any devices connected behind it are unable to get
>> out
>> to even the 192.168.1.0 network set up by the PP router, which dhcps the
>> alix.
>>
>> Everything on the router is default. All I've done is configure the
>> interfaces
>> by uncommenting them, and added the nat script on connection of eth0. Did
>> I do
>> that right, or is there something else that needs to be done to allow
>> access to
>> the outside world? I don't see ANY documentation on this, or anyone else
>> with
>> the same problem so I'm thinking that I've somehow screwed up the one line
>> of
>> code I've typed. ;)
>> This would be a good entry for the wiki, the post-install config.
>>
>> Thanks in advance.
>>
>> -------------
>> voyage:~# cat /etc/network/interfaces
>> # Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or
>> # /usr/share/doc/ifupdown/examples for more information.
>> auto lo
>> iface lo inet loopback
>>
>> auto eth0
>> iface eth0 inet dhcp
>>         up nat.sh eth0 eth1 "10.1.20.0/24"
>> auto eth1
>> iface eth1 inet static
>>        address 10.1.20.1
>>        netmask 255.255.255.0
>>        broadcast 10.1.20.255
>>
>> auto eth2
>> iface eth2 inet static
>>        address 10.1.30.1
>>        netmask 255.255.255.0
>>        broadcast 10.1.30.255
>>
>>
>>
>> _______________________________________________
>> Voyage-linux mailing list
>> Voyage-linux@...
>> http://list.voyage.hk/mailman/listinfo/voyage-linux
>>
>
>
> --
> Regards,
> Punky
>
> Voyage Solutions (http://solution.voyage.hk)
> * Embedded Solutions and Systems
>   - Mesh Networking, Captive Portal, IP Surveillance, VoIP/PBX
>   - Network Engineering, Development Platform and Consultation
>
> 	
>
>
Permalink | Reply | 1 comment |
headers
Stuart Poulton | 4 Jun 2008 12:48
Picon
Picon

Re: Voyage Latest and Alix2c3

Hi,

Thanks, now working a treat.

I've got apt working, and have tried to install gnu c onto the alix, however 
I get the following when trying to compile some software locally.

voyage:~/he220stat-0x03# ./configure
checking for gcc... gcc
checking for C compiler default output file name... configure: error: C 
compiler cannot create executables
See `config.log' for more details.

configure:1627: $? = 0
configure:1629: gcc -v </dev/null >&5
Using built-in specs.
Target: i486-linux-gnu
Configured with: 
../src/configure -v --enable-languages=c,c++,fortran,objc,obj-c++,treelang --prefix=/usr 
 --enabl
e-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext 
 --enable-threads=posix --enable-nls
--program-suffix=-4.1 --enable-__cxa_atexit --enable-clocale=gnu --enable-libstdcxx-debug 
 --enable-mpfr --with-tu
ne=i686 --enable-checking=release i486-linux-gnu
Thread model: posix
gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)
configure:1632: $? = 0
configure:1634: gcc -V </dev/null >&5
gcc: '-V' option must have argument
configure:1637: $? = 1
configure:1660: checking for C compiler default output file name
configure:1663: gcc    conftest.c  >&5
/usr/bin/ld: crt1.o: No such file: No such file or directory
collect2: ld returned 1 exit status
configure:1666: $? = 1
configure: failed program was:
| /* confdefs.h.  */
|
| #define PACKAGE_NAME "FULL-PACKAGE-NAME"
| #define PACKAGE_TARNAME "full-package-name"
| #define PACKAGE_VERSION "VERSION"
| #define PACKAGE_STRING "FULL-PACKAGE-NAME VERSION"
| #define PACKAGE_BUGREPORT "BUG-REPORT-ADDRESS"
| /* end confdefs.h.  */
|
| int
| main ()
| {
|
|   ;
|   return 0;
| }
configure:1705: error: C compiler cannot create executables
See `config.log' for more details.

----- Original Message ----- 
From: "Kim-man 'Punky' Tse" <punkytse@...>
To: "Stuart Poulton" <stuart.poulton@...>
Cc: <voyage-linux@...>
Sent: Friday, May 30, 2008 7:44 PM
Subject: Re: [Voyage-linux] Voyage Latest and Alix2c3

> Hi Stuart,
>
> Please read this:
>
> http://linux.voyage.hk/?q=node/30
>
> You need latest bios if you run Voyage Linux 0.5.0.
>
> Regards,
> Punky
>
>
> Stuart Poulton wrote:
>> Hi All,
>>  Just started out with voyage on my alix2c3, installed to the CF being 
>> careful to select ALIX as the board type.. I get the following, it 
>> appears to hang partway through booting, any pointer gratefully received.
>>  PC Engines ALIX.2 v0.98b                       640 KB Base Memory 
>> 261120 KB Extended Memory                        01F0 Master 044A SMI 
>> MODEL                         Phys C/H/S 15473/16/63 Log C/H/S 970/255/63 
>> LBA                                              GRUB Loading stage1.5.
>> GRUB loading, please wait...
>>     GNU GRUB  version 0.97  (640K lower / 261120K upper memory) 
>> +-------------------------------------------------------------------------+
>>  | voyage-linux-30May08
>>  Booting 'voyage-linux-30May08'                               root 
>> (hd0,0)           Filesystem type is ext2fs, partition type 0x83 
>> kernel /vmlinuz root=LABEL=ROOT_FS  console=ttyS0,38400n8
>>    [Linux-bzImage, setup=0x2800, size=0x14d9d8] 
>> initrd /initrd.img                 [Linux-initrd  <at>  0xfdf3000, 0x1fcfd0 
>> bytes]                                            Linux version 
>> 2.6.23-486-voyage (2.6.23-2) (root <at> punknix-uml <mailto:root <at> punknix-uml>) 
>> (gcc version 4.1.2
>>  20061115 (prerelease) (Debian 4.1.1-21)) #1 PREEMPT Wed May 21 15:31:49 
>> GMT 200
>> 8
>> BIOS-provided phy              BIOS-e820: 0000000000000000 - 
>> 00000000000a0000 (usable) 
>> BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) 
>> BIOS-e820: 0000000000100000 - 0000000010000000 (usable) 
>> BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved) 
>> 0MB HIGHMEM available.                     256MB LOWMEM available. 
>> Zone PFN ranges:               DMA             0 ->     4096 
>> Normal       4096 ->    65536                              HighMem 
>> 65536 ->    65536                              Movable zone start PFN for 
>> each node                                   early_node_map[1] active PFN 
>> ranges                                  0:        0 ->    65536 
>> DMI not present or invalid                       Allocating PCI resources 
>> starting at 20000000 (gap: 10000000:eff00000)
>> Built 1 zonelists in Zone order.  Total pages: 65024 
>> Kernel command line: root=LABEL=ROOT_FS  console=ttyS0,38400n8
>> No local APIC present or hardware disabled 
>> Initializing CPU#0                 PID hash table entries: 1024 (order: 
>> 10, 4096 bytes) 
>> Detected 498.048 MHz processor.                              Console: 
>> colour dummy device 80x25
>> console [ttyS0] enabled
>> Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
>> Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
>> Memory: 254452k/262144k available (1808k kernel code, 7124k reserved, 
>> 640k data,
>>  164k init, 0k highmem)
>> virtual kernel memory layout:
>>     fixmap  : 0xfffac000 - 0xfffff000   ( 332 kB)
>>     pkmap   : 0xff800000 - 0xffc00000   (4096 kB)
>>     vmalloc : 0xd0800000 - 0xff7fe000   ( 751 MB)
>>     lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
>>       .init : 0xc0368000 - 0xc0391000   ( 164 kB)
>>       .data : 0xc02c4021 - 0xc036419c   ( 640 kB)
>>       .text : 0xc0100000 - 0xc02c4021   (1808 kB)
>> Checking if this processor honours the WP bit even in supervisor mode... 
>> Ok.
>> Calibrating delay using timer specific routine.. 997.07 BogoMIPS 
>> (lpj=498536)
>> Mount-cache hash table entries: 512
>> CPU: L1 I Cache: 64K (32 bytes/line), D cache 64K (32 bytes/line)
>> CPU: L2 Cache: 128K (32 bytes/line)
>> Compat vDSO mapped to ffffe000.
>> CPU: AMD Geode(TM) Integrated Processor by AMD PCS stepping 02
>> Checking 'hlt' instruction... OK.
>> NET: Registered protocol family 16
>>  ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Voyage-linux mailing list
>> Voyage-linux@...
>> http://list.voyage.hk/mailman/listinfo/voyage-linux
>>
>
>
Permalink | Reply | 0 comments |

Gmane