You are not logged in.
Pages: 1
Topic closed
I decided to re-install arch on my Lenovo g50-70.
Executing the following command on the archboot iso
ip link show
listed 3 interfaces "lo, enp1s0, wlp2s0".
I was able to use my wired connection after executing
rfkill unblock all
and install arch successfully.
I booted into my fresh install, tried
ip link show
and enp1s0 and wlp2s0 were missing. I used my archboot iso to get on the network and install rfkill with arch-chroot, but when I booted back into my fresh install and tried running
rfkill unblock all
or
rfkill list
I got the message "Can't open RFKILL device: No such file or directory". I'm stuck and not sure what to do now.
Last edited by cdy (2014-10-17 01:55:31)
Offline
If the interfaces aren't showing then rfkill is irrelevant, you need to install the drivers for the device. Follow the wireless page on the wiki to figure out what those are.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
Don't know why you need rfkill, the devices for the network were present before you executed the rfkill command. Not sure why you're going that route. dhclient enpxxx will usually get you a connection, assuming you have dhcp on your network.
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
If the interfaces aren't showing then rfkill is irrelevant, you need to install the drivers for the device. Follow the wireless page on the wiki to figure out what those are.
Running "lspci -k" on the archboot iso gives me "rtl8723be" for my PCIe Wireless Network Adapter and "r8169" for the PCI Express Gigabit Ethernet Controller (rev 10).
The page, https://wiki.archlinux.org/index.php/Wi … d_firmware , says "rtl8723be" is included in the kernel since 3.15.
What do I need to do?
EDIT:
Following the bottom of https://wiki.archlinux.org/index.php/HC … rs_(Wired) I tried:
pacman -S r8168
echo "blacklist r8169" > /etc/modprobe.d/r8169_blacklist.conf
but that didn't seem to help
Last edited by cdy (2014-10-17 00:16:40)
Offline
You shouldn't need to blacklist the ethernet card to get the wifi to work.
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
You shouldn't need to blacklist the ethernet card to get the wifi to work.
What do I need to do then?
Offline
Is rtl8723be in loaded in the installed system? (run `lsmod | grep rtl8723be`)
If not, can you load it? (`modprobe rtl8723be' as root or with sudo)
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
Both "lsmod | grep rtl8723be" and "modprobe rtl8723be" display nothing.
Offline
You had the interface show up before you executed the rfkill so if the module was loaded you don't to follow the blacklist step. You'll probably need to reverse anything you've tried so far (blacklisting, and rfkill) before proceeding. If both interfaces were showing up, I don't know why you're going the way you're going. If you re-install a fresh arch installation, you'll have to add back the parts that you've obviously forgotten about to make things bring themselves back up after every reboot. Such as a netctl script for each wifi router you intend to use, or copying ethernet-dhcp so that wired will work. dhcpcd/dhclient on your ethernet interface should bring it up.
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
You had the interface show up before you executed the rfkill so if the module was loaded you don't to follow the blacklist step. You'll probably need to reverse anything you've tried so far (blacklisting, and rfkill) before proceeding. If both interfaces were showing up, I don't know why you're going the way you're going. If you re-install a fresh arch installation, you'll have to add back the parts that you've obviously forgotten about to make things bring themselves back up after every reboot. Such as a netctl script for each wifi router you intend to use, or copying ethernet-dhcp so that wired will work. dhcpcd/dhclient on your ethernet interface should bring it up.
No, the interfaces show up when I'm using the archboot iso. When I go into my actual install, they are gone. You've misread my post.
I looked inside /usr/lib/modules/3.16.4-1-ARCH/kernel/net/wireless/ and there is no rtlwifi folder like there is on the archboot iso.
EDIT:
I think I'm somehow running a different kernel than the one pacman is getting modules for.
"pacman -Qi linux" tells me the version is 3.16.4-1, but "uname -r" and "cat /proc/version" both say 3.16.1.
Any idea how I can fix this?
Last edited by cdy (2014-10-17 01:27:32)
Offline
You've forgotten to mount /boot when you last updated the kernel.
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
You've forgotten to mount /boot when you last updated the kernel.
Yeah just mounted it and re-ran
sudo pacman -S linux
Rebooted and now it's fixed. Thanks!
Offline
nomorewindows wrote:You've forgotten to mount /boot when you last updated the kernel.
Yeah just mounted it and re-ran
sudo pacman -S linux
Rebooted and now it's fixed. Thanks!
I'm sure I'm being super dense, but I don't know if I'm understanding what you mean by mounting /boot.
This is what I'm getting.
mount /boot
mount: can't find /boot in /etc/fstab
And when I try to get the uuid with
ls -l /dev/disk/by-uuid
I don't see a reference to /boot. How am I supposed to add it to my fstab?
Edit:
I've also tried
$ lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
├─sda1 vfat EFI 67E3-17ED
├─sda2 hfsplus Macintosh HD 26ff8b30-732b-329d-99fe-aa00493c9b1f
├─sda3 hfsplus Recovery HD 22be4c40-6473-3fa6-9748-d006672c6101
├─sda4 swap 228548e8-d797-460a-b141-692f7011bc0c [SWAP]
└─sda5 ext4 c0b1eb2b-ed87-4d0e-bf08-b7bfd81be877 /
Last edited by austincrft (2016-06-30 22:06:07)
Offline
Please don't hijack, especially a solved thread: https://wiki.archlinux.org/index.php/Co … _hijacking
Closing
Offline
Pages: 1
Topic closed