Operating System - HP-UX
1834533 Members
2749 Online
110069 Solutions
New Discussion

Re: error while adding kernel driver

 
mike worrell
Regular Advisor

error while adding kernel driver

I have a k460 on 11.0 OS.
This is a test box that will replace a live box that is being decommisioned. In comparing
the 2 I have found a few drivers that needed
to be added in. For instance I went to
Sam/Kernel Config/drivers
and selected the tape2 driver to move in
when i hit ok to add I got this error:
"can't build kernel using /usr/sbin/config
Make: don't know how to make /usr/conf/lib/libcommon.a. Stop.
Config make did an exit (1)
exitcode -71

Anyone have a clue what I need to do to get
this fixed. Tried several other drivers and
got same error.

Help plz,
Mike
3 REPLIES 3
Christopher McCray_1
Honored Contributor

Re: error while adding kernel driver

I don't know what type of tape drive you are using, but the current standard tape driver I use is stape. Find this one and load it. It should be on the application CDs if not in your list.

Good Luck.
It wasn't me!!!!
linuxfan
Honored Contributor

Re: error while adding kernel driver

Hi Mike,

what kind of tape drive are you using?

Did you try building the kernel manually?

-Regards
Ramesh
They think they know but don't. At least I know I don't know - Socrates
Varghese Mathew
Trusted Contributor

Re: error while adding kernel driver

Hi,

Which king of tape you are attaching??, if the system is not showing the device as CLAIMED even after connecting the drive then through SAM you can try going ahead to find the missing tape drive so let the system add the drivers automatically and then you may need to reboot the system . But before any such things you do ,please do a make_recovery tape and keep the current kernel's copy also.

More over there are few patches also to meet the vulnerabilities of latest DLT 8000 drives' functioning with the HP UX utilities -

The following is the recommended patch set for a DLT8000 at 11.00. You may
want to consider loading all these if your environment will permit it.

Patch Status Description

PHCO_16195 s700_800 11.00 mc(1m) bug fixes and enhancements
PHCO_16748 s700_800 11.00 mt(1) new reserve, release, status options
PHCO_23854 s700_800 11.00 cumulative fbackup(1M)/frecover(1M) patch
PHCO_19772 s700_800 11.00 st(1M), shared tape, cumulative patch
PHCO_21596 s700_800 11.00 mksf(1M) cumulative patch
PHCO_23876s 700_800 11.00 cumulative SAM/ObAM patch
PHCO_23963 s700_800 11.00 libc cumulative header file patch
PHCO_23422 s700_800 11.00 cumulative libsec patch
PHCO_23651 s700_800 11.00 fsck_vxfs(1M) cumulative patch
PHCO_24148 s700_800 11.00 libc cumulative patch
PHKL_18543 s700_800 11.00 PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_20016 s700_800 11.00 2nd CPU not recognized in G70/H70/I70
PHKL_24004 s700_800 11.00 SCSI IO Subsystem Cumulative Patch
PHKL_24027 s700_800 11.00 VxFS 3.1 cumulative patch
PHKL_22589 s700_800 11.00 LOFS, select(), IDS/9000 and umount race fix
PHKL_22677 s700_800 11.00 fix of getdirentries, MVFS, rcp, mmap & IDS
PHKL_23226 s700_800 11.00 syscall, msem_lock, umask cumulative patch
PHKL_23790 s700_800 11.00 SCSI Tape (stape) cumulative
PHKL_24116 s700_800 11.00 probe,sysproc,PM,VM,PA-8700 cumulative patch
PHNE_20949 s700_800 11.00 HyperFabric B.11.00.0[0-8] cumulative patch
PHNE_22159 s700_800 11.00 telnet kernel and telnetd(1M) patch
PHSS_19537 s700_800 11.00 STM cumulative, dm_stape disk_em panic scsi3

Hope this helps,
Cheers !!!
Mathew
Cheers !!!