I installed pidgin 2.6.6 on fedora 13 and setup as following:
protocol: yahoo
pager server : scsa.msg.yahoo.com
port: 5050
file transfer server: filetransfer.msg.yahoo.com
file transfer port: 80
[Code].....
1. Are there any USB wireless (802.11) sticks that work with the standard FC13 load? The Rosewill card almost works with the DVD load but breaks with the first updates. After playing with the rt2870 and losing every time, I would just like to get a usb wireless adapter that works.
2. If there is no such animal, is there a PCI wireless card that works without a major Kabuki dance prior to setup?
3. Finally, if I do not want to me in the world of GUIs and want a bare machine to run wireless, is there some place to find how to set up a wireless network with WPA2 using the /etc/init.d/network, instead of NetworkManager.
[Code]....
Code:
$ su -c 'yum install wine'
this forum won't let me put all the text in Transaction Check Error: package openldap-2.4.21-6.fc13.x86_64 (which is newer than openldap-2.4.21-4.fc13.i686) is already installed package nss-softokn-freebl-3.12.4-19.fc13.x86_64 (which is newer than nss-softokn-freebl-3.12.4-17.fc13.i686) is already installed
I am using Ubuntu 9.04. After doing sudo apt-get update When I try to insatll pidgin via terminal it shows: XXX@XXX-desktop:~$ sudo apt-get install pidgin Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming.
The following information may help to resolve the situation: The following packages have unmet dependencies: pidgin: Depends: libpurple0 (>= 1:2.6.0) but it is not going to be installed Depends: perl (>= 5.10.0-19ubuntu1.1) but 5.10.0-19ubuntu1 is to be installed E: Broken packages
There is something strange going on with Pidgin in Debian 6. I have just installed the system, then Pidgin, then configured my MSN accounts and chatted; but after rebooting, it no longer works. It just hangs while trying to connect - this is what I see from strace:
[Code].....
- a largish number of times. My very rough and ready thoughts about this so far are that it is probably not Pidgin that has an error, since 1) It worked initially, and 2) I am pretty sure the developers would have know about it very quickly if this was a general problem in Pidgin. On the other hand, my networking seems otherwise to be fine - s what is going on here?
This is my first post and I'm just starting to use Ubuntu again. I currently have 11.04 installed. So my friend and I are trying to voice chat using Google Talk. He is using Windows XP and is going through his web browser. If I use Empathy or Pidgin I can call him and he can hear me speak but I can't hear him. When he calls me, I get no notification from Pidgin, and from Empathy it rings and when I pick up I get nothing. It works perfectly fine for both of us if I also go through my browser. Hopefully someone can help with this or perhaps have another voice chat client we could use? For example, MSN is suppose to work with Empathy. If so, would we have fewer problems using that?
On a side note I always wanted to know when you guys give terminal commands on here do you have them memorized or do you copy and paste?! I'm such a noob when it comes to Linux and can't count the times Ubuntu has made me feel so dumb!
I have a mivvy l310 netbook. Before I had FC12 on it and I couldn't upgrade (not enough space on /boot, tried all commands and it didn't worked) to FC13. So I said I would do a fresh install for FC13. I used live CD FC 13 iso to make the usb drive (16gb) bootable.It boots, all goes ok, untill the installation is in progress of copying files to my HDD (at this point my HDD is empty, since it was formated). At about half of the progress bar of copying the installation files to HDD it stops with: ""There was an error installing the live image to your hard drive. This could be due to bad media. Please verify your installation media."" I can't go further and install it. I tried making the usb drive on FC13 (finished successfully, on another laptop with liveusb creator) and also on SUSE and it behaves the same.
I also tried second method (described in a thread around here, it worked for me in the past for FC11), by just making the usb drive bootable, using commands in the terminal (here my FC13 kernel, on another laptop crashes, for some commands) and when I try to install I get only: "missing operating system, sleeping forever". For this method, it does not boot at all, so I guess the usb drive is not properly setup. I don't know what else to try. I tried normal dvd iso, live cd, tried making the usb using commands, using live cd, with commands on suse, on FC13 etc...
LE: I found in messages log that I have: zlib_inflate error fc13
LE LE: what's more weird is that I downloaded the same live image of FC13 and burned it on a CD and managed to install it on my other laptop and it worked.
Later update: I tried now with the DVD iso for FC13 and now I get: operating system not found
I just installed FC13 on my laptop. I cannot upgrade from FF 3.6.7 to 3.6.8.
View 3 Replies View RelatedFedora (2.6.34.6-47.fc13.x86_64) I installed that update, during the installation process it said that it had to remove three packages, one of them was kmod nvidia for the old kernel (Fedora (2.6.33.8-149.fc13.x86_64))After the update finished installing the new kernel, I restarted the system and Nvidia did not load. (I assume because Update manager removed the old nvidia? But I also assumed that a new version would be installed automatically?)I received the following Boot messages:
Code:
Entering non-interactive startup
Starting monitoring for VG vg_user1: 3 logical volume(s) in volume group "vg_user1" monitored
[code]....
I'm confused, if Update Manager removed kmod nvidia, then why does yum say it is installed? And why doesn't the new kernel update work with that version? Or should I install a driver version for that particular kernel? I've read while searching that I need to install a kmod-nvidia for that particual kernel version and that I should login to my previous kernel until that happens, is that the problem I'm having?
Why don't rpmfusion and fedoraproject release the kmod-nvidia and kernel updates at the same time to avoid problems such as this? Does anyone know how long does it usually take for rpmfusion to release the new kmod-nvidia driver for the latest kernel?
Took an FC12 system to FC13 via 'preupgrade'There was a REALLY old version of gimp-print-cups in RPM, and the installer announced "a fatal error occurred". However, everything else seemed to download properly and I allowed the upgrader to reboot the system.
a) grub boots the kernel, then the kernel can't find root and panics. It does this because it can't root file system with root=UUID= kernel option. If I manually tweek the grub line to use root=/dev/sdx, kernel finds its root and boots up to the next problem.
b) GUI environment not launched. Init scripts die on "error loading modules.dep". Sure enough - one is not there. Ran "depmod" to generate it ,and rebooted. System reboots into GUI, where I login to find the next problem.
c) Evolution won't start. Reason turns out the evolution-data-server from FC12 is still present. Did a check on just how many other FC12 RPM's are present: 1100. Yeah - over 1000. About 850 of the FC12 RPM's also had FC13 replacements installed. Did an "rpm -e" on these. Also had to do some remove action on mkinitrd, nash, plymouth-scripts-0.8.0, and parted-1.9.0 as there are replacements for these utilities under different package names. That cleaned up the system some, to present me with the next problem.
d) yum package repository still linked into FC12. Removed fedora-release-12-2.noarch and then I could "yum install" evolution and a few other packages properly.
I've done one other FC12->FC13 upgrade today, and that went flawlessly. So, I think in general the upgrade works fine. It just looks like if preupgrade finds anything amiss, it doesn't take care of a lot of things and generally leaves you with an unbootable mess to clean up.
I had FC11 installed on a Toshiba Tecra A4 and when I upgraded via dvd, the system "hangs" after finishing the last gray bar(the bar flickers a lot at the last), keyboard ctrl-alt-del will reboot. I had used noapic and acpi=off before, but does not help now. Intel graphics, at first a flash about address collision.
View 1 Replies View RelatedI have installed my Fedora on a LVM2 group and alocated a total of 10 GB. Which of course is abusrdly and ridiculously low space. As a matter of fact I did even more stupid thing - I allocated 4 (four) gigabytes for /swap !
I am complete novice in Linux and fedora, but I want to extend my /root lvm drive with at least 20 gb.
I burned parted magic on a CD and tried to manage the LVM2 grop, but it said LVM2 was not supported in parted magic. And so I tried the Fedora Partition Manager and got lost in what and how. I tried reducing the /swap space and increasing the / space, but failed - I could only select zero Mbytes for swap space, and had the only option of decreasing space for /, which is really not what I want to do.
What I want to do is extend the space for the whole LVM2 Logical Group , which is now 10 GB total for / and /swap. Or at least I'd like to reduce my /swap size and increase my / size.
I am unable to login to kde after upgrade to fc14 from fc13 as user , the splash screen works for seconds and returns back to login screen, but I am able to do as root
I also managed to login to KDE (failsafe session)
and also I am able to login as normal user to gnome desktop
Now, all of a sudden, after I restarted after a system update, My dell desktop inspiron hangs on boot. The kernel is: 2.6.34.8-68.fc13.i686. Not only that, but the system won't boot for any of the remaining previous kernels.
View 6 Replies View RelatedI managed to successfully upgrade FC11 to FC13. While doing the post upgrade steps, I made a HUGE mistake. After identifying the unsupported packages, I used "yum remove package1 package2" command to remove the obsoleted ones without realizing the yum was also removing many FC13 packages! Here are the cmd sequence used:
# package-cleanup --orphans
...
# yum remove compat-db45-4.5.20-5.fc10.i386 flash-plugin-10.0.32.18-release.i386 gnome-spell-1.0.8-5.fc9.i386 ifd-egate-0.05-21.i586
[code]....
I simply typed Yes and left unattended for a few minutes after yum prompted there were # of packages to be removed as I blindly believed it would do the job. After returning to the computer, I found many installed icons were disappearing, the wireless suddenly turned off etc. I killed the yum process right away but it was too late.
-Is there anything I could do to undo the yum remove process?
-How to safely remove supported packages?
I'm running Ubuntu Lucid formatted ext3. It boots with Grub (old Grub) in sdb6 (hd1,5) It mounts at /, and its partition, sdb6. is flagged boot.
I created a new partition for Fedora 13, 64bit. I installed Fedora in sdb8 (hd1,7), formatted ext4, and created a separate /home in sdb7, formatted ext3, so I might share it with Ubuntu, in sdb6.
Fedora installed with Grub2. It booted fine, and after adjusting references in fstab Ubuntu booted OK too, but rather roughly.
That is when I shifted the boot flag to the Ubuntu partition. So now the original Ubuntu Grub is handling boot once again. Ubuntu boots as before, but I can't get Ubuntu's Grub to boot Fedora. An earlier post suggested this code, which generated error 13, Invalid or inappropriate executable:
Code:
I tried the following code, pasted from the Fedora Grub, but it doesn't work either:
Code:
I've got alternative lines invoking the kernel, because someone had suggested omitting the direct reference to root= ....
Either way I get error 2 - Bad File or directory.
I suspect the problem may be that I'm booting Grub in an ext3 partition and trying to invoke Fedora in an ext4 partition. Does anyone know if that is the likely cause of my problem? If so I can reinstall Fedora formatted ext3.
Alternatively, can I create a Fedora /boot partition, and move/reinstall Grub there? Either way -- should I use old Grub, so both Grubs are the same?
Should I have assigned mount points to sdb8 (Fedora) and sdb7 (home)? Currently I'm not using sdb7 at all.
I'll attach a screenshot from GParted of my partitions.
Having just installed fc13 and downloaded the KDE package I attempted to log out as user and back in as root, but I keep getting a message about the wrong password. This is odd as the same password works in terminal if I try to become a SuperUser. I have tried turning off SELinux to no avail. I cannot log in from cold as root,only as user.
View 1 Replies View RelatedI am running Fedora 13 in VMWare. I tried doing a software update and I get this error message when tring to install the updated kernel:
Test Transaction Errors: installing package kernel-PAE-2.6.33.6-147.fc13.i686 needs 6MB on the /boot filesystem
how to increase the memory space required for installation.
I have just upgraded my FC12 installation to FC13. The initial boot failed (just blank screen). Second time I received 'selinux targeted policy relabel is required'. I let that run, but still the boot did not suceed.
I then went in to verbose boot and saw that the boot would hang at libvirtd. So I disabled libvirtd for anything above run level 1. Next boot failed at atd, disabled atd. Next boot failed at 'monthly Smolt checkin'.
At that point and booted in to single user mode and dissabled SELinux, thinking that was the cause of all the problems. That did not help.
The update process has also removed my previous kernels, so I can't test a different kernel
I am running FC13 on a fairly old PC (PIII 500MHz, 384MB RAM, 10GB SCSI disk). It works fine using kernel 2.6.33.5-112.fc13.i686.PAE. After a series of recent updates the system now also has a new kernel 2.6.34.7-56.fc13.i686.PAE.
/boot/conf/grub.conf contains:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
code....
When I try and boot to the newer kernel I get an error like:
Kernel panic - not syncing VFS Unable to mount root fs on unknown block(0,0)
I read on the forum about a similar problem where the fix was to insert the line
initrd /initramfs-2.6.34.7-56.fc13.i686.PAE.img
but this file doesn't exist and so the boot then hangs with no messages, so I took this line out again. Here is contents of /boot:
$ ls -l
total 21148
-rw-r--r--. 1 root root 111391 May 27 04:06 config-2.6.33.5-112.fc13.i686.PAE
-rw-r--r--. 1 root root 112291 Sep 15 04:32 config-2.6.34.7-56.fc13.i686.PAE
drwxr-xr-x. 3 root root 1024 Jan 23 2010 efi
code....
As you may deduce from the above I haven't used the system much so the auto-update hasn't run for several months.
Any help on running / installing the newer kernel appreciated. Note that I am trying to install a wireless LAN card and am following instructions here: url
I got as far as
cd /lib/modules/`uname -r`
ls -l
which gave:
[root@localhost 2.6.33.5-112.fc13.i686.PAE]# ls -l
total 3300
lrwxrwxrwx. 1 root root 51 Jun 3 00:52 build -> ../../../usr/src/kernels/2.6.33.5-112.fc13.i686.PAE
drwxr-xr-x. 2 root root 4096 May 27 04:08 extra
drwxr-xr-x. 11 root root 4096 Jun 3 00:52 kernel
code.....
so I have the src files for the newer kernel not the one I am running. I thought it best to stop and think (and ask for help!) rather than break a working machine (but with no wireless LAN!)
Last nights upgrade of java-1.6.0-openjdk-1.6.0.0-43.1.8.2.fc13.i686 and java-1.6.0-openjdk-plugin-1.6.0.0-43.1.8.2.fc13.i686 prevent the loading of Ameritrades Command Center.Downgrading to version 1.6.0.0-37 fixes the problem. I'll post the bugzilla number as soon as I get the chance to file it.
View 3 Replies View RelatedI have a Kubuntu 10.10 install on which I can't update my packages due to some fail conflict between pidgin and pidgin-facebookchat. I can't even remove the stuff via apt-get due to this conflict...
sudo apt-get remove pidgin
Code:
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these:
[Code]...
I just installed FC13.It wiped out everything from the previous (FC11) installation. I cannot connect to the existing windows network that was working before. I don't see SAMBA so I downloaded and installed the RPM. I still don't see it on any of the menus. I am trying to connect to the existing Windows network
View 6 Replies View RelatedCan I migrate from fc12 to fc13 or do I have to do a full re-install? If I can migrate, can you point me to the instructions/working paper/etc.?
View 6 Replies View RelatedI have been running FC13 for some time now without any problems on my HP dc5800 Microtower. Recently I ran a software update, and when I rebooted the machine I got a blank screen with only a blinking underscore in the upper-left corner. Rebooted several times to no avail. I thought perhaps I had made a mistake, so I just reinstalled. I have tried reinstalling several times now with both 32-bit and 64-bit FC13, each time with the same result: everything works fine up until I install software updates; then after the next reboot I get a blank screen with the blinking underscore. I see the POST screen, and then it just goes blank. It doesn't seem to respond to any keyboard/mouse input; I eventually have to hold down the power button to make it power off.
View 5 Replies View RelatedI am trying to setup VNC server on FC13 box. i am not able to do proper configuration. Can anone point to me a good link which is working. I did many configurations. but no success yet. I have an issue especially with xstartup script. I am running VNC server on Linux and RealVNC viewer on Win Vista OS.When i try to connect to VNC server from RealVNC viewer from Win Vista. It gives error like "unable to connect to host: Connection timed out (10060)"
View 4 Replies View RelatedFollowing this from the wiki: It states Testing shows that upgrading within X will cause X to hang when installing bitmap-fonts-compat, but it can be done anyway by making sure that bitmap-fonts-compat is the last package to update. How do you ensure that its the last package to update?
First install the new fedora 13 gpg key. You may wish to verify this package against [URL] and the fedora ssl certificate.
rpm --import [URL]
Upgrade all packages with
yum update yum
yum clean all
yum --releasever=13 distro-sync
- Testing shows that upgrading within X will cause X to hang when installing bitmap-fonts-compat, but it can be done anyway by making sure that bitmap-fonts-compat is the last package to update ... YMMV.
- Intel video no longer works without Kernel Mode Setting (KMS). You must remove 'nomodeset' from your /etc/grub.conf kernel command line, if present.
- nVidia video no longer works without kernel mode Setting (KMS). You must remove 'nomodeset' from your /etc/grub.conf kernel command line, if present.
- It may be necessary to run "db_recover -h /var/lib/ldap/ ; chown ldap:ldap /var/lib/ldap/*" once in order for slapd to start.
I have FC 13 with both KDE and Gnome loaded. Over the last couple of years of using linux. I've found Gnome better suitable for my needs than KDE and now I'm stuck!
View 6 Replies View RelatedI did a fresh FC13 install on a computer and after trying to install the nvidia drivers the machine hangs on starting atd when it boots.Initially, I tried to install the nvidia drivers with yum but it didn't work. The nvidia module was not loading and although I blakclisted the nouveua driver the machine was still picking it up. Anyway after spending a lot of time trying to find a solution online, I decided to download the drivers from nvidia and install it myself.So I did that, run sh <nvidia-package>.run and the installation was completed without any complaints. Since then the machine hangs when I booted it up. Also I don't see any errors in var/log/messages or in /Xorg.0.logHere is my grub.conf:
Code: default=0
timeout=0
splashimage=(hd0,0)/grub/splash.xpm.gz
[code]....
got my upgraded fedora 14 partition to boot, but I find out that I had to reinstall my nvidia driver, no big deal. seemed to go ok, but now when I go applications->system tools -> terminal I get the "starting terminal" thing on the bar, and then nothing. Can't figure out whats up.
View 4 Replies View Related