New Kernel still bad

[Karl Larsen]

	Yesterday I yummed the updates and they included removing the last 
updated kernel and installed a new one called 2.6.22.1-33.fc7
which I hoped is better than the one it replaced.

	So I stuck my trusty 2 GB USB storage device into a USB port and the 
Hard Drive moved but the firewire things just didn't do the normal 
things. I got no listing of the files on it and no symbol on my desktop 
that shows it is mounted. I will stay with the new kernel today and see 
if I can find other things that stopped working.


-- 

	Karl F. Larsen, AKA K5DI
	Linux User
	#450462   http://counter.li.org.

[Erich Zigler]

On Wed, 01 Aug 2007 05:30:22 -0600 Karl Larsen <k5di(a)zianet.com&gt; wrote:

>  	Yesterday I yummed the updates and they included removing the
>  last updated kernel and installed a new one called 2.6.22.1-33.fc7
>  which I hoped is better than the one it replaced.
>  	So I stuck my trusty 2 GB USB storage device into a USB port
>  and the Hard Drive moved but the firewire things just didn't do the
>  normal things. I got no listing of the files on it and no symbol on
>  my desktop that shows it is mounted. I will stay with the new kernel
>  today and see if I can find other things that stopped working. 
Karl,
 Is this device a USB device or a Firewire device? Also after plugging
in the device open up a terminal and execute the command

dmesg

What does the last 5-10 lines say?

Thanks,

Erich

[Karl Larsen]

Erich Zigler wrote:
>  On Wed, 01 Aug 2007 05:30:22 -0600 Karl Larsen
> <k5di(a)zianet.com&gt; wrote:
>  
> > 	Yesterday I yummed the updates and they included removing the
> > last updated kernel and installed a new one called 2.6.22.1-33.fc7
> > which I hoped is better than the one it replaced.
> > 	So I stuck my trusty 2 GB USB storage device into a USB port
> > and the Hard Drive moved but the firewire things just didn't do the
> > normal things. I got no listing of the files on it and no symbol on
> > my desktop that shows it is mounted. I will stay with the new kernel
> > today and see if I can find other things that stopped working.
>  
>  Karl,
>   Is this device a USB device or a Firewire device?  
	It was my guess that USB uses Firewire. I can be wrong. The device is a 
tiny sim in a plastic housing with a USB male plug.

Also after plugging
>  in the device open up a terminal and execute the command
>  
>  dmesg
>  
>  What does the last 5-10 lines say?
>  
>  Thanks,
>  
>  Erich
>   
Here is dmesg:

usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
scsi 3:0:0:0: Direct-Access     Kingston DataTraveler 2.0 PMAP PQ: 0 
ANSI: 0 CCS
sd 3:0:0:0: [sdg] 4030464 512-byte hardware sectors (2064 MB)
sd 3:0:0:0: [sdg] Write Protect is off
sd 3:0:0:0: [sdg] Mode Sense: 23 00 00 00
sd 3:0:0:0: [sdg] Assuming drive cache: write through
sd 3:0:0:0: [sdg] 4030464 512-byte hardware sectors (2064 MB)
sd 3:0:0:0: [sdg] Write Protect is off
sd 3:0:0:0: [sdg] Mode Sense: 23 00 00 00
sd 3:0:0:0: [sdg] Assuming drive cache: write through
  sdg: sdg1
sd 3:0:0:0: [sdg] Attached SCSI removable disk
sd 3:0:0:0: Attached scsi generic sg8 type 0
usb 4-6: USB disconnect, address 3
usb 4-6: new high speed USB device using ehci_hcd and address 4
usb 4-6: configuration #1 chosen from 1 choice
scsi4 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
scsi 4:0:0:0: Direct-Access     Kingston DataTraveler 2.0 PMAP PQ: 0 
ANSI: 0 CCS
sd 4:0:0:0: [sdg] 4030464 512-byte hardware sectors (2064 MB)
sd 4:0:0:0: [sdg] Write Protect is off
sd 4:0:0:0: [sdg] Mode Sense: 23 00 00 00
sd 4:0:0:0: [sdg] Assuming drive cache: write through
sd 4:0:0:0: [sdg] 4030464 512-byte hardware sectors (2064 MB)
sd 4:0:0:0: [sdg] Write Protect is off
sd 4:0:0:0: [sdg] Mode Sense: 23 00 00 00
sd 4:0:0:0: [sdg] Assuming drive cache: write through
  sdg: sdg1
sd 4:0:0:0: [sdg] Attached SCSI removable disk
sd 4:0:0:0: Attached scsi generic sg8 type 0
[karl@k5di ~]$



-- 

	Karl F. Larsen, AKA K5DI
	Linux User
	#450462   http://counter.li.org.

[Andy Green]

Somebody in the thread at some point said:

>      It was my guess that USB uses Firewire. I can be wrong. The
> device
>  is a tiny sim in a plastic housing with a USB male plug. 
Your guess was wrong: USB and firewire are two totally different
protocols.  They both do a similar job but they are incompatible, like
VHS and Beta were.  So you will be connecting either by USB or firewire,
in this case it is definitely USB because the dmesg has messages from
the usb-storage module.

>  sd 3:0:0:0: [sdg] Assuming drive cache: write through
>   sdg: sdg1 
It's actually ready to go... you should be able to mount it by hand as root

mount /dev/sdg1 /mnt

and access it at /mnt, to unmount it

umount /mnt

but clearly the magic that makes haldaemon or whatever it is that pops
up the "what do you want to do with your new drive" dialog is broken.

-Andy

[Chris]

On Wed, 01 Aug 2007 06:29:21 -0600
Karl Larsen <k5di(a)zianet.com&gt; wrote:

>  Erich Zigler wrote:
>  > On Wed, 01 Aug 2007 05:30:22 -0600 Karl Larsen <k5di(a)zianet.com&gt;
>  > wrote:
>  > 
>  >> 	Yesterday I yummed the updates and they included removing
>  >> the last updated kernel and installed a new one called
>  >> 2.6.22.1-33.fc7 which I hoped is better than the one it replaced.
>  >> 	So I stuck my trusty 2 GB USB storage device into a USB
>  >> port and the Hard Drive moved but the firewire things just didn't
>  >> do the normal things. I got no listing of the files on it and no
>  >> symbol on my desktop that shows it is mounted. I will stay with
>  >> the new kernel today and see if I can find other things that
>  >> stopped working. 
I am using the new kernel on a old Compaq nx9010 (duals w/XP) and my
like-new Sony at home. 

I never had the issues that Karl states (plugging in the USB drive and,
not have it auto-mount, not have it list the contense).

I too use F7 on each device - at this point, one must wonder what it is
that either Karl is doing wrong OR, what type/old is the hardware?

It's just odd (to me at least) that nearly-everything Karl seems to do
- fails.


-- 
Best regards,
Chris
Registerd Linux user number 448639

[Andy Green]

Somebody in the thread at some point said:

>  I never had the issues that Karl states (plugging in the USB drive
> and,
>  not have it auto-mount, not have it list the contense).
>  
>  I too use F7 on each device - at this point, one must wonder what it is
>  that either Karl is doing wrong OR, what type/old is the hardware?
>  
>  It's just odd (to me at least) that nearly-everything Karl seems to do
>  - fails. 
That doesn't seem to be a fair summary.  In Bugzilla for example

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=249161
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=249282

Plenty of folks are having the same problem.  It's not Karl's fault that
there are problems in the kernel right now.

BTW on that last bugzilla, they recommend trying udev-113-8.fc7 to fix
the problem: I was able to get this with

yum --enablerepo=updates-testing update udev

-Andy

[Aaron Konstam]

On Wed, 2007-08-01 at 14:40 +0100, Andy Green wrote:
>  Somebody in the thread at some point said:
>  
>  > I never had the issues that Karl states (plugging in the USB drive and,
>  > not have it auto-mount, not have it list the contense).
>  > 
>  > I too use F7 on each device - at this point, one must wonder what it is
>  > that either Karl is doing wrong OR, what type/old is the hardware?
>  > 
>  > It's just odd (to me at least) that nearly-everything Karl seems to do
>  > - fails.
>  
>  That doesn't seem to be a fair summary.  In Bugzilla for example
>  
>  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=249161
>  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=249282
>  
>  Plenty of folks are having the same problem.  It's not Karl's fault that
>  there are problems in the kernel right now.
>  
>  BTW on that last bugzilla, they recommend trying udev-113-8.fc7 to fix
>  the problem: I was able to get this with
>  
>  yum --enablerepo=updates-testing update udev
>  
>  -Andy 
Confusion reigns. Both the bugzillas above are about kernel-2.6.22-27
and Karl is complaining about kernel-2.6.22-42.

My memory stick automounts on the latter so there must be a presumption
that the problem lies in the hardware used assuming no odd software
installations of udev are involved. 

It is hard to believe that sticking the memory stick into the port could
be done incorrectly, but who knows.
-- 
Aaron Konstam <akonstam(a)sbcglobal.net&gt;

[Karl Larsen]

Aaron Konstam wrote:
>  On Wed, 2007-08-01 at 14:40 +0100, Andy Green wrote:
> > Somebody in the thread at some point said:
> >
> >> I never had the issues that Karl states (plugging in the USB drive and,
> >> not have it auto-mount, not have it list the contense).
> >>
> >> I too use F7 on each device - at this point, one must wonder what it is
> >> that either Karl is doing wrong OR, what type/old is the hardware?
> >>
> >> It's just odd (to me at least) that nearly-everything Karl seems to do
> >> - fails.
> > That doesn't seem to be a fair summary.  In Bugzilla for example
> >
> > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=249161
> > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=249282
> >
> > Plenty of folks are having the same problem.  It's not Karl's fault that
> > there are problems in the kernel right now.
> >
> > BTW on that last bugzilla, they recommend trying udev-113-8.fc7 to fix
> > the problem: I was able to get this with
> >
> > yum --enablerepo=updates-testing update udev
> >
> > -Andy
>  Confusion reigns. Both the bugzillas above are about kernel-2.6.22-27
>  and Karl is complaining about kernel-2.6.22-42.
>  
>  My memory stick automounts on the latter so there must be a presumption
>  that the problem lies in the hardware used assuming no odd software
>  installations of udev are involved. 
>  
>  It is hard to believe that sticking the memory stick into the port could
>  be done incorrectly, but who knows. 
	I am mad that some think I am so STUPID that for 6 months I have used 
my memory stick with the old kernel, and stuck it in wrong when I first 
used the new kernel. Jeeze you IDIOTS! Grow up.

	What I was going to do is explain what happened this morning. I got not 
the 44 but the 41 kernel when I tried to get the 44. I guess yum  could 
not find the 44 and did the best it could. So I rebooted to the 41 
kernel and sure enough it will not work with a USB device. But I tried a 
  memory stick that you plug into the proper slot and it worked perfect!

	So what I have is a cheap thing about the size of a floppy drive at the 
front panel which plugs into one of the two USB things on the mother 
board. It has 5 slots for various memeory sticks from camera and cell 
phone and other things. With this kernel (41) the 5 slots work but the 
one USB on this devise does not work.

	I am sure there is something not quite right with my computer. But for 
sure with the old kernel it DID WORK.


-- 

	Karl F. Larsen, AKA K5DI
	Linux User
	#450462   http://counter.li.org.

[Andy Green]

Somebody in the thread at some point said:

>      I am sure there is something not quite right with my computer.
> But
>  for sure with the old kernel it DID WORK. 
The problem seems to have been tracked down in the meanwhile --
apparently it is not the kernel at fault but udev.  Update udev like this:

yum --enablerepo=updates-testing update udev

and see if that resolves the problem for you.

-Andy

[Chris]

On Wed, 01 Aug 2007 12:39:55 -0600
Karl Larsen <k5di(a)zianet.com&gt; wrote:

**** Snip to get to meaningful section ***

>  	So what I have is a cheap thing about the size of a floppy
>  drive at the front panel which plugs into one of the two USB things
>  on the mother board. It has 5 slots for various memeory sticks from
>  camera and cell phone and other things. With this kernel (41) the 5
>  slots work but the one USB on this devise does not work.
>  
>  	I am sure there is something not quite right with my
>  computer. But for sure with the old kernel it DID WORK.
>  
>   
So - what you really have is an external universal media reader.
Is that type of device covered within the supported hardware?

Fortunately for me, Sony has it's universal media reader built in (not
sure if that matters).

And in my case, it works perfectly however, my uni-media reader does
not read flash drives, only media from things like digital cameras.

-- 
Best regards,
Chris
Registerd Linux user number 448639

[Andy Green]

Somebody in the thread at some point said:

> > 	So what I have is a cheap thing about the size of a floppy
> > drive at the front panel which plugs into one of the two USB things
> > on the mother board. It has 5 slots for various memeory sticks from
> > camera and cell phone and other things. With this kernel (41) the 5
> > slots work but the one USB on this devise does not work. 
>  So - what you really have is an external universal media reader.
>  Is that type of device covered within the supported hardware? 
I have seen boxes with a 5 1/4" bay set of flash media sockets *and* a
usb socket on the same panel.

Earlier in the thread he mentioned he gets his device recognized by
usb-storage and allocated a device node /dev/sdg1, so there is no
fundamental problem.  It makes perfect sense it's an issue local to udev.

-Andy

[Karl Larsen]

Andy Green wrote:
>  Somebody in the thread at some point said:
>  
> >> 	So what I have is a cheap thing about the size of a floppy
> >> drive at the front panel which plugs into one of the two USB things
> >> on the mother board. It has 5 slots for various memeory sticks from
> >> camera and cell phone and other things. With this kernel (41) the 5
> >> slots work but the one USB on this devise does not work.
>  
> > So - what you really have is an external universal media reader.
> > Is that type of device covered within the supported hardware?
>  
>  I have seen boxes with a 5 1/4" bay set of flash media sockets *and* a
>  usb socket on the same panel.
>  
>  Earlier in the thread he mentioned he gets his device recognized by
>  usb-storage and allocated a device node /dev/sdg1, so there is no
>  fundamental problem.  It makes perfect sense it's an issue local to udev.
>  
>  -Andy
>   
	Also I just tested and Skype will not work using either the 33 or 41 
kernels. I am trying to get back to the old kernel now!

-- 

	Karl F. Larsen, AKA K5DI
	Linux User
	#450462   http://counter.li.org.

[Rogue]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Karl Larsen wrote:
>  Andy Green wrote:
>      Also I just tested and Skype will not work using either the 33 or 41
>  kernels. I am trying to get back to the old kernel now!
>   
Skype's working fine for me.

Skype 1.4.0.74
Kernel 2.6.22.1-41.fc7

- -Rogue
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (GNU/Linux)
>
> iD8DBQFGsPiNceS9IQvx51YRAs6oAJsHYLnoO9ibQ0rHY24pAj06/2cYtwCgkMRn
> apI2BIF00MCjGH/iNEOmvOw=
> =kNy2
> -----END PGP SIGNATURE-----

[Cameron Simpson]

On 01Aug2007 14:50, Karl Larsen <k5di(a)zianet.com&gt; wrote:
>  I am trying to get back to the old kernel now! 
Karl,

Also have a look at the file:

  /etc/yum/pluginconf.d/installonlyn.conf

Mine says:

  [main]
  enabled=1
  # this sets the number of package versions which are kept
  tokeep=4

which causes yum to keep 4 installed kernels around. You may want to wind
this up to 10 or something. That way you will be more likely to
have the older working kernel still installed after an upgrade.
-- 
Cameron Simpson <cs(a)zip.com.au&gt; DoD#743
http://www.cskk.ezoshosting.com/cs/

This morning I was writing an article containing some Perl.  My daughter Heidi
wandered in and said, "What is that gobbledygook?  It looks like swearing."

Out of the mouths of babes...    - Larry Wall, lwall(a)netlabs.com

[Todd Zullinger]

Cameron Simpson wrote:
>  Also have a look at the file:
>  
>   /etc/yum/pluginconf.d/installonlyn.conf
>  
>  Mine says:
>  
>   [main]
>   enabled=1
>   # this sets the number of package versions which are kept
>   tokeep=4
>  
>  which causes yum to keep 4 installed kernels around. You may want to
>  wind this up to 10 or something. That way you will be more likely to
>  have the older working kernel still installed after an upgrade. 
It's probably worth noting that with the update to yum-3.2.2, the
installonlyn plugin's functionality was merged into yum's core.  The
way to control things with 3.2.2 and later is via installonly_limit in
yum.conf.

The yum.conf manpage states that this option defaults to 0, which
disables the feature.  However, the yum rpm applies a patch that sets
the default to 2 AFAICT.

This change (and the discrepancy in the docs) is sure to bite some
folks.  This was reported in https://bugzilla.redhat.com/249396 .

-- 
Todd        OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
That men do not learn very much from the lessons of history is the
most important of all the lessons of history.
    -- Aldous Huxley Collected Essays, 1959

[Todd Zullinger]

>  This change (and the discrepancy in the docs) is sure to bite some
>  folks.  This was reported in https://bugzilla.redhat.com/249396 . 
FWIW, I submitted a patch to update the manpage and it was added to
CVS before my post even made it back to me.  3 minutes from submission
to inclusion, that's pretty damn quick! :)

-- 
Todd        OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Rome did not create a great empire by having meetings, they did it by
killing all those who opposed them.

[Timothy Murphy]

Todd Zullinger wrote:

>  It's probably worth noting that with the update to yum-3.2.2,
> the
>  installonlyn plugin's functionality was merged into yum's core.  The
>  way to control things with 3.2.2 and later is via installonly_limit in
>  yum.conf. 
1. Does this mean that the installonly plugin will not have any effect
with yum >= 3.2.2 ?

2. Does this feature only affect kernel RPMs?
If so, it isn't at all obvious from the name.

-- 
Timothy Murphy  
e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie
tel: [phone]
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland

[Todd Zullinger]

