January 2011 - openSUSE Users - openSUSE Mailing Lists

Re: [opensuse] Filling up of messages and warn
by Duaine Hechler 10 Jan '11

10 Jan '11

On 01/06/2011 11:09 AM, Obamaramalamadingdong wrote: > Duaine Hechler wrote: >> Running 11.3 >> >> Don't know when it started, probably within the last three months, also >> no hardware changes have been done for about a year. >> >> Every few days, /var/log/messages and /var/log/warn keep growing to take >> up my root partition - going from 26% to 100%. >> > > This is one reason why I keep /var on it's own partition... > > The other reason is, /var has lots of writing activity > (for example /var/spool/mail and /var/spool/print, which > I do NOT want (for reasons of possible filesystem corruption) > on the same filesystem (root partition) as the OS. > >> How do I stop this ? >> > > 1. Did you READ the messages? Too many people these days > think that everything is supposed to be nothing more than > a visual impression. But that's not the case here -- > which is why the log files are filling up with messages, > not "a giant blob which keeps growing bigger and bigger" > > 1b... After you READ THE MESSAGES, determine what the > problem is, and solve it. It could be anything from > smartd telling you that a disk is going to fail soon > to millions of attempted remote logins. If you don't > READ THE MESSAGES, you won't know what it is. > > 2. To avoid the root partition filling up (something > which seriously interferes with software updates), > put /var on its own partion. > > The logs are filling up with these messages: And I do know that cx88 is for my TV tuner card > Jan 6 16:15:55 localhost kernel: [135144.859923] cx88[0]: irq vid > [0xffffffff] y_risci1* u_risci1* v_risci1* vbi_risc1* > y_risci2* u_risci2* v_risci2* vbi_risc2* y_oflow* u_oflow* v_oflow* > vbi_oflow* y_sync* u_sync* v_sync* vbi_sync* opc_er > r* par_err* rip_err* pci_abort* 20* 21* 22* 23* 24* 25* 26* 27* 28* > 29* 30* 31* > Jan 6 16:15:55 localhost kernel: [135144.859965] cx88[0]/0: video > risc op code error > Jan 6 16:15:55 localhost kernel: [135144.859969] cx88[0]: video y / > packed - dma channel status dump > Jan 6 16:15:55 localhost kernel: [135144.859971] cx88[0]: cmds: > initial risc: 0xffffffff > Jan 6 16:15:55 localhost kernel: [135144.859974] cx88[0]: cmds: cdt > base : 0xffffffff > Jan 6 16:15:55 localhost kernel: [135144.859976] cx88[0]: cmds: cdt > size : 0xffffffff > Jan 6 16:15:55 localhost kernel: [135144.859978] cx88[0]: cmds: iq > base : 0xffffffff > Jan 6 16:15:55 localhost kernel: [135144.859981] cx88[0]: cmds: iq > size : 0xffffffff > Jan 6 16:15:55 localhost kernel: [135144.859983] cx88[0]: cmds: > risc pc : 0xffffffff > Jan 6 16:15:55 localhost kernel: [135144.859986] cx88[0]: cmds: iq > wr ptr : 0xffffffff > Jan 6 16:15:55 localhost kernel: [135144.859988] cx88[0]: cmds: iq > rd ptr : 0xffffffff > Jan 6 16:15:55 localhost kernel: [135144.859991] cx88[0]: cmds: cdt > current : 0xffffffff > Jan 6 16:15:55 localhost kernel: [135144.859993] cx88[0]: cmds: pci > target : 0xffffffff > Jan 6 16:15:55 localhost kernel: [135144.859995] cx88[0]: cmds: > line / byte : 0xffffffff > Jan 6 16:15:55 localhost kernel: [135144.859998] cx88[0]: risc0: > 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 1 > 9 18 cnt1 cnt0 resync 14 13 12 count=4095 ] > Jan 6 16:15:55 localhost kernel: [135144.860009] cx88[0]: risc1: > 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 1 > 9 18 cnt1 cnt0 resync 14 13 12 count=4095 ] > Jan 6 16:15:55 localhost kernel: [135144.860024] cx88[0]: risc2: > 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 1 > 9 18 cnt1 cnt0 resync 14 13 12 count=4095 ] > Jan 6 16:15:55 localhost kernel: [135144.860038] cx88[0]: risc3: > 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 1 > 9 18 cnt1 cnt0 resync 14 13 12 count=4095 ] > Jan 6 16:15:55 localhost kernel: [135144.860052] cx88[0]: iq 0: > 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 > 18 cnt1 cnt0 resync 14 13 12 count=4095 ] > Jan 6 16:15:55 localhost kernel: [135144.860066] cx88[0]: iq 1: > 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 > 18 cnt1 cnt0 resync 14 13 12 count=4095 ] > Jan 6 16:15:55 localhost kernel: [135144.860080] cx88[0]: iq 2: > 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 > 18 cnt1 cnt0 resync 14 13 12 count=4095 ] > Jan 6 16:15:55 localhost kernel: [135144.860094] cx88[0]: iq 3: > 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 > 18 cnt1 cnt0 resync 14 13 12 count=4095 ] > Jan 6 16:15:55 localhost kernel: [135144.860108] cx88[0]: iq 4: > 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 > 18 cnt1 cnt0 resync 14 13 12 count=4095 ] > Jan 6 16:15:55 localhost kernel: [135144.860121] cx88[0]: iq 5: > 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 > 18 cnt1 cnt0 resync 14 13 12 count=4095 ] > Jan 6 16:15:55 localhost kernel: [135144.860133] cx88[0]: iq 6: > 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 > 18 cnt1 cnt0 resync 14 13 12 count=4095 ] > Jan 6 16:15:55 localhost kernel: [135144.860142] cx88[0]: iq 7: > 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 > 18 cnt1 cnt0 resync 14 13 12 count=4095 ] > Jan 6 16:15:55 localhost kernel: [135144.860151] cx88[0]: iq 8: > 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 > 18 cnt1 cnt0 resync 14 13 12 count=4095 ] > Jan 6 16:15:55 localhost kernel: [135144.860160] cx88[0]: iq 9: > 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 > 18 cnt1 cnt0 resync 14 13 12 count=4095 ] > Jan 6 16:15:55 localhost kernel: [135144.860169] cx88[0]: iq a: > 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 > 18 cnt1 cnt0 resync 14 13 12 count=4095 ] > Jan 6 16:15:55 localhost kernel: [135144.860178] cx88[0]: iq b: > 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 > 18 cnt1 cnt0 resync 14 13 12 count=4095 ] > Jan 6 16:15:55 localhost kernel: [135144.860187] cx88[0]: iq c: > 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 > 18 cnt1 cnt0 resync 14 13 12 count=4095 ] > Jan 6 16:15:55 localhost kernel: [135144.860196] cx88[0]: iq d: > 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 > 18 cnt1 cnt0 resync 14 13 12 count=4095 ] > Jan 6 16:15:55 localhost kernel: [135144.860207] cx88[0]: iq e: > 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 > 18 cnt1 cnt0 resync 14 13 12 count=4095 ] > Jan 6 16:15:55 localhost kernel: [135144.860218] cx88[0]: iq f: > 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 > 18 cnt1 cnt0 resync 14 13 12 count=4095 ] > Jan 6 16:15:55 localhost kernel: [135144.860227] cx88[0]: fifo: > 0x00180c00 -> 0x183400 > Jan 6 16:15:55 localhost kernel: [135144.860228] cx88[0]: ctrl: > 0x00180400 -> 0x180460 > Jan 6 16:15:55 localhost kernel: [135144.860231] cx88[0]: ptr1_reg: > 0xffffffff > Jan 6 16:15:55 localhost kernel: [135144.860233] cx88[0]: ptr2_reg: > 0xffffffff > Jan 6 16:15:55 localhost kernel: [135144.860235] cx88[0]: cnt1_reg: > 0xffffffff > Jan 6 16:15:55 localhost kernel: [135144.860237] cx88[0]: cnt2_reg: > 0xffffffff -- 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 - 10 years -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

3 3

[opensuse] Pidgin horked by libgstreamer-0.10.so.0
by John Andersen 10 Jan '11

10 Jan '11

Running opensuse 11.3 with KDE 4.5.95 (4.6 RC2). Latest Pidgin seems to die upon invocation. Strace ends with 10/usr/bin/pidgin: symbol lookup error: /usr/lib64/libgstreamer-0.10.so.0: undefined symbol: g_error_get_type libgstreamer-0.10.so.0 that I have was from pacman Version 0.10.30-99.pm.1003.7-x86_64 The only way I could get it to work is to downgrade to version 0.10.29-1.7-x86_64 From Opensuse 11.3-0ss That allowed Pidgin to run, without any obvious side effects, (so far). I mention this mostly for the Google Spiders and anyone else having problems with Pidgin. -- A computer without Microsoft is like a chocolate cake without mustard. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] virtualbox: 11.3 host / 11.1 guest - won't install
by Greg Freemyer 10 Jan '11

10 Jan '11

All, This is my first effort to run VirtualBox. I seem to have the basics going. I'm trying to do a network install of 11.1 for now. I downloaded the net install ISO. When I start the new VM it asks for the location of the ISO and boots the CD. I select that install option on the screen, and it says kernel loading. After it loads, it gives me a warning that I don't have 32-bit color selected on my desktop. When I say ok, it goes to a black screen and stays there (for at least several minutes.) Am I doing something wrong. (FYI: I'm running the 2.6.36 kernel an vboxdrv module currently. I'm going backdown to the normal kernel and see if that helps.) Thanks Greg -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

5 11

[opensuse] forum grief
by Dave Howorth 10 Jan '11

10 Jan '11

Is there some problem with the forums? The formatting seems broken this morning, and I can't login. I just get continually returned to the login page. Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

4 7

[opensuse] (KDE Devs) kde-4.5.4 loads kde3 kicker and background (even with ~/.kde & ~/.kde4 removed)
by David C. Rankin 10 Jan '11

10 Jan '11

Guys, This is primarily for the kde devs on the list. For some reason, kde4-4.5.4 is pulling in the kde3 defaults and loading the kde3 kicker, dialogs and wallpaper even if your delete both ~/.kde and ~/.kde4 and launch kde4 (with kde4 kdm as the display manager). I have filed a bug at kde.org: See: https://bugs.kde.org/show_bug.cgi?id=262444 The bug report basically states: I launched kde4 and my kde3 kicker and the kde4 plasma panel are both present: [26k] http://www.3111skyline.com/dl/arch/bugs/kde4/k3+k4_panels-640.jpeg So I moved ~/.kde4 figuring it was the problem and launched kde4 again. Still it pulled in my kde3 kicker and background. Huh? So I moved both ~/.kde and ~/.kde4 to make sure there was nothing kde (3 or 4) related in my home directory and I launched kde4 again. To my surprise, kde4 loaded it's plasma panel and then proceeded to load the default kdemod3 kicker and kdemod3 background?? See: [24k] http://www.3111skyline.com/dl/arch/bugs/kde4/k3+k4_panels-new-640.jpg Obviously something is very wrong here. kde4 should not be loading the kdemod3 kicker or background. Looking at the newly created ~/.kde4/share/config files, the kickerrc file contains the following: 15:42 providence:~> cat .kde4/share/config/kickerrc [$Version] update_info=kickerrc.upd:kde_3_1_sizeChanges,kickerrc.upd:kde_3_4_reverseLayout,kickerrc.upd:kde_3_5_kconfigXTize Double-huh? Why would kde-4.5.4 create a kickerrc containing kde3 entries? Reproducible: Always Steps to Reproduce: Have both kde3 and kde4 installed. (using kde4 kdm as display manager) Clean home directory of both ~/.kde and ~/.kde4 Launch kde4 to force defaults to be applied Actual Results: kde3 kicker and kde4 plasma panel are both loaded. Default kde3 wallpaper is used for the kde4 background. Context menus and decorations appear to be kde3 default. Plasma panel is properly styled with kde4 theme. Expected Results: Just a default kde4 panel and theme. So kde devs. I'm really trying to use kde4, I just keep running into issues that cost hours to research, posts to multiple mailing lists, and bug reports. Here, it might be worth looking at why kde4 is even looking for kde3 settings and make sure it doesn't load both sets of configs. This is a kde4 defaults issue (I think), because after removing both ~/.kde and ~/.kde4, I did not expect kde4 to even look for anything kde3 related when it created it new default config on next launch.... -- 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 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

