couple questions

[w2ibc]

So I installed PCLinuxOS KDE just a couple hours ago. I got to say you guys have done KDE4 right. I like it. everything installed smooth

I have 2 issues.

1. How can I permanently set the mac address to what I desire without having to disable the card open terminal in root and hit the command

ifconfig wlan0 hw ether xx:xx:xx:xx:xx:xx

every time on reboot? with the gnome nm-applet I was able to set it in that. and I knew the other way was to set it in /etc/network/interfaces but I didn't see that in the filesystem.

2. How can I do a mass ownership change for the backup hdd i have (its showing correct username but uid of 1000) thus saving docs,removing files,ect is sorta impossible without dropping to root (and I don't want everything in that drive owned by root!) its my important backups of stuff.

thanks!

[7272andy]

Hi w2ibc, welcome to the mad house  

Question 1: 2 ways you could try;

   1 enter the command line commands you would normally use into rc.local so they run on startup
      or
   2 add the line "MACADDR=00:11:22:33:44:55" to  /etc/sysconfig/network-scripts/ifcfg-wlan0

save and reboot

Question 2 can be answered by using Konqerer on Super user mode (PC Button -> File Tools), navigate to the mount point and right click on it.
Select properties and then the permissions tab.
Tick apply changes to all subfolders and set appropriate access permissions and ownership.
click ok

Regards
Andy

[w2ibc]

thanks that seemed to work!

[w2ibc]

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

save and reboot

well. it works for 1 reboot it seems. then after that the line is removed. and i have to go though the whole deal again.

I have found a new issue.. it appears after some time, my mouse just dies. I can still ctrl-f2 and force reboot. but mouse is dead (wireless usb mouse) unplugging the usb and plugging it back in dose no good.

in dmesg usb gives and error.. cant remember what it is as it is gone when i reboot...

sort of suspect the nvidia graphics drivers (never had nvidia graphic drivers work on any distro)

[johnmart]

Hi w2ibc,
I don't mean to be insulting, but re. your wireless mouse issue; did you check your battery? 
Happened to me. (coupla times) 
Welcome to the forum.
John

[w2ibc]

Hi w2ibc,
I don't mean to be insulting, but re. your wireless mouse issue; did you check your battery? 
Happened to me. (coupla times) 
Welcome to the forum.
John

yea its a fresh battery.

I know when it happens its a light lockup. im able to alt+f2 get into terminal and hit dmesg which produces some usb connect error.

truthfully I think its part of the nvidia proprietary drivers. never have been able to get nvidia driver to work correctly on this box. always had to use the open source Xorg drivers for it. (nvidia drivers seems to cause me so many lockups on every distro ive ever had on this box. with just open source xorg no problems)

[pags]

Hi w2ibc,
I don't mean to be insulting, but re. your wireless mouse issue; did you check your battery?  
Happened to me. (coupla times)  
Welcome to the forum.
John

yea its a fresh battery.

I know when it happens its a light lockup. im able to alt+f2 get into terminal and hit dmesg which produces some usb connect error.

truthfully I think its part of the nvidia proprietary drivers. never have been able to get nvidia driver to work correctly on this box. always had to use the open source Xorg drivers for it. (nvidia drivers seems to cause me so many lockups on every distro ive ever had on this box. with just open source xorg no problems)

Instead of a reboot, after the mouse "locks up", try using CTRL-ALT-BACKSPACE.  That will reset your X server (current login session, and all running applications will close).  Report back if that works (it's much quicker than a reboot).  If so, this will help point at a software/driver issue, as opposed to hardware...

[w2ibc]

Instead of a reboot, after the mouse "locks up", try using CTRL-ALT-BACKSPACE.  That will reset your X server (current login session, and all running applications will close).  Report back if that works (it's much quicker than a reboot).  If so, this will help point at a software/driver issue, as opposed to hardware...

ok tried that this last lockup it did not bring the mouse back, was still forced to reboot.

[w2ibc]

EDIT

finally got it. happened again (didnt last 5mins before lockup. caught this in dmesg

wlan0: no IPv6 routers present
usb 2-5: USB disconnect, address 2

[djohnston]

I think flash+firefox is causing this...

last 2 times the lockup happened I was watching youtube videos.

going to disable all the FF plugins see if it still happenes

Either right-click on a flash video and disable hardware acceleration, or Edit > Preferences > Advanced, General tab. Uncheck Use hardware acceleration when available.

[w2ibc]

I think flash+firefox is causing this...

last 2 times the lockup happened I was watching youtube videos.

going to disable all the FF plugins see if it still happenes

Either right-click on a flash video and disable hardware acceleration, or Edit > Preferences > Advanced, General tab. Uncheck Use hardware acceleration when available.

see edited post. it wasnt firefox after all. something keeps killing usb.

[w2ibc]

kept having lockups. ended up installing pclos lxde on here.

same issue mouse will just quit. only way to get it back is to reboot.

also the mac change still wont pull in rc.local if I put it in the /etc/sysconfig/network-scripts/ifcfg-wlan0 it works for 1 reboot then its back to the old mac.

Installed macchanger. and again in rc.local I tossed this in it

/usr/bin/macchanger -r wlan0

which *should* change mac on boot up and its not. not sure whats the deal with it.

[pags]

Are you sure that the WLAN has had time to connect, before the rc.local is being run?  Maybe it's changing the MAC back to the one on the hardware when it connects to the network (or, conversely, are you connecting manually, after login)?

[w2ibc]

Are you sure that the WLAN has had time to connect, before the rc.local is being run?  Maybe it's changing the MAC back to the one on the hardware when it connects to the network (or, conversely, are you connecting manually, after login)?

mac is always changed to the original when desktop is loaded. in which I have to run the bash script I made to run the macchanger -r wlan0 from desktop.

I noticed in /etc/rc.sysinit the following

if [ -f /etc/sysconfig/network ]; then
    . /etc/sysconfig/network
fi

so which is ran 1st? rc.local or rc.sysinit? I would assume rc.sysinit is bringing network up. so would i put

/usr/bin/macchanger -r wlan0 after the network command in rc.sysinit?

[pags]

Are you sure that the WLAN has had time to connect, before the rc.local is being run?  Maybe it's changing the MAC back to the one on the hardware when it connects to the network (or, conversely, are you connecting manually, after login)?

mac is always changed to the original when desktop is loaded. in which I have to run the bash script I made to run the macchanger -r wlan0 from desktop.

I noticed in /etc/rc.sysinit the following

if [ -f /etc/sysconfig/network ]; then
    . /etc/sysconfig/network
fi

so which is ran 1st? rc.local or rc.sysinit? I would assume rc.sysinit is bringing network up. so would i put

/usr/bin/macchanger -r wlan0 after the network command in rc.sysinit?

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).