Re: Enabling llvmpipe in the mesa armhf packages

Le dimanche 06 novembre 2016 à 09:25 +0800, Paul Wise a écrit : > On Wed, Jul 29, 2015 at 10:38 PM, Paul Kocialkowski wrote: > > > Either way, I think it's critical that we seriously take a look at this > > and enable llvmpipe if it doesn't bring significant drawba

Re: Enabling llvmpipe in the mesa armhf packages

Le mardi 28 juillet 2015 à 12:27 +0800, Paul Wise a écrit : > On Tue, Jul 28, 2015 at 1:43 AM, Paul Kocialkowski wrote: > > > Hence, I wonder why exactly is llvmpipe disabled on mesa armhf builds in > > Debian (perhaps it was broken long ago?) and whether we could enable it >

Enabling llvmpipe in the mesa armhf packages

icant usability improvements. Hence, I wonder why exactly is llvmpipe disabled on mesa armhf builds in Debian (perhaps it was broken long ago?) and whether we could enable it again. What do you think? -- Paul Kocialkowski, Replicant developer Replicant is a fully free Android distribution running on sev

Re: Installing Wheezy on DreamPlug: Unable to make the system bootable

Le mardi 12 novembre 2013 à 15:42 -0800, Martin Michlmayr a écrit : > * Paul Kocialkowski [2013-09-01 00:05]: > > Running "udevadm trigger" brings the expected UUID, so I think there is > > a problem somewhere in the partitioner tool since it doesn't > > refre

Re: Kirkwood kernel installation

Le mardi 12 novembre 2013 à 15:50 -0800, Martin Michlmayr a écrit : > * Paul Kocialkowski [2013-08-31 11:09]: > > After installing Debian Wheezy (and generating the u-boot images the > > unorthodox way), I came to realize that apt-get install --reinstall > > linux-image-3.2

Re: Installing Wheezy on DreamPlug: Unable to make the system bootable

Le dimanche 01 septembre 2013 à 00:05 +0200, Paul Kocialkowski a écrit : > Well, it turns out my guess was the right one! I enabled ssh on the > installation and monitored syslog as the installation went and I found > the following message: > > Aug 31 21:54:52 in-target: u

Re: Kirkwood kernel installation

Le dimanche 01 septembre 2013 à 10:23 +0100, Tixy a écrit : > On Sat, 2013-08-31 at 20:51 +0200, Paul Kocialkowski wrote: > > Le samedi 31 août 2013 à 19:24 +0100, Tixy a écrit : > > > I did notice when I first got the Dreamplug that the supplied U-Boot was > > > very s

Re: Installing Wheezy on DreamPlug: Unable to make the system bootable

Le samedi 31 août 2013 à 22:36 +0200, Paul Kocialkowski a écrit : > From the working installation's installer syslog, I can tell that > generating a new initramfs and the u-boot images comes right next after > the u-boot-tools's installation. > Now my guess is that the proble

Re: Installing Wheezy on DreamPlug: Unable to make the system bootable

Le samedi 31 août 2013 à 20:14 +0100, Ian Campbell a écrit : > On Sat, 2013-08-31 at 21:08 +0200, Paul Kocialkowski wrote: > > Le samedi 31 août 2013 à 20:01 +0100, Ian Campbell a écrit : > > > > In any case, there is a bug there -- my guess is that > > > > flash-

Re: Installing Wheezy on DreamPlug: Unable to make the system bootable

Le samedi 31 août 2013 à 20:01 +0100, Ian Campbell a écrit : > > In any case, there is a bug there -- my guess is that > > flash-kernel-installer hangs because of the partitioning layout for some > > reason. Note that running flash-kernel from the installed working system > > with my custom layout

Re: Kirkwood kernel installation

Le samedi 31 août 2013 à 19:24 +0100, Tixy a écrit : > I did notice when I first got the Dreamplug that the supplied U-Boot was > very slow, especially enumerating the USB devices. With the Debian > U-Boot that takes about 3 or 4 seconds, then a second to load the kernel > and initrd. I'm using th

Re: Installing Wheezy on DreamPlug: Unable to make the system bootable

Le samedi 31 août 2013 à 19:16 +0100, Ian Campbell a écrit : > It's the only difference I can see between what you've done and what I > did. Can you try just accepting the default as an experiment? This is insane. Using all the defaults, including the partitioning layout worked. My previous attemp

Re: Kirkwood kernel installation

When I got the dreamplug to finally boot Wheezy, during the expert mode installation on which I skipped making the system bootable, I noticed that it takes u-boot a very long time to load the uImage and uInitrd (about 2 minutes for loading both) from the internal micro sdcard while tftp takes like

Re: Installing Wheezy on DreamPlug: Unable to make the system bootable

Le samedi 31 août 2013 à 10:59 +0100, Ian Campbell a écrit : > I downloaded: > ftp://ftp.uk.debian.org/debian/dists/wheezy/main/installer-armel/current/images/kirkwood/netboot/marvell/dreamplug/ > 7bc3332ed880606509511c7b4b439266 uImage > 6afad330c6d75296255782e79226c94a uInitrd I confirm I use

Re: Kirkwood kernel installation

Le samedi 31 août 2013 à 10:16 +0100, Ian Campbell a écrit : > Not all platforms which need flash-kernel need the u-boot tools. The > installer knows which platforms need what and will normally install > them, but you had to skip that step so you missed out. Ok, if flash-kernel and u-boot-tools ar

Kirkwood kernel installation

After installing Debian Wheezy (and generating the u-boot images the unorthodox way), I came to realize that apt-get install --reinstall linux-image-3.2.0-4-kirkwood did not generate the u-boot images. The flash-kernel packages has to be installed by hand, and it even lacks u-boot-tools as a depend

Installing Wheezy on DreamPlug: Unable to make the system bootable

Hello there! I'm new to this list, and I'm the happy owner of a Globalscale Dreamplug, that I intend to use as a home server, with Debian Wheezy. First, I followed the instructions[1] I could find to properly prepare the DreamPlug (that is, updating U-Boot to the Debian/DENX version), and then I c