Linux-Hardware Digest #725, Volume #14 Fri, 4 May 01 04:13:04 EDT
Contents:
Re: Question on Nvidia drivers with Suse 7.0 (Curtis Rey)
winmodem works anyway ("SilentNight")
Re: Kernel 2.4 : Ethernet connexion pb (Alberto Pires de Oliveira Neto)
Re: what are the parameters for scsi aic7xxx (ultra160) card (Alberto Pires de
Oliveira Neto)
Re: Two network cards (Alberto Pires de Oliveira Neto)
Re: writing a kenel (no one)
Asus A7A266 and lm_sensors? ("Bobby D. Bryant")
Asus A7A266 and DMA? ("Bobby D. Bryant")
Re: ZIP problems (Tim Moore)
Re: Kernel 2.4 : Ethernet connexion pb (Nicolas Delestre)
Re: Floppy drive problems ("J.H.ETTLE")
Re: ZIP problems ("J.H.ETTLE")
Re: $200 graphics card ("arthur")
Re: via 82c686a (Tim Moore)
----------------------------------------------------------------------------
From: Curtis Rey <[EMAIL PROTECTED]>
Crossposted-To: alt.linux,alt.os.linux,alt.os.linux.suse
Subject: Re: Question on Nvidia drivers with Suse 7.0
Date: Fri, 04 May 2001 03:38:38 GMT
Some of the NVidia drivers are only compiled for specific/generic kernel
version related to the stock release. If you have 7.1 with either/or
2.2.18 and 2.4.0-4GB then it works. I tried to get them to work with
2.4.2-4GB and 2.4.2-5 and they wouldn't work. I didn't have a black
screen but the full functionality/acceleration would not work. Best
answer I can give you. Hope someone else has the answer, but I suspect
this is a problem with NVidia's compile. You could use the src.rpm's
but you'll have to remove the old drivers and NVidia kernel rpm's
first.
Also, Mesa drivers conflict with the nvidia drivers. You don't want to
remove all the mesa packages, just the drivers. It also may have
conflicts with other video driviers/packages.
Cheers! Curtis.
me wrote:
>
> My Config:
>
> Suse 7.0 Pro
> 2.2.16
> Geforce 2 GTS video card
> Xfree86 4.0.2
> Latest Nvidia driver for Linux loaded off of Nvidia's site.
>
> When I try to run startx all I get is a black screen and I have to
> Ctrl-Alt-F1 out. When I look at the log I see the last line is something
> like "Write-combining range" with some memory addresses. If I try the "nv"
> driver that comes with Suse, no problem starting. However if I try the
> nvidia one (I change the driver name to "nvidia" in my config file) no go.
> I've configured everything according to the installation from NVidia and
> Tom's hardware. I've tryed disabling AGP (I can verify via the log that it
> disables it) to see if that was the problem as well.
>
> One question I have is that I downloaded a kernel from Suse's site
> (k_eide.rpm) that specifically was for issues with the Promise EIDE
> controller I have onboard and Nvidia Geforce cards. I booted (via a boot
> image) and went thru the install. Since with Geforce2 cards YAST2 is not
> possible I used YAST. Cause I am new to Linux I performed the following
> after the install (I guess redundant)
>
> rpm -ihv --force --nodeps k_eide.rpm
> mk_initrd
> lilo -v
>
> This was in Suse's instructions for a post install kernel update I think.
>
> Anyway my point is if I update the kernel with a boot image and via rpm, are
> the correct sources installed? (I installed the source package that comes
> with Suse in the install) I'm wondering because I have to make sure I
> compiled the Nvidia driver with the right sources. Are the original sources
> valid for the same kernel version with patches I guess?
>
> In the end I need to get past the "Write-combining range" part of startx.
> Thanks.
------------------------------
From: "SilentNight" <[EMAIL PROTECTED]>
Subject: winmodem works anyway
Date: Fri, 4 May 2001 12:45:38 +0900
yes, i put an old winmodem, test it and it works !!!
no idea why.
Maximus Idius
------------------------------
Date: Fri, 04 May 2001 00:57:15 -0300
From: Alberto Pires de Oliveira Neto <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.portable
Subject: Re: Kernel 2.4 : Ethernet connexion pb
Nicolas Delestre wrote:
> Hi,
> I have again a problem with the ethernet connexion of my computer under Kernel 2.4.3
>(not with the
> kernel 2.2.17, with this kernel everything works well).
> My computer is a Dell Latitude with Xircom (Ethernet + Modem) PCMCIA card.
> Since this morning, i success to detect my pcmcia card (thank you David Hints) but
>now when i try to
> make a ping to an other computer of my network, i get a "Destination Host
>Unreachable" error.
>
>
What happens if try a traceroute -n <computer_of_your_network> ? and do have gateway
to this host ?
------------------------------
Date: Fri, 04 May 2001 01:06:11 -0300
From: Alberto Pires de Oliveira Neto <[EMAIL PROTECTED]>
Subject: Re: what are the parameters for scsi aic7xxx (ultra160) card
Akram Abu-Odeh wrote:
I had a similar problem once with a 2Gb(ram) computer, even if it's not your
case, you should check to see if your kernel is configured for just 1Gb and
also check to if you aic7xxx is configured as a module in
your kernel.
------------------------------
Date: Fri, 04 May 2001 01:30:05 -0300
From: Alberto Pires de Oliveira Neto <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.networking,comp.os.linux.setup
Subject: Re: Two network cards
Stranger in the night expecting glanses wrote:
> I've got two tulip compatible network adapters in my computer, but i don't
> get them to work, as the first one should be used for pppoe (TDSL/
> germany).
> i configured it in KDE2, and got the message an icon will be available to
> connect to the net after the next xserver start... but i'm to stupid to
> find
> it.
> The normal network should work over eth1, but every action (ping etc) uses
> eth0, which is connected to the tdsl adapter...
> thanks for any help!
May be you should take a look at Ethernet-HOWTO, there you can find a lot of
tips.
------------------------------
Crossposted-To: alt.os.linux,comp.os.linux
Subject: Re: writing a kenel
From: [EMAIL PROTECTED] (no one)
Date: 4 May 2001 01:04:10 -0500
I don't think there is a college kid alive who hasn't reinvented the wheel
at least once.
All I have to say it that while it's an honorable goal, employers are not
impressed with such things anymore. They're more interested in: 1) will
you carry a pager with you on your wedding day, and 2) will you be the
sacrificial lamb and cover your bosses ass when the project fails due to
mismanagement or improper budgetting. :^P
-Bobert
"bindou" <[EMAIL PROTECTED]> wrote in <9cgkq8$nu0$[EMAIL PROTECTED]>:
>Hi all,
>I am a computer student and would like to write a kernel from scratch
>based on minix. I know that linux has already all the source code
>necessary for kernel writing and there are other free os with source
>code. But i would like to develop one myself just to get a grasp on the
>inner workings of my pc and to understand the linux kernel better. I
>have the intention to start with a 486 dx computer. anyone have any
>comments or suggestions??
>
>Rgds
>Bindou
>
>
>
>
====== Posted via Newsfeeds.Com, Uncensored Usenet News ======
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
======= Over 80,000 Newsgroups = 16 Different Servers! ======
------------------------------
From: "Bobby D. Bryant" <[EMAIL PROTECTED]>
Subject: Asus A7A266 and lm_sensors?
Date: Fri, 04 May 2001 01:03:25 +0600
Does anyone know how to get lm_sensors working on the Asus A7A266?
While running sensors-detect:
...
Probing for PCI bus adapters...
Use driver `i2c-matroxfb' for device 00:0c.0: MGA 2064W [Millennium]
Use of uninitialized value in numeric eq (==) at
prog/detect/sensors-detect line 870, <STDIN> line 1.
Use driver `i2c-ali15x3' for device 00:11.0: Acer Labs M7101
Probe succesfully concluded.
...
[The indicated line looks like it is part of a loop stepping through the
devices.]
...
We will now try to load each adapter module in turn.
[...fails on matroxfb, because I don't have the module -- different
problem...]
Load `i2c-ali15x3' (say NO if built into your kernel)? (YES/no):
/lib/modules/2.4.4-athlon/misc/i2c-ali15x3.o: init_module: No such
device
Hint: insmod errors can be caused by incorrect module parameters,
including invalid IO or IRQ parameters
/lib/modules/2.4.4-athlon/misc/i2c-ali15x3.o: insmod
/lib/modules/2.4.4-athlon/misc/i2c-ali15x3.o failed
/lib/modules/2.4.4-athlon/misc/i2c-ali15x3.o: insmod i2c-ali15x3 failed
Loading failed ()... skipping.
...
What device? There weren't any errors when I ran the script to make the
devices.
Also, /proc/pci doesn't show any 00:11.0, though it does have this:
...
Bus 0, device 17, function 0:
Bridge: Acer Laboratories Inc. [ALi] M7101 PMU (rev 0).
...
00:11.0 does show up in lspci though:
...
00:11.0 Bridge: Acer Laboratories Inc. [ALi] M7101 PMU
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
00: b9 10 01 71 00 00 00 02 00 00 80 06 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Thanks,
Bobby Bryant
Austin, Texas
------------------------------
From: "Bobby D. Bryant" <[EMAIL PROTECTED]>
Subject: Asus A7A266 and DMA?
Date: Fri, 04 May 2001 01:11:10 +0600
On my Asus A&A266, /proc/ide/ide0/hda/settings shows using_dma = 0. I'm
tempted to just enable it, but I'm wondering whether it might be the
symptom of a more serious problem.
>From /var/log/messages -
...
May 4 00:01:38 castor kernel: ALI15X3: IDE controller on PCI bus 00 dev
20
May 4 00:01:38 castor kernel: PCI: No IRQ known for interrupt pin A of
device 00:04.0. Please try using pci=biosirq.
May 4 00:01:38 castor kernel: ALI15X3: chipset revision 196
May 4 00:01:38 castor kernel: ALI15X3: not 100%% native mode: will
probe irqs later
May 4 00:01:38 castor kernel: ALI15X3: simplex device: DMA disabled
May 4 00:01:38 castor kernel: ide0: ALI15X3 Bus-Master DMA disabled
(BIOS)
May 4 00:01:38 castor kernel: ALI15X3: simplex device: DMA disabled
May 4 00:01:38 castor kernel: ide1: ALI15X3 Bus-Master DMA disabled
(BIOS)
May 4 00:01:38 castor kernel: hda: WDC WD400BB-00AUA1, ATA DISK drive
...
I don't see anywhere in the BIOS that requests disabling DMA. I tried
to track down the interrupt so I could set it with the pci= hint, and
found this -
...
00:04.0 IDE interface: Acer Laboratories Inc. [ALi] M5229 IDE (rev c4)
(prog-if
fa)
Subsystem: Asustek Computer, Inc.: Unknown device 8053
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Step
ping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort
- <MAbort- >SERR- <PERR-
Latency: 32 (500ns min, 1000ns max)
Interrupt: pin A routed to IRQ 0
Region 4: I/O ports at d400 [size=16]
Capabilities: [60] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot
-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00: b9 10 29 52 05 00 90 02 c4 fa 01 01 00 20 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 d4 00 00 00 00 00 00 00 00 00 00 43 10 53 80
30: 00 00 00 00 60 00 00 00 00 00 00 00 ff 01 02 04
...
Is it normal to route something to IRQ 0?
I have tried both "yes" and "no" to the "PNP OS" setting in the BIOS,
and it comes up with 00:04.0 --> IRQ 0 both ways.
Thanks,
Bobby Bryant
Austin, Texas
------------------------------
From: Tim Moore <[EMAIL PROTECTED]>
Subject: Re: ZIP problems
Date: Fri, 04 May 2001 07:16:06 GMT
John Bauer wrote:
>
> hi -
>
> i have problems mounting my ZIP under LINUX resp. under Windows.desperate
> as i am - i was wondering whether you could help.
<snip>
Use windows to format windows Zip drives, linux to format linux zip drives.
Linux can read and write either.
Put entries in /etc/fstab for ext2 and vfat versions. linux = partition 1,
vfat = partition 4:
...
/dev/sda1 /zip ext2 noauto,suid,user,defaults,rw 0 0
/dev/sda4 /Z vfat noauto,suid,user,defaults,rw 0 0
Look at dmesg output for which device (eg- sda, sdb) your system assigns. I
have one of the old parallel port Zip-100's:
...
kernel: parport0: PC-style at 0x378 [SPP,PS2,EPP]
...
kernel: ppa: Version 2.07 (for Linux 2.2.x)
kernel: ppa: Found device at ID 6, Attempting to use EPP 32 bit
kernel: ppa: Communication established with ID 6 using EPP 32 bit
kernel: scsi0 : SCSI host adapter emulation for IDE ATAPI devices
kernel: scsi1 : Iomega VPI0 (ppa) interface
...
kernel: Vendor: IOMEGA Model: ZIP 100 Rev: D.13
kernel: Type: Direct-Access ANSI SCSI revision: 02
kernel: Detected scsi removable disk sda at scsi1, channel 0, id 6, lun 0
...
kernel: SCSI device sda: hdwr sector= 512 bytes. Sectors= 196608 [96 MB]
[0.1 GB]
kernel: sda: Write Protect is off
--
timothymoore
bigfoot
com
------------------------------
From: Nicolas Delestre <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.portable
Subject: Re: Kernel 2.4 : Ethernet connexion pb
Date: Fri, 04 May 2001 09:24:02 +0200
Alberto Pires de Oliveira Neto wrote:
> Nicolas Delestre wrote:
>
>
>> Hi,
>> I have again a problem with the ethernet connexion of my computer under Kernel
>2.4.3 (not with the
>> kernel 2.2.17, with this kernel everything works well).
>> My computer is a Dell Latitude with Xircom (Ethernet + Modem) PCMCIA card.
>> Since this morning, i success to detect my pcmcia card (thank you David Hints) but
>now when i try to
>> make a ping to an other computer of my network, i get a "Destination Host
>Unreachable" error.
>>
>>
>
>
> What happens if try a traceroute -n <computer_of_your_network> ? and do have gateway
>to this host ?
If i run traceroute -n direction to a computer that are on the same network (just
seprate by a Hub)
i get the following result :
tracroute to 194.254.15.104 (194.254.15.104), 30 hops max, 38 bytes packets
1 194.254.15.104 2993.789 ms !H 3000.534 ms !H 2999.936 ms !H
..and the traceroute stops.
------------------------------
From: "J.H.ETTLE" <[EMAIL PROTECTED]>
Subject: Re: Floppy drive problems
Date: Fri, 04 May 2001 08:37:53 +0100
Fixed it. I kicked myself when I found out why. The power cord had come
out of the back of the drive. It seems that the drive's electronics are
powered independently from its motors, hence the lights coming on.
------------------------------
From: "J.H.ETTLE" <[EMAIL PROTECTED]>
Subject: Re: ZIP problems
Date: Fri, 04 May 2001 08:44:12 +0100
John Bauer wrote:
>
> hi -
>
> i have problems mounting my ZIP under LINUX resp. under Windows.desperate
> as i am - i was wondering whether you could help.
>
> pls, reply to me via e-mail: [EMAIL PROTECTED]
>
> some info: i have an IOMEGA IDE ZIP drive, run SuSE.
>
> everything worked fine with my first ZIP disk, but my new ones don't work.
> first, i couldn't mount them under LINUX (using: mount -t vfat /dev/hdd4
> /zip), but they worked fine for Windows. so, i used fdisk resp. sfdisk to
> delete the partitions on the ZIP, which were kinda all messed up, created
> a new, empty hdd4, and used mkfs.msdos /dev/hdd4 to write a DOS
> filesystem. this works fine with LINUX, i can mount with the usual
> command, but Windows can't read the ZIP, saying it doesn't recognise the
> filesystem. when i use IOMEGAWARE under Windows to re-format the ZIP, it
> works well for Windows but under LINUX: no way to mount it on hdd4; hdd
> goes.
>
> this is what IOMEGAWARE "produces" on the ZIP after formatting it:
> ---BOF---
>
> Disk /dev/hdd: 64 heads, 32 sectors, 96 cylinders
> Units = cylinders of 2048 * 512 bytes
>
> Device Boot Start End Blocks Id System
> /dev/hdd1 ? 937477 1203315 272218546+ 20 Unknown
> Partition 1 has different physical/logical beginnings (non-Linux?):
> phys=(356, 97, 46) logical=(937476, 3, 15)
> Partition 1 has different physical/logical endings:
> phys=(357, 116, 40) logical=(1203314, 30, 19)
> Partition 1 does not end on cylinder boundary:
> phys=(357, 116, 40) should be (357, 63, 32)
> /dev/hdd2 ? 649505 912677 269488144 6b Unknown
> Partition 2 has different physical/logical beginnings (non-Linux?):
> phys=(288, 110, 57) logical=(649504, 0, 11)
> Partition 2 has different physical/logical endings:
> phys=(269, 101, 57) logical=(912676, 1, 10)
> Partition 2 does not end on cylinder boundary:
> phys=(269, 101, 57) should be (269, 63, 32)
> /dev/hdd3 ? 263179 945973 699181456 53 OnTrack DM6 Aux3
> Partition 3 has different physical/logical beginnings (non-Linux?):
> phys=(345, 32, 19) logical=(263178, 26, 16)
> Partition 3 has different physical/logical endings:
> phys=(324, 77, 19) logical=(945972, 51, 15)
> Partition 3 does not end on cylinder boundary:
> phys=(324, 77, 19) should be (324, 63, 32)
> /dev/hdd4 * 680971 680981 10668+ 49 Unknown
> Partition 4 has different physical/logical beginnings (non-Linux?):
> phys=(87, 1, 0) logical=(680970, 34, 16)
> Partition 4 has different physical/logical endings:
> phys=(335, 78, 2) logical=(680980, 61, 8)
> Partition 4 does not end on cylinder boundary:
> phys=(335, 78, 2) should be (335, 63, 32)
> ---EOF---
>
I have a similar problem. Apparently, Windows 98 formatted the Zip Disk
FAT (like a floppy). The only machines with Zip drives at university are
Windows machines (yuck), and it was only after I'd filled it up with
several downloads and a kernel updated that I discovered that Linux
(with or without mtools) would refise to mount it.
------------------------------
From: "arthur" <[EMAIL PROTECTED]>
Subject: Re: $200 graphics card
Date: Fri, 04 May 2001 00:54:31 -0700
In article <[EMAIL PROTECTED]>, "Michael"
<[EMAIL PROTECTED]> wrote:
> need help selecting a graphics card for a new system i am building. I
> don't run games, but kids might play a few. SYSTEM:
> athlon 1.2
> iwill kk266
> 512 mb pc-133 micron
> 30 gb maxtor ata/100
> 10.2 gb maxtor ata/33
> sound= turtle beach (probably)
> thanks michael
>
I'm using a 32meg Pine NVidia TNT called Detonator
(where do they dig up these exotic names for video cards?) that works
fine for me on RH 7.0 and Win98. I don't know the exact price, but you
can purchase the 16mb version for about $45 at a computer show.
Arthur
------------------------------
From: Tim Moore <[EMAIL PROTECTED]>
Subject: Re: via 82c686a
Date: Fri, 04 May 2001 07:55:01 GMT
Alessandro D'Angelo wrote:
>
> I red there is problem with this south bridge and linux ata66 patch, for
> kernel 2.2.x, is it true?
> And if is true, there are solutions?
I use 2.2.19 + ide.2.2.19.04092001.patch with no problems.
[tim@abit linux]# cat /proc/ide/via
==========VIA BusMastering IDE Configuration================
Driver Version: 3.20
South Bridge: VIA vt82c686a
Revision: ISA 0x22 IDE 0x10
BM-DMA base: 0xd001
PCI clock: 35MHz
Master Read Cycle IRDY: 0ws
Master Write Cycle IRDY: 0ws
BM IDE Status Register Read Retry: yes
Max DRDY Pulse Width: No limit
=======================Primary IDE=======Secondary IDE======
Read DMA FIFO flush: yes yes
End Sector FIFO flush: no no
Prefetch Buffer: no no
Post Write Buffer: no no
Enabled: yes yes
Simplex only: no no
Cable Type: 80w 80w
===================drive0====drive1====drive2====drive3=====
Transfer Mode: PIO PIO PIO PIO
Address Setup: 28ns 28ns 28ns 28ns
Cmd Active: 84ns 84ns 84ns 84ns
Cmd Recovery: 56ns 56ns 56ns 56ns
Data Active: 84ns 84ns 84ns 84ns
Data Recovery: 56ns 56ns 56ns 56ns
Cycle Time: 42ns 140ns 42ns 140ns
Transfer Rate: 46.6MB/s 14.0MB/s 46.6MB/s 14.0MB/s
ftp.it.kernel.org/pub/linux/kernel/people/hedrick/
or see http://www.kernel.org/mirrors/
--
timothymoore
bigfoot
com
------------------------------
** 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
******************************
