|
sledgehammer
|
 |
« Reply #105 on: April 29, 2011, 08:36:39 am » |
|
j.a.watson,
I am at the office now and can't try "lspci -v". Do you recall what repository you used to get the iwlagn driver? I can try that tomorrow.
thanks
John
|
|
|
|
|
Logged
|
VL7.0 xfce4 Samsung RF511
|
|
|
|
sledgehammer
|
 |
« Reply #106 on: May 01, 2011, 03:29:11 pm » |
|
uelsk8s Post the id of your wireless card. it should be in the output of lspci or possibly lsusb Here goes: 00:00.0 Host bridge: Intel Corporation Device 0104 (rev 09) 00:01.0 PCI bridge: Intel Corporation Device 0101 (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Device 0116 (rev 09) 00:16.0 Communication controller: Intel Corporation Cougar Point HECI Controller #1 (rev 04) 00:1a.0 USB Controller: Intel Corporation Cougar Point USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation Cougar Point High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation Cougar Point PCI Express Root Port 1 (rev b4) 00:1c.3 PCI bridge: Intel Corporation Cougar Point PCI Express Root Port 4 (rev b4) 00:1c.4 PCI bridge: Intel Corporation Cougar Point PCI Express Root Port 5 (rev b4) 00:1d.0 USB Controller: Intel Corporation Cougar Point USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation Device 1c49 (rev 04) 00:1f.2 IDE interface: Intel Corporation Cougar Point 4 port SATA IDE Controller (rev 04) 00:1f.3 SMBus: Intel Corporation Cougar Point SMBus Controller (rev 04) 00:1f.5 IDE interface: Intel Corporation Cougar Point 2 port SATA IDE Controller (rev 04) 01:00.0 3D controller: nVidia Corporation Device 0df4 (rev a1) 02:00.0 Network controller: Intel Corporation WiFi Link 1000 Series 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06) 04:00.0 USB Controller: NEC Corporation Device 0194 (rev 04) vector://home/johwhi
I noticed the following in the README file, as I attempted to follow along with j.a.watson's suggestion (by downloading the microcode images (iwlwifi-5000-ucode-8.83.5.1/iwlwifi-5000-5.ucode) from intellinuxwireless.org. This file apparently has to be somewhere on the system but I don't know where to put it. : 1. OVERVIEW
The file iwlwifi-5000-5.ucode provided in this package must be present on your system in order for the Intel Wireless WiFi Link AGN driver for Linux (iwlagn) to operate on your system.
The "-5" in the filename reflects an interface/architecture version number. It will change only when changes in new uCode releases make the new uCode incompatible with earlier drivers.
On adapter initialization, and at varying times during the uptime of the adapter, the microcode is loaded into the memory on the network adapter. The microcode provides the low level MAC features including radio control and high precision timing events (backoff, transmit, etc.) while also providing varying levels of packet filtering which can be used to keep the host from having to handle packets that are not of interest given the current operating mode of the device.
2. INSTALLATION
The iwlagn driver will look for the file iwlwifi-5000-5.ucode using the kernel's firmware_loader infrastructure. In order to function correctly, you need to have this support enabled in your kernel. When you configure the kernel, you can find this option in the following location:
Device Drivers -> Generic Driver Options -> Hotplug firmware loading support
You can determine if your kernel currently has firmware loader support by looking for the CONFIG_FW_LOADER definition on your kernel's .config.
In addition to having the firmware_loader support in your kernel, you must also have a working hotplug and udev infrastructure configured. The steps for installing and configuring hotplug and udev are very distribution specific.
Once you have the firmware loader in place (or if you aren't sure and you just want to try things to see if it works), you need to install the microcode file into the appropriate location.
Where that appropriate location is depends (again) on your system distribution. You can typically find this location by looking in the hotplug configuration file for your distro:
% grep \"^FIRMWARE_DIR\" /etc/hotplug/firmware.agent
This should give you output like:
FIRMWARE_DIR=/lib/firmware
If it lists more than one directory, you only need to put the microcode in one of them. In the above example, installation is simply:
% cp iwlwifi-5000-5.ucode /lib/firmware
You can now load the driver (see the INSTALL and README.iwlwifi provided with the iwlwifi package for information on building and using that driver.) Other than the problem I am having getting on the wireless, VL 7 Beta 2.1 seems to work great on my new Samsung RF511 S03. John
|
|
|
|
|
Logged
|
VL7.0 xfce4 Samsung RF511
|
|
|
hata_ph
Packager
Vectorian
   
Posts: 2828
-- Just being myself --
|
 |
« Reply #107 on: May 01, 2011, 08:27:33 pm » |
|
uelsk8s Post the id of your wireless card. it should be in the output of lspci or possibly lsusb Here goes: 00:00.0 Host bridge: Intel Corporation Device 0104 (rev 09) 00:01.0 PCI bridge: Intel Corporation Device 0101 (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Device 0116 (rev 09) 00:16.0 Communication controller: Intel Corporation Cougar Point HECI Controller #1 (rev 04) 00:1a.0 USB Controller: Intel Corporation Cougar Point USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation Cougar Point High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation Cougar Point PCI Express Root Port 1 (rev b4) 00:1c.3 PCI bridge: Intel Corporation Cougar Point PCI Express Root Port 4 (rev b4) 00:1c.4 PCI bridge: Intel Corporation Cougar Point PCI Express Root Port 5 (rev b4) 00:1d.0 USB Controller: Intel Corporation Cougar Point USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation Device 1c49 (rev 04) 00:1f.2 IDE interface: Intel Corporation Cougar Point 4 port SATA IDE Controller (rev 04) 00:1f.3 SMBus: Intel Corporation Cougar Point SMBus Controller (rev 04) 00:1f.5 IDE interface: Intel Corporation Cougar Point 2 port SATA IDE Controller (rev 04) 01:00.0 3D controller: nVidia Corporation Device 0df4 (rev a1) 02:00.0 Network controller: Intel Corporation WiFi Link 1000 Series 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06) 04:00.0 USB Controller: NEC Corporation Device 0194 (rev 04) vector://home/johwhi
I noticed the following in the README file, as I attempted to follow along with j.a.watson's suggestion (by downloading the microcode images (iwlwifi-5000-ucode-8.83.5.1/iwlwifi-5000-5.ucode) from intellinuxwireless.org. This file apparently has to be somewhere on the system but I don't know where to put it. : 1. OVERVIEW
The file iwlwifi-5000-5.ucode provided in this package must be present on your system in order for the Intel Wireless WiFi Link AGN driver for Linux (iwlagn) to operate on your system.
The "-5" in the filename reflects an interface/architecture version number. It will change only when changes in new uCode releases make the new uCode incompatible with earlier drivers.
On adapter initialization, and at varying times during the uptime of the adapter, the microcode is loaded into the memory on the network adapter. The microcode provides the low level MAC features including radio control and high precision timing events (backoff, transmit, etc.) while also providing varying levels of packet filtering which can be used to keep the host from having to handle packets that are not of interest given the current operating mode of the device.
2. INSTALLATION
The iwlagn driver will look for the file iwlwifi-5000-5.ucode using the kernel's firmware_loader infrastructure. In order to function correctly, you need to have this support enabled in your kernel. When you configure the kernel, you can find this option in the following location:
Device Drivers -> Generic Driver Options -> Hotplug firmware loading support
You can determine if your kernel currently has firmware loader support by looking for the CONFIG_FW_LOADER definition on your kernel's .config.
In addition to having the firmware_loader support in your kernel, you must also have a working hotplug and udev infrastructure configured. The steps for installing and configuring hotplug and udev are very distribution specific.
Once you have the firmware loader in place (or if you aren't sure and you just want to try things to see if it works), you need to install the microcode file into the appropriate location.
Where that appropriate location is depends (again) on your system distribution. You can typically find this location by looking in the hotplug configuration file for your distro:
% grep \"^FIRMWARE_DIR\" /etc/hotplug/firmware.agent
This should give you output like:
FIRMWARE_DIR=/lib/firmware
If it lists more than one directory, you only need to put the microcode in one of them. In the above example, installation is simply:
% cp iwlwifi-5000-5.ucode /lib/firmware
You can now load the driver (see the INSTALL and README.iwlwifi provided with the iwlwifi package for information on building and using that driver.) Other than the problem I am having getting on the wireless, VL 7 Beta 2.1 seems to work great on my new Samsung RF511 S03. John try this...should be similar with your 1000 series check your log files under /var/log/ for any message http://www.linuxquestions.org/questions/slackware-14/wireless-internet-not-working-intel-corporation-wimax-wifi-link-6050-series-871210/btw, can u post your lsmod too...
|
|
|
|
|
Logged
|
|
|
|
|
sledgehammer
|
 |
« Reply #108 on: May 01, 2011, 11:09:23 pm » |
|
Thanks, hata_ph I looked at the site and tried some of the things mentioned. I need to study it more. Later. Getting tired now. here is lsmod: root:# lsmod Module Size Used by zd1211rw 34753 0 fuse 51496 3 rfcomm 25101 0 l2cap 29295 3 rfcomm bluetooth 41358 2 rfcomm,l2cap snd_seq_dummy 1047 0 snd_seq_oss 21919 0 snd_seq_midi_event 3936 1 snd_seq_oss snd_seq 36784 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event snd_seq_device 3978 3 snd_seq_dummy,snd_seq_oss,snd_seq snd_pcm_oss 28733 0 snd_mixer_oss 10601 1 snd_pcm_oss speedstep_lib 2566 0 acpi_cpufreq 4625 1 freq_table 1771 1 acpi_cpufreq mperf 953 1 acpi_cpufreq snd_hda_codec_hdmi 17474 1 snd_hda_codec_realtek 203563 1 i915 277114 2 drm_kms_helper 19476 1 i915 drm 126262 3 i915,drm_kms_helper snd_hda_intel 16338 0 iwlagn 122480 0 snd_hda_codec 50634 3 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel iwlcore 44104 1 iwlagn i2c_algo_bit 3678 1 i915 intel_agp 7950 1 i915 uvcvideo 47304 0 snd_hwdep 4213 1 snd_hda_codec mac80211 156516 3 zd1211rw,iwlagn,iwlcore processor 21878 1 acpi_cpufreq video 9832 1 i915 intel_gtt 9667 3 i915,intel_agp snd_pcm 48986 4 snd_pcm_oss,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec videodev 46664 1 uvcvideo rtc_cmos 7153 0 thermal 6458 0 fan 1858 0 r8169 28956 0 rtc_core 12059 1 rtc_cmos agpgart 19252 3 drm,intel_agp,intel_gtt snd_timer 13063 2 snd_seq,snd_pcm thermal_sys 10226 4 processor,video,thermal,fan cfg80211 101032 4 zd1211rw,iwlagn,iwlcore,mac80211 rtc_lib 1547 1 rtc_core mii 2838 1 r8169 i2c_i801 6270 0 snd 36085 12 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer wmi 6416 0 battery 8434 0 button 3869 1 i915 ac 2485 0 soundcore 3740 1 snd i2c_core 13669 6 i915,drm_kms_helper,drm,i2c_algo_bit,videodev,i2c_i801 rfkill 11023 2 bluetooth,cfg80211 snd_page_alloc 5232 2 snd_hda_intel,snd_pcm sg 18105 0 evdev 6678 16 hwmon 1109 1 thermal_sys vector://home/johwhi/Downloads root:#
Don't know if this is relevant or not, but here is locate iwlwifi root:# locate iwlwifi /lib/modules/2.6.38.2/kernel/drivers/net/wireless/iwlwifi /lib/modules/2.6.38.2/kernel/drivers/net/wireless/iwlwifi/iwlcore.ko /lib/modules/2.6.38.2/kernel/drivers/net/wireless/iwlwifi/iwlagn.ko /lib/modules/2.6.38.2/kernel/drivers/net/wireless/iwlwifi/iwl3945.ko /lib/firmware/LICENSE.iwlwifi-3945-ucode /lib/firmware/README.iwlwifi-3945-ucode /lib/firmware/iwlwifi-4965-1.ucode /lib/firmware/iwlwifi-4965.ucode /lib/firmware/iwlwifi-3945-1.ucode /lib/firmware/iwlwifi-4965-2.ucode /usr/src/linux-2.6.38.2/include/config/iwlwifi.h /home/johwhi/Downloads/iwlwifi-5000-ucode-8.83.5.1-1.tgz /home/johwhi/Downloads/iwlwifi-5000-ucode-8.83.5.1 /home/johwhi/Downloads/iwlwifi-5000-ucode-8.83.5.1/README.iwlwifi-5000-ucode /home/johwhi/Downloads/iwlwifi-5000-ucode-8.83.5.1/iwlwifi-5000-5.ucode /home/johwhi/Downloads/iwlwifi-5000-ucode-8.83.5.1/LICENSE.iwlwifi-5000-ucode John
|
|
|
|
« Last Edit: May 01, 2011, 11:14:22 pm by sledgehammer »
|
Logged
|
VL7.0 xfce4 Samsung RF511
|
|
|
hata_ph
Packager
Vectorian
   
Posts: 2828
-- Just being myself --
|
 |
« Reply #109 on: May 02, 2011, 06:38:46 am » |
|
Your lsmod show iwlagn module is loaded. Did you try ifconfig or iwconfig? iwlcore 44104 1 iwlagn
|
|
|
|
|
Logged
|
|
|
|
|
sledgehammer
|
 |
« Reply #110 on: May 02, 2011, 09:30:51 am » |
|
Here is my ifconfig and iwconfig: root:# ifconfig eth0 Link encap:Ethernet HWaddr E8:11:32:46:E3:FA inet addr:192.168.2.7 Bcast:192.168.2.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1842 errors:0 dropped:0 overruns:0 frame:0 TX packets:2007 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1480024 (1.4 Mb) TX bytes:362682 (354.1 Kb) Interrupt:46 Base address:0xc000
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vector://home/johwhi root:# iwconfig lo no wireless extensions.
eth0 no wireless extensions.
vector://home/johwhi root:#
|
|
|
|
|
Logged
|
VL7.0 xfce4 Samsung RF511
|
|
|
hata_ph
Packager
Vectorian
   
Posts: 2828
-- Just being myself --
|
 |
« Reply #111 on: May 02, 2011, 07:19:23 pm » |
|
Have u try to download the 1000 series firmware?
|
|
|
|
|
Logged
|
|
|
|
|
sledgehammer
|
 |
« Reply #112 on: May 02, 2011, 08:42:18 pm » |
|
I am trying to figure out how to download the 1000 series firmware. Meanwhile, here is lspci -v, which I think was requested earlier. root:# lspci -v 00:00.0 Host bridge: Intel Corporation Device 0104 (rev 09) Subsystem: Samsung Electronics Co Ltd Device c0a5 Flags: bus master, fast devsel, latency 0 Capabilities: [e0] Vendor Specific Information <?> Kernel driver in use: agpgart-intel Kernel modules: intel-agp
....
02:00.0 Network controller: Intel Corporation WiFi Link 1000 Series Subsystem: Intel Corporation WiFi Link 1000 Series 1000BGN Flags: fast devsel, IRQ 16 Memory at f6c00000 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [e0] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number 8c-a9-82-ff-ff-15-c3-44 Kernel modules: iwlagn
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06) Subsystem: Samsung Electronics Co Ltd Device c0a5 Flags: bus master, fast devsel, latency 0, IRQ 46 I/O ports at b000 [size=256] Memory at e2c04000 (64-bit, prefetchable) [size=4K] Memory at e2c00000 (64-bit, prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [b0] MSI-X: Enable- Count=4 Masked- Capabilities: [d0] Vital Product Data Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel <?> Capabilities: [160] Device Serial Number 01-00-00-00-68-4c-e0-00 Kernel driver in use: r8169 Kernel modules: r8169
..... vector://home/johwhi/src/python-dateutil-2.0 root:#
And here is dmesg (which I will delete in whole or part following response as it messes up the thread, in case that is relevant: root:# dmesg ... [ 14.198311] HDA Intel 0000:00:1b.0: setting latency timer to 64 [ 14.233558] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree: [ 14.233562] iwlagn: Copyright(c) 2003-2010 Intel Corporation [ 14.233615] iwlagn 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 14.233625] iwlagn 0000:02:00.0: setting latency timer to 64 [ 14.233656] iwlagn 0000:02:00.0: Detected Intel(R) Centrino(R) Wireless-N 1000 BGN, REV=0x6C [ 14.254952] iwlagn 0000:02:00.0: device EEPROM VER=0x15d, CALIB=0x6 [ 14.254956] iwlagn 0000:02:00.0: Device SKU: 0X9 [ 14.254958] iwlagn 0000:02:00.0: Valid Tx ant: 0X1, Valid Rx ant: 0X3 [ 14.254970] iwlagn 0000:02:00.0: Tunable channels: 13 802.11bg, 0 802.11a channels [ 14.255057] iwlagn 0000:02:00.0: irq 48 for MSI/MSI-X [ 14.384047] iwlagn 0000:02:00.0: request for firmware file 'iwlwifi-1000-3.ucode' failed. [ 14.385385] iwlagn 0000:02:00.0: request for firmware file 'iwlwifi-1000-2.ucode' failed. [ 14.386618] iwlagn 0000:02:00.0: request for firmware file 'iwlwifi-1000-1.ucode' failed. [ 14.386622] iwlagn 0000:02:00.0: no suitable firmware found! [ 14.386793] iwlagn 0000:02:00.0: PCI INT A disabled [ 14.736188] hda_codec: ALC269VB: BIOS auto-probing. ... vector://home/johwhi/src/python-dateutil-2.0 root:#
|
|
|
|
« Last Edit: May 03, 2011, 09:23:43 pm by sledgehammer »
|
Logged
|
VL7.0 xfce4 Samsung RF511
|
|
|
hata_ph
Packager
Vectorian
   
Posts: 2828
-- Just being myself --
|
 |
« Reply #113 on: May 02, 2011, 09:04:35 pm » |
|
from your /var/log/messages it say missing iwlwifi-1000-3.ucode. Download it and put it in your /lib/firmware and try again.., http://www.intellinuxwireless.org/?n=downloads[ 14.233558] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree: [ 14.233562] iwlagn: Copyright(c) 2003-2010 Intel Corporation [ 14.233615] iwlagn 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 14.233625] iwlagn 0000:02:00.0: setting latency timer to 64 [ 14.233656] iwlagn 0000:02:00.0: Detected Intel(R) Centrino(R) Wireless-N 1000 BGN, REV=0x6C [ 14.254952] iwlagn 0000:02:00.0: device EEPROM VER=0x15d, CALIB=0x6 [ 14.254956] iwlagn 0000:02:00.0: Device SKU: 0X9 [ 14.254958] iwlagn 0000:02:00.0: Valid Tx ant: 0X1, Valid Rx ant: 0X3 [ 14.254970] iwlagn 0000:02:00.0: Tunable channels: 13 802.11bg, 0 802.11a channels [ 14.255057] iwlagn 0000:02:00.0: irq 48 for MSI/MSI-X [ 14.384047] iwlagn 0000:02:00.0: request for firmware file 'iwlwifi-1000-3.ucode' failed. [ 14.385385] iwlagn 0000:02:00.0: request for firmware file 'iwlwifi-1000-2.ucode' failed. [ 14.386618] iwlagn 0000:02:00.0: request for firmware file 'iwlwifi-1000-1.ucode' failed.
|
|
|
|
|
Logged
|
|
|
|
|
sledgehammer
|
 |
« Reply #114 on: May 02, 2011, 11:01:31 pm » |
|
Ha! It works! YAAAAAAAAAAAAAAAAAAAAAAAAAAAY! hata_ph and everyone who helped, thanks a trillion! Unless I hear otherwise, in the morning I will delete some of the quotes I posted tonight as they are too lengthy and are messing up this thread.
Another comment about VL 7.beta 2.1. I don't see the root (backup) version of grsync. That was quite helpful. Now that the wireless is working I plan to move my stuff over and will report further. I think moving files over would be easier with the root backup grsync program.
John
|
|
|
|
|
Logged
|
VL7.0 xfce4 Samsung RF511
|
|
|
hata_ph
Packager
Vectorian
   
Posts: 2828
-- Just being myself --
|
 |
« Reply #115 on: May 02, 2011, 11:58:06 pm » |
|
Ha! It works! YAAAAAAAAAAAAAAAAAAAAAAAAAAAY! hata_ph and everyone who helped, thanks a trillion! Unless I hear otherwise, in the morning I will delete some of the quotes I posted tonight as they are too lengthy and are messing up this thread.
Another comment about VL 7.beta 2.1. I don't see the root (backup) version of grsync. That was quite helpful. Now that the wireless is working I plan to move my stuff over and will report further. I think moving files over would be easier with the root backup grsync program.
John
Good that it is work. Maybe u can write a How to in the forum for other to follow it 
|
|
|
|
|
Logged
|
|
|
|
|
sledgehammer
|
 |
« Reply #116 on: May 03, 2011, 10:19:43 pm » |
|
dosemu (testing repository) installs as root. Formerly, I ran it as non-root.
grsync (root backup) is not available. This is a crucial backup program.
As I have said, I really like VL7
John
|
|
|
|
|
Logged
|
VL7.0 xfce4 Samsung RF511
|
|
|
hata_ph
Packager
Vectorian
   
Posts: 2828
-- Just being myself --
|
 |
« Reply #117 on: May 03, 2011, 10:32:52 pm » |
|
dosemu (testing repository) installs as root. Formerly, I ran it as non-root.
grsync (root backup) is not available. This is a crucial backup program.
As I have said, I really like VL7
John
not sure about dosemu but grsync-1.1.1 is in the VL7 testing repo...can you double check?
|
|
|
|
|
Logged
|
|
|
|
Ralph_Ellis
Member

Posts: 27
|
 |
« Reply #118 on: May 04, 2011, 06:51:11 pm » |
|
Recently, my normally very fast Vector Linux 7 installation started slowing down to a crawl for long periods. When I ran htop, I noticed that there were 9 instances of cairo-dock running. I turned off cairo-dock and uninstalled it. The speed of the operating system improved dramatically. I am running a normal installation with the packages, extra and testing repositories for updates. I have also installed the proprietary Nvidia driver. Clearly, the problem was cairo-dock since everything else is running well. The cairo-dock is very pretty to look at but perhaps it should not be part of the base installation. Has anyone else hit this problem? I should note that cairo-dock was not an issue with the initial installation. Only after I had been running Vector Linux for about two weeks did I run into an ongoing problem. It may have been affected by one of the updates.
|
|
|
|
|
Logged
|
|
|
|
|