Re: Version(s) working with BlizzardPPC

[Andreas <aw...@sw...>]

Hi Kulwant

On Tue, 2003-12-16 at 00:30, Kulwant Bhogal wrote:

> Hello Andi, 
> 
> > Just Ctrl-Alt-F2 and there should be a shell IIRC.
> 
> I will try this. Although I think my biggest problem whilst configuring the
> base system was knowing what I wanted and what I didn't!! Not sure how to
> figure that out yet. In theory I would like to leave as much installed as
> possible and know what to install to get some sort of gui and maybe some
> apps like a browser etc installed - but I may be trying to run before I can
> crawl here......

You maybe want to leave out tasksel and dselect completely, since I
don't like them (and you may not like them too). I usually just skip
them and install a usable system myself using apt-get install, since
this lets you choose the packages you really want, and you don't get
lots of (not needed) stuff installed like when using tasksel. The
downside, of course, is that you have to know which packages you have to
install to get a running system.. ;) If you'd like, I could send a
comprehensive list of packages to install if you want to have things
like xfree86 and gnome running.

> not forgetting that the clock problem isn't really resolved
> yet (I'm reminding myself).

Yeah, but this mainly seems to be the only obstacle right now.

> I remember getting some dependency conflicts and not being able to resolve
> them. Maybe I will post details here later after I have had another go.

D'oh. What did you try to install and from where? This shouldn't happen
on a stable release (i.e. woody ATM).

> > This is good news! Also that this clearly isolates the system crashes to
> > the hardware clock reads.
> 
> Yes, I am glad that the problem seems to have been totally isolated. Thanks
> in no small part to you - nobody had made those suggestions before and this
> is the furthest I have ever got with trying to get Linux running on my
> machine.

You're welcome. The renaming stuff was really a bit of last resort
thing, but it helped to isolate the problem.

> >> > But this is definitely not how a productive system should be run! So,
> >> > try to get the dmesg output anyway and post it.
> 
> I will put the clock stuff back to how it was originally and collect some
> debug output to post here. Watch this space.

Cool! Please do so!! Or at least try to look up the symbols in the
System.map as Geert mentioned in another mail (I think there's a
System.map delivered with the kernel lha for the amigaOS side).

> > Because you didn't tell it to save the stuff in the memory. Well, I
> > guess it was me who forgot to mention it in the last mail anyway..
> 
> Don't worry, better late than never. And if my brain had retained any of the
> stuff I had been reading, I would have noticed that myself.

Ok, so I'm relieved! :)

> >> The other question is, is there a way
> >> of resetting the Linux side which cleanly unmounts my hda2 partition?
> 
> > After the crash? I don't think so. Except if you can get a debug monitor
> > running maybe, but this is over my head ATM.
> 
> No, I meant before a crash. For example when running the installation
> program, if I chose "reboot the system" then when starting Linux again it
> would run a check on hda2 everytime because it would complain that the
> partition had not been cleanly unmounted. I am sure I even "unmounted" hda2
> and still the revalidate ran afterwards - I will recheck that but I'm sure
> that's what happened.

Hmmm, this is not normal! What type of filesystem did you choose for the
linux partition(s)? I'd take ext3 anyway. I don't think this has
something to do with the clock problem (though it may) since I once
booted with the clock reset to 1978 (say hello to my clock battery..)
and it did only complain about some module/kernel date mismatch.

> Thank you for all your help so far - I really appreciate it.

As I said, you're welcome. Always nice if I can help!! :)

-- 
Best wishes,
Andi