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
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
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
тАО08-25-2000 07:41 AM
тАО08-25-2000 07:41 AM
i am seeing some messages in a file
/var/adm/msgbuff
they read
WARNING: modpath: DLKM is not initialized
WARNING: modadm: DLKM is not initialized
repeated each a few time
any ideas?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-25-2000 07:48 AM
тАО08-25-2000 07:48 AM
SolutionNormally this error indicates that the current version of the kernel does not match the current version of the symbol table symtab in /stand/dlkm.
This can be verified with the following command:
echo mod_initialized/D | adb -k /stand/vmunix /dev/mem
You can resolve this issue by using the following procedure:
1. cd /stand/build
2. /usr/lbin/sysadm/system_prep -s system
3. mk_kernel -s system
4. kmupdate /stand/build/vmunix_test
5. shutdown -r 0
Note: Do not use reboot.
*************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-25-2000 07:48 AM
тАО08-25-2000 07:48 AM
Re: DLKM
I had this problem and looked it up on the Knowledge base. It's likely that the kernel '/stand/vmunix' does not match the running kernel. DLKM is a kernel module.
Have you regenerated the kernel and deferred a reboot? If so, then either reboot to get the new kernel or move your /stand/vmunix.prev to /stand/vmunix to revert your kernel.
Hope this helps,
John
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-25-2000 07:53 AM
тАО08-25-2000 07:53 AM
Re: DLKM
thnks for the help
Jim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-25-2000 08:17 AM
тАО08-25-2000 08:17 AM