couple questions

[w2ibc]

rc.local runs last.  What I was suggesting is that it might take time for the WLAN to connect to the network, during which time the bootup process has continued, and perhaps rc.local has run before the network is connected (which might still be taking place, using the actual "old" MAC address).

ok got ya now.  I do know attaching

MACADDR=00:11:22:33:44:55" to  /etc/sysconfig/network-scripts/ifcfg-wlan0

works but only for 1 reboot. after the 1 reboot. its back to the old mac how can I get this or macchanger -r to work on every reboot. or am I just boned.

also again another light lockup happened (lost mouse control) thought maybe it was a KDE issue but its still continuing on LXDE (pclos lxde is the best lxde version ive ever seen no joke)

when this happens before i caught
usb 2-5: USB disconnect, address 2
in dmesg. that was under kde. sadly that is not in dmesg now..

I have started to see the following in dmesg on lxde
pcmanfm[3026]: segfault at aaaaaae2 ip 45964dda sp bf8fcc00 error 4 in libgtk-x11-2.0.so.0.2400.4[456f7000+45d000]
ld-linux.so.2[17133]: segfault at 74799315 ip 44af8be4 sp bfc29ea0 error 6 in ld-2.13.so[44aee000+1a000]

idk why but I have a hunch is nvidia drivers causing it. I see in synaptic these are installed

dkms-nvidia173
dkms-nvidia96xx
dkms-nvidia-current
libdri-drivers-experimental
x11-driver-video-nouveau
x11-driver-video-nv
x11-driver-video-nvidia173
x11-driver-video-nvidia96xx
x11-driver-video-nvidia-current

the mouse issue is a real pain.

[Old-Polack]

rc.local runs last.  What I was suggesting is that it might take time for the WLAN to connect to the network, during which time the bootup process has continued, and perhaps rc.local has run before the network is connected (which might still be taking place, using the actual "old" MAC address).

ok got ya now.  I do know attaching

MACADDR=00:11:22:33:44:55 to  /etc/sysconfig/network-scripts/ifcfg-wlan0

works but only for 1 reboot. after the 1 reboot. its back to the old mac how can I get this or macchanger -r to work on every reboot. or am I just boned.

Did you try placing that line in /etc/sysconfig/network?

[pags]

...
MACADDR=00:11:22:33:44:55" to  /etc/sysconfig/network-scripts/ifcfg-wlan0

works but only for 1 reboot. after the 1 reboot. its back to the old mac how can I get this or macchanger -r to work on every reboot. or am I just boned.
...

After the reboot the sets it back, again, check

Code: [Select]

/var/log/msec.log
and

Code: [Select]

/var/log/security.log
and see if there is any indication of it being switched back...

...
idk why but I have a hunch is nvidia drivers causing it. I see in synaptic these are installed

dkms-nvidia173
dkms-nvidia96xx
dkms-nvidia-current
libdri-drivers-experimental
x11-driver-video-nouveau
x11-driver-video-nv
x11-driver-video-nvidia173
x11-driver-video-nvidia96xx
x11-driver-video-nvidia-current

the mouse issue is a real pain.

Not sure about the mouse thing...if you suspect the nVidia drivers, which version of "current" do you have (do you have "Testing" enabled in Synaptic, which would bring in the 295 driver, or not, which would bring in the 290 drivers)?

[w2ibc]

tried the /etc/sysconfig/network worked for 1 reboot. and after that reboot is it removed from the file and back to the old mac. for some reason nothing I do stays permanent

nothing in  msec or security showing the line being removed.

current nvidia shows 290.10-1pclos2011 (testing is not enabled)

grap card is nvidia geforce 6100 (onboard card in mobo)

[w2ibc]

OK went back to KDE since the mouse loss isnt a KDE issue.

I can say for sure it is the proprietary nvida drivers. can I totally purge them from synaptic? thus forcing X to use the X nv driver without any major issues?

[djohnston]

OK went back to KDE since the mouse loss isnt a KDE issue.

I can say for sure it is the proprietary nvida drivers. can I totally purge them from synaptic? thus forcing X to use the X nv driver without any major issues?

Not sure the proprietary nVidia drivers are the issue. In any case, set your video to use the nv driver before purging the other drivers. The proprietary drivers won't interfere with the nv driver.

[w2ibc]

OK went back to KDE since the mouse loss isnt a KDE issue.

I can say for sure it is the proprietary nvida drivers. can I totally purge them from synaptic? thus forcing X to use the X nv driver without any major issues?

Not sure the proprietary nVidia drivers are the issue. In any case, set your video to use the nv driver before purging the other drivers. The proprietary drivers won't interfere with the nv driver.

set nv driver, purged all the proprietary nvidia drivers and my system is stable havent had an issue with losing mouse or display blocking up. its seems pretty rock solid. so it would appear nvidia prop drivers was the cause to it (never had the prop drivers work right.)

now only thing left is getting the mac set on bootup to run correctly and ill be good to go *yay!*

[AS]

OK went back to KDE since the mouse loss isnt a KDE issue.

I can say for sure it is the proprietary nvida drivers. can I totally purge them from synaptic? thus forcing X to use the X nv driver without any major issues?

Not sure the proprietary nVidia drivers are the issue. In any case, set your video to use the nv driver before purging the other drivers. The proprietary drivers won't interfere with the nv driver.

set nv driver, purged all the proprietary nvidia drivers and my system is stable havent had an issue with losing mouse or display blocking up. its seems pretty rock solid. so it would appear nvidia prop drivers was the cause to it (never had the prop drivers work right.)

now only thing left is getting the mac set on bootup to run correctly and ill be good to go *yay!*

glad you have found a solution.  One question: do you have prelink installed ?

[w2ibc]

glad you have found a solution.  One question: do you have prelink installed ?

No I dont.

should i have it?

[AS]

glad you have found a solution.  One question: do you have prelink installed ?

No I dont.

should i have it?

no, prelink is known to cause some issue under unknown circumstances, often in combination with nvidia drivers.
I was thinking about the cause of your issue ... prelink was only an hypothesis  ...

[w2ibc]

glad you have found a solution.  One question: do you have prelink installed ?

No I dont.

should i have it?

no, prelink is known to cause some issue under unknown circumstances, often in combination with nvidia drivers.
I was thinking about the cause of your issue ... prelink was only an hypothesis  ...

Ah ok. For some reason I have had nothing but trouble with the nvidia prop drivers. not sure why. but its been the case in ubuntu,mint,and pclos but works great with the x nv drivers. this has been running on the nv drivers since 2am NY time. its 8:15p now and its stable. with the nvidia id be lucky to go an hour or two.