I'm making some small progress.. I found I could not see the HDD with "ls /dev/block", looking in the BIOS I saw IDE mode was set to "Enhanced", I changed it to "Compatible" and while the install still fails I can now see the HDD partitions.
I now get the message "diskconfig: Could not re-read partition table. REBOOT! (errno=16)" I've tried rebooting but get the same error, if I execute "mount" I see "/dev/block/sdb2 /data" is mounted read only, if I remount it rw I get the partition table read error again (and so on, I do notice the USB key has 8 partitions when I look at it from Ubuntu, is that right?). Does any of this ring any bells? I'm really determined to get this working, as I mentioned I had no trouble at all getting Android x86 running on VirtualBox so there is something about my ASUS 1000HE that it's not liking. I'm now re syncing and rebuilding the installer from scratch just to make sure I haven't broken something. Thanks again for any further suggestions! On Jun 29, 9:23 pm, Chen Yang <[email protected]> wrote: > No, it doesn't care about the target hdd's parition as the access to that > drive is write only: it will WIPE all the DATA!! > You can try to mount the partition you think as data partition, and see > whether it works. > installer does accept some parameters to play with: > -c <path> - Path to installer conf file (/system/etc/installer.conf) > -l <path> - Path to device disk layout conf > file (/system/etc/disk_layout.conf) > -d - Dump the compiled in partition info > -p <path> - Path to device that should be mounted to /data. > -t - Test mode. Don't write anything to disk > -- > Chen > > > > On Mon, Jun 29, 2009 at 5:00 PM, Bruce <[email protected]> wrote: > > > Thanks for the suggestions, I do appreciate your time. > > > One quick question, does the Android installer care about the existing > > hard-drive partitions? Currently the HDD has 2 x 70GB NTFS > > partitions.. is it possible that the size or format of these is > > causing an issue? > > > On Jun 29, 6:23 pm, Chen Yang <[email protected]> wrote: > > > it looks like that the installer is waiting for the second partition on > > the > > > usb drive. > > > You can check the paritions via looks into: > > > /dev/block/ > > > try to list the nodes under that directory. > > > if you have the installer.img dd-ed on your usb drive, it should have 2 > > > paritions. Don't know the detail of your hard drive, if it has different > > > number of paritiions, it should be easy to find out. Otherwise, maybe you > > > can try to see the kernel log via: dmesg > > > -- > > > Chen > > > > On Mon, Jun 29, 2009 at 1:32 PM, Bruce <[email protected]> wrote: > > > > > I tried various combinations of that (kill installer process and / > > > > system/bin/installer -p ..) before I loaded Ubuntu to check the volume > > > > ids, the ids seem correct unless the Android installer sees them > > > > differently? Is there a way to find out via the shell prompt that > > > > installer stops at? > > > > Thanks! > > > > Bruce > > > > > On Jun 29, 4:59 pm, Yi Sun <[email protected]> wrote: > > > > > if I remember it right, you can do something like > > > > > installer -p /dev/<your disk node> > > > > > > On Sun, Jun 28, 2009 at 2:23 AM, Bruce <[email protected]> wrote: > > > > > > > I have created a standard VESA x86 Android build (eg. without the > > > > > > intelfb mods) and created the bootable USB installer but I can't > > get > > > > > > past the message "Waiting for device: /dev/block/sdb2" when it > > boots, > > > > > > I'm using 1000HE which has a single harddrive instead of the 2 SDD > > > > > > drives in the earlier 1000 series, when I boot Ubuntu from USB and > > use > > > > > > fdisk -l it shows the hard-drive partitions as sda1 thru sda4 and > > the > > > > > > USB drive as sdb1 so I'm assuming the standard layout of sda being > > the > > > > > > destination drive and sdb the USB drive, with sdb2 as the ext2 > > > > > > partition on the USB key is correct for this machine. > > > > > > > This machine currently has XP on it, did I need to delete the > > existing > > > > > > partitions to prepare it for this? > > > > > > > Has anyone had this problem and solved it? I've seen a few posts > > > > > > around mentioning the same error but no obvious solutions. I'd > > > > > > appreciate any pointers. > > > > > > > Thanks! --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
