problem compling 2.6

tanalam · 06-29-2006, 06:01 AM

hi all,
I was trying to compile and install 2.6.17.1 to my exisitng
FC3 kernel but ....

Before I state my problem I put down the output of fdisk -l

255 heads, 63 sectors/track, 4865 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 2550 20482843+ 7 HPFS/NTFS
/dev/hda2 2551 4865 18595237+ f W95 Ext'd (LBA)
/dev/hda5 2551 4080 12289693+ b W95 FAT32
/dev/hda6 4081 4093 104391 83 Linux
/dev/hda7 4094 4158 522081 82 Linux swap
/dev/hda8 4159 4865 5678946 83 Linux

Disk /dev/hdb: 40.0 GB, 40060403712 bytes
16 heads, 63 sectors/track, 77622 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes

Device Boot Start End Blocks Id System
/dev/hdb1 1 20318 10240240+ c W95 FAT32 (LBA)
/dev/hdb2 20319 36984 8399664 7 HPFS/NTFS
/dev/hdb3 36985 57301 10239768 c W95 FAT32 (LBA)
/dev/hdb4 57302 77618 10239768 c W95 FAT32 (LBA)

I already have FC3 2.6.9-1.667 in "/dev/ha8" with "/dev/hda6" as /boot
I downloaded 2.6.17.1 from kernel .org and uncompressed it in "/dev/hdb3" which I have already formated as EXT3 type (though I do not know why it is still showing W95 FAT32).
-> I did not do any change in the "menuconfig"
-> make bzImage
-> make modules
-> make modules_install
-> mkinitrd /boot/initrd-2.6.17.1 2.6.17.1
-> cp arch/i386/boot/bzImage /boot/bzImage-2.6.17.1
-> cp System.map /boot/System.map-2.6.17.1
-> ln -s /boot/System.map-2.6.17.1 /boot/System.map

After that I made the following changes in /grub/menu.1st
title Fedora Core (2.6.9-1.667)
root (hd0,5)
kernel /vmlinuz-2.6.9-1.667 ro root=LABEL=/12 rhgb quiet
initrd /initrd-2.6.9-1.667.img
#Added afterward
#**********************
title Test Kernel (2.6.0)
root (hd0,5)
kernel /bzImage-2.6.17.1 ro root=(hd0,7)
initrd /initrd-2.6.17.1.img
#************************
title MS Dos
rootnoverify (hd0,0)
chainloader +1

now when I try to boot into the new kernel I get the following errors

->mount: error 6 mountning ext3
->mount : error 2 mounting none
switching to newroot
switchroot : mount failed:22
umount /init/dev/ failed:2
kernel panic- not syncing

TIA
tan..

Lenard · 06-29-2006, 06:26 AM

Quote:

-> I did not do any change in the "menuconfig"

Here's your problem this will not build a good working kernel you need to actually add support your system (hardware iptables filesystem and such). Have a look at the /boot/config-2.6.9-1.667 file and compare it you the one you built
the 2.6.17.1 kernel with. Use the information from 'cat /proc/modules' and 'lspci -v' to assit you in creating a proper configuration (.config) file for your system.

Quote:

-> make bzImage
-> make modules
-> make modules_install
-> mkinitrd /boot/initrd-2.6.17.1 2.6.17.1
-> cp arch/i386/boot/bzImage /boot/bzImage-2.6.17.1
-> cp System.map /boot/System.map-2.6.17.1
-> ln -s /boot/System.map-2.6.17.1 /boot/System.map

Try again this time do the following;

make mrproper
make menuconfig (or gconfig or xconfig) ;remember what I said above
make
make modules_install
make install

Please get used to using 'make' instead of 'make bzImage' and 'make modules', it does both steps and works across most architectures, and does work;

$ uname -a
Linux Aspire5000 2.6.17.1 #1 Sun Jun 25 13:15:35 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux

tanalam · 06-29-2006, 10:36 PM

Thanks for help
One more issue before I move on with your adive
I have also posted the changes in the grub menu that I have made I am reproducing it here

After that I made the following changes in /grub/menu.1st
title Fedora Core (2.6.9-1.667)
root (hd0,5)
kernel /vmlinuz-2.6.9-1.667 ro root=LABEL=/12 rhgb quiet
initrd /initrd-2.6.9-1.667.img

#Added afterward
#**********************
title Test Kernel (2.6.0)
root (hd0,5)
kernel /bzImage-2.6.17.1 ro root=(hd0,7)
initrd /initrd-2.6.17.1.img
#************************

title MS Dos
rootnoverify (hd0,0)
chainloader +1

The one within "********" is the addition
my original kernel, /boot sector is in /dev/hda6
/root in /dev/hda8

Does the above seems OK!
TIA
tan..

Lenard · 06-30-2006, 06:26 AM

You should delete this, you had no need add it in the first place;

Quote:

#Added afterward
#**********************
title Test Kernel (2.6.0)
root (hd0,5)
kernel /bzImage-2.6.17.1 ro root=(hd0,7)
initrd /initrd-2.6.17.1.img
#************************

I'm not 100% sure of the kernel line above, not enough information to say one way or the other if this is correct or not. It looks OK if your root partition is (hd0,7).

Yesterday the 2.6.17.2 kernel was released and I did almost exactly what I suggested to you earlier, I did not need to create a good working .config file since I already have one. When done with the last step (make install) the /boot/grub/grub.conf file was updated as part of the process, see example below;

Code:

#          kernel /vmlinuz-version ro root=/dev/hda5
#          initrd /initrd-version.img
#boot=/dev/hda
default=1
timeout=5
splashimage=(hd0,2)/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.17.2)
        root (hd0,2)
        kernel /vmlinuz-2.6.17.2 ro root=LABEL=/ quiet video=sisfb:mode:1280x800x16
        initrd /initrd-2.6.17.2.img
title CentOS (2.6.17.1)
        root (hd0,2)
        kernel /vmlinuz-2.6.17.1 ro root=LABEL=/ quiet video=sisfb:mode:1280x800x16

See the very first line in the example above, this tells me where the root partition really is which the same as the partition label (root=LABEL=/) in the kernel line. This is good to know incase your kernel cannot use the partition label to continue the boot process.

tanalam · 07-03-2006, 12:09 AM

hi ,
I followed the method that you told for "2.6.8.1" kernel and it worked.
However the same method failed for "2.6.14.1" with error "kernel panoc -syncing error" might be because of improper .config file.
Any way the way I configured the config file for "2.6.8.1" was also not convincing

I copied old config file and used make oldconfig
But I am not happy with the method as it was very much automated.

Initially I tried to select the options in the xconfig window, by looking at the currently existing .config file.
But the problem is that I am not able correlate the option in the xconfig window and the entries in .config file. Probably each "Y,N or M" option is generating multiple entries in the .config file.
Can u give me some "tips" on how to parse the config file

TIA
tan...

Lenard · 07-03-2006, 05:46 AM

First step (if you have not already) is to review the Kernel Rebuild Guide;

http://www.digitalhermit.com/linux/K...ild-HOWTO.html

All of the options are in the config file as you can see, each section is parsed within the file, for example (choosing a small section);

#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
# CONFIG_CPU_FREQ_DEBUG is not set
CONFIG_CPU_FREQ_STAT=y
# CONFIG_CPU_FREQ_STAT_DETAILS is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=m
CONFIG_CPU_FREQ_GOV_USERSPACE=y
# CONFIG_CPU_FREQ_GOV_ONDEMAND is not set
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m

(y) means builtin into the kernel, (m) means built as a kernel module and (n) [# in the config file] means not built or 'is not set' as shown above.

Each entry in the config file has a correlation to the [menu][g][x]config window, just look at the help or comments. The 'name' used in help or comments can be found in the config file.

Copying an old config file works most of the time but sometimes changes happen with the kernel things added or removed or rearranged for example) and the copy process does not work as expected. This happened to you, changes between 2.6.8 and 2.6.14 kernel releases happened (around the 2.6.12 release). Changes also happened with the 2.6.16 and 2.6.17 kernel releases. The kernels as supplied by Red Hat (Fedora) and others (SuSE for example) do not have a one to one relationship with the vanilla kernel from kernel.org, they can be used as a starting point (maybe 75-90%) but not much more.

The kernel panic error is because something important to the kernel start process is not right or you do not have the correct version of one or more of the tools required to build the kernel (see the kernel rebuild guide). You can also read the requirements to build a working kernel in the Documentation folder within the extracted kernel source folder structure.

tanalam · 07-04-2006, 03:52 AM

Hi,
Thanku for ur advice.
Infact when I am having a closer look at the options it is making more of a sense to me

As I mentioned before that I have compiled kernel 2.6.8.1 and it is working "almost"

When I looked at "dmesg" I observed unusual messages. but I was not able to figure out the reason. I also saw the same things when I was shutting down from 2.6.8.1 .Below is the message that I got

audit(1152000737.057:0): avc: denied { write } for pid=2449 exe=/sbin/minilogd dev=tmpfs ino=923 scontext=user_u:system_r:syslogd_t tcontext=user_u

bject_r:tmpfs_t tclass=dir
audit(1152000737.247:0): avc: denied { write } for pid=2460 exe=/sbin/minilogd dev=tmpfs ino=923 scontext=user_u:system_r:syslogd_t tcontext=user_u

bject_r:tmpfs_t tclass=dir
audit(1152000737.354:0): avc: denied { write } for pid=2472 exe=/sbin/minilogd dev=tmpfs ino=923 scontext=user_u:system_r:syslogd_t tcontext=user_u

bject_r:tmpfs_t tclass=dir
eth0: no IPv6 routers present
audit(1152000737.994:0): avc: denied { write } for pid=2493 exe=/sbin/minilogd dev=tmpfs ino=923 scontext=user_u:system_r:syslogd_t tcontext=user_u

bject_r:tmpfs_t tclass=dir
audit(1152000738.205:0): avc: denied { write } for pid=2505 exe=/sbin/minilogd dev=tmpfs ino=923 scontext=user_u:system_r:syslogd_t tcontext=user_u

bject_r:tmpfs_t tclass=dir
audit(1152000739.081:0): avc: denied { write } for pid=2516 exe=/sbin/minilogd dev=tmpfs ino=923 scontext=user_u:system_r:syslogd_t tcontext=user_u

bject_r:tmpfs_t tclass=dir
audit(1152000739.466:0): avc: denied { write } for pid=2527 exe=/sbin/minilogd dev=tmpfs ino=923 scontext=user_u:system_r:syslogd_t tcontext=user_u

bject_r:tmpfs_t tclass=dir

I was more concerned with "denied" thing can u shed some light on this.

TIA

regards
tan...

tanalam · 07-04-2006, 03:53 AM

Hi,
Thanku for ur advice.
Infact when I am having a closer look at the options it is making more of a sense to me

As I mentioned before that I have compiled kernel 2.6.8.1 and it is working "almost"

When I looked at "dmesg" I observed unusual messages. but I was not able to figure out the reason. I also saw the same things when I was shutting down from 2.6.8.1 .Below is the message that I got

audit(1152000737.057:0): avc: denied { write } for pid=2449 exe=/sbin/minilogd dev=tmpfs ino=923 scontext=user_u:system_r:syslogd_t tcontext=user_u: object_r:tmpfs_t tclass=dir
audit(1152000737.247:0): avc: denied { write } for pid=2460 exe=/sbin/minilogd dev=tmpfs ino=923 scontext=user_u:system_r:syslogd_t tcontext=user_u

bject_r:tmpfs_t tclass=dir
audit(1152000737.354:0): avc: denied { write } for pid=2472 exe=/sbin/minilogd dev=tmpfs ino=923 scontext=user_u:system_r:syslogd_t tcontext=user_u

bject_r:tmpfs_t tclass=dir
eth0: no IPv6 routers present
audit(1152000737.994:0): avc: denied { write } for pid=2493 exe=/sbin/minilogd dev=tmpfs ino=923 scontext=user_u:system_r:syslogd_t tcontext=user_u

bject_r:tmpfs_t tclass=dir
audit(1152000738.205:0): avc: denied { write } for pid=2505 exe=/sbin/minilogd dev=tmpfs ino=923 scontext=user_u:system_r:syslogd_t tcontext=user_u

bject_r:tmpfs_t tclass=dir
audit(1152000739.081:0): avc: denied { write } for pid=2516 exe=/sbin/minilogd dev=tmpfs ino=923 scontext=user_u:system_r:syslogd_t tcontext=user_u

bject_r:tmpfs_t tclass=dir
audit(1152000739.466:0): avc: denied { write } for pid=2527 exe=/sbin/minilogd dev=tmpfs ino=923 scontext=user_u:system_r:syslogd_t tcontext=user_u

bject_r:tmpfs_t tclass=dir

I was more concerned with "denied" thing can u shed some light on this.

TIA

regards
tan...

tanalam · 07-04-2006, 03:53 AM

Hi,
Thanku for ur advice.
Infact when I am having a closer look at the options it is making more of a sense to me

As I mentioned before that I have compiled kernel 2.6.8.1 and it is working "almost"

When I looked at "dmesg" I observed unusual messages. but I was not able to figure out the reason. I also saw the same things when I was shutting down from 2.6.8.1 .Below is the message that I got

audit(1152000737.057:0): avc: denied { write } for pid=2449 exe=/sbin/minilogd dev=tmpfs ino=923 scontext=user_u:system_r:syslogd_t tcontext=user_u: object_r:tmpfs_t tclass=dir
audit(1152000737.247:0): avc: denied { write } for pid=2460 exe=/sbin/minilogd dev=tmpfs ino=923 scontext=user_u:system_r:syslogd_t tcontext=user_u: object_r:tmpfs_t tclass=dir
audit(1152000737.354:0): avc: denied { write } for pid=2472 exe=/sbin/minilogd dev=tmpfs ino=923 scontext=user_u:system_r:syslogd_t tcontext=user_u: object_r:tmpfs_t tclass=dir
eth0: no IPv6 routers present
audit(1152000737.994:0): avc: denied { write } for pid=2493 exe=/sbin/minilogd dev=tmpfs ino=923 scontext=user_u:system_r:syslogd_t tcontext=user_u: object_r:tmpfs_t tclass=dir
audit(1152000738.205:0): avc: denied { write } for pid=2505 exe=/sbin/minilogd dev=tmpfs ino=923 scontext=user_u:system_r:syslogd_t tcontext=user_u: object_r:tmpfs_t tclass=dir
audit(1152000739.081:0): avc: denied { write } for pid=2516 exe=/sbin/minilogd dev=tmpfs ino=923 scontext=user_u:system_r:syslogd_t tcontext=user_u: object_r:tmpfs_t tclass=dir
audit(1152000739.466:0): avc: denied { write } for pid=2527 exe=/sbin/minilogd dev=tmpfs ino=923 scontext=user_u:system_r:syslogd_t tcontext=user_u: object_r:tmpfs_t tclass=dir

I was more concerned with "denied" thing can u shed some light on this.

TIA

regards
tan...

tanalam · 07-04-2006, 04:01 AM

EXTREAMLY SOORRY FOR THE MULTIPLE POST ..
ACTUALLY INSTEAD OF EDITTING THE POST I MADE MULTIPLE POST

Lenard · 07-04-2006, 06:09 AM

Looks like you need to adjust your selinux and auditing polices, as a test turn them off at boot time and see if they go away. This is a one shot to turn off selinux;

When the grub splash screen is displayed press any key.

Select the 2.6.8.1 boot choice and press 'e' key.

Select the kernel line and press the 'e' key.

At the end of the line add a space followed by selinux=0

When done press the 'Enter' key followed by the 'b' key

That's the number zero not the letter 'o' above.

Also see this; http://fedora.redhat.com/docs/selinu...html#id2826243

tanalam · 07-05-2006, 01:57 AM

hi,

I followed your advice and it worked, not just that earlier I was not able connect to net and play test tone. But after I did what you said I was able to do the same. "I donot know how and will be delighted if u could shed some light on how the net and sound play started working"
Anyway the bigger surprise was that soon a message poped up on the opened terminal window which goes like this

"Message from syslogd@localhost at Wed Jul 5 11:58:14 2006 ...
localhost kernel: Disabling IRQ #5"

and after words net as well as sound were not working again

I thought that while booting we are modifying the boot option from the command prompt so modifying "menu.1st" will do the same.
So I added selinux= 0 as below

kernel /vmlinuz-2.6.8.1 ro root=LABEL=/12 rhgb quiet selinux=0

but it was not working.

I read on the document (that u referred) that changing the config file in /etc/selinux as
SELINUX=disabled will disable it.
Is it so?
or do I need to make further changes elsewhere?

TIA

regards
tan...

Lenard · 07-05-2006, 06:13 AM

Quote:

I read on the document (that u referred) that changing the config file in /etc/selinux as
SELINUX=disabled will disable it.
Is it so?
or do I need to make further changes elsewhere?

Yes this is correct and no need to make any further changes as far as selinux is concerned.

Quote:

"Message from syslogd@localhost at Wed Jul 5 11:58:14 2006 ...
localhost kernel: Disabling IRQ #5"

Now this may be a problem, it sound like you may have an interrupt conflict (disabling IRQ#5) between the soundcard and something else (maybe the ethernet interface). Please check and see (and maybe post the results);

cat /proc/interrupts

If yes then then try adding 'pci=routeirq' to the kernel line instead of the selinux=0 portion. You might want to build (inthe kernel configuration) and use acpi instead of apm also.

Almost forgot, if you rebuild your kernel for acpi support also make sure you install the acpid rpm package (if not already installed);

The check;rpm -qa acpid

To install(for example); rpm -ivh http://download.fedora.redhat.com/pu...0.3-2.i386.rpm

tanalam · 07-06-2006, 04:17 AM

I check for acpid and it was there
acpid-1.0.3-2

following is the output of /proc/intrrupts
CPU0
0: 116275 XT-PIC timer
1: 126 XT-PIC i8042
2: 0 XT-PIC cascade
5: 200000 XT-PIC Intel ICH5, uhci_hcd, uhci_hcd, eth0
8: 1 XT-PIC rtc
9: 100000 XT-PIC acpi
10: 0 XT-PIC uhci_hcd, uhci_hcd
11: 0 XT-PIC ehci_hcd
12: 1066 XT-PIC i8042
14: 9987 XT-PIC ide0
15: 614 XT-PIC ide1
NMI: 0
ERR: 0

which is almost the same as what I have in my first kernel which I am giving below

CPU0
0: 2385622 XT-PIC timer
1: 7632 XT-PIC i8042
2: 0 XT-PIC cascade
5: 14042 XT-PIC Intel ICH5, uhci_hcd, uhci_hcd, eth0
8: 1 XT-PIC rtc
9: 100000 XT-PIC acpi
10: 0 XT-PIC uhci_hcd, uhci_hcd, i915@pci:0000:00:02.0
11: 0 XT-PIC ehci_hcd
12: 65544 XT-PIC i8042
14: 19368 XT-PIC ide0
15: 20858 XT-PIC ide1
NMI: 0
ERR: 0

also
I am giving below output of ifconfig "I donot know if required"

eth0 Link encap:Ethernet HWaddr 00:0F:FE:34:E9:9E
inet addr:107.108.92.196 Bcast:107.108.92.255 Mask:255.255.255.0
inet6 addr: fe80::20f:feff:fe34:e99e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:170 errors:0 dropped:0 overruns:0 frame:0
TX packets:39 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:16059 (15.6 KiB) TX bytes:3538 (3.4 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1427 errors:0 dropped:0 overruns:0 frame:0
TX packets:1427 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1466270 (1.3 MiB) TX bytes:1466270 (1.3 MiB)

Lenard · 07-06-2006, 05:32 AM

I have a slighty new version of the acpid package, but that's not a big deal. I do have acpi built for my kernel and do not have apm built or the apm package installed. A snippet from my laptop's 2.6.17.X .config file;

Code:

#
# Power management options
#
CONFIG_PM=y
CONFIG_PM_LEGACY=y
# CONFIG_PM_DEBUG is not set
CONFIG_SOFTWARE_SUSPEND=y
CONFIG_PM_STD_PARTITION=""

#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
# CONFIG_ACPI_SLEEP_PROC_SLEEP is not set
CONFIG_ACPI_AC=m
CONFIG_ACPI_BATTERY=m
CONFIG_ACPI_BUTTON=m
# CONFIG_ACPI_VIDEO is not set
# CONFIG_ACPI_HOTKEY is not set
CONFIG_ACPI_FAN=m
CONFIG_ACPI_PROCESSOR=m
CONFIG_ACPI_THERMAL=m
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_IBM is not set
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y
# CONFIG_ACPI_CONTAINER is not set
# CONFIG_ACPI_HOTPLUG_MEMORY is not set

The IRQ's used for comparsion first my laptop;

Code:

$ cat /proc/interrupts
           CPU0
  0:   37962083    IO-APIC-edge  timer
  1:       4500    IO-APIC-edge  i8042
  8:          0    IO-APIC-edge  rtc
 11:      38696   IO-APIC-level  acpi
 12:     739360    IO-APIC-edge  i8042
 14:      69228    IO-APIC-edge  ide0
 15:     336057    IO-APIC-edge  ide1
 16:          1   IO-APIC-level  yenta
 18:          0   IO-APIC-level  ohci_hcd:usb1
 19:          0   IO-APIC-level  ohci_hcd:usb2
 20:          0   IO-APIC-level  ehci_hcd:usb3
 21:       3226   IO-APIC-level  SiS SI7013 Modem, SiS SI7012
 22:     117881   IO-APIC-level  ndiswrapper

Now my desktop which has a very similar kernel config for power management;

Code:

           CPU0       
  0:   65734624    IO-APIC-edge  timer
  1:         10    IO-APIC-edge  i8042
  7:          0    IO-APIC-edge  parport0
  8:          1    IO-APIC-edge  rtc
  9:          0   IO-APIC-level  acpi
 12:        257    IO-APIC-edge  i8042
 14:      64938    IO-APIC-edge  ide0
 15:     197146    IO-APIC-edge  ide1
 16:    4931207   IO-APIC-level  mga@pci:0000:02:00.0
 17:      25459   IO-APIC-level  eth0
 18:          0   IO-APIC-level  NVidia nForce2, ohci_hcd:usb3
 19:          0   IO-APIC-level  ehci_hcd:usb1
 20:          0   IO-APIC-level  ohci_hcd:usb2

The big thing to notice is both my ethernet interfaces on both systems (ndiswrapper and eth0) each have a seperate IRQ which is not shared be any other device.

Thanks for the ifcfg output, if your not using ip6 then I suggest you turn it off, example line entries follow;

for /etc/modprobe.conf; alias net-pf-10 off
for /etc/sysconfig/network-scripts/ifcfg-XXXX; IPV6INIT=no

Note: ifcfg-XXXX can be any ethernet interface (eth0, eth1 or wlan0)

The results;

Code:

$ ifconfig wlan0
wlan0     Link encap:Ethernet  HWaddr 00:14:A4:36:13:09
          inet addr:192.168.1.8  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:24062 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16516 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:28170538 (26.8 MiB)  TX bytes:2236818 (2.1 MiB)
          Interrupt:22 Memory:e2000000-e2002000