Bug#228763: Debian installer installation-report

2004-05-02 Thread Martin Michlmayr
* Nagy Gabor [EMAIL PROTECTED] [2004-01-20 20:23]:
 For some reason the installer thought that I had a 80x30 display, and it
 tried to use that area. I was in 80x25, so the last 5 lines were not
 visible.

Can you please use the new beta4 and tell us if this still happens?

 After installation the PCMCIA subsystem did not work. During installation
 everything was loaded, but it seems that the installer forgot to include
 yenta_socket into the list of modules to be loaded before trying the other
 PCMCIA modules.

This is probably fixed.
-- 
Martin Michlmayr
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#228763: Debian installer installation-report

2004-01-25 Thread Gaudenz Steinlin
Am Don, den 22.01.2004 schrieb Nagy Gabor um 19:11:
 On 04-Jan-21 16:24, Gaudenz Steinlin wrote:
  Am Die, den 20.01.2004 schrieb Nagy Gabor um 20:23:
   Output of lspci:
   00:00.0 Host bridge: Intel Corp. 82845 845 (Brookdale) Chipset Host Bridge (rev 
   04)
   00:01.0 PCI bridge: Intel Corp. 82845 845 (Brookdale) Chipset AGP Bridge (rev 04)
   00:1e.0 PCI bridge: Intel Corp. 82801BAM/CAM PCI Bridge (rev 42)
   00:1f.0 ISA bridge: Intel Corp. 82801CAM ISA Bridge (LPC) (rev 02)
   00:1f.1 IDE interface: Intel Corp. 82801CAM IDE U100 (rev 02)
   00:1f.5 Multimedia audio controller: Intel Corp. 82801CA/CAM AC'97 Audio 
   Controller (rev 02)
   01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M7 LW 
   [Radeon Mobility 7500]
   02:04.0 Communication controller: Lucent Microelectronics LT WinModem (rev 02)
   02:06.0 CardBus bridge: Texas Instruments PCI1420
   02:06.1 CardBus bridge: Texas Instruments PCI1420
   02:08.0 Ethernet controller: Intel Corp. 82801CAM (ICH3) PRO/100 VM (KM) 
   Ethernet Controller (rev 42)
   02:0e.0 USB Controller: NEC Corporation USB (rev 41)
   02:0e.1 USB Controller: NEC Corporation USB (rev 41)
   02:0e.2 USB Controller: NEC Corporation USB 2.0 (rev 02)
  Could you please also provide the output of lspci -n so we can see if
  your PCMCIA problem is because of wrong pci ids in discover-data.
 
 swordfish:~# lspci -n
 00:00.0 Class 0600: 8086:1a30 (rev 04)
 00:01.0 Class 0604: 8086:1a31 (rev 04)
 00:1e.0 Class 0604: 8086:2448 (rev 42)
 00:1f.0 Class 0601: 8086:248c (rev 02)
 00:1f.1 Class 0101: 8086:248a (rev 02)
 00:1f.5 Class 0401: 8086:2485 (rev 02)
 01:00.0 Class 0300: 1002:4c57
 02:04.0 Class 0780: 11c1:0450 (rev 02)
 02:06.0 Class 0607: 104c:ac51
 02:06.1 Class 0607: 104c:ac51
 02:08.0 Class 0200: 8086:1038 (rev 42)
 02:0e.0 Class 0c03: 1033:0035 (rev 41)
 02:0e.1 Class 0c03: 1033:0035 (rev 41)
 02:0e.2 Class 0c03: 1033:00e0 (rev 02)
 
 
  I guess this is a problem with the discover hardware data listing the
  wrong module for your CardBus bridge. The lspci -n output will help to
  confirm this.
 
 Hope it helps.
Yes it helps. Your report confirmed another report about the same issue.
This will be fixed by the next upload of discover-data.

Thanks Gaudenz



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#228763: Debian installer installation-report

2004-01-23 Thread Christian Perrier
Quoting Nagy Gabor ([EMAIL PROTECTED]):

  I think he means what's is #228839.
 
 No, actually what I would like, is to have the package debconf installed
 pretty soon, and configured, so later every package will use the output
 and the level, that I am used to.
 
 Usually I use medium or low.
 
 Anyway, I did not try the expert boot thing.

Debconf *is* installed and configured. Priority is high by default and
the debconf priority question isa medium priority menu item.:-)

D-i is by default targeted at more novice users than you are so this
explains why the debconf priority question is not shown by default.

FOr using d-i a default priority you have t explicitely require it at
the bootprompt.

On of the design choices is to lower as much as possible the number of
asked questions.

However, there is, in 228839, some discussion about a way to offer
users a simple method for having the debconf priority they want, after
installation ran.




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#228763: Debian installer installation-report

2004-01-22 Thread Nagy Gabor
On 04-Jan-21 16:24, Gaudenz Steinlin wrote:
 Am Die, den 20.01.2004 schrieb Nagy Gabor um 20:23:
  Output of lspci:
  00:00.0 Host bridge: Intel Corp. 82845 845 (Brookdale) Chipset Host Bridge (rev 04)
  00:01.0 PCI bridge: Intel Corp. 82845 845 (Brookdale) Chipset AGP Bridge (rev 04)
  00:1e.0 PCI bridge: Intel Corp. 82801BAM/CAM PCI Bridge (rev 42)
  00:1f.0 ISA bridge: Intel Corp. 82801CAM ISA Bridge (LPC) (rev 02)
  00:1f.1 IDE interface: Intel Corp. 82801CAM IDE U100 (rev 02)
  00:1f.5 Multimedia audio controller: Intel Corp. 82801CA/CAM AC'97 Audio 
  Controller (rev 02)
  01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M7 LW 
  [Radeon Mobility 7500]
  02:04.0 Communication controller: Lucent Microelectronics LT WinModem (rev 02)
  02:06.0 CardBus bridge: Texas Instruments PCI1420
  02:06.1 CardBus bridge: Texas Instruments PCI1420
  02:08.0 Ethernet controller: Intel Corp. 82801CAM (ICH3) PRO/100 VM (KM) Ethernet 
  Controller (rev 42)
  02:0e.0 USB Controller: NEC Corporation USB (rev 41)
  02:0e.1 USB Controller: NEC Corporation USB (rev 41)
  02:0e.2 USB Controller: NEC Corporation USB 2.0 (rev 02)
 Could you please also provide the output of lspci -n so we can see if
 your PCMCIA problem is because of wrong pci ids in discover-data.

swordfish:~# lspci -n
00:00.0 Class 0600: 8086:1a30 (rev 04)
00:01.0 Class 0604: 8086:1a31 (rev 04)
00:1e.0 Class 0604: 8086:2448 (rev 42)
00:1f.0 Class 0601: 8086:248c (rev 02)
00:1f.1 Class 0101: 8086:248a (rev 02)
00:1f.5 Class 0401: 8086:2485 (rev 02)
01:00.0 Class 0300: 1002:4c57
02:04.0 Class 0780: 11c1:0450 (rev 02)
02:06.0 Class 0607: 104c:ac51
02:06.1 Class 0607: 104c:ac51
02:08.0 Class 0200: 8086:1038 (rev 42)
02:0e.0 Class 0c03: 1033:0035 (rev 41)
02:0e.1 Class 0c03: 1033:0035 (rev 41)
02:0e.2 Class 0c03: 1033:00e0 (rev 02)


 I guess this is a problem with the discover hardware data listing the
 wrong module for your CardBus bridge. The lspci -n output will help to
 confirm this.

Hope it helps.
Regards,
Gabor


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#228763: Debian installer installation-report

2004-01-22 Thread Nagy Gabor
On 04-Jan-21 23:20, Christian Perrier wrote:
   I would also like to be able to set the debconf question level before
   configuring all the packages.
  You mean to select another level than you used for the first stage? You
  can set the level for d-i with the expert boot option.
 
 I think he means what's is #228839.

No, actually what I would like, is to have the package debconf installed
pretty soon, and configured, so later every package will use the output
and the level, that I am used to.

Usually I use medium or low.

Anyway, I did not try the expert boot thing.

Regards,
Gabor


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#228763: Debian installer installation-report

2004-01-21 Thread Gaudenz Steinlin
Am Die, den 20.01.2004 schrieb Nagy Gabor um 20:23:
 Output of lspci:
 00:00.0 Host bridge: Intel Corp. 82845 845 (Brookdale) Chipset Host Bridge (rev 04)
 00:01.0 PCI bridge: Intel Corp. 82845 845 (Brookdale) Chipset AGP Bridge (rev 04)
 00:1e.0 PCI bridge: Intel Corp. 82801BAM/CAM PCI Bridge (rev 42)
 00:1f.0 ISA bridge: Intel Corp. 82801CAM ISA Bridge (LPC) (rev 02)
 00:1f.1 IDE interface: Intel Corp. 82801CAM IDE U100 (rev 02)
 00:1f.5 Multimedia audio controller: Intel Corp. 82801CA/CAM AC'97 Audio Controller 
 (rev 02)
 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M7 LW 
 [Radeon Mobility 7500]
 02:04.0 Communication controller: Lucent Microelectronics LT WinModem (rev 02)
 02:06.0 CardBus bridge: Texas Instruments PCI1420
 02:06.1 CardBus bridge: Texas Instruments PCI1420
 02:08.0 Ethernet controller: Intel Corp. 82801CAM (ICH3) PRO/100 VM (KM) Ethernet 
 Controller (rev 42)
 02:0e.0 USB Controller: NEC Corporation USB (rev 41)
 02:0e.1 USB Controller: NEC Corporation USB (rev 41)
 02:0e.2 USB Controller: NEC Corporation USB 2.0 (rev 02)
Could you please also provide the output of lspci -n so we can see if
your PCMCIA problem is because of wrong pci ids in discover-data.
 

 Thoughts: Even if I don't want an expert install, I would like to be asked
 if I have network, or if I want to install network at all.
The problem with this is, that even though you don't need a network to
complete the first stage of the d-i install, you need a network setup to
complete your install to a usable system. Only the base packages (those
required to get a minimal booting system) are included on the CD. All
other packages you need for a really usefull system have to be
downloaded from a debian mirror. 
Ideal the network configuration would be in base-config, but we don't
have a network configuration there yet, so it's the second best option
to configure it in d-i.
 
 I would also like to be able to set the debconf question level before
 configuring all the packages.
You mean to select another level than you used for the first stage? You
can set the level for d-i with the expert boot option.
 
 After installation the PCMCIA subsystem did not work. During installation
 everything was loaded, but it seems that the installer forgot to include
 yenta_socket into the list of modules to be loaded before trying the other
 PCMCIA modules.

I guess this is a problem with the discover hardware data listing the
wrong module for your CardBus bridge. The lspci -n output will help to
confirm this.

Gaudenz



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#228763: Debian installer installation-report

2004-01-21 Thread Christian Perrier

  I would also like to be able to set the debconf question level before
  configuring all the packages.
 You mean to select another level than you used for the first stage? You
 can set the level for d-i with the expert boot option.

I think he means what's is #228839.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#228763: Debian installer installation-report

2004-01-20 Thread Nagy Gabor
Package: installation-reports

INSTALL REPORT

Debian-installer-version: 2004-01-09 people.debian.org/~manty/testing/...
uname -a: Linux swordfish 2.4.23-1-386 #1 Sun Nov 30 16:49:14 EST 2003 i686 GNU/Linux
Date: 2004-01-10, 20:00 - 0:20 hours CET
Method: How did you install?  What did you boot off?  If network
  install, from where?  Proxied?
Burnt the debian-installer image (the bigger, around 100M in size) on a
CDRW, and booted from that.

cdrom-detect: Detected CD 'Debian GNU/Linux testing Sarge - Official
NetInst Snapshot i386 Binary-1 (20040109)'

I did not specify anything at the boot prompt first. Later I rebooted
since I could not see the bottom of the installation messages, and I
wrote: Linux vga=ask at the boot prompt. I have chosen 80x30, and that
way everything worked.
I did not have access to the Internet, so I did not download anything else.

Machine: Compaq Evo N610c
Processor: Pentium4 Mobile 1800
Memory: 256M
Root Device: IDE /dev/hda
Root Size/partition table:
 at installation time I have just created a 256M partition for /
 After the installation, and base system installation I have installed
 LVM, and now I am using logical volumes.
Output of lspci:
00:00.0 Host bridge: Intel Corp. 82845 845 (Brookdale) Chipset Host Bridge (rev 04)
00:01.0 PCI bridge: Intel Corp. 82845 845 (Brookdale) Chipset AGP Bridge (rev 04)
00:1e.0 PCI bridge: Intel Corp. 82801BAM/CAM PCI Bridge (rev 42)
00:1f.0 ISA bridge: Intel Corp. 82801CAM ISA Bridge (LPC) (rev 02)
00:1f.1 IDE interface: Intel Corp. 82801CAM IDE U100 (rev 02)
00:1f.5 Multimedia audio controller: Intel Corp. 82801CA/CAM AC'97 Audio Controller 
(rev 02)
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M7 LW [Radeon 
Mobility 7500]
02:04.0 Communication controller: Lucent Microelectronics LT WinModem (rev 02)
02:06.0 CardBus bridge: Texas Instruments PCI1420
02:06.1 CardBus bridge: Texas Instruments PCI1420
02:08.0 Ethernet controller: Intel Corp. 82801CAM (ICH3) PRO/100 VM (KM) Ethernet 
Controller (rev 42)
02:0e.0 USB Controller: NEC Corporation USB (rev 41)
02:0e.1 USB Controller: NEC Corporation USB (rev 41)
02:0e.2 USB Controller: NEC Corporation USB 2.0 (rev 02)

Base System Installation Checklist:

Initial boot worked:[O]
Configure network HW:   [O]
Config network: [ ]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Create file systems:[O]
Mount partitions:   [O]
Install base system:[O]
Install boot loader:[O]
Reboot: [O]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Comments/Problems:
For some reason the installer thought that I had a 80x30 display, and it
tried to use that area. I was in 80x25, so the last 5 lines were not
visible.
I managed to get through until the partitioning step, where I did not see
what cfdisk has printed, and I got lost.
I tried to solve the problem on another VT, but setting LINES did not
help, and I did not know what to do.
I rebooted, with vga=ask I have specified 80x30, and everything worked.

Thoughts: Even if I don't want an expert install, I would like to be asked
if I have network, or if I want to install network at all.

I would also like to be able to set the debconf question level before
configuring all the packages.

After installation the PCMCIA subsystem did not work. During installation
everything was loaded, but it seems that the installer forgot to include
yenta_socket into the list of modules to be loaded before trying the other
PCMCIA modules.

Anyway, good impression, good work.
Regards,
Gee


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]