Hi!
> Have you had any progress on getting the kernel to detect the USB devices on
> the Asus VivoTab Smart ME400C?
> I'm replying to the thread about this
> https://lists.debian.org/debian-boot/2015/12/msg00066.html, but I'm unsure if
> you'll receive this email as such.
Nope, I didn't invest
I've been investigating a bit on where the devices are on Windows and I saw
that the Broadcom wifi is on the SDIO bus:
SD\VID_02D0&PID_4330&FN_1\3&18BDEB84&0&0
This device should be supported by the brcmfmac driver but it is not loaded
automatically and if I try to load it it does nothing, I'm gue
> I'll try to get the same dump under Debian to see if we are seing the same
> tables as Windows sees.
I have run the acpica-tools under Debian and I got the same 4 tables I had
under Windows plus a lot other tables, I have put a new tar available with
all the tables at:
http://www.manty.net/linu
> > The firmware appears to have set up the PCI root and ACPI tables
> > wrongly:
Just in case Windows had done some black magic or something, while reading
and trying to understand how this works (still no minimal idea on how all
this PCI/ACPI tables work), I came accross the acpica-tools and dum
First of all thanks for your reply. I have tested your suggestions with
unfortunately little luck.
First of all I can confirm that the machine doesn't hang like I thought it
did, the kernel runs Ok, which is great, however I cannot access the machine
as I don't yet have any net or keyboard or any
Hi!
A friend gave me this tablet which has a broken glass + digitizer so I
thought I could maybe make some use of it under Debian.
The device is a 32 bits Atom based uefi machine, so I got first jessie's
installer and then a weekly stretch build but on both of them I could get to
the first menu b
> I had used debmirror with that options:
> debmirror debian --nosource --host=ftp.fi.debian.org --method=http --progress
> --dist=etch --section=main,contrib,non-free,main/debian-installer --arch=i386
> --ignore-release-gpg
> What's wrong with that, had I missed some debmirror options?
I'd su
> Now that I check, Gnash has that feature already:
>
> Edit -> Preferences -> Player -> Start Gnash in pause mode
And is it activated by default? I think it would be good if that was the
case, as otherwise most people will not realize that this feature is there,
like it happened to you untill
> How long have you used each? (I assume you've used gnash a lot since you
> maintain it..) I've only tried each for a few hours myself, about once
> per month since January, as I use websites with flash that neither
> supports, but my general impression is that swfdec supports more sites,
> includ
> I did, a couple of days ago. As you say, debian-cd on gluck needs a cvs
> update of tools/boot/sarge/boot-powerpc. manty?
Sorry, my fault, I thought I had updated that already, but I hadn't, I have
just updated it right now, so today's build should be ok.
Regards..
--
Manty/BestiaTester -> htt
Hi!
I think I already told joeyh some time ago that I had already fixed this
and changed the scripts so that it is easier to select what we build
sarge_d-i with. So, sarge_d-i dailies are now built using sid instead of
sarge.
Regards...
--
Manty/BestiaTester -> http://manty.net
--
To UNSUBSCR
> OK. What size difference is there? It won't be huge (a few bytes per
> directory), but I'd expect it to be noticeable, especially on the
> businesscard image where we're short of space.
Well, it is difficult to mesure, I mean, cds change from one day to the next
one, The smaller difference I saw
> >Agreed. Feel free to commit a fix.
> Done.
I have applied your changes to gluck before today's build, but I do not see
any important changes in sizes :- at least comparing today's build with
yesterday's and I have checked them and there is no TRANS.TBL files on them.
Regards...
--
Manty/B
Hi!
I have two uncommited changes in gluck's debian-cd that we where testing to
see if they solved some issues with sparc cds, I'd like to know if they did
solve the issues and thus I should commit them to debian-cd cvs, or if I
should remove them as they don't solve anything. These are the change
Hi!
Today we have produced our first set of mipsel cd images of testing, they
have not yet been tested, so we need people with cd equiped mipsel machines
to test the new images, they are available at the usual place, which for
mipsel is:
http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/mi
> having this reaction, and I think the result of testing outweighs the
> vote. Would it be ok to go back to the old (klowner) logo?
Yes, for me the old was better anyway, in fact, next time we vote for a logo
I think people should see a full screen with the logo and our boot message
and everythin
> Anyway, I'm concerned that this will probably not fit on a netinst iso
> image. The current netinst iso is 106 mb (that includes the existing
> 2.6.5 kernel udebs; it's under 200 mb without them). To add full 2.6
> support, we would need to add a vmlinux file and an initrd for the 2.6
> kernel (3
Hi!
Some time ago somebody asked on our lists why didn't we made our cds behave
like the Windows cd do, in the sense that if you forget the cd in the drive
while rebooting the machine, and this one boots from the cd, if the user
doesn't touch the keyboard in a certain time, the boot continues from
> > - Is is ok to have bootloaders for i386 listed but not for others?
> I think that most bootloaders are pulled in by debootstrap, so appear on
> tasks/base-sarge. lilo and grub are an exception as debootstrap installs
> neither.
Anyway, this boot loaders should only be listed in the i386 arch,
> > The CD should only boot on keypress, like the Windows NT (ugh!) CD does:
> >Please press any key to start from the Debian GNU/Linux CD,
> >otherwise normal BIOS boot order will continue in seven seconds.
> You don't say what cd you're using, but the current daily builds only
> boot on a
> Looks like we need to add these to discover-data and to usb-discover.
> I've added it for usb-discover, at least, which should be enough to make
> the memory stick work.
When will that end up in the cds? I'd like to do the install using for my
public talk using a stick and wireless :-)
> What i
Today I got at last a machine that is able to boot from USB, so I said, hey,
let's try installing from USB, but unluckily it didn't work.
Machine boots from our image and debian-installer is launched, but when it
get's to the part where it tries to gather the stuff from the iso image it
fails to f
> > attempt to access beyond end of device
> > 01:00: rw=0, want=820#, limit 8192
>
> Well, this sounds like you have a bad CD or ISO. Try another one.
It looks like the cds since the 6th have been having this problem, the d-i
images are too bloated for everything to fit in the ramdisk, we alread
> If we can only build one set, they should be built against sid's d-i for
> now, I think.
We could build against the two, but it takes a really long time to build
because of jigdo, so I think it is better to build just for the one we wan't
people to test, besides, if we provide several, people te
> Well I saw "http://gluck.debian.org/cdimage/testing/"; mentioned somewhere
> and "netinst/i386/" seemed the relevant sub-directory hierarchy under that
> for what I wanted.
That used to be the old place for things, but we have reorganized things
around and now it is not, I had left symlinks in p
Hi!
I thought I had added this info, but I've looked now and I cannot see it
here, so I'm sending it "again".
Well, the thing is that I have managed to reproduce this in two more
machines, and I have gathered enough info to get the pattern that makes this
bug appear.
This bug appears on every ma
> Full CD and DVD can be done once a week.
That is how we've been doing it all the time, but changes in building (I
suppose it was jigdo, but also hard could have helped) have increased the
time it takes a lot, so now I think we are only able to build 5 or 6 a day,
not all the 11 like we used to d
Hi!
I'd like to let you know that we now have netinst bootable images for hppa,
with that one, we are having 5 arches with bootable cds, that is however
only less than half of the arches we have, so we still miss a lot of them.
I'd like to thank Thorsten Sauter for his work on hppa (as well as ot
> Maybe we could send out a mail to everyone who filed an install report
> of failure, and see if they can reproduce the failure, and also make
> sure they didn't produce a CD with a .iso file on it or similar mistake.
Sounds like a good idea, but we should have tested cd images before that, if
yo
Hi!
The recovery of the functionality of our servers is taking long, we still
don't have gluck.debian.org/cdimage back, however that doesn't mean we have
stopped making images, in fact, we are now able to produce DVD images as
well.
While we don't recover gluck.debian.org/cdimage you can find the
> Just the BETA-1 20031109 release doesn't boot.
That is really weird, can you tell the message it outputs?
Not that I expect it to tell us much, but...
Thanks for the info, I knew about the other cases, I was going to ask all of
the known cases with problems to test the image I was building on t
> > isolinux just doesn't work with all BIOSes. Knoppix has either
> > syslinux or a different version of isolinux.
Knoppix uses in all their versions up to now a floppy emulation boot, with a
1.44 floppy image.
> I have the same problem in my ASUS TX97-X mainboard BIOS (AWARD), but
> only with
> Right, we'll want to add help screens to syslinux for all of our images
> in any case. I think I understand now, isolinux uses its own help
> screens which it reads from the CD, and these come from debian-cd (for
> now..), but we can control the rest of them.
That's it.
> I don't particularly w
> > I think that the main problem from the d-i team's perspective is that
> > all the daily cds and the cds for beta 1 use isolinux. So when users
> > come to us who cannot boot from isolinux, we have no alternative except
> > boot floppies or the monthly full cd builds. Any approach that provides
Umm, seems like we go again for the same discusion, ok, I've been gathering
some old links to try to shorten this.
The isolinux / multiboot / boot floppy emulation (syslinux) decision was
already discussed for woody, at that time I was building unofficial images
for all woody's arches, and I also
Package: partconf
Severity: important
Hi!
When installing into my of my systems which has a 10 gigas disk I found out
a really weird thing, as the disk has 8 partitions and only one was offered
by partconf, the size of this partion was also not ok.
The disk has this partitioning:
Disk /dev/hda:
Hi!
Like for powerpc, i386 has also stopped building, we are trying to download
these files from sjogren's repository for the cd:
cd_drivers-image.img
cdrom-image.img
cdrom-initrd.gz
floppy-image.img
floppy-initrd.gz
net_drivers-image.img
netboot-initrd.gz
vmlinuz
while we have these there:
[
Hi!
I was revising now the powerpc cds which hadn't built in the last days
(sorry for not doing it before, I've been busy and not too well) and found
out that the two files (vmlinux and cdrom-initrd.gz) we are using from the
d-i repository (Thorsten's repository) are not there, and instead I have
Peter, please reply to the lists, I don't know a thing about ia64 and people
on the lists can help us with this kind of things ;-)
On Oct 07 2003, Peter Chubb wrote:
> >>>>> "Santiago" == Santiago Garcia Mantinan <[EMAIL PROTECTED]> writes:
>
> Sa
Thanks to the help of Richard Hirst who has made the script to make ia64 cds
bootable and shown Jeff Bailey how to build debian-installer for ia64, Jeff
has built a debian-installer image for ia64 and I have built both netinst
and businesscard cds, now we need somebody that can test the cds to see
> to increase the size of the ramdisk to 16M (when 32M ram is installed),
> that way you can install on a system with 32M of ram.
Umm, what are the reasons so use a ramdisk of a fixed size when there is
tmpfs that does the same thing and doesn't require fixed sizes?
Regards...
--
> Maybe it needs the debian-cd package or something such ?
Yes, well, the problem with this is how to make the cd bootable, for that
there are scripts on debian-cd/tools/boot/sarge/ there should be one for
ppc, once we have a working script for there and somewhere where one can
dowload ppc images
Hi!
Today I upgraded cd creation stuff on gluck and rebuilt the i386 images,
this weekend all other arches will be rebuilt, so if somebody wants to have
a look at the i386 images and try to see if something is wrong, it would be
great. The main changes are that I'm now using debootstrap 0.2.2 and
Hi!
I'm happy to announce that we'll be weekly creating netinst cds for testing
(the future sarge distribution), this cds are made using Tollef Fog Heen's
daily images of the debian-installer, like the full images we are currently
building.
The images will be accesible by the full ones, this is,
> | First of all, what do we want to build, the smaller ones 45 Mb right now,
> | or the installable from cd ones, 83 Mb.
>
> Why not both?
It's ok with me, we only need good names for them so that people know what
to download ;-)
> This could be fixed by having packages not using the normal
> s
> because they depend on libdebian-installer3 and that one is not on sarge but
Same happens with libparted1.6-0 which is also needed and is not in sarge.
I'm happy to see that the other problem I was going to report now,
autopartkit depending on di-fake, is already fixed.
Well, I have hacked my
Hi!
I've been trying lately on getting barebones Sarge cds for easily allowing
people to test d-i, today I thought I had made it, and in fact I believe
I've done it, but checking the results I found out that some udebs were
missing, let's explain the problem.
We have some udebs on the debian-inst
> I'm trying to get CD installs to work, and right now I can't do ...
> anything, really, since libc-udeb is missing, so I'm stuck with the
> ultra-reduced libc from the floppy I boot from.
Well, the libc-udeb problem has been worked out severall days ago via hacks
on deiban-cd and while we didn't
I built the last images of woody for alpha on the 9th of may, I believe they
have the loop bug on the base-config, however if you still want them they
are available via rsync, http or ftp on alpha.trasno.net. I could also try
to build newer ones without that bug if you want them.
Regards...
--
M
I was testing woody cds on a alpha and though the cds boot ok I was not able
to install, this was because the kernel on trying to mount the root fs it
first tried fat related fs failing, and then tried to mount it as ufs
failing and saying that it was not able to mount it.
I realy don't know whic
Package: boot-floppies
Version: 3.0.22
Severity: normal
Hi!
First of all it would be good that the B50 machine is tagged as a chrp
machine and not as a prep machine on the Boot Floppies doc.
This is the log of trying to boot a B50 machine with the kernel from Boot
Floppies 3.0.22 using the chrp
Hi!
First of all, sorry for the crosspost, but I think that the message belongs
to all the three lists.
I'm trying to see if woody will work on one of this machines, they are
powerpc based, the one I have access to has a serial console, cdrom and
floppy.
I read the Boot Floppies documentation w
> I'm curious. Does PLIP work in the woody boot-floppies?
Well, last time I tried it needed to make some steps by hand.
> Are there things we could do to make installation via PLIP network
> easier?
Yes, if it has not been corrected still, make a plip device configurable
under the normal insta
> A package for such a small file seems like overkill. How about I put it
> in base-config and whoever we find who understands how it works (You, or
> if not you, I contemplate looking up the original author in the cvs
> logs..) can just maintain it from there. Everyone has commits to
> base-confi
Hi!
I have been asking about termwrap for almost a month now, since my first
real tests of our cvs code, on the 26 of April, and still this is unsolved
but we are suppose to be on the way to solving this...
As I see that some people have still not got it, I'm putting here again the
recent histor
Hi!
I had experienced one of problems that Jordi also has on his install, I knew
it was related to the 8139too module, so I left it aside and used rtl8139
instead.
I have traced the thing and I have found that the problem is in dbootstrap's
util.c, we have a function called execlog that has this
On May 16 2001, [EMAIL PROTECTED] wrote:
> Use dhcp-client instead of pump
I was just wondering... why do we change from pump to dhcp-client?
Does dhcp-client have something really usefull that pump doesn't?
Regards...
--
Manty/BestiaTester -> http://manty.net
--
To UNSUBSCRIBE, email to [
Hi!
About this stuff, the guys at 194.98.93.142 seem to be accesing some stuff
of this spanish site, and the apache placeholder has put them in our way, I
have replied to them in the message sent also to the list that debian has
nothing to do with that machine (atlas.brainstorm.fr) and that they
Hola!
> Desde la dirección 194.98.93.142 (algo sobre "debian y apache", ver página
> web anexa) se realizan varios intentos diarios, presumiblemente de modo
He estado mirando dicha página y parece una máquina con la distribución
Debian GNU/Linux, pero que no tiene nada que ver, al menos que yo s
> setenv("LANG", _("C"), 1);
> add_modules_from_floppy();
> Anybody know why we're setting the LANG to 'C' here, modconf keys off that in
> source_eval().
No, this is not the problem, in fact we are not setting it to C we are
setting it to whatever the translator has put there, wich is suppo
Hi!
I have asked this before, but still no compromise has been achieved on it.
Are we planning on using termwrap or will we be switching to another new
scheme?
If we are gonna continue using terwrap for setting the LANG and LC variables
and all terminal settings in general... Could we please fi
> (What's "Galacian" out of curiousity?)
Galician, not Galacian, or Galego as it is said in Galician is a language
spoken here in Galicia, on the north west of Spain, Galician and Portuguese
are brothers, they once were the same language, Galego-Portugués.
Jacobo adds: There is another Galicia b
> > I have removed fdutils because the interactive setup it has was breaking the
> > install, as aj had noticed when building debootstrap 0.1.7, has anybody
> > noticed the maintainer about this? shall I do it?
> yes, please file a serious bug against fdutils. It is preventing us from making
> a
Hi!
Yesterday I made my first complete install of debian woody using the new
boot floppies, well, my customiced version of them, so, I'd like you to
comment the changes I have done fot achieving this and if you agree with
them I'll do my first commit to our cvs.
Well, I have done this on a galic
> Debconf should fall back to dialog when it determines slang is not going
> to work.
Yes, it does I realised later when instead of trying to fullfill his needs I
just let it continue :-)
> Anyway, it is basically a bug in debconf that it half-defaults[1] to the
> slang frontend. The slang front
The inclusion of fdutils on debootstrap causes it to end with an error, as
fdutils like to get an answer to the questions it makes when configuring it.
What does this leads to?
Well, in extract_base and after marking the system as unconfigured we ask
for the result of debootstrap and if it gave
> I guess that the declaration/debiandoc.decl file should be added to cvs or
> it's reference be removed from documentation/install.sgml ?
You can also install debiandoc-sgml and then you will have it ;-)
BTW: have you run "make check" first?
Regards...
--
Manty/BestiaTester -> http://manty.ne
> save off /target/etc/modutils before calling debootstrap, fix it after calling
> debootstrap as it gets trampled by the modutils package.
For what I see you are not talking about modutils overwriting
/target/etc/modutils but /target/etc/modules, well, after a talk with
Wichert yesterday he has
> Please somebody enlighten me about this, because I want to produce a
> bootable *and* installable woody CD set, but without base tarball it is
> very hard to do...
You can visit http://lists.debian.org/debian-boot-0104/msg00846.html to
read a message I sent to the list after testing the instal
Hi!
After debugging busybox enough so that I could use the cvs version to
build installable floppies, so here is my report and also some questions I'd
like to know the answer, so that I could continue trying to inprove boot
floppies.
When installing the base packages there seems to be a problem
> P.S. I should have the above bug fixed momentarily. Thanks for
> the report.
Erik has already applied a preliminary patch I submited to him, it is
already on cvs, however I like my second patch better. I also have reported
to Erik a malloc missing on chmod wich causes segfault, this does not s
Hi!
Well, I'm new to boot floppies, have been looking at them the last few days
to see if I can make it install on cds and I think I'm going on the right
direction, I already have an small patch, really ridiculous one, I'm
putting it at the end of the message, I could not fully test it as I have
72 matches
Mail list logo
