• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1]
Author Topic: trouble with booting debian  (Read 859 times)
soulShadow
Newbie
*

Karma: 0
Posts: 6


View Profile
« on: March 11, 2010, 07:28:58 AM »

Hi forum,

im not shure wether its' a uboot or a installer problem, but
after long attempts I finally succeded in installing a kirkwood kernel on a usb device on my plug
with lvm.
Ifollowed MM descriptions to upgrade uboot and install the plug.
(uboot 3.4.19) but i cant suceed in getting it the boot process done.

the boot process braeks with this:
Code:
Gave up waiting for root device.
 Common problems:
- Boot args (cat /proc/cmdline) 
 - Check rootdelay= (did the system wait long enough?)   
 - Check root= (did the system wait for the right device?)
 - Missing modules (cat /proc/modules; ls /dev)

ALERT! /dev/mapper/savageSoul-root does not exist.
Dropping to a shell!BusyBox v1.14.2 (Debian 1:1.14.2-2) built-in shell (ash)
Enter 'help' for a list of built-in commands./bin/sh: can't access tty; job control turned off(initramfs)

can anyone give me a hint?
« Last Edit: March 13, 2010, 01:17:03 AM by soulShadow » Logged

mundhra
Newbie
*

Karma: 1
Posts: 34


View Profile
« Reply #1 on: March 11, 2010, 09:06:46 AM »

can you post the output of a printenv at the uboot prompt?
Logged

soulShadow
Newbie
*

Karma: 0
Posts: 6


View Profile
« Reply #2 on: March 13, 2010, 01:15:38 AM »

sorry I've should done this before:
printenv

Code:
baudrate=115200
loads_echo=0
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
console=a0000
e=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x1ff00000@0x100000(root)
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
ethmtu=1500
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
nandEcc=1bit
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
ethact=egiga0
mtdpartitions=mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs)
ethaddr=00:50:43:01:c1:e6
real_bootcmd=setenv bootargs $(bootargs_console) $(mtdpartitions) $(bootargs_root); nand read.e 0x00800000 0x00100000 0x00400000; bootm 0x00800000
recover1=setenv mainlineLinux yes; setenv arcNumber 2097; setenv bootcmd run recover2; saveenv; reset
recover2=run recover3; setenv bootcmd $(real_bootcmd); saveenv; setenv bootargs $(bootargs_console) $(mtdpartitions) root=/dev/ram0 rw ramdisk=0x01100000,8M install_type=nand; bootm 0x00800000 0x01100000
recover3=run recover4; nand erase clean 0x00100000 0x00400000; nand write.e 0x00800000 0x00100000 0x00400000
recover4=usb start; fatload usb 0 0x00800000 uImage; fatload usb 0 0x01100000 initrd
mainLineLinux=yes
ipaddr=192.168.1.200
serverip=192.168.1.13
filesize=15C5C8
arcNumber=2097
bootcmd_usb=usb start; ext2load usb 0:1 0x01100000 /uInitrd; ext2load usb 0:1 0x00800000 /uImage
bootargs_console=console=ttyS0,115200
bootcmd_mmc=mmcinit;mmcinit; ext2load mmc 0 0x01100000 /uInitrd; ext2load mmc 0 0x00800000 /uImage
bootargs=console=ttyS0,115200
bootcmd=setenv bootargs $(bootargs_console) $(bootargs_root); run bootcmd_usb; bootm 0x00800000 0x01100000; reset
bootargs_root=rootdelay=30
stdin=serial
stdout=serial
stderr=serial
nandEnvBase=a0000
mainlineLinux=yes
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
enaAutoRecovery=yes
pcieTune=no
Logged

mundhra
Newbie
*

Karma: 1
Posts: 34


View Profile
« Reply #3 on: March 13, 2010, 02:17:09 PM »

your boot arguments are:

