Re: [arch-general] Arch linux doesn't recognises micro SD card
On Thu, Feb 26, 2015 at 07:58:13PM +0100, Csányi Pál wrote: > > 1: Your SD card is damaged / broken. To test this, try it in > > a known-working reader. Note that Windows will not understand Linux / > > RPi partitions (but should be able to at least see the boot partition). > > I can mount it's first partition, that with FAT32 type filesystem. > I can't only format it's second partition, with ex4 type filesystem. > > Still does it mean that the uSD card is damaged? If when you attempt to do an operation on it, you get IO errors in dmesg, yes, that means your card OR card reader OR card adapter is broken. If it is partition-specific, I would assume that it is the card that is broken. --Sean
Re: [arch-general] Arch linux doesn't recognises micro SD card
On 26/02/15 at 06:41pm, Csányi Pál wrote:
2015-02-25 23:58 GMT+01:00 Aaron Caffrey :
Install udisks, udisks2.
Create /etc/polkit-1/rules.d/10-enable-mount.rules
polkit.addRule(function(action, subject) {
if (action.id == "org.freedesktop.udisks2.filesystem-mount-system"
&& subject.isInGroup("storage")) {
return polkit.Result.YES;
}
});
I did follow your advice and did create this config file.
I have installed udisks and udisks2.
I can follow these steps:
http://archlinuxarm.org/platforms/armv6/raspberry-pi
to the step 4. where the following command:
mkfs.ext4 /dev/sdX2
can't be completed successfully, because after I run it, I can't mount
the new second partition formatted to have ext4 type filesystem.
I tried these steps by using Gparted too, but at this step Gparted
can't read partitions from the during read on
/dev/mmcblk0
Gparted gives the error message:
I/O error during read on /dev/mmcblk0
What can I do to solve this problem?
--
Regards from Pal
If my memory serves me correctly, you said that your card is read in
Windows.
What I would suggest you is to format it in Windows, but from the
command prompt (start menu, type "cmd" or just browse accessories and
start "command prompt"):
In the terminal/command prompt type:
diskpart.exe
list disk
select disk X
detail disk
clean
create partition primary
active
format fs=fat32 quick
assign
exit
Re: [arch-general] Arch linux doesn't recognises micro SD card
On 26/02/15 at 07:31pm, Jens Adam wrote: Wed, 25 Feb 2015 11:36:59 +0100 Csányi Pál : mmcblk0: error -84 transferring data, sector 7, nr 1, cmd response 0x900, card status 0x0 Buffer I/O error on dev mmcblk0, logical block 0, async page read This clearly indicates a hardware/kernel problem, so I don't know why people are suggesting to paste random config snippets that won't solve anything. Simple googling will produce dozens of similar problems, most without solution. My guess: Your card reader (which one? lspci/lsusb/dmesg? laptop type and age?) or its firmware is simply too old to recognize the card. See https://en.wikipedia.org/wiki/Secure_Digital#Compatibility --byte Because I had exactly the same issue with different kernels, one kernel will read my micro sd card and others wont. The solution which I posted has helped me long time ago, that is why I shared it. What is the purpose of this mailing list if we can't help each other ?
Re: [arch-general] Arch linux doesn't recognises micro SD card
Op 26 feb. 2015 19:58 schreef "Csányi Pál" : > > 2015-02-26 19:25 GMT+01:00 Sean Greenslade : > > On Thu, Feb 26, 2015 at 06:41:24PM +0100, Csányi Pál wrote: > >> I tried these steps by using Gparted too, but at this step Gparted > >> can't read partitions from the during read on > >> > >> /dev/mmcblk0 > >> > >> Gparted gives the error message: > >> I/O error during read on /dev/mmcblk0 > >> > >> What can I do to solve this problem? > > > > Your hardware has issues, and I don't think any software will fix it. My > > guess is that the issue is in one of three places: > > > > 1: Your SD card is damaged / broken. To test this, try it in > > a known-working reader. Note that Windows will not understand Linux / > > RPi partitions (but should be able to at least see the boot partition). > > I can mount it's first partition, that with FAT32 type filesystem. > I can't only format it's second partition, with ex4 type filesystem. > > Still does it mean that the uSD card is damaged? > > > 2. If you're using a microSD to SD adapter, I've seen plenty of those be > > flaky and crappy. Try a different adapter, or get a reader that supports > > uSD directly. > > Yes, I'm using a microSD card to SD adapter. I shall try another brand > of SD adapter, that I have. > > > 3. The reader is broken. Since it's the built-in one on the laptop, the > > only way to test this is to try a different card / try on a different OS > > (live boot USB drives are useful for this). > > I shall try that too. One thing I ran into was the difference between sd versions; sdhc cards wont work in an (standard) sd reader. I don't know how to check the reader from Linux, but it's probably in the hardware specs. Mvg, Guus
Re: [arch-general] Arch linux doesn't recognises micro SD card
2015-02-26 19:25 GMT+01:00 Sean Greenslade : > On Thu, Feb 26, 2015 at 06:41:24PM +0100, Csányi Pál wrote: >> I tried these steps by using Gparted too, but at this step Gparted >> can't read partitions from the during read on >> >> /dev/mmcblk0 >> >> Gparted gives the error message: >> I/O error during read on /dev/mmcblk0 >> >> What can I do to solve this problem? > > Your hardware has issues, and I don't think any software will fix it. My > guess is that the issue is in one of three places: > > 1: Your SD card is damaged / broken. To test this, try it in > a known-working reader. Note that Windows will not understand Linux / > RPi partitions (but should be able to at least see the boot partition). I can mount it's first partition, that with FAT32 type filesystem. I can't only format it's second partition, with ex4 type filesystem. Still does it mean that the uSD card is damaged? > 2. If you're using a microSD to SD adapter, I've seen plenty of those be > flaky and crappy. Try a different adapter, or get a reader that supports > uSD directly. Yes, I'm using a microSD card to SD adapter. I shall try another brand of SD adapter, that I have. > 3. The reader is broken. Since it's the built-in one on the laptop, the > only way to test this is to try a different card / try on a different OS > (live boot USB drives are useful for this). I shall try that too. > In any case, seeing IO errors in dmesg means that there are hardware > problems. Udisk will not in any way solve those, and is not needed for > imaging SD cards for the Pi. If your edit to the polkit config broke > your login, undo it. I did remove the configuration file, and did remove udisks; I have now installed udisks2 only. -- Regards from Pal
Re: [arch-general] Arch linux doesn't recognises micro SD card
Wed, 25 Feb 2015 11:36:59 +0100 Csányi Pál : > mmcblk0: error -84 transferring data, sector 7, nr 1, cmd response > 0x900, card status 0x0 > Buffer I/O error on dev mmcblk0, logical block 0, async page read This clearly indicates a hardware/kernel problem, so I don't know why people are suggesting to paste random config snippets that won't solve anything. Simple googling will produce dozens of similar problems, most without solution. My guess: Your card reader (which one? lspci/lsusb/dmesg? laptop type and age?) or its firmware is simply too old to recognize the card. See https://en.wikipedia.org/wiki/Secure_Digital#Compatibility --byte pgpVKbSmq9slk.pgp Description: Digitale Signatur von OpenPGP
Re: [arch-general] Arch linux doesn't recognises micro SD card
On Thu, Feb 26, 2015 at 06:41:24PM +0100, Csányi Pál wrote: > I tried these steps by using Gparted too, but at this step Gparted > can't read partitions from the during read on > > /dev/mmcblk0 > > Gparted gives the error message: > I/O error during read on /dev/mmcblk0 > > What can I do to solve this problem? Your hardware has issues, and I don't think any software will fix it. My guess is that the issue is in one of three places: 1: Your SD card is damaged / broken. To test this, try it in a known-working reader. Note that Windows will not understand Linux / RPi partitions (but should be able to at least see the boot partition). 2. If you're using a microSD to SD adapter, I've seen plenty of those be flaky and crappy. Try a different adapter, or get a reader that supports uSD directly. 3. The reader is broken. Since it's the built-in one on the laptop, the only way to test this is to try a different card / try on a different OS (live boot USB drives are useful for this). In any case, seeing IO errors in dmesg means that there are hardware problems. Udisk will not in any way solve those, and is not needed for imaging SD cards for the Pi. If your edit to the polkit config broke your login, undo it. --Sean
Re: [arch-general] Arch linux doesn't recognises micro SD card
2015-02-25 23:58 GMT+01:00 Aaron Caffrey :
> Install udisks, udisks2.
> Create /etc/polkit-1/rules.d/10-enable-mount.rules
>
> polkit.addRule(function(action, subject) {
>if (action.id == "org.freedesktop.udisks2.filesystem-mount-system"
>&& subject.isInGroup("storage")) {
>return polkit.Result.YES;
>}
>});
After I created this file and try to reboot with microSD card left
inserted in the card reader, I can't even login into my system. Why?
--
Regards from Pal
Re: [arch-general] Arch linux doesn't recognises micro SD card
2015-02-25 23:58 GMT+01:00 Aaron Caffrey :
> Install udisks, udisks2.
> Create /etc/polkit-1/rules.d/10-enable-mount.rules
>
> polkit.addRule(function(action, subject) {
>if (action.id == "org.freedesktop.udisks2.filesystem-mount-system"
>&& subject.isInGroup("storage")) {
>return polkit.Result.YES;
>}
>});
I did follow your advice and did create this config file.
I have installed udisks and udisks2.
I can follow these steps:
http://archlinuxarm.org/platforms/armv6/raspberry-pi
to the step 4. where the following command:
mkfs.ext4 /dev/sdX2
can't be completed successfully, because after I run it, I can't mount
the new second partition formatted to have ext4 type filesystem.
I tried these steps by using Gparted too, but at this step Gparted
can't read partitions from the during read on
/dev/mmcblk0
Gparted gives the error message:
I/O error during read on /dev/mmcblk0
What can I do to solve this problem?
--
Regards from Pal
Re: [arch-general] LightDM GTK+ Greeter 2.0.0
On Thu, Feb 26, 2015 at 7:15 AM, Pablo Lezaeta Reyes wrote: > On 02/25/2015 04:33 PM, Pablo Lezaeta Reyes wrote: > >>>* Hi all, > *>>* Version 2.0.0 of the LightDM GTK greeter was released about week > ago. > *>>>* This release drops GTK2 support. > **> That's ironic, Xfce recommend lightdm as DM for the gtk2 theme, > and the > *>*> upcomimng xfce-gtk-engine 3.1 drop gtk3 support. > *>*> > *> > >From what I saw, it didn't drop it. It just disabled it by default, which > >makes sense given that the desktop is GTK+2 only and they don't want to > >unnecessary pull in the gtk+3 dep only for the engine. > > > 3.1.0 taged http://git.xfce.org/xfce/gtk-xfce-engine/tree/NEWS > > verbatim from the news: "Gtk+-3 support has been stopped" > > I asume they keep it but they stop supporting so I think unles a patch > that fix all the themes emerge wldly, will be better drop xfce3-gtk-engine > or the entire xfce-gtk-engine, but that mostly prove that they not > support gtk3, drop gtk2-greeter will render without a wai to use a gtk2 > only > environment since lxdm is mostly no-more-maintained and is better have a > greeter > than a binary unsupported. > > Also xfce4 recomend greybird as theme for xfce if someone need a gtk2-gtk3 > theme > > > >>>* Therefore I propose to rename the current "lightdm-gtk3-greeter" into > *>>>* "lightdm-gtk-greeter" and drop the legacy "lightdm-gtk2-greeter" to > AUR. > *>*> looking oxygen keep the gtk3 in AUR gtk3 only themes tend to use gtk3 > and > *>*> gtk2 only thend to use gtk or gtk2, I will preffer keep the 3 in the > name. > *>>*> I could keep "lightdm-gtk2-greeter" around for a while in > [community] if > *>>*> some people want me to (I'm thinking people using MATE for example, > *>>*> but it's going towards GTK3 anyway), but keep in mind that you can > use > *>>>* LXDM instead if you really need a GTK2 display manager. > *>*> Or Xfce4 users, the upcoming xfce4 release is gtk2, and only after > that the > *>*> migration to gtk3 will start. > *>*> so a gtk2-greeter will be apreciated until xfce drop gtk2, and dont > forget > *>*> that LXDM is now presumably unmaintained or in low maintainance since > they > *>*> migrate to QT > *>*> If there aren't any objections by the end of the week, I'll > proceed with my > *>>*> proposal. > **> Me > *>*> > *>>>* Cheers, > *>> > > tldr; I will go for keep gtk2-greeter for xfce4 user since lxdm is > semi-unmaintained and better a unmaintained theme that a > binary. > someone know if slim keep working with systemd, last time was buggy > or not start or not let thing start at all (like logind) > > -- > *Pablo Lezaeta* > LXDM is a different story because AFAIK it hasn't been officially abandonned, whereas the LightDM GTK2 greeter has, meaning I essentially become upstream if I continue to package it. Anyone is free to keep maintining it in AUR though, it won't be lost into oblivion. Also, as Ralf mentioned, even for a GTK2 desktop, the GTK3 greeter will work just fine if you can live with a few more megabytes. As for the change of name, we always try to follow upstream's naming, the GTK2 drop is a good opportunity to abide by that. FTR nearly all other distros have had a single "lightdm-gtk-greeter" package for a while now, providing only the GTK3 greeter even when GTK2 was still an option. Since a lot less people than I expected seem to object, I pushed 2.0.0 in [community-testing] for now, please give it a spin. Cheers, -- Maxime
Re: [arch-general] LightDM GTK+ Greeter 2.0.0
On Wed, Feb 25, 2015 at 4:55 PM, Armin K. wrote: >> gtk3 already dropped support for theme engines, so fixing the xfce gtk3 >> engine would be wasted effort. > > No, they did not, that would be a feature for GTK+4. They just discourage > people > from using it and they keep telling them to just use css. I suppose you meant > that gnome-themes-standard dropped the gtk+3 engine and you are right, simply > because Adwaita doesn't require it anymore. Yeah, they did. GTK+ 3.15.0 and newer does not load theming engines anymore. https://git.gnome.org/browse/gtk+/tree/NEWS#n517 https://git.gnome.org/browse/gtk+/commit/?id=4d9d655b4efe9fd23ad18449d3e45fb8cd4d9cf0
Re: [arch-general] LightDM GTK+ Greeter 2.0.0
On Thu, 26 Feb 2015 11:32:13 +, Richard Ullger wrote: >I was interested in this thread because I was thinking of trying >lightdm I prefer an environment, IOW a window manager and applications based on GTK2, but I'm using lightdm with the GTK3 greeter and don't understand why there should be a problem doing this. Once I used lightdm without an additional greeter, perhaps it's impossible nowadays, I dunno. The greeter has absolutely no impact to an user sessions. Regards, Ralf -- "We believe in the synergies that develop from several relations. So, livestock, crop production, energy production, and aquaculture energize each other." - http://www.songhai.org/index.php/en/qui-sommes-nous-en/vision-mission-en
Re: [arch-general] LightDM GTK+ Greeter 2.0.0
On 26/02/15 06:15, Pablo Lezaeta Reyes wrote: > On 02/25/2015 04:33 PM, Pablo Lezaeta Reyes wrote: * Hi all, > *>>* Version 2.0.0 of the LightDM GTK greeter was released about week ago. > *>>>* This release drops GTK2 support. > **> That's ironic, Xfce recommend lightdm as DM for the gtk2 theme, and > the > *>*> upcomimng xfce-gtk-engine 3.1 drop gtk3 support. > *>*> > *> >>From what I saw, it didn't drop it. It just disabled it by default, which >> makes sense given that the desktop is GTK+2 only and they don't want to >> unnecessary pull in the gtk+3 dep only for the engine. >> > 3.1.0 taged http://git.xfce.org/xfce/gtk-xfce-engine/tree/NEWS > > verbatim from the news: "Gtk+-3 support has been stopped" > > I asume they keep it but they stop supporting so I think unles a patch > that fix all the themes emerge wldly, will be better drop xfce3-gtk-engine > or the entire xfce-gtk-engine, but that mostly prove that they not > support gtk3, drop gtk2-greeter will render without a wai to use a gtk2 only > environment since lxdm is mostly no-more-maintained and is better have a > greeter > than a binary unsupported. > > Also xfce4 recomend greybird as theme for xfce if someone need a gtk2-gtk3 > theme > > * Therefore I propose to rename the current "lightdm-gtk3-greeter" into > *>>>* "lightdm-gtk-greeter" and drop the legacy "lightdm-gtk2-greeter" to AUR. > *>*> looking oxygen keep the gtk3 in AUR gtk3 only themes tend to use gtk3 and > *>*> gtk2 only thend to use gtk or gtk2, I will preffer keep the 3 in the > name. > *>>*> I could keep "lightdm-gtk2-greeter" around for a while in [community] if > *>>*> some people want me to (I'm thinking people using MATE for example, > *>>*> but it's going towards GTK3 anyway), but keep in mind that you can use > *>>>* LXDM instead if you really need a GTK2 display manager. > *>*> Or Xfce4 users, the upcoming xfce4 release is gtk2, and only after that > the > *>*> migration to gtk3 will start. > *>*> so a gtk2-greeter will be apreciated until xfce drop gtk2, and dont > forget > *>*> that LXDM is now presumably unmaintained or in low maintainance since > they > *>*> migrate to QT > *>*> If there aren't any objections by the end of the week, I'll > proceed with my > *>>*> proposal. > **> Me > *>*> > *>>>* Cheers, > *>> > > tldr; I will go for keep gtk2-greeter for xfce4 user since lxdm is > semi-unmaintained and better a unmaintained theme that a > binary. > someone know if slim keep working with systemd, last time was buggy > or not start or not let thing start at all (like logind) > I'm using slim with systemd and have noticed no issues. My arch is up to date. I was interested in this thread because I was thinking of trying lightdm with light-locker. I can't get xflock4 and gnome-screensaver to lock the screen. It works if I run xflock4 from the cli but the screen locking is not working automatically via power-manager. Regards, Richard
