Re: [OpenIndiana-discuss] BTX halted

2018-03-20 Thread Priyadarshan via openindiana-discuss 

On 2018-03-20 11:03, bscuk2 wrote:

Hi,

I came across this post which may help.

Robert

https://unix.stackexchange.com/questions/294364/btx-halted-when-i-trying-to-install-freebsd-10-3-on-my-notebook-i-got-this-mess



Hello Robert,

Thank you for the pointer. I did try "burning" the image to various USB 
sticks, and verifying the SHA sum.


Also, the same stick was booting fine on a ThinkPad.

I feel now that it could be some subtle mismatch between current 
bootloader and firmaware in use on the workstations.


I have not stopped trying though.

I am just waiting for upcomig OpenIndiana April release, hoping it will 
bring UEFI boot (one can always hope), and those issues will go away.


I am itching to become a more active contributor to OpenIndiana, perhaps 
some contributions to docs and userland.


But until I have a properly working OI on workstations too I do not feel 
confident enough.


Thank you again,

Priyadarshan



On 08/03/2018 15:54, Priyadarshan via openindiana-discuss wrote:

Hi,

I have successfully installed OpenIndiana Hipster 2017.10 Live via USB 
image on a ThinkPad W541.


Now, I am trying to install to 2 different workstations, using same 
USB stick:


- HP z620 with Xeon E5
- Asus X399 motherboard with AMD 1950X Threadripper

After a few seconds, both machines give same message "BTX halted"

See screehsots https://imgur.com/a/pXMKn

I tried setting BIOS to legacy mode and UEFI mode.

Right now both machines are running FReeBSD 11.1-RELEASE.

From both, I am able to boot a FreeBSD installer, both in legacy mode 
and UEFI mode.


I wonder why it boots fine from the ThinkPad, and not from the other 2 
machines.


Is there anything I need to do in order to have the image boot?

Priyadarshan

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


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

Re: [OpenIndiana-discuss] BTX halted

2018-03-20 Thread Francis.D 
hi,

On your Lenovo W541 did you test the sound?
Does the sound work fully for you  on realtek HD driver ?


Because for me on all my installation the sound doesn't work properly.
I've already posted on the channel but there doesn't seem to be a solution
that works.
So I'm curious about the sound experience of other users

regard

2018-03-20 6:03 GMT-04:00 bscuk2 :

> Hi,
>
> I came across this post which may help.
>
> Robert
>
> https://unix.stackexchange.com/questions/294364/btx-halted-
> when-i-trying-to-install-freebsd-10-3-on-my-notebook-i-got-this-mess
>
> On 08/03/2018 15:54, Priyadarshan via openindiana-discuss wrote:
>
>> Hi,
>>
>> I have successfully installed OpenIndiana Hipster 2017.10 Live via USB
>> image on a ThinkPad W541.
>>
>> Now, I am trying to install to 2 different workstations, using same USB
>> stick:
>>
>> - HP z620 with Xeon E5
>> - Asus X399 motherboard with AMD 1950X Threadripper
>>
>> After a few seconds, both machines give same message "BTX halted"
>>
>> See screehsots https://imgur.com/a/pXMKn
>>
>> I tried setting BIOS to legacy mode and UEFI mode.
>>
>> Right now both machines are running FReeBSD 11.1-RELEASE.
>>
>> From both, I am able to boot a FreeBSD installer, both in legacy mode and
>> UEFI mode.
>>
>> I wonder why it boots fine from the ThinkPad, and not from the other 2
>> machines.
>>
>> Is there anything I need to do in order to have the image boot?
>>
>> Priyadarshan
>>
>> ___
>> openindiana-discuss mailing list
>> openindiana-discuss@openindiana.org
>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>>
>
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] BTX halted

2018-03-20 Thread bscuk2 

Hi,

I came across this post which may help.

Robert

https://unix.stackexchange.com/questions/294364/btx-halted-when-i-trying-to-install-freebsd-10-3-on-my-notebook-i-got-this-mess

On 08/03/2018 15:54, Priyadarshan via openindiana-discuss wrote:

Hi,

I have successfully installed OpenIndiana Hipster 2017.10 Live via USB 
image on a ThinkPad W541.


Now, I am trying to install to 2 different workstations, using same 
USB stick:


- HP z620 with Xeon E5
- Asus X399 motherboard with AMD 1950X Threadripper

After a few seconds, both machines give same message "BTX halted"

