Jump to content
funtoo forums

Search the Community

Showing results for tags 'network'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Funtoo Discussion Forums
    • News and Announcements
    • General Discussion
    • Dev Central
    • Funtoo Hosting
    • Funtoo Infrastructure
  • Help Central
    • General Help
    • Installation Help
    • Portage Help
    • Desktop Help
    • Server Help
  • Funtoo Services

Blogs

There are no results to display.

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


freenode


github


Location


Interests

Found 4 results

  1. After doing a sucessful emerge -auvDN @world for the first time since the switch to ego (which involved a LOT of pain and masking/unmasking/oneshots due to version differences), my NIC is not working. Due to the very large number of packages updated, I have no idea which one could have caused the malfunction.I'm having to tether my desktop to my phone through USB. I have tried every possible relevant genkernel config, and I even tried patching the atl1c driver by hand to support my card (details below) 03:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 13) Subsystem: Micro-Star International Co., Ltd. [MSI] Killer E220x Gigabit Ethernet Controller Flags: bus master, fast devsel, latency 0, IRQ 46 Memory at fe800000 (64-bit, non-prefetchable) [size=256K] I/O ports at d000 [size=128] Capabilities: [40] Power Management version 3 Capabilities: [58] Express Endpoint, MSI 00 Capabilities: [c0] MSI: Enable+ Count=1/16 Maskable+ 64bit+ Capabilities: [d8] MSI-X: Enable- Count=16 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [180] Device Serial Number ff-85-2b-be-44-8a-5b-ff Kernel driver in use: alx Kernel modules: alx As you can see, the alx network driver recognizes the card, but it provides no connection. NetworkManager shows eth0 going through a loop of trying to connect, failing to get an IP address from DHCP, and pausing for a minute.
  2. Hello! I timed Funtoo current + Xorg + xdm + Slim boot. It is 64 seconds, much more that I had after first installation pure64 + Xorg XFCE. The NetworkManager is the main problem When I deleted NetworkManager and dhcpcd from rc-update. My Slim appeared after 38 seconds. So I think to use wpa_supplicant, but I cannot connect with it. I added dhcpcd to rc-update and rebooted. I tried to use line that worked on Gentoo. Have no sense why it is not working. # rfkill list 0: ideapad_wlan: Wireless LAN Soft blocked: yes Hard blocked: no 1: ideapad_bluetooth: Bluetooth Soft blocked: yes Hard blocked: no 2: phy0: Wireless LAN Soft blocked: yes Hard blocked: no 3: hci0: Bluetooth Soft blocked: yes Hard blocked: no # rfkill unblock 0 # rfkill unblock 2 # cat wpa.sh wpa_supplicant -B -i wlan0 -c<(wpa_passphrase internet password) && dhcpcd wlan0 # ./wpa.sh Successfully initialized wpa_supplicant sending commands to master dhcpcd process # ping -c 5 funtoo.org ping: unknown host funtoo.org # ifconfig eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether xx:xx:xx:xx:xx:xx txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1 (Local Loopback) RX packets 2 bytes 100 (100.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2 bytes 100 (100.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether xx:xx:xx:xx:xx:xx txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 # rc-status -a Runlevel: default dhcpcd [ started ] sshd [ started ] dbus [ started ] xdm [ started ] local [ started ] Runlevel: sysinit sysfs [ started ] devfs [ started ] dmesg [ started ] kmod-static-nodes [ started ] opentmpfiles-dev [ started ] udev [ started ] cgroups [ started ] Runlevel: shutdown savecache [ stopped ] killprocs [ stopped ] mount-ro [ stopped ] Runlevel: boot hwclock [ started ] swap [ started ] modules [ started ] fsck [ started ] root [ started ] mtab [ started ] localmount [ started ] procfs [ started ] loopback [ started ] urandom [ started ] sysctl [ started ] binfmt [ started ] hostname [ started ] bootmisc [ started ] termencoding [ started ] keymaps [ started ] opentmpfiles-setup [ started ] Runlevel: nonetwork local [ started ] Dynamic Runlevel: hotplugged Dynamic Runlevel: needed/wanted modules-load [ started ] xdm-setup [ started ] Dynamic Runlevel: manual Please, is there way to use wpa_supplicant + wpa_passphrase + dhcpcd to connect to wifi via one bash line ?
  3. dirkme

    how to get wireless working

    I have a fresh install of funtoo XFCE4, ethernet network is working fine, but wireless, doesn't show. I used (chroot) # emerge linux-firmware networkmanager (chroot) # rc-update add NetworkManager default and it installed fine. sorry to get you guys thru my birth pain with Funtoo ;-)
  4. Whenever I boot into funtoo, my wifi will only connect for about 2 seconds until losing connection and reconnecting, but I haven't had that problem on the other network I've connected to. Just so you know, I have the problem no matter how strong my signal is. I'm using networkmanager to manage my connections, and I havent edited any config files regarding networking, and my wifi card is a "Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01)" My home wifi has the interface wlp5s0, and is encrypted with a wpa psk passphrase. My network supplier is Uverse, if that's any use to anyone. The other wifi has the interface wlan0 (I'm pretty sure) and I don't know how it's secured, but I needed a passwork to connect. The owner said that's it's very "open" , although I'm not sure what that's supposed to mean. None of these networks are hidden, by the way.
×