September 1998 - openSUSE Users - openSUSE Mailing Lists

[SuSE Linux] WindowMaker-0.19.1 install
by mlankton＠home.com 06 Sep '98

06 Sep '98

whoever it was (flushed my mail already) that had 0.19.1 bail on wrlib, the object it bails on uses jpeg, xpm, tiff, png, and libz. I bet if you were to build those libs from the source packages that come on your S.u.S.E. discs you would get a clean build. Don't ask me why, but I have had problems using the precompiled gfx libs before, and I have successfully built 0.19.1 on 5.3 and 5.2, so give that a try and let me know if it worked for you. -- .###. /#######\## -==============================================- ;##### ;# Mike's WindowMaker ;##### ;# <A HREF="http://tasteslikechicken.ml.org/windowmaker.html"><A HREF="http://tasteslikechicken.ml.org/windowmaker.html</A">http://tasteslikechicken.ml.org/windowmaker.html</A</A>> \# /## -==============================================- ###'---'#### - To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

1 0

[SuSE Linux] Sweet success...nearly
by steve＠millsphoto.com 06 Sep '98

06 Sep '98

At last, I can DIAL OUT with WVDial...I can log on...I can almost check my mail, then I get disconnected. But hey, I'm leaps and bounds beyond where I was. Avery Pennarun at WVDial was right...I had a conflict with IRQ 1 and 4. I was never aware that my mouse interrupts shared IRQ 4 with my modem. Very odd when my modem lists itself as being on IRQ 11 in Windows. Under Linux, they are (were) sharing 4. I have to type setserial /dev/ttyS2 irq 11 to make it work. That needs to be placed in my boot sequence. Can anyone tell me what file that is? I'm too tire to hunt it down right now. I still don't understand why I get disconnected within seconds, and I also want to learn how to keep the connection active during sessions, even if I shut down my mail program (XFMail). Thank you everyone for the help today and yesterday. I am almost there and wow...wvdial is fast. :) Steve <A HREF="http://www.millsphoto.com"><A HREF="http://www.millsphoto.com</A">http://www.millsphoto.com</A</A>> - To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

1 0

[SuSE Linux] FLOPPY BOOT DISK
by jclaude＠bow.intnet.mu 06 Sep '98

06 Sep '98

My floppy boot disk was corrupt. I managed to boot and create a new one (Prefer not to boot from HDU b'cause of Win98 and NTFS installed on the two other partitions). How can I create a spare boot disk (not sure I can restart the complicated process I did)? J C - To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

4 5

Re: [SuSE Linux] PCMCIA troubles
by jwaalkes＠edge.net 06 Sep '98

06 Sep '98

---------- > From: Jon Hartwell <glacierdenali(a)yahoo.com> > To: suse-linux-e(a)suse.com > Subject: Re: [SuSE Linux] PCMCIA troubles > Date: Saturday, September 05, 1998 11:10 PM > > > Yah, I had the same problem with a Zenith notebook (Z-Star EX) when I > first tried to install SuSE. I finally got the problem resolved some > how. I will review the notes I took while installing and see if I can > help you get these slots up and working. > > Do you know type of PCMCIA you have (Cirrus, Intel, VLSI, etc.)? > > > No, I just checked the manual.pdf file and it has the internal (infernal?) IBM part #'s. I'll 'pop-the-top' later (now is not a good time :) and see. Thanks, I appreciate the help! John - To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

1 0

[SuSE Linux] A sound suggestion.
by hattons＠CPKWEBSER5.ncr.disa.mil 06 Sep '98

06 Sep '98

For folks who are having trouble with MIDE etc., which used to work under 5.2, may I suggest looking at the versions of source code for the respective devices and versions of S.u.S.E.. I'm certainly no expert on this, but if there was a source code change in the driver, it may work to simply backup the new source and copy the old in its place, recompile and see what happens. Another thing I am finding to be a blessing, which I only do because I haven't taken the time to get my NT loader setup to boot linux from the second HD is that I boot from floppy. Since I have an old kernel on the original boot disk, I can always boot with that and get back lost functionality. I just went through this with my NIC. Here are the steps I took. 1) compiled with the new Kernel and glibc2: System can't see the net 2) grabbed the old version of 3c59x.c and put it in the new source tree, mv 3c5x9.o 3c59x.o.35 and recompiled as before: System can't see the net 3) booted from old boot disk: System sees the net. 4) deleted the 3c59x.o.35 and restored the latest 3c59x.c that came with 2.0.35, recompiled: system sees the net. Ok, you say, but what did I change? Didn't I go back to where I started? Yep! Beats the heck out of me! I see this with computers all the time. I once had a boss who truly believed computers know when you were frustrated, and had fun at your expense. Perhaps he's not such a nut case after all. HTH, Steve - To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

1 0

[SuSE Linux] X windows after 5.3
by squeegy＠c54820-a.carneg1.pa.home.com 06 Sep '98

06 Sep '98

Hello ALl, I am having a problem with X after upgrading to 5.3 from 5.2. First if I have kdm or xdm choosen as my login in rc.config, I get the login window but when i login the screen changes to that grey and the xconsole window opens and that is as far as i get. if I switch to console login and do startx I go into kde just fine. If I comment out kde in .xinitrc and try to startx, X crashes anyone else getting this? how do I fix it? I want to be able to use xdm or kdm again. one other complaint about 5.3, I had 2.0.35 already with 5.2 and did not want 5.3 to touch the kernel. well I was able to keep the kernel intact but the modules where messed up so I ended up haveing to rebuild the kernel and modules anyway. - To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

