USB card reader worked in 1.05, only partially in 2.10

[mouldy]

Ok, for most part 2.10 works ok, even got it to shut down properly thanks to a suggestion in another thread. However still have this nagging little problem. My generic 23in1 usb card reader worked fine in 1.05. With either a cf card or a Sony memory stick, Pmount found it and I could mount and access either one. In 2.10, Pmount only sees the Sony memory stick. Mut sees the cf card as sdb but wont let me mount it. Card is used in a camera and has dos partition.

I've searched and searched about what changed but came up empty. Any suggestions?

[mouldy]

Ok, this is interesting. I renamed /usr/sbin/pmount in 2.10 and copied old version of pmount from 1.05 to 2.10. This old version of Pmount running on 2.10 now sees the cf card dos partition, but wont mount it.

Geanie wont open two separate instances of itself so hard to compare the scripts. Anybody know how to force geanie to open two separate instances of itself rather than tabs? Or do I have to bring back beaver or TED? I hate software that tries to outguess me without at least giving me the option to turn automated stuff off. Windows wants to do that all the time. Thats the reason I dont do windows.

EDIT: Supposedly the commandline -i option will force geany to open separate instances. It doesnt work. TED it is then.

[GuestToo]

for the version of Geany that comes with Puppy 2.10:

edit /usr/local/bin/defaulttexteditor (right click the "editor" desktop icon, click Open As Text) ... change:

exec geanyshell "$AT"

to:

exec geanyshell -p "$AT"

(the forum does not like the At_sign)

[mouldy]

for the version of Geany that comes with Puppy 2.10:

edit /usr/local/bin/defaulttexteditor (right click the "editor" desktop icon, click Open As Text) ... change:

exec geanyshell "$AT"

to:

exec geanyshell -p "$AT"

(the forum does not like the At_sign)

Nope didnt work, still opens tabs.

[GuestToo]

it works on my machine, running Geany 0.8 on Puppy 2.10

type:

geany --help

-p, --no-pipe don't open files in a running instance, force opening a new instance

[mouldy]

?? Dont know then. I just downloaded and installed bunch editors. Zoinks was only one that did what I wanted. Ted crashed. Tea opened tabs and I didnt even bother looking for commandline argument. Elvis doesnt open box to choose, and when I did it the hardway, it couldnt find the file.


But all that is neither here nor there, I looked at the two pmounts side by side in zoinks and they are too different from each other for me to make heads or tails of at least with just cursory look.

So until i have bunch time on my hands to mull usb in Puppy in more depth, looks like I just have to boot Puppy 1.05 if I want to get files of my cf card.

[GuestToo]

you could probably mount the usb drive from the command line ... and you could make a script to mount it with one click

[mouldy]

mut in 2.10 below

2.10 pmount results below

1.05 pmount running on 2.10 below (the msdos on /dev/sdb1 is it)

1.05 pmount running on 2.10 when I try to mount (it works in 1.05)


So whats the trick to mounting usb in commandline. The obvious tries return "not in /etc/fstab".

[mouldy]

Havent had time to read up on usb yet, but Barry or somebody mentioned command "probedisk" on another non-related thread.



This is best recognition of my 23in1 card reader that I have seen even though I only use CF and MS type cards. How can I make Puppy see and put these into fstab so I can mount them?

[MU]

Simply mount with these commands:

mkdir /mnt/sdb
mount /dev/sdb /mnt/sdb

Mark

[mouldy]

Simply mount with these commands:

mkdir /mnt/sdb
mount /dev/sdb /mnt/sdb

Mark

[MU]

try
mount -t vfat /dev/sdb /mnt/sdb

This tells it, what filesyste to use.
I think CF-cards use vfat, but I'm not shure.

Enter "mount" here to see a description of all options of mount in general:
http://noforum.de/man/

Mark

[MU]

-- sent wice

[mouldy]

I tried with vfat and msdos and both return same invalid argument.

May boot 1.05 and see if I can manually mount cf card in it. Should be able to since pmount can find it there.

[mouldy]

Ok, changed sdb in the command to sdb1 like the pmount from 1.05 sees the cf card. I mounted it but ROX acted weird, it showed the directories on the cf card but when I got to the picture files with the thumbnails nested couple layers down, it crashed. This may be first time I've ever seen ROX crash. I could go in the back door with mtpaint and open a particular pic file so indeed it is mounted.

Ok, must be the thumbnail part of ROX crashing as uXplor showed pic files (no thumbnails of course) and when I clicked on them they opened in mtpaint.

[GuestToo]

pmount says your usb drive is /dev/sdb1 (partitioned) ... so the mount command would be:

mkdir /mnt/sdb1
mount -t vfat /dev/sdb1 /mnt/sdb1

if you want to use the mount point /mnt/sdb1 ... you can use any mount point you like, like /mnt/data or /mnt/zip etc etc etc

/dev/sdb would be used if the usb drive is a "superfloppy" with no partitions

[Gn2]

If a few (personal/biased) musings on above may be tolerated: :

To find out if the device has been detected & status
Plug in run

Code: Select all

tail /var/log/mess*

Please see man tail and look in your /var/log/ folders

Code: Select all

lsusb <or> lspci

gives bus info

Code: Select all

demsg|grep usb (may help)

As does

Code: Select all

cdrecord  -scanbus

Hot-plugging gets tricky > not all F/Systems/devices are automatically probed correctly.
Asides: -NTIM - "vfat" may invoke fat32 minimum-size conventions
Fat12 is bad enough - or why OEMs still sometimes use it
Other flash devices may not 8>( even have F/tables/partitions

Thankfully once the device has been found - we may manually access most.
Many find it less hassle to do as already suggested:
Edit /fstab for (optional) name & mountpoint ~ stating F/System to use (or use "auto-detect")

Without a sub-number sda"1","2" etc indicates the whole device -
which may be incorrect if it contains any F/Sys table data

Why fight it just for sake of "auto-convenience"
Or use automounting then hope it gets cleanly unmounted before removing media-
Esp if normal async writes are pending in background

Since Devfs is now redundant:
Persistent unique-naming under scsi conventions help "re-names" of removeable media devices
The Scsi interface "chain-structure" linking ??? is convoluted/weird.
Esp since devices may be usb -remember the "ide-scsi" for burners ?
Requiring sg/sr/pg modular or better > - compiled in ?

http://sg.torque.net/sg/sg3_utils.html
http://www.die.net/doc/linux/man/man3/aio_write.3.html
http://www.google.ca/search?hl=en&ie=IS ... arch&meta=


HTH