Re: eth0 : no such device
Quoting Lisi Reisz (lisi.re...@gmail.com): On Friday 31 July 2015 19:59:40 David Wright wrote: Ironically, your suggestion yesterday (ifconfig) was not so potentially useful for a different reason (ifconfig might not be there), but of course you didn't have the context. I was suggesting it in a very specific context, and did know that it was there - or I wouldn't have suggested it. It is still available otb in Wheezy. That's why I wrote not so *potentially* useful. I'm not clear what the *very* specific context was, but your reply was to a post that included the lines: And the tower.. I had to install fedora because it didn't want to mount my home during installation - which was a new 1To disk to format, even after formatted it which gparted. Plus the unavailable network issue of course, also during installation. In the context of installation, ifconfig is not available and hasn't been at least since squeeze, whereas ip (a cut down version) is in busybox. Cheers, David. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150801014840.GA18733@alum
Re: eth0 : no such device
On Fri, 31 Jul 2015, Gene Heskett wrote: To use my fixed address methods, which are officialy discouraged by the list police... And what, exactly, pray tell, do those august personages (the list police) preach? Something tells me that what you jocularly term my fixed address methods are the exact ones I have been using since lo those many aeons ago when I sat down to read a hardcopy printout of the ifconfig man page. you will need to edit /etc/resolv.conf after nuking the softlink that it is and creating a real file, saying order hosts,dns on the first line, and the address of the local dns resolver as nameserver on the next line. Ditto above. Been doing it that way for aeons. Is there a new way? Changing resolv.conf to a softlink merits harsh punishment. Where's my PPK? AND, I am going to have to make sure that my next $100 Staples refurb box boots one of the *bsd's! This is incredible! -- IMPORTANT: This email is intended for the use of the individual addressee(s) named above and may contain information that is confidential, privileged or unsuitable for overly sensitive persons with low self-esteem, no sense of humour or irrational metaphysical beliefs. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/nycvar.QRO.7.75.3.1507310932160.3438@arjgebyy.ybpnyqbznva
Re: eth0 : no such device
On Friday 31 July 2015 14:50:18 Bob Bernstein wrote: On Fri, 31 Jul 2015, Gene Heskett wrote: To use my fixed address methods, which are officialy discouraged by the list police... And what, exactly, pray tell, do those august personages (the list police) preach? Something tells me that what you jocularly term my fixed address methods are the exact ones I have been using since lo those many aeons ago when I sat down to read a hardcopy printout of the ifconfig man page. I prefer fixed address, almost always use it (I sometimes now achieve static IPs by using DHCP and having fixed IP allocation by MAC for some addresses in the router) and have never had a problem, nor been aware that I was being discouraged... Just be deaf to discouragement, Gene. I clearly am. Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201507311500.06589.lisi.re...@gmail.com
Re: eth0 : no such device
On Friday 31 July 2015 16:55:45 David Wright wrote: Yes, ifconfig's indentation is prettier when you just want a quick summary, but ip is more flexible and the output is much easier /to parse/. Emphasis directed at Lisi :) :-) I wanted to be able to read it - and the OP had said that he had Wheezy, so I knew that he had ifconfig. If you remember, I got in trouble the other day for saying that the command is ip. ;-) I just wanted to be able compare what he had as ip in /e/n/i and what ifconfig said, to see if they tallied. Or to suggest it to the OP. ;-) So a pretty quick summary was ideal. And no, ip is not easier to parse. It may be for you, and even for most people - but I find it so difficult to read that it is hard to get anything out of it. (And I do mean read - physically read). But ip clearly gives more information - _if_ you can read it. ;-) Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201507311737.36420.lisi.re...@gmail.com
Re: eth0 : no such device
Quoting Diogene Laerce (me_buss...@yahoo.fr): Le 30/07/2015 18:35, Lisi Reisz a écrit : On Wednesday 29 July 2015 18:09:36 Diogene Laerce wrote: Hi, I have big issues recently with debian that I don't understand, maybe someone could help on the matter ? First, debian does not want to give me any network. I really say debian because I have 3 possibilities to run the OS : 2 USB sticks and a PC tower, all on wheezy, which worked fine til they do not for no reason. The one USB stick which does boot and run says, when /ifconfig eth0 up/ : eth0: ERROR while getting interface flags: no such device The other stick now even doesn't want to start X (but that I guess is not related, surely USB stick issue). And the tower.. I had to install fedora because it didn't want to mount my home during installation - which was a new 1To disk to format, even after formatted it which gparted. Plus the unavailable network issue of course, also during installation. These network issues only happen with debian as I could install fedora with no issue at all : it took care of my home and found the network without raising any flag. Any idea ? Did you do anything to your network device(s)? New anything? New card? What happens with a new Debian installation? Well no, I didn't. Everything was fine and the same until it didn't. Actually it started with repetitive attempt to connect from a live cd 7.8 version which froze my internet box (router + TV). But the repetitive attempt seems to underline the existence of a pre-existing issue.. I guess. After that, I was unable to connect from any debian device. Even a mint live cd couldn't. But parted magic live cd could, fedora could. I then tried to install 8.1 but it wouldn't either and raise the home issue with it. All those happen on the workstation/tower. Did you move anyhting? Yes I actually change my home disk to another one, new, 1To Seagate. What is the physical relationship, if any, between the USB sticks and the tower? I installed all stick OSes with the station which failed first. I now have access only to one USB stick : 1 does not load X as said before and I have fedora now on the workstation (tower). A mysterious comrade who wants to remain anonymous it seems, I will call him Mr T. :), advised me to look into /etc/udev/rules : eth0 had been renamed to eth2 with eth0 bound to the tower MAC address (fedora today) and eth2 bound to another tower MAC address I tried the USB stick on after. I deleted the first tower line and updated the eth2 definition - changing it to eth0 and now it works. But it still does not explain why the 7.8 and 8.1 did not, on the first tower ? And neither why the Mint live cd did not ? And as I can't reproduce the issue now, I may never know. I was reluctant to make any comment on your first post because, at the end of it, I wasn't sure how many computers you were using and what was and wasn't running on them. Having in the past played fast and loose with switching hard drives, NICs and kernels between computers (no USB sticks back then), I remember the problems with the kernel's random naming of multiple identical NICs (the university naturally bought hundreds of them), and the usefulness of udev when it arrived. But the persistence of /etc/udev/rules.d/ comes at a price. I think there's work in progress but it's probably quite hard to keep things in sync between different distributions/versions etc. What does /etc/network/interfaces say? What is the result of #ifconfig -a ? Now the result is normal : http://pastebin.com/DDvQCePg I did try to get it during the 8.1 installation though, from the shell, but it seems that the installation shell lacks a lot of tools and I couldn't get a clear status of what happened there. ifconfig is considered outdated, so installers use ip. You don't even have to be root to find ip in your path. Yes, ifconfig's indentation is prettier when you just want a quick summary, but ip is more flexible and the output is much easier /to parse/. Emphasis directed at Lisi :) So I guess this is it for this issue. One small thing: your concealed MAC address is fully revealed in the ipv6 link address. If you obscure just the 2nd half of the MAC (and its corresponding part of the ipv6), we can then still read the manufacturer's part without your revealing then full MAC. Glad it's all working now. Cheers, David. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150731155545.GA8779@alum
Re: eth0 : no such device
On 07/31/2015 at 12:37 PM, Lisi Reisz wrote: And no, ip is not easier to parse. It may be for you, and even for most people - but I find it so difficult to read that it is hard to get anything out of it. (And I do mean read - physically read). But ip clearly gives more information - _if_ you can read it. ;-) I usually interpret parse in this sort of context to refer to machine parsing, not reading by humans - i.e., ease of parsing refers to how comparatively easy it is to write a program to look at the output and extract exactly the piece of information you want without any extraneous bits. easier to parse does _not_ mean the same thing as easier to read. I'm not familiar with the use of 'ip' (it took me half-a-dozen tries and several references to the man page to figure out how to get it to produce any potentially useful output, rather than just its usage message or an error message), but at a glance, I can see some merit to the claim that the output of 'ip address' is more readily parseable by e.g. a shell script than is the output of 'ifconfig'. To human eyes, however, at a glance the output of 'ip address' is significantly less readable than that of 'ifconfig' - which is saying something. I certainly would not want to have to use 'ip' to the exclusion of 'ifconfig', if this sort of output is the best that it provides. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: eth0 : no such device
On Friday 31 July 2015 18:15:14 The Wanderer wrote: I usually interpret parse in this sort of context to refer to machine parsing, not reading by humans Ah! I'll certainly accept that. I took it to mean: 1. (linguistics) To resolve into its elements, as a sentence, pointing out the several parts of speech, and their relation to each other by government or agreement; to analyze and describe grammatically. I.e. to deconstruct and understand. I didn't know the meaning: 2.(computing) To split a file or other input into pieces of data that can be easily stored or manipulated. https://en.wiktionary.org/wiki/parse So you have taught me something, and I wouldn't argue about that! Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201507311904.02201.lisi.re...@gmail.com
Re: eth0 : no such device
On Friday 31 July 2015 10:00:06 Lisi Reisz wrote: On Friday 31 July 2015 14:50:18 Bob Bernstein wrote: On Fri, 31 Jul 2015, Gene Heskett wrote: To use my fixed address methods, which are officialy discouraged by the list police... And what, exactly, pray tell, do those august personages (the list police) preach? Something tells me that what you jocularly term my fixed address methods are the exact ones I have been using since lo those many aeons ago when I sat down to read a hardcopy printout of the ifconfig man page. I prefer fixed address, almost always use it (I sometimes now achieve static IPs by using DHCP and having fixed IP allocation by MAC for some addresses in the router) and have never had a problem, nor been aware that I was being discouraged... Just be deaf to discouragement, Gene. I clearly am. Lisi Gotta play the Sid Dabster part to the end, both of us. ;-) Cheers, Gene Heskett -- There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) Genes Web page http://geneslinuxbox.net:6309/gene -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201507311501.38857.ghesk...@wdtv.com
Re: eth0 : no such device
On Friday 31 July 2015 19:59:40 David Wright wrote: Ironically, your suggestion yesterday (ifconfig) was not so potentially useful for a different reason (ifconfig might not be there), but of course you didn't have the context. I was suggesting it in a very specific context, and did know that it was there - or I wouldn't have suggested it. It is still available otb in Wheezy. Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201507312026.58880.lisi.re...@gmail.com
Re: eth0 : no such device
Le 31/07/2015 17:55, David Wright a écrit : Quoting Diogene Laerce (me_buss...@yahoo.fr): ... I was reluctant to make any comment on your first post because, at the end of it, I wasn't sure how many computers you were using and what was and wasn't running on them. Having in the past played fast and loose with switching hard drives, NICs and kernels between computers (no USB sticks back then), I remember the problems with the kernel's random naming of multiple identical NICs (the university naturally bought hundreds of them), and the usefulness of udev when it arrived. But the persistence of /etc/udev/rules.d/ comes at a price. I think there's work in progress but it's probably quite hard to keep things in sync between different distributions/versions etc. I didn't test it yet but a little ifdown script deleting the faulty line should solve this, no ? One small thing: your concealed MAC address is fully revealed in the ipv6 link address. If you obscure just the 2nd half of the MAC (and its corresponding part of the ipv6), we can then still read the manufacturer's part without your revealing then full MAC. Yeah.. My ass was kind of itching while I posted but I didn't get why at the moment. ;) Glad it's all working now. Thanks ! / -- “One original thought is worth a thousand mindless quotings.” “Le vrai n'est pas plus sûr que le probable.” Diogene Laerce/ signature.asc Description: OpenPGP digital signature
Re: eth0 : no such device
Quoting Lisi Reisz (lisi.re...@gmail.com): On Friday 31 July 2015 18:15:14 The Wanderer wrote: I usually interpret parse in this sort of context to refer to machine parsing, not reading by humans Ah! I'll certainly accept that. I took it to mean: 1. (linguistics) To resolve into its elements, as a sentence, pointing out the several parts of speech, and their relation to each other by government or agreement; to analyze and describe grammatically. I.e. to deconstruct and understand. I didn't know the meaning: 2.(computing) To split a file or other input into pieces of data that can be easily stored or manipulated. https://en.wiktionary.org/wiki/parse So you have taught me something, and I wouldn't argue about that! My apologies for causing confusion. The original exchange that I was referring back to with my emphasis was indeed the ip address thread. I ought to have added two words to my comment (in brackets): ifconfig output is much easier to look at. But much harder to parse. And ip's -o switch makes it even easier [to parse] because each item is all on one line. I still think it's fairly obvious that I *was* contrasting reading (ie looking at) and something else (using the results in a script, parsing). That's why I wrote But Still harking back to that thread, I made my original comment there because I didn't think that the OP's posting (flagged solved) answered the question satisfactorily, viz. Q: What command will tell me what ip address it is using? A: The problem was that ifconfig is in sbin not bin. Your answer, ip addr, was much better and ought IMHO to have been quoted and flagged. Ironically, your suggestion yesterday (ifconfig) was not so potentially useful for a different reason (ifconfig might not be there), but of course you didn't have the context. There's nowt wrong with ifconfig but a lot of people don't seem to even know about ip. BTW it might be worth pointing out that the examples of its use are all in the man pages listed at the bottom of man ip. It keeps man ip smaller but unfortunately means you can't use bash-completion on such as man ip-neighbour. What a contrast to ip itself, eg, ip n! Cheers, David. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150731185940.GA12786@alum
Re: eth0 : no such device
Le 31/07/2015 21:26, Lisi Reisz a écrit : On Friday 31 July 2015 19:59:40 David Wright wrote: Ironically, your suggestion yesterday (ifconfig) was not so potentially useful for a different reason (ifconfig might not be there), but of course you didn't have the context. I was suggesting it in a very specific context, and did know that it was there - or I wouldn't have suggested it. It is still available otb in Wheezy. I do confirm, it was. :) Best regards, /-- “One original thought is worth a thousand mindless quotings.” “Le vrai n'est pas plus sûr que le probable.” Diogene Laerce/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55bbd99c.2040...@yahoo.fr
Re: eth0 : no such device
On Friday 31 July 2015 09:50:18 Bob Bernstein wrote: On Fri, 31 Jul 2015, Gene Heskett wrote: To use my fixed address methods, which are officialy discouraged by the list police... And what, exactly, pray tell, do those august personages (the list police) preach? They have been drinking the koolaid and saying the network-mangler can handle it. The number of times it HAS handled it for me has not used up the fingers on one hand yet. And I've been using linux since 1998. Something tells me that what you jocularly term my fixed address methods are the exact ones I have been using since lo those many aeons ago when I sat down to read a hardcopy printout of the ifconfig man page. you will need to edit /etc/resolv.conf after nuking the softlink that it is and creating a real file, saying order hosts,dns on the first line, and the address of the local dns resolver as nameserver on the next line. Ditto above. Been doing it that way for aeons. Is there a new way? Changing resolv.conf to a softlink merits harsh punishment. Where's my PPK? AND, I am going to have to make sure that my next $100 Staples refurb box boots one of the *bsd's! This is incredible! -- IMPORTANT: This email is intended for the use of the individual addressee(s) named above and may contain information that is confidential, privileged or unsuitable for overly sensitive persons with low self-esteem, no sense of humour or irrational metaphysical beliefs. Cheers, Gene Heskett -- There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) Genes Web page http://geneslinuxbox.net:6309/gene -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201507311500.27299.ghesk...@wdtv.com
Re: eth0 : no such device
On Friday 31 July 2015 05:58:28 Diogene Laerce wrote: Le 30/07/2015 18:35, Lisi Reisz a écrit : On Wednesday 29 July 2015 18:09:36 Diogene Laerce wrote: Hi, I have big issues recently with debian that I don't understand, maybe someone could help on the matter ? First, debian does not want to give me any network. I really say debian because I have 3 possibilities to run the OS : 2 USB sticks and a PC tower, all on wheezy, which worked fine til they do not for no reason. The one USB stick which does boot and run says, when /ifconfig eth0 up/ : eth0: ERROR while getting interface flags: no such device The other stick now even doesn't want to start X (but that I guess is not related, surely USB stick issue). And the tower.. I had to install fedora because it didn't want to mount my home during installation - which was a new 1To disk to format, even after formatted it which gparted. Plus the unavailable network issue of course, also during installation. These network issues only happen with debian as I could install fedora with no issue at all : it took care of my home and found the network without raising any flag. Any idea ? Did you do anything to your network device(s)? New anything? New card? What happens with a new Debian installation? Well no, I didn't. Everything was fine and the same until it didn't. Actually it started with repetitive attempt to connect from a live cd 7.8 version which froze my internet box (router + TV). But the repetitive attempt seems to underline the existence of a pre-existing issue.. I guess. After that, I was unable to connect from any debian device. Even a mint live cd couldn't. But parted magic live cd could, fedora could. I then tried to install 8.1 but it wouldn't either and raise the home issue with it. All those happen on the workstation/tower. Did you move anyhting? Yes I actually change my home disk to another one, new, 1To Seagate. What is the physical relationship, if any, between the USB sticks and the tower? I installed all stick OSes with the station which failed first. I now have access only to one USB stick : 1 does not load X as said before and I have fedora now on the workstation (tower). A mysterious comrade who wants to remain anonymous it seems, I will call him Mr T. :), advised me to look into /etc/udev/rules : eth0 had been renamed to eth2 with eth0 bound to the tower MAC address (fedora today) and eth2 bound to another tower MAC address I tried the USB stick on after. I deleted the first tower line and updated the eth2 definition - changing it to eth0 and now it works. But it still does not explain why the 7.8 and 8.1 did not, on the first tower ? And neither why the Mint live cd did not ? And as I can't reproduce the issue now, I may never know. What does /etc/network/interfaces say? What is the result of #ifconfig -a ? Now the result is normal : http://pastebin.com/DDvQCePg I did try to get it during the 8.1 installation though, from the shell, but it seems that the installation shell lacks a lot of tools and I couldn't get a clear status of what happened there. So I guess this is it for this issue. Why did you write /lspci -n/ when the instruction was lspci -n? Did you try it without the fwd slash? Actually those are italic font markers, I did run the good command. Thanks to all for the good pointers, If you search your dmesg, you wil probably find that udev, after discovering eth0, then quite a bit later, renames it according to the connection attempts made during THIS install. That bit me when I was moving the drive with a linuxcnc install on it from machine to machine while looking for a machine capable of doing the realtime correctly. So now, and the ethernet works fine once I had excised network-mangler and edited /etc/network/interfaces to tell it to use eth5. Obviously my local network is /etc/host file based, fixed addresses for all my machines. To use my fixed address methods, which are officialy discouraged by the list police you will need to edit /etc/resolv.conf after nuking the softlink that it is and creating a real file, saying order hosts,dns on the first line, and the address of the local dns resolver as nameserver on the next line. My router runs dd-wrt, so its address is used as the nameserver and it then forwards a dns query it doesn't know about to the dns servers it gets from my cable modem. And it all Just Works(TM). I have no clue what genius thought that renameing eth0 was the right thing to do, but its damned sure biteing a lot of folks that do not need to be so bitten. This list is not the only one being littered with where's my network questions. Cheers, Gene Heskett -- There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) Genes Web page
Re: eth0 : no such device
Le 30/07/2015 18:35, Lisi Reisz a écrit : On Wednesday 29 July 2015 18:09:36 Diogene Laerce wrote: Hi, I have big issues recently with debian that I don't understand, maybe someone could help on the matter ? First, debian does not want to give me any network. I really say debian because I have 3 possibilities to run the OS : 2 USB sticks and a PC tower, all on wheezy, which worked fine til they do not for no reason. The one USB stick which does boot and run says, when /ifconfig eth0 up/ : eth0: ERROR while getting interface flags: no such device The other stick now even doesn't want to start X (but that I guess is not related, surely USB stick issue). And the tower.. I had to install fedora because it didn't want to mount my home during installation - which was a new 1To disk to format, even after formatted it which gparted. Plus the unavailable network issue of course, also during installation. These network issues only happen with debian as I could install fedora with no issue at all : it took care of my home and found the network without raising any flag. Any idea ? Did you do anything to your network device(s)? New anything? New card? What happens with a new Debian installation? Well no, I didn't. Everything was fine and the same until it didn't. Actually it started with repetitive attempt to connect from a live cd 7.8 version which froze my internet box (router + TV). But the repetitive attempt seems to underline the existence of a pre-existing issue.. I guess. After that, I was unable to connect from any debian device. Even a mint live cd couldn't. But parted magic live cd could, fedora could. I then tried to install 8.1 but it wouldn't either and raise the home issue with it. All those happen on the workstation/tower. Did you move anyhting? Yes I actually change my home disk to another one, new, 1To Seagate. What is the physical relationship, if any, between the USB sticks and the tower? I installed all stick OSes with the station which failed first. I now have access only to one USB stick : 1 does not load X as said before and I have fedora now on the workstation (tower). A mysterious comrade who wants to remain anonymous it seems, I will call him Mr T. :), advised me to look into /etc/udev/rules : eth0 had been renamed to eth2 with eth0 bound to the tower MAC address (fedora today) and eth2 bound to another tower MAC address I tried the USB stick on after. I deleted the first tower line and updated the eth2 definition - changing it to eth0 and now it works. But it still does not explain why the 7.8 and 8.1 did not, on the first tower ? And neither why the Mint live cd did not ? And as I can't reproduce the issue now, I may never know. What does /etc/network/interfaces say? What is the result of #ifconfig -a ? Now the result is normal : http://pastebin.com/DDvQCePg I did try to get it during the 8.1 installation though, from the shell, but it seems that the installation shell lacks a lot of tools and I couldn't get a clear status of what happened there. So I guess this is it for this issue. Why did you write /lspci -n/ when the instruction was lspci -n? Did you try it without the fwd slash? Actually those are italic font markers, I did run the good command. Thanks to all for the good pointers, -- One original thought is worth a thousand mindless quotings. Le vrai n'est pas plus sûr que le probable. Diogene Laerce signature.asc Description: OpenPGP digital signature
Re: eth0 : no such device
Hi, Le 29/07/2015 20:37, MENGUAL Jean-Philippe a écrit : Hi, What's the result of dmesg? In particular: dmesg|grep .fw? You can find the results here : dmesg - http://pastebin.com/YPdmfkyG lspci -n - http://pastebin.com/y6xEUfiL And I put /sudo lspci -vvv /as well as I didn't find the n option very explicit./ // //dmesg | grep .fw/ does not return anything. Maybe you need some firmware? I doubt that. As I said before, everything was working well before and all of sudden, all of my debian devices seemed to fail to get any network. Eave you checked from lspci -n if the module of the kernel is the correct one? I think it is but I don't fully understand what you mean or how to get this answer from the /lspci -n/ output. Also, I don't believe the OP states which version of Debian this is a problem with, but testing is now moving towards systemd-style persistent network names. That is, something like enp1s4 (EtherNet on Pci-bus 1, Slot 4). If the OP is me - I don't know what it means :), I did : wheezy. Kind regards, -- One original thought is worth a thousand mindless quotings. Le vrai n'est pas plus sûr que le probable. Diogene Laerce signature.asc Description: OpenPGP digital signature
Re: eth0 : no such device
Le 30/07/2015 15:29, Diogene Laerce a écrit : Hi, Le 29/07/2015 20:37, MENGUAL Jean-Philippe a écrit : Hi, What's the result of dmesg? In particular: dmesg|grep .fw? You can find the results here : dmesg - http://pastebin.com/YPdmfkyG lspci -n - http://pastebin.com/y6xEUfiL hmmm, check with ifconfig -a wether your net interface wouldn't be eth2. I'll check the remaining (lspci) afterwards. Regards, And I put /sudo lspci -vvv /as well as I didn't find the n option very explicit./ // //dmesg | grep .fw/ does not return anything. Maybe you need some firmware? I doubt that. As I said before, everything was working well before and all of sudden, all of my debian devices seemed to fail to get any network. Eave you checked from lspci -n if the module of the kernel is the correct one? I think it is but I don't fully understand what you mean or how to get this answer from the /lspci -n/ output. Also, I don't believe the OP states which version of Debian this is a problem with, but testing is now moving towards systemd-style persistent network names. That is, something like enp1s4 (EtherNet on Pci-bus 1, Slot 4). If the OP is me - I don't know what it means :), I did : wheezy. Kind regards, -- Jean-Philippe MENGUAL HYPRA, progressons ensemble Tél.: 01 84 73 06 61 Mail: cont...@hypra.fr Site Web: http://hypra.fr -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55ba71d8.2010...@free.fr
Re: eth0 : no such device
On Thu, Jul 30, 2015 at 03:29:01PM +0200, Diogene Laerce wrote: Hi, Le 29/07/2015 20:37, MENGUAL Jean-Philippe a écrit : ...snip... Eave you checked from lspci -n if the module of the kernel is the correct one? I think it is but I don't fully understand what you mean or how to get this answer from the /lspci -n/ output. Why did you write /lspci -n/ when the instruction was lspci -n? Did you try it without the fwd slash? -- Bob Holtzman A fair fight is the result of poor planning. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150730213902.ga14...@cox.net
Re: eth0 : no such device
On Wednesday 29 July 2015 18:09:36 Diogene Laerce wrote: Hi, I have big issues recently with debian that I don't understand, maybe someone could help on the matter ? First, debian does not want to give me any network. I really say debian because I have 3 possibilities to run the OS : 2 USB sticks and a PC tower, all on wheezy, which worked fine til they do not for no reason. The one USB stick which does boot and run says, when /ifconfig eth0 up/ : eth0: ERROR while getting interface flags: no such device The other stick now even doesn't want to start X (but that I guess is not related, surely USB stick issue). And the tower.. I had to install fedora because it didn't want to mount my home during installation - which was a new 1To disk to format, even after formatted it which gparted. Plus the unavailable network issue of course, also during installation. These network issues only happen with debian as I could install fedora with no issue at all : it took care of my home and found the network without raising any flag. Any idea ? Did you do anything to your network device(s)? New anything? New card? Did you move anyhting? What is the physical relationship, if any, between the USB sticks and the tower? What happens with a new Debian installation? What does /etc/network/interfaces say? What is the result of #ifconfig -a ? Could you post both those. Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201507301735.12526.lisi.re...@gmail.com
Re: eth0 : no such device
On Wed, Jul 29, 2015 at 08:37:31PM +0200, MENGUAL Jean-Philippe wrote: Hi, What's the result of dmesg? In particular: dmesg|grep .fw? Maybe you need some firmware? Eave you checked from lspci -n if the module of the kernel is the correct one? Also, I don't believe the OP states which version of Debian this is a problem with, but testing is now moving towards systemd-style persistent network names. That is, something like enp1s4 (EtherNet on Pci-bus 1, Slot 4). Regards, Le 29/07/2015 19:09, Diogene Laerce a écrit : Hi, I have big issues recently with debian that I don't understand, maybe someone could help on the matter ? First, debian does not want to give me any network. I really say debian because I have 3 possibilities to run the OS : 2 USB sticks and a PC tower, all on wheezy, which worked fine til they do not for no reason. The one USB stick which does boot and run says, when /ifconfig eth0 up/ : eth0: ERROR while getting interface flags: no such device The other stick now even doesn't want to start X (but that I guess is not related, surely USB stick issue). And the tower.. I had to install fedora because it didn't want to mount my home during installation - which was a new 1To disk to format, even after formatted it which gparted. Plus the unavailable network issue of course, also during installation. These network issues only happen with debian as I could install fedora with no issue at all : it took care of my home and found the network without raising any flag. Any idea ? Thank you, -- Jean-Philippe MENGUAL HYPRA, progressons ensemble Tél.: 01 84 73 06 61 Mail: cont...@hypra.fr Site Web: http://hypra.fr -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55b91d6b.20...@free.fr -- For more information, please reread. signature.asc Description: Digital signature
Re: eth0 : no such device
Hi, What's the result of dmesg? In particular: dmesg|grep .fw? Maybe you need some firmware? Eave you checked from lspci -n if the module of the kernel is the correct one? Regards, Le 29/07/2015 19:09, Diogene Laerce a écrit : Hi, I have big issues recently with debian that I don't understand, maybe someone could help on the matter ? First, debian does not want to give me any network. I really say debian because I have 3 possibilities to run the OS : 2 USB sticks and a PC tower, all on wheezy, which worked fine til they do not for no reason. The one USB stick which does boot and run says, when /ifconfig eth0 up/ : eth0: ERROR while getting interface flags: no such device The other stick now even doesn't want to start X (but that I guess is not related, surely USB stick issue). And the tower.. I had to install fedora because it didn't want to mount my home during installation - which was a new 1To disk to format, even after formatted it which gparted. Plus the unavailable network issue of course, also during installation. These network issues only happen with debian as I could install fedora with no issue at all : it took care of my home and found the network without raising any flag. Any idea ? Thank you, -- Jean-Philippe MENGUAL HYPRA, progressons ensemble Tél.: 01 84 73 06 61 Mail: cont...@hypra.fr Site Web: http://hypra.fr -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55b91d6b.20...@free.fr
Re: eth0: no such device
Jan Hauke Rahm wrote: Hey ihr, ich muss hier mal ein Problem los werden: Sarge installiert mit Netinstall, Upgrade auf Etch, Kernelwechsel -everydays work - sollte man meinen... Mit den Kerneln 2.6.16 und 2.6.17 (aus Etch) läuft die Netzwerkkarte nicht und ich habe drei verschiedene(!) probiert; zuletzt eine Realtek RTL 8139. Im Detail: lspci zeigt alle Karten richtig an. lsmod nennt alle nötigen Module (verglichen mit 2.6.8, wo's lief). grep eth /var/log/dmesg spuckt nichts aus. Ich bin ratlos. Any hints? Hauke Hallo Hauke, nur so ins blaue rein geschossen ich hatte vor kurzem event. ein aehnliches Problem. Subject auf der Liste : MII Problem / MII transceiver Wenn eine RTL 8139 nicht funzt, muss schon etwas gaanz faul sein ;) Nach einem Bios Update war mein Problem geloest ... Gruesse, micha -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: eth0: no such device
Am Dienstag, den 19.09.2006, 22:44 +0200 schrieb Michael Frank: nur so ins blaue rein geschossen ich hatte vor kurzem event. ein aehnliches Problem. Subject auf der Liste : MII Problem / MII transceiver Wenn eine RTL 8139 nicht funzt, muss schon etwas gaanz faul sein ;) Nach einem Bios Update war mein Problem geloest ... Komischerweise läuft's ja mit 2.6.8. Naja, ich hab eben gesehen, dass udev in neuerer Version nach Etch gewandert ist. Und nahezu gleichzeitig rief mich der Bekannte an, bei dem ich installiert hatte; er hat neu installiert (wieder mit sarge). Vielleicht wage ich jetzt - mit frischem System und neuem udev - einen zweiten Versuch. Danke für Hilfe und Tipps! Hauke -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: eth0: no such device
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Jan Hauke Rahm schrieb: Ich bin ratlos. Any hints? ja. kann es sein, dass du irgendwas Grundsätzliches in der Kernel Konfiguration vergessen hast? was sagt lsmod sowie lspci genau? - -- * Stefan Bauer * * Bavaria / Germany / Chiemsee * * [EMAIL PROTECTED] * * GPG ID: D5176489 * * www.plzk.de . www.plzk.com . www.lug-ts.de * * * -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (MingW32) iD8DBQFFDtEeAtCt2tUXZIkRCi3RAJ9S759PPgl4NPPN0EbLhdrroVp5fwCfd3dm XeOgqVdUVtKCIYSKG5wg9do= =szWH -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature
Re: eth0: no such device
kann es sein, dass du irgendwas Grundsätzliches in der Kernel Konfiguration vergessen hast? Eigentlich nicht - ich hab die Config nicht gemacht; das waren die Debian-Maintainer ;-) Soll heißen: Alle verwendeten Kernel sind die installierten Images aus Stable und Testing. was sagt lsmod sowie lspci genau? Hab ich gerade nicht hier, weil ich nicht dran sitze. lspci hat aber bei allen Karten und allen Kerneln brav ein sehr plausibles Bild von der Karte wiedergegeben. Und Realtek kenne ich; der Eintrag sah sehr gut aus. lsmod müsste ich erneut nachschauen, war aber - was die Karten betrifft - bei den beiden neueren identisch zu 2.6.8, wo's ja lief. Persönlich tippe ich eher auf udev als Ursache, weiß ich aber nicht. Die aktuelle Netinstall konnte auf jeden Fall auch nix mit den Karten anfangen. Hauke PS: Sorry an Stefan für die PM! War die falsche Tastenkombination. -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
RE: eth0 no such device
I believe I have correct driver. Thanks for any advice. Start by telling uss what card it is, and what chipset it uses. If it is a PCI device, you should with almost complete certanty _not_ add anything to lilo.conf. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: eth0 no such device
You need to have the drivers for your card either in the kernel or in a module and load that module. I suggest you generate a custom kernel by installing the source and following the directions in the README. You will be able to configure it to support your network card specifically that way. Jim. Ken Januski wrote: Hi, Can anyone give me any clues on how to get my ethernet card working. It works on W2K on other partition so I know card is fine. I've added append parameters to lilo.conf which I think are correct. And I believe I have correct driver. But everything I do gives me this error: eth0 no such device. I'm sure I'm missing something obvious but I just don't know what. I did look at /dev/MAKEDEV and it tells me network devices are in /proc/net/dev. But that file is empty. So I'm really not sure where to go next. Thanks for any advice. Ken -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
