Date: Mon, 13 Jul 2020 17:38:14 +0000 (UTC) From: Paul Pathiakis <pathiaki2@yahoo.com> To: freebsd-hardware@freebsd.org, Javier Sturman <sturmanj@gmail.com> Subject: Re: DELL PowerEdge T130 - Devices detected as SATA Message-ID: <1588569072.955025.1594661894787@mail.yahoo.com> In-Reply-To: <CANG%2B0R8pPAz3J6yQZqWmq=xEkMg2dmjG9jY6_LQXNtf3wBOqLg@mail.gmail.com> References: <CANG%2B0R8pPAz3J6yQZqWmq=xEkMg2dmjG9jY6_LQXNtf3wBOqLg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi,
I have a 'possibility'. IF your CD/DVD are not plugged into SATA ports, do so. Get them off this controller. SAS will try to accommodate SATA but, depending on the order of detection, it will 'step down' in speed.
Next, try putting all the SAS drives (do you have any?), on a separate controller line.
If you have only SATA drives, put the SATA III, followed by SATA II, (any SATA I ?) on the chain as detected. I believe as SAS encounters devices, it will allow transfers at the highest speed it encounters and step down as it goes.
This is all off the top of my head not having read SAS spec in a while and only having SAS and M.2 drives now.
Paul
On Monday, July 13, 2020, 1:29:07 PM EDT, Javier Sturman <sturmanj@gmail.com> wrote:
Hi. I've got FreeBSD 12.1 installed on a Dell PowerEdge T130 with:
2x 2TB hdd
1 SSD.
I've got the PERC configured as HBA. This is the output from dmesg:
AVAGO MegaRAID SAS FreeBSD mrsas driver version: 07.709.04.00-fbsd
mrsas0: <AVAGO Fury SAS Controller> port 0x3000-0x30ff mem
0x92c00000-0x92c0ffff,0x92b00000-0x92bfffff irq 16 at device 0.0 on pci1
mrsas0: FW now in Ready state
mrsas0: Using MSI-X with 4 number of vectors
mrsas0: FW supports <96> MSIX vector,Online CPU 4 Current MSIX <4>
mrsas0: max sge: 0x46, max chain frame size: 0x400, max fw cmd: 0xef
mrsas0: Issuing IOC INIT command to FW.
mrsas0: IOC INIT response received from FW.
mrsas0: System PD created target ID: 0x0
mrsas0: System PD created target ID: 0x1
mrsas0: System PD created target ID: 0x2
mrsas0: FW supports: UnevenSpanSupport=1
mrsas0: max_fw_cmds: 239 max_scsi_cmds: 223
mrsas0: MSI-x interrupts setup success
mrsas0: mrsas_ocr_thread
........
ZFS filesystem version: 5
ZFS storage pool version: features support (5000)
Timecounters tick every 1.000 msec
mrsas0: Disestablish mrsas intr hook
ugen0.1: <0x8086 XHCI root HUB> at usbus0
uhub0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
Trying to mount root from zfs:zroot/ROOT/default []...
cd0 at ahcich4 bus 0 scbus6 target 0 lun 0
cd0: <PLDS DVD+-RW DU-8A5LH 6D5M> Removable CD-ROM SCSI device
cd0: Serial Number 2WXxxxPLC0086451X0A00
cd0: 150.000MB/s transfers (SATA 1.x, UDMA6, ATAPI 12bytes, PIO 8192bytes)
cd0: Attempt to query device size failed: NOT READY, Medium not present -
tray closed
da2 at mrsas0 bus 1 scbus1 target 2 lun 0
da2: <ATA SanDisk SDSxxxA24 30RL> Fixed Direct Access SPC-4 SCSI device
da2: Serial Number 172757804261
da2: 150.000MB/s transfers
da2: 228936MB (468862128 512 byte sectors)
da0 at mrsas0 bus 1 scbus1 target 0 lun 0
da0: <ATA HUS722TxxxLA600 MU03> Fixed Direct Access SPC-4 SCSI device
da0: Serial Number WMC6N0M1FFPK
da0: 150.000MB/s transfers
da0: 1907729MB (3907029168 512 byte sectors)
da1 at mrsas0 bus 1 scbus1 target 1 lun 0
da1: <ATA ST2000NM00xx-2F3 EA04> Fixed Direct Access SPC-4 SCSI device
da1: Serial Number ZDS0LJKY
da1: 150.000MB/s transfers
da1: 1907729MB (3907029168 512 byte sectors)
When I installed the server I had to enable mrsas in device.hints for
better results:
hw.mfi.mrsas_enable="1"
Any ideas why could the devices be detected as 150MB/s transfers only?
--
Javier Sturman
_______________________________________________
freebsd-hardware@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org"
From owner-freebsd-hardware@freebsd.org Mon Jul 13 21:14:02 2020
Return-Path: <owner-freebsd-hardware@freebsd.org>
Delivered-To: freebsd-hardware@mailman.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
by mailman.nyi.freebsd.org (Postfix) with ESMTP id 373573711C5
for <freebsd-hardware@mailman.nyi.freebsd.org>;
Mon, 13 Jul 2020 21:14:02 +0000 (UTC)
(envelope-from patpro@patpro.net)
Received: from rack.patpro.net (rack.patpro.net [193.30.227.216])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "patpro.net", Issuer "Let's Encrypt Authority X3" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 4B5Gbs1qddz4XCF
for <freebsd-hardware@freebsd.org>; Mon, 13 Jul 2020 21:14:00 +0000 (UTC)
(envelope-from patpro@patpro.net)
X-Virus-Scanned: amavisd-new at patpro.net
Received: from cassandre.patpro.net (lns-bzn-58-82-251-217-20.adsl.proxad.net
[82.251.217.20])
(using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
(Client did not present a certificate)
by rack.patpro.net (Postfix) with ESMTPSA id D48803F42;
Mon, 13 Jul 2020 23:13:50 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: keyboard has a weird layout after boot
From: Patrick Proniewski <patpro@patpro.net>
In-Reply-To: <CA+=RcCp5x3BBDLbO9P78BbmHB7offbq8K2sHgKbrVRcfjR831w@mail.gmail.com>
Date: Mon, 13 Jul 2020 23:13:50 +0200
Cc: freebsd-hardware@freebsd.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <4EA5D9EF-4205-49AD-9AC9-1B381EDAA473@patpro.net>
References: <CA+=RcCrSqGE=rDoLxTTAfyVCtyOmE544Zo=yr_d-OpFB3tr5zA@mail.gmail.com>
<E1DFC9A7-A69A-4ADC-9C49-1BF5165F0A35@patpro.net>
<CA+=RcCp5x3BBDLbO9P78BbmHB7offbq8K2sHgKbrVRcfjR831w@mail.gmail.com>
To: =?utf-8?Q?László_Lajos_Jánszky?= <laszlo.janszky@gmail.com>
X-Mailer: Apple Mail (2.3124)
X-Rspamd-Queue-Id: 4B5Gbs1qddz4XCF
X-Spamd-Bar: ---
X-Spamd-Result: default: False [-3.19 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[];
ARC_NA(0.00)[];
R_DKIM_ALLOW(-0.20)[patpro.net:s 2006-68cfba9b];
MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[];
TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+a];
TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain];
NEURAL_HAM_LONG(-1.01)[-1.008]; TO_MATCH_ENVRCPT_SOME(0.00)[];
DKIM_TRACE(0.00)[patpro.net:+]; RCPT_COUNT_TWO(0.00)[2];
DMARC_POLICY_ALLOW(-0.50)[patpro.net,quarantine];
NEURAL_HAM_SHORT(-0.71)[-0.707];
NEURAL_HAM_MEDIUM(-0.97)[-0.974]; FREEMAIL_TO(0.00)[gmail.com];
FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+];
ASN(0.00)[asn:29608, ipnet:193.30.224.0/22, country:FR];
RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.33
Precedence: list
List-Id: General discussion of FreeBSD hardware <freebsd-hardware.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-hardware>,
<mailto:freebsd-hardware-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hardware/>;
List-Post: <mailto:freebsd-hardware@freebsd.org>
List-Help: <mailto:freebsd-hardware-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
<mailto:freebsd-hardware-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jul 2020 21:14:02 -0000
Sorry it did not work out :/
I'm not so sure it's an NKRO related bug but it might need some debugging. You might as well post of FreeBSD forums to see if other people are using the same keyboard as you.
I'm using a Vortex ViBE and a Vortex Tab90M without any problem on FreeBSD but I'm not sure they are really NKRO.
patpro
> On 13 juil. 2020, at 15:30, László Lajos Jánszky <laszlo.janszky@gmail.com> wrote:
>
> Same with "sysctl kern.evdev.rcpt_mask=12" and removing the "driver kbd"
> line from xorg config.
>
> Patrick Proniewski <patpro@patpro.net> ezt írta (időpont: 2020. júl. 12.,
> V, 16:04):
>
>> Hello,
>>
>> Give this a try and let us know if it solves your problem:
>>
>>
>> https://forums.freebsd.org/threads/xfce-keyboard-goes-wild-after-pkg-upgrade.74397
>>
>> good luck,
>> patpro
>>
>>
>>> On 12 juil. 2020, at 15:51, László Lajos Jánszky <
>> laszlo.janszky@gmail.com> wrote:
>>>
>>> I have an Obins Anne Pro keyboard, which is a 60% mechanical NKRO
>> keyboard
>>> http://en.obins.net/anne-pro It works properly in the UEFI and in the
>>> rescue shell when I quit the boot menu, but after FreeBSD booted up and I
>>> got the login screen it changes layout to something weird. For example I
>>> got "a" when pressing backspace or "w". Most of the keys stop working. I
>>> used it on a Win7 PC for a few years, so it works fine and in theory it
>> has
>>> a standard US ANSI layout, at least the UEFI and the rescue shell does
>> not
>>> have problems with it. I tried it with FreeBSD 12.1 and KDE. I tried
>>> another keyboard, which is a Logitech K360 and that works as expected
>> with
>>> 102 key generic Hungarian layout. I tried all the generic models in KDE
>>> with US layout by the Anne Pro, but had no success. I tried to disable
>> the
>>> KDE by commenting out "exec ck-launch-session startplasma-x11" from the
>>> .xinitrc file, but somehow FreeBSD still boots with KDE idk why. I tried
>>> the keyboard in a console with ctrl+alt+f3, which in theory would be the
>>> same as booting without KDE and it had the same issue in that console
>> too,
>>> so I think it is not an xorg related thing, but I am not entirely sure.
>>> Somebody suggested changing the keyboard mode to 6-KRO, but I did not
>> find
>>> anything about it in the manual, so probably this keyboard is NKRO only.
>>> Any idea how to make it work with FreeBSD or what causes this problem?
>>> _______________________________________________
>>> freebsd-hardware@freebsd.org mailing list
>>> https://lists.freebsd.org/mailman/listinfo/freebsd-hardware
>>> To unsubscribe, send any mail to "
>> freebsd-hardware-unsubscribe@freebsd.org"
>>
>>
> _______________________________________________
> freebsd-hardware@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-hardware
> To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1588569072.955025.1594661894787>