Re: kde fully broken in debian/testing
On 07/30/2015 02:27 PM, Hans wrote: Am Donnerstag, 30. Juli 2015, 22:34:55 schrieb Gabriel Corona: Hi, Hello, yeah, I am still trying to fix it. The problem is, that many version 5 packages are still not in testing. Instead of this, the repo-maintainers removed many version-4-packages, so you cannot go back. Sigh! I hope, they will put it back, as at the moment, KDE is fully unusable. I tried to install from sid, but the same problem here: packages missing, bad versions, same pita. Somebody told, to use the repo from aptosid, these shall run. Hope this will be fixed soon. Best Hans For my needs kde-plasma-desktop is completely functional, except kdf/kwikdisk has not been upgraded yet but kdiskfree is still functional and system sounds are not playing, but movie and music audio are playing. I have upgraded 3 sid systems(I'm not using experimental or siduction), in synaptic I click install or reinstall kde-plasma-desktop and let it go..It works for me. :) My Plasma 5: https://flic.kr/p/wFfKs4 In testing 'kde runtime' has not been upgraded and is a needed package, it's still kde 4, but I have upgraded all that I can to plasma 5. libkf5 and libqt5 are complete plus many more, but plasma-desktop in testing is still dysfunctional, but fun to play with. :) -- Jimmy Johnson Debian Stretch - KDE 4.14.2 - AMD 64 - EXT4 at sda12 Registered Linux User #380263 -- 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/55baf6c0.2090...@gmail.com
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: VLAN config on Jessie
> Date: Thu, 30 Jul 2015 21:43:25 +0100 > From: aw...@comms.org.uk > > Ive got a Jessie machine acting as a router with eth0 being the WAN > connection to the internet and eth1 being the LAN connection with 2 > VLANS on it (VLAN1 has addresses 192.168.10.x and VLAN2 192.168.100.x) Your /e/n/interfaces does not match that description... > auto eth1 > iface eth1 inet static > address 192.168.10.254 > broadcast 192.168.10.255 > netmask 255.255.255.0 > up /etc/network/if-up.d/iptables This configures an untagged connection, which is not the same as vlan 1. Also, there's no need to set that broadcast address manually, it's inferred from the netmask. > auto eth1.2 > iface eth1.2 inet static > address 192.168.100.254 > netmask 255.255.255.0 > vlan-raw-device eth1 > > > I want vlan 1 to be the default hence I decared it as eth1 not eth1.1 That is most likely wrong. You set a "default interface" by configuring the default gateway with the lowest metric. Other than that, there's no "default" between network interfaces. > Whats the correct way to do this please? I would expect you only configure eth1.1 and eth1.2, and leave eth1 itself unconfigured. Or perhaps, if that configuration confuses ifupdown: iface eth1 inet manual up ip link set eth1 up Regards, Arno -- 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/dub130-w4309ea24d2ff0d1ecd7102b8...@phx.gbl
RE: kde fully broken in debian/testing
> From: hans.ullr...@loop.de > Date: Thu, 30 Jul 2015 22:18:18 +0200 > > Hi folks, > > it looks like kde is fully broken in testing and unstable, due to a big > version mismatch in the repo. Yes. It was announced/explained a few days ago: http://perezmeyer.blogspot.nl/2015/07/plasmakf5-testing-situation.html Regards, Arno -- 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/dub130-w57ce0fcddc2783d09d34b6b8...@phx.gbl
Re: Help - 13-year Debian veteran can't install Jessie
On Sun 26 Jul 2015 at 21:46:31 -0500, David Bruce wrote: > 5. (most troubling) - I posted a couple of days ago that I had trouble > with DHCP not working during install, and have had exactly zero > follow-ups (although I did receive one very nice off-list email > suggestion, which unfortunately did not help). Zero follow-ups are not unknown. Even when there are 20+ reponses to a mail the OP is quiescent. One just assumes there is nothing which helps him so there is nothing to respond to. -- 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/20150730214245.gb1...@copernicus.demon.co.uk
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: VLAN config on Jessie
On 07/30/2015 01:43 PM, Andrew Wood wrote: Can I please clarify the correct way to configure VLANS on Jessie as Im having problems with DHCPD giving out IP addresses for the wrong VLAN subnet but only for certain clients - Windows 7, & Apple iOS whereas Debian clients and Windows XP clients are working fine. Ive got a Jessie machine acting as a router with eth0 being the WAN connection to the internet and eth1 being the LAN connection with 2 VLANS on it (VLAN1 has addresses 192.168.10.x and VLAN2 192.168.100.x) If I assign addresses statically on the clients its all fine but on Wifi via DHCP the Wifi AP is set to map two separate SSIDs to the two VLANS and in such cases the clients use DHCP. As I say, if a Debian or Windows XP client connects via wifi it works fine but if a Windows 7 client connects to VLAN2s SSID DHCPD is giving it an IP on VLAN1 and then nothing works. This is the /etc/network/interfaces file: auto eth0 iface eth0 inet dhcp #LAN (MZ) auto eth1 iface eth1 inet static address 192.168.10.254 broadcast 192.168.10.255 netmask 255.255.255.0 up /etc/network/if-up.d/iptables auto eth1.2 iface eth1.2 inet static address 192.168.100.254 netmask 255.255.255.0 vlan-raw-device eth1 I want vlan 1 to be the default hence I decared it as eth1 not eth1.1 however I did try that and it reversed the problem - vlan1 gets vlan2 ip addresses! Whats the correct way to do this please? Thanks Andrew Could you post the DHCPD config? Matt Ventura -- 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/55ba985a.1070...@mattventura.net
Re: kde fully broken in debian/testing
Am Donnerstag, 30. Juli 2015, 22:34:55 schrieb Gabriel Corona: > Hi, Hello, yeah, I am still trying to fix it. The problem is, that many version 5 packages are still not in testing. Instead of this, the repo-maintainers removed many version-4-packages, so you cannot go back. Sigh! I hope, they will put it back, as at the moment, KDE is fully unusable. I tried to install from sid, but the same problem here: packages missing, bad versions, same pita. Somebody told, to use the repo from aptosid, these shall run. Hope this will be fixed soon. Best Hans > > In fact, I did the update yesterday. It was quite painful but it's now > working OK-ish: > > * You need to move all the plasma packages to the version 5 (I'm >using testing so I had to force the packar manager to use them). > > * Check that you have powerdevil, plasma-desktop, kdeartwork, etc in >version 5. > > * Purge the old plasma packages. > > * You need to restart the session (otheriwse it's compltely broken); > > * I added a `kwin` script in my path (doing 'exec kwin_init "$@"). >It's probably not needed if you have updated all your packages but >at some point I did not have window decoration and adding this >fixed it. It was probably because I was still using some Plasma 4 >packages. > > * I had to manually launch kbuildsycoca5 (otherwise systemsettings >wouldn't display any configuration panel). > > Some remaining issues: > > * systemsettings segaults sometimes but it's mostly working. > > * There is not support for XEmbed systray by design: xchat, hexchat, >nm-applet, etc. are quite broken. We're supposed to fill a lot of >bugs in a log of packages in order to have SNI support in the >applications. I used trayer [1] in order to have a systray. > > Good luck! > > [1] http://www.gabriel.urdhr.fr/2015/07/29/i-can-has-systray/ > > -- > Gabriel -- 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/7694366.sZ9u9E3Ifs@protheus2
VLAN config on Jessie
Can I please clarify the correct way to configure VLANS on Jessie as Im having problems with DHCPD giving out IP addresses for the wrong VLAN subnet but only for certain clients - Windows 7, & Apple iOS whereas Debian clients and Windows XP clients are working fine. Ive got a Jessie machine acting as a router with eth0 being the WAN connection to the internet and eth1 being the LAN connection with 2 VLANS on it (VLAN1 has addresses 192.168.10.x and VLAN2 192.168.100.x) If I assign addresses statically on the clients its all fine but on Wifi via DHCP the Wifi AP is set to map two separate SSIDs to the two VLANS and in such cases the clients use DHCP. As I say, if a Debian or Windows XP client connects via wifi it works fine but if a Windows 7 client connects to VLAN2s SSID DHCPD is giving it an IP on VLAN1 and then nothing works. This is the /etc/network/interfaces file: auto eth0 iface eth0 inet dhcp #LAN (MZ) auto eth1 iface eth1 inet static address 192.168.10.254 broadcast 192.168.10.255 netmask 255.255.255.0 up /etc/network/if-up.d/iptables auto eth1.2 iface eth1.2 inet static address 192.168.100.254 netmask 255.255.255.0 vlan-raw-device eth1 I want vlan 1 to be the default hence I decared it as eth1 not eth1.1 however I did try that and it reversed the problem - vlan1 gets vlan2 ip addresses! Whats the correct way to do this please? Thanks Andrew -- 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/55ba8c6d.7050...@comms.org.uk
Re: kde fully broken in debian/testing
Hi, In fact, I did the update yesterday. It was quite painful but it's now working OK-ish: * You need to move all the plasma packages to the version 5 (I'm using testing so I had to force the packar manager to use them). * Check that you have powerdevil, plasma-desktop, kdeartwork, etc in version 5. * Purge the old plasma packages. * You need to restart the session (otheriwse it's compltely broken); * I added a `kwin` script in my path (doing 'exec kwin_init "$@"). It's probably not needed if you have updated all your packages but at some point I did not have window decoration and adding this fixed it. It was probably because I was still using some Plasma 4 packages. * I had to manually launch kbuildsycoca5 (otherwise systemsettings wouldn't display any configuration panel). Some remaining issues: * systemsettings segaults sometimes but it's mostly working. * There is not support for XEmbed systray by design: xchat, hexchat, nm-applet, etc. are quite broken. We're supposed to fill a lot of bugs in a log of packages in order to have SNI support in the applications. I used trayer [1] in order to have a systray. Good luck! [1] http://www.gabriel.urdhr.fr/2015/07/29/i-can-has-systray/ -- Gabriel -- 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/20150730203455.GA13738@marvin
kde fully broken in debian/testing
Hi folks, it looks like kde is fully broken in testing and unstable, due to a big version mismatch in the repo. There is 4.* and 5.* version mixed. If you did accidently an update, kde will be broken afterwards. As the older 4.* packages are no more in the repo, you will have no choice of going back. So DO NOT UPGRADE ANY KDE PACKAGES for now! Hope, this will be fixed soon, If someone has a better solution, please tell it. Best regards Hans -- 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/1812294.RHb855zaJ4@protheus2
Re: Suspend-sedation Problem
I wasn't reloading the script properly. Still doesn't work, but now I see that the "if" is dropping through because rtcwake always returns "alarm: on" even though it must have expired because the script is running. I still get the incomprehensible "file exists" message. -- John Hasler jhas...@newsguy.com Elmwood, WI USA -- 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/87io91e95s@thumper.dhh.gt.org
Re: recommended imapd?
Arthur Marsh wrote on 31/07/15 02:26: I finally removed the long-unsupported uw-imapd and have so far been unsuccessful setting up a replacement that is available in Debian. Currently I have mailutils-imap4d installed but am unsure of configuration needed. All it needs to do is to access the files in /var/mail/user and be accessible from icedove 38.0.1 (running Debian unstable i386 here) with reasonably straightforward configuration. Arthur. After doing: [DOWNGRADE] icedove:i386 38.0.1-1 -> 38.0~b5-1 [DOWNGRADE] icedove:i386 38.0~b5-1 -> 31.7.0-1 IMAP is working with mailutils-imap4d 1:2.99.98-2 (not securely, but it's all restricted to the one machine). It appears that icedove 38.x was misbehaving. Arthur. -- 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/55ba6093.6010...@internode.on.net
Re: recommended imapd?
On Qui, 30 Jul 2015, Arthur Marsh wrote: I finally removed the long-unsupported uw-imapd and have so far been unsuccessful setting up a replacement that is available in Debian. Currently I have mailutils-imap4d installed but am unsure of configuration needed. All it needs to do is to access the files in /var/mail/user and be accessible from icedove 38.0.1 (running Debian unstable i386 here) with reasonably straightforward configuration. Take a look at dovecot. It's quite powerful and should be straightforward to setup for this use case. -- Eduardo M KALINOWSKI edua...@kalinowski.com.br -- 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/20150730170249.horde._e1g87bialgiuywp4l1s...@mail.kalinowski.com.br
Re: recommended imapd?
Le 30/07/2015 18:56, Arthur Marsh a écrit : > I finally removed the long-unsupported uw-imapd and have so far been > unsuccessful setting up a replacement that is available in Debian. > > Currently I have mailutils-imap4d installed but am unsure of > configuration needed. > > All it needs to do is to access the files in /var/mail/user and be > accessible from icedove 38.0.1 (running Debian unstable i386 here) > with reasonably straightforward configuration. > > Arthur. > > I use dovecot, works well with maildir storage, but mbox is also supported : note that mbox format is very bad for performance. -- 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/55ba5882.8070...@rail.eu.org
Re: Suspend-sedation Problem
Additional information: "systemctl suspend" produces exactly the same result as closing the lid except of course that the machine does not go back into suspension after the script runs. "systemctl hibernate" produces exactly the same result as "systemctl suspend" except that the machines goes into hibernation for the time set in the script rather than into suspension. -- John Hasler jhas...@newsguy.com Elmwood, WI USA -- 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/87mvydeg2u@thumper.dhh.gt.org
recommended imapd?
I finally removed the long-unsupported uw-imapd and have so far been unsuccessful setting up a replacement that is available in Debian. Currently I have mailutils-imap4d installed but am unsure of configuration needed. All it needs to do is to access the files in /var/mail/user and be accessible from icedove 38.0.1 (running Debian unstable i386 here) with reasonably straightforward configuration. Arthur. -- 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/ij1q8c-18a@ppp14-2-48-242.lns21.adl2.internode.on.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: post-up in interfaces doesn't work
Hi Mojtaba, > Van: Mojtaba [mailto:ker...@rp2.org] > I have a brand new jessie setup in a KVM VPS. > The server is in OVH network which needs manual routing applied. > However the post-up and setting in the /etc/network/interfaces is not > executed This is my interfaces file > auto eth0 > iface eth0 inet static > address 198.50.210.32 > netmask 255.255.255.255 > broadcast 198.50.210.32 > #gateway192.99.39.254 > post-up route add 192.99.39.254 dev eth0 post-up route add default gw > 192.99.39.254 post-down route del 192.99.39.254 dev eth0 post-down route del > default gw 192.99.39.254 > I've tried a simple 'echo working > /testfile.txt' line but the post-up or > pre-up is not executed Is there anything I'm missing? It might be reformatting due to the email posting but... Did you proper indent the lines below the iface eth0 ... line? Also, my post-up lines look similar but I use the ip route add via command. Lastly, I do not understand how your routing is supposed to work. Unless... read on. Eth0 connects to a network where the host ip number = the network ip number = the network broadcast ip number. This looks like an illegal config. If you want to tell your system that 192.99.39.254 is also behind eth0 then how is your system supposed to communicate with it? They have no common network address? Unless If they are on the same LAN / line (dial up PPP, etc) and should communicate using layer 2 then the pointopoint config is indeed what you want. Bonno Bloksma
How to automate away partition prompt in preseeded Jessie auto-intall?
Hi, I'm trying preseeded installation with the Jessie netinst CD ISO. Everything seems to work fine, except one prompt that still stalls until manual confirmation for the drive to erase/format/use for target installation. My preseed file and the screenshot of the dailog prompt can be found at the following URL: https://drive.google.com/open?id=0B9-tBo8X88GLfllQZURQQ3NyMTkzUzlHRDFYc1hVeGlVZU5iQWpodFIzVkxwTkF6YXc5TGM Details: * Installation is being done inside a KVM instance on my laptop. * Network is provided by VDE (Virtual Distributed Ethernet) * Preseed file is being served via a python SimpleHTTPServer invocation * KVM instances can access both the host (hypervisor) and the internet KVM invocation: (single command line) kvm -drive file=debian-8.1.0-amd64-netinst.iso,media=cdrom -drive if=virtio,file=test-install.qcow2,media=disk -netdev vde,id=net0 -device virtio-net,mac=52:54:00:12:13:15,netdev=net0 -m 256 -boot once=d Here are the lines relevant to the partitioning portion from the preseed # Partitioning d-i partman-auto/init_automatically_partition select biggest_free # Still prompts for confirmation even after specifying d-i partman-auto/disk string /dev/vda # Also tried with /dev/sda (with KVM IDE interface emulation) # A total shot in the dark, obviously didn't work #d-i partman-auto/confirm boolean true d-i partman-lvm/device_remove_lvm boolean true d-i partman-md/device_remove_md boolean true d-i partman-lvm/confirm boolean true d-i partman-lvm/confirm_nooverwrite boolean true d-i partman-auto/choose_recipe select atomic d-i partman-partitioning/confirm_write_new_label boolean true d-i partman/choose_partition select finish d-i partman/confirm boolean true d-i partman/confirm_nooverwrite boolean true d-i partman-md/confirm boolean true d-i partman-partitioning/confirm_write_new_label boolean true d-i partman/choose_partition select finish d-i partman/confirm boolean true d-i partman/confirm_nooverwrite boolean true This singular prompt is the only hitch in the completely automated installation. Directions/pointers appreciated. Regards, Didar -- 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/20150730133511.GA26561@mylappy
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
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
