Bug#316586: Package: installation-reports

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#316586: Package: installation-reports

Chuck Williams-2
Package: installation-reports

INSTALL REPORT

Debian-installer-version: 6/20/2005 debian-testing-i386-netinst.iso
uname -a: Linux debian-mana 2.6.12.1-mppe #1 SMP Wed Jun 29 22:46:25 PDT
2005 i686 GNU/Linux
Date: 6/20/2005-6/27/2005
Method: Installed from downloaded netinst image burned onto CD with
machine connected via cable to DHCP network
Machine: Compaq nx9600 notebook
Processor:  Intel Pentium 4 3.6GHz with hyperthreading
Memory: 2Gig
Root Device: 60Gig ide on /dev/hda
Root Size/partition table:  Results of df (/dev/sda is external usb
60Gig scsi)
  /dev/hda1             55313052   6584248  45919040  13% /
  tmpfs                  1036560        16   1036544   1% /dev/shm
  tmpfs                    10240       536      9704   6% /dev
  /dev/sda1             57685532  43084248  11671032  79% /home/chuck/vmwin
Output of lspci and lspci -n:
  0000:00:00.0 Host bridge: Intel Corp. 915G/P/GV Processor to I/O
Controller (rev 04)
  0000:00:01.0 PCI bridge: Intel Corp. 915G/P/GV PCI Express Root Port
(rev 04)
  0000:00:1c.0 PCI bridge: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6
Family) PCI Express Port 1 (rev 03)
  0000:00:1d.0 USB Controller: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB UHCI #1 (rev 03)
  0000:00:1d.1 USB Controller: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB UHCI #2 (rev 03)
  0000:00:1d.2 USB Controller: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB UHCI #3 (rev 03)
  0000:00:1d.3 USB Controller: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB UHCI #4 (rev 03)
  0000:00:1d.7 USB Controller: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB2 EHCI Controller (rev 03)
  0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev d3)
  0000:00:1e.2 Multimedia audio controller: Intel Corp.
82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 03)
  0000:00:1e.3 Modem: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family)
AC'97 Modem Controller (rev 03)
  0000:00:1f.0 ISA bridge: Intel Corp. 82801FB/FR (ICH6/ICH6R) LPC
Interface Bridge (rev 03)
  0000:00:1f.1 IDE interface: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6
Family) IDE Controller (rev 03)
  0000:00:1f.3 SMBus: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family)
SMBus Controller (rev 03)
  0000:01:00.0 VGA compatible controller: ATI Technologies Inc: Unknown
device 3150
  0000:0b:00.0 CardBus bridge: Texas Instruments: Unknown device 8031
  0000:0b:00.2 FireWire (IEEE 1394): Texas Instruments: Unknown device 8032
  0000:0b:00.3 Unknown mass storage controller: Texas Instruments:
Unknown device 8033
  0000:0b:00.4 0805: Texas Instruments: Unknown device 8034
  0000:0b:02.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8169 Gigabit Ethernet (rev 10)
  0000:0b:03.0 Network controller: Broadcom Corporation BCM4306
802.11b/g Wireless LAN Controller (rev 03)

  0000:00:00.0 0600: 8086:2580 (rev 04)
  0000:00:01.0 0604: 8086:2581 (rev 04)
  0000:00:1c.0 0604: 8086:2660 (rev 03)
  0000:00:1d.0 0c03: 8086:2658 (rev 03)
  0000:00:1d.1 0c03: 8086:2659 (rev 03)
  0000:00:1d.2 0c03: 8086:265a (rev 03)
  0000:00:1d.3 0c03: 8086:265b (rev 03)
  0000:00:1d.7 0c03: 8086:265c (rev 03)
  0000:00:1e.0 0604: 8086:244e (rev d3)
  0000:00:1e.2 0401: 8086:266e (rev 03)
  0000:00:1e.3 0703: 8086:266d (rev 03)
  0000:00:1f.0 0601: 8086:2640 (rev 03)
  0000:00:1f.1 0101: 8086:266f (rev 03)
  0000:00:1f.3 0c05: 8086:266a (rev 03)
  0000:01:00.0 0300: 1002:3150
  0000:0b:00.0 0607: 104c:8031
  0000:0b:00.2 0c00: 104c:8032
  0000:0b:00.3 0180: 104c:8033
  0000:0b:00.4 0805: 104c:8034
  0000:0b:02.0 0200: 10ec:8169 (rev 10)
  0000:0b:03.0 0280: 14e4:4320 (rev 03)

  Also relevant:  ATI Mobility Radeon X600 video card on PCI Express bus
                  The overall chipset is Intel 915P Express

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

Initial boot worked:    [O]
Configure network HW:   [O]
Config network:         [O]
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:                 [E]

Comments/Problems:

  There were many problems with this install and I had great difficulty
finding solutions.
  I'd like to first express my gratitude to Stuart Prescott who
responded (off-list) to my pleas
  for help on debian-latop, pointed me at the fglrx drivers, suggested
my sound problem my be a
  conflict with the modem driver, and generally provided encouragement
during various frustrating moments.

  Note:  I quickly moved from the installer 2.6.8 kernel to a 2.6.12
kernel (and now 2.6.12.1) for
  several reasons, including:
    1.  I wanted the latest drivers to try to get more devices to work
    2.  I need to custom-compile my kernel anyway in order to get the
mppe patch for a pptp vpn

  The problems I hit and their solutions were:

  Problem:  Reboot after installation crashes the kernel.
  Solution:  Blacklist i810_audio

  Problem:  Display will only run with vesa driver in XFree86 (radeon
driver crashes).  Vesa does not not
    have access to appropriate video modes.  This is a widescreen WSXGA+
display with a natural resolution
    of 1680x1050.  Running at 1280x1024, best available after install,
is both under-using the screen
    and distorts everything.
  Solution:  Use the fglrx package at
http://xoomer.virgilio.it/flavio.stanchina/debian/fglrx-installer.html.
    For fglrx to run in the 2.6.12 kernel required two patches:
      1.  In agpgart_be.c:  dev->slot_name ==> pci_name(dev) everywhere
      2.  In firegl_public.c:  inter_module_get(x) ==>
      inter_module_get_request(x,y) in #define, and the two calls to
      inter_module_get become calls to inter_module_get_request that
pass the
      same argument twice ("drm" ==> "drm","drm" and "drm_agp" ==>
      "drm_agp","drm_agp")
    After getting the appropriate kernel, it was of course necessary to
configure XF86Config-4 to
    use the fglrx driver.  All functions of the video card appear to
work properly now,

  Problem:  Wireless networking device did not work
  Solution:  Load ndiswrapper package and encapsulate their recommended
Windows driver for the
    Broadcom device listed above.

  Problem:  System bell worked, but neither alsa nor esd sound would work.
  Solution:  Blacklist snd_intel8x0m as it was improperly associated
with the sound device instead
    of with the modem device.  The proper sound driver is snd_intel8x0.
(Rather than blacklist, I just
    compiled snd_intel8x0m out of my kernel).  One consequence of this
is that presumably the modem will
    not work -- I haven't bothered to check since I didn't plan on using
it anyway.

  Problem:  pptp tunnel seems to conflict with vmware virtual nics
  Solution:  I haven't resolved this one yet, but am confident I will be
able to resolve it.  I run
    mppe, pptpconfig, tsclient and vmware all successfully on my
desktop.  The difference on this laptop
    is that I've configured vmware to be on a host-only network with NAT
to provide access to the external
    network if one is available.  The reason for that is that I need to
be able to network the host Linux and
    a virtual Lossdows for certain applications when completely
disconnected.

CONCLUSIONS AND RECOMMENDATIONS:
  Generally I find installing Debian and Linux on anything non-standard
to be a pain.  I do it because I
  love Debian and Linux and don't want to use anything else, plus I'm a
persistent SOB who doesn't like to give
  up.  Many people do give up, including friends of mine.  More people
would use and come to love Debian/Linux
  if it was easier to install.

  The biggest problems are accurately identifying the hardware, finding
the proper drivers, and getting them
  installed and working properly.  The biggest issue in this for me is
to accurately assess the current state
  of affairs.  E.g., devices are reported and/or specified in different
ways by lspci, /proc, /sys, /dev,
  hal-device-manager and XF86Config-4.  I have found no way to do these
basic things:
    1.  Determine definitively which device is mapped to which /dev node
    2.  Associate bus addresses as reported by /sys, hal-device-manager,
/proc and lspci -n with bus address
        specifications as required by XF86Config-4

  Getting accurate information on the hardware in the machine is also
difficult.  You can see from the lspci
  above that important devices on this machine are simply "unknown".  I
did Google searches, searched Debian
  archives and posted messages to debian-user and debian-latop, but
could find no one who had installed on
  this kind of machine before, and no definitive information.  I
contacted HP technical support to at least
  get accurate detailed hardware specs.  They publish a technical
specification document on their site, but
  it is incomplete.  HP Support could not, or would not, give me any
additional information.  They said,
  "Unfortunately, we did not test Linux operating system with nx9600
notebook. The nx9600 is designed to work
  with Windows 2000/XP operating system with optimum performance. And
the device drivers for Linux are not
  designed or available for this model notebook. However, we suggest you
install the preloaded Windows that was
  shipped with the notebook."

  Needless to say, that infuriated me and they were the brunt of what
ensued, but it didn't solve any of
  my problems.

  Life would be better if the two device and /dev identification issues
above were addressed, and if there
  was a single place one could go to find all available drivers.  In the
end, all the drivers I needed for this
  machine were available (modulo the modem confict and a minor patch to
fglrx, which I found a description of
  on a discussion board that Google turned up).  The problem wasn't
making it work, it was discovering how to
  make it work.  If information was more readily available, this would
have gone much quicker and smoother.
  For example, I did not know that ndiswrapper existed.  I only stumbled
on it after expending considerable
  effort on other fruitless attempts.

  Debian is great and I wish more people used it.  But for that to
happen these issues need to be addressed.

  I want to thank everyone who contributes to Debian and Linux.  Your
work is greatly appreciated -- the above is
  intended to be constructive suggestions.  I have not contributed
anything to Debian yet, but hope to in the
  futre as I have contributed to some other open source efforts.

Chuck



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

Reply | Threaded
Open this post in threaded view
|

Bug#316586: marked as done (Package: installation-reports)

Debian Bug Tracking System
Your message dated Sat, 2 Jul 2005 08:12:47 +0200
with message-id <[hidden email]>
and subject line Bug#316586: Package: installation-reports
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 2 Jul 2005 04:16:47 +0000
>From [hidden email] Fri Jul 01 21:16:47 2005
Return-path: <[hidden email]>
Received: from dev.allthingslocal.com [69.44.58.51]
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DoZQs-0000dY-00; Fri, 01 Jul 2005 21:16:46 -0700
Received: from [192.168.1.106] ([::ffff:66.92.12.207])
  (AUTH: LOGIN chuck, TLS: TLSv1/SSLv3,256bits,AES256-SHA)
  by dev.allthingslocal.com with esmtp; Fri, 01 Jul 2005 23:16:46 -0500
  id 000742F1.42C6152F.0000095F
Message-ID: <[hidden email]>
Date: Fri, 01 Jul 2005 21:16:57 -0700
From: Chuck Williams <[hidden email]>
User-Agent: Debian Thunderbird 1.0.2 (X11/20050602)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: [hidden email]
Subject: Package: installation-reports
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Delivered-To: [hidden email]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-5.1 required=4.0 tests=BAYES_44,HAS_PACKAGE
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:

Package: installation-reports

INSTALL REPORT

Debian-installer-version: 6/20/2005 debian-testing-i386-netinst.iso
uname -a: Linux debian-mana 2.6.12.1-mppe #1 SMP Wed Jun 29 22:46:25 PDT
2005 i686 GNU/Linux
Date: 6/20/2005-6/27/2005
Method: Installed from downloaded netinst image burned onto CD with
machine connected via cable to DHCP network
Machine: Compaq nx9600 notebook
Processor:  Intel Pentium 4 3.6GHz with hyperthreading
Memory: 2Gig
Root Device: 60Gig ide on /dev/hda
Root Size/partition table:  Results of df (/dev/sda is external usb
60Gig scsi)
  /dev/hda1             55313052   6584248  45919040  13% /
  tmpfs                  1036560        16   1036544   1% /dev/shm
  tmpfs                    10240       536      9704   6% /dev
  /dev/sda1             57685532  43084248  11671032  79% /home/chuck/vmwin
Output of lspci and lspci -n:
  0000:00:00.0 Host bridge: Intel Corp. 915G/P/GV Processor to I/O
Controller (rev 04)
  0000:00:01.0 PCI bridge: Intel Corp. 915G/P/GV PCI Express Root Port
(rev 04)
  0000:00:1c.0 PCI bridge: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6
Family) PCI Express Port 1 (rev 03)
  0000:00:1d.0 USB Controller: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB UHCI #1 (rev 03)
  0000:00:1d.1 USB Controller: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB UHCI #2 (rev 03)
  0000:00:1d.2 USB Controller: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB UHCI #3 (rev 03)
  0000:00:1d.3 USB Controller: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB UHCI #4 (rev 03)
  0000:00:1d.7 USB Controller: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB2 EHCI Controller (rev 03)
  0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev d3)
  0000:00:1e.2 Multimedia audio controller: Intel Corp.
82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 03)
  0000:00:1e.3 Modem: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family)
AC'97 Modem Controller (rev 03)
  0000:00:1f.0 ISA bridge: Intel Corp. 82801FB/FR (ICH6/ICH6R) LPC
Interface Bridge (rev 03)
  0000:00:1f.1 IDE interface: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6
Family) IDE Controller (rev 03)
  0000:00:1f.3 SMBus: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family)
SMBus Controller (rev 03)
  0000:01:00.0 VGA compatible controller: ATI Technologies Inc: Unknown
device 3150
  0000:0b:00.0 CardBus bridge: Texas Instruments: Unknown device 8031
  0000:0b:00.2 FireWire (IEEE 1394): Texas Instruments: Unknown device 8032
  0000:0b:00.3 Unknown mass storage controller: Texas Instruments:
Unknown device 8033
  0000:0b:00.4 0805: Texas Instruments: Unknown device 8034
  0000:0b:02.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8169 Gigabit Ethernet (rev 10)
  0000:0b:03.0 Network controller: Broadcom Corporation BCM4306
802.11b/g Wireless LAN Controller (rev 03)

  0000:00:00.0 0600: 8086:2580 (rev 04)
  0000:00:01.0 0604: 8086:2581 (rev 04)
  0000:00:1c.0 0604: 8086:2660 (rev 03)
  0000:00:1d.0 0c03: 8086:2658 (rev 03)
  0000:00:1d.1 0c03: 8086:2659 (rev 03)
  0000:00:1d.2 0c03: 8086:265a (rev 03)
  0000:00:1d.3 0c03: 8086:265b (rev 03)
  0000:00:1d.7 0c03: 8086:265c (rev 03)
  0000:00:1e.0 0604: 8086:244e (rev d3)
  0000:00:1e.2 0401: 8086:266e (rev 03)
  0000:00:1e.3 0703: 8086:266d (rev 03)
  0000:00:1f.0 0601: 8086:2640 (rev 03)
  0000:00:1f.1 0101: 8086:266f (rev 03)
  0000:00:1f.3 0c05: 8086:266a (rev 03)
  0000:01:00.0 0300: 1002:3150
  0000:0b:00.0 0607: 104c:8031
  0000:0b:00.2 0c00: 104c:8032
  0000:0b:00.3 0180: 104c:8033
  0000:0b:00.4 0805: 104c:8034
  0000:0b:02.0 0200: 10ec:8169 (rev 10)
  0000:0b:03.0 0280: 14e4:4320 (rev 03)

  Also relevant:  ATI Mobility Radeon X600 video card on PCI Express bus
                  The overall chipset is Intel 915P Express

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

Initial boot worked:    [O]
Configure network HW:   [O]
Config network:         [O]
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:                 [E]

Comments/Problems:

  There were many problems with this install and I had great difficulty
finding solutions.
  I'd like to first express my gratitude to Stuart Prescott who
responded (off-list) to my pleas
  for help on debian-latop, pointed me at the fglrx drivers, suggested
my sound problem my be a
  conflict with the modem driver, and generally provided encouragement
during various frustrating moments.

  Note:  I quickly moved from the installer 2.6.8 kernel to a 2.6.12
kernel (and now 2.6.12.1) for
  several reasons, including:
    1.  I wanted the latest drivers to try to get more devices to work
    2.  I need to custom-compile my kernel anyway in order to get the
mppe patch for a pptp vpn

  The problems I hit and their solutions were:

  Problem:  Reboot after installation crashes the kernel.
  Solution:  Blacklist i810_audio

  Problem:  Display will only run with vesa driver in XFree86 (radeon
driver crashes).  Vesa does not not
    have access to appropriate video modes.  This is a widescreen WSXGA+
display with a natural resolution
    of 1680x1050.  Running at 1280x1024, best available after install,
is both under-using the screen
    and distorts everything.
  Solution:  Use the fglrx package at
http://xoomer.virgilio.it/flavio.stanchina/debian/fglrx-installer.html.
    For fglrx to run in the 2.6.12 kernel required two patches:
      1.  In agpgart_be.c:  dev->slot_name ==> pci_name(dev) everywhere
      2.  In firegl_public.c:  inter_module_get(x) ==>
      inter_module_get_request(x,y) in #define, and the two calls to
      inter_module_get become calls to inter_module_get_request that
pass the
      same argument twice ("drm" ==> "drm","drm" and "drm_agp" ==>
      "drm_agp","drm_agp")
    After getting the appropriate kernel, it was of course necessary to
configure XF86Config-4 to
    use the fglrx driver.  All functions of the video card appear to
work properly now,

  Problem:  Wireless networking device did not work
  Solution:  Load ndiswrapper package and encapsulate their recommended
Windows driver for the
    Broadcom device listed above.

  Problem:  System bell worked, but neither alsa nor esd sound would work.
  Solution:  Blacklist snd_intel8x0m as it was improperly associated
with the sound device instead
    of with the modem device.  The proper sound driver is snd_intel8x0.
(Rather than blacklist, I just
    compiled snd_intel8x0m out of my kernel).  One consequence of this
is that presumably the modem will
    not work -- I haven't bothered to check since I didn't plan on using
it anyway.

  Problem:  pptp tunnel seems to conflict with vmware virtual nics
  Solution:  I haven't resolved this one yet, but am confident I will be
able to resolve it.  I run
    mppe, pptpconfig, tsclient and vmware all successfully on my
desktop.  The difference on this laptop
    is that I've configured vmware to be on a host-only network with NAT
to provide access to the external
    network if one is available.  The reason for that is that I need to
be able to network the host Linux and
    a virtual Lossdows for certain applications when completely
disconnected.

CONCLUSIONS AND RECOMMENDATIONS:
  Generally I find installing Debian and Linux on anything non-standard
to be a pain.  I do it because I
  love Debian and Linux and don't want to use anything else, plus I'm a
persistent SOB who doesn't like to give
  up.  Many people do give up, including friends of mine.  More people
would use and come to love Debian/Linux
  if it was easier to install.

  The biggest problems are accurately identifying the hardware, finding
the proper drivers, and getting them
  installed and working properly.  The biggest issue in this for me is
to accurately assess the current state
  of affairs.  E.g., devices are reported and/or specified in different
ways by lspci, /proc, /sys, /dev,
  hal-device-manager and XF86Config-4.  I have found no way to do these
