topic Re: making a new kernel to configure btlan3 driver. in Operating System - HP-UX

making a new kernel to configure btlan3 driver.

John Paine — Tue, 20 Feb 2001 11:31:48 GMT

Hi All,
I am trying to confiure the btlan3 driver into the kernel (Currently getting UNCLAIMED UNKNOWN from ioscan)Have changed my C200 box into a standalone unit and run SAM to add driver.However this is the error message I get:-
/usr/ccs/bin/ld : Unsatisfied symbols
bucket (data)
lanc_lla_open (code)
.....Error exit code 1

Has anyone seen this before or know of a way to fix my problem?
Many thanks in anticpation.

JP.

Re: making a new kernel to configure btlan3 driver.

Marc Dijkstra — Tue, 20 Feb 2001 12:11:53 GMT

May be an obvious question, but is this the onboard 10/100mb card, or an additional PCI card?

How many cards are reported with a ioscan -fknC lan? This sounds like a driver issue, but if you could clarify these points, TS should be easier.

MND

Re: making a new kernel to configure btlan3 driver.

John Paine — Tue, 20 Feb 2001 13:55:14 GMT

Hi Marc,
Thanks for the response.The lan0 i/f
is the 10/100BaseT on board card.There is no PCI lan card fitted, consequently ioscan -fnkC gives just the one i/f - there is one thing though....this box has had another backplane fitted and I know there used to be an issue with trying to configure PCI lan cards on a c180 which had a serial number lower than
US67430000 but I'm not sure if this error I have is a symptom of that problem.
Thanks,
JP.

Re: making a new kernel to configure btlan3 driver.

Alex Glennie — Tue, 20 Feb 2001 13:58:26 GMT

Has the system been upgraded 32-> 64 bit ? or 10.20 -> 11.xx ?

Does model output return as expected ?

Re: making a new kernel to configure btlan3 driver.

Rita C Workman — Tue, 20 Feb 2001 13:59:19 GMT

Well I came across a thread showing 'similar' error as yours you may want to review:

http://us-support.external.hp.com/cki/bin/doc.pl/sid=2b58d5921b41405793/screen=ckiDisplayDocument?docId=200000046363387

If this doesn't help, let me suggest creating the kernel manually. More than once, I couldn't get SAM to build the kernel, but manually it built and worked fine. Here's a good 'ol thread for building manually:

http://us-support.external.hp.com/cki/bin/doc.pl/sid=ac36af9d0ccafeb534/screen=ckiDisplayDocument?docId=200000006303790

/rcw

Re: making a new kernel to configure btlan3 driver.

Marc Dijkstra — Tue, 20 Feb 2001 14:02:23 GMT

Is this perhaps a 10.20 ACE problem? I know that the C200 (with the B132L+) HAD to have the ACE bundle loaded as they were the first workstations with the 10/100mb IF and the WSE instead of the FWD SCSI interface.

If a lower rev of the software was loaded, problems existed with no understanding of the net IF.

Re: making a new kernel to configure btlan3 driver.

John Paine — Tue, 20 Feb 2001 14:18:10 GMT

Alex,
in answer to your questions....the box is probably about 5 years old so would suspect it's a 32bit m/c.Is there an easy command to find out for sure?..But more interestingly,the m/c was indeed originally loaded with 10.20 (same motherboard/lan0 and worked fine on network) but was upgraded to 11.0 and the guy who did the upgrade cannot recall if the box was ever "up" on the network...would this be some sort of HP-UX 11.0/driver problem? do I need to load a patch to fix?
Thanks
JP

Re: making a new kernel to configure btlan3 driver.

John Paine — Tue, 20 Feb 2001 14:30:05 GMT

Marc,
now that you mention it,I do recall having a problem with a C box before (360 I thought?) where I had to load the ACE OS to get the box to communicate properly.However,I now find OS 11.0 has been loaded.As for my reply to Alex's questions,I am now wondering if there is maybe a patch for 11.0 to fix this driver problem or if I have to downgrade back to 10.20?
Much appreciated.

JP.

Re: making a new kernel to configure btlan3 driver.

John Paine — Tue, 20 Feb 2001 14:33:14 GMT

Rita,
thanks for the response....unfortunately I could not follow your 2 threads as HP in the states won't let me in!!
However, I did try a manual mk_kernel from the command line and got the same error....I'm thinking now it may be an OS 11.0 problem having seen some other guys replies.
Thanks,
JP.