I did buy an optical mouse & Gigabyte keyboarI.
On my SAM 460ex booting with the optical USB dongle plugged in invariably bring the CLI window up after having opened the AOS4.1 log screen.
I don't seem the only one having these problems: there was a thread about this on Amigans website.
What can i do or hope for?
Re: Optical mouse& keyboard problems
Posted: Fri Feb 14, 2014 4:24 pm
by javierdlr
JosDuchIt wrote:I did buy an optical mouse & Gigabyte keyboarI.
On my SAM 460ex booting with the optical USB dongle plugged in invariably bring the CLI window up after having opened the AOS4.1 log screen.
I don't seem the only one having these problems: there was a thread about this on Amigans website.
What can i do or hope for?
Hi
Does it happens ALWAYS?
Try disabling USB ohci module (comment out in Kicklayout) if not already done, letting only USB uhci & ehci modules load/start.
With update5, update6? Maybe trying to rvert to a prevous USBxxxxx kicklayout files solves it. If you can, try with Update5.
When you get on the system CLI try to see what DumpDebugBuffer tool outputs or post it here if you can.
Re: Optical mouse& keyboard problems
Posted: Sat Feb 15, 2014 2:30 pm
by JosDuchIt
@javier
It does not happen always
Pracically always after some crash or freeze (whether you reboot warmor cold)
Rarely when you just reboot Ctl Amiga Amiga
I commented out ohci, and maybe there is some progresbut not much The problem is certainly not gone
Dumpdebugbudffer output when the CLI showed up is below.(ohcicomented out)
Maybe trying to rvert to a prevous USBxxxxx kicklayout files solves it. If you can, try with Update5.
Can you explain which files exactly?
Please note this too:
withou uncommenting i could not boot when an USB stick was pluggd in: the USB stick reading out never stopped.
Now i can boot in some cases but the same problem reappears in other cases, durring "scanning for USB storage devices" boot phase.
w
Hidden Text - Click to Show :
msr = 0x00001030
rtg.library PPC460ex optimizations enabled
RadeonHD (2): Graphics card name is: Radeon HD 6450
RadeonHD (2): Identified the chipset as: CAICOS
RadeonHD (2): If - and only if - your card does not work or does not work optimally
please contact Hans de Ruiter at hans --email-sign-- hdrlab.org.nz to help rectify this.
Use the subject: 0x6779:0x174B:0xE204: <name of board>
and *please* describe the problems you are seeing
in your message.
RadeonHD.chip (0): Object: ID: 310C name: HDMI_TYPE_A type: 3 id: C
RadeonHD.chip (0): Object: ID: 3104 name: DUAL_LINK_DVI_D type: 3 id: 4
RadeonHD.chip (0): Object: ID: 3105 name: VGA type: 3 id: 5
RadeonHD.chip (0):
RadeonHD.chip (0): --------------------------------------
RadeonHD.chip (0): CONNECTOR TABLE:
RadeonHD.chip (0):
RadeonHD.chip (0): Connector[0] HDMI 1:
RadeonHD.chip (0): Type: RHD_CONNECTOR_HDMI_A
RadeonHD.chip (0): DDC bus: RHD I2C line 1
RadeonHD.chip (0): HPD: RHD_HPD_3 (monitor not connected)
RadeonHD.chip (0): Outputs:
RadeonHD.chip (0): Output AtomOutputUniphyD:
RadeonHD.chip (0): Type: RHD_OUTPUT_UNIPHYD
RadeonHD.chip (0): Device Type: atomDFP1
RadeonHD.chip (0): Device Record: Type: atomDFP1, Connector Type: RHD_CONNECTOR_HDMI_A, ConnectorID: 0xC, EncoderID: 0x20
RadeonHD.chip (0):
RadeonHD.chip (0): Connector[1] DVI-D 1:
RadeonHD.chip (0): Type: RHD_CONNECTOR_DVI
RadeonHD.chip (0): DDC bus: RHD I2C line 3
RadeonHD.chip (0): HPD: RHD_HPD_0 (monitor connected)
RadeonHD.chip (0): Outputs:
RadeonHD.chip (0): Output AtomOutputUniphyA:
RadeonHD.chip (0): Type: RHD_OUTPUT_UNIPHYA
RadeonHD.chip (0): Device Type: atomDFP2
RadeonHD.chip (0): Device Record: Type: atomDFP2, Connector Type: RHD_CONNECTOR_DVI, ConnectorID: 0x4, EncoderID: 0x1E
RadeonHD.chip (0):
RadeonHD.chip (0): Connector[2] VGA 1:
RadeonHD.chip (0): Type: RHD_CONNECTOR_VGA
RadeonHD.chip (0): DDC bus: RHD I2C line 0
RadeonHD.chip (0): HPD: RHD_HPD_NONE
RadeonHD.chip (0): Outputs:
RadeonHD.chip (0): Output AtomOutputDACA:
RadeonHD.chip (0): Type: RHD_OUTPUT_DACA
RadeonHD.chip (0): Device Type: atomCRT1
RadeonHD.chip (0): Device Record: Type: atomCRT1, Connector Type: RHD_CONNECTOR_VGA, ConnectorID: 0x5, EncoderID: 0x15
RadeonHD.chip (0):
RadeonHD.chip (0): --------------------------------------
RadeonHD.chip (0):
RadeonHD.chip (0): RadeonHD card successfully opened
Scanning bus 'HDMI 1'
RadeonHD.chip (0): hw_i2c error (2)
RadeonHD.chip (0): hw_i2c error (2)
RadeonHD.chip (0): hw_i2c error (2)
failed.
Scanning bus 'DVI-D 1'
0000: 00 FF FF FF FF FF FF 00 22 F0 36 29 01 01 01 01 ........".6)....
0010: 28 15 01 03 80 30 1B 78 2A 95 25 A1 59 57 9F 27 (....0.x*.%.YW.'
0020: 0D 50 54 A1 08 00 81 C0 81 80 95 00 B3 00 D1 C0 .PT.............
0030: 01 01 01 01 01 01 02 3A 80 18 71 38 2D 40 58 2C .......:..q8-@X,
0040: 45 00 DC 0C 11 00 00 1E 00 00 00 FD 00 32 4C 18 E............2L.
0050: 5E 11 00 0A 20 20 20 20 20 20 00 00 00 FC 00 48 ^..............H
0060: 50 20 32 32 31 31 0A 20 20 20 20 20 00 00 00 FF P.2211..........
0070: 00 43 4E 54 31 34 30 33 32 4E 4A 0A 20 20 00 1D .CNT14032NJ.....
EDID V1.3
ManufacturerID HWP ProductID 2936
SerialNo 16843009 Manufactured week 40 of 2011
Input type digital
Display gamma 2.20
Maximum Image Size 48x27cm
PowerManagement Standby no Suspend no ActiveOff yes
Monitor Name HP 2211
Serial Number CNT14032NJ
Established timings:
800x600@60
640x480@60
720x400@70
1024x768@60
Standard Timing Identification:
1280x720@60hz (16:9)
1280x1024@60hz (5:4)
1440x900@60hz (16:10)
Not Found: 1440x900@60hz (16:10) - calling CVT(RB=1)
1680x1050@60hz (16:10)
Not Found: 1680x1050@60hz (16:10) - calling CVT(RB=1)
1920x1080@60hz (16:9)
It does not happen always
Pracically always after some crash or freeze (whether you reboot warmor cold)
Rarely when you just reboot Ctl Amiga Amiga
So, when you cold boot (reset button) sometimes Uboot says/shows only 'USB devices: 1' plugged.
Here happens too sometimes when system has a hard crash/freeze, upon reseting my SAM460ex I only get 'USB devices: 1', have to power off and power on machine and it shows again USB devices: 5'
I commented out ohci, and maybe there is some progresbut not much The problem is certainly not gone
Dumpdebugbudffer output when the CLI showed up is below.(ohcicomented out)
If you use AmiUpdate you can rollback USB, but forget what I said, maybe is causes too much trouble mixing old/new usb libs/modules.
withou uncommenting i could not boot when an USB stick was pluggd in: the USB stick reading out never stopped.
Now i can boot in some cases but the same problem reappears in other cases, durring "scanning for USB storage devices" boot phase.
IIRC it was massstorage problem (solved on latest update).
