ubiquity fails after /bin/hw-detect, on armel hardware, on first boot

[Robert Nelson]

Binary package hint: ubiquity

To ease new users to setup their own rootfs on armel hardware. A new option in project-rootstock for lucid is to run oem-config in the rootfs on first boot.

A typical user would:

1: Run rootstock on a x86 machine to setup an ubuntu armel rootfs.
2: The user would copy the rootfs to an SD card.
3: Boot the SD card with their armel hardware.
4: oem-config would start and user inputs settings.
5: User would reboot the system configured for them.

With alpha-3, Task 4 is failing, shortly after ubiquity's /bin/hw-detect phase..

Dec 31 18:09:48 ubiquity: Starting up '['log-output', '-t', 'ubiquity', '--pass-stdout', '/bin/hw-detect']' for ubiquity.components.hw_detect.HwDetect
debconf (developer): <-- GET hw-detect/load-ide
debconf (developer): --> 0 false
<snip>
debconf (developer): --> 0 OK
debconf (developer): <-- PROGRESS INFO ubiquity/install/hardware
Can't call method "info" on an undefined value at /usr/share/perl5/Debconf/FrontEnd.pm line 142, <GEN0> line 324.
grep: /target/etc/apt/sources.list: No such file or directory

User info is setup, and it's possible to switch to ttys2 to login, but 'every' following reboot, oem-config is still run...

Test rootfs setup for beagleboard users is here: http://www.rcn-ee.net/deb/rootfs/ubuntu-lucid-alpha3-minimal-armel.tar.7z

freescale/marvel hardware would need an appropriate uImage....

[Timofey Solomko (timofey-solomko-deactivatedaccount)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't start working on it yet, because your description didn't include enough information.

Please include the information requested at https://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs as separate attachments by visiting your bug's web page. Thanks in advance.

[Launchpad Janitor (janitor)]

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]