May 2006 - openSUSE Factory - openSUSE Mailing Lists

tagmedia question
by houghi 10 May '06

10 May '06

SUSE uses tagmedia to check the media. I used the following command (and outcome) houghi@penne : tagmedia --md5 --pad 150 --check \ ~/iso/10.1_RC3/DVD_DIR/SUSE-10.1-0-DVD.iso md5sum=99b7d0c508d213aa0c9ab6edfad56ef1 pad=150 check=1 However when I boot, YaST is looking for: 508ed5a962cc236da9e141df99c33386 What am I doing wrong? The next thing is when I do a`checkmedia ~/iso/10.1_RC3/DVD_DIR/SUSE-10.1-0-DVD.iso` I get: not an iso This even though it is burnable and bootable: houghi@penne : file ~/iso/10.1_RC3/DVD_DIR/SUSE-10.1-0-DVD.iso /home/houghi/iso/10.1_RC3/DVD_DIR/SUSE-10.1-0-DVD.iso: ISO 9660 CD-ROM filesystem data 'SU101DVD.001 ' (bootable) What gives? houghi -- Nutze die Zeit. Sie ist das Kostbarste, was wir haben, denn es ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Werk und Arbeit, und das Sein wichtiger als das Tun - Johannes Müller-Elmau

10 33

iSCSI testing
by Anders Norrbring 08 May '06

08 May '06

