Werner changed the topic of #armbian to: armbian - Linux for ARM development boards | www.armbian.com | Github: github.com/armbian | Commits: #armbian-commits | Forums Feed: #armbian-rss | This channel is logged -> irc.armbian.com
lids has quit [Ping timeout: 246 seconds]
lids has joined #armbian
macc24 has joined #armbian
macc24 has quit [Remote host closed the connection]
macc24 has joined #armbian
macc24 has quit [Ping timeout: 256 seconds]
dddddd has quit [Ping timeout: 256 seconds]
sunshavi has quit [Ping timeout: 258 seconds]
<lanefu>
man i'm behind on armbianland.. whats new?
<Tonymac32>
Howdy lanefu
buZz has quit [Remote host closed the connection]
patrixl has joined #armbian
sunshavi has joined #armbian
<archetech>
o/
Tonymac32 has quit [Read error: Connection reset by peer]
Tonymac32 has joined #armbian
<patrixl>
heya
<patrixl>
soo all this time I was avoiding KDE Plasma cuz I thought it was slow like GNOME, turns out it performs really well on a rk3399, albeit with the compositor disabled (evne with compositor it wasn't bad)
drobo_00 has quit [Ping timeout: 258 seconds]
xec has joined #armbian
xecuter has quit [Ping timeout: 246 seconds]
chewitt has quit [Quit: Zzz..]
chewitt has joined #armbian
_whitelogger has joined #armbian
_whitelogger has joined #armbian
<Werner>
Good morning.
<ArmbianTwitter>
@DieZuckerbude (Ben Zucker 🍰): This is a really cool one of you like to build your own router or hardware firewall from scratch. https://t.co/7NoUEy90cz (9s ago)
mpmc is now known as noslots
archetech has quit [Quit: Konversation terminated!]
noslots is now known as mpmc
mpmc is now known as stay_home_or_els
stay_home_or_els is now known as stay_home
Saurabh009 has joined #armbian
<Saurabh009>
Hi, does anyone know how to QEMU a armbian image? Since everything is closed and my board got damaged, I am thinking of this only.
<Saurabh009>
Or share a link with me. ^^
<solderfumes>
Hi Saurabh009
<Saurabh009>
Hello solderfumes
<solderfumes>
The static QEMU binary is part of the Armbian installation
<solderfumes>
So on your x86 linux machine, you can mount the imate, and `chroot /mount/point`, and you'll get bash in the emulator
<solderfumes>
*image
<Saurabh009>
Oh thank you, thats something new. Are there any defined steps where I can do this? I am a newbie and trying to learn so do not know much how to do it.
<solderfumes>
Do you need help with mounting the image?
<Werner>
If it is not really necessary to chroot into the image you can always easily mount the filesystems of the sd card in any Linux based OS.
<Saurabh009>
I meant that the emulator turns up and it shows a virtual image of the armbian which I was running on the board. And do my compilations there. Sorry I googled about this on yourtube it showed me QEMU launching emulator thing.
<Saurabh009>
My image is armbian for ornage pi
<Saurabh009>
OrangePi PC
<solderfumes>
Saurabh009: you're going to have to tell us what you want your goal is
<solderfumes>
you might not need QEMU at all, as Werner said
<Werner>
Saurabh009, you stated "and my board got damaged". The easiest way of determine if there is a hardware defect simply grab a fresh image and boot from it.
<Saurabh009>
I was using the armbian image to do code compile and other development stuffs. Since board is gone now, I read somewhere by QEMU you can emulate a arm image.(Actually someone told me this).
<Saurabh009>
I checked it , new image isn't booting too.
<Saurabh009>
So I do not need Qemu for this ?
<Werner>
I see. Well for simply recovering your data mount will suffice.
stay_home is now known as stayhome
<Saurabh009>
Yeah data will be recovered by mounting. But can I emulate a new armbian image like what QEMU videos shows and download binaries there and do compilations ?
<Werner>
No idea TBH
<Saurabh009>
Oh, Ok, thank you for the info. I need to do more google then. If anyone knows about this, please let me know. ^^
<solderfumes>
1: `losetup` to point a loopback block device to the image file
<solderfumes>
2: `partprobe` to update the in-memory partition table
<solderfumes>
3: `mount` the partition
<Saurabh009>
losetup is like kpartx right ?
<Saurabh009>
I will try your steps now.
<solderfumes>
`losetup`, as used here will set up `/dev/loopN` to be a device that's served by the image file. kpartx edits partitions afaik
<solderfumes>
so no
<Saurabh009>
Oh, Ok, something new I learned.
<solderfumes>
IMO it's easier to use a loopback device, but you could use the `mount -o offset` option of mount to point it the partition, if you have the byte offset
<Saurabh009>
I will check this too
selfbg has joined #armbian
macc24 has joined #armbian
<ArmbianTwitter>
@armbian (armbian): @RoganDawes @LucaBongiorni @cnxsoft @FriendlyARM_ @POTAEbox Proper software support is already there https://t.co/51QwY8KpWk (3s ago)
<IgorPec>
good morning
wi has quit []
wi has joined #armbian
Saurabh009 has quit [Quit: Leaving]
<ArmbianTwitter>
@RoganDawes (Rogan Dawes): @armbian @LucaBongiorni @cnxsoft @FriendlyARM_ @POTAEbox And the R1S? (21s ago)
<ArmbianTwitter>
@armbian (armbian): @RoganDawes @LucaBongiorni @cnxsoft @FriendlyARM_ @POTAEbox For R1 we do have support while S model only have a different wireless https://t.co/q88Wl5ExxT which means it should work by adjusting DT. Also a model with H5 chip might get an image https://t.co/m4aIO2yKV1 (9s ago)
<patrixl>
well
<patrixl>
that is a new bot , or I've been away too long and don't remember
<IgorPec>
yes, its forwarding @armbian #armbian twitter activity
<IgorPec>
1-2 weeks in operation
buZz has joined #armbian
buZz is now known as Guest45388
Guest45388 has quit [Changing host]
Guest45388 has joined #armbian
Guest45388 is now known as buZz
wi has quit []
wi has joined #armbian
wi has quit []
wi has joined #armbian
IgorPec has quit [Remote host closed the connection]
IgorPec has joined #armbian
IgorPec has quit [Changing host]
IgorPec has joined #armbian
dddddd has joined #armbian
<lanefu>
good morning
sassinak-work has quit [Remote host closed the connection]
sassinak-work has joined #armbian
<ArmbianTwitter>
@RoganDawes (Rogan Dawes): @armbian @LucaBongiorni @cnxsoft @FriendlyARM_ @POTAEbox I tried using the Orange Pi R1 image, which surprisingly had a working WiFi adapter, but failed to detect carrier on the main ethernet (WAN) connection. The USB ethernet interface did work, although it does not have a consistent MAC address, I assume as a result of uboot vars. (11s ago)
<ArmbianTwitter>
@RoganDawes (Rogan Dawes): @armbian @LucaBongiorni @cnxsoft @FriendlyARM_ @POTAEbox However, trying to run my own WiFi configuration triggered a kernel oops that knocked all local WiFi devices off whatever AP they were connected to, including disconnecting my iPhone from a Unifi AC-AP, and causing an ESP8266 to start its own AP. Maybe it oopsed at full TX pwr? (10s ago)
<IgorPec>
morning Lanefu
drobo_00 has joined #armbian
drobo_01 has joined #armbian
drobo_00 has quit [Ping timeout: 260 seconds]
drobo_01 is now known as drobo_00
<ArmbianTwitter>
@armbian (armbian): @RoganDawes @LucaBongiorni @cnxsoft @FriendlyARM_ @POTAEbox Twitter is not an ideal place for R&D or debug. Especially not for hardware we don't support. If you want to bring this board up, join forums https://t.co/vfCUbGZAPC or H3 / H5 forums. Its should not be difficult (except WiFi might be more troublesome) ... (21s ago)
selfbg has quit [Ping timeout: 258 seconds]
wi has quit []
wi has joined #armbian
maccraft has joined #armbian
macc24 has quit [Ping timeout: 264 seconds]
maccraft is now known as macc24
DaRock has quit [Ping timeout: 240 seconds]
archetech has joined #armbian
sunshavi has quit [Ping timeout: 264 seconds]
sunshavi has joined #armbian
wi has quit []
wi has joined #armbian
t4h4[m] has quit [Ping timeout: 240 seconds]
macc24 has quit [Ping timeout: 256 seconds]
macc24 has joined #armbian
t4h4[m] has joined #armbian
macc24 has quit [Ping timeout: 240 seconds]
drobo_00 has quit [Quit: drobo_00]
macc24 has joined #armbian
<IgorPec>
steev:
<steev>
me:
<steev>
IgorPec: btw, even though it's packaged for arm64, it seems like there's some arm build cruft in the sources (arch/arm/boot/Image and friends)
<IgorPec>
how are those monitor mode patches organised?
<steev>
there's just the 1
<IgorPec>
maintained? can you point me to proven ?
<steev>
i don't think we have the history back to 4.4 (or older) though i have them in my build scripts, but i'd have to go through them again to see just what's needed for the older kernels
<IgorPec>
4.4 4.14 and 4.19 are still used ...
<steev>
si, 4.14 and 4.19 are in there
<steev>
i only try to patch vendor kernels, i don't try to maintain multiple kernels like you guys do, since it's just me
<IgorPec>
yes, well, if patches exists, they can be added for older kernels. I will add this for current
<IgorPec>
but its not that important to adjust patches for older kernels
<IgorPec>
most of board can run 5.4.y which is recommended
<steev>
some older kernels used to have an issue with the channel reporting as -1, but i can't recall which kernel version fixed it
<ArmbianTwitter>
@noncollared (./noncollared.sh): RT @armbian: @system76 Home office / lab in action. https://t.co/dB1Y0JbEFX (17s ago)
<IgorPec>
steev: so i just left out the others?
<steev>
for the 4.4 kernels, si, that's the only patch needed for injection
<steev>
i wouldn't yank out the rtl88xxxx drivers, if that's what you're meaning
<IgorPec>
yeah
<steev>
those are different, these affect all the in-kernel drivers - even though the rtlxxxx are patched in, they're still not mac80211 drivers
<steev>
this will *not* enable it for the ampak... i've been debating sitting down some weekend and actually digging in to getting nexmon working with them
<steev>
but they've never documented it, so everyone has to stumble through it
<IgorPec>
so this will not affect most used AP62xx ?
<steev>
correct, it's for all the others, like people using an ath9k, and various other mac80211 devices
<IgorPec>
yes. but i saw somewhere patches also for those IIrC
<steev>
at some point, i'll grab up all the ap62xx firmwares and start poking at nexmon
<steev>
i haven't seen them at all :(
<steev>
if you can find them in your history/backlog, i'd *love* to see
<IgorPec>
not really sure. but isn't rpi using one of those?
<steev>
similar yeah, but different firmware
drobo_00 has quit [Quit: drobo_00]
<IgorPec>
aha, damn
<IgorPec>
then it was that what i saw
<steev>
yeah, we patch the brcmfmac driver... but it requires firmware modifications too, and since they're all a wee bit different... the firmwares have to be patched individually
<IgorPec>
patches are not applying fine at 4.4 and 4.19 ... eh, i will not bother with fixing them