Arch Linux

[viking60]

Also, not knowing much about these things, how do I stop this message?

Code: Select all

# modprobe eeprom
--->WARNING: All config files need .conf: /etc/modprobe.d/blacklist, it will be ignored in a future release.

Must mean that you should call the file blacklist.conf instead of just blacklist.

[dedanna1029]

How though, when all I'm trying to do is run a simple command (modprobe eeprom)?

Thanks.

[viking60]

I'm going to uninstall lm_sensors. Updates tonight did not fix the sound card failing on boot issue.

Edit: But not without running sensors-detect first.

Code: Select all

Found `SMSC LPC47M172 Super IO Fan Sensors'                 
    (but not activated)

Not activated? Any clue? Thanks.

Here is mine:

Code: Select all

sudo sensors-detect
Passord:
# sensors-detect revision 5861 (2010-09-21 17:21:05 +0200)
# Board: Intel Corporation D955XBK

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): yes
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
Intel Core family thermal sensor...                         No
Intel Atom thermal sensor...                                No
Intel AMB FB-DIMM thermal sensor...                         No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): yes
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     Yes
Found `SMSC LPC47M182 Super IO Fan Sensors'                 
    (but not activated)
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): yes
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no): no

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): no
Sorry, no sensors were detected.
Either your system has no sensors, or they are not supported, or
they are connected to an I2C or SMBus adapter that is not
supported. If you find out what chips are on your board, check
http://www.lm-sensors.org/wiki/Devices for driver status.


It seems to be perfectly normal. Mine are not activated either.
To check out that stuff I use this brilliant tip

[dedanna1029]

Ah, I see, so you got the same thing. Howcome you didn't let the I2C/SMBus adapters run?

Your system must be similar to mine? I got almost the exact same thing (except for the I2C/SMBus adapters part).

And now, we present to you the cool part...



(You'll need to zoom)

[viking60]

I wonder how many times I have tried to tell you that my system is similar You have tried to makes yours different because then you could have some exclusive bug to yourself. But really the systems are quite similar from what I have gathered -thats true.
Why should I let those adapters run? (The system is rock stable with no problem what so ever) How would it help me?

[dedanna1029]

Anyone on the gdm2setup issue posted on page 19 of this thread? Thanks.

[dedanna1029]

Is there is a specific firewall proggie that's best to use in Arch? I'm to the point to where I need one. Never did before, but I do now. The simpler the better. So far, I've installed shorewall, firehol, and fwbuilder - fwbuilder looks cool but am not 100% on it as I've never used it.

Thanks.

[dedanna1029]

Figured out the screensaver/blanking issue. Neither screensaver proggie, whether it be gnome-screensaver, or xscreensaver, has been starting on login - the gnome-screensaver "daemon" if you will, is not in startup applications (it should be started on login), and neither is xscreensaver, so I will have to add gnome-screensaver.

Got the idea, kind of a "what the hell" thing, to type in "gnome-screensaver" as regular user into terminal tonight, just to see if it would do anything. It did. Then, I typed in xscreensaver, and got this response:

Code: Select all

:) xscreensaver
xscreensaver: 00:43:43: "gnome-screensaver" is already running on display :0.0 (window 0x5200001)

I looked at it like, "WTH? gnome-screensaver wasn't running???!!!" - sure enough, it's not in Startup Applications.

I hit the shortcut key that I set up to kick in the screensaver (Ctrl+Alt+Z), and sure enough, the screensaver kicked in, and when I moved the mouse to get it to stop, there was my locking window, I put in my password to unlock, and it unlocked.

I'm just trying to figure out what took it out of desktop startup.

Oh, and FYI, I took kde's policykit out of startup applications, logged out/in, and my hard drive is running a LOT quieter now. I left Gnome's - it's fine!

Just wish I'd thought of this crap before!

Ah, the weird stuff we can think up when we're exhausted...

I do still need an answer to the firewall question though. Thanks!

[dedanna1029]

Also, I haz a nice one for you! Nero is in yaourt!

Code: Select all

:) yaourt nero
1 community/nrg2iso 0.4-7 [0.00 M] [installed]
    Utility for converting CD or DVD image generated by Nero Burning Rom to ISO format
2 aur/cdi2nero 0.9.9-2 (0)
    A simple utility to convert a DiscJuggler image to a Nero NRG image.
3 aur/nero 2-1 (8)
    Neuro-Evolving Robotic Operatives. A game of training and battle.
4 aur/neroaacdec 1.5.4-2 (34)
    Nero AAC reference quality MPEG-4 and 3GPP audio codec
5 aur/neroaacenc 1.5.4-2 (72)
    Nero AAC reference quality MPEG-4 and 3GPP audio codec
6 aur/neroaactag 1.5.4-2 (18)
    Nero AAC reference quality MPEG-4 and 3GPP audio codec
7 aur/neroconv 1.00-2 (16)
    A program which converts Nero image files (nrg) to ISO9660
8 aur/nerolinux 4.0.0.0-2 [installed] (356)
    Nero Burning ROM for linux
9 aur/nerolinux3 3.5.3.1-1 (31)
    Nero Burning ROM 3 for linux
10 aur/ogmrip-nero-aac 0.4-1 (2)
    ogmrip-nero-aac is a plugin which adds support for Nero-AAC audio codec
11 aur/qtuneroid 0.9-7 (19)
    Tuner for variety of musical instruments (especially guitar)
12 aur/tuneroid 0.9.5-2 (10)
    Tuner for variety of musical instruments (especially guitar)
==> Enter n° of packages to be installed (ex: 1 2 3 or 1-3)

So, if you've bought Nerolinux, and have a valid serial number, it will install from yaourt - plug your s/n into it, and go with it - I have kept up on paying for it, and for the most part, it works wonderfully!

Nero Linux + Arch Linux = WOOOOOOOOOOOWWW...

I'm having chance to use it tonight - need to burn me off some hard drive space.

[dedanna1029]

Per this post, I r haz fixored the sound issue on boot.

What happened, was alsactl was moved in an update from /usr/bin/alsactl to /usr/sbin/alsa/alsactl - it was no longer in the path. Ran this:

Code: Select all

alsactl -f /var/lib/alsa/asound.state store

Said "alsactl: command not found"...
So, I ran an ls, sure 'nuff, it wasn't there. Neither was /var/lib/alsa/asound.state, so... ran "whereis alsactl", and it came back that it was in "/usr/sbin/alsactl", not the usual "/usr/bin/alsactl".

Modified the above command, and ran:

Code: Select all

/usr/sbin/alsactl -f /var/lib/alsa/asound.state store

Rebooted, and all's good - no errors at all.

[viking60]

Ok update today needed a pacman update. Everytime i update pacman I have to uninstall pacman-color It will be ok in a couple of days I guess so I can reinstall. But that is annoying.

[dedanna1029]

Got the same myself just last night. Was trying to get updated before I get shut down online.

Hope that update for pacman-color comes through before I do.