New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gpm not started in grml-2017-05 #76

Closed
leo-b opened this Issue Sep 28, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@leo-b

leo-b commented Sep 28, 2017

gpm doesn't start correctly on my system.
grml-autoconfig seems to run at startup and it even shows [ OK ] Started Grml boot option support.. (See below.)

Running systemctl start grml-autoconfig.service a second time doesn't work either but systemctl start gpm does.

It looks like running service_wrapper gpm start >>$DEBUG & in the background seems to be the problem:

https://github.com/grml/grml-autoconfig/blob/master/autoconfig.functions#L1217

Changing that line to...

      service_wrapper gpm start >>$DEBUG

... fixes the problem for me.

Cheers,
--leo

[  OK  ] Reached target Basic System.
         Starting Grml boot option support...
         Starting Login Service...
         Starting Permit User Sessions...
[  OK  ] Started Permit User Sessions.
[  OK  ] Started D-Bus System Message Bus.
[  OK  ] Started Login Service.
[  OK  ] Found device 82567LM-3 Gigabit Network Connection.
[  OK  ] Started ifup for eth0.
[  OK  ] Reached target Sound Card.
[  OK  ] Starting rsyslog in background.
[  OK  ] Activating language settings:
[  OK  ] Listening on Syslog Socket.
         Starting System Logging Service...
[  OK  ] Writing language settings (en) to /etc/default/locale was successful.
[  OK  ] Setting up unicode environment.
[  OK  ] Started System Logging Service.
[  OK  ] Running loadkeys for de-latin1-nodeadkeys in background
[  OK  ] Setting font to Uni3-Terminus16
[  OK  ] Running Linux Kernel 4.9.0-1-grml-amd64
[  OK  ] CPU(s) featuring virtualization technology detected
[  OK  ] Creating /etc/mdadm/mdadm.conf for use with mdadm.
[  OK  ] Just run 'mdadm --assemble --scan' to assemble md arrays or boot using 'swraid' as bootoption for autostart.
[  OK  ] Searching for any present dmraid sets:
[  OK  ] No active dmraid devices found
[  OK  ] You seem to have logical volumes (LVM) on your system.
[  OK  ] Just run 'Start lvm2-pvscan@name' to activate LV or VG 'name' or boot using 'lvm' as bootoption for autostart.
[  OK  ] Found CPU:
        Processor 0 is Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz 3000MHz, 6144 KB Cache
        Processor 1 is Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz 2000MHz, 6144 KB Cache
[  OK  ] Trying to set up cpu frequency scaling:
         Starting LSB: Load kernel modules needed to enable cpufreq scaling...
[  OK  ] Started LSB: Load kernel modules needed to enable cpufreq scaling.
[  OK  ] Setting ondemand governor
[  OK  ] Searching for device(s) labeled with GRMLCFG. (Disable this via boot option: noautoconfig)
[  OK  ] Configuring soundcard "Intel"
[  OK  ] Setting mixer volumes to level 75.
[  OK  ] Configuring soundcard "HDMI"
[  OK  ] Setting mixer volumes to level 75.
[  OK  ] Starting gpm in background.
[  OK  ] Started Grml boot option support.
[  OK  ] Started grml-quickconfig on tty1.
[  OK  ] Reached target Login Prompts.
[  OK  ] Reached target Grml Live System.
@mika

This comment has been minimized.

Show comment
Hide comment
@mika

mika Sep 29, 2017

Member

Thanks @leo-b for reporting and also debugging this. I plan to include the suggested fix, though need to investigate what happens in the non-systemd situation then, will do so ASAP, thanks!

Member

mika commented Sep 29, 2017

Thanks @leo-b for reporting and also debugging this. I plan to include the suggested fix, though need to investigate what happens in the non-systemd situation then, will do so ASAP, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment