You are not logged in.

#1 2007-11-29 04:16:36

fflarex
Member
Registered: 2007-09-15
Posts: 466

issues i haven't been able to solve by googling/RTFMing...

I've been running Arch on my laptop for several weeks now, and there are still some woes that Google/RTFMing haven't been able to solve.

First and foremost, every once in a while my screen or mouse cursor will flicker. I put up with this for a long time, figuring there were bigger issues I needed to deal with first. But now... holy crap, this is annoying me to no end. Xorg.conf is below.

Second, I am having serious issues trying to get my bluetooth mouse to work. It only connects after several manual commands (not automatically), and once it does connect the buttons are all weird and seem to register multiple times in quick succession on a single click. I've tried everything I could find. I'm using KDE so I would prefer to set it up through the kdebluetooth packages, but any way I can get it to work would be amazing. I even found an Arch thread with someone who has an identical model as me, but it still didn't help. (note that I haven't actually been able to follow any single tutorial all the way to the end; something invariably goes wrong first)

And finally, I don't know how to get my keyboard set up correctly. Right now, it does 99% of what it needs to, but certain keys don't work. The Win key (Super?) and special laptop shortcuts don't work (the Fn key and its various key chords).

Thanks in advance. I'll post necessary config files in the next post.

Offline

#2 2007-11-29 04:25:52

jacko
Member
Registered: 2007-11-23
Posts: 840

Re: issues i haven't been able to solve by googling/RTFMing...

There is no problem with the keyboard, the windows super key is windows specific and the Fn key on your laptop has to do with the bios I believe. Neither of those will u fix in any linux unless u do it manually by binding them to a specific function.

Offline

#3 2007-11-29 04:30:02

fflarex
Member
Registered: 2007-09-15
Posts: 466

Re: issues i haven't been able to solve by googling/RTFMing...

/etc/X11/xorg.conf

# /etc/X11/xorg.conf
#  Configuration file for the X server
#  For reference information regarding how to edit this file:
#      man xorg.conf

Section "ServerLayout"
        Identifier      "Default Layout"
        Screen          "Laptop Screen"
        InputDevice     "Laptop Keyboard"
        InputDevice     "Synaptics Touchpad"
        InputDevice     "Bluetooth Mouse" "SendCoreEvents"
EndSection

#################
# Input Devices #
#################

Section "InputDevice"
        Identifier      "Laptop Keyboard"
        Driver          "kbd"
        #Option          "CoreKeyboard"
        #Option          "XkbRules"        "xorg"
        Option          "XkbModel"        "pc105"
        Option          "XkbLayout"       "us+inet" #"us"
        #Option          "XkbVariant"      "dvorak"
        #Option          "XkbOptions"      "lv3:ralt_switch"
EndSection

Section "InputDevice"
        Identifier      "Synaptics Touchpad"
        Driver          "synaptics"
        Option          "Device"          "/dev/psaux"
        Option          "Protocol"        "auto-dev"
        Option          "LeftEdge"        "1700"
        Option          "RightEdge"       "5300"
        Option          "TopEdge"         "1700"
        Option          "BottomEdge"      "4200"
        Option          "FingerLow"       "25"
        Option          "FingerHigh"      "30"
        Option          "MaxTapTime"      "180"
        Option          "MaxTapMove"      "220"
        Option          "VertScrollDelta" "100"
        Option          "MinSpeed"        "0.06"
        Option          "MaxSpeed"        "0.12"
        Option          "AccelFactor"     "0.0010"
        Option          "SHMConfig"       "on"
        #  Option          "Repeater"        "/dev/ps2mouse"
EndSection

Section "InputDevice"
        Identifier      "Bluetooth Mouse"
        Driver          "mouse"
        Option          "Device"          "/dev/input/mice"
        Option          "Protocol"        "IMPS/2"
        Option          "Buttons"         "5"
        Option          "ZAxisMapping"    "4 5"
EndSection

#################
#   Graphics    #
#################

Section "Device"
        Identifier      "ATI X1400 Radeon Mobility"
        Driver          "fglrx"
        Busid           "PCI:1:0:0"
        #Option          "HWCursor"        "off"
EndSection

#Section "Monitor"
#        Identifier      "Laptop Monitor"
#        Option          "DPMS"
#        Horizsync       30-70
#        Vertrefresh     50-160
#EndSection

Section "Screen"
        Identifier      "Laptop Screen"
        Device          "ATI X1400 Radeon Mobility"
        DefaultDepth    24
        #SubSection "Display"
        #           Viewport   0 0
        #           Depth     24
        #EndSubSection
        #Monitor         "Laptop Monitor"
EndSection

Section "Module"
        Load            "glx"
EndSection

Section "Extensions"
        Option          "Composite"       "0"
EndSection

Note that this file was handwritten as an amalgamation of the preconfigured xorg.conf files from Ubuntu and Fedora, as well as some options I found on the net. For instance, the HWCursor options is supposed to fix flickering cursors for Nvidia cards, so I tried it despite having a card from ATI.

/etc/rc.d/bluetooth

# Bluetooth configuraton file

# Bluetooth services (allowed values are "true" and "false")

# Run the hcid daemon (default: true)
#DAEMON_ENABLE="true"

# Run hid2hci (default: false)
HID2HCI_ENABLE="true"

# Run the sdp daemon (default: false)
# If this is disabled, hcid's internal sdp daemon will be used
#SDPD_ENABLE="false"

# Added from tutorial:
HCID_ENABLE="true"

# Run the bluetooth HID daemon (default: false)
HIDD_ENABLE="true"
HIDD_ENABLED=1

# Activate rfcomm ports (default: false)
#RFCOMM_ENABLE="false"

# Run bluetooth dial-up networking daemon (default: false)
#DUND_ENABLE="false"

# Run bluetooth PAN daemon (default: false)
#PAND_ENABLE="false"

# hcid configuration file (default: /etc/bluetooth/hcid.conf)
#DAEMON_CONFIG="/etc/bluetooth/hcid.conf"

# rfcomm configuration file (default: /etc/bluetooth/rfcomm.conf)
#RFCOMM_CONFIG="/etc/bluetooth/rfcomm.conf"

# Options for hidd, dund and pand (default: none)
#HIDD_OPTIONS=""
#DUND_OPTIONS=""
#PAND_OPTIONS=""

/etc/rc.conf

#
# /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"
# 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="UTC"
TIMEZONE="America/Chicago"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

#
# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# Scan hardware and load required modules at bootup
MOD_AUTOLOAD="yes"
# Module Blacklist - modules in this list will never be loaded by udev
MOD_BLACKLIST=()
#
# Modules to load at boot-up (in this order)
#   - prefix a module with a ! to blacklist it
#
MODULES=(acpi-cpufreq sky2 mac80211 iwl4965 snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

#
# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
HOSTNAME="gatewa"
#
# 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
#
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
#
# Don't use this for wireless interfaces, see network profiles below
#
lo="lo 127.0.0.1"
eth0="dhcp"
wlan0="dhcp"
wlan_wlan0="wlan0 essid default"
INTERFACES=(lo !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 192.168.0.1"
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-profiles
#
#NET_PROFILES=(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 dhcdbd networkmanager netfs crond alsa acpid cpufreq hal fam kdm)


# End of file

Offline

#4 2007-11-29 04:30:56

fflarex
Member
Registered: 2007-09-15
Posts: 466

Re: issues i haven't been able to solve by googling/RTFMing...

jacko wrote:

There is no problem with the keyboard, the windows super key is windows specific and the Fn key on your laptop has to do with the bios I believe. Neither of those will u fix in any linux unless u do it manually by binding them to a specific function.

They work in both Ubuntu and Fedora. Also, I forgot to mention that I can't enter backticks.

Offline

#5 2007-11-29 06:49:54

pauldonnelly
Member
Registered: 2006-06-19
Posts: 776

Re: issues i haven't been able to solve by googling/RTFMing...

It sounds like your keymap may be wrong if ` can't be typed.

But what do you mean that your Windows key "doesn't work"? Do you mean that it doesn't do what you expect, or do you mean that when you type it into an xev window you get no reaction?

Offline

#6 2007-11-29 09:36:58

pelle.k
Member
From: Åre, Sweden (EU)
Registered: 2006-04-30
Posts: 667

Re: issues i haven't been able to solve by googling/RTFMing...

tr "us" instead of "us+inet" as layout (maybe you already did, since it's commented out?).
Ubuntu applies quite a few patches to assign these keys automatically, but you need to do that with xbindkeys.

Install xbindkeys, create .Xbindkeys in your $HOME (gdm will load it at login). example;

keycode 162 = XF86Play

you can expose the keycodes with xev, like pauldonelly said.

Can't help you with the bt mouse though, sorry.


"Your beliefs can be like fences that surround you.
You must first see them or you will not even realize that you are not free, simply because you will not see beyond the fences.
They will represent the boundaries of your experience."

SETH / Jane Roberts

Offline

#7 2007-11-29 21:48:42

fflarex
Member
Registered: 2007-09-15
Posts: 466

Re: issues i haven't been able to solve by googling/RTFMing...

Okay, thanks about the keyboard. I have that mostly fixed now, and the stuff which isn't fixed yet I have a fairly good idea of what I still need to do.

Pretend my mouse isn't bluetooth. Is there anything that would cause it to behave differently? Like, clicking on a window's titlebar maximizes it (it's set so that a double click is required for that), even if I hold it down as if to drag the window. I need to hold the left mouse button down to look at menus or else they disappear right away. And (most annoying of all) when I click on links in a web page, it just selects the text rather than following the link. All this stuff works on my touchpad, and leads me to believe that it's double clicking when I'm single clicking. Yet it does work correctly on other things. For instance in KDE where some toolbar buttons have drop down menus, it works perfectly for that (if it were double clicking it would need to be held down like normal menus).

And of course I will mail a batch of cookies to anyone who solves my flickering cursor and screen problems (probably...) They are of the hypothetical chocolate chip variety.

Offline

#8 2007-11-29 21:56:44

barebones
Member
Registered: 2006-04-30
Posts: 235

Re: issues i haven't been able to solve by googling/RTFMing...

What are you trying to do with your win key? My win key "works" with out any other configuration in arch, in the sense that the awesome wm recognizes that it is pushed (all of it's special commands are default to MOD4 + something). If you want it to do something else, say from the desktop, like start a program, you'll have to use xbindkeys like pelle.k mentioned.

Offline

Board footer

Powered by FluxBB