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 | Type 'help' for help | Logs: -> irc.armbian.com
phenom has joined #armbian
<ArmbianTwitter> @seeteegee (Chris McGee): @LukaszErecinsk1 I've added a new section for low light in the wiki with the steps that I used with armbian. https://t.co/2aSf6SLXAx https://tinyurl.com/yjzkwbv9 (10s ago)
archetech has quit [Quit: Textual IRC Client: www.textualapp.com]
LanDi has quit [Remote host closed the connection]
<[TheBug]> yeah but 850% on probably .20 or something
<[TheBug]> still a lot but not like astonomical or anything
<[TheBug]> may have even been cheaper than that
<[TheBug]> but yeah
<[TheBug]> inflation is on it's way
<stipa> it'll be on all parts maybe
<stipa> why not
<stipa> inflation yeah, it stinks on it
monotux has quit [Remote host closed the connection]
monotux has joined #armbian
Guest36656 is now known as comrade
oida has quit [Ping timeout: 240 seconds]
oida has joined #armbian
kolla has quit [Quit: %fog relay%]
kolla has joined #armbian
attah has joined #armbian
caiortp has quit [Ping timeout: 252 seconds]
xtron has joined #armbian
marco44 has quit [Ping timeout: 240 seconds]
marco44 has joined #armbian
marco44 has quit [Quit: ZNC 1.8.2+deb2~bpo10+1 - https://znc.in]
marco44 has joined #armbian
<Werner> lanefu, could become complicated having a small form like r4s if considering an optional pcie breakout board...
rhagu has joined #armbian
<rhagu> Hi, I saw in ps that both journald and rsyslogd are running on my armbian bionic installation, can I remove one of them?
<lanefu> Werner: yeah makes sense. Is zero 2 formfactor larger than r4s?
<Werner> lanefu, from a quick look I'd say its even smaller
<lanefu> rhagu: you could try removing rsyslogd
<Werner> My most recent idea was to use ROC RK3399 from firefly as basis. PCIe adapter plugged on top and on the bottom where the SoC sits a massive backplate holds the sbc which in the same way acts as heatsink. Make things more expensive of course
<Werner> kind a like the station p1 housing which serves as heat sink
<lanefu> Yeah i like the soc on bottom boards a lot
<Werner> I actually dont but in this case it might be worth going into this direction
<lanefu> Since its xunlong i figure we need to stay within the domain of existing designs
<Werner> Sure but adjust existing ideas is easier than start from scratch
<lanefu> Fyi i got a 40x40 heatsink to fit on my.opi4
<Werner> 40x40? cover the memory?
<Werner> soc is only 20x20 or so
<kprasadvnsi[m]> Somebody said OPi zero 2
<kprasadvnsi[m]> Is there issue with form factor?
<lanefu> Werner: yep
<rhagu> lanefu thanks, any idea why there are two logging mechanisms?
<lanefu> rhagu: no. Does standard x86 ubuntu and debian not have rsyslog
<rhagu> lanefu: I dont know, maybe people at #ubuntu know a reason why, I will check
<Werner> something like this: https://snipboard.io/vHZlkg.jpg view from inside. Board sits with SoC facing down on this plate. Next step would be to make it possible to mount board to the backplate and then shove them together in the rack
<Werner> you cannot see in the shot but the opposing side is slotted for heat dissipation
<Werner> https://de.aliexpress.com/item/4000107291369.html heatsink for my R4S. The 20x20x11 model
xtron has quit [Ping timeout: 240 seconds]
rhagu has quit [Quit: Leaving]
LanDi has joined #armbian
<nekomancer[m]> Kupfer!!!
xtron has joined #armbian
<stipa> -- kupfer
<ArmbianHelper> copper [de~>eng]
<stipa> yeah, it's rare to see compper heatsinks in that format
<stipa> copper*
<stipa> is it maybe a new trend?
LanDi has quit [Read error: Connection reset by peer]
stipa_ has joined #armbian
stipa__ has joined #armbian
stipa has quit [Ping timeout: 240 seconds]
stipa__ is now known as stipa
stipa_ has quit [Ping timeout: 240 seconds]
sunshavi has quit [Ping timeout: 252 seconds]
stipa_ has joined #armbian
stipa has quit [Ping timeout: 240 seconds]
stipa_ is now known as stipa
stipa_ has joined #armbian
stipa has quit [Remote host closed the connection]
stipa_ is now known as stipa
stipa_ has joined #armbian
stipa has quit [Ping timeout: 240 seconds]
stipa_ is now known as stipa
archetech has joined #armbian
stipa has quit [Ping timeout: 240 seconds]
LanDi has joined #armbian
stipa has joined #armbian
LanDi has quit [Remote host closed the connection]
stipa has quit [Ping timeout: 240 seconds]
xtron has quit [Ping timeout: 268 seconds]
luxemboye has quit [Remote host closed the connection]
luxemboye has joined #armbian
stipa has joined #armbian
LanDi has joined #armbian
xtron has joined #armbian
nkuttler has quit [Quit: K-Lined]
nkuttler has joined #armbian
<stipa> my opi lite 2 does something strange, when usb to serial tries to connect to it it lowers the baudrate of its ttyS0 to 9600
<stipa> instead of it being 115200
<stipa> i connect from the other side with specifying baudrate of 115200 not 9600
<stipa> and i get blank screen on the other side with whatever serial terminal emulator i try, in rare occasions it works
<stipa> when it works it's with minicom and it sometims achieves to come to the login screen and it logis in but boot data is bunch of garbage
<stipa> so it connects to it using 9600 baud
<stipa> something that should syncronize baudrate is fucked
<stipa> somwehere
<stipa> i think this doesn't happen with putty on windows
<stipa> i never had that problems there
<stipa> root@orangepilite2:~# stty < /dev/ttyS0
<stipa> speed 9600 baud; line = 0;
<stipa> lnext = <undef>; discard = <undef>; min = 1; time = 0;
<stipa> -brkint -icrnl ixoff -imaxbel iutf8
<stipa> -icanon -iexten -echo
<stipa> i tried to set it manually with 'stty -F /dev/ttyS0 115200' but when client tries to connect to it it gets back to 9600 and client sees blank screen
<stipa> so when it works client is actually connected with 9600 baud and boot screen is bunch of junk data because it's spitting 15200 out i guess but it's connected with 9600
xtron has quit [Ping timeout: 265 seconds]
<stipa> when it arrives to login it can be clearly seen and all works after that, but the connection is at 9600
<stipa> so, i have to connect to it with 9600 baud but i'm not to see boot messages then
xtron has joined #armbian
<stipa> if i connect with 115200 baud to it and change buad of orange ttyS0 from 9600 to 115200 it sets it to 115200
<stipa> but as soon as i start to type stuff at the client side it jumps down to 9600
xtron has quit [Ping timeout: 246 seconds]
xtron has joined #armbian
attah has quit [Quit: badarg]
stipa has quit [Quit: WeeChat 2.8]
stipa has joined #armbian
<stipa> seems like ch34x for usb to serial is crappy for linux
<stipa> driver*
LanDi has quit [Remote host closed the connection]
xtron has quit [Ping timeout: 240 seconds]
<nekomancer[m]> or ch34x not genuine
luxemboye has quit [Ping timeout: 240 seconds]
luxemboye has joined #armbian
<stipa> it's from ebay
<stipa> i'm installing one more time and blocking ch341 that comes with the kernel
<stipa> that works even worse than ch34x driver
<stipa> yeah, missing stuff on the screen, typing and not seeing what's typed, typing but it doesn't type and that stuff
<stipa> ut's recoginzes as ch340
<stipa> it's recognized*
<stipa> the kernel gives it ch341
<stipa> if ch34x driver is not installed
<stipa> ch32x driver gives it ch430
<stipa> ch340 works better but it's still unusable
<stipa> ch34x *
<stipa> maybe it's just to fast for the driver 115200 rate
<stipa> that's more than 10x 9600
<stipa> could i maybe force my sbc to work at 9600 ?
<nekomancer[m]> you can try until you get other converter
huhuhu has joined #armbian
<stipa> after the system update it works better, maybe some things fell into place
<stipa> dunno
<stipa> but the driver is not the one shipped with the kernel
<stipa> it's the dkms thing called ch34x
<stipa> after the update something happened and converter is usable
<stipa> seems like it hasn't been armbian fault, sorry for the spam
<stipa> but i have no idea why arbian throtelled the speed of serial ttyS0 to 9600 naud
<stipa> in either case the problem was in the clients side driver