comment to F23 Final RC10 - still card reader problem

[Joerg Lechner]

Hi,
i have tried now several apps, some are still not ok, this may be the job of the maintainers of these apps. One thing still disturbs me. On my Acer laptop the card reader is a Realtek PCIE card reader. When I open the file menue, I can not see the flash card inserted into the card reader, therefore I can not eject the card. But the fotos can be downloaded i.e. with Shotwell. Does anyone else have similar card reader problems in F23?
Kind regards

[Richard Ryniker]

I think you may be the victim of GNOME's "Do what you maybe probably
want." attitude.  This is something you might be able to configure to
your taste, given sufficient knowledge about what specifications to
change.

I have a Lenovo machine with a Realtec card reader:

[ryniker@lenovo ~]$ lspci | grep Card
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5209 PCI Express Card Reader (rev 01)

This is known as /dev/mmcblk0, and when I insert a SD card with file
systems on a couple of partitions:

[root@lenovo ryniker]# blkid | grep mmc
/dev/mmcblk0: PTUUID="ba2edfb9" PTTYPE="dos"
/dev/mmcblk0p1: SEC_TYPE="msdos" LABEL="boot" UUID="74BD-74CF" TYPE="vfat" PARTUUID="ba2edfb9-01"
/dev/mmcblk0p2: UUID="ec2aa3d2-eee7-454e-8260-d145df5ddcba" TYPE="ext4" PARTUUID="ba2edfb9-02"

GNOME kindly mounts these under /run/media:

[ryniker@lenovo ~]$ mount | grep mmc
/dev/mmcblk0p1 on /run/media/ryniker/boot type vfat (rw,nosuid,nodev,relatime,uid=501,gid=501,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,showexec,utf8,flush,errors=remount-ro,uhelper=udisks2)
/dev/mmcblk0p2 on /run/media/ryniker/ec2aa3d2-eee7-454e-8260-d145df5ddcba type ext4 (rw,nosuid,nodev,relatime,seclabel,data=ordered,uhelper=udisks2)

which I find sometimes helpful, sometimes not.  In any case, these are
"user" mounts.  I have not explored what happens when multiple users are
logged in when a card is loaded.  If I do not want these file systems
mounted, I can:

[ryniker@lenovo ~]$ umount /dev/mmcblk0p1
[ryniker@lenovo ~]$ umount /dev/mmcblk0p2

and then remove the SD card when umount completes (this may take a while
if a lot of data must be flushed to the media).

Often, I want to write a new image onto a SD card (dd of=/dev/mmcblk0).
If I do not first umount these automatically-mounted file systems, dd
output is buffered in memory - dd may report a transfer rate of one
gigabyte per second - and I am exceedingly careful to wait until I
observe activity to the SD card has ended before I remove it (without any
umount operations, which I fear may corrupt the image I just wrote.)

The automatic behavior may be right for most users.  I have enough
experience to (usually) avoid the pits, and recognize what has gone wrong
when I stumble into one.

This Lenovo machine also has a reboot problem similar to one you
reported.  Windows reboots successfully, but Fedora does not.  Fedora
shuts down, I see the Lenovo splash screen, but no boot.  I must force
power off, then wait through a ten-second "Power Saving" countdown
displayed on-screen before actual power off, then I can boot
successfully.  Peculiarity of the Lenovo hardware, I suppose, and I just
live with it.

[Joerg Lechner]

Hi,
a further investigation with the internal card reader of my Acer E15 E5-571G with lspci brought up amongst other well defined components:
"01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5287 (rev 01)"
I think this could be the Realtek card reader of the laptop?
Is it possible that "unassigned class" is the reason why I don't find this laptop internal card reader in the file list on the left hand side of the Gnome file display?
In lshw I also don't find the laptop internal card reader (SD card is inserted), even when I can see the SD card in /run/media/joerg/  (my user name is joerg).
Is this F23/Gnome special? Or have I to live with this behaviour also in F24,F25,....?
Kind Regards

