xboxscene.org forums

Pages: [1] 2

Author Topic: Xdsl Problem  (Read 157 times)

avstheman

  • Archived User
  • Newbie
  • *
  • Posts: 3
Xdsl Problem
« on: May 23, 2005, 10:53:00 PM »

any help?
Logged

t0m

  • Archived User
  • Jr. Member
  • *
  • Posts: 75
Xdsl Problem
« Reply #1 on: May 23, 2005, 11:03:00 PM »

what other stuff have you tried? a common problem seems to be the IR reciver for the dvd remote being plugged in...if you have one try unplugging it if you havnt already...or try booting your xbox with just your usb keuboard/mouse plugged in (no controllers) and load dsl that way (your arrow/enter/backspace keys on the kb work in evox). does the kb work in evox or any other apps?

not sure what else to suggest...good luck. blink.gif
Logged

friedgold

  • Archived User
  • Sr. Member
  • *
  • Posts: 266
Xdsl Problem
« Reply #2 on: May 24, 2005, 10:57:00 AM »

What type of controller is it? Not every 3rd party controller is supported. Also are you sure the usb port works ok (i.e. have you had a usb device working with your Xbox before). Do you have your usb keyboard plugged directly into the port or do you have a usb hub? Does the keyboard work in windows without drivers or do you need to load anything to use it?

Do you have the ability to ssh into X-DSL as this would help diagnose the problem.
Logged

avstheman

  • Archived User
  • Newbie
  • *
  • Posts: 3
Xdsl Problem
« Reply #3 on: May 24, 2005, 01:08:00 PM »

i tried every combination of unplugging/plugging in all the devices. i took out the dvd receiver so thats not a problem. the controller is an s-type... also tried the original big controllers with no luck. the keyboard works fine in windows, no drivers needed, and even works fine in evox, but when i go to xdsl, it doesnt work... i dont know what the problem is
Logged

LESTAT

  • Archived User
  • Hero Member
  • *
  • Posts: 794
Xdsl Problem
« Reply #4 on: May 24, 2005, 01:47:00 PM »

you need to be using a different keybaord.

some keyboards just dont work with the xbox.

this is about the only thing i can think of.
i actually have one that wont work at all. so i had to switch to a different one.
Logged

avstheman

  • Archived User
  • Newbie
  • *
  • Posts: 3
Xdsl Problem
« Reply #5 on: May 24, 2005, 07:00:00 PM »

it doesnt matter about the keyboard, i cant even use the controller...
no good with the different minirt24.gz... thanks though. i really dont know what the problem is with this.
Logged

friedgold

  • Archived User
  • Sr. Member
  • *
  • Posts: 266
Xdsl Problem
« Reply #6 on: May 25, 2005, 10:37:00 AM »

Sorry to hear it still isn't working for you sad.gif.

Really with the Xbox we shouldn't be getting these kind of problems since everyone's hardware is roughly the same. I would expect these kind of things to either not work at all or work on everyones Xbox, so this has got me stumped.

If you are able to ssh into your Xbox with X-DSL running that might help us get to the bottom of this problem. You'll need to do a ftp install and add the cheatcode ssh into linuxboot.cfg (see CHEATCODES.txt for more info). You then need to use a ssh client (if you using windows try putty) to connect to you Xbox's ip address with the username root, pass xbox.

I'd be interested in the result of lsmod (should show all the loaded modules), dmesg (shows any errors loading modules) and also what happens if you load the modules manually (modprobe hid, modprobe xpad).
Logged

xboxxxxx-linuxxxxx

  • Archived User
  • Newbie
  • *
  • Posts: 1
Xdsl Problem
« Reply #7 on: June 01, 2005, 04:06:00 PM »

Hi

My problem is quite the same.

My keyboard and mouse are detected by "xdsl" but I can only use my keyboard as a mouse and my mouse can only be used for cliks and not for roll.

I tried everything that you said:

Only plug the mouse and keyboard
Change the mouse and keyboard to try with other ones
Replacing my .gz file


So I was at the last solution, ssh

I added the "2" and the "ssh" cheats to my "linuxconfig" file

**is     "2 ssh" before the word "frugal" is all I have to add or is there more to add????***


Then I booted my xdsl with those 2 cheats added

The linux boots but stops at the line:

mnt/auto/cdrom : not mounted

The problem is that I can't see the line ater cause my frame buffers are not changed.

Is there a line after the:
mnt/auto/cdrom : not mounted

?????

So I decided to change my video buffers to see the next line but I need to write "fbset" in text mode adding the "2" cheat.

The problem is that xdsl stops at the same line and I can't write "fbset"

And even if I had the chance to write it, my keyboard is detected but can't write letters


The last point

Is there another way to "ssh" with xdsl else then adding the "ssh" and the "2" cheats??


Thanks
Logged

spuckigel

  • Archived User
  • Newbie
  • *
  • Posts: 9
Xdsl Problem
« Reply #8 on: July 23, 2005, 03:46:00 PM »

hi there, i've got the same problem. i have an s-controller, and its is not able to move the mouse pointer. even before, where you choose between "live cd" or "e:\knoppix", i cant choose between either, because the thing is not responding. so it just loads after 30secs the installation on e:\.

one other thing is that my scrren seems to be deadjusted, i cant see the stuff on the left side. i thinkm this has to do with the xcalibur on the 1.6 xboxes?

so, if anybody would have a solution for the mouse problem, that would be really good and help me much. thanx a lot...


---
edt: while i was typing this, i left the xbox on its own. the linux seems to have an screen saver, which turned on, its all black. not surprisingly i am not able to wake it up by pressing any buttons of the controller. and, in-game-reset is not working neither. so there must be a total failure in adressing the controller (maybe a v1.6 related problem?)
Logged

friedgold

  • Archived User
  • Sr. Member
  • *
  • Posts: 266
Xdsl Problem
« Reply #9 on: July 23, 2005, 03:58:00 PM »

QUOTE(spuckigel @ Jul 23 2005, 11:57 PM)
hi there, i've got the same problem. i have an s-controller, and its is not able to move the mouse pointer. even before, where you choose between "live cd" or "e:\knoppix", i cant choose between either, because the thing is not responding. so it just loads after 30secs the installation on e:\.
Logged

spuckigel

  • Archived User
  • Newbie
  • *
  • Posts: 9
Xdsl Problem
« Reply #10 on: July 23, 2005, 05:08:00 PM »

ok, i was able to ssh onto the xbox. i tried to manually load hid and xpad, but it didnt help (still no mouse response)


as for the loaded modules, i got these:

CODE

root@0[root]# lsmod
Module                  Size  Used by    Not tainted
xpad                    7984   0 (unused)
mousedev                3768   1
hid                    22180   0 (unused)
joydev                  6944   0
input                   3040   0 [xpad mousedev hid joydev]
nls_iso8859-1           2876   0 (autoclean)
i810_audio             21848   1
ac97_codec             12140   0 [i810_audio]
soundcore               3236   2 [i810_audio]
forcedeth               9516   1
serial                 43652   0 (autoclean)
usb-ohci               16136   0 (unused)
usbcore                55392   1 [xpad hid usb-ohci]
cloop                   9796   2




CODE

root@0[root]# dmesg
de: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
NFORCE: IDE controller at PCI slot 00:09.0
NFORCE: chipset revision 212
NFORCE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
NFORCE: 00:09.0 (rev d4) UDMA100 controller
    ide0: BM-DMA at 0xff60-0xff67, BIOS settings: hda:DMA, hdb:DMA
hda: C/H/S=0/0/0 from BIOS ignored
hdb: C/H/S=0/0/0 from BIOS ignored
hda: SAMSUNG SP1614N, ATA DISK drive
hdb: HL-DT-STDVD-ROM GDR8050L, ATAPI CD/DVD-ROM drive
blk: queue c02ed040, I/O limit 4095Mb (mask 0xffffffff)
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: attached ide-disk driver.
hda: host protected area => 1
hda: 312581808 sectors (160042 MB) w/8192KiB Cache, CHS=19457/255/63, UDMA(33)
hdb: attached ide-cdrom driver.
hdb: ATAPI 52X DVD-ROM drive, 256kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.12
Partition check:
 hda: unknown partition table
 hda50 hda51 hda52 hda53 hda54 hda55bh with no client!?
bh with no client!?
i2c-core.o: driver i2c xbox-extsmi driver registered.
extsmi: Using 'SMBus AMD756 adapter at c000'!
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 4096)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 107k freed
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 96k freed
Unable to identify CD-ROM format.
VFS: Can't find ext2 filesystem on dev ide0(3,0).
FATX: boot block signature not found.  Not FATX?
hdb: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdb: packet command error: error=0x54
ATAPI device hdb:
  Error: Illegal request -- (Sense key=0x05)
  (vendor-specific error) -- (asc=0x81, ascq=0x00)
  The failed "Start/Stop Unit" packet command was:
  "1b 00 00 00 03 00 00 00 00 00 00 00 "
cdrom: open failed.
hdb: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdb: packet command error: error=0x54
ATAPI device hdb:
  Error: Illegal request -- (Sense key=0x05)
  (vendor-specific error) -- (asc=0x81, ascq=0x00)
  The failed "Prevent/Allow Medium Removal" packet command was:
  "1e 00 00 00 00 00 00 00 00 00 00 00 "
hdb: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdb: packet command error: error=0x54
ATAPI device hdb:
  Error: Illegal request -- (Sense key=0x05)
  (vendor-specific error) -- (asc=0x81, ascq=0x00)
  The failed "Start/Stop Unit" packet command was:
  "1b 00 00 00 03 00 00 00 00 00 00 00 "
cdrom: open failed.
hdb: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdb: packet command error: error=0x54
ATAPI device hdb:
  Error: Illegal request -- (Sense key=0x05)
  (vendor-specific error) -- (asc=0x81, ascq=0x00)
  The failed "Prevent/Allow Medium Removal" packet command was:
  "1e 00 00 00 00 00 00 00 00 00 00 00 "
hdb: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdb: packet command error: error=0x54
ATAPI device hdb:
  Error: Illegal request -- (Sense key=0x05)
  (vendor-specific error) -- (asc=0x81, ascq=0x00)
  The failed "Start/Stop Unit" packet command was:
  "1b 00 00 00 03 00 00 00 00 00 00 00 "
cdrom: open failed.
hdb: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdb: packet command error: error=0x54
ATAPI device hdb:
  Error: Illegal request -- (Sense key=0x05)
  (vendor-specific error) -- (asc=0x81, ascq=0x00)
  The failed "Prevent/Allow Medium Removal" packet command was:
  "1e 00 00 00 00 00 00 00 00 00 00 00 "
Unable to identify CD-ROM format.
VFS: Can't find ext2 filesystem on dev ide0(3,50).
cloop: Initializing cloop v2.01
cloop: loaded (max 8 devices)
cloop: /cdrom/KNOPPIX/KNOPPIX: 1544 blocks, 65536 bytes/block, largest block is 65552 bytes.
ISO 9660 Extensions: RRIP_1991A
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.275 $ time 18:18:29 May  4 2005
usb-uhci.c: High bandwidth mode enabled
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
usb.c: deregistering driver usbdevfs
usb.c: deregistering driver hub
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
PCI: Setting latency timer of device 00:02.0 to 64
usb-ohci.c: USB OHCI at membase 0xc5eb9000, IRQ 1
usb-ohci.c: usb-00:02.0, nVidia Corporation nForce USB Controller
usb.c: new USB bus registered, assigned bus number 1
usb-ohci.c: request interrupt 1 failed
usb.c: USB bus 1 deregistered
Trying to vfree() nonexistent vm area (c5eb9000)
PCI: Setting latency timer of device 00:03.0 to 64
usb-ohci.c: USB OHCI at membase 0xc5eb9000, IRQ 9
usb-ohci.c: usb-00:03.0, nVidia Corporation nForce USB Controller (#2)
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
usbdevfs: remount parameter error
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled
PCI: Enabling device 00:06.1 (0000 -> 0003)
PCI: No IRQ known for interrupt pin B of device 00:06.1. Please try using pci=biosirq.
forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.30.
PCI: Setting latency timer of device 00:04.0 to 64
eth0: forcedeth.c: subsystem: 00000:0000 bound to 00:04.0
Intel 810 + AC97 Audio, version 1.01, 18:17:44 May  4 2005
PCI: Setting latency timer of device 00:06.0 to 64
i810: NVIDIA nForce Audio found at IO 0xd200 and 0xd000, MEM 0x0000 and 0x0000, IRQ 6
i810_audio: Audio Controller supports 6 channels.
i810_audio: Defaulting to base 2 channel mode.
i810_audio: Resetting connection 0
ac97_codec: AC97  codec, id:  (Unknown)
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 25M
agpgart: Unsupported NVIDIA chipset (device id: 02a5), you might want to try agp_try_unsupported=1.
agpgart: no supported devices found.
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 25M
agpgart: Trying generic NVIDIA routines for device id: 02a5
agpgart: agpgart: Detected an NVIDIA nForce/nForce2 chipset, but could not find the secondary devices.
agpgart: no supported devices found.
VFS: Can't find ext3 filesystem on dev ide0(3,51).
VFS: Can't find ext2 filesystem on dev ide0(3,51).
Unable to identify CD-ROM format.
sh-2021: reiserfs_read_super: can not find reiserfs on ide0(3,51)
VFS: Can't find ext3 filesystem on dev ide0(3,52).
VFS: Can't find ext2 filesystem on dev ide0(3,52).
Unable to identify CD-ROM format.
sh-2021: reiserfs_read_super: can not find reiserfs on ide0(3,52)
VFS: Can't find ext3 filesystem on dev ide0(3,53).
VFS: Can't find ext2 filesystem on dev ide0(3,53).
Unable to identify CD-ROM format.
sh-2021: reiserfs_read_super: can not find reiserfs on ide0(3,53)
VFS: Can't find ext3 filesystem on dev ide0(3,54).
VFS: Can't find ext2 filesystem on dev ide0(3,54).
Unable to identify CD-ROM format.
sh-2021: reiserfs_read_super: can not find reiserfs on ide0(3,54)
VFS: Can't find ext3 filesystem on dev ide0(3,55).
VFS: Can't find ext2 filesystem on dev ide0(3,55).
Unable to identify CD-ROM format.
sh-2021: reiserfs_read_super: can not find reiserfs on ide0(3,55)
i810_audio: only 48Khz playback available.
i810_audio: AC'97 codec 0 Unable to map surround DAC's (or DAC's not present), total channels = 2
usb.c: registered new driver hiddev
usb.c: registered new driver hid
hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik
hid-core.c: USB HID support drivers
mice: PS/2 mouse device common for all mice
usb.c: registered new driver xpad
xpad-core.c: driver for Xbox controllers with mouse emulation v0.1.5


i hope someone is able to "debug" this huge text information, as it doenst make much sense for me... thanx for your help
Logged

friedgold

  • Archived User
  • Sr. Member
  • *
  • Posts: 266
Xdsl Problem
« Reply #11 on: July 23, 2005, 06:00:00 PM »

Well the xpad module seems to have loaded ok, but just not detected any xpads. For reference you would usually get something like this as the output of dmesg:

QUOTE
usb.c: registered new driver xpad
xpad-core.c: MS Xbox Controller S
xpad-mouse.c: Mouse Emulation @ MS Xbox Controller S
xpad-core.c: MS Xbox Controller
xpad-mouse.c: Mouse Emulation @ MS Xbox Controller
xpad-core.c: driver for Xbox controllers with mouse emulation v0.1.5


Could you try ssh'ing into you Xbox again but this time using lsusb. This lists the vendor/product id's of any connected peripherals. It maybe that you have newer revision of the S controller with a different id??? Run lsusb with the xpad disconnected and then run it again with it plugged in. When the xpad is plugged in you should see two new entries in the following form:

QUOTE
Bus 001 Device 002: ID 045e:0288 MS Corp.
Bus 001 Device 005: ID 045e:0289 MS Corp.


One will be for the controller itself and one for the controller's built in hub. What output do you get when you try this? For the controller to work the product/vendor id's must be listed here. If it's not it can easily be added.
Logged

spuckigel

  • Archived User
  • Newbie
  • *
  • Posts: 9
Xdsl Problem
« Reply #12 on: July 24, 2005, 03:21:00 AM »

ok, first thing which i maybe didnt prompt out exactly: the xpad demon has been loaded manually, after that i did the dmesg listing. i dont know for sure if that is important.

and this is my linuxboot.cfg

CODE
title 640x480
kernel linux24
initrd minirt24.gz
append root=/dev/ram0 init=/etc/init rw video=xbox:640x480 frugal lang=de norestore joy ssh eth0=192.168.178.25,255.255.255.0,192.168.178.1,64.59.160.13

anything incorrect in here? it didnt work with the original settings, so i started to try stuff here first, like loading country specific kbd, matching IP adress etc. one idea might be the counrty/region code of the box. i heard some games refuse to play when the region code is not matching their default? where do i check this?

so, i did another ssh session this morning (funny thing happend. as i have xbmc as dashboard and its usually working excellent, i seem not to be able to start the linux loader (default.xbe on e:\) anymore with xbmc. i had to start another file manager through xbmc and then start the linux loader.  no idea what caused this, and its still not working any more).

i started the x-dsl without controller connected, this is the lsusb result:

CODE
root@0[root]# lsusb
Bus 001 Device 001: ID 0000:0000


looks like nothing connected. same result when controller pluged in again. no plug and play? same after loading xpad manually and trying lsusb again.

ok, i started again with controller connected, and confusingly, got the same printout.

CODE

root@0[root]# lsusb
Bus 001 Device 001: ID 0000:0000


what does that mean? do v1.6 xboxes have different usb controllers in the chipset and the linux kernel (or modules) are not able to address them? by the way, my xbox is quite new, got it in april, the label says "manufactured in mar 05". maybe a new revision :-) v1.7?
Logged

manu_xl

  • Archived User
  • Sr. Member
  • *
  • Posts: 393
Xdsl Problem
« Reply #13 on: July 24, 2005, 03:40:00 AM »

maybe a silly remark ... but those input devices like a controller, keyboard, ... have to be plugged in before you launch xdsl
Logged

friedgold

  • Archived User
  • Sr. Member
  • *
  • Posts: 266
Xdsl Problem
« Reply #14 on: July 24, 2005, 08:08:00 AM »

QUOTE
PCI: Setting latency timer of device 00:02.0 to 64
usb-ohci.c: USB OHCI at membase 0xc5eb9000, IRQ 1
usb-ohci.c: usb-00:02.0, nVidia Corporation nForce USB Controller
usb.c: new USB bus registered, assigned bus number 1
usb-ohci.c: request interrupt 1 failed
usb.c: USB bus 1 deregistered


where as at the same point in the boot process I get

QUOTE
PCI: Setting latency timer of device 00:02.0 to 64
usb-ohci.c: USB OHCI at membase 0xc5eb9000, IRQ 1
usb-ohci.c: usb-00:02.0, nVidia Corporation nForce USB Controller
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 4 ports detected


I'm not really sure the best way to solve this issue. You say the controller won't work in Cromwell either so I doubt this is just a issue with how X-DSL is configured. It might be best to post your problem to the xbox-linux mailing list.
Logged
Pages: [1] 2