headers
mgrollman | 1 May 2007 01:16
Picon

Read/Write on CF Question for Voyage 0.3


I have built a number of systems using Voyage 0.2 and now Voyage 0.3.  
Both are great, but from time to time, with have an issue using 0.3 with 
a hard disk.

Often we add a small hard disk to our systems to record sensor data, 
still running Voyage itself from the CF.  There is something is the way 
our 0.2 systems handle the read/write status of the CF card that is 
different from he way it is handled in 0.3 that relates back to working 
with the hard disk.  Thus I am curious if there is a way to get the 
Voyage 0.3 to behave in this manner a bit more like the Voyage 0.2, as 
in the Voyage 0.3 version, we wind up with some junk data written to the 
CF card if we are not careful.

Let me explain the failure mode.  For some reason, when a hard disk 
failures in our 0.2 systems, by the time the application programs that 
access the drive are loaded, the CF card has been made read-only by the 
Voyage boot cycle.  However, if the 0.3 version (Etch) in the event of a 
hard disk failure, application programs will have started already that 
are accessing the files on the drive mount point, and this makes it 
impossible to remountro the CF card.  The net result is a bunch of 
sensor data that should be written to the hard disk gets written to the 
CF card instead.

I assume the reason the the CF is ever in a read/write state has 
something to do with preserving the boot log.  But if I am willing to 
forgo this benefit, what would I need to change in the Voyage startup to 
ensure that the CF card is read-only as early as possible in the boot cycle?

Any insights are greatly appreciated.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Kim-man "Punky" TSE | 1 May 2007 13:13
Favicon

Re: smbfs on 2.6.20 (0.3.1)

Andy,

Would you try cifs instead of smbfs to see if any different?

- Punky

Andy Brown wrote:
> Hi All,
> I'm having problems using smbfs to mount remote windows drives.
> An example of the command I'm using:
>
> mount -t smbfs -o username='backup',password='backup' 
> "//server1/backup" /mnt/
>
> This returns with:
> "Can't get /etc/mtab~ lock"
> (whether the drive is in read-only or read-write)
> And trying to access the mount-point fails with dmesg errors of:
> "smbfs: Unrecognized mount option (null)"
>
> And dies.
>
> Has anyone had similar, these mounts definately worked previously, so 
> I suspect something new has caused this, but can't put my finger on it 
> at present.
> Using smbclient to browse interactively works, so looks like its the 
> kernel fs module perhaps?
>
> Thanks in advance!
>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Kim-man "Punky" TSE | 1 May 2007 13:16
Favicon

Re: Read/Write on CF Question for Voyage 0.3

Hi Michael,

May be you can edit /etc/fstab to mount the CF as ro.

- Punky

mgrollman wrote:
>
>
> I have built a number of systems using Voyage 0.2 and now Voyage 0.3.  
> Both are great, but from time to time, with have an issue using 0.3 
> with a hard disk.
>
> Often we add a small hard disk to our systems to record sensor data, 
> still running Voyage itself from the CF.  There is something is the 
> way our 0.2 systems handle the read/write status of the CF card that 
> is different from he way it is handled in 0.3 that relates back to 
> working with the hard disk.  Thus I am curious if there is a way to 
> get the Voyage 0.3 to behave in this manner a bit more like the Voyage 
> 0.2, as in the Voyage 0.3 version, we wind up with some junk data 
> written to the CF card if we are not careful.
>
> Let me explain the failure mode.  For some reason, when a hard disk 
> failures in our 0.2 systems, by the time the application programs that 
> access the drive are loaded, the CF card has been made read-only by 
> the Voyage boot cycle.  However, if the 0.3 version (Etch) in the 
> event of a hard disk failure, application programs will have started 
> already that are accessing the files on the drive mount point, and 
> this makes it impossible to remountro the CF card.  The net result is 
> a bunch of sensor data that should be written to the hard disk gets
(Continue reading)

Permalink | Reply | 0 comments |
headers
Andreas Wisskirchen DG1KWA | 1 May 2007 14:26
Picon

Problem with WLAN-Card

Hello,
 
I have a problem with a wlan-card in my wrap-board. The card will not run, here is the output from lspci:
 

00:0d.0 Ethernet controller: Atheros Communications, Inc. AR5005G 802.11abg NIC (rev 01)
        Subsystem: Atheros Communications, Inc. Unknown device 2052
        Flags: bus master, medium devsel, latency 168, IRQ 12
        Memory at 80000000 (32-bit, non-prefetchable) [size=64K]
        Capabilities: [44] Power Management version 2
I think the madwifi-driver will don't support this chipset.
 
Do you have any idee ?
 
Thank you.
 
Regards 
  Andreas 
 
_______________________________________________
Voyage-linux mailing list
Voyage-linux@...
http://list.voyage.hk/mailman/listinfo/voyage-linux
Permalink | Reply | 0 comments |
headers
Kim-man "Punky" TSE | 1 May 2007 14:56
Favicon

Re: Problem with WLAN-Card

Hi Andreas,

I have no problem even with AR5006X single chip Atheros.  Let us know 
the following information:

- Atheros cards model and spec.
- voyage linux version (run uname -a)
- output of "dmesg|grep ath"
- WRAP board BIOS ver.

======================================
00:0d.0 Ethernet controller: Atheros Communications, Inc. AR5006X 
802.11abg NIC(rev 01)
        Subsystem: Atheros Communications, Inc. EnGenius EMP-8602 
(400mw) or Compex WLM54AG
        Flags: bus master, medium devsel, latency 168, IRQ 12
        Memory at 80000000 (32-bit, non-prefetchable) [size=64K]
        Capabilities: [44] Power Management version 2

