Intel I217LM ethernet controller not detected

Intel I217LM ethernet controller not detected

Solution

The Linux* e1000e driver supports PCI Express* Gigabit Network Connections except the 82575, 82576, 82580, and I350.

Download e1000e
Overview
Building and installation
For information concerning driver configuration details, refer to the Read Me file in the Download Center.


Overview

The Linux* base drivers support the 2.4.x and 2.6.x kernels. They include support for Itanium® 2-based systems.

The drivers are only supported as a loadable module. We don't supply patches against the kernel source to allow for static linking of the drivers. For questions related to hardware requirements, see the documentation supplied with your Intel® Gigabit Network Adapter. All hardware requirements listed apply for use with Linux.

Features now available in supported kernels:

Native VLANs
Channel Bonding (teaming)
SNMP
Find Channel Bonding documentation in the Linux kernel source: /documentation/networking/bonding.txt

This release doesn't support the driver information previously displayed in the /proc file system. You can also use ethtool (version 1.6 or later), lspci, and ifconfig to get the same information. Find instructions on updating ethtool in the additional configurations section.

Note The Intel® 82562v 10/100 Network Connection only provides 10/100 support.
back to top back to top

Building and installation

To build a binary RPM* package of this driver, run rpmbuild -tb e1000e.tar.gz.

Notes
For the build to work properly, the currently running kernel must match the version and configuration of the installed kernel sources. If you have just recompiled the kernel, reboot the system.

RPM functionality was only tested in Red Hat distributions.

Download current e1000e package from Download Center or SourceForge. Move the base driver tar file to the directory of your choice. For example, use "/home/<USERNAME>/e1000e" or "/usr/local/src/e1000e".

Untar/unzip the archive, where <x.x.x> is the version number for the driver tar file:

tar zxf e1000e-<x.x.x>.tar.gz
Change to the driver src directory, where <x.x.x> is the version number for the driver tar:

cd e1000e-<x.x.x>/src/
Compile the driver module:

# make install
The binary installs as:

/lib/modules/<KERNEL VERSION>/kernel/drivers/net/e1000e/e1000e.[k]o
The install location listed above is the default. Location may differ for various Linux distributions.

Load the module using either the insmod or modprobe command:

modprobe e1000e insmod e1000e
Note that you can use the insmod command for 2.6 kernels if you specify the full path to the driver module. For example:

insmod /lib/modules/<KERNEL VERSION>/kernel/drivers/net/e1000e/e1000e.ko
With 2.6 based kernels, make sure that older e1000e drivers are removed from the kernel before you load the new module:

rmmod e1000e; modprobe e1000e
Assign an IP address to the interface by entering the following, where <x> is the interface number:

ifconfig eth<x> <IP_address>
Verify that the interface works. Enter the following, where <IP_address> is the IP address for another machine on the same subnet as the interface you are testing:

ping <IP_address>

Note
Some systems have trouble supporting MSI and/or MSI-X interrupts. If your system must disable this style of interrupt, build and install the driver with the command:

# make CFLAGS_EXTRA=-DDISABLE_PCI_MSI install
Normally the driver generates an interrupt every two seconds If you're no longer seeing interrupts in cat /proc/interrupts for the ethX e1000e device, then this workaround may be necessary.

Reference :
Intel site

Your boot partition is on a disk using the GPT partitioning scheme but this machine cannot boot using GPT

Your boot partition is on a disk using the GPT partitioning scheme but this machine cannot boot using GPT

Following error after telling anaconda to install on pre-existing partitions (with GPT label):

On Partitioning screen, press Ctrl + Alt + F2 to get to a shell prompt.

$ parted /dev/sda -s mklabel msdos

Press Ctrl + Alt + F6 to return to the partitioning screen

SP2-0618: Cannot find the Session Identifier. Check PLUSTRACE role is enabled

SP2-0618: Cannot find the Session Identifier. Check PLUSTRACE role is enabled

 

ISSUE: 

SQL> set autotrace traceonly;

SP2-0618: Cannot find the Session Identifier. Check PLUSTRACE role is enabled

SP2-0611: Error enabling STATISTICS report

SOLUTION:

Users needs to have the PLUSTRACE role, which does not exist by default.

PLUSTRACE role can be created using SYS user by executing

ORACLE_HOME\sqlplus\admin\plustrce.sql 

The plustrace.sql creates the PLUSTRACE role

It also grants SELECT on V_$SESSTAT, V_$STATNME and V_$MYSTAT. 

PLUSTRACE is granted to the DBA role with ADMIN OPTION.

For 9i and earlier databases you may also need to create the plan table

by executing following script:-

$ORACLE_HOME\rdbms\admin\utlxplan.sql 

The PLAN_TABLE already exists on database version 10g and higher.

SQL> connect sys/sys as sysdba

Connected.

SQL> @%oracle_home%\sqlplus\admin\plustrce.sql;

SQL>

SQL> drop role plustrace;

drop role plustrace

          *

ERROR at line 1:

ORA-01919: role 'PLUSTRACE' does not exist

SQL> create role plustrace;

Role created.

SQL> grant select on v_$sesstat to plustrace;

Grant succeeded.

SQL> grant select on v_$statname to plustrace;

Grant succeeded.

SQL> grant select on v_$mystat to plustrace;

Grant succeeded.

SQL> grant plustrace to dba with admin option;

Grant succeeded.

After executing ORACLE_HOME\sqlplus\admin\plustrce.sql,

we need to grant PLUSTRACE role to the user.

SQL> grant plustrace to scott;

Grant succeeded.

SQL> connect scott/tiger

Connected.

SQL> set autotrace trace 

SQL> select user from dual; 

Execution Plan ----------------------------------------------------------

Plan hash value: 1388734953

----------------------------------------------------------------- 

| Id | Operation | Name | Rows | Cost (%CPU)| Time | 

-----------------------------------------------------------------

 | 0 | SELECT STATEMENT 

| | 1 | 2 (0)| 00:00:01 | | 1 | FAST DUAL | | 1 | 2 (0)| 00:00:01 | 

-- Statistics --------- 1 recursive calls 0 db block gets 

0 consistent gets 0 physical reads 0 redo size 421 bytes 

sent via SQL*Net to client 415 bytes received via 

SQL*Net from client 2 SQL*Net roundtrips to/from 

client 0 sorts (memory) 0 sorts (disk) 1 rows processed

RC-20200: Fatal: Could not find Unzip. At this time only Native UnZip 5.X is supported.

RC-20200: Fatal: Could not find Unzip. At this time only Native UnZip 5.X is supported.

While cloning database Tier

Error :
RC-20200: Fatal: Could not find Unzip. At this time only Native UnZip 5.X is supported.

Please make sure you have UnZip 5.X in your path and try again…

 ERROR while running Apply…

 ERROR: Failed to execute /clone/oracle/product/11.2.0/appsutil/clone/bin/adclone.pl

  Please check logfile.

Solution 1

Which unzip should point to $ORACLE_HOME/bin/unzip

Take the backup of existing unzip from $ORACLE_HOME/bin

cd $ORACLE_HOME/bin

mv unzip unzip_bkp

cp /usr/bin/unzip to $ORACLE_HOME/bin

Make sure the unzip utility under /usr/bin should be of version 5.X and not 6

Solution 2

As root user, rename the default unzip (/usr/bin/unzip) to a temporary filename (e.g. /usr/bin/unzip-ver6), perform the task, and then rename unzip-ver6 to the original name when completed.

# mv /usr/bin/unzip /usr/bin/unzip-ver6

Solution 3

unzip utility
https://oss.oracle.com/el4/unzip/unzip.html


 

While cloning, adcfgclone.pl error:RC-50014: Fatal: Execution of AutoConfig was failed in R12.

While cloning, adcfgclone.pl error:RC-50014: Fatal: Execution of AutoConfig was failed in R12.
When we check the log file we can see the error like below
AutoConfig could not successfully instantiate the following files:


adcrdb.sh INSTE8

AutoConfig is exiting with status 1

RC-50014: Fatal: Execution of AutoConfig was failed


Solution: Copy adcrdb.sh file ($ORACLE_HOME/appsutil/template) from
Source to target ($ORACLE_HOME/appsutil/template) then
we run the adcfgclone.pl dbTier again.