Bug#982270: Re Bug#982270 (installer can not find an ehternet driver for CuBox-i4Pro)

> Pushed a fix to git: > > https://salsa.debian.org/kernel-team/linux/-/commit/f952b94621847732b3ed96a74babb89b6a1862f6 Wow! Thanks! At least I now know I'm not crazy... Any idea how long it will be before the fix is in something I can download and install with? Enjoy! Rick

Bug#982270: Re Bug#982270 (installer can not find an ehternet driver for CuBox-i4Pro)

On Tue, Jun 1, 2021, at 11:06 PM, Vagrant Cascadian wrote: > On 2021-06-01, Rick Thomas wrote: > > Is there any estimate of when the assumed fix (linux/5.10.40-1) will > > show up in the installer at [1] ? I'd love to test it! > ... > > [1] https://d-i.debian.org/daily-im

Bug#982270: Re Bug#982270 (installer can not find an ehternet driver for CuBox-i4Pro)

Hi! Is there any estimate of when the assumed fix (linux/5.10.40-1) will show up in the installer at [1] ? I'd love to test it! Failing that, is there some other place I can get an installer SDcard image with that fix? Thanks! Rick [1]

Bug#785419: Bug#855203: hwclock-set: Synchronize from hwclock despite systemd presence

sign it to util-linux. > > Is the problem still present? > > Further: > > On Fri, Mar 17, 2017 at 07:55:31PM +0100, Lukas Wunner wrote: > [...] > > @Rick Thomas: Could you verify if the attached patch solves this issue > > for you? > > Were you able to test the pro

Bug#741663: G4 MDD report (finally) Re: Bug#741663: linux-image-3.13-1-powerpc-smp: therm_windtunnel does not load correctly

task yet. Hope this helps! Rick On Tue, Apr 27, 2021, at 3:55 PM, Rick Thomas wrote: > > > On Tue, Apr 27, 2021, at 12:15 AM, John Paul Adrian Glaubitz wrote:> > > On 4/27/21 8:54 AM, Rick Thomas wrote: > > > I'll look around and see if I have any MDD (mi

Bug#741663: linux-image-3.13-1-powerpc-smp: therm_windtunnel does not load correctly

Hi William! On Thu, Apr 29, 2021, at 11:05 AM, William Bonnet wrote: > > The PowerMac G5 users on this list are kindly asked to confirm the bug > > has been fixed. Until then, I'll reopen it. > > I am running the latest version (5.10.0-6-sparc64-smp #1 SMP Debian > 5.10.28-1 (2021-04-09)

Bug#741663: linux-image-3.13-1-powerpc-smp: therm_windtunnel does not load correctly

On Tue, Apr 27, 2021, at 12:15 AM, John Paul Adrian Glaubitz wrote:> > On 4/27/21 8:54 AM, Rick Thomas wrote: > > I'll look around and see if I have any MDD (mirror drive door -- the type > > in the > > original bugreport) machines. If so, I'll try to find some time

Bug#741663: linux-image-3.13-1-powerpc-smp: therm_windtunnel does not load correctly

On Mon, Apr 26, 2021, at 10:45 PM, John Paul Adrian Glaubitz wrote: > On 4/27/21 2:07 AM, Rick Thomas wrote: > > I've got the latest (Apr 17) running on my G5 right now. No problems. > > Rick, you should just confirm that this particular problem is fixed but I > assume >

Bug#741663: linux-image-3.13-1-powerpc-smp: therm_windtunnel does not load correctly

I've got the latest (Apr 17) running on my G5 right now. No problems. Rick rbthomas@kmac:~$ cat /proc/version Linux version 5.10.0-6-powerpc64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.28-1

Bug#741663: linux-image-3.13-1-powerpc-smp: therm_windtunnel does not load correctly

On Sep 9, 2018, at 1:59 AM, Wolfram Sang wrote: > On Sat, Sep 08, 2018 at 02:48:01PM -0700, Rick Thomas wrote: >> Thanks! Yes, I’ll give it a try. > > Note: You can either build the v4.19-rc1 tar ball which has the patch > already included. Or you can take your Deb

Bug#741663: linux-image-3.13-1-powerpc-smp: therm_windtunnel does not load correctly

