Hi guys, I’m quiet new to linux, so please hold my hands through this complex procedure for I don’t know alot of things about linux. So I got this new PC and decided to try out openSUSE. The problem is the neither the lan driver and my usb wireless driver are prepackaged into version 13.1.
The thing is to compile these I need the kernel-header, but I can’t seem to find a way to install the kernel-header without internet. So this becomes a circular problem for me.
Because my PC is very far away from any LAN connections, so I’d prefer to fix my wireless issue first. However if it is easier to get the LAN working first then I’m all for it.
Thanks for the prompt reply, deano. Here are the outputs of the commands you suggested.
/sbin/lspci -nnk:
sean@kai-desktop:/dev> /sbin/lspci -nnk
00:00.0 Host bridge [0600]: Intel Corporation 4th Gen Core Processor DRAM Controller [8086:0c00] (rev 06)
Subsystem: Micro-Star International Co., Ltd. Device [1462:7915]
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [8086:0c01] (rev 06)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:14.0 USB controller [0c03]: Intel Corporation Device [8086:8cb1]
Subsystem: Micro-Star International Co., Ltd. Device [1462:7915]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_hcd
00:16.0 Communication controller [0780]: Intel Corporation Device [8086:8cba]
Subsystem: Micro-Star International Co., Ltd. Device [1462:7915]
***00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection (2) I218-V [8086:15a1]
Subsystem: Micro-Star International Co., Ltd. Device [1462:7915]***
00:1a.0 USB controller [0c03]: Intel Corporation Device [8086:8cad]
Subsystem: Micro-Star International Co., Ltd. Device [1462:7915]
Kernel driver in use: ehci-pci
00:1b.0 Audio device [0403]: Intel Corporation Device [8086:8ca0]
Subsystem: Micro-Star International Co., Ltd. Device [1462:d915]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:8c90] (rev d0)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.2 PCI bridge [0604]: Intel Corporation Device [8086:8c94] (rev d0)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.3 PCI bridge [0604]: Intel Corporation Device [8086:8c96] (rev d0)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.4 PCI bridge [0604]: Intel Corporation Device [8086:8c98] (rev d0)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1d.0 USB controller [0c03]: Intel Corporation Device [8086:8ca6]
Subsystem: Micro-Star International Co., Ltd. Device [1462:7915]
Kernel driver in use: ehci-pci
00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:8cc4]
Subsystem: Micro-Star International Co., Ltd. Device [1462:7915]
00:1f.2 RAID bus controller [0104]: Intel Corporation 82801 SATA Controller [RAID mode] [8086:2822]
Subsystem: Micro-Star International Co., Ltd. Device [1462:7915]
Kernel driver in use: ahci
00:1f.3 SMBus [0c05]: Intel Corporation Device [8086:8ca2]
Subsystem: Micro-Star International Co., Ltd. Device [1462:7915]
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290] [1002:67b1]
Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e285]
01:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:aac8]
Subsystem: PC Partner Limited / Sapphire Technology Device [174b:aac8]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
03:00.0 SATA controller [0106]: ASMedia Technology Inc. ASM1062 Serial ATA Controller [1b21:0612] (rev 01)
Subsystem: Micro-Star International Co., Ltd. Device [1462:7915]
Kernel driver in use: ahci
lsusb:
sean@kai-desktop:/dev> lsusbBus 001 Device 002: ID 8087:8009 Intel Corp.
Bus 002 Device 002: ID 8087:8001 Intel Corp.
Bus 003 Device 002: ID 174c:2074 ASMedia Technology Inc.
Bus 003 Device 003: ID 0781:5406 SanDisk Corp. Cruzer Micro U3
Bus 004 Device 002: ID 174c:3074 ASMedia Technology Inc.
Bus 003 Device 004: ID 1038:1378 Ideazon, Inc.
Bus 003 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
***Bus 003 Device 006: ID 20f4:805b TRENDnet ***
Bus 004 Device 003: ID 1058:1140 Western Digital Technologies, Inc. My Book Essential USB3.0
You are certainly in between a rock and a hard place
Ultimately, you need a newer e1000e driver than the install kernel version (for openSUSE 13.1) allows. A kernel upgrade is required, but as you’re already aware, it is a chicken-egg situation. You could try using a Live distro with a newer kernel, and use that to download a newer openSUSE kernel package perhaps which you could then install offline in openSUSE.
The pragmatic approach would be to buy a cheap network card, or wireless device that is supported out-of-the-box.
to see if the device is now recognised and active. If that does work, then you’ll want to configure via YaST to get connectivity. From there you could update to a newer kernel that offers support for your NIC.
On 08/14/2014 07:56 PM, deano ferrari wrote:
>
> Code:
> --------------------
> 00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection (2) I218-V
> [8086:15a1]
> Subsystem: Micro-Star International Co., Ltd. Device [1462:7915]
>
> --------------------
>
> You are certainly in between a rock and a hard place
>
> Ultimately, you need a newer e1000e driver than the install kernel
> version (for openSUSE 13.1) allows. A kernel upgrade is required, but as
> you’re already aware, it is a chicken-egg situation. You could try using
> a Live distro with a newer kernel, and use that to download a newer
> openSUSE kernel package perhaps which you could then install offline in
> openSUSE.
>
> The pragmatic approach would be to buy a cheap network card, or wireless
> device that is supported out-of-the-box.
You have the dilemma of early adopters of new hardware. I am the person that
takes Realtek software, and gets it into the shape needed for it to be included
in the kernel. At the moment, I don’t have any RTL8821AU hardware, and I just
downloaded the first software from the Realtek site.
deano, I tried the “desperate” hack. For some reason I can’t write (using sudo) to new_id file even though the file does have write permission for root. However when I did /usr/sbin/hwinfo --netcard, here’s what I got:
I guess I can’t do much about it til I get my hands on another wifi/lan card.
lwfinger, just out of curiosity, approximately how long will it take to get the driver into a pre-packaged kernel? And more specifically on to the openSUSE update server?
malcolm, thanks for the link, I guess I will be needing that once I get some kind of internet connection going.
lwfinger, just out of curiosity, approximately how long will it take to get the driver into a pre-packaged kernel? And more specifically on to the openSUSE update server?
Just remember Larry is referring to the wireless driver. Your LAN card (8086:15a1 chipset) is supported by in-kernel drivers from wards. 3.14.x upwards AFAIU.
On 08/14/2014 11:46 PM, deano ferrari wrote:
>
> SeanKai;2659259 Wrote:
>> Thanks for the suggestions guys.
>>
>> deano, I tried the “desperate” hack. For some reason I can’t write
>> (using sudo) to new_id file even though the file does have write
>> permission for root.
> Try it again, but become root with
>
> Code:
> --------------------
> su -
> --------------------
>
> then the commands.
>
> However when I did /usr/sbin/hwinfo --netcard, here’s what I got
>
>
> Code:
> --------------------
>
> sean@kai-desktop:/sys/bus/pci/drivers/e1000e> /usr/sbin/hwinfo --netcard
> 11: PCI 19.0: 0200 Ethernet controller
> [Created at pci.319]
> Unique ID: kpGf.MXcMENmJXW7
> SysFS ID: /devices/pci0000:00/0000:00:19.0
> SysFS BusID: 0000:00:19.0
> Hardware Class: network
> Model: “Intel Ethernet controller”
> Vendor: pci 0x8086 “Intel Corporation”
> Device: pci 0x15a1
> SubVendor: pci 0x1462 “Micro-Star International Co., Ltd.”
> SubDevice: pci 0x7915
> Memory Range: 0xee300000-0xee31ffff (rw,non-prefetchable)
> Memory Range: 0xee338000-0xee338fff (rw,non-prefetchable)
> I/O Ports: 0xf040-0xf05f (rw)
> IRQ: 4 (no events)
> Module Alias: “pci:v00008086d000015A1sv00001462sd00007915bc02sc00i00”
> Config Status: cfg=no, avail=yes, need=no, active=unknown
>
> --------------------
>
>
>
> So the card is recognized, just not active.
> No, there should be a driver status and driver activation reported,
> similar to this
>
> Code:
> --------------------
> Driver Info #0:
> Driver Status: tg3 is active
> Driver Activation Cmd: “modprobe tg3”
> Config Status: cfg=no, avail=yes, need=no, active=unknown
>
> --------------------
>
>
> I guess I can’t do much about it til I get my hands on another wifi/lan
> card.
>
> lwfinger, just out of curiosity, approximately how long will it take to
> get the driver into a pre-packaged kernel? And more specifically on to the
> openSUSE update server?
If I had a test card, I started today, and I had nothing else to do, the
earliest would be kernel 3.18 or 3.19. Of course, none of the above is true. It
takes about 10 weeks per cycle, and 3.16 was just released; therefore, it would
be 20 or 30 weeks. For a standard distribution kernel, openSUSE 13.3 would be
the earliest, which will be out in about a year.
deano, I will try using the “su” command when I get back.
If I were to get another wireless network adaptor (be it usb or pci-e), what is my best bet on getting a fast connection (say ac rather than n)? Since I would like to read and write large data sets to and from a backup NAS from time to time, I would like my wireless connection to be as fast as possible.
On 08/15/2014 02:56 PM, SeanKai wrote:
>
> deano, I will try using the “su” command when I get back.
>
> If I were to get another wireless network adaptor (be it usb or pci-e),
> what is my best bet on getting a fast connection (say ac rather than n)?
> Since I would like to read and write large data sets to and from a
> backup NAS from time to time, I would like my wireless connection to be
> as fast as possible.
Of course, 802.11ac has the most potential; however, the hardware is rather new,
and the drivers may not be capable. I would suggest using 802.11n for the next
couple of years.
