From: dwinters6@verizon.net
Moe Trin wrote:
> On Sat, 08 Jun 2013, in the Usenet newsgroup alt.os.linux.mandriva, in
> article , Its Dale wrote:
>
> I'm not sure what's going on with your KNode/4.4.9 as it isn't quoting
> (marking stuff you are replying to). I'll fix this post as if you
> were.
>
>>Moe Trin wrote:
>
>>> Well, we could start with "what version of Mandriva"?
>
>>what command do I enter to get that?
>
> Linux distributions have one (or more) file[s] in /etc/ named after
> the distribution with the characters "-release" or "-version" in the
> name. For Mandriva, it should be "/etc/mandriva-release". For
> distributions adhering to the Linux Standard Base, there should also
> be a "/etc/lsb-release" file, and there _may_ be a /etc/lsb-release.d/
> directory. Easy thing to do is to "cat /etc/*release" and that should
> tell you.
root@localhost ~]# cat /etc/*release
LSB_VERSION=lsb-4.0-ia32:lsb-4.0-noarch
DISTRIB_ID=MandrivaLinux
DISTRIB_RELEASE=2010.2
DISTRIB_CODENAME=Henry_Farman
DISTRIB_DESCRIPTION="Mandriva Linux 2010.2"
Mandriva Linux release 2010.2 (Official) for i586
Mandriva Linux release 2010.2 (Official) for i586
Mandriva Linux release 2010.2 (Official) for i586
Mandriva Linux release 2010.2 (Official) for i586
Mandriva Linux release 2010.2 (Official) for i586
[root@localhost ~]#
> Second method is to use the "lsb_release" command - such
> as "lsb_release -a". One other item that may be helpful to know is
> which Linux kernel are you using. For that,
>
> [fermi ~]$ uname -r
> 3.4.45-3.ia64
> [fermi ~]$
>
uname -r
2.6.33.7-desktop586-2mnb
>>>Don't know the drive, but a search engine suggests it's a USB device.
>>That being the case,
>
> Did I guess correctly here?
Yes its a curzer.
>
>>> run the command 'lsusb' to see what the system sees "now". The
>>> output might look something like
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0781:5530 SanDisk Corp.
Bus 001 Device 003: ID 03f0:9311 Hewlett-Packard
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>
>>> [euclid ~]$ lsusb
>>> Bus 002 Device 004: ID 046d:c05a Logitech, Inc.
>>> Bus 002 Device 002: ID 04f2:0841 Chicony Electronics Co., Ltd
>>> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>>> Bus 001 Device 002: ID 03f0:7711 Hewlett-Packard
>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> [euclid ~]$
>
>>[root@localhost bin]# lsusb
>>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>Bus 001 Device 002: ID 03f0:9311 Hewlett-Packard
>>Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>>[root@localhost bin]#
>
> OK - the only thing the kernel is seeing is an HP PhotoSmart printer.
> Wonder what (kernel) modules you have loaded. Try also
>
> [fermi ~]$ lsmod | grep -i usb
> usb_storage 82556 1
> usblp 10616 0
> [fermi ~]$
>
lsmod | grep -i usb
usb_storage 40375 0
usbcore 176684 4 usb_storage,ohci_hcd,ehci_hcd
scsi_mod 146881 5 sr_mod,sg,usb_storage,libata,sd_mod
> The "usb_storage" module is the "USB Mass Storage driver for Linux",
> while the "usblp" module is "USB Printer Device Class driver".
>
>>cat /etc/mtab
>>/dev/sda5 / ext4 rw 0 0
>>/dev/sda8 /back/drive ext4 rw,relatime,acl 0 0
>>/dev/sda7 /home ext4 rw 0 0
>
> There's the primary hard drive, but with 'lsusb' not seeing anything,
> there won't be anything here.
>
>>> Bus 001 Device 012: ID 0781:5153 SanDisk
>
>>did not see this
>
> Assuming you looked at the 'lsusb' output a second time, while the
> device is plugged in, that's the bad news. The kernel didn't see the
> drive, so nothing else is going to show up.
>
>>> The real clues should show up in /var/log/messages, where you may
>>> see some mention of a new device being found at the time you
>>> plugged it in. An example might be:
>
>>I didnt find any thing like that but Im not sure which
>>file I should be looking at.
>
> [fermi ~]$ ls /var/log/mess*
> /var/log/messages /var/log/messages-20130526
> /var/log/messages-20130512 /var/log/messages-20130602
> /var/log/messages-20130519
> [fermi ~]$
>
ls /var/log/mess*
/var/log/messages /var/log/messages.2.gz /var/log/messages.4.gz
/var/log/messages.1 /var/log/messages.3.gz
> This system runs continuously, and has the 'log-rotate' program
> rotating the logs Sunday at oh-dark-thirty. "/var/log/messages" is
> the "current" file, and the other files are from previous weeks.
> What you want to do is look at "/var/log/messages" shortly after you
> plugged in the device. I don't have a USB drive handy, but what I
> saw earlier on another system was:
[root@localhost ~]# ls /var/log/mess*
/var/log/messages /var/log/messages.2.gz /var/log/messages.4.gz
/var/log/messages.1 /var/log/messages.3.gz
[root@localhost ~]# ls /var/log/mess*
/var/log/messages /var/log/messages.2.gz /var/log/messages.4.gz
/var/log/messages.1 /var/log/messages.3.gz
[root@localhost ~]# /var/log/messages /var/log/messages.2.gz
/var/log/messages.4.gz
-bash: /var/log/messages: Permission denied
[root@localhost ~]# /var/log/messages.1 /var/log/messages.3.gzls
/var/log/mess*
-bash: /var/log/messages.1: Permission denied
[root@localhost ~]# /var/log/messages /var/log/messages.2.gz
/var/log/messages.4.gz
-bash: /var/log/messages: Permission denied
[root@localhost ~]# /var/log/messages.1 /var/log/messages.3.gz
-bash: /var/log/messages.1: Permission denied
[root@localhost ~]# [root@localhost ~]# /var/log/messages
/var/log/messages.2.gz /var/log/messages.4.gz
-bash: [root@localhost: command not found
[root@localhost ~]# -bash: /var/log/messages: Permission denied
-bash: -bash:: command not found
[root@localhost ~]# [root@localhost ~]# /va
>
>>> ---------------
>>> Dec 26 19:15:33 spica kernel: usb 1-8: new high speed USB device
>>> using ehci_hcd and address 12
>>> Dec 26 19:15:33 spica kernel: usb 1-8: New USB device found,
>>> idVendor=154b, idProduct=005b
>>> Dec 26 19:15:33 spica kernel: usb 1-8: New USB device strings:
>>> Mfr=1,Product=2, SerialNumber=3
>>> Dec 26 19:15:33 spica kernel: usb 1-8: Product: USB 2.0 FD
>>> Dec 26 19:15:33 spica kernel: usb 1-8: Manufacturer: PNY Technologies
>>> Dec 26 19:15:33 spica kernel: usb 1-8: SerialNumber: AA00000000002351
>
> and so on. If this kind of information doesn't appear, my only guess
> is that the kernel doesn't have the right module installed (the
> "usb_storage" item shown in the 'lsmod' output), or you've got a
[continued in next message]
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
