Print

[stevewal]

thanks for the link. Maybe I'll have another go at implimenting softvol.

I'm using a stripped down version of alsa without alsa oss to reduce memory usage. It's possibe to do this, but I might have to create another alsa dsl app for download as it will be too large to put in the base system. Like I said I tryed alsa player which implements softvol and ended up with no sound on flash player. The problem with dsl is that it doesn't support flashplayer 9 and only certain archetectures can use it without perpetual crash. Luckily the xbox is one of these but it's not perfect, and alsa still crashes flash sometimes on certain sites. That's why I've made a program to switch between sound  drivers for difficult sites. Unfortunately adding an extra software layer, seems to make the problem worse. But saying that I'll keep trying.

Have you been able to use this in xebian? That would certainly be a start especially if it could be used in conjunction with umix and/or dmix .

[stevewal]

Thanks for checking that out for me.
I'm guessing your using a 1.6b.
I've never seen that problem before, but obviously there is a fault in the linux 24 file. I'll have a look at it when I get the chance.

[willows02]

PS: I just played in Xebian with sound apps, like Audacity, Mplayer, xine.
Results using alsamixer to control volume:

Audacity = Dont have a option to choose ALSA driver then alsamixer cant control volume

Mplayer = Selected ALSA driver as output, but again alsamixer cant control volume

Xine = Selected ALSA driver as output and alsamixer can control volume

xmms =   Selected ALSA driver as output and alsamixer can control volume

So alsamixer can control volume but depending on each app, well at least some  
 apps could take sound control in xdsl, but the problem I found was compiling ALSA with patched xbox sound drivers in xdsl, I want to use the ALSA upgrade from repository but  I erased some files and I cant upgrade to ALSA, Stevewal: can you try your ALSA upgrade and check if alsamixer can control volume of multimedia apps?, thanks.

[stevewal]

hi willows02
Thanks for all your work.
I'm using the alsa upgrade from the repository to get working the modules that I've already compiled. You can find them in lib/module/--/--/sound (sorry I'm using xebian right now).  But there is no softvol in the alsa apps I'm using so I would have to compile a new set to see if it works.

But I can say that xmms won't work like you said

Xine should work with softvol but not tested yet.

The commandline version of mplayer packaged with the new version of xdsl works fine, cus it has its own software volume control. So does mplyaer plugin (not the gtk2 version)

Vlc player also works fine having it's own software volume control.

Th compile error you had b4 for alsa, was looking for a header file. If this is still the problem compile from the kernel headers and not the kernel sources

Cheers.

[8BitBrad]

I have a question.

First of I have a 1.6 Xbox. I did a FTP install dir setup as such.

E:/apps/xdsl/default.xbe
E:/KNOPPIX
E:/KNOPPIX/KNOPPIX
E:/KNOPPIX/linux24
E:/KNOPPIX/minirt24.gz
E:/linuxboot.cfg

I have the 1.6 over scan issue. I run the fix and it tells me that it is going to adjust the screen size. I choose yes to fix. It flashes some commands really quick goes to Grey screen with Black border. It then gives a can't find display error and shutsdown. My guess is that I can't change this due to a FTP install. Would I be able to do this with a loopback install?

[8BitBrad]

Ok,

I made loopback install. Booted into that, applied the 1.6fix does the same as above. Gives me a kill signal.

Edit.
I did a quick google and found that I should wait 10 mins and reboot. This worked like a charm.

[willows02]

Just to be more specific with FATX error above mentioned.

dsl@box:~$ dmesg
.
.
.
FATX: fatx_raw_scan_nonroot: start sector 0 not in use
Filesystem panic (dev 03:01).
  FATX error
  File system has been set read-only

[ldotsfan]

QUOTE(willows02 @ May 20 2008, 11:36 PM)

FATX: fatx_raw_scan_nonroot: start sector 0 not in use
Filesystem panic (dev 03:01).
  FATX error
  File system has been set read-only

I'm not sure if this is related to http://forums.xbox-s...&...t&p=4107671

[stevewal]

QUOTE

But I can say that xmms won't work like you said

Yea you are right it does work. I had so many bit's of different sound programs installed that it was confusing xmms and the alsa option wasn't appearing. I've made a new install on xdsl beta 0.6 and it works like you said, with the volume not saving. I guess I've got to get around to making a new alsa install to see what can be done.

About the fatx error. Idiotsfan could be right about the cause. I had the same problem before with an xdsl0.5 install and ended up reformatting the hard drive. But saying that, I've ony experienced the problem once in using xdsl daily for 4 years.

[stevewal]

willows02
Hi I was thinking about the problem you had with loop and fatx. I think it could be attributed at least partially to some mounting and unmounting errors with cloop/loop. Theres a bug which sets /home/dsl and (maybe) /dev/loop to read only, when the file system is full and a uci app or other disk image is mounted. I've noticed that /home/dsl resets to user root - root and should be dsl - staff. The fatx error may be unrelated, but I have a feeling there may be some connection.

I'm working on xdsl 0.6 at preasent , to try to get that as stable as I can. Xdsl 0.7 is only in alpha and problems should be expected for now. I'll try to work out some of the bugs in 0.7 after I finnish with 0.6. If you find any solutions please post them and I will try to integrate them for the next release.

Cheers,
Steve.

[stevewal]

hi sickdelan
for some reason xnest has'nt copied over when you installed. Best thing to do is make a new loopback install without the screen fix on. Then after you've got your loopback install working, implement the screen fix.

[stevewal]

Hi,
After a very large amount of time racking my brains for a solution, I think I've just about got the sound problem under control. There's still no volume control in xmms for oss as expected, but it's just about running perfectly for alsa. I've even got a master volume controll and a sftware slave. So it's prety much the same as xebian now. Xine from the dsl repository also works (for the volume control), though it works directly through alsa and not softvol. Some of the dsl repository apps hav'nt been compiled with alsa support, so it's pot luck.

I've put alsa mixer on the dock (for xdsl 0.6) and the mute button also works. So far I hav'nt got the dock slider working. I've stuck to using only volume slider in alsamixer because the treble/base etc kept crashing (I don't think the xbox chip is compatible enough).  Mplayer uses it's own mixer so it can't be controlled through alsa mixer, but it can be controlled using the keyboard (up and down arrows) and the xpad right stick.

So far I've implemented this on xdsl 0.6 I'll transfer the files over to xdsl 0.7 when I get the chance

Cheers
Steve.

[ldotsfan]

QUOTE(stevewal @ Jun 1 2008, 09:04 AM)

Hi,
After a very large amount of time racking my brains for a solution, I think I've just about got the sound problem under control. There's still no volume control in xmms for oss as expected, but it's just about running perfectly for alsa. I've even got a master volume controll and a sftware slave. So it's prety much the same as xebian now. Xine from the dsl repository also works (for the volume control), though it works directly through alsa and not softvol. Some of the dsl repository apps hav'nt been compiled with alsa support, so it's pot luck.

I've put alsa mixer on the dock (for xdsl 0.6) and the mute button also works. So far I hav'nt got the dock slider working. I've stuck to using only volume slider in alsamixer because the treble/base etc kept crashing (I don't think the xbox chip is compatible enough).  Mplayer uses it's own mixer so it can't be controlled through alsa mixer, but it can be controlled using the keyboard (up and down arrows) and the xpad right stick.

So far I've implemented this on xdsl 0.6 I'll transfer the files over to xdsl 0.7 when I get the chance

Cheers
Steve.

Great work and all xdsl users including myself are grateful for your effort and time you have devoted to this project. I patiently await the next release

[willows02]

QUOTE(stevewal @ May 22 2008, 02:02 PM)

willows02
Hi I was thinking about the problem you had with loop and fatx. I think it could be attributed at least partially to some mounting and unmounting errors with cloop/loop. Theres a bug which sets /home/dsl and (maybe) /dev/loop to read only, when the file system is full and a uci app or other disk image is mounted. I've noticed that /home/dsl resets to user root - root and should be dsl - staff. The fatx error may be unrelated, but I have a feeling there may be some connection.
Cheers,
Steve.

Hi stevewal.
I clearly remember that I had available 608Mb in Filesystem, but not a problem now, because It is my 10th Loopback Install with xdsl 0.7 and the error appeared just once. The number of Loopback Installs are because I made a lot of mistakes deleting files by accident.

I use xdsl 0.7 everyday and I know that problems should be expected in the Alpha release but 0.7 seems perfect to me. Thanks.

[willows02]

1) Recently, another time I had the error regarding to "file system with errors" twice.
First time: fsck corrected file system
Second time: fsck couldnt correct the error then:

2) Complete log by hand

Accesing loopback file on /dev/hda50...
INIT: version 2.78-knoopix booting
Running Linux Kernel 2.4.31-xbox

Running from HD, checking filesystems...
Activating swap...
Checking root file system
fsck 1.34-WIP (21-May-2003)
/dev/loop0 contains a file system with errors check forced

Inode 203447 has illegal block(s)

/dev/loop0: UNEXPECTED INCONSISTENCY ; RUN fsck MANUALLY

             (i.e, without -a or -p options)

fsck failed. Please repair manually and reboot. Please note that the root file system is currently mounted as read-only. To remount it read-write:

             #mount -n -o remount,rw /

CONTROL-D will exit from this shell and REBOOT the sytem.

su (pam-unix)[72]: session opened for user dsl by (UID=O)

Starting X...

      xauth: error in locking authority file /home/dsl/.Xauthority
      xauth: error in locking authority file /home/dsl/.Xauthority
      xauth: error in locking authority file /home/dsl/.Xauthority
      xauth: error in locking authority file /home/dsl/.Xauthority

Fatal server error
Could not create lock file /tmp/.tX0-lock

When reporting a problem related to a server crash, please send the full server output, not just the last messages.
Please report problems to [email protected]

giving up

xinit: Connection refused (errno 111): unable to connect to X server
xinit: No such process (errno 3): Server error
xauth: error in locking authority file /home/dsl/.Xauthority

dsl@console[dsl]$

3) Then I booted XEBIAN. The commands executed as root:

mkdir /mnt/E
mount /dev/hda50 /mnt/E
fsck /mnt/E/xdslfs

4) And fsck corrected the file system, it ask me a lot of questions, as I don't have the knowledge, answered Y to all questions.
5) Finally run xdsl 0.7, and all seems OK   .

*** I will post the fsck output tomorrow, maybe it would help to correct this continuous file system error in xdsl 0.7 Alpha.
*** Also I will format my HD to avoid hardware related problems, and try a new Loopback Install to see if problem persists.
*** I assume that this procedure could be similar by booting xdsl from live CD to execute fsck and correct the file system.