[gentoo-user] My Gentoo and Windows don't get along on vfat
He guys, I regularly attach a friend’s external HDD to my laptop or NAS, both running “standard” Gentoo. The main partition is fat32 formatted. On and off she has problems mounting the drive, usually after I had it connected to one of my machines. It happened again today. So chronologically: 1) Someone else attached the drive to his Windows 10 laptop and put a few Gigs into a single folder. 2) Then I attached it to my NAS, which didn’t even create a device for it. I read some hardware error in the system log. 3) I attached it to my laptop. It also showed the error message (see below), but it did create a device and I could mount the data partition. Sep 22 12:14:53 kern kernel: sd 7:0:0:0: [sdd] tag#0 FAILED Result: Sep 22 12:14:53 kern kernel: sd 7:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE Sep 22 12:14:53 kern kernel: sd 7:0:0:0: [sdd] tag#0 Sense Key : Hardware Error [current] [descriptor] Sep 22 12:14:53 kern kernel: sd 7:0:0:0: [sdd] tag#0 Add. Sense: No additional sense information Sep 22 12:14:53 kern kernel: sd 7:0:0:0: [sdd] tag#0 CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00 When I had the drive hooked to my laptop in 3), I was shuffling stuff around on it (mostly copying and deleting a few files from the folder mentioned in 1) and renaming files in other places). Today she left me a note saying her Windows needed to check the drive and now that folder was missing. I found that Windows “recovered” its contend into /FOUND.001 with all filenames lost. m( Naturally, I always unmount the drive prior to removing it physically, usually with KDE’s media manager. The drive (or the controller in the case?) contains a cdrom emulation to offer drivers and something called “WD SmartWare”. *shiver* I always wonder whether this plays a part with our problems. When the drive is connected to Windows – IIRC – first the cdrom appears, and after a while disappears and makes way for the actual data partition. Do you have similar experiences and maybe even a tip on how to make her and my systems play along better? The only thing coming to my mind right now is to ditch fat32 and go with something more robust like exfat(?) or ntfs. Cheerio. -- Gruß | Greetings | Qapla’ Please do not share anything from, with or about me on any social network. A wise man once said: “Web 2.0, that is round corners.” I think that is a very fitting summary of two hypes. (SelfHTML forum) signature.asc Description: Digital signature
Re: [gentoo-user] My Gentoo and Windows don't get along on vfat
On Friday, September 22, 2017 12:56:01 PM CEST Frank Steinmetzger wrote: > He guys, > > I regularly attach a friend’s external HDD to my laptop or NAS, both running > “standard” Gentoo. The main partition is fat32 formatted. On and off she > has problems mounting the drive, usually after I had it connected to one of > my machines. > > It happened again today. So chronologically: > 1) Someone else attached the drive to his Windows 10 laptop and put a few >Gigs into a single folder. > 2) Then I attached it to my NAS, which didn’t even create a device for it. I > read some hardware error in the system log. > 3) I attached it to my laptop. It also showed the error message (see below), > but it did create a device and I could mount the data partition. > > Sep 22 12:14:53 kern kernel: sd 7:0:0:0: [sdd] tag#0 FAILED Result: > Sep 22 12:14:53 kern kernel: sd 7:0:0:0: [sdd] tag#0 FAILED Result: > hostbyte=DID_ERROR driverbyte=DRIVER_SENSE Sep 22 12:14:53 kern kernel: sd > 7:0:0:0: [sdd] tag#0 Sense Key : Hardware Error [current] [descriptor] Sep > 22 12:14:53 kern kernel: sd 7:0:0:0: [sdd] tag#0 Add. Sense: No additional > sense information Sep 22 12:14:53 kern kernel: sd 7:0:0:0: [sdd] tag#0 CDB: > ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 > 00 > > > When I had the drive hooked to my laptop in 3), I was shuffling stuff around > on it (mostly copying and deleting a few files from the folder mentioned in > 1) and renaming files in other places). Today she left me a note saying her > Windows needed to check the drive and now that folder was missing. I found > that Windows “recovered” its contend into /FOUND.001 with all filenames > lost. m( > > Naturally, I always unmount the drive prior to removing it physically, > usually with KDE’s media manager. The drive (or the controller in the case?) > contains a cdrom emulation to offer drivers and something called “WD > SmartWare”. *shiver* I always wonder whether this plays a part with our > problems. When the drive is connected to Windows – IIRC – first the cdrom > appears, and after a while disappears and makes way for the actual data > partition. aargh... I stopped using those WD drives, if you want to disable that part, follow instructions on the WD support page: https://support.wdc.com/knowledgebase/answer.aspx?ID=3835 (If this works) > Do you have similar experiences and maybe even a tip on how to make her and > my systems play along better? The only thing coming to my mind right now is > to ditch fat32 and go with something more robust like exfat(?) or ntfs. As mentioned, I stopped using drives like that. Never did encounter similar issues, but then I only used those with MS Windows systems in the past. My guess is, you unmount the cd-partition, instead of the actual data partition. The broken firmware in those drives cause issues with the drivers, which is what that "cdrom" partition actually tries to fix. Best advice: Scrap that drive and get one without the cdrom-partition. I use WD Elements drives, these don't come with that cr*p. -- Joost
Re: [gentoo-user] My Gentoo and Windows don't get along on vfat
On Fri, Sep 22, 2017 at 01:43:24PM +0200, J. Roeleveld wrote: > > Naturally, I always unmount the drive prior to removing it physically, > > usually with KDE’s media manager. The drive (or the controller in the case?) > > contains a cdrom emulation to offer drivers and something called “WD > > SmartWare”. *shiver* I always wonder whether this plays a part with our > > problems. When the drive is connected to Windows – IIRC – first the cdrom > > appears, and after a while disappears and makes way for the actual data > > partition. > > aargh... > I stopped using those WD drives, if you want to disable that part, follow > instructions on the WD support page: > https://support.wdc.com/knowledgebase/answer.aspx?ID=3835 > (If this works) > > > Do you have similar experiences and maybe even a tip on how to make her and > > my systems play along better? The only thing coming to my mind right now is > > to ditch fat32 and go with something more robust like exfat(?) or ntfs. > […] > My guess is, you unmount the cd-partition, instead of the actual data > partition. The broken firmware in those drives cause issues with the > drivers, which is what that "cdrom" partition actually tries to fix. Well I can’t say for sure what I did yesterday, but usually I try to make quite sure to Do the Right Thing™ (usually I go through both partition entries in the media panel and try to unmount them) to avoid exactly what had happened. > Best advice: Scrap that drive and get one without the cdrom-partition. Well the disk itself works alright, smart is clean and the long self-test came back with no problems. So I guess that’s not really an option. :o) An extended smart self-test just came back with 100 % A-OK. I’ll suggest to her to disable SmartWare. -- Gruß | Greetings | Qapla’ Please do not share anything from, with or about me on any social network. Kids in the back seat cause accidents. Accidents in the backseat cause kids. signature.asc Description: Digital signature
[gentoo-user] Pure Data (Pd) can't access ALSA device
I can't get Pure Data to work with ALSA. It detects my sound card, but whenever I try to turn on the audio I get the error: ALSA output error (snd_pcm_open): Device or resource busy. I've tried both using the ebuild from the audio-overlay and compiling from the source on the Pd website, both behave the same. I've read that Pd deals with ALSA differently than most other programs, but haven't found an explanation how. I did get it to work with JACK. - Lasse
Re: [gentoo-user] Pure Data (Pd) can't access ALSA device
This sounds pretty normal to me. ALSA isn't really suited for simultaneous audio access. In general with ALSA you have only one program that can use audio at a time, or you use the mixer module from ALSA. I assume a program running on the background has claimed ALSA already for certain reasons. If you run PulseAudio (which is pretty standard on a regular desktop), this one will be the cullprit. Usually the jack tools are smart enough to suspend pulseaudio. You can in fact run puredata through the pasuspend script which suspends pulseaudio so ALSA is free again. What I recommend (which you already tried) is using JACK. JACK will take ownership of your ALSA device, and gives you a capable routing system allowing you to hook up more than just PureData to your audio card. Optionally routing it to other software. In addition, it's possible to compile pulseaudio with jack support which means you can in fact have regular (non-audio) apps work together with jack, which is what I sometimes use: Set up my audio studio setup, while still having pulseaudio around for stuff like browsers and video players. If I suddenly have a creative spark, I have my studio ready to play with. When I'm done, browsers still work with sound Daniel On vrijdag 22 september 2017 18:23:10 CEST Lasse Pouru wrote: > I can't get Pure Data to work with ALSA. It detects my sound card, but > whenever I try to turn on the audio I get the error: > > ALSA output error (snd_pcm_open): Device or resource busy. > > I've tried both using the ebuild from the audio-overlay and compiling > from the source on the Pd website, both behave the same. I've read that > Pd deals with ALSA differently than most other programs, but haven't > found an explanation how. I did get it to work with JACK. > > - Lasse
Re: [gentoo-user] Pure Data (Pd) can't access ALSA device
I don't (and won't) use PulseAudio and haven't set up dmix or anything like it. The weird thing is the simultaneous audio works with every other program I use (Qutebrowser, mpd, Audacity etc.) -- it's only Pd that gives the error. I already use JACK when recording but it would be more convenient for me to use ALSA when I'm just quickly trying out stuff. (I've set up JACK to use an audio interface I don't have plugged in most of the time.) - Lasse Daniel Sonck writes: > This sounds pretty normal to me. ALSA isn't really suited for simultaneous > audio access. In general with ALSA you have only one program that can use > audio at a time, or you use the mixer module from ALSA. I assume a program > running on the background has claimed ALSA already for certain reasons. > > If you run PulseAudio (which is pretty standard on a regular desktop), this > one will be the cullprit. Usually the jack tools are smart enough to suspend > pulseaudio. You can in fact run puredata through the pasuspend script which > suspends pulseaudio so ALSA is free again. > > What I recommend (which you already tried) is using JACK. JACK will take > ownership of your ALSA device, and gives you a capable routing system > allowing > you to hook up more than just PureData to your audio card. Optionally routing > it to other software. In addition, it's possible to compile pulseaudio with > jack support which means you can in fact have regular (non-audio) apps work > together with jack, which is what I sometimes use: Set up my audio studio > setup, while still having pulseaudio around for stuff like browsers and video > players. If I suddenly have a creative spark, I have my studio ready to play > with. When I'm done, browsers still work with sound > > Daniel > > On vrijdag 22 september 2017 18:23:10 CEST Lasse Pouru wrote: >> I can't get Pure Data to work with ALSA. It detects my sound card, but >> whenever I try to turn on the audio I get the error: >> >> ALSA output error (snd_pcm_open): Device or resource busy. >> >> I've tried both using the ebuild from the audio-overlay and compiling >> from the source on the Pd website, both behave the same. I've read that >> Pd deals with ALSA differently than most other programs, but haven't >> found an explanation how. I did get it to work with JACK. >> >> - Lasse
Re: [gentoo-user] no more googleearth in portage
On 09/20/17 07:55, Raffaele Belardi wrote: I suppose it's due to Google's choice to support only Chrome, although I missed the Gentoo news bit if there was one. For Android there is the really good Open Street Map application, are there any desktop alternatives in Portage for non-Chrome users? I know OSM has a web interface but I'd prefer a standalone application. raffaele Maybe sci-geosciences/viking ? Try to change the map from MapQuest to MapNik to get a first impression. Urs
[gentoo-user] Re: Pure Data (Pd) can't access ALSA device
On 2017-09-22 23:13, Lasse Pouru wrote: > I don't (and won't) use PulseAudio and haven't set up dmix or anything > like it. The weird thing is the simultaneous audio works with every > other program I use (Qutebrowser, mpd, Audacity etc.) -- it's only Pd > that gives the error. AFAIK dmix has been the default output for libasound for quite a while. Normally you don't have to set up anything for dmix to be used - that's why your other programs work, I think. Maybe pd is trying to use the underlying sound card directly as a libasound output? I don't know abything about puredata, unfortunately. -- Please don't Cc: me privately on mailing lists and Usenet, if you also post the followup to the list or newsgroup. Do obvious transformation on domain to reply privately _only_ on Usenet.
