System will not shutdown nor reboot

Asked by Gary Ratliff Sr. on 2006-11-03

I have Ubuntu 6.06 installed in two different partitions on my 100 gig hard drive.

On the initial install in each of these the screen resolution was 640x480. Installing easyubuntu and selecting the ati graphics drivers did not change this. Now I soon purchased the book: Ubuntu Unleashed and learned thet the driver I wanted was installed by:

sudo apt-get install xorg-driver-fglrx fglrx-control

This is followed by sudo gedit /etc/X11/xorg.conf and changing the driver from:
"ati" to "fglrx"

Now I have 3d acceleration and I can chose various svreen resolutions. Here I am using the 1280x1024 which is recomended for the HP vs17e TFT monitor.

Now when clicking the icon in the right upper corner of thescreen any link to restart, shutdown or hybernate yields a blank screen and after a wait pressing the on/off switch om the console reboots the machine.

As the HP Pavillion a1253w uses an amd64 I instaled the 64 version of ubuntu to another partition and grub set this up so it boots: generic amd84 on hda7, i386 on hda6 and xp media center edition on had1.

Now again the start resolution was 640x480 and I again set up the fllrx driver and agian could not reboot with out manually turning off the machine.

Other than that the system works as expected.

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu gnome-power-manager Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Júlio Santos Monteiro (juliomonteiro) said :
#1

Here it go some questions:

1- Are you using Ubuntu Edgy or Ubuntu Dapper?

2- You get the blank screen *before* or *after* pressing restart/shutdown/hypernate?

3- Try this command and tell me if it work:
sudo halt
... or ...
sudo reboot

If the commands (sudo halt / sudo reboot) work, this mean there is probably a bug in GNOME.

Thanks!

Revision history for this message
Gary Ratliff Sr. (eronstuc) said :
#2

To answer your questions:1) I am using Ubuntu Dapper on both the i386 and amd64 partitions.� The uname -r for the amd 64 side yields:� 2.6.15-27-amd64-generic.� The i386 partition is also using the 2.6.27 kernel.� The 386 partition was installed from a cd in the recent Linux Format magazine.� The amd 64 version was from a set of 10 cd's� I recieved from your cd mail program.� I took 8 of these cd's to the local computer repair shop:� Computer Systems and Technology Inc.� on Hardy Street in Hattiesburg.� Thus he can pass these out to his customers to introduce them to Ubuntu.� Also if I knew when the USM Linux User group was having an install fest I might like to obtain some for them to give out to the people attending to have a system installed.� This is usually in the spring.2.� The blank screen happens after pressing the icons for restart/shutdown/or hybernate.� Also the screen blanks out if trying to change the run level using the init 0� or init 6. 3.� The command sudo
halt yields a blank screen when used.� Because the symptoms only happened once the fglrx driver from ati was installed I checked the search at:google.com/linus for the word fglrx.� Here was some comments to the need to alter the gdm.comf file in:/etc/gdm/gdm.conf so that AlwaysRestartServer=true isused.Using cat /etc/gdm/gdm.conf | grep Always shows that all instances of this are on lines which have been commented out.� The original line was thus:#AlwaysRestartServer=false.� This was changed to the recommended:� AlwaysRestartServer=true and did not yield any altered behavior.One other side effect from the install of the ati fglrx driver also seems to be that when I had a screen resolution of 640x480 my webcam worked with xawtv and produced a good picture.� However once the ati drivers were used the command to start xawtv also produces a blank screen from which the only recoivery is to press the on/off switch on the hard drive.Regards,Gary --- On Fri 11/03,
=?utf-8?q?J=C3=BAlio_Santos_Monteiro?= &lt; <email address hidden> &gt; wrote:From: =?utf-8?q?J=C3=BAlio_Santos_Monteiro?= [mailto: <email address hidden>]To: <email address hidden>: Sat, 04 Nov 2006 02:27:22 -0000Subject: [Support #2326]: Re: System will not shutdown nor rebootSupport request #2326 on Ubuntu changed:https://launchpad.net/distros/ubuntu/+ticket/2326Comment:Here it go some questions:1- Are you using Ubuntu Edgy or Ubuntu Dapper?2- You get the blank screen *before* or *after* pressing restart/shutdown/hypernate?3- Try this command and tell me if it work:sudo halt... or ...sudo rebootIf the commands (sudo halt / sudo reboot) work, this mean there is probably a bug in GNOME.Thanks!Regards,Gary

_______________________________________________
No banners. No pop-ups. No kidding.
Make My Way your home on the Web - http://www.myway.com

Revision history for this message
Gary Ratliff Sr. (eronstuc) said :
#3

I replied to this already.� However, some experimentation with the problem confirms that the problem is comming from the fglrx driver from ati.As I have two complete distros of Ubuntu it is possible to use one for a test.� Now as I cannot use the APLX fro Linux from Micro APL Ltd.� And as some of the features from easyubuntu hae not yet been setu for the amd64 platform, I decided to limit my experiments fo the amd64� version.first lsmod was used to determing the names of the drivers in use on the system.� Now the command:sudo rmmod fglrx yielded the info that this could not be removed as it was in use.� Reboot system and use the recovery mode to be in single user mode.� Now rmmod fglrx dosn't work as the module is not loaded at the single user runlevel.However, the exit command allows booting to level 5.So the last step to set up the driver was to edit /etc/X11/xorg.cong to change the driver from &quot;ati&quot; to &quot;fglrx&quot;.� Therefore, a sudo gedit
/etc/X11/xorg.conf was given and the driver line restored to &quot;ati&quot;.Also xawtv and its plugin's was installed as I noted in the previous reply that this now also froze the screen.Now once the xorg.conf file was restored.� A re-boot (manually using the on/off switch) Set up a system which now had a resolution of 640x480 and the ability to shutdown and restart the system in the amd 64 mode functioned properly.� Also the web camera was able to be used when the xawtv command was issued.Therefore, the area search for correcting the problem is with the fglrx under the known problems.� Hopefully so user will have found the same error and perhaps ati will have addressed the issue.I noticed that on last friday one of my updates was for the fglrx-control and xorg-driver-fglrx yet the install did not correct the problem I am experiencing with this.Regards,Gary --- On Fri 11/03, =?utf-8?q?J=C3=BAlio_Santos_Monteiro?= &lt; <email address hidden> &gt; wrote:From:
=?utf-8?q?J=C3=BAlio_Santos_Monteiro?= [mailto: <email address hidden>]To: <email address hidden>: Sat, 04 Nov 2006 02:27:22 -0000Subject: [Support #2326]: Re: System will not shutdown nor rebootSupport request #2326 on Ubuntu changed:https://launchpad.net/distros/ubuntu/+ticket/2326Comment:Here it go some questions:1- Are you using Ubuntu Edgy or Ubuntu Dapper?2- You get the blank screen *before* or *after* pressing restart/shutdown/hypernate?3- Try this command and tell me if it work:sudo halt... or ...sudo rebootIf the commands (sudo halt / sudo reboot) work, this mean there is probably a bug in GNOME.Thanks!

_______________________________________________
No banners. No pop-ups. No kidding.
Make My Way your home on the Web - http://www.myway.com

Revision history for this message
Gary Ratliff Sr. (eronstuc) said :
#4

In a series of experiments I have reached the real source of the problem. Now the alteration of the /etc/X11/xorg.conf to change the driver from "fglrx" back to the "ati" which the system identified on the install restored the ability to reboot and restart in the amd64 part of the system.

However, the i386 system was left alone. So by following this same process itwas possible to restart and reboot the i386 ubuntu system. However, I desired the 1280x1024 resolution as that is recommended. The next portion of the experiments was to learn that it was possible to reboot and restart the system from
640x480 screen resolution. Thus to not have the screen go blank and get the system to reboot one would just change the screen resolution preference from the desired 1280x1024 to 640x480.

Once I had loaded the monitor manual which was as a pdf file on the install cd I learned tha the preferred resolution was 1280x1024 with a freq of 60Hz. While my system was set for 1280x1024 with a freq of 75Hz. Now this was altered to
chage the frequence from 75 to 60 and then see if the system would reboot and shutdown. This alteration seemed to function.

So to determine if this is the real solution. The completion of the experiment will be to restart and get to the amd64 side of the system and edit the /etx/X11/xorg.conf file to again allow "fglrx" and set the freq from 75 to 60 and see if the system then becomes completely functional.

Revision history for this message
Gary Ratliff Sr. (eronstuc) said :
#5

The results of the experiment to restore the "fglrx" driver to the amd64 distro yield the result that it is the change to 640x480 resolution prior to restart or reboot which allows this to function properly. This is true regardless if I am using the i386 or the amd64 distro.

The previous result of setting the Hz on 1280x1024 mode from 75 to 60 Hz seems to be in error. To work and reset or restart. Actually to select any of the options from the icon with the white circle on the red backround seems to require 640x480
resolution. There, are several combinations which have not been tried. However, I wished to find a method which works and this does.

So I can use the system in any of the resolutions I find convienient with the fglrx driver installedand functioning as long as I do not try toi restart/reboot without first setting 640x480 resolution.

Again the actual hardware this is on is: an HP Media Center PC a1253w with an HP vs17e monitor.

VGA Controller ATI RS480 (Radeon Xpress 200G Series).

Partitions:

hda1 Windows XP Media Center Edition
hda2 HP Recovery PArtition for Windows
hda3 Extended partition
hda4 swap
hda6 i386 Ubuntu Dapper
hda7 amd64 Ubuntu Dapper

Revision history for this message
devil3000 (alexisright1000) said :
#6

Okay hello every one, i am new to this complicated system, i am a windows user i have been reading over 50 threads of problems and yet i am still stuck with like 20 of them
1. When installing ubuntu 7.04 on my dell xps 210 2.66 dual core ati x1300 1gb ram very fast computer.

i run the installation goes thru very well like a drink of water, but when i try to install my graphic card so i can change the resolution i get no where . i have tried the following steps (http://lhansen.blogspot.com/2006/10/3d-desktop-beryl-and-xgl-on-ubuntu-edgy.html)
and completed them 6 times meaning 6 additional steps of formatting my drive to remove ubuntu so i can re-install and try these steps again, why because every time i complete these steps ubuntu will lose my lcd display when entering the login screen and i am left with a blank screen , from what i understand it has to do with my ati x1300 which i have tried to configure several times

ok about now your probably wondering how stupid i am i agree because this ubuntu is so dam hard to understand comparing to xp , and the name its self is hard to read ( u.b.u.n.t.u ) who made that name any ways its sounds like a error in my head .

The only reason i would ever consider using ubuntu is because it looks hot. But dam how many of us had to go thru problems and problems
:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(:(

Now i am still looking to make the best of it if any one can help me or forward me to information easy to understand i would greatly appreciated my email address is <email address hidden>
Now I am a new Yorker so time is every thing

Can you help with this problem?

Provide an answer of your own, or ask Gary Ratliff Sr. for more information if necessary.

To post a message you must log in.