January 2009 - openSUSE Users - openSUSE Mailing Lists

[opensuse] openSUSE 11.1 x86_64 on a 512MB RAM system
by Rui Santos 06 Jan '09

06 Jan '09

Hi all, I've stumbled on a problem, on a test machine, using openSUSE 11.1 x86_64 system with 512MB of RAM. This test was just to confirm a friends claim that he was unable to get a working server with that kind of hardware. The problem is that openSUSE uses all of the memory for simple tasks, like fsck. Just as an example, here is an strace of a fsck.vfat on a filesystem. For this I just left the system with 90MB free memory before I ran this command: 2090 execve("/sbin/fsck.vfat", ["fsck.vfat", "/dev/sdb1"], [/* 20 vars */]) = 0 2090 brk(0) = 0x60f000 2090 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f093726f000 2090 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f093726e000 2090 access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory) 2090 open("/etc/ld.so.cache", O_RDONLY) = 3 2090 fstat(3, {st_mode=S_IFREG|0644, st_size=32722, ...}) = 0 2090 mmap(NULL, 32722, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f0937266000 2090 close(3) = 0 2090 open("/lib64/libc.so.6", O_RDONLY) = 3 2090 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\240\346\1\0\0\0\0\0"..., 832) = 832 2090 fstat(3, {st_mode=S_IFREG|0755, st_size=1406248, ...}) = 0 2090 mmap(NULL, 3506872, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f0936cfa000 2090 fadvise64(3, 0, 3506872, POSIX_FADV_WILLNEED) = 0 2090 mprotect(0x7f0936e49000, 2097152, PROT_NONE) = 0 2090 mmap(0x7f0937049000, 20480, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x14f000) = 0x7f0937049000 2090 mmap(0x7f093704e000, 17080, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f093704e000 2090 close(3) = 0 2090 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f0937265000 2090 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f0937264000 2090 arch_prctl(ARCH_SET_FS, 0x7f09372646f0) = 0 2090 open("/dev/urandom", O_RDONLY) = 3 2090 read(3, "\25\v\205\210\266\247\351\223", 8) = 8 2090 close(3) = 0 2090 mprotect(0x7f0937049000, 16384, PROT_READ) = 0 2090 mprotect(0x60b000, 4096, PROT_READ) = 0 2090 mprotect(0x7f0937270000, 4096, PROT_READ) = 0 2090 munmap(0x7f0937266000, 32722) = 0 2090 fstat(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(5, 1), ...}) = 0 2090 ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0 2090 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f093726d000 2090 write(1, "dosfsck 2.11, 12 Mar 2005, FAT32"..., 38) = 38 2090 open("/dev/sdb1", O_RDONLY) = 3 2090 fstat(3, {st_mode=S_IFBLK|0660, st_rdev=makedev(8, 17), ...}) = 0 2090 lseek(3, 0, SEEK_SET) = 0 2090 read(3, "\353X\220mkdosfs\0\0\2 \0\2\0\0\0\0\370\0\0?\0\377\0\0\0\0\0"..., 512) = 512 2090 lseek(3, 160039240192, SEEK_SET) = 160039240192 2090 brk(0) = 0x60f000 2090 brk(0x630000) = 0x630000 2090 read(3, "\353R\220NTFS \0\2\10\0\0\0\0\0\0\0\370\0\0?\0\377\0?\0\0\0"..., 512) = 512 2090 lseek(3, 3072, SEEK_SET) = 3072 2090 read(3, "\353X\220mkdosfs\0\0\2 \0\2\0\0\0\0\370\0\0?\0\377\0\0\0\0\0"..., 512) = 512 2090 lseek(3, 512, SEEK_SET) = 512 2090 read(3, "RRaA\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 512) = 512 2090 mmap(NULL, 39055360, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f09347bb000 2090 lseek(3, 16384, SEEK_SET) = 16384 2090 read(3, "\370\377\377\17\377\377\377\17\370\377\377\17\377\377\377\17\211\4\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 39053012) = 39053012 2090 mmap(NULL, 39055360, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f093227c000 2090 lseek(3, 39069696, SEEK_SET) = 39069696 2090 read(3, <unfinished ...> 2090 +++ killed by SIGKILL +++ The latest SIGKILL was generated by ooom-kill. Linux kernel kills the process in order to get memory. There were no programs running, as this command was issued under init 1 The system has no SWAP If you check the final two mmap's, fsck maps 80MB of memory just to check a simple vfat filesystem. What is this ?! 80 MB. I used to run a full system on this, including fsck's. As I stated, this is just an example. Numerous other programs take a lot of memory making a system with 512MB of RAM almost unusable. Even so with a 1GB of RAM ooo-kill is sometimes called to free up RAM. Has anyone else noticed this ? I've googled a bit but unfortunately, I found no one using 512MB of RAM with a 64bits System. -- Rui Santos http://www.ruisantos.com/ Veni, vidi, Linux! -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

8 26

[opensuse] M-player problem!
by James Hatridge 06 Jan '09

06 Jan '09

Hi all, I upgraded my system with a new power pack, motherboard, better cpu, and more main memory. I put back in my video card and hard disks. When I rebooted I had only minor problems. BUT now Mplayer will not work! I get his error: Error opening/initializing the selected video_out (-vo) device. Its odd that when I use mc and click on a video it works, but run Mplayer and I get this error and then the sound track of the video starts. Any ideas what to do? Thanks, JIM -- Jim Hatridge Linux User #88484 Ebay ID: WartHogBulletin ------------------------------------------------------ WartHog Bulletin Info about new German Stamps http://www.WartHogBulletin.de Many Enemies -- Much Honor! Anti-US Propaganda stamp collection http://www.manyenemies-muchhonor.info An American in Bavaria http://www.gaubodengalerie.de -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

6 9

[opensuse] Installing 11.1 to Unused Partition From Running System?
by Randall R Schulz 06 Jan '09

06 Jan '09

Hi, I was wondering if it's feasible (if at all possible) to perform an openSUSE 11.1 installation to an unused partition on my existing 10.0 system while it (the 10.0 system) is running? Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] New partition killed MBR?
by L. V. Lammert 06 Jan '09

06 Jan '09

I built an 11.1 system a few weeks ago, .. originally installing 11.1 into physical partition 1, using it as an extended partition of 50GB [the system will eventually be multi-boot]. Yesterday I created physical partition 2 & 3 [both ext3], but that has killed the boot record! The partition table shows [with a System Rescue CD] all three partitions correctly, .. and /dev/sda1 is still flagged bootable. Does 11.1 have a problem with a disk configuration like this? Why would creating a new partition kill the MBR? I tried booting 'Repair Installation' on the 11.1 CD, and gave up loading an Install Kernel with six parts - I stopped it after 10 minutes only got to part 2. Any suggestions would be appreciated, .. Lee -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

5 5

[opensuse] 11.1 upgrade on md raid root fails to boot
by Joe Morris 06 Jan '09

06 Jan '09

Well, i have managed to get enough info to know this is bug https://bugzilla.novell.com/show_bug.cgi?id=445490, which says it is resolved, but obviously not in the GM version of packages. Unfortunately, I cannot see what was needed to fix this, as I get an access denied when clicking on https://bugzilla.novell.com/show_bug.cgi?id=435778 at the end (where the fix was supposed to be). Is there an update of mkinitrd, or udev, or something to fix this? I upgraded from 10.3 yesterday, but not being able to boot after it was finished was a real problem. I was finally able to boot installed system (hidden in the repair tools) to be able to boot again and was able to find the above bug report and found out with a few tweaks I could eventually boot up by hitting Ctrl-D to seemingly exit the bootup system. I have been running mdraid 1 since 8.0, and mdraid 1 roots since 9.1 IIRC, but this was the hardest to figure out, and appears to be a problem that is quite old ( http://lists.opensuse.org/opensuse-bugs/2008-08/msg07297.html ). I would really appreciate it if anyone knows how I can repair the boot process in 11.1 so boot.md does not fail, and I do not need to hit Ctrl-D to be able to boot? BTW, I have a mdraid root and home, and yesterday trying to repair it I was seeing it go from md0 & md1 to md126 and md127, trying the repair option was a disaster, as it fscked the individual disk, which failed (and I canceled, but that I eventually figured out had somehow split the 2 partitions to one disk was md125_0 and the other md127_0. It was bizarre. Seems the mdraid part of 11.1 has some real problems this time around (and the server at our office has 4 mdraid devices, not looking forward to that upgrade). Does anyone know if this was worse because of the upgrade path (or in other words, has anyone installed 11.1 on a mdraid root device and did not have problems)? TIA for any help. -- Joe Morris Registered Linux user 231871 running openSUSE 10.3 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

3 2

[opensuse] Querying write buffer type and size
by Markus Moeller 06 Jan '09

06 Jan '09

I'd like to find out if an output stream is buffered and if so what is the buffer size. I know there are several set functions setvbuf, setbuffer, etc.. but I can't find a get function. Is there a standard way of getting this information ? Thank you Markus -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] Cheese webcam wrong input
by Teruel de Campo MD 06 Jan '09

06 Jan '09

ref opensuse 11.1 logitech Orbit-AF mythtv - Hauppage pvr-350 Problem: cheese loads OK but it seems to point to /dev/video1 which is the pvr-350 card instead of to the UVC Camera that is /dev/video0. I have not found a way to change it. BTW the web camera is working well not only the video but also the motor controls. skype, ekiga guvcview luvcview all work great. Thxs -=terry=- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] Kontact 1.10.3 (KDE4) and MS Exchange server?
by Joop Beris 06 Jan '09

06 Jan '09

Hello listmates, I am looking for information, some good tips or something like that about how I can connect to an MS Exchange server using Kontact 1.10.3. There was an experimental Exchange plugin for Kontact under KDE3, but it is not available for KDE4, it seems. Email is working fine, using IMAP. But I'd like to be able to use the calender and address book functions as well. Has anybody got this working? Or knows how it is done? I know about Evolution and that I can use Evolution as an Exchange client, but I prefer KDE and KDE apps. Thanks in advance, Joop ------------------------------------------------------------ Dit bericht is gescand op virussen en andere gevaarlijke inhoud door MailScanner en lijkt schoon te zijn. Mailscanner door http://www.prosolit.nl Professional Solutions fot IT -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] Another 64bit thread
by Mark Misulich 06 Jan '09

06 Jan '09

Hi, I am thinking about trying a new linux adventure and installing 64bit 11.1 on the laptop that I use for work. I am wondering if I install the 64 bit operating system in root, can I use the old 32 bit home? Or, does that need to be formatted and made new in 64 bit too? Thanks, Mark -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

3 2

[opensuse] suspend to disk and size of swap partition
by Malte Gell 06 Jan '09

06 Jan '09

Hi there, in order to use suspend to disk one has to set a swap partition with the "resume=" option in the bootloader. Okay. But, if I have e.g. 2 GB of RAM I should have 2 GB swap space for suspend to disk. Now I have two seperate swap paritions, each 1 GB, in sum it is enough, but with "resum=" you can name only one partition. So, my question is, is "suspend to disk" intelligent enough to use ALL available swap partitions, though there is only one resume=/dev/hdc5 specified in GRUB ? /dev/hdc5 is only 1GB swap, but I have more swap space, does STD recognize them automagically? tia Malte -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 2