LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Desktop
User Name
Password
Linux - Desktop This forum is for the discussion of all Linux Software used in a desktop context.

Notices

Reply
 
Search this Thread
Old 09-17-2013, 10:15 AM   #1
wikapuki
Member
 
Registered: Jun 2009
Distribution: Debian
Posts: 78

Rep: Reputation: 15
Swapped out Motherboard+CPU now desktop gone... ish


Debian Wheezy, gnome3

This weekend a friend swapped out a motherboard and CPU, used the same Graphics card (Sapphire HDMI, DVI, VGA) of which I use only the VGA.

When system now boots, all I get is a black blank screen but the mouse moves.
However if I VNC into the machine I get the desktop background.

If I do a ps ax | grep gnome-shell and do a kill -HUP <process-id> while VNC'd into it, the original desktop appears but there is no keybaord or mouse control.

Unfortuantely I cannot remove the card to force it to use the onboard VGA as I am disabled and can only do that when competent IT people are visiting.

Is there some files I can hand modify or remove that will for the system to use the monitor and old desktop?
 
Old 09-17-2013, 10:48 AM   #2
cynwulf
Senior Member
 
Registered: Apr 2005
Distribution: OpenBSD, FreeBSD
Posts: 1,304

Rep: Reputation: Disabled
Strange... Do you have an xorg.conf defined? Perhaps there is some configuration there specific to the other machine (bus ID?)?

Post your full /var/log/Xorg.0.log
 
1 members found this post helpful.
Old 09-17-2013, 11:58 AM   #3
wikapuki
Member
 
Registered: Jun 2009
Distribution: Debian
Posts: 78

Original Poster
Rep: Reputation: 15
Yes I have /etc/X11/xorg.conf

here are both files.
Attached Files
File Type: log Xorg.0.log (51.5 KB, 6 views)
File Type: txt xorg.conf.txt (1.6 KB, 4 views)
 
Old 09-18-2013, 03:00 AM   #4
cynwulf
Senior Member
 
Registered: Apr 2005
Distribution: OpenBSD, FreeBSD
Posts: 1,304

Rep: Reputation: Disabled
Code:
# mv /etc/X11/xorg.conf /etc/X11/xorg.conf.old
And try to startx?

You had refresh/sync values defined but commented them out, do you have an old CRT monitor?
 
1 members found this post helpful.
Old 09-18-2013, 04:41 AM   #5
wikapuki
Member
 
Registered: Jun 2009
Distribution: Debian
Posts: 78

Original Poster
Rep: Reputation: 15
Same result, will try moving the monitors.xml file to monitors.xml.old from home? I presume it should recreate it ?
 
Old 09-23-2013, 03:54 AM   #6
gradinaruvasile
Member
 
Registered: Apr 2010
Location: Cluj, Romania
Distribution: Debian Testing
Posts: 515

Rep: Reputation: 102Reputation: 102
The log shows that your monitor is detected and the EDID is read from it, so that should not be an issue. What mobo did you have previously and what do you have now?
 
Old 09-23-2013, 08:10 AM   #7
wikapuki
Member
 
Registered: Jun 2009
Distribution: Debian
Posts: 78

Original Poster
Rep: Reputation: 15
The replacement MOBO is an ASROCK p4vm890 HAL says: 'K7VT4 motherboard' with a 2.5GHz Celeron CPU :-(
The Old MOBO is an MSI with a 3GHz CPU :-) (I've attached the last messages boot log as I cant remember full spec)

Video card used on both systems: HAL says: 'Redwood PRO [Radeon HD 5500 Series]' (DVI VGA & HDMI)


In the old Mobo BIOS I could DISABLE the onboard graphics, in the ASROCK BIOS I can only set which one is primary, it's set to PCIe (The Saphhire Radeon).

During boot which ever you have set as primary we see the Boot, Grub, Boot until X starts, then the screen goes blank but the mouse moves.

VNC shows the desktop background but nothing else until I ssh into it and do a -HUP on the gnome-shell which then displays everything but the mouse and keyboard don't work via VNC. However the real VGA screen remains Blank with a mouse that can move.

hwinfo (HAL) states: fbcon: radeondrmfb (fb0) is primary device

Also attached: Jill MK6 hwinfo-snip.log


It's all a complete nightmare as it will be weeks before anyone can swap the motherboard/CPU back. Thank goodness for ssh -X, X11 & nfs so I can get to the stuff I need!!

Note: The following is not written for answers, just background.

It appears the random crashing of previous board may have been the SATA card, not sure, cos since in new MOBO a drive attached started giving off lots of errors and went read only... YET when I made an image of the said drive with ddrescue it found no errors. So its either a loose/bad cable or bad port on the SATA card. smartctrl says the drive is fine... go figure. Anyway I have an image so happy to leave that problem aside.

Then Samba will not start it's smdb either (seg fault core dumps) which was not happening before the swapout, hence Phew for NFS.
Attached Files
File Type: txt Jill Boot Sep11 messages.txt (44.8 KB, 2 views)
File Type: log Jill MK6 hwinfo-snip.log (53.5 KB, 2 views)
 
Old 09-23-2013, 01:26 PM   #8
gradinaruvasile
Member
 
Registered: Apr 2010
Location: Cluj, Romania
Distribution: Debian Testing
Posts: 515

Rep: Reputation: 102Reputation: 102
You should use a newer kernel, you have there the one compiled for 486. Use i686, it should work with what you have. Also you should run a memtest.
 
Old 09-23-2013, 06:52 PM   #9
Shadow_7
Senior Member
 
Registered: Feb 2003
Distribution: debian
Posts: 1,530

Rep: Reputation: 238Reputation: 238Reputation: 238
You may need to modify the /etc/X11/xorg.conf.

Code:
      Driver "vesa"
      BusID "PCI:0:13:0"
Those values probably differ on the new motherboard. Namely the BusID location. lspci will help find out what applies. If you're on a relatively new-ish distro with distro supplied kernel, you might be able to just remove / rename the /etc/X11/xorg.conf file and X might run. Otherwise adjust the settings accordingly.
 
1 members found this post helpful.
Old 09-24-2013, 05:49 AM   #10
wikapuki
Member
 
Registered: Jun 2009
Distribution: Debian
Posts: 78

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by gradinaruvasile View Post
You should use a newer kernel, you have there the one compiled for 486. Use i686, it should work with what you have. Also you should run a memtest.
Are you sure? I did a: apt-cache search linux-headers-
Code:
linux-headers-3.2.0-4-486 - Header files for Linux 3.2.0-4-486
linux-headers-3.2.0-4-686-pae - Header files for Linux 3.2.0-4-686-pae
linux-headers-3.2.0-4-all - All header files for Linux 3.2 (meta-package)
linux-headers-3.2.0-4-all-i386 - All header files for Linux 3.2 (meta-package)
linux-headers-3.2.0-4-amd64 - Header files for Linux 3.2.0-4-amd64
linux-headers-3.2.0-4-common - Common header files for Linux 3.2.0-4
linux-headers-3.2.0-4-common-rt - Common header files for Linux 3.2.0-4-rt
linux-headers-3.2.0-4-rt-686-pae - Header files for Linux 3.2.0-4-rt-686-pae
linux-headers-2.6-486 - Header files for Linux 486 configuration (dummy package)
linux-headers-2.6-686-pae - Header files for Linux 686-pae configuration (dummy package)
linux-headers-2.6-amd64 - Header files for Linux amd64 configuration (dummy package)
linux-headers-486 - Header files for Linux 486 configuration (meta-package)
linux-headers-686-pae - Header files for Linux 686-pae configuration (meta-package)
linux-headers-amd64 - Header files for Linux amd64 configuration (meta-package)
linux-headers-rt-686-pae - Header files for Linux rt-686-pae configuration (meta-package)
linux-headers-3.2.0-0.bpo.4-486 - Header files for Linux 3.2.0-0.bpo.4-486
linux-headers-3.2.0-0.bpo.4-686-pae - Header files for Linux 3.2.0-0.bpo.4-686-pae
linux-headers-3.2.0-0.bpo.4-all - All header files for Linux 3.2 (meta-package)
linux-headers-3.2.0-0.bpo.4-all-i386 - All header files for Linux 3.2 (meta-package)
linux-headers-3.2.0-0.bpo.4-amd64 - Header files for Linux 3.2.0-0.bpo.4-amd64
linux-headers-3.2.0-0.bpo.4-common - Common header files for Linux 3.2.0-0.bpo.4
linux-headers-3.2.0-0.bpo.4-common-rt - Common header files for Linux 3.2.0-0.bpo.4-rt
linux-headers-3.2.0-0.bpo.4-rt-686-pae - Header files for Linux 3.2.0-0.bpo.4-rt-686-pae
then did: apt-get install linux-headers-3.2.0-4-686-pae
Code:
Preparing to replace linux-headers-3.2.0-4-486 3.2.46-1+deb7u1 (using .../linux-headers-3.2.0-4-486_3.2.51-1_i386.deb) ...
Unpacking replacement linux-headers-3.2.0-4-486 ...
Preparing to replace linux-headers-3.2.0-4-common 3.2.46-1+deb7u1 (using .../linux-headers-3.2.0-4-common_3.2.51-1_i386.deb) ...
Unpacking replacement linux-headers-3.2.0-4-common ...
Selecting previously unselected package linux-headers-3.2.0-4-686-pae.
Unpacking linux-headers-3.2.0-4-686-pae (from .../linux-headers-3.2.0-4-686-pae_3.2.51-1_i386.deb) ...
Setting up tex-common (3.15) ...
Running mktexlsr. This may take some time... done.
Running updmap-sys. This may take some time... 
updmap-sys failed. Output has been stored in
/tmp/updmap.e2YsuK8L
Please include this file if you report a bug.

Sometimes, not accepting conffile updates in /etc/texmf/updmap.d
causes updmap-sys to fail.  Please check for files with extension
.dpkg-dist or .ucf-dist in this directory

dpkg: error processing tex-common (--configure):
 subprocess installed post-installation script returned error exit status 1
Setting up linux-headers-3.2.0-4-common (3.2.51-1) ...
Setting up linux-headers-3.2.0-4-486 (3.2.51-1) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 3.2.0-4-486
Error! Could not locate dkms.conf file.
File:  does not exist.
Setting up linux-headers-3.2.0-4-686-pae (3.2.51-1) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 3.2.0-4-686-pae
Error! Could not locate dkms.conf file.
File:  does not exist.
Errors were encountered while processing:
 tex-common
E: Sub-process /usr/bin/dpkg returned an error code (1)
Ignore the tex-common (3.15) error, that has been with me since gnome3 upgrade and keeps returning after all attempts to get rid off. Other stuff still upgrades/installs.
 
Old 09-24-2013, 05:52 AM   #11
wikapuki
Member
 
Registered: Jun 2009
Distribution: Debian
Posts: 78

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by cynwulf View Post
Code:
# mv /etc/X11/xorg.conf /etc/X11/xorg.conf.old
And try to startx?

You had refresh/sync values defined but commented them out, do you have an old CRT monitor?
Its a VGA Flatscreen. I did do the move and start but did not check (Opps) that a new xorg.conf had been made. It had NOT.

so did Xorg -configure and copied the file from /root but that did not work (as expected since Xorg -configure exited with errors).
 
Old 09-24-2013, 08:44 AM   #12
wikapuki
Member
 
Registered: Jun 2009
Distribution: Debian
Posts: 78

Original Poster
Rep: Reputation: 15
Smile Solved

uname -ra:
Linux jilldando 3.2.0-4-486 #1 Debian 3.2.46-1+deb7u1 i686 GNU/Linux

Success!! Thank you all.

I recreated xorg.conf file by NOT ssh -X into the box and doing:
Xorg -configure

then edited (with your fav editor) :-) /root/xorg.conf.new
It had 3 device sections

Quote:
Section "Device"
Identifier "Card0"
Driver "radeon"
BusID "PCI:2:0:0"
EndSection

Section "Device"
Identifier "Card1"
Driver "fbdev"
BusID "PCI:2:0:0"
EndSection

Section "Device"
Identifier "Card2"
Driver "vesa"
BusID "PCI:2:0:0"
EndSection
It is a radeon card but I remembered seeing during boot it stating
Quote:
fbcon: radeondrmfb (fb0) is primary device
So I changed all 3 Device sections to

Quote:
Section "Device"
Identifier "Card0"
Driver "fbdev"
BusID "PCI:2:0:0"
EndSection

Section "Device"
Identifier "Card1"
Driver "fbdev"
BusID "PCI:2:0:0"
EndSection

Section "Device"
Identifier "Card2"
Driver "fbdev"
BusID "PCI:2:0:0"
EndSection
and that worked!


Strangely all the gnome3 new stuff (Applications with sidebar and the Windows/Applications thing under the top bar) have gone!!! It Looks like a hybrid gnome2 gname3 desktop and it works faster!!!! Yes

The Monitor attached can no longer be detected but thats fine.

I am just concerned about being told to install the 686 kernel yet on this debian site it states:
Quote:
Upgrade issues

Linux: linux-image-686-bigmem kernel flavor renamed to linux-image-686-pae, 686 flavor dropped. 686-class systems not supporting Physical Address Extension - all 400 MHz-bus versions of the Intel Pentium M and Celeron M (i.e. all "Banias" and pre-Sonoma "Dothan"), VIA C3 "Nehemiah" and AMD Geode LX - should migrate to the 486 flavour (also more efficient due to optimisation for uniprocessor systems).
So off to software forum to work out the samba cores dumps.
 
  


Reply

Tags
gnome-shell, vga, x11vnc


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
not sure whether this motherboard would take my CPU newbiesforever General 5 07-20-2013 10:14 AM
[SOLVED] What Motherboard has the most CPU's? BuckNekkid Linux - Hardware 12 03-22-2012 03:30 AM
Swapped Motherboard and Lost Internet Access in Kubuntu 10.4 mhumm2 Linux - Desktop 2 05-10-2011 09:19 AM
USB ports not working properly- Slack 12.2 & old-ish motherboard bogzab Slackware 6 08-27-2009 04:08 AM
Remote desktop/headless(ish) config help please ADxD_7 Solaris / OpenSolaris 0 03-18-2009 03:53 PM


All times are GMT -5. The time now is 09:57 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration