Problem booting

[Konrad Neuwirth]

More on this: 

Am 27.11.2011 um 06:39 schrieb Chris Turner:

> On 11/22/11 04:13, Konrad Neuwirth wrote:
> 
>> The keyboard the devices has is well recognized; but after the ums0 probe,
> > nothing happens.
> > Theoretically, there should still be a CD Rom attachment on the
> > device; that is what I'm trying to boot off.
> 
> Is the ums port the CD device being mis-recognized
> or is this some kind of virtual mouse device?
> 
> If it is a virtual mouse or similar, you might want to
> disable this device and retry - if it is the CD - you might wish to boot
> another OS that works and provide the usb and PCI device info
> (e.g. 'usbdevs -lv' / 'pciconf -lv' on dragonfly ) -
> perhaps some simple device ID's are missing somewhere that could be added.

I've now had success in installing NetBSD on that machine, which recognized the pseudo-CD right away. 

usbdevs -dv reports the following (appropriately snipped): 

| petzval# usbdevs -dv
| Controller /dev/usb0:
| Controller /dev/usb1:
| addr 1: high speed, self powered, config 1, EHCI root hub(0x0000), vendor 0x8086(0x8086), rev 1.00
|  uhub1
| port 1 addr 2: high speed, self powered, config 1, product 0x0024(0x0024), vendor 0x8087(0x8087), rev 0.00
|  uhub2
| port 1 powered
| port 2 powered
| port 3 powered
| port 4 powered
| port 5 addr 3: high speed, self powered, config 1, Multidevice(0x0002), Peppercon AG(0x14dd), rev 0.01, serial 58A7153FDE5EA0209BF3268C1CFEADF0
|     uhidev0
|     uhidev1
|     umass0
|   port 6 powered
|   port 7 powered
|   port 8 powered
|  port 2 powered

In dmesg, umass0 is the following: 

| umass0 at uhub2 port 5 configuration 1 interface 2
| umass0: Peppercon AG Multidevice, rev 2.00/0.01, addr 3
| umass0: using SCSI over Bulk-Only
| scsibus0 at umass0: 2 targets, 1 lun per target
| umass0 at uhub2 port 5 configuration 1 interface 2
| umass0: Peppercon AG Multidevice, rev 2.00/0.01, addr 3
| umass0: using SCSI over Bulk-Only
| scsibus0 at umass0: 2 targets, 1 lun per target

Does that help anybody to include the device configuration stuff so that the machine finds its root when booting? 

Thank you,
 Konrad