Issue with X crashing in Redhat EL 5.3 after changing the IP address to a different subnet

[Doug Kuvaas]

I have a server running RHEL 5.3 ( Kernel 2.6.18-128.el5 ) that I am
having some trouble with.  I set the system up in-house for testing on
our internal network, and everything worked fine.  However, after
changing the network configuration (IP address is on a different
subnet) to match where this system will be installed, Xorg does not
start.  If I change the IP address within the same subnet, the system
starts normally. Originally it was 192.168.1.2, if I change it to
192.168.1.20, it works.  Also, if I disable the network card at boot,
the system starts up normally.  However, if I change the IP address to
192.6.1.2 (site setting) it does not work.  If I start the network
with the 192.6.1.2 IP after the system boots, everything seems to work
fine.

I don't get any errors in /var/log/Xorg.0.log when I grep (EE), though
this is the output of grepping (WW):

(WW) I810(0): Bad V_BIOS checksum
(WW) I810(0): Detected stolen memory (7104 kB) doesn't match what the
BIOS reports (8128 kB)
(WW) I810(0): Bad V_BIOS checksum
(WW) I810(0): Extended BIOS function 0x5f64 not supported.
(WW) I810(0): Extended BIOS function 0x5f64 not supported.
(WW) I810(0): Extended BIOS function 0x5f64 not supported.
(WW) I810(0): Extended BIOS function 0x5f64 not supported.
(WW) I810(0): Extended BIOS function 0x5f64 not supported.
(WW) I810(0): Extended BIOS function 0x5f64 not supported.
(WW) I810(0): Extended BIOS function 0x5f64 not supported.
(WW) I810(0): Extended BIOS function 0x5f64 not supported.
(WW) I810(0): Unable to estimate virtual size
(WW) I810(0): Bad V_BIOS checksum
(WW) I810(0): Extended BIOS function 0x5f05 not supported.
(WW) I810(0): Extended BIOS function 0x5f05 not supported.
(WW) AIGLX: 3D driver claims to not support visual 0x23
(WW) AIGLX: 3D driver claims to not support visual 0x24
(WW) AIGLX: 3D driver claims to not support visual 0x25
(WW) AIGLX: 3D driver claims to not support visual 0x26
(WW) AIGLX: 3D driver claims to not support visual 0x27
(WW) AIGLX: 3D driver claims to not support visual 0x28
(WW) AIGLX: 3D driver claims to not support visual 0x29
(WW) AIGLX: 3D driver claims to not support visual 0x2a
(WW) AIGLX: 3D driver claims to not support visual 0x2b
(WW) AIGLX: 3D driver claims to not support visual 0x2c
(WW) AIGLX: 3D driver claims to not support visual 0x2d
(WW) AIGLX: 3D driver claims to not support visual 0x2e
(WW) AIGLX: 3D driver claims to not support visual 0x2f
(WW) AIGLX: 3D driver claims to not support visual 0x30
(WW) AIGLX: 3D driver claims to not support visual 0x31
(WW) AIGLX: 3D driver claims to not support visual 0x32
(WW) I810(0): Successfully set original devices
(WW) I810(0): Setting the original video mode instead of restoring
(WW) I810(0): Extended BIOS function 0x5f05 not supported.
(WW) I810(0): Successfully set original devices (2)

One thing to note is this line at the very bottom of the Xorg.0.log file:

FreeFontPath: FPE "unix/:7100" refcount is 2, should be 1; fixing.

I don't notice this when I look at the log file generated when the
system successfully loads Xorg.



This is the /etc/sysconfig/network-scripts/ifcfg-eth0 configuration file:

# Intel Corporation 82566DM-2 Gigabit Network Connection
DEVICE=eth0
BOOTPROTO=none
ONBOOT=no
TYPE=Ethernet
USERCTL=yes
IPV6INIT=no
PEERDNS=yes
HWADDR=00:25:90:62:2d:52
NETMASK=255.255.255.0
IPADDR=192.6.1.2
GATEWAY=192.6.1.1



The /etc/X11/xorg.conf file:

# Xorg configuration created by pyxf86config

Section "ServerLayout"
        Identifier     "Default Layout"
        Screen      0  "Screen0" 0 0
        InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "InputDevice"
        Identifier  "Keyboard0"
        Driver      "kbd"
        Option      "XkbModel" "pc105"
        Option      "XkbLayout" "us"
EndSection

Section "Device"
        Identifier  "Videocard0"
        Driver      "intel"
EndSection

Section "Screen"
        Identifier "Screen0"
        Device     "Videocard0"
        DefaultDepth     24
        SubSection "Display"
                Viewport   0 0
                Depth     24
        EndSubSection
EndSection


Has anyone ever seen this before?  Any ideas on how to fix?

Let me know if more information is needed.

Doug