ubuntu-phone team mailing list archive

[Oliver Grawert <ogra@xxxxxxxxxx>]

hi,
Am Mittwoch, den 19.03.2014, 11:47 +0100 schrieb Corvus:
> New tests.
> 
> 
> This is what i added to my default boot
> cmdline datapart=/dev/mmcblk0p9 debug rw console=tty0,115200n8
> no_console_suspend=1 and the result is the same. 
> 
hmm, adbd should fire up at least ...

> I added too symlinks in init script:
> 
> 
> #Added symlinks for dev devices
> ln -s /dev/userdata /dev/mmcblk0p9
> ln -s /dev/USERDATA /dev/block/mmcblk0p9
> ln
> -s /dev/UDA /dev/block/platform/intel/by-uuid/80868086-8086-8086-8086-000000000008
> ln
> -s /dev/DATAFS /dev/platform/intel/by-uuid/80868086-8086-8086-8086-000000000008

doing this will just confuse udev I suspect since it produces the right
links itself based on udev rules ...

> 
> to make sure that i cover all the possibilities, but doesnt work :(
> 
> 
> Anyway, it's supposed that if this doesnt work adbd should start and
> this is not happening:
> 
> 
> List of devices attached 
> 0123456789ABCDEF offline
aha !
this means adbd *has* actually started but did not set the gadget device
online (see below) ...
> 
> 
> But in /scripts/panic/adbd i
> modified /sys/class/android_usb/android0/iSerial to AABBBCCCDDDEE and
> now when i do a adb devices i get:
> 
> 
> List of devices attached 
> 
> AABBBCCCDDDEE  offline
right (see above) ... did you use some adb version on the device before
that required you to accept a key on the PC ? it usually stores that
somewhere (I forgot where exactly, either under /cache or /data in some
"persist" directory) try to find it and delete the dir ...

> 
> 
> So init script is running, and it launch to panic/adb script, and /sys
> is working ok, but /sbin/adbd isnt :(
> 
> 
> I think that there is a problem with /dev, not mounting or something
> and this is why it doesnt mount data partition and adbd is not working
> (because i read somewhere that it needs /dev/urandom or something like
> this).
> 
> 
> Any clue of how i can test if /dev is working correctly or if i need
> to modify any udev configuration?
> 
well, lets get adbd to work, then you can debug ... beyond this there is
always /proc/last_kmesg that you can look at from recovery after a
failed boot, might probably make sense to take a look there.

ciao
	oli

Attachment: signature.asc
Description: This is a digitally signed message part