- Arch-general - lists.archlinux.org

[arch-general] Alsa state and my front speakers
by Magnus Therning 06 May '09

06 May '09

I had no problems at all configuring the basic setup for Alsa, everything worked perfect. At the end I issued `alsactl store` and rebooted hoping that my settings would be restored on boot. They were, almost; all settings except the unmute of the front speakers. This forces me to go in and use `alsamixer` each time I boot, just to unmute the front speakers. I've had a look at the the file `/etc/asound.state` but can't make heads or tails of it. Any suggestions on how I can get my front speakers to be unmuted on boot? /M -- Magnus Therning (OpenPGP: 0xAB4DFBA4) magnus＠therning．org Jabber: magnus＠therning．org http://therning.org/magnus identi.ca|twitter: magthe

1 1

[arch-general] [signoff] jfsutils 1.1.14-1
by Tobias Powalowski 05 May '09

05 May '09

Hi update to latest version, please signoff for both arches. greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa(a)archlinux.org

2 1

[arch-general] org.freedesktop.hal.storage.mount-removable no <-- (action, result)
by David C. Rankin, J.D.,P.E. 05 May '09

05 May '09

Listmates, I'm fighting with PolicyKit to mount my USB drives and --- it's Winning! I've modified /etc/PolicyKit/PolicyKit.conf to give all users and myself (david) explicit authority (as a member of wheel and as me) and I've *restarted* hal and still no-go? My conf file looks like this: <config version="0.1"> <define_admin_auth group="wheel"/> <match action="org.freedesktop.hal.storage.mount-removable"> <match group="users"> <return result="yes"/> </match> </match> <match user="david"> <return result="yes"/> </match> </config> No matter what I do I get: org.freedesktop.hal.storage.mount-removable no <-- (action, result) What gives?? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com

8 11

[arch-general] Corruption with new intel driver
by Nicolas Bigaouette 05 May '09

05 May '09

Hi all, I just fully upgraded on two of my machines. These packages related to xorg were updated: [2009-04-14 12:36] upgraded xf86-input-evdev (2.1.2-1 -> 2.2.1-1) [2009-04-14 12:36] upgraded xf86-input-keyboard (1.3.2-1 -> 1.3.2-2) [2009-04-14 12:36] upgraded xf86-input-mouse (1.3.0-1 -> 1.4.0-2) [2009-04-14 12:36] upgraded xf86-video-intel (2.4.3-1 -> 2.6.3-3) [2009-04-14 12:36] upgraded xf86-video-vesa (2.1.0-1 -> 2.2.0-1) [2009-04-14 12:36] upgraded xorg-server-utils (7.4-3 -> 7.4-4) [2009-04-14 12:36] upgraded xorg-server (1.5.3-5 -> 1.6.0-3) [2009-04-14 12:36] upgraded xorg-utils (7.4-2 -> 7.4-3) Unfortunately, I am facing some screen corruptions, as seen on this screenshot: http://nbigaouette.inrs-emt.homelinux.net/linux/arch/xf86_video_intel_corru… The only way to make it disappear is to force a redraw. It is not sufficient to hide the window and make it appear again. If the corruption appears inside the text of a KDE editor, moving the cursor to the corrupted line should change its background color and thus force a redraw. Or if it appears in toolbars, I need to mouse over the toolbard to refresh it. This happens on both of my computers. One is an asus eeepc 1000: 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03) The other is a Dell Optiplex 755 desktop: 00:02.0 VGA compatible controller: Intel Corporation 82Q35 Express Integrated Graphics Controller (rev 02) 00:02.1 Display controller: Intel Corporation 82Q35 Express Integrated Graphics Controller (rev 02) Both are using kwin's compositing and no xorg.conf. These are what might look suspiscious from /var/log/Xorg.0.log: [...] (II) intel(0): Comparing regs from server start up to After PreInit (WW) intel(0): Register 0x61114 (PORT_HOTPLUG_STAT) changed from 0x00000000 to 0x00000b00 [...] (II) intel(0): I830CheckAvailableMemory: 4669436 kB available (WW) intel(0): DRI2 requires UXA [...] drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such device or address) drmOpenDevice: open result is -1, (No such device or address) drmOpenDevice: Open failed drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such device or address) drmOpenDevice: open result is -1, (No such device or address) drmOpenDevice: Open failed drmOpenByBusid: Searching for BusID pci:0000:00:02.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 10, (OK) drmOpenByBusid: drmOpenMinor returns 10 drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0 (II) [drm] loaded kernel module for "i915" driver. [...] exaCopyDirty: Pending damage region empty! What could be the cause of that? Thanx!

7 14

[arch-general] Why do I have 20-ups-nut-device.fdi in my / dir?
by David C. Rankin, J.D.,P.E. 05 May '09

05 May '09

Listmates, Picking around with mc, I saw a file that looked really out of place. In my / dir, I have 20-ups-nut-device.fdi. Shouldn't that be in /etc/hal/fdi/policy/. I plead the 5th, I don't know how it got there. This is on my x86_64 box. The date and time of the file are: -rw-r--r-- 1 root root 12367 2008-06-17 08:39 20-ups-nut-device.fdi [20:05 alchemy:/] # pacman -Qo 20-ups-nut-device.fdi error: No package owns 20-ups-nut-device.fdi Dunno? Can somebody take a quick check and see if they have this stray .fdi file in their / directory. It looks like a 'network ups tools' (nut) policy, but why it's in / escapes me. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com

6 7

[arch-general] freetype2 with enabled tt bytecode interpreter, license issues?
by Gerardo Exequiel Pozzi 05 May '09

05 May '09

Hi, Because it is being a topic of great interest to the licenses of the packages, I question, because I'm not good at anything legal issues: This package with this option enabled, not is problematic in legal terms? http://freetype.sourceforge.net/patents.html Personally in my machine, I recompiled this package without the patch, I prefer the auto-hinting from freetype2, because fonts looks better (at least on CRT), I know that this can be configured with fontconf, but because some programs/libs based on xpdf libs (example poppler*, kpdf), look at headers at compile time instead of using fontconfig I recompile these packages too. Searching in the bug tracker i found this old ticket http://bugs.archlinux.org/task/2033 Citation from ftoption.h: /* Define TT_CONFIG_OPTION_BYTECODE_INTERPRETER if you want to compile */ /* a bytecode interpreter in the TrueType driver. Note that there are */ /* important patent issues related to the use of the interpreter. */ /* */ /* By undefining this, you will only compile the code necessary to load */ /* TrueType glyphs without hinting. */ /* */ /* Do not #undef this macro here, since the build system might */ /* define it for certain configurations only. */ Thanks for your time. -- Gerardo Exequiel Pozzi ( djgera ) http://www.djgera.com.ar KeyID: 0x1B8C330D Key fingerprint = 0CAA D5D4 CD85 4434 A219 76ED 39AB 221B 1B8C 330D

3 6

Re: [arch-general] org.freedesktop.hal.storage.mount-removable no <-- (action, result)
by David C. Rankin, J.D.,P.E. 05 May '09

05 May '09

On Monday 04 May 2009 13:36:03 you wrote: > [snip] > > I don't know if this has anything to do with your problem, but I've had > difficulty auto-mounting NTFS partitions as read/write. The reason seems > to be that auto-mount autodetects NTFS partitions as using the ntfs driver, > but in order to get full functionality, you need to use the ntfs-3g driver. > Mounting as root, explicitly using the ntfs-3g driver, works. > > HTH, > Dave Moore Yes, I think that is exactly what the problem is. I didn't want 'rw', all I wanted was read-only. So I just created a directory as a mount point and did 'mount -t ntfs /dev/sdb2 /mountpoint'. It worked just fine. I'll play around to find a way to get this (politely put 'dad-gum') hal/dbus/PolicyKit to do what a simple 'mount -t ntfs' had done for years.... -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com

1 0

[arch-general] Laptop Install - 2 questions remain, WPA and Compiz with Radeon Driver
by David C. Rankin, J.D.,P.E. 05 May '09

05 May '09

