FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora User

 
 
LinkBack Thread Tools
 
Old 03-01-2010, 07:24 PM
Andrew Junev
 
Default Fedora 12 does not work after replacing the motherboard

Hello All,

I kindly ask for your support. On my MythTV frontend-only machine, I
had to replace the motherboard. The old motherboard was an ASUS P5KR
(Intel P35 chipset), and the newly installed motherboard is an MSI
P43T-C51 (Intel P43 chipset). The old MB wasn't faulty - I just had
to urgently use it in another machine.
Everything else in this system remained basically the same - CPU,
Video, etc. My video adapter is NVidia 8600GT made by ASUS (don't
remember the model exactly). I am using proprietary NVidia driver from
rpmfusion.

With the new MSI MB, the system just hangs when booting into graphical
mode (runlevel 5), and there seem to be no errors in /var/log/messages,
dmesg or in Xorg.log.
If booted in runlevel 3 (text mode), the system seem to work, but
there are several kernel oopses coming right after boot:

2010-03-01T22:19:06.175302+03:00 frontend1 abrt: Kerneloops: Reported 1 kernel oopses to Abrt
2010-03-01T22:19:06.175409+03:00 frontend1 abrtd: Directory 'kerneloops-1267471146-1' creation detected
2010-03-01T22:19:10.113246+03:00 frontend1 abrtd: Getting local universal unique identification
2010-03-01T22:19:10.119410+03:00 frontend1 abrtd: New crash /var/cache/abrt/kerneloops-1267471146-1, processing
2010-03-01T22:19:10.138685+03:00 frontend1 abrtd: Registered Action plugin 'RunApp'
2010-03-01T22:19:10.138735+03:00 frontend1 abrtd: RunApp('/var/cache/abrt/kerneloops-1267471146-1','test x"`cat component`" = x"xorg-x11-server-Xorg" && cp /var/log/Xorg.0.log .')
2010-03-01T22:21:06.111275+03:00 frontend1 abrt: Kerneloops: Reported 1 kernel oopses to Abrt
2010-03-01T22:21:06.111358+03:00 frontend1 abrtd: Directory 'kerneloops-1267471266-1' creation detected
2010-03-01T22:21:06.175171+03:00 frontend1 abrtd: Getting local universal unique identification
2010-03-01T22:21:06.179860+03:00 frontend1 abrtd: New crash /var/cache/abrt/kerneloops-1267471266-1, processing
2010-03-01T22:21:06.179881+03:00 frontend1 abrtd: RunApp('/var/cache/abrt/kerneloops-1267471266-1','test x"`cat component`" = x"xorg-x11-server-Xorg" && cp /var/log/Xorg.0.log .')
2010-03-01T22:23:06.112950+03:00 frontend1 abrt: Kerneloops: Reported 1 kernel oopses to Abrt
2010-03-01T22:23:06.113047+03:00 frontend1 abrtd: Directory 'kerneloops-1267471386-1' creation detected
2010-03-01T22:23:06.176437+03:00 frontend1 abrtd: Getting local universal unique identification
2010-03-01T22:23:06.181005+03:00 frontend1 abrtd: New crash /var/cache/abrt/kerneloops-1267471386-1, processing
2010-03-01T22:23:06.181066+03:00 frontend1 abrtd: RunApp('/var/cache/abrt/kerneloops-1267471386-1','test x"`cat component`" = x"xorg-x11-server-Xorg" && cp /var/log/Xorg.0.log .')



If I do an 'init 5' while I'm in runlevel 3, I can see Xorg starting
and occupying all of the CPU resources (so that my PC doesn't respond
to keyboard at all, and remote SSH sessions are also interrupted).
Again, I don't see any obvious error messages in the logs when the
system stops responding...

I made a 'yum update', getting all the packages up to date. It didn't
change the behavior at all...

I thought I could reinstall the system completely, but Fedora 12
install DVD also stops responding shortly after the "Check
installation media" step - before actually starting the installation.

At the same time, Fedora 12 Live CD boots up fine (in Gnome) but stops
responding after a few minutes.


I thought this could be a hardware issue. I checked the RAM with
memtest (well, 2 passes went without errors, then I interrupted it).
Then I installed Windows XP - to test if it will fail. XP worked good,
I installed all the drivers and noticed no stability problems at all.

So this looks more like a software incompatibility to me, rather than
a hardware issue (still, I'm not 100% sure)...

Unfortunately my knowledge of Linux isn't any good to be able to
track the problem. Could you please help me to investigate it further?
I can run any tests / provide logs, dumps, etc. Just need to know
where to go and how to look for a solution...


Thanks!



Here are some details for now:

# uname -a
Linux frontend1 2.6.31.12-174.2.22.fc12.i686 #1 SMP Fri Feb 19 19:26:06 UTC 2010 i686 i686 i386 GNU/Linux


End of dmesg when the system stopped responding (while booting
directly to runlevel 5):

ALSA sound/pci/hda/patch_realtek.c:1197: realtek: Enabling init ASM_ID=0xf603 CODEC_ID=10ec0885
input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input5
EXT3 FS on dm-0, internal journal
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Adding 2031608k swap on /dev/mapper/VolGroup00-LogVol01. Priority:-1 extents:1 across:2031608k


respective end of /var/log/messages for ~the same period of time:

2010-03-01T22:12:25.546565+03:00 frontend1 avahi-daemon[1443]: Registering HINFO record with values 'I686'/'LINUX'.
2010-03-01T22:12:26.448523+03:00 frontend1 avahi-daemon[1443]: Server startup complete. Host name is frontend1.local. Local service cookie is 565159940.
2010-03-01T22:12:26.977899+03:00 frontend1 smartd[1578]: smartd 5.39.1 2010-01-28 r3054 [i386-redhat-linux-gnu] (local build)#012Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net#012
2010-03-01T22:12:26.977988+03:00 frontend1 smartd[1578]: Opened configuration file /etc/smartd.conf
2010-03-01T22:12:26.989087+03:00 frontend1 smartd[1578]: Configuration file /etc/smartd.conf parsed.
2010-03-01T22:12:26.989152+03:00 frontend1 smartd[1578]: Device: /dev/sda, opened
2010-03-01T22:12:26.998766+03:00 frontend1 smartd[1578]: Device: /dev/sda, found in smartd database.
2010-03-01T22:12:27.279045+03:00 frontend1 smartd[1578]: Device: /dev/sda, is SMART capable. Adding to "monitor" list.
2010-03-01T22:12:27.279187+03:00 frontend1 smartd[1578]: Monitoring 1 ATA and 0 SCSI devices
2010-03-01T22:12:27.350154+03:00 frontend1 avahi-daemon[1443]: Service "frontend1" (/services/ssh.service) successfully established.
2010-03-01T22:12:27.455723+03:00 frontend1 smartd[1602]: smartd has fork()ed into background mode. New PID=1602.


... and the Xorg.log file:

# cat Xorg.0.log

X.Org X Server 1.7.5
Release Date: 2010-02-16
X Protocol Version 11, Revision 0
Build Operating System: x86-04 2.6.18-164.6.1.el5
Current Operating System: Linux frontend1 2.6.31.12-174.2.22.fc12.i686 #1 SMP Fri Feb 19 19:26:06 UTC 2010 i686
Kernel command line: ro root=/dev/VolGroup00/LogVol00 rhgb quiet SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us selinux=0
Build Date: 16 February 2010 04:33:31AM
Build ID: xorg-x11-server 1.7.5-1.fc12
Current version of pixman: 0.16.6
Before reporting problems, check http://bodhi.fedoraproject.org/
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Mar 1 22:12:28 2010
(==) Using config file: "/etc/X11/xorg.conf"
(==) No Layout section. Using the first Screen section.
(==) No screen section available. Using defaults.
(**) |-->Screen "Default Screen Section" (0)
(**) | |-->Monitor "<default monitor>"
(==) No device specified for screen "Default Screen Section".
Using the first device section listed.
(**) | |-->Device "Videocard0"
(==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
(**) Option "AIGLX" "on"
(==) Automatically adding devices
(==) Automatically enabling devices
(==) FontPath set to:
catalogue:/etc/X11/fontpath.d,
built-ins
(**) ModulePath set to "/usr/lib/xorg/modules/extensions/nvidia,/usr/lib/xorg/modules"
(**) Extension "Composite" is enabled
(II) Cannot locate a core pointer device.
(II) Cannot locate a core keyboard device.
(II) The server relies on HAL to provide the list of input devices.
If no devices become available, reconfigure HAL or disable AutoAddDevices.
(II) Loader magic: 0x821c900
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 6.0
X.Org XInput driver : 7.0
X.Org Server Extension : 2.0
(++) using VT number 1

(--) PCI:*(0:1:0:0) 10de:0402:1043:8243 nVidia Corporation GeForce 8600 GT rev 161, Mem @ 0xfd000000/16777216, 0xd0000000/268435456, 0xfa000000/33554432, I/O @ 0x0000cc00/128, BIOS @ 0x????????/131072
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.7.5, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension SELinux
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.7.5, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions/nvidia/libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Server Extension
(II) NVIDIA GLX Module 190.53 Tue Dec 8 20:47:42 PST 2009
(II) Loading extension GLX
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions/librecord.so
(II) Module record: vendor="X.Org Foundation"
compiled for 1.7.5, module version = 1.13.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension RECORD
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions/libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.7.5, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "dri2"
(II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
compiled for 1.7.5, module version = 1.1.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "nvidia"
(II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
(II) Module nvidia: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Video Driver
(II) NVIDIA dlloader X Driver 190.53 Tue Dec 8 19:16:02 PST 2009
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
(II) Primary Device is: PCI 01@00:00:0
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules/libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.7.5, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "wfb"
(II) LoadModule: "wfb"
(II) Loading /usr/lib/xorg/modules/libwfb.so
(II) Module wfb: vendor="X.Org Foundation"
compiled for 1.7.5, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(II) NVIDIA(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
(==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Option "AddARGBGLXVisuals" "True"
(**) Mar 01 22:12:29 NVIDIA(0): Enabling RENDER acceleration
(II) Mar 01 22:12:29 NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
(II) Mar 01 22:12:29 NVIDIA(0): enabled.
(II) Mar 01 22:12:36 NVIDIA(0): NVIDIA GPU GeForce 8600 GT (G84) at PCI:1:0:0 (GPU-0)
(--) Mar 01 22:12:36 NVIDIA(0): Memory: 524288 kBytes
(--) Mar 01 22:12:36 NVIDIA(0): VideoBIOS: 60.84.41.00.00
(II) Mar 01 22:12:36 NVIDIA(0): Detected PCI Express Link width: 16X
(--) Mar 01 22:12:36 NVIDIA(0): Interlaced video modes are supported on this GPU
(--) Mar 01 22:12:36 NVIDIA(0): Connected display device(s) on GeForce 8600 GT at PCI:1:0:0:
(--) Mar 01 22:12:36 NVIDIA(0): FUS P19-1S (DFP-1)
(--) Mar 01 22:12:36 NVIDIA(0): FUS P19-1S (DFP-1): 330.0 MHz maximum pixel clock
(--) Mar 01 22:12:36 NVIDIA(0): FUS P19-1S (DFP-1): Internal Dual Link TMDS




What else should I check???

--
Best regards,
Andrew

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 03-01-2010, 08:04 PM
"Kevin J. Cummings"
 
Default Fedora 12 does not work after replacing the motherboard

On 03/01/2010 03:24 PM, Andrew Junev wrote:
> Hello All,
>
> I kindly ask for your support. On my MythTV frontend-only machine, I
> had to replace the motherboard. The old motherboard was an ASUS P5KR
> (Intel P35 chipset), and the newly installed motherboard is an MSI
> P43T-C51 (Intel P43 chipset). The old MB wasn't faulty - I just had
> to urgently use it in another machine.
> Everything else in this system remained basically the same - CPU,
> Video, etc. My video adapter is NVidia 8600GT made by ASUS (don't
> remember the model exactly). I am using proprietary NVidia driver from
> rpmfusion.
>
> With the new MSI MB, the system just hangs when booting into graphical
> mode (runlevel 5), and there seem to be no errors in /var/log/messages,
> dmesg or in Xorg.log.
> If booted in runlevel 3 (text mode), the system seem to work, but
> there are several kernel oopses coming right after boot:
>
> 2010-03-01T22:19:06.175302+03:00 frontend1 abrt: Kerneloops: Reported 1 kernel oopses to Abrt
> 2010-03-01T22:19:06.175409+03:00 frontend1 abrtd: Directory 'kerneloops-1267471146-1' creation detected
> 2010-03-01T22:19:10.113246+03:00 frontend1 abrtd: Getting local universal unique identification
> 2010-03-01T22:19:10.119410+03:00 frontend1 abrtd: New crash /var/cache/abrt/kerneloops-1267471146-1, processing
> 2010-03-01T22:19:10.138685+03:00 frontend1 abrtd: Registered Action plugin 'RunApp'
> 2010-03-01T22:19:10.138735+03:00 frontend1 abrtd: RunApp('/var/cache/abrt/kerneloops-1267471146-1','test x"`cat component`" = x"xorg-x11-server-Xorg" && cp /var/log/Xorg.0.log .')
> 2010-03-01T22:21:06.111275+03:00 frontend1 abrt: Kerneloops: Reported 1 kernel oopses to Abrt
> 2010-03-01T22:21:06.111358+03:00 frontend1 abrtd: Directory 'kerneloops-1267471266-1' creation detected
> 2010-03-01T22:21:06.175171+03:00 frontend1 abrtd: Getting local universal unique identification
> 2010-03-01T22:21:06.179860+03:00 frontend1 abrtd: New crash /var/cache/abrt/kerneloops-1267471266-1, processing
> 2010-03-01T22:21:06.179881+03:00 frontend1 abrtd: RunApp('/var/cache/abrt/kerneloops-1267471266-1','test x"`cat component`" = x"xorg-x11-server-Xorg" && cp /var/log/Xorg.0.log .')
> 2010-03-01T22:23:06.112950+03:00 frontend1 abrt: Kerneloops: Reported 1 kernel oopses to Abrt
> 2010-03-01T22:23:06.113047+03:00 frontend1 abrtd: Directory 'kerneloops-1267471386-1' creation detected
> 2010-03-01T22:23:06.176437+03:00 frontend1 abrtd: Getting local universal unique identification
> 2010-03-01T22:23:06.181005+03:00 frontend1 abrtd: New crash /var/cache/abrt/kerneloops-1267471386-1, processing
> 2010-03-01T22:23:06.181066+03:00 frontend1 abrtd: RunApp('/var/cache/abrt/kerneloops-1267471386-1','test x"`cat component`" = x"xorg-x11-server-Xorg" && cp /var/log/Xorg.0.log .')
>
>
>
> If I do an 'init 5' while I'm in runlevel 3, I can see Xorg starting
> and occupying all of the CPU resources (so that my PC doesn't respond
> to keyboard at all, and remote SSH sessions are also interrupted).
> Again, I don't see any obvious error messages in the logs when the
> system stops responding...

Have you rebuilt your initrd images? They possibly contain some drivers
that your old MB needed and your new MB needs different? The easist way
is to probably do a "yum reinstall kernel" when you are certain that the
loaded modules you are using are correct for your system.

Do this from "init 3" mode. Then debug what's wrong with your graphical
setup and the new MB before trying to make "init 5" your default boot
mode again.

I've made more drastic motherboard changes in the past, without seeing
this (i586->i686). But sometimes, all it takes is a chipset change to
really screw things up. B^)

> I made a 'yum update', getting all the packages up to date. It didn't
> change the behavior at all...
>
> I thought I could reinstall the system completely, but Fedora 12
> install DVD also stops responding shortly after the "Check
> installation media" step - before actually starting the installation.
>
> At the same time, Fedora 12 Live CD boots up fine (in Gnome) but stops
> responding after a few minutes.

Any idea why?

> I thought this could be a hardware issue. I checked the RAM with
> memtest (well, 2 passes went without errors, then I interrupted it).
> Then I installed Windows XP - to test if it will fail. XP worked good,
> I installed all the drivers and noticed no stability problems at all.

Running memtest overnight or for 24 hours would be a better test. Once
before I didn;t see an error until the 5th iteration before it triggered
an error.... Whether it was thermal, or bit pattern related, I never
did figure out, I just replaced the bad RAM.

> So this looks more like a software incompatibility to me, rather than
> a hardware issue (still, I'm not 100% sure)...
>
> Unfortunately my knowledge of Linux isn't any good to be able to
> track the problem. Could you please help me to investigate it further?
> I can run any tests / provide logs, dumps, etc. Just need to know
> where to go and how to look for a solution...
>
>
> Thanks!
>
>
>
> Here are some details for now:
>
> # uname -a
> Linux frontend1 2.6.31.12-174.2.22.fc12.i686 #1 SMP Fri Feb 19 19:26:06 UTC 2010 i686 i686 i386 GNU/Linux
>
>
> End of dmesg when the system stopped responding (while booting
> directly to runlevel 5):
>
> ALSA sound/pci/hda/patch_realtek.c:1197: realtek: Enabling init ASM_ID=0xf603 CODEC_ID=10ec0885
> input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input5
> EXT3 FS on dm-0, internal journal
> kjournald starting. Commit interval 5 seconds
> EXT3 FS on sda1, internal journal
> EXT3-fs: mounted filesystem with ordered data mode.
> Adding 2031608k swap on /dev/mapper/VolGroup00-LogVol01. Priority:-1 extents:1 across:2031608k
>
>
> respective end of /var/log/messages for ~the same period of time:
>
> 2010-03-01T22:12:25.546565+03:00 frontend1 avahi-daemon[1443]: Registering HINFO record with values 'I686'/'LINUX'.
> 2010-03-01T22:12:26.448523+03:00 frontend1 avahi-daemon[1443]: Server startup complete. Host name is frontend1.local. Local service cookie is 565159940.
> 2010-03-01T22:12:26.977899+03:00 frontend1 smartd[1578]: smartd 5.39.1 2010-01-28 r3054 [i386-redhat-linux-gnu] (local build)#012Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net#012
> 2010-03-01T22:12:26.977988+03:00 frontend1 smartd[1578]: Opened configuration file /etc/smartd.conf
> 2010-03-01T22:12:26.989087+03:00 frontend1 smartd[1578]: Configuration file /etc/smartd.conf parsed.
> 2010-03-01T22:12:26.989152+03:00 frontend1 smartd[1578]: Device: /dev/sda, opened
> 2010-03-01T22:12:26.998766+03:00 frontend1 smartd[1578]: Device: /dev/sda, found in smartd database.
> 2010-03-01T22:12:27.279045+03:00 frontend1 smartd[1578]: Device: /dev/sda, is SMART capable. Adding to "monitor" list.
> 2010-03-01T22:12:27.279187+03:00 frontend1 smartd[1578]: Monitoring 1 ATA and 0 SCSI devices
> 2010-03-01T22:12:27.350154+03:00 frontend1 avahi-daemon[1443]: Service "frontend1" (/services/ssh.service) successfully established.
> 2010-03-01T22:12:27.455723+03:00 frontend1 smartd[1602]: smartd has fork()ed into background mode. New PID=1602.
>
>
> ... and the Xorg.log file:
>
> # cat Xorg.0.log
>
> X.Org X Server 1.7.5
> Release Date: 2010-02-16
> X Protocol Version 11, Revision 0
> Build Operating System: x86-04 2.6.18-164.6.1.el5
> Current Operating System: Linux frontend1 2.6.31.12-174.2.22.fc12.i686 #1 SMP Fri Feb 19 19:26:06 UTC 2010 i686
> Kernel command line: ro root=/dev/VolGroup00/LogVol00 rhgb quiet SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us selinux=0
> Build Date: 16 February 2010 04:33:31AM
> Build ID: xorg-x11-server 1.7.5-1.fc12
> Current version of pixman: 0.16.6
> Before reporting problems, check http://bodhi.fedoraproject.org/
> to make sure that you have the latest version.
> Markers: (--) probed, (**) from config file, (==) default setting,
> (++) from command line, (!!) notice, (II) informational,
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> (==) Log file: "/var/log/Xorg.0.log", Time: Mon Mar 1 22:12:28 2010
> (==) Using config file: "/etc/X11/xorg.conf"
> (==) No Layout section. Using the first Screen section.
> (==) No screen section available. Using defaults.
> (**) |-->Screen "Default Screen Section" (0)
> (**) | |-->Monitor "<default monitor>"
> (==) No device specified for screen "Default Screen Section".
> Using the first device section listed.
> (**) | |-->Device "Videocard0"
> (==) No monitor specified for screen "Default Screen Section".
> Using a default monitor configuration.
> (**) Option "AIGLX" "on"
> (==) Automatically adding devices
> (==) Automatically enabling devices
> (==) FontPath set to:
> catalogue:/etc/X11/fontpath.d,
> built-ins
> (**) ModulePath set to "/usr/lib/xorg/modules/extensions/nvidia,/usr/lib/xorg/modules"
> (**) Extension "Composite" is enabled
> (II) Cannot locate a core pointer device.
> (II) Cannot locate a core keyboard device.
> (II) The server relies on HAL to provide the list of input devices.
> If no devices become available, reconfigure HAL or disable AutoAddDevices.
> (II) Loader magic: 0x821c900
> (II) Module ABI versions:
> X.Org ANSI C Emulation: 0.4
> X.Org Video Driver: 6.0
> X.Org XInput driver : 7.0
> X.Org Server Extension : 2.0
> (++) using VT number 1
>
> (--) PCI:*(0:1:0:0) 10de:0402:1043:8243 nVidia Corporation GeForce 8600 GT rev 161, Mem @ 0xfd000000/16777216, 0xd0000000/268435456, 0xfa000000/33554432, I/O @ 0x0000cc00/128, BIOS @ 0x????????/131072
> (II) LoadModule: "extmod"
> (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
> (II) Module extmod: vendor="X.Org Foundation"
> compiled for 1.7.5, module version = 1.0.0
> Module class: X.Org Server Extension
> ABI class: X.Org Server Extension, version 2.0
> (II) Loading extension SELinux
> (II) Loading extension MIT-SCREEN-SAVER
> (II) Loading extension XFree86-VidModeExtension
> (II) Loading extension XFree86-DGA
> (II) Loading extension DPMS
> (II) Loading extension XVideo
> (II) Loading extension XVideo-MotionCompensation
> (II) Loading extension X-Resource
> (II) LoadModule: "dbe"
> (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
> (II) Module dbe: vendor="X.Org Foundation"
> compiled for 1.7.5, module version = 1.0.0
> Module class: X.Org Server Extension
> ABI class: X.Org Server Extension, version 2.0
> (II) Loading extension DOUBLE-BUFFER
> (II) LoadModule: "glx"
> (II) Loading /usr/lib/xorg/modules/extensions/nvidia/libglx.so
> (II) Module glx: vendor="NVIDIA Corporation"
> compiled for 4.0.2, module version = 1.0.0
> Module class: X.Org Server Extension
> (II) NVIDIA GLX Module 190.53 Tue Dec 8 20:47:42 PST 2009
> (II) Loading extension GLX
> (II) LoadModule: "record"
> (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
> (II) Module record: vendor="X.Org Foundation"
> compiled for 1.7.5, module version = 1.13.0
> Module class: X.Org Server Extension
> ABI class: X.Org Server Extension, version 2.0
> (II) Loading extension RECORD
> (II) LoadModule: "dri"
> (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
> (II) Module dri: vendor="X.Org Foundation"
> compiled for 1.7.5, module version = 1.0.0
> ABI class: X.Org Server Extension, version 2.0
> (II) Loading extension XFree86-DRI
> (II) LoadModule: "dri2"
> (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
> (II) Module dri2: vendor="X.Org Foundation"
> compiled for 1.7.5, module version = 1.1.0
> ABI class: X.Org Server Extension, version 2.0
> (II) Loading extension DRI2
> (II) LoadModule: "nvidia"
> (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
> (II) Module nvidia: vendor="NVIDIA Corporation"
> compiled for 4.0.2, module version = 1.0.0
> Module class: X.Org Video Driver
> (II) NVIDIA dlloader X Driver 190.53 Tue Dec 8 19:16:02 PST 2009
> (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
> (II) Primary Device is: PCI 01@00:00:0
> (II) Loading sub module "fb"
> (II) LoadModule: "fb"
> (II) Loading /usr/lib/xorg/modules/libfb.so
> (II) Module fb: vendor="X.Org Foundation"
> compiled for 1.7.5, module version = 1.0.0
> ABI class: X.Org ANSI C Emulation, version 0.4
> (II) Loading sub module "wfb"
> (II) LoadModule: "wfb"
> (II) Loading /usr/lib/xorg/modules/libwfb.so
> (II) Module wfb: vendor="X.Org Foundation"
> compiled for 1.7.5, module version = 1.0.0
> ABI class: X.Org ANSI C Emulation, version 0.4
> (II) Loading sub module "ramdac"
> (II) LoadModule: "ramdac"
> (II) Module "ramdac" already built-in
> (II) NVIDIA(0): Creating default Display subsection in Screen section
> "Default Screen Section" for depth/fbbpp 24/32
> (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
> (==) NVIDIA(0): RGB weight 888
> (==) NVIDIA(0): Default visual is TrueColor
> (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
> (**) NVIDIA(0): Option "AddARGBGLXVisuals" "True"
> (**) Mar 01 22:12:29 NVIDIA(0): Enabling RENDER acceleration
> (II) Mar 01 22:12:29 NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
> (II) Mar 01 22:12:29 NVIDIA(0): enabled.
> (II) Mar 01 22:12:36 NVIDIA(0): NVIDIA GPU GeForce 8600 GT (G84) at PCI:1:0:0 (GPU-0)
> (--) Mar 01 22:12:36 NVIDIA(0): Memory: 524288 kBytes
> (--) Mar 01 22:12:36 NVIDIA(0): VideoBIOS: 60.84.41.00.00
> (II) Mar 01 22:12:36 NVIDIA(0): Detected PCI Express Link width: 16X
> (--) Mar 01 22:12:36 NVIDIA(0): Interlaced video modes are supported on this GPU
> (--) Mar 01 22:12:36 NVIDIA(0): Connected display device(s) on GeForce 8600 GT at PCI:1:0:0:
> (--) Mar 01 22:12:36 NVIDIA(0): FUS P19-1S (DFP-1)
> (--) Mar 01 22:12:36 NVIDIA(0): FUS P19-1S (DFP-1): 330.0 MHz maximum pixel clock
> (--) Mar 01 22:12:36 NVIDIA(0): FUS P19-1S (DFP-1): Internal Dual Link TMDS
>
>
>
>
> What else should I check???

I like to debug my X configuration using the "startx" command. That way
I can (usually) abort the server with Ctrl-Alt-Bckspc when necessary. X
can be a pain when it hangs the machine making it impossible to switch
to another VC. If you can't login remotely, odds are the whole kernel
has hung (which is bad for you with the nvidia driver in use as it
taints the kernel, and noone here will help you debug it unless you can
reproduce it using either the nv or nouveau drivers).

It might be good to see of using nouveau or nv helps you get *some*
graphics up, even if it doesn't help your MythTV system.

Solve one problem at a time....

Have you tried underclocking your system (if you can)? That might show
some thermal problems....

--
Kevin J. Cummings
kjchome@rcn.com
cummings@kjchome.homeip.net
cummings@kjc386.framingham.ma.us
Registered Linux User #1232 (http://counter.li.org)
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 03-02-2010, 03:17 AM
Andrew Junev
 
Default Fedora 12 does not work after replacing the motherboard

Hello All,

I kindly ask for your support. On my MythTV frontend-only machine, I
had to replace the motherboard. The old motherboard was an ASUS P5KR
(Intel P35 chipset), and the newly installed motherboard is an MSI
P43T-C51 (Intel P43 chipset). The old MB wasn't faulty - I just had
to urgently use it in another machine.
Everything else in this system remained basically the same - CPU,
RAM, Video, etc. My video adapter is NVidia 8600GT made by ASUS (don't
remember the model exactly). I am using proprietary NVidia driver from
rpmfusion.

With the new MSI MB, the system just stops responding when trying to
boot into graphical mode (runlevel 5), and there seem to be no errors
in /var/log/messages, dmesg or in Xorg.log.
If booted in runlevel 3 (text mode), the system seem to work, but
there are several kernel oopses coming right after boot:

2010-03-01T22:19:06.175302+03:00 frontend1 abrt: Kerneloops: Reported 1 kernel oopses to Abrt
2010-03-01T22:19:06.175409+03:00 frontend1 abrtd: Directory 'kerneloops-1267471146-1' creation detected
2010-03-01T22:19:10.113246+03:00 frontend1 abrtd: Getting local universal unique identification
2010-03-01T22:19:10.119410+03:00 frontend1 abrtd: New crash /var/cache/abrt/kerneloops-1267471146-1, processing
2010-03-01T22:19:10.138685+03:00 frontend1 abrtd: Registered Action plugin 'RunApp'
2010-03-01T22:19:10.138735+03:00 frontend1 abrtd: RunApp('/var/cache/abrt/kerneloops-1267471146-1','test x"`cat component`" = x"xorg-x11-server-Xorg" &&
cp /var/log/Xorg.0.log .')
2010-03-01T22:21:06.111275+03:00 frontend1 abrt: Kerneloops: Reported 1 kernel oopses to Abrt
2010-03-01T22:21:06.111358+03:00 frontend1 abrtd: Directory 'kerneloops-1267471266-1' creation detected
2010-03-01T22:21:06.175171+03:00 frontend1 abrtd: Getting local universal unique identification
2010-03-01T22:21:06.179860+03:00 frontend1 abrtd: New crash /var/cache/abrt/kerneloops-1267471266-1, processing
2010-03-01T22:21:06.179881+03:00 frontend1 abrtd: RunApp('/var/cache/abrt/kerneloops-1267471266-1','test x"`cat component`" = x"xorg-x11-server-Xorg" &&
cp /var/log/Xorg.0.log .')
2010-03-01T22:23:06.112950+03:00 frontend1 abrt: Kerneloops: Reported 1 kernel oopses to Abrt
2010-03-01T22:23:06.113047+03:00 frontend1 abrtd: Directory 'kerneloops-1267471386-1' creation detected
2010-03-01T22:23:06.176437+03:00 frontend1 abrtd: Getting local universal unique identification
2010-03-01T22:23:06.181005+03:00 frontend1 abrtd: New crash /var/cache/abrt/kerneloops-1267471386-1, processing
2010-03-01T22:23:06.181066+03:00 frontend1 abrtd: RunApp('/var/cache/abrt/kerneloops-1267471386-1','test x"`cat component`" = x"xorg-x11-server-Xorg" &&
cp /var/log/Xorg.0.log .')



If I do an 'init 5' while I'm in runlevel 3, I can see Xorg starting
and occupying all of the CPU resources (so that my PC doesn't respond
to keyboard at all, and remote SSH sessions are also interrupted).
Again, I don't see any obvious error messages in the logs when the
system stops responding...

I made a 'yum update', getting all the packages up to date. It didn't
change the behavior at all...

I thought I could reinstall the system completely, but Fedora 12
install DVD also stops responding shortly after the "Check
installation media" step - before actually starting the installation.

At the same time, Fedora 12 Live CD boots up fine (in Gnome) but stops
responding after a few minutes.


I thought this could be a hardware issue. I checked the RAM with
memtest (well, 2 passes went without errors, then I interrupted it).
Then I installed Windows XP - to test if it will fail. XP worked good,
I installed all the drivers and noticed no stability problems at all.

So this looks more like a software incompatibility to me, rather than
a hardware issue (still, I'm not 100% sure)...

Unfortunately my knowledge of Linux isn't any good to be able to
track the problem. Could you please help me to investigate it further?
I can run any tests / provide logs, dumps, etc. Just need to know
where to go and how to look for a solution...


Thanks!



Here are some details for now:

# uname -a
Linux frontend1 2.6.31.12-174.2.22.fc12.i686 #1 SMP Fri Feb 19 19:26:06 UTC 2010 i686 i686 i386 GNU/Linux


End of dmesg when the system stopped responding (while booting
directly to runlevel 5):

ALSA sound/pci/hda/patch_realtek.c:1197: realtek: Enabling init ASM_ID=0xf603 CODEC_ID=10ec0885
input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input5
EXT3 FS on dm-0, internal journal
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Adding 2031608k swap on /dev/mapper/VolGroup00-LogVol01. Priority:-1 extents:1 across:2031608k


respective end of /var/log/messages for ~the same period of time:

2010-03-01T22:12:25.546565+03:00 frontend1 avahi-daemon[1443]: Registering HINFO record with values 'I686'/'LINUX'.
2010-03-01T22:12:26.448523+03:00 frontend1 avahi-daemon[1443]: Server startup complete. Host name is frontend1.local. Local service cookie is 565159940.
2010-03-01T22:12:26.977899+03:00 frontend1 smartd[1578]: smartd 5.39.1 2010-01-28 r3054 [i386-redhat-linux-gnu] (local build)#012Copyright (C) 2002-10 by
Bruce Allen, http://smartmontools.sourceforge.net#012
2010-03-01T22:12:26.977988+03:00 frontend1 smartd[1578]: Opened configuration file /etc/smartd.conf
2010-03-01T22:12:26.989087+03:00 frontend1 smartd[1578]: Configuration file /etc/smartd.conf parsed.
2010-03-01T22:12:26.989152+03:00 frontend1 smartd[1578]: Device: /dev/sda, opened
2010-03-01T22:12:26.998766+03:00 frontend1 smartd[1578]: Device: /dev/sda, found in smartd database.
2010-03-01T22:12:27.279045+03:00 frontend1 smartd[1578]: Device: /dev/sda, is SMART capable. Adding to "monitor" list.
2010-03-01T22:12:27.279187+03:00 frontend1 smartd[1578]: Monitoring 1 ATA and 0 SCSI devices
2010-03-01T22:12:27.350154+03:00 frontend1 avahi-daemon[1443]: Service "frontend1" (/services/ssh.service) successfully established.
2010-03-01T22:12:27.455723+03:00 frontend1 smartd[1602]: smartd has fork()ed into background mode. New PID=1602.


... and the Xorg.log file:

# cat Xorg.0.log

X.Org X Server 1.7.5
Release Date: 2010-02-16
X Protocol Version 11, Revision 0
Build Operating System: x86-04 2.6.18-164.6.1.el5
Current Operating System: Linux frontend1 2.6.31.12-174.2.22.fc12.i686 #1 SMP Fri Feb 19 19:26:06 UTC 2010 i686
Kernel command line: ro root=/dev/VolGroup00/LogVol00 rhgb quiet SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us selinux=0
Build Date: 16 February 2010 04:33:31AM
Build ID: xorg-x11-server 1.7.5-1.fc12
Current version of pixman: 0.16.6
Before reporting problems, check http://bodhi.fedoraproject.org/
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Mar 1 22:12:28 2010
(==) Using config file: "/etc/X11/xorg.conf"
(==) No Layout section. Using the first Screen section.
(==) No screen section available. Using defaults.
(**) |-->Screen "Default Screen Section" (0)
(**) | |-->Monitor "<default monitor>"
(==) No device specified for screen "Default Screen Section".
Using the first device section listed.
(**) | |-->Device "Videocard0"
(==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
(**) Option "AIGLX" "on"
(==) Automatically adding devices
(==) Automatically enabling devices
(==) FontPath set to:
catalogue:/etc/X11/fontpath.d,
built-ins
(**) ModulePath set to "/usr/lib/xorg/modules/extensions/nvidia,/usr/lib/xorg/modules"
(**) Extension "Composite" is enabled
(II) Cannot locate a core pointer device.
(II) Cannot locate a core keyboard device.
(II) The server relies on HAL to provide the list of input devices.
If no devices become available, reconfigure HAL or disable AutoAddDevices.
(II) Loader magic: 0x821c900
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 6.0
X.Org XInput driver : 7.0
X.Org Server Extension : 2.0
(++) using VT number 1

(--) PCI:*(0:1:0:0) 10de:0402:1043:8243 nVidia Corporation GeForce 8600 GT rev 161, Mem @ 0xfd000000/16777216, 0xd0000000/268435456, 0xfa000000/33554432,
I/O @ 0x0000cc00/128, BIOS @ 0x????????/131072
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.7.5, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension SELinux
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.7.5, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions/nvidia/libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Server Extension
(II) NVIDIA GLX Module 190.53 Tue Dec 8 20:47:42 PST 2009
(II) Loading extension GLX
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions/librecord.so
(II) Module record: vendor="X.Org Foundation"
compiled for 1.7.5, module version = 1.13.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension RECORD
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions/libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.7.5, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "dri2"
(II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
compiled for 1.7.5, module version = 1.1.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "nvidia"
(II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
(II) Module nvidia: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Video Driver
(II) NVIDIA dlloader X Driver 190.53 Tue Dec 8 19:16:02 PST 2009
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
(II) Primary Device is: PCI 01@00:00:0
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules/libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.7.5, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "wfb"
(II) LoadModule: "wfb"
(II) Loading /usr/lib/xorg/modules/libwfb.so
(II) Module wfb: vendor="X.Org Foundation"
compiled for 1.7.5, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(II) NVIDIA(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
(==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Option "AddARGBGLXVisuals" "True"
(**) Mar 01 22:12:29 NVIDIA(0): Enabling RENDER acceleration
(II) Mar 01 22:12:29 NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
(II) Mar 01 22:12:29 NVIDIA(0): enabled.
(II) Mar 01 22:12:36 NVIDIA(0): NVIDIA GPU GeForce 8600 GT (G84) at PCI:1:0:0 (GPU-0)
(--) Mar 01 22:12:36 NVIDIA(0): Memory: 524288 kBytes
(--) Mar 01 22:12:36 NVIDIA(0): VideoBIOS: 60.84.41.00.00
(II) Mar 01 22:12:36 NVIDIA(0): Detected PCI Express Link width: 16X
(--) Mar 01 22:12:36 NVIDIA(0): Interlaced video modes are supported on this GPU
(--) Mar 01 22:12:36 NVIDIA(0): Connected display device(s) on GeForce 8600 GT at PCI:1:0:0:
(--) Mar 01 22:12:36 NVIDIA(0): FUS P19-1S (DFP-1)
(--) Mar 01 22:12:36 NVIDIA(0): FUS P19-1S (DFP-1): 330.0 MHz maximum pixel clock
(--) Mar 01 22:12:36 NVIDIA(0): FUS P19-1S (DFP-1): Internal Dual Link TMDS




What else should I check???


--
Best regards,
Andrew

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 03-02-2010, 12:33 PM
Andrew Junev
 
Default Fedora 12 does not work after replacing the motherboard

Tuesday, March 2, 2010, 7:17:57 AM, you wrote:

>> Hello All,
>
>> I kindly ask for your support. On my MythTV frontend-only machine, I
>> had to replace the motherboard. The old motherboard was an ASUS P5KR
>> (Intel P35 chipset), and the newly installed motherboard is an MSI
>> P43T-C51 (Intel P43 chipset). The old MB wasn't faulty - I just had
>> to urgently use it in another machine.
>> Everything else in this system remained basically the same - CPU,
>> RAM, Video, etc. My video adapter is NVidia 8600GT made by ASUS (don't
>> remember the model exactly). I am using proprietary NVidia driver from
>> rpmfusion.
>
>> With the new MSI MB, the system just stops responding when trying to
>> boot into graphical mode (runlevel 5), and there seem to be no errors
>> in /var/log/messages, dmesg or in Xorg.log.

<skip>

>> If I do an 'init 5' while I'm in runlevel 3, I can see Xorg starting
>> and occupying all of the CPU resources (so that my PC doesn't respond
>> to keyboard at all, and remote SSH sessions are also interrupted).
>> Again, I don't see any obvious error messages in the logs when the
>> system stops responding...
>


> Have you rebuilt your initrd images? They possibly contain some drivers
> that your old MB needed and your new MB needs different? The easist way
> is to probably do a "yum reinstall kernel" when you are certain that the
> loaded modules you are using are correct for your system.

Oh, yes!
I think I rebuilt initrd on this machine, as I wanted to disable
nouveau (in order to use proprietary NVidia driver).

'yum reinstall kernel' returns to me:

Package kernel-2.6.31.12-174.2.22.fc12.i686 is allowed multiple installs, skipping



>
> Do this from "init 3" mode. Then debug what's wrong with your graphical
> setup and the new MB before trying to make "init 5" your default boot
> mode again.



>> At the same time, Fedora 12 Live CD boots up fine (in Gnome) but stops
>> responding after a few minutes.


> Any idea why?

Not really... (see below)


>> I thought this could be a hardware issue. I checked the RAM with
>> memtest (well, 2 passes went without errors, then I interrupted it).
>> Then I installed Windows XP - to test if it will fail. XP worked good,
>> I installed all the drivers and noticed no stability problems at all.

> Running memtest overnight or for 24 hours would be a better test. Once
> before I didn;t see an error until the 5th iteration before it triggered
> an error.... Whether it was thermal, or bit pattern related, I never
> did figure out, I just replaced the bad RAM.

Yes, I know I need to test it for a longer period of time. I'll leave
the machine with memtest running tonight... Or ... maybe I'll leave it
with some general system stability test, not to concentrate
exclusively on RAM at this step...


>> What else should I check???
> I like to debug my X configuration using the "startx" command. That way
> I can (usually) abort the server with Ctrl-Alt-Bckspc when necessary. X
> can be a pain when it hangs the machine making it impossible to switch
> to another VC. If you can't login remotely, odds are the whole kernel
> has hung (which is bad for you with the nvidia driver in use as it
> taints the kernel, and noone here will help you debug it unless you can
> reproduce it using either the nv or nouveau drivers).

Yep, thanks for the hint!


> It might be good to see of using nouveau or nv helps you get *some*
> graphics up, even if it doesn't help your MythTV system.

Ummm... I'd also like to try it with nouveau, but I'm not sure how to
do that (I need to somehow get back the original initrd first)...


> Have you tried underclocking your system (if you can)? That might show
> some thermal problems....

Well, I'm not fond of overclocking, so I'm not sure if there's any
possiblity to underclock. BIOS settings are at their defaults (and I
have the latest BIOS version - I checked that). CPU temperature is
around 37C and chipset is around 42C which is (generally) a perfect
temperature for this kind of system. Of course there could be some
other element far from the thermal sensor that gets excessively hot.
But I didn't find anything unusual by now.



Yet, I found another evidence. I tried replacing my video adapter
(8600GT) with an older 7600GS and then with a newer GT220. In both
cases, the system started in graphical mode without any errors. So
it seems that the system works fine with any other video adapter!

I then put my "problematic" 8600GT to a couple of other machines (one
was running similar Fedora 12, and the other one - WinXP). It worked
without issues as well - I watched a movie (using VDPAU) and played a
modern game on a Windows machine. No problems at all...

So there seem to be an incompatibility between a particular MSI MB
and a particular 8600GT video adapter... Ummm...



--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 03-02-2010, 06:50 PM
Andrew Junev
 
Default Fedora 12 does not work after replacing the motherboard

Sorry for double posting. This one is to keep a proper threading:


Tuesday, March 2, 2010, 12:04:24 AM, you wrote:

>> Hello All,
>
>> I kindly ask for your support. On my MythTV frontend-only machine, I
>> had to replace the motherboard. The old motherboard was an ASUS P5KR
>> (Intel P35 chipset), and the newly installed motherboard is an MSI
>> P43T-C51 (Intel P43 chipset). The old MB wasn't faulty - I just had
>> to urgently use it in another machine.
>> Everything else in this system remained basically the same - CPU,
>> RAM, Video, etc. My video adapter is NVidia 8600GT made by ASUS (don't
>> remember the model exactly). I am using proprietary NVidia driver from
>> rpmfusion.
>
>> With the new MSI MB, the system just stops responding when trying to
>> boot into graphical mode (runlevel 5), and there seem to be no errors
>> in /var/log/messages, dmesg or in Xorg.log.

<skip>

>> If I do an 'init 5' while I'm in runlevel 3, I can see Xorg starting
>> and occupying all of the CPU resources (so that my PC doesn't respond
>> to keyboard at all, and remote SSH sessions are also interrupted).
>> Again, I don't see any obvious error messages in the logs when the
>> system stops responding...
>


> Have you rebuilt your initrd images? They possibly contain some drivers
> that your old MB needed and your new MB needs different? The easist way
> is to probably do a "yum reinstall kernel" when you are certain that the
> loaded modules you are using are correct for your system.

Oh, yes!
I think I rebuilt initrd on this machine, as I wanted to disable
nouveau (in order to use proprietary NVidia driver).

'yum reinstall kernel' returns to me:

Package kernel-2.6.31.12-174.2.22.fc12.i686 is allowed multiple installs, skipping



>
> Do this from "init 3" mode. Then debug what's wrong with your graphical
> setup and the new MB before trying to make "init 5" your default boot
> mode again.



>> At the same time, Fedora 12 Live CD boots up fine (in Gnome) but stops
>> responding after a few minutes.


> Any idea why?

Not really... (see below)


>> I thought this could be a hardware issue. I checked the RAM with
>> memtest (well, 2 passes went without errors, then I interrupted it).
>> Then I installed Windows XP - to test if it will fail. XP worked good,
>> I installed all the drivers and noticed no stability problems at all.

> Running memtest overnight or for 24 hours would be a better test. Once
> before I didn;t see an error until the 5th iteration before it triggered
> an error.... Whether it was thermal, or bit pattern related, I never
> did figure out, I just replaced the bad RAM.

Yes, I know I need to test it for a longer period of time. I'll leave
the machine with memtest running tonight... Or ... maybe I'll leave it
with some general system stability test, not to concentrate
exclusively on RAM at this step...


>> What else should I check???
> I like to debug my X configuration using the "startx" command. That way
> I can (usually) abort the server with Ctrl-Alt-Bckspc when necessary. X
> can be a pain when it hangs the machine making it impossible to switch
> to another VC. If you can't login remotely, odds are the whole kernel
> has hung (which is bad for you with the nvidia driver in use as it
> taints the kernel, and noone here will help you debug it unless you can
> reproduce it using either the nv or nouveau drivers).

Yep, thanks for the hint!


> It might be good to see of using nouveau or nv helps you get *some*
> graphics up, even if it doesn't help your MythTV system.

Ummm... I'd also like to try it with nouveau, but I'm not sure how to
do that (I need to somehow get back the original initrd first)...


> Have you tried underclocking your system (if you can)? That might show
> some thermal problems....

Well, I'm not fond of overclocking, so I'm not sure if there's any
possiblity to underclock. BIOS settings are at their defaults (and I
have the latest BIOS version - I checked that). CPU temperature is
around 37C and chipset is around 42C which is (generally) a perfect
temperature for this kind of system. Of course there could be some
other element far from the thermal sensor that gets excessively hot.
But I didn't find anything unusual by now.



Yet, I found another evidence. I tried replacing my video adapter
(8600GT) with an older 7600GS and then with a newer GT220. In both
cases, the system started in graphical mode without any errors. So
it seems that the system works fine with any other video adapter!

I then put my "problematic" 8600GT to a couple of other machines (one
was running similar Fedora 12, and the other one - WinXP). It worked
without issues as well - I watched a movie (using VDPAU) and played a
modern game on a Windows machine. No problems at all...

So there seem to be an incompatibility between a particular MSI MB
and a particular 8600GT video adapter... Ummm...


Please share your ideas on how this could be analyzed further!



--
Best regards,
Andrew

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 03-05-2010, 06:48 PM
Andrew Junev
 
Default Fedora 12 does not work after replacing the motherboard

Tuesday, March 2, 2010, 10:50:29 PM, you wrote:

> Yet, I found another evidence. I tried replacing my video adapter
> (8600GT) with an older 7600GS and then with a newer GT220. In both
> cases, the system started in graphical mode without any errors. So
> it seems that the system works fine with any other video adapter!

> I then put my "problematic" 8600GT to a couple of other machines (one
> was running similar Fedora 12, and the other one - WinXP). It worked
> without issues as well - I watched a movie (using VDPAU) and played a
> modern game on a Windows machine. No problems at all...

> So there seem to be an incompatibility between a particular MSI MB
> and a particular 8600GT video adapter... Ummm...


> Please share your ideas on how this could be analyzed further!

I guess I'll have to reply to myself.
After many attempts to make it work, I still tend to think my 8600GT
is just not compatible with MSI motherboard I have when working under
Fedora. The problem only appears when the card is installed to an MSI
motherboard _and_ only when running Fedora in graphical mode.

Any other cases like installing my video adapter to another
motherboard or putting a new video to MSI motherboard and running
Fedora on it - everything works flawlessly. Windows works just fine in
8600GT + MSI MB combo, too. But trying to run Fedora on this system
just kills the machine within seconds / minutes after switching to
graphical mode, no matter what video driver I use.
Unfortunately, I couldn't get any more details on what is going wrong
in this case.

Anyway, I'm likely to buy a passively-cooled Zotac GT240 now and that
would solve this issue.


--
Best regards,
Andrew



--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 03-06-2010, 06:19 AM
Tim
 
Default Fedora 12 does not work after replacing the motherboard

On Fri, 2010-03-05 at 22:48 +0300, Andrew Junev wrote:
> Any other cases like installing my video adapter to another
> motherboard or putting a new video to MSI motherboard and running
> Fedora on it - everything works flawlessly. Windows works just fine in
> 8600GT + MSI MB combo, too. But trying to run Fedora on this system
> just kills the machine within seconds / minutes after switching to
> graphical mode, no matter what video driver I use.
> Unfortunately, I couldn't get any more details on what is going wrong
> in this case.

Sometime that just happens. I've, also, seen the opposite (a PC dies a
fiery death with Windows).

If you have the ability, you can try getting the computer to output a
log to a serial port, and have another computer monitor it while you
crash it. That's one technique to debug a computer that crashes very
badly.

Ask someone else for advise on setting that up, though. It's a very
long time since I've played with serial ports, and you probably do need
a PC with genuine serial ports to try that.

--
[tim@localhost ~]$ uname -r
2.6.27.25-78.2.56.fc9.i686

Don't send private replies to my address, the mailbox is ignored. I
read messages from the public lists.



--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 03-06-2010, 07:40 AM
Andrew Junev
 
Default Fedora 12 does not work after replacing the motherboard

Hello Tim,

Saturday, March 6, 2010, 10:19:11 AM, you wrote:

> If you have the ability, you can try getting the computer to output a
> log to a serial port, and have another computer monitor it while you
> crash it. That's one technique to debug a computer that crashes very
> badly.

Thanks for the hint! That's an interesting idea. I do have a "proper"
serial port on the motherboard, and I can find another machine with a
serial port to monitor it.

But...

> Ask someone else for advise on setting that up, though. It's a very
> long time since I've played with serial ports, and you probably do need
> a PC with genuine serial ports to try that.

That's the problem. I have no idea on how to configure a machine to
output logs to a serial port. And I don't really know what logs should
be put there.
'/var/log/messages' are being kept on the disk after a reboot, and it
doesn't contain anything wrong, in my opinion...


--
Best regards,
Andrew

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 03-07-2010, 07:38 AM
Chris Kloiber
 
Default Fedora 12 does not work after replacing the motherboard

Well if a kernel is panics, the first thing it typically does is stop
disk writing to prevent corruption (I haven't played with kdump yet).
More stuff can often get logged, but its lost in memory when the board
gets re-powered. If you are logging to serial, that information can
sometimes be preserved.


--
Chris Kloiber


On 03/06/2010 03:40 AM, Andrew Junev wrote:

Hello Tim,

Saturday, March 6, 2010, 10:19:11 AM, you wrote:


If you have the ability, you can try getting the computer to output a
log to a serial port, and have another computer monitor it while you
crash it. That's one technique to debug a computer that crashes very
badly.


Thanks for the hint! That's an interesting idea. I do have a "proper"
serial port on the motherboard, and I can find another machine with a
serial port to monitor it.

But...


Ask someone else for advise on setting that up, though. It's a very
long time since I've played with serial ports, and you probably do need
a PC with genuine serial ports to try that.


That's the problem. I have no idea on how to configure a machine to
output logs to a serial port. And I don't really know what logs should
be put there.
'/var/log/messages' are being kept on the disk after a reboot, and it
doesn't contain anything wrong, in my opinion...




--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 

Thread Tools




All times are GMT. The time now is 10:17 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org