SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hello!
I just installed Slackware 12.1 with kernel vmlinuz-generic-smp-2.6.24.5-smp. I generated my xorg.conf with xorgsetup. I have the following problem. Sometimes my X server starts ok, but sometimes it fails. I generated a diff from the Xorg.0.log files in both cases. Here is the output of diff between the successful Xorg.0.log and the one generated after a freezing:
23c23
< (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 16 14:57:24 2008
---
> (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 16 14:23:54 2008
250c250
< (II) Loading /usr/lib/xorg/modules//fonts/libfreetype.so
---
> (II) Loading /usr/lib/xorg/modules/fonts//libfreetype.so
257c257
< (II) Loading /usr/lib/xorg/modules//fonts/libtype1.so
---
> (II) Loading /usr/lib/xorg/modules/fonts//libtype1.so
488c488,490
< drmOpenDevice: open result is 10, (OK)
---
> drmOpenDevice: open result is -1, (No such device or address)
> drmOpenDevice: open result is -1, (No such device or address)
> drmOpenDevice: Open failed
490c492,494
< drmOpenDevice: open result is 10, (OK)
---
> drmOpenDevice: open result is -1, (No such device or address)
> drmOpenDevice: open result is -1, (No such device or address)
> drmOpenDevice: Open failed
495a500
> (II) [drm] loaded kernel module for "i915" driver.
539c544
< (II) intel(0): 0x000df000-0x000dffff: overlay registers (4 kB, 0x0000000035f74000 physical
---
> (II) intel(0): 0x000df000-0x000dffff: overlay registers (4 kB, 0x00000000331fe000 physical
551c556
< (II) intel(0): [drm] dma control initialized, using IRQ 18
---
> (II) intel(0): [drm] dma control initialized, using IRQ 17
626a632,683
> Error in I830WaitLpRing(), timeout for 2 seconds
> pgetbl_ctl: 0x4ffe0001getbl_err: 0x39
> ipeir: 0 iphdr: 54f00006
> LP ring tail: 1fe0 head: 2000 len: 1f001 start 0
> eir: 0 esr: 10 emr: ff7b
> instdone: ffc1 instpm: 0
> memmode: 0 instps: 20
> hwstam: fffe ier: 2 imr: 53c iir: 80
> Ring at virtual 0xafa26000 head 0x2000 tail 0x1fe0 count 32760
> 00001f80: 00000000
> 00001f84: 00000000
> 00001f88: 00000000
> 00001f8c: 00000000
> 00001f90: 00000000
> 00001f94: 00000000
> 00001f98: 00000000
> 00001f9c: 00000000
> 00001fa0: 00000000
> 00001fa4: 00000000
> 00001fa8: 00000000
> 00001fac: 00000000
> 00001fb0: 00000000
> 00001fb4: 00000000
> 00001fb8: 00000000
> 00001fbc: 00000000
> 00001fc0: 00000000
> 00001fc4: 00000000
> 00001fc8: 00000000
> 00001fcc: 00000000
> 00001fd0: 00000000
> 00001fd4: 00000000
> 00001fd8: 00000000
> 00001fdc: 00000000
> 00001fe0: 00000000
> 00001fe4: 00000000
> 00001fe8: 00000000
> 00001fec: 00000000
> 00001ff0: 00000000
> 00001ff4: 00000000
> 00001ff8: 00000000
> 00001ffc: 00000000
> 00002000: f000eef3
> Ring end
> space: 24 wanted 32
> (II) intel(0): [drm] removed 1 reserved context for kernel
> (II) intel(0): [drm] unmapping 8192 bytes of SAREA 0xf8f0c000 at 0xb7b5f000
> (II) intel(0): [drm] Closed DRM master.
>
> Fatal server error:
> lockup
>
> (II) AIGLX: Suspending AIGLX clients for VT switch
I googled a lot. Some users report a solution to this problem by disabling direct rendering in xorg.conf. However, this does not solve the promlem in my case:
I looked at the threads you suggested. So long I as I could understand the solution should be reinstalling the
xf86-video-intel-2.2.1-i486-1.tgz
xf86-video-i810-1.7.4-i486-2.tgz
packages. I did that and then startx started working. I reenabled DRI and there was no problem. However, when I rebooted this morning the old problem reappeared. It was even worse: just a black screen, not even jumbled colours. After I rebooted there was no error message in Xorg.0.log, but /var/log/syslog reported:
May 17 10:23:06 marto kernel: Using IPI No-Shortcut mode
May 17 10:23:06 marto kernel: rtc_cmos: probe of 00:02 failed with error -16
May 17 10:23:06 marto kernel: ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is not present [20070126]
May 17 10:23:06 marto kernel: intel_rng: Firmware space is locked read-only. If you can't or
May 17 10:23:06 marto kernel: intel_rng: don't want to disable this in firmware setup, and if
May 17 10:23:06 marto kernel: intel_rng: you are certain that your system has a functional
May 17 10:23:06 marto kernel: intel_rng: RNG, try using the 'no_fwh_detect' option.
I tried adding "options intel_rng no_fwh_detect" to a file in /etc/modprobe.d, but there was no effect. Then I removed this option and reinstalled the two above mentioned packages once again. I got the screen with jumbled colours and system freeze. What I finally did is disabling DRI and Composite in xorg.conf. Now I can startx. It seems that after rebooting startx is also succesful, but I do not bet. I really do not know what will happen when I reboot tomorrow.
Does someone see any further than me? I have no clue.
After I rebooted there was no error message in Xorg.0.log, but /var/log/syslog reported:
May 17 10:23:06 marto kernel: Using IPI No-Shortcut mode
May 17 10:23:06 marto kernel: rtc_cmos: probe of 00:02 failed with error -16
May 17 10:23:06 marto kernel: ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is not present [20070126]
May 17 10:23:06 marto kernel: intel_rng: Firmware space is locked read-only. If you can't or
May 17 10:23:06 marto kernel: intel_rng: don't want to disable this in firmware setup, and if
May 17 10:23:06 marto kernel: intel_rng: you are certain that your system has a functional
May 17 10:23:06 marto kernel: intel_rng: RNG, try using the 'no_fwh_detect' option.
I tried adding "options intel_rng no_fwh_detect" to a file in /etc/modprobe.d, but there was no effect.
This errors are not Xorg related: CONFIG_RTC option is enabled unconditionally in kernel .config file, an ACPI Exception error related to your motherboard capabilities and an Intel Random Number Generator error, related to your motherboard too.
Back to X server, can you post here your xorg.conf file?
Here is my xorg.conf. I posted it in my first post, but here it is again with the DRI and Composite disabled so that I can startx. I should emphasize that disabling that functionality did not work until I reinstalled the two packages suggested.
Did you try without these 2 lines above?
Did you try with:
Code:
Driver "i810"
Previously I had tried without the Modeline and displaysize with no difference. Now I experimented with Driver i810 and ran into another epic of frustration. Right after the change I reenabled the DRI and Composite and X started ok. There was direct rendering. I rebooted to make sure that things are finally stable. Again the jumbled colours freeze. I disabled DRI and Composite, but troubles persisted. I reinstalled the two packages first
xf86-video-intel-2.2.1-i486-1.tgz and then
xf86-video-i810-1.7.4-i486-2.tgz. Again freeze. I reinstalled them in reversed order and then started X ok. Now I am writing from X and I am really afraid to reboot ...
After some more experimenting I found out that the only way to startx successfully after a reboot is to first reinstall the xf86-video-intel-2.2.1-i486-1.tgz package and then issue startx.
Does someone know how to solve that frustrating issue? I do not feel like reinstalling that package each time I boot. As a last resort I will add "installpkg xf86-video-intel-2.2.1-i486-1.tgz" to my rc.local.
So I have the following final results for the weird behaviour of my 12.1 system:
After a fresh reboot startx always fails with a server lockup.
After a fresh reboot with a fresh installation of the stock xf86-video-intel package, startx is successful provided that DRI is disabled in xorg.conf.
X starts ok with direct rendering only if:
1.Reboot 2.startx with the DRI-disabled xorg.conf. 3. log out of X and startx with the DRI enabled xorg.conf. If I attempt to startx with the DRI-enabled xorg.conf directly after a fresh installation of the xf86-video-intel package, I end up with the lockup and system freeze.
My system used to work quite stably and predictably in 12.0. I have no idea what is happening at all. I would be thankful if you give some clues on what else I could check to track down what actually is happening. I would be happy if you at least direct me to the suitable forum to ask about these weird X server lockups. So long as I can see from google, the latter do not seem to be Slackware specific, although some slackers have found individual solutions.
OK, this is seems to have nothing to do with the two packages above. After I added their installing to rc.local, at some reboots startx was successful and at some not.
I kompared the difference between the Xorg.0.logs after a successful and after an unsuccessful startx and these are the only different lines:
However, I have the same onboard video (Intel 82845G/GL) and what I have found is that in 12.1 the "i810" driver gives me the best results. The intel driver was too unpredictable and gave errors. Don't keep reinstalling both drivers because from what I understand the whole problem is that they share common files that are overwriting each other.
Reinstall the "i810" driver and only that one. You can do that from console so don't bother starting up X yet. Then run xorgconfig (not xorgsetup) and walk through the steps. It's very straightforward, but make sure you know the horizontal and vertical sync range for your monitor. When asked which driver to use select "i810".
However, I have the same onboard video (Intel 82845G/GL) and what I have found is that in 12.1 the "i810" driver gives me the best results. The intel driver was too unpredictable and gave errors. Don't keep reinstalling both drivers because from what I understand the whole problem is that they share common files that are overwriting each other.
Reinstall the "i810" driver and only that one. You can do that from console so don't bother starting up X yet. Then run xorgconfig (not xorgsetup) and walk through the steps. It's very straightforward, but make sure you know the horizontal and vertical sync range for your monitor. When asked which driver to use select "i810".
That worked for me and my video flies now.
Dig
Thank you very much indeed! That worked. I reinstalled only the i810 driver, changed the driver in xorg.conf from "intel" to "i810", added my monitor's refresh rates and everything seems all right now. At least after 4 consecutive reboots startx is successful. Thank you again!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
