On Wed, 2005-03-30 at 17:51 +0200, dr.bob wrote:
Using the current netinstall image for debian-amd64..
The system is a dual xeon server by Fujitsu-SIemens, the installer
selected kernel 2.6.8-10-em64t-p4.
Installed the base system successfully, cannot get the network to operate :(
The
On Wed, 2005-03-30 at 18:41 +0200, dr.bob wrote:
Oh, did I forget to mention that I grabbed a copy of the firmware files
(http://home.twcny.rr.com/nerode/neroden/debian/)
and after putting them on the system, warnings from the driver about
firmware went away. But the NICs still don't work,
On Fri, 2005-03-18 at 21:07 +0100, Hannes Mayer wrote:
First I tried to use pptp from alioth, but that did not work, so as a
last resort I tried to run the 32bit versions and voila! They worked!
Definitely check your PPTP settings. If you want the best encryption and
compression, you'll have to
On Fri, 2005-03-04 at 00:16 +0100, Carsten Prie wrote:
On Thu, 03 Mar 2005 17:47:47 -0500 Tong [EMAIL PROTECTED] wrote:
This is not clear. Should I do it in the chroot environment, or out
side it? If I should do it in the chroot environment, isn't that
Not in chroot. Do it in basesystem.
On Fri, 2005-03-04 at 01:54 +0100, Carsten Prie wrote:
On Thu, 03 Mar 2005 16:32:28 -0800
Alex Perry [EMAIL PROTECTED] wrote:
Once you know what the drift value is, you can tell the kernel (using
the adjtime related commands) and it will apply the correction for
you.
I had the problem
On Fri, 2005-03-04 at 01:43 +0100, Alexandru Cabuz wrote:
My AMD64 sid box was running along nicely until yesterday, when after
a reboot it didn't want to connect to the internet anymore. I am using
dhcp, and when I start the client here is what I get:
I've had this happen. Usually it's
On Thu, 2004-12-02 at 10:10 +0100, Alexandru Cabuz wrote:
Make sure you have /dev, /proc and /sys mounted in the chroot
directory. According to the howto add /home and /tmp also.
The howto does not say anything about /dev. So it should also be
mounted in the chroot, huh? Cos the chroot has
On Fri, 2004-11-19 at 17:59 +0100, Alexandru Cabuz wrote:
I just got done installing pure64 on my new box, kde3.3, mozilla,
everything works smooth, except that I can't get on the internet,
Check your /etc/resolv.conf for PPP's DNS servers. If it is empty or has
the wrong DNS IPs, then your PPP
On Sun, 2004-11-14 at 12:05 -0700, Bob Proulx wrote:
Alex Perry wrote:
hardware clock). Once the clock is close, by using this method, the ntp
will always be able to keep it on time from then onwards.
Agreed.
To check if ntp is in a happy state, use the 'ntpq -p' command.
ntpq -p
OK, so if your system clock is way off and NTP doesn't work, try this
before blaming hardware:
1) delete /etc/adjtime
2) run /etc/init.d/hwclock.sh
3) run adjtimexconfig
4) run ntpdate server
5) run /etc/init.d/ntp-server start
Turns out my adjtime was way off due to a bad clock on the previous
ALSA works pretty well with 32-bit user space and 64-bit kernel (so long
as you have snd-ioctl32 loaded). However, the dmix plugin appears to
be broken. Have any of you been able to get ALSA's dmix to work?
Thanks,
-s
signature.asc
Description: This is a digitally signed message part
On Wed, 2004-10-13 at 08:04, Ron Johnson wrote:
On Wed, 2004-10-13 at 00:37 -0500, Stephen Waters wrote:
On Tue, 2004-10-12 at 21:13, Ron Johnson wrote:
Now, if the OP's question really was can a 32-bit X server run
inside a chroot jail on an otherwise pure-64 system, then that
would
I want to run 64-bit kernel, 32-bit user space. I was wondering if
anyone has a statically linked amd64 iptables binary hanging around.
That seems to be the only issue.
Thanks,
-s
signature.asc
Description: This is a digitally signed message part
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,
14 matches
Mail list logo