basic things:
    1.  Determine definitively which device is mapped to which /dev node
    2.  Associate bus addresses as reported by /sys, hal-device-manager,
/proc and lspci -n with bus address
        specifications as required by XF86Config-4

  Getting accurate information on the hardware in the machine is also
difficult.  You can see from the lspci
  above that important devices on this machine are simply "unknown".  I
did Google searches, searched Debian
  archives and posted messages to debian-user and debian-latop, but
could find no one who had installed on
  this kind of machine before, and no definitive information.  I
contacted HP technical support to at least
  get accurate detailed hardware specs.  They publish a technical
specification document on their site, but
  it is incomplete.  HP Support could not, or would not, give me any
additional information.  They said,
  "Unfortunately, we did not test Linux operating system with nx9600
notebook. The nx9600 is designed to work
  with Windows 2000/XP operating system with optimum performance. And
the device drivers for Linux are not
  designed or available for this model notebook. However, we suggest you
install the preloaded Windows that was
  shipped with the notebook."

  Needless to say, that infuriated me and they were the brunt of what
ensued, but it didn't solve any of
  my problems.

  Life would be better if the two device and /dev identification issues
above were addressed, and if there
  was a single place one could go to find all available drivers.  In the
end, all the drivers I needed for this
  machine were available (modulo the modem confict and a minor patch to
fglrx, which I found a description of
  on a discussion board that Google turned up).  The problem wasn't
making it work, it was discovering how to
  make it work.  If information was more readily available, this would
have gone much quicker and smoother.
  For example, I did not know that ndiswrapper existed.  I only stumbled
on it after expending considerable
  effort on other fruitless attempts.

  Debian is great and I wish more people used it.  But for that to
happen these issues need to be addressed.

  I want to thank everyone who contributes to Debian and Linux.  Your
work is greatly appreciated -- the above is
  intended to be constructive suggestions.  I have not contributed
anything to Debian yet, but hope to in the
  futre as I have contributed to some other open source efforts.

Chuck


---------------------------------------
Received: (at 316586-done) by bugs.debian.org; 2 Jul 2005 06:13:37 +0000
>From [hidden email] Fri Jul 01 23:13:37 2005
Return-path: <[hidden email]>
Received: from perrier.eu.org (kheops.perrier.eu.org) [81.56.227.253]
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DobFw-00049l-00; Fri, 01 Jul 2005 23:13:37 -0700
Received: from localhost (localhost [127.0.0.1])
        by kheops.perrier.eu.org (Postfix) with ESMTP id CCAD14F971;
        Sat,  2 Jul 2005 08:13:05 +0200 (CEST)
Received: from kheops.perrier.eu.org ([127.0.0.1])
        by localhost (kheops [127.0.0.1]) (amavisd-new, port 10024)
        with ESMTP id 26364-02; Sat, 2 Jul 2005 08:13:04 +0200 (CEST)
Received: from mykerinos.kheops.frmug.org (mykerinos.kheops.frmug.org [192.168.1.3])
        by kheops.perrier.eu.org (Postfix) with ESMTP id AFB484F897;
        Sat,  2 Jul 2005 08:13:04 +0200 (CEST)
Received: by mykerinos.kheops.frmug.org (Postfix, from userid 7426)
        id 2446823237; Sat,  2 Jul 2005 08:12:47 +0200 (CEST)
Date: Sat, 2 Jul 2005 08:12:47 +0200
From: Christian Perrier <[hidden email]>
To: Chuck Williams <[hidden email]>, [hidden email]
Subject: Re: Bug#316586: Package: installation-reports
Message-ID: <[hidden email]>
References: <[hidden email]>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Disposition: inline
In-Reply-To: <[hidden email]>
User-Agent: Mutt/1.5.9i
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at kheops.frmug.org
Content-Transfer-Encoding: quoted-printable
Delivered-To: [hidden email]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:


> Initial boot worked:    [O]
> Configure network HW:   [O]
> Config network:         [O]
> 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:                 [E]


Given that your installation was a complete success, I do as
usual with reports for successful installations: I close the bug..:-)

Yes, I wrote success, despite the later explanations you
gave. Actually, none of the problems you encountered do really belong
to the installer, except probably the hang solved by blacklisting the
audio driver.

Nearly all of these problems are either known ones (mostly kernel
issues) or general problems (proper support and detection of the
needed drivers for X).

And, yes, your considerations about the difficulties to install Debian
(and indeed any Linux system) on recent hardware are actually
true. This is currently a good method found by proprietary softwrae
vendors to block the progress of free operating systems=A0: encourage
hardware vendors to continue the nightmare of constant hardware
changes (SATA, various Wifi chipsets, incredible number of network
chipsets). This even makes the life of Windows system engineers
difficults actually (just try to install W2K on recent hardware....).

This does not of course mean you weren't right to report. Knowing the
installations are correct or get a general picture of the installation
process seen from users is important for the d-i team.

Many thanks for your time testing the Debian Installer and reporting
your results. Have fun with your new Debian system!



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

Reply | Threaded
Open this post in threaded view
|

Bug#316586: acknowledged by developer (Re: Bug#316586: Package: installation-reports)

Chuck Williams-2
In reply to this post by Chuck Williams-2
Debian Bug Tracking System wrote:

>...
>From: Christian Perrier <[hidden email]>
>  
>
> ...
>
>Given that your installation was a complete success, I do as
>usual with reports for successful installations: I close the bug..:-)
>
>Yes, I wrote success, despite the later explanations you
>gave. Actually, none of the problems you encountered do really belong
>to the installer, except probably the hang solved by blacklisting the
>audio driver.
>
>  
>
Hi Christian,

Thanks for your response.  There is one simple installer issue that I
forgot to write in the original installation report.  I suggest that the
install guide have a paragraph on blacklisting.  This would have saved
me one of the large time-sync/frustration hurdles.

When the installer failed to reboot on the nx9600 I had no idea what to
do.  From the boot messages, I knew immediately there was a problem with
the i810_audio driver.  At that moment, I didn't know this driver was
part of oss and could be safely eliminated.  Once I discovered it could
be eliminated (through Googling) I had no idea how to do it.

Eventually I found some references to "blacklisting".  However, I never
found any description of how to do that.  Frustration was growing.  
Then, I finally found one discussion board thread where somebody talked
about the requirement to blacklist i810_audio in two places:  both
hotplug and discover.  That was finally a clue.

I found the following process to accomplish the blacklisting and am
still uncertain as to whether or not this is the recommended approach.  
Using expert26 install mode, I progressed the installer to the point
just before it rebooted, switched to the virtual console, figured out
where the new root disk was mounted, found /etc on the root disk from
the mount point, looked at files/directories involving hotplug and
discover, homed in on /etc/hotplug/blacklist and /etc/discover.conf,
read those files and edited them to blacklist i810_audio, and then
continued with the boot into the new root.

Given the number of references to blacklisting I found on the web, this
would seem to be a sufficiently common occurrence to warrant an
install-guide note.  I never read the entire install guide, as I suspect
few users do, but it was the first place I turned when there was a
problem.  I text-searched it initially for i810_audio, and soon for
blacklist (and obvious variants like "black").  If the process had been
there, it would have helped a great deal.

Thanks for all your efforts on the installer.  I have a deeper
appreciation of the issues in the installer than this message suggests.  
Prior to installing the nx9600, I tried it on a new Sager 9880.  That
was much more difficult, if not impossible, as I could never the disk
accessible.  I gave up, returned the Sager, and bought the HP instead.  
In the process of trying things on the Sager, I built my own install
packages with custom kernels that contained all the various drivers I
could find that the Sager required (e.g., I needed fixes in libata for a
Promise sata378 tx2plus controller that were only made in 2.6.11 and
2.6.12).  This got me closer to the installer and the various issues it
faces with module lists/correspondences, etc.

Best,

Chuck

//


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