OK, I stand corrected!
In any case, whatever the number, it seems to be fixed. And that's what's
important!
Rick
On Wed, Oct 11, 2023, at 2:02 AM, John Paul Adrian Glaubitz wrote:
> Hi Rick!
>
> On Wed, 2023-10-11 at 01:20 -0700, Rick Thomas wrote:
>> I just did an update -> upgrade on my Power
Hi Rick!
On Wed, 2023-10-11 at 01:20 -0700, Rick Thomas wrote:
> I just did an update -> upgrade on my Power Mac G4 and noticed
> that it provides the new kernel version 6.5.0-2 .
That's not the kernel version, but the ABI version of the kernel.
The kernel version is 6.5.6 and the version of the
Wow!
I just did an update -> upgrade on my Power Mac G4 and noticed that it provides
the new kernel version 6.5.0-2 .
This appears to have fixed the panic-on-boot bug in version 6.5.0-1 .
Big thanks for all your efforts!
Rick
Hi Adrian,
On 10/1/23 2:31 PM, John Paul Adrian Glaubitz wrote:
> ...
> You can build a kernel with Debian's configuration. You just have to disable
> the kernel config options CONFIG_SYSTEM_TRUSTED_KEY and CONFIG_MODULE_SIG_KEY.
> ...
I think the problem with the references to trusted keys has b
On Sun, 2023-10-01 at 12:56 -0600, Stan Johnson wrote:
> On a PowerMac G4 MDD (2 CPUs, 2 GiB), I tested the following stock
> kernels with a current Debian SID installation:
>
> v6.5 : smp works, non-smp crashes (oops panic)
> v6.6-rc3 : smp works, non-smp works
>
> Since the latest stock kernel
On 9/28/23 2:38 AM, Dan Whitehouse wrote:
> Hi all,
> I am seeing a kernel panic on my PowerMac3,1 MacRISC Power Macintosh
> running debian with kernel 6.5.0-1.
>
> It seems to be working well with:
>
> Linux powermac-g4 6.4.0-4-powerpc #1 Debian 6.4.13-1 (2023-08-31) p
> On Sep 30, 2023, at 4:25 PM, DistroHopper39B Business
> wrote:
>
>
> This patch worked for me. I have a successful 6.5.3 built and running on my
> PowerBook G4 (with CONFIG_KFENCE=y as well).
Please report that back to the patch author.
Use the Tested-by tag. [1]
Adrian
> [1] https://
3, at 01:02, DistroHopper39B Business <
> distrohopper39b.busin...@gmail.com> wrote:
>
> I rebuilt the kernel with CONFIG_KFENCE=n and the kernel panic persists
> (same error). I used the source from the linux-source-6.5 package in Debian
> sid.
>
>
>
at 01:02, DistroHopper39B Business
> wrote:
>
> I rebuilt the kernel with CONFIG_KFENCE=n and the kernel panic persists (same
> error). I used the source from the linux-source-6.5 package in Debian sid.
I rebuilt the kernel with CONFIG_KFENCE=n and the kernel panic persists
(same error). I used the source from the linux-source-6.5 package in Debian
sid.
On 9/28/23 2:38 AM, Dan Whitehouse wrote:
> Hi all,
> I am seeing a kernel panic on my PowerMac3,1 MacRISC Power Macintosh
> running debian with kernel 6.5.0-1.
>
> It seems to be working well with:
>
> Linux powermac-g4 6.4.0-4-powerpc #1 Debian 6.4.13-1 (2023-08-31) p
On Thu, 2023-09-28 at 07:58 -0400, DistroHopper39B Business wrote:
> This issue is also happening to me, on both a 15 inch Powerbook G4 and an
> iBook Clamshell. It’s worth noting that neither a test build of Linux 6.5.5
> I recently built for PowerPC or Linux 6.5.4 packaged by ArchPOWER has this
>
000 9421f
> > e0 7c0802a6 3d20c141 93e1001c 90010024 83e9c294 <943f1ff0> 7fe1fb78
> 48b24909 80
> > 1
> > 0.00] ---[ end trace ]---
> > 0.00]
> > 0.00] Kernel panic - not syncing: Attempted to kill the idle
> task!
> >
; 0.00] Code: 7d2a01a4 4c00012c 4b28 7c0802a6 90010004 6000
> 9421f
> e0 7c0802a6 3d20c141 93e1001c 90010024 83e9c294 <943f1ff0> 7fe1fb78 48b24909
> 80
> 10000
> 0.00] ---[ end trace ]---
> 0.00]
> 0.00] Kernel pan
trace ]---
0.00]
0.00] Kernel panic - not syncing: Attempted to kill the idle task!
0.00] ---[ end Kernel panic - not syncing: Attempted to kill the idle t
ask! ]---
--
Dan Whitehouse
GPG: 3AA4 369C 86E1 4939 D420 AB25 D0DC 7BDD CA92 AD2E
Telephone: +44(0)203 0955088
Hi all,
I am seeing a kernel panic on my PowerMac3,1 MacRISC Power Macintosh
running debian with kernel 6.5.0-1.
It seems to be working well with:
Linux powermac-g4 6.4.0-4-powerpc #1 Debian 6.4.13-1 (2023-08-31) ppc
GNU/Linux
I have a photo of the panic screen which I can attach if useful
Good question, Amos.
You should begin with listing the files:
ls -al /mnt2
What do you get? Usually there are links vmlinux and initrd.img
pointing at vmlinux-2.6.x.x.x and initrd.img-2.6.x.x.x, respectively.
They should come from a package called linux-image-2.6 or something
similar. You can se
Risto,
Thanks for the continued support. I continued through the
installation to the partitions portions, and all of the partitions
were as I thought - sda6 is the hfsplus partition where OS 9 is
loaded. I then continued all the way through the installation to the
point where I was inst
Hmm... looks like /dev/sda does not exist, yet. But somewhere under
the /dev tree there are probably the right entries. Perhaps /dev/scsi
or /dev/bus or /dev/disk something.
You could just try to let the installation process continue a bit
further. When it's about to start the partitioning, the sd
Risto,
Thanks much for your response. I followed your directions, but after
issuing this command: "mount -t hfsplus /dev/sda6 /mnt1", I received
the following text: "mount: Mounting /dev/sda6 on /mnt1 failed: No
such device."
I also made attempts with "hfs" and "sda5", but received the s
Hi Amos,
The one thing you probably forgot, was to copy the vmlinux and
initrd.img images from /boot to Mac OS 'Linux Kernels' folder. Then
you will have to direct BootX to use them, as you did with the images
from the install CD.
Now you must try to re-start the installation and then suspend it
te blocks and clicked "Save to prefs" and then the "Linux"
button. After seeing a half page of text, followed by a full page of
text, the boot stops and the bottom four lines of text are as follows:
"VFS: Cannot open root device "sda8" or unknown-block (0,
On Monday 02 July 2007 10:46, Peter Czanik wrote:
> I can't help you with coding, but I don't think, that testing the PPC
> installer once or twice a week on Pegasos PPC would be a problem for
> me.
That is an excellent offer. However, without somebody else from the
PowerPC community able to help
Hello,
Frans Pop wrote:
> Let me also use this opportunity to remind the Debian PowerPC community
> that are still looking for people willing to get involved more in the
> installer for PowerPC and help us deal with port-specific issues.
>
> In this case, this bug report from Peter was the first
Original Message
Subject:Re: Bug#429985: PPC installer kernel panic from libc problem
Date: Mon, 2 Jul 2007 09:48:12 +0200
From: Sven Luther <[EMAIL PROTECTED]>
To: Frans Pop <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED], Peter Czanik <[EMAIL PROT
On Thursday 21 June 2007 16:21, Peter Czanik wrote:
> Installation fails right after the kernel is booted with the following
> message:
> /bin/sh: symbol lookup error: /lib/libc.so.6: undefined symbol:
> _rtld_global Kernel panic - not syncing: attembed to kill init!
With today&#x
Subject:
PPC installer kernel panic from libc problem
From:
Peter Czanik <[EMAIL PROTECTED]>
Date:
Thu, 21 Jun 2007 16:21:06 +0200
To:
[EMAIL PROTECTED]
CC:
[EMAIL PROTECTED]
Package: installation-reports
Boot method: CD
Image version:
http://cdimage.debian.org/cdimage/daily-builds
> > dmesg -- http://deserved.servegame.org/serial.txt
> >
> > Anybody have any ideas on how to fix this? Thanks.
>
> It seems to be as simple as to create that file:
>
> mknod /dev/console c 5 1
I strongly doubt that:
pivot_root: No such file or directory
/K
De Served wrote:
>
> dmesg -- http://deserved.servegame.org/serial.txt
>
> Anybody have any ideas on how to fix this? Thanks.
It seems to be as simple as to create that file:
mknod /dev/console c 5 1
Or let the kernel load devfs with a statement in the append line:
devfs=mount,all
Cheers,
I'm attempting to install Debian Sarge on a PowerMac 7200/90. The
install process works just fine. The machine reboots without a problem
for a little while, then I get a kernel panic and message saying that
the console cannot be found.
Here's a link to the dmesg. I'll upda
;>>Caused by (from SRR1=149030): Transfer error ack signal
>>>Oops: machine check, sign: 7[#1]
>>>.
>>>
>>>.
>>>Kernel panic -not syncing: Aiee, killing interrupt handler!
>>>
>>>
&
0x70
[c0006964] cpu_idle+0x44/0x50
[c0004cd8] rest_init+0x28/0x40
[c02cc6d8] start_kernel+0x158/0x1c0
[00003700] 0x3700
Kernel panic -not syncing: Aiee, killing interrupt handler!
ive copied it by hand and in two or three times so some numbers may
differ,(i supouse that it wont be in any
On Tue, 2005-11-01 at 03:35 +, Saladino wrote:
> Hi, it is the usb handler i supose(when i unplug the usb mouse it
> works correctly) i can paste the whole backtrace if its needed.
> Thanks for your time
> Saladino
Yes, I need to track that down.
Ben.
--
To UNSUBSCRIBE, email to [EMAIL PR
r error ack signal
> > Oops: machine check, sign: 7[#1]
> > .........
> >
> > .
> > Kernel panic -not syncing: Aiee, killing interrupt handler!
>
> Was it happening in the USB interrupt handler ? (the call backtrace
> should be appended to the Oop
149030): Transfer error ack signal
> Oops: machine check, sign: 7[#1]
> .
> ........
> .
> Kernel panic -not syncing: Aiee, killing interrupt handler!
Was it happening in the USB interrupt handler ? (the call backtrace
should be appended to
ror ack signal
Oops: machine check, sign: 7[#1]
.....
....
.
Kernel panic -not syncing: Aiee, killing interrupt handler!
Zack:/home/saladino# cat /proc/cpuinfo
processor : 0
cpu : 7447A, altivec supported
clock : 666MHz
revision: 0.5 (p
gt; Machine check in Kernel mode
> Caused by (from SRR1=149030): Transfer error ack signal
> Oops: machine check, sign: 7[#1]
> .
> ....
> .
> Kernel panic -not syncing: Aiee, killing interrupt handler!
>
> Before i used(im using a
RR1=149030): Transfer error ack signal
> > Oops: machine check, sign: 7[#1]
> > .
> >
> > .
> > Kernel panic -not syncing: Aiee, killing interrupt handler!
> >
> > Before i used(im using again) 2.6.13.4 kernel with 2 patches for
...
> Machine check in Kernel mode
> Caused by (from SRR1=149030): Transfer error ack signal
> Oops: machine check, sign: 7[#1]
> .
> ....
> .
> Kernel panic -not syncing: Aiee, killing interrupt handler!
>
> Before i used(
chine check, sign: 7[#1]
.
.
Kernel panic -not syncing: Aiee, killing interrupt handler!
Before i used(im using again) 2.6.13.4 kernel with 2 patches for sleep
support, and works well.
If more information is required please let me know.
Thanks for
Hi,
On Mon, Jun 13, 2005 at 07:57:42PM +0200, Antoni Aloy wrote:
> Hello!
>
> I've recently purchased a PowerMac G2 dual processor, 1 Gb RAM, 250 Gb of HD
> with 20" flat screen.
>
> I'm trying to install debian or Ubuntu on it, but I get a kernel panic e
Hello!
I've recently purchased a PowerMac G2 dual processor, 1 Gb RAM, 250 Gb of HD
with 20" flat screen.
I'm trying to install debian or Ubuntu on it, but I get a kernel panic each
time.
It says:
Oops: kernel acccess of bad area, sig: 11 [#1]
Then a register dump follows and
On Thu, May 05, 2005 at 10:29:38PM +0800, William Xuuu wrote:
> Wolfgang Pfeiffer <[EMAIL PROTECTED]> writes:
>
> > On Thu, May 05, 2005 at 08:16:45PM +0800, William Xuuu wrote:
> >> Wolfgang Pfeiffer <[EMAIL PROTECTED]> writes:
> >>
> >> > On Thu, May 05, 2005 at 04:56:45PM +0800, [EMAIL PROTECT
Wolfgang Pfeiffer <[EMAIL PROTECTED]> writes:
> On Thu, May 05, 2005 at 08:16:45PM +0800, William Xuuu wrote:
>> Wolfgang Pfeiffer <[EMAIL PROTECTED]> writes:
>>
>> > On Thu, May 05, 2005 at 04:56:45PM +0800, [EMAIL PROTECTED] wrote:
>>
>>
>> Well, when i first installed debian, the kernel was
On Thu, May 05, 2005 at 08:16:45PM +0800, William Xuuu wrote:
> Wolfgang Pfeiffer <[EMAIL PROTECTED]> writes:
>
> > On Thu, May 05, 2005 at 04:56:45PM +0800, [EMAIL PROTECTED] wrote:
>
>
> Well, when i first installed debian, the kernel was only 2.4.23, and
> couldn't recognize my ATA harddisk c
gt; with initrd support, but was unable to boot the new kernel, which stops
>> at:
>>
>> Please append a correct "root=" boot option
>> Kernel panic - not syncing: VFS: Unable to mount root fs on
>> unknown-block..
>>
>> In `/'
to boot the new kernel, which stops
>>at:
>>
>>Please append a correct "root=" boot option
>>Kernel panic - not syncing: VFS: Unable to mount root fs on
>>unknown-block..
>>
>>In `/' i have:
>>
>>/initrd.img ->
On Thu, May 05, 2005 at 04:56:45PM +0800, [EMAIL PROTECTED] wrote:
> Hi,
>
> os: debian on an ibook(G4, 1G, 12")
>
> I've just installed a new kernel image (kernel-image-2.6.11-powerpc)
> with initrd support, but was unable to boot the new kernel, which stops
> at:
[ ... ]
> ==
[EMAIL PROTECTED] wrote:
Hi,
os: debian on an ibook(G4, 1G, 12")
I've just installed a new kernel image (kernel-image-2.6.11-powerpc)
with initrd support, but was unable to boot the new kernel, which stops
at:
Please append a correct "root=" boot option
Kernel pani
t; at:
>
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block..
>
> In `/' i have:
>
> /initrd.img -> boot/initrd.img-2.6.11-powerpc
> /vmlinux -> boot/vmlinux-2
Hi,
os: debian on an ibook(G4, 1G, 12")
I've just installed a new kernel image (kernel-image-2.6.11-powerpc)
with initrd support, but was unable to boot the new kernel, which stops
at:
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Una
On Wed, Mar 02, 2005 at 11:40:34AM -0800, Kim Cascone wrote:
> unfortunately when you start the install from the Ubuntu .iso and drop
> into the command line it only offers you a small range of commands to
> use:
> break
> cd
> chdir
> continue
> eval
> exec
> exit
> export
> false
> hash
> help
wait
so apparently this is not like Debianppc...anyone else have experience
with fixing an Ubuntu kernel panic?
On Mar 2, 2005, at 10:53 AM, Wolfgang Pfeiffer wrote:
If Ubuntu/ppc does not differ too much from Debian/ppc I'd try to run
again "ybin -v"
The exact procedure is descri
-X" I get the boot screen swiftly followed by a Darwin
kernel panic:
panic(cpu 0): Unable to find a driver for this platform: "AAPL,MOL".
Latest stack backtraceetc etc
Reinstalling the Debian packages has no effect, can I/should I reinstall
the OSX kexts. If so, how?
On Tue, Jun 22, 2004 at 02:04:08AM +0100, Colin Watson wrote:
> On Tue, Jun 22, 2004 at 09:44:58AM +0900, Jerome Walter wrote:
> > As we are to deal with the question: how to make a kernel including the
> > initrd ?
>
> mkvmlinuz
But this should really be automatically handled at kernel install
On Tue, Jun 22, 2004 at 09:44:58AM +0900, Jerome Walter wrote:
> As we are to deal with the question: how to make a kernel including the
> initrd ?
mkvmlinuz
--
Colin Watson [EMAIL PROTECTED]
Jens Schmalzing wrote:
Thanks for the advice. How do I make an initrd?
Use the mkinitrd command from the initrd-tools package. Make sure you
configure your bootloader to actually use the initrd.
Hi,
As we are to deal with the question: how to make a kernel including the
initrd ? I am try
Hi,
Doug Mellot <[EMAIL PROTECTED]> writes:
> --- Jens Schmalzing <[EMAIL PROTECTED]> wrote:
> > Use the mkinitrd command from the initrd-tools package. Make sure
> > you configure your bootloader to actually use the initrd.
And before I forget: Add the line "do_initrd = yes" to
/etc/kernel-im
Hi,
Doug Mellot writes:
> Thanks for the advice. How do I make an initrd?
Use the mkinitrd command from the initrd-tools package. Make sure you
configure your bootloader to actually use the initrd.
Regards, Jens.
--
J'qbpbe, le m'en fquz pe j'qbpbe!
Le veux aimeb et mqubib panz je pézqbpbe
Thanks a bunch, Jens. I'll try it out tonight.
--- Jens Schmalzing <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Doug Mellot writes:
>
> > Thanks for the advice. How do I make an initrd?
>
> Use the mkinitrd command from the initrd-tools
> package. Make sure you
> configure your bootloader to actuall
evice "Label=/" [note:
> I've
> > tried several things in yaboot.conf] or unknown
> block
> > (0,0)
> >
> > Please append a correct "root=" boot option.
> >
> > Kernel panic: VFS: Unable to mount root fs on
> > unknown block (0,
e-2.6.6-powerpc'), I get errors while
booting:
VFS: Cannot open root device "Label=/" [note: I've
tried several things in yaboot.conf] or unknown block
(0,0)
Please append a correct "root=" boot option.
Kernel panic: VFS: Unable to mount root fs on
unknown b
x27;), I get errors while
booting:
VFS: Cannot open root device "Label=/" [note: I've
tried several things in yaboot.conf] or unknown block
(0,0)
Please append a correct "root=" boot option.
Kernel panic: VFS: Unable
OoO En ce début d'après-midi nuageux du samedi 27 décembre 2003, vers
14:04, Soeren Sonnenburg <[EMAIL PROTECTED]> disait:
> then t in xmon (where you end up with when getting oopses or when
> pressing apple+power) gives you a backtrace that could be useful for
> developers.
Thanks, I was usi
On Sat, 2003-12-27 at 22:54, Vincent Bernat wrote:
> Hello !
>
> I have bought some USB sound card (Sound Blaster MP3+) and while this
> is working fine with usbaudio from the kernel OSS, I get some kernel
> panic with ALSA after some use (a matter of minutes).
>
> I
Hello !
I have bought some USB sound card (Sound Blaster MP3+) and while this
is working fine with usbaudio from the kernel OSS, I get some kernel
panic with ALSA after some use (a matter of minutes).
I'd like to report this to ALSA guys but the output of the internal
debugguer (from test11
> On Thu, 2003-09-04 at 18:57, Giuseppe Sacco wrote:
>> Il dom, 2003-08-31 alle 10:12, Pander ha scritto:
>> > Same here on PowerBook G4 12"
>> >
>> > Didn't change any settings in .config
>>
>> The problem seems to be solved in 2.4.22-ben2. The new kernel boots
>> without problem, but then it pani
On Thu, 2003-09-04 at 18:57, Giuseppe Sacco wrote:
> Il dom, 2003-08-31 alle 10:12, Pander ha scritto:
> > Same here on PowerBook G4 12"
> >
> > Didn't change any settings in .config
>
> The problem seems to be solved in 2.4.22-ben2. The new kernel boots
> without problem, but then it panics when
... still panic ...
I was syncing JPilot with an external PalmOS device, via USB, when I got
this kernel panic:
vector: 300 at pc = e30088b4, lr = e30088a4
msr = 9032, sp = dfe77ee0 [dfe77e30]
dar = 99c, dsisr = 4200
current = dfe76000, pid = 8, comm = kbubd
mon> t
backtrace:
e3008
Il dom, 2003-08-31 alle 10:12, Pander ha scritto:
> Same here on PowerBook G4 12"
>
> Didn't change any settings in .config
The problem seems to be solved in 2.4.22-ben2. The new kernel boots
without problem, but then it panics when closing the lid (in the pmud
task).
Do you experience the same
On Mon, 2003-09-01 at 02:06, Paul van Tilburg wrote:
> But now I'd like to move to a BenH kernel but penguinppc.org seems to be
> down :|.
> Since I used XFS for my / and /home partition I also need it to be
> patched with XFS support. Does anyone have the source + XFS patched
> available? Does any
On Sun, Aug 31, 2003 at 06:06:41PM +0200, Paul van Tilburg wrote:
> [...] Does anyone know what the deal is with penguippc.org
OK, it is up again, forget that question... ping -a forever!
Paul (hrm, replying to myself)
--
Student @ Eindhoven | JID: [EMAIL PROTECTED]
Un
On Sun, Aug 31, 2003 at 02:04:36PM +0200, Toni Cerdà wrote:
> On Sunday 31 August 2003 10:12, Pander wrote:
> > Same here on PowerBook G4 12"
> >
> > Didn't change any settings in .config
>
> I have also a PB G4 12'', 2.4.22-ben1 works without problems, here is my
> config:
>
> http://thebigpig.
On Sunday 31 August 2003 10:12, Pander wrote:
> Same here on PowerBook G4 12"
>
> Didn't change any settings in .config
I have also a PB G4 12'', 2.4.22-ben1 works without problems, here is my
config:
http://thebigpig.org/~toni/tmp/config-2.4.22-ben1.bz2
--
Ton
Same here on PowerBook G4 12"
Didn't change any settings in .config
eric b wrote:
Hi,
Récemment 30 Aug 2003 22:17:19 +0200
Giuseppe Sacco <[EMAIL PROTECTED]> a écrit:
I just rsync'd from CVS the latest kernel and got a kernel panic
during boot.
Yes, kernel panic
Hi,
Récemment 30 Aug 2003 22:17:19 +0200
Giuseppe Sacco <[EMAIL PROTECTED]> a écrit:
> I just rsync'd from CVS the latest kernel and got a kernel panic
> during boot.
Yes, kernel panic for me too...
> The machine is a powerbook3,5 [EMAIL PROTECTED], 15" with radeon,
I just rsync'd from CVS the latest kernel and got a kernel panic during
boot.
The last line printed is
Serial driver version enabled
the I get the internal monitor. The backtrace is
c031c14d
c02dde2c
c02ca4d4
c000400c
c0008bed
symbol map:
c0008bec __main
c0003ff8 init
c02ca4ac do_init
On Sat, 2003-08-16 at 22:49, W. Crowshaw wrote:
> Does anyone use quik anymore? I do on my PowerMac
> 7500 and it works fine (after some Open Firmware
> patches). But I get a kernel
> panic using quik when I add my
> Adaptec 2940U2W SCSI card to my machine. I've
> co
Does anyone use quik anymore? I do on my PowerMac
7500 and it works fine (after some Open Firmware
patches). But I get a kernel
panic using quik when I add my
Adaptec 2940U2W SCSI card to my machine. I've
compiled support for this card
into my kernel and yet it still panics.
Any sugges
t; device alias for cd: is wrong but it won't let me change it with nvalias??
> So I jump into handy dandy OF and do a:
>
> 0> boot ide1:,\install\powermac\yaboot
>
> I get the yaboot prompt. Then I do:
>
> boot: ide1:0,/install/powermac/vmlinux2.4
>
> Kernel
it with nvalias??
So I jump into handy dandy OF and do a:
0> boot ide1:,\install\powermac\yaboot
I get the yaboot prompt. Then I do:
boot: ide1:0,/install/powermac/vmlinux2.4
Kernel panic VFS blah blah. So I do:
boot: ide1:0,/install/powermac/vmlinux2.4 root=/dev/hdf ro (which is t
> The machine I use is a PowerBook G4 running at 867Mhz.
What model exactly ? (what do you have in /proc/cpuinfo ?) Also
what model of video chip do you have ?
> What I do in order to block the kernel is just to log in using XDM. The
> system hangs immediately. Or, when I have the XDM window, s
Mercoledì, 25 Giu 2003, alle 01:33 Europe/Rome, Benjamin Herrenschmidt
ha scritto:
On Tue, 2003-06-24 at 16:08, Giuseppe Sacco wrote:
Hi people,
lately I got many kernel panic using 2.4.21-ben1 kernel compiled with
gcc-3.3 and with gcc-2.95.
The message I get at the monitor prompt is
kernel
On Tue, 2003-06-24 at 16:08, Giuseppe Sacco wrote:
> Hi people,
> lately I got many kernel panic using 2.4.21-ben1 kernel compiled with
> gcc-3.3 and with gcc-2.95.
>
> The message I get at the monitor prompt is
>
> kernel bug at page_alloc.c:106!
> vector: 0 at pc=c00
Hi people,
lately I got many kernel panic using 2.4.21-ben1 kernel compiled with
gcc-3.3 and with gcc-2.95.
The message I get at the monitor prompt is
kernel bug at page_alloc.c:106!
vector: 0 at pc=c0034c64, lr=c0034c64
msr=9032, sp=dc5dfde0 [dc5dfd18]
current=dc5de000, pid=447, comm=XFree86
op to
> monitor the system load (the squid refresh is probably the most cpu
> intensive process that is run.) While top was running, I had a kernel
> panic. The syslog messages are appended below.
>
> This is the only crash in circa six months with this configuration.
> Do I have
t cpu
intensive process that is run.) While top was running, I had a kernel
panic. The syslog messages are appended below.
This is the only crash in circa six months with this configuration.
Do I have a problem? Where else should I look? I am a relative newbie
with linux, and admit that the s
On Sun, Nov 03, 2002 at 11:20:35AM -0800, Johan en Katrien Dewaele wrote:
> Hi,
> > > > > I acquired this old Mac PPC 4400/200
...
> One thing I noticed and find very strange: when I zap
> the PRAM (alt-cmd P R) I almost immediatly get the
> white screen with the arrow and then the Mac searche
Hi,
> > > > I acquired this old Mac PPC 4400/200
> > When boot-floppy boots I get a nice screenoutput
> with
> > the penguin on top : kernel detects following
> (dmesg
> > output) :
> >
> > MacOs display is /bandit/ATY,264VT
> > Using unsupported 640x480 ATY,264VT at 81800480,
> > depth=8, pitch=
On Tue, Oct 29, 2002 at 12:57:51PM -0800, Johan en Katrien Dewaele wrote:
> Hi again,
>
> --- Chris Tillman <[EMAIL PROTECTED]> wrote:
> > On Sat, Oct 26, 2002 at 04:56:56AM -0700, Johan en
> > Katrien Dewaele wrote:
> > > Hi people,
> > > I need your help/advice on this one : I'm a newbie
> > in
acquired this old Mac PPC 4400/200
> > wants to mount root fs I get following error :
> > Kernel panic: VFS: Unable to mount root fs on
> 03:40.
> > Rebooting in 180 seconds.
> >
> Thanks for applying all the wisdom available in the
> manual and so on
> before
nux.bin in the
> BootX-kernel-map, choose /dev/hdb2 as root-device and
> choose Linux as OS.
>
> So when I now try to boot using this
> BootX-configuration: kernel boots, the 2 HD + CD are
> detected, partition check goes ok but when the kernel
> wants to mount root fs I get fo
the kernel
wants to mount root fs I get following error :
Kernel panic: VFS: Unable to mount root fs on 03:40.
Rebooting in 180 seconds.
I relaunched the installer with the floppies and here
I CAN mount /dev/hdb2 on /target.
What am I missing? Are there any other kernel
parameters I should add ?
I
On Mon, Sep 23, 2002 at 10:10:27AM +0200, Patrik Nyman wrote:
> Thu, 19 Sep 2002 19:47:06 -0700, Cris Tillman wrote:
>
> >On Thu, Sep 19, 2002 at 10:09:56AM +0200, Patrik Nyman wrote:
> >> I also tried running the installer from the ramdisk, and then I
> >> realized, that not only does it not find
Thu, 19 Sep 2002 19:47:06 -0700, Cris Tillman wrote:
On Thu, Sep 19, 2002 at 10:09:56AM +0200, Patrik Nyman wrote:
> I also tried running the installer from the ramdisk, and then I
> realized, that not only does it not find the root partition, it does
> not find the hard drive at all! When insta
On Thu, Sep 19, 2002 at 10:09:56AM +0200, Patrik Nyman wrote:
> I also tried running the installer from the ramdisk, and then I
> realized, that not only does it not find the root partition, it does
> not find the hard drive at all! When installing from floppies, there's
> no problem.
>
> So,
in the installation manual:
put a folder "Linux Kernels" in the MacOS system folder, with linux.bin and
ramdisk.image.gz in it. I told BootX that the root is in /dev/hda8.
But, on booting I get:
request_module[block-major.3]: Root fs not mounted.
VFS: cannot open root device 03:08.
Kernel p
I got two replies to my posting, I'll answer them both here, hope
it's not confusing.
On Mon, 16 Sep 2002 07:59:42 -0700 Chris Tillman wrote:
you un-checked the root ramdisk checkbox
Yes.
and added "root=/dev/hda8" to the boot arguments box, right?
Well, there is a special box for naming
hat mean your kernel doesn't inlcude a driver for
IDE (major 3)? What kernel are you trying to boot?
Can you try and boot that same kernel from BootX with a ramdisk, and
once it's running, do a 'cat /proc/devices'?
> VFS: cannot open root device 03:08.
> Kernel
anual:
> put a folder "Linux Kernels" in the MacOS system folder, with linux.bin and
> ramdisk.image.gz in it. I told BootX that the root is in /dev/hda8.
> But, on booting I get:
>
> request_module[block-major.3]: Root fs not mounted.
> VFS: cannot open root d
1 - 100 of 162 matches
Mail list logo
