On 2019-04-01, David wrote:
> On Mon, 1 Apr 2019 at 09:56, David Wright wrote:
>>
>> I hit this bizarre page that has a comparable multitude of possibilities.
>> https://stackoverflow.com/questions/212466/what-is-a-bus-error
>
> The "bizarre" that I'm seeing on that page is probably due to
> toda
On Mon, 1 Apr 2019 at 09:56, David Wright wrote:
>
> I hit this bizarre page that has a comparable multitude of possibilities.
> https://stackoverflow.com/questions/212466/what-is-a-bus-error
The "bizarre" that I'm seeing on that page is probably due to
today's date being April 1st in some parts
On Sun 31 Mar 2019 at 16:35:44 (-0400), rhkra...@gmail.com wrote:
> On Saturday, March 30, 2019 04:12:05 PM rh kramer wrote:
> > I already made an attempt, and I'm a little worried that I may have messed
> > things up -- I'd like to try to recover and get back to a reliable Jessie
> > system.
Saw
Hello,
On Sun, Mar 31, 2019 at 04:35:44PM -0400, rhkra...@gmail.com wrote:
>* Aside: what the heck does errorackage mean / stand for and what is it
> telling me? Who came up with that "word"?
Ah, I thought you were aware of what it was printing. It was printing
"Bus error" over the top of i
Hi,
On Sat, Mar 30, 2019 at 04:12:05PM -0400, rh kramer wrote:
> I found a post that told me what the content of
> /etc/apt/sources.list should be for Jessie LTS.
LTS updates (for a limited set of architectures) make their way into
the /updates suite that is found on
security.debian.org, just lik
On Saturday, March 30, 2019 04:12:05 PM rh kramer wrote:
> I already made an attempt, and I'm a little worried that I may have messed
> things up -- I'd like to try to recover and get back to a reliable Jessie
> system.
Things might be OK. Things I did:
* googled for errorackage -- found some
I already made an attempt, and I'm a little worried that I may have messed
things up -- I'd like to try to recover and get back to a reliable Jessie
system.
What I did and why:
I understood from some other posts on the list that the mirrored
repositories for Wheezy and Jessie went away in early M
On Tuesday 15 March 2016 22:20:42 David Christensen wrote:
> On 03/15/2016 11:59 AM, Lisi Reisz wrote:
> > My husband's computer died today.
>
> First:
>
> 1. Back up everything on all of the drives in the old computer.
>
> 2. Take an image of the system drive in the old computer.
>
> 3. Copy th
On 03/15/2016 11:59 AM, Lisi Reisz wrote:
My husband's computer died today.
First:
1. Back up everything on all of the drives in the old computer.
2. Take an image of the system drive in the old computer.
3. Copy the above to another device and put the copy off-site.
What is the make an
My husband's computer died today. We rushed out and got another, cheap,
temporary one while his main one is being repaired. I said that I could get
it up and running quickly. Famous last words.
I downloaded the most recent Jessie Net-install + firmware, didn't checksum it
because of the enor
On Jun 8, 2015, at 7:01 AM, Martin Michlmayr wrote:
> * Rick Thomas [2015-06-07 19:39]:
>> I’ve attached a screenlog file from “screen -L /dev/ttyUSB0 115200”
>> if that’s any help. The VT100-style curses stuff makes it a bit
>> hard to interpret…
>
> From the log it looks like you didn't fin
* Rick Thomas [2015-06-07 19:39]:
> I’ve attached a screenlog file from “screen -L /dev/ttyUSB0 115200”
> if that’s any help. The VT100-style curses stuff makes it a bit
> hard to interpret…
>From the log it looks like you didn't finish the installation. These
are the last messages in the log:
On Jun 7, 2015, at 7:39 PM, Rick Thomas wrote:
>
> On Jun 6, 2015, at 10:55 AM, Martin Michlmayr wrote:
>
>> * Rodrigo Valiña Gutiérrez [2015-05-18 13:42]:
>>> The relevant part of /var/log/installer/syslog seems to be this:
>> ...
>>> May 17 15:19:13 base-installer: info: could not determin
* Rodrigo Valiña Gutiérrez [2015-05-18 13:42]:
> The relevant part of /var/log/installer/syslog seems to be this:
...
> May 17 15:19:13 base-installer: info: could not determine kernel flavour
The installer is fixed now and you can install Debian on the
SheevaPlug (and other plug variants) again.
>> But now the installer fails in the "Install the base system" step,
>> saying: "No installable kernel was found in the defined APT sources"...
>> when the last time I tested with changed machid and original uImage it
>> worked with the same sources.
>
>What does /var/log/syslog say when this happ
* Rodrigo Valiña Gutiérrez [2015-05-17 16:09]:
> But now the installer fails in the "Install the base system" step,
> saying: "No installable kernel was found in the defined APT sources"...
> when the last time I tested with changed machid and original uImage it
> worked with the same sources.
Wh
>Does this boot?
>
>This is how I prepare the image:
>
>wget
>http://ftp.debian.org/debian/dists/jessie/main/installer-armel/current/images/kirkwood/device-tree/kirkwood-sheevaplug.dtb
>wget
>http://ftp.debian.org/debian/dists/jessie/main/installer-armel/current/images/kirkwood/netboot/marvell/sh
I am not an expert...
The workaround just worked, but I don't know whether "0692
Marvell RD-88F6281 Reference Board"
is a valid machid for the sheevaplug, instead of the 'original' 0831.
At the beggining it worked, but now I have a problem: the sheevaplug
ethernet subsystem does not work
* Martin Michlmayr [2015-05-16 21:37]:
> So the best solution now is to append the device tree blob (DTB) to
> the kernel in the installer. This way, the kernel will find the
> correct device tree and can boot (and everything else will work since
> flash-kernel already appends the DTB on the Shee
* Rick Thomas [2015-05-16 17:47]:
> > - In u-boot:
> >
> > setenv machid 0692
> > saveenv
This is not the correct solution.
The problem is that there are different ways to boot on ARM machines.
The old way was for the boot loader to pass a machine ID to the kernel
which would tell the kerne
On May 16, 2015, at 10:33 AM, Rodrigo Valiña Gutiérrez
wrote:
> I had the same problem installing Debian 8 'Jessie' on a SheevaPlug.
>
> I solved it temporarily by doing the following:
>
> - In u-boot:
>
> setenv machid 0692
> saveenv
>
> - Then install normally. The 'make the system bo
I had the same problem installing Debian 8 'Jessie' on a SheevaPlug.
I solved it temporarily by doing the following:
- In u-boot:
setenv machid 0692
saveenv
- Then install normally. The 'make the system bootable' phase will fail
because flash-kernel fails:
/var/log/installer/syslog:
Ma
Hello
I'm trying to install debian 8.0 (jessie) on a Sheevaplug
I follow the guide of Martin Michlmayr
I don't succeed
down is the capture of the output
note the same procedure for wheezy was successfull
some help would be appreciated
(sorry for my english)
rb
*
U-Boot 2011.12 (Ma
On Mon 15 Sep 2014 at 16:26:30 -0300, Adrián Orellana wrote:
> I'm trying to install jessie amd64 and with the installer I got two
> important issues:
> 1st: when it asked me about non free drivers, I told him that there were in
> an external device (usb), but it never saw after several attemps.
Hi,
I'm trying to install jessie amd64 and with the installer I got two
important issues:
1st: when it asked me about non free drivers, I told him that there were in
an external device (usb), but it never saw after several attemps.
2nd. I need to manually partition my disk as it have another distri
25 matches
Mail list logo
