Mailinglist Archive: opensuse-amd64 (299 mails)

< Previous Next >
Re: [suse-amd64] Status of Serial ATA support [Virus checked US]
  • From: Rodrigo V Monteiro <Rodrigo.V.Monteiro@xxxxxxxxx>
  • Date: Mon, 12 Jan 2004 15:13:49 +0000 (UTC)
  • Message-id: <OFA2756B90.81F0BC35-ON83256E19.0050B86B-83256E19.0053A3DC@xxxxxxx>





Hello Pete,

Yes, I read your reply and found your machine a splendid one setup.
Mine setup involves a ATA133- 80GB disc layouted like this:

hda1 - Windows 2000 (just for games)
hda2 - /boot for Slackware
hda3 - /boot for Suse 9.0 AMD64
hda4 - extended like this:
hda5: Windows data volume
hda6: Linux Swap for both ones
hda7: / for Slackware
hda8: / for Suse

Just keeping boot partitions at the begining of the disc to play safe
with IDE issues.

I had Suse 8.2 installed before but I am not sure if I had problems
booting it with SK8N (I had similiar problems with an older K7 board). When
installing Suse 9-64bit I got no problems with the boot CD but the first
reboot would not work stopping after discs messages. I booted safe option
grom GRUB, added the 3 parameters to it (ide=nodma apm=no acpi=no) and
everything went fine. I took out ide=dma and got the regular boot, so I
need to isolate the apm and acpi yet. The setup is 2 days old so I haven't
time to play around with it. I do intend to buy next AMD64 Suse version
with new Kernel and SATA drivers (the 64-bit is not sold here yet so I had
to download it for awhile). Also I do believe Suse will provide them soon
since SK8N is the most popular board for Opteron/64-FX processor.

As it goes on the list, SATA chipset used in this board is still not
well supprted or designed. People advise to buy a well supported board for
SATA and RAID. Unfortunatelly there is no SATA drivers easily to be found
in Brazil to test it. It should be a year until it caches up.


If I can be of any help, just let me know.



(Embedded image moved to file:
pic00153.gif)

(Embedded image moved to file: O: +55 11 F: +55 11 EY/Comm:
pic00292.gif)Rodrigo De 3523-5494 3078-1105 4776668
Vincenzo Monteiro







"Pete Bradbury"
<pete.bradbury@stantonb To: "Rodrigo V Monteiro" <Rodrigo.V.Monteiro@xxxxxxxxx>
ury.org.uk> cc:
Subject: Re: [suse-amd64] Status of Serial ATA support [Virus checked US]
12/01/2004 12:36





Hi Rodrigo

Was yours a dual boot or a standalone?

I ask because I have a similar setup - perhaps you've read my reply to this
thread along the way?


----- Original Message -----
From: "Rodrigo V Monteiro" <Rodrigo.V.Monteiro@xxxxxxxxx>
To: <suse-amd64@xxxxxxxx>
Sent: Monday, January 12, 2004 11:14 AM
Subject: Re: [suse-amd64] Status of Serial ATA support [Virus checked US]







Hi Dave, not sure if it helps but when I installed Suse 8.2 and Suse
9.0 64-bit in my SK8N board with ATA133 I only was able to reboot it using
ide=nodma apm=off acpi=off parameters at boot line in GRUB. These
parameters are listed at Safe Boot menu option. This same problem happend
to me with an older board during install boot and I could proceed normally
using the safe boot option from the install menu.

I still have to trim down which of the 3 parameters I can exclude
from the boot line so to disable functions. ide=nodma should slow down
disc performance a bit but I would have to benchmark how much.

Hope that helps.

(Embedded image moved to file:
pic26299.gif)

(Embedded image moved to file: O: +55 11 F: +55 11
EY/Comm:
pic17035.gif)Rodrigo De 3523-5494 3078-1105
4776668
Vincenzo Monteiro







Andreas Jaeger

<aj@xxxxxxx> To:
<davereid@xxxxxxxxxxxxxxx>
cc:
<suse-amd64@xxxxxxxx>
12/01/2004 06:12 Subject: Re: [suse-amd64]
Status of Serial ATA support





"Dave Reid" <davereid@xxxxxxxxxxxxxxx> writes:

> I disabled the Serial ATA drive and installed a 60GIG standard ATA133
drive.
> I installed Windows on this drive to confirm all the hardware was working
> and it was. In went the SUSE 9.0 PRO for AMD 64 DVD I paid $200 for, it
> displayed the install menu, I selected INSTALL and it start to boot. It
then
> promptly seized up at exactly the same place it did before as below:
>
> Starting hardware detection
>>misc.1.3 read floppy - then nothing.

This so far was always a BIOS bug. So, please buy next time correctly
working hardware.

Workarounds:
- Add "idle=poll" to the linuxrc command line (where you choose the
boot options)
- Disable legacy USB support

Which of these two will help, depends on the exact problem and the
BIOS bug.

> [...]

Andreas
--
Andreas Jaeger, aj@xxxxxxx, http://www.suse.de/~aj
SuSE Linux AG, Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
(See attached file: attmnqoz.dat)
----------------------------------------------------------
The information contained in this communication is intended solely for the
use of the individual or entity to whom it is addressed and others
authorized to receive it. It may contain confidential or legally
privileged information. If you are not the intended recipient you are
hereby notified that any disclosure, copying, distribution or taking any
action in reliance on the contents of this information is strictly
prohibited and may be unlawful. If you have received this communication in
error, please notify us immediately by responding to this email and then
delete it from your system. Ernst & Young is neither liable for the proper
and complete transmission of the information contained in this
communication nor for any delay in its receipt.

Note: If you have received a delivery failure report, it may be due to the
change in the Ernst & Young e-mail domains from "eyi.com", "ey.bm", or
"ey.bs" to "ey.com". Could you please make the necessary amendment, if
required, and resend the message.




----------------------------------------------------------------------------

----


> --
> Check the List-Unsubscribe header to unsubscribe
> For additional commands, email: suse-amd64-help@xxxxxxxx


----------------------------------------------------------
The information contained in this communication is intended solely for the
use of the individual or entity to whom it is addressed and others
authorized to receive it. It may contain confidential or legally
privileged information. If you are not the intended recipient you are
hereby notified that any disclosure, copying, distribution or taking any
action in reliance on the contents of this information is strictly
prohibited and may be unlawful. If you have received this communication in
error, please notify us immediately by responding to this email and then
delete it from your system. Ernst & Young is neither liable for the proper
and complete transmission of the information contained in this
communication nor for any delay in its receipt.

Note: If you have received a delivery failure report, it may be due to the
change in the Ernst & Young e-mail domains from "eyi.com", "ey.bm", or
"ey.bs" to "ey.com". Could you please make the necessary amendment, if
required, and resend the message.
< Previous Next >
Follow Ups