LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 05-23-2012, 11:04 PM   #1
thund3rstruck
Member
 
Registered: Nov 2005
Location: East Coast, USA
Distribution: Fedora 18, Slackware64 13.37, Windows 7/8
Posts: 346

Rep: Reputation: 38
Machine Hard Locks with Firefox


Hi everyone,

I'm using slack64 13.37 with Firefox 12 and Kde 4.6.5 (from ktown). Tonight my new Dell Laptop hard locked..froze up like Windows 95. No CTRL+ALT+Backspace or ALT+F2, nothing. Mouse moves but nothing in the UI responds. The only way to resolve was to hard reset. Tried 3 more times to use firefox tonight and all of them resulted in the same hard lock.

I have no idea how to troubleshoot this. Does anyone have any clues or tips I might investigate.

I was deep into research so I had to reboot into Win 7 so I could get my work done....
 
Old 05-24-2012, 01:24 PM   #2
NyteOwl
Member
 
Registered: Aug 2008
Location: Nova Scotia, Canada
Distribution: Slackware, OpenBSD, others periodically
Posts: 512

Rep: Reputation: 139Reputation: 139
Does it happen in any other browsers (Opera, Chromium, Konqueror, etc.) or just Firefox?
 
Old 05-24-2012, 01:56 PM   #3
KeithE
Member
 
Registered: Jan 2003
Location: Phoenix, AZ
Distribution: Mint, Slackware
Posts: 88

Rep: Reputation: 19
Are you using a newer nVidia graphics chip with the Nouveau driver? If so, then that might be the problem. It's not a Slackware or Firefox issue. I had the same problem while running mplayer before I switched to the nVidia driver with a GT218 chip.

This is a comment I wrote in another thread on the main Linux Distributions page:

If you have a nVidia GT218 graphics chip, you can't use the default Nouveau driver. It WILL lock up (discovered while running both Slackware 13.37 and Debian Wheezy - 32 and 64 bit - on a Zotac ZBox). The proprietary nVidia driver is required here. It takes all of 10-15 minutes to download and compile it, then reboot. This is not a Slackware issue, per-se, but this driver is required. Other graphics chips may also require a proprietary driver, but I'm not familiar with them.
 
Old 05-24-2012, 02:47 PM   #4
thund3rstruck
Member
 
Registered: Nov 2005
Location: East Coast, USA
Distribution: Fedora 18, Slackware64 13.37, Windows 7/8
Posts: 346

Original Poster
Rep: Reputation: 38
Quote:
Originally Posted by KeithE View Post
Are you using a newer nVidia graphics chip with the Nouveau driver? If so, then that might be the problem. It's not a Slackware or Firefox issue. I had the same problem while running mplayer before I switched to the nVidia driver with a GT218 chip.

This is a comment I wrote in another thread on the main Linux Distributions page:

If you have a nVidia GT218 graphics chip, you can't use the default Nouveau driver. It WILL lock up (discovered while running both Slackware 13.37 and Debian Wheezy - 32 and 64 bit - on a Zotac ZBox). The proprietary nVidia driver is required here. It takes all of 10-15 minutes to download and compile it, then reboot. This is not a Slackware issue, per-se, but this driver is required. Other graphics chips may also require a proprietary driver, but I'm not familiar with them.
Its an Intel® HD Graphics 3000 embedded video card, not NVidia or ATI. I only use firefox as my browser because I have 10 years of bookmarks synced over the cloud to all my machines at home and work so my Operating System has to support firefox. Everything else I can work around but Firefox is not something I can live without.

I'll try to get more data after work but this is my personal laptop and I only use it a few hours at night before bed. Everything was going great for the first few weeks but now firefox just hard locks the entire system. The last time I opened firefox it automatically tried to load my 15 previous tabs and it just hard locked the system again. At that point I had to get my work done so I rebooted into Win 7.
 
Old 05-24-2012, 04:12 PM   #5
Martinus2u
Member
 
Registered: Apr 2010
Distribution: Slackware
Posts: 350

Rep: Reputation: 56
welcome to the world of intel graphics. It sometimes helps to follow the recommendations on here:
http://intellinuxgraphics.org/download.html .

After years of wasted time I personally have come to the conclusion to avoid the intel driver stack at all cost.
 
Old 05-24-2012, 04:35 PM   #6
schmatzler
Member
 
Registered: Jan 2011
Location: Germany
Distribution: Slackware64 -current + Multilib
Posts: 205

Rep: Reputation: 61
I love my Intel card. It works fine with Mesa 8 and with libxtc_dxtn it can also play some nice 3D games. I never experienced problems like this hardlock here with it. Plus, that damn thing does never get hot and consumes much less power than NVIDIA or AMD chips.

True is, that it was really slow with older releases of Mesa and produced a lot of graphical bugs in Firefox, though it was still useable.

I suspect an old version of Mesa here, try upgrading it to the latest one. The 8-release has nice OpenGL3 support, which is really useful

If you have a custom xorg.conf, try renaming it or deleting it and see if the chip works fine if its autodetected.

You should also check /var/log/dmesg or Xorg.log if any errors occured when you started Firefox.
 
Old 05-24-2012, 07:49 PM   #7
thund3rstruck
Member
 
Registered: Nov 2005
Location: East Coast, USA
Distribution: Fedora 18, Slackware64 13.37, Windows 7/8
Posts: 346

Original Poster
Rep: Reputation: 38
Wink

Quote:
Originally Posted by schmatzler View Post
I love my Intel card. It works fine with Mesa 8 and with libxtc_dxtn it can also play some nice 3D games. I never experienced problems like this hardlock here with it. Plus, that damn thing does never get hot and consumes much less power than NVIDIA or AMD chips.

True is, that it was really slow with older releases of Mesa and produced a lot of graphical bugs in Firefox, though it was still useable.

I suspect an old version of Mesa here, try upgrading it to the latest one. The 8-release has nice OpenGL3 support, which is really useful

If you have a custom xorg.conf, try renaming it or deleting it and see if the chip works fine if its autodetected.

You should also check /var/log/dmesg or Xorg.log if any errors occured when you started Firefox.
I'm running mesa 7.9.2 per glxinfo. Everything is stock Slackware64 13.37 other than the KDE version on a brand new Dell Inspiron 15R.

I did notice this bizarre message in dmesg:
Code:
[    9.000066] [drm] MTRR allocation failed.  Graphics performance may suffer.
I really have no idea what MTRR is or if this might have something to do with the hardlocks.
 
Old 05-25-2012, 12:10 AM   #8
TracyTiger
Member
 
Registered: Apr 2011
Location: California, USA
Distribution: Slackware
Posts: 290

Rep: Reputation: 72
MTRR tidbits

Quote:
Originally Posted by thund3rstruck View Post
I did notice this bizarre message in dmesg:
Code:
[    9.000066] [drm] MTRR allocation failed.  Graphics performance may suffer.
I really have no idea what MTRR is or if this might have something to do with the hardlocks.
I was also trying to find out if this (common) MTRR error was of any consequence (intel graphics performance in my case). I found these two forum threads discussing this. There are more in various Linux distribution forums.

http://www.linuxquestions.org/questi...raphic-887537/

http://www.linuxquestions.org/questi...memory-903691/

I also found a thread where someone referenced more details in the kernel documents ( /usr/src/linux/Documentation/x86/mtrr.txt ).

The boot parameters involved (found at http://kernel.org/doc/Documentation/...parameters.txt) appear to be:
  • mtrr_chunk_size=n[KMG]
  • mtrr_gran_size=n[KMG]
  • mtrr_spare_reg_NR=n, n=0-7, default 1
  • enable_mtrr_cleanup
  • disable_mtrr_cleanup
  • disable_mtrr_trim

I set boot parameters according to one of the threads referenced above to get the MTRR error to go away. (It did NOT appear to affect/improve graphics performance in my case.

There are also a few settings in kernel configuration. (grep MTRR .config)

So to summarize, I also don't know anything about MTRR but thought I'd give you some items I discovered about it in case you need to pursue it. You could try setting some of the parameters to get the MTRR error to go away an see if it has an impact on your issue.

Perhaps someone knowledgeable can let us know if MTRR errors on boot are of any importance and how it impacts the system...or can we usually ignore them.

P.S. I should mention that I use the graphics on my Intel i5 Sandybridge and had tremendous problems (graphics, boot/acpi, i915 driver) on my Asus P8Z68-V LE motherboard the last few weeks. My main problems have gone away since I went to Slack(both 32 & 64) current and a 3.3.7 kernel. If I remember correctly the turning point was the current May 5th changes and the 3.2.x kernel. Just a note to a fellow Intel embedded graphics user. This is my first foray into the world of Intel graphics. I've always used Nvidia in the past. I may eventually come to the same conclusion as Martinus2U.

Last edited by TracyTiger; 05-25-2012 at 12:53 AM. Reason: Added additional paragraph at end
 
1 members found this post helpful.
Old 05-25-2012, 01:32 AM   #9
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,566

Rep: Reputation: 462Reputation: 462Reputation: 462Reputation: 462Reputation: 462
As root, what does the output of
Code:
/sbin/lspci -v
give you?

It should be possible to take the output of that lspci command and figure out the correct MTRR setting for your graphics card. The wikipedia MTRR article may be of some assistance.
 
Old 05-25-2012, 04:16 AM   #10
Martinus2u
Member
 
Registered: Apr 2010
Distribution: Slackware
Posts: 350

Rep: Reputation: 56
Quote:
Originally Posted by Tracy Tiger View Post
I may eventually come to the same conclusion as Martinus2U.
just to elaborate, the intel driver stack supports a number of very differnt hardware, and the results may vary. I have or used to have machines with the following intel chip sets:

GM45: this one seems to be working just fine. Of course, the laptop will not do any taxing 3D applications or screen savers, but the daily workload is 100% solid.

GMA965: still crashing by random screen savers.

Clarkdale: long history of posting bugzilla entries and upgrading various stack components up to the craziness of compiling xorg myself. In the end xorg still segfaulted once a week which is lethal when you are in the middle of doing something important. Recently I've replaced this crap with an nvidia card and a Lynnfield CPU - which unfortunately runs hotter due to the 45nm process :-(

If Sandybridge support improves as quickly as Clarkdale did, you will be in the same position in two years time.
 
1 members found this post helpful.
Old 05-25-2012, 07:31 AM   #11
thund3rstruck
Member
 
Registered: Nov 2005
Location: East Coast, USA
Distribution: Fedora 18, Slackware64 13.37, Windows 7/8
Posts: 346

Original Poster
Rep: Reputation: 38
Quote:
Originally Posted by Tracy Tiger View Post
I was also trying to find out if this (common) MTRR error was of any consequence (intel graphics performance in my case). I found these two forum threads discussing this. There are more in various Linux distribution forums.

http://www.linuxquestions.org/questi...raphic-887537/

http://www.linuxquestions.org/questi...memory-903691/

I also found a thread where someone referenced more details in the kernel documents ( /usr/src/linux/Documentation/x86/mtrr.txt ).

The boot parameters involved (found at http://kernel.org/doc/Documentation/...parameters.txt) appear to be:
  • mtrr_chunk_size=n[KMG]
  • mtrr_gran_size=n[KMG]
  • mtrr_spare_reg_NR=n, n=0-7, default 1
  • enable_mtrr_cleanup
  • disable_mtrr_cleanup
  • disable_mtrr_trim

I set boot parameters according to one of the threads referenced above to get the MTRR error to go away. (It did NOT appear to affect/improve graphics performance in my case.

There are also a few settings in kernel configuration. (grep MTRR .config)

So to summarize, I also don't know anything about MTRR but thought I'd give you some items I discovered about it in case you need to pursue it. You could try setting some of the parameters to get the MTRR error to go away an see if it has an impact on your issue.

Perhaps someone knowledgeable can let us know if MTRR errors on boot are of any importance and how it impacts the system...or can we usually ignore them.

P.S. I should mention that I use the graphics on my Intel i5 Sandybridge and had tremendous problems (graphics, boot/acpi, i915 driver) on my Asus P8Z68-V LE motherboard the last few weeks. My main problems have gone away since I went to Slack(both 32 & 64) current and a 3.3.7 kernel. If I remember correctly the turning point was the current May 5th changes and the 3.2.x kernel. Just a note to a fellow Intel embedded graphics user. This is my first foray into the world of Intel graphics. I've always used Nvidia in the past. I may eventually come to the same conclusion as Martinus2U.
Wow, thanks for all this detail! I also have the i5 Sandy Bridge chipset. If I upgrade to -current is that going to be an upgrade or a new install? In other words, am I going to re-customize everything all over again (conky, cairo-dock, etc). It took me two weeks to build the perfect desktop and it makes me cringe thinking about having to do that all over again if I switch to -cuurent.

Here's my lspci output

Code:
bash-4.1$ su -c 'lspci -v'
Password: 
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
	Subsystem: Dell Device 04b0
	Flags: bus master, fast devsel, latency 0
	Capabilities: [e0] Vendor Specific Information: Len=0c <?>
	Kernel driver in use: agpgart-intel
	Kernel modules: intel-agp

00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
	Subsystem: Dell Device 04b0
	Flags: bus master, fast devsel, latency 0, IRQ 52
	Memory at f6800000 (64-bit, non-prefetchable) [size=4M]
	Memory at e0000000 (64-bit, prefetchable) [size=256M]
	I/O ports at f000 [size=64]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [d0] Power Management version 2
	Capabilities: [a4] PCI Advanced Features
	Kernel driver in use: i915
	Kernel modules: i915

00:16.0 Communication controller: Intel Corporation 6 Series Chipset Family MEI Controller #1 (rev 04)
	Subsystem: Dell Device 04b0
	Flags: bus master, fast devsel, latency 0, IRQ 11
	Memory at f7f0a000 (64-bit, non-prefetchable) [size=16]
	Capabilities: [50] Power Management version 3
	Capabilities: [8c] MSI: Enable- Count=1/1 Maskable- 64bit+

00:1a.0 USB Controller: Intel Corporation 6 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) (prog-if 20 [EHCI])
	Subsystem: Dell Device 04b0
	Flags: bus master, medium devsel, latency 0, IRQ 16
	Memory at f7f08000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: [50] Power Management version 2
	Capabilities: [58] Debug port: BAR=1 offset=00a0
	Capabilities: [98] PCI Advanced Features
	Kernel driver in use: ehci_hcd
	Kernel modules: ehci-hcd

00:1b.0 Audio device: Intel Corporation 6 Series Chipset Family High Definition Audio Controller (rev 05)
	Subsystem: Dell Device 04b0
	Flags: bus master, fast devsel, latency 0, IRQ 54
	Memory at f7f00000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [50] Power Management version 2
	Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
	Capabilities: [100] Virtual Channel
	Capabilities: [130] Root Complex Link
	Kernel driver in use: HDA Intel
	Kernel modules: snd-hda-intel

00:1c.0 PCI bridge: Intel Corporation 6 Series Chipset Family PCI Express Root Port 1 (rev b5) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=03, subordinate=04, sec-latency=0
	Capabilities: [40] Express Root Port (Slot+), MSI 00
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [90] Subsystem: Dell Device 04b0
	Capabilities: [a0] Power Management version 2
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:1c.1 PCI bridge: Intel Corporation 6 Series Chipset Family PCI Express Root Port 2 (rev b5) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=05, subordinate=06, sec-latency=0
	I/O behind bridge: 0000e000-0000efff
	Prefetchable memory behind bridge: 00000000f1100000-00000000f11fffff
	Capabilities: [40] Express Root Port (Slot+), MSI 00
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [90] Subsystem: Dell Device 04b0
	Capabilities: [a0] Power Management version 2
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:1c.3 PCI bridge: Intel Corporation 6 Series Chipset Family PCI Express Root Port 4 (rev b5) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=09, subordinate=0a, sec-latency=0
	Memory behind bridge: f7e00000-f7efffff
	Capabilities: [40] Express Root Port (Slot+), MSI 00
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [90] Subsystem: Dell Device 04b0
	Capabilities: [a0] Power Management version 2
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:1c.4 PCI bridge: Intel Corporation 6 Series Chipset Family PCI Express Root Port 5 (rev b5) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=0b, subordinate=0c, sec-latency=0
	Memory behind bridge: f7d00000-f7dfffff
	Capabilities: [40] Express Root Port (Slot+), MSI 00
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [90] Subsystem: Dell Device 04b0
	Capabilities: [a0] Power Management version 2
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:1c.7 PCI bridge: Intel Corporation 6 Series Chipset Family PCI Express Root Port 8 (rev b5) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=11, subordinate=1f, sec-latency=0
	I/O behind bridge: 0000c000-0000dfff
	Memory behind bridge: f6c00000-f7cfffff
	Prefetchable memory behind bridge: 00000000f0000000-00000000f10fffff
	Capabilities: [40] Express Root Port (Slot+), MSI 00
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [90] Subsystem: Dell Device 04b0
	Capabilities: [a0] Power Management version 2
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:1d.0 USB Controller: Intel Corporation 6 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) (prog-if 20 [EHCI])
	Subsystem: Dell Device 04b0
	Flags: bus master, medium devsel, latency 0, IRQ 23
	Memory at f7f07000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: [50] Power Management version 2
	Capabilities: [58] Debug port: BAR=1 offset=00a0
	Capabilities: [98] PCI Advanced Features
	Kernel driver in use: ehci_hcd
	Kernel modules: ehci-hcd

00:1f.0 ISA bridge: Intel Corporation HM67 Express Chipset Family LPC Controller (rev 05)
	Subsystem: Dell Device 04b0
	Flags: bus master, medium devsel, latency 0
	Capabilities: [e0] Vendor Specific Information: Len=0c <?>
	Kernel modules: iTCO_wdt

00:1f.2 SATA controller: Intel Corporation 6 Series Chipset Family 6 port SATA AHCI Controller (rev 05) (prog-if 01 [AHCI 1.0])
	Subsystem: Dell Device 04b0
	Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 45
	I/O ports at f0b0 [size=8]
	I/O ports at f0a0 [size=4]
	I/O ports at f090 [size=8]
	I/O ports at f080 [size=4]
	I/O ports at f060 [size=32]
	Memory at f7f06000 (32-bit, non-prefetchable) [size=2K]
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [70] Power Management version 3
	Capabilities: [a8] SATA HBA v1.0
	Capabilities: [b0] PCI Advanced Features
	Kernel driver in use: ahci

00:1f.3 SMBus: Intel Corporation 6 Series Chipset Family SMBus Controller (rev 05)
	Subsystem: Dell Device 04b0
	Flags: medium devsel, IRQ 18
	Memory at f7f05000 (64-bit, non-prefetchable) [size=256]
	I/O ports at f040 [size=32]
	Kernel modules: i2c-i801

05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 05)
	Subsystem: Dell Device 04b0
	Flags: bus master, fast devsel, latency 0, IRQ 51
	I/O ports at e000 [size=256]
	Memory at f1104000 (64-bit, prefetchable) [size=4K]
	Memory at f1100000 (64-bit, prefetchable) [size=16K]
	Capabilities: [40] Power Management version 3
	Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [70] Express Endpoint, MSI 01
	Capabilities: [b0] MSI-X: Enable- Count=4 Masked-
	Capabilities: [d0] Vital Product Data
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Virtual Channel
	Capabilities: [160] Device Serial Number 01-00-00-00-36-4c-e0-00
	Kernel driver in use: r8169
	Kernel modules: r8169

09:00.0 Network controller: Intel Corporation Centrino Wireless-N 1030 (rev 34)
	Subsystem: Intel Corporation Centrino Wireless-N 1030 BGN
	Flags: bus master, fast devsel, latency 0, IRQ 53
	Memory at f7e00000 (64-bit, non-prefetchable) [size=8K]
	Capabilities: [c8] Power Management version 3
	Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [e0] Express Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Device Serial Number 4c-eb-42-ff-ff-71-93-f0
	Kernel driver in use: iwlagn
	Kernel modules: iwlagn

0b:00.0 USB Controller: Texas Instruments Device 8241 (rev 02) (prog-if 30 [XHCI])
	Subsystem: Dell Device 04b0
	Flags: bus master, fast devsel, latency 0, IRQ 16
	Memory at f7d00000 (64-bit, non-prefetchable) [size=64K]
	Memory at f7d10000 (64-bit, non-prefetchable) [size=8K]
	Capabilities: [40] Power Management version 3
	Capabilities: [48] MSI: Enable- Count=1/8 Maskable- 64bit+
	Capabilities: [70] Express Endpoint, MSI 00
	Capabilities: [c0] MSI-X: Enable+ Count=8 Masked-
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [150] Device Serial Number 08-00-28-00-00-20-00-00
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci-hcd
 
Old 05-25-2012, 08:02 AM   #12
Martinus2u
Member
 
Registered: Apr 2010
Distribution: Slackware
Posts: 350

Rep: Reputation: 56
Quote:
Originally Posted by thund3rstruck View Post
I also have the i5 Sandy Bridge chipset.
In that case it is worth a try to upgrade every component of the graphics stack to the latest possible, including the kernel:

http://intellinuxgraphics.org/2012.02.html

Quote:
Originally Posted by thund3rstruck View Post
If I upgrade to -current is that going to be an upgrade or a new install? In other words, am I going to re-customize everything all over again (conky, cairo-dock, etc).
In theory you should be safe. But then there is Murphy's Law.
 
Old 05-25-2012, 10:40 AM   #13
thund3rstruck
Member
 
Registered: Nov 2005
Location: East Coast, USA
Distribution: Fedora 18, Slackware64 13.37, Windows 7/8
Posts: 346

Original Poster
Rep: Reputation: 38
Quote:
Originally Posted by Martinus2u View Post
In that case it is worth a try to upgrade every component of the graphics stack to the latest possible, including the kernel:

http://intellinuxgraphics.org/2012.02.html

In theory you should be safe. But then there is Murphy's Law.
Ok, I'll try an in place upgrade to -current this weekend. It took so long to get my system the way I want it that I don't have the stomach for hacking at the graphics stack lest I totally bork the machine and have to start all over again!

Thanks again guys!
 
Old 05-25-2012, 12:12 PM   #14
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 875

Rep: Reputation: 1819Reputation: 1819Reputation: 1819Reputation: 1819Reputation: 1819Reputation: 1819Reputation: 1819Reputation: 1819Reputation: 1819Reputation: 1819Reputation: 1819
You might start by just upgrading to the libdrm and mesa that shipped with 13.37 in /testing. Maybe that would help.
 
Old 05-25-2012, 05:10 PM   #15
TracyTiger
Member
 
Registered: Apr 2011
Location: California, USA
Distribution: Slackware
Posts: 290

Rep: Reputation: 72
Quote:
Originally Posted by thund3rstruck View Post
Ok, I'll try an in place upgrade to -current this weekend. It took so long to get my system the way I want it that I don't have the stomach for hacking at the graphics stack lest I totally bork the machine and have to start all over again!
I should mention that my three new Asus boards are not yet in production. I'm still fiddling with the recipe to run the equipment in a production environment. So I did not just upgrade. I've reloaded the OS from scratch many times and had no previous settings to preserve. So please don't take my previous post to mean you can just upgrade to current without impacting things.

Quote:
Originally Posted by thund3rstruck View Post
Here's my lspci output

Code:
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
	Subsystem: Dell Device 04b0
	Flags: bus master, fast devsel, latency 0, IRQ 52
	Memory at f6800000 (64-bit, non-prefetchable) [size=4M]
	Memory at e0000000 (64-bit, prefetchable) [size=256M]
	I/O ports at f000 [size=64]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [d0] Power Management version 2
	Capabilities: [a4] PCI Advanced Features
	Kernel driver in use: i915
	Kernel modules: i915
I had much more severe issues than you. The i915 driver would not actually run without acpi and the system wouldn't boot without acpi turned off. I gradually worked my way up to moving the system to -current and replacing the kernel before I saw results.

Quote:
Originally Posted by Martinus2u View Post
In that case it is worth a try to upgrade every component of the graphics stack to the latest possible, including the kernel:

http://intellinuxgraphics.org/2012.02.html
Martinus2u suggestion is not a bad one. I considered it a few weeks ago and in my exploration I made a weak attempt at updating files from the intellinuxgraphics.org site but I was confused how the pieces fit together and lacked the knowledge to make it work properly.

TobiSGD gave me the same advice Mr. Volkerding just gave you. It sounds like the lowest risk first step before you try riskier alternatives.

Quote:
Originally Posted by thund3rstruck View Post
It took so long to get my system the way I want it that I don't have the stomach for hacking at the graphics stack lest I totally bork the machine and have to start all over again!
How many times do we read on this forum that a member spent a lot of time trying to solve a problem and was only able to finally solve the problem when they reloaded the software. Just a thought unpleasant as it may be.

Last edited by TracyTiger; 05-25-2012 at 05:14 PM.
 
1 members found this post helpful.
  


Reply

Tags
firefox, slackware


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Machine Locks Up When Hibernating / Suspend carlosinfl Linux - Laptop and Netbook 2 11-26-2010 04:45 PM
Suse 9.3 install locks up my machine Joe Phoebus Linux - Hardware 1 07-29-2005 04:33 PM
Machine locks up hard when compiling software buddha joe Linux - Software 6 04-27-2004 05:53 PM
Machine locks up at 100% usage... vbp6us Linux - General 10 08-18-2003 02:24 PM
Yast2 Locks machine dbs Linux - Software 0 08-17-2002 05:34 PM


All times are GMT -5. The time now is 10:03 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration