December 2005 - openSUSE Users - openSUSE Mailing Lists

problem with playing wmv in suse 10
by Istvan Gabor 28 Dec '05

28 Dec '05

Hello all: I have suse 10.0 i386 with multimedia packages from packman: MPlayer-1.0pre7-pm.3 mplayerplug-in-3.17-0.pm.0 w32codec-all-20050412-0.pm.0 There are a few wmv files that mplayer can't play correctly. An example is here: http://totalcar.index.hu/ujauto/link/tv.php3?tvurl=http://dl. totalcar.hu/tc25_02.wmv Playing this file is not continous but jumping and jumping... I tried to play this file in windows and it plays well there. How could I fix this problem? Thanks, IG _____________________________________________________________________________ Töltse az év végét sztárokkal! Ingyen filmek egészen Újévig a T-Online Tékában! http://www.t-online.hu

2 2

Re: [SLE] XP strange behaviour after SUSE install
by lerninlinux＠comcast.net 28 Dec '05

28 Dec '05

-------------- Original message ---------------------- From: "ferdybassi(a)tin.it" <ferdybassi(a)tin.it> > Hi all. > I have a toshiba laptop with a 60 GB HD which I have > partitioned as follows: > > - hda1 14 GB NTFS Windows XP > - hda5 16 GB NTFS > Windows XP Data > - hda6 4 GB FAT32 to share files between WinXP and SUSE > - hda7 400 MB Reiser /boot > - hda8 16 GB Reiser / > - hda9 10 GB Reiser > /home > > I first installed Windows XP on its primary partition, then > installed SUSE 10 and set up Grub to boot both. > Now SUSE 10 can boot > w/out any problem, but when I boot Windows XP I get this strange > behaviour: it boots, it lets me CTRL+ALT+DEL, it lets me log in with my > username/password... then it loads my desktop settings and suddenly > freeze. I got "busy mouse pointer" and I can't do anything. By entering > Task manager it seems that the problem is caused by AVG Free antivirus > (it freezes and I can't stop it) or by ConfigFree, a Toshiba tool to > easily switch between different LANs. I can't even CTRL+ALT+DEL again > to reboot: I just have to press shutdown button... > Never happened with > SUSE 9.2... > Both Windows XP and SUSE 10 are fresh installations. I just > updated them, without installing any other software, except AVG > antivirus > > My hypothesis: > - AVG Free detects some change into the > reisers partitions or into the MBR and it just goes crazy > - SUSE 10 has > some bugs into partition handling > - Windows XP SP2 doesn't like that > someone manages partitions after its installation > > Any hints? > > TIA, > Ferdinando > > -- > Check the headers for your unsubscription address > For additional commands send e-mail to suse-linux-e-help(a)suse.com > Also check the archives at http://lists.suse.com > Please read the FAQs: suse-linux-e-faq(a)suse.com > > When did you install AVG? If you installed it right after Windows, but before Suse, you answered your own question.... "> - AVG Free detects some change into the > reisers partitions or into the MBR and it just goes crazy" Grub changes the master boot record. My father had a problem with AVG on a system a couple of years ago, he used Ranish on the boot partition, and AVG didn't like it, it saw it as a virus.

1 0

serving Cups
by Susemail 28 Dec '05

28 Dec '05

I have a Cups Server and client on my Lan. I setup the client in Yast to use the Cups Server to print with. In the cupsd.conf file on the server I wrote: BrowseAddress @IF(eth0) and restarted the Cups Server. When I test IPP access on the client in the Yast printer module the server address is found but I get an error message: 'There was a problem. Cannot connect to the printer server' Any ideas what the problem is? Or how to find out what the problem is? Thanks, Jerome

2 1

Secure Digital card - SuSE 10.0
by Carlos Romero-Martin 28 Dec '05

28 Dec '05

Hello, I has a Toshiba Satellite with SD interface and I probe to use it with SuSE 10.0 How I can made to access The result of my lspci is : 00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03) 00:01.0 PCI bridge: Intel Corporation Mobile 915GM/PM Express PCI Express Root Port (rev 03) 00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03) 00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03) 00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03) 00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03) 00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d3) 00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 03) 00:1e.3 Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Modem Controller (rev 03) 00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge (rev 03) 00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA Controller (rev 03) 00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 03) 01:00.0 VGA compatible controller: ATI Technologies Inc: Unknown device 5462 06:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 06:02.0 Network controller: Intel Corporation PRO/Wireless 2200BG (rev 05) 06:04.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller 06:04.2 FireWire (IEEE 1394): Texas Instruments OHCI Compliant IEEE 1394 Host Controller 06:04.3 Unknown mass storage controller: Texas Instruments PCIxx21 Integrated FlashMedia Controller 06:04.4 Class 0805: Texas Instruments PCI6411, PCI6421, PCI6611, PCI6621, PCI7411, PCI7421, PCI7611, PCI7621 Secure Digital (SD) Controller Thanks for you help -- Carlos Romero-Martin

1 0

Can't make Software RAID0 volume greater than 4TB
by Patrick Freeman 28 Dec '05

28 Dec '05

The following oops occurred when trying to join two large hardware arrays into a single raid0 of over 7TB (I included a little more than the Oops). I was able to reproduce this error with any volume greater than 4TB. This is a dual Xeon system (x86_64). Any ideas? Nov 29 18:11:31 dev kernel: md: bind<sda> Nov 29 18:11:31 dev kernel: md: bind<sdb> Nov 29 18:11:31 dev kernel: raid0: module not supported by Novell, setting U taint flag. Nov 29 18:11:31 dev kernel: md: raid0 personality registered as nr 2 Nov 29 18:11:31 dev kernel: md2: setting max_sectors to 512, segment boundary to 131071 Nov 29 18:11:31 dev kernel: raid0: looking at sdb Nov 29 18:11:31 dev kernel: raid0: comparing sdb(4296872192) with sdb(4296872192) Nov 29 18:11:31 dev kernel: raid0: END Nov 29 18:11:31 dev kernel: raid0: ==> UNIQUE Nov 29 18:11:31 dev kernel: raid0: 1 zones Nov 29 18:11:31 dev kernel: raid0: looking at sda Nov 29 18:11:31 dev kernel: raid0: comparing sda(4296872192) with sdb(4296872192) Nov 29 18:11:31 dev kernel: raid0: EQUAL Nov 29 18:11:31 dev kernel: raid0: FINAL 1 zones Nov 29 18:11:31 dev kernel: raid0: done. Nov 29 18:11:32 dev kernel: raid0 : md_size is 8593744384 blocks. Nov 29 18:11:32 dev kernel: raid0 : conf->hash_spacing is 8593744384 blocks. Nov 29 18:11:32 dev hald[5857]: Timed out waiting for hotplug event 940. Rebasing to 941 Nov 29 18:11:33 dev kernel: raid0 : nb_zone is 2256. Nov 29 18:11:34 dev kernel: raid0 : Allocating 18048 bytes for hash. Nov 29 18:11:35 dev kernel: Unable to handle kernel paging request at 000000000001d508 RIP: Nov 29 18:11:37 dev kernel: <ffffffff88433c0b>{:raid0:raid0_make_request+459} Nov 29 18:11:39 dev kernel: PGD 212e0b067 PUD 212e0a067 PMD 0 Nov 29 18:11:39 dev kernel: Oops: 0000 [1] SMP Nov 29 18:11:40 dev kernel: CPU 0 Nov 29 18:11:42 dev kernel: Modules linked in: raid0 ib_ipoib ib_sa_client ib_client_query ib_poll ib_useraccess ib_tavor ib_mad ib_core ib_services mod_rhh mst_pciconf mst_pci mod_vip ipv6 evdev joydev mlxsys st sr_mod edd sg sk98lin e1000 hw_random ehci_hcd uhci_hcd i2c_i801 i2c_core usbcore parport_pc lp parport video1394 ohci1394 raw1394 ieee1394 capability dm_mod reiserfs xfs exportfs ide_cd cdrom ide_disk piix ide_core raid1 arcmsr sd_mod scsi_mod Nov 29 18:11:43 dev kernel: Pid: 7687, comm: udev_volume_id Tainted: GF U 2.6.11.4-21.9-smp Nov 29 18:11:47 dev kernel: RIP: 0010:[<ffffffff88433c0b>] <ffffffff88433c0b>{:raid0:raid0_make_request+459} Nov 29 18:11:49 dev kernel: RSP: 0018:ffff810212e1d948 EFLAGS: 00010286 Nov 29 18:11:50 dev kernel: RAX: 0000000000000000 RBX: ffff81021cdc5780 RCX: 0000000000000008 Nov 29 18:11:52 dev kernel: RDX: 0000000000003aa1 RSI: 0000000000000008 RDI: ffff81021e5d6e10 Nov 29 18:11:53 dev kernel: RBP: 0000000000000100 R08: 0000000002003a21 R09: ffff8102131b7000 Nov 29 18:11:55 dev kernel: R10: 00000000000001ff R11: 000000000003ffff R12: ffff8102132532c0 Nov 29 18:11:55 dev kernel: R13: ffff81021f6d8040 R14: 0000000000001000 R15: 0000000000000001 Nov 29 18:11:55 dev kernel: FS: 0000000000000000(0000) GS:ffffffff804e3980(0000) knlGS:0000000000000000 Nov 29 18:11:57 dev kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b Nov 29 18:11:57 dev kernel: CR2: 000000000001d508 CR3: 00000002133ad000 CR4: 00000000000006e0 Nov 29 18:11:57 dev kernel: Process udev_volume_id (pid: 7687, threadinfo ffff810212e1c000, task ffff81021cceb070) Nov 29 18:11:58 dev kernel: Stack: 0000000000000000 ffff81021cdc5780 ffff81021f6d8040 ffff810212e1d9a8 Nov 29 18:11:58 dev kernel: ffff81021cdc5780 ffffffff80295281 0000000000000000 ffff81021cceb070 Nov 29 18:11:59 dev kernel: ffffffff8014d720 ffff810212e1d9c0 Nov 29 18:11:59 dev kernel: Call Trace:<ffffffff80295281>{generic_make_request+545} <ffffffff8014d720>{autoremove_wake_function+0} Nov 29 18:11:59 dev kernel: <ffffffff8015d384>{mempool_alloc+164} <ffffffff8014d720>{autoremove_wake_function+0} Nov 29 18:11:59 dev kernel: <ffffffff8015fa31>{buffered_rmqueue+529} <ffffffff8014d720>{autoremove_wake_function+0} Nov 29 18:12:00 dev kernel: <ffffffff8029537d>{submit_bio+221} <ffffffff80183c27>{bio_alloc+359} Nov 29 18:12:01 dev kernel: <ffffffff8017fe6b>{submit_bh+283} <ffffffff80182cba>{block_read_full_page+602} Nov 29 18:12:02 dev kernel: <ffffffff80185700>{blkdev_get_block+0} <ffffffff80161650>{__do_page_cache_readahead+480} Nov 29 18:12:03 dev kernel: <ffffffff802234ae>{prio_tree_insert+494} <ffffffff801617b6>{blockable_page_cache_readahead+22} Nov 29 18:12:06 dev kernel: <ffffffff801619da>{page_cache_readahead+490} <ffffffff8015b3c2>{do_generic_mapping_read+354} Nov 29 18:12:10 dev kernel: <ffffffff8015a320>{file_read_actor+0} <ffffffff8015bfe7>{__generic_file_aio_read+423} Nov 29 18:12:12 dev kernel: <ffffffff8015c1ab>{generic_file_read+187} <ffffffff80120a22>{do_page_fault+1234} Nov 29 18:12:16 dev kernel: <ffffffff8014d720>{autoremove_wake_function+0} <ffffffff80224711>{__up_write+49} Nov 29 18:12:17 dev kernel: <ffffffff8017ebd4>{vfs_read+244} <ffffffff8017ed43>{sys_read+83} Nov 29 18:12:18 dev kernel: <ffffffff8010e9de>{system_call+126} Nov 29 18:12:20 dev kernel: Nov 29 18:12:20 dev kernel: Code: 48 8b 14 d0 8b 03 44 21 d0 4a 8d 0c 48 48 8b 42 28 48 89 43 Nov 29 18:12:21 dev kernel: RIP <ffffffff88433c0b>{:raid0:raid0_make_request+459} RSP <ffff810212e1d948> Nov 29 18:12:21 dev kernel: CR2: 000000000001d508 >>RIP; ffffffff88433c0b <_end+7f0ec0b/7f0db000> <===== Trace; ffffffff80295281 <generic_make_request+221/240> Trace; ffffffff8015d384 <mempool_alloc+a4/190> Trace; ffffffff8015fa31 <buffered_rmqueue+211/310> Trace; ffffffff8029537d <submit_bio+dd/100> Trace; ffffffff8017fe6b <submit_bh+11b/150> Trace; ffffffff80185700 <blkdev_get_block+0/70> Trace; ffffffff802234ae <prio_tree_insert+1ee/2a0> Trace; ffffffff801619da <page_cache_readahead+1ea/2f0> Trace; ffffffff8015a320 <file_read_actor+0/150> Trace; ffffffff8015c1ab <generic_file_read+bb/e0> Trace; ffffffff8014d720 <autoremove_wake_function+0/30> Trace; ffffffff8017ebd4 <vfs_read+f4/170> Trace; ffffffff8010e9de <system_call+7e/83> Code; ffffffff88433c0b <_end+7f0ec0b/7f0db000> 0000000000000000 <_RIP>: Code; ffffffff88433c0b <_end+7f0ec0b/7f0db000> <===== 0: 48 8b 14 d0 mov (%rax,%rdx,8),%rdx <===== Code; ffffffff88433c0f <_end+7f0ec0f/7f0db000> 4: 8b 03 mov (%rbx),%eax Code; ffffffff88433c11 <_end+7f0ec11/7f0db000> 6: 44 21 d0 and %r10d,%eax Code; ffffffff88433c14 <_end+7f0ec14/7f0db000> 9: 4a 8d 0c 48 lea (%rax,%r9,2),%rcx Code; ffffffff88433c18 <_end+7f0ec18/7f0db000> d: 48 8b 42 28 mov 0x28(%rdx),%rax Code; ffffffff88433c1c <_end+7f0ec1c/7f0db000> 11: 48 89 43 00 mov %rax,0x0(%rbx) Thanks, Patrick

