RE: RAMDISK: ran out of compressed data

Siva Prasad ha scritto: Hi, I am getting the following error when I tried to boot with ramdisk. Any specific reason or clue why this is happening? RAMDISK: Compressed image found at block 0 RAMDISK: ran out of compressed data invalid compressed format (err=1) I am running

RAMDISK: ran out of compressed data

Hi, I am getting the following error when I tried to boot with ramdisk. Any specific reason or clue why this is happening? RAMDISK: Compressed image found at block 0 RAMDISK: ran out of compressed data invalid compressed format (err=1) I am running into this on 8641D runing 2.6.24-rc6 kernel.

mpc86xx - couple of questions...

Hi, I took the latest tree from linux/kernel/git/galak/powerpc.git (2.6.26-rc2), and the latest dtc from linux/kernel/git/galak/dtc.git. After compiling, I am having couple of questions. 1) Doesn't the latest dtc support /memreserve/ on the top before or after /dts-v1/? This used to work fine

Trying 10/HALF

Hi, After booting, my MPC8641 based board keeps printing Trying 10/HALF for ever. I am unable to use the Ethernet, even though there are interrupts occuring. Based on /proc/interrupts, both tx and rx interrupt count is increasing, and zero count for enet_error interrupt. I think this is

RE: Device node - How does kernel know about it

, December 28, 2007 12:39 AM To: Siva Prasad Cc: linuxppc-dev@ozlabs.org; [EMAIL PROTECTED] Subject: Re: Device node - How does kernel know about it -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 * Ramdisk is also executing fine, just that prints are not coming out of serial. I can see the execution

RE: Device node - How does kernel know about it

, 2007 8:16 PM To: Siva Prasad Cc: Nicholas Mc Guire; linuxppc-dev@ozlabs.org; [EMAIL PROTECTED] Subject: Re: Device node - How does kernel know about it On 12/27/07, Siva Prasad [EMAIL PROTECTED] wrote: Thank you Jon and Nicholas. I already have console=ttyS0 in the kernel command line

Device node - How does kernel know about it

Hi, I am really interested in finding out how kernel knows about device nodes and how the whole thing work. This is as part of my debugging effort on 8641D based PowerPC board. * It all started with the problem of not printing any thing that comes from ramdisk (echo and printf statements), while

RE: hangs after Freeing unused kernel memory

some help with this console loosing. Thanks in advance for your help. - Siva -Original Message- From: Linas Vepstas [mailto:[EMAIL PROTECTED] Sent: Monday, November 19, 2007 9:52 AM To: Siva Prasad Cc: [EMAIL PROTECTED]; linuxppc-dev@ozlabs.org Subject: Re: hangs after Freeing unused

RE: initrd - console

. copy_strings: kaddr = USER=root. copy_strings: kaddr = INTERFACE0=eth0. copy_strings: kaddr = /dev/console. copy_strings: kaddr = echo. Thanks Siva -Original Message- From: Michael Ellerman [mailto:[EMAIL PROTECTED] Sent: Monday, December 10, 2007 5:34 PM To: Siva Prasad Cc: linuxppc-dev

printf - How does it work?

Hi, Can some one point me to an URL or some thing that explains how exactly the characters from printf in user program gets printed on to the console. Some thing like it goes to /dev/console, and kernel reads from . would be great, so that I can trace it out. Is there any way, we can

initrd - /dev

Hi, I have a initrd image that I am trying to use on 8641D. When I mount it on a regular PC (using mount -o loop ramdisk file dir), I can see all the required files in /dev directory. However, after loading the same ramdisk file.gz into the target board, all the files in /dev is missing, making

initrd - console

Hi, I am trying to boot kernel with initrd. However, it hangs in run_init_process(/sbin/init). I went into the system calls to see what it is doing. As part of debugging, I ended up adding a printk statement in arch/powerpc/kernel/process.c:sys_execve() routine. Noticed that all the calls are

RE: Linuxppc-dev Digest, Vol 40, Issue 57

mem=504 or greater than we are not able to ioremap, if mem is less than 500 there was no issues on ioremap. We can't understand why ioremap was failed for 504M? Thanks and Regards S.Balamurugan Siva Prasad-3 wrote: Hi, If you want to use SMP, do not enable low memory offset mode

Regarding MPC8641D

mem=504 or greater than we are not able to ioremap, if mem is less than 500 there was no issues on ioremap. We can't understand why ioremap was failed for 504M? Thanks and Regards S.Balamurugan Siva Prasad-3 wrote: Hi, If you want to use SMP, do not enable low memory offset mode

Regarding MPC8641D

Hi, If you want to use SMP, do not enable low memory offset mode. That is only and only for AMP, not for SMP. All the exception vectors go into a different address range for core1, once you enable that, resulting in a need for entirely different copy of OS (be it Linux, or any other OS). You are

RE: Regarding MPC8641D

BTW... it is not true that core1 is idle when low memory offset mode is disabled. Taking core1 out of reset will enable core1 to start booting. These two are two different things. - Siva -Original Message- From: Siva Prasad Sent: Wednesday, December 05, 2007 5:06 PM To: 'linuxppc-dev

kernel_thread pid - stuck (after VFS: Mounted root (ext2 filesystem).)

Hi, I am trying to bring up 8641 based on 2.6.19 kernel. My system hangs after printing the message VFS: Mounted root (ext2 filesystem). I tried to follow down the path to identify where it is hanging, and ended up at the following... init/do_mounts_initrd.c: handle_initrd() function . . .

RE: printk/console_init - baud rate setting

Thanks Segher. It was because of the BASE_BAUD value. We are working at 600MHz, not 18.432. After that change, it worked fine. Thanks Siva -Original Message- From: Segher Boessenkool [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 14, 2007 3:00 PM To: Siva Prasad Subject: Re

RE: printk/console_init - baud rate setting

-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Geert Uytterhoeven Sent: Tuesday, November 13, 2007 12:17 AM To: Siva Prasad Cc: linuxppc-dev@ozlabs.org; [EMAIL PROTECTED] Subject: Re: printk/console_init On Mon, 12 Nov 2007, Siva Prasad wrote: I am

printk/console_init

Hi, I am using 2.6.19 Linux on 8641D based system. I am using early printk's and it works fine until console_init() is executed. After that it does not, as the early printk's get disabled, which is fine. However, I don't see any prints after that at all, that are based on regular printk

Open Firmware - dts file

Hi, I am trying to understand .. 1) How a given dts file is embedded into the zImage (how about vmlinux?) 2) Where does it get stored for later access during booting? 3) How a specific dts file out of the available in /boot/dts directory is chosen? I am a newbie to this open firmware thing and

dlopen source

Hi, Can some one point to where I can find the source code for dlopen() function. Thanks Siva ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev