- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: X-server can not be started
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-04-2011 06:50 AM
10-04-2011 06:50 AM
Re: X-server can not be started
> "gvid_hom_cons" is in the status of "out'
"gvid_info" is in the status of "in' - type 'loadable'.
Mine as well
> What's about kernel driver 'graph3'? It should be 'in', too.
The same as mine.
> Can you select a monitor type (graphic mode) at boot-up?
Just after keyboard is activated?
I can, What excatly should I do at this stage?
> Can you find 'graph3' in your syslog.log?
Nothing concerning 'graph3' is mentioned on syslog.log
> Is xf86 activated in boot process (Sxxxxf86 in /sbin/rc2.d)?
> Does /etc/rc.config.d/xf86 exist?
Yes, it exists.
> Check the settings:
gvid_info: parameters are set to '1' all other are set to '0'.
It already exist.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-04-2011 07:36 AM
10-04-2011 07:36 AM
Re: X-server can not be started
> "gvid_info" is in the status of "in' - type 'loadable'.
>Mine as well
On Sunday you said:
>If it has any meaning, the "gvid_hom_cons" & "gvid_info" fields are in the status of "out for both parameters.
So "gvid_info" is in the status of "in' now?
BUT from your /var/X11/Xserver/logs/Xstarup.0.log:
>"ERROR - Detected GVID graphics devices but the gvid_info kernel
>module did not load successfully. /usr/bin/X11/X: unable to start an Xserver.
It looks like you have to do something here - maybe you can test or change something in SAM to get it work (Process new kernel?).
Just for interest:
>> Can you select a monitor type (graphic mode) at boot-up?
> Just after keyboard is activated?
>I can, What excatly should I do at this stage?
So during boot-up monitor messages are working?
Until CDE should start?
In syslog.log very soon (line 39) the slot of the graphics card is initialized (10/6/2/0 graph3).
But we should focus to this kernel parameter ...
V.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-06-2011 04:44 AM
10-06-2011 04:44 AM
Re: X-server can not be started
The gvid_him_cons and the gvid_info are in status of "out".
Indeed, I wrote that the gvid_info is in the status of "in" but it is not correct. (I might was wrong or something has been changed. Sorry for that).
I attached the kernel configuration from SAM just to be on a safe side.
Please let me know what parameter should I set on the kernel configuration.
Thank you,
Yali
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-06-2011 05:21 AM
10-06-2011 05:21 AM
Re: X-server can not be started
Configure gvid_info to current status of "in".
Type 'loadable'.
V.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-06-2011 05:54 AM
10-06-2011 05:54 AM
Re: X-server can not be started
I tried to set it via:
Action -> Configure Kernal Logging. Then, I set it to "Enable" but It cannot be config (it is not on the configurable paraneters list). How can I set it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-06-2011 07:32 AM
10-06-2011 07:32 AM
Re: X-server can not be started
V.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-08-2011 11:55 PM
10-08-2011 11:55 PM
Re: X-server can not be started
Ok, that option seems to be the one (add driver to kernel) but after I made the changes as request, I couldn't process new kernel.
I attached the print screen (process new kernel.png) and the /usr/sbin/config (due to the error message).
BR,
Yali
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-08-2011 11:57 PM
10-08-2011 11:57 PM
Re: X-server can not be started
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-09-2011 12:00 AM
10-09-2011 12:00 AM
Re: X-server can not be started
Sorry, there is a problem to attach files.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-09-2011 01:40 AM
10-09-2011 01:40 AM
Re: X-server can not be started
In addition, when I try to set the gvid_info via Action -> Add Driver(s) to Kernel, parameters cannot be changed.
The following message received:
"The kadmin command has failed to load driver module gvid_info. The stderr output from the command is showen below:
Kmadmin: gvid_info: Invalid argument"