Re: Soekris net5501 and voyage 0.4.0

Hi Hans,

My patch didn't release, although this patch could be found from the 
web, this is not the exact patch I have.

Secondly, can you show me "dmesg|grep geode-mfgpt".  This output will 
let me know if you are using the correct kernel image.  My outboard from 
alix board shows:

geode-mfgpt:  6 timers available.
geode-mfgpt:  Registered timer 1

The first line indicates the built-in kernel code detected a Geode GX/LX 
processor and geode-mfgpt is enabled for 6 timer
The second lines shows wheb geode-wdt is loaded and it registers one 
timer from geode-mfgpt for watchdog.

Regards,
Punky

Hans Harder wrote:
> Punky,
>
> I was checking the config file for the kernel and I saw this:
> #
> # Processor type and features
> ...
> # CONFIG_MGEODE_LX is not set
>
> Should the MGEODE_LX not be set, I saw in the patch for the driver of 

Re: Soekris net5501 and voyage 0.4.0

Hi Punky,

voyage:~# dmesg|grep geode-mfgpt
geode-mfgpt:  Error initalizing the timers

Well its build in, only it goes wrong
I can imagine that the geode-wdt module then goes wrong

Hans

> Hi Hans,
>
> My patch didn't release, although this patch could be found from the
> web, this is not the exact patch I have.
>
> Secondly, can you show me "dmesg|grep geode-mfgpt".  This output will
> let me know if you are using the correct kernel image.  My outboard from
> alix board shows:
>
> geode-mfgpt:  6 timers available.
> geode-mfgpt:  Registered timer 1
>
> The first line indicates the built-in kernel code detected a Geode GX/LX
> processor and geode-mfgpt is enabled for 6 timer
> The second lines shows wheb geode-wdt is loaded and it registers one
> timer from geode-mfgpt for watchdog.
>
> Regards,
> Punky
>

Re: Soekris net5501 and voyage 0.4.0

Hi Hans,

This is strange.  geode-mfgpt is not board specific and should works for 
all standard Geode GX/LX + CS5536 companion chipset. 

FYI, the code that return "Error initailizing the timers" are below:

if ((ret = pci_enable_device_bars(pdev, 1 << MFGPT_PCI_BAR)))
    goto err;

if ((ret = pci_request_region(pdev, MFGPT_PCI_BAR, "geode-mfgpt")))
    goto err;

where MFGPT_PCI_BAR is 2;

Regards,
Punky

Hans Harder wrote:
> Hi Punky,
>
> voyage:~# dmesg|grep geode-mfgpt
> geode-mfgpt:  Error initalizing the timers
>
> Well its build in, only it goes wrong
> I can imagine that the geode-wdt module then goes wrong
>
> Hans
>
>   

Re: Soekris net5501 and voyage 0.4.0

On Mon, Jul 02, 2007 at 12:19:26PM +0800, Punky Tse wrote:
> This is strange.  geode-mfgpt is not board specific and should works for 
> all standard Geode GX/LX + CS5536 companion chipset. 

no idea if that's related at all, but after upgrading comBIOS to 1.31b
on a net4526 i had a *LOT* of problems like oops, invalid opcode and
bad page allocation ...
the comBIOS code seems to be buggy somewhere :(
just for information...

  --Jan

_______________________________________________
Voyage-linux mailing list
Voyage-linux@...
http://list.voyage.hk/mailman/listinfo/voyage-linux

RE: RE: quick voyage boot

Hi,
I don't know eactly what is it that u did.
If i do (u can put them in a file and make it
executable):

/etc/init.d/networking restart
echo "networkig done"

it takes a long time for the networking to complete
after which "networking done" is displayed.

On the other hand if i do:

/etc/init.d/networking restart &
echo "networkig done"

"networking done" is displayed immediately whilst
/etc/init.d/..... keeps running. You may go further in
silencing it by sending the output to /dev/null.

Please post to the list to benifit from a lot more
people.

Best Regards,
solo.

--- Think Blue Media <joe.ross@...>
wrote:

> Thanks for the help Solomon,

Re: quick voyage boot

Hi all,

1. remove "auto eth0" in /etc/network/interfaces.  it makes dhclient not 
requesting DHCP lease
2. udev, again, is the evil.  Remove z25_persistent-net.rules and 
z45_persistent-net-generator.rules under /etc/udev/rules.d before copy 
over to CF.

- Punky

Solomon Asare wrote:
> Hi,
> I don't know eactly what is it that u did.
> If i do (u can put them in a file and make it
> executable):
>
> /etc/init.d/networking restart
> echo "networkig done"
>
> it takes a long time for the networking to complete
> after which "networking done" is displayed.
>
> On the other hand if i do:
>
> /etc/init.d/networking restart &
> echo "networkig done"
>
> "networking done" is displayed immediately whilst
> /etc/init.d/..... keeps running. You may go further in
> silencing it by sending the output to /dev/null.

Re: quick voyage boot

Hi Joe,

Please reply to the list so that others is able to add comments

Take a look to dhclient.conf, may be some setting there yo can control 
timeout and retry.

- Punky

Think Blue Media wrote:
> Hi punky,
>
> I removed auto eth0 as you suggested however now it doesn't request an IP at
> all. Is it possible to make it just request once and if it doesn't get a
> response then carry on with the boot as opposed to reattempting over and
> over which holds up the boot process massively.
>
> Cheers
>
> Joe
>
> -----Original Message-----
> From: Punky Tse [mailto:punkytse@...] 
> Sent: 03 July 2007 17:26
> To: Solomon Asare
> Cc: Think Blue Media; voyage-linux
> Subject: Re: [Voyage-linux] quick voyage boot
>
> Hi all,
>

Kernel Upgrade

_______________________________________________
Voyage-linux mailing list
Voyage-linux@...
http://list.voyage.hk/mailman/listinfo/voyage-linux

Lexar CF Professional - no boot device found

Folks,

I've been running Voyage on WRAPs for the last two years and have used 
both San Disk and Kingston CFs (256Mb and 512MB) with zero problems.  
Just got in some 512MB Lexar Professional (Lt) 80x units for my latest 
builds and am getting "no boot device found" errors. 

I did an A-B test of my load procedure ( starting with fdisk, mke2fs, 
tunefs and the voyage.update) using one of the older CFs and the 
identical download directory.  On one occasion, the Lexar did actually 
boot but after about 10 tries it has not booted again.  The Kingston 
works every time.

There are no problems indicated during any of the installation steps, 
only the failure to boot when installed in the WRAP.  (BTW, the WRAP 
BIOS are 1.11)

Anyone else have this problem or have successfully used the Lexar CFs?

Thanks,

Edwin

--

-- 
<=+=+=+==+=+=+==+=+=+=+=+=+=+=+=>
Edwin Whitelaw, P.E.
New River Valley Unwired, LLC
2200 Lonesome Dove Dr
Christiansburg, VA 24073
540-239-0318

Re: Voyage Linux Sound Support

On Thursday 12 July 2007 22:29:44 Gustavo Samour wrote:
> Hi,I'm using Voyage version 0.3.1 on Nohrtec's Microclient Jr. I don't have
> sound and I read somewhere that the Voyage kernel is compiled WITHOUT sound
> support by default. Is this true? If so, where can I download an iso WITH
> sound support? Another way to go is to compile the same kernel with sound
> support, but for some reason, I get an error while compiling the 2.6.15
> kernel. This doesn't happen with newer kernels (which version of the kernel
> comes with Voyage 0.4.0?). Could anyone please point me in the right
> direction? Thanks in advance.Gustavo

Sound support on Voyage Linux? Why?

However, you have to recompile the kernel and install alsalib.
Bye bye