February 2010 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Documentation "creator"
by Ciro Iriarte 05 Feb '10

05 Feb '10

-- Ciro Iriarte http://cyruspy.wordpress.com -- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 3

[opensuse] md RAID5 problem, Sata hard reset I/O error, ICH9R, driver bug in opensuse 11.2?
by Dan Kopparhed 05 Feb '10

05 Feb '10

Hello! Has anyone else seen this problem? Could it be a bug in 11.2? Description: ----------------------------------------------------------------------------------------- I installed 11.2 on my server last weekend, moving from 11.0 (new install). For many years I've been running RAID5 over three partitions of three HDDs using md and ext3, without a hitch. I've also had other RAID constellations running in parallel on the same HDDs and others, also for years without any problems. When installing 11.2 I also changed the partitioning and created a new, otherwise identical RAID5 setup. However, when copying back the data from my backup the array suddenly broke down with 2 of the drives marked faulty and removed! I retried a number of times to try to understand what was happening. I tried both the default and the Xen kernel (both x86_64). I always got the same error. When testing, I saw that first one drive would get an exception and "hard reset" and be removed from the array - always the last raid device (2). This happened after copying several GB of data (usually after around 8 GB). If I then stopped and re-added the "faulty" drive it would get back in sync and I could continue copying another several GB until it got the hard reset again. If I didn't stop to re-add, then the second last raid device (1) would get a hard reset and be removed as faulty - obviously causing the 3-disk raid5 to break down. After trying this for a while I tried instead to create a RAID1 setup using the same 3 partitions and ext4. I've had no problems at all with this setup, filling 90% (about 80 GB) and running for 5 days. Worth mentioning is that I've never had any problems with these physical HDDs which are now around 4-5 years old. I'm also running root and other partitions and a few VMs using LVM and Xen from the very same HDDs. I checked smart incl long self test without finding any errors. I've been running exactly the same hardware for a few years without any problems. When googling a saw a similar problem reported but with nvidia (sata_nv) and some change introduce in the 2.6.26 kernel or around there. I don't know if this issue is related. In this case it's Intel ICH9R. ----------------------------------------------------------------------------------------- Product: OpenSuse 11.2 (final) uname -a: Linux serv 2.6.31.8-0.1-xen #1 SMP 2009-12-15 23:55:40 +0100 x86_64 x86_64 x86_64 GNU/Linux dmesg: ----------------------------------------------------------------------------------------- [ 2.992003] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 2.997047] ata3.00: ATA-7: SAMSUNG SP2004C, VM100-33, max UDMA7 [ 2.997049] ata3.00: 390721968 sectors, multi 0: LBA48 NCQ (depth 31/32) [ 3.002142] ata3.00: configured for UDMA/133 ... [15431.871709] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen [15431.871723] ata3.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 [15431.871724] res 40/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout) [15431.871733] ata3.00: status: { DRDY } [15431.871739] ata3: hard resetting link [15432.355696] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [15432.365819] ata3.00: configured for UDMA/133 [15432.365825] ata3.00: device reported invalid CHS sector 0 [15432.365831] end_request: I/O error, dev sdc, sector 185181205 [15432.365836] md: super_written gets error=-5, uptodate=0 [15432.365840] raid5: Disk failure on sdc5, disabling device. [15432.365841] raid5: Operation continuing on 2 devices. [15432.365853] ata3: EH complete [15432.443698] RAID5 conf printout: [15432.443706] --- rd:3 wd:2 [15432.443711] disk 0, o:1, dev:sda5 [15432.443715] disk 1, o:1, dev:sdb5 [15432.443718] disk 2, o:0, dev:sdc5 [15432.463691] RAID5 conf printout: [15432.463696] --- rd:3 wd:2 [15432.463700] disk 0, o:1, dev:sda5 [15432.463703] disk 1, o:1, dev:sdb5 ----------------------------------------------------------------------------------------- sudo /usr/sbin/smartctl -a /dev/sdc: OK ----------------------------------------------------------------------------------------- Model Family: SAMSUNG SpinPoint P120 series Device Model: SAMSUNG SP2004C Serial Number: S07GJ10Y946521 Firmware Version: VM100-33 User Capacity: 200,049,647,616 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 7 ATA Standard is: ATA/ATAPI-7 T13 1532D revision 4a Local Time is: Fri Jan 29 07:59:58 2010 CET ----------------------------------------------------------------------------------------- lspci -nn: ----------------------------------------------------------------------------------------- 00:1f.2 SATA controller [0106]: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA AHCI Controller [8086:2922] (rev 02) ----------------------------------------------------------------------------------------- Mobo: Gigabyte GA-P35C-DS3R -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 1

[opensuse] printing defaults in KDE4 or is it me?
by eddie 05 Feb '10

05 Feb '10

I cannot find how to set the printing defaults. I typically have more than one printer connected to my computers. Each time I want to print, I have to scroll down and find the printer that I want to use and then change the print options to select dulex printing. I have to do this every time and it is really annoying. I don't actually see any way of saving the settings and the system doesn't seem to remember the last settings. So even if I want to print something just moments later I have to go through the whole routine all over again. Can someone please guide as to how to get the system / KDE4 to remember the settings? I hate to say this but this was not a problem in KDE3 and just adds to my "disappointment" with KDE4. On the other hand, maybe it is just me and I'm overlooking the obvious. Thanks in advance for the help. Eddie -- Let us encourage one another—and all the more as you see the Day approaching. Heb. 12:25 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 1

[opensuse] Dark Red & Gold KDE4 Theme - brighten your desktop for a bit
by David C. Rankin 05 Feb '10

05 Feb '10

Listmates, I never thought red and gold would work on a kde4 desktop, but it looks great. Here is the theme, a background to go with it, and an emerald theme as well. For use, the theme, as do the rest of the gold themes, works best with either Bespin, Nitrogen, Ozone or Oxygen decorations. Uncheck the option to blend the title bar with theme colors. The charcoal titlebar works well into the theme. You can also use Crystal, Modern, Laptop or Glow window decorations and they will look pretty good as well. A screenshot: (140k) http://www.3111skyline.com/dl/ss/kde4/DcrDarkRedGoldKDE4.jpg The color theme: (2k) http://www.3111skyline.com/dl/dt/kde4/color-schemes/DcrDarkRedGoldKDE4.colo… The background: (112k) http://www.3111skyline.com/dl/dt/kde4/color-schemes/wp/heatLightWind1440.jpg The emerald theme: (70k) http://www.3111skyline.com/dl/dt/emerald/dcr-BlackGold.emerald ** Note: you can grab all the current color schemes at: (3.2k) http://www.3111skyline.com/dl/dt/kde4/color-schemes/dcrKDE4Colors-Current.t… Enjoy :p -- 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

1 0

Re: [opensuse] dnssec-keygen problem in opensuse 11.2, including the genDDNSkey script
by Dan Kopparhed 05 Feb '10

05 Feb '10

On 2010-02-04 13:19, Marcus Meissner wrote: > On Thu, Feb 04, 2010 at 11:45:01AM +0100, Dan Kopparhed wrote: > >> On 2010-02-04 11:10, Marcus Meissner wrote: >> >>> On Thu, Feb 04, 2010 at 10:53:20AM +0100, Dan Kopparhed wrote: >>> >>>> Hi, I ran into a problem that I suspect may be a bug in dnssec-keygen. >>>> Can someone confirm this? >>>> >>>> I was trying to generate keys with the genDDNSkey script, but the script >>>> just freezes. So I had a look at the script and discovered that the >>>> problem occurs when calling dnssec-keygen. It sleeps, seemingly stuck >>>> waiting 4-ever (well, I honestly only tried for a few minutes). >>>> Actually, when trying this over and over again, it succeeded once out of >>>> something like 15+ attempts. I changed nothing between trials. >>>> >>>> In opensuse 11.1, latest bind update, running this command immediately >>>> generates private and public keys Ktest.* >>>> /usr/sbin/dnssec-keygen -a HMAC-MD5 -b 512 -r /dev/random -n USER test >>>> >>>> In opensuse 11.2, fully patched, the same command just falls asleep >>>> until killed. >>>> >>>> >>> The sleep might be due to reads from /dev/random, which blocks until enough >>> randomness is there. >>> > filedescriptor 3 is /dev/random, so you dont have sufficient entropy > currently in it (and its waiting until you have). > > either wait a while and/or pound on the keyboard ... or you could fallback > to /dev/urandom Thanks for helping out, Marcus! This "error" was somewhat confusing at first (since there are no messages, just silence). So, in case someone else encounters this issue in the future, I'll elaborate on the explanation a little. First, the difference between /dev/random and /dev/urandom: /dev/random returns high quality noise generated from sources such as "human" input devices like mice and keyboard, etc. It is possible to increase the rate of entropy gathered by e.g. banging the keyboard (if connected to the computer, i.e. not by SSH it seems). /dev/random will block until enough entropy is gathered. /dev/urandom generates as much noise as requested, but with lower quality randomness (pseudo random algorithms). Using /dev/urandom for generating encryption keys makes it theoretically "easy" to find a way to crack the encryption. The genDDNSkey script is using /dev/random by default. Thus, on a server without any human devices connected, as in my case, the available entropy may be too low, causing the script (or rather dnssec-keygen) to apparently freeze. You can see how much entropy is available for /dev/random by reading this: /proc/sys/kernel/random/entropy_avail I hope this is helpful for someone. /Dan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] 11.0 Kernel Call Trace - am I attempting to load 2 vga drivers? How to get rid of the error? PCI Gurus?
by David C. Rankin 05 Feb '10

05 Feb '10

Listmates, My Toshiba 205d laptop has always given the following error on boot that appears to either be a fglrx bug -- or looks like I'm trying to load a second vga driver after fglrx has loaded. The error doesn't effect performance of anything, but since this laptop will die with 11.0 on it, I might as well try and understand the issue a little more. The dmesg output is always the same: <snip> input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:01/device:02/input/input7 [fglrx] Maximum main memory to use for locked dma buffers: 3679 MBytes. [fglrx] vendor: 1002 device: 791f count: 1 ACPI: PCI Interrupt 0000:1d:04.1[B] -> <6>[fglrx] ioport: bar 4, base 0x9000, size: 0x100 ACPI: PCI Interrupt 0000:01:05.0[A] -> GSI 18 (level, low) -> IRQ 18 GSI 21 (level, low) -> IRQ 21 [fglrx] PAT is enabled successfully! [fglrx] module loaded - fglrx 8.53.4 [Sep 8 2008] with 1 minors ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[21] MMIO=[f8406000-f84067ff] Max Packet=[2048] IR/IT contexts=[4/8] ACPI: Video Device [VGA] (multi-head: yes rom: no post: no) proc_dir_entry 'VGA' already registered Pid: 848, comm: modprobe Tainted: P M N 2.6.25.20-0.5-default #1 Call Trace: [<ffffffff8020d696>] dump_trace+0xc4/0x57d [<ffffffff8020db8f>] show_trace+0x40/0x57 [<ffffffff804477bd>] dump_stack+0x72/0x7b [<ffffffff802e342e>] proc_register+0x11b/0x151 [<ffffffff802e35d6>] proc_mkdir_mode+0x3d/0x53 [<ffffffff802e35fd>] proc_mkdir+0x11/0x13 [<ffffffff88361954>] :video:acpi_video_bus_add+0x22a/0xf1e [<ffffffff80370e6d>] acpi_device_probe+0x56/0x108 [<ffffffff803a0486>] driver_probe_device+0xc0/0x16e [<ffffffff803a05a4>] __driver_attach+0x70/0xae [<ffffffff8039fcee>] bus_for_each_dev+0x4f/0x89 [<ffffffff803a02d1>] driver_attach+0x1c/0x1e [<ffffffff8039f5c0>] bus_add_driver+0xb1/0x1e2 [<ffffffff803a0762>] driver_register+0x5e/0xc9 [<ffffffff8037125b>] acpi_bus_register_driver+0x3e/0x40 [<ffffffff881ae03c>] :video:acpi_video_init+0x3c/0x5e [<ffffffff8025ab5d>] sys_init_module+0x1b10/0x1c4d [<ffffffff8020bffa>] system_call_after_swapgs+0x8a/0x8f [<00007f8a001996fa>] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:26/device:27/input/input8 <snip> The biggest problem I have is that I don't know what in the hell the Call Trace above is trying to tell me?? The lspci output for the video card is: 01:05.0 VGA compatible controller: ATI Technologies Inc RS690M [Radeon X1200 Series] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device ff00 Flags: bus master, fast devsel, latency 64, IRQ 18 Memory at f0000000 (64-bit, prefetchable) [size=128M] Memory at f8100000 (64-bit, non-prefetchable) [size=64K] I/O ports at 9000 [size=256] Memory at f8000000 (32-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 2 Capabilities: [80] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable- Kernel driver in use: fglrx_pci Kernel modules: fglrx Which according to the IRQ 18 dmesg output is the correct pci address for the card at 01:05.0. The bizarre part of the dmesg output is the line: "proc_dir_entry 'VGA' already registered" What the heck?? That maybe nothing, but I'm left thinking if 'VGA' is already registered, why in the heck is it trying to register it again?? I've looked at the error before, but since it never seemed to hurt anything, I never looked further into it. That coupled with the fact I don't really recognize what I'm looking at. So what says the brain trust? What does this error look like to any of the hardware gurus? Where is Stefan Dirsch when you need him.... I'm open to any suggestions or any tips of additional tests or output I can provide. Seems Peter isn't the only one with a rouge Tosh box ;P Thanks. -- 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

1 1

[opensuse] Rescue MySQL - Disaster Recovery -
by LLLActive＠GMX.Net 04 Feb '10

04 Feb '10

Hi all, An openSUSE 11.1 installation with MySQL hosting a Wikipedia was lost due to a hard disk failure. Only the OS seems to have been effected. I need to recover the MySQL database to a new machine, using the old HD's data, which I managed to recover to a new disk. Has anyone done this before? Any suggestions to some material for such disaster recovery will be very welcome, or can someone help in this list? TIA Al -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 3

[opensuse] KDE 4 strikes again
by Curtis Rey 04 Feb '10

04 Feb '10

Hello list. I posted this earlier and did what was suggested to no avail. If I issue the command /usr/bin/firefox in any desktop other than KDE 4.4 I get a fully functional browser. However, the minute I do this in a KDE 4.4 evironment I get the following. #/usr/bin/firefox: line 128: 5965 Segmentation fault $MOZ_PROGRAM "$@" So then I have a look at /usr/bin/firefox and find the following: #cat firefox ---snip--- if [ $moz_debug -eq 1 ]; then tmpfile=`mktemp /tmp/mozargs.XXXXXX` || { echo "Cannot create temporary file" >&2; exit 1; } trap " [ -f \"$tmpfile\" ] && /bin/rm -f -- \"$tmpfile\"" 0 1 2 3 13 15 echo -e "set args ${1+"$@"}\nrun" > $tmpfile echo "$moz_debugger $MOZ_PROGRAM -x $tmpfile" $moz_debugger "$MOZ_PROGRAM" -x $tmpfile else $MOZ_PROGRAM "$@" fi exitcode=$? exit $exitcode Seems to revolve around the debug protocols/code in the program or the incompatibility with KDE 4.4 debug/environ.... I did earlier try to install themozilla-xulrunner192-buildsymbols-1.9.2.0-2.1.i586 mozilla-xulrunner191-gnomevfs-1.9.1.7-1.1.1.i586 mozilla-xulrunner191-devel-1.9.1.7-1.1.1.i586 mozilla-xulrunner192-devel-1.9.2.0-2.1.i586 mozilla-xulrunner190-gnomevfs-1.9.0.17-1.3.i586 mozilla-xulrunner191-translations-common-1.9.1.7-1.1.1.i586 mozilla-xulrunner192-1.9.2.0-2.1.i586 mozilla-xulrunner191-kde4-0.6-0.1.1.i586 mozilla-xulrunner192-translations-common-1.9.2.0-2.1.i586 mozilla-xulrunner190-1.9.0.17-1.3.i586 mozilla-xulrunner191-1.9.1.7-1.1.1.i586 mozilla-xulrunner191-translations-other-1.9.1.7-1.1.1.i586 mozilla-xulrunner192-gnome-1.9.2.0-2.1.i586 mozilla-xulrunner190-translations-1.9.0.17-1.3.i586 lastest XULrunner due to suspicions that it was the culprit.... I have multiple versions install (which seem to make no difference because the browser runs fine in every other desktop). The following for reference: #rpm -qa | grep firefox mhtml-firefox-0.5-2.3.i586 #rpm -qa | grep Firefox MozillaFirefox-branding-upstream-3.6.0-1.2.i586 MozillaFirefox-3.5.7-1.1.1.i586 MozillaFirefox-theme-oxygen-1.4.92-10.1.noarch #rpm -qa | grep xulrunner mozilla-xulrunner192-buildsymbols-1.9.2.0-2.1.i586 mozilla-xulrunner191-gnomevfs-1.9.1.7-1.1.1.i586 mozilla-xulrunner191-devel-1.9.1.7-1.1.1.i586 mozilla-xulrunner192-devel-1.9.2.0-2.1.i586 mozilla-xulrunner190-gnomevfs-1.9.0.17-1.3.i586 mozilla-xulrunner191-translations-common-1.9.1.7-1.1.1.i586 mozilla-xulrunner192-1.9.2.0-2.1.i586 mozilla-xulrunner191-kde4-0.6-0.1.1.i586 mozilla-xulrunner192-translations-common-1.9.2.0-2.1.i586 mozilla-xulrunner190-1.9.0.17-1.3.i586 mozilla-xulrunner191-1.9.1.7-1.1.1.i586 mozilla-xulrunner191-translations-other-1.9.1.7-1.1.1.i586 mozilla-xulrunner192-gnome-1.9.2.0-2.1.i586 mozilla-xulrunner190-translations-1.9.0.17-1.3.i586 Again, it only fails in KDE 4.4. and it seems to make no difference if its FF 3.5, 3.6, 3.7. I realize their may be a conflict between MozillaFirefox-branding- upstream-3.6.0-1.2 and MozillaFirefox-3.5.7-1.1.1 - YaST suggested this and did not complain during installation. Any help will be greatly appreciated. TIA, Curtis. -- BEWARE! Spammers will be shot, survivors will be shot again! Those throwing objects at the alligators will be asked to retrieve them! -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

3 3

[opensuse] Skype problem?
by Jim Hatridge 04 Feb '10

04 Feb '10

Hi all! I just had a odd thing happen. I let Skype run all the time my system is on. About an hour ago, out of the blue a girl in Canada started a chat with me. I know that it was a scammer, but I like to play with them. So i chated back. Anyway she asked me to add her to my contact list. I did and she suddenly disconnected. My question is: is there any thing that they can do to my system by being on my Skype contact list? Thanks, JIM in Germany -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 1

[opensuse] directory time stamps on mounted DC
by Istvan Gabor 04 Feb '10

04 Feb '10

Hello: I have another question related to mounting CDs in linux. I have a CD that I burned years ago. If I mount it in openSUSE 11.2 the directory dates on the CD are all set to '1970-01-01 01:00'. File dates look correct. But the directory dates look correct in MS Windows. Why is this difference? How could I get the correct directory dates in linux? (If I make an iso image from the CD using k3b, the directory dates are also correct in the image.) Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

4 4