Welcome, Guest. Please login or register.
April 24, 2014, 11:09:21 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!

  Show Posts
Pages: [1] 2 3 ... 6
1  Assistance / Pardus for beginners / Re: Virtual Desktops...different wallpapers on: December 25, 2011, 02:30:45 AM
When you originally set up your virtual desktops you should see a tiny box on the left hand side of the first screen ...
It's not clear to me which screen you mean by "first screen".
Is this the first screen or one of the screens of Kaptan Huh?

I'm on Pclos at present but the Config screens are similar.

 So in Pclos the path is - Configure your Desktop/Workspace Behaviour//Virtual Desktops. You should find similar Headings in Pardus

I'm pretty sure you won't find it in Kaptan.

2  Assistance / Pardus for beginners / Re: Virtual Desktops...different wallpapers on: December 23, 2011, 05:25:20 AM
How can I set up a different wallpaper for each of the four virtual desktops? At the moment all desktops have the same backdrop.

You've probably had this solved already MusicLover but, if not ---

When you originally set up your virtual desktops you should see a tiny box on the left hand side of the first screen which says Different widgets for all Desktops or words to that effect. Tick that.
3  Assistance / Pardus for beginners / Re: UNSOLVED - Pardus not closing down properly and needing a hard switchoff on: December 07, 2011, 01:46:59 AM
good morning maurice,

sad to see your troubles are so persistent. alas i can't provide you with an solution neither. Embarrassed
one thing i found are updated iso's of 2011, you'll find them here.

p.s. i'm going to try and install the minimal 2011 and build from there.

Thanks owiknowi but I don't want to lose all my present settings by installing another .iso. Especially when there's no guarantee that it would solve the shutdown problem.
4  Assistance / Pardus for beginners / Re: Pardus not closing down properly and needing a hard switchoff on: December 04, 2011, 01:49:28 AM
Thanks Lisa.

As far as I can see I would have to go back to kernel .33 with pae to solve this problem and I can't imagine that happening in future updates, after all it's a retrograde step. However I'll keep trying from time to time - something might turn up.

Many thanks to all posters for the help and suggestions that have been given.

Maurice
5  Assistance / Pardus for beginners / Re: Pardus not closing down properly and needing a hard switchoff on: December 01, 2011, 03:02:07 AM
Good Morning,
Maurice, to link your bug report, go to where the bug report is (launchpad?)  double-click on the URL  which will select all of it, copy, then open new browser window or tab and open Pardus forum,  then past it here in one of your threads, which will hot link it.

