Re: [opensuse-factory] 21/12/07, Many unsatisfied deps, when zypper dup.
Am Freitag, 21. Dezember 2007 schrieb M9.: > Hi, > > I am looking for yast to be repaired, but it is nearly impossible to > update now, every solution causes another problem atm. > Does anyone know a solution for the Yast2 problem? > After the update yesterday, it does not show when called upon. > even the dos-version does not respond. > > [EMAIL PROTECTED]:~> rpm -qa | grep yast2 > yast2-storage-lib-2.16.6-7 > yast2-pam-2.16.0-24 > yast2-control-center-2.16.0-7 > yast2-backup-2.16.1-3 > yast2-ldap-client-2.16.5-3 > yast2-metapackage-handler-0.7.3-13 > yast2-qt-2.16.9-2 > yast2-pkg-bindings-2.16.7-2 > yast2-firewall-2.15.8-35 > yast2-x11-2.15.11-56 > yast2-printer-2.16.6-7 > yast2-registration-2.16.0-15 > yast2-nis-client-2.16.0-23 > yast2-samba-server-2.16.0-27 > autoyast2-2.16.3-3 > yast2-trans-nl-2.15.12-2 > yast2-slp-2.15.0-59 > yast2-control-center-qt-2.16.0-7 > yast2-bootloader-2.16.3-3 > autoyast2-installation-2.16.3-3 > yast2-hardware-detection-2.16.0-7 > yast2-2.16.18-3 > yast2-irda-2.15.1-122 > yast2-scanner-2.15.5-70 > yast2-ldap-2.15.1-108 > yast2-sound-2.16.1-17 > yast2-kerberos-client-2.16.1-3 > yast2-security-2.15.1-52 > yast2-repair-2.16.2-14 > yast2-tune-2.15.7-51 > yast2-users-2.16.5-3 > yast2-sudo-2.15.3-118 > yast2-update-2.16.1-15 > yast2-trans-stats-2.15.0-46 > yast2-country-data-2.16.4-3 > yast2-core-2.16.16-2 > yast2-nfs-client-2.15.0-52 > yast2-mouse-2.16.0-13 > yast2-ncurses-2.16.7-3 > yast2-xml-2.16.0-10 > yast2-apparmor-2.1-54 > yast2-support-2.15.3-42 > yast2-storage-2.16.6-7 > yast2-ntp-client-2.16.2-9 > yast2-tv-2.16.0-27 > yast2-fingerprint-reader-2.16.2-3 > yast2-installation-2.16.8-2 > yast2-restore-2.16.0-15 > yast2-add-on-2.16.0-22 > yast2-inetd-2.15.1-72 > yast2-perl-bindings-2.16.0-29 > yast2-transfer-2.16.0-4 > yast2-bluetooth-2.15.4-46 > yast2-sysconfig-2.15.3-85 > yast2-packager-2.16.12-3 > yast2-online-update-2.16.6-3 > yast2-network-2.16.17-3 > yast2-samba-client-2.16.1-13 > yast2-mail-2.15.23-34 > yast2-control-center-gnome-2.13.2-127 > yast2-schema-2.15.0-156 > yast2-theme-openSUSE-2.16.1-2 > yast2-runlevel-2.16.0-15 > yast2-country-2.16.4-3 > yast2-iscsi-client-2.16.2-9 > yast2-online-update-frontend-2.16.6-3 > yast2-profile-manager-2.16.0-14 > [EMAIL PROTECTED]:~> > > Anyone sees something out of order here? I've basically the same versions and the ncurses interface worked for me. The current dependency problem seems to be that there is a update to openldap-2.4 but there are still many packages , which have dependencies on libldap-2.3/liblber-2.3 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Problems with yast2
Am Donnerstag, 20. Dezember 2007 schrieben Sie: > Hi, > > Sorry only replying now; I have this email account from college, and > that's what I use regularly now. > > Is this resolved? It doesn't seem UI related, but there is an easy way > to isolate the problem. Do the following work for you? > sw_single with another UI bridge: > # (as super-user:) /usr/lib/YaST2/bin/y2base sw_single qt This works basically: UI comes up, but it seems to be a little bit buggy. For example choosing packages in the list window doesn't work any more. > (or "ncurses" if you don't have yast-qt installed) The ncurses UI comes up as fallback for the qt UI and seems to work. > Check another tool. e.g.: > $ /sbin/yast2 timezone That doesn't work either ( same error message: libpy2wfm.so.2 => not found) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] Update a non active factory installation
I'am using a 10.3 installation for working and a factory installation for playing. To be up to date , the first thing I have to do when booting factory, is to run the update. But often this lasts 2 hours and then there is no time to play with factory any more :-(. My idea is now, to run the update for factory in the background when running the 10.3 installation. The steps, I've done so far is mount the factory installation to /mnt , do a mount --bind /mnt/etc/zypp /etc/zypp to make zypper using the factory configuration and then running "zypper -R /mnt -t package" . That works for most packages , but there a some failures in post install scripts. Which additional steps are needed to provide the environment to get all post install scripts working ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] yast2 qt frontend broken on x86_64
If I start yast2 it doesn't start it's qt frontend: libpy2wfm.so.2 => not found warning: the qt frontend is installed but does not work Qt GUI wanted but not found, falling back to ncurses. But libpy2wfm.so.2 exists in /usr/lib64/YaST2/plugin an is a link to /usr/lib64/YaST2/plugin/libpy2wfm.so.2.0.0 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Problems with yast2 and zypper was: Problems with yast2
Am Mittwoch, 12. Dezember 2007 schrieb Lukas Ocilka: [...] > > It seems to show two different problems: > > * Loading module 'Language' failed > Import.cc(import):97 No matching component found > > - yast2-country has been split into two packages recently > (yast2-country and yast2-country-data). Language.ycp is newly in > yast2-country-data. > - Make sure you have yast2-country-data package installed. > - (Wrong dependencies in some YaST RPM?) > - If you have updated yast2-country to a new verson, Language.ycp > probably got deleted. > > * Caught invalid bytecode in SlideShow.ybc > > - Probably old yast2-packager (SlideShow is part of it). You need to > update that package too. > - Maybe caused be the very same mistake by wrong RPM dependencies. > > You can still use 'zypper' to update your packages when YaST is broken :) > Unfortunately today a "zypper up -t package" has decided to destroy itself on that installation. This is the output of "zypper up -t package" before I did enter 'y' (problem marked): The following packages are going to be upgraded: apparmor-docs desktop-data-SuSE gnome-doc-utils gnome2-user-docs gnucash-docs inst-source-utils kdelibs3-devel-doc latex2html-pngicons libqt4-devel-doc-data manufacturer-PPDs oxygen-icon-theme oxygen-icon-theme-scalable release-notes suse-build-key xdg-utils ImageMagick ImageMagick-devel LibVNCServer OpenOffice_org-Quickstarter a2ps alsa-plugins apparmor-parser aqbanking aqbanking-lang avahi avahi-compat-mDNSResponder-devel blktrace bluez-utils bootsplash-theme-SuSE cdrkit-cdrtools-compat coreutils cryptsetup ddd desktop-file-utils device-mapper dmraid dvd+rw-tools evms evms-gui filesystem filters foomatic-filters freetype genisoimage gftp gftp-lang gitk git-email git-core gltt gnome-mag gstreamer010-plugins-bad gstreamer010-plugins-ugly gtkmm2 gtkspell gwenview icedax iproute2 iptables kaffeine kcm_gtk kde4-kmahjongg kde4-kmines kde4-kpat kde4-kreversi kde4-ksudoku kdeartwork3-kscreensaver kdeartwork3-xscreensaver kdegames3 kdegames3-card kdegames4 kdelibs3 kdelibs3-32bit kdelibs3-default-style kdelibs3-default-style-32bit kdelibs3-devel kdelibs3-arts kdelibs3-doc kdelibs4 kdelibs4-core kdemultimedia3 kdemultimedia3-CD kdemultimedia3-arts kdemultimedia3-mixer kdenetwork3 kdenetwork3-InstantMessenger kdenetwork3-news kdenetwork3-vnc kdepimlibs4 kdeutils3 kdetv kernel-default kernel-source kerry kio_beagle kio_slp kio_iso kio_ipodslave knights konversation kpartx krecord ksudoku ktorrent kwin-decor-suse2 libMagick10 libMagick++10 libWand10 libakode libakode-devel libavahi-client3 libavahi-devel libavahi-common3 libavahi-core5 libavahi-glib-devel libavahi-glib1 libavahi-ui0 libdjvulibre15 libdns_sd libkde4 libkdecore4 libkdegames4 libkdepimlibs4 libkexiv2 libkipi0 libopensc2 libopenct1 libqscintilla2-2 libqimageblitz-devel libqimageblitz4 libqt4 libqt4-dbus-1 libqt4-devel libqt4-devel-doc libqt4-qt3support libqt4-sql libqt4-sql-mysql libqt4-sql-postgresql libqt4-sql-unixODBC libqt4-sql-sqlite libqt4-x11 libsoprano4 libsoprano-devel lilo lvm2 metacity metacity-lang mozilla-nss mozilla-nss-32bit mpt-status multipath-tools openct opensc openssh openssh-askpass orca parted pcsc-lite pessulus pessulus-lang pstoedit python-opengl qtcurve-gtk2 qtcurve-gtk2-32bit qtcurve-kde resmgr rsync sabayon sabayon-lang skencil splashy strigi strigi-devel suspend tix wodim wpa_supplicant xlockmore yast2-core yast2-xml yauap zenity zsh The following packages are going to be REMOVED: hal-resmgr libzypp gnome-main-menu gnome-utils brasero evolution ^^^ cups-backends k3b gnome-pilot pm-utils gnome-vfs2 gnome-applets libnjb banshee hal-palm gstreamer010-plugins-good libipoddevice0 hal NetworkManager-gnome gnome-media libgphoto2 totem cups-autoconfig libipoddevice kdebase3-SuSE totem-plugin kpowersave sax2 kdebase3 gnome-volume-manager evolution-pilot NetworkManager gnome-python-desktop nautilus-cd-burner gnome-mount hal-devel kio_sysinfo NetworkManager-kde hwinfo sysconfig bluez-gnome gnome-power-manager control-center2 gimp Overall download size: 316.6 M. After the operation, 192.3 M will be freed. Continue? [yes/no]: How to fix that problem ? I allready tried to mount that instalation to /mnt on a working 10.3 installation and use the zypper -R /mnt up -t package. But zypper insisted to use the repos configured for 10.3. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] Problems with yast2
After updating my factory installation yesterday evening " yast2 sw_single" fails with: 635 Error while creating client module sw_single y2log shows [...] 2007-12-11 19:38:23 <1> linux-n04x(5049) [wfm] Y2WFMComponent.cc(import):698 Y2WFMComponent::import (SlideShow) 2007-12-11 19:38:23 <3> linux-n04x(5049) [Interpreter] clients/sw_single.ycp:21 Loading module 'Language' failed 2007-12-11 19:38:23 <3> linux-n04x(5049) [libycp] Import.cc(import):97 No matching component found 2007-12-11 19:38:23 <3> linux-n04x(5049) [Interpreter] clients/sw_single.ycp:21 Import 'Language' failed... 2007-12-11 19:38:23 <3> linux-n04x(5049) [Interpreter] clients/sw_single.ycp:21 Could not create its namespace 2007-12-11 19:38:23 <3> linux-n04x(5049) [libycp] Bytecode.cc(readFile):1161 Caught invalid bytecode in '/usr/share/YaST2/modul es/SlideShow.ybc' 2007-12-11 19:38:23 <3> linux-n04x(5049) [Interpreter] clients/sw_single.ycp:21 Loading module 'SlideShow' failed 2007-12-11 19:38:23 <3> linux-n04x(5049) [Interpreter] clients/sw_single.ycp:21 Import 'SlideShow' failed... 2007-12-11 19:38:23 <3> linux-n04x(5049) [Interpreter] clients/sw_single.ycp:21 Could not create its namespace 2007-12-11 19:38:23 <3> linux-n04x(5049) [libycp] Bytecode.cc(readFile):1161 Caught invalid bytecode in '/usr/share/YaST2/modul es/PackageCallbacks.ybc' 007-12-11 19:38:23 <3> linux-n04x(5049) [Interpreter] clients/sw_single.ycp:23 Loading module 'SlideShow' failed 2007-12-11 19:38:23 <3> linux-n04x(5049) [Parser] clients/sw_single.ycp:23 Can't load module 'SlideShow'. [...] 2007-12-11 19:38:23 <3> linux-n04x(5049) [Interpreter] clients/sw_single.ycp:43 Loading module 'Packages' failed 2007-12-11 19:38:23 <3> linux-n04x(5049) [Parser] clients/sw_single.ycp:43 Can't load module 'Packages'. 2007-12-11 19:38:23 <3> linux-n04x(5049) [Parser] clients/sw_single.ycp:139 Unknown namespace 'SlideShow'. Missing 'import'? 2007-12-11 19:38:23 <3> linux-n04x(5049) [Parser] clients/sw_single.ycp:139 syntax error, unexpected SCANNER_ERROR 2007-12-11 19:38:23 <1> linux-n04x(5049) [wfm] Y2CCWFM.cc(createInLevel):148 Parsing finished 2007-12-11 19:38:23 <3> linux-n04x(5049) [liby2] genericfrontend.cc(print_error):635 Error while creating client module sw_single Known problem or should I write a bug report ? Is there a workaround ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Factory x86_64 still broken ?
Am Sonntag, 5. August 2007 schrieb Stephan Kulow: > Am Sunday 05 August 2007 schrieb Markus Koßmann: > > which seems to be a known problem IIRC. > > Does zypper refresh help? > Yes, that seems to fix the problem. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Factory x86_64 still broken ?
Am Samstag, 4. August 2007 schrieb Stephan Kulow: > Am Saturday 04 August 2007 schrieb Markus Koßmann: > > Is factory x86_64 still known to be broken ? > > No, not known. > > > Unfortunately searching for "error" or "warn" in /var/log/zypper.log > > shows nothing usable. > > > > zypper is zypper-0.8.5-3, libzypp is libzypp-3.12.1-2 which seem to be > > the current versions from the thursday update. > > And zypper -v up? > With zypper -v no change. But zypper -vv shows: linux-n04x:/var/log # zypper -vv up Verbosity: 2 Initializing Target Repository 'inst_source' not cached. Caching... * Building repository 'inst_source' cache Problem loading data from 'inst_source': Unsupported kind of Filesystem Capability'filesystem(minix)-64bit ' Resolvables from 'inst_source' not loaded because of error. * Reading installed packages [100%] (1224 resolvables) Establishing status of aggregates Establishing status of aggregates Resolving dependencies... Summary: Nothing to do. Exiting main() which seems to be a known problem IIRC. But it's not nice that you need -vv to get an usable error message and that the problem is not clearly marked as error in the logfile. So I filed bug 297626. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] Factory x86_64 still broken ?
Is factory x86_64 still known to be broken ? When running "zypper up" I get : linux-n04x:~ # zypper up * Building repository 'inst_source' cache Problem loading data from 'inst_source' Resolvables from 'inst_source' not loaded because of error. * Reading installed packages [100%] with every mirror I tried. That includes gwdg, rwth-aachen,fr.rpmfind.net. It starts building the cache and inrementing the percentage until about 17% then jump to about 30% and then finaly the error message comes up. Unfortunately searching for "error" or "warn" in /var/log/zypper.log shows nothing usable. zypper is zypper-0.8.5-3, libzypp is libzypp-3.12.1-2 which seem to be the current versions from the thursday update. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] latest factory updates for x86_64 break yast sw_single
Latest factory (update from june 29 ) comes with libzypp-3.1.1 but yast sw_single still depends on libzypp-3.0.2. If you ignore the dependency when updating, yast sw_single will stop to work until you make a link /usr/lib64/libzypp.so.302.2.2 -> libzypp.so.303.0.1 (Bug 288754) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] USB not working (for me) in Alpha 5 X86_64
Am Montag, 18. Juni 2007 schrieb Keith Goggin: > On Monday 18 June 2007 05:50, Greg KH wrote: > > On Mon, Jun 18, 2007 at 12:23:32AM +1000, Keith Goggin wrote: > > > > Eeek, that's not good at all (and is indicitive of not a USB problem, > > but something else.) > > > > Can you try out the -vanilla kernel and let us know if that fixes the > > problem or not? If not, we need to know this real soon as 2.6.22 is > > about to be released. > > Hi Greg, > > I thought I was using the default (vanilla) kernel. Do you mean the i386 > kernel? -vanilla kernel means a kernel as delivered on kernel.org without any additional patches from SUSE. You will find it on ftp.opensuse.org (or mirrors) at /pub/opensuse/repositories/Kernel:/Vanilla/SUSE_Factory/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] KOTD 2.6.21-rc6-git1-20070408211613-default x86_64 and parallel port
Current status of the problem: 2.6.21 vanilla also is broken but 2.6.22-rc1 seems to fix that problem. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] KOTD 2.6.21-rc6-git1-20070408211613-default x86_64 and parallel port
Am Mittwoch, 11. April 2007 schrieb Greg KH: > On Wed, Apr 11, 2007 at 10:05:32AM +0200, Andreas Jaeger wrote: > > Markus Ko?mann <[EMAIL PROTECTED]> writes: > > > Am Dienstag, 10. April 2007 schrieb Andreas Jaeger: > > >> Markus Ko?mann <[EMAIL PROTECTED]> writes: > > >> > I tried KOTD 2.6.21-rc6-git1-20070408211613-default on a SUSE-10.2 > > >> > system and noticed that the parallel port driver seems to be broken. > > >> > It garbles the output. A cat some_asciifile > /dev/lp0 gives > > >> > unreadable output on my Epson Stylus Color 880. And any other try to > > >> > print something using cups doesn't work, too. Switching back to > > >> > 2.6.18.8-0.1-default fixes the problem. > > >> > > >> Please test our vanilla upstream kernel as well > > > > > > Where do I find that vanilla upstream kernel ? Or did you mean the > > > vanilla kernel from kernel.org ? > > > > There should be (at least in the build service) an vanilla kernel > > without any of our patches. Sorry, don't know the exact place right > > now;-( > > It's called kernel-vanilla and is sitting right next to where you got > the other KOTD :) > Well, I 'am using traditionally http://ftp.suse.com/pub/projects/kernel/kotd/ and there is no kernel-vanilla ;-) I've found it now at http://software.opensuse.org/download/Kernel:/ and the vanilla upstream kernel shows the same problem. Sending a bugreport to linux-kernel now. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] KOTD 2.6.21-rc6-git1-20070408211613-default x86_64 and parallel port
Am Dienstag, 10. April 2007 schrieb Andreas Jaeger: > Markus Koßmann <[EMAIL PROTECTED]> writes: > > I tried KOTD 2.6.21-rc6-git1-20070408211613-default on a SUSE-10.2 system > > and noticed that the parallel port driver seems to be broken. It garbles > > the output. A cat some_asciifile > /dev/lp0 gives unreadable output on > > my Epson Stylus Color 880. And any other try to print something using > > cups doesn't work, too. Switching back to 2.6.18.8-0.1-default fixes the > > problem. > > Please test our vanilla upstream kernel as well Where do I find that vanilla upstream kernel ? Or did you mean the vanilla kernel from kernel.org ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] KOTD 2.6.21-rc6-git1-20070408211613-default x86_64 and parallel port
I tried KOTD 2.6.21-rc6-git1-20070408211613-default on a SUSE-10.2 system and noticed that the parallel port driver seems to be broken. It garbles the output. A cat some_asciifile > /dev/lp0 gives unreadable output on my Epson Stylus Color 880. And any other try to print something using cups doesn't work, too. Switching back to 2.6.18.8-0.1-default fixes the problem. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] Latest KDE4 updates seem to break dbus on SUSE-10.2
I have the both the KDE3 and KDE4 repos added to my installation sources on SUSE-10.2. Today morning I decided to update all packages to the current version with yast2. That included a update of the KDE4 packages. After a restart KDE3 came up with a blank screen. First I found no usable error messages but after init 3 and starting X with startx i found some messages about missing kded and dbus failures. And when trying to start kded manually it complained about missing dbus. I decided to reinstall the dbus packages. That didn't fix anything. Then I reinstalled all KDE3 packages and removed KDE4. That "fixes" the problem for now. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] KOTD 2.6.20_rc5-20070113193557 and vmware-5.5.3
When trying to build the vmware-5.5.3 (with any-any-update 105 applied) modules on 2.6.20_rc5-20070113193557 ,I get the following error: make -C /lib/modules/2.6.20-rc5-20070113193557-default/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/linux-2.6.20-rc5-20070113193557' CC [M] /tmp/vmware-config1/vmmon-only/linux/driver.o In file included from /tmp/vmware-config1/vmmon-only/linux/driver.c:85: /tmp/vmware-config1/vmmon-only/./include/compat_kernel.h:21: error: expected declaration specifiers or ... before compat_exit /tmp/vmware-config1/vmmon-only/./include/compat_kernel.h:21: error: expected declaration specifiers or ... before exit_code /tmp/vmware-config1/vmmon-only/./include/compat_kernel.h:21: warning: type defaults to int in declaration of _syscall1 make[2]: *** [/tmp/vmware-config1/vmmon-only/linux/driver.o] Error 1 make[1]: *** [_module_/tmp/vmware-config1/vmmon-only] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.20-rc5-20070113193557' make: *** [vmmon.ko] Error 2 make: Leaving directory `/tmp/vmware-config1/vmmon-only' Unable to build the vmmon module. Any ideas ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] RC1 install fails on new PC
Today I got a new pc with ASUS M2NPV-MX motherboard.CDROM is HL-DT-ST DVD-RAM
GSA-H10N.
Installation from RC1 x86_64 CD set works fine ( including media check for
all CDs) until first media change.
When the messagebox asking for CD2 pops up , the dvd drive is still locked.
You need to click the eject button.
Then you will the messages on console 4:
hda: irq timeout: status=0x10d { busy }
ide: failed opcode was: unkown
hda: DMA disabled
hda: ATAPI reset complete
If you try to access the 2nd CD after the reset, by clicking OK in the message
boy, you will see now:
attempt to access beyond end of device
hda: rw=0, want=1419404, limit=1335712
Buffer I/O error on device /dev/hda, logical block 354850
If I switch to a console and run md5sum on the 2nd CD I get a wrong checksum
But if I put the CD into another PC the checksum is OK again.
When running md5sum on CD1 on the new PC all is OK
Then I burned another CD2 on the other PC , verified it before inserting
with md5sum and the exact same buffer error occurs again.
and running md5sum on the new PC gives exact the same wrong value as before.
with the other media. back in the other PC checksum id OK again.
And if reboot on the new PC from installation into the rescue system and run
md5sum on CD2 it is OK again.
Changing the DVD drive to another model and moving it from primary IDE to
secondary IDE doesn't change anything
Also using the pata_nv driver instead of amd74xx only changes the error
message, but the drive will also be resetted and fails to work after that.
Are the any known issues with NVIDIA 6150 based board relating to the IDE
controler, or is this just a defective board ?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Monitor frequences during installation
Am Freitag, 8. September 2006 23:52 schrieb William Gallafent: > On Friday 08 September 2006 22:48, Eberhard Moenkeberg wrote: > > The general policy with LCD displays HAS TO be: "lowest > > frequencies" at recognized resolutions. > > Er, I disagree. If it is possible to sense using the EDID system > the "preferred" frequency of the attached panel, then that > should be used. I believe that Xorg can correctly read these > values. That's not safe. I have a LCD display, which EDID reports a broken timing for its native resolution. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] openSUSE-10.2-Alpha3_Alpha4-x86_64-CD5.delta.iso on ftp.gwdg.de broken ?
Am Mittwoch, 6. September 2006 21:18 schrieb Andreas Jaeger: > Markus Koßmann <[EMAIL PROTECTED]> writes: > > Noticed that ftp.gwdg.de allready has the openSUSE-10.2-Alpha4 directory > > open and populated. The openSUSE-10.2-Alpha3_Alpha4-x86_64-CD5.delta.iso > > has only > > But I haven't announced it, so this can't be the official ones ;-) > Yes, I know. But better complain now about "unofficial" packages then later about the official ones ;-) >Something is strange here, we'll investigate and I'll remove all >broken deltas now, Thanks for the fast reaction . Looking at the file dates and sizes I guess that anything newer than openSUSE-10.2-Alpha3_Alpha4-x86_64-CD4.delta.iso is broken. But CD4.delta.iso seems to be ok . I could apply it sucessfully. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] openSUSE-10.2-Alpha3_Alpha4-x86_64-CD5.delta.iso on ftp.gwdg.de broken ?
Noticed that ftp.gwdg.de allready has the openSUSE-10.2-Alpha4 directory open and populated. The openSUSE-10.2-Alpha3_Alpha4-x86_64-CD5.delta.iso has only 8.4 MB, which seemed too small for me. So I downloaded it and checked the md5sum 01237374b19454cfb7f1051229584346 is right according MD5SUMS. But applying the delta to my openSUSE-10.2-Alpha3-x86_64-CD5.iso (MD5SUM f0cd3467a6b1afebdd0c66112a7b2ff2 ) fails with : [...] FreeNX.noarch: verbatim copy free-ttf-fonts.noarch (bzip): applying delta gtkdoc.noarch (bzip): applying delta gtksourceview-sharp2.noarch (bzip): applying delta ikvm.noarch (bzip): applying delta indata read 334 bytes failed So it seems to me, that the upstream of ftp.gwdg.de provides a broken openSUSE-10.2-Alpha3_Alpha4-x86_64-CD5.delta.iso. That should be fixed ASAP - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] delta.iso
Am Freitag, 3. März 2006 19:39 schrieb Edward Dunagin: > tell me please, is a delta.iso used like a kernel patch? > is it applied to the present cd.iso of what? ie is it to be > applied to beta5 cd's or beta6 cd's? man applydeltaiso - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] ivtv driver for Hauppauge PVR TV-cards missing in 10.1b3
Just noticed, that there is no ivtv driver coming with 10.1b3. Will this be changed in the final release ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] KDE_USE_IPV6="yes"
Am Samstag, 11. Februar 2006 13:43 schrieb houghi: > On Sat, Feb 11, 2006 at 01:15:39PM +0100, Stephan Kulow wrote: > > If there is a problem with the router, then konqueror is the least of > > your problems. And KDE_USE_IPv6 is (as the name) suggests only a > > workaround that applies to KDE. And as it's a workaround, we won't enable > > it by default (as in ="no"). Either SUSE is default IPv6 or it's not - so > > if you want to file a bug report, then target a wider audience. > > Then why is it YES in my standard Beta 3 configuration? > > Also perhaps having IPv6 off by default would be a good idea, as it would > solve speedproblems with many users. Would it be possible to write a testprogram which recognizes these problems and let that program decide to enable the workaround ? So that there would be three options "Yes" "Test" (default) "No" . - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] 10.1 and dmraid
Am Montag, 6. Februar 2006 12:19 schrieb Carl-Daniel Hailfinger: > Markus Koßmann schrieb: > > Is 10.1 intended to have dmraid support during installation ? > > Do you mean installation on dmraid or making dmraid partitions > available for later use? > installation on dmraid - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
