Bug#248011: installation-reports: Partial installation report on Dell Latitude X200 (Firewire CD)

2004-05-15 Thread Gaudenz Steinlin
On Sat, May 08, 2004 at 12:53:40PM -0400, Joey Hess wrote:
 Christian Perrier wrote:
  :02:03.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C551 IEEE 1394 Controller
 
 Discover-data has the following for Ricoh controllers:
 
 11800522unknown unknown R5C522 IEEE 1394 Controller
 11800551unknown unknown R5C551 IEEE 1394 Controller
 11800552unknown unknown R5C552 IEEE 1394 Controller
 
 Can you provide lspci -n output too, so we can see which of these is
 your controller, and make it load ieee1394.

AFAIK to module to load is not ieee1394, but ohci1394 (see below). The
ieee1394 is the common code of all 1394 controllers and when you load one of
the host controller modules with modprobe it is automatically loaded as a
dependeny. 

Gaudenz
 
 FWIW, my firewire controller is this:
 
 00:13.0 FireWire (IEEE 1394): Texas Instruments TSB43AB21 IEEE-1394a-2000 Controller 
 (PHY/Link)
 00:13.0 Class 0c00: 104c:8026
 
 Listed in discover1-data as:
 
 104c8026unknown unknown TSB43AB21 IEEE-1394a-2000 Controller 
 (PHY/Link)
 
 I can load ieee1394 and it finds the controller, I have no firewire
 stuff to test further. discover1-data seems to have a lot of firewire
 controllers that are listed as unknown and so load no module. I don't
 know if the procedure is to wait for a report from a user for each
 before turning it on, or what.
 
  With 2.6 kernel, all went fine as soon as I manually loaded the following
  modules (order is important):
  
  -ieee1394
  -ohci1394
  -sbp2
  -sr_mod
 
 If discover can find the controller, then loading the rest of these
 modules can be taken care of by hw-detect or something.
 
 -- 
 see shy jo




signature.asc
Description: Digital signature


Bug#248011: installation-reports: Partial installation report on Dell Latitude X200 (Firewire CD)

2004-05-09 Thread Christian Perrier
Quoting Joey Hess ([EMAIL PROTECTED]):
 Christian Perrier wrote:
  :02:03.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C551 IEEE 1394 Controller
 
 Discover-data has the following for Ricoh controllers:
 
 11800522unknown unknown R5C522 IEEE 1394 Controller
 11800551unknown unknown R5C551 IEEE 1394 Controller
 11800552unknown unknown R5C552 IEEE 1394 Controller
 
 Can you provide lspci -n output too, so we can see which of these is
 your controller, and make it load ieee1394.

[EMAIL PROTECTED]:~/src/debian/debian-installer/packages/lvmcfg/debian lspci -n
:00:00.0 Class 0600: 8086:3575 (rev 04)
:00:02.0 Class 0300: 8086:3577 (rev 04)
:00:02.1 Class 0380: 8086:3577
:00:1d.0 Class 0c03: 8086:2482 (rev 02)
:00:1d.1 Class 0c03: 8086:2484 (rev 02)
:00:1d.2 Class 0c03: 8086:2487 (rev 02)
: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.3 Class 0c05: 8086:2483 (rev 02)
:00:1f.5 Class 0401: 8086:2485 (rev 02)
:00:1f.6 Class 0703: 8086:2486 (rev 02)
:02:03.0 Class 0607: 1180:0475 (rev b8)
:02:03.1 Class 0c00: 1180:0551
:02:05.0 Class 0200: 10b7:9200 (rev 78)

BTW, I also have a Dell X300 not far from me for testing also (but the
CD is not Firewire on these and thus it works). The problem on that
one is the Broadcom Ethernet controller (firmware problemblah
blah).






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



Bug#248011: installation-reports: Partial installation report on Dell Latitude X200 (Firewire CD)

2004-05-08 Thread Christian Perrier
Package: installation-reports
Severity: normal

Debian-installer-version: beta4 i386 netinst
uname -a: Not run (partial install)
Date: 2004/05/08
Method: Partial install aimed at testing Firewire CD support
  
Machine: Dell Latitude X200 with deck and Firewire CD/DVD
Processor:
Memory: 640Mb
Root Device: N/A
Root Size/partition table: N/A

Output of lspci:

:00:00.0 Host bridge: Intel Corp. 82830 830 Chipset Host Bridge (rev 04)
:00:02.0 VGA compatible controller: Intel Corp. 82830 CGC [Chipset
Graphics Controller] (rev 04)
:00:02.1 Display controller: Intel Corp. 82830 CGC [Chipset Graphics
Controller]
:00:1d.0 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #1) (rev 02)
:00:1d.1 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #2) (rev 02)
:00:1d.2 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #3) (rev 02)
: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.3 SMBus: Intel Corp. 82801CA/CAM SMBus Controller (rev 02)
:00:1f.5 Multimedia audio controller: Intel Corp. 82801CA/CAM AC'97
Audio Controller (rev 02)
:00:1f.6 Modem: Intel Corp. 82801CA/CAM AC'97 Modem Controller (rev 02)
:02:03.0 CardBus bridge: Ricoh Co Ltd RL5c475 (rev b8)
:02:03.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C551 IEEE 1394 Controller
:02:05.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado]
(rev 78)


Base System Installation Checklist:

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

Comments/Problems:

I had to boot with debian-installer/framebuffer=false otherwise the screen
is difficult to read (sync problem?).

With the 2.4 kernel, I failed to find a way to get the CD recognised even by
loading the modules manually (see below). I guess this is because I had no
way to get the SCSI bus rescanned and the needed devices added (see #246790)

With 2.6 kernel, all went fine as soon as I manually loaded the following
modules (order is important):

-ieee1394
-ohci1394
-sbp2
-sr_mod

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (400, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.5-1-686
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (ignored: LC_ALL set to fr_FR.UTF-8)


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



Bug#248011: installation-reports: Partial installation report on Dell Latitude X200 (Firewire CD)

2004-05-08 Thread Joey Hess
Christian Perrier wrote:
 :02:03.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C551 IEEE 1394 Controller

Discover-data has the following for Ricoh controllers:

11800522unknown unknown R5C522 IEEE 1394 Controller
11800551unknown unknown R5C551 IEEE 1394 Controller
11800552unknown unknown R5C552 IEEE 1394 Controller

Can you provide lspci -n output too, so we can see which of these is
your controller, and make it load ieee1394.

FWIW, my firewire controller is this:

00:13.0 FireWire (IEEE 1394): Texas Instruments TSB43AB21 IEEE-1394a-2000 Controller 
(PHY/Link)
00:13.0 Class 0c00: 104c:8026

Listed in discover1-data as:

104c8026unknown unknown TSB43AB21 IEEE-1394a-2000 Controller (PHY/Link)

I can load ieee1394 and it finds the controller, I have no firewire
stuff to test further. discover1-data seems to have a lot of firewire
controllers that are listed as unknown and so load no module. I don't
know if the procedure is to wait for a report from a user for each
before turning it on, or what.

 With 2.6 kernel, all went fine as soon as I manually loaded the following
 modules (order is important):
 
 -ieee1394
 -ohci1394
 -sbp2
 -sr_mod

If discover can find the controller, then loading the rest of these
modules can be taken care of by hw-detect or something.

-- 
see shy jo


signature.asc
Description: Digital signature