See screehsots https://imgur.com/a/pXMKn

I tried setting BIOS to legacy mode and UEFI mode.

Right now both machines are running FReeBSD 11.1-RELEASE.

From both, I am able to boot a FreeBSD installer, both in legacy mode 
and UEFI mode.


I wonder why it boots fine from the ThinkPad, and not from the other 2 
machines.


Is there anything I need to do in order to have the image boot?

Priyadarshan

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



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

Re: [OpenIndiana-discuss] BTX halted

2018-03-10 Thread Priyadarshan via openindiana-discuss 

An update (posted on Issue tracker as well):

I spent several hours yesterday and today, playing around with bios 
settings on both machines.


It seems there is no much hope with Asus X399 motherboard, even 
switching to bios-Legacy mode and disabling ACPI.


I had more success with the HP Z620 (late 2012 model).

By setting bios SATA to IDE compatibility mode, the OpenIndiana Live USB 
finally booted.


That system is running a Xeon E5 1650, with no builtin graphics, but it 
has an nvidia GeForce card.


After a few seconds, lightdm fails, and issue message "default failed: 
transitioned to maintenance". Then I am dropped in openindiana console 
login.


Still, I finally got to boot!

But, there is another issue:

Unfortunately, when I booted the Live USB image, it forced the HP Z620 
worstation, which was fine booting FreeBSD via UEFI, to Bios-legacy 
mode, effectively botching the boot disk.


Mind you, I was not installing it. Just the mere running of the Live USB 
image changed the boot setup to legacy mode and leaving a boitched 
FreeBSD install.


Unfortunately, we do not have any non-UEFI machines here, so I will need 
to wait to play more with OI when UEFI install image will be available.


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

Re: [OpenIndiana-discuss] BTX halted

2018-03-09 Thread Priyadarshan via openindiana-discuss 

On 2018-03-09 15:14, Bob Pasken wrote:


Hi,

I have successfully installed OpenIndiana Hipster 2017.10 Live via USB
image on a ThinkPad W541.

Now, I am trying to install to 2 different workstations, using same 
USB

stick:

- HP z620 with Xeon E5
- Asus X399 motherboard with AMD 1950X Threadripper

After a few seconds, both machines give same message "BTX halted"

See screehsots https://imgur.com/a/pXMKn

I tried setting BIOS to legacy mode and UEFI mode.

Right now both machines are running FReeBSD 11.1-RELEASE.

  From both, I am able to boot a FreeBSD installer, both in legacy 
mode

and UEFI mode.

I wonder why it boots fine from the ThinkPad, and not from the other 2
machines.

Is there anything I need to do in order to have the image boot?




There are also problems with the FreeBSD bootloader on SunFire
X4600's, Sun Ultra-40's and Sun Ultra-20's that are somewhat related.
Toomas Soome has a fix, but it hasn't been put into OI yet



Hello Bob,

Thank you, your words are somehow consoling.

I have spent many hours yesterday and today, trying different methods, 
beside follwoing the instructions here: 
http://docs.openindiana.org/handbook/getting-started/


creating the USB stick using different OS: Win, OSX, Linux.

I even tried using UNetbootin, and "burning" the iso image to a USB 
stick.


Both machines do start the boot process. I can see the cursor spinning.

But, right after a few seconds, all methods fails with "BTX halted", as 
screenshots here: https://www.illumos.org/issues/9254


Thank you, I guess I will wait, hoping the FreeBSD bootloader will 
improve with next version of OpenIndiana.


Priyadarshan

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

Re: [OpenIndiana-discuss] BTX halted

2018-03-09 Thread Priyadarshan via openindiana-discuss 

On 2018-03-08 16:54, Priyadarshan via openindiana-discuss wrote:

Hi,

I have successfully installed OpenIndiana Hipster 2017.10 Live via USB
image on a ThinkPad W541.

Now, I am trying to install to 2 different workstations, using same USB 
stick:


- HP z620 with Xeon E5
- Asus X399 motherboard with AMD 1950X Threadripper

After a few seconds, both machines give same message "BTX halted"

See screehsots https://imgur.com/a/pXMKn

I tried setting BIOS to legacy mode and UEFI mode.

Right now both machines are running FReeBSD 11.1-RELEASE.

From both, I am able to boot a FreeBSD installer, both in legacy mode
and UEFI mode.

I wonder why it boots fine from the ThinkPad, and not from the other 2 
machines.