Listmates, The laptop install (Toshiba 205D) went great accept where I am stuck with video drivers for my ati card, and the last little nit of getting wifi to start automatically. First the easy one, the wireless: (1) My laptop has an Atheros card and is happily using the madwifi driver. The only problem is that I'm starting it manually and need to know where to put the pieces to have it start automatically. Basically, it takes 3 commands to get my wifi going: ESSID=${1:-skyline} IFACE=${2:-wlan0} iwconfig ${IFACE} essid "${ESSID}" wpa_supplicant -i${IFACE} -Dwext -c/etc/wpa_supplicant.conf -d -B >> /var/log/wpa_start.log 2>&1 sleep 2 # This doesn't count as a command dhcpcd wlan0 My question is "Where do I put this stuff to make it happen when I start Arch?? (2) No Compiz with the radeon driver. I know there must be a trick or two that will make this work. Heck, I even got compiz working on the intel card, so I know the ATI card (X1200) will do it (it does it with the fglrx driver on openSuSE). However, I don't know what the tricks are to getting it working on the stock radeon driver. Any other ATI Arch users know any more about this?? Here is my current xorg.conf: # Section "Files" FontPath "/usr/share/fonts/misc:unscaled" FontPath "/usr/share/fonts/local" FontPath "/usr/share/fonts/75dpi:unscaled" FontPath "/usr/share/fonts/100dpi:unscaled" FontPath "/usr/share/fonts/Type1" FontPath "/usr/share/fonts/URW" FontPath "/usr/share/fonts/speedo" FontPath "/usr/share/fonts/artwiz-fonts" FontPath "/usr/share/fonts/cyrillic" FontPath "/usr/share/fonts/truetype" FontPath "/usr/share/fonts/TTF" FontPath "/usr/share/fonts/uni:unscaled" FontPath "/usr/local/share/fonts" FontPath "/opt/kde3/share/fonts" InputDevices "/dev/gpmdata" InputDevices "/dev/input/mice" EndSection Section "ServerFlags" Option "AllowMouseOpenFail" "on" Option "IgnoreABI" "on" EndSection Section "Module" Load "dbe" Load "type1" Load "freetype" Load "extmod" Load "glx" Load "dri" EndSection Section "InputDevice" Driver "kbd" Identifier "Keyboard[0]" Option "Protocol" "Standard" Option "XkbLayout" "us" Option "XkbModel" "microsoftpro" Option "XkbRules" "xfree86" EndSection Section "InputDevice" Driver "mouse" Identifier "Mouse[1]" Option "Buttons" "5" Option "Device" "/dev/input/mice" Option "Name" "Microsoft Wheel Mouse Optical" Option "Protocol" "explorerps/2" Option "Vendor" "Sysp" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" Identifier "Mouse[3]" Driver "synaptics" Option "Device" "/dev/input/mice" Option "Emulate3Buttons" "on" Option "Name" "Touchpad" Option "SHMConfig" "on" Option "Vendor" "Synaptics" Option "ZAxisMapping" "4 5" EndSection Section "Monitor" Identifier "Monitor[0]" VendorName "TOSHIBA" ModelName "TOSHIBA 17IN TRUEBRIGHT" UseModes "Modes[0]" DisplaySize 367 230 HorizSync 30.0 - 70.0 VertRefresh 43.0 - 60.0 Option "CalcAlgorithm" "XServerPool" Option "DPMS" Option "PreferredMode" "1440x900" EndSection Section "Modes" Identifier "Modes[0]" EndSection Section "Screen" DefaultDepth 24 SubSection "Display" Depth 15 Modes "1440x900" "1024x768" "800x600" EndSubSection SubSection "Display" Depth 16 Modes "1440x900" "1024x768" "800x600" EndSubSection SubSection "Display" Depth 24 Modes "1440x900" "1024x768" "800x600" EndSubSection SubSection "Display" Depth 8 Modes "1440x900" "1024x768" "800x600" EndSubSection Device "Device[0]" Identifier "Screen[0]" Monitor "Monitor[0]" EndSection Section "Device" BoardName "RV350 NP" # BusID "1:5:0" Driver "radeon" Identifier "Device[0]" # Option "GARTSize" "32" VendorName "ATI" EndSection Section "ServerLayout" Identifier "Layout[all]" InputDevice "Keyboard[0]" "CoreKeyboard" InputDevice "Mouse[1]" "CorePointer" InputDevice "Mouse[3]" "SendCoreEvents" Option "Clone" "off" Option "Xinerama" "off" Screen 0 "Screen[0]" 0 0 EndSection Section "DRI" Group "video" Mode 0660 EndSection Section "Extensions" Option "Composite" "true" Option "DAMAGE" "true" EndSection -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com

4 7

[arch-general] Function keys not working?
by David Rosenstrauch 05 May '09

05 May '09

Not sure what happened but looks like all of a sudden the function keys (i.e., F1 through F12) are no longer working on my keyboard today. REALLY annoying. Tried using xev and it's responding with weird key codes: F1 - keycode 244 (keysym 0x0, NoSymbol) F3 - nothing F11 - keycode 210 (keysym 0x1008ff43, XF86Launch3) Anybody know WTF is up and how to fix? Is this something having to do with the recent upgrade to xf86-input-evdev? Tnx, DR

1 2

[arch-general] kde3 Error: Could Not Determine Resource Status - Kmail??
by David C. Rankin, J.D.,P.E. 04 May '09

04 May '09

Listmates, Every minute or two I have this large and annoying dialog appear on the screen complainting about something related to kmail. The difficult part about it is it does *not* tell you what it is complaining about. The only thing close to a description it gives is "Could not stat resource". Huh? I have a screenshot of it here: ( 50K ) http://www.3111skyline.com/download/Archlinux/kde/kontact-err.jpg The text of the error states: <quote> Error while getting folder information. Could Not Determine Resource Status An attempt to determine information about the status of the resource Mail, such as the resource name, type, size, etc., was unsuccessful. Technical reason: Could Not Stat Resource Details of the request: URL: (unknown) Date and time: Sunday 03 May 2009 04:30 pm Additional information: Mail Possible causes: The specified resource may not have existed or may not be accessible. A protocol error or incompatibility may have occurred. Although unlikely, a hardware error may have occurred. Possible solutions: Retry the request and ensure your authentication details are entered correctly. Contact your appropriate computer support system, whether the system administrator, or technical support group for further assistance. Anybody see this before and more importantly, How do I fix it? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com

3 3