On 23 March 2013 13:31, Thierry Vignaud thierry.vign...@gmail.com wrote:
@thierry: i donno what you think of it, but imo:
A) fixing lstdetect would be the cleanest way (maybe not the simplest)
B) perhaps in the comparing i can workaround this, but the compare code
will not be as simple as
Op dinsdag 26 maart 2013 18:35:00 schreef Thierry Vignaud:
On 23 March 2013 13:31, Thierry Vignaud thierry.vign...@gmail.com wrote:
@thierry: i donno what you think of it, but imo:
A) fixing lstdetect would be the cleanest way (maybe not the
simplest)
B) perhaps in the comparing i can
On 20 March 2013 21:39, AL13N al...@rmail.be wrote:
@thierry: i donno what you think of it, but imo:
A) fixing lstdetect would be the cleanest way (maybe not the simplest)
B) perhaps in the comparing i can workaround this, but the compare code
will not be as simple as it should...
On 03/23/2013 08:31 AM, Thierry Vignaud wrote:
I've backported the needed changes.
I've tested it with USB hid, it worked.
Please test too (normal modules + xen).
Then I'll submit it
Working now, thanks.
On 23 March 2013 17:12, Frank Griffin f...@roadrunner.com wrote:
I've backported the needed changes.
I've tested it with USB hid, it worked.
Please test too (normal modules + xen).
Then I'll submit it
Working now, thanks.
What do you means?
- The current stage1 available on mirrors?
- The
On 03/23/2013 12:34 PM, Thierry Vignaud wrote:
On 23 March 2013 17:12, Frank Griffin f...@roadrunner.com wrote:
I've backported the needed changes.
I've tested it with USB hid, it worked.
Please test too (normal modules + xen).
Then I'll submit it
Working now, thanks.
What do you means?
-
Op dinsdag 19 maart 2013 18:53:07 schreef Frank Griffin:
On 03/19/2013 04:56 PM, AL13N wrote:
a module list of loaded modules with that hardware...
i think it might be this commit, but i'm wondering what's the difference
inbetween automatic loading and loading from the module box.
@tv
You could try:
- rebuilding drakx-installer-stage1 with reverting this commit,
- rebuilding drakx-installer-images with new drakx-installer-stage1
- then boot the new boot.iso or vmlinuz+all.rdz
Could you please elaborate on the first and part of the second step ?
There is a
On 03/20/2013 03:34 AM, AL13N wrote:
ok, i found out the issue... it seems that stage1 uses lst-detect and the
usbtable.gz file. and that file only contains '_' ...
the function i modified had not only effect for the modules.dep/filenames when
manually selecting, but also for the lst-detect
On 03/20/2013 12:34 PM, Frank Griffin wrote:
I'm confused.
I see your point: modules.dep and the actual driver module filenames
in /lib/modules use dashes in the names, while usbtable uses
underscores. So why does lsmod show underscores instead of dashes ?
Also, why do the two differ ? If
On 20 March 2013 08:34, AL13N al...@rmail.be wrote:
ok, i found out the issue... it seems that stage1 uses lst-detect and the
usbtable.gz file. and that file only contains '_' ...
the function i modified had not only effect for the modules.dep/filenames when
manually selecting, but also for
On 20 March 2013 17:50, Frank Griffin f...@roadrunner.com wrote:
I'm confused.
I see your point: modules.dep and the actual driver module filenames in
/lib/modules use dashes in the names, while usbtable uses underscores. So
why does lsmod show underscores instead of dashes ?
Also, why do
On 03/20/2013 11:25 AM, Frank Griffin wrote:
@tv
Am I correct in assuming that you meant:
1) Download the drakx-installer-binaries SRPM
2) rpm -ivh it
3) svn checkout the mdk-stage1 directory
4) revert the 7542 commit there
5) replace the mdk-stage1 directory in the binaries SRPM source
Op woensdag 20 maart 2013 12:50:06 schreef Frank Griffin:
On 03/20/2013 12:34 PM, Frank Griffin wrote:
I'm confused.
I see your point: modules.dep and the actual driver module filenames
in /lib/modules use dashes in the names, while usbtable uses
underscores. So why does lsmod show
On 03/20/2013 01:33 PM, Thierry Vignaud wrote:
That's because modules.alias enables to match through wildchars.
eg for ehci (see either /sbin/modinfo ehci_pci or
fgrep ehci /lib/modules/3.8.3-desktop-2.mga3/modules.alias):
alias pci:v104AdCC00sv*sd*bc*sc*i* ehci_pci
alias
Op woensdag 20 maart 2013 15:50:06 schreef Frank Griffin:
On 03/20/2013 01:33 PM, Thierry Vignaud wrote:
That's because modules.alias enables to match through wildchars.
eg for ehci (see either /sbin/modinfo ehci_pci or
fgrep ehci /lib/modules/3.8.3-desktop-2.mga3/modules.alias):
On 20 March 2013 20:47, AL13N al...@rmail.be wrote:
I see your point: modules.dep and the actual driver module filenames
in /lib/modules use dashes in the names, while usbtable uses
underscores. So why does lsmod show underscores instead of dashes ?
Also, why do the two differ ? If the
Op woensdag 20 maart 2013 21:20:14 schreef AL13N:
Op woensdag 20 maart 2013 15:50:06 schreef Frank Griffin:
On 03/20/2013 01:33 PM, Thierry Vignaud wrote:
That's because modules.alias enables to match through wildchars.
eg for ehci (see either /sbin/modinfo ehci_pci or
fgrep ehci
On 03/20/2013 04:22 PM, AL13N wrote:
not really, it just means that in the kernel - are mapped to _; modprobe
tools handle both cases, just modinfo reports the filename which can
include '-', but it can still handle both.
lspci and most tools just report it as it's really named (depending on
On 20 March 2013 21:22, AL13N al...@rmail.be wrote:
That's because modules.alias enables to match through wildchars.
eg for ehci (see either /sbin/modinfo ehci_pci or
fgrep ehci /lib/modules/3.8.3-desktop-2.mga3/modules.alias):
alias pci:v104AdCC00sv*sd*bc*sc*i* ehci_pci
Op woensdag 20 maart 2013 21:21:35 schreef Thierry Vignaud:
On 20 March 2013 20:47, AL13N al...@rmail.be wrote:
I see your point: modules.dep and the actual driver module filenames
in /lib/modules use dashes in the names, while usbtable uses
underscores. So why does lsmod show
Op woensdag 20 maart 2013 21:28:51 schreef Thierry Vignaud:
On 20 March 2013 21:22, AL13N al...@rmail.be wrote:
That's because modules.alias enables to match through wildchars.
eg for ehci (see either /sbin/modinfo ehci_pci or
fgrep ehci
On 03/18/2013 10:20 AM, Colin Guthrie wrote:
'Twas brillig, and Frank Griffin at 18/03/13 13:49 did gyre and gimble:
Trying a fresh install this morning (booting isolinux from grub), the
select your install type curses menu comes up, but the keyboard is
completely unresponsive.
Perhaps stage1
'Twas brillig, and Frank Griffin at 19/03/13 15:25 did gyre and gimble:
On 03/18/2013 10:20 AM, Colin Guthrie wrote:
'Twas brillig, and Frank Griffin at 18/03/13 13:49 did gyre and gimble:
Trying a fresh install this morning (booting isolinux from grub), the
select your install type curses
On 03/19/2013 12:15 PM, Colin Guthrie wrote:
'Twas brillig, and Frank Griffin at 19/03/13 15:25 did gyre and gimble:
Problem still present in last night's installer upload...
Were you able to try Thierry's suggestion?
My apologies, I must have missed it. I looked it up in the archives,
Op dinsdag 19 maart 2013 14:33:30 schreef Frank Griffin:
On 03/19/2013 12:15 PM, Colin Guthrie wrote:
'Twas brillig, and Frank Griffin at 19/03/13 15:25 did gyre and gimble:
Problem still present in last night's installer upload...
Were you able to try Thierry's suggestion?
My
On 03/19/2013 03:35 PM, AL13N wrote:
the patch removes the previous workaround that converts - in module filenames,
to _ . it's removed because if a module is selected manually, it's made from
filenames. so the - must match.
maybe if a module isn't selected manually, it comes from lstdetect or
Op dinsdag 19 maart 2013 16:53:46 schreef Frank Griffin:
On 03/19/2013 03:35 PM, AL13N wrote:
the patch removes the previous workaround that converts - in module
filenames, to _ . it's removed because if a module is selected manually,
it's made from filenames. so the - must match.
On 03/19/2013 04:56 PM, AL13N wrote:
a module list of loaded modules with that hardware...
i think it might be this commit, but i'm wondering what's the difference
inbetween automatic loading and loading from the module box.
iow: we need to find what module is actually the problem
Here we
Trying a fresh install this morning (booting isolinux from grub), the
select your install type curses menu comes up, but the keyboard is
completely unresponsive. There's no problem with the keyboard itself,
as it worked fine to navigate the grub menu to select isolinux.
Isolinux gives the
'Twas brillig, and Frank Griffin at 18/03/13 13:49 did gyre and gimble:
Trying a fresh install this morning (booting isolinux from grub), the
select your install type curses menu comes up, but the keyboard is
completely unresponsive. There's no problem with the keyboard itself,
as it worked
On 18 March 2013 15:20, Colin Guthrie mag...@colin.guthr.ie wrote:
Trying a fresh install this morning (booting isolinux from grub), the
select your install type curses menu comes up, but the keyboard is
completely unresponsive. There's no problem with the keyboard itself,
as it worked fine
32 matches
Mail list logo
