**** BEGIN LOGGING AT Sat Nov 01 03:00:00 2014 Nov 01 03:06:21 ok, got recording working but it's very quiet Nov 01 03:09:40 PCChris: if the noise is low to raise the volume... if noise is high check the source Nov 01 03:11:10 BellinganRoy: hmmm? Do you know what I should be adjusting in alsamixer to increase capture volume? Nov 01 03:20:00 sorry no... PCChris Nov 01 04:33:38 I am interested in connecting a BBB to a PCB I am designing. I know the BBB requires 5V input to power. What is the 3.3V I see mentioned for the BBB? Nov 01 06:27:14 Has anyone messed with Streisand on BBB? Nov 01 09:31:08 <_av500_> Barbara? Nov 01 09:48:51 you don't mess with her Nov 01 09:50:09 *g* Nov 01 18:54:38 jkridner are you there Nov 01 18:57:49 i still have a problem with setting of the gpio pin to high/low in kernelversion 3.17.1-armv7-x3 Nov 01 18:58:10 i downloaded the latest ubuntu image from http://elinux.org/BeagleBoardUbuntu for beagleboard xm Nov 01 18:58:35 what i found is that in the folder /sys/kernel/debug/omap_mux/ there is no data Nov 01 18:59:11 so i cant set the mux mode or anything else Nov 01 18:59:14 :/ Nov 01 20:59:14 hi vncm Nov 01 20:59:33 newer kernels might not have omap_mux Nov 01 20:59:45 you need device tree or pinmux helpers to set the muxes. Nov 01 21:13:03 jkridner: where is the default dts for boneblack located in the kernel tree? i cannot find it under firmware/ ? Nov 01 21:13:22 arch/arm/boot or something like that. Nov 01 21:14:32 jkridner: thank you! Nov 01 21:52:56 I've written the debian .xz image from http://beagleboard.org/latest-images and booted it on this beagleboneblack from a 16GB SD-card, however the ext partition doesn't like to be resized Nov 01 21:55:41 is that on purpose? Nov 01 22:04:34 how do you try to resize it? what errors do you get? Nov 01 22:06:12 with resize2fs Nov 01 22:06:50 I tried to work around that by recreating the ext (ext4?) partition Nov 01 22:08:19 i'm guessing when you run resize2fs it doesn't respond with "sorry, i don't like this partition". Nov 01 22:08:33 the error message it gives might give useful information in figuring out what to do... Nov 01 22:08:51 no, it responds with something like "can't expand beyond current size" Nov 01 22:09:04 have you resized the partition first? Nov 01 22:09:43 hello, how do i get a toolchain for crosscompiling? i am running jessie on my bbb and my dev-machine. Sould i just get the one from Linaro? Nov 01 22:13:51 before the first boot? I've tried that, yes Nov 01 22:15:12 idwer: and does fdisk/cfdisk/sfdisk recognize the larger size of the partition... ? Nov 01 22:17:43 Yes Nov 01 22:17:46 [ 26.802075] sd 6:0:0:0: [sdb] 30898176 512-byte logical blocks: (15.8 GB/14.7 GiB) Nov 01 22:18:00 that looks like the device, not the partition Nov 01 22:19:16 that *is* the device, not the parition ;) Nov 01 22:20:33 idwer: are you running "resize2fs /dev/mmcblk0p1" or "resize2fs /dev/mmcblk0" ? Nov 01 22:20:41 >> /dev/sdb1 * 2048 198655 196608 96M e W95 FAT16 (LBA) Nov 01 22:20:41 /dev/sdb2 198656 3481599 3282944 1.6G 83 Linux Nov 01 22:20:41 Free space 3481600 30898175 27416576 13.1G Nov 01 22:20:42 idwer: or something else entirely? Nov 01 22:21:06 looks like /dev/sdb2 is still only 1.6G Nov 01 22:21:19 so i presume you want to grow that partition Nov 01 22:21:25 yes, I'm rewriting the card Nov 01 22:21:47 mmcblk0p2 was the partition I passed to resize2fs Nov 01 22:21:57 sdb2, in this case Nov 01 22:22:49 so, resize the partition, re-run resize2fs (it may demand you run fsck on the partition first, unless you do it while mounted) Nov 01 22:23:10 fsck, that might work Nov 01 22:23:25 cfdisk usually has a 'maximize' option, not on this partition Nov 01 22:28:45 vagrantc: "The filesystem is already 410368 (4k) blocks long. Nothing to do!" Nov 01 22:31:43 well, it worked Nov 01 22:32:15 booting :) Nov 01 22:32:44 debian@beaglebone:~$ df -h Nov 01 22:32:45 Filesystem Size Used Avail Use% Mounted on Nov 01 22:32:45 rootfs 1.6G 1.5G 2.2M 100% / Nov 01 22:32:55 like I said, there are some issues Nov 01 22:33:48 the fsck with e2fsck -f Nov 01 22:34:11 s/with/was done using Nov 01 22:35:57 alrighty. 'The filesystem on /dev/mmcblk0p2 is now 3837440 blocks long.' Nov 01 22:37:36 looks promising Nov 01 22:37:46 rootfs 15G 1.5G 13G 11% / Nov 01 22:38:10 so it sounds like you didn't resize the partition successfully Nov 01 22:38:22 sometimes that may require a reboot Nov 01 22:38:52 or reloading the kernel modules ... there was also a command i recall that sometimes worked to refresh the partition tables Nov 01 22:49:16 tar the parition while its offline ( linux PC ), then create partition on the sdcard the remainder of the soe left and untar the tar'd image back over . . . Nov 01 22:50:37 problem solved ^^^ Nov 01 22:54:53 or rsync the files back and forth, recreate the partition inbetween those actions Nov 01 22:55:12 which also did not work out as expected Nov 01 22:55:19 so yes, something was kept locked Nov 01 23:04:38 I know for a fact that using tar will work Nov 01 23:06:05 Since ive mounted the "production demo" images and extracted them to boot NFS Nov 01 23:08:05 maybe the write tab on the physicaly sdcard got bumped off ? ive doen that to myself before but meh who knows what you're hving problems with Nov 01 23:08:57 no, that was not what was wrong.. nor was it in the write protection position Nov 01 23:12:43 well why are you having this problem then ? seems you knwo everything. **** ENDING LOGGING AT Sun Nov 02 03:00:00 2014