August 2005 - openSUSE Users - openSUSE Mailing Lists

Uriel Carrasquilla/BOCA/NCCI is out biking and hiking.
by Uriel_Carrasquilla＠ncci.com 12 Aug '05

12 Aug '05

I will be out of the office starting 08/12/2005 and will not return until 08/22/2005. If you need to send me a message, e-mail uriel(a)adelphia.net. I will check on a best effort basis. If it is urgent to call me, check my cell number with Judy. The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.

1 0

Wireless NIC USB Troubles Take 2
by jim jim 12 Aug '05

12 Aug '05

You can see this is making me dingy by the last message or 2 I have sent. Must be that until I get this fixed I am stuck with Windose. Strange things going on. Installation of Suse 9.3 Everthing works great except cannot get on the internet. Used Yast to configure USB Wireless NIC. Made the choices in the Suse help. Wireless, USB, DHCP, ESSID, Channel, etc. Ended up with a device wlan0. I can put it up with ifconfig so it exists. It is in the proc filesystem and correctly identified but I can't talk to the network with it. I have overlooked something really obvious I know, so all comments welcome. Maybe a route command or something? Do you still need this? It should pick this up from DHCP it is configured to be a client. Is there something special about wireless that I missed. It has been so long since I had a NIC problem I don't remember the process. It works on Windose or I would not be able to send this email. Rescue me. ____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs

1 0

usb-wireless nic troubles
by jim jim 12 Aug '05

12 Aug '05

I have just installed 9.4 and cannot get the network to work. The system sees the card. I can see the lights blink. Configured it with Yast as per the help page. I can bring it up with ifconfig but can't talk to it. Shows up on the proc filesystem and correctly identifies the card. I must have missed something somewhere. Just can't think of it. Got to be too obvious. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

RE: [opensuse] Problems with wireless devices?
by Christopher S. Arnold 12 Aug '05

12 Aug '05

