When I try to IPL Redhat Linux 7.2 on a Z/OS LPAR it does not pick up the
network device that it is supposed to pick up , therefore Iam unable
to connect to the LPAR thru telnet . Can anybody Help ?
When I try to IPL Redhat Linux 7.2 on a Z/OS LPAR it does not pick up the
network device that it is supposed to pick up , therefore Iam unable
to connect to the LPAR thru telnet . Can anybody Help ?
hello,
i will assume you have the redhat build that is meant for the z900 - it is kinda hard for me to find specs on this machine, esp. the networking part. is there any option for adding a network interface when you run redhat-config-network (something like that...) or netconfig?
[quote author=ramki link=board=2;threadid=5908;start=0#56261 date=1040274575]
When I try to IPL Redhat Linux 7.2 on a Z/OS LPAR it does not pick up the
network device that it is supposed to pick up , therefore Iam unable
to connect to the LPAR thru telnet . Can anybody Help ?
[/quote]
I tried tweaking my Linux box to change some network config
stuff but it does'nt give any results
When I install Linux on Zseries and when it comes to configuring the network interface it says it cannot find any
device
Or rather when I type "ifconfig eth0" at command prompt
it gives me a message:
Error finding interface information
Device not found
Please help
here try this :
type dmesg | less (the bar there is the pipe, in case you didnt know, or wasnt clear. My pipe is near my backspace key.)
Then scroll on down. You should see where there is a bunch of parts being identified and a driver being attatched. Keep going until you discover
a) No NIC being seen.
b) A NIC is found, and it happens to use XXYYZZ driver.
This will clue us into the next step. Obviously if there is no NIC being detected, that sucks, and may want to try antoher one. Possibly another brand. I have been using the $20 linksys cards for some time now with great reliability.
if you see a detected NIC, you can run setup from the command line as root.
Dear all
Thanks for all your support and help I managed to bring up
RHlinux7.2 on Zseries please find the output of command
dmesg|less below
Linux version 2.4.9-37tape (root@s390.redhat.de) (gcc version 2.95.3 20010315 (release)) #1 SMP Wed Apr 24 17:0
2:50 CEST 2002
We are running native
This machine has an IEEE fpu
On node 0 totalpages: 32768
zone(0): 32768 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/dasda1 dasd=1a00-1a01
Subchannel 0490 reports non-I/O subchannel type 0001
Highest subchannel number detected (hex) : 0490
Calibrating delay loop... 758.57 BogoMIPS
Memory: 119580k/131072k available (1719k kernel code, 0k reserved, 843k data, 64k init)
Dentry-cache hash table entries: 16384 (order: 5, 131072 bytes)
Inode-cache hash table entries: 8192 (order: 4, 65536 bytes)
Mount-cache hash table entries: 2048 (order: 2, 16384 bytes)
Buffer-cache hash table entries: 8192 (order: 3, 32768 bytes)
Page-cache hash table entries: 32768 (order: 6, 262144 bytes)
debug: Initialization complete
debug: reserved 4 areas of 4 pages for debugging ccwcache
POSIX conformance testing by UNIFIX
Detected 2 CPU's
Boot cpu address 0
cpu 0 phys_idx=0 vers=00 ident=050D63 machine=2064 unused=0000
cpu 1 phys_idx=1 vers=00 ident=150D63 machine=2064 unused=0000
init_mach : starting machine check handler
init_mach : machine check buffer : head = 00254E48
mach_handler : ready
mach_handler : waiting for wakeup
init_mach : machine check buffer : tail = 00254E4C
init_mach : machine check buffer : free = 00254E50
init_mach : CRW entry buffer anchor = 00254E54
init_mach : machine check handler ready
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
:Initializing RT netlink socket
Starting kswapd v1.8
VFS: Diskquotas version dquot_6.5.0 initialized
Journalled Block Device driver loaded
pty: 2048 Unix98 ptys configured
block: queued sectors max/low 79245kB/26415kB, 256 slots per queue
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
dasd:initializing...
debug: reserved 2 areas of 1 pages for debugging dasd
dasd:Registered successfully to major no 94
dasd(eckd):ECKD discipline initializing
dasd(eckd):1A00 on sch 848: 3390/0A(CU:3990/01) Cyl:3339 Head:15 Sec:224
dasd(eckd):1A00 on sch 848: 3390/0A(CU:3990/01): Configuration data read
debug: reserved 2 areas of 1 pages for debugging dasda
dasd(eckd):1A01 on sch 849: 3390/0A(CU:3990/01) Cyl:3339 Head:15 Sec:224
dasd(eckd):1A01 on sch 849: 3390/0A(CU:3990/01): Configuration data read
debug: reserved 2 areas of 1 pages for debugging dasdb
dasd:waiting for responses...
dasd(eckd):/dev/dasda(94:0),1a00@0x3504kB blks): 2404080kB at 48kB/trk compatible disk layout
dasd(eckd):/dev/dasdb(94:4),1a01@0x3514kB blks): 2404080kB at 48kB/trk compatible disk layout
Partition check:
dasda:VOL1/ 0X1A00: dasda dasda1
dasdb:VOL1/ 0X1A01: dasdb dasdb1
dasd(eckd):We are interested in: CU 3880/00
dasd(eckd):We are interested in: CU 3990/00
dasd(eckd):We are interested in: CU 2105/00
dasd(eckd):We are interested in: CU 9343/00
dasd:Registered ECKD discipline successfully
dasd(fba):FBA discipline initializing
dasd(fba):We are interested in: Dev 9336/00 @ CU 6310/00
dasd(fba):We are interested in: Dev 3370/00 @ CU 3880/00
dasd:Registered FBA discipline successfully
dasd:initialization finished
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
debug: reserved 4 areas of 16 pages for debugging cio_msg
debug: cio_msg: new level 2
debug: reserved 4 areas of 16 pages for debugging cio_trace
debug: cio_trace: new level 2
debug: reserved 4 areas of 4 pages for debugging cio_crw
debug: cio_crw: new level 6
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 8Kbytes
TCP: Hash tables configured (established 4096 bind 8192)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 16k freed
EXT3 FS 2.4-0.9.11, 3 Oct 2001 on dasd(94,1), internal journal
Starting lcs module $Revision: 1.1.2.1 $ $Date: 2002/03/29 00:14:37 $
with chandev support,with multicast support, with ethernet support, with token ring support.
debug: reserved 16 areas of 2 pages for debugging lcs
debug: lcs: new level 0
eth0: ip v6 supported no enabled no
eth0: multicast supported yes enabled yes
lcs: eth0 configured as follows read subchannel=13c write subchannel=13d
read_devno=0202 write_devno=0203
hw_address=00:06:29:FB:60C rel_adapter_no=0
A partially successful startup read_devno=0202 write_devno= 203 was detected rc=-5
please check your configuration parameters,cables & connection to the network.
debug: lcs: new level 0
lcs_fix_multicast_list failed to add multicast entry e0000001 multicast address table possibly full.
s390_do_machine_check : starting ...
crw_info : looking for CRWs ...
crw_info : CRW reports slct=0, oflw=0, chn=0, rsc=B, anc=0, erc=0, rsid=0
s390_do_machine_check : done
mach_handler : wakeup ...
do_crw_pending : starting ...
do_crw_pending : source is channel subsystem
do_crw_pending : done
mach_handler : nothing to do, sleeping
mach_handler : waiting for wakeup
Thanks
Ramki
Bookmarks