voyage:~# dmesg|grep ath
ath_hal: module license 'Proprietary' taints kernel.
ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
ath_pci: 0.9.4.5 (0.9.3)
ath_rate_sample: 1.2 (0.9.3)
======================================

- Punky

Andreas Wisskirchen DG1KWA wrote:
> Hello,
>  
> I have a problem with a wlan-card in my wrap-board. The card will not 
> run, here is the output from lspci:
>  
>
> 00:0d.0 Ethernet controller: Atheros Communications, Inc. AR5005G 
> 802.11abg NIC (rev 01)
>         Subsystem: Atheros Communications, Inc. Unknown device 2052
>         Flags: bus master, medium devsel, latency 168, IRQ 12
>         Memory at 80000000 (32-bit, non-prefetchable) [size=64K]
>         Capabilities: [44] Power Management version 2
> I think the madwifi-driver will don't support this chipset.
>  
> Do you have any idee ?
>  
> Thank you.
>  
> Regards 
>   Andreas 
> ------------------------------------------------------------------------
>
> _______________________________________________
> Voyage-linux mailing list
> Voyage-linux@...
> http://list.voyage.hk/mailman/listinfo/voyage-linux
>   

--

-- 

P U N K N ! X  . c o m
Technology + Lifestyle
(http://www.punknix.com)

V O Y A G E . H K - http://www.voyage.hk
Linux - voyage-0.3.1 is released!
Store - New stock for Senao NMP8601 and NMP8602 (100mW)!
      - New low price for Senao NMP-8602 Plus (400mW)!
Permalink | Reply | 0 comments |
headers
Andy Brown | 2 May 2007 11:34
Picon
Favicon
Gravatar

Re: smbfs on 2.6.20 (0.3.1)

Absolutely spot-on, sorry about that I'd not followed the samba 
progression to cifs.

Thanks once again.

Andy.

Kim-man "Punky" TSE wrote:
> Andy,
> 
> Would you try cifs instead of smbfs to see if any different?
> 
> - Punky
> 
> Andy Brown wrote:
>> Hi All,
>> I'm having problems using smbfs to mount remote windows drives.
>> An example of the command I'm using:
>>
>> mount -t smbfs -o username='backup',password='backup' 
>> "//server1/backup" /mnt/
>>
>> This returns with:
>> "Can't get /etc/mtab~ lock"
>> (whether the drive is in read-only or read-write)
>> And trying to access the mount-point fails with dmesg errors of:
>> "smbfs: Unrecognized mount option (null)"
>>
>> And dies.
>>
>> Has anyone had similar, these mounts definately worked previously, so 
>> I suspect something new has caused this, but can't put my finger on it 
>> at present.
>> Using smbclient to browse interactively works, so looks like its the 
>> kernel fs module perhaps?
>>
>> Thanks in advance!

--

-- 
Andy
e: andy  <at>  thebmwz3.co.uk
e: andy  <at>  broadcast-tech.co.uk
w: http://www.thebmwz3.co.uk
w: http://www.broadcast-tech.co.uk
Permalink | Reply | 0 comments |
headers
e | 8 May 2007 14:43

Beginner's questions

Hi - I'm just starting getting into Voyage-Linus on a net4801 board. The
board hasn't arrived yet but I have uploaded CL image to the CompactFlash
card and I'm waiting to go.

I copied the image with physidskwrite.exe. No formating of the CF was
done, I prweume this was not necessary, but does it mean that the CF
memory is not acessible to me when the system is running?

I have been concerned about the lifetime of CF. Does VL run form the CF or
does it copy to a RamDisk and run form there?

The purpose is to run my home automation under Java from this device,
which I already do - either from a Java embedded device or a PC. One gives
me a compact solution and the other the power. I'm hoping that the new
setup will give both.

Ta,
Eddie.
Permalink | Reply | 0 comments |
headers
Marek Andricik | 9 May 2007 10:07

iptables + ipp2p

Hi,

is anybody using ipp2p in stable voyage? I can see that kernel is
patched but iptables is not ready (according to mailing list archive
and simple test :)

What are my options if I want to use ipp2p? Patching iptables by myself?
Vanila version? Is there already patched version somewhere? I could not
find it. Thanks for any suggestions.

Marek
--

-- 
"You are hologram too?"
Permalink | Reply | 0 comments |
headers
Robert Rawlins - Think Blue | 9 May 2007 11:25
Picon
Favicon
Gravatar

Time/Date Issues

Hello Guys,

 

I’ve used ‘date –s’ command to set a date and time on my voyage system, but when the box boots up without an internet connection it goes back to 31/12/1999. This is an embedded system that will quite often boot without a net connection, so i really need to get this sorted, does anyone know the best way to set the date/time and have it keep it regardless of being connected to the net or not?

 

Thanks,

 

Rob

_______________________________________________
Voyage-linux mailing list
Voyage-linux@...
http://list.voyage.hk/mailman/listinfo/voyage-linux
Permalink | Reply | 0 comments |
headers
Mike O'Connor | 9 May 2007 11:55

Re: Time/Date Issues

Hi Robert

You will need to get a board which has a battery for the clock.

Mike

Robert Rawlins - Think Blue wrote:
>
> Hello Guys,
>
>  
>
> I’ve used ‘date –s’ command to set a date and time on my voyage
> system, but when the box boots up without an internet connection it
> goes back to 31/12/1999. This is an embedded system that will quite
> often boot without a net connection, so i really need to get this
> sorted, does anyone know the best way to set the date/time and have it
> keep it regardless of being connected to the net or not?
>
>  
>
> Thanks,
>
>  
>
> Rob
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Voyage-linux mailing list
> Voyage-linux@...
> http://list.voyage.hk/mailman/listinfo/voyage-linux
>
Permalink | Reply | 1 comment |

Gmane