**** BEGIN LOGGING AT Fri Apr 07 03:00:01 2017
Apr 07 06:35:27 <Guest38210> Hi, I faced a problem when sudo apt-get install nodejs in my beaglebone black.
Apr 07 06:35:39 <Guest38210> Err https://deb.nodesource.com/node_4.x/ jessie/main nodejs armhf 4.8.1-2nodesource1~jessie   server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfil E: Failed to fetch https://deb.nodesource.com/node_4.x/pool/main/n/nodejs/nodejs_4.8.1-2nodificates.crt CRLfile: none
Apr 07 06:36:20 <Guest38210> Any help will be appreciated! Thanks in advance!
Apr 07 06:45:24 <zmatt> ancient ca-certificates probably
Apr 07 06:46:04 <zmatt> pretty ancient version of node too
Apr 07 07:08:13 <Guest38210> huh?
Apr 07 07:08:18 <Guest38210> what does it means?
Apr 07 07:52:08 <thinkfat> zmatt: adr r0, =_start and bx r0 might have fooled the assembler I guess
Apr 07 14:47:54 <zmatt> thinkfat: no, it'll work fine as long as _start is marked as a thumb function
Apr 07 14:50:15 <thinkfat> interesting
Apr 07 20:00:03 <windsurf_> I'm trying to clone a 4gb sd card to an 8gb sd card. I've formatted the cards correctly and am using ddrescue to do the backup/restore. Then I think I need to resize the primary partition. Is that a good plan for my goal?
Apr 07 20:43:43 <ayjay_t> i built a thing that works
Apr 07 20:48:23 <zmatt> windsurf_: ext4 ?
Apr 07 20:48:28 <zmatt> ayjay_t: yay \o/
Apr 07 20:48:34 <windsurf_> ?
Apr 07 20:48:39 <zmatt> windsurf_: the filesystem?
Apr 07 20:49:05 <zmatt> (if you don't know then probably yes)
Apr 07 20:49:20 <windsurf_> beaglebone getting started guide, debian
Apr 07 20:49:26 <windsurf_> i don't know whatever that download is
Apr 07 20:49:44 <zmatt> yeah ext4 then
Apr 07 20:50:44 <windsurf_> I have an 8gb card now that thinks its capacity is ~4GB
Apr 07 20:50:49 <zmatt> to expand a partition to a card I just delete the partition and create a new one *at the same offset*
Apr 07 20:51:49 <zmatt> and then once the partition is the correct size, expand the filesystem to fit using e.g.  resize2fs /dev/mmcblk0p1
Apr 07 21:11:29 <windsurf_> zmatt in fdisk I get /dev/mmcblk0p1       2048 15122431 15120384  7.2G 83 Linux after deleting and creating new, so that looks like it worked. I 'w' which saves. All good so far, but then resize2fs gives me, "resize2fs: Bad magic number in super-block while trying to open /dev/mmcblk0p1
Apr 07 21:11:29 <windsurf_> Couldn't find valid filesystem superblock."
Apr 07 21:11:44 <zmatt> are you sure that offset is right?
Apr 07 21:12:00 <zmatt> did you check what it was previously?
Apr 07 21:13:27 <zmatt> since I generally place it at sector 8192 (4 MB from start) rather than sector 2048, and I think rcn (who makes the official images) also started doing so at some point
Apr 07 21:14:45 <windsurf_> zmatt I used defaults
Apr 07 21:14:53 <windsurf_> following this tutorial http://dev.iachieved.it/iachievedit/expanding-your-beaglebone-microsd-filesystem/
Apr 07 21:15:14 <zmatt> it *has* to be at the same offset
Apr 07 21:15:19 <zmatt> as it was before
Apr 07 21:15:57 <zmatt> if you don't have that information anymore, try recreating it at offset 8192 and see if resize2fs recognizes it as a filesystem then
Apr 07 21:16:22 <windsurf_> when i look in fdisk is 'start' the offset you mean? right now it says 2048 but not sure if that's after messing it up?
Apr 07 21:16:47 <zmatt> of course it says so, you just created it there
Apr 07 21:16:51 <windsurf_> ok
Apr 07 21:17:04 <windsurf_> i'll create a new backup and start again
Apr 07 21:17:08 <zmatt> no need
Apr 07 21:17:11 <windsurf_> o
Apr 07 21:17:11 <zmatt> nothing has been damaged
Apr 07 21:17:14 <windsurf_> ok
Apr 07 21:17:21 <windsurf_> i'll try 8192
Apr 07 21:18:13 <windsurf_> resize command is working now
Apr 07 21:18:16 <zmatt> voila
Apr 07 21:20:14 <windsurf_> Maybe I'm using the on-board storage
Apr 07 21:20:26 <windsurf_> fdisk is showing /dev/mmcblk0p1       8192 15122431 15114240  7.2G 83 Linux
Apr 07 21:20:26 <zmatt> changing the partition map does not destroy or change any other data on a disk/card, so you can then always still get your filesystems back, provided you can find them
Apr 07 21:20:29 <windsurf_> and df -h is showing
Apr 07 21:20:40 <windsurf_>  /dev/mmcblk1p1  3.6G  1.9G  1.5G  56% /
Apr 07 21:20:51 <zmatt> different block devices
Apr 07 21:20:55 <zmatt> mmcblk1p1 vs mmcblk0p1
Apr 07 21:21:11 <zmatt> df only shows mounted partitions
Apr 07 21:21:54 <windsurf_> so, how do I know if I'm using the sd card? I did hold the user btn on boot
Apr 07 21:22:14 <windsurf_> I don't know which numbers I can trust
Apr 07 21:22:19 <zmatt> all of them
Apr 07 21:23:13 <zmatt> although I'm a bit confused, you held down the S2 button?
Apr 07 21:23:39 <zmatt> your df -h listing indicates you did boot from eMMC
Apr 07 21:24:08 <windsurf_> so is /dev/mmcblk1p1 the on-board (aka eMMC?) storage and /dev/mmcblk0p1 is the SD?
Apr 07 21:24:27 <windsurf_> I did hold down the "user" button but I don't know when it's safe to let go
Apr 07 21:24:40 <windsurf_> I held it until I saw some lights flashing a bit more regularly
Apr 07 21:24:47 <zmatt> a few miliseconds after the power led turns on
Apr 07 21:25:07 <windsurf_> k
Apr 07 21:25:08 <zmatt> it is sampled at the moment power turns on
Apr 07 21:25:26 <windsurf_> ok that's good to know – the 8gb card must not be bootable then, I'm guessing
Apr 07 21:25:36 <zmatt> no you probably didn't hold it down properly
Apr 07 21:25:41 <windsurf_> i'll try again
Apr 07 21:25:45 <zmatt> why?
Apr 07 21:26:01 <windsurf_> because you said I didn't do it properly
Apr 07 21:26:14 <zmatt> I also asked puzzled why you were doing it in the first place
Apr 07 21:26:35 <windsurf_> to boot from the SD card, the getting started guide says that's needed
Apr 07 21:27:21 <zmatt> how exactly did you copy stuff over to the card?
Apr 07 21:27:42 <zmatt> you rarely need to hold down the S2 button, the bootloader will normally already prefer booting from card if it is bootable
Apr 07 21:28:00 <zmatt> what holding it down (during power on) does is exclude eMMC from the boot order
Apr 07 21:28:33 <windsurf_> hm i see
Apr 07 21:29:56 <zmatt> so, where was the image originally located, on a different card? eMMC?
Apr 07 21:30:14 <windsurf_> I was just following getting started guides which suggested I download debian from the beaglebone site (an .img file), on OS X used PiFiller script to copy it to the 4GB SD card, which I thought was larger than it was, then used ddrescue to clone that 4GB card to a new SD after doing a bunch of linux setup stuff for my purposes, then used ddrescue and tried PiFiller too, to clone the 4gb img back to the 8GB card
Apr 07 21:30:46 <windsurf_> cloned the 4GB card to a new .img file*
Apr 07 21:31:12 <windsurf_> so 4GB SD -> .img -> 8GB SD
Apr 07 21:31:25 <windsurf_> hence the partition expansion
Apr 07 21:31:33 <zmatt> can you do:   dd if=/dev/mmcblk0 count=1 | hexdump -C
Apr 07 21:31:43 <windsurf_> sure
Apr 07 21:32:17 <zmatt> if it says something with "CHSETTINGS" in it then all is fine
Apr 07 21:32:59 <windsurf_> hey so I did reboot and held down the user button for less time and now df -h is reporting that I've got 8gb minus what's used
Apr 07 21:33:36 <zmatt> how long you hold it down has no impact
Apr 07 21:33:37 <windsurf_> I also have dd output now
Apr 07 21:33:49 * windsurf_ reboots again without holding
Apr 07 21:34:01 <zmatt> note: it's sampled on power-on, not on reboot
Apr 07 21:34:08 <windsurf_> oh
Apr 07 21:34:17 <windsurf_> that might have occasionally been one issue
Apr 07 21:34:20 <zmatt> the setting remains in effect until you power off and on again
Apr 07 21:34:32 <windsurf_> very good to know
Apr 07 21:35:08 <zmatt> so, question is whether it also boots from card without S2
Apr 07 21:35:21 <windsurf_> we'll see
Apr 07 21:35:39 <zmatt> since it really should, unless maybe the bootloader on eMMC is too ancient
Apr 07 21:36:52 <windsurf_> worked without 2d down
Apr 07 21:38:04 <windsurf_> thanks a lot for your help and insight
Apr 07 21:38:11 <zmatt> np
Apr 07 21:48:53 <windsurf_> zmatt so I just booted without holding s2 – how do I access the eMMC storage now
Apr 07 21:48:56 <windsurf_> cd ?
Apr 07 21:49:01 <zmatt> you may need to mount it
Apr 07 21:49:11 <windsurf_> mmcblk1p1 ?
Apr 07 21:49:39 <zmatt> so, e.g.  mount /dev/mmcblk1p1 /mnt
Apr 07 21:49:52 <zmatt> or some other empty directory of choice
Apr 07 21:50:08 <zmatt> you can of course configure things to mount it automatically
Apr 07 21:50:30 <windsurf_> is /mnt just an arbitrary name that isn't already seen in ls -l /
Apr 07 21:51:17 <zmatt> it needs to exist as empty directory
Apr 07 21:52:12 <windsurf_> special device does not exist
Apr 07 21:52:19 <zmatt> lsblk
Apr 07 21:52:56 <windsurf_> I see a couple boots and a couple mmcblk's, 0 and 1
Apr 07 21:53:08 <windsurf_> 0p1, 1p1
Apr 07 21:53:30 <zmatt> "boot" block devices are only associated with eMMC
Apr 07 21:54:15 <zmatt> afaik on recent kernels eMMC should always be mmcblk1
Apr 07 21:55:14 <zmatt> "special device does not exist" ?   o.O
Apr 07 21:55:33 <windsurf_> mount: special device mmcblk1p1 does not exist
Apr 07 21:55:39 <windsurf_> mount: special device mmcblk1 does not exist
Apr 07 21:56:48 <zmatt> ehh, you're omitting the /dev/
Apr 07 21:57:42 <zmatt> possibly because you saw lsblk omitting them out of laziness, but unfortunately mount doesn't tolerate that :)
Apr 07 21:58:01 <windsurf_> right, thanks
Apr 07 21:59:59 <zmatt> gotto catch a train, bbl
Apr 07 22:00:02 <zmatt> *bus
Apr 08 02:55:53 <Set_> I am alive!
Apr 08 02:55:59 <Set_> BBBW!
Apr 08 02:56:20 <Set_> How can I use connmanctl to get online via WiFi on the BBBW?
Apr 08 02:57:15 <Set_> I tried to find my wlan0 but it is an Ethernet port for some reason and not a WiFi adapter.
Apr 08 02:57:32 <zmatt> ?
Apr 08 02:57:37 <Set_> Yep.
Apr 08 02:57:55 <zmatt> it's showing "eth0" instead of "wlan0" ?
Apr 08 02:58:09 <Set_> No.
Apr 08 02:58:23 <Set_> Hold on. Let me get you the exact reading.
Apr 08 02:58:57 <Set_> LinkEncap: Ethernet
Apr 08 02:59:19 <Set_> I perform ifconfig wlan0
Apr 08 02:59:41 <zmatt> ok, and?
Apr 08 02:59:48 <Set_> That is it.
**** ENDING LOGGING AT Sat Apr 08 03:00:02 2017