> Is this limitation mentioned in the Sarge Sparc install manual
> anywhere? I couldn't find it on a cursory scan.
>
there are a few threads about this on www.sunmanagers.org, eg
http://sunportal.sunmanagers.org/pipermail/summaries/2001-September/70.html
this might be of use to the documenters
> I can not get exact log out due to missing libutil.so.1 :)
> But my RC1 install fails on some machine (one which had hard time
> mounting CD initially) with;
>
> anna[4147]: /cdrom/dists//Release
> anna[4147]: : No such file or directory
>
> I have cdrom mounted and /cdrom/dists/*/RElea
>
> The thing seems to be mounting kernel error disapeared now as I
> remember. That may be the source of problem. I think it should error
> and reset kernel IDE driver to use non-DMA mode.
>
> (So no need for my patch in a sense. This relied on kernel error and
> remount.)
>
> By the way, for b
Package: installation-reports
version: rc1
severity: normal
Debian-installer-version: Sarge RC1
downloaded from
http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/i386/rc1/sarge-i386-netinst.iso
uname -a: Linux (none) 2.4.26-1-386 #2 Sat May 1 16:31:24 EST 2004 i686
unknown
Date: 2004-0
> Sounds like a broken CD build without Rock Ridge extensions, perhaps.
I'm pretty sure the cd is ok. I checked by booting another machine. And
if I load the ide modules without dma for hdc, things work normally.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trou
> 1. Patch by Vincent McIntyre (Bug#265636) has good intent but buggy
>as is. (I wish this type of syntax exists for "fail" function.)
That was only a sketch, as I don't have a good understanding of how such
an error should be presented to the user by d-i.
I think t
I've tested Osamu's latest modification to rc1's cdrom-detect (the
"invasive" patch).
(http://people.debian.org/~osamu/pub/sarge-i386-netinst-rc1-hacked.iso
dated 20-Aug-2004 01:52)
It seems to work fine on the hardware I had available.
I may be able to to test with a system that has multiple cd
Additional info:
I tested only with kernel2.4. I shall try 2.6 later on.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
tests with kernel 2.6:
dell latitude d600 - cdrom detection ok
dell lattude cpia - cdrom detection ok
details in the tarball attached
linux26.tar.gz
Description: Binary data
> Thanks. Just to be sure, can you veryfy the version?
> following output is a good start.
>
> grep -e "bugreporter-udeb.*udeb" < md5sum.txt
7e7842077197b6936ed6be2b500b2df3
./pool/main/b/bugreporter-udeb/bugreporter-udeb_0.28_all.udeb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subjec
Hello Osamu
attached are another round of tests, using
http://people.debian.org/~osamu/pub/sarge-i386-netinst-bug.iso,
md5 f01dbaea95c0d8627951ab788c56e3d3
The hardware is the same d600 and cpia laptops as my previous tests.
The cdrom drive detection succeeded.
It takes seems to take a looo
Package: installation
Severity: normal
Hello
I tried to install from the sarge install iso. It failed when
'anna' tries to grep the file /cdrom/dists/stable/Release.
This is because in the 'dists' directory on the cdrom, there is a
_file_ named 'stable', not a symlink to 'sarge'.
The 'sarge' direc
With the assistance of some local debian developers I made a few
further tests. This is also relevant to bugs 220529, 247704.
The three bugs should probably be merged.
I tested with Official netinst i386 of 20040528,
http://gluck.debian.org/cdimage/testing/sarge_d-i/i386/20040528/sarge-i386-netin
thanks for that careful analysis, Osamu.
I have very similar hardware and it appears the problem may also be
avoidable by configuring the kernel to not use DMA on cdroms.
See bugs #250323 (and referenced therein #222939.b)
Your solution is probably the least intrusive however.
If this patch is appl
Package: installation-reports
Version: testing daily 20040619
Severity: normal
Debian-installer-version: 20040619 testing netinst
http://cdimage.debian.org/pub/cdimage-testing/daily/sparc/20040619/sarge-sparc-netinst.iso
uname -a: kernel 2.4.26 I think
Date: 20040620
Method: netinst cdrom, note
Package: installation-reports
Version: beta3
Severity: normal
*** Please type your report below this line ***
I'm not sure this is necessary anymore but since I had much trouble with
installing woody on this h/w, I'd like to tell you how well sarge-beta3
did.
Debian-installer-version: sarge beta3
Package: installation-reports
Version: 20040410
Severity: normal
Debian-installer-version:
http://gluck.debian.org/cdimage/testing/sarge_d-i/sparc/current/sarge-sparc-netinst.iso
(2004-04-10) ( MD5=21e4902c4ece557fc192fe2e94fa3862 )
uname -a:
Date: 2004-04-11 15:00 (GMT+10)
Method: cdrom, extern
Package: installation-reports
Version: sparc 20040410
Severity: normal
Debian-installer-version:
http://gluck.debian.org/cdimage/testing/sarge_d-i/sparc/current/sarge-sparc-netinst.iso
(2004-04-10) ( MD5=21e4902c4ece557fc192fe2e94fa3862 )
uname -a:
Date: 2004-04-11 15:00 (GMT+10)
Method: cdrom
merge 242343 243122
quit
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Not quite sure about the wording, but a first try:
diff --git a/en/install-methods/install-tftp.xml
b/en/install-methods/install-tftp.xml
index 868c70155..7236fa836 100644
--- a/en/install-methods/install-tftp.xml
+++ b/en/install-methods/install-tftp.xml
@@ -178,7 +178,10 @@ For PXE booting, eve
Hello
I was trying to download the netboot image for amd64,
because the one I have (2018-12-06) has a segfault in libc6.
The link on the installer team page
https://www.debian.org/devel/debian-installer/
for the _netinst_ image points at
https://cdimage.debian.org/cdimage/buster_di_alpha4/amd
On Mon, Dec 17, 2018 at 01:18:59AM +, Steve McIntyre wrote:
> On Mon, Dec 17, 2018 at 11:00:25AM +1100, Vincent McIntyre wrote:
> >Hello
> >
> >I was trying to download the netboot image for amd64,
> >because the one I have (2018-12-06) has a segfault in libc6.
>
On Mon, Dec 17, 2018 at 02:29:27AM +0100, Cyril Brulebois wrote:
> Steve McIntyre (2018-12-17):
> > But... The problem you're most likely seeing is caused by a simple
> > fact. The *netboot* image ends up downloading significant chunks of
> > the installer and the base system at runtime from the s
On Wed, Aug 02, 2017 at 07:58:05PM +0100, Ben Hutchings wrote:
> On Wed, 2017-08-02 at 12:26 +1000, Vincent McIntyre wrote:
> > Package: hw-detect
> > Version: 1.124
> > Severity: normal
> > Tags: patch
> >
> > I keep seeing this in installer logs, back t
I can confirm this bug, on Dell Latitude CPiA 300, with netinst 20040907
from
http://cdimage.debian.org/pub/cdimage-testing/daily/i386/20040907/sarge-i386-netinst.iso
(md5:ea94232e95adc1e3bb8c51d71a4d941b)
This appears to be the same problem as 265612, 247704, 220529.
As before the cdrom is mount
> A minimal graphic environment task, which loads the x-window-system
> package, and maybe a few other stuff that are needed, would be a very
> welcome addition
thirded
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
package: cdrom-detect
severity: normal
I reported in #265636 that is was possible for cdrom-detect to
exit with status 0 but with the $suite variable (later used by
cdrom-retriever) unset.
Attached are two different attempts to detects that $suite is unset
and deal with this.
The first just caus
see also #271976
> I had to umount and remount cdrom. After that, it worked all right with
> netboot cd. Worked with two Dell Latitude CPi A400XT that I tried on.
>
...
> This should prob. be in installation manual.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscrib
Package: installation-reports
Debian-installer-version: Sarge netinst 20040921 i386
downloaded from
http://cdimage.debian.org/pub/cdimage-testing/daily/i386/20040921/sarge-i386-netinst.iso
uname -a:
Date: 20040924 03:00 GMT
Method: booted and installed from netinst cd. No network configured.
Package: installation-guide
Tags: patch
thanks
see also #760923.
Not sure this is quite correct for powerpc.
Index: manual/en/post-install/shutdown.xml
===
--- manual/en/post-install/shutdown.xml (revision 69984)
+++ manual/en/post
On Thu, Jun 25, 2015 at 05:51:02PM +0100, Justin B Rye wrote:
> Vincent McIntyre wrote:
> > Justin B Rye wrote:
> >> It's good, but I've got a couple of English usage nitpicks:
> >
> > And I'm happy to have you pick the nits off my contribution :)
&
On Sun, Mar 19, 2017 at 05:31:53PM +0100, Baptiste Jammet wrote:
Thanks for raising these important items.
...
> +ifname instead of mac address
> +
> +
> +The installer and the installed systems will now use ifnames by default
> +instead of mac for network interface names.
> +
> +
> +
Not havi
On Tue, Mar 21, 2017 at 09:45:24PM +0100, Baptiste Jammet wrote:
> Hi Vince,
>
> Dixit Vincent McIntyre, le 20/03/2017 :
>
> >> +ifname instead of mac address
> ...
> >Not having really worked with stretch yet (ie target audience member),
> >I'm had
I just realised this went to the libc maintainers;
I was expecting it would go to the debian-installer team.
This might be an issue in the way libc6-udeb is being used
within debian-installer, rather than libc6-udeb itself.
I don't know how to figure out if that is the case;
if it is the case, p
Hi,
For some years the disable_autoconfig preseed has been shown
in the appendix on preseeding. However setting that just sets
use_autoconfig appropriately. Yet use_autoconfig is not even
mentioned in the appendix, ever.
There might be something I'm missing here, such as disable_autoconfig
is the
Package: installation-guide
Severity: minor
Tags: d-i patch
thanks
(resending as a bug, my post to -boot didn't elicit any replies)
For some years the disable_autoconfig preseed has been shown
in the appendix on preseeding. However setting that just sets
use_autoconfig appropriately. Yet use_au
(we were discussing having a branch of manual for each stable release)
This appears to have happened - thanks Samuel!
https://anonscm.debian.org/viewvc/d-i/branches/manual/jessie/
I think it would be worth mentioning the existence of this
in the trunk README - suggested patch below. Please let m
Package: boot-floppies
Version: 3.0.22-2002-04-03
Arch: i386
host machine:
I am trying to install on a Digital Celebris GL5133, circa 1996.
BIOS is Phoenix 4.04, (1984-1995). Memory 64Mb. PentiumI processor.
Win98 currently installed, I am looking forward to blowing it away.
IDE controller is In
RedHat7.2 boot floppy (boot.img from std cdrom) fails in the same way
Loading vmlinuz...
Boot failed: please change disks and press a key to continue.
RedHat6.1 boot floppy succeeds, by loading an initial ram disk, before
loading vmlinuz.
I went back to the install manual, and read about ra
> > RedHat7.2 boot floppy (boot.img from std cdrom) fails in the same
way
> > Loading vmlinuz...
> ...
> > boot: ramdisk0 (also tried "linux ramdisk0")
> > Loading linux.bin...
> > Boot failed: please change disks and press a key to continue.
>
> Please try another floppy...
I
>
>
gah. The patch was not ok. My apologies for such a gross error.
I caught this by testing with 1.86 as downloaded from the archive.
[PATCH] Actually set bootdev.
After taking all the trouble to get the right value into
the $bootdev shell variable, ensure that we db_set
grub-installe
On Sun, Jun 09, 2013 at 01:47:36AM +0200, Cyril Brulebois wrote:
> Vincent McIntyre (30/04/2013):
> > gah. The patch was not ok. My apologies for such a gross error.
> > I caught this by testing with 1.86 as downloaded from the archive.
>
> Thanks, Vincent.
>
> Ap
On Sun, Jun 09, 2013 at 01:47:36AM +0200, Cyril Brulebois wrote:
> Vincent McIntyre (30/04/2013):
> > gah. The patch was not ok. My apologies for such a gross error.
> > I caught this by testing with 1.86 as downloaded from the archive.
>
> Thanks, Vincent.
>
> Ap
On Fri, Jul 28, 2017 at 12:28:58PM +1000, Vincent McIntyre wrote:
> the promised attachment, inline
A perusal of the syslog turned up this
A perusal of the syslog turned up this
Jul 28 01:27:32 grub-installer: info: Installing grub on '/dev/sdc'
Jul 28 01:27:32 grub-installe
the promised attachment, inline
uname -a: Linux testbox 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u2
(2017-06-26) x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Skylake Host
Bridge/DRAM Registers [8086:191f] (rev 07)
lspci -knn: Subsystem: Dell Device [1028:06b9]
l
We noticed this issue today and there is a further aspect to it.
I won't have time to make a proper bug report for a couple of days.
The initrd path that was given to the pxe netboot installer
gets included in the boot command line, to wit:
GRUB_CMDLINE_LINUX="initrd=::debian/stretch/amd64/de
Tags: patch
Thanks
Can this be fixed please? I wasted an hour tracking this down
while trying to resolve another issue.
--- lib/auto-lvm.sh.org 2017-08-02 10:24:35.773321165 +1000
+++ lib/auto-lvm.sh 2017-08-02 10:24:49.709392154 +1000
@@ -302,7 +302,7 @@
defvgname="$RET"
Package: hw-detect
Version: 1.124
Severity: normal
Tags: patch
I keep seeing this in installer logs, back to jessie.
Aug 2 01:52:11 main-menu[193]: (process:224): modprobe: invalid option -- 'l'
I rated this normal rather than minor because the way it is working
now the is_available() function
On Wed, Aug 02, 2017 at 07:58:05PM +0100, Ben Hutchings wrote:
>
> But this still prints error messages for missing modules. I think the
> function should be implemented as:
>
> is_available () {
> modprobe -qn "$1"
> }
>
I agreee, much better!
Package: lowmem
Version: 1.45
Severity: normal
Poking around an install environment I looked in /lib/main-menu.d
and found these files:
10rescue
5lowmem
Then I found the original commit message:
commit b9741a97a349f9ed4364b3411c3ab8afc590e385
Author: Joey Hess
Date: Fri May 6 01:3
A discussion with Steve suggested looking at when udev updates
/dev/disk/by-uuid - has something changed that stops that directory
being refreshed after partman-base is done (or at least before
bootstrap-base starts)?
I ran some stretch/jessie comparison installs on the following VM system:
amd
It would be good to make this change.
Is there some reason to not include a build stamp in the installer
initrd at, say, /build-stamp? This would be the same string as in
boot-screens/f1.txt (e.g. 20170615+deb9u2).
Regards
--
Below is a known-good partitioning recipe similar to your use case.
It puts all of /, not just /boot, in a real partition.
I think the main difference is the start of the second stanza
614401000 1 lvm
while you have
100 1000 -1 xfs
There may be a bug in handling -1 as the upper limi
see also #247704
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> > Can you please test a daily image from
> > http://gluck.debian.org/cdimage/testing/sarge_d-i/ to make sure there
> > are no regressions. This would be helpful since we're preparing for
> > rc1. If all of the issues you reported originally have been dealt
> > with, can you close this bug.
>
>
Package: installation-reports
Boot method: usb key
Image version: [1] lenny beta 1 boot.img.gz, plus [2] netinst .iso image
[1]
http://cdimage.debian.org/cdimage/lenny_di_beta1/i386/iso-cd/debian-testing-i386-netinst.iso
(md5: 23e8300f117a3d305b46a889ba71da83)
[2]
http://ftp.nl.debian.org/debi
Package: installation-reports
INSTALL REPORT
Debian-installer-version: lenny i386 hd-media daily 2008.07.21
(see comments for details)
uname -a: (does not boot)
Date: 2008.07.22
Method:
How did you install? Boot from USB key.
What did you boot off? USB key
If network install, from wher
I tried lenny beta 2, that booted successfully.
http://ftp.nl.debian.org/debian/dists/testing/main/installer-i386/current/images/hd-media/boot.img.gz
md5: 6d3bb654070a821de94774f89dd5d11d
http://cdimage.debian.org/cdimage/lenny_di_beta2/i386/iso-cd/debian-LennyBeta2-i386-netinst.iso
md5: 9dab64b
I tried 20080721 again, to be sure I hadn't muffed the usb install.
I redid the setup of the key, as described in the initial report,
double-checking I did not have the think mounted by usbmount or
whatever while I was zcatting to it.
Same result.
I see 'linux' and 'initrd.gz' all the
Vincent, have you made another Debian installation on the same system
since your original installation report (9 Mar 2007)? Did you
experencie a similar issue? If you have not, would you take the time to
boot a recent build of d-i (netboot mini.iso will do) and see if the
problem is still ther
addendum:
see also bug #439462
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=439462
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hi Jeremy
[ for some reason I did not get an email with your question, only the
bug did... Should I have gotten one if you sent mail just to the bug?
This may have been a transitory problem in our email system.
]
Is this also the last message you see when using "Expert Installation"?
Yes
Hi,
I was trying to make a recipe that differs only slightly from the
"multi_scheme" pre-cooked recipe, which has a real /boot and everything
else including swap in an LVM volume group.
The differences were that
* I want a separate, real "/" partition, with all the others in LVM.
* I don't want
package: debian-installer
Version: Debian GNU/Linux installer 4.0 (installer build 20070308etch2)
severity: minor
I was wondering how to set a label on a partition (not a partition
table, but a label that e2label could read).
I couldn't see this documented in [1] so I wrote a patch, attached.
I think this was fixed very recently, if you look back at the traffic
in http://lists.debian.org/debian-boot/2008/07
The installer should at least prompted you to supply a .fw firmware file.
Did it do this?
The firmware can be obtained from the firmware-* packages, e.g.
http://packages.debian.
package: debian-installer
severity: wishlist
Hi,
I was looking at packages/apt-setup/generators/and noticed a
difference between the way that 91security and 92volatile add lines
to the new sources.list file (subversion, r54582):
91security does this -
echo "deb http://$host/ $codename/updat
Package: installation-reports
INSTALL REPORT
Debian-installer-version: etch i386 netinst daily 2006.12.12
md5sum 135db969cce6d94c64adb9f42764581a
uname -a: Linux testhost 2.6.18-3-686 #1 SMP Mon Dec 4 16:41:14 UTC 2006 i686
GNU/Linux
Date: 2006.12.13
Method:
How did you install? netinst cd
Package: installation-guide
Hi,
in the installation guide, at
http://d-i.alioth.debian.org/manual/en.i386/ch06s03.html
there is a discussion of "Configuring Your Mail Transport Agent" that
no longer reflects the debian installer (at least as of rc1 or later).
In the d-i tree the text is at
retitle 402851 [i386][netinst][daily 20061212] Dell Optiplex 745 (mostly
successful)
thanks mate
it helps googlers if the machine model name is in the title...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Mon, 25 Dec 2006, Frans Pop wrote:
apologies for the late response...
I've written a new section explaining the default configuration and how to
configure exim4 after the installation. The new section is intended to be
included in chapter 8 which has some "post-installation" information.
A
Package: installation-reports
Boot method: CD, with the command 'install'
Image version: Netinst daily image
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso, version 20070211-2.iso
md5sum: 045f122cd20090fca10772c72f61ab57
Date: 2007-0
Hi,
I've had another swing at patching cdrom-detect to handle the case where
$suite never gets set.
This patch (v3) is a svn diff against svn://svn.debian.org/d-i/trunk.
After poring over the docs for some time I still am not sure how to
give user feedback, ie the correct use of db_subst, db_inpu
> It looks like all the issues are sorted out for the initrds, I plan to
> begin the final build shortly after archive sync tomorrow. I'm only
> waiting now for a few builds to be uploaded from the autobuilders and
> similar.
not sure this is relevant, but here goes -
I reported some failures-to-b
Package: installation-reports
INSTALL REPORT
Debian-installer-version:
http://cdimage.debian.org/pub/cdimage-testing/daily/i386/20040921/sarge-i386-netinst.iso
(md5sum 09697510e1123190e78e103fd61b413f)
uname -a:
Linux version 2.6.7-1-686 ([EMAIL PROTECTED]) (gcc version 3.3.4 (De
bian 1:3.3.4-2)
forwarding this as it appears the cc: from BTS didn't make it.
Bug#275428
-- Forwarded message --
Date: Fri, 8 Oct 2004 12:32:02 +1000 (EST)
From: Vincent McIntyre <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: [pre-rc2][netinst][i386] fa
Package: installation-reports
Severity: critical
INSTALL REPORT
Debian-installer-version:
netinst 20041007 from
http://cdimage.debian.org/pub/cdimage-testing/daily/sparc/20041007/sarge-sparc-netinst.iso
(md5sum b370379763a9e7efbe3439ab5c16113e )
% file sarge-sparc-netinst.iso
sarge-sparc
Package: installation-reports
INSTALL REPORT
Debian-installer-version:
netinst 20041007 from
http://cdimage.debian.org/pub/cdimage-testing/daily/sparc/20041007/sarge-sparc-netinst.iso
(md5sum b370379763a9e7efbe3439ab5c16113e )
uname -a: 2.4.27
Date: 20040 10 08
Method:
hit L1-A after open
Package: installation-reports
INSTALL REPORT
Debian-installer-version:
netinst 20041007 from
http://cdimage.debian.org/pub/cdimage-testing/daily/sparc/20041007/sarge-sparc-netinst.iso
(md5sum b370379763a9e7efbe3439ab5c16113e )
uname -a: 2.4.27
Date: 20040 10 08
Method:
hit L1-A after open
clarification: PROM version is OpenBoot 3.25, not 4.0
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: installation-reports
INSTALL REPORT
Debian-installer-version:
businesscard 20041009 from
http://cdimage.debian.org/pub/cdimage-testing/daily/sparc/20041009/sarge-sparc-businesscard.iso
(md5sum )
uname -a: 2.4.27
Date: 20040 10 10
Method:
hit L1-A after openboot banner appears
ty
I tried again with businesscard 20041009, (md5sum
0efb58b13d4f3179c48d996b60f9da3).
The same failure occurs, ie USB keyboard doesn't work at first screen of
installer (choose language).
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PR
Hi all,
I made some more (unsuccessful) attempts.
> Vincent, re. your "cramfs: wrong magic" intermittent problem:
> I have this problem on my Blade 100 as well, when I don't hit Stop+A
> at precisely the instant that the machine wants it. On my machine I
> have to send break after initializing m
forwarding for info
-- Forwarded message --
Date: Mon, 18 Oct 2004 09:25:07 +1000 (EST)
From: [EMAIL PROTECTED]
To: Colleen Hatfield <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED], Vincent McIntyre <[EMAIL PROTECTED]>,
Herbert Kaminski <[EMAIL PROTECTED]>,
yet more more (unsuccessful) attempts.
These were all done with the serial port connected, but that's all.
No monitor, no keyboard, no mouse.
1. JoshK mini-iso (20041015)
Power up.
Let solaris boot part way (I had the wrong baud rate set)
send
ok boot cdrom
system starts booting,
oops, forgot the logs...
logs.tar.gz
Description: Binary data
The failure I was experiencing was occuring because I had memory
in slots 3 and 4, and no memory in slots 1 and 2.
Moving the DIMMs into slots 1 and 2 avoids the
Kernel panic: VFS: Unable to mount root fs on 00:00
Press L1-A to return to the boot prom
error message.
I thought this problem
> > It turns out I needed to 'modprobe ata_piix' for the SATA to appear as a SCSI
> > device - I don't know if this is something the d-i team would like to bear in
> > mind as SATA becomes more common?
>
> Yeah, this is why the lspci output is important so that the bug may be
> assigned to discover
I finally made some more tests, with netinst 20041024
(http://cdimage.debian.org/pub/cdimage-testing/daily/sparc/20041024/sarge-sparc-netinst.iso)
Power up, boot into solaris.
Ran 'memconf' to discover the memory layout.
This showed:
U701, U601, U703, U603 had 64Mb DIMMs installed
U702, U60
> Please try the netinst iso image in http://people.debian.org/~blarson/
> and let me know if that works or not.
Thanks for supplying the image. I downloaded it and tried it.
(I get an md5 sum of 0e883183c42ecf4266043516fe513ede )
We're not quite there yet.
Stop-A during "boot disk" phase
ok
I think this is bug #267168
see also #271976
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=267168
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=271976
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> The AMD64 install had another major obstacle, the installer did not find the
> release file. It was looking in (typing from memory) debian/dists//Release,
> which does not exist on the CD. I think the double slash is a clue, the
> distribution (sarge, sid, whatever) is missing here. I didn't want
Some additional info about these raid controllers, copied from
http://mlug.missouri.edu/pipermail/members/2004-September/006213.html
Discussion:
Some of the new Dell PowerEdge servers use Dell's PERC4ei (alternate
spellings for search: PERC 4/ei, PERC4/ei, PERC4 EI, PERC 4ei) RAID
controller, w
> The problem is not that the controller is not supported, but rather that
> it is not yet recognized by the installer.
> See: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=278203
oh? When I tried this it looked like there was no support from upstream
for SATA (ata_piix) and I couldn't see that
> This installation was with the IDE compatibility mode enable :
> - The autodetection of the CDROM didn't work. Going in exprt mode and not
> loading ata_piix solved this but..
> - I then wasn't able to have the hard drive detected
>
> I tried a bunch of module loading/unloading but I couldn't h
This report can be closed!
The installer now supports this hardware. The only trick to installation
is to power cycle immediately before booting off the cdrom.
Full report below.
Package: installation-reports
INSTALL REPORT
Debian-installer-version: netinst 20041015, from
http://cdimage.debia
I tested this hardware again, with i386 netinst 20041110.
Now the megaraid2 module is loaded correctly, yay.
The partitioner starts normally, detecting a 73GB RAID-0 partition.
Hence, I'm closing this report.
Thanks all
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "un
>
> After selecting language etc. the installer quits with message stating wrong
> cd or can't read from cd. This is an ongoing problem inherent to previous
> installer cd's. I've tried them all. Going to a shell prompt, the cd is
> mounted.
> This is not a cd read/write problem. Multible cd's
> We have many IBM blades (HS20). They have TG3 cards in them. This seems
> to fail on newer Debian Installer images (rc1, rc2). lspci says:
>
> :01:00.0 Ethernet controller: Broadcom Corporation NetXtreme
> BCM5704S Gigabit Ethernet (rev 02)
> :01:00.1 Ethernet controller: Broadcom Corpora
> The kernel seems to load correctly, but when I get to the first
> installation screen "Please choose your language" the keyboard is
> completely frozen. The keyboard connected to the machine is the default
> SUN usb keyboard. I notice during the kernel boot that the usbkbd module
> is loaded.
>
>
forwarding for info.
283666 and 275627 should probably merge
-- Forwarded message --
Date: Wed, 01 Dec 2004 12:32:02 +0100
From: Daniel Robinson <[EMAIL PROTECTED]>
To: Vincent McIntyre <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: Re: Bug#283666: Package:
1 - 100 of 167 matches
Mail list logo