I think we are getting somewhere.  Looking at your snippet, that shouldn't be the output if you are running NetworkManager.  I get that output when I totally disable NM which I can get away with since I don't have to use it with dial up. (Note:  I'm assuming after the previous threads where I asked you to try something, that you have reverted back to the default, such as when I asked you to start HAL.  Just to make sure you return these test settings back to their defaults before you try more tests, makes it easier to debug.)

I did a search for acpid not exiting and came back to this Arch thread.  Someone there has the same board as you.  So, read it over and try blacklisting one of the suggested ethernet modules.  I couldn't go to the kernel bug link that was posted, for some odd reason, so I couldn't read it.  Here's the Arch thread
Looking at your manual, you have "lan support intel 824566DC gigabit ethernet controller".  
I think you can test this by going into your computer BIOS and disabling the ethernet controller as tried here
Let's hope.  

I'm afraid all this is getting a bit beyond me Lisa. I may have to mark the thread as Unsolved. You are all doing a superb job but I know it must be frustrating in the extreme trying to get your suggestions and instructions over to someone who is not sufficiently computer literate to apply many of them.

For example - afaik the bug report is at bug.pardus where I filled it out and not on my computer.  .

I checked the threads you mentioned but the only place I can find the word Ethernet in Bios is in the Boot device priority section - no mention of "Ethernet Controller". And I went through Bios twice. The url for Linuxquesions returned a Page not found error.

And yes I do return test settings back to their original ones. Grin

Something new - this page of the thread, for some reason, now stretches far beyond the right edge of my screen so that I have to keep scrolling to be able to read it. Fixing it may be simple but I don't know how

Sorry to be so negative - I'm probably having the male equivalent of a "bad hair day". Grin



 
6  Assistance / Pardus for beginners / Re: Pardus not closing down properly and needing a hard switchoff on: November 30, 2011, 04:42:36 AM
Lisa - I have got this from /var/log/syslog showing the end of one session and start of another. Trouble is I don't know whether that was a failed shutdown or a good one. Huh?

Nov 26 20:56:33 pardus2011 pulseaudio[1221]: pid.c: Daemon already running.
Nov 26 21:00:01 pardus2011 /usr/sbin/cron[1351]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons)
Nov 26 21:00:01 pardus2011 /usr/sbin/cron[1353]: (root) CMD (rm -f /var/spool/cron/lastrun/cron.hourly)
Nov 26 21:15:01 pardus2011 /usr/sbin/cron[1420]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons)
Nov 26 21:23:46 pardus2011 shutdown[1570]: shutting down for system halt
Nov 26 21:23:46 pardus2011 init: Switching to runlevel: 0
Nov 26 21:23:49 pardus2011 kernel: Kernel logging (proc) stopped.
Nov 26 21:23:49 pardus2011 rsyslogd: [origin software="rsyslogd" swVersion="5.7.2" x-pid="607" x-info="http://www.rsyslog.com"] exiting on signal 15.
Nov 27 09:34:02 pardus2011 kernel: imklog 5.7.2, log source = /proc/kmsg started.
Nov 27 09:34:02 pardus2011 rsyslogd: [origin software="rsyslogd" swVersion="5.7.2" x-pid="615" x-info="http://www.rsyslog.com"] start
7  Assistance / Pardus for beginners / Re: Pardus not closing down properly and needing a hard switchoff on: November 30, 2011, 02:36:36 AM
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.
 

Where would I find my bug report link Lisa?

"mpstat"  gave


maurice@pardus2011 ~ $ mpstat
Linux 2.6.37.6 (pardus2011.2)   11/30/2011      _i686_    (4 CPU)
12:02:23 PM  CPU    %usr   %nice    %sys %iowait    %irq   %soft  %steal  %guest   %idle
12:02:23 PM  all    4.27    0.10    2.10    2.08    0.00    0.01    0.00    0.00   91.45


My 4 cores show up OK.

I changed the acpi settings from S2 state to S1 state and altered the power settings to Restart after power cut. Apart from those changes I saw nothing else that might help.

So according to that post in the Intel forum it seems that I should not update my bios. No surprise the poor guy got no replies.

And, for grins, another user with admin privileges also failed to shut down

Back to the grindstone. Grin

Edit - just found your edit. Will try again.
8  Assistance / Pardus for beginners / Re: Pardus not closing down properly and needing a hard switchoff 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?
9  Assistance / Pardus for beginners / Re: Pardus not closing down properly and needing a hard switchoff 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.
10  Assistance / Pardus for beginners / Re: Pardus not closing down properly and needing a hard switchoff on: November 28, 2011, 12:49:20 PM

Many thanks atolboo. My apologies for putting you to extra trouble with bad info.
11  Assistance / Pardus for beginners / Re: Pardus not closing down properly and needing a hard switchoff 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
12  Assistance / Pardus for beginners / Re: Pardus not closing down properly and needing a hard switchoff on: November 28, 2011, 09:08:26 AM
Sorry for that atolboo - a typo. Should have read DG33FB
13  Assistance / Pardus for beginners / Re: Pardus not closing down properly and needing a hard switchoff 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.
14  Assistance / Pardus for beginners / Re: Pardus not closing down properly and needing a hard switchoff 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.
15  Assistance / Pardus for beginners / Re: Pardus not closing down properly and needing a hard switchoff 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
Pages: [1] 2 3 ... 6


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