[opensuse] Installation disk detection problems
New machine: Asus M2N-VM mobo (NVIDIA GeForce 6100 chipset) 2 WD800JD 80G SATA2 PIONEER DVD-RW SATA SuSE 10.1 (10.3 on the way, but I wanted to test the box) This thing has 4 SATA slots on the mobo. Near as I can figure it the order (when looking in the box at the board looks like 2 3 1 4 by experimentation with cables and what the BIOS says. All drives are recognized by the BIOS. Here's the problems: Only with the DVD-RW in slot 1 can SuSE figure out that the installation media is present (c.f. http://en.opensuse.org/SDB:CD_not_found_problem) but it *is* an SATA drive, one which works fine for installation in the machine on which I am typing this email. With the DVD-RW in slot 1, Installation begins, but the installer says it can't find any hard drives. Kernel messages show ata2: SATA link down (SStatus 0) Install with "Safe Settings" didn't help. Google shows various people having similar issues, but seemingly with different motherboards. Not sure if there's a driver which needs to be loaded or what. Following url has decent-looking specs of this motherboard: http://www10.uk.shopping.com/xPF-ASUS-ASUS-M2N-VM-DH-mainboard-micro-ATX-nFo... Does SATA2 put me in trouble here? Thanks in advance. Michael -- Michael Fischer michael@visv.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hello Michael. Sounds similar to my issue with 10.1 - drive unrecognised. Same with 10.2 IIRC ASUS P5K motherboard has onboard Jmicron chip. I could not get 10.1 to install. As it happened Ubuntu (7.0.4??) installed fine and I was content for a while. When 10.3 openSuSE came out I tried again. Bingo - success. In my case it gets more interesting... I have four SATA drives, one system drive at 80 gig and three data drives in software RAID5 at 320 gig each. The only way I could get things to work - tried a lot of BIOS settings, too! - was to set the system drive to be on SATA port 4 (/dev/sdd) and then the magic happened. By the way, you may profit from upgrading the motherboard BIOS. Mine was 0302 and I had very strange CPU core temperature readings - 40 degrees idle, 60 degrees running gklxgears. Upgraded to the latest no-Beta BIOS (0704) and that problem has gone away. Mind you the drive setup is a bit different between 0302 and 0704. Also be warned - you cannot regress at least not from 0704 to 0302. Your mileage may vary :-) HTH, Denis At 12:13 PM 29/11/2007, Michael Fischer wrote:
New machine:
Asus M2N-VM mobo (NVIDIA GeForce 6100 chipset) 2 WD800JD 80G SATA2 PIONEER DVD-RW SATA
SuSE 10.1 (10.3 on the way, but I wanted to test the box)
This thing has 4 SATA slots on the mobo. Near as I can figure it the order (when looking in the box at the board looks like
2 3
1 4
by experimentation with cables and what the BIOS says.
All drives are recognized by the BIOS.
Here's the problems:
Only with the DVD-RW in slot 1 can SuSE figure out that the installation media is present (c.f. http://en.opensuse.org/SDB:CD_not_found_problem) but it *is* an SATA drive, one which works fine for installation in the machine on which I am typing this email.
With the DVD-RW in slot 1, Installation begins, but the installer says it can't find any hard drives.
Kernel messages show
ata2: SATA link down (SStatus 0)
Install with "Safe Settings" didn't help.
Google shows various people having similar issues, but seemingly with different motherboards. Not sure if there's a driver which needs to be loaded or what.
Following url has decent-looking specs of this motherboard:
http://www10.uk.shopping.com/xPF-ASUS-ASUS-M2N-VM-DH-mainboard-micro-ATX-nFo...
Does SATA2 put me in trouble here?
Thanks in advance.
Michael -- Michael Fischer michael@visv.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Nov 29, Denis Brown wrote:
Hello Michael.
Sounds similar to my issue with 10.1 - drive unrecognised. Same with 10.2 IIRC
ASUS P5K motherboard has onboard Jmicron chip. I could not get 10.1 to install. As it happened Ubuntu (7.0.4??) installed fine and I was content for a while.
How exatly does one figure that out? If it has the Jmicron thing?
When 10.3 openSuSE came out I tried again. Bingo - success.
Will be trying that soon.
In my case it gets more interesting... I have four SATA drives, one system drive at 80 gig and three data drives in software RAID5 at 320 gig each.
The only way I could get things to work - tried a lot of BIOS settings, too! - was to set the system drive to be on SATA port 4 (/dev/sdd) and then the magic happened.
Hmm. I can't quite figure out the whole master-slave port thing here. I can only see what happens in the BIOS reporting as I move the connections around on the motherboard. Putting both HD's into what appeared to be "slave" ports got the BIOS to say "hey, I can't find a master HD", not surprisingly. Also not surprisingly, SuSE didn't find them either. Oh, FWIW, acpi=off made the DVD detection fail.. Thanks. Michael -- Michael Fischer michael@visv.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
在 2007-11-29四的 00:01 -0500，Michael Fischer写道：
On Thu, Nov 29, Denis Brown wrote:
Hello Michael.
Sounds similar to my issue with 10.1 - drive unrecognised. Same with 10.2 IIRC
ASUS P5K motherboard has onboard Jmicron chip. I could not get 10.1 to install. As it happened Ubuntu (7.0.4??) installed fine and I was content for a while.
How exatly does one figure that out? If it has the Jmicron thing?
If you are using JMicron chipset it will has a seperated sata controller beside the buildin motherboard one. Also you can look for the jmicron chip on the motherboard.
When 10.3 openSuSE came out I tried again. Bingo - success.
Will be trying that soon.
In my case it gets more interesting... I have four SATA drives, one system drive at 80 gig and three data drives in software RAID5 at 320 gig each.
The only way I could get things to work - tried a lot of BIOS settings, too! - was to set the system drive to be on SATA port 4 (/dev/sdd) and then the magic happened.
Hmm. I can't quite figure out the whole master-slave port thing here. I can only see what happens in the BIOS reporting as I move the connections around on the motherboard. Putting both HD's into what appeared to be "slave" ports got the BIOS to say "hey, I can't find a master HD", not surprisingly. Also not surprisingly, SuSE didn't find them either.
Oh, FWIW, acpi=off made the DVD detection fail..
Thanks.
Michael -- Michael Fischer michael@visv.net
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Michael Fischer wrote:
Hmm. I can't quite figure out the whole master-slave port thing here. I can only see what happens in the BIOS reporting as I move the connections around on the motherboard. Putting both HD's into what appeared to be "slave" ports got the BIOS to say "hey, I can't find a master HD", not surprisingly. Also not surprisingly, SuSE didn't find them either. Master/Slave was an obsession of the IDE protocol: There you need to set a jumper on each hard disk so that every IDE cable only has one master (and one slave), or CS (cable select) both. Sata does not need this.
Kind regards Philippe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 11/28/2007 Philippe Landau wrote:
Michael Fischer wrote:
Hmm. I can't quite figure out the whole master-slave port thing here. I can only see what happens in the BIOS reporting as I move the connections around on the motherboard. Putting both HD's into what appeared to be "slave" ports got the BIOS to say "hey, I can't find a master HD", not surprisingly. Also not surprisingly, SuSE didn't find them either. Master/Slave was an obsession of the IDE protocol: There you need to set a jumper on each hard disk so that every IDE cable only has one master (and one slave), or CS (cable select) both. Sata does not need this.
Kind regards Philippe
My configuration is probably a bit different than most. I have three hard drives, each loaded with a different OS. Two are SATA drives and one is an IDE. All three are "master". I don't think SATA has such a thing as a "slave" port, unless its a raid thing. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Philippe Landau wrote:
Michael Fischer wrote:
Hmm. I can't quite figure out the whole master-slave port thing here. I can only see what happens in the BIOS reporting as I move the connections around on the motherboard. Putting both HD's into what appeared to be "slave" ports got the BIOS to say "hey, I can't find a master HD", not surprisingly. Also not surprisingly, SuSE didn't find them either.
Master/Slave was an obsession of the IDE protocol: There you need to set a jumper on each hard disk so that every IDE cable only has one master (and one slave), or CS (cable select) both. Sata does not need this.
Kind regards Philippe
Those master and slave jumpers are ancient. For many years, the selection is determined by the cable. If you use the end connector, the drive is the master. If the middle connector, it's the slave. -- Use OpenOffice.org <http://www.openoffice.org> -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 James Knott wrote:
Philippe Landau wrote:
Michael Fischer wrote:
<snip>
Master/Slave was an obsession of the IDE protocol: There you need to set a jumper on each hard disk so that every IDE cable only has one master (and one slave), or CS (cable select) both. Sata does not need this.
Kind regards Philippe
Those master and slave jumpers are ancient. For many years, the selection is determined by the cable. If you use the end connector, the drive is the master. If the middle connector, it's the slave.
Unfortunately, in my experience cable detection tended to be somewhat unreliable ... it may have improved since on newer drives... but has given me much grief in the past.... - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHTvvzasN0sSnLmgIRAi+6AKDVasps7J/ZtsBtnrYLNmk7HHoMgQCdE/Yl LQFPfpuf61Cd0lCcGzHaPAM= =fl9+ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
James Knott wrote:
Philippe Landau wrote:
Master/Slave was an obsession of the IDE protocol: There you need to set a jumper on each hard disk so that every IDE cable only has one master (and one slave), or CS (cable select) both. Sata does not need this. Those master and slave jumpers are ancient. For many years, the selection is determined by the cable. If you use the end connector, the drive is the master. If the middle connector, it's the slave. This is not true. Of course you can use CSEL but you still need to set the jumpers correctly. Also CSEL does not work with old IDE cables. http://www.pcguide.com/ref/hdd/if/ide/conf_CS.htm So if you want to be sure, just set the jumpers to master/slave.
G T Smith wrote:
Unfortunately, in my experience cable detection tended to be somewhat unreliable ... it may have improved since on newer drives... but has given me much grief in the past.... CSEL was a good idea badly implemented and then overtaken by Sata.
Kind regards Philippe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Michael Fischer wrote:
On Thu, Nov 29, Denis Brown wrote:
ASUS P5K motherboard has onboard Jmicron chip. I could not get 10.1 to install. As it happened Ubuntu (7.0.4??) installed fine and I was content for a while.
How exatly does one figure that out? If it has the Jmicron thing? I run in problems with SuSE 10.2 and the ASUS P5K motherboard. Here my notes I made at that time how I got it running:
--------------------------------------------------------------------------- Install notes for OpenSuSE 10.2 on a PC with Asus P5B / P5K / P5K-E board. --------------------------------------------------------------------------- Possible problem with "Install-CD not found". Load the BIOS, pressing DEL just after power it on. Somewhere in the BIOS setup there should be an option for the JMicron drive controller("Onboard Devices" in the P5B BIOS menu). Set it to AHCI mode. Save and exit with F10. Re-start the installation process adding in the first boot menu the boot option: insmod=ide-generic insmod=pata_jmicron As of the JMicron chip: there should be an entry in the BIOS. Rgds, Stephan. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Nov 29, Stephan Hegel wrote:
Michael Fischer wrote:
On Thu, Nov 29, Denis Brown wrote:
ASUS P5K motherboard has onboard Jmicron chip. I could not get 10.1 to install. As it happened Ubuntu (7.0.4??) installed fine and I was content for a while.
How exatly does one figure that out? If it has the Jmicron thing? I run in problems with SuSE 10.2 and the ASUS P5K motherboard. Here my notes I made at that time how I got it running:
--------------------------------------------------------------------------- Install notes for OpenSuSE 10.2 on a PC with Asus P5B / P5K / P5K-E board. --------------------------------------------------------------------------- Possible problem with "Install-CD not found".
Load the BIOS, pressing DEL just after power it on. Somewhere in the BIOS setup there should be an option for the JMicron drive controller("Onboard Devices" in the P5B BIOS menu). Set it to AHCI mode. Save and exit with F10.
Re-start the installation process adding in the first boot menu the boot option: insmod=ide-generic insmod=pata_jmicron
As of the JMicron chip: there should be an entry in the BIOS.
Yes, that's the thing from the opensuse Wiki (CD not found). However, in my case, its a different motherboard, and the recommended simple solution (use an SATA DVD drive) applies. The drives in question are DVD - Pioneer SATA HD - WD SATA2 HD - WD SATA2 Michael, who is puzzled and will try burning and installing the 10.3 image tonight... -- Michael Fischer michael@visv.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 11:33 PM 29/11/2007, Stephan Hegel wrote:
Michael Fischer wrote:
On Thu, Nov 29, Denis Brown wrote:
ASUS P5K motherboard has onboard Jmicron chip. I could not get 10.1 to install. As it happened Ubuntu (7.0.4??) installed fine and I was content for a while.
How exatly does one figure that out? If it has the Jmicron thing? I run in problems with SuSE 10.2 and the ASUS P5K motherboard. Here my notes I made at that time how I got it running:
--------------------------------------------------------------------------- Install notes for OpenSuSE 10.2 on a PC with Asus P5B / P5K / P5K-E board. --------------------------------------------------------------------------- Possible problem with "Install-CD not found".
Load the BIOS, pressing DEL just after power it on. Somewhere in the BIOS setup there should be an option for the JMicron drive controller("Onboard Devices" in the P5B BIOS menu). Set it to AHCI mode. Save and exit with F10.
Re-start the installation process adding in the first boot menu the boot option: insmod=ide-generic insmod=pata_jmicron
As of the JMicron chip: there should be an entry in the BIOS.
Rgds, Stephan.
Thank you very much. Stephan. That is most interesting and I will file the solution away for the future! Please note that the option for the running onboard devices (the Jmicron chip) in AHCI mode seems to be absent in the latest released version (0704) BIOS for the P5K board. It now shows only IDE. As part of troubleshooting system instability I updated the original BIOS (version 0302) and discovered the AHCI option was missing! Version 0704 of the BIOS does, however, fix a problem where glxgears apparently jumps the CPU core temperature dramatically. With version 0302 the temps went up 20 degrees Celcius! Why that should be I have no idea :-) Hope this helps, Denis -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, Nov 30, Denis Brown wrote:
Load the BIOS, pressing DEL just after power it on. Somewhere in the BIOS setup there should be an option for the JMicron drive controller("Onboard Devices" in the P5B BIOS menu). Set it to AHCI mode. Save and exit with F10.
Thank you very much. Stephan. That is most interesting and I will file the solution away for the future!
Please note that the option for the running onboard devices (the Jmicron chip) in AHCI mode seems to be absent in the latest released version (0704) BIOS for the P5K board. It now shows only IDE.
As part of troubleshooting system instability I updated the original BIOS (version 0302) and discovered the AHCI option was missing! Version 0704
Yes, my BIOS version also does not seem to have any options for playing with the Jmicron stuff. Michael -- Michael Fischer michael@visv.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Nov 29, Michael Fischer wrote:
On Thu, Nov 29, Denis Brown wrote:
Hello Michael.
Sounds similar to my issue with 10.1 - drive unrecognised. Same with 10.2 IIRC
ASUS P5K motherboard has onboard Jmicron chip. I could not get 10.1 to install. As it happened Ubuntu (7.0.4??) installed fine and I was content for a while.
How exatly does one figure that out? If it has the Jmicron thing?
Does hwinfo --bridge show the Jmircon vendor name/string? Michael -- Michael Fischer michael@visv.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (8)
-
Alex Lau -
Billie Walsh -
Denis Brown -
G T Smith -
James Knott -
Michael Fischer -
Philippe Landau -
Stephan Hegel