March 2009 - openSUSE Users - openSUSE Mailing Lists

Re: [opensuse] RAID1 boot problems
by cagsm 06 Mar '09

06 Mar '09

> Did you ever get an answer? If not let me know and I'll pickup the thread. But > if you got it solved -- no need. stop sending private mails. this is exactly what you are asking me if anyone else was intelligent enough to answer a question in private that was started in public. :( and no, i have not worked it out with grub, i have found a number of threads and discussions and hits (they talk about going to rescue mode with opensuse install media, selecting rescue mode, and doing the grub commands and various stuff there) but that all didnt work out and i didnt have the time to do some bugreporting yet. but i think i remember seeing some bugreport about grub that was talking about exactly this behaviour. will need to look up the links again. http://advosys.ca/viewpoints/2007/04/setting-up-software-raid-in-ubuntu-ser… i have also found some additional info about the pre-chroot remount stuff of /proc and /dev and stuff like that, that helped a little but the re-installing of grub on the two harddisks i have didnt succeed i still get errors and lots of complications inside the opensuse rescue system.... i dont recall the exact errors any more, it annoyed me really much, but its still unsolved. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

4 4

[opensuse] openSUSE, X86_64, Python and FusionIcon
by Chuck Payne 06 Mar '09

06 Mar '09

Guys, This is the second e-mail about this issue. I would have wrote off as something I did. But I have now install 11.1 on three systems. All diffirent hardware. All give me the same error when I launch fusion-icon. * Error: the "FusionIcon" module is missing. If you did not install fusion-icon to /usr, you may need to add the appropriate site-packages directory to your PYTHONPATH I have done a TON of searching on the net and don't see where I can fix this. I have try to export a path, but I still export PYTHONPATH=/usr/lib/python2.5/site-packages/:/usr/lib/python2.6/site-packages/:/usr/lib64/python/site-packages/:/usr/lib64/python2.5/site-packages/:/usr/lib/python2.6/site-packages/:$PYTHONPATH But I am still getting that error. What do I need to do to fix this? Payne -- ---------------------------------------- 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

3 5

[opensuse] Asterisk @11.1
by Hans Witvliet 06 Mar '09

06 Mar '09

For those who are using Asterisk: At last they've managed to create ready-to-run packages for openSUSE_11.1. They are there since a couple of hours.. (For other versions it was allready available for some time on the OBS) And for 32 aswell Mirrored at: http://ftp5.gwdg.de/pub/opensuse/repositories/network:/telephony:/asterisk/… For those who finaly succeeded (I tried to package it, but it was a rough job): Tnx a lot! hw -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] Evolution stuff
by Roger Oberholtzer 06 Mar '09

06 Mar '09

The latest release of Evolution from openSUSE has fixed a problem where calendar invites did not get parsed properly and added to the calendar. That now works again. I'm happy! I have two questions about intended behavior with calendar emails that I don't feel I see a specific answer to in the places I have looked: 1. When I receive a calendar item that is a meeting, I can press a button that I want to attend, or refuse, or whatever. If I do so, Evolution zips a message off to the sender of the calendar message. However, I eventually get a message that the mail could not be delivered, like: This is an automatically generated Delivery Status Notification. Delivery to the following recipients failed. user(a)wherever.com This user exists and I send normal mail to them. The response comes from the postmaster at wherever.com, which is running Exchange. Should Evolution be able to respond properly? I do not use the Exchange part of Evolution, as I do not get any of my mail from such a place. But someone sending me mail may have it so. 2. I think I know the answer (negative) but I have to ask: can Evolution directly share it's calendar with someone running outlook? And, can Evolution access someone else's outlook calendar? I realize this may not be the best list for this, but I thought since I was asking about Evolution as configured/compiled/delivered with openSUSE, this was a good place to start. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 8-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 2

Re: [opensuse] rsync with password?
by L. V. Lammert 05 Mar '09

05 Mar '09

At 05:29 PM 3/5/2009 -0500, Greg Freemyer wrote: >All, > >I'm trying to connect to a remote rsync server. ie. It is running >rssh as the shell and rsync is one of the few allowed programs to run. Forget the password - setup a keypair and use ssh. Lee -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] open suse project management?
by JW 05 Mar '09

05 Mar '09

If you really have a feature you want to see intergrated in to future versions of SuSE . . . who do you talk to or write? Or are we stuck using the opensuse.org wiki wishlists? Is there any "higher authority" to appeal to than the wiki? JW -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

6 7

[opensuse] Re: [opensuse-factory] kpartx -d / activate_device_mapper -d
by Felix Miata 05 Mar '09

05 Mar '09

