May 2004 - openSUSE AMD64 - openSUSE Mailing Lists

Re: [suse-amd64] Suse9.1 still fails to install
by sean-lynch＠sean-lynch.com 21 May '04

21 May '04

Just Mandrake or redhat should do. When you set up the SuSE boot loader it may autodetect your other linux installs and any windows and set them all up for you. It is not hard to add them using Yast. You may be happy with that. At this point you should try it. You only need one bootloader, no matter how many different images, distros and OS's you want to boot to. It is hard to recall, but the last red Hat install I did had a reboot in the middle. That was RH 4.2 i think. It has been a while. I am probably wrong, but I think Corel Linux was one of the first to do away with the mid install re-boot. You can use a single bootloader to boot to many different images. They can share the same /boot directory and have different names, or you can just point to the different /boot directories from a single bootloader. I still use Lilo because I know it and have not taken the time to learn grub yet(I know, tsk tsk). Everyone says grub is better in every way than Lilo, so it should be able to do what Lilo does. Too bad it has to create yet another way of listing and numbering your drives and pertitions. Again, Good Luck, Seán On Fri, 21 May 2004 11:56:25 -0400 (EDT), michael12(a)mindspring.com wrote: > > I'll try, but I have quite a few different boot images. Will I need one floppy > disk per image? Also, neither Redhat nor Mandrake has ever required a reboot at > this stage. It's just insane... > > Michael

1 0

Re: [suse-amd64] Suse9.1 still fails to install
by michael12＠mindspring.com 21 May '04

21 May '04

I'll try, but I have quite a few different boot images. Will I need one floppy disk per image? Also, neither Redhat nor Mandrake has ever required a reboot at this stage. It's just insane... Michael -----Original Message----- From: sean-lynch(a)sean-lynch.com Sent: May 21, 2004 10:39 AM To: suse-amd64(a)suse.com Subject: Re: [suse-amd64] Suse9.1 still fails to install Oh! This is a problem. SuSE still does a reboot after installing the basic system. The reboot gets you off the dvd booted system and on to your newly installed system. Then there is more installation and setup after you do this re-boot. If you did not install a bootloader, you will not be able to boot your newly installed SuSE to finish the install. Historically I believe almost all Linux ditributions used this reboot half way through install. Here are two solutions to try A or B (please read both): A) 1)Boot to Mandrake. Make a mandrake boot floppy. confirm you can boot to Mandrake with the boot floppy. 2)Install SuSE. Install the bootloader to your harddrive (yes, overwriting the Mandrake boot loader, but don't worry you have a Mandrake boot floppy from point 1 above!). Completely install SuSE past the mid install re-boot, Sax X setup, post configuration. create a SuSE boot floppy now. Reboot again to make sure SuSE is perfectly installed. You might add Mandrake and any other OS's you have to the SuSE boot loader and quit here, or print out (or write down) the lines from Grub (or Lilo) config files for the SuSE boot. 3)Use your Mandrake boot floppy to boot to Mandrake. Edit your Mandrake Grub (or Lilo) config file to include SuSE. Update Grub (or Lilo) with these changes and re-install it to your hard drive. This overwrites your SuSE installed boot loader, but you get all your old Mandrake settings back, plus a new entry for SuSE. B) On the other hand you may not have to start completely over... You might be able to use the SuSE install DVD as a rescue disk to boot to an OS on the hard drive. Choose the partion you started your SuSE install to and boot to it. You might be able to pick up the installation where you left off, even without a boot loader installed. If this is the case, create a SuSE boot floppy as soon as you get a working system. Good Luck, Seï¿½n On Fri, 21 May 2004 08:48:23 -0500 (GMT-05:00), michael12(a)mindspring.com wrote: > > I tried that. It reset before I was able to set up the root password, printer, > XF86, etc... Basically, just after the RPM installs completed. When I tried > booting from the DVD again, the DVD started as if it was a new install. Is > there something else I'm supposed to do? I don't recall anything in the manual > saying "Your system will reset before you can finish configuring it". I don't > even have a root password, my XF86 hasn't been set up, etc... Neither Redhat > nor Mandrake work that way - why does Suse work that way? > > Thanks, > Michael > > -----Original Message----- > From: Andi Kleen <ak(a)suse.de> > Sent: May 21, 2004 3:44 AM > To: Michael White <michael12(a)mindspring.com> > Cc: suse-amd64(a)suse.com > Subject: Re: [suse-amd64] Suse9.1 still fails to install > > > My plan was to add an entry in my Mandrake bootloader for Suse. > > > > Well, this crashes too, but in a much worse way. I look down after all the > > RPMs have been installed, and when I look up again I see Yast starting up. > > Immediately after that, the system starts shutting down. No real indication > > as to why this is happening. I didn't see anything of any significance in > > SUSE always reboots once during the installation. If you had looked > you had seen a dialog box telling you that. > > This is also documented in the handbook. > > Just make it somehow boot again and then the installation will continue. > > -Andi > > > -- > Check the List-Unsubscribe header to unsubscribe > For additional commands, email: suse-amd64-help(a)suse.com -- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help(a)suse.com

1 0

Re: [suse-amd64] Suse9.1 still fails to install
by sean-lynch＠sean-lynch.com 21 May '04

21 May '04

Oh! This is a problem. SuSE still does a reboot after installing the basic system. The reboot gets you off the dvd booted system and on to your newly installed system. Then there is more installation and setup after you do this re-boot. If you did not install a bootloader, you will not be able to boot your newly installed SuSE to finish the install. Historically I believe almost all Linux ditributions used this reboot half way through install. Here are two solutions to try A or B (please read both): A) 1)Boot to Mandrake. Make a mandrake boot floppy. confirm you can boot to Mandrake with the boot floppy. 2)Install SuSE. Install the bootloader to your harddrive (yes, overwriting the Mandrake boot loader, but don't worry you have a Mandrake boot floppy from point 1 above!). Completely install SuSE past the mid install re-boot, Sax X setup, post configuration. create a SuSE boot floppy now. Reboot again to make sure SuSE is perfectly installed. You might add Mandrake and any other OS's you have to the SuSE boot loader and quit here, or print out (or write down) the lines from Grub (or Lilo) config files for the SuSE boot. 3)Use your Mandrake boot floppy to boot to Mandrake. Edit your Mandrake Grub (or Lilo) config file to include SuSE. Update Grub (or Lilo) with these changes and re-install it to your hard drive. This overwrites your SuSE installed boot loader, but you get all your old Mandrake settings back, plus a new entry for SuSE. B) On the other hand you may not have to start completely over... You might be able to use the SuSE install DVD as a rescue disk to boot to an OS on the hard drive. Choose the partion you started your SuSE install to and boot to it. You might be able to pick up the installation where you left off, even without a boot loader installed. If this is the case, create a SuSE boot floppy as soon as you get a working system. Good Luck, Seán On Fri, 21 May 2004 08:48:23 -0500 (GMT-05:00), michael12(a)mindspring.com wrote: > > I tried that. It reset before I was able to set up the root password, printer, > XF86, etc... Basically, just after the RPM installs completed. When I tried > booting from the DVD again, the DVD started as if it was a new install. Is > there something else I'm supposed to do? I don't recall anything in the manual > saying "Your system will reset before you can finish configuring it". I don't > even have a root password, my XF86 hasn't been set up, etc... Neither Redhat > nor Mandrake work that way - why does Suse work that way? > > Thanks, > Michael > > -----Original Message----- > From: Andi Kleen <ak(a)suse.de> > Sent: May 21, 2004 3:44 AM > To: Michael White <michael12(a)mindspring.com> > Cc: suse-amd64(a)suse.com > Subject: Re: [suse-amd64] Suse9.1 still fails to install > > > My plan was to add an entry in my Mandrake bootloader for Suse. > > > > Well, this crashes too, but in a much worse way. I look down after all the > > RPMs have been installed, and when I look up again I see Yast starting up. > > Immediately after that, the system starts shutting down. No real indication > > as to why this is happening. I didn't see anything of any significance in > > SUSE always reboots once during the installation. If you had looked > you had seen a dialog box telling you that. > > This is also documented in the handbook. > > Just make it somehow boot again and then the installation will continue. > > -Andi > > > -- > Check the List-Unsubscribe header to unsubscribe > For additional commands, email: suse-amd64-help(a)suse.com

