April 2006 - openSUSE Factory - openSUSE Mailing Lists

applydeltaiso error
by Kenneth Schneider 22 Apr '06

22 Apr '06

When running applydeltaiso to CD1 I get the following error: payload uncompress error Any clue as to what this means? I have over 27g of free disk space. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998

2 1

factory update RC1->RC2
by jdd 22 Apr '06

22 Apr '06

hello :-) I really don't like the delta iso process, even if I understand the necessity. but I beg the net install is still possible, with factory as source? thanks 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

4 4

nut UPS problems with USB ports
by Graham Smith 22 Apr '06

22 Apr '06

Hi, I have a Powerware 3105 UPS and am trying to get nut to work with it. The UPS communicates via a USB port. I have SuSE 10.0 which comes with nut 2.02 which does not support this UPS so I downloaded nut-2.0.3-10.src.rpm from the 10.1 factory depository and compiled it without any problems. Where the problem arrises is the port configuration and permissions. lsusb Bus 005 Device 001: ID 0000:0000 Bus 004 Device 002: ID 04b8:0110 Seiko Epson Corp. Perfection 1650 Bus 004 Device 001: ID 0000:0000 Bus 003 Device 001: ID 0000:0000 Bus 002 Device 006: ID 0592:0002 Powerware Corp. Bus 002 Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000 If I change the owner of /proc/bus/usb/002/006 to upsd:root I can get the bcmxcp_usb driver to load. The /etc/init.d/uspd script will not run because the port is defined as 'auto' as per the bcmxcp_usb man page Implemention. The script fails when testing for the port as there is no physical port defined in /etc/ups/ups.conf as stated above. The script I believe will only work with 'tty' devices where you have an actual port assigned, but USB ports appear to be configured differently. BTW I just checked the latest nut-2.0.3-13.src.rpm has the same problem with /etc/init.d/upsd script. How do I file a bug report as I'm using SuSE 10.0 but using the src.rpm from the current 10.1 factory repository. -- Regards, Graham Smith

2 1

XEN
by Hans Witvliet 22 Apr '06

22 Apr '06

As release date is getting closer, and xen is going to be a part of sles-10, i wonder if anybody else had problems with xen. At work, i was asked to have a look at virtualisation, and because of my background, i prefer xen above vmware. On 10.0 systems 32/64-bit, xen (vs 3.0) seems stable enough. However on beta-6, beta-8 and rc1 (XEN 3.0.2) situation is highly unstable. Disks on the dom-U are not seen, loop-back devices still exist after dom-U is gone, verry picky about config files. I found that if one makes the slightest typo in a config file, it is no use to re-launch a dom-U, sometimes it works, often not. Mostly one has to start dom-0 (reboot) Anybody else testing xen? Hans -- pgp-id: 926EBB12 pgp-fingerprint: BE97 1CBF FAC4 236C 4A73 F76E EDFC D032 926E BB12 Registered linux user: 75761 (http://counter.li.org)

2 1

updating using rug
by Hubertus A. Haniel 21 Apr '06

21 Apr '06

Hi, Has anybody else tried using rug to update their 10.1 RC1 boxes? - I have mirrored the update tree to a local box and can add this as a source to rug and I know there are new packages (such as aaa_base) but I always get "no updates available". I followed pretty much the examples from http://en.opensuse.org/Examples_using_rug. I have also updated rug, libzypp and zmd to the latest levels. Best regards Hubba

1 0

texteditor and beagleindexer
by Martin Schlander 21 Apr '06

21 Apr '06

A couple of quick questions about 10.1rc1 w/ KDE: After Pico was moved to non-oss section, I'd expect Nano to be installed by default instead - but it isn't. This means there's no console text editor installed by default - at least when installing from 5 cds. I think this is almost a bug - or am I missing something? Also on my 10.1rc1 I notice that the beaglein-process is running amok on my hard drive - even though I haven't activated the beagle indexing daemon with Kerry. I don't remember this behaviour on earlier betas - it's rather annoying on slow and noisy hard drives - like on my laptop. Anyone else got this problem? Bug or intended? cb400f

3 2

RC1: Sound card won't configure
by Richard 19 Apr '06

19 Apr '06

Not sure if this is a bug, I thought it worth a punt here before logging as one: Fresh install of 10.1 RC1 on elderly AMD K6-2/500 but with plenty of RAM (512M) and hard disc (40G). Previously running SuSE 9.3 with no problems at all. Install of RC1 completed OK though with already-reported failures e.g. of yast update, fixed using the new rpms. Sound card is Creative / Ensonic PCI-128, correctly identified by installer - this is from hwinfo --sound: 15: PCI 0b.0: 0401 Multimedia audio controller [...] Model: "Ensoniq Creative Sound Blaster AudioPCI64V, AudioPCI128" Vendor: pci 0x1274 "Ensoniq" Device: pci 0x1371 "ES1371 [AudioPCI-97]" [...] Config Status: cfg=no, avail=yes, need=no, active=unknown However, when I try to configure using Yast, it always fails with lines like the following in y2log: [...] 2006-04-19 20:26:56 <3> beige(27813) [bash] ShellCommand.cc(shellcommand):78 Cannot stat /dev/dsp*: No such file or directory [...] 2006-04-19 20:27:01 <1> beige(27813) [YCP] sound/routines.ycp:619 modname: snd-ens1371 2006-04-19 20:27:01 <1> beige(27813) [YCP] sound/routines.ycp:620 mod_name: snd_ens1371 2006-04-19 20:27:01 <1> beige(27813) [YCP] sound/routines.ycp:621 get_running_cards: [] 2006-04-19 20:27:01 <1> beige(27813) [YCP] sound/routines.ycp:622 card_id: 0 2006-04-19 20:27:01 <1> beige(27813) [YCP] sound/routines.ycp:623 /proc cards: --- no soundcards --- 2006-04-19 20:27:01 <1> beige(27813) [YCP] sound/volume.ycp:307 starting extra attempt: 0 [...] 2006-04-19 20:27:02 <1> beige(27813) [YCP] sound/volume.ycp:313 result of the extra attempt: The kernel module snd-ens1371 for sound support could not be loaded. This can be caused by incorrect module parameters, including invalid IO or IRQ parameters. Attempting to install with alsaconf seems to work but also results in no card being found. Has anyone any idea what's wrong here? I have to say generally that 10.1 is looking pretty good, though there are clearly a few issues still to fix. Regards, -- Richard mailto:osl@16hd.freeserve.co.uk

1 0

rug failed to delete a ZYPP service
by Eberhard Moenkeberg 19 Apr '06

19 Apr '06

Hi, after y2pmsh "upgrade" from beta9 to rc1, I like to get YaST2 operational again. So I try to delete the old installation sources first, but it seems impossible. A popup window is telling rug failed to delete a ZYPP service: $["exit":1, "stderr":["FEHLER: Dienst 'nfs://lxi001/HE4/suse/10.1/SUSE-Linux10.1-Beta9-Extra?alias=SUSE LINUX-10.1-20060405-194517' nicht gefunden"], "stdout":[]] and it is impossible to delete the old entries. This is in a way ridiculous if I interpret it right that I doubt we ever left the alpha state with these new maintenance tools... Cheers -e -- Eberhard Moenkeberg (emoenke(a)gwdg.de, em(a)kki.org)

2 1

Fwd: Installation Sources
by Martin Soltau 18 Apr '06

18 Apr '06

Hi @ all, I tried to check packman for new software and I tried to add libxine1 to my installation. It was missing for some reason. So I started Yast2, selected "Install/uninstall software" and got an error message saying that he was unable to contact the server. Sorry, I don't have the exact wording right now. I then went into "Installation Sources" because I learned from Suse 10.0 that it sometimes helps to select e.g Packmna, select change / overwrite and just confirm again with OK. So I tried the same with 10.1 RC1. It sort of worked well, but when I tried to leave that dialogue the system was very busy (100% CPU) for about 15 Minutes. I killed the process because I assumed it hanged. But when I went into that part of yast again I found that the installation path was totally missing now. I re-entered everything, but he is now not able to add it. Again, I don't have the exact wording of the error mesage. Sorry. Question: - Is this a bug? - Or a known bug (I saw that there are some on the list but I am not sure whether what they are said to be is what I am experiencing here) - Or a feature? Martin Soltau

1 0

Booting Suse from a USB Pendrive via Floppy
by Cristian Lodtmann 18 Apr '06

18 Apr '06

Dear List. Pls. add to RC2 floppy image, to boot from a pendrive via floppy. This for bioses w/o USB booting option. Thanks Chris

2 1