I performed an upgrade from the above to R5C7 and X will not start.

I have tried an nVidia MX400/440/4000 card and an nVidia FX 5500 card, but haven't had any success getting it up and running. It is really puzzling.

I ran the Auto Upgrade install several times with the same result-No X.

I've also ran the nvida-install-debian.sh script, but it didn't help or install correctly. I ran the nvidia driver install script from nvidia's website. This script completed and appeared to install correctly. I have uncompressed the kernel before each attempt. I also stopped the gdm.

The results from each attempt of starting X is that it states the XF86Config-4 is not configured corectly and would I like to view the file. I reply Yes and view the file, but there is no text to review (it also shows 100% at the bottom of the screen). It then drops me down to the CLI.

I've tried to use the nvidia installers XF86Config-4 file, but it didn't help. I also have a copy of my original file from R5A26, but it too doesn't help. I'm at my wits end and I don't know what else to try.

My configuration is:
either MX4xxx or FX 5500 nVidia video card
2 -PVR-350
1 -200GB PATA HDD
1 -300GB PATA HDD
(Both HDD are part of the LVM VG group)
Athlon 2800+
DFI nF4 250gb MB (with 7.1 Audio, NIC, etc. on board)

The system and all components were working prior to the upgrade attempt.

Incidentally, even though I've ran the auto upgrade several times, from more than one CD, it has not ran the restore database (or myth) yet. I have recreated the LVM VG group by running the recreate LVM script.

Any and all help will be very much appreciated!

Thanks --Brian

Did you follow the R5C7 upgrade hints sticky here? http://mysettopbox.tv/phpBB2/viewtopic.php?t=10116

Have you looked at the troubleshooting pages on the wiki? Especially: http://www.knoppmythwiki.org/index.php? ... ngLogFiles and: http://www.knoppmythwiki.org/index.php? ... terInstall

I found the R5C7 upgrade sticky a bit too late, but I did perform similar steps, just not in the process described. I did a restore and backed up my XF86Config-4 file to another machine.

I appreciate the heads up on the log files and messages. I'll review them and hopefully have a followup post with additional information.

Below is the output from my dmesg log file:

Looking through dmesg file:
Boot video device is 0000:01:00.0
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected AGP bridge 0
agpgart: Setting up Nforce3 AGP.
agpgart: AGP aperture is 128M @ 0xd0000000
ACPI: PCI Interrupt Link [APCJ] enabled at IRQ 20
ACPI: PCI Interrupt 0000:00:06.0[A] -> Link [APCJ] -> GSI 20 (level, high) -> IRQ 19
PCI: Setting latency timer of device 0000:00:06.0 to 64
intel8x0_measure_ac97_clock: measured 51625 usecs
intel8x0: clocking to 46902
NET: Registered protocol family 17
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
Linux video capture interface: v1.00
saa7146: register extension 'dvb'.
saa7146: register extension 'budget dvb'.
saa7146: register extension 'budget_ci dvb'.
bttv: driver version 0.9.16 loaded
bttv: using 8 buffers with 2080k (520 pages) each for capture
bt878: AUDIO driver version 0.0.0 loaded
saa7146: register extension 'budget_av'.
usbcore: registered new driver ttusb
usbcore: registered new driver ttusb-dec

Grep'ping through the file:
grep -i agp /var/log/dmesg

ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGPB._PRT]
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected AGP bridge 0
agpgart: Setting up Nforce3 AGP.
agpgart: AGP aperture is 128M @ 0xd0000000

The Syslog File
grep -i nvidia /var/log/syslog:

Aug 16 05:05:14 mythtv kernel: NVRM: loading NVIDIA Linux x86 Kernel Module 1.0-8762 Mon May 15 13:06:38 PDT 2006
Aug 27 17:12:40 mythtv kernel: ACPI: RSDP (v000 Nvidia ) @ 0x000f7b00
Aug 27 17:12:40 mythtv kernel: ACPI: RSDT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3fff3040
Aug 27 17:12:40 mythtv kernel: ACPI: FADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3fff30c0
Aug 27 17:12:40 mythtv kernel: ACPI: MADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3fff7bc0
Aug 27 17:12:40 mythtv kernel: ACPI: DSDT (v001 NVIDIA AWRDACPI 0x00001000 MSFT 0x0100000e) @ 0x00000000

The Messages File
grep -i nvidia /var/log/messages

Aug 16 05:05:14 mythtv kernel: nvidia: module license 'NVIDIA' taints kernel.
Aug 16 05:05:14 mythtv kernel: NVRM: loading NVIDIA Linux x86 Kernel Module 1.0-8762 Mon May 15 13:06:38 PDT 2006

The Daemon File
From /var/log/daemon.log:

Aug 27 17:13:06 mythtv gdm[5232]: deal_with_x_crashes: Running the XKeepsCrashing script
Aug 27 17:13:10 mythtv gdm[5232]: Failed to start X server several times in a short time period; disabling display :0

From /var/log/kern.log:

Grep –I nvidia
Aug 16 05:05:14 mythtv kernel: nvidia: module license 'NVIDIA' taints kernel.
Aug 16 05:05:14 mythtv kernel: NVRM: loading NVIDIA Linux x86 Kernel Module 1.0-8762 Mon May 15 13:06:38 PDT 2006
Aug 27 17:12:40 mythtv kernel: ACPI: RSDP (v000 Nvidia ) @ 0x000f7b00
Aug 27 17:12:40 mythtv kernel: ACPI: RSDT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3fff3040
Aug 27 17:12:40 mythtv kernel: ACPI: FADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3fff30c0
Aug 27 17:12:40 mythtv kernel: ACPI: MADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3fff7bc0
Aug 27 17:12:40 mythtv kernel: ACPI: DSDT (v001 NVIDIA AWRDACPI 0x00001000 MSFT 0x0100000e) @ 0x00000000

Grep –I agp
Aug 27 17:12:40 mythtv kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGPB._PRT]
Aug 27 17:12:40 mythtv kernel: Linux agpgart interface v0.101 (c) Dave Jones
Aug 27 17:12:40 mythtv kernel: agpgart: Detected AGP bridge 0
Aug 27 17:12:40 mythtv kernel: agpgart: Setting up Nforce3 AGP.
Aug 27 17:12:40 mythtv kernel: agpgart: AGP aperture is 128M @ 0xd0000000


The Nvidia Installation Log File:

From nvidia Installation Log:

-> Kernel module compilation complete.
-> Kernel messages:
ivtv1: loaded v4l-cx2341x-init.mpg firmware (155648 bytes)
tuner 3-0061: type set to 47 (LG NTSC (TAPE series))
ivtv1: Initialized WinTV PVR 350, card #1
ivtv: ==================== END INIT IVTV ====================
input: PC Speaker as /class/input/input2
00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
NET: Registered protocol family 23
eth0: no IPv6 routers present
ACPI: PCI Interrupt Link [APCL] enabled at IRQ 22
ACPI: PCI Interrupt 0000:00:02.2[C] -> Link [APCL] -> GSI 22 (level, high)
-> IRQ 16
PCI: Setting latency timer of device 0000:00:02.2 to 64
ehci_hcd 0000:00:02.2: EHCI Host Controller
ehci_hcd 0000:00:02.2: debug port 1
PCI: cache line size of 64 is not supported by device 0000:00:02.2
ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 3
ehci_hcd 0000:00:02.2: irq 16, io mem 0xe3004000
ehci_hcd 0000:00:02.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 8 ports detected
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
nvidia: module license 'NVIDIA' taints kernel.
ACPI: PCI Interrupt Link [APC5] enabled at IRQ 16
ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [APC5] -> GSI 16 (level, low) ->
IRQ 20
NVRM: loading NVIDIA Linux x86 Kernel Module 1.0-8762 Mon May 15 13:06:38
PDT 2006
-> Installing both new and classic TLS OpenGL libraries.
-> Parsing log file:
-> done.
-> Validating previous installation:
-> done.
-> Uninstalling NVIDIA Accelerated Graphics Driver for Linux-x86 (1.0-8762):
-> done.
-> Uninstallation of existing driver: NVIDIA Accelerated Graphics Driver for
Linux-x86 (1.0-8762) is complete.
-> Installing 'NVIDIA Accelerated Graphics Driver for Linux-x86' (1.0-8762):
executing: '/sbin/ldconfig'...
executing: '/sbin/depmod -aq'...
-> done.
-> Driver file installation is complete.
-> Running post-install sanity check:
-> done.
-> Post-install sanity check passed.
-> Shared memory test passed.
-> Running runtime sanity check:
-> done.
-> Runtime sanity check passed.
-> Would you like to run the nvidia-xconfig utility to automatically update you
r X configuration file so that the NVIDIA X driver will be used when you res
tart X? Any pre-existing X configuration file will be backed up. (Answer: Y
es)
-> Your X configuration file has been successfully updated. Installation of
the NVIDIA Accelerated Graphics Driver for Linux-x86 (version: 1.0-8762) is
now complete.

The nvidia installation script claims it is complete and hopefully setup correctly. I've tried running it several times with the same result.

What seems strange is that there isn't a descriptive name for the card present in these files. For example, NVidia MX4000, Nvidia FX-5500, etc.

Is there permission issues that can stop gdm from loading/running properly?

The other issue that I find strange is that the X Log file when X doesn't load properly and is the XF86Config-4 file is displayed to allow me to troubleshoot the configuration. There isn't any text in the display to allow troubleshooting. Usually, it will display the XF86Config-4 file for review. The file is located in /etc/X11/, named XF86Config-4 and is not blank.

Once again, thanks for any and all advise.

--Brian

For X problems you ought tobe looking at the X log file - /var/log/XFree86.0.log as descibed in http://www.knoppmythwiki.org/index.php?page=CheckingLogFile

The problem is usually either that X isn't starting properly because it's misconfigured so that X gives up (try this sample XF86Config-4) or because the TV can't sync to the Modeline it's using even though X thinks everything is fine.

Hi,

Do a ctl alt f1 and login as root
# killall gdm
# startx

It will most likely dump out and you can read what it thinks are troubles. Most likely, the Driver is set as nv where with the 5200 should be "nvidia"

Then retry startx, when x finally does start, do ctl alt Backspace to kill it. Once x runs, enter gdm to restart xserver & frontend system

You can also use "vesa" as a driver, generic in nature but works 99.9% with just a little less performance but great for testing / setup.

Mike

tjc,

There isn't an var/log/XFree86xx.log file in my /var/log/ directory? Strange huh!

Researching the wiki for checking config file.

Also tried killall gdm and startx, but that came up with the following:

Using authority file /root/.Xauthority
Writing authority file /root/.Xauthority
Using authority file /root/.Xauthority
Writing authority file /root/.Xauthority
xinit: Server error.

Brian

/root/.Xauthority File is a zero bit file:

-rw------- 1 root root 0 Aug 27 23:51 .Xauthority

Brian

Hi,

When playing with xserver, you have to login as root. If you can do it with ssh that is ok also.
The log should be less /var/log/gdm/:0.log

# killall gdm stops the desktop manager
# startx simply starts up the gui screen driver (may be wrong way to say it)
# gdm should startx & bring up the mythfrontend once you can startx.
If there is a problem with x, it will dump out and show you the error(s) so that you may go back in to /etc/X11/XF86Config-4 to fix it / them. To get a basic driver running, it needs to match the card and sometimes I have seen a mis-id . My Dell for example, will id the nvidia card just fine however sticks ati in as the driver. Driver "nvidia" and I am good to go.


Since x is not running, you don't need to do ctl alt F1, you should be at the console already, just login as root. Re-try the previous commands.

Normal:
-rw------- 1 root root 0 May 15 11:22 /root/.Xauthority

Mike

After some edits to the XF86Config and XF86Config-4 files (I made them the same) I tried to start X and this is the output.

startx
Using authority file /root/.Xauthority
Writing authority file /root/.Xauthority
Using authority file /root/.Xauthority
Writing authority file /root/.Xauthority

X: warning; process set to priority -1 instead of requested priority 0
giving up.
xinit: No such file or directory (errno 2): unable to connect to X server
xinit: No such process (errno 3): Server error.

Any ideas? --Brian

Hi,

Just soaked in, (it's a rainy day) :


May have been a defective upgrade, maybe try rerun the install cd with boot: knoppmyth testcd It will check things and report out.. You can abort the actual install with a reset.

Mike

This problem was all due to a bad CD-Rom Burn from one of the Mirrors.

I downloaded the ISO from the same site three times, primarily because it was faster than others.

I tried installing the upgrade multiple times from three different CDs. Each without success. I downloaded the ISO from a different mirror--a lot slower. But it worked. All is well in the universe again.

The solution is to take the upgrade hints. I did not run the TESTCD option on the upgrade until the fifth try. All failed until the last burn from the slow mirror.

The moral of the story is to run the upgrade with the TESTCD Option. I feel extremely foolish, but I sincerely appreciate everyones help.

I'm currently up and running R5C7 with zero loss of data--only time was lost. Thanks again everyone for your help.

_________________
--Brian
___________________
BE / FE v8.6
Intel NUC PC NUC7i5BNH
FE for v8.6
Intel NUC PC UDC3217BY
BE / FE v9
Giada Mini PC
3 each WeChip Mini Air Mouse
1 - HDHomeRun Dual Tuner
1 - HDHomeRun Flex Quatro Tuner
OTA Amplified Antenna
Since 2003

Hi,

Good story I like happy endings..

Don't feel too bad about not testing the cd, we all sometimes have trouble taking a hint.

Have a great day!
Mike