[Solved] X11 issue - intel driver

darkeye · 2010-05-03 23:39:08

Hello all,

Although I'm not new to the world of Linux, and I have used Arch before, for whatever reason I cannot get X11 and KDM to work.

Here's the story:

I install Arch Linux off a cd, enable the repositories, and update it.
Then I install kdemod-complete by adding those repositiories, and now I want to add kdm to startup in order to boot into kde.

Now here's the thing. I modified my Inittab to run level 5 and changed the display manger to kdm.
Upon boot, It boots up awesomely and quickly, and then, right after loading the Hardware Abstraction Layer I get a message.
Its really hard to read, since it goes by really fast, but it has to do with /var/run/dbus.pid and the message bus.
After that, I got a blank screen with a cursor flashing, which I'm supposing is when X11 should kick in.

So, Understanding that I have quite the issue on my hands, I boot up into a live cd, change the inittab back to normal, and reboot.
I then check my /var/log and notice that I have a log from Xorg, which says that I have no screens available, and that several drivers failed to load.
Coincidentally, one of those was the xf86-video-intel driver, which I promptly installed with pacman -S. (Because my graphics chipset is intel.)

I then change my inittab to load up kdm again, and I get the same flipping blank screen with a cursor.
After changing it back, I examine the Xorg log again, which this time tells me that the intel_srv.so (or something like that) file is too short, and wasn't loaded.

Anyone have any ideas on how to get my computer up and running?

If you need any more information, like output from commands or something, just ask and ill post em.

Thanks again!

Last edited by darkeye (2010-05-04 23:21:00)

demian · 2010-05-03 23:53:08

Whats your daemons array?

grey · 2010-05-04 00:08:27

Can you start X from the command line? Can you start KDE from the command line? Did you try another display manager (e.g. Slim)?

darkeye · 2010-05-04 00:13:52

@grey:
I can't even configure Xorg. I keep getting that driver file is too short error.
startx doesnt work, and neither does startkde, unless i have those commands wrong. :S
It says command not found.

@demian:
I'd have to boot into linux to check it out, So I'll post that when I get home.
But the only things I added to my daemons array are hal and dbus.

Thanks!

cesura · 2010-05-04 00:15:43

darkeye wrote:

@grey:
I can't even configure Xorg. I keep getting that driver file is too short error.
startx doesnt work, and neither does startkde, unless i have those commands wrong. :S
It says command not found.
@demian:
I'd have to boot into linux to check it out, So I'll post that when I get home.
But the only things I added to my daemons array are hal and dbus.
Thanks!

Does it give a path to that file? Usually that means it is blank.

Try:

cat /path/to/driver/file

grey · 2010-05-04 00:23:22

darkeye wrote:

@grey:
I can't even configure Xorg. I keep getting that driver file is too short error.
startx doesnt work, and neither does startkde, unless i have those commands wrong. :S

How *exactly* are you using these commands?

darkeye wrote:

@grey:
It says command not found.

Which command? Pls. try to be a bit more precise.

darkeye · 2010-05-04 00:32:40

@grey:
startx returns a command not found from bash.
startkde says that $DISPLAY is not set or could not locate X server.
Sorry for being imprecise.

@itsbrad:
Here is the actual report itself:

X.Org X Server 1.7.6
Release Date: 2010-03-17
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.33-ARCH i686 
Current Operating System: Linux Brad-Desktop 2.6.33-ARCH #1 SMP PREEMPT Mon Apr 26 20:00:20 CEST 2010 i686
Kernel command line: root=/dev/disk/by-uuid/a06aeea0-d374-4e10-99d1-a67f27a2dfff ro
Build Date: 01 April 2010  05:35:33PM
 
Current version of pixman: 0.18.0
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon May  3 23:25:49 2010
(II) Loader magic: 0x81e4c60
(II) Module ABI versions:
    X.Org ANSI C Emulation: 0.4
    X.Org Video Driver: 6.0
    X.Org XInput driver : 7.0
    X.Org Server Extension : 2.0
(--) using VT number 7

(--) PCI:*(0:0:2:0) 8086:2582:103c:2a08 Intel Corporation 82915G/GV/910GL Integrated Graphics Controller rev 4, Mem @ 0xcfe80000/524288, 0xd0000000/268435456, 0xcfe40000/262144, I/O @ 0x0000c800/8
List of video drivers:
    intel
