Daniel, Sorry, I forgot that Red Hat dynamically creates the device entries in /dev/ after you tell it what DASD devices you have. So, get your network up, telnet in, and start rhsetup, but once you get to the point where you see the DASD being activated (should show up on the HMC), break out of it, can continue from there.
Yes, I was talking about the "boot from tape" image. Mark -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 13, 2002 3:19 PM To: [EMAIL PROTECTED] Subject: Re: upgraded rh 7.2 kernel, lost ctc connection (no network conne ctivity) Hey Mark, are you talking about the installation "boot from tape" image or the one on that IPL's from dasd but lacks the network connectivity? There is no chandev stuff on the installation "boot from tape" image that I can see. And I do the insmod, but end up with no /dev/dasd* filesystems to mount. Trying the echo to /proc/dasd/devices reported that they were already there, but still, no /dev/dasd*. And insmod the DASD driver on the other image I IPL off of dasd doesn't make sense because I already have everything mounted on that image, just lack the network connectivity. My changes to /etc/chandev.conf were written, but rebooting doesn't change that the ctc driver is using protocol 0 instead of 3. What am I misunderstanding? ~ Daniel [EMAIL PROTECTED] wrote: >Daniel, > >Since you're using a 2.4 system, you have to set up the chandev stuff, and >_then_ insmod the DASD driver. Or, do a >echo -n "add device range=6B40-6B43 ">>/proc/dasd/devices >and that should work also. Note the trailing blank on the echo command. It >is significant. > >Mark Post > >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] >Sent: Thursday, June 13, 2002 1:02 PM >To: [EMAIL PROTECTED] >Subject: Re: upgraded rh 7.2 kernel, lost ctc connection (no network >connectivity) > > >My /etc/chandev.conf was > >ctc0,0x1370,0x1371 > >So I did an echo "ctc0,0x1370,0x1371,3" > /etc/chandev.conf >shutdown -r now... it comes back up still using proto: 0 :(. >cat /etc/chandev.conf confirmed that the ",3" really was there >I doubted it would do any different, but I shutdown -h now then reIPLed >the LPAR, still proto 0 (still all the same errors). >Any ideas why it's not picking up my change? locate chandev.conf found >nothing else, and I looked in various other places where I might have >specified ctc0,0x1370,0x1371 but couldn't find anything > > >Mark's idea was what I was trying first, IPL from the install tape to >get the network connectivity, mount root on /mnt, chroot to mount, then >mount the other dasd devices and "upgrade" to the older rpm's that I >could ftp to the system. > >#insmod dasd dasd=6B40-6B43 >#mount /dev/dasda1 /mnt >mount: you must specify the filesystem type >#mount -t ext2 /dev/dasda1 /mnt >mount special device /dev/dasda1 does not exist > >ls /dev/dasd* turned up nothing > >I remember reading something else earlier so I tried: >echo "add device range=6b40-6b43 ">>/proc/dasd/devices >It told me they were already there >echo "set device range=6b40-6b43 on">>/proc/dasd/devices >said they were set on > >still no dasd anything in /dev/ > >Ideas? Thanks, >~ Daniel > >[EMAIL PROTECTED] wrote: > > >>It looks like youre talking to a MVSish system on the other end of that >>CTC, by those vary commands youre using there. Linux's CTC driver has a >>specific z/OS / OS/390 mode for that, mode 3. In your chandev.conf file, >>change the ctc line from this: >>ctc0,0x1370,0x1371 >> >>to this: >>ctc0,0x1370,0x1371,0,3 >> >>and your driver loading message should now look like this: >>CTC driver Version 1.54 with chandev support initialized >>ctc0 read ch 1370 (irq 04fa) write ch 1371 (irq 04fb) proto 3 >> >>You will get much nicer behavior from your CTC then. >> >> >>Jay Brenneman >> >>z/OS System Build and Installation >>Dept. C90A 1A26/710 >> >>T/L: 295 - 7745 >>Extern: 845 - 435 - 7745 >>[EMAIL PROTECTED] >>
