Re: A lot of problems with debian sid on a Notebook
Am 23.12.2012 17:32, schrieb berenger.morel@neutralite.org:
Both entrys have a pae, my question is: can (and how can) I remove
the ...-2-686-pae entry?
As many other people said, your usual package manager is able to
remove kernels. Aptitude will warn you if you are removing the last
kernel of your system. And it will update grub accordingly. As others
I guess :)
2:My Network Manager is not working right.
First the Wlan wasn't working I installed the driver and it worked.
The next day I restarted and nothing worked.
I needed a few time to set up eth0.
Over eth0 I can use Iceweasel and aptitude but the networkmanager
(kde) doesn't accepts the connection. Because of this Pidgin is not
working.
wlan isn't working too.
eth0 and wlan0 are two different things. wlan usually means,
wireless, and wireless have often closed source drivers. So with
debian, you will need to enable them by yourself. Wiki and internet
are full of informations about that, but, in short, enable contrib
and non-free repo in your /etc/apt/sources.list, know your hardware
with $lspci or $lsusb and you should have enough informations to
discover what you need to install.
Eth0 is usually working fine with generic, and free, versions, this
is why it works. If your network manager gives you problem... the
solution I took until now, which is not advised, is to only enable
the kind of network you need.
In few words, this consist about using commands like #ifdown
<eth0/wlan0>, #ifdown <eth0/wlan0> and editing the file named
/etc/network/interfaces.
Of course, this is not an automated solution, but it avoids the use
of any software taking decisions for you.
I set up wlan0 with the iwifi driver it worked fine, but than i
shutdown the laptop and nothing worked anymore. Than I set up eth0 (I
can use the www with iceweasel or aptitude) but wlan0 doesn't works
and the network manager meant I have no connection, I think thats the
reason, why pidgin isn't connecting.
The way I'm doing it:
I use #ifdown <network> and #ifup <network> to be sure to have only
one up at a time, and I use #vim /etc/network/interfaces to add
wireless networks, by adding following lines:
wpa-ssid <router-name>
wpa-key <the key :) >
It's not exactly something I would recommend to users, but it works
well. I simply should do a script to switch wireless networks in the
interfaces file, because commenting and decommenting lines is boring :)
About your question to switch to Ubuntu, well... if you do not want to
spend time maybe it is better, I do not know, I tried it many years
ago but did not liked it. But I love to tinker, so it was obvious that
I could not like a distro where it is hard to do fun things like
destroying the system :D
If you stay with Debian, in my opinion, debian testing (Wheezy, IIRC,
never sure of the distro names...) is good enough for a normal user.
For production servers, I would prefer the stable Debian.
Thank you for your answer,
you are right a system which is hard to destroy is boring.
I will try it out with an 64bit system,
maybe it works with it,if not there would be ubuntu.
My server isn't an production server and when it could be used as an
production Server wheezy is stable.
So I will start the installation now and hopefully the kernels are away
regards
Thore
Reply to: