alent to the magic
sysrq key combo.
https://tldp.org/HOWTO/Remote-Serial-Console-HOWTO/security-sysrq.html
With ipmitool break is sent by typing ~B
https://linux.die.net/man/1/ipmitool
Thanks
Michal
ort of monitoring for capturing the
> output
> of the serial console non-interactively? This way I would be able to capture
> the
> crash besides what I have seen above.
I am pretty sure you can run something like
script ipmitool
to capture output indefinitely, and the same inside screen on a remote
machine.
Thanks
Michal
>> - boot into open firmware,
>> - type 'boot hd:2,yaboot'
>>(changing the number to the # of your boot partition)
> it stays on Waiting for root file system for a few minutes and then
> tells me /dev/sdb4 does not exist and brings be to a initramfs shell
I don't know the answer, but I'm wo
> I mailed this list a couple weeks ago about yaboot returning to a grey
> screen when I try to boot both OS X and Linux. Well, the problem is
> still there and I have been trying to fix it for a long time now.
I have what looks like the same problem for a long time too. While I
would love to
relevant. If they
> aren't, then please let me know. I would also appreciate if I were
> kept on carbon copies as I am only subscribed to debian-powerpc at the
> moment.
>
>
> Regards, Rogério Brito.
>
> P.S.: It unfortunately doesn't matter if I switch to a console or if I
> am in X when I press the power button with recent kernels.
> -
Regards,
Michal
--
LOG
http://www.stardust.webpages.pl/log/
PROTECTED],0 partition=2
when I run only rescue64, rescue mode auto starts which I don't want and
there is also not possible select install any additional packege (kernel
package)
Thanks a lot for any help!
Michal
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "u
> -m64
ok, that failed, with the output below. For the record, here are the
steps I took:
1. first it complained with this:
e2011# gcc -Wall -m64 -g -o mouseemu mouseemu.c
/usr/bin/ld: skipping incompatible
/usr/lib/gcc/powerpc-linux-gnu/4.0.3/libgcc_s.so when searching for -lgcc_s
/usr
ates
the same error ("ioctl UI_SET_KEYBIT: Invalid argument").
Are there any flags or options to pass in order to build it 64bit?
Hints or pointers to RTFM would be appreicated!
Thanks,
Michal
---
Here is an extract of the output of apt-build:
/usr/bin/make
make[1]: Entering di
l version, and where did the
> source come from?
The kernel is the one found in unstable as of today, ie
linux-image-2.6.14-2-powerpc64:
$ uname -a
Linux e2011 2.6.14-2-powerpc64 #1 SMP Wed Nov 16 02:17:10 UTC 2005 ppc64
GNU/Linux
thanks,
Michal
--
To UNSUBSCRIBE, email to [EMAIL P
Does anyone else have problems when trying to use mouseemu on 2.6.14?
(I have googled this and browsed the bug reports, but found nothing).
On a PowerMac 7,2 running unstable, I get:
$ /etc/init.d/mouseemu restart
ioctl32(mouseemu:2395): Unknown cmd fd(5) cmd(80045564){00} arg(0001) on
way of doing it?
Thanks!
Michal
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Does anyone know of any progress on the issue of getting sound working
on the G5?
Benjamin Herrenschmidt wrote:
> All of the details can be found in the darwin drivers, they are open
> source.
I would be glad to spend some time on this, if I knew even where to
start :(
Michal
>> First off, I have a dual 1.8 GHz G5.
> Then it's the entry-level model of the new product line. That
> explains a lot. There may be a whole lot of pitfalls lurking in
> there,
I have a dual 1.8G G5 too, but I get the behaviour described by Jens:
it boots but hangs around floppy detection (
(Creating a symbolic link from
some other ata drivers to ata_k2 makes the package install, but hangs
on boot immediately).
Any ideas?
Michal
> Fill a bug report against debian-installer with this info for start,
> so it gets fixed.
ok, done.
Here's hoping for a fix, as otherwise I'm sitting on a useless
dual G5...
Michal
orted out.
Any advice on how to install Debian on such a machine?
thanks, Michal
I compiled the previous prerelease. I deleted it later. The only thing I
found is that when compiling the mozilla component you have to add
IIRC -fno-rtti and -fno-exceptions to the CFLAGS.
Mike
On Thu, 8 Feb 2001, Phil Fraering wrote:
> Hi. I thought I'd toss a feeler out, see if anyone
> has
type
vmlinux-2.4.0 root=/dev/hda10
you may need something like
hd:9,vmlinux-2.4.0 root=/dev/hda10
replace the 9 with wherever the image is
On Sun, 28 Jan 2001, Gerhard Reuteler wrote:
> Hi,
> I want to compile the kernel 2.4.0 for my pismo. To test the new kernel
> without changing the yaboot.c
18 matches
Mail list logo
