[SOLVED] network is not detected r8169 module is not loaded

Hey there,
I have problems to get my archlinux server running, it has no network.
It's a server at kimsufi so I only can chroot in the new installation.
It looks like the module 'r8169' isn't loaded at start, so it has no network.
After adding '/etc/modules-load.d/r8169.conf' with 'r8169' inside (w/o quotes) the journalctl says:
systemd-modules-load[92]: Failed to lookup alias 'r8169': Function not implemented
The installation is up-to-date, newest kernel.
I hope you have some ideas how to get that module loaded.
Greetings
edit: I tried it just now again and it worked atm. If network will work completely, I will mark this thread as solved.
Last edited by lookingaty (2014-02-14 21:19:43)

I'm sorry that I opened the thread.
I had built myself a kernel with kdump and had set debug and loglevel=7 parameters.
Either one of the parameter was bad or my buildprocess was bad.
Now (with the original kernel) I don't get that error and the module is loading fine.
I have (after about a month) the server up and running.
At least I got some new experience.
Last edited by lookingaty (2014-02-14 21:23:48)

Similar Messages

[SOLVED]Custom DSDT not loading - OEM battery doesn't work - Sony Vaio

EDITING ORIGINAL POST TO POST SOLUTION so I don't do a massive bump
Installed windows and ran the BIOS flasher that came with the battery. Didn't work until I changed a line in the plaintext configuration file (config.ini or something) it comes with. Changed "Capacity: 20" to "Capacity: -10". This changed the battery charge requirement from 20% to negative ten percent (any negative number will do), allowing the program to run and flash the BIOS. Didn't realize I could do that, but it fixed the problem 100%.
#### BEGIN ORIGINAL POST: ################################
Hey guys,
I'm a bit of a linux noob, but I've spent many hours this week trying to fix this issue on my own and have learned a lot about making custom kernels, hardware stuff, ACPI, and ABS. However, nothing I've done has worked and I've hit a wall. For reference, I'm on a Sony Vaio VGN-FZ4000 with linux-3.0 base kernel, gnome3/gdm. The battery is made in china and doesn't list a manufacturer, just model number BPS8, 52000mAh.
[Backstory]
So I recently got an OEM battery to replace the broken original, which hasn't worked since before I installed arch (though it worked with an Arch install I did a couple years ago). When I first plugged it in, the gnome battery symbol popped up listing the battery at 0% with an exclamation icon. I unplugged from AC power and the laptop still ran, but the battery monitor just said it was at 0% and 'Estimating' remaining time. I figured this was a glitch with gnome or just because it was this battery's first cycle so I let it run down until it hard-crashed. Then I plugged back into AC and tried to turn on the computer, but it wouldn't do anything until I removed the battery.
Looking into the problem I discovered this was due to the ACPI firmware table DSDT being compiled for Windows, which has, shall we say, fewer restrictions on sanity than the Intel ASL compiler used for UNIX systems. Sure enough I extracted /sys/firmware/acpi/tables/DSDT to find that its section about the battery contained the entry 'Zero' for Battery Technology, which translates to "non-rechargeable", rather than 'One', which makes it chargeable. acpitool confirmed this; my system thought the battery was non-rechargeable and was constantly discharging it. Needless to say I've only been putting it in temporarily to test solutions since.
[/backstory]
[tl;dr] DSDT firmware contains malformed battery description, now I can't get my system to run with a custom DSDT. [/tl;dr]
Attempted solutions:
[1]
Extract, modify, recompile DSDT and include it with the kernel compilation .config options
CONIFG_ACPI_CUSTOM_DSDT=y
CONFIG_ACPI_CUSTOM_DSDT_FILE="/usr/src/custom_dsdt.hex
CONIFG_STANDALONE=n
as suggested here, a page linked to by the arch wiki page on DSDT.
I followed the instructions but no matter what this has generated errors during the kernel compilation, sometimes due to every line containing unexpected \231 (or other numbers) characters, sometimes finding some error in the DSDT file and then claiming that the driver it was compiling (ol.c somewhere in the drivers/acpi section I believe) had references to undefined functions all over the place. I CANNOT compile with a custom DSDT specified.
[2]
Place recompiled DSDT in /lib/initcpio/custom.dsdt and add 'dsdt' to the HOOKS in mkinitcpio (and rebuild the initramfs-linux-*.img, of course). Another version of this included recompiling the kernel with CONFIG_STANDALONE disabled.
In neither of these situations has the running DSDT ever been anything but the BIOS-supplied one and not once has the battery shown any different behavior.
acpitool and $ cat /proc/acpi/battery/BAT0/info have consistently claimed the information specified in the BIOS-supplied DSDT; the battery is non-rechargeable and is discharging at an unknown rate. Sometimes acpi will even report that the battery has zero capacity.
The arch wiki does say mkinitcpio doesn't support the dsdt hook as of 2.6.30, but [1] didn't work either and mkinitcpio -H dsdt still told me to try this so I did.
[3]
The final solution I have tried has been to do [2] but to recompile the kernel with the legacy support for battery and ac adapter stuff disabled. I tried this because it was suggested in the kernel.log;
Sep 13 11:51:03 localhost kernel: [ 11.740059] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Sep 13 11:51:03 localhost kernel: [ 11.753434] ACPI: AC Adapter [ADP1] (on-line)
The corresponding line now reads
ACPI: AC Adapter [ADP1] (on-line)
(The same goes for the battery BAT0)
but all this does is remove the battery/ and adp1/ folders from /proc/acpi/ and break acpitool functionality. The log still doesn't mention the dsdt hook, either.
[4]
The old way to do this was to use the acpi-dsdt-initrd-patch-* patch, but that hasn't been updated for modern kernels, presumably because of the new "functionality" from mkiniticpio. The current kernel .config doesn't include any options for ACPI initrd/initramfs support or reading a DSDT from initramfs, which is the functionality provided by this patch.
This covers all the methods I've been able to find on the internet and I'm at a loss for what to do. Am I doing something wrong in [1]? Under what conditions will the compiler fail/succeed with a CONFIG_ACPI_CUSTOM_DSDT_FILE?
When I recompile I fix the 'Zero' definition and a couple compiler errors and warnings. The errors come from section length definitions, which read as 0x00000000 rather than the appropriate max-min value so I fix those, and the warnings come from _T_* methods belonging to the compiler, so I refactor the code to remove the initial underscores. The last warning comes from an isolated And statement that's within brackets (compiler complains it doesn't do anything), but if I remove that the compiler fails hard.
Thanks to anyone who's read this far. Please let me know if you have any ideas how to get my system to use a customized DSDT.
Last edited by paraffin (2011-09-29 23:20:30)

Thanks for the offer, Radioactive man However, I'm actually compiling a customized kernel with the linux-ck and -sony patches, so your packages won't help. (The custom kernel works fine and I've tested this battery behavior on the the regular, -ck, and -sony kernels as well)
Anyway, so I tried another compile with
CONFIG_PREVENT_FIRMWARE_BUILD=n in addition to the options listed in [1] and that time it compiled.
Unfortunately it still didn't load the DSDT!
I did catch a quick little error message that turned up in kernel.log though;
/var/log/kernel.log:Sep 15 11:50:24 localhost kernel: [ 0.925780] acerhdf: unknown (unsupported) BIOS version Sony Corporation/VGN-FZ4000E/R2110J7, please report, aborting!
acerhdf is a fan controller module for the Aspire One, and perhaps I left that in the kernel config and it's preventing the custom DSDT from loading, even though the acerhdf module never gets loaded itself, nor is it in my rc.conf or anything else... If that was the cause of all this, I'm gonna be angry...
Anyway, this message does not appear with my latest kernel build because I took off the custom DSDT option, hoping to be able to use ACPI_CUSTOM_METHOD=y, which supposedly allows one to inject a custom AML method into a debug fs. It wouldn't have worked anyway, as it doesn't let you modify Device sections, but even with a dummy method insertion it didn't give my root modification privileges as it was supposed to...
Will try recompiling AGAIN with this CONFIG_ACERHDF=n (it's simply 'not set' in my current .config), while also enabling the custom kernel etc. If this doesn't work I have no idea what I'll do.
Anyway, thanks for your help and time:

[solved] TV card not loaded after upgrade to kmod

After the upgrade to mkinitcpio and kmod replacing module-init-tools, my TV card (Hauppauge WinTV Nova-S) is not loaded.
Downgrading mkinitcpio and re-installing module-init-tools and regenerating my initramfs and all is well.
Is there any extra setup needed with kmod? There are no man files in the kmod package so I'm at a loss what to do.
Incase it helps, here are (maybe not all) the modules related to my tv card when downgraded:
-->lsmod | grep dvb
cx88_dvb 23415 39
cx88_vp3054_i2c 1932 1 cx88_dvb
videobuf_dvb 4794 1 cx88_dvb
dvb_core 92868 2 cx88_dvb,videobuf_dvb
cx8802 13121 1 cx88_dvb
cx88xx 73365 4 cx88_dvb,cx88_alsa,cx8800,cx8802
videobuf_dma_sg 7936 5 cx88_dvb,cx88_alsa,cx8800,cx8802,cx88xx
videobuf_core 15879 5 videobuf_dvb,cx8800,cx8802,cx88xx,videobuf_dma_sg
i2c_core 20492 15 isl6421,cx24123,wm8775,cx88_dvb,cx88_vp3054_i2c,cx8800,cx88xx,tveeprom,v4l2_common,videodev,i2c_piix4,nouveau,drm_kms_helper,drm,i2c_algo_bit
Last edited by fastfret79 (2012-01-10 22:29:35)

Yes - initramfs regenerated after each upgrade and downgrade.
Forgot to mention I was also suffering from the 'Filename too long' FS#27862 and your updated kmod in that bug's comments fixed that. I'm guessing that my issue is unrelated.
With both kmod packages, initramfs complains that /etc/modprobe.d/modprobe.conf doesn't exist, but I've never added anything in there anyway and the kmod package doesn't contain that file.
Last edited by fastfret79 (2012-01-10 11:53:07)

[Solved] Menu Editor not loading.

I installed py solitaire, it didn't show up in the list. I tried to open up the menu editor, and that will not load either. I have fam and alacarte installed, and I am not sure what is wrong. Any help would be greatly appreciated.
Edit: alacarte will not run as a normal user, only as root. Is this normal?
Last edited by perlluver (2008-02-24 21:45:37)

perlluver wrote:
I installed py solitaire, it didn't show up in the list. I tried to open up the menu editor, and that will not load either. I have fam and alacarte installed, and I am not sure what is wrong. Any help would be greatly appreciated.
Edit: alacarte will not run as a normal user, only as root. Is this normal?
Ok I ran menu editor from the terminal and I got this message:
** (gmenu-simple-editor:7417): WARNING **: Failed to add monitor on '/home/perlluver/.config/menus/applications.menu': Permission denied
** (gmenu-simple-editor:7417): WARNING **: Failed to add monitor on '/home/perlluver/.config/menus/applications-merged': Permission denied
** (gmenu-simple-editor:7417): WARNING **: Failed to add monitor on '/home/perlluver/.config/menus/settings.menu': Permission denied
** (gmenu-simple-editor:7417): WARNING **: Failed to add monitor on '/home/perlluver/.config/menus/settings-merged': Permission denied
** (gmenu-simple-editor:7417): WARNING **: Failed to add monitor on '/home/perlluver/.config/menus/preferences-merged': Permission denied

[Solved] Synaptics driver not loaded

Recently im getting
Couldn't find synaptics properties. No synaptics driver loaded?
when I run synclient
Touchpad still works but the synaptics driver is apparently not loaded. I have xf86-input-synaptics installed.
I can't figure out how to load the synaptics driver.
Last edited by Mythreya (2015-03-10 12:45:34)

This started after an update about a week ago. It was working perfectly fine with no effort before. I have an elantech touchpad.
$ xinput list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ ETPS/2 Elantech Touchpad id=17 [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)]
↳ Video Bus id=8 [slave keyboard (3)]
↳ Power Button id=9 [slave keyboard (3)]
↳ Sleep Button id=10 [slave keyboard (3)]
↳ ASUS USB2.0 Webcam id=14 [slave keyboard (3)]
↳ Asus WMI hotkeys id=15 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=16 [slave keyboard (3)]
↳ USB Keyboard id=11 [slave keyboard (3)]
↳ USB Keyboard
I've mostly found ubuntu forums with the issue, they all linked to the debian wiki on synaptics which didn't help much. Even the allmighty archwiki had no troubleshooting instructions for synaptics.
Last edited by Mythreya (2015-03-06 18:12:37)

[SOLVED] Network shares not shown in File Explorers

Hi.
I absolutely love Arch and I am big fan because it forces me to learn...
Time to start noob linux questions , I am sorry...
So....
In any GUI file manager I am not able to see most of my network shares... Till this point I was mainly using Mint, Ubuntu etc and obviously everything comes preconfigured, so I never had this problem.
I have installed Manjaro on same machine just to see if I will have same problem, but there I am able to browse network shares on Nautilus and Nemo out of the box. On Arch I can find only local host and one other share (as on the picture).
Initially I have thought that this is due to network configuration but I have checked with
smbtree -U
and I get:
WORKGROUP
\\WDMYCLOUD WD My Cloud
\\WDMYCLOUD\Public Public
\\WDMYCLOUD\BrightSide
\\WDMYCLOUD\Aneta
\\WDMYCLOUD\Piotr
\\WDMYCLOUD\IPC$ IPC Service (WD My Cloud)
\\ROUTER Router
\\MINTSERVER MintServer server (Samba, Linux Mint)
\\MINTSERVER\SamsungPrinter Samsung Printer on Mint Server
\\MINTSERVER\print$ Printer Drivers
\\MINTSERVER\DyskDomowy1
\\MINTSERVER\IPC$ IPC Service (MintServer server (Samba, Linux Mint))
\\KOMPUTER_MADZI
So Samba is discovering just fine...
I tried to research on it but no luck so far, maybe I am looking for wrong thing.
Can someone point me out what I am missing here? Should I enable some sort of service to be able to see and browse those shares in file explorers?
Thanks for any kind tip
Last edited by hede0n (2015-01-21 19:43:50)

Ok.....
After few reboots it started to work on its own....

[Solved] Network does not starts on every boot

Yet another problem on fresh arch...
Network service does not starts every time I booting my headless. For every 10 attempts service starts 5 or 6 times only.
Ping says: Networking unreachable.
systemctl status network:
network.service - Static IP Connectivity
Loaded: loaded (/etc/systemd/system/network.service; enabled)
Active: inactive (dead)
'systemctl start network' just hangs. In order to get it start I have to reboot the box hoping next boot service will start.
I am not using dhcp (if it makes a sence). Service was configured as described in wiki for static IP assigning.
The config itself:
[Unit]
Description=Static IP Connectivity
Wants=network.target
Before=network.target
BindsTo=sys-subsystem-net-devices-enp4s1.device
After=sys-subsystem-net-devices-enp4s1.device
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/sbin/ip link set dev enp4s1 up
ExecStart=/sbin/ip addr add 192.168.1.5/24 dev enp4s1
ExecStart=/sbin/ip route add default via 192.168.1.1
ExecStop=/sbin/ip addr flush dev enp4s1
ExecStop=/sbin/ip link set dev enp4s1 down
[Install]
WantedBy=multi-user.target
What's wrong?
Thanks in advance for any help.
Last edited by chord (2013-06-03 17:04:55)

Thaks for your reply.
I got this interface name from ip addr, how it should be named if 'enp4s1' is wrong?
journalctl is here: http://bpaste.net/show/104083/
I found only one string realted to this device name:
Jun 03 15:18:23 localhost systemd[1]: Expecting device sys-subsystem-net-devices-enp4s1.device...
Is there some other logs where it can be checked?

[SOLVED] network does not work at bootup

the only way i can get the network to work is by doing dhcpcd eth0 at root. how to set it up so that it works at bootup?
Last edited by stevestark (2010-08-24 22:31:18)

http://wiki.archlinux.org/index.php/Beginners'_Guide#NETWORKING_Section

[SOLVED] Network Manager not working after disabling GDM daemon

Morning All,
1st post so go easy on me.
I have recently setup Arch on a Samsung Q320 notebook, using GNOME DE and enabling gdm. Everything is working fine installed network manager no probs it connects to wireless network each time I login, really impressed with the distro. However I have been playing around with it a bit and when a disable the 'gdm' daemon by prefixing it with '!' in /etc/rc.conf, then reboot then login in with username & pw, and 'startx' GNOME DE starts fine however network manager fails to start, it is still located in the preferences menu I can open it and see the networks I have created previously however cannot join any of them. Can shed any light on the situation.
Cheers
Chris
Last edited by phatrat (2010-03-12 21:24:49)

just add in ~/.xinitrc
exec ck-launch-session gnome-session

[SOLVED] ALSA firmware not loading properly with kernel 3.8.6-1

Hi All,
I have a E-MU 1820 card + breakout box that have been working beautiful under Archlinux for years but now something happen.
It still work OK under windows (dual boot same computer).
Normally during boot all indicators on the breakout box blink and then only thin show is clock setting indicator. But now all the indicators still blink but instead it is a -12 dB indicator that light up and not the clock settings and no sound.
dmesg show following.
[christer@Arch ~]$ dmesg | grep emu
[ 5.269612] emu1010: Special config.
[ 5.269731] emu1010: EMU_HANA_ID = 0x7f
[ 5.274685] emu1010: firmware file = emu/hana.fw, size = 0x133a4
[ 13.465727] emu1010: Hana Firmware loaded
[ 13.465776] emu1010: Hana version: 3.4
[ 13.465864] emu1010: Card options = 0x0
[ 13.465888] emu1010: Card options = 0x0
[ 13.466379] emu1010: Card options3 = 0x0
[ 14.486723] emu1010: Loading Audio Dock Firmware
[ 16.477785] emu1010: EMU_HANA+DOCK_IRQ_STATUS = 0x36
[ 16.477809] emu1010: EMU_HANA+DOCK_ID = 0x55
[ 16.477809] emu1010: Audio Dock Firmware loaded
[christer@Arch ~]$
aplay -l looks like it did before.
[christer@Arch ~]$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: EMU1010 [E-mu 1010 [MAEM8810]], device 0: emu10k1 [ADC Capture/Standard PCM Playback]
Subdevices: 32/32
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7
Subdevice #8: subdevice #8
Subdevice #9: subdevice #9
Subdevice #10: subdevice #10
Subdevice #11: subdevice #11
Subdevice #12: subdevice #12
Subdevice #13: subdevice #13
Subdevice #14: subdevice #14
Subdevice #15: subdevice #15
Subdevice #16: subdevice #16
Subdevice #17: subdevice #17
Subdevice #18: subdevice #18
Subdevice #19: subdevice #19
Subdevice #20: subdevice #20
Subdevice #21: subdevice #21
Subdevice #22: subdevice #22
Subdevice #23: subdevice #23
Subdevice #24: subdevice #24
Subdevice #25: subdevice #25
Subdevice #26: subdevice #26
Subdevice #27: subdevice #27
Subdevice #28: subdevice #28
Subdevice #29: subdevice #29
Subdevice #30: subdevice #30
Subdevice #31: subdevice #31
card 0: EMU1010 [E-mu 1010 [MAEM8810]], device 2: emu10k1 efx [Multichannel Capture/PT Playback]
Subdevices: 8/8
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7
card 0: EMU1010 [E-mu 1010 [MAEM8810]], device 3: emu10k1 [Multichannel Playback]
Subdevices: 1/1
Subdevice #0: subdevice #0
[christer@Arch ~]$
lsmod
[christer@Arch ~]$ lsmod | grep emu
snd_emu10k1 140245 1
snd_util_mem 2403 1 snd_emu10k1
snd_hwdep 6428 1 snd_emu10k1
snd_ac97_codec 113456 1 snd_emu10k1
snd_rawmidi 18831 1 snd_emu10k1
snd_seq_device 5268 5 snd_seq,snd_rawmidi,snd_seq_oss,snd_emu10k1,snd_seq_dummy
snd_pcm 78146 3 snd_pcm_oss,snd_ac97_codec,snd_emu10k1
snd_page_alloc 7426 2 snd_pcm,snd_emu10k1
snd_timer 18934 3 snd_pcm,snd_seq,snd_emu10k1
snd 60156 13 snd_pcm_oss,snd_ac97_codec,snd_hwdep,snd_timer,snd_pcm,snd_seq,snd_rawmidi,snd_seq_oss,snd_emu10k1,snd_seq_device,snd_mixer_oss
[christer@Arch ~]$
From what I can see all looks OK, like it did when it worked, but something is not at it should.
Any thoughts or ideas about what might have happen or how to progress in troubleshooting.
All input most welcome.
I found info describing problem with firmware loading, but it is over my head.
http://git.kernel.org/cgit/linux/kernel … 54cf7008ab
Output from Aadebug ( http://alsa.opensrc.org/Aadebug )
[christer@Arch ~]$ ./alsadebug
ALSA Audio Debug v0.2.0 - Fri Apr 12 20:46:05 CEST 2013
http://alsa.opensrc.org/aadebug
http://www.gnu.org/licenses/agpl-3.0.txt
Kernel ----------------------------------------------------
Linux Arch 3.8.6-1-ARCH #1 SMP PREEMPT Sat Apr 6 07:27:01 CEST 2013 x86_64 GNU/Linux
Advanced Linux Sound Architecture Driver Version k3.8.6-1-ARCH.
Loaded Modules --------------------------------------------
snd_emu10k1 139271 2
snd_util_mem 2339 1 snd_emu10k1
snd_hwdep 6364 1 snd_emu10k1
snd_pcm_oss 38511 0
snd_mixer_oss 14995 1 snd_pcm_oss
snd_ac97_codec 112216 1 snd_emu10k1
snd_seq_dummy 1463 0
snd_seq_oss 29098 0
snd_seq_midi_event 5660 1 snd_seq_oss
snd_rawmidi 18742 1 snd_emu10k1
snd_seq 49946 5 snd_seq_midi_event,snd_seq_oss,snd_seq_dummy
snd_seq_device 5180 5 snd_seq,snd_rawmidi,snd_seq_oss,snd_emu10k1,snd_seq_dummy
snd_pcm 76956 4 snd_pcm_oss,snd_ac97_codec,snd_emu10k1
snd_page_alloc 7298 2 snd_pcm,snd_emu10k1
snd_timer 18687 3 snd_pcm,snd_seq,snd_emu10k1
snd 58893 14 snd_pcm_oss,snd_ac97_codec,snd_hwdep,snd_timer,snd_pcm,snd_seq,snd_rawmidi,snd_seq_oss,snd_emu10k1,snd_seq_device,snd_mixer_oss
Proc Asound -----------------------------------------------
0 [EMU1010 ]: Audigy2 - E-mu 1010 [MAEM8810]
E-mu 1010 [MAEM8810] (rev.3, serial:0x40011102) at 0xd000, irq 19
1: : sequencer
2: [ 0- 0]: hardware dependent
3: [ 0- 1]: raw midi
4: [ 0- 0]: raw midi
5: [ 0- 3]: digital audio playback
6: [ 0- 2]: digital audio playback
7: [ 0- 2]: digital audio capture
8: [ 0- 1]: digital audio capture
9: [ 0- 0]: digital audio playback
10: [ 0- 0]: digital audio capture
11: [ 0] : control
33: : timer
00-00: EMU10K1 (FX8010)
00-00: emu10k1 : ADC Capture/Standard PCM Playback : playback 32 : capture 1
00-01: emu10k1 mic : Mic Capture : capture 1
00-02: emu10k1 efx : Multichannel Capture/PT Playback : playback 8 : capture 1
00-03: emu10k1 : Multichannel Playback : playback 1
Client info
cur clients : 3
peak clients : 3
max clients : 192
Client 0 : "System" [Kernel]
Port 0 : "Timer" (Rwe-)
Port 1 : "Announce" (R-e-)
Connecting To: 15:0
Client 14 : "Midi Through" [Kernel]
Port 0 : "Midi Through Port-0" (RWe-)
Client 15 : "OSS sequencer" [Kernel]
Port 0 : "Receiver" (-we-)
Connected From: 0:1
Client 16 : "E-mu 1010 [MAEM8810]" [Kernel]
Port 0 : "Audigy MPU-401 (UART)" (RWeX)
Port 32 : "Audigy MPU-401 #2" (RWeX)
Client 17 : "Emu10k1 WaveTable" [Kernel]
Port 0 : "Emu10k1 Port 0" (-We-)
Port 1 : "Emu10k1 Port 1" (-We-)
Port 2 : "Emu10k1 Port 2" (-We-)
Port 3 : "Emu10k1 Port 3" (-We-)
Dev Snd ---------------------------------------------------
total 0
drwxr-xr-x 2 root root 60 Apr 12 20:42 by-path
crw-rw----+ 1 root audio 116, 11 Apr 12 20:42 controlC0
crw-rw----+ 1 root audio 116, 2 Apr 12 20:42 hwC0D0
crw-rw----+ 1 root audio 116, 12 Apr 12 20:46 hwC0D2
crw-rw----+ 1 root audio 116, 4 Apr 12 20:42 midiC0D0
crw-rw----+ 1 root audio 116, 3 Apr 12 20:42 midiC0D1
crw-rw----+ 1 root audio 116, 13 Apr 12 20:46 midiC0D2
crw-rw----+ 1 root audio 116, 14 Apr 12 20:46 midiC0D3
crw-rw----+ 1 root audio 116, 10 Apr 12 20:42 pcmC0D0c
crw-rw----+ 1 root audio 116, 9 Apr 12 20:43 pcmC0D0p
crw-rw----+ 1 root audio 116, 8 Apr 12 20:42 pcmC0D1c
crw-rw----+ 1 root audio 116, 7 Apr 12 20:42 pcmC0D2c
crw-rw----+ 1 root audio 116, 6 Apr 12 20:42 pcmC0D2p
crw-rw----+ 1 root audio 116, 5 Apr 12 20:42 pcmC0D3p
crw-rw----+ 1 root audio 116, 1 Apr 12 20:42 seq
crw-rw----+ 1 root audio 116, 33 Apr 12 20:42 timer
CPU -------------------------------------------------------
model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
cpu MHz : 2000.000
model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
cpu MHz : 2000.000
RAM -------------------------------------------------------
MemTotal: 4051696 kB
SwapTotal: 51196 kB
Hardware --------------------------------------------------
01:00.0 VGA compatible controller: NVIDIA Corporation G94 [GeForce 9600 GT] (rev a1)
05:01.0 Multimedia audio controller: Creative Labs SB Audigy (rev 03)
Interupts -------------------------------------------------
CPU0 CPU1
0: 48 0 IO-APIC-edge timer
1: 1 1 IO-APIC-edge i8042
6: 1 2 IO-APIC-edge floppy
8: 0 1 IO-APIC-edge rtc0
9: 0 0 IO-APIC-fasteoi acpi
12: 4 1 IO-APIC-edge i8042
16: 529 493 IO-APIC-fasteoi uhci_hcd:usb1, pata_jmicron, nvidia
18: 10654 10645 IO-APIC-fasteoi uhci_hcd:usb3, ehci_hcd:usb4, uhci_hcd:usb8, firewire_ohci, i801_smbus
19: 3621 3626 IO-APIC-fasteoi uhci_hcd:usb7, snd_emu10k1
21: 0 0 IO-APIC-fasteoi uhci_hcd:usb2
23: 0 0 IO-APIC-fasteoi ehci_hcd:usb5, uhci_hcd:usb6
44: 7637 7652 PCI-MSI-edge ahci
45: 11719 11736 PCI-MSI-edge eth0
NMI: 47 47 Non-maskable interrupts
LOC: 49551 45081 Local timer interrupts
SPU: 0 0 Spurious interrupts
PMI: 47 47 Performance monitoring interrupts
IWI: 0 0 IRQ work interrupts
RTR: 0 0 APIC ICR read retries
RES: 28730 28313 Rescheduling interrupts
CAL: 94 54 Function call interrupts
TLB: 3503 3509 TLB shootdowns
TRM: 0 0 Thermal event interrupts
THR: 0 0 Threshold APIC interrupts
MCE: 0 0 Machine check exceptions
MCP: 1 1 Machine check polls
ERR: 0
MIS: 0
[christer@Arch ~]$
output from systemctl show somw inacive sound related sevices.
alsa-restore.service loaded inactive dead Restore Sound Card State
alsa-store.service loaded inactive dead Store Sound Card State
auditd.service error inactive dead auditd.service
display-manager.service error inactive dead display-manager.service
dmeventd.service loaded inactive dead Device-mapper event daemon
emergency.service loaded inactive dead Emergency Shell
lvmetad.service loaded inactive dead LVM2 metadata daemon
plymouth-quit-wait.service error inactive dead plymouth-quit-wait.service
plymouth-start.service error inactive dead plymouth-start.service
rc-local-shutdown.service loaded inactive dead /etc/rc.local.shutdown Compatibility
rescue.service loaded inactive dead Rescue Shell
systemd-...console.service loaded inactive dead Dispatch Password Requests to Console
systemd-...rd-wall.service loaded inactive dead Forward Password Requests to Wall
systemd-fsck-root.service loaded inactive dead File System Check on Root Device
systemd-...e8ee844.service loaded inactive dead File System Check on /dev/disk/by-uuid/9751ee37-e769-4bbe-9436-2d8e5e8ee844
systemd-...ev-sda2.service loaded inactive dead File System Check on /dev/sda2
systemd-...ev-sda4.service loaded inactive dead File System Check on /dev/sda4
systemd-initctl.service loaded inactive dead /dev/initctl Compatibility Daemon
systemd-...l-flush.service loaded inactive dead Trigger Flushing of Journal to Persistent Storage
systemd-...ed-load.service loaded inactive dead Load Random Seed
systemd-...ed-save.service loaded inactive dead Save Random Seed
systemd-...ad-done.service loaded inactive dead Stop Read-Ahead Data Collection
systemd-shutdownd.service loaded inactive dead Delayed Shutdown Service
systemd-...s-clean.service loaded inactive dead Cleanup of Temporary Directories
systemd-...unlevel.service loaded inactive dead Update UTMP about System Runlevel Changes
systemd-...hutdown.service loaded inactive dead Update UTMP about System Shutdown
ypbind.service error inactive dead ypbind.service
emergency.target loaded inactive dead Emergency Mode
final.target loaded inactive dead Final Step
nss-lookup.target loaded inactive dead Host and Network Name Lookups
nss-user-lookup.target loaded inactive dead User and Group Name Lookups
remote-fs-pre.target loaded inactive dead Remote File Systems (Pre)
remote-fs-setup.target error inactive dead remote-fs-setup.target
rescue.target loaded inactive dead Rescue Mode
runlevel1.target error inactive dead runlevel1.target
runlevel2.target error inactive dead runlevel2.target
runlevel3.target error inactive dead runlevel3.target
runlevel4.target error inactive dead runlevel4.target
runlevel5.target error inactive dead runlevel5.target
shutdown.target loaded inactive dead Shutdown
syslog.target error inactive dead syslog.target
umount.target loaded inactive dead Unmount All Filesystems
All the best!
Christer
Last edited by agkbill (2013-04-15 18:41:03)

Thank you mich41!
It looks like a kernel bug.
I downgraded to 3.7.10-1 then firmware loaded OK and I could play sounds.
Upgraded to 3.8.6-1 then the firmware fail to load.
Something looks not ok with 3.8.6-1.
Best regards,
Christer

[SOLVED] Awesome's not loading

I did some updates and now I awesome won't start, giving this output instead
awesome: error while loading shared libraries: libev.so.3: cannot open shared object file: No such file or directory
After a bit of googling I found this to be a pretty common error, which just requires to recompile awesome, so I reinstalled awesome from the AUR. Since that didn't solve the problem, I tried getting rid of libev and insalling awesome. It installed just fine, but I still got the same error. I also tried awesome-git but with the same result.
I guess I'm doing something wrong since this is fixed for most people by just compiling awesome again but after a few hours of tinkering I don't seem to find what it is.
Any help would be greatly appreciated.
Last edited by Macdelaney (2010-12-17 04:13:05)

First of all thanks for your reply.
I do have Libev 4.01-1 and it-s in /usr/lib/libev.so.4 too.
I've removed awesome with yaourt -Rns, then cleared the cache from not installed packaged, and installed awesome again. I repeated this for awesome-git just in case, but the same thing happens. I downloaded the package from the AUR manually and then installed, again, same thing happens.
I must be missing something stupidly obvious, but I can't put my finger in it.
Again, any help would be greatly appreciated.
EDIT: A simple whereis awesome showed that /usr/local/bin/awesome existed, apparently I did this at some point (don't really remember). Running /usr/bin/awesome everything works great.
So yes, pretty stupid on my part!
Last edited by Macdelaney (2010-12-17 04:12:38)

[SOLVED] Intel microcode not loaded - already available in the bios?

I'm getting ready to the linux 3.17 release and thought I should manually install the Intel microcode.
I noticed that I didn't even have the package installed, so that was my first stop.
After doing the steps outlined in the wiki, I'm not sure it's actually loaded.
The `sig` and `revision` in the available patch and the kernel output is the same.
Does this mean I already have the microcodes updated through the BIOS, or is this irrelevant?
And if it's irrelevant, any idea what I'm doing wrong?
$ uname -a
Linux simendsjo-t520 3.16.7-1-ck #1 SMP PREEMPT Fri Oct 31 13:09:18 CET 2014 x86_64 GNU/Linux
$ dmesg | grep microcode
[ 0.521721] microcode: CPU0 sig=0x206a7, pf=0x10, revision=0x29
[ 0.521739] microcode: CPU1 sig=0x206a7, pf=0x10, revision=0x29
[ 0.521764] microcode: CPU2 sig=0x206a7, pf=0x10, revision=0x29
[ 0.521783] microcode: CPU3 sig=0x206a7, pf=0x10, revision=0x29
[ 0.521894] microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
The initrd lines in grub.cfg has been changed (not showing entire config, but it's on each non-fallback initrd line)
(But this should matter yet anyway as I'm on 3.16..?)
# grep intel /boot/grub/grub.cfg
initrd /boot/intel-ucode.img /boot/initramfs-linux-ck.img
initrd /boot/intel-ucode.img /boot/initramfs-linux.img
But iucode_tool says an update is available (ref: https://wiki.archlinux.org/index.php/Microcode)
# bsdtar -Oxf /boot/intel-ucode.img | iucode_tool -tb -lS -
iucode_tool: system has processor(s) with signature 0x000206a7
selected microcodes:
001: sig 0x000206a7, pf mask 0x12, 2013-06-12, rev 0x0029, size 10240
Last edited by simendsjo (2014-11-05 20:12:36)

kokoko3k wrote:
I think iucode_tool is just saying that an update has been released for your cpu model.
But yout particular cpu has already it in place.
I don't know if it is the bios to update the microcode or your cpu has been shipped with the new firmware.
Thanks! I don't really care As long as I haven't failed the installation process, I'm happy.

[solved] AMD Ucode not loading on boot

Its being called twice during the early hooks stage of udev.
i have already googled and found I needed to have installed the AMD Ucode package. I have version 2012.1.17-3 but it is being ignored.
Im getting the error
[unix time stamp i assume] microcode: failed to load file amd-ucode/microcode_amd.bin
twice after a long pause.
How do I fix it?
Last edited by Rhiadratech (2012-09-10 14:10:51)

I have put microcode in there as per instructions, but the word microcode was not in mkinitcpio.conf when I installed the system and started seeing the message. I think I added it on instructions in one of the 2 threads or an arch wiki page on the subject. I'll remove it.
The thing is I HAVE the amd-ucode package installed, and i'm STILL getting the message and associated delay on boot. So I'm looking for how I inform it I have installed it?
Last edited by Rhiadratech (2012-09-08 19:35:07)

[SOLVED]Virtualbox drivers not loaded at startup

I followed the wiki and added vboxdrv to my DAEMONS. The only change is that I start it in the background. However, when I start Virtualbox, and then the guest OS within, it gives me an error.
DAEMONS=(syslog-ng @net-profiles @dbus !sshd !netfs @crond @alsa @acpid @ntpd @vboxdrv)
I have to manually
modprobe vboxdrv
in order to start the guest OS. How can I have the vboxdrv started at boot?
also, is there a way to start the guest OS directly, without having to start the Virtualbox console?

Inittab:
# Runlevel 5 starts X environments
x1:5:once:/bin/su work -l -c "/usr/bin/startx -- :11 vt11 > /dev/null 2>&1"
x2:5:once:/bin/su windows -l -c "/usr/bin/startx -- :10 vt10 > /dev/null 2>&1"
x3:5:once:/bin/su windows -l -c "/usr/bin/VBoxManage startvm Ama --type vrdp > /dev/null 2>&1"
The first two start new X sessions, user "work" on vt11 and user "windows" on vt10. The third starts an RDP headless VirtualBox VM as user "windows". When the two X sessions start, they execute ~/.xinitrc (each of ~work/.xinitrc and ~windows/.xinitrc):
#!/bin/sh
# ~/.xinitrc
# Executed by startx
VirtualBox
This starts the VirtualBox GUI so I then switch to vt11 or vt10 and select a VM to run. Note each of ~windows/.VirtualBox and ~work/.VirtualBox are completely separate VB configs owned by the separate accounts.
Note that I don't bother with a window manager because I run the VMs full screen anyway, but you can start one if you want within .xinitrc.
You can change "VirtualBox" in .xinitrc to start a specific VM using VBoxManage startvm "MyVMName"
Hope this helps.
Last edited by starfry (2011-03-29 21:49:33)

[SOLVED] KDE Is not loading

HI, i'm been an archlinux user for a while, never have great issues, but now i reinstalled arch in a formated disk and started all over. The thing is that I installed kde basis (following the wiki), but neither kdm via inittab, or kdm via daemon works! it just load the tt1 console and do nothing. No erors, or something. The only difference with previous installation is that the first time i installed kde-meta package, and have no issues
Any thoughts?
Last edited by atercor (2012-05-20 01:26:48)

Anything in the logs? What happens if you try to start KDE with startx/.xinitrc instead of KDM?

[SOLVED] network is not detected r8169 module is not loaded

Similar Messages

Maybe you are looking for