brook has quit [Remote host closed the connection]
brook has joined #beagle
brook has quit [Remote host closed the connection]
brook has joined #beagle
starblue has quit [Ping timeout: 246 seconds]
starblue has joined #beagle
Shadyman has joined #beagle
vagrantc has quit [Quit: leaving]
<zmatt>
jkridner: hmm, git.beagleboard.org doesn't allow sign in using a GitHub/GitLab.com account (despite the login page offering that) and creating a normal account requires approval... that doesn't make reporting issues very convenient
<zmatt>
have I really not previously created an account there at some point? I guess not
<zmatt>
the error you get when attempting to login/register using a GitLab.com account is supremely confusing btw... "Signing in using your GitLab.com account without a pre-existing GitLab account is not allowed. Create a GitLab account first, and then connect it to your GitLab.com account"
<zmatt>
it took me a bit to realize that with "GitLab" (without .com) it's referring to git.beagleboard.org, I wonder if you can customize that string somewhere so it says "git.beagleboard.org account" instead of "GitLab account"
MrigankP has joined #beagle
MrigankP has quit [Client Quit]
MrigankP has joined #beagle
MrigankP has quit [Client Quit]
MrigankP has joined #beagle
MrigankP has quit [Ping timeout: 260 seconds]
brook has quit [Read error: Connection reset by peer]
brook has joined #beagle
brook has quit [Remote host closed the connection]
brook has joined #beagle
buzzmarshall has quit [Quit: Konversation terminated!]
brook has quit [Ping timeout: 268 seconds]
mattb0ne has quit [Ping timeout: 255 seconds]
Guest58 has joined #beagle
Guest58 has quit [Client Quit]
brook has joined #beagle
mattb0ne has joined #beagle
<zmatt>
jkridner: also, yikes... the schematic for a DP++-to-HDMI/DVI adapter in the spec (VESA DisplayPort Interoperability Guideline 1.1) shows HPD connected directly to the HDMI/DVI port, which would cause it to be strongly pulled up to 5V by the display, and HPD connects directly to a GPIO on the BBAI-64
<zmatt>
fortunately in reality every DP++-to-HDMI/DVI chip I've found does in fact perform level shifting on HPD
starblue has quit [Ping timeout: 255 seconds]
ikarso has joined #beagle
<zmatt>
but it's disconcerting that a spec-compliant adapter may just dump 5V onto HPD (even though the DisplayPort spec gives a max voltage of 3.6V)
brook has quit [Ping timeout: 248 seconds]
<set_>
dang.
Shadyman has quit [Ping timeout: 276 seconds]
<set_>
I tried the R5F .elf files. I got busted or it worked. No way to tell...
<set_>
Building my own image now for the AI-64. Not sure if I will bust the current image or make sweet piglets out of jello molds.
<set_>
Wish me luck!
<set_>
I was able to get LinuxCNC on it! But...
<set_>
You know...
<set_>
W/out a RT kernel, LinuxCNC is sort of bust.
<set_>
The arm64 port works but puttin' it on the AI-64 is work. Where to start?
Shadyman has joined #beagle
mattb0ne has quit [Ping timeout: 268 seconds]
Stat_headcrabed has joined #beagle
rob_w has joined #beagle
Stat_headcrabed has quit [Quit: Stat_headcrabed]
insurgent_ has joined #beagle
dinuxbg_ has joined #beagle
insurgent has quit [*.net *.split]
bryanb has quit [*.net *.split]
mvaittin has quit [*.net *.split]
dinuxbg has quit [*.net *.split]
Parduz has joined #beagle
<Parduz>
my journal is full of errors from the bb-wl18xx service, and i don't know what's the problem:
<Parduz>
Mar 28 10:31:24 beaglebone systemd[1]: bb-wl18xx-wlan0.service: Control process exited, code=killed, status=15/TERM
<Parduz>
Mar 28 10:31:24 beaglebone systemd[1]: bb-wl18xx-wlan0.service: Failed with result 'timeout'.
<Parduz>
Mar 28 10:31:24 beaglebone systemd[1]: Failed to start BB WL18xx wlan0 Service.
<Parduz>
Mar 28 10:31:30 beaglebone systemd[1]: bb-wl18xx-wlan0.service: Service RestartSec=5s expired, scheduling restart.
<Parduz>
Mar 28 10:31:30 beaglebone systemd[1]: bb-wl18xx-wlan0.service: Scheduled restart job, restart counter is at 41.
<Parduz>
this cycle of messages goes forever.
<zmatt>
Parduz: please don't spam multi-line output into chat, use a paste service like pastebin if you want to share text snippets such as logs
<Parduz>
and i'm TTYing using the BBB wifi.
<Parduz>
zmatt sorry: i thought it was small enough to be acceptable. Sorry
<zmatt>
other than hard to say from this, evidently the service is hanging which causes systemd to kill it but I'm not familiar with the service or what it might be doing
<Parduz>
how can i disable it permanently?
<zmatt>
if you think that's a good idea, sudo systemctl disable --now bb-wl18xx-wlan0.service
<zmatt>
("disable --now" is shorthand for disable and then stop)
<Parduz>
ok, i try it now
<Parduz>
great.
<Parduz>
dunno what it does, seems i don't need it.
<Parduz>
another question:
<Parduz>
i have a fstab line that to automount /dev/sda1 on /media/usb. Yesterday my BBB ceased to automount the USB. I don't see any error in the journal (that's why i sumbeld on the bb-wl19 service) and if i mount it with "mount" it works.
<Parduz>
what should i look at?
<zmatt>
uhh, what exactly do you have in the fstab?
<zmatt>
like, fstab doesn't have functionality to automount, depending on what you mean by that
<zmatt>
fstab doesn't mount a device in response to that device appearing
<Parduz>
i can't paste the line here?
<Parduz>
"/dev/sda1 /media/usb auto user,uid=1000,gid=1000,fmask=0137,dmask=0027,noauto 0 0"
<Parduz>
ok
<zmatt>
yeah that's just a normal fstab line that allows user 1000 to mount the filesystem
<Parduz>
well, it was all i need to have it auto-mounted. (if i'm not forgetting somthing)
<zmatt>
I vaguely recall you were using usb to do backups? based on that fstab line I would assume whatever program that does the backup also mounts it before and unmounts after?
<Parduz>
i do read or write there, yes. but it is not my program that mounts it
<Parduz>
uh .... wait.
<zmatt>
well it probably should... that would be the sensible place to do it
<Parduz>
i MAY have gor a brainfart.... i'll be back in 15 minutes :|
mvaittin has joined #beagle
bryanb has joined #beagle
mattb0ne has joined #beagle
shoragan[m] has quit [Ping timeout: 246 seconds]
mvaittin has quit [Ping timeout: 248 seconds]
siddh has quit [Ping timeout: 246 seconds]
tomba has quit [Ping timeout: 248 seconds]
static_rocket has quit [Ping timeout: 264 seconds]
<Parduz>
yes, i'm dumb :|
<Parduz>
it was my app that was mounting it.
<Parduz>
This what happens when you stop developing for a year and then go back to it
florian_kc has joined #beagle
mattb0ne has quit [Ping timeout: 250 seconds]
set_ has quit [Ping timeout: 264 seconds]
set_ has joined #beagle
<Parduz>
New question:
<Parduz>
how can i fully disable Bluetooth?
<Parduz>
i've used connmanctl disable bluetooth but there's still kernel errors like:
<zmatt>
properly disabling is probably best done via DT, but I guess you could also just blacklist the kernel driver provided it's compiled as module (rather than built into the kernel)
<Parduz>
how to do it?
static_rocket has joined #beagle
ft has quit [Quit: leaving]
<zmatt>
actually the first thing to try is just disabling it using rfkill
<zmatt>
but I guess that may not be enough
<zmatt>
I do wonder what's up with those messages
<zmatt>
i.e. "rfkill block bluetooth" ... systemd should save that setting on shutdown/reboot and restore it on boot
<Parduz>
rfkill list says Bluetooth is soft blocked but not hard blocked
<Parduz>
i try and see.
<zmatt>
yeah hard-blocked means blocked using a physical switch, and there's obviously isn't any
<Parduz>
oh ... so it should be already blocked without need to try, right?
<zmatt>
oh if it's already soft-blocked then yeah that's all you can do with rfkill
<zmatt>
I guess the problem isn't that you want bluetooth disabled, since it already is, but that the kernel driver is for some reason have loud problems and you want it to shut up
<zmatt>
just to check, what board are you using?
<Parduz>
beaglebone black wireless
<zmatt>
just to verify, can you do: ls /proc/device-tree/chosen/overlays/
<Parduz>
BB-ADC-00A0.bb.org-overlays BB-BBBW-WL1835-00A0.bb.org-overlays BB-BONE-eMMC1-01-00A0.bb.org-overlays BB-BONE-LCD4-PHASE-002 BB-UART2-00A0 name
static_rocket has quit [Quit: Bridge terminating on SIGTERM]
<Parduz>
the "PHASE" one is my own LCD board and keyboard.
<zmatt>
do you have bb-wl18xx-bluetooth.service disabled?
<Parduz>
yup
shoragan[m] has joined #beagle
<zmatt>
ah that's probably causing those errors, because it is responsible for asserting the bluetooth-enable signal without which the kernel driver is failing
mvaittin has joined #beagle
tomba has joined #beagle
static_rocket has joined #beagle
siddh has joined #beagle
<zmatt>
this is actually kinda weird, they're exporting the gpio for manual control (bizarrely using gpio-leds) but it's also declared as enable-gpios on the bluetooth node, which is clearly a conflict
<zmatt>
regardless, you could try putting in your custom overlay: &uart3 { bluetooth { status = "disabled"; }; };
<Parduz>
ok, i'll try right now.
<set_>
I done thought it, made it come true, and then broke it. Blah.
<set_>
Thank you, thank you, thank you. Now, time to gather the dust.
shoragan[m] has quit [Ping timeout: 246 seconds]
static_rocket has quit [Ping timeout: 265 seconds]
siddh has quit [Ping timeout: 265 seconds]
tomba has quit [Ping timeout: 265 seconds]
mvaittin has quit [Ping timeout: 265 seconds]
siddh has joined #beagle
shoragan[m] has joined #beagle
<set_>
Whelp, I broke the fan somehow.
<set_>
What would make the USB Fan not spin on the BBAI-64? Loss of power?
<zmatt>
set_: why the fuck are you removing regulatory databases?
<zmatt>
those are necessary for wifi
<zmatt>
even if you're not using wifi, why the hell are you removing system files?
<set_>
I had an issue w/ them while porting kernel 6.2.x.
<set_>
But...I found that there are already kernels for it. I already removed the files before finding so-said kernels.
<zmatt>
"issues" wtf are you talking about and how did you conclude that removing these databases was a good idea?
<zmatt>
to fix the damage, sudo apt reinstall wireless-regdb
<set_>
Those files were showing in the output of my build as not available.
<set_>
So, I made them not available to make it correct.
<zmatt>
????
<set_>
I know. Too odd!
<zmatt>
wtf are you talking about
<set_>
Okay...
<zmatt>
these files are not part of the kernel
<set_>
oh.
<set_>
Hmm.
<set_>
I installed wireless-regdb.
<set_>
I then built the kernel on the BBAI-64 to test its capabilities.
<set_>
I got a make error at regulatory.db each and every build.
<zmatt>
pastebin
<set_>
I got tired of trying on the BBAI-64...this was hours ago. I already erased everything and built on a debian machine x86_64.
<set_>
I got lucky. Sheesh.
<set_>
For a bit, I thought I ruined the chip. That would have ruined my week.
Guest58 has joined #beagle
mrigank has joined #beagle
<mrigank>
Hi, sorry for asking here a second time. I lost previous chats because it's my first time using IRC. I want to request @wmat to approve my request to join eLinux. This is regarding GSoC.
<zmatt>
though I don't see any previous conversation here containing your name or wmat this year... you sure you're in the right channel? I think there should also be a channel specifically for gsoc stuff