Linux-Hardware Digest #868, Volume #14 Tue, 5 Jun 01 10:13:06 EDT
Contents:
Re: Geforce2 Go and XFree 4.0.3 (Fabrice Colin)
Re: VIA KT133 686B Chipset (Alberto BARSELLA)
Re: Geforce2 Go and XFree 4.0.3 (Mike H. Miller)
AMD K6-2 500 & Soyo SY-5EMA Pro motherboard (James Omura)
Re: Plz tell me this is not a hardware bug. (M. Buchenrieder)
Re: Why is my IBM DTLA hard disk so slow? (M. Buchenrieder)
cdrecord fails with kernel 2.4.x (Chris Hall)
Re: PCI Expansion card for USB Client(device) required (Iwo Mergler)
Re: Why is my IBM DTLA hard disk so slow? ("Peter T. Breuer")
Re: Dual P3 vs P4 - need recommendation fast ("Justin Mahn")
Re: SCSI problems (Trevor Hemsley)
Re: VIA KT133 686B Chipset (Kenneth Rørvik)
Re: Opengl On linux (Kenneth Rørvik)
software raid with raidtools (A. GUILLEVIC)
----------------------------------------------------------------------------
Date: Tue, 05 Jun 2001 12:15:10 +0100
From: Fabrice Colin <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.portable,comp.os.linux.setup,comp.os.linux.x
Subject: Re: Geforce2 Go and XFree 4.0.3
"T. J. Domsalla" wrote:
>
> Hi,
>
> I recently installed SuSE Linux 7.2 (XFree 4.03) on a Dell Inspiron 8000
> with Nvidia Geforce2 Go. Kernel is 2.4.5, Nvidia GLX and kernel driver
> 1.0.1251.
> When starting X I get "Failed to initialize the NVdriver kernel module" and
> "Screen found, but none have a usable configuration".
> Did anyone get it running?
>
I had the same problem this weekend after having installed 1.0-1251, but
with a GeForce2 GTS on RH6.2/XFree86 4.02/kernel 2.4.5.
Unfortunately I don't remember how I fixed it. I wonder if it was
because
I played with the IgnoreEDID option in XF86Config ?
If it says "Failed to initialize the NVdriver kernel module", it's maybe
worth switching to initlevel 3 (that's "multi-user without X"), load
the NVdriver manually with 'modpobe NVdriver' and run X with 'startx'.
See if it makes any difference.
Sorry if this is all very vague, but I am at work and I am hungry ;-)
Fabrice
------------------------------
From: Alberto BARSELLA <[EMAIL PROTECTED]>
Subject: Re: VIA KT133 686B Chipset
Date: 05 Jun 2001 13:26:44 +0200
Albert <[EMAIL PROTECTED]> writes:
> Hello
>
> I bought new motherboard with this chipset and new HD IBM 30GB 7200. I
> installed RH7.1 with kernel 2.4.2. I didn't compiled the kernel. When I
> check "hdparm -i /dev/hda" I get the following message:
[.....]
Had the same problem with 2.4.2.
I tried again in 2.4.4 (or was it 2.4.5?) and it works fine. It seems
like they fixed something in the via code (BTW, I have 686A).
Update the kernel and try again....
Bye,
Alberto
--
Alberto BARSELLA - infringing US Pat. 5,443,036 every evening!
- check: http://www.delphion.com/details?pn=US05443036__
** Beliefs are dangerous. Beliefs allow the mind to stop functioning.
A non-functioning mind is clinically dead. Believe in nothing... **
------------------------------
From: [EMAIL PROTECTED] (Mike H. Miller)
Crossposted-To:
comp.os.linux.portable,comp.os.linux.setup,comp.os.linux.x,de.comp.os.unix.linux.hardware
Subject: Re: Geforce2 Go and XFree 4.0.3
Date: 5 Jun 2001 11:18:28 GMT
On Mon, 4 Jun 2001 18:34:42 +0200, T. J. Domsalla <[EMAIL PROTECTED]> wrote:
>Hi,
>
>I recently installed SuSE Linux 7.2 (XFree 4.03) on a Dell Inspiron 8000
>with Nvidia Geforce2 Go. Kernel is 2.4.5, Nvidia GLX and kernel driver
>1.0.1251.
>When starting X I get "Failed to initialize the NVdriver kernel module" and
>"Screen found, but none have a usable configuration".
>Did anyone get it running?
>
>Thorsten J. Domsalla
You're going to love this ;). Where I work, we've got a few of these laptops...
they're great machines, but the GeForce2 Go chips were giving us problems.
First, you can use the 0.9-769 drivers (just be aware that the kernel module
and the GLX driver must be the same version). The problem with that approach is
that it crashes whenever you exit X (known bug). This means you can never shut
down the machine safely.
But wait! 1.251 will work... if you pass the kernel modules an option of
NVreg_Mobile=1 (1 for a Dell, 2 if you have a Toshiba). To do this, either load
the modules manually using modprobe NVdriver NVreg_Mobile=1, or add the
following to /etc/modules.conf (or /etc/conf.modules, which was the older style)
options NVdriver NVreg_Mobile=1
Once you do this (which, btw, is obscurely documented in /usr/share/doc/NVIDIA_
GLX_1.251/ ... NOT with the kernel modules... duh), you can run X safely. Note
that there still is a bug that prevents you from _starting_ X more than once.
Therefore, I advise you edit inittab and make sure you have a line that reads
id:5:initdefault:
instead of
id:3:initdefault:
The first one will automatically load into X. Good luck!
P.S. Everything I did was on a RH 6.2 and RH7.1 system. YMMV.
------------------------------
From: [EMAIL PROTECTED] (James Omura)
Subject: AMD K6-2 500 & Soyo SY-5EMA Pro motherboard
Date: Tue, 5 Jun 2001 08:15:09 -0400
This is one of the strangest things I've seen in years.
For the time being, the situation is "resolved" but Ithink I
may need to know more about this later:
I recently bought the above named parts, a Soyo SY-5EMA Pro
motherboard (aka SY-5EMA+) and an AMD K6-2 500MHz CPU. The ETEQ
chipset is apparently a Via licensed chipset (MVP-3?). According
to the manual (Copyright 1999, but actually updated at least to
May 2000 -- I have also downloaded revised documents including
the "Quick Start Guide" for 5EMA+ from Mar. 2000, and 5EMA Pro
Version 1.1 Edition: Jan. 2001, both of which are the same in
the relevant info) the CPU came in a number of voltaged, so I
should look at the package. The chip package was marked as a
3.3V device. The manual says 3.3V is set as follows:
SW2: 1 on, 2 off, 3 on, 4 on, 5 off
The manual also says to populate the board starting at
DIMM 3, then DIMM 2 (iff you use 2) and then DIMM 1, only
if you are using 3.
So I did that. I also set the rest of the jumpers and
switches properly.
It didn't work. After much mucking around and returning
the motherboard and getting another (same result), the store
manager said to bring my stuff in and he'd help for a price.
I watched, he worked and paid -- I won't say how much, but it
was fair.
First, contrary to the big deal the manual makes, he
stuck the DIMM into the DIMM 1 slot. (Huh?)
At first no difference. Then after checking the manual
for a while, he "realized" something that I didn't, and changed
the SW2 settings as follows:
SW2: 1 off, 2 on, 3 off, 4 off, 5 off
I checked the manual later and he has it set for 2.2V.,
which is common for most K6-2 versions, but not for this
particular part. It works. (HUHHH?)
First, there's no way that I'm misreading the chip. It
says 3.3V. No doubt. But what if I'm wrong? Well, that
would mean that I was far over-voltage and when I tried to
run it at that voltage the CPU should have been fried.
If it didn't fry the CPU, then why wouldn't it work? It
wasn't just the DIMM slot. The memory is still sitting in
DIMM 1 where he put it.
So far, the setup seems to be working. Most of the
hardware I've installed seems to work. I'm having software
problems right now (need to re-install Win 98 first to backup
some data, then I'll be figuring out how I'm going to divide
up the disk -- or replace the HD). But I still don't get it.
According to the manual, what I did should have worked, and
what he did was "all wrong". What's going on here?
------------------------------
From: [EMAIL PROTECTED] (M. Buchenrieder)
Subject: Re: Plz tell me this is not a hardware bug.
Date: Tue, 5 Jun 2001 11:40:15 GMT
"Kilian A. Foth" <[EMAIL PROTECTED]> writes:
>Hello world,
>I'm getting hard freezes on my system after a day at the most and
>can't figure out why. This is my box:
> Micro-Star MS-6323 mainboard
> Apollo Pro 133A chipset with VIA 694X/686A (not the 686B, thank God)
> on-chip AC97 sound blaster
> 800Mhz PIII
> ATI Rage 128 PF
[...]
Well, since you already tried changing the memory modules, all
there is left to do is
- checking the usual suspects, like CPU cooler, or incorrect
BIOS settings (disable APM etc.);
- stop XFree and see whether the system runs stable in console
mode only;
- check for available memory ;
- switch components.
Michael
--
Michael Buchenrieder * [EMAIL PROTECTED] * http://www.muc.de/~mibu
Lumber Cartel Unit #456 (TINLC) & Official Netscum
Note: If you want me to send you email, don't munge your address.
------------------------------
From: [EMAIL PROTECTED] (M. Buchenrieder)
Subject: Re: Why is my IBM DTLA hard disk so slow?
Date: Tue, 5 Jun 2001 11:45:49 GMT
"Peter T. Breuer" <[EMAIL PROTECTED]> writes:
>Andrew Nesbit <[EMAIL PROTECTED]> wrote:
^^^^^^^^^^^^^^^^^^^^^^^^^^
This is a bad thing (TM).
[...]
>I honestly don't understand you. 80 pin cable implies 80 pin socket,
[...]
No, not with today's motherboards. They use a specific UDMA socket
and IDE cable with 80 wires, but just 40 (or, more precisely, 39) pins.
The sockets and the plugs on these cables usually are blue,
contrary to the standard IDE interfaces and connectors (black).
Michael
--
Michael Buchenrieder * [EMAIL PROTECTED] * http://www.muc.de/~mibu
Lumber Cartel Unit #456 (TINLC) & Official Netscum
Note: If you want me to send you email, don't munge your address.
------------------------------
Date: Tue, 05 Jun 2001 13:31:37 +0100
From: Chris Hall <[EMAIL PROTECTED]>
Subject: cdrecord fails with kernel 2.4.x
I am somewhat at my wits end now, as since I've gone to 2.4 my cdrw now
fails with scsi errors. I have an IDE Traxdata drive that I can see
through the ide-scsi stuff, as demonstrated below:
# cdrecord -scanbus
Cdrecord 1.9 (i686-pc-linux-gnu) Copyright (C) 1995-2000 Jörg Schilling
Linux sg driver version: 3.1.17
Using libscg version 'schily-0.1'
scsibus0:
0,0,0 0) 'TOSHIBA ' 'CD-ROM XM-6202B ' '1108' Removable CD-ROM
0,1,0 1) 'Traxdata' ' CDRW2260+ ' '3.09' Removable CD-ROM
0,2,0 2) *
0,3,0 3) *
0,4,0 4) *
0,5,0 5) *
0,6,0 6) *
0,7,0 7) *
But when I blanking a cdrw I get this:
# cdrecord dev=0,1,0 blank=fast
Cdrecord 1.9 (i686-pc-linux-gnu) Copyright (C) 1995-2000 Jörg Schilling
scsidev: '0,1,0'
scsibus: 0 target: 1 lun: 0
Linux sg driver version: 3.1.17
Using libscg version 'schily-0.1'
Device type : Removable CD-ROM
Version : 0
Response Format: 1
Vendor_info : 'Traxdata'
Identifikation : ' CDRW2260+ '
Revision : '3.09'
Device seems to be: Generic mmc CD-RW.
Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
Driver flags : SWABAUDIO
cdrecord: Drive needs to reload the media to return to proper status.
Starting to write CD/DVD at speed 2 in write mode for single session.
Last chance to quit, starting real write in 1 seconds.
cdrecord: Input/output error. blank unit: scsi sendcmd: retryable error
CDB: A1 01 00 00 00 00 00 00 00 00 00 00
status: 0x0 (GOOD STATUS)
cmd finished after 8.107s timeout 9600s
cdrecord: Cannot blank disk, aborting.
I have tried the various versions of cdrecord (1.8, 1.9, and the latest
beta), I've downloaded the latest version of the kernel and gone from
2.4.2 to 2.4.5 and its not made the blindest bit of a difference - any
ideas now would be gratefully received.
TIA
--
Chris.
------------------------------
Date: Tue, 05 Jun 2001 13:49:38 +0100
From: Iwo Mergler <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.embedded
Subject: Re: PCI Expansion card for USB Client(device) required
Girish G wrote:
>
> Hi,
> I reside in India. Also, this page is in German and when I
> tried "Suche" which I took to be Search, I could not find
> this product number listed. It gave me some German text
> which I could not understand at all. It would be very
> helpful if you could locate this page for me and send the
> page or it's link to me by e-mail.
>
> Any other info would also be helpful.
>
> Regards
> Girish
>
> Anders Larsen wrote:
> >
> > On Thu, 31 May 2001 17:38:58 +0200, "Girish G" <[EMAIL PROTECTED]>
> > wrote:
> >
> > > Don't know if this mail befits this newsgroup. However, could not find
> > > a better place to post to. So here goes.
> > >
> > > We need an PCI board for USB CLIENT(b'coz our hardware does not have a
> > > USB port, either client or host and we need a USB client sitting on
> > > PCI). Any recommendations. We have searched the web but did not come
> > > up with anything worthwhile
> > >
> > > Please note, the board must be PCI
> >
> > Hi,
> >
> > I don't know where you're located, but here in Germany a USB interface
> > card (2 ports, PCI) is available from the supplier Secomp
> > (http://www.secomp.de/ - order no. 15.06.2152).
> > The catalogue doesn't state any manufacturer, so I guess it comes
> > from somwhere in the far east (the low price tag, EUR 23,-, comfirmes
> > this); on the picture you can see that it's based on a VIA chip.
> >
> > HTH
> > cheers
> > Anders
> > --
> > "In theory there is no difference between theory and practice.
> > In practice there is." - Yogi Berra
This is an english supplier, but they might ship abroad...
http://www.dabs.com/products/prod-search.asp?action=search&tid=523&ob=manufacturer&obd=asc&stab=ref
Iwo
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: Why is my IBM DTLA hard disk so slow?
Date: Tue, 5 Jun 2001 14:45:15 +0200
M. Buchenrieder <[EMAIL PROTECTED]> wrote:
> "Peter T. Breuer" <[EMAIL PROTECTED]> writes:
>>Andrew Nesbit <[EMAIL PROTECTED]> wrote:
> ^^^^^^^^^^^^^^^^^^^^^^^^^^
> This is a bad thing (TM).
yes.
>>I honestly don't understand you. 80 pin cable implies 80 pin socket,
> [...]
> No, not with today's motherboards. They use a specific UDMA socket
Aaaaaaaah. I hoped it was something like that as the explanation.
> and IDE cable with 80 wires, but just 40 (or, more precisely, 39) pins.
> The sockets and the plugs on these cables usually are blue,
> contrary to the standard IDE interfaces and connectors (black).
Lesseeee (I'm mostly scsi), my modern fast ide drives look like they
have the usual 40pin cable and black connectors, but the cables are
stranded into ribbons of 4 or 5 wires apiece. Of course, these are
definitely on standard controllers ... 120/15 MB/s under hdparm -Tt,
apparently using udma mode2, or so the (wd) drive says.
I'll believe you on that.
Peter
------------------------------
From: "Justin Mahn" <[EMAIL PROTECTED]>
Crossposted-To: alt.comp.hardware
Subject: Re: Dual P3 vs P4 - need recommendation fast
Date: Tue, 5 Jun 2001 08:42:17 -0500
try dual athlons on the amd760mp
www.slashdot.org
"Lars Preben S. Arnesen" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> I'm going to buy a new computer and have to decide within a few hours
> what prosessor configuration to choose.
>
> First I decided to choose a dual P3 1GHz with 512 MB DIMM SDRAM PC133.
> After a conversation with a friend and the local computer store, I
> decided to go for the P4 1,7 GHz with 2x256MB RIMM 400MHz RAMBUS.
>
> I was recommended this mainly because of the faster RAM bus that comes
> with the P4 solution.
>
> After reading some articles (for instance <URL:
> http://www.inqst.com/articles/p3vp4/p4vp3article.htm>) I'm starting to
> change my mind.
>
> What should I do? The computer is going to be my workstation running
> Linux. I don't think I'm going to use all the CPU time for a while
> (other than running dnetc), but I hate to get the second best option
> when I'm going to buy a new box. I'm not a real game buff, but I'm
> going to buy a GeForce2 card so that gaming now becomes an option.
>
> --
> Lars Preben
------------------------------
From: [EMAIL PROTECTED] (Trevor Hemsley)
Crossposted-To: comp.os.linux.setup
Subject: Re: SCSI problems
Date: 05 Jun 2001 13:45:51 GMT
On Mon, 4 Jun 2001 15:46:39, John English <[EMAIL PROTECTED]> wrote:
> Thanks to those who replied, and to those who helped by private email.
> I seem to be suffering from a bad case of versionitis...
>
> Trevor Hemsley wrote:
> > There's a known problem with FAT formatted media on MO disks (or
> > anything which uses a 2K sector size) when run with a 2.4.x kernel.
>
> Eric DESHAYES wrote:
> > for writing cd, i have been told that you need the kernel 2.4.5(maybe
> > 2.4.4).
>
> Does anyone know whether these problems exist with earlier kernels?
> Is there anything in RH7.1 which *requires* a 2.4 kernel, or could
> I get away with a kernel "downgrade" to fix my problems?
>
> I've certainly used the same M-O drive model on another box, many
> moons ago (kernel version < 2, but I can't remember exactly) and
> am quite happily burning CDs on a RH6.2 setup (but using a SCSI
> burner)...
>
> Any thoughts, anyone?
It's certainly possible to run a newer kernel on a machine based on an
older distribution - as long as you update the bits that need updating
(see /usr/src/linux/Documentation/Changes). I'm not sure if you can
run an older kernel on a distribution that is specifically built
around a 2.4.x kernel though. Try it and see is about the best answer
- you can set up a new lilo stanza to boot a different kernel
alongside the existing one.
Does RH 7.1 not supply 2.2.x and 2.4.x kernels? I run SuSE 7.1 and
that gives you a choice of 2.2.18 and 2.4.something.
There are patches for the MO 2KB sector problem and I think they are
included in the latest 2.4.x-acn series of kernels which will be on
ftp.[country].kernel.org in an Alan cox specific directory somewhere.
Writing CD's does not require 2.4.5 - at least not generically. I've
written CD's on my SCSI Plextor 12/10/32 with lots of different kernel
releases up to and including 2.4.3. The ide-scsi emulation layer may
be a different thing to factor in but I do not remember reading that
it was terribly broken at any recent time.
--
Trevor Hemsley, Brighton, UK.
[EMAIL PROTECTED]
------------------------------
Subject: Re: VIA KT133 686B Chipset
From: [EMAIL PROTECTED] (Kenneth Rørvik)
Date: Tue, 05 Jun 2001 13:51:32 GMT
[EMAIL PROTECTED] (Albert) wrote in
<9fi4dt$iup$[EMAIL PROTECTED]>:
>I bought new motherboard with this chipset and new HD IBM 30GB 7200. I
>installed RH7.1 with kernel 2.4.2. I didn't compiled the kernel. When I
>check "hdparm -i /dev/hda" I get the following message:
> DMA modes: mdma0 mdma1 mdma2 udma0 udma1 *udma2 udma3 udma4 udma5
>
>Then I try to set my HDD into UDMA5 mode - it should work correctly. But
>ide0:Speed warnings UDMA 3/4/5 is not functional
>
>What is wrong with my ide0.
The kernel is telling you that UDMA modes 3-5 are disabled (to avoid
filesystem corruption). I think a workaround was implemented in 2.4.3 or
2.4.4. I'd recommend upgrading the kernel to 2.4.5.
--
Kenneth Rørvik 91841353/22950312
Nordbergv. 60A [EMAIL PROTECTED]
0875 OSLO home.no.net/stasis
------------------------------
Subject: Re: Opengl On linux
From: [EMAIL PROTECTED] (Kenneth Rørvik)
Date: Tue, 05 Jun 2001 13:57:39 GMT
[EMAIL PROTECTED] (187) wrote in <[EMAIL PROTECTED]>:
>Can anyone help me, I just started using linux mandrake 8.0
>I have a elsagladiac geforce2mx, and I am unable to get any
>Program that requires opengl to work such as Gltron
>I seriously need help, when I tried 4.0.3, my whole computer
>Crashed and would not boot in linux,so I had to reformat.Please help
You need to install nVidias own drivers to get 3D acceleration with Linux:
http://www.nvidia.com/view.asp?PAGE=linux
Read the instructions carefully, and you should have no problems :)
As for the crash after trying 4.0.3, did your computer actually boot, but
stopped when trying to launch X, or did it refuse to boot *at all*? I am
guessing it did boot, and when trying to launch X, it could not find a
valid setup and ended up respawning X with only a few seconds intervals.
Which, of course, is no good. If you experience further problems, your best
bet would be to boot into another runlevel (At the lilo prompt type linux 3
for textmode), this will allow you to fix any problems with the X
configuration.
Good luck :)
--
Kenneth Rørvik 91841353/22950312
Nordbergv. 60A [EMAIL PROTECTED]
0875 OSLO home.no.net/stasis
------------------------------
From: [EMAIL PROTECTED] (A. GUILLEVIC)
Subject: software raid with raidtools
Date: 5 Jun 2001 07:07:05 -0700
Hello,
I made some other tests with software raid. I tried to build a linear array
with two IDE disks to validate procedure. Here are disk models:
Seagate Barracuda ATA III
Model ST320414A
20 Gbytes
I wanted to create an array with these two disks. I created a partition on
each drive, I set up partition type to 0xfd, for persistent superblock.
Here's my /etc/raidtab file:
raiddev /dev/md0
raid-level linear
nr-raid-disks 2
chunk-size 32
persistent-superblock 1
device /dev/hdc1
raid-disk 0
device /dev/hdd1
raid-disk 1
When I run mkraid, it aborts. I tried without a persitent superblock, but I keep
on having problem.
When I try to reboot the machine, I have the following error message:
starting up RAID devices: /dev/md0
Invalid argument: /dev/md0 must be a non persistent RAID0 or LINEAR array.
Thanks in advance for your suggestions
------------------------------
** 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
******************************
