gpg key generation
Has anyone else had any trouble with key generation for gpg? I'm using a reva imac; I've tried different sizes and types of keys, and do lots of typing, mouse moving, try to give the hard disk stuff to do, etc, but it still complains about not having enough entropy and needing another 2-300 bytes (and then appears to hang). Any tips? Thanks, Mark.
Re: gpg key generation
Thanks for that; I was beginning to wonder if it was just me! Still having problems, but if need be I suppose I can just drop in my files from my x86 box. Cheers, Mark. > > This is a known issue. PowerPCs are built too well, and don't gain > disorder as fast as, say, i386 does. > > If this doesn't do it > > find / >/tmp/out & rm /tmp/out; lynx http://web.slashdot.org/ > > then take a baseball bat to it to add lots of entropy. Maybe too much. >
Re: Problem installing debian on G3 beige
> documentation does need to be improved, but this is a volunteer > effort. when you see holes volunteering to help is the best approach > to getting them fixed. > Just my 2c worth; I ran into a small problem during my installation due to section '4.6.1 Partitioning newer Macs' which says the type of the bootstrap partition should be '_Apple_Bootstrap_'. This is most likely meant to be underscored for emphasis, but for a few attempts I was including the preceding and trailing underscores. Or maybe I shouldn't admit to that :) -Mark.
LS-120 drive
Hi, I'm running 2.2r2, kernel 2.2.1pre20-ben3 and I'm trying to get my imation LS-120 superdrive to work (on my revA imac) I've applied the patch to usb-storage.c and compiled and inserted it, but I seem to be having trouble with scsi emulation still. When I try 'mount -t vfat /dev/sda /mnt' I get: mount: the kernel does not recognise /dev/sda as a block device (maybe `insmod driver'?) and 'mount -t vfat /dev/sg0 /mnt' (with or without module sg inserted): mount: /dev/sg0 is not a block device These are the messages from dmesg after 'insmod usb-storage' (with drive already connected): usb.c: registered new driver usb-storage scsi1 : SCSI emulation for USB Mass Storage devices scsi : 2 hosts. usb-storage: bus_reset() requested but not implemented usb-storage: bus_reset() requested but not implemented usb-storage: host_reset() requested but not implemented WARNING: USB Mass Storage data integrity not assured USB Mass Storage device found at 5 USB Mass Storage support registered. The entry for the drive from /proc/bus/usb/devices is: T: Bus=01 Lev=02 Prnt=02 Port=02 Cnt=03 Dev#= 5 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=04e6 ProdID=0001 Rev= 2.00 S: Manufacturer=Shuttle Technology Inc. S: Product=E-USB Bridge C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=usb-storage E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl= 0ms E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl= 0ms E: Ad=83(I) Atr=03(Int.) MxPS= 2 Ivl=255ms Does anyone have any ideas? I would be happy to supply any further information. Thanks in advance, Mark.
truecolor on fbdev?
Hi, I've just been trying to install realplayer, but it won't play and complains that it needs true/pseudocolor. fbset -i in the console gives "Visual: PseudoColor", yet in X says "Visual : Directcolor". Adding a 'Visual "TrueColor"' (or "PseudoColor") in XF86Config produces a message in startup like "(**) FBDev: Default visual is TrueColor" or whatever I set it to, but this seems to have no effect to the output of fbset. I'm running XFree86 3.3.6 with an ATI Mach64 card. Searching through the archives I could only find a mention of something like "...directcolor modes (like ATI Mach64 ...)"; does this imply that I can't get truecolor with 3.3.6? I'm also currently running at 32bpp if that information is required; mainly because this was the only one that worked when I was setting stuff up. Any information gratefully received, thanks, Mark.
thanks
Due to time commitments I'm unsubscribing from debian-ppc, so I'd just like to take this opportunity to thank all on this list for their help (whether by answering my questions, or those of others similar to mine). I now have a fully functional debian-powered imac so I can use a %100 free os both at home and now at work. It's thanks to you that Debian is (IMHO) the best distro out there. Thanks guys, Mark. -- Mark Hepburn Engineering/Computer Science, University of Tasmania pgp public key: http://bronte.comp.utas.edu.au/~mark_h/pgpkeys.asc
ibook2 hangs during install
Howdy; I've just been trying to boot my ibook2 using a set of 2.2r0 cds (using the 'debian video=ofonly' boot arguments) and it appears to boot fine, loads the installer; the problem is I press 'continue' following the welcome message, then it just sits and hangs at the 'Please wait while the installer determines the next step needed' message. I'm sorry if I'm repeating anything here; I seem to recall seeing something similar a while ago but a trawl through the archives didn't reveal anything. Does anyone have any ideas on how to progress? I intend to dual-boot (with a shared partition) so I might be able to boot from a macos partition, and I'll also upgrade to testing as soon as I can get an initial install. Thanks, Mark. -- Mark Hepburn Engineering/Computer Science, University of Tasmania pgp public key ID: 91602C17
missing ofboot.b?
A very big thankyou to the creator(s) of the debian-imac sourceforge archive;
I've now managed to boot my ibook2 and install the base system, etc. (couple
of things I should note; I had to remove the space from the 'boot hd:x,
yaboot' line to become 'boot hd:x,yaboot', and I also needed to supply the
extra arguments 'install video=ofonly' at the boot prompt in case anyone is
following this)
I have got to the step of running mkofboot
('mkofboot --boot /dev/hda9 -m /target/etc/ofboot.b --root /dev/hda11
--partition 11'); the first time this complained that no such ofboot.b file
existed; I have an iMac running potato so I used ae to copy the contents of
its /etc/ofboot.b (skipping the bit!) into
/target/etc/ofboot.b.
The next time I ran the same mkofboot line I got a
"/target/etc/ofboot.b: Line too long"
message followed by a "create hfs filesystem on /dev/hda9" message, to which I
answered no and it aborted. The only long line in ofboot.b was the
section; I removed an entry from that but with the same result.
Have I missed a step in the installation, or can anyone help me?
Thanks in advance, Mark.
--
Mark Hepburn
Engineering/Computer Science, University of Tasmania
pgp public key ID: 91602C17
Re: missing ofboot.b?
> The next time I ran the same mkofboot line I got a > "/target/etc/ofboot.b: Line too long" > message followed by a "create hfs filesystem on /dev/hda9" message, to which I > answered no and it aborted. The only long line in ofboot.b was the > section; I removed an entry from that but with the same result. Oops; was missing a '\n' on the last line. Sorry about that. :/ (I can't remember from my last install; I presume you have to answer yes to the "create hfs filesystem?" question? It aborts when you answer no). -- Mark Hepburn Engineering/Computer Science, University of Tasmania pgp public key ID: 91602C17
triple-boot question
Thanks to everyone's help I now have testing installed on my ibook2. In the process though I have exceeded the 15-partition limit (partion-map + drivers + bootstrap + swap + root + linux/macos share + os9 + osx + 2 extras added when you install osx on ufs). Sure enough, osx (on partition 16) is inaccessable from yaboot, although it still seems to boot (albeit slowly) from the graphical menu. I prefer yaboot (if nothing else, it's a _lot_ quicker); to elminate some partitions I was thinking of merging the 9 and x parititions in one hfs+ and just using the software restore disks to get both os in the same partition. My question: is it still possible to specify in yaboot.conf macos= and macosx= being the same partition, or is it neccessary to boot into one, change the startup disk and reboot? Thanks in advance, Mark. -- Mark Hepburn Engineering/Computer Science, University of Tasmania pgp public key ID: 91602C17
Re: missing ofboot.b?
On Tue, Aug 14, 2001 at 11:24:59PM -0800 or thereabouts, Ethan Benson wrote:
> On Wed, Aug 15, 2001 at 11:27:33AM +1000, Mark Hepburn wrote:
> > I have got to the step of running mkofboot
> > ('mkofboot --boot /dev/hda9 -m /target/etc/ofboot.b --root /dev/hda11
> > --partition 11'); the first time this complained that no such ofboot.b file
> > existed; I have an iMac running potato so I used ae to copy the contents of
> > its /etc/ofboot.b (skipping the bit!) into
> > /target/etc/ofboot.b.
>
> this is anchient fossilized, very long ago deprecated behavior. i
> have no idea where you are finding these historic documents but the
> current procedure is -m /usr/lib/yaboot/ofboot (no .b).
>
> this has been the case for a loong time now.
Yes, sorry about that, fixed that with the help of Chris Tillman yesterday.
The 'historic document' was the 2.2r0 install manual that I had a print out of
from doing an install, well, a long time ago. Since it was still potato I was
installing I hadn't bothered to check if there had been any changes; oops.
Works now anyway; thanks very much everyone.
--
Mark Hepburn
Engineering/Computer Science, University of Tasmania
pgp public key ID: 91602C17
Re: ibook2 hangs during install
On Sun, Aug 19, 2001 at 11:18:54PM -0400 or thereabouts, Colin Walters wrote: > Mark Hepburn <[EMAIL PROTECTED]> writes: > > > I've just been trying to boot my ibook2 using a set of 2.2r0 cds > > (using the 'debian video=ofonly' boot arguments) and it appears to > > boot fine, loads the installer; the problem is I press 'continue' > > following the welcome message, then it just sits and hangs at the > > 'Please wait while the installer determines the next step needed' > > message. > > So, any luck with the woody boot-floppies? Also, you could also try > potato 2.2r3. I ended up booting off the debian-imac archive from sourceforge (another thankyou there for that); debian.imac.sourceforge.net with the boot argument 'video=ofonly' then using my 2.2r0 cd to complete a base install. Then upgraded to testing straight away. The debian-imac collection (2.2r3 from memory) worked fine; I never got around to trying the woody boot-floppies. Thanks for you help though. Btw, in my limited exploration I didn't find any howtos for booting from hard-disk (such as using woody boot-floppies from a mac partition) (apart from debian-imac). Does such a thing exist? The installation manual doesn't give much detail at all. Cheers, Mark. -- Mark Hepburn Engineering/Computer Science, University of Tasmania pgp public key ID: 91602C17
framebuffer problems on revA iMac
Hi; I've been through the archives but couldn't find anything related. I've just installed debianppc on my reva imac. The first couple of times I tried booting from cds everything went fine; however I messed up the partitioning the first installation attempt and had to try again. Since then however when booting from the cds the curses display doesn't draw correctly; roughly the top third of the screen is 'blue' while the rest is black, and old dialog boxes can be seen 'underneath' newer ones. Problems persisted after installation; the system works fine but the screen doesn't refresh properly. Typing 'clear' clears only the top 10 or so lines, and the last line on the screen is always an echo of what came before; eg aaa bb prompt~$bba I finally cured the console problem by using a 'novideo' option in my yaboot.conf (after video=atyfb and aty128fb didn't work), but now of course I'm stuck at a lower resolution in X (tried both XF86_FBDev and Xpmac). I'm happy to live with the console as it is (25x80 chars or whatever), but I'd like 1024x768 in X if possible! Anyone have any ideas? Apologies if this is too long; I was trying to supply all info that might be helpful. Thanks very much, Mark.
X permission problems
I'm currently trying to set up X. I have a working XF86Config, however when I type startx (or just 'X') I get the following message: X: exec of /usr/bin/X11/XF86_FBDev failed I can start up fine by typing 'xinit /usr/bin/enlightenment -- /usr/bin/X11/XF86_FBDev' as root, but cannot of course do the same as a user or fakeroot. What am I doing wrong? (one other thing; X seems to work fine with both 16 and 32 bpp; however after shutting down under 16 the screen is filled with the following message: mach64CreateGC: unsupported depth: 16. Using cfbCreateGC instead. Can I do anything about this, or don't I need to?) Thanks in advance, Mark.
Re: X permission problems
At 01:55 AM 12/29/00 +0100, Michel Dänzer wrote: >Mark Hepburn wrote: >> >> I'm currently trying to set up X. I have a working XF86Config, however >> when I type startx (or just 'X') I get the following message: >> X: exec of /usr/bin/X11/XF86_FBDev failed >> >> I can start up fine by typing 'xinit /usr/bin/enlightenment -- >> /usr/bin/X11/XF86_FBDev' as root, but cannot of course do the same as a >> user or fakeroot. >> >> What am I doing wrong? > >Have you edited /etc/X11/Xserver to allow users other than root to start the X >server? > The second line is currently "Console"; I just tried with "Anybody" with the same result. I hadn't thought of that though; anywhere else I should be looking? Thanks for your help, Mark. > > >Sounds harmless, as long as there is no real problem which could be related >I'd say you can ignore it. > Thanks; I'll do that!
Re: X permission problems
anywhere else I should >> be looking? > >The permissions of the binary itself are fine? > > They should be; I checked them against my (working) x86 box at home last night and I haven't changed anything that I can remember. /usr/bin/X11/X -rwsr-sr-x root.root /usr/bin/X11/XF86_FBDev -rwxr-xr-x root.root /usr/bin/X11/xinit -rwxr-xr-x root.root This is getting quite frustrating as you can imagine, but I must be almost there! cheers, Mark.
Re: X permission problems
Not sure how many people have been following this thread, but I've just apt-get upgraded and everything works fine. Not sure if it was something I'd inadvertantly done or not, but all seems to be fine now. Thanks to everyone, cheers Mark. At 12:10 PM 12/29/00 +1100, Mark Hepburn wrote: >anywhere else I should >>> be looking? >> >>The permissions of the binary itself are fine? >> >> > >They should be; I checked them against my (working) x86 box at home last >night and I haven't changed anything that I can remember. > >/usr/bin/X11/X -rwsr-sr-x root.root >/usr/bin/X11/XF86_FBDev -rwxr-xr-x root.root >/usr/bin/X11/xinit -rwxr-xr-x root.root > >This is getting quite frustrating as you can imagine, but I must be almost >there! > >cheers, Mark. > > >-- >To UNSUBSCRIBE, email to [EMAIL PROTECTED] >with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > >
Re: framebuffer problems on revA iMac
On Fri, Dec 29, 2000 at 03:34:56PM +0100, Geert Uytterhoeven wrote:
> On Thu, 28 Dec 2000, Michel [iso-8859-1] Dänzer wrote:
> > Mark Hepburn wrote:
> > > I finally cured the console problem by using a 'novideo' option in my
> > > yaboot.conf (after video=atyfb and aty128fb didn't work),
> >
> > Note that the colon at then of video=aty(128)fb: is vital.
>
> This is something I've been wondering about since a while: why??
>
> I'd expect it to work with `video=atyfb' and `video=128fb', and even without
> these since they will be autoprobed anyway.
>
Mine is working now with a 'video=atyfb' option and no colon; might make a
difference
that this is just an option to yaboot and not an 'append' (or whatever) option.
If that makes sense.
> BTW, anyone who tried `video=ofonly' with 2.4.0-testX?
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like
> that.
> -- Linus Torvalds
>
Re: framebuffer problems on revA iMac
On Sun, Dec 31, 2000 at 01:56:18AM +1100, Mark Hepburn wrote: > On Fri, Dec 29, 2000 at 03:34:56PM +0100, Geert Uytterhoeven wrote: > > On Thu, 28 Dec 2000, Michel [iso-8859-1] Dänzer wrote: > > > Mark Hepburn wrote: > > > > I finally cured the console problem by using a 'novideo' option in my > > > > yaboot.conf (after video=atyfb and aty128fb didn't work), > > > > > > Note that the colon at then of video=aty(128)fb: is vital. > > > > This is something I've been wondering about since a while: why?? > > > > I'd expect it to work with `video=atyfb' and `video=128fb', and even without > > these since they will be autoprobed anyway. > > > > Mine is working now with a 'video=atyfb' option and no colon; might make a > difference > that this is just an option to yaboot and not an 'append' (or whatever) > option. > If that makes sense. > I should also point out that it finally worked when I tried a benh kernel (seems to be the standard advice for any problem!); 2.2.17pre20-ben3 I think it was.
