syslog errors with Slackware current kernel install.

You have a problem with Salix? Post here and we'll do what we can to help.
Post Reply
User avatar
globetrotterdk
Posts: 435
Joined: 26. Oct 2010, 13:57
Location: Denmark

syslog errors with Slackware current kernel install.

Post by globetrotterdk »

I have become aware of the following errors and warnings in connection with my installing a Slackware current kernel on my Salix64 KDE 13.37 system. Solutions and comments are appreciated.

Code: Select all

Mar 19 07:36:13 darkstar udevd[1990]: bind failed: Address already in use 
Mar 19 07:36:13 darkstar udevd[1990]: error binding control socket, seems udevd is already running 
Mar 19 07:36:13 darkstar kernel: [    0.000000] ACPI: RSDP 00000000000f0450 00024 (v02 ALASKA)
Mar 19 07:36:13 darkstar kernel: [    0.000000] ACPI: XSDT 00000000bd889068 0004C (v01 ALASKA    A M I 01072009 AMI  00010013)
Mar 19 07:36:13 darkstar kernel: [    0.000000] ACPI: FACP 00000000bd891c30 000F4 (v04 ALASKA    A M I 01072009 AMI  00010013)
Mar 19 07:36:13 darkstar kernel: [    0.000000] ACPI Warning: Optional field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20110623/tbfadt-560)
---snip---
Mar 19 07:36:13 darkstar kernel: [    0.514172] ACPI: Executed 2 blocks of module-level executable AML code
Mar 19 07:36:13 darkstar kernel: [    0.518061] ACPI Error: [RAMB] Namespace lookup failure, AE_NOT_FOUND (20110623/psargs-359)
Mar 19 07:36:13 darkstar kernel: [    0.518066] ACPI Exception: AE_NOT_FOUND, Could not execute arguments for [RAMW] (Region) (20110623/nsinit-349)
---snip---
Mar 19 07:36:13 darkstar console-kit-daemon[2102]: WARNING: Failed to acquire org.freedesktop.ConsoleKit 
Mar 19 07:36:13 darkstar console-kit-daemon[2102]: WARNING: Could not acquire name; bailing out 
Mar 19 07:36:14 darkstar ntpd[2301]: line 0 column 0 syntax error, unexpected $end
Mar 19 07:36:15 darkstar console-kit-daemon[2359]: WARNING: Failed to acquire org.freedesktop.ConsoleKit 
Mar 19 07:36:15 darkstar console-kit-daemon[2359]: WARNING: Could not acquire name; bailing out 
Mar 19 07:36:20 darkstar kdm_greet[2456]: Cannot load /usr/share/apps/kdm/faces/.default.face: No such file or directory
Mar 19 07:36:25 darkstar dhcpcd[2469]: dhcpcd not running
Mar 19 07:36:25 darkstar dhcpcd[2476]: dhcpcd not running
Mar 19 07:36:28 darkstar kernel: [   29.177699] start_kdeinit (2567): /proc/2567/oom_adj is deprecated, please use /proc/2567/oom_score_adj instead.
To recap, for those members of the forum, that are wondering why I installed a Slackware current kernel, I installed the kernel in an attempt to get my Asus PCE-N15 wireless card working. The card is listed as

Code: Select all

[code]# lspci -knn
---snip---
07:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n WiFi Adapter [10ec:8178] (rev 01)
	Subsystem: ASUSTeK Computer Inc. Device [1043:84b6]
---snip---
The card is believed to have a RealTek rtl8192ce chipset.
Military justice is to justice what military music is to music. - Groucho Marx
User avatar
mimosa
Salix Warrior
Posts: 3311
Joined: 25. May 2010, 17:02
Contact:

Re: syslog errors with Slackware current kernel install.

Post by mimosa »

I don't know whether 8188 is just another name for 8192, (often the driver isn't called what you'd expect) but unless you actually do have to load it manually - which you shouldn't - it shouldn't matter because the right one just gets chosen automatically.

Regarding those messages, they may well be no cause for alarm, but I can't comment specifically. With the 2.6 kernel, I got all sorts of warnings, and I think that's pretty normal. But maybe some of these actually do matter; afraid I can't say. The key thing though is whether everything appears to be working properly.
Post Reply