May 2009 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Can't read mounted floppy disk
by Stan Goodman 02 Jun '09

02 Jun '09

Only rarely anymore does one have to read of write diskettes, and I am having to do so now for the first time since I installed openSuSE. I have a floppy disk containing files. I can read these files in another OS using the same floppy drive on the same machine, but not in openSuSE. The Disk List in the Konqueror /sysinfo display shows that the available space on this diskette is much smaller than the total space, so it does see that there are files there. According to the Properties for fd0, the diskette is mounded on "/media/floppy". The following is the line in fstab that relates to the floppy drive: ***** /dev/fd0 /media/floppy auto noauto,user,sync 0 0 ***** When I click on the floppy-disk icon, Konqueror opens a window, showing the Location as: "media:/fd0", which doesn't look quite the same as the alleged mount point. The window is empty, although I know that there are files there. In the Konqueror view of directory "floppy", the status line at the bottom shows "No Items - No Files - No folders". The permissions for the floppy drive are RW for the owner (which is me), RO for group and others. It is not possible, even as root, to extend writing to group. Can someone help me see what is wrong here? -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

3 10

[opensuse] Problem with VirutalBox
by Chuck Payne 01 Jun '09

01 Jun '09

Guys, I am using AD to log into my linux box. I want to use VirtualBox, but I can't see to add my account to the group. How can I add my account to the group? -- ---------------------------------------- When a place gets crowded enough to require ID's, social collapse is not far away. It is time to go elsewhere. The best thing about space travel is that it made it possible to go elsewhere. -- Robert Heinlein -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 2

[opensuse] ssh tunnelling for firefox
by jdd 01 Jun '09

01 Jun '09

Hello :-) I try using a tunnelling from openSUSE 11.1 to an online server with the syntax below with firefox: $ssh -D 9999 username@ip-address-of-ssh-server and proxy localhost 9999 in firefox google seems to say there is nothing more to do, but FF keep saying the proxy don't accept the connection I tried this with a 10.2 server (old, I know, to be replaced by the next) and ubuntu server with the same result. of course the connection terminal to the server opens, I give the pass, but FF still don't works any idea? thanks jdd -- http://www.dodin.net http://valerie.dodin.org http://news.opensuse.org/2009/04/13/people-of-opensuse-jean-daniel-dodin/ -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

3 3

Re: [opensuse] I've messed something up - YaST modules won't load...
by Rodney Baker 31 May '09

31 May '09

On Mon, 1 Jun 2009 01:32:13 Randall R Schulz wrote: > On Sunday May 31 2009, Rodney Baker wrote: > > Hi, all. Somehow I've messed something up along the way and I suspect > > I've got some incompatible libs installed somewhere. > > > > Every time YaST2 Control Centre tries to load a module I get xmessage > > popping up with an error message: > > > > YaST got signal 11 at YCP file Wizard.ycp:341 > > /sbin/yast2: line 421: 15125 Segmentation fault $ybindir/y2base > > $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS > > > > This is occurring under KDE3, KDE4 and Gnome. The last time I saw > > this it was related to incompatible qt libs but I'm not sure if this > > is the case this time. (See - that's what I get for playing around > > with factory repositories etc...some people never learn ;-) ). > > > > Anyone got any ideas? > > You can see if it's related to GUI library issues by running the > character-mode version. You'll get that if you're outside a GUI context > completely, of course (virtual console, SSH session, etc.). To force it > from a terminal emulator in an X session, just suppress the DISPLAY > variable: > > % DISPLAY= yast2 > > > Randall Schulz I can run the ncurses version of YaST within Konsole (or from a virtual console) - that works fine. YaST2, however dies with a message "Couldn't load plug-in ncurses-pkg." The relevant section from the log file... 2009-06-01 01:59:41 <1> mako(29895) [YCP] clients/inst_packages.ycp:147 Stage: normal, Mode: normal, Args: [`searchMode, `repoMgr] 2009-06-01 01:59:41 <1> mako(29895) [YCP] clients/inst_packages.ycp:159 inst_packages called with: `searchMode 2009-06-01 01:59:41 <1> mako(29895) [ui-shortcuts] YShortcutManager.cc(checkShortcuts):79 Not enough widgets with valid shortcut characters - no check 2009-06-01 01:59:41 <3> mako(29895) [ui] YUIPlugin.cc(YUIPlugin):48 Could not load UI plugin "ncurses_pkg": /usr/lib/YaST2/plugin/libpy2ncurses_pkg.so.2: undefined symbol: _ZN10NCTablePad8setOrderEi 2009-06-01 01:59:41 <2> mako(29895) [ui] NCPackageSelectorPluginStub.cc(NCPackageSelectorPluginStub):47 THROW: Couldn't load plug-in ncurses_pkg 2009-06-01 01:59:41 <2> mako(29895) [ui] YCP_UI.cc(ReplaceWidget):834 CAUGHT: Couldn't load plug-in ncurses_pkg 2009-06-01 01:59:41 <3> mako(29895) [libycp] clients/inst_packages.ycp:36 UI::ReplaceWidget() failed: UI::ReplaceWidget( `rep, `PackageSelector (`id (`packages), `opt (`searchMode, `repoMgr), "") ) 2009-06-01 01:59:41 <1> mako(29895) [ui] YPushButton.cc(setFunctionKey):160 Guessing button role YOKButton for YPushButton "Close" at 0x92b1e00 from function key F10 2009-06-01 01:59:48 <2> mako(29895) [ui] YWidget.cc(findWidget):627 THROW: No widget with ID `packages 2009-06-01 01:59:48 <2> mako(29895) [ui] YCP_UI.cc(RunPkgSelection):1390 CAUGHT: No widget with ID `packages 2009-06-01 01:59:48 <3> mako(29895) [libycp] clients/inst_packages.ycp:49 RunPkgSelection() failed 2009-06-01 01:59:48 <1> mako(29895) [ui] YWidget.cc(dumpWidget):704 Widget tree: YDialog at 0x9275dd8 2009-06-01 01:59:48 <1> mako(29895) [ui] YWidget.cc(dumpWidget):704 Widget tree: YReplacePoint ID: "`rep" at 0x882ecf0 2009-06-01 01:59:48 <1> mako(29895) [YCP] clients/inst_packages.ycp:51 Package selector returned nil 2009-06-01 01:59:48 <1> mako(29895) [Interpreter] clients/inst_packages.ycp:172 Called YaST client returned. 2009-06-01 01:59:48 <1> mako(29895) [YCP] clients/inst_packages.ycp:387 inst_packages returns nil 2009-06-01 01:59:48 <1> mako(29895) [ncurses] YNCursesUI.cc(~YNCursesUI):113 Stop YNCursesUI 2009-06-01 01:59:48 <1> mako(29895) [ncurses] NCurses.cc(~NCurses):149 Shutdown NCurses... 2009-06-01 01:59:48 <1> mako(29895) [ncurses] NCurses.cc(~NCurses):168 NCurses down Note that I do have yast2-ncurses-pkg installed (in fact I tried reinstalling it with zypper in --force the first time this failed - no change). I think I've properly hosed it this time. Nevertheless, I can still run YaST in a terminal and I can still install stuff via the zypper cli so all is not lost. It would be nice to know what I screwed up and how to fix it (and how not to do it again). Cheers, Rodney. -- =================================================== Rodney Baker VK5ZTV rodney.baker(a)iinet.net.au ===================================================

1 0

[opensuse] Device Loading persistent
by Mike McMullin 31 May '09

31 May '09

I'm having a bit of trouble with mythtv, it seems that that I have an issue with consistent video devices being loaded. I have an USB Webcam, and a HP-PVR which are duking it out for being video0 and video1, I know that there is a method for having persistent devices, but I'm having a major brain fart over what it's called and how to do it. Any ideas would be most appreciated. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] Kernel Panic init --Help
by Bob S 31 May '09

31 May '09

Hello SuSE people Running 10.3 64 bit. Yesterday I ran the Yast partioner to change labels on various partitions. While it was executing it froze at 85% finished. It sat there for over an hour and nothing worked, keyboard, mouse,etc. Had to do a hard shutdown. When I went to reboot I got the following message: --------------------------------------------------------------------------------------- /bin/run-init /sbin/init Permission denied Kernel Panic - not syncing: Attempted to kill init ! --------------------------------------------------------------------------------------- Googled the message and got lots of "init not found" and "init error parsing config"'s but nothing about my situation. I am able to access all of the partitions and did an e2fsck on that partition and no errors were found. I checked the permissions on init and they are correct. I also substituted another init for the existing one, No change. I tried to do a "Repair installed system" from the 10.3 dvd and that errored out with the message "There was an error in the installation process" Nothing in the boot log. Here are the last few lines of /var/log/messages: -------------------------------------------------------------------------------- May 29 23:30:01 Easystreet /usr/sbin/cron[8169]: PAM adding faulty module: /lib64/security/pam_deny.so May 29 23:30:01 Easystreet /usr/sbin/cron[8169]: Module is unknown May 29 23:31:03 Easystreet console-kit-daemon[2701]: WARNING: Unable to spawn /etc/ConsoleKit/run-session.d/dbus_at_console.ck: Failed to execute child process "/etc/ConsoleKit/run-session.d/dbus_at_console.ck" (Permission denied) May 29 23:31:03 Easystreet console-kit-daemon[2701]: WARNING: Unable to spawn /etc/ConsoleKit/run-session.d/dbus_at_console.ck: Failed to execute child process "/etc/ConsoleKit/run-session.d/dbus_at_console.ck" (Permission denied) May 29 23:31:03 Easystreet kdm: :0[8223]: Can't execute "/etc/X11/xdm/Xreset": Permission denied May 29 23:31:04 Easystreet kdm[8236]: Failed to execute shutdown command "/sbin/reboot" May 29 23:31:27 Easystreet mingetty[4815]: mingetty: tty1: can't exec /bin/login: Permission denied May 29 23:31:27 Easystreet init: cannot execute "/bin/sh" May 29 23:31:27 Easystreet init: cannot execute "/bin/sh" May 29 23:31:27 Easystreet init: cannot execute "/bin/sh" May 29 23:31:27 Easystreet init: cannot execute "/bin/sh" May 29 23:31:27 Easystreet init: cannot execute "/bin/sh" May 29 23:31:27 Easystreet init: cannot execute "/bin/sh" May 29 23:31:27 Easystreet init: cannot execute "/bin/sh" May 29 23:31:27 Easystreet init: cannot execute "/bin/sh" May 29 23:31:27 Easystreet init: cannot execute "/bin/sh" May 29 23:31:27 Easystreet init: cannot execute "/bin/sh" May 29 23:31:27 Easystreet init: Id "1" respawning too fast: disabled for 5 minutes -------------------------------------------------------------------------------------------- Here are the last 20 lines from "warn" ------------------------------------------------------------------------------------- May 29 23:30:01 Easystreet /usr/sbin/cron[8169]: PAM unable to dlopen(/lib64/security/pam_unix2.so): /lib64/security/pam_unix2.so: failed to map segment from shared object: Operation not permitted May 29 23:30:01 Easystreet /usr/sbin/cron[8169]: PAM adding faulty module: /lib64/security/pam_unix2.so May 29 23:30:01 Easystreet /usr/sbin/cron[8169]: PAM unable to dlopen(/lib64/security/pam_pwcheck.so): /lib64/security/pam_pwcheck.so: failed to map segment from shared object: Operation not permitted May 29 23:30:01 Easystreet /usr/sbin/cron[8169]: PAM adding faulty module: /lib64/security/pam_pwcheck.so May 29 23:30:01 Easystreet /usr/sbin/cron[8169]: PAM unable to dlopen(/lib64/security/pam_loginuid.so): /lib64/security/pam_loginuid.so: failed to map segment from shared object: Operation not permitted May 29 23:30:01 Easystreet /usr/sbin/cron[8169]: PAM adding faulty module: /lib64/security/pam_loginuid.so May 29 23:30:01 Easystreet /usr/sbin/cron[8169]: PAM unable to dlopen(/lib64/security/pam_limits.so): /lib64/security/pam_limits.so: failed to map segment from shared object: Operation not permitted May 29 23:30:01 Easystreet /usr/sbin/cron[8169]: PAM adding faulty module: /lib64/security/pam_limits.so May 29 23:30:01 Easystreet /usr/sbin/cron[8169]: PAM unable to dlopen(/lib64/security/pam_umask.so): /lib64/security/pam_umask.so: failed to map segment from shared object: Operation not permitted May 29 23:30:01 Easystreet /usr/sbin/cron[8169]: PAM adding faulty module: /lib64/security/pam_umask.so May 29 23:30:01 Easystreet /usr/sbin/cron[8169]: PAM unable to dlopen(/lib64/security/pam_warn.so): /lib64/security/pam_warn.so: failed to map segment from shared object: Operation not permitted May 29 23:30:01 Easystreet /usr/sbin/cron[8169]: PAM adding faulty module: /lib64/security/pam_warn.so May 29 23:30:01 Easystreet /usr/sbin/cron[8169]: PAM unable to dlopen(/lib64/security/pam_deny.so): /lib64/security/pam_deny.so: failed to map segment from shared object: Operation not permitted May 29 23:30:01 Easystreet /usr/sbin/cron[8169]: PAM adding faulty module: /lib64/security/pam_deny.so May 29 23:30:01 Easystreet /usr/sbin/cron[8169]: Module is unknown May 29 23:31:03 Easystreet console-kit-daemon[2701]: WARNING: Unable to spawn /etc/ConsoleKit/run-session.d/dbus_at_console.ck: Failed to execute child process "/etc/ConsoleKit/run-session.d/dbus_at_console.ck" (Permission denied) May 29 23:31:03 Easystreet console-kit-daemon[2701]: WARNING: Unable to spawn /etc/ConsoleKit/run-session.d/dbus_at_console.ck: Failed to execute child process "/etc/ConsoleKit/run-session.d/dbus_at_console.ck" (Permission denied) May 29 23:31:03 Easystreet kdm: :0[8223]: Can't execute "/etc/X11/xdm/Xreset": Permission denied May 29 23:31:04 Easystreet kdm[8236]: Failed to execute shutdown command "/sbin/reboot" May 29 23:31:27 Easystreet mingetty[4815]: mingetty: tty1: can't exec /bin/login: Permission denied ------------------------------------------------------------------------------------- Don't know what else to do. Need help. Hopefully some guru can point me in the right direction. Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] Suse 11.0 CPU oddities with ksoftirqd & migration
by James D. Parra 31 May '09

31 May '09

Hello, Getting a lot of cpu anomalies and after a bit of googling found that perhaps there is a kernel bug. Could that be the case here? kernel: 2.6.25.20-0.1-default #1 SMP 2008-12-12 20:30:38 +0100 x86_64 x86_64 x86_64 GNU/Linux Any significant disk i/o results in 90% to 100% wait times. I have the following in top; <snip> 3 root RT -5 0 0 0 S 0 0.0 0:00.00 migration/0 4 root 15 -5 0 0 0 S 0 0.0 0:00.10 ksoftirqd/0 5 root RT -5 0 0 0 S 0 0.0 0:00.00 migration/1 6 root 15 -5 0 0 0 S 0 0.0 0:00.04 ksoftirqd/1 7 root RT -5 0 0 0 S 0 0.0 0:00.00 migration/2 8 root 15 -5 0 0 0 S 0 0.0 0:00.04 ksoftirqd/2 9 root RT -5 0 0 0 S 0 0.0 0:00.00 migration/3 10 root 15 -5 0 0 0 S 0 0.0 0:00.04 ksoftirqd/3 11 root RT -5 0 0 0 S 0 0.0 0:00.00 migration/4 12 root 15 -5 0 0 0 S 0 0.0 0:00.00 ksoftirqd/4 13 root RT -5 0 0 0 S 0 0.0 0:00.00 migration/5 14 root 15 -5 0 0 0 S 0 0.0 0:00.00 ksoftirqd/5 15 root RT -5 0 0 0 S 0 0.0 0:00.00 migration/6 16 root 15 -5 0 0 0 S 0 0.0 0:00.00 ksoftirqd/6 17 root RT -5 0 0 0 S 0 0.0 0:00.00 migration/7 18 root 15 -5 0 0 0 S 0 0.0 0:00.00 ksoftirqd/7 <snip> Anyone else have this problem and is there a way to fix it? As an aside, 'dmesg' hasn't shown any disk or scsi errors. Thank you, James -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 2

[opensuse] Re: new 'man' behavior: "ask questions *WHY* REVERT?"
by Joachim Schrod 30 May '09

30 May '09

Dan Goodman wrote: > PS vi rules, if you take the time to learn how to use it. [...] > And the time to do so is a lot less than the time to learn the > Wordstar-like multi-key sequences of Emacs. OK, I'll bite. You wanted it, you get it... ;-) :-) I know vi -- both the original and vim -- better than almost any hard-core vi fans that I ever met. Actually, those who know vi better than I do, are no vi `fans' but proficient vi users who knows the deficiencies of their tool and are therefore no fans any more. I learned vi back in 1984, and met Emacs in 1988 or so, and use both until today. But: Emacs was a revelation, and it still is. vi is just an editor. Emacs is not an editor, but a working environment -- that's the whole difference. Back then, getting rid of a modal interface was like heaven -- I had enough of them before, when I had to worked with MVS and BS 2000, no need to repeat that on Unix. > "Real hackers know how to use vi, even if they prefer Emacs. But > if you > really know vi, what do you need Emacs for?" ;-) You know how vi is pronounced, do you? "Why?" Read the classic, `Tog on Interface', and get an enlightenment how user interfaces should be designed. Please, no modal interfaces in a thing as essential as a development environment. Btw, tongue-in-cheek, I don't know what you mean with `multi-key sequences', the days of Escape-Meta-Alt-Control-Shift are long gone; nowadays one uses the mouse or has adequate bindings to one's function keys -- just as in vim. In vi, I have more often to use : and some ex command than I use M-x and a function name in Emacs. > Plus, if you have to get on many different machines, many of which you > don't control, depending on Emacs leaves you on the dock when the ship > sails, at least part of the time. I have yet to find a Unix, POSIX-like, > Linux distro, or other non-M$ system that didn't have a fully > functioning vi on it, I beg to differ. As Wikipedia already tells: In a 1984 interview Bill Joy explained that, at Sun, he used an early desktop publishing program, called Interleaf; when visiting labs outside Sun, he used plain old ed. Although vi was almost ubiquitous, he could not count on the local version working the way he expected. However, ed was never modified, so he could count on making it work without stumbling. Or, from my personal experience: You obviously haven't been in many troubleshooting environments where one has a Windoze system without putty, and some suits breezing down your neck that you shall solve the problem with the multi-million Euro Unix system that doesn't run properly since 4 weeks and where they tried to solve the problems with their outsourced Indian provider and didn't succed? Lucky you. Not that Emacs would help here, but that's exactly my point. If I would restrict myself to something that works in all environments where I regularly have to work; I would need to restrict myself to ed, sed, and awk. (And yes, I know ed, and can use it properly. Since, as you should now: ed is *the* standard text editor; see http://www.dina.dk/~abraham/religion/ed-standard for reference.) 0.75 :-) Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod(a)acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

9 11

Re: [opensuse] Bug during logon
by russbucket 30 May '09

30 May '09

On Friday 29 May 2009 08:36:24 am Максим Фомин wrote: > 2009/5/29 russbucket <russbucket(a)nwi.net>: > > On Friday 29 May 2009 01:37:48 am Максим Фомин wrote: > >> Hello. > >> > >> I have a bug that really irritates me. It is an incorrect logon screen > >> during entering in my account and it looks like > >> http://f.imagehost.org/view/0282/bug. > >> > >> I use kde 4.2 and libqt 4.5. My monitor is intel gm 965 and resolution > >> is 1280x800. When I turn it to 1024x768 bug disappears but this don't > >> appeal to me. > >> No driver is installed but as I understand it is included in distro > >> (suse 11). I tried to stop service splash but there is no result. Boot > >> screen is OK (I use vga=0x318). > >> Also I tried to set up another logon theme, but the default theme > >> (opensuse) is shown whatever theme is selected as like systemsettings > >> ignores me. > >> But when I run systemsettings and press button "Preview" (I do not > >> know exactly how this button is named in English version, maybe > >> "Preview" or "Check Theme" but it allows to preview selected logon > >> theme and look how it will be shown during login) all is OK. > >> The resolution on my desktop id 1280x800 and all works properly. > >> > >> The description of bug in words: image doesn't touch the right sight > >> of the monitor. > >> > >> Does anybody know how to fix it? > >> ========================= > >> Maxim F. suse(a)winwebwiz.net.ru > > > > Don't know how to fix it, but I'm getting it on my system (Panasonic 19" > > monitor, VESA 1280x1024@75HZ. I have the vertical and horizontal setup > > per my Monitor manual. I have the problem on openSUSE 11.1 and 11.2 > > milestone 1. Started after recent update to 11.1 but don't know which > > one. 11.2 has been there all along. > > > > It occurs only on the screen between making the grub selection and the > > KDM login screen. Both the grub screen and kdm screens are normal. > > > > I loaded the openSuSE 11.2 milestone 2 LiveCd_KDE4 yesterday and forgot > > to check this. I will load it later today and see if its fixed. will post > > result. > > > > Have you turned in a bug report? Please post a solution if you find one. > > > > -- > > To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org > > For additional commands, e-mail: opensuse+help(a)opensuse.org > > Finally I understand where bug is. > Firstly I thought that the bug appears because of incorrect settings > in xorg.conf. > To my surprise, after deleting this file, executing sax2 and typing > "startx" the bug disappeared. > I suggested that I was right but after reboot the situation repeated. > Then I thought that something is editing xorg.conf (during login or > before it) and damage proper settings. I compared two files ("good" > and "bad" ) but they were simular. > After it I understood where the bug is. I noticed that correct logon > screen is shown after manually console logging and typing "startx" and > incorrect - during usual login. So the problem is in package kde4-kdm > (kde4 session manager) which damages logon theme. I removed it and the > bug disappeared. > I also tried to keep kde4-kdm but remove theme - this didn't help. > I also installed different versions of it (4.0.4, 4.1.3,4.2.3) which > where in official repo but it also didn't help. > So my opinion is that this package is conflicting with something. > > Maxim > ============================================== Monitor: Micron Electronics [MEI](900Lx [Panasonic} It also occurs in KDE4.2.1 which is installed on my openSUSE 11.1 system, Need to restart my system to check 11.2 milestone2. I'll do that first thing in the morning. kde4-kdm-4.2.1-214.5 kde4-kdm-branding-openSUSE-11.1.1-69.13 They was another problem on boot that was cured by the changing the "branding to upstream". This problem is now back!! i installed the latest nvidia drivers (180.51) instead of (180.44) and it did not fix any of the problems. Interesting thing is YaST --> hardware--> graphics card & monitor uses VESA 1280x1024@75HZ. Sync frequencies are well within my monitor manual shows, display size is correct, now sure of aspect ratio (not called out in manual), diagonal appears close to correct. Test shows it 1280 x1024@91KHZ 85 Hz. Nvidia X Server setting show correct monitor model (Panasonic 1280x1024), resolution 87x92 dots/in., Depth 24, Dimensions: 1280x1024 (374x283 mm). Dimensions are bigger than manual says for preset mode. I know on my none updated old system using this monitor but earlier YaST versions the is a selection for my monitor (MEI) -->(Panasonic) and all works fineusing nv driver. This all started I think when I upgraded to the 180 drivers. It may be a nvidia drive problem for the GeForce boards, mine is a 8400GS. Not sure what this tells us? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] Flood of "Transaction timeout" Messages in /var/log/messages [resend]
by Randall R Schulz 30 May '09

30 May '09

Hi, No one has any experience with or knowledge of this phenomenon? My /var/log/messages is entirely overrun with these messages! -==--==--==--==--==--==--==--==--==--==--==--==--==--==--==- A new message, repeated often and, it seems, interminably, has started appearing in my /var/log/messages file: May 25 06:52:15 208-201-233-232 kernel: i801_smbus 0000:00:1f.3: Transaction timeout Based on the compressed log files, this started happening yesterday. The volume of these messages is such that the log file rolling threshold is now being reached daily, where as in the past it was more like three weeks per compressed log file. Does anyone know what this is? Why it just started appearing? How to fix whatever problem it represents? Google was unhelpful. Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 3