Thanks! Yes, I’ll give it a try. On Sep 8, 2018, at 6:51 AM, Salvatore Bonaccorso wrote: > Hi, > > On Mon, Sep 03, 2018 at 11:38:32PM -0700, Rick Thomas wrote: >> Hi Mathieu, >> >> I’m sorry that I don’t have the expertise to apply a patch and build >> a kern

Bug#741663: linux-image-3.13-1-powerpc-smp: therm_windtunnel does not load correctly

Hi Mathieu, I’m sorry that I don’t have the expertise to apply a patch and build a kernel. However, if someone who does have that expertise can build a “.deb’ file and tell me where to download it, I’ll be happy to test and provide detailed feedback. Another possibility, of course, would be

Re: armel/marvell kernel size

On Mar 28, 2018, at 2:22 AM, Rick Thomas <rbtho...@pobox.com> wrote: >> What filesystems do you use? Do you use any (para)virtualization? What >> about addon hardware that you have? Any USB dongles? Anything that you >> can think of? Sound? >> >> Do you use

Re: armel/marvell kernel size

On Mar 27, 2018, at 2:08 PM, Rogério Brito <rbr...@ime.usp.br> wrote: > On 2018-03-27 17:29, Rick Thomas wrote: >> On Mar 27, 2018, at 1:04 PM, Rogério Brito <rbr...@ime.usp.br> wrote: >>> As a related subject, I could compile a more stripped down versio

Re: armel/marvell kernel size

On Mar 27, 2018, at 1:04 PM, Rogério Brito wrote: > As a related subject, I could compile a more stripped down version of > the armel kernel, put it for people to download and ask people to > comment if it works for them, so that we can gauge what people actually > need from

Bug#762634: initramfs-tools: [armhf] mounting rootfs on USB disk fails / some USB host controller drivers missing in initramfs

