[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: d-i via floppy/usb/netinst.iso, cleaned up version



Joey Hess wrote:

Gerhard Kroder wrote:

So, reading from usb is not the issue?

Sure sounds like it's not.
is it worth tracking meanwhile obsoleted images? or should i better get
new/current images?

Perhaps it is using the wrong usb driver, or
wrongly configuring it. Could you look at the boot messages before it
asks you to hit enter, and compare them to the boot messages on the
working system? In particular the ones about usb-ohci or usb-uhci, and
anything else usb releasted.
do you know any other way than typing it manually from screen? things like console/serial log/copy at this stage? some lot work...

ok, so bootfloppy says to usb related things (and some others of some
importance, imho): [i replaced some unimportant message parts with "[..]","..." and the like, and added some comments, you'll recognice easily. Output now nearly as it shows up on console:

--->start console message<---
Mounted devfs on /dev [..]
mount: Mounting devfs on /dev failed:
Device or ressource busy [..]
Using /lib/.....usbcore
usb.c: registered.... usbdevfs
.......registered.... hub
Using .....usb-ohci.o
us-ohci: USB OHCI at membase 0xcc83d000, IRQ10 .....usb-00:14.0, ALi
Corp USB 1.1 Controller
usb.c:...new USB bus registered, assigned bus number 1
....USB hub found ....2 ports detected
Using /lib/..2.4.22-1-386../input.o
Using /lib/..../usbkbd.o
usb.c: registered new driver usbkbd
usbkbd.c: USB HID Boot Protocol keyboard driver
Using /lib/...keybdev.o
Using /lib/...usbserial.o
usb.c: registered new driver serial
usbserial.c: ..... registered for Generic
...... Driver core 1.4
[..]
SCSI subsystem driver Revision: 1.00
Initializing USB Mass Storage driver....
usb.c: registered new driver
usb-storage USB Mass Storage support registered


Insert the root floppy or plug in a USB storage device. Press Enter when ready, or type a
command:
--->end console message<---


now i plug in usb device:

--->start console message<---
new USB device 00:14.0-1, assingned address 2
...SCSI emulation...
...<messages already posted about PRIVHEAS errors>
unable to read partition table
--->end console message<---

so now i hit Enter as requested, d-i starts reading from usb with
already posted result.

ok, now what knoppix 3.3 cd (as reference system) tells about usb:

--->start console message<---
[..]
...usbdevfs
...hub
[..]
usb-uhci.c: $Revision: 1.275 $
usb-uhci.c: High bandwith mode enabled
usb-uhci.c: v1.275: Universal Host Controller Interface driver
usb-ohci.c: USB OHCI at membase 0xccaa4000, IRQ 10
usb-ohci.c: usb-00:14.o, ALi Corp USB 1.1 Controller
usb.c: new USB bus registered, assigned bus number 1
usb.c: USB hub found
hub.c: 2 ports detected
--->end console message<---


thisone may come from knoppix autodect, as there is no usb device plugged in yet:

--->start console message<---
usbdevfs: remount parameter error
--->end console message<---

now plugging usb device dmesg says:

--->start console message<---
usb.c: new USB device 00:14.0-1, assigned address 2
usb.c: USB device 2 (vend/prod 0xea0/0x6803) is not claimed by any other driver
Initializing USB Mass Storage driver....
usb.c: registereed new driver
usb-storage...
... SCSI emulation...
[..]
[...<already known PRIVHEAD errors>...]
unable to read partition table
USB Mass storage foung at 2 USB
Mass storage registered.
[..]
--->end console message<---


so, to me it looks quite the same. forgive me not testing my second pc
on that, but that's the one im writing now this mail...

my native debian system on this laptop instead of knoppix tells me about
usb-ohci membase/IRQ assignment too, thoug it later also has msg on uhci
High bandwith mode. plugging device gives same usb device path/address
and scsi emulatin message as above.


i'll try to dd hdimage t a partition instead of whole device to see, if
some errors are solved then. and i'll go get more recent images of
floppy/netinst, if you don't mind. reports later.


btw: any idea on #225654 yet?


gerhard






Reply to: