> Ha! This seems to assume that the (fdisk) DOS partition
> is the 'i' partition in the disklabel - it is not;
> I created a [c]ustom disklabel.
A bunch of architectures work this way. And it is a quite normal
expectation that the 'i' partition match the 'spoofed label'
semantics.
But for now I
On Sat, Jul 20, 2013 at 08:23:35PM +0200, Jan Stary wrote:
> On Jul 20 11:23:01, kwesterb...@rogers.com wrote:
> > On Sat, Jul 20, 2013 at 11:45:07AM +0200, Jan Stary wrote:
> > > > What troubles me is that whatever device (device name) I try,
> > > > it is the 'ofwboot' which is not found.
> > > >
> I made the DOS partition start at 512 (and then 1024
> and then everything under 4096 wherethe obsd part starts),
> but never could I mount that DOS partition ...
Silly me, it's 1, not 512;
and it mounts, and the ofwboot is NOT there,
and not in the wd0i as designated by me either.
So there is n
On Jul 20 11:23:01, kwesterb...@rogers.com wrote:
> On Sat, Jul 20, 2013 at 11:45:07AM +0200, Jan Stary wrote:
> > > What troubles me is that whatever device (device name) I try,
> > > it is the 'ofwboot' which is not found.
> > > I don't mind calling my disk 'cd' in the boot sequence
> > > or alte
On Sat, Jul 20, 2013 at 11:45:07AM +0200, Jan Stary wrote:
> > What troubles me is that whatever device (device name) I try,
> > it is the 'ofwboot' which is not found.
> > I don't mind calling my disk 'cd' in the boot sequence
> > or altering the devaliases, or "setenv boot-device cd:,ofwboot",
>
> What troubles me is that whatever device (device name) I try,
> it is the 'ofwboot' which is not found.
> I don't mind calling my disk 'cd' in the boot sequence
> or altering the devaliases, or "setenv boot-device cd:,ofwboot",
> but that doesn't work either, as shown above.
> How can I make sure
The saga continues: I tried to reinstall with 5.4-beta,
and have a similar, but different problem now.
To recall the previous situation: the kernel was
confused about what 'cd0' and 'hd0' is, and I had
to hardcode the bootpath into the kernel config.
A patch from mpieuc...@nolizard.org solved it f
On 23/05/13(Thu) 17:00, Miod Vallat wrote:
> > Were you thinking of something like that? It works for me (c) tm, with
> > my PowerBooks (disk@0/wd0), I haven't tried NFS boot yet.
>
> Not exactly, but your version is probably better than what I was
> thinking of. However, it will not allow for roo
> Were you thinking of something like that? It works for me (c) tm, with
> my PowerBooks (disk@0/wd0), I haven't tried NFS boot yet.
Not exactly, but your version is probably better than what I was
thinking of. However, it will not allow for root on the second wd disk
of a controller, or on any se
On May 23 08:41:50, mpieuc...@nolizard.org wrote:
> On 26/12/12(Wed) 20:54, Miod Vallat wrote:
> > > Just upgraded to a current again, with the same problem,
> > > and the same solution:
> >
> > [...]
> > > wdc1 at kauaiata0 irq 39: DMA
> > > atapiscsi0 at wdc1 channel 0 drive 0
> > > scsibus0 at
On 26/12/12(Wed) 20:54, Miod Vallat wrote:
> > Just upgraded to a current again, with the same problem,
> > and the same solution:
>
> [...]
> > wdc1 at kauaiata0 irq 39: DMA
> > atapiscsi0 at wdc1 channel 0 drive 0
> > scsibus0 at atapiscsi0: 2 targets
> > cd0 at scsibus0 targ 0 lun 0: ATAPI 5/c
> Just upgraded to a current again, with the same problem,
> and the same solution:
[...]
> wdc1 at kauaiata0 irq 39: DMA
> atapiscsi0 at wdc1 channel 0 drive 0
> scsibus0 at atapiscsi0: 2 targets
> cd0 at scsibus0 targ 0 lun 0: ATAPI 5/cdrom
> removable
> wd0 at wdc1 channel 0 drive 1:
> wd0:
On Jun 13 14:12:45, h...@stare.cz wrote:
> This is current/macppc on a "late 2005" Mac Mini,
> which is PowerMac10,2.
>
> I needed to hardcode the root device into the kernel config,
> otherwise boot stops with unknown root device, as discussed
> in the misc thread that starts at
> http://marc.in
13 matches
Mail list logo
