Bug 122015

Sure. Boot with 'brokenmodules=sis5513 insmod=foo'.  
  
But I think the module should be fixed.  

That work around is probably the best we can do for now.

(In reply to comment #2)
> That work around is probably the best we can do for now.

Unfortunately this doesn't solve. I tried booting with brokenmodules=sis5513.
The sis5513 module doesn't get loaded and the generic ide module gets loaded
instead. But still /dev/hda and /dev/hdc don't get created and installation
aborts since the installation files (on /dev/hdc) cannot be found.
Any ideas? Should these device get automatically created after loading the
generic module?
Today I tried also with Scientific Linux 4.1 x64_86 which is based on kernel
2.6.9 and that one works fine. However it's not true that it doesn't use the
sis5513 driver. It just doesn't load it as a module but probably has it compiled
in the kernel (I get the same SIS5513 messages reported above except for the
last "SIS_IDE: probe ...fail..." line).

Can you provide lspci -s 00:02.5 -vv output from the working kernel?

It looks like it doesn't actually know your specific sis chipset in the sis5513
driver and that is what is causing the error.

Created attachment 53816 [details]
lspci -s 00:02.5 -vv output

More stats: Suse 9.1, Fedora Core 2,  Kubuntu 5.04 and ScientLinux 4.0 and 4.1 
all works all right. Suse 9.3 has same issue as 10.0 and 10.1. Fedora Core 4 
doesn't even load kernel (probably for a different issue).

Please include a full lspci as well btw, sorry I forgot to mention that in the
first place.

Created attachment 53819 [details]
lspci -vv output

Without the -vv please as well :-)

A lspci -n would be great!

Created attachment 53823 [details]
lspci -n output

Created attachment 53824 [details]
Add the 760 chipset to the sis driver

This should probably fix it. Are you able to build a kernel yourself?