I can't get iSCSI to work as an initiator.. I run it on a x86_64 installation of 10.1 GM + factory and I have installed iscsid 0.3 plus the yast2 modules. The last try I made I could at least reach the target, but got this in the log.. Has anybody gotten iSCSI to work? If so, how...? May 8 16:32:33 labbet kernel: scsi0 : iSCSI Initiator over TCP/IP, v.0.3 May 8 16:32:33 labbet kernel: klogd 1.4.1, ---------- state change ---------- May 8 16:32:34 labbet syslog-ng[2069]: Changing permissions on special file /dev/xconsole May 8 16:32:34 labbet syslog-ng[2069]: Changing permissions on special file /dev/tty10 May 8 16:32:34 labbet kernel: ----------- [cut here ] --------- [please bite here ] --------- May 8 16:32:34 labbet kernel: Kernel BUG at drivers/scsi/scsi_transport_iscsi.c:964 May 8 16:32:34 labbet kernel: invalid opcode: 0000 [1] May 8 16:32:34 labbet kernel: last sysfs file: /class/scsi_host/host0/proc_name May 8 16:32:34 labbet kernel: CPU 0 May 8 16:32:34 labbet kernel: Modules linked in: iscsi_tcp scsi_transport_iscsi scsi_mod ipv6 cpufreq_ondemand cpufreq_userspace cpufreq_powersave powernow_k8 freq_table edd button battery ac apparmor aamatch_pcre xfs_quota xfs exportfs loop dm_mod floppy i2c_nforce2 i2c_core ide_cd cdrom e1000 ehci_hcd forcedeth ohci_hcd usbcore reiserfs fan thermal processor amd74xx ide_disk ide_core May 8 16:32:34 labbet kernel: Pid: 3904, comm: iscsid Not tainted 2.6.16.13-4-default #1 May 8 16:32:34 labbet kernel: RIP: 0010:[<ffffffff8823930d>] <ffffffff8823930d>{:scsi_transport_iscsi:iscsi_copy_param+14} May 8 16:32:34 labbet kernel: RSP: 0018:ffff81003c197af0 EFLAGS: 00010206 May 8 16:32:34 labbet kernel: RAX: 000000000000002f RBX: ffff81003f790800 RCX: ffffffff8823fca0 May 8 16:32:34 labbet kernel: RDX: ffff8100167e4c48 RSI: ffff8100167e4c48 RDI: ffff8100167e4c10 May 8 16:32:34 labbet kernel: RBP: ffff810027ae4800 R08: ffff81003c197b3c R09: 0000000000000000 May 8 16:32:34 labbet kernel: R10: 61742d3032746661 R11: 0000000000000246 R12: ffff81003c197ed8 May 8 16:32:34 labbet kernel: R13: ffff8100167e4c10 R14: ffff81003c197dd8 R15: ffff81003bc68b80 May 8 16:32:34 labbet kernel: FS: 00002af6ba677ae0(0000) GS:ffffffff803f7000(0000) knlGS:00000000f7db5aa0 May 8 16:32:34 labbet kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b May 8 16:32:34 labbet kernel: CR2: 00000000005160b0 CR3: 000000002ad7f000 CR4: 00000000000006e0 May 8 16:32:34 labbet kernel: Process iscsid (pid: 3904, threadinfo ffff81003c196000, task ffff81003d4d9080) May 8 16:32:34 labbet kernel: Stack: ffffffff8823a9cf ffff810029835e70 ffff81003973c000 ffff81003bc68bd8 May 8 16:32:34 labbet kernel: ffffffff80253e46 ffff8100167e4c00 ffffffff8824a7c0 0000007800000000 May 8 16:32:34 labbet kernel: 0000000000000246 00000000000000d0 May 8 16:32:34 labbet kernel: Call Trace: <ffffffff8823a9cf>{:scsi_transport_iscsi:iscsi_if_rx+1039} May 8 16:32:34 labbet kernel: <ffffffff80253e46>{skb_recv_datagram+119} <ffffffff8026a985>{netlink_data_ready+18} May 8 16:32:34 labbet kernel: <ffffffff80269b97>{netlink_sendskb+38} <ffffffff8026afcf>{netlink_sendmsg+723} May 8 16:32:34 labbet kernel: <ffffffff8024d2d7>{sock_sendmsg+240} <ffffffff80136b5e>{autoremove_wake_function+0} May 8 16:32:34 labbet kernel: <ffffffff80170482>{link_path_walk+207} <ffffffff80144e86>{audit_sockaddr+56} May 8 16:32:34 labbet kernel: <ffffffff8024d7fc>{sys_sendmsg+527} <ffffffff8014466e>{audit_syscall_entry+301} May 8 16:32:34 labbet kernel: <ffffffff8010cf11>{syscall_trace_enter+190} <ffffffff8010a529>{tracesys+209} May 8 16:32:34 labbet kernel: May 8 16:32:34 labbet kernel: Code: 0f 0b 68 38 b4 23 88 c2 c4 03 b9 04 00 00 00 83 f8 04 4c 89 May 8 16:32:34 labbet kernel: RIP <ffffffff8823930d>{:scsi_transport_iscsi:iscsi_copy_param+14} RSP <ffff81003c197af0> May 8 16:32:34 labbet iscsid: could not open '/sys/class/iscsi_connection/connection0:0/exp_statsn': 2 May 8 16:32:34 labbet iscsid: Could not read /sys/class/iscsi_connection/connection0:0/exp_statsn. Using zero fpr exp_statsn

2 1

Strange behaviour of installation source
by Marcel Hilzinger 08 May '06

08 May '06

I just added a normal, selfmade YaST installtion source to 10.1, using the Add-on-Produkt module. There was one selection on the media. If I choose selections in YaST, the selection is not displayed does YaST only display signed selections? If I switch the view to installation sources, I can choose packages for installtion and this also seems to work. But I can not install newer versions of packages, which are already installed (tried with kaffeine 0.8.1) any idea, what's the reason for this? -- Mit freundlichen Grüßen, Marcel Hilzinger Linux New Media AG Süskindstr. 4 D-81929 München Tel: +49 (89) 99 34 11 0 Fax: +49 (89) 99 34 11 99

1 1

FreeNX seems to have problems with some passwords
by Heiko Helmle 08 May '06

08 May '06

Hello, Did anyone try the FreeNX Server that's on OpenSuSE RC3? When you try to use a password that starts with a blank character, login with that user fails. If you use any other type of password it seems to work, just blank at the beginning is not working. If anybody can reproduce this, then i'll assume this is a bug in nxserver and not in my nxclient installation. Regards Heiko Helmle

1 0

Eiffel, once again?
by Ulrich Windl 08 May '06

08 May '06

Hi, would an announcement like the following qualify for adding the software?: ----------quote---------- - Eiffel Software to Offer Dual Licensing for EiffelStudio Eiffel Software is pleased to announce its new Dual Licensing Model for EiffelStudio. This new model described at http://www.eiffel.com/licensing/licensing.html is based the principle of Fair Exchange and allows customers to develop applications either for commercial use or as Open Source products. The release of EiffelStudio as Open Source environment which took place on April 5 (see column below) has already generated tremendous excitement in the developers community. The Open Source version of EiffelStudio under the GNU General Public License (GPL) is available at: http://eiffelsoftware.origo.ethz.ch. --------------end quote----------- Regards, Ulrich

3 2

Re: Delta-ISO problem for CD1
by Heiko Helmle 08 May '06

08 May '06

I have the same problem, albeit on a non-SuSE distribution (gentoo), trying to get RC3 ISOs. hel@hellap ~/tmp $ md5sum SUSE-Linux-10.1-RC1-Addon-BiArch.iso SUSE-Linux-10.1-RC1_RC3-Addon-BiArch.delta.iso 05644d16b959a54d6c68a997ffa95fb5 SUSE-Linux-10.1-RC1-Addon-BiArch.iso 49c163be6fcfd11ab4e43d3b3acaabc3 SUSE-Linux-10.1-RC1_RC3-Addon-BiArch.delta.iso but the resulting RC3-ISO has the md5: 4d3c42182655136a112f4d01a35cedd2 SUSE-Linux-10.1-RC3-Addon-BiArch.iso I'm re-running applydeltaiso to check if the corrupt ISO is created the same every time (and to rule out memory issues) and under valgrind - as suggested in an earlier post. Regards Heiko Andras Mantia wrote: >> Hi, >> >> Until now I could apply the delta ISOs without problems. Now I cannot >> create the CD1. I verified, the md5sum for the RC1-CD1 is OK, the >> md5sum for the delta-iso is OK, but after applying, the result CD is >> NOT OK, both according to applydeltaiso and a manual checking of the >> md5sum: >> >> md5sum SUSE-Linux-10.1-RC1-x86_64-CD1.iso >> 6fcd57b438477ebb90162236678ebefc SUSE-Linux-10.1-RC1-x86_64-CD1.iso >> >> md5sum SUSE-Linux-10.1-RC1_RC2-x86_64-CD1.delta.iso >> ad44f70c5eee8ee7001fce102b229899 >> SUSE-Linux-10.1-RC1_RC2-x86_64-CD1.delta.iso >> >> The result of applydeltaiso: >> md5sum mismatch, iso is corrupt >> >> Manual checking: >> md5sum SUSE-Linux-10.1-RC2-x86_64-CD1.iso >> d55dadb1b636d3fe3433a7ecb5e1dc32 SUSE-Linux-10.1-RC2-x86_64-CD1.iso >> >> It should be 47f3cf67680c0cafdf64911c0eabfc53 . >> >> Any idea what can I do? >> >> Andras >>

2 3

call for a full time "en" sysop
by jdd 08 May '06

08 May '06

It may be simpler for me to write this because I can't be a candidate :-) I think we should have a full time english-wiki sysop. Full time don't mean he will spend all his time on the wiki, but that the wiki will be his first concern. and sysop mean he will have to make strategic changes, organisation ones, not than he should have to write the wiki himself, of course. http://en.opensuse.org/index.php?title=Welcome_to_openSUSE.org&action=histo… shows that several people share the front page update. this is probably not the better way for consistency and we know they have also very sharp work do do on the distribution itself. I don't care if the sysop is Novell or voluntary, but I would like to know his name. I think also than it's his responsability, aftyer all kinds of discussions, to make the necessary changes. specially on the blocked pages, he is the only who can do it. we are simply not enough, here, to speak of democracy or votes. We don't represent anybody than ourselves. of course, Novell can (must) keep the css control. the main point is than we need a referee :-). On my concern, it's better to have a consistent layout, even if I don't like it (and why should I don't like it :-), than as many layouts as pages... jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos

1 1

Online Update during install hangs PC
by David Wright 08 May '06

08 May '06

Just a warning, currently it seems that trying to do an online update during the install causes the system to hang - on my machine it tried to download the Kernel package, but after 2 hours it was still at 0%. There doesn't seem to be a timeout on this process and all user action buttons other than help are greyed out. The only solution was to reset the machine and start the install from scratch - the update happens before any passwords have been given, so, although the machine boots to a login prompt (it doesn't start the installation process where it left off), not even the root account is accessible because it hasn't been given a password and an empty password doesn't work... I've reported this as bug 171588. I am not sure if this was a server issue, a synchronisation issue or a duff package issue, but currently if the process hangs, there is no way of proceeding with the install. -- "I got to go figure," the tenant said. "We all got to figure. There's some way to stop this. It's not like lightning or earthquakes. We've got a bad thing made by men, and by God that's something we can change." - The Grapes of Wrath, by John Steinbeck

3 2

yast2 bootloader hangs?
by Carl-Daniel Hailfinger 08 May '06

08 May '06

Hi, did anybody manage to use the yast2 bootloader module in current factory? It always hangs for me when it wants to write out the new configuration. Last y2log line is "bootloader/routines/lib_iface.ycp:271 Writing files to system" IIRC it worked well in one of the later betas. Oh well... Bug #173421 Regards, Carl-Daniel -- http://www.hailfinger.org/

1 0

Problems with prelink
by Christoph Weidmann 07 May '06

07 May '06

Hello list, I've noticed that prelinking seems to stop working beetween RC2 und RC3. I used it to minimize the time needed to start KDE (I think mainly a "placebo-effect") since 10.0. It worked with the usual messages ("could not find one of the dependecies" or something like this at a small number of files). But after upgrading to RC3, I get only messages like these for every file: " Executing /sbin/conf.d/SuSEconfig.prelink... running prelink, can take a long time .../usr/sbin/prelink: /lib/mkinitrd/bin/run-init: Could not parse `/lib/mkinitrd/bin/run-init: error while loading shared libraries: /lib/mkinitrd/bin/run-init: cannot open shared object file: Operation not permitted' /usr/sbin/prelink: /lib/udev/create_floppy_devices: Could not parse `/lib/udev/create_floppy_devices: error while loading shared libraries: /lib/udev/create_floppy_devices: cannot open shared object file: Operation not permitted' /usr/sbin/prelink: /usr/lib/YaST2/bin/elf-arch: Could not parse `/usr/lib/YaST2/bin/elf-arch: error while loading shared libraries: /usr/lib/YaST2/bin/elf-arch: cannot open shared object file: Operation not permitted' /usr/sbin/prelink: /usr/lib/YaST2/bin/md_autorun: Could not parse `/usr/lib/YaST2/bin/md_autorun: error while loading shared libraries: /usr/lib/YaST2/bin/md_autorun: cannot open shared object file: Operation not permitted' /usr/sbin/prelink: /usr/lib/YaST2/bin/startshell: Could not parse `/usr/lib/YaST2/bin/startshell: error while loading shared libraries: /usr/lib/YaST2/bin/startshell: cannot open shared object file: Operation not permitted' /usr/sbin/prelink: /usr/lib/YaST2/bin/y2base: Could not parse `/usr/lib/YaST2/bin/y2base: error while loading shared libraries: /usr/lib/YaST2/bin/y2base: cannot open shared object file: Operation not permitted' /usr/sbin/prelink: /usr/lib/YaST2/bin/y2controlcenter: Could not parse `/usr/lib/YaST2/bin/y2controlcenter: error while loading shared libraries: /usr/lib/YaST2/bin/y2controlcenter: cannot open shared object file: Operation not permitted' /usr/sbin/prelink: /usr/lib/YaST2/servers/scr: Could not parse `/usr/lib/YaST2/servers/scr: error while loading shared libraries: /usr/lib/YaST2/servers/scr: cannot open shared object file: Operation not permitted' .... .... ..." First time, I thought it could be my fault (I've messed a little bit with rebuilt SRPMs), so I've done a clean install from factory-tree this morning and the problem still occurs. Is there something known I've missed out or should I file a bug report? Greetings Christoph

1 0