Linux-Hardware Digest #43, Volume #14 Sat, 16 Dec 00 21:13:05 EST
Contents:
Re: Can't get floppy to work (Jorge)
Re: ATI Rage Fury (Jorge)
Re: ATI Rage Fury (Jorge)
Re: Soft-Power Shutdown RH7 (Markku Kolkka)
Re: Sound Blaster not working ([EMAIL PROTECTED])
Re: how diagnose hardware - Hard lockup then crc error ("Harry-0")
Re: GeForce2 with any distro - any success? failure? anybody? ("bigtiny")
choosing a hard drive (sherry)
Re: TV card question ("Jason Byrne")
ATA disk bad blocks ("lewis e. lipkin")
Xfree86 and cl-5429? ([EMAIL PROTECTED])
Is (networking kit) Linksys FESWSK5 supported under Linux? (Michael Badt)
Re: X window font server crash: help (=?ISO-8859-1?Q?Rasmus_B=F8g_Hansen?=)
Re: how diagnose hardware - Hard lockup then crc error
(=?ISO-8859-1?Q?Rasmus_B=F8g_Hansen?=)
----------------------------------------------------------------------------
From: Jorge <[EMAIL PROTECTED]>
Subject: Re: Can't get floppy to work
Date: Sun, 17 Dec 2000 00:00:15 GMT
James Richard Tyrer wrote:
>
> Jorge wrote:
>
> > I am unable to I/O to my floppy drive, althoght it has been congured by
> > the OS when I use 'fdflush' it reports that the following
> > floppy0: probe failed.
> > When I 'ls' the /dev/fd0 the file is set to
> > br----x--t 1 root floppy 2, 0 .....
> >
> > I tryed the same floppy drive on a Win95 and it worked, which leads me
> > to accept that it is CLOS where the problem is and not in the floppy
> > drive.
>
> The permissions for the floppy devices should be: 660. That is, as root:
> chmod 660 /dev/fd0*
>
> Then, you need to make all users that are allowed to use the floppy drives
> members of the group: floppy
>
> At least that is doing it by the book.
>
> Also check the permissions of the mount point. If it is root:root then it
> needs to be 666. Unless you need something else for security reasons.
>
> JRT
Thanks for the help. I'll try it ASAP.
------------------------------
From: Jorge <[EMAIL PROTECTED]>
Subject: Re: ATI Rage Fury
Date: Sun, 17 Dec 2000 00:05:26 GMT
What Pyr0 says is true, but will only work if your monitor can handle
that resolution.
As once said by Jorge - the great programmer "You can't give what you
don't have".
Robert wrote:
>
> PyrO wrote:
> >
> > In your XF86Config file, go to the Screen section (I believe its the screen
> > section) where it shows you the different types of resolution / colour depth
> > / etc. Now the first resolution X reads is obviously the first one (in your
> > case, 640x480). Delete the one that you dont want and have your default /
> > favorite resolution the first one (instead of 640x480, change it to
> > 1024x768).
>
> i use the xf86config script and always tell it to set resolution to
> 800x600
> or better (which is the same than doing manually) but startx simply
> doesnt work.
------------------------------
From: Jorge <[EMAIL PROTECTED]>
Subject: Re: ATI Rage Fury
Date: Sun, 17 Dec 2000 00:09:58 GMT
Well, let me put it bluntly to you. What you think is of not concern for
Linux, what you know is what matter.
Having said that, try using SuperProbe, it will tell you what kind of
chip set you have.
Have fun man, 'cos linux is SO much fun!!
Robert wrote:
>
> no i think my chipset is mach64 but is worth trying anyway,
> where can i get it?
>
> Doug Kramer wrote:
> >
> > I am having problems with mine so I don't have room to talk!
> >
> > But wouldn't you want to install ATI Wonder SVGA server for your Rage 128
> > chip? I thought that's what XFree86 suggested for this ATI hardware instead
> > of the old Mach64 server under version 4.01.
> >
> > You want the R128 driver.
> >
> > "Robert" <[EMAIL PROTECTED]> wrote in message
> > news:[EMAIL PROTECTED]...
> > > i've tried lots of things on xf86config, perhaps a lower-level
> > > configuration
> > > can solve the problem. and what about the xserver? i'm using the mach64
> > > server
> > > and i've set the card to number 104 in xf86config, does it matter?
> > >
> > > James Richard Tyrer wrote:
> > > >
> > > > Robert wrote:
> > > >
> > > > > Hi all!
> > > > > anyone been succesful on configuring an ATI Rage Fury under xfree86
> > > > > 4.0.1?
> > > > > i actually can only get 640x480, which is *pathetic*
> > > >
> > > > At the risk of being redundant:
> > > >
> > > > Section "Screen"
> > > > Identifier "Screen 1"
> > > > Device "ATI Rage IIC"
> > > > Monitor "NEC MultiSync3V"
> > > > DefaultDepth 24
> > > >
> > > > Subsection "Display"
> > > > Depth 24
> > > > Modes "1024x768"
> > > > ViewPort 0 0
> > > > EndSubsection
> > > > EndSection
> > > >
> > > > Ad some other Modes if you want, need, and you monitor can support them.
> > > >
> > > > But this isn't enough, you have to have the proper horizontal refresh
> > > > and vertical sync rates. And, don't enter something that your monitor
> > > > won't handle or you may give new meaning to the term "smoke test".
> > > >
> > > > Section "Monitor"
> > > >
> > > > Identifier "NEC MultiSync3V"
> > > >
> > > > HorizSync 31.5 - 48.5
> > > >
> > > > VertRefresh 50-70
> > > >
> > > > EndSection
> > > >
> > > > The above range will support 1024 x 768.
> > > >
> > > > These are copies from my XFree86Config file.
> > > >
> > > > And, I presume that your driver (device) is also correct:
> > > >
> > > > Section "Device"
> > > > Identifier "ATI Rage IIC"
> > > > Driver "ati"
> > > > #VideoRam 4096
> > > > EndSection
> > > >
> > > > The documentation says not to tell it how much VRAM you have unless it
> > > > can't figure it out for itself -- put in the figure, but leave it
> > > > commented out.
> > > >
> > > > JRT
>
> --
>
> Have a lot of fun!
------------------------------
From: Markku Kolkka <[EMAIL PROTECTED]>
Subject: Re: Soft-Power Shutdown RH7
Date: 17 Dec 2000 02:17:32 +0200
"HiLLStEr" <[EMAIL PROTECTED]> writes:
> i have a prob where i think the kernel in 7.0 has no soft power off
The problem isn't in the kernel, it's in the shutdown script
/etc/rc.d/init.d/halt. Try this patch:
--- /etc/rc.d/init.d/halt~ Thu Aug 3 01:44:17 2000
+++ /etc/rc.d/init.d/halt Sat Nov 4 19:49:10 2000
@@ -28,7 +28,7 @@
case "$0" in
*halt)
message="The system is halted"
- command="halt"
+ command="poweroff"
;;
*reboot)
message="Please stand by while rebooting the system..."
--
Markku Kolkka
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: alt.os.linux,comp.os.linux,comp.os.linux.help
Subject: Re: Sound Blaster not working
Date: Sun, 17 Dec 2000 00:36:35 GMT
In article <4sS_5.217677$[EMAIL PROTECTED]>,
"Chris" <e e z e e 7 @ h o m e . c o m> wrote:
> I am running Redhat Linux 6.2, and I'm having trouble with my Sound Blaster
> clone sound card. When I try to use sndconfig, I get the following error
> messages (these also appear when the computer is booting up):
>
> /lib/modules/2.2.14-5.0/misc/sb.o: init_module: Device or
> resource busy
> /lib/modules/2.2.14-5.0/misc/sb.o: insmod
> /lib/modules/2.2.14-5.0/misc/sb.o failed
> /lib/modules/2.2.14-5.0/misc/sb.o: insmod sound-slot-0 failed
>
> I have no idea what the trouble is, and I am hoping someone here can resolve
> this. One thing to note however; my sound card DID work properly running an
> older version of RH Linux (I think it was RH5 or something).
> -----
> Chris
>
I am also running 6.2 with a Sound Blaster 16 card which is currently
working. When I upgraded from RH 6.1 to 6.2, I had some trouble with the
sound card working, but I was able to correct this by re-running the "pnpdump
-c" command ("-c" option allows the pnpdump program to guess at a good
configuration for the pnp devices), and redirect the output to the
isapnp.conf file. After rebooting, I was able to configure the card with the
sndconfig utility. I don't know if this will work for you, but it is
something that worked for me.
Sent via Deja.com
http://www.deja.com/
------------------------------
From: "Harry-0" <[EMAIL PROTECTED]>
Subject: Re: how diagnose hardware - Hard lockup then crc error
Date: Sat, 16 Dec 2000 17:04:27 -0800
Crossposted-To: comp.os.linux.setup,alt.os.linux,alt.os.linux.mandrake
This may well be because your computer vents are clogged with dust or the
fan that cools the CPU is also blocked with the stuff or worn out
(bad bearings?) RAM chips usually don't go bad slowly, but cooling does,
causing the CPU to become very error-prone before complete lockups. Take
the cover off the case and see if the CPU fan is clean and turns fast. See
if it still locks. If it does, gently touch the CPU or the heat sink to
find out if it is very hot, or just warm (if you burn your finger, it's
too hot.) If just warm, look elsewhere for the cause, but I'll be that's
it.
In article <[EMAIL PROTECTED]>, "Stan Towianski"
<[EMAIL PROTECTED]> pounded on his/her keyboard until this came out:
> Hi,
>
> My system; AMD-K6 233Mhz 64mb ram has been locking hard at pretty
> frequently lately. It seems to be getting worse. I did not know if it
> is with each Mandrake upgrade ..,7,7.1, now 7.2 or what. I wonder if
> the new KDE 2.0 is buggy.
>
> But I am questioning hardware and I don't know how to figure that out. I
> found memtest and ran that. It blew out once. Then I decided to boot
> from cd and mount my / with usr on it to run the memtest binary I
> created.
>
> Twice it blew out at the apparently last test. test16: Walking zeroes:
> setting ...XSegmentation fault.
>
> Anyone know if memtest works?
>
> Also, after a hard lockup I have to reset or turn it off and on.
> Usually it does not come back up. I usually get a 'CRC Error....' and
> have to reset a few times or turn the system off and wait a few minutes
> (it won't work right away). Then it will run again.
>
> The last time I got this error on rebooting:
> .
> .
> .
> Partition check:
> hda: hda1 hda2 hda3 < hda5 hda6 hda7 hda8 >
> RamDisk: compressed image found at block 0 crc error<6>autodetecting
> RAID arrays autorun ...
> ... autorun DONE.
> VFS: Cannot open boot device 08:06 kernel panic: VFS: Unable to mount
> root fs on 08:06
>
> I usually think of CRC errors with floppies. Could this be a hard drive
> error? or memory? or what?
>
> What programs are there for linux to find hardware problems??
>
> Stan Towianski [EMAIL PROTECTED]
------------------------------
From: "bigtiny" <[EMAIL PROTECTED]>
Subject: Re: GeForce2 with any distro - any success? failure? anybody?
Date: Sun, 17 Dec 2000 01:17:57 GMT
I've been struggling with this for a couple of weeks and finally got it to
work with help from this thread.....here's what I did (is there some way to
have procedures like this archived in a FAQ or something) ????
I am using an ASUS v7100 card with the NVIDIA Geforce2 MX chipset.
Either verify that you're running XFree 4.0.1 or later; or download and
install it. I'm running RedHat 7.0 so that's what came with the
distribution.
FTP to ftp1.detonator.nvidia.com/pub/drivers/english and download the
tarballs for the NVIDIA_kernal and NVIDIA_GLX materials (I think they are
version 0.9-5).
Now untar both sets (tar xvzf 'filename'). Go to the untarred directory for
the GLX stuff and look at the README for the M64 chipset (don't ask me
why...I just know it worked for me) and make the mod it talks about
(os-registry.c in the NVIDIA_kernel make directory).
Run make in both directories. In the NVIDIA_GLX* make directory you'll see a
file called nvidia_drv.o...copy it to /usr/X11R6/lib/drivers/video (you
should see nv_drv.o in the same directory...it's for the older nvidia
chipsets).
Your make for the NVIDIA_kernel might have encountered errors trying to do
insmod on the NVdriver file. To get around them I did this from the command
line:
modprobe agpgart agp_try_unsupported=1
modprobe NVdriver
You might have to modprobe the GLX module too....I didn't, but who knows?
Go to /etc/X11 and edit your XF86Config-4 file. In the devices section
specify 'nvidia' for the driver name.
This worked for me. At the beginning of the XF86Config-4 file there's a list
of modules that get loaded. On my system there was a call to load a module
called "v41" that didn't exist, so I commented it out.
I also put the modprobe commands in /etc/rc.local at the end so that they
will get loaded at boot time. I don't boot my system into the X environment
initially and this has worked for me. If you boot up directly into X, I
can't tell you whether doing the modprobes in the rc.local script will
work...there may boot chronology issues (you may need the modprobes executed
before rc.local gets run....) I don't have any experience with this, so I
don't know.
If someone does know of a place to archive this procedure and how to do it,
please let me know and I'll do it. I installed Linux to learn, and I learned
A LOT trying to get this card to work, but I think some of it was
unnecessarily painful. I think it's just because people are at such
different levels of experience and certain knowledge is just VERY hard to
find....anyway, thanks to all who responded to this thread and I hope this
explanation helps the next person who has to deal with this...
keith hedger
Kevin Krumwiede <[EMAIL PROTECTED]> wrote in message
news:9176h6$[EMAIL PROTECTED]...
> I'm not finding very much info on installing a GeForce2 card. All I see
> are scattered reports of trouble with nvidia's drivers, which leads me to
> two possible conclusions: either it's working fine for most people, or not
> very many people are trying to use it yet!
>
> I'm building a system and considering a GeForce2 MX. I have not picked a
> distro yet. Possibly Drake 7.2 or Deb 2.2. I know enough to feel
> confident about tweaking and rebuilding things if necessary -- something I
> want to learn more about anyway so I can optimize for my processor.
>
> So, does anybody have a GeForce2 card working in 2D and 3D? How well are
> the OpenGL drivers working? What about the DRI thing?
>
> Thanks for anything...
>
> Krum
------------------------------
From: sherry <[EMAIL PROTECTED]>
Crossposted-To: comp.hardware,alt.comp.hardware
Subject: choosing a hard drive
Date: Sun, 17 Dec 2000 01:18:05 GMT
Hello,
I'm uncertain as to whether cross posting the same message to three
different newsgroups constitutes as spam, technically speaking, so I
will apologize in advance if this is the case.
I wish to buy a new hard drive for my computer that will be used as a
second (and perhaps third) partition. I'd like it to be of the IDE sort.
I'd like it to be of a price tag of no more than $200CND. Also,
importantly, I'd very much like it to be supported under most if not all
linux distros. Aside from these three criterias, I haven't the slightest
clue on how to pick a good quality hard drive. What am I to look for?
What are "good" access times in this day and age? I realize hard drive
performance can be a considerable factor in overall computing speed, so
I thought it best to ask the gurus. I'd be much obliged with any help
any of you can provide, especially on the access time issue. Any hard
drive recommendations would also be appreciated as long as you tell me
why you are recommending it specifically :)
best regards,
------------------------------
From: "Jason Byrne" <[EMAIL PROTECTED]>
Subject: Re: TV card question
Date: Sat, 16 Dec 2000 17:24:46 -0800
"Jason Byrne" <[EMAIL PROTECTED]> wrote in message
news:LNk_5.7036$[EMAIL PROTECTED]...
Also... I just noticed there is some information at http://linux.3dfx.com
with a link pointing to a sourceforge project for that specific card...
> Check out http://linuxvideo.org
>
> I believe this is the best word on the latest status of the various TV
> cards.
>
> - Jason
>
> "Matt Balmer" <[EMAIL PROTECTED]> wrote in message
> news:Pine.LNX.4.21.0012122243470.319-100000@elminster...
> > Hello all,
> >
> > Got a quick (maybe) one for you on a Voodoo3 3500 TV card. All I would
> > like to know is if there is any way I can use the TV tuner functions
with
> > this card, and how to set them up if there's a way to make it all work -
> > I'd assume it would need to be done in X. Linux build information
> > below.
> >
> > Any help is GREATLY appreciated, please reply in person.
> >
> > [EMAIL PROTECTED]
> > (slay the "beast" first)
> >
> > Build information:
> > Debian 2.2r2 (Potato)
> > Kernel 2.2.17
> >
>
>
------------------------------
From: "lewis e. lipkin" <[EMAIL PROTECTED]>
Subject: ATA disk bad blocks
Date: Sat, 16 Dec 2000 20:34:47 -0500
Does an ATA disk handle bad blocks the way old IDEs did by remapping
them,?
Or does it act like SCSI and mark them ?
TIA
Lew Lipkin
------------------------------
From: [EMAIL PROTECTED]
Subject: Xfree86 and cl-5429?
Reply-To: [EMAIL PROTECTED]
Date: Sun, 17 Dec 2000 00:44:57 GMT
I've run X a few times with just the plain Vga server.
I've got an Stb Horizon-32 (Cl-5429) It holds it's refresh
rates on eeprom. The same "clmode" utility that sets the
rates for CL cards also flashes the eeprom on this card.
But the eeprom has a limited number of times it can be flashed.
If I start using an X server designed for this chipset, will
it's setting of the refresh rate also flash the eeprom just
like "clmode" does?
If it did that every time it started X, my video card's eeprom
would have a short lifespan.
Or does the X server set the rate in a way that wouldn't flash
the card?
Thanks.
------------------------------
From: [EMAIL PROTECTED] (Michael Badt)
Subject: Is (networking kit) Linksys FESWSK5 supported under Linux?
Date: Sat, 16 Dec 2000 04:13:20 GMT
Hi,
I'm considering to buy this kit for my Mandrake 7.0 system. Mandrake
hardware support does NOT list any Linksys items. Has anybody used
this kit under LInux?
If Y, what NIC types (assuming these are compatible with a known
brand) and any other parameters should I use?
Thanks !
------------------------------
From: =?ISO-8859-1?Q?Rasmus_B=F8g_Hansen?= <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,linux.redhat.install
Subject: Re: X window font server crash: help
Date: Sun, 17 Dec 2000 02:45:31 +0100
On Sat, 16 Dec 2000, Gilles Lamoureux wrote:
> People,
>
> I was able to login to /home cia x window. After trying several times, I
> now cannot access X windows. Here are the error messages:
> ////////////////////////////////////////////////////////////////////////////
> ////////////////////////////////////
> FontTransSocket UNIX Connect: can't connect: errno=111
> failed to get default font path 'unix/:-1'
> fatal server error:
> not able to open default font 'fixed'
>
> according to /var/run/gdm.pid, gdm was already running but seems to have
> been murdered mysteriously.
> ////////////////////////////////////////////////////////////////////////////
> /////////////////////////////////
>
> Any ideas. I had been downloading font files to run pdf files and such. I
> will gather exactly what I downloaded. But if the errors here are
> sufficient to help me, please,
> HELP ME. I need to get to my sutdy materials pronto.
If you have downloaded and installed buggy fonts, the font server will
crash at startup. You will have to remove the buggy fonts before starting
xfs.
Not 100% sure (sitting on a non-X box), but I think the xfs error messages
should be found in /var/log/messages.
Rasmus B. Hansen
------------------------------
From: =?ISO-8859-1?Q?Rasmus_B=F8g_Hansen?= <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,alt.os.linux,alt.os.linux.mandrake
Subject: Re: how diagnose hardware - Hard lockup then crc error
Date: Sun, 17 Dec 2000 03:00:48 +0100
On Sat, 16 Dec 2000, Stan Towianski wrote:
To me this sounds like a memory problem. Are you running PC66 RAM at
speeds >66MHz?
If you have any chance of pulling out your RAM and inserting some working
RAM, you could try that (e.g. borrow some). Also, if you have more than
one piece of RAM, try pulling one out - then try pulling the other one out
etc.
If you get an error (like the kernel uncompressing CRC-errors) sometimes,
but not others, it is probably not the hard drive.
You could also look at www.bitwizard.nl/sig11/ - it tells something about
memory problems.
Hope this helps.
Rasmus B�g Hansen
> My system; AMD-K6 233Mhz 64mb ram has been locking hard at pretty
> frequently
> lately. It seems to be getting worse. I did not know if it is with
> each
> Mandrake upgrade ..,7,7.1, now 7.2 or what. I wonder if the new KDE 2.0
> is buggy.
>
> But I am questioning hardware and I don't know how to figure that out.
> I found memtest and ran that. It blew out once. Then I decided to boot
> from cd and mount my / with usr on it to run the memtest binary I
> created.
>
> Twice it blew out at the apparently last test.
> test16: Walking zeroes: setting ...XSegmentation fault.
>
> Anyone know if memtest works?
>
> Also, after a hard lockup I have to reset or turn it off and on.
> Usually
> it does not come back up. I usually get a 'CRC Error....' and have to
> reset a few times or turn the system off and wait a few minutes (it
> won't
> work right away). Then it will run again.
>
> The last time I got this error on rebooting:
> .
> .
> .
> Partition check:
> hda: hda1 hda2 hda3 < hda5 hda6 hda7 hda8 >
> RamDisk: compressed image found at block 0
> crc error<6>autodetecting RAID arrays
> autorun ...
> ... autorun DONE.
> VFS: Cannot open boot device 08:06
> kernel panic: VFS: Unable to mount root fs on 08:06
>
> I usually think of CRC errors with floppies. Could this be a hard drive
> error? or memory? or what?
>
> What programs are there for linux to find hardware problems??
>
> Stan Towianski
> [EMAIL PROTECTED]
>
------------------------------
** 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 by posting to comp.os.linux.hardware.
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
******************************
