December 1999 - openSUSE Users - openSUSE Mailing Lists

[SLE] PNP SB16
by jon＠document-solutions.com 23 Dec '99

23 Dec '99

I have a SB16 ISA in the box running SuSE 6.3 I ran the ISADump and got Isapnp.conf I uncommented some of the lines for IRQ and DMA etc but see no change. Anybody know what I am doing wrong here? Is there support in Yast for Sound Blasters? I thought there would be.... Regards, Jon -- To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

3 2

[SLE] Moor kernal Compile errors
by samelash＠ix.netcom.com 23 Dec '99

23 Dec '99

<HR> <UL> <LI>text/enriched attachment: stored </UL>

1 0

Re: [SLE] IP Masq module for Net Meeting 3 - GCC help needed - solved!!!
by grtoft＠yahoo.com 23 Dec '99

23 Dec '99

Leyon, Christopher wrote: > > [Total shot in the dark follows] > > But does the compiler actually know to look there? You might use gcc's -I > (capital i) switch to specify a directory to look in. > > If -I/usr/src/linux (or whatever) is already present, does the symlink point > to the correct directory? Tried that, too. No go. Here's what I did: Put ip_masq_h3231.c in /usr/src/linux/net/ipv4 Edited /usr/src/linux/net/ipv4/Makefile to add the ip_masq_h3231.c file in with the other ip_masq stuff (it's obvious), then... cd /usr/src/linux make dep make modules Now ip_masq_h3231.o exists in /usr/src/linux/net/ipv4 and I implemented it in /etc/rc.d/rc.firewall (custom script based on the firewall tool and the ip_masq how-to). Yahoo -- George Toft http://www.georgetoft.com -- To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

1 0

[SLE] ALSA, all talk and no sound.
by colWilson＠bigfoot.com 23 Dec '99

23 Dec '99

I've downloaded the latest ALSA, built it, configured the conf.modules and turned the sound settings in the mixer up. I've also loaded the OSS compatibility modules . All looks well (modules showup in lsmod and so on), but no sound and although the alsa mixers (eg amixer) can see the modules, the ones in Xwindows cannot. Help. I have a PCI 64 (using the ens1370 module) Col -- To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

2 1

[SLE] Kenal Compile Errors
by samelash＠ix.netcom.com 23 Dec '99

23 Dec '99

<HR> <UL> <LI>text/enriched attachment: stored </UL>

1 0

[SLE] IXMicro TV/FM card
by brittain＠ilinkusa.net 23 Dec '99

23 Dec '99

Is anyone using such a device? I've labored with bttv for a day now and cant get the bloody thing to work. Has anyone had success? -- To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

1 0

Re: [SLE] 'NO CARRIER' error with ISDN
by andrew＠andrew.dabsol.co.uk 23 Dec '99

23 Dec '99

hi thanks for all your help. i finally found out what was wrong: the 'NO CARRIER' was caused by a protocol error. to fix this, i changed the initialisation string to "AT&F&C1&D2%A2=95@B0=1@M2=P". the last three are the most important, setting up the correct protocol - PPP instead of V.120. it's a stupid mistake, but at least now its working. thanks again, and happy christmas! Andrew Smith -- To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

1 0

Re: [SLE] 'NO CARRIER' error with ISDN
by andrew＠andrew.dabsol.co.uk 23 Dec '99

23 Dec '99

hi i still can't get it working. i turned on extra messages and it reports "CHANNEL B1", then "CARRIER 64000", then "NO CARRIER". the terminal adaptor documentation states that 'NO CARRIER' is returned if: "Valid carrier not detected within period specified by register S7, or carrier lost for 300ms or more. Message is also sent when incompatible protocols are configured for the originating and answering ISDN terminal adaptor." ince register S7 is 30seconds, I presume that the problem is with protocols. When using the terminal adaptor in a win95 machine, protocol errors were also periodically experienced. any more ideas? thanks again, Andrew Smith -----Original Message----- From: Juergen Braukmann <juergen.braukmann(a)ruhr-west.de> To: SuSE Linux English <suse-linux-e(a)suse.com> Date: 22 December 1999 16:11 Subject: Re: [SLE] 'NO CARRIER' error with ISDN >jan vermeulen wrote: >> >> > Andrew Smith wrote: >> >> > i have a BT isdn ignition line and a terminal adapter (the adapter is >> > like a modem). everything works fine under windows, but under linux, >> > the adapter reports 'NO CARRIER' when sent 'ATD<phone-number>'. >> >my collegues had similar problems when they started with the terminal >adapter. I remember they use the dial string ATDI<number>. Maybe, you >can experiment with the usual X3 (ATX3DI<number>) as well... > >Juergen > >(PS: probably won't have the dial string before the new year... if it >persists mail me direct, I'll try to find so. after x-mas) > > >> You will need to run X75 on top of HDLC. Do you? >> >> JV > >-- >=========================================== __ _ >Juergen Braukmann juergen.braukmann(a)gmx.de| -o)/ / (_)__ __ ____ __ >Tel: 0201-743648 dk4jb(a)db0qs.#nrw.deu.eu | /\\ /__/ / _ \/ // /\ \/ / >===========================================_\_v __/_/_//_/\_,_/ /_/\_\ > >-- >To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com >For additional commands send e-mail to suse-linux-e-help(a)suse.com >Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/ > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"> <HEAD> <META content=text/html;charset=iso-8859-1 http-equiv=Content-Type> <META content='"MSHTML 4.72.2106.6"' name=GENERATOR> </HEAD> <BODY> <DIV><FONT size=2>hi</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>i still can't get it working. i turned on extra messages and it reports "CHANNEL B1", then "CARRIER 64000", then "NO CARRIER". the terminal adaptor documentation states that 'NO CARRIER' is returned if:</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>"Valid carrier not detected within period specified by register S7, or carrier lost for 300ms or more. Message is also sent when incompatible protocols are configured for the originating and answering ISDN terminal adaptor."</EM></EM></FONT></DIV> <DIV> <DIV><FONT size=2>since register S7 is 30seconds, I presume that the problem is with protocols. When using the terminal adaptor in a win95 machine, protocol errors were also periodically experienced.</FONT></DIV> <DIV><FONT size=2> </FONT></DIV> <DIV><FONT size=2>any more ideas?</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>thanks again,</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV> </DIV> <DIV><FONT size=2>Andrew Smith</FONT></DIV> <DIV><FONT size=2></FONT> </DIV></DIV> <DIV><FONT face=Arial size=2>-----Original Message-----From: Juergen Braukmann <<A href="mailto:juergen.braukmann@ruhr-west.de">juergen.braukmann(a)ruhr-west.de</A>>To: SuSE Linux English <<A href="mailto:suse-linux-e@suse.com">suse-linux-e(a)suse.com</A>>Date: 22 December 1999 16:11Subject: Re: [SLE] 'NO CARRIER' error with ISDN<BR></DIV></FONT>>jan vermeulen wrote:<BR>>> <BR>>> > Andrew Smith wrote:>> <BR>>> > i have a BT isdn ignition line and a terminal adapter (the adapter is>> > like a modem). everything works fine under windows, but under linux,>> > the adapter reports 'NO CARRIER' when sent 'ATD<phone-number>'.>> >my collegues had similar problems when they started with the terminal>adapter. I remember they use the dial string ATDI<number>. Maybe, you>can experiment with the usual X3 (ATX3DI<number>) as well...><BR>>Juergen<BR>><BR>>(PS: probably won't have the dial string before the new year... if it>persists mail me direct, I'll try to find so. after x-mas)><BR>><BR>>> You will need to run X75 on top of HDLC. Do you?>> <BR>>> JV<BR>><BR>>-- >=========================================== __ _>Juergen Braukmann <A href="mailto:juergen.braukmann@gmx.de|">juergen.braukmann(a)gmx.de|</A> -o)/ / (_)__ __ ____ __>Tel: 0201-743648 <A href="mailto:dk4jb@db0qs.#nrw.deu.eu">dk4jb(a)db0qs.#nrw.deu.eu</A> | /\\ /__/ / _ \/ // /\ \/ />===========================================_\_v __/_/_//_/\_,_/ /_/\_\><BR>>-- <BR>>To unsubscribe send e-mail to <A href="mailto:suse-linux-e-unsubscribe@suse.com">suse-linux-e-unsubscribe(a)suse.com</A>>For additional commands send e-mail to <A href="mailto:suse-linux-e-help@suse.com">suse-linux-e-help(a)suse.com</A> >Also check the FAQ at <A href="http://www.suse.com/Support/Doku/FAQ/">http://www.suse.com/Support/Doku/FAQ/</A>><BR>></BODY>

3 2

Re: [SLE] Can't even get my Network card installed :`(
by fountai＠hursley.ibm.com 23 Dec '99

23 Dec '99

> Is this a one time thing or every time I boot? YaST and the kernel between them sort things out so that you only need to set it up once. It's put back automagically when you reboot. > >There is a file called /proc/pci in your filesystem. (Actually it's a > >technical trick, it's not on the disk at all, but that doesn't matter.) > >If you look at it with "cat /proc/pci" it'll show what is connected to > >the PCI bus. Most of this stuff is irrelevant, but if you skim it you > >should see an entry for the network adapter - if the card is working. > >Email me (privately) the output of this command if you like. > > Yes, I tried that after your first response, no network adapter in there > yet. > Has any of this got to do with loop back that I set when I first installed? This is the source of your problem. Your NIC is not being detected on the PCI bus. This is probably not a Linux problem - it's more likely hardware. Reboot the machine, and watch carefully for error messages near the start of the boot sequence. When it's rebooted type "dmesg" (which lists the boot up messages) and see if there are any problems listed there. (The PCI probe is normally right at the top.) If you can, email me (privately) the output of /proc/pci and dmesg. It seems you have a conflict or a duff card. Try swapping the NIC card. I presume you have 2. Try moving the card to a different PCI slot on the motherboard. Some machines like this. When you boot up is there a BIOS screen which describes the hardware which is attached? Some machines tell you about the graphics adapter, SCSI card, NIC, etc which are on the PCI bus. If you have this feature, what does it say? Does the machine dual boot? If it does, what does Windows think about the NIC? Basically, it appears you have a low level problem. You need to find a clue as to what it is. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