On 2009/03/03 03:25 (GMT+0100) Carlos E. R. composed: > > On Monday, 2009-03-02 at 17:14 -0500, Felix Miata wrote: >>> >>> During 11.1 devel via https://bugzilla.novell.com/show_bug.cgi?id=397816 I >>> >>> setup device mapper on one system in order to access all actual partitions >>> >>> while using ata_piix driver. Now on that system I have a 2.6.29 kernel, so no >>> >>> longer need dm_linear. So far, I've had no luck reversing the process. >>> >>> Neither subject command seems to produce any impact. I ran both kpartx -d >>> >>> /dev/sda and activate_device_mapper -d /dev/sda before running mkinitrd, and >>> >>> still the resulting initrd features dm_linear and kpartx. >>> >>> /etc/udev/rules.d/dm_linear.rules did get a fresh write, while >>> >>> /etc/udev/rules.d/70-kpartx.rules did not. I blacklisted dm_linear & kpartx >>> >>> in /etc/modprobe.conf.local too, but that didn't help either. Short of a >>> >>> fresh install, how do I eliminate them, and go back to mounting directly to >>> >>> /dev/sda* devices instead of /dev/dm-* devices? > > I have no idea, but you could test renaming those modules, so that they > > can not be loaded. The blacklist does not work if another module > > explicitly wants to load a blacklisted module. Renaming didn't result in any progress. :-( > > At least you should get an error, and that error might point to what wants > > to load them :-? > > Another idea. How about checking your fstab does refer to /dev/sdX? All native partitions are LABEL=. I've made a lot of progress. I'm now running 2.6.29-rc5-1 on the ata_piix driver, but I still get "waiting for device /dev/root to appear ... could not find /dev/root ... want to fall back to /dev/hda10" during booting if I used my traditional Grub stanza with root=LABEL= instead of root=/dev/Xda10. While booted to an old kernel using piix instead of device mapper, I did: activate_device_mapper -d /dev/sda kpartx -d /dev/sda rpm -e --nodeps kpartx rpm -e --nodeps dmraid rm /dev/device-mapper rm /dev/mapper/control mv /etc/udev/rules.d/dm_linear.rules dm0_linear.rule0s mv /lib/modules/....29...-pae/kernel/drivers/md to m000d mkinitrd -v -k -i on .29 kernel Booting that got me again "waiting for device /dev/root to appear ... could not find /dev/root ... want to fall back to /dev/hda10", but then it couldn't find /dev/hda10. Next I updated to 2.6.27.19-3.2-pae on a different 11.1 system running on ata_piix, installed that kernel on this system, copied the initrd from the other system, and tried again. Again on the freshly generated initrd I got "waiting for device /dev/root to appear ... could not find /dev/root ... want to fall back to /dev/hda10", which it couldn't find. Then I tried the copied initrd, which got me "waiting for device /dev/root to appear ... could not find /dev/root ... want to fall back to /dev/sda10". That succeeded. After I did that, I did mkinitrd on the .29 kernel, which got me "waiting for device /dev/root to appear ... could not find /dev/root ... want to fall back to /dev/dev/disk/by-id/...part10", which succeeded. I tried zypper rm dmraid kpartx before doing rpm -e on kpartx and dmraid, but zypper then wanted to remove: autoyast2-installation multipath-tools yast2-add-on yast2-backup yast2-bootloader yast2-installation yast2-repair yast2-restore yast2-storage yast2-tune yast2-update in addition to dmraid and kpartx. After 'zypper in kpartx dmraid', activate_dm_linear -d /dev/sda returned nothing, and kpartx -d /dev/sda returned: /proc/misc: No entry for device-mapper found Is device-mapper driver missing from kernel? device-mapper: version ioctl failed: Inappropriate ioctl for device device-mapper-prerequisites not met Then I tried on Grub kernel line replacing root=LABEL=S16A-10factory with root=/dev/sda10, and booting proceeded normally. This looks like https://bugzilla.novell.com/show_bug.cgi?id=300550 has resurfaced. AFAICT, I might still need to get dm_linear & kpartx left out of the initrd for .29. Is this true? Any other suggestions? -- "The plans of the diligent lead to profit as surely as haste leads to poverty." Proverbs 21:5 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] Re: [opensuse-factory] kpartx -d / activate_device_mapper -d
by Felix Miata 05 Mar '09

05 Mar '09

