**** BEGIN LOGGING AT Sat Mar 02 02:59:57 2019 Mar 02 16:01:39 Error not seen before. On the hdmi display during installation of bone-debian-9.5-lxqt-armhf-2018-10-07-4gb.img the screen picture moves to far to the left. It is not centered correctly. After flashing and turning on the beaglebone black revision c the desktop gui does not show. Mar 02 16:15:39 there are people who actually use the lxqt image voluntarily? :D Mar 02 16:16:01 not sure what you mean with not centered correctly, what do you expect to be centered and why? Mar 02 16:17:10 no idea about the desktop gui not showing up... maybe the 2018-10-07 lxqt image is broken but nobody noticed until now? :D Mar 02 16:19:23 I was wrong about the desktop gui not displaying. It does. On the display the gui is to far to the left. And to far down. You almost cannot see the tast bar. Mar 02 16:19:26 I use it, but never used the GUI Mar 02 16:19:59 flj: do you have it connected to a monitor or to a tv? Mar 02 16:20:17 because this sounds like an overscan issue Mar 02 16:20:21 a tv hdmi. Mar 02 16:20:41 The error has not shown before. Mar 02 16:20:54 yeah, it's due to your tv. usually there's a way to configure it to fix it. check for a way to classify an input as being from a PC Mar 02 16:21:28 well I don't know what to say, it sounds exactly like a classic issue with using a TV as computer monitor that has existed since the dawn of time Mar 02 16:22:23 like, on my samsung TV there's an option to change the "name" of an input from a list of options. if I select "PC" from that list of options, the problem is fixed Mar 02 16:23:13 (and this is not just with the beaglebone, also when connecting any other computer to it) Mar 02 16:23:25 maybe the issue you're having is a different one, but in that case I have no idea Mar 02 16:26:05 I was able to open monitor settings. In monitor settings it says 1920 x 1080. There is no other resolution to select. Mar 02 16:26:38 But the hdmi tv is 1280 x720. Mar 02 16:26:56 how can I set another resolution? Mar 02 16:27:00 it must advertise 1920x1080 Mar 02 16:28:05 if the xorg-video-modesetting driver is used I think xrandr should be able to select the resolution, otherwise use /boot/uEnv.txt to select the resolution using the video parameter Mar 02 16:29:12 if I open the file in question on my computer, will you say instructions? Mar 02 16:30:22 Or can I start xrandr on the bbb? Mar 02 16:31:17 just find the "cmdline=coherent_pool=1M net.ifnames=0 quiet" line and append " video=HDMI-A-1:1280x720" Mar 02 16:32:26 monitor settings sounds like a gui wrapper for xrandr, so presumably that's not working Mar 02 16:32:43 (which probably means the fbdev driver is used rather than modesetting) Mar 02 16:39:28 I installed on the emmc. Therefore I have to edit on the sd card. Then reflash. Mar 02 16:39:42 uhh, just edit the file on emmc? Mar 02 16:40:43 Then I have to connect the bbb to the computer? Mar 02 16:40:49 if you log in via ssh (via ethernet or usb networking) you can use "sudo nano /boot/uEnv.txt" to edit the file Mar 02 16:42:04 yes, which is how the bbb is typically used (see also the getting-started guide) Mar 02 16:42:14 I connect the bbb with an usb cable? Then how do I ssh log in? Mar 02 16:42:43 ssh debian@beaglebone.local Mar 02 16:43:18 do I use the small usb port? Mar 02 16:44:06 yes? that's why the bbb ships with a mini-usb cable Mar 02 16:44:35 mine did not. Mar 02 16:45:31 that sounds really strange, where did you buy it? Mar 02 16:45:52 bought it from a private seller. Mar 02 16:46:06 I found a correct usb cable. Mar 02 16:46:19 oh it's a second-hand beaglebone and the seller didn't bother giving you the original cable that came with it... rude Mar 02 16:47:11 I got the cable. If he could use his, it is fine. Mar 02 16:47:26 I connected the bbb. Mar 02 16:49:12 command ssh debian@beaglebone.local results in ssh: Could not resolve hostname beaglebone.local: Name or service not known Mar 02 16:50:12 odd, it should be resolvable via mDNS (once the beaglebone has properly booted up) Mar 02 16:50:22 check the table here: http://beagleboard.org/getting-started#step2 Mar 02 16:50:48 one or more of the "Status" fields in that table should change to "Active" Mar 02 16:50:56 ssh was not installed. Are there other packages I should install on the host computer? Mar 02 16:51:14 ssh was not installed? o.O what distro are you using? Mar 02 16:51:25 debian 9 Mar 02 16:52:24 libnss-mdns is required to resolve .local names. without that you'd need to specify the IP address instead, e.g. ssh debian@192.168.6.2 Mar 02 16:53:15 also maybe confirm using "ip addr" that the usb network interface has showed up and has an IP address Mar 02 16:53:27 libnss-mdns was installed. Mar 02 16:56:13 normally on linux, the beaglebone will show up as two network interfaces (one using RNDIS, one using CDC-ECM), and typically your network manager will bring both of them up (the first will receive ip 192.168.7.1, the second 192.168.6.1) Mar 02 16:57:12 the beaglebone has ip 192.168.7.2 and 192.168.6.2 via those interfaces respectively Mar 02 16:57:36 though if those work, beaglebone.local also ought to work Mar 02 16:57:57 brb, need to make some food Mar 02 17:00:06 no ip addr does not display 192.168.7.2 or 192.168.6.2 Mar 02 17:01:30 ssh debian@beaglebone.local does not work either. ssh: Could not resolve hostname beaglebone.local: Name or service not known Mar 02 17:06:12 please show what it does show flj Mar 02 17:06:13 on a pastebin Mar 02 17:06:21 the interfaces were not brought up maybe Mar 02 17:06:25 you can do it manually Mar 02 17:06:32 but first ensure there're here Mar 02 17:10:22 ssh debian@beaglebone.local Mar 02 17:10:22 ssh: Could not resolve hostname beaglebone.local: Name or service not known Mar 02 17:10:57 no I mean the output of ip a Mar 02 17:12:04 #cmdline=coherent_pool=1M net.ifnames=0 quiet video=HDMI-A-1:1024x768@60e Mar 02 17:12:31 the output of ip addr Mar 02 17:12:58 is this the line of code I have to set to 1280 x 720. Then uncomment? Mar 02 17:14:05 I rather not paste everything from ip address because I do not know if it shows data I should not display publicly? Mar 02 17:14:19 ipv6 may be public Mar 02 17:14:23 you can show only the ipv4 Mar 02 17:14:25 ip -4 addr Mar 02 17:14:55 the ipv4 should be private unless you're on a server Mar 02 17:16:08 I avoid pasting data I am unable to determine if I rather should not. Mar 02 17:18:14 can you tell #cmdline=coherent_pool=1M net.ifnames=0 quiet video=HDMI-A-1:1024x768@60e should be edited to 1280 x 720. And uncommented? Mar 02 17:21:09 probably Mar 02 17:21:14 comment the other cmdline= line Mar 02 17:23:21 when the bbb is running and connected to the hdmi tv then you cannot open a command line and edit the resolution? Mar 02 17:24:27 you can use the xrandr tool for that Mar 02 17:24:35 but editing the configuration file is better Mar 02 17:25:11 and you cannot edit the configuration file on a running bbb? Mar 02 17:26:20 I have a 1080 dvi display. I cannot use an hdmi to dvi adapter and get that to work? Mar 02 17:27:22 you can edit the configuration file live yes Mar 02 17:27:24 and then reboot Mar 02 17:27:59 I will start the bbb. Mar 02 17:32:47 I have opened a command line on a running bbb. Mar 02 17:33:16 so when you plug your monitor nothing shows up Mar 02 17:33:26 What do I write? Mar 02 17:34:20 The desktop gui displays. But it is moved to the left and down. You can barely watch the task bar. Mar 02 17:34:46 I have opened a command line. Mar 02 17:34:48 I don't know how xrandr works, you can check that online post: https://askubuntu.com/a/883996 Mar 02 17:35:09 Can't I edit the configuration file? Mar 02 17:35:22 uEnv.txt Mar 02 17:35:42 yeah you can Mar 02 17:35:56 uncomment the #cmdline=coherent_pool blablah Mar 02 17:36:04 and comment the cmdline= that was previously uncommented Mar 02 17:36:09 then edit your resolution, save the file and restart Mar 02 17:47:09 I have done the editing. Turning off the computer restarting. Mar 02 17:55:30 strange. The desktop gui fits a little better. But it still has not the right resolution. Mar 02 17:58:26 flj: "it is moved to the left and down" .. that would suggest you have a black bar or something at the top and right. don't you mean "it is too large" ? Mar 02 17:59:16 (i.e. it is overscanned, which is exactly the known issue with using TV as monitors I've mentioned earlier) Mar 02 18:00:56 to large, yes. You can only see part of the task bar and not see what is displayed to the very left. The error has not occurred before. Mar 02 18:02:47 I can try to reverse the resolution again. Then connect to hdmi2. Right now it is connected to hdmi1. Mar 02 18:03:19 yeah if you had different results before, it may very well be that you used a different input on your tv Mar 02 18:03:27 like I said, it's ultimately the tv that's responsible for this Mar 02 18:03:39 how to fix it is tv-dependent Mar 02 18:09:09 no did not work on hdmi2. Mar 02 18:37:30 on the hdmi tv's remote control is a button to select aspect ratio. It was on auto. If full is selected the desktop gui fits again. Mar 02 18:38:57 previously when desktop gui fitted I think aspect ratio was auto. Mar 02 18:39:22 it probably wasn't. Mar 02 18:39:53 I can't imagine anything having changed on the beaglebone side that could make a difference Mar 02 18:40:10 far more likely that some tv setting was different Mar 02 18:40:49 I only say so because I have not noticed I touched the aspect ratio button at all. Mar 02 18:49:23 sudo! Mar 02 20:00:57 Is this how to get the rt kernel on the BBB? ----> --bone-rt-channel Mar 02 20:01:55 so, it would look like this: sudo /opt/scripts/tools/update_kernel.sh --lts-4_14 --bone-rt-channel Mar 02 21:35:32 in general, unless you know what you're doing, you should use the ti series rather than the bone series Mar 02 21:36:04 i.e. --ti-rt-channel Mar 02 21:38:17 why do you think you need/want an rt kernel? Mar 02 21:43:29 since getting useful guarantees from an rt kernel requires carefully considering the priorities to assign to all realtime tasks on the system, including the kernel threads an rt kernel creates for each interrupt handler. and to be honest I'm not even sure how one is supposed to arrange for getting their priorities set Mar 02 22:07:53 Okay. Mar 02 22:08:30 Oh and I was going to keep trying to use the ArduCopter stuff to get this BBBlue in the air. Mar 02 22:08:41 I think I may have found my mistake in the whole process. Mar 02 22:09:19 imfatant/test on github says to use the bone-rt-channel for rt support. Mar 02 22:09:33 I can try another rt kernel. Mar 02 22:10:06 how old is that information? :P Mar 02 22:10:06 I will try the --ti-rt-channel. Mar 02 22:10:13 A month or two? Mar 02 22:10:17 Let me check. Mar 02 22:10:21 curious Mar 02 22:10:36 a month ago. Mar 02 22:10:54 The last addition was made a month ago on the README. Mar 02 22:11:13 Anyway, I could not get the bone-rt kernel on my BBBlue anyway. Mar 02 22:11:22 I guess I will try ti-channel. Mar 02 22:11:22 ? Mar 02 22:11:30 what do you mean? Mar 02 22:11:49 I am using the console image and my BBBlue stops when I update to that kernel. Mar 02 22:11:56 It just stops every time. Mar 02 22:11:59 ah Mar 02 22:12:08 I have to push the power button and boot again to use it. Mar 02 22:12:34 uhh Mar 02 22:12:51 Uhh? Mar 02 22:13:11 and then you're still on the old kernel? you mean the update_kernel.sh script somehow causes a freeze? that sounds extremely strange Mar 02 22:13:24 But...the bone-channel is not on the BBBlue. I think there is something wrong. Mar 02 22:13:26 Right. Mar 02 22:13:38 given that's it's basically just a wrapper around apt-get install Mar 02 22:13:45 I am on the old kernel still. Mar 02 22:14:35 at first, I was kicked out of my terminal session and then it would just halt and do nothing until I pushed the power button to boot again. Mar 02 22:15:09 I will go and grab a new console image. Mar 02 22:15:22 that sounds extremely bizarre to me Mar 02 22:15:32 Right. This is the first time this has happened to me. Mar 02 22:15:36 I can't imagine what could possibly be going on that could do that Mar 02 22:16:12 Maybe the imfatant/test image on their github page was an outdated image from rcn-ee that is no longer supported. I have no clue. Mar 02 22:16:31 oh you're using a random image found on the internet Mar 02 22:16:51 (not that that explains anything) Mar 02 22:17:18 Hhahah. I thought these people got their image straight from the rcn's repo. Mar 02 22:17:20 I might be wrong. Mar 02 22:17:44 Linux beaglebone 4.14.79-ti-r89 #1 SMP PREEMPT Sat Jan 5 02:49:29 UTC 2019 armv7l GNU/Linux is the image. Mar 02 22:17:51 no it isn't Mar 02 22:17:53 that's a kernel Mar 02 22:18:02 Oh. sorry. Please hold. I keep forgetting. Mar 02 22:18:23 BeagleBoard.org Debian Image 2019-01-13 Mar 02 22:18:36 so it's actually a testing image Mar 02 22:18:40 Aw. Mar 02 22:18:52 Yes. Mar 02 22:19:04 that's not necessarily a problem, I just wonder what the reason is for selecting that image Mar 02 22:19:36 But, they keep saying that something is "broken" w/ the 4.14 and 4.9 kernels. Mar 02 22:19:56 I thought I updated to 4.19 but obviously something else took place. Mar 02 22:20:25 Maybe that is it. I have to update to 4.19 and then to 4.19 --bone-rt-channel? Mar 02 22:21:29 I guess I can try it. Mar 02 22:21:58 uhh, don't use 4.19, use 4.14 Mar 02 22:22:16 Are you sure? I think the people were using the 4.14 kernel. Mar 02 22:22:26 sorry. 4.19 kernel. Mar 02 22:22:58 Okay. I will go and get the regular image and try again. Mar 02 22:23:03 4.19 didn't even support remoteproc-pru until like, a week ago or something Mar 02 22:23:13 it's not ready for prime time yet Mar 02 22:23:24 Hmmm. Mar 02 22:23:24 Okay. No issue. Mar 02 22:23:28 4.14-ti is the current stable kernel series Mar 02 22:23:43 Oy! I will try that then. Mar 02 22:23:45 Again! Mar 02 22:24:52 Do you suggest a console image? Mar 02 22:26:15 I ask b/c the idea was to boot faster when booting the board. This way, things can fly around quicker. I guess. Mar 02 22:26:29 I guess I could use the IoT if necessary. Mar 02 22:28:00 ... Mar 02 22:28:01 brb Mar 02 22:47:55 Okay. I am beat until later. See ya! Mar 03 00:10:22 i am trying to ssh the device via usb. ssh 192.168.7.2 -l root Mar 03 00:10:29 i see it is asking for password Mar 03 00:10:51 temppwd doesnt work Mar 03 00:11:07 username is 'debian' Mar 03 00:12:01 thanks zmatt - this works : ssh 192.168.7.2 -l debian Mar 03 00:12:09 with temppwd password Mar 03 01:41:54 I am building the arducopter stuff again. Is anyone interested in making the BBBlue fly? Mar 03 01:42:08 So far, no errors. Things are looking promising. Mar 03 01:43:06 And when I say "looking," I mean that I absolutely know nothing about what is in the future. Mar 03 01:46:01 I don't know if this is a good place to ask but beagle's hardwares are built on top of ARM's processors. They are not open source, only licensed, I think? Is there any chance RISC-V will make it to one of beagle's boards? Mar 03 01:46:35 rhinoboi[m]: beagleboard.org specifically makes boards based on Texas Instruments' ARM-based SoCs Mar 03 01:47:56 as far as designs go they are quite open, with the hardware designs being open, the parts being available for purchase by anyone even in low quantity, and the SoC has thousands of pages of documentation Mar 03 01:50:16 the licensing status of the ARM architecture itself is not really relevant to anyone other than SoC designers Mar 03 01:57:11 I'm sorry if this sounds super noob Mar 03 02:00:46 historically beagleboard.org has only worked with TI ARM SoCs ... but I don't think there's anything embedded in it's mission or anything like that Mar 03 02:03:22 While the licensing status of the ARM architecture is only relevant to SoC designers and there are thoudsands of pages of documentation for ARM's processors, aren't the designers only given the blueprints and there are not much room to expand?? Adapting RISC-can help beagleboard.org broaden its scope and prolly take advantage of the open source community Mar 03 02:04:02 rhinoboi[m]: ehm, no? what? Mar 03 02:05:02 zmatt: haha nvm I should probably just do my hw and ask a better question later Mar 03 02:05:11 I don't understand what you're trying to say. A SoC that's relevant and competitive in terms of performance is not going to be open source itself either way Mar 03 02:05:29 more importantly, even if it was, there isn't really much you could do with it. it's not like you could make your own SoC unless you have an insane budget Mar 03 02:06:08 it's something that just requires very specialized knowledge, skills, and tools Mar 03 02:07:25 I got ./waf to work w/ python3! Now, I see the skies are coming! Mar 03 02:07:42 so I'm sure RISC-V is great for things like university researchers in processor design and stuff like that, but it's not really of any relevance if you just want to make a cool board Mar 03 02:08:50 true Mar 03 02:09:49 zmatt: are you working are studying? Mar 03 02:09:52 having a well-documented SoC does matter for open source development, and having an open hardware design (based on parts you can actually buy) is very useful too. it means that if you make a prototype of something based on a beaglebone + external hardware, you could later migrate to a custom design Mar 03 02:10:10 using RISC-V would guarantee neither of these things Mar 03 02:11:14 I work yes, as software developer in embedded systems Mar 03 02:12:22 vagrantc: you're technically true, but it does have strong ties with TI as far as I know Mar 03 02:12:31 *technically right Mar 03 02:14:20 indeed Mar 03 02:15:57 e.g. the about page does say "Texas Instruments generously allows Jason Kridner, community manager and software cat herder, to spend time to provide support and development of the BeagleBoard.org project as part of their duties at TI." ... I'm sure that making a board based on a SoC from a competitor would cause... friction. :P Mar 03 02:21:34 NXP? Mar 03 02:21:38 Just kidding. Mar 03 02:23:05 Okay zmatt: I am using the 4.14.x --ti-rt-channel kernel and I got waf to build the arducopter build for the BBBlue w/ python3 w/out sudo. Mar 03 02:23:12 Am I am making a mark yet? Mar 03 02:23:54 hurray? Mar 03 02:24:18 Yea. I know. It is a question as of now. Mar 03 02:24:26 But ya! For now. Mar 03 02:25:00 This BBBlue was born to fly w/ ESCs for some reason and I am just the person to pretend it works until it does actually work. Mar 03 02:29:23 So, does this seem like a fair assumption of a bash script for making the GPIO80 work on boot? https://pastebin.com/J1Z1mzEZ Mar 03 02:31:00 Oh...I am still discussing the BBBlue here. Mar 03 02:44:32 https://pastebin.com/FFBsGPMc is the .service file for starting up the bash script and other entities on the BBBlue. Mar 03 02:44:33 ... Mar 03 02:45:09 Anyway...if you get bored and want to chat about it, please reply at some point. **** ENDING LOGGING AT Sun Mar 03 02:59:56 2019