[SOLVED] Arch as Guest on VirtualBox on a Dell XPS 15 - Wireless Not..

I have a Dell XPS 15 (2012 Model L521X) that I'm running arch on as a guest in virtualbox. Dell XPS 15 Wiki says the Atheros wireless adapter should work out of the box. It's not working for me, so I found under the wireless wiki that the module for this card is ath9k. I modprobed it but I still can't get the interface to come up. I also tried /etc/modules-load.d/ath9k.conf and rebooted. Still nothing. ip link shows no wireless interface. Ethernet works fine.
lspci -v
only shows the Ethernet controller.
journalctl -b | grep Network
just shows the e1000 Intel PRO/1000 Network Driver.
The last thing I tried per the XPS 15 wiki is installing rfkill to toggle the wireless adapter on/off by using fn+f2 key, also with no luck. So I'm stomped. Anything else that I can possibly check for to get this wifi running?
Last edited by w201 (2014-01-23 19:52:37)

The problem is, you are not running on a Dell XPS 15. You are running on a VirtualBox virtual machine. That machine has a (virtual) wired Ethernet adapter that looks like an e1000. You establish Ethernet connectivity through that 'wired' network to your host computer. Depending on how VirtualBox is configured, that virtual network is either bridged to to Wireless Card that is owned by the host, or the host/VirtualBox provide NAT forwarding to whatever network the host is attached. In all likelihood, it is NAT. Leave it NAT, unless your guest needs to be a server.
What is your host OS?
What happens, on your guest OS, if you just run dhcpcd as root? You should get an address like 10.0.0.2. If so, and if the host has a wireless connection, you will probably find the guest does too.
Last edited by ewaller (2014-01-23 19:29:26)

Similar Messages

[SOLVED] Arch Linux Guest Virtual Box OSE problem

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

Updating Virtualbox fixed the issue.

Copy and paste not working with Arch as guest on virtualbox

In my ~/.xinitrc file I have the following:
exec awesome
/usr/bin/VBoxClient-all
VBoxClient-all &
I have checked the /usr/bin directory and there is no VBoxClient-all file.
I have installed the virtualbox-guest-utils aswell as adding the following to /etc/modules-load.d/virtualbox.conf:
vboxguest
vboxsf
vboxvideo
Thanks.
Last edited by psycho_tea_drinker (2013-07-22 12:24:34)

jasonwryan wrote:https://wiki.archlinux.org/index.php/Xi … ng_started
Thank you! The problem was exec *something* should be on the last line.

No internet/DNS connection with Arch guest on Virtualbox

I am trying to run Archlinux as a guest OS in Virtualbox on an Ubuntu 7.10 host system, and I cannot connect to anything but my router. So far, I have only installed the base system (Arch Linux core 2007.08-2) from a CD.
I can ping the localhost (both on 127.0.0.1 and 10.0.2.15) and my gateway (10.0.2.2), but not my DNS server (10.0.2.3) or anything else (like www.google.com). So far, I went through the "Beginners Guide", the "Official Arch Linux Install Guide", the configuring network section of the ArchWiki, and tried to find some solution on the internet. Still no luck.
I have set up networking to use dhcp. The networking section in my /etc/rc.conf file looks like:
HOSTNAME="arch"
lo="lo 127.0.0.1"
eth0="dhcp"
INTERFACES=(lo eth0)
ROUTES=(!gateway)
The daemons that run during startup are:
DAEMONS=(syslog-ng network netfs crond)
I have put the hostname in the /etc/hosts file like:
127.0.0.1 localhost.localdomain localhost arch
The nameserver that shows up in my /etc/resolv.conf file is:
nameserver 10.0.2.3
I am a bit puzzled and I don't know what to do. I do think it is an Arch issue, since I also have Windows XP running in a Virtualbox with Ubuntu as host, and that works fine with the same Virtualbox settings and network settings within the guest OS.
I would appreciate any help here.
Last edited by Average Joe (2008-04-19 12:41:29)

Try reading the VirtualBox manuals.
I specifically remember that ping doesn't work at all, although you DO have internet connection.
Try running some sort of web browser (firefox or links), and then decide if you have internet access or not.
And, of course, make sure you do have dhcp running ("dhcpcd eth0").
One last thing:
I have an Arch guest (on VirtualBox), running on an Arch host.
Everything works fine..
Simply installed it from the installation CD, didn't have to do nothing special for it to work..
Last edited by fiod (2008-04-19 13:41:19)

[Solved] Arch and virtual networking, not working as planned.

Running pfSense trough virtualbox, running virtual machines behind it.
What setup do I need, to get wireless LAN solely to pfSense. Currently I use the bridged setup in virtualbox as the WAN side. LAN is a host only adapter vboxnet0, all other VM's connect through that virtual adapter.
I would like to use a second host only adapter on a different subnet, but, once I create the adapter vboxnet1 and add it as second LAN card OPT1 to pfSense, internet stops working on the first LAN, though I can still ping google from the pfSense box.
How do I get Arch to not use the wireless connection but only the second host only adapter.
At the moment I use NetworkManager for the network.
Current setup (working):
Router – 192.168.1.1
Arch bare hardware, main OS – 192.168.1.9 (wireless)
pfSense WAN - 192.168.1.12 ( through wireless)
pfSense LAN - 10.10.2.1
host only adapter vboxnet0 - 10.10.2.3
I would like to add (not working):
pfSense OPT1 - 10.10.10.1
host only adapter vboxnet1 - 10.10.10.3
But this fails for unknown reasons.
What do I miss, or should I do different, thanks in advance, Mark
Last edited by qinohe (2015-01-30 12:39:32)

All is working well. I extended to four virtual adapters, one for the Arch host, and a wireless AP connected to eth0, bridged to pfSense. All applications on the host are finding the pfSense squid proxy, I have libproxy installed. Set the default gateway on the host to be the proxy of pfSense.
Now I can use my laptop to connect to insecure networks while not belonging to it, and host for friends at the same time, very nice

Arch PV guest in Xen won't boot

Hi,
I have Xen installed and running several (win 7) HVMs. I've setup an Arch PV guest but I am having a problem booting it. After each failed attempt to fix this issue I try to view the /var/log/xen/bootloader.XX.log file but all of these files are zero bytes. So, I'm having some trouble troubleshooting this. I followed the instructions from https://wiki.archlinux.org/index.php/xen on setting up an Arch PV and do not think I missed anything.
This is the error message I get:
[root@earth arch1]# xl create -c /vm/arch1/arch1.conf
Parsing config from /vm/arch1/arch1.conf
libxl: error: libxl_bootloader.c:628:bootloader_finished: bootloader failed - consult logfile /var/log/xen/bootloader.85.log
libxl: error: libxl_exec.c:129:libxl_report_child_exitstatus: bootloader [-1] died due to fatal signal Killed
libxl: error: libxl_create.c:1022:domcreate_rebuild_done: cannot (re-)build domain: -3
This is the vm conf that I use to boot the arch install iso after loop mounting it.
name = "arch1"
kernel = "/mnt/arch/boot/x86_64/vmlinuz"
ramdisk = "/mnt/arch/boot/x86_64/archiso.img"
extra = "archisobasedir=arch archisolabel=ARCH_201410"
memory = 1024
vif = [ 'mac=00:16:3E:42:01:3D,bridge=xenbr0,model=e1000' ]
disk = [ '/vm/arch1/arch1.img,,hda,w', '/vm/img/ARCH_201410.iso,,hdb,cdrom']
This is my vm conf used to boot the VM after installing arch and umount-ing the loop mounted iso:
name = "arch1"
bootloader = "pygrub"
memory = 1024
vif = [ 'mac=00:16:3E:42:01:3D,bridge=xenbr0,model=e1000' ]
disk = [ '/vm/arch1/arch1.img,,hda,w']
And this is an abbreviated version of how I install arch on the VM. During the install I don't think I've missed anything from the wiki.
My understanding is that pygrub will take care of booting as long as /boot/grub/grub.conf is exists and is setup correctly which I believe I have done.
I copied the sample grub.conf from "Xen - ArchWiki" and used the UUID for "/" found in /etc/fstab (its the same I get from blkid)
The wiki mentions that without certain modules in /etc/mkinitcpio.conf the VM will not boot. But I've added them as shown below.
So I'm not sure why I'm getting the above error.
gdisk /dev/xvda
n
1
<enter>
<enter>
8e00 #this sets up my lvm partition to stick everything in (root and home) as shown below.
pvcreate /dev/xvda1
vgcreate arch /dev/xvda1
lvcreate -L 18G -n root arch
lvcreate -L 1G -n home arch
mkfs.ext4 -F /dev/mapper/arch-root
mkfs.ext4 -F /dev/mapper/arch-home
mount /dev/mapper/arch-root /mnt
mkdir /mnt/home
mount /dev/mapper/arch-home /mnt/home
pacstrap -i /mnt base base-devel
genfstab -U -p /mnt >> /mnt/etc/fstab
arch-chroot /mnt /bin/bash
#setup /etc/locale.gen & /etc/locale.conf
#setup host name
#setup network
sed -i 's/MODULES=\"\"/MODULES=\"xen-blkfront\ xen-fbfront\ xen-netfront\ xen-kbdfront\"/g' /etc/mkinitcpio.conf
mkinitcpio -p linux
mkdir /boot/grub
cd /boot/grub
cat /etc/fstab
#create /boot/grub/grub.conf based on the sample from "Xen - ArchWiki" with the UUID for "/" found in /etc/fstab (its the same I get from blkid)
After doing the above install I poweroff and umount the loop mounted iso. I then get the above error message when running xl create. Unfortunately the bootloader logs are empty.
Last edited by hbc2 (2014-10-13 15:28:18)

