Tomas, hello. Thanks for your advice.
> Devs and list need to see your dmesg output for sure (it can be posted > somewhere as screenshots via link) I've put the dmesg output at * http://nxg.me.uk/temp/dmesg-screenshot-5.4-1.jpg * http://nxg.me.uk/temp/dmesg-screenshot-5.4-2.jpg * http://nxg.me.uk/temp/dmesg-screenshot-5.4-3.jpg A pretty desperate set of screenshots -- photos of the screen! Those are temporary URIs. On 2014 Apr 6, at 20:59, Tomas Bodzar <tomas.bod...@gmail.com> wrote: Problem 0 is that the boot fails to detect networking hardware. I >> understand that the wireless interface doesn't work on this machine >> with OpenBSD, but that the wired one should work [2]. > > ATT specs page is pretty crap (sounds like ATT :-)), but that type of > netbook was known under different model name as well which is AO531h. Here > are some much better details Thanks. One would have thought that the real place to find these would be at acer.com, of course, but no, they don't acknowledge the thing ever existed. > (not sure why you were looking for fxp driver in dmesg). Just guessing, really. It's one of the network interfaces illustrated in the relevant bit of <http://www.openbsd.org/faq/faq4.html> > All of that is > anyway showing path for you. Install -current i386 on it, not "old" OpenBSD > 5.4 release I downloaded 5.4 because it's the highest-numbered version listed in the mirror at <http://mirror.bytemark.co.uk/pub/OpenBSD/> , and 5.4 is the one mentioned at <http://www.openbsd.org/ftp.html>. I tend to think of snapshots as bleeding-edge things, but if the current snapshot is the preferred new download for OpenBSD, I'll note that for next time. >> However the >> wired interface _isn't_ detected, and the installation script goes >> straight from 'System hostname?' to 'DNS domain name?' even though >> it's plugged in to an ethernet network which is offering DHCP >> services. I can't see anything in the dmesg that's relevant (no 'fxp' >> or 'vlan'). I'm reasonably confident the network is behaving as it >> should, but it's _possible_, though unlikely, that the wired interface >> is simply broken (the machine's previous owner only ever used it >> wireless). Hmm: still doesn't work. I'm now starting to wonder if network interface is actually broken. They're generally rather robust, and there's no obvious damage. However the tell-tale light flickers on at power-up, and stays off thereafter, so that, plus the reassurance that this _should_ work with this release, makes me think of hardware brokenness as the next most likely thing. Damn. I'll reply to Martin's Brandenburg's message separately. Thanks for your help. All the best, Norman -- Norman Gray : http://nxg.me.uk SUPA School of Physics and Astronomy, University of Glasgow, UK
