Hi,
> Ed Swierk (14/12/2012):
>> Dec 14 02:17:16 main-menu[190]: (process:1505): ofpath: Driver pata_macio
>> is not supported
If this is the reason for the failure, then it's probably harmless. My
memory tells me that oldworld booting didn't need any OF path
parameters to be set. Thus, there wo
Hi Ed,
and thanks for your report.
Adding debian-powerpc@ to the loop, in case somebody there can shed
some light. Not sure when I'll be able to play with qemu+powerpc.
Ed Swierk (14/12/2012):
> Package: quik-installer
> Version: 0.0.30
> Severity: normal
> Tags: d-i
>
>
ma I install the
> minimal version of Debian because I only have 1,2G. I do the manual partition
> and format the root partition with first ext2 and in the second try with ext3.
>
> /dev/hda7 swap
> /dev/hda8 root
>
> I choose as the first try not to install Quik because,
partition and
format the root partition with first ext2 and in the second try with ext3.
/dev/hda7 swap
/dev/hda8 root
I choose as the first try not to install Quik because, if I may quote from the
manual:
“If you use BootX to boot into the installed system, just select your desired
debian terminated the 2.6.15 series and
at the time i could not get the newer ones to go
anyhow.
i also used quik to boot 3400, i needed to because
it would often hang during the boot from scsi error
with bootx (sort of randomly).
2) i also build a 2.6.18 that i booted from quik later
that did
debian terminated the 2.6.15 series and
at the time i could not get the newer ones to go
anyhow.
i also used quik to boot 3400, i needed to because
it would often hang during the boot from scsi error
with bootx (sort of randomly).
2) i also build a 2.6.18 that i booted from quik later
that did
I hope this question is within the scope of debian-powerpc; if not, please
accept my apologies.
I have to stick kernel 2.4.34. When I tried to compile quik-2.1 with the
debian patch 2.1-9 applied this is what I get. Looks like ffs is missing
from 2.4 bitops.h.
So, is quik-2.1 only
Hello, check this out:
https://launchpad.net/ubuntu/+source/quik/+bug/83346
apparently quik can't boot ubuntu's newer kernels. I also a kernel panic
with the newer 2.6 kernel under debian. I was however able to boot the
2.6.8 kernel, though, and Ubuntu warty has kernel-image-2.6.7-p
aybe it was for scsi, I
don't know, it could have been a few things, I've been going so fast
forgetting stuff... Anyway
On 3/19/07, Paul Mackerras <[EMAIL PROTECTED]> wrote:
Anthony Henson writes:
> I run quik, I reboot, I set my real-base to F0, boot-device to
Why F
Anthony Henson writes:
> I run quik, I reboot, I set my real-base to F0, boot-device to
Why F0?
> ide0/[EMAIL PROTECTED]:9 bootfile to /vmlinux root=/dev/hda9 reset-all, when
> it comes
> back to OF, I type boot, I get the boot: prompt, I type linux, and I get
> "
/etc/quik.conf
I run quik, I reboot, I set my real-base to F0, boot-device to
ide0/[EMAIL PROTECTED]:9 bootfile to /vmlinux root=/dev/hda9 reset-all, when it
comes
back to OF, I type boot, I get the boot: prompt, I type linux, and I get
"Read error on block 63747" twice, then cannot loa
; the boot-device, I get the black boot screen with the penguin in the upper
> left.
Well, I got it to boot. After some creative chrooting, I upgraded quik to
2.1-6 (the sarge version) and installed 2.4.18 (from woody). I also
installed all the other kernels from woody and sarge. 2.6.8 fr
kernel. If it's
the kernel, I've set both the boot-file env and applied changes to quik in
a chroot. If it's frozen, could it be a framebuffer problem? I only ask
because the last info that appears is about that. I think it is, anyway.
Here are the last few lines (copied by hand, so th
--- brian <[EMAIL PROTECTED]> wrote:
> Date: Sat, 26 Aug 2006 03:33:42 -0700 (PDT)
> From: brian <[EMAIL PROTECTED]>
> Subject: Re: Etch on old world with 2.5.15-1 and
> Quik
> To: brian <[EMAIL PROTECTED]>
>
> hey, its really working now.
>
> go
xcuse, i meant "upgrade from sarge to etch"
> 2.6.16-2 that
> never i could boot). it booted with quik, surprise
> tho not with bootx.
> (just for reference
> :powerbook3400/603ev-ppc-180/80MB Ram)
> so i went ahead to try upgrade the rest of the
> pieces.
>
> i spli
Le jeu 2006-08-10 a 12:31:52 -0400, [EMAIL PROTECTED] a dit:
> Hello PowerPC users,
>
> Does quik normallly give a menu at startup? On an
Only if you count the one shown in OF. Otherwise no, not like
yaboot's.
> old PowerWave 604|120 here there was only a black
> scre
well i tried this, upgrade from etch (removing the 2.6.16-2 thatnever i could boot). it booted with quik, surprise tho not with bootx.(just for reference :powerbook3400/603ev-ppc-180/80MB Ram)so i went ahead to try upgrade the rest of the pieces. i split it up into parts guiding the best i could
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19 Aug 2006, at 13:36, Holger Levsen wrote:
Some more information from a private disucssion on IRC, p2-mate is
the quik
maintainer:
Aug 11 10:12:16 p2-mate, have you seen
http://lists.debian.org/debian-powerpc/2006/08/msg00073.html
On Sat, Aug 19, 2006 at 03:43:06PM +0200, Simon Stapleton wrote:
> Yeah, I was looking directly at pre_boot_ppc.c, which seems to be
> doing a bunch of register writes on ati cards. Apple's BootX seems
> to do pretty much everything through the forth interpreter, which
> makes it a bit trick
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19 Aug 2006, at 15:33, Aurélien GÉRÔME wrote:
On Sat, Aug 19, 2006 at 03:03:31PM +0200, Simon Stapleton wrote:
Aye, agreed, although I'm not sure that it's _all_ done in the ROM,
ISTR from poking about in the miBoot / BootX source a while back
On Sat, Aug 19, 2006 at 03:03:31PM +0200, Simon Stapleton wrote:
> Aye, agreed, although I'm not sure that it's _all_ done in the ROM,
> ISTR from poking about in the miBoot / BootX source a while back that
> it does a certain amount of video configuration itself. I wonder
> what OSX's BootX
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19 Aug 2006, at 14:46, Aurélien GÉRÔME wrote:
All that's missing for Wallstreets to boot from quik with accelerated
video, it would seem, is a little video hardware initialisation; that
step _should_ be derivable from the ATI document
On Sat, Aug 19, 2006 at 02:41:40PM +0200, Simon Stapleton wrote:
> On 19 Aug 2006, at 13:43, Aurélien GÉRÔME wrote:
> >It does not surprise me at all. It is not the fault of Quik, it is
> >simply that OF is completely broken on OldWorld PowerMacs. Those
> >machines were never
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19 Aug 2006, at 13:43, Aurélien GÉRÔME wrote:
Hi,
On Fri, Aug 11, 2006 at 09:33:03AM +0200, Simon Stapleton wrote:
Yes, just using video=atyfb causes the same issue. There is a
difference somewhere in the way quik configures stuff and the
Hi,
On Fri, Aug 11, 2006 at 09:33:03AM +0200, Simon Stapleton wrote:
> Yes, just using video=atyfb causes the same issue. There is a
> difference somewhere in the way quik configures stuff and the way
> BootX/miBoot do it, using video=atyfb (+ all the various gubbins)
>
Hi,
On Friday 11 August 2006 09:33, Simon Stapleton wrote:
> On 10 Aug 2006, at 22:19, Holger Levsen wrote:
> Yes, just using video=atyfb causes the same issue. There is a
> difference somewhere in the way quik configures stuff and the way
> BootX/miBoot do it, using video=atyf
acceleration that is issued by quik when you first load the
kernel. I've
been using:
video=atyfb:vmode:16,cmode:32,mclk:67
However, it doesn't seem to let me boot, as a get a crazy mess of
graphics going hangwire. Is there something in quik that needs to
changed, or is the above command
Hi,
On Saturday 15 July 2006 17:17, Ben Racher wrote:
> So my Powerbook G3 266mhz Wallstreet is now successfully running Debian,
> however its a little slow. And I suspect the culprit is the video
> acceleration that is issued by quik when you first load the kernel. I've
> be
Hello PowerPC users,
Does quik normallly give a menu at startup? On an
old PowerWave 604|120 here there was only a black
screen until the default Linux 2.2.20 started.
Subsequently I added a 2.4.27 kernel and made it
the default. Now the system fails to boot or doesn't
progress far.
lease tell him to upgrade !)
i am downloading netinstall of etch now, see how
it boots there later. didn't have before i just
did in place upgrade from sarge.
--- Simon Stapleton <[EMAIL PROTECTED]> wrote:
>
> On 17 Jul 2006, at 07:51, brian wrote:
>
> > on my power
based
kernels? Or is it just 2.4 and below?
As far as I'm aware, the video part at least applies to all the video
drivers, but the ultimate reference remains, of course, the source.
At least for ATI drivers it appears to be current for 2.6.15 (modulo
that particular driver not working f
On Jul 18, 2006, at 4:31 AM, Simon Stapleton wrote:
Hrm. This might be a useful link, http://www.jonh.net/lppcfom-
serve/cache/1043.html
Thanks Simon! That's extremely helpful.
One question: Does the information there apply to 2.6 based
kernels? Or is it just 2.4 and below?
Thanks!
On 17 Jul 2006, at 07:51, brian wrote:
on my powerbook3400 where i just got quik going,
i just double checked -- i have no video options set at all.
Interesting. A friend of mine has an "original" (3400-based) G3, and
is having video issues. I'll get him to try th
on my powerbook3400 where i just got quik going, i just double checked -- i have no video options set at all. just in case i worry somebody, my disk is ok i think (its just the old fashioned laptop parking makes me nervous, or maybe it does need some tuning somewhere, but its ok) i do have
t, I have it up and running, booting with
quik, and all is well. Except that, like Ben Racher, I can't get
accelerated video running with a quik boot. I _think_ that way back
when, I was quik booting with accelerated video (video=atyfb:vmode:
14,cmode:32 etc etc), but whether or not
First off, I've replied offlist to Ben Racher on this, but here's a
bit of a howto on getting quik booting working on a Wallstreet
powerbook with 2.6 initrd kernels (it probably works for other
oldworld powerbooks too and might be useful for other machines with
horribly busted fi
So my Powerbook G3 266mhz Wallstreet is now successfully running Debian,
however its a little slow. And I suspect the culprit is the video
acceleration that is issued by quik when you first load the kernel. I've
been using:
video=atyfb:vmode:16,cmode:32,mclk:67
However, it doesn'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Just thought I'd let you all know that if you want to multi-boot on old
world with the quik boot loader you can use
image=$bye
label=MacOS
in your /etc/quik.conf
At least with my 2.0.2 Open Firmware
Cheers,
Daniel
- --
And that
e new
>>installation!
>
> Can you provide a full installation report describing how it fails, and
> possible logs, and send it to the installer bug reports (debian-installer the
> meta-package is named i think). Try to use the template linked from
> w.d.o/devel/debian-installer.
blem with the root-image, it was too big to fit a
floppy. The latest ones that work are:
http://people.debian.org/~luther/d-i/sid/images/2005-11-16/powerpc/floppy/
This is not meant for you, since quick fails on your box, but for
anywone with an oldworld machine that do work with quik.
> but I
tp://people.debian.org/~luther/d-i/sid/images/daily/powerpc/floppy/boot.img
> >>http://people.debian.org/~luther/d-i/sid/images/daily/powerpc/floppy/root.img
>
> These ones doesn't work at the moment, it's impossible to load the
> net/cd-driver floppies, but I did try to
tp://people.debian.org/~luther/d-i/sid/images/daily/powerpc/floppy/boot.img
> >>http://people.debian.org/~luther/d-i/sid/images/daily/powerpc/floppy/root.img
>
> These ones doesn't work at the moment, it's impossible to load the
> net/cd-driver floppies, but I did try to
.org/~luther/d-i/sid/images/daily/powerpc/floppy/root.img
These ones doesn't work at the moment, it's impossible to load the
net/cd-driver floppies, but I did try to install Sarge AND Woody and
they both fail with quik. Reading around on the internet, it seems I
have THE machine that causes
Have you tried something like video=controlfb:[EMAIL PROTECTED] ?
If not, you can try the old style Mac Modes support with
video=controlfb:vmode:15
(Try different values, 15 is 1024x768 at 70Hz, 14 at 60Hz etc... the
full list is in drivers/video/macmodes.h)
It should have picked up the default
> man nvsetenv is the most confusing I ever see, tells nothing useful .
Suggest improvements, please.
Michael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> > > To get this sorted out, tell us more:
> >
> > - what monitor are you using? Apple? Third party?
> > - if third party, what adapter? With video mode switches? How are the
> > switches configured?
> > - did you install a display manager, that would be started
> > automatically, i.e. your sy
s parameters !?!
> >> man nvsetenv is the most confusing I ever see, tells nothing useful .
> >> Someone can help me with this ?
>
> It's very simple:
>
> nvsetenv
>
> prints the contents of the OF variable , while
>
> nvsetenv
&
#x27;s very simple:
nvsetenv
prints the contents of the OF variable , while
nvsetenv
writes into the OF variable .
> I use nvsetenv in the following way to set the variables "boot-device"
> and "boot-command" to get quik working:
>
>
On Jan 12 2006, Fábio Rabelo wrote:
> I've try ed this, do not works, when I try to install ssh with dpkg (
> apt do not work in chroot env )
Did you mount all the filesystems correctly in the chroot? I can say
that, if the system is correctly set up, then apt *does* work in a
chroot environment.
nd output-device in the OF tree) set at the moment quik is running
aren't supported for the machine.
This has happened to me in the past, but, fortunately, I learned which
device corresponds to the video device and now I don't get anything like
the "frequency not supported"
t; man nvsetenv is the most confusing I ever see, tells nothing useful .
> Someone can help me with this ?
>
I use nvsetenv in the following way to set the variables "boot-device"
and "boot-command" to get quik working:
nvsetenv boot-device ata/[EMAIL PROTECTED]:0
nvsetenv boot
d, Jan 11, 2006 at 05:56:32PM -0200, Fábio Rabelo wrote:
> > > > > But after that, in the first boot within Sarge, my monitor just shows
> > > > > a
> > > > > msg "scan ou of range" .
> > > > > The noise from HD sugests the boo
> > Well then you might not even have to resolve the display issue, just
> > install ssh in the chroot and reboot.
> Googling around I found this
> :http://www.cpu.lu/~mlan/linux/dev/g3upgrade.html
> but I do not found any command called "nvsetenv" , there are another
> way to change OF paramete
r that, in the first boot within Sarge, my monitor just shows a
> > > > msg "scan ou of range" .
> > > > The noise from HD sugests the boot is going fine, but I can do anything
> > > > from that on .
> > >
> > > OK. But if quik boots
; > > msg "scan ou of range" .
> > > The noise from HD sugests the boot is going fine, but I can do anything
> > > from that on .
> >
> > OK. But if quik boots alright, then what good would it be to boot with
> > BootX instead?
> >
> To change quik
is going fine, but I can do anything
> > from that on .
>
> OK. But if quik boots alright, then what good would it be to boot with
> BootX instead?
>
To change quik for bootX
> One simple test is to press Ctrl-alt-delete. If the box reboots, then
> it was properly booted
> Remind me what video chip you have on this machine ? It's a control or a
> platinum ?
>
> Ben.
Motherboard os "TNT", OF is 1.05 and video controler is identified as
"Chaos Control" .
Googling I found this :http://www.cpu.lu/~mlan/linux/dev/g3upgrade.html
Maybe the issue is the G3 upgrade ?
I no
mentation about installing Sarge with BootX in an old world is
> outdated .
> The name of files ( kernel and initrd ) are wrong .
> Passed this issue, the installer works fine ( really much better then
> Woody ! ) .
> At the very end of install process, the installer warn about Quik, but
>
mentation about installing Sarge with BootX in an old world is
> outdated .
> The name of files ( kernel and initrd ) are wrong .
> Passed this issue, the instaler works fine ( realy much better then
> Woody ! ) .
> At the very end of install proccess, the instaler warn about Qu
files ( kernel and initrd ) are wrong .
Passed this issue, the installer works fine ( really much better then
Woody ! ) .
At the very end of install process, the installer warn about Quik, but
installs it ( cool )
But after that, in the first boot within Sarge, my monitor just shows
a MSG "
files ( kernel and initrd ) are wrong .
Passed this issue, the installer works fine ( really much better then
Woody ! ) .
At the very end of install process, the installer warn about Quik, but
installs it ( cool )
But after that, in the first boot within Sarge, my monitor just shows
a MSG "
files ( kernel and initrd ) are wrong .
Passed this issue, the instaler works fine ( realy much better then
Woody ! ) .
At the very end of install proccess, the instaler warn about Quik, but
installs it ( cool )
But after that, in the first boot within Sarge, my monitor just shows a
msg
Hi,
firstly, you need to configure your mailing properly. Your mails are
sent using an adress called "pc <[EMAIL PROTECTED]>". So you won't be able
to receive any replies adressed to you privately.
Secondly, using Quik isn't really easy, you might want to browse t
On Sat, 2005-11-12 at 08:56 +0200, pc wrote:
>
> Hi, Quik make my lost my installation - 2nd times-
>
> How is corect command to update kernel in /etc/quik.conf ?
>
>
> Thanks
>
> System powerpc , 604e processor, 7200-8500
> OS woody first , sarge second
> 2.
Hi, Quik make my lost my installation - 2nd times-
How is corect command to update kernel in /etc/quik.conf ?
Thanks
System powerpc , 604e processor, 7200-8500
OS woody first , sarge second
2.2.20 first kernel , 2.6.8 second
History: Installation is recent, one week, but the only
On Wed, May 25, 2005 at 06:19:34AM -0300, Rogério Brito wrote:
> Hi, Vinai.
>
> On Apr 13 2005, Rogério Brito wrote:
> > On Apr 13 2005, vinai wrote:
> > > And what are you using to boot linux without MacOS on this machine ?
> >
> > Humm, good question. So
On May 25 2005, Peter 'p2' De Schrijver wrote:
> On Wed, May 25, 2005 at 08:01:31AM -0300, Rogério Brito wrote:
> > Yes, that was the point of my message. OTOH, the sarge d-i says that
> > quik won't work with a /boot partition separated from a root partition.
&
On Wed, May 25, 2005 at 08:01:31AM -0300, Rogério Brito wrote:
> On May 25 2005, Peter 'p2' De Schrijver wrote:
> > quik doesn't know about ext3 journaling. So better use a normal ext2
> > partition for /boot or be very sure that the /boot partition is unmounted
On Wed, 25 May 2005, [iso-8859-1] Rogério Brito wrote:
On May 25 2005, Peter 'p2' De Schrijver wrote:
quik doesn't know about ext3 journaling. So better use a normal ext2
partition for /boot or be very sure that the /boot partition is unmounted
properly before rebooting.
Ye
On May 25 2005, Peter 'p2' De Schrijver wrote:
> quik doesn't know about ext3 journaling. So better use a normal ext2
> partition for /boot or be very sure that the /boot partition is unmounted
> properly before rebooting.
Yes, that was the point of my message. OTOH, the
Hi,
> I think that I discovered that quik doesn't like ext3 partitions.
>
> I tried this just once, but it seemed to work and I would like to know if
> the same method works for you: before upgrading/installing a new kernel,
> disable the journal (tune2fs -O ^has_journal /dev
Hi, Vinai.
On Apr 13 2005, Rogério Brito wrote:
> On Apr 13 2005, vinai wrote:
> > And what are you using to boot linux without MacOS on this machine ?
>
> Humm, good question. Sometimes, I can make quik work, but I have more
> luck with getting the kernel compiled, compressin
On Sat, 5 Mar 2005 14:39:13 +0100
Simon Vallet <[EMAIL PROTECTED]> wrote:
> Sources are available at http://www.castalie.org/debian/quik_md.tar.gz
> ; you will need an existing quik install to test it, as the first- and
> second-stage bootstrap programs are not included.
Oops.
Hi,
I just added some support for md devices in quik. Could you please test
this to ensure it doesn't break existing installs and/or works as
intended if your / is on an md device. I intend to file a bug
against the debian package next week, as I think it would be a nice
thing to have i
On Wed, Feb 16, 2005 at 08:00:51PM +0100, Holger Levsen wrote:
> Hi,
>
> On Wednesday 16 February 2005 13:02, Hans Ekbrand wrote:
> > > This was a common problem with previous, non-initrd enabled quik
> > > versions-- are you sure you've got the latest quik from sa
Hi,
On Wednesday 16 February 2005 13:02, Hans Ekbrand wrote:
> > This was a common problem with previous, non-initrd enabled quik
> > versions-- are you sure you've got the latest quik from sarge ?
>
> Yes,
>
> pc236:~# apt-cache policy quik
> quik:
> In
root device "" or unkown-block(0,1)
> > Please append a correct "root=" boot option
> > Kernel panic: VFS: Unable to mount root fs on uknown-block(0,1)
> > (0)Rebooting
>
> This was a common problem with previous, non-initrd enabled quik
> versions-- are
root fs on uknown-block(0,1)
> (0)Rebooting
This was a common problem with previous, non-initrd enabled quik
versions-- are you sure you've got the latest quik from sarge ?
> but that should be a minor problem.
You may also try with a non-initrd kernel.
> The boot-file argument, s
his /etc/quik.conf
image=/boot/vmlinux-2.6.8-powerpc
append="root=/dev/ram"
initrd=/boot/initrd.img-2.6.8-powerpc
label=Linux
read-only
default=Linux
-
but it didn't work :-(
The OF variables that I ne
On Tuesday, February 15, 2005, at 03:02 AM, Hans Ekbrand wrote:
I thought that I could always zap pram and boot from cd into macos and
bootX, but holding down command-option-p-r after reboot doesn't help.
The screen stays black and I don't hear any disk spinning up. Tried to
boot from CD or floppy,
On Tue, Feb 15, 2005 at 12:02:44AM +0100, Hans Ekbrand wrote:
> On Mon, Feb 14, 2005 at 11:56:24PM +0100, Hans Ekbrand wrote:
>
> [...]
>
> > Thanks Brad, Thanks Simon. I changed the load-base to 0x1000 as that
> > worked on 6400. Rebooting as I write this.
>
> Doesn't seem to work :-( I don't h
On Mon, Feb 14, 2005 at 11:56:24PM +0100, Hans Ekbrand wrote:
[...]
> Thanks Brad, Thanks Simon. I changed the load-base to 0x1000 as that
> worked on 6400. Rebooting as I write this.
Doesn't seem to work :-( I don't have physical access to the box at
the moment (it is at work, I am at home), so
> load-base.
[...]
> Based on my understanding, the 0:0 is a special value that tells it to
> search all partitions on that disk. Some of the older machines choke
> if you configure a specific partition. The quik boot blocks are written
> into the bootable partition.
Thanks Bra
On Mon, Feb 14, 2005 at 11:54:57AM -0500, Rich Johnson wrote:
> On Monday, February 14, 2005, at 04:09 AM, Hans Ekbrand wrote:
[...]
> Fortunately, you can boot 'cmd-ctrl-O-F' (requires ADB keyboard) with a
> console or use the woody boot/rescue disk to run nvsetenv.
That is good to know, but
will choose based
on the quik.conf file.
> This is quite normal : AFAIK, quik writes some of it's bootloading
> code into the MBR, which is 0:0. But you might want to check that the
> ata/ata-disk device really exists under OF (using devalias, dev and ls
> OF commands) -- this may v
messages sometimes look a bit cryptic ;-)
For correct load- and real-base settings, I'm afraid you'll need to
experiment a bit -- look at penguinppc.org and the NetBSD/macppc FAQ
for more info on possible values.
> Now, Linux resides on /dev/hda6, and quik installed something into the
>
On Monday, February 14, 2005, at 04:09 AM, Hans Ekbrand wrote:
Do I have to manually use nvsetnv to make it work. I am suspicious of
the line
"boot-device /AAPL,ROM"
Unfortunately yes! That's Apple's boot loader. Your system will
revert to that value whenever PRAM is reset. So make sure you pra
c quirks mentioned on
> > http://penguinppc.org/bootloaders/quik/quirks.ph?
>
> No. Quik doesn't know how to manipulate OF vars -- in fact, you may only
> load quik with correct OF values
>
> > Is it up to me as an user to configure OF?
>
> Yes, you'll have to figure
On Mon, 14 Feb 2005 10:18:00 +0100
Hans Ekbrand <[EMAIL PROTECTED]> wrote:
> On Mon, Feb 14, 2005 at 10:09:38AM +0100, Hans Ekbrand wrote:
> Does quick know of the model-specific quirks mentioned on
> http://penguinppc.org/bootloaders/quik/quirks.ph?
No. Quik doesn't know
ine
>
> "boot-device /AAPL,ROM"
>
> below?
>
> pc236:~# quik -v
> Second-stage loader is on /dev/hda6
> Config file is on partition 6
> Writing first-stage QUIK boot block to /dev/hda6
> Making /dev/hda6 bootable (map entry 6)
> Writing block table t
On Fri, Feb 11, 2005 at 11:16:52AM -0500, Rich Johnson wrote:
> On Friday, February 11, 2005, at 03:15 AM, Hans Ekbrand wrote:
[...]
> > I am also interesting boot with quick, but I thought that required
> > an
> > non-initrd kernel.
[...]
> Modern quik supports init
hen I run Mozilla and anything much else, but it should make a fine
firewall.
If you are willing to put up with the foibles of the quik bootloader
(see my previous rants on the subject in this mailing list and
debian-boot) you should be able to get Debian to install just fine,
without having to deal
tem).
Full report at: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=294958
The moral of the story is to check /etc/quik very, _very_, VERY
carefullyand be sure to preserve an alternate boot mechanism.
--rich
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubs
I can run Debian on a 7200/120 _without_ any MacOS partition ?
Is my understanding correct ?
ABSOLUTELY! It makes a nice little server. It doesn't need to be any
faster than my network.
Just make sure you have enough disk & ram. I recommend a reasonable
(DSL or better) network connection for
On Fri, Feb 11, 2005 at 12:10:47PM -0500, Mehul Sanghvi wrote:
> I can run Debian on a 7200/120 _without_ any MacOS partition ?
> Is my understanding correct ?
>
>
>
> I don't have a MacOS that works on the 7200, so can I do the install
> without MacOS ? Or do I need MacOS to do the install a
On Fri, 11 Feb 2005 11:16:52 -0500, Rich Johnson
<[EMAIL PROTECTED]> wrote:
>
> Modern quik supports initrd. I have an old-world 7200 which, after a
> dist-upgrade, is happily running sarge/testing (3.1?) with a stock 2.6
> kernel. Here's the relevant info:
>
I ca
kernels? Or is there another way of doing it?
--
Note that I use Debian version 3.1
Linux emac140 2.6.9-1-686 #1 Thu Nov 25 03:48:29 EST 2004 i686 GNU/Linux
Modern quik supports initrd. I have an old-world 7200 which, after a dist-upgrade, is happily running sarge/testing (3.1?) with a stock
On Fri, Feb 11, 2005 at 09:15:28AM +0100, Hans Ekbrand wrote:
> On Thu, Feb 10, 2005 at 04:00:56PM -0500, Eric C. Cooper wrote:
> > On Thu, Feb 10, 2005 at 01:51:04PM -0500, Rich Johnson wrote:
> > > The time has come for me to decommission OS 9 from my old-word 8500 and
> > > go pure linux--but t
the
> > disks.
[...]
> One thing that I got bitten by: quik doesn't understand symlinks, so
> /vmlinux should be a hard link to /boot/vmlinux-NNN. Also, updating
> the kernel image via apt-get or dpkg invariably messes up the links;
> you'll have to fix them by hand each t
at I want to do:
>
> 1. apt-get install quik - but do NOT install a boot-record.
> 2. remount the existing /boot (hfs) as /oldboot. /boot becomes just a
> directory on the root dev.
> 3. copy vmlinux, System.map and cofig files from /oldboot to /boot
> 4. modify /etc/quik.con
1 - 100 of 433 matches
Mail list logo
