cant program with usb adapter except through sudo nautilus ubuntu

Help please
only way I can gete axepad to program is by opening axepad using terminal and typing "sudo nautilus, then navigating to axepad folder and it works. If I open axepad via my desktop link or by going through home folder and clicking -although it opens axepad, when it comes to programming f5 etc it says unable to open..permission denied.
The folder permissions tab say "allow execution as a program" etc.
Must be some sort of ubuntu thing I am using 12.04 and I also had to go through the routine of sudo modprobe for my usb adapter (vendor and id )etc
Can someone please help I dont want to have to go through terminal every time I want to run axepad
thanks in advance.

I had thought that someone would have replied before now.

As you have discovered, it is apparently a permission thing and you can get around it by using sudo. Doable, but obviously not what's required.
It is difficult for me to advise you, not seeing what you can see, but look at the permissions, owner and group entries in response to an appropriate ls -l command around the Axepad directory.

Your answer should be here:
http://www.yolinux.com/TUTORIALS/LinuxTutorialManagingGroups.html

Hopefully you will be able to identify an appropriate group that you need to also belong to.
In the output from an appropriate ls -l command the third column is the owner and the fourth is the group. Typically users may require to be members of the video group to be able to watch . . . video.

It's a start, hopefully.


.

I also had to go through the routine of sudo modprobe for my usb adapter

Click to expand...

I have Linux mint 13, which is Ubuntu 12.04 based distro and Axepad is working perfectly when opening it via sudo nautilus. I don't know which installiong option you have used but in manual: http://www.picaxe.com/docs/axe027.pdf go to section 4.2 and try to do tricks that have mentioned in linux option 2. That's the way i'm using it.

still no good

Paix said:

I had thought that someone would have replied before now.

As you have discovered, it is apparently a permission thing and you can get around it by using sudo. Doable, but obviously not what's required.
It is difficult for me to advise you, not seeing what you can see, but look at the permissions, owner and group entries in response to an appropriate ls -l command around the Axepad directory.

Your answer should be here:
http://www.yolinux.com/TUTORIALS/LinuxTutorialManagingGroups.html

Hopefully you will be able to identify an appropriate group that you need to also belong to.
In the output from an appropriate ls -l command the third column is the owner and the fourth is the group. Typically users may require to be members of the video group to be able to watch . . . video.

It's a start, hopefully.


.

Click to expand...

this is what I get from ls -l

pete@pete-travelmate6293:~/axepad$ ls -l LinAXEpad
-rwxrwxrwx 1 pete pete 8715223 May 1 2012 LinAXEpad
not sure which of the above is column 4-is it the second pete? what is the 8715223 thing? I am a newbie please keep it simple thanks

@peterx, the 8715223 is the number of bytes in the file LinAXEpad

I can see where you are now.
type in:
ls -l ~/axepad*

Which should show the permissions on the directory axepad itself as well as the contents which indicate that you are the file owner and the usergroup is yours too.

It is fairly unusual for files to have permissions of 777 as your LinAXEpad is, but that's not to say that it is wrong. 755 I would have thought would be more normal to stop other users from deleting your file - obviously not an issue in a non-business, privately owned situation. 755 would be -rwxr-xr-x I tend to use numbers with chmod chgrp because I can't remember the syntax of the other way of doing it. the three groups are "owner, group and other or world".

I will read the link that Puuhaaja has kindly supplied and comment further. I am unable to load LinAXEpad as my SUSE 11.0 distro is a few years out of support and in need of a retread.

Can you give me a heads up please Technical?

I appear to hit an error when attempting to run the modprobe command from the options > ports > AXE027 MODPROBE dialogue button.

On SUSE Linux it's /sbin/modprobe. SUSE has a few non-standard locations for significant files. Normally it's just a tweak to get things headed in the right direction.

@Technical, can you tell me where LinAXEpad will be looking for modprobe. I can then try a soft link to pick up my OS modprobe file and give it a try.

I have edited my /etc/group file to add myself to the uucp group. The groups command comes back correctly indicating that I'm a member of the in crowd, but I'm still failing. At least if I can solve for the finding of modprobe I can rule that out. My OS is rather out of date and so the problem may be deeper, but I can't test on a more recent release for some while yet. Not a major problem for me as I currently develop on a Win7 netbook (not out of choice).

Paix
here is what I get when typing what you suggested from the prompt. I cant figure out all of these exactly I have the "execute as a program" box checked in the permissions tab.
and thanks so far

pete@pete-travelmate6293:~$ ls -l ~/axepad*
total 32212
drwxrwxrwx 2 pete pete 4096 May 1 2012 compiler_linux
drwxrwxrwx 2 pete pete 4096 May 1 2012 datasheets
-rwxrwxrwx 1 pete pete 8715223 May 1 2012 LinAXEpad
drwxrwxrwx 2 pete pete 4096 May 1 2012 LinAXEpad Libs
-rw-rw---- 1 pete pete 24248832 Dec 1 15:27 LinAXEpad.tar
drwxrwxrwx 2 pete pete 4096 May 1 2012 syntax

Paix said:

@Technical, can you tell me where LinAXEpad will be looking for modprobe. I can then try a soft link to pick up my OS modprobe file and give it a try.

Click to expand...

When the "modprobe" button is used it executes -

sudo modprobe ftdi_sio vendor=0x0403 product=0xbd90

I would guess it finds the 'modprobe' command from some environment variable which specifies where to look for executable files.

Details on how to configure the modprobe can be found on pages 27 and 28 of the AXEpad manual, accessible through the Help menu in AXEpad or online at -

http://www.picaxe.com/docs/pad001.pdf

I found that AXEpad didn't perform very well under Ubuntu so I use a windows license under Virtualbox, which works well. If you have a windows license sufficient to run PE (I use XP but I think other older versions also work, though I can't check that) then you could also do this. Unfortunately PE5 won't run under Wine but maybe PE6 will (it is on the wish list but there is no indication whether Rev-Ed will action).

Fundamentally your problem is that AXEpad on your machine requires root permissions (hence success when using sudo). Whilst that may be necessary for installation it should not be necessary for usage. Unfortunately I don't know why that is.

Thanks for that Hippy, Modified axepad.ini to use /sbin/modprobe and gave it the password, but when executed from the command line, pressing the modprobe button prompts for the password and accepts it, but my mileage varies significantly and I have no wish to proceed further. I have a Windows netbook and use that for programming, Far from ideal, but it works and life is too short. I'm way out of date and that is probably contributing to the problem.

I'm very grateful for the help and only regret that I am unable to successfully solve Peterx's problem.

to all and sundry with usb adapter problem with axepad requiring sudo nautilus(ubuntu) here is the fix
HERE IS THE FIX change the word pete to your name as it appears in terminal
ie copy and paste the following line having changed the word pete.
sudo adduser pete dialout

log out and log back in, you should beable to run and download the axe stuff as your user, no need to sudo nautilus

this is because usb, modems etc by default are in a group called dialout...for security reasons dont allow root access, the fix just makes you a member of the group and it works.

HERE IS THE FIX change the word pete to your name as it appears in terminal
ie copy and paste the following line having changed the word pete.
sudo adduser pete dialout

Click to expand...

Wow! Thanks! That really works.

all this is from the id axe027, because the same FTDI cable standard work fine without any.
axe027 used the same drivers under ftdi_sio and can't find ttyusb0.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
JOUAS .JOUAS LINUX 3.2.9 / UBUNTU 12.04 LTS 32 /64- AXE027 PICAXE INSTALLATION
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1- follow axe027 documentation

# the axe027 cable is supply by FTDI USB/Serial/TTL 5v, with id product specific 0403:bd90
# it's overwrited original FTDI 0403:6001
# linux provided all ready installed the drivers for so, but the id is not defined for Axe027.
# the Picaxe documentation required :

/etc/udev/rules.d/
create file : 99-axe027.rules
contains :

# /etc/udev/rules.d/99-axe027.rules
# contains axe027 udev rule to patch default
# FTDI product id to AXE027 product id (0xbd90)
SYSFS{idProduct}=="bd90", SYSFS{idVendor}=="0403", RUN+="/sbin/modprobe -q ftdi_sio product=0xbd90 vendor=0x0403"

