Hello all!! We belive we had the same problem that is been described, and we came out of this with the spec of "CHANDEV" with the portname. Our system is working OK. The Lpar Params that worked for us, are as follows: >>>>>>>> root=/dev/ram0 ro ip=off ramdisk_size=9216 DASD=728-72F HOST=lxl010390.inf.spo.ncnb:eth0:10.216.205.56 NETWORK=10.216.0.0:255.255.0.0:10.216.255.255:10.216.1.1 DNS=10.216.200.3 SEARCHDNS=inf.spo.ncnb RPMSERVER=ftp://10.216.0.102/pub/linux/s390 QETH=qeth1,0x4c0,0x4c1,0x4c2 CHANDEV=add_parms,0x10,0x4c0,0x4ce,portname:OSAGIG3C <----- <<<<<<<<< Luís F. Fabio Napoles > ---------- Mensagem original ----------- > > De : redhat-s390-list-admin@redhat.com > Para : "'Wilson, Eric'" <Eric.Wilson@anheuser-busch.com>,"'redhat-s390-list@redhat.com'" <redhat-s390-list@redhat.com> > Cc : > Data : Mon, 1 Jul 2002 14:18:59 -0400 > Assunto : RE: [Redhat-s390-list] RH v 7.2 on s/390 LPAR install - LCS / eth failure. > > Eric, > > I came up with 914 based on the statement "There are also some cards where > the first address has to start on a boundary that is a multiple of four > (0,4,8,c)." The intent was that perhaps you could try getting the > 914/915/916 addresses assigned to your system so that you could see if that > worked better. > > Mark Post > > -----Original Message----- > From: Wilson, Eric [mailto:Eric.Wilson@anheuser-busch.com] > Sent: Monday, July 01, 2002 2:04 PM > To: 'redhat-s390-list@redhat.com' > Subject: RE: [Redhat-s390-list] RH v 7.2 on s/390 LPAR install - LCS / > eth failure. > > > Mark; > > Thanks for your quick reply. Unfortunately the values suggested did not > work, as > illustrated below. Can you tell me how you came to the values 914, 915, and > 916? My OSA is at 913. Using that as a starting point, and using your > example, I > get a different error message RE: the second example below. Have I missed > something? This is a 100 Mbit interface. Why would it state Gigabit? > > > Please enter any parameters you need to pass to the channel device layer. > This includes the I/O ports of your ctc, escon and lcs devices, > (e.g. "ctc0,0x600,0x601" will activate the ctc0 interface at I/O > ports 0x600,0x601): > qeth0,0x0914,0x0915,0x0916 > SIOCADDRT: No such device > > > > This includes the I/O ports of your ctc, escon and lcs devices, > (e.g. "ctc0,0x600,0x601" will activate the ctc0 interface at I/O > ports 0x600,0x601): > qeth0,0x0912,0x0913,0x0914 > chandev_probe unable to force gigabit_ethernet driver invalid device no > 0x0914 > given > SIOCADDRT: No such device > > > > Cheers; > > E! > > > Eric Wilson > IBM Certified Advanced Technical Expert > RedHat Certified Engineer > > Anheuser-Busch Companies, Inc. Voice: 314.589.7601 > One Busch Place Facsimile: 314.632.6901 > 1CC-8 email: > Eric.Wilson@Anheuser-Busch.com > St. Louis, MO Pager: > Eric.Wilson@PageBUD.com > > > > -----Original Message----- > From: Post, Mark K [mailto:mark.post@eds.com] > Sent: Friday, June 28, 2002 4:44 PM > To: 'Wilson, Eric'; 'redhat-s390-list@redhat.com' > Subject: RE: [Redhat-s390-list] RH v 7.2 on s/390 LPAR install - LCS > / > eth failure. > > Eric, > > It kind of looks like the problem is the parameters you're passing to the > chandev layer. You specify: > qeth0,0x0912,0x0913,0x0913,-1,4096 > > I see a number of problems here. The three device numbers have to be > different. There are also some cards where the first address has to start > on a boundary that is a multiple of four (0,4,8,c). > > Where you have that "-1" value is supposed to be a non-negative integer > indicating the amount of buffer storage to allocate. "0" says the driver > figures out the value. I would think that -1 is undefined. > > I also think the 4096 value for port number isn't going to work well, > either. > > Try this, just to get things going: > qeth0,0x0914,0x0915,0x0916 > > Mark Post > > -----Original Message----- > From: Wilson, Eric [mailto:Eric.Wilson@anheuser-busch.com] > Sent: Friday, June 28, 2002 9:48 AM > To: 'redhat-s390-list@redhat.com' > Subject: [Redhat-s390-list] RH v 7.2 on s/390 LPAR install - LCS / eth > failure. > > > Good Morning; > > As stated in the subject line, I'm attempting to install RH v7.2 on an > s/390. > The install kernel img boots fine, and seems to accept my parm file values, > except for the LCS. I can see the device in the kernel but can not load a > driver > for it. I have the latest OCO drivers from IBM. Still no joy. Have I got the > parameters wrong? > > Linux version 2.4.9-21BOOT (harald@s390.redhat.de) (gcc version 2.95.3 > 20010315 > (release)) #1 SMP Fri Jan 18 16:50:02 CET 2002 > We are running native > This machine has an IEEE fpu > On node 0 totalpages: 53248 > zone(0): 53248 pages. > zone(1): 0 pages. > zone(2): 0 pages. > Kernel command line: root=/dev/ram0 ro ip=off > HOST=llx1.stl.anheuser-busch.com:eth0:10.48.2.25 > LCS=0x912,0 <<<<<<---------***** > DASD=01ea-01ee > NETWORK=10.48.2.0:255.255.255.0:10.48.2.255:10.48.2.2 > DNS=170.100.205.18:170.100.205.16 > SEARCHDNS=stl.anheuser-busch.com > RPMSERVER=http://10.144.8.25/install/s390 > INSTALL=default > DZT=America/Chicago > ......... > Please enter any parameters you need to pass to the channel device layer. > This includes the I/O ports of your ctc, escon and lcs devices, > (e.g. "ctc0,0x600,0x601" will activate the ctc0 interface at I/O > ports 0x600,0x601): > > qeth0,0x0912,0x0913,0x0913,-1,4096 <<<<<<-------****** > chandev_add_force memory_usage_in_k is bad > SIOCADDRT: No such device > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use > Iface > 127.0.0.1 0.0.0.0 255.255.255.255 UH 0 0 0 lo > Starting portmap. > Loading DASD kernel module. This can take a while. > Starting telnetd and sshd to allow login over the network. > Please connect now to 10.48.2.25 and start 'loader' > from this shell. > # > > > cat /proc/chandev > chan_type key bitfield > ctc=0x1,escon=0x2,lcs=0x4,osad=0x8,qeth=0x10,claw=0x20 > *'s for cu/dev type/models indicate don't cares > cautious_auto_detect: on > persist = 0x00 > use_devno_names: off > Channels enabled for detection > chan cu cu dev dev max checksum use hw auto > recovery > type type model type model port_no. received stats type > ============================================================================ > = > 0x20 0x3088 0x61 * * 0 no no > not_operational,no_ > path,revalidate,device_gone > 0x08 0x3088 0x62 * * 0 no no > not_operational,no_ > path,revalidate,device_gone > 0x10 0x1731 0x05 0x1732 0x05 0 no no > not_operational,no_p > ath,revalidate,device_gone > 0x10 0x1731 0x01 0x1732 0x01 0 no no > not_operational,no_p > ath,revalidate,device_gone > 0x04 0x3088 0x60 * * 1 no no > not_operational,no_ > path,revalidate,device_gone > 0x06 0x3088 0x1f * * 15 no no > not_operational,no_ > path,revalidate,device_gone > 0x05 0x3088 0x08 * * 15 no no > not_operational,no_ > path,revalidate,device_gone > 0x04 0x3088 0x01 * * 15 no no > not_operational,no_ > path,revalidate,device_gone > channels detected > chan cu cu dev dev in > chandev > irq devno type type model type model pim chpids use > reg. > ============================================================================ > === > > 0x0bee 0x0912 0x04 0x3088 0x60 0x0000 0x00 0x80 0xfcffffffffffffff no > no > > 0x0bef 0x0913 0x04 0x3088 0x60 0x0000 0x00 0x80 0xfcffffffffffffff no > no > > 0x0bfb 0x091f 0x08 0x3088 0x62 0x0000 0x00 0x80 0xfcffffffffffffff no > no > > # > > > > > Cheers; > > E! > > > Eric Wilson > IBM Certified Advanced Technical Expert > RedHat Certified Engineer > > Anheuser-Busch Companies, Inc. Voice: 314.589.7601 > One Busch Place Facsimile: 314.632.6901 > 1CC-8 email: > Eric.Wilson@Anheuser-Busch.com > St. Louis, MO Pager: > Eric.Wilson@PageBUD.com > > > > > _______________________________________________ > Redhat-s390-list mailing list > Redhat-s390-list@redhat.com > https://listman.redhat.com/mailman/listinfo/redhat-s390-list > > _______________________________________________ > Redhat-s390-list mailing list > Redhat-s390-list@redhat.com > https://listman.redhat.com/mailman/listinfo/redhat-s390-list > > _______________________________________________ > Redhat-s390-list mailing list > Redhat-s390-list@redhat.com > https://listman.redhat.com/mailman/listinfo/redhat-s390-list > >
