Topic: Xdsl 0.7 Beta Released! (Read 458 times)

bassquake · « **Reply #30 on:** January 14, 2009, 03:40:00 PM »

Hi.

I got this wireless keyb/mouse device.

But it doesnt work in xdsl. It works in Ubuntu 8.04-64 on a pc, so is it possible to somehow get the drivers or usb stack used in Ubuntu and use it in xdsl? Or is it a hardware issue? The keyboard doesnt work in xbmc. It works on the 360 though.

ps. How do I view the boot info as something pops up about it but it goes too quick to view it properly.

All in all, ace job, thanks.

brandogg · « **Reply #31 on:** January 14, 2009, 10:30:00 PM »

If it's plug & play, then it should work. I use some generic wireless eyboard/mouse from Wal-Mart, it works fine for me. Also, if it doesn't work in XBMC, then it probably won't work in xDSL, at least not without some drivers.

defyboy · « **Reply #32 on:** January 15, 2009, 12:29:00 AM »

Well, I did that. Now I get a Blank black screen followed by a blue screen, Any suggestions on how to repair this?

bassquake · « **Reply #33 on:** January 15, 2009, 06:36:00 AM »

QUOTE

If it's plug & play, then it should work. I use some generic wireless eyboard/mouse from Wal-Mart, it works fine for me. Also, if it doesn't work in XBMC, then it probably won't work in xDSL, at least not without some drivers.

Yes, the keyboard is plug n play. No drivers are needed for Xp, vista or ubuntu. So I dont know why its not working on the xbox yet does on 360.

Do you know what make your keyb/mouse combo is?

bassquake · « **Reply #34 on:** January 15, 2009, 10:18:00 AM »

Carrying on about my wireless keyboard. I notice on bootup, the following is stated:

QUOTE

cloop: Initializing cloop v2.02
usb.c: unable to get device descriptor (error=-110)
usb.c: unable to get device descriptor (error=-110)
INIT: Entering runlevel: 5
usb.c: unable to get device descriptor (error=-110)
usb.c: USB device 22 (vend/prod 0x45e/0x284) is not claimed by any driver.
Starting X...

So its detecting it, but cant find info for it.

I found this site which mentions some people having trouble with it in Ubuntu:

http://ubuntuforums....p/t-356280.html

I tried adding that info to the /etc/X11/xorg.conf to no avail.

Also please can someone tell me where the info that loads up during boot is saved somewhere like a boot log. Thanks.

Any help appreciated.

ps. Should I start my own thread on this?

brandogg · « **Reply #35 on:** January 15, 2009, 02:09:00 PM »

I believe it's made by Micro Innovations or some crap like that. Have you tried simply using a different USB port? Sometimes xDSL acts weird for me and I have to switch ports, even if was already working during the current session.

Red_Breast · « **Reply #36 on:** January 15, 2009, 11:54:00 PM »

I just tried with a composite lead plugged into a line-doubler with VGA output and it's working. I'm sure I used a component to VGA adaptor last time but that must be the problem. It's not so bad as I can set it to XGA 1024x768. Helps. A little. Slightly. I think.
I do have a Frozen cable which I can use on another Sony monitor (SoG 4:3) with Krayzie's extras but I've never got it working on the usual monitor I use for Xbox (not SoG) with any of Frosty's apps. I believe it supports all VGA IDs.
I think I'll just look out for a cheap KVM switch or something as I like to use the Sony with the PC.

bassquake · « **Reply #37 on:** January 17, 2009, 07:25:00 AM »

QUOTE

I believe it's made by Micro Innovations or some crap like that. Have you tried simply using a different USB port? Sometimes xDSL acts weird for me and I have to switch ports, even if was already working during the current session.

Yeah, tried that.

Mouse and keyboard also works on the ps3 fine too, so really have no idea why its not working. When I plug it into an xp pc, it'll load as hids. And its not using usb2 so it should be fine with the xbox usb1.

There must be someway of getting x-dsl to use it as it detects it on boot.

Brandogg, could u post me a copy of your xorg.conf file please?

jp1324 · « **Reply #38 on:** January 21, 2009, 09:21:00 PM »

I'm running xdsl0.7 beta on a loopback install and when I go to start it up, linux starts up fine, but the xserver can't start (I get a "Fatal IO error 104") and it puts me at the text cmd prompt.

This is my third install in a row, and I think this problem is only occurring once I've selected setup>xvesa while running the GUI.

Anyone know what this is about?

thanks

stevewal · « **Reply #39 on:** January 22, 2009, 05:51:00 AM »

Xvesa setup gui is not really set up to use with the xbox. Maybe I should take it off the menu. if you want to change xvesa resolutions then it is best done via cheatcodes which you can find information about in the xdsl wiki

stevewal · « **Reply #40 on:** January 23, 2009, 09:53:00 AM »

Hi donofrio everything you require is under help in the xdsl menu.
Look under installing xdsl extensions for installing open office or cups. Cups is a little bit tricky to configure, but I can confirm it does work.

I've been doing a bit of work on usb compatibility. My aim was to get as many different usb devices as possible to work. Unfortunately I've not been able to improve on the usb keyboard/mouse compatibility. Usb devices I'm using:- usb hub; usb keyboard/mouse adapter; usb printer (with cups); usb scanner (with sane); usb flash drive; usb sd card reader; usb webcam; usb mic (integrated in webcam).

New kernel modules added:
qcmessenger for quick cams.
spca5xx for many different cams (not tested, so please test).
alsa usb sound modules, for usb mic's etc.

My qickcam messenger cam now works out of the box for video capture and sound, but it's the only cam i've got to test.

Also another request was to make the old icons available. Fluxbox is also improved as it has some advantages over jwm when using the xpad and firefox shutting down cleanly. The newer dsl versions use cheatcodes to switch from different icon managers, but I've decided to go a different way, and extend the desktop switcher.

-So you can now have jmw with dfm icons:-

IPB Image

fluxbox with xtdesk icons

IPB Image

Or any combination. Just use the gui:

IPB Image

I've been also trying to sort out the stability issues with firefox etc, but have not got too far. The same bugs seem to be present when using dsl 4 series. But I think all round it's still an improvement on Xdsl 0.6.

stevewal · « **Reply #41 on:** January 23, 2009, 02:31:00 PM »

Ok donofrio,
I've got you now.
I'm assuming your using a frugal installation. So I'll try to replicate the bug.

stevewal · « **Reply #42 on:** January 23, 2009, 04:03:00 PM »

Ok,
I've got no Idea why you can't make a loopback install. I've just tried to find the bug, but i can't reproduce it. I really need more info. I basically made a frugal install, then used the xbox loopback install option from the tools menu.
Can you be more specific about the steps you took to get the error.

stevewal · « **Reply #43 on:** January 25, 2009, 09:04:00 AM »

QUOTE

FTP Install

If you don't wish burn XDSL onto a cd and have the ability to ftp to you Xbox, it is possible to simply copy across the required files. Create a directory E:\KNOPPIX on your Xbox. Extract linux24, minirt24.gz and the KNOPPIX file (found in the KNOPPIX subdirectory) from the iso and copy them into this directory. You should be left with the following files:

E:\KNOPPIX\KNOPPIX
E:\KNOPPIX\linux24
E:\KNOPPIX\minirt24.gz

There should be no subdirectories in E:\KNOPPIX. The filenames are case sensitive.

Now create a file E:\linuxboot.cfg with the following content:

title XDSL
kernel KNOPPIX/linux24
initrd KNOPPIX/minirt24.gz
append root=/dev/ram0 init=/etc/init rw video=xbox:640x480 frugal quiet kbd-reset

Thanks for posting the pics. it's clarified the situation. Just follow the instrucions above. Put your files in the correct places and it should work fine.

Vejita · « **Reply #44 on:** January 25, 2009, 12:53:00 PM »

Is support for the Xbox remote used as a mouse added in XDSL 0.7?

Author Topic: Xdsl 0.7 Beta Released! (Read 458 times)