linux-apus-user

Re: USB support in APUS kernels?

[Geert U. <ge...@li...>]

On Sat, 14 Jun 2003, Bj=F6rn Johansson wrote:
> There is no USB support in the APUS kernels, correct?
> If this is true, how come there exist a modules.usbmap
> in the archive?

I think it's created by depmod.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m6=
8k.org

In personal conversations with technical people, I call myself a hacker. =
But
when I'm talking to journalists I just say "programmer" or something like=
 that.
							    -- Linus Torvalds

USB support in APUS kernels?

[Björn J. <kh...@te...>]

Hi!

There is no USB support in the APUS kernels, correct?
If this is true, how come there exist a modules.usbmap
in the archive?


-- 

Bj=F6rn Johansson "Debian rocks!!"

Any progress?

[Björn J. <kh...@te...>]

Will there be a 2.6 APUS kernel available in the future?

I REALLY would like a better kernel. I'm using the 2.4.18
kernel right now, and I can't even go online with this
one. I almost managed to get online with the 2.4.4 kernel,
but it feels slower than the 2.4.18, and why use an
old kernel?

It's VERY quiet on the LinuxAPUS mailinglist..
Any progress on drivers or something?


-- 

Bj=F6rn Johansson "Debian rocks!!"

Re: Highway USB support in APUS kernels?

[Stefan N. <Ste...@mh...>]

And how about mediator? I know this has been answered before, but I can't
find the email, sorry..
Mediator/Voodoo would be really neat!

//shoe - UNIX _IS_ user friendly, its just picky about who its friends are.=
=2E.

On Tue, 10 Jun 2003, Bj=F6rn Johansson wrote:

>
> Hi!
>
> Are there any drivers for the HighwayUSB for Linux available
> somewhere? If not, will there ever be?
>
>
> --
>
> Bj=F6rn Johansson "Debian rocks!!"
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
> thread debugger on the planet. Designed with thread debugging features
> you've never dreamed of, try TotalView 6 free at www.etnus.com.
> _______________________________________________
> Linux-APUS-user mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-apus-user
>

Re: Highway USB support in APUS kernels?

[Geert U. <ge...@li...>]

On Tue, 10 Jun 2003, Bj=F6rn Johansson wrote:
> Are there any drivers for the HighwayUSB for Linux available
> somewhere? If not, will there ever be?

Anyone who has the hardware and specs?

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m6=
8k.org

In personal conversations with technical people, I call myself a hacker. =
But
when I'm talking to journalists I just say "programmer" or something like=
 that.
							    -- Linus Torvalds

Highway USB support in APUS kernels?

[Björn J. <kh...@te...>]

Hi!

Are there any drivers for the HighwayUSB for Linux available
somewhere? If not, will there ever be?


-- 

Bj=F6rn Johansson "Debian rocks!!"

Re: APUS dosn't recognise my BlizzPPC-SCSI HDs

[Oliver R. <ol...@fu...>]

Hi Christoph,

On 06-Jun-03 18:22:33, Christoph Gutjahr wrote:

>> I think you need to add "nobats" (minus quotes) to the bootstrap
>> command-line, IIRC, to allow the BlizzPPC SCSI support to work.  At
>> least, that's what I use here, and everything is fine (my root partition
>> is on a SCSI drive).  I'm sure I remember reading that nobats was
>> required, but can't remember where.

> Thanks for the hint. I'm one step further now (it *does* recognise my
> drives), but a new problem appeared.
>
> The kernel recognises the drive(s), but it gets stuck in an endless loop
> as soon as it tries to "identify" the first drive in the chain. Lots of
> error messages
> (quote: "Duh? Bad things happening in the NCR driver"). It's not a
> problem with a specific HD, I tried both.

