Project Home
Project Home
Documents
Documents
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - USB memory stick not mounted on x86 6.4.1: (4 Items)
   
USB memory stick not mounted on x86 6.4.1  
It seems there are two types of memory sticks. The one type will be visible as /dev/umass0t?? the other type as /dev/
hd1t6 (example). As I understand a flash drive is mounted as /dev/hd? and then its partitions.

If a memory stick is inserted and the device /dev/umass0 is created, the memory stick will automatically be mounted 
under /fs/usb0, no problem.

If a memory stick(a flash drive)  is inserted and the device /dev/hd1t6, as an example, is created, the memory stick is 
not automatically mounted.

If however QNX boot up with the flash drive inserted (/dev/hd1), then the memory stick is mounted as /fs/hd1xxxx. If the
 memory stick is now removed and inserted, then the memory stick mounts automatically.

We have to write software to handle all this because the customer will arrive with any type of USB memory stick and I 
want the system to respond in a consistent manner.

To add to the confusion, it seems the way the device is created depends on the motherboard and the BIOS. On one 
motherboard, the memory stick is mounted as /dev/hd1 and on another motherboard as /dev/umass0.

Any information to understand the issues involved will be appreciated.
Thomas Luetzel/EHPCM/DE is not in the office. [virus checked]  
Ich werde ab  05.06.2010 nicht im Büro sein. Ich kehre zurück am
18.06.2010.

I will answer this mail after my return.

Kind Regards,
Thomas Luetzel



_________________________________________________________________________


Endress+Hauser GmbH+Co. KG
Amtsgericht : Freiburg i.Br. HRA 670225
Sitz der Gesellschaft : Maulburg
Persönlich haftender Gesellschafter : Endress+Hauser Verwaltungs-GmbH
Sitz der Gesellschaft : Maulburg
Amtsgericht : Freiburg i.Br. HRB 670222
Geschäftsführer : Matthias Altendorf


Endress+Hauser GmbH+Co. KG
County Court : Freiburg i.Br. HRA 670225
Registered Office : Maulburg
Generell Partner : Endress+Hauser Verwaltungs-GmbH
Registered Office : Maulburg
County Court : Freiburg i.Br. HRB 670222
General Manager : Matthias Altendorf

__________________________________________________________________________

Disclaimer:

The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you receive
this in error, please contact the sender and delete the material from any
computer.

__________________________________________________________________________

http://www.endress.com/
Re: USB memory stick not mounted on x86 6.4.1  
On Wed, 9 Jun 2010, Francois Joubert wrote:

> It seems there are two types of memory sticks. The one type will be visible
> as /dev/umass0t?? the other type as /dev/hd1t6 (example). As I understand a
> flash drive is mounted as /dev/hd? and then its partitions.

I think this is more dependent on when the stick is inserted. There are still
two versions of usb enumerator used in 6.4.1 on the selfhosted default installation.

>
> If a memory stick is inserted and the device /dev/umass0 is created, the
> memory stick will automatically be mounted under /fs/usb0, no problem.
>
> If a memory stick(a flash drive)  is inserted and the device /dev/hd1t6, as
> an example, is created, the memory stick is not automatically mounted.
>
> If however QNX boot up with the flash drive inserted (/dev/hd1), then the
> memory stick is mounted as /fs/hd1xxxx. If the memory stick is now removed
> and inserted, then the memory stick mounts automatically.
>
> We have to write software to handle all this because the customer will arrive
> with any type of USB memory stick and I want the system to respond in a
> consistent manner.
>
> To add to the confusion, it seems the way the device is created depends on
> the motherboard and the BIOS. On one motherboard, the memory stick is mounted
> as /dev/hd1 and on another motherboard as /dev/umass0.

Compare the args to devb-umass in the two cases and you'll see that in the
second case specific device names are passed in (name=umass) where as in the
first case the defaults are used which is the hd# convention.

You want to look at the new device enumerators as those are supported going
forward. (enum-devices and enum-usb) Also check out the docs on mcd which
should handle mounting of partitioned and non-partitions memory sticks.

Hope this helps a bit.

Peter
Thomas Luetzel/EHPCM/DE is not in the office. [virus checked]  
Ich werde ab  05.06.2010 nicht im Büro sein. Ich kehre zurück am
18.06.2010.

I will answer this mail after my return.

Kind Regards,
Thomas Luetzel



_________________________________________________________________________


Endress+Hauser GmbH+Co. KG
Amtsgericht : Freiburg i.Br. HRA 670225
Sitz der Gesellschaft : Maulburg
Persönlich haftender Gesellschafter : Endress+Hauser Verwaltungs-GmbH
Sitz der Gesellschaft : Maulburg
Amtsgericht : Freiburg i.Br. HRB 670222
Geschäftsführer : Matthias Altendorf


Endress+Hauser GmbH+Co. KG
County Court : Freiburg i.Br. HRA 670225
Registered Office : Maulburg
Generell Partner : Endress+Hauser Verwaltungs-GmbH
Registered Office : Maulburg
County Court : Freiburg i.Br. HRB 670222
General Manager : Matthias Altendorf

__________________________________________________________________________

Disclaimer:

The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you receive
this in error, please contact the sender and delete the material from any
computer.

__________________________________________________________________________

http://www.endress.com/