April 2008 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] ext3
by Peter Czanik 23 Apr '08

23 Apr '08

Hello, Up to beta1, firmware of Genesi PPC machines (Pegasos & EFIKA) could list content of ext3 partitions and boot from them. With beta1 use of ext3 filesystems is no more possible from the firmware. Looking at the output of dumpfs (see below), only one feature seems to be added between older factory releases and beta1: needs_recovery Is there any way to turn it off during installation? Bye, CzP Olaf Hering írta: >> What changed in file system creation with beta1? All the previous alpha & >> factory releases worked fine, I mean the firmware had no problem reading >> the ext3 partition formatted during installation. With beta1 this changed, >> the firmware can't list it any more... >> > Maybe a new e2fsprogs, which enables or uses more ext3 features. > Better ask on the factory list, if the feature list of mke2fs or the > config file changed. > openSUSE 10.3 linux:~ # dumpe2fs -h /dev/sda8 | grep -i fea dumpe2fs 1.40.8 (13-Mar-2008) Filesystem features: has_journal resize_inode dir_index filetype sparse_super large_file openSUSE 11.0 beta1 linux:~ # dumpe2fs -h /dev/sda10 | grep -i fea dumpe2fs 1.40.8 (13-Mar-2008) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file openSUSE factory before beta1 linux:~ # dumpe2fs -h /dev/sda11 | grep -i fea dumpe2fs 1.40.8 (13-Mar-2008) Filesystem features: has_journal ext_attr resize_inode dir_index filetype sparse_super large_file --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 3

[opensuse-factory] NetworkManager: <WARN> Couldn't get connection secrets: dbus-settings.c.108 - Connection's plugin did not return a secrets hash
by James PEARSON 23 Apr '08

23 Apr '08

Hello all ################################ # wifi connection problem ################################ I installed Beta 1 DVD on T60 Thinkpad, Core Duo Post boot my wifi Essid "Mercury" (wlan0) WPA connection is KO using an Intel Wifi(3945abg) card ################################ # My analyse ################################ dmesg states "wlan0: disassociate(reason=3)" which means "Station has left the basic service area or extended service area and is deauthenticated". Why is this error happening at this point ? IMHO NetworkNetworkManger log suggests that the reason is that NetworkManager "Couldn't get connection secrets: dbus-settings.c.108 - Connection's plugin did not return a secrets hash.." More details follow... ################################ # dmesg gives ################################ ADDRCONF(NETDEV_UP): wlan0: link is not ready NET: Registered protocol family 17 wlan0: Initial auth_alg=0 wlan0: authenticate with AP 00:17:33:98:2c:3c wlan0: RX authentication from 00:17:33:98:2c:3c (alg=0 transaction=2 status=0) wlan0: authenticated wlan0: associate with AP 00:17:33:98:2c:3c wlan0: RX AssocResp from 00:17:33:98:2c:3c (capab=0x401 status=0 aid=1) wlan0: associated wlan0: switched to short barker preamble (BSSID=00:17:33:98:2c:3c) ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready wlan0: Initial auth_alg=0 wlan0: authenticate with AP 00:17:33:98:2c:3c wlan0: RX authentication from 00:17:33:98:2c:3c (alg=0 transaction=2 status=0) wlan0: authenticated wlan0: associate with AP 00:17:33:98:2c:3c wlan0: RX AssocResp from 00:17:33:98:2c:3c (capab=0x401 status=0 aid=1) wlan0: associated wlan0: disassociate(reason=3) wlan0: disassociate(reason=3) ################################ # dmesg analyse ################################ "wlan0: disassociate(reason=3)" means "Station has left the basic service area or extended service area and is deauthenticated". Why is this error happening at this point ? NetworkManger log would suggests that the reason is that NetworkManager "Couldn't get connection secrets: dbus-settings.c.108 - Connection's plugin did not return a secrets hash.." ################################ NetworkManger log on boot lists ################################ NetworkManger log on boot lists Apr 22 19:28:38 linux NetworkManager: <info> Trying to start the system settings daemon... Apr 22 19:28:42 linux NetworkManager: <info> Bringing up device eth0 Apr 22 19:28:42 linux NetworkManager: <info> Deactivating device eth0. Apr 22 19:28:42 linux NetworkManager: <info> Bringing up device wlan0 Apr 22 19:28:42 linux NetworkManager: <info> Deactivating device wlan0. Apr 22 19:28:42 linux NetworkManager: <info> (wlan0) supplicant interface is now in state 2 (from 1). Apr 22 19:28:44 linux NetworkManager: <info> Activation (wlan0) starting connection 'System Mercury (wlan0)' Apr 22 19:28:44 linux NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Apr 22 19:28:44 linux NetworkManager: <info> (wlan0) Supplicant interface state change: 1 -> 4 Apr 22 19:28:44 linux NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Apr 22 19:28:44 linux NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Apr 22 19:28:44 linux NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Apr 22 19:28:44 linux NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Apr 22 19:28:44 linux NetworkManager: <info> Activation (wlan0/wireless): access point 'System Mercury (wlan0)' has security, but secrets are required. Apr 22 19:28:44 linux NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Apr 22 19:28:44 linux NetworkManager: <WARN> get_secrets_cb(): Couldn't get connection secrets: dbus-settings.c.108 - Connection's plugin did not return a secrets hash.. Apr 22 19:28:44 linux NetworkManager: <info> Activation (wlan0) failed for access point (Mercury) Apr 22 19:28:44 linux NetworkManager: <info> Marking connection 'System Mercury (wlan0)' invalid. Apr 22 19:28:44 linux NetworkManager: <info> Activation (wlan0) failed. Apr 22 19:28:44 linux NetworkManager: <info> Deactivating device wlan0. ############### # Other info ############### linux:~ # uname -a Linux linux 2.6.25-rc9-17-pae #1 SMP 2008-04-15 22:54:53 +0200 i686 i686 i386 GNU/Linux linux:~ # lsmod | grep 3945 iwl3945 108504 0 firmware_class 25984 3 microcode,pcmcia,iwl3945 mac80211 238820 1 iwl3945 led_class 21764 1 iwl3945 cfg80211 43784 2 iwl3945,mac80211 lspci | grep -i 3945 03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) rpm -qa | grep -i Net | sort NetworkManager-0.7.0.r3556-4 NetworkManager-glib-0.7.0.r3556-4 NetworkManager-kde-0.7r795810-5 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 1

