Hi Jaromil

I'm running Dyne2-rc on an AMD 64 3500+ nforce5 Gigabyte motherboard
with PCI Express video. I haven't found a Linux system yet that can
handle this config using either the nv or the nvidia driver or even
an ATI one, so I set the driver to vesa and it works OK, otherwise
it randomly freezes. Windows (yuk) works OK. I've tried installing
the nforce Linux motherboard drivers, but that's NBG as well.
Otherwise its great especially with 1.5GB of RAM. It does about 4700
bogomips. It will do until the PS3 comes out in November. If I can
get Linux going on that, I'll send you the board for the cost of the
postage if you want it for testing or whatever.

Have been having fun putting Dyne2 through the wringer. I'll let you
know all my findings, but just to keep you busy, killing the window
manager from the menu puts one in a console state where the root
password doesn't work, but you can log in as luther with no
password. Ho Hum.
Had some early fun with a new nest (the old beta5 one didna work at
all as its got the wrong etc files) as it got the default menu from
/usr/share/Windowmaker which has no system exit feature. Soon as I
used the config script to modify the menu and rebooted, it went back
to your great scripted one.
Oh one last minor thing the xsetkbmap thingy at the end of wmaker.sh
complains about too many args.
I know this is the wrong place for these issues but I was writing so
I went with the brain flow ....

Otherwise its really awesome.

Stomfi

jaromil wrote:
>
> hi Robbt,
>
> On Wed, May 03, 2006 at 12:32:15PM +0000, robbt wrote:
>>> Hey Dyne:2 is pretty rad so far. I'm running it on the office windows
>>> machine and it's running a lot faster than XP.
>>>
>>> I was running it on a AMD 64bit Compaq Presario and it hard crashed both
>>> times. Has it been tested on the 64 bit platform, how would I bug test
>>> it, especially since it is hard-crashing.
>
> at which point it crashes?
>
> it might be a kernel problem, anyone with experience with that please
> help, since it should'nt be a problem to run on 64bit (with emulation?)
>
> i do not possses nor have access to any 64bit machine.
>
>>> Also there is no sound on either of these computers and they are both
>>> Compaq's with built in sound, pretty standard. Should I look up the
>>> chipset and file a bug report ? I'll try and do that.
>
> sound should be autodetected, but when is not you can use the 'alsaconf'
> utility, just open a XTerm and write alsaconf[enter] then follow the
> instructions.
>
>>> Also for some reason it didn't auto-detect the NTFS filesystem on that
>>> computer but it did on here, which leads me to think it may be an
>>> architecture problem.
>
> i'd be courious to read the contents of /boot/volumes and
> /var/log/messages on the machine where it wasn't recognized
> (better send them off-list in private to me if you do)
>
>>> Have you thought about incorporating the Captive NTFS project which uses
>>> Wine to grab the NTFS file system from windows so that people could
>>> read/write their NTFS partitions, cuz otherwise I'm not sure how I could
>>> dock it
>
> it is a good idea but quite delicate and not high on my priority: in the
> meanwhile there is a very simple solution, that of docking (copying the
> dyne/ directory on harddisk) from WIN, where you can write on your NTFS.
>
> When dyne:II can still mount read-only NTFS and that will be good enough
> to use the docking (which is not writing anything, that is nesting).
>
>>> , except on a flash card. And the problem I ran into with dyne
>>> 1.4.1 was that all of the tmp files when it was docked where written
>>> onto flash card which soon ran out of space when I was using audacity.
>
> yes, this was a problem with nesting in 1.x versions, which is solved
> now. more in general nesting has been reengineered in the 2.0 version
> for much more flexibility, future compatibility and stability.
>
> thanks for your report,
> ciao
>
_______________________________________________
dynebolic mailing list
dynebolic@???
http://mailinglists.dyne.org/mailman/listinfo/dynebolic