Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Slackintosh, Slackware for Mac for those who aren't familiar with the name. I just need some simple help for those with experience with it.
I need to just get the powerbook keys working. I want brightness control, volume, bleh bleh bleh, you get the idea.
Also... this is just a simple request... how do i specify acceptable resolutions for Xserver in xorg.conf? I totally forgot as it's been a long time since I did a fresh install of Slack, on anything. Thx in advance for the help folks.
Well, can you get a signal out of the keys? e.g. xev is a great tool to test that. If you can, then you might want to try out xbindkeys and bind some shellscripts to them to lower / raise volume, and even adjust the brightness. Ofcourse that would only be possible if there is some acpi / apm command to do that, I have no idea..
The resos should be defined under the section Screen, and spesificly for each subsection. Ill throw in an example of mine:
I found the xorg configuration a little earlier, and "fixed" it, but to no avail. I don't have the ability to change the resolution in kde. As for the keys... there is actually some programs included with Slackintosh that are designed to capture and register commands for the powerbook volume/brightness, but for some reason they do not work. Any advice on that?
Well, if X thinks for some reason that your powerbook cant take the resolution, it wont allow you to try.. Sometimes installing the graphics cards own drivers helps
Well, without any error messages its hard to say what could be wrong.. Maybe run the catcher from a terminal and see if you get any helpful output when pressing the buttons.. Also their docs might be worth a read (;
It doesn't catch the keys, not too concerned about that... more about the video. The card is marked as an nVidia GeForce4 440 Go 64mb and is using the generic preloaded "nv" (nVidia) driver. I'm trying another configuration, and so far... no go... I cannot get this damned thing to change res! Anybody know where I can get PPC nVidia drivers? Something that I can compile hopefully?
the nvidia drivers compile the kernel module, but I think its pretty x86 still.. ): I doubt they have any interest in releasing Linux PPC drivers.. Perhaps the OSX package could be ported, but that gets kinda tricky..
Actually... i got it sorted out. I wasn't sure that it would work but it did. I used the same "Monitor" section from http://www.nvnews.net/vbulletin/show...4863&page=4#46 in my xorg.conf, started it up, and BLAM! 1024x768 on my Mactop again! WOO! I'm dancing now... and now i can take a look into those keys after i've gotten the ANNOYING part out of the way. Care to help me with that as well?
Well well.. Lets see.. I think you could start out by reading the manual for those, btw, whats the app called? Those kinda applications usually have some verbose or debug mode, so making use of such we might get better grounds to work upon..
The applications is called pbbuttonsd (PowerBook BUTTONS Daemon). And there's an interface application called pbbcmd (PowerBook Buttons CoMManD), which sends direct commands to pbbuttonsd and configures it to one key or another. Here's the stuff that you asked for...
pbbuttonsd:
Code:
pbbuttonsd - daemon to support special features of laptops and notebooks.
Usage: pbbuttonsd [OPTION]...
Options:
-h, --help display this help text and exit
-v, --version display version information and exit
-q, --quiet suppress welcome message
-d, --detach[=PIDFILE] start pbbuttonsd as background process and
optional use an alternative pid-file
(default: /var/run/pbbuttonsd.pid)
-c, --configfile=CONFIG use alternative configuration file
(default: /etc/pbbuttonsd.conf)
see configuration file for more options.
pbbcmd
Code:
pbbcmd (version 0.7.1) - control client for pbbuttonsd.
Usage:
pbbcmd [-hvi] <command>
pbbcmd [-hvi] query <tag>
pbbcmd [-hvi] config <tag> <data>
Options:
-h, --help display this help and exit
-v, --version display version information and exit
-i, --ignore ignore config return and error values
Supported commands:
listclients - prints a list of clients attached
saveconfig - save the current configuration to disk
reinit - reinitialising the keyboard and the trackpad
ejectcd - eject the CDROM
sleep - suspend to RAM
config - reconfigure server parameters
query - queries the server for certain parameters
Supported tags:
TAG_AUTORESCAN TAG_TIMEFORCMD TAG_VERSION
TAG_SYSINFO TAG_TIMEREMAINING TAG_POWERSOURCE
TAG_SLEEPSUPPORTED TAG_PMUDEVICE TAG_ADBDEVICE
TAG_TPMODEUPKEY TAG_TPMODEUPMOD TAG_TPMODEDOWNKEY
TAG_TPMODEDOWNMOD TAG_TPMODE TAG_NOTAPTYPING
TAG_KBDMODE TAG_BATLOG TAG_BATTERYPRESENT
TAG_BATCYCLE TAG_AMBIENTLIGHT TAG_LCDILLUMUPKEY
TAG_LCDILLUMUPMOD TAG_LCDILLUMDOWNKEY TAG_LCDILLUMDOWNMOD
TAG_KBDILLUMUPKEY TAG_KBDILLUMUPMOD TAG_KBDILLUMDOWNKEY
TAG_KBDILLUMDOWNMOD TAG_KBDILLUMONKEY TAG_KBDILLUMONMOD
TAG_LCDBRIGHTNESS TAG_LCDBRIGHTNESSMAX TAG_LCDFADINGSPEED
TAG_LCDAUTOADJUST TAG_LCDTHRESHOLD TAG_LCDAUTOADJMINBAT
TAG_LCDAUTOADJMAXBAT TAG_LCDAUTOADJMINAC TAG_LCDAUTOADJMAXAC
TAG_KBDBRIGHTNESS TAG_KBDONBRIGHTNESS TAG_KBDBRIGHTNESSMAX
TAG_KBDFADINGSPEED TAG_KBDTHRESHOLD TAG_KBDAUTOADJUST
TAG_FRAMEBUFFERDEVICE TAG_BLANKFRAMEBUFFER TAG_DIMFULLYDARK
TAG_CRTMIRROR TAG_CRTMIRRORKEY TAG_CRTMIRRORMOD
TAG_SOUNDSYSTEM TAG_SOUNDSYSTEMCFG TAG_MIXERDEVICE
TAG_MIXERCARD TAG_VOLUMEUPKEY TAG_VOLUMEUPMOD
TAG_VOLUMEDOWNKEY TAG_VOLUMEDOWNMOD TAG_MUTEKEY
TAG_MUTEMOD TAG_MIXERINITDELAY TAG_VOLUME
TAG_MUTE TAG_MIXERCHANNELS TAG_MIXERELEMENTS
TAG_CDROMDEVICE TAG_EJECTCDKEY TAG_EJECTCDMOD
TAG_EJECTCDKEYDELAY TAG_SCRIPTPMCS TAG_SLEEPKEY
TAG_SLEEPMOD TAG_SLEEPKEYDELAY TAG_BWLFIRST
TAG_BWLSECOND TAG_BWLLAST TAG_CURRENTBWL
TAG_CPULOADSLEEPLOCK TAG_CPULOADMIN TAG_CPULOADPERIOD
TAG_NETLOADSLEEPLOCK TAG_NETLOADMIN TAG_NETLOADPERIOD
TAG_NETLOADDEV TAG_POLICY TAG_ONAC_POLICY
TAG_ONAC_TIMERACTION TAG_ONAC_COVERACTION TAG_ONAC_KEYACTION
TAG_ONAC_TIMESUSPEND TAG_ONAC_TIMEDIM TAG_ONBATT_POLICY
TAG_ONBATT_TIMERACTION TAG_ONBATT_COVERACTION TAG_ONBATT_KEYACTION
TAG_ONBATT_TIMESUSPEND TAG_ONBATT_TIMEDIM TAG_EMERGENCYACTION
TAG_HEARTBEATBEEP TAG_IDENTITY
The leading 'TAG_' could be omited.
ERROR: Problems with IPC, maybe server is not running.
pbbuttonsd.conf:
Code:
# Configuration file for PBButtonsd >= Version 0.5
# for complete list of options please see pbbuttonsd.conf man-page
# [SYSTEM]
#userallowed = "paranoid" ; user who is allowed to use IPC
autorescan = no ; automatic rescan of event devices
CmdTimeout = 4
# [MODULE POWERSAVE]
onAC_policy = performance ; nochange, performance, custom or powersave
onAC_TimerAction = none ; none, suspend-to-ram, suspend-to-disk, blankscreen
onAC_CoverAction = suspend-to-ram
onAC_KeyAction = suspend-to-ram ; SleepKey
onAC_SuspendTime = 0 ; time in 1/10 seconds
onAC_DimTime = 0 ; time in 1/10 seconds
onBattery_policy = powersave
onBattery_TimerAction = suspend-to-ram ; none, suspend-to-ram, suspend-to-disk, blankscreen
onBattery_CoverAction = suspend-to-ram
onBattery_KeyAction = suspend-to-ram ; SleepKey
onBattery_SuspendTime = 3000 ; time in 1/10 seconds
onBattery_DimTime = 600 ; time in 1/10 seconds
SleepKey = 116
SleepKeyDelay = 0 ; values > 0 may be dangerous, if the power key is used to trigger sleep
BWL_first = 22 ; first battery warnlevel, time in minutes
BWL_second = 10 ; second battery warnlevel, time in minutes
BWL_last = 3 ; last battery warnlevel, time in minutes
Script_PMCS = "/etc/power/pmcs-pbbuttonsd %s %s %s"
EmergencyAction = sleep ; action, if battery is critically low
HeartbeatBeep = no ; beep, if nothing else showed that the computer lives
CPULoad_sleeplock = yes
CPULoad_min = 20 ; value in percent
CPULoad_period = 20 ; time in seconds
NETLoad_sleeplock = yes
NETLoad_min = 4096 ; traffic in Bytes/s
NETLoad_period = 20 ; time in seconds
NETLoad_device = "eth0"
# [MODULE DISPLAY]
#LCD_Brightness = 8 ; initial LCD brightness level
LCD_FadingSpeed = 5 ; 0 = no smooth fading
LCD_AutoAdjust = yes ; only on Aluminum PowerBooks
LCD_IllumUpKey = 225
LCD_IllumDownKey = 224
LCD_Threshold = 94
LCD_AutoAdjMin_Bat = 2 ; autoadjust parameter
LCD_AutoAdjMax_Bat = 7
LCD_AutoAdjMin_AC = 1
LCD_AutoAdjMax_AC = 15
#KBD_Brightness = 0 ; initial keyboard illumination level
KBD_OnBrightness = 5 ; initial level if KBD on/off key is pressed
KBD_FadingSpeed = 5 ; 0 = no smooth fading
KBD_AutoAdjust = yes ; only on Aluminum PowerBooks
KBD_IllumUpKey = 230
KBD_IllumDownKey = 229
KBD_IllumOnKey = 228
KBD_Threshold = 28 ; only on Aluminum PowerBooks
dev_FrameBuffer = "/dev/fb0"
UseFBBlank = yes
DimFullyDark = no
CRT_MirrorKey = 65 + ctrl
# [MODULE MIXER]
SoundSystem = OSS ; none, auto, OSS or ALSA
#Volume = 50 ; initial volume level
Speakers_muted = no ; mute after startup?
VolumeUpKey = 115
VolumeDownKey = 114
MuteKey = 113
OSS_Mixer = "/dev/mixer" ; settings for OSS
OSS_Channels = "volume, speaker"
ALSA_Card = "default" ; settings for ALSA
ALSA_Elements = "Master, PCM"
MixerInitDelay = no
# [MODULE CDROM]
dev_CDROM = "/dev/cdrom"
EjectCDKey = 161
EjectCDKeyDelay = 0
# [MODULE PMAC]
dev_PMU = "/dev/pmu"
dev_ADB = "/dev/adb"
TPModeUpKey = 225 + alt
TPModeDownKey = 224 + alt
TPMode = drag
KBDMode = fkeysfirst
Batlog = none
NoTapTyping = no
Well, two things come to mind.. The second app complained that the daemon wasn't running, so I think that might be quite a problem.. (:
And the second one is from the config:
Code:
#userallowed = "paranoid" ; user who is allowed to use IPC
I don't know whats the default action if the option is uncommented, but perhaps you should try uncommenting it and entering your username?
Also, Make sure that whatever rc that creates, lets assume /etc/rc.d/rc.buttons, is chmod +x:ed so it will be run at boot. (hopefully, if not, then you can add it to rc.local) Also you can try starting it manually via: /etc/rc.d/rc.buttons
You can get the full package file lists by reading at /var/log/packages/packagename (:
I figured out the buttons already... interestingly enough, the daemon would always work on every OTHER console than the one you start it on, or at least the one you started it on, it would be intermittent in working. The keys for the special stuff have to be pressed with FN already pressed to send the right key number. For my Mactop, it's FN+ESC=110 FN+F1=111 etc etc... all the way to F12=122. I mapped out the keys and was listening to mpg123 as i usually do when working in console, and i hit FN and the vol up key, OW! It gets loud, this mactop. Now... the BEST thing you can help me with, is some way to capture the key NUMBERS like this daemon looks for. Any ideas?
yeah, that would be xev .. Works under X, forms a little box. Get the cursor over it and youll see alot of debug info in the terminal you started it from. Hold the cursor still and press the button you want the code for.. The keycode is there among the debug info (:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Ok...