Timothy Murphy wrote:
>  Todd Zullinger wrote:
>  
> > It's probably worth noting that with the update to yum-3.2.2, the
> > installonlyn plugin's functionality was merged into yum's core.
> > The way to control things with 3.2.2 and later is via
> > installonly_limit in yum.conf.
>  
>  1. Does this mean that the installonly plugin will not have any
>  effect with yum>= 3.2.2 ? 
Correct.  The plugin's functionality was merged into yum.  All that's
really changed is where you configure it.  Instead of editing
/etc/yum/pluginconf.d/installonlyn.conf, you now edit /etc/yum.conf
and set the installonly_limit variable (adding it if need be).

>  2. Does this feature only affect kernel RPMs?  If so, it isn't
> at
>  all obvious from the name. 
By default, yes.  The option (like the plugin before it) controls how
many of each "installonlypkgs" are installed at one time.  So it is
possible to add things other than kernel packages to installonlypkgs
(though many packages won't work when trying to install multiple
versions of them AFAIK).

The default list of installonlypkgs is:

kernel, kernel-bigmem, kernel-debug, kernel-devel, kernel-enterprise,
kernel-modules, kernel-smp, kernel-source, kernel-unsupported

(Once again, the man page isn't quite in sync with the code, and it
says the default lists is: kernel, kernel-bigmem, kernel-debug,
kernel-enterprise, kernel-smp, kernel-unsupported.  It's too early for
patches and bugzilla, but if I remember later, I'll see about sending
an update to the yum manpage to the yum folks.)

-- 
Todd        OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If you're not confused, you're not paying attention

[Timothy Murphy]

Todd Zullinger wrote:

> > 1. Does this mean that the installonly plugin will not have any
> > effect with yum>= 3.2.2 ?
>  
>  Correct.  The plugin's functionality was merged into yum.  All that's
>  really changed is where you configure it.  Instead of editing
>  /etc/yum/pluginconf.d/installonlyn.conf, you now edit /etc/yum.conf
>  and set the installonly_limit variable (adding it if need be). 
Thanks. I've added

installonly_limit=4

to my /etc/yum.conf , in anticipation of yum-3.2.2 .

-- 
Timothy Murphy  
e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie
tel: [phone]
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland

[Chris Jones]

>  which causes yum to keep 4 installed kernels around. You may want to
> wind
>  this up to 10 or something. That way you will be more likely to
>  have the older working kernel still installed after an upgrade. 
Before you set this to a higher value, which is generally a good idea, 
you should first check how large your /boot partition is and work out 
how many you have space for. If /boot is just a directory in / then OK, 
but often /boot is a small partition on its own, and thus will only be 
able to accommodate a certain number of kernels...

Chris

[Mikkel]

Chris Jones wrote:
>  
> > which causes yum to keep 4 installed kernels around. You may want to wind
> > this up to 10 or something. That way you will be more likely to
> > have the older working kernel still installed after an upgrade.
>  
>  Before you set this to a higher value, which is generally a good idea,
>  you should first check how large your /boot partition is and work out
>  how many you have space for. If /boot is just a directory in / then OK,
>  but often /boot is a small partition on its own, and thus will only be
>  able to accommodate a certain number of kernels...
>  
>  Chris
>  
The installer gives you a warning if you make /boot smaller then
75M, and grub itself uses 220K, so this should not be a problem for
most users. If you figure 6M for each kernel, initial RAM disk, and
system map, you should have room for at least 12 kernels. (6M allows
for a larger then normal initrd file.)

Mikkel
-- 

  Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!

[Chris Jones]

>  The installer gives you a warning if you make /boot smaller then
>  75M, and grub itself uses 220K, so this should not be a problem for
>  most users. If you figure 6M for each kernel, initial RAM disk, and
>  system map, you should have room for at least 12 kernels. (6M allows
>  for a larger then normal initrd file.) 
Thanks for the info, I wasn't aware of that. I tend to play around with a few 
kernels, so always manually setup my partitions and make /boot fairly large.

I guess though its not fool proof since not everyone uses the installer (you 
can update via yum) and also some might have partitions left over from old 
installs where smaller boot partitions were OK.

Chris

[Timothy Murphy]

Karl Larsen wrote:

>  So I rebooted to the 41
>  kernel and sure enough it will not work with a USB device. 
When you say it doesn't work,
do you mean that it is not automatically mounted,
or that it doesn't appear at all, eg as /dev/sdb ?


-- 
Timothy Murphy  
e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie
tel: [phone]
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland

[Karl Larsen]

Timothy Murphy wrote:
>  Karl Larsen wrote:
>  
> > So I rebooted to the 41
> > kernel and sure enough it will not work with a USB device.
>  
>  When you say it doesn't work,
>  do you mean that it is not automatically mounted,
>  or that it doesn't appear at all, eg as /dev/sdb ?
>  
>   
	It doesn't appear and if you do ls on /media/ there is nothing there 
either. It just does nothing.


-- 

	Karl F. Larsen, AKA K5DI
	Linux User
	#450462   http://counter.li.org.

[Timothy Murphy]

Karl Larsen wrote:

> > When you say it doesn't work,
> > do you mean that it is not automatically mounted,
> > or that it doesn't appear at all, eg as /dev/sdb ?
> >  
>  It doesn't appear and if you do ls on /media/ there is nothing there
>  either. It just does nothing. 
You didn't really answer my question.

In my case, my memory stick is not automatically mounted,
as it was with earlier kernels;
but I can mount it myself with "mount /dev/sdb /mnt" (or whatever).
Then I can use it as before.

-- 
Timothy Murphy  
e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie
tel: [phone]
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland

[Vivek J. Patankar]

Chris wrote:
>  I am using the new kernel on a old Compaq nx9010 (duals w/XP) and my
>  like-new Sony at home. 
>  I never had the issues that Karl states (plugging in the USB drive and,
>  not have it auto-mount, not have it list the contense). 
I've never had the problem, but that doesn't mean that it doesn't 
happen. And Karl is not the only one who's facing the problem. There are 
quite a few.

-- 
Regards,
विवेक ज. पाटणकर (Vivek J. Patankar)

Registered Linux User #374218
Fedora release 7 (Moonshine)
Linux 2.6.22.1-33.fc7 x86_64
My USB drives automount! :p

[Bob Goodwin]

Vivek J. Patankar wrote:
>  Chris wrote:
> > I am using the new kernel on a old Compaq nx9010 (duals w/XP) and my
> > like-new Sony at home. I never had the issues that Karl states 
> > (plugging in the USB drive and,
> > not have it auto-mount, not have it list the contense).
>
>  I've never had the problem, but that doesn't mean that it doesn't 
>  happen. And Karl is not the only one who's facing the problem. There 
>  are quite a few.
>  
I still have a problem that the icon does not appear on the desktop.  I 
see the LED blink on the memory stick but it will not mount unless I 
have an entry in fstab.  Then I can access it from the command line. I 
tried commenting out the /mnt/flash line in fstab but it did not help.

uname -a
Linux box6 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686 i686 
i386 GNU/Linux

df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
                      74529904   5414416  65268528   8% /
/dev/sdb1               101086     18677     77190  20% /boot
tmpfs                   256868         0    256868   0% /dev/shm
/dev/sdc1              4022580    851316   3171264  22% /mnt/flash

It did show up on the desktop automatically until the last three kernel 
updates but I'm not sure that something else was not updated also that 
causes the "problem?"

Bob Goodwin

[Rahul Sundaram]

Bob Goodwin wrote:
>  Vivek J. Patankar wrote:
> > Chris wrote:
> >> I am using the new kernel on a old Compaq nx9010 (duals w/XP) and my
> >> like-new Sony at home. I never had the issues that Karl states 
> >> (plugging in the USB drive and,
> >> not have it auto-mount, not have it list the contense).
> >
> > I've never had the problem, but that doesn't mean that it doesn't 
> > happen. And Karl is not the only one who's facing the problem. There 
> > are quite a few.
> >
>  I still have a problem that the icon does not appear on the desktop.  I 
>  see the LED blink on the memory stick but it will not mount unless I 
>  have an entry in fstab.  
Get the latest udev update in updates-testing repository which will 
resolve this issue. It is not a kernel problem.

Rahul

[Ashley Pritchard]

updating udev to udev-113.8.fc7 resolves the problem. I found it here:
http://koji.fedoraproject.org/koji/builds?prefix=u&order=-completion_...

On 8/1/07, Rahul Sundaram <sundaram(a)fedoraproject.org&gt; wrote:
>  Bob Goodwin wrote:
>  > Vivek J. Patankar wrote:
>  >> Chris wrote:
>  >>> I am using the new kernel on a old Compaq nx9010 (duals w/XP) and my
>  >>> like-new Sony at home. I never had the issues that Karl states
>  >>> (plugging in the USB drive and,
>  >>> not have it auto-mount, not have it list the contense).
>  >>
>  >> I've never had the problem, but that doesn't mean that it doesn't
>  >> happen. And Karl is not the only one who's facing the problem. There
>  >> are quite a few.
>  >>
>  > I still have a problem that the icon does not appear on the desktop.  I
>  > see the LED blink on the memory stick but it will not mount unless I
>  > have an entry in fstab.
>
>  Get the latest udev update in updates-testing repository which will
>  resolve this issue. It is not a kernel problem.
>
>  Rahul
>
>  --
>  fedora-list mailing list
>  fedora-list(a)redhat.com
>  To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>  


-- 
Diolch yn fawr, Ashley

[Rahul Sundaram]

Ashley Pritchard wrote:
>  updating udev to udev-113.8.fc7 resolves the problem. I found it
> here:
>
> http://koji.fedoraproject.org/koji/builds?prefix=u&order=-completion_...
>
>
> <http://koji.fedoraproject.org/koji/builds?prefix=u&order=-completion_...
>   
You can simple run

# yum install udev --enablerepo=updates-testing

Rahul

[Bob Goodwin]

Rahul Sundaram wrote:
>  Ashley Pritchard wrote:
> > updating udev to udev-113.8.fc7 resolves the problem. I found it here:
> >
> http://koji.fedoraproject.org/koji/builds?prefix=u&order=-completion_...
>
> >
> <http://koji.fedoraproject.org/koji/builds?prefix=u&order=-completion_...
>
> >
> >
>
>  You can simple run
>
>  # yum install udev --enablerepo=updates-testing
>
>  Rahul
>  
Yes, I did as you suggest, commented out the /dev/sdc1 line in fstab, 
and normal operation is restored.  Plugging in the flash memory stick 
puts an icon on the desktop again.

I guess that demonstrates that it is not a kernel problem ...

Thanks.

Bob Goodwin

[Claude Jones]

On Wednesday August 1 2007 11:21:52 am Rahul Sundaram wrote:
>  Get the latest udev update in updates-testing repository which
>  will resolve this issue. It is not a kernel problem.
>
>  Rahul 
Just tried that, and you're right, fixed my pen drive mounting 
problem -- NTFS mount is still broken

-- 
Claude Jones
Brunswick, MD, USA

[Rahul Sundaram]

Claude Jones wrote:
>  On Wednesday August 1 2007 11:21:52 am Rahul Sundaram wrote:
> > Get the latest udev update in updates-testing repository which
> > will resolve this issue. It is not a kernel problem.
> >
> > Rahul
>  
>  Just tried that, and you're right, fixed my pen drive mounting 
>  problem -- NTFS mount is still broken 
This is a SELinux policy issue.

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=249943

It isn't clear yet whether the latest update in updates-testing will 
resolve this issue. Please test and provide feedback in the bugzilla report.

Rahul

[Claude Jones]

On Wednesday August 1 2007 2:51:00 pm Rahul Sundaram wrote:
>  This is a SELinux policy issue.
>
>  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=249943
>
>  It isn't clear yet whether the latest update in
>  updates-testing will resolve this issue. Please test and
>  provide feedback in the bugzilla report. 
Already did, some hours ago

-- 
Claude Jones
Brunswick, MD, USA

[Erich Zigler]

On Wed, August 1, 2007 7:29 am, Karl Larsen wrote:

>  	It was my guess that USB uses Firewire. I can be wrong. The device
> is a
>  tiny sim in a plastic housing with a USB male plug. 
Nope. USB and Firewire are two different devices types. If it was a
firewire device it would be plugged in to a Firewire card on your
computer.

