Bug in 3.0.17 images (i386)
Hello,
I noticed a bug in the 3.0.17 (i386) floppy images (flavour=udma100-ext3, 1,44 images).
The complete description is:
vga=normal noinitrd load_ramdisk=1 prompt_ramdisk=1 ramdisk_size=16384 root=/dev/fd0
disksize=1.44 flavor=udma100-ext3 BOOT_IMAGE=linux
"version" shows this:
Linux version 2.2.19-udma100-ext3 (inet@zombie) (gcc version 2.95.4 20011006 (Debian
prerelease)) #1 SMP Sat Oct 20 18:53:37 CEST 2001
"messages" contains this:
(strange ?!)
Nov 16 21:04:09 (none) syslog.info syslogd started: BusyBox v0.60.2.pre
(2001.10.19-06:33+0000)
Nov 16 21:04:44 (none) user.debug dbootstrap[53]: umount: /dev/fd0: No such file or
directory
Nov 16 21:04:44 (none) user.debug dbootstrap[53]: umount: /floppy: Invalid argument
Nov 16 21:04:44 (none) user.err dbootstrap[53]: I will write a report to /dev/fd0. Please
insert a floppy.
Nov 16 21:04:46 (none) user.debug dbootstrap[53]: mount: Mounting /dev/fd0 on /floppy
failed: No such device
Nov 16 21:04:47 (none) user.debug dbootstrap[53]: mount: Mounting /dev/fd0 on /floppy
failed: Invalid argument
Nov 16 21:04:47 (none) user.debug dbootstrap[53]: mount: Mounting /dev/fd0 on /floppy
failed: No such device
Nov 16 21:04:47 (none) user.debug dbootstrap[53]: mount: Mounting /dev/fd0 on /floppy
failed: Invalid argument
Nov 16 21:04:47 (none) user.debug dbootstrap[53]: mount: Mounting /dev/fd0 on /floppy
failed: Invalid argument
Nov 16 21:04:57 (none) user.debug dbootstrap[53]: mount: Mounting /dev/fd0 on /floppy
failed: No such device
Nov 16 21:04:57 (none) user.debug dbootstrap[53]: mount: Mounting /dev/fd0 on /floppy
failed: Invalid argument
Nov 16 21:04:57 (none) user.debug dbootstrap[53]: mount: Mounting /dev/fd0 on /floppy
failed: No such device
Nov 16 21:04:58 (none) user.debug dbootstrap[53]: mount: Mounting /dev/fd0 on /floppy
failed: Invalid argument
I booted from the rescue disk, then inserted the root disk and that was just normal, but
when the "Configure Network" task came up, it showed me 2 devices: eth0 and eth1...I only
have one ethernet card (rtl8139) and choose eth0...But when I finished configuring it, the
installer told me that I have to configure my network before I can install vie ftp/http.
Then I chose eth1 and it worked...For some reason, it shows me 2 eth devices and eth1
seems to work and 0 is a dummy or so...(Installation went on correctly, so there was just
a device shown which isn't there and not a real "problem") That wasn't with 3.0.15...I did
"Report a problem"
and saved the logs onto a floppy and I have them here now but the only thing of interest
is the pci thing:
-------
PCI devices found:
Bus 0, device 0, function 0:
Host bridge: VIA Technologies Unknown device (rev 3).
Vendor id=1106. Device id=305.
Medium devsel. Master Capable. Latency=8.
Prefetchable 32 bit memory at 0xe8000000 [0xe8000008].
Bus 0, device 1, function 0:
PCI bridge: VIA Technologies Unknown device (rev 0).
Vendor id=1106. Device id=8305.
Medium devsel. Master Capable. No bursts. Min Gnt=12.
Bus 0, device 7, function 0:
ISA bridge: VIA Technologies VT 82C686 Apollo Super (rev 64).
Medium devsel. Master Capable. No bursts.
Bus 0, device 7, function 1:
IDE interface: VIA Technologies VT 82C586 Apollo IDE (rev 6).
Medium devsel. Fast back-to-back capable. Master Capable. Latency=32.
I/O at 0xd000 [0xd001].
Bus 0, device 7, function 2:
USB Controller: VIA Technologies VT 82C586 Apollo USB (rev 22).
Medium devsel. IRQ 11. Master Capable. Latency=32.
I/O at 0xd400 [0xd401].
Bus 0, device 7, function 3:
USB Controller: VIA Technologies VT 82C586 Apollo USB (rev 22).
Medium devsel. IRQ 11. Master Capable. Latency=32.
I/O at 0xd800 [0xd801].
Bus 0, device 7, function 4:
Bridge: VIA Technologies VT 82C686 Apollo Super ACPI (rev 64).
Medium devsel. Fast back-to-back capable.
Bus 0, device 8, function 0:
Ethernet controller: Realtek 8139 (rev 16).
Medium devsel. Fast back-to-back capable. IRQ 11. Master Capable. Latency=32.
Min Gnt=32.Max Lat=64.
I/O at 0xdc00 [0xdc01].
Non-prefetchable 32 bit memory at 0xee000000 [0xee000000].
Bus 0, device 15, function 0:
Multimedia audio controller: Unknown vendor Unknown device (rev 8).
Vendor id=1102. Device id=2.
Medium devsel. Fast back-to-back capable. IRQ 5. Master Capable. Latency=32.
Min Gnt=2.Max Lat=20.
I/O at 0xe000 [0xe001].
Bus 0, device 15, function 1:
Input device controller: Unknown vendor Unknown device (rev 8).
Vendor id=1102. Device id=7002.
Medium devsel. Fast back-to-back capable. Master Capable. Latency=32.
I/O at 0xe400 [0xe401].
Bus 1, device 0, function 0:
VGA compatible controller: NVidia Unknown device (rev 161).
Vendor id=10de. Device id=110.
Medium devsel. Fast back-to-back capable. IRQ 10. Master Capable. Latency=32.
Min Gnt=5.Max Lat=1.
Non-prefetchable 32 bit memory at 0xec000000 [0xec000000].
Prefetchable 32 bit memory at 0xe0000000 [0xe0000008].
--------
The boot messages were the same as with 3.0.15 and for my realtek8139 the rtl8139 was
loaded automatically...I just don't know why it shows me 2 eth devices...
Hope this helps and sorry for my newbieish description I am quite new to Linux.
btw: I downloaded them from
http://people.debian.org/~aph/debian/dists/woody/main/disks-i386/3.0.17-2001-11-13/images-
1.44/udma100-ext3/
and checked the md5sums and all were right.
Rainer
PS: Please CC me I am not subscribed to the list
Reply to: