Linux-Hardware Digest #464, Volume #9 Fri, 19 Feb 99 12:13:39 EST
Contents:
Re: ethernet problems (James Russell)
Re: Help: Viper550 with AMD K6-2 and Linux... (Johnny Stenback)
RH5.2 unable to install to DPT PM3334 Raid? (Lambeth IT Support)
Re: SCSI CDROM Problem (Chien Wang)
RedHat 5.2/ how to install/update ghostscript 4.03 to 5.10? (doug)
just making sure (diff between cua2 ttyS2) ([EMAIL PROTECTED])
Re: Problems when removing SCSI-HDD (Stuart R. Fuller)
Re: Cheap PCI SCSI? (Stuart R. Fuller)
Re: Winmodems and Linux? ("~The Seventh Sign~")
----------------------------------------------------------------------------
From: James Russell <[EMAIL PROTECTED]>
Subject: Re: ethernet problems
Date: Thu, 18 Feb 1999 12:11:32 -0500
The Seeker wrote:
>
> First of all : I am (yet) a NEWBIE with linux (as much as it concerns
> troubleshooting!). So if can help and willing to answer, please be as
> specific as possible in your answer.
>
> I believe that this question will have been posted a million times !!! Linux
> is not the operating system with the easiest way to make your lan work ! I
> have done everything i could have imagined in order to make my lan work
> (with the linux pc) but all my attempts have failed. So i ask help from you.
> This email has as much info as i have imagined that would be helpful. If you
> need more info in order to help or any any any idea that could lead to the
> solution, please reply to me and i will provide as much info as i can & you
> need.
>
> My LAN has 4 PCs. Three with win98 (192.168.0.2 - 192.168.0.4) and one with
> win98 & linux redhat 5.0 (192.168.0.1). Windows Plug & play has worked fine
> (it happens now and then !! hehe) and all the network cards have been
> configured in the windows environment. In the win environment i can ping all
> pcs and the lan is running ok. TCP-IP protocol has been setup normally.
>
> When i boot with linux, i cant even ping the other pcs. In fact, i am not
> sure whether linux detects or does not detect my network card (in the
> 192.168.0.1 pc). In the starting procedure (dmesg) only one message appears
> (related to eth0) and this is the following:
> -delaying eth0 initialisation
>
> I have no idea what this means. I thought that this message appears because
> linux failed to detect my network card, but if i "cat" the /proc/pci file i
> see that linux does that.
> More talking would be waste of time. Here is the info of my network card and
> i have attached the configuration files that (i think) are related to the
> network card and it's configuration. I dont know whether there is a conflict
> (but if i boot in win98 no conflict appears) so i have also attached some
> files that might help
>
> The card is a CNet PowerNIC network interface card (NE2000 combatible) pci
> and i have done anything the instructions say, in order to make linux detect
> my card. But no light found in instructions........
>
> I dont know what else could i do. All my friend of those who seemed to know
> something about linux, have no idea what goes wrong (but now i am so sure
> whether they are less newbies than me). Anyway, these newgroups i believe
> are my last option.
>
> Thanks to all who spent time reading all of this stuff !!
>
> The Seeker
>
> *** SORRY ABOUT THE LENGTH OF THIS MESSAGE - BUT SINCE NO ATTACHMENTS ARE
> SUPPORTED, THIS WAS THE ONLY WAY :o( ***
>
> [devices] /proc/devices
> Character devices:
> 1 mem
> 2 pty
> 3 ttyp
> 4 ttyp
> 5 cua
> 7 vcs
> 10 misc
> 14 sound
>
> Block devices:
> 1 ramdisk
> 2 fd
> 3 ide0
> 9 md
> 11 sr
>
> [dma] /proc/dma
> 1: Sound Blaster8
> 2: floppy
> 4: cascade
> 5: Sound Blaster16
>
> [dmesg] , i suppose you know about that !!
> Console: 16 point font, 400 scans
> Console: colour VGA+ 80x25, 1 virtual console (max 63)
> pcibios_init : BIOS32 Service Directory structure at 0x000fac10
> pcibios_init : BIOS32 Service Directory entry at 0xfb090
> pcibios_init : PCI BIOS revision 2.10 entry at 0xfb270
> Probing PCI hardware.
> Warning : Unknown PCI device (8086:7190). Please read include/linux/pci.h
> Warning : Unknown PCI device (8086:7191). Please read include/linux/pci.h
> Warning : Unknown PCI device (12d2:18). Please read include/linux/pci.h
> Warning : Unknown PCI device (121a:2). Please read include/linux/pci.h
> Calibrating delay loop.. ok - 349.80 BogoMIPS
> Memory: 127620k/131072k available (736k kernel code, 384k reserved, 2156k
> data)
> Swansea University Computer Society NET3.035 for Linux 2.0
> NET3: Unix domain sockets 0.13 for Linux NET3.035.
> Swansea University Computer Society TCP/IP for NET3.034
> IP Protocols: IGMP, ICMP, UDP, TCP
> VFS: Diskquotas version dquot_5.6.0 initialized
> Checking 386/387 coupling... Ok, fpu using exception 16 error reporting.
> Checking 'hlt' instruction... Ok.
> Linux version 2.0.32 ([EMAIL PROTECTED]) (gcc version 2.7.2.3) #1 Wed
> Nov 19 00:46:45 EST 1997
> Starting kswapd v 1.4.2.2
> Serial driver version 4.13 with no serial options enabled
> tty00 at 0x03f8 (irq = 4) is a 16550A
> tty01 at 0x02f8 (irq = 3) is a 16550A
> Real Time Clock Driver v1.07
> Ramdisk driver initialized : 16 ramdisks of 4096K size
> ide: i82371 PIIX (Triton) on PCI bus 0 function 17
> ide0: BM-DMA at 0xf000-0xf007
> ide1: BM-DMA at 0xf008-0xf00f
> hda: FUJITSU MPB3043ATU, 4125MB w/0kB Cache, CHS=525/255/63
> hdb: QUANTUM FIREBALL ST1.6A, 1539MB w/81kB Cache, CHS=782/64/63
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> Floppy drive(s): fd0 is 1.44M, fd1 is 1.2M
> FDC 0 is a post-1991 82077
> md driver 0.35 MAX_MD_DEV=4, MAX_REAL=8
> scsi : 0 hosts.
> scsi : detected total.
> Partition check:
> hda: hda1 hda2 < hda5 hda6 > hda3 hda4
> hdb: hdb1 hdb2 < hdb5 >
> RAMDISK: Compressed image found at block 0
> VFS: Mounted root (ext2 filesystem).
> aha152x: BIOS test: passed, detected 1 controller(s)
> aha152x0: vital data: PORTBASE=0x340, IRQ=11, SCSI ID=7, reconnect=enabled,
> parity=enabled, synchronous=disabled, delay=100, extended
> translation=disabled
> aha152x: trying software interrupt, ok.
> scsi0 : Adaptec 152x SCSI driver; $Revision: 1.18 $
> scsi : 1 host.
> Vendor: PLEXTOR Model: CD-ROM PX-20TS Rev: 1.01
> Type: CD-ROM ANSI SCSI revision: 02
> Detected scsi CD-ROM sr0 at scsi0, channel 0, id 1, lun 0
> VFS: Mounted root (ext2 filesystem) readonly.
> Trying to unmount old root ... okay
> Adding Swap: 56220k swap-space (priority -1)
> aha152x: ignoring spurious interrupt, nothing to do
> QUEUE STATUS:
> issue_SC:
> current_SC:
> none
> disconnected_SC:
>
> waiting: SCSISEQ (); SCSISIG (DATA OUT); INTSTAT (lo); SSTAT (SELINGO
> BUSFREE PHASECHG ); SSTAT (); SXFRCTL0 (CH1 ); SIGNAL (); SELID (ff), SSTAT2
> (SEMPTY ); SFCNT (0); SCSICNT (0), OFFCNT(0), SSTAT4 (); DMACNTRL0 (16BIT
> PIO READ ); DMASTAT (DFIFOEMP )
> enabled interrupts ()
> Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996
> SB 4.16 detected OK (220)
> Installed 0
> sysctl: ip forwarding off
> Swansea University Computer Society IPX 0.34 for NET3.035
> IPX Portions Copyright (c) 1995 Caldera, Inc.
> Appletalk 0.17 for Linux NET3.035
> CSLIP: code copyright 1989 Regents of the University of California
> PPP: version 2.2.0 (dynamic channel allocation)
> PPP Dynamic channel allocation code copyright 1995 Caldera, Inc.
> PPP line discipline registered.
> registered device ppp0
> Swansea University Computer Society IPX 0.34 for NET3.035
> IPX Portions Copyright (c) 1995 Caldera, Inc.
> Appletalk 0.17 for Linux NET3.035
> VFS: Disk change detected on device 02:00
> end_request: I/O error, dev 02:00, sector 0
> PPP: ppp line discipline successfully unregistered
> VFS: Disk change detected on device 02:00
>
> [ifeth0-cfg] /etc/sysconfig/network-scripts/ifeth0-cfg
> DEVICE=eth0
> USERCTL=no
> ONBOOT=yes
> BOOTPROTO=none
> BROADCAST=192.168.0.255
> NETWORK=192.168.0.4:x
> NETMASK=255.255.255.0
> IPADDR=192.168.0.1
>
> [interrupts] /proc/interrupts
> 0: 240310 timer
> 1: 7034 keyboard
> 2: 0 cascade
> 4: 44 + serial
> 6: 24 + floppy
> 7: 1 sound blaster
> 8: 1 + rtc
> 11: 34 + aha152x
> 13: 1 math error
> 14: 26112 + ide0
>
> [ioports] /proc/ioports
> 0000-001f : dma1
> 0020-003f : pic1
> 0040-005f : timer
> 0060-006f : keyboard
> 0070-007f : rtc
> 0080-009f : dma page reg
> 00a0-00bf : pic2
> 00c0-00df : dma2
> 00f0-00ff : npu
> 01f0-01f7 : ide0
> 0220-022f : sound blaster
> 02f8-02ff : serial(auto)
> 0340-035f : aha152x
> 03c0-03df : vga+
> 03f0-03f5 : floppy
> 03f6-03f6 : ide0
> 03f7-03f7 : floppy DIR
> 03f8-03ff : serial(auto)
> f000-f007 : IDE DMA
> f008-f00f : IDE DMA
>
> [network] /etc/sysconfig/network/network
> NETWORKING=yes
> FORWARD_IPV4=no
> HOSTNAME=veneficus
> GATEWAYDEV=
> GATEWAY=
>
> [pci] /proc/pci
>
> PCI devices found:
> Bus 0, device 15, function 0:
> Ethernet controller: Realtek 8029 (rev 0).
> Medium devsel. IRQ 5.
> I/O at 0xe400.
> Bus 0, device 13, function 0:
> Multimedia video controller: 3Dfx Unknown device (rev 2).
> Vendor id=121a. Device id=2.
> Fast devsel. Fast back-to-back capable. IRQ 255.
> Prefetchable 32 bit memory at 0xe7000000.
> Bus 0, device 2, function 3:
> Bridge: Intel 82371AB PIIX4 Power Management (rev 2).
> Medium devsel. Fast back-to-back capable.
> Bus 0, device 2, function 2:
> USB Controller: Intel 82371AB PIIX4 (rev 1).
> Medium devsel. Fast back-to-back capable. IRQ 12. Master Capable.
> Latency=64.
> I/O at 0xe000.
> Bus 0, device 2, function 1:
> IDE interface: Intel 82371AB 430TX PIIX4 (rev 1).
> Medium devsel. Fast back-to-back capable. Master Capable.
> Latency=64.
> I/O at 0xf000.
> Bus 0, device 2, function 0:
> ISA bridge: Intel 82371AB PIIX4 (rev 2).
> Medium devsel. Fast back-to-back capable. Master Capable. No
> bursts.
> Bus 1, device 0, function 0:
> VGA compatible controller: Unknown vendor Unknown device (rev 16).
> Vendor id=12d2. Device id=18.
> Medium devsel. Fast back-to-back capable. IRQ 10. Master Capable.
> Latency=64. Min Gnt=3.Max Lat=1.
> Non-prefetchable 32 bit memory at 0xe4000000.
> Prefetchable 32 bit memory at 0xe6000000.
> Bus 0, device 1, function 0:
> PCI bridge: Intel Unknown device (rev 2).
> Vendor id=8086. Device id=7191.
> Medium devsel. Master Capable. Latency=64. Min Gnt=136.
> Non-prefetchable 32 bit memory at 0x40010100.
> Non-prefetchable 32 bit memory at 0x22a0d0d0.
> Non-prefetchable 32 bit memory at 0xe5f0e400.
> Non-prefetchable 32 bit memory at 0xe6f0e600.
> Bus 0, device 0, function 0:
> Host bridge: Intel Unknown device (rev 2).
> Vendor id=8086. Device id=7190.
> Medium devsel. Master Capable. Latency=64.
> Prefetchable 32 bit memory at 0xe0000000.
I don't think that Linux will detect that card out of the blue. Try
loading the network module ne2k-pci at the shell with this...
insmod ne2k-pci
Then look in /proc/interrupts and /proc/ioports to see if the card shows
up...
If so, then just run '/etc/rc.d/init.d/network restart'
This makes RedHat Linux reload all the ifconfig stuff, the routing.
If you can ping other systems, then you just need to go into linuxconf
and add make sure the module for eth0 (under networking host adapter) is
loading the ne2k-pci module.
That might help you.
Jim
--
James Russell [EMAIL PROTECTED]
IT Engineer, Trinity Academy; Waterbury, CT; USA
------------------------------
From: Johnny Stenback <[EMAIL PROTECTED]>
Subject: Re: Help: Viper550 with AMD K6-2 and Linux...
Date: Thu, 18 Feb 1999 19:19:34 +0200
"adam.cheney" wrote:
>
> Hi All,
>
> I'm just about to start buying and building my new PC, and I've already
> decided that it will be running Linux on a K6-2 at 350MHz. I need a
> shit-hot graphics card, and several people have recommended the
> Viper550. However, Diamond support have just told me that the Viper has
> problems with VIA and ALI chipsets, because they don't cascade IRQ's
> properly, and that they "can't be sure that it would be a problem in
> Linux".
I don't know where it works or not but I just got one and I did get it
to work in linux (with the newest XFree) however the performance sucks,
you'll haveto use the SVGA driver, ie no acceleration...
Please correct me if I'm wrong...
>
> Can anyone tell me if it's possible to use the Viper550 under Linux with
> a Super7 mainboard with those chipsets (All AMD's recommended mainboards
> have either the ALI or the VIA chipsets)?
> Can anyone recommend another mainboard?
> Can anyone comment on my choice of graphics card and possibly recommend
> another (RIVA TNT chipset)?
>
I wouldn't buy it unless my above statement is incorrect...
> Thanks in andvance to any gurus who can help me.
>
> Cheers - Adam...
--
jst
------------------------------
From: Lambeth IT Support <[EMAIL PROTECTED]>
Subject: RH5.2 unable to install to DPT PM3334 Raid?
Date: Thu, 18 Feb 1999 17:24:32 +0000
I'm trying to load RH5.2 on a twin PentPro system which has a DPT
(PM3334) raid controller.
However during install the process hangs whilst trying to identify the
controller.
The message is: "Scanning EATA DMA Adapter SCSI bus..."
The motherboard is Intel M/B with on-board SCSI UW controller. However I
have tried using the on-board SCSI port with a CD drive as well as
attempting to load from another system via FTP (tried this to disable
the on-board SCSI controller).
I think I have setup the Raid controller correctly (once with OS as
"Other", another time selecting the option DPTMGR manager gives as
Linux). I have read "....HOWTO/mini/DPT-Hardware-RAID", but once the
array is setup, I think it then assumes the install will work.
Can anyone help?
Chris
------------------------------
From: Chien Wang <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc,comp.os.linux.setup
Subject: Re: SCSI CDROM Problem
Date: Fri, 19 Feb 1999 09:09:12 -0600
Hi Gerald,
Did you save the old kernel? because it seems that the old kernel was able
to recognize the cdrom, and from your e-mail, it assigned it to
/dev/sr0(which is the same as /dev/scd0 but not /dev/sdc). Once you can get
the proper kernel that detects your CDROM, then you can go to /dev and do a
MAKEDEV sr0, then you should be able to mount it, i.e. mount -t iso9660
/dev/sr0 /cdrom(or something like that).
Good luck,
Chien
Pavel Greenfield wrote:
> I'm sorry, I meant /dev/sdc. I guess it's still not right. Thanks...
>
> Gerald Willmann wrote:
>
> > On Fri, 19 Feb 1999, Pavel Greenfield wrote:
> >
> > > I can't seem to get my SCSI Toshiba CDRom to work. (It's Toshiba
> > > XM-5401TA.)
> > > (I tried >>>mount /dev/hdc /cdrom, and mount would respond /dev/sdc is
> >
> > try /dev/scd0 - it's definitely not hdc if you have a scsi cdrom
> >
> > Gerald
------------------------------
From: doug <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,comp.os.linux.misc
Subject: RedHat 5.2/ how to install/update ghostscript 4.03 to 5.10?
Date: Fri, 19 Feb 1999 11:38:07 -0500
Hi,
I'm having some problems in getting the newer (5.10) ghostscript
package
installed on my RedHat 5.2 system. It currently has 4.03 ghostscript. If
I use rpm -i or rpm -u, the package is installed OK, but it breaks the
printtool (i.e. in the filters menu there are only 2 selections instead
of
the normal many. it shows only postscript & plain text filters). If I
try
gs --version, it errors out with unable to open libraries. If I then
uninstall
the package, and re-install the rpms from the 5.2 CD everything is fine.
I'm installing the fonts, (gs/urw) & the latest printtool and
printfilter
packages. I've tried many combinations of the packages. It seems to me
that it
shouldn't be this hard, I mean I haven't had this type of trouble until
this.
If anyone has successfully done the upgrade from the 5.2 CD
ghostscript(4.03)
to the newer ghostscript 5.10 and has it working I'd sure like to know
if there
is a magical sequence of events to perform that I don't know about.
Thanks for
any help. Doug
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.misc,comp.os.linux.setup
Subject: just making sure (diff between cua2 ttyS2)
Date: Thu, 18 Feb 1999 14:47:03 GMT
Hi, i run linux slackware and recently upgraded (well backed up formated
reinstalled restored ;> ) to slackware 3.6.0 and it all went smoothly. but
when i setup ppp and then tried the ppp-go script it gave me this:
tty_io.c: process 109 (pppd) used obsolete /dev/cua2 - update software to use
/dev/ttyS2
tty_io.c: process 109 (pppd) used obsolete /dev/cua2 - update software to use
/dev/ttyS2
tty_io.c: process 112 (pppd) used obsolete /dev/cua2 - update software to use
/dev/ttyS2
tty_io.c: process 115 (pppd) used obsolete /dev/cua2 - update software to use
/dev/ttyS2
tty_io.c: process 118 (pppd) used obsolete /dev/cua2 - update software to use
/dev/ttyS2
now i just went to the /dev/ dir and mv'd /dev/modem -> /dev/modem.bak and
made a sym lnk modem file linked to /dev/ttyS2 and everything *seems* to be
working ok... my question is: IS this fix too half ass? I have had fixes in
the past that really <so i have been told> shouldn't have worked.
Last question: wht is the diff between cua and tty ? they seem to be the same
but the computer seems to think otherwise.
thank you,
-Gaiko
Gaikokujin Kyofusho
Student Extraordinare & UN*X Guru Wannbe
[EMAIL PROTECTED]
============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
From: [EMAIL PROTECTED] (Stuart R. Fuller)
Subject: Re: Problems when removing SCSI-HDD
Reply-To: [EMAIL PROTECTED]
Date: Thu, 18 Feb 1999 17:00:03 GMT
Stefan Wuerthle ([EMAIL PROTECTED]) wrote:
: Hi,
:
: when I remove my first SCSI-HDD (Win98; /dev/sda) I can't boot any
: more from my second SCSI-HDD (Linux; /dev/sdb) because /dev/sdb
: becomes now /dev/sda.
:
: How can I solve this problem without installing Linux once again?
Don't remove the first SCSI-HDD.
If you want to permanently remove the first drive, what I did to resolve that
problem was to buy a cheap, small SCSI drive, and make it the "first drive".
Alternatively, change your /etc/fstab to replace /dev/sdb with /dev/sda, and
also change the root device name in the kernel image to point to /dev/sda.
Use the "/sbin/rdev" command to do that.
Stu
------------------------------
From: [EMAIL PROTECTED] (Stuart R. Fuller)
Subject: Re: Cheap PCI SCSI?
Reply-To: [EMAIL PROTECTED]
Date: Thu, 18 Feb 1999 17:00:03 GMT
Dae ([EMAIL PROTECTED]) wrote:
: Is there a Lowcost (hoping for around $50 USD) PCI SCSI card I can get
: that will allow me to hook up, CD-RW,ZIP, scanner, and possble and
: internal HD that will work with Linux (Red Hat 5.2) with little/so
: problems with setup?
Most any PCI-SCSI card with the NCR 53c810 chip.
Stu
------------------------------
From: "~The Seventh Sign~" <[EMAIL PROTECTED]>
Subject: Re: Winmodems and Linux?
Date: Thu, 18 Feb 1999 12:57:47 -0500
No drivers for winmodems and there should never be any drivers for
winmodems they hog CPU resources. It is like having a bicycle car when you
need a motorized car.
--
~The �eventh �ign ~
Life on this planet has such limited visions.
If aliens in outerspace tapped into the Internet what would they say?
A. Ashton <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
:This may be obvious to some:
:Can you use a USR WinModem with Linux? I've been thinking of kicking
:the Microsoft habit but I don't wanna have to buy a new modem. I know
:WinModems are supposed to only work in Windows (hence the name) but I
:figured maybe they weren't counting on Linux when they made them. Are
:there drivers for these? Please post or email any help. THanks! A.
:Ashton
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list (and comp.os.linux.hardware) via:
Internet: [EMAIL PROTECTED]
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Hardware Digest
******************************
