-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Bonjour,
I can see people getting problems when they update their kernel: one cannot get his preceding resolution on his monitor, another one has no more printer....
I posted some messages about new problems after updating my kernel....
NO ANSWER!
I post again, in hope... before switching to another distro...
USB:
At the early beginning of kernel boot, I can read this message:
USB 3-1 device descriptor read/64 error -71 (repeated four times) USB 3-1 device not accepting address 5 error -71
and... my scanner no longer works....
LVM: When I installed fc6, I used lvm and no problem occured with the first kernel.
When I updated the kernel (I'm now using the last one), I got this message at the early beginning of boot up:
volume with uuid P3thCb-...... (long sequence of letters and figures) not found...
this message repeated at least 3 times.
The system boots at last but from where is this uuid read? I cannot find it anywhere (/dev/disk/byuuid, using command blkid, etc...)
Added today, after updating the kernel, this new message:
WARNING: VG name fedora: existing f50a09-..... (created here) takes precedence over 6cB1NT-.....
ETH1:
WARNING: Kernel Errors Present e1000: eth1: e1000_request_irq: Unable to allocate MSI interrupt Error: -22 ...: 1 Time(s)
I never got any answer! do kernel developers never read this list?
What will happen with the next kernel? System won't boot? shall I lose my printer? My soundcard?
Regards.
- -- François Patte UFR de mathématiques et informatique Université René Descartes http://www.math-info.univ-paris5.fr/~patte
François Patte wrote:
WARNING: Kernel Errors Present e1000: eth1: e1000_request_irq: Unable to allocate MSI interrupt Error: -22 ...: 1 Time(s)
Possibly this and the USB problems are to do with interrupt allocation... have a look through
dmesg | less
looking for advice about interrupt allocation issues. Sometimes when there are problems there is a warning to try a kernel parameter like noapic or pci=biosirq -- give these a try and see if the situation changes.
-Andy
On Thu, 28 Jun 2007 10:05:20 +0200 François Patte francois.patte@math-info.univ-paris5.fr wrote:
I can see people getting problems when they update their kernel: one cannot get his preceding resolution on his monitor, another one has no more printer....
I posted some messages about new problems after updating my kernel....
NO ANSWER!
The correct way to post about bugs in Fedora is to use bugzilla. Asking on the lists to assess whether anyone else experiences the same problem is a good thing, but when nobody else seems to do so, please file a bug.
https://bugzilla.redhat.com/bugzilla/index.cgi
Do provide lots of detail (exact kernel version and other packages involved, system specs, etc), it will get you a faster and better response.
I post again, in hope... before switching to another distro...
It is of no use to mention 'other distros'. In fact if it works better for you, there's no reason you shouldn't switch.
Regards,
--Stijn
Verily I say unto thee, that François Patte spake thusly: [snip rant]
1. The kernel is in a constant state of flux. Some versions work well on most hardware, and some don't. If an updated kernel does not work on your hardware, then simply reboot back into the previous one, and be happy. There is no law that forces you to use new kernels, unless your current one is lacking in some way. If the kernel you use now works, then keep it. End of story.
2. As much as I'm sure there are some very helpful people in the group, you're unlikely to get much help with a rant, especially one severely lacking in detail. Keep it calm and clear and you may get an answer.
3. This is not a bug reporting service. See bugzilla.redhat.com.
4. "Threatening" to switch distros unless your demands are met, will likely just result in a good hearty laugh all round, followed by the traditional "don't let the door hit your ass on the way out". Even the infamous Eric S. Raymond didn't impress with that stunt, so I doubt anyone else can.
5. Oh and just for good measure, when in doubt - RTFM. There's about 300MB worth in /usr/share/{man,doc} so that ought to keep you busy.
Bonne chance.
Keith G. Robertson-Turner wrote:
- "Threatening" to switch distros unless your demands are met, will
likely just result in a good hearty laugh all round, followed by the traditional "don't let the door hit your ass on the way out". Even the infamous Eric S. Raymond didn't impress with that stunt, so I doubt anyone else can.
Yes BTW on that...
'' Linspire deal: What will ESR and Shuttleworth do now?
By Sam Varghese Friday, 15 June 2007
A few months back, the self-styled open source advocate Eric S. Raymond made a grand announcement about switching Linux distributions and moving from Fedora to Ubuntu.
What Raymond did not let on at that time - February 2007 - was that he had joined the board of Freespire, a community Linux distribution which is owned by the company which sells the commercial distribution Linspire. Formerly known as Lindows, Linspire has no problems with including proprietary software, as long as it meets users' needs.
Raymond has been an implacable foe of Microsoft; one incident which is touted as proof of this is an encounter with Microsoft's Craig Mundie in an elevator. When Mundie asked him who he was, Raymond is reported to have said: "I am your worst nightmare."
Given his background, I'd like to pose a query to Raymond: Now that Linspire has genuflected to the people in Redmond, will you do the honourable thing and quit the board of Freespire?
...''
http://www.itwire.com.au/content/view/12899/1090/
Not sure he actually joined the "board", it was some advisory panel IIRC, but I don't know.
-Andy
Verily I say unto thee, that Andy Green spake thusly:
Given his background, I'd like to pose a query to Raymond: Now that Linspire has genuflected to the people in Redmond, will you do the honourable thing and quit the board of Freespire?
Frankly I just don't care about either Lindows or ESR enough to even ask the question. ESR is an OSS evangelist, but he's no Free Software advocate, so he'd probably quite enjoy working for MS anyway.
I'm more concerned about Szulik's recent "no comment" remark over "negotiations" to join Microsoft's patent protection racket.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Keith G. Robertson-Turner a écrit :
Verily I say unto thee, that François Patte spake thusly: [snip rant]
- The kernel is in a constant state of flux. Some versions work well on
most hardware, and some don't. If an updated kernel does not work on your hardware, then simply reboot back into the previous one, and be happy. There is no law that forces you to use new kernels, unless your current one is lacking in some way. If the kernel you use now works, then keep it. End of story.
In that case I don't understand too much many warnings about too old versions of softwares.... You can read these warnings on this list and on some others.
I believe, but I seem to be wrong, that a new version is done to correct and enhance previous ones, not to make what was working no more working.
- As much as I'm sure there are some very helpful people in the group,
you're unlikely to get much help with a rant, especially one severely lacking in detail. Keep it calm and clear and you may get an answer.
I put in my message all what I was aware of: even turning the log_error to "debug" in dev.conf file, for instance, did not give other information about my usb scanner.
- This is not a bug reporting service. See bugzilla.redhat.com.
Before reporting a bug, I want to know if it is really a bug, not something misconfigured. I sent on the list the error codes returned: what are these codes if you can't find their meaning somewhere (and not in the 300Mb man pages you refer to).
- "Threatening" to switch distros unless your demands are met, will
likely just result in a good hearty laugh all round, followed by the traditional "don't let the door hit your ass on the way out". Even the infamous Eric S. Raymond didn't impress with that stunt, so I doubt anyone else can.
OK! I apologize... I don't want to be kicked out in my ass! Though it is difficult to accept that things that were working are no more working after an update. I use redhat/fedora since redhat 5 and it used to go better and better.... I am not sure that it is still the policy when I read here some messages about fc6 and now f7....
Bonne chance.
Merci.
- -- François Patte UFR de mathématiques et informatique Université René Descartes http://www.math-info.univ-paris5.fr/~patte
Verily I say unto thee, that François Patte spake thusly:
Keith G. Robertson-Turner a écrit :
Verily I say unto thee, that François Patte spake thusly:
[snip rant]
- The kernel is in a constant state of flux. Some versions work
well on most hardware, and some don't. If an updated kernel does not work on your hardware, then simply reboot back into the previous one, and be happy. There is no law that forces you to use new kernels, unless your current one is lacking in some way. If the kernel you use now works, then keep it. End of story.
In that case I don't understand too much many warnings about too old versions of softwares.... You can read these warnings on this list and on some others.
I believe, but I seem to be wrong, that a new version is done to correct and enhance previous ones, not to make what was working no more working.
This is sometimes true, sometimes not. Often an "update" is actually the *addition* of features (e.g. in the case of the kernel - new hardware support). By adding features, one invariably adds bugs. In fact simply by fixing bugs, one invariably creates others. E.g.:
9 little bugs in the code 9 little bugs in the code Fix one bug, compile it again 10 little bugs in the code
Unless you read about a *specific* security vulnerability then there may be no reason to upgrade the kernel, *unless* you are currently having difficulties with that kernel.
It *is* important to keep up with *security* updates, and obviously you'll want updates that address stability (bugs) issues, but don't feel pressured to update a package just because it's "there".
There will be occasions where you don't have a choice, because in order to install or update a particular package you *need* another to also be installed or updated so as to meet dependencies. Previous examples of that in the kernel include udev and SELinux.
I have machines on my network with uptimes in excess of three years, or IOW no kernel updates for three years, and all those systems work perfectly well, so trust me when I say updates are not always *essential*, although they may be *desirable*. YMMV.
This is why I stress that if you update a package (in your case - the kernel) and it has severe issues, then the solution is not to rant about it, but rather:
1) ... Go back to the previous (working) kernel. 2) ... File a bugzilla report. 3) ... Discuss (amiably) this issue with others, who *may* have a solution or workaround. 4) ... Have a coffee and relax.
- As much as I'm sure there are some very helpful people in the
group, you're unlikely to get much help with a rant, especially one severely lacking in detail. Keep it calm and clear and you may get an answer.
I put in my message all what I was aware of: even turning the log_error to "debug" in dev.conf file, for instance, did not give other information about my usb scanner.
- This is not a bug reporting service. See bugzilla.redhat.com.
Before reporting a bug, I want to know if it is really a bug, not something misconfigured. I sent on the list the error codes returned: what are these codes if you can't find their meaning somewhere (and not in the 300Mb man pages you refer to).
I saw the OP in this thread, but not the previous message. One little detail that's missing is the kernel *version*, which is in this case absolutely essential for determining the (possible) cause. IIRC you also missed the sequence of steps needed to reproduce the given errors (specifics are important).
In any case, let me repeat ... this is not a bug reporting service, and there is no one here under any contractual obligation to even read your messages, let alone answer them. Most of the people here are just ordinary users, *not* devs ... although there are a few devs who monitor this list too.
As for man pages ... it is my considerable experience that if one carefully reads the documentation for any given problematic component, then the solution presents itself quite readily, even if specific error codes are not explicitly mentioned.
As a recent example, I had difficulty using a tool called "nut" (Network UPS Tools) on one of my servers. As far as I could tell, the configuration files were perfectly correct, but it produced an error stating that it had "lost communication with the UPS" every time it started (from init). After reading the documentation I discovered that the actual initscript was calling upsd using the wrong flags, so I edited the script and now it works. Actually that reminds me - I should file a bug on that ;)
- "Threatening" to switch distros unless your demands are met,
will likely just result in a good hearty laugh all round, followed by the traditional "don't let the door hit your ass on the way out". Even the infamous Eric S. Raymond didn't impress with that stunt, so I doubt anyone else can.
OK! I apologize... I don't want to be kicked out in my ass! Though it is difficult to accept that things that were working are no more working after an update. I use redhat/fedora since redhat 5 and it used to go better and better.... I am not sure that it is still the policy when I read here some messages about fc6 and now f7....
Heck, I'm still using Red Hat 7.3 on some machines, which was for many the pinnacle of Red Hat on the Desktop. I'd say that the many technical innovations since then, make modern Red Hat/Fedora systems a very worthwhile upgrade, although you still need to beware certain issues like bloat and featuritis. I even have one using 5.1 (Manhattan) on Motorola 68K hardware running at a whopping 8MHz, which I very much doubt would run Fedora 7 :)
Updates are optional ;)
Bonne chance.
Merci.
Je vous en prie.
I never got any answer! do kernel developers never read this list?
They do but bugs are tracked in bugzilla, and like all free distributions there is no service contract or guarantee.
What will happen with the next kernel? System won't boot? shall I lose my printer? My soundcard?
Well hopefully whatever is broken on your box will get fixed, but if you want that to happen file a bugzilla for it and include relevant details (such as what hardware, processor, disks etc you have)
Alan
François Patte wrote:
I can see people getting problems when they update their kernel: one cannot get his preceding resolution on his monitor, another one has no more printer....
I must say, my experience is the opposite - I used to find that distribution kernels often would not run on one or other of my (7) machines, but I haven't had any such problem with FC-6 or Fedora-7.
What I have noticed is that I get much more gumpf on the screen when I re-boot, much of it about USB. I don't read this properly - it flashes by too fast, for one thing - and it doesn't seem to be repeated in /var/log/dmesg (or if I run "dmesg").
I sort of thought everything that came up on the screen when re-booting would appear in a log file?