LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Laptop and Netbook
User Name
Password
Linux - Laptop and Netbook Having a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).

Notices

Reply
 
LinkBack Search this Thread
Old 06-06-2007, 05:57 PM   #16
sulvereagle59
Member
 
Registered: May 2007
Location: Portland, Oregon
Distribution: Slackware 11
Posts: 42

Original Poster
Rep: Reputation: 15

Okay change in issues, I just noticed that each time I reboot that my external HD changes locations and that i possibly why I am having the difficulties that I am is there a way to make it so that my external HD basically stays at one address?

Last edited by sulvereagle59; 06-06-2007 at 06:33 PM.
 
Old 06-07-2007, 12:26 AM   #17
Nylex
LQ Addict
 
Registered: Jul 2003
Location: London, UK
Distribution: Slackware
Posts: 7,464

Rep: Reputation: Disabled
Quote:
Originally Posted by sulvereagle59
3) I have set up a log in other then root
now what my issue is is that
1) I am unable to access many of the folders when I am logged in as anything other then root.
Which directories are you trying to access? Those on your disk?

Quote:
2)I am unable to mount /E which is the second partition on my external Hd which is in fat32 format.
You mean you're not able to mount the device as your normal user?

Quote:
root@darkstar:~# mount /dev/sda2 /E -t vfat
mount: wrong fs type, bad option, bad superblock on /dev/sda2,
missing codepage or other error
(aren't you trying to mount an extended partition,
instead of some logical partition inside?)
In some cases useful info is found in syslog - try
dmesg | tail or so
Post the output from "fdisk /dev/sda" (or whatever the kernel's calling your device now).
I have been able to identify sda1 as the ntfs format of the external HD and sda2 as the fat32 format. I have no idea what the < sda5 > is though.

Quote:
Originally Posted by sulvereagle59
Okay change in issues, I just noticed that each time I reboot that my external HD changes locations and that i possibly why I am having the difficulties that I am is there a way to make it so that my external HD basically stays at one address?
I've replied to your problems above because I don't know if this post means you've fixed them. Yeah, this is the problem I described in an earlier post. You can use udev to get around this, but you'll need to use a 2.6 kernel. If you used the default kernel, you'll be using a 2.4 kernel. However, if you chose test26.s or huge26.s when you installed, you'll be using a 2.6. If you don't know, run "uname -r" to find out. Slackware provides packages for 2.6 kernels, so it won't be that hard to upgrade. We can help with setting up udev as well .
 
Old 06-07-2007, 01:33 AM   #18
sulvereagle59
Member
 
Registered: May 2007
Location: Portland, Oregon
Distribution: Slackware 11
Posts: 42

Original Poster
Rep: Reputation: 15
Ok, to answer you questions,

Quote:
Which directories are you trying to access? Those on your disk?
Due to me dual booting Windows Xp and Slackware 11 I am trying to set it up so that I can access my partition drive C:\ which is hda1 in linux and then of course my linux partition which is hda5. when I am logged in as david (which is my other log in other then root) it tells me that i do not have access.

Quote:
Post the output from "fdisk /dev/sda" (or whatever the kernel's calling your device now).
I have been able to identify sda1 as the ntfs format of the external HD and sda2 as the fat32 format. I have no idea what the < sda5 > is though.
Disk /dev/sde: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sde1 1 28930 232380193+ 7 HPFS/NTFS
/dev/sde2 28931 53993 201318547+ f W95 Ext'd (LBA)
/dev/sde5 28931 53993 201318516 b W95 FAT32

Quote:
I've replied to your problems above because I don't know if this post means you've fixed them. Yeah, this is the problem I described in an earlier post. You can use udev to get around this, but you'll need to use a 2.6 kernel. If you used the default kernel, you'll be using a 2.4 kernel. However, if you chose test26.s or huge26.s when you installed, you'll be using a 2.6. If you don't know, run "uname -r" to find out. Slackware provides packages for 2.6 kernels, so it won't be that hard to upgrade. We can help with setting up udev as well
I am using Kernel 2.4.33.3

in my slackware Cd's there are 2 what apperas to be kernals which one do i use, linux-2.6.17.13 or linux-smp-2.6.17.13? I have no idea or even how to go about doing it for that matter.
 
Old 06-07-2007, 02:09 AM   #19
Nylex
LQ Addict
 
Registered: Jul 2003
Location: London, UK
Distribution: Slackware
Posts: 7,464

Rep: Reputation: Disabled
I will reply to this later on today, as I don't have much time right now .
 
Old 06-07-2007, 11:53 PM   #20
Nylex
LQ Addict
 
Registered: Jul 2003
Location: London, UK
Distribution: Slackware
Posts: 7,464

Rep: Reputation: Disabled
You could put the "users" option in the 4th column of your fstab file to give your normal user access.

Quote:
Originally Posted by sulvereagle59
Disk /dev/sde: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sde1 1 28930 232380193+ 7 HPFS/NTFS
/dev/sde2 28931 53993 201318547+ f W95 Ext'd (LBA)
/dev/sde5 28931 53993 201318516 b W95 FAT32
Have you tried mounting /dev/sde5, rather than /dev/sde2?

Quote:
Originally Posted by sulvereagle59
in my slackware Cd's there are 2 what apperas to be kernals which one do i use, linux-2.6.17.13 or linux-smp-2.6.17.13? I have no idea or even how to go about doing it for that matter.
The SMP kernel is for machines with multiple processors. FYI, there's also the 2.6.18 kernel in /testing. There's nothing wrong with using 2.6.27.13 really, you'll be able to use udev. Whichever kernel you decide to use, you'll want to install all the kernel-*.tgz packages, but not the kernel headers package. Then, you'll want to make an initrd if necessary (see the file README.initrd) and add a new entry to your /etc/lilo.conf so you can boot with the new kernel (an example entry is given in README.initrd). Next, you'd try booting with said kernel and see if you have any problems with stuff. Then we can go on to helping you set up udev .
 
Old 06-08-2007, 12:30 AM   #21
sulvereagle59
Member
 
Registered: May 2007
Location: Portland, Oregon
Distribution: Slackware 11
Posts: 42

Original Poster
Rep: Reputation: 15
All right,

Now on updating the kernel, would I just go into the extra folder of my slackware cd's and install using KPackage or is there a better way of doing it? Next I was looking at the packages in the extra folder and in the kernel 2.6.17.13 folder there is the following items kernel generic,headers,modules, and source. Now if I am understanding you correctly I would install all but the headers, correct? If so is there an order in which I would do this in? Also, after doing the install would I need to do a Kernel compiling?
 
Old 06-08-2007, 12:47 AM   #22
Nylex
LQ Addict
 
Registered: Jul 2003
Location: London, UK
Distribution: Slackware
Posts: 7,464

Rep: Reputation: Disabled
Quote:
Originally Posted by sulvereagle59
All right,

Now on updating the kernel, would I just go into the extra folder of my slackware cd's and install using KPackage or is there a better way of doing it?
I've never used KPackage myself, but if you want to use it, that's up to you. You'll need to run it as root, though. You could just install the packages from the terminal using installpkg (again, you'll need to do this as root). If you're doing the latter, then change to the directory where the CD is mounted (using the "cd" command) and then run "installpkg kernel-generic*.tgz kernel-modules*.tgz kernel-source*.tgz" (the stars mean you don't have to type out the rest of the file name).

Next I was looking at the packages in the extra folder and in the kernel 2.6.17.13 folder there is the following items kernel generic,headers,modules, and source. Now if I am understanding you correctly I would install all but the headers, correct? If so is there an order in which I would do this in? Also, after doing the install would I need to do a Kernel compiling?[/QUOTE]

Yes, you are correct about not installing the headers. I don't think you need to worry about the order in which you install the packages. Also, no, you don't need to compile the kernel. The compiled image is in the kernel-generic package. Install the source just in case you need it later on.
 
Old 06-08-2007, 01:03 AM   #23
sulvereagle59
Member
 
Registered: May 2007
Location: Portland, Oregon
Distribution: Slackware 11
Posts: 42

Original Poster
Rep: Reputation: 15
Ok I have installed the new kernel now what do I need to do to change lilo to boot the new kernal? What exactly would I need to change?

Here is a copy of lilo as it is now:

Quote:
LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# Normal VGA console
vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Windows bootable partition config begins
other = /dev/hda1
label = Windows
table = /dev/hda
# Windows bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda5
label = Linux
read-only
# Linux bootable partition config ends
 
Old 06-08-2007, 01:38 AM   #24
sulvereagle59
Member
 
Registered: May 2007
Location: Portland, Oregon
Distribution: Slackware 11
Posts: 42

Original Poster
Rep: Reputation: 15
Ok some minor changes from my last post. First i thought I found what to change in lilo so my last post has my original lilo file and this was what I changed in it

Quote:
# Linux bootable partition config begins
image = /boot/vmlinuz-generic-2.6.17.13
initrd = /boot/initrd.gz
root = /dev/hda5
label = Lnx261713
read-only
# Linux bootable partition config ends
Then I rebooted my system and nothing changed i checked uname -r and still have 2.4.33.3
as my kernel so what did i do wrong?

this is what I have in my boot file

Quote:
file:///boot/initrd-tree
file:///boot/boot.0300
file:///boot/boot_message.txt
file:///boot/config
file:///boot/config-generic-2.6.17.13
file:///boot/config-ide-2.4.33.3
file:///boot/diag1.img
file:///boot/initrd.gz
file:///boot/map
file:///boot/README.initrd
file:///boot/System.map
file:///boot/System.map-generic-2.6.17.13
file:///boot/System.map-ide-2.4.33.3
file:///boot/vmlinuz
file:///boot/vmlinuz-generic-2.6.17.13
file:///boot/vmlinuz-ide-2.4.33.3
if there is any other information needed please let me know and I will try to get it to you.
 
Old 06-08-2007, 02:08 AM   #25
sulvereagle59
Member
 
Registered: May 2007
Location: Portland, Oregon
Distribution: Slackware 11
Posts: 42

Original Poster
Rep: Reputation: 15
Allright, there has been some additional changes since my last post just a few minutes ago. The changes are as follows
1) i figured out what it was that I was doing wrong and have since fixed the problem. ( while I did make the changes in lilo.config I did not type lilo on a command prompt since the changes I made did not take effect untill i did so.

2)I now have kernal 2.6.17.13 finally.

thus far everything that worked with the other kernel is working now so that is a very good thing.But, now I need to start working on udev.
 
Old 06-08-2007, 02:13 AM   #26
Nylex
LQ Addict
 
Registered: Jul 2003
Location: London, UK
Distribution: Slackware
Posts: 7,464

Rep: Reputation: Disabled
Indeed, I had forgotten you need to rerun lilo after making changes to your lilo.conf.. oops .

Do you have the udev package installed? To check, you can do "ls /var/log/packages | grep udev" in a terminal. To explain what this does: ls is for listing files and the | separating "ls /var/log/packages" and "grep udev" says to send the output of the thing on the left hand side to the thing on the right hand side. grep is used to print out lines containing a given string, in this case "udev". I prefer to explain what commands do usually, rather than just telling you to run them.
 
Old 06-08-2007, 02:20 AM   #27
sulvereagle59
Member
 
Registered: May 2007
Location: Portland, Oregon
Distribution: Slackware 11
Posts: 42

Original Poster
Rep: Reputation: 15
I actually appreciate the explainations it helps me learn what it is i am actually doing.

Yes I do have udev

Quote:
udev-097-i486-10
 
Old 06-08-2007, 02:32 AM   #28
Nylex
LQ Addict
 
Registered: Jul 2003
Location: London, UK
Distribution: Slackware
Posts: 7,464

Rep: Reputation: Disabled
You will need to write a rules file for udev that includes a rule for your external hard disk. There's a document called "Writing udev rules" which you should read and can find in /usr/doc/udev-0.97/. If you have problems understanding how to write a rule, post back here.
 
Old 06-08-2007, 03:57 AM   #29
sulvereagle59
Member
 
Registered: May 2007
Location: Portland, Oregon
Distribution: Slackware 11
Posts: 42

Original Poster
Rep: Reputation: 15
OK, I have read and kinda understand what I am doing. But, I do have some question.

1) ok according to the rules
Quote:
USB Hard Disk
A USB hard disk is comparable to the USB camera I described above, however typical usage patterns are different. In the camera example, I explained that I am not interested in the sdb node - it's only real use is for partitioning (e.g. with fdisk), but why would I want to partition my camera!?
Of course, if you have a 100GB USB hard disk, it is perfectly understandable that you might want to partition it, in which case we can take advantage of udev's string substitutions:
BUS=="usb", KERNEL=="sd*", SYSFS{product}=="USB 2.0 Storage Device", NAME="%k", SYMLINK+="usbhd%n"
This rule creates symlinks such as:
/dev/usbhd - The fdiskable node
/dev/usbhd1 - The first partition (mountable)
/dev/usbhd2 - The second partition (mountable)
now how and where do I get the SYSFS codes to be able to make the rule for my HD.

Now whaqt I have done thus far,
1) I have made a dir 10-local.rules
2) i have come up with what i think is a starting point of the rule for my HD

Quote:
BUS=="usb", KERNEL=="sd*", SYSFS {model}=="5000AAKS Externa", NAME=="My Book",SYMLINK+="usbhd%n"
Now if any of this is incorrect please let me know. Also could you let me know if I am even in the ballpark in understanding all this.

By the way I don't know if it is right or not but I got the information for my HD from dmesg which is
Quote:
Vendor: WD Model: 5000AAKS Externa Rev: 101a
Type: Direct-Access ANSI SCSI revision: 04
SCSI device sde: 976773168 512-byte hdwr sectors (500108 MB)
sde: Write Protect is off
sde: Mode Sense: 11 00 00 00
sde: assuming drive cache: write through
SCSI device sde: 976773168 512-byte hdwr sectors (500108 MB)
sde: Write Protect is off
sde: Mode Sense: 11 00 00 00
sde: assuming drive cache: write through
sde: sde1 sde2 < sde5 >

Last edited by sulvereagle59; 06-08-2007 at 04:08 AM.
 
Old 06-08-2007, 04:12 AM   #30
Nylex
LQ Addict
 
Registered: Jul 2003
Location: London, UK
Distribution: Slackware
Posts: 7,464

Rep: Reputation: Disabled
Look at the section titled "Finding information from sysfs" in the Writing udev rules document.

There are several things wrong with your rules. Firstly, you need to enclose things in double quotes as in the examples, e.g. KERNEL=="sd*". Also NAME isn't being used to match something, it's being used to define the NAME for the device, so you use 1 equals sign rather than two, e.g. NAME="foo". You might want to use SYMLINK instead, which leaves the kernel name intact, but creates a symbolic link (it's like a kind of shortcut) to the kernel named device node.
 
  


Reply

Tags
hd, mount


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Newbie seeking help with FTP cdawley4 Linux - Networking 2 07-28-2005 07:02 AM
A newbie is seeking for document about linux programing TruongAn Programming 4 02-21-2005 09:12 PM
newbie seeking help with initial mysql installation marvc Linux - Software 14 04-14-2003 07:05 PM
newbie seeking advice on properly configuring server marvc Linux - General 3 03-29-2003 03:45 PM
Real newbie seeking info for learning. DaDdY SnEb Linux - General 5 06-19-2002 04:58 PM


All times are GMT -5. The time now is 06:58 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration