Re: [osol-discuss] startx failing after move from b129 => b133
Harry Putnam writes: > Alan Coopersmith > writes: > >> Harry Putnam wrote: >>> After booting into the new b133, my system fails with all these warnings >>> and errors in /var/log/Xorg.0.log. >>> >>> (WW) Warning, couldn't open module extmod >>> (EE) Failed to load module "extmod" (module does not exist, 0) >> >> Make sure your /etc/X11/xorg.conf does not contain a ModulePath line - it >> appears to be incorrectly set for the new path (the files moved in 130), >> and if you just remove it, Xorg will use the right path by default. >> >> In general, you should remove any settings from xorg.conf that you don't >> need to override - Xorg will use the defaults as much as possible - >> including removing the file altogether if you don't need to override any >> defaults. > > Egad.. I forgot I even had an xorg.conf in place. Removed it and > startx worked fine. > > Thanks.. > > There was a time I tried to get X to have a huge virtual desktop like > I've done on linux for yrs by having this in xorg.conf: > >SubSection "Display" >Depth 24 >Modes "1280x1024" "1024x768" "800x600" "640x480" >Virtual 2048 1536 >Viewport 0 0 >EndSubSection > > But never did get it to fly on Osol.. I forgot to remove the > xorg.conf from that experiment. I may have spoke a tad bit too soon... Now I have no keyboard. It appears there is a problem with keyboard in Xorg.0.log but I'm not really sure what I'm looking at here. I've posted it below. This is on b133 These lines mention that no CORE keyboard or mouse input devices are found. (==) ModulePath set to "/usr/lib/xorg/modules/amd64,/usr/X11/lib/modules/" (II) Cannot locate a core pointer device. (II) Cannot locate a core keyboard device. (II) The server relies on HAL to provide the list of input devices. If no devices become available, reconfigure HAL or disable AutoAddDevices. (II) LoadModule: "extmod" But then later on hal appears to get the mouse figured out but not the keyboard. Full Xorg.0.log X.Org X Server 1.7.4 Release Date: 2010-01-08 X Protocol Version 11, Revision 0 Build Operating System: SunOS 5.11 i86pc Current Operating System: SunOS zfs 5.11 snv_133 i86pc Build Date: 01 February 2010 03:45:48PM Solaris ABI: 64-bit Current version of pixman: 0.16.4 Before reporting problems, check http://sunsolve.sun.com/ 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: Tue Feb 23 22:22:39 2010 (II) Loader magic: 622318 (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 2 (--) PCI:*(0:1:0:0) 1002:4e4a:1043:c000 ATI Technologies Inc R360 NJ [Radeon 9800 XT] rev 0, Mem @ 0xe800/134217728, 0xf803/65536, I/O @ 0xd000/256, BIOS @ 0x/65536 (--) PCI: (0:1:0:1) 1002:4e6a:1043:c001 ATI Technologies Inc RV350 NJ [Radeon 9800 XT] (Secondary) rev 0, Mem @ 0xf000/134217728, 0xf802/65536, BIOS @ 0x/65536 (--) console driver: SUNWtext (==) Using default built-in configuration (30 lines) (==) --- Start of built-in configuration --- Section "Device" Identifier "Builtin Default ati Device 0" Driver "ati" EndSection Section "Screen" Identifier "Builtin Default ati Screen 0" Device "Builtin Default ati Device 0" EndSection Section "Device" Identifier "Builtin Default vesa Device 0" Driver "vesa" EndSection Section "Screen" Identifier "Builtin Default vesa Screen 0" Device "Builtin Default vesa Device 0" EndSection Section "Device" Identifier "Builtin Default fbdev Device 0" Driver "fbdev" EndSection Section "Screen" Identifier "Builtin Default fbdev Screen 0" Device "Builtin Default fbdev Device 0" EndSection Section "ServerLayout" Identifier "Builtin Default Layout" Screen "Builtin Default ati Screen 0" Screen "Builtin Default vesa Screen 0" Screen "Builtin Default fbdev Screen 0" EndSection (==) --- End of built-in configuration --- (==) ServerLayout "Builtin Default Layout" (**) |-->Screen "Builtin Default ati Screen 0" (0) (**) | |-->Monitor "" (**) | |-->Device "Builtin Default ati Device 0" (==) No monitor specified for screen "Builtin Default ati Screen 0". Using a default monitor configuration. (**) |-->Screen "Builtin Default vesa Screen 0" (1) (**) | |-->M
Re: [osol-discuss] startx failing after move from b129 => b133
Alan Coopersmith writes: > Harry Putnam wrote: >> After booting into the new b133, my system fails with all these warnings >> and errors in /var/log/Xorg.0.log. >> >> (WW) Warning, couldn't open module extmod >> (EE) Failed to load module "extmod" (module does not exist, 0) > > Make sure your /etc/X11/xorg.conf does not contain a ModulePath line - it > appears to be incorrectly set for the new path (the files moved in 130), > and if you just remove it, Xorg will use the right path by default. > > In general, you should remove any settings from xorg.conf that you don't > need to override - Xorg will use the defaults as much as possible - > including removing the file altogether if you don't need to override any > defaults. Egad.. I forgot I even had an xorg.conf in place. Removed it and startx worked fine. Thanks.. There was a time I tried to get X to have a huge virtual desktop like I've done on linux for yrs by having this in xorg.conf: SubSection "Display" Depth 24 Modes "1280x1024" "1024x768" "800x600" "640x480" Virtual 2048 1536 Viewport 0 0 EndSubSection But never did get it to fly on Osol.. I forgot to remove the xorg.conf from that experiment. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] startx failing after move from b129 => b133
Brian Cameron writes: > I would recommend starting your desktop like this: > > startx /etc/gdm/Xsession gnome-session That fails even on the old build 129 BE, not to mention on 133. Running the suggested command: startx /etc/gdm/Xsession gnome-session: Errors from /var/log/Xorg.0.log (from my last good BE build 129) [...] (EE) Couldn't init device "hotkey" (EE) config/hal: NewInputDeviceRequest failed compiled for 1.6.5, module version = 1.3.2 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 4.0 (EE) input: Failed to get keyboard LED's: No such device (EE) input: Failed to set keyboard LED's: No such device (EE) input: Failed to get keyboard LED's: No such device (EE) input: Failed to get keyboard LED's: No such device (EE) input: Failed to set keyboard LED's: No such device (EE) input: Failed to get keyboard LED's: No such device (EE) input: Failed to get keyboard LED's: No such device (EE) input: Failed to set keyboard LED's: No such device compiled for 1.6.5, module version = 1.4.0 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 4.0 (EE) Couldn't init device "hotkey" (EE) config/hal: NewInputDeviceRequest failed [...] input: Device no longer present - removing. disable primary dac finished PLL2 finished PLL1 Entering Restore TV Restore TV PLL Restore TVHV Restore TV Restarts Restore Timing Tables Restore TV standard Leaving Restore TV ---- ---=--- - Starting X with: startx /usr/bin/dbus-launch --exit-with-session gnome-session Also leaves some errors in /var/log/Xorg.0.log but starts up X and seems to run fine. Errors from /var/log/Xorg.0.log: startx /usr/bin/dbus-launch --exit-with-session gnome-session: [...] (EE) Couldn't init device "hotkey" (EE) config/hal: NewInputDeviceRequest failed compiled for 1.6.5, module version = 1.3.2 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 4.0 (EE) input: Failed to get keyboard LED's: No such device (EE) input: Failed to set keyboard LED's: No such device (EE) input: Failed to get keyboard LED's: No such device (EE) input: Failed to get keyboard LED's: No such device (EE) input: Failed to set keyboard LED's: No such device (EE) input: Failed to get keyboard LED's: No such device (EE) input: Failed to get keyboard LED's: No such device (EE) input: Failed to set keyboard LED's: No such device compiled for 1.6.5, module version = 1.4.0 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 4.0 (EE) Couldn't init device "hotkey" (EE) config/hal: NewInputDeviceRequest failed [...] input: Device no longer present - removing. Unhandled monitor type 0 Unhandled monitor type 0 So, I'm not that sure how correct the environment is but X starts and I don't notice any obvious problems while working in the environment. However neither one of those commands works on 133 ---- ---=--- - Running build 133 now. I'll post the errors using your suggested command in the environment. startx /etc/gdm/Xsession gnome-session: (Note: I did notice there is no mention of `hal', as there is in the other failure messages) [...] (EE) Failed to load module "extmod" (module does not exist, 0) (EE) Failed to load module "ia" (module does not exist, 0) compiled for 4.0.2, module version = 1.0.0 Module class: X.Org Server Extension (EE) Failed to load module "dbe" (module does not exist, 0) (EE) Failed to load module "dri" (module does not exist, 0) (EE) Failed to load module "dri2" (module does not exist, 0) (EE) Failed to load module "xtsol" (module does not exist, 0) (EE) Failed to load module "radeon" (module does not exist, 0) (EE) No drivers available. [...] Fatal server error: no screens found ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] startx failing after move from b129 => b133
Harry Putnam wrote: > After booting into the new b133, my system fails with all these warnings > and errors in /var/log/Xorg.0.log. > > (WW) Warning, couldn't open module extmod > (EE) Failed to load module "extmod" (module does not exist, 0) Make sure your /etc/X11/xorg.conf does not contain a ModulePath line - it appears to be incorrectly set for the new path (the files moved in 130), and if you just remove it, Xorg will use the right path by default. In general, you should remove any settings from xorg.conf that you don't need to override - Xorg will use the defaults as much as possible - including removing the file altogether if you don't need to override any defaults. -- -Alan Coopersmith- alan.coopersm...@sun.com Oracle Solaris Platform Engineering: X Window System ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] startx failing after move from b129 => b133
Harry: After doing an image-update from build 129 to 133, I'm finding my old system for starting X fails now. I usually run with gdm disabled and rely on startx to get X up when I need it, so have a console login. I've been starting X with: startx /usr/bin/dbus-launch --exit-with-session gnome-session I would recommend starting your desktop like this: startx /etc/gdm/Xsession gnome-session Note that the /etc/gdm/Xsession script sets up the environment so the desktop will work properly, including sourcing all the scripts in /etc/X11/xinit/xinitrc.d. Note the /etc/X11/xinit/xinitrc.d/0070.dbus script will start dbus-launch for you. This also bypasses GDM, but your environment will be more correct if you start up this way. I'm checking now if just enabling gdm will work now, but don't have much hope since it doesn't bring on a graphical login from the console, which it should when enabled I think... but still trying a reboot with gdm running. Well, that didn't work at all. I see gdm trying over and over but just keeps popping back to console login which cannot be used because every few seconds it gdm trying again. Finally gdm apparently gives up... and console login works, so not able to get to X that way either. Check your Xorg logs in /var/log and /var/log/gdm. Do they report any errors which might indicate why it is failing? Often, such a failure is caused by a graphics driver issue. If that doesn't help, you can edit /etc/gdm/custom.conf so it has these lines: [debug] Enable=true Then restart GDM. This will cause GDM to put debug messages in your syslog file (/var/adm/messages). Reviewing these after the failure might help to highlight what is going wrong. Brian ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] startx failing after move from b129 => b133
After doing an image-update from build 129 to 133, I'm finding my old system for starting X fails now. I usually run with gdm disabled and rely on startx to get X up when I need it, so have a console login. I've been starting X with: startx /usr/bin/dbus-launch --exit-with-session gnome-session By-passing gdm altogether... I've had many problems with the graphical login, that have persisted over many builds so have come to this system over time. After booting into the new b133, my system fails with all these warnings and errors in /var/log/Xorg.0.log. (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled. (WW) Disabling Mouse0 (WW) Disabling Keyboard0 (WW) Warning, couldn't open module extmod (EE) Failed to load module "extmod" (module does not exist, 0) (WW) Warning, couldn't open module ia (EE) Failed to load module "ia" (module does not exist, 0) (WW) Warning, couldn't open module dbe (EE) Failed to load module "dbe" (module does not exist, 0) (WW) Warning, couldn't open module dri (EE) Failed to load module "dri" (module does not exist, 0) (WW) Warning, couldn't open module dri2 (EE) Failed to load module "dri2" (module does not exist, 0) (WW) Warning, couldn't open module xtsol (EE) Failed to load module "xtsol" (module does not exist, 0) (WW) Warning, couldn't open module radeon (EE) Failed to load module "radeon" (module does not exist, 0) (EE) No drivers available. Fatal server error: no screens found I never did understand the X startup on osol and have no real clue what might be happening here. There must have been some changes in how it works between the two builds (129-133) I'm checking now if just enabling gdm will work now, but don't have much hope since it doesn't bring on a graphical login from the console, which it should when enabled I think... but still trying a reboot with gdm running. Well, that didn't work at all. I see gdm trying over and over but just keeps popping back to console login which cannot be used because every few seconds it gdm trying again. Finally gdm apparently gives up... and console login works, so not able to get to X that way either. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
