slackware 9.1 with SATA

You are quite correct:

hdparm -t /dev/sda

sorry about that... (In winXP Pro again.. trying to do this from memory) hehe

my bad

bc

So bonecrusher do you know why I can`t see my sata disc though I use your sata.i kernel?????

Originally posted by qlaret So bonecrusher do you know why I can`t see my sata disc though I use your sata.i kernel?????

....

and his system: hello I`m trying to install slackware 9.1 I have Asus A7N8X Deluxe Gold (with Silicon 3112A controler) and WD800JD disc I made sata.i disk (Made for slack 9.0 install by Bonecrusher) and install 1 and 2 disk

I went back two pages and found this info in regards to what system you have. The silicon chipset should work, hmm sure you are using:

cfdisk /dev/sda

?

fdisk may not show it in the list.. not really sure on that one. (SCSI) You definitely need to specify it specifically, though! Otherwise fdisk reverts to the ide system. When you boot you may want to try:

noprobe=/dev/(your IDE disk that should be SATA) <--- only do this if one of those drives listed in that previous msg is suppose to be SATA and is coming up IDE. I doubt this is the problem though.

It is hard to give you help, though without more info. Like boot messages, etc.

bc

PS:
See these links also:
http://www.linuxquestions.org/questi...762#post257762
http://www.siimage.com/products/overview_sii3112.asp (bottom of page says it supports linux..?)
http://12.24.47.40/?cid=2&c=12&cpc=U...P4SveI6dt2WJi7 See the sata link on left side of web page....

These may not help that much, but wanted to let you know what I was basing my facts on when I said, 'Silicon works....' ... thats all.

Is there any possibility to save all this messages which are displaied when kernel is loading?

Here is my email msg from the mailing list. Thought it may be of some interest to ppl who have sata hardware. It is basically an update of the current SATA development in 2.4.28 and 2.6.7(8):

------ Begin Email ------


Serial ATA (SATA) for Linux
status report
July 8, 2004



This status report applies to the latest SATA driver release, found in
(not yet release) kernels 2.4.28 and 2.6.7.



Recent updates
==============
Recent libata changes have focused on updating the libata core to be
more flexible, and support newer SATA-II host controllers. These
changes aren't very visible, but they lay the groundwork for a more
ATA hardware interface that supports queueing.

Various bits of the core have been tweaked in association with the
following buzzwords: ATAPI, DMADIR, legacy TCQ, NCQ, hotplug, port
multiplier, jelly beans. Ok, that last one isn't part of any official
specification. But the others should be fun.


Hardware support
================


Intel ICH5, ICH5-R, ICH6
------------------------
Summary: No TCQ. Looks like a PATA controller, but with a few added,
non-standard SATA port controls. Hardware does not support hotplug.
"Coldplug" support is potentially feasible.

libata driver status: Production, but see issue #2, #3.
Recently work on issue #2 has improved the state of that issue.

drivers/ide driver status: Production, but see issue #1, #2.


Issue #1: Depending on BIOS settings, IDE driver may lock up computer
when probing drives.

Issue #2: Excessive interrupts are seen in some configurations.

Issue #3: "Enhanced mode" or "SATA-only mode" may need to be set in BIOS.



AHCI (Intel ICH6-R/ICH6-M currently)
------------------------------------
Summary: Per-device queues, full SATA control including hotplug
and PM.

libata driver status: "looks like ICH5" support available in ata_piix.
Preliminary driver with full AHCI support now exists, and is being
integrated into libata mainline.

Note1: AHCI specification is completely open.

Note2: To ease integration, AHCI on ICH6 will be deployed inside the
ata_piix driver.

Note3: SiS has AHCI on its roadmap. Hopefully others will follow.


Promise TX2/TX4/SX4
-------------------
Summary: Per-host queues on all controllers. Full SATA control
including hotplug and PM on all but one controller (SX4).

libata TX2/TX4 driver status: Production, but see issue #5.

libata SX4 driver status: Production, but see issue #6.


Issue #5: Some boards appear to have PATA as well as SATA ports. PATA
is not currently supported, and no plans have yet been made to rectify
this. Ideally drivers/ide would drive PATA, but if they are the same
PCI device, that would not be feasible.

Issue #6: The SX4 hardware is not fully utilized by the Linux kernel
driver. The SX4 hardware includes an on-board DIMM and hardware XOR
offload. Using the on-board DIMM as cache, and issuing each RAID
transaction once (instead of once for each disk), will result in
increased performance, but the driver doesn't do that yet. SX4 hardware
is very "RAID friendly", particularly RAID1/5. Users may wish to use
the Promise driver to fully utilize the hardware.


Silicon Image 3112/3114
-----------------------
Summary: No TCQ. Looks like a PATA controller, but with full SATA
control including hotplug and PM.

libata driver status: Beta.

drivers/ide driver status: Beta?


Silicon Image 3124
------------------
Soon, hopefully. Silicon Image has made documentation and sample
hardware available to me (jgarzik) for development. Some code exists
internally.


Broadcom/ServerWorks/Apple
--------------------------
Summary: Huge per-device queues, full SATA control including hotplug
and PM for the "Frodo4" and "Frodo8" boards. Apple K2 SATA, which also
uses this chipset, has all the feature of Frodo4/8 save the host DMA
queueing feature ("QDMA"). QDMA supports legacy TCQ, but not NCQ.

libata driver status: Beta, but no QDMA support yet.


VIA
---
Summary: No TCQ. Looks like a PATA controller, but with full SATA
control including hotplug and PM.

libata driver status: Beta.


NVIDIA
------
Summary: No TCQ. Looks like a PATA controller, but with full SATA
control including hotplug and PM.

libata driver status: Beta.


SiS 180
-------
Summary: No TCQ. Looks like a PATA controller, but with full SATA
control including hotplug and PM.

libata driver status: Beta


Vitesse 7174 / Intel 31244
--------------------------
Summary: NCQ and 64-bit DAC support possible, but not implemented.
Looks like a PATA controller, but with full SATA control including
hotplug and PM.

libata driver status: Beta


Marvell 88SX50[48]x
-------------------
Summary: Similar to ServerWorks "frodo": per-device queues, supports
legacy TCQ but not NCQ (I think??), full SATA control including hotplug
and PM.

libata driver status: in progress


HighPoint (HPT)
---------------
I've had no contact with the company. Someone poke them, and get
them to get me a card and docs

libata driver status: no driver planned at this point.


ADMA (including Pacific Digital Talon SATA)
-------------------------------------------
Summary: No control over SATA phy at all (no hotplug/PM). Has
per-device hardware queues, and supports legacy TCQ.

Docs are public (yay!)

libata driver status: none, but hopefully soon


3ware SATA RAID
---------------
Not suited for libata architecture. Separate SCSI driver exists.



Software support
================


Basic Serial ATA support
------------------------
The "ATA host state machine", the core of the entire driver, is
considered production-stable.

The error handling is _very_ simple, but at this stage that is an
advantage. Error handling code anywhere is inevitably both complex and
sorely under-tested. libata error handling is intentionally simple.
Positives: Easy to review and verify correctness. Never data
corruption. Negatives: if an error occurs, libata will simply send
the error back the block layer. There are limited retries by the block
layer, depending on the type of error, but there is never a bus reset.

Or in other words: "it's better to stop talking to the disk than
compound existing problems with further problems."

As Serial ATA matures, and host- and device-side errata become apparent,
the error handling will be slowly refined. I am planning to work with a
few (kind!) disk vendors, to obtain special drives/firmwares that allow
me to inject faults, and otherwise exercise error handling code.



Queueing support
----------------
Even though some SATA host controllers on the market already support
command queueing (a.k.a. "TCQ"), libata does not yet support it.

However, libata was designed from the ground-up to support queueing, so
I need only change a few lines of code, and write two functions, to
enable this behavior.

Queueing will be enabled in libata soon, but to do so requires a long
stretch of testing on a large variety of controllers and drives. This
is very time-intensive, and is the largest part of this task.


Tangent: Host-based queueing and Native Command Queueing

Queueing is the process of sending multiple commands to a single device,
without waiting for prior commands to finish. This increases
performance and reduces latency. There are three types of queueing in
the ATA world:

1) "legacy TCQ" -- some PATA devices support this. Just ignore it,
it's going away.

2) "host-based TCQ" -- the host controller supports a queue of drive
commands, whether or not the drive supports it.

3) "Native Command Queueing" -- both host and drive cooperate in the
queueing and execution of drive commands. This should provide the
highest performance and lowest latency of all three options.


#1 will be supported only where hardware handles all the details.
#2 will soon be supported by libata.
#3 will be supported by libata when hardware is available from drive
manufacturers.


Hotplug support
---------------
All SATA is hotplug.

libata does not support hotplug... yet.

The following SATA controllers will never support hotplug:
Intel ICH5, Intel ICH5-R, Intel ICH6 (non-AHCI), Pacific Digital Talon,
Promise SATA SX4.

These controllers do not export enough information about the SATA phy to
make it possible to support hotplug. In some cases, such as Intel
ICH5/ICH6, it is possible to support "coldplug" operation: the user
informs the OS driver he wishes to disconnect his SATA device, rather
than simply disconnecting it.


Power Management support
------------------------
Over and above the power management specified in the ATA/ATAPI
specification, one can aggressively control the power consumption of
SATA hosts, the SATA bus, and the SATA device.

Note: as discussed on some mailing lists, the aggressive power
management can be too aggressive, and park the heads too often
(resulting in shortened disk drive life). Careful attention must be
paid to balance.


SMART support
-------------
Soon. Requires the capability to directly submit ATA commands from
userspace to the low-level device, which must be added with care. The
smartmontools developers have committed to adding a new device type '-d
sata' to utilize this passthrough, once it is ready.


------- End Email -------

Thats it!


bc

Originally posted by qlaret Is there any possibility to save all this messages which are displaied when kernel is loading?

Are you able to boot the system to a prompt?

If so just do this:

bash# dmesg > /root/bootlog_2004-17-7

bash# tail -200 /var/log/messages > /root/syslog_200_2004-17-7

That should do it I think. If you aren't able to boot to a prompt, you'll just have to do the best you can by using [PG]{UP}/[DOWN] and writing it longhand (just the pertinent stuff --> e.g. > /dev/sda info and all that... (If your still not sure what I mean let me know and I will elaborate more....)

bc

I will try......

Originally posted by qlaret I will try......

umm? huh?
Did I miss something?



bc


.......

at first your msg read ' so i wait...' and that was the reply above. But now you changed it to 'I will try...'
So now I understand.. uhhh nevermind..... !!

Originally posted by bonecrusher Are you able to boot the system to a prompt? If so just do this: bash# dmesg > /root/bootlog_2004-17-7 bash# tail -200 /var/log/messages > /root/syslog_200_2004-17-7 That should do it I think. If you aren't able to boot to a prompt, you'll just have to do the best you can by using [PG]{UP}/[DOWN] and writing it longhand (just the pertinent stuff --> e.g. > /dev/sda info and all that... (If your still not sure what I mean let me know and I will elaborate more....) bc

ok I tried.... everything will by ok...but I tried to save all this messages in file at windows partition (because I wonna paste it in here) ... so i wrote just like You said
dmesg > /root/bootlog_2004-17-7
and then :
cp bootlog...... /dev/hde5 and now my windows can`t load <- so I think it was wrong )
so my next question is : how I can save this msgs to a file which I can next open in windows and copy inhere (I tried copy this file to a floppy but it don`t want to open in windows)

THANKS GOOD I HAVE SECOND PC )

Originally posted by qlaret I tried to use cfdisk but it send me message that: there is no drive (or something like that) and no... hd isn`t my cd-rom if I use fdisk -l i can see something like that /dev/hd1 ntfs (primary) /dev/hd2 extended /dev/hd3 boot (primary) /dev/hd4 swap (logical like the others) /dev/hd5 fat /dev/hd6 ex3 /dev/hd7 ntfs /dev/hd8 fat32 /dev/hd9 fat32

BTW what is this? I dont know what disk your using because you have 'hd#' not 'hde#' or 'a' or 'b' or whatever....

and also what partition would your linux partition be on? I see /dev/hd(6) -- i guess you meant ext3 but it is showing it as IDE drive it looks like not a SCSI.
hmm

bc

Originally posted by qlaret cp bootlog...... /dev/hde5 and now my windows can`t load <- so I think it was wrong ) so my next question is : how I can save this msgs to a file which I can next open in windows and copy inhere (I tried copy this file to a floppy but it don`t want to open in windows) THANKS GOOD I HAVE SECOND PC )

