Re: Cobalt Qube 2
What about putting the disk from the working install in an USB closure and dd'ing it to the disk of the non working Qube2.
If I recall correctly, there used to be a root image you could dd to the disk of the Qube2 (using an USB closure for example) in case you didn't have enough memory to startup the installer (apparently this does not exist anymore :( ). This is how I installed my Qube2 a long time ago :)
----- Original Message -----
From: "Andy Barnes" <andy@barnes.net>
To: "Chris Thomas" <sruchris@gmail.com>
Cc: debian-mips@lists.debian.org, zero@colonel-panic.org, "Martin Michlmayr" <tbm@cyrius.com>
Sent: Wednesday, March 7, 2012 5:46:38 PM
Subject: Re: Cobalt Qube 2
in fact it deffinately is - this is from the self diagnostics before
it's tried to boot:
pci: unit type <Qube2>
>> tulip: {00:10:e0:00:bf:04}
and this is from my dhcpd.conf:
hardware ethernet 00:10:e0:00:bf:04;
though for some reason my original post showed both as the same in
dhcpd.conf - I will double check tomorrow but I'm certain it's
correct.
Andy
On 7 March 2012 16:41, Andy Barnes <andy@barnes.net> wrote:
> I think so. It looks like it gets a dhcp offer at the start of the
> output with the correct address. I will break it on purpose tomorrow
> and check the outputs regardless.
>
> net: interface up
> dhcp: DISCOVER
> dhcp: OFFER 192.168.1.78 <-- 192.168.1.0
> dhcp: REQUEST
> arp: sent request for 192.168.1.0
> arp: resolved 192.168.1.0
> dhcp: ACK
>
> I don't see how it would get the 192.168.1.78 address (as specified in
> my previous dhcpd.conf file) if it wasn't getting some communication
> with the server I have set up.
>
> On 7 March 2012 16:17, Chris Thomas <sruchris@gmail.com> wrote:
>> In your dhcpd.conf do both qube and cobalt have the correct, unique
>> MAC addresses?
>>
>> -Chris
--
To UNSUBSCRIBE, email to debian-mips-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/CALRDe2Y0SYEPaf-ADGaw_PVDUXFs_N8QxJ�2f234Hjc-Y5ZA@mail.gmail.com
Reply to: