Re: [OpenIndiana-discuss] install on very recent hardware
On 09/19/19 08:34 PM, Tim Mooney wrote: In regard to: Re: [OpenIndiana-discuss] install on very recent hardware,...: Hi Tim, Hi Michal! Thanks much for the response and the info you provided. I know I've seen a link somewhere about loading updated or additional drivers, but I can't find it now.? Is there a way to load updated drivers that the LiveCD or GUI installer can use?? Pointer to the docs appreciated. I am afraid that's not possible. There were two attempts to deliver multiple nvidia drivers and mediate them so users can switch, but they stalled 2 years ago: https://github.com/OpenIndiana/oi-userland/pull/3458/ https://github.com/OpenIndiana/oi-userland/pull/3673/ The tricky thing is that v340 supports all the old devices https://www.nvidia.com/Download/driverResults.aspx/135163/en-us and I am not sure we can update it to v390 or newer which supports these new cards. Unless we have a reasonable driver mediation I am afraid we are stuck with v340 and users have to install newer version manually... Ok, that's more or less what I suspected, but I appreciate the confirmation. Is there something special that needs to be done to install OI onto an NVMe drive? It should work. nvme driver should be in the install medium. If you still have access to the HW, you can check that the nvme package is present in the medium and that the driver was loaded via modinfo. Could you report this to the illumos developer mailing list? Unfortunately I don't have access to the hardware any longer. I had it for about a week, but my coworker needed it back to begin using it. New Dell workstations are coming with either more security or more restrictions (depending on how you look at it) in the "BIOS". I'm guessing the problem seeing the NVMe drive wasn't so much a driver issue as one of the many features that could not be overridden when I switched the system from UEFI to Legacy BIOS. As of recently I have Lenovo ThinkPad P52 with the very same nvidia GPU, also with NVMe. So far I was unable to even boot OpenIndiana from USB, but I tried for only like 10 minutes or so. Over the weekend I may try harder and see more closely what the situation is. Michal ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Beginner format help needed
Hi, Have you tried writing a sol2 label on the disc? #fdisk -B /dev/rdsk/c9t002538B471B9EFD3d0p0 - Espen martinsen > Den 19. sep. 2019 kl. 20.12 skrev Stephan Althaus > : > > c9t002538B471B9EFD3d0 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] install on very recent hardware
In regard to: Re: [OpenIndiana-discuss] install on very recent hardware,...: Hi Tim, Hi Michal! Thanks much for the response and the info you provided. I know I've seen a link somewhere about loading updated or additional drivers, but I can't find it now.? Is there a way to load updated drivers that the LiveCD or GUI installer can use?? Pointer to the docs appreciated. I am afraid that's not possible. There were two attempts to deliver multiple nvidia drivers and mediate them so users can switch, but they stalled 2 years ago: https://github.com/OpenIndiana/oi-userland/pull/3458/ https://github.com/OpenIndiana/oi-userland/pull/3673/ The tricky thing is that v340 supports all the old devices https://www.nvidia.com/Download/driverResults.aspx/135163/en-us and I am not sure we can update it to v390 or newer which supports these new cards. Unless we have a reasonable driver mediation I am afraid we are stuck with v340 and users have to install newer version manually... Ok, that's more or less what I suspected, but I appreciate the confirmation. Is there something special that needs to be done to install OI onto an NVMe drive? It should work. nvme driver should be in the install medium. If you still have access to the HW, you can check that the nvme package is present in the medium and that the driver was loaded via modinfo. Could you report this to the illumos developer mailing list? Unfortunately I don't have access to the hardware any longer. I had it for about a week, but my coworker needed it back to begin using it. New Dell workstations are coming with either more security or more restrictions (depending on how you look at it) in the "BIOS". I'm guessing the problem seeing the NVMe drive wasn't so much a driver issue as one of the many features that could not be overridden when I switched the system from UEFI to Legacy BIOS. Thanks again, Tim -- Tim Mooney tim.moo...@ndsu.edu Enterprise Computing & Infrastructure 701-231-1076 (Voice) Room 242-J6, Quentin Burdick Building 701-231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Beginner format help needed
Hello!
The disk inquestion has a GPT.
When i add a test-partition with win10 in the unallocated space,
the disk is shown in oi (wich reconfigure 'on') in gparted with all
partitions.
when i then make a simple change with #format like #volname
the disk is no more listed in gparted.
So i assume it is a bug in #format that is triggered by the GPT
partition data of my disk. (?)
#format complains about "no reserved partition found".
Any hints are welcome.
Stephan
--
OUTPUT of #format:
format> verify
Volume name = < >
ascii name =
bytes/sector = 512
sectors = 2000409264
accessible sectors = 2000409230
Part Tag Flag First Sector Size Last Sector
0 - wm 2048 16.00MB 34815
1 - wm 34816 33.53GB 70348799
2 system wm 70348800 99.00MB 70551551
3 usr wm 71600128 100.00GB 281315327
4 - wm 302286848 32.23GB 369870847
5 - wm 369870848 218.88GB 828893439
6 unassigned wm 0 0 0
format> volname
Enter 8-character volume name (remember quotes)[""]:"DISK1 "
Ready to label disk, continue? y
no reserved partition found
format> quit
--
On 09/18/19 20:26, Stephan Althaus wrote:
Hello!
I have unused space on a second NVMe drive,
which i intend to use as a mirror partition to my existing root pool.
(and i know that this is not the best way to do, but thats not the
point here)
Yesterday evening i tried to #format a new #partition but the format
process ended surprisingly,
and i left the system w/o checking.
As of today, something ("solaris label"?) is gone,
and i cant write a modified partition to disk with an error message.
The old partition is readable somewhere on the disk..
Which options do i have now?
Any help is welcome,
Stephan
Heres the format output:
#format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c8t002538B471B9EFD6d0 1024GB-CXY74D1Q-953.87GB>
/pci@0,0/pci8086,a167@1b/pci144d,a801@0/blkdev@w002538B471B9EFD6,0
1. c9t002538B471B9EFD3d0 1024GB-CXY74D1Q-953.87GB>
/pci@0,0/pci8086,a118@1d/pci144d,a801@0/blkdev@w002538B471B9EFD3,0
2. c27t1d0 hd 224 sec 56> OIROOT
/pci@0,0/pci1028,7b1@17/disk@1,0
Specify disk (enter its number): 1
selecting c9t002538B471B9EFD3d0
Ready to get manufacturer's defect list from unformatted drive.
This cannot be interrupted and takes a long while.
Continue? y
Extracting manufacturer's defect list...[disk unformatted, no defect
list found]
Error: can't open disk '/dev/rdsk/c9t002538B471B9EFD3d0p0'.
No Solaris fdisk partition found.
FORMAT MENU:
disk - select a disk
type - select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk
fdisk - run the fdisk program
repair - repair a defective sector
show - translate a disk address
label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
volname - set 8-character volume name
! - execute , then return
quit
format> partition
PARTITION MENU:
0 - change `0' partition
1 - change `1' partition
2 - change `2' partition
3 - change `3' partition
4 - change `4' partition
5 - change `5' partition
6 - change `6' partition
expand - expand label to use whole disk
select - select a predefined table
modify - modify a predefined partition table
name - name the current table
print - display the current table
label - write partition map and label to the disk
! - execute , then return
quit
partition> print
Current partition table (original):
Total disk sectors available: 2000392813 + 16384 (reserved sectors)
Part Tag Flag First Sector Size Last Sector
0 - wm 2048 16.00MB 34815
1 - wm 34816 33.53GB 70348799
2 system wm 70348800 99.00MB 70551551
3 unassigned wm 0 0 0
4 usr wm 71600128 100.00GB 281315327
5 unassigned wm 0 0 0
6 - wm 302286848 32.23GB 369870847
partition> 5
Part Tag Flag First Sector Size Last Sector
5 unassigned wm 0 0 0
Enter partition id tag[usr]: usr
Enter partition permission flags[wm]:
Enter new starting
