LVM write performance
Dear list, When writing to a logical volume (/dev/sys/test) directly through the device, I obtain a slow performance: root@dom0-2:/dev/mapper# dd of=/dev/sys/test if=/dev/zero 4580305+0 records in 4580305+0 records out 2345116160 bytes (2.3 GB) copied, 119.327 s, 19.7 MB/s Making a file system on top of the LV, mounting it and write into a file is ok: root@dom0-2:/dev/mapper# mkfs.xfs /dev/sys/test root@dom0-2:/mnt# mount /dev/sys/test /mnt/lv root@dom0-2:/mnt# dd of=/mnt/lv/out if=/dev/zero 2647510+0 records in 2647510+0 records out 1355525120 bytes (1.4 GB) copied, 11.3235 s, 120 MB/s Furthermore, by accident I noticed that writing directly to the block device is oke when the LV is mounted (of course destroying the file system on it): root@dom0-2:/mnt# dd of=/dev/sys/test if=/dev/zero 3703375+0 records in 3703374+0 records out 1896127488 bytes (1.9 GB) copied, 15.4927 s, 122 MB/s Does anyone know what is going on? The configuration is as follows: Debian 6.0.2 Kernel 2.6.32-5-xen-amd64 Tests are on a partition on one physical disk Best regards, Dion Kant -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e3f8173.5040...@concero.nl
Re: ad-hoc wifi - network unreachable
On Sat, 06 Aug 2011 15:29:04 -0400, "Robert Blair Mason Jr." writes: > 1. Why do I have to call iwconfig twice? Because wicd overwrites it somehow? > 2. Is wicd at fault in this case? If so, should I file a bug report? If you can do it manually and wicd cannot by default, then, yes, you should, IMHO. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8762m8ebbs@alamut.ozun.int
Re: Fwd: Billion 7800N
On 6 August 2011 01:25, Gavin Elliot Jones wrote: > > > I'm not sure I understand when you mean "was it detected during the > install procedure". > What I was asking was if it was detected during a new install of Debian, or was it connected to an already established O.S.? > > For the 7800N there wasn't anything to install. I simply plugged the > rounter into the power adapter then connected a laptop directly to it > via an ethernet port. If I remember correctly I had to manually set the > laptops IP address to initially talk to the 7800N in order to turn on > the DHCP server. Once that was done I connected the 7800N to my network > and all my computers were able to communicate just fine. > I can't get anywhere near it to configure anything. It's looking as though I have a bug of some sort in the operating system. I might have to try a new install. Looks like the only option left. Tried to ping and tcptraceroute with the only reaction either way 'No network present'. Long process getting back to SID with a Lenny disc. Thanks for your help. Regards, Weaver -- Religion is regarded by the common people as true, by the wise as false, and by the rulers as useful. — Lucius Annæus Seneca. Terrorism, the new religion.
Re: Install on new iMac failing
Has anybody had any success installing any version of Debian on a new iMac? As I've posted below, I suspect a kernel incompatibility with the new AMD graphics chip. If somebody could confirm this for me, I'll post a bug report to try to get something done. Or if somebody can disprove it, fine, tell me how to get up and running! TIA, Mike. I wrote: ... This didn't fix the problem. So basically I now have a new problem, that I can run a full install of wheezy (kernel 2.6.39-2) and set up GRUB and sync the MBR etc etc, but the new system won't boot. It gives some scrolling text for a minute or so, then gives interesting flashing lights with no further progress. Any advice, anyone? It appears it might be a kernel issue with some incompatibility with the Apple hardware. Another relevant point -- I couldn't do a graphical install. I just got a lot of square boxes instead of text on the screen. That made me think, new graphics processor! These new iMacs have an AMD Radeon HD 6750M GPU for graphics. Maybe the kernel doesn't recognize these yet? Anybody know? Here's the full hardware info for the graphics: Chipset Model: AMD Radeon HD 6750M Type: GPU Bus: PCIe PCIe Lane Width: x16 VRAM (Total): 512 MB Vendor: ATI (0x1002) Device ID: 0x6741 Revision ID: 0x ROM Revision: 113-C2950H-136 EFI Driver Version: 01.00.512 Displays: iMac: Resolution: 1920 x 1080 Pixel Depth: 32-Bit Color (ARGB) Main Display: Yes Mirror: Off Online: Yes Built-In: Yes Connection Type: DisplayPort Cheers, Mike. --- Mike Hore mike_h...@aapt.net.au --- -- --- Mike Horemike_h...@aapt.net.au --- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e3f477b.1040...@aapt.net.au
Re: cups usbfs: process .... (usb) did not claim interface 1 before use (SOLVED downgrade to 1.4.4)
Wayne Topa wrote: > > The only dist here (Squeeze, Wheezy, Sid) with a working cups is > Squeeze. So try a squeeze line in your sources.list but remember > Downgrading has it's problems. YMMV > Yes, thanks. I downgraded and the problem's gone. I'm having squeeze/testing in my apt source, but I'll go for stable, as there are too many issues like this, that cause a headache exactly then, when I don't need it. Thanks guys for posting regards -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j1n2ro$ge9$2...@dough.gmane.org
Re: Re: cups usbfs: process .... (usb) did not claim interface 1 before use (SOLVED downgrade to 1.4.4)
Pascal Dormeau wrote: >> I'm wondering if it is not related to dis/enabling particular options >> in the kernel - like the usb device id lib or something (I don't > > No it rather seems a problem in the cups libusb backend (see the link I > gave for the report upstream). Upstream does not seem inactive on it, so > the best is to have patience. In the meantime, you can download packages > for a working version at http://snapshot.debian.org/ and stick to that > version with apt-preferences (4.6-11+b1 is working fine for me). > > Regards > > Pascal Dormeau thank you, Pascal! It just confirmed what I was afraid of and read about in another thread - the solution was to downgrade to 1.4.4 regards -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j1n2kv$ge9$1...@dough.gmane.org
Re: Setting up dhcp-server on my desktop machine
On Sun 07 Aug 2011 at 14:17:03 -0400, Nico Kadel-Garcia wrote: > On Sun, Aug 7, 2011 at 4:00 AM, Bob Proulx wrote: > > > For your own sanity you probably want to add 'auto eth0' in addition > > to the 'allow-hotplug eth0' line. > > Replace "allow-hotpug eth0" with "auto eth0". Don't just add it. Why? Not that I'm advocating it in every network situation but what harm does it do in this case? > > Deprecated because things have moved to an event driven hotplug system > > instead. But both can co-exist for a while longer if you add the auto > > line. But in the future get used to interfaces being completely > > dynamic. This topic gets discussion here in the mailing list > > regularly. > > The "hotplug" business is unstable and inappropriate for servers. Why is the process unstable? Is it something inherent in udev or its scripts? > > auto eth1 > > allow-hotplug eth1 # to my ISP > > iface eth1 inet dhcp > > > > Then bring the interface up with ifup. > > See my note above. There is no *point* to allow-hotplug for a desktop > or server system. Rather a strong statement but maybe it can be sustantiated. From my point of view allow-hotplug gives faster booting and facilitates switching between wired and wireless connections easily and quickly. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110807215627.GN14528@desktop
Re: Connect to eth0 or wlan0 (NetworkManager from the command line?) - Wheezy
On Sun, Aug 7, 2011 at 5:20 PM, Bob Proulx wrote: # service network-manager stop > > Edit /etc/network/interfaces and set the following. You can simply > uncomment the "#NetworkManager#iface eth0 inet dhcp" line. See > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=530024#49 > for the details of that particular line. See this next > > http://www.debian.org/doc/manuals/debian-reference/ch05.en.html#_the_basic_syntax_of_etc_network_interfaces > for general information about that file. > > auto eth0 > allow-hotplug eth0 > iface eth0 inet dhcp > > Plug in your ethernet wire. Bring up the interface. > > # ifup eth0 > > You should be able to watch the progress by tailing the syslog in > another window. (Hint: Alt-F2 gets you to the second virtual console > terminal.) After it is up something like 'netstat -nr' should print > useful network information about the network. > > At that point you should be up and on the network and can re-install > anything that you want. That should get your system going. > > The /var/log/dpkg.log could be useful in seeing what was recently > uninstalled. Also /var/backups/ contains dpkg.status* and other files > that should allow you to know what was previously installed and > therefore be able to get back to a known good state. > > # apt-get install dctrl-tools > > $ grep-dctrl -s Package -n "install ok installed" > /var/backups/dpkg.status.0 > ...dumps a list of previously installed packages... > > $ grep-status -s Package -n "install ok installed" > ...dumps the current list of packages installed now... > > Putting that information to use you can see what was different between > the backup file and now. > > $ grep-dctrl -s Package -n "install ok installed" > /var/backups/dpkg.status.0 | sort > /tmp/list.prev > > $ grep-status -s Package -n "install ok installed" | sort > /tmp/list.now > > $ comm -3 /tmp/list.prev /tmp/list.now > > And then inspecting that list make a decision about how to repair. > > Whew! That above is somewhat complicated. But if you are in a hurry > then you probably you just need the following to pull in what you > lost. These metapackages (and gdm I prefer over the gdm3) will > probably pull in what you need. But the above would give you exact > answers. > > # apt-get install gnome gnome-core gnome-desktop-environment gdm > > Hope that helps, > Bob > Bob, Thank you so much for such a great and comprehensive answer. Googling around i thought of simply uninstalling NetworkManager, as i wasn't sure how to stop services. Also, /var/backups was exactly what i was hunting for but simply couldn't find. Muchas gracias for referencing that (and /var/log). And lastly, dctrl-tools is awesome! +1 thanks for that, too! Problems solved! And nothing ventured, nothing earned... i'm currently (and graciously) diving into all of this!
Re: Connect to eth0 or wlan0 (NetworkManager from the command line?) - Wheezy
Kieran Smyth wrote: > I'm using Debian Testing (Wheezy) on my netbook, & accidentally uninstalled > gnome-panel, gnome-session, GDM3, & something else i can't quite remember > right now. I thought it would be an easy fix using aptitude Yes! > but i have no network connections anymore, & can't get into my > Desktop Environment (well, i can... but it's a cursor & a blank > screen). Drat! :-) > Now, without a GUI... i'm useless (and i hate that!). In the beginning was the command line... > If anyone could help me get connected using the wlan0 or eth0 interfaces i > would really appreciate it. If this could be done using the command line, > that would be ideal as i would love to know how it's done. I actually like > it when things break as it helps me get to know the system i am using > better. Here is one recipe that I am sure will get you going. Stop network-manager first. # service network-manager stop Edit /etc/network/interfaces and set the following. You can simply uncomment the "#NetworkManager#iface eth0 inet dhcp" line. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=530024#49 for the details of that particular line. See this next http://www.debian.org/doc/manuals/debian-reference/ch05.en.html#_the_basic_syntax_of_etc_network_interfaces for general information about that file. auto eth0 allow-hotplug eth0 iface eth0 inet dhcp Plug in your ethernet wire. Bring up the interface. # ifup eth0 You should be able to watch the progress by tailing the syslog in another window. (Hint: Alt-F2 gets you to the second virtual console terminal.) After it is up something like 'netstat -nr' should print useful network information about the network. At that point you should be up and on the network and can re-install anything that you want. That should get your system going. The /var/log/dpkg.log could be useful in seeing what was recently uninstalled. Also /var/backups/ contains dpkg.status* and other files that should allow you to know what was previously installed and therefore be able to get back to a known good state. # apt-get install dctrl-tools $ grep-dctrl -s Package -n "install ok installed" /var/backups/dpkg.status.0 ...dumps a list of previously installed packages... $ grep-status -s Package -n "install ok installed" ...dumps the current list of packages installed now... Putting that information to use you can see what was different between the backup file and now. $ grep-dctrl -s Package -n "install ok installed" /var/backups/dpkg.status.0 | sort > /tmp/list.prev $ grep-status -s Package -n "install ok installed" | sort > /tmp/list.now $ comm -3 /tmp/list.prev /tmp/list.now And then inspecting that list make a decision about how to repair. Whew! That above is somewhat complicated. But if you are in a hurry then you probably you just need the following to pull in what you lost. These metapackages (and gdm I prefer over the gdm3) will probably pull in what you need. But the above would give you exact answers. # apt-get install gnome gnome-core gnome-desktop-environment gdm Hope that helps, Bob signature.asc Description: Digital signature
Connect to eth0 or wlan0 (NetworkManager from the command line?) - Wheezy
Hey List! I'm using Debian Testing (Wheezy) on my netbook, & accidentally uninstalled gnome-panel, gnome-session, GDM3, & something else i can't quite remember right now. I thought it would be an easy fix using aptitude but i have no network connections anymore, & can't get into my Desktop Environment (well, i can... but it's a cursor & a blank screen). In my Desktop Environment (gnome), I have manually set NetworkManager so that neither eth0 or wlan0 connect automatically. It connects when i tell it to. So if i plug in an ethernet cable, it doesn't automatically connect. Same thing for wlan0... it can detect access points but will only connect when i select one (with both eth0 and wlan0, I have to click the NetworkManager icon on my system tray in order to connect). Now, without a GUI... i'm useless (and i hate that!). When i boot up, i see NetworkManager is working, & using nm-tool i can see a list of access points around me but i have no idea how to connect to any of them from the commandline. My wireless network is named Home, & uses DHCP and WPA/WPA2 encryption. I have tried using... root@netbook:/# iwconfig wlan0 essid Home key=password and - root@netbook:/# iwconfig wlan0 essid Home s:key=password and - root@netbook:/# iwconfig wlan0 essid Home key=password (converted to hexadecimal) ...to no avail. Cat of /etc/network/interfaces is - # 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 # The primary network interface allow-hotplug eth0 #NetworkManager#iface eth0 inet dhcp If anyone could help me get connected using the wlan0 or eth0 interfaces i would really appreciate it. If this could be done using the command line, that would be ideal as i would love to know how it's done. I actually like it when things break as it helps me get to know the system i am using better.
Re: screenshot manipulation tool
> > Do you have a good screenshot manipulation tool to recommend? > > I meant a simple one, just to the point, not a big monster like gimp. > > thanks KolourPaint or ImageMagick might be good. Mark -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110807151803.273d7...@torfree.net
Re: Setting up dhcp-server on my desktop machine SOLVED
Bob Proulx wrote: > Csanyi Pal wrote: > > * /etc/network/interfaces > > allow-hotplug eth0 > > auto eth0 This is a good place to add a reference to a good document on this file. In addition to the normal documentation, Osamu Aoki did us the great service by creating the following documentation: http://www.debian.org/doc/manuals/debian-reference/ch05.en.html And in particular this section is very useful: http://www.debian.org/doc/manuals/debian-reference/ch05.en.html#_the_basic_syntax_of_etc_network_interfaces Bob P.S. Thank you Osamu Aoki! signature.asc Description: Digital signature
Re: Setting up dhcp-server on my desktop machine SOLVED
Csanyi Pal wrote:
> Bob Proulx writes:
> > Your server is configured to use dhcp to acquire a network address?
>
> Yes, of course.
It was a serious question. Servers are often configured with static
addresses. Another popular alternative is to use the dhcp server to
assign known addresses.
> OK so now I have changed to the following my /etc/network/interfaces
> file:
>
> * /etc/network/interfaces
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> # To my ISP
> auto eth1
> allow-hotplug eth1 # to my ISP
> iface eth1 inet dhcp
Oops. I had a stray tab indent in my example. Normally that iface
line would not be indented like that. I know you followed my posting
but now I need to say I typo'd that line by indenting it when it would
not normally be indented.
> # to my LAN
> allow-hotplug eth0
> auto eth0
> iface eth0 inet static
> address 192.168.1.1
> netmask 255.255.255.0
Looks good.
> * /etc/dhcp/dhcpd.conf
>
> ddns-update-style none;
> option domain-name "example.org";
> option domain-name-servers 192.168.1.1, 91.102.231.242, 91.102.231.241;
You probably did the same thing I did which was to edit those to be
generic answers. But for the archive I will note that the domain name
should be your actual domain name instead of example.org and your
nameservers should be the nameservers you want to pass down to dhcp
clients for use.
To add a few more hints here the nameservers will in the simple case
be added to /etc/resolv.conf in order. All queries go to the first
nameserver listed in the resolv.conf. If that server does not respond
after a timeout interval then the resolver library code will switch to
the next nameserver and repeat. Up to a maximum of three nameservers
may be listed. This fallback is a "last resort" type of fallback and
isn't intended for normal operation because the delays in each lookup
can be very long and by very long I mean too long to be practical for
interactive use. So don't count on the secondary nameserver listings
for high availability. Alternatively a local caching nameserver
installed on the client such as bind9 or dnsmasq or others will list
only themselves in /etc/resolv.conf and then the local caching
nameserver will round-robin among all of the available nameservers and
can provide true high availability redundancy for dns. I always
install a local caching nameserver.
> default-lease-time 600;
> max-lease-time 7200;
> authoritative;
> log-facility local7;
>
> subnet 192.168.1.0 netmask 255.255.255.0 {
> interface eth0;
> range 192.168.1.99 192.168.1.99;
> default-lease-time 86400;
> max-lease-time 86400;
> option routers 192.168.1.1;
> option subnet-mask 255.255.255.0;
> option broadcast-address 192.168.1.255;
> }
Looks good.
> > What did /var/log/syslog say?
> > # grep dhcpd /var/log/syslog
>
> No it is OK:
Agreed. That output you showed looked okay to me too.
> > If your desktop is always online then you might consider avoiding
> > network-manager. It is useful on a mobile device that needs to be
> > selecting different networks at different times. But wicd does the
> > job better. Adn you don't need it on an always on desktop or server
> > and n-m has so many bad problems that it is best to avoid it when
> > possible. Stop network-manager and add this to your interfaces file.
>
> I have purged now network-manager from my desktop system that is always
> online.
Network Manager is one of those very polarizing items that some people
love extemely and others hate extremely. I am always happy to avoid it.
I think you will be much better off without it too.
> > Hopefully the above will get you going. Please let us know how it
> > goes one way or the other.
>
> Thank you very much Bob and Tom! It goes well with the abowe showed
> setup!
Excellent! Very glad to hear that things are now working for you.
Good luck!
Bob
signature.asc
Description: Digital signature
Re: Setting up dhcp-server on my desktop machine
On Sun, Aug 7, 2011 at 4:00 AM, Bob Proulx wrote: >> I have sofar following setup on my desktop system: >> >> * /etc/network/interfaces >> >> auto lo >> iface lo inet loopback >> >> allow-hotplug eth1 # to my ISP > > Normally you would not mention eth1 at all if you want network-manager > to manage it. NetworkManager is *NOT* your friend for any stable server. It should be disabled, by default, in any system that doesn't need to manage wifi devices or migrating VPN connections. In fact, ripping it *out* by the roots is usually safest on any desktop or server class host.. >> allow-hotplug eth0 # LAN to my server >> iface eth0 inet static >> address 192.168.1.1 >> netmask 255.255.255.0 >> network 192.168.1.0 >> broadcast 192.168.1.255 >> gateway 192.168.1.1 > > For your own sanity you probably want to add 'auto eth0' in addition > to the 'allow-hotplug eth0' line. Replace "allow-hotpug eth0" with "auto eth0". Don't just add it. > For eth0 you have netmask set which is good. But you also have > network and broadcast set and those are not necessary to set > explicitly since setting netmask is sufficient. Having all three > appear in one of the examples as an example of something you could > change if needed but it wasn't expected for them to always be set. Yeah, this is a bit of old "let the system derive the correct value, it's safer" programming. It's too easy when things move around to forget to change the "network" or "broadcast" setting in concert with the "netwmask" and IP address. > But in error you have set a second gateway on your secondary interface > and are gatewaying back to yourself. You will get the default gateway > from your ISP on eth1 when network-manager dhcp's an address and > gateway. That is the one you want. Remove this second gateway > statement from eth0. That isn't what you want there. That by itself > might be the cause of whatever problems you experienced. Good point. > Stop there for a moment and test the network and don't proceed to the > dhcp server step until you think the networking is configured > correctly. > You are missing some of the standard configurations. Some of this > might not be needed but it is part of the standard template and what I > have in my files. [ good notes about setting additional options, such as default domain-name, snipped. ] >> Running /etc/init.d/networking restart is deprecated because it may not >> enable again some interfaces ... (warning). > > Deprecated because things have moved to an event driven hotplug system > instead. But both can co-exist for a while longer if you add the auto > line. But in the future get used to interfaces being completely > dynamic. This topic gets discussion here in the mailing list > regularly. The "hotplug" business is unstable and inappropriate for servers. >> I restarted networking with network-manager too but still get not eth0 >> up: >> >> sudo /etc/init.d/network-manager restart > > If your desktop is always online then you might consider avoiding > network-manager. It is useful on a mobile device that needs to be > selecting different networks at different times. But wicd does the > job better. Adn you don't need it on an always on desktop or server > and n-m has so many bad problems that it is best to avoid it when > possible. Stop network-manager and add this to your interfaces file. If your network is at all stable you should avoid NetworkManager. (That's what the software is actually called.) > auto eth1 > allow-hotplug eth1 # to my ISP > iface eth1 inet dhcp > > Then bring the interface up with ifup. See my note above. There is no *point* to allow-hotplug for a desktop or server system. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOCN9rzj6Xt0L1a2MwKmF5+nOOZ=rwwzrf1w8z8paqyk9ez...@mail.gmail.com
Re: Best linux Distro 2011
On Sun, Aug 7, 2011 at 9:45 AM, Anirudh Parui wrote: > Hi Friends, > > The comparison between Linux Distros is a big matter of discussion. > And when it comes to finding out what is the best everyone has his own > point of view. > Well i found this link which does a good comparison in all domains and > want to share with you all. > http://www.tuxradar.com/content/best-distro-2011 > > And Well Debian wins over all the Distros :) It also gets the origin of Linux as an operating system wrong. (The core GNU application swuite, of the compiler, compilation tools, core libraries, and core system utilities came first, not the kernel: the kernel simply completed the suite and led to the newly published OS's being called "Linux".) And it completely ignores the commercially supported Linux distributions, such as RHEL, OEL, and the (recently defunct) commercial SuSE. So while patting oneself on the back for the popularity of your favorite distro, take it with a grain of salt. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOCN9rxc8fLfwVMUL-vp9tXck==YY=uxfwk6--x9ucfi6ch...@mail.gmail.com
Re: Re: cups usbfs: process .... (usb) did not claim interface 1 before use
> I'm wondering if it is not related to dis/enabling particular options > in the kernel - like the usb device id lib or something (I don't No it rather seems a problem in the cups libusb backend (see the link I gave for the report upstream). Upstream does not seem inactive on it, so the best is to have patience. In the meantime, you can download packages for a working version at http://snapshot.debian.org/ and stick to that version with apt-preferences (4.6-11+b1 is working fine for me). Regards Pascal Dormeau -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110807193037.f76f47ffb617fdc08c30e...@free.fr
Re: Problems ejecting cd.
I've recently noticed one of my DVD drives giving the same eject message, but ejecting shortly afterwards. It isn't a new drive, but seems to work apart from the message. I've had that problem too, but it eventually does eject, and I leave well-enough alone. Thanks for your reply. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87r54xb3c6@ulanbator.myhome.westell.com
Re: Problems ejecting cd.
From a mechanical point of view, this sounds like a bad servo or actuator motor in the drive. Is it old? New? The hardware's an ibm thinkpad a31; that's maybe eight or nine years old. Is the drive sluggish to eject the drive, does it feel stiff, like something might be grinding on the tray itself? When it works, the cd drive works well, smoothly with no ominous sounds. Thanks for your answer to my message. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87vcu9b3ny@ulanbator.myhome.westell.com
powerdevil lacks options
Hello all, since the last versions of KDE, powerdevil can no more configured, to inhibit the rise of the frequency by processes (WTF!). I am saddly missing ist, as when I let run my notebook during night for a longer download, I do not want to get the cpu power to max by any process. I already filed a wish to the developers, but sadly I am only one person, so i am not so important. However, powerdevil gives me the abilty, to add a script, which is executed by the required profile. But how can I get the cpu stay in low frequency mode whatever happens? I suppose, a command related to /proc might help. But which command is telling the cpu to stay in low mode? Any help is welcome. Regards Hans -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201108071756.46973.hans.ullr...@loop.de
Re: cups usbfs: process .... (usb) did not claim interface 1 before use
On 08/07/2011 10:06 AM, deloptes wrote: Camaleón wrote: Do you know where I can find the 1.4 debian version of cups. I was trying to find a repo with it, or source file, but couldn't make it in about 15-20min and gave up. The only dist here (Squeeze, Wheezy, Sid) with a working cups is Squeeze. So try a squeeze line in your sources.list but remember Downgrading has it's problems. YMMV ii cups1.4.4-7 Common UNIX Printing System(tm) - server ii cups-bsd 1.4.4-7 Common UNIX Printing System(tm) - BSD commands ii cups-client 1.4.4-7 Common UNIX Printing System(tm) - client programs (SysV) ii cups-common 1.4.4-7 Common UNIX Printing System(tm) - common files ii cups-dbg 1.4.4-7 Common UNIX Printing System(tm) - debugging symbols ii cups-driver-gutenprint 5.2.6-1 printer drivers for CUPS ii cups-pdf 2.5.0-16 PDF printer for CUPS ii cups-ppdc1.4.4-7 Common UNIX Printing System(tm) - PPD manipulation utilities ii cupsddk 1.4.4-7 Common UNIX Printing System (transitional package) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e3ea0a5.9010...@gmail.com
Re: cups usbfs: process .... (usb) did not claim interface 1 before use
Camaleón wrote: Do you know where I can find the 1.4 debian version of cups. I was trying to find a repo with it, or source file, but couldn't make it in about 15-20min and gave up. regards -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j1m65d$bi9$4...@dough.gmane.org
Re: cups usbfs: process .... (usb) did not claim interface 1 before use
Camaleón wrote: Sorry for not being able to do anything. I was too busy at work > > "dmesg" showed nothing -no activity- when replugging? Well it prints the usual usb stuff > > Ah, that makes sense... well, you can configure exim (or whatever MTA) to > deliver external e-mails through a remote smtp server like any MUA will > do. Yes I think it was, but now not quite sure. I need to check, because the email client is using the correct way, I think only reportbug has been configured to bypass the smpt regards -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j1m5ut$bi9$3...@dough.gmane.org
Re: cups usbfs: process .... (usb) did not claim interface 1 before use
Pascal Dormeau wrote: >> where do I find the older version in the debian repo? > > http://snapshot.debian.org/ > > Is it an HP printer ? > The kernel message you gave makes me think of a similar problem known > upstream http://www.cups.org/str.php?L3884+Qversion:1.5 > > Best regards > > Pascal Dormeau Yes it is HP printer 5L paralell over usb. I just get a headache when something already working stops after upgrade. I'm wondering if it is not related to dis/enabling particular options in the kernel - like the usb device id lib or something (I don't remember exactly the name). Unfortunately I was too busy at work to follow or do anything to debug and I can not print at all regards -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j1m5qd$bi9$2...@dough.gmane.org
Best linux Distro 2011
Hi Friends, The comparison between Linux Distros is a big matter of discussion. And when it comes to finding out what is the best everyone has his own point of view. Well i found this link which does a good comparison in all domains and want to share with you all. http://www.tuxradar.com/content/best-distro-2011 And Well Debian wins over all the Distros :) -- Regards, Anirudh Parui -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAM0XJ0AxxgaOgksjV9+Tvq_ntYSeWecLOD10uk+7PGoBAyG=6...@mail.gmail.com
System crash when swithing to text-console
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear experts, i recently got my wife a new machine and installed stable on it. At first run it was all smooth but after the latest upgrade, which i performed after installing a second HD, the machine won't shutdown properly. I tracked it down to the following behaviour: Start up Log in work ... up to here all is good! The misery begins as soon as you try to switch from X to console either by Ctrl-Alt-F1 or induced by system shutdown the monitor goes black and the sysem will not react to any input not even to SysReq Keys after about a minute or so the system powers off and immediately on again to boot up normally (with the usual warning about HDs not having been unpountet properly) I have no idea so far as to where I should start investigating. The logs don't show any abnormality as far as I can say. thank you very much greets martin -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOPnzXAAoJECZ8myNlGwU1BcwH/icykvyzjks50/J515atmCNN KAPO5oOupJvF3QLE568ZNtJDGP38Qn0Hq9qe5qPun3zgWyagoLSPBtvKC0B8VlKp AvmaxmvJzt3Zg+qKcAiXxefmS49MKB3+PkCXaRsJGX7HtCYufdqrnCKBYiV0dqXa sLLIy1ciQtN25MQU2RB1m4u5jiFduc7VVrA2+eLdQjCIQ9uE2HijJg4eEJ/lyrJm q9tVEw8FoYVLMV8OwjzWEOhkSuPNYTE/evyztaL1jkYV4dowUOX/mvakPmlyf1wj s958iJJoMYaIoBwGqSjpemnZ9/OeEWkHZRs2sJ2bJYQWPLpij56VIx8bhAKzeK8= =LqBV -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e3e7ce1.5020...@lorenz.priv.at
Re: Install on new iMac failing
I wrote: ... This didn't fix the problem. So basically I now have a new problem, that I can run a full install of wheezy (kernel 2.6.39-2) and set up GRUB and sync the MBR etc etc, but the new system won't boot. It gives some scrolling text for a minute or so, then gives interesting flashing lights with no further progress. Any advice, anyone? It appears it might be a kernel issue with some incompatibility with the Apple hardware. Another relevant point -- I couldn't do a graphical install. I just got a lot of square boxes instead of text on the screen. That made me think, new graphics processor! These new iMacs have an AMD Radeon HD 6750M GPU for graphics. Maybe the kernel doesn't recognize these yet? Anybody know? Here's the full hardware info for the graphics: Chipset Model:AMD Radeon HD 6750M Type: GPU Bus: PCIe PCIe Lane Width: x16 VRAM (Total): 512 MB Vendor: ATI (0x1002) Device ID:0x6741 Revision ID: 0x ROM Revision: 113-C2950H-136 EFI Driver Version: 01.00.512 Displays: iMac: Resolution: 1920 x 1080 Pixel Depth: 32-Bit Color (ARGB) Main Display: Yes Mirror: Off Online: Yes Built-In: Yes Connection Type: DisplayPort Cheers, Mike. --- Mike Horemike_h...@aapt.net.au --- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e3e72ff.7020...@aapt.net.au
Install on new iMac failing
I wrote: On 6/08/11 1:01 AM, Camaleón wrote: On Fri, 05 Aug 2011 17:03:26 +1000, Mike Hore wrote: I've tried installing Squeeze (via NetInstall) on a brand new iMac (Intel i5 processor), but early on it tells me it can't find an Ethernet connection. It gives me a big list of drivers to choose from, but I can't see my Ethernet card there (Broadcom 57765-BO). So I can't proceed further. Is this a known problem? Should I try a weekly Testing build? You may need to install a backported/updated kernel. It seems that support for that card was included in kernel 2.6.34: *** http://wiki.debian.org/MacMiniIntel#Known_Issues OK, thanks, so far so good. Using the current weekly wheezy netinst, it recognizes the Ethernet and installs OK. But I haven't been able to get it to boot yet, since at the end of the installation, when I added the line GRUB_CMDLINE_LINUX "nomodeset reboot=pci" to /etc/default/grub, I then forgot to run update-grub!! So on boot, it enters GRUB, some lines scroll up the screen but then I get weird flashing color effects and nothing else happens. I hope my forgetting to update-grub is the only problem. This didn't fix the problem. So basically I now have a new problem, that I can run a full install of wheezy (kernel 2.6.39-2) and set up GRUB and sync the MBR etc etc, but the new system won't boot. It gives some scrolling text for a minute or so, then gives interesting flashing lights with no further progress. Any advice, anyone? It appears it might be a kernel issue with some incompatibility with the Apple hardware. Cheers, Mike. --- Mike Horemike_h...@aapt.net.au --- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e3e6dda.9010...@aapt.net.au
Re: Setting up dhcp-server on my desktop machine SOLVED
Bob Proulx writes:
> Csanyi Pal wrote:
>> I must recover my server system through ssh connection so so I must
>> to setup dhcp-server on my desktop system first so it can provide for
>> the server an IP address.
>
> Your server is configured to use dhcp to acquire a network address?
Yes, of course.
>> On my desktop system there I have already installed the
>> network-manager package and now I have installed the isc-dhcp-server
>> package too on this system.
>>
>> I don't know how to setup my interfaces so I achieve my goal.
>
> Setting up a dhcp server is completely independent of setting up the
> /etc/network/interfaces file. First you should set up your networking
> without doing anything about the dhcp server. Then after networking
> is set up as you like it then set up the dhcp server to use the now
> existing networking.
>
>> I have sofar following setup on my desktop system:
>>
>> * /etc/network/interfaces
>>
>> auto lo
>> iface lo inet loopback
>>
>> allow-hotplug eth1 # to my ISP
>
> Normally you would not mention eth1 at all if you want network-manager
> to manage it.
>
>> allow-hotplug eth0 # LAN to my server
>> iface eth0 inet static
>> address 192.168.1.1
>> netmask 255.255.255.0
>> network 192.168.1.0
>> broadcast 192.168.1.255
>> gateway 192.168.1.1
>
> For your own sanity you probably want to add 'auto eth0' in addition
> to the 'allow-hotplug eth0' line.
>
> For eth0 you have netmask set which is good. But you also have
> network and broadcast set and those are not necessary to set
> explicitly since setting netmask is sufficient. Having all three
> appear in one of the examples as an example of something you could
> change if needed but it wasn't expected for them to always be set.
>
> But in error you have set a second gateway on your secondary interface
> and are gatewaying back to yourself. You will get the default gateway
> from your ISP on eth1 when network-manager dhcp's an address and
> gateway. That is the one you want. Remove this second gateway
> statement from eth0. That isn't what you want there. That by itself
> might be the cause of whatever problems you experienced.
>
> Stop there for a moment and test the network and don't proceed to the
> dhcp server step until you think the networking is configured
> correctly.
OK so now I have changed to the following my /etc/network/interfaces
file:
* /etc/network/interfaces
# The loopback network interface
auto lo
iface lo inet loopback
# To my ISP
auto eth1
allow-hotplug eth1 # to my ISP
iface eth1 inet dhcp
# to my LAN
allow-hotplug eth0
auto eth0
iface eth0 inet static
address 192.168.1.1
netmask 255.255.255.0
>> * /etc/dhcp/dhcpd.conf
>>
>> subnet 192.168.1.0 netmask 255.255.255.0 {
>> interface eth0;
>> range 192.168.1.99 192.168.1.99;
>> option routers 192.168.1.1;
>> option subnet-mask 255.255.255.0;
>> }
>
> You are missing some of the standard configurations. Some of this
> might not be needed but it is part of the standard template and what I
> have in my files.
>
> # The ddns-updates-style parameter controls whether or not the server
> # will
> # attempt to do a DNS update when a lease is confirmed. We default to
> # the
> # behavior of the version 2 packages ('none', since DHCP v2 didn't
> # have support for DDNS.)
> ddns-update-style none;
>
> # option definitions common to all supported networks...
> option domain-name "example.com";
> option domain-name-servers 192.168.1.1, 192.0.43.10;
>
> default-lease-time 600;
> max-lease-time 7200;
>
> # If this DHCP server is the official DHCP server for the local
> # network, the authoritative directive should be uncommented.
> authoritative;
>
> # Use this to send dhcp log messages to a different log file (you also
> # have to hack syslog.conf to complete the redirection).
> log-facility local7;
>
> subnet 192.168.1.0 netmask 255.255.255.0 {
> interface eth0;
> range 192.168.1.99 192.168.1.99;
> default-lease-time 86400;
> max-lease-time 86400;
> option routers 192.168.1.1;
> option subnet-mask 255.255.255.0;
> option broadcast-address 192.168.1.255;
> }
* /etc/dhcp/dhcpd.conf
ddns-update-style none;
option domain-name "example.org";
option domain-name-servers 192.168.1.1, 91.102.231.242, 91.102.231.241;
default-lease-time 600;
max-lease-time 7200;
authoritative;
log-facility local7;
subnet 192.168.1.0 netmask 255.255.255.0 {
interface eth0;
range 192.168.1.99 192.168.1.99;
default-lease-time 86400;
max-lease-time 86400;
option routers 192.168.1.1;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.1.255;
}
>> * /etc/default/isc-dhcp-server
>>
>> INTERFACES="eth0"
>
> Okay.
>
>> So when I try to start dhcp-server I get an error message:
>> sudo /etc/init.d/isc-dhcp-server start
>> Starting ISC DHCP server: dhcpdcheck syslog for
>> diagnostics. ... failed!
>> failed!
>
> What did /var/log/syslog say?
>
> # grep dhc
Re: Setting up dhcp-server on my desktop machine
On Sun, Aug 7, 2011 at 3:30 AM, Csanyi Pal wrote:
>
> I have my desktop machine and my headless server machine being running
> on booth Debian GNU/Linux Squeeze operating system.
>
> I must recover my server system through ssh connection so so I must to
> setup dhcp-server on my desktop system first so it can provide for the
> server an IP address.
>
> On my desktop system there I have already installed the network-manager
> package and now I have installed the isc-dhcp-server package too on this
> system.
>
> I don't know how to setup my interfaces so I achieve my goal.
>
> I have sofar following setup on my desktop system:
>
> * /etc/network/interfaces
>
> auto lo
> iface lo inet loopback
>
> allow-hotplug eth1 # to my ISP
>
> allow-hotplug eth0 # LAN to my server
> iface eth0 inet static
> address 192.168.1.1
> netmask 255.255.255.0
> network 192.168.1.0
> broadcast 192.168.1.255
> gateway 192.168.1.1
>
> * /etc/dhcp/dhcpd.conf
>
> subnet 192.168.1.0 netmask 255.255.255.0 {
> interface eth0;
> range 192.168.1.99 192.168.1.99;
> option routers 192.168.1.1;
> option subnet-mask 255.255.255.0;
> }
>
> * /etc/default/isc-dhcp-server
>
> INTERFACES="eth0"
>
> So when I try to start dhcp-server I get an error message:
> sudo /etc/init.d/isc-dhcp-server start
> Starting ISC DHCP server: dhcpdcheck syslog for diagnostics. ... failed!
> failed!
>
> sudo ifconfig shows only eth1 but not the eth0:
> eth1 Link encap:Ethernet HWaddr 00:14:04:31:19:9f
> inet addr:95.85.169.32 Bcast:95.85.169.255 Mask:255.255.254.0
> inet6 addr: fe80::214:4ff:fe31:199f/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:70891 errors:0 dropped:0 overruns:0 frame:0
> TX packets:44387 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:93706740 (89.3 MiB) TX bytes:4889805 (4.6 MiB)
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:126 errors:0 dropped:0 overruns:0 frame:0
> TX packets:126 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:11635 (11.3 KiB) TX bytes:11635 (11.3 KiB)
>
> I restarted networking but still get not eth0 up:
> sudo /etc/init.d/networking restart
> Running /etc/init.d/networking restart is deprecated because it may not
> enable again some interfaces ... (warning).
> Reconfiguring network interfaces...done.
>
> I restarted networking with network-manager too but still get not eth0
> up:
>
> sudo /etc/init.d/network-manager restart
>
> What am I missing here?
The warning when running "sudo /etc/init.d/networking restart":
"Running /etc/init.d/networking restart is deprecated because it may
not enable again some interfaces ... (warning)."
"sudo /etc/init.d/networking restart" only brings up NICs marked
"auto"/"allow-auto"; NICs marked "auto-hotplug" are ignored.
Comment out or delete "gateway 192.168.1.1" and run "ifup --verbose
eth0" or "ifup --verbose --allow=hotplug" to bring up eth0.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CAOdo=SwcPpNOqqdiOBpPR+dBz_ph=hhggsy_ng-nlcamc7y...@mail.gmail.com
Re: install and wireless issues on Dell D600
Well, I solved this. I decided to leave the laptop alone for a while. After doing this, I had another go at installing Debian, and it found both network devices (the Broadcom and the wireless), and the Debian Installer obtained the non-free driver for the wireless that I provided on my usb-stick. So, it turns out the laptop was just tired. It worked perfectly after it was rested. Mark -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110807041206.18210...@torfree.net
Re: Setting up dhcp-server on my desktop machine
Csanyi Pal wrote:
> I must recover my server system through ssh connection so so I must to
> setup dhcp-server on my desktop system first so it can provide for the
> server an IP address.
Your server is configured to use dhcp to acquire a network address?
> On my desktop system there I have already installed the network-manager
> package and now I have installed the isc-dhcp-server package too on this
> system.
>
> I don't know how to setup my interfaces so I achieve my goal.
Setting up a dhcp server is completely independent of setting up the
/etc/network/interfaces file. First you should set up your networking
without doing anything about the dhcp server. Then after networking
is set up as you like it then set up the dhcp server to use the now
existing networking.
> I have sofar following setup on my desktop system:
>
> * /etc/network/interfaces
>
> auto lo
> iface lo inet loopback
>
> allow-hotplug eth1 # to my ISP
Normally you would not mention eth1 at all if you want network-manager
to manage it.
> allow-hotplug eth0 # LAN to my server
> iface eth0 inet static
> address 192.168.1.1
> netmask 255.255.255.0
> network 192.168.1.0
> broadcast 192.168.1.255
> gateway 192.168.1.1
For your own sanity you probably want to add 'auto eth0' in addition
to the 'allow-hotplug eth0' line.
For eth0 you have netmask set which is good. But you also have
network and broadcast set and those are not necessary to set
explicitly since setting netmask is sufficient. Having all three
appear in one of the examples as an example of something you could
change if needed but it wasn't expected for them to always be set.
But in error you have set a second gateway on your secondary interface
and are gatewaying back to yourself. You will get the default gateway
from your ISP on eth1 when network-manager dhcp's an address and
gateway. That is the one you want. Remove this second gateway
statement from eth0. That isn't what you want there. That by itself
might be the cause of whatever problems you experienced.
Stop there for a moment and test the network and don't proceed to the
dhcp server step until you think the networking is configured
correctly.
> * /etc/dhcp/dhcpd.conf
>
> subnet 192.168.1.0 netmask 255.255.255.0 {
> interface eth0;
> range 192.168.1.99 192.168.1.99;
> option routers 192.168.1.1;
> option subnet-mask 255.255.255.0;
> }
You are missing some of the standard configurations. Some of this
might not be needed but it is part of the standard template and what I
have in my files.
# The ddns-updates-style parameter controls whether or not the server
# will
# attempt to do a DNS update when a lease is confirmed. We default to
# the
# behavior of the version 2 packages ('none', since DHCP v2 didn't
# have support for DDNS.)
ddns-update-style none;
# option definitions common to all supported networks...
option domain-name "example.com";
option domain-name-servers 192.168.1.1, 192.0.43.10;
default-lease-time 600;
max-lease-time 7200;
# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
authoritative;
# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
log-facility local7;
subnet 192.168.1.0 netmask 255.255.255.0 {
interface eth0;
range 192.168.1.99 192.168.1.99;
default-lease-time 86400;
max-lease-time 86400;
option routers 192.168.1.1;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.1.255;
}
> * /etc/default/isc-dhcp-server
>
> INTERFACES="eth0"
Okay.
> So when I try to start dhcp-server I get an error message:
> sudo /etc/init.d/isc-dhcp-server start
> Starting ISC DHCP server: dhcpdcheck syslog for diagnostics. ... failed!
> failed!
What did /var/log/syslog say?
# grep dhcpd /var/log/syslog
> sudo ifconfig shows only eth1 but not the eth0:
Because eth0 isn't up.
> I restarted networking but still get not eth0 up:
> sudo /etc/init.d/networking restart
That will only restart interfaces specified with 'auto' and you don't
have auto in any of your interfaces.
To bring up an interface manually you need to use ifup.
# ifup eth0
> Running /etc/init.d/networking restart is deprecated because it may not
> enable again some interfaces ... (warning).
Deprecated because things have moved to an event driven hotplug system
instead. But both can co-exist for a while longer if you add the auto
line. But in the future get used to interfaces being completely
dynamic. This topic gets discussion here in the mailing list
regularly.
> I restarted networking with network-manager too but still get not eth0
> up:
>
> sudo /etc/init.d/network-manager restart
If your desktop is always online then you might consider avoiding
network-manager. It is useful on a mobile device that needs to be
selecting different networks at different times. But wicd does the
jo
Setting up dhcp-server on my desktop machine
Hi,
I have my desktop machine and my headless server machine being running
on booth Debian GNU/Linux Squeeze operating system.
I must recover my server system through ssh connection so so I must to
setup dhcp-server on my desktop system first so it can provide for the
server an IP address.
On my desktop system there I have already installed the network-manager
package and now I have installed the isc-dhcp-server package too on this
system.
I don't know how to setup my interfaces so I achieve my goal.
I have sofar following setup on my desktop system:
* /etc/network/interfaces
auto lo
iface lo inet loopback
allow-hotplug eth1 # to my ISP
allow-hotplug eth0 # LAN to my server
iface eth0 inet static
address 192.168.1.1
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.1
* /etc/dhcp/dhcpd.conf
subnet 192.168.1.0 netmask 255.255.255.0 {
interface eth0;
range 192.168.1.99 192.168.1.99;
option routers 192.168.1.1;
option subnet-mask 255.255.255.0;
}
* /etc/default/isc-dhcp-server
INTERFACES="eth0"
So when I try to start dhcp-server I get an error message:
sudo /etc/init.d/isc-dhcp-server start
Starting ISC DHCP server: dhcpdcheck syslog for diagnostics. ... failed!
failed!
sudo ifconfig shows only eth1 but not the eth0:
eth1 Link encap:Ethernet HWaddr 00:14:04:31:19:9f
inet addr:95.85.169.32 Bcast:95.85.169.255 Mask:255.255.254.0
inet6 addr: fe80::214:4ff:fe31:199f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:70891 errors:0 dropped:0 overruns:0 frame:0
TX packets:44387 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:93706740 (89.3 MiB) TX bytes:4889805 (4.6 MiB)
loLink encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:126 errors:0 dropped:0 overruns:0 frame:0
TX packets:126 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:11635 (11.3 KiB) TX bytes:11635 (11.3 KiB)
I restarted networking but still get not eth0 up:
sudo /etc/init.d/networking restart
Running /etc/init.d/networking restart is deprecated because it may not
enable again some interfaces ... (warning).
Reconfiguring network interfaces...done.
I restarted networking with network-manager too but still get not eth0
up:
sudo /etc/init.d/network-manager restart
What am I missing here?
--
Regards, Pal
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87bow1y8z8.fsf@debian-asztal.excito
