Dr. Ephemeron Posted March 30, 2004 Report Share Posted March 30, 2004 (edited) What is the difference between starting Gnome with init 5 and starting it with startx? I notice that sometimes startx can give you problems with permissions and init 5 doesn't... I am not sure exactly how it works. For example, /dev/nvidia* is set 0600 by pam_console and if I use startx to start GNOME, glxgears won't run because it needs 0660. If I su and then init 5, it will run. Also I notice that shutdown from gnome that has been started using startx can give errors or seg faults when a shutdown after being started with init 5 will go smoothly. For example if I shutdown from GNOME after starx from console. I see a seg fault in the bootsplash routine. Although I have no ill effects from it. I need to look and see if it is a file permission thing causing it... probably is. Edited March 30, 2004 by Dr. Ephemeron Quote Link to comment Share on other sites More sharing options...
bvc Posted March 30, 2004 Report Share Posted March 30, 2004 (edited) in /etc/X11/XF86Config-4 at he very bottom put; Section "DRI" Mode 0660 EndSection not sure about everything else but you can read the scripts and follow them to see where they lead and what they do. Same concept with a .xinitrc in your $HOME dir. Stuff happens differently. Edited March 30, 2004 by bvc Quote Link to comment Share on other sites More sharing options...
Dr. Ephemeron Posted March 30, 2004 Author Report Share Posted March 30, 2004 (edited) So what log would I look in to see details of the shutdown seg fault of the "bootsplash"... I see nothing in messages? Err I mean I see nothing that looks like the same message that scrolls up the screen that is... I see stuff that may be it, that I don't understand. Edited March 30, 2004 by Dr. Ephemeron Quote Link to comment Share on other sites More sharing options...
Dr. Ephemeron Posted March 30, 2004 Author Report Share Posted March 30, 2004 (edited) Never mind... I found it in messages... it is a big mess of stuff. Mar 29 19:23:52 localhost shutdown: shutting down for system reboot Mar 29 19:23:52 localhost init: Switching to runlevel: 6 Mar 29 19:23:52 localhost gconfd (dr_ephemeron-2714): Received signal 1, shutting down cleanly Mar 29 19:23:53 localhost gconfd (dr_ephemeron-2714): Exiting Mar 29 19:23:54 localhost kernel: bootsplash 3.1.3-2003/11/14: looking for picture.... silentjpeg size 14856 bytes, found (800x600, 14808 bytes, v3). Mar 29 19:23:54 localhost kernel: bootsplash: status on console 0 changed to on Mar 29 19:23:54 localhost kernel: Unable to handle kernel paging request at virtual address e1df50f0 Mar 29 19:23:54 localhost kernel: printing eip: Mar 29 19:23:54 localhost kernel: c023fe77 Mar 29 19:23:54 localhost kernel: *pde = 1d3b2067 Mar 29 19:23:54 localhost kernel: *pte = 00000000 Mar 29 19:23:54 localhost kernel: Oops: 0000 [#1] Mar 29 19:23:54 localhost kernel: CPU: 0 Mar 29 19:23:54 localhost kernel: EIP: 0060:[splash_renderc+247/448] Tainted: PF VLI Mar 29 19:23:54 localhost kernel: EIP: 0060:[<c023fe77>] Tainted: PF VLI Mar 29 19:23:54 localhost kernel: EFLAGS: 00010202 Mar 29 19:23:54 localhost kernel: EIP is at splash_renderc+0xf7/0x1c0 Mar 29 19:23:54 localhost kernel: eax: 00000001 ebx: e1df50f0 ecx: e09d86f0 edx: 00000000 Mar 29 19:23:54 localhost kernel: esi: 00000000 edi: 00000000 ebp: db391db4 esp: db391d90 Mar 29 19:23:54 localhost kernel: ds: 007b es: 007b ss: 0068 Mar 29 19:23:54 localhost kernel: Process splash (pid: 2822, threadinfo=db390000 task=db3978c0) Mar 29 19:23:54 localhost kernel: Stack: 00000640 00000010 00000003 00000000 0000ad55 00000001 00000240 e1831000 Mar 29 19:23:54 localhost kernel: 00000007 db391dec c024052a e1831000 c041da40 00000007 00000000 c041dc34 Mar 29 19:23:54 localhost kernel: 0000025e 00000158 00000010 00000008 00000002 c1516000 c041da40 db391e78 Mar 29 19:23:54 localhost kernel: Call Trace: Mar 29 19:23:54 localhost kernel: [splash_cursor+362/480] splash_cursor+0x16a/0x1e0 Mar 29 19:23:54 localhost kernel: [<c024052a>] splash_cursor+0x16a/0x1e0 Mar 29 19:23:54 localhost kernel: [fbcon_cursor+647/992] fbcon_cursor+0x287/0x3e0 Mar 29 19:23:54 localhost kernel: [<c0238bb7>] fbcon_cursor+0x287/0x3e0 Mar 29 19:23:54 localhost kernel: [do_IRQ+229/256] do_IRQ+0xe5/0x100 Mar 29 19:23:54 localhost kernel: [<c010d845>] do_IRQ+0xe5/0x100 Mar 29 19:23:54 localhost kernel: [common_interrupt+24/32] common_interrupt+0x18/0x20 Mar 29 19:23:54 localhost kernel: [<c010bf28>] common_interrupt+0x18/0x20 Mar 29 19:23:54 localhost kernel: [complement_pos+18/368] complement_pos+0x12/0x170 Mar 29 19:23:54 localhost kernel: [<c01fc222>] complement_pos+0x12/0x170 Mar 29 19:23:54 localhost kernel: [hide_cursor+69/96] hide_cursor+0x45/0x60 Mar 29 19:23:54 localhost kernel: [<c01fc715>] hide_cursor+0x45/0x60 Mar 29 19:23:54 localhost kernel: [redraw_screen+312/464] redraw_screen+0x138/0x1d0 Mar 29 19:23:54 localhost kernel: [<c01fc9a8>] redraw_screen+0x138/0x1d0 Mar 29 19:23:54 localhost kernel: [vc_resize+923/1184] vc_resize+0x39b/0x4a0 Mar 29 19:23:54 localhost kernel: [<c01fd09b>] vc_resize+0x39b/0x4a0 Mar 29 19:23:54 localhost kernel: [splash_status+249/368] splash_status+0xf9/0x170 Mar 29 19:23:54 localhost kernel: [<c023d429>] splash_status+0xf9/0x170 Mar 29 19:23:54 localhost kernel: [splash_write_proc+478/1056] splash_write_proc+0x1de/0x420 Mar 29 19:23:54 localhost kernel: [<c023d73e>] splash_write_proc+0x1de/0x420 Mar 29 19:23:54 localhost kernel: [dentry_open+173/416] dentry_open+0xad/0x1a0 Mar 29 19:23:54 localhost kernel: [<c015314d>] dentry_open+0xad/0x1a0 Mar 29 19:23:54 localhost kernel: [proc_file_write+46/64] proc_file_write+0x2e/0x40 Mar 29 19:23:54 localhost kernel: [<c017fece>] proc_file_write+0x2e/0x40 Mar 29 19:23:54 localhost kernel: [vfs_write+142/224] vfs_write+0x8e/0xe0 Mar 29 19:23:54 localhost kernel: [<c0153cde>] vfs_write+0x8e/0xe0 Mar 29 19:23:54 localhost kernel: [sys_write+46/80] sys_write+0x2e/0x50 Mar 29 19:23:54 localhost kernel: [<c0153dae>] sys_write+0x2e/0x50 Mar 29 19:23:54 localhost kernel: [sysenter_past_esp+82/121] sysenter_past_esp+0x52/0x79 Mar 29 19:23:54 localhost kernel: [<c010afa9>] sysenter_past_esp+0x52/0x79 Mar 29 19:23:54 localhost kernel: Mar 29 19:23:54 localhost kernel: Code: c6 07 00 00 00 75 11 8b 45 18 8a 10 40 81 e2 ff 00 00 00 89 45 18 89 d7 89 f8 8b 55 ec 84 c0 78 15 8b 45 f0 8b 55 e8 85 c0 74 0b <66> 8b 03 89 c2 81 e2 ff ff 00 00 83 c3 02 f7 c7 40 00 00 00 75 Mar 29 19:23:54 localhost kernel: <6>bootsplash: status on console 0 changed to o Edited March 30, 2004 by Dr. Ephemeron Quote Link to comment Share on other sites More sharing options...
Dr. Ephemeron Posted March 30, 2004 Author Report Share Posted March 30, 2004 ah, it's a segmentation fault that occurs when /sbin/bootspash.sh executes /sbin/splash Quote Link to comment Share on other sites More sharing options...
bvc Posted March 30, 2004 Report Share Posted March 30, 2004 ah.....well I don't use that :P Quote Link to comment Share on other sites More sharing options...
Dr. Ephemeron Posted March 30, 2004 Author Report Share Posted March 30, 2004 It has already been reported. Click to See Bug 8608 Quote Link to comment Share on other sites More sharing options...
Qchem Posted March 30, 2004 Report Share Posted March 30, 2004 in /etc/X11/XF86Config-4 at he very bottom put; Section "DRI" Mode 0660 EndSection AFAIK you can't use DRI with the official nvidia drivers so this probably won't help. Quote Link to comment Share on other sites More sharing options...
bvc Posted March 30, 2004 Report Share Posted March 30, 2004 (edited) in /etc/X11/XF86Config-4 at he very bottom put; Section "DRI" Mode 0660 EndSection AFAIK you can't use DRI with the official nvidia drivers so this probably won't help. why not? There was a time when after updating your nvidia drivers you were locked out of X because of the console.perms/dri issue. Because of that I suggested trying it since glxgears isn't part of nvidia but X. Having nvidia isn't going to stop glxgears from checking this value. Is it? Edited March 30, 2004 by bvc Quote Link to comment Share on other sites More sharing options...
sttroopers Posted March 30, 2004 Report Share Posted March 30, 2004 I dont know. Nvidia recommends removing dri.. You should also remove the following lines: Load "dri" Load "GLcore" if they exist. There are also numerous options that can be added to the XF86Config file to fine-tune the NVIDIA XFree86 driver. Please see Appendix D for a complete list of these options. Quote Link to comment Share on other sites More sharing options...
Qchem Posted March 30, 2004 Report Share Posted March 30, 2004 I thought DRI and the GL provided by the nvidia drivers were competing, hence the need to remove DRI from the config. Having heard more of the history from bvc it sounds like it may just be permissions based. Sorry. Assumption, the mother of all fsck's :D Quote Link to comment Share on other sites More sharing options...
Dr. Ephemeron Posted March 30, 2004 Author Report Share Posted March 30, 2004 I just edit console.perms and put in 0660 and it works. Quote Link to comment Share on other sites More sharing options...
peman Posted March 30, 2004 Report Share Posted March 30, 2004 For example if I shutdown from GNOME after starx from console. I see a seg fault in the bootsplash routine. Although I have no ill effects from it. I need to look and see if it is a file permission thing causing it... probably is. I have the same problem, at least i think this is the same problem. When i shutdown my pc from KDE or Gnome its just a black picture with texts on thats impossible to read, how can i Fix this? It happened after i install Nvidia! Quote Link to comment Share on other sites More sharing options...
bvc Posted March 31, 2004 Report Share Posted March 31, 2004 (edited) boot w/o bootsplash and vga to normal. Good old black and white Oh, it is an nvidia issue. Happens to me. In your bootloader config change splash=silent to splash=quiet and change vga= 788 (usually) to vga=normal Linux is useless without a console. Edited March 31, 2004 by bvc Quote Link to comment Share on other sites More sharing options...
illogic-al Posted March 31, 2004 Report Share Posted March 31, 2004 I just edit console.perms and put in 0660 and it works. yup. that's the ticket :D Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.