[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#492878: lenny installer -dosen't detect Broadcom ethernet adapter



I type here just what is going on for bnx2 and I will not put here messages for another hw that needs firmwaremessages, qla2xxx


11:04:56 kernel: Broadcom Nextreme II Gigabit Ethernet Driver bnx2 v1.7.4 (Feburary 18, 2008)
11:04:56 kernel: bnx2: Can't load firmware file bnx2-06-4.0.5.fw
11:04:56 kernel: bnx2: probe of 0000:02:03.0 failed with error -2
11:04:56 kernel: bnx2: Can't load firmware file bnx2-06-4.0.5.fw
11:04:56 kernel: bnx2: probe of 0000:02:04.0

11:06:13 check-missing-firmware: missing firmware files (ql2400_fw.bin bnx2-06-4.0.5.fw) for qlaxxx bnx2 11:13:50 kernel: FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
(repeated cca 10x in the same second)

here the show begins:
11:13:51 main-menu[1481]: (process:5851): mount: mounting /dev/sda on /media failed: Invalid argument

the same for sdb, sdc

then FAT comply 3x again, and then it tryes to mount cciss/c0d0p2 (the internal HP raid E200) and fails with "attempt to access beyond end of device"

then FAT again ...

another attempts to mount all the backage found in /dev...

It seems for me, that it simply fails to mount the USB pendrive. Anyhow, the partition of course resides on /dev/sda1, not on /dev/sda! So I don't wonder it fails.


Peter



(Please keep the bug CC'ed)

On Wed, Jul 30, 2008 at 09:30:40AM +0200, Peter Tuhársky wrote:
The installer should at least prompted you to supply a .fw firmware file.
Did it do this?
Well, I tested daily build from 20080729, and yes, the installer prompts for these files. However, I can't figure out, how could I give it to him. I have put them on the root of usb pendrive, they are exactly the files that he needs, and it still asks for them again and again.

Could you look closely at the syslog (Alt+F4, or Alt+F2 and
/var/log/syslog) for firmware related issues?

You can also edit (using nano) /bin/check-missing-firmware and add a
"set -x" at the beginning of the script.  This will trace its execution
in the syslog.

Cheers,



Reply to: