booting on kernel-2.4.21-ben1
Hi, I got the sources and compiled them fine. But when I try to boot on this kernel I get a black screen with: "Welcome to Linux, kernel 2.4.21-ben1 linked at :0xc000 [...] openpic: exit" and everything hang. I never had this problem with the 2.4.20 version. My computer is a Powermac G4 (AGP). I tried with some configurations, always the same problem. Someone has a solution? Thanks Laurent config Description: Binary data
Re: booting on kernel-2.4.21-ben1
Le mardi, 17 juin 2003, à 22:54 Europe/Brussels, Benjamin Herrenschmidt a écrit : On Tue, 2003-06-17 at 21:53, Laurent Bigonville wrote: Hi, I got the sources and compiled them fine. But when I try to boot on this kernel I get a black screen with: "Welcome to Linux, kernel 2.4.21-ben1 linked at :0xc000 [...] openpic: exit" and everything hang. I never had this problem with the 2.4.20 version. My computer is a Powermac G4 (AGP). I tried with some configurations, always the same problem. You tried the pmac defconfig ? (first make distclean, then make pmac_defconfig; make oldconfig; and buid it) If it still doesn't work, try with video=ofonly on the kernel command line from yaboot and let me know It's only work with the video=ofonly stuff. My graphic card is a Radeon 8500 mac edition.
Some problems with a radeon 8500
Hi, I have some problems with my Radeon 8500 on my Macintosh G4. I'm now under dapper but I had the same problem with a debian sid. If I kill the X server (by stopping gdm (/etc/init.d/gdm stop)) the fonts on the console (with radeonfb) become completely unreadable, if I restart X it's readable again. A second problem, the 3D seems to skip a lot of frames (the dri is enabled). For example if I run a 3D screensaver, the screensaver blinks. A last one, radeonfb seems to find 2 monitors radeonfb: Monitor 1 type CRT found radeonfb: EDID probed radeonfb: Monitor 2 type CRT found radeonfb: EDID probed I have two heads on the card but only one monitor connected. Somebody has the same problems? Regards Laurent pgpICjHGmlhpg.pgp Description: PGP signature
undefined reference to outb
Hi, I try to compile this file[1] on my ppc sarge. But I get some linking errors with some functions (outb,...). This program compiles fine on x86. I suspect problems in asm/io.h. [1]ftp://ftp.scyld.com/pub/diag/ne2k-pci-diag.c pgpZOV8ibUZOW.pgp Description: PGP signature
Error with Bluetooth dongle and kernel 2.6
Hi, I get a strange error when I load the hci-usb module or using hciconfig hub 2-1:1.0: new USB device on port 3, assigned address 7 hci_usb: probe of 2-1.3:1.1 failed with error -5 hci_usb: probe of 2-1.3:1.2 failed with error -5 hci_usb_isoc_rx_submit: hci0 isoc rx submit failed urb deea4414 err -90 No problem under 2.4.23 Have somebody a clue? Laurent PGP.sig Description: =?ISO-8859-1?Q?Ceci_est_une_signature_=E9lectronique_PGP?=
The scancode of a key has changed under 2.6
Hi, Since I have installed the 2.6.1-rc1-ben1 (maybe the same problem with the previous version of the 2.6) the scancode of the key with dead_grave and the pound sign (on my azerty keyboard) has changed. Under 2.4 the scancode was 0x2b (keycode 43) and now under the 2.6 the scancode is 0x54 (keycode 84)... No problem with the other keys (so far i tested) Laurent Bigonville PGP.sig Description: =?ISO-8859-1?Q?Ceci_est_une_signature_=E9lectronique_PGP?=
Re: The scancode of a key has changed under 2.6
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >Hi, > >Since I have installed the 2.6.1-rc1-ben1 (maybe the same problem with >the previous version of the 2.6) the scancode of the key with dead_grave >and the pound sign (on my azerty keyboard) has changed. > >Under 2.4 the scancode was 0x2b (keycode 43) and now under the 2.6 the scancode is 0x54 (keycode 84)... hu? no answer? is my english so awful? on startup i get an error, i don't know if it's related Setting up general console font... done. KDSKBENT: Argument invalide failed to bind key 256 to value 638 KDSKBENT: Argument invalide failed to bind key 256 to value 638 KDSKBENT: Argument invalide failed to bind key 256 to value 638 KDSKBENT: Argument invalide failed to bind key 256 to value 638 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (Darwin) iD8DBQFABEfYVLyDt/3apY8RApwbAKCti7B8ysN4WZbfV97/U3QfufS7wwCfdSwO Mwp61qM2JtsjnUv5/sFTfPw= =bnOr -END PGP SIGNATURE-
CTRL-ALT-DEL not working...
Hi, I know it's not very usefull under linux but the ctrl-alt-del sequence doesn't work on my machine, nothing happend. I have the last vanilla 2.6.4 kernel, I had this problem with previous version too. i have an apple pro keyboard, i don't know if it's a keycode problem or some thing else. Laurent PGP.sig Description: =?ISO-8859-1?Q?Ceci_est_une_signature_=E9lectronique_PGP?=
Re: Re: CTRL-ALT-DEL not working...
Hi, I know it's not very usefull under linux but the ctrl-alt-del sequence doesn't work on my machine, nothing happend. I have the last vanilla 2.6.4 kernel, I had this problem with previous version too. i have an apple pro keyboard, i don't know if it's a keycode problem or some thing else. Check the relevant entry in /etc/inittab. I think I never modified the inittab file... I found these lines in it... # What to do when CTRL-ALT-DEL is pressed. ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now Is that correct? signature.asc Description: OpenPGP digital signature
Fw: debian-installer: Cannot boot the installer on powerpc
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've sent a few days ago a bug report (bug #248234) about the fact that I cannot boot with the last daily build of the sarge installer on my g4, nobody answers ... I would like to know if anybody else has the same problem? >Yesterday, I had problem to boot on the installer 1/3 time... but today >no more way to boot on it. >The kernel hang juste after: >"Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ >SERIAL_PCI enable" >I have a G4(agp). I tried with the beta4 release, with the yesterday >daily build >and with the today (20040509) build, same problem. > >Any clue? thanks Laurent Bigonville -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (Darwin) iD8DBQFApRZHVLyDt/3apY8RAofuAKCOxfwT860Uvp/zzbfTRAHdSqBvYQCcCUYW 2Z2NhEisEi5sQr3a9/EWEf0= =13En -END PGP SIGNATURE-
Re: Re: Fw: debian-installer: Cannot boot the installer on powerpc
Clive Menzies wrote: I downloaded the beta4 powerpc installer last night and it has booted fine. Have you looked at the cd to verify that it burned ok? My first try didn't user error ;) The cd is ok... I tried with different iso, the only one that booted was the beta 3.
Bug#857172: Please enable SSE2 on amd64 and disable altivec on PPC ports
Source: babl
Version: 0.1.18-1
Severity: normal
Hi,
According to [0], optimisation upto SSE2 can be enabled on amd64.
Also, I'm not sure that altivec is officially supported on any of the
ppc ports, so I'm disabling it completely, I'm putting debian-powerpc ML
in copy.
See attached patch.
Regards,
Laurent Bigonvilleo
[0] https://www.debian.org/ports/amd64/index.en.html
-- System Information:
Debian Release: 9.0
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru babl-0.1.18/debian/rules babl-0.1.18/debian/rules
--- babl-0.1.18/debian/rules2016-03-16 18:06:40.0 +0100
+++ babl-0.1.18/debian/rules2017-03-08 15:02:28.0 +0100
@@ -7,10 +7,19 @@
export LDFLAGS += -Wl,--as-needed
+# disable sse2 except on amd64
+ifneq ($(DEB_HOST_ARCH_CPU),amd64)
+sse_flags := --disable-mmx --disable-sse --disable-sse2
+else
+sse_flags := --enable-mmx --enable-sse --enable-sse2
+endif
+
DEB_CONFIGURE_EXTRA_FLAGS += \
--libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH) \
- --disable-mmx \
- --disable-sse
+ $(sse_flags) \
+ --disable-sse4_1 \
+ --disable-f16c \
+ --disable-altivec
DEB_DH_MAKESHLIBS_ARGS_libbabl-0.1-0 =
"--exclude=/usr/lib/$(DEB_HOST_MULTIARCH)/babl-0.1"
DEB_DH_INSTALLDOCS_ARGS_libbabl-0.1-doc = "--exclude=Makefile"
Re: Bug#857172: Please enable SSE2 on amd64 and disable altivec on PPC ports
Le 08/03/17 à 16:06, John Paul Adrian Glaubitz a écrit : On Wed, Mar 08, 2017 at 03:57:55PM +0100, Laurent Bigonville wrote: Also, I'm not sure that altivec is officially supported on any of the ppc ports, so I'm disabling it completely, I'm putting debian-powerpc ML in copy. The firefox package is built with AltiVec enabled and so is mplayer, for example. So, yes, Altivec is actively used and I would honestly refrain from disabling it in a performance-sensitive package like babl. Altivec is disabled on powerpcspe where it's not available in the hardware, but most machines on which people install Debian powerpc should have Altivec. For the powerpc port, if G3 are still supposed to be supported, altivec should be disabled as they are not supporting it IIRC (longtime I didn't use a ppc machine). If you are telling me altivec is OK, I guess that the flag can be removed and the situation can be kept as before for PPC
