[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#240606: installation-reports



Package: installation-reports

Debian-installer-version: <Fill in date and from where you got the image>
uname -a: <The result of running uname -a on a shell prompt>
Date: <Date and time of the install>
Method: <How did you install?  What did you boot off?  If network
      install, from where?  Proxied?>

Machine: Duron 1.5G chip on a Microtek MS6378 motherboard
Processor: Duron
Memory: 637896K
Root Device: 120G drive

Root Size/partition table:
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/hda1            116682960  13492308 103190652  12% /
tmpfs                   318948         0    318948   0% /dev/shm
/dev/hdc1            117214656  76800924  40413732  66% /home/ftp/pub

Output of lspci:

Base System Installation Checklist:
Initial boot worked:    [O]
Configure network HW:   [O]
Config network:         [ Other -- See Below ]
Detect CD:              [O]
Load installer modules: [O]
Detect hard drives:     [O]
Partition hard drives:  [O]
Create file systems:    [ Other -- See Below ]
Mount partitions:       [O]
Install base system:    [O]
Install boot loader:    [O]
Reboot:                 [O]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Comments/Problems:

#1 Network --

This is my second Debian install.  The following comments hold true for my
second *and* third install.  The third was a reinstall on my *first*
computer.

For some unknown reason, my router/firewall (D-Link DI-604) is no longer
refusing to send DCHP info to computers that are in it's table as having a
static IP.

As a result, both machines were autoconfigured for DCHP, when I would
really like it to be static IP.  (One of the two machines is a server...)

Any thoughts on how to go about fixing this?

#2 Create File Systems --

This happened in both my second and third install.  Actually, it happened
(but was left unreported) on my first install, because I didn't notice it
at the time.

I've chosen to run a Reiser File System.  As a result, during boot, I get
a message that it can't check things because it's the wrong file system
type.  It errors out, and then continues on.  Not that big of a deal,
but...

Mar 28 02:58:45 liberator kernel: Journalled Block Device driver loaded
Mar 28 02:58:45 liberator kernel: VFS: Can't find ext2 filesystem on dev
ide0(3,1).
Mar 28 02:58:45 liberator kernel: Unable to identify CD-ROM format.
Mar 28 02:58:45 liberator kernel: FAT: bogus logical sector size 0
Mar 28 02:58:45 liberator kernel: VFS: Can't find a valid FAT filesystem
on dev 03:01.
Mar 28 02:58:45 liberator kernel: reiserfs: found format "3.6" with
standard journal
Mar 28 02:58:45 liberator kernel: reiserfs: checking transaction log
(device ide0(3,1)) ...

Otherwise, the installs went rather smoothly.

(Data on the other computer I installed at the same time:  Emachines
eTower 533i, with 192 Meg Ram intel Celeron chip.)

Krikket





Reply to: