Hi,
It's been quite a while now and haven't seen anything about Linux
adding support for these new Intel controllers in RAID mode. Nothing
shows at all unless the controller is changed to AHCI mode. The
manufactures are typically selling their systems with that controller
in RAID mode having
:38 PM David F. wrote:
>
> Well, it's not straightforward. No direct calls, it must be somehow
> when kmod is used to load the module. The only difference I see in
> the udevadm output is the old system has attribute differences
> capability new==11, old==1, event_poll_msec new=2
the "hidden" attribute to 1 then it looks like
/proc/partitions won't list it (already "removable"attribute), but
udev doesn't seem to allow changing the attributes, only referencing
them. unless I'm missing something?
On Mon, Sep 30, 2019 at 5:13 PM David F. wrote:
>
> Thanks f
output, it's close to the same, the
message log (busybox) not much in there to say what's up. I even
tried the old .rules that were being used with the old udev version,
but made no difference.
On Mon, Sep 30, 2019 at 4:49 PM Randy Dunlap wrote:
>
> On 9/30/19 3:47 PM, David F. wrote:
Hi,
I want to find out why fd0 is being added to /proc/partitions and stop
that for my build. I've searched "/proc/partitions" and "partitions",
not finding anything that matters.
If udev is doing it, what function is it call so I can search on that?
TIA!!
Hi,
I was updating some tools such as udev, mdadm, lvm, and came across a
hang and messages about unable to read fd0 which wasn't occurring with
the old tools, but using same kernel. So I've found that in the old
version the /proc/partitions didn't have fd0 whereas now it does. But
both have
Answer: No nothing got broken except the driver itself.
On Fri, Jun 30, 2017 at 4:10 PM, David F. <df7...@gmail.com> wrote:
> Hi,
>
> I have a driver that reads data from a file that has worked from
> kernel 3.x up to 4.9.13. I haven't tried all the other 4.9's or 4.10,
>
Answer: No nothing got broken except the driver itself.
On Fri, Jun 30, 2017 at 4:10 PM, David F. wrote:
> Hi,
>
> I have a driver that reads data from a file that has worked from
> kernel 3.x up to 4.9.13. I haven't tried all the other 4.9's or 4.10,
> or 4.11.6 or earlier, but
Using up to and including 4.11.7 getting reports coming in of black
screens on new laptops (includes booting to console only). The
solution is to use kernel parameter acpi=off. The newer include Dell
Latitude 5289 and Lenovo e-560. (although searching Internet even
older system affected like
Using up to and including 4.11.7 getting reports coming in of black
screens on new laptops (includes booting to console only). The
solution is to use kernel parameter acpi=off. The newer include Dell
Latitude 5289 and Lenovo e-560. (although searching Internet even
older system affected like
Hi,
I have a driver that reads data from a file that has worked from
kernel 3.x up to 4.9.13. I haven't tried all the other 4.9's or 4.10,
or 4.11.6 or earlier, but in 4.11.7 it's now broken and an error is
returned. It's based on
Hi,
I have a driver that reads data from a file that has worked from
kernel 3.x up to 4.9.13. I haven't tried all the other 4.9's or 4.10,
or 4.11.6 or earlier, but in 4.11.7 it's now broken and an error is
returned. It's based on
Very possible it affects other devices attached, but all consumer
reports and test systems here all have NVME drives on m2 and when in
RAID mode. Listing PCI data linux will show Intel SATA controller
detected in RAID mode, but no drives detected, all you get is your
/dev/sda USB boot device. A
Very possible it affects other devices attached, but all consumer
reports and test systems here all have NVME drives on m2 and when in
RAID mode. Listing PCI data linux will show Intel SATA controller
detected in RAID mode, but no drives detected, all you get is your
/dev/sda USB boot device. A
More and more systems are coming with M2 on RAID and Linux doesn't
work unless you change the system out of RAID mode. This is becoming
more and more of a problem. What is the status of Linux support for
the new systems?
TIA!!
More and more systems are coming with M2 on RAID and Linux doesn't
work unless you change the system out of RAID mode. This is becoming
more and more of a problem. What is the status of Linux support for
the new systems?
TIA!!
More and more system are coming with M2 devices on RAID configured
controllers which Linux does not support. Switching to AHCI mode
instead of RAID mode allows it to see the drives but that is not a fix
when you want it in RAID mode and want to use Windows as well. The
question I have is this
More and more system are coming with M2 devices on RAID configured
controllers which Linux does not support. Switching to AHCI mode
instead of RAID mode allows it to see the drives but that is not a fix
when you want it in RAID mode and want to use Windows as well. The
question I have is this
On 12/05/2016 04:20 AM, Joerg Roedel wrote:
> Hi David,
>
> On Sun, Dec 04, 2016 at 06:57:57PM -0600, David F wrote:
>> Aug 19 13:32:20 taz [ 156.425627] [ cut here ]
>> Aug 19 13:32:20 taz [ 156.428136] kernel BUG at
>> drivers/iommu/intel-iom
On 12/05/2016 04:20 AM, Joerg Roedel wrote:
> Hi David,
>
> On Sun, Dec 04, 2016 at 06:57:57PM -0600, David F wrote:
>> Aug 19 13:32:20 taz [ 156.425627] [ cut here ]
>> Aug 19 13:32:20 taz [ 156.428136] kernel BUG at
>> drivers/iommu/intel-iom
On 16/12/15 09:50, Adrian Hunter wrote:
>
>
> On 15/12/15 18:01, Ulf Hansson wrote:
>> +Adrian
>>
>> On 8 November 2015 at 23:05, Denis Bychkov wrote:
>>> The only started in 4.3 kernel (at least RC-5), 4.2.x does not have
>>> this problem. The kernel panic happens
On 16/12/15 09:50, Adrian Hunter wrote:
>
>
> On 15/12/15 18:01, Ulf Hansson wrote:
>> +Adrian
>>
>> On 8 November 2015 at 23:05, Denis Bychkov wrote:
>>> The only started in 4.3 kernel (at least RC-5), 4.2.x does not have
>>> this problem. The kernel panic happens immediately after the SDHC
is needed to make the modversions create a reference to
it.
On Sat, Feb 13, 2016 at 12:13 AM, David F. wrote:
> After sending the below, I realized that if someone doesn't want to
> have to dereference a pointer it could still be done the same way and
> just omitting the member variable (o
Frankly if XFS is going to change and break, now would be a good time
to convert from MSBF to LSBF, easy to do and would be much more
efficient on PC's.
On Sat, Feb 13, 2016 at 6:50 AM, Arnd Bergmann wrote:
> On Saturday 13 February 2016 13:18:32 Dave Chinner wrote:
>> On Fri, Feb 12, 2016 at
Feb 12, 2016 at 11:45 PM, David F. wrote:
> While creating a linux module that should be usable across a wide
> array of linux versions and builds, I've run into struct modules
> (THIS_MODULE) being a problem. It's the only internal struct accessed
> as a requirement to struct block_de
Frankly if XFS is going to change and break, now would be a good time
to convert from MSBF to LSBF, easy to do and would be much more
efficient on PC's.
On Sat, Feb 13, 2016 at 6:50 AM, Arnd Bergmann wrote:
> On Saturday 13 February 2016 13:18:32 Dave Chinner wrote:
>> On Fri,
is needed to make the modversions create a reference to
it.
On Sat, Feb 13, 2016 at 12:13 AM, David F. <df7...@gmail.com> wrote:
> After sending the below, I realized that if someone doesn't want to
> have to dereference a pointer it could still be done the same way and
> just omi
Feb 12, 2016 at 11:45 PM, David F. <df7...@gmail.com> wrote:
> While creating a linux module that should be usable across a wide
> array of linux versions and builds, I've run into struct modules
> (THIS_MODULE) being a problem. It's the only internal struct accessed
> as a
While creating a linux module that should be usable across a wide
array of linux versions and builds, I've run into struct modules
(THIS_MODULE) being a problem. It's the only internal struct accessed
as a requirement to struct block_device_operations .owner. It's a
bit annoying for this module
While creating a linux module that should be usable across a wide
array of linux versions and builds, I've run into struct modules
(THIS_MODULE) being a problem. It's the only internal struct accessed
as a requirement to struct block_device_operations .owner. It's a
bit annoying for this module
Yes. The drive was found fine on other controllers I tried it on.
On Mon, Mar 24, 2014 at 8:27 AM, Bartlomiej Zolnierkiewicz
wrote:
>
> + linux-ide mailing list on Cc:
>
> On Monday, March 24, 2014 02:15:58 PM One Thousand Gnomes wrote:
>> On Sat, 22 Mar 2014 16:32:54 -0700
&g
David F. df7...@gmail.com wrote:
Hi,
It appears if nIEN is set all polling type IO fails. After an
attempt, future non-polled communications also fails. This patch
allows it to work. Not sure if any spin lock protection would be
needed or the system already handles the device
Hi,
It appears if nIEN is set all polling type IO fails. After an
attempt, future non-polled communications also fails. This patch
allows it to work. Not sure if any spin lock protection would be
needed or the system already handles the device existence for the
generated irq with polling
Hi,
It appears if nIEN is set all polling type IO fails. After an
attempt, future non-polled communications also fails. This patch
allows it to work. Not sure if any spin lock protection would be
needed or the system already handles the device existence for the
generated irq with polling
34 matches
Mail list logo