Memory?

ceh383 · 03-18-2012, 03:23 PM

Not sure if this is the right forum for this question.
I have a desktop machine running Slack 13.37_64bit. I have 8GB (2x4GB)DDR3 ram. System BIOS shows 8GB ~ 7.5GB for system 512MB for video. top, free, and conky show only 2.7GB installed. Just wondering if I missed something during the install? Or is there a config file somewhere that can be edited?

Celyr · 03-18-2012, 04:46 PM

Hi,

can you post the result of the

Code:

dmesg

command ? Thanks

TobiSGD · 03-18-2012, 05:04 PM

Are you sure you have the 64 bit version installed? Please post the output of

Code:

uname -a

ceh383 · 03-18-2012, 05:05 PM

Quote:

Originally Posted by Celyr

Hi,

can you post the result of the

Code:

dmesg

command ? Thanks

I get an error trying to post it..."The text that you have entered is too long (31993 characters). Please shorten it to 30000 characters long."

Is there a particular section you want to see?

onebuck · 03-18-2012, 05:14 PM

Hi,

Place it at: http://pastebin.com/ then provide the URL.

ceh383 · 03-18-2012, 05:24 PM

Quote:

Hi,

Place it at: http://pastebin.com/ then provide the URL.

dmesg at pastebin dmesg at pastebin

Quote:

Are you sure you have the 64 bit version installed? Please post the output of

uname -a

Code:

bash-4.1$ uname -a
Linux nightmare 2.6.37.6-smp #2 SMP Sat Apr 9 23:39:07 CDT 2011 i686 AMD Phenom(tm) II X6 1035T Processor AuthenticAMD GNU/Linux

T3slider · 03-18-2012, 05:27 PM

i686 = 32-bit Slackware (64-bit would show x86_64 instead). You would have to reinstall using proper 64-bit Slackware. I'm guessing you accidentally downloaded/burned/installed the wrong ISO at some point in the chain.

ceh383 · 03-18-2012, 05:33 PM

Quote:

Originally Posted by T3slider

i686 = 32-bit Slackware (64-bit would show x86_64 instead). You would have to reinstall using proper 64-bit Slackware. I'm guessing you accidentally downloaded/burned/installed the wrong ISO at some point in the chain.

Well that truly sucks, must have mislabeled the disks. I had a feeling that was the problem. Time to start over I guess.

Thanks, Chuck

ceh383 · 03-18-2012, 08:22 PM

Ok, re-downloaded the 64bit version. Now memory shows correctly.
I guess I had mislabeled the disk, oh well...
Threw everything away and started over....

Again thanks to all

ceh383 · 03-19-2012, 09:18 AM

This brings up a new issue. I have a second hard drive that has all the SlackBuilds and source code for everything I added to the original install. The drive has 3 partitions + swap space on it. During this install the swap was mounted, but I left the other partitions alone. Looking at cfdisk /dev/sdb I see the partitions, I edited fstab to point to them with the proper mount points, yet I have no access to them. Do I need to run mkdir?

Mark Pettit · 03-19-2012, 09:27 AM

Yes - whatever mountpoints you use in fstab must exist on disk somewhere.

ceh383 · 03-19-2012, 09:28 AM

Quote:

Originally Posted by Mark Pettit

Yes - whatever mountpoints you use in fstab must exist on disk somewhere.

Thanks, I'll try that when I get home tonight.

ceh383 · 03-20-2012, 12:03 AM

Ok, got it working.
Now when I do fdisk -l
I get this...

Code:

bash-4.1# fdisk -l

Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders, total 156301488 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x05d205d1

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *          63      385559      192748+  83  Linux
/dev/sda2          385560    39455639    19535040   83  Linux
/dev/sda3        39455640    40435604      489982+  83  Linux
/dev/sda4        40435605   156301487    57932941+   5  Extended
/dev/sda5        40435668    79505684    19535008+  83  Linux
/dev/sda6        79505748   156301487    38397870   83  Linux

Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x000b144c

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *          63   390620474   195310206   83  Linux
Partition 1 does not start on physical sector boundary.
/dev/sdb2       390620475   781240949   195310237+  83  Linux
Partition 2 does not start on physical sector boundary.
/dev/sdb3       957238128   976773167     9767520   82  Linux swap
/dev/sdb4       781240950   957238127    87998589   83  Linux
Partition 4 does not start on physical sector boundary.

Partition table entries are not in disk order

How does one get rid of Partition does not start on physical sector boundary?