Tux in Arch

I really like the way Arch keeps the whole system clean and stays very close to mainline overall I think Arch is great. But there is one cosmetic detail I really miss.
And that's the fact that even though Tux is imho one of the best mascots there is and it really is a symbol for the Free Software world (GNU would be the original one but it's simply not cute enough), is nowhere to be seen in Arch, which is especially a pity with the boot process, while I really like the fact that Arch uses a text boot rather then this nonsense boot splash stuff that not only looks eerie but also makes absolutely no sense from a technical point of view.
That Tux is an awesome mascot has become the clearest to me when I once found out that some female friends used to have a Tux picture in their photo albums in the social networks, so I propose that Tux should be added somewhere in Arch so that everyon sees it's a Linux (I mean it has linux in it's name so don't tell me it's more then just the Kernel and might even once run on a *BSD Kernel).

Spacenick wrote:Actually Tux as it is in mailine is absolutely not a classical boot logo. It's jsut sits at the etch of sthe screen hiding nothing during the boot process.
Not to continue the debate [he said, continuing the debate], but my objection is not that it obstructs anything, but that it's pointless and frivolous.
Spacenick wrote:And, I think it should be there because the Kernel developers have chosen that this would be good and because I think Arch with it's philosophy of keeping things vanilla should honor the linux kernel they way the kernel devs wanted it to be.
An interesting point. Though I'd still end up disabling it no matter what it was.
Spacenick wrote:Actually I don't think Arch overrites it with an Arch logo, have never seen an Arch logo where the Tux is with hand built kernels,
I believe that's *because* you're using a hand-built kernel. The logo is embedded into the kernel image - it's not a separate entity in the filesystem. From a quick glance at the patch file (patches for various versions located here) used by the Arch package's pkgbuild, it overwrites the .pbm logo as it exists in the kernel source tree.
// edit - clarity
Last edited by Peasantoid (2010-04-07 17:28:00)

Similar Messages

Tux, Tux linux, Arch Linux, T-shirt artwork.

He he sounds really easy till you realize you need 10" by about 11" inch prints with about 600px res resulting in huge files and load times. Anyways I am on a disability and run a small Tux Linux Artwork Swag shop and here is some of the artwork. I am working on a large tux logo with small Arch Linux writing on the side but still in the planning stages.
Concept proof.
This is a post about the swag shop on this forum
http://bbs.archlinux.org/viewtopic.php?id=79807
Last edited by TomWitko (2010-06-11 03:15:58)

xc1024 wrote:Can I use the grafitti logo for a wallpaper? http://witko.ca/image-shack/tux/archlin … -shirt.png
The grafitti logo wallpaper is Streetart Arch Linux from kde-look.org the owner said I could use it for t-shirts but you would have to ask him.
http://kde-look.org/content/show.php/Ar … ent=102620
You could send him a pm from there thats how I got in touch with him. He has some real nice artwork

Place to get Tux/Arch modkey stickers and stickers to cover dell logo

Hello,
So my laptop is en route, and I'm looking for a sticker to cover the modkey (windows key) and a sticker to cover the dell logo, plus case badges if I can get them. Tux or arch would be great. Does anyone know of a place where I can get all of those from the same place?
I found www.unixstickers.com, but they require payment by Bitcoin or PayPal, of which I have neither ( ).
I found circular 1.5" Make-your-own stickers on Zazzle and Tux case badges and modkey stickers on ThinkPenguin, but as I said, I would like to get them all from the same place.
Where can I get modkey stickers, case badges, and dell covering stickers from the same place?
Thanks,
Wesley.

Oh, I didn't notice that they had a Zazzle store, I thought it was just what was on the main page.
Cool, but I might end up getting more than I was planning by accident
Although that wouldn't help me with the stickers to cover the windows logo on my modkey, since the stickers are 1.5" at the smallest.

Mounting USB drive as regular user (with ntfs-3g)

