Re: Install report
On Thursday 16 October 2003 13:28, Joey Hess wrote:
> > When "detecting network hardware and installing modules for it" I do not
> > consistently get warned that not all the modules are available. For
> > example my machine had a pcnet32 card and an 8139too, it loads the
> > 8139too but doesn't warn that the pcnet32 is unavailable. I did see the
> > warning on one of many runs through, just do not get the warnings
> > consistently.
>
> I'd appreciate more information about this. Either discover is not
> always noticing your pcnet32, or there is a logic error causing it to
> fail to display a note when it does find the card. Given the
> intermittancy, I'd bet on discover. Note that the pcnet32 is not
> supported by the 2 floppy set, you have to load the net drivers floppy
> to get its driver.
I performed 2-3 installs, only the final one was complete. From my
recollection, I was never warned that the pcnet32 module was unavailable
except during the first install attempt when I ran the network detection a
second time. It was late and my memory may be faulty so, if you'd like, I can
do the install again and take better notes on this part.
> What you could do is boot up and repeatedly run discover on the seconf
> tty, and see if it consitently finds your pcnet32. The command line it
> uses to run discover is:
>
> discover --format="%m:%V %M\n" \
> --disable-all --enable=pci,ide,scsi,pcmcia scsi cdrom ethernet
>
> If discover is consistently finding the card, a copy of the syslog would
> be a handy thing to have. You should already have the syslog from your
> successful install in /var/lib/messages/installer.log on the final
> system. (I think that's the name).
Ran discover in loop (500 times) and it consistently found the card. Output
from discover is as follows:
pcnet32:Advanced Micro Devices [AMD] 79c970 [PCnet LANCE]
8139too:Realtek Semiconductor Co., Ltd. RTL-8139
I do still have syslog output in /var/log/debian-installer/syslog, here's the part
that I think might be relevant:
Oct 16 03:44:06 (none) user.debug frontend: <-- 0 Detect network hardware and load kernel drivers for it
Oct 16 03:44:06 (none) user.debug frontend: --> METAGET debian-installer/languagechooser/title Description-en.UTF-8
Oct 16 03:44:06 (none) user.debug frontend: <-- 0 Choose language
Oct 16 03:44:06 (none) user.debug frontend: --> METAGET debian-installer/ethdetect/title Description-en.UTF-8
Oct 16 03:44:06 (none) user.debug frontend: <-- 0 Detect network hardware and load kernel drivers for it
Oct 16 03:44:06 (none) user.debug main-menu[191]: DEBUG: Menu item 'ethdetect' selected
Oct 16 03:44:06 (none) user.debug frontend: --> SETTITLE debian-installer/ethdetect/title
Oct 16 03:44:06 (none) user.debug frontend: <-- 0 OK
Oct 16 03:44:06 (none) user.debug main-menu[191]: DEBUG: configure ethdetect, status: 2
Oct 16 03:44:06 (none) user.debug main-menu[191]: DEBUG: configure hw-detect, status: 2
Oct 16 03:44:06 (none) user.debug main-menu[191]: DEBUG: configure modutils-basic, status: 0
Oct 16 03:44:06 (none) user.debug main-menu[191]: DEBUG: configure discover-udeb, status: 2
Oct 16 03:44:06 (none) user.debug main-menu[191]: DEBUG: configure libc6, status: 0
Oct 16 03:44:07 (none) user.debug main-menu[191]: DEBUG: configure discover-data-udeb, status: 2
Oct 16 03:44:07 (none) user.debug frontend: --> SETTITLE ethdetect/title
Oct 16 03:44:07 (none) user.debug frontend: <-- 0 OK
Oct 16 03:44:07 (none) user.debug frontend: --> INPUT low ethdetect/detection_type
Oct 16 03:44:07 (none) user.debug frontend: <-- 30 question skipped
Oct 16 03:44:07 (none) user.debug frontend: --> GO
Oct 16 03:44:07 (none) user.debug frontend: <-- 0 ok
Oct 16 03:44:07 (none) user.debug frontend: --> GET ethdetect/detection_type
Oct 16 03:44:07 (none) user.debug frontend: <-- 0 true
Oct 16 03:44:07 (none) user.notice hw-detect: Detecting hardware...
Oct 16 03:44:07 (none) user.debug frontend: --> SETTITLE hw-detect/title
Oct 16 03:44:07 (none) user.debug frontend: <-- 0 OK
Oct 16 03:44:07 (none) user.debug frontend: --> PROGRESS START 0 9 hw-detect/progress_title
Oct 16 03:44:07 (none) user.debug frontend: <-- 0 OK
Oct 16 03:44:08 (none) user.notice hw-detect: Detected load module 'floppy' for 'Linux Floppy Driver'
Oct 16 03:44:08 (none) user.debug frontend: --> SUBST hw-detect/progress_step CARDNAME Linux Floppy Driver
Oct 16 03:44:08 (none) user.debug frontend: Adding [CARDNAME] -> [Linux Floppy Driver]
Oct 16 03:44:08 (none) user.debug frontend: <-- 0
Oct 16 03:44:08 (none) user.debug frontend: --> SUBST hw-detect/progress_step MODULE floppy
Oct 16 03:44:08 (none) user.debug frontend: Adding [MODULE] -> [floppy]
Oct 16 03:44:08 (none) user.debug frontend: <-- 0
Oct 16 03:44:08 (none) user.debug frontend: --> PROGRESS INFO hw-detect/progress_step
Oct 16 03:44:08 (none) user.debug frontend: <-- 0 OK
Oct 16 03:44:08 (none) user.debug frontend: --> PROGRESS STEP 1
Oct 16 03:44:08 (none) user.debug frontend: <-- 0 OK
Oct 16 03:44:08 (none) user.notice hw-detect: Detected load module 'pcnet32' for 'Advanced Micro Devices [AMD] 79c970 [PCnet LANCE]'
Oct 16 03:44:08 (none) user.debug frontend: --> SUBST hw-detect/progress_step CARDNAME Advanced Micro Devices [AMD] 79c970 [PCnet LANCE]
Oct 16 03:44:08 (none) user.debug frontend: Adding [CARDNAME] -> [Advanced Micro Devices [AMD] 79c970 [PCnet LANCE]]
Oct 16 03:44:08 (none) user.debug frontend: <-- 0
Oct 16 03:44:08 (none) user.debug frontend: --> SUBST hw-detect/progress_step MODULE pcnet32
Oct 16 03:44:08 (none) user.debug frontend: Adding [MODULE] -> [pcnet32]
Oct 16 03:44:08 (none) user.debug frontend: <-- 0
Oct 16 03:44:08 (none) user.debug frontend: --> PROGRESS INFO hw-detect/progress_step
Oct 16 03:44:08 (none) user.debug frontend: <-- 0 OK
Oct 16 03:44:08 (none) user.notice hw-detect: Trying to load module 'pcnet32'
Oct 16 03:44:08 (none) user.notice hw-detect: Could not locate driver 'pcnet32' for 'Advanced Micro Devices [AMD] 79c970 [PCnet LANCE]'.
Oct 16 03:44:08 (none) user.debug frontend: --> FSET hw-detect/not_included seen false
Oct 16 03:44:08 (none) user.debug frontend: <-- 0 false
Oct 16 03:44:08 (none) user.debug frontend: --> SUBST hw-detect/not_included CARDNAME Advanced Micro Devices [AMD] 79c970 [PCnet LANCE]
Oct 16 03:44:08 (none) user.debug frontend: Adding [CARDNAME] -> [Advanced Micro Devices [AMD] 79c970 [PCnet LANCE]]
Oct 16 03:44:08 (none) user.debug frontend: <-- 0
Oct 16 03:44:08 (none) user.debug frontend: --> SUBST hw-detect/not_included MODULE pcnet32
Oct 16 03:44:08 (none) user.debug frontend: Adding [MODULE] -> [pcnet32]
Oct 16 03:44:08 (none) user.debug frontend: <-- 0
Oct 16 03:44:08 (none) user.debug frontend: --> INPUT low hw-detect/not_included
Oct 16 03:44:08 (none) user.debug frontend: <-- 30 question skipped
Oct 16 03:44:08 (none) user.debug frontend: --> GO
Oct 16 03:44:08 (none) user.debug frontend: <-- 0 ok
Oct 16 03:44:08 (none) user.debug frontend: --> PROGRESS STEP 1
Oct 16 03:44:08 (none) user.debug frontend: <-- 0 OK
Oct 16 03:44:08 (none) user.notice hw-detect: Detected load module '8139too' for 'Realtek Semiconductor Co., Ltd. RTL-8139'
Oct 16 03:44:08 (none) user.debug frontend: --> SUBST hw-detect/progress_step CARDNAME Realtek Semiconductor Co., Ltd. RTL-8139
Oct 16 03:44:08 (none) user.debug frontend: Adding [CARDNAME] -> [Realtek Semiconductor Co., Ltd. RTL-8139]
Oct 16 03:44:08 (none) user.debug frontend: <-- 0
Oct 16 03:44:08 (none) user.debug frontend: --> SUBST hw-detect/progress_step MODULE 8139too
Oct 16 03:44:08 (none) user.debug frontend: Adding [MODULE] -> [8139too]
Oct 16 03:44:08 (none) user.debug frontend: <-- 0
Oct 16 03:44:08 (none) user.debug frontend: --> PROGRESS INFO hw-detect/progress_step
Oct 16 03:44:08 (none) user.debug frontend: <-- 0 OK
Oct 16 03:44:08 (none) user.notice hw-detect: Trying to load module '8139too'
Oct 16 03:44:08 (none) user.debug frontend: --> SUBST hw-detect/module_params MODULE 8139too
Oct 16 03:44:08 (none) user.debug frontend: Adding [MODULE] -> [8139too]
Oct 16 03:44:08 (none) user.debug frontend: <-- 0
Oct 16 03:44:08 (none) user.debug frontend: --> INPUT low hw-detect/module_params
Oct 16 03:44:08 (none) user.debug frontend: <-- 30 question skipped
Oct 16 03:44:08 (none) user.debug frontend: --> GO
Oct 16 03:44:08 (none) user.debug frontend: <-- 0 ok
Oct 16 03:44:08 (none) user.debug frontend: --> GET hw-detect/module_params
Oct 16 03:44:08 (none) user.debug frontend: <-- 0
Oct 16 03:44:08 (none) syslog.info klogd: 8139too Fast Ethernet driver 0.9.26
Oct 16 03:44:08 (none) syslog.info klogd: eth0: RealTek RTL8139 Fast Ethernet at 0xc2860000, 00:00:e8:67:f7:da, IRQ 11
Oct 16 03:44:08 (none) syslog.debug klogd: eth0: Identified 8139 chip type 'RTL-8139A'
Oct 16 03:44:08 (none) user.debug frontend: --> PROGRESS STEP 1
Oct 16 03:44:08 (none) user.debug frontend: <-- 0 OK
If you'd like to see all the logging output I've compressed the contents of
/var/log/debian-installer/ and put it at
http://www.wehave.net/debian/debian-installer-fraser-2003-10-15.tar.bz2
> > When first trying to partition harddrive nothing seemed to be happening,
> > pressing enter moved the screen up a line but didn't wake anything up.
> > After 2-3 minutes I pressed CTRL-C. I had done the full hardware
> > detection prior to trying this and had confirmed that the disk was
> > detected ... at least /proc/ide/hda/ existed. After cancelling the first
> > try I immediately went back in to partitioning my disk was listed as
> > available.
>
> I have filed a bug report on this. The syslog would probably be useful
> here too. It would be good to know if you can reproduce it. It would
I can reproduce it, I did at least two installs and had the same behaviour on each.
> also be good if you could try a daily build with hw-detect 0.46 on it,
> this has some fixes for IDE drives, though it might not apply to yours.
Are there prebuilt floppies I can use for that? I tried building the installer myself
but it seemed to want to install some udebs that conflicted with packages on my
host system. If you can point me to a download location for these images I'll give
them a try.
> > Progress bar does not move when downloading packages file. Again my
> > screen goes blank, on tty2 I can see that debootstrap is running though
> > so I wait ... eventually a progress bar does reappear. Package retrieval
> > froze at mawk, no progress seemed to be happening, I killed a few wget
> > and debootstrap processes until I got back to the main menu and then
> > restarted base system install. Second try got past mawk without
> > incident, odd but didn't feel like debugging that one too much. Packages
> > installed, didn't have much trouble then until the bootloader.
>
> Hmm, what kind of network uplink do you have? Packages file should
> download quite quickly, and it's hard to segment it to give progress. I
> am on dialup and it still downloads quickly. The hang you experienced
> also rather points to a network problem.
I have a pretty good connection (DSL, downloads typically peak at 183KB/sec).
I'm not too worried about this one, on future installs if a similar problem crops
up I'll try to track it down a little better.
> Thanks for your report, it was very useful, and great to hear that the
> two floppy install actually works for someone again!
No problem, unfortunately I don't have the time to get my hands dirty and work
on the installer but I'd be happy to continue doing some test installs if it helps.
--
Fraser Campbell <fraser@wehave.net> http://www.wehave.net/
Halton Hills, Ontario, Canada Debian GNU/Linux
Reply to: