Linux-Hardware Digest #385, Volume #14 Fri, 23 Feb 01 02:13:03 EST
Contents:
Cable modem, DHCP , MAC Problem ("Hatem")
Lockup under load -- Intel CA810E ("KR")
Re: G400 & dual monitors ("D. Stimits")
Re: linux 2.4.1 and pppd (Glitch)
Re: How-to- Linux on Unix?? (David Efflandt)
Re: mounting udf cds as nonroot (Matt Haley)
Losing My Mind Over Hardware Conflict ("Tim Little")
Re: Losing My Mind Over Hardware Conflict (Robert Redelmeier)
Re: Losing My Mind Over Hardware Conflict ("Roy B")
Big Drive, Reluctant BIOS, how to work around? ("g.montgomery")
NetGear FA310TX (Tim Lyth)
Dual NIC Problem ("Ken Wilson")
Re: ATI Radeon + Linux ("Wes Campaigne")
Re: adaptec boot (Mark)
Re: mounting udf cds as nonroot (Matt Haley)
Re: A new driver for Netgear fa311 netcard working on RedHat Linux 7 + kernel 2.4
(Simon)
Re: Netgear FA311 and nvidia drivers (Simon)
----------------------------------------------------------------------------
From: "Hatem" <[EMAIL PROTECTED]>
Subject: Cable modem, DHCP , MAC Problem
Date: Fri, 23 Feb 2001 02:20:50 GMT
Hi all,
Everyone knows that cable modem companies are dhcp complient but at the end
you can use the given IP and treate it as a fixed IP address.
I have two computers, the first one has windows and linux (dual boot) and I
configured its network cards on both operating systems and everything works
just perfect!
Now there is another computer (firegate), and I need to make it my
gateway/firewall/proxy linux server, and I had two net cards in it, I tried
the net cards and tested their operability and they are both working
excellent.
Now on this Firegate computer the first card ifcfg-eth0 need to be connected
to the internet (cable modem)..
Bill helped me to setup the proper network and IP addresses (thanks Bill)
but I still could not get the connection to the internet working, I tried to
ping www.sybase.com and www.oracle.com and even www.microsoft.com and here
what happens:
1) the send and recieve lights on the cable modem are blinking on a rythem,
that the packets are sent and recieved..
2) I do not recieve a successful ping result on my computer screen.
What I am suspecting, is that the cable modem whcih is (TERAYON) has lost
the MAC address that it recognized first (which is on the other computer)
,,,
So is my guess correct?
if no please help me!
second thing, is there a way to re-register a new MAC on the cable modem?
without the use of DHCP or DHCP is a must in this case??
At the end, I really would like to thank all the people who helped me to
have my beautiful linux up and running!!
------------------------------
From: "KR" <[EMAIL PROTECTED]>
Subject: Lockup under load -- Intel CA810E
Date: Fri, 23 Feb 2001 02:29:34 GMT
The one with integrated video & ethernet. IDE drives &CD. PIII 866, 256MB.
RH6.2 install OK, noticed the video driver problem so don't run X. Uptime
3+ weeks OK with light ftp and telnet usage. Then five minutes under a
serious load (top says 99+% cpu usage as it's processing large image files)
and it just hangs. Won't respond to ping. It's not the program crashing;
the same tasks run fine on RH6.2 elsewhere in the lab. No messages on the
console and don't know where else to look. I have four of these that were
OK just sitting there doing nothing for 3+ weeks, and today tested two under
load with the same result. Very distressing.
Would someone please tell me how to ask an intelligent question about the
problem?
------------------------------
Date: Thu, 22 Feb 2001 19:54:20 -0700
From: "D. Stimits" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Re: G400 & dual monitors
Marc Ulrich wrote:
>
> I've noticed a few messages here about this subject, but I yet have some
> questions.
>
> My system uses RedHat 7.0 with the 2.4.1 kernel which I compiled for
> this system.
>
> How can I determine the version of XFree86 on my system?
Run "xdpyinfo | less", and near line 4 you will find "vendor release
number". For 4.0.2, the number is 4002. For 4.0.0, it is 4000.
>
> I also found matrox's readme file rather confusing. I'm rather new to
> compiling pieces of the kernel (I barely survived the 2.4.1 upgrade) or
> other packages, such as XFree86. What is matrox referring to in the
> readme with the "/xc/..." directory? No such thing exists on this
> system.
Generic instructions for a complete X source compile would have you
unpack into /xc/, which you would create. You might be better off
finding Linux-specific instructions. You probably don't need to do an X
compile, likely some prebuilt version will do the job. I'm not familiar
with matrox requirements, but Xinerama seems to be available by default
on the linux distributions shipping with 4.0.x (redhat 7.1 beta works
quite well for what I've tried). There is a possibility that your X
already supports what you are looking for, but simply isn't configured
for it. I think what you are looking for is Xinerama (maybe someone
knows, is it still using that name? I recall recently something related
had its name changed).
>
> Thanks,
> Marc
------------------------------
Date: Thu, 22 Feb 2001 22:29:03 -0500
From: Glitch <[EMAIL PROTECTED]>
Subject: Re: linux 2.4.1 and pppd
pppd 2.4+ is needed when upgrading beyond kernel 2.4.....it says that in
the Changes file I believe.
Larry Sonderling wrote:
>
> I have recently upgraded from kernel 2.2.16 to 2.4.1 and I when I try to
> connect to my ISP pppd dies with a syslog message of "ioctl(PPPIOCGFLAGS)
> invalid arguement" after successfully connecting. This never occurred under
> 2.2.16 and I cannot find a clue in the documentation that I have. i am
> using pppd 2.1.13. Is there a newer version of pppd that I should use with
> kernel 2.4.1 or have I missed something obvious?
>
> thanks,
>
> Larry
------------------------------
From: [EMAIL PROTECTED] (David Efflandt)
Crossposted-To: alt.os.linux.caldera,comp.os.linux.setup
Subject: Re: How-to- Linux on Unix??
Date: Fri, 23 Feb 2001 03:25:44 +0000 (UTC)
Reply-To: [EMAIL PROTECTED]
On Thu, 22 Feb 2001 14:09:09 -0800, Mun Sing <[EMAIL PROTECTED]> wrote:
>Hi,
>
>I am new to Linux.... and I am wondering if it is possible Linux on a
>Unix System??
>I know it does not make much of a scene... but this question just pop
>into my head...
>If anyone has tried it or have some knowledge of it.
Not sure what you are asking, but FreeBSD can run many Linux binaries
(probably RH 6.1) using something that I think is called a compat
package. When it recognizes a Linux ELF program it runs it under a Linux
like directory structure containing Linux libs.
However, somewhat problematic was that FreeBSD (at least 4.0) could read,
but not write to RH 6.x ext2 file systems (it could write RH 5.2 ext2).
But RH 5.2 cannot write to RH 6.x file systems either (something changed
in 6.x ext2).
But if you can get Unix sources (instead of binaries only), it is best to
compile them on the system you are running (Linux or whatever).
--
David Efflandt [EMAIL PROTECTED] http://www.de-srv.com/
http://www.autox.chicago.il.us/ http://www.berniesfloral.net/
http://cgi-help.virtualave.net/ http://hammer.prohosting.com/~cgi-wiz/
------------------------------
From: [EMAIL PROTECTED] (Matt Haley)
Crossposted-To: comp.os.linux.setup
Subject: Re: mounting udf cds as nonroot
Date: Fri, 23 Feb 2001 03:44:25 -0000
On Thu, 22 Feb 2001 17:28:38 -0500,
Gregory Davis <[EMAIL PROTECTED]> wrote:
>either an iso cd or a udf cd in the same drive as a user! Still, I don't
>know why the auto entry in fstab doesn't find udf. Maybe this is something
>that needs to be addressed in the next version of mount. dunno.
>From the man page for mount (concerning the '-t' option):
The type iso9660 is the default. If no -t option
is given, or if the auto type is specified, the
superblock is probed for the filesystem type
(minix, ext, ext2, xiafs, iso9660, romfs ,ufs,
ntfs, qnx4, bfs are supported). If this probe
fails, mount will try to read the file
/etc/filesystems, or, if that does not exist,
/proc/filesystems. All of the filesystem types
listed there will be tried, except for those that
are labeled "nodev" (e.g., devpts, proc and nfs).
It appears that udf isn't in the list of filesystems that 'auto' checks for.
--
Matt Haley <[EMAIL PROTECTED]>
Mandrake 7.2 / RedHat 6.1 / Windows 98 SE / FreeBSD 4.2 / Windows NT 4
------------------------------
From: "Tim Little" <[EMAIL PROTECTED]>
Subject: Losing My Mind Over Hardware Conflict
Date: Fri, 23 Feb 2001 04:11:40 GMT
PROBLEM: System lockups requiring hard shutdown after accessing a SCSI device.
Distribution: RedHat 6.2, unmodified 2.2.14-5 kernel.
Mainboard: ASUS A7V
CPU: AMD Duron 850
3Com 3c905 10/100 NIC
BusLogic Flashpoint SCSI controller, BT-930
Ensoniq ES1371 Soundcard
3dfx Voodoo3 2000 AGP Video
****** /proc information at end of text *******
This mainboard has a number of integrated devices, such as a
Promise ATA 100 controller. I've disabled
everything that can be disabled in the BIOS, including serial and printer
ports.
The SCSI controller runs a CD-RW and a DAT drive, both of which ran
well until they were installed on the new mainboard.
The 3com NIC and the Ensoniq soundcard are newly acquired, but the other
components were pulled from my last computer, where they all worked
together happily.
What happens now is that, although I get a good boot, good ethernet, and
good soundcard performance, doing anything with any device on the SCSI
card produces a lock-up. Sometimes, I can work for a few minutes from a
disk in the CD-RW before it hangs - - i.e., I can browse a few JPGs from a
CD-ROM before a lockup occurs, forcing a hard shutdown.
This seems to be a perfectly stable system until I activate a SCSI
device. At that point, she crashes within seconds.
If anyone has the patience to help an old hand, I could sure use some
tips.
Here's some info from /proc:
/proc/Interrupts:
CPU0
0: 434452 XT-PIC timer
1: 7218 XT-PIC keyboard
2: 0 XT-PIC cascade
5: 14 XT-PIC BusLogic BT-930
8: 1 XT-PIC rtc
9: 7246 XT-PIC eth0
10: 8147 XT-PIC es1371
12: 165707 XT-PIC PS/2 Mouse
13: 1 XT-PIC fpu
14: 171767 XT-PIC ide0
15: 308 XT-PIC ide1
NMI: 0
/proc/pci
Bus 0, device 0, function 0:
Host bridge: VIA Technologies Unknown device (rev 2).
Vendor id=1106. Device id=305. Medium devsel. Master Capable. No
bursts. Prefetchable 32 bit memory at 0xe4000000 [0xe4000008].
Bus 0, device 1, function 0:
PCI bridge: VIA Technologies Unknown device (rev 0).
Vendor id=1106. Device id=8305. Medium devsel. Master Capable. No
bursts. Min Gnt=8.
Bus 0, device 4, function 0:
ISA bridge: VIA Technologies Unknown device (rev 34).
Vendor id=1106. Device id=686. Medium devsel. Master Capable. No
bursts.
Bus 0, device 4, function 1:
IDE interface: VIA Technologies VT 82C586 Apollo IDE (rev 16).
Medium devsel. Fast back-to-back capable. Master Capable.
Latency=32. I/O at 0xb800 [0xb801].
Bus 0, device 4, function 2:
USB Controller: VIA Technologies VT 82C586 Apollo USB (rev 16).
Medium devsel. IRQ 9. Master Capable. Latency=32. I/O at 0xb400
[0xb401].
Bus 0, device 4, function 3:
USB Controller: VIA Technologies VT 82C586 Apollo USB (rev 16).
Medium devsel. IRQ 9. Master Capable. Latency=32. I/O at 0xb000
[0xb001].
Bus 0, device 4, function 4:
Host bridge: VIA Technologies Unknown device (rev 48).
Vendor id=1106. Device id=3057. Medium devsel. Fast back-to-back
capable.
Bus 0, device 10, function 0:
SCSI storage controller: BusLogic FlashPoint (rev 1).
Fast devsel. IRQ 5. Master Capable. Latency=32. Min Gnt=8.Max
Lat=8. I/O at 0x9400 [0x9401]. Non-prefetchable 32 bit memory at
0xdd800000 [0xdd800000].
Bus 0, device 11, function 0:
Multimedia audio controller: Ensoniq ES1371 (rev 2).
Slow devsel. IRQ 10. Master Capable. Latency=32. Min Gnt=12.Max
Lat=128. I/O at 0x9000 [0x9001].
Bus 0, device 13, function 0:
Ethernet controller: 3Com 3C905 100bTX (rev 0).
Medium devsel. IRQ 9. Master Capable. Latency=32. Min Gnt=3.Max
Lat=8. I/O at 0x8800 [0x8801].
Bus 0, device 17, function 0:
Unknown mass storage controller: Promise Technology Unknown device
(rev 2).
Vendor id=105a. Device id=d30. Medium devsel. IRQ 10. Master
Capable. Latency=32. I/O at 0x8400 [0x8401]. I/O at 0x8000
[0x8001]. I/O at 0x7800 [0x7801]. I/O at 0x7400 [0x7401]. I/O at
0x7000 [0x7001]. Non-prefetchable 32 bit memory at 0xdd000000
[0xdd000000].
Bus 1, device 0, function 0:
VGA compatible controller: 3Dfx Unknown device (rev 1).
Vendor id=121a. Device id=5. Fast devsel. Fast back-to-back
capable. IRQ 11. Non-prefetchable 32 bit memory at 0xde000000
[0xde000000]. Prefetchable 32 bit memory at 0xe2000000 [0xe2000008].
I/O at 0xd800 [0xd801].
/proc/ioports
0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0070-007f : rtc
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
02f8-02ff : serial(auto)
0376-0376 : ide1
03c0-03df : vga+
03f6-03f6 : ide0
03f8-03ff : serial(auto)
8800-883f : eth0
9000-903f : es1371
9400-94ff : BusLogic BT-930
b800-b807 : ide0 b808-b80f : ide1
------------------------------
Date: Thu, 22 Feb 2001 22:41:41 -0600
From: Robert Redelmeier <[EMAIL PROTECTED]>
Subject: Re: Losing My Mind Over Hardware Conflict
Tim Little wrote:
>
> PROBLEM: System lockups requiring hard shutdown after
> accessing a SCSI device.
[...]
> The SCSI controller runs a CD-RW and a DAT drive, both of which
> ran well until they were installed on the new mainboard.
Could you have a bus topology [cabling] or termination problem?
The SCSI card might be happier in a different PCI slot.
-- Robert author `cpuburn` http://users.ev1.net/~redelm
------------------------------
Reply-To: "Roy B" <[EMAIL PROTECTED]>
From: "Roy B" <[EMAIL PROTECTED]>
Subject: Re: Losing My Mind Over Hardware Conflict
Date: Fri, 23 Feb 2001 05:55:34 GMT
After studying the info you sent - it appears that the Ensonique audio
controller and the 'unknown mass storage controller" are both trying to park
on interrupt 10.
So perhaps as soon as you try to access the SCSI controller the O.S.
responds by branching to the audio driver code and everything goes downhill
from there in a hurry? I don't know the kernel internals or dev driver
API's but perhaps (probably) interrupt sharing is frowned on.
Does your motherboard support manual BIOS assignment of interrupts to PCI
slots? If so perhaps you could re-assign either the audio or the SCSI
controller to interrupt 9 or 11?
Hope this helps or leads to something else that helps.
Incidentally - in case you aren't aware, most BIOS's sort of flash a screen
at you for 3 microseconds during the boot process that tells you which
devices are on what interrupts. It might be interesting to freeze that
(with the 'Pause' key) and see if what it says agrees with what Linux thinks
is happening (in /proc/interrupts).
Let us know how you do.
"Robert Redelmeier" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Tim Little wrote:
> >
> > PROBLEM: System lockups requiring hard shutdown after
> > accessing a SCSI device.
> [...]
> > The SCSI controller runs a CD-RW and a DAT drive, both of which
> > ran well until they were installed on the new mainboard.
>
> Could you have a bus topology [cabling] or termination problem?
> The SCSI card might be happier in a different PCI slot.
>
> -- Robert author `cpuburn` http://users.ev1.net/~redelm
------------------------------
From: "g.montgomery" <[EMAIL PROTECTED]>
Subject: Big Drive, Reluctant BIOS, how to work around?
Date: Fri, 23 Feb 2001 05:57:24 GMT
Okay, I've been down this road once, and as I
recall, I conquered the monster, but cannot
locate the documentation as to how. Perhaps
someone on this list has the answer...
I did an install from scratch on a 40 GB maxtor
with a 1 Gig / partition, a couple 128 Meg
swap partitions, a 4 Gig /usr partition, and the
rest in one large /home partition.
The thing will only boot from a floppy, and then
only if I tell the bios in the standard cmos setup
that there the Primary Master is of type None.
If I leave the Primary Master set to auto, the
BIOS hangs when looking for the Primary Master
drive. I remember this situation as being one
where I am running into a problem with a drive
that is over 30 Gig or something like that. I
also remember something about a jumper on
the drive which can be set to limit the apparent
size of the drive to a small number (maybe it
was around 2 Gigs) to the BIOS. I remember
going round and round with this, trying the
jumper, trying various BIOS settings, etc. But
I can't remember the path through the maze.
It could be that I never was able to get this
particular machine's BIOS to work, and simply
moved the over 30 Gig drives onto other
machines out of frustration. I am determined
to find out what is causing this, and get a
set of settings which work, or replace the BIOS
or the whole motherboard.
Coes anyone have a ready explanation of a way
through this? My machine is as follows:
Award BIOS: ROM PCI/ISA BIOS (2A5KKJ1E)
Processor K6/2 400 MHz
RAM: 128 MB
Hard Drive: Maxtor Model 34098H4, Cylinders:
16383, Heads: 16, Sectors: 63, 40.9 GB It has
a "4096 Cylinder Limit" jumper location, currently
not set.
To summarize, my HD isn't recognized by my BIOS,
but when booted from floppy, the HD is recognized
by Linux EIDE drivers and works flawlessly. What
setup permits me to boot from the HD?
TIA,
Gene
------------------------------
From: Tim Lyth <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.networking
Subject: NetGear FA310TX
Date: Fri, 23 Feb 2001 06:08:48 GMT
Hi.
I was wondering if anyone has successfully install a NetGear FA310TX NIC on a
computer running Redhat 7.0 with kernel 2.2.16? If so, could you please tell me
how as I'm having difficulties.
When I type 'lsmod' the tulip module is not on the list until I load it. But it
isn't loaded when I boot up Redhat.
When I use netconf to setup the NIC, if I specify an IRQ or an I/O port, both of
which are optional I get an error message saying something about insmod and the
tulip.o (the driver for this particular card) module. However, if I don't
specify either an IRQ or I/O port, I get an IP initialisation failure.
In either case, I can't access the internet.
Fortunately (for me), I have not disposed of Windoze which is what's allowing me
to write the post.
------------------------------
From: "Ken Wilson" <[EMAIL PROTECTED]>
Subject: Dual NIC Problem
Date: Fri, 23 Feb 2001 06:17:22 GMT
I have installed two Linksys Ether16 LAN cards in a Packard Bell Legend
2051. I have been able to get one of the card recognized but not the
second. Both have been reconfigured to be non-PNP using the DOS setup
utility supplied with the cards and each given distinctive base IO addresses
and IRQs, 0x280 IRQ 3 and 0x380 IRQ 15. The cards are NE2000 clones.
My set up in conf.modules is as follows:
alias eth0 ne
alias eth1 ne
options ne io=0x280,0x380 irq=3,15
Just the way the HOWTO says to. In addition I have tried append in lilo in
order to get the two cards recognized. My append string is as follows
append "ether=3,0x280,0,1,eth0 ether=15,0x380,0,1,eth1"
Hunting around in the various logs it seems that the module for these cards,
ne.c, only probes one card and never probes the second. The sad part is
that individually, these cards both work.
Current installation consists of RedHat 6.2 on a 486 w/12MB RAM.
Any help ferreting out a solution is greatly appreciated as I'd like to get
this router established before the real computer comes home from Compusmart
this weekend.
--
Ken Wilson
[EMAIL PROTECTED]
------------------------------
From: "Wes Campaigne" <[EMAIL PROTECTED]>
Subject: Re: ATI Radeon + Linux
Date: Fri, 23 Feb 2001 06:24:28 GMT
> :> Has anyone successfully gotten the Radeon working with X in at least
2D?
> :> I have an AMD Athlon 650 on the irongate chipset. I just swapped out my
> :> G400 for the Radeon and installed X 4.02 and the server goes to change
> :> into SVGA mode and then I get the good ole BSOD. If anyone knows of a
> :> fix please let me know.
> :>
> :> John
> :
X 4.02 comes in a few different flavours, depending on which CVS it came
from. The DRI project people are the ones doing major work for open source,
fully accelerated drivers for the Radeon. See dri.sourceforge.net for more
info on that....
What's in your XF86Config file? Running "XFree86 -configure" in 4.02
should recognize the Radeon and generate a decent config file
On my machine (Radeon DDR 64MB on a ASUS A7V, which uses the KT133 chipset,
with a TBird 800) I got it working without problems... again, though, it
depends on the build of X.
> b. There are no text consoles. I really miss these.
> c. If you kill the server, you're dead--there's no text
> console fallback.
Unfortunate... that's something one usually depends on when doing any of the
things referred to in threads like these :P
> d. There's no support for USB mice.
>
?? Really? As far the X Server is concerned, USB mice should be the same as
any PS/2 mouse, except its reading from a different config file; the
protocol's the same.
Can't you point the server to /dev/input/mice or make a symlink to that?
-Wes
------------------------------
From: Mark <[EMAIL PROTECTED]>
Subject: Re: adaptec boot
Date: Fri, 23 Feb 2001 06:27:26 GMT
I had the same problem.
recompiled the kernel and put scsi as a module and things died.
Have to put ramdisk ability in and compile that way if you want scsi as a
module, and boot from the drive.
(mkinitrd stuff)
The howto on recompiling the kernel for 2.2 has the relevant stuff,
(works for 2.4 as well) but the mkinitrd section did the trick for me.
ymmv.
Drew Roedersheimer wrote:
> On 21 Feb 2001 00:13:09 -0500, Eric P. McCoy wrote:
> >Tom Gafford <[EMAIL PROTECTED]> writes:
> >
> >> I'm trying to set up an adaptec 2940u2w to boot directly into linux.
> >> The
> >> disk works fine when I do a lilo boot from a floppy. I have the
> >> adaptec scsi select set to include the drive in the bios scan, and to
> >> boot the unit number of the drive, and the motherboard bios to try the
> >> adaptec before the ide drive (MB is Intel 440-BX 'Jabil'), and it sure
> >> looks like YaST (SuSE 6.3) is writing to the MBR of the scsi drive when
> >> I do a lilo config, but it
> >> sure don't boot! Is this supposed to work?
> >
> >Yes. I have an onboard AIC7895 which I've used to boot just fine.
> >
> >You might get more help if you described what, exactly, went wrong.
> >Did you see any part of the "LILO" message, or does the BIOS simply
> >report it can't boot from the device? When installing LILO, does it
> >do anything like warn you about possibly not installing on the boot
> >device?
> >
> >--
> >Eric McCoy <[EMAIL PROTECTED]>
> > "Knowing that a lot of people across the world with Geocities sites
> >absolutely despise me is about the only thing that can add a positive
> >spin to this situation." - Something Awful, 1/11/2001
>
>
> This may not be it at all, but I'll give you my $0.02. I have the same
> board
> which I've been using for quite a while under linux. I use lilo, and I've
> found that I need to compile the aic7xx support (I think that's the name)
> directly into the kernel... I'm sure there's a workaround with modules,
> but if I don't compile it into the kernel, it hangs on boot. If you're
> not
> even getting a boot prompt, then this is probably not the issue. Answers
> to Eric's questions would probably shed some more light on the real
> problem...
>
>
> HTH
> -DR
>
------------------------------
From: [EMAIL PROTECTED] (Matt Haley)
Crossposted-To: comp.os.linux.setup
Subject: Re: mounting udf cds as nonroot
Date: Fri, 23 Feb 2001 06:29:29 -0000
Don't you love it when you read your post and notice something you should have
said earlier? Read on...
On Fri, 23 Feb 2001 03:44:25 -0000,
Matt Haley <[EMAIL PROTECTED]> wrote:
>On Thu, 22 Feb 2001 17:28:38 -0500,
> Gregory Davis <[EMAIL PROTECTED]> wrote:
>
>>either an iso cd or a udf cd in the same drive as a user! Still, I don't
>>know why the auto entry in fstab doesn't find udf. Maybe this is something
>>that needs to be addressed in the next version of mount. dunno.
>
>From the man page for mount (concerning the '-t' option):
>
> The type iso9660 is the default. If no -t option
> is given, or if the auto type is specified, the
> superblock is probed for the filesystem type
> (minix, ext, ext2, xiafs, iso9660, romfs ,ufs,
> ntfs, qnx4, bfs are supported). If this probe
> fails, mount will try to read the file
> /etc/filesystems, or, if that does not exist,
> /proc/filesystems. All of the filesystem types
> listed there will be tried, except for those that
> are labeled "nodev" (e.g., devpts, proc and nfs).
>
>It appears that udf isn't in the list of filesystems that 'auto' checks for.
So, after re-reading this above quote I check my /proc/filesystems
and saw that udf was listed so mount should be trying for it when
you specify auto as the type. Yes, except I had an /etc/filesystems
that _didn't_ list udf. Now, since I don't have a udf cd to try out
anymore I can't test myself, but, I would suggest adding udf to
/etc/filesystems and see if it'll be detected by mount.
--
Matt Haley <[EMAIL PROTECTED]>
Mandrake 7.2 / RedHat 6.1 / Windows 98 SE / FreeBSD 4.2 / Windows NT 4
------------------------------
From: Simon <[EMAIL PROTECTED]>
Subject: Re: A new driver for Netgear fa311 netcard working on RedHat Linux 7 +
kernel 2.4
Date: Fri, 23 Feb 2001 06:30:04 -0000
Hi Yan,
I still have the 2.2.16-22 kernel, and I am having a real hard time
making the card work. What is involved in upgrading to the 2.4 release?
Is it a huge download?
I have been trying to get this card to work for three days now, and I am
really getting annoyed that it is coming up with a page of errors each
time I try to compile the driver. Can I get the driver to work with my
kernel, or do I need to upgrade it?
Thanks,
Simon. ([EMAIL PROTECTED])
Yan Deng wrote:
>
> Hi guys,
>
> I bought a Netgear netcard fa311 and installed it and its dirver on my
> RedHat Linux6.0. It worked well.
>
> After I upgraded RedHat Linux6.0 to RedHat 7.0 ( whose kernel
> is 2.2.16-22 ), it did not work. Then I upgraded the linux kernel
> from 2.2.16-22 to 2.4 , and modified the source file fa311.c that
> Netgear company provides with the netcard and made a new driver
> for the fa311 netcard working on RedHat Linux 7.0+ kernel 2.4.
>
> Does someone who needs a new driver for fa311 want to try to
> use it(free)?
>
> If you have questions, please feel free to ask me.
>
> Yan Deng
>
--
Posted via CNET Help.com
http://www.help.com/
------------------------------
From: Simon <[EMAIL PROTECTED]>
Subject: Re: Netgear FA311 and nvidia drivers
Date: Fri, 23 Feb 2001 06:30:05 -0000
Were you able to get your fa311 to work properly in the 2.2 kernel? I
have tried and tried, recompiled and recompiled, and all I get is errors.
What did you do to make the downloaded driver work?
Thanks,
Simon.
aflinsch wrote:
>
> Alim wrote:
> >
> > Hi there
> >
> > Does anybody know how to get the Netgear FA311 fast ethernet card up
and
> > running using the 2.4 kernel?
> >
>
> Not with the 2.4 kernel, but to get it working with the 2.2 kernel i
> needed to snag the updated driver source (downloadable from netgear,
> and probably elsewhere) & recompile.
>
> The driver & source provided with the card seem to have been for a 2.0
> kernel...
--
Posted via CNET Help.com
http://www.help.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
******************************
