[Voyage-linux] Re: Kingston 2GB CF won't boot ALIX (Edwin Whitelaw)
Edwin Whitelaw
(spam-protected)
Mon May 11 21:42:25 HKT 2009
Hmm, that didn't work with my Transcend CF. The gnu-fdisk installed and
appeared to work fine followed by mke2fs and tunefs. Here's what I get
when trying to connect after booting...
---------------
d2300:/usr/src/voyage-0.5.2# cu -l /dev/ttyS0 -s 38400
Connected.
GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB
GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB
GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB
GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB
GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB
GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB
GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB..... etc., etc.
-----------------------------
Actually, I've never seen this before and I've been installing on
WRAP/ALIX since Voyage 0.2, Of course, the CFs then were 256 and 512MB.
Edwin
Rui Pedro Bernardino wrote:
> Hi,
>
> I had this same issue, fixed it by using a different fdisk program
> (gnu-fdisk in my case, "sudo apt-get install gnu-fdisk" if you're a
> Ubuntu user): it seems the 'normal' fdisk won't handle all CF
> geometries correctly and messes boot.
>
> Regards
>> Update....
>>
>> Seems these new CF cards will load/boot 0.6.1 just fine. If I switch
>> the boot loader to lilo, they will then also boot 0.5.2. Not a huge
>> workaround but odd nonetheless. I rather prefer grub but can live
>> with this. I've used earlier Kingston 1 & 2GB CFs with no problem so
>> I assume they've changed something internally. Had the same problem
>> with a new Transcend card (maybe manufactured by the same company?)
>>
>> A side note - I had tried 0.6.1 a few months ago with an Atheros card
>> as AP (and WEP) at two sites and both exhibited the same problem of
>> working for a period of several hours and then mysteriously losing
>> connection with all clients. Ifdown/ifup on the interface would
>> restore function. Going back to 0.5.2 at one location and using a
>> Prism card at the other solved that problem but it would be nice if
>> there was confirmation that the AP mode with Atheros radios now works
>> reliably so I can move forward with the newer release
>>
>>
>> Thanks to those who responded.
>>
>> Edwin.
>>
>> Edwin Whitelaw wrote:
>>
>>> Been using these cards for a while without problems.
>>>
>>> I run fdisk and replace the FAT with one Linux partition and make
>>> that bootable.
>>>
>>> Fresh load of 0.5.2 (from a well used standard setup) with boot
>>> partition set (and confirmed on CF) and the ALIX board shows
>>>
>>> d2300:/usr/src/voyage-0.5.2# cu -l /dev/ttyS0 -s 38400
>>> Connected.
>>> PC Engines ALIX.3 v0.99h
>>> 640 KB Base Memory
>>> 261120 KB Extended Memory
>>>
>>> 01F0 Master 044A CF CARD 2GB
>>> Phys C/H/S 3909/16/63 Log C/H/S 977/64/63
>>> Missing operating system
>>>
>>> When powered up.
>>>
>>> Any ideas on this?
>>>
>>> Thanks,
>>>
>>> Edwin
>>>
>>>
>>
>>
>
>
> _______________________________________________
> Voyage-linux mailing list
> Voyage-linux at list.voyage.hk
> http://list.voyage.hk/mailman/listinfo/voyage-linux
--
<=+=+=+==+=+=+==+=+=+=+=+=+=+=+=>
Edwin Whitelaw, P.E.
New River Valley Unwired, LLC
2200 Lonesome Dove Dr
Christiansburg, VA 24073
540-239-0318
More information about the Voyage-linux
mailing list