-----Ursprüngliche Mitteilung----- 
Von: Richard Ryniker 
An: For testing and quality assurance of Fedora releases 
Cc: Joerg Lechner 
Verschickt: Sa, 31 Okt 2015 4:34 pm
Betreff: Re: comment to F23 Final RC10 - still card reader problem

I think you may be the victim of GNOME's "Do what you maybe probably
want."
attitude.  This is something you might be able to configure to
your taste,
given sufficient knowledge about what specifications to
change.

I have a
Lenovo machine with a Realtec card reader:

[ryniker@lenovo ~]$ lspci | grep
Card
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5209
PCI Express Card Reader (rev 01)

This is known as /dev/mmcblk0, and when I
insert a SD card with file
systems on a couple of partitions:

[root@lenovo
ryniker]# blkid | grep mmc
/dev/mmcblk0: PTUUID="ba2edfb9"
PTTYPE="dos"
/dev/mmcblk0p1: SEC_TYPE="msdos" LABEL="boot" UUID="74BD-74CF"
TYPE="vfat" PARTUUID="ba2edfb9-01"
/dev/mmcblk0p2:
UUID="ec2aa3d2-eee7-454e-8260-d145df5ddcba" TYPE="ext4"
PARTUUID="ba2edfb9-02"

GNOME kindly mounts these under
/run/media:

[ryniker@lenovo ~]$ mount | grep mmc
/dev/mmcblk0p1 on
/run/media/ryniker/boot type vfat
(rw,nosuid,nodev,relatime,uid=501,gid=501,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,showexec,utf8,flush,errors=remount-ro,uhelper=udisks2)
/dev/mmcblk0p2
on /run/media/ryniker/ec2aa3d2-eee7-454e-8260-d145df5ddcba type ext4
(rw,nosuid,nodev,relatime,seclabel,data=ordered,uhelper=udisks2)

which I find
sometimes helpful, sometimes not.  In any case, these are
"user" mounts.  I
have not explored what happens when multiple users are
logged in when a card is
loaded.  If I do not want these file systems
mounted, I can:

[ryniker@lenovo
~]$ umount /dev/mmcblk0p1
[ryniker@lenovo ~]$ umount /dev/mmcblk0p2

and then
remove the SD card when umount completes (this may take a while
if a lot of
data must be flushed to the media).

Often, I want to write a new image onto a
SD card (dd of=/dev/mmcblk0).
If I do not first umount these
automatically-mounted file systems, dd
output is buffered in memory - dd may
report a transfer rate of one
gigabyte per second - and I am exceedingly
careful to wait until I
observe activity to the SD card has ended before I
remove it (without any
umount operations, which I fear may corrupt the image I
just wrote.)

The automatic behavior may be right for most users.  I have
enough
experience to (usually) avoid the pits, and recognize what has gone
wrong
when I stumble into one.

This Lenovo machine also has a reboot problem
similar to one you
reported.  Windows reboots successfully, but Fedora does
not.  Fedora
shuts down, I see the Lenovo splash screen, but no boot.  I must
force
power off, then wait through a ten-second "Power Saving"
countdown
displayed on-screen before actual power off, then I can
boot
successfully.  Peculiarity of the Lenovo hardware, I suppose, and I
just
live with it.

[Joerg Lechner]

Hi,
I have just found that this problem of a Realtek Card reader seems to be more generic in Linux, I found     https://bugzilla.kernel.org/show_bug.cgi?id=57061
which talks about  rtsx_pci and rts_bpp. Kernel is really not my area - I am more user, and a little bit testing. Does anyone know the corresponding modules in F23, because this can be the answer of my card reader problem
Kind regards

-----Ursprüngliche Mitteilung----- 
Von: Joerg Lechner 
An: test 
Verschickt: Mo, 2 Nov 2015 7:50 am
Betreff: Re: comment to F23 Final RC10 - still card reader problem

Hi,
a further investigation with the internal card reader of my Acer E15
E5-571G with lspci brought up amongst other well defined components:
"01:00.0
Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5287 (rev
01)"
I think this could be the Realtek card reader of the laptop?
Is it
possible that "unassigned class" is the reason why I don't find this laptop
internal card reader in the file list on the left hand side of the Gnome file
display?
In lshw I also don't find the laptop internal card reader (SD card is
inserted), even when I can see the SD card in /run/media/joerg/  (my user name
is joerg).
Is this F23/Gnome special? Or have I to live with this behaviour
also in F24,F25,....?
Kind Regards

-----Ursprüngliche Mitteilung-----

Von: Richard Ryniker 
An: For testing and quality
assurance of Fedora releases 
Cc: Joerg Lechner

Verschickt: Sa, 31 Okt 2015 4:34 pm
Betreff: Re: comment
to F23 Final RC10 - still card reader problem

I think you may be the victim
of GNOME's "Do what you maybe probably
want."
attitude.  This is something you
might be able to configure to
your taste,
given sufficient knowledge about
what specifications to
change.

I have a
Lenovo machine with a Realtec card
reader:

[ryniker@lenovo ~]$ lspci | grep
Card
02:00.0 Unassigned class
[ff00]: Realtek Semiconductor Co., Ltd. RTS5209
PCI Express Card Reader (rev
01)

This is known as /dev/mmcblk0, and when I
insert a SD card with
file
systems on a couple of partitions:

[root@lenovo
ryniker]# blkid | grep
mmc
/dev/mmcblk0: PTUUID="ba2edfb9"
PTTYPE="dos"
/dev/mmcblk0p1:
SEC_TYPE="msdos" LABEL="boot" UUID="74BD-74CF"
TYPE="vfat"
PARTUUID="ba2edfb9-01"
/dev/mmcblk0p2:
UUID="ec2aa3d2-eee7-454e-8260-d145df5ddcba"
TYPE="ext4"
PARTUUID="ba2edfb9-02"

GNOME kindly mounts these
under
/run/media:

[ryniker@lenovo ~]$ mount | grep mmc
/dev/mmcblk0p1
on
/run/media/ryniker/boot type
vfat
(rw,nosuid,nodev,relatime,uid=501,gid=501,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,showexec,utf8,flush,errors=remount-ro,uhelper=udisks2)
/dev/mmcblk0p2
on
/run/media/ryniker/ec2aa3d2-eee7-454e-8260-d145df5ddcba type
ext4
(rw,nosuid,nodev,relatime,seclabel,data=ordered,uhelper=udisks2)

which
I find
sometimes helpful, sometimes not.  In any case, these are
"user"
mounts.  I
have not explored what happens when multiple users are
logged in
when a card is
loaded.  If I do not want these file systems
mounted, I
can:

[ryniker@lenovo
~]$ umount /dev/mmcblk0p1
[ryniker@lenovo ~]$ umount
/dev/mmcblk0p2

and then
remove the SD card when umount completes (this may
take a while
if a lot of
data must be flushed to the media).

Often, I want
to write a new image onto a
SD card (dd of=/dev/mmcblk0).
If I do not first
umount these
automatically-mounted file systems, dd
output is buffered in
memory - dd may
report a transfer rate of one
gigabyte per second - and I am
exceedingly
careful to wait until I
observe activity to the SD card has ended
before I
remove it (without any
umount operations, which I fear may corrupt
the image I
just wrote.)

The automatic behavior may be right for most users.
I have
enough
experience to (usually) avoid the pits, and recognize what has
gone
wrong
when I stumble into one.

This Lenovo machine also has a reboot
problem
similar to one you
reported.  Windows reboots successfully, but Fedora
does
not.  Fedora
shuts down, I see the Lenovo splash screen, but no boot.  I
must
force
power off, then wait through a ten-second "Power
Saving"
countdown
displayed on-screen before actual power off, then I
can
boot
successfully.  Peculiarity of the Lenovo hardware, I suppose, and
I
just
live with it.