On Mon, Jul 31, 2017 at 1:46 PM, Igor Kozhukhov <ikozhuk...@gmail.com> wrote:
> for these issues i’d like recommend prepare and use some images with DEBUG > illumos and probably boot menu with -kvd > where you can see panic and more info if beet process failed. > > just like idea. > Yes that would be a good idea to have a minimal debug image for diagnostics. > > and - it is hardly to say more info without access to hw, but not at all > hw has remote access like IPMI - and it is hardly debug with with monitor > only. > Indeed :) but better than just posting complaints without trying to fix the issues. Thank you ;) > > -Igor > > > Hi, > again Michael Larabel attempted a review and could boot on his hardware: > > http://phoronix.com/scan.php?page=news_item&px=OpenIndiana-7900X-Hipster > > Obviously, instead of contacting us, he wrote directly an article to state > the fact. > > Last time this happened I contacted him to find out what caused the > problem but he never reached back. What can we do about it? > > Kind regards > > Aurelien > > > It needs 3 things - hardware, engineer and time. AFAIK right now there are > 2 companies behind illumos who have more direct relations with hardware - > Joyent and Nexenta and those companies are still most likely interested > about the server class hardware. > > Anything else is really about the community - if anyone has such hardware > and is willing to help with diagnostics and testing, then we can do > something, otherwise... > > rgds, > toomas > _______________________________________________ > oi-dev mailing list > oi-dev@openindiana.org > https://openindiana.org/mailman/listinfo/oi-dev > > > > _______________________________________________ > oi-dev mailing list > oi-dev@openindiana.org > https://openindiana.org/mailman/listinfo/oi-dev > -- --- Praise the Caffeine embeddings
_______________________________________________ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
