Re: Hello! from a newbie+ problems with debian for amd64+can't boot debian for i386 on amd64 from cd+can't extract sbm.bin from cd

2005/11/29, Daniel Foote <freefoote@gmail.com>:

Hello...

Sorry about that... I actually meant to post it to the list, as well
as you, but that didn't happen.

If you go to the terminal during the install, I've specified some
commands you can type.

The "dmesg" command will list the kernel's message buffer. You can see
what messages the kernel has generated and get an idea of what
hardware was detected. The kernel puts messages here as it detects
hardware and other things related to the operation of the kernel. To
make dmesg easier to see, use the command "dmesg | less" and then use
pageup/pagedown/cursorup/cursordown to browse through it, and "q" to
exit that. In this you're looking for lines with "eth0" and "eth1" in
them.

As to the modprobeing - "modprobe" is a command used to load/remove
modules from the kernel.

"modprobe <modulename>" will insert the module into the kernel, and
usually detect the hardware that maches the module. You can confirm
that it went it by looking at the last lines of "dmesg". You should
see some additional messages.

"modprobe -r <modulename>" will remove a module. You may see
additional messages in dmesg about it.

To see what modules are in the kernel, you can use "lsmod". And then
try to find the right modules to remove. Note that the last column
indicates what modules "depend" on that module, ie; the dependancies
have to be removed first before that module can be removed.

In this case, to get the install to work, I removed several modules
related to ieee1394, in the other that they depended, and then
inserted the "forcedeth" module.

If you can't unload a module, the hardware it drives is in use or the
another module depends on that module.

I'll say at this point, that I don't recall all the modules that I had
to fiddle with to make it work. As you get some experience with Linux,
you'll get a feel for how this all works.

Anyway, I hope that is of some help.

(And I'll repost my last message to the list, for the record. So
you'll get it again, sorry.)

Have fun!

Daniel.

On 11/29/05, Martin Baldan < martinobal@gmail.com> wrote:
> Hello, Daniel!
>
>  Thanks for your tip. It seems very useful. Unfortunately I'm stilll too
> much of a beginner. Could you please give me a more detailed/verbose
> explanation? I mean, what does it mean to "peruse dmesg", to "modprobe" and
> to "-r"? Do you recall the specific commands you used?
>
>  take care,
>
>  Martin
>
> 2005/11/28, Daniel Foote <freefoote@gmail.com>:
> > Hello...
> >
> > Just to add my little bit...
> >
> > I recently bought a new machine, which was NForce4 based, like yours.
> > When I did my net install, it could not get an address (DHCP, from a
> > machine on my internal net). I didn't set it manually.
> >
> > Instead, I went to a terminal (hit CTRL+ALT+F2 during the install).
> > Perusing dmesg revealed that eth0 was the ieee1394 (firewire) ethernet
> > - which I was not using.
> >
> > modprobe -r'ed the appropriate modules to make it free eth0, and then
> > I modprobed "forcedeth", which registered itself as eth0. After that,
> > CTRL+ALT+F1 back into the install, and retry the automatic network
> > setup. Worked perfectly after that.
> >
> > I don't recall if forcedeth was already loaded as eth1 - if so, just
> > modprobe -r that as well, and then reinsert it once the eth0 slot is
> > free.
> >
> > (I was impressed that I could do this - I can't think of too many
> > other installers that would allow sorting out of a problem like this
> > that early in the install).
> >
> > Hope this helps someone else...
> >
> > Daniel Foote.
> >
> > On 11/28/05, Martin Baldan <martinobal@gmail.com> wrote:
> > > Hi!
> > > >>1) Why don't I have permission to extract the " sbm.bin" file? How can
> I
> > > >> solve that?
> > > >Don't think its a good way to trying to extract something, may
> > >
> > > >you've burned your cd in a wrong way. Did you setup your
> > > >burning software in the correct way to create a bootable image?
> > > Definitely! A while later I realised I was dumbly copying
> > > the ".iso" file to a cd instead of burning an image.
> > > Besides, I was trying to extract the file into the cd-rom instead of,
> say,
> > > the desktop.
> > > Anyway, I've finally burnt the cd and it more or less works
> > >  (though I had to type "linux26",otherwise it wouldn't recognise my
> ethernet
> > > card) Now the problem is that I can't connect to the mirrors to complete
> the
> > > installation (it says "temporal error").
> > >
> > > I had to set the internet configuration manually, so I may have done a
> > > mistake, but I don't know where.
> > > I'm re-installing the amd64 version, which at least can set the internet
> > > configuration automatically,
> > >
> > >  and download nearly all packages (except security updates, among others
> > > !!).
> > >  >if you are a real newby, you may wait until december. As I knew debian
> > > etch
> > >
> > >
> > >
> > >
> > > >should be finished in december, and there amd64 should be one of the
> > > standard
> > >  >supported systems.
> > >
> > > That's cool! I thought it would take a bit longer.
> > > Anyway, I have nothing better to install on my drive,
> > >
> > >  so I'll try to get used to Debian now,
> > > and then, when Etch is released, I'll give it a try.
> > >
> > > Thanks for your help!
> > >
> > > Regards,
> > >
> > >
> > >
> > >
> > >
> >
>
>