Hmmm... Can't say I've ever had that problem :(

> Could you tell me how you configured the node that your SCSI drive is
> connected to is configured in the BPPC early startup menu? I've got no

I'm not sure if these have any effect on LinuxAPUS, but I have both
the SCSI and NCR SCSI patches disabled (in the system section).  For
the SCSI section I have everything set to auto.  However, for the SCSI
IDs that I'm not using, I have manually set those all to NO LUN, so
those IDs aren't scanned - figured it might speed things up.

> idea about all those settings. What kernel parameters are you using?
> Thanks in advance.

I've absolutely no idea, sorry :(  I'm using one of the older kernels -
IIRC, it's the same one that was supplied on an Amiga Active CD-ROM
some time ago (possibly 2.2.10).  I've had nothing but problems with
the 2.4 kernels, so I just stick with the old one :)  I don't use
Linux much anyway - just occassional testing with Mozilla and Opera.

-- 
 Oliver Roberts  -  http://www.oliver-roberts.co.uk/  -  ICQ: 34640231

 Pace 56 Solo mailing list  ==>  http://groups.yahoo.com/group/56solo/

Re: APUS dosn't recognise my BlizzPPC-SCSI HDs

[Christoph G. <C.G...@gm...>]

Hi Oliver!

> I think you need to add "nobats" (minus quotes) to the bootstrap
> command-line, IIRC, to allow the BlizzPPC SCSI support to work.  At least,
> that's what I use here, and everything is fine (my root partition is on
> a SCSI drive).  I'm sure I remember reading that nobats was required,
> but can't remember where.

Thanks for the hint. I'm one step further now (it *does* recognise my drives),
but a new problem appeared.

The kernel recognises the drive(s), but it gets stuck in an endless loop as soon
as it tries to "identify" the first drive in the chain. Lots of error messages
(quote: "Duh? Bad things happening in the NCR driver"). It's not a problem with
a specific HD, I tried both.

Could you tell me how you configured the node that your SCSI drive is connected
to is configured in the BPPC early startup menu? I've got no idea about all
those settings. What kernel parameters are you using? Thanks in advance.

Regards
-- 
Christoph Gutjahr - c.g...@gm...
Gutjahr's Amiga Pages: http://gutjahr.free.fr

Re: APUS dosn't recognise my BlizzPPC-SCSI HDs

[Oliver R. <ol...@fu...>]

Hi Christoph,

On 06-Jun-03 13:01:46, Christoph Gutjahr wrote:

> I'm new to this list and I hope this is not a FAQ ;-)
>
> I tried to install LinuxAPUS recently, using the 2.2.10-000927 kernel and
> the latest version of boothack (both downloaded from the sourceforge
> site). I used the ramdisk images (both the test image and the RH
> installer image) from the AmigaFormat CD.
>
> My Setup:
>
> BlizzPPC 68040/25 + 603/210, SCSI, 32 MB, BlizzardVision, AmigaOS 3.9
> Drives: 2x4.2 GB SCSI HD (ID0, ID1), SCSI CD-ROM (ID4, terminated).
>
> According to the supplied readme, the kernel supports my SCSI-host. I
> prepared two partitions (LNX\00 and SWP\00, as described in the docs) and
> tried to boot using this commandline:
>
> bootstrap --apus -k vmlinux -r ramdisk.image.gz root=/dev/ram
> video=pm2fb:mode:800x600-60
[...]
> Any hints?

I think you need to add "nobats" (minus quotes) to the bootstrap
command-line, IIRC, to allow the BlizzPPC SCSI support to work.  At least,
that's what I use here, and everything is fine (my root partition is on
a SCSI drive).  I'm sure I remember reading that nobats was required,
but can't remember where.

-- 
 Oliver Roberts  -  http://www.oliver-roberts.co.uk/  -  ICQ: 34640231

 WarpBMP.datatype  ==>  http://www.nanunanu.org/~oliver/warpbmp.html

APUS dosn't recognise my BlizzPPC-SCSI HDs

[Christoph G. <C.G...@gm...>]

Hi!

I'm new to this list and I hope this is not a FAQ ;-)

I tried to install LinuxAPUS recently, using the 2.2.10-000927 kernel and the
latest version of boothack (both downloaded from the sourceforge site). I used
the ramdisk images (both the test image and the RH installer image) from the
AmigaFormat CD.

My Setup:

BlizzPPC 68040/25 + 603/210, SCSI, 32 MB, BlizzardVision, AmigaOS 3.9
Drives: 2x4.2 GB SCSI HD (ID0, ID1), SCSI CD-ROM (ID4, terminated).

According to the supplied readme, the kernel supports my SCSI-host. I prepared
two partitions (LNX\00 and SWP\00, as described in the docs) and tried to boot
using this commandline:

bootstrap --apus -k vmlinux -r ramdisk.image.gz root=/dev/ram
video=pm2fb:mode:800x600-60

But the kernel doesn't recognise my drives: It seems to be searching on the SCSI
bus, as I get the following output when the kernel tries to initialise my
hardware:

scsi0 : disabled or bad target 0 lun 0
scsi0 : disabled or bad target 1 lun 0
scsi0 : disabled or bad target 2 lun 0
scsi0 : disabled or bad target 3 lun 0
scsi0 : disabled or bad target 4 lun 0
scsi0 : disabled or bad target 5 lun 0
scsi0 : disabled or bad target 6 lun 0

When I boot with the RH installer ramdisk image, the installer complains that I
don't have any drives connected.

Any hints?

Regards
-- 
Christoph Gutjahr - c.g...@gm...
Gutjahr's Amiga Pages: http://gutjahr.free.fr

Supported USB cards

[Björn J. <kh...@te...>]

Hi!

Does anyone know if there are any USB cards that work together
with any LinuxAPUS kernels together with Debian(PPC).
Like for example: HighwayUSB/AlgorUSB.


-- 

Bj=F6rn Johansson "Debian rocks!!"

Re: Olivetti printer refuses to work with Debian :(

[Daniel P. <cor...@ho...>]

Take a look at: LinuxPrinting.org to see if your printers supported. If so 
its just a case of installing cups and the linuxprinting.org drivers(package 
is called foomatic IIRC) and adding the printer to cups with the webbrowser 
interface.

Daniel Palmer

_________________________________________________________________
Surf together with new Shared Browsing 
http://join.msn.com/?page=features/browse&pgmarket=en-gb&XAPID=74&DI=1059

Olivetti printer refuses to work with Debian :(

[Björn J. <kh...@te...>]

Hi!

I'm using a precompiled APUS kernel 2.4.18, which I have downloaded
from the APUS homepage. Is there printer support in the kernel?
I have an Olivetti JP 150WS together with a standard HP Deskjet
driver. When I've selected a HP driver within OpenOffice and trying
to print out a testpage, I get no connection to the printer.
It works perfectly with AmigaOS3.1, but I just can't get it to work
under Debian3.0. Do anyone here know how I can fix this?
I'm a total newbie when it comes to printers together with Linux :(.


-- 

Bj=F6rn Johansson "Debian rocks!!"

Re: Debian finally works!!

[Bartosz S. <baz...@po...>]

Hello Alan,

On 30.04.03, you wrote:

> lack of voltage perhaps due to your larger RAM modules... maybe thats why

> Phase5 specced 128Mb maximum? :-)
>  
>> So now we can note that Debian works on following hardware :)

> well, of course it does.. my 603e@240 060@50 has been a long Linux/debian

> running system ;-)

> PS perhaps i should add this form of info to FAQ...as in 'my system is 
> unstable'?

Go ahead ;). I couldn't  find information when having troubles, so maybe
someone will be more lucky :)

Regards
-- 
Bartosz (Bazant) Sokolowski
A1200T PPC603@210, 060@50, 192MB RAM, 
BVision, HD 30GB, FastATA etc. :)


----------------------------------------------------------------------
Dla tych, co sie cenia... >>> http://link.interia.pl/f1713 

