Linux-Setup Digest #649, Volume #19 Tue, 19 Sep 00 05:13:11 EDT
Contents:
Re: NEW NVIDIA DRIVERS (Warning) (moonie;))
Can't install Linux of ATA100 Harddisk? ("24601")
Hard drive forgets partitions (John Wilkinson)
External Modem Woes ([EMAIL PROTECTED])
Re: Increase memory (Eric)
Partition Problems (Hanno =?iso-8859-1?Q?B=F6ttcher?=)
Re: modem initialization problem (Francis Tseng)
Re: modem initialization problem (Francis Tseng)
help with redhat 6.2 and upgrades (Stephen P. Hill)
Re: NEW NVIDIA DRIVERS (Warning) (Bernhard Mogens Ege)
Re: Installation problem (Jim Backus)
Re: Existing Partition/newbie (Jim Backus)
----------------------------------------------------------------------------
From: moonie;) <[EMAIL PROTECTED]>
Crossposted-To: alt.linux,alt.os.linux.mandrake,comp.os.linux.x
Subject: Re: NEW NVIDIA DRIVERS (Warning)
Date: Tue, 19 Sep 2000 02:08:10 -0400
On Fri, 08 Sep 2000, Bernhard Mogens Ege wrote:
>>>>>> "Stuart" == Stuart Levy <[EMAIL PROTECTED]> writes:
>
>> In article <[EMAIL PROTECTED]>,
>> Bernhard Mogens Ege <[EMAIL PROTECTED]> wrote:
>>> I would be very carefull with these new nvidia drivers (version 0.9-5)
>>> as I have just lost my ext2 partition due to a crash caused by these
>>> drivers. I am reinstalling redhat as I type this.
>> [...]
>
>> Do you enable DMA on your hard disk? If so, don't!
>
>No DMA enabled. AMD chipset not recognized in RedHat kernels.
>
>> With earlier NVidia drivers (0.92), I did experience lockups,
>> and if I had DMA enabled on my IDE system drive, my filesystem
>> would be corrupted (chunks of i-node control information replaced
>> by junk) at essentially every lockup. With DMA off -- using slower
>> PIO for disk I/O -- I still got lockups, but never any filesystem
>> corruption.
>
>Good for you (not loosing data). I did get filesystem corruption with
>DMA off. It is less likely to appear with DMA off, I believe, but not
>impossible.
>
>> I haven't tried any of the more recent NVidia drivers (0.93-0.95)
>> though maybe I'll try again now -- but with DMA disabled, for sure.
>
>I did not have problems with DMA enabled and XFree86-4.0 and the 0.92
>drivers. Only the later ones posed problems.
>
>> I did report the above to NVidia and to this newsgroup. I never heard
>> back from NVidia, but did see a reference from there to a web page
>> I'd mentioned with a screen snapshot of an opengl rendering defect,
>> so somebody *was* paying attention to bug reports.
>
>I also reported some of my experiences and files bugreports to nvidia
>without ever hearing from them.
>
>> For free software, I don't expect help-line support. Sounds good to me.
>
>I don't expect help-line support, just a feedback on bugreports. I can
>live without that feedback if only I knew they were working that much
>harder on removing the cause for the crashes instead of fixing minor
>problems.
>
>> Stuart Levy, [EMAIL PROTECTED]
>
>Bernhard Ege
Hate to burst your bubble but its not the drivers themselves, I have VIA
chipset with K6-III/450 running ATA/66 with DMA and all the optimizations
running with XFree86 4.0, Nvidia .94's on a TNT2U. Same with my friends C300
with TNT. My sons system doesn't like (locks up on boot up) the optimizations
(pcchips mobo, going to replace it soon with the 503a like mine) with or
without XFree86 4.0/.94 nvidia.
--
moonie ;)
Registered Linux User #175104
http://counter.li.org
KDE2
Kernel 2.4.0-test5
XFree86 4.0 Nvidia .94 drivers
RAID 0 Striped
Test-Pilots-R-Us ;)
------------------------------
From: "24601" <[EMAIL PROTECTED]>
Subject: Can't install Linux of ATA100 Harddisk?
Date: Tue, 19 Sep 2000 13:49:39 +0800
Can't install Linux of ATA100 Harddisk?
Installing System can't check ATA100 harddisk,
is this true?& Is it have some driver to supported ATA100
Linux: red-hats linux 6.2,
Harddisk: Maxtor 15GB ATA100 IDE Harddisk,
IDE Cable: ATA66
------------------------------
From: John Wilkinson <[EMAIL PROTECTED]>
Subject: Hard drive forgets partitions
Date: Tue, 19 Sep 2000 06:34:40 GMT
Hi all,
I have been using Mandrake 7.0 now for some months with no complaints. I
got a 7.1 disk the other day and decided to update. However during
installation I ran out of disk space and the whole process ended in a
lock up. So I reset my PC, and behold a system that refused to boot into
linux.
OK I was going to change my partion sizes on my 4G HD anyway. So I
decided to go the whole hog and install 7.1 from scratch.
I put Linux on my second drive and made partion sizes as /boot=20M, /=~
3G, swap=64K and /home=the rest =~1G
Ok Mandrake did all the usual stuff and installed without a hitch.
On reboot I find that system commander says that there is only one
partion and that when I boot that the kernel starts to boot then hangs
with a message like "Kernel panic cant find hdb5" or something like
that.
I have tried about 6 installs now all with the same problem.
Could it be the partion table problem on the second drive, and if so how
do I go about correcting it?
Do I need a new HD?
Any suggestions?
Regards,
John.
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.hardware,comp.os.linux.help,comp.os.linux.networking
Subject: External Modem Woes
Date: Tue, 19 Sep 2000 07:12:01 GMT
I recently purchased a Zoltrix Rainbow 56K external to replace one
burned up in a storm we had here. My old Zoom 56K external ran
flawlessly under Linux. This new one does not.
The one thing I do notice is that this one is seen by Windows Plug and
Play. Is there something anyone may suggest for trying to get this up
and running under Linux? I have no probs under Windoze.
I can implicitly assign it a stty/com number, and it dials out under
Linux in kppp, but falis to connect to the host. It fails to be
detected in wvdial in SUSE 6.3 at all.
I also notice that unless it is turned on, it is not seen by Win2000.
I get a "not connected" when I pull up modem properties in Control
Panel.
The Zoltrix uses a Rockwell ACF56K chipset.
I have it connected to stty01 aka COM2.
please email as well as post any suggestions. Thanks!
------------------------------
From: Eric <[EMAIL PROTECTED]>
Subject: Re: Increase memory
Date: Tue, 19 Sep 2000 09:13:01 +0200
Reply-To: [EMAIL PROTECTED]
Mr. Liaw wrote:
>
> Hi
> I am new in Linux world.
> I recently installed a Red Hat Linux 6.2. Initially I only have 64M of
> memory. I have increase it to 128M but it seem that linux still using 64M.
> Can anyone show me how to change the system configuration so that linux will
> fully utilize all 128M.
add the line append="mem=128m"
to your lilo.conf (check manpage for correct syntax)
> Is there any place I can adjust the grasphic resolution from 640 x 480
> to 800 x 600.
in /etc/X11/XF86Config
Eric
> Thanks
>
> Teck Meng, Liaw
Eric
------------------------------
From: Hanno =?iso-8859-1?Q?B=F6ttcher?=
Subject: Partition Problems
Date: Tue, 19 Sep 2000 08:54:27 +0100
Hi all!
Following scenario:
I have one 20 GB Harddisk (dev/hda). I want to install a
Multi-OS-System:
Win98 (For Playing Games not running under Win2000 or Linux)
Win2000 (Playing and using programs only available for Windows)
Debian 2.2 (For all important things ;-))
I would like to have Lilo as a boot loader in the MBA managing the start
process.
I need 3 primary system partitions:
Win98 (~2GB)
Win2000 (~3GB)
/boot (~10 MB)
+
Exchange Partition (Fat32) (~9 GB)
Linux Partitions (/, /var, /usr, /root).
=> I have to make about 8 Partitions, 5 Logical.
I tried this several times, but I always get problems with the Lilo. Can
anyone explain me the necessary rules for partitioning? It seems I'm to
silly to find it out myself :-((((((
Thank you very much for helping a Newbie
Hanno
------------------------------
From: Francis Tseng <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware,comp.os.linux.misc
Subject: Re: modem initialization problem
Date: Tue, 19 Sep 2000 02:41:46 -0500
I've tried setserial as well. In particular, I use the following line:
setserial -v /dev/ttyS0 port 0x3f8 auto_irq autoconfig
and the response I get is:
/dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4
Under Windows, my modem is configured for com 1 on irq 4.
Again, to reiterate the problem, the modem only responds to the "AT" command
if I turn it off and back on during a minicom session. If I don't switch the
modem off and on and run minicom for a second time, the modem still does not
respond to the "AT" command.
--
Francis
L Ellison wrote:
> Read the man page on setserial. Your modem is probably using a non-standard
> IRQ and you need to tell the kernel this at boot time. This info is
> supposed to go in /etc/rc.d/rc.serial but I had to put it in
> /etc/rc.d/rc.sysinit. ( format ) setserial
> /dev/ttySx IRQ y x=your modem comm port, y=your modem IRQ. If you
> dual boot Windows, go there and find out what comm port the modem is using.
> It will not be diferent in Linux. DOS com1=ttyS0 com2=ttyS1 etc. Also
> find out the IRQ while in Win. If you don't have Win, keep trying IRQs
> until you find the right one. It will probably be : 2 3 4 5 7 9 but
> possibly one of the higher #s.
------------------------------
From: Francis Tseng <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc,comp.os.linux.hardware
Subject: Re: modem initialization problem
Date: Tue, 19 Sep 2000 03:05:58 -0500
The problem is that I can't get the modem to respond to the "AT" command
in the first place. I've also tried typing "+++" as you have suggested
but nothing happens. How do you recommend checking for IRQ conflicts?
The Modem-HOWTO says that looking at /proc/interrupts or the output of
setserial will not necessaily provide an indication of a conflict. As I
indicated in a previous post, the output of running the command:
setserial -v /dev/ttyS0 port 0x3f8 auto_irq autoconfig
is
/dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4
which is the same as how my modem is configured under Windows.
--
Francis
MaryP wrote:
-
- In article <[EMAIL PROTECTED]>, Francis Tseng
- <[EMAIL PROTECTED]> wrote:
-
- > Hi, I have a Zoom external modem but have trouble initializing it
upon
- > boot. After my system is ready, I run minicom and don't get the "OK"
- > prompt. If I type "AT" myself, I see nothing on the screen. The
strange
- > thing is that if I switch the power of my external modem off and
then on
- > again, I can get the modem to respond with "OK" when I type
- > "AT". Does anyone know why this is happening? Oh, the modem is
turned on
- > during the boot process.
-
- I still have the manual for an old 28.8 Zoom here, and the init string
- that reset it to factory specs was AT&F. AT&F1 is also a common init
- string. Give those a try, as well as ATZ. I don't know if those same
- commands work with modern Zooms or not, but hey. If you do not have
your
- modem's docs, try looking up Zoom's web site.
-
- Maybe the modem is getting turned on (at boot) in data mode instead of
AT
- (command) mode. On one of mine, the characters +++ and a one-second
pause
- escape it into AT mode if it is in data mode. See what happens if you
send
- it those characters. If it sends you an OK after the +++ (pause), then
you
- can start sending it AT commands. (I know this applies to internal
modems,
- not sure about externals -- ?)
-
- Is your computer messing around with the IRQ your modem is using? Did
you
- check for IRQ conflicts before *and* after switching the modem off and
on
- manually? Plug and play could be playing tricks. If so, you could
always
- tell the computer to leave it alone at boot and just turn the modem on
by
- hand until you sort this one out.
-
- HTH
- MP
------------------------------
From: [EMAIL PROTECTED] (Stephen P. Hill)
Subject: help with redhat 6.2 and upgrades
Date: 19 Sep 2000 04:08:47 -0400
Hi all:
I installed RedHat 6.1 on my system a few weeks before 6.2
became available. I just got around to upgrading, via the
automatic "upgrade" option, and then I installed the misc
security and bug fixes that are currently available.
[ P-II 350 MHz with 192 MB Ram, EIDE HD, ATAPI cdrom, plus
a Tekram DC390U2W SCSI controller with a small spare HD,
tape backup, and CDRW on the narrow bus. Simple ISA
modem and soundcard, i740 agp video ]
The system was seeming stable and working well until the
end. I can't quite recall if it was the libc update or
the kernel upgrade to 2.2.16-3 that was about the time
I first noticed problems.
The first thing that happened was that my cdrw wrote
several coasters, with a scsi sendcmd error. I thought
it was my cheap blanks and tried a better one - same
problem.
Next, I noticed that good data CDs wouldn't mount in
my IDE/ATAPI cdrom drive any more - it would give
errors about the wrong media type, just like what
I get if try to mount an audio CD. The same discs
work fine in the SCSI cdrw, and they sometimes
will mount in the ATAPI reader after a boot.
Next, I had problems with Gnome - those I tracked
down to options changing in a GDM config file,
and RPM not installing the changed config file.
Maybe not related.
Next, I noticed font error messages when exiting
X. They just indicate that xfs couldn't translate
some fontname to a fontname.
Lastly, I noticed that "gtcd" coredumps on me when
I run it. Running it under GDB shows:
> Program received signal SIGSEGV, Segmentation fault.
> 0x8050de4 in setup_fonts ()
I am suspicious about the fonts - any ideas? I hauled
out my RedHat disk again and installed almost every
font there, at least the ones that looked useful.
Thanks for any help,
=======
Thanks,
Stephen P. Hill
[EMAIL PROTECTED]
------------------------------
Crossposted-To: alt.linux,alt.os.linux.mandrake,comp.os.linux.x
Subject: Re: NEW NVIDIA DRIVERS (Warning)
From: Bernhard Mogens Ege <[EMAIL PROTECTED]>
Date: Tue, 19 Sep 2000 08:05:31 GMT
>>>>> "whoever" == whoever <moonie> writes:
> On Fri, 08 Sep 2000, Bernhard Mogens Ege wrote:
>>>>>>> "S" == S Umar <[EMAIL PROTECTED]> writes:
>>
>>> Did you compile the kernel module from source rpm? I have no problems
>>> using ANY of the nvidia drivers with my GeForce 256 and 2.2.16 kernel.
>>> I don't think using your ext2 partition had anything to do with these
>>> drivers....I think NVIDIA has done a great job putting together a
>>> install FAQ....As I said I have been using 0.92 through 0.95 WITH NO
>>> PROBLEMS!!! Let's be more fair.
>>
>> I am as fair as I can be. Loosing my filesystem really wasn't what I
>> needed. Nowhere in the FAQ does it say that you could potientially
>> loose your filesystem, now does it.
>>
>> I dont know what went wrong. I am not able to debug these drivers. I
>> have to disable Agp support using the nvidia drivers, and why is that?
>> Nvidia even doesn't know, but in Windows, it works. With agp, X hangs
>> and any attemt to kill it freezes my machine.
>>
>> The FAQ doesn't mention any problems with the GeForce card, only
>> TNT1/2 cards. I am using a TNT2 card, which I might have forgotten to
>> write.
>>
>> Neither of this changes my point. I lost my filesystem trying to make
>> the nvidia driver work. Why I lost it, I dont know. I did an rpm -ivh
>> on both rpm files, compiled with rpm -ba SPECS/NV... and installed the
>> resulting package.
>>
>> The FAQ says nothing about the /usr/lib/libGL.a file which needs to be
>> removed. Nor does it check that the /usr/lib/libGL.so link actually
>> points to libGL.so.1.0.5 (which it does not if Mesa is installed).
>>
>> So the rpm installation does not install properly and one need to
>> remove both /usr/lib/libGL.a and /usr/lib/libGL.so.1.2.030300 (or
>> whatever the name).
>>
>> Not doing so will cause a wrong GL library to be loaded and errorneous
>> communication with NVdriver results. This again can crash X and the
>> kernel (whatever it might be doing at that point, e.g. update the
>> filesystem).
>>
>> I have now reinstalled redhat (necessary) and installed the 0.9-5
>> nvidia drivers, being very careful about what files I left behind and
>> what files I deleted/moved and managed to get an image on
>> screen (first after adding NvAGP 0). I am not using the 2.2.17 kernel
>> this time but am using the 2.2.16-21 kernel from rawhide.
>>
>> As I managed to loose my filesystem easily in connection with
>> upgrading to nvidia drivers, I felt I had to share my bad
>> experience. This might cause people to check again to see if they have
>> done their upgrade right before starting X.
>>
>> I will now test nvidia driver a bit, but am expecting it to crash my
>> machine. But if not, hey, great, to finally made it (except for agp
>> support, have to mail them about that).
>>
>> Besides, you having no problems with the drivers only means that your
>> cpu/motherboard/graphic card combo is better supported than my
>> combo. We can't all be using GeForce cards.
>>
>> regards,
>>
>> Bernhard Ege
> Well I'm not using a GeForce, I am using a TNT2U and DIDN'T install from RPM's
> I installed from source! Have used the .94's with 2.2.14 and now 2.4.0-test5
> (it has AGP support BTW) and have also used the same procedure to install them
> on my friends TNT, and my sons TNT2 M64 with no problems, and no lockups. I
> read that installing XFree86 4.0 and the nvidia drivers from RPM's were a bad
> idea, so I never tried!
You did notice the part where I used the 2.2.17 kernel and not the
2.2.14 like you do? The 2.2.17 kernel does not appear to be compatible
with nvidia's drivers, as I am not the only one to discover.
I don't care if it is stable for you (not quite true), I want it
stable for my setup! I am using the original Athlon 500 on the MSI6167
motherboard (AMD chipset) and the 3com network driver. Apparently,
this is a bad combination as it crashes linux once in a while (only
when running 100mbps on my network interface, otherwise
stable). Anyway, I don't think its the 3com drivers fault as they
apparently work well for other setups. I has to be a problem with the
nvidia drivers (they are the newest drivers, even newer than my
motherboard).
Anyway, my motherboard just died (human error) and I have to replace
it. Maybe one of the same type.
regards,
Bernhard
------------------------------
Date: Tue, 19 Sep 2000 09:17:39 +0100
From: Jim Backus <[EMAIL PROTECTED]>
Subject: Re: Installation problem
Student wrote:
>
> After I have install the Linux, I have found that some files such as the
> inetd.conf has a modified date and access date19-Sept 11:45am, which is 12
> hrs faster. And this make me cannot do any in the linuxconf. The linuxconf
> always gives me the message that "The file /etc/inetd.conf as revision date
> in the future. This probably means that you system time is wrong or as been
> wrong at some point." And it also gives me some other message about the same
> thing for other files with date 19-Sept.
> Could someone please kindly help me to solve the problem?
Use "touch" to change file date stamp? (I'm no expert)
--
Jim Backus
------------------------------
Date: Tue, 19 Sep 2000 09:18:38 +0100
From: Jim Backus <[EMAIL PROTECTED]>
Subject: Re: Existing Partition/newbie
Bryce Mitchell wrote:
>
> I already have a partion that I have formatted to install Linux on. However,
> I know realise that this was stupid because Linux does not recognise the
> Windows Formated Drive and thinks there is no space on the disc. Help! How
> can I make it recongise the space?
Use Linux "fdisk" followed by "make2fs"? (I'm no expert)
--
Jim Backus
------------------------------
** 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.setup) 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-Setup Digest
******************************
