I've got the same problem with 10.3 Final and RC1 on the same motherboard. My hard disk is a Maxtor 6L100M0 SATA150. I'm using 10.2 for now until this can get fixed.

I've had the same problem.  All hardware works fine in 10.2.  But in 10.3 the defection of the SATA controller fails.  I don't get any error messages.  It just sits there for about 2 minutes "loading" the sata_sis driver.  I'm not the only one...

http://www.suseforums.net/index.php?showtopic=39625&view=getnewpost

Here's my hardware specs.

Board:     PC-Chips M871G
Chipsets:  SiS760GX
CPU:       AMD Sempron 2800+ x86_64
PATA HD:   WDC WD1200AB-22DYA0 driver=sis_ide
SATA HD:   Maxtor 6V200E0 driver=sata_sis
Video:     nVidia GeForce 6800 XE AGP driver=nvidia
LAN/WiFi:  SiS900 10/100 Ethernet Adapter driver=sis900
           D-Link AirPlus G DWL-G510 Wireless PCI Adapter(rev.B) driver=ath_pci

This is a correction of typos.  Sorry about that.  I've also changed some options as this isn't just limited to x86.

I've had the same problem.  All hardware works fine in 10.2.  But in 10.3 the
detection of the SATA controller fails.  I don't get any error messages.  It
just sits there for about 2 minutes "loading" the sata_sis driver.  I'm not the
only one...

http://www.suseforums.net/index.php?showtopic=39625

Created attachment 176921 [details]
Hardware List

This is a hardware list with much more specific details of my specs.  I saved it from the "Hardware Information" module in Yast.

I forgot to mention that I'm currently running openSUSE 10.2 which is what the hardware list was created from.  When I first installed 10.3 (on the PATA drive as where I put the OS) it wouldn't detect my SATA drive (which is where I put /home).  I couldn't get access to my data so I reinstalled 10.2.  I'll be sticking with 10.2 until this issue can be resolved.

(In reply to comment #5 from Nathaniel Dube)
> I forgot to mention that I'm currently running openSUSE 10.2 which is what the
> hardware list was created from.  When I first installed 10.3 (on the PATA drive
> as where I put the OS) it wouldn't detect my SATA drive (which is where I put
> /home).  I couldn't get access to my data so I reinstalled 10.2.  I'll be
> sticking with 10.2 until this issue can be resolved.
> 


Damn...I can't get openSUSE 10.2 to work on my computer. It's the video card's fault. (it worked before, how strange)

So no HW list yet.    Can anyone tell me how to create one without installing, please?

My rough specs:

CPU: Intel Celeron D 2.66Ghz
M. Board: ASUS P4S800DX (SiS 655FX N. Bridge, SiS 964 S. Bridge)
SATA HD: WD-something    driver : sata_sis
Video: ATI Radeon 9600 XT   driver: ati           
LAN:  SiS900 10/100 Ethernet Adapter     driver : sis900

I've the exactly same problem> My mobo is a Asus p4s800d. Is unbelievable how come  Novell released the Opensuse 10.3 with this bug, I hope they release some patch or wherever to correct this mistake. 

This was a upstream bug fixed recently and it was too late to make GM.  Passing the following kernel parameter should get you going.

  Options="libata.pata_dma=0"

It will be slow but should work.  After installation succeeds, please install KOTD and remove "libata.pata_dma=0" from kernel parameter.  It should work fine from that point.

  ftp://ftp.suse.com/pub/projects/kernel/kotd/

Please try the above workaround and report whether it works.  Thanks.

No it doesn't :(
It still hangs for a couple of minutes during the splash screen
no HDs detected

and same errors in Kernel Messages

Hmmm.. Can you please take a photo of the kernel messages using a digital camera and attach it here?  Thanks.

Before I take the photos, I took a look at the K. Msg. and saw this:

Unknown boot option 'libata.pata_dma=0' : ignoring

 I entered the option with out any quotes

Now what...

