* Rick Thomas [2022-06-10 00:19]:
> > 1) Install bullseye
>
> Worked fine and checked OK (yeah, it's Bullseye).
Thanks for testing! I've updated my web pages to link to the bullseye
download images.
> > Warning: if this fails, you need OpenOCD to recover. I can't help
> > with this. (I ha
in case. These instructions
are still correct:
https://www.cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade/
(It's not the latest version of u-boot, but it is one that worked for
a long of people. Rick Thomas agreed to test the latest and report
back. I will update my web site accordingl
Hi Martin,
On Wed, Jun 8, 2022, at 10:17 PM, Martin Michlmayr wrote:
>> Indeed, I do have two OpenRD machines running right now, an
>> "Ulitmate" and a "Client". Both are available for testing. Let me
>> know what you would like me to do and I'll ge
image!
> Marvell>>
>
> On 09/06/2022 15:14, Gilles wrote:
>> I used another USB stick, with the root+boot formated in ext4, the
>> install completed, but… Uboot fails loading:
>>
>> =
>> U-Boot 2011.12 (Mar 11 2012 - 18:59:46)
>> Marv
till correct:
https://www.cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade/
(It's not the latest version of u-boot, but it is one that worked for
a long of people. Rick Thomas agreed to test the latest and report
back. I will update my web site accordingly.)
I'm not sure about
Verifying Checksum ... Bad Data CRC
ERROR: can't get kernel image!
Marvell>>
On 09/06/2022 15:14, Gilles wrote:
I used another USB stick, with the root+boot formated in ext4, the
install completed, but… Uboot fails loading:
=
U-Boot 2011.12 (Mar 11 2012 - 18:59:46)
Marvell-Sheevap
I used another USB stick, with the root+boot formated in ext4, the
install completed, but… Uboot fails loading:
=
U-Boot 2011.12 (Mar 11 2012 - 18:59:46)
Marvell-Sheevaplug - eSATA - SD/MMC
SoC: Kirkwood 88F6281_A0
DRAM: 512 MiB
WARNING: Caches not enabled
NAND: 512 MiB
In
Gilles writes:
> On 08/06/2022 00:54, Rick Thomas wrote:
>> On Tue, Jun 7, 2022, at 6:32 AM, Gilles wrote:
>>> It ends with a single error : "partman: mkswap: can't open '/dev/sda5':
>>> No such file or directory":
>>>
>>> https://pastebin.com/raw/h0beZWnP
>> It looks like /dev/sd5 doesn't actual
On 08/06/2022 00:54, Rick Thomas wrote:
On Tue, Jun 7, 2022, at 6:32 AM, Gilles wrote:
It ends with a single error : "partman: mkswap: can't open '/dev/sda5':
No such file or directory":
https://pastebin.com/raw/h0beZWnP
It looks like /dev/sd5 doesn't actually exist. This is probably because
On Tue, Jun 7, 2022, at 6:32 AM, Gilles wrote:
> It ends with a single error : "partman: mkswap: can't open '/dev/sda5':
> No such file or directory":
>
> https://pastebin.com/raw/h0beZWnP
It looks like /dev/sd5 doesn't actually exist. This is probably because the
USB stick has an MBR partition
On 07/06/2022 05:57, Martin Michlmayr wrote:
* Gilles [2022-06-06 18:02]:
Using a fresh 64GB USB keydrive, I sucessfully launched the D11 installer
with default options… which fails creating the swap partition:
https://gofile.io/d/MO7pb1
Can you go back to the main menu when this happens and
* Paul Wise [2022-06-03 09:36]:
> > Does it mean Debian 11 still isn't available for that device?
>
> I found that there are Sheevaplug installer images for bullseye,
> so I suspect that Debian 11 still supports the Sheevaplug,
> so Martin probably just hasn't updated
Perhaps it will break at some point, but I have one of my Sheevaplugs on
bookworm, and there is a 5.17.0-1-marvell kernel for it.
Jim
Thanks, good to know !
May be I'll try to give a test...
Good example of long time support !!!
Le 03/06/2022 à 03:36, Paul Wise a écrit :
On Thu, 2022-06-02 at 14:15 +0200, Gilles wrote:
A search in the archives returned no hits.
This mail says Sheevaplug support will be dropped *
On Thu, 2022-06-02 at 14:15 +0200, Gilles wrote:
> A search in the archives returned no hits.
This mail says Sheevaplug support will be dropped *after* bullseye:
https://lists.debian.org/msgid-search/5393e08f-0224-4f83-a1d6-3c2780401...@www.fastmail.com
That doesn't seem to have happ
On Thu, Jun 2, 2022, at 5:15 AM, Gilles wrote:
> Hello,
>
> A search in the archives returned no hits.
>
> Martin Michlmayr's page* shows how to install Debian 10 on a USB
> keydrive to run on a Sheevaplug.
>
> Does it mean Debian 11 still isn't availa
Hello,
A search in the archives returned no hits.
Martin Michlmayr's page* shows how to install Debian 10 on a USB
keydrive to run on a Sheevaplug.
Does it mean Debian 11 still isn't available for that device?
Thank you.
* https://www.cyrius.com/debian/kirkwood/sheevaplug/install/
On 30/09/2019 11:53:16+0200, Uwe Kleine-König wrote:
> Hello,
>
> On 9/30/19 10:37 AM, Rick Thomas wrote:
> > Another case where this argument falls down is the Cubox-iPro which has two
> > hardware clocks. The first, labeled /dev/rtc0 by the Debian kernel, is
> > accurate as long as the power
Hello,
On 9/30/19 10:37 AM, Rick Thomas wrote:
> Another case where this argument falls down is the Cubox-iPro which has two
> hardware clocks. The first, labeled /dev/rtc0 by the Debian kernel, is
> accurate as long as the power is up, but it has no battery backup, so when
> the power fails t
> On Sep 30, 2019, at 12:41 AM, Alexandre Belloni
> wrote:
>
> My opinion is that distributions should stop relying on HCTOSYS and do
> the RTC read from userspace. This is especially important because
> distros are hardcoding rtc0 as the RTC to read from which is most likely
> to not be the
Thanks for the explanation!
> On Sep 30, 2019, at 12:22 AM, Uwe Kleine-König wrote:
>
> IIRC systemd-timesyncd fast forwards the time at boot time to be not
> earlier than before the last shutdown. Maybe this is not active for you?
> (There is
> /lib/systemd/system/systemd-timesyncd.service.d/di
gt; > On Sep 28, 2019, at 1:14 PM, John Blake wrote:
> > > >
> > > > After upgrading my Sheevaplug from Stretch to Buster, it would not
> > > > set the system time from the RTC at boot. Here is what I see in
> > > > dmesg output:
> >
hine. I think I’ll hold off on installing
> >>> that update for a while!
> >>>
> >>> And, FWIW:
> >>>
> >>> rbthomas@sheeva:~$ grep RTC_DRV_CMOS /boot/config-4.19.0-6-marvell
> >>> CONFIG_RTC_DRV_CMOS=m
> >
> &
;
>>> rbthomas@sheeva:~$ grep RTC_DRV_CMOS /boot/config-4.19.0-6-marvell
>>> CONFIG_RTC_DRV_CMOS=m
>
> Note that CONFIG_RTC_DRV_CMOS isn't relevant for the Sheevaplug. The
> relevant symbol is CONFIG_RTC_DRV_MV there.
So here’s what I get for that:
rbtho
Hello,
[I repaired the quoting style and expanded To: a bit]
On Sun, Sep 29, 2019 at 07:36:27PM +, John Blake wrote:
> On Saturday, September 28, 2019, 3:52:11 PM MDT, Rick Thomas
> wrote:
> > On Sep 28, 2019, at 1:14 PM, John Blake wrote:
> > >
> > > Afte
I do not have this problem on my sheevaplug running kernel ‘4.19.67-2’ . I see
that ‘4.19.67-2+deb10u1’ is available, but not yet installed on this machine.
I think I’ll hold off on installing that update for a while!
And, FWIW:
rbthomas@sheeva:~$ grep RTC_DRV_CMOS /boot/config-4.19.0
Thanks for your tips, now I have a working Debian Buster on my
SheevaPlug! See
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934974#30
Bye
Florian
>>>>> "Martin" == Martin Michlmayr writes:
> * Florian Dütsch [2019-09-04 21:43]:
>> So I used the manual
>> https://www.cyrius.com/debian/kirkwood/sheevaplug/install/ from Martin
>> Michlmayr. As a first step a had to upgrade u-boot. I stric
* Florian Dütsch [2019-09-04 21:43]:
> So I used the manual
> https://www.cyrius.com/debian/kirkwood/sheevaplug/install/ from Martin
> Michlmayr. As a first step a had to upgrade u-boot. I strictly
> followed https://www.cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade/ and
>
* Florian Dütsch [2019-09-04 21:43]:
> I found a SheevaPlug at home I haven't used for many years.
Unfortunately, not many people still have this hardware and as such
it's not well tested. :(
> 2 USB Device(s) found
>scanning usb for storage devices... 0 Storage De
Hi,
I found a SheevaPlug at home I haven't used for many years. As a first step
I wanted to install an actual, fresh operation system.
So I used the manual
https://www.cyrius.com/debian/kirkwood/sheevaplug/install/ from Martin
Michlmayr. As a first step a had to upgrade u-boot. I str
; Does this mean that my OpenRD hardware will no longer be supported in Buster?
> What about SheevaPlug hardware? Is that still supported by upstream u-boot?
>
>> * u-boot:
> …
>> - [armel] Drop openrd targets (no longer supported upstream).
>
> Nice, physically s
.debian.org/intro/organization#donations-hardware
>
> I thought that since IIRC you are interested in the armel port, the
> SheevaPlug would be interesting to you in particular, other armel
> porters might be interested too I guess.
I already have one :-D
Thanks for your support for armel!
C
IIRC you are interested in the armel port, the
SheevaPlug would be interesting to you in particular, other armel
porters might be interested too I guess.
In general, this mailing list is a better target for donations of such
old hardware, since it doesn't make good buildd hardware and the ARM
porters a
On Wed, Aug 23, 2017 at 4:38 AM, Rasmus Vind wrote:
> Hey guys,
>
> I just subscribed to this list to give away my old white SheevaPlug. I
> don't use it anymore and would like to give it away. I only ask that you
> pay for the shipping. I live in Denmark.
Thanks for your kin
Hey guys,
I just subscribed to this list to give away my old white SheevaPlug. I
don't use it anymore and would like to give it away. I only ask that you
pay for the shipping. I live in Denmark.
Any takers?
Rasmus
I've follow this guide
http://www.blaicher.com/2012/07/installing-debian-on-a-sheevaplug-into-flash/
to
upgrade my GuruPlug/SheevaPlug to New Debian 8.
I use an USB Stick and all work fine, but when i try to install it on
inside flash memory using:
*ubiformat /dev/mtd2 -s 512*
its fail
nge them. Also,
the name flash-kernel is a misnomer on the SheevaPlug because it
doesn't write the kernel to flash. Your SheevaPlug boots from SD card
(via that bootcmd_mmc).
On u-boot, you typically require an "uImage" file. Instead of booting
a kernel directly (e.g. /boot/vmlin
Hello,
> It depends on how you've configured u-boot. Connect to u-boot and run:
>
> printenv bootcmd
>
> If it looks like this:
>
> bootcmd=setenv bootargs ${bootargs_console}; run bootcmd_usb; bootm
> 0x0080 0x0110
>
> (bootcmd_usb might be bootcmd_mmc or bootcmd_sata)
It is bootcmd_mmc
* Christoph Pleger [2016-01-04 10:59]:
> I already posted my question on debian-us...@lists.debian.org, but
> probably here is a better place:
>
> I want to enable apparmor on my SheevaPlug device. This requires the
> kernel command line parameters "apparmor=1 security=apparm
gt; Hello,
>
> I already posted my question on debian-us...@lists.debian.org, but
> probably here is a better place:
>
> I want to enable apparmor on my SheevaPlug device. This requires the
> kernel command line parameters "apparmor=1 security=apparmor" to be set.
> But
Hello,
I already posted my question on debian-us...@lists.debian.org, but
probably here is a better place:
I want to enable apparmor on my SheevaPlug device. This requires the
kernel command line parameters "apparmor=1 security=apparmor" to be set.
But I do not know how to set kern
: Stretch installer fails to detect network device for Sheevaplug
On Fri, 2015-11-27 at 13:57 +, Steve Ginter wrote:
> Hi all,
> The newest stretch installer does not detect the network card, and
> manually selecting the driver for "mv643xx_eth: Ethernet driver for
> Marvell MV643
On Fri, 2015-11-27 at 13:57 +, Steve Ginter wrote:
> Hi all,
> The newest stretch installer does not detect the network card, and
> manually selecting the driver for "mv643xx_eth: Ethernet driver for
> Marvell MV643XX" does not work. I keep getting kicked back to the
> "Detect Network Hardware
atest installer from here:
http://ftp.debian.org/debian/dists/stretch/main/installer-armel/current/images/kirkwood/netboot/marvell/sheevaplug/uImage
http://ftp.debian.org/debian/dists/stretch/main/installer-armel/current/images/kirkwood/netboot/marvell/sheevaplug/uInitrd
and I'm loading the
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:
* John Hughes [2015-06-08 08:51]:
> >bootcmd=setenv bootargs $(bootargs_console); run bootcmd_mmc; bootm
> > 0x0080 0x0110
> >
> Replacing "$(bootargs_console)" (cut'n'pasted from
> http://www.cyrius.com/debian/kirkwood/sheevaplug/install/)
5: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.
>>
>> --
>> Martin Michlmayr
>> http://www.cyrius.com/
>
> Hi Martin!
&g
On 07/06/15 14:09, John Hughes wrote:
But I get no console output with :
bootcmd=setenv bootargs $(bootargs_console); run bootcmd_mmc; bootm
0x0080 0x0110
Replacing "$(bootargs_console)" (cut'n'pasted from
http://www.cyrius.com/debian/kirkwood/sheev
* Ian Campbell [2015-06-07 13:55]:
> > testvar=$(teststring)
> > It looks like the interpolation is not working.
>
> I think u-boot only expands ${teststring} not $(teststring), so the
> instructions have a typo.
John, does it work with ${...}?
--
Martin Michlmayr
http://www.cyrius.co
On Sun, 2015-06-07 at 14:09 +0200, John Hughes wrote:
> Marvell>> setenv teststring abcdef
> Marvell>> setenv testcmd 'setenv testvar $(teststring)'
> Marvell>> run testcmd
> Marvell>> printenv testvar
> testvar=$(teststring)
> It looks like the interpolation
4.10+dfsg1-5 (Apr 07 2015 - 21:57:04)
Marvell-Sheevaplug
SoC: Kirkwood 88F6281_A0
DRAM: 512 MiB
WARNING: Caches not enabled
NAND: 512 MiB
MMC: MVEBU_MMC: 0
In:serial
Out: serial
Err: serial
Net: egiga0
88E1116 Initialized on egiga0
Warning: Your bo
On 07/06/15 12:40, John Hughes wrote:
On 06/06/15 19:55, Martin Michlmayr wrote:
The installer is fixed now and you can install Debian on the
SheevaPlug (and other plug variants) again.
I must be stupid because I'm having some trouble with this.
I am of course, stupid. Problem was
On 06/06/15 19:55, Martin Michlmayr wrote:
The installer is fixed now and you can install Debian on the
SheevaPlug (and other plug variants) again.
I must be stupid because I'm having some trouble with this.
When I try booting
http://ftp.debian.org/debian/dists/jessie/main/installer-
* 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)
* Rick Thomas [2015-05-25 18:06]:
> I've got an old Sheevaplug I'd like to install Jessie on, so I'm
> getting ready to install your new uboot, but I've never used OpenOCD
> before (if I have to recover) Can you point me to instructions for
> doing that --
* John Mbayu [2015-05-29 08:35]:
> Did you find the cause of the problem with this Jessie installer?
Thanks to Rasmus Abrahamsen who gave me remote access to his
SheevaPlug, I have identified and fixed the issue today (bug #787563).
I believe an update to Debian 8 with a new installer is plan
Hello,
Did you find the cause of the problem with this Jessie installer?
It is still marked as broken on cyrius.com.
>> 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 tes
On 05/17/15 20:22, Martin Michlmayr wrote:
If someone can try the u-boot binary from
https://people.debian.org/~tbm/u-boot/2014.10+dfsg1-4/ and tell me
whether it works I'd appreciate it. Make sure you know how to use
OpenOCD if you have to recover.
Hi Martin,
I've got an old Shee
>> 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
* Martin Michlmayr [2015-05-17 20:22]:
> Even better:
>
> nand erase 0x0 0x6
I meant:
nand erase 0x0 0x7
> nand write 0x080 0x0 ${filesize}
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
with a subject of "unsubscribe
* Rick Thomas [2015-05-11 00:42]:
> http://cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade/
> you recommend updating uboot before doing the install. You give a
> link to version 2011.12-3, but looking at the referenced website, it
> seems that there are later versions of ubo
* drEagle [2015-04-10 06:56]:
> > Can someone confirm that the 2014.10+dfsg1-4 u-boot on SheevaPlug
> > passes a correct DT to the kernel?
>
> No it doesn't.
> I just made a report #782293
Thanks!
In any case, we cannto assume that people are running a current
vers
* 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
kirkwood/netboot/marvell/sheevaplug/uImage
># Remove the u-boot header
>dd if=uImage of=kernel.without bs=1 skip=64
>rm -f uImage
># Append device tree
>cat kirkwood-sheevaplug.dtb >> kernel.without
># Create new uImage
>sudo apt-get install u-boot-tools
>mkimage -A arm
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
etherne
e DTB on the SheevaPlug).
Here's a test image.
Take the kernel from http://www.cyrius.com/tmp/sheevaplug/uImage
Take the ramdisk from
http://ftp.debian.org/debian/dists/jessie/main/installer-armel/current/images/kirkwood/netboot/marvell/sheevaplug/uInitrd
Boot it as described here:
http://www.
figured it) but not the device tree. Newer kernels require the
device tree on the SheevaPlug and no longer support the machine ID,
which is why you get the error about the machine ID not being known.
Ideally, u-boot would pass the device tree to the kernel, but this is
currently not done in Deb
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
>
> - The
Hi,
I’ve got an old sheevaplug (non-esata) that I’d like to install with wheezy
(or, dare I suggest, jessie).
Reading your web page at
http://cyrius.com/debian/kirkwood/sheevaplug/
and
http://cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade/
you recommend updating uboot before doing
Hello everyone,
after the upgrade to jessie on my Qnap NAS worked so well yesterday
(thanks again to Arjen for trying it first), I thought I would try the
upgrade on my Sheevaplug today.
I am using the eSata-model with an SD-card for the Debian installation,
the device was previously installed
Am 08.04.2015 um 21:36 schrieb Martin Michlmayr:
> My SheevaPlug instructions don't work for jessie. I'm not sure if we
> just need an update to the instructions or whether a fix in the
> installer is required. Unfortunately, I don't have a SheevaPlug
> anymor
My SheevaPlug instructions don't work for jessie. I'm not sure if we
just need an update to the instructions or whether a fix in the
installer is required. Unfortunately, I don't have a SheevaPlug
anymore, so I am looking for help.
The instructions currently refer to the 2011.12-
On Thu, 26 Mar 2015 15:20:03 +0100, Gilles
wrote:
>Next, tried connecting with Debian and minicom, and then CuteCom, same
>issue: The Sheevaplug says nothing when rebooting the device :-/
For some reason, rebooting the device bricked it.
Back in business after following the documents be
Du schriebst am 26. Mar um 13:33 Uhr:
> But I'm also getting errors when trying to upgrade the kernel after
> running "apt-get update":
>
>
> # apt-get upgrade
>
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> 0 upgraded, 0 newly
On Wed, 25 Mar 2015 18:00:03 +0100, Gilles
wrote:
>I'm no expert and would like to upgrade a Sheevaplug to the latest
>stable release of Debian.
I rebooted with a cable connecting my Windows host to the mini-USB
port, but get nothing from the Sheevaplug, although the serial
connec
On Thu, 26 Mar 2015 13:30:01 +0100, Rick Thomas
wrote:
>Ive heard (but cant remember where, sadly) that this is *not* a sign of the
>mmcblk device wearing out. Its actually (according to my, possibly faulty,
>recollection) indicative of a difference in understanding between uboot and
>Linux
I’ve heard (but can’t remember where, sadly) that this is *not* a sign of the
mmcblk device wearing out. It’s actually (according to my, possibly faulty,
recollection) indicative of a difference in understanding between uboot and
Linux as to what the partition table should look like for an mmcb
Thanks for the infos.
At 18:09 25/03/2015, Björn Wetterbom wrote:
You should start at
<http://cyrius.com/debian/kirkwood/sheevaplug/>http://cyrius.com/debian/kirkwood/sheevaplug/
I think you'll find everything you need there.
(Skickat från min telefon == Sent from my phon
On Wed, 25 Mar 2015 21:00:03 +0100, "Jim MacKenzie"
wrote:
>If your SheevaPlug is already running Debian and you simply want to upgrade
>it, you can upgrade to Debian 7 in-place. This requires a firmware upgrade
>to the SheevaPlug (in some cases) as the Debian 7 kernel isn
If your SheevaPlug is already running Debian and you simply want to upgrade
it, you can upgrade to Debian 7 in-place. This requires a firmware upgrade
to the SheevaPlug (in some cases) as the Debian 7 kernel isn't compatible
with older versions of the SheevaPlug's boot loader. I just u
You should start at
http://cyrius.com/debian/kirkwood/sheevaplug/
I think you'll find everything you need there.
(Skickat från min telefon == Sent from my phone)
On Mar 25, 2015 5:50 PM, "Gilles" wrote:
> Hello
>
> I'm no expert and would like to upgrade a Shee
Hello
I'm no expert and would like to upgrade a Sheevaplug to the latest
stable release of Debian.
Sheevaplug manufacturer GlobalScale provides two files:
Sheeva-Debian7-SW.rar
sheevaplug_env.tar.rar
http://globalscaletechnologies.com/download/
Should I go ahead with those files or are
On 21/01/2015 18:43, Ulrich Kleynmans wrote:
Hello,
in the meantime I found out, that installer hangs if one ext2 file
system is used for installation, i.e. / on ext2 file system with /boot
as a normal subdirectory. Don't know why.
With a separate /boot ext2 file system installation works f
Am 14.01.2015 um 17:22 schrieb Martin Michlmayr:
* Ulrich Kleynmans [2015-01-09 19:29]:
Installation is done with uImage und uInitrd from
ftp.debian.org/debian/dists/stable/main/installer-armel/current/images/kirkwood/netboot/marvell/sheevaplug/.
Installation can be started and works as expected
* Ulrich Kleynmans [2015-01-09 19:29]:
> Installation is done with uImage und uInitrd from
> ftp.debian.org/debian/dists/stable/main/installer-armel/current/images/kirkwood/netboot/marvell/sheevaplug/.
> Installation can be started and works as expected until 'Making the
> syste
Hello,
I want to install current Debian wheezy on a SheevaPlug according to
http://www.cyrius.com/debian/kirkwood/sheevaplug/.
u-boot is updated:
version
U-Boot 2011.12 (Mar 11 2012 - 18:59:46)
Marvell-Sheevaplug - eSATA - SD/MMC
gcc (Debian 4.6.3-1) 4.6.3
GNU ld (GNU Binutils for Debian
Am 09.11.2014 um 22:26 schrieb David Given:
On 08.11.2014 10:44, Markus Krebs wrote:
[...]
Since kernel 3.12 (i. e. when dtb was introduced) I'm experiencing
various erratic problems when transferring files over the network. For
example unison (over ssh) is complaining about "Corrupted MAC on in
On 08.11.2014 10:44, Markus Krebs wrote:
[...]
> Since kernel 3.12 (i. e. when dtb was introduced) I'm experiencing
> various erratic problems when transferring files over the network. For
> example unison (over ssh) is complaining about "Corrupted MAC on input";
> or when I'm trying to read a file
On Sat, 2014-11-08 at 14:53 +0100, Markus Krebs wrote:
> Am 08.11.2014 um 11:48 schrieb Ian Campbell:
> > Taking it upstream would probably be best, I've found the upstream
> > kirkwood maintainers to be very responsive.
>
> Thank you, Ian. How can I take that upstream? Is there another mailing li
s it helped
sometimes, with others it didn't, so I'm afraid it doesn't solve the
real problem (at least not with my Sheevaplug).
--
To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/545f3b1c.9030...@drkrebs.de
On Sat, Nov 08, 2014 at 10:44:25AM +0100, Markus Krebs wrote:
> For example unison (over ssh) is complaining about "Corrupted MAC on
> input"; or when I'm trying to read a file over the network, Windows
I gained this problem upgrading my Dreamplug from "wheezy" to jessie;
disabling checksum offloa
Am 08.11.2014 um 11:48 schrieb Ian Campbell:
Taking it upstream would probably be best, I've found the upstream
kirkwood maintainers to be very responsive.
Thank you, Ian. How can I take that upstream? Is there another mailing list?
--
To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.
On Sat, 2014-11-08 at 10:44 +0100, Markus Krebs wrote:
> Hello,
>
> I've been using a Sheevaplug with an USB-Stick for storage as a server
> for many years now.
> Since kernel 3.12 (i. e. when dtb was introduced) I'm experiencing
> various erratic problems when
Hello,
I've been using a Sheevaplug with an USB-Stick for storage as a server
for many years now.
Since kernel 3.12 (i. e. when dtb was introduced) I'm experiencing
various erratic problems when transferring files over the network. For
example unison (over ssh) is complaining about
Hi Vagrant,
> kerma-sheevaplug-mvsdio.diff is no more needed because it is mainlined with a
> newer version
> ->
> http://git.denx.de/u-boot.git/?p=u-boot.git;a=commit;h=3fe3b4fb1c5adb00502276312696e38e9a7e9b5b
>
> but the env fix/corruption is still waiting for a review
l make patch for features add also. (sata, ext4, haskshell, bootscript)
>> They are just parameters for config files (no real code).
>
> What's the current status of these patches? They no longer apply to
> u-boot v2014.10-rc2; are the remaining patches still needed, or can
Hi!
maintainer of the u-boot-marvell does not seem to be active.
If you can, please talk about this on u-boot ML.
And If you need help, I can help you as a U-boot Custodian.
Best regards,
Nobuhiro
2014-09-03 14:07 GMT+09:00 Vagrant Cascadian :
> On 2014-08-06 22:39:38 -0700, Gérald Kerma wrot
On 2014-08-06 22:39:38 -0700, Gérald Kerma wrote:
> On 07/08/2014 07:19, Paul Wise wrote:
>> On Thu, 2014-08-07 at 06:11 +0200, Gérald Kerma wrote:
>>> Thank's to Debian team who add support of all versions of MVSDIO driver in
>>> the debian u-boot package.
>>
>> Will these be merged too?
>
> Th
1 - 100 of 553 matches
Mail list logo