Re: Kernel 2.4.13 and modules.deb

[Alan B. <A.L...@lb...>]

hi,

> Hello,
> 
> I use 2.4.13 kernel from APUS site and during boot I see that Woody cannot
> find lib/modules/2.4.13/modules.deb 
> It's quite obvious since such file isn't included in kernel's archive.
> Where can I get it? Or how can I create it myself?

modules.deb or modules.dep ?

if the former...its most likely some debian package thing - you didnt 
install kernel via debian package, thus the file isnt there - ignore 
warning.

if the latter, then its because the dependency list hasnt been made,

as root, run "depmod -a"

alan

Re: Debian finally works!!

[Alan B. <A.L...@lb...>]

hi,

> correctly only if I remove '60nsram' from bootstrap. This is quite strange
> since I can set memory controller of BlizzPPC to fastest possible mode by
> "setmemmode" command and run Workbench (Quake in window and RC5 client) for

this is well known historically. the timings of AmigaOS and its memory 
access speeds arent as demanding. Linux really does push more stuff 
through the hardware

> several hours with no problems! The second thing is powering the PPC card.
> Without bootstrap's 60nsram Debian worked basically fine but some strange
> opses happened from time to time. I checked voltage at BlizzPPC fan
> connector - had ~4.57V :( I did some powering tuning to my tower system and
> I achieved ~4.92V and Debian Woody with kernel 2.4.13 seems to work fine :)

lack of voltage perhaps due to your larger RAM modules... maybe thats why 
Phase5 specced 128Mb maximum? :-)
 
> So now we can note that Debian works on following hardware :)

well, of course it does.. my 603e@240 060@50 has been a long Linux/debian 
running system ;-)

Alan

PS perhaps i should add this form of info to FAQ...as in 'my system is 
unstable'?

Kernel 2.4.13 and modules.deb

[Bartosz S. <baz...@po...>]

Hello,

I use 2.4.13 kernel from APUS site and during boot I see that Woody cannot
find lib/modules/2.4.13/modules.deb 
It's quite obvious since such file isn't included in kernel's archive.
Where can I get it? Or how can I create it myself?

Regards,
-- 
Bartosz (Bazant) Sokolowski
A1200T PPC603@210, 060@50, 192MB RAM, 
BVision, HD 30GB, FastATA etc. :)


----------------------------------------------------------------------
Dla tych, co sie cenia... >>> http://link.interia.pl/f1713 

XWindow speed... hard drive speed..

[Bartosz S. <baz...@po...>]

Hello,

I installed XWindow system (glint driver) on my Debian Woody (2.4.13
kernel) and I'm quite dissapointed with the speed of WWW Browsers (Galeon
and Mozilla). Basically they work much SLOWER than Voyager or AWEB on Amiga
side!! Is it normal?? Can any speedup be achieved? 
Another thing is hard drive speed. Since plain A1200 IDE controller is slow
and CPU hungry how much faster in practice a SCSI drive is?? Theoreticly
SCSI is few times faster and consumes very little of CPU time. Any
comments?

Regards,
-- 
Bartosz (Bazant) Sokolowski
A1200T PPC603@210, 060@50, 192MB RAM, 
BVision, HD 30GB, FastATA etc. :)


----------------------------------------------------------------------
Dla tych, co sie cenia... >>> http://link.interia.pl/f1713 

Debian finally works!!

[Bartosz S. <baz...@po...>]

Hello,

Some time ago I was suffering from troubles installing Debian and having
strange kernel opses and panics. At the moment I think the problems are
solved :)! The main cause was RAM speed. Debian on my system works
correctly only if I remove '60nsram' from bootstrap. This is quite strange
since I can set memory controller of BlizzPPC to fastest possible mode by
"setmemmode" command and run Workbench (Quake in window and RC5 client) for
several hours with no problems! The second thing is powering the PPC card.
Without bootstrap's 60nsram Debian worked basically fine but some strange
opses happened from time to time. I checked voltage at BlizzPPC fan
connector - had ~4.57V :( I did some powering tuning to my tower system and
I achieved ~4.92V and Debian Woody with kernel 2.4.13 seems to work fine :)

So now we can note that Debian works on following hardware :)

Regards,
-- 
Bartosz (Bazant) Sokolowski
A1200T PPC603@210, 060@50, 192MB RAM, 
BVision, HD 30GB, FastATA etc. :)


----------------------------------------------------------------------
Dla tych, co sie cenia... >>> http://link.interia.pl/f1713 

Fw: Problems booting Debian on new hardware

[<baz...@po...>]

 Hi!

By accident I forgot to send the answer also to the ml, so here it goes...
Anyone any comments?

> add 'nobats' to your bootstrap line. also, use kernel 2.4.4 or 2.4.13

I have nobats at bootstrap... kernel 2.4.4 not tested - I'll try it :)

> what speed do you have set on the board ('escape menu')? what speeds are
> the SIMMs. you are better off using matched sizes and speeds!

All SIMMs seems to be 60ns. At the moment I have 60ns at 'escape menu' but
I tried different variants. On AmigaOS ALL variants works well.

> IIRC, the Blizzard can only handle 128Mb maximum!!

Based on Phase5 specs - yes. Based on user experiences not. 192MB works
fine on AmigaOS on my system :)

> your SCSI properly terminated too?

Yhm... terminated?? I've got nothing connected to it, so I know nothing
about termination :( Any clues? Do I need any terminator?? Maybe this is
the problem??? Or maybe I can use kernel without SCSI support?

--
Best regards,
Bartosz (Bazant) Sokolowski
A1200T PPC603@210, 060@50, 192MB RAM,
BVision, HD 30GB, FastATA etc. :)


----------------------------------------------------------------------
Ponad 100 tysiecy facetow szukajacych przyjaciolki, kochanki, zony, 
dziewczyny... Czekamy! >>> http://link.interia.pl/f170e

Re: Problems booting Debian on new hardware

[Alan B. <A.L...@lb...>]

hi,

> Few days ago I bought "new" PPC board (sig ;)) and I wanted to launch
> Debian but it failed :( I get strange kernel opses and panics and I don't
> know what to do. The main differences beetween new and the old 
> board are: SCSI (old one hadn't),
> RAM 192MB vs 80MB (I have 160MB of swap only), 68k - 040 vs 060. I've got
> no SCSI devices connected so far. 
> I removed "noscsi" from bootstrap line but I'm not sure if I should
> configure something at Blizzard SCSI menu (the one which appears after

add 'nobats' to your bootstrap line. also, use kernel 2.4.4 or 2.4.13

> hiting ESC at startup). The problem is that I even couldn't install Debian
> booting the "root.bin" image from potato CD (with more than 64MB of RAM).
> At the moment I have 3 different SIMMs: 128MB, 64MB, 16MB. I noticed that
> the more ram I have the better are chances to crash. With 64MB I can work
> for a while, with 80MB or 192MB it probably won't boot (I also removed

what speed do you have set on the board ('escape menu')? what speeds are 
the SIMMs. you are better off using matched sizes and speeds!

> bootstrap? BTW: what ammount of RAM is known to work fine on BlizzPPC
> running Debian??

i have 96 (64+32, same speed ;-) ), other have just 64, others have 128Mb.

IIRC, the Blizzard can only handle 128Mb maximum!!

> so far. My candidates for bad behavior of Debian: SCSI - something
> misconfigured, RAM - amount of maybe, RAM speed rather not, 160MB of swap
> vs 192MB of RAM? Any comments, ideas?

your SCSI properly terminated too?

alan

Problems booting Debian on new hardware

[Bartosz S. <baz...@po...>]

Hello,

Few days ago I bought "new" PPC board (sig ;)) and I wanted to launch
Debian but it failed :( I get strange kernel opses and panics and I don't
know what to do. The main differences beetween new and the old 
board are: SCSI (old one hadn't),
RAM 192MB vs 80MB (I have 160MB of swap only), 68k - 040 vs 060. I've got
no SCSI devices connected so far. 
I removed "noscsi" from bootstrap line but I'm not sure if I should
configure something at Blizzard SCSI menu (the one which appears after
hiting ESC at startup). The problem is that I even couldn't install Debian
booting the "root.bin" image from potato CD (with more than 64MB of RAM).
At the moment I have 3 different SIMMs: 128MB, 64MB, 16MB. I noticed that
the more ram I have the better are chances to crash. With 64MB I can work
for a while, with 80MB or 192MB it probably won't boot (I also removed
60nsram from bootstrap). I noticed that the more RAM I put on board the
lower address the kernel is placed. Maybe the problems are caused by
bootstrap? BTW: what ammount of RAM is known to work fine on BlizzPPC
running Debian??
Amiga side works well on new board - I can leave GLQuake for 
several hours and it won't crash. I've got
"Free Config" of memory on Blizzard, every feature with "no" - no crashes
so far. My candidates for bad behavior of Debian: SCSI - something
misconfigured, RAM - amount of maybe, RAM speed rather not, 160MB of swap
vs 192MB of RAM? Any comments, ideas?

Regards,
-- 
Bartosz (Bazant) Sokolowski
A1200T PPC603@210, 060@50, 192MB RAM, 
BVision, HD 30GB, FastATA etc. :)


