package linux-wlan-ng-doc 0.2.9+dfsg-2ubuntu1 failed to install/upgrade: cannot access archive: No such file or directory

[tdflanders]

Binary package hint: linux-wlan-ng

thomas@thomas-laptop:~$ lsb_release -rd ; uname -a ; apt-cache policy linux-headers-generic linux-image-generic linux linux-source-2.6.27 linux-restricted-modules synaptic apport-gtk software-properties-gtk network-manager linux-wlan-ng
Description: Ubuntu intrepid (development branch)
Release: 8.10
Linux thomas-laptop 2.6.27-3-generic #1 SMP Wed Sep 10 16:02:00 UTC 2008 i686 GNU/Linux
linux-headers-generic:
  Installed: 2.6.27.2.2
  Candidate: 2.6.27.2.2
  Version table:
 *** 2.6.27.2.2 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
linux-image-generic:
  Installed: 2.6.27.2.2
  Candidate: 2.6.27.2.2
  Version table:
 *** 2.6.27.2.2 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
linux:
  Installed: 2.6.27.2.2
  Candidate: 2.6.27.2.2
  Version table:
 *** 2.6.27.2.2 0
        500 http://gb.archive.ubuntu.com intrepid/restricted Packages
        100 /var/lib/dpkg/status
linux-source-2.6.27:
  Installed: 2.6.27-3.4
  Candidate: 2.6.27-3.4
  Version table:
 *** 2.6.27-3.4 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
linux-restricted-modules:
  Installed: 2.6.27.2.2
  Candidate: 2.6.27.2.2
  Version table:
 *** 2.6.27.2.2 0
        500 http://gb.archive.ubuntu.com intrepid/restricted Packages
        100 /var/lib/dpkg/status
synaptic:
  Installed: 0.62.1ubuntu8
  Candidate: 0.62.1ubuntu8
  Version table:
 *** 0.62.1ubuntu8 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
apport-gtk:
  Installed: 0.114
  Candidate: 0.114
  Version table:
 *** 0.114 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
software-properties-gtk:
  Installed: 0.66
  Candidate: 0.66
  Version table:
 *** 0.66 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
network-manager:
  Installed: 0.7~~svn20080908t183521+eni0-0ubuntu2
  Candidate: 0.7~~svn20080908t183521+eni0-0ubuntu2
  Version table:
 *** 0.7~~svn20080908t183521+eni0-0ubuntu2 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
linux-wlan-ng:
  Installed: 0.2.9+dfsg-2ubuntu1
  Candidate: 0.2.9+dfsg-2ubuntu1
  Version table:
 *** 0.2.9+dfsg-2ubuntu1 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
     0.2.8+svn1854+dfsg-1ubuntu1 0
        500 cdrom://Ubuntu 8.10 _Intrepid Ibex_ - Alpha i386 (20080903) intrepid/main Packages
thomas@thomas-laptop:~$

ProblemType: Package
Architecture: i386
Dependencies:

DistroRelease: Ubuntu 8.10
ErrorMessage: cannot access archive: No such file or directory
Package: linux-wlan-ng-doc 0.2.9+dfsg-2ubuntu1
PackageArchitecture: all
SourcePackage: linux-wlan-ng
Title: package linux-wlan-ng-doc 0.2.9+dfsg-2ubuntu1 failed to install/upgrade: cannot access archive: No such file or directory
Uname: Linux 2.6.27-3-generic i686

[Tormod Volden (tormodvolden)]

Why do you not have /proc mounted when you run the upgrades? Can you please attach your /etc/fstab?

In what context are you doing the upgrade?

Why do you have linux-wlan-ng installed?

It seems that you have filed a number of bugs that can not be confirmed by anyone else. Are you sure you don't have faulty RAM or other hardware issues? Do you have a special setup? Please describe it shortly.

[tdflanders (thomasdelbeke)]

Hi there Tormod,

Now that is exactly what I told you in the wlan-linux-ng topic. Can you reopen that, or give me a way to view the bugs that I have filed formerly, but were dismissed as invalid, so I can organise my stuff a bit? Thank you. I have deleted a lot of messages in my inbox already, since I thought they would pop up at this site: . This is the case, but as soon as they are marked as invalid, I can no longer retrieve the information I filed there, for my own records.

Anyway, I will attach my /etc/fstab here, but since my system is reinstalled since due to yet another fatal system crash, I doubt it will help. I am trying to be as constructive as I can here, but not knowing anything about the linux architecture, or about informatics in general, does not help a lot. All I get from you people is some generalities about not adding too much info, and not too little, do not waffle, stay to the point ... This works fine for an informatics graduate, but I can not do that obviously, since I do not know what the point is, nor what info you are actually looking for. I can only try to be as meticulous as possible in my reports.

Can you please help me out on how to file a report that anyone will actually read, without it being dismissed as invalid at the first glance? I will try and some up my findings in the next screen.

[tdflanders (thomasdelbeke)]

So, about trying to sum up my findings.

I know my memory is just fine. I do suffer from the memtest86 bug. I have filed a comment there previously.

https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/246412

I will try to verify it know just one more time. I will try to recreat the aptoncdbug after I take out one of the 2 GB chips, than the other. I will also do memcheck86+ again, and tell you what the result is.

https://bugs.launchpad.net/aptoncd/+bug/267633

The problem is in my opion a BIOS problem.

My BIOS settings are:

Phoenix Trusted Core (tm)
BIOS Version: v1.23
VGA BIOS Version: 1264
KBC Version: 08.26

Virtualbox recognises the correct amount of memory, while gnome-system-monitor does not. I have described this earlier, also in the aptoncdbug (see above). I have added two screenshots about this, so I will not upload them again.

See the bug you closed down earlier:

https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/267607

I mind you again that I was able to find this bug again in my email, but not all of the others. I have deleted a lot, since I get about 50 replies a day of duplicate bugs, that other people have filed.

Now I have tried to bundle my ideas about this in the consolekit bug:

https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/267328

Hobsee thought it was unstructured and James does not understand me either.

I have referred to my post in the forum a couple of times before, but no one is reading it:

http://ubuntuforums.org/showthread.php?t=912682

[tdflanders (thomasdelbeke)]

Ok, so I am opening up a new window every time, so you do not have to click 'read more'. The only button anyone wants to click on my posts is 'read less'. Unfortunately it is not there. Let's add it to the wish list. There we have it, I am waffling again. Sorry about that Hopsee.

Anyway, let's try to recap in a hundred words, knowing that this is insufficient:

There is something wrong with my BIOS. An eBay salesman has possibly tempered with it. Therefore my memtest86+ my actually correctly indicate faulty memory, but the memory itself is just fine. This may or may not be related to the memtest86+ bug described above.

After this comment I will log off to validate the memory once more. In the mean time, can anyone look at the valgrind.log of the aptoncd bug? It should contain some data you could use. Also the memory behaviour is as visualised on gnome-system-monitor is explained there. Anyway: the RAM usage increases linearly up to 3 GB, after which it crashes due to incorrect BIOS settings. Also see my screenshots on the BIOS settings there pleased.

There are many more arguments I have, but I will try to keep it with this for now.

[tdflanders (thomasdelbeke)]

One more thing, the terminal ouput error (one of the many) of the '$ sudo dpkg-reconfigure -a'command (please notice the RAM errors):

update-initramfs: Generating /boot/initrd.img-2.6.27-1-generic
cp: cannot stat `/lib/udev/hotplug.functions': No such file or directory

...done
Replacing config file /etc/clamav/clamd.conf with new version
 * Stopping ClamAV virus database updater freshclam [ OK ]
 * Starting ClamAV virus database updater freshclam [ OK ]
 * Saving console font and keymap for next boot... [ OK ]
update-initramfs: Generating /boot/initrd.img-2.6.27-1-generic
cp: cannot stat `/lib/udev/hotplug.functions': No such file or directory
Error: kernel headers not found in '/usr/src/linux/'
 * Stopping periodic command scheduler crond

The system user `messagebus' already exists. Exiting.
 * Reloading system message bus config... [ OK ]
File '/usr/share/applications/gxine.desktop' contains invalid MIME type 'x-content/video-vcdx-content/video-vcd' that has more than one slash
 * Stopping DHCP D-Bus daemon dhcdbd [ OK ]
 * Reloading system message bus config... [ OK ]
 * Starting DHCP D-Bus daemon dhcdbd

File '/usr/share/applications/gxine.desktop' contains invalid MIME type 'x-content/video-vcdx-content/video-vcd' that has more than one slash
Unknown media type in type 'all/all'

rm: cannot remove `ram1-': Read-only file system
rm: cannot remove `ram2-': Read-only file system
mknod: `ram2-': Read-only file system
makedev ram2 b 1 2 root disk 0660: failed
rm: cannot remove `ram2-': Read-only file system
rm: cannot remove `ram3-': Read-only file system
mknod: `ram3-': Read-only file system
makedev ram3 b 1 3 root disk 0660: failed
rm: cannot remove `ram3-': Read-only file system
rm: cannot remove `ram4-': Read-only file system
mknod: `ram4-': Read-only file system
makedev ram4 b 1 4 root disk 0660: failed
rm: cannot remove `ram4-': Read-only file system
rm: cannot remove `ram5-': Read-only file system
mknod: `ram5-': Read-only file system
makedev ram5 b 1 5 root disk 0660: failed
rm: cannot remove `ram5-': Read-only file system
rm: cannot remove `ram6-': Read-only file system
mknod: `ram6-': Read-only file system
makedev ram6 b 1 6 root disk 0660: failed
rm: cannot remove `ram6-': Read-only file system
rm: cannot remove `ram7-': Read-only file system
mknod: `ram7-': Read-only file system
makedev ram7 b 1 7 root disk 0660: failed
rm: cannot remove `ram7-': Read-only file system
rm: cannot remove `ram8-': Read-only file system
mknod: `ram8-': Read-only file system
makedev ram8 b 1 8 root disk 0660: failed
rm: cannot remove `ram8-': Read-only file system
rm: cannot remove `ram9-': Read-only...

[Tormod Volden (tormodvolden)]

I am afraid no developers have time to look into your problems, because they seem to be something specific to your hardware. We can not accommodate software to work around the broken BIOS of one user, right? You also have mention somewhere that you have broken your installation by changing file permissions en masse.

You should try to install from scratch with fresh filesystems, using for instance only 2GB, since your BIOS messes up higher memory from what I understand.

[tdflanders (thomasdelbeke)]

OK,

this about does it:

https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/264897

Can you sit down for just one second with:

Sebastien Bacher
Sarah Hobbes
James Westby

possibly also:

Brian Murray
Chris Coulson

and then tell me EXACTLY what to do?

I did what you asked so far, I now have only ubuntu repositories installed, not even virtual box ose or any dependencies and no etch-backports either. I will go down for a beauty sleep now, when I wake up, I will do the memory test again. Anyway, I am smart enough to realise that I should refrain from reporting any more bugs if it is a hardware problem, but I doubt it.

So see you,

Thomas

[Tormod Volden (tormodvolden)]

Unless you can confirm the bugs on another hardware I am convinced it is a hardware problem. Thanks for all your bug reporting, but I think it's better that you fix the hardware before continuing. Otherwise you distract all these developers with non-bugs. There are so many real software bugs and so few developers and I think you understand which problems can be given priority or not.

[tdflanders (thomasdelbeke)]

Hi Tormod,

It is certainly not a hardware problem, since both memtest86+v.165 on the 7.04 live CD and memtest86+v1.70 on the 7.10 live CD indicated no error. I will stop wasting my time here, since you guys are not listening anyway. I asked you if there is a way I can retrace the bugs that you have incorrectly closed as invalid, for my personal records. I hope there is really, since you guys have destroyed a zillion usefull crashreports. Now the bug is certainly a BIOS issue, which is software, not hardware. I will now reinstall hardy and reproduce the DVD-RW MD5SUM bug there, which probably is a BIOS-memory issue as well, and which you also have closed down incorrectly. After that I will open a case with Canonical, were I have a 24/7 support contract. I will refrain from posting any further intrepid bugs, as you have asked, but I fear that you will just have to note that the hardy freeze ups and the Red Had consolekit bug in intrepid, are both caused by BIOS conflicts. If I am right, Canonical will have to help me to install a u-boot BIOS are whatever it is they use for pre-cut off date BIOS's, unlike mine in fact, since they cannot defend a stable release on correct hardware being unable to verify md5checksums.

Cheers,

Thomas

[Tormod Volden (tormodvolden)]

memtest86+ not detecting an error does not prove anything. However, if you can reproduce on another piece of hardware, it would indicate a software problem. Your BIOS counts as your hardware in this situation, unless other people have the same problem. Ubuntu is not going to fix the BIOS of one particular user's PC. You will also spend less of your valuable time if you keep the reports more concise and listen and act to the comments that people give you.

There are no bug reports deleted, they can be found with the search interface, just enable the "Invalid" ones. I doubt your closed reports are "useful". They are not "incorrectly" closed, but closed because there is nothing that can be done about them from the OS side. They don't indicate anything is wrong in the Ubuntu software.

"on correct hardware being unable to verify md5checksums" - you should rather contact your hardware manufacturer, this is probably not correct hardware. Please understand that the BIOS is part of the motherboard and not of the OS.

There is still a slight chance that the kernel doesn't cope with your motherboard/BIOS/memory combination, but then you have to file a bug on the kernel ("linux" package) and provide concise, relevant information. If you have a contract with Canonical maybe they can help you with this.

[tdflanders (thomasdelbeke)]

Hi there,

this does not reoccur in 8.10 beta. You can close this one. Anyway, I reflashed my BIOS and asked Canonical to verify my hardware, to their annoyance. Please do not tell people they have malfunctioning hardware unless you can say what hardware that would be and provide a testing tool from main to verify this, thank you.

Thomas