Is your hard disk attached via usb? If not, you did not have the proper modules for the intramfs to access the hard disk itself. You had it set up so that it could boot from a usb device, but not an internal device. You should have read the comments for each of those examples. It explains pretty cearly what each example would be used for.
Edit: I use lvm and my mkinitcpio.conf HOOKS line looks like this:
HOOKS="base udev autodetect sata lvm2 filesystems fsck timestamp"
My SSD's are connected via SATA III, the lvm2 hook is obvious, the filesystems load the ext4 module (all filesystems are ext4), fsck adds fsck and fsck.ext4, timestamp makes 'systemd-analyze' able to tell you how long it takes the initramfs and kernel to load individually instead of together. base should always be there, and first (unless you really really know what you are doing), udev adds... udev, and autodetect tries its best to strip everything you don't need for your particular system.
For info on a paritcular hook, use the -H option with mkinitcpio. (ie. 'mkinipcio -H lvm2'). There is also a fantasticlly informative wiki page about mkinitcpio.
Last edited by WonderWoofy (2012-11-26 03:44:40)

[SOLVED]Arch Linux / UEFI / BTRFS using Grub2 & Windows 8 in a 2nd HDD

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

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

[SOLVED] OpenBox with XP in VirtualBox

Hi All
I'm hoping someone has an answer to this one. I'm in the process of switching from Gnome 3 to OpenBox. I'm almost there except for getting VirtualBox to work correctly in seamless mode.
If I login to Gnome 3 then seamless virtualbox works brilliantly but in openBox I get a sort of screen lag as though the graphics driver is running incredibly slow. VirtualBox works fine when it's not in seamless mode though.
Contents of .config/openbox/autostart:
xcompmgr &
# Restore wallpaper
nitrogen --restore &
# Start Devilspie to alter windows
devilspie -a &
# Start Main Panel
tint2 &
EDIT: I use Docky as a program launcher hence the need for xcompmgr. Devilspie I use to move NetBeans to the development desktop.
Thanks
Rich
Last edited by RichAustin (2011-11-06 12:36:23)

Unfortunately I don't think either xcompmgr or cairo-compmgr will work with virtualbox seamless mode. I think seamless mode works decently with compiz and kwin, though in the past these have had problems as well. Seamless and compositing just don't mix well and unfortunately I doubt oracle cares about making it work with xcompmgr, which isn't even being developed anymore, so no fix likely to come from that end either.
You could either use docky uncomposited, it still works, just not as pretty, use another dock, or use compiz as your window manger instead of openbox.
Also you can move an application to a specific dektop in openbox rc.xml with
<application class="the class of the app you want to move*">
<desktop>2</desktop>
</application>
So you maybe you don't need to run Devilspie, if you use compiz it also has features to control where applications are placed. There are also more application placement variables in openbox then just my above example.

[semi-solved] dell xps 12 touchscreen not working (2013, 12-9Q33)

does anyone know how to get the touch screen working the dell xps 12?
ran windows on it for a few days and there did not appear to be any hardware issues with touchscreen (or anything else).
deleted all windows partitions and installed arch + kde with no issues, boots and runs great. but no response from the touch screen.
have tried to cat every /dev/input/event* but get nothing when tapping touch screen.
beleve it uses an atmel maxtouch digitizer... which i think should be picked up by udev... but dont think udev even sees the device, it just detetcs boring old mouse.
this looks like a simmilar issue with ubuntu https://bugs.launchpad.net/ubuntu/+sour … ug/1218973 but on my system there is no indication that it is an i2c device.
tried atmel kernel but still no action https://git.kernel.org/cgit/linux/kerne … mel-mxt-ts
lsusb
Bus 003 Device 002: ID 8087:8000 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:09fa Intel Corp.
Bus 001 Device 003: ID 0bda:5716 Realtek Semiconductor Corp.
Bus 001 Device 002: ID 8087:07dc Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
input
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=11 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Power Button id=8 [slave keyboard (3)]
↳ Integrated Webcam id=9 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)]
↳ Dell WMI hotkeys id=12 [slave keyboard (3)]
sudo cat /proc/bus/input/devices
I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input0
U: Uniq=
H: Handlers=sysrq kbd event0
B: PROP=0
B: EV=120013
B: KEY=1100f02902000 8380307cf910f001 feffffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1
U: Uniq=
H: Handlers=kbd event1
B: PROP=0
B: EV=3
B: KEY=10000000000000 0
I: Bus=0019 Vendor=0000 Product=0005 Version=0000
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input2
U: Uniq=
H: Handlers=event2
B: PROP=0
B: EV=21
B: SW=1
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
U: Uniq=
H: Handlers=kbd event3
B: PROP=0
B: EV=3
B: KEY=10000000000000 0
I: Bus=0001 Vendor=10ec Product=0668 Version=0001
N: Name="HDA Digital PCBeep"
P: Phys=card1/codec#0/beep0
S: Sysfs=/devices/pci0000:00/0000:00:1b.0/input/input4
U: Uniq=
H: Handlers=kbd event4
B: PROP=0
B: EV=40001
B: SND=6
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card1/input5
U: Uniq=
H: Handlers=event5
B: PROP=0
B: EV=21
B: SW=4
I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name="PC Speaker"
P: Phys=isa0061/input0
S: Sysfs=/devices/platform/pcspkr/input/input6
U: Uniq=
H: Handlers=kbd event6
B: PROP=0
B: EV=40001
B: SND=6
I: Bus=0019 Vendor=0000 Product=0000 Version=0000
N: Name="Dell WMI hotkeys"
P: Phys=wmi/input0
S: Sysfs=/devices/virtual/input/input7
U: Uniq=
H: Handlers=kbd rfkill event7
B: PROP=0
B: EV=13
B: KEY=1500b00000000 200300000 0 0
B: MSC=10
I: Bus=0003 Vendor=0bda Product=5716 Version=3204
N: Name="Integrated Webcam"
P: Phys=usb-0000:00:14.0-5/button
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/input/input8
U: Uniq=
H: Handlers=kbd event8
B: PROP=0
B: EV=3
B: KEY=100000 0 0 0
I: Bus=0011 Vendor=0002 Product=0007 Version=01b1
N: Name="SynPS/2 Synaptics TouchPad"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input9
U: Uniq=
H: Handlers=mouse0 event9
B: PROP=5
B: EV=b
B: KEY=e520 610000 0 0 0 0
B: ABS=660800011000003
I: Bus=0019 Vendor=0000 Product=0006 Version=0000
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input10
U: Uniq=
H: Handlers=kbd event10
B: PROP=0
B: EV=3
B: KEY=3e000b00000000 0 0 0
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel MID HDMI/DP,pcm=8"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:03.0/sound/card0/input11
U: Uniq=
H: Handlers=event11
B: PROP=0
B: EV=21
B: SW=140
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel MID HDMI/DP,pcm=7"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:03.0/sound/card0/input12
U: Uniq=
H: Handlers=event12
B: PROP=0
B: EV=21
B: SW=140
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel MID HDMI/DP,pcm=3"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:03.0/sound/card0/input13
U: Uniq=
H: Handlers=event13
B: PROP=0
B: EV=21
B: SW=140
sudo dmidecode
[sudo] password for gamera:
# dmidecode 2.12
# SMBIOS entry point at 0x000f04c0
SMBIOS 2.7 present.
56 structures occupying 2720 bytes.
Table at 0x000EBA70.
Handle 0xDA00, DMI type 218, 251 bytes
OEM-specific Type
Header and Data:
DA FB 00 DA B2 00 0D 5F 0F 37 40 7D 00 00 00 00
00 7E 00 01 00 00 00 75 01 01 80 01 00 76 01 02
80 01 00 4F 02 05 80 01 00 50 02 06 80 00 00 A5
02 02 00 00 00 A6 02 02 00 01 00 9C 00 03 00 01
00 9B 00 03 00 00 00 8A 01 04 00 01 00 89 01 04
00 00 00 7F 01 05 00 00 00 80 01 05 00 01 00 53
01 06 00 00 00 52 01 06 00 01 00 7B 01 07 00 00
00 7C 01 07 00 01 00 94 01 08 00 00 00 93 01 08
00 01 00 7D 00 09 00 00 00 2D 00 0A 00 01 00 2E
00 0A 00 00 00 6E 00 0B 00 00 00 95 00 0C 00 01
00 96 00 0C 00 00 00 2F 02 0D 00 01 00 30 02 0D
00 00 00 50 02 0E 00 00 00 51 02 0E 00 01 00 52
02 0E 00 02 00 53 02 0E 00 03 00 54 02 0E 00 04
00 56 02 0E 00 05 00 F0 00 5D 80 01 00 ED 00 5E
80 01 00 4B 01 5F 80 01 00 4A 01 60 80 01 00 EA
00 0F 00 01 00 FF FF 00 00 00 00
Handle 0xDA01, DMI type 218, 251 bytes
OEM-specific Type
Header and Data:
DA FB 01 DA B2 00 0D 5F 0F 37 40 EB 00 0F 00 00
00 37 01 61 80 01 00 38 01 62 80 01 00 39 01 63
80 01 00 3D 03 66 80 01 00 3E 03 67 80 01 00 2E
02 07 80 01 00 2D 02 08 80 01 00 4F 03 09 80 01
00 50 03 0A 80 01 00 0E 01 64 80 01 00 0F 01 65
80 01 00 47 01 68 80 01 00 46 01 69 80 01 00 36
02 17 80 01 00 35 02 18 80 01 00 36 03 19 80 01
00 37 03 1A 80 01 00 3A 03 1B 80 01 00 3B 03 1C
80 01 00 41 03 1D 80 01 00 42 03 1E 80 01 00 43
03 1F 80 01 00 44 03 20 80 01 00 45 03 21 80 01
00 46 03 22 80 01 00 47 03 23 80 01 00 4B 03 24
80 01 00 4C 03 25 80 01 00 4A 02 0B 80 01 00 26
03 0C 80 01 00 5B 03 0D 80 01 00 5C 03 0E 80 01
00 5D 03 0F 80 01 00 5E 03 10 80 01 00 5F 03 11
80 01 00 60 03 12 80 01 00 0C 80 13 80 01 00 04
A0 14 80 01 00 FF FF 00 00 00 00
Handle 0xDA02, DMI type 218, 29 bytes
OEM-specific Type
Header and Data:
DA 1D 02 DA B2 00 0D 5F 0F 37 40 44 01 15 80 01
00 45 01 16 80 01 00 FF FF 00 00 00 00
Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: Dell Inc.
Version: A02
Release Date: 07/26/2013
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 2048 kB
Characteristics:
MCA is supported
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
ESCD support is available
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
CGA/mono video services are supported (int 10h)
ACPI is supported
USB legacy is supported
ATAPI Zip drive boot is supported
BIOS boot specification is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 0.2
Firmware Revision: 0.2
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: Dell Inc.
Product Name: XPS 12-9Q33
Version: A02
Serial Number: FZS4SY1
UUID: 4C4C4544-005A-5310-8034-C6C04F535931
Wake-up Type: Power Switch
SKU Number: XPS 12-9Q33
Family:
Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
Manufacturer: Dell Inc.
Product Name: XPS 12-9Q33
Version: A02
Serial Number: .FZS4SY1.CN1296139P0049.
Asset Tag: Not Specified
Features:
Board is a hosting board
Board is replaceable
Location In Chassis: To Be Filled By O.E.M.
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0
Handle 0x0003, DMI type 3, 22 bytes
Chassis Information
Manufacturer: Dell Inc.
Type: Portable
Lock: Not Present
Version: Not Specified
Serial Number: FZS4SY1
Asset Tag: Not Specified
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: None
OEM Information: 0x00000000
Height: Unspecified
Number Of Power Cords: 1
Contained Elements: 0
SKU Number: To be filled by O.E.M.
Handle 0x0008, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J1A1
Internal Connector Type: None
External Reference Designator: PS2Mouse
External Connector Type: PS/2
Port Type: Mouse Port
Handle 0x0009, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J1A1
Internal Connector Type: None
External Reference Designator: Keyboard
External Connector Type: PS/2
Port Type: Keyboard Port
Handle 0x000A, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J2A1
Internal Connector Type: None
External Reference Designator: TV Out
External Connector Type: Mini Centronics Type-14
Port Type: Other
Handle 0x000B, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J2A2A
Internal Connector Type: None
External Reference Designator: COM A
External Connector Type: DB-9 male
Port Type: Serial Port 16550A Compatible
Handle 0x000C, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J2A2B
Internal Connector Type: None
External Reference Designator: Video
External Connector Type: DB-15 female
Port Type: Video Port
Handle 0x000D, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J3A1
Internal Connector Type: None
External Reference Designator: USB1
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x000E, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J3A1
Internal Connector Type: None
External Reference Designator: USB2
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x000F, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J3A1
Internal Connector Type: None
External Reference Designator: USB3
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0010, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J9A1 - TPM HDR
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0011, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J9C1 - PCIE DOCKING CONN
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0012, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J2B3 - CPU FAN
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0013, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J6C2 - EXT HDMI
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0014, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J3C1 - GMCH FAN
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0015, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J1D1 - ITP
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0016, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J9E2 - MDC INTPSR
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0017, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J9E4 - MDC INTPSR
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0018, DMI type 9, 17 bytes
System Slot Information
Designation: J6B2
Type: x16 PCI Express
Current Usage: In Use
Length: Long
ID: 0
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Bus Address: 0000:00:01.0
Handle 0x0019, DMI type 9, 17 bytes
System Slot Information
Designation: J6B1
Type: x1 PCI Express
Current Usage: In Use
Length: Short
ID: 1
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Bus Address: 0000:00:1c.3
Handle 0x001A, DMI type 10, 6 bytes
On Board Device Information
Type: Video
Status: Enabled
Description: Mobile Intel HD Graphics
Handle 0x001B, DMI type 11, 5 bytes
OEM Strings
String 1: Dell System
String 2: 1[05E3h]
String 3: 3[1.0]
String 4: 4[0001]
String 5: 5[0000]
String 6: 6[D0, D4, D8, DA, DE]
String 7: 7[]
String 8: 8[]
String 9: 9[]
String 10: 10[A02]
String 11: 11[]
String 12: 12[]
String 13: 13[P20S]
String 14: 14[0]
String 15: 15[0]
Handle 0x001C, DMI type 12, 5 bytes
System Configuration Options
Option 1: To Be Filled By O.E.M.
Handle 0x001D, DMI type 21, 7 bytes
Built-in Pointing Device
Type: Touch Pad
Interface: Bus Mouse
Buttons: 2
Handle 0x001E, DMI type 22, 26 bytes
Portable Battery
Location: System Battery
Manufacturer: SDI
Manufacture Date: Not Specified
Serial Number: Not Specified
Name: DELL 7YM0739
Chemistry: Lithium Ion
Design Capacity: 51060 mWh
Design Voltage: 7400 mV
SBDS Version: 1.0
Maximum Error: 100%
OEM-specific Information: 0x00000001
Handle 0x001F, DMI type 32, 20 bytes
System Boot Information
Status: No errors detected
Handle 0x0021, DMI type 27, 12 bytes
Cooling Device
Type: Fan
Status: OK
OEM-specific Information: 0x00000000
Handle 0x0022, DMI type 28, 20 bytes
Temperature Probe
Description: CPU Internal Temperature
Location: Processor
Status: OK
Maximum Value: 127.0 deg C
Minimum Value: 0.0 deg C
Resolution: 1.000 deg C
Tolerance: 0.5 deg C
Accuracy: Unknown
OEM-specific Information: 0x00000000
Handle 0xB000, DMI type 176, 10 bytes
OEM-specific Type
Header and Data:
B0 0A 00 B0 00 00 00 00 E3 05
Handle 0xB100, DMI type 177, 12 bytes
OEM-specific Type
Header and Data:
B1 0C 00 B1 1A 06 00 00 00 00 00 00
Handle 0x0025, DMI type 208, 12 bytes
OEM-specific Type
Header and Data:
D0 0C 25 00 02 05 FE 00 E3 05 01 02
Strings:
20130614
20130924
Handle 0x0026, DMI type 212, 57 bytes
OEM-specific Type
Header and Data:
D4 39 26 00 70 00 71 00 01 49 50 48 9C 00 49 FC
01 9B 00 49 FC 00 7F 01 4A FB 04 80 01 4A FB 00
53 01 4A F7 08 52 01 4A F7 08 7B 01 4A EF 10 7C
01 4A EF 10 FF FF 00 00 00
Handle 0x0027, DMI type 216, 9 bytes
OEM-specific Type
Header and Data:
D8 09 27 00 01 02 01 00 00
Strings:
INTEL
0000
Handle 0x0028, DMI type 217, 8 bytes
OEM-specific Type
Header and Data:
D9 08 28 00 01 02 00 00
Strings:
Handle 0x0029, DMI type 219, 11 bytes
OEM-specific Type
Header and Data:
DB 0B 29 00 00 01 02 03 00 04 05
Strings:
Handle 0x002A, DMI type 220, 22 bytes
OEM-specific Type
Header and Data:
DC 16 2A 00 01 F0 00 00 02 F0 00 00 00 00 03 F0
04 F0 00 00 00 00
Handle 0x002B, DMI type 221, 19 bytes
OEM-specific Type
Header and Data:
DD 13 2B 00 00 00 00 00 00 03 00 00 00 00 00 00
00 00 00
Handle 0x002C, DMI type 222, 16 bytes
OEM-specific Type
Header and Data:
DE 10 2C 00 01 08 FF FF 00 00 00 00 00 00 00 00
Handle 0x002D, DMI type 4, 42 bytes
Processor Information
Socket Designation: SOCKET 0
Type: Central Processor
Family: Core i5
Manufacturer: Intel
ID: 51 06 04 00 FF FB EB BF
Signature: Type 0, Family 6, Model 69, Stepping 1
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
DS (Debug store)
ACPI (ACPI supported)
MMX (MMX technology supported)
FXSR (FXSAVE and FXSTOR instructions supported)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
SS (Self-snoop)
HTT (Multi-threading)
TM (Thermal monitor supported)
PBE (Pending break enabled)
Version: Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz
Voltage: 1.2 V
External Clock: 100 MHz
Max Speed: 3800 MHz
Current Speed: 1600 MHz
Status: Populated, Enabled
Upgrade: Socket rPGA988B
L1 Cache Handle: 0x0004
L2 Cache Handle: 0x0005
L3 Cache Handle: 0x0006
Serial Number: Not Specified
Asset Tag: Fill By OEM
Part Number: Fill By OEM
Core Count: 2
Core Enabled: 2
Thread Count: 4
Characteristics:
64-bit capable
Handle 0x0004, DMI type 7, 19 bytes
Cache Information
Socket Designation: CPU Internal L1
Configuration: Enabled, Not Socketed, Level 1
Operational Mode: Write Back
Location: Internal
Installed Size: 128 kB
Maximum Size: 128 kB
Supported SRAM Types:
Unknown
Installed SRAM Type: Unknown
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Other
Associativity: 8-way Set-associative
Handle 0x0005, DMI type 7, 19 bytes
Cache Information
Socket Designation: CPU Internal L2
Configuration: Enabled, Not Socketed, Level 2
Operational Mode: Write Back
Location: Internal
Installed Size: 512 kB
Maximum Size: 512 kB
Supported SRAM Types:
Unknown
Installed SRAM Type: Unknown
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Unified
Associativity: 8-way Set-associative
Handle 0x0006, DMI type 7, 19 bytes
Cache Information
Socket Designation: CPU Internal L3
Configuration: Enabled, Not Socketed, Level 3
Operational Mode: Write Back
Location: Internal
Installed Size: 3072 kB
Maximum Size: 3072 kB
Supported SRAM Types:
Unknown
Installed SRAM Type: Unknown
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Unified
Associativity: 12-way Set-associative
Handle 0x0007, DMI type 16, 23 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 16 GB
Error Information Handle: Not Provided
Number Of Devices: 2
Handle 0x0020, DMI type 17, 34 bytes
Memory Device
Array Handle: 0x0007
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 2048 MB
Form Factor: SODIMM
Set: None
Locator: ChannelA-DIMM0
Bank Locator: BANK 0
Type: DDR3
Type Detail: Synchronous
Speed: 1600 MHz
Manufacturer: Hynix/Hyundai
Serial Number: 00000001
Asset Tag: 0987654321
Part Number:
Rank: 1
Configured Clock Speed: 1600 MHz
Handle 0x0023, DMI type 20, 35 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0007FFFFFFF
Range Size: 2 GB
Physical Device Handle: 0x0020
Memory Array Mapped Address Handle: 0x002F
Partition Row Position: 2
Interleave Position: 1
Interleaved Data Depth: 1
Handle 0x0024, DMI type 17, 34 bytes
Memory Device
Array Handle: 0x0007
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 2048 MB
Form Factor: SODIMM
Set: None
Locator: ChannelB-DIMM0
Bank Locator: BANK 2
Type: DDR3
Type Detail: Synchronous
Speed: 1600 MHz
Manufacturer: Hynix/Hyundai
Serial Number: 00000002
Asset Tag: 0987654321
Part Number:
Rank: 1
Configured Clock Speed: 1600 MHz
Handle 0x002E, DMI type 20, 35 bytes
Memory Device Mapped Address
Starting Address: 0x00080000000
Ending Address: 0x000FFFFFFFF
Range Size: 2 GB
Physical Device Handle: 0x0024
Memory Array Mapped Address Handle: 0x002F
Partition Row Position: 2
Interleave Position: 1
Interleaved Data Depth: 1
Handle 0x002F, DMI type 19, 31 bytes
Memory Array Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x000FFFFFFFF
Range Size: 4 GB
Physical Array Handle: 0x0007
Partition Width: 2
Handle 0x0037, DMI type 131, 64 bytes
OEM-specific Type
Header and Data:
83 40 37 00 31 00 00 00 00 00 00 00 00 00 00 00
F8 00 43 9C 00 00 00 00 01 20 00 00 05 00 09 00
D1 05 02 00 00 00 00 00 C8 00 FF FF 00 00 00 00
00 00 00 00 26 00 00 00 76 50 72 6F 00 00 00 00
Handle 0x0038, DMI type 13, 22 bytes
BIOS Language Information
Language Description Format: Long
Installable Languages: 1
en|US|iso8859-1
Currently Installed Language: en|US|iso8859-1
Handle 0x0039, DMI type 127, 4 bytes
End Of Table
Last edited by fungi (2013-10-13 10:31:45)

Semi solved the problem by building a kernel with an ubuntu .config from http://kernel.ubuntu.com/~kernel-ppa/ma … y/current/
I think i have multi touch working on the touchscreen, but this has resulted in breakage of the synapic touchpad which is now operating in a very simple mode (no scrolling or multitouch).
Probably best to follow https://bugs.launchpad.net/ubuntu/+sour … ug/1218973 and http://thread.gmane.org/gmane.linux.kernel.input/32207 for a real solution

[Solved] No sound on Dell XPS 13 2015 (9343) with BIOS A03

I have been unable to get sound to work on my new 2015 Dell XPS 13 Developer Edition running kernel 4.0.1-1-ARCH. Arch is the only OS installed.
I have checked the wiki page and this forum post, which seems to indicate it should work with this configuration out of the box.
However, audio does not play through the speakers (the speakers were working in the original Ubuntu 14.04 installation) and when I tried to un-mute the volume, as described in the ALSA wiki page I received the following message:
$ amixer sset Master unmute
amixer: Unable to find simple control 'Master',0
I am not sure what other pertinent information to post, please forgive my ignorance and let me know. Thank you for your assistance.
Last edited by lkarunan (2015-05-17 13:42:47)

I have installed the patched kernel and rebooted twice but am still encountering the same problem. The only difference to altercation's instructions is that the aur package has been updated:
$ uname -r
4.0.2-1-xps13-alt
The output of amixer is identical to before. However, there are now two headphone channels visible in alsamixer, which were not present under the stock kernel.
┌─────────────────────── AlsaMixer v1.0.29 ────────────────────────┐
│ Card: HDA Intel PCH F1: Help │
│ Chip: Realtek ALC3263 F2: System information │
│ View: F3:[Playback] F4: Capture F5: All F6: Select sound card │
│ Item: Headphone Mic [dB gain: -16.50, -16Esc: Exit │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ ┌──┐ ┌──┐ ┌──┐ ┌──┐ ┌──┐ ┌──┐ ┌──┐ │
│ │▒▒│ │▒▒│ │ │ │▒▒│ │▒▒│ │▒▒│ │▒▒│ │
│ │▒▒│ │▒▒│ │ │ │▒▒│ │▒▒│ │▒▒│ │▒▒│ │
│ │▒▒│ │▒▒│ │ │ │▒▒│ │▒▒│ │▒▒│ │▒▒│ │
│ │▒▒│ │▒▒│ │ │ │▒▒│ │▒▒│ │▒▒│ │▒▒│ │
│ │▒▒│ │▒▒│ │ │ │▒▒│ │▒▒│ │▒▒│ │▒▒│ │
│ │▒▒│ │▒▒│ │ │ │▒▒│ │▒▒│ │▒▒│ │▒▒│ │
│ │▒▒│ │▒▒│ │ │ │▒▒│ │▒▒│ │▒▒│ │▒▒│ │
│ │▒▒│ │▒▒│ │ │ │▒▒│ │▒▒│ │▒▒│ │▒▒│ >
│ │▒▒│ │▒▒│ │ │ │▒▒│ │▒▒│ │▒▒│ │▒▒│ >
│ │▒▒│ │▒▒│ │ │ │▒▒│ │▒▒│ │▒▒│ │▒▒│ >
│ │▒▒│ │▒▒│ │ │ │▒▒│ │▒▒│ │▒▒│ │▒▒│ >
│ │▒▒│ │▒▒│ │ │ │▒▒│ │▒▒│ │▒▒│ │▒▒│ >
│ │▒▒│ │▒▒│ │ │ │▒▒│ │▒▒│ │▒▒│ │▒▒│ >
│ │▒▒│ │▒▒│ │ │ │▒▒│ │▒▒│ │▒▒│ │▒▒│ >
│ │▒▒│ │▒▒│ │ │ │▒▒│ │▒▒│ │▒▒│ │▒▒│ >
│ │▒▒│ │▒▒│ │ │ │▒▒│ │▒▒│ │▒▒│ │▒▒│ >
│ │▒▒│ │▒▒│ │ │ │▒▒│ │▒▒│ │▒▒│ │▒▒│ >
│ │▒▒│ │▒▒│ │ │ │▒▒│ │▒▒│ │▒▒│ │▒▒│ >
│ │▒▒│ │▒▒│ │ │ │▒▒│ │▒▒│ │▒▒│ │▒▒│ >
│ │▒▒│ │▒▒│ │ │ │▒▒│ │▒▒│ │▒▒│ │▒▒│ >
│ │▒▒│ │▒▒│ │ │ │▒▒│ │▒▒│ │▒▒│ │▒▒│ >
│ │▒▒│ │▒▒│ │ │ │▒▒│ │▒▒│ │▒▒│ │▒▒│ >
│ │▒▒│ │▒▒│ │ │ │▒▒│ │▒▒│ │▒▒│ │▒▒│ >
│ │▒▒│ │▒▒│ │ │ │▒▒│ │▒▒│ │▒▒│ │▒▒│ >
│ │▒▒│ │▒▒│ │ │ │▒▒│ │▒▒│ │▒▒│ │▒▒│ │
│ │▒▒│ │▒▒│ │▒▒│ │▒▒│ │▒▒│ │▒▒│ │▒▒│ │
│ │▒▒│ │▒▒│ │▒▒│ │▒▒│ │▒▒│ │▒▒│ │▒▒│ │
│ │▒▒│ │▒▒│ │▒▒│ │▒▒│ │▒▒│ │▒▒│ │▒▒│ │
│ │▒▒│ │▒▒│ │▒▒│ │▒▒│ │▒▒│ │▒▒│ │▒▒│ │
│ │▒▒│ │▒▒│ │▒▒│ │▒▒│ │▒▒│ │▒▒│ │▒▒│ │
│ │▒▒│ │▒▒│ │▒▒│ │▒▒│ │▒▒│ │▒▒│ │▒▒│ │
│ ├──┤ ├──┤ ├──┤ └──┘ ├──┤ └──┘ ├──┤ │
│ │OO│ │OO│ │OO│ │OO│ │OO│ │
│ └──┘ └──┘ └──┘ └──┘ └──┘ │
│ 100 100<>100 20<>20 100<>100 100<>100 100<>100 100<>100 │
│ Master Headphon<Headphon>Headphon Speaker PCM Beep │
│ │
│ │
│
The channel which is set at 20 gives a continuous "beep" (sine tone?) through headphones, when they are plugged into the jack.
This is the other sound card visible in alsamixer (and the one that is displayed by default):
┌─────────────────────── AlsaMixer v1.0.29 ────────────────────────┐
│ Card: HDA Intel HDMI F1: Help │
│ Chip: Intel Broadwell HDMI F2: System information │
│ View: F3:[Playback] F4: Capture F5: All F6: Select sound card │
│ Item: S/PDIF Esc: Exit │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ ┌───── Sound Card ──────┐ │
│ │- (default) │ │
│ │0 HDA Intel HDMI │ │
│ │1 HDA Intel PCH │ │
│ │ enter device name...│ │
│ └───────────────────────┘ │
│ < S/PDIF >S/PDIF 1 S/PDIF 2 │
│ │
│ │
─────────────────────── AlsaMixer v1.0.29 ────────────────────────┐
│ Card: HDA Intel HDMI F1: Help │
│ Chip: Intel Broadwell HDMI F2: System information │
│ View: F3:[Playback] F4: Capture F5: All F6: Select sound card │
│ Item: S/PDIF Esc: Exit │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ ┌──┐ ┌──┐ ┌──┐ │
│ │OO│ │OO│ │OO│ │
│ └──┘ └──┘ └──┘ │
│ < S/PDIF >S/PDIF 1 S/PDIF 2 │
│ │
The only other thing I have noticed in ~20 minutes of use are some graphical artefacts and flickering that occur with this kernel. I have previously set the Intel graphics acceleration to uxa, as described in the wiki, because of issues with virtual terminals and resuming from suspend. The graphical issues I am currently encountering are very minor, however.
Update:
Thanks to fumlead for this post. The problem seems to have been that the wrong card was set as default. Creating /etc/asound.conf and adding this:
pcm.!default {
type hw
card 1
has solved the problem under both the stock and aur kernels. I am going to stick with the stock kernel because of the graphical issues encountered with the alternate kernel. I am not currently using the audio jack for a microphone, which I believe should work for the alternate kernel but not the stock one.
There is a small bug with the speakers not automatically being silenced when headphones are plugged in, but hopefully that will be fixed in kernel 4.1.
Thank you to everyone who viewed and commented in this thread and special thanks to fumlead.
Last edited by lkarunan (2015-05-17 13:41:23)

Running VirtualBox in a Xen environment is not supported

Dear Experts,
The server is:
lsb_release -a
LSB Version: :core-3.1-amd64:core-3.1-ia32:core-3.1-noarch:graphics-3.1-amd64:graphics-3.1-ia32:graphics-3.1-noarch
Distributor ID: EnterpriseEnterpriseServer
Description: Enterprise Linux Enterprise Linux Server release 5.5 (Carthage)
Release: 5.5
Codename: Carthage
I tried installing VirtualBox.
rpm -ivh VirtualBox-4.1-4.1.8_75467_rhel5-1.x86_64.rpm
warning: VirtualBox-4.1-4.1.8_75467_rhel5-1.x86_64.rpm: Header V4 DSA signature: NOKEY, key ID 98ab5139
Preparing... ########################################### [100%]
1:VirtualBox-4.1 ########################################### [100%]
Creating group 'vboxusers'. VM users must be member of that group!
No precompiled module for this kernel found -- trying to build one. Messages
emitted during module compilation will be logged to /var/log/vbox-install.log.
Stopping VirtualBox kernel modules [ OK ]
Uninstalling old VirtualBox DKMS kernel modules [ OK ]
Trying to register the VirtualBox kernel modules using DKMS [FAILED]
(Failed, trying without DKMS)
Recompiling VirtualBox kernel modules [ OK ]
Starting VirtualBox kernel modules [FAILED]
(Running VirtualBox in a Xen environment is not supported)
But it did not install.
A retry gave the same result:
/etc/init.d/vboxdrv setup
Stopping VirtualBox kernel modules [ OK ]
Uninstalling old VirtualBox DKMS kernel modules [ OK ]
Removing old VirtualBox pci kernel module [ OK ]
Removing old VirtualBox netadp kernel module [ OK ]
Removing old VirtualBox netflt kernel module [ OK ]
Removing old VirtualBox kernel module [ OK ]
Trying to register the VirtualBox kernel modules using DKMS[FAILED]
(Failed, trying without DKMS)
Recompiling VirtualBox kernel modules [ OK ]
Starting VirtualBox kernel modules [FAILED]
(Running VirtualBox in a Xen environment is not supported)
What is the secret to getting Virtual Box to install?
Install the RPM: dkms?
If so, which RPM version would be the correct one?
Thanks a lot.

Thanks for responding. Lots of output below.
I've already installed 11G, Oracle Apps R12 and OBIEE on this server. If I use a different kernel, will everything still work? Alternatively, could I shut xen down, and be confident that everything will still work?
uname -a
Linux black.testrac.com 2.6.18-194.el5xen #1 SMP Mon Mar 29 22:22:00 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
xm info
host : black.testrac.com
release : 2.6.18-194.el5xen
version : #1 SMP Mon Mar 29 22:22:00 EDT 2010
machine : x86_64
nr_cpus : 8
nr_nodes : 1
sockets_per_node : 2
cores_per_socket : 4
threads_per_core : 1
cpu_mhz : 2493
hw_caps : bfebfbff:20100800:00000000:00000140:040ce3bd:00000000:00000001
total_memory : 16382
free_memory : 383
node_to_cpu : node0:0-7
xen_major : 3
xen_minor : 1
xen_extra : .2-194.el5
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : unavailable
cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-48)
cc_compile_by : mockbuild
cc_compile_domain : us.oracle.com
cc_compile_date : Mon Mar 29 22:07:53 EDT 2010
xend_config_format : 2
rpm -qa --qf "%{NAME}-%{VERSION}-%{RELEASE}_%{ARCH}.rpm \n " | grep "xen" | sort
kernel-xen-2.6.18-194.el5_x86_64.rpm
kernel-xen-devel-2.6.18-194.el5_x86_64.rpm
kmod-cmirror-xen-0.1.22-3.0.1.el5_x86_64.rpm
kmod-gfs-xen-0.1.34-12.el5_x86_64.rpm
kmod-gnbd-xen-0.1.5-2.0.1.el5_x86_64.rpm
ocfs2-2.6.18-194.el5xen-1.4.4-1.el5_x86_64.rpm
oracleasm-2.6.18-194.el5xen-2.0.5-1.el5_x86_64.rpm
xen-3.0.3-105.el5_x86_64.rpm
xen-libs-3.0.3-105.el5_i386.rpm
xen-libs-3.0.3-105.el5_x86_64.rpm
xm top:
xentop - 15:33:14 Xen 3.1.2-194.el5
1 domains: 1 running, 0 blocked, 0 paused, 0 crashed, 0 dying, 0 shutdown
Mem: 16775668k total, 16382760k used, 392908k free CPUs: 8 @ 2493MHz
NAME STATE CPU(sec) CPU(%) MEM(k) MEM(%) MAXMEM(k) MAXMEM(%) VCPUS NETS NETTX(k) NETRX(k) VBDS
VBD_OO VBD_RD VBD_WR SSID
Domain-0 -----r 414674 28.8 16015360 95.5 no limit n/a 8 5 172265 1798646 0
0 0 0 0
ps -efH | grep -i "xen"
root 37 35 0 2011 ? 00:00:00 [xenwatch]
root 38 35 0 2011 ? 00:00:00 [xenbus]
root 4400 1 0 2011 ? 00:00:00 xenstored --pid-file /var/run/xenstore.pid
root 4405 1 0 2011 ? 00:00:00 /usr/bin/python /usr/sbin/xend start
root 4406 4405 0 2011 ? 00:00:00 /usr/bin/python /usr/sbin/xend start
root 4408 1 0 2011 ? 00:00:00 xenconsoled --log none --timestamp none --log-dir /var/log/xen/console
root 17476 3439 0 15:32 pts/9 00:00:00 xentop
root 17577 3439 0 15:34 pts/9 00:00:00 grep -i xen
cat grub.conf
# grub.conf generated by anaconda
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/sda4
# initrd /initrd-version.img
#boot=/dev/sda1
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Enterprise Linux (2.6.18-194.el5xen)
root (hd0,0)
kernel /xen.gz-2.6.18-194.el5
module /vmlinuz-2.6.18-194.el5xen ro root=LABEL=/ rhgb quiet
module /initrd-2.6.18-194.el5xen.img
title Enterprise Linux-base (2.6.18-194.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-194.el5 ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.18-194.el5.img
title Other
rootnoverify (hd0,1)
chainloader +1
If I boot to a different kernel, say
title Enterprise Linux-base (2.6.18-194.el5)
will 11G, R12, and OBIEE still work?

When the message arrives, the message tone sound that many times. How this problem can be solved? I installed the new version, but the problem is not resolved, the future is to be taken into account in the new version of this?

When the message arrives, the message tone sound that many times. How this problem can be solved? I installed the new version, but the problem is not resolved, the future is to be taken into account in the new version of this?

I'm not sure I understand the question, is the message tone going more then once?
Turn off repeat message alert here:
settings > notifications > messages > repeat alert > never
Some people have found this does not stop the repeat miessage tone,
if you are one of those then I suggest you contact Apple:
http://www.apple.com/feedback/iphone.html
They may not respond, but hopefully will fix in uodate if enough people complain.

How to solve Audition CS6 error "The amount of audio to burn will not fit on the CD........."?

I have a brand new PC that is MORE than adequate. I have once succeeded in burning a CD after learning all about time tracks and merging them. (made a few with only ONE track)
Two things:
1) I find that I must add a CD marker at the end of the WAV because Audition CS6 erases whatever is the last CD marker I've made. Very frustrating but now I know I have to do this but I have no idea WHY!!
2) Right now I have a WAV that is just over 1 hour and 3 minutes with a total of 637.74MB of info. When I try to export/burn a CD, I get an error message stating "The amount of audio to burn will not fit.......". I am using TDK 700MB blanks with a Pioneer Blu-ray burner.
Obviously it will fit.
What am I doing wrong, all of a sudden?

Hey ryclark,
Thanks for responding. Something else is going on here.....
Here's what I re-replied to our friend...
Thanks for the response.
When I built this computer last Nov/Dec, it was built with the second
fastest Intel 7i, quad-core chipset on an 64-bit ASUS motherboard. It's running
Win 7 Pro. It has a 500GB SSD "C" drive with another 14 TB of true hard
drive space. It is set up with 64 bit. I had been using Audition CS3 for many
years and even go back to it's origin: Cool Edit and Cool Edit Pro. My
learning curve was minimal, sans the CD burning, which I used other software
for which is now antiquated, so I need Audition for this. Between this and
IZotope 3 I've repaired and improved many a recording. All-in-all extremely
useful software.
As for the idea "to burn it anyway", well the error message comes up and
that's it - if I "X" out of that message and try to burn again the message
comes back - so Audition will not let me. It is convinced that this file is
longer than it really is, but only when I add track marks to it!
There are only 11 tracks.
I was able to burn a CD of this same file but without all the track marks,
so the same exact file length/size will burn, only as the one track.
I've also succeeded in burning other WAV's , both greater and smaller, with
and without multiple track marks, without issue. Of course all with less
than the CD's max. capacity.
This problem seems to be with this one file. I've even re-made/re-recorded
the file from scratch with no change. There's something else going on here
that I can't put my finger on. (I am "recording" LP's and making personal
CDs of them)
Also, only from time to time, I have another error after burning a CD that
states it could not verify the CD. For this I assume it is the blank rather
than AA? The first might burn without issue and with the second burn I
get the error. It is near the end of a stack of blanks, so.....
As for the need to "mark the end" of the file makes a lot of sense but of
all the other CD track-marking software I've used, none needed one to do
this, but this IS Adobe after all.
You'd think there might be a smidge of intuitiveness with Adobe, but maybe
not.
- Mark
In a message dated 8/2/2014 8:11:52 A.M. Eastern Daylight Time,
[email protected] writes:
How to solve Audition CS6 error "The amount of audio to burn will not fit
on the CD........."?
created by ryclark (https://forums.adobe.com/people/ryclark) in
Audition CS5.5, CS6 & CC - View the full discussion
(https://forums.adobe.com/message/6605916#6605916)

SOLVED: Dell XPS 1530 wireless not configured properly , need help.

Had another post about different questions but after playing around with this for a few days I think that my wifi is not configured properly. Every thing looks good on the hardware and driver end and shows up properly.
This is my wifi card
grep -i wireless
0b:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:15:C5:84:7A:7C
inet addr:162.178.12.101 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::215:c5ff:fe84:7a7c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6225 errors:0 dropped:0 overruns:0 frame:0
TX packets:6557 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4309676 (4.1 Mb) TX bytes:996746 (973.3 Kb)
Interrupt:16
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:6 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:380 (380.0 b) TX bytes:380 (380.0 b)
wlan0 Link encap:Ethernet HWaddr 00:1C:BF:75:0A:1F
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
wmaster0 Link encap:UNSPEC HWaddr 00-1C-BF-75-0A-1F-00-00-00-00-00-00-00-00-00-00
[NO FLAGS] MTU:0 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
My rc.conf is asfollows.
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.utf8"
HARDWARECLOCK="local"
USEDIRECTISA="no"
TIMEZONE="America/Toronto"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=()
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="archtom"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
eth0="eth0 162.178.12.101 netmask 255.255.255.0 broadcast 192.168.0.255"
INTERFACES=(eth0 wlan0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 162.178.12.1"
#ROUTES=(!gateway)
ROUTES=(gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng network netfs crond alsa hal fam gdm)
Another think is the card is there and recognized but the led light is not on so the card is not actually turning on and that can be an issue so can not scan for networks or even bring wlan0 up as I get this error.
SIOCSIFFLAGS: No such file or directory
Your help would be greatly appreciated as though I have used Ubuntu and Fedora for years everything worked out of the box so this is new to me. He he breakage I love Arch , learning so much.
Last edited by TomWitko (2009-08-23 15:05:33)

Umm k looking into this and fixing this now. Went by the wiki page for the dell xps 1530 and it stated I needed the 65 driver, just figured out I have the 45 card so need the 45 driver. Will update later when I get it fixed.
K changed the driver and now can get wlan0 up ,, have to check out if everthing works now.
Last edited by TomWitko (2009-08-23 14:58:09)

[SOLVED] Dell XPS 15 l502x + GT 540M + Bumblebee: No devices detected

Hello everyone,
I have Dell XPS 15 l502x laptop with GT 540M graphics card with optimus support. I want to enable optimus with bumblebee, but no matter what I do I just can't make it work. I'm already start thinking that this laptop is not supported....
I've installed the following packages from AUR to support optimus on my laptop:
bumblebee
nvidia-bumblebee
nvidia-utils-bumblebee
Also, I am using my own custom configured kernel, uname -a shows:
Linux milktea 3.2.13-1-abs #1 SMP PREEMPT Wed Mar 28 14:16:29 CST 2012 i686 Intel(R) Core(TM) i7-2760QM CPU @ 2.40GHz GenuineIntel GNU/Linux
The only changes from ArchLinux default kernel is CPU architecture (I changed to Core 2 Duo and later instead of default i686) and support for PAE.
When I run optirun glxgears I get this output:
[ERROR]Cannot access secondary GPU - error: [XORG] (EE) Failed to load module "mouse" (module does not exist, 0)
[ERROR]Aborting because fallback start is disabled.
And Xorg.8.log is:
[ 4430.976]
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
[ 4430.976]
X.Org X Server 1.12.0.901 (1.12.1 RC 1)
Release Date: 2012-03-30
[ 4430.976] X Protocol Version 11, Revision 0
[ 4430.976] Build Operating System: Linux 3.3.0-1-ARCH i686
[ 4430.976] Current Operating System: Linux milktea 3.2.13-1-abs #1 SMP PREEMPT Wed Mar 28 14:16:29 CST 2012 i686
[ 4430.976] Kernel command line: root=/dev/sda3 ro initrd=../initramfs-linux-abs.img BOOT_IMAGE=../vmlinuz-linux-abs
[ 4430.976] Build Date: 31 March 2012 09:47:27AM
[ 4430.976]
[ 4430.976] Current version of pixman: 0.24.4
[ 4430.976] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 4430.976] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 4430.976] (==) Log file: "/var/log/Xorg.8.log", Time: Sat Apr 7 12:10:38 2012
[ 4430.977] (++) Using config file: "/etc/bumblebee/xorg.conf.nvidia"
[ 4430.977] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 4430.977] (==) ServerLayout "Layout0"
[ 4430.977] (**) |-->Screen "Screen0" (0)
[ 4430.977] (**) | |-->Monitor "Monitor0"
[ 4430.977] (**) | |-->Device "Device0"
[ 4430.977] (**) Option "AutoAddDevices" "false"
[ 4430.977] (**) Not automatically adding devices
[ 4430.977] (==) Automatically enabling devices
[ 4430.977] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 4430.977] Entry deleted from font path.
[ 4430.977] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 4430.977] Entry deleted from font path.
[ 4430.977] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 4430.977] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 4430.977] Entry deleted from font path.
[ 4430.977] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 4430.977] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/
[ 4430.977] (++) ModulePath set to "/usr/lib/nvidia-bumblebee/xorg/,/usr/lib/xorg/modules"
[ 4430.977] (==) |-->Input Device "<default pointer>"
[ 4430.977] (==) |-->Input Device "<default keyboard>"
[ 4430.977] (==) The core pointer device wasn't specified explicitly in the layout.
Using the default mouse configuration.
[ 4430.977] (==) The core keyboard device wasn't specified explicitly in the layout.
Using the default keyboard configuration.
[ 4430.977] (II) Loader magic: 0x82225a0
[ 4430.977] (II) Module ABI versions:
[ 4430.977] X.Org ANSI C Emulation: 0.4
[ 4430.977] X.Org Video Driver: 12.0
[ 4430.977] X.Org XInput driver : 16.0
[ 4430.977] X.Org Server Extension : 6.0
[ 4430.978] (--) PCI:*(0:1:0:0) 10de:0df4:1028:050e rev 161, Mem @ 0xf0000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x00003000/128, BIOS @ 0x????????/524288
[ 4430.978] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 4430.978] (II) LoadModule: "extmod"
[ 4430.979] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 4430.979] (II) Module extmod: vendor="X.Org Foundation"
[ 4430.979] compiled for 1.12.0.901, module version = 1.0.0
[ 4430.979] Module class: X.Org Server Extension
[ 4430.979] ABI class: X.Org Server Extension, version 6.0
[ 4430.979] (II) Loading extension MIT-SCREEN-SAVER
[ 4430.979] (II) Loading extension XFree86-VidModeExtension
[ 4430.979] (II) Loading extension XFree86-DGA
[ 4430.979] (II) Loading extension DPMS
[ 4430.979] (II) Loading extension XVideo
[ 4430.979] (II) Loading extension XVideo-MotionCompensation
[ 4430.979] (II) Loading extension X-Resource
[ 4430.979] (II) LoadModule: "dbe"
[ 4430.979] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 4430.979] (II) Module dbe: vendor="X.Org Foundation"
[ 4430.979] compiled for 1.12.0.901, module version = 1.0.0
[ 4430.979] Module class: X.Org Server Extension
[ 4430.979] ABI class: X.Org Server Extension, version 6.0
[ 4430.979] (II) Loading extension DOUBLE-BUFFER
[ 4430.979] (II) LoadModule: "glx"
[ 4430.979] (II) Loading /usr/lib/nvidia-bumblebee/xorg/modules/extensions/libglx.so
[ 4430.998] (II) Module glx: vendor="NVIDIA Corporation"
[ 4430.998] compiled for 4.0.2, module version = 1.0.0
[ 4430.998] Module class: X.Org Server Extension
[ 4430.998] (II) NVIDIA GLX Module 295.33 Sat Mar 17 15:18:29 PDT 2012
[ 4430.999] (II) Loading extension GLX
[ 4430.999] (II) LoadModule: "record"
[ 4430.999] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 4430.999] (II) Module record: vendor="X.Org Foundation"
[ 4430.999] compiled for 1.12.0.901, module version = 1.13.0
[ 4430.999] Module class: X.Org Server Extension
[ 4430.999] ABI class: X.Org Server Extension, version 6.0
[ 4430.999] (II) Loading extension RECORD
[ 4430.999] (II) LoadModule: "dri"
[ 4430.999] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 4430.999] (II) Module dri: vendor="X.Org Foundation"
[ 4430.999] compiled for 1.12.0.901, module version = 1.0.0
[ 4430.999] ABI class: X.Org Server Extension, version 6.0
[ 4430.999] (II) Loading extension XFree86-DRI
[ 4430.999] (II) LoadModule: "dri2"
[ 4430.999] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 4430.999] (II) Module dri2: vendor="X.Org Foundation"
[ 4430.999] compiled for 1.12.0.901, module version = 1.2.0
[ 4430.999] ABI class: X.Org Server Extension, version 6.0
[ 4430.999] (II) Loading extension DRI2
[ 4431.000] (II) LoadModule: "intel"
[ 4431.000] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 4431.000] (II) Module intel: vendor="X.Org Foundation"
[ 4431.000] compiled for 1.11.99.903, module version = 2.18.0
[ 4431.000] Module class: X.Org Video Driver
[ 4431.000] ABI class: X.Org Video Driver, version 12.0
[ 4431.000] (II) LoadModule: "mouse"
[ 4431.000] (WW) Warning, couldn't open module mouse
[ 4431.000] (II) UnloadModule: "mouse"
[ 4431.000] (II) Unloading mouse
[ 4431.000] (EE) Failed to load module "mouse" (module does not exist, 0)
[ 4431.000] (II) LoadModule: "kbd"
[ 4431.001] (WW) Warning, couldn't open module kbd
[ 4431.001] (II) UnloadModule: "kbd"
[ 4431.001] (II) Unloading kbd
[ 4431.001] (EE) Failed to load module "kbd" (module does not exist, 0)
[ 4431.001] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server
[ 4431.001] (--) using VT number 7
[ 4431.001] (EE) No devices detected.
[ 4431.001]
Fatal server error:
[ 4431.001] no screens found
[ 4431.001]
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 4431.001] Please also check the log file at "/var/log/Xorg.8.log" for additional information.
[ 4431.001]
Does anyone have any ideas on what might be wrong? Please, help.
Thanks in advance.
Last edited by leonid (2012-04-12 01:55:31)

I have bumblebee, dkms-bbswitch, nvidia-utils-bumblebee, nvidia, virtualgl
My bumblebee.conf is:
# Configuration file for Bumblebee. Values should **not** be put between quotes
## Server options. Any change made in this section will need a server restart
# to take effect.
[bumblebeed]
# The secondary Xorg server DISPLAY number
VirtualDisplay=:8
# Should the unused Xorg server be kept running? Set this to true if waiting
# for X to be ready is too long and don't need power management at all.
KeepUnusedXServer=false
# The name of the Bumbleblee server group name (GID name)
ServerGroup=bumblebee
# Card power state at exit. Set to false if the card shoud be ON when Bumblebee
# server exits.
TurnCardOffAtExit=true
# The default behavior of '-f' option on optirun. If set to "true", '-f' will
# be ignored.
NoEcoModeOverride=false
# The Driver used by Bumblebee server. If this value is not set (or empty),
# auto-detection is performed. The available drivers are nvidia and nouveau
# (See also the driver-specific sections below)
Driver=nvidia
## Client options. Will take effect on the next optirun executed.
[optirun]
# The method used for VirtualGL to transport frames between X servers.
# Possible values are proxy, jpeg, rgb, xv and yuv.
VGLTransport=proxy
# Should the program run under optirun even if Bumblebee server or nvidia card
# is not available?
AllowFallbackToIGC=false
# Driver-specific settings are grouped under [driver-NAME]. The sections are
# parsed if the Driver setting in [bumblebeed] is set to NAME (or if auto-
# detection resolves to NAME).
# PMMethod: method to use for saving power by disabling the nvidia card, valid
# values are: auto - automatically detect which PM method to use
# bbswitch - new in BB 3, recommended if available
# switcheroo - vga_switcheroo method
# none - disable PM completely
# https://github.com/Bumblebee-Project/Bumblebee/wiki/Comparison-of-PM-methods
## Section with nvidia driver specific options, only parsed if Driver=nvidia
[driver-nvidia]
# Module name to load, defaults to Driver if empty or unset
KernelDriver=nvidia
Module=nvidia
PMMethod=bbswitch
# colon-separated path to the nvidia libraries
LibraryPath=/usr/lib/nvidia-bumblebee:/usr/lib32/nvidia-bumblebee
# comma-separated path of the directory containing nvidia_drv.so and the
# default Xorg modules path
XorgModulePath=/usr/lib/nvidia-bumblebee/xorg/,/usr/lib/xorg/modules
XorgConfFile=/etc/bumblebee/xorg.conf.nvidia
## Section with nouveau driver specific options, only parsed if Driver=nouveau
[driver-nouveau]
KernelDriver=nouveau
PMMethod=bbswitch
XorgConfFile=/etc/bumblebee/xorg.conf.nouveau
I haven't edited any xorg.conf files whatsoever, so they are just the default ones. Here is /etc/bumblebee/xorg.conf.nvidia:
Section "ServerLayout"
Identifier "Layout0"
Option "AutoAddDevices" "false"
EndSection
Section "Device"
Identifier "Device1"
Driver "nvidia"
VendorName "NVIDIA Corporation"
Option "NoLogo" "true"
Option "UseEDID" "false"
Option "ConnectedMonitor" "DFP"
EndSection
What are the full relevant sections in lspci -vvnn saying? your grepping removed the verbose bits. e.g. when my nvidia card is off, it gives:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF108 [GeForce GT 540M] [10de:0df5] (rev ff) (prog-if ff)
!!! Unknown header type 7f
but different when it's turned on.

[SOLVED] Arch as Guest on VirtualBox on a Dell XPS 15 - Wireless Not..

Similar Messages

Maybe you are looking for