----------------------------------------------------------------------
Ponad 100 tysiecy facetow szukajacych przyjaciolki, kochanki, zony, 
dziewczyny... Czekamy! >>> http://link.interia.pl/f170e

Working XF86Config-4

[<baz...@po...>]

Hi!

Can someone send me working XF86Config-4 file?? I'm trying to set up my X
system but something still fails :( I tried with contributions from APUS
site but I can't find a bug in my config file :(. I use Debian Woody with
APUS kernel 2.4.13.
I'm not sure if I should send logs to this ml, because the topic was
discussed several times.

--
Best Regards,
Bartosz (Bazant) Sokolowski
A1200T PPC603@180, 040@25, 128MB RAM,
BVision, HD 30GB, FastATA etc. :)


----------------------------------------------------------------------
Informacyjny portal INTERIA.PL >>> http://link.interia.pl/f1705

Linux-Apus & Grex4000

[amiga <am...@li...>]

Hello=20

I need an info if possible, I'd like to know if It's possible now to use =
now a grex4000 + voodoo3 pci card with Linux-Apus, and if not is someone =
is working to support it

thanks a lot=20

regards.=20

Re: Optimized XConfig

[Wilfried C. <wca...@no...>]

Hi,

> justa  quick question, but do you run X at the same resolution as you send
> via bootstrap line?  These should be the same is possible.  please check
> that the FrameBuffer is okay with your resolution by using the 'fbset'
> program on the console (you may need to search net for this tool and
> compile it)

Yes, this is the same resolution for X and the console, but the console is
in 8 bits color mode and X in 24 bits color mode. The modeline for 1024x768
was computed with the fbset tool.

> please remove the  "Load Int10" from your "Section Module" section
>
> you have an A4k with CS_PPC 604?  you'll probably need to add
>
> Option "XAANoScanlineCPUToScreenColorExpandFill"
>
> to your 'Device' section.

Ok. I will try.

> I'd seriously strip out the modules that are loaded by default in the
> XF86Config - eg DRI, GLX, DDC etc etc and put them back one at a time
> (they do some seriously playing-up things if they dont work properly on
> your setup)
>
> and i'd seriously strip out the modelines and abilities of the monitor.
> you didnt just use XF86Config-4 without checking and editing did you? You
> can kill your monitor doing things like that....

The monitor is capable to support this range of frequencies. And i use the
modeline for 1024x768 to allow fast swapping between X and the console
because this is the same resolution for both.

Willy.