On Mon, Nov 5, 2012 at 1:32 PM, Phoenix Nemo wrote:

Can you use any other flash drives or removable devices? Which display manager do you use, and which file manager?

I get this error several times due to added 'ck-launch-session' to my $HOME/.xinitrc because my display manager have already support this.

Notice that consolekit is no longer supported, and should be removed. To get the equivalent functionality you should just boot with systemd. I don't know if this is relevant to OP's problem though. -t

My son-in-law recently purchased 2 of these & he could not access them on PS3 or my arch desktop. It turned out they were formatted as EXFAT, he re-formatted as NTFS & all was ok for him. What are yours formatted as? Also I have had similar issue's in the past & just re-formatted to FAT & all was ok. On Mon, Nov 05, 2012 at 01:40:21PM +0100, Tom Gundersen wrote:

On Mon, Nov 5, 2012 at 1:32 PM, Phoenix Nemo wrote:

...

Can you use any other flash drives or removable devices? Which display manager do you use, and which file manager?

I get this error several times due to added 'ck-launch-session' to my $HOME/.xinitrc because my display manager have already support this.

Notice that consolekit is no longer supported, and should be removed. To get the equivalent functionality you should just boot with systemd. I don't know if this is relevant to OP's problem though.

-t

On Mon, Nov 05, 2012 at 07:00:43PM +0000, P .NIKOLIC wrote:

On Mon, 5 Nov 2012 17:18:48 +0200 Tom Rand wrote:

...

My son-in-law recently purchased 2 of these & he could not access them on PS3 or my arch desktop. It turned out they were formatted as EXFAT, he re-formatted as NTFS & all was ok for him.

What are yours formatted as?

Also I have had similar issue's in the past & just re-formatted to FAT & all was ok.

Hi Tom .

Been there using the laptop that is not as upto date and completely redid the partition and formatted one of them vfat still the same on this machine but ok on the laptop .

I need to keep them vfat as they are actually for use in the car it takes mp3's on usb drives (max 4Gb) and only read vfat (and only mp3 not ogg)

Pete .

-- Linux 7-of-9 3.6.5-1-ARCH #1 SMP PREEMPT Wed Oct 31 20:57:39 CET 2012 x86_64 GNU/Linux

I take it you tried all ports on this machine. (apologies for the top post earlier) the only other possible thing i could think of which might cause this would be that your mobo is set to use usb 3 only or one of the other versions I know some mobo's can be set to one of the 3. Either that or some of the ports are not initialised. plug the drive in run lsusb this at least will tell you if the drive is visible &/or if the usb port is initialised.

On Mon, 5 Nov 2012 19:00:43 +0000 "P .NIKOLIC" wrote:

On Mon, 5 Nov 2012 17:18:48 +0200 Tom Rand wrote:

...

My son-in-law recently purchased 2 of these & he could not access them on PS3 or my arch desktop. It turned out they were formatted as EXFAT, he re-formatted as NTFS & all was ok for him.

What are yours formatted as?

Also I have had similar issue's in the past & just re-formatted to FAT & all was ok.

Hi Tom .

Been there using the laptop that is not as upto date and completely redid the partition and formatted one of them vfat still the same on this machine but ok on the laptop .

I need to keep them vfat as they are actually for use in the car it takes mp3's on usb drives (max 4Gb) and only read vfat (and only mp3 not ogg)

Pete .

Replying to ones self .. as in the previous mail Now Solved Pete -- Linux 7-of-9 3.6.5-1-ARCH #1 SMP PREEMPT Wed Oct 31 20:57:39 CET 2012 x86_64 GNU/Linux

On Mon, Nov 5, 2012 at 7:22 PM, P .NIKOLIC wrote:

This is possible ..from what i have been reading not too sure if i have Systemd running or not the system is fully updated .

You will not have been converted over automatically. See the wiki for how to do that.

How do i check to see if it is systemd or not sorry to sound fick but got lots of other things on my mind as well right now ..

I guess running "systemctl" should tell you? If you are using systemd it will list a lot of running services. Otherwise I assume it will return a dbus error (but I haven't tried that myself, so only a guess). -t

On 6 November 2012 02:50, Squall Lionheart wrote:

...

I guess running "systemctl" should tell you? If you are using systemd it will list a lot of running services. Otherwise I assume it will return a dbus error (but I haven't tried that myself, so only a guess).

FYI, I haven't updated to systemd yet and the error when running systemctl reads: Failed to get D-Bus connection: No connection to service manager.

Yes, that is correct behaviour, and means you're not running systemd. I believe a valid logind session needs to exist for these to work, and that means booting with systemd. -- GPG/PGP ID: C0711BF1

On Mon, 5 Nov 2012 19:42:20 +0100 Tom Gundersen wrote:

On Mon, Nov 5, 2012 at 7:22 PM, P .NIKOLIC wrote:

...

This is possible ..from what i have been reading not too sure if i have Systemd running or not the system is fully updated .

You will not have been converted over automatically. See the wiki for how to do that.

...

How do i check to see if it is systemd or not sorry to sound fick but got lots of other things on my mind as well right now ..

I guess running "systemctl" should tell you? If you are using systemd it will list a lot of running services. Otherwise I assume it will return a dbus error (but I haven't tried that myself, so only a guess).

-t

Hi Tom .. Right so a reply of Failed to get D-Bus connection: No connection to service manager i take it means no I will start a new thread i think to get systemd running .. Pete . -- Linux 7-of-9 3.6.5-1-ARCH #1 SMP PREEMPT Wed Oct 31 20:57:39 CET 2012 x86_64 GNU/Linux

Am Montag, den 05.11.2012, 18:22 +0000 schrieb P .NIKOLIC:

How do i check to see if it is systemd or not

$ printf "%d" `systemd-notify --booted` man systemd-notify: “[…] --booted Returns 0 if the system was booted up with systemd, non-zero otherwise. […]”

On Mon, 5 Nov 2012 15:03:52 -0500 Dave Reisner wrote:

On Mon, Nov 05, 2012 at 08:22:33PM +0100, coderkun wrote:

...

Am Montag, den 05.11.2012, 18:22 +0000 schrieb P .NIKOLIC:

...

How do i check to see if it is systemd or not

$ printf "%d" `systemd-notify --booted`

systemd-notify doesn't print anything. If you really want to print something:

$ systemd-notify --booted && echo "booted on systemd"

or

$ systemd-notify --booted; echo $?

...

man systemd-notify: “[…] --booted Returns 0 if the system was booted up with systemd, non-zero otherwise. […]”

Note the "returns", not "prints".

d

Hi All .. Well after a little messing now on systemd , And the strange thing is that now ALL the usb flash drives i have work not just the older ones but the new SanDisk as well Explain that one someone . I think this can be classed as solved right now thanks all Pete . -- Linux 7-of-9 3.6.5-1-ARCH #1 SMP PREEMPT Wed Oct 31 20:57:39 CET 2012 x86_64 GNU/Linux

On Tue, 6 Nov 2012 19:14:09 -0500 Todd Carnes wrote:

On Tue, 6 Nov 2012 07:58:27 +0000 "P .NIKOLIC" wrote:

...

Hi All ..

Well after a little messing now on systemd , And the strange thing is that now ALL the usb flash drives i have work not just the older ones but the new SanDisk as well Explain that one someone .

I think this can be classed as solved right now thanks all

Pete .

But I don't get it. What exactly did you do to solve it?

Your solution might help others in the future.

Well If i knew Exactly i would tell cus it was a real pita it seems it may have been some outlandish permissions think as i say the only drives i could not access were these new SanDisk ones . The problem no longer exists by switching to systemd it went away on this machine but on the laptop Arch linux as well they work perfectly but i do not keep the laptop as up to date i need that to just work . Cheers Pete . -- Linux 7-of-9 3.6.6-1-ARCH #1 SMP PREEMPT Mon Nov 5 11:57:22 CET 2012 x86_64 GNU/Linux