Debian Configuration :: Deconfiguring Network Devices Is Slow
Jan 26, 2010
I've been keeping my feet wet learning Debian. So far only in a virtual machine but I have had that machine running every day. I'm running a Lenny/Squeeze mix.The system is running well, yet every time I reboot or halt the system there is a long pause at the "Deconfiguring network devices" message. I traced the message to S35networking. With this virtual machine, which is a model for my eventual physical machine installation, I have only a single wired eth0 NIC (pcnet32).
I'll take a wild guess the script might be trying to find additional cards to halt, or perhaps a wireless card that does not exist, but that is just a guess. I'm stil learning my way around with how the init.d scripts and various /etc config files interact.I'm using a static IP address. DHCP is disabled, as far as I can tell. I did not notice anything in the logs.
I have 2 ASUS Boxes (one with 8GB, one with 4GB) When both mtus are set at 7200, using scp to copy a 56MB file takes 2:06. If I reduce either mtu to 1500, the speed is 2 seconds. I'm wondering if this is some kind of kernel bug or driver bug or what. For the moment, I've lowered the mtu to 1500 to get the performance out of the machines, but find it interesting that what should make it faster is actually slowing down. Where should I post this to get it looked at? Is anyone else seeing it.I see a similar performance issue with smbclient too.
I got a TP-Link WN951N Wireless-N PCI card for my Squeeze HTPC (this is AR5008. Performance is awful. On the lucky runs I'm getting 4 MB/s from Samba, most of the times I'm seeing 1-2 MB/s, and sometimes less than 1 MB/s. Also, ssh is not smooth, e.g. when I type commands, it can take seconds before text appears on the console, or I get slo-mo. Forcing 11g gets me a consistent 2.2 MB/s but lag is still there.
The machine has also been tested under XP SP3 and pulled off a solid 11 MB/s on a large file with no lag, so the hardware would seem OK. I've tried several kernel versions (both Liquorix and Debian stock), and a couple versions of compat-wireless (2.6.38-rc4 and 2011/03/03 bleeding edge), with little variation in outcomes. The logs got no weird messages in them, although with the more recent drivers/kernels iwconfig looks like this:
wlan0 IEEE 802.11bgn ESSID:"GuessIt" Mode:Managed Frequency:2.457 GHz Access Point: x:y:z:t:u:w Bit Rate=270 Mb/s Tx-Power=19 dBm Retry long limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality=46/70 Signal level=-64 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:64 Invalid misc:19967 Missed beacon:0
Tx discarded packets are through the roof and excessive retries is not bad either. The system doesn't run NetworkManager, wicd or whatnot. All of the wireless is configured through /etc/network/interfaces: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback
i have a HP MSA 2312fc SAN with 2 LUNs configured. The first LUN (LUN ID 1) is correctly connected to the system, but when i connect the second LUN (LUN ID 30), i find in the syslog this message: multipathd: 8:64: size 6835937472, expected 5267578112. Discard
Here is the multipath.conf
[Code]....
So I correctly see the two luns, but multipath doesn't create the relative devices. Under /dev/mapper I see: control mpath0 mpath0-part1 mpath0-part1 is the first lun, the one I mounted in a directory under filesystem. I can't find the device for the second lun
I am running Lenny. USB storage devices are painfully slow, if the data to be copied is above 4GB it works on transferring for more than half an hour and then comes up with an error dialog(saying something like file size is too big). The problem exists in both read and write.
I did google a bit and here is the output of lsmod | grep hci ehci_hcd28428 0 uhci_hcd18672 0 usbcore118192 4 usb_storage,ehci_hcd,uhci_hcd
I'm trying to assign pci devices to pci-stub at boot before any of the kernel drivers can access it. I've successfully managed to do this on a Ubuntu system but I cannot get it to work on Debian. I've set pci-stub to load as a module in /etc/modules. I've then tried both these methods:
Add pci_stub ids=8086:100f to /etc/initramfs-tools/modulesSet GRUB_CMDLINE_LINUX_DEFAULT="pci_stub.ids=8086:100f" in /etc/default/grub.
Both give the same result after updating grub/initramfs and a reboot: when I check "dmesg | grep pci-stub" I get:
The actual device id's are not claimed by stub. Same for lspci -v which shows that the devices are still using the kernel drivers.Again, this configuration works on Ubuntu. Also issuing the following commands successfully assigns one of the devices to pci-stub but I need it to work on boot before the kernel drivers load:
I've followed the guide at URL.... but my computer is unable to find any Bluetooth devices. Whether I'm using the command line or gnome-bluetooth, I don't get any results. If I plug in a cheap USB adapter, I'm able to connect and use the devices.My computer is a HP ProBook 4330s running Debian Jessie. And as far as I can tell the Bluetooth adapter is a Ralink rt3592 combination Wi-Fi and Bluetooth PCI card. The Wi-Fi works fine, but when i try to connect to a Bluetooth device, I get no search results.
When I connect my Debian PC to my WiFi router my PC doesn't get internet if other devices are connected to it .
When i disconnect those devices and connect my Debian PC only then my PC connects to internet but other devices connected to it later do not get inernet connection.
When I connect my Debian PC using LAN Cable to the same router all devices work fine.
I have installed jessie on a couple of machines. One is configured as the NFS filesystem exporter and NIS server. The other one, I am trying to configure as NFS and NIS client. NFS does not seem too much of a problem, I can mount the exported filesystem to a directory in the client and unmount it, but when I install NIS the system becomes very slow. Any command preceded by "sudo" takes a very long time (a few minutes) to complete. Then, upon rebooting the system, it reports many services failed to start (login, accounts, modem manager, avahi, network manager, exim). When if finally completes, I get a terminal login, instead the graphic login window.
i use a telekom s100 set-top-box, which originally had a prism54 wlan-card. but wlan was very slow. but the driver was working well and it did not seem to be a configuration issue, so i assumed that its that card which is so slow. following i purchased a atheros based wlan-card which is working perfectly well with the ath5k driver of my linux kernel (2.6.26-1-686). but the connection is pretty bad anyway. i get max 300kb/s from pc to pc. as its the same with 3 different cards i tested in the s100 i assume it is a configuration issue? or might there be chipset or mini-pci-slot limitation?
when i check the connection with iwconfig the bitrate is somewhere between 1-54mb/s, rising to 54mb/s and then falls back to 1mb/s, rising to 54mb/s again, falling down, its an infinite loop. im using wpa_supplicant for the connection, but i don't think thats the malefactor. well, you never know .. i tried to set the bitrate with iwconfig wlan0 rate 54M but that ended in a disconnection ...
I'm running testing and over the last week or two my system is getting slow. Any disk access slows everything to a crawl. Even the cli can take several seconds to display characters as I type them.
Installing stretch stops at detecting network devices. This is an attempt to install stretch over the top of Windows 10 on a Toshiba Radius 15 with 2 each USB2 ports and 2 each USB3 ports, and no RJ-45. Its wireless is based upon the Intel 7265. Just before the presentation of the wireless list, the system reports the need to install non-free:
and asks for media. Whether I respond yes or no, the driver selection screen comes up. [I have not been able to find those four specific files on the Internet.The network card screen comes up, I select the Intel recommended firmware iwlsifi, but the page just recreates itself and waits for a new selection. If I select either 'none' or 'not listed', the installation fails saying there is no network card.I have obtained from Intel their suggestion as of Aug 2015: iwlwifi-7265-ucode-25.30.14.0.tgz.I placed this on a USB stick in a subdirectory labeled 'firmware'. This was built from Windows 7 on a FAT32 file system.
There is also a Dynadock docking station that connects to the Toshiba via a USB3 cable. Besides video, USB,and audio, this has an Ethernet port. I have tried this connected to the laptop but it also requires a driver. I have placed that driver on the firmware directory of the USB also.
Are the four files listed above somehow inside the iwlwifi driver tgz?Is there a way to get the docking station drive to load so I can use its Ethernet port?
I have used Rufus to build the stretch USB from Windows. I do have a a Linux box I built with the same USB. I would use it but so far, I only have a command line on it and I have not figured out how to access debian.org to download the installation files nor how to put that on the stick.
Intel Core i7-5500U with Intel HD Graphics.So I updated to the backports kernel and backports intel xorg drivers and I have the weirdest thing.Everything is stuttery even cinnamon desktop effects are no longer smooth. If I boot back to 3.16, everything is butter (except the screen corruption). Even my favorite wine game dropped 25% in fps.
I remember that on windows, if the cpu is too slow (pstate_min_speed), graphics is also stuttery. However, increasing /sys/devices/system/cpu /intel_ pstate/min_perf_pct even to 100% didn't do the trick. I suspect, that this measure is causing it: URL....
how to increase the performance again? I just found out, after running glxgears (with about 40 fps), that xrandr shows an available framerate of 40fps
xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767 eDP1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 293mm x 165mm 1920x1080 60.00*+ 59.93 40.00
I guess that's what makes it feel slow. Do you know how to get that back up to 60 (fixed)? It seems like the screen refresh rate set in xrandr has no effect on the problem. When I boot, glxgears runs with 60 fps and everything is fine. After a while, it drops to 40 and the whole desktop keeps stuttering. if I change the resolution with xrandr and then change it back, it goes to 60 again for a while
 Attributes:   coresize      = "1028096"   initsize      = "0"   initstate      = "live"   refcnt       = "5"   taint        = ""   uevent       = <store method only>
Let me introduce myself, my name is Carlos AlegrÃa from Chile and I'm System administrator for a educational Institute. We use samba+ldap, for login accounts and file sharing but we not use samba with PDC.
Long time ago at the 2009 year, I was Installing the same system and this worked perfectly. But on our summer the hard disk of server has broken, so i was need installing all the system again. So the problem is with SAMBA, when i connect to the network resource, this is to slow, and when i try transfer files are slow.
My sistem is on Debian 8 Jessie and the Samba Version is 2:4.1.17+dfsg-2+deb
Code: Select all[global]   workgroup = LABORATORIO   netbios name = Shinigami   server string = debian
I am running on debian squeeze 6.0.2. I have been using it for the last id say 3 weeks and really am enjoying it.
I generally use transmission-gtk to share files over the internet. Normally I seed torrents at 110-160kb/s for hours at a time. However after messing around with firestarter my upload speed for seeding torrents rarely peaks over 70kb/s. I have purged firestarter with no success of my regular upload speed, and am very confused as to what happened. I also notice sometimes when it will get to about 70kb/s it will immediately drop down to the 20-30kb/s range.
For incoming bittorrent connections I use port 37294. I have set port 37294 to be allowed in my firewall, and forwarded in my router (since purging firestarter did not help I just reinstalled it).
I have also read allowing ports 6881-6889 is important, but I have never done that in my history of using torrents, and I have never experienced a decrease in UL speed like this.
Have I done something incorrect? I have never had this issue on other machines?
FLAGS=" --archive --one-file-system --acls --xattrs --numeric-ids --fake-super --progress --human-readable --ignore-existing --log-file="backup.log" "                                                        Â
FLAGS+=" ${DIRS} ${BACKUP_FILE}"
rsync ${FLAGS}Â Â
I then used iptraf to check the performance and I get miserable results (from the PC), even below 1 MB:
I got a new machine with GA-p55A-ud3 mobo and a WDC WD10EARS 1T disk. When I tried to benchmark the disk IO, I was suprised by the low write speed:
[Children see throughput for 1 initial writers = 35962.63 KB/sec Parent sees throughput for 1 initial writers = 35962.63 KB/sec Min throughput per process = 35962.63 KB/sec
I have a mysql server in guest domU on debian squeeze. when i create test table and do INSERT INTO test (name, value) VALUES(RAND(), RAND()); Query OK, 1 row affected (0.28 sec)
At other physical server with same configuration Query OK, 1 row affected (0.00 sec)
I try this several time but on physical server max value never get over 0.05sec and on VM lowest value was 0.13sec.
Another tests:
On physical server:
OLTP test statistics:
Threads fairness:
on VM:
OLTP test statistics:
Threads fairness:
performance of disk write speed on VM is much better then on physical server .
Just installed squeeze and noticing slow responses to ping. Ping with -n is fine, and as expected. Ping without -n is very slow to appear on the screen.
ben@WOPR:~$ ping google.com PING google.com (74.125.230.114) 56(84) bytes of data. 64 bytes from 74.125.230.114: icmp_req=1 ttl=54 time=26.2 ms 64 bytes from 74.125.230.114: icmp_req=2 ttl=54 time=25.9 ms 64 bytes from 74.125.230.114: icmp_req=3 ttl=54 time=29.3 ms 64 bytes from 74.125.230.114: icmp_req=4 ttl=54 time=25.5 ms ^C64 bytes from 74.125.230.114: icmp_req=5 ttl=54 time=25.8 ms
--- google.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 20199ms rtt min/avg/max/mdev = 25.514/26.569/29.308/1.399 ms ben@WOPR:~$ ping -n google.com PING google.com (74.125.230.115) 56(84) bytes of data. 64 bytes from 74.125.230.115: icmp_req=1 ttl=54 time=25.6 ms 64 bytes from 74.125.230.115: icmp_req=2 ttl=54 time=26.0 ms 64 bytes from 74.125.230.115: icmp_req=3 ttl=54 time=26.8 ms 64 bytes from 74.125.230.115: icmp_req=4 ttl=53 time=21.5 ms ^C --- google.com ping statistics --- 5 packets transmitted, 4 received, 20% packet loss, time 4006ms rtt min/avg/max/mdev = 21.540/25.042/26.859/2.064 ms
I've tried disabling ip6, disabling avahi and adding options single-request to my /etc/resolv.conf - problem remains. If it helps when installing Squeeze was prompted to install firmware-realtek, which I didn't have. So downloaded onto usb from another machine installed once setup was complete.
Up until very recently I've had a wired network, and at boot I'd see messages about DHCPREQUEST and DHCPOFFER and stuff as it set up the wired network.
Now I've just got wireless working instead, but it still tries to use DHCP on the no-longer-existing wired network. So it says "DHCPDISCOVER on eth0..." and waits for a bit, then again and waits again, and all the time the boot is waiting for a reply to its DHCP requests and it's not going to get one. It doesn't seem to do any harm, because once it's given up and proceeded with the boot then the wireless does seem to work fine, but I'd like to speed up the boot a little by cutting out this needless waiting. Has anyone got an idea how I can stop it? I tried in Preferences-Network connections and in Administration-Network, and in System Tools-Network tools, and also from the network icon in the task bar, but I can't find anything which lets me configure the wired network eth0 or disable it or disable the DHCP.
I have Acer Aspire 4740 laptop with Atheros ar928x wireless. My wireless is very slow, unstable. Wireless card still works well and fast in Windows (dual booting). After searching I see that there are many Ubuntu users have the same problem in Ubuntu 11.04 with this card.
I upgraded my main PC's Xfce 4.6 to Xfce 4.8 this morning.Now, every time I start Thunar for the first time after a new boot, it takes about 30 seconds to appear, and then about 10 seconds later, a second instance of it appears.After that, Thunar appears instantly every time I start it during that same session. But if I shut-down or restart my PC, Thunar again takes about 30 seconds to start up, and a second instance of it appears about 10 seconds later.
Google searches seem to indicate that people running other distros are also experiencing this problem. On advice in a different forum, I deleted the ~/.config/Thunar folder and restarted my PC, but that didn't help -- it created a new Thunar folder, but the long delay and the double-Thunars are still there every time I run Thunar for the first time in a session.
I used make-kpkg to build the 3.0.0 source debian wheezy on a dual 3.4GHz Xeon/L1-16k/L2-1mb/800Mhz bus with 4GB PC2-3200 ECC ram and Ultra 320 SCSI, using CONCURRENCY_LEVEL=4 (2 hyperthreading cpus=4 cores). The build was slower than molasses in January! Top reported cpu usage total between 10% and 25%. Why won't the build use the amount of machine it has available. One footnote: I wasn't using swap space. It literally took over an hour to build the deb kernel package.
My notebook from 2003 is at least three times faster building the 3.0.0 debian kernel source. Is it possible that this might cause improvement: make -j4 KDEB_PKGVERSION=version deb-pkg
Could amd64 vs. i386 have some influence? Could the small processor caches on the XEON cpus have an effect. The 64-bit machine absolutely flies doing everything else. I'm miffed! I've used debian since woody, although I am not an expert, but I'm no slouch!
I am using Debian sid 4.1.3-1 and when i shutdown the system it takes 3 - 5 minutes before actually shutdown, there is only a black screen until the hdd led start flashing and after that the system finally shutdown. The weird part is that sometimes it happen in less than 30 seconds , how can i figure out where the problem is ?
I'm having a strange problem with data transfers between systems. I have a file server + my desktop. Both are running Debian 8.3. I have a samba share running on the file server and I mount the shares on my desktop on boot via /etc/fstab
When I copy a file using the nautilus from my home folder (on my HDD) on my desktop to the mounted network location, my transfers start out at gigabit speeds 80MB/s-90MB/s for a couple seconds and then drop down to about 8MB/s
But when I terminate the transfer and then use scp to transfer the same file, I get consistent gigabit speed throughout the transfer. I am not sure what is going on.
I was playing with my debian server when something went totally wrong while i was editing something on my network interface,i removed those crap that i wrote and left the network interface configuration as it was
Like for example after re-editing my network interface,it was like :
As i did a network restart, i get this error saying :
There is already a pid file /var/run/dhclient.eth0.pid with pid 2802 killed old client process, removed PID file.
What is this error and how can i fix it,because every time im re booting my server i lost my network config.
I'm planning to use Debian as the OS for a firewall machine, which will sit between my internet connection and the rest of my computers. Now my network is all wired, no wireless whatsoever. I'm using the onboard the motherboards cat5 socket which seems to be using the VIA rhine driver and I'm also using a 3com 100MBps card.
I can list the machine spec if you want but it's nothing special, an old Athlon 64 rig with 1gb ram and an OEM motherboard, it all seems to work ok apart from the internet doesn't' seem to work. Lenny seems to detect both cards ok and I even used the net install CD and it managed to download everything using the 3com card.
The strange thing is when I'm in Lenny, I can't seem to connect. I can ping google, but when I try and view a webpage, the browser just sits there with a while screen... Could it be that using 2 network cards is confusing Debian? Right now I've only got the modem hooked up the the 3com card, and nothing connected to the onboard network card.
Using Fedora 15 64 bit. The problem is when I put in a USB stick (directly into USB port front or back), or SD memory card via Card reader, they take a long time to auto mount. About 30 seconds. I've tried a few different USB sticks and memory cards. Once mounted they work fine. This is a new install, been running for a few weeks, but the problem only seems to have started in the last few days. Also, not sure if it's related, but now Shotwell takes about 30 seconds to start. The screen comes up, but the interface in non responsive for around 30 seconds. Both USB and Shotwell problems seem to have started at the same time.
I am struggling trying to understand the reason for a fairly slow data transfer rate between two machines. ( tried point to point and also via a 1 gb switch ) One is nfs/http/ftp server ( with raid1 and lvm on top ), the other one my desktop pc. Both OS with default options, no changes to kernel in proc or other sort of thing.
Hardware is full recognized and perfectly working: The server has 4gb ram, Intel Core 2 Duo CPUE6850 @ 3.00GHz, 1000Mb/s NIC card and Lucid 10.04 64 bit, 250Giga Hard disk. The client has 3gb ram, Intel Core 2 CPU 6320 @ 1.86GHz, 1000Mb/s NIC card and Ubuntu Maverick 32bit , 150Gb Hard disk.
Raw data is good: gettons@gettons-desktop:~$ iperf -c MYSERVER ------------------------------------------------------------ Client connecting to MYSERVER, TCP port 5001
