Linux-Hardware Digest #913, Volume #13 Sun, 19 Nov 00 03:13:03 EST
Contents:
Re: "Jumpy" mouse in Linux... console and X (Matt Sollie)
Re: SB Awe 64 Configuration ("Chas")
Re: Tape drive troubles: HP colorardo 20GB TR5 ("Jean-Michel F Moreau")
Re: Promise Ultra100, IBM 75GXP - Slow and small??? (James Richard Tyrer)
Re: newbie problems (James Richard Tyrer)
Re: Linux for the 486 (Lew Pitcher)
alsa problem - no sound (Andreas Hiltenkamp)
Re: Old School (Michael V. Ferranti)
Re: Old School (Michael V. Ferranti)
----------------------------------------------------------------------------
From: Matt Sollie <[EMAIL PROTECTED]>
Subject: Re: "Jumpy" mouse in Linux... console and X
Date: Sun, 19 Nov 2000 05:20:02 GMT
Nevermind. I figured it out
> I have a PII 300 on a Intel AL440LX Motherboard. I am running
> Debian(woody), and am having problems with my mouse.
>
> The mouse I am using is a Logitech MouseMan+ PS/2, and when I use in in
> gpm, or X it.. I hope I can explain this well... "jumps"; when I start
> movind the mouse, the cursor does not move untill I stop moving the
> mouse, at which point the cursor goes to where you moved the mouse to. I
> have no clue what is causing this, but I am thinking it is the
> motherboard, as I used to have this problem when I ran SUSE 6.1 on this
> same box, with a different PS/2 mouse, with the same results. BTW, at
> the moment, I am running XFree86 4. Thanks for any help you can give me.
>
> -Matt
------------------------------
From: "Chas" <[EMAIL PROTECTED]>
Subject: Re: SB Awe 64 Configuration
Date: Sat, 18 Nov 2000 23:26:40 -0600
One thing.. my CDROM works great it is the MP3 files
that have the issue...
I did look in /etc/modules.conf and this is what I found
alias eth0 3c90x
alias parport_lowlevel parport_pc
alias sound-slot-0 sb
options sound dmabuf=1
options opl3 io=0x388
alias midi awe_wave
post-install awe_wave /bin/sfxload /etc/midi/GU11-ROM.SF2
options sb io=0x220 irq=5 dma=1 dma16=5 mpu_io=0x330
"Chas" <[EMAIL PROTECTED]> wrote in message
news:neJR5.601$[EMAIL PROTECTED]...
> I have a dual processer machine and have a
> SBAwe64.
> I have run the soundconf utility but still am getting
> scratchy audio..
> Included is my isapnp.conf file.. I think the IRQ might
> be the problem..
> TIA
> # $Id: pnpdump_main.c,v 1.23 2000/04/19 22:49:44 fox Exp $
>
> # Release isapnptools-1.22
>
> #
>
> # This is free software, see the sources for details.
>
> # This software has NO WARRANTY, use at your OWN RISK
>
> #
>
> # For details of the output file format, see isapnp.conf(5)
>
> #
>
> # For latest information and FAQ on isapnp and pnpdump see:
>
> # http://www.roestock.demon.co.uk/isapnptools/
>
> #
>
> # Compiler flags: -DREALTIME -DNEEDSETSCHEDULER -DABORT_ONRESERR
>
> #
>
> # Trying port address 0273
>
> # Board 1 has serial identifier bc 0e 11 c4 1c c1 00 8c 0e
>
> # (DEBUG)
>
> (READPORT 0x0273)
>
> (ISOLATE PRESERVE)
>
> (IDENTIFY *)
>
> (VERBOSITY 2)
>
> (CONFLICT (IO FATAL)(IRQ FATAL)(DMA FATAL)(MEM FATAL)) # or WARNING
>
> # Card 1: (serial identifier bc 0e 11 c4 1c c1 00 8c 0e)
>
> # Vendor Id CTL00c1, Serial Number 236045340, checksum 0xBC.
>
> # Version 1.0, Vendor version 1.0
>
> # ANSI string -->Creative SB AWE64 PnP<--
>
> #
>
> # Logical device id CTL0042
>
> # Device supports vendor reserved register @ 0x38
>
> # Device supports vendor reserved register @ 0x39
>
> # Device supports vendor reserved register @ 0x3a
>
> # Device supports vendor reserved register @ 0x3d
>
> # Device supports vendor reserved register @ 0x3f
>
> #
>
> # Edit the entries below to uncomment out the configuration required.
>
> # Note that only the first value of any range is given, this may be
changed
> if required
>
> # Don't forget to uncomment the activate (ACT Y) when happy
>
> (CONFIGURE CTL00c1/236045340 (LD 0
>
> # ANSI string -->Audio<--
>
> # Multiple choice time, choose one only !
>
> # Start dependent functions: priority preferred
>
> # IRQ 5.
>
> # High true, edge sensitive interrupt (by default)
>
> (INT 0 (IRQ 5 (MODE +E)))
>
> # First DMA channel 1.
>
> # 8 bit DMA only
>
> # Logical device is not a bus master
>
> # DMA may execute in count by byte mode
>
> # DMA may not execute in count by word mode
>
> # DMA channel speed in compatible mode
>
> (DMA 0 (CHANNEL 1))
>
> # Next DMA channel 5.
>
> # 16 bit DMA only
>
> # Logical device is not a bus master
>
> # DMA may not execute in count by byte mode
>
> # DMA may execute in count by word mode
>
> # DMA channel speed in compatible mode
>
> (DMA 1 (CHANNEL 5))
>
> # Logical device decodes 16 bit IO address lines
>
> # Minimum IO base address 0x0220
>
> # Maximum IO base address 0x0220
>
> # IO base alignment 1 bytes
>
> # Number of IO addresses required: 16
>
> (IO 0 (SIZE 16) (BASE 0x0220))
>
> # Logical device decodes 16 bit IO address lines
>
> # Minimum IO base address 0x0330
>
> # Maximum IO base address 0x0330
>
> # IO base alignment 1 bytes
>
> # Number of IO addresses required: 2
>
> (IO 1 (SIZE 2) (BASE 0x0330))
>
> # Logical device decodes 16 bit IO address lines
>
> # Minimum IO base address 0x0388
>
> # Maximum IO base address 0x0388
>
> # IO base alignment 1 bytes
>
> # Number of IO addresses required: 4
>
> (IO 2 (SIZE 4) (BASE 0x0388))
>
> # Start dependent functions: priority acceptable
>
> # IRQ 5, 7, 9 or 10.
>
> # High true, edge sensitive interrupt (by default)
>
> # (INT 0 (IRQ 5 (MODE +E)))
>
> # First DMA channel 0, 1 or 3.
>
> # 8 bit DMA only
>
> # Logical device is not a bus master
>
> # DMA may execute in count by byte mode
>
> # DMA may not execute in count by word mode
>
> # DMA channel speed in compatible mode
>
> # (DMA 0 (CHANNEL 0))
>
> # Next DMA channel 5, 6 or 7.
>
> # 16 bit DMA only
>
> # Logical device is not a bus master
>
> # DMA may not execute in count by byte mode
>
> # DMA may execute in count by word mode
>
> # DMA channel speed in compatible mode
>
> # (DMA 1 (CHANNEL 5))
>
> # Logical device decodes 16 bit IO address lines
>
> # Minimum IO base address 0x0220
>
> # Maximum IO base address 0x0280
>
> # IO base alignment 32 bytes
>
> # Number of IO addresses required: 16
>
> # (IO 0 (SIZE 16) (BASE 0x0220))
>
> # Logical device decodes 16 bit IO address lines
>
> # Minimum IO base address 0x0300
>
> # Maximum IO base address 0x0330
>
> # IO base alignment 48 bytes
>
> # Number of IO addresses required: 2
>
> # (IO 1 (SIZE 2) (BASE 0x0300))
>
> # Logical device decodes 16 bit IO address lines
>
> # Minimum IO base address 0x0388
>
> # Maximum IO base address 0x0388
>
> # IO base alignment 1 bytes
>
> # Number of IO addresses required: 4
>
> # (IO 2 (SIZE 4) (BASE 0x0388))
>
> # Start dependent functions: priority acceptable
>
> # IRQ 5, 7, 9 or 10.
>
> # High true, edge sensitive interrupt (by default)
>
> # (INT 0 (IRQ 5 (MODE +E)))
>
> # First DMA channel 0, 1 or 3.
>
> # 8 bit DMA only
>
> # Logical device is not a bus master
>
> # DMA may execute in count by byte mode
>
> # DMA may not execute in count by word mode
>
> # DMA channel speed in compatible mode
>
> # (DMA 0 (CHANNEL 0))
>
> # Next DMA channel 5, 6 or 7.
>
> # 16 bit DMA only
>
> # Logical device is not a bus master
>
> # DMA may not execute in count by byte mode
>
> # DMA may execute in count by word mode
>
> # DMA channel speed in compatible mode
>
> # (DMA 1 (CHANNEL 5))
>
> # Logical device decodes 16 bit IO address lines
>
> # Minimum IO base address 0x0220
>
> # Maximum IO base address 0x0280
>
> # IO base alignment 32 bytes
>
> # Number of IO addresses required: 16
>
> # (IO 0 (SIZE 16) (BASE 0x0220))
>
> # Logical device decodes 16 bit IO address lines
>
> # Minimum IO base address 0x0300
>
> # Maximum IO base address 0x0330
>
> # IO base alignment 48 bytes
>
> # Number of IO addresses required: 2
>
> # (IO 1 (SIZE 2) (BASE 0x0300))
>
> # Start dependent functions: priority acceptable
>
> # IRQ 5, 7, 9 or 10.
>
> # High true, edge sensitive interrupt (by default)
>
> # (INT 0 (IRQ 5 (MODE +E)))
>
> # First DMA channel 0, 1 or 3.
>
> # 8 bit DMA only
>
> # Logical device is not a bus master
>
> # DMA may execute in count by byte mode
>
> # DMA may not execute in count by word mode
>
> # DMA channel speed in compatible mode
>
> # (DMA 0 (CHANNEL 0))
>
> # Next DMA channel 5, 6 or 7.
>
> # 16 bit DMA only
>
> # Logical device is not a bus master
>
> # DMA may not execute in count by byte mode
>
> # DMA may execute in count by word mode
>
> # DMA channel speed in compatible mode
>
> # (DMA 1 (CHANNEL 5))
>
> # Logical device decodes 16 bit IO address lines
>
> # Minimum IO base address 0x0220
>
> # Maximum IO base address 0x0280
>
> # IO base alignment 32 bytes
>
> # Number of IO addresses required: 16
>
> # (IO 0 (SIZE 16) (BASE 0x0220))
>
> # Start dependent functions: priority acceptable
>
> # IRQ 5, 7, 9 or 10.
>
> # High true, edge sensitive interrupt (by default)
>
> # (INT 0 (IRQ 5 (MODE +E)))
>
> # First DMA channel 0, 1 or 3.
>
> # 8 bit DMA only
>
> # Logical device is not a bus master
>
> # DMA may execute in count by byte mode
>
> # DMA may not execute in count by word mode
>
> # DMA channel speed in compatible mode
>
> # (DMA 0 (CHANNEL 0))
>
> # Logical device decodes 16 bit IO address lines
>
> # Minimum IO base address 0x0220
>
> # Maximum IO base address 0x0280
>
> # IO base alignment 32 bytes
>
> # Number of IO addresses required: 16
>
> # (IO 0 (SIZE 16) (BASE 0x0220))
>
> # Logical device decodes 16 bit IO address lines
>
> # Minimum IO base address 0x0300
>
> # Maximum IO base address 0x0330
>
> # IO base alignment 48 bytes
>
> # Number of IO addresses required: 2
>
> # (IO 1 (SIZE 2) (BASE 0x0300))
>
> # Logical device decodes 16 bit IO address lines
>
> # Minimum IO base address 0x0388
>
> # Maximum IO base address 0x0388
>
> # IO base alignment 1 bytes
>
> # Number of IO addresses required: 4
>
> # (IO 2 (SIZE 4) (BASE 0x0388))
>
> # Start dependent functions: priority acceptable
>
> # IRQ 5, 7, 9 or 10.
>
> # High true, edge sensitive interrupt (by default)
>
> # (INT 0 (IRQ 5 (MODE +E)))
>
> # First DMA channel 0, 1 or 3.
>
> # 8 bit DMA only
>
> # Logical device is not a bus master
>
> # DMA may execute in count by byte mode
>
> # DMA may not execute in count by word mode
>
> # DMA channel speed in compatible mode
>
> # (DMA 0 (CHANNEL 0))
>
> # Logical device decodes 16 bit IO address lines
>
> # Minimum IO base address 0x0220
>
> # Maximum IO base address 0x0280
>
> # IO base alignment 32 bytes
>
> # Number of IO addresses required: 16
>
> # (IO 0 (SIZE 16) (BASE 0x0220))
>
> # Logical device decodes 16 bit IO address lines
>
> # Minimum IO base address 0x0300
>
> # Maximum IO base address 0x0330
>
> # IO base alignment 48 bytes
>
> # Number of IO addresses required: 2
>
> # (IO 1 (SIZE 2) (BASE 0x0300))
>
> # Start dependent functions: priority acceptable
>
> # IRQ 5, 7, 9 or 10.
>
> # High true, edge sensitive interrupt (by default)
>
> # (INT 0 (IRQ 5 (MODE +E)))
>
> # First DMA channel 0, 1 or 3.
>
> # 8 bit DMA only
>
> # Logical device is not a bus master
>
> # DMA may execute in count by byte mode
>
> # DMA may not execute in count by word mode
>
> # DMA channel speed in compatible mode
>
> # (DMA 0 (CHANNEL 0))
>
> # Logical device decodes 16 bit IO address lines
>
> # Minimum IO base address 0x0220
>
> # Maximum IO base address 0x0280
>
> # IO base alignment 32 bytes
>
> # Number of IO addresses required: 16
>
> # (IO 0 (SIZE 16) (BASE 0x0220))
>
> # Start dependent functions: priority functional
>
> # IRQ 5, 7, 9 or 10.
>
> # High true, edge sensitive interrupt (by default)
>
> # (INT 0 (IRQ 5 (MODE +E)))
>
> # First DMA channel 0, 1 or 3.
>
> # 8 bit DMA only
>
> # Logical device is not a bus master
>
> # DMA may execute in count by byte mode
>
> # DMA may not execute in count by word mode
>
> # DMA channel speed in compatible mode
>
> # (DMA 0 (CHANNEL 0))
>
> # Next DMA channel 5, 6 or 7.
>
> # 16 bit DMA only
>
> # Logical device is not a bus master
>
> # DMA may not execute in count by byte mode
>
> # DMA may execute in count by word mode
>
> # DMA channel speed in compatible mode
>
> # (DMA 1 (CHANNEL 5))
>
> # Logical device decodes 16 bit IO address lines
>
> # Minimum IO base address 0x0220
>
> # Maximum IO base address 0x0280
>
> # IO base alignment 32 bytes
>
> # Number of IO addresses required: 16
>
> # (IO 0 (SIZE 16) (BASE 0x0220))
>
> # Logical device decodes 16 bit IO address lines
>
> # Minimum IO base address 0x0300
>
> # Maximum IO base address 0x0330
>
> # IO base alignment 16 bytes
>
> # Number of IO addresses required: 2
>
> # (IO 1 (SIZE 2) (BASE 0x0300))
>
> # Logical device decodes 16 bit IO address lines
>
> # Minimum IO base address 0x0388
>
> # Maximum IO base address 0x0394
>
> # IO base alignment 4 bytes
>
> # Number of IO addresses required: 4
>
> # (IO 2 (SIZE 4) (BASE 0x0388))
>
> # End dependent functions
>
> (NAME "CTL00c1/236045340[0]{Audio }")
>
> (ACT Y)
>
> ))
>
> #
>
> # Logical device id CTL7002
>
> # Device supports vendor reserved register @ 0x3a
>
> # Device supports vendor reserved register @ 0x3b
>
> # Device supports vendor reserved register @ 0x3d
>
> # Device supports vendor reserved register @ 0x3f
>
> #
>
> # Edit the entries below to uncomment out the configuration required.
>
> # Note that only the first value of any range is given, this may be
changed
> if required
>
> # Don't forget to uncomment the activate (ACT Y) when happy
>
> (CONFIGURE CTL00c1/236045340 (LD 1
>
> # Compatible device id PNPb02f
>
> # ANSI string -->Game<--
>
> # Multiple choice time, choose one only !
>
> # Start dependent functions: priority preferred
>
> # Logical device decodes 16 bit IO address lines
>
> # Minimum IO base address 0x0200
>
> # Maximum IO base address 0x0200
>
> # IO base alignment 1 bytes
>
> # Number of IO addresses required: 8
>
> (IO 0 (SIZE 8) (BASE 0x0200))
>
> # Start dependent functions: priority acceptable
>
> # Logical device decodes 16 bit IO address lines
>
> # Minimum IO base address 0x0200
>
> # Maximum IO base address 0x0208
>
> # IO base alignment 8 bytes
>
> # Number of IO addresses required: 8
>
> # (IO 0 (SIZE 8) (BASE 0x0200))
>
> # End dependent functions
>
> (NAME "CTL00c1/236045340[1]{Game }")
>
> (ACT Y)
>
> ))
>
> #
>
> # Logical device id CTL0022
>
> # Device supports vendor reserved register @ 0x38
>
> # Device supports vendor reserved register @ 0x3a
>
> # Device supports vendor reserved register @ 0x3b
>
> # Device supports vendor reserved register @ 0x3d
>
> # Device supports vendor reserved register @ 0x3f
>
> #
>
> # Edit the entries below to uncomment out the configuration required.
>
> # Note that only the first value of any range is given, this may be
changed
> if required
>
> # Don't forget to uncomment the activate (ACT Y) when happy
>
> (CONFIGURE CTL00c1/236045340 (LD 2
>
> # ANSI string -->WaveTable<--
>
> # Multiple choice time, choose one only !
>
> # Start dependent functions: priority preferred
>
> # Logical device decodes 16 bit IO address lines
>
> # Minimum IO base address 0x0620
>
> # Maximum IO base address 0x0620
>
> # IO base alignment 1 bytes
>
> # Number of IO addresses required: 4
>
> # (IO 0 (SIZE 4) (BASE 0x0620))
>
> # Start dependent functions: priority acceptable
>
> # Logical device decodes 16 bit IO address lines
>
> # Minimum IO base address 0x0620
>
> # Maximum IO base address 0x0680
>
> # IO base alignment 32 bytes
>
> # Number of IO addresses required: 4
>
> (IO 0 (BASE 0x620)) (IO 1 (BASE 0x0A20)) (IO 2 (BASE 0x0E20))
>
> # End dependent functions
>
> (NAME "CTL00c1/236045340[2]{WaveTable }")
>
> (ACT Y)
>
> ))
>
> # End tag... Checksum 0x00 (OK)
>
> # Returns all cards to the "Wait for Key" state
>
> (WAITFORKEY)
>
>
>
>
------------------------------
From: "Jean-Michel F Moreau" <[EMAIL PROTECTED]>
Subject: Re: Tape drive troubles: HP colorardo 20GB TR5
Date: Sat, 18 Nov 2000 21:41:47 -0800
I just thought of that. And I tested doing tar -cvf /dev/st0 /root then I
restored it and it worked perfectly. I also think I found out what was
wrong with taper! Thank you very much for your advice.
--
http://members.tripod.com/jeanmichel_moreau <--- aquarium webpage, email
address
"John Thompson" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Jean-Michel F Moreau wrote:
>
> > I found it. Ok now taper works w/o that wierd error. Now my tape drive
> > appears to be a scsi device. I did a test backup (went fine). Then I
did a
> > test restore. BUT.. most of the directories were restored but WITHOUT
the
> > files. I have no clue why this tape drive is acting funny. Do I need
to
> > set it up some how or.... is there some other step I am missing?
>
> That sounds like a software problem. I haven't used taper in
> quite a while. What happens if you try tar instead? If you can
> determine that the drive works with other software you may get a
> handle on how to fix it so it will work with taper.
>
> --
>
>
> -John ([EMAIL PROTECTED])
------------------------------
From: James Richard Tyrer <[EMAIL PROTECTED]>
Subject: Re: Promise Ultra100, IBM 75GXP - Slow and small???
Date: Sun, 19 Nov 2000 07:40:06 GMT
Jason Kerr wrote:
> I've got an IBM 75GXP 46.1GB drive attached to Promise Ultra100 card,
> running on an older ASUS P55TP4 mobo with the IntelFX chipset and Award
> 4.51 BIOS. I'm running RH7, with a prisitine 2.2.17, patched with Andre
> Hedrick's ide.2.2.17.20000904.
>
> The system boots OK, and the kernel recognizes the card and the drive --
> given the BIOS, that's a good thing. However, I can't (for the life of
> me) get the system to use the card at anything faster than UDMA2, or to
> recognize more than 33.8GB of the 46.1 total.
>
> It'd be a shame to use the card & drive with these limitations, so I'd
> appreciate any help people could provide me.
>
> - How do I set the IDE subsystem to use UDMA5?
> - How do I get the IDE subsystem to recognize the add'l 14GB of space on
> the drive?
>
> (The latter could also be stated as "How do I convince the system to
> ignore the BIOS and recognize the full disk size?")
>
> Here are the details ...
>
> ## LILO is set to use LINEAR rather than CHS
>
> ## kernel src config -
>
> CONFIG_BLK_DEV_IDE=y
> CONFIG_BLK_DEV_IDEDISK=y
> CONFIG_BLK_DEV_IDEPCI=y
> CONFIG_IDEPCI_SHARE_IRQ=y
> CONFIG_BLK_DEV_IDEDMA=y
> CONFIG_IDEDMA_AUTO=y
> CONFIG_IDEDMA_PCI_EXPERIMENTAL=y
> CONFIG_BLK_DEV_PIIX=y
> CONFIG_PIIX_TUNING=y
> CONFIG_BLK_DEV_PDC202XX=y
> CONFIG_PDC202XX_BURST=y
>
> ## kernel boot messages -
> ...
> PDC20267: IDE controller on PCI bus 00 dev 58
> PDC20267: chipset revision 2
> PDC20267: not 100% native mode: will probe irqs later
> PDC20267: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode.
> ide2: BM-DMA at 0xb800-0xb807, BIOS settings: hde:pio, hdf:pio
> ide3: BM-DMA at 0xb808-0xb80f, BIOS settings: hdg:DMA, hdh:pio
> ...
> hde: IBM-DTLA-307045, ATA DISK drive
> ...
> ide2 at 0xe000-0xe007,0xd802 on irq 10
> ...
> hde: IBM-DTLA-307045, 32253MB w/1916kB Cache, CHS=65531/16/63, UDMA(33)
>
> ## The drive is attached @ ide2 .. PIO? It should be UDMA!
My Ultra66 does this too. Try rebooting the system and see if it says DMA?
If you are worried about this you can put the command: "hdparm -d 1
/dev/hde" in your startup files. At the end of "rc.local" is safest.
>
> ## The CHS should read 89355/16/63, but the BIOS is balking at C > 65535
>
> # hdparm -i /dev/hde
>
> /dev/hde:
>
> Model=IBM-DTLA-307045, FwRev=TX6OA50C, SerialNo=YMDYMLN1911
> Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
> RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=40
> BuffType=DualPortCache, BuffSize=1916kB, MaxMultSect=16, MultSect=16
> CurCHS=16383/16/63, CurSects=-66060037, LBA=yes, LBAsects=66055249
> IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
> PIO modes: pio0 pio1 pio2 pio3 pio4
> DMA modes: mdma0 mdma1 mdma2 udma0 udma1 *udma2 udma3 udma4 udma5
>
> ## Negative CurSects? Is CurSects stored in a short int?
> ## LBAsects should be 90069840
> ## DMA modes should be udma5
>
> Suggestions? Pointers? Patches?
>
> As I said, any help would be greatly appreciated.
>
> Thanks,
>
> Jason Kerr
> [EMAIL PROTECTED]
It was my understanding that DMA100 was only with the 2.4 Kernel -- that
the patch for 2.2.1x only provided DMA66.
It is possible that if the drive can't use DMA100 that it is falling back
to DMA33. Some drives come with a utility to fix this problem. Or, you
should be able to download it from IBM.
JRT
------------------------------
From: James Richard Tyrer <[EMAIL PROTECTED]>
Subject: Re: newbie problems
Date: Sun, 19 Nov 2000 07:46:54 GMT
"Paul S. Wilson" wrote:
> Hi Peter,
>
> You should check and make sure that the sbin directory is in your search path.
> Do an echo $PATH (or env, which will display all of your environment variables).
> The output will show you the PATH variable, which will be a list of directories
> separated by colons. The shell uses the directories stored in this variable to
> search for commands; if the command you try to execute is not in the search
> path, the shell won't find it. You can add a directory to your search path with
> the following commands (using your example):
>
> export PATH=$PATH:/sbin -- for bash
> or
> set path = ($PATH /sbin) -- for csh
>
> Paul
>
> >
If you don't have "/sbin" and "/usr/sbin" in your root path, you have a problem.
The reason I say that is that "login" is supposed to start the basic path which you
can add to in "/etc/profile". But, you don't really want these two directories in
the user accounts paths.
JRT
------------------------------
From: [EMAIL PROTECTED] (Lew Pitcher)
Subject: Re: Linux for the 486
Date: Sun, 19 Nov 2000 04:44:06 GMT
On Sat, 18 Nov 2000 05:49:16 GMT, in comp.os.linux.hardware, "chrismendes"
<[EMAIL PROTECTED]> wrote:
>Is it still possible to get off-the-shelf linux installed on an old 486 ?
>How hard would it be to do this ?
Not difficult at all.
I run Slackware Linux 3.3 on a 486DX4/80 w 16MB ram. It runs all my networking
facilities, and X (and Netscape) as well. Reasonably fast too, so long as you
have adequate memory/swap space.
--
Lew Pitcher
Master Codewright and JOAT-in-training
------------------------------
From: Andreas Hiltenkamp <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux.suse,comp.os.linux.setup
Subject: alsa problem - no sound
Date: Sun, 19 Nov 2000 08:56:28 GMT
Hi !
I've got a problem getting sound using a via sound chip
The alsa driver can be sucessfully loaded but I can't hear any sound.
Looking into /proc/asound/sndstat gives the following result
=====================================================================
--
Sound Driver:3.8.1a-980706 (ALSA v0.5.9b emulation code)
Kernel: Linux ibh03 2.2.14 #4 Sun Oct 22 08:59:05 CEST 2000 i686
Config options: 0
Installed drivers:=20
Type 10: ALSA emulation
Card config:=20
VIA 82C686A at 0xb800, irq 15
Audio devices: NOT ENABLED IN CONFIG
Synth devices: NOT ENABLED IN CONFIG
Midi devices:
0: MPU-401 (UART)
Timers:
7: system timer
What's wrong ? Why does sndstat tell me that here is no audio device,=20=
synth device, system timer, mixer
How to enable them. I don't find anything about that in the alsa docu
lsmod looks as follows
Module Size Used by
snd-card-via686a 7180 0=20
snd-pcm 28760 0 [snd-card-via686a]
snd-timer 8032 0 [snd-pcm]
snd-ac97-codec 23904 0 [snd-card-via686a]
snd-mixer 22608 0 [snd-ac97-codec]
snd-mpu401-uart 2312 0 [snd-card-via686a]
snd-rawmidi 9112 0 [snd-mpu401-uart]
snd-seq-device 3392 0 [snd-rawmidi]
snd 34816 1 [snd-card-via686a snd-pcm snd-timer=20=
snd-ac97-codec snd-mixer snd-mpu401-uart snd-rawmidi snd-seq-device]
Any suggestions whats wrong ?
andi
------------------------------
From: Michael V. Ferranti <[EMAIL PROTECTED]>
Subject: Re: Old School
Date: Sun, 19 Nov 2000 08:02:37 +0000
And [EMAIL PROTECTED] spoke thusly:
>Can you do without _any_ package manager?
Well, I view rpm and apt the same as Windows' .cab files. They're
pretty much only good for one OS, unlike tar and gzip. Next thing you
know, there'll be serial numbered rpm upgrades. - Don't use tarballs. Use
only "RedHat Approved" rpm packages, made only by RedHat, only for RedHat.
>I don't believe Debian will ever be commercialized. It's one of the
>more GPL-ish distros out there.
That's what I'm looking for. No ties to any commercial organization.
Intentional or not, RedHat is already taking steps to distance itself from
the rest of the Linux community, changing the way the OS functions,
distributing software and upgrades via rpm, modifying the actual kernel.
It just makes their users even more dependant on RedHat for the answers.
>I really don't understand why RedHat has so much support.
It's as simple as it is funny. RedHat provides the thing their users
need the most. Technical support. <grins>
>This may be the same sort of confusion I have as to why Windows beat
>out OS/2.
Windows beat out OS/2 because nobody was supporting it. All the
mainstream software distributors were writing Windows apps. It was where
all the profits were coming from.
-- Michael V. Ferranti [blades&inreach*com]
Warning: The Surgeon General has deemed that excessive displays of warning
labels and public service announcements produce stress and shortens lives.
------------------------------
From: Michael V. Ferranti <[EMAIL PROTECTED]>
Subject: Re: Old School
Date: Sun, 19 Nov 2000 08:02:38 +0000
And [EMAIL PROTECTED] (Dances With Crows) spoke thusly:
>*cough* Every distro in existence is dependent on some sort of package
>tool. Even Slack, which installs binaries from tarballs using pkgtool.
I'm talking about the most common denominator. All distros have
tarball support, but RedHat seems to be ditching it in full support of rpm
(which is pretty RedHat specific). Debian may or may not follow suit with
apt. I dunno. I just know that this "package manager" battle is slicing
up the Linux community into tiny little distro-specific segments, when what
we need the most at this stage is more community solidarity. The more
fragmented we become, the less commercial support we can expect from the
rest of the world.
>You certainly *can* do without a package manager-
Don't get me wrong. I *like* the idea of package management. The
problem is that they're being used to make each distro distinctive and
unique from one another.
>Debian will be around for a while, I'm sure. Plus, "alien" can convert
>RPM to .deb or .tgz, and alien is a Perl script. Give Debian a try.
That's good to hear, backward compatibility with tarballs, which still
seems to be the most common form of package management and distribution. I
intend switching to Debian here as soon as the CDs arrive. I tried finding
out which distro Linus Torvalds preferred, but that was a lost cause. What
could be better than what the author himself uses, but he uses them all,
they say. <sighs> Debian it is...
-- Michael V. Ferranti [blades&inreach*com]
Warning: The Surgeon General has deemed that excessive displays of warning
labels and public service announcements produce stress and shortens lives.
------------------------------
** 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
******************************
