Hullo,
I tried ext3 a while ago, and almost fried my system. Still, the power goes
out here often enough that I'd like a journaling filesystem. Does anyone
have some useful experience they could share concerning reiserfs, xfs, etc
on powerpc?
Thanks,
Peter
> > Normal behavior of a disk that was forced to spin down using hdparm -Y.
> > Pity it didn't remain powered down, there's probably some other processes
> > running that still cause disk I/O.
>
> Like [kupdate], bdflush or whatever?
>
> I've noticed that my disk is periodically accessed (about e
Michael Schmitz wrote:
> > Nov 8 13:46:34 yoko kernel: hde: ATAPI reset complete
>
> Normal behavior of a disk that was forced to spin down using hdparm -Y.
> Pity it didn't remain powered down, there's probably some other processes
> running that still cause disk I/O.
Like [kupdate], bdflush o
> I now that sleep is not supported on pismos but could someone explain me
> this errors
>
> yoko:~ > snooze
> zsh: alarm snooze
> yoko:~ >
Easy: it won't sleep. Period.
[...]
> Nov 8 13:46:34 yoko kernel: hde: ATAPI reset complete
Normal behavior of a disk that was forced to spin down u
> > Must be yet another reason for the invisible cursor: atyfb uses
> > the hardware cursor :-) Any idea why setting the cursor color sometimes
> > won't work? The cursor color gets set pretty early, maybe the chip needs
> > some more init, or it isn't idle at that stage?
>
> You're right. This is
On Wed, Nov 08, 2000 at 08:36:31AM -0500, Chris Bryan wrote:
> alright everyone, I've gotten a little farther. When I boot into yaboot, it
> says "boot: " and then "Loading kernel..." but then complains that it
> "can't find image". Wouldn't this be ramdisk.image.gz? Wouldn't this be
> ramdisk.imag
On Wed, 8 Nov 2000, Michael Schmitz wrote:
> > > Happens sometime, for reasons yet unknown. What seems to happen is
> > > that the cursor changes color to black. Feel free to look up where
> > > the cursor color gets set, and pepper the fbcon code with printk to find
> > > where it goes wrong.
> >
alright everyone, I've gotten a little farther. When I boot into yaboot, it
says "boot: " and then "Loading kernel..." but then complains that it
"can't find image". Wouldn't this be ramdisk.image.gz? Wouldn't this be
ramdisk.image.gz? I've tried loading it manually after that, but still no
luck P
On Wed, 8 Nov 2000, Hadess wrote:
> Hi,
>
> This question has already been asked, check the mailing-list archive, thread
> starts at:
> http://lists.debian.org/debian-powerpc-0010/msg00463.html
thank's
Eric
--
"La disparition de la carte perforée est un trou dont personne n
Hi,
This question has already been asked, check the mailing-list archive, thread
starts at:
http://lists.debian.org/debian-powerpc-0010/msg00463.html
Cheers
Quoting Eric Deveaud <[EMAIL PROTECTED]>:
>
> Hello,
>
> I just grab pmud from unstable archives, and installed it.
> I now that s
Hello,
I just grab pmud from unstable archives, and installed it.
I now that sleep is not supported on pismos but could someone explain me
this errors
yoko:~ > snooze
zsh: alarm snooze
yoko:~ >
what I notice
I heard the disk spinnig off, and stop
the screen remain a
> > Happens sometime, for reasons yet unknown. What seems to happen is
> > that the cursor changes color to black. Feel free to look up where
> > the cursor color gets set, and pepper the fbcon code with printk to find
> > where it goes wrong.
>
> However, the reason is known: the fbcon-* code dr
On Tue, 7 Nov 2000, Michael Schmitz wrote:
> > > yep, it's in Debian/unstable a while now.
>
> pmud_0.7-3.deb, in section admin.
>
> > tahnk's I will deb-get install pmud-0.7.apt ;-
>
> Nope, just do 'apt-get install pmud'. (assuming your sources.list points
> to unstable not stable).
>
13 matches
Mail list logo
