Bug#514826: installation-report: Unable to boot with /boot on LVM and lilo

2009-02-11 Thread Daniel Dehennin
Package: installation-reports
Version: 2.38
Severity: normal



-- Package-specific info:

Boot method: CD
Image version: debian-Lenny-DI-rc2-amd64-netinst.iso
Date: 10 Ferbuary 2009

Machine: KVM 72+dfsg-4 on debian sid
Partitions: 

Disk /dev/hda: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000cc2b8

   Device Boot  Start End  Blocks   Id  System
/dev/hda1   *   1 486 3903763+  8e  Linux LVM
/dev/hda2 4871305 6578617+  8e  Linux LVM

  --- Volume group ---
  VG Name   datas
  System ID 
  Formatlvm2
  Metadata Areas1
  Metadata Sequence No  5
  VG Access read/write
  VG Status resizable
  MAX LV0
  Cur LV4
  Open LV   4
  Max PV0
  Cur PV1
  Act PV1
  VG Size   6,27 GB
  PE Size   4,00 MB
  Total PE  1606
  Alloc PE / Size   1312 / 5,12 GB
  Free  PE / Size   294 / 1,15 GB
  VG UUID   pwLChv-ruvR-ws0L-oRO6-oNUQ-oEDd-cDenQg
   
  --- Volume group ---
  VG Name   system
  System ID 
  Formatlvm2
  Metadata Areas1
  Metadata Sequence No  10
  VG Access read/write
  VG Status resizable
  MAX LV0
  Cur LV5
  Open LV   5
  Max PV0
  Cur PV1
  Act PV1
  VG Size   3,72 GB
  PE Size   4,00 MB
  Total PE  953
  Alloc PE / Size   953 / 3,72 GB
  Free  PE / Size   0 / 0   
  VG UUID   V67an8-HLYb-aIQb-Hxcq-rtFs-FH9M-YGjNiV
   

  --- Logical volume ---
  LV Name/dev/datas/var
  VG Namedatas
  LV UUID1nPqMM-Dzd2-C3Lo-7xWc-WAd1-Ijaz-bY1xSw
  LV Write Accessread/write
  LV Status  available
  # open 1
  LV Size1,86 GB
  Current LE 476
  Segments   1
  Allocation inherit
  Read ahead sectors auto
  - currently set to 256
  Block device   254:5
   
  --- Logical volume ---
  LV Name/dev/datas/var-log
  VG Namedatas
  LV UUIDmj1lYo-CCVE-jlYJ-XXK1-tBJG-VSon-Hubgv0
  LV Write Accessread/write
  LV Status  available
  # open 1
  LV Size488,00 MB
  Current LE 122
  Segments   1
  Allocation inherit
  Read ahead sectors auto
  - currently set to 256
  Block device   254:6
   
  --- Logical volume ---
  LV Name/dev/datas/var-lib
  VG Namedatas
  LV UUIDG0AeVy-Esnf-gKVP-HNtx-zUei-2ok7-YDbm2b
  LV Write Accessread/write
  LV Status  available
  # open 1
  LV Size952,00 MB
  Current LE 238
  Segments   1
  Allocation inherit
  Read ahead sectors auto
  - currently set to 256
  Block device   254:7
   
  --- Logical volume ---
  LV Name/dev/datas/var-cache
  VG Namedatas
  LV UUIDnjXPqz-KKY1-1YSJ-zVpO-rfYX-SP9T-14mN3n
  LV Write Accessread/write
  LV Status  available
  # open 1
  LV Size1,86 GB
  Current LE 476
  Segments   1
  Allocation inherit
  Read ahead sectors auto
  - currently set to 256
  Block device   254:8
   
  --- Logical volume ---
  LV Name/dev/system/racine
  VG Namesystem
  LV UUIDRKps3s-1lDZ-hcor-cT2N-Vj7r-3zYI-tptIco
  LV Write Accessread/write
  LV Status  available
  # open 1
  LV Size952,00 MB
  Current LE 238
  Segments   1
  Allocation inherit
  Read ahead sectors auto
  - currently set to 256
  Block device   254:0
   
  --- Logical volume ---
  LV Name/dev/system/swap
  VG Namesystem
  LV UUIDk0jKcJ-2VAz-Ntci-6BbR-uJ1D-IiMN-RmjS73
  LV Write Accessread/write
  LV Status  available
  # open 2
  LV Size488,00 MB
  Current LE 122
  Segments   1
  Allocation inherit
  Read ahead sectors auto
  - currently set to 256
  Block device   254:1
   
  --- Logical volume ---
  LV Name/dev/system/usr
  VG Namesystem
  LV UUID0muiV9-r24x-sk8E-xRLM-XJNM-FB73-15Xhtd
  LV Write Accessread/write
  LV Status  available
  # open 1
  LV Size952,00 

