public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Philip Webb <purslow@ca.inter.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: new machine : mobo fault
Date: Fri, 25 Sep 2015 20:33:35 -0400	[thread overview]
Message-ID: <20150926003335.GB1090@ca.inter.net> (raw)
In-Reply-To: <56018A16.809@gmail.com>

For the first time ever, I've bought a defective part for a new computer.

Today, my Gigabyte GA-970A-UD3P mobo fried a USB stick.
I was using a longstanding stick to transfer data from the present machine :
some files copied successfully, then further attempts were met
with an error msg "unreadable FS ... " or similar wording.
Back in the present machine the same obstacle occurred,
so something bad had been done to the stick.
I used Fdisk to delete + recreate the partition, reformatted,
then successfully copied the contents back from the HDD there
(yes, always keep multiple backups ! ) : no physical problem with the stick.

There's also a problem with the front USB-3 port, which freezes the system.

The store has a 14-day return, so I plan to try an ASUS instead :

  Item Code: MBAS003960 -- $ 105 mail-in $ -10 -- downtown 4
  ASUS M5A97 LE R2.0 Socket AM3+ AMD 970/SB950 Chipset
  Dual Channel DDR3 2133(O.C.) MHz, 2x PCI-Express x16
  GLAN, 6xSATA 6.0 Gb/s 2xUSB 3.0 6x USB 2.0

  Item Code: MBAS003965 -- $ 130 -- downtown 2
  ASUS M5A97 R2.0 Socdket AM3+ AMD 970/SB950 Chipset
  Dual Channel DDR3 2133(O.C.) MHz, 2x PCI-Express x16
  GLAN, 6xSATA 6.0 Gb/s 2xUSB 3.0 6x USB 2.0

  Item Code: MBAS004035 -- $ 165 mail-in $ -20 -- downtown 2
  ASUS M5A99X EVO R2.0 Socket AM3+ AMD 990X/SB950 Chipset
  Dual Channel DDR3 2133(O.C.) MHz, 3x PCI-Express x16
  GLAN, 6xSATA 6.0Gb/s 2xeSATA 6.0 Gb/s 2xUSB 3.0 8x USB 2.0

  Item Code: MBAS003885 -- $ 180 mail-in $ -15 -- downtown 2
  ASUS M5A99FX PRO R2.0 Socket AM3+ AMD 990FX/SB950 Chipset
  Dual Channel DDR3 2133(O.C.) MHz, 4x PCI-Express x16
  GLAN, 7xSATA 6.0Gb/s 1xeSATA 2xUSB 3.0 8x USB 2.0

Comments or suggestions very welcome.

-- 
========================,,============================================
SUPPORT     ___________//___,   Philip Webb
ELECTRIC   /] [] [] [] [] []|   Cities Centre, University of Toronto
TRANSIT    `-O----------O---'   purslowatchassdotutorontodotca



  reply	other threads:[~2015-09-26  0:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17  3:04 [gentoo-user] new machine : case + power Philip Webb
2015-09-17  3:33 ` Dale
2015-09-17  3:38 ` [gentoo-user] " james
2015-09-17  6:29   ` Alan McKinnon
2015-09-17  6:56     ` Dale
2015-09-17  8:13     ` Neil Bothwick
2015-09-17 12:52     ` Rich Freeman
2015-09-18  2:21   ` Philip Webb
2015-09-22 12:27   ` [gentoo-user] Re: new machine : case fan Philip Webb
2015-09-22 17:04     ` Dale
2015-09-26  0:33       ` Philip Webb [this message]
2015-09-24 14:00   ` [gentoo-user] Re: new machine : case + power Volker Armin Hemmann
2015-09-24 16:12     ` Alan McKinnon
2015-09-24 20:55       ` Volker Armin Hemmann
2015-09-17  5:28 ` Nikos Chantziaras
2015-09-17 13:26   ` james
2015-09-17 13:36     ` Alan McKinnon
2015-09-17 14:09       ` james
2015-09-17 14:26         ` Alan McKinnon
2015-09-17 16:56           ` james
2015-09-17 19:36             ` Alan McKinnon
2015-09-17 20:25       ` Alec Ten Harmsel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150926003335.GB1090@ca.inter.net \
    --to=purslow@ca.inter.net \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox