On Mon, 2023-11-20 at 11:21 +0100, to...@tuxteam.de wrote:
> (and oh, it hasn't been mentioned: make super-sure some smart and
> overly helpful automounter has got hold of the USB).
That's a good point. I tend to use an Ubuntu live image to do things
like cloning my main disk, and I've wasted quit
On Mon, Nov 20, 2023 at 11:27:45AM +0100, Thomas Schmitt wrote:
[...]
> to...@tuxteam.de wrote:
[...]
> > all blocks of the block device get overwritten,
>
> Not all. Only as far as the new image reaches. That's how the GPT backup
> can survive (xorriso-dd-target would explicitely overwrite the
Hi,
Zenaan Harkness wrote:
> > > all of the grub menu options (Graphical
> > > install, Graphical expert install, Expert install, etc) give 2 errors:
> > > 1) "..invalid buffer alignment... " with some long number beginning with
> > > minus.
> > > 2) kernel fail to load error, presumably due to er
On Mon, Nov 20, 2023 at 11:17:15AM +0100, to...@tuxteam.de wrote:
[...]
> For reference, what I do is
>
> sudo dd if=image.file of=/dev/sdX bs=1M oflag=sync status=progress
(and oh, it hasn't been mentioned: make super-sure some smart and
overly helpful automounter has got hold of the USB).
On Mon, Nov 20, 2023 at 09:13:01PM +1100, Zenaan Harkness wrote:
> On Monday, November 20, 2023, wrote:
> > On Mon, Nov 20, 2023 at 08:59:02AM +, Tom Furie wrote:
> >> Zenaan Harkness writes:
> >>
> >> > Attempting a fresh Debian stable install with
> >> > debian-12.2.0-amd64-netinst.iso (lat
On Monday, November 20, 2023, wrote:
> On Mon, Nov 20, 2023 at 08:59:02AM +, Tom Furie wrote:
>> Zenaan Harkness writes:
>>
>> > Attempting a fresh Debian stable install with
>> > debian-12.2.0-amd64-netinst.iso (latest default amd64 boot image), `cp
>> > deiban-...iso /dev/sdX; sync`, and re
On Mon, Nov 20, 2023 at 08:59:02AM +, Tom Furie wrote:
> Zenaan Harkness writes:
>
> > Attempting a fresh Debian stable install with
> > debian-12.2.0-amd64-netinst.iso (latest default amd64 boot image), `cp
> > deiban-...iso /dev/sdX; sync`, and rebooted to the usb stick with the
>
> You ca
Zenaan Harkness writes:
> Attempting a fresh Debian stable install with
> debian-12.2.0-amd64-netinst.iso (latest default amd64 boot image), `cp
> deiban-...iso /dev/sdX; sync`, and rebooted to the usb stick with the
You can't just copy the iso to the stick and get it to boot. This stick
must ha
In case it's useful, my laptop is currently running Ubuntu - I'm
wondering if it's possible to do some sort of chroot from Ubuntu into
the USB stick, so that I can format the laptop's SSD and begin the
install process that way? Surely that has been thought of before?
(That said, I ought ensure I c
Attempting a fresh Debian stable install with
debian-12.2.0-amd64-netinst.iso (latest default amd64 boot image), `cp
deiban-...iso /dev/sdX; sync`, and rebooted to the usb stick with the
grub graphical screen, but all of the grub menu options (Graphical
install, Graphical expert install, Expert ins
Anyone knows where this kerberos detailed log might be. I can't find it.
Failed to start Kerberos 5 Key Distribution Center.
See 'systemctl status krb5-kdc.service' for details.
I found this on the boot.log
And the following somewhere else:
Mar 8 11:04:35 G0 systemd[1]: Starting Kerberos 5 Ke
On 24/07/15 12:24 PM, Nathaniel Nelson wrote:
Hello! I hope this is the proper way to seek Debian support, and that
I'm not making a mistake/emailing the wrong list/whatever.
I've never used Debian before, and I'm trying to install it on an old
Mac Mini with a PowerPC G4 processor. I downloade
Should have re-read before I posted.
On Sat, Jul 25, 2015 at 1:36 PM, Joel Rees wrote:
> [...] but I've generally had the best success using the
> Mac OS 10 partitioning tool to set up the three Mac OS style
> partitions I use for debian, one for yaboot, one for the root
> partition, and one for
2015/07/25 1:42 "Nathaniel Nelson" :
>
> Hello! I hope this is the proper way to seek Debian support, and that I'm not
> making a mistake/emailing the wrong list/whatever.
>
There is a better list. I've cross-posted, but I haven't set the reply header.
> I've never used Debian before, and I'm tr
Hello! I hope this is the proper way to seek Debian support, and that I'm
not making a mistake/emailing the wrong list/whatever.
I've never used Debian before, and I'm trying to install it on an old Mac
Mini with a PowerPC G4 processor. I downloaded the PowerPC iso file
(debian-8.1.0-powerpc-netin
On Fri, 6 Jun 2014 13:55:23 -0600
Glenn English wrote:
> I get "ERST:Failed to get Error Log Address Range" when I boot the
> new server I'm preparing.
This recent thread:
https://lists.debian.org/debian-kernel/2014/05/msg00213.html
suggest that the Debian kernel's involved.
So, I would say, ei
I get "ERST:Failed to get Error Log Address Range" when I boot the new server
I'm preparing.
There is very little on the net about it -- one that almost says not to worry
about and some others that imply there might be an incorrectly configured
kernel (this is an untouched Wheezy kernel, update
From: billnick...@hotmail.com
To: t@gmx.de; debian-user@lists.debian.org
Subject: RE: I have a boot error. concerning not finding acl.end
Date: Sat, 23 Oct 2010 18:55:00 -0500
Thanks, a perfect fix.
> To: debian-user@lists.debian.org
> From: t@gmx.de
> Subject: Re:
Thanks, a perfect fix.
> To: debian-user@lists.debian.org
> From: t@gmx.de
> Subject: Re: I have a boot error. concerning not finding acl.end
> Date: Sat, 23 Oct 2010 21:58:23 +0200
>
> Bill Nickels wrote the following on 23.10.2010 21:36
>
> > The system conti
Bill Nickels wrote the following on 23.10.2010 21:36
> The system continues to boot without errors and no indications of problems.
> Linux debianhp 2.6.32-5-amd64. Squeeze.dmesg doesn't reference it
http://bugs.debian.org/600446
cheers
--
bye Thilo
4096R/0xC70B1A8F
721B 1BA0 095C 1ABA 3FC6
The system continues to boot without errors and no indications of problems.
Linux debianhp 2.6.32-5-amd64. Squeeze.dmesg doesn't reference it
On Feb 8, 2008 5:27 PM, Michael D. Norwick <[EMAIL PROTECTED]> wrote:
> Raj Kiran Grandhi wrote:
> > Schiz0 wrote:
> >> I have Lenny running on a laptop. I selected to use grub version 2
> >> when it prompted me (back when I first installed grub).
> >>
> >> I just now updated my apt sources and ran
Raj Kiran Grandhi wrote:
Schiz0 wrote:
I have Lenny running on a laptop. I selected to use grub version 2
when it prompted me (back when I first installed grub).
I just now updated my apt sources and ran a upgrade. It upgraded the
grub package, and I rebooted.
Now, after the bios tests, the te
I observed the same here
Schiz0 wrote:
I have Lenny running on a laptop. I selected to use grub version 2
when it prompted me (back when I first installed grub).
I just now updated my apt sources and ran a upgrade. It upgraded the
grub package, and I rebooted.
Now, after the bios tests, the te
Schiz0 wrote:
I have Lenny running on a laptop. I selected to use grub version 2
when it prompted me (back when I first installed grub).
I just now updated my apt sources and ran a upgrade. It upgraded the
grub package, and I rebooted.
Now, after the bios tests, the text "Grub loading kernel" f
I have Lenny running on a laptop. I selected to use grub version 2
when it prompted me (back when I first installed grub).
I just now updated my apt sources and ran a upgrade. It upgraded the
grub package, and I rebooted.
Now, after the bios tests, the text "Grub loading kernel" flashes up
for ab
On Sat, Aug 25, 2007 at 12:09:34PM -0400, Frank McCormick wrote:
> Took your advice here and re-installed Hal...at least the error
> message goes away. I have no idea which package was still referring
> to Haldaemonhow would I track that down ?
>
I suppose the brute-force method would be a
On Sat, 25 Aug 2007 15:42:45 +0200
Florian Kulzer <[EMAIL PROTECTED]> wrote:
> On Sat, Aug 25, 2007 at 08:46:01 -0400, Frank McCormick wrote:
> > On Sat, 25 Aug 2007 10:23:54 +0200
> > Florian Kulzer wrote:
>
> [...]
>
> > > > > On Thu, Aug 23, 2007 at 21:25:29 -0400, Frank McCormick wrote:
> >
On Sat, 25 Aug 2007 15:42:45 +0200
Florian Kulzer <[EMAIL PROTECTED]> wrote:
> On Sat, Aug 25, 2007 at 08:46:01 -0400, Frank McCormick wrote:
> > On Sat, 25 Aug 2007 10:23:54 +0200
> > Florian Kulzer wrote:
>
> [...]
>
> > > > > On Thu, Aug 23, 2007 at 21:25:29 -0400, Frank McCormick wrote:
> >
On Sat, Aug 25, 2007 at 08:46:01 -0400, Frank McCormick wrote:
> On Sat, 25 Aug 2007 10:23:54 +0200
> Florian Kulzer wrote:
[...]
> > > > On Thu, Aug 23, 2007 at 21:25:29 -0400, Frank McCormick wrote:
> > > > > For the past few weeks I've been seeing an error message fly by
> > > > > (doesn't see
On Sat, 25 Aug 2007 10:23:54 +0200
Florian Kulzer <[EMAIL PROTECTED]> wrote:
> On Fri, Aug 24, 2007 at 20:46:22 -0400, Frank McCormick wrote:
> > On Fri, 24 Aug 2007 15:07:49 +0200 Florian Kulzer wrote:
> > > n Thu, Aug 23, 2007 at 21:25:29 -0400, Frank McCormick wrote:
> > > > For the past few we
On Fri, Aug 24, 2007 at 20:46:22 -0400, Frank McCormick wrote:
> On Fri, 24 Aug 2007 15:07:49 +0200 Florian Kulzer wrote:
> > n Thu, Aug 23, 2007 at 21:25:29 -0400, Frank McCormick wrote:
> > > For the past few weeks I've been seeing an error message fly by
> > > (doesn't seem to affect anything) a
On Fri, 24 Aug 2007 15:07:49 +0200
Florian Kulzer <[EMAIL PROTECTED]> wrote:
> n Thu, Aug 23, 2007 at 21:25:29 -0400, Frank McCormick wrote:
> > For the past few weeks I've been seeing an error message fly by
> > (doesn't seem to affect anything) and I curious what's going on.
> >
> > the message
On Thu, Aug 23, 2007 at 21:25:29 -0400, Frank McCormick wrote:
> For the past few weeks I've been seeing an error message fly by (doesn't
> seem to affect anything) and I curious what's going on.
>
> the message is:
>
> dbus unknown username "haldemon" in message bus configuration file.
It shoul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
For the past few weeks I've been seeing an error message fly by (doesn't
seem to affect anything) and I curious what's going on.
the message is:
dbus unknown username "haldemon" in message bus configuration file.
I'm running Sid...so it shouldn'
On Thu, Jun 14, 2007 at 01:00:03PM -0700, yong lee wrote:
> I am not a Linux expert. I hope someone would kindly
> help me or give me some suggestions to fix the
> problem.
>
> I just installed a pre-made/customized Linux 2.6.x
> kernel. I converted its installation package from the
> .rpm format
yong lee <[EMAIL PROTECTED]>:
>
> I am not a Linux expert. I hope someone would kindly help me or
> give me some suggestions to fix the problem.
>
> I just installed a pre-made/customized Linux 2.6.x kernel. I
> converted its installation package from the .rpm format to a .deb
> format using
On Thu, 14 Jun 2007 13:00:03 -0700 (PDT)
yong lee <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I am not a Linux expert. I hope someone would kindly
> help me or give me some suggestions to fix the
> problem.
>
> I just installed a pre-made/customized Linux 2.6.x
> kernel. I converted its installation pa
Hi,
I am not a Linux expert. I hope someone would kindly
help me or give me some suggestions to fix the
problem.
I just installed a pre-made/customized Linux 2.6.x
kernel. I converted its installation package from the
.rpm format to a .deb format using alien command.
After the installation and a
David Fuchs wrote:
thanks for the help.
as I mentioned, the modules.dep file is there - but not in the initrd
image that's created.
I've addressed that same issue:
http://lists.debian.org/debian-user/2007/03/msg00772.html
and never got an answer.
modules.dep is not in the initrd of kernels t
thanks for the help.
as I mentioned, the modules.dep file is there - but not in the initrd
image that's created.
however, I've solved it by recompiling the kernel with the parallel
port driver as a module rather than into the kernel. it seems it was
this driver that tried to load some additional
On Mon, 2007-05-21 at 22:33 +0200, David Fuchs wrote:
> hi all,
>
> I want to have a grsecurity enabled kernel and thus compiled my own.
> while doing so, I also removed tons of modules from the kernel config
> (drivers I know I'll never need), and chose to compile some into the
> kernel instead o
hi all,
I want to have a grsecurity enabled kernel and thus compiled my own.
while doing so, I also removed tons of modules from the kernel config
(drivers I know I'll never need), and chose to compile some into the
kernel instead of modules (e.g., drivers for my sata disks).
I followed the dire
hi
I have a system with sarge stable up to date
Because the driver's reason, I update the kernel to 2.6.14.5.
Everything is OK, except some error in /var/log/boot:
Tue Jan 10 18:42:30 2006: Setting up LVM Volume Groups...Tue Jan 10 18:42:30 2006: Reading all physical volumes. This may take a while.
Marco Calviani wrote:
>i've got an error (maybe a warning) during the boot up process, as
> written in /var/log/boot:
> Cleaning /tmpfind: warning: you have specified the -maxdepth option
> after a non-option argument -perm, but options are not positi
> onal (-maxdepth affects tests spe
Hi,
i've got an error (maybe a warning) during the boot up process, as
written in /var/log/boot:
Cleaning /tmpfind: warning: you have specified the -maxdepth option
after a non-option argument -perm, but options are not positi
onal (-maxdepth affects tests specified before it as well as those
Oops... sends message in sucky outlook... sorry. See below
for the rest of my message...
-Original Message-
From: Michael Kahle
Sent: Wednesday, March 03, 2004 11:27 AM
To: Debian User List
Subject: boot error -> cdrom: open failed.?
Hello. I recently built a 2.6.3 custom kernel
Hello. I recently built a 2.6.3 custom kernel for my debian/unstable
machine. I am using the unstable kernel-source package. When booting my
computer now I get a strange error:
cdrom: open failed.
cdrom: open failed.
cdrom: open failed.
cdrom: open failed.
--
To UNSUBSCRIBE, email to [EMAIL P
On Wed, 28 May 2003 18:10:23 +0200
Adam Majer <[EMAIL PROTECTED]> wrote:
> On Fri, May 09, 2003 at 12:22:48PM +, Guldo K wrote:
> > Hello everybody :-)
> >
> > usb_control/bulk_msg: timeout
> > usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x85 len 512 ret -110
>
> This means that you have some US
On Fri, May 09, 2003 at 12:22:48PM +, Guldo K wrote:
> Hello everybody :-)
>
> usb_control/bulk_msg: timeout
> usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x85 len 512 ret -110
This means that you have some USB device that either broken or
the driver for it is broken. Some IN endpoint (EP: 5 IN )
No, I have all the programs updated as of today. Everything is as
required. I'll try reconfiguring the kernel
Barbara
Michael Wagner wrote:
On Mittwoch, 12. Dez. 2001 at 12:36:35, Barbara Pfieffer wrote:
When I boot the new kernel, it starts to boot, then I get over a
screenful of the same
On Mittwoch, 12. Dez. 2001 at 12:36:35, Barbara Pfieffer wrote:
>When I boot the new kernel, it starts to boot, then I get over a
>screenful of the same error message:
>
>kmod: failed to exec /sbin/modprobe -s -k binfmt-464c, errno = 8
>
>Where did I go wrong?
Hello Barbara,
you didn't read the
I'm currently running Woody, with kernel 2.2.19pre17.
I wanted to try the newest kernel 2.4.16. I downloaded the kernel source
and the pcmicia source, since this is a laptop with a pcmcia network
card. I unpack them, run make menuconfig, being sure to put pcmcia in as
a module. I run make-kpkg
According to Donald R. Spoon on Wed, Nov 28, 2001 at 04:28:17AM -0600:
> See comments in your text copied below.
>
Thank you for a complete and very informative answer -
Well I have not managed to "Fix" the /boot for my 2.4 kernel,
i did manage for the previous 2.19 though.
I re-installed the k
See comments in your text copied below.
Cheers,
-Don Spoon-
Eric Smith <[EMAIL PROTECTED]> wrote:
> I installed the new lilo and let debconf create a new
> lilo.conf and add a boot sector. Before restarting,
> however I added an entry for Windows, then /sbin/lilo -v
> which reported nothing a
Could some one please advise whether this is the best / safest
way to recover a bootable system?
backup the / partition.
reinstall a base system - upgrade this to sid - copy back
the / omitting /boot (I actually have /boot on another partition).
Thanks for an answer.
According to Eric Smith on
I installed the new lilo and let debconf create a new
lilo.conf and add a boot sector. Before restarting,
however I added an entry for Windows, then /sbin/lilo -v
which reported nothing abnormal.
However when i tried to reboot, I get:
unable to mount root fs
add a root= entry (or something to th
Try
#> dmesg
to read boot messages at your leisure.
The remaining pcmcia messages probably come from scripts in etc/rc*.d/
directories. Try
#> ls -l /etc/rc*.d/ | grep pcmcia
to see which such scripts are softlinked there. I should be 'OK' to
remove those links as well as the corresponding script
dpkg --purge pcmcia-cs
Eileen Orbell wrote:
>
> Thank you that removed most of the errors. When I ran that command I did
> receive the following errors though:
> directory not empty so it could not remove all reference..
> can I delete these directories???
> I still get some reference to pcmcia o
Thank you that removed most of the errors. When I ran that command I did
receive the following errors though:
directory not empty so it could not remove all reference..
can I delete these directories???
I still get some reference to pcmcia on boot...
Thanks
At 01:41 AM 12/5/2000 +0100, you wr
I reconfig my kernel and now on boot I get about 5 -6 lines of error re
PCMICIA modules. Because it boots fast I cannot read them all but I am
assuming I am missing the modules. I do not have any PCMCIA hardware
anyway so can I remove this? I did not see any reference to it in make
xconfig??
On Mon, Dec 04, 2000 at 07:21:38PM -0500, Eileen Orbell wrote:
> I reconfig my kernel and now on boot I get about 5 -6 lines of error re
> PCMICIA modules. Because it boots fast I cannot read them all but I am
> assuming I am missing the modules. I do not have any PCMCIA hardware
> anyway so c
I reconfig my kernel and now on boot I get about 5 -6 lines of error re
PCMICIA modules. Because it boots fast I cannot read them all but I am
assuming I am missing the modules. I do not have any PCMCIA hardware
anyway so can I remove this? I did not see any reference to it in make
xconfig??
I reconfig my kernel and now on boot I get about 5 -6 lines of error re
PCMICIA modules. Because it boots fast I cannot read them all but I am
assuming I am missing the modules. I do not have any PCMCIA hardware
anyway so can I remove this? I did not see any reference to it in make
xconfig??
Hello, the list! I just upgraded from slink up to potato and am now
getting a nice error on bootup that's slowing things down a big. I
can't seem to find the error in my logs anywhere, but it says something
about my boot sector not matching what's saved, gives a bunch of sector
numbers, then says
On Tue, Jun 20, 2000 at 10:32:31AM +0100, Moore, Paul wrote:
> But the message comes at bootup. AFAIK, the root FS is always mounted
> read-only in the first instance, and is then remounted read-write later in
> the boot sequence.
I think this is so.
> So this looks like a problem in the base De
AFAIK, the root filesystem is mounted read-write and remounted read-only
on errors...
Ron
On Tue, 20 Jun 2000, Moore, Paul wrote:
> From: Ron Rademaker [mailto:[EMAIL PROTECTED]
> > On Mon, 19 Jun 2000, Sven Burgener wrote:
> >
> > > Anyone know why do I get the following error upon bootup:
> >
From: Ron Rademaker [mailto:[EMAIL PROTECTED]
> On Mon, 19 Jun 2000, Sven Burgener wrote:
>
> > Anyone know why do I get the following error upon bootup:
> >
> > insmod: /lib/modules/2.2.15/misc/unix.o cannot create
> > /var/log/ksymoops/2619212757.ksyms Read Only Filesystem
> >
> Looks like
Looks like your root file system is mounted read only, try to do (as
root): touch /a (if no error occurs, don't forget to do rm /a). If it's
mounted read only, you can remount it read-write, but you better check out
your /etc/fstab.
Ron Rademaker
On Mon, 19 Jun 2000, Sven Burgener wrote:
> Hi al
Hi all
Anyone know why do I get the following error upon bootup:
insmod: /lib/modules/2.2.15/misc/unix.o cannot create
/var/log/ksymoops/2619212757.ksyms Read Only Filesystem
Indeed that file doesn't exist. Should I create it using /dev/null
or what?
If I should post more infos, please let
On Sat, 12 Jun 1999, Kevin A. Foss wrote:
> On Thu, Jun 10, 1999 at 07:55:58AM -0700, Lazar Fleysher wrote:
> > Hi everyone,
> >
> > I have noticed that sometimes I get this boot error:
> > mktime() failed unexpectedly (rc -1). Aborting.
> > Could someone
On Thu, Jun 10, 1999 at 07:55:58AM -0700, Lazar Fleysher wrote:
> Hi everyone,
>
> I have noticed that sometimes I get this boot error:
>
> mktime() failed unexpectedly (rc -1). Aborting.
>
> Could someone tell what and how dengerous it is?
This is probably from hwclock
Hi everyone,
I have noticed that sometimes I get this boot error:
mktime() failed unexpectedly (rc -1). Aborting.
Could someone tell what and how dengerous it is?
Thanks
ZORO
Take these broken wings and learn to fly
Hi All,
Just installed Gimp1.1 from potato using apt-get and got 11.4M of upgrade.
I'm using kernel 2.2.5 (F%$ HOSTILE!! aka Rules). Anyway, after the gimp
upgrade I get this error on boot.
initd 2.76 booting
could not initalize
It hangs for sometime the boots. Everything seems
I finally got a new kernel compiled. But when I boot it I get this error.
kmod: failed to exec /sbin/modprobe -s -k binfmt -464c errno=8
request_modle[binfmt-464c]:fork failed errno=11
it scroll up the screen and all I can do is crtl+alt+del, to reboot and
stop it. Luckly I can still bot my old k
Lindsay Allen writes:
>
>IIRC that is fixed by installing the latest setserial.
>
>> >> Ever since I switched to the dev kernel, I've had the following
>> >> message on boot:
>> >>
>> >> TIOCSER?WILD ioctl obsolete, ignored
Yup, that fixed it. Thanks!
octl obsolete, ignored
> >>
> >> I doesn't sound dangerous or anything, but a boot error just doesn't
> >> look good. So does anyone know how I could fix this? Is it a bug, just
> >> like the SIOCADDR thingy?
> >
> >It was my understanding t
Ossama Othman writes:
>Hi,
>
>> Ever since I switched to the dev kernel, I've had the following
>> message on boot:
>>
>> TIOCSER?WILD ioctl obsolete, ignored
>>
>> I doesn't sound dangerous or anything, but a boot error just doesn't
>
Hi,
> Ever since I switched to the dev kernel, I've had the following
> message on boot:
>
> TIOCSER?WILD ioctl obsolete, ignored
>
> I doesn't sound dangerous or anything, but a boot error just doesn't
> look good. So does anyone know how I could fix
Ever since I switched to the dev kernel, I've had the following
message on boot:
TIOCSER?WILD ioctl obsolete, ignored
I doesn't sound dangerous or anything, but a boot error just doesn't
look good. So does anyone know how I could fix this? Is it a bug, just
like the SIOCADDR thingy?
On Mon, 15 Dec 1997, Aaron Walker wrote:
> I just setup this experimental system to run Debian 1.3.1:
>
> 486SX/25
> 4MB RAM
> CL3424 w/512K
>
> A real POWER-HOUSE!!! I just put this machine together to test Debian
> 2.0 aka hamm.
> Anyways... When I try to boot the rescue disk, I get the messa
I just setup this experimental system to run Debian 1.3.1:
486SX/25
4MB RAM
CL3424 w/512K
A real POWER-HOUSE!!! I just put this machine together to test Debian
2.0 aka hamm.
Anyways... When I try to boot the rescue disk, I get the message:
RAMDISK: Compressed image found at block 0
It hanges for
I get this error message when I boot everytime. I didn't mean to put a MBR
on the drive, but I redid the one on hda. It is the secind HD on IDE.
Before I put the MBR on hdb, I didn't get the message.
Anyone have any suggestions about fixing the problem?
hdb: [DM6:MBR] [remap [DM6:MBR]] [656/12
Hello again...
I have been noticing some error messages during boot, that I have
been wondering about. I wonder if someone can tell me whether or
not I should be worried about these. The thing that is odd about
this is that my system seems to be working fine, as far as I can see.
Here are the e
84 matches
Mail list logo
