I think you should hit w to write the data, if I remember correctly, the "q" command will exit fdisk without writing anything, that means, the partition table will not be modified by fdisk.

BTW, I have just finished snapshots uploading:
http://fisherss.com/linux50/snapshots.html

Good luck !


Angel Sánchez Morales wrote:
Woho!!! woho!!! I got more output!!! :D

After the Freeing init memory: 80K i can see this (the above seems to be the same as before):

open("/dev/mem"): No such file or directory
open("/dev/mem"): No such file or directory
Initial RAM Disk started ...
mount: Mounting /dev/mmc/blk0/disc on /mnt/rootfs failed: No such device or address
Failed to mount root filesystem, dropping to a shell


Busybox v0.60.5 (2004.04.11-12:09+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

sh: can't access tty: job control turned off
#


If i use Fisherss' method to format the sd it makes an entire ext2 partition on the sd, but then when using fdisk it doesn't recognizes any partition and when you hit w (for writting the data to the medium) it tries to sync with the device and then it exits by itself, i should hit q to exit from fdisk.

So i left the partition created with mke2fs /dev/sda and put all the filesystem there. I got the same output as before, and looking at it I noticed that it says that mmc0 doesn't have read-only access and makes it rw (mmc0: host does not support reading read-only switch. assuming write-enable.) and then i can see the line trying to mount mmc (mount: Mounting /dev/mmc/blk0/disc on /mnt/rootfs failed: No such device or address), perhaps in x50v we need to mount /dev/mmc0/blk0/disc?

If i have time this night i'll try to modify the initrd to mount that device :)


Fisherss wrote:
I remember that the Chinese guy has mentioned this, use this line:
set cmdline "root=/dev/ram0 rw ramdisk_size=12288 keepinitrd init=/linuxrc console=tty0"
instead of this line :
set cmdline "root=/dev/ram0 rw ramdisk_size=12288 keepinitrd init=/linuxrc console=tty0 console=ttyS0,115200n8 "

Then you may get the output from linuxrc or other thing.

JeDi wrote:

On 1/4/06, Fisherss <[EMAIL PROTECTED]> wrote:
The "echo" lines appear only through your serial console,  not on the
screen. The size of fonts is suitable for x50, and I don't know what
size x50v needs.


It's in the post from the guy that got framebuffer working for x50v:
"Graphics support->Console display driver support:enable VGA8X8 and VGA8x16"

When these are enabled (the mini one can stay enabled too), the text
is realy nicely readable on the x50v (kinda hard to read with the mini
font on that resolution).

Is there a way to put messages on screen in the linuxrc script? Would
be great for us without a serial cable :-)


I am uploading it. About the newest kernel,  I have tried CVS version,
but looks like something is aximx30.c file is incorrect, it cant pass
compiling process.


Thanks for uploading! As for the aximx30.c file not compiling, that's
in the previously mentioned post too:

[quote]
f) modify aximx30.c to support new kernel: from kernel 2.6.13
,the macros to setup machine descrtipion is delete from kernel
source,so you should modify the endof aximx30.c as following:

       MACHINE_START(X30, "Dell Axim X30")
#if 0
       MAINTAINER("Giuseppe Zompatori, <[EMAIL PROTECTED]>")
       BOOT_MEM(0xa8000000, 0x40000000, io_p2v(0x40000000))
       BOOT_PARAMS(0xa0000100)
       MAPIO(x30_map_io)
       INITIRQ(x30_init_irq)
#endif
       .phys_ram       = 0xa8000000,
       .phys_io        = 0x40000000,
       .io_pg_offst    = (io_p2v(0x40000000) >> 18) & 0xfffc,
       .boot_params    =  0xa0000100,
       .map_io         = x30_map_io,
       .init_irq       = x30_init_irq,
       .timer          = &pxa_timer,
       .init_machine   = x30_init,
MACHINE_END
[/quote]


Thanks Fisherss and all the rest, for the great work you all put into this!

Greetz and good luck,
JeDi
--
_______________________________________________
Aximx50-port mailing list
[email protected]
https://www.handhelds.org/mailman/listinfo/aximx50-port

Reply via email to