February 2008 - openSUSE Users - openSUSE Mailing Lists

[opensuse] 11.0 A2
by Ken Schneider 09 Feb '08

09 Feb '08

First impressions. Fresh install on real machine went smoothly on one machine but trying to upgrade an 11.0A1 VirtualBox install failed to upgrade even one package. No errors occurred it just seemed to skip the part where software would be selected. Since KDE 4 is the default KDE version installed and it is still fairly new there are numerous bugs that I hope are worked out before the GM release. But then that is why I am testing on spare hardware, to help find the bugs. It also appears that the KDE devs are taking lessons from the gnome devs where less control is better. The number of options available for config in the control panel is far less then what I would expect based on past experience. This could be setup as a choice: beginner == fewer options presented, advanced == more config options presented. On freshly installed machine my Logitech wheel mouse is not recognized. Even after adding the appropriate info in xorg.conf. Re-sizing any window larger in the KDE desktop requires a click in the missing portion to make it visible. Launching KDE apps from the menu (or via alt-f2 popup) causes a SIGSEGV error to pop up but they run from the command line. More info (and bug reports opened) as I continue to test. Bottom line: keep up the great work as I think this will end up as a very good version, not great (because of the KDE4 bugs that will persist. But that is to be expected when you have a major UI change. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] openSuse 11 Alpha
by Vahe Avedissian 09 Feb '08

09 Feb '08

Folks, If I install openSUSE 11 alpha, will I get regular updates through YOU and will it eventually update itself to openSUSE 11 rc1, or would I still need to do a fresh install once rc1 is out? Vahe ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

3 2

[opensuse] installation via IPv6
by Hans Witvliet 09 Feb '08

09 Feb '08

Hi all, Could it be that during installation IPv6 is not enabled? At work aswell as at home i've my own installation-server / gwdg-mirror. Identical setup, but at home i use for all my vhosts an V6 address. After a system is installed, i can upgrade or add aditional repo's without any problem with my IPv6 servers. However during the initial installation the installation source coming froman IPv6 address are not recognised. If i perform a DVD-installation, just before the first boot, i saw that the module "ipv6" is not loaded. I presume this could be the reason. Any suggestions how i can load this module in grub before installation takes place, so that i can add my own installationsources? Hans -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 1

[opensuse] Unable to download list of online reprositories
by Wael Showair 09 Feb '08

09 Feb '08

hi all, first of all i m happy to participate in opensuse mailing list. this is my first post. i m using 10.3 64 bit when i click on yast -->Community Reprositories there are 3 steps should be done: 1. Check Network Configuration 2. Download list of online reprositories 3. Inialize the reprository manager my problem appears in step 2 where i have got the following message: Unable to download list of reprositories or no reprositories defined why this happens i dont know? note that i add NON-OSS reprository during Installation then after i finished installation i added the OSS reprository by clicking yast --> Community Reprositories? is there any way to get out of this problem since i want to add new reprositories to install from them new packages thanks in advance -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

Re: [opensuse] openSuSe 10.3 hangs after kernel update
by Vahe Avedissian 09 Feb '08

09 Feb '08

I booted from the 64b installation DVD and chose boot installed system, and that only tried to boot the "bad" kernel (i.e. system hangs with same errors). I tried doing update system but that did not quit ego well. Can I even "update" a very current 10.3 to the initial 10.3 DVD kernel level? Sounds like that may not work either. I think I need to install a working kernel from scratch. I see openSuSE released a new kernel two days back... Given I cannot boot to this machine what is the best way to install a new kernel? I can boot using a live DVD (openSuSE Ubuntu, etc...) and try to compile the kernel and then copy it to the 10.3 kernel directory, but I am not sure this approach will work. I notice yast did not save my old kernels so I cannot edit grub's menu.lst to use an older working kernel. Is there a way to configure yast to not delete an old kernel when a new one is installed? Giving I update to this non-function kernel using yast, I am still not clear why I seem to have ended up with the wrong kernel. How do I protect from this happening again? Thanks, Vahe ----- Original Message ---- From: David C. Rankin <drankinatty(a)suddenlinkmail.com> To: suse <opensuse(a)opensuse.org> Sent: Monday, February 4, 2008 10:48:00 AM Subject: Re: [opensuse] openSuSe 10.3 hangs after kernel update Jan Ritzerfeld wrote: > Am Montag, 4. Februar 2008 schrieb Vahe Avedissian: > >> I just used YaST to update to the latest kernel (vmlinuz-2.6.22.16-01). I >> am running openSuSE x64 (AMD) and my machine now hangs early during the >> boot process with the following message repeated several times: >> >> request_module: runaway loop modprobe binfmt-464c >> >> I googled this and all I could find was either 32bie ELF file on an x64 >> bit machine, or a bad/incompatible disk controller driver. > > For me, your problem looks like > https://bugzilla.novell.com/show_bug.cgi?id=333689 > >> I suspect the install did not go correctly. What is the best way to back >> off or undo the kernel update and revert to the > > The easiest way would be to boot from the 64 bit installation DVD. Then, > select the grub menu item "Boot Installed System". If this works, you will > be able to re-install the correct x86_64 kernel by simply using YaST. > > HTH > Jan All of the old kernels are contained in the /updates repository. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org ____________________________________________________________________________________ Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

5 6

[opensuse] Warning - 10.3/XGL repository has compiz/emerald version mismatch
by David C. Rankin 09 Feb '08

09 Feb '08

Listmates, If you upgrade compiz from yast->software management with the X11/XGL repository at present, you will break compiz due to a RPM version mismatch between compiz and emerald. 15:21 rankin-p35a~> rpm -qa | grep compiz compiz-0.7.0-5.1 ^^^^^^^^^ compiz-emerald-0.6.9_git071204-1.4 ^^^^^^^^^^^^^^^^^^^ With the update to compiz 0.7.0-5.1, compiz-emerald and emerald-themes will completely stop working. From the compiz list: "The decoration protocol version was changed. You need to recompile your emerald copy with the new headers (or wait for your packagers to have done so)" So packagers -- How goes it? -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

3 5

Re: [opensuse] 10.3 and powermanagement
by Hans Petter Jansson 09 Feb '08

09 Feb '08

On Sun, 2008-01-13 at 18:17 -0600, John E. Perry wrote: > Hans Petter Jansson wrote: > > I guess this is a bit offtopic, but have you tried the GNOME Power > > Manager? It creates dynamic battery profiles through statistical > > sampling. Seems to work pretty well. Pretty graphs too :) > I didn't know about it. I tried gnome early on, but it simply was > nowhere near KDE's level of function and ease of use, so I haven't paid > a lot of attention to it since then. As I understand it, much of gnome > works under KDE, too, so I could certainly give it a try. Do you know > offhand if it works well under KDE? I haven't tried it, but I can't see any immediate reason why it would'nt. The package name is "gnome-power-manager", and you can start it from the command line using that same string. It should pop up an icon with both right- and left-click menus in the system tray. -- Hans Petter -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

5 7

[opensuse] what happened to smbmount
by David Bear 08 Feb '08

08 Feb '08

In older versions of Suse, smbmount was included in the samba packages. Now I can't find it anywhere. I know I can use konqueror and create network connections to smb resources, but I like the more generalized nature of smbmount. Anyone know where smbmount is -- or how to get it (short of removing the suse samba rpms and installing samba from scratch)? -- David Bear College of Public Programs/ASU 411 N Central, Phoenix, AZ 85004 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

5 6

[opensuse] [Feature Request] Splitting of kernel-sources for easier download and module builds
by Sunny 08 Feb '08

08 Feb '08

Hi, I have opened a case in bugzilla: https://bugzilla.novell.com/show_bug.cgi?id=360026 It is about splitting the kernel-sources package (250MB) into 2 parts - one with the prepared "includes" - about 24MB, and the rest of the source tree, as only a "prepared" include files are required if one needs to build a custom kernel module - i.e. for vmware-tools, or vmware-server, or some new hardware, which has OSS driver, but it is not yet in the main kernel, or the corresponding vendor insists in providing their own driver, which is not OOS. I agree, that we have to (and I do) pursue the vendors, but meanwhile it's going to save me (us) a lot of downloads and hdd space, as well as a lot of bandwidth on opensuse servers. Ubuntu are using this approach, and it's much easier there in that regard. Please, review the case, and vote for it if you support my opinion. Cheers and have nice weekend. -- Svetoslav Milenov (Sunny) Even the most advanced equipment in the hands of the ignorant is just a pile of scrap. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] Mayday! - /dev/mapper now points to /dev/sda instead of sdb and sdc in raid 1
by David C. Rankin 08 Feb '08

08 Feb '08

Listmates, Help! Production box is down and I need help. Problem: For some reason, the 10.3 server went down last night. Today, on boot, the system points /boot, /, and /home to all to /dev/sda instead of software raid1 (sdb and sdc) and will not boot. /sda/fails fsck check (obviously) and I am left in maintenance mode and I don't know how to point the /dev/mapper back to md0, md1 and md2 that contain the proper /boot, /, and /home. I have 2 kernel installed on the box after installing the latest kernel with rpm -ivh. Both the 2.6.22.13-0.3-default and 2.6.22.16-0.2-default kernels were working fine. Both now experience the exact same problem when trying to boot, so it isn't a kernel install issue. Prior to this problem we were working an initrd issue that thankfully caused me to save all of the boot configuration files and post them as part of: https://bugzilla.novell.com/show_bug.cgi?id=357725 Here are the relevant pre-failure files are: 17:11 bonza~> cat /etc/fstab /dev/mapper/nvidia_haheegdb_part2 / ext3 acl,user_xattr 1 1 /dev/mapper/nvidia_haheegdb_part1 /boot ext3 acl,user_xattr 1 2 /dev/mapper/nvidia_haheegdb_part3 /home ext3 acl,user_xattr 1 2 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 /dev/sda1 /data ext3 acl,user_xattr 1 2 /dev/disk/by-id/scsi-SATA_Maxtor_5T020H2_T2H34J2C-part2 swap swap defaults 0 0 17:09 bonza~> df Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/nvidia_haheegdb_part2 20641788 6952760 12640388 36% / udev 1038168 120 1038048 1% /dev /dev/mapper/nvidia_haheegdb_part1 69972 20647 45712 32% /boot /dev/mapper/nvidia_haheegdb_part3 219648612 18501700 189989368 9% /home /dev/sda1 17551956 176200 16484152 2% /data 17:10 bonza~> mount /dev/mapper/nvidia_haheegdb_part2 on / type ext3 (rw,acl,user_xattr) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) debugfs on /sys/kernel/debug type debugfs (rw) udev on /dev type tmpfs (rw) devpts on /dev/pts type devpts (rw,mode=0620,gid=5) /dev/mapper/nvidia_haheegdb_part1 on /boot type ext3 (rw,acl,user_xattr) /dev/mapper/nvidia_haheegdb_part3 on /home type ext3 (rw,acl,user_xattr) /dev/sda1 on /data type ext3 (rw,acl,user_xattr) securityfs on /sys/kernel/security type securityfs (rw) 9:17 root@bonza:/boot # l /dev/mapper/ total 0 drwxr-xr-x 2 root root 140 2008-02-05 17:19 ./ drwxr-xr-x 10 root root 6640 2008-02-05 17:19 ../ lrwxrwxrwx 1 root root 16 2008-02-05 17:19 control -> ../device-mapper brw------- 1 root root 253, 0 2008-02-05 17:19 nvidia_haheegdb brw------- 1 root root 253, 1 2008-02-05 17:19 nvidia_haheegdb_part1 brw------- 1 root root 253, 2 2008-02-05 17:19 nvidia_haheegdb_part2 brw------- 1 root root 253, 3 2008-02-05 17:19 nvidia_haheegdb_part3 When I now access all files in maintenance mode, all files are still the same. What changed is when I do a df, now all of the /dev/mapper/nvidia_haheegdb_part1 /dev/mapper/nvidia_haheegdb_part2 /dev/mapper/nvidia_haheegdb_part3 show that they are all pointing to /dev/sda the 20G drive that only contains swap and not the correct 250G raid1 array comprised of /dev/sdb and /dev/sdc that contains /boot, / and /home. cat /proc/partitions show all of the proper partitions for sda, sdb, sdc and md are all still there and listed as partitions. What in the world could have gone wrong?? Where I am lost is dealing with maintenance mode to fix this. /boot is unmounted so I don't know how to go look at grub/device.map to see what is screwed up and I am not that good with maintenance mode to begin with. I really, really need some good help from the list on this one. Thank you in advance to whoever can reply! I am dead in the water and sweating it out right now. (I do have all data backed up....) -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 4