Problems compiling ppc kernels.

Problems compiling ppc kernels.

[Mike Panetta]

I have been having some real weird problems with compiling 
kernels for my iMAC.  I have tried kernel versions 2.2.12, 2.3.23, 2.3.21
And have goten pretty much the same results.  In all these compile attemts
I have had to make drivers/usb/mkmap (2.2.x), or drivers/usb/mkmap.adb (2.3.x)
executable because the Makefile complained that it did not have permissions to
run the script.  After that was fixed I had various linking problems at the
very end of the compile when it was making vmlinux.  Usually pertaining to 
mac_floppy or something.  Disabling this in the .config did not help.  It just
went on complaining about other symbols not being found.  Could someone please
point me at some patches or directions on what I am doing wrong?  I have never
had a problem compiling kernels on my i386, except for some of the 2.3.x series.
What am I doing wrong? (it must be me since obviously someone compile a kernel!)

Thanks,
Mike Panetta


-- 

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Problems compiling ppc kernels.

[David Riley]

Mike Panetta wrote:
> 
> I have been having some real weird problems with compiling
> kernels for my iMAC.  I have tried kernel versions 2.2.12, 2.3.23, 2.3.21
> And have goten pretty much the same results.  In all these compile attemts
> I have had to make drivers/usb/mkmap (2.2.x), or drivers/usb/mkmap.adb (2.3.x)
> executable because the Makefile complained that it did not have permissions to
> run the script.  After that was fixed I had various linking problems at the
> very end of the compile when it was making vmlinux.  Usually pertaining to
> mac_floppy or something.  Disabling this in the .config did not help.  It just
> went on complaining about other symbols not being found.  Could someone please
> point me at some patches or directions on what I am doing wrong?  I have never
> had a problem compiling kernels on my i386, except for some of the 2.3.x series.
> What am I doing wrong? (it must be me since obviously someone compile a kernel!)
> 
> Thanks,
> Mike Panetta
> 
> --

If it helps, HFS doesn't work in the vger kernels.  You are probably not
using vger, since as far as I know vger doesn't have past 2.3.18 yet
(but I haven't checked in a month).  Try turning HFS support off (though
that wouldn't fuss at all about the floppy).
-- 
--"Your mouse has been moved.  Windows 95 must be restarted for change
to take effect."

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Problems compiling ppc kernels.

[Neil Russell]

On Tue, Oct 26, 1999 at 01:47:28PM -0400, Mike Panetta wrote:
> I have been having some real weird problems with compiling 
> kernels for my iMAC. ....


I had basically the same problems compiling a kernel for iMac, and
fixed them by turning off config for the offending items.  I did not
get any of those kernels to boot on the iMac.  I ended up using 2.2.6
(the one shipped on the LinuxPPC CD).  The 226 kernel works, except for
the keyboard/mouse ("version 1.16 USB, only understand 1.0 problem").
I ended up hacking a small change into the ethernet code to snarf
specially formatted UDP packets and shove them into the console queue.
This works fine, but is rather ugly.
  
Does anyone else have any insight into this?  Can anyone point me to
a kernel binary that works on the iMac?  How about the config file for
the said kernel?

I have a rev.D iMac, purchased about a month ago (just before the new
iMac came out).


Thanks,
	Neil.


-- 
Neil Russell <caret@c-side.com>

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Problems compiling ppc kernels.

[Mike Panetta]

Thanks!  I will try this.  I didn't even think of reconfiguring for a more
specific arch.  I will try the pmac only config as well.
Thanks also to all the others that replied.  

Mike Panetta

On Tue, Oct 26, 1999 at 01:21:24PM -0700, Ani Joshi wrote:
> 
> 
> 	There are a few still outstanding config issues in 2.3.23, take a
> look at my patch for 2.3.22 at 
> 	ftp://devel.linuxppc.org/users/ajoshi/2.3.22-ppc.patch
> 
> 	it should apply to 2.3.23, even if it doesn't it should provide
> you with enuff info to get your .23 to build.
> 
> iirc, swim3 needs a few #ifdef CONFIG_PMAC_PBOOK around all its media_bay
> calls, as with ide-pmac.  both of which are in the patch.
> 
> btw, its a good idea *not* to config for pmac/chrp/prep for pmacs, but
> only for pmac.
> 
> 
> ani
> 
> On Tue, 26 Oct 1999, Mike Panetta wrote:
> 
> > 
> > I have been having some real weird problems with compiling 
> > kernels for my iMAC.  I have tried kernel versions 2.2.12, 2.3.23, 2.3.21
> > And have goten pretty much the same results.  In all these compile attemts
> > I have had to make drivers/usb/mkmap (2.2.x), or drivers/usb/mkmap.adb (2.3.x)
> > executable because the Makefile complained that it did not have permissions to
> > run the script.  After that was fixed I had various linking problems at the
> > very end of the compile when it was making vmlinux.  Usually pertaining to 
> > mac_floppy or something.  Disabling this in the .config did not help.  It just
> 

-- 

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Problems compiling ppc kernels.

[Ani Joshi]

	There are a few still outstanding config issues in 2.3.23, take a
look at my patch for 2.3.22 at 
	ftp://devel.linuxppc.org/users/ajoshi/2.3.22-ppc.patch

	it should apply to 2.3.23, even if it doesn't it should provide
you with enuff info to get your .23 to build.

iirc, swim3 needs a few #ifdef CONFIG_PMAC_PBOOK around all its media_bay
calls, as with ide-pmac.  both of which are in the patch.

btw, its a good idea *not* to config for pmac/chrp/prep for pmacs, but
only for pmac.


ani

On Tue, 26 Oct 1999, Mike Panetta wrote:

> 
> I have been having some real weird problems with compiling 
> kernels for my iMAC.  I have tried kernel versions 2.2.12, 2.3.23, 2.3.21
> And have goten pretty much the same results.  In all these compile attemts
> I have had to make drivers/usb/mkmap (2.2.x), or drivers/usb/mkmap.adb (2.3.x)
> executable because the Makefile complained that it did not have permissions to
> run the script.  After that was fixed I had various linking problems at the
> very end of the compile when it was making vmlinux.  Usually pertaining to 
> mac_floppy or something.  Disabling this in the .config did not help.  It just


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Problems compiling ppc kernels.

[Gerd Knorr]

In lists.linuxppc.dev, you wrote:
> 
> I have been having some real weird problems with compiling 
> kernels for my iMAC.  I have tried kernel versions 2.2.12, 2.3.23, 2.3.21
> And have goten pretty much the same results.

I got 2.3.23 sorta working on my iMac (rev B).  "grep ^C .config" is attached
at the end of this mail.  There are alot of gliches:

  * needs some careful tuning of the config options to get a kernel which
    compiles and links without errors.
  * hfs does'nt compile.
  * other filesystems don't work as modules.
  * usb keyboard needs a (trivial) patch, see below.
  * usb keyboard works only if ADB_KEYBOARD is compiled in too.
  * I have a few keys which don't work at all because they are
    not mapped by usb_kbd_map (that's why the debug printk in the
    patch).
  * I could'nt make the usb mouse work.  usb mouse driver is listed
    in /proc/bus/usb/drivers, the (logitech) mouse is listed in
    /proc/bus/usb/devices, but /proc/misc has no entry for usb mouse.
    gpm does'nt work too.
  * The kernel does'nt survive a "make clean && make vmlinux".
    Starts swapping, gets slower and slower over time.

vger is still at 2.3.18.  usb keyboard does'nt work at all for me.

My default kernel is still 2.2.6 with the old uubsd stack patched in.

  Gerd

------------------------ cut here ---------------------------
diff -u 2.3.23/drivers/usb/keyboard.c my-2.3.23/drivers/usb/keyboard.c
--- 2.3.23/drivers/usb/keyboard.c	Tue Oct 26 23:25:39 1999
+++ my-2.3.23/drivers/usb/keyboard.c	Sun Oct 24 11:50:09 1999
@@ -66,13 +66,15 @@
     int scancode = (int) usb_kbd_map[key];
     if(scancode)
     {
-#ifndef CONFIG_MAC_KEYBOARD
+#ifndef CONFIG_ADB_KEYBOARD
         if(scancode & PCKBD_NEEDS_E0)
         {
             handle_scancode(0xe0, 1);
         }
-#endif /* CONFIG_MAC_KEYBOARD */
+#endif /* CONFIG_ADB_KEYBOARD */
         handle_scancode((scancode & ~PCKBD_NEEDS_E0), down);
+    } else {
+	printk("usb-keyboard: key=%d (0x%x) not found in usb_kbd_map\n",key,key);
     }
 }
 
------------------------ cut here ---------------------------
CONFIG_PPC=y
CONFIG_6xx=y
CONFIG_PMAC=y
CONFIG_MACH_SPECIFIC=y
CONFIG_6xx=y
CONFIG_EXPERIMENTAL=y
CONFIG_MODULES=y
CONFIG_KMOD=y
CONFIG_PCI=y
CONFIG_NET=y
CONFIG_SYSCTL=y
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_BINFMT_ELF=y
CONFIG_KERNEL_ELF=y
CONFIG_BINFMT_MISC=m
CONFIG_FB=y
CONFIG_PMAC_PBOOK=y
CONFIG_MAC_SERIAL=y
CONFIG_ADB=y
CONFIG_ADB_CUDA=y
CONFIG_ADB_MACIO=y
CONFIG_ADB_PMU=y
CONFIG_ADB_KEYBOARD=y
CONFIG_PROC_DEVICETREE=y
CONFIG_BLK_DEV_IDE=y
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_BLK_DEV_IDECD=y
CONFIG_BLK_DEV_IDE_PMAC=y
CONFIG_BLK_DEV_IDEDMA_PMAC=y
CONFIG_IDEDMA_PMAC_AUTO=y
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_IDEDMA_AUTO=y
CONFIG_BLK_DEV_LOOP=m
CONFIG_PARIDE_PARPORT=y
CONFIG_BLK_DEV_IDE_MODES=y
CONFIG_PACKET=m
CONFIG_PACKET_MMAP=y
CONFIG_NETFILTER=y
CONFIG_FILTER=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m
CONFIG_IP_ALIAS=y
CONFIG_SKB_LARGE=y
CONFIG_KHTTPD=m
CONFIG_ATALK=m
CONFIG_SCSI=m
CONFIG_BLK_DEV_SD=m
CONFIG_CHR_DEV_ST=m
CONFIG_BLK_DEV_SR=m
CONFIG_CHR_DEV_SG=m
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y
CONFIG_SCSI_NCR53C8XX=m
CONFIG_SCSI_SYM53C8XX=m
CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS=8
CONFIG_SCSI_NCR53C8XX_MAX_TAGS=32
CONFIG_SCSI_NCR53C8XX_SYNC=20
CONFIG_SCSI_NCR53C8XX_IOMAPPED=y
CONFIG_NETDEVICES=y
CONFIG_DUMMY=m
CONFIG_NET_ETHERNET=y
CONFIG_BMAC=y
CONFIG_FB=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FB_OF=y
CONFIG_FB_ATY=y
CONFIG_FB_VIRTUAL=m
CONFIG_FBCON_MFB=m
CONFIG_FBCON_CFB2=m
CONFIG_FBCON_CFB4=m
CONFIG_FBCON_CFB8=y
CONFIG_FBCON_CFB16=y
CONFIG_FBCON_CFB24=y
CONFIG_FBCON_CFB32=y
CONFIG_FBCON_MAC=m
CONFIG_FBCON_FONTS=y
CONFIG_FONT_8x16=y
CONFIG_FONT_SUN12x22=y
CONFIG_FONT_6x11=y
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
CONFIG_BUSMOUSE=y
CONFIG_ADBMOUSE=y
CONFIG_MOUSE=y
CONFIG_PSMOUSE=y
CONFIG_NVRAM=y
CONFIG_USB=y
CONFIG_USB_OHCI=y
CONFIG_USB_PROC=y
CONFIG_USB_HUB=y
CONFIG_USB_MOUSE=y
CONFIG_USB_KBD=y
CONFIG_AUTOFS_FS=m
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
CONFIG_UDF_FS=m
CONFIG_MINIX_FS=m
CONFIG_PROC_FS=y
CONFIG_DEVPTS_FS=y
CONFIG_ROMFS_FS=m
CONFIG_EXT2_FS=y
CONFIG_NFS_FS=y
CONFIG_SUNRPC=y
CONFIG_LOCKD=y
CONFIG_PARTITION_ADVANCED=y
CONFIG_MAC_PARTITION=y
CONFIG_MSDOS_PARTITION=y
CONFIG_NLS=y
CONFIG_NLS_CODEPAGE_437=m
CONFIG_NLS_CODEPAGE_850=m
CONFIG_NLS_ISO8859_1=m
CONFIG_NLS_ISO8859_2=m
CONFIG_NLS_ISO8859_15=m
CONFIG_NLS_KOI8_R=m
CONFIG_SOUND=m
CONFIG_DMASOUND=m

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Problems compiling ppc kernels.

[Dan Malek]

Neil Russell wrote:


> I have a rev.D iMac, purchased about a month ago (just before the new
> iMac came out).

Me, too, and I am having the same difficulties.....

Unfortunately, I bought them for new employees to use and recommended
them to new clients over the past month or so.

Now, I get to spend time to learn about USB.......If anyone is working
on this, please let me know, as it is now my highest priority task.
I will post any updates or information.

Does anyone know why the USB doesn't work?  Hints would be appreciated
so all I have to do is patch some code and test it.......


	-- Dan

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Missing USB keys (Was Re: Problems compiling ppc kernels.)