I too am unable to get this to work on 2 laptops: dell latitude D600 and ibm t42. I tried to use the ipw2100 rpm from Suse 9.3. This installed with no problems but was not able to ping internal or external. I use 128bit static wep hex. Also use MAC authentication and both laptops MAC address is registered with my AP. I can right click kinternet->wireless connection then click scan tab->start scan; enter in the 128bit hex key and click connect and will always say "authenticated successfully" but can not ping anything internal or external. Anybody gotten the wireless to work. Chris -----Original Message----- From: Carlos [mailto:dubbsix@yahoo.com] Sent: Thursday, August 11, 2005 7:29 PM To: opensuse(a)opensuse.org Subject: Re: [opensuse] Problems with wireless devices? Try no encryption -- as a test. Is your authentication type set as open or shared? --- robbinsc(a)email.arizona.edu wrote: > Quoting Carlos <dubbsix(a)yahoo.com>: > > Yes - AP is using 128bit hex WEP. I've set the key > a few times, but I can't > figure where the problem is....I'll give no > encryption a go. > > > > Is the AP setup using any encryption? > > > > --- robbinsc(a)email.arizona.edu wrote: > > > >> I'm having a lot of trouble getting my wireless > card > >> to work with my wireless > >> AP. I have one of the > >> famous-for-not-releasing-drivers Broadcom > chipsets > >> (specifically the Dell Truemobile 1300 (B/G) ). > I > >> tried using ndiswrapper, but > >> I had little success. The driver installed > >> properly, and everything else worked > >> fine, but I couldn't get SuSE to ping the router > and > >> get an IP address. I tried > >> a few restarts, but nothing happened. I started > >> over again, this time using > >> Linuxant's Driverloader package. The problem > >> remains the same. I've set the > >> configuration quite a few times, both within YaST > >> and by using iwconfig. I've > >> also tried using ifdown to stop eth1 and then > >> restart it and dhcp with ifup. > >> Is this a known bug, or am I doing something > wrong? > >> I can confirm the AP is > >> working fine, because the other computers on my > >> network are reporting no > >> problems. The weird thing is - if I execute > >> KWifiManager, the AP is seen, the > >> ESSID displayed, and the signal is reported as > 100% > >> (which makes sense, as I'm > >> seated right next to the router), but it can't > >> detect the MAC of the AP, and it > >> says that it's disconnected. > >> > >> Thanks for the help. > >> > >> -Chris > >> > >> > >> > > > --------------------------------------------------------------------- > >> To unsubscribe, e-mail: > >> opensuse-unsubscribe(a)opensuse.org > >> For additional commands, e-mail: opensuse-help(a)opensuse.org > >> > >> > > > > > > __________________________________________________ > > Do You Yahoo!? > > Tired of spam? Yahoo! Mail has the best spam > protection around > > http://mail.yahoo.com > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > opensuse-unsubscribe(a)opensuse.org > > For additional commands, e-mail: > opensuse-help(a)opensuse.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > opensuse-unsubscribe(a)opensuse.org > For additional commands, e-mail: > opensuse-help(a)opensuse.org > > ____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-help(a)opensuse.org

2 1

Digest anyone?
by Christopher S. Arnold 12 Aug '05

12 Aug '05

Hello all! I just wondered if it is possible to have a "digest" option for each list? Instead of recieving indiviual emails, you could opt to recieve 1 "digest" of the days posts, or recieve 1 digest after x posts/hours? Thanks Chris

2 1

Problem DDNS + DHCP in SuSE 9.3 not response any dhcp request from client.
by Arie Reynaldi Z 12 Aug '05

12 Aug '05

Hi, I already had working dhcpd server in suse 9.1, and now I want to replace with another server that running SuSE 9.3. And now I got a problem, it seems my suse 9.3 server didn't response any DHCP connection from client, it work in previous suse 9.1... :( I have genDDNS.sh to make named.key and add it to /etc/sysconfic/named and /etc/sysconfig/dhcpd. I also have add bootps in /etc/sysconfic/SuSEfirewall (which it's never add in suse 9.1) Before I run it, I have turn off my dhcpd-server in suse 9.1. Why my server didnt response dhcp client ? Anyway here's my named.conf options { directory "/var/lib/named"; dump-file "/var/log/named_dump.db"; statistics-file "/var/log/named.stats"; listen-on-v6 { any; }; allow-query { 127.0.0.1 ; 192.127.0.0/24; 202.152.21.234; }; notify no; forwarders {192.127.0.1;}; }; #include "/etc/rndc.key"; #include "/etc/named.keys"; controls { inet 127.0.0.1 allow {localhost;} keys {rndc-key;}; }; zone "." in { type hint; file "root.hint"; }; zone "localhost" in { type master; file "localhost.zone"; }; zone "0.0.127.in-addr.arpa" in { type master; file "127.0.0.zone"; }; include "/etc/named.conf.include"; zone "fsi.info" in { type master; file "dyn/fsi.info"; allow-update { key DHCP_UPDATER; }; }; zone "0.127.192.in-addr.arpa" in { type master; file "dyn/0.127.192.in-addr.arpa"; allow-update { key DHCP_UPDATER; }; And here's my DHCPD.CONF ddns-update-style interim; ddns-updates on; one-lease-per-client true; ignore client-updates; include "/etc/named.keys"; include "/etc/rndc.key"; subnet 192.127.0.0 netmask 255.255.255.0 { option routers 192.127.0.1; option broadcast-address 192.127.0.255; option domain-name "fsi.info"; option domain-name-servers 192.127.0.7; option netbios-name-servers 192.127.0.1; ddns-domainname "fsi.info"; ddns-rev-domainname "0.127.192.in-addr.arpa"; range dynamic-bootp 192.127.0.180 192.127.0.254; default-lease-time 21600; max-lease-time 86400; zone fsi.info. {primary 127.0.0.1; key DHCP_UPDATER;} zone 0.127.192.in-addr.arpa. {primary 127.0.0.1; key DHCP_UPDATER;} } #max-lease-time 172800; #host back1 { hardware ethernet 00:60:97:63:1b:68; fixed-address 192.127.0.18; } host printer1 { hardware ethernet 00:10:83:93:2c:87; fixed-address 192.127.0.205; } host printer2 { hardware ethernet 00:01:e6:5a:94:a6; fixed-address 192.127.0.206; } host maindata { hardware ethernet 00:08:02:8B:1B:57; fixed-address 192.127.0.210; } host receptionits { hardware ethernet 00:e0:7d:95:29:ed; fixed-address 192.127.1.123;} And here's /var/lib/named/dyn -rw------- 1 named named 172 Aug 11 14:13 0.127.192.in-addr.arpa -rw-r--r-- 1 named named 172 Aug 11 14:11 0.127.192.in-addr.arpa-1 -rw------- 1 named named 193 Aug 11 14:13 fsi.info -rw-r--r-- 1 named named 194 Aug 11 14:11 fsi.info-1 -- Arie Reynaldi Zanahar reymanx at gmail.com http://www.reynaldi.or.id

3 3

After using man, how to return to the shell prompt?
by Shriramana Sharma 12 Aug '05

12 Aug '05

After using a man command, (I recently read up on man mount) how do I get back to the shell prompt? I tried ESC, but most intelligently it just parrots my key - says "ESC" and does nothing else. Ctrl+F4 completely closes the Konsole window. Thanks in advance... -- Shriramana Sharma http://samvit.org

10 15

Re: [opensuse] Open Suse beta 1 grub no boot windows xp partition
by Jerry Marshall 12 Aug '05

12 Aug '05

no secondary hard drive for me. i used the default partitioning scheme with one hard drive, 1 gig swap on hda1 and the rest as / on hda2. grub by default installs to hda2 and when i rebooted, no OS. when in to expert and changed grub to install on MBR of hda and it booted fine -----Original Message----- From: houghi <houghi(a)houghi.org> Sent: Aug 11, 2005 3:11 PM To: opensuse(a)opensuse.org Subject: Re: [opensuse] Open Suse beta 1 grub no boot windows xp partition On Thu, Aug 11, 2005 at 03:06:34PM -0400, Jerry Marshall wrote: > i had an issue like this however i was not dual booting. i did all the defaults and when disc 1 was done and it rebooted, i got the message that there was no operating system found. did another reinstall and clicked the expert tab to modify the boot loader. it was installing grub to hda2, i told it to install to MBR of hda and it worked. is that the same bug that will be fixed in beta 2? No, that sounds like another bug: http://opensuse.org/index.php/Bugs:most_annoying_bugs Installation on secondary hard drive can cause the system to be unbootable. Bug #100728, solved for beta2 I personaly got `Invalid Partition Table`, repaired grub with my SUSE 9.1 and got it running. I am waiting for Beta2 if there are other issues like this. houghi -- When in doubt, do what the President does -- guess. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-help(a)opensuse.org Jerry Marshall jsmarshall85(a)earthlink.net Choose you this day whom ye will serve, but as for me and my house, we will serve the Lord. - Joshua 24:15 http://www.lds.org http://www.mormon.org

1 0

Re: [opensuse] Question about posting
by Eberhard Moenkeberg 12 Aug '05

12 Aug '05

Hi, On Fri, 12 Aug 2005, Christoph Thiel wrote: > why? ;) > On Fri, 12 Aug 2005, Eberhard Moenkeberg wrote: >> I see a lot of top and bottom posting going on. It makes it very hard to >> read with all the scrolling up and down. First to see what the question >> was and then back to the answer. >> >> Would it be wise to recommend bottom posting? > > Yes, very much recommended here. > > Let anyone ask "why", and I 'll explode. You are demonstrating the heart of the answer yourself. OK, I know you do it just to take the chance to fool me from "opposite" there at Frisco, but it is showing very well that the "reader" has the wrong sequence in case the "original poster" holds his dicipline. ;-)) BTW: best wishes that you represent SUSE at your best. ;-)) Cheers -e -- Eberhard Moenkeberg (emoenke(a)gwdg.de, em(a)kki.org)

1 0

RE: [SLE] Kdesktop Locker Signal 11 (SIGSEGV) LDAP
by Urciolo, Kevin 12 Aug '05

12 Aug '05

I upgraded to the latest qt3 for kicks. That did not fix the problem. I also upgraded to the 3.4 kdelibs since the stack trace has libkdecore listed. That did not fix the problem either. It did produce other expected inconsistencies, but that is beside the point. I wonder if this works in SUSE professional 9.3. -----Original Message----- From: Anders Johansson [mailto:andjoh@rydsbo.net] Sent: Thursday, August 11, 2005 6:42 PM To: suse-linux-e(a)suse.com Subject: Re: [SLE] Kdesktop Locker Signal 11 (SIGSEGV) LDAP On Friday 12 August 2005 00:18, Urciolo, Kevin wrote: > The crash is consistent on several machines. One problem area may be > that KDM 3.4.1 (I just tried 3.4.2 and it has the same problem) is > used along with everything else KDE being 3.2.1. There did not seem > to be package dependencies. KDM was bumped up to allow password > expiration prompts to function with LDAP. KDM 3.2.1 would prompt the > user to change his/her password. However, it would complain that the > orginal password was incorrect, even though the prompt did not ask for it. Hm, ok. As far as I'm aware, kde 3.4 hasn't been released officially for NLD, so I assume this is something you have installed manually. I don't know if there are compatibility issues, but this could very well be the problem. If there was a problem with KDM and LDAP in NLD, did you report this as s bug? I think that would be preferable to upgrading from unsupported packages Where did you find the new kdm package? Did you compile it yourself, or did you get a precompiled rpm from somewhere? If so, where? -- 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

2 1