On Sat, Apr 12, 2003 at 12:33:17PM -0600, Jessica Blank wrote:
> On Sat, 12 Apr 2003, Benjamin Herrenschmidt wrote:
>
> >
> > > Eh? Why does the keyboard WORK with init=/bin/sh, but NOT WORK when
> > > booting as per usual? That makes zero sense...
> >
> > It does make senes. With init=/bin/sh, th
On Sun, 2003-04-13 at 01:28, Jessica Blank wrote:
[...]
> Point is, why is the box going to runlevel 0 or 6 in the first place?
> Those are the only runlevels on my box where it runs the RTC scripts... :/
IIRC, the sysvinit stuff _used_ to go through every runlevel on the way
to the runlevel you w
My box sees the drives now!!
Now, why can't I get RTC to work?
On Sat, 12 Apr 2003, Benjamin Herrenschmidt wrote:
> On Sat, 2003-04-12 at 19:59, Jessica Blank wrote:
> > Interesting notes:
> >
> > init=/bin/sh DOES get me to a shell! And everything works fine.
> >
> > HOWEVER: Booting WITHOUT in
Now, all of this begs the question... since my Mac started working again
after I disabled BOTH RTC settings... yet previously, I'd been using 2.4
kernels
(non-Ben-patched/virgin/stock/unaltered/Linus's-tree/whatever-you-call-it)
with the PPC RTC option on, and it booted fine...
...what did you do
Err. Ignore the bit about the dmesg. I gotta get my keyboard working first
;)
On Sat, 12 Apr 2003, Jessica Blank wrote:
> Wonkalicious. Now it boots just fine... when I disabled both RTC and
> PPC_RTC (or RTC_PPC or whatever it was), the thing boots just fine O_o
>
> However... after having disab
Wonkalicious. Now it boots just fine... when I disabled both RTC and
PPC_RTC (or RTC_PPC or whatever it was), the thing boots just fine O_o
However... after having disabled ADB_KEYBOARD, the keyboard does NOTHING!
Like, zilch, zero, zip, nada... I can't even log in. I can, of course,
ctrl-openappl
On Sat, Apr 12, 2003 at 12:46:46PM -0600, Jessica Blank wrote:
> Ahh. Color me stupid, but what is i2c again?
Here's a document about the standard that's pretty generic:
http://www.semiconductors.philips.com/buses/i2c/facts/
Summary: it's a simple, 2 line serial bus for connecting chips.
On Sat, 12 Apr 2003, Benjamin Herrenschmidt wrote:
>
> > I could find no CONFIG_ADB_KEYCODES. (I rgrep -r -i'd for it). I am
> > presuming you meant CONFIG_ADB_KEYBOARD, and proceeding along those
> > lines...
>
> Yup.
>
>
> > Was ist das "Cuda"?
>
> Cuda is the "system controller" chip of those o
> I could find no CONFIG_ADB_KEYCODES. (I rgrep -r -i'd for it). I am
> presuming you meant CONFIG_ADB_KEYBOARD, and proceeding along those
> lines...
Yup.
> Was ist das "Cuda"?
Cuda is the "system controller" chip of those old machines, it does,
among other, the real time clock, the poweroff/
On Sat, 12 Apr 2003, Benjamin Herrenschmidt wrote:
>
> > Eh? Why does the keyboard WORK with init=/bin/sh, but NOT WORK when
> > booting as per usual? That makes zero sense...
>
> It does make senes. With init=/bin/sh, the keyboard works with
> the kernel built-in keymap. Later on, your userland s
> Eh? Why does the keyboard WORK with init=/bin/sh, but NOT WORK when
> booting as per usual? That makes zero sense...
It does make senes. With init=/bin/sh, the keyboard works with
the kernel built-in keymap. Later on, your userland scripts are
loading a keymap, which is probably designed for th
On Sat, 12 Apr 2003, Benjamin Herrenschmidt wrote:
> On Sat, 2003-04-12 at 19:59, Jessica Blank wrote:
> > Interesting notes:
> >
> > init=/bin/sh DOES get me to a shell! And everything works fine.
> >
> > HOWEVER: Booting WITHOUT init=/bin/sh (even with the 601 bug thingy turned
> > on, which I r
On Sat, 2003-04-12 at 19:59, Jessica Blank wrote:
> Interesting notes:
>
> init=/bin/sh DOES get me to a shell! And everything works fine.
>
> HOWEVER: Booting WITHOUT init=/bin/sh (even with the 601 bug thingy turned
> on, which I really doubted would solve the problem anyhow), I get the same
>
Interesting notes:
init=/bin/sh DOES get me to a shell! And everything works fine.
HOWEVER: Booting WITHOUT init=/bin/sh (even with the 601 bug thingy turned
on, which I really doubted would solve the problem anyhow), I get the same
problem... oh, and for some reason the keyboard is also screwed
I was thinking of the init=/bin/sh idea. Will try.
On Sat, 12 Apr 2003, Benjamin Herrenschmidt wrote:
> On Sat, 2003-04-12 at 17:28, Jessica Blank wrote:
>
> > > Make sure you have CONFIG_PPC_RTC and _not_ CONFIG_RTC and let me
> > > know. If the kernel tries to access the legacy RTC chip on the
On Sat, 2003-04-12 at 17:28, Jessica Blank wrote:
> > Make sure you have CONFIG_PPC_RTC and _not_ CONFIG_RTC and let me
> > know. If the kernel tries to access the legacy RTC chip on the ISA
> > bus, it will hang.
>
> Yeah, that's how I did it.
>
> Actually, I was currently trying (just for grin
On Sat, 12 Apr 2003, Benjamin Herrenschmidt wrote:
> On Sat, 2003-04-12 at 17:14, Jessica Blank wrote:
> > Well... okay. This is interesting.
> >
> > Ben, your kernel patches simply don't like my machine. Maybe I'm doing
> > something wrong, but I've configured around a billion trillion bajillion
On Sat, 2003-04-12 at 17:14, Jessica Blank wrote:
> Well... okay. This is interesting.
>
> Ben, your kernel patches simply don't like my machine. Maybe I'm doing
> something wrong, but I've configured around a billion trillion bajillion
> kernels in my life (since age 15) and I see nothing missing
Well... okay. This is interesting.
Ben, your kernel patches simply don't like my machine. Maybe I'm doing
something wrong, but I've configured around a billion trillion bajillion
kernels in my life (since age 15) and I see nothing missing.
Plain old non-Ben-patched 2.4.20 kernels seem to boot fin
> Dear God, HFS is _STILL_ experimental!?
Yes. Until someone show up to really maintain it and fix some
of the most annoying bugs, it will stay that way.
> What ticks me off is the utter lack of attention paid to non-x86 platforms
> by Linus and crew. Shouldn't your superb patches be integrated
On Fri, 11 Apr 2003, Benjamin Herrenschmidt wrote:
> On Fri, 2003-04-11 at 17:54, Jessica Blank wrote:
> > On Fri, 11 Apr 2003, Benjamin Herrenschmidt wrote:
> >
> > > On Fri, 2003-04-11 at 17:48, Jessica Blank wrote:
> > >
> > > > These messages weren't FROM the boot. I already tried compiling th
On Fri, 2003-04-11 at 17:54, Jessica Blank wrote:
> On Fri, 11 Apr 2003, Benjamin Herrenschmidt wrote:
>
> > On Fri, 2003-04-11 at 17:48, Jessica Blank wrote:
> >
> > > These messages weren't FROM the boot. I already tried compiling the
> > > ide-disk and ide-mod modules into the kernel... they di
Ben: Found your patches, installing 'em, compiling IDE into the kernel
itself (i.e. not as a module). Will send dmesg if that dunna fix my
problem. Thanks!
On Fri, 11 Apr 2003, Benjamin Herrenschmidt wrote:
> On Fri, 2003-04-11 at 17:48, Jessica Blank wrote:
>
> > These messages weren't FROM the
On Fri, 11 Apr 2003, Benjamin Herrenschmidt wrote:
> On Fri, 2003-04-11 at 17:48, Jessica Blank wrote:
>
> > These messages weren't FROM the boot. I already tried compiling the
> > ide-disk and ide-mod modules into the kernel... they did not work. So,
> > getting sick and tired of rebooting the ma
On Fri, 2003-04-11 at 17:48, Jessica Blank wrote:
> These messages weren't FROM the boot. I already tried compiling the
> ide-disk and ide-mod modules into the kernel... they did not work. So,
> getting sick and tired of rebooting the machine around 50 times, I decided
> to compile them as modules
On Fri, 11 Apr 2003, Benjamin Herrenschmidt wrote:
> On Fri, 2003-04-11 at 16:24, Jessica Blank wrote:
> > I am having a big problem here.
> >
> > My nice little "CD burning server", under my bed, is crippled because the
> > large (40GB) IDE drive in it simply does not detect.
> >
> > This is a KN
On Fri, 2003-04-11 at 16:24, Jessica Blank wrote:
> I am having a big problem here.
>
> My nice little "CD burning server", under my bed, is crippled because the
> large (40GB) IDE drive in it simply does not detect.
>
> This is a KNOWN WORKING drive. I just pulled it out of a working system.
>
It was pulled out of a PeeCee Debian box. And to answer your question:
Yes. My "Partition Types" setup (for the record, I am using KERNEL VERSION
2.4.20...) looks like this:
x x [*] Advanced partition selection
x x [ ] Acorn partition support
x x [ ] Alpha OSF partition suppo
On Fre, 2003-04-11 at 16:24, Jessica Blank wrote:
>
> My nice little "CD burning server", under my bed, is crippled because the
> large (40GB) IDE drive in it simply does not detect.
>
> This is a KNOWN WORKING drive. I just pulled it out of a working system.
[...]
> Apr 11 10:19:28 gandalf ker
I am having a big problem here.
My nice little "CD burning server", under my bed, is crippled because the
large (40GB) IDE drive in it simply does not detect.
This is a KNOWN WORKING drive. I just pulled it out of a working system.
I've tried compiling IDE Disk Support and the Promise controller
30 matches
Mail list logo