Hello. First of all, I not asking to do the homework for me, rather is someone can help me understand why I can't get this work.
I spent the last night trying to figure how mount an USB drive as a regular user, using ntfs-3g. I read the related wiki entries and researched quite a lot in the forums. I came up with this:
fstab:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs nodev,nosuid 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/sda1 / ext3 defaults,noatime 0 1
/dev/sda2 /home ext3 defaults,noatime 0 2
/dev/sda3 swap swap defaults 0 0
/dev/sdb1 /mnt/usb ntfs-3g noauto,uid=0,gid=0,noatime,umask=000, 0 0
I created a ntfsuser group, added my user to that group and trim permissions to the ntfd-3g executable (link in this post). That allows me mount the partition as root and read/write as regular user. It works, so (i think) not big deal here.
However if I add user to the mount options the following error shows up:
Mount is denied because setuid and setgid root ntfs-3g is insecure with the
external FUSE library. Either remove the setuid/setgid bit from the binary
or rebuild NTFS-3G with integrated FUSE support and make it setuid root.
Please see more information at http://ntfs-3g.org/support.html#unprivileged
What bugs me the most is I don't understand why I can't mount as regular user when the user option is set in the fstab. Shouldn't that allow regular users to mount and unmount? Is not like that I'm mounting and dismounting USB drives every 5', but I would like to get this done because I know it can be done
Sorry for asking such trivial question, but I sense that I'm missing something really stupid and I just can't figure what it is

Beware of the double post! (+1)
Ok, I decided I'd get this to work, although the method and the implications it could have might not seem pretty to some. There are certain conditions for a user to mount any ntfs volume with ntfs-3g, I will name them here:
1. ntfs-3g with integrated fuse support. You'll get this by:
1A. Removing ntfs-3g and fuse from your system if you have them installed as separate packages, so do this as root:
pacman -Rn ntfs-3g
pacman -Rn fuse
Now you can install the new package.
1B. Getting a modified version of the PKGBUILD found in that AUR link previously mentioned by me, here's mine:
# Maintainer: Gula <gulanito.archlinux.org>
# Slightly modified by anderfs
# Don't forget to setuid-root for the ntfs-3g binary after you install this
pkgname=ntfs-3g-fuse-internal
pkgver=2010.5.16
pkgrel=1
pkgdesc="Stable read and write NTFS driver (whit internal fuse suport)"
url="http://www.tuxera.com"
arch=('i686' 'x86_64')
license=('GPL2')
depends=('glibc')
conflicts=('ntfs-3g')
makedepends=('pkgconfig')
options=('!libtool')
source=(http://www.tuxera.com/opensource/ntfs-3g-${pkgver}.tgz
http://aur.archlinux.org/packages/ntfs-3g-fuse-internal/ntfs-3g-fuse-internal/25-ntfs-config-write-policy.fdi)
sha1sums=('895da556ad974743841f743c49b734132b2a7cbc'
'200029f2999a2c284fd30ae25734abf6459c3501')
build() {
cd "${srcdir}/ntfs-3g-${pkgver}"
ac_cv_path_LDCONFIG=/bin/true ./configure --prefix=/usr \
--with-fuse=internal --disable-static || return 1
make || return 1
package() {
cd "${srcdir}/ntfs-3g-${pkgver}"
make DESTDIR="${pkgdir}" install || return 1
ln -s /bin/ntfs-3g "${pkgdir}/sbin/mount.ntfs" || return 1
install -m755 -d "${pkgdir}/usr/share/hal/fdi/policy/10osvendor"
install -m644 "${srcdir}/25-ntfs-config-write-policy.fdi" "${pkgdir}/usr/share/hal/fdi/policy/10osvendor/" || return 1
Save this as PKGBUILD, preferrably in an empty directory so it doesn't clutter things up when you build it.
1C. Now go to the directory where you saved it and do this as a regular user:
makepkg PKGBUILD
After that's done, you'll get a package called ntfs-3g-fuse-internal-2010.5.16-1-i686.pkg.tar.xz, or something similar.
1D. Install that package as root:
pacman -U ntfs-3g-fuse-internal-2010.5.16-1-i686.pkg.tar.xz
If all went well you now have ntfs-3g compiled with integrated fuse support.
2. The ntfs-3g version must be higher than 1.2506, this is already covered, the package installed from AUR matches this requirement.
3. The ntfs-3g binary must be set to setuid-root, to accomplish this you shall do the following as root:
chown root $(which ntfs-3g)
chmod 4755 $(which ntfs-3g)
I used 4750 instad of 4755, I guess that last bit can be a matter of personal taste as long as it isn't something obnoxious like "7".
4. The user must have the right access to the volume. Okay, this is the ugly part, volumes are owned by root and managed by the disk group with permissions brw-rw----, this means you have to add any users you want mounting this volume to the disk group.
4A. So, do this as root:
gpasswd -a [user] disk
Where [user] is obviously the name of whichever user you're adding to the disk group, do this for any user you want mounting this volume.
Any users currently logged in will have to log out and back in for these change to take effect, this most likely includes you.
4B. Now that you logged back in, try this:
groups
One of the groups listed should be disk, if it's not there you didn't completely log out of all open sessions.
5. The user must have the right permissions/access to the mount point. For a user to be able to mount something to a mount point, that user needs to have read permission (pretty self-explanatory), write permission (so the user can make any changes to the sub-structure of the mount point), and execute permission (so the user can change-dir to that mount point) to it. Mount points can be anywhere, so this really depends where you're mounting.
In my case, I'm mounting these volumes on certain directories under /mnt/, for example /mnt/example. If you're mounting stuff there, you might as well take advantage of the fact your "mounting user" is already in the group disk, and do the following as root:
chgrp disk /mnt/example
chmod 774 /mnt/example
Now users in the disk group will be able to manage these mount points.
6. Mount it. That's it, you should now be able to mount ntfs volumes as an "unpriveleged enough" user. Here's an example of what you'd have to put in /etc/fstab:
UUID=XXXXYYYYXXXXYYYY /mnt/example ntfs-3g noauto,noatime,user,uid=0,gid=6,fmask=137,dmask=027,rw 0 0
uid=0 means root will be the owner of this mount-point and anything in it after it's mounted. This is due to the fact that even though users might own their mountpoints and have rwx permissions on them, you might still not want them to write to the mounted ntfs volumes. Remove this if you want them to be able to write to the volume.
gid=6 means this will be managed by the disk group in my system. Perhaps the disk group has a different id in your system, run "id root" to find out, as root usually is part of this group.
fmask = 137 means the owner (root) can do anything with files in this volume except executing files. Group members (disk) can only read files here, not create or execute them. And other users can't do anything in this volume.
dmask = 027 means the owner can do anything with directories (execute here is needed to chdir), users can't write directories but they can read or execute in them (once again, needed by 'cd'), and finally other users still don't have any access.
You can use whichever fmask and dmask makes sense to you, or use an umask instead.
Last edited by anderfs (2010-07-15 11:34:48)

AS5920G sound problem ....

With my sound card, the sound is too low and microphones do not work.
[ubermensch@arch-tux ~]$ sudo lspci -d 8086:284b -vv
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
Subsystem: Acer Incorporated [ALI] Aspire 5920G
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 22
Region 0: Memory at f3500000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [60] MSI: Mask- 64bit+ Count=1/1 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [70] Express (v1) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
ExtTag- RBE- FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
LnkCap: Port #0, Speed unknown, Width x0, ASPM unknown, Latency L0 <64ns, L1 <1us
ClockPM- Surprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed unknown, Width x0, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
Capabilities: [100] Virtual Channel <?>
Capabilities: [130] Root Complex Link <?>
Kernel driver in use: HDA Intel
Kernel modules: snd-hda-intel
[ubermensch@arch-tux ~]$
[ubermensch@arch-tux ~]$ cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.20.
[ubermensch@arch-tux ~]$
[ubermensch@arch-tux ~]$ cat /proc/asound/cards
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xf3500000 irq 22
[ubermensch@arch-tux ~]$
[ubermensch@arch-tux ~]$ cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.20.
[ubermensch@arch-tux ~]$ cat /proc/asound/cards
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xf3500000 irq 22
[ubermensch@arch-tux ~]$ cat /proc/asound/modules
0 snd_hda_intel
[ubermensch@arch-tux ~]$ cat /etc/modprobe.d/50-sound.conf
alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel
options snd-hda-intel model=auto probe_mask=1
[ubermensch@arch-tux ~]$
[ubermensch@arch-tux ~]$ aplay -L
default:CARD=Intel
HDA Intel, ALC1200 Analog
Default Audio Device
front:CARD=Intel,DEV=0
HDA Intel, ALC1200 Analog
Front speakers
surround40:CARD=Intel,DEV=0
HDA Intel, ALC1200 Analog
4.0 Surround output to Front and Rear speakers
surround41:CARD=Intel,DEV=0
HDA Intel, ALC1200 Analog
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=Intel,DEV=0
HDA Intel, ALC1200 Analog
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=Intel,DEV=0
HDA Intel, ALC1200 Analog
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=Intel,DEV=0
HDA Intel, ALC1200 Analog
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=Intel,DEV=0
HDA Intel, ALC1200 Digital
IEC958 (S/PDIF) Digital Audio Output
null
Discard all samples (playback) or generate zero samples (capture)
[ubermensch@arch-tux ~]$
:cool:

What type of sound problem are you having- low sound, static, no sound at all,etc?
Get your Product Number by pressing Fn + Esc key or check the Service Tag attached to bottom, may be under battery.Post it.
******Clicking the Thumbs-Up button is a way to say -Thanks!.******
**Click Accept as Solution on a Reply that solves your issue to help others**

Arch Linux "pacman-enhanced Tux" :)

Hey,
I just wanted to gimp a unique 'start'-button for my fbpanel.. so I inkscaped a 'pacman-enhanced' tux (get it? ) that I'm of course sharing with you folks:
Well.. maybe somebody else out there also likes him

Thanks for the nice feedback! Concerning the art svg upload.. Err.. I just tried.. :oops: so where exactly is art.archlinux.org's 'upload' function?
By the way, Inkscape seems to distinguish 'Inkscape SVG' from 'Plain SVG'. I did not compare the xml and am not yet that much into svg as I'd like to be.. Does someone know the difference? Is it that plain is preferable for web and inkscape formatted files are preferable for editing?

[SOLVED] Arch terminal issues

Having some trouble with my terminal in Arch. I currently have Arch running with i3 and using Terminator emulating xterm. Everything is fine except something is causing the terminal instance to wrap the cursor way too earlier (before the end of the columns) and it wraps back to the start of the line rather than the beginning of a new line. I'm not sure how this would have happened or if there is some option to fix this. It works fine when I have no seperate tiles, adding vertical tiles causes the weird word wrap but horizontal tiling doesn't affect it. It's almost like its trying to programmatically figure out the word wrap point but gets halved with you add vertical tiles
Thanks for any help!
Last edited by mihok (2013-01-29 14:27:04)

Thanks for the direction.
PS1="\[\e[00;31m\][- \[\e[107;34m\]\u@\h\[\e[00;31m\]- ]
|-\[\e[107;31m\] in [* \W * ]\[\e[00;31m\]-|-->\[\e[00m\]"
[- joe@Tux-Box- ]
|- in [* Tunes * ]-|-->

Arch Linux Pumpkin Carving!

After seeing Best Halloween Pumpkin Carvings from Ghost1227's blog, it inspired me to do a unique pumpkin carving this year. Looking through the archive of awesome pumpkin carvings, of course I didn't see Arch Linux (but there was Tux fortunately). So I wanted to make that carving! I planned this days ahead, thinking how the design should be. I did a practice carving before I did this one, which I made several mistakes on. Considering that was only practice, this second one came out much better! Happy Halloween!
Wallpapers:
1280x1024
Last edited by Acecero (2009-10-31 03:24:06)

Well I did two more pumpkin carvings at the last minute before the tricker treaters arrive.
One of them is a taco, because of how much significance tacos have in the Arch community! I hope you like it, I also included the moldy Arch Linux carving as well.
Last edited by Acecero (2009-11-01 02:20:36)

Tux Commander Mounting USB

I loaded Arch with Openbox on my netbook. When I plug in a USB drive, the device does not show up in Tux Commander. The device is properly mounted as I can see it in /media and Thunar recognizes it as well. I have loaded Tuxcmd and Tuxcmd-modules from the repository.
Anyone have any ideas?
Regards
Ronnie

I still haven't found a solution for this issue.
Any ideas?

Installing arch to macbook 2,1

Hi,
I'm trying to install arch (dual boot with OSX) on my macbook 2,1. I've install rEFIt.
The partitions that I have setup are
1 OSX boot partition
2. OSX system partition
3. Archlinux
4. Home
I've arrive at the stage where I need to install the bootloader. But the installer doesn't give the option of installing grub to the Archlinux paritions. So I exit the installer and manually install grub using grub-install /dev/sda3 (which is where my arch partition is).
I still can't boot into arch. There are 2 entries now in my rEFIt menu (OSX and "Boot Legacy OS") How do I setup grub to boot into arch?

So, is rEFIT able to boot GRUB but GRUB is not able to find Arch? Or is rEFIT not able to find GRUB?
For what it's worth, I recently installed Arch on my Macbook 5,1. I also used rEFIT (installed using OS X). My drive partitioning was
/dev/sda1: EFI/OS X boot partition
/dev/sda2: OS X
/dev/sda3: Linux Swap
/dev/sda4: Arch
As you mentioned, the new Arch installer doesn't give you the option of selecting primary partitions to install GRUB (the old installer did). So, when I reached the last stage of the installer (installation of the bootloader), I exited the installer, launched GRUB in interactive mode, and installed GRUB to my 4th partition (where /boot is). (It sounds like you did something similar.) When I rebooted rEFIT discovered that my 4th partition was bootable and displayed a Tux logo. Clicking on the Tux logo launched grub. From there I am able to launch Arch.
Some thoughts:
1. Did you make sure your partition tables are synced? I didn't need to do this, but I've heard of other needing to do this.
2. Did you make sure that the grub was configured properly; e.g. you've specified the correct path to the kernel, etc.
3. Did you try prayer and/or other forms of divinity?

Arch Linux Wallpaper 1080p (Rendered with Blender Cycles)

Title pretty much says it all. I've included the source .blend (Blender) file for those that want to tweek it.
Wallpaper:
Blender Source File: Download

Haikarainen wrote:
This is really beautiful! I read you rendered it using blender, is this available for linux also or is it windows/mac only?
Criticism: Tux stands out too much, doesn't feel like he fits in. I think it would be really cool and better if you worked on his materials, perhaps making him look like a plushy? You know a little furry.
Thank you Yes, Blender works very well on Linux, you can get it from the official arch repo ($ sudo pacman -S blender). This image was modeled and rendered entirely on Arch Linux using Blender + Gimp for some touch-ups (I would never make an Arch Linux wallpaper on Windows/Mac, that's sacrilege ).
Thanks for the criticism as well. Like I mentioned above, I'm working on a couple improvements and different designs already. I'll keep your suggestion in mine while designing them.

Review: Arch: Pros Only, But Not Bad

Saw this on Tux Machines. A very simple review.
distrogue.blogspot: Arch Linux is one of the few distributions to be optimized for an i686 processor- in other words, it's really fast without having to compile anything. It uses a custom package manager called Pacman.
Overall: 3.2/5- A solid distribution, but not recommended for newbies.

fflarex wrote:
I think it was a pretty bad review. It seemed to me like he was trying to review Arch using the same criteria as he would if he were reviewing other distros, without taking into account the different goals that Arch is built on. He acknowledged that Arch was only for "pros," but continued to review it as if it were not. Arch may only be suitable for competent linux users, but as far as similar distros go, Arch still greatly simplifies most administration tasks. I really don't understand how he only gave a 3.5/5 for package management, citing "too many options" and a lack of a GUI. Last I checked, a GUI was not an integral part of package management, but is handled by separate programs (and isn't there a packagekit backend being developed by someone around here?).
Off topic, but I also just have to say that xabbott: you have the coolest avatar ever!
Yea, he reviewed it as a Ubuntu user would review it, not reviewing it compared to EVERY distro or reviewing it on it's own merit. For example:
Slackware = MUCH harder to install, but he didn't mention that
Gentoo = Source-based distro...He said it's harder to install, but i always found it just as easy, perhaps easier if you don't count the time you wait around for it to compile

Arch Linux Newsletter for July 01, 2008, Discussion.

http://archlinux.org/static/newsletters … ul-07.html
Here we are going to discuss any questions, suggestions or random talk about the newsletter for June 04, 2008. Feel free to contribute with ideas and suggestions.
As always thanks for your support,
In the name of the Arch Linux Newsletter Team
Eduardo "kensai" Romero

Misfit138 wrote:
kensai wrote:
Dusty wrote:apparently people are more loyal to the Arch brand than the tux brand. :-D
Those people have not seen an angry penguin charging at them.
I most certainly am. Philosophically, I resent using the penguin kernel.
It's just that Arch is so damn good, it has spoiled me for anything else.
-->Same Here<--
The linux kernel can drive me crazy sometimes...
Hmmm, do you want to start ArchBSD Misfit? That is, FreeBSD + Pacman goodness + updated rc.conf?
I shouldn't have suggested that, I don't have the time to be a dev for anything right now.

Arch does not boot (MacBook Pro, rEFIt)

Several months ago I installed Arch on my MacBookPro (5.1, late 2008) in dual boot with Mac OS X 10.7 (Lion).
Everything was fine until last Friday when, after a forced shutdown, ArchLinux refused to boot and showed me a black screen instead (I use rEFIt).
I followed several forum suggestions, mainly consisting in the reflagging of the boot partition (using both fdisk in Mac OS X and parted in Linux) and in the reinstallation of GRUB. After some work, nothing changed: Mac OS X works fine, whilst Linux still offers me a black screen. After few seconds of black screen, the laptop reboots, and rEFIt shows me the same options.
Does anyone have any suggestion?
Thank in advance for any help I can get
Alessia
This is the output of the rEFIt Partition Inspector tool:
*** Report for internal hard disk ***
Current GPT partition table:
# Start LBA End LBA Type
1 40 409639 EFI System (FAT)
2 409640 200228415 Mac OS X HFS+
3 200228416 201497951 Mac OS X Boot
4 207269888 207464447 GRUB2 BIOS Boot
5 207464448 247463935 Basic Data
6 247463936 271464447 Basic Data
7 271464448 488396799 Basic Data
Current MBR partition table:
# A Start LBA End LBA Type
1 1 488397167 ee EFI Protective
MBR contents:
Boot Code: GRUB
Partition at LBA 40:
Boot Code: None (Non-system disk message)
File System: FAT32
Listed in GPT as partition 1, type EFI System (FAT)
Partition at LBA 409640:
Boot Code: None
File System: HFS Extended (HFS+)
Listed in GPT as partition 2, type Mac OS X HFS+
Partition at LBA 200228416:
Boot Code: None
File System: HFS Extended (HFS+)
Listed in GPT as partition 3, type Mac OS X Boot
Partition at LBA 207269888:
Boot Code: None
File System: ext2
Listed in GPT as partition 4, type GRUB2 BIOS Boot
Partition at LBA 207464448:
Boot Code: None
File System: ext4
Listed in GPT as partition 5, type Basic Data
Partition at LBA 247463936:
Boot Code: None
File System: ext4
Listed in GPT as partition 6, type Basic Data
Partition at LBA 271464448:
Boot Code: None
File System: ext4
Listed in GPT as partition 7, type Basic Data

alesssia wrote:The rEFInd's auto-detection shows a generic Linux OS bootable from a generic HD. When selected, Tux is shown, followed by a grub line (that is "GRUB loading"), then by a black screen. Finally, the rEFInd menu shows up again. This is the same behaviour showed by rEFIt and the reason because I used stanzas.
That description indicates that you were launching a BIOS-mode version of GRUB, and that it failed for some reason that's almost certainly GRUB-specific (bad configuration file, missing modules, etc.).
After playing with the EFI shell I was able of fixing the Arch stanza, finally finding an error that should be expected:
Starting vm-linuz-linux
Using load options root=UUID=e6db22f2-e5bb-4933-bba7-20be86db00if ro quiet initrd=initramfs-linux.img
Error: Unsupported while loading vmlinuz-linux
In fact, I'm using a 32-bit version of Arch on a 64-bit EFI.
That's the problem, then. On a 64-bit EFI, rEFInd can launch 64-bit kernels but not 32-bit kernels.
I’m currently trying to fix my hybrid MBR, but despite all my efforts with the gdisk and the gptsync (in rEFInd) tools I always end up with the behaviour described in the first lines of this post: “Grub loading...”, black screen, then rEFInd menu again
I'm not sure what's wrong with that, but I can say with some certainty that it's a GRUB issue. (That's not to say that the solution is in the GRUB configuration; adjusting the hybrid MBR might fix it, but I'm not sure precisely what to suggest.)
I have no idea about how to proceed. Perhaps (re)installing the 64-bit version of Arch is the only possible solution, but I’m scared by all the painful configuration steps that will follow a fresh installation...
As you suspect, installing a 64-bit version of Arch should fix the problem. For that matter, a 64-bit kernel with 32-bit userland should work OK, although that might be tricky to maintain -- I imagine that pacman would try to "upgrade" you to new 32-bit kernels every now and then. Still, it might be worth giving it a try. If you do, I recommend installing a kernel, initrd file, and kernel modules (in /lib/modules) outside of pacman. Install a kernel that's slightly behind whatever is current in pacman. That way, even if pacman upgrades your kernel, your 64-bit kernel will be untouched. You can then upgrade your kernel manually whenever it's convenient or desirable to do so.
Another option is to install a 64-bit version of EFI-mode GRUB, ELILO, or SYSLINUX, and have it launch a 32-bit kernel. I know this is possible because I've done it in some test installations, but I don't recall offhand which boot loader I used, so I can't promise that all three of the ones I mentioned would work. If you go this route, you'll end up with rEFInd to select OS X or GRUB/ELILO/SYSLINUX, which you can then use to select your Linux kernel (or set a very short timeout to launch the kernel more-or-less immediately). See my Web page on EFI boot loaders for Linux for my thoughts on each of these boot loaders.

Clarification: Installing ARCH to RAID setup in BIOS

So I've been looking in to setting up ARCH on my laptop that has a RAID that's set up in the BIOS. I've been researching on the wiki as well as on the internet but it's only partially answered my question:
With a BIOS enabled RAID do I still need to use tools like MDADM to set up the raid inside of arch, or should arch see its own drive like windows does?
I'm sure I will have other questions as I delve in to installing on a RAID so I will ask what I have now as well:
Reading threads about doing this it seems like I will need a third drive something outside of the RAID to store the RAID configuration if I opt to use GRUB, however syslinux supports RAID during boot, does this still hold true and if so what do I need to do while installing syslinux to have it know that there's a RAID there and configure correctly?
Any other tips on this topic are very welcome.

So, is rEFIT able to boot GRUB but GRUB is not able to find Arch? Or is rEFIT not able to find GRUB?
For what it's worth, I recently installed Arch on my Macbook 5,1. I also used rEFIT (installed using OS X). My drive partitioning was
/dev/sda1: EFI/OS X boot partition
/dev/sda2: OS X
/dev/sda3: Linux Swap
/dev/sda4: Arch
As you mentioned, the new Arch installer doesn't give you the option of selecting primary partitions to install GRUB (the old installer did). So, when I reached the last stage of the installer (installation of the bootloader), I exited the installer, launched GRUB in interactive mode, and installed GRUB to my 4th partition (where /boot is). (It sounds like you did something similar.) When I rebooted rEFIT discovered that my 4th partition was bootable and displayed a Tux logo. Clicking on the Tux logo launched grub. From there I am able to launch Arch.
Some thoughts:
1. Did you make sure your partition tables are synced? I didn't need to do this, but I've heard of other needing to do this.
2. Did you make sure that the grub was configured properly; e.g. you've specified the correct path to the kernel, etc.
3. Did you try prayer and/or other forms of divinity?

Tux in Arch

Similar Messages

Maybe you are looking for