Bug#580265: Failed netinst

2010-05-05 Thread Notifier
On Wed, May 5, 2010 at 10:41 AM, Frans Pop elen...@planet.nl wrote:
 reassign 580265 linux-2.6 2.6.32-9
 thanks

 On Tuesday 04 May 2010, Gmail Notifier wrote:
 00:19.0 Ethernet controller [0200]: Intel Corporation 82578DC Gigabit
 Network Connection [8086:10f0] (rev 06)
 Subsystem: Intel Corporation Device [8086:0037]
 Kernel driver in use: e1000e

 Comments/Problems:

 Did not find my e1000e network interface, even after selecting it
 explicitly from the list. After installing without using a net
 connection, a simple modprobe e1000e and dhclient made the net
 connection work. The following were added automaticly to /etc/modules
 by the installation:

 e100
 e1000
 e1000e

 But booting with these in /etc/modules did not make the network
 interface work. Had to do modprobe e1000e manually after each boot.

 This sounds like a kernel issue. Reassigning to the kernel team.

 Cheers,
 FJP


I have a correction to make, it was only the DHCP part that didn't
work when booting into the installed kernel. The e1000e driver is
loaded correctly, and the other (incorrect) drivers can't be seen when
doing lsmod. The detection in the installation is still broken
though.

If it's any help, the installed kernel is 2.6.32-trunk-amd64, and the
one used on the USB key is 2.6.30-2-amd64. The network also worked
fine with the installed kernel being 2.6.32-3-amd64. I remember
reading that Linus and Molnar had problems with this driver in one of
the latest kernels, maybe updating the USB key kernel would fix it.

When making the USB key I used the boot.img.gz from
http://ftp.nl.debian.org/debian/dists/testing/main/installer-amd64/current/images/hd-media/
and the netinstall image
http://cdimage.debian.org/cdimage/squeeze_di_alpha1/amd64/iso-cd/debian-testing-amd64-netinst.iso



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#580265: Failed netinst

2010-05-05 Thread Notifier
On Wed, May 5, 2010 at 12:12 PM, Notifier notif...@gmail.com wrote:
 On Wed, May 5, 2010 at 10:41 AM, Frans Pop elen...@planet.nl wrote:
 reassign 580265 linux-2.6 2.6.32-9
 thanks

 On Tuesday 04 May 2010, Gmail Notifier wrote:
 00:19.0 Ethernet controller [0200]: Intel Corporation 82578DC Gigabit
 Network Connection [8086:10f0] (rev 06)
         Subsystem: Intel Corporation Device [8086:0037]
         Kernel driver in use: e1000e

 Comments/Problems:

 Did not find my e1000e network interface, even after selecting it
 explicitly from the list. After installing without using a net
 connection, a simple modprobe e1000e and dhclient made the net
 connection work. The following were added automaticly to /etc/modules
 by the installation:

 e100
 e1000
 e1000e

 But booting with these in /etc/modules did not make the network
 interface work. Had to do modprobe e1000e manually after each boot.

 This sounds like a kernel issue. Reassigning to the kernel team.

 Cheers,
 FJP


 I have a correction to make, it was only the DHCP part that didn't
 work when booting into the installed kernel. The e1000e driver is
 loaded correctly, and the other (incorrect) drivers can't be seen when
 doing lsmod. The detection in the installation is still broken
 though.

 If it's any help, the installed kernel is 2.6.32-trunk-amd64, and the
 one used on the USB key is 2.6.30-2-amd64. The network also worked
 fine with the installed kernel being 2.6.32-3-amd64. I remember
 reading that Linus and Molnar had problems with this driver in one of
 the latest kernels, maybe updating the USB key kernel would fix it.

 When making the USB key I used the boot.img.gz from
 http://ftp.nl.debian.org/debian/dists/testing/main/installer-amd64/current/images/hd-media/
 and the netinstall image
 http://cdimage.debian.org/cdimage/squeeze_di_alpha1/amd64/iso-cd/debian-testing-amd64-netinst.iso


Another followup: I tried the daily build of the netinst with the
daily USB stick image, and the hardware detection worked, so this can
probably be closed. Maybe add this to the errata.



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#580265: Failed netinst

2010-05-04 Thread Gmail Notifier
Package: installation-reports

Boot method: USB stick
Image version: 
http://cdimage.debian.org/cdimage/squeeze_di_alpha1/amd64/iso-cd/debian-testing-amd64-netinst.iso
Date: May 4th 2010

Machine: Intel DH55HC Mainboard
Processor: i5-750
Memory: DDR3-10666
Partitions:

/dev/mapper/debian-root
  ext373506040   2268184  67503944   4% /
tmpfstmpfs  996064 0996064   0% /lib/init/rw
udev tmpfs   10240   140 10100   2% /dev
tmpfstmpfs  996064 0996064   0% /dev/shm
/dev/sda1 ext2  25 39443181444  18% /boot

Output of lspci -knn:

00:00.0 Host bridge [0600]: Intel Corporation Core Processor DMI
[8086:d131] (rev 11)
Subsystem: Intel Corporation Device [8086:0037]
00:03.0 PCI bridge [0604]: Intel Corporation Core Processor PCI
Express Root Port 1 [8086:d138] (rev 11)
Kernel driver in use: pcieport
00:08.0 System peripheral [0880]: Intel Corporation Core Processor
System Management Registers [8086:d155] (rev 11)
Subsystem: Device [0086:0037]
00:08.1 System peripheral [0880]: Intel Corporation Core Processor
Semaphore and Scratchpad Registers [8086:d156] (rev 11)
Subsystem: Device [0086:0037]
00:08.2 System peripheral [0880]: Intel Corporation Core Processor
System Control and Status Registers [8086:d157] (rev 11)
Subsystem: Device [0086:0037]
00:08.3 System peripheral [0880]: Intel Corporation Core Processor
Miscellaneous Registers [8086:d158] (rev 11)
Subsystem: Device [0086:0037]
00:10.0 System peripheral [0880]: Intel Corporation Core Processor QPI
Link [8086:d150] (rev 11)
Subsystem: Device [0086:0037]
00:10.1 System peripheral [0880]: Intel Corporation Core Processor QPI
Routing and Protocol Registers [8086:d151] (rev 11)
Subsystem: Device [0086:0037]
00:16.0 Communication controller [0780]: Intel Corporation 5
Series/3400 Series Chipset HECI Controller [8086:3b64] (rev 06)
Subsystem: Intel Corporation Device [8086:0037]
00:16.2 IDE interface [0101]: Intel Corporation 5 Series/3400 Series
Chipset PT IDER Controller [8086:3b66] (rev 06)
Subsystem: Intel Corporation Device [8086:0037]
00:16.3 Serial controller [0700]: Intel Corporation 5 Series/3400
Series Chipset KT Controller [8086:3b67] (rev 06)
Subsystem: Intel Corporation Device [8086:0037]
Kernel driver in use: serial
00:19.0 Ethernet controller [0200]: Intel Corporation 82578DC Gigabit
Network Connection [8086:10f0] (rev 06)
Subsystem: Intel Corporation Device [8086:0037]
Kernel driver in use: e1000e
00:1a.0 USB Controller [0c03]: Intel Corporation 5 Series/3400 Series
Chipset USB2 Enhanced Host Controller [8086:3b3c] (rev 06)
Subsystem: Intel Corporation Device [8086:0037]
Kernel driver in use: ehci_hcd
00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series
Chipset High Definition Audio [8086:3b56] (rev 06)
Subsystem: Intel Corporation Device [8086:0037]
Kernel driver in use: HDA Intel
00:1c.0 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series
Chipset PCI Express Root Port 1 [8086:3b42] (rev 06)
Kernel driver in use: pcieport
00:1c.4 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series
Chipset PCI Express Root Port 5 [8086:3b4a] (rev 06)
Kernel driver in use: pcieport
00:1d.0 USB Controller [0c03]: Intel Corporation 5 Series/3400 Series
Chipset USB2 Enhanced Host Controller [8086:3b34] (rev 06)
Subsystem: Intel Corporation Device [8086:0037]
Kernel driver in use: ehci_hcd
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge
[8086:244e] (rev a6)
00:1f.0 ISA bridge [0601]: Intel Corporation 5 Series Chipset LPC
Interface Controller [8086:3b06] (rev 06)
Subsystem: Intel Corporation Device [8086:0037]
00:1f.2 IDE interface [0101]: Intel Corporation 5 Series/3400 Series
Chipset 4 port SATA IDE Controller [8086:3b20] (rev 06)
Subsystem: Intel Corporation Device [8086:0037]
Kernel driver in use: ata_piix
00:1f.3 SMBus [0c05]: Intel Corporation 5 Series/3400 Series Chipset
SMBus Controller [8086:3b30] (rev 06)
Subsystem: Intel Corporation Device [8086:0037]
Kernel driver in use: i801_smbus
00:1f.5 IDE interface [0101]: Intel Corporation 5 Series/3400 Series
Chipset 2 port SATA IDE Controller [8086:3b26] (rev 06)
Subsystem: Intel Corporation Device [8086:0037]
Kernel driver in use: ata_piix
01:00.0 VGA compatible controller [0300]: nVidia Corporation GT218
[GeForce 210] [10de:0a65] (rev a2)
Subsystem: CardExpert Technology Device [10b0:1401]
01:00.1 Audio device [0403]: nVidia Corporation High Definition Audio
Controller [10de:0be3] (rev a1)
Subsystem: CardExpert Technology Device [10b0:1401]



Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:    [E]
Configure network:  [ ]

Bug#459889: Re

2009-04-06 Thread WINNERS ONLINE NOTIFIER
You Won 1.350,000Pounds Name,Age,Country.

Email:stevenmarkclaimsu...@btinternet.com




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#420238: text

2008-01-04 Thread Email Firewall Notifier
===
METLIFE SYSTEM GENERATED MESSAGE:

When this e-mail was received by MetLife, one or more of these
attachment(s): symantec.gif, text_lior.hefer.zip was found to be a
potential threat to MetLife's computer systems and therefore deleted.

If you deem this to be a necessary and valid business attachment, please
contact the AEMC Help Desk for instructions for receiving executable
type attachments.  

The AEMC Help Desk can be reached by MetLife International customers at:
-  +603-831-80449 for English language service
-   004422601228 for Japanese language service
-   or by E-mail at [EMAIL PROTECTED]

Very often, e-mails of this type are sent by virus infected computers.
If you were not expecting this e-mail from the sender, or the file name
looks suspicious, you should just delete this e-mail and not respond to
the sender.
===


Bug#99324: Delivery Failure Report

2007-07-22 Thread undeliver-notifier
Delivery Failure Report

Your message

Subject: Re: Hi

was not delivered to: [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED] because:

User [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED] not listed in Address Book

DO NOT REPLY TO THIS MESSAGE