Subj : USB 3 Issue? To : Ky Moffet From : Barry Martin Date : Wed Jan 22 2020 10:10:00 Hi Ky! > > Mike and Ky (and anyone else!): > KM> Anyone! speak up! :D > Or here preferably type! KM> I thought I'd try smoke signals. :D The people near forest fires may have interference. > KM> ADATA have a dreadful rep, as I've mentioned before. I expect > KM> they're strictly rebadging seconds (not manufacturing their own > KM> chips) so what you get depends on the source... and they may > KM> differentiate source by color. > That might explain why 'all' blues worked and 'all' of the yellows KM> Yeah, usually a reasonable guess. If you open 'em up they likely KM> aren't quite the same inside. I should have cracked open the yellow ones! Thought I don't recall if any problems with the blue ones and don't want to damage one just to see: already annoying enough to have wasted money on the ones that failed. ... There might be another way: the 'lsusb' command displays a vendor:device code. I still have at least one yellow thumbdrive left. ...Test later: don't want that testing to lock up the computer! > didn't. I was also thinking it was a slightly odd name for an > electronics company: 'a-' is a Latin prefix for 'without/lack of'..... KM> Bit alarming, eh? :) Even moreseo now! > > KM> https://en.wikipedia.org/wiki/USB_flash_drive#Counterfeit_products > > KM> ====== > KM> Counterfeit products > > Hmmmm! I'm recalling a failed thumbdrive (thought not which brand) where > a recovery tool indicated the data went beyond the sector count - > something like that. KM> Yep, that's exactly what you'd see with a counterfeit. And as stupid as it may seem I will continue to occasionally purchase cheap and potentially counterfeit thumbdrives: sometimes just need to work a few times to 'get there'. > > ..Suggestions? Ideas? > KM> Shouldn't be static with USB stuff, because it self-grounds. > KM> (Same with SATA.) Also, judging by the shocks I've seen this > KM> stuff survive unfazed, it's not really all that sensitive. My > KM> New! Improved!! mainboard (Asus P9X79LE, about 5 years old) has a > KM> function to protect itself from static or overvoltage, which I > KM> expect is probably fairly standard now. > OK, good. I don't recall hearing a zap but couldn't absolutely say no. > Will continue to ground-before-insert just as a good practice. KM> If only because *I* don't like getting zapped. :) So we have found out you're not into that cheap a thrill!! > KM> Response in comments: > KM> ========= > KM> Make sure you have all drives plugged into the Intel ports, these > KM> are the white or black SATA ports and USB 2.0 ports. Disable the > KM> Marvell SATA ports and Etron USB ports in the BIOS. > Will check that one out: "Marvell" doesn't sound quite right but does > sound close to one (maybe a pair) port on the motherboard. "Etron" > doesn't sound familiar. (Why am I thinking Eltron Port, song writer to > "Good Bye Yellow Bricked Load" and "Crocodile Clip"??) KM> Only Marvell ports I have are IDE, nowadays decidedly unheroic. I KM> like your musical choices, tho. :D The "Marvell" I'm half-remembering had something to so with the SATA ports on the motherboard and pretty sure is on a diferent computer. Need to check still - when go to the store tomorrow wil pick u psome more Round TuIts. >> KM> C3, C6, EIST and CPU PLL Overvoltage solved it for some people so > KM> you may want to try that. ========== > OK, thanks! No overclocking/overvoltage tweaks done here -- I can get > in enough trouble as is! -- but quite possible the manufacturer's > default values 'turned up the control' a bit to make the motherboard's > specs look better. KM> Yeah, sometimes undervoltaging/underclocking will solve a KM> stability issue. Right: if manufacturer's defaults too close to the edge just to get a higher rating..... KM> Among the weirds formerly infesting The Closet... pair of KM> nominally identical early Pentium motherboards. Pair of early KM> Pentium CPUs. Each board would only speak to one of the two CPUs, KM> and only when misclocked: the 60MHz had to be set to 66MHz and KM> the 66MHz had to be set to 60MHz. W.T.F. I'd say 'mixed up labeling' bu that would make sense only if you or someone else did the actual labeling of the two specific mother- boards and CPUs. At least you figured out the problem: I pretty much go with the defaults so don't fiddle with the overclocking/underclocking. ¯ ® ¯ Barry_Martin_3@ ® ¯ @Q.COM ® ¯ ® .... 486DX2/666: The CPU that's damned fast. --- MultiMail/Win32 v0.47 þ wcECHO 4.2 ÷ ILink: The Safe BBS þ Bettendorf, IA --- QScan/PCB v1.20a / 01-0462 * Origin: ILink: CFBBS | cfbbs.no-ip.com | 856-933-7096 (454:1/1) .