[opensuse] Remote install/upgrade of SUSE (updated)
Hi, I asked about how to do this a few weeks ago. I got sent a useful HOWTO cheers. But I've run into a bit of trouble that makes little sense. I've several machines all 'white boxes' all kinds of motherboards etc. some of them are Intel P4 based and others AMD Athlon. If I go through the motions of getting it to install it's fine, once YaST has finished doing its' thing and reboots if it's an Intel based machine then fine it reboots and everything is fine. However if it's an AMD machine then it won't restart, doesn't give an error just hangs. No GRUB error or anything. I've been told that sometimes it doesn't quite install grub correctly so before I click reboot in YaST I ssh in again using another terminal create a mountpoint /x and mount the disks. I then manually install grub using: chroot /x grub root (hd0,1) setup (hd0,1) Which reports that grub is installed. However it makes no sense, I've tried blanking the MBR record and then installing GRUB but it makes no difference the machines always just die after POST. I've killed 4 machines now and have a 600 Mile round trip to go n fix them. I suppose it's just as well that this is not a commercial platform!! Can anyone explain what the deal is with this, If I install SUSE using a CD it always works so why is this any different and why would it matter that it's AMD? Confused. Matthew -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Remote install/upgrade of SUSE (updated)
On Tuesday 13 March 2007 12:31, Matthew Stringer wrote: Can anyone explain what the deal is with this, If I install SUSE using a CD it always works so why is this any different and why would it matter that it's AMD? Confused. Have you tried turning ACPI off? -- Kind regards, M Harris -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Remote install/upgrade of SUSE (updated)
Matthew Stringer wrote: However it makes no sense, I've tried blanking the MBR record and then installing GRUB but it makes no difference the machines always just die after POST. I've killed 4 machines now and have a 600 Mile round trip to go n fix them. I wonder if it is related to the change to load grub onto the disk instead of the mbr. There is a setting in /etc/sysconfig/bootloader, i.e. LOADER_LOCATION. I don't remember now what is default, but I changed mine to MBR. It might be affected by /etc/grub.conf, but I saw that problem when I installed on our office server, where it appeared to NOT install grub nor a generic master boot record. I also had an AMD processor. I assumed it was my raid1 drives, but perhaps not. I'm not sure if the grub command would care about the setting in /etc/sysconfig or just Yast bootloader module, but that is my take on it. -- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
