Package: installation-reports
Boot method: Network
Image version: (Downloaded at 20061229)
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso
Date: Dec 30, 2006
Machine: Home built system, based on an Asus P5B-V motherboard.
Processor: I
Op 01-01-2007 om 18:07 schreef Geert-Jan Hut:
> lspci -vnn =
> 04:03.0 0c00: 1106:3044 (rev c0) (prog-if 10)
> Subsystem: 1043:81fe
> Flags: bus master, medium devsel, latency 64, IRQ 50
> Memory at ff7ff800 (32-bit, no
On Monday 01 January 2007 21:57, Geert Stappers wrote:
>
> Please provide the output of
>
> lspci -s 04:04.0 -vnn
My version of lspci doesn't provide much descriptive text with the -n option,
so I included both options, with and without the -n option (and more debug
info with -vv) .
[EMAIL P
On Monday 01 January 2007 18:07, Geert-Jan Hut wrote:
> It looks like the installer someway messes up the network hardware
> during detection, after which it isn't functional anymore. A simple
> reboot doesn't solve the problem, only using software that also sets
> this network configuration makes
On Wednesday 03 January 2007 00:24, Frans Pop wrote:
>
> I suggest that you check the output of dmesg and the contents
> of /var/log/syslog (using 'nano') after switching to VT2 to see if that
> shows any reason that the driver is not working.
A warning appears in the log:
Warning **: MII ioctl f
reassign 405196 linux-2.6
retitle 405196 Two drivers listed for [11ab:4320] causing driver conflict
thanks
On Wednesday 03 January 2007 23:38, Geert-Jan Hut wrote:
> > The modules.pcimap for 2.6.18 shows two drivers for your ethernet
> > card: skge and sk98lin. This is unusual.
> > You can also tr
6 matches
Mail list logo
