LinuxQuestions.org
Latest LQ Deal: Linux Power User Bundle
Go Back   LinuxQuestions.org > Blogs > Musings on technology, philosophy, and life in the corporate world
User Name
Password

Notices


Hi. I'm a Unix Administrator, mathematics enthusiast, and amateur philosopher. This is where I rant about that which upsets me, laugh about that which amuses me, and jabber about that which holds my interest most: Unix.
Rate this Entry

u-boot is infuriating

Posted 08-08-2018 at 04:36 AM by rocket357

Spent the better part of the night screwing around with installing OpenBSD on a Raspberry Pi 3 B+ (note the subtle extra character right at the end, there). It's irritating that a device can go from Version "3 B" to "3 B+" and so much changed. Spent a good bit of time goofing around with dtb files and trying to find the magic combination that would allow me to boot. Got close a few times, but the ethernet port refused to show up.

Ok, perhaps this is just an issue of how OpenBSD interprets or interacts with the dtb file? I dunno, but in the interest of not being here all night goofing with dtb files, I just want to get the OS installed.

Oh. My. God.

I thought I was at my ropes end with dtb files. No. U-can't-boot threw a hissy fit with virtually every single USB device I threw at it. USB-SATA disk? Apparently the disk doesn't come up soon enough for U-boot. DataTraveler? Documented madness! PNY 64G usb stick (sorry, cover was removed, don't recall the model)? Ok, that *might* legit be a bad usb stick, but I haven't tested yet. I'm on my third "generic" usb stick now.

So after throwing the install sets on a usb/sd adapter with a PNY 16G sd card in it (Note to self: put in a FR: can I get a RPI 4 with 2* sd slots?) and booting with every other usb card I have (I'd use the usb/sd adapter, as it seems incredibly reliable, at least in terms of the RPI, but I need that for other projects, sadly), I'm on install number <lost_track> and I'm going to throw my Mac out the window if it fails once more (yeah, not really the silver fisher price's fault, as I'm just ssh'ing to an OpenBSD/amd64 box with it to run the serial console from, but I'm really annoyed with the Mac anyways and well, I'm tired of looking at it).

Rebooting the pi in a few seconds...

Ahh, the funniest response thus far. I get "scanning bus 0 for devices..." and...nothing. That's it. Curtains!

This is all your fault, Intel. >=\
Posted in Uncategorized
Views 1812 Comments 2
« Prev     Main     Next »
Total Comments 2

Comments

  1. Old Comment
    Bit the bullet and picked up one of these:

    https://www.amazon.com/AmazonBasics-...70_&dpSrc=srch

    Shows up as:

    axen0 at uhub1 port 2 configuration 1 interface 0 "ASIX Elec. Corp. AX88179" rev 2.10/1.00 addr 4
    axen0: AX88179, address xx:xx:xx:xx:xx:xx
    rgephy0 at axen0 phy 3: RTL8169S/8110S/8211 PHY, rev. 5
    Posted 08-08-2018 at 10:52 PM by rocket357 rocket357 is offline
  2. Old Comment
    Ok, a bit of fudging stuff around and I think I have this figured out. The Raspberry Pi 3 B+ has the magic boot bits set to boot from usb0, however, I haven't been able to get the OpenBSD bootloader to load a kernel from an FFS filesystem at the boot> prompt if I boot from usb0 (mmc0 loads just fine, however).

    So I dd'd the latest miniroot63.fs to an sd card, then disklabel'd the sd card and deleted the 'a' partition. I edited the sd card with fdisk and grew out the OpenBSD partition to the full remainder of the sd card after the msdos partition. Once that was done, I disklabel -dE'd the sd card and created an 'a' partition that took up the entire OpenBSD area. Once that was done, I dd'd the first 4 MB of the miniroot back to the sd card, ftp'd the bsd* files for arm64 to the sd0a partition, and booted the pi up with my franken-sd.

    Now at the boot> prompt I can select any of the bsd* files I copied to the sd0a partition, so I obviously select the bsd.rd file, install to my external SATA drive. I reboot, catch the ddb error about the duid it can't find (and copy that to a safe location), then boot back up to bsd.rd, disklabel -E sd0 and update the duid ('i'), edit /etc/fstab to use the new duid, and...

    Then I cross my fingers and reboot!

    Success!

    NOTE: this approach basically disables any advantage you would get from kernel re-linking! And updating this franken-sd isn't going to be fun =\
    Posted 08-09-2018 at 11:47 AM by rocket357 rocket357 is offline
 

  



All times are GMT -5. The time now is 01:05 PM.

Main Menu
Advertisement
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration