On Fri, Nov 24, 2023 at 12:34:50PM -0600, David Hillman wrote:
>
> Package: installation-reports
>
> Boot method: USB stick
> Image version:
> https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-12.2.0-amd64-netinst.iso
> Date: 2023-November-23 11PM GMT
>
> Machine: Dell R720
>
On Fri, Oct 27, 2023 at 02:29:30PM +0100, Steve McIntyre wrote:
> Are either of those ports (armeb/arm64ilp32) actually useful / alive
> at this point?
Not that I have seen. I didn't think anything other than the IXP ever
really used big endian and that's a long time ago. arm64ilp32 seems
to
On Mon, Sep 25, 2023 at 02:03:35AM +0200, Bastian Blank wrote:
> The current way does not work. See all the bug reports about
> uninstallable packages and what not with dkms.
>
> To build modules against version x, you'll need to install version x of
> the headers, not x-1 or x+1. This
On Sun, Jul 30, 2023 at 01:08:13PM +0100, Steve McIntyre wrote:
> Hi Axel!
>
> I'm a little confused here...
>
> You say the machine is a Thinkpad X230, but the attached cpuinfo says
> you have an Atom CPU and the DMI data says it's an ASUSTeK Eee
> PC. What hardware are we actually looking at
On Fri, May 05, 2023 at 07:24:19PM +0200, fab...@greffrath.com wrote:
> Am 05.05.2023 18:23, schrieb Cyril Brulebois:
> > Right, initial support seems to have been merged in time for v6.2-rc1
> > only.
>
> Oh, no!
>
> When will be the earliest chance for a D-I image with kernel >= 6.2?
I am
On Fri, Jun 24, 2022 at 02:10:44PM -0700, Vagrant Cascadian wrote:
> Package: installation-reports
> Severity: normal
> X-Debbugs-Cc: vagr...@debian.org
>
> Boot method: network
> Image version:
> https://d-i.debian.org/daily-images/arm64/20220624-02:19/netboot/netboot.tar.gz
> Date: 2022-06-24
On Mon, Jan 10, 2022 at 05:10:04PM -0800, Vagrant Cascadian wrote:
> Package: u-boot
> Version: 2022.01+dfsg1-1
> Severity: serious
> X-Debbugs-Cc: debian-powe...@lists.debian.org, q...@packages.debian.org,
> binut...@packages.debian.org
>
> Something in the toolchain recently changed which
On Thu, Jul 29, 2021 at 10:23:38PM +0200, John Paul Adrian Glaubitz wrote:
> It should work on the standard 32-bit PowerPC baseline which includes
> AltiVec. Other systems such as PowerPC E500 had their own Debian port
> anyway (powerpcspe).
32 bit powerpc does not require altivec. e300 runs it
Now Debian has a release with a useful package missing. What ever
happened to orphaning a package if you didn't want to maintain it anymore?
I certainly see nothing that make the claim that it isn't suitable for
release justified. It is working very well and does not appear to have
any serious
On Thu, Mar 25, 2021 at 09:45:17AM +1030, Andrew McDonnell wrote:
> Package: debian-installer
> Version: 20190702+deb10u8
> Severity: important
> Tags: d-i
>
> In a preseed file I accidentally had a space before a comment character, which
> caused my preseed to fail in unexpected ways. I could
On Tue, Jan 26, 2021 at 10:33:07PM +0100, Martin wrote:
> On 2021-01-26 14:02, Lennart Sorensen wrote:
> > It is not that simple.
> ...
> > Simply manually putting in the config instead seems like a lot less work.
>
> Thanks for the investigation, Lenna
On Tue, Jan 26, 2021 at 05:24:14PM +0100, Martin wrote:
> Package: keyboard-configuration
> Version: 1.200
> Severity: wishlist
>
> It is convenient to have compose keys for both hands, e.g.
> capslock and ralt, similar to the two shift keys.
>
> When running
> $ sudo dpkg-reconfigure
https://bugzilla.kernel.org/show_bug.cgi?id=201813 looks pretty much
the same. It sounds like it has been fixed in a newer kernel and/or
firmware for the card, but I don't know what the chances of such changes
being backported to the stable kernels are.
--
Len Sorensen
On Tue, Sep 08, 2020 at 05:35:45PM -0400, Lennart Sorensen wrote:
> On Tue, Sep 08, 2020 at 10:35:26PM +0200, Andreas Tille wrote:
> > Control: tags -1 help
> >
> > Hi Debian Arm team,
> >
> > I admit I have no idea how to deal with this except by excluding
>
On Tue, Sep 08, 2020 at 10:35:26PM +0200, Andreas Tille wrote:
> Control: tags -1 help
>
> Hi Debian Arm team,
>
> I admit I have no idea how to deal with this except by excluding
> arm64 from the list of supported architectures which is definitely
> not my prefered way of action.
>
> Any help
On Fri, Jun 05, 2020 at 03:08:55PM +0200, John Paul Adrian Glaubitz wrote:
> Is POWER5 still supported by the Linux kernel? I thought IBM removed a
> bunch of older machines but kept PowerPC 970 support.
4.17 dropped power4. power5 and up are still supported just fine.
--
Len Sorensen
On Fri, Jun 05, 2020 at 08:37:02AM +0200, John Paul Adrian Glaubitz wrote:
> I would like to switch the ppc64 kernel back to 4k pages. The majority
> of our users are people on G5 Macs anyway, so I don't see a point
> in using 64k pages.
>
> Anyone with a large modern POWER machine is going to
On Thu, Oct 10, 2019 at 07:50:33PM +0200, Pavel Kosina wrote:
> Package: installation-guide-amd64
> Severity: normal
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate ***
>
>* What led up to the situation?
> In installation of debian 10,
On Mon, Sep 30, 2019 at 12:51:33PM -0400, Daniel wrote:
> Dear Lennart,
>
> I hope that when one opens a "whishlist bug" at least there is a chance to
> have a confrontation.
>
> The main point I want to address is when you do a "smart installation" it is
> supposed to perform a clean
On Sat, Sep 28, 2019 at 11:27:29PM -0400, Daniel wrote:
> Hi Nicholas,
>
> thanks for your reply, I really appreciated your constructive approach.
>
> I use Debian since 2007 and I did a lot of installation, I personally use a
> FrankenDebian (testing with pinning toward SID and Experimental)
On Tue, Aug 06, 2019 at 08:30:56PM +0200, Holger Wansing wrote:
> I was about to commit these changes, however it came to my mind if such
> changes to the GPL are allowed?
>
> At least the English variant of the GPL is 'official' and is not to be
> changed, so what about changing the quoting
On Fri, May 24, 2019 at 11:10:43AM +0200, mb wrote:
> Package: installation-reports
>
> Boot method: USB pen drive prepared in Windows10 with RUFUS (MBR, GPT, iso,
> dd: always same problem) or with UBUNTU 18 dd command
> Image version:
>
On Tue, Mar 26, 2019 at 07:13:21PM +, Steve McIntyre wrote:
> On Wed, Mar 27, 2019 at 02:58:36AM +0800, 積丹尼 Dan Jacobson wrote:
> >Package: debian-installer
> >
> >Guess what, seen with ASUS X370-A:
>
> Dan, you know better than this. A useful bug report needs much more
> information. For a
On Fri, Dec 07, 2018 at 12:22:38AM +, Steve McIntyre wrote:
> I've no idea why he things this is a regression. But this is something
> we should probably change anyway - installing on RAID is pointlessly
> slow here unless you know how to work around it. And it's been that
> way since
On Fri, Aug 10, 2018 at 10:08:52AM +0200, Herbert Kaminski wrote:
> Am Thu, 9 Aug 2018 14:14:15 -0400
> schrieb lsore...@csclub.uwaterloo.ca (Lennart Sorensen):
>
> > [...]
> > Well 99.9% of installs don't have another linux on the system,
>^
> I
On Thu, Aug 09, 2018 at 07:37:15PM +0200, John Landmesser wrote:
> Package: debian-installer
>
>
> is there a reason why the installer defaults to format given swap partition?
>
> I now know that you can opt out to format swap, but i don't understand that
> formatting swap is default!
>
> I
I found this:
https://bugs.freedesktop.org/show_bug.cgi?id=66722
Seems to indicate they have no intention of supporting python3 since
they believe it can be used from python3 in a different way already.
So semms they think the answer in python3 is to use GObject Introspection
(GIR)
--
Len
On Fri, Jan 26, 2018 at 05:16:38PM +0100, Samuel Thibault wrote:
> Hello Grub maintainers, any idea about this?
Is this too much of a hack:
menuentry ' ' {true}
menuentry 'Help:' {true}
submenu ' Prerequesites for installing Debian.' {
menuentry 'PREREQUISITES FOR INSTALLING DEBIAN'
On Fri, Jan 26, 2018 at 04:21:08PM +0100, melissa M. wrote:
> Package: debian-installer
> Version: stable
> Severity: grave
>
> hi maintainer,
>
> big graphical bug with the installer netinstall of Debian Stretch 9.3, but
> also Testing and Sid.
>
> Ditto with the installer mini iso-Stretch 9.3
On Tue, Nov 14, 2017 at 06:59:41PM +, Holger Levsen wrote:
> you are aware that this would only cause (these) people to switch away
> from Debian, but not from telnet?
I honestly believe they just haven't tried. As long as you indulge them,
they will keep training new people with bad habits.
On Mon, Nov 13, 2017 at 05:16:26PM +, Luca Boccassi wrote:
> Package: busybox
> Version: 1.27.2-1
> Severity: wishlist
> Tags: patch
>
> Dear Maintainers,
>
> Please consider enabling telnetd in the busybox package. A tiny and
> trivial patch to set the config is attached inline. A rebuild
On Fri, Nov 10, 2017 at 04:19:14PM +, Ben Hutchings wrote:
> This is true, but I don't think it's a good reason not to implement a
> mostly-reliable heuristic.
>
> If there are multiple disks, there are usually going to be just 2 of
> them, one of which contains the installer. In any
On Tue, Nov 07, 2017 at 09:56:31PM +0100, Michael Kesper wrote:
> Yes sure but why can't I correct it after the fact?
> Even "rescanning disks" does not let you chose any other disks.
>
> Is there a way of chosing "first internal disk" then?
> Imagine I want to create one installation medium for
I do get this error when using 5.1.30 at the moment:
VBoxClient: VBoxClient (seamless): failed to start. Stage: Setting guest IRQ
filter mask Error: VERR_INTERNAL_ERROR
But that is with 5.2.0 guest utils and 5.1.30 dkms. Maybe not a good
combination to have installed.
--
Len Sorensen
I still get the same unpin error with 5.2.0-dfsg-2. So vboxvideo still
crashes when X starts.
5.1.30-dfsg-1 is fine.
--
Len Sorensen
If you force vboxvideo to build by editing the makefile, you get a
file that crashes when you try to use it. Going back to 5.1.x works
fine however.
There error given is:
kernel: [ 17.290464] [drm:vbox_bo_unpin [vboxvideo]] *ERROR* unpin bad
8f5597836400
So somehow the 5.2.0 version is
On Thu, Sep 28, 2017 at 01:49:50AM +0300, Adrian Bunk wrote:
> What compile times exactly did you measure?
>
> The numbers I got are:
> -O0: 11s
> -O1: 82m
> -O2: 249m
Maybe I did it wrong and failed to change the flag then. I must admit
I did find it odd that I saw no change in time between
I just tried with the gcc 7.2.0 cross compiler. It took 28 minutes to
compile the file but it did finish. It took 5 times the ram and 30
times the time that it took to compile for amd64. It was not stuck,
just doing a lot of work trying to optimize it seems.
Fixing the causes of the warnings
On Wed, Sep 27, 2017 at 01:47:52PM +0200, Ben Hutchings wrote:
> DO NOT use a fat32 partition for /boot!
>
> It will appear to work, but the first upgrade of a package that
> installs into /boot will fail because dpkg cannot create a hard link
> there.
Maybe /boot/efi was what was meant.
--
On Wed, Sep 27, 2017 at 04:39:39PM +0200, Andreas Tille wrote:
> I realised that the first patch was included but I considered it better
> to split it into two.
All good.
> To make things really clear for me: Edmund suggested another upload
> with only -O1 (how can I make sure that -O1 is used
On Tue, Sep 26, 2017 at 08:43:32PM +0200, Andreas Tille wrote:
> Hi Lennart,
>
> thanks again for your analysis of the code.
>
> To summarise: We should go with the patch you suggested originally
>
>
>
On Tue, Sep 26, 2017 at 08:19:59PM +0100, Edmund Grimley Evans wrote:
> It's a possibility to bear in mind, definitely, but the
> perhaps-infinite loop can be observed with a cross-compiler:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876825
I just tried doing the cross compile
On Tue, Sep 26, 2017 at 02:09:56PM -0400, wrote:
> On Tue, Sep 26, 2017 at 07:30:40PM +0200, Andreas Tille wrote:
> > Hi Marc,
> >
> > thanks for the quick response.
> >
> > On Tue, Sep 26, 2017 at 06:45:42PM +0200, Marc Rehmsmeier wrote:
> > > Hi Andreas,
> > >
> > > I am not entirely sure
On Tue, Sep 26, 2017 at 07:30:40PM +0200, Andreas Tille wrote:
> Hi Marc,
>
> thanks for the quick response.
>
> On Tue, Sep 26, 2017 at 06:45:42PM +0200, Marc Rehmsmeier wrote:
> > Hi Andreas,
> >
> > I am not entirely sure what I was doing there and then. That seems to be
> > version 2.1.2,
On Tue, Sep 26, 2017 at 12:21:20PM -0400, Lennart Sorensen wrote:
> Here is a patch that removes all the warnings I see. Maybe that will
> help. I don't have an armel to test on.
>
> Most of the warnings are due to missing #include in a lot of places.
The failure in build may
On Tue, Sep 26, 2017 at 05:48:40PM +0200, Andreas Tille wrote:
> Hi Lennart,
>
> thanks for your suggestions. I hereby will forward it upstream hoping
> for comments.
Here is a patch that removes all the warnings I see. Maybe that will
help. I don't have an armel to test on.
Most of the
On Tue, Sep 26, 2017 at 09:57:09AM +0100, Edmund Grimley Evans wrote:
> The infinite loop is still there with gcc-7. I've created bug #876825.
>
> Before you exclude armel, you could perhaps try doing something about
> this warning, which is given not just on armel and may or may not be
> related
On Thu, Aug 03, 2017 at 07:55:09PM +0200, Samuel Thibault wrote:
> The gtk initrd is like 38MB, at USB 1.0 speed (1.5Mbps) that's almost
> two minutes yes. I however wonder how old a computer needs to be to be
> only 1.0...
I have never seen a machine with only 1.0 USB that could boot from USB.
On Thu, Jul 20, 2017 at 11:30:26AM +1000, Jason Lewis wrote:
> Package: installation-reports
>
> Boot method: usb stick
> Image version:
> http://saimei.ftp.acc.umu.se/cdimage/unofficial/non-free/cd-including-firmware/9.0.0+nonfree/amd64/iso-cd/firmware-9.0.0-amd64-netinst.iso
> Date: 2017-07-20
On Tue, Jul 18, 2017 at 10:40:30AM +0200, standard wrote:
> Package: win32-loader
> Followup-For: Bug #824648
>
> I tried to install Debian (9.0) on a Tablet with Windows 10 Home.
> * SSD-Harddrive with GPT
> * 2 GB RAM
> * 64 bit CPU
> * UEFI-BIOS
>
> After restart I got the error 0xc07b
On Fri, Jul 07, 2017 at 10:10:04PM +0200, Tomasz Buchert wrote:
> Wow, this is nice. Would you mind adding some tests to cover this?
> Ideally, we would have coverage for all rsyncable "dialects" we
> support. Can you commit to collab-maint?
Something like this perhaps:
diff --git
On Fri, Jul 07, 2017 at 10:10:04PM +0200, Tomasz Buchert wrote:
> Wow, this is nice. Would you mind adding some tests to cover this?
> Ideally, we would have coverage for all rsyncable "dialects" we
> support.
I can try to add some test coverage. I will have to check how to do that.
>Can you
I managed to fix almost half the failures in knownproblems by making
--gnu always be tried rather than only when GZIP_OS_UNIX is found.
Doing the same for --rsyncable and --new-rsyncable probably makes sense
too.
The --new-rsyncable was written for gzip 1.4, while gzip 1.6 does things
a bit
On Wed, Jun 28, 2017 at 08:52:31AM +0200, Narcis Garcia wrote:
> If you *will* be connected to the internet you *will* need to install
> security updates;
> Internet is not the only source for packages (). If someone
> installs Debian on 3 computers (or repeats installation 3 times), it
>
I was under the impression stretch would release with 4.9 kernel.
So fixing it in 4.10 and marking it done seems like it might loose the
bug report without ever getting it actually included in stretch.
Will the config change in the 4.10 experimental automatically be included
in any updates to the
On Wed, Mar 08, 2017 at 04:06:17PM +0100, John Paul Adrian Glaubitz wrote:
> The firefox package is built with AltiVec enabled and so is mplayer,
> for example. So, yes, Altivec is actively used and I would honestly
> refrain from disabling it in a performance-sensitive package like
> babl.
>
>
On Fri, Feb 17, 2017 at 07:14:11PM +0100, Michael Siemmeister wrote:
> Last week I tried to install Debian in a virtual-box. Currently I use
> Debian 8.7 for running the virtual-box program. I managed to install
> Debian stable without any problems. Then I cloned the virtual-box and
> tried an
On Sat, Feb 04, 2017 at 11:33:02PM +1000, David wrote:
> Hi. I'm a noob but I think I had a similar problem.
> Legacy BIOS on laptop with 2 identical SATA disks.
> Windows 7 on /dev/sda1. Installed jessie 8.7.1 from USB on /dev/sdb2 (swap
> on sdb1)
> Grub wanted to install to /dev/sda MBR but I
On Mon, Jan 23, 2017 at 04:03:06PM +, Steve McIntyre wrote:
> On Mon, Jan 23, 2017 at 06:43:27PM +0300, Andrey Jr. Melnikov wrote:
> >Package: debian-installer
> >Severity: important
> >Tags: d-i
> >
> >
> >Installation procedure of grub2 dont't transform root= entry from /dev/sd??
> >to UUID
On Sat, Jan 21, 2017 at 11:31:37PM -0800, Josh Triplett wrote:
> I do think we ought to attempt autodetection for this. As long as a
> means exists for preseeders and expert installs to specify one anyway
> (for optional caching proxies), autodetecting by default seems like a
> good idea, to
On Fri, Jan 20, 2017 at 11:25:37AM +0200, :-) wrote:
> Package: installation-reports
>
> Boot method: UEFI from USB flash drive
> Image version: http://cdimage.debian.org/debian-cd/current/amd64/iso-cd/
> Date: 19.01.2017
>
> Machine: HP ProBook 4540s
> Processor: Intel Core i5-3230M
> Memory:
On Wed, Jan 18, 2017 at 10:56:58AM +0100, bkk wrote:
> Package: installation-reports
>
> Boot method: Installer bootet via USB
> Image version:
> http://cdimage.debian.org/cdimage/stretch_di_rc1/amd64/iso-cd/debian-stretch-DI-rc1-amd64-netinst.iso
> Date: 2017-01-18 09:45
>
> Machine:
On Mon, Jan 16, 2017 at 10:46:44PM +0100, Samuel Thibault wrote:
> Package: partman-md
> Version: 77
> Severity: wishlist
>
> Hello,
>
> partman-md doesn't warn when disks to be used for RAID are partitioned
> with GPT without a bios boot partition for embedding (and I haven't seen
>
On Thu, Dec 22, 2016 at 11:28:27AM +, Holger Levsen wrote:
> interesting.
Yes.
> as another data point, for reproducible-builds we're running four i386 build
> nodes on virtual amd64 hardware, with 36GB ram each, and at least building the
> Debian archive works nicely.
But are they amd64
On Tue, Dec 20, 2016 at 10:33:24PM +0100, Rudi Pfau wrote:
> Package: installation-reports
> Severity: normal
>
>
>
> -- Package-specific info:
>
> Boot method: network
> Image version: Debian 8.6.0.i386 1
> Date:
>
> Machine: self build tower
> - board: Asus X99-A II
> - RAM: 32GB (4*8G)
On Sat, Nov 12, 2016 at 10:00:53PM +0200, Adrian Bunk wrote:
> I do not understand this part.
>
> -maltivec should only be set for the code that is behind the runtime
> feature check, so this code is only run on hardware that has AltiVec.
Well a mistake in the configure script is making it set
On Fri, Nov 04, 2016 at 01:33:36PM -0400, Lennart Sorensen wrote:
> And of course I made a typo while copying things into the patch.
>
> Doing another build test of it now.
>
> --- vlc-2.2.4.orig/configure.ac 2016-05-31 12:11:07.0 -0400
> +++ vlc-2.2.4/configure.a
And of course I made a typo while copying things into the patch.
Doing another build test of it now.
--- vlc-2.2.4.orig/configure.ac 2016-05-31 12:11:07.0 -0400
+++ vlc-2.2.4/configure.ac 2016-11-04 12:22:02.543265439 -0400
@@ -1422,25 +1422,24 @@
VLC_SAVE_FLAGS
Actually maybe this simpler version is better. I think I just figured
out why libdeinterlace wasn't getting the altivec flags, which was that
it was listed as deinterlace rather than libdeinterlace.
Doing a build test of it now.
--- vlc-2.2.4.orig/configure.ac 2016-05-31 12:11:07.0
On Fri, Nov 04, 2016 at 10:44:21AM -0400, Lennart Sorensen wrote:
> This would of course go much faster if I currently had access to a
> powerpc box rather than running in qemu. :)
>
> I miss the p710 at my previous job.
So here is the patch I am currently building. I think i
On Fri, Nov 04, 2016 at 10:41:57AM -0400, Lennart Sorensen wrote:
> Well it's not the complete solution yet.
>
> I have it down to only deinterlace being miscompiled (it auto vectorized
> Generic* functions with altivec instructions, which is not good).
>
> At the moment it
On Fri, Nov 04, 2016 at 10:52:05AM +0100, Sebastian Ramacher wrote:
> On 2016-11-03 13:58:58, Lennart Sorensen wrote:
> > On Tue, Nov 01, 2016 at 01:42:17PM -0400, Lennart Sorensen wrote:
> > > Well that looks like it only adds it for libvlccore.
> >
> > So at least
On Tue, Nov 01, 2016 at 01:42:17PM -0400, Lennart Sorensen wrote:
> Well that looks like it only adds it for libvlccore.
So at least something like this is needed, but I think the VLCCORE is
wrong too, and maybe the deinterlace has to be moved to only merge.c
rather than all of deinterl
On Tue, Nov 01, 2016 at 07:37:33PM +0200, Adrian Bunk wrote:
> On Tue, Nov 01, 2016 at 01:08:03PM -0400, Lennart Sorensen wrote:
> > On Tue, Nov 01, 2016 at 12:22:19PM -0400, Lennart Sorensen wrote:
> > > On Tue, Nov 01, 2016 at 04:34:01PM +0200, Adrian Bunk wrote:
> > >
On Tue, Nov 01, 2016 at 12:22:19PM -0400, Lennart Sorensen wrote:
> On Tue, Nov 01, 2016 at 04:34:01PM +0200, Adrian Bunk wrote:
> > This doesn't looks wrong to me.
> >
> > Note that depending on the software --enable-altivec can either mean
> > - compile
On Tue, Nov 01, 2016 at 04:34:01PM +0200, Adrian Bunk wrote:
> This doesn't looks wrong to me.
>
> Note that depending on the software --enable-altivec can either mean
> - compile unconditionally for AltiVec, or
> - enable AltiVec parts with autodetection to only use them when the
> hardware
On Mon, Oct 31, 2016 at 11:13:00PM +0200, Adrian Bunk wrote:
> This actually looks like a bug in upstream configure.ac to me:
> VLC_ADD_CFLAGS([libvlccore],[${ac_cv_c_altivec}])
> ALTIVEC_CFLAGS="$ALTIVEC_FLAGS ${ac_cv_c_altivec} ${ac_cv_c_altivec_abi}"
>
On Mon, Oct 31, 2016 at 04:18:55PM +0100, Cyril Brulebois wrote:
> No, the “certainly did” and “worked fine” bits are wrong.
>
> And that's not just me, we've had users report it, Philip Hands saw it
> as well. So no it did *NOT* work (in the specific case where it actually
> matters).
Yes,
On Sun, Oct 30, 2016 at 05:28:57PM +0100, Cyril Brulebois wrote:
> Package: debootstrap-udeb
> Version: 1.0.85
> Severity: grave
> Justification: renders package unusable
>
> The (re)addition of InRelease support broke debootstrap(-udeb) in a d-i
> context. The sed|tr|sed dance doesn't kill the
On Mon, Oct 24, 2016 at 12:12:41PM +0200, W. Martin Borgert wrote:
> Len, you are right! I just checked the buildbot-0.9.0 branch and it
> does not seem to use the Node server, just some Node tools and
> AngularJS client-side. I wonder where I did got this idea from...
Well there is a mention of
I don't see any mention of Node/JS in buildbot's code or documentation.
I do see requirements for ramlfications and a few other things not in
Debian, but I sure can't find the Node/JS stuff anywere.
--
Len Sorensen
On Tue, Oct 18, 2016 at 08:59:35PM +0200, Remi Vanicat wrote:
> Package: installation-reports
> Severity: important
>
> Dear Maintainer,
>
> -- Package-specific info:
>
> Boot method: CD
> Image version:
>
On Mon, Oct 17, 2016 at 11:49:05AM +0200, Erwan Prioul wrote:
> Package: installation-reports
>
> Boot method: ISO image
> Image version:
> http://cdimage.debian.org/mirror/cdimage/daily-builds/daily/current/ppc64el/iso-cd/debian-testing-ppc64el-netinst.iso
> Date: Mon Oct 17 00:44:56 2016
>
>
On Thu, Oct 06, 2016 at 11:28:07PM +0100, Ben Hutchings wrote:
> Is that actually controlled by straps, though? For the TI SoC I've
> been working with recently, when the boot device is set to eMMC the ROM
> code will look for the SPL in:
>
> 1. boot area
> 2. fixed offsets in main area
> 3.
On Thu, Oct 06, 2016 at 12:29:13PM -0700, Vagrant Cascadian wrote:
> To make matters more complicated, there are definitely some boards
> (Firefly, maybe BeagleBoard-X15) which can install the OS to eMMC, but
> u-boot still has to be loaded from SD card. I don't think we have much
> information on
On Thu, Oct 06, 2016 at 07:45:36AM +, Jonathan Quick wrote:
> Package: installation-reports
> Version: 2.58
> Severity: important
>
> Dear Maintainer,
>
> Whilst installing from a (Jessie) 8.6 netboot installer the GRUB installation
> step failed, leaving the system unbootable.
>
> --
On Thu, Oct 06, 2016 at 04:31:39PM +0200, Gianluca Renzi wrote:
> Just a clue: try to add a module parameter, for example videodepth= where
> you pass to the module offb.
> So if not passed gets the default, otherwise get the correct bpp value
> (8,15,16,24,32)???
The offb.c code seems to clearly
On Thu, Oct 06, 2016 at 07:44:35AM +0200, Mathieu Malaterre wrote:
> That's precisely what I tried yesterday.
>
> Anytime I press 'Enter' after '22 set-mode' or '32 set-depth' I loose
> display (either black or corrupted). when I then type 'boot' it goes
> back to normal 8 bits. I have access to
On Wed, Oct 05, 2016 at 08:55:50PM +0200, Mathieu Malaterre wrote:
> Will do ASAP. For reference:
>
> https://bugs.debian.org/825840#92
>
> and
>
> devalias tells me that 'screen' points to
> '/pci@f000/ATY,RockHopper2Parent@10/ATY,RockHopper2_A@0'
Not sure how that maps to the dev syntax
On Wed, Oct 05, 2016 at 06:40:36PM +0200, Mathieu Malaterre wrote:
> On Tue, Oct 4, 2016 at 10:24 PM, Lennart Sorensen
> <lsore...@csclub.uwaterloo.ca> wrote:
> > On Tue, Oct 04, 2016 at 09:22:17PM +0200, Mathieu Malaterre wrote:
> >> On Tue, Oct 4, 2016 at 4:44 PM, L
On Tue, Oct 04, 2016 at 09:39:12PM +0200, Mathieu Malaterre wrote:
> Here is what I see:
>
> [ 52.270154] bus: 'pci': add driver radeonfb
> [ 52.270224] bus: 'pci': driver_probe_device: matched device
> :00:10.0 with driver radeonfb
> [ 52.270233] bus: 'pci': really_probe: probing
On Tue, Oct 04, 2016 at 09:22:17PM +0200, Mathieu Malaterre wrote:
> On Tue, Oct 4, 2016 at 4:44 PM, Lennart Sorensen
> <lsore...@csclub.uwaterloo.ca> wrote:
> > On Tue, Oct 04, 2016 at 03:49:12PM +0200, Samuel Thibault wrote:
> >> € grep bogl_set_palette *
> &g
On Tue, Oct 04, 2016 at 08:41:45PM +0200, Mathieu Malaterre wrote:
> Hi Len,
>
> Here is the release function I am using:
>
> static void offb_destroy(struct fb_info *info)
> {
> struct offb_par *par = (struct offb_par *) info->par;
> if (info->screen_base)
>
On Tue, Oct 04, 2016 at 08:20:13AM +0200, Mathieu Malaterre wrote:
> Hi,
>
> > Well it seems ATY,Rockhopper2 (not Rockhopper) in the Mac Mini is in fact
> > a Radeon, and the way the radeonfb driver handles the pallete appears
> > to match the cmap_radeon in offb, so perhaps this would work in
On Tue, Oct 04, 2016 at 04:47:21PM +0200, Mathieu Malaterre wrote:
> Yes. If you re-read my post on debian-powerpc :) But getting `modprobe
> radeonfb` to work does not work as you know very well :)
> So the userland code in bterm is correct (no big endian issue).
Yes I also really doubt this is
On Tue, Oct 04, 2016 at 03:49:12PM +0200, Samuel Thibault wrote:
> € grep bogl_set_palette *
> bogl.c: bogl_set_palette = bogl_fb_set_palette;
> bogl.c: bogl_set_palette = bogl_fb_set_palette;
> bogl.c: bogl_set_palette = bogl_tcfb_set_palette;
> bogl.c: the palette with
On Tue, Oct 04, 2016 at 08:20:13AM +0200, Mathieu Malaterre wrote:
> I had time to test this patch yesterday night. It did not work using
> `cmap_radeon` codepath. I even tried changing:
>
> out_le32(par->cmap_adr + 0xb4, (red << 16 | green << 8 | blue));
>
> into:
>
> out_le32(par->cmap_adr +
On Mon, Oct 03, 2016 at 05:30:09PM +, Brett Taylor wrote:
> Package: installation-reports
>
> Boot method: network
> Image version:
> Date: Oct 3 2016 12pm
>
> Machine: supermicro SC826E16/MB-X9DRE-TF+
> Processor: E5-2680v2
> Memory: 36JSF2G72PZ / 36KSF2G72PZ
> Partitions:
>
> Output of
Well it seems ATY,Rockhopper2 (not Rockhopper) in the Mac Mini is in fact
a Radeon, and the way the radeonfb driver handles the pallete appears
to match the cmap_radeon in offb, so perhaps this would work in offb.c
--- a/drivers/video/fbdev/offb.c
+++ b/drivers/video/fbdev/offb.c
@@ -333,7
I think the problem with registereing the PCI address in radeonfb is
that the offb does not unmap its addresses fully in the destroy function.
After all, it allocates both info->screen_base and par->cmap_addr as
using seperate ioremap calls on some hardware. The radeonfb on the
other hand does a
1 - 100 of 630 matches
Mail list logo