after reebot linux the get this in terminal :

~$ sudo udevcontrol_reload rules //WRONG ----> not available

# !!! check it what's appen

~$ lsusb

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
++++++> Bus 001 Device 003: ID 0403:bd90 Future Technology Devices International, Ltd <++++++++++++++++
Bus 002 Device 003: ID 0483:7554 SGS Thomson Microelectronics 56k SoftModem
Bus 002 Device 004: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 002 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 002 Device 006: ID 0bda:0152 Realtek Semiconductor Corp. Mass Storage Device
Bus 002 Device 007: ID 0a5c:4502 Broadcom Corp. Keyboard (Boot Interface Subclass)
Bus 002 Device 008: ID 0a5c:4503 Broadcom Corp. Mouse (Boot Interface Subclass)
Bus 002 Device 009: ID 050d:016a Belkin Components Bluetooth Mini Dongle

~$ dmesg | tail
[ 14.347783] [fglrx] Reserved FB block: Unshared offset:fbfd000, size:403000
[ 14.347784] [fglrx] Reserved FB block: Unshared offset:3fff4000, size:c000
[ 14.396862] sd 6:0:0:2: [sde] Attached SCSI removable disk
[ 14.402105] sd 6:0:0:0: [sdc] Attached SCSI removable disk
[ 14.404773] sd 6:0:0:4: [sdg] Attached SCSI removable disk
[ 24.842744] wlan1: no IPv6 routers present
[ 696.524104] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
[ 1735.589254] usb 1-1.4: USB disconnect, device number 4
++++++>[ 1735.589457] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 <+++BAD++++
[ 1735.589474] ftdi_sio 1-1.4:1.0: device disconnected

you cannot use :
ttyUSB0 dosen't stay ( connected and disconnected ) !

AxePad do not found ttyUSB0 because do not exist.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
---------------------METHODS----------------------------
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
STEP 1:
-----------
/etc/udev/rules.d/99-axe027.rules
mode permission superuser
open file
overwrite SYSFS by ATTR
ATTR{idProduct}=="bd90", ATTR{idVendor}=="0403", RUN+="/sbin/modprobe -q ftdi_sio product=0xbd90 vendor=0x0403"
save file
reebot linux

~$ lsusb

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 003: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 002 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 002 Device 005: ID 0bda:0152 Realtek Semiconductor Corp. Mass Storage Device
Bus 002 Device 006: ID 0a5c:4502 Broadcom Corp. Keyboard (Boot Interface Subclass)
Bus 002 Device 007: ID 0a5c:4503 Broadcom Corp. Mouse (Boot Interface Subclass)
Bus 002 Device 008: ID 050d:016a Belkin Components Bluetooth Mini Dongle
++++++> Bus 001 Device 003: ID 0403:bd90 Future Technology Devices International, Ltd <++++++++++++

~$ dmesg | tail
[ 239.491246] USB Serial support registered for FTDI USB Serial Device
[ 239.491536] ftdi_sio 1-1.3:1.0: FTDI USB Serial Device converter detected
[ 239.491588] usb 1-1.3: Detected FT232RL
[ 239.491597] usb 1-1.3: Number of endpoints 2
[ 239.491599] usb 1-1.3: Endpoint 1 MaxPacketSize 64
[ 239.491601] usb 1-1.3: Endpoint 2 MaxPacketSize 64
[ 239.491602] usb 1-1.3: Setting MaxPacketSize 64
+++++++++++>[ 239.492096] usb 1-1.3: FTDI USB Serial Device converter now attached to ttyUSB0 <+++++++++++++++
[ 239.492116] usbcore: registered new interface driver ftdi_sio
[ 239.492118] ftdi_sio: v1.6.0:USB FTDI Serial Converters Driver

good : ttyUSB0 stay
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
STEP 2:
-------
the ttyUSBO dynamic created by linux at moment of plug in cable, and stayed during SESSION.
without permission enough for use with AxePad (error 13 : acces denied)

because the permission of ttyUSBO is by default user: root and group: dialout

you should gived permissions curent user by add in this group.

~$ sudo adduser [your user name] dialout

and restart ubuntu

-------RUN FINE ----------