Sorry about that.  The option syntax is confusing and I got it confused again.  The parameter to use is...

  options="libata=pata_dma=1"

You need to type everything in the above line including options= and the double quotes.

Kernel will complain that it doesn't know about the option.  The parameter is for linuxrc after all.  You can verify that the option worked by "cat /sys/module/libata/parameters/pata_dma".

The option is accepted and your command returned the value 1, which means it worked, right?
Grrr...
BUT Still no HDs for me ...

And the kernel seemed to understand the option - no 'Unknown boot option' errors

Please post a picture of kernel messages during and after pata_sis probing.  Let's see what went wrong.  Thanks.

Here are the photos...
Sorry for the large shinny spot in the right, but i failed to find out how to switch off the flashlight
The photos have a very high resolution...if you can't see theh words, just zoom :)

Created attachment 178236 [details]
libata loaded

Created attachment 178237 [details]
errors...

Oh... I missed a path while converting SCR access function return values.  This bug is also present in mainline.  Gee.. I wonder how this went unnoticed during all the -mm, mainline and our testing phases. :-(

I'll submit a patch to fix it and update kernel CVS and see what we can do to make installation possible.

Thanks.

Isn't that there is going to be a livecd+installation version of openSUSE 10.3?
Well..since it's not yet released, integrate the bug fix into it then :)

I'm asking people around for solution.  Hopefully, we'll be able to come up with something.

(In reply to comment #20 from Tejun Heo)
> I'm asking people around for solution.  Hopefully, we'll be able to come up
> with something.
> 

What Novell/openSUSE community could do is, include a separate ISO with all latest patches/updates.  I can understand why there is a "freeze" on changes to the GM ISO.  openSUSE has the ability at the begging of installation to include an add-on disc.  Each time a patch/update, change or what ever comes out, it can be included in the update iso.  This will makes things very simple for people who need as many bugs patched from the start.

My only access to the internet is through an Atheros base wireless PCI card.  So on a fresh install I can't get access to my router until I install the madwifi drivers.  In which case I can't download any necessary patches/updates during installation.

I'm not asking Novell to include madwifi drivers.  That's not the point I'm trying to get at.  The point is, for what ever reasons, many of us are unable to do any kind of updates during a installation.  So it would be very usefull if people in my position could download an iso (you can call it a extra complimentary disc) that includes some of the latest patches/updates.  Especially useful when the updates includes a fix for a screwed up kernel that doesn't detect my hardware. ;-)

Right now I'm on 10.2, which is working great.  The only way I will be able to get 10.3 working is if I can get a fix or new kernel on a second disk I can use as a add-on during the 10.3 installation.  Ok, I'm ranting.  I'm sure you get the point I'm trying to make.

Here's my reasons for changing the Severity and Priority levels.  After trying every thing mentioned above as well as ideas from other forums, emails and news post nothing has worked.  So because this "bug" prevents me from even installing openSUSE 10.3 I'll either have to stick with 10.2 for the time being or upgrade my hardware.  It's not in my budget right now to get more compatible hardware.  So I'll be sticking with 10.2 and praying to the Novell gods for a updated ISO I can download to fix this "problem".

Created attachment 179146 [details]
sata_sis-scr-fix.patch

This is the proposed patch which will soon be committed to kernel tree.  For installation solution, please wait a bit more.  Thanks.

So..now what??????

Okay, it turns out libata ATAPI support needs some major update.  I'm working on it now.  After the update is done, I'll backport those to SL103 tree and issue driver update disk.

Thanks.

(In reply to comment #25 from Tejun Heo)
> Okay, it turns out libata ATAPI support needs some major update.  I'm working
> on it now.  After the update is done, I'll backport those to SL103 tree and
> issue driver update disk.
> 
> Thanks.
> 

Where can we expect to find this driver update disk?  I'm assuming maybe in http://download.opensuse.org/distribution/10.3/iso/torrent/ ?  When you say SL103 tree, are you referring to http://download.opensuse.org/distribution/10.3/repo/ ?  And does this include updated ISO's or just the repo alone?  An updated ISO would be nice, then we can re-download that and just have one disk.

I might recommend posting an update to http://news.opensuse.org/ that way every one is aware of the update.

I don't know but I'm pretty sure it will be very easy to spot when it comes out.

Has anyone heard any updates on this?? I purchased the retail version and cannot install it until this is solved. Its been almost two months. 

Sorry about lack of update.  It turned out libata ATAPI support and was hoping to include related updates to driver update.  Unfortunately, the issue is still not finalized but I guess this waited long enough.  I'll gather what I can now and initiate the process.  Thanks.

This is probably a duplicate of <a href="https://bugzilla.novell.com/show_bug.cgi?id=347160">347160</a> - the issue occurs for PATA hard drives as well.  I have a SATA-enabled motherboard (Asus K8N4-E, PATA controller is nForce2-based), but only use the PATA for my drives - didn't have a lot of money when I built the box ;)

Same problem, though.  Fails to find my hard drives.  Even when I manually load the kernel drivers and start the installation again, nothing.  Although it's worth noting that it does not load the kernel modules that the console output says it's loading, for hard drive I/O at least.

Screwed up my link - you got the point of it though.

Patch committed.  It seems we'll have to do with driver update disk for now (will be announced on opensuse page).  I'll keep looking for implementing more permanent solution - auto generation of iso image containing up-to-date kernel image.  Maybe I can pull it before SL110.  Resolving as FIXED.  Thanks.

Many thanks, Tejun. Will it be obvious where to find this patch?

Yes, it will and I'll ping all the related bugzilla entries too.  I still have a few more bugs to update and still have no idea how to make / release driver update disk so please give me one more week.  Thanks.

Quick Question on planned fix. How will I be able to apply the fix so I can update my 10.2 to 10.3. when I tried install it hangs at the very beginning since it cannot see the SATA drives? Will I have to completely reinstall everything or make a new iso disk. I have the Novell 10.3 retail dvd.

Thanks I am waitting for your final fix. 

Thanks for your continued support!

That's what driver update disk is supposed to fix.  I dunno how it exactly works but it basically loads updated modules before installation system starts so updated drivers can be used to access the hardware during installation.

Any word on the driver update disk?  I've been trying to keep an eye on the main site(s), but haven't seen anything.

Where is this fix at?  I am another one who has been hit hard by this bug.

*** Bug 347160 has been marked as a duplicate of this bug. ***

I see this bug has been re-opened. On my machine, here, the bug went away with the kernel update issued about 10 days ago. uname -a = Linux barrowhillfarm 2.6.22.16-0.2-default #1 SMP 2008/02/01 19:36:55 UTC x86_64 x86_64 x86_64 GNU/Linux

I'm going to be away from this machine for the next week, but let me know if you'd like any more info.

Bob

hi,

The big problem in this bug is for users who want to install openSUSE 10.3 not for users that have already the openSUSE 10.3, as for that, after a kernel update it works fine, but the problem is thata some people just can't install openSUSE because this driver error, and this bug was reported a long time ago.
Tejun Heo says about a "disk update driver"in october but nothing was released nor published in  news.opensuse.org

regards

There was yet another update and now the kernel has "libata.force" parameter to help other installation problem.  The re-opening was to get SWAMPID assigned for update disk release.  So, it will happen soon.  I apologize for all the delays.  The delays are mostly caused by me.  I was trying to get other issues resolved too and they just took too much time.  Thanks a lot.

Glad to know it will happen soon. If this helps 11.0 alpha1 and alpha2 installed on the same system and mother board with not hang during the installation startup. Its the same SIS controller etc on an the same ASUS motherboard.

This is a 32 bit motherboard. P4 3.4GHZ,  

Any word on said driver update disk? ;)

Yeap, finally.  There was some reluctance against releasing DUD for hardware enablement for openSUSE as it has never been done before and DUD can't be built automatically, so I worked on something which can be automated.  It's called kISO for kernel ISO and basically a mini-ISO with updated kernel and kernel package for it.  The following URL contains kISOs for i386 and x86_64 built with KOTD (kernel-of-the-day).

  http://htj.dyndns.org/export/kiso/

Documentation on how to use kISO is at

  http://htj.dyndns.org/export/kiso/SL103-kISO-doc.txt

This is still in the works.  These ISOs can be built by invoking single command and I'm trying to make this thing automated such that kISOs for kernel updates and KOTD are generated automatically so that this kind of bugs can be dealt with much quicker in the future.

Please report whether the kISOs do the job.

Thanks.

I finally managed to install Opensuse 10.3 in my ASUS P4S800D. I did just like the documentation in the kiso directed to do. I'm actually wrinting this in my installed Opensuse 10.3. Great distro. Thanks for this iso.

It's now generally agreed upon that we make kISO automatically generated for at least KOTD so there will be KIOSTD (kISO-of-the-day).  So, in the future, this kind of problem will be handled much more swiftly.  There's now also OBS project for build-suse-kiso script so you can roll your own kISO.

http://software.opensuse.org/search?baseproject=openSUSE%3A10.3&p=1&q=build-suse-kiso

Resolving as FIXED.  Thanks.

I also used the KISO and it worked. I did forget the part about libata. Since all my drives are working I'm not two worried unless thats what causes my system to not shutdown. Thats a known bug. I had a work around for it on my other system so I'll try it later. 

Only thing that would be nice is a pause in the KISO program to allow you to change cd's at the right time.

Thanks for all of your work on this.

Thank you. This solved my installation problems with 10.3.

I just tried this, and I am still having problems with getting 10.3 to find all my SATA drives.

I downloaded the KISO, and followed the instructions... boot the KISO CD (I have to use the noapic option on boot), swap it out for the installation CD after the patched kernel was loaded.  The initial installation screens come up, and all looks OK until I see the partitioning.  One of my SATA drives is still missing.  This is essentially the same behavior as without the patched kernel... except with a few less errors on boot.

Hardware config/layout:  Asus M2N-E motherboard with drives on PATA 1, PATA 2, SATA 1, SATA2, SATA 3.  SATA 4 is empty.  I also have a PCI RAID card with 2 SATA drives attached.

On boot, PATA1 and PATA2 are found.  SATA 1 and SATA 2 are found.  The drives on the RAID card are found.  SATA 3 on the motherboard is not found.

Is this more of the same problem?  Or another problem with similar symptoms?  What extra info can I provide?

Clayton, it looks like a similar but different problem because sata_sis is two ported controller.  The third one must be a different controller.  Can you please post /var/log/boot.msg and the result of 'lspci -nn' from the installation system?  It can be done by switching to command console (ctrl-alt-f9) after the installation system is fully loaded, mounting any accessible file system (a partition on disk, usb disk whatever) under /mnt and copying the results there and unmounting.

Thanks.

Created attachment 199673 [details]
boot.msg file

This is the boot.msg from a clean boot using the 10.3 kISO KOTD with noapic option.

Created attachment 199674 [details]
lspci -nn output

lspci -nn output from a clean boot of the 10.3 kIOS KOTD with noapic option

Okay, your isn't sata_sis.  It's sata_nv and the second controller is failing initialization.

  <4>sata_nv: probe of 0000:00:08.0 failed with error -16

-16 is EBUSY.  It indicates that one of the resources (probably ioport) the driver wants to use to drive the controller is already occupied by someone else.  Can you please open a separate bug report and attach the followings?

* Just attach boot.msg posted here once more for completeness.
* "lspci -nnvvv".  Let's see what's going on with PCI BARs.
* "cat /proc/ioports" and "cat /proc/iomem" to see who's occupying which.

I'm resolving this one as FIXED.  See you in the new bug report.

Thanks.

Sorry about the confusion on my part.

A new bug on sata_nv not detecting the second controller has been opened here: https://bugzilla.novell.com/show_bug.cgi?id=370906