linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "José Luis Añamuro Machicao" <jose.annamuro@ESTUDIANTE.UAM.ES>
To: <Linuxppc-embedded@ozlabs.org>
Subject: Fw: Cannot open root device "xsysace/disco0/part3" or 00:00
Date: Wed, 26 Mar 2008 20:42:11 +0100	[thread overview]
Message-ID: <002301c88f79$7f197a10$7738f496@JoseLuisAM> (raw)

[-- Attachment #1: Type: text/plain, Size: 2302 bytes --]


----- Original Message ----- 
From: José Luis Añamuro Machicao 
To: Linuxppc-embedded@ozlabs.org 
Cc: josel_am2@yahoo.es ; jose_luis@fun-humanismo-ciencia.es 
Sent: Wednesday, March 26, 2008 8:39 PM
Subject: Cannot open root device "xsysace/disco0/part3" or 00:00


Hi
I am installing the linux kernel 2.4.26 in the FPGA Virtex II Pro following the instruction of 
http://www.cs.washington.edu/research/lis/empart/xup_ppc_linux.shtml

I compiled the linux kernel successfully, after that I build the root file system using the BusyBox 1.1.0 infrastructure. I configured the busybox and the kernel with the cross compiler, finally I execute the mkrootfs.sh script and obtain the all files of fyle system, these files I copied to ext3 partition of CompacFlash when I probe operatión by the hyperTerminal (38400 bps) appears a error that say:

Serial driver version 5.05c (2001-07-08) with no serial options enabled
ttyS00 at 0xfdfff003 (irq = 30) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
VFS: Cannot open root device "xsysace/disco0/part3" or 00:00
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 00:00
 <0>Rebooting in 180 seconds.


I configured the linux kernel with:

Code maturity level options ---> 

            [*] Prompt for development and/or incomplete code/drivers 

File systems ---> 

    [*] /dev file system support (EXPERIMENTAL) 

     [*] Automatically mount at boot 

    [*] Virtual memory file system support (former shm fs) 

    [*] /proc file system support 

General Setup ---> 

    [*] Networking support 

    [*] Sysctl support 

    [*] System V IPC 



and edit the /etc/fstab 

tmpfs /dev/shm tmpfs nodev,nosuid,noexec 0 0 

proc /proc proc defaults 0 0

/dev/root / auto defaults,errors=remount-ro 0 0 



-------------------------------------------------------------------------------------
__    _        __  __      José Luis Añamuro - PhD Student
\/    V  /\  |\_\ /\_\      Dept. Ingeniería Informática
| |     |  /  \  | |  \/  |   |    Universidad Autónoma de Madrid
| |     | / /\\ | |   |   |   |    Lab B-209   Tel. +34 615887260
| |     |/ __ \| | \  /    |    http://www.ii.uam.es/
`-_-/_/    \_\|_|\/|__| 

[-- Attachment #2: Type: text/html, Size: 5045 bytes --]

             reply	other threads:[~2008-03-26 19:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-26 19:42 José Luis Añamuro Machicao [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-03-26 20:25 Fw: Cannot open root device "xsysace/disco0/part3" or 00:00 José Luis Añamuro Machicao

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='002301c88f79$7f197a10$7738f496@JoseLuisAM' \
    --to=jose.annamuro@estudiante.uam.es \
    --cc=Linuxppc-embedded@ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).