HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Internal Error (using SAM)
Operating System - HP-UX
1833829
Members
2006
Online
110063
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
11-24-1999 11:32 AM
11-24-1999 11:32 AM
Internal Error (using SAM)
1) In SAM Kernel Configuration
2) Configurable Parameters appears the next message:
Internal error: The kernel discovery tool used by SAM failed.
Kernel changes cannot be made by SAM. The standard error output of the command
is shown below:
getkinfo: Syntax error in system file.
Incorrect driver/subsystem statement(s): fddi
Each driver/subsystem shown above is not valid for one of the following
reasons: The driver (including any aliases) is not recognized; there is no
support for this driver in the kernel libraries; the driver is not supported;
one or more dependency drivers for this driver are missing, not supported, or
not included in the kernel
libraries.
Be sure all kernel libraries from HP-UX product filesets are installed, and
that the driver/subsystem names shown above are valid.
Refer to the SAM logfile for more information. getkinfo: Unable to read
the kernel file "/stand/vmunix".
3) I can't see the parameters.
2) Configurable Parameters appears the next message:
Internal error: The kernel discovery tool used by SAM failed.
Kernel changes cannot be made by SAM. The standard error output of the command
is shown below:
getkinfo: Syntax error in system file.
Incorrect driver/subsystem statement(s): fddi
Each driver/subsystem shown above is not valid for one of the following
reasons: The driver (including any aliases) is not recognized; there is no
support for this driver in the kernel libraries; the driver is not supported;
one or more dependency drivers for this driver are missing, not supported, or
not included in the kernel
libraries.
Be sure all kernel libraries from HP-UX product filesets are installed, and
that the driver/subsystem names shown above are valid.
Refer to the SAM logfile for more information. getkinfo: Unable to read
the kernel file "/stand/vmunix".
3) I can't see the parameters.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-29-1999 01:14 AM
11-29-1999 01:14 AM
Re: Internal Error (using SAM)
This behaviour is a result of confusion about the fddi driver in the kernel.
It can be remedied fairly easily.
cd /stand/build
/usr/lbin/sysadm/system_prep -s system
vi system
remove the driver: fddi
mk_kernel -s system
move the new kernel into place and reboot:
mv /stand/vmunix /stand/vmunix.prev
mv /stand/build/vmunix_text /stand/vmunix
shutdown -r
If you need the fddi driver, you'll need to reinstall that from the application
cd.
Wyly O'Brien
It can be remedied fairly easily.
cd /stand/build
/usr/lbin/sysadm/system_prep -s system
vi system
remove the driver: fddi
mk_kernel -s system
move the new kernel into place and reboot:
mv /stand/vmunix /stand/vmunix.prev
mv /stand/build/vmunix_text /stand/vmunix
shutdown -r
If you need the fddi driver, you'll need to reinstall that from the application
cd.
Wyly O'Brien
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP