CDE doesn't load...

[Scott McDade]

Hello:

I have 3 brand new HP C8000 series workstation running HPUX 11.11. I am at a point that on all 3 systems I canâ t seem to get CDE to load. I am having a problem getting them onto the network. I have had to run set_parms initial from single user mode and the OS is in a state that I am not familiar with. In that VI isnâ t responding to normal command and such. I was thinking there could be a possible DNS conflict so I moved the resolv.conf out of the way and the machine still comes up in the same state where it hangs trying to load CDE. I have several C3750â s that I am comparing the info contained in the netconf and /etc/hosts and resolv.conf files and it all looks ok. I have noticed that on some of my systems C3750 but not all of them some of the parms in the netconf file are contained within â â quotes. But on some of the other the parm is not. So I am not sure what the correct format is. I have included the /etc/rc.log and would love it is someone could suggest other logs or possibly identify what could be causing this.

Thanks, Scott

[Alex Glennie · Accepted solution]

CDE relies heavily on succesful hostname resolution.

If this were me I'd :

edit /etc/nsswitch to ->

hosts: files

edit /etc/hosts to reflect your correct workstation hostname and ip.

leave resolv.conf for the time being (nsswitch entry above will force O/S to use host file only)

/sbin/init 2
/sbin/init 3

does CDE now start ?

If no try dr_dt and examine output

If yes ammend nsswitch.conf to start using DNS eg

hosts: files [NOTFOUND=continue] dns

[Alex Glennie]

One other point ....

ps -ef | grep dtlogin, is it running ?

If yes ALSO check /etc/dt/config/Xservers and /usr/dt/config/Xserver

look at last entry :

Local local@console /usr/bin/X11/X :0 if either file exists and has a # in front of this line remove it.

ps maybe worth posting your netconf file.

[Scott McDade]

Alex:

Thanks for the info, i will check out what you suggested. Shouldn't I still be able to get it on the network even though CDE won't load? The reason I ask is I am going to have to edit one or several files to fix this and VI isn't acting correctly and I am assuming its due the fact I am in single user mode. So editing files could be difficult.

-S

[Alex Glennie]

on the local console (monitor) you maybe able to prevent X starting at run level 3 by using and logging in from the ogin prompt.

Otherwise you could try at run level 2

as to vi is TERM set correctly ? normally hpterm will suffice see http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=982798

[Scott McDade]

Hello Alex and all:

I did as you suggested and edited the /etc/nsswitch.conf file but oddly enough there was not one on the new C8000 machines. So I sneaker-netâ ed it from one of my working C3750â s. Once I did that and modified the /etc/hosts file to look locally CDE came up instantly. The strange thing is we are still not on the network. I have included the rc.log file for your review it looks as if the 100BASE-T device configuration at boot is being skipped. I know there is a Ethernet card I the machine is there an easy way to check to see if it configured correctly? I also started comparing the device files on my working C3750 and my C8000 and notice that on the C8000 there is no /dev/lan0 device file. When I look at a working C3750 machine and do ls -l /dev/ | grep la, I find dev files for lan and lan0. On the new C8000 workstations I get the following for the same command Lan -> /dev/dlpi and there is no lan0 file. On the working C3750 machines I also find that snap -> /dev/dlpi

[Tim Nelson]

Scott,

For the LAN problems start with "lanscan".

This a good starting point to see what the system thinks it has for loaded LAN modules/interfaces.

It is possible that you have a NIC card that needs a driver that is not provided with the OS CD. An "ioscan -kf|grep unknown" may lead you to the HW address of interface with no drivers loaded"

Keep us posted.

[Scott McDade]

Hello Tim, Alex and all:

I ran lanscan as you suggested and it looks like the OS recognizes the interface.

What could be some of the other reason why the /etc/rc.log would complain about the 10BaseT interface?

~sniper from /etc/rc.log

No 100BASE-T device configured in system (btlan)
"/sbin/rc2.d/S333hpbtlan start" SKIPPED

I have attached the lanscan output as well.

Any other ideas as to where to look for why I can't get this workstation on the network?

-Scott