openSUSE Factory July 2009

factory@lists.opensuse.org

115 participants
113 discussions

[opensuse-factory] Need to add boot message Warning about duplicate fixed IP address on subnet

by David C. Rankin

List, Moving machines between subnets yesterday, I was faced with the problem of a box completing the boot process and then hanging just before login was reached. No message, no log entry and no warnings. The only thing shown on the console was miscellaneous smb and normal nmb browse master messages but nothing concerning a duplicate IP. The conflict arose when before moving the box from subnet to subnet the last thing I did before shutting the machine down was to use yast so set the IP of the box to the new subnet. I was certain (I thought) that the assigned IP wasn't used. Several hours later when the box was started on the new subnet, thinking about a possible IP conflict was the last thing on my mind. Nevertheless, the box would not boot. To investigate I booted to repair mode and started shutting down the activation of processes in reverse order of activation to eliminate messages on the console and hopefully find out why the box wouldn't reach login. (shutting down xinetd, smb, ksysguardd, etc..) Nothing provided a glimpse of the error. (There was one obscure smb socket message that hinted at an IP conflict, but I doubt anyone other than samba developers would have clicked to the relationship) Finally, just shooting in the dark, I started yast and started picking through the settings. Somewhat on a whim, I decided to step through the network configuration again. Global, Overview and Routing were fine so I decided to edit the adapter configuration. All settings were fine. Just by chance, instead of clicking "abort" to leave the settings unchanged, I decided to click "finish" and -- Wham! -- yast issued the "Address already taken on network" error message that identified the conflict. Just exactly what yast should have done. Problem solved. In the openSuSE boot process, when the network card is activated, this same check should be performed and a message displayed and logged concerning the conflict. In its current state the boot process proceeds right through network activation without giving any indication of a conflicting IP. (I know, I watched the boot messages for the network probably 10 times during this process). The boot process needs to be smart enough to conduct this check and warn when a conflict occurs. It seems like this would just required taking the few lines of code from the yast2 card configuration check and putting it in the network activation script. Yes, I know this is just a check to protect people from their own stupidity, but that is what good software is supposed to do. I added https://bugzilla.novell.com/show_bug.cgi?id=526495 -- 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-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

12 years, 2 months

Re: [opensuse-factory] Palm Pilot module

by Fred A. Miller

Greg KH wrote: > On Thu, Jul 30, 2009 at 11:29:11AM -0400, Fred A. Miller wrote: >> Greg KH wrote: >>> On Thu, Jul 30, 2009 at 01:06:53AM -0400, Fred A. Miller wrote: >>>> Donn Washburn wrote: >>>>> On 07/29/2009 08:30 PM, Donn Washburn wrote: >>>>>> Hey group; >>>>>> >>>>>> In the past my Palm device was spotted right off by SuSE after >>>>>> installing a custom /etc/udev/rules.d file. >>>>>> Now it is not even spotted by hwinfo --usb. This brings me to my >>>>>> question. (Senior Moment) - What was the kernel module need to have >>>>>> this device seen? Something like "joliet". >>>>>> >>>>> Got it - visor and usbserial >>>>> >>>>> It is amassing how quickly a old brain comes around >>>> Sometimes. Where do I find "visor" and "usbserial" as Yast doesn't find >>>> them for 11.1? >>> They are kernel modules, not separate packages. >>> >>>> I get the error(s): >>>> >>>> 01:04:20 Starting the KPilot daemon ... >>>> 01:04:20 Daemon started. >>>> 01:04:20 Daemon status is `.kde.kpilot.daemon was not provided by any >>>> .service files' >>>> 01:04:22 Trying to open device /dev/pilot... >>>> 01:04:22 Cannot open Pilot port: [/dev/sr0]. >>>> >>>> Do you or anyone else know how to fix this? >>> press sync on your device first. >> Tried that and still get: >> >> HotSync Log >> >> 11:25:55 Starting the KPilot daemon ... >> 11:25:55 Daemon started. >> 11:25:55 Daemon status is `.kde.kpilot.daemon was not provided by any >> .service files' >> 11:25:55 Trying to open device /dev/pilot... >> 11:25:55 Cannot open Pilot port: [/dev/sr0]. >> 11:25:59 Trying to open device /dev/pilot... >> 11:25:59 Cannot open Pilot port: [/dev/sr0]. >> 11:26:04 Trying to open device /dev/pilot... >> 11:26:04 Cannot open Pilot port: [/dev/sr0]. > > Looks like kpilot needs to be configured to use the proper device node > (usually /dev/ttyUSB1 or so.) But note, it's usually better to just use > the libusb version of the pilot-link tools these days, no need to touch > the kernel drivers at all. That works much better, as the visor kernel > driver is pretty much unmaintained due to a lack of hardware (yes, it's > my code, but without hardware, I can't test it anymore...) > > Try asking on a kpilot mailing list, > > good luck, Thanks.....I'm going to need it! ;) You are correct...the system does see it, and as /dev/ttyUSB1, which of course is in /dev, bu then, neither is pilot. :( Even though the system does see it, NO software will. Thanks for trying, Fred -- Liberals ALWAYS, ALWAYS consider socialist dogma more important than telling the truth! -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

12 years, 2 months

[opensuse-factory] RPM 4.4.2.3 vs 4.7.0

by Pavol Rusnak

Hi! There is still rpm 4.4.2.3 in Factory and upstream is already at 4.7.0. Will we try to update the package for 11.2 to the newest version we can afford? Thanks for the answer! -- Best Regards / S pozdravom, Pavol RUSNAK SUSE LINUX, s.r.o openSUSE Community Multiplier Team Lihovarska 1060/12 PGP 0xA6917144 19000 Praha 9, CR prusnak[at]suse.cz http://www.suse.cz -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

12 years, 2 months

Re: [opensuse-factory] Why don't we change to cdrtools ?

by Joerg.Schilling＠fokus.fraunhofer.de

>I have just verified that bug 226019 is still a problem. With cdrecord from >home:/hennichodernich/ on 11.1 I am not able to burn a cd, unless I kill >hald-addon-storage. I could reproduce it with all LG devices that I tested. >This particular device was 'DVDRAM GSA-U10N '. This bug is a Linux kernel bug - it needs to be fixed in the Linux kernel. Cdrecord powerless if the Linux kernel reports wrong DMA sizes. If killing hald helps, then this is a really obscure side effect. BTW cdrecord does not try to do more than 62 KB of DMA by default. If you have one of the problematic USB chips that use a driver that does not allow to do more than 32 kB DMA, you always may specify ts=32k with cdrecord, cdda2wav or readcd. >Also, cdrecord from that package is installed with suid root. I am quite sure >that our security team won't like it. The solutuion used by cdrecord is no security problem as cdrecord is carefully audited. There are other security problems on suse that result from the fact that the security issue that allowed non-root applications to send SCSI commands have not beed fixed correctly. Jörg -- EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin js(a)cs.tu-berlin.de (uni) joerg.schilling(a)fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

12 years, 2 months

[opensuse-factory] Cannot install Nvidia driver(from YaST)- 11.2 M3

by upscope

I've been trying to install the Nvidia driver from YaST and the hardway. Keep getting the following dependence errors in YaST. Can anyone tell me where to find the files needed? Message #1: #### YaST2 conflicts list - generated 2009-07-30 15:54:53 #### nothing provides kernel(default:kernel_time) = 737dc055885b5e6f needed by nvidia-gfxG02-kmp-default-185.18.14_2.6.27.23_0.1-2.2.x86_64 [ ] do not install nvidia-gfxG02-kmp- default-185.18.14_2.6.27.23_0.1-2.2.x86_64 #### YaST2 conflicts list END ### and Messsage: #### YaST2 conflicts list - generated 2009-07-30 15:55:21 #### nothing provides kernel(xen:arch_x86_kernel_cpu_mtrr) = db56abf1c0bf189f needed by nvidia-gfxG02-kmp-xen-185.18.14_2.6.27.23_0.1-2.2.x86_64 [ ] do not install x11-video-nvidiaG02-185.18.14-2.2.x86_64 #### YaST2 conflicts list END ### These are the recommended drivers and worked had same error on Milestone 2 trying to install from YaST. Install the Hardway worked. Also tried to install hardway and get the following log. I do not understand the errors. I did check and gcc, make and kernel.syms are installed. Installer Log: nvidia-installer log file '/var/log/nvidia-installer.log' creation time: Thu Jul 30 16:34:43 2009 installer version: 1.0.7 option status: license pre-accepted : false update : false force update : false expert : false uninstall : false driver info : false precompiled interfaces : true no ncurses color : false query latest version : false OpenGL header files : true no questions : false silent : false no recursion : false no backup : false kernel module only : false sanity : false add this kernel : false no runlevel check : false no network : false no ABI note : false no RPMs : false no kernel module : false force SELinux : default no X server check : false no cc version check : false force tls : (not specified) force compat32 tls : (not specified) X install prefix : (not specified) X library install path : (not specified) X module install path : (not specified) OpenGL install prefix : (not specified) OpenGL install libdir : (not specified) compat32 install chroot : (not specified) compat32 install prefix : (not specified) compat32 install libdir : (not specified) utility install prefix : (not specified) utility install libdir : (not specified) doc install prefix : (not specified) kernel name : (not specified) kernel include path : (not specified) kernel source path : (not specified) kernel output path : (not specified) kernel install path : (not specified) proc mount point : /proc ui : (not specified) tmpdir : /tmp ftp mirror : ftp://download.nvidia.com RPM file list : (not specified) Using: nvidia-installer ncurses user interface -> License accepted. -> Installing NVIDIA driver version 185.19. -> There appears to already be a driver installed on your system (version: 185. 18.14). As part of installing this driver (version: 185.19), the existing d river will be uninstalled. Are you sure you want to continue? ('no' will ab ort installation) (Answer: Yes) -> No precompiled kernel interface was found to match your kernel; would you li ke the installer to attempt to download a kernel interface for your kernel f rom the NVIDIA ftp site (ftp://download.nvidia.com)? (Answer: Yes) -> No matching precompiled kernel interface was found on the NVIDIA ftp site; this means that the installer will need to compile a kernel interface for your kernel. -> Performing CC sanity check with CC="cc". -> Performing CC version check with CC="cc". -> Kernel source path: '/lib/modules/2.6.30-10-default/source' -> Kernel output path: '/lib/modules/2.6.30-10-default/build' -> Performing rivafb check. -> Performing nvidiafb check. -> Performing Xen check. -> Cleaning kernel module build directory. executing: 'cd ./usr/src/nv; make clean'... -> Building kernel module: executing: 'cd ./usr/src/nv; make module SYSSRC=/lib/modules/2.6.30-10- defau lt/source SYSOUT=/lib/modules/2.6.30-10-default/build'... NVIDIA: calling KBUILD... make CC=cc KBUILD_OUTPUT=/lib/modules/2.6.30-10-default/build KBUILD_VERBOSE =1 -C /lib/modules/2.6.30-10-default/source SUBDIRS=/tmp/selfgz3663/NVIDIA- L inux-x86_64-185.19-pkg2/usr/src/nv modules make -C /lib/modules/2.6.30-10-default/build \ KBUILD_SRC=/usr/src/linux-2.6.30-10 \ KBUILD_EXTMOD="/tmp/selfgz3663/NVIDIA-Linux-x86_64-185.19-pkg2/usr/src/nv" -f /usr/src/linux-2.6.30-10/Makefile \ modules test -e include/linux/autoconf.h -a -e include/config/auto.conf || ( \ echo; \ echo " ERROR: Kernel configuration is invalid."; \ echo " include/linux/autoconf.h or include/config/auto.conf are mis sing."; \ echo " Run 'make oldconfig && make prepare' on kernel src to fix it ."; \ echo; \ /bin/false) mkdir -p /tmp/selfgz3663/NVIDIA-Linux-x86_64-185.19- pkg2/usr/src/nv/.tmp_ver sions ; rm -f /tmp/selfgz3663/NVIDIA-Linux-x86_64-185.19- pkg2/usr/src/nv/.tm p_versions/* make -f /usr/src/linux-2.6.30-10/scripts/Makefile.build obj=/tmp/selfgz3663/ NVIDIA-Linux-x86_64-185.19-pkg2/usr/src/nv cc -Wp,-MD,/tmp/selfgz3663/NVIDIA-Linux-x86_64-185.19- pkg2/usr/src/nv/.nv. o.d -nostdinc -isystem /usr/lib64/gcc/x86_64-suse-linux/4.4/include - Iinclu de -Iinclude2 -I/usr/src/linux-2.6.30-10/include - I/usr/src/linux-2.6.30-10/ arch/x86/include -include include/linux/autoconf.h - I/tmp/selfgz3663/NVIDI A-Linux-x86_64-185.19-pkg2/usr/src/nv -D__KERNEL__ -Wall -Wundef -Wstrict- pr ototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit- fu nction-declaration -Os -m64 -mtune=generic -mno-red-zone -mcmodel=kernel - fu nit-at-a-time -maccumulate-outgoing-args -fstack-protector -fstack- protector -all -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -pipe -Wno-sign- compar e -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -Wframe-larger-than=2048 -fno- omit- frame-pointer -fno-optimize-sibling-calls -fasynchronous-unwind-tables -g - W declaration-after-statement -Wno-pointer-sign -fwrapv -fno-dwarf2-cfi-asm -I/tmp/selfgz3663/NVIDIA-Linux-x86_64-185.19-pkg2/usr/src/nv -Wall - Wimplici t -Wr eturn-type -Wswitch -Wformat -Wchar-subscripts -Wparentheses -Wpointer- arith -Wno-multichar -Werror -mcmodel=kernel -mno-red-zone -MD -Wsign-compare - Wno -cast-qual -Wno-error -D__KERNEL__ -DMODULE -DNVRM - DNV_VERSION_STRING=\"185 .19\" -UDEBUG -U_DEBUG -DNDEBUG -DMODULE -D"KBUILD_STR(s)=#s" - D"KBUILD_BAS ENAME=KBUILD_STR(nv)" -D"KBUILD_MODNAME=KBUILD_STR(nvidia)" - D"DEBUG_HASH=3 8" -D"DEBUG_HASH2=29" -c -o /tmp/selfgz3663/NVIDIA-Linux-x86_64-185.19- pkg2/ usr/src/nv/.tmp_nv.o /tmp/selfgz3663/NVIDIA-Linux-x86_64-185.19- pkg2/usr/src /nv/nv.c In file included from /usr/src/linux-2.6.30-10/include/linux/bitops.h:17, from /usr/src/linux-2.6.30-10/include/linux/kernel.h:15, from /usr/src/linux-2.6.30-10/include/linux/sched.h:52, from /usr/src/linux-2.6.30-10/include/linux/utsname.h:35, from /tmp/selfgz3663/NVIDIA-Linux-x86_64-185.19- pkg2/usr/sr c/nv/nv-linux.h:19, from /tmp/selfgz3663/NVIDIA-Linux-x86_64-185.19- pkg2/usr/sr c/nv/nv.c:14: /usr/src/linux-2.6.30-10/arch/x86/include/asm/bitops.h: In function ‘set_b it’: /usr/src/linux-2.6.30-10/arch/x86/include/asm/bitops.h:64: warning: pointer of type ‘void *’ used in arithmetic /usr/src/linux-2.6.30-10/arch/x86/include/asm/bitops.h: In function ‘clear _bit’: /usr/src/linux-2.6.30-10/arch/x86/include/asm/bitops.h:102: warning: pointer of type ‘void *’ used in arithmetic /usr/src/linux-2.6.30-10/arch/x86/include/asm/bitops.h: In function ‘chang e_bit’: /usr/src/linux-2.6.30-10/arch/x86/include/asm/bitops.h:178: warning: pointer of type ‘void *’ used in arithmetic In file included from /usr/src/linux-2.6.30-10/include/linux/utsname.h:35, from /tmp/selfgz3663/NVIDIA-Linux-x86_64-185.19- pkg2/usr/sr c/nv/nv-linux.h:19, from /tmp/selfgz3663/NVIDIA-Linux-x86_64-185.19- pkg2/usr/sr c/nv/nv.c:14: /usr/src/linux-2.6.30-10/include/linux/sched.h: In function ‘object_is_on_ stack’: /usr/src/linux-2.6.30-10/include/linux/sched.h:2126: warning: pointer of typ e ‘void *’ used in arithmetic In file included from /usr/src/linux-2.6.30-10/include/linux/dma- mapping.h:7 , from /usr/src/linux-2.6.30-10/include/asm-generic/pci-dma- c ompat.h:7, from /usr/src/linux-2.6.30-10/arch/x86/include/asm/pci.h:12 9, from /usr/src/linux-2.6.30-10/include/linux/pci.h:1110, from /tmp/selfgz3663/NVIDIA-Linux-x86_64-185.19- pkg2/usr/sr c/nv/nv-linux.h:86, from /tmp/selfgz3663/NVIDIA-Linux-x86_64-185.19- pkg2/usr/sr c/nv/nv.c:14: /usr/src/linux-2.6.30-10/include/linux/scatterlist.h: In function ‘sg_virt ’: /usr/src/linux-2.6.30-10/include/linux/scatterlist.h:199: warning: pointer o f type ‘void *’ used in arithmetic In file included from /tmp/selfgz3663/NVIDIA-Linux-x86_64-185.19- pkg2/usr/sr c/nv/nv-linux.h:113, from /tmp/selfgz3663/NVIDIA-Linux-x86_64-185.19- pkg2/usr/sr c/nv/nv.c:14: /usr/src/linux-2.6.30-10/include/linux/highmem.h: In function ‘zero_user_s egments’: /usr/src/linux-2.6.30-10/include/linux/highmem.h:149: warning: pointer of ty pe ‘void *’ used in arithmetic /usr/src/linux-2.6.30-10/include/linux/highmem.h:152: warning: pointer of ty pe ‘void *’ used in arithmetic In file included from /usr/src/linux-2.6.30-10/include/linux/compat.h:14, from /usr/src/linux-2.6.30-10/arch/x86/include/asm/mtrr.h:1 67, from /tmp/selfgz3663/NVIDIA-Linux-x86_64-185.19- pkg2/usr/sr c/nv/nv-linux.h:142, from /tmp/selfgz3663/NVIDIA-Linux-x86_64-185.19- pkg2/usr/sr c/nv/nv.c:14: /usr/src/linux-2.6.30-10/arch/x86/include/asm/compat.h: In function ‘compa t_alloc_user_space’: /usr/src/linux-2.6.30-10/arch/x86/include/asm/compat.h:210: warning: pointer of type ‘void *’ used in arithmetic /tmp/selfgz3663/NVIDIA-Linux-x86_64-185.19-pkg2/usr/src/nv/nv.c: In function ‘nvos_proc_create’: /tmp/selfgz3663/NVIDIA-Linux-x86_64-185.19-pkg2/usr/src/nv/nv.c:591: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /tmp/selfgz3663/NVIDIA-Linux-x86_64-185.19-pkg2/usr/src/nv/nv.c:592: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /tmp/selfgz3663/NVIDIA-Linux-x86_64-185.19-pkg2/usr/src/nv/nv.c:593: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /tmp/selfgz3663/NVIDIA-Linux-x86_64-185.19-pkg2/usr/src/nv/nv.c:613: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /tmp/selfgz3663/NVIDIA-Linux-x86_64-185.19-pkg2/usr/src/nv/nv.c:627: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /tmp/selfgz3663/NVIDIA-Linux-x86_64-185.19-pkg2/usr/src/nv/nv.c:638: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /tmp/selfgz3663/NVIDIA-Linux-x86_64-185.19-pkg2/usr/src/nv/nv.c:648: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /tmp/selfgz3663/NVIDIA-Linux-x86_64-185.19-pkg2/usr/src/nv/nv.c:658: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /tmp/selfgz3663/NVIDIA-Linux-x86_64-185.19-pkg2/usr/src/nv/nv.c:669: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /tmp/selfgz3663/NVIDIA-Linux-x86_64-185.19-pkg2/usr/src/nv/nv.c:676: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /tmp/selfgz3663/NVIDIA-Linux-x86_64-185.19-pkg2/usr/src/nv/nv.c: In function ‘nvos_proc_add_warning_file’: /tmp/selfgz3663/NVIDIA-Linux-x86_64-185.19-pkg2/usr/src/nv/nv.c:703: error: ‘struct proc_dir_entry’ has no member named ‘owner’ make[4]: *** [/tmp/selfgz3663/NVIDIA-Linux-x86_64-185.19- pkg2/usr/src/nv/nv. o] Error 1 make[3]: *** [_module_/tmp/selfgz3663/NVIDIA-Linux-x86_64-185.19- pkg2/usr/sr c/nv] Error 2 make[2]: *** [sub-make] Error 2 NVIDIA: left KBUILD. nvidia.ko failed to build! make[1]: *** [module] Error 1 make: *** [module] Error 2 -> Error. ERROR: Unable to build the NVIDIA kernel module. ERROR: Installation has failed. Please see the file '/var/log/nvidia-installer.log' for details. You may find suggestions on fixing installation problems in the README available on the Linux driver download page at www.nvidia.com. I logged in as root at level 3. Is it possible I missed a step? I used the hardway on M2 and everything worked fine. Should this be reported at opensuse (Bugzilla) or Nvidia's bug reporting? Thanks for any assistance. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

12 years, 2 months

[opensuse-factory] Re: [opensuse-kernel] Backporting 2.6.30?

by AndiSugandi™

On Sun, Jul 26, 2009 at 1:08 AM, Markus Koßmann<mkossmann_ml1(a)gmx.de> wrote: > Just try it. I'am running 3.6.30 kernels on 11.1 for some time now without > problems. Most error messages are caused by a configuration change. The > driver is no longer build as module but compiled into the kernel. I'm using this kernel on openSUSE 11.1 too but have a problem, it won't boot until I disable acpi module to be looded at grub menu (acpi=off). The boot log looks like this: [ 10.361694] acer-wmi : Acer Laptop ACPI-WMI Extras [ 10.373790] Kernel Panic - not syncing: stack-protector: kernel stack is corrupted in: 4845ca0e ...bla bla bla [ 10.623049] [cffffe424] 0xffffe424 <- #at this line, kernel booting stopped. Notes: > uname -r 2.6.30.2-4-default but has different kernel-source version as in "Kernel:/HEAD/openSUSE_Factory" repository: ls -l /usr/src/linux lrwxrwxrwx 1 root root 16 2009-07-26 15:51 /usr/src/linux -> linux-2.6.30.2-6 rpm -qa | grep kernel-source kernel-source-2.6.30.2-6.1 My box is Acer Aspire 5620: http://www1.dealtime.co.uk/xPF-Acer-ACER-AS5622WLMI-050 Should I file the bug? Because it happened similar when I tried to install openSUSE 11.2 Milestone 3-Live CD KDE4 on the same machine (stopped booting with the same error boot log, and could not reach GUI even it booted with acpi=off enabled). Or I should do some more workaround? Btw, I'm new here, and glad to discuss with many experts of my favorite Linux distribution. TIA. Best regards, Andi S. -- AndiSugandi™ is andi.opensuse-id.org -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

12 years, 2 months

[opensuse-factory] 11.2m4 live installer does not ask for root password

by Rolf Offermanns

Hi All, I just did a fresh 11.2m4 install inside VirtualBox using the KDE4 Live CD and I was not asked for a root password. Since I was not 100% focused on the installation I repeated it in a second VM. Same result. Am I missing something? Do the Live CDs have a default password? I tried "root", "linux", <empty> without success... Thanks, Rolf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

12 years, 2 months

[opensuse-factory] Making restricted codecs installation easier for 11.2

by Atri

It will be really nice if 11.2 implements an easier way of installing restricted multimedia codecs than that exists currently. The current way of doing it via one-click installation is somewhat more complicated than ubuntu's codec installer. In my opinion, the entire process could easily be done via a script that runs a terminal showing a warning about the usage of restricted codecs requiring user-interaction, then calls zypper to add the Packman repo and installs/updates the required multimedia packages from that repo. Of course there may exist several better ways than what I suggest, but it would be worthwhile to explore methods of installing codec support that make it much easier for a complete newcomer. In any case this is probably one of the first things a home user does, so the ease with which it can be done does influence his/her opinion about the distribution somewhat. -- Atri -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

12 years, 2 months

Re: [opensuse-factory] Why don't we change to cdrtools ?

by Joerg.Schilling＠fokus.fraunhofer.de

>Free software wants to be patched. Sorry. Good free software does not need to be patched - it works out of the box like cdrtools do. There are a few cases where cdrtools have problems and these cases are caused by Linux kernel bugs or Linux hald implementation/design bugs. Jörg -- EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin js(a)cs.tu-berlin.de (uni) joerg.schilling(a)fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

12 years, 2 months

Re: [opensuse-factory] Why don't we change to cdrtools ?

by Joerg.Schilling＠fokus.fraunhofer.de

>Is there a way we can fix this without patching cdrtools ? If you like to fix a kernel problem, you need to fix the kernel. The linux kernel has a very idiosyncratic interface for setting/retrieving the DMA size for SCSI transfers. I did never like this idiosyncratic interface but I followed it's definitions. Now it's time for the Linux kernel to correctly follow it's own interface definitions. Jörg -- EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin js(a)cs.tu-berlin.de (uni) joerg.schilling(a)fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

12 years, 2 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

openSUSE Factory July 2009