Hi Dave,
On Fri, 2024-08-16 at 11:17 -0400, Dave Vasilevsky wrote:
> > Could you verify that this change actually fixes the problem? This would
> > save me some work.
>
> Verified with PPC qemu. I fail to boot with "You can’t boot a kdump kernel
> from OF" with
> CONFIG_CRASH_DUMP on, and I boo
> Could you verify that this change actually fixes the problem? This would
save me some work.
Verified with PPC qemu. I fail to boot with "You can’t boot a kdump kernel
from OF" with CONFIG_CRASH_DUMP on, and I boot fine with it disabled.
Details:
* Tested against the Debian 6.10.4-1 kernel as un
On Tue, 13 Aug 2024 at 14:30, Ed Robbins wrote:
>
> On Tue, 13 Aug 2024 at 12:32, Mike wrote:
> >
> > I am also interested in this grub migration guide. My trusty powerbook is
> > on yaboot, but if grub can't boot OSX or MorphOS I'll need to chain these
> &
On Tue, 13 Aug 2024 at 12:32, Mike wrote:
>
> I am also interested in this grub migration guide. My trusty powerbook is on
> yaboot, but if grub can't boot OSX or MorphOS I'll need to chain these as i
> bet yaboot boots grub just fine. Could you link to that script for boo
I am also interested in this grub migration guide. My trusty powerbook is
on yaboot, but if grub can't boot OSX or MorphOS I'll need to chain these
as i bet yaboot boots grub just fine. Could you link to that script for
booting osx under grub? I'll be taking a deep dive into g
Thank you Adrian.
It looks as though this also affects boot in grub as it's a kernel assertion?
It seems also that the culprit kernel config option was found in the
thread you linked to. Is some further investigation required to
discover why that config option causes an issue?
Aside:
I trawled t
Hi,
On Mon, 2024-08-12 at 21:09 +0100, Ed Robbins wrote:
> ERROR: claim of 0x170 in range 0xc200 0x1000 failed
> Claim error, can't allocate kernel memory
This is a known issue (see [1]), but I have not had time yet to work on it.
Adrian
> [1] https://lists.debian.org/debian-powerpc
Hello!
I updated my system a few weeks ago for the first time in a while, and
I am unable to boot the last two kernels at all. Those are
6.10.3-powerpc and 6.9.10-powerpc. I get an error from yaboot:
ERROR: claim of 0x170 in range 0xc200 0x1000 failed
Claim error, can't allocate kernel
, 2024, at 5:09 PM, Reimar Döffinger
>>>> wrote:
>>>>
>>>> Hi!
>>>> The newest 6.9 powerpc kernel build seems to be incompatible with
>>>> OpenFirmware boot,
>>>> so boot fails on my PowerPC macMini.
>>&g
> On 6 Jul 2024, at 18:18, John Paul Adrian Glaubitz
> wrote:
>
> Hi Reimar,
>
>> On Jul 6, 2024, at 5:45 PM, Reimar Döffinger
>> wrote:
>>
>>> Could you verify that this change actually fixes the problem? This would
>>> save me some work.
>>
>> I checked the kernel source, the error me
> On Jul 7, 2024, at 6:10 PM, Reimar Döffinger wrote:
>
>
>
>> On 6 Jul 2024, at 18:18, John Paul Adrian Glaubitz
>> wrote:
>>
>> Hi Reimar,
>>
On Jul 6, 2024, at 5:45 PM, Reimar Döffinger
wrote:
>>>
Could you verify that this change actually fixes the problem? This wo
Hi Reimar,
> On Jul 6, 2024, at 5:45 PM, Reimar Döffinger wrote:
>
>> Could you verify that this change actually fixes the problem? This would
>> save me some work.
>
> I checked the kernel source, the error message is under a if (PHYSICAL_START
> > 0), so that I am quite certain is the issue
Hi!
>>> The newest 6.9 powerpc kernel build seems to be incompatible with
>>> OpenFirmware boot,
>>> so boot fails on my PowerPC macMini.
>>> The error message is
>>> "Error: You can't boot a kdump kernel from OF!"
>>> T
oot,
>> so boot fails on my PowerPC macMini.
>> The error message is
>> "Error: You can't boot a kdump kernel from OF!"
>> The error message seems not entirely accurate, it seems the issue is that
>> CONFIG_PHYSICAL_START
>> is no longer 0, which p
Hi Reimar,
> On Jul 6, 2024, at 5:09 PM, Reimar Döffinger wrote:
>
> Hi!
> The newest 6.9 powerpc kernel build seems to be incompatible with
> OpenFirmware boot,
> so boot fails on my PowerPC macMini.
> The error message is
> "Error: You can't boot a kdump ke
Hi!
The newest 6.9 powerpc kernel build seems to be incompatible with OpenFirmware
boot,
so boot fails on my PowerPC macMini.
The error message is
"Error: You can't boot a kdump kernel from OF!"
The error message seems not entirely accurate, it seems the issue is that
CONFIG_PHYSI
Yes it works !
I tried the latest version (2020-05-30) with this command line :
qemu-system-ppc -monitor stdio -M mac99 -k en -machine accel=tcg -m 512
-cdrom /home/david/Bureau/debian-10.0.0-powerpc-NETINST-1.iso -hda
/home/david/Documents/Informatique\ et\ téléphone/Documentation\
informatique/
On Sun, Jul 19, 2020 at 2:21 PM Mark Cave-Ayland <
mark.cave-ayl...@ilande.co.uk> wrote:
> On 19/07/2020 10:37, David VANTYGHEM wrote:
>
> >> I did a comparison with a couple of DT dumps I have around and I see
> some Old World
> >> Macs reserve up until 0x4000 and some New World Macs reserve up t
On 19/07/2020 10:37, David VANTYGHEM wrote:
>> I did a comparison with a couple of DT dumps I have around and I see some
>> Old World
>> Macs reserve up until 0x4000 and some New World Macs reserve up to 0x3000 in
>> low
>> memory, so I don't think this change should break anything. I should add
> I did a comparison with a couple of DT dumps I have around and I see some Old
> World
> Macs reserve up until 0x4000 and some New World Macs reserve up to 0x3000 in
> low
> memory, so I don't think this change should break anything. I should add from
> looking
> at the MMU translations I thi
On 18/07/2020 17:10, Mark Cave-Ayland wrote:
> Thanks for the report and the forum reference above - I can confirm that I can
> reproduce the error here.
>
> Digging around for a couple of hours shows that we appear to generating an
> unexpected
> memory fault when reading the kernel from the di
On 17/07/2020 17:35, David VANTYGHEM wrote:
> Hello,
>
> All debian-10.0-powerpc-NETINST-1.iso in
> https://cdimage.debian.org/cdimage/ports/
> boot with qemu and GRUB, until 2019-07-16 version.
> They don't boot with 2019-11-17 version and newer versions.
>
> GRUB menu appears, I choose "Defau
Hello,
All debian-10.0-powerpc-NETINST-1.iso in
https://cdimage.debian.org/cdimage/ports/ boot with qemu and GRUB, until
2019-07-16 version.
They don't boot with 2019-11-17 version and newer versions.
GRUB menu appears, I choose "Default install", the yellow screen is
cleaned and after "Loading..
> On Apr 28, 2019, at 12:30 PM, Frank Scheiner wrote:
>
> On 4/28/19 18:08, John Paul Adrian Glaubitz wrote:
>> Hi!
>>
>> On 4/25/19 9:20 AM, Mathieu Malaterre wrote:
Best would be, of course, to fix the ofpathname from the IBM utils package.
>>>
>>> Could you give more details as to wh
On 4/28/19 18:08, John Paul Adrian Glaubitz wrote:
Hi!
On 4/25/19 9:20 AM, Mathieu Malaterre wrote:
Best would be, of course, to fix the ofpathname from the IBM utils package.
Could you give more details as to why you believe this would be 'best'
? While I never had feedback from neither IBM
Hi!
On 4/25/19 9:20 AM, Mathieu Malaterre wrote:
>> Best would be, of course, to fix the ofpathname from the IBM utils package.
>
> Could you give more details as to why you believe this would be 'best'
> ? While I never had feedback from neither IBM group nor GRUB group
> about my (WIP) patches,
Hi Adrian,
On Thu, Apr 18, 2019 at 4:30 PM John Paul Adrian Glaubitz
wrote:
>
> On 4/18/19 1:10 AM, Frank Scheiner wrote:
> > @Adrian, Mathieu:
> >
> > We could use this opportunity to evaluate Mathieu's patches from [1] and
> > [2]. This will also require changes to `grub-install`, but in the en
ted off it
> > several times, but I believe after an update to grub-ieee1275
> > installed, I can't boot back in. The boot selector does not display
> > an HD with a penguin as it always did, and not even running
> > install-grub and update-grub2 in a rescue terminal change
On 4/18/19 1:10 AM, Frank Scheiner wrote:
> @Adrian, Mathieu:
>
> We could use this opportunity to evaluate Mathieu's patches from [1] and
> [2]. This will also require changes to `grub-install`, but in the end
> could be the "best" solution as `grub-ofpathname` would be included in
> the GRUB pac
On 4/18/19 00:26, John Paul Adrian Glaubitz wrote:
> On 4/18/19 12:06 AM, Frank Scheiner wrote:
>>> My guess is an update broke something, because I don't remember
>>> successfully rebooting after that, but I'm not sure.
>>
>> Sad to hear that. Doesn't `boot hd:2,\grub` work - assuming you have a
On 4/18/19 12:06 AM, Frank Scheiner wrote:
>> My guess is an update broke something, because I don't remember successfully
>> rebooting after that, but I'm not sure.
>
> Sad to hear that. Doesn't `boot hd:2,\grub` work - assuming you have a
> single disk drive in your G5?
>
> What does `printenv
Hi Noah,
On 4/16/19 19:50, Noah Wolfe wrote:
> Hey all, it is I again.
>
> GRUB initially installed fine, and this G5 even booted off it several times,
> but I believe after an update to grub-ieee1275 installed, I can't boot back
> in. The boot selector does not display an
Hey all, it is I again.
GRUB initially installed fine, and this G5 even booted off it several times,
but I believe after an update to grub-ieee1275 installed, I can't boot back in.
The boot selector does not display an HD with a penguin as it always did, and
not even running install-gru
Good that there are patches. I ran out of ideas.
Another option would be not to link against libext2fs, but copy some
essential code out for ext2/3.
It is likely that more patches will be needed in future.
Like it is done with xfs and reiserfs.
G
On 08/05/2011 12:34 AM, Rick Thomas wrote:
Does this patch (from the yaboot-devel mailinglist) help with this bug?
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636269
Is there some way I can help test it?
"[PATCH 1/2] Support sysfs in ofpath"
http://lists.ozlabs.org/pipermail/yaboot-devel/2011-August/000382.html
a
hi!
first sorry for my english because is very bad.
my problem is that i installed in a Mac PowerPC G5 debian, all the HD for
debian i dont need mac becuse i would like have a server, when the
installation was good except the deteccion off DHCP. when i finished the
installation and reboot the G5 s
> I don't know what I did wrong. According to some NetBSD documentation I
> had a look at, the broken folder icon means that Mac OSX cannot find a
> bootable partition. mac-fdisk see the partitions in Debian, but parted
> does not see any. Also I booted the OSX installer CD and accessed the
> di
I meant iBook in this message not Powerbook. It's an iBook G3 700 MHz that
I've got.
Ananda
On Tue, 23 Jan 2007 11:11:57 +
Ananda Samaddar <[EMAIL PROTECTED]> wrote:
> I used the image I got from here:
>
> http://wiki.debian.org/DebianInstaller/GUI
>
> I think the link for the PPC images
I used the image I got from here:
http://wiki.debian.org/DebianInstaller/GUI
I think the link for the PPC images are for a daily build so yes I must have
used one of those. I did have Ubuntu on there, but via the alternate CD. When
I found out they were dropping PPC I decided to put Debian on
Hi,
On Tuesday 23 January 2007 10:13, Ananda Samaddar wrote:
> Must have been something with the buggy graphical installer or my messing
> with the partitions. I used OSX partitioning tool to partition the HDD
> (it's piece of crap by the way) and everything is working dual-boot wise
> now.
>
>
Must have been something with the buggy graphical installer or my messing with
the partitions. I used OSX partitioning tool to partition the HDD (it's piece
of crap by the way) and everything is working dual-boot wise now.
Feel like a bit of a moron now!
Ananda
On Mon, 22 Jan 2007 20:12:03
I don't know what I did wrong. According to some NetBSD documentation I had a
look at, the broken folder icon means that Mac OSX cannot find a bootable
partition. mac-fdisk see the partitions in Debian, but parted does not see
any. Also I booted the OSX installer CD and accessed the disk util
On Monday 22 January 2007 19:14, Clive Menzies wrote:
> On (22/01/07 16:49), Ananda Samaddar wrote:
> > I am new to the PPC platform after having use either Debian or Ubuntu
> > on X86 for a while now. I would describe myself as an intermediate
> > user, I can usually get most things working on my
On (22/01/07 16:49), Ananda Samaddar wrote:
> I am new to the PPC platform after having use either Debian or Ubuntu
> on X86 for a while now. I would describe myself as an intermediate
> user, I can usually get most things working on my own, but this one
> has got me stumped.
>
> After selecting
Forgot to mention the system specs are:
iBook G3 12" 700 MHz
128 MB RAM
ATI Radeon, 16MB Gfx
cheers,
Ananda
On Mon, 22 Jan 2007 16:49:52 +
Ananda Samaddar <[EMAIL PROTECTED]> wrote:
> Hello everyone,
>
> I am new to the PPC platform after having use either Debian or Ubuntu on X86
> for
Hello everyone,
I am new to the PPC platform after having use either Debian or Ubuntu on X86
for a while now. I would describe myself as an intermediate user, I can
usually get most things working on my own, but this one has got me stumped.
After selecting Mac OSX (10.1 btw) from the Yaboot pr
ly I get something like 'can't boot kernel' (stable)
> or Can't read Elf e_ident/e_type/e_machine info (etch) and the kernel
> does not even get started. Can anyone suggest what might be wrong? I've
> tried it with ubuntu as well with the same result as etch.
>
I've installed debian on my 233MHz imac without problems.I bet it is that you need to upgrade your firmware
On 7/10/06, Matthew Yee-King <[EMAIL PROTECTED]> wrote:
I am trying to bring an ancient imac g3 233 back into service but am
If the system is Circa 1999 then this is an iffy situation -- not all
of those iMacs released during 1999 are compatible.
The oldest iMac I have been able to get Debian
Hello list folk
I am trying to bring an ancient imac g3 233 back into service but am
having trouble booting the kernel from yaboot. I can boot the install CD
and am presented with the yaboot prompt but when i type install or
install video=ofonly I get something like 'can't boot kerne
Paul,
This new version of the patch breaks 32-bit arch/ppc builds. The changes
to the idle_6xx code are shared between architectures, but the entry.S
code and asm-offsets.c are not.
Here's a patch that puts the changes in arch/ppc as well. Builds and
boots on 834x (which is CONFIG_6xx).
On Tue, Apr 18, 2006 at 09:56:00AM -0500, Olof Johansson wrote:
> On Tue, Apr 18, 2006 at 04:32:46PM +1000, Paul Mackerras wrote:
>
> > > understand now why you were talking about putting the code in the exit
> > > path on irc ... I don't like it that way Also, if you want to keep
> > > it, ma
On Tue, Apr 18, 2006 at 04:32:46PM +1000, Paul Mackerras wrote:
> > understand now why you were talking about putting the code in the exit
> > path on irc ... I don't like it that way Also, if you want to keep
> > it, maybe use a separate CONFIG_PPC_970STYLE_NAP or something that gets
> > sele
Benjamin Herrenschmidt writes:
> The 970 version bloats the exception prolog significantly... I
Four instructions, in the external and decrementer interrupt entry
paths - I don't think that's really significant bloat.
> understand now why you were talking about putting the code in the exit
> pat
Benjamin Herrenschmidt writes:
> Looks good to me except that we need the same for ppc64 since the 970
> theorically has the same problem...
OK, does this look OK to everyone, before I send it off to Linus? I
now use a bit in the thread_info rather than using the HID0 bits
themselves to indicate
On Tue, 2006-04-18 at 16:32 +1000, Paul Mackerras wrote:
> Benjamin Herrenschmidt writes:
>
> > The 970 version bloats the exception prolog significantly... I
>
> Four instructions, in the external and decrementer interrupt entry
> paths - I don't think that's really significant bloat.
Yeah well
On Tue, 2006-04-18 at 15:45 +1000, Paul Mackerras wrote:
> Benjamin Herrenschmidt writes:
>
> > Looks good to me except that we need the same for ppc64 since the 970
> > theorically has the same problem...
>
> OK, does this look OK to everyone, before I send it off to Linus? I
> now use a bit in
> > Actually, I think the problem is that the code linux is using to turn
> > on nap mode is not guaranteed to put the processor in nap mode by the
> > time the blr in ppc6xx_idle occurs.
>
> Thanks, Becky.
>
> This patch fixes it for me. Comments, anyone?
Works for me :-)
Michael
--
On Fri, 2006-04-14 at 12:07 -0700, Paul Mackerras wrote:
Becky Bruce writes:
Actually, I think the problem is that the code linux is using to turn
on nap mode is not guaranteed to put the processor in nap mode by the
time the blr in ppc6xx_idle occurs.
Thanks, Becky.
This patch fixes it f
Olof Johansson writes:
> Where is cr0 set now -- you took the dot off of rlwinm?
transfer_to_handler does mfspr r11,SPRN_HID0; mtcr r11 before jumping
to power_save_6xx_restore. The rlwinm. was wrong anyway since it was
setting cr0.eq based on all the *other* bits in HID0, not HID0_NAP
(doh!).
He's being sneaky - there's a copy of HID0 in the CR at this point
from the caller, and bit 9 is the position for NAP.
-B
On Apr 14, 2006, at 2:54 PM, Olof Johansson wrote:
Hi,
On Fri, Apr 14, 2006 at 12:07:23PM -0700, Paul Mackerras wrote:
Becky Bruce writes:
Actually, I think the proble
Becky Bruce writes:
> Actually, I think the problem is that the code linux is using to turn
> on nap mode is not guaranteed to put the processor in nap mode by the
> time the blr in ppc6xx_idle occurs.
Thanks, Becky.
This patch fixes it for me. Comments, anyone?
Paul.
diff -urN powerpc-me
On Fri, 2006-04-14 at 15:00 -0500, Becky Bruce wrote:
> He's being sneaky - there's a copy of HID0 in the CR at this point
> from the caller, and bit 9 is the position for NAP.
It's a trick I learned from Darwin :) They do that regulary when code is
very cpu-feature dependant, like cache code fo
On Fri, 2006-04-14 at 12:07 -0700, Paul Mackerras wrote:
> Becky Bruce writes:
>
> > Actually, I think the problem is that the code linux is using to turn
> > on nap mode is not guaranteed to put the processor in nap mode by the
> > time the blr in ppc6xx_idle occurs.
>
> Thanks, Becky.
>
>
On Fri, Apr 14, 2006 at 01:19:36PM -0700, Paul Mackerras wrote:
> Olof Johansson writes:
>
> > Where is cr0 set now -- you took the dot off of rlwinm?
>
> transfer_to_handler does mfspr r11,SPRN_HID0; mtcr r11 before jumping
> to power_save_6xx_restore. The rlwinm. was wrong anyway since it was
Hi,
On Fri, Apr 14, 2006 at 12:07:23PM -0700, Paul Mackerras wrote:
> Becky Bruce writes:
>
> > Actually, I think the problem is that the code linux is using to turn
> > on nap mode is not guaranteed to put the processor in nap mode by the
> > time the blr in ppc6xx_idle occurs.
>
> Thanks,
On Apr 13, 2006, at 3:55 PM, Benjamin Herrenschmidt wrote:
The above code should really look like this:
mfmsr r7
ori r7,r7,MSR_EE
orisr7,r7,[EMAIL PROTECTED]
sync
isync
mtmsr r7
isync
label:
b label
On Apr 13, 2006, at 5:20 AM, Benjamin Herrenschmidt wrote:
(For those who haven't followed the beginning, current git locks up at
boot on most recent powermacs. It was tracked down to a weird problem
with the idle code. My latest experiments seem to show something dodgy
with MSR_POW). Help from
Benjamin Herrenschmidt writes:
> > _GLOBAL(power_save_6xx_restore)
> > mfspr r11,SPRN_HID0
> > rlwinm r11,r11,0,10,8 /* Clear NAP */
> > mtspr SPRN_HID0,r11
> > b transfer_to_handler_cont
> >
> > If I take out that rlwinm, it boots. Bizaare.
>
> Gack ? Didn't
On Mon, 2006-04-10 at 13:10 +0200, Enrico Cataldi wrote:
> Finally, got it!
> 2.6.17-rc1 plus patch from Paul Mackerras, now i've it running!
> Thanks a lot for the great work!
The patch isn't entirely correct though. It just hides the problem. I
think I've found out what's going on and wi
On Fri, Apr 14, 2006 at 08:37:21AM +1000, Benjamin Herrenschmidt wrote:
> I need to verify what's up with the 970. I noticed Apple has some
970 keeps executing too. I guess it's never bitten hard enough to
trigger anything serious.
-Olof
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a s
> FYI, the user's manual recommends this sequence:
> loop:
>sync
>mtmsr POW
>isync
>b loop
Ok, that's what OS X does... I always wondered ...
So ideally, we should do something similar to the above and set some
global bit somewhere telling the exception path t
>
> The above code should really look like this:
>
> mfmsr r7
> ori r7,r7,MSR_EE
> orisr7,r7,[EMAIL PROTECTED]
> sync
> isync
> mtmsr r7
> isync
> label:
> b label
> blr
Ohhh ... we always assumed mtmsr wi
(For those who haven't followed the beginning, current git locks up at
boot on most recent powermacs. It was tracked down to a weird problem
with the idle code. My latest experiments seem to show something dodgy
with MSR_POW). Help from Freescale folks would be appreciated.
On Sat, 2006-04-08 at 1
On Sat, 2006-04-08 at 12:55 +1000, Paul Mackerras wrote:
> Benjamin Herrenschmidt writes:
>
> > From my quick tests here (I'm travelling, so no much time), it looks
> > like it's dying on the first msleep() (either radeonfb or whatever else
> > if you play with driver order), which makes me strong
Finally, got it!
2.6.17-rc1 plus patch from Paul Mackerras, now i've it running!
Thanks a lot for the great work!
Best regards,
cataenry
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> > Even more bizarre: if I get the old arch/ppc default_idle() from the
> > attic, and call that in cpu_idle() instead of ppc_md.power_save(), it just
> > works.
> >
> Thanks. It works for me.
> Now I get another new problem, I lose the sound:
You should have noticed errors when building the soun
On 4/8/06, Michael Schmitz <[EMAIL PROTECTED]> wrote:
> > > From my quick tests here (I'm travelling, so no much time), it looks
> > > like it's dying on the first msleep() (either radeonfb or whatever else
> > > if you play with driver order), which makes me strongly suspect the idle
> > > loop ch
> > From my quick tests here (I'm travelling, so no much time), it looks
> > like it's dying on the first msleep() (either radeonfb or whatever else
> > if you play with driver order), which makes me strongly suspect the idle
> > loop changes. I'll try to fix that when I'm back next week unless pau
Benjamin Herrenschmidt writes:
> From my quick tests here (I'm travelling, so no much time), it looks
> like it's dying on the first msleep() (either radeonfb or whatever else
> if you play with driver order), which makes me strongly suspect the idle
> loop changes. I'll try to fix that when I'm b
> I've hard resetted the source and reverted the "bad commit", and it
> still hangs.
> If i can do something to help, let me know.
You can try to revert the idle loop changes manually. The comment in
Paulus' commit indicates that the caller of the idle loop handles
interrupt enable/disable,
> > >From my quick tests here (I'm travelling, so no much time), it looks
> > like it's dying on the first msleep() (either radeonfb or whatever else
> > if you play with driver order), which makes me strongly suspect the idle
> > loop changes. I'll try to fix that when I'm back next week unless pa
> >From my quick tests here (I'm travelling, so no much time), it looks
> like it's dying on the first msleep() (either radeonfb or whatever else
> if you play with driver order), which makes me strongly suspect the idle
> loop changes. I'll try to fix that when I'm back next week unless paulus
> b
I've hard resetted the source and reverted the "bad commit", and it
still hangs.
If i can do something to help, let me know.
Regards,
CataEnry
--
Enrico Cataldi - Undergraduate student @ Computer Science
mailto: [EMAIL PROTECTED] ICQ: 211912796 MSN: [EMAIL PROTECTED]
Hamradio: IW6DMM http:/
> > This is an ATi-based machine, Mobility 9600 or 9700. Not sure of the
> > exact number. As others have already tried, it doesn't seem to help to
> > switch to OpenFirmware framebuffer. The machine will lock up anyway :/
>
> Yep, that points to radeonfb being OK. I'll have a look myself later
>
> >> I see the same hang on my PowerBook 5,9 (17" G4 HR). Note that I don't
> >> run Debian, but I thought I'd help out.
> >> The patch has a bit too much changes behind it to do a simple revert.
> >
> > Please add the later commit from Paulus on top of this one (ff2e6d7427...)
> > and try that one
> On Apr 06 2006, Michael Schmitz wrote:
> > Well, 2.6.17 not booting seems well established now. What you can do
> > to track down the cause is called 'git bisection'. Google should have
> > a few instructions on that.
>
> Hummm, this is strange, since I just grabbed the .17-rc1 patch,
> recompile
On Apr 06 2006, Michael Schmitz wrote:
> Well, 2.6.17 not booting seems well established now. What you can do
> to track down the cause is called 'git bisection'. Google should have
> a few instructions on that.
Hummm, this is strange, since I just grabbed the .17-rc1 patch,
recompiled a kernel fo
Hi! I've done some hard work, even if i think there's somthing strange..
that simple pointer initialization shouldn't do all this. But i
shouldn't have make mistakes. Hope this helps.
At least, i hope the attempt will be appreciated.
Best regards,
CataEnry
--
Michael Schmitz wrote:
A bisection between 2.6.16 and 2.6.17-rc1 (current GIT tree), which
took quite a few reboots, thinks this is the bad guy:
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=a0652fc9a28c3ef8cd59264bfcb089c44d1b0e06
I see the same hang on my Powe
> A bisection between 2.6.16 and 2.6.17-rc1 (current GIT tree), which
> took quite a few reboots, thinks this is the bad guy:
> http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=a0652fc9a28c3ef8cd59264bfcb089c44d1b0e06
>
> I see the same hang on my PowerBook 5,9 (17" G
> A bisection between 2.6.16 and 2.6.17-rc1 (current GIT tree), which
> took quite a few reboots, thinks this is the bad guy:
No bisect without reboots :-) Thanks for taking the time ...
> http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=a0652fc9a28c3ef8cd59264bfcb0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
A bisection between 2.6.16 and 2.6.17-rc1 (current GIT tree), which
took quite a few reboots, thinks this is the bad guy:
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=a0652fc9a28c3ef8cd59264bfcb089c44d1b0e06
I see th
> On my system the kernel hangs during console_init.
> Since its configuration comes from an oldconfig and others manual
> check, it should be right.
> Hope this helps.
Well, 2.6.17 not booting seems well established now. What you can do to
track down the cause is called 'git bisection'. Google sh
Hi all.
On my system the kernel hangs during console_init.
Since its configuration comes from an oldconfig and others manual
check, it should be right.
Hope this helps.
CataEnry
--
Enrico Cataldi - Undergraduate student @ Computer Science
mailto: [EMAIL PROTECTED] ICQ: 211912796 MS
On 4/4/06, cataenry <
[EMAIL PROTECTED]> wrote:
Hi Bin,yes, i've the same problem, in particular, my iBook (PowerBook6,7)hangs after time_init prints. Now i'm building a kernel with someprintk to detect if it hangs during console_init.
I'm seeing the same problem with 2.6.17-rc1 on my Powerbook6,
Hi Bin,
yes, i've the same problem, in particular, my iBook (PowerBook6,7)
hangs after time_init prints. Now i'm building a kernel with some
printk to detect if it hangs during console_init.
--
Enrico Cataldi - Ungraduate student @ Computer Science
mailto: [EMAIL PROTECTED] - Hamradio: IW6
Hi,
I have just tested the 2.6.17-rc1? It did not start on my ibook, I
saw yaboot and the first screen, but it stopped before "linux logo".
Did somebody succeed?
Regards,
Bin
On Wed, 2006-02-08 at 10:58 +0100, Arnaud Vandyck wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Arnaud Vandyck wrote:
> > Benjamin Herrenschmidt wrote:
> >
> >>>On Tue, 2006-02-07 at 14:55 +0100, Arnaud Vandyck wrote:
> >
> > [...]
> >
> 0 > boot ide1/[EMAIL PROTECTED]:0,\ins
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sven Luther wrote:
> On Wed, Feb 08, 2006 at 12:52:19PM +0100, Arnaud Vandyck wrote:
[...]
>>So, with Woody AND Sarge (booting with BootX), I could install a
>>complete Debian installation but it's impossible to boot on the new
>>installation!
>
> C
1 - 100 of 193 matches
Mail list logo
