test of today's release of "uboot for powerkernel v46" - in maemo-devel, and most recent h-e-n hostmode GUI as of today, on a pr1.1.1 system (yes!) with a custom kernel:

installation of uboot-pk-v46 went fine and pulled in pk as a dependency as supposed.
Not showing any of the usual warning dialogs though that usually come with pk.
uboot bootmenu showing fine, boot to system OK.

(installed backup-menu after that, and it also worked as expected)

installation of h-e-n GUI listed pk-v46 as a dependency that gets installed, obviously the dependencies of h-e-n aren't satisfied by uboot-pk-v46.
I refused to accept the warning dialog that showed up for pk this time ("click outside gray area...") -> HAM rises error notifier "installation wasn't possible"
Nevertheless h-e-n got installed

Clicking Icon doesn't work, running `update-sudoers` from a rootshell fixed this (why is the file so awkwardly named? ->"/etc/sudoers.d/hostmode.sudoers.dpkg-new")

after that h-e-n works like expected, until mounting.
error:"sh: /opt/h-e-n/mount.sh: Permission denied"
in a rootsh `chmod u+x /opt/h-e-n/mount.sh` fixed this, for the first time I tested. For some weird reason h-e-n wasn't able to call ` /opt/h-e-n/mount.sh --mount` after this initial success, on all my tests. I guess there's some bug in h-e-n regarding the mount button.
A manual call, in a rootshell, of ` /opt/h-e-n/mount.sh --mount` worked just fine
Maybe of interest: the unmount button works like expected. (checked by inserting "set -vx" at top of /opt/h-e-n/mount.sh)
[edit] unchecking the settings->"open fm after mount" seems fixed the mount button[/edit]

settings->default-filemanager: is locked, i.e it's empty and I can't change it. Not even after ticking above checkmark and closing/restarting h-e-n

The help text is using USB1.1 as descriptive term for both fullspeed and lowspeed. I suggest to check if that's not LS=USB1.0, and maybe even change the button labels to the more clear USBx.y terms rather than the HS/FS/LS. Also a sort order left=low, right=high would be more intuitive, I.E.: [USB1.0] [USB1.1] [USB2.0] for the three buttons.
[VBUS boost] should become a checkmark widget above those three buttons, and hitting any of the 3 would do both select speed and - according to VBUS checkmark - enable vboost same moment. The three speed buttons then change to a single [STOP] button.

Sidenote: it seems you need to be patient when hitting the buttons. My pendrive needs some 8s after vboost enable, and then again several seconds after ENUM, until kernel finally created device sda{1}. Prior to that 'mount' won't work I guess

bottom line: some weirdness might have come in by HAM aborting the installation as a result of me refusing to accept installation of pk. This probably resulted in postinstall script never being executed, which might explain the missing permissions and update-sudoers run.
The mount-button breakage I guess is related to inconsistencies between my 1.1.1 filesystem and pathes, and what h-e-n GUI expects to find for HFM. However this shouldn't cause the mount button to become dysfunctional

for the rest of it: nice work Mohammad. Thanks a lot
cheers
jOERG