1 0

Re: [suse-amd64] Suse9.1 still fails to install
by michael12＠mindspring.com 21 May '04

21 May '04

I tried that. It reset before I was able to set up the root password, printer, XF86, etc... Basically, just after the RPM installs completed. When I tried booting from the DVD again, the DVD started as if it was a new install. Is there something else I'm supposed to do? I don't recall anything in the manual saying "Your system will reset before you can finish configuring it". I don't even have a root password, my XF86 hasn't been set up, etc... Neither Redhat nor Mandrake work that way - why does Suse work that way? Thanks, Michael -----Original Message----- From: Andi Kleen <ak(a)suse.de> Sent: May 21, 2004 3:44 AM To: Michael White <michael12(a)mindspring.com> Cc: suse-amd64(a)suse.com Subject: Re: [suse-amd64] Suse9.1 still fails to install > My plan was to add an entry in my Mandrake bootloader for Suse. > > Well, this crashes too, but in a much worse way. I look down after all the > RPMs have been installed, and when I look up again I see Yast starting up. > Immediately after that, the system starts shutting down. No real indication > as to why this is happening. I didn't see anything of any significance in SUSE always reboots once during the installation. If you had looked you had seen a dialog box telling you that. This is also documented in the handbook. Just make it somehow boot again and then the installation will continue. -Andi

1 0

Clock problem on Suse 9.0
by Milan Gabor 21 May '04

21 May '04

Hi! I noticed lately, that system clock on my dual opteron system is going slower than real time. In one day clock goes wrong about 10 seconds :( What could cause this behaviour? FOr couple of months everything was OK. MIlan

1 0

Suse9.1 still fails to install
by Michael White 21 May '04

21 May '04

Hi All, I tried to install Suse9.1 again, this time skipping the bootloader install completely (I chose to not install a bootloader) rather than trying to install a bootloader onto a floppy disk (which fails - see my earlier email). My plan was to add an entry in my Mandrake bootloader for Suse. Well, this crashes too, but in a much worse way. I look down after all the RPMs have been installed, and when I look up again I see Yast starting up. Immediately after that, the system starts shutting down. No real indication as to why this is happening. I didn't see anything of any significance in the /var/log/ area of the install, but I'd be happy to send anything that was logged to the partition I was installing Suse on. Is anyone else seeing this? Again, my system is nothing special - Asus SK8N, latest BIOS, a single 80 GB SATA drive, an Initio SCSI card with two drives (which Suse doesn't recognize on startup), HP Laserjet 5 Printer. Mandrake 9.2 for AMD64 (what I'm currently running) had some glitches when installing it (I had to pull the SCSI card and unplug my printer). Are there any tricks I need to know about for Suse? Thanks in advance. -- Michael White "To protect people from the effects of folly is to fill the world with fools." -Herbert Spencer, 1891

2 1

How much ram, how many processors?
by Christian Hofmann 21 May '04

21 May '04

Hi, I am interested in buying SuSe 9.1 Pro (not SLES) for my firm. Maybe someone can answer me the following questions: How much Opteron (AMD64) processors will SuSe 9.1 Pro support? What is the maximum memory SuSe 9.1 will Support? When I have more than one Server, will I have to buy SuSe Linux Pro once again, or is it allowed to install it also on the other machine? I hope someone can answer this question, I found nothing about that on the homepage. Best regards, Christian

3 2

Re: [suse-amd64] Suse9.1 Failed Install on SK8N
by michael12＠mindspring.com 20 May '04

20 May '04

All, Thanks for the help. I may try that (although I have a number of images on my /boot drive - I'd hate to lose them). I was hoping to have the Suse boot info installed on a floppy disk, and I could just copy the info over from floppy to /boot without disturbing my current configuration. Does anyone know why the install program can't find /dev/fd0? Does Suse 9.1 have problems accessing /dev/fd0? Thanks again, Michael -----Original Message----- From: ï¿½rn Hansen <orn.hansen(a)swipnet.se> Sent: May 20, 2004 1:16 PM To: suse-amd64(a)suse.com Subject: Re: [suse-amd64] Suse9.1 Failed Install on SK8N torsdag 20 maj 2004 19:08 skrev sean-lynch(a)sean-lynch.com: > > 1) Before installing SuSE, create a mandrake boot floppy for your current > settings. > > 2) Install SuSE. This, of course overwrites the mandrake boot loader on > your hard drive. That is why you created the floppy in step 1. > > 3) After SuSE is installed, boot to mandrake from your floppy. Update the > mandrake boot loader by adding a new entry for SuSE, and write it to your > hard drive. This will overwrite the bootloader installed by SuSE in step 2, > but will give you back all you had before, and a new entry for SuSE. > > Seï¿½n I think something like the above, should be put in the User manual ... -- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help(a)suse.com

2 1

Some Problems
by Gernot Bauer 20 May '04

20 May '04

Hello everybody. My name is Gery and i just switched from Suse Linux 32-bit to 64-bit :) As I studied computer science a few years ago, I would like to share my experiences with Suse-x64 as I would like it to be an excellent distribution. I would like to start with the installation-problems I had, and - although I already mastered them - it would be very nice if others could comment my experiences. I bought a hp pavillon with a 149 GB ide-hd with one primary partition /dev/hda1 74 GB HPFS/NTFS and an ext-partition 74 GB with two smaller partitions /dev/hda5 72 GB HPFS/NTFS and /dev/hda6 2,5 GB W95 FAT32 I tried the automatic setup, but the chosen linux partitions were too small for me. So I used advanced setup and tried to modify the existing partitions. All 3 win-partitions were set to "Mountpoint /windows/C, D and E" (although not mounted). When I tried to resize /dev/hda1 (windows/C) I was told that this is NOT possible because it is mounted (which it wasn't). I could only resize it after "Edit" -> empty the field "Mountpoint" on all windows partitions. When i reinserted the mountpoints after resizing and started the whole process, I got an error message, that the partitions could not be re-partitioned... Only when I left the mountpoint-fields empty for the windows-partitions, it worked... I think this would have been a deathtrap for any newbies (sp?). Any chance to get this fixed for future Suse-distributions? Thank you, Gery P.S.: Is this the right place to post/verify bug-reports?

1 0

Re: [suse-amd64] Suse9.1 Failed Install on SK8N
by sean-lynch＠sean-lynch.com 20 May '04

20 May '04

On Thu, 20 May 2004 18:11:23 +0200, Örn Hansen wrote: > > Since you want to use the Mandrake boot loader, simply boot up Mandrake and > add a boot entry, and specify the SuSE partition/kernel. Should be simple > enough. > more detailed answer... 1) Before installing SuSE, create a mandrake boot floppy for your current settings. 2) Install SuSE. This, of course overwrites the mandrake boot loader on your hard drive. That is why you created the floppy in step 1. 3) After SuSE is installed, boot to mandrake from your floppy. Update the mandrake boot loader by adding a new entry for SuSE, and write it to your hard drive. This will overwrite the bootloader installed by SuSE in step 2, but will give you back all you had before, and a new entry for SuSE. Seán

2 1