Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
i915 not working
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2  
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 31980
Location: 56N 3W

PostPosted: Wed Jul 24, 2013 8:28 pm    Post subject: Reply with quote

deltamalloc,

I suspect an issue with slim or its setup.

Remove xdm from the defualt runlevel and kill its processes if they are running.

Code:
emerge -1 twm xclock xterm


When that completes, run startx with your ~/.xinitrc file, if you have one, renamed.
You should get twm, with three xterms and a clock.

This will confirm that Xorg and a simple window manger work.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
deltamalloc
Tux's lil' helper
Tux's lil' helper


Joined: 18 Jan 2013
Posts: 135

PostPosted: Sat Jul 27, 2013 7:51 am    Post subject: Reply with quote

I broke my system in desperation while trying to get this to work (before reading that last comment).

I did

Code:

# emerge --update --deep --with-bdeps=y world
# emerge --depclean
# revdep-rebuild


X fails to start at all now.

I got a blank screen with backlight staying on, not able to kill it with ctrl+alt+backspace, ctrl+c, ctrl+z or by switching back to console.
There was nothing in Xorg.log.0, in fact it contained nothing at all (0 bytes). There was nothing of interest in dmesg. I did not change anything beyond running those commands.

Then I did:

Code:

emerge -e world


This took forever. But the result is exactly the same. X fails to start at all.

Does anyone have any idea what is causing this?
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 31980
Location: 56N 3W

PostPosted: Sat Jul 27, 2013 5:42 pm    Post subject: Reply with quote

deltamalloc,

You ran the following commands in the wrong order.
Code:
# emerge --depclean
# revdep-rebuild

Also --depclean has been known to remove things you would rather keep.

Boot with the liveCD,
mount your root filesystem at /mnt/gentoo
cd to /mnt/gentoo/etc/runlevels/default
delete xdm

This is the same as doing
Code:
rc-update del xdm default


You should now be able to reboot without the CD and get to a login: prompt.
Once you can log in as root, you can use
Code:
emerge -uDNav xorg-server
to fix Xorg.
Only things that are out of date, missing or have changed USE flags will be compiled.
Ideally that will be nothing.

Then you can test with my post above.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
deltamalloc
Tux's lil' helper
Tux's lil' helper


Joined: 18 Jan 2013
Posts: 135

PostPosted: Sun Jul 28, 2013 5:58 am    Post subject: Reply with quote

NeddySeagoon wrote:
deltamalloc,

You ran the following commands in the wrong order.
Code:
# emerge --depclean
# revdep-rebuild

Also --depclean has been known to remove things you would rather keep.

Boot with the liveCD,
mount your root filesystem at /mnt/gentoo
cd to /mnt/gentoo/etc/runlevels/default
delete xdm

This is the same as doing
Code:
rc-update del xdm default


You should now be able to reboot without the CD and get to a login: prompt.
Once you can log in as root, you can use
Code:
emerge -uDNav xorg-server
to fix Xorg.
Only things that are out of date, missing or have changed USE flags will be compiled.
Ideally that will be nothing.

Then you can test with my post above.


I booted with "single" as argument to my kernel image in lilo. This let me just chmod -x xdm in /etc/init.d.

I then did:

Code:

emerge -uDNav xorg-server
emerge -1 twm xclock xterm


The results are the same.

I get a blank screen which I cannot get out of. Nothing in the logs.

This happens when I do startx too, therefore it seems unlikely slim has anything to do with it.

I do however have one interesting piece of information in my dmesg:

Code:

[Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module parameter "video.allow_duplicates=1" if the current driver doesn't work.


However, this didn't prevent me from starting X before. If this is related to the OpenGL-problem, I do not know.

I tried passing "video.allow_duplicates=1" to my kernel with an append statement in lilo.conf, ran lilo again and rebooted. Nothing. I tried this with both 3.10.1 and 3.10.2, 3.10.1 could start X before anyway, so it seems strange this would be related.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 31980
Location: 56N 3W

PostPosted: Sun Jul 28, 2013 10:02 am    Post subject: Reply with quote

deltamalloc,

Emerge wgetpaste, if you don't already have it and use it to post your Xorg.0.log and dmesg

Thats
Code:
dmesg | wgetpaste
wgetpaste /var/log/Xorg.0.log

Post the URLs that wgetpaste returns.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
deltamalloc
Tux's lil' helper
Tux's lil' helper


Joined: 18 Jan 2013
Posts: 135

PostPosted: Sun Jul 28, 2013 4:11 pm    Post subject: Reply with quote

NeddySeagoon wrote:
deltamalloc,

Emerge wgetpaste, if you don't already have it and use it to post your Xorg.0.log and dmesg

Thats
Code:
dmesg | wgetpaste
wgetpaste /var/log/Xorg.0.log

Post the URLs that wgetpaste returns.


As I've mentioned my Xorg.0.log contains 0 bytes, regardless of how many times I try starting X.

However dmesg I can certainly put up: http://bpaste.net/show/118085/
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 31980
Location: 56N 3W

PostPosted: Sun Jul 28, 2013 4:57 pm    Post subject: Reply with quote

deltamalloc,

dmesg is OK. You get your framebuffer console which indicates the kernel is in good shape.

What does
Code:
df -T
when its run as root?
It will give different answers when run as a normal user as extX flesystems have 5% reserved for root by default. This prevents normal users from crashing the system by filling up partitions. There is always space for root to write logs and lockfiles.

For Xorg to get far enough to clear the screen bit not leave a log suggests that you may be out of space.

You may do
Code:
rm -rf /var/tmp/portage
to remove the remains of broken builds to free some space ... but not while emerge is running.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
deltamalloc
Tux's lil' helper
Tux's lil' helper


Joined: 18 Jan 2013
Posts: 135

PostPosted: Sun Jul 28, 2013 9:24 pm    Post subject: Reply with quote

NeddySeagoon wrote:
deltamalloc,

dmesg is OK. You get your framebuffer console which indicates the kernel is in good shape.

What does
Code:
df -T
when its run as root?
It will give different answers when run as a normal user as extX flesystems have 5% reserved for root by default. This prevents normal users from crashing the system by filling up partitions. There is always space for root to write logs and lockfiles.

For Xorg to get far enough to clear the screen bit not leave a log suggests that you may be out of space.

You may do
Code:
rm -rf /var/tmp/portage
to remove the remains of broken builds to free some space ... but not while emerge is running.


Creative suggestion, I've actually been surprised to find before that the reason my system was broken was due to no free space left, giving me strange errors.

However this is not the case this time unfortunately. I only use about 31% of the root file system (and I only have one file system for everything), 18 GB free.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 31980
Location: 56N 3W

PostPosted: Sun Jul 28, 2013 10:30 pm    Post subject: Reply with quote

deltamalloc,

Maybe its some rubbish left over that would normally be cleared.

Make a new user then run startx as that user.
Do not call the new user test. Its the first thing someone trying to break into your system would guess.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
deltamalloc
Tux's lil' helper
Tux's lil' helper


Joined: 18 Jan 2013
Posts: 135

PostPosted: Mon Jul 29, 2013 5:24 pm    Post subject: Reply with quote

NeddySeagoon wrote:
deltamalloc,

Maybe its some rubbish left over that would normally be cleared.

Make a new user then run startx as that user.
Do not call the new user test. Its the first thing someone trying to break into your system would guess.


I tried this and sadly got the same result. Blank/black (but lit with backlight) screen, not able to get back out.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 31980
Location: 56N 3W

PostPosted: Mon Jul 29, 2013 5:44 pm    Post subject: Reply with quote

deltamalloc,

Try rebuilding the Xorg video driver and input driver you need. That will be
Code:
emerge -1 xf86-video-intel xf86-input-evdev


To save pulling the pug out and risking corrupt filesystems to regain control, try
Code:
startx; sleep 30 && killall X

This startsx, waits 30 seconds, then kills the X server if its running.
You may need to get back to your console with Ctrl-Alt-F1
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
deltamalloc
Tux's lil' helper
Tux's lil' helper


Joined: 18 Jan 2013
Posts: 135

PostPosted: Tue Jul 30, 2013 1:49 pm    Post subject: Reply with quote

NeddySeagoon wrote:
deltamalloc,

Try rebuilding the Xorg video driver and input driver you need. That will be
Code:
emerge -1 xf86-video-intel xf86-input-evdev


To save pulling the pug out and risking corrupt filesystems to regain control, try
Code:
startx; sleep 30 && killall X

This startsx, waits 30 seconds, then kills the X server if its running.
You may need to get back to your console with Ctrl-Alt-F1


I have tried the following:

1: Rebuild everything with emerge -e world.
2: Rebuild everything related to Xorg.
3: Rebuild only the drivers.
4: Try with vesa drivers, this starts X but gives me artifacts and low resolution, display data channel appears not to be working; I can see in the X log that it uses default parameters for refresh rate, sync rates and pixel clock.
5: Verified that the hardware is still working, a livecd boots fine with i915 and full resolution, no artifacts.
6: Tried at least three different kernels (3.8.13, 3.10.1 and 3.10.2, and one unstable as a desperate attempt).

The fact that DDC is not working can be verified with the read-edid tool and with xrandr. read-edid cannot get the EDID data and xrandr only shows 640x480 as resolution when running with vesa. However DDC obviously works, hardware-wise, as the livecd boots fine and can read this data which it needs in order to start X.
Back to top
View user's profile Send private message
albright
Advocate
Advocate


Joined: 16 Nov 2003
Posts: 2097
Location: Near Toronto

PostPosted: Tue Jul 30, 2013 2:08 pm    Post subject: Reply with quote

what a painful journey you have been on

since originally X worked fine for you, it may be
that depclean removed something important that
has not been replaced (I have no idea what that
would be)

given the time already invested, why not re-install
from scratch and get X back, then work on the
opengl problem?
_________________
.... there is nothing - absolutely nothing - half so much worth
doing as simply messing about with Linux ...
(apologies to Kenneth Graeme)
Back to top
View user's profile Send private message
deltamalloc
Tux's lil' helper
Tux's lil' helper


Joined: 18 Jan 2013
Posts: 135

PostPosted: Tue Jul 30, 2013 3:56 pm    Post subject: Reply with quote

albright wrote:
what a painful journey you have been on

since originally X worked fine for you, it may be
that depclean removed something important that
has not been replaced (I have no idea what that
would be)

given the time already invested, why not re-install
from scratch and get X back, then work on the
opengl problem?


I try to avoid doing this though, since I'll never know what was the problem, and not really have learned anything from the experience. But it doesn't seem like anyone has any better ideas, so I'll reinstall.
Back to top
View user's profile Send private message
deltamalloc
Tux's lil' helper
Tux's lil' helper


Joined: 18 Jan 2013
Posts: 135

PostPosted: Wed Jul 31, 2013 7:21 am    Post subject: Reply with quote

I have now reinstalled Gentoo.

X is working again. As before I do not get OpenGL working.

I have only followed these guides:

http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1
http://www.gentoo.org/doc/en/xorg-config.xml

That is, I haven't emerged anything else.

This is the error (same as before):

Code:

$ glxgears
libGL error: failed to load driver: i915
libGL error: Try again with LIBGL_DEBUG=verbose for more details.
DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [9]
param: 4, val: 100
Segmentation fault
Back to top
View user's profile Send private message
deltamalloc
Tux's lil' helper
Tux's lil' helper


Joined: 18 Jan 2013
Posts: 135

PostPosted: Wed Jul 31, 2013 12:16 pm    Post subject: Reply with quote

Solution:

Set "mesa" with eselect to classic instead of gallium.

No idea why gallium shouldn't work though. Is this a kernel bug or user space bug, or a configuration problem?
Back to top
View user's profile Send private message
albright
Advocate
Advocate


Joined: 16 Nov 2003
Posts: 2097
Location: Near Toronto

PostPosted: Wed Jul 31, 2013 2:53 pm    Post subject: Reply with quote

Quote:
No idea why gallium shouldn't work though.


I assume that you have upgraded to the newest mesa?

you could try a masked version (e.g. I am using 9.1.5)

EDIT: also, what makes you think gallium ever worked/works with
855gm chip?
_________________
.... there is nothing - absolutely nothing - half so much worth
doing as simply messing about with Linux ...
(apologies to Kenneth Graeme)
Back to top
View user's profile Send private message
deltamalloc
Tux's lil' helper
Tux's lil' helper


Joined: 18 Jan 2013
Posts: 135

PostPosted: Wed Jul 31, 2013 5:59 pm    Post subject: Reply with quote

albright wrote:
Quote:
No idea why gallium shouldn't work though.


I assume that you have upgraded to the newest mesa?

you could try a masked version (e.g. I am using 9.1.5)

EDIT: also, what makes you think gallium ever worked/works with
855gm chip?


I did upgrade to the newest mesa, yes.

What makes me think Gallium worked/works with 855GM is the following:

1) Gallium has supposedly a software renderer.
2) I receive a segmentation fault instead of a warning or error telling me the hardware is not supported.
3) No one pointed out that Gallium does not support 855GM.
Back to top
View user's profile Send private message
hololeap
n00b
n00b


Joined: 05 Oct 2013
Posts: 9

PostPosted: Tue Oct 08, 2013 3:10 pm    Post subject: Reply with quote

I have been having a similar problem with the Intel 82865G/PE/P. I have not found any documentation saying which chipsets are not supported by Gallium. If anyone can point me to a link, I would really appreciate it.
Back to top
View user's profile Send private message
FizzyWidget
Veteran
Veteran


Joined: 21 Nov 2008
Posts: 1113
Location: 127.0.0.1

PostPosted: Tue Oct 08, 2013 3:40 pm    Post subject: Reply with quote

I have been having similar issues with the Intel HD4000 - in the end i fixed it by just having intel only in make.conf in video cards
_________________
I know 43 ways to kill with a SKITTLE, so taste my rainbow bitch.
Back to top
View user's profile Send private message
Gusar
Advocate
Advocate


Joined: 09 Apr 2005
Posts: 2643
Location: Slovenia

PostPosted: Tue Oct 08, 2013 4:58 pm    Post subject: Reply with quote

hololeap wrote:
I have been having a similar problem with the Intel 82865G/PE/P. I have not found any documentation saying which chipsets are not supported by Gallium. If anyone can point me to a link, I would really appreciate it.

I don't know if there's any link that shows it all nicely in a table, but it goes like this (g = gallium, c = classic):

  • i915c: gen2, gen3

  • i915g: gen3 - note, not developed by Intel but by Google

  • i965c: gen4, gen5, gen6, gen7, gen7.5

  • i965g: gen6, gen7 - note, this driver is very incomplete and a lot slower than i965c; it's not developed by Intel, it's a hobby project of a single developer

  • not supported by mesa: GMA500 (Poulsbo), GMA3600/3650 (Cedarview)

Refer to the nice list at wikipedia to know what GPU falls into which generation: http://en.wikipedia.org/wiki/Comparison_of_Intel_graphics_processing_units

You have a 865, which is gen2, so there's only one driver for you - i915c
Back to top
View user's profile Send private message
Jonathan_R
n00b
n00b


Joined: 21 Mar 2011
Posts: 17

PostPosted: Fri Mar 07, 2014 11:12 am    Post subject: Reply with quote

What I did to fix this was rather simple. I found this thread since I was having the same issue. I read all the posts, and then did this; in package.use I added this line.
Code:
>=media-libs/mesa-10.0.3 video_cards_i915 video_cards_i965 video_cards_intel gallium vdpau
I then ran emerge --changed-use =media-libs/mesa-10.0.3
Then ldd shows
Code:
# ldd /usr/lib/mesa/i965_dri.so
        linux-vdso.so.1 (0x00007ffff49ff000)
        libdrm_intel.so.1 => /usr/lib64/libdrm_intel.so.1 (0x00007f59c448f000)
        libdrm.so.2 => /usr/lib64/libdrm.so.2 (0x00007f59c4283000)
        libexpat.so.1 => /usr/lib64/libexpat.so.1 (0x00007f59c4058000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f59c3e3a000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007f59c3c36000)
        libstdc++.so.6 => /usr/lib/gcc/x86_64-pc-linux-gnu/4.8.2/libstdc++.so.6 (0x00007f59c3932000)
        libm.so.6 => /lib64/libm.so.6 (0x00007f59c362f000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f59c3287000)
        libgcc_s.so.1 => /usr/lib/gcc/x86_64-pc-linux-gnu/4.8.2/libgcc_s.so.1 (0x00007f59c3070000)
        libpciaccess.so.0 => /usr/lib64/libpciaccess.so.0 (0x00007f59c2e67000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f59c4d4e000)
        libz.so.1 => /lib64/libz.so.1 (0x00007f59c2c50000)


Problem solved.
Back to top
View user's profile Send private message
Jonathan_R
n00b
n00b


Joined: 21 Mar 2011
Posts: 17

PostPosted: Fri Mar 07, 2014 11:17 am    Post subject: Reply with quote

Someone should update the Intel wiki page; http://wiki.gentoo.org/wiki/Intel to include these details.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Goto page Previous  1, 2
Page 2 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum