Processing commands for [EMAIL PROTECTED]:
> severity 415620 important
Bug#415620: Wrong driver for Radeon card?
Severity set to `important' from `normal'
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrato
On Tuesday 27 February 2007 03:30, Thanatermesis - Elive wrote:
> I have found a user where os-prober don't has autodetected its windows
> systems, after to a long trace i have found to the problem is on the
> file "NTDETECT.COM" to its called "ntdetect.com", I would recommend to
> change the line
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello, first of all I want to tell you to my english is not very good,
but I try to help in my posible way
I have found a user where os-prober don't has autodetected its windows
systems, after to a long trace i have found to the problem is on the
file
Your message dated Sat, 20 Jan 2007 12:47:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#407138: fixed in discover-data 2.2007.01.20
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Le jeudi 18 janvier 2007 à 22:40 +0100, Petter Reinholdtsen a écrit :
> [Josselin Mouette]
> > lspci -n output:
> >
> > 00:07.0 0604: 8086:25e7 (rev 12)
>
> This is the wrong device. It is a bridge. Please send info on PCI
> device 07:00.0. I suspect it is PCI id 10de:029d, but need you to
> c
[Josselin Mouette]
> lspci -n output:
>
> 00:07.0 0604: 8086:25e7 (rev 12)
This is the wrong device. It is a bridge. Please send info on PCI
device 07:00.0. I suspect it is PCI id 10de:029d, but need you to
confirm it.
Friendly,
--
Petter Reinholdtsen
--
To UNSUBSCRIBE, email to [EMAIL P
Package: discover1-data
Version: 2.2006.12.28
I've just installed etch on a brand new Xeon system with a nVidia Quadro
FX 3500 graphics card, and the X server configured itself to use the
"vesa" driver, while this card is perfectly supported by the "nv"
driver.
Here is the lspci output for this d
tags 289101 pending
retitle 289016 Problems in locales generation
tags 289016 moreinfo
thanks
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing commands for [EMAIL PROTECTED]:
> tags 289101 pending
Bug#289101: Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet not
detected
Tags were: patch
Tags added: pending
> retitle 289016 Problems in locales generation
Bug#289016: TG3 NIC autodetection fails
Changed Bug
clone 289016 -1
retitle -1 Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet not detected
reassign -1 discover1-data
tags -1 patch
thanks
> 1) Installer didn't autodetect onboard TG3 NIC. When installer asked me to
> specify manually what modules to load, I selected tg3, and the NIC was
>
Processing commands for [EMAIL PROTECTED]:
> clone 289016 -1
Bug#289016: TG3 NIC autodetection fails
Bug 289016 cloned as bug 289101.
> retitle -1 Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet not
> detected
Bug#289101: TG3 NIC autodetection fails
Changed Bug title.
>
Processing commands for [EMAIL PROTECTED]:
> reassign 289016 discover1-data
Bug#289016: TG3 NIC autodetection fails
Bug reassigned from package `installation-reports' to `discover1-data'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug
Package: installation-reports
Debian-installer-version: 27-12-2004
uname -a: Linux test 2.6.8-1-386 #1 Thu Nov 25 04:24:08 UTC 2004 i686 GNU/Linux
Date: Thu 06-01-2005 15:00
Method: Booted from sarge netinst CD (27-12-2004) and installed using
ftp://ftp.fi.debian.org, no proxies.
Machine
On Thursday 06 January 2005 15:41, Pasi Kärkkäinen wrote:
> I just installed sarge/testing with network installation CD from
> 27-12-2004. I used "linux26" kernel.
>
> NIC autodetection did not detect onboard tg3 NIC's. But when I chose
> tg3 from the "manual
Hi!
I just installed sarge/testing with network installation CD from 27-12-2004. I
used
"linux26" kernel.
NIC autodetection did not detect onboard tg3 NIC's. But when I chose tg3
from the "manual driver selection" list, the NIC was detected OK.
Output of lspci fo
nk, is whether the hardware ID implies a
>> > layout. (It's not really autodetection; it's a lookup.) I don't know.>
Its hard to do keyboard detection based on hardware ID because
of the cheap way keyboard manufacturers build keyboards:
they do not want to build key l
r the installer chooses
> the modules to load and prompts me for any parameters,
> or whether the expert install was indeed using
> modconf, so that I would have to choose the modules as
> well as set the parameters.
>
> So, does the expert install do autodetection or not?
ers,
or whether the expert install was indeed using
modconf, so that I would have to choose the modules as
well as set the parameters.
So, does the expert install do autodetection or not?
__
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bon
Package: ethdetect
Version: 0.22
Severity: minor
If no NIC is autodetected, ethdetect should default to manual
loading on the next attempt (or just go directly to it).
Matt
--
Oink!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTE
Hello!
I made a program to autoconfigure the kernel (in a very soft manner).
My program is a simple shell script that detect what kernel know
(/proc, ...). It can detect most of modern hardware.
I can convert very fast this program for a installer autodetection.
But I'm not subscrib
Daniel Migowski wrote:
> Sounds good. I didn't know about those tools before, but I think the
> detection is something we should do at one of the first things during the
> install-process.
Of course, I disagree.
The main purpose of the debian installer is to get debian *installed*.
It doesn't
Hi,
On Friday 03 November 2000 03:17, you wrote:
> Assuming you mean DDC for getting monitor frequencies and such, X4
> already does this automatically. If not there are apps out there like
> read-edid that can do this in user-space. Combined with things like
> anXious (or Progeny's dexter) this
__
Make A Buck Or Two @ TheMail.com - Free Internet Email
Sign-up today at http://www.themail.com/ref.htm?ref=1527645
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTE
__
Make A Buck Or Two @ TheMail.com - Free Internet Email
Sign-up today at http://www.themail.com/ref.htm?ref=1527645
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTE
> even if this can only be done with a special kernel, what's wrong with
> probing the monitor. I am new to the list, so i don't know if the your
> installer will install X at boottime, which I highly recommend. Most users
> from Windos haven't seen the DOS-Prompt before, and having to use the
Hi,
even if this can only be done with a special kernel, what's wrong with
probing the monitor. I am new to the list, so i don't know if the your
installer will install X at boottime, which I highly recommend. Most users
from Windos haven't seen the DOS-Prompt before, and having to use the she
On Thu, Oct 05, 2000 at 07:22:41PM -0400, Will Lowe wrote:
> I'll look at it. I'm using a table of device->driver mappings I stole
> from RH 6.2, so unless it has the X info, I don't.
Some time ago (actually it must be 0.5 to 1 year ago now) I also
started implementing a pci hardware detection.
Please don't CC me on replies.
> A generic svga at 1024x768@60Hz should be a good default in most situations
> if nothing else is found.
Hrm, I'd rather not contribute to workplace violence in the United States
by defauling to a refresh rate that is guaranteed to result in psychosis.
> Consider
> Well, it looks like everybody's doing the same thing at the same time.
>
> At Progeny, Joseph Carter has been developing a libdetect based program
> called "discover" which spits out the correct X server (for 3.x) or X
> server and driver (for 4.x) given the PCI info.
>
> I'm writing a program
> While you're at it -- perhaps you could try to come up with some
> patches against xviddetect so it knows about more cards? It really
> only knows pathetically few right now. See the bugs against that
> package too.
woah if you want to add more things to xviddetect, file bugs or
email me
Excellent. Will, let us know what else we can do to help.
--
.Adam Di [EMAIL PROTECTED]http://www.onShore.com/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Thu, Oct 05, 2000 at 07:22:41PM -0400, Will Lowe wrote:
> > That would be cool. You wanna patch dbootstrap -- we could even make
> > that conditional on the pci stuff being there at all..
>
> I'm in the midst of building a patch to dboostrap now. I'll throw in a
> check to see if /proc/bus/p
> That would be cool. You wanna patch dbootstrap -- we could even make
> that conditional on the pci stuff being there at all..
I'm in the midst of building a patch to dboostrap now. I'll throw in a
check to see if /proc/bus/pci exists, and if not we'll skip the "do you
want to autodetect PCI d
Will Lowe <[EMAIL PROTECTED]> writes:
> Right. I'm adding a step just before the user is presented with the list
> of modules that asks if the user would like to try autoprobing for PCI
> devices.
That would be cool. You wanna patch dbootstrap -- we could even make
that conditional on the pci
> busybox and mini-grep are on the root filesystem, not the base set.
Right. I realized this later last night. So I rewrote the whole thing in
ash, and it's now down to 2k (after gzip -9). It will, of course, get
larger as the table grows when new hardware is added.
> Sure, of course. The 'c
> Please don't forget that debian supports machines without pci bus. What would
> your changes to boot floppies do if this is the case ?
Nothing. The program that does autopci detection just says "Can't find
PCI bus" and you go one to configure the drivers the old way.
> Also, it would be nice
Will Lowe <[EMAIL PROTECTED]> writes:
> (I just remembered:)
>
> The reason I did it in C rather than in ash was that I wanted the program
> to be usable _before_ base.tar.gz is untarred (and hence before grep and
> the rest of busybox is available)
busybox and mini-grep are on the root filesy
On Tue, Oct 03, 2000 at 04:20:23PM -0400, Will Lowe wrote:
> I've put together (from pciutils and Redhat's anaconda) a small program
> that asks the kernel about devices on the PCI bus and loads (or lists )the
> needed driver modules. This hopefully enables NIC autodetection
> I suppose I could write a shell script to do the same thing, looking at
> /proc/bus/pci/devices instead of asking the kernel directly, and keep the
> table as text ...
(I just remembered:)
The reason I did it in C rather than in ash was that I wanted the program
to be usable _before_ base.tar
> this is really just like what xviddetect/anXious does; you just have a
> db of kernel modules instead of Xserver names
Yes. It's something of a pain because it means you've (I've) got to keep
the table up to date as new drivers are written or old ones expanded, but
I don't see how else it
In reference to a message from Will Lowe, dated Oct 03:
> I've put together (from pciutils and Redhat's anaconda) a small program
> that asks the kernel about devices on the PCI bus and loads (or lists )the
> needed driver modules. This hopefully enables NIC autodetection
> > If you're not already gzip'ing the vendor/device id table this could be
> > an option for reducing it.
> That doesn't matter since the root filesystem is gzipped anyhow.
Actually, in order to reduce the amount of parsing needing to be done by
the program, I've got a perl script that builds a
Will Lowe <[EMAIL PROTECTED]> writes:
> > For boot-floppies for Potato? I am not sure we'd be allowed to add
> > this sort of change to potato -- anaconda isn't included in Potato.
>
> This is _hacked_ from anaconda, but isn't anaconda itself. It's one
> smallish (22k if you build the "tiny"
Ray Knight <[EMAIL PROTECTED]> writes:
> If you're not already gzip'ing the vendor/device id table this could be
> an option for reducing it.
That doesn't matter since the root filesystem is gzipped anyhow.
--
.Adam Di [EMAIL PROTECTED]http://www.onShore.com/>
--
To UNSUBSCRIBE, email t
Will Lowe wrote:
>
> > For boot-floppies for Potato? I am not sure we'd be allowed to add
> > this sort of change to potato -- anaconda isn't included in Potato.
>
> This is _hacked_ from anaconda, but isn't anaconda itself. It's one
> smallish (22k if you build the "tiny" version) binary. I
> For boot-floppies for Potato? I am not sure we'd be allowed to add
> this sort of change to potato -- anaconda isn't included in Potato.
This is _hacked_ from anaconda, but isn't anaconda itself. It's one
smallish (22k if you build the "tiny" version) binary. It can't get a
whole lot smalle
Will Lowe <[EMAIL PROTECTED]> writes:
> I've put together (from pciutils and Redhat's anaconda) a small program
> that asks the kernel about devices on the PCI bus and loads (or lists )the
> needed driver modules. This hopefully enables NIC autodetection for
>
I've put together (from pciutils and Redhat's anaconda) a small program
that asks the kernel about devices on the PCI bus and loads (or lists )the
needed driver modules. This hopefully enables NIC autodetection for
anyone who's using a PCI nic.
You can grab the current version o
Last night I put together some code from pciutils and Redhat's anaconda
and came up with a little program that asks the kernel about installed PCI
hardware and modprobes the needed drivers, using a little table. I don't
know if it's useful or not for the next incarnation of boot-floppies, but
you
This is a nice idea but I don't think we can consider such a change
for Potato. I don't know. I'll leave it to Randolph to assess. If a
Potato modconf does come in, we can make this change though, seems
pretty minor.
--
.Adam Di [EMAIL PROTECTED]http://www.onShore.com/>
--
To UNSUBSCR
Package: boot-floppies
Version: N/A
Severity: wishlist
This small patch enables the boot-floppies to take advantage of
the modconf module autodetection feature (I submitted a patch for
the integration of modconf and libdetect against modconf,
bug #70588).
---8<--- cut h
rig/template/eval_C.fixed Sun Aug 6 22:34:06 2000
+++ modconf-0.2.27/template/eval_C.fixedTue Aug 29 13:05:11 2000
@@ -84,6 +84,12 @@
dir_descr_scsi="Drivers for SCSI controller cards and classes of SCSI devices"
dir_descr_video="Drivers for Video4Linux"
52 matches
Mail list logo