bootargs_console=console=ttyS0,115200
bootargs_root=rootdelay=30
bootcmd_usb=usb start; ext2load usb 0:1 0x01100000 /uInitrd; ext2load usb 0:1 0x00800000 /uImage
bootcmd=setenv bootargs $(bootargs_console) $(bootargs_root); run bootcmd_usb; bootm 0x00800000 0x01100000; reset

you are not specifying a root; bootargs_root should look something like 'root=/dev/sda2 rootdelay=10'.
Logged

tbm
Full Member
***

Karma: 6
Posts: 111



View Profile WWW
« Reply #4 on: March 14, 2010, 03:27:36 AM »

soulShadow,

can you post the full boot log?
Logged

soulShadow
Newbie
*

Karma: 0
Posts: 6


View Profile
« Reply #5 on: March 14, 2010, 07:26:59 AM »

while booting i noticed several lines with bad eraseblock:
Code:

[    1.113509] Bad eraseblock 2457 at 0x000013320000
[    1.118446] Bad eraseblock 2464 at 0x000013400000
[    1.123401] Bad eraseblock 2472 at 0x000013500000
[    1.128364] Bad eraseblock 2480 at 0x000013600000
[    1.133325] Bad eraseblock 2488 at 0x000013700000
[    1.184999] Creating 3 MTD partitions on "orion_nand":
[    1.190178] 0x000000000000-0x000000100000 : "u-boot"
[    1.195718] 0x000000100000-0x000000500000 : "uImage"
[    1.201193] 0x000000500000-0x000020000000 : "root"
[    1.207429] mice: PS/2 mouse device common for all mice
[    1.213020] rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
[    1.218975] i2c /dev entries driver
[    1.222645] cpuidle: using governor ladder
[    1.226893] cpuidle: using governor menu
[    1.230925] Registered led device: plug:green:
« Last Edit: March 14, 2010, 09:29:35 AM by soulShadow » Logged

soulShadow
Newbie
*

Karma: 0
Posts: 6


View Profile
« Reply #6 on: March 14, 2010, 09:33:13 AM »

i tried to set a parameter for root=/dev/sda2 rootdelay=20
and root=/dev/sda5 rootdelay=20
without a change

@tbm unfortunatliy i can not realy get a boot log, but i tried to pipe the output in a file
(didn't found a way to avoid the escape-sequences
file attached cause its to large.

* sp.log (19.33 KB - downloaded 32 times.)
« Last Edit: March 14, 2010, 10:17:38 AM by soulShadow » Logged

soulShadow
Newbie
*

Karma: 0
Posts: 6


View Profile
« Reply #7 on: March 18, 2010, 12:13:10 AM »

I've updated this tread with a (kind of) boot log.
Maybe someone can guess the error I'm realy stuck,
couse of to less knowledge of u-boot stuff

is there a posibility to make a repair install?
thanx
« Last Edit: March 19, 2010, 04:17:39 AM by soulShadow » Logged

cjm
Newbie
*

Karma: 4
Posts: 34


View Profile
« Reply #8 on: March 21, 2010, 11:39:00 PM »

The boot log two posts ago still uses the kernel old command line:


0.000000] Kernel command line: console=ttyS0,115200 rootdelay=30


Something is still wrong with your boot args.
Logged

soulShadow
Newbie
*

Karma: 0
Posts: 6


View Profile
« Reply #9 on: March 26, 2010, 03:19:16 AM »

hmm maybe somethings wrecked up. guess I should try a new installation :/

I nearly tried it abotu 30 or forty times. everytime it hangs up or ides another way.
I give up   the plug dont wants to be my friend … Lips sealed
« Last Edit: March 28, 2010, 02:00:09 AM by soulShadow » Logged

cjm
Newbie
*

Karma: 4
Posts: 34


View Profile
« Reply #10 on: March 30, 2010, 11:57:58 AM »

It has to be the boot command you're using -- the kernel has nothing to do with this because the command line is passed from uboot to the kernel.
Logged

Pages: [1]
Print
Jump to: