Bug#405250: marked as done (SPARC32 floppy install - issues switching between floppies)
Your message dated Sat, 22 Jan 2011 18:21:14 + with message-id <1295720474.2505.233.camel@eeepc.Belkin> and subject line has caused the Debian Bug report #405250, regarding SPARC32 floppy install - issues switching between floppies to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 405250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=405250 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Boot method: floppy Image version: http://people.debian.org/~stappers/d-i/images/daily/sparc32/floppy/2.6/boot.img Date: 20061219 Machine: Sun SparcStation 5 Processor: 70Mhz Memory: 80MB Partitions: Output of lspci -nn and lspci -vnn: none Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [E] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: There are some oddities when performing a floppy install of the "testing" version of Debian: After booting the system from floppy, it will not automatically eject the boot floppy when prompting for the root floppy. The install process does later automatically eject the root floppy at the point where it asks if you have a floppy disk containing drivers needed for the install. When you manually switch the boot floppy for the root floppy, it takes exactly four keypresses of the ENTER key before the system takes any action with the root floppy. After hitting the ENTER key on the QWERTY part of a Sun5c keyboard four times, the system behaves normally, and you see a message that the system has found the root image. This is on a SparcStation 20 w/CG6 framebuffer and Sun5c keyboard/mouse, as well as a SparcStation 5 (170Mhz) and SparcStation 5 (70Mhz) using the same keyboard and mouse between all three systems. I've also seen the same behaviour switching floppys during an install where I was using a serial console instead of a real monitor/keyboard/mouse. It took four ENTERs to get from the boot to the root floppy on an x86 Linux workstation running Minicom in VT102 emulation and ANSI emulation. At this point in time, these are the only issues I've seen performing a successful floppy based install of the SPARC32 version of Debian "testing" on a Sun SparcStation 20, a Sun SparcStation 5 (170Mhz processor), and a Sun SparcStation 5 (70Mhz processor). --Dan __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --- End Message --- --- Begin Message --- Floppies are no longer supported in the installer. Hence, i am closing this BR. -- Melhores cumprimentos/Best regards, Miguel Figueiredo http://www.DebianPT.org --- End Message ---
Bug#405177: marked as done (install-report: no reboot after FLOPPY install)
Your message dated Wed, 08 Sep 2010 03:58:23 + with message-id and subject line Closing old installation report #405177 has caused the Debian Bug report #405177, regarding install-report: no reboot after FLOPPY install to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 405177: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=405177 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Boot method: Floppy Image version: Downloaded September 2006 Date: 1. January 2007 Machine: Compaq Pressario 701ea Processor: AMD Duron 950 Mhz Memory: 192 mb Partitions: Standart Desktop Partitions ( /, Swap, /home ) Output of lspci and lspci -n: ?? Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[First Error in downloading Packages, Than OK!] Install boot loader:[O] Reboot: [E] Comments/Problems: Don't know why it doesn't boot, but I'll try another Kernel ( I tried 2.6-k7.. ) ___ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de --- End Message --- --- Begin Message --- We are closing this installation report for one of the following reasons: - it was reported with a pre-lenny version of Debian Installer. - indications in the installation report give the feeling that the reported problem waslying in another software, unrelated to D-I, which we can't easily identify. - indications in the installation report suggest that it may have been fixed in a more recent version of a D-I component - it was successful and we forgot closing it..:-) - it has no information we consider useful The D-I team is currently in the process of cleaning out the old spool of installation reports that haven't bene processed yet. In case you think that the problem you reported has chances to be still present, please reiterate your installation test with a more recent image of D-I, if you're in position of doing this. You'll find daily builds at http://www.debian.org/devel/debian-installer. We recommend you choose the netboot image, in the "daily builds section", then choose to install "squeeze" when prompted. If some problems are found, please report them with a new bug sent against installation-reports. Many thanks for your understanding and your help improving Debian, past and present. --- End Message ---
Bug#357704: marked as done (Floppy install does not configure boot dir and grub correctly)
Your message dated Wed, 08 Sep 2010 03:58:11 + with message-id and subject line Closing old installation report #357704 has caused the Debian Bug report #357704, regarding Floppy install does not configure boot dir and grub correctly to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 357704: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=357704 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports -> -> If you don't mind, please don't put my e-mail address on the web. -> Boot method: Floppy. 4 x 1.44 mb Image version: 17-Mar-2006 from http://people.debian.org/~joeyh/d-i/images/daily/floppy/access. Date: 18-Mar-2006, around 6:00 EST Machine: Spare parts, mobo about 3-4 years old. Fairly modern. Runs GNU/Debian well. Processor: AMD K7 Memory: 1GB Partitions: FilesystemType 1K-blocks Used Available Use% Mounted on [#/dev/hda1 ntfs (not mounted)] [#/dev/hda2 swap] /dev/hda3 reiserfs16602624 8456792 8145832 51% / [#/dev/hda4 reiserfs (*** not mounted, but see below)] tmpfstmpfs 518412 0518412 0% /dev/shm tmpfstmpfs 518412 100518312 1% /dev Output of lspci and lspci -n: :00:00.0 Host bridge: Silicon Integrated Systems [SiS] 741/741GX/M741 Host (rev 03) :00:01.0 PCI bridge: Silicon Integrated Systems [SiS] SiS AGP Port (virtual PCI-to-PCI bridge) :00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS964 [MuTIOL Media IO] (rev 36) :00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev 01) :00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) :00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) :00:03.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) :00:03.3 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller :00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 91) :00:0a.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 0a) :00:0a.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 0a) :00:0b.0 VGA compatible controller: ATI Technologies Inc Rage 128 Pro Ultra TR :01:00.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200] (rev 01) :01:00.1 Display controller: ATI Technologies Inc RV280 [Radeon 9200] (Secondary) (rev 01) :00:00.0 0600: 1039:0741 (rev 03) :00:01.0 0604: 1039:0003 :00:02.0 0601: 1039:0964 (rev 36) :00:02.5 0101: 1039:5513 (rev 01) :00:03.0 0c03: 1039:7001 (rev 0f) :00:03.1 0c03: 1039:7001 (rev 0f) :00:03.2 0c03: 1039:7001 (rev 0f) :00:03.3 0c03: 1039:7002 :00:04.0 0200: 1039:0900 (rev 91) :00:0a.0 0401: 1102:0002 (rev 0a) :00:0a.1 0980: 1102:7002 (rev 0a) :00:0b.0 0300: 1002:5452 :01:00.0 0300: 1002:5961 (rev 01) :01:00.1 0380: 1002:5941 (rev 01) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [ ] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] *** but see below Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[E] Reboot: [E] Comments/Problems: The install went perfectly (but I do miss full-screen ncurses-style menus). I booted boot.img in expert mode, mounted root.img, loaded net-drivers.img for the SiS900, configured static IP, then downloaded the rest from a mirror without a problem. I chose Standard System and Desktop/Workstation for software. However, while the app software was installed to the correct partition (hda4), the OS was not installed, and grub did not add hda4 as a menu choice. Background: I have 1 hardisk, hda, with 4 partitions: hda1 ntfs for Windows, should I need to do something with that thing. hda2 linux paging hda3 reiserfs for my normal GNU/Debian boot device and root (been working fine with 'testing' for a long time) hda4 an empty partition on which I was trying to install afresh the lastest GNU/Debian Prior to this install, grub would offer hda1 (Windows) and hda3 (2.6.15) as boot choices from the MBR. My goal was to keep hda1 and hda3 intact, and try a fresh install on hda4, with safe fallback to hda3 or even hda1 (ugh!). After the install, I expected grub to offer hda1, hda3, and also hda4 (t
Bug#303812: marked as done (sarge floppy install report)
Your message dated Wed, 08 Sep 2010 03:57:57 +
with message-id
and subject line Closing old installation report #303812
has caused the Debian Bug report #303812,
regarding sarge floppy install report
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
303812: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=303812
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Debian-installer-version:
not recorded. floppy images downloaded March 29 2005
uname -a:
linux 2.4.27-2-686 #1 Thu Jan 20 11:10:41 JST 2005 i686 GNU/Linux
Date: week of April 4 2005
Method: floppies
Machine: IBM Thinkpad 770x
Processor: 300 MHz pentium II
Memory: 128 Megabytes
Root Device: IDE /dev/hda2
/dev/hd1 is windows 2000 fat32.
Root Size/partition table: only one linux partion, 15G, plus swap
Output of lspci :
:00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge
(rev 02)
:00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge
(rev 02)
:00:02.0 CardBus bridge: Texas Instruments PCI1251A
:00:02.1 CardBus bridge: Texas Instruments PCI1251A
:00:06.0 Multimedia audio controller: Cirrus Logic CS 4610/11
[CrystalClear SoundFusion Audio Accelerator] (rev 01)
:00:07.0 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02)
:00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)
:00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01)
:00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 02)
:01:00.0 VGA compatible controller: Trident Microsystems
Cyber 9397DVD (rev f3)
:05:00.0 Ethernet controller: 3Com Corporation 3c575
Megahertz 10/100 LAN CardBus [Boomerang]
and lspci -n:
:00:00.0 0600: 8086:7190 (rev 02)
:00:01.0 0604: 8086:7191 (rev 02)
:00:02.0 0607: 104c:ac1d
:00:02.1 0607: 104c:ac1d
:00:06.0 0401: 1013:6001 (rev 01)
:00:07.0 0680: 8086:7110 (rev 02)
:00:07.1 0101: 8086:7111 (rev 01)
:00:07.2 0c03: 8086:7112 (rev 01)
:00:07.3 0680: 8086:7113 (rev 02)
:01:00.0 0300: 1023:939a (rev f3)
:05:00.0 0200: 10b7:5057
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot worked:[O ]
Configure network HW: [O ]
Config network: [O ]
Detect CD: [ ]
Load installer modules: [O ]
Detect hard drives: [O ]
Partition hard drives: [O ]
Create file systems:[O ]
Mount partitions: [O ]
Install base system:[O ]
Install boot loader:[O ]
Reboot: [O ]
Comments/Problems:
I installed using a 3Com pcmcia wired ethernet card. The first
stage install went fine. The reboot went fine except the
network connection failed. ('does not seem to be currently
connected'). I was then offered ppp as an option, but not dhcp.
That is the install floppies found the network but the
installed system did not.
I switched to tty2 and only had to run dhclient to make the connection
succeed. I switched back to tty1 and, after backing out a few
steps, the installation continued and completed OK.
I then deleted the linux partitions and started the floppy install
a second time. The same thing happened. I did it yet again with the
same result.
I think I remember being asked whether the computer would have a
permanent internet connection or not, on the first time through,
but was not asked that on either of the subsequent two installs.
If I _was_ asked that, I don't remember how I answered.
This would be very discouraging for someone of little experience:
('It found the network when I used the floppies. Why doesn't it
find it now?').
Could there be a dhcp offer at the same place where there is a ppp
offer? Or record the method that worked at the first stage and
transmit that to the intalled system?
Charles Kaufman
ch...@uri.edu
--- End Message ---
--- Begin Message ---
We are closing this installation report for one of the following
reasons:
- it was reported with a pre-lenny version of Debian
Installer.
- indications in the installation report give the feeling that
the reported problem waslying in another software, unrelated to
D-I, which we can't easily identify.
- indications in the installation report suggest that it may have been
fixed in a more recent version of a D-I component
- it was successful and we forgot closing it..:-)
- it has no information we consider useful
The D-I team is currently in the process of cleaning out th
Bug#272310: marked as done (Floppy install on Oldworld PowerMac G3 tower)
Your message dated Wed, 08 Sep 2010 03:57:39 + with message-id and subject line Closing old installation report #272310 has caused the Debian Bug report #272310, regarding Floppy install on Oldworld PowerMac G3 tower to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 272310: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=272310 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports I tried the PowerMac install floppy set from the 18th Index of /~luther/d-i/images/2004-09-18/powerpc/floppy-2.4 NameLast modified Size Description [DIR] Parent Directory26-Aug-2004 21:35 - [ ] asian-root.img 18-Sep-2004 01:35 1.1M [ ] boot.img18-Sep-2004 01:35 1.4M [ ] cd-drivers.img 18-Sep-2004 01:35 1.4M [ ] net-drivers.img 18-Sep-2004 01:35 1.4M [ ] ofonlyboot.img 18-Sep-2004 01:35 1.4M [ ] root-2.img 18-Sep-2004 01:35 1.4M [ ] root.img18-Sep-2004 01:37 1.2M _ Apache/1.3.26 Server at people.debian.org Port 80 The boot floppy reads OK and calls for the root floppy, which also reads OK. It asks for Language (I gave it English), then the screen started blinking. Switching to the other consoles (opt-F2, -F3, -F4), which are also blinking, so it's hard to get any details, it appears that the /sbin/debian-installer process is crashing and restarting repeatedly. Enjoy! Rick --- End Message --- --- Begin Message --- We are closing this installation report for one of the following reasons: - it was reported with a pre-lenny version of Debian Installer. - indications in the installation report give the feeling that the reported problem waslying in another software, unrelated to D-I, which we can't easily identify. - indications in the installation report suggest that it may have been fixed in a more recent version of a D-I component - it was successful and we forgot closing it..:-) - it has no information we consider useful The D-I team is currently in the process of cleaning out the old spool of installation reports that haven't bene processed yet. In case you think that the problem you reported has chances to be still present, please reiterate your installation test with a more recent image of D-I, if you're in position of doing this. You'll find daily builds at http://www.debian.org/devel/debian-installer. We recommend you choose the netboot image, in the "daily builds section", then choose to install "squeeze" when prompted. If some problems are found, please report them with a new bug sent against installation-reports. Many thanks for your understanding and your help improving Debian, past and present. --- End Message ---
Bug#270599: marked as done (Floppy install on Oldworld PowerMac)
Your message dated Wed, 08 Sep 2010 03:57:37 + with message-id and subject line Closing old installation report #270599 has caused the Debian Bug report #270599, regarding Floppy install on Oldworld PowerMac to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 270599: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=270599 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports powerpc boot-floppy 20040906 OldWorld PowerMac INSTALL REPORT Debian-installer-version: I got the floppy disk images from: Index of /~luther/d-i/images/daily/powerpc/floppy-2.4 NameLast modified Size Description Parent Directory26-Aug-2004 21:35 - asian-root.img 06-Sep-2004 22:38 1.2M boot.img06-Sep-2004 22:38 1.4M cd-drivers.img 06-Sep-2004 22:39 1.4M net-drivers.img 06-Sep-2004 22:39 1.4M ofonlyboot.img 06-Sep-2004 22:39 1.4M root-2.img 06-Sep-2004 22:41 1.4M root.img06-Sep-2004 22:42 1.3M Apache/1.3.26 Server at people.debian.org Port 80 uname -a: Linux debian 2.6.7-powerpc #1 Thu Aug 5 23:48:59 CEST 2004 ppc GNU/Linux Date: 4 AM (UTC) 2004-09-07 Method: How did you install? boot/root/driver floppies with an assist from the uchicago mirror What did you boot off? boot floppy If network install, from where? debian.uchicago.edu Proxied? No Machine: PowerMac G3/300 MHz Processor: processor : 0 cpu : 740/750 temperature : 36-41 C (uncalibrated) clock : 300MHz revision: 2.2 (pvr 0008 0202) bogomips: 601.29 machine : Power Macintosh motherboard : AAPL,Gossamer MacRISC detected as : 48 (PowerMac G3 (Gossamer)) pmac flags : L2 cache: 1024K unified pipelined-syncro-burst memory : 384MB pmac-generation : OldWorld Memory: 384 MB Root Device: Didn't get that far Root Size/partition table: Feel free to paste the full partition table, with notes on which partitions are mounted where. Output of lspci and lspci -n: :00:00.0 Host bridge: Motorola MPC106 [Grackle] (rev 40) :00:0d.0 Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 10) :00:0e.0 SCSI storage controller: Artop Electronic Corp ATP865 (rev 06) :00:0f.0 PCI bridge: Hint Corp HB6 Universal PCI-PCI bridge (non-transparent mode) (rev 13) :00:10.0 ff00: Apple Computer Inc. Heathrow Mac I/O (rev 01) :00:12.0 VGA compatible controller: ATI Technologies Inc 3D Rage I/II 215GT [Mach64 GT] (rev 9a) :01:08.0 USB Controller: NEC Corporation USB (rev 41) :01:08.1 USB Controller: NEC Corporation USB (rev 41) :01:08.2 USB Controller: NEC Corporation USB 2.0 (rev 02) :01:0b.0 FireWire (IEEE 1394): Texas Instruments TSB12LV26 IEEE-1394 Controller (Link) :00:00.0 0600: 1057:0002 (rev 40) :00:0d.0 0200: 1186:1300 (rev 10) :00:0e.0 0100: 1191:0009 (rev 06) :00:0f.0 0604: 3388:0021 (rev 13) :00:10.0 ff00: 106b:0010 (rev 01) :00:12.0 0300: 1002:4754 (rev 9a) :01:08.0 0c03: 1033:0035 (rev 41) :01:08.1 0c03: 1033:0035 (rev 41) :01:08.2 0c03: 1033:00e0 (rev 02) :01:0b.0 0c00: 104c:8020 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[?] Note 1 Configure network HW: [o] Config network: [o] Detect CD: [ ] Load installer modules: [o] Detect hard drives: [e] Note 2 Partition hard drives: [?] Create file systems:[ ] Mount partitions: [ ] Install base system:[ ] Install boot loader:[ ] Reboot: [ ] Comments/Problems: Note 1: The "ofonlyboot" floppy booted and gave me the "tuxmac" icon in the middle of the screen. After the floppy noises stopped, the screen inverted colors, but did not switch to text mode. The ofonly boot floppy ejected. Normally, at this point it's calling for the root floppy, so I gave it the root floppy and hit . As expected, it read the root floppy, but the text screen never appeared -- just the inverted
Bug#380585: marked as done (d-i: floppy install fails for USB keyboards)
Your message dated Tue, 7 Sep 2010 20:39:53 +0200 (CEST) with message-id <20100907183953.8fb1623b8...@mykerinos.kheops.frmug.org> and subject line Closing old installation reports has caused the Debian Bug report #380585, regarding d-i: floppy install fails for USB keyboards to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 380585: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=380585 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: debian install FD version: 3.1 I can not complete install from FD. I'm using USB keybord. After initrd.gz is read, Insmod error "hid.o" is displayed. Ten USB keyboard halts. Tere is not "hid.o" in "initrd.gz" in boot FD. _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ 愛媛新聞エリアサービス北条東 清水宏之 as_ho...@hotmail.com _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ --- End Message --- --- Begin Message --- We are closing this installation report for one of the following reasons: - it was reported with a pre-lenny version of Debian Installer. - indications in the installation report give the feeling that the reported problem waslying in another software, unrelated to D-I, which we can't easily identify. - indications in the installation report suggest that it may have been fixed in a more recent version of a D-I component - it was successful and we forgot closing it..:-) - it has no information we consider useful The D-I team is currently in the process of cleaning out the old spool of installation reports that haven't bene processed yet. In case you think that the problem you reported has chances to be still present, please reiterate your installation test with a more recent image of D-I, if you're in position of doing this. You'll find daily builds at http://www.debian.org/devel/debian-installer. We recommend you choose the netboot image, in the "daily builds section", then choose to install "squeeze" when prompted. If some problems are found, please report them with a new bug sent against installation-reports. Many thanks for your understanding and your help improving Debian, past and present. --- End Message ---
RFR: documentation about floppy install (Was: Re: floppy install)
Hello all, Philip Hands wrote: > James, if you try that, perhaps you could write-up any issues you bump > into, so that we could still offer a floppy install method, even if we > no longer try to cram the latest installer onto a floppy. I'm thinking of an addition to the d-i manual to document such installation (etch release) via floppy followed by dist-upgrades to actual stable release. I want to request a rough review of the attached patch, which is only a first proposal, with several unclear paragraphs (marked with FIXME), that I need to check further. My intention of this mail: is there some interest to include something like this into the d-i manual? Frans? If not, I wouldn't waste any more time on this. Holger -- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Created with Sylpheed 2.5.0 under DEBIAN GNU/LINUX 5.0.0 - L e n n y Registered LinuxUser #311290 - http://counter.li.org/ = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Index: w-c/build/entities/urls.ent === --- w-c/build/entities/urls.ent (Revision 64161) +++ w-c/build/entities/urls.ent (Arbeitskopie) @@ -319,6 +319,12 @@ http://oss.software.ibm.com/developerworks/opensource/linux390/index.shtml";> +http://archive.debian.org/debian/dists/etch/main/installer-i386/current/images/floppy";> + +http://cdimage.debian.org/cdimage/archive/4.0_r9/i386/iso-cd/";> + + + + + Installing from floppy disc + + + +Although installing &debian; &release; from floppy is not directly +supported (since the kernel and initrd don't fit on a floppy disc +anymore), we want to show a way to install &debian; &release; on machines, +that can only boot from floppy anyway. + + + +Requirement for this is at least a system, that can boot from floppy +disc and a way to provide an installation cdrom image. One possibility +for the latter is a cdrom drive, internal or external via usb for example, +another one is an usb mass storage device FIXME. +Via this way a pure base Etch system will be installed. No additional +packages are to be installed at this step, this can be done later in +the process. In this later step you will also need an internet connection. + + + +So, download the images: you need boot.img, +root.img and cd-drivers.img +from and +debian-40r9-i386-netinst.iso from +. +Write the floppy images to floppies as described in section FIXME. +The netinst.iso cdrom image needs to be burned to a cdrom, if you +want to use a cdrom drive for that image, or you have to store it on +an usb stick or the like FIXME. + + + + + Installing the Etch base system + + + +Boot your system from floppy now, choose the default install option (or +use expert if you want full control about the process) and insert the root +disc when the system asks for it. Then go through the steps as usual +(you can get more info about the normal installation process in +). +When asked for a driver floppy FIXME, insert the cd-driver floppy. +If you have burned the netinst.iso image to a cdrom, put it into the drive +and the system will detect the image automatically. +If you wrote the image to an usb mass storage device, plug it in and mount +the partition manually via virtual console (Alt +F2) FIXME. +You will reach the step to load additional installer components from the +cdrom (image). Choose that ones from which you think you will need them. + + + +From here on you can follow the normal installation procedure as described +in . When you come to the step for selecting +additional software to be installed, you should mark "Standard system" +FIXME for installation, nothing else. + + + + + Upgrading to lenny + + + +Now that you have completed the installation of Debian Etch, you will have +to prepare your system to get upgraded to Lenny via internet. At this time it +is not supported to use a dialup connection via normal phone line, +ISDN, DSL or the like. The supported way is to use an ethernet connection and +let another pc or your internet router care about connecting to the internet. +For this, a network connection has to be configured: we will assume, that you +have a working network interface on your system, let's say /dev/eth0 FIXME. +Maybe your network interface is already correctly configured, in this case +you can skip the next paragraph and go directly to editing /etc/apt/sources.list. + + + +Otherwise you will have to edit some configuration files for your network settings +now: the first one is /etc/network/interfaces. If you want to use DHCP to get your +network settings allocated from a server (i.e. from your internet router), add the +following lines to /etc/network/interfaces (substitute +eth0 with the notation of your interface, if yours is +not eth0): + + +auto eth0 +iface eth0 inet dhcp + + +If you want to use static network settings, use this lines (edit the lines
Re: floppy install - unable to find root filesystem, ide_generic not loaded
Hi, Holger Wansing wrote: > Philip Hands wrote: > > Do you happen to know the name of the module that was providing ide > > support before the kernel upgrade was? > > Don't know, but I will start the whole floppy installation again, then I > will see. I have installed the system from scatch. A pure 4.0 aka etch system is now running on that machine. The only ide related modules are actually: ide_core ide_generic ide_disc Holger -- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Created with Sylpheed 2.5.0 under DEBIAN GNU/LINUX 5.0.0 - L e n n y Registered LinuxUser #311290 - http://counter.li.org/ = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100724231738.dd3f0f11.li...@wansing-online.de
Re: floppy install - unable to find root filesystem, ide_generic not loaded
Hi, Philip Hands wrote: > Do you happen to know the name of the module that was providing ide > support before the kernel upgrade was? Don't know, but I will start the whole floppy installation again, then I will see. > saying that it's no longer directly supported, but you can do it by > following the instructions in e.g. Appendix X: Floppy Installs > if you think that's an appropriate place. > > You can submit what you write as a bug/patch against the package > installation-guide Yes, I planned to add an additional appendix to the installation guide. But I will ask Frans Pop for his opinion, before I start the work, as he is somewhat responsible for the manual IIRC. Holger -- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Created with Sylpheed 2.5.0 under DEBIAN GNU/LINUX 5.0.0 - L e n n y Registered LinuxUser #311290 - http://counter.li.org/ = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100723223740.021eae49.li...@wansing-online.de
Re: floppy install - unable to find root filesystem, ide_generic not loaded
On Thu, 22 Jul 2010 20:17:56 +0200, Holger Wansing wrote: > Hi, > > Philip Hands wrote: > > It seems like the initramfs hasn't picked up on the fact that that > > module is needed. This should be fixable by doing: > > > > echo ide_generic >> /etc/initramfs-tools/modules > > update-initramfs > > > > You may find that once booted with the module loaded, update-initramfs > > can work out that that module is needed, and that it doesn't need to be > > explicitly listed in the /etc/initramfs-tools/modules file, but the > > problem presumably comes from the fact that ide_generic was not needed > > in the earlier kernel, or that it was loading a specific chipset's > > module in the etch kernel, and that module's name has changed rendering > > it unavailable for the new kernel. > > Yes, I have fixed the system that way, but my real intention was, > to avoid that this problem occures again in the future. > Thus asking what package is responsible for this. Since that fix works, it seems to me that the fault lies somewhere in the linux-image or initramfs-tools packages -- one or other of them should realise that if we're currently relying on ide_oldname, that means that we need to ensure that either ide_generic or ide_newname get added to the list of modules that get built into the new kernel's initrd. Do you happen to know the name of the module that was providing ide support before the kernel upgrade was? > But maybe this is not really important for the docu I want to write for > that floppy installation process. It really ought to be covered here: http://www.debian.org/releases/stable/i386/release-notes/ch-upgrading.en.html#boot-hangs but I get the impression that your problem is not helped by these suggestions, so perhaps you should write a subsection that would have helped, and submit it as a bug report against the manual -- see: http://www.debian.org/releases/stable/i386/release-notes/ch-about.en.html#bug-reports Once that's fixed, you'd be able to refer to that manual in your floppy install notes. Actually, if you're writing a floppy install section, it's probably best to submit it as a bug against the install guide, so that it gets incorporated permanently. There should at least be a reference to it in this bit: http://www.debian.org/releases/stable/i386/ch02s04.html.en and perhaps here: http://www.debian.org/releases/stable/i386/apas02.html.en saying that it's no longer directly supported, but you can do it by following the instructions in e.g. Appendix X: Floppy Installs if you think that's an appropriate place. You can submit what you write as a bug/patch against the package installation-guide Cheers, Phil. -- |)| Philip Hands [+44 (0)20 8530 9560]http://www.hands.com/ |-| HANDS.COM Ltd.http://www.uk.debian.org/ |(| 10 Onslow Gardens, South Woodford, London E18 1NE ENGLAND pgpT6KRsp3OEJ.pgp Description: PGP signature
Re: floppy install - unable to find root filesystem, ide_generic not loaded
Hi, Philip Hands wrote: > It seems like the initramfs hasn't picked up on the fact that that > module is needed. This should be fixable by doing: > > echo ide_generic >> /etc/initramfs-tools/modules > update-initramfs > > You may find that once booted with the module loaded, update-initramfs > can work out that that module is needed, and that it doesn't need to be > explicitly listed in the /etc/initramfs-tools/modules file, but the > problem presumably comes from the fact that ide_generic was not needed > in the earlier kernel, or that it was loading a specific chipset's > module in the etch kernel, and that module's name has changed rendering > it unavailable for the new kernel. Yes, I have fixed the system that way, but my real intention was, to avoid that this problem occures again in the future. Thus asking what package is responsible for this. But maybe this is not really important for the docu I want to write for that floppy installation process. Thanks Holger -- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Created with Sylpheed 2.5.0 under DEBIAN GNU/LINUX 5.0.0 - L e n n y Registered LinuxUser #311290 - http://counter.li.org/ = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100722201756.c98ba2b6.li...@wansing-online.de
Re: floppy install - unable to find root filesystem, ide_generic not loaded
On Sat, 17 Jul 2010 14:28:50 +0200, Holger Wansing wrote: ... > Doing "modprobe ide_generic" makes the harddisk available, and > closing the shell with exit let's the system boot continue fine. > > Can anyone tell me, why this happens? > Should I file a bugreport? Against which package? Hi, It seems like the initramfs hasn't picked up on the fact that that module is needed. This should be fixable by doing: echo ide_generic >> /etc/initramfs-tools/modules update-initramfs You may find that once booted with the module loaded, update-initramfs can work out that that module is needed, and that it doesn't need to be explicitly listed in the /etc/initramfs-tools/modules file, but the problem presumably comes from the fact that ide_generic was not needed in the earlier kernel, or that it was loading a specific chipset's module in the etch kernel, and that module's name has changed rendering it unavailable for the new kernel. Cheers, Phil. -- |)| Philip Hands [+44 (0)20 8530 9560]http://www.hands.com/ |-| HANDS.COM Ltd.http://www.uk.debian.org/ |(| 10 Onslow Gardens, South Woodford, London E18 1NE ENGLAND pgpah8uTp9ptM.pgp Description: PGP signature
Re: floppy install - unable to find root filesystem, ide_generic not loaded
Hi, Philip Hands wrote:. > > BTW, is there any reason why not install Etch from floppy instead of > > Sarge? > > No, none -- I thought I'd checked that. Actually, I think what actually > happened is that I found the sarge link first, checked for etch, found > it and then must have pasted the wrong one into the email -- Doh! > > Sorry for any wasted time. Installing from Etch floppies would be much > more sensible. So, I made a new try with installing Etch and then upgrading to Lenny. The first step, installing Etch worked fine, booting from Etch floppies and the installing from a Etch netinst cd. Then I upgraded to Lenny, according to the Lenny release notes in three steps: apt-get install apt aptitude aptitude safe-upgrade aptitude dist-upgrade No problems so far, upgrade completed without errrors or any glitches, but the new kernel was unable to boot (more exactly spoken: cannot find the root filesystem). It's an 2.6.26 kernel from debian linux image package (linux-image-2.6.26-486). System boot hangs at "Waiting for root filesystem ..." and then the debug shell comes up. The problem is: there are no ide related modules loaded, only some ACPI modules are loaded. Doing "modprobe ide_generic" makes the harddisk available, and closing the shell with exit let's the system boot continue fine. Can anyone tell me, why this happens? Should I file a bugreport? Against which package? Holger -- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Created with Sylpheed 2.5.0 under DEBIAN GNU/LINUX 5.0.0 - L e n n y Registered LinuxUser #311290 - http://counter.li.org/ = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100717142850.5b6ed249.li...@wansing-online.de
Re: floppy install
On Sun, 11 Jul 2010 22:09:14 +0200, Holger Wansing wrote: > Hi, ... > BTW, is there any reason why not install Etch from floppy instead of > Sarge? No, none -- I thought I'd checked that. Actually, I think what actually happened is that I found the sarge link first, checked for etch, found it and then must have pasted the wrong one into the email -- Doh! Sorry for any wasted time. Installing from Etch floppies would be much more sensible. > http://archive.debian.org/debian/dists/etch/main/installer-i386/current/images/floppy/ Cheers, Phil. -- |)| Philip Hands [+44 (0)20 8530 9560]http://www.hands.com/ |-| HANDS.COM Ltd.http://www.uk.debian.org/ |(| 10 Onslow Gardens, South Woodford, London E18 1NE ENGLAND pgpkbysDntqEO.pgp Description: PGP signature
Re: floppy install
Hi, Philip Hands wrote: > One could of course install Sarge, using images from here: > > > http://archive.debian.org/debian/dists/sarge/main/installer-i386/current/images/floppy/ > > and then edit /etc/apt/source.list and apt-get update ; apt-get > dist-upgrade. > > A minimal Sarge install should be quick, and the upgrade should be > trivial, after which running tasksel should get one to the same place > as a normal install. BTW, is there any reason why not install Etch from floppy instead of Sarge? There are floppy images available for Etch: http://archive.debian.org/debian/dists/etch/main/installer-i386/current/images/floppy/ That would result in only one upgrade step (etch -> lenny) instead of two (sarge -> etch -> lenny). Holger -- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Created with Sylpheed 2.5.0 under DEBIAN GNU/LINUX 5.0.0 - L e n n y Registered LinuxUser #311290 - http://counter.li.org/ = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100711220914.cf537a5b.li...@wansing-online.de
Re: floppy install
Hi Holger, On Donnerstag, 8. Juli 2010, Holger Wansing wrote: > I could perhaps use one of the force options in dpkg, or something like > that, but I wanted to ask for the "correct debian way" for such situations, > as this all would maybe lead to a "semi-official floppy installation > howto". The correct debian way to upgrade is not to skip an upgrade, like you tried. It might work fine or it might need workarounds, but it's not the recommended way. cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: floppy install
Hello, Philip Hands wrote: > Is it worth mentioning this for future people hunting for floppy > installs? > > James, if you try that, perhaps you could write-up any issues you bump > into, so that we could still offer a floppy install method, even if we > no longer try to cram the latest installer onto a floppy. I'm on the way doing such test installation the explained way, in order to provide a install documentation later. I have installed a sarge base system via floppy and netinst cd, everything fine so far. Now I tried to upgrade to lenny (yes, I know the recommended way would be to upgrade to etch first, and then to lenny in a second step, but it would be nice, if it works with on step, or what do you think?) Now I have a problem and want to ask for assistance: the upgrade fails due to the packages passwd and debianutils (passwd 1:4.0.3-31sarge9 and debianutils 2.8.4). The binary "/usr/sbin/add-shell" is in the package 'passwd' in sarge, while in lenny, the binary is in the package 'debianutils', it was moved from one package to the other. So, the upgrade stops with the error message (only wrote from mind) "debianutils: trying to overwrite add-shell, which is already in package passwd". I could perhaps use one of the force options in dpkg, or something like that, but I wanted to ask for the "correct debian way" for such situations, as this all would maybe lead to a "semi-official floppy installation howto". Thanks Holger -- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Created with Sylpheed 2.5.0 under DEBIAN GNU/LINUX 5.0.0 - L e n n y Registered LinuxUser #311290 - http://counter.li.org/ = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100708221259.d86ba446.li...@wansing-online.de
Re: floppy install
On Thu, 8 Jul 2010 22:12:59 +0200, Holger Wansing wrote: ... > So, the upgrade stops with the error message (only wrote from mind) > "debianutils: trying to overwrite add-shell, which is already in > package passwd". Does upgrading passwd first, with something like: apt-get install passwd get you over this bump? Cheers, Phil. -- |)| Philip Hands [+44 (0)20 8530 9560]http://www.hands.com/ |-| HANDS.COM Ltd.http://www.uk.debian.org/ |(| 10 Onslow Gardens, South Woodford, London E18 1NE ENGLAND pgp7YHNmaIFWo.pgp Description: PGP signature
Re: floppy install
On Fri, 25 Jun 2010 06:32:15 +0200, Christian PERRIER wrote: > Quoting James (ja...@onyx.nurealm.net): > > > So, where are these floppy install images? Or do they exist? Or is the > > documentation just wrong? > > > There are no more floppy install disks as things no longer fit on them > for quite a while now. Sorry for this. One could of course install Sarge, using images from here: http://archive.debian.org/debian/dists/sarge/main/installer-i386/current/images/floppy/ and then edit /etc/apt/source.list and apt-get update ; apt-get dist-upgrade. A minimal Sarge install should be quick, and the upgrade should be trivial, after which running tasksel should get one to the same place as a normal install. Is it worth mentioning this for future people hunting for floppy installs? James, if you try that, perhaps you could write-up any issues you bump into, so that we could still offer a floppy install method, even if we no longer try to cram the latest installer onto a floppy. Cheers, Phil. -- |)| Philip Hands [+44 (0)20 8530 9560]http://www.hands.com/ |-| HANDS.COM Ltd.http://www.uk.debian.org/ |(| 10 Onslow Gardens, South Woodford, London E18 1NE ENGLAND pgp71ukTM3Jpp.pgp Description: PGP signature
Re: floppy install
Hello, Alexander Reichle-Schmehl wrote: > -You can download a couple of image files the size of a floppy disk > -or another removable media of similar small size, write them to the media, > +You can download a couple of image files the size of a > +removable media of similar small size, write them to the media, > and then start the installation by booting from that. That sentence seems to be hard to understand for me (both the old and the new version). I am not a native english speaker, but I could not find out, what that should mean. And: the "similar" has lost its reference: It was" floppys and similar media", now it is "similar media". Similar to what? I would propose: You can download a couple of image files that should fit on removable media of small size, write them to ... Greetings Holger -- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Created with Sylpheed 2.5.0 under DEBIAN GNU/LINUX 5.0.0 - L e n n y Registered LinuxUser #311290 - http://counter.li.org/ = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100625140914.57e44688.li...@wansing-online.de
Re: floppy install
Hi! Am 25.06.2010 06:32, schrieb Christian PERRIER: > There are no more floppy install disks as things no longer fit on them > for quite a while now. Sorry for this. > > Documentation that still points them should be updated. I just applied the following: -Tiny CDs, floppy disks, USB sticks, etc +Tiny CDs, USB sticks, etc -You can download a couple of image files the size of a floppy disk -or another removable media of similar small size, write them to the media, +You can download a couple of image files the size of a +removable media of similar small size, write them to the media, and then start the installation by booting from that. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c2473c2.6070...@schmehl.info
Re: floppy install
Quoting James (ja...@onyx.nurealm.net): > So, where are these floppy install images? Or do they exist? Or is the > documentation just wrong? There are no more floppy install disks as things no longer fit on them for quite a while now. Sorry for this. Documentation that still points them should be updated. signature.asc Description: Digital signature
floppy install
Hey Looking at this page http://www.debian.org/distrib/netinst there is prominantly referenced Tiny CDs, floppy disks, USB sticks, etc with, in my case, particular interest in the phrase "floppy disks", then which, if, for instance, the i386 link is followed http://ftp.nl.debian.org/debian/dists/lenny/main/installer-i386/current/images/ and reading the manifest http://ftp.nl.debian.org/debian/dists/lenny/main/installer-i386/current/images/MANIFEST there seems to, in fact, be no such thing as a "floppy disk" size set of vmlinuz and initrd.img. So, where are these floppy install images? Or do they exist? Or is the documentation just wrong? Thanks James -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100625013218.bd80584...@onyx.nurealm.net
Processed: installation report: #480935: floppy install 20080227 not working - REASSIGN
Processing commands for [EMAIL PROTECTED]: > reassign 480935 syslinux Bug#480935: installationreport: floppy install 20080227 not working Bug reassigned from package `installation-reports' to `syslinux'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#480935: installationreport: floppy install 20080227 not working
Package: installation-reports Boot method: Image version: < http://ftp.nl.debian.org/debian/dists/testing/main/ installer-i386/current/images/ > Date: <11.05.2008 12:00> Machine: Processor: several (486 + Pentium II + Pentium) Memory: different (from 32MB to 192MB) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Tried the floppy install on three different machines, with similar results: booting from "boot" floppy -> initial boot screen - Pressed ENTER -> "Loading linux .." -> "Loading initrd " -> "ready" -> [Then cursor flashing in the next line, and hang for ever] and: [Sometimes I got a kernel panic: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(9,0)] Tried also with params like "acpi=off" or "noapic" or "nolapic" or "BOOT_DEBUG=3": no success, no additional infos. Kind regards Holger -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#441446: Swap partition problem with low memory "expert" floppy install
On Tue 02 Oct, Jérémy Bobbio wrote: > On Sun, Sep 09, 2007 at 09:05:36PM +, Chris Bell wrote: > >I then attempted to install a second system on hdb plus hdc, with swap > > plus a single RAID 1 partition on each disc. I tried several times with > > similar parameters, and each time the swap partition on every one of the > > three discs was displayed by Partman but the error message later said that > > there was no swap available and the installation failed. > > Was the message one which follows? > > No swap partition found; userspace software suspend will not work > > Currently userspace software suspend can write only to a swap > partition. Your system doesn't seem to have such a partition. Please > make one, preferably with twice the size of your physical ram. Then > run dpkg-reconfigure or setup the configuration file yourself. > > > In this case, you have been bitten by #427104Â [1], which is a bug in the > uswsusp package. This bug is going to be fixed in the next Etch point > release. > > [1]Â http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=427104 > > Cheers, Yes that was part of the problem, but I also failed to install Etch in "expert" mode starting from both the most recent set of floppies and from CD, both in low memory mode (64M RAM) and with 128M RAM, the point of failure always being somewhere around setting up the printing system, just before the first re-boot, although I did manage to get past the re-boot, but it failed to complete the boot. A simple auto installation (just started by pressing return) just worked. I have installed many debian systems, but this was my first series of attempts to install 4.0r1 and I still do not understand what was causing the failures. I used both uk.debian.org direct, and a local apt-cacher as proxy, as well as a CD built using jigdo, burned and verified immediately before use, with a brand new DVD drive. I wanted to test what would happen if I physically moved one of a RAID1 pair between IDE cables, starting with one connected as primary slave and the other as secondary master, ending with both connected via the secondary cable. I first tried to install a simple system on the first of three identical drives (primary IDE master) in expert mode, and after repeated failures installed the basic system in auto mode, which just worked. The swap partition was visible to other later installations, but in every case I created a swap partition on every drive. I then tried to install a simple basic system (base system plus desktop) on the second and third drives, with single LVM on RAID1. After several failures I tried just / on RAID1, but this also failed. I then spent some time trying to figure out why a simple installation in expert mode gave repeated failures, but did not achieve any repeatable conclusion. The most likely cause that I could find was that some files had been upgraded or replaced during security updates, and the installer was downloading files which did not match the specifications. -- Microsoft sells you Windows ... Linux gives you the whole house. Chris Bell
Bug#441446: Swap partition problem with low memory "expert" floppy install
On Sun, Sep 09, 2007 at 09:05:36PM +, Chris Bell wrote: >I then attempted to install a second system on hdb plus hdc, with swap > plus a single RAID 1 partition on each disc. I tried several times with > similar parameters, and each time the swap partition on every one of the > three discs was displayed by Partman but the error message later said that > there was no swap available and the installation failed. Was the message one which follows? No swap partition found; userspace software suspend will not work Currently userspace software suspend can write only to a swap partition. Your system doesn't seem to have such a partition. Please make one, preferably with twice the size of your physical ram. Then run dpkg-reconfigure or setup the configuration file yourself. In this case, you have been bitten by #427104 [1], which is a bug in the uswsusp package. This bug is going to be fixed in the next Etch point release. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=427104 Cheers, -- Jérémy Bobbio.''`. [EMAIL PROTECTED]: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature
Bug#299564: marked as done (Floppy install needs ide-drivers disk to allow early swap mount on lowmem installs)
Your message dated Sat, 29 Sep 2007 17:39:13 -0500 with message-id <[EMAIL PROTECTED]> and subject line Shipping Clerk - flexible time work-at-home opening has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: installation-reports INSTALL REPORT Debian-installer-version: 14 Mar 2005 uname -a: Linux bob 2.4.27-2-586tsc #1 Thu Jan 20 10:47:31 JST 2005 i586 GNU/Linux Date: 14 Mar 2005 11:00 Method: Installed HDD into laptop, installed from 1.44M floppy images then installed via PCMCIA network through debian.goldweb.com.au/debian, not proxied. After initial install complete moved HDD into target laptop as target laptop didn't have enough ram for the installer (only 16M). Machine:IBM Thinkpad 380XD Processor: Intel Pentium 200Mhz MMX Memory: 64MB Root Device:IDE Root Size/partition table: hda1 = swap 256MB hda2 = linux3.8GB Output of lspci and lspci -n: :00:00.0 Host bridge: OPTi Inc. 82C557 [Viper-M] (rev 14) :00:01.0 ISA bridge: OPTi Inc. 82C558 [Viper-M ISA+IDE] (rev 02) :00:02.0 VGA compatible controller: Cirrus Logic GD 7548 :00:14.0 IDE interface: OPTi Inc. 82C621 [Viper-M/N+] (rev 12) :00:00.0 0600: 1045:c557 (rev 14) :00:01.0 0601: 1045:c558 (rev 02) :00:02.0 0300: 1013:0038 :00:14.0 0101: 1045:c621 (rev 12) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [E] Was not using CD but installer forced detection Load installer modules: [E] IDE driver is on FDD marked as cd-drivers.img Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [O] Comments/Problems: The IDE drivers are on the fdd image marked as cd-drivers, this disk should be marked as ide-drivers or somthing more generic. Once loaded drivers from cd-drivers for the IDE the installer still expects to find a debian CD, this should be optional, I had to force the installer to continue without the CD. --- End Message --- --- Begin Message --- Our company is looking for energetic and accountable individuals to occupy Shipping Clerk positions throughout the USA. These vacancies are entirely home-based and do not require any travel or relocation. They are also suitable for students and senior citizens who are able to dedicate up to three business hours per day to their duties. No special qualifications are required, although previous shipping or customer service experience is a plus. We are an international company providing mail/internet order opportunities for a global clientele since 1997. We are based in Russia, and also have offices in Latvia and Kazakhstan. Our business provides online/Online Order facilities for those who are unable to benefit from the convenience of e-commerce due to lack of a banking relationship with an internationally recognized bank or because major online vendors will not ship to their location. We have domestic purchasing agents who place the orders on behalf of our clients, and the goods are then shipped to the local shipping clerks for further sorting and international shipment. We also provide escrow services for high amount and/or web auction orders, and offer assistance with customs clearance, if required. Currently, we are looking for individuals to fill in the positions of shipping clerks throughout the USA. Your duties will include receiving, sorting, repackaging and re-sending the orders made on behalf of our clients using the pre-paid USPS shipping labels that you will receive via email. You will be paid $20 for each parcel that you ship, plus $5 for each order that you will need to re-sort or re-package. We will also cover any other authorized expense, such as extra insurance or shipping materials. Your remuneration will be remitted to you via Western Union twice a month. You can expect to handle 5-15 incoming packages weekly, following a 2 week probation period. You can perform your duties from the convenience of your home. You will generally be re-shipping the orders on same day or next day basis, so you will
Re: USB-floppy install problem
peter green wrote: Greg Flynn wrote: Frans Pop wrote: On Monday 11 June 2007 02:51, Greg Flynn wrote: I'm trying to install debian 4.0r0 via the floppy images. The laptop is a Averatec 3200 series laptop with AMD Athlon XP-m 2000+, 256MB RAM, a dead DVD-ROM/CD-RW (will not work at all), Via chipset(not sure exactly which) and Via-rhine II ethernet. The floppy drive i'm trying to install from is an external USB floppy. Because of the size of the kernel, installing from a USB floppy drive is not supported for Etch (the USB driver modules just do not fit on the boot floppy anymore). If you have no alternatives, we suggest you try installing Sarge instead and upgrade afterwards. Note that installing Sarge is not really straightforward at the moment. The problem is that the installer does not really support installing "oldstable'. As far as we know, it should be possible to work around any problems. We are working to improve that with the next point release for Sarge. Cheers, FJP I tried sarge back in the day and it has the same issue with the usb, after the boot floppy, it won't be able to find any other one I have had recent reports of a sucessfull sarge install with a usb floppy drive. The suite switch issues were avoided by using an appropriate date from snapshot.debian.net as the source (i wouldn't rely on that method though given thier habit of losing stuff). There WERE a load of io errors trying to find the root floppy but it found it eventually. The net drivers floppy was also a pain to get in (required waiting for a timeout and manualy selecting a device that was marked as scsi). Sometime when i'm less busy with other stuff i intend to contact the isolinux guys about the possibility of reading in more than one floppy before booting linux and seeing if i can make a set of floppies that boot D-I that way. btw on a related note will the current plans for fixing up the sarge installer also allow for installing it after it is moved to archive? sorry that should have been syslinux not isolinux and i got the list address wrong -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: USB-floppy install problem
Frans Pop wrote: On Monday 11 June 2007 02:51, Greg Flynn wrote: I'm trying to install debian 4.0r0 via the floppy images. The laptop is a Averatec 3200 series laptop with AMD Athlon XP-m 2000+, 256MB RAM, a dead DVD-ROM/CD-RW (will not work at all), Via chipset(not sure exactly which) and Via-rhine II ethernet. The floppy drive i'm trying to install from is an external USB floppy. Because of the size of the kernel, installing from a USB floppy drive is not supported for Etch (the USB driver modules just do not fit on the boot floppy anymore). If you have no alternatives, we suggest you try installing Sarge instead and upgrade afterwards. Note that installing Sarge is not really straightforward at the moment. The problem is that the installer does not really support installing "oldstable'. As far as we know, it should be possible to work around any problems. We are working to improve that with the next point release for Sarge. Cheers, FJP I tried sarge back in the day and it has the same issue with the usb, after the boot floppy, it won't be able to find any other one -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: USB-floppy install problem
On Monday 11 June 2007 02:51, Greg Flynn wrote: > I'm trying to install debian 4.0r0 via the floppy images. The laptop > is a Averatec 3200 series laptop with AMD Athlon XP-m 2000+, 256MB RAM, > a dead DVD-ROM/CD-RW (will not work at all), Via chipset(not sure > exactly which) and Via-rhine II ethernet. The floppy drive i'm trying > to install from is an external USB floppy. Because of the size of the kernel, installing from a USB floppy drive is not supported for Etch (the USB driver modules just do not fit on the boot floppy anymore). If you have no alternatives, we suggest you try installing Sarge instead and upgrade afterwards. Note that installing Sarge is not really straightforward at the moment. The problem is that the installer does not really support installing "oldstable'. As far as we know, it should be possible to work around any problems. We are working to improve that with the next point release for Sarge. Cheers, FJP pgpQM2atCriZZ.pgp Description: PGP signature
USB-floppy install problem
I'm trying to install debian 4.0r0 via the floppy images. The laptop is a Averatec 3200 series laptop with AMD Athlon XP-m 2000+, 256MB RAM, a dead DVD-ROM/CD-RW (will not work at all), Via chipset(not sure exactly which) and Via-rhine II ethernet. The floppy drive i'm trying to install from is an external USB floppy. my BIOS boot the floppy fine to the Debian boot floppy, but after it starts trying to load the kernel, i hit the error: floppy0: no floppy controllers found cannot load floppy and then it just hangs after that. I have installed debian before on this laptop when the CD drive has seen better days and never had the USB working initially after an install. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#405250: SPARC32 floppy install - issues switching between floppies
Processing commands for [EMAIL PROTECTED]: > reassign 405250 rootskel-bootfloppy Bug#405250: SPARC32 floppy install - issues switching between floppies Bug reassigned from package `installation-reports' to `rootskel-bootfloppy'. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#405250: SPARC32 floppy install - issues switching between floppies
Package: installation-reports Boot method: floppy Image version: http://people.debian.org/~stappers/d-i/images/daily/sparc32/floppy/2.6/boot.img Date: 20061219 Machine: Sun SparcStation 5 Processor: 70Mhz Memory: 80MB Partitions: Output of lspci -nn and lspci -vnn: none Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [E] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: There are some oddities when performing a floppy install of the "testing" version of Debian: After booting the system from floppy, it will not automatically eject the boot floppy when prompting for the root floppy. The install process does later automatically eject the root floppy at the point where it asks if you have a floppy disk containing drivers needed for the install. When you manually switch the boot floppy for the root floppy, it takes exactly four keypresses of the ENTER key before the system takes any action with the root floppy. After hitting the ENTER key on the QWERTY part of a Sun5c keyboard four times, the system behaves normally, and you see a message that the system has found the root image. This is on a SparcStation 20 w/CG6 framebuffer and Sun5c keyboard/mouse, as well as a SparcStation 5 (170Mhz) and SparcStation 5 (70Mhz) using the same keyboard and mouse between all three systems. I've also seen the same behaviour switching floppys during an install where I was using a serial console instead of a real monitor/keyboard/mouse. It took four ENTERs to get from the boot to the root floppy on an x86 Linux workstation running Minicom in VT102 emulation and ANSI emulation. At this point in time, these are the only issues I've seen performing a successful floppy based install of the SPARC32 version of Debian "testing" on a Sun SparcStation 20, a Sun SparcStation 5 (170Mhz processor), and a Sun SparcStation 5 (70Mhz processor). --Dan __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Bug#401396: 20061202 - daily build for sparc32 floppy install
Frans Pop <[EMAIL PROTECTED]> wrote:On Thursday 21 December 2006 03:03, Dan Oglesby wrote: > Could you file one new installation report for the issue that you need > to press enter 4 times to get the root floppy loaded so we can keep > track of that? I think that is now the only issue remaining. Let's investigate the issue below a bit further in this report, but I'd still appreciate a new report for the issue above so we can reassign it properly and don't have to wade through all the history in this one. Done. I sent an email regarding the installation floppy switch issues a few minutes ago. > The install completes on the SS5-70, but will not successfully boot > after install. It doesn't appear to load the esp module from the > initfs, and cannot locate the root filesystem. OK. Let's start with the basic questions: - what are the last messages (10-15) on the console? - do you get dropped into a debug shell on the failure? - if so, please check: - if the module is present in the initrd (ls /lib/modules/) - if the module is loaded (lsmod) - if the module is listed in /etc/modules or in /etc/initramfs-tools/modules or similar - if the device is recognized at all (dmesg) I'm confident the installation process is correct with regards to the module. I verified that the disk I had in the SS5-70 would in fact boot with no modifications in an SS5-170 and the SS20 systems I have at my disposal. All I did was move the drive between the systems, and power up. All systems booted to a prompt. So, the SS5-70 system is not loading the esp module during boot from the initfs for some reason. It does load and configure the esp module automatically during the installation process. I have the console up with a failed boot on the SS5-70. On the systems that boot successfully (SS20 and SS5-170), I do see where the esp module is loaded and the output it generates when the drives and SCSI devices are detected. I do not see this output when I boot the SS5-70 system. The only lines that appear to be error messages are the last four, which are: VFS: Cannot open root device "sda2" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic - not syncing; VFS: Unable to mount root fs on unknown-block(0,0) <0>Press Stop-A (L1-A) to return to the boot prom Pressing L1-A does nothing, and I am not dropped to a debug shell, or see an option at any time for a debug shell. The only way to reset the system is to power cycle it at this point. --Dan __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Processed: retitle 405177 to install-report: no reboot after FLOPPY install
Processing commands for [EMAIL PROTECTED]: > retitle 405177 install-report: no reboot after FLOPPY install Bug#405177: Changed Bug title. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#401396: 20061202 - daily build for sparc32 floppy install
Frans Pop <[EMAIL PROTECTED]> wrote: Hi, Sorry for delay. I had to concentrate on other work for a bit. Not a problem at all. I know how that goes. :-) On Thursday 21 December 2006 03:03, Dan Oglesby wrote: > Could you file one new installation report for the issue that you need > to press enter 4 times to get the root floppy loaded so we can keep > track of that? I think that is now the only issue remaining. Let's investigate the issue below a bit further in this report, but I'd still appreciate a new report for the issue above so we can reassign it properly and don't have to wade through all the history in this one. I'll open a new bug report for the SS5 machines when I return from vacation (after Jan 3rd). > The install completes on the SS5-70, but will not successfully boot > after install. It doesn't appear to load the esp module from the > initfs, and cannot locate the root filesystem. OK. Let's start with the basic questions: - what are the last messages (10-15) on the console? - do you get dropped into a debug shell on the failure? - if so, please check: - if the module is present in the initrd (ls /lib/modules/) - if the module is loaded (lsmod) - if the module is listed in /etc/modules or in /etc/initramfs-tools/modules or similar - if the device is recognized at all (dmesg) I poked around right before leaving vacation, so I can answer some of the questions right now. The last thing that appears on the console is an error message stating the root filesystem could not be located when the system tries to switch from the initfs image to the / partition on the disk. The esp module is present in the initfs image, but does not appear to load. It is listed in /etc/modules in the initfs image as well. I cannot drop to a debug shell, or even do a "Stop-A" to get to PROM at the point the system locks up. It is totally unresponsive to keyboard input at the point where the root filesystem fails to mount. This is with a Sun5c keyboard and a CG6 framebuffer for a console. --Dan __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Bug#401396: 20061202 - daily build for sparc32 floppy install
Hi, Sorry for delay. I had to concentrate on other work for a bit. On Thursday 21 December 2006 03:03, Dan Oglesby wrote: > Could you file one new installation report for the issue that you need > to press enter 4 times to get the root floppy loaded so we can keep > track of that? I think that is now the only issue remaining. Let's investigate the issue below a bit further in this report, but I'd still appreciate a new report for the issue above so we can reassign it properly and don't have to wade through all the history in this one. > The install completes on the SS5-70, but will not successfully boot > after install. It doesn't appear to load the esp module from the > initfs, and cannot locate the root filesystem. OK. Let's start with the basic questions: - what are the last messages (10-15) on the console? - do you get dropped into a debug shell on the failure? - if so, please check: - if the module is present in the initrd (ls /lib/modules/) - if the module is loaded (lsmod) - if the module is listed in /etc/modules or in /etc/initramfs-tools/modules or similar - if the device is recognized at all (dmesg) Cheers, FJP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#401396: 20061202 - daily build for sparc32 floppy install
Frans Pop <[EMAIL PROTECTED]> wrote: On Wednesday 20 December 2006 05:18, Dan Oglesby wrote: > Just completed a flawless install of Debian off of the 2006-12-19 > floppy images on the SS20 system. All hardware detected automatically, > no errors during the install, and the system rebooted to a login > prompt. Great! Thanks for following up. As this report has now become a bit long and difficult to follow, I'm closing it. Could you file one new installation report for the issue that you need to press enter 4 times to get the root floppy loaded so we can keep track of that? I think that is now the only issue remaining. Cheers, FJP The install completes on the SS5-70, but will not successfully boot after install. It doesn't appear to load the esp module from the initfs, and cannot locate the root filesystem. So, the install process is fine on the SS20, but still does not install properly on an SS5 system. There were no errors that I saw during the installation process. Onboard ethernet and SCSI were detected automatically during the install. --Dan __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Bug#401396: 20061202 - daily build for sparc32 floppy install
Frans Pop <[EMAIL PROTECTED]> wrote: On Wednesday 20 December 2006 05:18, Dan Oglesby wrote: > Just completed a flawless install of Debian off of the 2006-12-19 > floppy images on the SS20 system. All hardware detected automatically, > no errors during the install, and the system rebooted to a login > prompt. Great! Thanks for following up. As this report has now become a bit long and difficult to follow, I'm closing it. Could you file one new installation report for the issue that you need to press enter 4 times to get the root floppy loaded so we can keep track of that? I think that is now the only issue remaining. Cheers, FJP If possible, could you wait until I verify the same process works on the SparcStation 5? The install is almost finished, I think all that will be left by the time I get home is to reboot the system. If that works, then I'm sure we're out of the woods on this one. I'll submit a new bug report for the 4 x ENTER issue booting off the floppy when I get home tonight. Thanks! --Dan __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Bug#401396: 20061202 - daily build for sparc32 floppy install
Dan Oglesby <[EMAIL PROTECTED]> wrote: Frans Pop <[EMAIL PROTECTED]> wrote: On Tuesday 12 December 2006 05:32, Dan Oglesby wrote: All of my hardware in the SS5-70 is detected automatically by the 2006-12-16 floppy images. The older floppies would not automatically detect the onboard ethernet chipset (sunlance), so I had to choose the module manually during the install after it failed to detect any networking hardware. When I was doing the installs on the SS20, I had to manually choose an ethernet chipset module and the SCSI module. This was with floppies older than the 2006-12-16 images. I will retest the SS20 with the latest floppy images tonight. --Dan Just completed a flawless install of Debian off of the 2006-12-19 floppy images on the SS20 system. All hardware detected automatically, no errors during the install, and the system rebooted to a login prompt. Started the install to the SS5-70 just now. --Dan __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Bug#401396: 20061202 - daily build for sparc32 floppy install
Frans Pop <[EMAIL PROTECTED]> wrote: On Tuesday 12 December 2006 05:32, Dan Oglesby wrote: > Both boots I had to manually tell it to load the lance module for my > onboard NIC. I can't find a lance module, so I guess you mean sunlance. Sorry, I meant sunlance. What exactly do you mean by "both boots"? Does the NIC get detected automatically by the installer or not? If it does get detected by the installer, it should automatically add the module to /etc/modules for the installed system. Could you check if it is listed in that file? All of my hardware in the SS5-70 is detected automatically by the 2006-12-16 floppy images. The older floppies would not automatically detect the onboard ethernet chipset (sunlance), so I had to choose the module manually during the install after it failed to detect any networking hardware. When I was doing the installs on the SS20, I had to manually choose an ethernet chipset module and the SCSI module. This was with floppies older than the 2006-12-16 images. I will retest the SS20 with the latest floppy images tonight. --Dan __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Bug#401396: 20061202 - daily build for sparc32 floppy install
Frans Pop <[EMAIL PROTECTED]> wrote: On Sunday 17 December 2006 06:03, Dan
Oglesby wrote:
> The installation went perfect, all hardware detected (network, SCSI
> controller, and hard drive), drive partitioned just fine. After
> rebooting, it looks like the SCSI controller module is missing from the
> initial ramdisk again. System boots from the hard drive, then can't
> find the root filesystem (can't open root device).
Is this the esp module again or a different one?
It's esp again.
This is strange because the installer should add the esp module in
/etc/initramfs-tools/modules, which in turn should ensure that the initrd
contains and loads it.
I'm pretty sure it's in the initramfs image. I booted from the floppies,
switched to the 2nd and 3rd virtual console and started poking around last
night.
Could you check if esp is listed in /etc/initramfs-tools/modules?
Could you check if the initrd actually contains the module or not (should
be under /lib/modules/...; you can check when dropped into the debug
shell)?
It is listed there, and I did see the esp module where I thought it was
supposed to be (with the kernel modules). I will verify this again tonight, as
I am away from the machine right now (work).
I did not get dropped to a debug shell. The system hung, and I couldn't even
do a Stop-A on the keyboard to drop to PROM. I had to cycle the power, boot
like I'm doing an install ("rescue" and "expert" doesn't work from SILO, fails
to locate the root filesystem after booting the kernel).
I booted like I was doing an install, let it detect all the hardware, then
switched to the 2nd and 3rd virtual consoles to do the troubleshooting.
> Does this need to go into a seperate bug report since it is a different
> system (but same architecture as the SS20 I've been using)?
No, as there are no different issues I don't think a separate report adds
anything. Thanks very much for your tests!
No problem! :-)
--Dan
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Bug#401396: 20061202 - daily build for sparc32 floppy install
On Tuesday 12 December 2006 05:32, Dan Oglesby wrote: > Both boots I had to manually tell it to load the lance module for my > onboard NIC. I can't find a lance module, so I guess you mean sunlance. What exactly do you mean by "both boots"? Does the NIC get detected automatically by the installer or not? If it does get detected by the installer, it should automatically add the module to /etc/modules for the installed system. Could you check if it is listed in that file? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#401396: 20061202 - daily build for sparc32 floppy install
On Sunday 17 December 2006 06:03, Dan Oglesby wrote: > The installation went perfect, all hardware detected (network, SCSI > controller, and hard drive), drive partitioned just fine. After > rebooting, it looks like the SCSI controller module is missing from the > initial ramdisk again. System boots from the hard drive, then can't > find the root filesystem (can't open root device). Is this the esp module again or a different one? This is strange because the installer should add the esp module in /etc/initramfs-tools/modules, which in turn should ensure that the initrd contains and loads it. Could you check if esp is listed in /etc/initramfs-tools/modules? Could you check if the initrd actually contains the module or not (should be under /lib/modules/...; you can check when dropped into the debug shell)? > Does this need to go into a seperate bug report since it is a different > system (but same architecture as the SS20 I've been using)? No, as there are no different issues I don't think a separate report adds anything. Thanks very much for your tests! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#401396: 20061202 - daily build for sparc32 floppy install
I just did an install tonight using the floppies created on 2006-12-16 on a SparcStation 5, 70Mhz system w/80MB of RAM, a 4.3GB SCSI drive, and a CG6 framebuffer. The installation went perfect, all hardware detected (network, SCSI controller, and hard drive), drive partitioned just fine. After rebooting, it looks like the SCSI controller module is missing from the initial ramdisk again. System boots from the hard drive, then can't find the root filesystem (can't open root device). Does this need to go into a seperate bug report since it is a different system (but same architecture as the SS20 I've been using)? --Dan __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Bug#401396: 20061202 - daily build for sparc32 floppy install
Frans Pop <[EMAIL PROTECTED]> wrote:Could you provide the output of 'lspci -nn' and 'prtconf' (from the sparc-utils package) for your box? Just to make sure I wasn't incorrect in my assumptions that lspci wouldn't work, I installed the pciutils package and ran the utility as you asked. It returned with no output. debian:~# lspci -nn debian:~# --Dan __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Bug#401396: 20061202 - daily build for sparc32 floppy install
Frans Pop <[EMAIL PROTECTED]> wrote:> Both boots I had to manually tell it to load the lance module for my > onboard NIC. Could you provide the output of 'lspci -nn' and 'prtconf' (from the sparc-utils package) for your box? lspci doesn't exist on the system (no PCI slots anyway). prtconf returns the following: System Configuration: Sun Microsystems sun4m Memory size: 256 Megabytes System Peripherals (Software Nodes): SUNW,SPARCstation-20 packages (driver probably installed) disk-label (driver probably installed) deblocker (driver probably installed) obp-tftp (driver probably installed) options (driver probably installed) aliases (driver probably installed) openprom (driver probably installed) iommu (driver probably installed) sbus (driver probably installed) espdma (driver probably installed) esp (driver probably installed) sd (driver probably installed) st (driver probably installed) ledma (driver probably installed) le (driver probably installed) SUNW,bpp (driver probably installed) SUNW,DBRIe (driver probably installed) cgsix (driver probably installed) obio (driver probably installed) zs (driver probably installed) zs (driver probably installed) eeprom (driver probably installed) counter (driver probably installed) interrupt (driver probably installed) SUNW,fdtwo (driver probably installed) auxio (driver probably installed) power (driver probably installed) memory (driver probably installed) virtual-memory (driver probably installed) eccmemctl (driver probably installed) SUNW,sx (driver probably installed) TI,TMS390Z55 (driver probably installed) TI,TMS390Z55 (driver probably installed) I'm trying to get a SS5-70 to install via floppy, but it's not working as well as the SS20 did. The installation went fine, but when it boots it can't find the disk again. I'm going to try the latest disk images on the SS5 tonight and see if it's fixed already. --Dan __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Bug#401396: 20061202 - daily build for sparc32 floppy install
On Tuesday 12 December 2006 05:32, Dan Oglesby wrote: > I first tried to boot my SS20 that contained a CG6 framebuffer and a > Sun Wide-SCSI + 100Mbit NIC SBUS card, but it froze the system hard > while loading the esp module. So, I pulled the SBUS board with the > SCSI and NIC, and tried again. This time it detected all hardware, and > did a successful installation. The sparc kernel maintainer for Debian is going to look into this > Both boots I had to manually tell it to load the lance module for my > onboard NIC. Could you provide the output of 'lspci -nn' and 'prtconf' (from the sparc-utils package) for your box? > kernel: program parted_server is using a deprecated SCSI ioctl, please > convert it to SG_IO Known issue, but thanks for mentioning it. Cheers, FJP pgpbmwftDbXt2.pgp Description: PGP signature
Bug#401396: 20061202 - daily build for sparc32 floppy install
Frans Pop <[EMAIL PROTECTED]> wrote:> It appears to work after pressing the Enter key on the number pad, then > pressing the Enter key on the keyboard. I was able to duplicate this > on the serial console as well. I get a ^M when I'm on the serial > console after pressing the number pad Enter key. OK. I doubt we'll have time to look into this before the release of Etch. Nice to hear that floppies actually work. We've not had an installation report for those in ages :-) OK, played with this again tonight, and it takes four ENTERs to get the root floppy to mount. Doesn't matter about timing the ENTERs, (four quick taps of ENTER will get it going). This was with the ENTER key on a Sun5c keyboard, not touching the one on the number pad. > I was able to complete an install once the root image loaded, but the > esp module doesn't get loaded in the initial ramdisk image, so the > system won't boot properly after install. This should be fixed with current images. Would be nice if you could verify. It has been verified. :-) I first tried to boot my SS20 that contained a CG6 framebuffer and a Sun Wide-SCSI + 100Mbit NIC SBUS card, but it froze the system hard while loading the esp module. So, I pulled the SBUS board with the SCSI and NIC, and tried again. This time it detected all hardware, and did a successful installation. Both boots I had to manually tell it to load the lance module for my onboard NIC. The 18GB SCSI drive was detected properly, and parted was able to use the entire drive. I did see the following message on the fourth virtual terminal repeating while parted was doing its thing: kernel: program parted_server is using a deprecated SCSI ioctl, please convert it to SG_IO After the install, the system booted properly, and went straight to a login prompt without anything that looked like an error. I'm going to see if this works on some of my SS5 systems now. :-) Thanks!!! --Dan - Everyone is raving about the all-new Yahoo! Mail beta.
Bug#401396: 20061202 - daily build for sparc32 floppy install
Frans Pop <[EMAIL PROTECTED]> wrote: (Please always reply to the bug report rather than individual persons.) It looks like the message I replied to was not CC'd to the mailing list. I'll make sure to CC the list from now on. On Monday 11 December 2006 21:14, you wrote: > Frans Pop wrote: > > Just tried today's testing boot floppies along with a CG6 > > framebuffer, Sun monitor, and Sun Type5 keyboard. It still looks > > like it needs more than one ENTER key press at the root disk prompt, > > but it did continue the boot process. > > So the problem is not the enter key versus the keypad enter key, but > rather that it needs to be pressed more than once? > > Were you able to complete the installation after loading the other > floppies? > > P.S. Please type your replies below the text you quote (and delete any > irrelevant text). That makes things much easier to read... > > It appears to work after pressing the Enter key on the number pad, then > pressing the Enter key on the keyboard. I was able to duplicate this > on the serial console as well. I get a ^M when I'm on the serial > console after pressing the number pad Enter key. OK. I doubt we'll have time to look into this before the release of Etch. Nice to hear that floppies actually work. We've not had an installation report for those in ages :-) > I was able to complete an install once the root image loaded, but the > esp module doesn't get loaded in the initial ramdisk image, so the > system won't boot properly after install. This should be fixed with current images. Would be nice if you could verify. I'll download the newest images tonight and see how things go. I'm new to the whole Debian community, so I apologize if my postings are in the wrong mailing lists and such. I'll probably switch to a different mail account with a real mail client tonight, so it'll be easier to format replies and keep things organized. --Dan - Want to start your own business? Learn how on Yahoo! Small Business.
Bug#401396: 20061202 - daily build for sparc32 floppy install
(Please always reply to the bug report rather than individual persons.) On Monday 11 December 2006 21:14, you wrote: > Frans Pop <[EMAIL PROTECTED]> wrote: > > Just tried today's testing boot floppies along with a CG6 > > framebuffer, Sun monitor, and Sun Type5 keyboard. It still looks > > like it needs more than one ENTER key press at the root disk prompt, > > but it did continue the boot process. > > So the problem is not the enter key versus the keypad enter key, but > rather that it needs to be pressed more than once? > > Were you able to complete the installation after loading the other > floppies? > > P.S. Please type your replies below the text you quote (and delete any > irrelevant text). That makes things much easier to read... > > It appears to work after pressing the Enter key on the number pad, then > pressing the Enter key on the keyboard. I was able to duplicate this > on the serial console as well. I get a ^M when I'm on the serial > console after pressing the number pad Enter key. OK. I doubt we'll have time to look into this before the release of Etch. Nice to hear that floppies actually work. We've not had an installation report for those in ages :-) > I was able to complete an install once the root image loaded, but the > esp module doesn't get loaded in the initial ramdisk image, so the > system won't boot properly after install. This should be fixed with current images. Would be nice if you could verify. > I have a small pile of sun4m machines (three SparcStation 5 systems, > one SparcStation 20 w/dual SM71 processors), with floppies and CD-ROMs. > I'd love to be able to run Debian on these, so anything I can do to > help test stuff, please let me know. I also have a handful of SBus > cards (various framebuffers, 100Mbit + Wide SCSI, and narrow SCSI). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#401396: 20061202 - daily build for sparc32 floppy install
On Friday 08 December 2006 05:21, Dan Oglesby wrote: > Just tried today's testing boot floppies along with a CG6 framebuffer, > Sun monitor, and Sun Type5 keyboard. It still looks like it needs more > than one ENTER key press at the root disk prompt, but it did continue > the boot process. So the problem is not the enter key versus the keypad enter key, but rather that it needs to be pressed more than once? Were you able to complete the installation after loading the other floppies? P.S. Please type your replies below the text you quote (and delete any irrelevant text). That makes things much easier to read... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#401396: 20061202 - daily build for sparc32 floppy install
Just tried today's testing boot floppies along with a CG6 framebuffer, Sun monitor, and Sun Type5 keyboard. It still looks like it needs more than one ENTER key press at the root disk prompt, but it did continue the boot process. --Dan Frans Pop <[EMAIL PROTECTED]> wrote: On Sunday 03 December 2006 07:01, Dan Oglesby wrote: > Comments/Problems: After booting from the boot.img on floppy, the > system prompted for the root.img floppy to be inserted into the floppy > drive. After manually ejecting the boot.img floppy and inserting the > root.img floppy, the system would not proceed after pressing the > "ENTER" key. What type of keyboard do you have connected to the machine? Sun, USB, regular PC? - Everyone is raving about the all-new Yahoo! Mail beta.
Bug#401396: 20061202 - daily build for sparc32 floppy install
I just tried to boot from floppy again, and this time used the ENTER key on the numeric key pad. It appears to work using that ENTER key. Still did not work using the ENTER key on the qwerty area of the keyboard. --Dan Frans Pop <[EMAIL PROTECTED]> wrote: On Sunday 03 December 2006 07:01, Dan Oglesby wrote: > Comments/Problems: After booting from the boot.img on floppy, the > system prompted for the root.img floppy to be inserted into the floppy > drive. After manually ejecting the boot.img floppy and inserting the > root.img floppy, the system would not proceed after pressing the > "ENTER" key. What type of keyboard do you have connected to the machine? Sun, USB, regular PC? - Cheap Talk? Check out Yahoo! Messenger's low PC-to-Phone call rates.
Bug#401396: 20061202 - daily build for sparc32 floppy install
Serial console at 9600,8,n,1. Connected to a Linux machine with minicom in vt102 emulation mode. When I hit ENTER, the console drops down a line, so it's getting the command (no other issues using the console so far either). --Dan Frans Pop <[EMAIL PROTECTED]> wrote: On Sunday 03 December 2006 07:01, Dan Oglesby wrote: > Comments/Problems: After booting from the boot.img on floppy, the > system prompted for the root.img floppy to be inserted into the floppy > drive. After manually ejecting the boot.img floppy and inserting the > root.img floppy, the system would not proceed after pressing the > "ENTER" key. What type of keyboard do you have connected to the machine? Sun, USB, regular PC? - Cheap Talk? Check out Yahoo! Messenger's low PC-to-Phone call rates.
Bug#401396: 20061202 - daily build for sparc32 floppy install
On Sunday 03 December 2006 07:01, Dan Oglesby wrote: > Comments/Problems: After booting from the boot.img on floppy, the > system prompted for the root.img floppy to be inserted into the floppy > drive. After manually ejecting the boot.img floppy and inserting the > root.img floppy, the system would not proceed after pressing the > "ENTER" key. What type of keyboard do you have connected to the machine? Sun, USB, regular PC? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#401396: 20061202 - daily build for sparc32 floppy install
Package: installation-reports Boot method: floppy Image version: http://people.debian.org/~stappers/d-i/images/daily/sparc32/floppy/2.6/ Date: 2006-12-02 23:30 Machine: Sun SparcStation 5 Processor: microSPARC II 70Mhz Memory: 80 MB Partitions: none Output of lspci -nn and lspci -vnn: none Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [E] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: After booting from the boot.img on floppy, the system prompted for the root.img floppy to be inserted into the floppy drive. After manually ejecting the boot.img floppy and inserting the root.img floppy, the system would not proceed after pressing the "ENTER" key. - Everyone is raving about the all-new Yahoo! Mail beta.
Bug#394079: marked as done (installation-reports: x86 floppy install failed, cpio missing)
Your message dated Wed, 15 Nov 2006 21:17:27 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#394079: fixed in rootskel 1.42 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: installation-reports Severity: normal Hi, I just activated my good old floppy drive and did a test with the images from 17.10.06: inserting the boot disk works fine, I was prompted to give root disk; then this: Loading ../init: 194: cpio not found failed to extract initrd (may be out of space on ram disk) Giving up! I tried with two other media for boot and root disk, but no way. cpio is not there. Best Holger -- == Created with Sylpheed 2.2.2 under Debian GNU/LINUX 3.1 »Sarge« http://counter.li.org/, Registered LinuxUser #311290 Spamfiltering by bogofilter.sourceforge.net = --- End Message --- --- Begin Message --- Source: rootskel Source-Version: 1.42 We believe that the bug you reported is fixed in the latest version of rootskel, which is due to be installed in the Debian FTP archive: rootskel-bootfloppy_1.42_i386.udeb to pool/main/r/rootskel/rootskel-bootfloppy_1.42_i386.udeb rootskel_1.42.dsc to pool/main/r/rootskel/rootskel_1.42.dsc rootskel_1.42.tar.gz to pool/main/r/rootskel/rootskel_1.42.tar.gz rootskel_1.42_i386.udeb to pool/main/r/rootskel/rootskel_1.42_i386.udeb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Frans Pop <[EMAIL PROTECTED]> (supplier of updated rootskel package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 16 Nov 2006 05:46:50 +0100 Source: rootskel Binary: rootskel-bootfloppy rootskel Architecture: source i386 Version: 1.42 Distribution: unstable Urgency: low Maintainer: Debian Install System Team Changed-By: Frans Pop <[EMAIL PROTECTED]> Description: rootskel - Skeleton root filesystem used by debian-installer (udeb) rootskel-bootfloppy - Skeleton root filesystem used by debian-installer boot floppy (udeb) Closes: 394079 398255 Changes: rootskel (1.42) unstable; urgency=low . [ Sylvain Ferriol ] * Include klibc-utils in src-rootskel. cpio binary and klibc-utils share the same klibc library. Closes: #394079, #398255. Files: 277cc23a052c182854fc5fc6c593c6a4 909 debian-installer standard rootskel_1.42.dsc 9c31150abe684ec4cbb6caf12ea517ed 36484 debian-installer standard rootskel_1.42.tar.gz fe028f348d1ed26e0421ddfe2048cd28 6128 debian-installer standard rootskel_1.42_i386.udeb a08d6b9b7ea1846f8e2c722c41e2ce0e 88202 debian-installer extra rootskel-bootfloppy_1.42_i386.udeb Package-Type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFW/EDgm/Kwh6ICoQRAodbAKCjmPczYRAKvteW63Z3oRQiy1uugACgrP8s j/CwzH8exI47BfJQM7sqMdw= =WY4W -END PGP SIGNATURE- --- End Message ---
Processed (with 4 errors): Bug#394079: installation-reports: x86 floppy install failed, cpio missing: REOPEN
Processing commands for [EMAIL PROTECTED]: > reopen 394079 Bug#394079: installation-reports: x86 floppy install failed, cpio missing Bug reopened, originator not changed. > This problem was fixed at ~ 20061026, but now it is there Unknown command or malformed arguments to command. > again (testet with images from 2006 + 20061113) Unknown command or malformed arguments to command. > i386 floppies not usable. Unknown command or malformed arguments to command. > Holger Unknown command or malformed arguments to command. > -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#394079: installation-reports: x86 floppy install: ONE COMMENT
Hi, I forgot to mention: I had the cd-driver image written to a damaged disk. When trying to load it, I got the message, that the load failed, the next screen told about that one installation step failed, and then the system hung up. The screen repeatly changed between the normal screen and complete white flashing. Not usable. Changing to e.g. vt2 worked, but was also unusable because of the same flashing. Only hard reset possible. Although that's not a common situation, I know. Holger -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#394079: installation-reports: x86 floppy install: UPDATE - SUCCESS
Hi, only for completeness: I tried the images from 19.10.2006 and indeed it works. First I did a try without a cd or dvd and thus loading the additional installer modules from the mirror - success. Then I tried with a netinst cd and without network - successfull, too. Well done. Sorry for beeing too late. I would have closed this report with this mail, too. As attachment the file hardware-summary generated by the d-i module "save debug logs" (not sure, if this is ever needed). Holger hardware-summary.tar.gz Description: Binary data
Bug#394079: marked as done (installation-reports: x86 floppy install failed, cpio missing)
Your message dated Fri, 20 Oct 2006 14:22:28 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#394079: installation-reports: x86 floppy install failed, cpio missing has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: installation-reports Severity: normal Hi, I just activated my good old floppy drive and did a test with the images from 17.10.06: inserting the boot disk works fine, I was prompted to give root disk; then this: Loading ../init: 194: cpio not found failed to extract initrd (may be out of space on ram disk) Giving up! I tried with two other media for boot and root disk, but no way. cpio is not there. Best Holger -- == Created with Sylpheed 2.2.2 under Debian GNU/LINUX 3.1 »Sarge« http://counter.li.org/, Registered LinuxUser #311290 Spamfiltering by bogofilter.sourceforge.net = --- End Message --- --- Begin Message --- Closing this bug since it's already fixed in the archive. -- see shy jo --- End Message ---
Bug#394079: installation-reports: x86 floppy install failed, cpio missing
Holger Wansing a écrit : Package: installation-reports Severity: normal Hi, hi I just activated my good old floppy drive and did a test with the images from 17.10.06: inserting the boot disk works fine, I was prompted to give root disk; then this: Loading ../init: 194: cpio not found failed to extract initrd (may be out of space on ram disk) Giving up! I tried with two other media for boot and root disk, but no way. cpio is not there. as cpio is not in klibc udeb package, cpio is build separatly. but cpio was built with libklibc 1.4.27 and boot floppy has 1.4.29 libklibc. so you have to wait tomorrow for new floppies or go there: http://www-timc.imag.fr/Sylvain.Ferriol/debian/d-i/i386/2006_10_19/ Best Holger smime.p7s Description: S/MIME Cryptographic Signature
Bug#394079: installation-reports: x86 floppy install failed, cpio missing
Package: installation-reports Severity: normal Hi, I just activated my good old floppy drive and did a test with the images from 17.10.06: inserting the boot disk works fine, I was prompted to give root disk; then this: Loading ../init: 194: cpio not found failed to extract initrd (may be out of space on ram disk) Giving up! I tried with two other media for boot and root disk, but no way. cpio is not there. Best Holger -- == Created with Sylpheed 2.2.2 under Debian GNU/LINUX 3.1 »Sarge« http://counter.li.org/, Registered LinuxUser #311290 Spamfiltering by bogofilter.sourceforge.net = -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to "recognize" that the install is a floppy install?
Quoting Joey Hess ([EMAIL PROTECTED]): > I do think we should take care to only use this rarely. Making lots of > paths that are determined by boot type will make testing harder, and > help hide bugs. Yeah, I understand. Here the point is not really making a real branch but just display a special debconf note to explain why some dialogs are still using English while users did choose another language. signature.asc Description: Digital signature
Re: How to "recognize" that the install is a floppy install?
Christian Perrier wrote: > Would anyone else have an idea ? > > Indeed, if not already existing, such a mechanism for D-I to always > "know" which type of install it is running could have other uses We could add this to the /etc/lsb-release file in the installer. Just tack on a field, like X_BOOT_METHOD=floppy. I do think we should take care to only use this rarely. Making lots of paths that are determined by boot type will make testing harder, and help hide bugs. -- see shy jo signature.asc Description: Digital signature
How to "recognize" that the install is a floppy install?
In #269972, I developed a patch which could be used by localechooser to warn users that the install runs in English temporarily even if they choose another language. This patch is meant to be used on floppy installs where all translations are removed from the initial udebs for space reasons. The only remazining problem is for localechooser to "recognize" that it is running a floppy install. Sven did suggest to "set some variable for floppy installs et build time" but indeed I don't know how to do this. Would anyone else have an idea ? Indeed, if not already existing, such a mechanism for D-I to always "know" which type of install it is running could have other uses -- signature.asc Description: Digital signature
Bug#357704: Floppy install does not configure boot dir and grub correctly
> step 16 said that it had detected a list of OS's on my computer. but the > list showed only one entry, 'Debian GNU/Linux (testing/unstable), which > could refer to my existing hda3 'testing' OS or my newly installed hda4 > 'testing' OS. the entry in the list shows no device info, so i cannot > tell whether it refers to hda3 or hda4. It certainly refers to the old install, ie hda3. What's puzzling is the lack of detection of the Windows install. > my analysis: i think that the initial problem is that the OS list is not > correct. the install script does not detect all of the OS's on hda. in > my case, there should be 3 OSs: > > hda1 // windows Which Windows flavour? > hda2 // linux swap > hda3 // existing working debian 'testing' (still working well, i am > using it now as i type) > hda4 // newly installed 'testing' which i am trying to install > > since the OS list is not correct, all of the script logic that follows > does not have the correct input to configure grub and the grub boot menu > correctly. > > for more information, i also mounted hda on /mnt/tmp to have a look. > again, the app software was installed, but hda4/boot is empty, except > for the grub subdirectory and files. there is no kernel image stuff in > hda4/boot (i am comparing it to /hda3/boot, which has vmlinuz, config, > initrd, system.map, and all that stuff for booting the kernel.) This is really strange, indeed. Anyone with a better idea? signature.asc Description: Digital signature
Bug#357704: Floppy install does not configure boot dir and grub correctly
Hi Christian, thanks for your email reply. i have some more detailed info for you, based on a third installation attempt following your advice. i re-ran the same installation on the same box and diskettes as before, and took careful notes at step 16, the 'install grub boot loader' step. step 16 said that it had detected a list of OS's on my computer. but the list showed only one entry, 'Debian GNU/Linux (testing/unstable), which could refer to my existing hda3 'testing' OS or my newly installed hda4 'testing' OS. the entry in the list shows no device info, so i cannot tell whether it refers to hda3 or hda4. (it would be good to see device info because, if there are multiple installations of the same debian release on the same box, you could tell which is which.) then step 16 said that, if the list is complete (which it is not), it should be safe to install the boot loader to the MBR of the first harddrive. step 16 offered the default of 'install to MBR', but i did not choose this default because the list was not complete. i chose 'no', hoping to find a menu which would re-scan hda for OS's and choose again. but step 16 presented me only with some examples of how to enter the boot device. so i entered '/dev/hda' (which, i think, is the same as its default anyway), then step 16 installed the boot loader to hda. finally, i completed the remaining steps and rebooted. grub started with only one choice, hda3, my original 'testing' installation. so the outcome of this third installation attempt is the same as the first two, so i think that my steps and menu choices were correct. my analysis: i think that the initial problem is that the OS list is not correct. the install script does not detect all of the OS's on hda. in my case, there should be 3 OSs: hda1 // windows hda2 // linux swap hda3 // existing working debian 'testing' (still working well, i am using it now as i type) hda4 // newly installed 'testing' which i am trying to install since the OS list is not correct, all of the script logic that follows does not have the correct input to configure grub and the grub boot menu correctly. for more information, i also mounted hda on /mnt/tmp to have a look. again, the app software was installed, but hda4/boot is empty, except for the grub subdirectory and files. there is no kernel image stuff in hda4/boot (i am comparing it to /hda3/boot, which has vmlinuz, config, initrd, system.map, and all that stuff for booting the kernel.) anyway, i hope this info is useful. let me know if you would like more info. On Sun, 2006-03-19 at 08:37 +0100, Christian Perrier wrote: (third try as the stupid RBL and so-called "ant-spam system" used by your ISP blocked my first answerplease use a real ISP) Quoting Anthony Merhi ([EMAIL PROTECTED]): > Package: installation-reports > > -> > -> If you don't mind, please don't put my e-mail address on the web. > -> The Debian BTS has a web interface. So I'm afraid that reporting this bug already exposes your mail address. I'm alays puzzled by people wanting to hide their mail address. Do you really want to communicate? :-) > I booted boot.img in expert mode, mounted root.img, loaded > net-drivers.img for the SiS900, configured static IP, then downloaded > the rest from a mirror without a problem. > > I chose Standard System and Desktop/Workstation for software. > > However, while the app software was installed to the correct partition > (hda4), the OS was not installed, and grub did not add hda4 as a menu > choice. You don't explain us what you exactly did at the GRUB installation step. Did you leave the default choices or did you something weird like asking to install GRUB on hda4? If you did the latter, then what you see is expectedthe grub-installer did not touch the GRUB install on the MBR, which is still the one you see booting. This GRUB points to /dev/hda3 as root...which hasn't been touched by the installer and of course does not offer hda4 as an option. If you leave the *default* GRUB option to install on /dev/hda (ie the MBR), then a new GRUB will be installed on the MBR and it will use /dev/hda4 as rootand will offer the 3 choices, I guess.
Bug#357704: Floppy install does not configure boot dir and grub correctly
(second try as the stupid RBL and so-called "ant-spam system" used by your ISP blocked my first answerplease use a real ISP) Quoting Anthony Merhi ([EMAIL PROTECTED]): > Package: installation-reports > > -> > -> If you don't mind, please don't put my e-mail address on the web. > -> The Debian BTS has a web interface. So I'm afraid that reporting this bug already exposes your mail address. I'm alays puzzled by people wanting to hide their mail address. Do you really want to communicate? :-) > I booted boot.img in expert mode, mounted root.img, loaded > net-drivers.img for the SiS900, configured static IP, then downloaded > the rest from a mirror without a problem. > > I chose Standard System and Desktop/Workstation for software. > > However, while the app software was installed to the correct partition > (hda4), the OS was not installed, and grub did not add hda4 as a menu > choice. You don't explain us what you exactly did at the GRUB installation step. Did you leave the default choices or did you something weird like asking to install GRUB on hda4? If you did the latter, then what you see is expectedthe grub-installer did not touch the GRUB install on the MBR, which is still the one you see booting. This GRUB points to /dev/hda3 as root...which hasn't been touched by the installer and of course does not offer hda4 as an option. If you leave the *default* GRUB option to install on /dev/hda (ie the MBR), then a new GRUB will be installed on the MBR and it will use /dev/hda4 as rootand will offer the 3 choices, I guess.
Bug#357704: Floppy install does not configure boot dir and grub correctly
Quoting Anthony Merhi ([EMAIL PROTECTED]): > Package: installation-reports > > -> > -> If you don't mind, please don't put my e-mail address on the web. > -> The Debian BTS has a web interface. So I'm afraid that reporting this bug already exposes your mail address. I'm alays puzzled by people wanting to hide their mail address. Do you really want to communicate? :-) > I booted boot.img in expert mode, mounted root.img, loaded > net-drivers.img for the SiS900, configured static IP, then downloaded > the rest from a mirror without a problem. > > I chose Standard System and Desktop/Workstation for software. > > However, while the app software was installed to the correct partition > (hda4), the OS was not installed, and grub did not add hda4 as a menu > choice. You don't explain us what you exactly did at the GRUB installation step. Did you leave the default choices or did you something weird like asking to install GRUB on hda4? If you did the latter, then what you see is expectedthe grub-installer did not touch the GRUB install on the MBR, which is still the one you see booting. This GRUB points to /dev/hda3 as root...which hasn't been touched by the installer and of course does not offer hda4 as an option. If you leave the *default* GRUB option to install on /dev/hda (ie the MBR), then a new GRUB will be installed on the MBR and it will use /dev/hda4 as rootand will offer the 3 choices, I guess. signature.asc Description: Digital signature
Bug#357704: Floppy install does not configure boot dir and grub correctly
Package: installation-reports -> -> If you don't mind, please don't put my e-mail address on the web. -> Boot method: Floppy. 4 x 1.44 mb Image version: 17-Mar-2006 from http://people.debian.org/~joeyh/d-i/images/daily/floppy/access. Date: 18-Mar-2006, around 6:00 EST Machine: Spare parts, mobo about 3-4 years old. Fairly modern. Runs GNU/Debian well. Processor: AMD K7 Memory: 1GB Partitions: Filesystem Type 1K-blocks Used Available Use% Mounted on [#/dev/hda1 ntfs (not mounted)] [#/dev/hda2 swap] /dev/hda3 reiserfs 16602624 8456792 8145832 51% / [#/dev/hda4 reiserfs (*** not mounted, but see below)] tmpfs tmpfs 518412 0 518412 0% /dev/shm tmpfs tmpfs 518412 100 518312 1% /dev Output of lspci and lspci -n: :00:00.0 Host bridge: Silicon Integrated Systems [SiS] 741/741GX/M741 Host (rev 03) :00:01.0 PCI bridge: Silicon Integrated Systems [SiS] SiS AGP Port (virtual PCI-to-PCI bridge) :00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS964 [MuTIOL Media IO] (rev 36) :00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev 01) :00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) :00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) :00:03.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) :00:03.3 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller :00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 91) :00:0a.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 0a) :00:0a.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 0a) :00:0b.0 VGA compatible controller: ATI Technologies Inc Rage 128 Pro Ultra TR :01:00.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200] (rev 01) :01:00.1 Display controller: ATI Technologies Inc RV280 [Radeon 9200] (Secondary) (rev 01) :00:00.0 0600: 1039:0741 (rev 03) :00:01.0 0604: 1039:0003 :00:02.0 0601: 1039:0964 (rev 36) :00:02.5 0101: 1039:5513 (rev 01) :00:03.0 0c03: 1039:7001 (rev 0f) :00:03.1 0c03: 1039:7001 (rev 0f) :00:03.2 0c03: 1039:7001 (rev 0f) :00:03.3 0c03: 1039:7002 :00:04.0 0200: 1039:0900 (rev 91) :00:0a.0 0401: 1102:0002 (rev 0a) :00:0a.1 0980: 1102:7002 (rev 0a) :00:0b.0 0300: 1002:5452 :01:00.0 0300: 1002:5961 (rev 01) :01:00.1 0380: 1002:5941 (rev 01) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked: [O] Configure network HW: [O] Config network: [O] Detect CD: [ ] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] *** but see below Create file systems: [O] Mount partitions: [O] Install base system: [O] Install boot loader: [E] Reboot: [E] Comments/Problems: and ideas you had during the initial install.> The install went perfectly (but I do miss full-screen ncurses-style menus). I booted boot.img in expert mode, mounted root.img, loaded net-drivers.img for the SiS900, configured static IP, then downloaded the rest from a mirror without a problem. I chose Standard System and Desktop/Workstation for software. However, while the app software was installed to the correct partition (hda4), the OS was not installed, and grub did not add hda4 as a menu choice. Background: I have 1 hardisk, hda, with 4 partitions: hda1 ntfs for Windows, should I need to do something with that thing. hda2 linux paging hda3 reiserfs for my normal GNU/Debian boot device and root (been working fine with 'testing' for a long time) hda4 an empty partition on which I was trying to install afresh the lastest GNU/Debian Prior to this install, grub would offer hda1 (Windows) and hda3 (2.6.15) as boot choices from the MBR. My goal was to keep hda1 and hda3 intact, and try a fresh install on hda4, with safe fallback to hda3 or even hda1 (ugh!). After the install, I expected grub to offer hda1, hda3, and also hda4 (the new fresh install) as well. But it offered only hda3, zapped hda1 (as a menu choice; I can still mount ntfs, so it's alive), and never added hda4, the new install. After rebooting, the system booted up as usual on hda3 (with a different grub timeout), and I mounted hda4 to take a look-see. All of the /usr/* stuff was installed as well as /etc and so on, but 'boot was empty, except for the grub subdir and its file, including menu.lst. So it seems that something went wrong when the configure grub stage ran. The install process changed grub stuff on hda3 as well as creating the /boot/grub dir on hda4. Odd. I performed the whole install twice because I thought that I might have chose the wrong menu number somewhere along the way (being used to full-screen ncurses). Also, I notice that the /etc/
Re: Floppy install: weird Arabic glyph
Quoting Mohammed Adnène Trojette ([EMAIL PROTECTED]): > On Fri, Feb 17, 2006, Davide Viti wrote: > > While writing some instructions about doing a floppy install using > > qemu on the wiki [1] I noticed a weird glyph in the Arabic string. > > I grabbed a screenshot [2] which shows the problem (compare floppy > > vs. netboot) > > Not sure if it's a known problem. > > The right one is correct. > The left one neither uses ligatures (wrong font?) nor respects RTL > direction. This is probably because libfribidi is not available on the root floppy. I'm afraid there's not much we can do about it. Maybe have a special template with NO translations for "Choose language" and display it instead of the standard template with bilingual entries. Anyway, on floppy installs, if one chooses Arabic or any other language than English, the installation will continue in English until packages with translations are downloaded from the network or the CDSee #269972 for which I just proposed a patch to warn users about this limitation. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Floppy install: weird Arabic glyph
On Fri, Feb 17, 2006, Davide Viti wrote: > While writing some instructions about doing a floppy install using > qemu on the wiki [1] I noticed a weird glyph in the Arabic string. > I grabbed a screenshot [2] which shows the problem (compare floppy > vs. netboot) > Not sure if it's a known problem. The right one is correct. The left one neither uses ligatures (wrong font?) nor respects RTL direction. I hope this will help, -- adn Mohammed Adnène Trojette -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Floppy install: weird Arabic glyph
While writing some instructions about doing a floppy install using qemu on the wiki [1] I noticed a weird glyph in the Arabic string. I grabbed a screenshot [2] which shows the problem (compare floppy vs. netboot) Not sure if it's a known problem. regards, Davide [1] http://wiki.debian.org/DebianInstaller/Qemu [2] http://www.webalice.it/zinosat/shots/floppy_install_ar.png signature.asc Description: Digital signature
Bug#291453: Installation report, Sarge/d-i rc2, 20050120, floppy install, x86
Package: installation-reports Debian-installer-version: d-i rc2 floppies (root.img + boot.img + net-drivers.img) uname -a: Linux pitr 2.4.27-2-586-tsc #1 Thu Dec 30 18:06:49 JST 2004 i586 GNU/Linux Date: 20050119-20 Method: Floppy boot and network installation Machine: Fuijutsu desktop PC Processor: Pentium II/200 MHz Memory: 80 Mb Root Device: NEC IDE 1,7Gb Root Size/partition table (df output): Filsystem 1K-blockAnvänt Tillgängl Anv% Monterat på /dev/hda2 685777391811257376 61% / tmpfs39400 0 39400 0% /dev/shm /dev/hda1 793680708548 44816 95% /media/hda1 Output of lspci and lspci -n: :00:00.0 0600: 8086:7030 (rev 02) :00:0c.0 0601: 8086:7000 (rev 01) :00:0c.1 0101: 8086:7010 :00:0c.2 0c03: 8086:7020 (rev 01) :00:0d.0 0300: 1002:5654 (rev 40) Base System Installation Checklist: [O] = OK, [E] = Fel (beskriv utförligt nedan på engelska), [ ] = testade ej Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [E?] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O/E] Reboot: [E] Comments/Problems: -- First, some observations about the installation manual: My first problem was finding the correct floppy images. I think either section 5.1.4 of the manual (Booting the Installer on Intel x86/Booting from Floppies) or section 4.3 (Creating Floppies from Disk Images) should explain which images I need or at least link directly to the MANIFEST file. That link is now in section 4.2.1 where it is not easily found. A link to the ftp directory containing the floppies and to rawrite/rwwrtwin would also be handy. Also, I think that the section about floppy reliability should be moved from 5.3.1 to 4.3. These changes would get all important information about boot floppies in two places instead of four. OK, I can now see that section A.2.2 actually does some of what I ask for. Is it really necessary to spread information to all these places? In general, I also think that chapters 4 and 5 of the manual should be reorganized from "Obtaining media" and "Boot" to one chapter covering the entire process of different types of installations (Floppy/CD/Netboot/USB/harddrive). Sections A through C should be integrated with the beginning of the document. These comments apply to the installation manual at http://d-i.alioth.debian.org/manual/en.i386/index.html, as of 2005-01-05. Now to the installation: I choose Swedish as my language in the first screen, but didn't get swedish until several screens later. That could have been really confusing if I hadn't understod english quite well. On my admittedly very slow computer there are several blank screens that come up after a choice has been made and they sometimes last for more than a couple of seconds. This may give the impression that d-i has hung, but is no big problem. I tried to get an old ISA network card working, but failed. I would have liked rmmod to be present on the system though, now I had to reboot (shifting three floppies) every time I wanted to try another IRQ. I finally gave up and replaced the network card with one that worked. Shouldn't the installation floppies give me the choice to insert a CD (the netinst image for example)? It just downloaded everything from the Debian mirror. Or should I somehow have used the CD instead of the root floppy? The downloads went OK anyway, but not completely smooth. The installer tried to download Packages.gz three times before getting it right. Partitioning went smoothly, I just reused (reformated) an old ext2 partition (hda2) where I used to have Hurd installed. I ignored a partition (hda1) with an old Debian (Linux) installation and reused a swap partition (hda3). There was a tiny skull indicated by my new root partition, but the installer happily allowed me to carry on and the manual doesn't mention it. What does it mean? After doing the base install, I tried to install GRUB. It all seemed OK (My old Debian install was even identified correctly), but the reboot failed with "GRUB hard disk error", so I had to start over from the beginning. I tried LILO instead, with success. This time though, my other Debian installation was not detected. After the reboot I finally got the option to use my CD, but I settled for HTTP install anyway and it worked out just fine. I choose the web server and file server tasks, not sure at that point if file server meant NFS, Samba or FTP. Conclusions: I liked the new debian-installer very much, thank you. Even though I didn't use LVM or RAID this time I really appreciate your work with that. The GRUB problem is of course unacceptable, especially for people who hasn't got a clue about what a boot loa
Bug#280519: marked as done (Boot-floppy install fails to see net driver disk in USB floppy drive)
Your message dated Mon, 15 Nov 2004 13:17:08 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#280519: fixed in floppy-retriever 1.04 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 9 Nov 2004 23:21:43 + >From [EMAIL PROTECTED] Tue Nov 09 15:21:43 2004 Return-path: <[EMAIL PROTECTED]> Received: from atarelbas01.hp.com (atlrel6.hp.com) [156.153.255.205] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CRfJ1-00011z-00; Tue, 09 Nov 2004 15:21:43 -0800 Received: from janus0.fc.hp.com (janus0.fc.hp.com [15.6.89.23]) by atlrel6.hp.com (Postfix) with ESMTP id 3A9DA4679 for <[EMAIL PROTECTED]>; Tue, 9 Nov 2004 18:21:42 -0500 (EST) Received: from robsims.ipf.fc.hp.com (robsims.ipf.fc.hp.com [156.153.222.168]) by janus0.fc.hp.com (Postfix) with ESMTP id 12BB712045 for <[EMAIL PROTECTED]>; Tue, 9 Nov 2004 16:21:42 -0700 (MST) Received: by robsims.ipf.fc.hp.com (Postfix, from userid 20291) id 03F861BBD9; Tue, 9 Nov 2004 16:21:41 -0700 (MST) From: Rob Sims <[EMAIL PROTECTED]> Organization: HP CVL To: [EMAIL PROTECTED] Subject: Boot-floppy install fails to see net driver disk in USB floppy drive Date: Tue, 9 Nov 2004 16:21:41 -0700 User-Agent: KMail/1.6 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: debian-installer Version: pre-rc2 I used the i386 floppy images to install to a Sony PCG-C1X which has no CD-ROM or floppy disk controller. Booting was done via a USB floppy drive. Boot followed by root disks (in expert mode) worked until I was prompted for a driver disk. The system failed to see the network driver image, and simply returned to the load driver prompt each time I tried. Workaround: I changed to another virtual console, mounted the corresponding SCSI device to /floppy, changed back to the setup console, and installation proceeded from there via a Netgear PCMCIA network adapter. -- Rob --- Received: (at 280519-close) by bugs.debian.org; 15 Nov 2004 18:23:14 + >From [EMAIL PROTECTED] Mon Nov 15 10:23:13 2004 Return-path: <[EMAIL PROTECTED]> Received: from newraff.debian.org [208.185.25.31] (mail) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CTlVR-0007R6-00; Mon, 15 Nov 2004 10:23:13 -0800 Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian)) id 1CTlPY-0004r5-00; Mon, 15 Nov 2004 13:17:08 -0500 From: Joey Hess <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] X-Katie: $Revision: 1.51 $ Subject: Bug#280519: fixed in floppy-retriever 1.04 Message-Id: <[EMAIL PROTECTED]> Sender: Archive Administrator <[EMAIL PROTECTED]> Date: Mon, 15 Nov 2004 13:17:08 -0500 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Source: floppy-retriever Source-Version: 1.04 We believe that the bug you reported is fixed in the latest version of floppy-retriever, which is due to be installed in the Debian FTP archive: floppy-retriever_1.04.dsc to pool/main/f/floppy-retriever/floppy-retriever_1.04.dsc floppy-retriever_1.04.tar.gz to pool/main/f/floppy-retriever/floppy-retriever_1.04.tar.gz floppy-retriever_1.04_all.udeb to pool/main/f/floppy-retriever/floppy-retriever_1.04_all.udeb load-floppy_1.04_all.udeb to pool/main/f/floppy-retriever/load-floppy_1.04_all.udeb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joey Hess <[EMAIL PROTECTED]> (supplier of updated floppy-retriever package) (This me
Bug#280519: Boot-floppy install fails to see net driver disk in USB floppy drive
I've found the problem, and a fix has been uploaded. It should show up in the floppy images built tomorrow. I'll try to do some usb floppy testing of my own, though it's a real pain to do with real floppies. -- see shy jo
Bug#280519: Boot-floppy install fails to see net driver disk in USB floppy drive
On Tue, Nov 09, 2004 at 07:36:23PM -0500, Joey Hess wrote: > Hmm, it's supposed to prompt for a device to mount in this case. If you > can boot d-i with DEBCONF_DEBUG=5 and reproduce that and get a copy of > /var/log/syslog that would help debug this. Failing that > /var/log/debian-installer/syslog from your installed system might be > useful. Here's the DEBCONF_DEBUG=5 syslog, before and after mounting the floppy manually: http://www.robsims.com/nomountusb.syslog http://www.robsims.com/nomountusb.syslog.after There was no /var/log/debian-installer/syslog on the installed system. drwxr-xr-x 2 robsims robsims 4096 Nov 14 06:28 cdebconf -rw-r--r-- 1 robsims robsims 14909 Nov 14 06:28 hardware-summary -rw-r--r-- 1 robsims robsims292 Nov 14 06:28 messages -rw-r--r-- 1 robsims robsims 182421 Nov 14 06:28 partman -rw-r--r-- 1 robsims robsims 43278 Nov 14 06:28 status ./cdebconf: total 3128 -rw-r--r-- 1 robsims robsims 54410 Nov 14 06:28 questions.dat -rw-r--r-- 1 robsims robsims 3133921 Nov 14 06:28 templates.dat -- Rob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#280519: Boot-floppy install fails to see net driver disk in USB floppy drive
Rob Sims wrote: > I used the i386 floppy images to install to a Sony PCG-C1X which has no > CD-ROM or floppy disk controller. Booting was done via a USB floppy > drive. Boot followed by root disks (in expert mode) worked until I was > prompted for a driver disk. The system failed to see the network > driver image, and simply returned to the load driver prompt each time I > tried. Hmm, it's supposed to prompt for a device to mount in this case. If you can boot d-i with DEBCONF_DEBUG=5 and reproduce that and get a copy of /var/log/syslog that would help debug this. Failing that /var/log/debian-installer/syslog from your installed system might be useful. -- see shy jo signature.asc Description: Digital signature
Bug#280519: Boot-floppy install fails to see net driver disk in USB floppy drive
Package: debian-installer Version: pre-rc2 I used the i386 floppy images to install to a Sony PCG-C1X which has no CD-ROM or floppy disk controller. Booting was done via a USB floppy drive. Boot followed by root disks (in expert mode) worked until I was prompted for a driver disk. The system failed to see the network driver image, and simply returned to the load driver prompt each time I tried. Workaround: I changed to another virtual console, mounted the corresponding SCSI device to /floppy, changed back to the setup console, and installation proceeded from there via a Netgear PCMCIA network adapter. -- Rob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#272310: Floppy install on Oldworld PowerMac G3 tower
Rick Thomas wrote: > I tried the PowerMac install floppy set from the 18th Most images built on the 18th are broken in the way you describe, I'd suggest trying a different build. -- see shy jo signature.asc Description: Digital signature
Bug#272310: Floppy install on Oldworld PowerMac G3 tower
Package: installation-reports I tried the PowerMac install floppy set from the 18th Index of /~luther/d-i/images/2004-09-18/powerpc/floppy-2.4 NameLast modified Size Description [DIR] Parent Directory26-Aug-2004 21:35 - [ ] asian-root.img 18-Sep-2004 01:35 1.1M [ ] boot.img18-Sep-2004 01:35 1.4M [ ] cd-drivers.img 18-Sep-2004 01:35 1.4M [ ] net-drivers.img 18-Sep-2004 01:35 1.4M [ ] ofonlyboot.img 18-Sep-2004 01:35 1.4M [ ] root-2.img 18-Sep-2004 01:35 1.4M [ ] root.img18-Sep-2004 01:37 1.2M _ Apache/1.3.26 Server at people.debian.org Port 80 The boot floppy reads OK and calls for the root floppy, which also reads OK. It asks for Language (I gave it English), then the screen started blinking. Switching to the other consoles (opt-F2, -F3, -F4), which are also blinking, so it's hard to get any details, it appears that the /sbin/debian-installer process is crashing and restarting repeatedly. Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#270599: Floppy install on Oldworld PowerMac
On Mon, Sep 13, 2004 at 05:15:34PM -0400, Rick Thomas wrote: > I tried again with the latest floppies: > > Index of /~luther/d-i/images/daily/powerpc/floppy-2.4 > > NameLast modified Size Description > > > Parent Directory26-Aug-2004 21:35 - > asian-root.img 13-Sep-2004 03:16 1.2M > boot.img13-Sep-2004 03:17 1.4M > cd-drivers.img 13-Sep-2004 03:17 1.4M > net-drivers.img 13-Sep-2004 03:17 1.4M > ofonlyboot.img 13-Sep-2004 03:17 1.4M > root-2.img 13-Sep-2004 03:17 1.4M > root.img13-Sep-2004 03:18 1.3M > > Apache/1.3.26 Server at people.debian.org Port 80 > > > No change. > > 1) The ofonlyboot still doesn't give me a text screen. > > 2) Loading the root-2 floppy still gives me an error message about > not finding any driver modules, which I ignore and it loads the > root-2 floppy anyway. > > 3) No reasonable combination of choice of mirrors > (ftp.us.debian.org vs debian.uchicago.edu) and distributions > (testing vs unstable) give me anything but "no disks found". > > 4) For what it's worth, at least one combination of mirror and > distro (I don't remember exactly which -- I *think* it was uchicago > and testing) complained about not being able to find any driver > modules (presumably) on the mirror. But the other combinations > didn't complain. (So maybe the uchicago unstable distro does have > driver modules for the 2.4.27 kernel, but their testing > doesn't... Does that make sense? Is there any way to check this?) > > 5) Two of the 2.6 floppy images are still too large to fit on a > physical 1.44 MB disk. Sorry, i haven't had time to work on this recently. On the other hand, Jens managed to boot the 2.6 kernel in miboot, and i normally adapted things to it, let's see how the builds go today. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#270599: Floppy install on Oldworld PowerMac
On Friday, September 10, 2004, at 05:04 PM, Rick Thomas wrote: The "ofonlyboot" has not changed. It reads and inverts the colors of the tuxmac, but never switches to text-mode screen from the inverted color tuxmac. The boot floppy reads and switches to the text screen then asks for the root floppy, which it reads. It then asks for language (English) and location (US) (but not keyboard layout) then invites me to load drivers from a floppy. I gave it the "root-2" floppy and it complained about not being able to find any kernel drivers on that floppy. I chose and re-executed "load drivers from a floppy". This time I gave it the net-drivers floppy, and it was happy. Still thinking that we wouldn't get any where without the root-2 floppy loading (and being a bit bull headed anyway) I tried "load drivers from floppy" for the third time, and again fed it the root-2. It complained again about not finding any kernel modules. This time I told it to "continue without loading drivers" and to my amazement, it started decoding the stuff from the root-2 floppy! Curioser and curioser! I think it was at this point that it asked for my keyboard layout, and suggested "European" as default, even though I had given it every reason to suspect that US-English was my preferred locale. I've reported this violation of the principle of least astonishment before. It proceeded then to find my ethernet interface (remember I'd loaded the net-drivers floppy earlier) and do DHCP discovery on it. This succeeded, as expected. When it asked, I chose the uchicago mirror as usual, and it loaded the installer-components list (I think -- I didn't get the exact words) after which it *again* complained about not finding any kernel modules! I told it to continue anyway, and it started downloading and unpacking installer components from the uchicago mirror (presumably). When it got done with that and moved on to the partitioner, it couldn't find any of my disks (not my IDE main disk or my SCSI Zip disk). The only IDE think it knew about was the CD-ROM drive. Exploring on the F2 console showed that it wasn't just the partitioner that was confused. There was no evidence of IDE or SCSI disks in /proc or /dev. (Same as last time -- no progress on that front...) So I wrapped it up and took a tea break to write this report. I have to consider the check for kernel modules at inappropriate times to be a serious bug... I tried again with the latest floppies: Index of /~luther/d-i/images/daily/powerpc/floppy-2.4 NameLast modified Size Description Parent Directory26-Aug-2004 21:35 - asian-root.img 13-Sep-2004 03:16 1.2M boot.img13-Sep-2004 03:17 1.4M cd-drivers.img 13-Sep-2004 03:17 1.4M net-drivers.img 13-Sep-2004 03:17 1.4M ofonlyboot.img 13-Sep-2004 03:17 1.4M root-2.img 13-Sep-2004 03:17 1.4M root.img13-Sep-2004 03:18 1.3M Apache/1.3.26 Server at people.debian.org Port 80 No change. 1) The ofonlyboot still doesn't give me a text screen. 2) Loading the root-2 floppy still gives me an error message about not finding any driver modules, which I ignore and it loads the root-2 floppy anyway. 3) No reasonable combination of choice of mirrors (ftp.us.debian.org vs debian.uchicago.edu) and distributions (testing vs unstable) give me anything but "no disks found". 4) For what it's worth, at least one combination of mirror and distro (I don't remember exactly which -- I *think* it was uchicago and testing) complained about not being able to find any driver modules (presumably) on the mirror. But the other combinations didn't complain. (So maybe the uchicago unstable distro does have driver modules for the 2.4.27 kernel, but their testing doesn't... Does that make sense? Is there any way to check this?) 5) Two of the 2.6 floppy images are still too large to fit on a physical 1.44 MB disk. Any thoughts? Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#270599: Floppy install on Oldworld PowerMac
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 (Please don't CC the BTS on subjects like this that don't really have anything to do with the bug itself.) Hello Russel, On Saturday 11 September 2004 13:11, Russell Hires wrote: > I've offered my services before in writing up some docs (or simply > modifying the woody ones to fit the sarge install) in a couple of > previous threads. Always happy when help is offered. If you'd like to help on the manual, it would be very good if you could check the Mac-specific portions of the manual. The problem with Mac's is, as I understand it, that there are several different families of hardware that require different approaches (e.g. different bootloaders). It is important to keep these separated and to make sure we cover them all. The suggestion from Rick to first get to know your way around the installer is very valuable. The current version of the manual itself can be found on [1]. Start by reading the document [2] for background information. Next, get an _anonymous_ SVN checkout of the manual [3]. (Note: a full checkout for d-i is 223MB. If you'd like to just checkout the manual, you can use 'debian-installer/installer/doc'.) Look for files in './doc/manual/en/...'. Most Mac-specific parts will be in directories named powerpc or documents named powerpc.xml. There is also Mac-specific stuff hidden in other documents. You can find these by grepping for 'arch="powerpc"'. Start by sending in corrections to this list (patches are preferred). Someone will pick them up and make sure they're included. If you're not comfortable with xml, just send in 'normal' texts and we'll find a way to include them as well. [1]http://d-i.alioth.debian.org/manual/ [2]http://svn.debian.org/viewcvs/d-i/trunk/installer/doc/manual/translations.txt [3]http://www.nl.debian.org/devel/debian-installer/svn Cheers, FJP -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBRMLBgm/Kwh6ICoQRAtL1AJ9+9CHdN+Qy1ldr9/YRwY/DiFQuKQCeOaOk jS7jMukHCZB57vEmu2DQJCI= =KhQC -END PGP SIGNATURE-
Bug#270599: Floppy install on Oldworld PowerMac
Frans Pop wrote: > Ignoring this message will mean your installation is always going to fail as > the installer won't recognize your disk. Nope.. This is a bad interaction between the new warning message in anna and sven's new powerpc root-2 floppy hack. Now anna will complain if any one floppy full of udebs does not happen to contain a kernel module. Good for regular driver floppies, but not for this one, which, AIUI, does not contain any drivers at all, only a few udebs that apparently don't fit anywhere else. IMHO, this hack should go away, or someone will need to write some code to explcitly deal with it by prompting the user for this floppy and bypassing the check in anna.. -- see shy jo signature.asc Description: Digital signature
Re: Floppy install on Oldworld PowerMac
On Thursday, September 9, 2004, at 01:23 PM, Sven Luther wrote: On Thu, Sep 09, 2004 at 12:45:29PM -0400, Rick Thomas wrote: Ummm... The contents of http://people.debian.org/~luther/d-i/images/daily/powerpc/floppy-2.4/ haven't changed in the last few days. Is the build process stalled somewhere? [DIR] 2004-09-08_RSYNC_IN_PROGRESS/ 07-Sep-2004 22:05 - [DIR] 2004-09-09_RSYNC_IN_PROGRESS/ 08-Sep-2004 22:05 - Hmmm.. It seems to be doing it again... 2004-09-11/ 10-Sep-2004 23:13 - 2004-09-12_RSYNC_IN_PROGRESS/ 11-Sep-2004 22:05 - daily/10-Sep-2004 23:13 - It's been this way for over an hour... Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#270599: Floppy install on Oldworld PowerMac
On Saturday, September 11, 2004, at 07:11 AM, Russell Hires wrote: P.S. When are you finally going to start work on the manual? All joking aside... That is an important task! But I kinda figured it was less important than getting the software working at all on oldworld hardware, since I seem to be the only one on the list who has oldworld pmac hardware available for testing. If there were someone else who could do the testing part, I'd have time to work on the documentation part... Any takers out there? Rick I've offered my services before in writing up some docs (or simply modifying the woody ones to fit the sarge install) in a couple of previous threads. Meanwhile, I'm running on a G3/266 that I'd be willing to test with. Also, I need help with setting my G3 to send output to a serial console, since the 2.6.x kernels don't give my voodoo3 card any console data. Russell OK Russell, you're on! Here's what you need to do: First, google a bit to find and get copies of the distribution files for BootX, miboot, and quik -- the three boot-loaders that work on OldWorld PowerMacs. Read and try to understand the documentation that comes with the package distributions. Most of it is sketchy, but if you combine it with more googling for stuff in the various mailinglist archives (debian and YellowDog Linux, in particular, but also the PowerPC Linux mailing list and any other distros that support PowerPC, such as SuSE and Fedora) and there's useful (if anecdotal) stuff in several people's personal home web pages as well. Retrieve and read the Apple Tech notes on Open Firmware. Start with TN1061 and follow pointers from there. There's also lots of useful stuff on the web. Google for "Open Firmware Apple macintosh". There are also some very useful docs about using OpenFirmware with NetBSD. If you're really dedicated, the first stage should take you a couple of weeks. Second, partition your disk so that you have plenty of free space to install test releases of Debian into. Each installation takes a minimum of about 1.5 GB -- more if you want to make it actually useful. So multiply 2-3 GB by the maximum number of test installations you intend to make before you wipe the disk and start over clean. On that disk (or another one dedicated to the purpose) also set up an HFS partition (*not* HFS-plus -- Debian does not at this time support access to HFS-plus filesystems from inside the installer) of about 1 GB (more if you want it to be actually useful other than as an intermediate boot loader. If you're going to run Toast here, you should allow plenty of space [gigabytes] for CD-images). Install MacOS-9 there. Then install BootX (both the BootX extension and the BootX.app application) according to the instructions you got with the BootX distribution. MacOS-X does not support BootX. (Unfortunately, part of the MacOS_X boot loader is called "bootx". It's not related to the one we are interested in here.) Third, download the latest d-i businesscard iso, and burn it (I use Toast) to a CD-RW (don't waste a CD-R on it -- you're probably only going to use it a couple of times at most). Copy the kernel of your choice from the CD (install:powerpc:vmlinux or install:powerpc:2.4:vmlinux) into the "System Folder:Linux Kernels" folder of your MacOS-9 partition, and the initrd.gz file from the same place to the "System Folder:Linux Ramdisks" folder. Invoke BootX.app, set the appropriate parameters and let her rip. Answer the questions and file an installation report. Dig out my previous d-i installation reports for OldWorld PowerPC installations from the mailing list archives. They may give you some useful hints. Fourth, try a floppy disk install. Contact Sven for instructions on where to download the latest floppy images. Let it try to install the quik bootloader, and see if you can figure out how to make that work. If you succeed in this, let me know. I haven't gotten this far yet. When you're completely familiar with all the various aspects of booting, you can start on re-writing a "D-I on OldWorld installation manual". Contact me if you have questions at any point. I've left out a massive amount of detail! Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#270599: Floppy install on Oldworld PowerMac
> > > > P.S. When are you finally going to start work on the manual? > > All joking aside... That is an important task! But I kinda figured it > was less important than getting the software working at all on oldworld > hardware, since I seem to be the only one on the list who has oldworld > pmac hardware available for testing. If there were someone else who > could do the testing part, I'd have time to work on the documentation > part... Any takers out there? > > Rick > I've offered my services before in writing up some docs (or simply modifying the woody ones to fit the sarge install) in a couple of previous threads. Meanwhile, I'm running on a G3/266 that I'd be willing to test with. Also, I need help with setting my G3 to send output to a serial console, since the 2.6.x kernels don't give my voodoo3 card any console data. Russell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#270599: Floppy install on Oldworld PowerMac
On Fri, 2004-09-10 at 17:57, Frans Pop wrote: > On Friday 10 September 2004 23:04, Rick Thomas wrote: > > When it asked, I chose the > > uchicago mirror as usual, and it loaded the installer-components > > list (I think -- I didn't get the exact words) after which it > > *again* complained about not finding any kernel modules! I told it > > to continue anyway, and it started downloading and unpacking > > installer components from the uchicago mirror (presumably). > > Ignoring this message will mean your installation is always going to fail as > the installer won't recognize your disk. > > Missing installer modules probably means you are using an incorrect > distribution on your mirror. > You probably need to select 'unstable' instead of using the default 'testing'. > > You can do this by backing up to the menu (for example from country-chooser), > changing debconf priority to medium, and then choose 'unstable' when you are > selecting your mirror. > > The reason is there are kernel-changes happening ATM and the version the > floppies are build with is probably not yet available in testing. Well... these were the 2.4 floppies. Does that make a difference? I'll try it with a different mirror. That's easy and shouldn't take too much time. The pmac 2.6 floppies have worse problems than that -- specifically, the net-drivers.img and the root.img files are both too large for a 1.44 MB floppy, and the Mac floppy drives can't handle floppy disks written at 2.88 MB density the way some PC drives do. > > Cheers, > Frans > > P.S. When are you finally going to start work on the manual? All joking aside... That is an important task! But I kinda figured it was less important than getting the software working at all on oldworld hardware, since I seem to be the only one on the list who has oldworld pmac hardware available for testing. If there were someone else who could do the testing part, I'd have time to work on the documentation part... Any takers out there? Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#270599: Floppy install on Oldworld PowerMac
On Friday 10 September 2004 23:04, Rick Thomas wrote: > When it asked, I chose the > uchicago mirror as usual, and it loaded the installer-components > list (I think -- I didn't get the exact words) after which it > *again* complained about not finding any kernel modules! I told it > to continue anyway, and it started downloading and unpacking > installer components from the uchicago mirror (presumably). Ignoring this message will mean your installation is always going to fail as the installer won't recognize your disk. Missing installer modules probably means you are using an incorrect distribution on your mirror. You probably need to select 'unstable' instead of using the default 'testing'. You can do this by backing up to the menu (for example from country-chooser), changing debconf priority to medium, and then choose 'unstable' when you are selecting your mirror. The reason is there are kernel-changes happening ATM and the version the floppies are build with is probably not yet available in testing. Cheers, Frans P.S. When are you finally going to start work on the manual? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#270599: Floppy install on Oldworld PowerMac
On Thursday, September 9, 2004, at 12:45 PM, Rick Thomas wrote: On Wednesday, September 8, 2004, at 09:18 AM, Rick Thomas wrote: On Wednesday, September 8, 2004, at 05:18 AM, Sven Luther wrote: Please try again with todays floppies, and if it doesn't fix the problem, we need to investigate what driver is missing or something. I'll try the new floppies tonight. I guess whatever it was is fixed now. Because I was able to download a set of floppies from Index of /~luther/d-i/images/daily/powerpc/floppy-2.4 NameLast modified Size Description Parent Directory26-Aug-2004 21:35 - asian-root.img 10-Sep-2004 05:46 1.2M boot.img10-Sep-2004 05:47 1.4M cd-drivers.img 10-Sep-2004 05:49 1.4M net-drivers.img 10-Sep-2004 05:50 1.4M ofonlyboot.img 10-Sep-2004 05:51 1.4M root-2.img 10-Sep-2004 05:52 1.4M root.img10-Sep-2004 05:53 1.3M Apache/1.3.26 Server at people.debian.org Port 80 The "ofonlyboot" has not changed. It reads and inverts the colors of the tuxmac, but never switches to text-mode screen from the inverted color tuxmac. The boot floppy reads and switches to the text screen then asks for the root floppy, which it reads. It then asks for language (English) and location (US) (but not keyboard layout) then invites me to load drivers from a floppy. I gave it the "root-2" floppy and it complained about not being able to find any kernel drivers on that floppy. I chose and re-executed "load drivers from a floppy". This time I gave it the net-drivers floppy, and it was happy. Still thinking that we wouldn't get any where without the root-2 floppy loading (and being a bit bull headed anyway) I tried "load drivers from floppy" for the third time, and again fed it the root-2. It complained again about not finding any kernel modules. This time I told it to "continue without loading drivers" and to my amazement, it started decoding the stuff from the root-2 floppy! Curioser and curioser! I think it was at this point that it asked for my keyboard layout, and suggested "European" as default, even though I had given it every reason to suspect that US-English was my preferred locale. I've reported this violation of the principle of least astonishment before. It proceeded then to find my ethernet interface (remember I'd loaded the net-drivers floppy earlier) and do DHCP discovery on it. This succeeded, as expected. When it asked, I chose the uchicago mirror as usual, and it loaded the installer-components list (I think -- I didn't get the exact words) after which it *again* complained about not finding any kernel modules! I told it to continue anyway, and it started downloading and unpacking installer components from the uchicago mirror (presumably). When it got done with that and moved on to the partitioner, it couldn't find any of my disks (not my IDE main disk or my SCSI Zip disk). The only IDE think it knew about was the CD-ROM drive. Exploring on the F2 console showed that it wasn't just the partitioner that was confused. There was no evidence of IDE or SCSI disks in /proc or /dev. (Same as last time -- no progress on that front...) So I wrapped it up and took a tea break to write this report. I have to consider the check for kernel modules at inappropriate times to be a serious bug... Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#270599: Floppy install on Oldworld PowerMac
On Thu, Sep 09, 2004 at 12:45:29PM -0400, Rick Thomas wrote: > > On Wednesday, September 8, 2004, at 09:18 AM, Rick Thomas wrote: > > > > >On Wednesday, September 8, 2004, at 05:18 AM, Sven Luther wrote: > > > >> > >>Please try again with todays floppies, > >>and if it doesn't fix the problem, we need to investigate what > >>driver is > >>missing or something. > > > >I'll try the new floppies tonight. > > Ummm... The contents of > > http://people.debian.org/~luther/d-i/images/daily/powerpc/floppy-2.4/ > > haven't changed in the last few days. Is the build process stalled > somewhere? [DIR] 2004-09-08_RSYNC_IN_PROGRESS/ 07-Sep-2004 22:05 - [DIR] 2004-09-09_RSYNC_IN_PROGRESS/ 08-Sep-2004 22:05 - Oh, well, i wonder what went wrong this time, let me look at the logs ... ... and here it is : powerpc/floppy/root-2.img powerpc/floppy/root.img powerpc/netboot/2.4/initrd.gz Read from remote host people.debian.org: Connection reset by peer rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(839) Thu Sep 9 05:27:09 UTC 2004 powerpc/cdrom/2.4/vmlinuz-chrp.initrd powerpc/cdrom/2.4/vmlinuz-prep.initrd Read from remote host people.debian.org: Connection reset by peer rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(839) Wed Sep 8 05:26:40 UTC 2004 Mmm, i wonder what is the problem here, anyone can help me out on this one ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#270599: Floppy install on Oldworld PowerMac
On Wednesday, September 8, 2004, at 09:18 AM, Rick Thomas wrote: On Wednesday, September 8, 2004, at 05:18 AM, Sven Luther wrote: Please try again with todays floppies, and if it doesn't fix the problem, we need to investigate what driver is missing or something. I'll try the new floppies tonight. Ummm... The contents of http://people.debian.org/~luther/d-i/images/daily/powerpc/floppy-2.4/ haven't changed in the last few days. Is the build process stalled somewhere? Thanks! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#270599: Floppy install on Oldworld PowerMac
On Wednesday, September 8, 2004, at 05:18 AM, Sven Luther wrote: On Wed, Sep 08, 2004 at 04:17:55AM -0400, Rick_Thomas wrote: Package: installation-reports powerpc boot-floppy 20040906 OldWorld PowerMac ... Then I tried the "boot" floppy. It gave me the tuxmac and made reading noises. After a while it ejected the boot floppy and switched to a text mode screen at (I think) 640x480 resolution. This is good enough for installing -- but not satisfactory for long term usage. Yes, i guess quik-installer should allow you to use further kernel options. You could create your own miboot floppy, and then you can add the options you want, more on this below. For the time being, just adding "DEBCONF_PRIORITY=medium" to the standard "boot" floppy would be a major good-thing. Frankly, I think that "medium" priority would be acceptable as a default mode for floppy boots. It's nice to minimize user interaction and all, but if I'm going to all the trouble of burning a bunch of floppies, I want a reasonable amount of control over the details of the installation process. I don't think inexperienced users will find the "medium" priority dialogue any more confusing than the existing "woody" installer. Just my opinion -- YMMV, of course. It called for the root floppy, so I fed it that, which it read happily. After reading the root floppy and asking me some questions about languages and locations, it asked if I wanted to read a driver floppy. I said yes and fed it the "root-2" floppy. Well, i fixed the root-2 thingy earlier, so it is nice that it works, even if there is no real support for this in the installer yet. Feel free to participate in the fixing of this, be it only by suggesting what the root-2 asking question should be, and where it should be asked. Ideally we would add a load-second-root-floppy .udeb, which would present a menu and load the second floppy, and which would be part of the first root floppy. A special "load-root-2.udeb" (or whatever) may not be necessary: Just think of everything after the "root" as "extra installer component" floppies (or some such) rather than "driver" floppies specifically. Simply modify the existing dialogue to end with a question "Do you want to load another installer component?" If the answer is "yes" loop back and re-execute. If the answer is "no", make a normal return. The first pass through is mandatory and loads the "root-2" floppy. All subsequent passes are optional, based on what kind of installation you want to do. One thing to be careful of: It will be necessary to craft the wording of the dialogue questions very carefully so that the user understands fully what is going on, and what is required of them, at each step. The root-2 floppy contains stuff (namely netcfg and co) that was spilled out from the first root floppy. That's pretty much what I figured was going on. My choice of "root-2" at this point was based on a hunch. There was no indication of which driver floppy it was expecting (Indeed, it was not clear at all that "root-2" was a "driver" floppy. My hunch was that it would be needed immediately and that the easiest way to add files to the ram-disk root was to emulate a driver floppy.) It would be better to out-and-out say "root-2" if that's what is wanted. Like Joeyh mentioned, right now there is support for loading only one drivers floppy, which may well be buggy in itself, and maybe a question for asking for an additional floppy like asking for additional apt sources later on may be welcome. Also, the root-2 is not really a drivers floppy, but should be loaded earlier on, maybe. I have no problem with answering questions about language and location before loading additional installer components. I'd go ahead and leave it right where it is in the sequence, if that's easiest. It then tried to detect my network interface and failed, so it asked Because the net drivers are not on the floppy. for the network drivers floppy, which I gave it. This time it succeeded in finding my network interface and configured it via DHCP Woaw. I was under the impression that this would fail, from joeyh's comment about only one driver floppy, but this is great. Right. This is what makes me think we can use the existing framework to load an arbitrary number of extra "installer component" floppies. (I would have preferred the option to do this manually, but there is no way to specify "DEBCONF_PRIORITY=medium" in booting an oldworld pmac Like said, if you build your own miboot floppy, you can add any kernel arguments you like. As miboot is non-free, users may be forced to do this anyway, so ... Yuch! Please don't force inexperienced users to build their own "boot" floppy. You'll loose a large class of potential users if you do. machine from floppy.) It asked for a mirror, and I specified the uchicago one since it seems to be fastest and most reliable from my little corner of the Internet. Overcool. Note 2:
Bug#270599: Floppy install on Oldworld PowerMac
On Wed, Sep 08, 2004 at 04:17:55AM -0400, Rick_Thomas wrote: > Package: installation-reports > > powerpc boot-floppy 20040906 OldWorld PowerMac Thanks for testing this. > Note 1: > > The "ofonlyboot" floppy booted and gave me the "tuxmac" icon in the > middle of the screen. After the floppy noises stopped, the screen > inverted colors, but did not switch to text mode. The ofonly boot > floppy ejected. Normally, at this point it's calling for the root > floppy, so I gave it the root floppy and hit . As expected, > it read the root floppy, but the text screen never appeared -- just > the inverted color tuxmac. So it was impossible to proceed further > with the "ofonlyboot" experiment. Mmm. > Then I tried the "boot" floppy. It gave me the tuxmac and made > reading noises. After a while it ejected the boot floppy and switched > to a text mode screen at (I think) 640x480 resolution. This is good > enough for installing -- but not satisfactory for long term usage. Yes, i guess quik-installer should allow you to use further kernel options. You could create your own miboot floppy, and then you can add the options you want, more on this below. > It called for the root floppy, so I fed it that, which it read > happily. After reading the root floppy and asking me some questions > about languages and locations, it asked if I wanted to read a driver > floppy. I said yes and fed it the "root-2" floppy. Well, i fixed the root-2 thingy earlier, so it is nice that it works, even if there is no real support for this in the installer yet. Feel free to participate in the fixing of this, be it only by suggesting what the root-2 asking question should be, and where it should be asked. Ideally we would add a load-second-root-floppy .udeb, which would present a menu and load the second floppy, and which would be part of the first root floppy. The root-2 floppy contains stuff (namely netcfg and co) that was spilled out from the first root floppy. > My choice of "root-2" at this point was based on a hunch. There was > no indication of which driver floppy it was expecting (Indeed, it was > not clear at all that "root-2" was a "driver" floppy. My hunch was > that it would be needed immediately and that the easiest way to add > files to the ram-disk root was to emulate a driver floppy.) It would > be better to out-and-out say "root-2" if that's what is wanted. Like Joeyh mentioned, right now there is support for loading only one drivers floppy, which may well be buggy in itself, and maybe a question for asking for an additional floppy like asking for additional apt sources later on may be welcome. Also, the root-2 is not really a drivers floppy, but should be loaded earlier on, maybe. > It then tried to detect my network interface and failed, so it asked Because the net drivers are not on the floppy. > for the network drivers floppy, which I gave it. This time it > succeeded in finding my network interface and configured it via DHCP Woaw. I was under the impression that this would fail, from joeyh's comment about only one driver floppy, but this is great. > (I would have preferred the option to do this manually, but there is no > way to specify "DEBCONF_PRIORITY=medium" in booting an oldworld pmac Like said, if you build your own miboot floppy, you can add any kernel arguments you like. As miboot is non-free, users may be forced to do this anyway, so ... > machine from floppy.) It asked for a mirror, and I specified the > uchicago one since it seems to be fastest and most reliable from my > little corner of the Internet. Overcool. > Note 2: > > Things proceeded more or less as expected until it came time to > partition the disk. The partitioner could not find any disks to > partition! Switching to the F2 console and poking about, it became > clear that this was *not* just a problem with the partitioner -- the > only ide device present, as far as the kernel was concerned, was the > CD-ROM drive. My IDE disk was nowhere to be found! There was no > "/dev/discs" directory, and there was just the CD-ROM drive in the > /proc/ide directory. Very strange! There have been a few problems with partman lately, starting with the broken no_media handling, and then following with the missing dependency of parted 1.6.11-2, which is fixed in 1.6.11-3. Please try again with todays floppies, and if it doesn't fix the problem, we need to investigate what driver is missing or something. > Final note: > > Throughout this process, except for once when it asked for the "root" > floppy, it never ejected the previous floppy. On a Mac, this means I > have to manually eject the floppy with a bent paperclip. Mac floppy > drives do not have an "eject" button the way PC floppy drives do. > This is annoying to experienced folks, and will be confusing to > inexperienced users. This is indeed a problem, and it may be worth to include the (small) eject .udeb in the first root floppy, and add eject support in the
Bug#270599: Floppy install on Oldworld PowerMac
Package: installation-reports powerpc boot-floppy 20040906 OldWorld PowerMac INSTALL REPORT Debian-installer-version: I got the floppy disk images from: Index of /~luther/d-i/images/daily/powerpc/floppy-2.4 NameLast modified Size Description Parent Directory26-Aug-2004 21:35 - asian-root.img 06-Sep-2004 22:38 1.2M boot.img06-Sep-2004 22:38 1.4M cd-drivers.img 06-Sep-2004 22:39 1.4M net-drivers.img 06-Sep-2004 22:39 1.4M ofonlyboot.img 06-Sep-2004 22:39 1.4M root-2.img 06-Sep-2004 22:41 1.4M root.img06-Sep-2004 22:42 1.3M Apache/1.3.26 Server at people.debian.org Port 80 uname -a: Linux debian 2.6.7-powerpc #1 Thu Aug 5 23:48:59 CEST 2004 ppc GNU/Linux Date: 4 AM (UTC) 2004-09-07 Method: How did you install? boot/root/driver floppies with an assist from the uchicago mirror What did you boot off? boot floppy If network install, from where? debian.uchicago.edu Proxied? No Machine: PowerMac G3/300 MHz Processor: processor : 0 cpu : 740/750 temperature : 36-41 C (uncalibrated) clock : 300MHz revision: 2.2 (pvr 0008 0202) bogomips: 601.29 machine : Power Macintosh motherboard : AAPL,Gossamer MacRISC detected as : 48 (PowerMac G3 (Gossamer)) pmac flags : L2 cache: 1024K unified pipelined-syncro-burst memory : 384MB pmac-generation : OldWorld Memory: 384 MB Root Device: Didn't get that far Root Size/partition table: Feel free to paste the full partition table, with notes on which partitions are mounted where. Output of lspci and lspci -n: :00:00.0 Host bridge: Motorola MPC106 [Grackle] (rev 40) :00:0d.0 Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 10) :00:0e.0 SCSI storage controller: Artop Electronic Corp ATP865 (rev 06) :00:0f.0 PCI bridge: Hint Corp HB6 Universal PCI-PCI bridge (non-transparent mode) (rev 13) :00:10.0 ff00: Apple Computer Inc. Heathrow Mac I/O (rev 01) :00:12.0 VGA compatible controller: ATI Technologies Inc 3D Rage I/II 215GT [Mach64 GT] (rev 9a) :01:08.0 USB Controller: NEC Corporation USB (rev 41) :01:08.1 USB Controller: NEC Corporation USB (rev 41) :01:08.2 USB Controller: NEC Corporation USB 2.0 (rev 02) :01:0b.0 FireWire (IEEE 1394): Texas Instruments TSB12LV26 IEEE-1394 Controller (Link) :00:00.0 0600: 1057:0002 (rev 40) :00:0d.0 0200: 1186:1300 (rev 10) :00:0e.0 0100: 1191:0009 (rev 06) :00:0f.0 0604: 3388:0021 (rev 13) :00:10.0 ff00: 106b:0010 (rev 01) :00:12.0 0300: 1002:4754 (rev 9a) :01:08.0 0c03: 1033:0035 (rev 41) :01:08.1 0c03: 1033:0035 (rev 41) :01:08.2 0c03: 1033:00e0 (rev 02) :01:0b.0 0c00: 104c:8020 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[?] Note 1 Configure network HW: [o] Config network: [o] Detect CD: [ ] Load installer modules: [o] Detect hard drives: [e] Note 2 Partition hard drives: [?] Create file systems:[ ] Mount partitions: [ ] Install base system:[ ] Install boot loader:[ ] Reboot: [ ] Comments/Problems: Note 1: The "ofonlyboot" floppy booted and gave me the "tuxmac" icon in the middle of the screen. After the floppy noises stopped, the screen inverted colors, but did not switch to text mode. The ofonly boot floppy ejected. Normally, at this point it's calling for the root floppy, so I gave it the root floppy and hit . As expected, it read the root floppy, but the text screen never appeared -- just the inverted color tuxmac. So it was impossible to proceed further with the "ofonlyboot" experiment. Then I tried the "boot" floppy. It gave me the tuxmac and made reading noises. After a while it ejected the boot floppy and switched to a text mode screen at (I think) 640x480 resolution. This is good enough for installing -- but not satisfactory for long term usage. It called for the root floppy, so I fed it that, which it read happily. After reading the root floppy and asking me some questions about languages and locations, it asked if I wanted to read a driver floppy. I said yes and fed it the "root-2" floppy. My choice of "root-2" at this point was based on a hunch. There was no indication of which driver floppy it was expecting (Indeed, it was not clear at all that "root-2" was a "driver" floppy. My hunch was that it would b
