**** BEGIN LOGGING AT Fri Mar 31 03:00:03 2017 Mar 31 07:24:22 hi dear Mar 31 07:25:00 is here anyone who know password for new debian image? Mar 31 07:25:26 it is not the blank for root Mar 31 07:28:44 hi?? Mar 31 07:28:54 anyone here? Mar 31 07:29:56 i'd like to know new passwd for new debian img for beagle Mar 31 07:30:09 somebody is here. standard dos not apply? (15 seconds of google: http://elinux.org/BeagleBoardDebian#Debian_.28jessie.29) Mar 31 07:30:30 hi Mar 31 07:31:01 new image has passwd.. wan not the blank Mar 31 07:31:20 did you actually read the link i gave you? did you actually google yourself for at least one time? Mar 31 07:32:27 i mean root passwd Mar 31 07:32:36 not usr passwd Mar 31 07:33:20 debian can login but root cannot login with blank Mar 31 07:33:25 anymore Mar 31 07:37:33 and the standard user password also does not do the trick? respectively, does sodu work? Mar 31 07:39:09 default usr working fine. Mar 31 07:39:51 root is not possible to login, i do not know passwd for new img Mar 31 07:42:27 the new img i have installed is Debian 8.7 2017-03-19 4GB SD LoT Mar 31 07:43:04 previous version was blank for root passwd.. Mar 31 07:44:21 but this new img from beaglebone.org has some Mar 31 07:48:52 please let me know the passwd for root user of the latest firmware image(Debian 8.7 2017-03-19) Mar 31 08:37:03 Beaglebone Black is pretty cool huh? Mar 31 09:09:03 LetoThe2nd: *sudo Mar 31 09:10:01 hmm, rcn finally fixed the problem of root being able to log in with blank password? that was about time... Mar 31 09:11:16 zmatt: if somebody doesn't spot that typo, he/she gotta leave for good anyways :-P Mar 31 09:15:46 hum, I thought squashfs was kinda popular? it seems difficult to find any page about it that's not covered in a thick layer of dust Mar 31 09:17:32 iirc it has only one popular usecase, and that is live cds. Mar 31 09:19:17 afaik it's also used a lot in embedded systens Mar 31 09:28:45 possibly. Mar 31 09:43:00 damn this sounds interesting... https://www.youtube.com/watch?v=poWoCWDLxRU Mar 31 10:20:36 jeez how do you make a living doing this kind of stuff Mar 31 10:31:36 hmm? Mar 31 10:32:29 by having someone pay for your work ? Mar 31 10:40:02 I'm on mailine kernel, do I have to perform some magic when I want to enable uart4/uart4, or is the procedure the same as with uart1/2? Mar 31 10:40:35 once I pass a DT to barebox (my bootloader), it gets stuck during boot as soon as I enable uart4 or uart5 for some reason Mar 31 10:53:17 i use uart4 but i use it with a factory image and config-pin or pin-config i always forget the order Mar 31 10:53:38 i've done a little device tree voodoo but it's been basically modifying and copy-pasting cape-*.dts's Mar 31 10:54:10 and i load them with configfs, i think thats what its called its in a script now so i forget Mar 31 11:18:23 I still think better tools for generating a custom dt would be really nice to have Mar 31 11:18:32 instead of those yucky overlays Mar 31 11:19:01 jkt: your description isn't very clear though... Mar 31 11:19:12 ohh Mar 31 11:19:14 mainline kernel Mar 31 11:19:18 so, no overlays then Mar 31 11:19:32 yup, and no configfs Mar 31 11:20:02 so I'm essentially editing am335x-boneblack.dts and rebuilding what gets passed to barebox, and to the kernel afterwards Mar 31 11:20:08 ok so you added suitable fragments to your dts to enable other uarts? what's the boot log say? where does it get stuck? Mar 31 11:21:47 I mean, enabling uart4 should be as simple as something like this: https://github.com/mvduin/overlay-utils/blob/master/uart4.dtsi Mar 31 11:21:49 yeah maybe a paste of ur dts Mar 31 11:22:01 zmatt, ayjay_t: https://paste.fedoraproject.org/paste/N8zPfXRUl5GkvVf21BddeV5M1UNdIGYhyRLivL9gydE= is the diff Mar 31 11:22:11 do you want the output of fdtdump as well? Mar 31 11:22:14 no Mar 31 11:22:57 zmatt: right now, barebox (the bootloader) gets stuck in its scond stage Mar 31 11:23:22 with some extra debugging, I made it print https://paste.fedoraproject.org/paste/jowVFapZpK1MNJ03vQxEd15M1UNdIGYhyRLivL9gydE= Mar 31 11:24:03 btw, I strongly suggest making a *copy* of a dts and customizing that instead of changing one of the standard dtbs Mar 31 11:24:57 zmatt: yeah, understood, it's just that this makes it super-easy to simply let buildroot patch barebox as it builds the image Mar 31 11:25:36 I guess in mainline there's no boneblack variant dt that already omits the hdmi stuff, to use as base? would have made a diff a lot of messy I think... Mar 31 11:26:36 isn't it simply indexing an array out of bounds or something? Mar 31 11:26:46 not counting on that many uarts Mar 31 11:27:13 even linux has stupid limits you configure at compile-time for reasons that completely elude me Mar 31 11:28:11 btw I suspect you'll also want to remove the block enabling lcdc Mar 31 11:28:22 zmatt: yup, I checked that, and I don't see any obvious UART limit in barebox Mar 31 11:28:36 lcdc is an LCD controller I suppose? Mar 31 11:28:56 yes that's the actual display controller Mar 31 11:30:28 which kernel version is this? Mar 31 11:32:12 zmatt: 4.9.18 Mar 31 11:32:27 there's no way to make barebox simply ignore this stuff? I mean, these devices are not any of barebox' business really Mar 31 11:33:25 zmatt: removing lcdc didn't help, either Mar 31 11:33:36 I didn't expect it to Mar 31 11:33:46 zmatt: well, I wanted to make my life easier (hehe) and to reuse the same DTB between the bootloader and the kernel Mar 31 11:33:51 it was just being silly there, an lcd controller with no display to control Mar 31 11:34:15 I don't really need these UARTs right now anyway, so I can ignore them; I'm in the "let's learn stuff" mood now Mar 31 11:34:16 that seems a bit misguided imho Mar 31 11:34:47 a bootloader and the kernel don't need the same info Mar 31 11:37:43 *mainline* 4.9.18 ? Mar 31 11:38:38 since that doesn't seem to match your dts Mar 31 11:40:39 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/tree/arch/arm/boot/dts/am335x-boneblack.dts?h=v4.9.18#n80 Mar 31 11:42:33 zmatt: I'm also using barebox 2017.02; they import the DTS into their git, and then do $magic so that it turns up in another directory. I'm patching stuff found in that other directory, which gets actually used Mar 31 11:43:16 ok, but where did the port declarations go? Mar 31 11:44:02 I have no idea. OK, let's get rid of barebox' stuff, and tweak just the kernel's one Mar 31 11:44:20 that sounds like a good idea Mar 31 11:45:44 I see nothing weird about uarts 4 and 5 anyway, so it sounds like a barebox issue Mar 31 11:45:48 we're using uart4 without issue Mar 31 12:50:18 zmatt: thanks, just fixing the kernel's DTS did the trick Mar 31 12:51:45 is there an easy option to reuse stuff from arch/arm/boot/dts/am335x-boneblack.dts ? it's not a .dtsi, and it has the version block on top, and therefore #include "..." doesn't really work Mar 31 13:06:06 jkt: actually #include does work, but I suggest first taking a look at kernel 4.10 since they've reorganized things there Mar 31 13:06:42 and most of the dts is hdmi-related anyway, which you removed Mar 31 13:07:47 huh weird that mainline 4.9 has that &rtc block in the .dts, that definitely belongs in bone-common.dtsi Mar 31 13:13:41 dtc tolerates multiple /dts-v1/; directives, so to tweak an existing dts you can in fact #include it and then add your customizations below that Mar 31 13:14:26 zmatt: perhaps that's that ancient dtc, then. OK, thanks. Mar 31 13:18:13 heh, I'm still using my own dtc... I was hoping to restructure it to be a lot more flexible, but it didn't take long before I got really tired of fighting with bison and his reduce/reduce conflicts or whatever Mar 31 13:19:00 it did gain the ability to put multiple labels on one node Mar 31 13:19:46 in retrospect I should just have rewritten the parser in perl, would have been much easier Mar 31 13:37:44 hello hello Mar 31 13:42:53 BTW I got a little monitor for xmas that works with to BB "out of the box" so I don't have to mess with those troublesome monitors I have anymore Mar 31 13:42:55 :-D Mar 31 13:44:53 model? Mar 31 14:01:10 Black, Rev C I believe Mar 31 14:03:11 no the monitor Mar 31 19:08:06 hi, Mar 31 19:08:19 help me Mar 31 19:09:06 From where I download an operating system for a beagleboard xm Mar 31 19:11:27 Diabal: http://beagleboard.org/latest-images Mar 31 19:22:40 Thank you very much, and how do I install it? Mar 31 19:23:01 bbxm-debian-8.6 Mar 31 20:05:24 thinkfat: yay, an actual response :D Mar 31 20:36:29 zmatt: yeah Mar 31 20:46:40 zmatt: it's funny, you know. all documentation I found doesn't go any deeper into this matter, basically just states: "jtag may disturb deepsleep transition", without going into any detail Mar 31 22:35:14 howdy friends! Mar 31 22:47:26 Hello. I installed the latest iot debian image in my beaglebone black and the wifi dongle has a strange interface name. Mar 31 22:47:41 wlx6002b499943e Mar 31 22:48:20 Oh, and I also updated the kernel to 4.10.7-bone1 Mar 31 22:51:10 the problem is dhcp client 4.3.1 says "Bind socket to interface: No such device" Mar 31 22:51:39 And I can't use dhcp over my fancy wifi dongle. Mar 31 22:56:34 hah, apparently the name is too long for poor old dhcpcd **** ENDING LOGGING AT Sat Apr 01 03:00:02 2017