Re: debian-powerpc: Keyspan USB to serial converter works :)
Brendan J Simon wrote: I haven't used it in depth yet. I just got my embedded system to output it's boot screen and that was enough for me. It was late so I headed off to bed. The system outputs at 9600 bps and I didn't have to change any settings. I setup minicom to default to 9600 and everything worked fine. I didn't have to bump the speed up or down. I think this is in the Belkin USB-Serial driver, but I can live with it for now. I tried to add a call to set the baud to 9600 in the startup code, but that wasn't happy with that...:-/ I reverted back to my original and will send a message to the guy who wrote the driver (it says he didn't have any information and snoop'd a Win box to get the information he was able to get). I can do either. I'd prefer not to cross compile but it doesn't really matter. I laptop is a powerpc machine and this is the machine I will be using when travelling and going to robotics competitions so this will be my default machine for compilation too (just in case I have to make some last minute hacks when on the road). Well, I would prefer not to cross compile either, but in this case I would need a ppc 823 chip to make it native, and that would be PAINFUL. BTW, if you haven't seen, Linux Journal came out with a new magazine named Embedded Linux Journal. In the current issue (2nd one to hit the shelves) there is a pretty cool article by Bruce Perens titled Building Tiny Linux Systems with Busybox, which is pretty cool, he shows how to create a system that boots off a floppy using busybox with compression. The project I'm working on is using busybox, it's very cool for embedded. I just checked online, but that article is not there, but listed. MacOS is good, but it doesn't compare to the flexibility of Linux or some other the other free UNIX clones. Debian is my system of choice. MacOS is ok, but quite honestly when I got my PowerBook I was disappointed in the fact that MacOS crashes as much as it does (not as often as Win, which I won't use, but enough that it is an embarrassment to Apple, IMO). My linux boxes never go down like MacOS, and it's nice to have a functional linux on my PowerBook. Mac OSX public beta is more stable than Mac OS9, but the BSD core is hacked up so most of the ports wouldn't work on it anyway...Apple is painting themselves in the corner, IMO. They should have gone with Linux and added Aqua on top of it. None the less, Linux works better for me than Mac OSX, and most all of my tools are available for ppc linux that I've used on i386 linux. As far as distros, I only use Debian on my linux boxes, and when I was hired for the current project I'm working on, my boss said I could use Debian, even though the rest of the people use Red Hat (they didn't know any better, and they are starting to see the apt-get light at the end of the tunnel...;-) It was pretty painful getting Debian going on the PowerBook, and getting things setup. Much worse than I would expect most people to be dragged through. I hope others had an easier time... -- Alan DuBoff Software Orchestration, Inc.
Unidentified subject!
I would like to install Debian GNU/Linux 2.2 r0 Potato - Official powerpc Binary-1 CD on my powerbook G4, 5OOMo. I didn't geet the chance to install it, i don't know how to begin since i can not boot on the CD, which doesn't seem bootable do you have any advice? thank's -- Anne Vanet UPR 9073 du CNRS Institut de Biologie Physico-Chimique 13 rue Pierre et Marie Curie 75005 Paris [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.sollab.org/ tel: (33) 1 58 41 51 40 Fax: (33) 1 58 41 50 20
Re: airport driver
On Sun, Mar 04, 2001 at 04:33:25PM -0800, Alan DuBoff wrote: I have woody installed on a PowerBook (most recent G3 before new titaniam G4, the 2000 model, the Firewire model, Pismo, etc...call it what you like), which has an airport card in it that I would really like to use. I'm using a 2.2.18 kernel, and it is linked into /usr/src/linux. I grabbed the airport driver from www.penguinppc.org/~benh but can't get it to compile. Do I need to incorporate that directory into my kernel tree and be in: /usr/src/linux/modules/pcmcia-cs/wireless Or what is the magic trick to get the airport to compile? I've got most things worked out and the PowerBook rocks, and the last few things I'll resort to this list for help. HELP!g hmm well I had problems getting my airport driver from ben's site to compile when I got my airport card for my same model pismo, however I was using it with 2.4.*, anyway I posted a quick hack of a patch to linuxppc-dev list that would allow trhe thing to compile and be used, so I have been using that hapily since. You may want to have a look back in that mailing list's archive and use the patch or not, the two changes were pretty obvious. The change from using dev-name = s; to strncpy (dev-name, s, strlen (whatever)) is a 2.4 ism, the other thing was just something stopping it from building, anyway good luck. See You Steve -- [EMAIL PROTECTED] http://wibble.net/~sjh/ Look Up In The Sky Is it a bird? No Is it a plane? No Is it a small blue banana? YES
Re: Mac partitioning probs
On Sun, 4 Mar 2001, Taro Fukunaga wrote: What kind of partitions do you have on sda? You need one root and one swap at least. I made (in order, if I recall correctly): 250Mb Swap 125Mb Root 125Mb Tmp 500Mb Var 2Gb Usr remainder (around 1.3Gb I think) Home And there was the (I think) 32Kb partition map at the very beginning. Matthew.
Re: Mac partitioning probs
On Sun, 4 Mar 2001, Ethan Benson wrote: My next problem is that the kernel doesn't seem interested in recognising the partition table that I create on the disk. what kernel? did you compile it yourself? if so it looks very much like forgot to turn on support for mac partition tables. It's the Debian install kernel from /debian/dists/potato/powerpc/powermac/ (or something similar, I forget the exact URL). Partition check: sda: sda1 something is strange here, it sees one partition... mac-fdisk will happily display what's on sdb (the MacOS disk) and on sda (where Debian will live). post the output of mac-fdisk -l /dev/sda Will do when I get home tonight. For now, we have: I made (in order, if I recall correctly): 250Mb Swap 125Mb Root 125Mb Tmp 500Mb Var 2Gb Usr remainder (around 1.3Gb I think) Home And there was the (I think) 32Kb partition map at the very beginning. Matthew.
Re: Mac partitioning probs
My next problem is that the kernel doesn't seem interested in recognising the partition table that I create on the disk. Did that disk have a DOS partition table on it before? I've had to erase the first few megs of a disk in order to get it to honor the Mac partition table instead of the old DOS partition table. It's a matter of partition table parse order (stick the mac_partition call before dos_partition in genhd.c and it might work without overwriting). Michael
Re: Mac partitioning probs
On Mon, 5 Mar 2001, Michael Schmitz wrote: My next problem is that the kernel doesn't seem interested in recognising the partition table that I create on the disk. Did that disk have a DOS partition table on it before? I've had to erase the first few megs of a disk in order to get it to honor the Mac partition table instead of the old DOS partition table. It's a matter of partition table parse order (stick the mac_partition call before dos_partition in genhd.c and it might work without overwriting). Ah, I think you have probably hit the nail on the head there. I'll try that tonnight and report back. Many thanks, Matthew.
Re: Mac partitioning probs
On Mon, Mar 05, 2001 at 11:48:30AM +, Matthew Kirkwood wrote: post the output of mac-fdisk -l /dev/sda Will do when I get home tonight. this is a long shot but did this disk used to have a x86 partition table on it? i am not certain that mac-fdisk zeros out the first block, and the way mac partition tables are structured its actually possible to have both a x86 partition table and a mac partition table at the same time, both with completely different data. if there is a x86 partition table the kernel will probably see it first. For now, we have: I made (in order, if I recall correctly): 250Mb Swap 125Mb Root 125Mb Tmp 500Mb Var 2Gb Usr remainder (around 1.3Gb I think) Home And there was the (I think) 32Kb partition map at the very beginning. yes there should be, apple partition tables are kept in a apple partition. wierd eh? also note if this is a newworld box you need to create an 800K Apple_Bootstrap partition if you want this disk to ever be bootable. -- Ethan Benson http://www.alaska.net/~erbenson/ pgpILtMSMiz1B.pgp Description: PGP signature
Re: Mac partitioning probs
On Mon, Mar 05, 2001 at 01:11:55PM +0100, Michael Schmitz wrote: My next problem is that the kernel doesn't seem interested in recognising the partition table that I create on the disk. Did that disk have a DOS partition table on it before? I've had to erase the first few megs of a disk in order to get it to honor the Mac partition table instead of the old DOS partition table. It's a matter of partition table parse order (stick the mac_partition call before dos_partition in genhd.c and it might work without overwriting). actually all thats needed is a very careful dd of /dev/zero. x86 partition tables are only 66 bytes (iirc) at the end of the first block (512 bytes). there is a mac partition signature at the first byte, but this is normally empty on x86 partitions since thats where the bootloader goes. -- Ethan Benson http://www.alaska.net/~erbenson/ pgpEgSBSzLqGc.pgp Description: PGP signature
Re: Mac partitioning probs
At 03:29 -0900 3/5/2001, Ethan Benson wrote: this is a long shot but did this disk used to have a x86 partition table on it? i am not certain that mac-fdisk zeros out the first block, and the way mac partition tables are structured its actually possible to have both a x86 partition table and a mac partition table at the same time, both with completely different data. if there is a x86 partition table the kernel will probably see it first. Actually I may be having this problem with a disk I'm monkeying around with right now. Is there a way to wipe the x86 partition from Linux or do I need to initialize it in MacOS first? Kevin
Re: Mac partitioning probs
On Mon, Mar 05, 2001 at 07:22:50AM -0600, Kevin van Haaren wrote: Actually I may be having this problem with a disk I'm monkeying around with right now. Is there a way to wipe the x86 partition from Linux or do I need to initialize it in MacOS first? you never need MacOS. if you don't mind trashing any mac partition table you have attempted to put on there this will do: dd if=/dev/zero of=/dev/hda bs=512 count=1 that will remove an x86 partition table completely. it will also ruin a mac partition table (since the signature for mac tables is stored on the very first byte of the disk) if you want to preserve the mac table and just nuke the x86 table i think this will do: dd if=/dev/zero of=/dev/hda bs=1 seek=446 count=66 doing a quick test this seems to work. -- Ethan Benson http://www.alaska.net/~erbenson/ pgpK6ye6I9FNQ.pgp Description: PGP signature
debian2.2r2 on powerbook G4
Hi, I'm trying to install debian on a powerbook G4 (titanium). as the cd is non bootable, I grab the linux kernel and ramdisk.image.gz from /potato/main/disks-powerpc/2.2.19-2000-12-03/powermac/ to a mac partition of the disk, wich contains yaboot yaboot.conf (edited and modified) booting under OF to yaboot is OK, yaboot start to load the kernel, but everything stops with the following message. opening display /[EMAIL PROTECTED]/ATY,[EMAIL PROTECTED]/ATY,rageM3p12B_ somebody knows how to boot this machine. should I compile a new kernel on my pismo, and try with this new one ?? any advice ?? Thank's Eric -- TN: Hahahahahah ! Ma copine aussi est utilisable sous Linux ;-) ST: C'est quelle version , ta copine ? TN: Beta 1 ;-))) JP: C'est quel type de license ? -+- TN in Guide du linuxien pervers : pas le rouleau à patisserie
Re: HOW-TO : Debian on NuBus
I'm having trouble downloading the ramdisk installer. (It's really really slow...) Is there a mirror in the US that has the Installer? thanks. --markemmanuel Quoted from the Book of Paul Kimber Ch 6:7-13 on 3/4/01 8:46 PM: We now have a working ramdisk installer, so it is now much easier to install debian on nubus. Just grab the fake 'Mach Kernel' and the MkLinux Booter from ftp://penguin.tough.net.au change your root device to /dev/ram and reboot. Its that easy. If you have any problems just mail me. This is still a work in progress. Cheers, paul |- |penguin.tough.net.au |__
Re: debian-powerpc: Keyspan USB to serial converter works :)
In newsgate.debian.powerpc, Brendan J Simon wrote: I'd just like to let everyone know that I got my Keyspan USB to Serial converter working last night. Additionally, the Keyspan PDA USB serial converter also works fine under the last kernel I checked (including the USB backport in 2.2.x). -- rob off list/ng replies: [EMAIL PROTECTED]
Re: airport driver
Steven Hanley wrote: hmm well I had problems getting my airport driver from ben's site to compile when I got my airport card for my same model pismo, however I was using it with 2.4.*, anyway I posted a quick hack of a patch to linuxppc-dev list that would allow trhe thing to compile and be used, so I have been using that hapily since. You may want to have a look back in that mailing list's archive and use the patch or not, the two changes were pretty obvious. The problems I was getting were with redefinitions, and I tried pathing in /usr/src/linux/include as some stuff was called with linux/xxx.h which were located in /usr/src/linux/include/linux, but that didn't help and gave other redefinition errors. I'm using a 2.2.18 kernel, and even though I would like to upgrade to the 2.4.x kernel, I want to continue to try and get e2compr going (the kernel patch worked for 2.2.18 with one minor mod which I have sent a message to the maintainers), but the patch to the e2fsprogs didn't compile after it was patched. Anyway, I use this to compile a compressed image that I can flash over the net, and would like to be able to do that if possible. The change from using dev-name = s; to strncpy (dev-name, s, strlen (whatever)) is a 2.4 ism, the other thing was just something stopping it from building, anyway good luck. Thanks for the info Steve, I'll dig around the linuxppc-dev list and see if I can find your patch. -- Alan DuBoff Software Orchestration, Inc.
Re: debian2.2r2 on powerbook G4
Eric Deveaud wrote: I'm trying to install debian on a powerbook G4 (titanium). as the cd is non bootable, I grab the linux kernel and ramdisk.image.gz from /potato/main/disks-powerpc/2.2.19-2000-12-03/powermac/ No, that CD is bootable. The trick is knowing how to force the G4 titanium into booting from the CD. For my Pismo, this information was pointed out from a friend who knew it from their iBook, but it was located in the Troubleshooting section of the Getting Started book that came with the PowerBook. For the Pismo you hold down the C key while booting. should I compile a new kernel on my pismo, and try with this new one ?? any advice ?? I think you are better off getting the CD to boot and building the kernel on the titanium. I don't like the concept of building a kernel on another machine, since the hardware could be and probably is different, it gets confusing knowing which .config you used...just my $0.02, take it with a grain of salt. The two machines are similar, so you could do that though. BTW, please post the secret key combo when you find out how to force a boot from the CD, I think others will need to know that eventually. It might even be me if I get a titanium...(looking over shoulder to see if wife is watching me type;-). -- Alan DuBoff Software Orchestration, Inc.
Crash! kernel 2.4.2 jumps to mon
Hello everybody! For the first time in my life i saw mon. This happend to me when I tried to delete some files from a hfs partition. At the bottom of the screen I read kernel BUG at /usr/src/linux/include/linux/dcache.h:244! and at the top vector: 0 at pc = c00789F8 I´m running kernel 2.4.2 from ppc.linuxcare.com Hope some developers can see what went wrong. If someone needs more info, I try to reproduce this bug. Bye, Christoph -- Dipl. Ing. Christoph EweringC E Informationsdienste GbR 0 52 54 80 68 66 oder 0173 566 266 1 [EMAIL PROTECTED]
Re: evolution etc...
On Sun, Mar 04, 2001 at 09:26:10PM +1100, thus said Craige McWhirter: Toumas, not having really used the Evolution address book (I'm back to using Balsa/Mutt) I gave it a whirl and experienced exactly what you described. I could watch (with gkrellm) my RAM and swap get gobbled up. I averted a crash only by closing Evolution just before the swap filled up. It also works fine on my i386 machine. Scary stuff ;) Yep, but bugs happen when stuff is in progress.. :) Thanks for help though, I now know that it is just not my machine, but looks more likely that it is an endianness issue or something else that is processor architecture specific. Next I guess I gotta look with Chris (the addressbook dude) whether it crashes on Sparc too etc.. Duh. Well, good that I went for the Pismo instead of an IBM laptop, the end result would be one ppc-specific bug less.. Tuomas -- .--- [EMAIL PROTECTED].|\,/| [EMAIL PROTECTED] -. + www.ximian.com - ()-@@ , tigert.gimp.org + `- art director , `--')/ a gimp artist ---'
Re: Crash! kernel 2.4.2 jumps to mon
Can you send me your System.map for that kernel? The linuxcare.com kernels that Paul keeps have changes that he's not ready to push into the main tree yet. It's likely you discovered one of the reasons he holds off on pushing his changes :) You may want let Paul know, too. } For the first time in my life i saw mon. } This happend to me when I tried to delete some files from a hfs partition. } } At the bottom of the screen I read kernel BUG at /usr/src/linux/include/linux/dcache.h:244! } and at the top vector: 0 at pc = c00789F8 } } I´m running kernel 2.4.2 from ppc.linuxcare.com } } Hope some developers can see what went wrong. } If someone needs more info, I try to reproduce this bug. } } Bye, } Christoph } } -- } Dipl. Ing. Christoph EweringC E Informationsdienste GbR } 0 52 54 80 68 66 oder 0173 566 266 1 } [EMAIL PROTECTED] } } } -- } To UNSUBSCRIBE, email to [EMAIL PROTECTED] } with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian2.2r2 on powerbook G4
On Mon, Mar 05, 2001 at 01:16:32PM -0800, Alan DuBoff wrote: Eric Deveaud wrote: I'm trying to install debian on a powerbook G4 (titanium). as the cd is non bootable, I grab the linux kernel and ramdisk.image.gz from /potato/main/disks-powerpc/2.2.19-2000-12-03/powermac/ No, that CD is bootable. The trick is knowing how to force the G4 titanium its bootable, but the kernel on it may not like this hardware since its so new. into booting from the CD. For my Pismo, this information was pointed out from a friend who knew it from their iBook, but it was located in the Troubleshooting section of the Getting Started book that came with the PowerBook. For the Pismo you hold down the C key while booting. yes. try passing `video=ofonly' on the yaboot boot prompt, the video on that machine may not be supported by this kernel. should I compile a new kernel on my pismo, and try with this new one ?? any advice ?? I think you are better off getting the CD to boot and building the kernel on the titanium. I don't like the concept of building a kernel on another machine, since the hardware could be and probably is different, it gets confusing knowing which .config you used...just my $0.02, take it with a grain of salt. The two machines are similar, so you could do that though. BTW, please post the secret key combo when you find out how to force a boot from the CD, I think others will need to know that eventually. It might even be me if I get a titanium...(looking over shoulder to see if wife is watching me type;-). you hold down the `c' key to boot from CDs. -- Ethan Benson http://www.alaska.net/~erbenson/ pgpjveavVXckF.pgp Description: PGP signature
Re: debian2.2r2 on powerbook G4
On Mon, Mar 05, 2001 at 01:16:32PM -0800, Alan DuBoff wrote: I think you are better off getting the CD to boot and building the kernel on the titanium. I don't like the concept of building a kernel on another machine, since the hardware could be and probably is different, That's totally bogus. Nothing depends on the hardware of the computer the kernel is compiled on. With a cross-compiler, you should be able to use a fast PPC to compile a kernel on an old x86 laptop. it gets confusing knowing which .config you used...just my $0.02, take it with a grain of salt. The two machines are similar, so you could do that though. The .config files are the only confusing part. I usually copy .config to /usr/src/machinename.conf when I'm done. I use my P200MMX desktop machine to compile kernels for my slower x86 machines, a P75 and a 486 laptop. The laptop didn't (until a recent factor-of-20 upgrade to disk space :) have enough room for the kernel source tree, and it would have taken all day to compile 2.4.2 on it with 20MB of RAM. My PPC machine compiles its own kernel, because it's easier to do that than install a cross compiler to compile my x86 kernels on it. You can switch .config files by copying a new one in and running make oldconfig. -- #define X(x,y) x##y Peter Cordes ; e-mail: X([EMAIL PROTECTED] , ns.ca) The gods confound the man who first found out how to distinguish the hours! Confound him, too, who in this place set up a sundial, to cut and hack my day so wretchedly into small pieces! -- Plautus, 200 BCE
Re: Mac partitioning probs
At 05:02 -0900 3/5/2001, Ethan Benson wrote: you never need MacOS. if you don't mind trashing any mac partition table you have attempted to put on there this will do: dd if=/dev/zero of=/dev/hda bs=512 count=1 that will remove an x86 partition table completely. it will also ruin a mac partition table (since the signature for mac tables is stored on the very first byte of the disk) if you want to preserve the mac table and just nuke the x86 table i think this will do: dd if=/dev/zero of=/dev/hda bs=1 seek=446 count=66 doing a quick test this seems to work. This seemed to fix the problem i was having. It'll be a couple of runs of badblocks before I really trust it, but it did mkfs the correct partition at the correct size. Thanks, Kevin
Re: debian2.2r2 on powerbook G4
Peter Cordes wrote: That's totally bogus. Nothing depends on the hardware of the computer the kernel is compiled on. With a cross-compiler, you should be able to use a fast PPC to compile a kernel on an old x86 laptop. This was not meant to imply that you couldn't compile a kernel on the Pismo for the Titanium, however, I haven't done any or seen any testing. I've seen mixed results of ppc linux running on the G4. So, I certainly wouldn't commit to code being able to run on the Titanium, since it has a different chip. Latest report is that it runs fine, but I don't know if that is for the 400mhz or 500mhz or just what. They should be the same, but there could be some timing issues arise, I don't know. The .config files are the only confusing part. I usually copy .config to /usr/src/machinename.conf when I'm done. Yes, and the main reason I don't like to do that...because if you forget to copy the .config and build a bad kernel for the wrong machine, it could cause problems as the two PowerBooks will probably not be configured the exact same. In this case they will be slightly different, but similar. Call this part of me, paranoia. Providing you always remember the host is compiling for two targets, it shouldn't be a problem. I use my P200MMX desktop machine to compile kernels for my slower x86 machines, a P75 and a 486 laptop. The laptop didn't (until a recent factor-of-20 upgrade to disk space :) have enough room for the kernel source tree, and it would have taken all day to compile 2.4.2 on it with 20MB of RAM. My PPC machine compiles its own kernel, because it's easier to do that than install a cross compiler to compile my x86 kernels on it. You can do it, no question. But for myself, I would rather compile my kernel on the native machine it is running on. I don't compile kernels all that often on my development machines. If there wasn't any problem moving kernels to other chipsets, we wouldn't need the cross-compiler to begin with. I do use the cross-compiler on x86 architecture to produce a ppc 823 target, and compress images that can be flashed over the net, but this will only work with the cross-compiler unless you were using a 823 host (now that would be painful to build kernels). But I *believe* compiling for an 823 target on a 750 host (Pismo) requires that you use a cross compiler, that's how I do it. As a side, do you know that a PPC host running the cross-compiler produces different size binaries than an x86 host running the cross-compiler will produce with the exact same code and compiler revs? Both seem to run fine on the target, but size is different. Due to my ignorance in differences between a G3 and G4, I would certainly opt to compile the G4 on the native processor given the problems I've seen on getting ppc linux to run on the G4 Titanium anyway, call me old fashioned... -- Alan DuBoff Software Orchestration, Inc.
Re: debian2.2r2 on powerbook G4
On Mon, Mar 05, 2001 at 08:43:40PM -0800, Alan DuBoff wrote: Peter Cordes wrote: That's totally bogus. Nothing depends on the hardware of the computer the kernel is compiled on. With a cross-compiler, you should be able to use a fast PPC to compile a kernel on an old x86 laptop. This was not meant to imply that you couldn't compile a kernel on the Pismo for the Titanium, however, I haven't done any or seen any testing. I've seen mixed results of ppc linux running on the G4. So, I certainly wouldn't commit to code being able to run on the Titanium, since it has a different chip. Latest report is that it runs fine, but I don't know if that is for the 400mhz or 500mhz or just what. They should be the same, but there could be some timing issues arise, I don't know. GCC does the same thing no matter what host you run it on. With the same input, (which will be the case if you make your .config the same), gcc will give you identical output when run on any machine at all, as long as it is configured for the same target. In this (two powermacs), it would be. You would get an identical kernel if you built it on the other machine. The question is whether the generated binary works right on the Titanium. Generating it on the Titanium won't change anything. -- #define X(x,y) x##y Peter Cordes ; e-mail: X([EMAIL PROTECTED] , ns.ca) The gods confound the man who first found out how to distinguish the hours! Confound him, too, who in this place set up a sundial, to cut and hack my day so wretchedly into small pieces! -- Plautus, 200 BCE