Is there anything I need to do in order to have the image boot?


After trying with different options and different USB sticks, I have 
opened ticket here: https://www.illumos.org/issues/9254


I am hoping it is a boot loader issue that will be fixed in next 
OpenIndiana release.



Priyadarshan

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

Re: [OpenIndiana-discuss] BTX halted

2017-05-10 Thread Jim Klimov 
On May 6, 2017 2:12:18 PM GMT+03:00, Jim Klimov  wrote:
>On May 6, 2017 10:33:31 AM GMT+03:00, Nikola M 
>wrote:
>>On 05/ 6/17 01:38 AM, Jim Klimov wrote:
>>> Second, did the friend try the recent 2017.04 release of OI Hipster
>>(out this week)?
>>>
>>> Finally, AFAIK each snapshot "release" includes the latest (at its
>>time)  illumos-gate OS/Net "kernel" parts that work for some HW and
>>might not work for others - especially if noone tried it before so
>>there was nothing to fix or improve.
>>
>>2017 test snapshot (not a 'release', there are no 'releases' per se)
>is
>>unbootable on ACPI v1 PC that used to boot previously. I tried both
>>text
>>install and Live/GUI USB image.
>>Message: "No rootfs module provided, aborting" and ends up in 'ok'
>>prompt.
>>(This could also be related to not booting on older amd64 machines)
>>
>>Bug with loader about ACPI1 is fixed by tsoome in illumos and landed,
>>but even being informed on IRC, illumos used for test OI snapshot
>used,
>>illumos without a bug fix.
>>As I understand that OI snapshot is not final, and is there for
>>preview.
>>
>>On positive side, updating to current
>>osnet-incorporation@0.5.11-2017.0.0.16382 from previous install works
>>and system boots.
>>There is still an issue with Power button present on lightdm login
>>screen by default, that allows unauthorized persons to restarts or
>shut
>>down machine, without previously being identified and loggeed in, that
>>present security issue:
>>
>>Also, hostname on lightdm login screen is in the wrong uncentered
>>place:
>>https://www.illumos.org/issues/8111
>>and lightdm login screen allows unauthorized restart and shutdown by
>>default:
>>https://www.illumos.org/issues/8167
>>Workaround is to put: "indicators=~a11y;~spacer;~host;~session;~clock"
>>in /etc/lightdm/lightdm-gtk-greeter.conf  , that should be default.
>>
>>There are still other errors regarding ZFS pool on another drive,
>>somehow being read even that pool is long time zpool destroy, zdb
>>labelclear , and whole drive filled with dd, but that is I suppose the
>>other, also recently added bug, not related to boot.
>>
>>I see 201704 'release notes' are out there but I think that 20150502
>is
>>testing and not the snapshot that is considered 201704 snapshot, still
>>and there is the time to recompile illumos for it, remove power button
>>security issue and test.
>>
>>
>>___
>>openindiana-discuss mailing list
>>openindiana-discuss@openindiana.org
>>https://openindiana.org/mailman/listinfo/openindiana-discuss
>
>By the way, as another checkpoint - my VirtualBoxed installation on the
>laptop (still with GRUB) was pkg-updated early last weekend (and worked
>after reboot), and then on 3rd morning - and failed to boot. I ended up
>with a blank screen where X11 should've started. Logging in on the
>serial console, I saw that some networking services were disabled that
>I think should have been running, and a couple were in maintenance. I
>enabled and cleared those, rebooted - but still had no GUI (although no
>unexpected not-online services now).
>
>We were running off for a trip, so I had no time to write down the
>details or investigate, and I'll next see that laptop next week
>probably. My guess is that in the couple of days the Xorg changes had
>landed and perhaps just a reinstall (recompile) of Vbox guest additions
>might fix things; but without digging I can't rule out something more
>sinister yet ;)
>
>So just anecdotal experience from a single experiment, at the moment. 
>
>Jim
>--
>Typos courtesy of K-9 Mail on my Redmi Android

Following up with anecdotal experience, now I've got hands on the laptop, and 
reinstalled vbox guest additions package in the new BE fixed the presence of 
GUI ;)

Jim
--
Typos courtesy of K-9 Mail on my Redmi Android

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

Re: [OpenIndiana-discuss] BTX halted

2017-05-06 Thread Nikola M 
On 05/ 6/17 01:12 PM, Jim Klimov wrote:
> On May 6, 2017 10:33:31 AM GMT+03:00, Nikola M  wrote:
>
>> I see 201704 'release notes' are out there but I think that 20150502 is
>> testing and not the snapshot that is considered 201704 snapshot, still
>> and there is the time to recompile illumos for it, remove power button
>> security issue and test.
Here should be 20170502 test snapshot, not 2015.. of course. ;)
> By the way, as another checkpoint - my VirtualBoxed installation on the 
> laptop (still with GRUB) was pkg-updated early last weekend (and worked after 
> reboot), and then on 3rd morning - and failed to boot. I ended up with a 
> blank screen where X11 should've started. 

Check if you maybe have too many Boot Environments for GRUB to handle
and also, there is a mention that VirualBoox guest add-ons need
reinstallation.

> Logging in on the serial console, I saw that some networking services were 
> disabled that I think should have been running, and a couple were in 
> maintenance. I enabled and cleared those, rebooted - but still had no GUI 
> (although no unexpected not-online services now).

I have failure to restart lightdm service in recent few months, but it
fails to start just after being in long session for some time (fails to
start after logout), but restarts if just re-logging.
Don't know if it is related, but I got some lines in log that point to
some Nvidia driver failure, could be connected with something similar in
VirtualBox?
Mine is able to start after full restart, even it holds and stay there
frozen on restart and shutdow, in does restart/shutdown.

[ 55936.338] (EE) NVIDIA(GPU-0): EVO Push buffer channel allocation failed
[ 55936.339] (EE) NVIDIA(GPU-0): Failed to allocate EVO core DMA push buffer
[ 56025.101] (EE) NVIDIA(0): Failing initialization of X screen 0
in application-graphical-login-lightdm:default.log
and several
[ 55930.626] compiled for 1.18.4, module version = 1.0.0
in Xorg.0.log
(could be that nvidia driver is not set for newer environment and not
targeted for OI)
> We were running off for a trip, so I had no time to write down the details or 
> investigate, and I'll next see that laptop next week probably. My guess is 
> that in the couple of days the Xorg changes had landed and perhaps just a 
> reinstall (recompile) of Vbox guest additions might fix things; but without 
> digging I can't rule out something more sinister yet ;)
>
> So just anecdotal experience from a single experiment, at the moment. 
I suppose so.
Btw, my booting problem is reproducible only on ACPI v1 machines and
only on hardware, but I suppose many people still have those nice older
64bit machines working, so ISOs ned to be changed not to loose many
people's new installations.

When venting and discussing in getneral already,
main issue is that people should not hasitate to report their bugs as
soon as they appear and do that 'en masse'. Only way anything to be
fixed is to report it ASAP, not waiting. For example, during /hipster
repository updates, from one OI snapshot to another, one can surf
through osnet-incorporation and userland-incorporation incorporations,
to find out _when_ certain bug first appeared.
But after the OI snapshot, those previous states are gone/deleted, to
free disk space, to speed up IPS/pkg(5) operations, to lower RAM usage
for pkg, so not any bug reporting is too soon. :)

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

Re: [OpenIndiana-discuss] BTX halted

2017-05-06 Thread Jim Klimov 
On May 6, 2017 10:33:31 AM GMT+03:00, Nikola M  wrote:
>On 05/ 6/17 01:38 AM, Jim Klimov wrote:
>> Second, did the friend try the recent 2017.04 release of OI Hipster
>(out this week)?
>>
>> Finally, AFAIK each snapshot "release" includes the latest (at its
>time)  illumos-gate OS/Net "kernel" parts that work for some HW and
>might not work for others - especially if noone tried it before so
>there was nothing to fix or improve.
>
>2017 test snapshot (not a 'release', there are no 'releases' per se) is
>unbootable on ACPI v1 PC that used to boot previously. I tried both
>text
>install and Live/GUI USB image.
>Message: "No rootfs module provided, aborting" and ends up in 'ok'
>prompt.
>(This could also be related to not booting on older amd64 machines)
>
>Bug with loader about ACPI1 is fixed by tsoome in illumos and landed,
>but even being informed on IRC, illumos used for test OI snapshot used,
>illumos without a bug fix.
>As I understand that OI snapshot is not final, and is there for
>preview.
>
>On positive side, updating to current
>osnet-incorporation@0.5.11-2017.0.0.16382 from previous install works
>and system boots.
>There is still an issue with Power button present on lightdm login
>screen by default, that allows unauthorized persons to restarts or shut
>down machine, without previously being identified and loggeed in, that
>present security issue:
>
>Also, hostname on lightdm login screen is in the wrong uncentered
>place:
>https://www.illumos.org/issues/8111
>and lightdm login screen allows unauthorized restart and shutdown by
>default:
>https://www.illumos.org/issues/8167
>Workaround is to put: "indicators=~a11y;~spacer;~host;~session;~clock"
>in /etc/lightdm/lightdm-gtk-greeter.conf  , that should be default.
>
>There are still other errors regarding ZFS pool on another drive,
>somehow being read even that pool is long time zpool destroy, zdb
>labelclear , and whole drive filled with dd, but that is I suppose the
>other, also recently added bug, not related to boot.
>
>I see 201704 'release notes' are out there but I think that 20150502 is
>testing and not the snapshot that is considered 201704 snapshot, still
>and there is the time to recompile illumos for it, remove power button
>security issue and test.
>
>
>___
>openindiana-discuss mailing list
>openindiana-discuss@openindiana.org
>https://openindiana.org/mailman/listinfo/openindiana-discuss