[opensuse-factory] Deploying installation images?
by Per Jessen 22 Apr '08

22 Apr '08

It's no doubt my fault for not keeping up with progress here, but can anyone explain to me what happens during installation (BETA1) when YaST say 'Deploying installation images' ? /Per Jessen, Zürich --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 10

[opensuse-factory] update-mime-database fails
by Jackintus 22 Apr '08

22 Apr '08

zypper dup ... Downloading package MozillaFirefox-2.9.95-6.i586, 844.0 K (3.0 M unpacked) * Downloading: MozillaFirefox-2.9.95-6.i586.rpm [done (205.0 K/s)] * Installing: MozillaFirefox-2.9.95-6 Installation of MozillaFirefox-2.9.95-6 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: error: failed to stat /home/jack/.gvfs: Permission denied Usage: usr/bin/update-mime-database [-hvV] MIME-DIR No directories in update-desktop-database search path could be processed and updated. error: %postun(MozillaFirefox-2.0.0.12-5.3.i586) scriptlet failed, exit status 1 Usage: usr/bin/update-mime-database [-hvV] MIME-DIR No directories in update-desktop-database search path could be processed and updated. error: %postun(MozillaFirefox-2.0.0.12-5.4.i586) scriptlet failed, exit status 1 Bug 381735 Regards --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

6 10

[opensuse-factory] openSUSE 11.0 Beta 1 release?
by Terje J. Hanssen 21 Apr '08

21 Apr '08

I thought to start to help with testing out openSUSE 11.0, but had a broken installation attempt with Alpha 3 this week. I could't wait and installed 10.3 instead. The Roadmap for 11.0 told however http://en.opensuse.org/Roadmap/11.0 Thu, Apr 17 openSUSE 11.0 Beta 1 release Thu, Apr 24 openSUSE 11.0 Beta 1+ release As I can't find that Beta 1 is released yet, I wonder if there has been announced some delays in this release schedule? Cheers, Terje J. hanssen --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

18 30

[opensuse-factory] Zypper enhancement request.
by Oddball 21 Apr '08

21 Apr '08

Hi, As i lost my Yast2 repomngr, i wanted to disable some repos using zypper. Helas the options: enablerepo, er, and disablerepo, dr, do not exist. > repos, lr List all defined repositories. > addrepo, ar Add a new repository. > removerepo, rr Remove specified repository. > renamerepo, nr Rename specified repository. > modifyrepo, mr Modify specified repository. > refresh, ref Refresh all repositories. I tried to disable the repos using mr, but 'nothing to modify on repo <name repo>' was the answer... Is there an exact command to 'edit' the repos? switch off/on?, without totaly removing them? -- Enjoy your time around, Oddball (Now or never...) OS: Linux 2.6.25-rc8-12-default x86_64 Current user: oddball@AMD64x2-sfn1 System: openSUSE 11.0 (x86_64) Alpha3 KDE: 4.00.68 (KDE 4.0.68 >= 20080402) "release 6.4" --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 11

[opensuse-factory] My zypper can not download
by Carlos E. R. 21 Apr '08

21 Apr '08

Hi, zypper can not download and install anything (Yast also fails): minas-morgul:~ # zypper dup Download (curl) error for 'ftp://ftp5.gwdg.de/pub/opensuse/distribution/SL-Facto ry-non-oss/inst-source-extra/content': Error code: Connection failed Error message: Resolving host timed out: ftp5.gwdg.de Abort, retry, ignore? [A/r/i]: i Download (curl) error for 'ftp://ftp5.gwdg.de/pub/opensuse/distribution/SL-OSS-factory/inst-source/content': Error code: Connection failed Error message: Resolving host timed out: ftp5.gwdg.de There is nothing wrong with dns, network, or repository: minas-morgul:~ # wget ftp://ftp5.gwdg.de/pub/opensuse/distribution/SL-OSS-factory/inst-source/content --16:58:17-- ftp://ftp5.gwdg.de/pub/opensuse/distribution/SL-OSS-factory/inst-source/content => `content.1' Resolving ftp5.gwdg.de... 134.76.12.5 Connecting to ftp5.gwdg.de|134.76.12.5|:21... connected. Logging in as anonymous ... Logged in! ==> SYST ... done. ==> PWD ... done. ==> TYPE I ... done. ==> CWD /pub/opensuse/distribution/SL-OSS-factory/inst-source ... done. ==> PASV ... done. ==> RETR content ... done. Length: 18,733 (18K) (unauthoritative) 100%[=====================================================================>] 18,733 52.00K/s 16:58:19 (51.77 KB/s) - `content.1' saved [18733] -- Cheers / Saludos, Carlos E. R. (from 10.3-RC2) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 3

[opensuse-factory] Re: [opensuse-announce] Announcing openSUSE 11.0 Beta 1
by Andreas Jaeger 21 Apr '08

21 Apr '08

Henne wrote the following, let me sent it now on his behalf: Hello Users: There is a Bug which affects the adding of system users in the following packages: aaa_base avahi beagle cups dbus-1 festival fuse gdm hal ntp openssh PolicyKit postfix pulseaudio pwdutils samba scrollkeeper uuid-runtime You have to reinstall them to get the correct users created on your system. You can do so either in YaST or use zypper for i in aaa_base avahi beagle cups dbus-1 festival fuse \ gdm hal ntp openssh PolicyKit postfix pulseaudio pwdutils \ samba scrollkeeper uuid-runtime; \ do rpm -q $i && echo zypper in -f $i; done For details see also the most annoying bugs for 11.0: http://en.opensuse.org/Bugs:Most_Annoying_Bugs_11.0_dev Hope this works and is helpfull, Andreas -- Andreas Jaeger, Director Platform / openSUSE, aj(a)suse.de SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

3 2

[opensuse-factory] LILO and "read-only" flag
by Eberhard Moenkeberg 21 Apr '08

21 Apr '08

Hi, After update of 10.3 i386 to 11.0-Beta1, LILO's "read-only" flag does not work properly. The / filesystem gets mounted read-only first (to allow fsck), but it does not get remounted r/w later. Eliminating LILO's "read-only" flag cures it, but that can only be a temporary workaround. Viele Grüße Eberhard Mönkeberg (emoenke(a)gwdg.de, em(a)kki.org)

3 3

[opensuse-factory] beta1 live-cd mayhem: no initrd
by Silviu Marin-Caea 21 Apr '08

21 Apr '08

I have installed the system using the KDE4-LiveCD of beta1. The initrd has not been generated, there's only a orphaned symlink to it. I've booted up the LiveCD again and I'm trying to generate the initrd manually, but I forgot what needs to be done to create the device files in the chroot environment. I knew that before, but I forgot and can't think of a way to formulate the Google search. Thanks. Boot Live-CD, then: linux:~ # mkdir /tmp/local linux:~ # mount /dev/sda4 /tmp/local linux:~ # chroot /tmp/local linux:/> mkinitrd Kernel image: /boot/vmlinuz-2.6.25-rc9-17-default Initrd image: /boot/initrd-2.6.25-rc9-17-default node name not found /dev/sda4: error opening volume Root device (/dev/sda4) not found ReadPartitions(): Failed to open dir /sys/block at /usr/lib/perl5/vendor_perl/5.10.0/Bootloader/Tools.pm line 280. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 1