May 2011 - openSUSE Users - openSUSE Mailing Lists

[opensuse] In composing a quite long email and thunderbird crashed
by Duaine Hechler 01 Jun '11

01 Jun '11

Is my email still out here somewhere ? -- Duaine Hechler Piano, Player Piano, Pump Organ Tuning, Servicing& Rebuilding Reed Organ Society Member Florissant, MO 63034 (314) 838-5587 dahechler(a)att.net www.hechlerpianoandorgan.com -- Home& Business user of Linux - 11 years -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

4 7

[opensuse] Amazing New Tetris(R) Game For openSUSE!
by Jesse Palser 31 May '11

31 May '11

Hi, My team and I are working on an open-source cross-platform multi-player Tetris(R) game called: "TetriCrisis 3 100% C.P.U."... Was hoping some people can help test it on their openSUSE systems? Game requires the following: - SDL 1.2 - SDL_Image - SDL_Mixer - SDL_TTF - G++ - OpenGL(R) w/ hardware acceleration You can download the current Beta 5 for Linux here: http://16bitsoft.com/files/TC3100CPU/Linux/tc3.5-linux_beta5.zip The download includes a makefile to build on any 32bit/64bit Linux. Thanks! Jesse "JeZ+Lee" Palser JessePalser(a)GMail.com 16BitSoft Video Game Design Studio www.16BitSoft.com -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

3 2

[opensuse] dbus on OS 11.4
by Jim Flanagan 31 May '11

31 May '11

After a few days running I'm seeing dbus taking 95% + cpu resources. When this occurs, launching programs won't open, but running ones work somewhat but slow. Has anyone else seen this? This happens on 2 different boxes, both with OS 11.4 64 bit installed, KDE default. This seems to happen sooner with Firefox left open, but it also happens with no programs running other than system startup. Thanks for any heads up. Jim F -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] Wants root password to reset brightness upon resume?
by John Andersen 31 May '11

31 May '11

Lately my 11.4/kde 4.6.3 machine will pop up a request for root's password when I wake it from suspend to ram. Often when I'm finished with the laptop, I will simply close the lid because suspend to ram is set up and works very well. Often I will close the lid when the screen is already dark, because powersave has kicked in due to sitting there unused for a while, and the powersave profile says to dim the screen. Then when I resume the machine by simply opening the lid again, it will be rather dim, at some point in the process it will ask for root's password to adjust brightness. Since I have keyboard key combinations for brightness, I simply ignore this and brighten it up manually and the message usually goes away. So the question is, why does it need root to brighten the display when it didn't need root to dim it, and why does this only happen upon resume from suspend to ram if (and apparently only if) I close the lid with the screen already blanked out. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 2

[opensuse] Using a USB-to-VGA (displaylink) adapter with 11.4
by R. Tyler Croy 31 May '11

31 May '11

Howdy folks, I'm having trouble getting this adapter <http://www.amazon.com/gp/product/B0038P1TP4> set up properly. THe kernel (2.6.38.6-29-desktop, tumbleweedin' here) properly recognizes the device but I cannot quite figure out how to properly configure X.org to use it. I'm a heavy user of xrandr since I regularly use an external monitor with my laptop, and it doesn't show up in the `xrandr -q` output either. Below is the relevant section of /var/log/messages and the `xrandr -q` output. Any ideas? :-/ May 26 11:47:15 kiwi kernel: [64911.595456] usb 1-1.1.2: new high speed USB device using ehci_hcd and address 30 May 26 11:47:15 kiwi kernel: [64911.674283] usb 1-1.1.2: New USB device found, idVendor=17e9, idProduct=0360 May 26 11:47:15 kiwi kernel: [64911.674292] usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 May 26 11:47:15 kiwi kernel: [64911.674298] usb 1-1.1.2: Product: USB to DVI-19 May 26 11:47:15 kiwi kernel: [64911.674303] usb 1-1.1.2: Manufacturer: DisplayLink May 26 11:47:15 kiwi kernel: [64911.674308] usb 1-1.1.2: SerialNumber: 442313 May 26 11:47:15 kiwi kernel: [64911.675454] udlfb: DisplayLink USB to DVI-19 - serial #442313 May 26 11:47:15 kiwi kernel: [64911.675462] udlfb: vid_17e9&pid_0360&rev_0102 driver's dlfb_data struct at ffff8800ade8a000 May 26 11:47:15 kiwi kernel: [64911.675467] udlfb: console enable=0 May 26 11:47:15 kiwi kernel: [64911.675471] udlfb: fb_defio enable=0 May 26 11:47:15 kiwi kernel: [64911.676040] udlfb: vendor descriptor length:22 data:22 5f 01 0020 05 00 01 03 00 04 May 26 11:47:15 kiwi kernel: [64911.676046] udlfb: DL chip limited to 2360000 pixel modes May 26 11:47:15 kiwi kernel: [64911.676201] udlfb: allocated 4 65024 byte urbs May 26 11:47:15 kiwi mtp-probe: checking bus 1, device 30: "/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-1/1-1.1/1-1.1.2" May 26 11:47:15 kiwi kernel: [64911.759067] udlfb: 1920x1200 valid mode May 26 11:47:15 kiwi kernel: [64911.759075] udlfb: 640x480 valid mode May 26 11:47:15 kiwi kernel: [64911.759080] udlfb: 800x600 valid mode May 26 11:47:15 kiwi kernel: [64911.759085] udlfb: 800x600 valid mode May 26 11:47:15 kiwi kernel: [64911.759089] udlfb: 1024x768 valid mode May 26 11:47:15 kiwi kernel: [64911.759093] udlfb: 1600x1200 valid mode May 26 11:47:15 kiwi kernel: [64911.759097] udlfb: 1280x1024 valid mode May 26 11:47:15 kiwi kernel: [64911.759102] udlfb: 1280x960 valid mode May 26 11:47:15 kiwi kernel: [64911.759106] udlfb: 1280x1280 valid mode May 26 11:47:15 kiwi kernel: [64911.759110] udlfb: 1440x1440 valid mode May 26 11:47:15 kiwi kernel: [64911.759115] udlfb: 1680x1680 beyond chip capabilities May 26 11:47:15 kiwi kernel: [64911.759120] udlfb: Reallocating framebuffer. Addresses will change! May 26 11:47:15 kiwi kernel: [64911.763677] udlfb: 1600x1200 valid mode May 26 11:47:15 kiwi kernel: [64911.763684] udlfb: set_par mode 1600x1200 May 26 11:47:15 kiwi kernel: [64911.770498] udlfb: DisplayLink USB device /dev/fb1 attached. 1600x1200 resolution. Using 7504K framebuffer memory May 26 11:47:15 kiwi mtp-probe: bus: 1, device: 30 was not an MTP device % xrandr -q Screen 0: minimum 320 x 200, current 1920 x 2000, maximum 8192 x 8192 LVDS1 connected 1280x800+0+1200 (normal left inverted right x axis y axis) 261mm x 163mm 1280x800 60.0*+ 50.0 1024x768 60.0 800x600 60.3 56.2 640x480 59.9 VGA1 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0*+ 1600x1200 60.0 1680x1050 60.0 1280x1024 60.0 1440x900 59.9 1280x960 60.0 1280x800 59.8 1024x768 60.0 800x600 60.3 56.2 640x480 60.0 HDMI1 disconnected (normal left inverted right x axis y axis) DP1 disconnected (normal left inverted right x axis y axis) HDMI2 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) DP3 disconnected (normal left inverted right x axis y axis) - R. Tyler Croy -------------------------------------- Code: http://github.com/rtyler Chatter: http://identi.ca/agentdero http://twitter.com/agentdero

3 3

[opensuse] Update on LiveUSB 11.4 killed the Network
by Paulo Motta 31 May '11

31 May '11

I have been using and promoting openSUSE 11.4 on LiveUSB. Last week I was updating the USB drive when the system rebooted the network was dead, I did had the time to re-try the operation installing updates one at a time to see what really killed the network. Maybe the kernel update, maybe some update on KDE. This happened both in 32 and 64 bits, does anybody had a similar problem on a 11.4 box (not necessarly a USB drive problem I think)? Cheers -- Paulo Motta -- "Qualquer tecnologia suficientemente avançada é indistinguível da mágica" - Arthur C. Clarke -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] WLAN on Thinkpad T61 (with PRO/Wireless 4965 AG) stopped working after upgrade from 11.3 to 11.4
by Sven Hartrumpf 31 May '11

31 May '11

Hi all. After upgrading from openSUSE 11.3 to openSUSE 11.4, I cannot turn on any wireless connection. For example in KDE, the element in the NetworkManager is always ghosted. The kernel module iwlagn is loaded: # lsmod | grep iwl iwlagn 335035 0 iwlcore 152599 1 iwlagn mac80211 266082 2 iwlagn,iwlcore cfg80211 155017 3 iwlagn,iwlcore,mac80211 # uname -a Linux ... 2.6.37.6-0.5-desktop #1 SMP PREEMPT 2011-04-25 21:48:33 +0200 i686 i686 i386 GNU/Linux Any ideas? Sven -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

5 10

[opensuse] Blowing away 11.3
by James Knott 31 May '11

31 May '11

After all the problems with 11.4 and 11.3 on my ThinkPad, I've decided to blow it all away and revert to 11.0. At least that worked well. Problems: 11.4 - unable to use KDE, as system locked up and display faded 11.3, unreliable USB detection. Why no "Safely remove" option? Display often shifted about 1/2" to right, but mouse didn't. Poorer performance. General frustration with KDE 4. As I've often pointed out, since I first saw KDE 4, a few years ago, it needs a lot of work to be anywhere near as useful as 3.5 It would be *VERY* nice if support were resumed for 11.0, which would appear to be the last decent openSUSE distro. My experiences with KDE 4 are almost enough to send me back to Windows! What a piece of crap!!! -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

7 11

[opensuse] 局域网内无法Ping到SUSE，求助
by Poppy 31 May '11

31 May '11

全新安装OpenSuse11.3，安装时使用默认设置。现在Suse上网什么的都正常，可以ping通局域网内其他及其。但是其它机器无法Ping到SUSE，防火墙已经从YaST2中关闭。请问下，需要解决这个问题，还有什么工作要做啊？ -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

5 4

[opensuse] KMS and Xorg not finding native resolution with INTEL driver
by Charles Philip Chan 31 May '11

31 May '11

Hello all: I upgraded to 11.4 a few days ago and I am having problems with KMS and Xorg not finding and using the native resolution (1680x1050) of my monitor. There seem to be a problem probing the edid of my monitor and here is what I get in my Xorg.0.log: ,----[ Excerpt form Xorg.0.org ] | [ 1557.566] (II) intel(0): EDID for output VGA1 | [ 1557.566] (II) intel(0): Not using default mode "640x350" (vrefresh out of range) | [ 1557.566] (II) intel(0): Not using default mode "320x175" (doublescan mode not supported) | [ 1557.566] (II) intel(0): Not using default mode "640x400" (vrefresh out of range) | [ 1557.566] (II) intel(0): Not using default mode "320x200" (doublescan mode not supported) | [ 1557.566] (II) intel(0): Not using default mode "720x400" (vrefresh out of range) | [ 1557.566] (II) intel(0): Not using default mode "360x200" (doublescan mode not supported) | [ 1557.566] (II) intel(0): Not using default mode "320x240" (doublescan mode not supported) | [ 1557.566] (II) intel(0): Not using default mode "640x480" (vrefresh out of range) | [ 1557.566] (II) intel(0): Not using default mode "320x240" (doublescan mode not supported) | [ 1557.566] (II) intel(0): Not using default mode "640x480" (vrefresh out of range) | [ 1557.566] (II) intel(0): Not using default mode "320x240" (doublescan mode not supported) | [ 1557.566] (II) intel(0): Not using default mode "640x480" (vrefresh out of range) | [ 1557.566] (II) intel(0): Not using default mode "320x240" (doublescan mode not supported) | [ 1557.566] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported) | [ 1557.566] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported) | [ 1557.566] (II) intel(0): Not using default mode "800x600" (vrefresh out of range) | [ 1557.566] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported) | [ 1557.566] (II) intel(0): Not using default mode "800x600" (vrefresh out of range) | [ 1557.566] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported) | [ 1557.566] (II) intel(0): Not using default mode "800x600" (vrefresh out of range) | [ 1557.566] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported) | [ 1557.566] (II) intel(0): Not using default mode "1024x768i" (vrefresh out of range) | [ 1557.566] (II) intel(0): Not using default mode "512x384i" (doublescan mode not supported) | [ 1557.566] (II) intel(0): Not using default mode "512x384" (doublescan mode not supported) | [ 1557.566] (II) intel(0): Not using default mode "1024x768" (vrefresh out of range) | [ 1557.566] (II) intel(0): Not using default mode "512x384" (doublescan mode not supported) | [ 1557.566] (II) intel(0): Not using default mode "1024x768" (vrefresh out of range) | [ 1557.566] (II) intel(0): Not using default mode "512x384" (doublescan mode not supported) | [ 1557.566] (II) intel(0): Not using default mode "1024x768" (vrefresh out of range) | [ 1557.566] (II) intel(0): Not using default mode "512x384" (doublescan mode not supported) | [ 1557.566] (II) intel(0): Not using default mode "1152x864" (vrefresh out of range) | [ 1557.566] (II) intel(0): Not using default mode "576x432" (doublescan mode not supported) | [ 1557.566] (II) intel(0): Not using default mode "1280x960" (hsync out of range) | [ 1557.566] (II) intel(0): Not using default mode "640x480" (doublescan mode not supported) | [ 1557.566] (II) intel(0): Not using default mode "1280x960" (vrefresh out of range) | [ 1557.566] (II) intel(0): Not using default mode "640x480" (doublescan mode not supported) | [ 1557.566] (II) intel(0): Not using default mode "1280x1024" (hsync out of range) | [ 1557.566] (II) intel(0): Not using default mode "640x512" (doublescan mode not supported) | [ 1557.566] (II) intel(0): Not using default mode "1280x1024" (vrefresh out of range) | [ 1557.566] (II) intel(0): Not using default mode "640x512" (doublescan mode not supported) | [ 1557.566] (II) intel(0): Not using default mode "1280x1024" (vrefresh out of range) | [ 1557.566] (II) intel(0): Not using default mode "640x512" (doublescan mode not supported) | [ 1557.566] (II) intel(0): Not using default mode "1600x1200" (hsync out of range) | [ 1557.566] (II) intel(0): Not using default mode "800x600" (doublescan mode not supported) | [ 1557.566] (II) intel(0): Not using default mode "1600x1200" (vrefresh out of range) | [ 1557.566] (II) intel(0): Not using default mode "800x600" (doublescan mode not supported) | [ 1557.566] (II) intel(0): Not using default mode "1600x1200" (vrefresh out of range) | [ 1557.566] (II) intel(0): Not using default mode "800x600" (doublescan mode not supported) | [ 1557.566] (II) intel(0): Not using default mode "1600x1200" (vrefresh out of range) | [ 1557.566] (II) intel(0): Not using default mode "800x600" (doublescan mode not supported) | [ 1557.566] (II) intel(0): Not using default mode "1600x1200" (vrefresh out of range) | [ 1557.566] (II) intel(0): Not using default mode "800x600" (doublescan mode not supported) | [ 1557.566] (II) intel(0): Not using default mode "1792x1344" (hsync out of range) | [ 1557.566] (II) intel(0): Not using default mode "896x672" (doublescan mode not supported) | [ 1557.566] (II) intel(0): Not using default mode "1792x1344" (vrefresh out of range) | [ 1557.566] (II) intel(0): Not using default mode "896x672" (doublescan mode not supported) | [ 1557.566] (II) intel(0): Not using default mode "1856x1392" (hsync out of range) | [ 1557.566] (II) intel(0): Not using default mode "928x696" (doublescan mode not supported) | [ 1557.566] (II) intel(0): Not using default mode "1856x1392" (vrefresh out of range) | [ 1557.566] (II) intel(0): Not using default mode "928x696" (doublescan mode not supported) | [ 1557.566] (II) intel(0): Not using default mode "1920x1440" (hsync out of range) | [ 1557.566] (II) intel(0): Not using default mode "960x720" (doublescan mode not supported) | [ 1557.566] (II) intel(0): Not using default mode "1920x1440" (vrefresh out of range) | [ 1557.566] (II) intel(0): Not using default mode "960x720" (doublescan mode not supported) | [ 1557.567] (II) intel(0): Not using default mode "832x624" (vrefresh out of range) | [ 1557.567] (II) intel(0): Not using default mode "416x312" (doublescan mode not supported) | [ 1557.567] (II) intel(0): Not using default mode "1400x1050" (hsync out of range) | [ 1557.567] (II) intel(0): Not using default mode "700x525" (doublescan mode not supported) | [ 1557.567] (II) intel(0): Not using default mode "1400x1050" (vrefresh out of range) | [ 1557.567] (II) intel(0): Not using default mode "700x525" (doublescan mode not supported) | [ 1557.567] (II) intel(0): Not using default mode "1920x1440" (vrefresh out of range) | [ 1557.567] (II) intel(0): Not using default mode "960x720" (doublescan mode not supported) | [ 1557.567] (II) intel(0): Not using default mode "2048x1536" (hsync out of range) | [ 1557.567] (II) intel(0): Not using default mode "1024x768" (doublescan mode not supported) | [ 1557.567] (II) intel(0): Not using default mode "2048x1536" (vrefresh out of range) | [ 1557.567] (II) intel(0): Not using default mode "1024x768" (doublescan mode not supported) | [ 1557.567] (II) intel(0): Not using default mode "2048x1536" (vrefresh out of range) | [ 1557.567] (II) intel(0): Not using default mode "1024x768" (doublescan mode not supported) | [ 1557.567] (II) intel(0): Printing probed modes for output VGA1 | [ 1557.567] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz) | [ 1557.567] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz) | [ 1557.567] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz) | [ 1557.567] (II) intel(0): Modeline "848x480"x60.0 33.75 848 864 976 1088 480 486 494 517 +hsync +vsync (31.0 kHz) | [ 1557.567] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 489 492 525 -hsync -vsync (31.5 kHz) | [ 1557.567] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz) `---- If I manually put in the HorizSync, VertRefresh and a modeline generated by cvt in monitor.conf, kdm would not even start. I have to resort to using xrandr to add and set the mode. What could be the problem? Thanks. Charles -- "We all know Linux is great...it does infinite loops in 5 seconds." (Linus Torvalds about the superiority of Linux on the Amterdam Linux Symposium)

3 3