DS Justice

  • Content Count

  • Joined

  • Last visited

About DS Justice

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. As described here for kernel 4.18.6, the bcache module doesn't build when installing bcache tools. The bcache-tools package has a /usr/lib/initcpio/install/bcache file, which suggests the use of mkinitcpio... but I don't know enough about module compilation to know whether the bug is in armbian or this package. Would appreciate guidance on where I should direct this report.
  2. Yes, well past that. Reinstalled, reconfigured, the works. I have: $ lsinitramfs /boot/initrd.img-4.18.6-mvebu64 | grep bcache lib/udev/probe-bcache lib/udev/bcache-register lib/udev/rules.d/69-bcache.rules A working system would have an element under lib/modules as well.
  3. I just pulled my espressobin back out of the box, re-imaged with 4.18.6-nvebu64, and sparked it up. Nearly everything just works, I'm so impressed! The only problem I'm having is that the bcache tools doesn't seem to be providing a kernel module -- at least, none is present anywhere I can find, particularly in the initramfs. Any suggestions?
  4. I had similar repeated crashes after switching to Armbian (171106) from the Espressobin Ubuntu. It seemed to stabilize after I added `mw.l 0xd0011500 0x78e3ffff;` into my bootcmd. Full environment linked here. I really don't know what that *does*, I found it on a forum, someone suggested that it would disable the frequency governer, which they asserted was the source of *their* crashes. Good luck.
  5. So I guess I'm one of today's 10,000. Lucky me! And thanks.
  6. Fair enough. I guess I've been grumpy about systemd long enough, time to figure out what it is. Thanks for the nudge.
  7. The espressobin has three ethernet ports. In Ubuntu Armbian, left to right (looking into the ports), they're called "lan1", "lan0", and "wan". The weird thing is that you can't bring them up until you've *first* brought up eth0, which is not associated with a physical port. This causes all kinds of havoc trying to use /etc/network/interfaces/, because it takes a couple of seconds for eth0 to come up, in which time the other interfaces have already failed. 1) What is this mysterious eth0? 2) My attempts to bridge lan0 and lan1 from .../interfaces have failed. Got an example you can give me?