Welcome, Guest. Please login or register.
April 16, 2014, 09:17:09 AM
Home Help Search Calendar Login Register
Show unread posts since last visit.
News: Let Pardus-Anka become #1: Pardus-Anka Bug ReportPardus-Anka World Google+ | The Pardus wiki  | Visit Pardus-Anka official website  | Register as forum member?  Email the moderator!

+  Pardus Worldforum
|-+  Assistance
| |-+  Pardus for beginners
| | |-+  UNSOLVED - Pardus not closing down properly and needing a hard switchoff
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: 1 ... 6 7 [8] 9 Go Down Print
Author Topic: UNSOLVED - Pardus not closing down properly and needing a hard switchoff  (Read 9972 times)
atolboo
Pardus Guru
****
Posts: 2317



View Profile
« Reply #105 on: November 27, 2011, 11:20:45 AM »

Tried it but the Apply was greyed out so the "pci=nommconf" didn't stick so wouldn't work
That's correct.
Apply the OK button.
After this the main Boot Manager screen should appear again and check in konsole with
Code:
cat /boot/grub/menu.lst
Logged
Maurice
Pardus fellow craft
**
Gender: Male
Posts: 86


View Profile
« Reply #106 on: November 27, 2011, 12:39:07 PM »

Tried it but the Apply was greyed out so the "pci=nommconf" didn't stick so wouldn't work
That's correct.
Apply the OK button.
After this the main Boot Manager screen should appear again and check in konsole with
Code:
cat /boot/grub/menu.lst


Wouldn't stick so I added it directly into /boot/grub/menu.lst. Again to no avail. Sad
Logged

Triple booting - Pardus, PcLinuxos, XP - on Custom built - Intel 06600 cpu quad-core, 4gb ram, Nvidia  8600GT (512mb)gcard, SATA 500gb hard drive, 22" AOC lcd
atolboo
Pardus Guru
****
Posts: 2317



View Profile
« Reply #107 on: November 27, 2011, 13:28:30 PM »

When you are going to report this in Bugzilla also do give the exact (typenumber and link) of the used motherboard.
Logged
Lisa
Pardus Guru
****
Posts: 841



View Profile
« Reply #108 on: November 27, 2011, 15:42:18 PM »

I'm glad though, after all is said and done, that Maurice can still shutdown properly via the comnand line.  I almost thought he was not able to do this, and that had me concerned. 

My machine is huge, too, probably too big in today's eye's and I shut mine down when I don't use it the same as you. 

A bug report is a good idea, othewise you might be left in the cold with kernel changes.  I would guess it is some patch that has been applied to the kernel, that doesn't effect the 97% of us, especially if it is a home-built computer. 

On a side note, I found a much easier way to look over the log files and it can be found in this GUI: System>System Log Viewer, which you enter your administrator/root password to unlock.  The fonts and colours are easier on my eyes and you can easily do a search using the search field.  In system log, it should show the previous days shutdown.  You can look these logs over for any relevant stuff, maybe acpi related, memory related, or cpu, such as, if the quad cores are handled correctly. 
Another idea is to go to the Intel forum and write up a thread about this problem.  There might be another user there that has similar or same hardware using Linux, especially recent kernels. 

Just an experiment: I went to Pardus 2011.2 for 64 bits, devel repo, and with Firefox, installed the kernel 2.6.36.1-147  for 2,Dec. 2010.  I also installed the same kernel header, kernel module headers from that date,  and alsa-module.  I'm booted into it now and it is working fine, from the surface it appears to be, but there are errors in dmesg that is probably why Pardus team is now concentrating on kernel 37.  If I were you, I'd just keep on using the command line and stick with 37 kernel and write a bug report and concentrate on that for now.  I just wanted to let you know that there is another kernel you can try, but I've no idea if it will effect your shutdown problem.  I for one like to experiment.

P.S. Had a look over the DG33FB manual and interesting information there.  It isn't like my bios where you can disable the onboard graphics.  It says:   "when a pci-express x16 graphics card is installed, the Intel GMA graphics controller is disabled".   So simply removing it will boot your system with onboard graphics.  I've never heard of DVMT, either. 
« Last Edit: November 27, 2011, 20:48:59 PM by Lisa » Logged
Maurice
Pardus fellow craft
**
Gender: Male
Posts: 86


View Profile
« Reply #109 on: November 28, 2011, 00:35:26 AM »

When you are going to report this in Bugzilla also do give the exact (typenumber and link) of the used motherboard.

Excuse my ignorance but what is the typenumber and link. I have the make, D33FB - is that what you mean by typenumber? And now would I recognise the link? Thanks.
Logged

Triple booting - Pardus, PcLinuxos, XP - on Custom built - Intel 06600 cpu quad-core, 4gb ram, Nvidia  8600GT (512mb)gcard, SATA 500gb hard drive, 22" AOC lcd
Maurice
Pardus fellow craft
**
Gender: Male
Posts: 86


View Profile
« Reply #110 on: November 28, 2011, 07:29:19 AM »


On a side note, I found a much easier way to look over the log files and it can be found in this GUI: System>System Log Viewer, which you enter your administrator/root password to unlock.  The fonts and colours are easier on my eyes and you can easily do a search using the search field.  In system log, it should show the previous days shutdown.  You can look these logs over for any relevant stuff, maybe acpi related, memory related, or cpu, such as, if the quad cores are handled correctly. 
Another idea is to go to the Intel forum and write up a thread about this problem.  There might be another user there that has similar or same hardware using Linux, especially recent kernels. 


Thanks again Lisa

I found that log viewer but the font size is just too small to read comfortably and there is no way to enlarge it. Pity as it was otherwise very configurable.

I will file a bug report as soon as I have a reply from atolboo.

Just made a post on nixCraft which might help.
Logged

Triple booting - Pardus, PcLinuxos, XP - on Custom built - Intel 06600 cpu quad-core, 4gb ram, Nvidia  8600GT (512mb)gcard, SATA 500gb hard drive, 22" AOC lcd
owiknowi
Guest
« Reply #111 on: November 28, 2011, 07:42:34 AM »

good morning maurice,

- maybe you can adjust displayed font size in system settings /  application appearance / fonts (e.g. set them all to 10).
- or you could right click on a log file and select 'save as...' and save it as logname.txt so you can open it in a text editor.
Logged
atolboo
Pardus Guru
****
Posts: 2317



View Profile
« Reply #112 on: November 28, 2011, 08:56:13 AM »

I have the make, D33FB
Where did you get this D33FB Huh?
Because searching with "D33FB" doesn't bring any decent answer.
Isn't there any printing on the motherboard. Huh?
Logged
Maurice
Pardus fellow craft
**
Gender: Male
Posts: 86


View Profile
« Reply #113 on: November 28, 2011, 09:08:26 AM »

Sorry for that atolboo - a typo. Should have read DG33FB
Logged

Triple booting - Pardus, PcLinuxos, XP - on Custom built - Intel 06600 cpu quad-core, 4gb ram, Nvidia  8600GT (512mb)gcard, SATA 500gb hard drive, 22" AOC lcd
Maurice
Pardus fellow craft
**
Gender: Male
Posts: 86


View Profile
« Reply #114 on: November 28, 2011, 09:21:03 AM »

good morning maurice,

- maybe you can adjust displayed font size in system settings /  application appearance / fonts (e.g. set them all to 10).
- or you could right click on a log file and select 'save as...' and save it as logname.txt so you can open it in a text editor.

Thanks 0wiknowi but changing the font size has no effect on this particular program. However I'd forgotten the saving as a text file method. Many thanks for reminding me
Logged

Triple booting - Pardus, PcLinuxos, XP - on Custom built - Intel 06600 cpu quad-core, 4gb ram, Nvidia  8600GT (512mb)gcard, SATA 500gb hard drive, 22" AOC lcd
atolboo
Pardus Guru
****
Posts: 2317



View Profile
« Reply #115 on: November 28, 2011, 10:26:43 AM »

Should have read DG33FB
The link is http://www.intel.com/p/en_US/support/highlights/dsktpboards/dg33fb/
Logged
Maurice
Pardus fellow craft
**
Gender: Male
Posts: 86


View Profile
« Reply #116 on: November 28, 2011, 12:49:20 PM »


Many thanks atolboo. My apologies for putting you to extra trouble with bad info.
Logged

Triple booting - Pardus, PcLinuxos, XP - on Custom built - Intel 06600 cpu quad-core, 4gb ram, Nvidia  8600GT (512mb)gcard, SATA 500gb hard drive, 22" AOC lcd
Maurice
Pardus fellow craft
**
Gender: Male
Posts: 86


View Profile
« Reply #117 on: November 28, 2011, 23:35:42 PM »

Well, I've finally put in a Bug report. Hope it might solve the problem. But I guess it will be some time very much in the future so I won't mark the thread as SOLVED just yet.
Logged

Triple booting - Pardus, PcLinuxos, XP - on Custom built - Intel 06600 cpu quad-core, 4gb ram, Nvidia  8600GT (512mb)gcard, SATA 500gb hard drive, 22" AOC lcd
Maurice
Pardus fellow craft
**
Gender: Male
Posts: 86


View Profile
« Reply #118 on: November 29, 2011, 09:53:03 AM »

Lisa here is an extract from the system log that you mentioned. It shows the end of a session at 8.33 am and the start of another at 7.02 pm. But it doesn't show 3 sessions I had in between those times.

owned by 'maurice' high priority at nice level -11.
11/29/11 08:33:09 AM   pardus2011   rtkit-daemon[1159]   Supervising 4 threads of 2 processes of 1 users.
11/29/11 08:33:09 AM   pardus2011   rtkit-daemon[1159]   Successfully made thread 1201 of process 1201 (/usr/bin/pulseaudio) owned by 'maurice' high priority at nice level -11.
11/29/11 08:33:09 AM   pardus2011   rtkit-daemon[1159]   Supervising 4 threads of 2 processes of 1 users.
11/29/11 08:33:09 AM   pardus2011   rtkit-daemon[1159]   Successfully made thread 1202 of process 1202 (/usr/bin/pulseaudio) owned by 'maurice' high priority at nice level -11.
11/29/11 08:33:09 AM   pardus2011   rtkit-daemon[1159]   Supervising 4 threads of 2 processes of 1 users.
11/29/11 08:33:09 AM   pardus2011   rtkit-daemon[1159]   Successfully made thread 1203 of process 1203 (/usr/bin/pulseaudio) owned by 'maurice' high priority at nice level -11.
11/29/11 08:33:09 AM   pardus2011   rtkit-daemon[1159]   Supervising 4 threads of 2 processes of 1 users.
11/29/11 07:02:19 PM   pardus2011   kernel   [    0.000000] Kernel command line: root=UUID=5a825bf0-8d11-4797-91af-f4a32cf16ea4 splash quiet blacklist=nouveau
11/29/11 07:02:19 PM   pardus2011   kernel   [    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)


Nothing there for a mere pardus craft fellow but you might see something untoward?
Logged

Triple booting - Pardus, PcLinuxos, XP - on Custom built - Intel 06600 cpu quad-core, 4gb ram, Nvidia  8600GT (512mb)gcard, SATA 500gb hard drive, 22" AOC lcd
Lisa
Pardus Guru
****
Posts: 841



View Profile
« Reply #119 on: November 29, 2011, 23:01:18 PM »

Hi Maurice,
No, it doesn't tell me anything.

Glad to hear you took the time to place a bug report for it, in case any others are having similar problem with similar hardware, it will help them, too.  If you want, you can share the bug report link here and then if you post any of your /var/log files to it (upload them as .txt, which you should do) then we can look at them there, for as you know they can spit out quite a lot of information. 

We also have to take into account your processors.  I was looking at your pcLinuxos forum thread and the output of ACPI, and it just seemed strange that your four cores were showing up twice.  Maybe that's normal.  Thanks to your thread and looking up your problem I am learning new ways to check on hardware, as I installed "lshw" that was recommended in earlier page.  Another good on to install via PiSi is "sysstat".  After you install it, do:
Code:
mpstat -P ALL

