jojopi wrote:No. Your plan to tri-state the GPIOs as early as possible can not work because your settings will remain only until the next program tries to configure whichever pins you are using.

That was what I was afraid of... thanks!

Thanks for the reply, Unfortunately I am trying to avoid additional libraries, pretty much because I want to learn about how things work at a low level, and have already written the rest of my project without them. Also is there a place I can put this script where it will be executed before anything...

Sorry I don't mean to bump, but the forum wont let me edit...? I can use a script to set inputs, if I could disable the pull ups in a script too that would be nicer than executing another program I think, does anyone know how this is done? Is there an issue (other than being overwritten) with puttin...

Hi all, In setting a GPIO as an input as in the first example here: http://elinux.org/RPi_Low-level_peripherals, will this then leave the GPIO as an input even after the registers have been unmapped? If so is there a place I can put a script to run a C program that will set all the GPIOs to high imp...

thanks very much,

The setuid option seems appealing, its odd (and annoying) how there doesn't seem to be any way of controlling the GPIOs as a user...

thanks again!

Hi all, I have a project that requires access to /dev/mem in order to change GPIOs, at the moment I have been using root to do this but this is far from ideal. I have tried changing the permissions for /dev/mem to rw- for the kmem group and then adding my user to that group, not only does this not w...

I cant edit posts for some reason... but this worked, thanks all!

plugwash wrote:IIRC the kernel command line (including the location of the root partition) is set by cmdline.txt on the fat parition.

thanks, I have a strong feeling this will work to solve my problem

Well installing it in exactly the same manner except with the default partitions (including 256MB of swap space and / mounted on partition 3) it worked, so I'm fairly confident it has something to do with / being mounted to the 3rd partition that doesn't exist any more. There must be a setting somew...

So did you Google "PANIC: VFS: Unable to mount root fs on unknown-block" ? Yes, Google came up with this thread: http://www.raspberrypi.org/phpBB3/viewtopic.php?t=19338&p=188927 which seemed to suggest an SD card problem, however I have installed other OSs on the same card with success. The second ...

hmmm, my /etc/fstab is as follows... # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file sys...

Sander wrote: If you can't a prompt to edit /etc/fstab, you can put your SD card into another computer, mount it, find /etc/fstab and edit it.

Thanks for your replies, I think this is whats going to have to be done.

Thanks again!

I know this may not be the best idea, but trying to run the standard install without a swap partition leads to a kernel panic on the first boot b/c it tries to mount the root fs on partition 3 which doesn't exist...

any workaround?

thanks in advance.