Package: installation-reports
Boot method: CD
Image
version:http://cdimage.debian.org/cdimage/wheezy_di_beta4/i386/iso-cd/debian-wheezy-DI-b4-i386-netinst.iso
Date: 09:00 Fri 30 Nov 2012
Machine: Dell Inspiron 530
Processor:Intel® Core™2 Quad CPU Q6600 @ 2.40GHz × 4
Memory:4GB
Partitions: df
Many thanks, Loïc! I was beginning to feel REALLY puzzled by some of the
inconsistent behaviour I was seeing (on HP MediaVault 2120/5020 as well as
NSLU2). It's good to hear someone else getting that too, and some progress
towards a solution (and a workaround I can try).
Barry
On 6 Apr
I can confirm that there is a regression in 2.6.25 and 2.6.26 from
2.6.24 regarding reading from certain (actually quite a lot of) usb
flash readers.
I have personally experienced this with the eeepc internal SDHC card
reader, and a SanDisk MicroMate external usb SDHC card reader, with
Frans Pop wrote:
Sorry, I'm a moron.
Well, I don't think you're a moron. But then, I don't think I'm a moron
either, so maybe my judgement is impaired!
The correct line should be:
SUBSYSTEM==net, DRIVERS==?*, ATTR{address}==00:d0:59:bd:d5:c5, ATTR{type}==1,
NAME=eth1
Change the second
Frans Pop wrote:
You missed my point. There were still errors in the line I last suggested.
The correct syntax is: ATTR{type}==1
Your second line still has: ATTR{type}=1
Many apologies. I really thought I had checked by lining up the old and
the new line beneath each other in an editor,
Frans Pop wrote:
The workaround is still, as I wrote earlier, to remove the existing rename
rule for the wifi interface in the z25 script and to let udev regenerate
it.
I understand the complexity of the argument.
I would just stress that from the simple user (including me) point of
view,
Frans Pop wrote:
Barry: a few requests.
1) What was the wireless interface called in the installer?
You can probably tell from /var/log/installer/syslog.
eth1
You can check this from my original report (email of Fri, 27 Jun 2008
14:16:15 +0100 in bug 488267), and in the installer outputs I
I should have expanded the argument in two ways. Building on:
I suppose this does make some kind of sense, as hostap_pci must in fact do (at
least) two things in succession:
* create the master interface wifiN (where N=0 for us as it's the first such
interface to be created)
* create an sta
Otavio Salvador wrote:
Hello Barry,
Looking at the output data I fail to see how this mess happened. I'd
like to ask you to do another test for us. Please boot d-i and after
wireless has been properly setup grab the following information:
/proc/net/dev
lspci -knn
My current bet is that
Otavio Salvador wrote:
Hello Barry,
Looking at the output data I fail to see how this mess happened. I'd
like to ask you to do another test for us. Please boot d-i and after
wireless has been properly setup grab the following information:
/proc/net/dev
lspci -knn
My current bet is that
Package: installation-reports
Severity: important
-- Package-specific info:
Boot method: CD
Image version:
http://cdimage.debian.org/cdimage/lenny_di_beta2/i386/iso-cd/debian-LennyBeta2-i386-netinst.iso
Date: 26 June 2008 10:00 BST
Machine: Sony Vaio PCG-R600HMPD
Partitions: df -Tl will do;
Thanks - further info as requested given below.
Shall try to test daily build for the firewire/CD over the weekend.
Barry
MAIN PROBLEM: wifi (Prism2) nicely detected, install goes fine till main
reboot. On reboot, no wifi network. REASON:
* /etc/network/interfaces was written accurately, but
Package: genisoimage
Version: 9:1.1.7.1-1
Severity: important
Thanks again to Martin Guy, I can confirm that the buggy behaviour does
NOT happen for genisoimage version 1.1.7.1-1 (sid current) on armel.
Instead, the behaviour is just as on i386 and amd64: the RR signatures
are detected and
Package: genisoimage
Version: 9:1.1.7.1-1
Severity: important
Thanks to Martin Guy, I can confirm this buggy behaviour for genisoimage
version 1.1.7.1-1 (sid current) on arm (and indeed on a different
machine from my own NSLU2, whew).
The steps to reproduce in the original report again
Package: genisoimage
Version: 9:1.1.2-1
Severity: important
The following behaviour is in error on arm only, at least on my NSLU2
running etch. On i386 and amd64, the error does not occur.
Steps to reproduce on an arm machine:
cd somewhere safe
mkdir tmp1
touch tmp1/nullfile-with-long-name
posts) be of some use to
those who, like me, prefer to use testing (lenny) as their dom0, for
reasons of security and relative stability.
Thanks again for your help, and for all your debian efforts.
Barry Tennison
***
The following may be needed to convert a debian installation using
I can confirm Russell Coker's report of 25 Mar 2008 in almost exactly the same
detail.
linux-image-2.6.24-1-xen-686 does not work as a domU (nor as a dom0) for me in
a setup where 2.6.18-5-xen-686 works fine as a domU kernel (and is also the
dom0 kernel).
The extra I can add is that
Package: iceape-calendar
Version: 1.0.8-3
Severity: important
As mentioned in the body of my first report, this bug is equally
present in the version 1.0.8-3 in unstable (system details below).
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable')
), albeit on amd64.
Happy to provide further information.
Barry Tennison
no .sig, but kudos to all those working so hard on debian
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel
and effort.
Hope this helps - sorry, I'm not expert enough to attach a patch for the
recommended change.
Thanks for all the excellent debian work!
Barry Tennison
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin
I'm trying to help with getting a backtrace on the bug to which your
helpful email below refers. I'd love to see this bug cleared!
I've followed http://wiki.debian.org/?HowToGetABacktrace
building and installing mozilla-calendar and its build-deps. Whew!
I'm no gdb expert. The gnome menu
Thanks for your help, Loic.
I enclose backtraces on the segfault by:
mozilla-1.7.8-1sarge2
This is in my up-to-date etch/testing environment,
with the backtrace produced as described in
http://wiki.debian.org/?HowToGetABacktrace
mozilla-1.7.12
Unfortunately, I was unable to build
22 matches
Mail list logo
