[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)

Similar Messages

[SOLVED] Arch Linux Guest Virtual Box OSE problem

So I am installing my Arch Linux as a Guest in my Ubuntu partition, through Virtual Box OSE (3.2.8). I followed the wiki ( https://wiki.archlinux.org/index.php/Ar … lBox_Guest ) but still have an issue:
sudo pacman -S kernel26-headers xorg gcc make
sudo mount /dev/cdrom /mnt/cdrom
sudo /mnt/cdrom/VBoxLinuxAdditions-x86.run
But It fails on Shared folders, and cannot recognize X:
:: Building the VirtualBox Guest Additions Kernel Modules [BUSY]
:: Building the main Guest Additions module [DONE]
:: Building the shared folder support module [FAIL]
(Look at /var/log/vboxadd-install.log to find otu what went wrong)
:: Warning: Unknown version of the X Window System installed. Not installing X Window System drivers.
:: Installing graphics libraries and desktop services components [Done]
/var/log/vboxadd-install.log states:
/tmp/vbox.0/vfsmod.c:406:9: error: unknown field 'clear_inode' specified in initalizer
/tmp/vbox.0/vfsmod.c:406:9 warning: initalization from incompatible pointer type.
Which is strange, because as far as I know, clear_inode is part of the linux headers.
Any idea why this is happening? Do I just need to update VirtualBox to a newer version?
Last edited by gralamin (2011-03-11 18:22:14)

Updating Virtualbox fixed the issue.

[Solved]Arch Linux Gnome writing to usb disk destination is read only

Hi
i Have installed Arch Linux latest image 1-3-2015 not using Evolution Linux or any GUI installer
i installed Arch Linux using command line
i have gnome 3.14
each time i try to write movie to usb flash or usb external hard disk
the error says
the destination disk is read only
how to change this
Last edited by belal (2015-04-04 20:58:54)

I'm curious. Is the filesystem on the USB, ntfs ?
If yes, did you install NTFS-3G ? https://wiki.archlinux.org/index.php/NTFS-3G. Happened to me 8 days ago .
EDIT - Sorry for the repost using the same solution as my above post. Didn't see his link. Just surfed through the posts for the word "NTFS-3g" and it wasn't there.
Last edited by newguy (2015-03-31 07:51:48)

[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 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...

Arch Linux running on Asus Transformer T100/T100TA... sort of.

I'm not really asking for help here (can't find an appropriate place to put this post), but more to show off my accomplishment with this tablet.
As the thread title says, I've gotten Arch Linux to run on the Asus T100TA which is a quite annoying little thing. I haven't documented the steps myself, however, I remember exactly what I have done, and in order to get the live image to at least run on this tablet, here are the steps I did:
(you'll maybe need 2 USB drives, seems to be the easiest way)
1. Create an ISO using the archiso set as you normally would (except you won't really need the ISO itself) OR if you can figure it out yourself, install the base image to the USB drive (either architecture will do, but I recommend i686 since the processor is 32 bit as well)
https://wiki.archlinux.org/index.php/Archiso
This step will be unnecessary as of May, as the live images onwards on the main download site will already contain the 3.14 or newer kernels.
2. After the image building successfully finishes, copy all the contents from (PROFILE)/work/iso/ (except root-image squashfs files) to a FAT32 formatted USB drive (1). This is to simply create a bootloader drive that will allow us for later swapping the USB drives.
3. Download an ia32 version of grub. Any will do as long as it can boot up on the tablet.
http://www.supergrubdisk.org/category/download/supergrub2diskdownload/
This one works, download the standalone IA-32/i386 EFI and paste it in (USB Drive (1))/EFI/boot/bootia32.efi .
(use latest versions, no matter if it's unstable)
4. Now you need to make a grub.cfg. The one I made looks like this
menuentry 'Arch Linux i686'{
echo 'Loading Linux core repo kernel ...'
linux /arch/boot/i686/vmlinuz noefi nomodeset archisobasedir=arch archisolabel=ARCH_201404
echo 'Loading initial ramdisk ...'
initrd /arch/boot/i686/archiso.img
menuentry 'Arch Linux x86_64'{
echo 'Loading Linux core repo kernel ...'
linux /arch/boot/x86_64/vmlinuz noefi nomodeset archisobasedir=arch archisolabel=ARCH_201404
echo 'Loading initial ramdisk ...'
initrd /arch/boot/x86_64/archiso.img
NOTE: If you're using a later live image build, I advise to change the date accordingly. It's not necessary to do so, since the mount by label doesn't work, however, I like to keep everything intact.
noefi flag seems unnecessary as well, though I have added it to prevent some kernel panics from happening, for just in case. It works without it, still, however you need the nomodeset flag or else you'll get a black screen!
I'm not entirely sure where the grub.cfg goes, but I've put it in USB Drive(1)/boot/grub/ , /EFI/grub/ and in /EFI/boot/grub/ just to make it sure that it works.
5. Create an ext2/3/4 (recommended ext2 for flash drives, not to wear it out) USB drive (2) and copy the arch folder to the root of the USB drive (2)
---- BOOT PROCESS ----
Before this step, ensure that Secure Boot is set to OFF in the Aptio setup. Otherwise it will throw up an error in a red box crying it's not signed.
6. Plug in the USB drive (1) into a USB port and while powering on the tablet, tilt the escape key to pop up a boot menu.
7. Select UEFI: (your USB drive (1))
8. GRUB 2 will pop up. If you're running the SuperGrubDisk version, you're gonna have to go to Everything and then scroll down until it says something like
(hd0, msdos1)/boot/grub/grub.cfg
and click on it to open the configuration data manually created.
9. Simply select your desired version of Arch Linux live distro to boot.
10. VOILAaa, not really... It'll pop up with a mount error saying it's a wrong FS to mount. This is where you plug in your USB drive (2) in place of the first one.
11. Type in:
# mount /dev/sda1 /run/archiso/bootmnt
# exit
12. Congratulations, you're running Arch Linux on your ASUS Transformer T100TA tablet!
This is as far as I have went into running it. Installing it on a HDD would require mounting the mmcblk partitions, which I haven't looked into yet. For a start, I'd just recommend installing it on a USB drive, though you'd have to own one of the USB OTG converters or a USB hub. The screen is spammed with the mmcblk0rpmb timeout errors though and that is annoying. It stops after a while when it stops trying. Reboot doesn't work either, seems like acpi is broken.
You could do it with a single usb drive, though it requires some knowledge of this tablet's EFI because it disallowed me from running a kernel on another partition other than FAT32. Grub pops up with an error:
can't unload EFI services
or something like that.
I've also tried putting the USB Drive (2) in during grub and it pops up with an error with invalid sector sizes. That was to be expected.
btw I know it's my first post, I'm just here to share this with you. I never had the need to ask for help but when absolutely necessary.
PICS OF IT RUNNING
Some USB devices aren't visible, like the camera.
A custom partition layout without the recovery partitions. Yours may differ.
Last edited by xan1242 (2014-04-13 22:54:46)

I haven't tried much other than getting this live image to run on this machine. I'll attempt to install the base image using my desktop computer with the appropriate drivers and see how that goes. (or just install the wifi driver)
That guy really made it to work much better than I imagined it to work at all! I'll see what can be done using the same drivers, though running Ubuntu seems tempting as well. He even got the touchscreen to work, which is really awesome. It seems that he also merged the drivers into the kernel image, which is going to be a challenge in Arch.
Since he's using the 64 bit build of Ubuntu, I'll try it with x86_64 Arch as well to try and use his guide to make the drivers to work.
EDIT: I have successully installed the base to an external drive and booted it on the tablet, however since the base was installed externally on another machine, I need to regenerate initrd. It boots on the fallback ramdisk, but still no wifi and the screen is spammed even more with the timeout errors. I've seen topics on Raspberry Pi having a similar issue and that it was repaired using some kernel flags, but I am not sure if those will work with the tablet. Also, using the bootflags jfwells used on Ubuntu work here as well, and gives full resolution output now. Wifi doesn't work. ip link doesn't give any signs of a wifi card present.
EDIT2: Got Arch up and running relatively nicely on the tablet now. Though it is in the same state as the last edit in terms of functionality, it works I'd say well enough to be considered usable. I couldn't make the wireless card to work, for some strange reason, so I got a RT73 USB card (Edimax EW-7318USg to be precise, had to use 2 USB ports) and installed stuff on to the tablet. I ran X without a desktop manager, and the X apps worked fine, even with the touch screen (emulating a mouse, no right click) and I ran XFCE4 on it without a problem (with compositing).
It simply needs more developed drivers on it, that's mostly it. The state is exactly the same as Ubuntu 14.04 that jfwells made to work (minus the wifi). I haven't played with the sound, either, due to the warning he posted, but I believe it works as it does in Ubuntu.
The steps I made are as follows:
1. Simply made another live ISO with the archiso set
2. dd'd the image to a USB drive
3. On the second USB drive I created two GPT partitions (200 - 300 MB for ESP, everything else ext2)
4. Booted the live archiso USB drive
5. Installed the base to the second USB drive while being mounted like this: ext2 partition -> /mnt and ESP -> /mnt/boot
6. Installed GRUB x86_64-efi to simply generate a configuration
7. Installed wireless utilities as well as everything else needed to make it to work
8. To ensure bootability on the tablet, again, I put the IA32 GRUB to the ESP in /EFI/boot/bootia32.efi
9. I have edited the grub.cfg, can't exactly remember with what, but this is what it looks like
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-(hd0,gpt2)' {
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,gpt1'
echo 'Loading Linux core repo kernel ...'
linux /vmlinuz-linux root=/dev/sda2 video=VGA-1:1368x768e reboot=pci,force sdhci.debug_quirks=0x8000 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
menuentry 'Arch Linux, with Linux core repo kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-fallback-(hd0,gpt2)' {
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,gpt1'
echo 'Loading Linux core repo kernel ...'
linux /vmlinuz-linux root=/dev/sda2 video=VGA-1:1368x768e reboot=pci,force sdhci.debug_quirks=0x8000 rw quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux-fallback.img
### END /etc/grub.d/10_linux ###
I simply added the kernel flags jfwells added. It needs that root flag, or else it will not boot. I can't figure out the UUIDs though. It will reboot, but it will not shut down.
10. Boot up your second USB drive on the tablet and... IMPORTANT - Boot with the fallback ramdisk - or else you're going to experience non functional input
11. After booting it, you'll get the annoying mmcblk timeout spamming the screen. I haven't figured out how to fix it, but to hide it, type in
# dmesg -n 1
12. Generate another ramdisk (forgot the command, but search function should serve you)
13. Reboot with the normal ramdisk now.
14. After setting up the wireless connection, rock on with the pacman!
At this point I installed a bunch of stuff, like Intel GPU drivers, xorg, xfce4, ntfs-3g, gparted, and among other stuff I personally test stuff with.
I couldn't mount the mmcblk partitions to at least somehow be able to edit data on the Windows partitions or the disk as a whole.
Anybody willing to help getting Arch to run on this tablet is welcome.
EDIT3: Internal WiFi working! Simply added "sdhci.debug_quirks=0x8000" flag.
Last edited by xan1242 (2014-04-13 23:35:26)

[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] 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]Arch Linux / UEFI / BTRFS using Grub2 & Windows 8 in a 2nd HDD

PROBLEM:
====================================================================================
Dear fellas
I just purchased an new HP TouchSmart 17.3" laptop that comes with Windows 8.1 pro (1 tb HDD + small SSD for cache only ) and still have space for one more HDD or SSD.
I Google a lot and read a lot but many questions emerged since seems that no one has the same scenario (maybe I pick the wrong choices) like me.
The problem is.. I didn't wish to re-install Windows 8.1 since it came with from factory.. so I purchased a 750 gb hdd and put it into the free slot to install Arch Linux in a different HDD.
As I am not familiar with UEFI what I did was to reorder the hdds. I just put the Windows HDD as second disk and the new disk (For Arch Linux) as primary and changed into Bios from UEFI to compatibility mode and installed Arch Linux into the primary one.
I reaaaally need help to add to grub the correct "path" to Windows 8.1 disk that came with UEFI..
Anyone could please help me?
Thanks in advance!
====================================================================================
SOLUTION:
A huge thanks to @TheSaint and other users for their help and assistance!
More sources:
http://www.kossboss.com/linux---arch-in … -grub-boot
https://www.youtube.com/watch?v=METZCp_JCec#t=146
https://bbs.archlinux.org/viewtopic.php … 1#p1390741
Step by Step Summary:
Use gdisk to create partitions on /dev/sda:
- 512MB - EF02 type partition (for EFI boot)
- 690GB - Linux partition for the BTRFS.
- Create an EF00 (ESP) with 512mb
- Create a Linux System partition with the rest of space
Make the FAT 32 system for EFI boot:
# mkfs.vfat -F32 /dev/sda1
Make the BTRFS partition. If it complains about existing filesystems just add a "-f":
# mkfs.btrfs -L arch -f /dev/sda2
We will make out a root subvolume for sda1, this will be a folder called root located at the root of sda2. The way we will design this is that When the system boots we will not see /root, we will be inside root. Inside root you will have all of your etc,sys,proc,whatever folders etc.
# mount /dev/sda2 /mnt
# cd /mnt
# btrfs subvolume create /mnt/root
This should show you your root
# btrfs subvolume list -a /mnt
Something like this: ID 256 gen 5 top level 5 path root
# cd /
# umount /dev/sda2
Now we will mount sda2 root subvolume as /mnt and we will dump the arch system into there with pacman. We will also enable compress to utilize btrfs compress feature.
# mount -o defaults,compress=lzo,subvol=root /dev/sda2 /mnt
NOTE: the command "mount" will not show which subvolume is mounted, to see how subvolumes are mounted you need to look inside proc (cat /proc/self/mountinfo):
# cat /proc/self/mountinfo | egrep sda2
The line for the mount of sda2 looks like this:
43 21 0:34 /root /mnt rw,relatime shared:30 - btrfs /dev/sda2 rw,compress=zlib,ssd,space_cache
We can see that the subvolume /root is mounted to /mnt from the device /dev/sda3
Notice how with regular mount command its missing:
# mount | egrep sda2
/dev/sda3 on /mnt type btrfs (rw,relatime,compress=zlib,ssd,space_cache)
Pacman will dump stuff into a boot folder, so we better mount our sda1 EFI boot partition to it. Or else all of the boot stuff will go to sda3 instead of sda1:
# cd /
# pacstrap -i /mnt base base-devel
Let us create the directory and mount the EFI partition
# cd /mnt
# mkdir -p /mnt/boot/efi
# mount /dev/sda1 /mnt/boot/efi
Let us generate the FSTAB:
# genfstab -p /mnt >> /mnt/etc/fstab
Let us chroot into the arch installation:
# arch-chroot /mnt /bin/bash
Change password:
# passwd
Then pick the right one like this and associate it with a link to /etc/localtime
# ln -s /usr/share/zoneinfo/US/Pacific /etc/localtime
Let us generate the initial RAM disk
# mkinitcpio -p linux
Let us setup the bootloader (GRUB)
# pacman -Syu grub efibootmgr
Let us generate the grub configuration
# grub-mkconfig -o /boot/grub/grub.cfg
Let us install grub into the HDD
# grub-install /dev/sda
# umount -R /mnt
# umount /mnt
# reboot
From this step you can go straight and forward with the https://wiki.archlinux.org/index.php/Beginners%27_guide
Last edited by erickwill (2014-11-21 20:41:06)

TheSaint wrote:As UEFI BIOS is a boot loader itself. You should make on each HDD an ESP.
When you want to start win8 you go to BIOS and chose its entry, so will do for Arch the same.
For this way I suggest you write to boot the kernel directly from the BIOS. It just take some reading on this topic
Other option you set on you second ESP the boot loader of your liking and it will try to find win8 partition.
Thanks for your reply.
For the second option, may I use the compatibility mode and install the booloader into the first partition along with Arch?
Or in case the first option is still the better option, could you pleaaaase give me some directions from the scratch? Do you have Google Hangout?
Thanks in advance.
Last edited by erickwill (2014-11-18 19:54:26)

[Bounty] Free Macbook Pro to get Arch Linux running on Amazon's EC2

First, the details:
I will purchase a lowest–end Macbook Pro 13″ ($US 1,200 on Apple's store, new) for the first person to deliver to me a working set of step–by–step instructions for installing the latest Arch Linux on top of Amazon's EC2 platform.
Caveats & Rules:
- I don't care how long it takes you—there's a good chance I'm doing something absolutely stupid in my noobishness that's causing the problems I've been experiencing; if it takes you half an hour to make a working AMI, and produce instructions to do such… you just won yourself a Macbook Pro for half an hour's work. Booyah!
- Again, I say, I don't care how long it takes you—if you don't produce a working set of instructions, there will be no payout, even if you spend 200 hours trying (as I already have!). It's a bounty, not a work contract d-:
- You must provide me with instructions that work for me (as I don't intend to use your AMI, but rather modify the steps that worked for you a bit at a time until I arrive at an AMI configured exactly as I want it). If you arrive at a working AMI, and can reproduce your steps successfully locally, but they can't be made to work for me, I may be able to go about procuring alternative hardware for myself on which to preform the steps, or taking other measures to reproduce your environment; but the bottom line is I will not shell out until I can, personally, produce a working AMI running Arch Linux.
- The instructions are considered to be "working" when I can successfully SSH into the root account on an instance instantiated from an AMI created by following the instructions using the key generated by EC2.
- Your instructions must work both for x86_32 and x86_64 instance types; however, this shouldn't be too much of a problem, as (barring any weirdness) anything that works on x86_32 should be easily made to work on x86_64.
- Instructions that involve instantiating an intermediate bundling host (say, a CentOS or Fedora Core instance) and then installing Arch to a loopback filesystem using a statically–built pacman are much preferred to instructions that involve me having to install and package Arch locally and then ship it up to S3, because my upstream is unimaginably slow and I eventually will need to create something between eight and twenty different AMIs (see below). But anything that works will be accepted.
- If you don't want a Macbook Pro, alternative payment methods may be arranged, though you need to contact me before you start and arrange these, as there's only so much I can do.
- If you are in any way confused or unsure of what I'm offering here, please contact me before you start (see below for contact info)
Backstory:
I set up the first AMI for Arch Linux on Amazon, but unfortunately, I did some really stupid things (hey, I was completely new to Linux at the time, gimmie a break!). The root filesystem was limited to 1GB, there was a whole bunch of software that really was completely unnecessary (WiFi drivers? on a virtualized server? seriously?), there were no kernel modules provided… and so on.
So, after running all my stuff on instances of that for a while, I finally got fed up and found the time to start setting up a newer, cleaner AMI. Unfortunately, I made the mistake of deleting my old AMI before starting work on the first. Now I find myself completely unable to create an AMI that will work whatsoever, and I cannot for the life of me figure out why.
I've already invested 200 or so hours of my personal time since deleting my original, broken AMI; I'm very fed up and in badly need of working instances. I tried every method I could think of; running the Arch installer from a LiveCD locally and then bundling the running (and thus proved working) Arch install and shipping it off to S3; installing Arch on a loopback filesystem locally, cloning it to a local partition, booting to it to ensure it works, and shipping it off to S3; installing Arch on a loopback filesystem on a remote bundling host running CentOS or whatever and then shipping it off to S3… I've tried installing nothing but the essentials, I've tried installing everything the installer offers… I've tried to do my best to remember the exact steps I took the first time around, years ago, and reproduce them exactly… nothing has worked.
If I take EC2 out of the equation, and install the images I've prepared locally, they work. If I take Arch out of the equation, and install, say, CentOS instead, and then ship it off to EC2, it works. The only time I have problems is when I attempt to install Arch Linux specifically on EC2 specifically; the exact use–case I need.
I've run into a lot of problems along the way, and fixed them as I go, but I universally end up with an AMI that, once instantiated, does not successfully boot. Worse yet, I get absolutely no output from the console (provided by the ec2-get-console command–line tool) to help me debug the problem. I can't give you any more specifics beyond this to help you, because I don't want to insinuate some idea that will cause you to make some little stupid mistake that I also made, thus dooming the project.
Contact:
For more info of any sort, please hit me up on Google Talk or Jabber (… or any other XMPP–federated chat service, or AIM, or ICQ, or MSN, or whatever you like, they all use the same address anyway) at the following address:
[email protected]
Edit: I should point out that it would be good form to post here if you're going to make a stab at it, so interested parties know how many people are already making attempts.
Last edited by elliottcable (2009-07-25 03:59:46)

drtoki wrote:
http://blog.mudy.info/2009/04/archlinux-ec2-public-ami/
lolwat
from fryguy
Public AMIs aren't what I need, because I need to mass–produce quite a few AMIs with different custom configurations for different purposes; so I have to be able to start from scratch and arrive at a working AMI *myself*.
As for the script, I'm sitting down to play with it now; it looks just about exactly like what I've been doing so far. Maybe there's some small thing he did differently that will make it work. Here's hoping it works for me; that'll be a real load off my chest.

[SOLVED]Arch Linux, and Windows 8.1 Dual Boot issue

Hi guys. I recently bought a new laptop, and decided to run Arch Linux and Windows 8.1. I installed Windows 8.1 first as recommended by the beginners guide, and then installed Arch Linux. I made sure UEFI was enabled in my BIOS, and made sure everything was on a GPT partition. The install itself went fine. My laptop loads grub, and Arch Linux shows up and boots, but there is no option to boot into Windows 8.1. The only way I can boot into Windows 8.1 is by accessing my motherboard, and choosing to launch the windows boot manager instead of the grub launcher. How can I get Windows 8.1 to show up in grub? Thanks in advance guys.
Last edited by Painguy (2014-08-20 20:19:37)

Painguy wrote:
-----------Edit------------------
Yeah just ran this after installing os prober
grub-mkconfig -o /boot/grub/grub.cfg
and it works now. Sorry for the crazy posts guys. Thanks for the suggestions and help.
Yeah I'm sure I'm doing something wrong lol. I did not install OS-Prober. I think that's where the issue is. I'm missing the menu entry in grub.cfg right? Do I just run os prober or do I have to manually edit grub.cfg.
If that's not the case then here is what I did up until now. What I did was start with a blank SSD drive. I used cgdisk to make the disk use a GPT partitioning scheme. I installed windows 8.1 and checked in windows to make sure it boots into UEFI-GPT mode and it does. I then installed arch linux using the beginners guide. I made sure to use cgdisk to create any extra partitions, and installed GRUB to the efi partition that windows had created ( I did not format this partition ). I then finished the installation and rebooted, and Grub only shows arch linux. I don't think I'm dealing with anything MBR related. I made sure I used the GPT partitioning scheme....i think lol.
All you need to do is run os-prober then run grub-mkconfig. It should pick up Windows at that point.

[SOLVED] Arch Linux on Macbook Pro 4.1

Hey There,
I'm a 2 years old Arch Linux guy and due to the problems I've had with my HP Pavilion PC, I've bought a Macbook Pro 3-4 months ago.. Because that it's a pain in the ass to install, upgrade and remove software on Mac OS X, especially development software such as Python and its bindings, I'm thinking of migrating to Arch Linux. Any way, I've just installed Arch Linux and dual boot..
I've installed X, GNOME, NVIDIA so far and when I try to open GNOME (via startx), it opens up a 800x600 or 1024x768 resolution X and shows GNOME.. But I can't move the mouse and no matter what I type no menus show up.. So I'm stuck after GNOME starts.. I can't drop back into the terminal so I hold the power button to shutdown and start the machine...
It seems that this is the only problem I have for now.. Anyone had this problem before? I've tried it with and without xorg.conf and the result is the same..
Last edited by T-u-N-i-X (2008-11-30 16:17:11)

CTRL + ALT + Backspace
That should close startx. Also, the user manual has a couple of alternative methods of setting up your xorg.conf file. I'd try those next.
http://wiki.archlinux.org/index.php/Beg … phic_Cards
Last edited by sharpie (2008-11-30 14:05:39)

[Solved] Arch Linux in a Solaris branded Zone

Hello,
After having read this article at the Genunix WiKi, I 'd very much like to install Arch Linux (http://204.152.191.100/wiki/index.php/I … anded_zone) in a Solaris branded Zone. However, the Arch Linux file to download is about two years old now, so I 'd like to roll one with a bit more recent kernel.
I just wonder what might be the procedure to do so.
a) Is it just unpacking the ISO inside the zone and let it enroll whilst booting?, or
b) is it advisable to install the old package and upgrade from there?
I am quite curious to learn how this works.
TIA, Algey
Last edited by algernonz (2011-11-28 18:42:31)

Hi,
it does indeed sound like an interesting little project. You should, however, revert to your procedure (a) and use one of the recent ISO images the Arch team has updated this year.
Using that old tar will give you numerous headaches when trying to upgrade. Doing a simple upgrade from that old file will most probably break the system, thats why they took the effort to provide the new ones.
Good luck.

[SOLVED] Arch Linux Boot from USB fails while loading kernel

I am attempting to get arch linux booting off my usb. I use cfdisk to create a /dev/sdb1 partition then use mkfs.ext4 /dev/sdb1, mount the usb, pacstrap it, use install-syslinux_update -iam, generate fstab and then attempt to boot from it.
The boot extracts the kernel but then complains that DEVICE is missing in the option APPEND root=DEVICE (in syslinux.cfg). I looked in /dev/disk (on the temporary filesystem shell), it showed my ssd and cd drive but not the usb. Does anyone know what could be causing the USB to not load in that particular section of the kernel?
Last edited by afree10 (2013-12-11 14:28:14)

afree10 wrote:
Due to my situation I have to type the file in from scratch so I will only type uncommented lines:
MODULES=""
BINARIES=""
FILES=""
HOOKS="base udev autodetect modconf block filesystems keyboard fsck"
I will reboot and get that lsmod output.
Since you'll probably want to boot from different computers (portable USB system), you want to remove 'autodetect' from that line. This is the same as always booting the initramfs-linux-fallback.img image. To save some space, you could remove 'autodetect' from the configuration file, disable the fallback image in /etc/mkinitcpio.d/linux.preset and delete initramfs-linux.img (otherwise, you'll get two identical images).
Of course, run mkinitcpio -P when you're done.

[SOLVED] Arch Linux install on UEFI motherboard (Asus UX31A)

Hello all,
I am new to Arch Linux (moving over from Mint) and I am having an enormous amount of trouble with booting for UEFI. I go through all the command line installation steps and get to the step where you install and configure a bootloader. I have followed everything step-by-step up and cannot seem to get anything to boot, I get the motherboard settings menu instead. I've tried GRUB, rEFInd, and Gummiboot and all three have not worked for me. Is there any hope for configuring a bootloader? I am used to Mint/Ubuntu creating it for me.
Thanks
Last edited by somedood (2013-06-09 13:23:51)

srs5694 wrote:It shouldn't matter from where you launch the EFI shell, although that will affect device names. If you boot a USB flash drive with an EFI shell on it, chances are fs0: will be the USB flash drive itself. Your rEFInd, though, should be installed on your hard disk, and therefore on another device -- probably fs1:, although it could be fs2:, fs3:, or some other number. If the only filesystem you can find is fs0:, then that indicates something is wrong with your hard disk setup -- perhaps your ESP's filesystem is damaged, or maybe there's something wrong with the partition table.
I followed the steps in the beginners installation guide to create my file system starting with:
cgdisk /dev/sda1
I create 4 Linux filesystem partitions with this, then I run:
mkfs.vfat -32 /dev/sda1
mkfs.ext4 /dev/sda2
mkfs.ex4 /dev/sda3
mkswap /dev/sda4
I then toggle the boot flag of my FAT32 formatted ESP (/dev/sda1):
parted
toggle
1
boot
if it is not turned on according to the output of:
parted
print
After that I mount the drives and turn swap on:
mount /dev/sda2 /mnt
mkdir -p /mnt/home
mount /dev/sda3 /mnt/home
mkdir -p /mnt/boot/efi
mount /dev/sda1 /mnt/boot/efi
swapon /dev/sda4
I install my base system (without changing /etc/pacman.d/mirrorlist) by running:
pacstrap -i /mnt base
Finally I generate my fstab after the Arch installation:
genfstab -U -p /mnt >> /mnt/etc/fstab
I then check the fstab and I get the result from my previous post and according to the guide it is ok because everything but my root partition has a 0 or 2.
somedood wrote:# /dev/sda2
UUID=264fe719-b816-462d-af5b-1b76c73a875b / ext4 rw,relatime,data=ordered 0 1
# /dev/sda3
UUID=824c5b36-6bf3-4c66-8878-5c886dadc9dd /home ext4 rw,relatime,data=ordered 0 2
# /dev/sda1
UUID=49B1-AE7E /boot/efi vfat rw,relatime,fmask=0022, dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
# /dev/sda4
UUID=426143bf-0cb4-4b7e-8868-e82d6fe7bd8b none swap defaults 0 0
To clarify, sda2 and sda3 are my root and home partitions respectively, sda4 is my swap, and sda1 is my ESP.
What could have gone wrong here? This is quite frustrating to me and I really want to use Arch.

[SOLVED]Arch Linux running inside GNOME Boxes.

Similar Messages

Maybe you are looking for