-----BEGIN PGP SIGNED MESSAGE-----
Peter Geirnaert wrote:
> This should not appear any differently than a PATA hard drive. This
> does not make a lot of sense given that you are using a laptop with a
> SATA hard drive interface. I also get the sense that you have a working
> install of Ubuntu?
> No, I'm not using a laptop, Dave Philips is using a laptop, I'm using a
> desktop computer,
> but also with RS780 and SB700/SB800 controllers, a SATA hard drive and
> an AMD multi-core CPU.
OK, so you are not using a flash drive. I think I am starting to get a
feel for what is going on. I am certainly not the sharpest knife in the
> (Maybe this is all irrelevant, I only just found out RS780 and
> SB700/SB800 are components that can be found in a lot of different
> And I also get busybox after the boot, just like Dave Philips.
> That's why I write all this here, to share my experiences, I have Ubuntu
> 8.10 running here fine, on the same desktop computer
> and disk that I'm trying to get the alpha release installed on. I just
> didn't test the HDA intel onboard sound.
The different between the two that I see as important is the kernel.
The latest Ubuntu ships with 2.7.27.xx which supports newer chipsets and
> The card reader will present each slot as a device, but with no
> partitions until
> a media card with a partition is inserted.
> Yes, if I didn't have the card reader I would get 'no disk found', at
> least that's what I think because I didn't disconnect the card reader
> and see what it does.
I would expect a no disk found error.
> > PCI: BIOS Bug : MCFG area at e0000000 is not E820-reserved
> > PCI: Not using MMCONFIG
> Update your BIOS.
> I'm planning to sell this computer again, and Ubuntu runs fine on it,
> not giving this error, sorry I think I'll skip this as I'm not
> experienced with updating a BIOS.
> Or do you think this is really serious ? Btw :
> peter@ubustu:~$ sudo dmidecode -s bios-release-date
My experiences with my last laptop and an AM2 board would lead me to
respond with a yes. These machines were pretty much unusable on Linux
without BIOS updates. I have been more than disappointed with the AM2
platform. I have been using computers for a very long time, so to say
that my Turion and this AM2 board are the worst hardware choices I have
ever made says something.
In contrast I have been very happy with the Core2 laptop and the older
939 X2 systems that I have. The 939 4400+ X2 is probably the best
machine I have ever owned. 3 years on and it is still inside my DAW and
it is still a joy to use.
> > 64Studio 3
> > alpha uses 2.6.21 and the latest Ubuntu kernel is 2.6.27-9.19
> I suspect
> > that the newer udev/hotplug userspace apps that ship with
> Ubuntu may be
> > acting weirdly with such an old kernel.
> > So if I understand this correctly, to get it working,
> > these userspace apps should be modified/rewritten to work also
> with the
> > older kernel,
> No, these apps work hand in hand with the more recent kernels. The
> solution is one of two things;
> First option is to build a more recent kernel (I have had a reasonably
> good experience with the 2.6.24 and rt25 patch.
> The second is to wait for an RT patch to 2.6.28.
> Your hardware is not well supported by the 2.6.21 kernel anyway.
> I would not expect from anyone to rewrite any app just to get MY
> computer running 64studio Alpha NOW :-)
> So for testing purposes, we will need another AMD64 computer than Dave's
> laptop or my desktop computer, right ?
I will be putting the 64bit version through its paces on my laptop. I
will also be testing it on one of my machines at home. AMD FX60
(another 939 based system). I do not really expect driver problems with
either of these.
A more apples to apples comparison would be to test on other AM2 or AM2+
systems. I no longer have access to such a system.
Out of curiosity are you using the 32 or 64 bit version? I could
probably build a kernel for you to try.
> (At this time I'm trying to write a sysex driver so I'm not really in a
> need for a realtime kernel, just interested in testing it.)
> > for 64studio and other distro's who still depend on the 2.6.21 kernel.
> > Or use some sort of adaptor or "protocol" convertor ?
> 64Studio 3.0 is an *Alpha* release after all. I do not expect it to be
> released with a 2.6.21, it is simply what it is using at this stage of
> development. Also, depending on an old kernel is a bad idea for many
> It is unfortunate for us multimedia types that there are currently RT
> problems with the last few kernels, but the changes being made are
> important within the big picture.
> So at this time, the best multimedia production computer is not the
> newest but the tested one I guess.
> Maybe this already is a rule in Linux-life, I'm too new here to know
> about that.
That is an excellent general rule to follow. If you are buying new, I
would choose Intel since they have been very good at getting their
drivers integrated upstream (ie. into the vanilla kernel at kernel.org).
In other words their stuff tends to work out of the box sooner than
The latest ATI driver is open source so the future looks promising over
at AMD/ATI, they are just not there yet. The other problem with AMD is
that their chips often get paired with crappy wireless chips like broadcomm.
Of course as usual, YMMV.
> > Anyway, I'll try the for each in 'ls /dev ... thing now ..
> Look in /var/log/dmesg for each of those /dev/sd devices. It may give
> you more information. At this point my best guess is that the 2.6.21
> kernel does not have complete or bugfree drivers for your chipset.
> I'm not sure I understand this right. Running Ubuntu, i read
> /media/disk/var/log/dmesg (disk is the mounted 64studio partition)
> and there's only the line:
I actually want the /var/log/dmesg from Ubuntu, since it does boot it
should detect your hardware. This file is written at boot, since
64studio is not booting, it should be empty
> 1. (Nothing has been logged yet.)
> Maybe I'll have to do something to make the boot process write to the
> log file, but it's too late now so I'll do that tomorrow.
> What I already found out is syslog writes the dmesg log, does it do this
> automatically when there's an error? If so, there was no error.
You have to boot first. Since the hard drive is not being detected, it
is not booting, so the file is not being written. /var/log/dmesg is
boot info, after boot, all subsequent stuff gets logged to
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
64studio-users mailing list