3 4

[opensuse] Kodak Camera not "automounted"
by Robert Schweikert 09 Jan '11

09 Jan '11

Hi, When connecting a "new for X-mas" Kodak camera, the USB conection as such is recognized by the system but the camera is not mounted, neither does GNOME offer to start the default camera application. Here is the info from the kernel log: usb 6-1: new full speed USB device using uhci_hcd and address 7 usb 6-1: New USB device found, idVendor=040a, idProduct=060b usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 6-1: Product: KODAK EASYSHARE C183 Digital Camera usb 6-1: Manufacturer: Eastman Kodak Company usb 6-1: SerialNumber: C183 100523977 This is on openSUSE 11.3 32 bit. Anything I can do to get his camera to work? Thanks, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU Software Engineer Consultant LINUX rschweikert(a)novell.com 781-464-8147 Novell Making IT Work As One -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 3

[opensuse] openSUSE Weekly News 157 is out!
by Sascha 'saigkill' Manns 08 Jan '11

08 Jan '11

We are pleased to announce: Issue 157 of openSUSE Weekly News is out! [0] For a list of available translations see this page: http://en.opensuse.org/openSUSE:Weekly_news_translations [0] http://news.opensuse.org/?p=6512 (in HTML) [0] http://en.opensuse.org/File:OWN-157.pdf (in PDF) -- Sincerely yours Sascha Manns open-slx.com openSUSE Community & Support Agent openSUSE Marketing Team Blog: http://saigkill.wordpress.com -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 1

[opensuse] Finding unused packages
by John Andersen 08 Jan '11

08 Jan '11

I've noticed some libraries and stuff laying around in my machine (opensuse 11.3) that are apparently not used by anything (selecting them for removal shows no dependency alerts). Some of these are old packages, as this machine was upgraded from 10.something.) Is there any tool to find this stuff? -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

4 4

Re: [opensuse] IPv6 in Firefox: does it work? [Was: What is the proper entry for /etc/hosts 127.0.0.1?]
by James Knott 08 Jan '11

08 Jan '11

Hans Witvliet wrote: > If you want, you still are allowed to subnet, allthough it is not > advised. > You'd better use other than MAC addresses for your IPv6 address then. Otherwise, it's possible you may wind up with two devices having the same IP address. As I mentioned in another note, the last 64 bits of the MAC based IPv6 address is the 1st 24 bits of the MAC, then FE, followed by the remaining 24 bits of the MAC. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] IPv6 in Firefox: does it work?
by Per Jessen 08 Jan '11

08 Jan '11

Carlos E. R. wrote: > On Wednesday, 2011-01-05 at 15:22 +0100, Per Jessen wrote: > >> Yes, the link-local address can't be used like that - TBH, I don't >> know why. >> For ping6, you need to specify the interface: >> >> ping6 -I ethX FE80::21E:BFF:FE08:4CCB > > Ah, yes, I remember that now. As I don't use v6 and I can't understand > the reason of having to specify the interface, so I always forget that > detail. I've discovered the reason - the link local address may be assigned to multiple interfaces, so to use it, you need to specify which interface. -- Per Jessen, Zürich (3.0°C) -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 3