Brian Cameron <[email protected]> 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
[email protected]

Reply via email to