STEAM GROUP
Steam Universe Steam U
STEAM GROUP
Steam Universe Steam U
49,689
IN-GAME
343,441
ONLINE
Founded
September 23, 2013
All Discussions > Steam OS > Topic Details
Thrice_G Jan 22, 2014 @ 10:16pm
How to use rc.local to load "module" on start up?
Hi,

I installed the latest "Ye Olde SteamOSe" on my system yesterday and spent the entire day trying to get it running properly. Apparently SteamOS isn't the real culprit though. My motherboard has a compatibility issue with linux that prevents my onboard networking adapter from working and also causes my PC to freeze during shutdown or reboot. I found out that the only work around was to to either run a command in recovery mode or input a command into rc.local (and a kmod file, but that worked fine) in order to launch the command during boot. The first method works, but the second one doesn't work.

I googled the issue and found a site that implied that rc.local doesn't work in debian. What can I do to get it to work?

additional details:
The command that I'm trying to run via rc.local is:

modprobe forcedeth msi=0 msix=0

Also, here's a link to a bug report that details my problem:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1003297

Motherboard:
http://www.asrock.com/mb/NVIDIA/N68-VS3%20FX/?cat=Specifications

I know this question is probably more appropriate for a debian forum but I figured I'd post this question in both locations to help my chances.

If you need more details, please let me know. Thanks.
< >
Showing 1-8 of 8 comments
ecliptik Jan 22, 2014 @ 10:43pm 
/etc/rc.local is called by the /etc/init.d/rc.local init script which should work on Wheezy. You can make sure that the rc.local init script is started with:

sudo update-rc.d rc.local defaults

Make sure /etc/rc.local is executable too.
Thrice_G Jan 22, 2014 @ 11:24pm 
Originally posted by ecliptik:
/etc/rc.local is called by the /etc/init.d/rc.local init script which should work on Wheezy. You can make sure that the rc.local init script is started with:

sudo update-rc.d rc.local defaults

Make sure /etc/rc.local is executable too.
I ran your command and got this output:

desktop@steamos:~$ sudo update-rc.d rc.local defaults
[sudo] password for desktop:
update-rc.d: using dependency based boot sequencing
update-rc.d: warning: default stop runlevel arguments (0 1 6) do not match rc.local Default-Stop values (none)
desktop@steamos:~$


What happened?
Balderick Jan 23, 2014 @ 2:24am 
You are being told to edit the two files so that they both have the same default stop runlevel arguments.
update-rc.d: warning: default stop runlevel arguments (0 1 6) do not match rc.local Default-Stop values (none)

You need to edit the rc.local file adding (016) to the Default-Stop value section.


Alternatively you could try what is suggested at comment #5 of the link you shared[bugs.launchpad.net]
Last edited by Balderick; Jan 23, 2014 @ 2:33am
tarvoke Jan 23, 2014 @ 7:29am 
assuming the module is being auto loaded in the first place, why not simply create a file e.g. /etc/modprobe.d/forcedeth.conf containing the line:
options forcedeth msi=0 msix=0
Thrice_G Jan 23, 2014 @ 7:28pm 
Originally posted by 40-1PvtBalderick:
You are being told to edit the two files so that they both have the same default stop runlevel arguments.
update-rc.d: warning: default stop runlevel arguments (0 1 6) do not match rc.local Default-Stop values (none)

You need to edit the rc.local file adding (016) to the Default-Stop value section.

I'm actually very confused now. In the /etc/rc.local has no "Default-Stop value" section whatsoever, so I'm not sure what exactly I'm supposed to alter and where. Here's what it looks like now:

http://pastebin.com/6KyPMWWX

The /etc/init.d/rc.local init file did contain something about "Default-Stop" but, correct me if I'm wrong, doesn't the # symbol denote that the line is a comment? I added the zero anyways, but I'm pretty sure it's not doing anything. Here's how it looks:

http://pastebin.com/vZLvkr5a

All i need to know is what to edit.
Thrice_G Jan 23, 2014 @ 7:39pm 
Originally posted by tarvoke:
assuming the module is being auto loaded in the first place, why not simply create a file e.g. /etc/modprobe.d/forcedeth.conf containing the line:
options forcedeth msi=0 msix=0

You mean like what this[ubuntuforums.org] guy did? I assumed it wouldn't work, but I'll give it a try.
Thrice_G Jan 23, 2014 @ 11:30pm 
Alright, I tried creating the forcedeth.conf file and I'm glad to report that it fixed the problem.

Thanks guys.
JamieLinux Jan 24, 2014 @ 1:00am 
wish debian and steam os would migrate to upstart :P I know the code is gpl but they have to sign an agreement to push changes to upstream but the pros outweigh the cons.
< >
Showing 1-8 of 8 comments
Per page: 1530 50

All Discussions > Steam OS > Topic Details
Date Posted: Jan 22, 2014 @ 10:16pm
Posts: 8