On Tue, Jan 6, 2009 at 10:44 PM, Gustin Johnson <[email protected]> wrote:
> > Peter Geirnaert wrote: > > Hi Gustin, > > > > > ls /dev | grep sd gives me only > > > sda > > > sdb > > > sdc > > > These are the flash card usb type of drives I have, so there's no > hard > > > disk available. > > > > > Are we talking about SSDs, USB flash devices, or compact flash cards > in > > PATA adaptors? > > > > > > I think it's compact flash cards in PATA adaptors we're talking about. > > lsusb in the working Ubuntu shows me a "Standard Microsystems Corp. > > 9-in-2 Card Reader" > > and there are ports on the desktop computer's front panel to insert CF, > > MS/SD/MMC and SM/XD cards. > > > 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. (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 computers.) 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 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. > > 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 : pe...@ubustu:~$ sudo dmidecode -s bios-release-date 06/12/2008 > > > 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 ? (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 > reasons. > > 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. > > > 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: 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. > hth, > Kind regards, Peter
_______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
