10.1 install fails with SATA drives?
I'm trying to install 10.1 code (actually, sled 10) on a machine with a pretty new intel system board and sata drive. However, the install gets finished with the first section (after partitioning drives and choosing software, etc ...) and then it goes into what I think is the first scheduled reboot. However, it appears that the drives did not get the boot loader installed, or something. If I just leave the cd #1 in (the installed does not say to take it out, it just says rebooting in x seconds) then the default action is to boot to hard disk ... this fails, with the message "press a key to reboot". If I arrow down on the menu and choose "installation" it just starts the install again. So, I guess I have a couple questions: 1)at this point in the install, am I supposed to remove the cd and boot from the hard disk, or, is the installation supposed to pick up where it left off after booting to the cd? And, why oh why does the installer not SAY whether to remove the cd? 2)Is this likely a driver issue with the sata disks? If so, is there a procedure for inserting the correct drivers during the install (I see the F5 "driver" menu option, but I'm not sure what to do with it)? Below is what the installer sees as the disk devices /dev/sda (dsik, dev 8:0-*:15) model: "maxtor 6y080M0 revision: "YAR5" Serial: "Y2PBCQQE" Driver: "sata_sil" Geometry: (logical): CHS 9964/255/63 Size: 160086528 sectors (76 GB) Suggestions appreciated ... Peter
On Sunday 27 August 2006 17:34, Peter Van Lone wrote:
1)at this point in the install, am I supposed to remove the cd and boot from the hard disk, or, is the installation supposed to pick up where it left off after booting to the cd? And, why oh why does the installer not SAY whether to remove the cd?
It is supposed to boot from the hard drive at that point. Even if the bios says to boot from the CD, it will detect the installed SUSE and, boot it if you keep your hands off. It does not say to remove the cd because it is not necessary, and it will be using it after it gets booted. Further, if it does fail you already have the cd in there to do recovery.
2)Is this likely a driver issue with the sata disks? If so, is there a procedure for inserting the correct drivers during the install (I see the F5 "driver" menu option, but I'm not sure what to do with it)?
Sata is pretty standard, and SuSE detects them just fine. You can always press F5 and insert a driver disk, if you have one, and if it has linux drivers on it, but this seems highly unlikely that you will have such. The drivers in question are for the controller, not specifically the disk. What install options did you choose when asked where to install the boot loader? Did you take all the defaults? Check the hardware compatibility list for your controller. Basically my experience is that its almost impossible to find a IDE or SATA drive that does NOT work with linux. -- _____________________________________ John Andersen
On 8/27/06, John Andersen <jsa@pen.homeip.net> wrote:
It does not say to remove the cd because it is not necessary, and it will be using it after it gets booted. Further, if it does fail you already have the cd in there to do recovery.
ok, thnx for the explanation
Sata is pretty standard, and SuSE detects them just fine. You can always press F5 and insert a driver disk, if you have one, and if it has linux drivers on it, but this seems highly unlikely that you will have such. The drivers in question are for the controller, not specifically the disk.
I have subsequently seen how the F5 option works, but you are right I don't have an updated disk, anyway
What install options did you choose when asked where to install the boot loader? Did you take all the defaults?
well I have run through this a bunch of times now, but basically always vanilla/defaults, with the only variations being the generic "safe install and no acpi settings" as well as different software choices.
the hardware compatibility list for your controller. Basically my experience is that its almost impossible to find a IDE or SATA drive that does NOT work with linux.
the system board is an Intel Desktop Board D101GGC -- the manual does not really say what the controller is, beyond that it is "serial ATA". It's a new board, I guess I would be shocked if it does not support linux. Peter
On Sunday 27 August 2006 17:59, Peter Van Lone wrote:
well I have run through this a bunch of times now, but basically always vanilla/defaults, with the only variations being the generic "safe install and no acpi settings" as well as different software choices.
The only one that I would be concerened about is where it wrote the grub boot loader, and also if the bios is set for this drive to be bootable.
the system board is an Intel Desktop Board D101GGC -- the manual does not really say what the controller is, beyond that it is "serial ATA".
It's a new board, I guess I would be shocked if it does not support linux.
Peter
Some hints here about a bios upgrade: http://www.intel.com/cd/channel/reseller/asmo-na/eng/products/linux/feature/... -- _____________________________________ John Andersen
On Sunday 27 August 2006 18:06, John Andersen wrote:
On Sunday 27 August 2006 17:59, Peter Van Lone wrote:
well I have run through this a bunch of times now, but basically always vanilla/defaults, with the only variations being the generic "safe install and no acpi settings" as well as different software choices.
The only one that I would be concerened about is where it wrote the grub boot loader, and also if the bios is set for this drive to be bootable.
the system board is an Intel Desktop Board D101GGC -- the manual does not really say what the controller is, beyond that it is "serial ATA".
It's a new board, I guess I would be shocked if it does not support linux.
Peter
Some hints here about a bios upgrade: http://www.intel.com/cd/channel/reseller/asmo-na/eng/products/linux/feature /index.htm
Interestingly, the google cache of the above page is more interesting that the current version: You will probably have to unwrap this: http://64.233.167.104/search?q=cache:eNgwTHum8F4J:www.intel.com/cd/channel/reseller/asmo-na/eng/227400.htm%3Fiid%3Dsearch%26+%22Intel+Desktop+Board%22+D101GGC+linux&hl=en&gl=us&ct=clnk&cd=2 -- _____________________________________ John Andersen
On 8/27/06, John Andersen <jsa@pen.homeip.net> wrote:
Interestingly, the google cache of the above page is more interesting that the current version:
You will probably have to unwrap this:
yes, that is interesting .. the only supported distro is mandriva 2006!! Plenty of other boards would have worked, but this one ... So, I guess what this means is that I would have to figure out the whole range of drivers that would be needed to install on this board. Probably best to just kick it, and get a different board? (glad it is not mine ... I'm doing this as a favor for a friend, and I told him to get a generic intel board that supports linux -- hopefully he can swap it out, if there is no hope) Peter
On 8/27/06, John Andersen <jsa@pen.homeip.net> wrote:
The only one that I would be concerened about is where it wrote the grub boot loader, and also if the bios is set for this drive to be bootable.
so, I suppose I could take the second disk out to simplify the thing a bit ... but really, it's just 2 sata disks on a system board connected sata controller. It's weird. And I guess checking bios boot settings, that's a good idea, I'll look. These are supposed to be "automagic" boards, but I'll see what I can find. thnx for taking a moment. Peter
On Sunday 27 August 2006 21:59, Peter Van Lone wrote:
It's a new board, I guess I would be shocked if it does not support linux.
I'm sure you know the question is if the Linux version you're installing supports the board. It's based on an ATI Radeon Xpress 200 Chipset. Could this be one of those proprietary vs. open driver modules issues? Carl
On 8/27/06, Carl Hartung <suselinux@cehartung.com> wrote:
I'm sure you know the question is if the Linux version you're installing supports the board. It's based on an ATI Radeon Xpress 200 Chipset. Could this be one of those proprietary vs. open driver modules issues?
:-) Yes, I am aware. I figured the "ATI Radeon Xpress 200 Chipset" would have to do with video, and not disk channel troubles. P
On Sunday 27 August 2006 22:41, Peter Van Lone wrote:
I figured the "ATI Radeon Xpress 200 Chipset" would have to do with video, and not disk channel troubles.
From: http://www.ati.com/products/radeonxpress200intel/index.html: "... The integrated Serial ATA controller facilitates high-speed data transfers for each of 4 ports and allows easier hard drive upgrades and expansion for new SATA optical storage drives. ..." I didn't check to see if the Linux driver is available there, but it might be. regards, Carl
On Sunday 27 August 2006 22:41, Peter Van Lone wrote:
I figured the "ATI Radeon Xpress 200 Chipset" would have to do with video, and not disk channel troubles.
From: http://www.ati.com/products/radeonxpress200intel/index.html:
"... The integrated Serial ATA controller facilitates high-speed data transfers for each of 4 ports and allows easier hard drive upgrades and expansion for new SATA optical storage drives. ..."
I didn't check to see if the Linux driver is available there, but it might be.
Addendum: Not there :-/ I like your first option... finding another all-in-one board that is already directly picked up during installation and supported by SUSE 'out of the box.' OTOH, if Mandriva supports that board, it may be possible to track down the module and/or it's installer and adapt it to SUSE. Good luck! Carl
On Sunday 27 August 2006 19:22, Carl Hartung wrote:
OTOH, if Mandriva supports that board, it may be possible to track down the module and/or it's installer and adapt it to SUSE.
Good luck!
Carl
But Carl... The drive worked well enough to install the system, and only froze up when grub went into its second stage. Its just as likely that some (perhaps wrong) driver is being loaded, and falling back to a generic driver would work. -- _____________________________________ John Andersen
On 06/08/27 19:49 (GMT-0800) John Andersen apparently typed:
The drive worked well enough to install the system, and only froze up when grub went into its second stage.
Its just as likely that some (perhaps wrong) driver is being loaded, and falling back to a generic driver would work.
Does the Suse live CD work? The Mandriva live CD? Ought to be clues there if they do. -- "Let us not become weary in doing good, for at the proper time we will reap a harvest if we do not give up." Galatians 6:9 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/
On Sunday 27 August 2006 19:54, Felix Miata wrote:
On 06/08/27 19:49 (GMT-0800) John Andersen apparently typed:
The drive worked well enough to install the system, and only froze up when grub went into its second stage.
Its just as likely that some (perhaps wrong) driver is being loaded, and falling back to a generic driver would work.
Does the Suse live CD work? The Mandriva live CD? Ought to be clues there if they do. -- "Let us not become weary in doing good, for at the proper time we will reap a harvest if we do not give up." Galatians 6:9 NIV
Do live CD's make any use of the hard drive? -- _____________________________________ John Andersen
On 8/27/06, John Andersen <jsa@pen.homeip.net> wrote:
But Carl... The drive worked well enough to install the system, and only froze up when grub went into its second stage.
but I would not even call it a "freeze up" .. the system just fails to boot an os after the first reboot. Or, it fails to recognize that there IS an os there, to boot.
Its just as likely that some (perhaps wrong) driver is being loaded, and falling back to a generic driver would work.
is there a relatively simple method for deciding what the troubled driver is, and then identifying the appropriate generic driver? Or -- perhaps it really is an object lesson is being sure about the "linux support" of a particular system board. My freind (hopefully) can exchange this for one that is more generally supported by the various novell distro flavors.... if we do go this way ... can I extropolate "NLD9" support to mean also SLED10/suse10.1 support? peter
On Monday 28 August 2006 00:18, Peter Van Lone wrote:
is there a relatively simple method for deciding what the troubled driver is, and then identifying the appropriate generic driver?
Boot the installation system and proceed as though you're going to reinstall. Let it probe the hardware and repeat your previous steps... *but* stop a step or two before the final confirmation dialog. At this point, the installation kernel has a rescue-like root shell running on tty2 or tty4 (ctl+alt+F2 or F4). You can mount devices, run diagnostics and explore the system by hand. The installer also sends kernel messages to tty10 (ctl+alt+f10) while the graphical installer is running, so check there for clues. I get the feeling I'm leaving out another valuable 'back door' into the installation system, so check the other ctl+alt+Fn combinations out while you're there. Another approach is to *abort back to* manual installation, which is text (ncurses) mode, and use it's menu-based kernel module load/unload/display capability. That might give you some insight into what the installation kernel is 'seeing'. BTW, 'aborting back to' the manual installation system is not the same as selecting it first from the initial menu. The graphical installer doesn't really probe the hardware until the installation is underway, meaning you want it to proceed with the graphical installer first and let it load whatever modules it wants... *then* fall back to check via the manual menu system. hth & regards, Carl
On Sunday 27 August 2006 23:49, John Andersen wrote:
On Sunday 27 August 2006 19:22, Carl Hartung wrote:
OTOH, if Mandriva supports that board, it may be possible to track down the module and/or it's installer and adapt it to SUSE.
Good luck!
Carl
But Carl...
But what?
The drive worked well enough to install the system, and only froze up when grub went into its second stage.
I never said the drive didn't work.
Its just as likely that some (perhaps wrong) driver is being loaded, and falling back to a generic driver would work.
You are confirming my assessment of the situation... incorrect driver. Carl
On Sunday 27 August 2006 22:41, Carl Hartung wrote:
You are confirming my assessment of the situation... incorrect driver.
Well I've heard of suse using one driver at configuration time and a different one at post-install boot up in the case of PCMCIA cards, but I've never heard of installing with one disk controller driver and then booting up with a different one. After all, if the install went well, the driver obviously worked. Why would they switch? -- _____________________________________ John Andersen
On Monday 28 August 2006 02:50, John Andersen wrote:
On Sunday 27 August 2006 22:41, Carl Hartung wrote:
You are confirming my assessment of the situation... incorrect driver.
Well I've heard of suse using one driver at configuration time and a different one at post-install boot up in the case of PCMCIA cards, but I've never heard of installing with one disk controller driver and then booting up with a different one.
After all, if the install went well, the driver obviously worked. Why would they switch?
Because the installation kernel is a completely different animal. It's job is to boot and initialize whatever hardware it happens to 'wake up' in then supply the necessary install/repair tools. It might use a generic driver that you don't want 'permanently' installed... not optimized? ... outdated? etc... The installer is obviously configuring an incorrect module. It depends on a lot of things... how accurately it detects the mainboard and/or chipset... but it could also be a legitimate bug, too. In any event, the next step after definitively identifying the hardware is determining what is the correct module... is it provided by SUSE directly or proprietary and obtained elsewhere, etc. regards, Carl
On 8/27/06, Carl Hartung <suselinux@cehartung.com> wrote:
I'm sure you know the question is if the Linux version you're installing supports the board. It's based on an ATI Radeon Xpress 200 Chipset. Could this be one of those proprietary vs. open driver modules issues?
so, since none of the intel boards indicate supporting Suse (any version) but several do support Novell Linux Desktop9 (And sp1, and sp2, listed seperately) -- do you suppose that I could assume then that these boards will work with the 10.x versions? Peter
On 8/27/06, John Andersen <jsa@pen.homeip.net> wrote:
Check the hardware compatibility list for your controller. Basically my experience is that its almost impossible to find a IDE or SATA drive that does NOT work with linux.
hmm ... the only linux drivers intel offers for this board are a firmware updater and audio drivers for Mandriva 2006: http://www.intel.com/design/motherbd/gc/gc_drive.htm but they do have something called an intel quick start for linux cd ... and it mentions suse: http://www.intel.com/cd/channel/reseller/asmo-na/eng/products/linux/feature/... Is it likely that this is a "controller driver issue" and that maybe I will find something newer in this "quick start" cd than what SLED has on it's install media? p
I'm trying to install 10.1 code (actually, sled 10) on a machine with a pretty new intel system board and sata drive. However, the install gets finished with the first section (after partitioning drives and choosing software, etc ...) and then it goes into what I think is the first scheduled reboot. However, it appears that the drives did not get the boot loader installed, or something.
If I just leave the cd #1 in (the installed does not say to take it out, it just says rebooting in x seconds) then the default action is to boot to hard disk ... this fails, with the message "press a key to reboot". If I arrow down on the menu and choose "installation" it just starts the install again.
So, I guess I have a couple questions:
1)at this point in the install, am I supposed to remove the cd and boot from the hard disk, or, is the installation supposed to pick up where it left off after booting to the cd? And, why oh why does the installer not SAY whether to remove the cd?
2)Is this likely a driver issue with the sata disks? If so, is there a procedure for inserting the correct drivers during the install (I see the F5 "driver" menu option, but I'm not sure what to do with it)?
Below is what the installer sees as the disk devices
/dev/sda (dsik, dev 8:0-*:15) model: "maxtor 6y080M0 revision: "YAR5" Serial: "Y2PBCQQE" Driver: "sata_sil" Geometry: (logical): CHS 9964/255/63 Size: 160086528 sectors (76 GB)
Suggestions appreciated ...
Peter I had the same problem. I went into BIOS and disabled SATA Native Mode until
On Sunday 27 August 2006 21:34, Peter Van Lone wrote: the installation was 100% complete and I had restarted several times. Something you could check for. Carl L
participants (5)
-
Carl Hartung -
Carl Luescher -
Felix Miata -
John Andersen -
Peter Van Lone