Problems starting Slackware after new install
I have completed the install of Slackware 10.0 in an LPAR on our mainframe. The install seemed to complete without any problems, but my new Slack/390 will not IPL. The LPAR goes into disabled wait status. Any ideas why my boot information is not being found? Thanks, Russ -- 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
Re: Problems starting Slackware after new install
>>> On Wed, Mar 28, 2007 at 5:24 PM, in message <[EMAIL PROTECTED]>, "Jones, Russell" <[EMAIL PROTECTED]> wrote: > I have completed the install of Slackware 10.0 in an LPAR on our > mainframe. The install seemed to complete without any problems, but my > new Slack/390 will not IPL. The LPAR goes into disabled wait status. Any > ideas why my boot information is not being found? This is due to a bug/undocumented requirement in Slack/390 10.0. If you didn't select the s390-tools package (in the K series) to be installed, this is what happens. You can re-run the install and make sure it includes that package. I would recommend, however, that you use what's in Slack390-current on the download server. More up to date, etc. Just be aware that there's another lack in the both installers. The network information you supply during the install doesn't get propagated to the system being installed. You'll need to enter that information manually, later. Getting time to fix that has been what's holding up renaming -current to -10.1. :( I was going to respond to your prior note about the installing seeming to hang after "finding" the initrd. What happened to get you past that? Mark Post -- 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
Re: Problems starting Slackware after new install
That sounds like what my problem is. I did not install the "K" set. Are there any other sets that must be installed? *** So, is it correct that when I IPL Slack/390 after the install, it will not be accessible from the network, and will have to change the network settings from the HMC? *** I ended up giving up on the CD and IPLing from tape. Thanks, Russ Jones -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Wednesday, March 28, 2007 4:34 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Problems starting Slackware after new install >>> On Wed, Mar 28, 2007 at 5:24 PM, in message <[EMAIL PROTECTED]> , "Jones, Russell" <[EMAIL PROTECTED]> wrote: > I have completed the install of Slackware 10.0 in an LPAR on our > mainframe. The install seemed to complete without any problems, but my > new Slack/390 will not IPL. The LPAR goes into disabled wait status. Any > ideas why my boot information is not being found? This is due to a bug/undocumented requirement in Slack/390 10.0. If you didn't select the s390-tools package (in the K series) to be installed, this is what happens. You can re-run the install and make sure it includes that package. I would recommend, however, that you use what's in Slack390-current on the download server. More up to date, etc. Just be aware that there's another lack in the both installers. The network information you supply during the install doesn't get propagated to the system being installed. You'll need to enter that information manually, later. Getting time to fix that has been what's holding up renaming -current to -10.1. :( I was going to respond to your prior note about the installing seeming to hang after "finding" the initrd. What happened to get you past that? Mark Post -- 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
Re: Problems starting Slackware after new install
>>> On Thu, Mar 29, 2007 at 9:32 AM, in message <[EMAIL PROTECTED]>, "Jones, Russell" <[EMAIL PROTECTED]> wrote: > That sounds like what my problem is. I did not install the "K" set. Are > there any other sets that must be installed? Usually, A, part of AP, and N are all that is required. (I moved s390-tools into A). I personally also install L and K. > *** > So, is it correct that when I IPL Slack/390 after the install, it will > not be accessible from the network, and will have to change the network > settings from the HMC? > *** Essentially, you're looking at two commands: ifconfig ifname ipaddress netmask route add default gw ipaddress Then, you can SSH in from the outside and edit /etc/rc.d/rc.inet1.conf appropriately. Mark Post -- 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
Re: Problems starting Slackware after new install
I got farther this time. I completed the installation and IPLed from my DASD volume. It started to come up, but froze and went into a disabled wait after trying to start gmp. Starting gmp: /usr/sbin/gmp -m /dev/mouse -t ps2 gmp: oops() invoked from gmp.c(955) Failed on virtual console check: No such file or directory Bash-3.00# I don't need any mouse support for Slack/390, but the setup seemed to force me to choose a mouse driver. Do I need to reinstall and exclude the mouse package(s)? Is there any way to fix it without reinstalling everything? Russ -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Thursday, March 29, 2007 11:41 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Problems starting Slackware after new install >>> On Thu, Mar 29, 2007 at 9:32 AM, in message <[EMAIL PROTECTED]> , "Jones, Russell" <[EMAIL PROTECTED]> wrote: > That sounds like what my problem is. I did not install the "K" set. Are > there any other sets that must be installed? Usually, A, part of AP, and N are all that is required. (I moved s390-tools into A). I personally also install L and K. > *** > So, is it correct that when I IPL Slack/390 after the install, it will > not be accessible from the network, and will have to change the network > settings from the HMC? > *** Essentially, you're looking at two commands: ifconfig ifname ipaddress netmask route add default gw ipaddress Then, you can SSH in from the outside and edit /etc/rc.d/rc.inet1.conf appropriately. Mark Post -- 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
Re: Problems starting Slackware after new install
>>> On Thu, Mar 29, 2007 at 5:11 PM, in message <[EMAIL PROTECTED]>, "Jones, Russell" <[EMAIL PROTECTED]> wrote: > I got farther this time. I completed the installation and IPLed from my > DASD volume. It started to come up, but froze and went into a disabled > wait after trying to start gmp. Sigh. One more reason why I suggest people to go with 10.1. I ripped gpm out of that version. It doesn't always cause problems, but when it does, it's ugly. -snip- > Is there any way to fix it without reinstalling > everything? You should be able to IPL the starter system, but once you SSH in, instead of starting the install process, do an "insmod dasd_eckd_mod dasd=xxx" where xxx is the device number of the volume where your root file system is. Then, mount /dev/dasda? /mnt and chmod -x /mnt/etc/rc.d/rc.gpm If you then umount /mnt and re-IPL, you should be OK. If not, you'll need to follow the steps above to get the root file system mounted, then chroot /mnt, and then "removepkg gpm" followed by exit, umount, and a re-IPL. Mark Post -- 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
Re: Problems starting Slackware after new install
This time it died trying to start mysql. I wonder if I didn't get that package installed? I guess that I need to keep it from trying to start at IPL time for now. Can I do that from the starter system without running the setup? -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Thursday, March 29, 2007 5:25 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Problems starting Slackware after new install >>> On Thu, Mar 29, 2007 at 5:11 PM, in message <[EMAIL PROTECTED]> , "Jones, Russell" <[EMAIL PROTECTED]> wrote: > I got farther this time. I completed the installation and IPLed from my > DASD volume. It started to come up, but froze and went into a disabled > wait after trying to start gmp. Sigh. One more reason why I suggest people to go with 10.1. I ripped gpm out of that version. It doesn't always cause problems, but when it does, it's ugly. -snip- > Is there any way to fix it without reinstalling > everything? You should be able to IPL the starter system, but once you SSH in, instead of starting the install process, do an "insmod dasd_eckd_mod dasd=xxx" where xxx is the device number of the volume where your root file system is. Then, mount /dev/dasda? /mnt and chmod -x /mnt/etc/rc.d/rc.gpm If you then umount /mnt and re-IPL, you should be OK. If not, you'll need to follow the steps above to get the root file system mounted, then chroot /mnt, and then "removepkg gpm" followed by exit, umount, and a re-IPL. Mark Post -- 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
Re: Problems starting Slackware after new install
>>> On Fri, Mar 30, 2007 at 11:09 AM, in message <[EMAIL PROTECTED]>, "Jones, Russell" <[EMAIL PROTECTED]> wrote: > This time it died trying to start mysql. I wonder if I didn't get that > package installed? I guess that I need to keep it from trying to start > at IPL time for now. Can I do that from the starter system without > running the setup? The system wouldn't be trying to start it if you didn't install it. It also wouldn't be trying to start it unless you told it to during the services set up. Could you send me your console log off-list? I'm really curious as to why this is dying, since it works for me. Yes, you can turn this off by using the starter system. Just chmod -x /etc/rc.d/rc.mysql (relative to the mount point you have the root file system on). Mark Post -- 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
