Home > Cannot Open > Cannot Open Root Device 302

Cannot Open Root Device 302

stabu View Public Profile View LQ Blog View Review Entries View HCL Entries View LQ Wiki Contributions Find More Posts by stabu View Blog 04-28-2007, 05:53 PM #9 stabu Member Registration is quick, simple and absolutely free. Clearly partition table was parsed and > partitions are available; does the mention of unknown-block(0,0) mean > that kernel failed to parse the command line? > > I replaced "root=/dev/mmcblk0p2" with Knute You live, you die, enjoy the interval! have a peek here

I found out it was because I wasn't running lilo at the shell. Or is it? ---edit--- solved! All postings and use of the content on this site are subject to the Terms of Use of the site; third parties using this content agree to abide by any limitations DaHammer View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by DaHammer 08-18-2005, 01:36 PM #5 DaHammer Member Registered: Oct 2003 Location: Planet http://www.linuxquestions.org/questions/slackware-14/vfs-cannot-open-root-device-error-354413/

After discussing it more on irc, it seems like moving the delay/wait handling after md_run_setup [.i.e. Alle Rechte vorbehalten. Thanks, Kevin Reply Cancel Cancel Reply Suggest as Answer Use rich formatting Intellectual 325 points Amit Pundir63658 Jun 13, 2011 8:08 AM In reply to Kevin Chow: Kevin, This is indeed Schau morgen Früh noch mal rein bin dann aber erstmal für 2, 3 Tage off.

Maybe something got enabled in the kernel that is taking over that pin. Use of the information on this site may require a license from a third party, or a license from TI. Image Name: Arago/2.6.32.17-psp03.01.01.39/d Created: 2011-03-25 0:30:27 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2148060 Bytes = 2 MiB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... I ask because if I'm not mistaken (and I could be because don't own any SATA devices) SATA devices are assigned /dev/sdXX by the kernel since it handles them essentially as

How can I reconfig X to use the new video card? Yet it never gets that "I'm bloated and need suspenders" feeling.' - www.arkaoss.com Reply With Quote $spacer_open $spacer_close 04-26-2005 #4 puntmuts View Profile View Forum Posts Private Message View Articles Linux Home Forum Today's Posts | FAQ | Calendar | Community Groups | Forum Actions Mark Forums Read | Quick Links View Site Leaders | Unanswered Posts | Forum Rules Articles Marketplace http://www.linuxforums.org/forum/newbie/30199-swapped-my-mobo-cpu-get-cannot-open-root-device.html Possibly different IDE controller, since both (old and new) were on the moboards. 'Linux is like a swiss army knife.

Mike I miss MDWatts. I miss MDWatts. I substitute kernel/drivers/mtd/ubi and kernel/fs/ubifs from linux-2.6.32.41-longterm for that in ti android kernel. You may have to register before you can post: click the register link above to proceed.

Teste das ganze mal unter ext3 weil ich das gefühl habe das das Prob gehääuft bei ReiserFS auftaucht, wollte nur mal was neues testen und das hat man nun davon Zitieren I have to assume that my board is broke too? No license, either express or implied, by estoppel or otherwise, is granted by TI. I am not sure whether both NOR and NAND are served by the same conntroller, I don't know how to recognize the controller declaration in sources.

I can boot now... http://dekovsoft.com/cannot-open/cannot-open-root-device-cobd0.html Share your knowledge at the LQ Wiki. Reply Cancel Cancel Reply Suggest as Answer Use rich formatting Intellectual 2805 points Velan Mar 26, 2012 11:37 AM In reply to Norman Wong: Hi Wong, Thanks for you reply. I have seen patches being pushed in 2.6.32-longterm kernel for ubifs lately.

Powered by vBulletin Version 4.2.2Copyright ©2000 - 2016, Jelsoft Enterprises Ltd. I should add, the filesystem is actually fine as the older kernel has no problems with it. Maybe you need to reseat some boards. Check This Out iam whoiam View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by iam whoiam 04-28-2007, 04:15 PM #8 stabu Member Registered: Mar 2004

You can also try passing "vmilnuz root=/dev/xxx" at the boot prompt. Thanks PS: above kernel panic, I can see FWIW: kswapd VFS: dquot.6.4.0 devfs: boot options : 0x0 RAMDISK DRIVER NET4 -- Eric Smith Reply to: debian-boot@lists.debian.org Eric Smith (on-list) Eric Smith Mine >> > shows 3.16.0-11149-gba36899. >> >> Ok, thanks for info.

Forum New Posts FAQ Calendar Forum Actions Mark Forums Read Quick Links Today's Posts View Site Leaders What's New?

Frankly it should fail as well. I'm goign to look at kernelconfig now .. Thanks for your help. Sie müssen sich vermutlich registrieren, bevor Sie Beiträge verfassen können.

They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. Mein System 1200 mobile athlon S3 Twister onboard Graka 128mb RAM auf Knoppix 3.8. (ist nur zum Testen bitte kein Kritik) Danke auch an die von diesem Thema genervten .... Clearly partition table was parsed and > > > partitions are available; does the mention of unknown-block(0,0) mean > > > that kernel failed to parse the command line? > > http://dekovsoft.com/cannot-open/cannot-open-root-device-mtdblock.html Total pages: 62976Kernel command line: console=ttyO2,115200n8 androidboot.console=ttyO2mem=256M root=/dev/mmcblk0p2 rw rootfstype=ext3 rootdelay=1 init=/initip=off omap_vout.vid1_static_vrfb_alloc=y vram=8M omapfb.vram=0:8MPID hash table entries: 1024 (order: 0, 4096 bytes)Dentry cache hash table entries: 32768 (order: 5, 131072

Code: # Linux bootable partition begins image = /boot/vmlinuz-ide-2.4.29 root = /dev/hda2 Label = Linux24 read-only # Linux bootable partition ends # Linux bootable partition begins image = /boot/vmlinuz root = Die Antworten waren doch alle ok, oder nicht? input core section, I didn't have some event trigger thing checked which seemed to mess with my USB keyboard. Can you do a bisect? 3.17-rc2 booted fine for me today: EXT3-fs (mmcblk0p2): mounted filesystem with ordered data mode VFS: Mounted root (ext3 filesystem) on device 179:2.

Or... TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these If that is the case have you tried mounting a regular Linux file-system now instead of Android file-system?