[arch-general] X fails to start with intel card after latest kernel update
Listmates, After the latest kernel update, I cannot start X for the Arch box I have that has an onboard intel graphics card. (Dell 280GX sff) The errors are: 02:31 nirvana:/srv/www/download/Archlinux/bugs/supersff> grep "(EE)" Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (EE) Failed to load module "i810" (module does not exist, 0) (EE) Failed to load module "fbdev" (module does not exist, 0) Obviously it is complaining about the intel i810 and framebuffer modules. Why? This box has always worked fine with the 915 module. It looks like all the normal intel modules are loaded: 02:34 supersff:~> lsmod | grep "intel\|915" i915 231880 0 drm 156160 1 i915 i2c_algo_bit 5888 1 i915 video 20116 1 i915 snd_intel8x0 30616 0 snd_ac97_codec 106112 1 snd_intel8x0 snd_pcm 74464 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss snd 58820 9 snd_seq_oss,snd_seq,snd_intel8x0,snd_seq_device,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer snd_page_alloc 8900 2 snd_intel8x0,snd_pcm intel_agp 28348 1 i2c_core 21808 4 i915,drm,i2c_algo_bit,i2c_i801 agpgart 32660 2 drm,intel_agp Any ideas? I'm not even sure where to begin on this one. This box doesn't have an xorg.conf and the defaults have always worked just fine. What could have changed? Full Xorg.0.log and pacman.log are here: http://www.3111skyline.com/download/Archlinux/bugs/supersff/Xorg.0.log http://www.3111skyline.com/download/Archlinux/bugs/supersff/pacman.log.bz2 Any help would be appreciated. Thanks. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
After the latest kernel update, I cannot start X for the Arch box I have that has an onboard intel graphics card. (Dell 280GX sff) The errors are:
02:31 nirvana:/srv/www/download/Archlinux/bugs/supersff> grep "(EE)" Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (EE) Failed to load module "i810" (module does not exist, 0) (EE) Failed to load module "fbdev" (module does not exist, 0)
this is not important looking at you log file it seems that X did start just fine -- damjan
On Fri, 2009-10-09 at 12:53 +0200, Damjan Georgievski wrote:
After the latest kernel update, I cannot start X for the Arch box I have that has an onboard intel graphics card. (Dell 280GX sff) The errors are:
02:31 nirvana:/srv/www/download/Archlinux/bugs/supersff> grep "(EE)" Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (EE) Failed to load module "i810" (module does not exist, 0) (EE) Failed to load module "fbdev" (module does not exist, 0)
this is not important
looking at you log file it seems that X did start just fine
And it exited fine also, so it's not X related.
On Friday 09 October 2009 06:24:06 am Jan de Groot wrote:
On Fri, 2009-10-09 at 12:53 +0200, Damjan Georgievski wrote:
After the latest kernel update, I cannot start X for the Arch box I have that has an onboard intel graphics card. (Dell 280GX sff) The errors are:
02:31 nirvana:/srv/www/download/Archlinux/bugs/supersff> grep "(EE)" Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (EE) Failed to load module "i810" (module does not exist, 0) (EE) Failed to load module "fbdev" (module does not exist, 0)
this is not important
looking at you log file it seems that X did start just fine
And it exited fine also, so it's not X related.
Aargh! Must be the flu. What I'm saying is that when I boot, the box tries, but cannot get to the graphical login (kdm3) and dumps me at the cli. I then cannot get kde going with startx (it gives the same results). If X is starting, then it is dying as soon as it starts. Strange?? vncserver/vncviewer will not even start kde. I get the error: "Could not start kdeinit. Check your installation." when I open the vncviewer window. What other logs might help? Thanks. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Saturday 10 October 2009 12:25:41 am David C. Rankin wrote:
On Friday 09 October 2009 06:24:06 am Jan de Groot wrote:
On Fri, 2009-10-09 at 12:53 +0200, Damjan Georgievski wrote:
After the latest kernel update, I cannot start X for the Arch box I have that has an onboard intel graphics card. (Dell 280GX sff) The errors are:
02:31 nirvana:/srv/www/download/Archlinux/bugs/supersff> grep "(EE)" Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (EE) Failed to load module "i810" (module does not exist, 0) (EE) Failed to load module "fbdev" (module does not exist, 0)
this is not important
looking at you log file it seems that X did start just fine
And it exited fine also, so it's not X related.
Aargh! Must be the flu. What I'm saying is that when I boot, the box tries, but cannot get to the graphical login (kdm3) and dumps me at the cli. I then cannot get kde going with startx (it gives the same results). If X is starting, then it is dying as soon as it starts. Strange??
vncserver/vncviewer will not even start kde. I get the error:
"Could not start kdeinit. Check your installation."
when I open the vncviewer window. What other logs might help? Thanks.
Here is what is showing up in the errors.log that shows the problem started with the updates on 10/8 [00:29 supersff:/var/log] # grep kdm errors.log Oct 8 21:45:09 supersff kdm: :0[1514]: Abnormal termination of greeter for display :0, code 127, signal 0 Oct 9 10:37:42 supersff kdm: :0[1544]: Abnormal termination of greeter for display :0, code 127, signal 0 Oct 10 00:27:15 supersff kdm[1799]: X server died during startup Oct 10 00:27:15 supersff kdm[1799]: X server for display :0 can't be started, session disabled Oct 10 00:28:28 supersff kdm[1826]: X server died during startup Oct 10 00:28:28 supersff kdm[1826]: X server for display :0 can't be started, session disabled -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
Le Sat, 10 Oct 2009 00:30:53 -0500 "David C. Rankin" <drankinatty@suddenlinkmail.com> a écrit:
Here is what is showing up in the errors.log that shows the problem started with the updates on 10/8
Could you post the 60-70 last lines of /var/log/pacman.log ?
On Saturday 17 October 2009 05:50:29 am pascal wrote:
Le Sat, 10 Oct 2009 00:30:53 -0500
"David C. Rankin" <drankinatty@suddenlinkmail.com> a écrit:
Here is what is showing up in the errors.log that shows the problem started with the updates on 10/8
Could you post the 60-70 last lines of /var/log/pacman.log ?
Sure, the whole log is here: http://www.3111skyline.com/download/Archlinux/bugs/supersff/pacman.log.bz2 I have put all the files related to the bug in that directory: http://www.3111skyline.com/download/Archlinux/bugs/supersff/ -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
Le Sat, 17 Oct 2009 09:13:34 -0500 "David C. Rankin" <drankinatty@suddenlinkmail.com> a écrit:
Sure, the whole log is here:
http://www.3111skyline.com/download/Archlinux/bugs/supersff/pacman.log.bz2
I have put all the files related to the bug in that directory:
http://www.3111skyline.com/download/Archlinux/bugs/supersff/
The thing is your pacman log stops at 2009.10.09 and there's no information related to the xorg (and intel drivers) upgrade. It might not be related but who knows...
On Saturday 17 October 2009 11:41:31 am pascal wrote:
Le Sat, 17 Oct 2009 09:13:34 -0500
"David C. Rankin" <drankinatty@suddenlinkmail.com> a écrit:
Sure, the whole log is here:
http://www.3111skyline.com/download/Archlinux/bugs/supersff/pacman.log.bz 2
I have put all the files related to the bug in that directory:
http://www.3111skyline.com/download/Archlinux/bugs/supersff/
The thing is your pacman log stops at 2009.10.09 and there's no information related to the xorg (and intel drivers) upgrade. It might not be related but who knows...
AARGH! Got it now :-) pascal, I created an entire new directory for today and put new copies of all the files there. I also created a bzipped tar archive containing all the files for convenient download. The directory contents is: 1017-Xcrash-files.tar.bz2 daemon.log dmesg-2009-10-17.txt errors.log everything.log kdm.log lspci-2009-10-17.txt menu.lst mkinitcpio.conf pacman.log rc.conf Xorg.0.log Xorg.0.log.old Xorg.1.log The archive containing all the files is 1017-Xcrash-files.tar.bz2 (~98k). The URLS are: Directory: http://www.3111skyline.com/download/Archlinux/bugs/supersff/1017/ Archive: http://www.3111skyline.com/download/Archlinux/bugs/supersff/1017/1017-Xcrash... files.tar.bz2 Past Files: http://www.3111skyline.com/download/Archlinux/bugs/supersff/ Also, there was a suggestion with regard to the ticket to try and start X another way without the kde greeter. I'll work on just trying to start openbox and see if I can get that going. If you can think of another test or two for me to run, just let me know. My goal is to figure this thing out today (hope springs eternal...) -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Friday 09 October 2009 06:24:06 am Jan de Groot wrote:
On Fri, 2009-10-09 at 12:53 +0200, Damjan Georgievski wrote:
After the latest kernel update, I cannot start X for the Arch box I have that has an onboard intel graphics card. (Dell 280GX sff) The errors are:
02:31 nirvana:/srv/www/download/Archlinux/bugs/supersff> grep "(EE)" Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (EE) Failed to load module "i810" (module does not exist, 0) (EE) Failed to load module "fbdev" (module does not exist, 0)
this is not important
looking at you log file it seems that X did start just fine
And it exited fine also, so it's not X related.
I must have posted the Xorg from the wrong arch box. Here is what I'm seeing: (WW) intel(0): No outputs definitely connected, trying again... (II) intel(0): Output VGA disconnected (WW) intel(0): Unable to find initial modes (EE) intel(0): No valid modes. (II) UnloadModule: "intel" (II) UnloadModule: "vgahw" (II) Unloading /usr/lib/xorg/modules//libvgahw.so (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found Please consult the The X.Org Foundation support at http://wiki.x.org for help. Please also check the log file at "/var/log/Xorg.0.log" for additional information. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
Is KMS enabled? On Sat, Oct 10, 2009 at 2:39 AM, David C. Rankin < drankinatty@suddenlinkmail.com> wrote:
On Friday 09 October 2009 06:24:06 am Jan de Groot wrote:
On Fri, 2009-10-09 at 12:53 +0200, Damjan Georgievski wrote:
After the latest kernel update, I cannot start X for the Arch box I have that has an onboard intel graphics card. (Dell 280GX sff) The errors are:
02:31 nirvana:/srv/www/download/Archlinux/bugs/supersff> grep "(EE)" Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (EE) Failed to load module "i810" (module does not exist, 0) (EE) Failed to load module "fbdev" (module does not exist, 0)
this is not important
looking at you log file it seems that X did start just fine
And it exited fine also, so it's not X related.
I must have posted the Xorg from the wrong arch box. Here is what I'm seeing:
(WW) intel(0): No outputs definitely connected, trying again... (II) intel(0): Output VGA disconnected (WW) intel(0): Unable to find initial modes (EE) intel(0): No valid modes. (II) UnloadModule: "intel" (II) UnloadModule: "vgahw" (II) Unloading /usr/lib/xorg/modules//libvgahw.so (EE) Screen(s) found, but none have a usable configuration.
Fatal server error: no screens found
Please consult the The X.Org Foundation support at http://wiki.x.org for help. Please also check the log file at "/var/log/Xorg.0.log" for additional information.
-- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
-- Flávio Coutinho da Costa
On Saturday 10 October 2009 02:09:26 am Flavio Costa wrote:
Is KMS enabled?
Is KM..what enabled? That must have been a change I missed?? I'm reading back through http://wiki.archlinux.org/index.php/Intel_Graphics to try and figure out what it is and why I now need it but haven't since I built the box in ?March?. The strange part is that if that is the problem, something changed with the 10/8 update. For many months, this box with the intel card just worked... I'll report back after reading through the wiki and either claim success, or, beg for more help :p -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Sunday 11 October 2009 03:10:15 am David C. Rankin wrote:
The strange part is that if that is the problem, something changed with the 10/8 update. For many months, this box with the intel card just worked... I'll report back after reading through the wiki and either claim success, or, beg for more help :p
UUGH!!, I'm back already. The wiki page must be out of date. It says to put the following in modprobe.conf (which is deprecated): options i915 modeset=1 Now what?? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
Excerpts from David C. Rankin's message of So Okt 11 10:16:57 +0200 2009:
On Sunday 11 October 2009 03:10:15 am David C. Rankin wrote: I'm back already. The wiki page must be out of date. It says to put the following in modprobe.conf (which is deprecated):
options i915 modeset=1
Now what??
Put it in /etc/modprobe.d/modprobe.conf (that's where I have it).
Hey David, I am tracking this email thread as this issue has affected a couple of colleagues of mine and I'm holding back upgrading my box until I know there is a definite resolution as I have been reading too many horror stories around the net about how bad this has broken peoples boxes. Can you let us all know when you have resolved it and how you resolve it please? Cheers, Dusty. -----Original Message----- From: arch-general-bounces@archlinux.org [mailto:arch-general-bounces@archlinux.org] On Behalf Of Jan Spakula Sent: 11 October 2009 09:34 To: arch-general Subject: Re: [arch-general] X fails to start with intel card after latestkernel update Excerpts from David C. Rankin's message of So Okt 11 10:16:57 +0200 2009:
On Sunday 11 October 2009 03:10:15 am David C. Rankin wrote: I'm back already. The wiki page must be out of date. It says to put the following in modprobe.conf (which is deprecated):
options i915 modeset=1
Now what??
Put it in /etc/modprobe.d/modprobe.conf (that's where I have it). ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
On Monday 12 October 2009 11:47:59 am Dusty wrote:
Hey David,
I am tracking this email thread as this issue has affected a couple of colleagues of mine and I'm holding back upgrading my box until I know there is a definite resolution as I have been reading too many horror stories around the net about how bad this has broken peoples boxes.
Can you let us all know when you have resolved it and how you resolve it please?
Cheers,
Dusty.
Will do Dusty! -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
Hey guys, I have managed to upgrade (pacman -Syu) grabbing the new kernel upgrade and not killing my X using KMS. What I did to avoid the problems you guys are getting is the following: 1) Goto the ArchWiki and search for intel and bring up the following page: http://wiki.archlinux.org/index.php/Intel_Graphics 2) Follow the steps for the KMS settings.. 3) Then run pacman -Syu and grab the updates, install them. 4) Reboot. 5) It works :) I have the following hardware: root ~ # hwinfo --gfxcard 09: PCI 02.0: 0300 VGA compatible controller (VGA) [Created at pci.318] UDI: /org/freedesktop/Hal/devices/pci_8086_2a02 Unique ID: _Znp.3gR64TvADaC SysFS ID: /devices/pci0000:00/0000:00:02.0 SysFS BusID: 0000:00:02.0 Hardware Class: graphics card Model: "Lenovo T61" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x2a02 "965 GM" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x20b5 "T61" Revision: 0x0c Driver: "i915" Driver Modules: "drm" Memory Range: 0xf8100000-0xf81fffff (rw,non-prefetchable) Memory Range: 0xe0000000-0xefffffff (rw,prefetchable) I/O Ports: 0x1800-0x1807 (rw) IRQ: 29 (10253 events) I/O Ports: 0x3c0-0x3df (rw) Module Alias: "pci:v00008086d00002A02sv000017AAsd000020B5bc03sc00i00" Driver Info #0: XFree86 v4 Server Module: intel Driver Info #1: XFree86 v4 Server Module: intel 3D Support: yes Extensions: dri Config Status: cfg=new, avail=yes, need=no, active=unknown 10: PCI 02.1: 0380 Display controller [Created at pci.318] UDI: /org/freedesktop/Hal/devices/pci_8086_2a03 Unique ID: ruGf.a6pkzICrUB2 SysFS ID: /devices/pci0000:00/0000:00:02.1 SysFS BusID: 0000:00:02.1 Hardware Class: graphics card Model: "Lenovo T61" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x2a03 "Mobile GM965/GL960 Integrated Graphics Controller" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x20b5 "T61" Revision: 0x0c Memory Range: 0xf8200000-0xf82fffff (rw,non-prefetchable) Module Alias: "pci:v00008086d00002A03sv000017AAsd000020B5bc03sc80i00" Config Status: cfg=new, avail=yes, need=no, active=unknown Primary display adapter: #9 root ~ # I suspect, if you were to follow the KMS steps in the above URL, then reboot you will probably be ok. If that doesn't work, I would roll back, do the KMS steps, then upgrade (grab the new kernel) and reboot.. Hope this helps you guys, Let me know how you get on. Kind Regards, Dusty. -----Original Message----- From: arch-general-bounces@archlinux.org [mailto:arch-general-bounces@archlinux.org] On Behalf Of Jan Spakula Sent: 11 October 2009 09:34 To: arch-general Subject: Re: [arch-general] X fails to start with intel card after latestkernel update Excerpts from David C. Rankin's message of So Okt 11 10:16:57 +0200 2009:
On Sunday 11 October 2009 03:10:15 am David C. Rankin wrote: I'm back already. The wiki page must be out of date. It says to put the following in modprobe.conf (which is deprecated):
options i915 modeset=1
Now what??
Put it in /etc/modprobe.d/modprobe.conf (that's where I have it). ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
On Monday 12 October 2009 02:51:51 pm Dusty wrote:
Hey guys,
I have managed to upgrade (pacman -Syu) grabbing the new kernel upgrade and not killing my X using KMS.
What I did to avoid the problems you guys are getting is the following:
1) Goto the ArchWiki and search for intel and bring up the following page:
http://wiki.archlinux.org/index.php/Intel_Graphics
2) Follow the steps for the KMS settings..
3) Then run pacman -Syu and grab the updates, install them.
4) Reboot.
5) It works :)
I have the following hardware: <snip>
Primary display adapter: #9 root ~ #
I suspect, if you were to follow the KMS steps in the above URL, then reboot you will probably be ok. If that doesn't work, I would roll back, do the KMS steps, then upgrade (grab the new kernel) and reboot..
Hope this helps you guys,
Let me know how you get on.
Kind Regards,
Dusty.
<snip> Dusty, Glad you got it working, but for me: Bummer :-( I have followed the wiki to a T, using 'Late' Start, but my intel box is still dead in the water: Last login: Tue Oct 13 10:44:44 2009 from alchemy.3111skyline.com 14:24 supersff:~> cat /etc/modprobe.d/modprobe.conf # # /etc/modprobe.d/modprobe.conf (for v2.6 kernels) # options i915 modeset=1 14:25 supersff:~> grep i915 /etc/rc.conf MODULES=(tg3 acx intel_agp i915) I have updated everything, and I still get the black screen of death. On boot, you can tell that X tries to start, the screen flashes, but then BAM back to the terminal screen. Latest logs: http://www.3111skyline.com/download/Archlinux/bugs/supersff/Xorg.0.log.1014 dmesg (bzipped) http://www.3111skyline.com/download/Archlinux/bugs/supersff/dmesg.out.bz2 -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
Hi :) On Wednesday 14 October 2009 21:35:58 David C. Rankin wrote:
On Monday 12 October 2009 02:51:51 pm Dusty wrote:
Hey guys,
I have managed to upgrade (pacman -Syu) grabbing the new kernel upgrade and not killing my X using KMS.
What I did to avoid the problems you guys are getting is the following:
1) Goto the ArchWiki and search for intel and bring up the following page:
http://wiki.archlinux.org/index.php/Intel_Graphics
2) Follow the steps for the KMS settings..
3) Then run pacman -Syu and grab the updates, install them.
4) Reboot.
5) It works :)
I have the following hardware:
<snip>
Primary display adapter: #9 root ~ #
I suspect, if you were to follow the KMS steps in the above URL, then reboot you will probably be ok. If that doesn't work, I would roll back, do the KMS steps, then upgrade (grab the new kernel) and reboot..
Hope this helps you guys,
Let me know how you get on.
Kind Regards,
Dusty.
<snip>
Dusty, Glad you got it working, but for me:
Bummer :-(
I have followed the wiki to a T, using 'Late' Start, but my intel box is still dead in the water:
I'm using the "Early" start on an MSI Wind and works perfect.
Last login: Tue Oct 13 10:44:44 2009 from alchemy.3111skyline.com 14:24 supersff:~> cat /etc/modprobe.d/modprobe.conf # # /etc/modprobe.d/modprobe.conf (for v2.6 kernels) # options i915 modeset=1 14:25 supersff:~> grep i915 /etc/rc.conf MODULES=(tg3 acx intel_agp i915)
I have updated everything, and I still get the black screen of death. On boot, you can tell that X tries to start, the screen flashes, but then BAM back to the terminal screen. Latest logs:
How about booting into runlevel 3 and then manualy running "startx"? Have you tried that?
http://www.3111skyline.com/download/Archlinux/bugs/supersff/Xorg.0.log.1014
Been looking through your log and see this line: Kernel command line: root=/dev/sda6 ro vga=0x31a Shouldn't you remove all the vga= and/or video= options in menu.lst? Maybe that's the problem. HTH Rafa -- "We cannot treat computers as Humans. Computers need love." rgriman@skype.com rgriman@jabberes.org Happily using KDE 4.3.1 :)
Le Thu, 15 Oct 2009 11:48:44 +0200 Rafa Griman <rafagriman@gmail.com> a écrit:
Hi :)
On Wednesday 14 October 2009 21:35:58 David C. Rankin wrote:
On Monday 12 October 2009 02:51:51 pm Dusty wrote:
Hey guys,
I have managed to upgrade (pacman -Syu) grabbing the new kernel upgrade and not killing my X using KMS.
What I did to avoid the problems you guys are getting is the following:
1) Goto the ArchWiki and search for intel and bring up the following page:
http://wiki.archlinux.org/index.php/Intel_Graphics
2) Follow the steps for the KMS settings..
3) Then run pacman -Syu and grab the updates, install them.
4) Reboot.
5) It works :)
I have the following hardware:
<snip>
Primary display adapter: #9 root ~ #
I suspect, if you were to follow the KMS steps in the above URL, then reboot you will probably be ok. If that doesn't work, I would roll back, do the KMS steps, then upgrade (grab the new kernel) and reboot..
Hope this helps you guys,
Let me know how you get on.
Kind Regards,
Dusty.
<snip>
Dusty, Glad you got it working, but for me:
Bummer :-(
I have followed the wiki to a T, using 'Late' Start, but my intel box is still dead in the water:
I'm using the "Early" start on an MSI Wind and works perfect.
Last login: Tue Oct 13 10:44:44 2009 from alchemy.3111skyline.com 14:24 supersff:~> cat /etc/modprobe.d/modprobe.conf # # /etc/modprobe.d/modprobe.conf (for v2.6 kernels) # options i915 modeset=1 14:25 supersff:~> grep i915 /etc/rc.conf MODULES=(tg3 acx intel_agp i915)
I have updated everything, and I still get the black screen of death. On boot, you can tell that X tries to start, the screen flashes, but then BAM back to the terminal screen. Latest logs:
How about booting into runlevel 3 and then manualy running "startx"? Have you tried that?
http://www.3111skyline.com/download/Archlinux/bugs/supersff/Xorg.0.log.1014
Been looking through your log and see this line:
Kernel command line: root=/dev/sda6 ro vga=0x31a
Shouldn't you remove all the vga= and/or video= options in menu.lst?
Maybe that's the problem.
HTH
Rafa
Hi In the last Xorg.0.log I can see that you removed the "vga=0x31a" part. But the vesa module is still loaded (and unloaded short after) just after the intel module, and the output used is VGA1. I also have an 915 chipset (though a 915GM) and upgraded to Xorg from testing to see if I could reproduce your problem. Apart some serious performance regression (and some freezes...) it works almost fine. I diff'ed my Xorg.0.log with yours and I don't have the vesa module loaded. Also my output is set to LVDS1, which I remember changed when I went to KMS some months ago (before that the output was VGA1, if I record correctly). I also have a line saying " (**) intel(0): Kernel mode setting active, disabling FBC. ", which doesn't appear in your log. Makes me wonder if your kernel is really using KMS. When booted, does the framebuffer display in native resolution ? I switched back to Xorg from [extra] for stability matters. [testing] being for ... well, testing.
On Thursday 15 October 2009 07:47:11 am pascal wrote:
Hi In the last Xorg.0.log I can see that you removed the "vga=0x31a" part. But the vesa module is still loaded (and unloaded short after) just after the intel module, and the output used is VGA1. I also have an 915 chipset (though a 915GM) and upgraded to Xorg from testing to see if I could reproduce your problem. Apart some serious performance regression (and some freezes...) it works almost fine. I diff'ed my Xorg.0.log with yours and I don't have the vesa module loaded. Also my output is set to LVDS1, which I remember changed when I went to KMS some months ago (before that the output was VGA1, if I record correctly). I also have a line saying " (**) intel(0): Kernel mode setting active, disabling FBC. ", which doesn't appear in your log. Makes me wonder if your kernel is really using KMS. When booted, does the framebuffer display in native resolution ? I switched back to Xorg from [extra] for stability matters. [testing] being for ... well, testing.
Pascal, Thank you for taking the time to help. I'm really stumped here. The funny thing is "Yes", even with all vga= lines removed, I get native resolution of what looks like 1280x1024 when the box boot. What happens is the box will boot and the first 20 or so lines is in 640x480, then magically the box switches to 1280x1024. The actual resolution of the monitor is 1680x1050 when X starts (well when it used to start). I have never had this much trouble with X before. In answer to your second question "Yes" I have booted to runlevel 3 and tried to use startx -- same result. X tries to start then crashes. Here are some more hardware details in case that would help. The box is a dell gx280 with a P4-3.2GHz processor. The output of lspci is: 00:02.0 VGA compatible controller: Intel Corporation 82915G/GV/910GL Integrated Graphics Controller (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device 0179 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 16 Region 0: Memory at dff00000 (32-bit, non-prefetchable) [size=512K] Region 1: I/O ports at e898 [size=8] Region 2: Memory at c0000000 (32-bit, prefetchable) [size=256M] Region 3: Memory at dfec0000 (32-bit, non-prefetchable) [size=256K] Expansion ROM at <unassigned> [disabled] Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: i915 00:02.1 Display controller: Intel Corporation 82915G Integrated Graphics Controller (rev 04) Subsystem: Dell Device 0179 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Region 0: Memory at dff80000 (32-bit, non-prefetchable) [size=512K] Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Full output is here: http://www.3111skyline.com/download/Archlinux/bugs/supersff/lspci.txt dmidecode details are here: http://www.3111skyline.com/download/Archlinux/bugs/supersff/dmidecode.txt latest Xorg.0.log is here: http://www.3111skyline.com/download/Archlinux/bugs/supersff/Xorg.0.log If you have any other suggestions or ideas, please let me know. Thanks. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Thu, Oct 15, 2009 at 8:08 PM, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
latest Xorg.0.log is here:
http://www.3111skyline.com/download/Archlinux/bugs/supersff/Xorg.0.log
I don't see any errors in your xorg log. You are 100% sure it is the correct one ? The timestamp from the log : (==) Log file: "/var/log/Xorg.0.log", Time: Wed Oct 14 16:15:03 2009
If you have any other suggestions or ideas, please let me know. Thanks.
also paste output of dmesg.
On Thursday 15 October 2009 01:19:25 pm Xavier wrote:
On Thu, Oct 15, 2009 at 8:08 PM, David C. Rankin
<drankinatty@suddenlinkmail.com> wrote:
latest Xorg.0.log is here:
http://www.3111skyline.com/download/Archlinux/bugs/supersff/Xorg.0.log
I don't see any errors in your xorg log. You are 100% sure it is the correct one ? The timestamp from the log : (==) Log file: "/var/log/Xorg.0.log", Time: Wed Oct 14 16:15:03 2009
If you have any other suggestions or ideas, please let me know. Thanks.
also paste output of dmesg.
I don't know what rsync didn't update it, but it is updated now: (==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 15 13:36:06 2009 <snip> (II) UnloadModule: "evdev" (II) Power Button: Close (II) UnloadModule: "evdev" Backtrace: 0: /usr/bin/X (xorg_backtrace+0x3b) [0x809facb] 1: /usr/bin/X (0x8048000+0x54ab5) [0x809cab5] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb776d40c] 3: /usr/lib/xorg/modules/libshadow.so (shadowRemove+0x4e) [0xb70cfd9e] 4: /usr/lib/xorg/modules/libshadow.so (0xb70cf000+0x1234) [0xb70d0234] 5: /usr/bin/X (0x8048000+0x68cf4) [0x80b0cf4] 6: /usr/bin/X (0x8048000+0x15c2ac) [0x81a42ac] 7: /usr/bin/X (0x8048000+0x4f19c) [0x809719c] 8: /usr/bin/X (0x8048000+0x17447c) [0x81bc47c] 9: /usr/bin/X (0x8048000+0x13d3de) [0x81853de] 10: /usr/lib/xorg/modules/drivers/vesa_drv.so (0xb7740000+0x38a8) [0xb77438a8] 11: /usr/bin/X (0x8048000+0x6787c) [0x80af87c] 12: /usr/bin/X (0x8048000+0xb475d) [0x80fc75d] 13: /usr/bin/X (0x8048000+0xfa245) [0x8142245] 14: /usr/bin/X (0x8048000+0x141112) [0x8189112] 15: /usr/bin/X (0x8048000+0xa0430) [0x80e8430] 16: /usr/bin/X (0x8048000+0xc17b9) [0x81097b9] 17: /usr/bin/X (0x8048000+0x114872) [0x815c872] 18: /usr/lib/xorg/modules/extensions/libglx.so (0xb725f000+0x379e3) [0xb72969e3] 19: /usr/bin/X (0x8048000+0x1ab48) [0x8062b48] 20: /lib/libc.so.6 (__libc_start_main+0xe6) [0xb7385a36] 21: /usr/bin/X (0x8048000+0x1a6a1) [0x80626a1] Segmentation fault at address 0x1 I removed the [testing] repository and downgraded to: libgl-7.5.1-2 intel-dri-7.5.1-2 xf86-video-intel-2.8.1-1 I also rebuilt kernel init with mkinitcpio -p kernel26 Now X just hangs. Here is the dmesg output with the downgraded packages. Let me know if you want me to go back to the [testing] packages. Thanks: http://www.3111skyline.com/download/Archlinux/bugs/supersff/dmesg.txt.1015 -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Thursday 15 October 2009 01:43:57 pm David C. Rankin wrote:
On Thursday 15 October 2009 01:19:25 pm Xavier wrote:
On Thu, Oct 15, 2009 at 8:08 PM, David C. Rankin
<drankinatty@suddenlinkmail.com> wrote:
latest Xorg.0.log is here:
http://www.3111skyline.com/download/Archlinux/bugs/supersff/Xorg.0.log
I don't see any errors in your xorg log. You are 100% sure it is the correct one ? The timestamp from the log : (==) Log file: "/var/log/Xorg.0.log", Time: Wed Oct 14 16:15:03 2009
If you have any other suggestions or ideas, please let me know. Thanks.
also paste output of dmesg.
I don't know what rsync didn't update it, but it is updated now:
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 15 13:36:06 2009 <snip>
(II) UnloadModule: "evdev" (II) Power Button: Close (II) UnloadModule: "evdev"
Backtrace: 0: /usr/bin/X (xorg_backtrace+0x3b) [0x809facb] 1: /usr/bin/X (0x8048000+0x54ab5) [0x809cab5] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb776d40c] 3: /usr/lib/xorg/modules/libshadow.so (shadowRemove+0x4e) [0xb70cfd9e] 4: /usr/lib/xorg/modules/libshadow.so (0xb70cf000+0x1234) [0xb70d0234] 5: /usr/bin/X (0x8048000+0x68cf4) [0x80b0cf4] 6: /usr/bin/X (0x8048000+0x15c2ac) [0x81a42ac] 7: /usr/bin/X (0x8048000+0x4f19c) [0x809719c] 8: /usr/bin/X (0x8048000+0x17447c) [0x81bc47c] 9: /usr/bin/X (0x8048000+0x13d3de) [0x81853de] 10: /usr/lib/xorg/modules/drivers/vesa_drv.so (0xb7740000+0x38a8) [0xb77438a8] 11: /usr/bin/X (0x8048000+0x6787c) [0x80af87c] 12: /usr/bin/X (0x8048000+0xb475d) [0x80fc75d] 13: /usr/bin/X (0x8048000+0xfa245) [0x8142245] 14: /usr/bin/X (0x8048000+0x141112) [0x8189112] 15: /usr/bin/X (0x8048000+0xa0430) [0x80e8430] 16: /usr/bin/X (0x8048000+0xc17b9) [0x81097b9] 17: /usr/bin/X (0x8048000+0x114872) [0x815c872] 18: /usr/lib/xorg/modules/extensions/libglx.so (0xb725f000+0x379e3) [0xb72969e3] 19: /usr/bin/X (0x8048000+0x1ab48) [0x8062b48] 20: /lib/libc.so.6 (__libc_start_main+0xe6) [0xb7385a36] 21: /usr/bin/X (0x8048000+0x1a6a1) [0x80626a1] Segmentation fault at address 0x1
I removed the [testing] repository and downgraded to:
libgl-7.5.1-2 intel-dri-7.5.1-2 xf86-video-intel-2.8.1-1
I also rebuilt kernel init with mkinitcpio -p kernel26
Now X just hangs. Here is the dmesg output with the downgraded packages. Let me know if you want me to go back to the [testing] packages. Thanks:
http://www.3111skyline.com/download/Archlinux/bugs/supersff/dmesg.txt.1015
Here are a few more error messages that I hope will help. The kdm.log seems to point to a problem with greeter: http://www.3111skyline.com/download/Archlinux/bugs/supersff/kdm.log.bz2 Here are also a few additional error from the errors.log file that are kernel and kdm related: errors.log: Oct 15 15:01:48 supersff kernel: [drm:i915_wait_request] *ERROR* something (likely vbetool) disabled interrupts, re-enab ling Oct 15 15:01:48 supersff kernel: render error detected, EIR: 0x00000010 Oct 15 15:01:48 supersff kernel: page table error Oct 15 15:01:48 supersff kernel: PGTBL_ER: 0x00000010 Oct 15 15:01:48 supersff kernel: [drm:i915_handle_error] *ERROR* EIR stuck: 0x00000010, masking Oct 15 15:01:48 supersff kernel: render error detected, EIR: 0x00000010 Oct 15 15:01:48 supersff kernel: page table error Oct 15 15:01:48 supersff kernel: PGTBL_ER: 0x00000010 Oct 15 15:02:31 supersff kdm[1639]: X server died during startup Oct 15 15:02:31 supersff kdm[1639]: X server for display :0 can't be started, session disabled Oct 15 15:04:26 supersff nmbd[1479]: [2009/10/15 15:04:26, 0] nmbd/nmbd.c:terminate(71) Oct 15 15:04:26 supersff nmbd[1479]: Got SIGTERM: going down... Oct 15 15:04:59 supersff kernel: render error detected, EIR: 0x00000010 Oct 15 15:04:59 supersff kernel: page table error Oct 15 15:04:59 supersff kernel: PGTBL_ER: 0x00000010 Oct 15 15:04:59 supersff kernel: [drm:i915_handle_error] *ERROR* EIR stuck: 0x00000010, masking Oct 15 15:04:59 supersff kernel: render error detected, EIR: 0x00000010 Oct 15 15:04:59 supersff kernel: page table error Oct 15 15:04:59 supersff kernel: PGTBL_ER: 0x00000010 Oct 15 15:04:59 supersff kernel: iTCO_wdt: failed to reset NO_REBOOT flag, reboot disabled by hardware 17:46 supersff:/var/log> grep kdm errors.log Oct 14 14:23:03 supersff kdm: :0[1496]: Abnormal termination of greeter for display :0, code 127, signal 0 Oct 14 14:45:30 supersff kdm: :0[1543]: Abnormal termination of greeter for display :0, code 127, signal 0 Oct 14 15:28:56 supersff kdm: :0[1502]: Abnormal termination of greeter for display :0, code 127, signal 0 Oct 14 16:08:18 supersff kdm: :0[1522]: Abnormal termination of greeter for display :0, code 127, signal 0 Oct 14 16:15:04 supersff kdm: :0[1575]: Abnormal termination of greeter for display :0, code 127, signal 0 Oct 15 13:21:45 supersff kdm: :0[7402]: Abnormal termination of greeter for display :0, code 127, signal 0 Oct 15 13:28:56 supersff kdm: :0[1518]: Abnormal termination of greeter for display :0, code 127, signal 0 Oct 15 13:34:22 supersff kdm: :0[1497]: Abnormal termination of greeter for display :0, code 127, signal 0 Oct 15 13:36:07 supersff kdm: :0[1541]: Abnormal termination of greeter for display :0, code 127, signal 0 Oct 15 13:45:02 supersff kdm: :0[1575]: Abnormal termination of greeter for display :0, code 127, signal 0 Oct 15 15:02:31 supersff kdm[1639]: X server died during startup Oct 15 15:02:31 supersff kdm[1639]: X server for display :0 can't be started, session disabled Oct 15 15:29:30 supersff kdm_greet[1628]: Cannot load /usr/share/apps/kdm/faces/.default.face: No such file or directory Since downgrading the packages from from testing didn't help, I have re-enable testing and reinstalled intel-dri-7.6-1 xf86-video-intel-2.9.0-1 and libgl-7.6-1. Any other ideas welcomed :p -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Thursday 15 October 2009 05:54:11 pm David C. Rankin wrote:
Any other ideas welcomed :p
Maybe a brake-through I managed to get a strace of startx. While the strace was running, I had a sustained X session with a small xterm in the top-left corner of the display. I couldn't do anything with it and X crashed at the end of the strace session, but hopefully the information I captured will let a archlinux X guru solve the riddle. The strace output is here: http://www.3111skyline.com/download/Archlinux/bugs/supersff/strace-startx.tx... (~30k) -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Thursday 15 October 2009 06:06:15 pm David C. Rankin wrote:
On Thursday 15 October 2009 05:54:11 pm David C. Rankin wrote:
Any other ideas welcomed :p
Maybe a brake-through I managed to get a strace of startx. While the strace was running, I had a sustained X session with a small xterm in the top-left corner of the display. I couldn't do anything with it and X crashed at the end of the strace session, but hopefully the information I captured will let a archlinux X guru solve the riddle. The strace output is here:
http://www.3111skyline.com/download/Archlinux/bugs/supersff/strace-startx.t xt
(~30k)
Guys, I went ahead and opened a ticket under packages/testing. (I hope that is the right place) As always, I ready and willing to do what ever testing or provide any additional information anybody may want to see. Just let me know. The ticket is: http://bugs.archlinux.org/task/16682 -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
2009/10/16 David C. Rankin <drankinatty@suddenlinkmail.com>:
On Thursday 15 October 2009 06:06:15 pm David C. Rankin
[...]
Maybe a brake-through I managed to get a strace of startx. While the strace was running, I had a sustained X session with a small xterm in the top-left corner of the display. I couldn't do anything with it and X crashed at the end of the strace session, but hopefully the information I captured will let a archlinux X guru solve the riddle. The strace output is here:
http://www.3111skyline.com/download/Archlinux/bugs/supersff/strace-startx.t xt
Though i'm far from being any guru , i did notice the following lines: 472 (EE) Failed to load module "fbdev" (module does not exist, 0) 476 FATAL: Module fbcon not found. 477 Setting master 478 record: RECORD extension enabled at configure time. 479 record: This extension is known to be broken, disabling extension now.. 480 record: http://bugs.freedesktop.org/show_bug.cgi?id=20500 481 482 waiting for X server to shut down Dropping master (the numbers are the linenumbers). Could it be that it's just trying to load the wrong video driver? mvg, Guus
On Friday 16 October 2009 06:11:10 am Guus Snijders wrote:
2009/10/16 David C. Rankin <drankinatty@suddenlinkmail.com>:
On Thursday 15 October 2009 06:06:15 pm David C. Rankin
[...]
Maybe a brake-through I managed to get a strace of startx. While the strace was running, I had a sustained X session with a small xterm in the top-left corner of the display. I couldn't do anything with it and X crashed at the end of the strace session, but hopefully the information I captured will let a archlinux X guru solve the riddle. The strace output is here:
http://www.3111skyline.com/download/Archlinux/bugs/supersff/strace-start x.t xt
Though i'm far from being any guru , i did notice the following lines:
472 (EE) Failed to load module "fbdev" (module does not exist, 0)
476 FATAL: Module fbcon not found. 477 Setting master 478 record: RECORD extension enabled at configure time. 479 record: This extension is known to be broken, disabling extension now.. 480 record: http://bugs.freedesktop.org/show_bug.cgi?id=20500 481 482 waiting for X server to shut down Dropping master
(the numbers are the linenumbers).
Could it be that it's just trying to load the wrong video driver?
mvg, Guus
Well (yes and no), that's what I thought, but evidently the fbdev error isn't the show-stopper. It is expected and normally doesn't cause problems. The fbcon is the Biggie!. But that is now some compiled into the kernel magic that I'm pretty much at a loss to deal with. I installed xf86-video-fbdev and the fbdev error is gone, but as others correctly said, that wasn't the problem. The only thing I am 100% certain of at this point is there is a problem somewhere because the box worked great up until I did the update on 10/8 and I haven't seen kde since... I'm sure it's something simple that just needs to be fixed in the kernel or in one of the modules. But I am equally sure that it will take someone much smarter than I on the kernel or module at issue to do it :p -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
The fbcon is the Biggie!. But that is now some compiled into the kernel magic that I'm pretty much at a loss to deal with. I installed xf86-video-fbdev and the fbdev error is gone, but as others correctly said, that wasn't the problem.
fbcon is the framebuffer console,i.e. a module that provides a console over a framebuffer device (as opposed to the VGA console). It shouldn't be an issue for anything X related.
The only thing I am 100% certain of at this point is there is a problem somewhere because the box worked great up until I did the update on 10/8 and I haven't seen kde since...
I'm sure it's something simple that just needs to be fixed in the kernel or in one of the modules. But I am equally sure that it will take someone much smarter than I on the kernel or module at issue to do it :p
Does you KDE work if you try to log in as a new clean user? -- damjan
Hi! In data venerdì 16 ottobre 2009 23:20:45, Damjan Georgievski ha scritto:
Does you KDE work if you try to log in as a new clean user?
I'd also try to use another login manager, if you haven't tried this way yet, trying another desktop environment and trying to use the standard vesa driver in your xorg.conf (I think vesa will run on every video card, isn't it?). My odd bug related to xorg resetting (with no error) when pressing Enter was related to KDM, and the next kde-something update resolved it. Ok, maybe it's not related, but who knows?:) ciao! Dario Chiacchiera con i tuoi amici in tempo reale! http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com
On Friday 16 October 2009 07:30:51 pm Dario wrote:
Hi!
In data venerdì 16 ottobre 2009 23:20:45, Damjan Georgievski ha scritto:
Does you KDE work if you try to log in as a new clean user?
I'd also try to use another login manager, if you haven't tried this way yet, trying another desktop environment and trying to use the standard vesa driver in your xorg.conf (I think vesa will run on every video card, isn't it?).
My odd bug related to xorg resetting (with no error) when pressing Enter was related to KDM, and the next kde-something update resolved it. Ok, maybe it's not related, but who knows?:)
ciao!
Dario
Dario, I just went though that with the radeonhd driver and removing xorg.conf and using the kdm3 (kde3) greeter is the only way X will start now on my laptop. I have tried both kdm and kdm3 on the dell GX280 box (with the intel card) and nothing works. X just will not run (starts, crashes, exits) Like I've said before, I've worked through the wiki and tried both the "early start" and "late start" methods -- no help. I was hoping the strace of startx I posted with the bug report would help diagnose it. I'll go follow up there and see. Thanks for your help and if you think of anything else, let me know. I'll try anything at this poing :p -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Friday 16 October 2009 04:20:45 pm Damjan Georgievski wrote:
The fbcon is the Biggie!. But that is now some compiled into the kernel magic that I'm pretty much at a loss to deal with. I installed xf86-video-fbdev and the fbdev error is gone, but as others correctly said, that wasn't the problem.
fbcon is the framebuffer console,i.e. a module that provides a console over a framebuffer device (as opposed to the VGA console). It shouldn't be an issue for anything X related.
The only thing I am 100% certain of at this point is there is a problem somewhere because the box worked great up until I did the update on 10/8 and I haven't seen kde since...
I'm sure it's something simple that just needs to be fixed in the kernel or in one of the modules. But I am equally sure that it will take someone much smarter than I on the kernel or module at issue to do it :p
Does you KDE work if you try to log in as a new clean user?
No, I can't even get X to start -- period. Not at me, not as root, not as a fresh user created with useradd, nothing. X is just completely broken on this box and I'm really at a loss as to how to fix it. I'm usually great with dealing with X issues. I've build it, mesa, drm from scratch before without issue. What is killing me is I don't understand how moving the module into the kernel (this KMS thing) changes or complicates that process so I'm just kind of spinning my wheels at this point :-( -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Thursday 15 October 2009 01:19:25 pm Xavier wrote:
On Thu, Oct 15, 2009 at 8:08 PM, David C. Rankin
<drankinatty@suddenlinkmail.com> wrote:
latest Xorg.0.log is here:
http://www.3111skyline.com/download/Archlinux/bugs/supersff/Xorg.0.log
I don't see any errors in your xorg log. You are 100% sure it is the correct one ? The timestamp from the log : (==) Log file: "/var/log/Xorg.0.log", Time: Wed Oct 14 16:15:03 2009
If you have any other suggestions or ideas, please let me know. Thanks.
also paste output of dmesg.
Xavier, I am also starting kdm from inittab on boot: x:5:respawn:/opt/kde/bin/kdm -nodaemon However stopping and restarting using /etc/rc.d/kdm restart makes no difference. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Thursday 15 October 2009 07:47:11 am pascal wrote:
Hi In the last Xorg.0.log I can see that you removed the "vga=0x31a" part. But the vesa module is still loaded (and unloaded short after) just after the intel module, and the output used is VGA1. I also have an 915 chipset (though a 915GM) and upgraded to Xorg from testing to see if I could reproduce your problem. Apart some serious performance regression (and some freezes...) it works almost fine. I diff'ed my Xorg.0.log with yours and I don't have the vesa module loaded. Also my output is set to LVDS1, which I remember changed when I went to KMS some months ago (before that the output was VGA1, if I record correctly). I also have a line saying " (**) intel(0): Kernel mode setting active, disabling FBC. ", which doesn't appear in your log. Makes me wonder if your kernel is really using KMS. When booted, does the framebuffer display in native resolution ? I switched back to Xorg from [extra] for stability matters. [testing] being for ... well, testing.
I have also posted the pertinent files that may hold more information here: http://www.3111skyline.com/download/Archlinux/bugs/supersff/rc.conf http://www.3111skyline.com/download/Archlinux/bugs/supersff/mkinitcpio.conf http://www.3111skyline.com/download/Archlinux/bugs/supersff/menu.lst Let me know if I can post anything else that might help get to the bottom of this. Thanks. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Thursday 15 October 2009 04:48:44 am Rafa Griman wrote:
Been looking through your log and see this line:
Kernel command line: root=/dev/sda6 ro vga=0x31a
Shouldn't you remove all the vga= and/or video= options in menu.lst?
Maybe that's the problem.
HTH
Rafa
Rafa, Thanks for the help. I had actually removed all vga= lines from /boot/grub/menu.lst when I configured the system to use the "Early, Start" method. Unfortunately -- same result. I have a minute to work with it so I will post a new set of log files. Thanks again. Hopefully we can get this fixed. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Sunday 11 October 2009 03:33:57 am Jan Spakula wrote:
Excerpts from David C. Rankin's message of So Okt 11 10:16:57 +0200 2009:
On Sunday 11 October 2009 03:10:15 am David C. Rankin wrote: I'm back already. The wiki page must be out of date. It says to put the following in modprobe.conf (which is deprecated):
options i915 modeset=1
Now what??
Put it in /etc/modprobe.d/modprobe.conf (that's where I have it).
Jan, What about modprobe.conf being deprecated?? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Wed 14 Oct 2009 13:45 -0500, David C. Rankin wrote:
On Sunday 11 October 2009 03:33:57 am Jan Spakula wrote:
Excerpts from David C. Rankin's message of So Okt 11 10:16:57 +0200 2009:
On Sunday 11 October 2009 03:10:15 am David C. Rankin wrote: I'm back already. The wiki page must be out of date. It says to put the following in modprobe.conf (which is deprecated):
options i915 modeset=1
Now what??
Put it in /etc/modprobe.d/modprobe.conf (that's where I have it).
Jan,
What about modprobe.conf being deprecated??
/etc/modprobe.conf is deprecated. /etc/modprobe.d/*.conf is used instead.
On Wednesday 14 October 2009 02:57:58 pm Loui Chang wrote:
/etc/modprobe.conf is deprecated. /etc/modprobe.d/*.conf is used instead.
Thanks Loui! -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Sunday 11 October 2009 03:33:57 am Jan Spakula wrote:
Excerpts from David C. Rankin's message of So Okt 11 10:16:57 +0200 2009:
On Sunday 11 October 2009 03:10:15 am David C. Rankin wrote: I'm back already. The wiki page must be out of date. It says to put the following in modprobe.conf (which is deprecated):
options i915 modeset=1
Now what??
Put it in /etc/modprobe.d/modprobe.conf (that's where I have it).
Jan, All, What has changed with regard to the intel driver?? My box has been dead-in- the-water since the 10/8 updates. Since then, I have set up KMS (both late and early), I have added options i915 modeset=1 to /etc/modprobe.d/modprobe.conf I have added the following to /etc/mkinitcpio.conf: MODULES="... intel_agp i915" FILES="... /etc/modprobe.d/modprobe.conf" I have rebuilt the initramfs with: mkinitcpio -p kernel26 And still when I boot, the process gets to "Entering Runlevel 5", then the screen flashes, the little circular X cursor appears for a second and the BAM X crashes and I'm back to the terminal. I can't think of anything else to try. The salt-in-the-wound is that this box worked perfectly before the Oct. 8 updates. I haven't seen a gui since then. Can anyone think of any reason that X will not keep running after it starts? Latest Xorg.0.log at: http://www.3111skyline.com/download/Archlinux/bugs/supersff/Xorg.0.log -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Wed, 2009-10-14 at 16:16 -0500, David C. Rankin wrote:
On Sunday 11 October 2009 03:33:57 am Jan Spakula wrote:
Excerpts from David C. Rankin's message of So Okt 11 10:16:57 +0200 2009:
On Sunday 11 October 2009 03:10:15 am David C. Rankin wrote: I'm back already. The wiki page must be out of date. It says to put the following in modprobe.conf (which is deprecated):
options i915 modeset=1
Now what??
Put it in /etc/modprobe.d/modprobe.conf (that's where I have it).
Jan, All,
What has changed with regard to the intel driver?? My box has been dead-in- the-water since the 10/8 updates. Since then, I have set up KMS (both late and early), I have added
options i915 modeset=1
to /etc/modprobe.d/modprobe.conf
I have added the following to /etc/mkinitcpio.conf:
MODULES="... intel_agp i915" FILES="... /etc/modprobe.d/modprobe.conf"
I have rebuilt the initramfs with:
mkinitcpio -p kernel26
And still when I boot, the process gets to "Entering Runlevel 5", then the screen flashes, the little circular X cursor appears for a second and the BAM X crashes and I'm back to the terminal. I can't think of anything else to try.
The salt-in-the-wound is that this box worked perfectly before the Oct. 8 updates. I haven't seen a gui since then. Can anyone think of any reason that X will not keep running after it starts? Latest Xorg.0.log at:
http://www.3111skyline.com/download/Archlinux/bugs/supersff/Xorg.0.log
Hi, I am no developer and just joined the list and not that experienced with Linux. So, if this is totally off the wall please bear with me. But I think I had a similar problem a few months back with Puppy Linux. I had upgraded to a new version of Puppy with a new kernel and then tried to install the same Nivida graphics driver for my Nvidia card that I had stored on my hard drive, and X failed after I installed the driver. It was because the driver was for an older kernel and caused X to fail. I had to get a new updated driver and reinstall and it. Tom B
On Thursday 15 October 2009 05:45:53 am Thomas Bewick wrote:
Hi, I am no developer and just joined the list and not that experienced with Linux. So, if this is totally off the wall please bear with me. But I think I had a similar problem a few months back with Puppy Linux.
I had upgraded to a new version of Puppy with a new kernel and then tried to install the same Nivida graphics driver for my Nvidia card that I had stored on my hard drive, and X failed after I installed the driver. It was because the driver was for an older kernel and caused X to fail. I had to get a new updated driver and reinstall and it.
Tom B
Tom, Thanks for the idea. I'll try anything at this point. I'll remove the xf86- video-intel package and reinstall it and see if that help. I'll report back. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
participants (13)
-
Damjan Georgievski
-
Dario
-
David C. Rankin
-
Dusty
-
Flavio Costa
-
Guus Snijders
-
Jan de Groot
-
Jan Spakula
-
Loui Chang
-
pascal
-
Rafa Griman
-
Thomas Bewick
-
Xavier