Mike Martin | 1 Jan 01:54 2005
Picon

Re: 43p-140 install issues

(re-sending for the benefit of those on the lists .. sorry Sven)

Would there be any image I can use to install this machine currently?
Here's my situation, If I can get the machine to boot and install by
next week (back to work) my boss will let me keep working on it -
otherwise he'll declare it useless and it'll go back in the closet. If
I can get anything on it I'm ok - It doesn't need to be 2.6.

Attached is /var/log/syslog and /var/log/messages.

Mike Martin

On Fri, 31 Dec 2004 10:53:10 +0100, Sven Luther <sven.luther <at> wanadoo.fr> wrote:
> On Wed, Dec 29, 2004 at 01:51:51PM -0500, Mike Martin wrote:
> > I have a 43p-140, It will netboot, start the installer and let be run
> > through the motions. It doesn't seem to be able to recognize the cdrom
> > or be able to set up the network. This puts a stop on the installation
> > pretty quickly. I can't seem to figure it out on my own. Can anyone
> > help?
> >
> > Attached is a console capture from my latest boot using the Dec. 28th
> > image from:
> > http://people.debian.org/~luther/debian-installer/daily-powerpc-built/daily/powerpc/netboot/
> >
> > Other images are similar.
> 
> Could you try to get the /var/log/syslog and /var/log/messages out of that box
> ?
> 
> > When the installer gets to configuring the network with DHCP, it
(Continue reading)

Debian Bug Tracking System | 1 Jan 02:18 2005
Picon

Processed: typo. sorry!

Processing commands for control <at> bugs.debian.org:

> reopen 278183
Bug#278183: kernel-image-2.6.8-1-686: "invalid operand" in syscall
Bug reopened, originator not changed.

> close 276183
Bug#276183: dovecot-common: better location for configuration files.
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug closed, send any further explanations to Maciej Matysiak <phoner.debian.bugs <at> blah.pl>

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

Jaldhar H. Vyas | 1 Jan 02:01 2005
Picon

Bug#278183: typo. sorry!

reopen 278183
close 276183
thanks

Sorry.  Slip o'the fingers.

--

-- 
Jaldhar H. Vyas <jaldhar <at> debian.org>
La Salle Debain - http://www.braincells.com/debian/

Alexander E. Patrakov | 1 Jan 06:00 2005
Picon

Bug#288062: Dead link to patches

Package: kernel
Version: 2.6.9-1

In /usr/share/doc/kernel-image-2.6.9-1-686/README.Debian.1st.gz, there is a 
line:

> The patches can be found
> at http://svn.debian.org/viewcvs/kernel/tags/kernel/source/${version}.

This link is dead, please replace it with 
http://svn.debian.org/wsvn/kernel/tags/kernel/source/

--

-- 
Alexander E. Patrakov

Marco d'Itri | 1 Jan 11:32 2005
Picon

Re: Bug#288043: udev: kernel allow mounting non-working tmpfs

severity 288043 important
retitle 288043 kernel allow mounting non-working tmpfs
tag 288043 sarge sid help upstream
thanks

On Jan 01, Daniel Jacobowitz <dan <at> debian.org> wrote:

> It appears to be a problem with tmpfs in 2.6.10-rc1, maybe.  Witness:
> 
> root <at> nevyn:/home/drow# mount -t tmpfs tmpfs /mnt/spazmount
> root <at> nevyn:/home/drow# ls /mnt/spazmount
> ls: /mnt/spazmount: Not a directory
> 
> Aha:
> # CONFIG_TMPFS is not set
> 
> I don't know why the tmpfs mount succeeds even though tmpfs is
> disabled.  tmpfs also appears in /proc/filesystems.  That's really
> nasty!  It has something to do with the fact that tmpfs is used for
> in-kernel filesystems.
> 
> Should we be detecting this problem?
Yes, but I have no clue about how to do it. /proc/filesystems does not
work either: see #275874 for details.
That bug log reports that it has been fixed in debian kernels, but
apparently the patch has not been merged by Linus yet.

--

-- 
ciao,
Marco
(Continue reading)

Dionisio Martínez Soler | 1 Jan 11:42 2005

Bug#279689: Similar (probably the same) problem & more info

Followup-For: Bug #279689
Package: kernel-image-2.6.9-1-686
Version: 2.6.9-3