[Martin Costabel]

Gerd Knorr wrote:

> I got 2.3.23 sorta working on my iMac (rev B).  "grep ^C .config" is attached
> at the end of this mail.  There are alot of gliches:
[...]
>   * usb keyboard needs a (trivial) patch, see below.
>   * usb keyboard works only if ADB_KEYBOARD is compiled in too.
>   * I have a few keys which don't work at all because they are
>     not mapped by usb_kbd_map (that's why the debug printk in the
>     patch).

Gerd,

I suppose you have a German keyboard. Having had the same problem of
missing keys on a French USB keyboard, I dug into this USB->ADB keycode
translation stuff, and I think I understand some of it now. As I see it,
this part of the kernel sources is a pretty ugly hack, but it is
"official linux", so it is here to stay, and the following explanation
(possibly improved by someone more knowledgeable) will have to go into
some kind of FAQ (unless the kernel sources were patched accordingly):

1. The keycodes produced by a USB keyboard are first translated by the
kernel into the corresponding keycodes of an ADB keyboard. This has the
advantage that (even for for German, French etc keyboards) one can use
the same keymaps in /usr/lib/kbd/ and in /usr/lib/X11/xkb/ for USB
keyboards as for ADB keyboards, and one can use an ADB keyboard at the
same time as a USB keyboard. At least in principle...

2. This translation is done using the array usb_kbd_map which is defined
in the file drivers/usb/keymap-mac.c (for Mac keyboards, i.e. if
CONFIG_ADB_KEYBOARD is defined). In this array, undefined keys are
translated into keycode 0x00, so it would suffice to patch this file and
to write the correct ADB keycodes into the right places, except that...

3. The file drivers/usb/keymap-mac.c is a generated file which is made
during kernel compilation by the shell script drivers/usb/mkmap.adb.
This script uses two keymaps living in drivers/usb/maps/, namely usb.map
and mac.map and figures out how to translate between these two. The
mac.map is a standard ADB keymap, but to understand usb.map, one has to
recall some historical facts:

4. There exist two completely different USB drivers, namely UUSB which
was in use for example in the 2.2.6 kernel, and the newer USB which is
used from 2.2.10 onwards. In the UUSB system, one needed special USB
keymaps, because there the USB keycodes are directly translated into key
symbols, and there is no intermediate ADB keycode step. The usb.map in
drivers/usb/maps/ is such a keymap (used, however, within the new USB
system).

5. Thus the keycode translation in the new USB driver is a hack on top
of the old UUSB driver; the USB keycodes are in a sense first translated
into symbols via an old UUSB keymap and then retranslated into ADB
keycodes via an ADB keymap.

6. So where is the problem? The problem, of course, is that the two
keymaps in drivers/usb/maps/ which are used to produce the translation
table, are goddamn^H^H^H^H^H^H^Hstandard US keymaps. Therefore some of
the keys of European Apple Extended keyboards are missing (maybe just
one or two?). The right solution is therefore to add the missing keys in
both keymaps, which is what I did, see the patch below. Another (not so
universal) solution would be to replace both US keymaps by equivalent
French ones. Or German ones, of course, but I suspect this would produce
an identical usb_kbd_map translation table.

My patch for French USB keyboards is the following (the important part
is the "at numersign" stuff, the "KP_Equals" business is something I
don't quite understand, it might be related to weird mouse button
emulations). The patch is against the 2.3.18 vger kernel, but I think
any 2.3.x kernel should work similarly. And I would bet 2 Pfennig that
this patch makes the German keyboard work as well.

===================================================================
RCS file: /cvs/linux/linux/drivers/usb/maps/mac.map,v
retrieving revision 1.1
diff -u -r1.1 mac.map
--- drivers/usb/maps/mac.map    1999/06/09 08:20:17     1.1
+++ drivers/usb/maps/mac.map    1999/10/26 17:34:41
@@ -22,7 +22,7 @@
 keycode 0x08 = c
        altgr   keycode 0x08 = Hex_C   
 keycode 0x09 = v
-keycode 0x0a =
+keycode 0x0a = at numbersign
 keycode 0x0b = b
        altgr   keycode 0x0b = Hex_B
 keycode 0x0c = q               
@@ -144,7 +144,7 @@
 keycode 0x4f =
 keycode 0x50 =
 keycode 0x51 =
-#keycode 0x51 = KP_Equals
+keycode 0x51 = KP_Equals
 keycode 0x52 = KP_0            
        alt     keycode 0x52 = Ascii_0         
        altgr   keycode 0x52 = Hex_0         
Index: drivers/usb/maps/usb.map
===================================================================
RCS file: /cvs/linux/linux/drivers/usb/maps/usb.map,v
retrieving revision 1.1
diff -u -r1.1 usb.map
--- drivers/usb/maps/usb.map    1999/04/28 11:52:38     1.1
+++ drivers/usb/maps/usb.map    1999/10/26 17:34:42
@@ -88,7 +88,7 @@
 keycode  49 = backslash        bar             
        control keycode  43 = Control_backslash
        alt     keycode  43 = Meta_backslash  
-keycode 50 =
+keycode  50 = backslash        bar
 keycode  51 = semicolon        colon           
        alt     keycode  39 = Meta_semicolon  
 keycode  52 = apostrophe       quotedbl        
@@ -215,10 +215,10 @@
 keycode  99 = KP_Period       
 #      altgr   control keycode  83 = Boot            
        control alt     keycode  83 = Boot            
-keycode 100 =
+keycode 100 = at  numbersign
 keycode 101 = Application
 keycode 102 =
-keycode 103 =
+keycode 103 = KP_Equals
 keycode 104 = F13             
 keycode 105 = F14             

===================================================================

Have fun
--
Martin

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Missing USB keys

[bob]

Martin Costabel Said:
.
.
I dug into this USB->ADB keycode
translation stuff, and I think I understand some of it now. As I see it,
this part of the kernel sources is a pretty ugly hack,
.
.

End of quote...

Am I beating a dead horse? But this ugly hack is perhaps responsible for
the lack of N-KEY rollover in the "new" USB keyboard driver????

Bob
-- 
Robert E. Brose II    N0QBJ
http://www.jriver.com/~bob/
bob@kunk.jriver.com

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Missing USB keys

[Gerd Knorr]

On Wed, 27 Oct 1999, Martin Costabel wrote:

> [ ... ]

> 6. So where is the problem? The problem, of course, is that the two
> keymaps in drivers/usb/maps/ which are used to produce the translation
> table, are goddamn^H^H^H^H^H^H^Hstandard US keymaps. Therefore some of
> the keys of European Apple Extended keyboards are missing (maybe just
> one or two?). The right solution is therefore to add the missing keys in
> both keymaps, which is what I did, see the patch below. Another (not so
> universal) solution would be to replace both US keymaps by equivalent
> French ones. Or German ones, of course, but I suspect this would produce
> an identical usb_kbd_map translation table.

Up to that point I've traced it too.

> --- drivers/usb/maps/mac.map    1999/06/09 08:20:17     1.1
> +++ drivers/usb/maps/mac.map    1999/10/26 17:34:41
> +keycode 0x0a = at numbersign

How can I figure out the correct adb keycodes?  Hav'nt such a keyboard...

> --- drivers/usb/maps/usb.map    1999/04/28 11:52:38     1.1
> +++ drivers/usb/maps/usb.map    1999/10/26 17:34:42
> @@ -88,7 +88,7 @@
>  keycode  49 = backslash        bar             
                 ^^^^^^^^^^^^^^^^^^^^
> -keycode 50 =
> +keycode  50 = backslash        bar
                 ^^^^^^^^^^^^^^^^^^^^

Does'nt look like a good idea...

  Gerd

-- 
<script>alert("WARNING: You have JavaScript enabled.");</script>


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Missing USB keys

[Martin Costabel]

Gerd Knorr wrote:
> 

> How can I figure out the correct adb keycodes?  Hav'nt such a keyboard...

There are German keymaps in the console-tools rpm, for example
/usr/lib/kbd/keymaps/mac/mac-de-latin1-nodeadkeys.kmap.gz
I guess you would have to compare this with a corresponding German usb
keymap. Don't know where to find one, but I'm sure such keymaps have
been offered on the net.

> > --- drivers/usb/maps/usb.map    1999/04/28 11:52:38     1.1
> > +++ drivers/usb/maps/usb.map    1999/10/26 17:34:42
> > @@ -88,7 +88,7 @@
> >  keycode  49 = backslash        bar
>                  ^^^^^^^^^^^^^^^^^^^^
> > -keycode 50 =
> > +keycode  50 = backslash        bar
>                  ^^^^^^^^^^^^^^^^^^^^
> 
> Does'nt look like a good idea...

Looks bad, indeed. Works, however, on the B&W G3 where I tried it :-)
It just means that both USB keycodes 49 and 50 will be mapped to the
same ADB keycode. I don't quite remember (have been away from linux for
a month), but I think only one of the two actually exists on a key.

--
Martin

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/