Arch: linux-grsec isn't booting...

Discussion in 'all things UNIX' started by Anonfame1, Jul 5, 2016.

  1. Anonfame1

    Anonfame1 Registered Member

    Joined:
    May 25, 2016
    Posts:
    198
    Just FYI, the latest version of linux-grsec (version 4.5.7.201606302132-1) doesnt boot on my system. I dont have systemd log to disk, so I dont have anything in journalctl yet. Going to enable persistent logging and then see if anything shows up.

    Thanks to btrfs this wasnt really a problem for me :D

    Any of you guys on Arch have a similar problem with the latest linux-grsec?
     
  2. wat0114

    wat0114 Registered Member

    Joined:
    Aug 5, 2012
    Posts:
    1,985
    Location:
    Canada
    Yep, same problem here on i386 Arch. It appeared to be some sort of nvidia issue. After considerable time struggling with it like pulling teeth, I gave up and ditched grsec.
     
  3. Anonfame1

    Anonfame1 Registered Member

    Joined:
    May 25, 2016
    Posts:
    198
    Well, I know it isnt just my system now. I rolled back to a prior version for now.

    What led you to believe it was an nvidia problem btw? I have an nvidia card but have it disabled in UEFI (optimus laptop); all the operating system sees is my intel card. I dont even get console output indicating the kernel is trying to boot so it seems yours is getting further than mine is.

    If its more than just you and I, Ill submit a bug report via flyspray and see what happens.
     
  4. wat0114

    wat0114 Registered Member

    Joined:
    Aug 5, 2012
    Posts:
    1,985
    Location:
    Canada
    It was some sort of "denial RWX nmap of libnvidia-glcore.so.364.19..." error I was getting upon boot. It was at this point the boot process would freeze.
     
  5. linuxforall

    linuxforall Registered Member

    Joined:
    Feb 6, 2010
    Posts:
    2,136
    Stick to nouveau if you intend to use grsec, both work without issues.
     
  6. Anonfame1

    Anonfame1 Registered Member

    Joined:
    May 25, 2016
    Posts:
    198
    Not for me. Im using the intel driver and it hard locks upon boot. I dont even get any console output to indicate where the problem happens.

    Ill have to look into it tomorrow night.
     
  7. linuxforall

    linuxforall Registered Member

    Joined:
    Feb 6, 2010
    Posts:
    2,136
    Is this with new Intel driver thats been released recently, I would wait for repos to update then.
     
  8. Anonfame1

    Anonfame1 Registered Member

    Joined:
    May 25, 2016
    Posts:
    198
    Wait for the repos to update what? Im using the intel driver released on July 5th, and the kernel released on July 4th. Curiously, the name of the linux-grsec kernel includes a version number that suggests it was built June 30th.

    Anyways, when persistent logging is enabled, I dont get a single message. Ive tried compiling the kernel myself and using the one straight from the mirrors- both the same result. Unfortunately it seems this is unique to my system- wat014's problem seems to be later in the boot process and I see no bug report from someone else with this issue (as of last night).

    The confounding thing is prior kernels work completely fine. Im going to try uninstalling the intel driver and everything in xorg.conf.d to make sure it isnt some video bug.
     
  9. Anonfame1

    Anonfame1 Registered Member

    Joined:
    May 25, 2016
    Posts:
    198
    Fixed. The latest 4.6.3 build of linux-grsec boots no problem. I dont know what was up with the last one- probably something related to the specific grsecurity patchset used when the maintainer built the above one that failed.

    There might be more of this kind of thing now that grsecurity has locked out its stable patchset to customers only. Gentoo/Arch/Debian is forced to use the testing patchset which is bound to have more bugs.
     
Loading...