MEPIS Community Forum

I have to note that network manager is never a problem in KDE 4.8 for me.

My two Kubuntu installs started with version 11 and both I updated to 12, no fresh install for them. As richb said, only the known KDE bugs happened, with fixes coming in a few days.
Network manager has also been rock solid for me through all versions of KDE also. My Slack KDE load and Gentoo KDE load have been pretty much solid also.
All of them running on the same all AMD mb and ATI video card.

I never had a problem with kde network manager until Mepis 11. Using wicd works fine for me since then.

My problems with network-manager seemed related to some kind of conflict with mepis-network. Once removed, then network-manager would work fine. (mepis-network has all the ndiswrapper drivers, though, but I don't use them)

Using Chakra which is not Debian based has none of the problems mentioned. They do make a custom kernel tho.

Here is inxi for my machine:

System: Kernel: 3.2.0-2-amd64 x86_64 (64 bit) Desktop: KDE 4.8.3 Distro: Debian GNU/Linux wheezy/sid
Machine: System: System76 product: Pangolin Performance version: panp4n
Mobo: CLEVO model: M740TU(N)/M760TU(N) Bios: Phoenix version: 1.02.18 date: 02/25/2009
CPU: Dual core Intel Core2 Duo CPU T6400 (-MCP-) cache: 2048 KB flags: (lm nx sse sse2 sse3 sse4_1 ssse3)
Clock Speeds: 1: 1200.00 MHz 2: 2000.00 MHz
Graphics: Card: NVIDIA G98 [GeForce 9300M GS] X.Org: 1.12.1.902 driver: nvidia Resolution: 1680x1050@50.0hz
GLX Renderer: GeForce 9300M GS/PCIe/SSE2 GLX Version: 3.3.0 NVIDIA 295.59
Audio: Card: Intel 82801I (ICH9 Family) HD Audio Controller driver: snd_hda_intel Sound: ALSA ver: 1.0.24
Network: Card-1: Intel WiFi Link 5100 driver: iwlwifi
IF: wlan0 state: down mac: 00:21:5d:9f:da:0e
Card-2: Realtek RTL8111/8168B PCI Express Gigabit Ethernet controller driver: r8169
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 00:90:f5:89:f9:fd
Drives: HDD Total Size: 250.1GB (0.2% used) 1: id: /dev/sda model: Hitachi_HTS72322 size: 250.1GB
Partition: ID: / size: 12G used: 4.5G (40%) fs: ext4 ID: /home size: 9.8G used: 520M (6%) fs: ext4
ID: swap-1 size: 6.76GB used: 0.00GB (0%) fs: swap
Sensors: System Temperatures: cpu: 63.8C mobo: N/A gpu: 61C
Fan Speeds (in rpm): cpu: N/A
Repos: Active apt sources in file: /etc/apt/sources.list
deb http://ftp.us.debian.org/debian/ unstable main contrib non-free
deb-src http://ftp.us.debian.org/debian/ unstable main contrib non-free
deb http://www.deb-multimedia.org sid main non-free

Note I am one minor upgrade behind on the kernel and my video is 295.59 rather than the newest 302.17.

I often replace Knemo with wicd. In this case I have not bothered because Knemo seems unusually well behaved, at least with my ethernet connection. I have not tested wireless because I do not need it here.

Over-all this is a pretty "stock" Debian Sid. I have not seen the problems Warren reports. Wheezy is another story. After months of stable operation suspend/resume has failed with the kernel/nVidia combination of 3.20--amd64 and nVidia 302.17. The cure, at least for me, involved dropping back to an earlier nVidia.

I see there is an upgrade to kmix this morning. Hope this helps Warren.

1. Taken from "inxi" output;
Kernel: 2.6.36-1-mepis64-smp x86_64 (64 bit) Desktop: KDE 4.6.5 Distro: MEPIS 11.0 squeeze

Network Manager (disastrous) removed in favour of "Ceni" as it, just works.

2. Card-1: Intel 82801JI (ICH10 Family) HD Audio Controller driver: HDA Intel Sound: ALSA ver: 1.0.23

Kmix has always been a problem for the first few iterations, no PCM slider for instance. Currently settled down into a working but not ideal state.

KDE 4.6.5 input may not be very useful for KDE 4.8

+1 for knetwork.

it does show that the issue has been prevalent for awhile though. i'm pretty sure that i've seen it prior to that /specifics nah.

easy...

it's probably for the best as heavy updates again today for wheezy > 4.8.4-3.