* Re: [parisc-linux] compiling kernels with gcc-3.1
From: Randolph Chung @ 2002-07-12 15:01 UTC (permalink / raw)
To: joel.soete; +Cc: parisc-linux
In-Reply-To: <1026467388.3d2ea63c0ac65@webmail.tiscalinet.be>
> PS: Can you do a telnet or an ssh connection when this kernel is running? IIRC
> as well as gcc-3.1 as gcc-3.2, I always reach well to build and boot kernels
> (without kdb) but the system crashes as soon as you try to connect it via the
> network.
yes, i can ssh into the box.
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
^ permalink raw reply
* Re: [parisc-linux] XFree86 on STI 819/K210
From: Helge Deller @ 2002-07-12 15:00 UTC (permalink / raw)
To: Stephan Trajkoff; +Cc: parisc-linux
In-Reply-To: <200207121244.OAA16127@smtpde02.sap-ag.de>
Hi Stepham
CC'ed to the list...
1. Yes:
ii xfree86-common 4.1.0-17 X Window System (XFree86) infrastructure
ii xserver-xfree8 4.1.0-17 the XFree86 X server
2. Did you checheck the "Mode"- line ?
What does "dmesg | grep stifb" says ?
Helge
On Friday 12 July 2002 14:39, Stephan Trajkoff wrote:
> I get the same error again,
> can I run XFRee with only installed xserver-common and
> xserver-xfree86?
>
> -------- Original Message --------
>
> ==> From: Helge Deller <helge.deller@sap.com>
> ==> Date: Fri, 12 Jul 2002 14:10:49 0200
>
> On Friday 12 July 2002 14:06, Stephan Trajkoff wrote: > do anyone
> runs XFREE86 on STI? I have K210/819 HP > the error is
> FBIOPUT_VSCREENINFO: invalid argument > can anyone send me
> configuration file for X with STI working...?
>
> I think you should check the screen resolutions in your XF86Config-4.
>
> ftp://ftp.parisc-linux.org/XFree86/XF86Config-4 is one example and
> you should change it to have the correct Modelines as described at
> the top in this file.
>
> Greetings, Helge
^ permalink raw reply
* Re: [parisc-linux] Problem building gcc-3.2 (cvs head) on hppa-linux
From: John David Anglin @ 2002-07-12 13:44 UTC (permalink / raw)
To: randolph; +Cc: gcc, parisc-linux
In-Reply-To: <20020712072703.GA8838@tausq.org>
> Trying to build CVS head (3.2 20020711) with:
>
> configure --host=hppa-linux --build=hppa-linux --target=hppa64-linux
> --enable-shared --disable-nls --enable-languages=c
>
> I get:
>
> /home/tausq/build/gcc-3.2/gcc/xgcc -B/home/tausq/build/gcc-3.2/gcc/ -B/home/tausq/opt/gnu/hppa64-linux/bin/ -B/home/tausq/opt/gnu/hppa64-linux/lib/ -isystem /home/tausq/opt/gnu/hppa64-linux/include -O2 -DIN_GCC -DCROSS_COMPILE -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include -fPIC -Dpa64=1 -DELF=1 -g -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I.
> -I. -I/home/tausq/src/gcc-3.2/gcc -I/home/tausq/src/gcc-3.2/gcc/. -I/home/tausq/src/gcc-3.2/gcc/config -I/home/tausq/src/gcc-3.2/gcc/../include -DL__gcc_bcmp -c /home/tausq/src/gcc-3.2/gcc/libgcc2.c -o libgcc/./__gcc_bcmp.o
> /home/tausq/src/gcc-3.2/gcc/unwind-dw2.c: In function `uw_frame_state_for':
> /home/tausq/src/gcc-3.2/gcc/unwind-dw2.c:906: warning: implicit declaration of function `memset'
> /home/tausq/src/gcc-3.2/gcc/unwind-dw2.c: In function `uw_install_context_1':
> /home/tausq/src/gcc-3.2/gcc/unwind-dw2.c:1193: warning: implicit declaration of
> function `memcpy'
> In file included from /home/tausq/src/gcc-3.2/gcc/unwind-dw2.c:1210:
> /home/tausq/src/gcc-3.2/gcc/unwind.inc: In function `_Unwind_RaiseException':
> /home/tausq/src/gcc-3.2/gcc/unwind.inc:132: error: Attempt to delete prologue/epilogue insn:
> (insn 337 336 338 14 (nil) (set (reg:DI 7 %r7)
> (mem:DI (plus:DI (reg/f:DI 30 %r30)
> (const_int -296 [0xfffffffffffffed8])) [0 S8 A64])) -1 (nil)
> (nil))
> /home/tausq/src/gcc-3.2/gcc/unwind.inc:132: internal compiler error: Internal compiler error in propagate_one_insn, at flow.c:1637
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
> make[2]: *** [libgcc/./unwind-dw2.o] Error 1
> make[2]: Leaving directory `/home/tausq/build/gcc-3.2/gcc'
> make[1]: *** [libgcc.a] Error 2
> make[1]: Leaving directory `/home/tausq/build/gcc-3.2/gcc'
> make: *** [all-gcc] Error 2
>
> The bootstrapping compiler is gcc-3.0.4
Yes. This is one of the manifestations of the the long call bug
in 3.0.4. You need to use "-O2" in STAGE1_CFLAGS to work around
it or use gcc 3.1 later as a bootstrap compiler. You will have
the same problem if you try to rebuild 3.0.x. There is a silent
miscompilation of expr.c if I remember correctly.
Dave
--
J. David Anglin dave.anglin@nrc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6605)
^ permalink raw reply
* Re: [parisc-linux] Problem building gcc-3.2 (cvs head) on hppa-linux
From: John David Anglin @ 2002-07-12 13:44 UTC (permalink / raw)
To: randolph; +Cc: gcc, parisc-linux
In-Reply-To: <20020712072703.GA8838@tausq.org>
> Trying to build CVS head (3.2 20020711) with:
>
> configure --host=hppa-linux --build=hppa-linux --target=hppa64-linux
> --enable-shared --disable-nls --enable-languages=c
>
> I get:
>
> /home/tausq/build/gcc-3.2/gcc/xgcc -B/home/tausq/build/gcc-3.2/gcc/ -B/home/tausq/opt/gnu/hppa64-linux/bin/ -B/home/tausq/opt/gnu/hppa64-linux/lib/ -isystem /home/tausq/opt/gnu/hppa64-linux/include -O2 -DIN_GCC -DCROSS_COMPILE -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include -fPIC -Dpa64=1 -DELF=1 -g -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I.
> -I. -I/home/tausq/src/gcc-3.2/gcc -I/home/tausq/src/gcc-3.2/gcc/. -I/home/tausq/src/gcc-3.2/gcc/config -I/home/tausq/src/gcc-3.2/gcc/../include -DL__gcc_bcmp -c /home/tausq/src/gcc-3.2/gcc/libgcc2.c -o libgcc/./__gcc_bcmp.o
> /home/tausq/src/gcc-3.2/gcc/unwind-dw2.c: In function `uw_frame_state_for':
> /home/tausq/src/gcc-3.2/gcc/unwind-dw2.c:906: warning: implicit declaration of function `memset'
> /home/tausq/src/gcc-3.2/gcc/unwind-dw2.c: In function `uw_install_context_1':
> /home/tausq/src/gcc-3.2/gcc/unwind-dw2.c:1193: warning: implicit declaration of
> function `memcpy'
> In file included from /home/tausq/src/gcc-3.2/gcc/unwind-dw2.c:1210:
> /home/tausq/src/gcc-3.2/gcc/unwind.inc: In function `_Unwind_RaiseException':
> /home/tausq/src/gcc-3.2/gcc/unwind.inc:132: error: Attempt to delete prologue/epilogue insn:
> (insn 337 336 338 14 (nil) (set (reg:DI 7 %r7)
> (mem:DI (plus:DI (reg/f:DI 30 %r30)
> (const_int -296 [0xfffffffffffffed8])) [0 S8 A64])) -1 (nil)
> (nil))
> /home/tausq/src/gcc-3.2/gcc/unwind.inc:132: internal compiler error: Internal compiler error in propagate_one_insn, at flow.c:1637
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
> make[2]: *** [libgcc/./unwind-dw2.o] Error 1
> make[2]: Leaving directory `/home/tausq/build/gcc-3.2/gcc'
> make[1]: *** [libgcc.a] Error 2
> make[1]: Leaving directory `/home/tausq/build/gcc-3.2/gcc'
> make: *** [all-gcc] Error 2
>
> The bootstrapping compiler is gcc-3.0.4
Yes. This is one of the manifestations of the the long call bug
in 3.0.4. You need to use "-O2" in STAGE1_CFLAGS to work around
it or use gcc 3.1 later as a bootstrap compiler. You will have
the same problem if you try to rebuild 3.0.x. There is a silent
miscompilation of expr.c if I remember correctly.
Dave
--
J. David Anglin dave.anglin@nrc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6605)
^ permalink raw reply
* Re: [parisc-linux] XFree86 on STI 819/K210
From: Helge Deller @ 2002-07-12 12:10 UTC (permalink / raw)
To: Stephan Trajkoff, parisc-linux
In-Reply-To: <20020712120458.2AAD3486D@dsl2.external.hp.com>
On Friday 12 July 2002 14:06, Stephan Trajkoff wrote:
> do anyone runs XFREE86 on STI? I have K210/819 HP
> the error is FBIOPUT_VSCREENINFO: invalid argument
> can anyone send me configuration file for X with STI working...?
I think you should check the screen resolutions in your XF86Config-4.
ftp://ftp.parisc-linux.org/XFree86/XF86Config-4 is one example
and you should change it to have the correct Modelines as described
at the top in this file.
Greetings,
Helge
^ permalink raw reply
* [parisc-linux] XFree86 on STI 819/K210
From: Stephan Trajkoff @ 2002-07-12 12:06 UTC (permalink / raw)
To: parisc-linux
do anyone runs XFREE86 on STI? I have K210/819 HP
the error is FBIOPUT_VSCREENINFO: invalid argument
can anyone send me configuration file for X with STI working...?
-------------------------------------------------------------------
-->> Add WEB ACCESS to your POP email accounts with
-->> FREE Perl CGI scripts! Download today! http://www.adjeweb.com
-------------------------------------------------------------------
^ permalink raw reply
* Re: [parisc-linux] compiling kernels with gcc-3.1
From: joel.soete @ 2002-07-12 9:49 UTC (permalink / raw)
To: Randolph Chung; +Cc: parisc-linux
In-Reply-To: <20020712073628.GB8838@tausq.org>
Hi Randolph,
I am on going to build mirroring on my test server.
But I will test it asap (as I already cvs update gcc-3.1.. ) and let you inform.
Thanks a lot for info,
Joel
PS: Can you do a telnet or an ssh connection when this kernel is running? IIRC
as well as gcc-3.1 as gcc-3.2, I always reach well to build and boot kernels
(without kdb) but the system crashes as soon as you try to connect it via the
network.
Quoting Randolph Chung <randolph@tausq.org>:
> I seem to recall some reports that you cannot build a working kernel
> with gcc-3.1....
>
> Well, maybe they've changed things upstream, but I just tried with
> gcc-3.1.1 (3.1.1 20020708 snapshot) and it seems to work well, at least
> with my limited testing... this is with the debian default 64-bit smp
> .config.
>
> I did have to hack up a bunch of code... it seems like gcc-3.1.1
> doesn't
> like this construct:
>
> typedef struct {
> volatile unsigned int __attribute__((aligned(16))) lock;
> } spinlock_t;
>
> typedef struct {
> spinlock_t lock;
> volatile unsigned int count;
> } rwlock_t;
>
> rwlock_t foo = (rwlock_t) { (spinlock_t) { 1 }, 0 };
>
> it complains that the initializer is not constant in this case.
> removing the (rwlock_t) cast fixed that....
>
> also it doesn't like it when you have a variable and you initialize it
> after declaration with the { (spinlock_t) { 1 }, 0 } stuff...
>
> (e.g.
> rwlock_t foo;
>
> foo = { (spinlock_t) { 1 }, 0 };
>
> gives a "parse error at {" message)
>
> after working through these problems i got a working kernel...
>
> randolph
> --
> Randolph Chung
> Debian GNU/Linux Developer, hppa/ia64 ports
> http://www.tausq.org/
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
>
-------------------------------------------------
This mail sent through Tiscali Webmail (http://webmail.tiscali.be)
^ permalink raw reply
* [parisc-linux] compiling kernels with gcc-3.1
From: Randolph Chung @ 2002-07-12 7:36 UTC (permalink / raw)
To: parisc-linux
I seem to recall some reports that you cannot build a working kernel
with gcc-3.1....
Well, maybe they've changed things upstream, but I just tried with
gcc-3.1.1 (3.1.1 20020708 snapshot) and it seems to work well, at least
with my limited testing... this is with the debian default 64-bit smp
.config.
I did have to hack up a bunch of code... it seems like gcc-3.1.1 doesn't
like this construct:
typedef struct {
volatile unsigned int __attribute__((aligned(16))) lock;
} spinlock_t;
typedef struct {
spinlock_t lock;
volatile unsigned int count;
} rwlock_t;
rwlock_t foo = (rwlock_t) { (spinlock_t) { 1 }, 0 };
it complains that the initializer is not constant in this case.
removing the (rwlock_t) cast fixed that....
also it doesn't like it when you have a variable and you initialize it
after declaration with the { (spinlock_t) { 1 }, 0 } stuff...
(e.g.
rwlock_t foo;
foo = { (spinlock_t) { 1 }, 0 };
gives a "parse error at {" message)
after working through these problems i got a working kernel...
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
^ permalink raw reply
* Re: [parisc-linux] x windows keybord problem on 715/33
From: Dimitris Zilaskos @ 2002-07-12 7:27 UTC (permalink / raw)
Cc: parisc-linux
In-Reply-To: <200207120235.11571.deller@gmx.de>
Thank you all guys for the tips , I will give them a try . And
congratulations to all those developing PA-Linux for their excellent
work.
Regards ,
--
=============================================================================
Dimitris Zilaskos
Department of Physics @ Aristotle Univercity of Thessaloniki , Greece
=============================================================================
^ permalink raw reply
* [parisc-linux] Problem building gcc-3.2 (cvs head) on hppa-linux
From: Randolph Chung @ 2002-07-12 7:27 UTC (permalink / raw)
To: gcc; +Cc: parisc-linux
Trying to build CVS head (3.2 20020711) with:
configure --host=hppa-linux --build=hppa-linux --target=hppa64-linux
--enable-shared --disable-nls --enable-languages=c
I get:
/home/tausq/build/gcc-3.2/gcc/xgcc -B/home/tausq/build/gcc-3.2/gcc/ -B/home/tausq/opt/gnu/hppa64-linux/bin/ -B/home/tausq/opt/gnu/hppa64-linux/lib/ -isystem /home/tausq/opt/gnu/hppa64-linux/include -O2 -DIN_GCC -DCROSS_COMPILE -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include -fPIC -Dpa64=1 -DELF=1 -g -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I.
-I. -I/home/tausq/src/gcc-3.2/gcc -I/home/tausq/src/gcc-3.2/gcc/. -I/home/tausq/src/gcc-3.2/gcc/config -I/home/tausq/src/gcc-3.2/gcc/../include -DL__gcc_bcmp -c /home/tausq/src/gcc-3.2/gcc/libgcc2.c -o libgcc/./__gcc_bcmp.o
/home/tausq/src/gcc-3.2/gcc/unwind-dw2.c: In function `uw_frame_state_for':
/home/tausq/src/gcc-3.2/gcc/unwind-dw2.c:906: warning: implicit declaration of function `memset'
/home/tausq/src/gcc-3.2/gcc/unwind-dw2.c: In function `uw_install_context_1':
/home/tausq/src/gcc-3.2/gcc/unwind-dw2.c:1193: warning: implicit declaration of
function `memcpy'
In file included from /home/tausq/src/gcc-3.2/gcc/unwind-dw2.c:1210:
/home/tausq/src/gcc-3.2/gcc/unwind.inc: In function `_Unwind_RaiseException':
/home/tausq/src/gcc-3.2/gcc/unwind.inc:132: error: Attempt to delete prologue/epilogue insn:
(insn 337 336 338 14 (nil) (set (reg:DI 7 %r7)
(mem:DI (plus:DI (reg/f:DI 30 %r30)
(const_int -296 [0xfffffffffffffed8])) [0 S8 A64])) -1 (nil)
(nil))
/home/tausq/src/gcc-3.2/gcc/unwind.inc:132: internal compiler error: Internal compiler error in propagate_one_insn, at flow.c:1637
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
make[2]: *** [libgcc/./unwind-dw2.o] Error 1
make[2]: Leaving directory `/home/tausq/build/gcc-3.2/gcc'
make[1]: *** [libgcc.a] Error 2
make[1]: Leaving directory `/home/tausq/build/gcc-3.2/gcc'
make: *** [all-gcc] Error 2
The bootstrapping compiler is gcc-3.0.4
any ideas?
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
^ permalink raw reply
* [parisc-linux] Problem building gcc-3.2 (cvs head) on hppa-linux
From: Randolph Chung @ 2002-07-12 7:27 UTC (permalink / raw)
To: gcc; +Cc: parisc-linux
Trying to build CVS head (3.2 20020711) with:
configure --host=hppa-linux --build=hppa-linux --target=hppa64-linux
--enable-shared --disable-nls --enable-languages=c
I get:
/home/tausq/build/gcc-3.2/gcc/xgcc -B/home/tausq/build/gcc-3.2/gcc/ -B/home/tausq/opt/gnu/hppa64-linux/bin/ -B/home/tausq/opt/gnu/hppa64-linux/lib/ -isystem /home/tausq/opt/gnu/hppa64-linux/include -O2 -DIN_GCC -DCROSS_COMPILE -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include -fPIC -Dpa64=1 -DELF=1 -g -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I.
-I. -I/home/tausq/src/gcc-3.2/gcc -I/home/tausq/src/gcc-3.2/gcc/. -I/home/tausq/src/gcc-3.2/gcc/config -I/home/tausq/src/gcc-3.2/gcc/../include -DL__gcc_bcmp -c /home/tausq/src/gcc-3.2/gcc/libgcc2.c -o libgcc/./__gcc_bcmp.o
/home/tausq/src/gcc-3.2/gcc/unwind-dw2.c: In function `uw_frame_state_for':
/home/tausq/src/gcc-3.2/gcc/unwind-dw2.c:906: warning: implicit declaration of function `memset'
/home/tausq/src/gcc-3.2/gcc/unwind-dw2.c: In function `uw_install_context_1':
/home/tausq/src/gcc-3.2/gcc/unwind-dw2.c:1193: warning: implicit declaration of
function `memcpy'
In file included from /home/tausq/src/gcc-3.2/gcc/unwind-dw2.c:1210:
/home/tausq/src/gcc-3.2/gcc/unwind.inc: In function `_Unwind_RaiseException':
/home/tausq/src/gcc-3.2/gcc/unwind.inc:132: error: Attempt to delete prologue/epilogue insn:
(insn 337 336 338 14 (nil) (set (reg:DI 7 %r7)
(mem:DI (plus:DI (reg/f:DI 30 %r30)
(const_int -296 [0xfffffffffffffed8])) [0 S8 A64])) -1 (nil)
(nil))
/home/tausq/src/gcc-3.2/gcc/unwind.inc:132: internal compiler error: Internal compiler error in propagate_one_insn, at flow.c:1637
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
make[2]: *** [libgcc/./unwind-dw2.o] Error 1
make[2]: Leaving directory `/home/tausq/build/gcc-3.2/gcc'
make[1]: *** [libgcc.a] Error 2
make[1]: Leaving directory `/home/tausq/build/gcc-3.2/gcc'
make: *** [all-gcc] Error 2
The bootstrapping compiler is gcc-3.0.4
any ideas?
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
^ permalink raw reply
* Re: [parisc-linux] x windows keybord problem on 715/33
From: Helge Deller @ 2002-07-12 0:36 UTC (permalink / raw)
To: Dimitris Zilaskos, parisc-linux
In-Reply-To: <Pine.LNX.4.44.0207111849360.32161-100000@tassadar.physics.auth.gr>
Hi Dimitris,
please read ftp://ftp.parisc-linux.org/XFree86/HILkeyb/README
In any case I would suggest you update to a newer kernel.
HIL mice are now supported, and you won't have any bigger problems
on the console or under X. Just be sure to create the /dev/input/*
device nodes as described in the FAQ entry no. 12 at
http://www.parisc-linux.org/faq/index.html
The 100% cpu usage for softirqd is a known problem, but
it's just cosmetics and will not slower your machine.
I think we will fix this buglet in the future.
Greetings,
Helge
On Thursday 11 July 2002 17:50, Dimitris Zilaskos wrote:
> Hello ,
>
> I am trying to setup X windows in an 715/33 . I can start various Windows
> managers like wdm and xdm , but i cant get keys 'i' and 'o' to work (
> they work ok in console ).All other keys work ok .
>
> I have the following lines in the XF86Config
>
> Option "XkbdRules" "xfree86"
> Option "XkbModel" "hphil"
>
>
> and in my /etc/X11/xkb/rules/xfree86:
> hp = xfree86 pc(pc104)
> hphil = hp(hil) hp(hil)
>
> I am running 2.4.18-pa41 . Newer kernels till 54 either freeze my
> keyboard or have ksoftirqd consume 100% cpu ( or both) . I am using a
> serial mouse for X . It works most of the time but sometines the pointer
> stops moving untill I press a key . Work ok under console though .
>
> Any advice how to make 'o' and 'i' work ?
>
> Regards ,
> --
> ===========================================================================
>==
>
> Dimitris Zilaskos
>
> Department of Physics @ Aristotle Univercity of Thessaloniki , Greece
> ===========================================================================
>==
>
>
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
^ permalink raw reply
* Re: [parisc-linux] x windows keybord problem on 715/33
From: Andreas Seltenreich @ 2002-07-12 0:02 UTC (permalink / raw)
To: parisc-linux
In-Reply-To: <Pine.LNX.4.44.0207111849360.32161-100000@tassadar.physics.auth.gr>
Hallo Dimitris,
* Dimitris Zilaskos <dzila@tassadar.physics.auth.gr> [2002-07-11 17:51]:
> I am trying to setup X windows in an 715/33 . I can start various Windows
> managers like wdm and xdm , but i cant get keys 'i' and 'o' to work (
> they work ok in console ).All other keys work ok .
I had the same symptoms with a german ps2 keyboard on a 712, just with other
keys beeing dead (<, > and |).
xev showed that X is getting keycodes from those keys, but they were
not alligned.
I changed the keycodes in /etc/X11/xkb/keycodes/xfree86 according to the
ones xev reported. I guess in your case you would have to change them to:
<AD08> = code reported for i
<AD09> = code reported for o
Could also be that the cause for your dead keys is another
and this hint totally useless.
regards,
andreas
^ permalink raw reply
* Re: [parisc-linux] Not working PHP, security hole
From: Randolph Chung @ 2002-07-11 20:24 UTC (permalink / raw)
To: Stephan Trajkoff; +Cc: parisc-linux
In-Reply-To: <20020711194810.2007D485F@dsl2.external.hp.com>
In reference to a message from Stephan Trajkoff, dated Jul 11:
> Please admins of parisc-linux to fix their problem
thanks for posting the passwords to the mailing list :-/
the admins are fixing things now.
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
^ permalink raw reply
* Re: [parisc-linux] Not working PHP, security hole
From: Matt Taggart @ 2002-07-11 20:18 UTC (permalink / raw)
To: Stephan Trajkoff; +Cc: parisc-linux
In-Reply-To: <20020711194810.2007D485F@dsl2.external.hp.com>
"Stephan Trajkoff" writes...
> Please admins of parisc-linux to fix their problem
We're upgrading it today. It will be fixed shortly.
--
Matt Taggart Linux Development Lab
taggart@fc.hp.com HP Linux Systems Operation
^ permalink raw reply
* [parisc-linux] Not working PHP, security hole
From: Stephan Trajkoff @ 2002-07-11 19:49 UTC (permalink / raw)
To: parisc-linux
Please admins of parisc-linux to fix their problem
<?
$_db_host=3D"localhost";
#$_db_host=3D"puffin.external.hp.com";
$_db_user=3D"parisc";
$_db_password=3D"parisc";
$_db_database=3D"hw";
$_db_connection=3D"_db_unconnected";
$_db_result=3D"";
$_db_row=3D"";
Function connectDatabase(){
global $_db_host;
global $_db_user;
global $_db_password;
global $_db_connection;
if($_db_connection=3D=3D"_db_unconnected"){
$_db_connection=3Dmysql_connect
($_db_host,$_db_user,$_db_password);
}
}
Function queryDatabase($query){
global $_db_database;
global $_db_result;
$_db_result =3D mysql_db_query($_db_database,$query);
return $_db_result;
}
Function nextRow($result =3D "_db_unset"){
global $_db_result;
global $_db_row;
if($result=3D=3D"_db_unset"){
$_db_row =3D mysql_fetch_object($_db_result);
}
elseif(is_integer($result)){
$_db_row =3D mysql_fetch_object($result);
}
else {
return "";
}
return $_db_row;
}
Function numRows($result =3D "_db_unset"){
global $_db_result;
if($result=3D=3D"_db_unset"){
return mysql_num_rows($_db_result);
}
elseif(is_integer($result)){
return mysql_num_rows($result);
}
return "";
}
Function disconnectDatabase(){
global $_db_result;
global $_db_connection;
mysql_free_result($_db_result);
mysql_close($_db_connection);
}
Function insertId(){
return mysql_insert_id();
}
Function escapeString($instring){
return AddSlashes($instring);
}
?>
use apachetoolbox to compile apache php mysql
www.apachetoolbox.com
-------------------------------------------------------------------
-->> Add WEB ACCESS to your POP email accounts with
-->> FREE Perl CGI scripts! Download today! http://www.adjeweb.com
-------------------------------------------------------------------
^ permalink raw reply
* RE: [parisc-linux] L2000 stable with SMP and RAID
From: joel.soete @ 2002-07-11 16:25 UTC (permalink / raw)
To: James Braid; +Cc: 'Joel Soete', parisc-linux
In-Reply-To: <005801c22780$93f57770$5e01000a@bongo>
Hi James,
Quoting James Braid <james.braid@peace.com>:
> > For my part I would like to test RAID-1 on my B180 (2 of 9Gb).
> > Could you let me know more on the RAID configuration you implemented?
> > Do you have a special slice (partition) for your F0 (parisc
> > bootloader)
> > and may be also for /boot?
>
> My RAID config is just a 2-disk RAID-0 array for testing at the moment.
> Heres the raidtab (probably not a lot of use to you though):
>
> ----
>
> raiddev /dev/md0
> raid-level 0
> nr-raid-disks 2
> chunk-size 4
>
> device /dev/sdb1
> raid-disk 0
> device /dev/sdc1
> raid-disk 1
>
> ----
>
> Theres a RAID-1 root howto for Debian which I have used in the past
> here: http://www.james.rcpt.to/programs/debian/raid1/
>
Thanks to this, I build on my second disk
sdb1 (a F0 slice of about 16Mb)
sdb2 swap (128Mb == Physical memory size)
sdb3 /boot (about 64Mb to be able to test severall kernels)
sdb5 => md0 / (about 1.5 Gb)
modify fstab to replace my boot device by /dev/md0;
modify palo.conf to make this disk bootable and find its kernel into /boot
partition and that works.
I just now have to complete the raidtab configuration and recover the rest of my
own slices than finaly fully rebuild md in non degraded mode and a small script
to duplicate F0 and boot slices (not yet supported as md AFAIK).
Many thanks again for your help,
Joel
-------------------------------------------------
This mail sent through Tiscali Webmail (http://webmail.tiscali.be)
^ permalink raw reply
* [parisc-linux] x windows keybord problem on 715/33
From: Dimitris Zilaskos @ 2002-07-11 15:50 UTC (permalink / raw)
To: parisc-linux
Hello ,
I am trying to setup X windows in an 715/33 . I can start various Windows
managers like wdm and xdm , but i cant get keys 'i' and 'o' to work (
they work ok in console ).All other keys work ok .
I have the following lines in the XF86Config
Option "XkbdRules" "xfree86"
Option "XkbModel" "hphil"
and in my /etc/X11/xkb/rules/xfree86:
hp = xfree86 pc(pc104)
hphil = hp(hil) hp(hil)
I am running 2.4.18-pa41 . Newer kernels till 54 either freeze my
keyboard or have ksoftirqd consume 100% cpu ( or both) . I am using a
serial mouse for X . It works most of the time but sometines the pointer
stops moving untill I press a key . Work ok under console though .
Any advice how to make 'o' and 'i' work ?
Regards ,
--
=============================================================================
Dimitris Zilaskos
Department of Physics @ Aristotle Univercity of Thessaloniki , Greece
=============================================================================
^ permalink raw reply
* Re: [parisc-linux] O_DIRECT on devices
From: Patrick Caulfield @ 2002-07-11 9:35 UTC (permalink / raw)
To: Rodolfo Baselli; +Cc: parisc-linux
In-Reply-To: <3D2D4B4B.4010705@deaprofessionale.it>
On Thu, Jul 11, 2002 at 11:09:31AM +0200, Rodolfo Baselli wrote:
> Patrick Caulfield wrote:
> >I'm currently working on LVM2 and we want to use O_DIRECT to write the
> >metadata
> >from userspace. so I open a partition with O_DIRECT and try to read/write
> >the
> >data from an aligned buffer.
>
> Hmmm, so is LVM ready for HP PA-RISC Linux? WOW!
LVM2 works fine - I use it all the time on my HP and Alpha boxes. O_DIRECT is an
optimisation I would like to have in there though cos it avoids a lot of
buffer-cache nastiness when clustering (yes, I'm working on that too but that
bit won't be GPLed)
> By the way, I'm reading right now "The catcher in the rye" by J.D.
> Salinger, and as I glanced at your 2nd name I felt like I was still
> reading the book! :-)))
:-)
If you were a pop-art expert you might have got even more deja-vu !
http://www.postershop.com/Caulfield-Patrick/Caulfield-Patrick-After-Lunch-2405657.html
I blame my parents...
patrick
^ permalink raw reply
* [parisc-linux] O_DIRECT on devices
From: Patrick Caulfield @ 2002-07-11 8:22 UTC (permalink / raw)
To: parisc-linux
I'm currently working on LVM2 and we want to use O_DIRECT to write the metadata
from userspace. so I open a partition with O_DIRECT and try to read/write the
data from an aligned buffer.
This works fine on Alpha & Intel but seems very unreliable on parisc for some
reason. Sometimes it works, sometimes it oopses "do_page_fault() pid=2120
command='lvm' type=15 address=0x00000001" and sometimes I just get back the
wrong information (at least LVM thinks its wrong I haven't check in detail just
what is up with it).
I haven't tried writing yet - I'd rather not think what might happen to my disk
just ATM :)
This is a C110 with 256meg of memory running 2.4.18-pa46
patrick
^ permalink raw reply
* RE: [parisc-linux] L2000 stable with SMP and RAID
From: joel.soete @ 2002-07-11 6:15 UTC (permalink / raw)
To: James Braid; +Cc: 'Joel Soete', parisc-linux
In-Reply-To: <005801c22780$93f57770$5e01000a@bongo>
Quoting James Braid <james.braid@peace.com>:
> > For my part I would like to test RAID-1 on my B180 (2 of 9Gb).
> > Could you let me know more on the RAID configuration you implemented?
> > Do you have a special slice (partition) for your F0 (parisc
> > bootloader)
> > and may be also for /boot?
>
> My RAID config is just a 2-disk RAID-0 array for testing at the moment.
> Heres the raidtab (probably not a lot of use to you though):
>
> ----
>
> raiddev /dev/md0
> raid-level 0
> nr-raid-disks 2
> chunk-size 4
>
> device /dev/sdb1
> raid-disk 0
> device /dev/sdc1
> raid-disk 1
>
> ----
>
> Theres a RAID-1 root howto for Debian which I have used in the past
> here: http://www.james.rcpt.to/programs/debian/raid1/
>
Very interesting.
Many thanks,
Joel
-------------------------------------------------
This mail sent through Tiscali Webmail (http://webmail.tiscali.be)
^ permalink raw reply
* Re: [parisc-linux] SMP (in)stability
From: Jeremy Drake @ 2002-07-10 20:34 UTC (permalink / raw)
To: Grant Grundler; +Cc: parisc-linux
In-Reply-To: <Pine.LNX.4.44.0207100032050.19290-100000@garibaldi.apptechsys.com>
On Wed, 10 Jul 2002, Jeremy Drake wrote:
> I will look at the tgz and also cvs update tomorrow when I get in the same
> building with the box, and send uname -a and .config, and also any
> observations I can make of the box when I get to it (any messages on the
> LCD, any ser pim output that it may have, any log messages)... Next time
> I'll leave a serial console open to it :)
The LCD screen reads "OFF 0000:". This is a new one for me :)
uname -a says "Linux krakatoa 2.4.18-pa53 #1 SMP Tue Jul 9 14:38:41 PDT
2002 parisc unknown"
The last smp kernel to work is:
krakatoa:~# dpkg-deb -I kernel-image-2.4.17-32-smp_23.1_hppa.deb
new debian package, version 2.0.
size 2945664 bytes: control archive= 19355 bytes.
836 bytes, 20 lines control
52806 bytes, 1626 lines * postinst #!/usr/bin/perl
8679 bytes, 226 lines * postrm #!/usr/bin/perl
8595 bytes, 219 lines * preinst #!/usr/bin/perl
6591 bytes, 211 lines * prerm #!/usr/bin/perl
Package: kernel-image-2.4.17-32-smp
Version: 23.1
Section: base
Priority: optional
Architecture: hppa
Depends: initrd-tools (>= 0.1.6), fileutils (>= 4.0), modutils (>=
2.3.12)
Suggests: palo
Provides: kernel-image, kernel-image-2.4
Installed-Size: 8268
Maintainer: Bdale Garbee <bdale@gag.com>
Source: kernel-image-2.4.17-hppa
Description: 32 bit SMP Linux kernel image for version 2.4.17 on HPPA.
This package contains the 32 bit SMP Linux kernel image for version
2.4.17 on HPPA, the corresponding System.map file, and the modules built
by the packager. It also contains scripts that try to ensure that the
system is not left in a unbootable state after an update.
.
Kernel image packages are generally produced using kernel-package,
and it is suggested that you install that package if you wish to
create a custom kernel.
The log just stops and picks up again when I rebooted.
You can get the .deb for the smp kernel that I build from
http://linux.apptechsys.com/~jeremyd/kernel-image-2.4.18-pa53_jeremyd.200207091430.smp_hppa.deb
Here's the output of ser pim for the one that has the right date/time
stamp. Looks like another "runway broad error" -- broad seems to be short
for broadcast.
----------------- Processor 1 HPMC Information ------------------
Timestamp =
Tue Jul 9 22:21:13 GMT 2002 (20:02:07:09:22:21:13)
HPMC Chassis Codes = 2cbf0 25108 2cbfb
General Registers 0 - 31
00-03 0000000000000000 000000001034cf20 000000001010090c
0000000000000000
04-07 0000000000354000 00000000f0400008 00000000000000fa
00000000f0002f68
08-11 0000000000000000 0000000000000000 000000000004000e
0000000010393408
12-15 00000000000000f2 0000000000000001 0000000000000001
00000000000000f3
16-19 0000000002020202 0000000000000002 00000000f000016c
000000001117c000
20-23 0000000000000000 00000000103262a0 0000000010347804
0000000000000000
24-27 00000000103478e0 0000000000000032 0000000000000019
0000000010326010
28-31 0000000000000000 0000000000000010 000000001117c6c0
00000000103478e0
Control Registers 0 - 31
00-03 0000000000000000 0000000000000000 0000000000000000
0000000000000000
04-07 0000000000000000 0000000000000000 0000000000000000
0000000000000000
08-11 0000000000000114 0000000000000000 00000000000000c0
000000000000001e
12-15 0000000000000000 0000000000000000 0000000000106000
00000000ff000000
16-19 000005b532c52d74 0000000000000000 000000001010090c
0000000003c008b3
20-23 0000000000000000 0000000000000000 000000000006ff0f
0000000000000000
24-27 0000000000354000 000000001f778000 0000000000044021
00000000f0412000
28-31 0000000055555555 0000000055555555 000000001117c000
0000000011111111
Space Registers 0 - 7
00-03 00000000 0000008a 00000000 0000008a
04-07 00000000 00000000 00000000 00000000
IIA Space = 0x0000000000000000
IIA Offset = 0x0000000010100910
Check Type = 0x20000000
CPU State = 0x9e000004
Cache Check = 0x00000000
TLB Check = 0x00000000
Bus Check = 0x0030000d
Assists Check = 0x00000000
Assist State = 0x00000000
Path Info = 0x00000000
System Responder Address = 0xfffffffffffa2000
System Requestor Address = 0xfffffffffffa0000
Floating-Point Registers 0 - 31
00-03 0000001f00000000 0000000000000000 0000000000000000
0000000000000000
04-07 2ffba00000000001 000000011015fa10 1035305000000000
11174000103e8000
08-11 1035305000000002 ffffffff0000000a 10101fc000000000
103ffdb300000000
12-15 0000000010347810 1117469010148340 1034781010353640
11174000103e8000
16-19 2ffba00011174000 0000000000000002 000000001034b010
1034781010346810
20-23 1034701010347810 103478102ffba000 cccccccd51eb874f
0000000333333334
24-27 b38cf9b100000450 0000000600000000 0000000f102f46a8
2ffba005102f46b4
28-31 3031323334353637 38396162101485e8 6768696a6b6c6d6e
6f70717273747576
'9000/785 B,C,J Workstation Unarchitected (per-CPU)', rev 1, 140 bytes:
Check Summary = 0xcb81841000000000
Available Memory = 0x0000000020000000
CPU Diagnose Register 2 = 0x0201010000000004
CPU Status Register 0 = 0x3440c24000000000
CPU Status Register 1 = 0x8000000000000000
SADD LOG = 0x4800000000000000
Read Short LOG = 0xc1af00fffed30000
ERROR_STATUS = 0x0000000000100010
MEM_ADDR = 0x000001ff3fffffff
MEM_SYND = 0x0000000000000000
MEM_ADDR_CORR = 0x000001ff3fffffff
MEM_SYND_CORR = 0x0000000000000000
RUN_DATA_HIGH = 0x020008bc36a20000
RUN_DATA_LOW = 0xe840c002000014bc
RUN_CTRL = 0x0000005c00001658
RUN_ADDR = 0xc13ff0f0f0002b48
System Responder Path = 0x00ffffffffffffff
HPMC PIM Analysis Information:
Timestamp =
Tue Jul 9 22:21:13 GMT 2002 (20:02:07:09:22:21:13)
'9000/785 B,C,J Workstation HPMC PIM Analysis (per-CPU)', rev 0, 1304
bytes:
CPU 1 observed a Broadcast Error on the Runway Bus.
Memory/IO Controller Error Analysis Information:
The Memory/IO Controller only observed the Broadcast Error. It did not
log
any additional information about the HPMC.
----------------- Processor 1 LPMC Information ------------------
Check Type = 0x00000000
I/D Cache Parity Info = 0x00000000
Cache Check = 0x00000000
TLB Check = 0x00000000
Bus Check = 0x00000000
Assists Check = 0x00000000
Assist State = 0x00000000
Path Info = 0x00000000
System Responder Address = 0x0000000000000000
System Requestor Address = 0x0000000000000000
----------------- Processor 1 TOC Information -------------------
General Registers 0 - 31
00-03 0000000000000000 0000000000000000 0000000000000000
0000000000000000
04-07 0000000000000000 0000000000000000 0000000000000000
0000000000000000
08-11 0000000000000000 0000000000000000 0000000000000000
0000000000000000
12-15 0000000000000000 0000000000000000 0000000000000000
0000000000000000
16-19 0000000000000000 0000000000000000 0000000000000000
0000000000000000
20-23 0000000000000000 0000000000000000 0000000000000000
0000000000000000
24-27 0000000000000000 0000000000000000 0000000000000000
0000000000000000
28-31 0000000000000000 0000000000000000 0000000000000000
0000000000000000
<Press any key to continue (q to quit)>
Control Registers 0 - 31
00-03 0000000000000000 0000000000000000 0000000000000000
0000000000000000
04-07 0000000000000000 0000000000000000 0000000000000000
0000000000000000
08-11 0000000000000000 0000000000000000 0000000000000000
0000000000000000
12-15 0000000000000000 0000000000000000 0000000000000000
0000000000000000
16-19 0000000000000000 0000000000000000 0000000000000000
0000000000000000
20-23 0000000000000000 0000000000000000 0000000000000000
0000000000000000
24-27 0000000000000000 0000000000000000 0000000000000000
0000000000000000
28-31 0000000000000000 0000000000000000 0000000000000000
0000000000000000
Space Registers 0 - 7
00-03 00000000 00000000 00000000 00000000
04-07 00000000 00000000 00000000 00000000
IIA Space = 0x0000000000000000
IIA Offset = 0x0000000000000000
CPU State = 0x00000000
Memory Error Log Information:
Timestamp =
Tue Jul 9 22:21:13 GMT 2002 (20:02:07:09:22:21:13)
'9000/785 B,C,J Workstation Memory Error Log', rev 0, 64 bytes:
No memory errors logged
I/O Module Error Log Information:
Timestamp =
Tue Jul 9 22:21:13 GMT 2002 (20:02:07:09:22:21:13)
'9000/785 B,C,J Workstation IO Error Log', rev 0, 228 bytes:
Rope Word1 Word2 Word3
------ ------------ ------------
0 0x00000000 0x0e0cc009 0x00000000fed30048
1 0x00000000 0x1e0cc009 0x00000000fed32048
2 ---------- 0x2e0cc229 ------------------
3 ---------- 0x3e0cc009 ------------------
4 0x00000000 0x4e0cc009 0x00000000fed38048
5 ---------- 0x5e0cc009 ------------------
6 0x00000000 0x6e0cc009 0x00000000fed3c048
7 ---------- 0x7e0cc009 ------------------
>
> >
> > thanks,
> > grant
> >
> > _______________________________________________
> > parisc-linux mailing list
> > parisc-linux@lists.parisc-linux.org
> > http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
> >
>
>
--
NEW YORK-- Kraft Foods, Inc. announced today that its board of
directors unanimously rejected the $11 billion takeover bid by Philip
Morris and Co. A Kraft spokesman stated in a press conference that the
offer was rejected because the $90-per-share bid did not reflect the
true value of the company.
Wall Street insiders, however, tell quite a different story.
Apparently, the Kraft board of directors had all but signed the takeover
agreement when they learned of Philip Morris' marketing plans for one of
their major Middle East subsidiaries. To a person, the board voted to
reject the bid when they discovered that the tobacco giant intended to
reorganize Israeli Cheddar, Ltd., and name the new company Cheeses of Nazareth.
^ permalink raw reply
* Re: [parisc-linux] harmony driver on k210/819
From: Helge Deller @ 2002-07-10 19:57 UTC (permalink / raw)
To: Stephan Trajkoff, parisc-linux
In-Reply-To: <3D2BD8BE.7060409@itp.bg>
On Wednesday 10 July 2002 08:48, Stephan Trajkoff wrote:
> Hello, on kernel 2.4.18-pa52, i compiled harmony sound blaster
> in dmesg the sound blaster is detected
> but when I start mpg123 blahblah.mp3 the output is Illegal operation
Works for me. Have you tried updating mpg123 ?
pa64:~# dmesg | grep Harmony
Lasi Harmony Audio driver V0.9a, h/w id 20, rev. 0 at 0xf0104000, IRQ 82
pa64:~# uname -a
Linux pa64 2.4.18-pa53 #249 Tue Jul 9 21:27:22 CEST 2002 parisc unknown
pa64:~# dpkg -l mpg123
||/ Name Version Description
+++-======================-======================-============================================================
ii mpg123 0.59r-8 MPEG layer 1/2/3 audio player
Greetings,
Helge
^ permalink raw reply
* Re: [parisc-linux] SMP (in)stability
From: John David Anglin @ 2002-07-10 17:44 UTC (permalink / raw)
To: John David Anglin; +Cc: rhirst, grundler, varenet, parisc-linux
In-Reply-To: <200207101707.g6AH7xMS010810@hiauly1.hia.nrc.ca>
> > > -pa52 kernel panic'd at 22:07
> > > running gcc1 test in background
>
> In hacking gcc this morning trying to fix a bug in loading 64-bit
> constants, I seem to have achieved a state where the gcc build crashes
> gsyprf11 in a deterministic manner. It's gone down three times.
> It only takes a few seconds after the build starts for the machine
> to crash.
Moving the code to hpux11, this is the error that causes the crash:
stage1/xgcc -Bstage1/ -B/opt/gnu/hppa2.0w-hp-hpux11.11/bin/ -c -DIN_GCC -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long -DHAVE_CONFIG_H -I. -I. -I../../gcc/gcc -I../../gcc/gcc/. -I../../gcc/gcc/config -I../../gcc/gcc/../include ../../gcc/gcc/cfgbuil
d.c -o cfgbuild.o
Pi 16528 received a SIGSEGV for stck growth ailure.
Possible caues: insufficient memory or swap space,
or stack size exceeded maxssiz.
xgcc: Internal error: Segmentation fault (program cc1)
Dave
--
J. David Anglin dave.anglin@nrc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6605)
^ permalink raw reply
* Re: [parisc-linux] SMP (in)stability
From: John David Anglin @ 2002-07-10 17:07 UTC (permalink / raw)
To: Richard Hirst; +Cc: grundler, varenet, parisc-linux
In-Reply-To: <20020710142317.GS6681@sleepie.demon.co.uk>
> > -pa52 kernel panic'd at 22:07
> > running gcc1 test in background
In hacking gcc this morning trying to fix a bug in loading 64-bit
constants, I seem to have achieved a state where the gcc build crashes
gsyprf11 in a deterministic manner. It's gone down three times.
It only takes a few seconds after the build starts for the machine
to crash.
Dave
--
J. David Anglin dave.anglin@nrc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6605)
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox