MP3000 mainframe in an 512MB Lpar -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Hall, Ken (IDS ECCS) Sent: Tuesday, November 30, 2004 11:47 AM To: [EMAIL PROTECTED] Subject: Re: sles9 install
This sounds familiar. What platform are you running it on? > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Herczeg, Zoltan > Sent: Tuesday, November 30, 2004 11:44 AM > To: [EMAIL PROTECTED] > Subject: Re: [LINUX-390] sles9 install > > > During my particular installation the system did reboot itself > and this is when I found the problem of not having any network > connection. I will redo the installation one more time to make sure I > did not miss something. > Mark, thanks for the insmod dasd_mod command. I actually had > to use dasd_mod.ko in the > /lib/modules/2.6.5-7.97-s390/kernal/drivers/s390/block just in case > anyone is interested. > > Thanks > > Zoltan > > > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Hall, Ken (IDS ECCS) > Sent: Monday, November 29, 2004 9:17 AM > To: [EMAIL PROTECTED] > Subject: Re: sles9 install > > You shouldn't really have to do anything special if you use the > built-in install scripts and yast. > > The default install process seems to set nearly everything up > properly. > One thing it could do better is tell you when you need to reboot. > Once, I thought yast had just died, but it ended pending a reboot to > continue the install. When you come back up, you have to run a script > with a REALLY long path to continue. This seems a little pointless, > but it's really just a nit. > > There are only a couple of glitches still hanging around: > > 1) The CTC driver doesn't seem to initialize properly on boot. This > might be an artifact of Hercules, except I can manually start it > after. > It also occasionally reports errors. > > 2) Even when I manually activate the CTC using ipconfig and route, the > ipconfig display shows the wrong peer address. The SLES9 side is > 192.168.200.1, and the peer is 192.168.200.2. This is the same setup > I had for SLES8. After starting the interface, the ipconfig display > shows > 192.168.200.1 for both addresses, even though the link is working. I > also get some really strange messages on the console when IPCONFIG > runs, but again, that might be Hercules. > > 3) Postfix seems to have problems with it's config, and spits out a > boatload of error messages on startup. Some I was able to fix in the > config file, but there are still problems with it. > > 4) Numerous bogus error messages during boot. > > Unfortunately, I'm not home so I don't have detail on these items. If > anyone has ideas, I can post more later. I had to take the machine > down for a bit to swap hardware around, so I didn't get much time to > play with it this weekend. > > > > -----Original Message----- > > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] > Behalf Of > > Post, Mark K > > Sent: Friday, November 26, 2004 7:20 PM > > To: [EMAIL PROTECTED] > > Subject: Re: [LINUX-390] sles9 install > > > > > > You will need to insmod the DASD driver, with the > appropriate device > > numbers for your DASD units: > > insmod dasd_mod dasd=num1,num2,num3-num4 I haven't looked at the > > SLES9 install yet, so I don't know if dasd_mod will then > automatically > > > load dasd_eckd_mod or not. If not, then just > > insmod dasd_eckd_mod > > > > After that, you should be able to mount your file systems. > > > > > > Mark Post > > > > -----Original Message----- > > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On > Behalf Of > > Herczeg, Zoltan > > Sent: Friday, November 26, 2004 5:22 PM > > To: [EMAIL PROTECTED] > > Subject: sles9 install > > > > > > Thanks for the suggestions!., I was able to get sles9 > installation > > > done through yast. The system now reboots itself from dasd and it > > appears that all the networking information I entered during the > > install does not come up. I try to ping the ip address of the linux > > lpar and nothing. I cannot access this system through putty and to > > make matters worse any command I try to enter on the HMC > console for > > that lpar does nothing. So I had the idea that I would boot > the sles9 > > install, enter my network config then mount the previously created > > dasd /dev/dasda and see what might be wrong with the config files. > > So I boot the install stuff, enter the networking info > and telnet > > into this lpar. I then try to issue commands mkdir zoltan then > > mount -t ext2 /dev/dasda1 /zoltan and I get the message mount: > > /dev/dasda1 is not a valid block device. I think the > problem is that > > I have to associate a physical device address with > /dev/dasda1 but how > > > do I do that? I checked in all my Linux manuals and came up > blank. I > > am thinking this is a s390 type function only. > > All help is appreciated! > > > > Zoltan > > > > > -------------------------------------------------------- > > If you are not an intended recipient of this e-mail, please notify the > sender, delete it and do not read, act upon, print, disclose, copy, > retain or redistribute it. Click here for important additional terms > relating to this e-mail. http://www.ml.com/email_terms/ > -------------------------------------------------------- > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, send > email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or > visit http://www.marist.edu/htbin/wlvindex?LINUX-390 > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, send > email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or > visit http://www.marist.edu/htbin/wlvindex?LINUX-390 > > -------------------------------------------------------- If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -------------------------------------------------------- ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
