January 2008 - openSUSE Users - openSUSE Mailing Lists

[opensuse] beagleindex => bogus i_mode
by Stephen Berman 07 Feb '08

07 Feb '08

Starting four days ago, the kernel sends bogus i_mode messages after automatic beagle indexing, like this: Jan 25 21:15:02 escher su: (to beagleindex) root on none Jan 25 21:15:02 escher su: (to beagleindex) root on none Jan 25 21:18:09 escher syslog-ng[2198]: SIGHUP received, restarting syslog-ng Jan 25 21:18:10 escher syslog-ng[2198]: new configuration initialized Jan 25 21:18:36 escher kernel: klogd 1.4.1, ---------- state change ---------- Jan 25 21:19:07 escher su: (to nobody) root on none Jan 25 21:19:07 escher su: (to nobody) root on none Jan 25 21:19:11 escher su: (to nobody) root on none Jan 25 21:19:20 escher syslog-ng[2198]: last message repeated 4 times Jan 25 21:19:20 escher kernel: init_special_inode: bogus i_mode (33060) Jan 25 21:19:20 escher kernel: init_special_inode: bogus i_mode (30072) Jan 25 21:19:20 escher kernel: init_special_inode: bogus i_mode (31460) Jan 25 21:19:20 escher kernel: init_special_inode: bogus i_mode (30060) Jan 25 21:19:20 escher kernel: init_special_inode: bogus i_mode (30462) Jan 25 21:19:20 escher kernel: init_special_inode: bogus i_mode (31462) Jan 25 21:19:20 escher kernel: init_special_inode: bogus i_mode (57553) Jan 25 21:19:21 escher kernel: init_special_inode: bogus i_mode (30057) Jan 25 21:19:21 escher kernel: init_special_inode: bogus i_mode (30170) Jan 25 21:19:21 escher kernel: init_special_inode: bogus i_mode (72145) Jan 25 21:19:21 escher kernel: init_special_inode: bogus i_mode (71145) Jan 25 21:19:21 escher kernel: init_special_inode: bogus i_mode (55440) Jan 25 21:19:21 escher kernel: init_special_inode: bogus i_mode (35063) Can anyone tell me what this means, and is it a cause for concern? Thanks, Steve Berman -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

4 6

[opensuse] Bug: kernel-default-2.6.22.16-0.1 with RAID using /dev/mapper/
by David C. Rankin 06 Feb '08

06 Feb '08

The YOU kernel failed to install on my box using software raid. Apparently the new kernel install does not handle /dev/mapper correctly. Be very careful with this update. When it failed it had already re-linked vmlinuz and initrd and rendered the system unbootable before this error was encountered. So anyone doing remote site updates be VERY VERY wary of this Kernel. If it was me, I'd disable any automatic YOU updates you have scheduled until this and the wireless problem are addressed. This is the first failed kernel update I have seen since 8.0? * Installing: kernel-default-2.6.22.16-0.1 [100%]Installation of [S15:1][package]kernel-default-2.6.22.16-0.1.i586 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: Setting up /lib/modules/2.6.22.16-0.1-default Kernel image: /boot/vmlinuz-2.6.22.16-0.1-default Initrd image: /boot/initrd-2.6.22.16-0.1-default Root device: /dev/mapper/nvidia_haheegdb_part2 (mounted on / as ext3) Resume device: /dev/sda5 device-mapper: deps ioctl failed: No such device or address Command failed Device does not exist. Command failed Device does not exist. Command failed Device sda5 not found in sysfs Script /lib/mkinitrd/setup/72-block.sh failed! /sbin/mkinitrd failed error: %post(kernel-default-2.6.22.16-0.1.i586) scriptlet failed, exit status 1 (A)bort, (R)etry, (I)gnore? A -- 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

4 4

Re: [opensuse] USB Modem, wvdial not redialing
by Carlos E. R. 06 Feb '08

06 Feb '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 2008-02-01 a las 00:56 +0530, umesh b escribió: (You forgot to email to the list) > On Jan 30, 2008 6:27 PM, Carlos E. R. <> wrote: >> I never buy modems with propietary software. Now you know why. >:-) > > actually the modem was provided by the local telco..and the driver CD > was only for Win.. :-( > However being a USB modem i tried to use it in Linux. Its actually a > USB CDMA modem, ZTE make.. model AC8700 The fact is that, if the modem requires a driver, it is not a standard modem and you will have problems making it work under linux. I have no experience making such things work, because I don't want to use them: I'm fortunate to own a plain serial port external modem. But now and then people explain how they got their model working: search this list archive, the wiki pages, google... I'm sorry I can not give you more help. The needed info will be the output of the command "hwinfo --modem", as root. That will tell you how linux sees it, perhaps the chipset, and just maybe, somebody knows something. HTH. - -- Saludos Carlos E.R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHoibVtTMYHG2NR9URAmQhAJ9RwRfwql7zCDvsQWeU60P5CNDVugCfe3Dr iV+NkanD9qI2WXnctrPxG9c= =SGcV -----END PGP SIGNATURE-----

5 13

[opensuse] BUG: kernel 2.6.22.16-0.1-default Breaks Atheros Wireless
by David C. Rankin 04 Feb '08

04 Feb '08

Listmates, The latest online update to 2.6.22.16-0.1-default breaks the madwifi driver because the driver kernel modules ath_pci and ath_hal are NOT installed and CANNOT be installed with yast because of conflicts. 01:14 rankin-p35a~> cat linux/yast/wifi_conflicts.txt #### YaST2 conflicts list - generated 2008-01-31 01:09:17 #### This would invalidate atom:kernel-default-2.6.22.16-0.1.i586. atom:kernel-default-2.6.22.16-0.1.i586 has unfulfilled requirements === atom:kernel-default-2.6.22.16-0.1.i586 === kernel-default-2.6.22.16-0.1.i586 provides kernel-default == 2.6.22.16-0.1, but is scheduled to be uninstalled. kernel-default-2.6.22.16-0.1.i586[update] provides kernel-default == 2.6.22.16-0.1, but another version of that package is already installed. Can't satisfy requirement kernel-default >= 2.6.22.16-0.1 for atom:kernel-default-2.6.22.16-0.1.i586 atom:kernel-default-2.6.22.16-0.1.i586 will be evaluated for installation (freshened) by kernel-default-2.6.22.13-0.3.i586[update] (kernel-default == 2.6.22.13-0.3) (null) Conflict Resolution: ( ) delete kernel-default delete atom:kernel-default-2.6.22.16-0.1.i586 #### YaST2 conflicts list END ### Yast's Solution "delete kernel-default". WTF? And..., of course Yast DELETED the working kernel, and my working kernel modules, from my system, so there is no possibility of going back! Bug filed: https://bugzilla.novell.com/show_bug.cgi?id=357514 -- 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

4 8

Re: [Kiwi-devel] [opensuse] openSUSE 10.3 and LTSP
by CyberOrg 04 Feb '08

04 Feb '08

On Jan 15, 2008 4:41 PM, Marcus Schäfer <ms(a)suse.de> wrote: > > @Cyberorg: you use your own ltsp initrd. Did you make the adaptions > I posted in a former e-mail: > We are using unmodified kiwi netboot image, so this must be old description. @Roger, please update all kiwi packages, that should fix the neboot not building issue. > -------------- snip ----------- > Those of you who are using their own _boot_ image descriptions > and not the native ones provided by kiwi need to change the following > to be able to use kiwi >= 2.06 successfully: > > 1) remove the config/ directory > 2) edit the file images.sh and add the function call > > suseStripKernel > > as first call in this script > > I did the adaptions for all kiwi provided boot images so you can > have a look at for example /usr/share/kiwi/image/netboot/suse-10.3/images.sh > to see how I changed it > ------------------------------- > > Regards, > Marcus > -- > Public Key available > gpg --keyserver gpg-keyserver.de --recv-keys 0xCCE3C6A2 > ------------------------------------------------------- > Marcus Schäfer (Res. & Dev.) SUSE LINUX Products GmbH > Tel: 0911-740 53 0 Maxfeldstrasse 5 > FAX: 0911-740 53 479 D-90409 Nürnberg > GF: Markus Rex HRB: 16746 (AG Nürnberg) > http://www.suse.de Germany > ------------------------------------------------------- > -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 21

[opensuse] Unsubscribed! What has happened?
by Frank Fiene 01 Feb '08

01 Feb '08

Why was i unsubscribed from this list? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

9 13

[opensuse] ThinkPad X61 prof
by Verner Kjærsgaard 01 Feb '08

01 Feb '08

Hi list, I'm about to purchase a (Lenovo) ThinkPad X61 prof laptop. With 2G RAM, 100Gbyte SCSI (!) 7200 rpm HD, ATI GL and so. - It's to run OpenSuse10.3. - Has anyone on this list got any knowledge that this laptop will not run/is a no go/don't do it/what are you thinking of.. - Or should I just go ahead. I need the wireless to work in the box. I don't care about bluetooth. - as always, thank you! -- ------------------------------------------------------------------------- Med venlig hilsen/Best regards Verner Kjærsgaard Novell Certified Linux Professional 10035701 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

12 22

[opensuse] Need help installing SAR (without CD)
by Dirk Moolman 01 Feb '08

01 Feb '08

I have tried copying the packages I need, from CD to a machine, and then ftp'ing it to the Linux server that I need to install it on, but there are so many dependencies, it is starting to drive me crazy. All I need to do, is install SAR, to get performance statistics from a server (but I cannot install it from CD - the server is in another city and I need to ftp the software to that server). There must be a painless way of doing this. How can I do this, without loading the CD's - are there packages that include the dependancies, so that I can just install it all in just one go ? (and do it safely so that I don't affect the existing packages on the server - server belongs to one of our clients). Dirk *** Disclaimer *** The information contained in this e-mail is confidential and legally privileged and is intended solely for the addressee and to others who have the authority to receive it. Access to this e-mail by anyone else is unauthorized and as such, any disclosure, copying, distribution or any action taken or omitted in reliance on it is unlawful. If you have received this e-mail in error, please notify the sender immediately. The views expressed in this e-mail are the views of the individual sender and should in no way be construed as the views of the Company. The Company is not liable to ensure that outgoing e-mails are virus-free. The Company is not liable, should information or data, for whatever reason, be corrupted or fail to reach its intended addressee. The Company is not liable for any loss or damage of whatsoever nature and howsoever arising resulting from the opening or the use of the information in this e-mail, including its attachments and links. The sender of this e-mail is subject to and bound by the terms and conditions of Company+IBk-s Electronic Communications Usage Policy. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 2

[opensuse] GRUB will not boot up second windows partition
by Marc Chamberlin 01 Feb '08

01 Feb '08

I had something go drastically wrong with a Windows XP partition on a dual boot system (with SuSE) which is preventing it (Windows) from booting up properly. So I decided to purchase a second drive and create a new partition on this disk drive and reinstall Windows XP there. To accomplish this, for some darn reason only Microsoft knows, I had to disconnected my original drive in order to reinstall Windows XP on my new second drive, only when it was in the first SATA port position (I suspect this has something to do with the fact that I have an OEM reinstall disk for Win XP but that is only a guess...). I then reconnected the original drive into my second SATA slot. That much was successful and with the new XP I was able to at least read and start recovering files from the old XP partition. As I MOSTLY use SuSE 10.3 I decided to switch the order of the drives so that my original drive was again the first drive on my system and boot from it. As the boot menu was still referring to the original broken version of Windows XP, I booted up SuSE and attempted to fix GRUB (via YaST) so that it would also let me boot up the new XP partition. This is where I ran into troubles. Even though I am telling GRUB that the new XP partition is on my second drive, in the first primary partition, /dev/sdb0, it will not boot it up when I select it. Instead it continues to try an boot up the original broken XP that in now located on my first drive /dev/sda0. I even let the YaST boot manager find and suggest the possible operating systems and build a GRUB boot menu, and it properly found both XP partitions and made entries in the boot menu for each. BUT booting either still results in only the first Windows XP partition trying to boot up which as I said fails. If I unplug the drive that has this broken XP and SuSE on it, and reconfigure the SATA cables appropriately, then the new version of Windows XP will boot up fine, so I know there is nothing wrong with it. So I am lost and confused... Can anyone offer me advise on how to get this stubborn boot loader to do what I want it to? (That is to allow me to boot up my new second Win XP?) I REALLY do NOT want to have to reinstall SuSE as that would be a LOT of work for me!!! Marc... -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

8 11

[opensuse] Did Yast online updater break?
by Marc and Stephanie Chamberlin 01 Feb '08

01 Feb '08

I am running SuSE 10.3 and am getting an update notification as described - This update fixes various Xserver security issues. File existence disclosure vulnerability (CVE-2007-5958). XInput Extension Memory Corruption Vulnerability [IDEF2888 CVE-2007-6427]. TOG-CUP Extension Memory Corruption Vulnerability [IDEF2901 CVE-2007-6428]. EVI Extension Integer Overflow Vulnerability [IDEF2902 CVE-2007-6429]. MIT-SHM Extension Integer Overflow Vulnerability [IDEF2904 CVE-2007-6429]. XFree86-MISC Extension Invalid Array Index Vulnerability [IDEF2903 CVE-2007-5760]. PCF font parser vulnerability. When I install it I get the following error message - Repository 'openSUSE BuildService - KDE:Community' is invalid. Signature verification failed for repomd.xml Please, check if the URLs defined for this repository are pointing to a valid repository. Disabling repository 'openSUSE BuildService - KDE:Community' because of the above error. Repository 'openSUSE BuildService - Games (action)' is invalid. Signature verification failed for repomd.xml Please, check if the URLs defined for this repository are pointing to a valid repository. Disabling repository 'openSUSE BuildService - Games (action)' because of the above error. Repository 'openSUSE BuildService - KDE:Community' is invalid. Signature verification failed for repomd.xml Please, check if the URLs defined for this repository are pointing to a valid repository. Disabling repository 'openSUSE BuildService - KDE:Community' because of the above error. Error building the cache database: SQL logic error or missing database Disabling repository 'Packman Repository' because of the above error. Error building the cache database: SQL logic error or missing database Disabling repository 'VideoLan Repository' because of the above error. Error building the cache database: SQL logic error or missing database Disabling repository 'VideoLan Repository' because of the above error. Repository 'openSUSE BuildService - Games (action)' is invalid. Signature verification failed for repomd.xml Please, check if the URLs defined for this repository are pointing to a valid repository. Disabling repository 'openSUSE BuildService - Games (action)' because of the above error. What the heck??? This has been working fine, what broke it? Inquiring minds are worried.... Marc... -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

5 6