**** BEGIN LOGGING AT Wed May 15 02:59:57 2019 May 15 10:05:17 hi, i'm having a problem with my beaglebone blue. I'm trying to expand de memory with a microSD but it isn't working May 15 10:05:51 i'm following those steps: https://elinux.org/Beagleboard:Expanding_File_System_Partition_On_A_microSD May 15 10:06:35 but at the resize2fs command it's give me this error: resize2fs: Bad magic number in super-block while trying to open /dev/mmcblk0p2 Couldn't find valid filesystem superblock. May 15 10:06:47 can someone help me? May 15 10:07:07 well is there an extfs on second partition of the microsd ? May 15 10:11:09 nop May 15 10:11:58 well, then there's also nothing to resize May 15 10:12:24 oh ok, thank you May 15 10:12:39 :) May 15 11:01:11 Marex: yes there is May 15 11:01:23 :/ May 15 11:01:34 that's why these instructions exist May 15 11:02:01 but I don't understand why that person didn't just use the script, as indicated under 'the automated way' May 15 11:03:21 zmatt: well obviously there wasn't in that person's case ;-) May 15 11:03:45 well not anymore after they repartitioned their card wrong May 15 11:03:49 zmatt: and the "Simplified" section of the instructions doesn't create a FS on that partition either May 15 11:04:09 zmatt: well, there we go, the problem was identified May 15 11:04:28 yes, except to the person who needed it solved May 15 11:06:01 oh I kinda misread what you said... I shouldn't be typing when I'm barely awake May 15 11:06:34 though it still wasn't particularly helpful May 15 11:06:55 anyway, good morning -.- I need tea. May 15 11:21:20 zmatt: OK, I will stop trying to be helpful, sorry May 15 12:50:45 hello. I have a beaglebone black wireless, and i'm trying to get bluetooth working on it. i apt installed bluez and tried hcitool dev, but no devices show up. The WL light on the board isn't lit up either. Is there some kind of devicetree I need to install to get BT working or are there some special pins that are reserved for BT? I'm using debian 8.7, but over the many months i've removed packages (like connman because it's May 15 12:50:45 proven to be a complete nightmare for me) so I suspect that might be the issue :-( May 15 13:22:07 clockman: you're still using jessie? oof May 15 13:22:46 yea, all my code and scripts are built on that image. and I know that if I update the image and packages, it's going to crash the hell out of all my stuff May 15 13:23:35 I'm pretty sure the default DT for the bbbw ought to enable it... there's no benefit to not doing so (on the BBBW, wifi/bt doesn't use any expansion header pins or otherwise conflict with any resources, unlike the badly designed BBGW) May 15 13:25:53 also hcitool is deprecated May 15 13:26:05 agreed. I flash the original 8.7 image onto the bbbw and the BT led lights up and I can see the device. So I know the hardware is functioning, and I'm using the same image, but I must have just disabled something really deep in the setting because on my modified image, I can't see the BT hardware at all. I'm not sure where to begin looking for the device May 15 13:26:59 well every tutorial i see online is to use hcitool. BB doesn't exactly have up-to-date projects that I've found. May 15 13:27:37 can you pastebin your /boot/uEnv.txt ? May 15 13:28:34 https://pastebin.com/tt1ipMdg May 15 13:29:32 okay, so presumably no DT issues (unless you actually modified/replaced the base dtb) May 15 13:29:53 I haven't used bluetooth yet myself, so I'm not sure how much help I can offer May 15 13:30:42 Okay, well I'll just use USB BT Dongle for now - and maybe I'll have an AHA moment some day. May 15 13:30:49 I suggest just sticking around for a while, plenty of other knowledgable people here but it can take a while for one to glance at chat May 15 13:30:50 Thanks for taking a look for me May 15 13:31:06 will do May 15 13:31:43 I recall having seen a bluetooth-related startup service, so maybe check for that on the working image and see what happened to it on your image May 15 13:35:13 yea, checked just about every readable file in the entire filesystem with "blue" or "bt" in the name. May 15 13:35:32 lol May 15 13:35:43 does wifi work? May 15 13:35:47 perfectly May 15 13:37:23 (yes) May 15 13:38:06 then no idea... and since I'm at work I don't really have the time to dig around on my own bbbw May 15 13:39:01 understood. Thanks zmatt. May 15 17:14:46 I think we may have figured it out. looks like updating all the bb-wl18xx packages to latest worked. I'm glad I didn't have to update *all* packages cause a full system upgrade always f's up my code so hopefully just the upgrading the bb-wl18xx firmware will be okay May 15 17:55:14 what does your code do that's causing so much problems? I noticed you didn't have any overlay specified in /boot/uEnv.txt so I'm guessing you're loading those manually? May 15 18:00:41 I feel like it really shouldn't be that much of a problem to move software to the current debian stretch, unless you're dynamically generating and loading overlays or something May 15 19:18:02 I'm just paranoid because I've updated dozens of packages at once, and have gotten kernel panics, so I am very paranoid - if it's not a security flaw, I don't want to update it. May 15 19:18:57 I'm not actually talking about updating packages though but moving to the latest image May 15 19:20:23 of course it wouldn't be an overnight thing, but it is probably worth playing around with since there have obviously been a lot of improvements over time, and jessie is basically unmaintained afaik May 15 19:20:47 personally I just wouldn't want to be stuck on an old release forever :) May 15 19:21:32 getting a kernel panic after updating packages sounds a bit odd though, since the kernel is normally not automatically updated when you do apt-get upgrade **** ENDING LOGGING AT Thu May 16 03:00:30 2019