Linux-Hardware Digest #241, Volume #9 Fri, 22 Jan 99 01:13:32 EST
Contents:
Re: K6-400 "kernel paging request" errors ("David R. Bergstein")
Re: K6-400 "kernel paging request" errors ("David R. Bergstein")
Re: 3Com 3c509b, not working under RH 5.2 (Dan Kegel)
Re: Winmodem or no?? (Johan Kullstam)
Re: S3 Trio64V+ PCI supported in XFree86? (jedi)
Re: Linux keyboard? (For emacs use) (Jim Richardson)
Re: Linux keyboard? (For emacs use) (Ilya)
Re: CPU Monitor App (Darren Greer)
Re: Modem compatability (Dan Nguyen)
Re: SB16 Problems (Neil Zanella)
Re: New RedHat with linux version 3.3.3. coming soon? ([EMAIL PROTECTED])
Re: fdisk partitioning > 8GB drive (Bryan McKinley)
----------------------------------------------------------------------------
From: "David R. Bergstein" <[EMAIL PROTECTED]>
Crossposted-To: linux.dev.kernel,comp.os.linux.development.system,comp.os.linux.misc
Subject: Re: K6-400 "kernel paging request" errors
Date: Thu, 21 Jan 1999 21:52:38 -0500
Larry wrote:
>
> On Wed, 20 Jan 1999 08:13:13 -0500, David R. Bergstein <[EMAIL PROTECTED]>
> wrote:
> >If it helps at all, I am also seeing similar paging request errors under
> >linux 2.0.36 with an AMD K6-200 and 128MB RAM. I will need to change
> >my syslog.conf to obtain a dump next time it happens (will post).
> >
> I was getting this type of error with a cyrix p166 and finally took the
> processor fan off and cleaned it and the fins and put it back together and
> VOILA, it's been working famously ever since.
That is very interesting - I did use a high quality heat sink grease
when I installed the heat sink / CPU fan unit, but that was over a year
& 1/2 ago. I may try what you suggest.
Thanks,
- David
--
David R. Bergstein
Systems Engineer and Blues Musician
Rockville, MD
===========================================================================
[EMAIL PROTECTED] [EMAIL PROTECTED]
SE & Blues Musician Home Page Heart of Blue - Playin' the Blues for
You!
http://www.erols.com/dbergst http://heartofblue.com
===========================================================================
------------------------------
From: "David R. Bergstein" <[EMAIL PROTECTED]>
Crossposted-To: linux.dev.kernel,comp.os.linux.development.system,comp.os.linux.misc
Subject: Re: K6-400 "kernel paging request" errors
Date: Thu, 21 Jan 1999 21:55:57 -0500
"David R. Bergstein" wrote:
>
> Larry wrote:
> >
> > On Wed, 20 Jan 1999 08:13:13 -0500, David R. Bergstein <[EMAIL PROTECTED]>
> > wrote:
> > >If it helps at all, I am also seeing similar paging request errors under
> > >linux 2.0.36 with an AMD K6-200 and 128MB RAM. I will need to change
> > >my syslog.conf to obtain a dump next time it happens (will post).
> > >
> > I was getting this type of error with a cyrix p166 and finally took the
> > processor fan off and cleaned it and the fins and put it back together and
> > VOILA, it's been working famously ever since.
>
> That is very interesting - I did use a high quality heat sink grease
> when I installed the heat sink / CPU fan unit, but that was over a year
> & 1/2 ago. I may try what you suggest.
>
> Thanks,
>
> - David
BTW, my crash happened earlier today as expected. Here is a dump from my
syslog:
Jan 21 16:25:36 bluesman kernel: general protection: 0000
Jan 21 16:25:36 bluesman kernel: CPU: 0
Jan 21 16:25:36 bluesman kernel: EIP: 0010:[do_no_page+463/808]
Jan 21 16:25:36 bluesman kernel: EFLAGS: 00010246
Jan 21 16:25:36 bluesman kernel: eax: 00000000 ebx: 04f3b080 ecx:
00000400
edx: f2481000
Jan 21 16:25:36 bluesman kernel: esi: 04f3a2b0 edi: f2481000 ebp:
0205c458
esp: 00798f58
Jan 21 16:25:36 bluesman kernel: ds: 0018 es: 0018 fs: 002b gs:
002b ss:
0018
Jan 21 16:25:36 bluesman kernel: Process sendmail (pid: 1801, process
nr: 32, st
ackpage=00798000)
Jan 21 16:25:36 bluesman kernel: Stack: 0011b6e4 080ac39c 01693398
038c1c0c 0000
2f47 00105025 000c0000 00000000
Jan 21 16:25:36 bluesman kernel: 00105025 00105025 0011212c
038c1c0c 0205
c458 080ac000 00000001 00112010
Jan 21 16:25:36 bluesman kernel: 080ab388 400a3264 080ac390
0012afc3 0169
3398 bfffe614 0010ae40 00798fbc
Jan 21 16:25:36 bluesman kernel: Call Trace: [do_no_page+0/808]
[do_page_fault+2
84/736] [do_page_fault+0/736] [sys_newfstat+79/92] [error_code+64/80]
Jan 21 16:25:36 bluesman kernel: Code: f3 ab 0b 55 0c 89 54 24 18 89 54
24 1c 8b
44 24 18 0c 40 89
Jan 21 16:25:36 bluesman kernel: wait_queue is bad (eip = 0013e4d8)
Jan 21 16:25:36 bluesman kernel: q = 0092c04c
Jan 21 16:25:36 bluesman kernel: *q = 04f5e048
Jan 21 16:25:36 bluesman kernel: wait_queue is bad (eip = 0013e4d8)
Jan 21 16:25:36 bluesman kernel: q = 0092c04c
Jan 21 16:25:36 bluesman kernel: *q = 04f5e048
Jan 21 16:25:36 bluesman kernel: wait_queue is bad (eip = 0013e4d8)
Jan 21 16:25:36 bluesman kernel: q = 0092c04c
Jan 21 16:25:36 bluesman kernel: *q = 04f5e048
Jan 21 16:25:36 bluesman kernel: wait_queue is bad (eip = 0013e4d8)
Jan 21 16:25:36 bluesman kernel: q = 0092c04c
Jan 21 16:25:36 bluesman kernel: *q = 04f5e048
Jan 21 16:25:36 bluesman kernel: wait_queue is bad (eip = 0013e4d8)
Jan 21 16:25:36 bluesman kernel: q = 0092c04c
Jan 21 16:25:36 bluesman kernel: *q = 04f5e048
Jan 21 16:25:36 bluesman kernel: wait_queue is bad (eip = 0013e4d8)
[ numerous repeated entries snipped ]
Jan 21 16:25:36 bluesman kernel: q = 0090064c
Jan 21 16:25:36 bluesman kernel: *q = 04f5e054
Jan 21 16:25:36 bluesman kernel: wait_queue is bad (eip = 0013e4d8)
Jan 21 16:25:36 bluesman kernel: q = 0090064c
Jan 21 16:25:36 bluesman kernel: *q = 04f5e054
Jan 21 16:25:36 bluesman kernel: wait_queue is bad (eip = 0013e4d8)
Jan 21 16:25:36 bluesman kernel: q = 0090064c
Jan 21 16:25:36 bluesman kernel: *q = 04f5e054
Jan 21 16:25:36 bluesman kernel: wait_queue is bad (eip = 0013e4d8)
Jan 21 16:25:36 bluesman kernel: q = 0090064c
Jan 21 16:25:36 bluesman kernel: *q = 04f5e054
Jan 21 16:25:36 bluesman kernel: wait_queue is bad (eip = 0013e4d8)
Jan 21 16:25:36 bluesman kernel: q = 0090064c
Jan 21 16:25:36 bluesman kernel: *q = 04f5e054
Jan 21 16:25:36 bluesman kernel: general protection: 0000
Jan 21 16:25:36 bluesman kernel: CPU: 0
Jan 21 16:25:36 bluesman kernel: EIP:
0010:[wake_up_interruptible+53/232]
Jan 21 16:25:36 bluesman kernel: EFLAGS: 00010282
Jan 21 16:25:36 bluesman kernel: eax: 62614c73 ebx: c7e0c7e0 ecx:
0090064c
edx: c7e0c7e0
Jan 21 16:25:36 bluesman kernel: esi: 04f5e818 edi: 00900648 ebp:
02ae3ec4
esp: 02ae3eb8
Jan 21 16:25:36 bluesman kernel: ds: 0018 es: 0018 fs: 002b gs:
002b ss:
0018
Jan 21 16:25:36 bluesman kernel: Process xlock (pid: 1420, process nr:
35, stack
page=02ae3000)
Jan 21 16:25:36 bluesman kernel: Stack: 040cfc0c 04f5e818 00000800
02ae3f28 0013
e4d8 0090064c 040cfc0c 0013f506
Jan 21 16:25:36 bluesman kernel: 040cfc0c 00000800 00000800
00767a00 0076
7a90 00000020 00000046 00000000
Jan 21 16:25:36 bluesman kernel: 00000000 00000000 0229b810
fffffff5 0229
b8d0 081241cc 00000000 00000000
Jan 21 16:25:36 bluesman kernel: Call Trace: [def_callback2+24/44]
[unix_sendmsg
+954/988] [sock_write+158/180] [sys_write+339/396] [ide_intr+77/100]
[do_fast_IR
Q+42/76] [system_call+85/128]
Jan 21 16:25:36 bluesman kernel: Code: 8b 02 83 f8 01 75 67 9c 5e fa c7
02 00 00
00 00 83 7a 4c 00
Jan 21 16:25:37 bluesman kernel: wait_queue is bad (eip = 0013e4d8)
Jan 21 16:25:37 bluesman kernel: q = 0206194c
Jan 21 16:25:37 bluesman kernel: *q = 04f5e03c
Jan 21 16:25:37 bluesman kernel: wait_queue is bad (eip = 0013e4d8)
Jan 21 16:25:37 bluesman kernel: q = 0206194c
Jan 21 16:25:37 bluesman kernel: *q = 04f5e03c
Jan 21 16:25:38 bluesman kernel: wait_queue is bad (eip = 0013e4d8)
Jan 21 16:25:38 bluesman kernel: q = 0206194c
Jan 21 16:25:38 bluesman kernel: *q = 04f5e03c
Jan 21 16:25:38 bluesman kernel: wait_queue is bad (eip = 0013e4d8)
Jan 21 16:25:38 bluesman kernel: q = 0206194c
Jan 21 16:25:38 bluesman kernel: *q = 04f5e03c
Jan 21 16:25:39 bluesman kernel: wait_queue is bad (eip = 0013e4d8)
Jan 21 16:25:39 bluesman kernel: q = 0206194c
Jan 21 16:25:39 bluesman kernel: *q = 04f5e03c
Jan 21 16:25:39 bluesman kernel: wait_queue is bad (eip = 0013e4d8)
Jan 21 16:25:39 bluesman kernel: q = 0206194c
Jan 21 16:25:39 bluesman kernel: *q = 04f5e03c
Jan 21 16:25:40 bluesman kernel: wait_queue is bad (eip = 0013e4d8)
Jan 21 16:25:40 bluesman kernel: q = 0206194c
Jan 21 16:25:40 bluesman kernel: *q = 04f5e03c
Jan 21 16:25:40 bluesman kernel: wait_queue is bad (eip = 0013e4d8)
Jan 21 16:25:40 bluesman kernel: q = 0206194c
Jan 21 16:25:40 bluesman kernel: *q = 04f5e03c
Jan 21 16:25:41 bluesman kernel: wait_queue is bad (eip = 0013e4d8)
[ snip, many repeated entries again! ]
Jan 21 16:26:32 bluesman kernel: q = 0206194c
Jan 21 16:26:32 bluesman kernel: *q = 04f5e03c
Jan 21 18:05:35 bluesman kernel: Unable to handle kernel paging request
at virtu
al address e4448bfa
Jan 21 18:05:35 bluesman kernel: current->tss.cr3 = 03218000, ^Lr3 =
03218000
Jan 21 18:05:35 bluesman kernel: *pde = 00000000
Jan 21 18:05:35 bluesman kernel: Oops: 0000
Jan 21 18:05:35 bluesman kernel: CPU: 0
Jan 21 18:05:35 bluesman kernel: EIP: 0010:[__iget+60/544]
Jan 21 18:05:35 bluesman kernel: EFLAGS: 00010206
Jan 21 18:05:35 bluesman kernel: eax: 00000342 ebx: 24448bfa ecx:
031d9d18
edx: 00000000
Jan 21 18:05:35 bluesman kernel: esi: 002184f8 edi: 00000000 ebp:
0022ccdc
esp: 0321aed0
Jan 21 18:05:35 bluesman kernel: ds: 0018 es: 0018 fs: 002b gs:
002b ss:
0018
Jan 21 18:05:35 bluesman kernel: Process xntpd (pid: 171, process nr:
16, stackp
age=0321a000)
Jan 21 18:05:35 bluesman kernel: Stack: 00000000 004c4800 00000000
03426500 0016
3a60 00163a7d 0022ccdc 00002f43
Jan 21 18:05:35 bluesman kernel: 00000000 03426500 00000000
00000009 02c4
8005 0012caa2 031d9b18 031d9d18
Jan 21 18:05:35 bluesman kernel: ffffffff 01c2d11c 01c3f238
00163eeb 0342
6500 07dcc005 0000000e 03426500
Jan 21 18:05:35 bluesman kernel: Call Trace: [do_ext2_rename+380/1456]
[do_ext2_
rename+409/1456] [lookup+222/248] [ext2_rename+87/128]
[do_rename+560/604] [sys_
rename+93/132] [system_call+85/128]
Jan 21 18:05:35 bluesman kernel: Code: 66 39 03 75 0d 8b 4c 24 1c 39 4b
04 0f 84
fa 00 00 00 8b 5b
Jan 21 21:11:04 bluesman kernel: general protection: 0000
Jan 21 21:11:04 bluesman kernel: CPU: 0
Jan 21 21:11:04 bluesman kernel: EIP:
0010:[wake_up_interruptible+53/232]
Jan 21 21:11:04 bluesman kernel: EFLAGS: 00010282
Jan 21 21:11:04 bluesman kernel: eax: 435f5f65 ebx: c7e0c7e0 ecx:
04e88934
edx: c7e0c7e0
Jan 21 21:11:04 bluesman kernel: esi: 04e8831e edi: 04e88930 ebp:
001fec84
esp: 001fec78
Jan 21 21:11:04 bluesman kernel: ds: 0018 es: 0018 fs: 002b gs:
0018 ss:
0018
Jan 21 21:11:04 bluesman kernel: Process swapper (pid: 0, process nr: 0,
stackpa
ge=001fcdf4)
Jan 21 21:11:04 bluesman kernel: Stack: 04e88000 04e8831e 04372003
04372003 0019
405b 04e88934 04e8831c 04e8851c
Jan 21 21:11:04 bluesman kernel: 00000005 001fed2c 00000297
00000ffd 0000
0003 00000fff 001fed2c 0017c336
Jan 21 21:11:04 bluesman kernel: 00000046 00000000 f8fe9400
0040f398 0019
c95a 002233ac 00000001 00000006
--
David R. Bergstein
Systems Engineer and Blues Musician
Rockville, MD
===========================================================================
[EMAIL PROTECTED] [EMAIL PROTECTED]
SE & Blues Musician Home Page Heart of Blue - Playin' the Blues for
You!
http://www.erols.com/dbergst http://heartofblue.com
===========================================================================
------------------------------
From: Dan Kegel <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.networking
Subject: Re: 3Com 3c509b, not working under RH 5.2
Date: Wed, 20 Jan 1999 20:06:20 -0800
Melvin Mathew Meadlin II schrieb:
> I have a 3com 3c509b ethernet card which works fine under Windows 95,
> but I can't get it to work under Red Hat 5.2. Does anyone have any
> suggestions????
Is that ISA or PCI? I have a PCI 3c509b, and it works fine with
Red Hat 5.2.
- Dan
--
Speaking only for myself, not for my employer
------------------------------
Crossposted-To: comp.os.linux,comp.os.linux.advocacy,comp.os.linux.setup,comp.modems
Subject: Re: Winmodem or no??
From: Johan Kullstam <[EMAIL PROTECTED]>
Date: 21 Jan 1999 22:40:49 -0500
Rick Brice <[EMAIL PROTECTED]> writes:
> Have you ever ran a bit error rate or measured throughput on both
> boxes to see
> what you are really getting?
now i *know* you are lost. the bit error rate and throughput is
totally dominated by your phone line and the modems on each end. what
rs-232 port if it it's on a PC clone or an amiga is simply not going
to affect anything.
> Chris Lee wrote:
>
> > In article <[EMAIL PROTECTED]>,
> > [EMAIL PROTECTED] says...
> > >
> > >Interesting Idea
> > >but basically there is nothing standard about the external modem except
> > >that the RS232? interface is a specification, not a standard, that you
> > >generally cannot depend upon for consistency from one manufacturer, much
> > >less from different manufacturers.
> > >The wiring may be different from series to series or manufacturer to
> > >manufacturer.....
> > >from one generation of software to the next you cannot even depend on the
> > >same implementations of a/an/(the?) AT command set.
> > >When you add in an external interface RS232 ports on whatever manufacturers
> > >computer, using whatever manufacturer's UART's, or Modem emulator's, or
> > >however they see fit to implement the interface to the external box......ad
> > >infinitum........
> >
> > Funny. My V.90 56k external modem works just fine when I unplug it from my
> > pc and connect it to the RS-232 port on my Amiga 3000 that I bought around
> > '93 or so.
> >
> > I think you don't know what the hell you are talking about myself....
>
> --
> --------------
> Earth is a small target suspended in space......
> r dot w dot brice at lmco dot com
>
>
--
Johan Kullstam [[EMAIL PROTECTED]] Don't Fear the Penguin!
------------------------------
From: [EMAIL PROTECTED] (jedi)
Subject: Re: S3 Trio64V+ PCI supported in XFree86?
Date: Thu, 21 Jan 1999 19:30:05 -0800
On Fri, 22 Jan 1999 03:03:21 GMT, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>I know I can use a S3 Trio64V+ in XFree86 but I didn't see S3 Trio64V+
>PCI on the list of cards supported in XFree86. Are they the same thing?
>If anyone knows or knows where I can look, I'd appreciate it.
Just get a cheap copy of Redhat 5.2 and give it a whirl.
As far as I know, it should get autodetected just fine.
I use an S3 Virge myself (generic).
I doubt if the PCI will make a difference except to make
things easier.
--
Herding Humans ~ Herding Cats
Neither will do a thing unless they really want to, or |||
is coerced to the point where it will scratch your eyes out / | \
as soon as your grip slips.
In search of sane PPP docs? Try http://penguin.lvcm.com
------------------------------
From: [EMAIL PROTECTED] (Jim Richardson)
Crossposted-To:
comp.os.linux.misc,comp.unix.questions,comp.unix.misc,comp.emacs,comp.editors
Subject: Re: Linux keyboard? (For emacs use)
Date: 21 Jan 1999 02:57:11 GMT
Reply-To: [EMAIL PROTECTED]
On Wed, 20 Jan 1999 01:55:06 GMT,
Festus van Landingham, in the persona of <[EMAIL PROTECTED]>,
brought forth the following words...:
>
>Johan Kullstam wrote:
>
>>it's hard to find a keyboard with the keys labelled as such theses
>>days. on the other hand, it is very easy to remap the keys. in X use
>>xmodmap to swap caps lock and control. in console mode, there is a
>>keyboard map file (in /usr/lib/kbd/ somewhere i believe. hack the
>>`us' keymap to swap caps lock and control).
>>
>>i too use emacs. i even remapped the keys on windows nt since i use
>>emacs at work too.
>
>Do emacs users not type captial letters or does emacs not support
>capital letters?
>
>--
how often do you need more that one or two caps in a row?
(also, you can remap keys on the fly in emacs if you need to.)
--
Jim Richardson
Anarchist, pagan and proud of it
WWW.eskimo.com/~warlock
Linux, because life's too short for a buggy OS.
------------------------------
From: Ilya <[EMAIL PROTECTED]>
Subject: Re: Linux keyboard? (For emacs use)
Crossposted-To:
comp.os.linux.misc,comp.unix.questions,comp.unix.misc,comp.emacs,comp.editors
Date: 21 Jan 1999 20:14:57 +0800
In comp.editors Erik Naggum <[EMAIL PROTECTED]> wrote:
> * Sven Utcke <[EMAIL PROTECTED]>
> | So I noticed. Strangely enough you still employ capital letters for
> | the words "I" and "Emacs". Or rather Emacs does, I guess :-)
> case is an important property of a word. randomly capitalizing words
> just because they happen to start sentences destroys valuable information
> about that word. I therefore maintain the case properties of a word
> regardless of its position in the sentence.
I can respect that.
------------------------------
From: [EMAIL PROTECTED] (Darren Greer)
Crossposted-To: comp.os.linux.development.apps,comp.os.linux.misc
Subject: Re: CPU Monitor App
Date: Thu, 21 Jan 1999 03:16:54 GMT
Here is some info I pulled from some mailing list.....
==================================
As result I'm always running a dockable temperature sensor applet in
Linux
which displays both LED's and an EKG type temp display, with
alarms.... very
nice!
Try:
http://www.netroedge.com/~lm78/
for the actual "module" that is loaded, and then
http://www.netroedge.com/intranet/tellerstats/
for information about web routines to display the temp information and
graphs...
and finally
http://users.ox.ac.uk/~kebl0850/wmlm78/
for a WIndowmaker / Afterstep dockable applet which reads the results
from
the module...
"Cool!"
====================================
Id be interested to hear your thoughts on these.....
DrGreer
------------------------------
From: Dan Nguyen <[EMAIL PROTECTED]>
Subject: Re: Modem compatability
Date: 22 Jan 1999 03:58:15 GMT
Carson Saunders <[EMAIL PROTECTED]> wrote:
: I have a US Robotics internal 56K modem with X2. It came with my Dell
: system about a year and a half ago. Does anyone know if there are any
: compatability issues with Red Hat 5.2?
It may or may not work. Dell sells both 3COM/USR modems and
winmodems. If it is a winmodem it will not work! If it is a modem.
Setserial can help configure it, if it is PnP (Plug and Pray), use isapnp.
--
Dan Nguyen | There is only one happiness in
[EMAIL PROTECTED] | life, to love and be loved.
http://www.cse.msu.edu/~nguyend7 | -George Sand
------------------------------
From: Neil Zanella <[EMAIL PROTECTED]>
Subject: Re: SB16 Problems
Date: Fri, 22 Jan 1999 00:36:49 -0330
Hello,
Is this the "WavEffects" ISA card?
Why don't you try a development kernel?
They're supposed to have better support for PnP than just using the
buggy "isapnptools" which can be faulty.
Another thing you can do is open the box and see what IRQ the card
is set for by looking at the jumper settings.
I am also trying to get this card to work without much success,
What chipset does you card use and which kernel options did you use
to compile the kernel?
Write back and let me know,
Neil
On Sun, 17 Jan 1999, Helgonet wrote:
> Hi !
>
> I've been trying for hours, but I just can't get my sb 16 pnp card to
> work..
> I've compiled the kernel thousands of times and tried to pnpdump to
> isapnp.conf
> and then commentet out what I thought was right..
> (checked in win 95 what irq and dma's etc I had....)
> I have compiled my soundcard as modules, so it should work, but it
> don't..
> can't read /dev/sndstat with cat nor acces /dev/dsp (with mpg123)....
> I run slack 3.6.....
> Have been reading the sound howto, but it doesn't help..
> and can't find the sb 16 mini howto...
> plz help me B4 I go crazy!
>
> Danne
>
>
>
>
>
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: New RedHat with linux version 3.3.3. coming soon?
Date: 22 Jan 1999 05:30:10 GMT
Phil Jones <[EMAIL PROTECTED]> wrote:
> I understand RedHat 5.2 is the latest RedHat for
> sale and contains version 3.3.2 of linux. Anyone
> know when RedHat will put out a package with the
> linux 3.3.3? Thanks.
Um.... I think you may be a bit confused (or maybe I am)...
Stock Redhat 5.2 installs the 2.0.36 kernel. I just saw a messages
elsewhere that the major kernel release (2.2.0) is just about ready.
the only software I'm aware of in RH5.2 associated with a version number
of 3.3.2 is XFree86. the 3.3.3.1 RPMs for XFree86 are available from
the errata pages of the redhat site.
Other distributions (Slackware, Caldera, Debian etc) all have different
version numbering systems for their distributions, but as far as I'm
aware, if you're talking about the "version" of linux itself, you should
be referring to the kernel version number.
In any event, I'm sure that an occasional visit to www.redhat.com will
reveal a set of RPMs for the new kernel when they've got them ready.
If I've misunderstood your question or botched the answer, I'd appreciate
a correction.
Simeon
------------------------------
From: Bryan McKinley <[EMAIL PROTECTED]>
Subject: Re: fdisk partitioning > 8GB drive
Date: Thu, 21 Jan 1999 04:44:28 GMT
Jose,
Ok, under RedHat lilo I tried:
boot: hda=10022,8,[200,256,330] <--From drive specs 200-330 s/t
The square brackets indicate 3 values I have tried with fdisk without
committing
the partition changes. Question is, since the sectors/track varies from
200-300,
what should I use? 200 produced no warnings but 256 and 330 produced
cylinder ending warnings. (Your e-mail is bounced by the way).
Thank you for your help here,
Bryan
Jose Urena wrote:
> I am assumming that you want to add
> append="linear" to the /etc/lilo.conf
>
> I know for a fact that you mean
> append="hda=C#,H#,S#"
>
> get the C,H,S values from you HD manual or from the BIOS without LBA
> translation
>
> BTW, when using this, lilo will not boot if your boot partition is
> beyond cylinder 1024
>
> Bryan McKinley wrote:
>
>> win98 is loaded and supports my very large disk (~11GB); my bios has
>> LBA
>> support. I have
>> been reading the docs & howtos and they indicate that I should pass
>> 'linear' to the kernel on boot to make
>> it use logical sector-like addressing rather than CHS. I don't see
>> this
>> listed among options
>> available to pass to the kernel at boot time. Am I barking up the
>> wrong
>> tree? The docs
>> indicate that fdisk can handle disks this large so long as the
>> kernel
>> supports the linear
>> disk addressing mode. How do I set options at LILO-time to make
>> this
>> happen?
>> Is this already happening unbeknownst to me? Kernel logs CHS-style
>> disk
>> info on boot, not
>> linear info--at a cursory glance. I've done my homework, which has
>> included trying a couple
>> of beta tools that did not work. I need a clue here.
>>
>> Anyone?
>>
>> Bryan McKinley
>
------------------------------
** 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
******************************
