Thanks to Greg Poole, Alex Gorbachev and Tom Blinn for their responses.
I have the DE600 nic working with my custom-built kernel.(two of them
actually) I previously added the NHD-3 kit to get the nic working, over a
year ago. My question was about the generic kernel. The 4.0f generic
kernel does not come wht DE600 support. What I wanted to know was if I
added support for the DE600 to the /usr/sys/conf/GENERIC file, did a
doconfig -c GENERIC and made the resulting /usr/sys/GENERIC/vmunix file my
new genvmunix, would I get everything that I would if I booted with the
original genvmunix. Would my new genvmunix give me everything that the old
genvmunix did?
According to Tom Blinn, it would. The reason why I asked was because the
new genvmunix file is 1.5 times the size. Since I only added one line I
wanted to know why the new kernel was so much bigger. According to Tom:
The step you don't know about to make this a smaller file is that in
the product build process, we use the "ostrip" command with the "-x"
option to remove the local symbol table, which is generally useful if
you have kernel sources and are debugging, or you need to analyze a
crash dump while the GENERIC kernel was running. It's not needed to
boot and run the kernel.
My new kernel boots. Tom said upgrading to 4.0g would be the best way to
fix this, but if I just need a genvmunix with DE600 support to build a
'real' kernel then this method would be fine.
Original post below:
-----Original Message-----
From: tru64-unix-managers-owner_at_ornl.gov
[mailto:tru64-unix-managers-owner_at_ornl.gov]On Behalf Of Trevor Osatchuk
Sent: Monday, December 17, 2001 1:55 PM
To: Tru64-Unix-Managers (E-mail)
Subject: genvmunix advice about ee nics
I have an Alphaserver 800 8/533 running 4.0f. This machine oringally came
with a de500 interface, but has since been upgraded to de600. Now, if I
have to make some changes and need to boot the generic kernel I get a
problem when booting. It prompts me to go into failsafe mode and check my
network parameters. I am guessing that this is because the generic kernel
does not have 'config_driver ee' in the GENERIC file and hence not in the
generic kernel. Now, I did a doconfig -c GENERIC and compared the resulting
/sys/GENERIC/vmunix and /genvmunix and got:
##> ls -l /sys/GENERIC/vmunix
-rwxr-xr-x 3 root system 15795184 Dec 17 13:42 /sys/GENERIC/vmunix
##> ls -l /genvmunix
-rwxr-xr-x 1 root system 9936144 Feb 24 2000 /genvmunix
Obviously, there is a huge discrepency in the files. What I want to know
is, how do I make a genvmunix kernel that will have everything that it
should in the first place and additionally have the ee driver support? Can
I use this new kernel? It is 1.5 times the size, though that doesn't matter
for disk space reasons, could it cause problems down the road?
Any input appreciated.
Trevor Osatchuk
Process Solutions Canada Ltd.
Support and Integration Analyst
(780) 452-2227 Ext. 286
trevor.osatchuk_at_pscl.com
Any man whose errors take ten years to correct is quite a man.
- J. Robert Oppenheimer, speaking of Albert Einstein
Received on Mon Dec 17 2001 - 22:57:16 NZDT