Before this I was getting signal 10 (operational error, reboot) on
/dev/hda7. However, if i went into single user mode and fsck -f'd it, it
was fine, no errors. So i was wondering if anyone else had had this
problem, if it was a known issues, if it's some weird special case, etc...
i realize that fdisk complains about partition 1 nore ending on a cylinder
boundry, however, the drive is 14 gigs, and i assume that fdisk is simply
confused... it's worked perfectly under 2.2.x and now seems to be fine
under 2.3.26 after i do non-parrallel fsck... obviously, being hda, it's
an IDE drive... it's an IBM 14GXP 14gb 7200 rpm drive.
I also included the info on my second drive (/home) just in case someone
felt it might have an impact. It's one huge paritition, but nothing seems
to complain about it.
info follows:
[jane]:~/uname -a
Linux jane 2.3.26 #6 Wed Nov 10 01:07:45 EST 1999 i686 unknown
Command (m for help): p
Disk /dev/hda: 255 heads, 63 sectors, 1757 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 879 7060536 b Win95 FAT32
Partition 1 does not end on cylinder boundary:
phys=(1023, 15, 63) should be (1023, 254, 63)
/dev/hda2 * 880 896 136552+ 83 Linux
/dev/hda3 897 1757 6915982+ 5 Extended
/dev/hda5 897 1027 1052226 83 Linux
/dev/hda6 1028 1158 1052226 83 Linux
/dev/hda7 1159 1723 4538331 83 Linux
/dev/hda8 1724 1740 136521 82 Linux swap
/dev/hda9 1741 1757 136521 82 Linux swap
Command (m for help): p
Disk /dev/hdd: 16 heads, 63 sectors, 32760 cylinders
Units = cylinders of 1008 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hdd1 1 32760 16511008+ 83 Linux
ps. does anyone know if there are known issues with USB mice being
"unresponsive" in 2.3.x? My mouse seems sluggish, doesn't pick up clicks
as nicely as the ps/2, etc... any info would be appreciated, and any
pointers would be helpful...
also, does anyone know the equivalent for this under 2.3.x?:
ioaddr = pcidev->base_address[0];
i looked around for a while, and all i could find that seems to make any
sense is something like:
ioaddr = pcidev->resource[0].start;
but this is not working, and i haven't taken the time to really look at a
lot of this, and wondered if someone here might be able to give me the
quick fix... this code is from the sblive driver (emu10k1)... i got it to
build, but I get "Device or resource busy"... i'm assuming that's because
i'm ending up w/ the wrong base address... otherwise, i think i might be
semi-close to having it working... but then again, i'm not too familiar w/
drivers, so i could be way off-base...
thanks in advance...
andy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/