On Mon, 20 Sep 2004, amd64 wrote:
Does anyone know the relationship between the AMD64
port of ubuntu linux and the amd64 port of debian?
Is it a pure64 port? Is it based of the current
debian AMD64 port?
They are both based on packages patched and built from the debian source
packages and should
Has anyone gotten gstreamer alsasink to work? I can play a file with
alsaplayer just fine, so I know alsa and the kernel and everything is
working, but when I run for example
gst-launch-0.8 --gst-debug-level=2 sinesrc ! alsasink
RUNNING pipeline ...
WARN (0x50ac20 - 304367:44:35.501704000)
Does anyone know the relationship between the AMD64
port of ubuntu linux and the amd64 port of debian?
Is it a pure64 port? Is it based of the current
debian AMD64 port?
Found it...
/etc/mkinitrd needed:
libata
sata_via
sd_mod
ext3
In my case anyway
In The Night ([EMAIL PROTECTED]) wrote:
> And here is some info from syslog booting 2.6.7:
>
> Sep 20 23:43:02 localhost kernel: VIA8237SATA: IDE controller at PCI slot
> :00:0f.0
> Sep 20 23:43:02 localho
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 20 September 2004 3:43 am, Nicholas Hemsley wrote:
> Philipp Frauenfelder wrote:
> >This sounds very much like a networking problem to me. Something
> >like timeouts the systems waits for before it proceeds...
> >
> >Regards
>
> on that note
1) Is pivot_root the ext3-not-compiled-in problem?
2) Can you boot manually from Grub, changing the root= commandline
option?
(I have a meeting and have to go home, so I won't be responding till
tomorrow if you write back... just trynig to give you some ideas)
-s
On Mon, 2004-09-20 at 17:37, In
And here is some info from syslog booting 2.6.7:
Sep 20 23:43:02 localhost kernel: VIA8237SATA: IDE controller at PCI slot
:00:0f.0
Sep 20 23:43:02 localhost kernel: VIA8237SATA: chipset revision 128
Sep 20 23:43:02 localhost kernel: VIA8237SATA: 100%% native mode on irq 20
Sep 20 23:43:02 lo
Now I've got the SCSI subsystem up and running...
But still pivot_root error and panic.
Disklayout as of today:
hda = PATA HDD
hdb = PATA HDD
hdc = PATA HDD
hdd = PATA DVD
hde = SATA HDD
hdg = SATA HDD
Important /etc/fstab-entries:
proc/proc procdefaults0 0
Am Montag, 20. September 2004 09:43 schrieb Nicholas Hemsley:
> Philipp Frauenfelder wrote:
> >This sounds very much like a networking problem to me. Something
> >like timeouts the systems waits for before it proceeds...
> >
> >Regards
>
> on that note, is your hosts file setup properly? i.e. wi
I installed on nearly the same hardware - but I installed it on a WD
raptor on the onboard SATA (SI8114?) first, then I copied over the install
to the 3ware array once I compiled a kernel with support.
I would say all you need is an installer that's based off 2.6.8 or newer;
a custom install di
On Tue, Sep 14, 2004 at 09:08:04PM +0200, Harald Dunkel wrote:
> In The Night wrote:
> >Hmmm
> >I've tried that.
> >I've tried mkinitrd -r /dev/sdb1 too...
> >
> >The problem seems to be me having root on a SATA-drive
> >
>
> mkinitrd fails to find the sata driver necessary to mount
> your
A Diumenge 19 Setembre 2004 06:42, Bob Proulx va escriure:
Thank's a lot for the answer. I thought that nobody would answer me.
Maybe it would be a good idea to put your answer in the AMD64-howto, because I
think that I'm not the only that have this situation.
Another option that maybe its posib
Philipp Frauenfelder wrote:
Dear John
On Sun, Sep 19, 2004 at 11:25:17PM -0400, John C. Martin wrote:
a user logs in kde takes forever (well a long time at least) to start. It
sits on initializing system services for several minutes, then the startup
box dissapears and we have just the backgr
Dear John
On Sun, Sep 19, 2004 at 11:25:17PM -0400, John C. Martin wrote:
> a user logs in kde takes forever (well a long time at least) to start. It
> sits on initializing system services for several minutes, then the startup
> box dissapears and we have just the background for another few min
14 matches
Mail list logo