Bug#514826: Same problem here with another hardware configuration

2009-02-11 Thread Emmanuel Lesouef
I have the same problem here with a different hardware configuration.

The hardware summary is attached.

As suggested by Daniel, I can confirm that my system is booting after
modifying the lilo command-line.

-- 
Emmanuel Lesouef


hardware-summary
Description: Binary data


Re: Draft for lenny release announcement

2009-02-11 Thread Ferenc Wagner
Holger Levsen hol...@layer-acht.org writes:

 On Dienstag, 10. Februar 2009, Jérémy Bobbio wrote:

 For Microsoft Windows users, the installer can also be started
 without having to reconfigure the system BIOS.

 What does that sentence mean? Why should (only) Windows users need
 to reconfigure the bios?

To boot from CD instead of HDD, I guess.
-- 
Feri.


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



Bug#514826: Same problem here with another hardware configuration

2009-02-11 Thread Ferenc Wagner
Emmanuel Lesouef e.leso...@crbn.fr writes:

 As suggested by Daniel, I can confirm that my system is booting after
 modifying the lilo command-line.

It's probably the same issue as #511447.  Should we merge them?
-- 
Feri.



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



Re: Draft for lenny release announcement

2009-02-11 Thread Richard Hartmann
On Wed, Feb 11, 2009 at 11:50, Ferenc Wagner wf...@niif.hu wrote:
 Holger Levsen hol...@layer-acht.org writes:

 On Dienstag, 10. Februar 2009, Jérémy Bobbio wrote:

 For Microsoft Windows users, the installer can also be started
 without having to reconfigure the system BIOS.

 What does that sentence mean? Why should (only) Windows users need
 to reconfigure the bios?

 To boot from CD instead of HDD, I guess.

Makes sense. In that case, the sentence should be clearer, though.

_Assuming_ this is correct, how about:


---
The installer can now modify the boot sector of a running Windows,
enabling the user to install Debian without the need to reconfigure
the BIOS to boot from the installation CD.
---


Richard


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



Re: Draft for lenny release announcement

2009-02-11 Thread Holger Levsen
Hi,

On Mittwoch, 11. Februar 2009, Ferenc Wagner wrote:
  For Microsoft Windows users, the installer can also be started
  without having to reconfigure the system BIOS.
  What does that sentence mean? Why should (only) Windows users need
  to reconfigure the bios?
 To boot from CD instead of HDD, I guess.

That doesnt really have to do anything with Windows. Or if, it should be 
explained how/why.


regards,
Holger


signature.asc
Description: This is a digitally signed message part.


Re: Draft for lenny release announcement

2009-02-11 Thread Ferenc Wagner
Richard Hartmann richih.mailingl...@gmail.com writes:

 On Wed, Feb 11, 2009 at 11:50, Ferenc Wagner wf...@niif.hu wrote:
 Holger Levsen hol...@layer-acht.org writes:

 On Dienstag, 10. Februar 2009, Jérémy Bobbio wrote:

 For Microsoft Windows users, the installer can also be started
 without having to reconfigure the system BIOS.

 What does that sentence mean? Why should (only) Windows users need
 to reconfigure the bios?

 To boot from CD instead of HDD, I guess.

 Makes sense. In that case, the sentence should be clearer, though.

 _Assuming_ this is correct, how about:

 ---
 The installer can now modify the boot sector of a running Windows,
 enabling the user to install Debian without the need to reconfigure
 the BIOS to boot from the installation CD.
 ---

That sounds fishy.  As I understand it, win32-loader can start the
installer from Windows, not needing a reboot (thus not needing BIOS
boot order reconfiguration either).  I doubt Windows stays running
during installation, rather it's replaced by the Debian Installer.

So those who don't run Windows (or don't use the win32-loader) still
have to reboot to start the installer, and thus ensure that the BIOS
boots their installer media, not the current OS.

http://en.wikipedia.org/wiki/Win32-loader_(Debian)
-- 
Cheers,
Feri.


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



Bug#512546: Same problem on Dell Optiplex 760 with Intel Corporation 82567LM-3 Gigabit Network Connection [8086:10de] (rev 02)

2009-02-11 Thread Sebastiaan Couwenberg
Today I encountered this issue on a Dell Optiplex 760 while trying to
setup my new workstation at work.

Both the Etch and Etch 'N' Half D-I, which I initially tried, fail to
detect the network card. The Lenny D-I RC2 and the daily build of
2009-02-09 also fail to detect the network card. Manually selecting the
e1000e driver also fails. On Ubuntu 8.10 the NIC is detected correctly.

lspci -kvv output:

lspci -kvv: 00:00.0 Host bridge [0600]: Intel Corporation 4 Series Chipset
DRAM Controller [8086:2e10] (rev 03)
lspci -kvv: Kernel driver in use: agpgart-intel
lspci -kvv: Kernel modules: intel-agp
lspci -kvv: 00:01.0 PCI bridge [0604]: Intel Corporation 4 Series Chipset
PCI Express Root Port [8086:2e11] (rev 03)
lspci -kvv: Kernel driver in use: pcieport-driver
lspci -kvv: Kernel modules: shpchp
lspci -kvv: 00:02.0 VGA compatible controller [0300]: Intel Corporation 4
Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03)
lspci -kvv: 00:02.1 Display controller [0380]: Intel Corporation 4 Series
Chipset Integrated Graphics Controller [8086:2e13] (rev 03)
lspci -kvv: 00:03.0 Communication controller [0780]: Intel Corporation 4
Series Chipset HECI Controller [8086:2e14] (rev 03)
lspci -kvv: 00:03.2 IDE interface [0101]: Intel Corporation 4 Series
Chipset PT IDER Controller [8086:2e16] (rev 03)
lspci -kvv: 00:03.3 Serial controller [0700]: Intel Corporation 4 Series
Chipset Serial KT Controller [8086:2e17] (rev 03)
lspci -kvv: Kernel driver in use: serial
lspci -kvv: 00:19.0 Ethernet controller [0200]: Intel Corporation
82567LM-3 Gigabit Network Connection [8086:10de] (rev 02)
lspci -kvv: Kernel driver in use: e1000e
lspci -kvv: Kernel modules: e1000e
lspci -kvv: 00:1a.0 USB Controller [0c03]: Intel Corporation 82801JD/DO
(ICH10 Family) USB UHCI Controller #4 [8086:3a67] (rev 02)
lspci -kvv: Kernel driver in use: uhci_hcd
lspci -kvv: Kernel modules: uhci-hcd
lspci -kvv: 00:1a.1 USB Controller [0c03]: Intel Corporation 82801JD/DO
(ICH10 Family) USB UHCI Controller #5 [8086:3a68] (rev 02)
lspci -kvv: Kernel driver in use: uhci_hcd
lspci -kvv: Kernel modules: uhci-hcd
lspci -kvv: 00:1a.2 USB Controller [0c03]: Intel Corporation 82801JD/DO
(ICH10 Family) USB UHCI Controller #6 [8086:3a69] (rev 02)
lspci -kvv: Kernel driver in use: uhci_hcd
lspci -kvv: Kernel modules: uhci-hcd
lspci -kvv: 00:1a.7 USB Controller [0c03]: Intel Corporation 82801JD/DO
(ICH10 Family) USB2 EHCI Controller #2 [8086:3a6c] (rev 02)
lspci -kvv: Kernel driver in use: ehci_hcd
lspci -kvv: Kernel modules: ehci-hcd
lspci -kvv: 00:1b.0 Audio device [0403]: Intel Corporation 82801JD/DO
(ICH10 Family) HD Audio Controller [8086:3a6e] (rev 02)
lspci -kvv: Kernel driver in use: HDA Intel
lspci -kvv: Kernel modules: snd-hda-intel
lspci -kvv: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801JD/DO (ICH10
Family) PCI Express Port 1 [8086:3a70] (rev 02)
lspci -kvv: Kernel driver in use: pcieport-driver
lspci -kvv: Kernel modules: shpchp
lspci -kvv: 00:1c.1 PCI bridge [0604]: Intel Corporation 82801JD/DO (ICH10
Family) PCI Express Port 2 [8086:3a72] (rev 02)
lspci -kvv: Kernel driver in use: pcieport-driver
lspci -kvv: Kernel modules: shpchp
lspci -kvv: 00:1d.0 USB Controller [0c03]: Intel Corporation 82801JD/DO
(ICH10 Family) USB UHCI Controller #1 [8086:3a64] (rev 02)
lspci -kvv: Kernel driver in use: uhci_hcd
lspci -kvv: Kernel modules: uhci-hcd
lspci -kvv: 00:1d.1 USB Controller [0c03]: Intel Corporation 82801JD/DO
(ICH10 Family) USB UHCI Controller #2 [8086:3a65] (rev 02)
lspci -kvv: Kernel driver in use: uhci_hcd
lspci -kvv: Kernel modules: uhci-hcd
lspci -kvv: 00:1d.2 USB Controller [0c03]: Intel Corporation 82801JD/DO
(ICH10 Family) USB UHCI Controller #3 [8086:3a66] (rev 02)
lspci -kvv: Kernel driver in use: uhci_hcd
lspci -kvv: Kernel modules: uhci-hcd
lspci -kvv: 00:1d.7 USB Controller [0c03]: Intel Corporation 82801JD/DO
(ICH10 Family) USB2 EHCI Controller #1 [8086:3a6a] (rev 02)
lspci -kvv: Kernel driver in use: ehci_hcd
lspci -kvv: Kernel modules: ehci-hcd
lspci -kvv: 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge
[8086:244e] (rev a2)
lspci -kvv: 00:1f.0 ISA bridge [0601]: Intel Corporation 82801JD (ICH10D)
LPC Interface Controller [8086:3a1a] (rev 02)
lspci -kvv: 00:1f.2 SATA controller [0106]: Intel Corporation 82801JD/DO
(ICH10 Family) SATA AHCI Controller [8086:3a02] (rev 02)
lspci -kvv: Kernel driver in use: ahci
lspci -kvv: Kernel modules: ahci
lspci -kvv: 00:1f.3 SMBus [0c05]: Intel Corporation 82801JD/DO (ICH10
Family) SMBus Controller [8086:3a60] (rev 02)
lspci -kvv: Kernel modules: i2c-i801

lspci -s 00:19 -vvv:

00:19.0 Ethernet controller: Intel Corporation 82567LM-3 Gigabit Network
Connection (rev 02)
Subsystem: Dell Device 027f

Re: Draft for lenny release announcement

2009-02-11 Thread Tanco

As I understand, this may has a whole other meaning,

when installing Debian on a HDD that has a Windows installation, I 
wanted to use grub to load linux, but didn`t like installing it to the 
MBR, so I installed it on the Debian root partition boot record, after 
the installation procedure, I needed to set the Debian partition active 
in order to keep my mbr as is, and be able to run the Debian system. so 
maybe the Debian installer makes the debian partition active if you 
instruct grub to install its self on the root partition?


Ferenc Wagner wrote:

Richard Hartmann richih.mailingl...@gmail.com writes:

  

On Wed, Feb 11, 2009 at 11:50, Ferenc Wagner wf...@niif.hu wrote:


Holger Levsen hol...@layer-acht.org writes:

  

On Dienstag, 10. Februar 2009, Jérémy Bobbio wrote:



For Microsoft Windows users, the installer can also be started
without having to reconfigure the system BIOS.
  

What does that sentence mean? Why should (only) Windows users need
to reconfigure the bios?


To boot from CD instead of HDD, I guess.
  

Makes sense. In that case, the sentence should be clearer, though.

_Assuming_ this is correct, how about:

---
The installer can now modify the boot sector of a running Windows,
enabling the user to install Debian without the need to reconfigure
the BIOS to boot from the installation CD.
---



That sounds fishy.  As I understand it, win32-loader can start the
installer from Windows, not needing a reboot (thus not needing BIOS
boot order reconfiguration either).  I doubt Windows stays running
during installation, rather it's replaced by the Debian Installer.

So those who don't run Windows (or don't use the win32-loader) still
have to reboot to start the installer, and thus ensure that the BIOS
boots their installer media, not the current OS.

http://en.wikipedia.org/wiki/Win32-loader_(Debian)
  



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



Re: Draft for lenny release announcement

2009-02-11 Thread Richard Hartmann
On Wed, Feb 11, 2009 at 12:18, Holger Levsen hol...@layer-acht.org wrote:

 That doesnt really have to do anything with Windows. Or if, it should be
 explained how/why.

Because the installer carries executables for Windows only (well, and
Linux).
You are right though, it should be explained why.

Why the confusion right now, we should prolly wait for someone from
the installer team to chip in.


Richard


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



Re: Draft for lenny release announcement

2009-02-11 Thread Richard Hartmann
On Wed, Feb 11, 2009 at 12:25, Ferenc Wagner wf...@niif.hu wrote:

 That sounds fishy.  As I understand it, win32-loader can start the
 installer from Windows, not needing a reboot (thus not needing BIOS
 boot order reconfiguration either).  I doubt Windows stays running
 during installation, rather it's replaced by the Debian Installer.

That does not seem to make sense. Qemu or some such (if it runs
on Windows) sounds more likely than unloading the Windows kernel
on the fly.
But as I said, this is too important for speculation, we need
something in the know to explain what is meant by the initial
sentence. The -boot list is CC, so that should not be too much
of a problem :)


Richard


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



Re: Draft for lenny release announcement

2009-02-11 Thread Paul Wise
On Wed, Feb 11, 2009 at 8:25 PM, Ferenc Wagner wf...@niif.hu wrote:

 That sounds fishy.  As I understand it, win32-loader can start the
 installer from Windows, not needing a reboot (thus not needing BIOS
 boot order reconfiguration either).  I doubt Windows stays running
 during installation, rather it's replaced by the Debian Installer.

Wrong, win32-loader adds grub to the Windows boot.ini and you can then
reboot and choose to boot d-i via grub-win32 (or Windows) from the
Windows bootloader menu.

reboot-less installs under Windows could be done with coLinux perhaps:

http://www.colinux.org/
http://www.andlinux.org/

There are also WUBI, Instlux, UNetbootin, Lubi, Mubi and LVPM.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


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



Re: Draft for lenny release announcement

2009-02-11 Thread Jérémy Bobbio
On Wed, Feb 11, 2009 at 12:18:34PM +0100, Holger Levsen wrote:
 On Mittwoch, 11. Februar 2009, Ferenc Wagner wrote:
   For Microsoft Windows users, the installer can also be started
   without having to reconfigure the system BIOS.
   What does that sentence mean? Why should (only) Windows users need
   to reconfigure the bios?
  To boot from CD instead of HDD, I guess.
 
 That doesnt really have to do anything with Windows. Or if, it should be 
 explained how/why.

I wanted to highlight the inclusion of win32-loader.  But maybe this
does not fit the release announcement and should just be dropped
completely.

Cheers,
-- 
Jérémy Bobbio.''`. 
lu...@debian.org: :Ⓐ  :  # apt-get install anarchism
`. `'` 
  `-   


signature.asc
Description: Digital signature


Re: Draft for lenny release announcement

2009-02-11 Thread Holger Levsen
Hi,

thanks Paul for the explaination!

On Mittwoch, 11. Februar 2009, Holger Levsen wrote:
  For Microsoft Windows users, the installer can also be started
  without having to reconfigure the system BIOS.

Maybe something like this is better:

There is also a new tool for Windows users, win32-loader which can modifiy 
the boot.ini from Windows, so it's possible to install Debian without 
touching the BIOS.


regards,
Holger


signature.asc
Description: This is a digitally signed message part.


Re: 40r6 locks up during boot

2009-02-11 Thread John Summerfield

Ian Campbell wrote:

On Mon, 2009-01-12 at 11:04 +0900, John wrote:

John wrote:

Frans Pop wrote:
Ah, so. It's the DVD image.


It's different, but not satisfactory.

I'm copying by hand atm, I'll look at a serial cable (I think I can do 
that) later, so I will give a bare minimum for the moment.


Security framework initialized
SELinux diasbled at boot
Capability LSM initialized
Initializing xgroup subsys ns
cpuacct
devices
CPU: L1 cache 64K etc
CPU: L2 cache 512K etc
CPU: Amd Athlon (tm) Dual Core Processor 4450B stepping 02
checking HLT instruction ... ok
general protection fault: 3edc [#1]
Modules linked in:

Pid 0, comm: swapper Not tainted (2.6.26-1-486 #1)
EIP 0060:[c03633f0d] EFLAGS 0286 CPU: 0
EIP is at 0xc0363f0d

I will leave off now, lots of hex numbers which I'm likely to mistranscribe.

It ends with kernel panic - not syncing -: Attempted to kill the idle task!

Oh, the top item on the call trace:
[c0107a71] apply_paravirt+0x81/0x91.


Hmm, this suggests that adding noreplace-paravirt to your command line
might help.

It'd be interesting to see all the hex numbers once you've got serial
connected up though, especially since the crashing EIP is at 0xc03xx
which implies it is in a module. 


I vaguely recall some traffic on LKML about dynamic patching of stuff in
modules, need to try and remember more to dig it out.


and it's called from vgacon_set_cursor_size.


Called from? Did you see this address on the stack? It might be that it
is attempting to replace some code in this function so it appears on the
stack spuriously.

Ian.


Thanks for your help, Frans and Ian. I was at the beginning of a serious 
 deadline period. I made the deadline with just hours to spare, and 
there were no disasters.


I worked around it by installing virtualbox and Lenny. Lenny does what I 
need adequately, and I don't expect to revisit this.


For the record, it's an HP DC5850 (I mistyped the model number), the AMD 
 CPU does support virtualisation, it is turned off in the BIOS but can 
be turned on. To my surprise, it's listed under security features.




--


Cheers
John Summerfield.



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



Re: Draft for lenny release announcement

2009-02-11 Thread Richard Hartmann
On Wed, Feb 11, 2009 at 13:45, Holger Levsen hol...@layer-acht.org wrote:

 There is also a new tool for Windows users, win32-loader which can modifiy

s/win32-loader/win32-loader,/

 the boot.ini from Windows, so it's possible to install Debian without
 touching the BIOS.

touching the BIOS to change the boot device priority.


That was the reason why this discussion started in the first place ;)

Richard


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



Re: Draft for lenny release announcement

2009-02-11 Thread Ferenc Wagner
Richard Hartmann richih.mailingl...@gmail.com writes:

 On Wed, Feb 11, 2009 at 12:25, Ferenc Wagner wf...@niif.hu wrote:

 That sounds fishy.  As I understand it, win32-loader can start the
 installer from Windows, not needing a reboot (thus not needing BIOS
 boot order reconfiguration either).  I doubt Windows stays running
 during installation, rather it's replaced by the Debian Installer.

 That does not seem to make sense. Qemu or some such (if it runs
 on Windows) sounds more likely than unloading the Windows kernel
 on the fly.

Indeed, I was wrong.  win32-loader configures the Windows boot loader
to optionally start the Debian Installer (and also preconfigures some
settings like locale, timezone etc. based on the Windows settings).
So a reboot is still needed to actually start the installer, but
there's no need to boot from a separate device.

See http://goodbye-microsoft.com/demo.html or
http://www.youtube.com/watch?v=H937zZidIZk for a video demo.
-- 
Sorry for the confusion,
Feri.


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



Bug#514826: Same problem here with another hardware configuration

2009-02-11 Thread Ian McDonald
It looks to me very similar to 501969, which if the lilo command line 
was fixed up, would go away too.


--
ian


Ferenc Wagner wrote:

Emmanuel Lesouef e.leso...@crbn.fr writes:

  

As suggested by Daniel, I can confirm that my system is booting after
modifying the lilo command-line.



It's probably the same issue as #511447.  Should we merge them?
  


--
ian

Ian McDonald, ITS, University of St Andrews
T: +441334462779 F: +441334462759
The University of St Andrews is a charity registered in Scotland: SC013532




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



Ramdisk: ran out of compressed data p550

2009-02-11 Thread Roberto Lahoud

 Hi everybody, im having problem installing
 debian-Lenny-DI-rc2-powerpc-DVD-1.isohttp://cdimage.debian.org/cdimage/weekly-builds/powerpc/iso-dvd/debian-Lenny-DI-rc2-powerpc-DVD-1.isofrom
  week 02-Feb-2009 on a p550 power5, model 9406-550 with HMC, when i boot
 from de dvd the system the menu from yaboot shows, and when i make the
 selection install64, the installer start to boot until it fails, giving this
 errors


 [0.510170] Ramdisk: compressed image found at block0
 [0.722845] Ramdisk: incomplete write (-28!=32768) 10485760
 [0.771772] Ramdisk: ran out of compressed data
 [0.771782] Ramdisk: invalid compressed format (err=1)
 [0.791592] List all partitions:
 [0.791603] No filesystem could mount root, tried:
 [0.791614] Kernel panic - not syncing: VFS: unable to mount root fs on
 unkown block(0,1)
 [0.791631] Rebooting in 180 seconds

 the system has red hat already installed in the partition where i am trying
 to install debian i dont know if this could be making some problem, the
 error [0.722845] Ramdisk: incomplete write (-28!=32768) 10485760 dissaper
 whe i call the installer passing a difent size for the ramdisk, especificaly
 install64 ramdisk_size=20580, i very need your help how to solve it, i
 woul very apreciate your help, thanks.



Re: Draft for lenny release announcement

2009-02-11 Thread Christian Perrier
Quoting Jérémy Bobbio (lu...@debian.org):

  That doesnt really have to do anything with Windows. Or if, it should be 
  explained how/why.
 
 I wanted to highlight the inclusion of win32-loader.  But maybe this
 does not fit the release announcement and should just be dropped
 completely.

Given that it might be hard to explain what *exactly* win32-loader is
doing, I think it could be safer to drop this new feature from the
announcement. 



signature.asc
Description: Digital signature


Bug#512546: Same problem on Dell Optiplex 760 with Intel Corporation 82567LM-3 Gigabit Network Connection [8086:10de] (rev 02)

2009-02-11 Thread Christian Perrier
Quoting Sebastiaan Couwenberg (sebas...@xs4all.nl):

 Hopefully the e1000e driver in D-I can be fixed before the official Lenny
 release so I can reinstall my workstation using that. Or an addition to
 the release notes  documenting this issue if it cannot be fixed before the
 official release in the coming weekend.


I'm afraid that none of these is an option.

Fix D-I: too late...much too late
Add an item to the release notes: too late, they're frozen.

The only option could be adding something to an errata file.




signature.asc
Description: Digital signature


Re: Draft for lenny release announcement

2009-02-11 Thread Alexander Reichle-Schmehl
Hi!

Christian Perrier schrieb:

 Given that it might be hard to explain what *exactly* win32-loader is
 doing, I think it could be safer to drop this new feature from the
 announcement. 

Did so when the discussion started waiting for a consensus.  Seems we
reached it ;)


Best regards,
  Alexander



signature.asc
Description: OpenPGP digital signature


Bug#512546: Same problem on Dell Optiplex 760 with Intel Corporation 82567LM-3 Gigabit Network Connection [8086:10de] (rev 02)

2009-02-11 Thread Sebastiaan Couwenberg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Christian Perrier wrote:
 The only option could be adding something to an errata file.

That would very be nice.


While researching this problem a bit more, I found that support for the
Intel 82567LM-3 NIC was added in kernel 2.6.28:

commit f4187b56e1f8a05dd110875d5094b21b51ebd79b
Author: Bruce Allan bruce.w.al...@intel.com
Date:   Tue Aug 26 18:36:50 2008 -0700

e1000e: add support for 82567LM-3 and 82567LF-3 (ICH10D) parts

Add support for new LOM devices on the latest generation ICHx
platforms.

http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.28

This kernel is not even in unstable yet, so I think support for this
hardware will have to wait till Lenny 'N' Half at least?

In Ubuntu support for these ICH10 NICs was added to kernel 2.6.27-6.9:

  [ Tim Gardner ]

  * Add support in e1000e for a couple of ICH10 PCI IDs
  * Enable CONFIG_INPUT_PCSPKR=m
- LP: #275453

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/275453/comments/3

Apparently they merged some changes from the e1000e driver from SourceForge:

+   /* Even those these are ICH10 devices, the ICH9 setup (which really
+* uses ICH8) works fine. Just drop this patch when it collides with
+* upstream. I ripped this from the SourceForge e1000e 0.4.1.7 driver.
+*/
+#define E1000_DEV_ID_ICH10_D_BM_LM0x10DE
+#define E1000_DEV_ID_ICH10_D_BM_LF0x10DF
+   { PCI_VDEVICE(INTEL, E1000_DEV_ID_ICH10_D_BM_LM), board_ich9lan },
+   { PCI_VDEVICE(INTEL, E1000_DEV_ID_ICH10_D_BM_LF), board_ich9lan },
+

http://launchpadlibrarian.net/18283516/linux_2.6.27-5.8_2.6.27-6.9.diff.gz

Using the Intel drivers from SourceForge may be an option for Lenny
users with recent Intel ICH10 NICs.

Good luck with the release this weekend!

Regards,

Bas


- --
GnuPG: 0x77A975AD
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkmTQ/oACgkQRWRRA3epda1QIACfWf2zc1W3PInsZASRDPumX1Qk
mygAoJj/l34Yykl2peG2Gi3N+GyDP5mm
=JvwV
-END PGP SIGNATURE-



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



Re: Draft for lenny release announcement

2009-02-11 Thread Richard Hartmann
On Wed, Feb 11, 2009 at 22:45, Alexander Reichle-Schmehl
alexan...@schmehl.info wrote:

 Christian Perrier schrieb:

 Given that it might be hard to explain what *exactly* win32-loader is
 doing, I think it could be safer to drop this new feature from the
 announcement.

 Did so when the discussion started waiting for a consensus.  Seems we
 reached it ;)

Dunno, I think this feature is very important for non-tech-savvy users.
Thus, it's a good selling point which means it would be good to mention
it in the release announcement which a lot of people will read.


Richard


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



Re: Draft for lenny release announcement

2009-02-11 Thread Alexander Reichle-Schmehl
[ readding debian-boot since the discussion is going to their topic ]
Hi!


Justin B Rye schrieb:

[ several improvements ]

Applied.


 If that last sentence is trying to say without having to boot from
 it (with the assumption that my BIOS wasn't set up to boot from
 removable media by default in the first place) then I would suggest:
 
   The installer can also be started directly from Microsoft Windows.

Okay, that's a bit tricky:  Under normal circumstances you would reboot
need to check, if your bios allows to boot from CD/DVD/Blu-ray, and
could then boot from your optical drive continuing with the
installation.  With win32-loader you can insert your disc while running
windows.  It will add an entry to Windows boot loader (including some
settings like timezone and language IIRC) and when you reboot you can
start the installation process from windows boot menu without needing to
check your bios settings.  (d-i folk, is that summary correct?)

There was some discussion on the debian-boot list about that, while
searching for a good phrase for that.  Currently that sentence has been
removed, but maybe you can come up with something?



Best regards,
  Alexander



signature.asc
Description: OpenPGP digital signature


Re: Draft for lenny release announcement

2009-02-11 Thread Frans Pop
On Wednesday 11 February 2009, Alexander Reichle-Schmehl wrote:
 Okay, that's a bit tricky:  Under normal circumstances you would reboot
 need to check, if your bios allows to boot from CD/DVD/Blu-ray, and
 could then boot from your optical drive continuing with the
 installation.

Aren't most BIOSes set up to boot from removable media before hard disk?

IMO this is a lot of noise about nothing.


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



4minuti - 11 febbraio 2009

2009-02-11 Thread 4minuti.it
4minuti.it


a.link{
text-decoration:none;
font-weight: bold;
color:#33;
}
a.link:activelink{
text-decoration:none;
font-weight: bold;
color:#33;
}
a.link:visited{
text-decoration:none;
font-weight: bold;
color:#33;
}
a.link:hover{
text-decoration:underline;
font-weight: bold;
color:#33;
}






























Il quotidiano che puoi stampare 
dalla tua mail. - Giovedigrave;, 12 febbraio 2009  


Fatti di cronaca nazionale e 
internazionale, economia, politica, tv, spettacoli, sport e cultura.














Alcune notizie del numero di oggi:












Nuovo allarme 
meteo, una ondata di gelo polare sull'Italia




MILANO - Giagrave; nella 
giornata di martedigrave; le prime nevicate sul Nord che perograve; non hanno 
creato troppi disagi per la circolazione. In queste ore segnalata una forte 
perturbazione che porta a una progressiva diminuzione delle temperature che 
potranno scendere anche sotto lo zero. Attese pioggia e neve












Pubblica 
amministrazione: dilaga la corruzione, lo dice la Corte dei Conti




ROMA - Il procuratore generale 
Furio Pasqualucci punta il dito contro la gestione allegra della spesa in campo 
sanitario e farmaceutico. Ma non solo: truffe nel settore dei rifiuti, opere 
edilizie incompiute, danno all'immagine causato alla Pa dai dipendenti pubblici 
che hanno intascato mazzette e consulenze indebite.












Autopsia. La 
morte di Eluana è stata in linea con il protocollo