*Bug 575* <https://issues.openmandriva.org/show_bug.cgi?id=575> - Installing
proprietary drivers from nvidia: Regression

Please provide some more information (dkms logs, journalctl -f -n 100
etc.), because this is not needed to get any clue what could be wrong.




2014-03-21 13:34 GMT+01:00 <[email protected]>:

>  Report of tests
>
>
> https://drive.google.com/file/d/0B6QC6kfs4JvUU0FoLTM0dk56VVE/edit?usp=sharing
>
>
>
> it is much better, but we have still problem with nvidia proprietary
> installation
>
> *Bug 575* <https://issues.openmandriva.org/show_bug.cgi?id=575> - Installing
> proprietary drivers from nvidia: Regression
>
>
>
> And we have problem to manage double monitor during installation and also
> after first reboot,
>
> now I'm going to report a new bug but if someone can check is better
>
> I found visualizzation problem during installation process but also a
> problem with the mouse pointer that is missing
>
> (please note that if a perform the installation with one only monitor all
> is OK)
>
>
>
> first tentative of Live boot on EliteBook 8560W was OK but with the *terrible
> beep* always on
>
> but this time after next tentative of boot all was always OK....
>
>
>
> Regards
>
>
>
> ---
>
> Davide_01http://www.linux-corner.it
>
>  Il 2014-03-21 02:39 Rolf Pedersen ha scritto:
>
> Hi,
>
> On 03/20/2014 01:58 PM, Tomasz Paweł Gajc wrote:
>
> Hello, after a long time spent on fixing bug
> https://issues.openmandriva.org/show_bug.cgi?id=578 finally with
> engagement of few fellow cookers finally we can build a bootable iso. So
> here you are: 64 bit:
> https://abf.io/platforms/openmandriva2014.0/products/70/product_build_lists/2989
>
> For verified 2989 iso and verified burn to dvd, I get no boot.  I tried
> several iterations of the default install menu item, one for the live
> session, one for basic graphics.  AFAICT, they all get through initial
> boot messages and end in a black screen, keyboard, eventually, dead.
> Where I removed splash=silent, I saw the login prompt, where keyboard
> was operational.  Shortly after that, apparently while X is started and
> after about the same time in all the attempts, the keyboard goes dead
> and stays there, up to 10 minutes I waited once, and a reset is
> necessary.  One boot, with no apparent difference, I added the commands
> advised from a bit earlier post:
>
> debug quiet plymouth.enable=0 systemd.log_level=debug
> systemd.log_target=kmsg log_buf_len=1M
>
> I once tried nokmsboot.  An attached text file of inxi -F output shows
> some hardware information.
> Thanks,
> Rolf
>
>
>
>
>
>
>
>


Reply via email to