Vmware Player in Arch Linux and RFKILL

Hi,
I am a newbie to Arch Linux, I have installed Vmware player in Arch but it doesn't seem to be running. I have followed the guide in the Arch Wiki. This is the output of the related commands.
[root@swallowed Desktop]# uname -r
2.6.35-ARCH
[root@swallowed Desktop]# vmware-installer -l
No protocol specified
No protocol specified
Product Name Product Version
====================== ====================
vmware-player 3.1.2.301548
[root@swallowed Desktop]# /etc/rc.d/vmware
vmware vmware.d/
[root@swallowed Desktop]# /etc/rc.d/vmware start
Starting VMware services:
VMware USB Arbitrator done
Virtual machine monitor failed
Virtual machine communication interface failed
VM communication interface socket family failed
Blocking file system failed
Virtual ethernet failed
[root@swallowed Desktop]# vmplayer
No protocol specified
xprop: unable to open display ':0.0'
GLib-GIO:ERROR:gdbusconnection.c:2270:initable_init: assertion failed: (connection->initialization_error == NULL)
No protocol specified
xprop: unable to open display ':0.0'
GLib-GIO:ERROR:gdbusconnection.c:2270:initable_init: assertion failed: (connection->initialization_error == NULL)
No protocol specified
(vmware-modconfig:5602): Gtk-WARNING **: cannot open display: :0.0
[root@swallowed Desktop]#
Does anyone know how to resolve this problem?
Besides, I installed Arch on Dell Studio XPS 1640 and I don't seem tobe able to remove the hard block on my Wifi card. I installed all the driver already. This is the output of commands.
[root@swallowed Desktop]# rfkill list
0: dell-wifi: Wireless LAN
Soft blocked: yes
Hard blocked: yes
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
[root@swallowed Desktop]# rfkill unblock 0
[root@swallowed Desktop]# rfkill list
0: dell-wifi: Wireless LAN
Soft blocked: yes
Hard blocked: yes
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
[root@swallowed Desktop]#
I even try to include this inside modprobe but it doesn't work.
[root@swallowed Desktop]# cat /etc/modprobe.d/modprobe.conf
# /etc/modprobe.d/modprobe.conf (for v2.6 kernels)
options ath_pci rfkill=0
options snd-pcsp index=2
options iwlcore led_mode=1
Thank you so much!

vmware products need patching for kernel 2.6.35 - you didn't mention if you did that or not, but if you didn't, that would explain why vmware is not starting.

Similar Messages

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

Have Installed Arch Linux and Xmonad on 2013 15" MacBook Pro Retina

I just recieved the latest stunning MacBook Pro Retina 15" (ME665) released in Feb 2013, couldn't wait to install the Arch Linux 2013.02.01 on it, dual boot with Mac OSX.
I'm impressed by the performance of this device after working with the combo of Arch Linux and Xmonad for several days, everything works out of the box, including touchpad, audio, video, wireless network, bluetooth, etc. Even the apperance of most apps are compatible with the high resolution of Retina display.
Another important thing is the battery life, 5 hours! Program and compile, listen music, download AOSP through Wi-Fi, watch YouTube videos with Flash hardware accelaration on.
For the installtion details, see my long blog post at http://vec.io/posts/use-arch-linux-and- … na-display
-- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --
Last edited by vecio (2013-02-28 02:22:38)

Can you tell me what your /sys/class/backlight/gmux_backlight/brightness and max_brightness values are? This has not worked out of the box for me.

Incorporating both Arch Linux and a package repository onto one DVD.

Dear Arch Linux community,
I would like to tell you a little background information about myself before I start to talk about my actual subject. I know that this part of my message does not belong here, but it is my own ritual to do it like this in my first message in every community. I hope I can make friends with people here and try not to harm this community in any way. Thank you for reading this.
I am a 16-year-old male student from Finland and addicted to GNU/Linux and freeware / open source software. My previous experience with GNU/Linux is fairly large; from thin client Debian GNU/Linux administrator to kernel hacker and software developer. My delight is music, particularly writing and composing my own music tracks which vary from classic chiptunes to acid trance and dance beats. Arch Linux seems to be a great GNU/Linux operating system for me, because I am looking for a GNU/Linux distribution that does not focus on desktop, but rather on simplicity and lightweight solutions. I also do not fear "bleeding edge" software which is a positive point for Arch Linux compared to Debian GNU/Linux. As you can probably notice I have been using Debian GNU/Linux before I considered Arch Linux. However now I am here hoping for a totally new experience from Arch Linux.
Enough with my foreword, I would like to now go back to the actual subject. Usually I use DVD media for GNU/Linux images to have both the installer for the GNU/Linux distribution and the main package repository to make installations faster and to have the possibility for an offline installation. As I see, Arch Linux provides only CD images which are approximately 160MB in size, making me to think about incorporating Arch Linux's "Core" and "Extra" package repositories to fill up the remaining 4GB on the DVD. If the "Core" package repository is already included in the Arch Linux CD image, please forgive my lack of information as this is the first time I have ever entered to the world of Arch Linux.
My question is as follows: Is it possible to incorporate Arch Linux and a package repository onto one DVD while retaining the ability to install Arch Linux from that DVD? If positive, how should I go on to do it?
Thank you in advance!
Last edited by Amplify.EXE (2007-11-09 20:53:44)

No niin, tervetuloa arch-mailmaan.
Ok, I better stop at one sentence before someone gets mad at me :roll:.
To answer your question, yes. It is quite possible to put something like that together, heck I think someone suggested we should distribute those some time, but we decided not to (don't quote me, I'm too lazy to read the archives right now) since in most cases pacman will get the job done will job done with less bandwidth waste, and distributing huge snapshots isn't really too conducive to the whole rolling-release thing.
You might want to check out archiso [1], the install scripts [2], and one of my sample archiso configurations [3] that effectively creates an install CD. Now, keep in mind that archiso isn't the *current* way installers are created, but I think it's much more straightforward to work with than what we're using right now. That said, we currently use archboot to create the CDs, so that may be worth taking a look at as well. There is also a really old installer remastering wiki article [4], though not terribly relevant, you could still use a similar technique to pull apart one of our recent install iso's and remaster it with whatever packages you want. Anyhow, if you'd like help with this, I'd be more than happy to give you a hand (I need some more test-cases for archiso...), or if you look at it and go "gee, this is dumb", don't be afraid to send patches. Just get in touch with me through email, jabber, irc, or whatever.
Good luck
[1] http://projects.archlinux.org/git/?p=ar … a=summary)
[2] http://projects.archlinux.org/git/?p=in … ;a=summary
[3] http://code.neotuli.net/gitweb/?p=archi … stall-conf
[4] http://wiki.archlinux.org/index.php/Rem … nstall_ISO

Share files between Arch Linux and XP Home

Hi, I have an Arch Linux desktop and a XP Home Laptop both connected to a Billion 7401 ADSL Router to get to the internet. If I am using any computer sometimes I have a need to use files from the other one, and from an external HDD connected to the XP laptop. I have been googling for the last 3 weeks but could not find a concrete solution to this issue, maybe because I don't understand much about networking or p2p, and samba. Looks like I have to spend more money on either another computer to be setup as a server or on a router or hub or switch? But I thought my Billion Router is already a router? I wonder if you can please help me to solve this problem or point me to a good link? Thanks a lot.

SSHFS is another more Linux native option for sharing files (and it can be compatible with XP too using special programs).
http://en.wikipedia.org/wiki/SSHFS
http://wiki.archlinux.org/index.php/Sshfs
As I understand it XP Home uses simple file sharing which can be really insecure depending on your needs. Once when I ran a computer with Linux and was needing to set up a samba share I discovered massive issues since (at the time) I was connecting regularly over a shared wireless network among untrusted persons. I ended up looking into using SSH tunneling to overcome the issues associated with XP Home's Simple File sharing and that is when I came across SSHFS.
Whatever you do make sure to read this about XP Home's "Simple Filesharing"
http://www.centerlineit.com/index.php?v … q&Itemid=9
It's important you understand it.
Last edited by davidm (2010-04-12 04:01:34)

Dual-Booting Arch Linux and Windows 7

Hello,
I am attempting to set up a dual-boot configuration with Windows 7 (installed first), and Arch Linux. When I went to install, I read in the documentation that the AIF doesn't support installing GRUB to a separate partition other than the MBR on the drive. I want to install GRUB separate from the Windows MBR so I can use Easy BCD to chainload the two bootloaders (i.e. installing GRUB on /dev/sda5 instead of /dev/sda). I went through the installation process and tried to install GRUB manually via the instructions given in the documentation. But when I went to boot Arch, I was greeted with the GRUB shell instead of the boot menu. What did I do wrong? And is there any easier way to install Arch this way given that I do not want to overwrite the Windows bootloader? I went ahead and wiped the Linux partitions on my drive, so I am going to do the install again once I have some suggestions.
Thanks!

joshuawagner147 wrote:
hyperreal_logic wrote:
To the original poster:
If you want to chainload both Windows and Arch Linux using your preferred boot manager, you'd have to create a separate 'boot' partition when installing Arch Linux. When you are in the Arch installation, create a separate partition of about 500 MB, then create the root partition of whatever size you need, and then create swap partition if necessary. So your HD would resemble something like this: /dev/sda5=boot partition of 500 MB; /dev/sda6=root partition of ## MB/GB; and /dev/sda7=swap partition of (RAM * 2) GB. Then continue with the Arch installation procedure until you get to the end where you are prompted to install a boot loader. Choose GRUB, and install it to the 'boot' partition on /dev/sda5. This will allow you to chainload Arch via Easy BCD. What happens is Easy BCD will pass the message to GRUB on /dev/sda5, and GRUB will then load your Arch root system on /dev/sda6.
I hope this helps. I support your choice in using Easy BCD to chainload Windows and Linux. Software is, after all, about choice. Furthermore, you've presented a good reason to use Easy BCD as the main boot loader, which is to save you from unnecessary tinkering with the GRUB shell or Live CDs and whatnot. However, if you don't want to create the separate 'boot' partition, then you'll have no other choice but to use GRUB or syslinux on the MBR.
Thanks. Yes...I followed the procedure just like you described. I figured that my problem was that I didn't create a separate /boot partition, so I reformatted the partitions I created and redid the install. However, I was not able to install GRUB in the AIF; I had to reboot into the Live CD and install GRUB to my boot partition manually. All is good now as I have a working dual-boot now. Arch Linux has been a sort of learning curve for me, but I have gained valuable knowledge and experience by using this distro.
Yes. I didn't want to mess with GRUB or NTLDR. I know that reinstalling NTLDR is not that difficult, but I didn't want to mess with it at all. It just seemed easier to chainload GRUB to NTLDR using EasyBCD. I'm a sort of "distro-hopper" anyhow, and using this method allows me to cleanly remove any distro I install without having to mess with GRUB or reinstalling NTLDR.
Thanks!
Glad to hear! Yes, Arch Linux is a wonderful distribution, and one of my favorites. It's great for not-so-newbie beginners to learn from. pacman is one of my favorite package managers, as there is always the latest stable software available in the Arch repos. Glad everything worked out. Have fun with Arch!

How to setup grub2 with arch linux and xen, lvm on luks

OK, so I tried downloading this package from AUR: https://aur.archlinux.org/packages/xen-git/ , but that has patching problems as noted in the comments. It looks like the packagebuild sets up all the xen stuff for you, but I can't seem to get the package to install because of the error's while patching. If anyone can point me in the right direction on what all the extra files in the PKGBUILD are for or how to debug problems with PKGBUILDs not working because of patches.
So next I just tried to compile the latest xen from git://xenbits.xen.org/xen.git (with ./configure, make, make install) and that seemed to go fine, but I'm a bit confused:
1. Do I have to do any additional configuration for xen when working with arch linux? On ubuntu I could just compile the source, update grub, and make sure to start the x services at runtime.
2. How do I set up grub to load xen with this setup? Right now this is my /boot/grub/grub.cfg:
GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Arch"
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX="cryptdevice=/dev/sda3:vgStorage"
# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
# Uncomment to enable Hidden Menu, and optionally hide the timeout count
#GRUB_HIDDEN_TIMEOUT=5
#GRUB_HIDDEN_TIMEOUT_QUIET=true
# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console
# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE=auto
# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep
# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true
# Uncomment and set to the desired menu colors. Used by normal and wallpaper
# modes only. Entries specified as foreground/background.
#GRUB_COLOR_NORMAL="light-blue/black"
#GRUB_COLOR_HIGHLIGHT="light-cyan/blue"
# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/path/to/wallpaper"
#GRUB_THEME="/path/to/gfxtheme"
# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"
#GRUB_SAVEDEFAULT="true"
~
I've tried throwing in a line like: XEN_HYPERVISOR_CMDLINE="cryptdevice=/dev/sda3:vgStorage", but nothing new shows up on the grub boot menu.
First time trying to set up a non-ubuntu system, please help!

As for XEN.... well you could always try QEMU/KVM or LXC.
As for the LVM2-on-LUKS/dm-crypt
My /etc/mkinitcpio.conf looks like this...
MODULES="aesni_intel ata_generic ata_piix nls_cp437 ext4 intel_agp i915 dm-snapshot"
BINARIES=""
FILES=""
HOOKS="base udev autodetect block keymap encrypt lvm2 filesystems keyboard fsck shutdown"
/etc/defaults/grub
GRUB_CMDLINE_LINUX="cryptdevice=/dev/sda2:root:allow-discards"
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
GRUB_TERMINAL_INPUT=console
GRUB_GFXMODE=auto
GRUB_GFXPAYLOAD_LINUX=keep
GRUB_DISABLE_RECOVERY=true
The running grub config looks like this
/boot/grub/grub.cfg
9 insmod part_gpt
10 insmod part_msdos
53 if loadfont unicode ; then
54 set gfxmode=auto
55 load_video
56 insmod gfxterm
57 set locale_dir=$prefix/locale
58 set lang=en_US
59 insmod gettext
60 fi
61 terminal_input console
62 terminal_output gfxterm
63 set timeout=3
84 menuentry 'Backup, Arch Linux grsec kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-grsec kernel-true-12341234-8080-8080-8080-332200882255' {
85 load_video
86 set gfxpayload=keep
87 insmod gzio
88 insmod part_msdos
89 insmod ext2
90 set root='hd1,msdos2'
91 if [ x$feature_platform_search_hint = xy ]; then
92 search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos2 --hint-efi=hd1,msdos2 --hint-baremetal=ahci1,msdos2 BBAAEEAA-FFCC-CCFF-FFCC-AABBCCEEBBAA
93 else
94 search --no-floppy --fs-uuid --set=root BBAAEEAA-FFCC-CCFF-FFCC-AABBCCEEBBAA
95 fi
96 echo 'Loading Linux grsec kernel ...'
97 linux /vmlinuz-linux-grsec root=/dev/mapper/VolGroup00-lvroot rw cryptdevice=/dev/sda2:root:allow-discards quiet
98 echo 'Loading initial ramdisk ...'
99 initrd /initramfs-linux-grsec.img
100 }
Things to note:
Numerical UUID is the UUID of the ROOT partition.
Alphabetical UUIS is the BOOT partition
hd1,msdos2 AND ahci1,msdos2 are how the Grub Bootloader numbers the drives not Linux.
I have my BOOT partition on a USB stick, and it is the Second partition.
So, that would make it, Device 2 and Partition 2
Device numbering starts at 0
Partition numbering starts at 1
Oh, and note that you don't need ":allow-discards" ... at all but certainly if you don't have an SSD. Also note that I included the line numbers so it is very clear that I didn't post the whole thing, but instead what I thought was relevant. Finally, I am loading modules that I don't even need, but what the hell... if it ain't broke, don't fix it
Last edited by hunterthomson (2013-12-04 08:31:45)

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

Arch Linux and ARM

We have been talking to the Arch Linux ARM team and have decided to refine our policy around that architecture.
The Other Architectures forum has been moved into the Technical Issues and Asssistance category, and the ARM sticky has been updated with clearer direction about our policy.
If you are an ARM user, please take a couple of minutes to familiarize yourself with the updated policy. Both the Arch mod team and the ALARM team feel that this is the best way to ensure that assistance is sought from the community that is best placed to help.

Whoa, everyone's reading far too much into what I said. I just meant that I got it installed under the chroot in android following the steps that were on the plugapps site; the actual page doesn't seem to exist anymore, but I found similar instructions here. I meant that I thought it was cool that I had a functioning build of pacman running locally on the device. Didn't mean to imply that it was a native install.
Although I understand the reaction as I'm watching the developments in this thread with just as much anticipation.
Last edited by jb (2011-06-30 18:00:45)

[Solved] RAID 0 with Arch Linux and Intel Matrix Storage Manager

I just bought a brand new DELL Studio desktop and it has 2 500 HD's which I would like to run in RAID 0. I've setup the BIOS to run the RAID 0. Now I want the arch linux installation to recognise the volume. I followed the guide on the wikipage
http://wiki.archlinux.org/index.php/Ins … _Fake-RAID
but /dev/mapper doesn't show anything after modprobing the modules and installing dmraid. My controller is a intel matrix storage controller, so what module should I modprobe because sata_sil isn't the right one.
Regards
André
Last edited by fettouhi (2008-12-15 10:57:18)

you have a separate /boot partition, so your menu.lst must say :
root (hd0,0) # the partition including /boot
kernel /vmlinuz26 ... # without leading /boot
initrd /kernel26.img # without leading /boot
(in grub, / is the root of the partition that was set with the root command, your vmlinuz26 and kernel26.img are in (hd0,0)/, not in (hd0,0)/boot/)
did you install from core CD or from FTP ?
there was a dmraid update few weeks ago that modified device names that dmraid creates :
it add "p" before the number of the partition (your iws...Volume0 don't change, but your iws...Volume0# change to iws...Volume0p#)
if you installed from core CD, you will only need to add this "p" when you will upgrade dmraid (or the full system)
(you will then need to edit both /boot/grub/menu.lst and /etc/fstab)
if you installed from FTP, you need to add this "p" now, as you installed last version of dmraid

Dual boot arch linux and windows

I recently installed arch linux. However, I have a windows 7 installation on a separate hard drive (/dev/sdb), and it is not detected by grub. I have tried to use os-prober, and grub-mkconfig to generate my configuration file, but I think these programs are in grub2-common, and this conflicts with the package grub. When I do uninstall grub, and replace with grub2-common, I can generate the config file, but grub brings me to the grub prompt, and will not boot. Can I use grub-mkconfig without uninstalling grub, or do I have to create grub.cfg and edit it manually? Thank you in advance!

skunktrader wrote:
grub reads /boot/grub/menu.lst. You need to edit this file manually to add windows 7
Read this
It works! You are a genius!!!!!!! Thank you so much!!

Can Kerberos Server 5 be run on Arch Linux and Windows Clients use it?

Hi There,
I was wondering (before I invested a great deal of time into it) if I could run a kerberos 5 server on my Arch box and get a Windows machine on my network to use it to log into Windows? (eg. like a domain)
I've tried doing the same with Samba 4 (which I bet will be massive when it's eventually released!), but it doesn't really work too great at the moment and wondered if I could achieve what I wanted with Kerberos 5?
I have DNS & DHCP already running and Samba 3 for network shares; but I really want the whole SSO package for all my machines. I know it's possible for my Mac Laptop to use Kerberos, but just not sure about Windows (XP/2003/7)
Thanks,
Tom

I will post something when I get the last issues ironed out. There is very little information about this anywhere let-alone on Arch wiki! It has been a real struggle, shame Samba 4 isn't more stable/working.
Stuff like M$ just decided to disable DES encryption by default in Windows 7. You know; the usual c**p-ness!

[Solved] VMWare Player 4.0.0 and kernel 3.1.4-1-ARCH

Hi,
i followed the instructions here https://wiki.archlinux.org/index.php/VM … n.2FPlayer
while running the modconfig command i get this error.
Stopping VMware services:
VMware Authentication Daemon done
VM communication interface socket family done
Virtual machine communication interface done
Virtual machine monitor done
Blocking file system done
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmmon-only'
make -C /lib/modules/3.1.4-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.1.4-1-ARCH'
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/iommu.o
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/hostif.o
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driverLog.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/memtrack.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/vmx86.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/apic.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/task.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/cpuid.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/comport.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/hashFunc.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/phystrack.o
CC [M] /tmp/vmware-root/modules/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/vmware-root/modules/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmmon-only/vmmon.mod.o
LD [M] /tmp/vmware-root/modules/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-3.1.4-1-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmmon-only'
make[1]: »postbuild« ist bereits aktualisiert.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
No protocol specified
No protocol specified
Built vmmon module
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmnet-only'
make -C /lib/modules/3.1.4-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.1.4-1-ARCH'
CC [M] /tmp/vmware-root/modules/vmnet-only/driver.o
CC [M] /tmp/vmware-root/modules/vmnet-only/hub.o
CC [M] /tmp/vmware-root/modules/vmnet-only/userif.o
CC [M] /tmp/vmware-root/modules/vmnet-only/netif.o
CC [M] /tmp/vmware-root/modules/vmnet-only/bridge.o
CC [M] /tmp/vmware-root/modules/vmnet-only/filter.o
CC [M] /tmp/vmware-root/modules/vmnet-only/smac.o
CC [M] /tmp/vmware-root/modules/vmnet-only/procfs.o
CC [M] /tmp/vmware-root/modules/vmnet-only/smac_compat.o
CC [M] /tmp/vmware-root/modules/vmnet-only/vnetEvent.o
CC [M] /tmp/vmware-root/modules/vmnet-only/vnetUserListener.o
In file included from /tmp/vmware-root/modules/vmnet-only/bridge.c:51:0:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:186:0: Warnung: »alloc_netdev« redefiniert [standardmäßig aktiviert]
include/linux/netdevice.h:2438:0: Anmerkung: dies ist die Stelle der vorherigen Definition
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:187:0: Warnung: »alloc_etherdev« redefiniert [standardmäßig aktiviert]
include/linux/etherdevice.h:53:0: Anmerkung: dies ist die Stelle der vorherigen Definition
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:208:1: Fehler: In Konflikt stehende Typen für »netif_start_queue«
include/linux/netdevice.h:1804:20: Anmerkung: Vorherige Definition von »netif_start_queue« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_start_queue«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:210:21: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:214:1: Fehler: In Konflikt stehende Typen für »netif_stop_queue«
include/linux/netdevice.h:1869:20: Anmerkung: Vorherige Definition von »netif_stop_queue« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_stop_queue«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:216:19: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:220:1: Fehler: In Konflikt stehende Typen für »netif_queue_stopped«
include/linux/netdevice.h:1895:19: Anmerkung: Vorherige Definition von »netif_queue_stopped« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_queue_stopped«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:222:11: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:222:11: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:226:1: Fehler: In Konflikt stehende Typen für »netif_wake_queue«
include/linux/netdevice.h:1838:20: Anmerkung: Vorherige Definition von »netif_wake_queue« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_wake_queue«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:228:21: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:4: Fehler: Implizite Deklaration der Funktion »mark_bh« [-Werror=implicit-function-declaration]
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:12: Fehler: »NET_BH« nicht deklariert (erste Benutzung in dieser Funktion)
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:12: Anmerkung: jeder nicht deklarierte Bezeichner wird nur einmal für jede Funktion, in der er vorkommt, gemeldet
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:233:1: Fehler: In Konflikt stehende Typen für »netif_running«
include/linux/netdevice.h:1911:19: Anmerkung: Vorherige Definition von »netif_running« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_running«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:235:14: Fehler: »struct device« hat kein Element namens »start«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:239:1: Fehler: In Konflikt stehende Typen für »netif_carrier_ok«
include/linux/netdevice.h:2145:19: Anmerkung: Vorherige Definition von »netif_carrier_ok« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:245:1: Fehler: In Konflikt stehende Typen für »netif_carrier_on«
include/linux/netdevice.h:2154:13: Anmerkung: Vorherige Deklaration von »netif_carrier_on« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:250:1: Fehler: In Konflikt stehende Typen für »netif_carrier_off«
include/linux/netdevice.h:2156:13: Anmerkung: Vorherige Deklaration von »netif_carrier_off« war hier
cc1: Einige Warnungen werden als Fehler behandelt
make[2]: *** [/tmp/vmware-root/modules/vmnet-only/bridge.o] Fehler 1
make[2]: *** Warte auf noch nicht beendete Prozesse...
In file included from /tmp/vmware-root/modules/vmnet-only/netif.c:43:0:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:186:0: Warnung: »alloc_netdev« redefiniert [standardmäßig aktiviert]
include/linux/netdevice.h:2438:0: Anmerkung: dies ist die Stelle der vorherigen Definition
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:187:0: Warnung: »alloc_etherdev« redefiniert [standardmäßig aktiviert]
include/linux/etherdevice.h:53:0: Anmerkung: dies ist die Stelle der vorherigen Definition
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:208:1: Fehler: In Konflikt stehende Typen für »netif_start_queue«
include/linux/netdevice.h:1804:20: Anmerkung: Vorherige Definition von »netif_start_queue« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_start_queue«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:210:21: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:214:1: Fehler: In Konflikt stehende Typen für »netif_stop_queue«
include/linux/netdevice.h:1869:20: Anmerkung: Vorherige Definition von »netif_stop_queue« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_stop_queue«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:216:19: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:220:1: Fehler: In Konflikt stehende Typen für »netif_queue_stopped«
include/linux/netdevice.h:1895:19: Anmerkung: Vorherige Definition von »netif_queue_stopped« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_queue_stopped«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:222:11: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:222:11: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:226:1: Fehler: In Konflikt stehende Typen für »netif_wake_queue«
include/linux/netdevice.h:1838:20: Anmerkung: Vorherige Definition von »netif_wake_queue« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_wake_queue«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:228:21: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:4: Fehler: Implizite Deklaration der Funktion »mark_bh« [-Werror=implicit-function-declaration]
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:12: Fehler: »NET_BH« nicht deklariert (erste Benutzung in dieser Funktion)
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:12: Anmerkung: jeder nicht deklarierte Bezeichner wird nur einmal für jede Funktion, in der er vorkommt, gemeldet
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:233:1: Fehler: In Konflikt stehende Typen für »netif_running«
include/linux/netdevice.h:1911:19: Anmerkung: Vorherige Definition von »netif_running« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_running«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:235:14: Fehler: »struct device« hat kein Element namens »start«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:239:1: Fehler: In Konflikt stehende Typen für »netif_carrier_ok«
include/linux/netdevice.h:2145:19: Anmerkung: Vorherige Definition von »netif_carrier_ok« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:245:1: Fehler: In Konflikt stehende Typen für »netif_carrier_on«
include/linux/netdevice.h:2154:13: Anmerkung: Vorherige Deklaration von »netif_carrier_on« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:250:1: Fehler: In Konflikt stehende Typen für »netif_carrier_off«
include/linux/netdevice.h:2156:13: Anmerkung: Vorherige Deklaration von »netif_carrier_off« war hier
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetIfSetup«:
/tmp/vmware-root/modules/vmnet-only/netif.c:149:7: Fehler: »struct net_device« hat kein Element namens »init«
/tmp/vmware-root/modules/vmnet-only/netif.c:150:7: Fehler: »struct net_device« hat kein Element namens »open«
/tmp/vmware-root/modules/vmnet-only/netif.c:151:7: Fehler: »struct net_device« hat kein Element namens »hard_start_xmit«
/tmp/vmware-root/modules/vmnet-only/netif.c:152:7: Fehler: »struct net_device« hat kein Element namens »stop«
/tmp/vmware-root/modules/vmnet-only/netif.c:153:7: Fehler: »struct net_device« hat kein Element namens »get_stats«
/tmp/vmware-root/modules/vmnet-only/netif.c:154:7: Fehler: »struct net_device« hat kein Element namens »set_mac_address«
/tmp/vmware-root/modules/vmnet-only/netif.c:155:7: Fehler: »struct net_device« hat kein Element namens »set_multicast_list«
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetIfNetDeviceToNetIf«:
/tmp/vmware-root/modules/vmnet-only/netif.c:196:14: Fehler: »struct net_device« hat kein Element namens »priv«
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetIf_Create«:
/tmp/vmware-root/modules/vmnet-only/netif.c:311:4: Fehler: Implizite Deklaration der Funktion »compat_alloc_netdev« [-Werror=implicit-function-declaration]
/tmp/vmware-root/modules/vmnet-only/netif.c:311:8: Warnung: Zuweisung erzeugt Zeiger von Ganzzahl ohne Typkonvertierung [standardmäßig aktiviert]
/tmp/vmware-root/modules/vmnet-only/netif.c:316:7: Fehler: »struct net_device« hat kein Element namens »priv«
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetIfReceive«:
/tmp/vmware-root/modules/vmnet-only/netif.c:397:4: Warnung: Übergabe des Arguments 1 von »netif_running« von inkompatiblem Zeigertyp [standardmäßig aktiviert]
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:233:1: Anmerkung: »struct device *« erwartet, aber Argument hat Typ »struct net_device *«
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetifOpen«:
/tmp/vmware-root/modules/vmnet-only/netif.c:477:4: Warnung: Übergabe des Arguments 1 von »netif_start_queue« von inkompatiblem Zeigertyp [standardmäßig aktiviert]
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:208:1: Anmerkung: »struct device *« erwartet, aber Argument hat Typ »struct net_device *«
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetifClose«:
/tmp/vmware-root/modules/vmnet-only/netif.c:525:4: Warnung: Übergabe des Arguments 1 von »netif_stop_queue« von inkompatiblem Zeigertyp [standardmäßig aktiviert]
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:214:1: Anmerkung: »struct device *« erwartet, aber Argument hat Typ »struct net_device *«
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »netif_running«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:236:1: Warnung: Kontrollfluss erreicht Ende von Nicht-void-Funktion [-Wreturn-type]
cc1: Einige Warnungen werden als Fehler behandelt
make[2]: *** [/tmp/vmware-root/modules/vmnet-only/netif.o] Fehler 1
make[1]: *** [_module_/tmp/vmware-root/modules/vmnet-only] Fehler 2
make[1]: Leaving directory `/usr/src/linux-3.1.4-1-ARCH'
make: *** [vmnet.ko] Fehler 2
make: Leaving directory `/tmp/vmware-root/modules/vmnet-only'
Unable to install vmnet
Maybe someone has an idea whats going wrong ?
stubb
Last edited by stubb (2011-12-01 23:45:44)

rm /usr/lib/vmware/modules/source/.patched
fixed it

Differences between Arch linux and RHEL-based Distros?

Hi there!
So, I am officially trying to make the permanent switch from Windows to Linux. I've used Linux in the past, from Ubuntu, to Fedora, to Mint, and I've always liked Arch the most. Nothing beats the feeling of an OS you had a hand in setting up.
I'm wondering though, what are the differences in Arch vs distros like Red Hat, Fedora, and CentOS? I recently picked up a book called, "The Linux Bible" which provides a course-like approach to learning the intricacies of Linux. I'm wondering if it would be easily possible to adapt the lessons from that to Arch, or to use Fedora or another RHEL-based distro like it suggests.
Thanks

The biggest issue I find is with SE Linux. I don't know if this is default in RHEL itself but Fedora uses it. If I understood it properly, though, I doubt it would be such an issue!
EDIT: I think it would be best to learn one distro first, using documentation for that distro. So if you want to use the book, install something that matches the book as closely as possible. If you want to use Arch, use the wiki as your primary documentation. I say this because there is a big difference between figuring out the ways in which two distros differ when you understand the GNU/Linux basics and (I imagine) trying to do so when you are still learning those basics. I don't just mean ls, grep etc. - other systems use those - but the stuff which is common to any GNU/Linux distro. Obviously this applies even more if you also are learning stuff like ls, grep, cd etc. (which might be true if you're moving from Windows rather than, say, OS X or one of the BSDs).
Last edited by cfr (2013-10-31 23:30:15)

Vmware Player in Arch Linux and RFKILL

Similar Messages

Maybe you are looking for