[Bug 343749] Re: LSI SAS 1078 not detected when installing

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 5 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=541615. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at

[Bug 343749] Re: LSI SAS 1078 not detected when installing

2015-12-28 Thread Gad Maor
I can confirm this issue has not been resolved yet in Ubuntu 14.04 LTS latest ISO. Tried the iommu=soft solution -> didn't work. Tried to load every kernel module that seemed even remotely connected to the issue via the BusyBox tty -> no joy :( This is a major issue, since it's hampering

[Bug 343749] Re: LSI SAS 1078 not detected when installing

2014-10-07 Thread André Scholz
Yes, this is still an issue with 14.04 server. I have the same problem. Here what dmesg | tail says: [ 201.820039] scsi 2:0:0:0: megasas: RESET cmd=12 retries=0 [ 201.820049] megasas: [ 0]waiting for 1 commands to complete [ 202.824087] megaraid_sas: FW detected to be in faultstate, restarting

[Bug 343749] Re: LSI SAS 1078 not detected when installing

2014-10-07 Thread André Scholz
Well, an addition: it seems to work with kernel parameter iommu=soft Thanks for that tipp, Jaume. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/343749 Title: LSI SAS 1078 not detected when

[Bug 343749] Re: LSI SAS 1078 not detected when installing

2011-01-06 Thread Jason Unrein
It looks like Jaume Sabater might be correct on his issue in post in #1. The problem he encountered appears to be a MSI problem. Some systems I've seen the past cause issues with adapters and so it must be disabled. Newer versions of the driver have the option to disable MSI (see

[Bug 343749] Re: LSI SAS 1078 not detected when installing

2010-05-04 Thread thehighhat
this is still an issue. for tyan S7025WAGM2NR (S7025) which has LSI 1068E chipset. if all drives (ssd,sata,sas,optical) are connected to the LSI controller, then the 10.04 installer cd cannot detect anything. this is with the 64 bit alternative cd. why are not _all_ kernel drivers

[Bug 343749] Re: LSI SAS 1078 not detected when installing

2010-03-15 Thread Jaume Sabater
Unfortunately, I cannot try with a newer distribution of Ubuntu, as it's a live database cluster. But I can confirm it's still happening with the newest revision of the kernel of Ubuntu 8.10. I am very sorry, but I am using PostgreSQL 8.3 in that cluster and newest Ubuntu version comes with

[Bug 343749] Re: LSI SAS 1078 not detected when installing

2010-03-13 Thread Jeremy Foshee
Hi Jaume, This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/lucid. If it remains an

[Bug 343749] Re: LSI SAS 1078 not detected when installing

2009-11-26 Thread Luc Stepniewski
I have the same problem, on a x3850 M2 (I think it's the same as the x3950 M2): When I do an intensive I/O like a dd if=/dev/vg/mydev of=/dev/null, I will get the same errors. I have tried on Fedora 12, which gives also the same error : Calgary: DMA error on CalIOC2 PHB 0x3 Calgary:

[Bug 343749] Re: LSI SAS 1078 not detected when installing

2009-11-26 Thread Bug Watch Updater
** Changed in: linux (Fedora) Status: Unknown = Confirmed -- LSI SAS 1078 not detected when installing https://bugs.launchpad.net/bugs/343749 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list

[Bug 343749] Re: LSI SAS 1078 not detected when installing

2009-03-26 Thread Jaume Sabater
Managed to sort out the problem by booting both the installer and the installed kernel 2.6.27-X with the parameter iommu=soft. iommu=off did not work. Attached you'll find a lspci. Hope it helps. I've seen the guys at Red Hat updated their kernel in Red Hat Enterprise 9 with a workaround for this