Yes, thank God. And also, why not just install linux on your second computer and compile your own kernel? If your not sure how then I understand... but that is how I originally got my sata system booted up for SLackware.

Anyway,

I am not sure why your Win system crapped out. Sure it wasn't an NTFS part you tried to write to? and if you want to copy to floppy you have to format the floppy for FAT (Not ext2 which is what it defaults to.) try this:

bash# mformat a:
bash# mcopy /path/to/file/dmesg-namehere  a:
bash# mcopy /path/to/file/syslog-namehere a:

Now then I think those are dosutil (mtools) command to do it.. but you may want to check the man pages.. (Once again I am in windows and can't check (I could google..but then again so could you )


OMG: Don't look now.. It's my 100th Post! Bahaaha

bc

thanks for everything .....

Is anyone able to install slackware 10 on a serial raid-0 . I setup the boot disks using bonecrushers sata.i and install.1 and 2 but when i fdisk -l it shows as 2 drives and when I try to open cfdisk it gives an error and will not start.
This is for hardware raid on sil 3112a controller. NF2 chipset.

Originally posted by nablis Is anyone able to install slackware 10 on a serial raid-0 . I setup the boot disks using bonecrushers sata.i and install.1 and 2 but when i fdisk -l it shows as 2 drives and when I try to open cfdisk it gives an error and will not start. This is for hardware raid on sil 3112a controller. NF2 chipset.

As far as I know you cannot use hardware RAID on linux.
I could be wrong about this, there may be a proprietary driver around someplace, but I wouldn't count on it. You may want to try software RAID, I dunno much other then that. Sorry.

bc

Originally posted by bonecrusher Here is a link to my compile of slackware installation kernel for sata hard drives (any supported): Here is the directory. Pick sata.i *** EDIT: I just changed this on 7-12-2004 - I have recompiled and this should now support everything sata. (It is also now a 2.4.26 kernel to match up with slack 10)

If your downloading the .torrent (For SATA ISO or just the boot disk) file go to above link. I just changed trackers on it:
See my webpage.

So if you have the older .torrent, it probably isn't working. (Unless someone is still seeding that one which I doubt.)

One more PostScript to that:

Amrit who hosts all the other ISO's for Slackware is now hosting (tracking) my torrent which I am in gratitude for....Everything remains the same link wise please see my web page for details. if you started downloading and have a partial ISO you will more then likely be able to continue, but you will have to download the new torrent and add the datadirectory you downloaded already to the new torrent. (I tried to change trackers between people downloading the ISO to avoid this as much as possible.) Anyway I apologize again for having to change this so much, but as you can see it only makes sense to have it tracked at the same place as the others. I just wish I would have been able to do this from the beginning!




The boot disk is also still there as in above quote.
EDIT:
Now the ISO is at an FTP site .. go to web address above for link.

bc