By the way, as another checkpoint - my VirtualBoxed installation on the laptop 
(still with GRUB) was pkg-updated early last weekend (and worked after reboot), 
and then on 3rd morning - and failed to boot. I ended up with a blank screen 
where X11 should've started. Logging in on the serial console, I saw that some 
networking services were disabled that I think should have been running, and a 
couple were in maintenance. I enabled and cleared those, rebooted - but still 
had no GUI (although no unexpected not-online services now).

We were running off for a trip, so I had no time to write down the details or 
investigate, and I'll next see that laptop next week probably. My guess is that 
in the couple of days the Xorg changes had landed and perhaps just a reinstall 
(recompile) of Vbox guest additions might fix things; but without digging I 
can't rule out something more sinister yet ;)

So just anecdotal experience from a single experiment, at the moment. 

Jim
--
Typos courtesy of K-9 Mail on my Redmi Android

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

Re: [OpenIndiana-discuss] BTX halted

2017-05-06 Thread Apostolos Syropoulos via openindiana-discuss 
My friend has used the latest bits. Now aboutthe USB 3 thing, I think you did 
the right thing.But the real problem that the driver shouldn'tbe part of 
illumos-gate simply because itis not ready! I have asked people to tell mehow 
can I help testing  the driver but nooneresponded! I tried the experimental ISO 
andwhen I reported to the maintainer that thedriver is not working, he told me 
that thiswas a very experimental thing and the newbits should work BTW is 
there someonewho could report a success story I someonewho have tested the 
driver on hardware whereit actually works?
Apostolos
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] BTX halted

2017-05-05 Thread Jim Klimov 
On May 5, 2017 4:41:20 PM GMT+03:00, Apostolos Syropoulos via 
openindiana-discuss  wrote:
>A friend of mine has an Apple MacBook Pro Retina (4k) andhe would like
>to install OpenIndiana on it. For some reason,it is next to impossible
>to boot the system from a DVD. Sohe tried to boot OI from a USB flash
>disk. The system stopswith the message BTX halted and the screen looks
>like this
>https://imgur.com/ZgFKWhs
>I have checked on the Web this machine and it seems it hasUSB 3 ports.
>From my own experience the USB 3 support isbroken, so does it make
>sense to assume that the system cannot boot because of the broken USB 3
>support? BTW, Ithink that hipster is quite experimental yet the new
>Xorgbits work just fine. I have tested on systems with NVIDIAcards, ATI
>RADEON, and Intel and all work just fine. however,why did you include
>the completely broken USB 3 support?
>A.S.
>
>--
>Apostolos Syropoulos
>Xanthi, Greece
>___
>openindiana-discuss mailing list
>openindiana-discuss@openindiana.org
>https://openindiana.org/mailman/listinfo/openindiana-discuss

Hello,

First of all - i've got no experience with modern Mac hardware so anyone *with* 
experience is more authoritative on this stage ;)

Second, did the friend try the recent 2017.04 release of OI Hipster (out this 
week)?

Finally, AFAIK each snapshot "release" includes the latest (at its time)  
illumos-gate OS/Net "kernel" parts that work for some HW and might not work for 
others - especially if noone tried it before so there was nothing to fix or 
improve.

Jim
--
Typos courtesy of K-9 Mail on my Redmi Android

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