(II) LoadModule: "intel"
(II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
dlopen: /usr/lib/xorg/modules/drivers/intel_drv.so: file too short
(EE) Failed to load /usr/lib/xorg/modules/drivers/intel_drv.so
(II) UnloadModule: "intel"
(EE) Failed to load module "intel" (loader failed, 7)
(II) Primary Device is: PCI 00@00:02:0
No devices to configure.  Configuration failed.

Upon navigating to the /usr/bin/xorg/.../ directory, the .so file does actually exist, but running cat actually returns nothing. It seems that file is empty.

Thanks again.

grey · 2010-05-04 00:36:14

$ which startx
/usr/bin/startx
$ pacman -Qo /usr/bin/startx
/usr/bin/startx is owned by xorg-xinit 1.2.1-1

Pls. check

darkeye · 2010-05-04 01:14:08

@grey:
which startx:
startx not found in (directory listings)

I couldn't use the pacman -Qo cause I don't have the file. Should I install that package?

@everyone:

I think that the empty file intel_drv.so may be causing the issue. I just manually removed all the files related to the driver since pacman had issues removing it, and then reinstalled the driver. The file is no longer empty.
I'm going to test it in a bit.

mcmillan · 2010-05-04 02:32:07

It looks like you never installed xorg. I suggest you take a look the beginners' guide on the wiki, particularly the Install X section.

I think that the empty file intel_drv.so may be causing the issue. I just manually removed all the files related to the driver since pacman had issues removing it, and then reinstalled the driver. The file is no longer empty.
I'm going to test it in a bit.

Can you say exactly what you did here and what errors pacman was giving you since removing things by hand is a good way to break your system

demian · 2010-05-04 07:58:27

darkeye wrote:

@demian:
I'd have to boot into linux to check it out, So I'll post that when I get home.
But the only things I added to my daemons array are hal and dbus.

Hal starts dbus automatically. If you've added dbus after hal in the daemons array that might be the source of your problems.
Also, make sure you're using xf86-input-evdev and no xorg.conf.

Greets,
demian

Last edited by demian (2010-05-04 07:59:19)

thunderogg · 2010-05-04 08:34:13

If you have intel you should try to run without xorg.conf. No need to configure xorg!

grey · 2010-05-04 08:52:34

@thunderogg: s/No need/For most people there is no need/

These things tend to be "proven to just work out of the box on 70% of all current hardware" (Misfit138)

thunderogg · 2010-05-04 13:27:41

Yeah, that might be true. But, if he doesn't try without xorg.conf, he will not now if it will work without it. If it works without it, it is a much easier setup then trying to configure xorg.conf.

darkeye · 2010-05-04 21:20:49

Alright. I got it working.

What I had to to do was remove the old intel driver.
Since pacman was returning errors upon removing the file, it provided me with a bunch of errors of files that could not be deleted.
I then manually deleted them myself with rm.
After this, I reinstalled the driver with pacman -S, which informed me that the .tar i downloaded for it was corrupted. It then proceeded to download a new .tar and install it, which worked out great, since i now have X11.

I am however having some really weird issues with my KDE desktop, since as soon as the desktop starts, plasma desktop crashes, saying that kdeinit closed unexpectedly with a signal of 6.

I have found a workaround, although it is somewhat annoying. If I log into the console as root, and then use startx to start up the x server, I can then use startkde to start it up. However, the plasma desktop still crashes. Since I have xterm open though, I can restart the plasma desktop, and then everything works fine... which is really weird.

Any ideas why this would be happening?

darkeye · 2010-05-04 21:26:09

In addition, the Akonadi Server crashes on boot also...

Here is the log:

Akonadi Server Self-Test Report
===============================

Test 1:  SUCCESS
--------

Database driver found.
Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server configuration and was found on your system.

File content of '/root/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL
SizeThreshold=4096
ExternalPayload=false

[QMYSQL]
Name=akonadi
Host=
User=
Password=
Options="UNIX_SOCKET=/root/.local/share/akonadi/db_misc/mysql.socket"
ServerPath=/usr/sbin/mysqld
StartServer=true


Test 2:  SUCCESS
--------

MySQL server found.
Details: You currently have configured Akonadi to use the MySQL server '/usr/sbin/mysqld'.
Make sure you have the MySQL server installed, set the correct path and ensure you have the necessary read and execution rights on the server executable. The server executable is typically called 'mysqld', its locations varies depending on the distribution.

Test 3:  SUCCESS
--------

MySQL server is executable.
Details: MySQL server found: /usr/sbin/mysqld  Ver 5.1.46 for pc-linux-gnu on i686 (Source distribution)


Test 4:  SUCCESS
--------

No current MySQL error log found.
Details: The MySQL server did not report any errors during this startup into '/root/.local/share/akonadi/db_data/mysql.err'.

Test 5:  SUCCESS
--------

MySQL server default configuration found.
Details: The default configuration for the MySQL server was found and is readable at <a href='/usr/share/config/akonadi/mysql-global.conf'>/usr/share/config/akonadi/mysql-global.conf</a>.

File content of '/usr/share/config/akonadi/mysql-global.conf':
#
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
#
# Based on advice by Kris Köhntopp <kris@mysql.com>
#
[mysqld]
skip_grant_tables
skip_networking

# strict query parsing/interpretation
# TODO: make Akonadi work with those settings enabled
#sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
#sql_mode=strict_trans_tables

# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb
# case-insensitive table names, avoids trouble on windows
lower_case_table_names=1
character_set_server=latin1
collation_server=latin1_general_ci
table_cache=200
thread_cache_size=3
log_bin=mysql-bin
expire_logs_days=3
#sync_bin_log=0
# error log file name, relative to datadir
log_error=mysql.err
log_warnings=2
# log all queries, useful for debugging but generates an enormous amount of data
#log=mysql.full
# log queries slower than n seconds, log file name relative to datadir (for debugging only)
#log_slow_queries=mysql.slow
#long_query_time=1
# log queries not using indices, debug only, disable for production use
#log_queries_not_using_indexes=1
# maximum blob size
max_allowed_packet=32M
max_connections=256
# makes sense when having the same query multiple times
# makes no sense with prepared statements and/or transactions
query_cache_type=0
query_cache_size=0

innodb_file_per_table=1
innodb_log_buffer_size=1M
innodb_additional_mem_pool_size=1M
# messure database size and adjust
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");
innodb_buffer_pool_size=80M
# size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)
innodb_log_file_size=64M
innodb_flush_log_at_trx_commit=2



Test 6:  SKIP
--------

MySQL server custom configuration not available.
Details: The custom configuration for the MySQL server was not found but is optional.

Test 7:  SUCCESS
--------

MySQL server configuration is usable.
Details: The MySQL server configuration was found at <a href='/root/.local/share/akonadi/mysql.conf'>/root/.local/share/akonadi/mysql.conf</a> and is readable.

File content of '/root/.local/share/akonadi/mysql.conf':
#
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
#
# Based on advice by Kris Köhntopp <kris@mysql.com>
#
[mysqld]
skip_grant_tables
skip_networking

# strict query parsing/interpretation
# TODO: make Akonadi work with those settings enabled
#sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
#sql_mode=strict_trans_tables

# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb
# case-insensitive table names, avoids trouble on windows
lower_case_table_names=1
character_set_server=latin1
collation_server=latin1_general_ci
table_cache=200
thread_cache_size=3
log_bin=mysql-bin
expire_logs_days=3
#sync_bin_log=0
# error log file name, relative to datadir
log_error=mysql.err
log_warnings=2
# log all queries, useful for debugging but generates an enormous amount of data
#log=mysql.full
# log queries slower than n seconds, log file name relative to datadir (for debugging only)
#log_slow_queries=mysql.slow
#long_query_time=1
# log queries not using indices, debug only, disable for production use
#log_queries_not_using_indexes=1
# maximum blob size
max_allowed_packet=32M
max_connections=256
# makes sense when having the same query multiple times
# makes no sense with prepared statements and/or transactions
query_cache_type=0
query_cache_size=0

innodb_file_per_table=1
innodb_log_buffer_size=1M
innodb_additional_mem_pool_size=1M
# messure database size and adjust
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");
innodb_buffer_pool_size=80M
# size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)
innodb_log_file_size=64M
innodb_flush_log_at_trx_commit=2



Test 8:  SUCCESS
--------

akonadictl found and usable
Details: The program '/usr/bin/akonadictl' to control the Akonadi server was found and could be executed successfully.
Result:
Akonadi 1.3.1


Test 9:  ERROR
--------

Akonadi control process not registered at D-Bus.
Details: The Akonadi control process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.

Test 10:  ERROR
--------

Akonadi server process not registered at D-Bus.
Details: The Akonadi server process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.

Test 11:  ERROR
--------

Nepomuk search service not registered at D-Bus.
Details: The Nepomuk search service is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.

Test 12:  SKIP
--------

Protocol version check not possible.
Details: Without a connection to the server it is not possible to check if the protocol version meets the requirements.

Test 13:  ERROR
--------

No resource agents found.
Details: No resource agents have been found, Akonadi is not usable without at least one. This usually means that no resource agents are installed or that there is a setup problem. The following paths have been searched: '/usr/share/akonadi/agents'. The XDG_DATA_DIRS environment variable is set to '/usr/share:/usr/local/share', make sure this includes all paths where Akonadi agents are installed to.

Directory listing of '/usr/share/akonadi/agents':
birthdaysresource.desktop
contactsresource.desktop
icalresource.desktop
imapresource.desktop
kabcresource.desktop
kcalresource.desktop
knutresource.desktop
kolabproxyresource.desktop
localbookmarksresource.desktop
maildirresource.desktop
maildispatcheragent.desktop
mboxresource.desktop
microblog.desktop
mtdummyresource.desktop
nepomukcalendarfeeder.desktop
nepomukcontactfeeder.desktop
nepomuktagresource.desktop
nntpresource.desktop
notesresource.desktop
pop3resource.desktop
vcarddirresource.desktop
vcardresource.desktop

Environment variable XDG_DATA_DIRS is set to '/usr/share:/usr/local/share'

Test 14:  ERROR
--------

Current Akonadi server error log found.
Details: The Akonadi server did report error during startup into <a href='/root/.local/share/akonadi/akonadiserver.error'>/root/.local/share/akonadi/akonadiserver.error</a>.

File content of '/root/.local/share/akonadi/akonadiserver.error':
Database process exited unexpectedly during initial connection! 
executable: "/usr/sbin/mysqld" 
arguments: ("--defaults-file=/root/.local/share/akonadi//mysql.conf", "--datadir=/root/.local/share/akonadi/db_data/", "--socket=/root/.local/share/akonadi/db_misc/mysql.socket") 
stdout: "" 
stderr: "100504 21:25:15 [ERROR] Fatal error: Please read "Security" section of the manual to find out how to run mysqld as root!

100504 21:25:15 [ERROR] Aborting

100504 21:25:15 [Note] /usr/sbin/mysqld: Shutdown complete

" 
exit code: 1 
process error: "Unknown error" 
"[
0: akonadiserver(_Z11akBacktracev+0x35) [0x8052365]
1: akonadiserver() [0x805282e]
2: [0xb77b8400]
3: [0xb77b8424]
4: /lib/libc.so.6(gsignal+0x51) [0xb7098bf1]
5: /lib/libc.so.6(abort+0x17e) [0xb709a47e]
6: /usr/lib/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x84) [0xb7410094]
7: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0xc4) [0x8053794]
8: /usr/lib/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0x8e) [0xb74a630e]
9: /usr/lib/libQtCore.so.4(+0x108df5) [0xb74bbdf5]
10: /usr/lib/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x3d) [0xb74bd31d]
11: akonadiserver(_ZN6QDebugD1Ev+0x43) [0x804d3a3]
12: /usr/lib/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer25startMysqlDatabaseProcessEv+0x1c65) [0xb76782e5]
13: /usr/lib/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer20startDatabaseProcessEv+0x263) [0xb767ab03]
14: /usr/lib/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServerC1EP7QObject+0x7d) [0xb767ad1d]
15: /usr/lib/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer8instanceEv+0x58) [0xb767c1c8]
16: akonadiserver(main+0x2cf) [0x804c9bf]
17: /lib/libc.so.6(__libc_start_main+0xe6) [0xb7084b96]
18: akonadiserver() [0x804c621]
]
" 


Test 15:  ERROR
--------

Previous Akonadi server error log found.
Details: The Akonadi server did report error during its previous startup into <a href='/root/.local/share/akonadi/akonadiserver.error.old'>/root/.local/share/akonadi/akonadiserver.error.old</a>.

File content of '/root/.local/share/akonadi/akonadiserver.error.old':
Database process exited unexpectedly during initial connection! 
executable: "/usr/sbin/mysqld" 
arguments: ("--defaults-file=/root/.local/share/akonadi//mysql.conf", "--datadir=/root/.local/share/akonadi/db_data/", "--socket=/root/.local/share/akonadi/db_misc/mysql.socket") 
stdout: "" 
stderr: "100504 21:25:15 [ERROR] Fatal error: Please read "Security" section of the manual to find out how to run mysqld as root!

100504 21:25:15 [ERROR] Aborting

100504 21:25:15 [Note] /usr/sbin/mysqld: Shutdown complete

" 
exit code: 1 
process error: "Unknown error" 
"[
0: akonadiserver(_Z11akBacktracev+0x35) [0x8052365]
1: akonadiserver() [0x805282e]
2: [0xb7864400]
3: [0xb7864424]
4: /lib/libc.so.6(gsignal+0x51) [0xb7144bf1]
5: /lib/libc.so.6(abort+0x17e) [0xb714647e]
6: /usr/lib/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x84) [0xb74bc094]
7: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0xc4) [0x8053794]
8: /usr/lib/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0x8e) [0xb755230e]
9: /usr/lib/libQtCore.so.4(+0x108df5) [0xb7567df5]
10: /usr/lib/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x3d) [0xb756931d]
11: akonadiserver(_ZN6QDebugD1Ev+0x43) [0x804d3a3]
12: /usr/lib/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer25startMysqlDatabaseProcessEv+0x1c65) [0xb77242e5]
13: /usr/lib/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer20startDatabaseProcessEv+0x263) [0xb7726b03]
14: /usr/lib/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServerC1EP7QObject+0x7d) [0xb7726d1d]
15: /usr/lib/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer8instanceEv+0x58) [0xb77281c8]
16: akonadiserver(main+0x2cf) [0x804c9bf]
17: /lib/libc.so.6(__libc_start_main+0xe6) [0xb7130b96]
18: akonadiserver() [0x804c621]
]
" 


Test 16:  SUCCESS
--------

No current Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its current startup.

Test 17:  SUCCESS
--------

No previous Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its previous startup.

grey · 2010-05-04 21:40:31

I think you should mark this thread as [solved], since you are able to start X, and open a new thread about your new problem.

Arch Linux

#1 2010-05-03 23:39:08

[Solved] X11 issue - intel driver

#2 2010-05-03 23:53:08

Re: [Solved] X11 issue - intel driver

#3 2010-05-04 00:08:27

Re: [Solved] X11 issue - intel driver

#4 2010-05-04 00:13:52

Re: [Solved] X11 issue - intel driver

#5 2010-05-04 00:15:43

Re: [Solved] X11 issue - intel driver

#6 2010-05-04 00:23:22

Re: [Solved] X11 issue - intel driver

#7 2010-05-04 00:32:40

Re: [Solved] X11 issue - intel driver

#8 2010-05-04 00:36:14

Re: [Solved] X11 issue - intel driver

#9 2010-05-04 01:14:08

Re: [Solved] X11 issue - intel driver

#10 2010-05-04 02:32:07

Re: [Solved] X11 issue - intel driver

#11 2010-05-04 07:58:27

Re: [Solved] X11 issue - intel driver

#12 2010-05-04 08:34:13

Re: [Solved] X11 issue - intel driver

#13 2010-05-04 08:52:34

Re: [Solved] X11 issue - intel driver

#14 2010-05-04 13:27:41

Re: [Solved] X11 issue - intel driver

#15 2010-05-04 21:20:49

Re: [Solved] X11 issue - intel driver

#16 2010-05-04 21:26:09

Re: [Solved] X11 issue - intel driver

#17 2010-05-04 21:40:31

Re: [Solved] X11 issue - intel driver

Board footer