October 2004 - openSUSE Users - openSUSE Mailing Lists

RE: [SLE] Lexar 1gb usb jump drive sport
by WABonnett＠ups-scs.com 11 Oct '04

11 Oct '04

Thanks for the reply. I went ahead and ordered it, and it's scheduled to arrive today, woohoo. Couldn't pass up the $49 after rebate for 1gig. If it didn't work, I would have used it for something else. Again, thanks for the reply. Wayne -----Original Message----- From: Ti Kan [mailto:ti@amb.org] Sent: Saturday, October 09, 2004 03:58 To: suse-linux-e(a)suse.com Subject: Re: [SLE] Lexar 1gb usb jump drive sport WABonnett(a)ups-scs.com writes: > Has anyone had a good experience using this with SuSE 9.1? =20 > I found this item on sale at buy.com for $49.99 after a $30.00 rebate. = > I want to make sure I'll be able to use it on my SuSE linux box before I = > purchase it. I have a 256MB version of the Lexar USB Jump Drive, and it works perfectly on SuSE 9.1. I would expect the 1GB version to work fine as well. -Ti -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq(a)suse.com

1 0

Re: [SLE] new v9.2 is out
by rada and gus 11 Oct '04

11 Oct '04

On Sat, 2004-10-09 at 04:15, Branimir Vasilic wrote: > I am sure there are broken things, but the kde menu problem is I think a KDE > issue. I was never able to edit the KDE menu and have given up on it for some > time now. > No, I don;t believe that is correct, since I have been editing the KDE menu in Red Hat 7.1, 7.2, 7.3, 8, 9 and FC1 (I always prefered KDE to Gnome) without a problem. I recently switched to Suse 9.1 and was quite dissapointed that it is broken since it has worked so well before. I tried updating KDE through YOU but it did not help. Gus.

3 2

SuSE 9.2
by Kirk Coombs 11 Oct '04

11 Oct '04

I was just curious if anybody knew when 9.2 is scheduled to be released, and what major packages it will contain. (kernel, kde, gnome, etc.). Thanks! -- visit me at http://www.sparticus.us

11 11

Error installing IPTables::IPv4
by Christian Bjørnbak 11 Oct '04

11 Oct '04

Hi I trying to install the cpan perl module IPTables::IPv4, but I get the following compile error: /usr/src/linux/include/net/protocol.h:63: error: field `list' has incomplete type Can anyone help me? Or know were to find the module as a rpm? I have SuSE 9.1 with kernel-default and kernel-source 2.6.5-7.108. A shorted trace of the error is included below: cpan -i IPTables::IPv4 We have to reconfigure CPAN.pm due to following uninitialized parameters: cpan_home, keep_source_where, build_dir, build_cache, scan_cache, index_expire, gzip, tar, unzip, make, pager, makepl_arg, make_arg, make_install_arg, urllist, inhibit_startup_message, ftp_proxy, http_proxy, no_proxy, prerequisites_policy, cache_metadata /home/cb/.cpan/CPAN/MyConfig.pm initialized. CPAN is the world-wide archive of perl resources. It consists of about 100 sites that all replicate the same contents all around the globe. Many countries have at least one CPAN site already. The resources found on CPAN are easily accessible with the CPAN.pm module. If you want to use CPAN.pm, you have to configure it properly. If you do not want to enter a dialog now, you can answer 'no' to this question and I'll try to autoconfigure. (Note: you can revisit this dialog anytime later by typing 'o conf init' at the cpan prompt.) Are you ready for manual configuration? [yes] no ... commit: wrote /home/cb/.cpan/CPAN/MyConfig.pm CPAN: Storable loaded ok CPAN: LWP::UserAgent loaded ok Fetching with LWP: ... Checksum for /home/cb/.cpan/sources/authors/id/D/DP/DPATES/IPTables-IPv4-0.98.tar.gz ok Scanning cache /home/cb/.cpan/build for sizes IPTables-IPv4-0.98/ IPTables-IPv4-0.98/t/ IPTables-IPv4-0.98/t/56speed.t IPTables-IPv4-0.98/t/07flush.t ... IPTables-IPv4-0.98/unpacker.h IPTables-IPv4-0.98/packer.c IPTables-IPv4-0.98/module_iface.h IPTables-IPv4-0.98/loader.h CPAN.pm: Going to build D/DP/DPATES/IPTables-IPv4-0.98.tar.gz Checking if your kit is complete... Looks good Writing Makefile for IPTables::IPv4 cp IPv4/TableTie.pm blib/lib/IPTables/IPv4/TableTie.pm cp IPv4/Chain.pm blib/lib/IPTables/IPv4/Chain.pm cp IPv4.pm blib/lib/IPTables/IPv4.pm AutoSplitting blib/lib/IPTables/IPv4.pm (blib/lib/auto/IPTables/IPv4) cp IPv6.pm blib/lib/IPTables/IPv6.pm AutoSplitting blib/lib/IPTables/IPv6.pm (blib/lib/auto/IPTables/IPv6) cp IPv4/Toplevel.pm blib/lib/IPTables/IPv4/Toplevel.pm cp IPv4/Rule.pm blib/lib/IPTables/IPv4/Rule.pm cp IPv4/RuleList.pm blib/lib/IPTables/IPv4/RuleList.pm /usr/bin/perl /usr/lib/perl5/5.8.3/ExtUtils/xsubpp -noprototypes -typemap /usr/lib/perl5/5.8.3/ExtUtils/typemap -typemap IPTables.typemap IPv4.xs > IPv4.xsc && mv IPv4.xsc IPv4.c cc -c -Iinclude -I/usr/src/linux/include -Wall -DMODULE_PATH=\"/usr/lib/IPTables-IPv4\" -O2 -march=i586 -mcpu=i686 -fmessage-length=0 -Wall -Wall -pipe -DVERSION=\"0.98\" -DXS_VERSION=\"0.98\" -fPIC "-I/usr/lib/perl5/5.8.3/i586-linux-thread-multi/CORE" IPv4.c In file included from /usr/src/linux/include/linux/netdevice.h:28, from /usr/src/linux/include/linux/netfilter_ipv4.h:10, from /usr/src/linux/include/linux/netfilter_ipv4/ip_tables.h:25, from include/libiptc/libiptc.h:6, from IPv4.xs:28: /usr/src/linux/include/linux/if.h:25:1: warning: "IFNAMSIZ" redefined In file included from include/libiptc/ipt_kernel_headers.h:14, ... /usr/src/linux/include/linux/ipv6.h:19: error: redefinition of `struct in6_pktinfo' In file included from /usr/src/linux/include/linux/netfilter_ipv4.h:11, from /usr/src/linux/include/linux/netfilter_ipv4/ip_tables.h:25, from include/libiptc/libiptc.h:6, from IPv4.xs:28: /usr/src/linux/include/net/protocol.h:39: warning: `struct sk_buff' declared inside parameter list /usr/src/linux/include/net/protocol.h:39: warning: its scope is only this definition or declaration, which is probably not what you want /usr/src/linux/include/net/protocol.h:40: error: parse error before "u32" /usr/src/linux/include/net/protocol.h:40: warning: `struct sk_buff' declared inside parameter list /usr/src/linux/include/net/protocol.h:48: warning: `struct sk_buff' declared inside parameter list /usr/src/linux/include/net/protocol.h:53: warning: `struct inet6_skb_parm' declared inside parameter list /usr/src/linux/include/net/protocol.h:53: warning: `struct sk_buff' declared inside parameter list /usr/src/linux/include/net/protocol.h:63: error: field `list' has incomplete type IPv4.xs: In function `XS_IPTables__IPv4__Table_set_policy': IPv4.xs:329: warning: dereferencing type-punned pointer will break strict-aliasing rules make: *** [IPv4.o] Error 1 /usr/bin/make -- NOT OK Running make test Can't test without successful make Running make install make had returned bad status, install seems impossible

2 3

Ok Raid-1 is beggining to scare me BIG TIME!!
by Chris Roubekas 11 Oct '04

11 Oct '04

Dear all, I would like to thank you all for explaning to me that the "Dirty" state is nothing more than Raid being mounted. Next time that I have a problem, I better ask and then bet paranoid.... I tested the Raid again last night and all was well. Managed to correct the "shadow" drive that was hanging around in Raid and works like a breeze. Kindest regards, Chris

2 1

Re: [SLE] wireless network cards
by jcannare1＠comcast.net 11 Oct '04

11 Oct '04

Cosmo - thanks for the tip. That did the trick,once I got the driver loaded I was able to complete the setup in YaST and I'm now wireless again!! I appreciate your response...... > jcannare1(a)comcast.net wrote: > > Help anyone!! > > I've just loaded Suse 9.1 pro on an HP laptop. I've got my 100BT (eth0) > working but I haven't been able to get my PCMCIA wireless card to work. Yast see > the card and knows what it is but I can't get it to connect. > > I've tried my NetgearWG511 (802.11g), a Netgear WG521 (802.11b) and a Linksys > WPC11 (also 802.11b). At least with the Linksys I get a green power light. > > Any suggestions?? Am I missing a kernel module or subsystem entry?? > > > > Your Netgear WG511 (try google: WG511 linux) is prism54 card. Check out > http://prism54.org/ . Suse is actually very good at handling these > cards (better than Fedora) but you must understand the method of loading > a binary firmware for your card. > > you probably see this when running 'iwconfig': > > eth0 "DEVICE NOT READY" > > If you have the windows driver on CD, you may find a file named > 1.0.3.0.arm or 1.0.4.3.arm on the CD. Either of these should be copied > to /usr/lib/hotplug/firmware and renamed isl3890. > > Then try "ifconfig eth0 up" and "iwconfig": you should now be able to > configure the card to your wireless network. > > Attached is a mini-howto I wrote for some guys at work for the same card. > > > Hope that helps. > > Cosmo > > 1) physically install prism wireless card > > 2) boot os, run 'iwconfig'. you should see: > eth0 NOT READY! ESSID:off/any > ... > > 3) ifconfig eth0 up > (this will fail, but give us dmesg output) > > 4) dmesg |tail > prism54: request_firmware() failed for 'isl3890' > eth0: could not upload firmware ('isl3890') > > 5) find the firmware from vendor CD (or from www.prism54.org) it will be named > something like: 1.0.4.3.arm Copy it to /usr/lib/hotplug/firmware/ and rename it > isl3890 > > 6) try again: ifconfig eth0 up; dmesg | tail > if the correct firmware (and loading mechanism) are in place, you should see: > eth0: islpci_open() > eth0: resetting device... > eth0: uploading firmware... > eth0: firmware uploaded done, now triggering reset... > > 7) and: iwconfig eth0 > eth0 IEEE 802.11b/g ESSID: "pogo-guest" > ... > > that means all should be working. > > > -- > Check the headers for your unsubscription address > For additional commands send e-mail to suse-linux-e-help(a)suse.com > Also check the archives at http://lists.suse.com > Please read the FAQs: suse-linux-e-faq(a)suse.com

1 0

Help with lkcd
by Lucky Leavell 11 Oct '04

11 Oct '04

OS: SuSE 9.1 I installed both lkcd packages from the CDs and have rebooted the system but there are apparently some additional steps involved. I have an IBM and SGI document found on lkcd.sourceforge.net which go into some detail on patching the kernel, etc. Just how much of this does the SuSE installer do and how much must I do manually? For example, /etc/sysconfig/dump exists but /proc/sys/dump and the link to /dev/vmdump do not. Thank you, Lucky Leavell

1 1

Ok Raid-1 is beggining to scare me BIG TIME!!
by Chris Roubekas 11 Oct '04

11 Oct '04

----- Original Message ----- From: Chris Roubekas To: suse-linux-e(a)suse.com Sent: Saturday, October 09, 2004 11:47 PM Subject: Ok Raid-1 is beggining to scare me BIG TIME!! Dear friends, I recently posted a message asking for help on why my RAID-1 has a state of "dirty,no-errors" when issuing mdadm --detail /dev/md0. A friend in the list said that when he changed from reiserfs to ext3 it stopped being dirty as he was experiencing the same problems that I was when running reiserfsck on the /dev/md0 drive and found errors and upon running reiserfsck --fix-fixable the errors where not fixed. So being through this same tunnel of problems, I though I should follow his steps and try changing the entire md0 to ext3 to see if I will be able to avoide the problems that I am faced with. Well I thought of switching the md0 to md1 and recreating it in ext3 as opposed to reiserfs which it was before. Since my raid-1 in md0 is 2x200GB drives and I have no other drive to backup I removed one of the disks of md0, created a new md1 with mdadm and formated it in ext3 format. Then I copied all the data from md0 to md1 and finally I removed the second drive from md0 and added it to md1. After the process of reconstruction was over, I restarted my machine and issued cat /proc/mdstat which reported: server:/ # cat /proc/mdstat Personalities : [raid1] read_ahead 1024 sectors md1 : active raid1 hdc1[1] hdb1[0] 199125568 blocks [2/2] [UU] unused devices: <none> Which made me very happy as I saw that after the hard-drive lights stopped glowing things appeared just great! But then, I issued a mdadm --detail /dev/md0 and see what I get: server:/ # mdadm --detail /dev/md1 /dev/md1: Version : 00.90.00 Creation Time : Sat Oct 9 15:44:51 2004 Raid Level : raid1 Array Size : 199125568 (189.90 GiB 203.95 GB) Device Size : 199125568 (189.90 GiB 203.95 GB) Raid Devices : 2 Total Devices : 3 Preferred Minor : 1 Persistence : Superblock is persistent Update Time : Sun Oct 10 02:09:02 2004 State : dirty, no-errors Active Devices : 2 Working Devices : 2 Failed Devices : 1 Spare Devices : 0 Number Major Minor RaidDevice State 0 3 65 0 active sync /dev/hdb1 1 22 1 1 active sync /dev/hdc1 UUID : 22a79613:35bf4980:215dbc1e:910acdea I am totally confused by what I see here for the following reasons: a) How is it possible to say Total Devices 3 when there are only 2?? b) Why am I seeing the State: Dirty, no-errors still??? Then I copied a file from hda (which is the root filesystem; my raid is totally storage and nothing more as it is shared by Samba) and noticed that although the directory that is mounted on /dev/md1 has the file, when I mount /dev/hdb1 or hdc1 I notice that the file is not there. I tried issuing "sync" to see what would happen and I got nothing!! The file still doesn't appear on the drives! I am so confused and at the same time very very scared since I do not know if the data that the users put on that raid are actually being raid-ed (if there is such a word...). Tried to see how dmesg looks like and I got among other messages the following ones which report stuff about my md : md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: Autodetecting RAID arrays. [events: 0000000e] [events: 0000000e] md: autorun ... md: considering hdc1 ... md: adding hdc1 ... md: adding hdb1 ... md: created md1 md: bind<hdb1,1> md: bind<hdc1,2> md: running: <hdc1><hdb1> md: hdc1's event counter: 0000000e md: hdb1's event counter: 0000000e md: RAID level 1 does not need chunksize! Continuing anyway. kmod: failed to exec /sbin/modprobe -s -k md-personality-3, errno = 2 md: personality 3 is not loaded! md :do_md_run() returned -22 md: md1 stopped. md: unbind<hdc1,1> md: export_rdev(hdc1) md: unbind<hdb1,0> md: export_rdev(hdb1) md: ... autorun DONE. Then a little bellow this point I get the following messages: hdd: bad special flag: 0x03 md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. (recovery.c, 254): journal_recover: JBD: recovery, exit status 0, recovered transactions 4810 to 4908 (recovery.c, 256): journal_recover: JBD: Replayed 113 and revoked 0/1 blocks kjournald starting. Commit interval 5 seconds EXT3 FS 2.4-0.9.18, 14 May 2002 on ide1(22,1), internal journal EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. (recovery.c, 254): journal_recover: JBD: recovery, exit status 0, recovered transactions 4810 to 4921 (recovery.c, 256): journal_recover: JBD: Replayed 133 and revoked 1/2 blocks kjournald starting. Commit interval 5 seconds EXT3 FS 2.4-0.9.18, 14 May 2002 on ide0(3,65), internal journal EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. It looks like md is operating on one hand but is having a near to impossible day trying to import the hdc1 and hdb1 directories.... ARRRGGG!!!! THis is driving me crazy! Please please please try to give me a hand as I am about to loose my mind for ever! I am running a SuSE8.1 box with 3 HD 2 are 200GB in Raid-1 and the third is a small drive of 8GB for Linux and root filesystem. What do you think?? Thank you for your reply! Chris

6 5

HP ScanJet 3500c don't run under suse linux pro 9.1
by Kalos Bonasia 11 Oct '04

11 Oct '04

I tryed more scan configuration how to link this scanner to suse linux, via sane libraries, without results. Can anyone have the same scanner running under suse? -- Kalos Bonasia

4 12

Upgrade/update of SuSE 9.1 via red carpet results in login for 9.0 loop.
by Richard 10 Oct '04

10 Oct '04

Today I used red carpet to update my SuSE9.1/KDE3.3. That resulted in a reboot that turned into a loop. The login screen showed SuSE9.0 and wouldnt let me login as user OR root. I had to boot with the rescue disk, go into INIT 3 and using yast, reinstall kde3. All my sources are for 9.1 so I dont know where or how it got me into 9.0 login screen. Interestingly, it killed my networking ability until I did the reinstall from the cd's. Has anyone else had a similar problem? My current solution is to get rid of red carpet and use Yast & apt exclusively. richard -- Old age ain't for Sissies!

4 5