From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <9front-bounces@9front.inri.net>
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI
	autolearn=ham autolearn_force=no version=3.4.4
Received: from 9front.inri.net (9front.inri.net [168.235.81.73])
	by inbox.vuxu.org (Postfix) with ESMTP id C06DE2259A
	for <ml@inbox.vuxu.org>; Fri, 12 Apr 2024 11:11:07 +0200 (CEST)
Received: from mout02.posteo.de ([185.67.36.66]) by 9front; Fri Apr 12 05:09:57 -0400 2024
Received: from submission (posteo.de [185.67.36.169]) 
	by mout02.posteo.de (Postfix) with ESMTPS id 6041C240101
	for <9front@9front.org>; Fri, 12 Apr 2024 11:09:53 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017;
	t=1712912993; bh=A2YtDIgvpJshlGkuODyp9G9d8Jvw6XNp4i7nFSpbtT4=;
	h=MIME-Version:Content-Type:Content-Transfer-Encoding:Date:From:To:
	 Subject:Message-ID:From;
	b=GHGgXqM8gF+lqI6dY+Q6fLQijfq97UkLJ5jkO5m+FBCzXMr/1DFUVI+iEG0i3ikhz
	 RwY1J6ZlXMNKHzMD3yyQ/bzJ+en3brbYahvWiRz7YaGc04hPFwWAroqWRB8XliShXM
	 weOjI45jW7klMvQnpjViRV1Mw2j3PTeLL+MTye2kZ1/3YMif2hlyQmJGxhVnKUk28n
	 oY74BWv0aZRycO/IZ1HFsjhd6kum/YnZSrF42e2nvC5k9WkGFiXXru220XqVNypkf5
	 Qe6bTj4KooOjxFR0e9Lczgm2wIJ9YOoe0nizI9GBoK0Depa/X3OVWXPRBVRwFgW1bg
	 dpn/+xElPW2Vg==
Received: from customer (localhost [127.0.0.1])
	by submission (posteo.de) with ESMTPSA id 4VG9kT0rFLz6txn
	for <9front@9front.org>; Fri, 12 Apr 2024 11:09:52 +0200 (CEST)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Fri, 12 Apr 2024 09:09:52 +0000
From: alex-ml@posteo.de
To: 9front@9front.org
In-Reply-To: <46C5C43525BF082E9EC3F16AE4E96AAF@felloff.net>
References: <46C5C43525BF082E9EC3F16AE4E96AAF@felloff.net>
Message-ID: <0a13784c6f6d60e847565ef2f2679c54@posteo.de>
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: ISO-certified social reduce/map SSL over ActivityPub package-aware extension 
Subject: Re: [9front] Install to NVMe (MNT Reform)
Reply-To: 9front@9front.org
Precedence: bulk

Hello cinap,

thank you very much. pci shows the following:

0.0.0:      brg    06.04.00  16c3/abcd  255
128.0.0:  brg    06.04.00  16c3/abcd  255
129.0.0:  disk   01.08.02  15b7/5019  0  0:20104004  16384  4:20100004  
256

Unfortunately I do not understand this output, is there perhaps a 
possible indication of such a problem with the pcie controller?

Please excuse the missing information: I am using the nightly build from 
yesterday ("9front-10499.reform.img") and I have not noticed any error 
messages (I do not see any warnings / error messages when booting).

On boot there are the following lines (regarding "sdN0"):
...
sdN (nvme): using 4 submit queues
...
/dev/sdN0: WDC WDS100T2B0C-00PX
/dev/sdN0/data
...

Is there any way to test the functionality of the controller?

Thank you very much and best regards,
Alex


Am 12.04.2024 09:29 schrieb cinap_lenrek@felloff.net:
>> Hello,
> 
>> I have read about the installation of 9front on NVMe on
>> http://helpful.cat-v.org/Blog/2022/07/12/0/. Unfortunately, when I run
>> inst/start, there is only /dev/sdM0/ to choose from. On startup and 
>> when
>> I look at /dev and sysinfo, sdN0 is listed, so it should at least be
>> recognized. Is there a way to use this sdN0 to install 9front to?
> 
> try running "pci" command to see if the nvme drive shows up
> on the pci bus.
> 
> iirc there where some nvme drives that had some issues with
> the pcie controller of the mnt reform.
> 
> also, you have literally provided no information about the
> system. like are there any error messages/prints maybe during
> boot?
> 
> --
> cinap