Date: Wed, 2 Nov 2016 12:20:33 +0000 From: Manish Jain <bourne.identity@hotmail.com> To: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Could this be a software problem or a hardware issue ? Message-ID: <VI1PR02MB097424E598A33604546526E9F6A00@VI1PR02MB0974.eurprd02.prod.outlook.com> In-Reply-To: <mailman.115.1478088006.16970.freebsd-questions@freebsd.org> References: <mailman.115.1478088006.16970.freebsd-questions@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, I am on my second box which 'died' a while ago on account of a defective=20 SSD, which I have now replaced with a brand new SSHD in place of the=20 defective SSD. This system is a dual boot machine with XP and FreeBSD 11=20 amd64. XP is working very nicely. But FreeBSD is giving me a syndrome : If I=20 set the X driver to vesa, I get normal X display (with no drm, of=20 course). But if set the X driver to nvidia (which should be the correct=20 default for my NVidia GT 710 card), I get a strange screen with 'startx'=20 : mostly black with patches of colours spread across the screen.=20 Rebooting with the driver reset to vesa solves the problem. Further (with the X driver set to nvidia), I spotted that my ttyv0 gets=20 filled up with : ata0: FAILURE - odd-sized DMA transfer attempt 5 % 2 ata0: setting up DMA failed There are 3 components that I suspect could be the root of my problem[s] : 1) the motherboard (Gigabyte GA970) 2) RAM (Kingston DDR3 8 GB x 1, 1600 MHz) 3) the graphics card (NVidia 2 GB, GT 710) All of the above are just 2-3 months old, the RAM probably the newest. I would greatly appreciate any help trying to find out whether the=20 syndrome I see in the system is a software problem or a hardware issue.=20 Of course, if it is hardware, I request a hint what component is the=20 problem. Thanks & Regards Manish Jain
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?VI1PR02MB097424E598A33604546526E9F6A00>