You are not logged in.
Moved this thread to this location as the situation seems to have changed.
-------------------------------------------------------------------------------------------------------
Flash video consistantly crashes reboots my machine after enable acpi.
Any help would be greatly appreciated.
Linux Arch 3.11.1-1-ARCH #1 SMP PREEMPT Sat Sep 14 19:30:21 CEST 2013 x86_64 GNU/Linux
Machine Specs:
16 GB RAM
120 GB Digital Sata HD - OCZ3
Radeon HD 6570 PCIe Card
Asus motherboard M5A87
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 8
On-line CPU(s) list: 0-7
Thread(s) per core: 2
Core(s) per socket: 4
Socket(s): 1
NUMA node(s): 1
Vendor ID: AuthenticAMD
CPU family: 21
Model: 1
Model name: AMD FX(tm)-8120 Eight-Core Processor
Stepping: 2
CPU MHz: 1400.000
BogoMIPS: 6202.20
Virtualization: AMD-V
L1d cache: 16K
L1i cache: 64K
L2 cache: 2048K
L3 cache: 8192K
NUMA node0 CPU(s): 0-7
Last edited by apex (2013-09-22 12:38:35)
Offline
the following gub command seems to fix the flash issue but now lscpu only shows ONE CORE again. Arrrrgggghhhh im going bald over this.
GRUB_CMDLINE_LINUX="nolapic"
I have 8 cores and need all of them, I hope someone out there knows how to fix the flash video problem so all cpu cores can be used.
Offline
Can you link me to some documentation or explain exactly what that kernel command line argument you added does?
Offline
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Cute.
Offline
@OP --
Is ACPI enabled in your BIOS settings?
Offline
Cute.
I think the idea here was to hint towards the fact that you should be doing your own googling. People here are happy to help with issues, but trying to outsource your googling is kind of insulting.
If you want the actual documentation regarding the kernel command line's parameters, it can be found in the linux-docs package (along with all the other kernel documentation). Grep'ing through "pacman -Ql linux-docs" should lead you to it.
Offline
ub1quit33 wrote:Cute.
I think the idea here was to hint towards the fact that you should be doing your own googling. People here are happy to help with issues, but trying to outsource your googling is kind of insulting.
I didn't reaize me asking the OP to save me a bit of time in exchange for throwing in a suggestion or two would insult anyone. Apparently that's worth people taking time out of their day to mock me for though.
Offline
Apparently that's worth people taking time out of their day to mock me for though.
I don't mock. I will take my personal time to help with Linux problems big and small. All I (we) ask is that members respect the time of other volunteers by researching to the best of one's ability prior to asking a question. I thought your question showed a lack of motivation on your part and I tried to guide you to what should have been the canonical reference provided by a trivial search in a jovial manner. No insult intended.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
ub1quit33 wrote:Apparently that's worth people taking time out of their day to mock me for though.
I don't mock. I will take my personal time to help with Linux problems big and small. All I (we) ask is that members respect the time of other volunteers by researching to the best of one's ability prior to asking a question. I thought your question showed a lack of motivation on your part and I tried to guide you to what should have been the canonical reference provided by a trivial search in a jovial manner. No insult intended.
I'm cool with that, which is why when I start forum topics I always provide as complete of an information set as possible, which outlines my exploration of the problem up to that point. The thing about my posting in this thread was that it wasn't really my question, in the sense that I wasn't asking it for my own sake, personal curiosity, or pursuit of knowledge. It was a requisite piece of information I needed in order to further explore the OPs problem, and consider potential solutions. To that end, all I did was ask the OP to save me a bit of time in trying to help him. This doesn't seem like a disrespect of anyone's time, seeing as it's reasonable to assume that the OP explored some understanding of exactly what that kernel command line option does prior to applying it to his boot process. This means he doesn't even have to take extra time out of his day, just share a bit of information with me.
Offline