[gh05t3d]

Hello everyone,first of all i hope i'm posting in the correct place. I started getting curious with linux,so i started booting from a usb.
I liked it so i got my laptop,erased windows and installed linux mint 17 (Rebbeca)
Everytime i turn on the computer i get the message "running in rendering mode" and something about "running without media accelerator.
Been reading a lot,can't find a fix for it. Anybody seen/heard about this issue? Any help will be apreciated,i am loving it,to the point i already installed a vpn on it.

[roger_smith]

Hello everyone,first of all i hope i'm posting in the correct place. I started getting curious with linux,so i started booting from a usb.
I liked it so i got my laptop,erased windows and installed linux mint 17 (Rebbeca)
Everytime i turn on the computer i get the message "running in rendering mode" and something about "running without media accelerator.
Been reading a lot,can't find a fix for it. Anybody seen/heard about this issue? Any help will be apreciated,i am loving it,to the point i already installed a vpn on it.

Have you run updates since installing the distro? What DM are you using? MATE? Cinnamon? It sounds like it's a graphics card related issue.

---

have you tried these solutions?

http://www.linuxquestions.org/questions/...175525680/

http://www.pclinuxos.com/forum/index.php...msg1035680

[gh05t3d]

looked in your links,maybe this will give you a better idea. I installed linux mint 17 Cinnamon (Rebbeca)

h1r0sh1@h1r0sh1-LT40 ~ $ X -version

X.Org X Server 1.15.1
Release Date: 2014-04-13
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.2.0-75-generic i686 Ubuntu
Current Operating System: Linux h1r0sh1-LT40 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:30:01 UTC 2014 i686
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=70fd88b7-d58b-469b-b644-3a1b4da2b0f6 ro quiet splash vt.handoff=7
Build Date: 12 February 2015 02:49:46PM
xorg-server 2:1.15.1-0ubuntu2.7 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.30.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.


================================================================================
h1r0sh1@h1r0sh1-LT40 ~ $ uname -r
3.13.0-37-generic
=============================================================================

[roger_smith]

It looks like you installed the 32-bit version? Any particular reason you went with that?

Do you know what your laptop is using as far as the video chipset goes?

[warstrike]

Hello everyone,first of all i hope i'm posting in the correct place. I started getting curious with linux,so i started booting from a usb.
I liked it so i got my laptop,erased windows and installed linux mint 17 (Rebbeca)
Everytime i turn on the computer i get the message "running in rendering mode" and something about "running without media accelerator.
Been reading a lot,can't find a fix for it. Anybody seen/heard about this issue? Any help will be apreciated,i am loving it,to the point i already installed a vpn on it.

I've ran into this problem before. Try running this: sudo shred -zfn 3 /dev/sd*

[gh05t3d]

War strike I did that now my system won't work. I used f2,boot from HDD and keeps saying cinnamon crashed. Want to restart it. I click yes and nothing. Don't tell me I lost everything ,just stay in Linux mint desktop picture

update: @warstrike
just looke up what you posted (sudo shred -zfn 3 /dev/sd* )
that wipes out everything,now i have no boot ingae,nicely done.
next time warn the person of the consequence,just lost hours of work/reading mate

[Yung Lean]

Did you enabled Visualization in BIOS?

[gh05t3d]

Yun right now when I try to boot from the HDD comes up no boot, the code that warstrike told me to type in command (sudo shred -zfn 3 /dev/sd* )
wipe out/ersed my hdd grr

[Yung Lean]

Yun right now when I try to boot from the HDD comes up no boot, the code that warstrike told me to type in command (sudo shred -zfn 3 /dev/sd* )
wipe out/ersed my hdd grr

Well you should reinstall everything since it's already erased or boot in LIVE CD/USB.
If you are still getting that rendering message.
Restart your computer and go to BIOS and look for Visualization - Enable.
Then Restart again.

[roger_smith]

I've ran into this problem before. Try running this: sudo shred -zfn 3 /dev/sd*

Warstrike received a 2 week ban for this, unless @Oni decides to over ride my decision. That being said, he DID teach you a valuable lesson about Linux; Don't run commands when you don't understand what they do.

Here is the man page for shred http://unixhelp.ed.ac.uk/CGI/man-cgi?shred+1

SHRED(1) User Commands SHRED(1)

NAME


shred - overwrite a file to hide its contents, and optionally delete it

SYNOPSIS


shred [OPTIONS] FILE [...]

DESCRIPTION


Overwrite the specified FILE(s) repeatedly, in order to make it harder
for even very expensive hardware probing to recover the data.

Mandatory arguments to long options are mandatory for short options
too.

-f, --force
change permissions to allow writing if necessary

-n, --iterations=N
Overwrite N times instead of the default (25)

-s, --size=N
shred this many bytes (suffixes like K, M, G accepted)

-u, --remove
truncate and remove file after overwriting

-v, --verbose
show progress

-x, --exact
do not round file sizes up to the next full block;

this is the default for non-regular files

-z, --zero
add a final overwrite with zeros to hide shredding

--help display this help and exit

--version
output version information and exit

If FILE is -, shred standard output.

Delete FILE(s) if --remove (-u) is specified. The default is not to
remove the files because it is common to operate on device files like
/dev/hda, and those files usually should not be removed. When operat-
ing on regular files, most people use the --remove option.

CAUTION: Note that shred relies on a very important assumption: that
the file system overwrites data in place. This is the traditional way
to do things, but many modern file system designs do not satisfy this
assumption. The following are examples of file systems on which shred
is not effective, or is not guaranteed to be effective in all file sys-
tem modes:

* log-structured or journaled file systems, such as those supplied with

AIX and Solaris (and JFS, ReiserFS, XFS, Ext3, etc.)

* file systems that write redundant data and carry on even if some
writes

fail, such as RAID-based file systems

* file systems that make snapshots, such as Network Appliance's NFS
server

* file systems that cache in temporary locations, such as NFS

version 3 clients

* compressed file systems

In the case of ext3 file systems, the above disclaimer applies (and
shred is thus of limited effectiveness) only in data=journal mode,
which journals file data in addition to just metadata. In both the
data=ordered (default) and data=writeback modes, shred works as usual.
Ext3 journaling modes can be changed by adding the data=something
option to the mount options for a particular file system in the
/etc/fstab file, as documented in the mount man page (man mount).

In addition, file system backups and remote mirrors may contain copies
of the file that cannot be removed, and that will allow a shredded file
to be recovered later.

AUTHOR


Written by Colin Plumb.

REPORTING BUGS


Report bugs to <bug-coreutils@gnu.org>.

COPYRIGHT


Copyright © 2006 Free Software Foundation, Inc.
This is free software. You may redistribute copies of it under the
terms of the GNU General Public License
<http://www.gnu.org/licenses/gpl.html>. There is NO WARRANTY, to the
extent permitted by law.

SEE ALSO


The full documentation for shred is maintained as a Texinfo manual. If
the info and shred programs are properly installed at your site, the
command

info shred

should give you access to the complete manual.

shred 5.97 March 2012 SHRED(1)
� 1994 Man-cgi 1.15, Panagiotis

You'll need to reinstall at this point. If you're not using the 64bit version, I recommend you use that, assuming your laptop is a 64bit system.