On 2009/03/03 03:25 (GMT+0100) Carlos E. R. composed: > On Monday, 2009-03-02 at 17:14 -0500, Felix Miata wrote: >>> During 11.1 devel via https://bugzilla.novell.com/show_bug.cgi?id=397816 I >>> setup device mapper on one system in order to access all actual partitions >>> while using ata_piix driver. Now on that system I have a 2.6.29 kernel, so no >>> longer need dm_linear. So far, I've had no luck reversing the process. >>> Neither subject command seems to produce any impact. I ran both kpartx -d >>> /dev/sda and activate_device_mapper -d /dev/sda before running mkinitrd, and >>> still the resulting initrd features dm_linear and kpartx. >>> /etc/udev/rules.d/dm_linear.rules did get a fresh write, while >>> /etc/udev/rules.d/70-kpartx.rules did not. I blacklisted dm_linear & kpartx >>> in /etc/modprobe.conf.local too, but that didn't help either. Short of a >>> fresh install, how do I eliminate them, and go back to mounting directly to >>> /dev/sda* devices instead of /dev/dm-* devices? > I have no idea, but you could test renaming those modules, so that they > can not be loaded. The blacklist does not work if another module > explicitly wants to load a blacklisted module. Renaming didn't result in any progress. :-( > At least you should get an error, and that error might point to what wants > to load them :-? > Another idea. How about checking your fstab does refer to /dev/sdX? All native partitions are LABEL=. I've made a lot of progress. I'm now running 2.6.29-rc5-1 on the ata_piix driver, but I still get "waiting for device /dev/root to appear ... could not find /dev/root ... want to fall back to /dev/hda10" during booting if I used my traditional Grub stanza with root=LABEL= instead of root=/dev/Xda10. While booted to an old kernel using piix instead of device mapper, I did: activate_device_mapper -d /dev/sda kpartx -d /dev/sda rpm -e --nodeps kpartx rpm -e --nodeps dmraid rm /dev/device-mapper rm /dev/mapper/control mv /etc/udev/rules.d/dm_linear.rules dm0_linear.rule0s mv /lib/modules/....29...-pae/kernel/drivers/md to m000d mkinitrd -v -k -i on .29 kernel Booting that got me again "waiting for device /dev/root to appear ... could not find /dev/root ... want to fall back to /dev/hda10", but then it couldn't find /dev/hda10. Next I updated to 2.6.27.19-3.2-pae on a different 11.1 system running on ata_piix, installed that kernel on this system, copied the initrd from the other system, and tried again. Again on the freshly generated initrd I got "waiting for device /dev/root to appear ... could not find /dev/root ... want to fall back to /dev/hda10", which it couldn't find. Then I tried the copied initrd, which got me "waiting for device /dev/root to appear ... could not find /dev/root ... want to fall back to /dev/sda10". That succeeded. After I did that, I did mkinitrd on the .29 kernel, which got me "waiting for device /dev/root to appear ... could not find /dev/root ... want to fall back to /dev/dev/disk/by-id/...part10", which succeeded. I tried zypper rm dmraid kpartx before doing rpm -e on kpartx and dmraid, but zypper then wanted to remove: autoyast2-installation multipath-tools yast2-add-on yast2-backup yast2-bootloader yast2-installation yast2-repair yast2-restore yast2-storage yast2-tune yast2-update in addition to dmraid and kpartx. After 'zypper in kpartx dmraid', activate_dm_linear -d /dev/sda returned nothing, and kpartx -d /dev/sda returned: /proc/misc: No entry for device-mapper found Is device-mapper driver missing from kernel? device-mapper: version ioctl failed: Inappropriate ioctl for device device-mapper-prerequisites not met Then I tried on Grub kernel line replacing root=LABEL=S16A-10factory with root=/dev/sda10, and booting proceeded normally. This looks like https://bugzilla.novell.com/show_bug.cgi?id=300550 has resurfaced. AFAICT, I might still need to get dm_linear & kpartx left out of the initrd for .29. Is this true? Any other suggestions? -- "The plans of the diligent lead to profit as surely as haste leads to poverty." Proverbs 21:5 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 1

[opensuse] replacing X
by lynn 05 Mar '09

05 Mar '09

Is it possible to replace the X from 11.1 with the X from 11.0? Thanks L -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

12 18

Re: [opensuse] kernel, kernel source, utsrelease.h alignment
by Michael Mueller 05 Mar '09

05 Mar '09

problem solved completely; thanks everyone On Thu, Mar 5, 2009 at 5:54 AM, Istvan Gabor <suseuser04(a)lajt.hu> wrote: > I am not sure if this will be relevant in your case but I had problems earlier in openSUSE 10.x with building kernel drivers related to utsrelease.h. Then I found a cool solution at Novell's site and problems have gone. > It's titled as "Compiling Kernel Drivers for SUSE 10 By Example" and the link is: > http://www.novell.com/coolsolutions/feature/16340.html perfect! that solved the last problem of getting utsrelease.h aligned to the kernel and kernel source: dt:/usr/src/linux # rpm -q -a | grep -i kernel-source kernel-source-2.6.27.19-3.2.1 dt:/usr/src/linux # rpm -q -a | grep -i kernel-default kernel-default-base-2.6.27.19-3.2.1 kernel-default-extra-2.6.27.19-3.2.1 kernel-default-2.6.27.19-3.2.1 dt:/usr/src/linux # uname -r 2.6.27.19-3.2-default dt:/usr/src/linux # make cloneconfig Cloning configuration file /proc/config.gz # # configuration written to .config # dt:/usr/src/linux # make modules_prepare scripts/kconfig/conf -s arch/x86/Kconfig CHK include/linux/version.h CHK include/linux/utsrelease.h UPD include/linux/utsrelease.h CC arch/x86/kernel/asm-offsets.s GEN include/asm/asm-offsets.h CALL scripts/checksyscalls.sh dt:/usr/src/linux # cat /usr/src/linux/include/linux/utsrelease.h #define UTS_RELEASE "2.6.27.19-3.2-default" -- Mike -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 1