On Wed, 24 Feb 2016 15:06:27 -0800 Vagrant Cascadian wrote: > On 2016-02-24, Vagrant Cascadian wrote: > > On 2016-02-04, Ben Hutchings wrote: > >> Oh, so the MODULES=most case is bust and we need to list more host > >> controller drivers (or include all modules under

Re: Kernel version for stretch

On Feb 2, 2016, at 11:28 PM, Karsten Merker wrote: > On Tue, Feb 02, 2016 at 02:23:06PM +0100, Cyril Brulebois wrote: >> Niels Thykier (2016-02-02): >>> @Kernel+d-i - What is your take on the following: >>> >>> * How long will it take to have the new

Bug#811351: additional request...

> On Jan 20, 2016, at 2:54 PM, Aaro Koskinen wrote: > > I can add more verbose comments to mainline kernel .dts on how to > enable serial port, and how to select between rs232/485. Andrew, do > you want me to resend the current patches, or can it be done with an >

Bug#811351: additional request...

Hi Aaro, Andrew wrote > On Sun, Jan 17, 2016 at 11:55:19PM -0800, Rick Thomas wrote: >> >> On Jan 17, 2016, at 2:42 PM, Martin Michlmayr <t...@cyrius.com> wrote: >>> * Andrew Lunn <and...@lunn.ch> [2016-01-10 16:38]: >>>> Please can you t

Bug#811351: linux-image-4.3.0-0.bpo.1-kirkwood: MMC does not work on OpenRD Client / fix pending

Package: src:linux Version: 4.3.3-5~bpo8+1 Severity: normal Dear Maintainer, The 4.3.0.0 kernel on an "OpenRD Client" fails to recognize the SD card -- there is no mmc device shown by lsblk. This is fixed by using a modified DTB file provided by Aaro Koskinen. Fix tested by Rick Thom

Bug#783381: upgrade from wheezy to jessie on a PowerMac G4 Silver/Confirmation

Try adding append=“ nomodeset to the end of the main stanza in /etc/yaboot.conf. Then (as root) execute “ybin” to propagate the change to the bootstrap routines. This will set the kernel command line to inhibit the kernel from trying to use hardware acceleration for your video. The

Bug#785419: linux-image-4.0.0-1-armmp: with 2 RTC devices -- need way to chose which one sets system clock on boot

On May 16, 2015, at 12:58 PM, Rick Thomas rbtho...@pobox.com wrote: On May 16, 2015, at 6:02 AM, Ben Hutchings b...@decadent.org.uk wrote: This is not implemented directly by the init system. util-linux installs the script/lib/udev/hwclock-set and a udev rule that runs it for each RTC

Bug#785419: linux-image-4.0.0-1-armmp: with 2 RTC devices -- need way to chose which one sets system clock on boot

On May 16, 2015, at 6:02 AM, Ben Hutchings b...@decadent.org.uk wrote: If that’s correct, I’m not sure if even sysvinit with /etc/default/hwclock could have done the right thing in my case. This is not implemented directly by the init system. util-linux installs the script

Bug#785419: linux-image-4.0.0-1-armmp: with 2 RTC devices -- need way to chose which one sets system clock on boot

On May 16, 2015, at 6:02 AM, Ben Hutchings b...@decadent.org.uk wrote: This is not implemented directly by the init system. util-linux installs the script/lib/udev/hwclock-set and a udev rule that runs it for each RTC device. However, the hwclock-set script does nothing if systemd is

Bug#785419: linux-image-4.0.0-1-armmp: with 2 RTC devices -- need way to chose which one sets system clock on boot

On May 16, 2015, at 3:13 AM, Ian Campbell i...@debian.org wrote: On Fri, 2015-05-15 at 17:55 -0700, Rick Thomas wrote: [...] There does not seem to be any way to over-ride this. There's code in /etc/default/hwclock that would do part of the work in a sysvinit setup, but it seems

Bug#785419: linux-image-4.0.0-1-armmp: with 2 RTC devices -- need way to chose which one sets system clock on boot

Package: src:linux Version: 4.0.2-1 Severity: normal Tags: upstream My cubox-i4pro armhf device has two real-time-clocks. One, snvs, is not battery backed, hence is not useful for setting the system clock on boot after a power failure. The other, pcf8523, does have battery backup.

Bug#782364: linux-image-3.16.0-4-armmp: please configure drivers for both Cubox i4pro real time clocks

On May 6, 2015, at 3:35 AM, Rick Thomas rbtho...@pobox.com wrote: On May 6, 2015, at 3:27 AM, Ian Campbell i...@debian.org wrote: It would be preferable to test the thing in Sid before the upload to jessie-proposed-updates I’ll keep an eye out for it. But I don’t have one

Bug#782364: linux-image-3.16.0-4-armmp: please configure drivers for both Cubox i4pro real time clocks

On May 12, 2015, at 2:11 AM, Ian Campbell i...@debian.org wrote: On Tue, 2015-05-12 at 01:33 -0700, Rick Thomas wrote: On May 6, 2015, at 3:35 AM, Rick Thomas rbtho...@pobox.com wrote: On May 6, 2015, at 3:27 AM, Ian Campbell i...@debian.org wrote: It would be preferable to test

Bug#782364: linux-image-3.16.0-4-armmp: please configure drivers for both Cubox i4pro real time clocks

OK, How will I identify the upload when I see it? The box is running Debian/Sid and I do regular updates. So presumably, I’ll see a “linux-image-3.16.0-4-armmp” package go by sometime soon? And I’ll know I’ve got it when I see two /dev/rtc* devices? As for “rbtho...@cube.rcthomas.org” — I’m

Bug#782364: linux-image-3.16.0-4-armmp: please configure drivers for both Cubox i4pro real time clocks

On May 6, 2015, at 3:27 AM, Ian Campbell i...@debian.org wrote: It would be preferable to test the thing in Sid before the upload to jessie-proposed-updates I’ll keep an eye out for it. But I don’t have one of the cubox models without the battery-backed RTC, so I won’t be able to test that

Bug#782364: linux-image-3.16.0-4-armmp: please configure drivers for both Cubox i4pro real time clocks

On Apr 28, 2015, at 8:02 PM, Fabio Estevam feste...@gmail.com wrote: On Fri, Apr 10, 2015 at 9:08 PM, Ben Hutchings b...@decadent.org.uk wrote: Whenever I reset my cubox-i4Pro by disconnecting the power plug, the hardware real-time-clock gets reset to midnight UTC, Dec 31, 1970. Even

Bug#782364: linux-image-3.16.0-4-armmp: please configure drivers for both Cubox i4pro real time clocks

On Apr 28, 2015, at 8:02 PM, Fabio Estevam feste...@gmail.com wrote: On Fri, Apr 10, 2015 at 9:08 PM, Ben Hutchings b...@decadent.org.uk wrote: Whenever I reset my cubox-i4Pro by disconnecting the power plug, the hardware real-time-clock gets reset to midnight UTC, Dec 31, 1970. Even

Bug#782364: Actually, it makes some sense to keep both clocks

Ben Hutchings indicates that his preference would be to disable the non-battery-backed RTC and enable the battery-backed RTC in the kernel for the Cubox-i4pro. I’m not a kernel hacker, so what I’m about to say may be off the mark, but: If I’m not mistaken, this kernel is intended to be used on

Bug#782364: Actually, it makes some sense to keep both clocks

On Apr 12, 2015, at 6:10 AM, Ben Hutchings b...@decadent.org.uk wrote: On Sun, 2015-04-12 at 01:37 -0700, Rick Thomas wrote: Ben Hutchings indicates that his preference would be to disable the non-battery-backed RTC and enable the battery-backed RTC in the kernel for the Cubox-i4pro. I’m

Bug#782364: linux-image-3.16.0-4-armmp: please configure drivers for both Cubox i4pro real time clocks

Package: src:linux Version: 3.16.7-ckt7-1 Severity: wishlist Tags: newcomer Whenever I reset my cubox-i4Pro by disconnecting the power plug, the hardware real-time-clock gets reset to midnight UTC, Dec 31, 1970. Even though the SolidRun literature says that the i4Pro has a battery backed RTC.

Bug#713943: Not fixed for me

random kernel panics, but i think it is unrelated to this bug : something about radeon-kms (and I only have a software rasterizer for opengl, even if I boot with the video=offb:off video=radeonfb:off kernel argument.). Thank you again. Le 22/04/2014 05:18, Rick Thomas a écrit : On Apr 21

Bug#713943: Not fixed for me

On Apr 21, 2014, at 1:49 PM, Bertrand Dekoninck bdekoni...@free.fr wrote: I've installed jessie with linux-3.13.7-1 last night on my powermac7,3 (2x2.0 ghz). The fans are still crazy, even if i2c-powermac is build-in (and not a module anymore). Hi Bertrand, Have you tried echo

Bug#713943: Lack of i2c_powermac module may be the cause

On Feb 22, 2014, at 12:23 AM, Erik de Castro Lopo er...@mega-nerd.com wrote: Hi, I run debian testing on a dual G5 powermac. Just upgraded from linux-image-3.4-trunk-powerpc64 to linux-image-3.12-1-powerpc64 and found the same issue. The windfarm modules are loading but the about 30

Bug#713943: Lack of i2c_powermac module may be the cause

I have a single processor MacPro G5 PowerMac7,3 running Jessie. model : PowerMac7,3 machine : PowerMac7,3 motherboard : PowerMac7,3 MacRISC4 Power Macintosh detected as : 336 (PowerMac G5) I also have a dual core G5 PowerMac11,2 but it's running MacOS-X. The 7,3

Bug#713943: linux-image-3.9-1-powerpc64: windfarm module is not working any more

On Aug 30, 2013, at 8:01 AM, Vladimir Berezenko qmaster2...@gmail.com wrote: Seems that there's another one problem. From time to time cursor in X become garbage and after some time kernel goes panicking. Last update seems not causing panick, but cursor garbage stayed. The 3.2 kernel works

Bug#736130: Mac64 - wrong colors and other problems

On Jan 24, 2014, at 11:10 AM, Vladimir Berezenko qmaster2...@gmail.com wrote: В письме от 24 января 2014 11:07:51 пользователь Michel Dänzer написал: The mach64 DRM driver never made it into the mainline kernel, so I'm afraid getting DRI working is hopeless (unless you want to revive the

Bug#736130: linux-image-3.12-1-powerpc64 crashes during shutdown of PowerPC G5 Mac. But PowerPC g4 Mac (23-bit) works OK.

Package: src:linux Version: 3.12.6-2 Severity: important -- Package-specific info: ** Version: Linux version 3.12-1-powerpc64 (debian-kernel@lists.debian.org) (gcc version 4.8.2 (Debian 4.8.2-10) ) #1 SMP Debian 3.12.6-2 (2013-12-29) ** Command line:

Bug#736130: linux-image-3.12-1-powerpc64 crashes during shutdown of PowerPC G5 Mac. But PowerPC g4 Mac (23-bit) works OK.

Thanks, Ben, for the very quick response! I'd love to do that. But I don't have a serial console for this machine (no serial port -- it's a PowerMac MacPro G5, 64-bit CPU) and the messages logged at crash time scroll off the screen too fast for me to copy them down (or even photograph). I'll

Bug#736130: linux-image-3.12-1-powerpc64 crashes during shutdown of PowerPC G5 Mac. But PowerPC g4 Mac (23-bit) works OK.

One additional bit of information that may help -- Wheezey ( the 3.2 ppc64 kernel ) doesn't have this problem on this machine. Rick On Jan 19, 2014, at 7:23 PM, Rick Thomas rbtho...@pobox.com wrote: Thanks, Ben, for the very quick response! I'd love to do that. But I don't have a serial

Bug#736130: linux-image-3.12-1-powerpc64 crashes during shutdown of PowerPC G5 Mac. But PowerPC g4 Mac (23-bit) works OK.

On Jan 19, 2014, at 7:41 PM, Ben Hutchings b...@decadent.org.uk wrote: On Sun, 2014-01-19 at 19:23 -0800, Rick Thomas wrote: Thanks, Ben, for the very quick response! I'd love to do that. But I don't have a serial console for this machine (no serial port -- it's a PowerMac MacPro G5, 64

Bug#728936: Seems to be fixed in PowerPC Netinst from Jan 8th

This bug seems to be fixed in Debian GNU/Linux testing Jessie - Official Snapshot powerpc NETINST Binary-1 20140108-22:14 However, that netinst image installs a system that refuses to boot on PowerPC64 -- works fine on powerpc (32-bit) though! I'll be submitting a

Bug#728936: Seems to be fixed in powerpc netinst from Jan 8

This bug seems to be fixed in Debian GNU/Linux testing Jessie - Official Snapshot powerpc NETINST Binary-1 20140108-22:14 However, that netinst image installs a system that refuses to boot on PowerPC64 -- works fine on powerpc (32-bit) though! I'll be submitting a

Bug#728936: Is there a way to ssh into the debian installation process?

. Do you have any experience making a pre seeded bootable CD for powerpc? If so, could you share it with us? Rick On Jan 5, 2014, at 9:48 AM, Gary Driggs gdri...@gmail.com wrote: On Jan 5, 2014, at 1:22 AM, Rick Thomas wrote: So I think I could do the same thing on a PowerPC Mac if I knew

Re: Bug#728936: Bug#731939: debian-installer: USB input not functioning during install

Manfred and Jason, It would help a lot if each of you please reply-all to this with the output of (as root -- and with the USB keyboard and mouse plugged in to the machine) lsusb -v and lsmod That may help tell what USB/HCI driver is needed for your devices. Thanks! Rick

Re: Bug#731939: debian-installer: USB input not functioning during install

On Dec 11, 2013, at 5:06 AM, Cyril Brulebois k...@debian.org wrote: Jason Young doom...@gmail.com (2013-12-11): Package: debian-installer Severity: normal Dear Maintainer, I booted the amd64 netinstall disc for debian jessie, and at first I thought that it was frozen because neither the

Bug#713943: Fwd: Sound and BCM4318 wireless no longer working in Wheezy on late 2005 G5

This may have some relevance to bug#713943 Begin forwarded message from Debian PowerPC list: Resent-From: debian-powe...@lists.debian.org From: Chris Wareham ch...@chriswareham.net Date: August 5, 2013 12:27:06 PM PDT To: debian-powe...@lists.debian.org Subject: Re: Sound and BCM4318 wireless

Bug#684265: Bug#690515: Still with us -- still in Beta3

On Oct 14, 2012, at 11:55 PM, Rick Thomas wrote: On Sep 24, 2012, at 6:26 AM, Milan Kupcevic wrote: Please file a separate debian-installer bug report for problems related to finding other OS's on LVM partitions. Milan OK, here it is: Bug#690515 I hope it's an easy fix. It would

Bug#684265: Still with us

On Sep 24, 2012, at 6:26 AM, Milan Kupcevic wrote: Please file a separate debian-installer bug report for problems related to finding other OS's on LVM partitions. Milan OK, here it is: Bug#690515 I hope it's an easy fix. It would be a shame to see it get into beta3... Rick -- To

Bug#684265: Still with us

On Sep 24, 2012, at 6:26 AM, Milan Kupcevic wrote: Please file a separate debian-installer bug report for problems related to finding other OS's on LVM partitions. Milan Well... I tried it on a machine that was not using LVM, and got the same results. So the bug isn't fixed yet.

Bug#684265: Debian Installer 7.0 Beta2 release bug #684265

On Sep 15, 2012, at 8:36 PM, Ben Hutchings wrote: On Thu, 2012-09-13 at 14:58 -0700, Rick Thomas wrote: [...] 1) It seems likely that adding a udeb for fuse-modules will allow os- prober to identify other Linux OS root partitions and get them added to the boot-loader config file... But only

Bug#684265: Debian Installer 7.0 Beta2 release bug #684265

On Sep 12, 2012, at 10:41 PM, Christian PERRIER wrote: Quoting Rick Thomas (rbtho...@pobox.com): On Sep 12, 2012, at 4:21 PM, Rick Thomas wrote: I have not tried running os-prober from the alt-F2 console during the install, to see if it gives different results. I'll do that and report back

Bug#684265: Debian Installer 7.0 Beta2 release bug #684265

On 09/12/12 23:22, Rick Thomas wrote: On Sep 12, 2012, at 10:41 PM, Christian PERRIER wrote: Quoting Rick Thomas (rbtho...@pobox.com): On Sep 12, 2012, at 4:21 PM, Rick Thomas wrote: I have not tried running os-prober from the alt-F2 console during the install, to see if it gives

Bug#684265: Debian Installer 7.0 Beta2 release bug #684265

On 09/13/12 01:15, Rick Thomas wrote: The umount: can't umount... error message went away, but the three 'no such disk' messages remained. And grub install still objected because there was only one OS... I've attached the relevant section of /var/log/installer/syslog It may be worth noting

Bug#684265: Debian Installer 7.0 Beta2 release bug #684265 -- partial success

On 09/13/12 01:15, Rick Thomas wrote: On 09/12/12 23:22, Rick Thomas wrote: On Sep 12, 2012, at 10:41 PM, Christian PERRIER wrote: Quoting Rick Thomas (rbtho...@pobox.com): On Sep 12, 2012, at 4:21 PM, Rick Thomas wrote: I have not tried running os-prober from the alt-F2 console

Bug#684265: Debian Installer 7.0 Beta2 release bug #684265

On Sep 13, 2012, at 5:49 AM, Milan Kupcevic wrote: When I load the fuse module manually os-prober works fine. Therefore solution for bug reports 684265, 686314, 686631, 687286 is to create fuse-modules udeb package. Patch is available here:

Bug#684265: Debian Installer 7.0 Beta2 release bug #684265

On Sep 10, 2012, at 10:16 PM, Christian PERRIER wrote: Quoting Rick Thomas (rbtho...@pobox.com): I'll be happy to provide installation log files to anyone who wants them. I'd also be happy to look at the relevant code and see if I can figure out what's wrong, but I don't know where to look

Bug#684265: Debian Installer 7.0 Beta2 release bug #684265

On Sep 12, 2012, at 4:21 PM, Rick Thomas wrote: I have not tried running os-prober from the alt-F2 console during the install, to see if it gives different results. I'll do that and report back. Any hints of things I should be looking out for? Here's the stderr/stdout output when os

Bug#636269: Bug #636269 -- Problem is still with us...

I tried again today. I installed Sid from the Sid_d-i PowerPC daily businesscard. Same problem. Here's what I installed: Daily build #1 for powerpc, using installer build from sid ... This build finished at Wed Aug 10 03:24:48 UTC 2011. ... debian-testing-powerpc-businesscard.iso

Bug#614221: Things that make you go hmmmm....

Joey Hess said: Rick Thomas wrote: Well, in the mean-time, there's no way to test new d-i businesscard or netinst CDs beyond the disk partition step. Or, to put it more bluntly: Testing grinds to a halt until this is fixed. Use http://cdimage.debian.org/cdimage/daily-builds/sid_d-i/current

Bug#587290: initramfs-tools: malformed yaboot.conf created when alternate partitions use UUID= in fstab

On 06/27/10 08:19, Ben Hutchings wrote: Please send the files /etc/fstab, /etc/yaboot.conf.old and /etc/yaboot.conf from your system. Ben. OK. Here they are: /etc/yaboot.conf from the hda6 partition (see note [1]) ## yaboot.conf generated by debian-installer ## ## run: man yaboot.conf

Bug#587290: initramfs-tools: malformed yaboot.conf created when alternate partitions use UUID= in fstab

Package: initramfs-tools Version: 0.97 Severity: important The generated /etc/yaboot.conf contains lines append=root=UUID ro for partitions that have their /etc/fstab root line using UUID=... . This makes it impossible to boot into those partitions: the boot progresses to the point

Re: Removal of cramfs support

On Dec 5, 2009, at 10:47 AM, Bastian Blank wrote: Hi folks I intent to remove the cramfs support from the kernel and the cramfsprogs package. Current kernels supports squashfs, which is a far more advanced replacement. It is currently in use by the debian-installer for mips and the powerpc

Bug#519028: linux-image-powerpc has the same broken dependency...

This bug prevents an expert mode install from properly installing Sid unless you chose a non-default kernel. Instead of depending on linux-image-2.6.26-2-powerpc, in Sid, it should depend on linux-image-2.6.29-1-powerpc, because 2.6.26-2 doesn't exist in Sid. The 2.6.26 version may (I

Bug#369760: Video problems installing etch on oldworld PowerPC Mac (beige G3)

On Dec 25, 2008, at 5:22 PM, Moritz Muehlenhoff wrote: On Thu, Jun 01, 2006 at 03:00:47AM -0400, Rick Thomas wrote: Package: debian-installer Severity: Important I've been trying to test install the etch daily netinst CD on an oldworld Mac (beige G3) and I can't get off first base because I

Bug#375422: Boot failure with kernel 2.6.15 on G4

. I think you can close this bugreport. Enjoy! Rick On Nov 27, 2008, at 6:12 PM, Moritz Muehlenhoff wrote: On Sun, Jun 25, 2006 at 05:50:17PM -0400, Rick Thomas wrote: Package: debian-installer I just attempted to install the debian powerpc daily businesscard iso from June 24 on my OldWorld

Bug#499231: updated initramfs-tools now kernel oops during boot sequence - sorta fixed?

On Sep 18, 2008, at 3:55 AM, maximilian attems wrote: On Wed, Sep 17, 2008 at 11:54:01PM -0400, Rick Thomas wrote: Well... I did another dist-upgrade tonite, and the problem went away. Go figure... Some one of the following list of upgrades (extracted from /var/log/ dpkg.log) fixed

Bug#499231: updated initramfs-tools now kernel oops during boot sequence

On Sep 17, 2008, at 4:02 AM, Rick Thomas wrote: I have another system running Sid. I haven't done a dist-upgrade on it yet. So I'll see what happens there. I did the dist-upgrade on my other G4 running Sid, and the oops doesn't happen. Looking at the syslog extracts, it seems

Bug#499231: updated initramfs-tools now kernel oops during boot sequence - sorta fixed?

Well... I did another dist-upgrade tonite, and the problem went away. Go figure... Some one of the following list of upgrades (extracted from /var/log/ dpkg.log) fixed it. 2008-09-17 22:57:17 upgrade ncurses-bin 5.6+20080907-1 5.6+20080913-1 2008-09-17 22:57:23 upgrade libncurses5

Bug#429449: aptitude says kernel-image-2.6-powerpc version 102sarge2 depends on non-existent kernel version

Package: kernel-image-2.6-powerpc Version: 102sarge1 Severity: important aptitude dist-upgrade says: The following packages have been kept back: kernel-image-2.6-powerpc 0 packages upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 0B of archives. After

Bug#410845: [powerpc] The PCILynx firewire driver is broken on PPC machines, and should be disabled.

Package: linux-2.6 When I boot Debian (Etch or Sarge) on my BlueWhite PowerMac, with the old TI PCILynx firewire chip on the motherboard, the pcilynx driver crashes consistently. If I blacklist pcilynx, the crash goes away, but I have no firewire capability.

Bug#369760: Similar symptoms using miboot ofonlyboot floppy

Interestingly enough, I get similar results when booting from the miboot ofonlyboot floppy. Even more interesting, when I use the miboot boot floppy the video is slightly strange (some columns flicker) but usable for installation. Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED]