You are not logged in.
Pages: 1
lspci -v finds the ethernet card, and gives
08:00.0 Ethernet controller: Broadcom Corporation NetLink BCM57780 Gigabit Ethernet PCIe (rev 01)
Subsystem: Lenovo Device 38a2
Flags: bus master, fast devsel, latency 0, IRQ 50
Memory at f4500000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [48] Power Management version 3
Capabilities: [60] Vendor Specific Information: Len=6c <?>
Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [cc] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Virtual Channel
Capabilities: [160] Device Serial Number c8-0a-a9-ff-fe-db-60-3a
Capabilities: [16c] Power Budgeting <?>
Kernel driver in use: tg3
However, ip link shows only
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000
link/ether 00:24:d6:5e:64:d4 brd ff:ff:ff:ff:ff:ff
Arch is the only distribution to have problems with the internet: Fedora and Linux Mint have both worked fine.
I can't use wireless because of a broken antenna on the laptop, so ethernet is the only way to connect to the internet and finish the installation.
I tried as much as I could in the wiki's installation page, but it all seemed to rely on ip link finding the ethernet.
Computer is a Lenovo Ideapad U350
Offline
That card is specifically covered in the wiki: https://wiki.archlinux.org/index.php/Ne … m_BCM57780
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
That method worked on the live medium, but once I chroot onto the hard drive, the ethernet no longer works and the same method does not fix it.
lspci -v doesn't give a kernel driver for the card anymore. The line 'Kernel driver in use: tg3' is not there.
Last edited by JackBob (2014-07-25 14:36:30)
Offline
Odd ... I can't figure why that would happen - but there isn't any real need for networking in the chroot (it can be handy at times, but would never be necessary). Have you tried booting into the new system yet then doing the module unload/load sequence?
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
Will the system reboot without me installing a bootloader? That's what I was trying to use the internet for.
Last edited by JackBob (2014-07-25 14:49:05)
Offline
You can install the bootloader package without the chroot, then chroot and configure.
Offline
How do I install packages onto the hard drive from outside the chroot? If I just try pacman -S --dbpath /mnt/var/lib/pacman grub, it complains that all the files already exist. However, grub has not been installed on the drive, only on the live medium.
Last edited by JackBob (2014-07-25 16:04:23)
Offline
use the --root option
You are using the arch-chroot script, aren't you? If not, you'd have to do some other things to get the network working in the chroot.
Last edited by Scimmia (2014-07-25 16:14:54)
Offline
How do I install packages onto the hard drive from outside the chroot?
You could use pacman's --root flag, but I'd recommend using pacstrap instead - that's exactly what it is for. You've already just installed dozens of packages onto the hard drive from outside the chroot with `pacstrap /mnt base`. My typical install method adds several things to that command, including a bootloader.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
I wouldn't suggest pacstrap for an already installed system. That's not what it's designed for, it's designed to bootstrap a blank dir into something pacman can work with.
Offline
I don't know what I did, but the ethernet in the chroot worked after a reboot. Thanks for your help
Offline
Pages: 1