Linux-Hardware Digest #555, Volume #13 Sun, 10 Sep 00 20:13:08 EDT
Contents:
Promise Ultra66 working, but IDE-DMA not ready for Prime Time
([EMAIL PROTECTED])
Tearing video display ("Computer")
Re: Synaptics Touchpad and kernel 2.2.16 (Alexander Clouter)
Re: Xsane Plugin with Gimp: PROBLEMS (Joshua Baker-LePain)
Re: Tearing video display ("grep")
lucky tech ("Mario Passaggio")
Re: Compaq presario 924 into a Linux Box ([EMAIL PROTECTED])
Re: Epson Stylus Photo 870 (Emilio Federici)
Re: mobile rack dangers?, ata33/66 (Felix Miata)
Re: BP6 / HPT366 Problems? (Jeroen Roodhart)
which kernel for 486+16MB? ([EMAIL PROTECTED])
Re: Davicom drivers and Mandrake (redhat) linux ??? (Michael Perry)
Re: BIOS setup on an old 386 (Tom Massey)
Re: which kernel for 486+16MB? (gLiTcH)
Re: BP6 / HPT366 Problems? (Hal Burgiss)
Kernel question (Greg Goossens)
Re: BP6 / HPT366 Problems? (Johnny Luong)
Re: which kernel for 486+16MB? ("Peter T. Breuer")
Re: BIOS setup on an old 386 (Yves Bellefeuille)
----------------------------------------------------------------------------
From: [EMAIL PROTECTED]
Subject: Promise Ultra66 working, but IDE-DMA not ready for Prime Time
Date: 10 Sep 2000 14:58:11 -0400
I have an Asus K7M board (AMD Irongate/Via chipset). Whenever I enable DMA on
the controller I get failures (dma timeouts) when the system is under heavy
load. The system either hangs completely or reverts to PIO mode when I get a
timeout. I've tried all the different patches and it still fails.
To get DMA working, I tried a Promise Ultra66 controller. I used kernel
2.2.16 with the IDE patch (ide.2.2.16.all.20000825). This appeared to work
fine ... but it caused the system to lockup under heavy load!
What do I mean by heavy load? I have one process repeatedly compiling the
kernel. A second process repeatedly runs the program "Bonnie" which tests
disk throughput. A third process does a file find over the entire disk. The
combination of these processes really tortures the disk. My system reliably
locks up after a few minutes of thrashing. I have no way of knowing what
error occurred, but lockups are reproduceable. Lockups do not occur when I
turn off DMA.
Conclusion: DMA on IDE disks is NOT reliable. The only systems that seem
reliable are Asus motherboards based on Intel chipsets. Other brands and/or
other chipsets may or may not work.
This is a real shame, since IDE disks are cheap and fast. I get the idea that
a lot of people are having trouble with DMA, though. Every time I look
at other hardware groups I hear of some people having trouble (under Windows).
Also, people may not realize that newer versions of Linux turn off DMA
by default. To see if DMA is on, type "/sbin/hdparm /dev/hda" (as root).
If anyone has suggestions (including ideas how to diagnose these problems),
please let me know.
Thanks,
Richard
------------------------------
From: "Computer" <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux.mandrake,comp.os.linux.setup
Subject: Tearing video display
Date: Sun, 10 Sep 2000 19:29:28 GMT
Hi!
I have a NEC Ready 7020 that I am trying to install Linux onto. Everything
seems fine except the XWindows display has horizontal distortion
("tearing"). What happens is the display is stable vertically, but the sides
of the screen are a bit jagged and unstable. The screen is readable and
almost useable, but the display jitters up to an inch from each side.
This machine uses a CL5434 video chip that built into the mainboard. There
is 2Meg of ram for the video display. The computer is connected to an NEC
XV15 monitor.
I have installed RedHat 5.2, Mandrake 6.0 and Storm Linux and all have done
the same thing. I also tried XVIDTUNE and none of the settings there had any
affect. There are no issues on this PC where Windows is concerned.
I don't know much about Linux so I'm at a dead end. ANY help would be
appreciated!
------------------------------
From: [EMAIL PROTECTED] (Alexander Clouter)
Crossposted-To: comp.os.linux.portable
Subject: Re: Synaptics Touchpad and kernel 2.2.16
Date: 10 Sep 2000 20:34:30 +0100
On Sat, 9 Sep 2000 13:36:03 -0400, Josh Jones <[EMAIL PROTECTED]> wrote:
>
> I have an Acer Travelmate 737TLV portable, and am having a problem
> configuring the touchpad to work correctly. I originally installed Red Hat
> 6.2, which had the 2.2.14 kernel. I recently upgraded the kernel to 2.2.16,
> and now when I move my touchpad, the hard drive spins nonstop for a few
> seconds while the mouse becomes unmovable, and then stops. It's possible to
> move the mouse but it is very difficult and not really usable. I tried the
> "tpconfig" touchpad driver version 2.2 (a popular driver provided by a third
> party source) but it doesn't seem to do anything... When I was running
> 2.2.14 the mouse worked, but had a tendency to "float" along the screen.
> Does anyone have any suggestions?
>
You must *not* run tpconfig with anything else using the /dev/psaux
port! This means X and gpm must *not* be running.
See what happens now :)
Also the synaptics touchpad can be set up to automatically scroll
(drift), be used without actually touching the pad and other fancy
things, such as being a third mouse button when you tap a corner etc
Alex
------------------------------
From: Joshua Baker-LePain <[EMAIL PROTECTED]>
Subject: Re: Xsane Plugin with Gimp: PROBLEMS
Date: 10 Sep 2000 19:45:36 GMT
Darren Enns <[EMAIL PROTECTED]> wrote:
> I tried compiling 'xsane' with the 'gimp' option:
> configure --enable-gimp
> This is what the messages were:
> checking whether GIMP plugin is requested... yes
> checking whether JPEG support is requested... yes
> checking whether PNG support is requested... yes
> checking whether TIFF support is requested... yes
> ...
> checking for libgimp/gimp.h... (cached) no
> checking for libgimp/gimpfeatures.h... (cached) no
Had you run configure before installing sane-devel? I'm thinking
the "cached" entries are your problem. Try this:
make distclean
./configure --enable-gimp
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
------------------------------
Reply-To: "grep" <[EMAIL PROTECTED]>
From: "grep" <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux.mandrake,comp.os.linux.setup
Subject: Re: Tearing video display
Date: Sun, 10 Sep 2000 20:06:32 GMT
sounds like the horizontal scan rate or timing is very wrong.
This is a job for xvidtune.
basically the beam is scanned from left to right, it should try to scan just
beyond the right edge of the screen then it should get a blanking pulse and
turn off the beam, the beam is pulled back across to the beyond the left
side of the screen, then the beam is turned back on and starts its next
sweep across the screen.
turning the beam off too soon causes a black bar at the right edge of the
screen and turning the beam back on too late causes a black bar at the left
edge of the screen.
no timer is really accurate so they bars tend to be jagged.
The long and the short of it is the basic timings are way off for the
monitor you have selected.
Ron
"Computer" <[EMAIL PROTECTED]> wrote in message
news:siRu5.7122$[EMAIL PROTECTED]...
> Hi!
>
> I have a NEC Ready 7020 that I am trying to install Linux onto. Everything
> seems fine except the XWindows display has horizontal distortion
> ("tearing"). What happens is the display is stable vertically, but the
sides
> of the screen are a bit jagged and unstable. The screen is readable and
> almost useable, but the display jitters up to an inch from each side.
>
> This machine uses a CL5434 video chip that built into the mainboard. There
> is 2Meg of ram for the video display. The computer is connected to an NEC
> XV15 monitor.
>
> I have installed RedHat 5.2, Mandrake 6.0 and Storm Linux and all have
done
> the same thing. I also tried XVIDTUNE and none of the settings there had
any
> affect. There are no issues on this PC where Windows is concerned.
>
> I don't know much about Linux so I'm at a dead end. ANY help would be
> appreciated!
>
>
>
------------------------------
From: "Mario Passaggio" <[EMAIL PROTECTED]>
Subject: lucky tech
Date: Sun, 10 Sep 2000 20:56:16 GMT
hi
a couple of days ago I got this luckytech mather board and a mountain of
problems fell on me (CPU's K7 700Mhz)
BIOS can see fd but it's unbootable I installed Linux and I found fd cannot
be mounted
PCI cards cannot be detected (but the videocard) and this was hardware
that worked on a celeron cpu
is there anyone can help me??
thanks a lot in advice
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Compaq presario 924 into a Linux Box
Date: Sun, 10 Sep 2000 17:30:21 -0400 (EDT)
I agree with what you wrote (reproduced below).
But also watch out for the video card, if your Presario has a discrete
video card. Even if the video is on the motherboard, you need to
research and determine which (albeit integrated) "video card" you have.
Then check to see if it is supported by xFree86, here:
http://www.xfree86.org/
I am finding not all video schemes are supported by free Linux software.
There are commercial suppliers out there, though, that cover some
unsupported computers. This has surprised me, as I naively thought all
Linux was free.
Linux does appear to have free support for most popular and modern
items. Also, it is likely free Linux will support your Presario video
for text. But for graphics I am less certain, and you really need to
check.
Good luck.
~~~~~~~~~~~~~~~~~~~~~
You wrote:
Compaq presario 924 into a Linux Box
Group: comp.os.linux.hardware
Date: Mon, Sep 11, 2000, 12:47am (EDT+12)
From: [EMAIL PROTECTED] (Michelle)
Hello:
Has anybody converted a Compaq presario 924 into a Linux Box?
Presently I have one with Win95 OSR2 installed with the original 524 MB
Connor? HDD. with 24 mb RAM which I am thinking of installing Linux RH
6.2
AS the presario is different in having its "BIOS" as a partition on the
HDD itself and so I guess things would be a bit different.
I would probably install a bigger HDD (6GB Quantum).
Does f anyone has any tips/things to watch out for.
TIA
------------------------------
From: Emilio Federici <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Re: Epson Stylus Photo 870
Date: Sun, 10 Sep 2000 22:28:39 GMT
Wolfgang Fritz wrote:
>
> Emilio Federici wrote:
> >
> > Hi everybody!, I've recently bought this printer and I'm working on
> > trying to make it usable under Linux (SuSE 6.2).
>
> I did exactly what you want to to, but with an Epson Stylus Color 850.
> If you are interested in my setup, I can mail you my configuration.
>
> Wolfgang
Thanks Wolfgang I'll appreciate this very much.
--
Emilio Federici
NUOVO INDIRIZZO-> [EMAIL PROTECTED] <- NUOVO INDIRIZZO
ICQ:27013758
------------------------------
From: Felix Miata <[EMAIL PROTECTED]>
Crossposted-To: comp.sys.ibm.pc.hardware.storage
Subject: Re: mobile rack dangers?, ata33/66
Reply-To: Felix Miata <[EMAIL PROTECTED]>
Date: Sun, 10 Sep 2000 14:19:49 -0400
Dan Jacobson wrote:
> After weeks of happy computing, one day I turned on my PC and see "BOOT
> DISK FAILURE".
> I pull out "TP-20" mobile rack with Quantum 24Gb [1st IDE slave] and thank
> gawd, 15Gb Seagate [Master] still boots. I put in old 2Gb Seagate
> [slave] in rack, again no disks are detected at all [CD ROM still detected
> though]. I eliminate rack and directly connect old 2Gb Seagate to IDE
> cable and all is OK. I now instead put [slave] Quantum 24Gb on IDE
> cable... again, no disks are detected.
> I happen to have a second identical mobile rack [box & shell], but it's no
> difference... By the way, my 166Mhz Pentium computer uses the traditional
> IDE cables, whereas, in the mobile racks there are the new dense ATA-66
> cables... apparently no big deal. That the Quantum has Linux on it vs.
> win98 for the other two drives doesn't seem important, as the BIOS didn't
> even auto-find the disks like in the past. How now is it that my
> computer suddenly cannot use mobile racks anymore, and cannot autodetect
> the Quantum 24Gb anymore? The Quantum does spin. What did I do wrong?
> Did the cheap mobile racks get me in the end? Here's some info from the
> "Unicore BIOS Wizard" program the I downloaded from
> http://www.unicore.com/bioswiz/ :
> [SiS 5513 Dual PCI IDE Controller]
> BIOS Date: 01/22/98
> BIOS Type: Award Modular BIOS v4.51PG
> BIOS ID: 01/22/98-SiS-5598-<SP97_V>C-00
> BIOS Eval: #401A0-0106v
> Chipset: SiS 5597 rev 2
> Superio: Winbond 877F (use 87h) rev 0 found at port 3F0h
I've used the cheap variety of SCSI racks with cool running Quantum
Fireball ST & SE 5400 RPM drives for several years, but not for booting
a 24/7 system. I've had several bays defective from the start, but never
one that quit after working past the warranty period, nor have I
suffered a HD failure whilst using one.
Quantum has a free IDE diagnostic program on their web site. Run it.
Then call Quantum's 800 support number. What you tell them is up to you,
but currently available plastic racks without cooling fans typically
warn that they are not suitable for use with drives faster than 4500
RPM. What this really means is you shouldn't put a hot running drive in
one of these bays. How hot is hot is an interesting question, but you'd
be hard pressed to convince me to put any 7200 RPM boot device in an
uncooled plastic cartridge.
Think about it. A normal HD installation involves attaching the metal HD
case to your metal computer case with metal screws. Metal is a good heat
conductor, which means your computer's case is part of its cooling
system.
Conversely, plastic is a good heat insulator, besides doing a fair job
of inhibiting air flow to the device inside it. It doesn't take a
genious to see the potential for head related HD trouble when a plastic
removable rack is involved.
--
A discerning man keeps wisdom in view, but a fool's eyes wander to the
ends of the earth. Proverbs 17:24 NKJV
Team OS/2
Felix Miata *** http://mrmazda.members.atlantic.net
------------------------------
From: Jeroen Roodhart <[EMAIL PROTECTED]>
Crossposted-To: alt.comp.periphs.mainboard.abit
Subject: Re: BP6 / HPT366 Problems?
Date: Mon, 11 Sep 2000 00:47:00 +0200
Reply-To: [EMAIL PROTECTED]
Thanks for that bit of info Hal, this will certainly keep me from
wasting a lot of time to see if I can get it working ;)
Hal Burgiss wrote:
>
>
> This has been a hot button issue with MS BP6 users too, if that is any
> consolation.
Hmmm, I haven't experienced any problems under Windows 2K or Windows SE,
but that may just follow from the fact that I run Linux for the vast majority
of time... I didn't do any bechmarks under Windows either, so I haven't checked
if the Highpoint Windows drivers actually use UDMA4 ;)
If this turns out to be a persistent problem, there probably should be something
of a black list compiled.
Are the same kind of problems existent in the ATA100 spec as well? I just got
used
to not looking very hard at the linux compatibility listing when buying new
hardware.
I guess I shouldn't have :)
Anyway, thanks again, we know Andrew Hedrick is doing a great job, I've used his
driver for quite some time now (albeit at UDMA2 ;)),
Jeroen
--
-- Toevallig wel! --
Jeroen Roodhart ([EMAIL PROTECTED]) | Registered Linux User No. 73309
Brouwersgracht 214 III | Member of the UvA RoboSoccer Team
1013 HD, Amsterdam, The Netherlands | http://www.robocup.nl
------------------------------
From: [EMAIL PROTECTED]
Subject: which kernel for 486+16MB?
Date: Sun, 10 Sep 2000 22:36:16 GMT
Hi,
I will soon be using a 486 computer
to run Linux and it only has 16 megs of
RAM. I can try to find a RAM upgrade
but can anyone tell me if the latest
kernel, if stripped down to exclude
SMP and useless drivers, will work
alright on such a system?
Thanks
uwuh
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: [EMAIL PROTECTED] (Michael Perry)
Crossposted-To: comp.os.linux.networking,comp.os.linux.setup
Subject: Re: Davicom drivers and Mandrake (redhat) linux ???
Date: Sun, 10 Sep 2000 14:36:02 -0700
Reply-To: [EMAIL PROTECTED]
On Fri, 08 Sep 2000 17:43:25 +0100, David Yan <[EMAIL PROTECTED]> wrote:
>You will find the driver and full instructions on the CD that came with
>the motherboard.
>
>Hope this helps,
>Dave.
>
>
>peter wrote:
>
>> I'm using Mandrake 7.1 and everyone is saying that the Davicom lan
>> (dm9102) on my Amptron 599lmr (PCCHIPS) should be auto-detected...and
>> that it can also be setup with netconf, the only problem I have with
>> the netconf command is that I don't know what the name of the driver
>> is, the file is "dmfe" but nothing like that is listed in the Kernel
>> Module setting.
>>
>> Can someone help me setup this lan, step by step.
>>
>> Thanks,
>>
>> Peter
>
My issue with my motherboard with an integrated davicom card is that the
drivers are way old! On my redhat 6.2 box, all I did was to use linuxconf
to basically add a line to /etc/conf.modules which says "alias eth0 dmfe".
This produced a working eth0 for me on the next reboot. The drivers which I
found with redhat 6.2, installed as modules, were much newer than the ones
which came on cd. In fact, the cd drivers would not even install on a 2.2
kernel.
Try simply writing an alias command in /etc/conf.modules like "alias eth0
dmfe".
--
Michael Perry
[EMAIL PROTECTED]
==================
------------------------------
From: Tom Massey <[EMAIL PROTECTED]>
Subject: Re: BIOS setup on an old 386
Date: Mon, 11 Sep 2000 10:06:09 +1100
"M. Buchenrieder" wrote:
> Your problem is that you'll need a floppy with the BIOS setup
> program on it. ISTR that this is like the older Phoenix BIOS
> setup programs that you had to write on a floppy (360k) to
> get into the BIOS. That kind of machines doesn't have a
> CMOS setup program that you could invoke from the keyboard.
Thanks for your reply. Do I have to use a 360k floppy for this? This
would explain why I've been unable to get it to boot using 1.2M disks.
I've got a couple of generic setup programs that should work, but I just
can't seem to make a boot disk that will boot the machine.
Thanks,
Tom
------------------------------
Date: Sun, 10 Sep 2000 19:12:18 -0500
From: gLiTcH <[EMAIL PROTECTED]>
Subject: Re: which kernel for 486+16MB?
ram has nothing to do with the kernel size
the kernel has to fit within the 640k limit i believe, which has nothing
to do with how much ram you have installed. Unless u are running an
embedded system you should be able to include most things in the kernel
instead of using modules however if the kernel is too big then instead
of using 'make zImage' use 'make bzImage'
[EMAIL PROTECTED] wrote:
> Hi,
> I will soon be using a 486 computer
> to run Linux and it only has 16 megs of
> RAM. I can try to find a RAM upgrade
> but can anyone tell me if the latest
> kernel, if stripped down to exclude
> SMP and useless drivers, will work
> alright on such a system?
> Thanks
> uwuh
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
------------------------------
From: [EMAIL PROTECTED] (Hal Burgiss)
Crossposted-To: alt.comp.periphs.mainboard.abit
Subject: Re: BP6 / HPT366 Problems?
Reply-To: Hal Burgiss <[EMAIL PROTECTED]>
Date: Sun, 10 Sep 2000 23:11:28 GMT
On Mon, 11 Sep 2000 00:47:00 +0200, Jeroen Roodhart
<[EMAIL PROTECTED]> wrote:
>Thanks for that bit of info Hal, this will certainly keep me from
>wasting a lot of time to see if I can get it working ;)
>
>Hal Burgiss wrote:
>>
>>
>> This has been a hot button issue with MS BP6 users too, if that is
>> any consolation.
>
>Hmmm, I haven't experienced any problems under Windows 2K or Windows
>SE, but that may just follow from the fact that I run Linux for the
>vast majority of time... I didn't do any bechmarks under Windows
>either, so I haven't checked if the Highpoint Windows drivers actually
>use UDMA4 ;)
I followed BP6 issues on an abit.mainboard news group for some time back
when I was having lockups (unrelated issue). There was many lengthy
threads on this -- most from MS users that insisted Maxtor was broken
re: HPT. But, there were some (seemed to be a minority) that said they
were doing just fine. So? Maybe just certain models? Maybe other
contributing factors, eg load? Conflicts with other hardware?
>If this turns out to be a persistent problem, there probably should be
>something of a black list compiled.
Yea, but neither Maxtor nor HTP nor Abit want to admit the problem
(assuming I am right of course).
>Are the same kind of problems existent in the ATA100 spec as well? I
Dunno. What I am telling you is just word of mouth type stuff. I never
could find any hard evidence anywhere on this. I did have private email
correspondence with a guy who claimed he got someone at Maxtor to admit
to the problem. But I never could find a reference on their website, or
Highpoints, or Abit's for that matter.
>just got used to not looking very hard at the linux compatibility
>listing when buying new hardware. I guess I shouldn't have :)
Actually, if you look at linux-ide, Maxtor, IBM, and Quantam (IIRC), seem
to be recommended drives. Specific issues don't seem to be addressed.
>Anyway, thanks again, we know Andrew Hedrick is doing a great job, I've
>used his driver for quite some time now (albeit at UDMA2 ;)),
Yea, Andre is OK.
--
Hal B
[EMAIL PROTECTED]
[EMAIL PROTECTED]
--
------------------------------
From: Greg Goossens <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,comp.os.linux.misc,linux.redhat.misc,linux.redhat
Subject: Kernel question
Date: Mon, 11 Sep 2000 10:40:12 +1000
This is a multi-part message in MIME format.
==============6A668699406B30B87A4A4EF3
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
I have a question regarding a problem I have that I need to find a
simple solution for I am hoping that someone has a neat workaround for
this.
I need to setup an IBM Netfinity 6000 with Redhat 6.2 but the kernel in
the ISO image I have is a 2.2.14 kernel and the only kernel that
supports the RAID adapter is a 2.2.16-3 kernel. I can install redhat
using the device driver provided from IBM but when I reboot after the
initial install the system hangs. As I have said IBM say I need the
2.2.16-3 kernel.
Is the solution as simple as getting another release of redhat that has
the correct kernel in the original install (if possible ) or do I have
to build a redhat install on another disk upgrade that kernel and
somehow move the entire load to another disk using dd of a similar util.
==============6A668699406B30B87A4A4EF3
Content-Type: text/x-vcard; charset=us-ascii;
name="goossens.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for Greg Goossens
Content-Disposition: attachment;
filename="goossens.vcf"
begin:vcard
n:Goossens;Greg
x-mozilla-html:TRUE
org:Volante Group Ltd
adr:;;;;;;
version:2.1
email;internet:[EMAIL PROTECTED]
title:Network Systems Engineer
fn:Greg Goossens
end:vcard
==============6A668699406B30B87A4A4EF3==
------------------------------
Crossposted-To: alt.comp.periphs.mainboard.abit
Date: Sun, 10 Sep 2000 16:58:40 -0700
From: Johnny Luong <[EMAIL PROTECTED]>
Subject: Re: BP6 / HPT366 Problems?
Shrug, if the problems are associated with the components, then ultimately
it falls on the vendor of such components.... and that would probably
be ABIT in my case. I've had to return the board myself for a defective
transistor (?) and the HPT366 just add to the list of woes that I have
with the board... (amonsgst acpi, etc.) And yes Hedrick does a good
job, but if the hardware is lacking, then I'm not gonna blame the
programmer who made it possible for me to use in the first place. Other
people on the kernel mailing list posted something similar but offered
no solutions (other than the usual hdparm look at, which still didn't
address the problem). And if Abit is releasing a distro on it, they
should be concerned because of possible data corruption since their
redhat-based distro uses the hpt366 code that is publicly available. (the
nice gentus cd that comes with your board)
Just my two cents... I've about given up on trying to figure it out
and I'm putting my hard drive into another case with a different board.
Oh well, I was kinda hoping somebody had some unique idea to solve it. :)
On Sun, 10 Sep 2000, Hal Burgiss wrote:
> On Mon, 11 Sep 2000 00:47:00 +0200, Jeroen Roodhart
> <[EMAIL PROTECTED]> wrote:
> >Thanks for that bit of info Hal, this will certainly keep me from
> >wasting a lot of time to see if I can get it working ;)
> >
> >Hal Burgiss wrote:
> >>
> >>
> >> This has been a hot button issue with MS BP6 users too, if that is
> >> any consolation.
> >
> >Hmmm, I haven't experienced any problems under Windows 2K or Windows
> >SE, but that may just follow from the fact that I run Linux for the
> >vast majority of time... I didn't do any bechmarks under Windows
> >either, so I haven't checked if the Highpoint Windows drivers actually
> >use UDMA4 ;)
>
> I followed BP6 issues on an abit.mainboard news group for some time back
> when I was having lockups (unrelated issue). There was many lengthy
> threads on this -- most from MS users that insisted Maxtor was broken
> re: HPT. But, there were some (seemed to be a minority) that said they
> were doing just fine. So? Maybe just certain models? Maybe other
> contributing factors, eg load? Conflicts with other hardware?
>
> >If this turns out to be a persistent problem, there probably should be
> >something of a black list compiled.
>
> Yea, but neither Maxtor nor HTP nor Abit want to admit the problem
> (assuming I am right of course).
>
> >Are the same kind of problems existent in the ATA100 spec as well? I
>
> Dunno. What I am telling you is just word of mouth type stuff. I never
> could find any hard evidence anywhere on this. I did have private email
> correspondence with a guy who claimed he got someone at Maxtor to admit
> to the problem. But I never could find a reference on their website, or
> Highpoints, or Abit's for that matter.
>
> >just got used to not looking very hard at the linux compatibility
> >listing when buying new hardware. I guess I shouldn't have :)
>
> Actually, if you look at linux-ide, Maxtor, IBM, and Quantam (IIRC), seem
> to be recommended drives. Specific issues don't seem to be addressed.
>
> >Anyway, thanks again, we know Andrew Hedrick is doing a great job, I've
> >used his driver for quite some time now (albeit at UDMA2 ;)),
>
> Yea, Andre is OK.
>
> --
> Hal B
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> --
>
>
Johnny Luong
[EMAIL PROTECTED]
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: which kernel for 486+16MB?
Date: 10 Sep 2000 23:48:30 GMT
gLiTcH <[EMAIL PROTECTED]> wrote:
: ram has nothing to do with the kernel size
: the kernel has to fit within the 640k limit i believe, which has nothing
You believe wrong, but some aspects of what you say are not entirely
incorrect. A running kernel will occupy about 1.5 to 2MB nowadays.
Perhaps more. But one of the standard methods of loading a kernel image is
to copy it bit by bit into the 640K area, and then out again to its
final destination, either all at once or bit by bit.
: to do with how much ram you have installed. Unless u are running an
: embedded system you should be able to include most things in the kernel
: instead of using modules however if the kernel is too big then instead
: of using 'make zImage' use 'make bzImage'
No no no. This does not change the size of the kernel. It changes the
method used to load it, so that it can support a larger image.
: [EMAIL PROTECTED] wrote:
:> I will soon be using a 486 computer
:> to run Linux and it only has 16 megs of
:> RAM. I can try to find a RAM upgrade
This is fine. You will be happier with 32MB nowadays though it's fine
for a slightly older distro, with X and all.
:> but can anyone tell me if the latest
:> kernel, if stripped down to exclude
:> SMP and useless drivers, will work
:> alright on such a system?
Nothing to do with the kernel. Your limits way above the minima that any
kernel needs. 4MB would be "fine" for the kernel. It's the rest of
the running system that you need to worry about!
Peter
------------------------------
From: [EMAIL PROTECTED] (Yves Bellefeuille)
Subject: Re: BIOS setup on an old 386
Date: Sun, 10 Sep 2000 20:08:33 -0400
Reply-To: Yves Bellefeuille <[EMAIL PROTECTED]>
On Mon, 11 Sep 2000, Tom Massey <[EMAIL PROTECTED]> wrote:
> Thanks for your reply. Do I have to use a 360k floppy for this? This
> would explain why I've been unable to get it to boot using 1.2M disks.
> I've got a couple of generic setup programs that should work, but I just
> can't seem to make a boot disk that will boot the machine.
I'd try formatting a diskette to 360 kb capacity. Try FORMAT /F:360, and
see also the DRIVPARM command.
--
Yves Bellefeuille <[EMAIL PROTECTED]>, Ottawa, Canada
Francais / English / Esperanto
Fight Spam! Join CAUCE cost-free: http://www.cauce.org/
------------------------------
** 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.hardware) 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-Hardware Digest
******************************
