Re: Re: stuck on black screen

Hi

I've done a fresh, by-the-book, RR install of the GPE tarball, with the
partition table being the only thing untouched. I will repartition
shortly according to previous advice and see how that goes. Until then,
here's what I've got.

On Wed, 2007-06-06 at 14:40 +1000, Marcus Brown wrote:

> # e2fsck -f /dev/hda2 (or appropriate node on a host)

e2fsck 1.40-WIP (14-Nov-2006)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Familiar-0.8.4: 3392/119808 files (0.1% non-contiguous), 16111/239568
blocks

> # fdisk -l /dev/hda2

Disk /dev/sdb2: 981 MB, 981270528 bytes
32 heads, 62 sectors/track, 966 cylinders
Units = cylinders of 1984 * 512 = 1015808 bytes

Disk /dev/sdb2 doesn't contain a valid partition table

Also, /dev/sdb output:

Disk /dev/sdb: 1031 MB, 1031675904 bytes
32 heads, 62 sectors/track, 1015 cylinders
Units = cylinders of 1984 * 512 = 1015808 bytes

   Device Boot Start End Blocks Id System
/dev/sdb1 1 49 48577 b W95 FAT32
/dev/sdb2 50 1015 958272 83 Linux

>
> You *might* be able to get more info using the RR-kernel on your card,
> but I can't verify or support it.
> RamdiskRescue should be able to give you all sorts of information if
> you run through all the card-related tests and then save the syslog.
> Posting the gzipped syslog with your next post *might* help.

The syslog file is included as an attachment.

Thanks

--
Joshua