>  Here is dmesg:
>  usb-storage: device found at 3
>  usb-storage: waiting for device to settle before scanning
>  usb-storage: device scan complete
>  scsi 3:0:0:0: Direct-Access     Kingston DataTraveler 2.0 PMAP PQ: 0
>  ANSI: 0 CCS
>  sd 3:0:0:0: [sdg] 4030464 512-byte hardware sectors (2064 MB)
>  sd 3:0:0:0: [sdg] Write Protect is off
>  sd 3:0:0:0: [sdg] Mode Sense: 23 00 00 00
>  sd 3:0:0:0: [sdg] Assuming drive cache: write through
>  sd 3:0:0:0: [sdg] 4030464 512-byte hardware sectors (2064 MB)
>  sd 3:0:0:0: [sdg] Write Protect is off
>  sd 3:0:0:0: [sdg] Mode Sense: 23 00 00 00
>  sd 3:0:0:0: [sdg] Assuming drive cache: write through
>    sdg: sdg1
>  sd 3:0:0:0: [sdg] Attached SCSI removable disk
>  sd 3:0:0:0: Attached scsi generic sg8 type 0
>  usb 4-6: USB disconnect, address 3
>  usb 4-6: new high speed USB device using ehci_hcd and address 4
>  usb 4-6: configuration #1 chosen from 1 choice
>  scsi4 : SCSI emulation for USB Mass Storage devices
>  usb-storage: device found at 4
>  usb-storage: waiting for device to settle before scanning
>  usb-storage: device scan complete
>  scsi 4:0:0:0: Direct-Access     Kingston DataTraveler 2.0 PMAP PQ: 0
>  ANSI: 0 CCS
>  sd 4:0:0:0: [sdg] 4030464 512-byte hardware sectors (2064 MB)
>  sd 4:0:0:0: [sdg] Write Protect is off
>  sd 4:0:0:0: [sdg] Mode Sense: 23 00 00 00
>  sd 4:0:0:0: [sdg] Assuming drive cache: write through
>  sd 4:0:0:0: [sdg] 4030464 512-byte hardware sectors (2064 MB)
>  sd 4:0:0:0: [sdg] Write Protect is off
>  sd 4:0:0:0: [sdg] Mode Sense: 23 00 00 00
>  sd 4:0:0:0: [sdg] Assuming drive cache: write through
>    sdg: sdg1
>  sd 4:0:0:0: [sdg] Attached SCSI removable disk
>  sd 4:0:0:0: Attached scsi generic sg8 type 0
>  [karl@k5di ~]$ 
Well the kernel is seeing the device. It seems others are seeing this same
behavior with their devices. I would fill out a bugzilla report.

Thanks,

Erich

[Vivek J. Patankar]

Karl Larsen wrote:
>      Yesterday I yummed the updates and they included removing the
> last 
>  updated kernel and installed a new one called 2.6.22.1-33.fc7
>  which I hoped is better than the one it replaced. 
There is a newer (2.6.22.1-41.fc7) kernel available. You might want to 
try that.

-- 
Regards,
विवेक ज. पाटणकर (Vivek J. Patankar)

Registered Linux User #374218
Fedora release 7 (Moonshine)
Linux 2.6.22.1-33.fc7 x86_64
My USB drives automount! :p

[Andy Green]

Somebody in the thread at some point said:

>  Karl Larsen wrote:
> >     Yesterday I yummed the updates and they included removing the last
> > updated kernel and installed a new one called 2.6.22.1-33.fc7
> > which I hoped is better than the one it replaced.
>  
>  There is a newer (2.6.22.1-41.fc7) kernel available. You might want to
>  try that. 
According to a guy in fedora-devel, the -41 kernel is expected to clean
up several bad things that have been seen with some boxes on the last
few kernels, so it's definitely worth a go.

-Andy

[Claude Jones]

On Wed August 1 2007, Vivek J. Patankar wrote:
>  There is a newer (2.6.22.1-41.fc7) kernel available. You might want
> to
>  try that. 
I've tried it. It still produces errors when trying to mount my NTFS drives. 
I've already added to the existing bugzilla
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=249943

And just now, I've tried my USB stick, and after flashing for a few moments, 
it too failed to mount. Manual mount still works. 

-- 
Claude Jones
Brunswick, MD, USA

[Claude Jones]

On Wed August 1 2007, Claude Jones wrote:
>  On Wed August 1 2007, Vivek J. Patankar wrote:
>  > There is a newer (2.6.22.1-41.fc7) kernel available. You might want to
>  > try that.
>
>  I've tried it. It still produces errors when trying to mount my NTFS
>  drives. I've already added to the existing bugzilla
>  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=249943
>
>  And just now, I've tried my USB stick, and after flashing for a few
>  moments, it too failed to mount. Manual mount still works. 
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. 

-- 
Claude Jones
Brunswick, MD, USA

[Rui Miguel Silva Seabra]

On Wed, Aug 01, 2007 at 05:30:22AM -0600, Karl Larsen wrote:
>  	Yesterday I yummed the updates and they included removing the last 
>  updated kernel and installed a new one called 2.6.22.1-33.fc7
>  which I hoped is better than the one it replaced. 
I have problems with USB disks on a Pentium 4 Mobile laptop.
It's ok in another x86_64, AMD Turion2

I have problems when removing my ralink (rt2x00pci) pcmcia card on both
machines general instability, downwards spiral.

It's actually advisable to poweroff almost immediately just be sure.

Rui

-- 
This statement is false.
Today is Prickle-Prickle, the 68th day of Confusion in the YOLD 3173
+ No matter how much you do, you never do enough -- unknown
+ Whatever you do will be insignificant,
| but it is very important that you do it -- Gandhi
+ So let's do it...?