1 0

[SLE] Upgrading to 6.3 trials and tribulations...
by zentena＠hophead.dyndns.org 23 Dec '99

23 Dec '99

Hi all, My copy of 6.3 hit the porch late yesterday afternoon. So I spent some time upgrading. Everything was going fine until I hit CD #5. No go it couldn't be read. I got the red screen of death from yast and had to stop the upgrade. Well by this point the whole base system was upgraded so I figured no problem I'll just do an upgrade by FTP. Well there are allot of upgrades already on the FTP site 6.3.0.3 already-) No problem it's just keeps clicking along until it got to the kernel src. More red stuff. A cryptic error message that made no real sense. Something like file couldn't be read. I didn't know if it couldn't read the file from the FTP site or my disk. I finally figured out it didn't like something on my end. Plenty of room on /usr where the kernel src would go. So I figured maybe it was a problem with some sort of conflict with the old src in /usr/src/linux so I rm that. No go of course. Well I don't really need the src from suse so I went into package selection and deleted it. Restarted things and everything clipped along for awhile until I hit one of the java packages. Yup a big file. Same sort of problems. At this point I figured out the problem wasn't disk space on /usr but /var. Okay now to find where all the diskspace went. /var/log was fine. /var/spool is a separate disk forget partition. Well buried in /var/adm/backup/rpmdb were a bunch of old files that looked to be leftover from past upgrades. Big files using up a bunch of space. Well I wasn't sure what the files were for but since they were all dated they looked old and I deleted the oldest. Viola things now worded fine. From here on in things went fairly okay. Now time to start sax and see how it's been improved. Ooops sax doesn't start. The guess it makes about my video card is wrong and causes it to fail. No problem I using the cmd line switch to set the right card. It starts up fine and my new monitor is in the database. But the settings are actually a little more conservative then actual. Not a problem IMHO. Better safe then sorry. So when I go and check the setup everything looks great. But [you knew there would be a but] the monitor is being pushed at a higher refresh rate then it should-( Any one know the simplest way to change that. In addition I thought somebody had said Sax now can read the plug and play info from the monitor? Sax was able to probe my video card fine but couldn't get any info from the monitor. In my search for what happened to all my disk space I noticed that / was at 100%. OOOPS. Well I couldn't figure it out so I started just looking around /root had a massive du report. It looked like the last time windows had crashed it wrote a bunch of files to /root/.kde/share Most of the files were empty but still more proof of the dangers of using Windows even to play a video game. So all in all outside of the bad CD most things went okay. Better error messages would help though-) So how do I get a replacement CD? Nick -- -------------------------------------------------- Nick Zentena "Microsoft has unjustifiably jeopardized the stability and security of the operating system." U.S. District Judge Thomas Penfield Jackson Nov 5/1999 -------------------------------------------------- -- To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

1 0