Re: [OpenIndiana-discuss] What is the equivalent packages on OI?

[Toomas Soome via openindiana-discuss]

> On 7. Feb 2021, at 09:46, cretin1997 via openindiana-discuss 
>  wrote:
> 
> They are Ubuntu packages:
> 
> gcc libncurses5-dev libtinfo5 libffi-dev libgl1-mesa-dev
> libx11-dev libxext-dev libxrender-dev libxrandr-dev libxpm-dev
> 
> I searched for packages name using pkg search -rp but it seems I need to know 
> exact packages name already. It don't list all packages whose names contain 
> the text like on Q4OS.
> 

man pkg.

pkg search -r libncurses\*

rgds,
toomas
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] ~6 minutes to OI banner/boot options in text install

[Toomas Soome via openindiana-discuss]

> On 7. Feb 2021, at 09:04, Chris  wrote:
> 
> On 2021-02-06 13:36, Chris wrote:
>> On 2021-02-06 00:56, Toomas Soome wrote:
 On 6. Feb 2021, at 01:41, Chris  wrote:
 On 2021-02-05 14:16, Chris wrote:
> On 2021-02-05 13:46, Toomas Soome wrote:
>>> On 5. Feb 2021, at 19:54, Chris  wrote:
>>> On 2021-01-30 02:28, Toomas Soome wrote:
> On 30. Jan 2021, at 10:39, Chris  wrote:
> On 2021-01-30 00:03, Toomas Soome wrote:
>>> On 30. Jan 2021, at 09:40, Chris  wrote:
>>> On 2021-01-29 22:24, Toomas Soome via openindiana-discuss wrote:
> On 30. Jan 2021, at 03:43, Chris  wrote:
> On 2021-01-29 17:18, Andy Fiddaman wrote:
>> On Fri, 29 Jan 2021, Chris wrote:
>> ; OK just dragged a Dell Optiplex 790 off the shelf
>> ; with a 4 core 8 thread i5 CPU in it, and as much RAM
>> ; as I could jam in it.
>> ; BIOS:
>> ; boot UEFI
>> ; SATA ahci
>> ; I've tried 2 different Nvidia cards, as well as the
>> ; intermal video. The results are the same;
>> ; 2.5 minutes to get to the OI banner/boot options.
>> ; An additiona 3.5 to draw the OI banner/options screen.
>> ; It takes ~0.5 seconds to draw each cell. To be clear;
>> ; I'm not complaining here. Rather, I'm trying to
>> ; pinpoint WTF is going wrong in hopes of overcoming
>> ; the problem. I've attempted to put OI on 3 different
>> ; computers now, and the results have all been
>> ; underwhelming in the console dept.
>> ;
>> ; Any thoughts?
>> If you can press  really early in the boot process, you 
>> get the
>> first loader prompt (I forget exactly how it looks). At that 
>> point,
>> enter "-t" without the quotes and press return. That will keep in
>> VGA mode, which might well be faster/usable.
> Huge thanks for the reply, Andy!
> Yes, it made a difference. Drawing each cell only takes 0.25
> seconds. :-P
> So somewhat faster, anyway. It's funny. It starts out quite
> fast. The speed I normally experience with other stuff. It
> writes
> Available consoles:
> text VGA ...
> ttya port 0x3f8
> ttyb ... not present
> ttyc ... not present
> ttyd ... not present
> null software device
> spin software device
> Right at this point is where it drops to about 1/2 or slower 
> speed.
> Then, cell by cell, it prints
> console ttyb failed to initialize
> console ttyc failed to initialize
> console ttyd failed to initialize
 This is the point where you have got hint about why this happens. 
 The same defect
 is with virtualbox, when you have configured host pipe for serial 
 device.
 The three lines above tell us that ttya was successfully 
 initialized, so it must
 have to do about ttya.
>>> OK I neglected to note that this was including the advice by Andy 
>>> to drop to
>>> text mode, by interrupting loader, and entering -t at the prompt 
>>> followed by
>>> enter. It's clear that it was attempting serial mode -- note the 
>>> port 0x3f8
>>> Without interrupting loader, text and ttya return:
>>> text VESA (800x600 - 1600x1200 depending on what I'm hooked up to)
>>> ttya ... not present
>>> I'm attempting it again via Legacy where
>>> text VESA 1600x1200
>>> ttya ... not present
>>> Choosing 5 (options), followed by 5 (verbose) has already taken 20
>>> minutes (it's still in progress). I think I'm just going to try to
>>> install it and work on it further from the internal disk. In hopes
>>> of getting at least a small speed increase from 0 to actual boot.
>>> I greatly appreciate your insight on this, Toomas.
>> Ok, so this guess was not good one afterall. If you are doing CD 
>> (ISO) boot, you
>> will get loader started as first stage - that is, there is no way to 
>> enter
>> options; however, once you get out of menu and on O prompt, you can 
>> enter:
>> framebuffer off
>> on BIOS boot, this will switch to VGA text mode, on UEFI, it will 
>> switch terminal
>> draw from GOP Blt() to SimpleTextOutput protocol (gfx can not be 
>> switched off as
>> there is no VGA text mode in UEFI, there may not be even VGA).
>> If you are booting from USB stick, press space on very first spinner 
>> to get boot:
>> prompt, from there you can enter: -t 

Re: [OpenIndiana-discuss] catching hell getting booted

[Toomas Soome via openindiana-discuss]

> On 6. Feb 2021, at 11:16, Toomas Soome via openindiana-discuss 
>  wrote:
> 
> 
> 
>> On 6. Feb 2021, at 08:54, Harry Putnam > > wrote:
>> 
>> Gary Mills mailto:gary_mi...@fastmail.fm> 
>> >> writes:
>> 
>>> On Wed, Feb 03, 2021 at 01:06:12PM -0500, Harry Putnam wrote:
 I've been running an hp xw8600 for several years and for about 5-6 of
 those yrs running openindiana OS.
 
 A month ago or so I shutdown OI to change out a couple of disks.
 
 Once I did that I have not been able to use any of the oi installation
 media I've made up.  Both usb stick and DVD fails to boot,  No matter
 how I set the boot order. And even though those  same stick media will
 boot my HP Z800 to live media for OI install.
 
 I've tried all I can think, changing usb ports,  Trying ISO from CD.
 The xw8600 has two of those,  I set the boot order to CDrom first but it
 goes right buy with out a response and tries to boot from disk.
>>> 
>>> It sounds as if you are not really setting the boot order in the BIOS.
>>> Could it really that simple?  HP does do some funny things with their
>>> BIOS.  Are you saving your changes after you make them?  Does the BIOS
>>> show the new boot order after the boot fails?
>> 
>> Here is how real the boot order is: First I can look at the setting in
>> bios. Save and Close bios... then reopen and see my setting is still
>> there.  Further there is a switch early in boot where you can click F9
>> and wind up at a boot prompt where again I can see the order is correct.
>> 
>> Currently I'm tying to install from and older version 2018.10.  Burnded to 
>> DVD
>> today.  When the boot prompt opens I see CDrom at the top , usb next
>> then hhd.  I press cdrom... it pauses a few moments then reverts to
>> the install on hard disk of ubuntu (zfs on root).
>> 
>> It tell me there is no image on the cdrom.  I put it on a different
>> HP, this one HP Z800... and I'll give a guess what happens... it boots
>> into the OI on the cdrom.
>> 
>> I can assure you I have set the boot order depending on what media I'm
>> attempting. 
> 
> 
> I guess it does not really like the hybrid iso image and/or dual BIOS/UEFI 
> image. Unfortunately, to test what is exactly the issue, it means we should 
> create test image with less options (one without hybrid — that is, disk 
> partition) and if this does not help, one without EFI boot support.
> 
> Also, please check (if not already done) for firmware update.
> 
> 
>> 
>>> Some systems will not boot from USB, but in that case they will still
>>> boot from a CD reader.  I don't think that's your problem.
>> 
>> So far that has not happened here.  Except some years ago on this same
>> host when I made my initial install, clear back to build 147.
>> 
>> And a couple of months ago, I burned a USB stick with ubuntu on it.
>> After getting sick of dicking around trying to install OI
>> 
>> Booting from that stick right into ubuntu installation immediately.
>> 
>> I want to say it points to our software being a problem where others
>> work. But, I'm so unskilled as to be nearly certain that the fault is
>> right in myu pea brain somewhere.
> 
> 
> The same deal with stick; fortunately it is a bit easier to test (does not 
> involve burning the cd/dvd). I can prepare usb image(s) for test, but some 
> hours later - need to go afk now.
> 

Can you test with this USB stick image: OI-hipster-text-20201031-tsoome.usb 


rgds,
toomas

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] What is the equivalent packages on OI?

[Alan Coopersmith]

On 2/6/21 11:46 PM, cretin1997 via openindiana-discuss wrote:

They are Ubuntu packages:

gcc libncurses5-dev libtinfo5 libffi-dev libgl1-mesa-dev
libx11-dev libxext-dev libxrender-dev libxrandr-dev libxpm-dev


With the IPS package system, there usually aren't separate -dev packages,
but the dev files are part of the main package, with the "devel" facet
used to control whether or not they are installed, so the OI equivalent
to most of those is the same name with "-dev" removed.  (For libgl1-mesa-dev,
you'll also need to remove "libgl1-" - it's just "mesa" here, and libncurses5
is just "ncurses".)

For gcc, pick a version:
https://pkg.openindiana.org/hipster/en/search.shtml?token=gcc&action=Search

-alan-

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] ~6 minutes to OI banner/boot options in text install

[Chris]

On 2021-02-07 01:48, Toomas Soome wrote:

On 7. Feb 2021, at 09:04, Chris  wrote:

On 2021-02-06 13:36, Chris wrote:

On 2021-02-06 00:56, Toomas Soome wrote:

On 6. Feb 2021, at 01:41, Chris  wrote:
On 2021-02-05 14:16, Chris wrote:

On 2021-02-05 13:46, Toomas Soome wrote:

On 5. Feb 2021, at 19:54, Chris  wrote:
On 2021-01-30 02:28, Toomas Soome wrote:

On 30. Jan 2021, at 10:39, Chris  wrote:
On 2021-01-30 00:03, Toomas Soome wrote:

On 30. Jan 2021, at 09:40, Chris  wrote:
On 2021-01-29 22:24, Toomas Soome via openindiana-discuss wrote:

On 30. Jan 2021, at 03:43, Chris  wrote:
On 2021-01-29 17:18, Andy Fiddaman wrote:

On Fri, 29 Jan 2021, Chris wrote:
; OK just dragged a Dell Optiplex 790 off the shelf
; with a 4 core 8 thread i5 CPU in it, and as much RAM
; as I could jam in it.
; BIOS:
; boot UEFI
; SATA ahci
; I've tried 2 different Nvidia cards, as well as the
; intermal video. The results are the same;
; 2.5 minutes to get to the OI banner/boot options.
; An additiona 3.5 to draw the OI banner/options screen.
; It takes ~0.5 seconds to draw each cell. To be clear;
; I'm not complaining here. Rather, I'm trying to
; pinpoint WTF is going wrong in hopes of overcoming
; the problem. I've attempted to put OI on 3 different
; computers now, and the results have all been
; underwhelming in the console dept.
;
; Any thoughts?
If you can press  really early in the boot process, 
you get the
first loader prompt (I forget exactly how it looks). At that 
point,
enter "-t" without the quotes and press return. That will keep 
in

VGA mode, which might well be faster/usable.

Huge thanks for the reply, Andy!
Yes, it made a difference. Drawing each cell only takes 0.25
seconds. :-P
So somewhat faster, anyway. It's funny. It starts out quite
fast. The speed I normally experience with other stuff. It
writes
Available consoles:
text VGA ...
ttya port 0x3f8
ttyb ... not present
ttyc ... not present
ttyd ... not present
null software device
spin software device
Right at this point is where it drops to about 1/2 or slower 
speed.

Then, cell by cell, it prints
console ttyb failed to initialize
console ttyc failed to initialize
console ttyd failed to initialize
This is the point where you have got hint about why this 
happens. The same defect
is with virtualbox, when you have configured host pipe for 
serial device.
The three lines above tell us that ttya was successfully 
initialized, so it must

have to do about ttya.
OK I neglected to note that this was including the advice by Andy 
to drop to
text mode, by interrupting loader, and entering -t at the prompt 
followed by
enter. It's clear that it was attempting serial mode -- note the 
port 0x3f8

Without interrupting loader, text and ttya return:
text VESA (800x600 - 1600x1200 depending on what I'm hooked up 
to)

