Re: Where Did It Go? A Re-Post
by Mercury Morris
Mikkel wrote:
> What log messages do you get when you insert a disk in the drive
> after booting without one? Also, what does /proc/scsi/scsi list the
> drive as? From what you are reporting, it does not sounds like it is
> being detected as a removable hard drive.
There are no log messages when the disk is inserted. I agree that
the device is not being detected as a removable drive. And I would
go further by saying that the device is not detected at all, except
for the case when a disk is inserted BEFORE the system is booted.
Here are the lines from the command, cat /proc/scsi/scsi, basically
all blanks. The other scsi devices have vendor information included.
Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: Model: Rev:
Type: Direct-Access ANSI SCSI revision: 05
> I do not have an IDE ZIP drive handy to test with. On the USB ZIP
> drive, I get this after inserting a disk:
> Jul 31 17:44:47 asus kernel: sd 3:0:0:0: [sdb] Spinning up disk....ready
> Jul 31 17:44:47 asus kernel: sd 3:0:0:0: [sdb] 196608 512-byte
> hardware sectors (101 MB)
> Jul 31 17:44:47 asus kernel: sd 3:0:0:0: [sdb] Write Protect is off
> Jul 31 17:44:47 asus kernel: sd 3:0:0:0: [sdb] Assuming drive cache:
> write through
> Jul 31 17:44:47 asus kernel: sd 3:0:0:0: [sdb] 196608 512-byte
> hardware sectors (101 MB)
> Jul 31 17:44:47 asus kernel: sd 3:0:0:0: [sdb] Write Protect is off
> Jul 31 17:44:47 asus kernel: sd 3:0:0:0: [sdb] Assuming drive cache:
> write through
> Jul 31 17:44:47 asus kernel: sdb: sdb4
>
> I would expect something like that when a disk is inserted in an IDE
> ZIP drive as well. If not, you could try to re-scan the SCSI bus the
> ZIP drive is on. There is a script to do this at
> http://www.garloff.de/kurt/linux/rescan-scsi-bus.sh-1.25 but I have
> not had to use it. If you try it, let us know how it works. If it
> lets you mount the drive, it should give the developers the clues
> needed to fix the problem.
I ran the script that you pointed to (above). The output follows this
paragraph. I believe the lines for "scsi1" are the lines of interest.
The script was run twice, first with no disk in the drive, then after
a disk had been inserted. There was no difference between the two,
and the mount command failed, as well.
----- rescan-scsi-bus.sh output -----
[root@estreet ~]# ./rescan-scsi-bus.sh-1.25
Host adapter 0 (<NULL>) found.
Host adapter 1 (pata_amd) found.
Host adapter 2 (pata_amd) found.
Scanning SCSI subsystem for new devices
Scanning host 0 channels 0 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning for device 0 0 0 0 ...
OLD: Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: 3ware Model: Logical Disk 0 Rev: 1.2
Type: Direct-Access ANSI SCSI revision: -1
./rescan-scsi-bus.sh-1.25: line 262: return: : numeric argument required
Scanning for device 0 0 0 0 ...
OLD: Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: 3ware Model: Logical Disk 0 Rev: 1.2
Type: Direct-Access ANSI SCSI revision: -1
Scanning for device 0 0 1 0 ...
OLD: Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: 3ware Model: Logical Disk 1 Rev: 1.2
Type: Direct-Access ANSI SCSI revision: -1
./rescan-scsi-bus.sh-1.25: line 262: return: : numeric argument required
Scanning for device 0 0 1 0 ...
OLD: Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: 3ware Model: Logical Disk 1 Rev: 1.2
Type: Direct-Access ANSI SCSI revision: -1
Scanning for device 0 0 2 0 ...
OLD: Host: scsi0 Channel: 00 Id: 02 Lun: 00
Vendor: 3ware Model: Logical Disk 2 Rev: 1.2
Type: Direct-Access ANSI SCSI revision: -1
./rescan-scsi-bus.sh-1.25: line 262: return: : numeric argument required
Scanning for device 0 0 2 0 ...
OLD: Host: scsi0 Channel: 00 Id: 02 Lun: 00
Vendor: 3ware Model: Logical Disk 2 Rev: 1.2
Type: Direct-Access ANSI SCSI revision: -1
Scanning for device 0 0 3 0 ...
OLD: Host: scsi0 Channel: 00 Id: 03 Lun: 00
Vendor: 3ware Model: Logical Disk 3 Rev: 1.2
Type: Direct-Access ANSI SCSI revision: -1
./rescan-scsi-bus.sh-1.25: line 262: return: : numeric argument required
Scanning for device 0 0 3 0 ...
OLD: Host: scsi0 Channel: 00 Id: 03 Lun: 00
Vendor: 3ware Model: Logical Disk 3 Rev: 1.2
Type: Direct-Access ANSI SCSI revision: -1
Scanning host 1 channels 0 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning for device 1 0 0 0 ...
OLD: Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: Model: Rev:
Type: Direct-Access ANSI SCSI revision: 05
./rescan-scsi-bus.sh-1.25: line 262: return: : numeric argument required
Scanning for device 1 0 0 0 ...
OLD: Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: Model: Rev:
Type: Direct-Access ANSI SCSI revision: 05
Scanning host 2 channels 0 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning for device 2 0 0 0 ...
OLD: Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: SONY Model: DVD RW DRU-710A Rev: BY01
Type: CD-ROM ANSI SCSI revision: 05
./rescan-scsi-bus.sh-1.25: line 262: return: : numeric argument required
Scanning for device 2 0 0 0 ...
OLD: Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: SONY Model: DVD RW DRU-710A Rev: BY01
Type: CD-ROM ANSI SCSI revision: 05
0 new device(s) found.
0 device(s) removed.
I would like to submit all of this information to the developers.
As Andy suggested, I will go ahead and try to interest the folks
at Fedora's Bugzilla. I think it's a kernel problem, mostly because
I have been reading some of the kerneltrap traffic where one
discussion about the ide-scsi module might just indicate where
the trouble started. But, I don't particularly want to join the
kernel mailinglist, so I'll go the Bugzilla route.
Thanks, Mikkel, for taking an interest and pointing out the places
to look and the rescan-scsi-bus.sh script.
--
MM
16 years, 9 months
Re: Get message "Nothing to do" when yum installing kernel-2.6.22.1-33.fc7
by Antonio Olivares
----- Original Message ----
From: Tony Nelson <tonynelson(a)georgeanelson.com>
To: fedora-list(a)redhat.com
Sent: Wednesday, August 1, 2007 10:28:31 AM
Subject: Re: Get message "Nothing to do" when yum installing kernel-2.6.22.1-33.fc7
At 10:46 PM -0700 7/31/07, Antonio Olivares wrote:
>[root@localhost ~]# yum install kernel-2.6.22.1-33.fc7
>kernel-devel-2.6.22.1-33.fc7 kernel-headers-2.6.22.1-33.fc7 -y
>Loading "installonlyn" plugin
>Setting up Install Process
>Parsing package install arguments
>fedora 100% |=========================| 2.1 kB 00:00
>primary.sqlite.bz2 100% |=========================| 3.8 MB 13:16
>updates 100% |=========================| 1.9 kB 00:00
>primary.sqlite.bz2 100% |=========================| 1.1 MB 03:42
>Nothing to do
>
>Trying again as of right now, but this is strange.
When that happens, yum isn't specific enough about why. To find out, do a
"yum list whatever" to see if whatever is already installed or doesn't
exist in the repos.
--
____________________________________________________________________
TonyN.:' <mailto:tonynelson@georgeanelson.com>
' <http://www.georgeanelson.com/>
--
I have gotten it already on the two machines which run Fedora 7. However, I can only connect to the internet on only one of the machines with the -33 kernel :(.
[olivares@localhost ~]$ rpm -qa kernel
kernel-2.6.22.1-27.fc7
kernel-2.6.21-1.3194.fc7
kernel-2.6.22.1-33.fc7
kernel-2.6.21-1.3226.fc7
[olivares@localhost ~]$
Regards,
Antonio
____________________________________________________________________________________
Yahoo! oneSearch: Finally, mobile search
that gives answers, not web links.
http://mobile.yahoo.com/mobileweb/onesearch?refer=1ONXIC
16 years, 9 months
Flow control is off for TX ...
by Hongwei Li
Hi,
We had a problem with our FC6 system's network. Since today early morning,
the system hangs (I could not logon even locally) until I forced shut it
down and restarted.
The system information:
kernel -- 2.6.20-1.2952.fc6
one network card on a 100Mbs network line, pretty new pc.
The system log shows:
Aug 1 04:48:17 morpheus kernel: tg3: eth0: Link is down.
Aug 1 04:48:59 morpheus kernel: tg3: eth0: Link is up at 100 Mbps, full
duplex.
Aug 1 04:48:59 morpheus kernel: tg3: eth0: Flow control is off for TX and
off for RX.
... (repeat until I shut it down at around 8am)
I checked the earlier logs and found there was similar message on July 28,
but just one entry and at that time the system didn't hang -- seems
"recovered" to normal and so I didn't realize the problem.
Now, the system seems working normal. Below are some other information:
# netstat -in
Kernel Interface table
Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP
TX-OVR Flg
eth0 1500 0 12752 0 0 0 13363 0 0
0 BMRU
lo 16436 0 38734 0 0 0 38734 0 0
0 LRU
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:16:76:25:95:3F
inet addr:128.252.85.129 Bcast:128.252.85.255 Mask:255.255.255.0
inet6 addr: fe80::216:76ff:fe25:953f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:98052 errors:0 dropped:0 overruns:0 frame:0
TX packets:106395 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:29156234 (27.8 MiB) TX bytes:54961336 (52.4 MiB)
Interrupt:20
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:81565 errors:0 dropped:0 overruns:0 frame:0
TX packets:81565 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:60332142 (57.5 MiB) TX bytes:60332142 (57.5 MiB)
I installed packages that all from yum, nothing from other sources.
I can restart network service w/o any problem -- I can't repeat the above
error message myself.
Can somebody tell me what the above message mean? Hardware problem or
system problem? How to fix it?
Thanks for all help!
Hongwei Li
16 years, 9 months
Get message "Nothing to do" when yum installing kernel-2.6.22.1-33.fc7
by Antonio Olivares
[root@localhost ~]# yum install kernel-2.6.22.1-33.fc7 kernel-devel-2.6.22.1-33.fc7 kernel-headers-2.6.22.1-33.fc7 -y
Loading "installonlyn" plugin
Setting up Install Process
Parsing package install arguments
fedora 100% |=========================| 2.1 kB 00:00
primary.sqlite.bz2 100% |=========================| 3.8 MB 13:16
updates 100% |=========================| 1.9 kB 00:00
primary.sqlite.bz2 100% |=========================| 1.1 MB 03:42
Nothing to do
Trying again as of right now, but this is strange.
Regards,
Antonio
____________________________________________________________________________________
Yahoo! oneSearch: Finally, mobile search
that gives answers, not web links.
http://mobile.yahoo.com/mobileweb/onesearch?refer=1ONXIC
16 years, 9 months
Re: Re: New Kernel still bad
by Bob Staaf
>
> From: Claude Jones <cjones(a)levitjames.com>
> Date: 2007/08/01 Wed AM 08:53:58 EDT
> Replying to myself as I left out details: the NTFS mount problem referred to
> in that bugzilla is actually a Selinux issue. I've tried both the new Selinux
> policy referred to there AND the new kernel referred to by Vivek above, to
> resolve these mount problems. I'm sure they'll get fixed soon, though --
> that's been my general experience with Fedora, one of the principle reasons I
> stick with it.
>
Thanks, I was going to ask about this today. I got an alert from SELinux during last night's updates, apparently while ntfs was being updated.
16 years, 9 months
VMware Workstation 6 Audio Issue?
by Stanczak Group
I seem to be having trouble getting VMware to connect my audio. When
starting up windows it says "Failed to open sound device /dev/dsp:
Device or resource busy". Anyone having this problem? I put the alsa oss
plugin on, but still no help.
--
Justin Stanczak
Stanczak Group
812-735-3600
"All that is necessary for the triumph of evil is that good men do nothing."
Edmund Burke
16 years, 9 months
cpu speed problem
by fedora
Hi listers
here is a laptop with
[root@myhost ~]# cat /etc/fedora-release
Fedora release 7 (Moonshine)
[root@myhost ~]#
worked well until 10 days ago. then, the laptop started its fan, and
drove down its cpuspeed to about a quarter of the speed before. if i run
the system-monitor, the cpu is busy always about 30 %, whereas before it
was busy only about 6 %.
The fan from then on is never stopped and the CPU stays low in
performance from then on. i have to do a power down (either pm-hibernate
or halt/reboot) in order to make it come up with the "full" performance
and stay there for a while. after that, the fan starts again and the cpu
slows down.
after some googling i tried the following:
[root@myhost ~]# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
997500
[root@myhost ~]# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
731500
[root@myhost ~]# echo "997500"
>/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
[root@myhost ~]# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
997500
[root@myhost ~]#
i also changed the parameters of the cpuspeed program, so that now it
comes up with:
1413 ? Ss 0:01 cpuspeed -d -p 90 45 -m 731500 -M 997500 -n
all to no avail.
i also checked to see, whether in the BIOS the intelCPUstepping is
enabled, and it is enabled.
i understand, that the fan at a certain point in time starts turning.
but i don't understand, why at the same time, the cpu slows down.
has anyone got an idea, where this immediate change stems from and how i
could stop it?
thanks in advance for any reply
suomi
16 years, 9 months
Re: Where Did It Go? A Re-Post
by Mercury Morris
> How do you mean "fail to recognize the drive" when you are also saying
> you get a /dev/sdb1 created? That sounds like the drive is recognized fine.
On my system, I have four Western Digital SATA drives - /sda thru /sdd.
When the system boots with no disk in the drive, /dev/sde shows up and
all the code, except for sfdisk, sees it as a fifth SATA drive. That
is why I claim that the drive is not recognized, at least not correctly.
One other point that I didn't mention before: The only way to get the
/dev/sde4 created is to boot the system WITH a disk inside the ZIP drive.
That was not necessary with Fedora Core 6 and the 2.6.18 kernel(s).
The command, mknod /dev/sde4 b 8 68, does not create a valid device.
In order to get /dev/sde4 correctly created, there must be a ZIP disk
inside the ZIP drive before the system is booted.
Below, you can read what sfdisk has to say about the device, correcting
the error(s) generated by the kernel (kudzu or whatever). But when
an attempt is made to write to the ZIP drive, or even just print out
the partition table, hundreds of error messages show up in the system log.
I've included only very few of the system log messages, below.
---------- Some of the console output (commands and responses) ----------
[root@estreet ~]# ls -alt /dev/sde*
brw-r----- 1 root disk 8, 64 2007-07-28 14:23 /dev/sde
brw-r----- 1 root disk 8, 68 2007-07-28 14:23 /dev/sde4
[root@estreet ~]# sfdisk -l /dev/sde
Disk /dev/sde: 0 cylinders, 255 heads, 63 sectors/track
Warning: The partition table looks like it was made
for C/H/S=*/64/32 (instead of 0/255/63).
For this listing I'll assume that geometry.
Units = cylinders of 1048576 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sde1 0 - 0 0 0 Empty
/dev/sde2 0 - 0 0 0 Empty
/dev/sde3 0 - 0 0 0 Empty
/dev/sde4 * 0+ 95 96- 98288 6 FAT16
[root@estreet ~]# mount /dev/sde4 /mnt
mount: you must specify the filesystem type
[root@estreet ~]# mount -t vfat /dev/sde4 /mnt
mount: /dev/sde4: can't read superblock
---------- Some of the error messages from /var/log/messages ----------
Jul 28 15:02:23 estreet kernel: attempt to access beyond end of device
Jul 28 15:02:23 estreet kernel: sde: rw=0, want=196392, limit=1
Jul 28 15:02:23 estreet kernel: printk: 36 messages suppressed.
Jul 28 15:02:23 estreet kernel: Buffer I/O error on device sde4,
logical block 24544
Jul 28 15:02:23 estreet kernel: attempt to access beyond end of device
Jul 28 15:02:23 estreet kernel: sde: rw=0, want=196392, limit=1
Jul 28 15:02:23 estreet kernel: Buffer I/O error on device sde4,
logical block 24544
--
MM
16 years, 9 months
Re: Network manager - does no one care?
by William Murray
On Tue, 2007-07-31 at 21:23 -0400, fedora-list-request(a)redhat.com wrote:
> > networkmanager. So why is no one else screaming?
>
> Umm, 'cause it works for everyone else?
>
> Not really trying to be facetious, but it does work fine for me
> (Thinkpad T41, ipw2200). What's your wireless hardware?
>
> > Bill
> >
> >
> --
> Matthew Saltzman
Thanks for the replies. I guess I wait for the next kernel.
Its just rather frustrating in F7 that I have been hoping for the
ATI drivers (I know, I know, no one here's fault) and AFS, (where Atrpms
have had trouble with 2.6.22) and have
never had a working system. Now I get graphics and AFS but no network!
Thanks,
Bill
16 years, 9 months
KDE vs. gnome-mount
by Jonathan Ryshpan
Does KDE use gnome-mount to mount USB devices? If not, how does it
mount them?
Thanks - jon
16 years, 9 months