Werner changed the topic of #armbian to: armbian - Linux for ARM development boards | www.armbian.com | Github: github.com/armbian | Commits: #armbian-commits | Developer talk: #armbian-devel | Forum feed: #armbian-rss | Off-Topic: #armbian-offtopic | Logs: -> irc.armbian.com
mr_claus has quit [Quit: Leaving]
alekksander has quit [Quit: Konversation terminated!]
Toasty has quit []
archetech has quit [Quit: Konversation terminated!]
archetech has joined #armbian
norwich has quit [Ping timeout: 260 seconds]
norwich_ has joined #armbian
norwich_ is now known as norwich
archetech has quit [Quit: Leaving]
lemonzest has joined #armbian
on3pk has joined #armbian
<on3pk>
I'm trying to run a multipass container and I get the Vsock support is missing (no /dev/vsock) error message. Is this something that is board dependent?
<nekomancer[m]>
on3pk: maybe. check kernel configuration for `CONFIG_VSOCKETS` parameter. and tell board name.
<on3pk>
it's a libre computer aml-s905x
<on3pk>
CONFIG_VSOCKETS=m
<on3pk>
CONFIG_VSOCKETS_DIAG=m
<on3pk>
CONFIG_VSOCKETS_LOOPBACK=m
<on3pk>
but I have no idea what any of that means
<nekomancer[m]>
it means kernel kontains support of /dev/vsock. and it should work.
<on3pk>
when I use modprobe I get modprobe: FATAL: Module vhost_vsock not found in directory /lib/modules/6.0.13-meson64
<on3pk>
so is there a module package that needs to get installed?
<nekomancer[m]>
it should be.
<on3pk>
should be already installed or should be installed?
<on3pk>
or should need to be installed I mean
<nekomancer[m]>
file name possible differs...
<nekomancer[m]>
like vsock.ko.xz
<nekomancer[m]>
but it should be on your system already in case your kerbel config contain strings you posted
<nekomancer[m]>
try just sudo modprobe vsock
<on3pk>
I didn't get any output from the modprobe, but I still get the error (Failed creating instance record: Instance type "virtual-machine" is not supported on this server: Vsock support is missing (no /dev/vsock) from multipass
<nekomancer[m]>
look with ls and eyes if /dev/vsock file is present after you did modprobe.
* nekomancer[m]
just do modprobe and got that file
<on3pk>
hm yes, it did show up
* nekomancer[m]
* just did modprobe and got that file
<on3pk>
without having access to vsock, is there a different way to run virtualized containers?
lyri has quit [Remote host closed the connection]
gp5st has joined #armbian
kolla has quit [Quit: %fog relay%]
kolla has joined #armbian
kolla has quit [Remote host closed the connection]
kolla has joined #armbian
gp5st has quit [Ping timeout: 272 seconds]
Laskolnyk has joined #armbian
chewitt has joined #armbian
Laskolnyk has quit [Quit: leaving]
nickodd has quit [Ping timeout: 256 seconds]
popolon has joined #armbian
popolon has quit [Remote host closed the connection]
popolon has joined #armbian
alekksander has joined #armbian
qqqhhh8619935 has joined #armbian
qqqhhh861993 has quit [Ping timeout: 264 seconds]
qqqhhh8619935 is now known as qqqhhh861993
Laskolnyk has joined #armbian
nickodd has joined #armbian
<Armbian-Discord>
<Heisath> On my newly required RockPro64 I added a PCIe to SATA adapter and ssd. Now trying to boot from SPI+SATA via armbian-config.
<Armbian-Discord>
<Heisath> Setting it up via "install -> uboot-spi | root sata" seems to have put the correct stuff at the right location. But uboot does not load the kernel.
<Armbian-Discord>
<Heisath> I think uboot is missing configuration to use pcie-sata ssd. Although the pci submodules recognizes it.
<Armbian-Discord>
<rpardini> hmm, I wish you a happy defconfig patching session.
<Armbian-Discord>
<rpardini> (armbian-next will one day allow for UBOOT_CONFIGURE=yes too)
archetech has joined #armbian
<Armbian-Discord>
<rpardini> also, having shot myself in the foot more than once, I'd say avoid deploying to SPI before testing it on SD/eMMC
<Armbian-Discord>
<Tonymac32> sim
on3pk has quit [Quit: Client closed]
arch3r has quit [Quit: bye]
chewitt has quit [Quit: Zzz..]
arch3r has joined #armbian
popolon has quit [Ping timeout: 252 seconds]
<Armbian-Discord>
<Jason123> Does the h3 need a heatsink?
<Armbian-Discord>
<ManoftheSea> no scuzzy at all?
gp5st has joined #armbian
<Armbian-Discord>
<c0rnelius> Does the H3 need a heat sink? Depends what ur doing with it. Wouldn't hurt though. But like the H5 they tend to run pretty warm.
<Armbian-Discord>
<Jason123> Then I need to get the seller to give a refund or something the seller did not give me one for the cpu
<Armbian-Discord>
<Jason123> Only for the ram
<Armbian-Discord>
<c0rnelius> here are two I have running that are basically idle. one is at 59°C and the other 49°C.
<Armbian-Discord>
<Jason123> The seller did not send me everything
<Armbian-Discord>
<c0rnelius> what board is it?
<Armbian-Discord>
<c0rnelius> Like my orangepi h3's tend to run warmer than my friendlyarm ones. I find it depends on the vendor if a heat sink is really needed.
<Armbian-Discord>
<c0rnelius> well and form factor
<gp5st>
RichN: Yeah, new SD card solved the problem
popolon has joined #armbian
alekksander has quit [Read error: Connection reset by peer]
alekksander has joined #armbian
<Armbian-Discord>
<Jason123> Orange pi zero
lemonzest has quit [Quit: WeeChat 3.6]
gp5st has quit [Ping timeout: 252 seconds]
pablocastellanos has quit [Ping timeout: 248 seconds]
pablocastellanos has joined #armbian
arch3r has quit [Ping timeout: 260 seconds]
arch3r has joined #armbian
PhotoJim has joined #armbian
<PhotoJim>
I have a broken kernel upgrade on a NanoPi Neo4 board. Has a removable eMMC card. Finally got an adapter so I can read the eMMC card on another system. uboot seems fine. trying to figure out the best way to rescue the system without a reinstall.
<PhotoJim>
I have a backup (files only, not image) with a previous kernel. Ideally, though, I'd like to chroot into it but I'd either need a virtual environment that can emulate rockchip64, or to use an existing ARM system that could chroot to it. Ideas?
<PhotoJim>
(I imagine a later update fixed the problem.)
<Armbian-Discord>
<IgorPec> We don't have maintainer for Neo4, nor HW in the test lab. We don't know what is the status.
<PhotoJim>
I know it's not officially supported, but updates still work and there have been kernel upgrades, so someone must have been updating it (at least as of late October).
<Armbian-Discord>
<IgorPec> kernel is common for all rockchip devices
<PhotoJim>
ahh, okay
<Armbian-Discord>
<IgorPec> someone = unknown person from the internet
<Armbian-Discord>
<IgorPec> mainstream support is random, it usually fail at updates ... keeping those devices operatinal is very timely
<PhotoJim>
are there any non-rockchip64 ARM CPUs that you could use to chroot to such an image? Or virtual/emulated environments?