Always have to reboot to restart dsl
 

This problem is very annoying because i can't maintan the godly uptime of some people in here;)

I connect to the net using alcatel speedtouch kernel drivers, i use br2684ctl to create the ethernet interface and then i do adsl-start to use roaring penguin to login. Now here's the problem, when i disconnect the modem without doing anything else (unplug it from the usb port), and the plug it back in later i do adsl-start and it times out, then i have to reboot to reconnect. If i kill ppp by doing adsl-stop and then unplug it, when i plug it back in and do adsl-start my entire system locks up, i can't even move the mouse, thus forcing me to turn the power to the box off.

Anyone have any ideas of how i could unplug the modem then plug it back in without this happening and needing a reboot?

Well, try this:(as root) After running "adsl-stop" do a "lsmod" to search for the module being used by the ADSL-modem, and remove that before unplugging.

right... Also it would probably help to kill any left over processes that might be hanging around... Evolution does that with me sometimes... I have to reboot or kill the two left over pid's that are always there... Then it starts right up....

Thanks.. unloading the module makes sense, but now i'm having another very strange problem.
When i go to kill unwanted processes in dropline-gnome's system moniter, it asks me for the root password, but it ALWAYS says that it is the wrong password. I am 100% positive it is the right one. Very strange.

After you do "adsl-stop" do "ifdown eth0"
In my experience RoaringPenguin wants to bring up the eth0 during "adsl-start"

I solved that before by adding

ifconfig nas0 down
ifconfig nas0 up

to my asl-connect script so thats not it.

But seriously this dropline gnome problem is really bugging me. I can't kill any processes started by root.

ps -aux
kill ***

Re: the process killing use the terminal

You can use ps aux to list the running processes and then kill -9 <pid> to kill the desired process

Re: root password....

try to login as root and see if the password is correct...

As i stated before, i'm 100% positive the password is correct, i log in through the terminal all the time. This may be some sort of bug, I really have no idea, but until I, or someone else figures it our i guess i'm going to have to do everything from the terminal.