Gnome + ndiswrapper driver conflict... info on Ubuntu startup scripts?

Asked by malignor

I need modify whatever script runs before gdm and after gdm. This is necessary because of a conflict with ndiswrapper and the driver for the W8300 wireless network chip, which causes Gnome to freeze/sieze on startup if the driver is enabled. The driver/ndiswrapper can be enabled once Gnome is up, and also works before Gnome starts, so I'd like to modify whatever scripts are applicable to disable ndiswrapper for that brief window of time, while Gnome fires up.

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Emil Sørbrøden (bernie93) said :
#1

Hi there!

I had the exact same problem, so here is what i did

It is not a great solution, but it works...

open a gedit window, and insert this text:

sudo ndiswrapper -r mrv8k51
sudo shutdown -P 0

then open a command line and use

chmod 755 shutdownscriptfilename

then right click on the desktop and click "create launcher".
Click browse and select your script. Now when you want to shut down your computer ALWAYS use THIS link! That way you will be able to start your pc again normally.
You do however have to use ndis-gtk every time you restart your computer to have wireless internet. This is a temporary solution, so it is not perfect but it works for me

Revision history for this message
malignor (malignor-shaw) said :
#2

I saw your solution on the forums, and it's pretty useful.
What I'm looking for, however, is an automated solution, and I think it lies in the order of the scripts Ubuntu runs upon login... and where Gnome fits in there.

Revision history for this message
Philip Muškovac (yofel) said :
#3

I'm not sure since I don't use ndiswrapper, but here a few points you could start searching:

ndiswrapper configuration should be in /etc/ndiswrapper

maybe the module gets loaded automatically in /etc/modules

the system services are managed in /etc/init.d/ - DO NOT EDIT ANYTHING HERE
instead the startup scripts are managed in /etc/rcX.d/ [X stands for 0-6|S] the default runlevel for ubuntu is 2 so you want to edit the files in rc2.d. The files in there are symbolic links to the scripts in init.d prefixed with an S for start or K for stop and a number to identify the order the services should be started.

Also there is the file /etc/rc.local where you can insert your own system confiiguration commands. (It's called on startup by S99rc.local in rc2.d)

Can you help with this problem?

Provide an answer of your own, or ask malignor for more information if necessary.

To post a message you must log in.