Arch Linux RetroShare Thread

This thread provides a place for Arch Linux forum users to connect with each other by using the RetroShare darknet.
If you would like the opportunity to connect to other Arch Linux forum users, you may reply to this thread announcing that you are available on RetroShare. Other forum users may then send you a private message with their connection information, which you may then choose to respond to.
By "following" this thread, you can be notified when new people announce that they are available on RetroShare. You only need to post to this thread once. If you would like people to stop sending you requests, please edit your original post to say so.
As with all things Arch Linux, you are responsible for learning and understanding the use of RetroShare and any possible consequences.
Please remember to only connect with people you trust.
What this thread is not:
This is not a place to discuss what you will be using RetroShare for. As always, please remember to follow the Arch Linux forum etiquette.
Other:
I am not affiliated with the RetroShare software or website in any way. I have cleared the creation of this thread with the forum moderator ewaller.
Lastly, I don't use RetroShare, but I may in the future.
Thank you.
Last edited by drcouzelis (2012-04-12 19:01:07)

drcouzelis wrote:
No problem, this is a "forever" thread.
You're looking at the Arch Linux user Retroshare community (this thread). No, it's not active.
I suppose the distinctive features (FoF) of retroshare really don't have that much appeal for the common user.

Similar Messages

  • [SOLVED]Multiple Problems after a new install on Arch Linux

    Hello all,
    I just finished installing Arch Linux from the core ISO which I downloaded from the site. The install went smoothly and booted up fine. Also I was able to install gnome and its extras fine as well. On the first boot after installing gnome I managed to get my resolution correct also. However later on after I installed compiz fusion everything with the resolution seems to be going wrong . My computer specs are shown below :
    AMD 64 3200
    Asus M2N MX-SE
    2 GB Ram
    Geforce 8600 GT
    Viewsonic VA1918wm (Native resolution is 1440x900)
    At the moment I can only manage to get upto 1024x768 and it looks quite bad at that resolution. I have attached the xorg.conf I have at the moment.
    Section "ServerLayout"
    Identifier "X.org Configured"
    Screen 0 "Screen0" 0 0
    InputDevice "Mouse0" "CorePointer"
    InputDevice "Keyboard0" "CoreKeyboard"
    EndSection
    Section "Files"
    ModulePath "/usr/lib/xorg/modules"
    FontPath "/usr/share/fonts/misc"
    FontPath "/usr/share/fonts/100dpi:unscaled"
    FontPath "/usr/share/fonts/75dpi:unscaled"
    FontPath "/usr/share/fonts/TTF"
    FontPath "/usr/share/fonts/Type1"
    EndSection
    Section "Module"
    Load "dbe"
    Load "record"
    Load "extmod"
    Load "glx"
    Load "dri2"
    Load "dri"
    EndSection
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "kbd"
    EndSection
    Section "InputDevice"
    Identifier "Mouse0"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "Device" "/dev/input/mice"
    Option "ZAxisMapping" "4 5 6 7"
    EndSection
    Section "Monitor"
    Identifier "Monitor0"
    VendorName "Monitor Vendor"
    ModelName "Monitor Model"
    EndSection
    Section "Device"
    Identifier "Card0"
    Driver "nvidia"
    VendorName "nVidia Corporation"
    BoardName "G84 [GeForce 8600 GT]"
    BusID "PCI:2:0:0"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Card0"
    Monitor "Monitor0"
    SubSection "Display"
    Viewport 0 0
    Depth 1
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 4
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 8
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 15
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 16
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 24
    EndSubSection
    EndSection
    While I was trying to fix this I noticed I was encountering other problems also. For one I found that sometimes dhcpcd times out on booting up and I cant seemt o connect to the Internet on booting. Although I just thought of trying a static IP and I'll post if that helped later on.
    Another problem is I found that I seem to get the following error randomly. Pressing ctrl + D after this just restarts the machine.
    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>
    Finally, while I boot up I noticed that it says "Mounting root partition as read only   [DONE]"  Is the root partition supposed ot be mounted as read only ? Attached my fstab just in case it is needed.
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    none /dev/pts devpts defaults 0 0
    none /dev/shm tmpfs defaults 0 0
    #/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
    #/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
    #/dev/fd0 /media/fl auto user,noauto 0 0
    /dev/sda3 /boot ext3 defaults 0 1
    /dev/sdb1 / ext3 defaults 0 1
    /dev/sdb2 swap swap defaults 0 0
    /dev/sdb3 /home ext3 defaults 0 1
    As you can see I'm quite new to Arch Linux so any help would be deeply appreciated.
    Last edited by FilledVoid (2009-09-11 16:28:28)

    Thank you for all your suggestions . I tried replacing the ID to Card0 but it didnt seem to fix it . However on the bright side I checked more threads on the forum and found some that helped out . :)
    http://bbs.archlinux.org/viewtopic.php?id=75070&p=2
    http://bbs.archlinux.org/viewtopic.php?id=72788
    http://bbs.archlinux.org/viewtopic.php?id=76938
    I copied the xorg.conf file from the third link and just made minor changes to it like removing all the resolutions I didn't need and now its working fine :).
    Now Im just stuck with two problems. One is the following message which appears randomly.
    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>
    ******************* FILESYSTEM CHECK FAILED *************
    * Please repair manually and reboot. Note that the root *
    * filesystem is currently mounted read-only. To remount *
    * it read-write type: mount -n -o remount,rw / *
    * When you exit the mantenance shel the system will *
    * reboot automatically. *
    A thread about the same can be found http://bbs.archlinux.org/viewtopic.php?pid=295384 but there isn't a solution on it. 
    The second is the intermittent problems with the Network being setup. Sometimes when I boot up it just says dhcpcd timedout and I won't be able to connect . However I can connect on another machine at the same time.
    Took a look at the drive in question with gparted and it shows the below information:
    /dev/sdb1 ext3   /   32.59 GB    4.92 GB   27.68 GB  boot
    By any chance is any of the above information relevant :x ?

  • Windows 7 / Arch Linux Dual-Boot - win7 keeps changing the boot flag!

    Greetings!
    Its been a long while since I had to dual-boot with windows on the same machine.
    I 've installed windows 7 and then arch linux and installed GRUB on my sda1 where the /boot partitions is located at.
    I've managed to boot into arch successfully and later into windows also successfully.... but when i tried to boot into arch again I wasn't greeted with the typical GRUB boot screen... grub was ignored completely and win7 booting began as if it was the only OS in my hard drive.
    I've used the gparted live cd and realized that the boot flag has changed from my /boot partition (sda1) to my windows partition (sda2). I've changed it back and I was able to boot into arch again. but when I rebooted to win7 and then to arch the same thing has happened. The boot flag keeps changing whenever im rebooting into windows making impossible for me to boot with GRUB unles I manually change the flag again.
    I haven't installed GRUB into the MBR because I hear  it is a bad practice when you have a windows OS also installed (something with service packs not being able to install, among other things). I also don't want to use the easyBCD method to boot arch using the win7 loader.
    here is the partition scheme on my 500gb sata drive :
    /dev/sda1      /boot                 250mb    (primary)
    /dev/sda2      windows 7 ntfs   100gb     (primary)
    /dev/sda3      swap                  4gb        (primary)
    /dev/sda5     /                       16gb        (logical)
    /dev/sda6     /var                   8gb         (logical)
    /dev/sda7     /home               the rest of the hd space   (logical)
    What am I doing wrong and how do i prevent the boot flag from changing?
    Thanks in advance for any help you can give me!
    Last edited by kamigr (2010-01-12 14:35:07)

    naequs wrote:
    bumping this because i have the EXACT same problem !
    however i installed grub to sda1 because i didnt want my installs to mess with each other  (not that ive had any problems with grub in mbr though...) .
    this just looked cleaner to me.
    if anyone has figured out how to prevent windows from automagically changing the bootgflag, id like to know !
    but maybe this is a question more suitable for a windoze forum
    tia
    /edit: seriously, ive been searching the net for some time now, including irc chans and there seems to be no solution to this ! all threads similar to this just end dead !
    i hate how windows claims to own my computer!
    1. don't necrobump
    2. as mentioned in the thread, just install grub to mbr and chainload windows. It works just fine and is the easiest way to get it working reliable.

  • About the future of Arch Linux Newsletter.

    Hi,
    As you may have noticed, I have taken the job to make the Arch Linux weekly newsletter a possibility again. I the time I've been doing them, we speak of about 3 weeks, I have enjoyed writing them and have received very positive comments from the community that reads them. I would like to thank all of you personally for the support, you are the community and yours are the newsletter. But, as you all may have noticed the newsletter has been in an unchanged format for quite a long time. I mean, I just added the Humor section thats all, I know there is an email address to which you can all write your suggestions to, but I find people communicate and express themselves better on the forums.
    So what I will ask of you, dear readers, suggestions of sections I should add/remove/edit, I will appreciate your constructive criticism in general. Express your thoughts in this thread to help me make a better more quality newsletter.
    In other news, the newsletter won't be weekly no more, as Jason Chu and I have talked about, is easier to maintain a 2 time a month newsletter than 4 times a month, also the Arch Linux Developers/Community doesn't make that much noise as the other major distributions, we tend to be a bit quieter. The bright side is, the newsletter will be written with more time at hand, more stuff to write about, and will contribute to a better quality overall.
    What has been suggested so far and I will work out on the next issue of the newsletter?
    * Change the Bugs stats to not reflect the overall percentage but the actual bugs opened and closed that week.
    As Roman Kyrylych points out: "They show a summary of status field "Progress" in open reports, but in 99% this field goes straight from 0% to 100%, so the overall number is always very low and doesn't really show anything".
    So I wait for your suggestions as well.;)

    Hi again,
    I ask for your opinion again on the subject of the stats section in the newsletter, Do you find this an important part that should stay there?
    I mean, this is going to be the most tedious, time-taking and in my opinion useless section I will have to write for the newsletter. I do want to bring a high quality newsletter but I feel this part doesn't contribute to the quality of the newsletter at all, Why?
    * Newsletters that include this section are mostly from distributions that has point releases and not rolling releases.
    * The number will always increase with minimum decrease because as a rolling release system Arch Linux is every package keep being updated everyday to newer versions, opening and closing more bugs by itself.
    * People might not be interested in how many bugs are and how many are closed every week, since this numbers aren't even provided on the bug system itself.
    Please give this a consideration and tell me your opinions.

  • Installing/using Arch linux in Parallels on Mac OS X Lion MBP Retina

    I am having a problem where I can't install or use Arch Linux as the same error always crops up at some point or another.
    loading user-specifide modules [busy]
    pc_ich: RCBA is disabled by hardware/BIOS, device disabled
    pc_ich [some random numbers]: I/O space for GPIO uninitialized
    BUG: soft lockup -- CPU#0 stuck for 22s [kworker/u:0:5]
    Thanks for any ideas.

    I am pretty sure that Linux has some known serious issues with thre retina Macbook as well as some of the new Airs.
    See this thread, it may help: https://bbs.archlinux.org/viewtopic.php?id=144255&p=1
    Edit: Sorry i didn't read the "Parallels" in the title.  Though I am not familiar with parallels, so I am not sure what kind of system it is actually trying to emulate.  What happens if you use something else like virtualbox or some other free virtual machine software.
    Last edited by WonderWoofy (2012-09-27 03:18:07)

  • Please suggest non-English articles for Arch Linux Press Review

    Good day,
    If you know of any non-English language articles or reviews about Arch Linux, please contribute them to the Arch Linux Press Review wikipage. The page is found here:
    http://wiki.archlinux.org/index.php/Arc … ess_Review
    Feel free to edit the page directly, or post article suggestions in the thread of this topic.
    Please feel free to make any corrections needed to the non-English article section of the webpage.
    Translating and posting this message to other language based forums is appreciated.
    Thank you,
    Luke Seubert

    Don't double post....
    Replies go here: http://bbs.archlinux.org/viewtopic.php? … 09#p556409

  • Arch Linux Rocks! A Follow Up

    A week and a half ago, I took the plunge and installed Arch 0.7.1 (Noodle). I posted a thread here on that day called "And the Odyssey Begins - First Impressions of Arch Linux".
    It is a week and a half later, and I am a confirmed believer. I have retired my previous distro (SuSE 9.3) and use Arch exclusively. Noodle is amazing. It is the FASTEST linux distribution I have ever used: fast in terms of boot time from grub prompt to full desktop and fast in terms of the speed with which applications launch and run. Everything is significantly, noticably faster than it was under SuSE on the same hardware. Truly amazing.
    But that is not all. By and large, everything I have tried on Noodle JUST WORKS! All my physical devices JUST WORK, including the usually troublesome ones like my webcam. I have had almost no issues getting everything up and running. I had a brief issue with sound (my fault - didn't add my non root user to group "audio"), but that was it.
    ...and multimedia - it all JUST WORKS. I can't tell you how much trouble I had to go to in order to get other distros to do basic stuff like play MP3s or MPGs. In Noodle, I installed XMMS, MPlayer and gxine, and all my media JUST WORKS. Again, amazing.
    ...and then there is package management. Why can't everyone have a package manager that is as simple, fast and effective as pacman? pacman is a real winner! ...not to mention the impressive selection of packages that are available. I have been able to find almost everything I normally use in the repository. The few I haven't been able to find I have been able to build from source easily, without all the usual fussing about.
    Arch is the linux I have been looking for. It is fast, stable, capable and supported by a great bunch of folks here in the forums. My hat is off to those who created and maintain this great distro, and to everyone here in the forums. I have found a new home.

    Can you expand on that? What does qpkg do?
    I had one bad experience with AUR and haven't gotten back to it yet. I followed the instructions I found somewhere (Wiki, forum, somewhere - don't remember any more), dowloaded the package, and attempted to build. My screen flooded with compile errors and I just gave up - I figured that if I had to fight with compile errors, I might as well do it with the good 'ol
    ./configure, make, make install
    route, rather than adding the complexity of a (to me) unknown build system on top of it. So far, I haven't needed to go back. Arch is *so* good (i.e. follows normal standards, everything is where it should be) that pretty much everything I have tried to build from source the usual way has worked like a champ.
    I think it was qamix that I was trying to build this way, by the way. Eventually I built it myself from source via the ./configure, make, make install route. There were *lots* of compile errors this way too, but I fixed them all and got it to build. Perhaps the version in AUR was suffering from the same problems.
    If qpkg is in AUR, and it sounds interesting, perhaps I will give this a whirl again.
    Meantime, to get back on topic for a moment, it is a few weeks later now since my Arch install, and I remain incredibly impressed with it. The best part is the speed. I feel like I've gotten a new CPU that is twice as fast. Arch not only ROCKS, it RACES!

  • Arch Linux Gallery

    I am proud to present the re-opening of the new Arch Linux Gallery!
    The Arch Linux Gallery is a site dedicated to screenshots of (guess what?) Arch Linux. It is meant to be a repository for screenshots, configs, artistic creations, and anything else Arch Linux-related.
    When registering, zenphoto will provide you with your own personal album to which you can upload images and configs.
    The only caveat is that, for now, it only supports .txt for text objects. So when uploading configs, they should be of .txt extension. Extensions need to be added, and I'm not sure of all the extensions that will need to be added, so if you want to request an extension to be added please post here and let me know.
    Gallery searching, ie. filtering for only Openbox, is tag-driven, so make sure to tag photos with relevant information. Once some content starts being uploaded I can begin to create some dynamic albums of common content. I also plan to have a dynamic album for each month (like the screenshot threads) but I still need to figure out how to make that possible.
    Special thanks to dennizjov who provided the server and domain, Ghost1227 for the wonderful logo, and the zenphoto devs, an amazing piece of software found over at http://www.zenphoto.org/
    Here's the link, and have fun!
    http://www.archlinuxgallery.com/
    Last edited by kagutsuchi713 (2009-10-24 00:47:38)

    Is nothing being displayed my fault or the site's fault?
    I go to gallery, and it lists some names with question mark looking graphics beside them.  Then I click the name, and it comes to a page that looks like I should be expecting to see a picture but has nothing.
    Oh, and if I click archive after clicking a name, I see:
    Notice: Undefined variable: typeGallery in /home/web29205/domains/archlinuxgallery.com/public_html/themes/arch/archive.php on line 14
    Either way though, thanks for picking this up and running with it.  It looks like a great idea!

  • Arch Linux 0.7.1 - my feedback

    please read the post before vote
    Well, I've used Arch linux for many months in late 2004 / early 2005 and then I've switched to Ubuntu...
    some days ago I've installed version 0.7.1 and updated it with pacman -Syu
    I've seen a lot of improvement since the last time I used it and I was near to think "ok let's switch back to Arch" until I found I that thing I really hate  :!: is still here..
    You can't install old versions of some packages. For example, kernel.. or.. php (ok there is one in Aur that is maybe "too" old) and mysql..
    in the php/mysql example it's true that version 5 is the latest one but they (at least php) still develope the 4.x version for security and many server still have it and also many scripts supports only php4 and 5.
    also, as I am a php developer, I need to test scripts with old versions.
    but as I said this is just an example. I think that while you can't think to have a big repository of binaries it would be great to be able to install old versions via source.
    and recompiling software by hand using old PKGBUILDS is a problem case you don't have a tool that tells you wich packaged were "aligned" with wich.. I mean.. the new php works only with the mysql5 extension so even if you build mysql by yourself it won't work with php.. and so on for apache..
    anyway.. if a user is able to block a package and prevent the automatic update he should also be able to use the non-latest version of it.
    I know that arch is a bleeding edge distro but this shouldn't mean that you have only the bleeding things. (see gentoo for example)
    Another thing that will help a lot in my opinion is to have in the wiki 2 lists:
    - one very detailed with available daemons and their use.. for example.. ok.. fam is the file alteration monitor.. but why you need it and wich are the main programs that takes advantage from it and what happens if you doesn't run it? and so on for hal, etc. ..
    - one list with all available standard groups that tells user to wich group subscribe in order to be able to performe a specific action
    imho this 2 lists will help the (new) user understand better what is doing and why The arch philosophy of "do it yourself  and learn doing it" is great but have to be encouraged, and in fact there already is a very good documentation.
    Just my 2 cents. And sorry if some one else already said this before; in this case take my post as an underline mark btw.. I'll attach a poll to it.
    bye,
    Giovanni.

    iphitus wrote:To me this thread looks more like "i dont want to make a second package for myself, so let's get the devs to do it".
    hmm.. this sounds a bit offenisve to me. Cause I don't actually need that packages as I'm not using Arch as main distro. This post was meant to give a feedback..
    iphitus wrote:Especially as there isnt a huge demand for such a package, and you are most likely to be one of a very small minority to use that duplicate package.
    ok I agree with this. but from my point of view it is because users that needed it too already switched to another distro..
    and this leads us to this:
    tomk wrote:I voted "No, there is no need", because I think this is simply an indication that Arch is not the right distro for you - it doesn't meet your requirements.
    Imho, the point is that Arch have a lot of great features. The one I'd like to have is a feature that I think will just increase the number of great features Arch already have and will make Arch the right distro for more users. So users that switch to another distro will lose a lot of features that they like to get one or two that they need..
    tomk wrote:This "thing that you really hate" is still there because firstly the Arch devs, and secondly Arch users, have not needed to change it. If you want to work "from within" to change that, with polls like this, feature requests, etc, I wish you the best of luck, but I think your poll result so far should tell you something about the support you can expect.
    the poll was mainly for myself to get an idea of the users opinion not to change the things. And as I said it is not a change from my point of view, but just a new feature. About Arch devs I agree but about users I don't.. how you can say it if you say to me that I should change distro? In this way people that thinks like me will always remain a minority in arch community. And I don't think that having a old version of a "core" package would be against the Arch philosophy.
    tomk wrote:Finally a general point, and this applies to wiki entries as well - you will get a better response if you do something, and then ask "what do you think?" instead of asking "Why doesn't Arch do this?"
    I did it for the software thing with the poll and anyway also for the wiki I didn't wrote it but I thought it was clear.. For the wiki I posted my idea and there was no need for the question "what do you think" cause is a discussion forum Also please keep in mind that I wrote the original post in late night and that I'm italian so my english isn't so good  :oops:
    anyway.. thanks for the tip about subit a feature request and for your answers.
    bye,
    Giovanni.

  • Arch Linux (and general Linux) graphics and artists community

    TheBodziO has started a discussion about the (Arch) linux graphics community. That gives me an idea. It would be nice to create an online (sub)community dedicated to graphics, DTP, and photography centered around Arch Linux. For now, I can only offer some ideas, my experience in graphics and DTP, and lots of hosting space on a non-dedicated server.
    The ideas for the (sub)community:
    * an open forum for discussion, not just Arch-related but 'graphics on Linux' in general
    * a wiki for Linux artists
    * a gallery (d'oh!)
    * an Arch LiveCD for graphics artists
    * a dedicated graphics repository
    If you have suggestions and/or are interested to participate, please post below.

    For start I want to say that I'm content that the new thread have been started to discuss the matters of cooperation of designers and developers communities. It's a good sign.
    As foxbunny said the whole idea is *much* more than another art repository. I thought about creating a common ground - a meeting point - for both developers and designers. Developers have the skills to code. Designers have needs and ideas how to speed up/ease their work. Developers create tools that designers use and designers provide feedback and ideas. What I think free software world lacks is an organized way to provide the pan-project and pan-distro connection between these groups.
    To illustrate the whole thing on a simple example: let's assume that I'd love to have a possibility to lock some operations on elements of my project with password. It's because my work will be given to someone else who will be responsible for placing a text in proper places on the design. I don't want to see him to move or delete something accidentally. It's possible that also some other designers will find that feature useful too. Then maybe some developer will be willing to implement that. The trouble is, that if I propose that feature and encourage its implementation in gimp, I would have to repeat the same process for scribus for example. But the idea is common. I want to state it once and see who will catch the bait . To some extent it will promote deeper integration between different projects.
    Today graphic designers have the tools for editing vector graphics, raster graphics some page design tools. These tools often use the same methodologies! There are bezier curves in gimp, inkscape, scribus... whatever yet they are implemented redundantly. Perhaps thanks to one thoughts sharing panel it will be possible to come with some common solutions. Maybe some common libraries or platforms will emerge in time? I think that mentioned meeting point will keep us close to unix philosophy: do it for a single purpose and do it well. In other words I think that it will allow us to have powerful building blocks on which something even better than today state of the art apps could be build.
    I want to at least start some discussion about the issue. Hopefully this will be only a beginning.
    First I want to ask: do you believe that a subcommunity of archers that would be responsible for communication between the developers and designers would be useful? If so then we could more precisely state our goals and code of conduct.
    Designers experience is of the essence if we want to make free software usable for demanding "art" community.
    Last edited by TheBodziO (2007-10-28 20:35:15)

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

  • Arch Linux and Splashy, a big update

    edit 2:
    If you don't want to build from sources have a look at this post: http://bbs.archlinux.org/viewtopic.php? … 03#p371403
    edit:
    UPDATED LINK:
    http://slexiw.netsons.org/files/splashy-stuff7.tar.gz
    About me:
    I'm a professional developer (mainly c/c++) with 10 years of development experience. I've never programmed in bash before so this is my first experience. My Linux knowledge isn't good either but i learned a lot thanks to Arch Linux.
    About the thread:
    I need a boot splash for a mini-pc I'm building and i want, of course, use Arch Linux. The current status is pretty depressive, initscripts-splash are outdated and there is no real support for user-mode boot splashing system (like splashy).
    A few suggestions (IMHO) for the Arch Linux developers:
    -Integrate the splash system in the official initscripts. If you write a wrapper like start_daemon and stop_daemon to be used in /etc/rc.multi and /etc/rc.shutdown, we can limit the changes to just /etc/rc.d/functions and at least the initscripts-splash will be more maintainable and the whole code more clean.
    -Patch killall5 to add the support to ignore pids. The patch is really small and the one used by Ubuntu is http://patches.ubuntu.com/s/sysvinit/ex … ids.dpatch. There is a package in AUR that uses a different patch: http://aur.archlinux.org/packages.php?ID=16445. I tested it and so far it worked fine, no problems to be reported.
    Why do we need a patched killall5? Splashy gets killed early during the shutdown process and the whole purpose of having a splash system is defeated. Currently Splashy cannot handle the reboot/shutdown.
    Enough talking, now back to the real stuff. I've modified the initscript-splash package (completely rewritten) and the splashy package (almost completely rewritten).
    I've also written a new package to support splashy themes. I'm using these packages for my system and i never had any problem so far.
    initscripts-splash:
    Rewritten to fit my needs for Splashy. Based on initscripts-2008.05-1 (in testing, if you are not using the testing repo you should better wait till the package hits core).
    It only supports MY Splashy package, no other splash system is supported, not even the "old" Splashy package from AUR.
    splashy:
    Based on the great work done by the maintainers and the contributors of the package in AUR. A lot has been rewritten and it's actually a lot different.
    splashy-themes:
    Simple package with just 1 theme (for now), depends on archlinux-wallpaper and uses a little hack to use the wallpapers provided. I will provide new themes as soon as i have time.
    Splashy now supports:
    Progress bar
    Text output
    Shutdown/Reboot
    Still working on resume/suspend and "verbose on error".
    Installation tutorial:
    -Download, compile and install sysvinit-mod from aur: http://aur.archlinux.org/packages.php?ID=16445
    -Remove your old initscripts or initscripts-splash package, remember to back /etc/rc.conf and /etc/inittab before.
    -Download, build and install initscripts-splash from http://slexiw.netsons.org/files/initscr … ash.tar.gz
    -Download, build and install splashy from http://slexiw.netsons.org/files/splashy.tar.gz
    -Download, build and install splashy-themes from http://slexiw.netsons.org/files/splashy-themes.tar.gz
    -You may want to restore your old /etc/rc.conf and /etc/inittab now.
    -Add SPLASH="splashy" to the end of /etc/rc.conf.
    -Edit /etc/splashy/config.xml to select the theme you want (to list the installed themes do "ls /usr/share/splashy/themes/", use the directory name as the theme name).
    -Add the "splashy" hook to /etc/mkinitcpio.conf (mine is after v86d and before autodetect)
    -Rebuild your initramfs: mkinitcpio -g /boot/kernel26.img
    -Add "splash" to the kernel command line, if you are not using uvesafb (v86d hook) add vga=791 too. You should also add "quiet".
    If you are still confused follow this guide: http://wiki.archlinux.org/index.php/Splashy
    Looking for suggestions, bug reports and patches!
    Thank you for reading this, you've done what i couldn't do, i can't believe i wrote all that cr*p.
    Last edited by lexiw (2008-05-29 15:28:49)

    phrakture wrote:
    lexiw wrote:-Integrate the splash system in the official initscripts. If you write a wrapper like start_daemon and stop_daemon to be used in /etc/rc.multi and /etc/rc.shutdown, we can limit the changes to just /etc/rc.d/functions and at least the initscripts-splash will be more maintainable and the whole code more clean.
    Now, we've gone through this a couple of times, and I don't actually want to integrate splash SPECIFIC stuff in the initscripts.
    However, we have the ability to override functions used by the initscripts. All we need to do is extrapolate out the pieces that you would need so that you can override them.
    So, if you would be willing to provide a patch against git (http://projects.archlinux.org/?p=initsc … ;a=summary) which extrapolates the pieces you need, we could get that applied, and you simply need to dump your overriding functions in /etc/rc.d/functions.d/. NOTE: submit the patch to the bug tracker, it will get lost if you just post it on the forums.
    Alternatively, you can just tell us (http://bugs.archlinux.org/) which pieces you want extrapolated, but this will take much longer, as I don't think anyone dealing with this stuff is really gung-ho about splash support.
    I will probably provide a patch after i studied the code a little deeper The /etc/rc.d/functions.d/ solution seems the right way to implement it.
    phrakture wrote:
    lexiw wrote:-Patch killall5 to add the support to ignore pids. The patch is really small and the one used by Ubuntu is http://patches.ubuntu.com/s/sysvinit/ex … ids.dpatch. There is a package in AUR that uses a different patch: http://aur.archlinux.org/packages.php?ID=16445. I tested it and so far it worked fine, no problems to be reported.
    Why do we need a patched killall5? Splashy gets killed early during the shutdown process and the whole purpose of having a splash system is defeated. Currently Splashy cannot handle the reboot/shutdown.
    This seems a little silly to me. I'm sure there's 10 or 20 other ways you could implement the same functionality without needing to patch a quasi-critical binary just for splash support. The patch affects all users. Splashy does not.
    I could not find an alternative solution by myself, as i stated my Linux knowledge isn't more than average. If you could provide me some hints I'll be happy to do some further research on the issue and provide a patch. I'll be glad to drop the sysvinit-mod dependency.
    Without the right know-how i just went the "mainstream way" and did what Debian/Ubuntu did.
    Edit:
    I didn't know you could ovveride functions, this will be a great boost for the initscripts-splash project Thank you!
    Last edited by lexiw (2008-05-22 17:35:15)

  • Opinion: What you do NOT like in Arch Linux?

    Hello,
        I saw many topics about opinion of Linux and many like "why you have switched to Arch" but there was no topic about complaints. I know that most of Developers would not like to see topics like that but it is needed to improve this great distribution. If this is wrong section then please move it to "try this" but I was thinking that more people will look here. Let's write every thing, even that which cannot be just improved by Devs. Then let's begin:
    "What do I not like in Arch?"
    - I don't like that Firefox is not branded. I hate that blue globe.
    - I don't like that 'vlc' is not patched for embedded video so it is little annoying.
    - I would like to see [community] repository on main page with the same priority as [extra] because it sometimes happened that new kernel is going to extra and some packages are still not compiled for it. It would be nice if TU's could use [testing] to test their packages.
    - I hate that pulseaudio support is not included in Gnome, I know it is not very stable for many people but for me it is very usable.
    - I don't like that some icons of applications are in bad quality, I just hate that .
    - I don't like that I cannot even use virtualbox on x86_64.
    Now it is your turn to write what you do not like in Arch, guys. If you do not have complaints then you can go on to 'Arch is best' thread and write there how you love Arch but I think everybody will write something.

    Im going to put an end to this thread right here, because it is a waste of time, space, and bandwidth.
    If you want to help improve Arch, post bugs and/or feature requests in the bugtracker, including your proposed solution to the issue you have raised, and ideally a patch that implements that solution. All bug reports and feature requests are read and evaluated by at least one member of the dev team, and assigned to the most appropriate dev for resolution. This process is tracked, so that any progress that is made can be seen, and any required additional information can be requested. In contrast, forum threads such as this are usually not read by the devs, and therefore do not generate the intended action and results.
    The enthusiasm is appreciated - just use it more constructively.

  • [SOLVED] Mount Points In Arch Linux

    When I performed my initial testing install of Arch Linux today, and I was setting up mount points after I finished partitioning with Cfdisk, I was surprised to see that one of the precanned mount points in the Installer was /etc. On OpenBSD, we were warned against having /etc on its own partition, probably because so much important stuff lives there (like the fstab). I was also surprised to see /var wasn't in the precanned list.
    Anyway, my question is, can you really have /etc on it's own partition? And does the exclusion of /var indicate a problem with it being on its own partition?
    Last edited by NerveJessen (2010-04-02 12:50:38)

    NerveJessen wrote:
    It almost sounds like /var was accidently replaced by /etc.
    EDIT: I'll look into the bug reporting procedures.
    http://bugs.archlinux.org/
    There is the FLySpray link, and there is a button at the top right of your screen as well.
    Post back within this thread with your bug report, so other users may vote for the task once it has been assigned to a developer.
    Welcome to Arch!

  • Is there a tutorial for creating Arch Linux logo?

    as the title says, I am looking for a tutorial on how to create Arch Linux logo using either Gimp/Photoshop/Inkscape
    Any links / videos to one would be nice
    Thanks in advance

    You have the artwork, you just are interested in how it was created?
    There is a thread here somewhere about the new logo - Thayer describes the font selection (from memory), but I don't recall any detail about the icons themselves.
    You could always just work from the originals with trial and error...
    http://www.archlinux.org/art/

Maybe you are looking for