Alix 2D13 - CF - can't load 'kernel'

stephenw10

I would run the 2GB image (or even 1Gb) anyway just because you're very unlikely to ever need the extra space and it writes much quicker. ;)
However I would try writing the image differently. Try a different block size if you're using dd, 1M seems way too big. Figures plucked from the docs wiki and forum indicate bs=16k is more suitable.

https://forum.pfsense.org/index.php?topic=25413.msg132036#msg132036

Steve

bartounet

It is better whith 2G but it don't boot.

It is block to Booting [/boot/kernel/kernel]…
|
###############

boot: Consoles: serial port
BIOS drive C: is disk0
BIOS 640kB/261120kB available memory

FreeBSD/x86 bootstrap loader, Revision 1.1
(root@pf2_1_1_i386.pfsense.org, Mon Aug 25 08:20:02 EDT 2014)
Loading /boot/defaults/loader.conf
/boot/kernel/kernel data=0x91c91c data=0x51dad4+0x9e0c4 -
|
Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel]…
|
##################

stephenw10

What baud rate are you using on the serial console?
pfSense uses 9600 by default but I believe the ALIX tinycore bios uses something else.

Steve

bartounet

i have set 9600 on alix bios

stephenw10

Did you try the much smaller block size when flashing the card?

Steve

bartounet

yes.
A have test 16k
same problem….

stephenw10

Hmm, your symptoms exactly match those that happen if you don't have the correct bios version but you already have 0.99h. :-
Has this board been running pfSense before?
It doesn't have any mini-PCI cards?

Steve

bartounet

Yes this alix has running pfsense whith hdd microdrive yet

bartounet

news…
i have extract the same image pfSense-2.1.5-RELEASE-4g-i386-nanobsd.img
on hdd 2"5 whith the ide Sate adaptor...

And it boot...
Why does not boot whith CF...

stephenw10

It could be that your cf card presents some geometry that the bootloader handle.
You could try a 2.2beta snapshot. I'm not sure what might have changed in the bootloader but you may have more luck.

Any suggestions from ALIX veterans?

Steve

bartounet

Hello i have solve my problem…
i have simply change my CF Card Reader...

Whith anoter card Reader, on the same CF , no problem...

Perhaps my old card reader has written bad blocks on CF

stephenw10

Ah. Hadn't considered that could be an issue. Thanks for coming back with that. :)

Steve