[Solved]voip in arch linux

Hi
I just joined the arch bandwagon 2 weeks ago form ubuntu.
I like to know what voip software do u use in arch linux because skype is not officially supported ?
Last edited by neoDEH (2014-10-02 18:18:00)

https://wiki.archlinux.org/index.php/Skype

Similar Messages

[SOLVED] New to Arch Linux, Need help in Installation.

Hi,
I am Ubuntu user for sometime, but I want to migrate to Arch Linux. I need some help. Please note that I am not Linux Expert but I have been using Ubuntu and OpenSUSE for quite sometime now. The reason for deciding to migrate to Arch Linux is with I need speed.
My laptop configuration is
Dell Vostro 1015 - Intel Dual Core 1.8 GHz with 2 GB RAM.
I was using Ubuntu 64 bit version.
Here in Arch Linux, I find there are 3 options to download i686 CPU, x86-64 CPU, Dual Architecture
Now which one should I download among x86-64 and Dual Architecture?
Thanks.
Last edited by sanjaydelhi (2011-11-16 15:11:14)

Thank you all for welcoming me at Arch Linux!
I was bit worried at the beginning because I tried Fedora before but it has one bug because of which it does not get installed on my laptop.
http://forums.fedoraforum.org/showthread.php?t=255943
I was bit disappointed being not able to use Fedora (both 14 and 15 ) because of this bug.
The reason I got worried because I am new to Arch, as I mentioned I am not Linux expert and Arch is not for beginners( though I consider myself intermediate in Linux but certainly not expert). So I thought if I do not get community support probably I will not be able to use Arch Linux. The reason I got interest in Arch Linux is http://lifehacker.com/5680453/build-a-k … he-process this article. I am not thinking of upgrading my laptop for speed anytime sooner. So I thought of trying Arch Linux.
The reason to post the topic was in most of Linux distros we see two options (x86, AMD_64). I found 3 options at Arch. I just wanted to make sure I am downloading right download.
So I hope I clarified it.
ANOKNUSA wrote:However, just for future reference: When engaging in any discussion with anyone anywhere on the internet at any time, it's often best to just leave experience and credentials out of the discussion. I don't mean any offense myself, but claiming to be "in software development" while appearing unfamiliar with hardware architecture comes of as a bit odd.
You are right. I should not have have brought experience and credentials in discussion. I used to follow hardware architectures but now I have so many other things to follow, so I can not keep up with hardware architectures. I still do not know exact architecture of i3,i5 or i7 processor or any of AMD processors. Thats how it is.
I thank you all for support.
Looking forward to trying Arch Linux.
Thanks

[SOLVED] Triple Boot Arch Linux, Windows 7 + Windows 8 on second disk

Hi,
I have installed Arch Linux and Windows 7 on my primary disk. Everything's perfect. I want to install Windows 8 on my second disk. My only problem is how do I make grub2 recognize Windows 8 on the second disk and add it to the grub file, so i can boot Arch, Windows 7 and Windows 8.
Thank you for your time,
Deadvi
Last edited by Deadvi (2012-08-29 21:24:00)

It overwrote the MBR from the first disk, even though you installed Windows 8 on the second disk? That's odd... Make sure that the boot order in the BIOS is right (that the drive with Arch Linux is the first to boot) and from a 2012 Arch Linux install media run:
# mount /dev/sdxY /mnt #Your root partition.
# mount /dev/sdxZ /mnt/boot #Your boot partition (if you have one).
# arch-chroot /mnt
And continue with the instructions from here. If you don't have a 2012 Arch Linux install media (or you only have some other "live" Linux distribution), use the old chroot way.

(SOLVED) Dualboot Windows + Arch Linux (Windows boot partition)

Hi,
I have 4 partitions.
sda1: Windows boot partition (ntfs) - This has always been there
sda2: Windows Installation
sda3: HP_Tools - I need to keep this for warranty
sda4: Arch Installation
I want to use GRUB to have a dualboot option at startup. Do I need to install GRUB to the boot partition which is NTFS, this should be ext3 according to the tutorial.
Or can I just install grub on the Arch installation in the /boot folder?
Thanks already!
Last edited by AlexCogn (2012-10-02 15:02:10)

Scimmia wrote:
AlexCogn wrote:When I do that Windows just starts.
Then you didn't install grub to the MBR. Don't forget, installing the package isn't enough, you actually have to install grub to sda as a separate step.
So
# grub-install --target=i386-pc --recheck /dev/sda
# cp /usr/share/locale/en\@quot/LC_MESSAGES/grub.mo /boot/grub/locale/en.mo
and then
# grub-mkconfig -o /boot/grub/grub.cfg
I forgot the installation ... I'm trying it in half an hour, thanks already for you help guys!

[SOLVED]CR-48/Arch Linux/Installing Gnome or e17

I'm all the way up to installing a Desktop Environment/Windows Manager. I have tried both Gnome and e17. Same issue occurs with both.
I get hundreds of lines, "error: failed retrieving file..."
Then:
warning: failed to retrieve some files from extra
error: failed to commit transaction (download library error)
Errors occurred, no packages were upgraded.
Where to next?
Last edited by killingthemonkey (2012-03-28 20:32:13)

Never mind. A quick run of netcfg to connect to the wifi again resolved it.

[solved] Arch linux access point with multiple interfaces for the NAT

Hi, I have a router running Arch linux. It is connected via LAN (let's call it eth0) to the internet. It has a second LAN interface, eth1, and a wireless interface in master mode, wlan0.
Now, Everything works perfectly except providing network connectivity on eth1 and wlan0 simultaneously. I followed the guide in the "Internet share" wiki article and use dnsmasq/hostapd for the AP. It appears as if all traffic from the router is sent to the wlan0 interface, even if it came in through eth1 (for example, dhcp requests). I cannot really find information how to solve this. The words "bonding" and "iptables" are floating around, but there is not really an easy to understand tutorial for this.
What do I need to do to use both the eth1 and wlan0 interface (for different clients!) on my router?
Best regards, and thank you in advance
Jan Oliver
/e: This seems to be my problem: http://www.novell.com/support/kb/doc.php?id=7000318 How do I solve this using the usual iptables? (The way described in the article doesn't work: "RTNETLINK answers: No such process" errors.)
Last edited by janoliver (2013-09-25 22:24:53)

Or you could bridge eth1 and wlan0, and make dnsmasq bind/listen on that bridge...

[SOLVED] Ndiswrapper, NetworkManager 0.7 and 64-bit Arch Linux

Hi there!
I am having problems configuring my wireless card. I know I have to use Ndiswrapper, and this is what I have tried to do; however, it didn't go quite well.
This is rather odd because it worked perfectly in the 32-bit version of Arch Linux, but now it doesn't work.
So, here comes the code.
valandil ~ $ lspci | grep Network
0b:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 01)
I really use ndiswrapper and have already installed what I think is the proper driver (it seems that the list the official ndiswrapper site had has somehow disappeared.
sudo ndiswrapper -l
Password:
bcmwl5 : driver installed
device (14E4:4311) present (alternate driver: ssb)
Here's iwconfig:
valandil ~ $ iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11bg ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=0 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
I use NetworkManager 0.7 and have configured properly:
rc.conf:
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.utf8"
HARDWARECLOCK="localtime"
USEDIRECTISA="no"
TIMEZONE="America/Vancouver"
KEYMAP="cf"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(fuse ndiswrapper fglrx !b44 !mii bcm43xx !snd_pcsp snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore !pcspkr)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="cipher"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
INTERFACES=(lo !eth0 !wlan0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.1.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(@stbd httpd !network syslog-ng netfs crond alsa hal dhcdbd networkmanager fam gdm)
hosts file :
# /etc/hosts: static lookup table for host names
#<ip-address> <hostname.domain.org> <hostname>
127.0.0.1 localhost.localdomain localhost cipher
# End of file
/etc/NetworkManager/nm-system-settings.conf:
GNU nano 2.0.9 File: /etc/NetworkManager/nm-system-settings.conf
[main]
plugins=keyfile
[keyfile]
hostname=cipher
I hope you can solve this problem; wireless is really crucial.
Thanks for any help,
Last edited by valandil (2012-05-02 18:27:09)

Alleluia!!!
I think I will write a new rule for myself to follow :
Thou shalt never use ndiswrapper again.
Thanks a lot, wonder, and thanks to you too, Xyne.
FYI, I tried to use something else than ndiswrapper before, but it didn't yield satisfying results. Anyway, thanks.

[SOLVED] Arch Linux Duke (2007) Fails to Boot

Folks, I have a unique and challenging problem that has exhausted my Arch Linux skills, and so I am now turning to you.
I have a vintage Pentium Pro 200 system (that’s 200 MHz folks! – 200 MHz 686 architecture – the original 686!), two CPUs, running a dual boot between Windows NT 4.0 and Arch Linux Duke (2007). It has 512 MB of RAM and a 120 GB hard drive, partitioned up between Windows NT and Linux. I built this system new in 2007, hence the dated version of Arch. It has run like a charm all these years, granted not getting that much use. After about a year of no use at all, I fired the system up last week to help with a little research for a blog post I was writing on networking Windows NT 4.0 and Mac OS 8.6. Windows NT 4.0 fired right up with no issue, and after I was done testing what needed to be tested I tried to boot over to Arch.
After a year of disuse, Arch unexpectedly and stubbornly refused to boot. The boot process started up just fine, but towards the end, it declared that it could not mount the root file system on the root device and took a kernel panic and stopped. My Arch skills have gotten a bit rusty in the last few years, but I dusted them off and went to work. My guess was a file system or superblock error. Arch wouldn’t boot, but I dragged out my trusty RIPLinux 2.9 Rescue Live CD and fired it up. It came right up and ran, and I was able to mount the Arch partition and view all the files… everything seemed to be there; it just wouldn’t boot. Windows NT 4.0 AND RIPLinux both boot and run on the machine, so the hardware is fine as well.
A little information on the disk layout. Windows NT 4.0 is in the first partition on the hard drive. The extended partition has a second Windows NT 4.0 partition (sort of a /home partition for Windows NT 4.0), followed by the main Arch partition (the one I am trying to boot), followed by a swap partition and then the largest partition, which I use to share data between Arch and Windows NT 4.0 (I have loaded an ext2/3 driver into Windows NT 4.0 and it happily accesses the Linux partitions on the box).
RIPLinux’s e2fsck did find some issues with the Arch partition and I had it repair them all. I checked again afterwards that all the files were still there, and they were. With the partition now known to be clean, and the superblock repaired from one of the backups, all should have been well. However, Arch still wouldn’t (and still won’t) boot.
RIPLinux has a kind of a chain loader function, so I had it attempt to start up Arch for me. However, this was flummoxed by the fact that Arch addresses all my hard drive partitions as /dev/sdax and RIPLinux addresses them as /dev/hdax. Hence, without a common language, it was hard to get the one to start the other. Still, using this function, I have been able to get a crippled version of Arch running on the machine again. No modules had been loaded, and so it couldn’t do almost anything, but there it was (and is), Arch Linux Duke, at the CLI level. From there, I can see all the files, I can move freely in and out of my user account and the root account, but I can’t make the thing actually boot properly.
If you have read this far, you are a trooper. Summarizing what I know, the hardware is good, the file system is clean, the superblock is good, I can mount it cleanly from a live CD and I can chain load a crippled version of Arch. Here is the boot process blow-by-blow. When I try to do a normal boot, the Windows NT 4.0 loader passes control to the Lilo boot sector I have placed on hda1 (sda1 in Duke’s parlance). Lilo takes over, present a menu and when I select Duke, takes off. Arch Linux Duke starts to boot. It gets a good long way along, all the way along to:
:: Loading udev events [Pass]
:: Mount root Read-only
:: Checking file systems
This is where it stops.
The next thing I see is:
/dev/sda6
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else) then the superblock is corrupt and you might try running e2fsck with an alternate superblock:
E2fsck –b 8193 <device>
I then get a sort of character based splash screen that says
**********FILE SYSTEM CHECK FAILED ****************************
* Please repair manually and reboot. Note that the root file system
* is currently mounted read-only. To remount it read-write, type:
* mount –n –o remount,rw /. When you exit the maintenance
* shell, the system will reboot automatically
Give root password for maintenance
At this point, I give the root password and enter the maintenance shell as root. I typed in “mount” and the first entry I got back is
/dev/sda6 on / type ext3 (rw)
This is exactly the root partition that the start up complains about. It is clearly there. I can see it, I can walk around it… it is clearly there. Why won’t it boot? Despite the message, the superblock is fine – it passes every test e2fsck can throw at it.
At this point, I did a “e2fsck /dev/hda6 (which is how RIPLinux would have passed it into Arch” and it says it is “clean”. I suspect that the Superblock message is because Arch sees root as sda6, while RIP passed it in as hda6...
Deciding to see what Arch would be seeing as it tried to set things up in the boot sequence, I tried the following next:
# mknod “/dev/root2” b 3 6
(“3” because RIPLinux refers to my hard drive as IDE, while Arch refers to it by major number “8”, which is SCSI. By the way, it IS an IDE drive – not sure why Arch insists on using the sdx nomenclature instead of hdx)
Then I entered “mount /dev/root2 /mnt/hda6” and “ls /mnt/hda6”
All was well. I can make the node, I can mount it, and I can see the contents. All is clearly well, but something is clearly wrong enough that Arch can’t boot.
I am totally out of ideas. I have tried every trick I know and am out of tricks. I would welcome any insights as to what I could try to get this venerable Arch installation back on its legs.
By the way, the key section of the /etc/lilo.conf file (lest anyone want to know) is:
image = /boot/vmlinuz26
root = /dev/sda6
label = ArchLinux-Duke
initrd = /boot/kernel26.img
read-only
I am stumped. Thanks in advance for any and all pointers you may be able to offer.
Last edited by mac57 (2014-06-02 17:42:21)

Folks, thanks for all your helpful comments, and I wanted to report back to you that I finally overcame the issue, and ArchLinux-Duke (2007) is once again executing flawlessly on my old Pentium Pro 200 system. I won't bother reporting here all the blind allies I went down as I tried to figure out what was wrong, but in the end, literally moments before I was about to give up and overwrite my Arch installation with a new Linux variant (antiX seemed well suited for such old and low power hardware), my attention was drawn to a note I had made in my files back in 2007 about a problem with similar symptoms. In that case, I had just deleted ZenWalk Linux from the hard drive (both Arch and Zen had been on the drive), and merged several partitions to make use of the newly free space. This had changed Arch's view of the drive lettering, and what had been its /dev/sddx root device was now /dev/sdcx. Arch failed to boot, throwing off the same errors I was seeing now. I wish I had recalled that note a month or so ago! It would have saved me a lot of work and a lot of frustration.
At any rate, as a last step, and testing the idea that maybe the drive lettering had changed for some reason, I repeatedly manually booted Arch, specifying root=/dev/sda6, then /dev/sdb6, then /dev/sdd6, and finally, /dev/sdc6. Eureka! Arch now considered itself to be on /dev/sdc6 whereas previously it had been on /dev/sda6. This got me part way there, but the boot failed at the filesystem check stage and threw me into root. I disabled the file system check in /etc/rc.sysinit and got farther. Then I cleaned up /etc/fstab to agree with the new sdc naming, and I was back on the air fully.
So, what had happened was that Arch had changed its view of the drive it was on from sda6 to sdc6. While I could not understand why this "sudden" change had occurred, at least I had a solution, and had Arch back up and running.
Trolling through the rest of my notes, I found the answer. In 2012, the Tekram SCSI card in the machine failed, and I ultimately replaced it with an Adaptec card. The Tekram card did not have a BIOS segment on it. The Adaptec card did. My guess is that this caused the two internal SCSI devices I have built into the system (Iomega ZIP and Jaz respectively) to be enumerated first, claiming the "sda" and "sdb". device names. That left "sdc" for the root device, and that is where Arch went next. This is my guess anyway.
I should have caught this issue back in 2012, at the time, but from my notes, I can see that I tested the new card thoroughly using the Windows NT 4.0 side of the machine, but never thought to bring up Arch as well. Hence, this problem lay dormant for two years, before I attempted to fire up Arch last month and blundered right into it.
It has not all been bad. I have learned more about the ext2 and ext3 file systems and superblocks in the intervening time than I will ever need to use. I have learned how to manually boot Linux on a machine whose BIOS is so old that it cannot address the disk cylinder that the kernel is on and I have completely refreshed the many general Linux skills that used to just flow from my finger tips. It has been a frustrating experience, but ultimately a successful and useful one.
Just wanted to let everyone know that this is now [SOLVED]. I would mark the post as such, but I don't see any obvious way to do that. Thanks again everyone.

[SOLVED] Arch Linux on encrypted luks partition on USB key

Hi
I've installed Arch Linux on a USB key following this Wiki page: https://wiki.archlinux.org/index.php/In … _a_USB_key
I also used dm-crypt as described in this Wiki page: https://wiki.archlinux.de/title/Festpla … iante_1.29
I installed Arch Linux on the USB key using VirtualBox.
To do that, I created a "rawvmdk":
vboxmanage internalcommands createrawvmdk -filename ./usb.vmdk -rawdisk /dev/sdd
Everything works fine when I'm trying to start the system within VirtualBox.
Syslinux loads Arch using the following kernel command:
APPEND cryptdevice=UUID=6aa73872-3755-4bdf-bee3-d1cd7a3fe0bf:main root=/dev/mapper/main-root rw
/etc/mkinitcpio.conf holds the following "HOOKS" configuration:
HOOKS="base udev autodetect modconf block keyboard keymap encrypt lvm2 filesystems fsch resume"
As already mentioned the configuration works within VirtualBox. When I'm trying to boot from the USB key on my real computer, I'm getting an error. Syslinux works fine and loads Linux, but Linux is complaining. Here's the log:
:: running hoock [encrypt]
Waiting 10 seconds for device /dev/disk/by-uuid/6aa73872-3755-4bdf-bee3-d1cd7a3fe0bf ...
ERROR: device '/dev/mapper/main-root' not found. Skipping fschk.
ERROR: Unable to find root device '/dev/mapper/main-root'.
You are being dropped to a recovery shell
I'm not getting prompted for the passphrase since the cryptdevice can not be found. But why? It can be found when I'm booting within VirtualBox. What might be different? I successfully installed other Linux distributions (but without encryption and using GRUB as bootloader) previously within VirtualBox and was able to boot from the USB key on a real machine afterwards.
Some additional information that might help:
Here's the "lsblk -f output" for the stick:
sdd
├─sdd1 ext4 usbboot bb45e84e-842e-4209-8c44-1af3c7933389
└─sdd2 crypto_L 6aa73872-3755-4bdf-bee3-d1cd7a3fe0bf
When I'm running "lsblk" or "blkid" from the recovery shell after the failure, I'm getting no output. "ls /dev/sd*" returns nothing as well. The directory /dev/disk does not even exists in the recovery shell. (I'm not sure if this is normal or not.)
Thanks for helping.
Last edited by The Infinity (2014-08-14 20:26:06)

I still haven't solved the problem:
When starting the system on a machine with NVIDIA GTX 560Ti graphics card:
- X doesn't start using startx or xinit and there are no log entries in /var/log/Xorg.*.log (as I haven't tried to start X).
- I'm getting the message "Waiting for X server to begin accepting connections .. .. .. ..".
- I already tried to uninstall xf86-video-nouveau and nouveau-dri with no effect.
- Additionally: The "default terminals tty1/2/3/..." (which I'm using to start X) from have a poor resolution (I think 640x480 pixel).
When starting the system on a virtual machine or a machine with an ATI Radeon (mobile) graphics card:
- X starts and runs without any trouble the XFCE desktop environment.
- Additionally: The default terminals have a proper resolution (I think the maximal resolution of the display).

[SOLVED]Is there anybody using arch linux in coLinux?

Hei,guys!
I'm using arch linux in coLinux.I got the image file from sf and I successfully booted it on my machine,em,everything seemed to be OK.But when I tried to do this:
pacman -Syu
I got this message :
checking package integrity...
error: error while reading package /var/cache/pacman/pkg/gdbm-1.8.3-7-i686.pkg.tar.xz: Unrecognized archive format: Invalid or incomplete multibyte or wide character
error: failed to commit transaction (libarchive error)
Errors occurred, no packages were upgraded.
I think the pacman(maybe just libarchive) is too old to recognize the .pkg.tar.xz files. So dose someone have an idea to work out it?
Last edited by Cristie (2011-05-28 16:03:35)

@twilight0:yeah,I acknowledge that,but it didn't work at all. I guess you didn't understand my problem. You know, the pacman coudn't upgrade (in fact I was unable to install any packages) just because the libarchive package was out of date (it meant that I could do nothing with the .tar.xz files downloaded from the mirrors).So I solved the problem by doing like this(Stupid it is, but it really works):
1.Download libarchive from any of the mirrors around the world.
2.Find a way to access to the files you just downloaded.
3.Replace the original libarchive files.
4.Mofify the local db.It is OK to do this:go to /var/lib/pacman/local,rename the libarchive-VERSION to current version.
Then I found that depences need openssl >= 1.0.0, so try the same proccess with it.
So,now everything is running very well.
Last edited by Cristie (2011-05-28 16:20:03)

[SOLVED] Arch Linux is zombie infested !!!

Sigh !
I don't know what happened but a few minute before when I rebooted my Arch Linux desktop, it started acting weird.
First thing I do is to start my torrent client Deluge, look there was no icon in the tray for it but it was shown in System-monitor.
Then I started Firefox, a few minute later the whole thing logged off. I renter my password and then again it logged of within one minute.
So I rebooted to see if that changes this time, but this time I could see was that firefox was shown as ZOMBIE process and then when I tried to take the screenshot the system hanged
Some thing I did today was
Installed Yaourt
Then installed nautilus-dropbox plugin
Dropboxd service runs in background, so is there something fishy about the dropbox service. I tried to kill it but it again restarts.
Please help me from zombie infestation, I am writing this from Ubuntu
Last edited by visio159 (2008-09-14 08:41:47)

No one replied !!! huh
Well good news is that my RAM module needed a dust cleanup. Probably due to corrupt memory it was behaving bad.
I am impressed that it (linux) logged me off when it detected that there were memory violation and corruptions to prevent any data damage ! Now can anyone explain this to me ? Is it really a feature or was just random occurring ?
Case solved, learned a lesson too.
Last edited by visio159 (2008-09-13 05:44:10)

[Solved] Spammed with a nouveau message while installing Arch Linux?

Well despite being spammed the message which makes it impossible to partition my drive using cfdisk, all I could accomplish was setting up my wireless adapter. Here is the message: http://i.imgur.com/O6pIW0V.jpg
Is there any way I can solve this? It appears to happen in the Alt + Ctrl + F2 terminal in Ubuntu too. I have an Nvidia GTX 760. I am not using dual graphics. My only video card is the 760.
<modedit>Please read our forum policy about posting images: https://wiki.archlinux.org/index.php/Forum_Etiquette. /Xyne </modedit>
Last edited by kensclark16 (2013-08-28 01:53:35)

Should I make a new thread? I have another question. I followed the whole Beginner's Guide up to the point where I mount Arch Linux and chroot in. I then set up the language, font, etc and got to the wireless setup part. It told me to do a few commands then enter
pacman -S dialog
. I did that which I think I messed up after that. I misread the text because it said to reboot and use wifi-menu AFTER you install the rest. I rebooted right after I installed "dialog." Now when I boot into Arch with GRUB, it says that I am missing the kernel headers. I used the CD to boot and then I mounted the partition but then arch-chroot /mnt will not work. It says that the exec is invalid or something. Does that mean I have to reinstall Arch?
Last edited by kensclark16 (2013-08-28 01:25:36)

[SOLVED]Arch Linux running inside GNOME Boxes.

Hello,
I wanted to create a vm using GNOME Boxes to run another Arch Linux installation (to test things and avoid to break my main system).
I did a normal install, then installed gnome-shell and gdm from testing repos. I enabled gdm and NetworkManager and after reboot my box.
The box don't boot. The main display only see early fsck lines (about /), I can see in the thubnail more lines but can't read messages.
What is wrong here ?
Regards,
Fabien
Last edited by fbourigault (2014-10-07 11:22:36)

I can't read it it only show in the thumbnail. I posted here to known if I missed some package installation or if someone already had the problem and solve it !.
EDIT:
I installed a new box, using gnome from stable repositories. I installed the same packages but didn't enable anything. I'm starting services by hand to allow me do configuration in the box
You can find the gdm log here : http://pastebin.com/R5ek3Xwy (full version with multiple failing runs :http://pastebin.com/fCsPxAvb)
EDIT 2 :
Problem solved by installing xf86-video-qxl from AUR ! This package should really be in official repos.
Last edited by fbourigault (2014-10-07 08:41:32)

[SOLVED] (U)EFI dualboot Win7 Arch Linux - partitions gone - recovery?

Hi everybody,
I have a slight problem with my (U)EFI dualboot system (Windows 7 and Arch Linux) which used to be configured using rEFInd like it is described in my previous post:
https://bbs.archlinux.org/viewtopic.php … 6#p1300356
<EFI PARTITION> is /dev/sda1 and I used to boot via <EFI PARTITION>\EFI\Boot\Bootx64.efi which then successfully either loaded Windows or Linux kernel.
Thanks to my own stupidity and a recent update of refind I decided to copy the new driver, font and icon folders to the <EFI PARTITION> in order to be up-to-date.
After doing so, the rEFInd boot menu had a third icon which said "Boot via \EFI\Boot\Bootx64.efi" and if I clicked on it a second rEFInd boot menu appeared with only the two icons for Windows 7 and Arch.
So I figured I could delete Bootx64.efi and ultimately did so, unfortunately. Afterwards I couldn't boot neither Windows nor Linux anymore.
Following this I went through my noumerous USB boot sticks in order to be able to recover the Bootx64.efi. Unfortunately the first USB stick was a Windows XP one which has the plop bootloader alongside:
http://www.plop.at/en/bootmanager/thebootmanager.html
Out of couriousity I entered this bootloader and found HDA and HDB (I assume resembling my SSD and my USB stick).
To my knowledge I didn't change anything but after entering the bootloader again I just found HDA left, HDB seemed to be gone. But I didn't think of anything bad happening yet.
Then I found a working Archiso which I booted and using blkid I couldn't find the partitions of my earlier system anymore, only its device and the USB stick:
/dev/sda: PTUUID="..." PTTYPE="gpt"
/dev/sdb1: UUID="..." LABEL="ARCH_201312" TYPE="..." and so on
/dev/sdb2: SEC_TYPE="msdos" and so on
Even within the EFI shell I could not detect any internal drive anymore (only fs0: which is the USB stick)
Using Archiso onboard tool testdisk I could find the old partitions. The correct result of the GPT from testdisk is:
Fri Jul 4 08:45:25 2014
Command line: TestDisk
TestDisk 6.14, Data Recovery Utility, July 2013
Christophe GRENIER <[email protected]>
http://www.cgsecurity.org
OS: Linux, kernel 3.12.1-3-ARCH (#1 SMP PREEMPT Tue Nov 26 11:17:02 CET 2013) x86_64
Compiler: GCC 4.8
Compilation date: 2013-08-06T08:42:31
ext2fs lib: 1.42.8, ntfs lib: libntfs-3g, reiserfs lib: 0.3.0.5, ewf lib: none
/dev/sda: LBA, HPA, LBA48, DCO support
/dev/sda: size 500118192 sectors
/dev/sda: user_max 500118192 sectors
/dev/sda: native_max 500118192 sectors
/dev/sda: dco 500118192 sectors
Warning: can't get size for Disk /dev/mapper/control - 0 B - 1 sectors, sector size=512
Hard disk list
Disk /dev/sda - 256 GB / 238 GiB - CHS 31130 255 63, sector size=512 - Samsung SSD 840 PRO Series, S/N:S12RNEAD322171L, FW:DXM04B0Q
Disk /dev/sdb - 2013 MB / 1920 MiB - CHS 1022 62 62, sector size=512 - SMI USB DISK, FW:1100
Disk /dev/sdc - 4210 MB / 4015 MiB - CHS 1020 130 62, sector size=512 - Generic Flash Disk, FW:8.07
Disk /dev/mapper/arch_root-image - 1478 MB / 1410 MiB - 2887680 sectors, sector size=512
Disk /dev/dm-0 - 1478 MB / 1410 MiB - 2887680 sectors, sector size=512
Partition table type (auto): Intel
Disk /dev/sda - 256 GB / 238 GiB - Samsung SSD 840 PRO Series
Partition table type: EFI GPT
New options :
Dump : No
Align partition: Yes
Expert mode : Yes
Analyse Disk /dev/sda - 256 GB / 238 GiB - CHS 31130 255 63
hdr_size=92
hdr_lba_self=1
hdr_lba_alt=500118191 (expected 500118191)
hdr_lba_start=34
hdr_lba_end=500118158
hdr_lba_table=2
hdr_entries=128
hdr_entsz=128
hdr_size=92
hdr_lba_self=500118191
hdr_lba_alt=1 (expected 1)
hdr_lba_start=34
hdr_lba_end=500118158
hdr_lba_table=500118159
hdr_entries=128
hdr_entsz=128
Trying alternate GPT
Current partition structure:
Trying alternate GPT
search_part()
Disk /dev/sda - 256 GB / 238 GiB - CHS 31130 255 63
FAT32 at 0/32/33
FAT1 : 4110-6150
FAT2 : 6151-8191
start_rootdir : 8192 root cluster : 2
Data : 8192-2097151
sectors : 2097152
cluster_size : 8
no_of_cluster : 261120 (2 - 261121)
fat_length 2041 calculated 2041
set_FAT_info: name from BS used
FAT32 at 0/32/33
MS Data 2048 2099199 2097152 [NO NAME]
FAT32, blocksize=4096, 1073 MB / 1024 MiB
NTFS at 146/251/42
filesystem size 249593856
sectors_per_cluster 8
mft_lcn 786432
mftmirr_lcn 2
clusters_per_mft_record -10
clusters_per_index_record 1
NTFS part_offset=1209008128, part_size=127792054272, sector_size=512
NTFS partition cannot be added (part_offset<part_size).
NTFS at 146/251/42
filesystem size 249593856
sectors_per_cluster 8
mft_lcn 786432
mftmirr_lcn 2
clusters_per_mft_record -10
clusters_per_index_record 1
MS Data 2361344 251955199 249593856
NTFS, blocksize=4096, 127 GB / 119 GiB
recover_EXT2: s_block_group_nr=0/160, s_mnt_count=1318/4294967295, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 5242880
recover_EXT2: part_size 41943040
MS Data 251955200 293898239 41943040
ext4 blocksize=4096 Large file Sparse superblock, 21 GB / 20 GiB
recover_EXT2: s_block_group_nr=0/80, s_mnt_count=1317/4294967295, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 2621440
recover_EXT2: part_size 20971520
MS Data 293898240 314869759 20971520
ext4 blocksize=4096 Large file Sparse superblock, 10 GB / 10 GiB
recover_EXT2: s_block_group_nr=0/706, s_mnt_count=1317/4294967295, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 23156049
recover_EXT2: part_size 185248392
MS Data 314869760 500118151 185248392
ext4 blocksize=4096 Large file Sparse superblock, 94 GB / 88 GiB
Results
P MS Data 2048 2099199 2097152 [NO NAME]
FAT32, blocksize=4096, 1073 MB / 1024 MiB
P MS Data 2361344 251955199 249593856
NTFS, blocksize=4096, 127 GB / 119 GiB
P MS Data 251955200 293898239 41943040
ext4 blocksize=4096 Large file Sparse superblock, 21 GB / 20 GiB
P MS Data 293898240 314869759 20971520
ext4 blocksize=4096 Large file Sparse superblock, 10 GB / 10 GiB
P MS Data 314869760 500118151 185248392
ext4 blocksize=4096 Large file Sparse superblock, 94 GB / 88 GiB
interface_write()
1 P MS Data 2048 2099199 2097152 [NO NAME]
2 P MS Data 2361344 251955199 249593856
3 P MS Data 251955200 293898239 41943040
4 P MS Data 293898240 314869759 20971520
5 P MS Data 314869760 500118151 185248392
simulate write!
TestDisk exited normally.
ext4 blocksize=4096 Large file Sparse superblock, 94 GB / 88 GiB
Now the question is: Can I - using testdisk or any other tool - recover those partitions successfully so I will be able to boot again afterwards? I tested and I could mark them as:
P Primary
Any help will be greately appreciated.
Best regards
Last edited by blablubb1234 (2014-07-08 09:20:08)

Issue resolved If you care to know how, read on:
Looking at the disk using gdisk was doing no good. Neither of the recovery options in gdisk did the trick.
I then returned to testdisk and restored the partitions (successfully). However, afterwards I was greeted by shell telling me the root device was not found (seems like UUIDs get changed when one restores them using testdisk). Adjusting the PARTUUID for root in <EFI SYSTEM PARTIITION>/boot/refind_linux.conf did the trick and I could boot up Archlinux again.
Windows 7 still didn't boot telling me the required device was inaccessible (probably wrong UUID, too). I could however not restore/edit Windows' BCD using bcdedit, see my post Status: 0xc0000225 boot selection failed; required device inaccessible:
To make a long story short: Removing bcd and running autorecovery from withing Windows RE successfully created a new bcd. Unfortunately, Windows writes its backup bootloader at <EFI SYSTEM PARTITION>/boot/EFI/Boot/bootx64.efi. This file originally was a copy of refind_x64.efi which I need to put at that location to be able to dualboot. After chrooting to my Arch system I could restore bootx64.efi, create a new fstab and everything is running fine now again.
Best regards and thanks for the help.

[SOLVED]System Hang in Arch Linux

I have tried distributions like ubuntu and fedora in hope for finding a stable system . So I move on to Arch Linux
But this problem also exist on Arch. While using my Arch Linux (including ubuntu and fedora) my system hangs with a black screen with something written on the whole screen which cannot be pasted here as my system hangs and I have to push power button to restart.
So I check my errors.log file and found these errors
Jul 8 22:59:24 localhost kernel: [ 1.680013] ata3: softreset failed (device not ready)
Jul 8 22:59:24 localhost kernel: [ 7.298612] SP5100 TCO timer: mmio address 0xfec000f0 already in use
Jul 8 22:59:31 localhost kdm_greet[792]: Cannot load /usr/share/apps/kdm/faces/.default.face: No such file or directory
I have a HCL K21 pdc notebook
Note: In Ubuntu my notebook start with ata1: softreset failed error at boot time
Most often this error occur while watching videos or listening music with VLC
Last edited by Manuj19 (2011-07-09 10:13:24)

ewaller wrote:It might be better to just post the output of lspci -nn It will tell us a great deal more about the hardware related to the PCI bus, including specific chip set identifiers.
Thanks for suggestion
Here is output of lspci -nn
00:00.0 Host bridge [0600]: ATI Technologies Inc Device [1002:5a31] (rev 01)
00:01.0 PCI bridge [0604]: ATI Technologies Inc RS480 PCI Bridge [1002:5a3f]
00:04.0 PCI bridge [0604]: ATI Technologies Inc RS480 PCI Bridge [1002:5a36]
00:05.0 PCI bridge [0604]: ATI Technologies Inc RS480 PCI Bridge [1002:5a37]
00:06.0 PCI bridge [0604]: ATI Technologies Inc RS480 PCI Bridge [1002:5a38]
00:07.0 PCI bridge [0604]: ATI Technologies Inc RS480 PCI Bridge [1002:5a39]
00:12.0 SATA controller [0106]: ATI Technologies Inc SB600 Non-Raid-5 SATA [1002:4380]
00:13.0 USB Controller [0c03]: ATI Technologies Inc SB600 USB (OHCI0) [1002:4387]
00:13.1 USB Controller [0c03]: ATI Technologies Inc SB600 USB (OHCI1) [1002:4388]
00:13.2 USB Controller [0c03]: ATI Technologies Inc SB600 USB (OHCI2) [1002:4389]
00:13.3 USB Controller [0c03]: ATI Technologies Inc SB600 USB (OHCI3) [1002:438a]
00:13.4 USB Controller [0c03]: ATI Technologies Inc SB600 USB (OHCI4) [1002:438b]
00:13.5 USB Controller [0c03]: ATI Technologies Inc SB600 USB Controller (EHCI) [1002:4386]
00:14.0 SMBus [0c05]: ATI Technologies Inc SBx00 SMBus Controller [1002:4385] (rev 13)
00:14.1 IDE interface [0101]: ATI Technologies Inc SB600 IDE [1002:438c]
00:14.2 Audio device [0403]: ATI Technologies Inc SBx00 Azalia (Intel HDA) [1002:4383]
00:14.3 ISA bridge [0601]: ATI Technologies Inc SB600 PCI to LPC Bridge [1002:438d]
00:14.4 PCI bridge [0604]: ATI Technologies Inc SBx00 PCI to PCI Bridge [1002:4384]
01:05.0 VGA compatible controller [0300]: ATI Technologies Inc RC410 [Radeon Xpress 200M] [1002:5a62]
02:00.0 Ethernet controller [0200]: Atheros Communications Inc. AR5001 Wireless Network Adapter [168c:001c] (rev 01)
08:01.0 CardBus bridge [0607]: Ricoh Co Ltd RL5c476 II [1180:0476] (rev b3)
08:01.1 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C552 IEEE 1394 Controller [1180:0552] (rev 08)
08:01.2 SD Host controller [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter [1180:0822] (rev 17)
08:01.3 System peripheral [0880]: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter [1180:0592] (rev 08)
08:07.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ [10ec:8139] (rev 10)
Last edited by Manuj19 (2011-07-09 07:20:08)

[Solved]voip in arch linux

Similar Messages

Maybe you are looking for