wierd Xpmac problem
in X, only my left shift key and left control key work properly. The ones on the right-hand side of the keyboard are unresponsive. Here's the details: i've been using xpmac as my xserver happily for quite a while now on my g4, and have been tracking woody since the stable/testing/unstable split happened. a couple of days ago i made an aborted attempt to try the new xfree v4 packages. one package had a problem (snapshot below) | Unpacking xserver-xfree86 (from .../xserver-xfree86_4.0.2-1_powerpc.deb) ... | Setting up xserver-xfree86 (4.0.2-1) ... | Configuring Xserver-xfree86 | -- | | sh: -c: line 1: unexpected EOF while looking for matching `'' | sh: -c: line 2: syntax error: unexpected end of file | | a. atif. fbdev m. mga b. sis v. vga | c. chips g. glint s. s3virge t. trident | | Select the desired X server driver. i selected ati, and had a kernel panic when it tried to do a modprobe. So i decided i was in over my head. Fortunately, all i had to do to go back was remake the /etc/X11/X link back to Xpmac and put my '-mode 19 -depth 16' arguments in a config file...startx worked beautifully. But, as i said at the beginning, i can only shift or control with my left pinky -- a sad state of affairs for an emacs user. does anybody have any insights? Since Xpmac doesns't have the usual XF86Config file, i'm at a loss for altering the configuration. i'm using rev10 of the Xpmac server...is there a more recent one i could try? [EMAIL PROTECTED]
Re: wierd Xpmac problem
Andrew Sharp wrote: > pohl wrote: > > > > in X, only my left shift key and left control key work > > properly. The ones on the right-hand side of the keyboard > > are unresponsive. Here's the details: > > Does the right shift work while on the console? If not, then it's > the same problem I had, which was solved by getting one of those > so called Extended keyboards. Suddenly everything works fine. Unfortunately, this is not the same problem that I'm having. My keyboard works perfectly in console mode, only misbehaving in X. But since you mention it, i'm not using the keyboard that shipped with this G4...i couldn't stand not having a control key for the right-hand pinky, so i replaced it with a macally ikey keyboard -- and have been using it without any problems for months until my aborted attempt to upgrade to xfree 4. [EMAIL PROTECTED]
Re: x-window on powermac G3
I ran into this problem today while trying to get XFree86 v4 going. I managed to write a configuration file by hand, but would have loved a configurator. Paul, could you do a "dpkg -S Xconfigurator" and tell me what package that thing came in? Also, I recall running a configurator called "dexter" that was fairly nice on a debian/i386 system recently while installing XFree 4, but now I can't find the thing, and am doubting my memory of its existence. Paul Kimber wrote: > > Try 'Xconfigurator' instead. > > Alexander Kitzberger wrote: > > > > i want to configure the x-window system on a powermac G3 > > after installing xserver-common, i can't find the program xf86config. > > Can anyone help me? > > > > Thanks a lot > > > > > > Alex [EMAIL PROTECTED]
Re: Ximian Gnome packages updated
Bastien Nocera <[EMAIL PROTECTED]> wrote: > > I updated my lot of Ximian Gnome packages. Take a look at > http://hadess.net/idoru.shtml for more details. I had been trying to update to the gnome 1.2 packages in unstable without luck (gnome-panel and gnome-panel-data aren't happy with each other) but Hadess has allowed me to get around all that with his Ximian Gnome 1.2 packages. I just wanted to sing his praises in public. It went flawlessly on my system. Thank you! [EMAIL PROTECTED]
yaboot on sawtooth G4
I've begun the adventure of bootstrapping debian/ppc onto my new G4. Since I do not have a zip disk handy, and I do have a yellowdog CD, I thought the best way to go about this would be to leverage the yellowdog's convenient mac-fdisk to make the 800K Apple_Bootstrap partition that Ethan advocates. I managed to get the yaboot_0.4 package to work to get into the yellowdog installation routines to partition my disk. I made a partition of type Apple_HFS at the end of the disk to put MacOS on. Fortunately, the partitioning worked fine when I did this. MacOS is reinstalled, and my Apple_Bootstrap partition is waiting there for me to try Ethan's cool ybin tool on it. Here's where I'm stuck: In order to run ybin, I have to get linux started again. Unfortunately, I think that I may have broken yaboot_0.4 by placing the MacOS partition towards the end of my disk. In Open Firmware, it complains: boot: hd:yaboot_0.4 Can't open config file, err: -2 It had no trouble reading this configuration file before. I thought to try the most recent yaboot_0.5, but open firmware claims to not be able to yaboot_0.5 executable at all: boot: hd:yaboot_0.5 Can't open hd:yaboot_0.5 (So it looks like yaboot_0.4 had better luck.) Now, the difference between these to yaboot executables is that version 0.4 came in a stuffit bundle from yellowdoglinux.com, whereas version 0.5 came gzipped from Benjamin's page. On my linux/intel box, they are identified slightly differently. Could it be that being stripped causes yaboot_0.5 to fail to load? It wouldn't make sense to me, but that's the only difference I can see. Also, does anybody happen to know what an error code of -2 implies in 0.4? $ file yaboot_0.5 yaboot_0.5: ELF 32-bit MSB executable, PowerPC or cisco 4500, version 1, statically linked, stripped $ file yaboot_0.4 yaboot_0.4: ELF 32-bit MSB executable, PowerPC or cisco 4500, version 1, statically linked, not stripped $ ls -l yaboot* -rw-r--r--1 pohl pohl 146804 Feb 28 20:15 yaboot_0.4 -rw-rw-r--1 pohl pohl53832 Feb 27 20:00 yaboot_0.5 Now, just in case anybody is wondering whether or not I'm correctly referencing the right partition when I try to start yaboot from Open Firmware, I've tried referencing the numerical partition directly, with the same results. I've verified that I've counted the partitions correctly by booting MacOS from OF with like this... boot hd:9,\\:tbxi
Re: yaboot on sawtooth G4
I wrote: > > Also, does anybody happen to know what an error code of -2 > implies in 0.4? I found in include/file.h the definition for the error code. Now I just have to scrutinize file.c to figure out why the config file isn't being found. #define FILE_ERR_NOTFOUND -2 I'm looking through the source for version 0.5, of course, which I couldn't actually use. Is it possible to cross-compile this beast from a debian/x86 machine?
Re: yaboot on sawtooth G4
> if you get a boot: prompt you can enter the command: > > hd:,/boot/vmlinux-2.2.14 Thank you, I hadn't realized that I was returning to a yaboot prompt after the -2 error code. I wasn't watching closely enough, and thought it was an OF prompt. I'll give this a whirl. Is there syntax for pointing to an installation image too? > > boot hd:9,\\:tbxi > > ah ha, this won't work unless A) the file acutally has file > type tbxi AND B) the root directory is blessed, AND C) > the file is a CHRP script. This must be the case, then, because it worked for me. I don't think I was very clear in this paragarph. You see, I'm trying to yaboot a kernel that's on an HFS partition (never did the linux installation, only the partitioning) and used the above to test to see if slice 9 was the right slice to find yaboot_0.5 on. I would love it if you could send me a binary that I could try. I did find a friend last night with a ppc machine that I used to try to build my own, but I'm getting the same failure to find yaboot_0.5 -- on an HFS partition, recall. I used Lynx to download the binary from Ben's page, so I'm confident that it wasn't the browser mangling the file in any way.
Re: yaboot on sawtooth G4
My experiences with yaboot_0.5 are getting more interesting the more I play with it. I started giving the Open Firmware boot command silly arguments out of frustration, and got some interesting results. Apparently, I can pick random files that are sitting right beside yaboot_0.5 on the same HFS slice, and get a message that indicates that the boot command was at least able to locate the file, but so far no indication that it can even find the yaboot_0.5 binary itself... boot hd:vmlinux.benh.15<--- silly load-size=264466 adler32=(something) Loading ELF CLAIM failed ok boot hd:yaboot.conf<--- very silly load-size=4b adler32=b24b1919 unrecognized Client Program format Yet something not so silly yields... boot hd:yaboot_0.5 Can't open hd:yaboot_0.5
Re: X server error on 7200
I had a problem like this once on an old 7100 or 7200 (I can't rember which -- it was a nubus machine with an 80Mhz 601 PPC I think) and it turned out that xscreensaver was causing the X display server to crash. The nice thing was that xscreensaver was nice enough to give some message when I ran it that said something like "you must disable the X server's built in screensaver first" and it even gave the proper incantation. Once I did what it said, xscreensaver ran just fine and X was really stable. Hope this helps.
Re: imac install
Ethan wrote: > > not unfortunately, yaboot is more robust and reliable. just create a > 800K bootstrap partition at the front of your disk to hold it after > the install, and use my ybin utilites to manage it. just as easy as > lilo. (in mac-fdisk use the C command and create the bootstrap > partition as type Apple_Bootstrap) Will it work to place this partition after an HFS or HFS+ MacOS partition? I haven't yet found a way to keep the MacOS 9 partitioning tool to from destroying my poor little Apple_Bootstrap. Perhaps I should just consider that tool to be hostile and avoid it? (Apple's disk tool, not yaboot :-)
Re: The truth about Apple's fdisk (was: Re: imac install)
Ethan wrote: > > OK, I got annoyed enough to go test this, and i plan to write a > simple howto for partitioning (you're all in trouble now im annoyed > enough to write docs!) Thank you for spelling this all out for me. I'm sorry that I haven't given you any feedback on this until now. I'm in the middle of selling one house and buying another -- not much time for play in my world for a while. I have managed to squeeze in a few iterations of your recipie, though, and have always managed to get stuck in the same place... [munch] > now hit C to create the 800K Apple_Bootstrap partition. > > hit c for each linux partition you want. > > once your done w to write the table. > > install linux, configure ybin run mkofboot to setup yaboot. ^ | | +- right here. Configuring ybin can't happen unless I can manage to get the ybin stuff on my linux partition immediately after installation, before the first reboot, because if the box goes down, I can no longer boot into linux (with the HFS partition at the end of the volume, breaking yaboot's ability to find its config file there). Since I have no removable storage devices on this box, and can't seem to get it on the network during the initial install, I'm looking for ideas: how do I get ybin on there before it goes down? I'm going to try to figure out what it would take to help yaboot find its default configuration file properly in my copious free time barring some insight from the list. Plan B will be to figure out how to make ybin work even if the Apple_Boostrap partition isn't the first one.
Re: The truth about Apple's fdisk (was: Re: imac install)
Ethan wrote: > > the bootstrap partition will not inerfere with yaboot on the hfs > partition, you just need to boot into OF and run the following > command: > > boot hd:X,yaboot For me, yaboot_0.4 cannot find its config file in this situation, and yaboot_0.5 can't even be executed successfully by OF, unless the HFS partition is the first one, and even then yaboot_0.5 can't find its default config file properly. yaboot_0.4 is the only version I've had any success with, and that's only with the HFS partition being the first (not counting driver partitions, of course.) > if your macos partition is HFS not plus then: > > mount -t hfs /dev/hdaX /mnt This is promising. I'll give this a go. Thanks again.
yaboot errors on g4
This is exactly my experience on my sawtooth G4, except that I had been trying to get ybin 0.10 to function. I had thought maybe I wasn't following the installation instructions correctly, but can't find any discrepencies between what Ethan suggests and what I'm doing. > I finally went out and bought linuxppc (AUS$15) and yellowdog (AUS$15) > disks so I can boot into Linux. I don't plan on installing either, I > just wanted a boot disk so I could untar the debian base2_2.tgz file > and then use apt. > > I downloaded ybin (0.11), yaboot (0.5) and hfsutils and managed to > install them on a 800K HFS bootstrap partition (yes it is the first > partition, well 2nd partition after the partition table itself). > > I get an error message saying "can't read config file" so I can't load > linux. This is the way yaboot_0.5 has always behaved on my hardware, no matter where I put the config file or how I invoke yaboot. All it manages to do is turn the screen to green-on-black and give the above compliant. > I can't press tab as the config file was not read. I have tried > putting in commands manually at the boot: prompt. > eg. > "boot: hd:4,/boot/vmlinux ro" > but I get the following error > "Image not found.. try again" I get this too. > What am I doing wrong ? > How can I get debian to boot ? > I can't even get the LinuxPPC installation to boot of the hard disk. Same here.
Re: yaboot errors on g4
Ethan wrote: > you never got it to work? i really think this has to be some > difference in some G4's OpenFirmware... though i think Ben has > G4 and has yaboot working... I guess there is a lot of hardware (and probably firmware) variance even within the set of machines that go by the "G4" label. My machine was purchased after Apple bumped the CPU clockspeed back up to their original values. I've found several references to people getting pre-speedbump G4s going with yaboot, but nobody has reported success specifically with a post-speedbump G4 -- so far as I've seen. > did you ever try a debug build of yaboot? Not yet. My pace of experimenting with it is very slow since I'm in the middle of upgrading from one house to another. The ppclinux 2000 CD uses yaboot_0.5, and it seems to work fine on my machine. I'm curious as to why it can find its configuration file in this case -- perhaps because there's only one partition on the CD? The Open Firmware reports a build date of somewhere in late January of this year on my machine. I'm not in front of the machine right now so I can't be more specific than that. What date does yours report?
Re: yaboot errors on g4
Josh wrote: > > I've got a G4/500 running w/o any problems with yaboot here... > Just got it from Apple 2 weeks ago. Cool! Could you describe your partitioning scheme and attach the yaboot.conf and ybin.conf files you used?
Re: yaboot errors on g4
Thanks. Josh wrote: > > I don't have a ybin.conf file. (don't use it...) So you just manually enter OpenFirmware boot commands to boot? What version of yaboot do you use?
Re: yaboot errors on g4
Josh Huber <[EMAIL PROTECTED]> > > I'm using 0.5, which is think is the latest version. > I just set the boot-device to hd:9,yaboot_0.5 I think this explains the difference between your machine and mine. I have been trying to make a partition of type "Apple_Bootstrap" to install ybin onto. You, on the other hand, are just using as small HFS partition. I know for a fact that I could also get my machine to work this way. I had been too focused on trying to get ybin set up, because I was hoping to eventually make a dual-boot configuration with MacOS. We still don't have an instance of a post-speedbump G4 that uses yaboot _with_ ybin successfully, but now I know how to get around it -- if I'm willing to do without dual-boot. Thanks, Josh.
dvorak keymap
debian is now happily living on my G4 (though I had to break down and buy a zip drive to accomplish the install) but I need a dvorak keymap for the beast. Anybody got a pointer to one? This is strictlt for the console -- no X yet...
Re: Xpmac.deb
Today's thread on Xpmac spurred me to resume my efforts to get it running. It turned out to be very easy after all, with one exception: in the debian/x86 universe, I was never able to get mouse support under X unless "gpm" was running, but under Xpmac the exact opposite was the case: my mouse would only work after executing "/etc/init.d/gpm stop". Now that it's running, I have a configuration question: I'm used to tweaking XF86Config to get the resolution/bit-depth that I want, but Xpmac operates on some magic principles that I don't understand. How do I tell it these configuration values? Are there any arbitrary limitations that I need to know about? G4 w/ Rage128Pro(ATI)
Re: Xpmac.deb
After my last note, I discovered that Xpmac accepts a "-mode n" parameter that seems to do the trick. I'm can't find a table that says what the acceptable values of n are and what they mean, but I'm satisfied anyway. Thanks again!
Re: Xpmac.deb
Thanks to Andre and tigert for the information on setting the
depth -- now does anybody know what the incantation for setting
the resolution is and where I should put it?
> > Now that it's running, I have a configuration question: I'm used to
> > tweaking XF86Config to get the resolution/bit-depth that I want, but
> > Xpmac operates on some magic principles that I don't understand. How
> > do I tell it these configuration values? Are there any arbitrary
> > limitations that I need to know about?
>
> It works with command line arguments:
> % Xpmac.rev10 -h
>
> -depth # run screen at depth {8,16,24}
>
Re: kernel 2.2.17 compile problems
Michael wrote: > Don't do that, then. I'd only use the kernel.org source as base for > rsync'ing the PPC source. My understanding, from the following release notes, is that 2.2.17 stands the chance of getting us past the separate-tree madness. Could someone clarify? http://www.linux.org.uk/VERSION/relnotes.2217.html
open firmware netboot?
I have a bootable debian CD in hand (from debian-cd.com), and an old rev A iMac that refuses to boot it. The CD boots up on my G4 without fail, but with this iMac it cannot boot. (open firmware says that it has trouble reading block 0). The iMac won't even mount the CD on the desktop in MacOS, and offers to format it for me. :-/ This machine has never had trouble reading/mounting any other CDs in its history, and this same disk works fine in every machine I've tried -- so I'm at a loss. Plan B: do a tftp-style net boot from open firmware. I've heard rumorsr that some OF implementations can do this, but I can't find any documentation on what the incantation might be at the OF prompt. Has anybody accomplished something liket this? I'd love some pointers.
Re: open firmware netboot?
Ethan wrote: > > this is strange and disturbing. can it read regular ISO9660 CDs? > (debian CD 1 is hybrid ISO/HFS) Yes, it can read regular ISO9660s...what's more interesting is that we have another iMac of the same vintage that I just tested -- it boots just fine off of the same CD -- must be some subtle flaw in the cdrom drive? alignment? calibration? I don't know. > yes all newworld macs can do a netboot. all the work is involved on > your tftp/bootp server. the mac just needs to have the `n' key held > down on powerup. What happens then? does it go interactive so that I can specify an IP address, or do I need to set up some BOOTP magic? Is this documented anywhere? I'm also having troubles finding the right mkofboot incantation (yes, still) I can make yaboot start off of the Apple_Bootstrap partition, but it always complains about not finding an image. (More playing to be done, I guess.)
Re: newworld netboot mini-howto
Thanks to your timely mini-howto, I managed to install debian on the iMac with the flakey cdrom/cdrom-drive problem I posted about last night. There was only one thing that definately needs to be corrected in the document: where you suggest looking at /var/log/daemon.log to get the MAC address, we need to show how to make bootpd provide this debugging output (it's silent by default): by adding "-d 1" to the /etc/inetd.conf entry like this: bootps dgram udp waitroot/usr/sbin/bootpd bootpd -i \ -t 120 -d 1
librep5 & sawmill dependencies broken?
I recently tried to install sawmill on a debian-stable system, but dselect complained that sawmill depends upon rep, which depends upon librep5, which appears to not be available. I've tried this from several different mirrors now, all with the same results. Does anybody know the right way to satisfy this dependency?
yaboot dual boot problems
I managed to write yaboot to the Apple_Bootstrap partition so that it boots linux off of the hard drive. It's starting to make sense to me now. Unfortunately, I cannot boot into MacOS unless I command-option-o-f into open firmware and explicitly boot hd:8,\\:tbxi This is despite the fact that I deliberately copied the template from /usr/doc/yaboot/examples/menu_ofboot.b to /boot/ofboot.b, as per the docs, and edited the X's out of the boot lines: -- " get-key-map" " keyboard" open-dev $call-method dup 20 dump 5 + c@ 08 = if " Booting MacOS ..." cr " boot hd:8,\\:tbxi" eval else " Booting Yaboot ..." cr " boot hd:5,yaboot" eval then -- (/dev/hda5 is the Apple_Bootstrap, /dev/hda8 is the HFS MacOS slice) How do I interpret what is intended by this script? Am I supposed to be getting icons at boot time, or do I need to press some key? I've tried holding the spacebar down, as suggested in the FAQ[1], but that gets me nowhere. I'm going straight into yaboot's "boot:" prompt, and don't seem to have keyboard control and have to wait for the timeout. My yaboot.conf file is given below. [1] http://www.alaska.net/~erbenson/doc/yaboot-faq.html -- ## example yaboot.conf for ybin and yaboot 0.6 ## see man yaboot.conf for more details. ## change to your bootstrap partition ie /dev/hda2 device=hd: timeout=50 magicboot=/boot/ofboot.b boot=/dev/hda5 install=/boot/yaboot image=/vmlinux label=linux root=/dev/hda7 partition=7 read-only --
Re: yaboot dual boot problems
Ethan wrote: > > this is ybin 0.16, 0.16 sucks ;-) > > install 0.21, you can get a deb from http://them.org/~drow/debian There was a routing problem between us and them.org (and I was impatient to try your suggestion) so I grabbed the tarball for ybin 0.21 off of alaska.net. Since I wasn't using the deb, I didn't have to worry about the .sh extension on the ofboot.b file. Other than that, the yaboot.conf file is exactly as you suggested: - device=hd: delay=5 timeout=50 magicboot=/boot/ofboot.b boot=/dev/hda5 install=/boot/yaboot macos=/dev/hda8 image=/vmlinux label=linux root=/dev/hda7 partition=7 read-only - When installed with mkofboot or ybin, everything appears to go fine, with the exception of a warning about nvsetenv being an incompatible version. Upon reboot, all I get is the flashing question-mark-on-a-folder after a pause. I tried explicitly going into OF and setting setenv boot-device hd:5,\\:tbxi then boot But it complains: can't OPEN: hd:5,yaboot I tried this with the 0.6 yaboot that I was using before, and with the 0.7 binary that came in ybin-0.21.tar.gz, with the same result each time. P.S. I'm really appreciating the netboot mini-howto, by the way. It's a nice safety-net to have that set up.
Re: yaboot dual boot problems
Ethan wrote: > i think your OpenFirmware configuration is fscked... Last night I had made sure (using "which ybin", "which mkofboot", and "which ofpath") that the new 0.21 binaries were the ones being found. I deleted the old binaries entirely before running mkofboot...and I _did_ run "mkofboot -v", as you suggested -- and answered "Y" when it asked to create an hfs filesystem, so the old stuff in Apple_Bootstrap should have been obliterated. The magicboot variable was even pointing to the new ofboot.b script, and I repeated this in its entirety, zapping the nvram exactly as you describe here: > 3) shutdown your mac, and hold down command option p r while booting > it, keep these keys down till it reboots itself 3 times. The results were the same...I also incorporated Matt Brubeck's suggestion of setting the boot-device parameter like this: setenv boot-device hd:5,ofboot.b After using this setting, when I type "boot" (in OF, after doing this setenv incantation), it gives the same error as before: can't OPEN: hd:5,yaboot I take this to mean that the ofboot.b wrapper is being executed, and that it is, in turn, trying to execute yaboot to bring up linux but is unable to open the yaboot file. I noticed that I can traceroute all the way to them.org today, so I'm going to grab the two debs (ybin & powerpc-utils), remove the stuff in /usr/local/sbin, and see if the proper "nvsetenv" is able to make the difference between failure and success.
Re: yaboot dual boot problems (success!)
Ethan, Matt...thank you for your assistance. I've broken through the fog...the powerpc-utils must have made all the difference. I've bounced this baby about a dozen times, adjusted the delay and defaultos to where I'm satisifed. Awesome. Thanks again. P.S. This is my son's machine...he wants me to teach him Hello World in C in linux, and thanks to your help he can go from one partition to another with ease.
2.2.17, usb, and G4
I'm trying to build a kernel from stock source to see if it can be done, and managed to boot one that worked well except for usb support. All usb devices were unresponsive, but I could ssh into the box and see the following in the logs: Sep 18 21:49:18 obelisk kernel: OHCI USB Driver loading Sep 18 21:49:18 obelisk kernel: USB HID boot protocol mouse registered. Sep 18 21:49:18 obelisk kernel: usb-ohci: USB HC reset timed out! Has anybody made a bootable kernel from the stock source tree for a G4? Or is this a known problem? Or, maybe there's something about my configuration that's wrong? # # Automatically generated by make menuconfig: don't edit # # # Platform support # CONFIG_PPC=y CONFIG_6xx=y # CONFIG_8xx is not set CONFIG_PMAC=y # CONFIG_PREP is not set # CONFIG_CHRP is not set # CONFIG_ALL_PPC is not set # CONFIG_APUS is not set # CONFIG_GEMINI is not set # CONFIG_MBX is not set # CONFIG_SMP is not set # CONFIG_ALTIVEC is not set CONFIG_MACH_SPECIFIC=y CONFIG_6xx=y # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_MODULES=y # CONFIG_MODVERSIONS is not set CONFIG_KMOD=y CONFIG_PCI=y # CONFIG_PCI_QUIRKS is not set CONFIG_PCI_OLD_PROC=y CONFIG_NET=y CONFIG_SYSCTL=y CONFIG_SYSVIPC=y # CONFIG_BSD_PROCESS_ACCT is not set CONFIG_BINFMT_ELF=y CONFIG_KERNEL_ELF=y CONFIG_BINFMT_MISC=m # CONFIG_BINFMT_JAVA is not set # CONFIG_PARPORT is not set # CONFIG_VGA_CONSOLE is not set CONFIG_FB=y # CONFIG_PMAC_PBOOK is not set # CONFIG_MAC_KEYBOARD is not set # CONFIG_MAC_FLOPPY is not set # CONFIG_MAC_SERIAL is not set # CONFIG_PPC_RTC is not set # CONFIG_ADBMOUSE is not set CONFIG_PROC_DEVICETREE=y # CONFIG_TOTALMP is not set # CONFIG_BOOTX_TEXT is not set # CONFIG_MOTOROLA_HOTSWAP is not set # # Plug and Play support # # CONFIG_PNP is not set # # Block devices # # CONFIG_BLK_DEV_FD is not set CONFIG_BLK_DEV_IDE=y # CONFIG_BLK_DEV_HD_IDE is not set CONFIG_BLK_DEV_IDEDISK=y CONFIG_BLK_DEV_IDECD=y # CONFIG_BLK_DEV_IDETAPE is not set CONFIG_BLK_DEV_IDEFLOPPY=y # CONFIG_BLK_DEV_IDESCSI is not set # CONFIG_BLK_DEV_CMD640 is not set # CONFIG_BLK_DEV_RZ1000 is not set CONFIG_BLK_DEV_IDEPCI=y CONFIG_BLK_DEV_IDEDMA=y # CONFIG_BLK_DEV_OFFBOARD is not set CONFIG_IDEDMA_AUTO=y # CONFIG_BLK_DEV_OPTI621 is not set # CONFIG_BLK_DEV_TRM290 is not set # CONFIG_BLK_DEV_NS87415 is not set # CONFIG_BLK_DEV_VIA82C586 is not set CONFIG_BLK_DEV_CMD646=y # CONFIG_BLK_DEV_CS5530 is not set # CONFIG_BLK_DEV_SL82C105 is not set CONFIG_BLK_DEV_IDE_PMAC=y CONFIG_BLK_DEV_IDEDMA_PMAC=y CONFIG_BLK_DEV_IDEDMA=y CONFIG_PMAC_IDEDMA_AUTO=y # CONFIG_IDE_CHIPSETS is not set CONFIG_BLK_DEV_LOOP=y # CONFIG_BLK_DEV_NBD is not set # CONFIG_BLK_DEV_MD is not set CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_SIZE=4096 CONFIG_BLK_DEV_INITRD=y # CONFIG_BLK_DEV_XD is not set # CONFIG_BLK_DEV_DAC960 is not set CONFIG_PARIDE_PARPORT=y # CONFIG_PARIDE is not set # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_DEV_HD is not set # # Networking options # CONFIG_PACKET=y CONFIG_NETLINK=y # CONFIG_RTNETLINK is not set # CONFIG_NETLINK_DEV is not set # CONFIG_FIREWALL is not set # CONFIG_FILTER is not set CONFIG_UNIX=y CONFIG_INET=y CONFIG_IP_MULTICAST=y # CONFIG_IP_ADVANCED_ROUTER is not set # CONFIG_IP_PNP is not set # CONFIG_IP_ROUTER is not set # CONFIG_NET_IPIP is not set # CONFIG_NET_IPGRE is not set # CONFIG_IP_MROUTE is not set CONFIG_IP_ALIAS=y # CONFIG_SYN_COOKIES is not set CONFIG_INET_RARP=y CONFIG_SKB_LARGE=y # CONFIG_IPV6 is not set # CONFIG_IPX is not set CONFIG_ATALK=m # CONFIG_X25 is not set # CONFIG_LAPB is not set # CONFIG_BRIDGE is not set # CONFIG_LLC is not set # CONFIG_ECONET is not set # CONFIG_WAN_ROUTER is not set # CONFIG_NET_FASTROUTE is not set # CONFIG_NET_HW_FLOWCONTROL is not set # CONFIG_CPU_IS_SLOW is not set # # QoS and/or fair queueing # # CONFIG_NET_SCHED is not set # # SCSI support # CONFIG_SCSI=y CONFIG_BLK_DEV_SD=y CONFIG_CHR_DEV_ST=y CONFIG_BLK_DEV_SR=y CONFIG_BLK_DEV_SR_VENDOR=y # CONFIG_CHR_DEV_SG is not set # CONFIG_SCSI_MULTI_LUN is not set CONFIG_SCSI_CONSTANTS=y # CONFIG_SCSI_LOGGING is not set # # SCSI low-level drivers # # CONFIG_BLK_DEV_3W__RAID is not set # CONFIG_SCSI_7000FASST is not set # CONFIG_SCSI_ACARD is not set # CONFIG_SCSI_AHA152X is not set # CONFIG_SCSI_AHA1542 is not set # CONFIG_SCSI_AHA1740 is not set CONFIG_SCSI_AIC7XXX=y # CONFIG_AIC7XXX_TCQ_ON_BY_DEFAULT is not set CONFIG_AIC7XXX_CMDS_PER_DEVICE=8 CONFIG_AIC7XXX_PROC_STATS=y CONFIG_AIC7XXX_RESET_DELAY=15 # CONFIG_SCSI_IPS is not set # CONFIG_SCSI_ADVANSYS is not set # CONFIG_SCSI_IN2000 is not set # CONFIG_SCSI_AM53C974 is not set # CONFIG_SCSI_MEGARAID is not set # CONFIG_SCSI_BUSLOGIC is not set # CONFIG_SCSI_DTC3280 is not set # CONFIG_SCSI_EATA is not set # CONFIG_SCSI_EATA_DMA is not set # CONFIG_SCSI_EATA_PIO is not set # CONFIG_SCSI_FUTURE_DOMAIN is not set # CONFIG_SCSI_GDTH is not set # CONFIG_SCSI_GENERIC_NCR5380 is not set # CONFIG_SCSI_INITIO is not set # CONFIG_SCSI_INIA100 is not set # CONFIG_SCSI_NCR53C406A is not set # CONFIG_SC
Re: 2.2.17, usb, and G4
Ethan wrote: > > if you need to use USB then you must get the 2.3 USB backport. Is this in what I've heard referred to as "Paul's rsync tree"? In either case, where can I find it?
Re: Need Help USB keyboard mouse problem when make new kernel
> I'm using a old 2.2.6-15apmac kernel on my Imac Rev B box (G3 266 Mhz) > with bootX 1.2, all work perfectly. I try to use a new kernel, and I > 'have built > some differents kernel rev (2.2.13, 2.2.14, 2.2.15, 2.2.17 ) and I have > always > get USB troubles, with the keyboard and mouse. I had the same problem recently on a G4. It turned out that some critical USB patches for PPC are simply not yet in the main source tree. There are rumors that 2.2.18 might contain the missing magic, but for now you have to use rsync to grab sources from here: http://linuxcare.com.au/paulus/kernels.html [EMAIL PROTECTED]
Re: compile airport, dual boot
> > btw: www.linuxppc.org evaluates to www.linuxppc.com > > Not for me. You probably have a caching nameserver somewhere > that needs to be kicked real hard. The problem traces back to > a botched zone data change for linuxppc.org that had a lot of > name servers confused. But that's been months ago. I wondered what had happened. I'm seeing the same thing. I've tried from several networks: bash-2.03$ nslookup www.linuxppc.org Server: dns1.gallup.com Address: 198.175.140.220 Non-authoritative answer: Name:www.linuxppc.org Address: 169.207.161.4 bash-2.03$ nslookup www.linuxppc.com Server: dns1.gallup.com Address: 198.175.140.220 Name:www.linuxppc.com Address: 169.207.161.4 [EMAIL PROTECTED]
Re: usb support
> I am currently trying to install debian on a powermac g4, and usb > seems to be causing some problems. Just to experiment, I tried booting > without the keyboard and mouse plugged in, and it booted ok, but of > course I couldn't go anywhere from there. Could anyone tell me what's > going on??? Also, if anyone has installed successfully on a similar > machine, telling me any quirks they ran into would be great too. Any > help would be greatly appreciated!!! I'm running debian on a g4 without any usb problems. Are you trying to build your own kernel? I know that many people (including myself) have tried to build a custom kernel from stock source only to find that the usb support isn't in the standard source tree yet. If that's the case, it's still necessary to use "rsync" to get the kernel sources from here... http://linuxcare.com.au/paulus/kernels.html If you're not building your own kernel, your problem could be somewhere else, like your configuration of your Xserver. Are you booting directly into X, or do you get to a plain text-based console? [EMAIL PROTECTED]
Re: usb support
> p.s. I'm using bootx, which is not recommended for new-worlds, but I don't > know what else to use, and i'm not at all sure that that's the problem. This could account for it. I had to use yaboot when installing on my G4. http://www.alaska.net/~erbenson/ I had a zip drive to boot off of, which was very helpful. The steps went something like this: 1) HFS format a zip disk 2) On the zip disk, place the yaboot binary, a suitable yaboot.conf file, a kernel, and the installation boot image. In my case, the files were yaboot yaboot.conf vmlinux-2.2.15pre14-ben1 ramdisk.image.gz Ugh, I've been racking my brain to remember exactly what the yaboot.conf file looked like, but can't off the top of my head. 3) While the machine is booting, press CTRL-APPLE-O-F to get into the open firmware prompt. 4) Once you're in the open firmware prompt, type boot zip:yaboot where "yaboot" is the name you saved the yaboot binary as, which was, at one time, "yaboot_0.6" in my case. This will start the installation process. Yaboot is also the bootloader you want to use to boot into linux after you're done with the installation. At first I modified my yaboot.conf file on the zip disk to boot from my hard drive. This gave me time to figure out getting yaboot written to the Apple_Bootstrap partition. I used the mac-fdisk program (from within the debian installer) to make an 800K partition (1600 blocks) called "yaboot" of type "Apple_Bootstrap". The name of the partition doesn't matter, but the type does: it keeps Apple's disk partitioning tools from clobbering your yaboot partition. I placed this partition after all the Apple_Driver_* and Apple_Patches partitions. Here's my partition table for inspiration: #type name length base /dev/hda1 Apple_partition_map Apple 63 @ 1 /dev/hda2 Apple_Driver43 Macintosh 54 @ 64 /dev/hda3 Apple_Driver43 Macintosh 74 @ 118 /dev/hda4Apple_Driver_ATA Macintosh 54 @ 192 /dev/hda5Apple_Driver_ATA Macintosh 74 @ 246 /dev/hda6 Apple_FWDriver Macintosh 200 @ 320 /dev/hda7 Apple_Driver_IOKit Macintosh 512 @ 520 /dev/hda8 Apple_Patches Patch Partition 512 @ 1032 /dev/hda9 Apple_Bootstrap yaboot 1600 @ 1544 /dev/hda10Apple_UNIX_SVR2 one 2589353 @ 3144 /dev/hda11Apple_UNIX_SVR2 two 2097152 @ 2592497 /dev/hda12Apple_UNIX_SVR2 swap 260069 @ 4689649 /dev/hda13Apple_UNIX_SVR2 three11580065 @ 4949718 /dev/hda14 Apple_HFS untitled 33536457 @ 16529783 /dev/hda15 Apple_Free Extra 11 @ 20066240 Once the installation was over with, getting yaboot written to its partition took some playing. There's a program called "ybin" that does this job for you. Incidentally, there's an alternate name under which you invoke "ybin", called "mkofboot". Invoking it this way causes the bootstrap partition to be freshly formatted (HFS). You have to do this the first time you run ybin. Running it this way also helps to make sure an old configuration is properly overwritten. There were a couple of deb packages that I needed that were NOT on the installation CD. You see, the ybin program needs to run a program called "nvsetenv" in order to make OpenFirmware boot off of the yaboot partition automagically -- but it needed to be a more recent version of nvsetenv than was in potato when it was released. You can get it by installing http://screaming.org/~pohl/powerpc-utils_1.1.3-2_powerpc.deb Someone else may have a more recent version. This was the one that got me going. [EMAIL PROTECTED]
Re: floppy low-level format
Ethan Benson <[EMAIL PROTECTED]> wrote: > > On Tue, Dec 05, 2000 at 05:13:25PM +0100, Andre Berger wrote: > > I haven't figure out yet how to do a low-level format on > > /dev/fd0 on PPCs, can anybody help me? > > i don't think you can... the tool used for this is superformat > which function on ppc it does not. Maybe I'm misunderstanding what "low-level format" implies, but you should be able to use mkfs like this: mkfs -t ext2 -c -v /dev/fd0 I don't have a ppc machine with a floppy though, so I can't test it. [EMAIL PROTECTED]