1 0

Re: [SuSE Linux] PCMCIA troubles
by glacierdenali＠yahoo.com 06 Sep '98

06 Sep '98

Yah, I had the same problem with a Zenith notebook (Z-Star EX) when I first tried to install SuSE. I finally got the problem resolved some how. I will review the notes I took while installing and see if I can help you get these slots up and working. Do you know type of PCMCIA you have (Cirrus, Intel, VLSI, etc.)? ---John Waalkes <jwaalkes(a)edge.net> wrote: > > > Sorry about reposting this, but I was zombified when I previously posted it > with the wrong subject title. > > Hi all, > > I have a IBM 755CX thinkpad with PCMCIA slots, and using Suse 5.2 they > don't work. I've tried cardmgr and have looked in '/proc/devices' (nothing > there) and lsmod shows nothing either. With RH 5.1, it just came up > working. So I know they *should* work. > > I d'led the latest PCMCIA driver and installed it, but it's still not > working. In fact, cardmgr doesn't give out any messages whatsoever and as > far as I can tell, doesn't do anything. > > The how-to and the man page (other than the need to install the > latest-n-greatest driver) didn't really point me anywhere. Can anybody > help? > > Thanks, > > John > > - > To get out of this list, please send email to majordomo(a)suse.com with > this text in its body: unsubscribe suse-linux-e > > > _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at <A HREF="http://mail.yahoo.com"><A HREF="http://mail.yahoo.com</A">http://mail.yahoo.com</A</A>> - To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

1 0

Re: [SuSE Linux] PCMCIA troubles
by glacierdenali＠yahoo.com 06 Sep '98

06 Sep '98

Yah, I had the same problem with a Zenith notebook (Z-Star EX) when I first tried to install SuSE. I finally got the problem resolved some how. I will review the notes I took while installing and see if I can help you get these slots up and working. Do you know type of PCMCIA you have (Cirrus, Intel, VLSI, etc.)? ---John Waalkes <jwaalkes(a)edge.net> wrote: > > > Sorry about reposting this, but I was zombified when I previously posted it > with the wrong subject title. > > Hi all, > > I have a IBM 755CX thinkpad with PCMCIA slots, and using Suse 5.2 they > don't work. I've tried cardmgr and have looked in '/proc/devices' (nothing > there) and lsmod shows nothing either. With RH 5.1, it just came up > working. So I know they *should* work. > > I d'led the latest PCMCIA driver and installed it, but it's still not > working. In fact, cardmgr doesn't give out any messages whatsoever and as > far as I can tell, doesn't do anything. > > The how-to and the man page (other than the need to install the > latest-n-greatest driver) didn't really point me anywhere. Can anybody > help? > > Thanks, > > John > > - > To get out of this list, please send email to majordomo(a)suse.com with > this text in its body: unsubscribe suse-linux-e > > > _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at <A HREF="http://mail.yahoo.com"><A HREF="http://mail.yahoo.com</A">http://mail.yahoo.com</A</A>> - To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

1 0

Re: [SuSE Linux] enough already! 5.3 is going, going...
by chandlerrick＠hotmail.com 06 Sep '98

06 Sep '98

>Don't misunderstand....I have NO intention of giving up on SuSE's >Linux! I just don't like broken distributions, no matter who >produces them...including the junk from MickySoft! I had not seen >KDE 1.0 till now.......NICE...VERY NICE indeed! Once the KDE >spreadsheet and word processor are released, I'll be able to replace >most of the Windoze crap at Cornell with SuSE. The learning curve >for most of my users will be minimal, at worst! Does anyone know when this may be released? I use staroffice myself and would like to switch to mainly KDE apps. Just wish they didn't look so damn much like MicroSuck. ______________________________________________________ Get Your Private, Free Email at <A HREF="http://www.hotmail.com"><A HREF="http://www.hotmail.com</A">http://www.hotmail.com</A</A>> - To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

3 2

[SuSE Linux] WVDial by the numbers
by steve＠millsphoto.com 06 Sep '98

06 Sep '98

I am now completely befuddled about wvdial. My 2 computers each have a Diamond Supra Express 336i PnP asvd, each one on com3. One box has it on IRQ 12, the other on 11. Each one has PnP BIOS disabled. WVDial, try as I might with it, just can't find my modems. When I come to wvdialconf /etc/wvdial.conf, I get no modem. It can't find a thing anywhere in the computer. I can follow this immediately with Kppp and find my modem in each case. It's just not an IRQ conflict, period. The best advice (and I trust it's very good advice in most cases) is to do something like this: 1) Disable com1, see what happens 2) type setserial /dev/ttyS0 autoconfig auto_irq -v (to find out how each IRQ is perceived) 3) type setserial /dev/ttyS2 autoconfig irq 5 (or whatever IRQ you are aiming for, to force implementation of them) 4) Open the box and fiddle. I now will undertake the thing I never wanted to do in the first place which is open the box. It's time to move the cards and see if different slots change the rules, then it's on to moving jumpers. How bad do I want to leave Windows behind? That bad. Just not bad enough to buy 2 new modems. Not yet. What really frustrates me is the fact that this is probably the only part of RH5.1 I ever got to work, my modem. I could at least log onto my ISP then. Why is suseppp, kppp and wvdial a losing trio for my particular modem? back to the box. Steve <A HREF="http://www.millsphoto.com"><A HREF="http://www.millsphoto.com</A">http://www.millsphoto.com</A</A>> - To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

1 0