 Show Posts
|
|
Pages: 1 [2]
|
|
16
|
Assistance / Hardware / [solved]How to open port 631 for Linux-to-Linux printing?
|
on: July 10, 2008, 01:49:53 AM
|
|
I want to print from a Linux client to a Linux server. The latter has Pardus 2008. I used the Remote CUPS Server for the protocol and entered the IP address of the Pardus system and port 631. If the server runs Ubuntu, I then see all the pinters available on the Ubuntu server. However, if the server runs Pardus 2008, I get "unable to connect to <IP address> on port 631". Also, when I run nmap on the client I see that port 631 on the server is listed if the server runs Ubuntu, but not when the server runs Pardus 2008. So, the question is, I need port 631 open for CUPS printing to the server, but in Pardus 2008 it is closed by default. How do I open that port? Note that this has nothing to do with the firewall, which was turned off.
|
|
|
|
|
17
|
Assistance / Hardware / Printing between two laptops running Pardus 2008
|
on: July 07, 2008, 23:48:54 PM
|
|
I have said earlier that I had no printer problems with my laptops running Pardus 2008. However, that was from a Pardus system to a printer on a Windows computer. I print wirelessly without problems, using different Windows computers in my office and various printers. However, I have now converted one Windows computer to Pardus 2008 also and suddenly I can no longer print wirelessly! The remote Pardus system recognizes the printer on the other Pardus computer correctly and I am certain that I have set it up right. The Job IPP report says: "unable to connect to CIFS host, will retry in 60 seconds". Amazing is that in Samba Shares both computers see the other one and I can exchange files via their shares. Also, the appropriate services are on. Could it be that the protocol "SMB Shared Printer (Windows)" for printer set-up only works if the computer with the printer is a Windows computer? If so, which other prtocol do I need to use for Pardus-to-Pardus printing?
|
|
|
|
|
18
|
Assistance / Configuring Pardus / Re: XFCE?
|
on: July 07, 2008, 23:32:44 PM
|
you are not wrong here. I think the point "Configuration" in the Wiki is importantly for you.  I followed the Wiki line by line and I now have XFCE working also. It is quite standard, not so slick as the Pardus KDE, but it has some advantages they say, so it's nice to have. william5 |
|
|
|
|
19
|
Assistance / Configuring Pardus / Re: XFCE?
|
on: July 06, 2008, 19:26:37 PM
|
I believe I do not have to do this sudo pisi etc., as I have already installed all the xfce4 packages from the 2008 package manager. I just go to the next line of the wiki. Please advise me if I am wrong here. william5 ====== |
|
|
|
|
20
|
Assistance / Configuring Pardus / [reopened]XFCE?
|
on: July 06, 2008, 16:28:17 PM
|
|
How do I switch from KDE to XFCE (in Pardus 2008)? I have installed all the files of the XFCE category in the package manager, including panel, desktop, etc., but I cannot find how to choose between KDE and XFCE sessions upon start-up. In other distros you can click on Session or hit F10, but I do not see that in Pardus.
william5
=====
|
|
|
|
|
21
|
Assistance / Laptop / Re: Pardus 2008 always hangs 3 min on booting
|
on: July 05, 2008, 20:27:58 PM
|
It looks like the kernel has a problem with your laptop's card reader. Maybe the BIOS allows you to disable it ?
PhiX: You are absolutely right! I checked the boot time by eliminating all my external drives one by one. I have an external hard drive, a CF drive, an SD drive and a flash drive typically connected. When I disengaged the CF drive, the delay in booting was gone and it booted fast. This CF drive is not seen by the system, whether I boot with it or not. This is remarkable as some other distros (Ubuntu, PCLinuxOS) that I have, do see the CF drive. PCLinuxOS does not see the SD drive, on the other hand. I consider this problem solved, as I really do not need the CF drive. Thanks. william5 ====== |
|
|
|
|
22
|
Assistance / Laptop / Re: Pardus 2008 always hangs 3 min on booting
|
on: July 05, 2008, 18:35:04 PM
|
"populating /dev" means creating the device files related to the hardware components of your laptop.
Look in the following log files with Konqueror, you may find some clue (error messages) : /var/log/messages, /var/log/syslog, /var/log/mudur.log. Give us a copy of today's logs.
Here they are: /var/log/messages:
driverbyte=DRIVER_OK,SUGGEST_OK
Jul 5 12:28:09 localhost klogd: sd 7:0:0:0: [sdd] Sense not available.
Jul 5 12:28:09 localhost klogd: sd 7:0:0:0: [sdd] Write Protect is off
Jul 5 12:28:11 localhost klogd: sd 7:0:0:0: [sdd] READ CAPACITY failed
Jul 5 12:28:11 localhost klogd: sd 7:0:0:0: [sdd] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Jul 5 12:28:11 localhost klogd: sd 7:0:0:0: [sdd] Sense not available.
Jul 5 12:28:11 localhost klogd: sd 7:0:0:0: [sdd] Write Protect is off
Jul 5 12:28:11 localhost klogd: sd 7:0:0:0: [sdd] READ CAPACITY failed
Jul 5 12:28:11 localhost klogd: sd 7:0:0:0: [sdd] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Jul 5 12:28:11 localhost klogd: sd 7:0:0:0: [sdd] Sense not available.
Jul 5 12:28:11 localhost klogd: sd 7:0:0:0: [sdd] Write Protect is off
/var/log/syslog:
Jul 5 12:29:41 localhost klogd: sd 7:0:0:0: [sdd] READ CAPACITY failed
Jul 5 12:29:41 localhost klogd: sd 7:0:0:0: [sdd] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Jul 5 12:29:41 localhost klogd: sd 7:0:0:0: [sdd] Sense not available.
Jul 5 12:29:41 localhost klogd: sd 7:0:0:0: [sdd] Write Protect is off
Jul 5 12:29:41 localhost klogd: sd 7:0:0:0: [sdd] Mode Sense: 00 00 00 00
Jul 5 12:29:41 localhost klogd: sd 7:0:0:0: [sdd] Asking for cache data failed
Jul 5 12:29:41 localhost klogd: sd 7:0:0:0: [sdd] Assuming drive cache: write through
Jul 5 12:29:41 localhost klogd: sd 7:0:0:0: [sdd] READ CAPACITY failed
Jul 5 12:29:41 localhost klogd: sd 7:0:0:0: [sdd] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Jul 5 12:29:41 localhost klogd: sd 7:0:0:0: [sdd] Sense not available.
Jul 5 12:29:41 localhost klogd: sd 7:0:0:0: [sdd] Write Protect is off
Jul 5 12:29:41 localhost klogd: sd 7:0:0:0: [sdd] Mode Sense: 00 00 00 00
Jul 5 12:29:41 localhost klogd: sd 7:0:0:0: [sdd] Asking for cache data failed
Jul 5 12:29:41 localhost klogd: sd 7:0:0:0: [sdd] Assuming drive cache: write through
/var/log/mudur.log:
Jul 05 04:13:03 (up 9.44) /sbin/mudur.py sysinit
Jul 05 08:15:54 (up 179.98) /sbin/mudur.py boot
Jul 05 08:15:55 (up 181.00) /sbin/mudur.py default
Jul 05 09:23:28 (up 9.44) /sbin/mudur.py sysinit
Jul 05 13:26:18 (up 179.63) /sbin/mudur.py boot
Jul 05 13:26:19 (up 180.51) /sbin/mudur.py default
Jul 05 10:56:37 (up 5610.92) /sbin/mudur.py reboot
Jul 05 06:57:43 (up 9.44) /sbin/mudur.py sysinit
Jul 05 11:00:33 (up 179.76) /sbin/mudur.py boot
Jul 05 11:00:34 (up 180.61) /sbin/mudur.py default william5 ====== |
|
|
|
|
23
|
Assistance / Laptop / [solved]Pardus 2008 always hangs 3 min on booting
|
on: July 05, 2008, 17:22:12 PM
|
|
Hi,
I run Pardus 2008 on a Fujitsu Lifebook laptop. Everything works great (wireless, printing, sound, video, dual monitors, etc.). It is absolutely a fantastic Linux distro (and I have tried quite a few). The only issue that is annoying is that during boot-up the systems hangs for about 3 min. Alt-F2 shows that it is working on "populating /dev". I does that every time I start the system. I am not sure that I understand what that means. Identifying my hardware? Is there a way to accelerate this process?
william5
======
|
|
|
|
|
24
|
Assistance / Hardware / Re: Pardus 2008 sound-problem
|
on: July 01, 2008, 22:51:11 PM
|
@william5:
Unfortunately Pardus 2008 has alsa-driver 1.0.17.rc2 which is not a stable version yet. Latest stable alsa-driver is version 1.0.16. Pardus 2007.3 and probably all of other recent distros use alsa-driver 1.0.16 namely latest stable version.
I don't know what the *hell* they were thinking while including an unstable driver into production system. I hope they immediately replace alsa-driver with it's stable version soon.
Thank you, highenergy. Maybe that is the problem. On the other hand, I installed Pardus 2008 on two other laptops with different sound cards, and surprisingly, these cards work fine. So the problem is hardware-specific. |
|
|
|
|
25
|
Assistance / Hardware / Re: Pardus 2008 sound-problem
|
on: June 30, 2008, 18:48:02 PM
|
Before new posts please look hereHere is the same problem. Greetings Andreas Andreas, I did that but did not see much that could help me. All I read in the thread is that it seems to be a bug. I wonder if this problem affects all sound cards or only some? william5 |
|
|
|
|
26
|
Assistance / Installing Pardus / Re: Administrator's password not accepted
|
on: June 30, 2008, 16:46:52 PM
|
Have you give during the installation youryself (as the regular user) superusers privileges)? That's why sudo did nothing and su was not even possible in the Konsole (denied)[/b] If not, you can restored it via Tasma > System > Users Managment and check the checkbox " give systemadministrator privileges to this user" Greetings Andreas Thanks, Andreas, that solved the problem for me! william5 ===== |
|
|
|
|
27
|
Assistance / Hardware / Pardus 2008 sound-problem
|
on: June 30, 2008, 02:14:55 AM
|
|
Hi,
I installed Pardus 2008 on a Medion MD96340 laptop. It is my first experience with Pardus. So far, I am impressed, but there is a problem with the sound. My card is an nVidia MCP51 High Def. Audio. It is correctly shown in lspci, but there is no sound in any multimedia program. I have recently tried more than 10 other Lunix distros on this laptop (I am not exaggerating!) and none of them had a problem with this card, so it cannot be a very unusual one. I cannot imagine that Pardus does not have the driver for it.
Any suggestions?
Thanks - william5
|
|
|
|
|
28
|
Assistance / Installing Pardus / [solved]Administrator's password not accepted
|
on: June 30, 2008, 01:46:51 AM
|
|
Hi,
I installed Pardus 2008 on a MEDION MD96340 laptop and got almost everything working fine. The only problem I ran into is my administrator's password. When I install some software in PiSi, the password that I gave during installation is accepted. However, when I need to go into the Administrator mode, e.g., in Tasma for installing some fonts, that same password is not accepted. Further, on the command line, when I do su and then enter the pwd, I get the message "permission denied". When I use sudo, I get "sorry, try again". I know that one should use the user's pwd in that case, but that is not accepted either. I tried to log on as root, but that gave me the message "root logins are not allowed".
Not being able to use root privileges makes a distro pretty useless. Can anybody help?
William5
======
|
|
|
|
|
|
