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 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 up. > > Instead of: > > The keyboard problem is a config problem as well. Either you enabled > ADB keycodes and are using linux keycodes, or the opposite. > > ADB keycodes is deprecated now. > > > Setting the System Clock using the Hardware Clock as reference... > > So the problem is really with the real time clock, or with the > Cuda driver. It works fine on the 8500 I have here (approximately > same hardware), though. Can you disable both CONFIG_RTC and > CONFIG_PPC_RTC ? That will prevent sync'ing the clock but should > allow it to boot. > > Also, is your kernel compile with CONFIG_SMP ? (I beleive it isn't > but still...) > > Ben. > > > (and there she hangs) > > > > 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 ISA > > > > > bus, it will hang. > > > > > > > > Yeah, that's how I did it. > > > > > > > > Actually, I was currently trying (just for grins and giggles) to compile > > > > it with BOTH. (ctrl-Cs that one.. thanks for the warning). > > > > > > > > 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... > > > > :/ > > > > > > I never really bothered about the init scripts, but it always > > > run that script for me as well when booting to level 2... > > > > > > > I am currently trying my umpteenth 2.4.20-ben10 kernel compile, this > > > > time > > > > with the workaround for 601 bugs (my box has a 601 processor) enabled. > > > > However, I doubt that will fix it, since I didn't need to enable it for > > > > plain old stock 2.4.20 to boot :/ > > > > > > > > Is there anything I can provide to you to help? > > > > > > Well, afaik, this kernel works on 7200... so it's difficult to say > > > remotely what's up. Tried booting with init=/bin/sh to see if you > > > get a prompt at all ? > > > > > > Ben. > > > > > > > > > -- > > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > > > > > > J e s s i c a L e a h B l a n k > -- > Benjamin Herrenschmidt <[EMAIL PROTECTED]> > J e s s i c a L e a h B l a n k
