Bumpy progress with Webmin on Iomega iConnect

[cr08]

Hi there. Newbie to the forum but have been reading as much as possible here to help me on my way. Not exactly expert levels with *nix, but do sufficiently know my way around. At this point the two ARM devices I have available to me are an Iomega iConnect and a Pogoplug Pro.

Long story short the stock OS on the iConnect in my usage has been crap and it tends to go braindead when any significant file transfers are initiated. I found out the existing method to install Arch on it and figured I would go down that route, assuming the bugs are software rather than hardware. On top of that, it would allow me to add a few extra features missing from stock (NFS access, -Proper- torrent support and not the failboat implementation Iomega used, and a simplified web server for various uses).

Using the non-serial method of installation went smoothly and exactly how I expected it. Initially had network issues due to no gigabit switch. Do have one computer with Gigabit networking so connected it to that with TFTPD32 acting as DHCP server, got the arcNumber updated, rebooted, all works.

But here is the catch and main point of the thread: Upon installing webmin and manually starting it, I cannot access it normally even with attempted tweaks:
a) Set the allowed addresses accordingly
b) disable SSL access
c) install base-devel and use CPAN to load the perl PAM Auth libraries
Checking the miniserv.error log shows nothing relevant at this point. But when trying to access it all I end up is with a forever loading browser tab with a blank white screen.

Nothing else running on here so far. Just the base ALA install, webmin, base-devel, and the PAM auth perl lib. And dependencies of course.

Side note: I also seem to have intermittent shell problems (putty, stock configuration). Namely 'interactive' applications seem to kill the shell randomly. So far it seems to be nano and top which do this at random points. Just a blank screen shows if I try to run them and it decides to act up. If I close putty and re-open, all is well with no visible issues. Not sure if this is related but thought I'd bring it up anyways as a mild annoyance I haven't been able to figure out.