Re: SUMMARY: Install 5.4 onto netbook... almost
Moss, hello. On 2014 Apr 14, at 08:05, Maurice McCarthy m...@mythic-beasts.com wrote: Though I've only been using OpenBSD for about a year and, from reading your posts, I'm clearly no where as competent as yourself, may I ask if you have downloaded the necessary firmware for the athn ethernet card? Ah, an interesting point. No, I didn't download any firmware for the card -- it Just Worked. If, as you suggest, this is to some extent unexpected, it's possibly explained by the machine having had Windows on it before: it _might_ be (I'm not sure I've necessarily convinced myself of the logic here) that this had ensured there were up-to-date drivers, in a way that wouldn't have been true if I'd installed OpenBSD onto the 'raw' machine. Best wishes, Norman -- Norman Gray : http://nxg.me.uk SUPA School of Physics and Astronomy, University of Glasgow, UK
Re: SUMMARY: Install 5.4 onto netbook... almost
On 2014-04-16 09:57, Norman Gray wrote: Moss, hello. On 2014 Apr 14, at 08:05, Maurice McCarthy m...@mythic-beasts.com wrote: Though I've only been using OpenBSD for about a year and, from reading your posts, I'm clearly no where as competent as yourself, may I ask if you have downloaded the necessary firmware for the athn ethernet card? Ah, an interesting point. No, I didn't download any firmware for the card -- it Just Worked. If, as you suggest, this is to some extent unexpected, it's possibly explained by the machine having had Windows on it before: it _might_ be (I'm not sure I've necessarily convinced myself of the logic here) that this had ensured there were up-to-date drivers, in a way that wouldn't have been true if I'd installed OpenBSD onto the 'raw' machine. Best wishes, Norman Ah so your ethernet is now working then! Yes? If so then good. I'd thought that one problem was that you could not connect to the internet using the netbook. The install script does download any firmware it finds necessary but, of course, if you needed to install ethernet firmware to do that then there is a self-defeating loop. Maybe your Macbook has the same card? Moss
Re: SUMMARY: Install 5.4 onto netbook... almost
Moss, hello. On 2014 Apr 16, at 14:17, Maurice McCarthy m...@sphinx.mythic-beasts.com wrote: Ah so your ethernet is now working then! Yes? If so then good. I'd thought that one problem was that you could not connect to the internet using the netbook. The install script does download any firmware it finds necessary but, of course, if you needed to install ethernet firmware to do that then there is a self-defeating loop. Maybe your Macbook has the same card? I was having difficulty connecting initially, because of the choice/lack of drivers on the floppy5x.fs images (if I recall correctly). Booting the install CD on the MacMini meant that I was able to create a bootable flash disk with a full install, which, in particular, did have drivers enough to support the ethernet interface at least. At that point, I didn't need a network at all, because the flash drive had the install sets on it, too, but it was necessary for installing packages later. I believe that this netbook's wireless interface is incompletely supported by OpenBSD, but I've deliberately left that unconfigured in any case. I want this to be 'the secure laptop', so if the ethernet cable's not plugged in, then I can be confident it's not on a network at all. I had vague plans to install it completely air-gapped, but that's more trouble than it's worth in my situation -- that would be for drill rather than need. I remember noticing that the MacMini seemed to have the same ethernet card manufacturer as the netbook, but that wasn't my principal concern at that point, so I can't be sure. All the best, Norman -- Norman Gray : http://nxg.me.uk SUPA School of Physics and Astronomy, University of Glasgow, UK
Re: SUMMARY: Install 5.4 onto netbook... almost
Norman, Though I've only been using OpenBSD for about a year and, from reading your posts, I'm clearly no where as competent as yourself, may I ask if you have downloaded the necessary firmware for the athn ethernet card? I don't think the OpenBSD license call allow it in the core install. http://firmware.openbsd.org Good Luck Moss
Re: SUMMARY: Install 5.4 onto netbook... almost
PS When the firmware is installed try # sh /etc/netstart
SUMMARY: Install 5.4 onto netbook... almost
Greetings, all. On 2014 Apr 6, at 18:09, Norman Gray nor...@astro.gla.ac.uk wrote: I'm trying to install the released OpenBSD 5.4 onto a old-ish netbook without an optical drive. I thought I could do this via install54.iso; I can see where I need to get to, and can almost get there, but I can't find the last step. Thanks, everyone, for your various strands of advice. In the end, I installed 5.4 onto the netbook by booting a Mac Mini (the only optical drive I have available) from a burned install54.iso image, using that to install OpenBSD onto a flash drive, and then copy the install sets onto the flash drive, and then booting the netbook from the flash drive. This specific route was first suggested, in that particular form, by Brett Mahar, but there a fair bit of overlap between the various suggestions, and I've learned a lot. For your edification and delight, I've included the dmesg output below (and also sent it to dm...@openbsd.org, of course). This route does allow the install to happen without the netbook ever being connected to a network. But when it comes time to add other packages atop the base, it'd clearly be possible, but a pain in the neck, to do that without a network. I used 5.4 rather than 5.5-current, because when it came to add packages it turned out that (if I'm reading the runes correctly) the 'python' package within 5.5-current requires /usr/lib/libssl.so.20.0, but 5.5-current installs /usr/lib/libssl.so.21.0. I did try installing OpenBSD into a Virtualbox instance hosted on OS X (as Martin Brandenburg suggested). That mostly worked, but I seemed unable to mount the flash drive on the virtual machine, even after being sure (as Martin noted) to eject the device from the OS X side beforehand. I didn't investigate where the problem really was. Again: close, but not quite, and I moved on to booting the Mini from the CD. Below are more detailed instructions (aka brain-dump), for the benefit of anyone going the same route. Boot the Mac Mini (or whatever) from the install CD, with the flash drive in place. The install process will let you select the flash drive as a target. After that's finished: # mkdir -p /mnt/5.4/i386 # cd /mnt/5.4/i386 # ftp http://mirror.bytemark.co.uk/OpenBSD/5.4/i386/SHA256 ...and so on, including each of the INSTALL.i386, bsd* and *.tgz files # halt (or whatever mirror you prefer). If you do this right after installing from the CD, the network is in place, and the flash drive mounted. If (as a result of more faffing around) the network isn't up or the drive isn't mounted, then you might need one or more of # ifconfig # find your ethernet interface # dhclient interface-name To mount the flash drive: # sysctl hw.disknames # show available disks # disklabel sd0 # show the partitions on device sd0 # mount /dev/sd0a /mnt # mount partition 'a' onto /mnt Then put the flash drive into the netbook, and boot it with boot b hd0a:/bsd.rd This again boots to the install script, which lets you install onto the netbook's hard drive (finally!). Gotcha: even if you don't plan to use X on the target machine (I imagine it would be a fairly unpleasant experience), you _do_ need to select and install at least xbase54, xetc54 and xshare54 (so you might as well just install the lot!). This is because ports and packages aren't tested in the no-X configuration, and at least one of the ports I wanted to install did indeed fail to build until I went round the whole cycle again and included them in the install onto the flash drive. I also installed the OS onto an encrypted filesystem (so that there isn't necessarily a problem if this machine gets lost or stolen). There are very good instructions for doing this at http://www.bsdnow.tv/tutorials/fde. Useful things to know: 1. # sysctl hw.disknames # shows the available disks; sd0 is my hard disk 2. I configured a swap of 3MB (which is a round number slightly larger than the amount that the automatic layout decided to give to it). 3. With the devices on this hardware, I had to use # bioctl -c C -l /dev/sd0a softraid0 This reports the crypto device being sd2. Back to the installer and, as suggested, use the Whole of the crypto device (so sd2 in my case), and create a custom layout with everything in partition a. Added '/dev/sd0b none swap sw' to the end of the fstab So... Thanks again to jordon, Tomas, Martin, Stuart, Moss, Brett and Jan (and of course a modest number of EUR to the Foundation). Best wishes, Norman dmesg: OpenBSD 5.4 (GENERIC.MP) #44: Tue Jul 30 12:13:32 MDT 2013 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Intel(R) Atom(TM) CPU N270 @ 1.60GHz (GenuineIntel 686-class) 1.60 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,xTPR,PDCM,MOVBE,LAHF,PERF real mem =
Re: Install 5.4 onto netbook... almost
On Apr 08 09:24:09, br...@coiloptic.org wrote: | http://www.openbsd.org/faq/faq14.html#flashmemLive | | That route would indeed work (I quoted both of those links in my original | email), but both require a pre-existing OpenBSD installation in order | to create the bootable full install on the flash drive. That pre-existing | installation is what I don't have. Firstly, try with -current; there are many improvements over the 5.4 release, and possibly your network card ill just work, eliminating your original problem. If your problem persists, get any old PC for free; actually, you would be better off doing your first OpenBSD experience on such a 'regular' machine. Then: 1. download openbsd iso and burn to cd (can be done from windows/openbsd/linux/anything) 2. boot from cd after plugging usb stick into machine 3. install openbsd selecting usb stick as the target hard drive. That USB stick will be a regular OpenBSD install then. Boot from it, and downlad the install sets onto it. Then plug it into your target machine and you can both (1) boot the existing OpenBSD install from that stick (2) install OpenBSD on your machine from that stick. Jan
Re: Install 5.4 onto netbook... almost
Another possible solution is to make a default 5.4 install to a raw qemu image in OSX or FreeBSD and dd that to a usb stick. Regards Moss
Re: Install 5.4 onto netbook... almost
On Mon, 7 Apr 2014 10:35:31 +0100 Maurice McCarthy m...@mythic-beasts.com wrote: | Another possible solution is to make a default 5.4 install to a raw qemu image in OSX or FreeBSD and dd that to a usb stick. | | Regards | Moss | Maybe I missed some of the posts but instead of all these crazy convoluted methods, just install to a usb drive on a regular computer (ie one with a cd rom) then boot ramdisk (bsd.rd) on your netbook, explanations at: http://www.openbsd.org/faq/faq14.html#flashmemLive and slightly more complicated: http://undeadly.org/cgi?action=articlesid=20140225072408
Re: Install 5.4 onto netbook... almost
On Mon, Apr 7, 2014 at 1:36 PM, Brett Mahar br...@coiloptic.org wrote: On Mon, 7 Apr 2014 10:35:31 +0100 Maurice McCarthy m...@mythic-beasts.com wrote: | Another possible solution is to make a default 5.4 install to a raw qemu image in OSX or FreeBSD and dd that to a usb stick. | | Regards | Moss | Maybe I missed some of the posts but instead of all these crazy convoluted methods, just install to a usb drive on a regular computer (ie one with a cd rom) then boot ramdisk (bsd.rd) on your netbook, explanations at: http://www.openbsd.org/faq/faq14.html#flashmemLive and slightly more complicated: http://undeadly.org/cgi?action=articlesid=20140225072408 but still 5.4 is quite old now. His best bet now is to use and try -current. He may be surprised what things are already solved.
Re: Install 5.4 onto netbook... almost
On 2014/04/07 13:08, Norman Gray wrote: Stuart, hello. On 2014 Apr 6, at 23:39, Stuart Henderson s...@spacehopper.org wrote: ale(4) and the USB drivers are not on the single-floppy installer that you're using, hence the lack of network and flash devices. Ah, well that explains _that_ little problem, and neatly closes off a fruitless avenue. Oh - your other method (which should work for 5.4 too) is to pxeboot. Just needs a dhcp server (see mdoc.su/o/pxeboot for details) and tftp serving the pxeboot and bsd.rd files. But wouldn't that require a working network adapter? Since the wireless adapter in this netbook isn't supported by OpenBSD, and as you explain the wired interface isn't supported on the floppy.fs installer, doesn't this rule out a pxeboot? (or am I getting myself terribly confused?) Thanks! Norman There's a small piece of knowledge that you're missing; floppy.fs uses the RAMDISK kernel, which is a single-floppy kernel with tight size restrictions. pxeboot uses bsd.rd which is a RAMDISK_CD kernel which has a much larger set of drivers. I used this method to install onto my ZG5 which is quite similar to your ZG8. Apart from the supplied wireless card not being supported (which I handled by swapping with a different card, though the tiny USB adapters are also an option), on the whole OpenBSD works pretty well on my machine (and it was I think the first machine to have ACPI suspend+resume). Only problem I run into is that occasionally the keyboard doesn't work at boot; if so, the first thing to try is suspending and resuming, which clears it about half the time it happens.
Re: Install 5.4 onto netbook... almost
On 2014-04-07, Brett Mahar br...@coiloptic.org wrote: On Mon, 7 Apr 2014 10:35:31 +0100 Maurice McCarthy m...@mythic-beasts.com wrote: | Another possible solution is to make a default 5.4 install to a raw qemu image in OSX or FreeBSD and dd that to a usb stick. | | Regards | Moss | Maybe I missed some of the posts but instead of all these crazy convoluted methods, just install to a usb drive on a regular computer (ie one with a cd rom) then boot ramdisk (bsd.rd) on your netbook, explanations at: http://www.openbsd.org/faq/faq14.html#flashmemLive and slightly more complicated: http://undeadly.org/cgi?action=articlesid=20140225072408 While this is a good method, it's probably better suited to somebody who either already is quite familiar with OpenBSD or has a spare machine where it won't be a problem if a mistake is made.
Re: Install 5.4 onto netbook... almost
Stuart, hello. On 2014 Apr 6, at 23:39, Stuart Henderson s...@spacehopper.org wrote: ale(4) and the USB drivers are not on the single-floppy installer that you're using, hence the lack of network and flash devices. Ah, well that explains _that_ little problem, and neatly closes off a fruitless avenue. Oh - your other method (which should work for 5.4 too) is to pxeboot. Just needs a dhcp server (see mdoc.su/o/pxeboot for details) and tftp serving the pxeboot and bsd.rd files. But wouldn't that require a working network adapter? Since the wireless adapter in this netbook isn't supported by OpenBSD, and as you explain the wired interface isn't supported on the floppy.fs installer, doesn't this rule out a pxeboot? (or am I getting myself terribly confused?) Thanks! Norman -- Norman Gray : http://nxg.me.uk SUPA School of Physics and Astronomy, University of Glasgow, UK
Re: Install 5.4 onto netbook... almost
Brett, hello. On 2014 Apr 7, at 12:36, Brett Mahar br...@coiloptic.org wrote: Maybe I missed some of the posts but instead of all these crazy convoluted methods, just install to a usb drive on a regular computer (ie one with a cd rom) then boot ramdisk (bsd.rd) on your netbook, explanations at: http://www.openbsd.org/faq/faq14.html#flashmemLive and slightly more complicated: http://undeadly.org/cgi?action=articlesid=20140225072408 That route would indeed work (I quoted both of those links in my original email), but both require a pre-existing OpenBSD installation in order to create the bootable full install on the flash drive. That pre-existing installation is what I don't have. It sounds as if the best next step is to install 5.5-current onto a virtual machine, either Virtualbox or Qemu (thanks, Moss), which will allow me to go this route. I imagine that that will be quite a quick solution, once I start. It's tantalising that the other routes I described seemed to bring me s close to the promised land, prevented only by single final barriers. Somewhat educational barriers, yes, but still insuperable; so it's not time wasted. Thanks, all. I'll report back when I clear time to have a go at this. Best wishes, Norman -- Norman Gray : http://nxg.me.uk SUPA School of Physics and Astronomy, University of Glasgow, UK
Re: Install 5.4 onto netbook... almost
Norman Gray nor...@astro.gla.ac.uk wrote: Stuart, hello. On 2014 Apr 6, at 23:39, Stuart Henderson s...@spacehopper.org wrote: ale(4) and the USB drivers are not on the single-floppy installer that you're using, hence the lack of network and flash devices. Ah, well that explains _that_ little problem, and neatly closes off a \ fruitless avenue. Oh - your other method (which should work for 5.4 too) is to pxeboot. Just needs a dhcp server (see mdoc.su/o/pxeboot for details) and tftp serving the pxeboot and bsd.rd files. But wouldn't that require a working network adapter? Since the wireless adapter in this netbook isn't supported by OpenBSD, and as you explain the wired interface isn't supported on the floppy.fs installer, doesn't this rule out a pxeboot? (or am I getting myself terribly confused?) Thanks! Norman -- Norman Gray : http://nxg.me.uk SUPA School of Physics and Astronomy, University of Glasgow, UK A pxeboot is done by the firmware, so OpenBSD's hardware support doesn't enter into it (however if you have machines that netboot and then mount root from NFS they would obviously need hardware support; this does not apply to you but you may see the paradigm in netboot documentation). Once RAMDISK_CD is loaded you should be able to use the wired network and USB. Use either the bsd.rd on the distribution servers or one from cdXX.iso or installXX.iso - Martin
Re: Install 5.4 onto netbook... almost
On Mon, 7 Apr 2014 13:08:08 +0100 Norman Gray nor...@astro.gla.ac.uk wrote: | Brett, hello. | | On 2014 Apr 7, at 12:36, Brett Mahar br...@coiloptic.org wrote: | | Maybe I missed some of the posts but instead of all these crazy convoluted methods, just install to a usb drive on a regular computer (ie one with a cd rom) then boot ramdisk (bsd.rd) on your netbook, explanations at: | | http://www.openbsd.org/faq/faq14.html#flashmemLive | | and slightly more complicated: | | http://undeadly.org/cgi?action=articlesid=20140225072408 | | That route would indeed work (I quoted both of those links in my original | email), but both require a pre-existing OpenBSD installation in order | to create the bootable full install on the flash drive. That pre-existing | installation is what I don't have. | Hi Norman, You wouldn't need a pre-existing machine with openbsd on it, any machine with a cdrom will do, ie 1. download openbsd iso and burn to cd (can be done from windows/openbsd/linux/anything) 2. boot from cd after plugging usb stick into machine 3. install openbsd selecting usb stick as the target hard drive (probably be sd0 but during that part of install you can press '?' for details and make sure you select the correct 'disk' Brett.
Install 5.4 onto netbook... almost
Greetings. I'm trying to install the released OpenBSD 5.4 onto a old-ish netbook without an optical drive. I thought I could do this via install54.iso; I can see where I need to get to, and can almost get there, but I can't find the last step. I suspect this needs only a 1- or 2-line answer. Target machine (not ideal, admittedly): * Acer Aspire One ZG8 ('no, don't throw it out, I'll try OpenBSD on it!') [1] * ...so i386 * Internal disk * No optical drive, but two USB ports and an SD slot * Previously had Windows on it *shudder* * No dmesg, I'm afraid, since part of my problem is an inability to mount any storage. I can boot the machine with the floppy.fs image (dd'ed to a flash drive), and go through the configuration, accepting defaults, and whole-disk partitioning the internal disk, to the point where I select the full installation media. This I can't do. 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]. 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). But there's not much to go on, and I'm uncertain how to debug this further. But it's OK!: I can install it from install54.iso, also dd'ed to a flash drive. (the machine's intended for offline use, so 'never connected to the internet' would be a somewhat desirable property). And this is where I'm stuck. The install54.iso isn't bootable in this context, but all I need to do is to boot the machine using floppy.fs, then mount the install54 flash drive, and give that as the 'disks' target. But (plan A) if I select 'disks' as the location of the sets, the only device that comes up is the internal hard disk, and this is true whether I have the install54 flash drive plugged in to the second USB port, alongside the floppy.fs drive on a USB expander, or burned to an SD card. Again, nothing obviously relevant in dmesg -- I can see the wd0 device being detected, but no obvious 'USB failure'. The USB port/bus works, since that's where the bootable floppy.fs is sitting. OK, Plan B. The second-stage boot is detecting three devices (namely internal hard disk, plus the floppy.fs drive and the install54 drive): 'hd0', 'hd1', 'hd2'. So I try booting directly from there: boot b hd0:/5.4/i386/bsd (and so on through hd{0,1,2}{,a,c}:, with and without the leading slash, ..., -- I'm getting a bit desperate here), but I get 'no such file or directory' or 'invalid argument'. Looking at 'm diskinfo' tells me that there are three devices there (which is what I expect), but not much more. I'm vague about the details, but I have a reasonably secure schematic understanding of the boot process, which doesn't conflict with what I read in [3]. I'd be interested to know what I'm missing or misunderstanding. Plan C: create a custom installer (eg [4, 5]). That appears to depend on having a working OpenBSD system, to call /usr/mdec/installboot. But I don't -- the other OSs I have to hand are OS X and FreeBSD. Plan d (not worth a capital letter): it looks like I could try copying /bsd from /5.4/i386/bsd to the top of that filesystem and... see what happens, but (a) I run into filesystem support limitations on OS X, and (b) even if I dealt with that, I'd still have to make the modified filesystem bootable. bless(8) [6] is the broad analogue of installboot on OS X, but I suspect it's specific to both HFS+ and to Apple's BIOS, so this seems unlikely to work. Even then, 'flailing around blindly' is never a good problem solving strategy. Plan e: I could try booting the Mac with the floppy.fs, doing an OpenBSD install onto another flash drive, making _that_ bootable, and... no. On my main work machine, that could go very wrong very quickly (!), and I'm not even going to go there unless I'm very confident I know what I'm doing. So there I am. Plans A and B seem tantalisingly close to a solution, but missing a final step. Writing out the email hasn't produced an 'aha!'; a fair amount of googling suggests I'm not missing anything terribly obvious (somewhat surprisingly: this is a slightly odd configuration I'm attempting, but not insanely exotic); the misc@openbsd.org list doesn't appear to be searchable (right?). So I seem to have exhausted the DIY possibilities. Therefore... Dear list: What is the one line I'm missing? Thanks for any pointers. Norman [1] http://www.att.com/esupport/article.jsp?sid=KB102059cv=820 [2] http://www.darwinsys.com/openbsd/laptops.html [3]
Re: Install 5.4 onto netbook... almost
On Sun, Apr 6, 2014 at 7:09 PM, Norman Gray nor...@astro.gla.ac.uk wrote: Greetings. I'm trying to install the released OpenBSD 5.4 onto a old-ish netbook without an optical drive. I thought I could do this via install54.iso; I can see where I need to get to, and can almost get there, but I can't find the last step. I suspect this needs only a 1- or 2-line answer. Target machine (not ideal, admittedly): * Acer Aspire One ZG8 ('no, don't throw it out, I'll try OpenBSD on it!') [1] * ...so i386 * Internal disk * No optical drive, but two USB ports and an SD slot * Previously had Windows on it *shudder* * No dmesg, I'm afraid, since part of my problem is an inability to mount any storage. I can boot the machine with the floppy.fs image (dd'ed to a flash drive), and go through the configuration, accepting defaults, and whole-disk partitioning the internal disk, to the point where I select the full installation media. This I can't do. 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]. 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). But there's not much to go on, and I'm uncertain how to debug this further. But it's OK!: I can install it from install54.iso, also dd'ed to a flash drive. (the machine's intended for offline use, so 'never connected to the internet' would be a somewhat desirable property). And this is where I'm stuck. The install54.iso isn't bootable in this context, but all I need to do is to boot the machine using floppy.fs, then mount the install54 flash drive, and give that as the 'disks' target. But (plan A) if I select 'disks' as the location of the sets, the only device that comes up is the internal hard disk, and this is true whether I have the install54 flash drive plugged in to the second USB port, alongside the floppy.fs drive on a USB expander, or burned to an SD card. Again, nothing obviously relevant in dmesg -- I can see the wd0 device being detected, but no obvious 'USB failure'. The USB port/bus works, since that's where the bootable floppy.fs is sitting. OK, Plan B. The second-stage boot is detecting three devices (namely internal hard disk, plus the floppy.fs drive and the install54 drive): 'hd0', 'hd1', 'hd2'. So I try booting directly from there: boot b hd0:/5.4/i386/bsd (and so on through hd{0,1,2}{,a,c}:, with and without the leading slash, ..., -- I'm getting a bit desperate here), but I get 'no such file or directory' or 'invalid argument'. Looking at 'm diskinfo' tells me that there are three devices there (which is what I expect), but not much more. I'm vague about the details, but I have a reasonably secure schematic understanding of the boot process, which doesn't conflict with what I read in [3]. I'd be interested to know what I'm missing or misunderstanding. Plan C: create a custom installer (eg [4, 5]). That appears to depend on having a working OpenBSD system, to call /usr/mdec/installboot. But I don't -- the other OSs I have to hand are OS X and FreeBSD. Plan d (not worth a capital letter): it looks like I could try copying /bsd from /5.4/i386/bsd to the top of that filesystem and... see what happens, but (a) I run into filesystem support limitations on OS X, and (b) even if I dealt with that, I'd still have to make the modified filesystem bootable. bless(8) [6] is the broad analogue of installboot on OS X, but I suspect it's specific to both HFS+ and to Apple's BIOS, so this seems unlikely to work. Even then, 'flailing around blindly' is never a good problem solving strategy. Plan e: I could try booting the Mac with the floppy.fs, doing an OpenBSD install onto another flash drive, making _that_ bootable, and... no. On my main work machine, that could go very wrong very quickly (!), and I'm not even going to go there unless I'm very confident I know what I'm doing. So there I am. Plans A and B seem tantalisingly close to a solution, but missing a final step. Writing out the email hasn't produced an 'aha!'; a fair amount of googling suggests I'm not missing anything terribly obvious (somewhat surprisingly: this is a slightly odd configuration I'm attempting, but not insanely exotic); the misc@openbsd.org list doesn't appear to be searchable (right?). So I seem to have exhausted the DIY possibilities. Therefore... Dear list: What is the one line I'm missing?
Re: Install 5.4 onto netbook... almost
On Apr 6, 2014, at 14:43, Tomas Bodzar tomas.bod...@gmail.com wrote: On Sun, Apr 6, 2014 at 7:09 PM, Norman Gray nor...@astro.gla.ac.uk wrote: Greetings. I'm trying to install the released OpenBSD 5.4 onto a old-ish netbook without an optical drive. I thought I could do this via install54.iso; I can see where I need to get to, and can almost get there, but I can't find the last step. I suspect this needs only a 1- or 2-line answer. Target machine (not ideal, admittedly): * Acer Aspire One ZG8 ('no, don't throw it out, I'll try OpenBSD on it!') [1] * ...so i386 * Internal disk * No optical drive, but two USB ports and an SD slot * Previously had Windows on it *shudder* * No dmesg, I'm afraid, since part of my problem is an inability to mount any storage. I can boot the machine with the floppy.fs image (dd'ed to a flash drive), and go through the configuration, accepting defaults, and whole-disk partitioning the internal disk, to the point where I select the full installation media. This I can't do. 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]. 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). But there's not much to go on, and I'm uncertain how to debug this further. But it's OK!: I can install it from install54.iso, also dd'ed to a flash drive. (the machine's intended for offline use, so 'never connected to the internet' would be a somewhat desirable property). And this is where I'm stuck. The install54.iso isn't bootable in this context, but all I need to do is to boot the machine using floppy.fs, then mount the install54 flash drive, and give that as the 'disks' target. But (plan A) if I select 'disks' as the location of the sets, the only device that comes up is the internal hard disk, and this is true whether I have the install54 flash drive plugged in to the second USB port, alongside the floppy.fs drive on a USB expander, or burned to an SD card. Again, nothing obviously relevant in dmesg -- I can see the wd0 device being detected, but no obvious 'USB failure'. The USB port/bus works, since that's where the bootable floppy.fs is sitting. OK, Plan B. The second-stage boot is detecting three devices (namely internal hard disk, plus the floppy.fs drive and the install54 drive): 'hd0', 'hd1', 'hd2'. So I try booting directly from there: boot b hd0:/5.4/i386/bsd (and so on through hd{0,1,2}{,a,c}:, with and without the leading slash, ..., -- I'm getting a bit desperate here), but I get 'no such file or directory' or 'invalid argument'. Looking at 'm diskinfo' tells me that there are three devices there (which is what I expect), but not much more. I'm vague about the details, but I have a reasonably secure schematic understanding of the boot process, which doesn't conflict with what I read in [3]. I'd be interested to know what I'm missing or misunderstanding. Plan C: create a custom installer (eg [4, 5]). That appears to depend on having a working OpenBSD system, to call /usr/mdec/installboot. But I don't -- the other OSs I have to hand are OS X and FreeBSD. Plan d (not worth a capital letter): it looks like I could try copying /bsd from /5.4/i386/bsd to the top of that filesystem and... see what happens, but (a) I run into filesystem support limitations on OS X, and (b) even if I dealt with that, I'd still have to make the modified filesystem bootable. bless(8) [6] is the broad analogue of installboot on OS X, but I suspect it's specific to both HFS+ and to Apple's BIOS, so this seems unlikely to work. Even then, 'flailing around blindly' is never a good problem solving strategy. Plan e: I could try booting the Mac with the floppy.fs, doing an OpenBSD install onto another flash drive, making _that_ bootable, and... no. On my main work machine, that could go very wrong very quickly (!), and I'm not even going to go there unless I'm very confident I know what I'm doing. So there I am. Plans A and B seem tantalisingly close to a solution, but missing a final step. Writing out the email hasn't produced an 'aha!'; a fair amount of googling suggests I'm not missing anything terribly obvious (somewhat surprisingly: this is a slightly odd configuration I'm attempting, but not insanely exotic); the misc@openbsd.org list doesn't appear to be searchable (right?). So I seem to have exhausted
Re: Install 5.4 onto netbook... almost
On Sun, Apr 6, 2014 at 7:09 PM, Norman Gray nor...@astro.gla.ac.uk wrote: Greetings. I'm trying to install the released OpenBSD 5.4 onto a old-ish netbook without an optical drive. I thought I could do this via install54.iso; I can see where I need to get to, and can almost get there, but I can't find the last step. I suspect this needs only a 1- or 2-line answer. Target machine (not ideal, admittedly): * Acer Aspire One ZG8 ('no, don't throw it out, I'll try OpenBSD on it!') [1] * ...so i386 * Internal disk * No optical drive, but two USB ports and an SD slot * Previously had Windows on it *shudder* * No dmesg, I'm afraid, since part of my problem is an inability to mount any storage. I can boot the machine with the floppy.fs image (dd'ed to a flash drive), and go through the configuration, accepting defaults, and whole-disk partitioning the internal disk, to the point where I select the full installation media. This I can't do. 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 http://drp.su/drivers/notebooks/?v=acerm=AO531hid=39058l=en and based on that wired interface is really supposed to work and be supported by this http://www.openbsd.org/cgi-bin/man.cgi?query=alesektion=4apropos=0manpath=OpenBSD+Currentarch=i386(not sure why you were looking for fxp driver in dmesg). All of that is anyway showing path for you. Install -current i386 on it, not old OpenBSD 5.4 release 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). But there's not much to go on, and I'm uncertain how to debug this further. But it's OK!: I can install it from install54.iso, also dd'ed to a flash drive. (the machine's intended for offline use, so 'never connected to the internet' would be a somewhat desirable property). And this is where I'm stuck. The install54.iso isn't bootable in this context, but all I need to do is to boot the machine using floppy.fs, then mount the install54 flash drive, and give that as the 'disks' target. But (plan A) if I select 'disks' as the location of the sets, the only device that comes up is the internal hard disk, and this is true whether I have the install54 flash drive plugged in to the second USB port, alongside the floppy.fs drive on a USB expander, or burned to an SD card. Again, nothing obviously relevant in dmesg -- I can see the wd0 device being detected, but no obvious 'USB failure'. The USB port/bus works, since that's where the bootable floppy.fs is sitting. OK, Plan B. The second-stage boot is detecting three devices (namely internal hard disk, plus the floppy.fs drive and the install54 drive): 'hd0', 'hd1', 'hd2'. So I try booting directly from there: boot b hd0:/5.4/i386/bsd (and so on through hd{0,1,2}{,a,c}:, with and without the leading slash, ..., -- I'm getting a bit desperate here), but I get 'no such file or directory' or 'invalid argument'. Looking at 'm diskinfo' tells me that there are three devices there (which is what I expect), but not much more. I'm vague about the details, but I have a reasonably secure schematic understanding of the boot process, which doesn't conflict with what I read in [3]. I'd be interested to know what I'm missing or misunderstanding. Plan C: create a custom installer (eg [4, 5]). That appears to depend on having a working OpenBSD system, to call /usr/mdec/installboot. But I don't -- the other OSs I have to hand are OS X and FreeBSD. Plan d (not worth a capital letter): it looks like I could try copying /bsd from /5.4/i386/bsd to the top of that filesystem and... see what happens, but (a) I run into filesystem support limitations on OS X, and (b) even if I dealt with that, I'd still have to make the modified filesystem bootable. bless(8) [6] is the broad analogue of installboot on OS X, but I suspect it's specific to both HFS+ and to Apple's BIOS, so this seems unlikely to work. Even then, 'flailing around blindly' is never a good problem solving strategy. Plan e: I could try booting the Mac with the floppy.fs, doing an OpenBSD install onto another flash drive, making _that_ bootable, and... no. On my main work machine, that could go very wrong very quickly (!), and I'm not even
Re: Install 5.4 onto netbook... almost
Norman Gray nor...@astro.gla.ac.uk wrote: Greetings. I'm trying to install the released OpenBSD 5.4 onto a old-ish netbook without an optical drive. I thought I could do this via install54.iso; I can see where I need to get to, and can almost get there, but I can't find the last step. I suspect this needs only a 1- or 2-line answer. Target machine (not ideal, admittedly): * Acer Aspire One ZG8 ('no, don't throw it out, I'll try OpenBSD on it!') \ [1] * ...so i386 * Internal disk * No optical drive, but two USB ports and an SD slot * Previously had Windows on it *shudder* * No dmesg, I'm afraid, since part of my problem is an inability to mount any storage. I can boot the machine with the floppy.fs image (dd'ed to a flash drive), and go through the configuration, accepting defaults, and whole-disk partitioning the internal disk, to the point where I select the full installation media. This I can't do. 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]. 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). But there's not much to go on, and I'm uncertain how to debug this further. But it's OK!: I can install it from install54.iso, also dd'ed to a flash drive. (the machine's intended for offline use, so 'never connected to the internet' would be a somewhat desirable property). And this is where I'm stuck. The install54.iso isn't bootable in this context, but all I need to do is to boot the machine using floppy.fs, then mount the install54 flash drive, and give that as the 'disks' target. But (plan A) if I select 'disks' as the location of the sets, the only device that comes up is the internal hard disk, and this is true whether I have the install54 flash drive plugged in to the second USB port, alongside the floppy.fs drive on a USB expander, or burned to an SD card. Again, nothing obviously relevant in dmesg -- I can see the wd0 device being detected, but no obvious 'USB failure'. The USB port/bus works, since that's where the bootable floppy.fs is sitting. OK, Plan B. The second-stage boot is detecting three devices (namely internal hard disk, plus the floppy.fs drive and the install54 drive): 'hd0', 'hd1', 'hd2'. So I try booting directly from there: boot b hd0:/5.4/i386/bsd (and so on through hd{0,1,2}{,a,c}:, with and without the leading slash, ..., -- I'm getting a bit desperate here), but I get 'no such file or directory' or 'invalid argument'. Looking at 'm diskinfo' tells me that there are three devices there (which is what I expect), but not much more. I'm vague about the details, but I have a reasonably secure schematic understanding of the boot process, which doesn't conflict with what I read in [3]. I'd be interested to know what I'm missing or misunderstanding. Plan C: create a custom installer (eg [4, 5]). That appears to depend on having a working OpenBSD system, to call /usr/mdec/installboot. But I don't -- the other OSs I have to hand are OS X and FreeBSD. Plan d (not worth a capital letter): it looks like I could try copying /bsd from /5.4/i386/bsd to the top of that filesystem and... see what happens, but (a) I run into filesystem support limitations on OS X, and (b) even if I dealt with that, I'd still have to make the modified filesystem bootable. bless(8) [6] is the broad analogue of installboot on OS X, but I suspect it's specific to both HFS+ and to Apple's BIOS, so this seems unlikely to work. Even then, 'flailing around blindly' is never a good problem solving strategy. Plan e: I could try booting the Mac with the floppy.fs, doing an OpenBSD install onto another flash drive, making _that_ bootable, and... no. On my main work machine, that could go very wrong very quickly (!), and I'm not even going to go there unless I'm very confident I know what I'm doing. So there I am. Plans A and B seem tantalisingly close to a solution, but missing a final step. Writing out the email hasn't produced an 'aha!'; a fair amount of googling suggests I'm not missing anything terribly obvious (somewhat surprisingly: this is a slightly odd configuration I'm attempting, but not insanely exotic); the misc@openbsd.org list doesn't appear to be searchable (right?). So I seem to have exhausted the DIY possibilities. Therefore... Dear list: What is the one line I'm missing? Thanks
Re: Install 5.4 onto netbook... almost
Norman Gray nor...@astro.gla.ac.uk wrote: Greetings. I'm trying to install the released OpenBSD 5.4 onto a old-ish netbook without an optical drive. I thought I could do this via install54.iso; I can see where I need to get to, and can almost get there, but I can't find the last step. I suspect this needs only a 1- or 2-line answer. Target machine (not ideal, admittedly): * Acer Aspire One ZG8 ('no, don't throw it out, I'll try OpenBSD on it!') \ [1] * ...so i386 * Internal disk * No optical drive, but two USB ports and an SD slot * Previously had Windows on it *shudder* * No dmesg, I'm afraid, since part of my problem is an inability to mount any storage. I can boot the machine with the floppy.fs image (dd'ed to a flash drive), and go through the configuration, accepting defaults, and whole-disk partitioning the internal disk, to the point where I select the full installation media. This I can't do. 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]. 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). But there's not much to go on, and I'm uncertain how to debug this further. But it's OK!: I can install it from install54.iso, also dd'ed to a flash drive. (the machine's intended for offline use, so 'never connected to the internet' would be a somewhat desirable property). And this is where I'm stuck. The install54.iso isn't bootable in this context, but all I need to do is to boot the machine using floppy.fs, then mount the install54 flash drive, and give that as the 'disks' target. But (plan A) if I select 'disks' as the location of the sets, the only device that comes up is the internal hard disk, and this is true whether I have the install54 flash drive plugged in to the second USB port, alongside the floppy.fs drive on a USB expander, or burned to an SD card. Again, nothing obviously relevant in dmesg -- I can see the wd0 device being detected, but no obvious 'USB failure'. The USB port/bus works, since that's where the bootable floppy.fs is sitting. OK, Plan B. The second-stage boot is detecting three devices (namely internal hard disk, plus the floppy.fs drive and the install54 drive): 'hd0', 'hd1', 'hd2'. So I try booting directly from there: boot b hd0:/5.4/i386/bsd (and so on through hd{0,1,2}{,a,c}:, with and without the leading slash, ..., -- I'm getting a bit desperate here), but I get 'no such file or directory' or 'invalid argument'. Looking at 'm diskinfo' tells me that there are three devices there (which is what I expect), but not much more. I'm vague about the details, but I have a reasonably secure schematic understanding of the boot process, which doesn't conflict with what I read in [3]. I'd be interested to know what I'm missing or misunderstanding. Plan C: create a custom installer (eg [4, 5]). That appears to depend on having a working OpenBSD system, to call /usr/mdec/installboot. But I don't -- the other OSs I have to hand are OS X and FreeBSD. Plan d (not worth a capital letter): it looks like I could try copying /bsd from /5.4/i386/bsd to the top of that filesystem and... see what happens, but (a) I run into filesystem support limitations on OS X, and (b) even if I dealt with that, I'd still have to make the modified filesystem bootable. bless(8) [6] is the broad analogue of installboot on OS X, but I suspect it's specific to both HFS+ and to Apple's BIOS, so this seems unlikely to work. Even then, 'flailing around blindly' is never a good problem solving strategy. Plan e: I could try booting the Mac with the floppy.fs, doing an OpenBSD install onto another flash drive, making _that_ bootable, and... no. On my main work machine, that could go very wrong very quickly (!), and I'm not even going to go there unless I'm very confident I know what I'm doing. So there I am. Plans A and B seem tantalisingly close to a solution, but missing a final step. Writing out the email hasn't produced an 'aha!'; a fair amount of googling suggests I'm not missing anything terribly obvious (somewhat surprisingly: this is a slightly odd configuration I'm attempting, but not insanely exotic); the misc@openbsd.org list doesn't appear to be searchable (right?). So I seem to have exhausted the DIY possibilities. Therefore... Dear list: What is the one line I'm missing? Thanks
Re: Install 5.4 onto netbook... almost
Martin, hello. On 2014 Apr 6, at 22:21, mar...@martinbrandenburg.com (Martin Brandenburg) wrote: Assuming you are somewhat experienced with OpenBSD, setting up a bootable USB with install sets isn't hard. Among BSDs, I'm familiar with Solaris (a long while ago), OS X and FreeBSD, but this is my first time giving OpenBSD a spin. It's a pity I'm doing it with suboptimal hardware. And you'll be good to go. Thanks. But you need OpenBSD to run that, as you already know. If the MacBook you're using is x86, you'll be able to run VirtualBox and do it from there. The trick is to eject the USB drive from disk utility so you can attach it as a USB device to VirtualBox. That's an interesting plan, and thanks for the gotcha. I'll give that a try, though perhaps not tonight. Since you can boot floppy.fs, it _might_ be possible to run mount_cd9660 on a partition containing the ISO image. My problem there is that I can't get the image onto the netbook's disk, because I seem to be unable to see the flash drive with the image burned to it. That's a bit of a puzzle. With two flash drives plugged in (containing floppy.fs and install55), the boot sequence reports hd0, hd1 and hd2, as expected, but sysctl reports only rd0 and wd0, and there's nothing likely in /dev. I'm wondering if this blasted machine is even more broken than I now think it is. I have also done your plan e before. If you're really worried you can disconnect the hard drive before trying it. It's interesting to know that this is possible. Thanks for your help. All the best, Norman -- Norman Gray : http://nxg.me.uk SUPA School of Physics and Astronomy, University of Glasgow, UK
Re: Install 5.4 onto netbook... almost
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
Re: Install 5.4 onto netbook... almost
Unlike some OS which have special 'hybrid' iso images that also include an HD-like partition table, OpenBSD's are simple CD ISO images. For 5.5 (not yet released) there's a dd'able install55.fs image. If you want something to try now there are -current snapshots which also have this; they are *newer* than 5.5 so you will either need to reinstall to 5.5 later if you want the release (downgrades aren't supported), or stick with -current until 5.6 (which will require occasional updates of base os + packages). Testing -current to see if your NIC is detected would certainly be a good idea even if you prefer to run releases.
Re: Install 5.4 onto netbook... almost
On 2014-04-06, Norman Gray nor...@astro.gla.ac.uk wrote: 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 ale(4) and the USB drivers are not on the single-floppy installer that you're using, hence the lack of network and flash devices.
Re: Install 5.4 onto netbook... almost
On 2014-04-06, Stuart Henderson s...@spacehopper.org wrote: Unlike some OS which have special 'hybrid' iso images that also include an HD-like partition table, OpenBSD's are simple CD ISO images. For 5.5 (not yet released) there's a dd'able install55.fs image. If you want something to try now there are -current snapshots which also have this; they are *newer* than 5.5 so you will either need to reinstall to 5.5 later if you want the release (downgrades aren't supported), or stick with -current until 5.6 (which will require occasional updates of base os + packages). Testing -current to see if your NIC is detected would certainly be a good idea even if you prefer to run releases. Oh - your other method (which should work for 5.4 too) is to pxeboot. Just needs a dhcp server (see mdoc.su/o/pxeboot for details) and tftp serving the pxeboot and bsd.rd files.