Installation was on second drive, and grub was installed to the MBR
of that drive. Restart dropped me into grub rescue mode with the
message about normal.mod not being found. After mounting the drive
in Wheezy, I find that the directory that normal.mod is supposed to
be in, is not there. There are
Installation was on second drive, and grub was installed to the MBR of
that drive. Restart dropped me into grub rescue mode with the message
about normal.mod not being found. After mounting the drive in Wheezy, I
find that the directory that normal.mod is supposed to be in, is not
there. There
I'm a long-time Debian user and this system (Wheezy) is result of at
least 3 dist-upgrades (as well as motherboard upgrades). Last
dist-upgrade was not completely successful, so I thought to do a new
install of Jessie, onto a second hard drive. Since the current
motherboard is AMD FX 64bit capa
On Mon, Feb 27, 2006 at 10:09:19PM -0500, [EMAIL PROTECTED] wrote:
> During the installation, after the reboot into the new system, it goes
> into package-selection mode. It is during this time that it gave me the
> choice of choosing categories of packages or individual package
> selection. W
On Sun, Feb 26, 2006 at 10:38:43PM -0500, Kevin Mark wrote:
> On Mon, Feb 27, 2006 at 03:49:10PM +1300, Chris Bannister wrote:
> > On Sun, Feb 26, 2006 at 03:29:23PM -0500, [EMAIL PROTECTED] wrote:
> > > On Sun, Feb 26, 2006 at 03:59:23PM +1300, Chris Bannister wrote:
> > > > On Sun, Feb 19, 2006 a
On Mon, Feb 27, 2006 at 03:49:10PM +1300, Chris Bannister wrote:
> On Sun, Feb 26, 2006 at 03:29:23PM -0500, [EMAIL PROTECTED] wrote:
> > On Sun, Feb 26, 2006 at 03:59:23PM +1300, Chris Bannister wrote:
> > > On Sun, Feb 19, 2006 at 05:25:30PM -0500, [EMAIL PROTECTED] wrote:
> [..]
> > > > package
On Mon, Feb 27, 2006 at 03:49:10PM +1300, Chris Bannister wrote:
> On Sun, Feb 26, 2006 at 03:29:23PM -0500, [EMAIL PROTECTED] wrote:
> > On Sun, Feb 26, 2006 at 03:59:23PM +1300, Chris Bannister wrote:
> > > On Sun, Feb 19, 2006 at 05:25:30PM -0500, [EMAIL PROTECTED] wrote:
> [..]
> > > > package
On Sun, Feb 26, 2006 at 03:29:23PM -0500, [EMAIL PROTECTED] wrote:
> On Sun, Feb 26, 2006 at 03:59:23PM +1300, Chris Bannister wrote:
> > On Sun, Feb 19, 2006 at 05:25:30PM -0500, [EMAIL PROTECTED] wrote:
[..]
> > > package
> > > * report-bug: Depends: pythin 2.3 which is a cirtual package
> >
On Sun, Feb 26, 2006 at 03:59:23PM +1300, Chris Bannister wrote:
> On Sun, Feb 19, 2006 at 05:25:30PM -0500, [EMAIL PROTECTED] wrote:
> > * E: Unable to correct problems, you have held back broken packages.
> > * E: Unable to correct dependencies, some packages cannot be installed
> > * E: Unable t
On Sun, Feb 19, 2006 at 05:25:30PM -0500, [EMAIL PROTECTED] wrote:
> * E: Unable to correct problems, you have held back broken packages.
> * E: Unable to correct dependencies, some packages cannot be installed
> * E: Unable to resolve some dependencies
> *
> * Some packages had unmet dependencies.
On Mon, Feb 13, 2006 at 11:15:25PM -0500, [EMAIL PROTECTED] wrote:
> On Tue, Feb 14, 2006 at 01:13:01AM +, Peter Colton wrote:
> > On Monday 13 February 2006 20:29, [EMAIL PROTECTED] wrote:
> > > On Sun, Feb 12, 2006 at 04:24:44AM +, Peter Colton wrote:
> > > > On Saturday 11 February 2006
On 8/29/05, Turloch O'Tierney <[EMAIL PROTECTED]> wrote:
> Grant,
>
> Thanks for the pointer, I have not got it right though.
> If I get the tg3 network card working I will write a detailed
> description to the mailing list.
>
> Thank you for your time,
> Turloch
>
> Slightly confused messages f
> Dell Gx280 installation
>
> Tigon3 ethernet card is not supported on the debian testing network
> install download(kernel 2.6.8).
> (http://cdimage.debian.org/pub/cdimage-testing/daily/)
>
> Error:
> [tg3:eth%d:Firmware "tg3/tso-1.4.0" not loaded; continuing without TS0]
>
> The sarge network
On (26/08/05 15:46), Turloch O'Tierney wrote:
> Dell Gx280 installation
>
> Tigon3 ethernet card is not supported on the debian testing network
> install download(kernel 2.6.8).
> (http://cdimage.debian.org/pub/cdimage-testing/daily/)
>
> Error:
> [tg3:eth%d:Firmware "tg3/tso-1.4.0" not loaded; c
Dell Gx280 installation
Tigon3 ethernet card is not supported on the debian testing network
install download(kernel 2.6.8).
(http://cdimage.debian.org/pub/cdimage-testing/daily/)
Error:
[tg3:eth%d:Firmware "tg3/tso-1.4.0" not loaded; continuing without TS0]
The sarge network install failed due t
In message <[EMAIL PROTECTED]>, Adam Funk <[EMAIL PROTECTED]>
writes
On Thursday 06 January 2005 21:20, Joe wrote:
Is it a "defect" that requires the noapic option?
I think so. I don't believe a mere absence of a feature should stop a
kernel booting, particularly a Knoppix one. I think it must be
On Thursday 06 January 2005 21:20, Joe wrote:
>>Is it a "defect" that requires the noapic option?
>>
>>
> I think so. I don't believe a mere absence of a feature should stop a
> kernel booting, particularly a Knoppix one. I think it must be a
> hardware bug.
>
> In fact a quick Google on 'k7s8x n
In message <[EMAIL PROTECTED]>, Adam Funk <[EMAIL PROTECTED]>
writes
On Tuesday 04 January 2005 20:40, Joe wrote:
The motherboard is an ASRock K7S8X. (I don't know what chips are on
it.)
I didn't see the beginning of this. I have one of these and I've yet
to see any Linux boot without noapic. In
On Tuesday 04 January 2005 20:40, Joe wrote:
>>The motherboard is an ASRock K7S8X. (I don't know what chips are on
>>it.)
> I didn't see the beginning of this. I have one of these and I've yet
> to see any Linux boot without noapic. Including Knoppix, and Woody on
> 2.4.18, and the current Sarge
In message <[EMAIL PROTECTED]>, Adam Funk <[EMAIL PROTECTED]>
writes
On Wednesday 29 December 2004 00:10, Roberto Sanchez wrote:
Thanks. I added that to the append="..." in /etc/lilo.conf and it
fixed the problem.
Just out of curiosity, why did this become necessary (for my hardware
at least) bet
On Wednesday 29 December 2004 00:10, Roberto Sanchez wrote:
>> Thanks. I added that to the append="..." in /etc/lilo.conf and it
>> fixed the problem.
>>
>> Just out of curiosity, why did this become necessary (for my hardware
>> at least) between the 2.4.23 and 2.4.26 kernels?
>>
> What motherbo
Adam Funk wrote:
Herbert Xu <[EMAIL PROTECTED]> wrote:
Adam Funk <[EMAIL PROTECTED]> wrote:
I'm running Debian testing on an Athlon 1100 and currently using the
2.4.23-1-386 kernel. I've tried to upgrade to the following packages:
kernel-image-2.4.25-1-386
kernel-image-2.4.26-1-386
kernel-image-2.
Herbert Xu <[EMAIL PROTECTED]> wrote:
> Adam Funk <[EMAIL PROTECTED]> wrote:
> > I'm running Debian testing on an Athlon 1100 and currently using the
> > 2.4.23-1-386 kernel. I've tried to upgrade to the following packages:
> >
> > kernel-image-2.4.25-1-386
> > kernel-image-2.4.26-1-386
> > kerne
Adam Funk <[EMAIL PROTECTED]> wrote:
> I'm running Debian testing on an Athlon 1100 and currently using the
> 2.4.23-1-386 kernel. I've tried to upgrade to the following packages:
>
> kernel-image-2.4.25-1-386
> kernel-image-2.4.26-1-386
> kernel-image-2.4.26-1-k7
>
> and they all get stuck on "
On Friday 14 May 2004 10:41 am, Adam Funk wrote:
> On Friday 14 May 2004 17:10, Roberto Sanchez wrote:
> > What motherboard do you have?
>
> ASRock K7S8X
>
> > Are you loading the module for your
> > IDE chipset?
>
> Here's some info about the kernel that works. AFAIK all the kernels
> I've tried
On Friday 14 May 2004 17:10, Roberto Sanchez wrote:
> What motherboard do you have?
ASRock K7S8X
> Are you loading the module for your
> IDE chipset?
Here's some info about the kernel that works. AFAIK all the kernels
I've tried would use the same modules.conf file, so I can't see why
changi
Adam Funk wrote:
I'm running Debian testing on an Athlon 1100 and currently using the
2.4.23-1-386 kernel. I've tried to upgrade to the following packages:
kernel-image-2.4.25-1-386
kernel-image-2.4.26-1-386
kernel-image-2.4.26-1-k7
and they all get stuck on "hda: lost interrupt" while trying to b
I'm running Debian testing on an Athlon 1100 and currently using the
2.4.23-1-386 kernel. I've tried to upgrade to the following packages:
kernel-image-2.4.25-1-386
kernel-image-2.4.26-1-386
kernel-image-2.4.26-1-k7
and they all get stuck on "hda: lost interrupt" while trying to boot. I
thought
Quoting Danny O'Brien <[EMAIL PROTECTED]>:
>
> OK -- many thanks, much better
...
> However, the page is still refusing logins and passwords that were
> scripted into the DB (from the "fake_data" file), including the
> postgres db main user (not postgres, in our case).
>
> So, my next stop is
Danny O'Brien wrote:
Parse error: parse error in /var/www/srp/dbconnect.php on line 5
With this error...
$link = pg_connect ("", "", "", "", "ourdb" or
die ( "Could not connect to database." );
You are missing a closing bracket for pg_connect. With the bracket:
$link =
OK -- many thanks, much better -- the parse error is gone, so it
appears that the PHP page is connecting to the database! Alll
right! (Please forgive the missing ')' in the string below, I'm not a
PHP programmer, but I'm learning in a hurry. And under the old config,
these files worked perf
Quoting Danny O'Brien <[EMAIL PROTECTED]>:
...
> This led me to examine "dbconnect.php" -- the following line is present:
>
> $link = pg_connect ("", "", "", "", "ourdb" or
> die ( "Could not connect to database." );
Danny,
First of all, that code snippet can't be rig
My recommendation (I didn't see this in your extensive littany of steps
taken) is to add the following line to /etc/postgresql/postgresql.conf
and then restart postgresql)
tcpip_sociket = 1
good luck,
~c
Danny O'Brien wrote:
Thanks to everyone for the helpful replies (my or
Thanks to everyone for the helpful replies (my original post is below,
under the line). It appears that PHP is not connecting to our
postgre database, as indicated by the following error that appears on
the main PHP web page:
Parse error: parse error in /var/www/srp/dbconnect.php on line 5
On Tuesday 24 February 2004 18:50, Danny O'Brien shoved this is my mailbox:
> ... We have a PHP4 site that worked fine
> under a previous RedHat build, but we just can't get it working on this
> Debian build.
...
> But when we go to login to our PHP site, our login is rejected and we
> get the fol
On 2004-02-24, Danny O'Brien penned:
>
>
> Warning: Supplied argument is not a valid PostgreSQL link resource in
>/auth.php on line 10
>
> Line 10 in auth.php looks like this:
>
> $result = pg_exec( $link, $sql );
>
Well, first of all, from
http://us2.php.net/manual/en/function.pg-query.php :
No
On Tue, 2004-02-24 at 17:27, Danny O'Brien wrote:
> Any postgre experts out there? We have a PHP4 site that worked
> fineunder a previous RedHat build, but we just can't get it working
> onthis Debian build.
...
> But when we go to login to our PHP site, our login is rejected and we
> get the foll
Any postgre experts out there? We have a PHP4 site that worked fine under a previous RedHat build, but we just can't get it working on this Debian build.
Here's what we're running:
Debian 3.0r1 "woody"
Kernel 2.4.18-bf2.4
Apache 1.3.26-0woo
postgres 7.2.1-2wood
php 4.1.2-6wood
We've applied a s
Greetings;
I have successfully installed the 8003ep nic.
Many thanks to Michael Heldebrant for his moral support, the sharing of
which files I may want to look at to determine conflicts, and for his suggestion
that sacrificing a brown rooster (rather than the white one I was tying
to the alter wi
On 15 Aug 2001 12:03:45 -0500, [EMAIL PROTECTED] wrote:
> Mike -
>
> Thank you for the response. Here we go.
>
> I have a hard drive, 5-1/4 and 3-1/2 floppies, 8003ep nic. It's basically
> a vanilla Dell 486P/50. ;-)
>
> >You don't happen to have a soundcard with a midi port around there do
>
Mike -
Thank you for the response. Here we go.
I have a hard drive, 5-1/4 and 3-1/2 floppies, 8003ep nic. It's basically
a vanilla Dell 486P/50. ;-)
>You don't happen to have a soundcard with a midi port around there do
>you? What does /proc/ioports /proc/interrupts look like on your system?
On 14 Aug 2001 16:19:19 -0500, [EMAIL PROTECTED] wrote:
> Greetings;
>
> I have a 8003EP nic in a 32MB/3GB 486/50. I have the base system installed
> via floppy (no cd). I *could* install more of Debian via ppp. But since
> I have access to a T1+ line I'd much prefer to install via the network.
Subject: 8003EP nic installation woes...
Date: Tue, Aug 14, 2001 at 04:19:19PM -0500
In reply to:[EMAIL PROTECTED]
Quoting [EMAIL PROTECTED]([EMAIL PROTECTED]):
> Greetings;
>
> I have a 8003EP nic in a 32MB/3GB 486/50. I have the base system installed
> via floppy
Greetings;
I have a 8003EP nic in a 32MB/3GB 486/50. I have the base system installed
via floppy (no cd). I *could* install more of Debian via ppp. But since
I have access to a T1+ line I'd much prefer to install via the network.
But I can't get the dang-blamed card configured.
I went to www.
Wayne Topa wrote:
>
> Subject: Re: debian installation woes
> Date: Tue, Nov 02, 1999 at 10:59:08AM -0800
>
> In reply to:aphro
>
> Quoting aphro([EMAIL PROTECTED]):
> > you can't boot a logical drive, it must be primary..
> >
> > nate
Subject: Re: debian installation woes
Date: Tue, Nov 02, 1999 at 10:59:08AM -0800
In reply to:aphro
Quoting aphro([EMAIL PROTECTED]):
> you can't boot a logical drive, it must be primary..
>
> nate
OH?? Gee, I wonder why my potato dist is working so well
on h
Nick Phillips wrote:
>
> >
> > you can't boot a logical drive, it must be primary..
> >
>
> IIRC, LILO should be able to boot from any partition, although it gets
> a bit more complicated if the interesting bits aren't near enough to the
> front of the disk...
You *can* boot linux from a logic
--- Phil Brutsche <[EMAIL PROTECTED]> wrote:
> > I'm probably just going to re-download the whole
> thing
> > and try again.
>
> Ewww - I would try to find a copy of Debian 2.1 (or
> 2.0) at a local
> 'Borders' bookstore - much more convenient.
Believe me, I would if I could.
Unfortunately I live
>
> you can't boot a logical drive, it must be primary..
>
IIRC, LILO should be able to boot from any partition, although it gets
a bit more complicated if the interesting bits aren't near enough to the
front of the disk...
I couldn't tell from the bits of previous posts I could see exactly how
you can't boot a logical drive, it must be primary..
nate
[mailto:[EMAIL PROTECTED] ]--
Vice President Network Operations http://www.firetrail.com/
Firetrail Internet Services Limited http://www.aphroland.org/
Everett, WA 425-348-7336
uot;Re: debian
> installation woes"
>
> > 3: swap 127 megs (no swap may exceed 128mb, but
> you
> > can have more than one. Rummor has it that swap
>
> This 128M limit is no longer true in 2.2.x kernels.
> From the Changes
> file in the kernel s
*- On 2 Nov, Kenneth Scharf wrote about "Re: debian installation woes"
> 3: swap 127 megs (no swap may exceed 128mb, but you
> can have more than one. Rummor has it that swap
This 128M limit is no longer true in 2.2.x kernels. From the Changes
file in the kernel source doc
>1: w95 (1 gig)
>2: extended (the rest of it)
> 5: linux (1gig)
> 6: vfat storage partition (2 gigs)
> 7: vfat storage partition (the rest of it)
> 8: linux swap (150 megs)
There MAY be a problem with the boot sector crossing a
1024 cyl bound, not sure if scsi has this problem.
Just to b
On 2/11/99 Mock Ko wrote:
1: w95 (1 gig)
2: extended (the rest of it)
^
5: linux (1gig)
6: vfat storage partition (2 gigs)
7: vfat storage partition (the rest of it)
8: linux swap (150 megs)
I've gotten it to install and reboot off the mbr now
(I was usin
A long time ago, in a galaxy far, far way, someone said...
[...]
> Other hardware:
> - realtek 8029 PCI ethernet card (the installer can't
> find the module to install this card in the installer)
This uses the pci-ne2k module.
> - SB16
> - Riva TNT2 AGP
>
> I've gotten it to install and reboot
Whoops! I knew I forgot something =)
I'm running a celeron 300A system, 128MB ram, adaptec
2940UW, Seagate 9gig (scsi) partitioned as follows:
1: w95 (1 gig)
2: extended (the rest of it)
5: linux (1gig)
6: vfat storage partition (2 gigs)
7: vfat storage partition (the rest of it)
8: l
On Tue, 2 Nov 1999, Mock Ko wrote:
> I did the installation for debian, but it failed
> miserably.
>
> It did the initial install, but it crashed every time
> I rebooted, so I booted from the boot disk I created.
Hi,
I think that we need to know at least something about your hardware
specificat
I did the installation for debian, but it failed
miserably.
It did the initial install, but it crashed every time
I rebooted, so I booted from the boot disk I created.
Once I did that (it took about 15 minutes to read the
kernel from the floppy), it went to the main installer
thing.
I selected th
t;[EMAIL PROTECTED]>
To: Tom Anzalone <[EMAIL PROTECTED]>
Copies to: Debian User List
Subject: Re: Installation woes
> On Thu, 3 Dec 1998, Tom Anzalone wrote:
>
> > I had sent an earlier message regarding installation problems and
On Thu, 3 Dec 1998, Tom Anzalone wrote:
> I had sent an earlier message regarding installation problems and
> did receive some messages back but was unable to read them. So
> I will try this again. (Thanks to everyone that did reply) I have tried
> to install Debian numerous times on my machi
I had sent an earlier message regarding installation problems and
did receive some messages back but was unable to read them. So
I will try this again. (Thanks to everyone that did reply) I have tried
to install Debian numerous times on my machine:
P133, 128meg, 8.4 ide, 2.5 ide (install driv
Connor 60MB HDD
Oak Technologies Video Card (OTI037C)
486-SX 25
8MB
5.25 Drive
Hamish Moffatt wrote:
> On Thu, Nov 26, 1998 at 03:30:22PM +1300, Kieran wrote:
> > nope...It's only got a 5.25" drive and I was having problems even getting
> > past the
> > insert root.bin thing...I paralleled all d
On Thu, Nov 26, 1998 at 03:30:22PM +1300, Kieran wrote:
> nope...It's only got a 5.25" drive and I was having problems even getting
> past the
> insert root.bin thing...I paralleled all data to the HD and then ran
> install...it
> keeps saying:
> unknown interrupt
> then it loads the selection sc
nope...It's only got a 5.25" drive and I was having problems even getting past
the
insert root.bin thing...I paralleled all data to the HD and then ran
install...it
keeps saying:
unknown interrupt
then it loads the selection screen and hangs like a wild stallion...
Hamish Moffatt wrote:
> On Th
On Thu, Nov 26, 1998 at 02:33:48PM +1300, Kieran wrote:
> My 486 is hanging when it gets to the screen selection screen. I can't
> move with cursors, can't enter, can't escape, can't reboot...any ideas?
> I'm installing off a Hard Drive. Cheers!
Is scroll lock on, by any chance?
Hamish
--
Ham
My 486 is hanging when it gets to the screen selection screen. I can't
move with cursors, can't enter, can't escape, can't reboot...any ideas?
I'm installing off a Hard Drive. Cheers!
K
--
K I E R A N G A R B U T T
Email - [EMAIL PROTECTED]
Cellphone - 025 289 34 97
Homepage - http://homepages.
In article <[EMAIL PROTECTED]> you write:
>On Tue, 17 Dec 1996, Tim Sailer wrote:
>
>> You may have one of the WD drives that need to be flashed with
>> new BIOS. You can get the info and programs off their web site
>> (if I remember right)...
>
>d/led the firmware upgrade, the upgrade said I was u
On Tue, 17 Dec 1996, Tim Sailer wrote:
> You may have one of the WD drives that need to be flashed with
> new BIOS. You can get the info and programs off their web site
> (if I remember right)...
d/led the firmware upgrade, the upgrade said I was up to date. I then
through it in my 486dx4/100 bo
On Tue, 17 Dec 1996, Tim Sailer wrote:
> You may have one of the WD drives that need to be flashed with new BIOS.
> You can get the info and programs off their web site (if I remember
> right)... Tim
Pointed Lynx to www.wdc.com before I hit the reply button! thanks!
--
In your email to me, Daniel Stringfield, you wrote:
>
>
> I bought a 2.5 gig (Western Digital) IDE hard drive. It seems to be
> making weirdness happen on the machine its on. (a pentium 133, 430vx
> motherboard, 16mb ram). Whats happening on THIS machine is that the BIOS
> autodetects it, but
I bought a 2.5 gig (Western Digital) IDE hard drive. It seems to be
making weirdness happen on the machine its on. (a pentium 133, 430vx
motherboard, 16mb ram). Whats happening on THIS machine is that the BIOS
autodetects it, but "locks up" on boot. If I disable hard drive in CMOS,
boots ok, g
Hi,
> ok... I think I got Debian installed, at least part way I have a few
> problems
> though... 1st is when my computer turns on, it says "FA:" I figured out what
> this is
> (choses your method of booting, right?) I press "A" and it says "1234F"
> Pressing 1 gets
> me Windows 95, "F
ok... I think I got Debian installed, at least part way I have a few
problems
though... 1st is when my computer turns on, it says "FA:" I figured out what
this is
(choses your method of booting, right?) I press "A" and it says "1234F"
Pressing 1 gets
me Windows 95, "F" will boot from a
73 matches
Mail list logo