ttya ... not present
I'm attempting it again via Legacy where
text VESA 1600x1200
ttya ... not present
Choosing 5 (options), followed by 5 (verbose) has already taken 
20
minutes (it's still in progress). I think I'm just going to try 
to
install it and work on it further from the internal disk. In 
hopes

of getting at least a small speed increase from 0 to actual boot.
I greatly appreciate your insight on this, Toomas.
Ok, so this guess was not good one afterall. If you are doing CD 
(ISO) boot, you
will get loader started as first stage - that is, there is no way 
to enter
options; however, once you get out of menu and on O prompt, you 
can enter:

framebuffer off
on BIOS boot, this will switch to VGA text mode, on UEFI, it will 
switch terminal
draw from GOP Blt() to SimpleTextOutput protocol (gfx can not be 
switched off as

there is no VGA text mode in UEFI, there may not be even VGA).
If you are booting from USB stick, press space on very first 
spinner to get boot:
prompt, from there you can enter: -t as Andy was suggesting, it 
will start loader
in text mode, without switching to VBE framebuffer. Once the OS is 
installed, you
can create /boot/config with -t in it, this will achieve the same 
effect.

That much about workaround.
“normally”, if drawing in FB mode is slow, it will help to use 
lower resolution
and/or depth, but as you wrote, 800x600 was just as bad as 
1920x1200, it means

something else is going on there.
You can set mode as: framebuffer set XxY[xD], where D is for 
depth, defaults to
32, if not present. framebuffer list [depth] will list available 
modes. With BIOS
mode, you can also try something like 640x400 or 640x480, below 
that the terminal

will get too weird even with 6x12 font...
If depth 8 or 15/16 does not make it faster, it still means there 
is something
weird going on, and at this point, I’d suggest to check if there 
is firmware
update from vendor. (tbh, firmware update would be good as first 
check, the hw
vendors are known to produce a lot of bad things, especially if it 
comes to have

bios emulation with uefi csm.).
Sure. Good point. But already updated it. You've given me some 
things to poke at.

I'll give

Re: [OpenIndiana-discuss] ~6 minutes to OI banner/boot options in text install

[Toomas Soome via openindiana-discuss]

> On 7. Feb 2021, at 20:20, Chris  wrote:
> 
> On 2021-02-07 01:48, Toomas Soome wrote:
>>> On 7. Feb 2021, at 09:04, Chris  wrote:
>>> On 2021-02-06 13:36, Chris wrote:
 On 2021-02-06 00:56, Toomas Soome wrote:
>> On 6. Feb 2021, at 01:41, Chris  wrote:
>> On 2021-02-05 14:16, Chris wrote:
>>> On 2021-02-05 13:46, Toomas Soome wrote:
> On 5. Feb 2021, at 19:54, Chris  wrote:
> On 2021-01-30 02:28, Toomas Soome wrote:
>>> On 30. Jan 2021, at 10:39, Chris  wrote:
>>> On 2021-01-30 00:03, Toomas Soome wrote:
> On 30. Jan 2021, at 09:40, Chris  wrote:
> On 2021-01-29 22:24, Toomas Soome via openindiana-discuss wrote:
>>> On 30. Jan 2021, at 03:43, Chris  wrote:
>>> On 2021-01-29 17:18, Andy Fiddaman wrote:
 On Fri, 29 Jan 2021, Chris wrote:
 ; OK just dragged a Dell Optiplex 790 off the shelf
 ; with a 4 core 8 thread i5 CPU in it, and as much RAM
 ; as I could jam in it.
 ; BIOS:
 ; boot UEFI
 ; SATA ahci
 ; I've tried 2 different Nvidia cards, as well as the
 ; intermal video. The results are the same;
 ; 2.5 minutes to get to the OI banner/boot options.
 ; An additiona 3.5 to draw the OI banner/options screen.
 ; It takes ~0.5 seconds to draw each cell. To be clear;
 ; I'm not complaining here. Rather, I'm trying to
 ; pinpoint WTF is going wrong in hopes of overcoming
 ; the problem. I've attempted to put OI on 3 different
 ; computers now, and the results have all been
 ; underwhelming in the console dept.
 ;
 ; Any thoughts?
 If you can press  really early in the boot process, 
 you get the
 first loader prompt (I forget exactly how it looks). At that 
 point,
 enter "-t" without the quotes and press return. That will keep 
 in
 VGA mode, which might well be faster/usable.
>>> Huge thanks for the reply, Andy!
>>> Yes, it made a difference. Drawing each cell only takes 0.25
>>> seconds. :-P
>>> So somewhat faster, anyway. It's funny. It starts out quite
>>> fast. The speed I normally experience with other stuff. It
>>> writes
>>> Available consoles:
>>> text VGA ...
>>> ttya port 0x3f8
>>> ttyb ... not present
>>> ttyc ... not present
>>> ttyd ... not present
>>> null software device
>>> spin software device
>>> Right at this point is where it drops to about 1/2 or slower 
>>> speed.
>>> Then, cell by cell, it prints
>>> console ttyb failed to initialize
>>> console ttyc failed to initialize
>>> console ttyd failed to initialize
>> This is the point where you have got hint about why this 
>> happens. The same defect
>> is with virtualbox, when you have configured host pipe for 
>> serial device.
>> The three lines above tell us that ttya was successfully 
>> initialized, so it must
>> have to do about ttya.
> OK I neglected to note that this was including the advice by Andy 
> to drop to
> text mode, by interrupting loader, and entering -t at the prompt 
> followed by
> enter. It's clear that it was attempting serial mode -- note the 
> port 0x3f8
> Without interrupting loader, text and ttya return:
> text VESA (800x600 - 1600x1200 depending on what I'm hooked up to)
> ttya ... not present
> I'm attempting it again via Legacy where
> text VESA 1600x1200
> ttya ... not present
> Choosing 5 (options), followed by 5 (verbose) has already taken 20
> minutes (it's still in progress). I think I'm just going to try to
> install it and work on it further from the internal disk. In hopes
> of getting at least a small speed increase from 0 to actual boot.
> I greatly appreciate your insight on this, Toomas.
 Ok, so this guess was not good one afterall. If you are doing CD 
 (ISO) boot, you
 will get loader started as first stage - that is, there is no way 
 to enter
 options; however, once you get out of menu and on O prompt, you 
 can enter:
 framebuffer off
 on BIOS boot, this will switch to VGA text mode, on UEFI, it will 
 switch terminal
 draw from GOP Blt() to SimpleTe

Re: [OpenIndiana-discuss] What is the equivalent packages on OI?

[cretin1997 via openindiana-discuss]

‐‐‐ Original Message ‐‐‐
On Sunday, February 7, 2021 4:37 PM, Toomas Soome via openindiana-discuss 
 wrote:

> > On 7. Feb 2021, at 09:46, cretin1997 via openindiana-discuss 
> > openindiana-discuss@openindiana.org wrote:
> > They are Ubuntu packages:
> > gcc libncurses5-dev libtinfo5 libffi-dev libgl1-mesa-dev
> > libx11-dev libxext-dev libxrender-dev libxrandr-dev libxpm-dev
> > I searched for packages name using pkg search -rp but it seems I need to 
> > know exact packages name already. It don't list all packages whose names 
> > contain the text like on Q4OS.
>
> man pkg.
>
> pkg search -r libncurses\*
>
> rgds,
> toomas
>
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss

Thank you. So the asterisk works.

BTW, I use pkg search -rp because -r prints too much information. Of course I 
could pipe it to less but it's still too much of the details. I just want the 
packages name.

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] What is the equivalent packages on OI?

[Aurélien Larcher]

-o pkg.name is the option you need.

On Monday, February 8, 2021, cretin1997 via openindiana-discuss <
openindiana-discuss@openindiana.org> wrote:
> ‐‐‐ Original Message ‐‐‐
> On Sunday, February 7, 2021 4:37 PM, Toomas Soome via openindiana-discuss
 wrote:
>
>> > On 7. Feb 2021, at 09:46, cretin1997 via openindiana-discuss
openindiana-discuss@openindiana.org wrote:
>> > They are Ubuntu packages:
>> > gcc libncurses5-dev libtinfo5 libffi-dev libgl1-mesa-dev
>> > libx11-dev libxext-dev libxrender-dev libxrandr-dev libxpm-dev
>> > I searched for packages name using pkg search -rp but it seems I need
to know exact packages name already. It don't list all packages whose names
contain the text like on Q4OS.
>>
>> man pkg.
>>
>> pkg search -r libncurses\*
>>
>> rgds,
>> toomas
>>
>> openindiana-discuss mailing list
>> openindiana-discuss@openindiana.org
>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>
> Thank you. So the asterisk works.
>
> BTW, I use pkg search -rp because -r prints too much information. Of
course I could pipe it to less but it's still too much of the details. I
just want the packages name.
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>

-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss