So, the comment by me above "sounds like a pin conflict", doesn't mean I think for a second that it *is* a pin conflict. I just meant that it is a "reaction" one might expect from having a pin conflict . . . the sdcard, and hdmi should be able to work properly at the same time.
I seem to recall reading something about a udev rule fix a long time back - For situations like these but . . . What I am "remembering" is rather vague in my mind at the moment. On Wed, May 6, 2015 at 3:40 PM, William Hermans <[email protected]> wrote: > Sounds like a possible pin conflict but . . . > > I was reading an ARCHLinux post concerning a similar problem( but on PC ), > and the person fixed it by making some additions to the PAM configuration > file. > > https://bbs.archlinux.org/viewtopic.php?id=167947 > > ( post #5 ). > > Not sure that would fix the problem, but might be worth a try. However, if > you remove the "quiet" from the optarg variable, and you have a serial > debug cable. The output I believe should be more verbose. You can also look > through dmesg, and /var/log/messages to see if you can spot anything > obvious. > > On Wed, May 6, 2015 at 3:11 PM, Sam <[email protected]> wrote: > >> Hey again William! >> >> I am just using the default debian user for now so I have not messed with >> the sudoers file. >> >> If I comment out "optargs=quiet >> capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN" in my uEnv.txt then >> my usb and uSD is automounted correctly. So something strange is happening >> when HDMI is disabled. >> >> I am accessing the BBB with xrdp which may also have something to do with >> it. >> >> I wonder if there somewhere else that I can run the command to disable >> the hdmi that is not on external memory. See if that helps? >> >> Failing that I could try running debian from the uSD. At least that would >> give me all the memory I need. >> >> >> >> On Wednesday, 6 May 2015 19:44:30 UTC+10, Sam wrote: >>> >>> >>> Hey Everyone! >>> >>> I want to use my HDMI pins for other purposes. >>> >>> I have added a uEnv.txt to my bone that contains >>> "optargs=quiet capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN" >>> >>> when i cat the slots >>> debian@beaglebone:~$ cat /sys/devices/bone_capemgr.*/slots >>> 0: 54:PF--- >>> 1: 55:PF--- >>> 2: 56:PF--- >>> 3: 57:PF--- >>> 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G >>> 5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI >>> 6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN >>> >>> Unfortunately when I click a mounted drive in LXDE I get an error "Not >>> Authorised" >>> >>> I can access the drives as root though. >>> >>> Is something happening to the permissions of the mounted drives when >>> uEnv.txt is run? >>> >>> Cheers! >>> >>> Sam >>> >>> >>> >>> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to the Google Groups >> "BeagleBoard" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