Hi.
I'm seeing a similar problem, probably the same: the booting process 
doesn't finish because of rivafb module, I have on screen an infinite 
loop with the following messages when the rivafb module is probing the card:
-----------------------------------------------------------------------
rivafb_pan_display START
rivafb_pan_display END
rivafb_pan_display START
rivafb_pan_display END
-----------------------------------------------------------------------
This is repeated again and again, and I have to reboot.

The video card is working perfectly with the rivafb module in 
kernel-image-2.6.8-1-686 (v. 2.6.8-10). Here you are the relevant lines 
of kern.log :
------------------------------------------------------------------------
Dec 30 12:11:46 dmsoler kernel: Linux agpgart interface v0.100 (c) Dave 
Jones
Dec 30 12:11:46 dmsoler kernel: rivafb_probe START
Dec 30 12:11:46 dmsoler kernel: rivafb: nVidia device/chipset 10DE002D
Dec 30 12:11:46 dmsoler kernel: rivafb: RIVA MTRR set to ON
Dec 30 12:11:46 dmsoler kernel: riva_get_EDID START
Dec 30 12:11:46 dmsoler kernel: rivafb: Found EDID Block from BUS 1
Dec 30 12:11:46 dmsoler kernel: riva_get_EDID END
Dec 30 12:11:46 dmsoler kernel: riva_update_default_var START
Dec 30 12:11:46 dmsoler kernel: riva_update_var START
(Continue reading)

Debian Archive Maintenance | 1 Jan 12:27 2005
Picon

Bug#286655: fixed

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

kernel-doc-2.6.6 |    2.6.6-2 | all
kernel-doc-2.6.7 |    2.6.7-4 | all
kernel-headers-2.6.6-1 |    2.6.6-1 | alpha
kernel-headers-2.6.6-1-generic |    2.6.6-1 | alpha
kernel-headers-2.6.6-1-smp |    2.6.6-1 | alpha
kernel-headers-2.6.7-1 |    2.6.7-2 | i386
kernel-headers-2.6.7-1 |    2.6.7-3 | ia64
kernel-headers-2.6.7-1-386 |    2.6.7-2 | i386
kernel-headers-2.6.7-1-686 |    2.6.7-2 | i386
kernel-headers-2.6.7-1-686-smp |    2.6.7-2 | i386
kernel-headers-2.6.7-1-itanium |    2.6.7-3 | ia64
kernel-headers-2.6.7-1-itanium-smp |    2.6.7-3 | ia64
kernel-headers-2.6.7-1-k7 |    2.6.7-2 | i386
kernel-headers-2.6.7-1-k7-smp |    2.6.7-2 | i386
kernel-headers-2.6.7-1-mckinley |    2.6.7-3 | ia64
kernel-headers-2.6.7-1-mckinley-smp |    2.6.7-3 | ia64
kernel-image-2.6.6-1-generic |    2.6.6-1 | alpha
kernel-image-2.6.6-1-smp |    2.6.6-1 | alpha
kernel-image-2.6.6-alpha |    2.6.6-1 | source
kernel-image-2.6.7-1-386 |    2.6.7-2 | i386
kernel-image-2.6.7-1-686 |    2.6.7-2 | i386
kernel-image-2.6.7-1-686-smp |    2.6.7-2 | i386
kernel-image-2.6.7-1-itanium |    2.6.7-3 | ia64
kernel-image-2.6.7-1-itanium-smp |    2.6.7-3 | ia64
kernel-image-2.6.7-1-k7 |    2.6.7-2 | i386
kernel-image-2.6.7-1-k7-smp |    2.6.7-2 | i386
kernel-image-2.6.7-1-mckinley |    2.6.7-3 | ia64
(Continue reading)

Debian Archive Maintenance | 1 Jan 12:27 2005
Picon

Bug#286657: fixed

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

kernel-doc-2.6.6 |    2.6.6-2 | all
kernel-doc-2.6.7 |    2.6.7-4 | all
kernel-headers-2.6.6-1 |    2.6.6-1 | alpha
kernel-headers-2.6.6-1-generic |    2.6.6-1 | alpha
kernel-headers-2.6.6-1-smp |    2.6.6-1 | alpha
kernel-headers-2.6.7-1 |    2.6.7-2 | i386
kernel-headers-2.6.7-1 |    2.6.7-3 | ia64
kernel-headers-2.6.7-1-386 |    2.6.7-2 | i386
kernel-headers-2.6.7-1-686 |    2.6.7-2 | i386
kernel-headers-2.6.7-1-686-smp |    2.6.7-2 | i386
kernel-headers-2.6.7-1-itanium |    2.6.7-3 | ia64
kernel-headers-2.6.7-1-itanium-smp |    2.6.7-3 | ia64
kernel-headers-2.6.7-1-k7 |    2.6.7-2 | i386
kernel-headers-2.6.7-1-k7-smp |    2.6.7-2 | i386
kernel-headers-2.6.7-1-mckinley |    2.6.7-3 | ia64
kernel-headers-2.6.7-1-mckinley-smp |    2.6.7-3 | ia64
kernel-image-2.6.6-1-generic |    2.6.6-1 | alpha
kernel-image-2.6.6-1-smp |    2.6.6-1 | alpha
kernel-image-2.6.6-alpha |    2.6.6-1 | source
kernel-image-2.6.7-1-386 |    2.6.7-2 | i386
kernel-image-2.6.7-1-686 |    2.6.7-2 | i386
kernel-image-2.6.7-1-686-smp |    2.6.7-2 | i386
kernel-image-2.6.7-1-itanium |    2.6.7-3 | ia64
kernel-image-2.6.7-1-itanium-smp |    2.6.7-3 | ia64
kernel-image-2.6.7-1-k7 |    2.6.7-2 | i386
kernel-image-2.6.7-1-k7-smp |    2.6.7-2 | i386
kernel-image-2.6.7-1-mckinley |    2.6.7-3 | ia64
(Continue reading)

Harald Dunkel | 1 Jan 15:13 2005
Picon

Re: why should I send you any more patches 4 initrd-tools?


Otavio Salvador wrote:
|
| Well, IMHO, uploads so near of a stable release have to be only to RC
| bugs since a so important package like initrd-tools can brake a lot of
| things and a lot of users. This is the probably reason of your patches
| keep out of this release.
|

Sarge is near release for how many months? 6? Sorry, but
unless there is no comitted release date, this is no excuse
for not applying even the most simple patches. Please take
a look at other important packages: They are updated every
second week (e.g. util-linux, glibc, udev, etc), as expected.
initrd-tools on unstable wasn't changed for more than
4 months, even though a lot of patches and new bug reports
have been filed during this time.

For initrd-tools some really severe bugs are marked as
"normal" instead, e.g. the not existing migration path from
kernel 2.4.x to 2.6.y, if your root disk is sata (#256714).
Or not being able to do an interactive file system check
at boot time, because the keyboard driver modules are not
loaded (#264839). Or the badly broken mapping of scsi
module names (#285430, #266239). Etc.

| Sure your patches are important but the maintainer can't trust your
| patches about all possible implications and in that case it's not
| suitable for uploads near of stable release.

(Continue reading)

Geert Stappers | 1 Jan 15:08 2005
Picon

Bug#277298: installation issue: "No partitionable media were found"

On Sat, Jan 01, 2005 at 03:31:20AM +0100, Frans Pop wrote:
> On Saturday 01 January 2005 03:21, Asirvatham Kripps wrote:
> > I just bought a Dell poweredge SC-420 system with a 80
                                   ^^^^^^

				   mmm, another candidate for
				   bugreport #277298

> > GB SATA hard drive. When trying to install Debian
> > linux, I get a message saying "no partitionable media
> > found".
> >
> > I called Dell support and they say that Debian linux
> > doesn't support the hard drive and Red Hat Enterprise
> > version does. I hope this is not true :-(
> 
> That's bullshit (or, if you prefer, untrue).
> The question is not "does Debian support it", but "does the kernel that 
> Debian currently uses support it".
> 
> Try booting with 'linux26'.
That will work, but read on.

> However, be aware that SATA in some respects is still under development. 
> We see quite a few installation reports with problems on SATA hardware.
> Changing BIOS settings or cable connections sometimes helps.
IIRC the Dell SC420 has no such option in it is BIOS (but it is not needed,
the standard Debian 2.6 Kernel has ata_piix support)

> Things are sure to improve with time (maybe even using patches from Red 
(Continue reading)


Gmane