2 1

creating a new daemon
by Greg Freemyer 28 Dec '05

28 Dec '05

All, What is the SUSE way to invoke/create a daemon? In particular I want to have WEBrick from Ruby on Rails running on my server anytime the server is in init 3 or 5. I can manually invoke by "/srv/www/vhosts/my_server/scripts/server --daemon --port 3030" I know I can manually add appropriate entries in /etc/rc.d but I believe my changes will get destroyed the next time I upgrade the server. Thanks Greg -- Greg Freemyer The Norcross Group Forensics for the 21st Century

3 2

RE: [SLE] Problems with initrd after mkinitrd
by Patrick Freeman 28 Dec '05

28 Dec '05

Carl, Thanks again -- I just wanted to fill you in on the information that was missing, but have not yet finished my experiment. Thanks, again -- see below. > -----Original Message----- <snip> > I have to acknowledge this problem exist(s/ed) on older hardware, but it > is > also important to point out that modern drives and BIOSes set to use LBA > (which Grub and Linux 'speak') cleanly eliminates this specific > limitation. > AIUI, under LBA, the current "interesting" addressing barrier is 137GB. (BTW, thanks for the input, Terry) Well, interestingly, all of the machines were booting at cylinder 2082 prior to the mkinitrd problem -- because I wasn't concerned with it (see the board info below). My previous practice had been to use a 100 MB /boot partition, but I was doing much different things then -- and on older equipment. > > And Patrick, > > I've studied the entire thread again, top to bottom, to see if we have > overlooked something, and I'll share these thoughts: > > 1. We don't know the manufacturer or age of the machines we're > discussing... > no mainboard or CPU models/numbers etc... the only 'clue' is that you've > seen > this problem "to some degree" under SuSE 9.1. The ages and make/model of > these systems are important clues. All machines: -- AIC RMC2E2 chassis with hotpluggable SATA backplane. -- Intel SE7520BD2 motherboards with 6GB Registered ECC DDR RAM. -- Dual 2.8GHz (Low Voltage) Xeon's -- Ages range from ~1 year to ~2 months. > 2. Is the 2.5" to 3.5" "adapter" just a mechanical carrier, or is it also > involved in the (data) cabling? This adapter (coupled with WD's specific > recommendation that you *not* use this drive in your application) *and* > the > inclusion of the highpoint driver are big enough 'atypical' factors that > they > deserve special attention. You need to be certain that these have been > properly ruled out and aren't involved/contributing/confusing matters. The adapter is passive. My main problem with a hardware based resolution, is that things work 100% of the time with installation and probably something like 95-98% of the time with imaging (the only failures being the grub hangs which are usually corrected by grub re-install -- which I think are actually the same symptom (retrospectively) except it is hanging loading the kernel and before printing to the screen??). > 3. We should not overlook this one important clue: "... requires re- > installing > grub which sometimes produces a hang on loading stage1.5." > > All things being equal, I think Carlos' hypothesis is likely correct. I'll > be > looking forward to your "report", so have fun and good luck! <snip> Thanks -- my initial results: I resized reiserfs on three machines that were hanging (to move swap to the inside of the drive) -- created an ext2 formatted partition between cylinders 1 and 900 (which, predictably solved the problem). I am now waiting to allocate 20 machines (10 control, 10 experimental) to perform initrd updates on and reboot where the control group has a single / partition and the experimental group would have the /boot partition as described above. I'll keep you all updated -- thanks again. Patrick

3 4

OO: If you can make it, I can break it!
by Steven T. Hatton 28 Dec '05

28 Dec '05

I decided to see what I could accomplish using OpenOffice in terms of extracting data from HTML. When I try to open the document, it begins to load, and then locks up. This happens every time. There was a time, long, long ago when StarOffice was one of the best tools for playing with HTML in areas such as printing and data extraction. I suspect the functionality is still there, I just can't seem to access it. Has anyone else encountered this, or similar problems? My experience over the years has been that StarOffice/OO is very prone to locking up. That really needs to be addressed. There should be ways to handle the exceptional conditions which cause lockups that don't involve SIGKILL. The OO developers should stop doing anything else until this is corrected. Steven

10 13

Reliability of SuSE mirrors
by Paul W. Abrahams 28 Dec '05

28 Dec '05

I've always assumed that the SuSE mirrors -- at least the ones that claim to be complete -- were as reliable as the SuSE site itself. But I had a frustrating experience doing a KDE 3.5 update using mirrors.kernel.org and Yast. I kept getting a complaint that the kdebase3 package (and a number of others) couldn't be found, though a number of packages did get installed. So I finally tried going to ftp.suse.com instead and the update worked correctly -- all the packages that I was missing before were there and were installed. Has anyone else had a similar experience? Any opinions on mirror sites versus the SuSE site itself? Paul

5 10

RE: [opensuse] can't ping to gateway
by Fabian_Salamanca＠Dell.com 28 Dec '05

28 Dec '05

Please send the output for: # mii-tool Maybe there is a problem with your ethernet network Also some output from: # tcpdump -i eth0 Are you using DHCP? Cheers, -----Original Message----- From: Daniel Bauer [mailto:linux@daniel-bauer.com] Sent: Tuesday, December 20, 2005 11:58 AM To: opensuse(a)opensuse.org Subject: [opensuse] can't ping to gateway Hello, good evening Just installed opensuse succcessful (standard kde install, no changes in software selection). Installed network card with Yast, stopped firewall (clicked "start manual" and stopped it). Everything seems normal, but I don't get any connection to outside. Ping to my gateway doesn't work ("destination host unreachable"). I just entered all the same values for local ip, gateway, name-server... as in Suse 9 on same machine. Ping to local host works. I don't know which info you need, here's what is displayed when typing "ifconfig": eth0 Link encap:Ethernet HWaddr 00:08:A1:35:BF:BC inet addr:192.168.2.2 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: fe80::208:a1ff:fe35:bfbc/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:14 errors:0 dropped:0 overruns:0 frame:0 TX packets:38 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1957 (1.9 Kb) TX bytes:2462 (2.4 Kb) Interrupt:9 Base address:0xb400 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:102 errors:0 dropped:0 overruns:0 frame:0 TX packets:102 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:6880 (6.7 Kb) TX bytes:6880 (6.7 Kb) this is (apart from the no. of packets/bytes) exactly the same as in Suse 9. "route -n" gives the following: Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 eth0 where I am wondering about the "169.254.0.0"-line, because I never typed in such a ip-number anywhere. On Suse 9 this would give me only 2 lines (192... and 0.0.0.0). Should I send the /var/log/messages of my last Suse10 session? In case: Copy text in mail or attach? What did I forget to make my network connection work? Thanks for any help. Daniel --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-help(a)opensuse.org

9 16