Also do the following to show if you have four folders for each core:
Code:
ls /sys/devices/system/cpu/
Mine shows cpu0 as I have only one processor one core.  You should have cpu0 cpu1 cpu2 cpu3.
I got this information from ubuntu forum here

Also, look in your BIOS to check the ACPI settings and the power settings to see if something there can be enabled/disabled, then boot into Pardus and shutdown and see what happens.   

I'm trying to find that singular post at the intel forum where someone had same board as you, updated their BIOS and said they could no longer shutdown in kernels 2.6.34. to 2.6.37.  No one replied to that person. 
Lisa Marie
P.S. For grins, you might create a second user and add them to wheel group which gives them administrative rights.  Go to system settings>user manager>add user>enter name and password, then click on Advanced> and tick "give administrator rights", Apply and reboot into the new user and try shutdown.  Just a suggestion.  You can always delete that user after testing it out. 

Edited to add:  I assumed that the GUI System Log Viewer gave the same exact outputs of the logs under /var/log/, but syslog is not as information loaded as the GUI version.
Here is my output under
/var/log/syslog
 opened with text editor.  Using Ctrl + F (find) for "shutdown" gives me this:
Code:
Oct 29 23:11:51 pard2011 kernel: [  560.765660] [drm] nouveau 0000:01:00.0: nouveau_channel_free: freeing fifo 3
Oct 29 23:11:51 pard2011 kernel: [  560.767690] [drm] nouveau 0000:01:00.0: nouveau_channel_free: freeing fifo 2
Oct 29 23:11:51 pard2011 shutdown[1574]: shutting down for system halt
Oct 29 23:11:52 pard2011 init: Switching to runlevel: 0
Oct 29 23:11:55 pard2011 NetworkManager[741]: <info> caught signal 15, shutting down normally.
Oct 29 23:11:55 pard2011 NetworkManager[741]: <warn> quit request received, terminating...
Oct 29 23:11:55 pard2011 NetworkManager[741]: <info> (eth0): now unmanaged
Oct 29 23:11:55 pard2011 NetworkManager[741]: <info> (eth0): device state change: 2 -> 1 (reason 36)
Oct 29 23:11:55 pard2011 NetworkManager[741]: <info> (eth0): cleaning up...
Oct 29 23:11:55 pard2011 NetworkManager[741]: <info> (eth0): taking down device.
Oct 29 23:11:55 pard2011 NetworkManager[741]: <info> (eth1): now unmanaged
Oct 29 23:11:55 pard2011 NetworkManager[741]: <info> (eth1): device state change: 2 -> 1 (reason 36)
Oct 29 23:11:55 pard2011 NetworkManager[741]: <info> (eth1): cleaning up...
Oct 29 23:11:55 pard2011 NetworkManager[741]: <info> (eth1): taking down device.
Oct 29 23:11:57 pard2011 avahi-daemon[834]: Got SIGTERM, quitting.
Oct 29 23:11:57 pard2011 avahi-daemon[834]: avahi-daemon 0.6.29 exiting.
Oct 29 23:11:57 pard2011 acpid: exiting
Oct 29 23:11:58 pard2011 kernel: [  567.045335] comar[1673]: segfault at 7f54573fa0f0 ip 00007f54573fa0f0 sp 00007fff95701158 error 15
Oct 29 23:11:58 pard2011 kernel: Kernel logging (proc) stopped.
Oct 29 23:11:58 pard2011 rsyslogd: [origin software="rsyslogd" swVersion="5.7.2" x-pid="727" x-info="http://www.rsyslog.com"] exiting on signal 15.
You can see I am using nouveau open source free driver for my nVidia GT8500 card.  I would assume it would say nVidia since you are using the proprietary driver.  Anyway, just wanted to post that since there is some information logged during the shutdown process.  I also normally disable the avahi daemon, but on that date, I had it on.  With dial up, it takes up one more listening socket on my connection which is too valuable for me to spare  Cheesy
« Last Edit: November 30, 2011, 02:36:37 AM by Lisa » Logged
Pages: 1 ... 6 7 [8] 9 Go Up Print 
« previous next »
Jump to:  


Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!