(In reply to comment #11)
> Created an attachment (id=53824) [edit]
> Add the 760 chipset to the sis driver
> This should probably fix it. Are you able to build a kernel yourself?

Actually no. I'm able to build a patched kernel from a working system but here 
I don't even have another 64bit CPU to install Suse on and start with. And 
anyway I need to create a (patched) installation CD/DVD (at least the network 
install cd) in order to test the patched kernel on the new machine.

If you sent me the compiled (patched) module, would it be possible to use the 
current installation dvd and load the module from an usb memory stick?

I have the same problem. Mainboard is an Asus K8S-MX, SiS760GX chipset and SiS965L Southbridge. Setup cant find DVD anymore while booting up the setup. insmod ide-generic solves that but HDD on SATA isnt found though. Testet with Suse 10.0 64 bit and 32 bit and Suse 9.3. Newest Mandriva Kernel has solved that problem so Mandriva 2006 works fine (also SiS190 NIC is working under Mandriva... Kernel 2.6.14-RC1 has solved that too). Anyone please make a new driver module so I can load setup. Dont want to wait till march next year...

I think that this too can be related to bug #117541
(SiS chipset, ide problems)
Try if 10.0 beta3 is working for you too (It is the only version
that is working for me...)

This is a kernel bug fixed in 2.6.14-RC1 ... SiS190 NIC and SiS965L Southbridge SATA are not supported before. Someone please make a working driver to get installation work otherwise I cant install Suse 10. Kernel changelog from Mandriva kernel 2.6.12-12mdk:  Added sata_sil24 module, SiS182? minimal support, SiS190? driver, support of the IDE chipset of the SiS965L? boards. Kernel Patch here: http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc2/2.6.14-rc2-mm2/broken-out/sis5513-support-sis-965l.patch

Good digging, thanks! I've added the patch to the SL100 repo, so it should show up in the next release. It should be possible to dig the sl5513.ko out of that rpm and manually load it from a usb stick or similar to get the installation going.

Could you explain that? Where can I find this rpm?

It will go out via YOU like the other updates. But that can take a while, of course. I should have a built kernel here in a few hours, I will attach the updated sis5513.ko here so you can grab it.

One thing that you can try (I haven't verified if this works) is to enter the vendor and device ID in yast2 when it starts up and map it to sis5513 - in theory that should get you going right away.

Created attachment 56348 [details]
sis5513 for SL10.0 i386 default with 765l support

Try this module, I just generated it for SL10.0 i386 default kernel.

I need a 64 bit module I think

I've copied that module to an USB mass Storage device. It's the only file on that device but setup (64 and 32 Bit) says "No new Driver Updates found" after I've selected USB Stick as Update medium

Created attachment 56354 [details]
sis5513 for SL10.0 x86-64 default with 765l support

x86-64 module

Indeed you do, I have attached the SL10.0 x84-64 default module as well.

YOu need to load the module manually, it's not an update disk. So mount the stick and do an insmod /path/sis5513.ko

You did bunzip2 the file first, right?

bunziped that of course. Problem is I dont know where to mount the USB device and insmod the module when setup loads up. Tried boot options "mount /dev/sda insmod /dev/sda/sis5513_64.ko" but that doesnt worked.

You probably have to load usb-storage, sd, and the usb adapter driver and then mount /dev/sda first. If you have a floppy, that would be easier to use (just mount /dev/fd0 and insmod from there).

So "boot options" is the correct way to input "mount... insmod..."?! I've just loaded setup then the USB Storage is mounted by setup the normal way while booting up. Then setup says "No CD found. Going to manual setup" because of that bug. Now I'm there like before, storage device is found at "apply driver update" so it is mounted but I cant find a way to insmod the module from this device. No textmode no anything. Unfortunately I dont have a floppy. 

You should have a console on ctrl-alt-f2 after setup has started, do it from there. You can't mount/insmod with the boot options, you have to do it manually.

I'm now at the console but I cant mount/find the USB Device. Its a MP3 Player in USB Mass Storage mode and it seems to be mounted (the display shows "Do not disconnect"). I also see that from boot.msg. It should be sda... but /dev/sda is no dir and it cant be mounted or unmounted.

Ok, I've mounted sda at /media/floppy and can see sis5513_64.ko but "insmod /media/floppy/sis5513_64.ko" brings "insmod: error inserting 'sis5513_64.ko': -1 file exists"

OK my boot options are now "brokenmodules=sis5513 insmod=ide-generic" and insmod sis5513_64.ko make no errors. And now? How do I get back to Setup?

OK found that too... ctrl-alt-f7. Now I'm back at setup but the partitioner dont find my HDD... only sda USB Device.
Kernel messages after loading sis5513_64.ko are following:
sis5513: no version for "struct_module" found: kernel tainted.
sis5513: module not supported by Novell, setting U taint flag.
SIS5513: IDE controller at PCI slot 0000:00:02.5
    ACPI-0212: *** Warning: Device is not power manageable
SIS5513: chipset revision 1
SIS5513: not 100% native mode: will probe irqs later
SIS5513: SIS 965 IDE UDMA133 controller
SIS5513: port 0x01f already claimed by ide0
    ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:DMA
Probing IDE interface ide1...

Any ideas? Found another kernel patch: http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13/2.6.13-mm3/broken-out/sis5513-support-sis-965l.patch

I've tested the i386 module too but its the same thing. Nothing happens after Probing IDE interface ide1... Could you make new .ko from the other patch?

To use a new module, either make it a driver update disk by putting it as
  /linux/suse/x86_64-10.1/modules/foo.ko
on a disk or copy it to
  /foo.ko
which makes it a modules disk which can be used if you select the 'more modules' entry in the module loading dialog.

You may want to try 'manual=1' to prevent auto-loading of modules.

I don't if thats exactly what you mean but I renamed sis5513.ko (64 bit) to foo.ko and put that on a CD but setup doesn't recognize this CD as a module disk. Tried that with manual=1 and loaded ide-generic to access the CD device

Hm, ok, could be it accepts only floppy disks. :-(
I didn't actually mean you to rename it to 'foo', 'foo' is just a
placeholder for the module name.

In any case, go for the diver update variant, then. There's an 'apply driver update' menu item in linuxrc. It will accept CD-ROMs.
Note that 'x86_64' and '10.1' should be replaced with the real arch and
release you are testing with. ;-)

OK tried that. "Driver Update OK" but I get the same kernel messages I wrote 4 posts ago but without Probing IDE interface ide1... Still no HDD present

I was able to load the new sis5513. I had to load setup with manual=1, so sis5513 AND ide-generic both are not loaded because sis5513 cant be removed if loaded and ide-generic keeps sis5513 from loading correctly (I think). So loading of sis5513 brings up my DVD device on ide (like ide-generic did) but how do get the SATA HDD? Which modules I have to load to activate SATA support?

Used a USB Storage for that with /linux/suse/x86_64-10.0/modules/sis5513.ko and loaded usb storage module

Perhaps there's also missing a patch for sata_sis? I've loaded it but nothing happens... http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=f2c853bca542f5ac0b036377637192a74f2091c2

Modules that are relevant for your hardware are marked with a '*' in the
module loading menus.

If there are still no disks after all modules are loaded, then there might
still be a bug in this driver.

BTW, there's a simple shell running on console 9 all the time, in case you
need it for experiments.

No HDD is detected after loading all necessary modules. I've checked the kernel messages from the Mandriva 2006 Installation that works for the SIS965L Chipset and I made it that way Mandriva did (sis5513, later libata and sata_sis - after sata_sis the HDD is detected under Mandriva Linux) but it didnt worked. So I think problem is in sata_sis because nothing happens after loading it

Could you provide me the patched (two posts ago) sata_sis 64 Bit to test it?

I have the same problem, any news about the suport of the SATA HDs with SiS 965L ?

Not sure if this is related or should be in another but, but I am also seeing trouble with an Asus board and 10.1.  Actually, the problems started in one of the  update Kernels to 10.0, but vanilla 10.0 worked mostly okay.

Anyhow, for me it works to do at install time (not sure what happens on reboot yet):

 brokenmodules=sis5513 insmod=ide_generic

I've attached hwinfo from 10.0 with the drive working, and one from the install system without this work-around enabled.

Created attachment 70497 [details]
hwinfo from running SUSE 10.0

Created attachment 70498 [details]
hwinfo from default boot of beta 5

Created attachment 70499 [details]
dmidecode output from running 10.0

This bug hasn't seen any progress for more than a month now, what's the status?

What's up here? Jens is this bug still valid?

Closing due to inactivity.

If this is still valid on the 10.2 release, please reopen.

Reopening:

The bug is still valid in the 10.2 openSuSE release... installing on a IBM Lenovo ThinkCentre type 8873-79G with SiS5513 rev.2 the installation can not find any hard disk...

I've tryied with the "brokenmodules=sis5513 insmod=ide_generic" with no luck...

What happens if you pass only "brokenmodules=sis5513" but not the insmod part?  libata drivers should be able to take care of the device.

No response, closing old bug.